IP Library › Granted Patent US 12,224,873
Granted Patent B2
US 12,224,873 · App. 18/488,352 · Granted Feb 11, 2025

Capability signaling in wireless communications

Inventors: Roozbeh Atarius (Herndon, VA); Esmael Hejazi Dinan (McLean, VA)
Assignee: Comcast Cable Communications, LLC
H04L12/1407H04L47/20H04L65/1016H04L65/1045H04L65/1063H04L65/1104H04L65/80H04M15/00H04M15/66H04M15/8016H04M15/8214H04W28/0257H04W28/12H04W84/005H04L47/2458H04L67/125
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,224,873
App. No.
18/488,352
Granted
Feb 11, 2025
Kind
B2
Abstract

Wireless communications for capability signaling are described. A device may receive one or more parameters associated with capabilities of a wireless device. The one or more parameters may be used to determine one or more policy control provisions. The device may determine one or more policy control provisions associated with a quality of service of wireless communication for the wireless device.

Claims (111)

1. A method comprising:

receiving, by a computing device via an application function (AF), a first message comprising:

one or more priority parameters indicating one or more priorities associated with one or more vehicle-to-everything (V2X) capabilities of a wireless device; and

one or more quality of service (QOS) parameters indicating a QoS of a V2X communication associated with a V2X application for the wireless device;

determining, based on the one or more priority parameters and the QoS, one or more policy and charging control (PCC) provisions for adjusting the V2X communication; and

sending, based on the one or more PCC provisions for adjusting the V2X communication, a second message.

2. The method of claim 1 , further comprising:

receiving, from the wireless device, one or more capability parameters indicating the one or more V2X capabilities of the wireless device.

3. The method of claim 1 , wherein the determining the one or more PCC provisions for adjusting the V2X communication comprises:

determining, based on the one or more V2X capabilities of the wireless device and by a policy control function associated with the computing device, the one or more PCC provisions for adjusting the V2X communication.

4. The method of claim 1 , wherein the one or more priorities comprises one or more priorities of a V2X service associated with QoS requirements.

5. The method of claim 1 , wherein the sending the second message comprises:

sending, to at least one of the wireless device or the AF, at least one parameter indicating the one or more PCC provisions for adjusting the V2X communication.

6. The method of claim 1 , wherein the one or more V2X capabilities of the wireless device indicates a wireless device type comprising at least one of:

a vehicle associated with a first V2X capability; or

a communication device associated with a second V2X capability.

7. The method of claim 1 , further comprising receiving a request for a modification of a priority of the V2X application.

8. A method comprising:

sending, by a computing device via an application function (AF), a first message comprising:

one or more priority parameters indicating one or more priorities associated with one or more vehicle-to-everything (V2X) capabilities of a wireless device; and

one or more quality of service (QOS) parameters indicating a QoS of a V2X communication associated with a V2X application for the wireless device; and

receiving, based on one or more policy and charging control (PCC) provisions for adjusting the V2X communication, a second message, wherein the one or more PCC provisions for adjusting the V2X communication is based on the one or more priority parameters and the QoS.

9. The method of claim 8 , further comprising:

receiving, from the wireless device, one or more capability parameters indicating the one or more V2X capabilities of the wireless device.

10. The method of claim 8 , wherein the one or more PCC provisions for adjusting the V2X communication is further based on the one or more V2X capabilities of the wireless device.

11. The method of claim 8 , wherein the one or more priorities comprises one or more priorities of a V2X service associated with QoS requirements.

12. The method of claim 8 , wherein the receiving the second message comprises:

receiving at least one parameter indicating the one or more PCC provisions for adjusting the V2X communication.

13. The method of claim 8 , wherein the one or more V2X capabilities of the wireless device indicates a wireless device type comprising at least one of:

a vehicle associated with a first V2X capability; or

a communication device associated with a second V2X capability.

14. The method of claim 8 , further comprising sending a request for a modification of a priority of the V2X application.

15. A computing device comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, configure the computing device to:

receive, via an application function (AF), a first message comprising:

one or more priority parameters indicating one or more priorities associated with one or more vehicle-to-everything (V2X) capabilities of a wireless device; and

one or more quality of service (QOS) parameters indicating a QoS of a V2X communication associated with a V2X application for the wireless device;

determine, based on the one or more priority parameters and the QoS, one or more policy and charging control (PCC) provisions for adjusting the V2X communication; and

send, based on the one or more PCC provisions for adjusting the V2X communication, a second message.

16. The computing device of claim 15 , wherein the instructions, when executed by the one or more processors, configure the computing device to:

receive, from the wireless device, one or more capability parameters indicating the one or more V2X capabilities of the wireless device.

17. The computing device of claim 15 , wherein the instructions, when executed by the one or more processors, configure the computing device to determine the one or more PCC provisions for adjusting the V2X communication by:

determining, based on the one or more V2X capabilities of the wireless device and by a policy control function associated with the computing device, the one or more PCC provisions for adjusting the V2X communication.

18. The computing device of claim 15 , wherein the one or more priorities comprises one or more priorities of a V2X service associated with QoS requirements.

19. The computing device of claim 15 , wherein the instructions, when executed by the one or more processors, configure the computing device to send the second message by:

sending, to at least one of the wireless device or the AF, at least one parameter indicating the one or more PCC provisions for adjusting the V2X communication.

20. The computing device of claim 15 , wherein the one or more V2X capabilities of the wireless device indicates a wireless device type comprising at least one of:

a vehicle associated with a first V2X capability; or

a communication device associated with a second V2X capability.

21. The computing device of claim 15 , wherein the instructions, when executed by the one or more processors, configure the computing device to receive a request for a modification of a priority of the V2X application.

22. A computing device comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, configure the computing device to:

send, via an application function (AF), a first message comprising:

one or more priority parameters indicating one or more priorities associated with one or more vehicle-to-everything (V2X) capabilities of a wireless device; and

one or more quality of service (QOS) parameters indicating a QoS of a V2X communication associated with a V2X application for the wireless device; and

receive, based on one or more policy and charging control (PCC) provisions for adjusting the V2X communication, a second message, wherein the one or more PCC provisions for adjusting the V2X communication is based on the one or more priority parameters and the QoS.

23. The computing device of claim 22 , wherein the instructions, when executed by the one or more processors, configure the computing device to:

receive, from the wireless device, one or more capability parameters indicating the one or more V2X capabilities of the wireless device.

24. The computing device of claim 22 , wherein the one or more PCC provisions for adjusting the V2X communication is further based on the one or more V2X capabilities of the wireless device.

25. The computing device of claim 22 , wherein the one or more priorities comprises one or more priorities of a V2X service associated with QoS requirements.

26. The computing device of claim 22 , wherein the instructions, when executed by the one or more processors, configure the computing device to receive the second message by:

receiving at least one parameter indicating the one or more PCC provisions for adjusting the V2X communication.

27. The computing device of claim 22 , wherein the one or more V2X capabilities of the wireless device indicates a wireless device type comprising at least one of:

a vehicle associated with a first V2X capability; or

a communication device associated with a second V2X capability.

28. The computing device of claim 22 , wherein the instructions, when executed by the one or more processors, configure the computing device to send a request for a modification of a priority of the V2X application.

29. A non-transitory computer-readable medium storing instructions that, when executed, configure a computing device to:

receive, via an application function (AF), a first message comprising:

one or more priority parameters indicating one or more priorities associated with one or more vehicle-to-everything (V2X) capabilities of a wireless device; and

one or more quality of service (QOS) parameters indicating a QoS of a V2X communication associated with a V2X application for the wireless device;

determine, based on the one or more priority parameters and the QoS, one or more policy and charging control (PCC) provisions for adjusting the V2X communication; and

send, based on the one or more PCC provisions for adjusting the V2X communication, a second message.

30. The non-transitory computer-readable medium of claim 29 , wherein the instructions, when executed, configure the computing device to:

receive, from the wireless device, one or more capability parameters indicating the one or more V2X capabilities of the wireless device.

31. The non-transitory computer-readable medium of claim 29 , wherein the instructions, when executed, configure the computing device to determine the one or more PCC provisions for adjusting the V2X communication by:

determining, based on the one or more V2X capabilities of the wireless device and by a policy control function associated with the computing device, the one or more PCC provisions for adjusting the V2X communication.

32. The non-transitory computer-readable medium of claim 29 , wherein the one or more priorities comprises one or more priorities of a V2X service associated with QoS requirements.

33. A non-transitory computer-readable medium storing instructions that, when executed, configure a computing device to:

send, via an application function (AF), a first message comprising:

one or more priority parameters indicating one or more priorities associated with one or more vehicle-to-everything (V2X) capabilities of a wireless device; and

one or more quality of service (QOS) parameters indicating a QoS of a V2X communication associated with a V2X application for the wireless device; and

receive, based on one or more policy and charging control (PCC) provisions for adjusting the V2X communication, a second message, wherein the one or more PCC provisions for adjusting the V2X communication is based on the one or more priority parameters and the QoS.

34. The non-transitory computer-readable medium of claim 33 , wherein the instructions, when executed, configure the computing device to:

receive, from the wireless device, one or more capability parameters indicating the one or more V2X capabilities of the wireless device.

35. The non-transitory computer-readable medium of claim 33 , wherein the one or more PCC provisions for adjusting the V2X communication is further based on the one or more V2X capabilities of the wireless device.

36. The non-transitory computer-readable medium of claim 33 , wherein the one or more priorities comprises one or more priorities of a V2X service associated with QoS requirements.

37. A system comprising:

a first computing device; and

a second computing device,

wherein the first computing device is configured to:

receive, via an application function (AF), a first message comprising:

one or more priority parameters indicating one or more priorities associated with one or more vehicle-to-everything (V2X) capabilities of a wireless device; and

one or more quality of service (QOS) parameters indicating a QoS of a V2X communication associated with a V2X application for the wireless device;

determine, based on the one or more priority parameters and the QoS, one or more policy and charging control (PCC) provisions for adjusting the V2X communication; and

send, based on the one or more PCC provisions for adjusting the V2X communication, a second message.

38. The system of claim 37 , wherein the first computing device is configured to:

receive, from the wireless device, one or more capability parameters indicating the one or more V2X capabilities of the wireless device.

39. The system of claim 37 , wherein the first computing device is configured to determine the one or more PCC provisions for adjusting the V2X communication by:

determining, based on the one or more V2X capabilities of the wireless device and by a policy control function associated with the computing device, the one or more PCC provisions for adjusting the V2X communication.

40. The system of claim 37 , wherein the one or more priorities comprises one or more priorities of a V2X service associated with QoS requirements.

41. The system of claim 37 , wherein the first computing device is configured to send the second message by:

