EP1212919 청구항 1 · 3GPP TS 25.413 대조 샘플 클레임 차트

서지 정보

특허 번호

EP1212919

발명의 명칭

Relocation in a Communication System

발명자

Kalle Nokia Japan Co Ltd AHMAVAARA

최우선일

1999-09-14

출원일

1999-09-14

권리자

Nokia Oyj

대조 표준

UMTS (UTRAN) SRNS relocation — TS 25.331 §14.12 (RRC information between network nodes) with TS 25.413 §8.6 and §9.2.1.28 (RANAP Relocation Preparation) — Any 3GPP Rel-8 compliant UTRAN RNC / core network node

대상 릴리즈

Rel-8 (TS 25.413 v8.8.0, TS 25.331 v8.25.0, TS 25.301 v8.7.0, TS 25.401 v8.2.0)

청구항 1 (독립항)

(a) A method in a communication system for relocating a protocol termination point, characterised in the steps of: (b) using a first protocol to define a protocol initialization unit (2 at a first termination point of a first protocol (3, said protocol initialization unit containing predefined information pertaining to initialization of a second termination point (3 of said first protocol; (c) transferring the protocol initialization unit from the first termination point to a second termination point by a second protocol; and (d) initializing the second termination point based on the protocol initialization unit (3; (e) wherein the protocol initialization unit (2 is transparent for the second protocol.

대조 대상 표준

Rel-8 · TS 25.413 v8.8.0 · TS 25.331 v8.25.0 · TS 25.301 v8.7.0 · TS 25.401 v8.2.0

Primary target: UMTS (UTRAN) SRNS relocation — the RRC information container of TS 25.331 §14.12 (RRC information transferred between network nodes) carried by the Relocation Preparation procedure of TS 25.413 §8.6 and §9.2.1.28 (RANAP, Iu interface), with TS 25.301 §5.6.2 and TS 25.401 §7.2.3.2 for protocol termination and the relocation context. The assessment is made against Rel-8: TS 25.301 v8.7.0, TS 25.331 v8.25.0, TS 25.401 v8.2.0 and TS 25.413 v8.8.0, the last version of each specification in that release. The wording relied on is unchanged in Rel-19.

Why this release and family: Rel-8 is the earliest release of these specifications available for the assessment, so it is a lower bound for when the wording entered the standard; the change history of TS 25.331 already lists CR 215 (RP-000046, meeting RP-07) "Updates to RRC Initialisation Information transparent container and addition of reverse direction container description", which predates Rel-8. The UMTS family is therefore charted rather than the LTE specifications named in the ETSI declaration, whose change history starts in Rel-8; the two families' citations are not mixed.

Branch charted: SRNC relocation within UTRAN (Relocation Preparation followed by Relocation Resource Allocation), the relocation type not fixed. The other branch of TS 25.331 §14.12.1, handover to UTRAN, takes the information from another RAT. The first termination point is read as the source RNC and the second termination point as the target RNC.

Readings that go beyond the standard's literal words: the unit passes through the core network between the two termination points (RELOCATION REQUIRED to the core network, TS 25.413 §9.1.9, then RELOCATION REQUEST to the target RNC), while the claim names no intermediate node; and the standard states that the container is transparent to the core network (CN), which is read as transparent for the second protocol.

클레임 차트

같은 색상은 청구항과 표준에서 대응되는 구성을 나타냅니다. 원문 발췌의 밑줄은 대응의 근거가 된 문언입니다.

#청구항 1 — EP1212919Rel-8 · TS 25.413 v8.8.0 · TS 25.331 v8.25.0 · TS 25.301 v8.7.0 · TS 25.401 v8.2.0

P

A method in a communication system for relocating a protocol termination point, characterised in the steps of:

Context: RRC terminates in the Serving RNC (TS 25.301 §5.6.2); in an SRNS relocation that SRNS role is taken over by another RNS (TS 25.401 §7.2.3.2), and the source RNC triggers the execution of the relocation once the Relocation Preparation procedure has ended (TS 25.413 §8.6.2).

L1

using a first protocol to define a protocol initialization unit (2 at a first termination point of a first protocol (3, said protocol initialization unit containing predefined information pertaining to initialization of a second termination point (3 of said first protocol;

In an SRNC relocation the RRC Container IE (the RRC information container sent as "RRC Information to target RNC") originates from the source RNC (TS 25.331 §14.12.1), which includes it in the relocation message (TS 25.413 §8.6.2). The information it transfers specifies the configuration of RRC and the lower layers it controls — the content of SRNS RELOCATION INFO (TS 25.331 §14.12.4.2) — and is used by the target RNC to initialise RRC and the lower layer protocols.

L2

transferring the protocol initialization unit from the first termination point to a second termination point by a second protocol; and

The source RNC opens the relocation by sending RELOCATION REQUIRED over Radio Access Network Application Part (RANAP), including the RRC Container IE in the container of that message (TS 25.413 §8.6.2, §9.1.9). The container is produced by the source RNC and transmitted to the target RNC (TS 25.413 §9.2.1.28), which acts on the RELOCATION REQUEST message (TS 25.413 §8.7.2). The unit passes through the core network between the two ends.

L3

initializing the second termination point based on the protocol initialization unit (3;

The target RNC uses the RRC Container IE to initialise RRC and the lower layer protocols (TS 25.331 §14.12.1); the receiving RRC protocol entity is able to interpret the received container (TS 25.331 §14.12.0).

L4

wherein the protocol initialization unit (2 is transparent for the second protocol.

The RRC Container IE travels in an IE of Radio Access Network Application Part (RANAP) that "is transparent to the CN" (TS 25.413 §9.2.1.28). Read broadly, the claim's "transparent for the second protocol" corresponds to the standard's "transparent to the CN", the node that terminates that protocol.

종합

L1–L4 map to the standard.

참고 문헌

• TS 25.301 — Radio interface protocol architecture
• TS 25.331 — Radio Resource Control (RRC); Protocol specification
• TS 25.401 — UTRAN overall description
• TS 25.413 — UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling

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.