throbber
5/20/2020
`
`http://www.3gpp.org/specs/version-numbering.htm
`
`83 captures
`27 Nov 2005 - 12 Sep 2008
`
`3GPP Specifications - Version numbering scheme
`Go AUG SEP OCT
`12
`2007 2008 2009
`
`👤 ⍰ ❎
`
`
`f 🐦
`▾ About this capture
`
`3GPP Specifications - Version numbering scheme
`Spec download | Titles and spec numbers | Current version | Releases | Numbering scheme | Change Requests
`Published specifications | Historical information | Work plan | TSG Working methods | Drafting rules | Delegates corner| ASN.1
`
`As 3GPP Technical Specifications and Technical Reports evolve from the early drafting stages, though progressively more stable versions, to
`being brought under change control, so the version number of the document changes. The rules for maintaining the version number are contained
`in clause 4.4 of 3GPP TR 21.900, but are briefly summarized here.
`
`The "version" is comprised of three fields:
`
`major
`
`technical
`
`editorial
`
`and each has a numeric value, starting with zero. The fields are separated with dots, and the version number shows major, technical and editorial
`fields respectively from left to right. Thus a spec whose major field is 4, whose technical field is 7 and whose editorial field is 1 would be shown as
`version 4.7.1.
`The major version field reflects the stage of the spec:
`0 = immature draft
`
`1 = draft which is at least 50% complete and has been presented / will shortly be presented to the responsible TSG for information
`
`2 = draft which is at least 80% complete and has been presented / will shortly be presented to the responsible TSG for approval
`
`3 or greater = spec which has been approved by the responsible TSG and is under change control.
`
`Once under change control, the major field indicates the Release to which the spec applies. Thus it is quite normal for a Release 7 specification to
`go, on TSG approval, from version 2.0.0 directly to version 7.0.0. There will be no versions 3.0.0, 4.0.0 etc between.
`The technical version field is incremented each time a technical change is made to the spec as a result of the drafting process (major version <=
`2) or as a result of the incorporation of one or more approved Change Requests (major version > 2).
`The editorial version field is incremented each time a non-technical change is made to the spec, for example to correct trivial typographical
`errors. Note that any change which could conceivably have an effect on the interpretation of the technical provisions of a spec cannot be
`considered as editorial. (Thus changing the greater-than symbol > into the less-than symbol <, although only the result of a mistyped character, is
`not considered editorial, since it makes a profound difference to the interpretation of the technical provisions of the document.) Exceptionally, the
`editorial version is used to show the replacement of a new version of a spec within the period (normally three working weeks) immediately
`following the end of a TSG meeting prior to the "all specs available" deadline, even though the modification might be more than purely editorial.
`Such circumstances cover, for example, the late availability of C code or TTCN associated with a spec. The document's change history annex will
`always explain the nature of any such change.
`
`The version number, consisting of the three numeric fields, is reflected in the filename of the TS or TR concerned. Each field is represented by a
`single character, and the mapping between version field value and the character representing that value in the filename is as shown in the table
`below:
`
`version field value
`0
`1
`2
`3
`4
`5
`6
`7
`8
`9
`
`filename character
`0
`1
`2
`3
`4
`5
`6
`7
`8
`9
`
`https://web.archive.org/web/20080912163040/http://www.3gpp.org/specs/version-numbering.htm
`
`1/2
`
`Samsung Ex. 1214, Page 1 of 2
`
`

`

`3GPP Specifications - Version numbering scheme
`Go AUG SEP OCT
`12
`2007 2008 2009
`
`👤 ⍰ ❎
`
`
`f 🐦
`▾ About this capture
`
`5/20/2020
`
`a
`10
`http://www.3gpp.org/specs/version-numbering.htm
`11
`b
`83 captures
`12
`c
`27 Nov 2005 - 12 Sep 2008
`13
`d
`14
`e
`15
`f
`16
`g
`17
`h
`18
`i
`19
`jh
`20
`k
`21
`l
`22
`m
`23
`n
`24
`o
`25
`p
`26
`q
`27
`r
`28
`s
`29
`t
`30
`u
`31
`v
`32
`w
`33
`x
`34
`y
`35
`z
`36 onwards
`for further study
`
`last updated:
`2005-07-21: original
`
`https://web.archive.org/web/20080912163040/http://www.3gpp.org/specs/version-numbering.htm
`
`2/2
`
`Samsung Ex. 1214, Page 2 of 2
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket