throbber
www.arcluvc.org
`·115.56 1.67(>7
`4 15.&<1~0391 c;-f:.x
`
`lmL-met .\ rchivc
`300 FUI'\S-f(ll'l Avc..nuc
`~n Franci.~(). CA 9 4118
`
`AFFIDAVIT OF CHRISTOPHER BUTLER
`
`I. I am the Otlice Manager at the Internet Archive, located in San Francisco,
`California. I make this declaration of my own personal knowledge.
`2. The Internet Archive is a website that provides access to a digital library of
`Internet sites and other cultural artifacts in digital forn1. Like a paper library, we provide
`fre.e access to researchers, historians, scholars, and the general pub! ic. The Internet
`Archive has partnered with and receives support from various institutions, including the
`Library of Congress.
`3. The Internet Archive has created a service known as the Way back Machine. The
`Wayback Machine makes it possible to surf more than 450 billion pages stored in the
`Internet Archive's web archive. Visitors to the Way back Machi ne can search archives
`by URL (i.e., a website address). If archived records for a URL are available, the visitor
`will be presented with a list of available dates. The visitor may select one of those
`dates, and then begin surfing on a n archived version of the Web. The links on the
`archived tiles, when served by the Wayback Machi ne, point to other archived files
`(whether HTML pages or images). If a visitor cl icks on a link on an archived page. the
`Wayback Machine will serve the archived file with the closest avai lable date to the page
`upon which the link appeared and was clicked.
`4. The archived data made viewable and browseable by the Wayback Machine is
`compi led using software programs known as crawlers. which surf the Web and
`automatical ly store copies of web files, preserving these fi les as they exist at the point of
`time of capture.
`5. The Internet Archive assigns a URL on its site to the archived fi les in the format
`http://web.archive.org/web/(Year in yyyy][Month in mm][Day in dd][Time code in
`hh:mm:ss]/[Archived URL). T hus, the Internet Archive URL
`http://web.archive.org/web/ 19970 126045828/http://www.archive.org/ would be the
`URL for the record of the Internet Archive home page HTML file
`(http://www.archive.org/) archived on January 26, 1997 at4:58 a.m . and 28 seconds
`(1997/01/26 at 04:58:28). A web browser may be set such that a printout from it will
`display the URL of a web page in the printout's footer. The date assigned by the Internet
`Archive appl ies to the HTML fi le but not to image Iiles linked therein. Thus images that
`appear on a page may not have been archived on the same date as the HTML file.
`Likewise, if a website is designed with "frames," the date assigned by the Internet
`Archive appl ies to the frameset as a whole. and not the ind ividual pages within each
`frame.
`6. Attached hereto as Exhibit A arc true and accurate copies of printouts of the
`Internet Archive's records of the HTML files for the URLs a nd the dates specified in the
`footer of the printout.
`7. Attached hereto as Exhibit Bare true and accurate copies of printouts of
`screenshots of the Internet Archive's calendar pages, which display the dates for which
`archi ved captures are available for the URL specified in the attached coversheet for each
`printout.
`8. I declare under penalty of perjury that the foregoing is true and correct.
`
`OA TE:
`
`I (1.v. [ {(o
`
`~r~~
`
`SAMSUNG 1018-0001
`
`

`
`Exhibit A
`
`
`
`SAMSUNG 1018-0002
`
`

`
`3GPP home page
`
`1 of 2
`
`Advanced search of 3GPP site.
`
`3GPP Search
`
`Shaping the future of mobile
`communication standards
`
`News & info
`
`2008-06-17: SA4#49 - election information
`
`2008-06-15: The latest TSG meeting highlights - CT/RAN/SA#40,
`GERAN#38
`
`2008-06-04: China TD-SCDMA Summit puts LTE on the agenda
`
`2008-05-29: Election for 1 Vice Chairman to be held in RAN2#62bis
`
`2008-04-30: New page documenting working agreements.
`
`2008-04-29: Voting list for SA4#49.
`
`2008-04-29: Recruitment of a Project Manager for the ETSI Centre
`for Testing and Interoperability to support the 3GPP community
`(Sophia Antipolis, FR)
`
`2008-04-11: News Release - Beyond 3G: “LTE-Advanced”
`Workshop, Shenzhen, China
`
`2008-04-01: At meeting number #42 CT5 decided to recommend that it
`be closed down and its remaining work transferred to OMA
`
`2008-01-05: Mapping table from NGN (fixed network) standards on
`core IMS from ETSI TISPAN to 3GPP
`
`Other News:
`
`New email account for Liaison Statements to 3GPP TSG/WG,
`3GPPLiaison@etsi.org
`UTRA-UTRAN Long Term Evolution and System Architecture
`Evolution
` What does the future hold for 3GPP technologies?
`Downloadable iCalendar files for each future meetings. See the last
`column of (for example) the TSG SA WG1 meetings page: click on ICS to
`have the meeting registered as an appointment in your personal calendar
`(eg MS Outlook). (Each TSG and WG has a dedicated web page,
`accessible from the 3GPP structure page. To see meetings information,
`use the link top right of the table on the TSG/WG page.)
`3GPP IETF Dependencies and Priorities
`Results of 3GPP Satisfaction survey 2006
`3GPP Support for Conferences
`
`https://web.archive.org/web/20080622021057/http://www.3gpp.org/
`
`SAMSUNG 1018-0003
`
`

`
`3GPP home page
`
`2 of 2
`
`Click here for access to the 3GPP ftp site
`
`Last update:
`2008-06-17
`
`Legal notice
`
`https://web.archive.org/web/20080622021057/http://www.3gpp.org/
`
`SAMSUNG 1018-0004
`
`

`
`3GPP Specifications - Numbering scheme
`
`1 of 3
`
`3GPP Specifications - 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
`
`All 3G and GSM specifications have a 3GPP specification number consisting of 4 or 5 digits. (e.g. 09.02 or 29.002). The first two digits define
`the series as listed in the table below. They are followed by 2 further digits for the 01 to 13 series or 3 further digits for the 21 to 55 series. The
`term "3G" means a 3GPP system using a UTRAN radio access network; the term "GSM" means a 3GPP system using a GERAN radio access
`network. (Thus "GSM" includes GPRS and EDGE features.)
`
`The full title, specification number and latest version number for every specification can be found in the current status list [warning: large file!]
`(see also main specs page for status lists pertaining to each TSG SA meeting) and more information about terms such as R99 and Rel-4 can be
`found on the Releases and phases page.
`
`A specification in the 21 to 35 series may apply either to 3G only or to GSM and 3G. A clue lies in the third digit, where a "0" indicates that it
`applies to both systems. For example, 29.002 applies to 3G and GSM systems whereas 25.101 and 25.201 apply only to 3G. Most specs in all
`other series apply only to GSM systems. However, as the spec numbering space has been used up, this guide is frequently broken, and it is
`necessary to examine the information page for each spec (see the table below) or to check the lists in 01.01 / 41.101 (GSM) and 21.101 (3G)
`for the definitive specification sets for each system and each Release.
`
`Subject of specification series
`
`3G/GSM R99 and
`later
`
`GSM only (Rel-4
`and later)
`
`General information (long defunct)
`Requirements
`Service aspects ("stage 1")
`Technical realization ("stage 2")
`Signalling protocols ("stage 3") - user equipment to
`network
`Radio aspects
`CODECs
`
`Data
`
`Signalling protocols ("stage 3") -(RSS-CN)
`Signalling protocols ("stage 3") - intra-fixed-network
`Programme management
`Subscriber Identity Module (SIM / USIM), IC Cards.
`Test specs.
`OAM&P and Charging
`Access requirements and test specifications
`Security aspects
`UE and (U)SIM test specifications
`Security algorithms (3)
`Evolved UTRA aspects
`
`21 series
`
`22 series
`
`23 series
`
`24 series
`
`25 series
`
`26 series
`
`27 series
`
`28 series
`
`29 series
`
`30 series
`
`31 series
`
`32 series
`
`33 series
`
`34 series
`
`35 series
`36 series
`
`GSM only
`(before Rel-4)
`00 series
`01 series
`
`02 series
`
`03 series
`
`04 series
`
`05 series
`
`06 series
`
`07 series
`
`08 series
`
`09 series
`
`10 series
`
`11 series
`
`12 series
`
`41 series
`
`42 series
`
`43 series
`
`44 series
`
`45 series
`
`46 series
`47 series (none
`exists)
`48 series
`
`49 series
`
`50 series
`
`51 series
`
`52 series
`
`13 series (1)
`
`13 series (1)
`
`(2)
`
`(2)
`
`55 series
`-
`
`(2)
`
`11 series
`
`(4)
`-
`
`Note (1): The 13 series GSM specifications relate to European-Union-specific regulatory standards. On the
`closure of ETSI TC SMG, responsibility for these specifications was transferred to ETSI TC MSG, (Mobile
`Specification Group) and they do not appear on the 3GPP file server.
`
`Note (2): The specifications of these aspects are spread throughout several series.
`
`Note (3): Algorithms may be subject to export licensing conditions. See the relevant 3GPP page. See also the
`relevant ETSI pages.
`
`Note (4): The original GSM algorithms are not published and are controlled by the GSM Association.
`
`https://web.archive.org/web/20080620005257/http://www.3gpp.org/specs/numbering.htm
`
`SAMSUNG 1018-0005
`
`

`
`3GPP Specifications - Numbering scheme
`
`2 of 3
`
`Missing Specs: Click here to see those Specs not yet available following the most recent round of TSG meetings.
`
`The 3GPP Specifications are stored on the file server as zipped MS-Word files. The filenames have the following structure:
` SM[-P[-Q]]-V.zip
`
`where the character fields have the following significance ...
`
`S = series number - 2 characters (see the table above)
`M = mantissa (the part of the spec number after the series number) - 2 or 3 characters (see above)
`P = optional part number - 1 or 2 digits if present
`Q = optional sub-part number - 1 or 2 digits if present
`V = version number, without separating dots - 3 digits
`
`So for example:
`21900-320.zip is 3GPP TR 21.900 version 3.2.0
`0408-6g0.zip is 3GPP TS 04.08 version 6.16.0
`32111-4-410 is 3GPP TS 32.111 part 4 version 4.1.0
`29998-04-1-100 is 3GPP TS 29.998 part 4 sub-part 1 version 1.0.0
`
`Further information:
`
`Latest version
`The latest versions of the approved specifications in the "latest" directory. The latest version of draft specs (i.e. those not yet under change control) are in the
`"latest-drafts" directory. See also the page on version numbering.
`
`Particular version
`All older versions of specifications (where available) are stored in the archive subdirectory. All versions of all releases of a given specification are placed directly
`under the name of the specification.
`
`Title or subject
`If you only know the title or the subject, but not the specification number, the best place to start looking is the complete list of all 3GPP specification numbers
`and titles. This list also shows the most recent version in each Release.
`
`Specs related to a particular working group
`Each 3GPP TSG Working Group has a home page, which lists the specifications under its responsibility. Follow the links from here....
`
`Official versions published by recognized Standards Development Organizations
`The 3GPP Technical Specifications (and Technical Reports) which are publicly available from this site have, in themselves, no legal standing. They only
`become "official" when transposed into corresponding publications of the Partner Organizations. If you are looking for the official versions, see the official
`publications page.
`
`Yet more information:
`
`Work plan. The 3GPP Work plan describes the new functionality currently being elaborated in the TSG working groups. It also indicates the expected
`timescales for their finalization.
`
`Releases (and phases, stages). An introduction to the 3GPP mechanism for specifications releases can be found here.
`
`Historical information. If you need to look for old / superseded specifications or change requests, start here.
`
`TSG working methods. The procedures for creating, enhancing and maintaining specifications are described in TR 21.900. A
`presentation outlining the release and change request process can be found here.
`
`3GPP Drafting rules. The rules for drafting specifications are described in TR 21.801.
`
`Change Requests (CRs). The change request mechanism is used when a correction or new functionality is required for an existing specification. Here
`you can find all information related to change requests.
`
`Version numbering. More information on the version numbering page.
`
`last updated:
`2008-01-28: Link to missing specs page added.
`2006-09-04: 36.- series added.
`2005-08-05: Title for table entry 32/52/12.- series changed from "O&M".
`2005-07-29: Title for 34.-series changed from "(U)SIM test specs" to add "UE" as well.
`2005-07-21: corrects hyperlink to TB chart; adds links to info on version numbering
`2004-08-02: missing bracket inserted
`2004-03-02: typo in hyperlink to 45-series specs corrected.
`2003-10-21: "further information" section originally in main specs page transferred to this page; sundry editorial improvements.
`2003-09-10: links to current status list and to spec numbering system added.
`2003-07-10: minor editorial clarifications
`
`https://web.archive.org/web/20080620005257/http://www.3gpp.org/specs/numbering.htm
`
`SAMSUNG 1018-0006
`
`

`
`3GPP Specifications - Numbering scheme
`
`3 of 3
`
`2003-06-27: 00.-series added to table; URLs to spec lists made relative rather than absolute (to aid site mirroring)
`2003-09-26: minor corrections and clarifications
`2003-04-24: links to specs series indexes added
`2002-10-10: mention of 55 series specs added, plus notes 3 & 4.
`
`https://web.archive.org/web/20080620005257/http://www.3gpp.org/specs/numbering.htm
`
`SAMSUNG 1018-0007
`
`

`
`3GPP specification series: 36series
`
`1 of 3
`
`3GPP Specification series
`
`Back to numbering scheme page
`
`Click on spec number for details
`
`TS 36.101
`
`TS 36.104
`
`TS 36.106
`
`TS 36.113
`
`TS 36.124
`
`TS 36.133
`
`TS 36.141
`
`TS 36.143
`
`TS 36.201
`
`TS 36.211
`
`TS 36.212
`
`TS 36.213
`TS 36.214
`
`TS 36.300
`
`TS 36.302
`
`TS 36.304
`
`TS 36.306
`
`TS 36.314
`
`TS 36.321
`
`TS 36.322
`
`TS 36.323
`
`TS 36.331
`
`TS 36.401
`
`TS 36.410
`
`TS 36.411
`
`TS 36.412
`
`Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio
`transmission and reception
`Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio
`transmission and reception
`Evolved Universal Terrestrial Radio Access (E-UTRA); Rrepeater radio transmission
`and reception
`Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) and repeater
`ElectroMagnetic Compatibility (EMC)
`Evolved Universal Terrestrial Radio Access (E-UTRA); Electromagnetic compatibility
`(EMC) requirements for mobile terminals and ancillary equipment
`Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of
`radio resource management
`Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) conformance
`testing
`Evolved Universal Terrestrial Radio Access (E-UTRA); Repeater conformance testing
`Evolved Universal Terrestrial Radio Access (E-UTRA); Long Term Evolution (LTE)
`physical layer; General description
`Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and
`modulation
`Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel
`coding
`Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures
`Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer - Measurements
`Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
`Terrestrial Radio Access (E-UTRAN); Overall description; Stage 2
`Evolved Universal Terrestrial Radio Access (E-UTRA); Services provided by the
`physical layer
`Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
`procedures in idle mode
`Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio
`access capabilities
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Layer 2 -
`Measurements
`Evolved Universal Terrestrial Radio Accesss (E-UTRA); Medium Acces Control (MAC)
`protocol specification
`Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC)
`protocol specification
`Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence
`Protocol (PDCP) specification
`Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC);
`Protocol specification
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture
`description
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 layer 1 general
`aspects and principles
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 layer 1
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 signalling
`transport
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`https://web.archive.org/web/20080621102500/http://www.3gpp.org/ftp/Specs/html-info/36-series.htm
`
`SAMSUNG 1018-0008
`
`

`
`3GPP specification series: 36series
`
`2 of 3
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`Evolved Universal Terrestrial Radio Access (E-UTRA) ; S1 Application Protocol (S1AP) .
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 data transport
`.
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 general aspects
`and principles
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 layer 1
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 signalling
`transport
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application
`Protocol (X2AP)
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 data transport
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); General aspects and
`principles for interfaces supporting Multimedia Broadcast Multicast Service (MBMS)
`within E-UTRAN
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Layer 1 for interfaces
`supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Signalling Transport
`for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within
`E-UTRAN
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M2 Application
`Protocol (M2AP)
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M3 Application
`Protocol (M3AP)
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M1 Data Transport
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M1 User Plane
`protocol
`Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
`Terrestrial Radio Access Network (E-UTRAN); Common test environments for User
`Equipment (UE) conformance testing
`Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
`Terrestrial Radio Access Network (E-UTRAN); Terminal logical test interface; Special
`conformance testing functions
`Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
`Terrestrial Radio Access Network (E-UTRAN); User Equipment (UE) conformance
`specification; Radio transmission and reception Part 1: conformance testing
`Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
`Terrestrial Radio Access Network (E-UTRAN); User Equipment (UE) conformance
`specification; Radio transmission and reception Part 2: ICS
`Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
`Terrestrial Radio Access Network (E-UTRAN); User Equipment (UE) conformance
`specification; Part 1: Protocol conformance specification
`Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
`Terrestrial Radio Access Network (E-UTRAN); User Equipment (UE) conformance
`specification; Part 2: ICS
`Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
`Terrestrial Radio Access Network (E-UTRAN); User Equipment (UE) conformance
`specification; Part 3: Abstract Test Suites (ATS)
`Evolved Universal Terrestrial Radio Access (E-UTRA); Measurement Requirements
`Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio
`transmission and reception
`Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio
`transmission and reception
`Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Self-configuring and
`self-optimizing network (SON) use cases and solutions
`Requirements for further advancements for E-UTRA (LTE-Advanced)
`
`TS 36.413
`TS 36.414
`
`TS 36.420
`
`TS 36.421
`
`TS 36.422
`
`TS 36.423
`
`TS 36.424
`
`TS 36.440
`
`TS 36.441
`
`TS 36.442
`
`TS 36.443
`
`TS 36.444
`
`TS 36.445
`
`TS 36.446
`
`TS 36.508
`
`TS 36.509
`
`TS 36.521-1
`
`TS 36.521-2
`
`TS 36.523-1
`
`TS 36.523-2
`
`TS 36.523-3
`
`TR 36.801
`
`TR 36.803
`
`TR 36.804
`
`TR 36.902
`
`TR 36.913
`
`https://web.archive.org/web/20080621102500/http://www.3gpp.org/ftp/Specs/html-info/36-series.htm
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`SAMSUNG 1018-0009
`
`

`
`3GPP specification series: 36series
`
`3 of 3
`
`TR 36.938
`
`TR 36.942
`
`TR 36.956
`
`Improved network controlled mobility between LTE and 3GPP2/mobile WiMAX radio
`technologies
`Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Frequency (RF) system
`scenarios
`Evolved Universal Terrestrial Radio Access (E-UTRA); Repeater planning guidelines
`and system analysis
`
`.
`
`.
`
`.
`
`page generated from database: 2008-06-18 17:42:56
`
`https://web.archive.org/web/20080621102500/http://www.3gpp.org/ftp/Specs/html-info/36-series.htm
`
`SAMSUNG 1018-0010
`
`

