All sample charts (18)US8971279B2Claim 1Sample report

US8971279B2 Claim 1 vs 3GPP TS 36.321: Sample Claim Chart

The content of a report SEPPi generated, shown as delivered. Reports are written in English.

Bibliographic data

Patent number
US8971279B2
Title
Method and apparatus for indicating deactivation of semi-persistent scheduling
Inventors
Dong Youn Seo, Ki Jun Kim, Dae Won Lee, Young Woo Yun, Joon Kui Ahn
Priority date
2008-11-13
Filing date
2013-03-08
Assignee
Sisvel SpA
Standard assessed
3GPP E-UTRA Rel-8 — PDCCH validation for semi-persistent scheduling (TS 36.213 §9.2) and UL grant reception (TS 36.321 §5.4.1) — Any 3GPP Rel-8 compliant UE
Target release
Rel-8 (TS 36.321 v8.12.0, TS 36.300 v8.12.0, TS 36.213 v8.8.0, TS 36.331 v8.21.0, TS 36.211 v8.9.0, TS 36.212 v8.8.0)

Claim 1 (independent)

A method for deactivating Semi-Persistent Scheduling (SPS) transmission in a wireless mobile communication system, the method comprising: performing, by a User Equipment (UE), a SPS transmission at an interval of a subframe period configured by a radio resource control (RRC) signal; receiving, by the UE, a Physical Downlink Control Channel (PDCCH) signal with a Radio Network Temporary Identifier (RNTI), wherein the PDCCH signal includes a first field related to a resource allocation; and performing a procedure for deactivating the SPS transmission if the PDCCH signal satisfies conditions for SPS deactivation, wherein the conditions for SPS deactivation include: the RNTI is a SPS Cell RNTI (SPS C-RNTI); and the first field is entirely filled with ‘1’.

Standard under assessment

Rel-8 · TS 36.321 v8.12.0 · TS 36.300 v8.12.0 · TS 36.213 v8.8.0 · TS 36.331 v8.21.0 · TS 36.211 v8.9.0 · TS 36.212 v8.8.0

Primary target: 3GPP E-UTRA (LTE) Release 8 — TS 36.213 v8.8.0 §9.2 (PDCCH validation for semi-persistent scheduling) and TS 36.321 v8.12.0 §5.4.1 (UL grant reception), supported by TS 36.321 §5.10.2 and §7.1, TS 36.331 §5.3.10.5 and §6.3.2, TS 36.212 §5.3.3.1.1, TS 36.211 §6.8.1 and TS 36.300 §8.1 and §11.1.2. Release. Release 8 is the earliest release of these specifications available at the date of analysis, and every clause cited is present there, so Release 8 is the release in which the claimed technology is charted. The Release 8 documents are cited at their last version.

Branch of the standard followed. All rows are mapped along one branch: the release of an uplink semi-persistent grant by a PDCCH with DCI format 0 addressed with the Semi-Persistent Scheduling C-RNTI, for a single uplink SPS configuration. Release 8 specifies the PDCCH variant only.

Other specification family. The NR physical layer procedures specification (TS 38.213, first present in Release 15) also contains a PDCCH validation clause for semi-persistent scheduling and configured grants; they are not charted here because the claimed technology entered the standard in LTE first.

Reading of the release table. In the Release 8 page of TS 36.213 §9.2 the release-validation table gives the value 'Set to all ‘1’s' in the row 'Resource block assignment and hopping resource allocation'. The text of that cell cannot be read from the document text, so the value is shown in the screenshot of row L6 and the underline is placed on the row label.

Claim chart

Matching colors mark corresponding elements between the claim and the standard. An underline in a screenshot marks the text the mapping rests on.

P

A method for deactivating Semi-Persistent Scheduling (SPS) transmission in a wireless mobile communication system, the method comprising:

Context: TS 36.300 describes the setting of the claim — E-UTRAN can allocate a semi-persistent uplink resource, on which the UE makes the uplink transmission according to the semi-persistent allocation that the claim goes on to perform and deactivate.