sending, to at least one of the wireless device or the AF, at least one parameter indicating the one or more PCC provisions for adjusting the V2X communication.

42. The system of claim 37 , wherein the one or more V2X capabilities of the wireless device indicates a wireless device type comprising at least one of:

a vehicle associated with a first V2X capability; or

a communication device associated with a second V2X capability.

43. The system of claim 37 , wherein the first computing device is configured to receive a request for a modification of a priority of the V2X application.

44. The system of claim 37 , wherein the second computing device is configured to:

send, via the AF, the first message; and

receive, based on the one or more PCC provisions for adjusting the V2X communication, the second message.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 16, 2024
From: ATARIUS, ROOZBEH; DINAN, ESMAEL HEJAZI
To: OFINNO TECHNOLOGIES, LLC
Reel/Frame 069177/0194 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 16, 2024
From: ATARIUS, ROOZBEH; DINAN, ESMAEL HEJAZI
To: OFINNO TECHNOLOGIES, LLC
Reel/Frame 068909/0650 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 16, 2024
From: ATARIUS, ROOZBEH; DINAN, ESMAEL HEJAZI
To: OFINNO TECHNOLOGIES, LLC
Reel/Frame 068909/0688 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 16, 2024
From: OFINNO TECHNOLOGIES, LLC
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068909/0739 →
Continuity (5)
Continuation 17216097 · Mar 29, 2021
Continuation 15472801 · Mar 29, 2017
Provisional Application 62339845 · May 21, 2016
Provisional Application 62317520 · Apr 2, 2016
Related Publication 20240154827A1 · May 9, 2024
References Cited (171)
US 10531418B2 · Chun · 2020 [cited by examiner]
US 10645549B2 · Pinheiro · 2020 [cited by examiner]
US 10805395B2 · Cavalcanti · 2020 [cited by examiner]
US 10827502B2 · Basu Mallick · 2020 [cited by examiner]
US 20100098012A1 · Bala et al. · 2010 [cited by applicant]
US 20110105107A1 · Kwon et al. · 2011 [cited by applicant]
US 20110249578A1 · Nayeb Nazar et al. · 2011 [cited by applicant]
US 20130028229A1 · Suh et al. · 2013 [cited by applicant]
US 20130058233A1 · Kim · 2013 [cited by applicant]
US 20130121297A1 · Kim et al. · 2013 [cited by applicant]
US 20130301509A1 · Purnadi et al. · 2013 [cited by applicant]
US 20140016593A1 · Park et al. · 2014 [cited by applicant]
US 20140241319A1 · Lee et al. · 2014 [cited by applicant]
US 20140344472A1 · Lovsen et al. · 2014 [cited by applicant]
US 20150043429A1 · Kim et al. · 2015 [cited by applicant]
US 20150181576A1 · Papasakellariou et al. · 2015 [cited by applicant]
US 20150365831A1 · Ko et al. · 2015 [cited by applicant]
US 20150365963A1 · Won et al. · 2015 [cited by applicant]
US 20160100353A1 · Gleixner · 2016 [cited by applicant]
US 20160204905A1 · Lee et al. · 2016 [cited by applicant]
US 20160227486A1 · Park · 2016 [cited by applicant]
US 20160227602A1 · Yi et al. · 2016 [cited by applicant]
US 20160295624A1 · Novlan et al. · 2016 [cited by applicant]
US 20170019887A1 · Jiang et al. · 2017 [cited by applicant]
US 20170201461A1 · Cheng · 2017 [cited by examiner]
US 20170245245A1 · Kim et al. · 2017 [cited by applicant]
US 20170325076A1 · Fujishiro et al. · 2017 [cited by applicant]
US 20170347270A1 · Iouchi et al. · 2017 [cited by applicant]
US 20170366679A1 · Mohamed et al. · 2017 [cited by applicant]
US 20170374665A1 · Lee et al. · 2017 [cited by applicant]
US 20180007680A1 · Lee et al. · 2018 [cited by applicant]
US 20180007693A1 · Lee et al. · 2018 [cited by applicant]
US 20180027461A1 · Jia et al. · 2018 [cited by applicant]
US 20180035276A1 · Kang et al. · 2018 [cited by applicant]
US 20180035340A1 · Fujishiro et al. · 2018 [cited by applicant]
US 20180049225A1 · Lee et al. · 2018 [cited by applicant]
US 20180124707A1 · Lee et al. · 2018 [cited by applicant]
US 20180159935A1 · Cavalcanti et al. · 2018 [cited by applicant]
US 20180192268A1 · Xu et al. · 2018 [cited by applicant]
US 20180206089A1 · Cavalcanti et al. · 2018 [cited by applicant]
US 20180255569A1 · Aiba et al. · 2018 [cited by applicant]
US 20190014563A1 · Lee et al. · 2019 [cited by applicant]
US 20190098698A1 · Fukuta · 2019 [cited by applicant]
US 20190182644A1 · Zheng et al. · 2019 [cited by applicant]
US 20190245657A1 · Lee et al. · 2019 [cited by applicant]
EP 2763338A1 · 2014 [cited by applicant]
3GPP TR 22.885 V1.0.0 (Sep. 2015), Technical Report, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on LTE Support for V2X Services (Release 14), 42 pages, Sep. 2015. [cited by examiner]
R2-168043; 3GPP TSG-RAN WG2 #96; Reno, USA, Nov. 14-18, 2016; Agenda item: 8.13.3; Source: Kyocera; Title: Consideration of the P2V transmission scheme. [cited by applicant]
R2-168045; 3GPP TSG RAN WG2 #96; Reno, USA, Nov. 14, to 18, 2016; Agenda Item: 8.13.1; Source: Samsung; Title: Supporting small and variable Service Area in non-overlapped local MBMS service area. [cited by applicant]
R2-168068; 3GPP TSG-RAN WG2 Meeting #96; Reno, Nevada, USA, Nov. 14-18, 2016; Agenda item: 8.13.3; Source: Samsung; Title: Resource configuration for P2V. [cited by applicant]
R2-168083; 3GPP TSG RAN WG2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Source: CATT; Title: Discussion on Impact of LCP procedure in V2X SPS resource usage; Agenda Item: 8.13.2. [cited by applicant]
R2-168084; 3GPP TSG RAN WG2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Source: CATT, ZTE, Potevio; Title: Discussion on V2X SPS. [cited by applicant]
R2-168085; 3GPP TSG-RAN WG2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Source: CATT; Title: Consideration on pool management and resource selection. [cited by applicant]
R2-168137; 3GPP TSG-RAN WG2 #96; Reno, USA, Nov. 14-18, 2016; Agenda Item: 8.13.2; Source: ZTE; Title: Discussion on SPS related issues. [cited by applicant]
R2-168139; 3GPP TSG-RAN WG2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Title: MBMS enhancement for Uu based V2X communication; Source: ZTE Corporation. [cited by applicant]
R2-168144; 3GPP TSG-RAN WG2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Title: Discussion on V2P aspects; Source: ZTE. [cited by applicant]
R2-168273; 3GPP TSG-RAN WG2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Agenda Item: 8.13.3; Source: Coolpad; Title: Discussion on power saving for PCS-based V2P. [cited by applicant]
R2-168409; 3GPP TSG-RAN WG2 #96; Reno, USA, Aug. 14-18, 2016; Agenda Item: 8.13.2; Source: LG Electronics Inc.; Title: SPS and UE assistant information for V2X. [cited by applicant]
R2-168410; 3GPP TSG-RAN WG2 #96; Reno, USA, Nov. 14-18, 2016; Agenda Item : 8.13.3; Source: LG Electronics Inc.; Title: Support for V2P service. [cited by applicant]
R2-168426; 3GPP TSG-RAN WG2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Agenda item: 8.13.3; Source: Nokia, Alcatel-Lucent Shanghai Bell; Title: Efficient V2P/P2V activation. [cited by applicant]
R2-168427; 3GPP TSG-RAN WG2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Agenda item: 8.13.2; Source: Nokia, Alcatel-Lucent Shanghai Bell; Title: Further discussion on SPS enhancements. [cited by applicant]
R2-168486; 3GPP TSG-RAN WG2 #96; Reno, Nevada, USA, Nov. 14-18, 2016; Agenda Item: 9.3.1.1.3; Source: Ericsson; Title: Consideration on mobility for URLLC and eV2x. [cited by applicant]
R2-168642; 3GPP TSG-RAN WG2 #96; Reno, Nevada, USA, Nov. 14-18, 2016; Agenda Item: 8.13.3; Source: Ericsson; Title: Discussion on Sidelink Operations for Pedestrian. [cited by applicant]
R2-168653; 3GPP TSG-RAN WG2 #96; Reno, Nevada, USA, Nov. 14-18, 2016; Agenda Item: 8.13.2; Source: Ericsson; Title: SPS Protocol for Uu. [cited by applicant]
R2-168701; 3GPP TSG-RAN WG2 #96; Reno, Nevada, USA, Nov. 14-18, 2016; Agenda Item: 8.13.2; Source: Ericsson, Interdigital, Qualcomm; Title: Configuration of UE Assistance Information. [cited by applicant]
R2-168702; 3GPP TSG-RAN WG2 #96; Reno, Nevada, USA, Nov. 14-18, 2016; Agenda Item: 8.13.2; Source: Ericsson, Interdigital, ITL; Title:vSidelink SPS Configuration. [cited by applicant]
R2-168789; 3GPP TSG RAN WG2 Meeting #96; Reno, NV, USA, Nov. 14-18, 2016; Title: Draft LS reply on Voice and Video enhancement for LTE. [cited by applicant]
International Search Report dated Jan. 11, 2018 in International Application No. PCT/US2017/045754. [cited by applicant]
R2-164105, 3GPP TSG-RAN WG2 Meeting #94, Nanjing, China, May 23-27, 2016, Source: Ericsson, Title: Sidelink Resource Allocation in V2X. [cited by applicant]
R2-163836, 3GPP TSG-RAN WG2 Meeting #94, Nanjing, China, May 23-27, 2016, Source: ZTE, Title: SPS enhancements for V2V over PC5. [cited by applicant]
3GPP TS 36.213 V11.3.0 (Jul. 2013), Technical Specification, 3rd Generation Partnership Project; Technical Specification LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); (Release 11). [cited by applicant]
3GPP TS 36.211 V14.0.0 (Sep. 2016); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels… [cited by applicant]
3GPP TS 36.212 V14.0.0 (Sep. 2016); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and … [cited by applicant]
3GPP TS 36.213 V14.0.0 (Sep. 2016); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer pr… [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.321 V14.0.0 (Sep. 2016); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Con… [cited by applicant]
3GPP TS 36.331 V14.0.0 (Sep. 2016); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Co… [cited by applicant]
R2-162236; 3GPP TSG-RAN WG2 Meeting #93bis; Apr. 11-15, 2016, Dubrovnik, Croatia; Agenda Item: 8.8.2; Source: Samsung; Title: Discussion on acknowledging SPS command. [cited by applicant]
R2-162264; 3GPP TSG-RAN WG2 Meeting #93b; Dubrovnik, Croatia, Apr. 11-15, 2016; Agenda item: 8.8.2; Source: Huawei, HiSilicon; Title: On UL grants skipping. [cited by applicant]
R2-162265; 3GPP TSG-RAN WG2 Meeting #93bis; Dubrovnik, Croatia, Apr. 11-15, 2016; Agenda Item 8.8.2; Source: Huawei, HiSilicon; Title: Implicit SPS release under UL grants skipping. [cited by applicant]
R2-162266; 3GPP TSG-RAN WG2 Meeting #93b; Dubrovnik, Croatia, Apr. 11-15, 2016; Agenda item: 8.8.2; Source: Huawei, HiSilicon; Title: Necessity of feedback for SPS activation and deactivation. [cited by applicant]
R2-162415; 3GPP TSG-RAN WG2 Meeting #93bis; Dubrovnik, Croatia, Apr. 11-15, 2016; Agenda Item: 8.8.1; Source: CMCC; Title: Remaining issues related to UL SPS. [cited by applicant]
R2-162466; 3GPP TSG-RAN2 Meeting #93bis; Dubrovnik, Croatia Apr. 11-15, 2016; Agenda item: 8.8.1; Source: Intel Corporation; Title: Further aspects of short SPS interval. [cited by applicant]
R2-162467; 3GPP TSG-RAN2 Meeting #93bis; Dubrovnik, Croatia Apr. 11-15, 2016; Agenda item:8.8.2;Source: Intel Corporation; Title: Further aspects of UL grant skipping. [cited by applicant]
R2-162468; 3GPP TSG-RAN2 Meeting #93bis; Dubrovnik, Croatia Apr. 11-15, 2016; Agenda item: 8.8.3; Source: Intel Corporation; Title: SPS activation, reactivation and deactivation feedback. [cited by applicant]
R2-162515; 3GPP TSG RAN WG2 Meeting #93bis; Dubrovnik, Croatia, Apr. 11-15, 2016; Source:CATT; Title: Feedback for SPS PDCCH command. [cited by applicant]
R2-162572; 3GPP TSG-RAN WG2 Meeting #93bis; Dubrovnik, Croatia, Apr. 11-15, 2016; Source: ZTE Corporation; Title: Discussion on the feedback of the SPS activation command. [cited by applicant]
R2-162601; 3GPP TSG-RAN2 Meeting #93bis; Republika Hrvatska, Dubrovnik, Apr. 11-15, 2016; Agenda Item:8.8.2—LTE Rel-14: WI: L2 latency reduction techniques; Source: ASUSTek; Title: Discussion on skipping UL grants. [cited by applicant]
R2-162781; 3GPP TSG-RAN WG2 #93bis; Dubrovnik, Croatia, Apr. 11-15, 2016; Agenda Item: 8.8.3; Source: Ericsson; Title: Acknowledgements for SPS commands. [cited by applicant]
R2-162901; 3GPP TSG-RAN WG2 Meeting #93bis; Dubrovnik, Croatia, Apr. 11-15, 2016; Agenda Item: 8.8.2 (LTE_LATRED_L2-Core); Source: LG Electronics Inc.; Title: Need for feedback of SPS command. [cited by applicant]
R2-162902; 3GPP TSG-RAN WG2 Meeting #93bis; Dubrovnik, Croatia, Apr. 11-15, 2016; Agenda Item: 8.8.2 (LTE_LATRED_L2-Core); Source: LG Electronics Inc.; Title: SPS feedback transmission. [cited by applicant]
R2-162909; 3GPP TSG-RAN2 Meeting #93bis; Dubrovnik, Croatia, Apr. 12-16, 2016; Agenda item: 8.8.2; Source: Qualcomm Incorporated; Title: Open issues for skipping UL grants. [cited by applicant]
R2-163385; 3GPP TSG-RAN2 Meeting #94; Nanjing, China, May 23-27, 2016; Agenda item: 8.8.1; Source: FiberHome; Title: UL SPS command feedback. [cited by applicant]
R2-163386; 3GPP TSG-RAN WG2 Meeting #94; Nanjing, China, May 23-27, 2016; Agenda Item: 8.8.2; Source: FiberHome; Title: discussion of retransmission for short SPS period. [cited by applicant]
R2-163475; 3GPP TSG RAN WG2 Meeting #94; Nanjing, China, May 23-27, 2016; Source: CATT; Title: Feedback for SPS activation and deactivation. [cited by applicant]
R2-163671; 3GPP TSG-RAN WG2 Meeting #94; May 23, to 27, 2016, Nanjing, China; Agenda Item: 8.8.1; Source: Samsung; Title: Feedback for SPS activation/deactivation. [cited by applicant]
R2-163698; 3GPP TSG-RAN WG2 Meeting #94; Nanjing, China, May 23-27, 2016; Agenda item: 8.8.1; Source: Nokia, Alcatel-Lucent Shanghai Bell; Title: Feedback for SPS activation/deactivation. [cited by applicant]
R2-163771; 3GPP TSG-RAN WG2 Meeting #94; Nanjing, China, May 23-27, 2016; Agenda Item: 8.8.2; Source: Fujitsu; Title: Considerations on the SPS resource efficiency. [cited by applicant]
R2-163781; 3GPP TSG-RAN WG2 #94; Nanjing, China, May 23-27, 2016; Agenda Item: 8.8.1; Source: Ericsson; Title: Acknowledgements for SPS commands. [cited by applicant]
R2-163916; 3GPP TSG-RAN WG2 Meeting #94; Nanjing, China, May 23-27, 2016; Agenda item: 8.8.1; Source: Huawei, HiSilicon; Title: Discussion on feedback for SPS activation and deactivation. [cited by applicant]
R2-163917; 3GPP TSG-RAN WG2 Meeting #94; Nanjing, China, May 23-27, 2016; Agenda Item: 8.8.2; Source: Huawei, HiSilicon; Title: Implicit SPS release under UL grants skipping. [cited by applicant]
R2-164207; 3GPP TSG-RAN WG2 Meeting #94; Nanjing, China, May 23-27, 2016; Agenda Item: 8.8.1 (LTE_LATRED_L2-Core); Source: LG Electronics Inc.; Title: SPS feedback for SPS release. [cited by applicant]
R2-164217; 3GPP TSG-RAN WG2 Meeting #94; Nanjing, China, May 23-27, 2016; Agenda Item: 8.8.1 (LTE_LATRED_L2-Core); Source: LG Electronics Inc.; Title: Need of feedback for SPS activation. [cited by applicant]
R2-165266; 3GPP TSG-RAN2 Meeting #95; Goteborg, Sweden, Aug. 22-26, 2016; Source: ZTE Corporation; Title: Discussion on the configurable feedback. [cited by applicant]
R2-165267; 3GPP TSG-RAN2 Meeting #95; Goteborg, Sweden, Aug. 22-26, 2016; Source: ZTE Corporation; Title: Discussion on the feedback transmission of SPS release. [cited by applicant]
R2-165354; 3GPP TSG-RAN WG2 #95; Gothenburg, Sweden, May 22-26, 2016; Agenda Item: 8.8; Source: Ericsson; Title: Remaining issues with SPS with skip padding and short periods. [cited by applicant]
R2-165663; 3GPP TSG-RAN WG2 Meeting #95; Gothenburg, Sweden, Aug. 22-26, 2016; Agenda Item: 8.8 (LTE_LATRED_L2-Core); Source: LG Electronics Inc.; Title: Remaining issues on SPS Confirmation MAC CE. [cited by applicant]
R2-165686; 3GPP TSG-RAN2 Meeting #95; Gothenburg, Sweden, Aug. 22-26, 2016; Agenda item: 8.8; Source: Qualcomm Incorporated; Title: Remaining Open Issues for Uplink Skipping. [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-167409; 3GPP TSG RAN WG2 Meeting #96; Reno, USA, Nov. 14-18, 2016; 3GPP TSG RAN WG1 Meeting #86bis; R1-1610929; Lisboa, Portugal, Oct. 10-14, 2016; Title: LS response on DFN offset. [cited by applicant]
R2-167481; 3GPP TSG-RAN2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Agenda Item: 8.13.2; Source: OPPO; Title: Discussion on Remain Issues of V2X Sps Enhancements. [cited by applicant]
R2-167482; 3GPP TSG-RAN2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Agenda Item: 8.13.3; Source: OPPO; Title: Discussion on V2P. [cited by applicant]
R2-167567; 3GPP TSG-RAN WG2 #96; Reno, USA, Nov. 14-18, 2016; Agenda item: 8.13.2; Source: Samsung, Intel; Title: Handling Sidelink SPS Configurations. [cited by applicant]
R2-167889; 3GPP TSG-RAN WG2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Agenda item: 8.13.2; Source: Qualcomm Incorporated; Title: SPS enhancement for V2X. [cited by applicant]
R2-167890; 3GPP TSG-RAN WG2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Agenda item: 8.13.3; Source: Qualcomm Incorporated; Title: Sensing based resource selection for V2P. [cited by applicant]
R2-167919; 3GPP TSG RAN WG2 #96; Reno, USA, Nov. 14, to 18, 2016; Agenda Item: 8.13.3; Source: Samsung; Title: Discussion about prioritization of P-UEs. [cited by applicant]
R2-167928; 3GPP TSG RAN WG2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Agenda Item: 8.13.3; Source: Huawei, HiSilicon; Title: Discussion on P2X Sidelink Communication. [cited by applicant]
R2-167930; 3GPP TSG RAN WG2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Agenda Item: 8.13.2; Source: Huawei, HiSilicon; Title: Discussions on Remaining Issues for SPS. [cited by applicant]
R2-167934; 3GPP TSG RAN WG2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Agenda Item: 8.13.1; Source: Huawei, HiSilicon; Title: Multi-PLMN operation for Uu-based V2X. [cited by applicant]
R2-167998; 3GPP TSG RAN WG2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Agenda item: 8.13.2; Source: Potevio; Title: Details of LCP for enhanced SPS configurations. [cited by applicant]
R2-167999; 3GPP TSG RAN WG2 Meeting #96; Reno, USA, Nov. 14-18, 2016; Source: Potevio; Title: Discussion on SPS configuration related issues. [cited by applicant]
3GPP TS 22.185 V0.2.0 (Feb. 2016), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for V2X services; Stage 1 (Release 14). [cited by applicant]
3GPP TS 23.203 V13.7.0 (Mar. 2016), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control architecture (Release 13). [cited by applicant]
3GPP TS 23.303 V13.3.0 (Mar. 2016), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Proximity-based services (ProSe); Stage 2 (Release 13). [cited by applicant]
3GPP TS 24.334 V13.3.1 (Mar. 2016), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Proximity-services (ProSe) User Equipment (UE) to Prose function… [cited by applicant]
3GPP TS 29.214 V13.5.0 (Mar. 2016), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control over Rx reference point, (Release 13… [cited by applicant]
3GPP TS 36.213 V13.2.0 (Jun. 2016), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer pr… [cited by applicant]
3GPP TS 36.300 V13.4.0 (Jun. 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.321 V13.2.0 (Jun. 2016), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Con… [cited by applicant]
3GPP TS 36.331 V13.2.0 (Jun. 2016), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Co… [cited by applicant]
R1-164878, 3GPP TSG RAN WG1 Meeting #85, Nanjing, China May 23-27, 2016, Source: CMCC, Title: Discussion on SPS configurations. [cited by applicant]
R1-162122, 3GPP TSG RAN WG1 Meeting #84bis, Busan, Korea, Apr. 11-15, 2016, Agenda Item: 7.3.2.2.2, Source: Huawei, HiSilicon, Title: SPS enhancement for V2V. [cited by applicant]
R1-162340, 3GPP TSG RAN WG1 Meeting #84 bis, Busan, Korea, Apr. 11-15, 2016, Source: OPPO, Title: Discussion on the SPS configuration. [cited by applicant]
R1-162413, 3GPP TSG-RAN WG1 Meeting #84bis, Busan, Korea Apr. 11-15, 2016, Source: ZTE, Title: Discussion on V2V SPS resource scheme. [cited by applicant]
R1-162500, RAN WG1 Meeting #84bis, Busan, Korea, Apr. 11-15, 2016, Source: LG Electronics, Title: Discussions on UL enhancements for V2X. [cited by applicant]
R1-164421, 3GPP TSG-RAN WG1 #85, May 23-27, 2016, Nanjing, China, Agenda item: 6.2.2.3.1, Source: Qualcomm Incorporated, Title: eNodeB signaling for SPS resource allocation. [cited by applicant]
R1-164422, 3GPP TSG-RAN WG1 #85, May 23-27, 2016, Nanjing, China, Agenda item: 6.2.2.3.2, Source: Qualcomm Incorporated, Title: UE reporting for eNodeB resource allocation. [cited by applicant]
R1-164468, 3GPP TSG RAN WG1 Meeting #85, Nanjing, China, May 23-27, 2016, Source: Guangdong OPPO Mobile Telecom, Title: Discussion on the SPS configuration for mode-2. [cited by applicant]
R1-164514, 3GPP TSG RAN WG1 Meeting #85, Nanjing, China May 23-27, 2016, Source: LG Electronics, Title: Discussion on details of (E)PDCCH used for sidelink SPS. [cited by applicant]
R1-164515, 3GPP TSG RAN WG1 Meeting #85, Nanjing, China, May 23-27, 2016, Agenda item: 6.2.2.3.2, Source: LG Electronics, Title: Discussion on details of UE reporting. [cited by applicant]
R1-164538, 3GPP TSG RAN WG1 Meeting #85, Nanjing, China, May 23-27, 2016, Source: LG Electronics, Title: Discussion on UL SPS for V2X. [cited by applicant]
R1-164762, 3GPP TSG RAN WG1 Meeting #85, Nanjing, May 23-27, 2016, Agenda Item: 6.2.2.3.1, Source: Samsung, Title: Multiple SPS configuration support for SL. [cited by applicant]
R1-164763, 3GPP TSG RAN WG1 Meeting #85, Nanjing, May 23-27, 2016, Agenda Item: 6.2.2.3.2, Source: Samsung, Title: UE reporting procedure for SL SPS transmissions. [cited by applicant]
R1-164818, 3GPP TSG RAN WG1 Meeting #85, Nanjing, China, May 23-27, 2016, Agenda Item: 6.2.2.3, Source: Huawei, HiSilicon, Title: SPS enhancement for V2V. [cited by applicant]
R1-164906, 3GPP TSG RAN WG1 Meeting #85, Nanjing, China May 23-27, 2016, Source: Panasonic, Title: Signaling design to support SPS activation/release in V2V. [cited by applicant]
R1-164963, 3GPP TSG-RAN WG1 Meeting #85, Nanjing, China May 23-27, 2016, Source: ZTE, Title: Trigger and release of V2V SPS resources. [cited by applicant]
R1-164964, 3GPP TSG RAN WG1 Meeting #85, Nanjing, China May 23-27, 2016, Agenda item: 6.2.2.3.2, Source: ZTE, Title: Discussion on UE reporting. [cited by applicant]
R1-165193, 3GPP TSG RAN WG1 Meeting #85, Nanjing, China May 23-27, 2016, Source: Nttdocomo, Inc., Title: (E)PDCCH for sidelink SPS configuration switching. [cited by applicant]
R1-165194, 3GPP TSG RAN WG1 Meeting #85, Nanjing, China May 23-27, 2016, Source: Ntt Docomo, Inc., Title: UE reporting for sidelink SPS operation. [cited by applicant]
R1-165246, 3GPP TSG RAN WG1 Meeting #85, Nanjing, PRC, May 23-27, 2016, Source: Ericsson, Title: Contents of Downlink Control Information for V2V over PCS. [cited by applicant]
R1-165272, 3GPP TSG RAN WG1 Meeting #85, Nanjing, PRC, May 23-27, 2016, Source: Ericsson, Title: Mode-1 SPS for V2V over PCS. [cited by applicant]
R1-165274, 3GPP TSG RAN WG1 Meeting #85, Nanjing, May 23-27, 2016, Source: Ericsson, Title: UL SPS and reporting to eNB for V2X. [cited by applicant]
R1-165309, 3GPP TSG RAN WG1 Meeting #85, Nanjing, China May 23-27, 2016, Source: Panasonic, Title: Details on PCS SPS enhancement. [cited by applicant]
R2-162197, 3GPP TSG-RAN2 Meeting #93bis, Dubrovnik, Croatia, Apr. 11-15, 2016, Agenda Item: 8.2.1, Source: OPPO, Title: Discussion on SPS Enhancements for V2V. [cited by applicant]
R2-162454, 3GPP TSG RAN WG2 Meeting #93bis, Dubrovnik, Croatia, Apr. 11-15, 2016, Agenda item: 8.2.1, Source: Intel Corporation, Title: SL resource allocation in SPS manner. [cited by applicant]
R2-162927, 3GPP TSG-RAN2 Meeting #93bis, Dubrovnik, Croatia, Apr. 11-15, 2016, Agenda item: 8.2.1, Source: LG Electronics Inc., Title: SL SPS enhancement for V2V. [cited by applicant]
R2-163406, 3GPP TSG-RAN2 Meeting #94, Nanjing, P. R. China, Apr. 23-27, 2016, Agenda Item: 8.11.1, Source: OPPO, Title: Discussion on SPS Enhancements for V2X. [cited by applicant]
R2-163421, 3GPP TSG-RAN WG2 Meeting #94, Nanjing, China, May 23-25, 2016, Source: CATT, Title: Consideration on SPS Enhancement. [cited by applicant]
R2-163451, 3GPP TSG RAN WG2 Meeting #94, Nanjing, China, Apr. 23-25, 2016, Agenda Item: 8.2.4, Source: Samsung, Title: UE reporting and dynamic SL SPS transmission. [cited by applicant]
R2-163807, 3GPP TSG-RAN WG2 Meeting #94, Nanjing, China, May 23-27, 2016, Agenda Item: 8.11.1, Source: Huawei, HiSilicon, InterDigital, LG Electronics Inc., OPPO, Title: Discussions on CAM Characteristics. [cited by applicant]
R2-163812, 3GPP TSG-RAN WG2 #94, Nanjing, China, May 23-27, 2016, Agenda Item: 8.2.4, Source: Huawei, HiSilicon, Title: Enhancements for Sidelink Resource Allocation. [cited by applicant]
R2-163840, 3GPP TSG RAN WG2 #94, Nanjing, China, May 23, 27, 2016, Source: ZTE, Title: SPS enhancements for V2X over Uu. [cited by applicant]
R2-163865, 3GPP TSG RAN WG2 Meeting #94, Nanjing, China, May 23-25, 2016, Source: ITL, Title: SLSPS for V2V. [cited by applicant]
R2-163885, 3GPP TSG RAN WG2 Meeting #94, Nanjing, China, May 23-27, 2016, Source: Potevio, Title: UE assisted information for SPS. [cited by applicant]
R2-163900, 3GPP TSG-RAN WG2 Meeting #94, Nanjing, China, May 23-27, 2016, Agenda item: 8.11.1, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: Multiple inter-dependent UL SPS occasions. [cited by applicant]
R2-164063, 3GPP TSG-RAN WG2 Meeting #94, Nanjing, China, May 23-27, 2016, Agenda item: 8.2.4, Source: Qualcomm Incorporated, Title: SPS for V2V Communication. [cited by applicant]
R2-164079, 3GPP TSG-RAN2 Meeting #94, Nanjing, China, Apr. 11-15, 2016, Agenda item: 8.2.4, Source: LG Electronics Inc. Title: Support of Semi-Persistent Scheduling for PCS mode 1. [cited by applicant]
R2-164082, 3GPP TSG-RAN2 Meeting #94, Nanjing, China, Apr. 11-15, 2016, Agenda item: 8.11.1, Source: LG Electronics Inc, InterDigital, OPPO, Huawei, Title: Proposed TP for UL SPS enhancements. [cited by applicant]
R2-164377, 3GPP TSG-RAN WG2 Meeting #94, Nanjing, China, May 23-27, 2016, Agenda item: 8.11.1, Source: Huawei, HiSilicon, Title: TP on CAM Characteristics. [cited by applicant]
Tdoc R2-161571, 3GPP TSG-RAN WG2 #93, St. Julians, Malta, Feb. 15-19, 2016, Agenda Item: 7.11, Source: Ericsson, Title: Overview of V2X Enhancements for Further RAN2 Work. [cited by applicant]
Tdoc R2-164112, 3GPP TSG-RAN WG2 #94, Nanjing, P.R. China, May 23-27, 2016, Agenda Item: 8.11.1, Source: Ericsson, Title: SPS Enhancements for Uu Operations in V2X. [cited by applicant]