IP Library Granted Patent US 12,634,771
Granted Patent B2
US 12,634,771 · App. 18/100,101 · Granted May 19, 2026

Responding to second base station addition request for vehicle-to-everything (V2X)

Inventors: Kyungmin Park (Vienna, VA); Esmael Hejazi Dinan (McLean, VA)
Assignee: Ofinno, LLC
H04W36/0044H04W36/0016H04W36/0072H04W36/362H04W4/40H04W4/46H04W4/70H04W28/0268H04W36/00H04W36/0033H04W36/08H04W76/14H04W84/005
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,634,771
App. No.
18/100,101
Granted
May 19, 2026
Kind
B2
Abstract

A first base station receives a second base station addition request indicating, for each packet flow of packet flows of a wireless device, whether each packet flow is for at least one vehicle-to-everything (V2X) service, and a quality-of-service indicator of each packet flow. The first base station sends an indication of an acceptance or rejection of each packet flow of the packet flows.

Claims (67)

1 . A method comprising:

receiving, by a first base station, a handover request message indicating, for each packet flow of packet flows of a wireless device:

whether each packet flow is for at least one vehicle-to-everything (V2X) service; and

a quality-of-service indicator of each packet flow; and

sending, by the first base station, an indication of an acceptance or rejection of each packet flow of the packet flows.

2 . The method of claim 1 , wherein the indication of the acceptance or rejection is based on the handover request message indicating whether each packet flow is for the at least one V2X service.

3 . The method of claim 1 , wherein the handover request message comprises a secondary base station addition request for a dual connectivity of the wireless device.

4 . The method of claim 3 , wherein the wireless device receives a configuration message for the dual connectivity from a second base station; and wherein:

the indication is sent by the first base station to the second base station; and

the configuration message is based on the indication.

5 . The method of claim 1 , wherein the handover request message indicates whether each packet flow is for at least one of:

a vehicle-to-vehicle (V2V) service;

a vehicle-to-network (V2N) service;

a vehicle-to-pedestrian (V2P) service;

a vehicle-to-infrastructure (V2I) service;

a multimedia broadcast multicast service single frequency network (MBSFN) service;

a single cell point to multipoint (SC-PTM) service; or

a sidelink-based V2X service.

6 . The method of claim 1 , wherein the handover request message indicates at least one of:

a temporary mobile group identity (TMGI) associated with each packet flow; or

a periodic resource scheduling requirement for each packet flow.

7 . The method of claim 1 , wherein:

a second base station receives, from a core network entity or a third base station, a message indicating whether each packet flow is for the at least one V2X service; and

the receiving the handover request message comprises receiving a second base station addition request by the first base station from the second base station.

8 . A first base station comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the first base station to:

receive a handover request message indicating, for each packet flow of packet flows of a wireless device:

whether each packet flow is for at least one vehicle-to-everything (V2X) service; and

a quality-of-service indicator of each packet flow; and

send an indication of an acceptance or rejection of each packet flow of the packet flows.

9 . The first base station of claim 8 , wherein the handover request message comprises a secondary base station addition request for a dual connectivity of the wireless device.

10 . The first base station of claim 9 , wherein the wireless device receives, from a second base station, a configuration message for the dual connectivity; and wherein:

the indication is sent by the first base station to the second base station; and

the configuration message is based on the indication.

11 . The first base station of claim 8 , wherein the indication comprises configuration parameters associated with the at least one V2X service for the wireless device.

12 . The first base station of claim 8 , wherein the instructions, when executed, further cause the first base station to determine whether to accept the handover request message for the wireless device based on whether each packet flow is for the at least one V2X service.

13 . The first base station of claim 8 , wherein the handover request message indicates whether each packet flow is for at least one of:

a vehicle-to-vehicle (V2V) service;

a vehicle-to-network (V2N) service;

a vehicle-to-pedestrian (V2P) service;

a vehicle-to-infrastructure (V2I) service;

a multimedia broadcast multicast service single frequency network (MBSFN) service;

a single cell point to multipoint (SC-PTM) service; or

a sidelink-based V2X service.

14 . The first base station of claim 8 , wherein the handover request message indicates at least one of:

a temporary mobile group identity (TMGI) associated with each packet flow; or

a periodic resource scheduling requirement for each packet flow.

15 . A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a first base station, cause the first base station to:

receive a handover request message indicating, for each packet flow of packet flows of a wireless device:

whether each packet flow is for at least one vehicle-to-everything (V2X) service; and

a quality-of-service indicator of each packet flow; and

send an indication of an acceptance or rejection of each packet flow of the packet flows.

16 . The non-transitory computer-readable medium of claim 15 , wherein the indication indicates the acceptance or rejection of each packet flow, of the packet flows, for the at least one V2X service.

17 . The non-transitory computer-readable medium of claim 15 , wherein the indication comprises configuration parameters associated with the at least one V2X service for the wireless device.

18 . The non-transitory computer-readable medium of claim 15 , wherein the handover request message indicates whether each packet flow is for at least one of:

a vehicle-to-vehicle (V2V) service;

a vehicle-to-network (V2N) service;

a vehicle-to-pedestrian (V2P) service;

a vehicle-to-infrastructure (V2I) service;

a multimedia broadcast multicast service single frequency network (MBSFN) service;

a single cell point to multipoint (SC-PTM) service; or

a sidelink-based V2X service.

19 . The non-transitory computer-readable medium of claim 15 , wherein the handover request message indicates at least one of:

a temporary mobile group identity (TMGI) associated with each packet flow; or

a periodic resource scheduling requirement for each packet flow.