Excerpt from TS 36.300 v8.12.0 §11.1.2 — Uplink Scheduling, underlined where the mapping rests on it
TS 36.300 v8.12.0 §11.1.2 — Uplink Scheduling
L1

performing, by a User Equipment (UE), a SPS transmission at an interval of a subframe period configured by a radio resource control (RRC) signal;

The UE performs the uplink transmission according to the semi-persistent allocation by delivering the configured uplink grant to the HARQ entity (TS 36.321 §5.4.1); once the grant is configured it recurs in each subframe given by semiPersistSchedIntervalUL (TS 36.321 §5.10.2). That interval, in sub-frames, is a field of the SPS-Config IE, which RRC uses to specify the semi-persistent scheduling configuration (TS 36.331 §6.3.2). The configuration is optional: the behaviour holds when the UE is configured with uplink semi-persistent scheduling.

Excerpt from TS 36.300 v8.12.0 §11.1.2 — Uplink Scheduling, underlined where the mapping rests on it
TS 36.300 v8.12.0 §11.1.2 — Uplink Scheduling
Excerpt from TS 36.321 v8.12.0 §5.10.2 — Uplink, underlined where the mapping rests on it
TS 36.321 v8.12.0 §5.10.2 — Uplink
Excerpt from TS 36.321 v8.12.0 §5.4.1 — UL Grant reception, underlined where the mapping rests on it
TS 36.321 v8.12.0 §5.4.1 — UL Grant reception
Excerpt from TS 36.331 v8.21.0 §5.3.10.5 — Semi-persistent scheduling reconfiguration, underlined where the mapping rests on it
TS 36.331 v8.21.0 §5.3.10.5 — Semi-persistent scheduling reconfiguration
Excerpt from TS 36.331 v8.21.0 §6.3.2 — Radio resource control rmation elements, underlined where the mapping rests on it
TS 36.331 v8.21.0 §6.3.2 — Radio resource control rmation elements
Excerpt from TS 36.331 v8.21.0 §6.3.2 — Radio resource control rmation elements, underlined where the mapping rests on it
TS 36.331 v8.21.0 §6.3.2 — Radio resource control rmation elements
L2

receiving, by the UE, a Physical Downlink Control Channel (PDCCH) signal with a Radio Network Temporary Identifier (RNTI),

The UE receives the Semi-Persistent Scheduling assignment PDCCH: it handles an uplink grant 'received on the PDCCH for the UE’s Semi-Persistent Scheduling C-RNTI' (TS 36.321 §5.4.1) and validates that PDCCH (TS 36.213 §9.2), the PDCCH carrying scheduling assignments and other control information (TS 36.211 §6.8.1). The PDCCH is addressed with an RNTI, one of the E-UTRAN related UE identities (TS 36.321 §7.1, TS 36.300 §8.1).

Excerpt from TS 36.211 v8.9.0 §6.8.1 — PDCCH formats, underlined where the mapping rests on it
TS 36.211 v8.9.0 §6.8.1 — PDCCH formats
Excerpt from TS 36.213 v8.8.0 §9.2 — PDCCH validation for semi-persistent scheduling, underlined where the mapping rests on it
TS 36.213 v8.8.0 §9.2 — PDCCH validation for semi-persistent scheduling
Excerpt from TS 36.300 v8.12.0 §8.1 — E-UTRAN related UE identities, underlined where the mapping rests on it
TS 36.300 v8.12.0 §8.1 — E-UTRAN related UE identities
Excerpt from TS 36.321 v8.12.0 §5.4.1 — UL Grant reception, underlined where the mapping rests on it
TS 36.321 v8.12.0 §5.4.1 — UL Grant reception
Excerpt from TS 36.321 v8.12.0 §7.1 — RNTI values, underlined where the mapping rests on it
TS 36.321 v8.12.0 §7.1 — RNTI values
L3

wherein the PDCCH signal includes a first field related to a resource allocation; and

The Semi-Persistent Scheduling assignment PDCCH carries DCI format 0, which transmits the Resource block assignment and hopping resource allocation field (TS 36.212 §5.3.3.1.1); TS 36.213 §8.1 ties the resource allocation to the 'corresponding PDCCH with DCI format 0'.

