All sample charts (18)EP2229744Claim 1Sample report

EP2229744 Claim 1 vs 3GPP TS 36.322: Sample Claim Chart

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

Bibliographic data

Patent number
EP2229744
Title
Method and arrangement in a wireless communication network
Inventors
Janne Peisa, Michael Meyer, Johan Torsner
Priority date
2008-01-08
Filing date
2008-01-08
Assignee
Telefonaktiebolaget LM Ericsson AB
Standard assessed
TS 36.322 E-UTRA RLC — polling by PDU count and byte count (§5.2.2.1) — Any 3GPP Rel-8 compliant UE / eNB
Target release
Rel-8 (TS 36.322 v8.8.0, TS 36.300 v8.12.0, TS 36.331 v8.21.0)

Claim 1 (independent)

Method in a first node for requesting a status report from a second node, the first node and the second node both being comprised within a wireless communication network, the status report comprising positive and/or negative acknowledgement of data sent from the first node to be received by the second node, wherein the method comprises the steps of: transmitting a sequence of data units or data unit segments to be received by the second node, the method further comprises the steps of: counting the number of transmitted data units and the number of transmitted data bytes of the transmitted data units, and, requesting a status report from the second node if the counted number of transmitted data units exceeds or equals a first predefined value or the counted number of transmitted data bytes of the transmitted data units exceeds or equals a second predefined value.

Standard under assessment

Rel-8 · TS 36.322 v8.8.0 · TS 36.300 v8.12.0 · TS 36.331 v8.21.0

Primary target: TS 36.322 (E-UTRA Radio Link Control), version 8.8.0 of Rel-8 — §5.2.2.1 (transmission of an AMD PDU), §7.1 (counters) and §7.4 (configurable parameters) — with the RRC configuration of the thresholds in TS 36.331 version 8.21.0, §6.3.2 (RLC-Config), and the network architecture in TS 36.300 version 8.12.0, §4. All extracts and screenshots are taken from Rel-8.

The chart follows one path of the polling procedure: the count-based trigger of §5.2.2.1, which compares the number of AMD PDUs and the number of data bytes sent since the last poll with the configured thresholds. The other poll triggers of that clause (both buffers empty, expiry of t-PollRetransmit) are not used. The first node is read as the UE and the second node as the eNB; the specification words the procedure for either end of the link.

The same counters and thresholds are worded in the NR specification TS 38.322, whose polling clause first appears in Rel-15. The UMTS specification TS 25.322 triggers a poll by PDU count and SDU count only, with no byte count. E-UTRA is charted because the technology entered the standard there first. The declaration recorded by ETSI names TS 38.322, which has no Rel-8 version.

The wording of TS 36.322 §4.2.1, §5.2.2.1 and §7.4 is different in Rel-19; every other cited clause reads the same word for word in Rel-19.

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

Method in a first node for requesting a status report from a second node, the first node and the second node both being comprised within a wireless communication network, the status report comprising positive and/or negative acknowledgement of data sent from the first node to be received by the second node, wherein the method comprises the steps of:

Context: the claimed method is the polling of acknowledged-mode RLC in E-UTRA. The transmitting side of an AM RLC entity in the UE is the first node and the peer AM RLC entity in the eNB is the second node, both within the E-UTRAN. The STATUS report provides positive acknowledgement (ACK_SN field) and/or negative acknowledgement (NACK_SN) of the RLC data PDUs the first node sent.

Excerpt from TS 36.300 v8.12.0 §4 — Overall architecture, underlined where the mapping rests on it
TS 36.300 v8.12.0 §4 — Overall architecture
Excerpt from TS 36.322 v8.8.0 §4.2.1 — RLC entities, underlined where the mapping rests on it
TS 36.322 v8.8.0 §4.2.1 — RLC entities
Excerpt from TS 36.322 v8.8.0 §5.1.3.1 — Transmit operations, underlined where the mapping rests on it
TS 36.322 v8.8.0 §5.1.3.1 — Transmit operations
Excerpt from TS 36.322 v8.8.0 §5.2.2 — Polling, underlined where the mapping rests on it
TS 36.322 v8.8.0 §5.2.2 — Polling
Excerpt from TS 36.322 v8.8.0 §5.2.2.1 — Transmission of a AMD PDU or AMD PDU segment, underlined where the mapping rests on it
TS 36.322 v8.8.0 §5.2.2.1 — Transmission of a AMD PDU or AMD PDU segment
Excerpt from TS 36.322 v8.8.0 §5.2.3 — Status reporting, underlined where the mapping rests on it
TS 36.322 v8.8.0 §5.2.3 — Status reporting
Excerpt from TS 36.322 v8.8.0 §6.2.2.11 — Polling bit (P) field, underlined where the mapping rests on it
TS 36.322 v8.8.0 §6.2.2.11 — Polling bit (P) field
Excerpt from TS 36.322 v8.8.0 §6.2.2.14 — Acknowledgement SN (ACK_SN) field, underlined where the mapping rests on it
TS 36.322 v8.8.0 §6.2.2.14 — Acknowledgement SN (ACK_SN) field
Excerpt from TS 36.322 v8.8.0 §6.2.2.16 — Negative Acknowledgement SN (NACK_SN) field, underlined where the mapping rests on it
TS 36.322 v8.8.0 §6.2.2.16 — Negative Acknowledgement SN (NACK_SN) field
L1

