WO2024076265A1 - Procédé mis en oeuvre par un premier équipement utilisateur pour coordonner des ressources pour une communication de liaison latérale entre des équipements utilisateur - Google Patents

Procédé mis en oeuvre par un premier équipement utilisateur pour coordonner des ressources pour une communication de liaison latérale entre des équipements utilisateur Download PDF

Info

Publication number
WO2024076265A1
WO2024076265A1 PCT/SE2022/050887 SE2022050887W WO2024076265A1 WO 2024076265 A1 WO2024076265 A1 WO 2024076265A1 SE 2022050887 W SE2022050887 W SE 2022050887W WO 2024076265 A1 WO2024076265 A1 WO 2024076265A1
Authority
WO
WIPO (PCT)
Prior art keywords
coordinator
ues
indication
node
capability
Prior art date
Application number
PCT/SE2022/050887
Other languages
English (en)
Inventor
Bikramjit Singh
Jose Angel LEON CALVO
Majid GERAMI
Kimmo Hiltunen
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/SE2022/050887 priority Critical patent/WO2024076265A1/fr
Publication of WO2024076265A1 publication Critical patent/WO2024076265A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/25—Control channels or signalling for resource management between terminals via a wireless link, e.g. sidelink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • Embodiments herein relate to a first user equipment (UE), a second UE and methods performed therein regarding wireless communication. Furthermore, a computer program product and a computer-readable storage medium are also provided herein. Especially, embodiments herein relate to handling or enabling communication, e.g., handling sidelink (SL) communication between UEs, in a wireless communication network.
  • UE user equipment
  • SL sidelink
  • UEs also known as wireless communication devices, mobile stations, stations (STA) and/or wireless devices, communicate via a Radio access Network (RAN) to one or more core networks (CN).
  • the RAN covers a geographical area which is divided into service areas or cell areas, with each service area or cell area being served by network node such as an access node e.g. a Wi-Fi access point or a radio base station (RBS), which in some radio access technologies (RAT) may also be called, for example, a NodeB, an evolved NodeB (eNodeB) and a gNodeB (gNB).
  • the service area or cell area is a geographical area where radio coverage is provided by the radio network node.
  • the radio network node operates on radio frequencies to communicate over an air interface with the wireless devices within range of the access node.
  • the radio network node communicates over a downlink (DL) to the wireless device and the wireless device communicates over an uplink (UL) to the access node.
  • DL downlink
  • UL uplink
  • UMTS is a third generation telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM).
  • the UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and/or High-Speed Packet Access (HSPA) for communication with user equipments.
  • WCDMA wideband code division multiple access
  • HSPA High-Speed Packet Access
  • radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto.
  • RNC radio network controller
  • BSC base station controller
  • the RNCs are typically connected to one or more core networks.
  • the Evolved Packet System comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network.
  • E-UTRAN also known as the Long-Term Evolution (LTE) radio access network
  • EPC also known as System Architecture Evolution (SAE) core network.
  • E-UTRAN/LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network.
  • the Radio Access Network (RAN) of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks.
  • NR new radio
  • Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions.
  • a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions.
  • Sidelink (SL) transmissions are direct communications between two UEs without signal relay through a base station.
  • Sidelink transmissions over NR are specified for release (Rel.)-16 allowing direct communication between two UEs without going through a base station.
  • the NR SL is an evolution of the LTE sidelink, in particular of the features introduced in Rel-14 and Rel-15 for vehicle to everything (V2X) communication.
  • LTE V2X was first specified by 3GPP in Release 14 and was enhanced in Release 15.
  • LTE V2X consists of basic features and enhancements that allow for vehicular communications. One of the most relevant aspects is the introduction of direct vehicle-to- vehicle (V2V) communication functionalities.
  • the specifications support other types of vehicle-to-anything (V2X) communications, including vehicle-to-pedestrian or pedestrian- to-vehicle (V2P), vehicle-to-infrastructure (V2I), etc., as shown in Fig.1.
  • LTE device-to-device also known as Proximity Services (ProSe)
  • Proximity Services ProSe
  • LTE V2X operation is possible with and without network coverage and with varying degrees of interaction between the UEs and the network (NW), including support for standalone, network-less operation.
  • LTE V2X mainly targets basic road safety use cases like forward collision warning, emergency braking, roadworks warning, etc.
  • Vehicle UEs supporting V2X applications may exchange their own status information such as position, speed and heading, with other nearby vehicles, infrastructure nodes and/or pedestrians.
  • the typical messages sent by the vehicles are Co-operative Awareness Message (CAM) and Decentralized Environmental Notification Message (DENM), defined by ETSI, or Basic Safety Message (BSM), defined by the Society of the Automotive Engineers (SAE).
  • CAM Co-operative Awareness Message
  • DENM Decentralized Environmental Notification Message
  • BSM Basic Safety Message
  • NR V2X communications 3GPP has started a new study item (SI) in August 2018 within the scope of Rel-16 to develop a NR version of V2X communications.
  • SI new study item
  • the NR V2X will mainly target advanced V2X services, which can be categorized into four use case groups: vehicle platooning, extended sensors, advanced driving, and remote driving.
  • the advanced V2X services would require an enhanced NR system and new NR sidelink to meet stringent requirements in terms of latency and reliability.
  • NR V2X system also expects to have higher system capacity and better coverage and to allow for easy extension to support the future development of further advanced V2X services and other services.
  • Resource allocation for sidelink transmissions Like in LTE sidelink, there are two resource allocation modes for NR sidelink: ⁇ Network-based resource allocation, in which the network selects the resources and other transmit parameters used by sidelink UEs. In some cases, the network may control every single transmission parameter. In other cases, the network may select the resources used for transmission but may give the transmitter the freedom to select some of the transmission parameters, possibly with some restrictions. In the context of NR SL, 3GPP refers to this resource allocation mode as Mode 1. ⁇ Autonomous resource allocation, in which the UEs autonomously select the resources and other transmit parameters.
  • Mode 2 in NR SL.
  • SL transmission mode 2 distributed resource selection is employed, i.e., there is no central node for scheduling and UEs play the same role in autonomous resource selection.
  • Transmission Mode 2 is based on two functionalities: reservation of future resources and sensing-based resource allocation. Reservation of future resources is done so that the UE sending a message also notifies the receivers about its intention to transmit using certain time-frequency resources at a later point in time.
  • a UE transmitting at time T informs the receivers that it will transmit using the same frequency resources at time T+100 ms.
  • Resource reservation allows a UE to predict the utilization of the radio resources in the future. That is, by listening to the current transmissions of another UE, it also obtains information about potential future transmissions. This information can be used by the UE to avoid collisions when selecting its own resources.
  • a UE predicts the future utilization of the radio resources by reading received booking messages and then schedules its current transmission to avoid using the same resources. This is known as sensing-based resource selection.
  • the sensing-based resource selection scheme specified in NR Rel-16 can be roughly summarized in the following steps and defined in the specification TS 38.214 (v16.1.0).
  • a UE senses the transmission medium during an interval [n-a, n-b], where n is a time reference, and a > b ⁇ 0 define the duration of the sensing window.
  • the length of the sensing window is (pre-)configurable.
  • the UE predicts the future utilization of the transmission medium at a future time interval [n+T1, n+T2], where T2 > T1 ⁇ 0.
  • the interval [n+T1, n+T2] is the resource selection window.
  • the UE selects one or more time-frequency resources among the resources in the selection window [n+T1, n+T2] that are predicted/determined to be selectable (e.g., idle, usable, available, etc.).
  • the text of the NR Rel-16 specification that is related to sensing and selection windows has been included. More specifically, ⁇ The sensing window is explicitly defined in Step 2.
  • ⁇ The resource selection window corresponds to the time interval [ ⁇ + ⁇ ⁇ , ⁇ + ⁇ ⁇ ], as described below.
  • the higher layer can request the UE to determine a subset of resources from which the higher layer will select resources for PSSCH/PSCCH transmission.
  • the higher layer provides the following parameters for this PSSCH/PSCCH transmission: - the resource pool from which the resources are to be reported; - L1 priority, ⁇ ⁇ ; - the remaining packet delay budget; - the number of sub-channels to be used for the PSSCH/PSCCH transmission in a slot, ⁇ subCH ; - optionally, the resource reservation interval, ⁇ rsvp_TX , in units of ms.
  • the higher layer if the higher layer requests the UE to determine a subset of resources from which the higher layer will select resources for PSSCH/PSCCH transmission as part of re- evaluation or pre-emption procedure, the higher layer provides a set of resources ( ⁇ ⁇ , ⁇ ⁇ , ⁇ ⁇ , ... ) which may be subject to re-evaluation and a set of resources ( ⁇ ⁇ , ⁇ ⁇ , ⁇ ⁇ , ... ) which may be subject to pre-emption.
  • ⁇ ⁇ is the slot with the smallest slot index among ( ⁇ ⁇ , ⁇ ⁇ , ⁇ ⁇ , ... ) and ( ⁇ ⁇ ⁇ ⁇ ⁇ , ⁇ ⁇ , ⁇ ⁇ , ... )
  • ⁇ ⁇ is equal to ⁇ ⁇ , ⁇ , where ⁇ ⁇ ⁇ ⁇ , ⁇ is defined in slots in Table 8.1.4-2 where ⁇ ⁇ is the subcarrier spacing (SCS) configuration of the SL bandwidth part (BWP).
  • SCS subcarrier spacing
  • - t2min_SelectionWindow internal parameter ⁇ ⁇ is set to the corresponding value from higher layer parameter t2min_SelectionWindow for the given value of ⁇ ⁇ .
  • SCI sidelink control information
  • - RSforSensing selects if the UE uses the PSSCH-RSRP or PSCCH-RSRP measurement, as defined in clause 8.4.2.1.
  • - sl-ResourceReservePeriodList - t0_SensingWindow internal parameter ⁇ ⁇ is defined as the number of slots corresponding to t0_SensingWindow ms.
  • the UE shall assume that any set of ⁇ subCH contiguous sub-channels included in the corresponding resource pool within the time interval [ ⁇ + ⁇ ⁇ , ⁇ + ⁇ ⁇ ] correspond to one candidate single-slot resource, where - selection of ⁇ ⁇ is up to UE implementation under 0 ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ , ⁇ , where ⁇ ⁇ ⁇ ⁇ , ⁇ is defined in slots in Table 8.1.4-2 where ⁇ ⁇ is the SCS configuration of the SL BWP; - if ⁇ ⁇ is shorter than the remaining packet delay budget (in slots) then ⁇ ⁇ is up to UE implementation subject to ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ remaining packet budget (in slots); otherwise ⁇ ⁇ is set to the remaining packet delay budget (in slots).
  • the total number of candidate single-slot resources is denoted by ⁇ total .
  • the sensing window is defined by the range of slots [ ⁇ – ⁇ ⁇ , ⁇ – ⁇ ⁇ ⁇ ⁇ , ⁇ ) where ⁇ ⁇ is defined above and ⁇ ⁇ ⁇ ⁇ , ⁇ is defined in slots in Table 8.1.4-1 where ⁇ ⁇ is the SCS configuration of the SL BWP.
  • the UE shall monitor slots which can belong to a sidelink resource pool within the sensing window except for those in which its own transmissions occur.
  • the UE shall perform the behaviour in the following steps based on PSCCH decoded and reference signal received power (RSRP) measured in these slots.
  • RSRP reference signal received power
  • the internal parameter ⁇ h( ⁇ ⁇ ) is set to the corresponding value from higher layer parameter SL-ThresRSRP_pi_pj for ⁇ ⁇ equal to the given value of ⁇ ⁇ and each priority value ⁇ ⁇ .
  • the set ⁇ ⁇ is initialized to the set of all the candidate single-slot resources.
  • the UE shall exclude any candidate single-slot resource ⁇ x,y from the set ⁇ ⁇ if it meets all the following conditions: - the UE has not monitored slot ⁇ ⁇ ⁇ in Step 2.
  • condition c in step 6 would be met.
  • sensing-based resource allocation which aims at predicting future utilization of the channel and selecting resources as to avoid collisions.
  • collisions may be detected after the initial allocation of resources in the following two cases: ⁇ After selecting a resource, but prior to performing any transmission (i.e., prior to reserving any of the selected resource), the UE may detect through sensing a potential collision affecting one of the selected resources. Note that initially, the selection of resources made a UE is an internal decision, unknown to nearby UEs. At this point we say the resource is selected (but not reserved). After transmitting a reservation for a selected resource, the surrounding UEs become aware of this condition. At this point we say that the resource is reserved (or selected and reserved).
  • a UE may sense a conflicting reservation transmitted by another UE. Which of the two reservations has precedence (if any) can be determined by looking at the priority associated with each of them. This information is signaled together with the reservation.
  • the specification defines two mechanisms to avoid collisions in the preceding two situations: ⁇ Re-evaluation (and re-selection) for the case that a resource is selected but not reserved. ⁇ Pre-emption (and re-selection) for the case that a resource is selected and reserved. Re-evaluation. In the time lapse between the selection of the resource(s) and the transmission of a corresponding reservation, other UEs may reserve the same resources.
  • a UE is allowed to re-consider its selection.
  • the purpose of such procedure is to evaluate if the earlier selected resource(s) are still suitable for transmission or not. If a UE determines that the earlier selected resource(s) is (are) not suitable for its own transmission anymore, e.g., some other UE also selected the same resource in the meantime, it triggers the resource selection mechanism again. Meaning, a new set of candidate resources is created, and the resource(s) is(are) randomly selected from the newly created candidate resource set. This procedure is referred to as re- evaluation or re-evaluation and re-selection. Pre-emption. After a reservation has been sent, the UE cannot re-evaluate its selection anymore.
  • a UE (re-)triggers the resource selection if another UE with higher priority selects the same resource for its transmission.
  • a UE with low priority transmission (re-)triggers resource selection and a new set of candidate resource set is created/determined by the UE based on the recent sensing information. This procedure is referred to as pre-emption or pre-emption and re-selection.
  • Multi-hop networks in 5G specification The possibility for multi-hop communication—already partly introduced in 5G through integrated access backhauling (IAB)—will be an important component to enabling dynamic network deployments.
  • multi-hop networks are expected as a viable option involving D2D communications. Introducing multiple hops between the source and the destination device introduce new issues that need to be studied in order to unlock the potential of these networks.
  • Network adaptability for 6G Solutions that ensure dynamic and flexible site deployments are essential for future high-capacity, resilient networks. Different types of nodes, including ad-hoc and non-terrestrial ones, will be seamlessly integrated. For smaller sites with limited reach, the network topology will evolve with multi-hop routing capabilities leading to cost-effective network densification, as dedicated transport links will not be needed. Subnetworks in 6G technology It is envisioned that in 6G, devices might be organized in several sub-networks.
  • subnetwork is a segmented piece of a larger network. More specifically, subnets are a logical partition of an IP network into multiple, smaller network segments. Following this same principle, for 6G technologies specifically involving device-to-device communications, the network is divided into several small networks, i.e., subnetworks, where typically a UE/infrastructure acts as an access point to manage the subnetwork and establish a connection with other subnetwork – by means of connecting directly with another access point or connecting to directly to devices belonging to a different subnetwork.
  • subnetworks typically a UE/infrastructure acts as an access point to manage the subnetwork and establish a connection with other subnetwork – by means of connecting directly with another access point or connecting to directly to devices belonging to a different subnetwork.
  • Subnetwork will be relevant in the scope of 6G specially in scenarios where the devices are not extremely movable or they form a stable group, e.g., in factories where robots are confined in a static scenario; or goods being transported by a truck or in-body devices.
  • Examples of subnetworks are depicted in Fig.2.
  • Fig.2 shows examples of subnetworks covering industrial setup and automotive/aircraft scenarios. The last example covers in-body devices which monitors the body measurements.
  • subnetwork in the Fig.2 can be standalone, i.e., there is no need to have any other subnetwork or external infrastructure controlling the network, or can be connected to other subnetworks or managed by an external infrastructure, e.g., the access point or any UE belonging to the subnetwork is connected to a gNB.
  • an external infrastructure e.g., the access point or any UE belonging to the subnetwork is connected to a gNB.
  • problems were first identified. In some 6G use cases, it can be especially hard to predict where most resources are needed spatially, e.g., in a large factory, or a mine, interacting robots, etc. see Fig.2. Further examples include dense deployments of sensors with dynamic traffic load, i.e., when traffic is triggered simultaneously in spatially small regions.
  • IAB Integrated Access Backhaul
  • the resource allocation procedure among several hops can be extremely cumbersome and potentially not feasible.
  • This disclosure is mostly related with operations and methods using resource allocation Mode 2 or any other mode in which the UE(s) perform autonomous resource selection, e.g., based on sensing and resource allocation.
  • the main issue when defining the resource allocation procedure for autonomous UE selection comes from the lack of a central authority present in the form gNB (or higher hierarchy node). Without this central node, the UEs might try to access the same resource or spectrum which can lead to interference and collisions based on hidden node issues.
  • the nodes can do a sensing operation as defined in resource allocation mode 2, but these solutions are inspired from contention or sensing- based algorithms, which can deliver a satisfactory performance under the constraint that the operation scope, i.e., number of engaged nodes, is kept low, e.g., one-hop scenarios.
  • the operation scope i.e., number of engaged nodes
  • the UEs will be backing-off or colliding (due to hidden node) excessively when compared to the current single hop scenarios.
  • the contention-based resource allocation performance is degraded when the traffic load start increasing, i.e., under heavy load traffic the number of collisions is greatly increased.
  • embodiments herein are divergent from the idea of Inter-UE coordination already defined in Rel-17.
  • the hierarchy of the network may not be flat, and a coordinator UE is established for the peer UEs.
  • An object of embodiments herein is, thus, to provide a mechanism that handle communication between UEs efficiently in the wireless communication network.
  • the object is achieved by providing a method performed by a first UE, such as a device to device UE, for handling communication over one or more SLs in a wireless communication network.
  • the first UE provides a coordinator indication to a second UE, wherein the coordinator indication relates to a capability of being able to perform resource allocations for one or more UEs.
  • the first UE further obtains a selection indication indicating whether the first UE is accepted, or not, as a coordinator node for the second UE.
  • the object is achieved by providing a method performed by a second UE, such as a device to device UE, for handling communication over one or more SLs in a wireless communication network.
  • the second UE obtains one or more coordinator indications of one or more UEs, wherein a coordinator indication relates to a capability of being able to perform resource allocations for the one or more UEs.
  • the second UE selects a coordinator node out of the of one or more UEs based on the obtained one or more coordinator indications.
  • the second UE further provides a selection indication to the selected coordinator node of the one or more UEs, wherein the selection indication indicates that the selected coordinator UE is accepted as a coordinator node for the second UE.
  • the object is achieved by providing a first UE, and a second UE configured to perform the methods herein, respectively.
  • a first UE such as a device to device UE, for handling communication over one or more SLs in a wireless communication network.
  • the first UE is configured to provide a coordinator indication to a second UE, wherein the coordinator indication relates to a capability of being able to perform resource allocations for one or more UEs.
  • the first UE is further configured to obtain a selection indication indicating whether the first UE is accepted, or not, as a coordinator node for the second UE.
  • the object is achieved by providing a second UE, such as a device to device UE, for handling communication over one or more SLs in a wireless communication network.
  • the second UE is configured to obtain one or more coordinator indications of one or more UEs, wherein a coordinator indication relates to a capability of being able to perform resource allocations for the one or more UEs.
  • the second UE is further configured to select a coordinator node out of the of one or more UEs based on the obtained one or more coordinator indications, and to provide a selection indication to the selected coordinator node of the one or more UEs, wherein the selection indication indicates that the selected coordinator UE is accepted as a coordinator node for the second UE.
  • a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out any of the methods herein, as performed by the first UE or the second UE, respectively.
  • a computer-readable storage medium having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods herein, as performed by the first UE or the second UE, respectively.
  • embodiments herein disclose a subnetwork scenario or multi-hop chain, especially without network, or network is not capable of allocating resources and/or provide configuration, where one or more coordinator UE nodes are selected to do scheduling or resource allocation among UE nodes.
  • the selection of a coordinator UE may be based on certain rules including the UE capability, e.g., higher power class or higher amount of features in the UE, or based on a pre-configured identity of the UE.
  • the coordinator node manages the resource allocation of the connected UE, e.g., allocating specific resource pools or regions to different connected UEs.
  • embodiments herein are handling communication in a resource efficient manner resulting in an improved performance of the wireless communication network.
  • Fig.1 shows V2X scenarios for an LTE-based network (NW); Fig.2 shows examples of subnetworks covering industrial setup and automotive/aircraft scenarios;
  • Fig.3 is a schematic overview depicting a wireless communications network in accordance with embodiments herein;
  • Fig.4 is a combined signalling scheme and flowchart, showing communications between a UE and a network node, in accordance with embodiments herein;
  • Fig.5 is a schematic flowchart illustrating a method performed by a first UE, in accordance with embodiments herein;
  • Fig.6 is a schematic flowchart illustrating a method performed by a second UE, in accordance with embodiments herein;
  • Fig.7 a multi-hop scenario consisting of different subnetworks;
  • Fig.8 is depicting a first UE in accordance with some embodiments;
  • Fig.9 is depicting a second UE
  • Embodiments herein are described within the context of 3GPP NR radio technology. It is understood that the problems and solutions described herein are equally applicable to wireless access networks and user-equipments (UEs) implementing other access technologies and standards.
  • NR is used as an example technology where embodiments are suitable, and using NR in the description therefore is particularly useful for understanding the problem and solutions solving the problem.
  • embodiments are applicable also to 3GPP LTE, or 3GPP LTE and NR integration, also denoted as non-standalone NR and also non-3GPP technologies such as WiFi or Bluetooth.
  • Embodiments herein relate to wireless communication networks in general.
  • Fig.3 is a schematic overview depicting a wireless communication network 1.
  • the wireless communication network 1 comprises one or more RANs and one or more CNs.
  • the wireless communication network 1 may use one or a number of different technologies, such as Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Fifth Generation (5G), Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.
  • LTE Long Term Evolution
  • 5G Fifth Generation
  • WCDMA Wideband Code Division Multiple Access
  • GSM/EDGE Global System for Mobile communications/enhanced Data rate for GSM Evolution
  • WiMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • wireless devices e.g., a first UE 10 also denoted as a first UE 10 or just the SL UE, such as a mobile station, a non-access point (non-AP) STA, a STA, an internet of things (IoT) capable device, a user equipment and/or a wireless terminal, communicate via one or more Access Networks (AN), e.g. RAN, to one or more core networks (CN).
  • AN e.g. RAN
  • CN core networks
  • UE is a non-limiting term which means any terminal, wireless communication terminal, user equipment, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, IoT device, or node e.g.
  • MTC Machine Type Communication
  • D2D Device to Device
  • IoT device IoT device
  • the wireless communication network 1 comprises a radio network node 12 providing radio coverage over a geographical area, a first service area 14, of a radio access technology (RAT), such as LTE, Wi-Fi, WiMAX or similar.
  • the radio network node 12 may be a transmission and reception point e.g. a radio network node such as a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access node, an access controller, a base station, e.g.
  • WLAN Wireless Local Area Network
  • AP STA Access Point Station
  • a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), a gNodeB (gNB), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a UE within the area served by the radio network node 12 depending e.g. on the radio access technology and terminology used.
  • the radio network node 12 may alternatively or additionally be a controller node or a packet processing node such as a radio controller node or similar.
  • the wireless communication network 1 further comprises one or more second UEs 13, communicating with one another and/or with the first UE 10 over one or more SLs.
  • Embodiments herein relate to selection of one or more coordinator UEs, also referred to as coordinator node, to do scheduling or resource allocation among the UEs.
  • the selection of the coordinator node is based on certain rules including the UE capability, e.g., higher power class or higher amount of features in the UE, or based on a pre-configured identity of the UE.
  • the first UE 10 manages the resource allocation of the connected UE, e.g., allocating specific resource pools or regions to different connected UEs.
  • Advantages of the herein described embodiments are one or more of the following: - To reduce the potential number of collisions as the coordinator node will allocate/manage the resources of the peer UEs rather than having the peer UE relying on sensing procedures. a. Due to reduction in collisions, the probability of resource wastage is reduced, e.g., there is no need to reserve resources for HARQ feedback and/or the number of potential retransmissions is reduced.
  • the UEs under control of the coordinator node do not need to perform sensing actively as a coordinator node will take responsibility of resource allocation, and thus battery power is saved because UEs do not need to perform sensing for monitoring potential interferers. a. It is envisioned that in many of the potential 6G use cases, the UEs involved in multi-hop/flexible topologies are devices with a limited battery. Additionally, enabling a connection to a coordinator node allows for the following: - To increase the reliability of the communications.
  • one of sidelink main uses is to increase the redundancy of the communication by increasing the number of potential paths or to offload certain paths, e.g., the direct path with the coordinator node uses normal licensed SL while the indirect path uses unlicensed spectrum.
  • the direct path with the coordinator node uses normal licensed SL while the indirect path uses unlicensed spectrum.
  • Another aspect could be the case where a connected UE has both a direct link to the coordinator node and also indirect connection to the coordinator node, i.e., by means of an intermediate UE.
  • Fig.4 is a combined flowchart and signalling scheme according to embodiments herein.
  • the actions may be performed in any suitable order.
  • a number of UEs may exchange or transmit respective coordinator indications between one another.
  • Respective coordinator indication relates to a capability of being able to perform resource allocations for one or more UEs. For example, each UE may transmit a capability of respective UE, for example, in terms of power level, bandwidth range or similar.
  • Respective UE receiving the coordinator indications may then compare all the coordinator indications with one another or with configured thresholds.
  • the respective UE such as one or more second UEs 13 may then determine that, for example, the first UE 10 is to be the coordinator node for the respective UE based on the comparison of the received coordinator indications.
  • Action 404. The second UE 13 sends a response such as a selection indication to the first UE 10, wherein the selection indication indicates the selected coordinator node.
  • the first UE 10, being selected as coordinator node may then allocate resources to the second UEs that indicated that the first UE 10 is the coordinator node.
  • the method actions performed by the first UE 10 for handling communication over one or more sidelinks in the wireless communications network will now be described with reference to a flowchart depicted in Fig.5.
  • the actions do not have to be taken in the order stated below, but may be taken in any suitable order. Dashed boxes indicate optional features.
  • the communication may be using resources in a licensed and/or a unlicensed spectrum.
  • Action 501. The first UE 10 provides a coordinator indication to the second UE 13, wherein the coordinator indication relates to a capability of being able to perform resource allocations for one or more UEs.
  • the coordinator indication may comprise one or more parameter values, and wherein the one or more parameter values comprise one or more of the following: UE capability of the first UE 10; ID of the first UE 10; location indication of the first UE 10; traffic load information, IDs related to the resource allocation region, power capability of the first UE 10, bandwidth part capability of the first UE 10.
  • the first UE 10 may provide the coordinator indication by transmitting one or more beacons with the coordinator indication.
  • the indication may in fact be transmission power at the first UE indicating the capability of being able to perform resource allocations for one or more UEs.
  • a UE such as the first UE 10 may indicate that it has lower capability than a normal UE, e.g., smaller bandwidth part operation, and thus the UE cannot become coordinator node since it needs to operate in at least the same bands as the UEs connected to it. Also, the first UE 10 may indicate that it has power limitation (e.g., small battery or low battery), and thus it cannot become coordinator node since a coordinator node will engage in transmissions or signalling over larger geographic area for resource allocations for various UEs and, thus the coordinator UE should have minimal limitations towards power constraints.
  • the first UE 10 further obtains a selection indication indicating whether the first UE is accepted, or not, as a coordinator node for the second UE 13. Action 503.
  • the first UE 10 may, when the selection indication indicates that the first UE 10 is accepted as a coordinator node, allocate a unique identity to the first UE 10 and/or the second UE 13.
  • the unique identifier allocated to the first and/or second UE 13 may be based on an identity of the coordinator node, i.e., the first UE 10. Action 504.
  • the first UE 10 may, when the selection indication indicates that the first UE 10 is accepted as a coordinator node, perform a resource allocation for communication related to the second UE 13.
  • the first UE 10 may manage resource allocation in a multi-hop scenario for a plurality of UEs.
  • the first UE 10 may perform resource allocation based on a capability of the second UE 13, or respective capability of one or more UEs.
  • the first UE 10 may adjust one or more operation parameters to align its operation with one or more UEs connected to the first UE 10.
  • a coordinator node may adjust its operation, e.g., transmission power, bandwidth, etc., to align its operation with the UEs connected to it.
  • the first UE 10 may signal to the second UE 13 an indication to use a pool or a set of resources to communicate with one or more UEs.
  • the indication may indicate different spectrum regions related to multiple hops or carriers in an orthogonal or shared manner.
  • the resource pool to be used may thus be allocated in different carriers, i.e., the receiving UE is able to receive resources which can be located in different carriers. This can be understood as multi-carrier scheduling.
  • the resource pools belonging to different paths or carriers can be defined in orthogonal (non-shared) or shared manner.
  • the one or more operation parameters, the pool, set of resources, or spectrum region may be based on identity of the second UE 13 and/or capability of the second UE 13.
  • the first UE 10 may allocate different spectrum regions to the the one or more node. These different spectrum regions may be related to multiple hops or carriers in an orthogonal or shared manner. The different spectrum regions may be based on the ID of the first UE, and/or based on certain capabilities.
  • the first UE 10 may set multiple power thresholds for different types of transmissions based on spectrum region or UE capabilities of the second UE 13.
  • the first UE 10 may signal to the second UE 13 to use a specific resource pool or set of resource to communicate with the rest of connected UEs connected to the same coordinator UE.
  • the resource pool/resource set to be used may be based on the region or UE capabilities.
  • the method actions performed by the second UE 13 for handling communication over one or more sidelinks in the wireless communications network according to embodiments will now be described with reference to a flowchart depicted in Fig.6. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Dashed boxes indicate optional features.
  • the communication may be using resources in a licensed and/or an unlicensed spectrum. Action 601.
  • the second UE 13 obtains one or more coordinator indications of one or more UEs, wherein a coordinator indication relates to a capability of being able to perform resource allocations for the one or more UEs.
  • Respective coordinator indication may comprise one or more parameter values, and wherein the one or more parameter values comprise one or more of the following: UE capability of a UE; ID of a UE; location indication of a UE; traffic load information, IDs related to the resource allocation region, power capability of a UE, bandwidth part capability of a UE.
  • the second UE 13 may obtain the one or more coordinator indications by receiving signalling from the one or more UEs. The signalling may be received over dedicated resources. Action 602.
  • the second UE 13 selects a coordinator node out of the of one or more UEs based on the obtained one or more coordinator indications.
  • the second UE 13 may select the coordinator node by comparing the one or more coordinator indications with one another and/or with preconfigured set parameters.
  • the parameters may comprise thresholds and/or values related to: signal strength such as RSRP, SINR, Coordinator ID, order/time of receiving the coordinator indication, coordinator capabilities.
  • the second UE 13 may select coordinator node by comparing the signalling from the one or more UEs. It should be noted that when a UE indicates with a coordination indication that the UE has lower capability than a set threshold of capability, e.g.
  • the second UE 13 will not accept the UE to become a coordinator since it needs to operate in at least the same bands as the second UE 13 and/or able to reach all UEs connected to it.
  • a UE will be selected with a lower priority/likelihood as coordinator node based on its limitations, e.g., power limitation or lower capabilities. It should further be noted that every connected UE connects to at least one of the identified possible coordinator UE. Action 603.
  • the second UE 13 provides the selection indication to the selected coordinator node of the one or more UEs, wherein the selection indication indicates that the selected coordinator node, such as the first UE 10, is accepted as a coordinator node for the second UE 13.
  • the selection indication may comprise a feedback signalling that is transmitted in a dedicated resource, and/or as a standalone transmission, and/or transmitted together with other data, and/or scrambled based on a UE characteristics from the second UE or the coordinator node.
  • the second UE 13 may obtain a unique identifier based on an identity of the coordinator node.
  • the second UE 13 may receive an adjustment indication from the coordinator node adjusting one or more operation parameters at the second UE 13.
  • the second UE 13 may receive signalling from the coordinator node, with an indication to use a pool or a set of resources to communicate with one or more UEs.
  • the indication may indicate different spectrum regions related to multiple hops or carriers in an orthogonal or shared manner.
  • the one or more operation parameters, the pool, set of resources, or spectrum region may be based on identity of the second UE 13 and/or capability of the second UE 13.
  • Embodiments herein define a method to dynamically, or semi-statically, configure or select one or more UEs in a group of UEs participating in a multi-hop communication to perform/become temporarily a coordinator /parent node in order to assist (or manage) in the resource allocation procedure its peer UEs which are part of the multi-hop communication.
  • Fig.7 shows an example of a scenario where this procedure is beneficial including different coordinator nodes creating subnetworks. For instance, a tunnel or factory where the devices are located, and they need to communicate to each other (and potentially with devices outside the restricted area).
  • This framework is especially beneficial under the assumption that the UEs will perform a stable group, i.e., there are no frequent re- configurations of the members of the sub-network.
  • Fig.7 shows a multi-hop scenario consisting of different subnetworks.
  • one or more UEs are selected to act as coordinator UE(s) in the multi-hop chain.
  • One of the main manners to select the coordinator UE is based on the UE capability, e.g., based on the available power of the UE or as a hardwired capability.
  • the selection of the coordinator node can be based on signalling transmitted among the different peer UEs, e.g., based on a certain parameter of the signalling or based on ID of the transmitted node.
  • the coordinator node manages the resource allocation in the multi-hop scenario.
  • no focus is on routing algorithm or establishing a routing table. The assumption is that it is already done or known by the different UEs in the network.
  • the primary focus is (a) selecting the coordinator UE, which cannot be done by any external structure, e.g., cell, neither based on pre-configuration and (b) subsequently define the resource allocation procedure by the coordinator UEs to its connected UEs in the multi-hop scenario.
  • Embodiments herein are described in the context of sidelink communications.
  • a subnetwork is used as a general term to identify several UEs connected to a coordinator node or coordinator UE.
  • Embodiments herein enable a resource allocation procedure by selecting a coordinator node among the UEs participating in a multi-hop scenario.
  • the coordinator node manages/allocates the resources to the UEs in the multi-hop scenario.
  • an optimal resource allocation i.e., lower number of collisions and lower power consumption is obtained due to leaving all the resource allocation procedures to the coordinator UE.
  • the methods herein may be divided into two different steps: Step 1) o One or multiple UEs are selected as coordinator node(s) for a multi- hop/subnetwork scenario.
  • the selection of the coordinator node is based on signalling shared among the peer UEs; or based on specific UE capabilities to manage the resource allocation procedure; or based on a hardwired/configured identity of the UE. ⁇ It is herein provided different mechanisms to select the coordinator node depending on certain rules/parameters, e.g., signalling, scenario (subnetworks), capability or UE identity. Step 2) o Upon selecting one or several coordinator nodes in the multi-hop network or subnetwork, the resource allocation and related procedures are performed by the coordinator node in order to enhance the performance of the UEs. In the following, embodiments related to the two different aforementioned steps are defined. Selection of coordinator UE(s).
  • a UE capability may be signaled in order to indicate that a UE can act as a coordinator node or UE. Hence, if such capability signalling is transmitted, the coordinator node can be chosen among the UEs with this capability enabled.
  • the UE capability to serve as coordinator node may be hardwired in the UE, e.g., a specific type of device built to perform as coordinator UE.
  • the coordinator nodes may broadcast some beacon signalling.
  • the UEs read the beacons and gather beacon reports or other information included in the signalling.
  • the beacon signalling sequence may be a function of a positioning coordinate and/or UE ID, which can be unique information or reused along different subnetworks.
  • a specific resource may be configured for beacon transmissions. In case of collision among the beacons, if the orthogonality is maintained, the receiver can still identify different beacon transmissions coming from different UEs.
  • the UE connected to the coordinator node may transmit response/feedback to the coordinator node upon having selected it as a coordinator node. This response/feedback may be transmitted in dedicated resources and/or the signalling may be scrambled based on certain UE characteristics from the connected or coordinator UE, e.g., UE_ID or location. Every connected UE connects to at least one of the identified coordinator UE. This enables that every connected UE is under the control of at least one coordinator node disabling that the connected UE(s) behaviour is left uncontrolled.
  • the confirmation/feedback information may be transmitted as stand-alone signalling or may also be transmitted alongside other data, e.g., source and destination IDs.
  • the first UE 10 may indicate that it has power limitation, e.g., small battery or low battery, and thus it cannot become a coordinator node. This is due to the fact that coordinator node will engage in transmissions or signalling over larger geographic area for resource allocations for various UEs and, thus the coordinator UE should have minimal limitations towards power constraint.
  • the first UE 10 may indicate that it has lower capability than a normal UE, e.g., smaller bandwidth part operation, and thus it cannot become coordinator node since it needs to operate in at least the same bands as the nodes connected to it.
  • Every UE may have a unique ID when performing as a coordinator node. These unique IDs may be a function of UE ID, or coordinator UEs are allocated separately unique IDs (independent of UE ID).
  • the UE IDs to be used by coordinator UEs may be reserved from a pool of available IDs to be used.
  • the coordinator node may allocate to its connected UEs an ID which is generated based on the ID from the coordinator node and it is transmitted to its UEs in range, e.g., in unicast/multicast or broadcast manner. For instance, the coordinator node ID is established as 100 and the connected UE ID can be derived as follows: the connected UE 1 and connected UE 2 allocated IDs are 100
  • the coordinator UE ID can be defined either as 100 or either 100
  • the resource allocation for a connected UE may be prioritized based on characteristics of coordinator nodes, e.g., based on location or based on the particular ID.
  • the connected UE may prioritize the transmission generated by a coordinator UE based on certain characteristics, e.g., based on location, based on the particular ID and/or based on the received signal strength.
  • 1 is secondarily connected to the coordinator UE1, i.e., the UE2
  • the following non-limiting options may be considered: -
  • 1 is able to discover the coordinator UE1 and receive signalling from it. However, it is up to the connected UE implementation to decide whether to follow the coordinator UE1 recommendations in terms of resource allocation procedure. a.
  • Certain rules based on location or signal strength can be used in order to decide whether the connected UE follows the recommendation from the coordinator UE1.
  • the coordinator UE may broadcast its identity indicating – which is part of the reserved IDs – indicating that it is a coordinator node, and optionally, the resources it had reserved for its connected UEs.
  • the coordinator UE may broadcast its identity indicating – which is part of the reserved IDs – indicating that it is a coordinator node, and optionally, the resources it had reserved for its connected UEs.
  • the coordinator node may be allowed to allocate or reserve resources for external UE(s) even though they are not part of the subnetwork.
  • the primary and the secondary connection to coordinator UEs from the connected UE can be in licensed and/or unlicensed spectrum.
  • the primary connection to a coordinator UE may be performed using licensed spectrum while the secondary connection is under unlicensed spectrum.
  • the coordinator node transmits the following information in a non-limiting manner, e.g., broadcast, multicast or unicast.
  • - Its identity or user_ID as coordinator node
  • the traffic load information can be the actual or expected traffic load if there is some traffic prediction enabled.
  • - UE_IDs related to the resource allocation region or zone which has been reserved to be used by its connected UEs.
  • the coordinator node may allocate resources to its connected UEs based on UEs capability, say RedCap UE, normal UE, low power node, etc. For example, for UEs defined as RedCap UE, the resource allocation takes into consideration the fewer BWPs/carrier or lower BW for its allocation.
  • the spectrum may be divided into reference regions.
  • the coordinator UE allocates these reference regions to the multiple hops or carriers in an orthogonal or shared manner. For example, in Fig.7, coordinator UE2 can allocate resources of the same reference region connected UE2
  • the reference region allocated to a connected UE by a coordinator UE may be active for certain time. Once the timer value reaches null or zero, the connected UE cannot access the reference region and the coordinator UE would not accept transmission from the connected UE located in that region.
  • the grants and/or transmissions from the second UE 13 may be ignored or discarded by the coordinator node 10 after the expiration of the timer or based on the reference region where the transmission is generated.
  • the resources to be used by the connected UE may be based on the reference region where the connected UE is located.
  • the reference region may be based on the Zone_ID or based on the UE_ID, which is already included in specifications and exchanged during data transmission.
  • the second UE 13 may request the coordinator node for resources within a specific reference region, e.g., after some kind of establishment process, or if the timer is expired, or if synchronization fails, etc.
  • the coordinator node 10 may set of multiple power thresholds for different types of transmissions. For example, for data transmission, it can have lower maximum power threshold as the data transmissions are limited to neighboring UEs while for control or synchronization signalling the reach of the communication is higher.
  • the coordinator node 10 may set a different power threshold for each of the connected UEs based on their location or capability or priority of the expected transmissions.
  • the coordinator node 10 may select a particular beam or transmitter-receiver pair to transmit data/signalling to a specific UE or group of UEs.
  • the coordinator node For resource allocation or control signaling associated with different connected UEs under the coordinator node, the coordinator node has a larger power threshold as it covers a larger geographic area compared to the connected UEs.
  • the coordinator node may allocate one or more resources to a UE in following manner, where these options can be combined or not to create new options, e.g., - Allocate orthogonal resource or pool, - Allocate non-orthogonal resources or pools, - Multiple pools to a UE, where some pools can be orthogonal/dedicated and others not, - Coordinator node 10 may stipulate a policy that indicates the connected UE behavior , e.g., whether sensing shall be performed or the maximum transmit power, in a resource pool if the connected UE UE desires to transmit in that resource pool.
  • the coordinator node may signal to a connected UE (e.g., using sidelink control information) to use a specific resource pool or set of resource to communicate with the rest of connected UEs connected to the same coordinator node. Additionally, the coordinator node may indicate a set of resources or resource pool to be used only to transmit signals to the coordinator UE.
  • Fig.8 is a block diagram depicting the first UE 10 for handling communication over one or more sidelinks in the wireless communication network according to embodiments herein.
  • the first UE 10 may comprise processing circuitry 801, e.g. one or more processors, configured to perform the methods herein.
  • the first UE 10 and/or the processing circuitry 801 is configured to provide the coordinator indication to the second UE, wherein the coordinator indication relates to the capability of being able to perform resource allocations for one or more UEs.
  • the coordinator indication may comprise one or more parameter values, wherein the one or more parameter values comprise one or more of the following: UE capability of the first UE; ID of the first UE10 ; location indication of the first UE 10; traffic load information, IDs related to the resource allocation region, power capability of the first UE 10, bandwidth part capability of the first UE 10.
  • the first UE 10 and/or the processing circuitry 801 may be configured to provide the coordinator indication by transmitting one or more beacons with the coordinator indication.
  • the coordinator indication may be signalled over dedicated resources.
  • the first UE 10 and/or the processing circuitry 801 is configured to obtain the selection indication indicating whether the first UE 10 is accepted, or not, as a coordinator node for the second UE 13.
  • the selection indication may be received from the second UE 13 or another UE.
  • the selection indication may comprise a feedback signalling that is received in a dedicated resource, and/or as a standalone transmission, and/or transmitted together with other data, and/or scrambled based on a UE characteristics from the second UE 13 or the coordinator node.
  • the first UE 10 and/or the processing circuitry 801 may be configured to, when the selection indication indicates that the first UE 10 is accepted as a coordinator node, allocate a unique identity to the first UE 10 and/or the second UE 13.
  • the unique identifier allocated to the first and/or second UE may be based on the identity of the coordinator node, i.e., the first UE 10.
  • the first UE 10 and/or the processing circuitry 801 may be configured to, when the selection indication indicates that the first UE 10 is accepted as a coordinator node, perform a resource allocation for communication related to the second UE 13.
  • the first UE 10 and/or the processing circuitry 801 may be configured to adjust one or more operation parameters to align its operation with one or more UEs connected to the first UE 10, e.g., transmission power, bandwidth, etc.
  • the first UE 10 and/or the processing circuitry 801 may be configured to perform the resource allocation comprises managing resource allocation in a multi-hop scenario for a plurality of UEs.
  • the first UE 10 and/or the processing circuitry 801 may be configured to perform the resource allocation based on capability of the second UE 13.
  • the first UE 10 and/or the processing circuitry 801 may be configured to perform the resource allocation by further signalling to the second UE 13 the indication to use a pool or a set of resources to communicate with one or more UEs.
  • the indication may indicate different spectrum regions related to multiple hops or carriers in an orthogonal or shared manner.
  • the one or more operation parameters, the pool, set of resources, or spectrum region may be based on identity of the second UE and/or capability of the second UE 13.
  • the spectrum regions may be based on the connected node ID or based on certain capabilities.
  • the coordinator node may set multiple power thresholds for different types of transmissions based on the region or UE capabilities of the connected UE(s).
  • the first UE 10 may signal to a connected UE to use a specific resource pool or set of resources to communicate with the rest of connected UEs connected to the first UE 10.
  • the resource pool/set of resources to be used may be based on the spectrum region or UE capabilities.
  • the first UE 10 further comprises a memory 806.
  • the memory comprises one or more units to be used to store data on, such as indications, SL carriers, CSI information, requests, configuration, strengths or qualities, grants, coordinator indications, selection indications, requests, commands, timers, applications to perform the methods disclosed herein when being executed, and similar.
  • the first UE 10 may comprise the processing circuitry and the memory, said memory comprising instructions executable by said processing circuitry whereby said first UE is operative to perform the methods herein.
  • the first UE 10 comprises a communication interface 809 comprising e.g. a transmitter, a receiver, a transceiver and/or one or more antennas.
  • the methods according to the embodiments described herein for the first UE 10 are respectively implemented by means of e.g.
  • a computer program product 807 or a computer program comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the first UE 10.
  • the computer program product 807 may be stored on a computer-readable storage medium 808, e.g. a universal serial bus (USB) stick, a disc, or similar.
  • the computer-readable storage medium 808, having stored thereon the computer program product may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the first UE 10.
  • the computer-readable storage medium may be a non-transitory or a transitory computer- readable storage medium.
  • Fig.9 is a block diagram depicting the second UE 13 for handling communication over one or more sidelinks in the wireless communication network according to embodiments herein.
  • the second UE 13 may comprise processing circuitry 901, e.g. one or more processors, configured to perform the methods herein.
  • the second UE 13 and/or the processing circuitry 901 is configured to obtain one or more coordinator indications of one or more UEs, wherein a coordinator indication relates to a capability of being able to perform resource allocations for the one or more UEs.
  • Respective coordinator indication may comprise one or more parameter values, wherein the one or more parameter values comprise one or more of the following: UE capability of a UE; ID of the a UE; location indication of the a UE; traffic load information, IDs related to the resource allocation region, power capability of a UE, bandwidth part capability of a UE.
  • the second UE 13 and/or the processing circuitry 901 is configured to select a coordinator node out of the of one or more UEs based on the obtained one or more coordinator indications.
  • the second UE 13 and/or the processing circuitry 901 may be configured to select the coordinator node by comparing the one or more coordinator indications with one another and/or with preconfigured set parameters, such as signal strength, transmission power, location etc.
  • the second UE 13 and/or the processing circuitry 901 may be configured to obtain the one or more coordinator indications by receiving signalling from the one or more UEs, and then be configured to select the coordinator node by comparing the signalling from the one or more UEs. The signalling may be received over dedicated resources.
  • the second UE 13 and/or the processing circuitry 901 is configured to provide the selection indication to the selected coordinator node of the one or more UEs, such as the first UE 10, wherein the selection indication indicates that the selected coordinator UE is accepted as a coordinator node for the second UE 13.
  • the selection indication may comprise a feedback signalling that is transmitted in a dedicated resource, and/or as a standalone transmission, and/or transmitted together with other data, and/or scrambled based on a UE characteristics from the second UE 13 or the coordinator node.
  • the second UE 13 and/or the processing circuitry 901 may be configured to obtain a unique identifier based on an identity of the coordinator node.
  • the second UE 13 and/or the processing circuitry 901 may be configured to receive the adjustment indication from the coordinator node adjusting one or more operation parameters at the second UE 13.
  • the second UE 13 and/or the processing circuitry 901 may be configured to receive the signalling from the coordinator node, the indication to use a pool or a set of resources to communicate with one or more UEs.
  • the indication may indicate different spectrum regions related to multiple hops or carriers in an orthogonal or shared manner.
  • the one or more operation parameters, the pool, set of resources, or spectrum region may be based on identity of the second UE and/or capability of the second UE 13.
  • the second UE 13 further comprises a memory 906.
  • the memory comprises one or more units to be used to store data on, such as indications, SL carriers, CSI information, requests, configuration, strengths or qualities, grants, coordinator indications, selection indications, requests, commands, timers, applications to perform the methods disclosed herein when being executed, and similar.
  • the first UE 10 may comprise the processing circuitry and the memory, said memory comprising instructions executable by said processing circuitry whereby said second UE 13 is operative to perform the methods herein.
  • the second UE 13 comprises a communication interface 909 comprising e.g. a transmitter, a receiver, a transceiver and/or one or more antennas.
  • the methods according to the embodiments described herein for the second UE 13 are respectively implemented by means of e.g. a computer program product 907 or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the second UE 13.
  • the computer program product 907 may be stored on a computer-readable storage medium 908, e.g. a universal serial bus (USB) stick, a disc, or similar.
  • USB universal serial bus
  • the computer-readable storage medium 908, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the second UE 13.
  • the computer-readable storage medium may be a non-transitory or a transitory computer-readable storage medium.
  • a more general term “radio network node” is used and it can correspond to any type of radio network node or any network node, which communicates with a wireless device and/or with another network node.
  • network nodes are NodeB, Master eNB, Secondary eNB, a network node belonging to Master cell group (MCG) or Secondary Cell Group (SCG), base station (BS), multi- standard radio (MSR) radio node such as MSR BS, eNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node e.g.
  • the non-limiting term wireless device or user equipment is used and it refers to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system.
  • Examples of UE are target device, device-to-device (D2D) UE, proximity capable UE (aka ProSe UE), machine type UE or UE capable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.
  • D2D device-to-device
  • ProSe UE proximity capable UE
  • M2M machine type UE or UE capable of machine to machine (M2M) communication
  • PDA personal area network
  • PAD machine to machine
  • Tablet mobile terminals
  • smart phone smart phone
  • laptop embedded equipped (LEE) laptop mounted equipment
  • LME laptop mounted equipment
  • USB dongles etc.
  • the embodiments are described for 5G. However the embodiments are applicable to any RAT or multi-RAT systems, where the UE receives and/or transmit signals (e.g. data) e.g. LTE, LTE FDD/TDD, WCDMA/HSPA,
  • functions means or modules may be implemented using digital logic and/or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and/or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example. Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware.
  • ASIC application-specific integrated circuit
  • a communication system includes a telecommunication network 3210, such as a 3GPP-type cellular network, which comprises an access network 3211, such as a radio access network, and a core network 3214.
  • the access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs or other types of wireless access points being examples of the radio network node 12 herein, each defining a corresponding coverage area 3213a, 3213b, 3213c.
  • Each base station 3212a, 3212b, 3212c is connectable to the core network 3214 over a wired or wireless connection 3215.
  • a first user equipment (UE) 3291 being an example of the UE 10 and relay UE 13, located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c.
  • a second UE 3292 in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. While a plurality of UEs 3291, 3292 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212.
  • the telecommunication network 3210 is itself connected to a host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 3221, 3222 between the telecommunication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may go via an optional intermediate network 3220.
  • the intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 3220, if any, may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more sub-networks (not shown).
  • the communication system of Fig.10 as a whole enables connectivity between one of the connected UEs 3291, 3292 and the host computer 3230.
  • the connectivity may be described as an over-the-top (OTT) connection 3250.
  • OTT over-the-top
  • the host computer 3230 and the connected UEs 3291, 3292 are configured to communicate data and/or signaling via the OTT connection 3250, using the access network 3211, the core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection 3250 may be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of routing of uplink and downlink communications. For example, a base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291.
  • a host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 3300.
  • the host computer 3310 further comprises processing circuitry 3318, which may have storage and/or processing capabilities.
  • the processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the host computer 3310 further comprises software 3311, which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318.
  • the software 3311 includes a host application 3312.
  • the host application 3312 may be operable to provide a service to a remote user, such as a UE 3330 connecting via an OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the remote user, the host application 3312 may provide user data which is transmitted using the OTT connection 3350.
  • the communication system 3300 further includes a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330.
  • the hardware 3325 may include a communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 3300, as well as a radio interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in Fig.11) served by the base station 3320.
  • the communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310.
  • the connection 3360 may be direct or it may pass through a core network (not shown in Fig.11) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the base station 3320 further has software 3321 stored internally or accessible via an external connection.
  • the communication system 3300 further includes the UE 3330 already referred to. Its hardware 3335 may include a radio interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located.
  • the hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • the UE 3330 further comprises software 3331, which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338.
  • the software 3331 includes a client application 3332.
  • the client application 3332 may be operable to provide a service to a human or non-human user via the UE 3330, with the support of the host computer 3310.
  • an executing host application 3312 may communicate with the executing client application 3332 via the OTT connection 3350 terminating at the UE 3330 and the host computer 3310.
  • the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data.
  • the OTT connection 3350 may transfer both the request data and the user data.
  • the client application 3332 may interact with the user to generate the user data that it provides.
  • the host computer 3310, base station 3320 and UE 3330 illustrated in Fig.11 may be identical to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291, 3292 of Fig.10, respectively. This is to say, the inner workings of these entities may be as shown in Fig.11 and independently, the surrounding network topology may be that of Fig.10.
  • the OTT connection 3350 has been drawn abstractly to illustrate the communication between the host computer 3310 and the user equipment 3330 via the base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the UE 3330 or from the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve the performance since SLs are handled more efficiently and thereby provide benefits such as reduced user waiting time, and better responsiveness.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311, 3331 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 3320, and it may be unknown or imperceptible to the base station 3320.
  • measurements may involve proprietary UE signaling facilitating the host computer’s 3310 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 3311, 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while it monitors propagation times, errors etc.
  • Fig.12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figs.10 and 11. For simplicity of the present disclosure, only drawing references to Fig.12 will be included in this section.
  • a first step 3410 of the method the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE executes a client application associated with the host application executed by the host computer.
  • Fig.13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figs.10 and 11. For simplicity of the present disclosure, only drawing references to Fig.13 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE receives the user data carried in the transmission.
  • Fig.14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figs.10 and 11. For simplicity of the present disclosure, only drawing references to Fig.14 will be included in this section.
  • the UE receives input data provided by the host computer.
  • the UE provides user data.
  • the UE provides the user data by executing a client application.
  • the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in an optional third substep 3630, transmission of the user data to the host computer.
  • the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • Fig.15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figs.10 and 11. For simplicity of the present disclosure, only drawing references to Fig.15 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • the host computer receives the user data carried in the transmission initiated by the base station.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente invention concernent par exemple un procédé mis en oeuvre par un premier équipement utilisateur, UE, (10) pour gérer une communication sur une ou plusieurs liaisons latérales dans un réseau de communication sans fil. Le premier UE (10) fournit une indication de coordinateur à un second UE, l'indication de coordinateur concernant une capacité d'être de pouvoir effectuer des attributions de ressources pour une ou plusieurs UE. Le premier UE (10) obtient en outre une indication de sélection indiquant si le premier UE est accepté, ou non, en tant que noeud coordinateur pour le second UE.