Excerpt from TS 36.212 v8.8.0 §5.3.3.1.1 — Format 0, underlined where the mapping rests on it
TS 36.212 v8.8.0 §5.3.3.1.1 — Format 0
Excerpt from TS 36.213 v8.8.0 §8.1 — Resource Allocation for PDCCH DCI Format 0, underlined where the mapping rests on it
TS 36.213 v8.8.0 §8.1 — Resource Allocation for PDCCH DCI Format 0
L4

performing a procedure for deactivating the SPS transmission if the PDCCH signal satisfies conditions for SPS deactivation,

If the PDCCH contents indicate SPS release, the UE clears the configured uplink grant (TS 36.321 §5.4.1): the SPS release that deactivates the uplink transmission according to the semi-persistent allocation. Whether the received Semi-Persistent Scheduling assignment PDCCH is such a release is decided by the Semi-Persistent Scheduling Release PDCCH Validation of TS 36.213 §9.2: the UE validates the PDCCH only if all the listed conditions are met, and the fields are set as the release table requires. L5 and L6 state two of these conditions.

Excerpt from TS 36.213 v8.8.0 §9.2 — PDCCH validation for semi-persistent scheduling, underlined where the mapping rests on it
TS 36.213 v8.8.0 §9.2 — PDCCH validation for semi-persistent scheduling
Excerpt from TS 36.300 v8.12.0 §11.1.2 — Uplink Scheduling, underlined where the mapping rests on it
TS 36.300 v8.12.0 §11.1.2 — Uplink Scheduling
Excerpt from TS 36.321 v8.12.0 §5.4.1 — UL Grant reception, underlined where the mapping rests on it
TS 36.321 v8.12.0 §5.4.1 — UL Grant reception
L5

wherein the conditions for SPS deactivation include: the RNTI is a SPS Cell RNTI (SPS C-RNTI); and

One condition of the Semi-Persistent Scheduling Release PDCCH Validation is that the CRC parity bits of the PDCCH payload are scrambled with the Semi-Persistent Scheduling C-RNTI (TS 36.213 §9.2), the identity TS 36.300 §8.1 defines for semi-persistent scheduling. The RNTI with which the PDCCH is received is thereby that identity (TS 36.321 §7.1).

Excerpt from TS 36.213 v8.8.0 §9.2 — PDCCH validation for semi-persistent scheduling, underlined where the mapping rests on it
TS 36.213 v8.8.0 §9.2 — PDCCH validation for semi-persistent scheduling
Excerpt from TS 36.300 v8.12.0 §8.1 — E-UTRAN related UE identities, underlined where the mapping rests on it
TS 36.300 v8.12.0 §8.1 — E-UTRAN related UE identities
Excerpt from TS 36.321 v8.12.0 §7.1 — RNTI values, underlined where the mapping rests on it
TS 36.321 v8.12.0 §7.1 — RNTI values
L6

the first field is entirely filled with ‘1’.

The other condition: in the release validation the row of the Resource block assignment and hopping resource allocation field of DCI format 0 reads 'Set to all ‘1’s' (value shown in the screenshot, underline on the row label); the validation is achieved when all fields of the DCI format are set according to the table (TS 36.213 §9.2).

Excerpt from TS 36.213 v8.8.0 §9.2 — PDCCH validation for semi-persistent scheduling, underlined where the mapping rests on it
TS 36.213 v8.8.0 §9.2 — PDCCH validation for semi-persistent scheduling

Overall assessment

L1–L6 map to the standard along the uplink release path of semi-persistent scheduling: the Semi-Persistent Scheduling C-RNTI and the all-ones resource allocation field validate a PDCCH as an SPS release.

References

this document is a technical essentiality assessment prepared for reference, comparing published patent documents against 3GPP standard specifications. It is not a legal determination or legal advice on the essentiality, validity or infringement of the patent. Before any material decision such as licensing or litigation, obtain a review by a qualified patent attorney or attorney at law.

Run it on your own patent

Enter a patent number and get the same chart for your claim. Your first report is free with a company email.

Get started