`
`3GPP specification: 36.321
`
`1 of 1
`
`3GPP Specification detail
`
`Back to numbering scheme page
`
`Back to series index
`
`3GPP TS 36.321 (click spec number to see fileserver directory for this spec)
`Evolved Universal Terrestrial Radio Accesss (E-UTRA); Medium Acces Control (MAC)
`protocol specification
`
`. T
`
`SG / WG responsible: R2 (click TSG/WG to see its home page)
`
`Work item which gave rise to this spec: LTE-L23 (click WI code to see Work Item details in the Work Plan)
`
`Work items which may have impacted this spec: click here
`
`Rapporteur: LINDSTRÖM, Magnus
`
`Specification required for: E-UTRAN-based systems
`
`In the table below ...
`
`... click meeting number for meeting details;
`
`... click spec version number to download that version;
`
`... click SDO publication reference to download SDO transposed document.
`
`Release Freeze meeting
`
`Freeze date
`
`remarks
`
`Rel-8
`
`event
`
`RP-37
`
`RP-38
`
`RP-38
`
`RP-39
`
`RP-40
`
`-
`
`. .
`
`version
`
`available
`
`remarks
`
`1.0.0
`
`2.0.0
`
`8.0.0
`
`8.1.0
`
`8.2.0
`
`2007-09-24 RP-070688
`
`2007-12-11 RP-070917
`
`2007-12-20
`
`2008-03-20
`
`2008-06-17
`
`Change Requests for this spec: click here.
`
`Genealogy of this spec:
`
`antecedent(s)
`(no antecedents)
`
`this spec
`36.321
`
`descendant(s)
`(no descendants)
`
`page generated from database: 2008-06-30 17:22:43
`
`SDO publications
`
`ETSI
`
`click ref to download
`
`-
`
`-
`
`-
`
`-
`
`-
`
`https://web.archive.org/web/20080701220445/http://www.3gpp.org/ftp/Specs/html-info/36321.htm
`
`SAMSUNG 1018-0011
`
`

`
`3GPP home page
`
`1 of 2
`
`Advanced search of 3GPP site.
`
`3GPP Search
`
`Shaping the future of mobile
`communication standards
`
`News & info
`
`2008-06-30: Kari Järvinen re-elected Chairman and Stéphane
`Ragot elected Vice Chairman of TSG SA WG 4
`
`2008-06-30: Etienne Chaponniere elected Vice Chairman of TSG
`RAN WG 2
`
`2008-06-15: The latest TSG meeting highlights - CT/RAN/SA#40,
`GERAN#38
`
`2008-06-04: China TD-SCDMA Summit puts LTE on the agenda
`
`2008-04-30: New page documenting working agreements.
`
`2008-04-29: Recruitment of a Project Manager for the ETSI Centre
`for Testing and Interoperability to support the 3GPP community
`(Sophia Antipolis, FR)
`
`2008-04-11: News Release - Beyond 3G: “LTE-Advanced”
`Workshop, Shenzhen, China
`
`2008-04-01: At meeting number #42 CT5 decided to recommend that it
`be closed down and its remaining work transferred to OMA
`
`2008-01-05: Mapping table from NGN (fixed network) standards on
`core IMS from ETSI TISPAN to 3GPP
`
`Other News:
`
`New email account for Liaison Statements to 3GPP TSG/WG,
`3GPPLiaison@etsi.org
`UTRA-UTRAN Long Term Evolution and System Architecture
`Evolution
` What does the future hold for 3GPP technologies?
`Downloadable iCalendar files for each future meetings. See the last
`column of (for example) the TSG SA WG1 meetings page: click on ICS to
`have the meeting registered as an appointment in your personal calendar
`(eg MS Outlook). (Each TSG and WG has a dedicated web page,
`accessible from the 3GPP structure page. To see meetings information,
`use the link top right of the table on the TSG/WG page.)
`3GPP IETF Dependencies and Priorities
`Results of 3GPP Satisfaction survey 2006
`3GPP Support for Conferences
`
`https://web.archive.org/web/20080706091123/http://www.3gpp.org/
`
`SAMSUNG 1018-0012
`
`

`
`3GPP home page
`
`2 of 2
`
`Click here for access to the 3GPP ftp site
`
`Last update:
`2008-06-30
`
`Legal notice
`
`https://web.archive.org/web/20080706091123/http://www.3gpp.org/
`
`SAMSUNG 1018-0013
`
`

`
`Full details of all 3GPP Meetings
`
`1 of 1
`
`Advanced search of 3GPP site.
`
`3GPP Search
`
`3GPP meetings
`
`Meeting Calendar | Meeting documents | Meetings at ETSI | Hosting a meeting | 3GPP-endorsed Conferences
`
`Note that the meetings of TSGs CN and T and their working groups have become meetings of TSG CT and its working groups and RAN5 from
`mid-March 2005 onwards. See the current TSG structure.
`
`For comprehensive information on past and future information, see also the "meetings" links on the home pages of each TSG and WG,
`accessible via the current TSG structure.
`
`3GPP
`
`Full 3GPP
`meeting
`calendar
`including
`workshops
`
`PCG/OP
`
`CN
`All CN
`
`CN Plenary
`
`GERAN
`All GERAN
`
`GERAN
`Plenary
`
`GERAN WG1
`
`GERAN WG2
`
`GERAN WG3
`
`Meeting Calendar
`RAN
`All RAN
`
`All SA
`
`SA
`
`T
`
`All T
`
`CT
`
`All CT
`
`RAN Plenary
`
`SA Plenary
`
`T Plenary
`
`CT Plenary
`
`RAN WG1
`
`RAN WG2
`
`RAN WG3
`
`RAN WG4
`
`RAN WG5
`
`SA WG1
`
`SA WG2
`
`SA WG3
`
`SA WG4
`
`SA WG5
`
`CT WG1
`
`CT WG2
`
`CT WG3
`
`CT WG4
`
`CT WG5
`
`CT WG6
`
`Register for 3GPP meetings
`
`Information for meetings held in the Sophia Antipolis area
`
`How do I use on-line registration?
`
`3GPP
`
`CN
`CN Plenary
`
`GERAN
`ALL GERAN
`
`Meeting Documents
`RAN
`RAN Plenary
`
`SA
`SA Plenary
`
`T
`T Plenary
`
`CT
`CT Plenary
`
`GERAN
`WG3new
`TTCN
`
`CN WG1
`
`CN WG2
`
`CN WG3
`
`CN WG4
`
`CN WG5
`
`RAN WG1
`
`SA WG1
`
`RAN WG 2
`
`SA WG2
`
`RAN WG 3
`
`SA WG3
`
`RAN WG 4
`
`SA WG4
`
`RAN WG5
`
`SA WG5
`
`T WG1
`
`T WG2
`
`T WG3
`
`Text to be used in the call for IPRs during each 3GPP meeting
`
`CT WG1
`
`CT WG2
`
`CT WG3
`
`CT WG4
`
`CT WG5
`
`CT WG6
`
`PCG
`
`OP
`
`FFG
`
`Workshops
`
`Invitations
`
`Last update:
`2006-06-14: Top-of-page hyperlinks updated.
`2006-05-10: Top-of-page link to 3GPP-endorsed Conferences added; minor editorial change.
`2005-09-22
`
`https://web.archive.org/web/20080706133900/http://www.3gpp.org/Meetings/meetings.htm
`
`SAMSUNG 1018-0014
`
`

`
`www.3gpp.org - /ftp/tsg_ran/WG2_RL2/
`
`1 of 2
`
`www.3gpp.org - /ftp/tsg_ran/WG2_RL2/
`
`[To Parent Directory]
`
` 29 March 2007 22:17 <dir> Change_Requests
` 29 March 2007 22:17 <dir> Invitation
` 17 June 2008 00:31 <dir> Org
` 22 February 2008 15:19 <dir> Outgoing_Liaisons
` 30 April 2004 14:00 95515 R2_1999.zip
` 21 December 2000 20:03 120168 R2_2000.zip
` 04 January 2002 19:12 137260 R2_2001.zip
` 21 January 2003 15:07 160005 R2_2002.zip
` 24 November 2003 11:08 124992 R2_2003.zip
` 01 December 2004 10:45 141308 R2_2004.zip
` 14 November 2005 13:57 175578 R2_2005.zip
` 14 May 2008 12:21 <dir> Specifications
` 29 March 2007 22:18 <dir> TSGR2_01
` 29 March 2007 22:18 <dir> TSGR2_02
` 29 March 2007 22:18 <dir> TSGR2_03
` 29 March 2007 22:18 <dir> TSGR2_04
` 29 March 2007 22:18 <dir> TSGR2_05
` 29 March 2007 22:19 <dir> TSGR2_06
` 29 March 2007 22:19 <dir> TSGR2_07
` 29 March 2007 22:19 <dir> TSGR2_08
` 29 March 2007 22:19 <dir> TSGR2_09
` 29 March 2007 22:20 <dir> TSGR2_10
` 29 March 2007 22:20 <dir> TSGR2_11
` 29 March 2007 22:20 <dir> TSGR2_12
` 29 March 2007 22:20 <dir> TSGR2_13
` 29 March 2007 22:20 <dir> TSGR2_14
` 29 March 2007 22:21 <dir> TSGR2_15
` 29 March 2007 22:21 <dir> TSGR2_16
` 29 March 2007 22:21 <dir> TSGR2_17
` 29 March 2007 22:21 <dir> TSGR2_18
` 29 March 2007 22:22 <dir> TSGR2_19
` 29 March 2007 22:22 <dir> TSGR2_20
` 29 March 2007 22:22 <dir> TSGR2_21
` 29 March 2007 22:22 <dir> TSGR2_22
` 29 March 2007 22:23 <dir> TSGR2_23
` 29 March 2007 22:23 <dir> TSGR2_24
` 29 March 2007 22:23 <dir> TSGR2_25
` 29 March 2007 22:23 <dir> TSGR2_26
` 29 March 2007 22:24 <dir> TSGR2_27
` 29 March 2007 22:24 <dir> TSGR2_28
` 29 March 2007 22:24 <dir> TSGR2_29
` 29 March 2007 22:24 <dir> TSGR2_30
` 29 March 2007 22:25 <dir> TSGR2_31
` 29 March 2007 22:25 <dir> TSGR2_32
` 29 March 2007 22:25 <dir> TSGR2_33
` 29 March 2007 22:26 <dir> TSGR2_34
` 29 March 2007 22:26 <dir> TSGR2_35
` 29 March 2007 22:26 <dir> TSGR2_36
` 29 March 2007 22:27 <dir> TSGR2_37
` 29 March 2007 22:27 <dir> TSGR2_38
` 29 March 2007 22:27 <dir> TSGR2_39
` 29 March 2007 22:27 <dir> TSGR2_40
` 29 March 2007 22:28 <dir> TSGR2_41
` 29 March 2007 22:28 <dir> TSGR2_42
` 29 March 2007 22:28 <dir> TSGR2_43
` 29 March 2007 22:28 <dir> TSGR2_44
` 29 March 2007 22:29 <dir> TSGR2_45
` 29 March 2007 22:29 <dir> TSGR2_45bis
` 29 March 2007 22:29 <dir> TSGR2_46
` 29 March 2007 22:30 <dir> TSGR2_46bis
` 29 March 2007 22:30 <dir> TSGR2_47
` 29 March 2007 22:30 <dir> TSGR2_48
` 29 March 2007 22:31 <dir> TSGR2_48bis
` 29 March 2007 22:31 <dir> TSGR2_49
` 29 March 2007 22:31 <dir> TSGR2_50
` 29 March 2007 22:31 <dir> TSGR2_51
`
`https://web.archive.org/web/20080705223358/http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/
`
`SAMSUNG 1018-0015
`
`