transmitting a sequence of data units or data unit segments to be received by the second node, the method further comprises the steps of:

The transmitting side delivers each new AMD PDU to lower layer for sending to the peer entity and, for a retransmitted portion, AMD PDU segments; the receiving side of the peer AM RLC entity receives them.

Excerpt from TS 36.322 v8.8.0 §4.2.1 — RLC entities, underlined where the mapping rests on it
TS 36.322 v8.8.0 §4.2.1 — RLC entities
Excerpt from TS 36.322 v8.8.0 §4.2.1.3.2 — Transmitting side, underlined where the mapping rests on it
TS 36.322 v8.8.0 §4.2.1.3.2 — Transmitting side
Excerpt from TS 36.322 v8.8.0 §5.1.3.1 — Transmit operations, underlined where the mapping rests on it
TS 36.322 v8.8.0 §5.1.3.1 — Transmit operations
Excerpt from TS 36.322 v8.8.0 §5.2.2.1 — Transmission of a AMD PDU or AMD PDU segment, underlined where the mapping rests on it
TS 36.322 v8.8.0 §5.2.2.1 — Transmission of a AMD PDU or AMD PDU segment
Excerpt from TS 36.322 v8.8.0 §6.1.1 — RLC data PDU, underlined where the mapping rests on it
TS 36.322 v8.8.0 §6.1.1 — RLC data PDU
L2

counting the number of transmitted data units and the number of transmitted data bytes of the transmitted data units,

Upon assembly of a new AMD PDU the transmitting side increments PDU_WITHOUT_POLL by one; the counter holds the number of AMD PDUs sent since the most recent poll bit was transmitted. It increments BYTE_WITHOUT_POLL by every new byte of Data field element mapped to the Data field; the counter holds the number of data bytes sent since the most recent poll bit was transmitted.

Excerpt from TS 36.322 v8.8.0 §5.2.2.1 — Transmission of a AMD PDU or AMD PDU segment, underlined where the mapping rests on it
TS 36.322 v8.8.0 §5.2.2.1 — Transmission of a AMD PDU or AMD PDU segment
Excerpt from TS 36.322 v8.8.0 §7.1 — State variables, underlined where the mapping rests on it
TS 36.322 v8.8.0 §7.1 — State variables
L3

requesting a status report from the second node if the counted number of transmitted data units exceeds or equals a first predefined value or the counted number of transmitted data bytes of the transmitted data units exceeds or equals a second predefined value.

When either condition is met the transmitting side includes a poll in the RLC data PDU: the P field requests a STATUS report from the peer AM RLC entity. The condition is met if PDU_WITHOUT_POLL reaches the pollPDU Parameter, or if BYTE_WITHOUT_POLL reaches the pollByte Parameter; both are configured by RRC.

Excerpt from TS 36.322 v8.8.0 §5.2.2 — Polling, underlined where the mapping rests on it
TS 36.322 v8.8.0 §5.2.2 — Polling
Excerpt from TS 36.322 v8.8.0 §5.2.2.1 — Transmission of a AMD PDU or AMD PDU segment, underlined where the mapping rests on it
TS 36.322 v8.8.0 §5.2.2.1 — Transmission of a AMD PDU or AMD PDU segment
Excerpt from TS 36.322 v8.8.0 §6.2.2.11 — Polling bit (P) field, underlined where the mapping rests on it
TS 36.322 v8.8.0 §6.2.2.11 — Polling bit (P) field
Excerpt from TS 36.322 v8.8.0 §7.4 — Configurable parameters, underlined where the mapping rests on it
TS 36.322 v8.8.0 §7.4 — Configurable parameters
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

Overall assessment

L1–L3 map to the standard.

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