PCT/SE2022/050887 2022-10-04 2022-10-04 Procédé mis en oeuvre par un premier équipement utilisateur pour coordonner des ressources pour une communication de liaison latérale entre des équipements utilisateur WO2024076265A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/SE2022/050887 WO2024076265A1 (fr) 2022-10-04 2022-10-04 Procédé mis en oeuvre par un premier équipement utilisateur pour coordonner des ressources pour une communication de liaison latérale entre des équipements utilisateur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2022/050887 WO2024076265A1 (fr) 2022-10-04 2022-10-04 Procédé mis en oeuvre par un premier équipement utilisateur pour coordonner des ressources pour une communication de liaison latérale entre des équipements utilisateur

Publications (1)

Publication Number Publication Date
WO2024076265A1 true WO2024076265A1 (fr) 2024-04-11

Family

ID=90608469

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2022/050887 WO2024076265A1 (fr) 2022-10-04 2022-10-04 Procédé mis en oeuvre par un premier équipement utilisateur pour coordonner des ressources pour une communication de liaison latérale entre des équipements utilisateur

Country Status (1)

Country Link
WO (1) WO2024076265A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210266923A1 (en) * 2020-02-23 2021-08-26 Qualcomm Incorporated Generating Resource Allocation Coordination Information for Sidelink Communications
US20220065979A1 (en) * 2020-09-02 2022-03-03 Qualcomm Incorporated Assistance information for sidelink-assisted positioning
US20220303956A1 (en) * 2021-03-18 2022-09-22 Hyundai Motor Company Method and device for transmitting and receiving inter-ue coordination information in sidelink communication

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210266923A1 (en) * 2020-02-23 2021-08-26 Qualcomm Incorporated Generating Resource Allocation Coordination Information for Sidelink Communications
US20220065979A1 (en) * 2020-09-02 2022-03-03 Qualcomm Incorporated Assistance information for sidelink-assisted positioning
US20220303956A1 (en) * 2021-03-18 2022-09-22 Hyundai Motor Company Method and device for transmitting and receiving inter-ue coordination information in sidelink communication

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "On Inter-UE Coordination for Mode2 Enhancements", 3GPP DRAFT; R1-2105335, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210510 - 20210527, 12 May 2021 (2021-05-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052011379 *

Similar Documents

Publication Publication Date Title
US20210368533A1 (en) Protection for Mode-3 V2X UEs in the ITS Band
AU2017305148B2 (en) Dynamic resource allocation in a wireless network with wireless backhaul
US20220022279A1 (en) Low power operation method of terminal supporting direct communication, and apparatus for the same
US11425552B2 (en) Method of connection control for direct communication between terminals, and apparatus therefor
JP7097455B2 (ja) デバイスツーデバイス通信のための技法
WO2019169359A1 (fr) Système et procédé de radiorecherche hiérarchique, sélection de cellule et resélection de cellule
KR20230005162A (ko) Nr 사이드링크 지원 정보 메시지
CN116250330B (zh) 协调的ue间资源分配
JP2021500809A (ja) ビークルツーエブリシング（ｖ２ｘ）通信のビームベーススケジューリングのための技法および装置
CN115039502A (zh) 用于无线通信***的中继设备
US20230164582A1 (en) Beam Sweep Order Change due to RACH
US20240244682A1 (en) Establishing a signaling connection in a wireless network
EP3834541B1 (fr) Procédé d'attribution de ressources dans une communication de dispositif à dispositif
US20220322487A1 (en) Low-latency communication with discontinuous transmission
RU2737923C1 (ru) Обеспечение связи устройства беспроводной связи в сети беспроводной связи
WO2022056810A1 (fr) Sélection de cellule d'ancrage à double connectivité multi-rat
KR20200138402A (ko) 채널 통신을 페이징하기 위한 빔 검색 파일럿
WO2021163997A1 (fr) Techniques d'activation de cellule secondaire
WO2024076265A1 (fr) Procédé mis en oeuvre par un premier équipement utilisateur pour coordonner des ressources pour une communication de liaison latérale entre des équipements utilisateur
KR20210018049A (ko) 단말 간 직접 통신을 위한 연결 제어 방법 및 이를 위한 장치
WO2021189361A1 (fr) Manière économe en énergie de faire fonctionner un équipement utilisateur (ue) dans une connectivité double de technologie d'accès radio multiple
WO2023075665A1 (fr) Premier équipement utilisateur, nœud de réseau et procédés pour permettre la liaison latérale dans un réseau de communication sans fil
WO2023007020A1 (fr) Technique de sélection de cellules
EP4367917A1 (fr) N?ud de réseau radio, équipement utilisateur et procédés associés
CN117643169A (zh) 用于ue到ue中继资源管理的方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22961554

Country of ref document: EP

Kind code of ref document: A1