20 . The non-transitory computer-readable medium of claim 15 , wherein the instructions further cause the first base station to transmit, to the wireless device, packets via each packet flow.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 25, 2023
From: PARK, KYUNGMIN; DINAN, ESMAEL HEJAZI
To: OFINNO, LLC
Reel/Frame 062484/0996 →
Continuity (8)
Continuation 17092374 · Nov 9, 2020
Continuation 16551009 · Aug 26, 2019
Continuation 15796286 · Oct 27, 2017
Provisional Application 62413820 · Oct 27, 2016
Provisional Application 62413835 · Oct 27, 2016
Provisional Application 62413824 · Oct 27, 2016
Provisional Application 62413832 · Oct 27, 2016
Related Publication 20230379768A1 · Nov 23, 2023
References Cited (47)
US 9363781B2 · Won et al. · 2016 [cited by applicant]
US 11564133B2 · Park · 2023 [cited by examiner]
US 20140335882A1 · Lee · 2014 [cited by examiner]
US 20150365963A1 · Won · 2015 [cited by examiner]
US 20170099624A1 · Baghel et al. · 2017 [cited by applicant]
US 20170280325A1 · Xu · 2017 [cited by examiner]
US 20180176891A1 · Kim et al. · 2018 [cited by applicant]
US 20180262887A1 · Futaki · 2018 [cited by examiner]
US 20190028854A1 · Hua et al. · 2019 [cited by applicant]
US 20190320476A1 · Wang et al. · 2019 [cited by applicant]
3GPP TS 36.300 V14.0.0 (Sep. 2016); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Univer… [cited by applicant]
3GPP TS 36.423 V14.0.0 (Sep. 2016); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 appli… [cited by applicant]
R2-166176; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Oct. 10-14, 2016; Source: CATT; Title: Consideration on P2X; Agenda Item: 8.13.3; Document for: Discussion and Decision. [cited by applicant]
R2-166594; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Oct. 10-14, 2016; Agenda Item: 8.13.3; Source: Coolpad; Title: Discussion on power saving for P-UE; Document for: Discussion and Decision. [cited by applicant]
R2-166173; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Oct. 10-14, 2016; Source: CATT; Title: Impact of Multiple TMGI; Agenda Item: 8.13.1; Document for: Discussion and Decision. [cited by applicant]
R2-166174; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Oct. 10-14, 2016; Title: [Draft] Ls Response on Multiple TMGIs for support of small and variable MBMS areas; Response to: LS on Multiple TMGIs for support of small … [cited by applicant]
R2-166175; 3GPP TSG RAN WG2 Meeting #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Source: CATT; Title: Discussion on V2X SPS; Agenda Item: 8.13.2; Document for: Discussion and Decision. [cited by applicant]
R2-166189; 3GPP TSG-RAN2 Meeting #95bis; Kaohsiung, Oct. 10-14, 2016; Agenda Item: 8.13.2; Source: OPPO; Title: Discussion on Details of V2X SPS Enhancements; Document for: Discussion and Decision. [cited by applicant]
R2-166190; 3GPP TSG-RAN2 Meeting #95bis; Kaohsiung, Oct. 10-14, 2016; Agenda Item: 8.13.3; Source: OPPO; Title: Discussion on V2P; Document for: Discussion and Decision. [cited by applicant]
R2-166261; 3GPP TSG RAN WG2 Meeting #95bis; Kaohsiung, Oct. 10-14, 2016; Agenda item: 8.13.3; Source: Intel Corporation; Title: Resource pool management; Document for: Discussion and decision. [cited by applicant]
R2-166297; 3GPP TSG RAN WG2 Meeting #95-bis; Kaohsiung, Oct. 10-14, 2016; Agenda Item: 8.13.1; Source: Huawei, HiSilicon; Title: Inter-PLMN operation for UU-based V2X; Document for: Discussion and Decision. [cited by applicant]
R2-166298, 3GPP TSG RAN WG2 Meeting #95-bis; Kaohsiung, Oct. 10-14, 2016; Agenda Item: 8.13.3; Source: Huawei, HiSilicon; Title: Discussion on P2X Sidelink Communication; Document for: Discussion and Decision. [cited by applicant]
R2-166299; 3GPP TSG RAN WG2 Meeting #95-bis; Kaohsiung, Oct. 10-14, 2016; Agenda Item: 8.13.2; Source: Huawei, HiSilicon; Title: Enhancements of Uplink SPS for UU-based V2X. [cited by applicant]
R2-166300; 3GPP TSG RAN WG2 Meeting #95-bis; Kaohsiung, Oct. 10-14, 2016; Agenda Item: 8.13.2; Source: Huawei, HiSilicon; Title: Further Discussion of SPS over Sidelink; Document for: Discussion and Decision. [cited by applicant]
R2-166431; 3GPP TSG RAN WG2 Meeting #95bis; Kaohsiung, Oct. 10-14, 2016; Source: ITL; Title: Reporting issues on SL SPS; Agenda Item: 8.13.2; Document for: Discussion/Decision. [cited by applicant]
R2-166465; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Agenda: 8.13.1; Source: MediaTek; Title: SC-PTM Enhancements for LTE V2X; Document for: Discussion and Decision. [cited by applicant]
R2-166466; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Agenda: 8.13.1; Source: MediaTek; Title: On suitability of UU transport and PC5 transport for V2X Solutions; Document for: Discussion and … [cited by applicant]
R2-166471; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Oct. 10-14, 2016; Source: Potevio; Title: Discussion on Sidelink SPS configuration and UE assistant information; Agenda Item: 8.13.2; Document for: Discussion and D… [cited by applicant]
R2-166489; 3GPP TSG-RAN WG2 Meeting#95b; Kaohsiung, Oct. 10-14, 2016; Agenda item: 8.13.3; Source: Fujitsu; Title: Discussion on power saving for V2P communications; Document for: Discussion and Decision. [cited by applicant]
R2-166609; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Oct. 10-14, 2016; Title: Discussion on V2P aspects; Source: ZTE; Agenda item: 8.13.3; Document for: Discussion and Approval. [cited by applicant]
R2-166616; 3GPP TSG-RAN WG2 #95bis; Kaohsiung, Oct. 10-14, 2016; Agenda Item: 8.13.2; Source: ZTE; Title: Discussion on SPS related issues; Document for: Discussion. [cited by applicant]
R2-166721; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsuing, Oct. 10-14, 2016; Agenda item: 8.13.2; Source: Qualcomm Incorporated; Title: Details of DCI and SPS Configuration; Document for: Discussion/Decision. [cited by applicant]
R2-166733; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsuing, Oct. 10-14, 2016; Agenda item: 8.13.3; Source: Qualcomm Incorporated; Title: V2P Services over PC5; Document for: Discussion/Decision. [cited by applicant]
R2-166750; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Agenda item: 8.13.1; Source: Nokia, Alcatel-Lucent Shanghai Bell; Title: MBMS Session Reception for V2X; WID/SID: LTE-V2X-Core; Document f… [cited by applicant]
R2-166752; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Agenda item: 8.13.3; Source: Nokia, Alcatel-Lucent Shanghai Bell; Title: Efficient V2P/P2V activation; WID/SID: LTE_V2X-Core—Release 14; D… [cited by applicant]
R2-166861; 3GPP TSG-RAN WG2 #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Agenda item: 8.13.3; Source: Kyocera; Title: Consideration of the P2V transmission scheme; Document for: Discussion and decision. [cited by applicant]
R2-166872; 3GPP TSG-RAN WG2 #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Agenda Item: 8.13.2; Source: Interdigital; Title: Details on SPS for V2X; Document for: Discussion, Decision. [cited by applicant]
R2-166961; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; CR-Form-v11.1; Change Request; 36.321 CR xxxxx; rev-; Current version: 13.2.0; Title: Introducing Sidelink SPS in MAC. [cited by applicant]
R2-166962; 3GPP TSG-RAN WG2 Meeting #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; CR-Form-v11.1; Change Request; 36.331 CR xxxxx; rev—Current version: 13.2.0; Title: Introducing Sidelink SPS in RRC. [cited by applicant]
R2-166964; 3GPP TSG-RAN WG2 #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Agenda Item: 8.13.2; Source: Ericsson; Title: Configuration of UE Assistance Information; Document for: Discussion, Decision. [cited by applicant]
R2-166967; 3GPP TSG-RAN WG2 #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Agenda Item: 8.13.3; Source: Ericsson; Title: Discussion on Sidelink Operations for Pedestrian; Document for: Discussion, Decision. [cited by applicant]
R2-166975; 3GPP TSG-RAN WG2 #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Agenda Item: 8.13.2; Source: Ericsson (Rapporteur); Title: Report from [95#32][LTE/V2V] SPS; Document for: Discussion, Decision. [cited by applicant]
R2-166976; 3GPP TSG-RAN WG2 #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Agenda Item: 8.13.2; Source: Ericsson; Title: Sidelink SPS Configuration; Document for: Discussion, Decision. [cited by applicant]
R2-166977; 3GPP TSG-RAN WG2 #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Agenda Item: 8.13.2; Source: Ericsson; Title: SPS Protocol for UU; Document for: Discussion, Decision. [cited by applicant]
R2-166980; 3GPP TSG-RAN WG2 #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Title: [Draft] LS Reply on Multiple TMGIs for support of small and variable MBMS areas; Response to: R3-162067; Release: Rel-14; Work Item: TE_V2X… [cited by applicant]
R2-166982; 3GPP TSG-RAN WG2 #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Agenda Item: 8.13.1; Source: Ericsson; Title: V2X Message Broadcasting; Document for: Discussion, Decision. [cited by applicant]
R2-166983; 3GPP TSG-RAN WG2 #95bis; Kaohsiung, Taiwan, Oct. 10-14, 2016; Agenda Item: 8.13.1; Source: Ericsson; Title: On MBMS Latency; Document for: Discussion, Decision. [cited by applicant]