US 12,238,747 B2
Sidelink resource allocation for enhanced mobility
Marco Belleschi, Solna (SE); Massimo Condoluci, Solna (SE); Shehzad Ali Ashraf, Aachen (DE); and Ricardo Blasco Serrano, Espoo (FI)
Assigned to TELEFONAKTIEBOLAGET LM ERICSSON (PUBL), Stockholm (SE)
Appl. No. 17/278,707
Filed by Telefonaktiebolaget LM Ericsson (PUBL), Stockholm (SE)
PCT Filed Sep. 20, 2019, PCT No. PCT/EP2019/075283
§ 371(c)(1), (2) Date Mar. 23, 2021,
PCT Pub. No. WO2020/064527, PCT Pub. Date Apr. 2, 2020.
Claims priority of provisional application 62/737,575, filed on Sep. 27, 2018.
Prior Publication US 2022/0039082 A1, Feb. 3, 2022
Int. Cl. H04W 72/04 (2023.01); H04W 4/40 (2018.01); H04W 72/02 (2009.01); H04W 72/51 (2023.01); H04W 76/36 (2018.01); H04W 92/18 (2009.01)
CPC H04W 72/51 (2023.01) [H04W 4/40 (2018.02); H04W 72/02 (2013.01); H04W 76/36 (2018.02); H04W 92/18 (2013.01)] 18 Claims
OG exemplary drawing
 
1. A method performed by a wireless device, the method comprising:
in response to a triggering event, sending, to a network node, a request for a sidelink (SL) resource pool configuration for a V2X application associated with the wireless device, wherein the request includes one or more SL resource pool configurations, wherein the wireless device is one of a plurality of wireless devices involved in the V2X application, and wherein the wireless device is configured to send the request for the one or more SL resource pool configurations on behalf of the plurality of wireless devices involved in the V2X application; and
receiving, in response to the request, a SL resource pool configuration from the network node, and
wherein the triggering event comprises at least one of:
determining that the wireless device is configured with a previous SL resource pool configuration that no longer guarantees one or more quality of service requirements for the V2X application, and
determining that the wireless device has transitioned from an out-of-coverage scenario to an in-coverage scenario and a previous SL resource pool configuration configured for the out-of-coverage scenario is no longer valid.