`
`www.3gpp.org - /ftp/tsg_ran/WG2_RL2/
`
`2 of 2
`
` 29 March 2007 22:32 <dir> TSGR2_52
` 29 March 2007 22:32 <dir> TSGR2_53
` 29 March 2007 22:33 <dir> TSGR2_54
` 29 March 2007 22:33 <dir> TSGR2_55
` 29 March 2007 22:33 <dir> TSGR2_56
` 29 March 2007 22:34 <dir> TSGR2_56bis
` 29 March 2007 22:34 <dir> TSGR2_57
` 29 March 2007 22:34 <dir> TSGR2_57bis
` 09 May 2007 10:47 <dir> TSGR2_58
` 23 June 2007 01:50 <dir> TSGR2_58bis
` 18 August 2007 09:40 <dir> TSGR2_59
` 03 October 2007 12:06 <dir> TSGR2_59bis
` 17 February 2008 16:03 <dir> TSGR2_60
` 04 February 2008 03:41 <dir> TSGR2_60bis
` 08 February 2008 16:36 <dir> TSGR2_61
` 19 March 2008 10:02 <dir> TSGR2_61bis
` 21 April 2008 21:28 <dir> TSGR2_62
` 14 June 2008 22:07 <dir> TSGR2_62bis
` 11 June 2008 12:13 <dir> TSGR2_63
` 11 June 2008 12:13 <dir> TSGR2_63bis
` 10 April 2008 17:48 <dir> TSGR2_AHs
`
`https://web.archive.org/web/20080705223358/http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/
`
`SAMSUNG 1018-0016
`
`

`
`www.3gpp.org - /ftp/tsg_ran/WG2_RL2/TSGR2_62bis/
`
`1 of 1
`
`www.3gpp.org - /ftp/tsg_ran/WG2_RL2/TSGR2_62bis/
`
`[To Parent Directory]
`
` 14 June 2008 22:03 <dir> Agenda
` 02 July 2008 08:28 <dir> Docs
` 14 June 2008 22:02 <dir> Invitation
` 02 July 2008 08:29 <dir> LSin
` 02 July 2008 08:30 <dir> LSout
` 27 June 2008 17:42 <dir> Report
` 27 June 2008 17:42 <dir> Tdoclist
`
`https://web.archive.org/web/20080703060124/http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_62bis/
`
`SAMSUNG 1018-0017
`
`

`
`www.3gpp.org - /ftp/tsg_ran/WG2_RL2/TSGR2_

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