IP Library › Granted Patent US 12,526,608
Granted Patent B2
US 12,526,608 · App. 18/548,651 · Granted Jan 13, 2026

Reliable SPS configuration for MBS

Inventors: Ugur Baran Elmali (Munich, DE); Volker Pauli (Munich, DE); Esa Mikael Malkamäki (Espoo, FI); Benoist Pierre Sebire (Tokyo, JP); David Navrátil (Espoo, FI)
Assignee: Nokia Technologies
H04W4/06H04L1/1812H04W72/11H04W72/12
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,526,608
App. No.
18/548,651
Granted
Jan 13, 2026
Kind
B2
Abstract

Embodiments of the present disclosure relate to reliable SPS configuration for MBS. In the solution, a first device starts a first timer upon receiving, from a second device, configuration of a semi-persistent scheduling (SPS) for a multicast and broadcast service (MBS). Then if the first timer expires and there is no information received to activate corresponding SPS scheduled transmissions, the first device transmits to the second device a message indicating that the first device failed to receive the information. This solution allows reliable SPS configuration for MBS.

Claims (52)

1 . A first device, comprising:

at least one processor; and

at least one memory including computer program code;

the at least one memory and the program code are configured to, with the at least one processor, cause the first device to:

start a first timer upon receiving, from a second device, configuration of a semi-persistent scheduling (SPS) for a multicast and broadcast service (MBS); and

if the first timer expires and there is no information received to activate corresponding SPS scheduled transmissions, transmit to the second device a message indicating that the first device failed to receive the information.

2 . The first device of claim 1 , wherein the at least one memory and the program code are configured to, with the at least one processor, further cause the first device to:

restart the first timer upon the transmission of the message.

3 . The first device of claim 1 , wherein the at least one memory and the program code are configured to, with the at least one processor, further cause the first device to:

receive a configuration of a group-common uplink resource for a group of devices comprising the first device; and

transmit the message to the second device via the group-common uplink resource.

4 . The first device of claim 1 , wherein the message is transmitted to the second device via a user equipment-specific uplink resource.

5 . The first device of claim 1 , wherein the at least one memory and the program code are configured to, with the at least one processor, further cause the first device to:

increase a counter upon the transmission of the message; and

in accordance with a determination that the counter exceeds a threshold number, perform a random-access procedure for transmitting the message.

6 . The first device of claim 5 , wherein the threshold number is determined based on at least one of the following:

an indication of a maximum number from the second device, or

the maximum number of allowed hybrid automatic repeat request, HARQ, transmissions for a transport block of the MBS scheduled by the SPS.

7 . The first device of claim 1 , wherein the at least one memory and the program code are configured to, with the at least one processor, further cause the first device to:

in response to receiving the information indicating to activate the SPS, stop the first timer.

8 . A method comprising:

starting, at a first device, a first timer upon receiving, from a second device, configuration of a semi-persistent scheduling (SPS) for a multicast and broadcast service (MBS); and

if the first timer expires and there is no information received to activate corresponding SPS scheduled transmissions, transmitting to the second device a message indicating that the first device failed to receive the information.

9 . The method of claim 8 , wherein the at least one memory and the program code are configured to, with the at least one processor, further cause the first device to:

restart the first timer upon the transmission of the message.

10 . The method of claim 8 , wherein the at least one memory and the program code are configured to, with the at least one processor, further cause the first device to:

receive a configuration of a group-common uplink resource for a group of devices comprising the first device; and

transmit the message to the second device via the group-common uplink resource.

11 . The method of claim 8 , wherein the message is transmitted to the second device via a user equipment-specific uplink resource.

12 . The method of claim 8 , wherein the at least one memory and the program code are configured to, with the at least one processor, further cause the first device to:

increase a counter upon the transmission of the message; and

in accordance with a determination that the counter exceeds a threshold number, perform a random-access procedure for transmitting the message.

13 . The method of claim 12 , wherein the threshold number is determined based on at least one of the following:

an indication of a maximum number from the second device, or

the maximum number of allowed hybrid automatic repeat request, HARQ, transmissions for a transport block of the MBS scheduled by the SPS.

14 . The method of claim 8 , wherein the at least one memory and the program code are configured to, with the at least one processor, further cause the first device to:

in response to receiving the information indicating to activate the SPS, stop the first timer.

15 . A non-transitory computer readable storage medium comprising program instructions for causing an apparatus to perform at least:

starting, at a first device, a first timer upon receiving, from a second device, configuration of a semi-persistent scheduling (SPS) for a multicast and broadcast service (MBS); and

if the first timer expires and there is no information received to activate corresponding SPS scheduled transmissions, transmitting to the second device a message indicating that the first device failed to receive the information.

16 . The non-transitory computer readable storage medium of claim 15 , wherein the at least one memory and the program code are configured to, with the at least one processor, further cause the first device to:

restart the first timer upon the transmission of the message.

17 . The non-transitory computer readable storage medium of claim 15 , wherein the at least one memory and the program code are configured to, with the at least one processor, further cause the first device to:

receive a configuration of a group-common uplink resource for a group of devices comprising the first device; and

transmit the message to the second device via the group-common uplink resource.

18 . The non-transitory computer readable storage medium of claim 15 , wherein the message is transmitted to the second device via a user equipment-specific uplink resource.

19 . The non-transitory computer readable storage medium of claim 15 , wherein the at least one memory and the program code are configured to, with the at least one processor, further cause the first device to:

increase a counter upon the transmission of the message; and

in accordance with a determination that the counter exceeds a threshold number, perform a random-access procedure for transmitting the message.

20 . The non-transitory computer readable storage medium of claim 19 , wherein the threshold number is determined based on at least one of the following:

an indication of a maximum number from the second device, or

the maximum number of allowed hybrid automatic repeat request, HARQ, transmissions for a transport block of the MBS scheduled by the SPS.

Assignments (6)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 9, 2024
From: ELMALI, UGUR BARAN; PAULI, VOLKER
To: NOKIA SOLUTIONS AND NETWORKS GMBH & CO. KG
Reel/Frame 066057/0446 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 9, 2024
From: SEBIRE, BENOIST PIERRE
To: NOKIA SOLUTIONS AND NETWORKS JAPAN G.K.
Reel/Frame 066057/0453 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 9, 2024
From: MALKAMÄKI, ESA MIKAEL; NAVRÁTIL, DAVID
To: NOKIA SOLUTIONS AND NETWORKS OY
Reel/Frame 066057/0456 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 9, 2024
From: NOKIA SOLUTIONS AND NETWORKS GMBH & CO. KG
To: NOKIA TECHNOLOGIES OY
Reel/Frame 066057/0459 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 9, 2024
From: NOKIA SOLUTIONS AND NETWORKS JAPAN G.K.
To: NOKIA TECHNOLOGIES OY
Reel/Frame 066057/0463 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 9, 2024
From: NOKIA SOLUTIONS AND NETWORKS OY
To: NOKIA TECHNOLOGIES OY
Reel/Frame 066057/0467 →
Continuity (1)
Related Publication 20240155311A1 · May 9, 2024
References Cited (29)
US 10912102B2 · Shi · 2021 [cited by applicant]
US 11153060B2 · Babaei · 2021 [cited by examiner]
US 20140204819A1 · Ohta · 2014 [cited by examiner]
US 20170353273A1 · Zhang et al. · 2017 [cited by applicant]
US 20180242326A1 · Aiba et al. · 2018 [cited by applicant]
US 20190053211A1 · Ying · 2019 [cited by examiner]
US 20190174530A1 · Kim · 2019 [cited by examiner]
US 20190394794A1 · Mali et al. · 2019 [cited by applicant]
US 20200259622A1 · Cao et al. · 2020 [cited by applicant]
US 20200322921A1 · Zhou et al. · 2020 [cited by applicant]
US 20210076409A1 · Goto et al. · 2021 [cited by applicant]
US 20210160879A1 · Lin · 2021 [cited by examiner]
US 20210218503A1 · Babaei · 2021 [cited by examiner]
US 20230081792A1 · Kim · 2023 [cited by examiner]
WO 2016029352A1 · 2016 [cited by applicant]
WO 2020063351A1 · 2020 [cited by applicant]
WO WO2021031038A1 · 2021 [cited by examiner]
WO 2022151165A1 · 2022 [cited by applicant]
WO 2022151212A1 · 2022 [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 16)”, 3GPP TS 38.331, V16.3.1, Jan. 2021, pp. 1-932. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 16)”, 3GPP TS 38.213, V16.4.0, Dec. 2020, pp. 1-181. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 16)”, 3GPP TS 38.214, V16.4.0, Dec. 2020, pp. 1-169. [cited by applicant]
“New Work Item on NR support of Multicast and Broadcast Services”, 3GPP TSG RAN Meeting #86, RP-193248, Agenda Item: 9.1.2, Huawei, Dec. 9-12, 2019, 5 pages. [cited by applicant]
“FL summary#1 on improving reliability for MBS for RRC_CONNECTED UEs”, 3GPP TSG RAN WG1 Meeting #104-e, R1-200xxxx, Agenda Item: 8.12.2, Huawei, Jan. 25-Feb. 5, 2021, 67 pages. [cited by applicant]
International Search Report and Written Opinion received for corresponding Patent Cooperation Treaty Application No. PCT/EP2021/058911, dated Jan. 5, 2022, 14 pages. [cited by applicant]
“Error recovery from SPS activation failure”, 3GPP TSG RAN WG2 #67, R2-094491, Agenda Item: 6.7.2, ETRI, Aug. 24-28, 2009, pp. 1-4. [cited by applicant]
“Discussion on MBS reliability for RRC_CONNECTED UEs”, 3GPP TSG-RAN-WG1 #104b-e, R1-2102552, Agenda Item: 8.12.2, Google Inc, Apr. 12-20, 2021, 4 pages. [cited by applicant]
“Remaining details of UE behavior for SL and UL SPS”, 3GPP TSG RAN WG1 Meeting #87, R1-1611736, Agenda Item: 6.2.1.1.2, LG Electronics, Nov. 14-18, 2016, pp. 1-2. [cited by applicant]
“SPS enhancement for V2V”, 3GPP TSG RAN WG1 Meeting #84bis, R1-162122, Agenda Item: 7.3.2.2.2, Huawei, Apr. 11-15, 2016, 6 pages. [cited by applicant]