Document List for 3GPPSA1#49
List generated on : 2010-02-11 at 10:27:52 (GMT +01:00)

DOCUMENT: Agenda Draft 1
Doc.Name S1-100000 Allocations: Content Type:
File Name: S1-100000.zip
Source: TB Chairman
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Agenda Draft 2
Doc.Name S1-100001 Allocations: Content Type:
File Name: S1-100001.zip
Source: TB Chairman
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Agenda Draft 3
Doc.Name S1-100002 Allocations: Content Type:
File Name: S1-100002.zip
Source: TB Chairman
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Agenda
Doc.Name S1-100003 Allocations: Content Type:
File Name: S1-100003.zip
Source: TB Chairman
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Draft Minutes of SA1#48
Doc.Name S1-100004 Allocations: Content Type:
File Name: S1-100004.zip
Source: ETSI Secretariat
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Final Minutes of SA1#48
Doc.Name S1-100005 Allocations: Content Type:
File Name: S1-100005.zip
Source: ETSI Secretariat
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Extract for SA1#49 of the 3GPP Work Plan
Doc.Name S1-100006 Allocations: Content Type:
File Name: S1-100006.zip
Source: ETSI Secretariat
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Additional OA&M Requirement for Enterprise H(e)NB
Doc.Name S1-100007 Allocations: Content Type:
File Name: S1-100007.zip
Source: Verizon Wireless
Abstract: This CR adds a new requirement for OA&M for Enterprise H(e)NB
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: QoS Requirement for Enterprise H(e)NB
Doc.Name S1-100008 Allocations: Content Type:
File Name: S1-100008.zip
Source: Verizon Wireless
Abstract: The CR to TS 22.220 adds a QoS requirement for Enterprise H(e)NB
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: CR to 22.220: Mobility for Local IP Access (LIPA)
Doc.Name S1-100009 Allocations: Content Type:
File Name: S1-100009.zip
Source: Vodafone, Samsung, Verizon Wireless, TeliaSonera
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Clarification on ICS wrt data (CS) and fax (CR to 22.101)
Doc.Name S1-100010 Allocations: Content Type:
File Name: S1-100010.zip
Source: Ericsson, Vodafone
Abstract: The media components fax and CS data is supported in ICS so that it is possible
for an operator to support the CS services Fax and CS Data in legacy UEs while t
he control is handled by IMS.

Since the UE is a legacy UE it is not expected that the media components fax and
data (CS) is supported.
Service continuity between the CS services Fax and CS data and the media compone
nts fax and data (CS) in IMS Multimedia services is also not needed since the UE
is not expected to support IMS as such
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: CR to 22.101: SIPTO requirements common for macro network an
d H(e)NB subsystems
Doc.Name S1-100011 Allocations: Content Type:
File Name: S1-100011.zip
Source: Vodafone, Verizon Wireless, Cisco, Samsung
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: CR to 22.220: Removal of SIPTO common requirements
Doc.Name S1-100012 Allocations: Content Type:
File Name: S1-100012.zip
Source: Vodafone, Verizon Wireless, Cisco, Samsung
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: CR to 22.220: Termination of data session
Doc.Name S1-100013 Allocations: Content Type:
File Name: S1-100013.zip
Source: Vodafone
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Clarification on ICS wrt data (CS) and fax (CR to 22.173)
Doc.Name S1-100014 Allocations: Content Type:
File Name: S1-100014.zip
Source: Ericsson, Vodafone
Abstract: Some IMS supplementary services can not be used together with the IMS Multimedia
Telephony using fax and CS data media components. This is similar to the differ
ences between the CS services Fax and CS Data verses CS Speech (TS 11) that can
be found in Appendix A of TS 22.004.

The CR clarifies that the IMS supplementary services Hold, Explicit Communicatio
n Transfer and Conference are not applicable IMS Multimedia Telephony with the d
ata (CS) and fax media components.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Revisiting requirements on theft and vandalism use case in T
S23.368
Doc.Name S1-100015 Allocations: Content Type:
File Name: S1-100015.zip
Source: InterDigital Communications, LLC; Oscar Lopez-Torres
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Discussion on content-based service category for Machine Typ
e Communication (MTC)
Doc.Name S1-100016 Allocations: Content Type:
File Name: S1-100016.zip
Source: Alcatel-Lucent Shanghai Bell, Alcatel-Lucent
Abstract: This paper discuss a new content-based service category for MTC
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Discussion on high correlation service category for Machine
Type Communication (MTC)
Doc.Name S1-100017 Allocations: Content Type:
File Name: S1-100017.zip
Source: Alcatel-Lucent Shanghai Bell, Alcatel-Lucent
Abstract: In this contribution, we discuss new high correlation service categories for mac
hine-type communication.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Discussion on high scalability service category for Machine
Type Communication (MTC)
Doc.Name S1-100018 Allocations: Content Type:
File Name: S1-100018.zip
Source: Alcatel-Lucent Shanghai Bell, Alcatel-Lucent
Abstract: In this contribution, we discuss new high scalability service categories for mac
hine-type communication.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Discussion on location based service category for Machine Ty
pe Communication (MTC)
Doc.Name S1-100019 Allocations: Content Type:
File Name: S1-100019.zip
Source: Alcatel-Lucent Shanghai Bell, Alcatel-Lucent
Abstract: In this contribution, we discuss new location based service categories for machi
ne-type communication.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Proposed Event Detection and Reporting Use Case in Annex A a
nd proposed requirements
Doc.Name S1-100020 Allocations: Content Type:
File Name: S1-100020.zip
Source: Alcatel-Lucent Shanghai Bell, Alcatel-Lucent
Abstract: This contribution proposes a specific MTC service requirement for the device aut
omatically detecting an application-specific event and report reliably to the se
rver. A Use Case in Annex A reflecting the event detection and reporting is adde
d.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Discussion paper -SSAC for CSFB-
Doc.Name S1-100021 Allocations: Content Type:
File Name: S1-100021.zip
Source: NTT DOCOMO
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: SSAC for CSFB
Doc.Name S1-100022 Allocations: Content Type:
File Name: S1-100022.zip
Source: NTT DOCOMO
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: UICC/USIM enhancements Study Item : use cases
Doc.Name S1-100023 Allocations: Content Type:
File Name: S1-100023.zip
Source: Rapporteur
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: UICC/USIM enhancements Study Item : GSMA Smart SIM project d
eliverables
Doc.Name S1-100024 Allocations: Content Type:
File Name: S1-100024.zip
Source: Rapporteur
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: H(e)NB Hosting Party USIM management mirror
Doc.Name S1-100025 Allocations: Content Type:
File Name: S1-100025.zip
Source: Gemalto, Orange, Teliasonera, Giesecke & Devrient, Sagem Orga, Oberthur Technolo
gies
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Clarification on USIM storing provisioning parameters
Doc.Name S1-100026 Allocations: Content Type:
File Name: S1-100026.zip
Source: Gemalto, China Mobile, Telecom Italia, at&t, Sagem Orga, Oberthur
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Clarification on USIM storing provisioning parameters
Doc.Name S1-100027 Allocations: Content Type:
File Name: S1-100027.zip
Source: Gemalto, China Mobile, Telecom Italia, at&t, Sagem Orga, Oberthur
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: H(e)NB location verification
Doc.Name S1-100028 Allocations: Content Type:
File Name: S1-100028.zip
Source: Gemalto
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Replace 'MTC device' with 'MTC Equipment'
Doc.Name S1-100029 Allocations: Content Type:
File Name: S1-100029.zip
Source: Gemalto
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: CSG priority
Doc.Name S1-100030 Allocations: Content Type:
File Name: S1-100030.zip
Source: Gemalto, Sagem Orga
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Clarification on Allowed CSG List usage
Doc.Name S1-100031 Allocations: Content Type:
File Name: S1-100031.zip
Source: Gemalto, Telecom Italia, Sagem Orga
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Definition of IMS Multimedia Telephony
Doc.Name S1-100032 Allocations: Content Type:
File Name: S1-100032.zip
Source: France Telecom
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Remove Editor Note in Jamming Section
Doc.Name S1-100033 Allocations: Content Type:
File Name: S1-100033.zip
Source: Sierra Wireless
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Remove Editor Note in Addressing Section
Doc.Name S1-100034 Allocations: Content Type:
File Name: S1-100034.zip
Source: Sierra Wireless
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: 7.1.1 Generalize Peak Load Requirement
Doc.Name S1-100035 Allocations: Content Type:
File Name: S1-100035.zip
Source: Sierra Wireless
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: 7.2.5 and 7.2.5 Offline and Online clarifications
Doc.Name S1-100036 Allocations: Content Type:
File Name: S1-100036.zip
Source: Sierra Wireless
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: IPv6 support for Enterprise H(e)NB
Doc.Name S1-100037 Allocations: Content Type:
File Name: S1-100037.zip
Source: Verizon Wireless
Abstract: This CR adds a requirement for support of IPv6 in Enterprise H(e)NB.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Contribution to TS 22.368: MTC Feature Identification Requir
ements
Doc.Name S1-100038 Allocations: Content Type:
File Name: S1-100038.zip
Source: Qualcomm Incorporated
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: NOVES skeleton TR (proposed)
Doc.Name S1-100039 Allocations: Content Type:
File Name: S1-100039.zip
Source: Qualcomm Incorporated
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Discussion paper on Non-Voice Emergency Services
Doc.Name S1-100040 Allocations: Content Type:
File Name: S1-100040.zip
Source: Qualcomm Incorporated
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: TS 22.238 A modification on chapter 7.2.12 PAM
Doc.Name S1-100041 Allocations: Content Type:
File Name: S1-100041.zip
Source: China Mobile
Abstract: The term of “optimization categories “should be replaced with “MTC Feature
s” to align with other parts of TS 22.368.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: TS 22.368 Chapter 7.1.3 Identifies Clarification on MTC Devi
ce
Doc.Name S1-100042 Allocations: Content Type:
File Name: S1-100042.zip
Source: China Mobile
Abstract: This document clarifies that the requirement for MTC related to identifiers shal
l include MTC Device, not the ME.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Requirement for TS 22.368 Chapter 7.1.3: PS only
Doc.Name S1-100043 Allocations: Content Type:
File Name: S1-100043.zip
Source: China Mobile
Abstract: This contribution proposes text for an additional clause to the PS Only requirem
ent in the NIMTC TS
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Add VPLMN CSG support
Doc.Name S1-100044 Allocations: Content Type:
File Name: S1-100044.zip
Source: Deutsche Telekom
Abstract: It is proposed to add new text for VPLMN CSG lists in TS 22.220 section 5.3.1
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: IP interconnect
Doc.Name S1-100045 Allocations: Content Type:
File Name: S1-100045.zip
Source: Vodafone
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: TS22.368: 7.1.3 MTC Group
Doc.Name S1-100046 Allocations: Content Type:
File Name: S1-100046.zip
Source: Samsung, China Mobile, KPN, Vodafone, NSN, ZTE, Panasonic
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: TS22.368: 7.2.8 & 7.2.10 merging monitoring related MTC Feat
ures
Doc.Name S1-100047 Allocations: Content Type:
File Name: S1-100047.zip
Source: Samsung, Telecom Italia, KPN, Vodafone, NSN, ZTE, Ericsson
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: TS22.368: 7.2.11 Jamming Indication
Doc.Name S1-100048 Allocations: Content Type:
File Name: S1-100048.zip
Source: Samsung
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: TS22.368: 7.2.13 Extra Low Power Consumption
Doc.Name S1-100049 Allocations: Content Type:
File Name: S1-100049.zip
Source: Samsung
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: TS22.368: 7.2.7 Mobile Originated Only
Doc.Name S1-100050 Allocations: Content Type:
File Name: S1-100050.zip
Source: Samsung, NSN, Vodafone
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Contribution to 22.368 - Annex A
Doc.Name S1-100051 Allocations: Content Type:
File Name: S1-100051.zip
Source: ZTE,KPN, China Mobile, NSN, Samsung
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Conclusion of IMS based P2P CDS
Doc.Name S1-100052 Allocations: Content Type:
File Name: S1-100052.zip
Source: China Mobile, ZTE
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Peer Definition of IMS based P2P CDS
Doc.Name S1-100053 Allocations: Content Type:
File Name: S1-100053.zip
Source: China Mobile, ZTE
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: service requirements for continued downloading
Doc.Name S1-100054 Allocations: Content Type:
File Name: S1-100054.zip
Source: China Mobile, ZTE
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Use case - continued downloading
Doc.Name S1-100055 Allocations: Content Type:
File Name: S1-100055.zip
Source: China Mobile, ZTE
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Comparison of Different Access Networks
Doc.Name S1-100056 Allocations: Content Type:
File Name: S1-100056.zip
Source: ZTE, China Mobile
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Mobility considerations of the access network
Doc.Name S1-100057 Allocations: Content Type:
File Name: S1-100057.zip
Source: ZTE, China Mobile
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Proposed network peer deployment based on types of access ne
twork
Doc.Name S1-100058 Allocations: Content Type:
File Name: S1-100058.zip
Source: ZTE, China Mobile
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Proposed service requirements for user peer selection based
on bandwidth
Doc.Name S1-100059 Allocations: Content Type:
File Name: S1-100059.zip
Source: ZTE, China Mobile
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Proposed service requirements for user peer selection based
on mobility
Doc.Name S1-100060 Allocations: Content Type:
File Name: S1-100060.zip
Source: ZTE, China Mobile
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Proposed service requirements for user peer selection based
on transmission cost
Doc.Name S1-100061 Allocations: Content Type:
File Name: S1-100061.zip
Source: ZTE, China Mobile
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Transmission cost of the access network and inter-operator t
raffic
Doc.Name S1-100062 Allocations: Content Type:
File Name: S1-100062.zip
Source: ZTE, China Mobile
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Upload&download bandwidth of the access network
Doc.Name S1-100063 Allocations: Content Type:
File Name: S1-100063.zip
Source: ZTE, China Mobile
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: CR to 22.220 - Modification of requirements on H(e)NBs in en
terprise environments
Doc.Name S1-100064 Allocations: Content Type:
File Name: S1-100064.zip
Source: NEC ...
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: CR to 22.220 - Managed Remote Access
Doc.Name S1-100065 Allocations: Content Type:
File Name: S1-100065.zip
Source: NEC, Samsung
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: CR to 22.220 - Temporary CSG membership based on traffic vol
ume
Doc.Name S1-100066 Allocations: Content Type:
File Name: S1-100066.zip
Source: NEC
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Proposal for Rel-11 WID: Enterprise H(e)NB Subsystem
Doc.Name S1-100067 Allocations: Content Type:
File Name: S1-100067.zip
Source: NEC ...
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Discussion document on Enterprise H(e)NB Subsystem
Doc.Name S1-100068 Allocations: Content Type:
File Name: S1-100068.zip
Source: NEC
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Allowed and operator CSG lists (a summary)
Doc.Name S1-100069 Allocations: Content Type:
File Name: S1-100069.zip
Source: Ericsson, ST-Ericsson
Abstract: A summary of the CSG lists handling in 3GPP Rel-8 and Rel-9.
This is the slideset that Peter B circulated on the SA1/CT1/CT6 exploder and is
intended for the SA1/CT1/CT6 joint session.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Contribution to TS 22.368 - section 7.1.1
Doc.Name S1-100070 Allocations: Content Type:
File Name: S1-100070.zip
Source: ZTE
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Service Requirements for Enhanced Voice
Doc.Name S1-100071 Allocations: Content Type:
File Name: S1-100071.zip
Source: Ericsson, ST-Ericsson, Orange SA, Telecom Italia, Qualcomm Incorporated, Huawei
Technologies, Motorola Ltd, NOKIA Corporation, Nokia Siemens Networks
Abstract: Discussion paper for the CR to 22.173 about Enhanced voice services.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: [CR to 22.173] Enhanced voice services
Doc.Name S1-100072 Allocations: Content Type:
File Name: S1-100072.zip
Source: Ericsson, ST-Ericsson, Orange SA, Telecom Italia, Qualcomm Incorporated, Huawei
Technologies, Motorola Ltd, NOKIA Corporation, Nokia Siemens Networks
Abstract: TR 22.813 was a joint effort between SA1 and SA4. It identifies and defines serv
ice and system requirements and high level codec requirements that should be met
for “Enhanced Voice Services” within the EPS. This CR proposes that
a condensed version of the service requirements in chapter 5 “System and
service requirements” from TS 22.813 is captured as a new annex in TS 22.1
73 under the name “IMS Multimedia Telephony with Enhanced Voice”.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Removing Editor's Note in Scope
Doc.Name S1-100073 Allocations: Content Type:
File Name: S1-100073.zip
Source: SK Telecom
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Addition to References
Doc.Name S1-100074 Allocations: Content Type:
File Name: S1-100074.zip
Source: SK Telecom
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Revision to Definitions
Doc.Name S1-100075 Allocations: Content Type:
File Name: S1-100075.zip
Source: SK Telecom
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Removing Editor's Note in 5.1.2 Procedure
Doc.Name S1-100076 Allocations: Content Type:
File Name: S1-100076.zip
Source: SK Telecom
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Revision to 6.1 General Requirement
Doc.Name S1-100077 Allocations: Content Type:
File Name: S1-100077.zip
Source: SK Telecom
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Revision to 6.5 Data Description Requirements
Doc.Name S1-100079 Allocations: Content Type:
File Name: S1-100079.zip
Source: SK Telecom
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Revision to 6.6 Charging Requirements
Doc.Name S1-100080 Allocations: Content Type:
File Name: S1-100080.zip
Source: SK Telecom
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: 8. Conclusion
Doc.Name S1-100082 Allocations: Content Type:
File Name: S1-100082.zip
Source: SK Telecom
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Reply LS to S2-097491 on authentication and ASs for IMS emer
gency calls
Doc.Name S1-100083 Allocations: Content Type:
File Name: S1-100083.zip
Source: Deutsche Telekom
Abstract: Proposed reply to S2-097491. A new WID (S1-100087) and one CR (S1-100088) are re
lated to this reply.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Revision to 3. Definions, etc.
Doc.Name S1-100084 Allocations: Content Type:
File Name: S1-100084.zip
Source: SK Telecom
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Revision to 3. Definions, etc.
Doc.Name S1-100086 Allocations: Content Type:
File Name: S1-100086.zip
Source: SK Telecom
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: IMS Emergency Session Enhancements
Doc.Name S1-100087 Allocations: Content Type:
File Name: S1-100087.zip
Source: Deutsche Telekom
Abstract: WID proposal related to reply LS S1-100083 and CR S1-100088
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: CR 22.101, R10: IMS emergency call enhancements
Doc.Name S1-100088 Allocations: Content Type:
File Name: S1-100088.zip
Source: Deutsche Telekom, Orange
Abstract: A CR to 22.101 R10, related to the reply LS in S1-100083 and the proposed WID S1
-100087
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Revision to 4. Consideration
Doc.Name S1-100089 Allocations: Content Type:
File Name: S1-100089.zip
Source: SK Telecom
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Revision to 5. Requirement
Doc.Name S1-100090 Allocations: Content Type:
File Name: S1-100090.zip
Source: SK Telecom
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Revision to 5. Requirement
Doc.Name S1-100091 Allocations: Content Type:
File Name: S1-100091.zip
Source: SK Telecom
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Comments to S1-100040 Discussion paper on Non-Voice Emergenc
y Services
Doc.Name S1-100092 Allocations: Content Type:
File Name: S1-100092.zip
Source: RIM UK Ltd
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Revision to 6. Conclusion
Doc.Name S1-100093 Allocations: Content Type:
File Name: S1-100093.zip
Source: SK Telecom
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: CR 22.101, R10: general emergency call enhancements
Doc.Name S1-100094 Allocations: Content Type:
File Name: S1-100094.zip
Source: Deutsche Telekom
Abstract: This CR is _not_ related to the IMS emergency enhancements in S1-100083, 087 and
088. It adds a new general functionality.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: CR 22.220 - Rel-10: IMS HNB interworking alignment with SA2
decision
Doc.Name S1-100098 Allocations: Content Type:
File Name: S1-100098.zip
Source: Nokia Siemens Networks
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: CR 22.220 - Rel-9: IMS HNB interworking alignment with SA2 d
ecision
Doc.Name S1-100099 Allocations: Content Type:
File Name: S1-100099.zip
Source: Nokia Siemens Networks
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: CR TS 22.368 section 7.1.4: Charging
Doc.Name S1-100100 Allocations: Content Type:
File Name: S1-100100.zip
Source: Nokia Siemens Networks
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: [CR to 22.153 (MPS)] - Clarification of Service Aspects
Doc.Name S1-100101 Allocations: Content Type:
File Name: S1-100101.zip
Source: Telcordia Technologies
Abstract: This contribution contains a proposed CR to TS 22.153 (Release 10) to clarify se
rvice aspects for video and data bearer service.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: TS 22.368 Section 7.1.X Device triggering
Doc.Name S1-100102 Allocations: Content Type:
File Name: S1-100102.zip
Source: KPN, Telecom Italia, Sierra Wireless, Vodafone, NSN
Abstract: This contribution proposes to add requirements related to device triggering by t
he MTC Server to the common requirements in Section 7.1.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: TS22.368 Chapt4 removal of editors note
Doc.Name S1-100103 Allocations: Content Type:
File Name: S1-100103.zip
Source: KPN, Samsung, Vodafone
Abstract: This contribution proposes to remove the editors note in chapter 4
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Clarification of requirements for LIPA
Doc.Name S1-100104 Allocations: Content Type:
File Name: S1-100104.zip
Source: Samsung, Alcatel-Lucent, Vodafone
Abstract: Provides a general update and clarification to requirements for Local IP Access.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Removal of editors note on identifiers
Doc.Name S1-100105 Allocations: Content Type:
File Name: S1-100105.zip
Source: KPN, Vodafone, NSN
Abstract: This contribution proposes to remove the editors note in chapter 7.1.3 on identi
fiers
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: TS22.368 - 7.2.3: Time Tollerant
Doc.Name S1-100107 Allocations: Content Type:
File Name: S1-100107.zip
Source: Telecom Italia
Abstract: Clarification of the requirements in this section
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: 22.368 - section 7.2.3: Time Tolerant
Doc.Name S1-100108 Allocations: Content Type:
File Name: S1-100108.zip
Source: KPN, Vodafone, NSN, Sierra Wireless, Samsung
Abstract: This contribution proposes to modifiy the requirements about Time Tolerant MTC F
eature catering for the purpose of the MTC Feature.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Clarification of Time Controlled
Doc.Name S1-100109 Allocations: Content Type:
File Name: S1-100109.zip
Source: KPN, Sierra Wireless, NSN, ZTE, Panasonic
Abstract: This contribution proposes a number of clarifications regarding the MTC Feature
Time Controlled based on questions raised on Time Controlled in the previous 3GP
P SA2 meeting.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: 22.368 - section 7.2.15 removal of editors note
Doc.Name S1-100110 Allocations: Content Type:
File Name: S1-100110.zip
Source: KPN
Abstract: This contribution proposes to remove the editors note in section 7.2.15 Location
based trigger
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: 22.368: which features are really features?
Doc.Name S1-100111 Allocations: Content Type:
File Name: S1-100111.zip
Source: Telecom Italia
Abstract: Not all the features are loooking as capabilities to be subscribed....
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Clarification about the sending of IMSI for Emergency calls
Doc.Name S1-100112 Allocations: Content Type:
File Name: S1-100112.zip
Source: WG Chairman
Abstract: Australian regulator has raised the problem of possible unclear specifications a
bout the sending of IMSI during emergency calls in limited service state, even w
hen a xSIM is present in the UE.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: LS about IMSI and Emergency calls (to CT1)
Doc.Name S1-100115 Allocations: Content Type:
File Name: S1-100115.zip
Source: WG Chairman
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: More Discussion on the Operator CSG list
Doc.Name S1-100116 Allocations: Content Type:
File Name: S1-100116.zip
Source: Motorola
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: 22.368 - Contents of Extra Low Power Consumption
Doc.Name S1-100117 Allocations: Content Type:
File Name: S1-100117.zip
Source: Motorola
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: 22.368 - Concerns on Jamming Indication
Doc.Name S1-100118 Allocations: Content Type:
File Name: S1-100118.zip
Source: Motorola
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: TS 22.368: clarifications and modifications to requirements
Doc.Name S1-100119 Allocations: Content Type:
File Name: S1-100119.zip
Source: Ericsson AB, ST-Ericsson
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Emergency call support
Doc.Name S1-100120 Allocations: Content Type:
File Name: S1-100120.zip
Source: Research In Motion
Abstract: Emergency call support
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Discussion on Non-Voice Emergency Services Considerations
Doc.Name S1-100121 Allocations: Content Type:
File Name: S1-100121.zip
Source: Alcatel-Lucent
Abstract: Discussion on Non-Voice Emergency Services considerations - what capabilities ar
e expected on the emergency services networks
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Mapping of MTC features to service properties
Doc.Name S1-100122 Allocations: Content Type:
File Name: S1-100122.zip
Source: Ericsson AB, ST-Ericsson
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Discussion about FMC Operational Scenario
Doc.Name S1-100123 Allocations: Content Type:
File Name: S1-100123.zip
Source: Telecom Italia
Abstract: Discussion about FMC Operational Scenario
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: 22.278: Operational Requirements on Fixed Mobile Convergenc
e
Doc.Name S1-100124 Allocations: Content Type:
File Name: S1-100124.zip
Source: Telecom Italia
Abstract: 22.278: Operational Requirements on Fixed Mobile Convergence
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Reply to SA3 LS about SIP Digest Authentication in IMS
Doc.Name S1-100126 Allocations: Content Type:
File Name: S1-100126.zip
Source: Telecom Italia
Abstract: Reply to SA3 LS about SIP Digest Authentication in IMS
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Work Item Description for IP Interconnection Requirements
Doc.Name S1-100127 Allocations: Content Type:
File Name: S1-100127.zip
Source: Telefónica
Abstract: This WID is to start the requirement specification work on Advanced IP Interconn
ection Requirements tofollow from the study in TR22.893
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Contribution to TS 22.368: Bearer restriction
Doc.Name S1-100128 Allocations: Content Type:
File Name: S1-100128.zip
Source: Huawei Technologies
Abstract: propose a new MTC Feature for Devices not needing user plane or not needing two-
directions user plane
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Contribution to TS 22.368 section 7.2.5: Replace Online Offl
ine Small Data Transmission by Small Data Transmission
Doc.Name S1-100129 Allocations: Content Type:
File Name: S1-100129.zip
Source: Huawei Technologies
Abstract: Current Online and Offline Data Transmission MTC Features mix optimisation possi
ble for the sending of small amount of data (no overhead…) and optimisation po
ssible when data transfer is infrequent (detach the device) while this is not ne
eded
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Contribution to TS 22.368: Specific MTC Feature for Infreque
nt Transmission
Doc.Name S1-100130 Allocations: Content Type:
File Name: S1-100130.zip
Source: Huawei Technologies
Abstract: Separate the Infrequent transmission MTC Feature from small data feature
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: TS 22.368 Clause 7.2.12: PAM Clarification
Doc.Name S1-100131 Allocations: Content Type:
File Name: S1-100131.zip
Source: Huawei Technologies
Abstract: This contribution discusses the applicability of PAM when MTC Device may not be
attached to the network.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Group Based Charging MTC Feature
Doc.Name S1-100132 Allocations: Content Type:
File Name: S1-100132.zip
Source: Huawei Technologies
Abstract: This contribution proposes to introduce the Group Based Charging MTC Feature in
TS 22.368.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: TS22.368 Efficient Network-Triggered Communications with MTC
Devices
Doc.Name S1-100133 Allocations: Content Type:
File Name: S1-100133.zip
Source: Qualcomm Incorporated
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: TS22.368 Use of MSISDNs as MTC Device identifiers
Doc.Name S1-100134 Allocations: Content Type:
File Name: S1-100134.zip
Source: Qualcomm Incorporated
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: TS 22.368 Clause 7.2.2: Clarification for Time Control
Doc.Name S1-100135 Allocations: Content Type:
File Name: S1-100135.zip
Source: Huawei Technologies
Abstract: This contribution proposes to clarify the Time Control requirements in TS 22.368
.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: CR to TS22.153 on priority for delay tolerant services
Doc.Name S1-100136 Allocations: Content Type:
File Name: S1-100136.zip
Source: Qualcomm Incorporated
Abstract: eMPS
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Group based addressing for TS 22.368
Doc.Name S1-100137 Allocations: Content Type:
File Name: S1-100137.zip
Source: InterDigital communications, Inc.
Abstract: For the purpose of scalability and efficient utilization of network resources, a
common IMSI, called Group IMSI, for a group of MTC devices is proposed.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Group Based Registration for TS 22.368
Doc.Name S1-100138 Allocations: Content Type:
File Name: S1-100138.zip
Source: Interdigital Communication
Abstract: In order to minimize registration of individual MTC devices, a group based regis
tration procedure is proposed.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Group Based Access for TS 22.368
Doc.Name S1-100139 Allocations: Content Type:
File Name: S1-100139.zip
Source: Interdigital Communication
Abstract: In order to optimize control, management, data exchange for M2M devices a group
based access feature is proposed.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Group Based RAB & IP assignment for TS 22.368
Doc.Name S1-100140 Allocations: Content Type:
File Name: S1-100140.zip
Source: Interdigital Communication
Abstract: In order to optimize use of network resources, group based allocation of radio r
esource and IP address is proposed.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Classification of Time Controlled feature for TS 22.368
Doc.Name S1-100141 Allocations: Content Type:
File Name: S1-100141.zip
Source: Interdigital Communication
Abstract: The Time controlled feature in the TS 22.368 is classified as Control cycle and
wake up cycle.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Single and Multiple Registrations for TS 22.368
Doc.Name S1-100142 Allocations: Content Type:
File Name: S1-100142.zip
Source: Interdigital Communication
Abstract: Registration procedures for MTC devices can be controlled by the user or network
operator from only single registration to multiple registration based on mobili
ty, time controlled feature etc.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Use Case for Non-Voice Emergency Services
Doc.Name S1-100143 Allocations: Content Type:
File Name: S1-100143.zip
Source: at&t
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Group Based Registration and Access (Device Based Operation)
Doc.Name S1-100144 Allocations: Content Type:
File Name: S1-100144.zip
Source: InterDigital Communication
Abstract: The present document aims to provide a range of solutions based on using a Group
IMSI to reduce the overhead related to a large number of MTC Devices. In this d
ocument, the solution presented is based on having the MTC Devices initiating co
mmunication with the network, while another discussion document presents solutio
ns where the network initiates communication.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Group Based Registration and Access (Network Based Operation
)
Doc.Name S1-100145 Allocations: Content Type:
File Name: S1-100145.zip
Source: IntrDigital Communication
Abstract: The following describes the main points of the network-based group IMSI method:
- A single IMSI is allocated to a group of MTC Devices located in a single cell,
routing area (RA) or tracking area (TA)
- Activity time periods are defined and known by all MTC Devices (using pre-conf
iguration and/or updates from the network); during these activity periods all MT
C Devices are required to listen to pre-determined channels.
- During these activity periods, a reporting event may be sent by the MTC Server
to wake up the devices; it is also possible for the MTC Server to send control
commands during these periods.
- Upon reception of event or control trigger, the CN initiates a pre-registratio
n process for any targeted group, using their Group Identification, and starts t
he Mobility Management State Machine for the Group.
o This includes assigning Temporary UE Identity (e.g. P-TIMSI) and optionally th
e IP Address for the group.
- From this point on, the CN may access the MTC Devices either targeting a whole
group or an individual device:
o The network sends information to all MTC Devices using for example broadcast o
r paging. The addressing information to reach the group is a pre-determined loca
tion (e.g. cell/RA/TA) and the group IMSI.
o Paging may be used for unicast access. To access an individual MTC Device, the
network needs an additional MTC Device identifier in the message. This identifi
er is for example an end user account number. A MTC Device uses its identifier t
o filter out unicast messages not sent specifically to it.
- CN pages individual Groups to assign Bearer Information and (optionally) IP Ad
dress.
o If the IP Address was not allocated in the pre-registration sequence, this cou
ld be done at a later stage, for example during the first MTC Device network acc
ess.
- CN then control the MTC Device network access sequence order by paging individ
ual MTC Devices.
o Upon page reception, a MTC Device uses network access to send a usage report,
or respond to control messages for example.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Network initiated inter-UE transfer
Doc.Name S1-100146 Allocations: Content Type:
File Name: S1-100146.zip
Source: InterDigital Communications
Abstract: With existing IMS procedures it is possible that the network initiates session r
elease upon receiving information that the IP-CAN can no longer support the exis
ting IMS session. This can be due to, for example, loss of IP-CAN connectivity,
or degraded QoS. With Service Continuity, there is the possibility to transfer t
he session(s) from the failing access leg to another IP-CAN on the same device.
With inter-UE transfers, it could also be feasible to transfer the session and/o
r media components to a different UE.
The procedure may be a user preference allowing the network to initiate inter-UE
transfers in the cases where connectivity is lost, and a list of preferred UEs
may also be supported as part of the user’s profile. The user profile may incl
ude information such that if a particular UE is in close proximity to a UE which
has an ongoing session, then the network is allowed to transfer the session or
media components to this different UE.
Other cases where such network initiated inter-UE transfers are envisaged are fo
r load balancing purposes to elliviate traffic on a specific access leg or to ov
ercome one UE’s bandwidth limitations by diverting some media components or se
ssions to another device.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Clarification of SIPTO security requirements
Doc.Name S1-100148 Allocations: Content Type:
File Name: S1-100148.zip
Source: Panasonic
Abstract: The general security requirements for H(e)NB Subsystem in section 9 are also app
licable in case of SIPTO, i.e. the security of the mobile operator's network or
the user’s privacy should not be compromised. However, this is currently not c
lear from the security requirements stated in section 5.9.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Alignment of SIPTO security requirements
Doc.Name S1-100149 Allocations: Content Type:
File Name: S1-100149.zip
Source: Panasonic
Abstract: Alignment of the security requirements for SIPTO in case of macro access with th
e security requirements valid for SIPTO in case of H(e)NB Subsystem.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Introduction of Charging requirements for Heterogeneous netw
orks
Doc.Name S1-100151 Allocations: Content Type:
File Name: S1-100151.zip
Source: Alcatel-Lucent
Abstract: This CR introduces requirements related to etherogeneaous networks,including HeN
B's and Relays, that is nodes relaying communications between a Donor eNB and th
e UE.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Draft LS reponse to the SIP Digest Authentication in IMS LS
Doc.Name S1-100153 Allocations: Content Type:
File Name: S1-100153.zip
Source: Huawei Technologies
Abstract: This contribution proposes a draft LS response to the SIP Digist Authentication
in IMS LS
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Requirements for Heterogeneous networks support in the EPS
Doc.Name S1-100154 Allocations: Content Type:
File Name: S1-100154.zip
Source: Alcatel-Lucent
Abstract: This CR iontroduces service and operational requirements in the EPS to support E
therogeneous networks
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Requirements for Heterogeneous networks support in the EPS
Doc.Name S1-100155 Allocations: Content Type:
File Name: S1-100155.zip
Source: Alcatel-Lucent
Abstract: This CR iontroduces service and operational requirements in the EPS to support E
therogeneous networks
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Offline Indication Editorial (7.2.10)
Doc.Name S1-100157 Allocations: Content Type:
File Name: S1-100157.zip
Source: Panasonic, China Mobile
Abstract: Some editorial corrections on section 7.2.10. In addition, the informative NOTE
on the detection time should be a normative requirement instead.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Definition of Heterogeneous networks
Doc.Name S1-100158 Allocations: Content Type:
File Name: S1-100158.zip
Source: Alcatel-Lucent
Abstract: Addition of the definition of heterogeneous networks, so that this is agreed 3GP
P-wide
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Location Specific Notification to be sent to MTC Server (7.
2.x)
Doc.Name S1-100159 Allocations: Content Type:
File Name: S1-100159.zip
Source: Panasonic, China Mobile
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Removing the requirement for PSAP call back identification
Doc.Name S1-100160 Allocations: Content Type:
File Name: S1-100160.zip
Source: InterDigital Communication
Abstract: In S1-094246, 3GPP CT1 inform SA1 that it was unlikely that a mechanism to ident
ify PSAP call backs could be provided in the release 9 timeframe. Thus CT1 reque
sted that such conclusion is taken into account in 22.101. The solution for mark
ing PSAP call backs is to come from IETF and requirements for marking PSAP call
backs should be removed from 3GPP specifications until the solution is available
.
The change in this CR is identical to that agreed for release 8 in S1-090157 CR#
0305r1 (SA1#44).
Summary of change: Removal of PSAP call back identification requirements in subc
lause 10.1.3.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Proposed WID on ' Enhancements to EPS for E-UTRA-based Heter
ogeneous Networks'
Doc.Name S1-100161 Allocations: Content Type:
File Name: S1-100161.zip
Source: Alcatel-Lucent
Abstract: With growing demand for data services, it is becoming increasingly difficult to
meet the required data capacity through traditional cell-splitting techniques, w
hich require deployment of more wide-area eNBs.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: MTC feature on Group Based Mobility (7.2.16.x)
Doc.Name S1-100162 Allocations: Content Type:
File Name: S1-100162.zip
Source: Panasonic
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Removing the requirement on call back for emergency call
Doc.Name S1-100163 Allocations: Content Type:
File Name: S1-100163.zip
Source: InterDigital Communications
Abstract: Abstract: In S1-094246, 3GPP CT1 inform SA1 that it was unlikely that a mechanis
m to identify PSAP call backs could be provided in the release 9 timeframe. Thus
CT1 requested that such conclusion is taken into account in 22.173. The solutio
n for marking PSAP call backs is to come from IETF and requirements for marking
PSAP call backs should be removed from 3GPP specifications until the solution is
available.
In release 9, the PSAP call back is treated as a normal incoming call and since
no explicit distinction can be made between normal calls and call backs, service
s may be applied to the incoming call back.
The change in this CR is identical to that agreed for release 8 in S1-090045 CR#
0051 (SA1#44).
Summary of change: Removal of PSAP call back requirements.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Proposed WID on ' Enhancements to EPS for E-UTRA-based Heter
ogeneous Networks'
Doc.Name S1-100164 Allocations: Content Type:
File Name: S1-100164.zip
Source: Alcatel-Lucent
Abstract: With growing demand for data services, it is becoming increasingly difficult to
meet the required data capacity through traditional cell-splitting techniques, w
hich require deployment of more wide-area eNBs.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Proposed WID on ' Enhancements to EPS for E-UTRA-based Heter
ogeneous Networks'
Doc.Name S1-100165 Allocations: Content Type:
File Name: S1-100165.zip
Source: Alcatel-Lucent
Abstract: With growing demand for data services, it is becoming increasingly difficult to
meet the required data capacity through traditional cell-splitting techniques, w
hich require deployment of more wide-area eNBs.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: [Discussion]Emergency call support to H(e)NB R8 and R9
Doc.Name S1-100167 Allocations: Content Type:
File Name: S1-100167.zip
Source: Research In Motion
Abstract: [Discussion]Emergency call support to H(e)NB R8 and R9
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Discussion on the Interaction of the Allowed CSG list and Op
erator CSG list
Doc.Name S1-100168 Allocations: Content Type:
File Name: S1-100168.zip
Source: Qualcomm Incorporated
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: CR to TS22.220 Enhancements to supporting enterprise deploym
ents for hot spots
Doc.Name S1-100169 Allocations: Content Type:
File Name: S1-100169.zip
Source: Qualcomm Incorporated
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Classifications of Service for NIMTC features
Doc.Name S1-100170 Allocations: Content Type:
File Name: S1-100170.zip
Source: InterDigital Communications
Abstract: The current categorization of various use cases is causing an impact on the feas
ibility of developing stage-2 specifications in a reasonable time. It is recomme
nded to re-classify these use cases into specific services (e.g., Smart metering
, Health, ..etc.). This will reduce the specification burden and syetem optimiza
tion to a set of coherent categories.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Texts for alignment in 8.5.0 and 8.5.1
Doc.Name S1-100171 Allocations: Content Type:
File Name: S1-100171.zip
Source: Research In Motion
Abstract: Texts for alignment in 8.5.0 and 8.5.1
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Contribution to TS 22.368 - Section 7.2.3 Time Tolerant
Doc.Name S1-100172 Allocations: Content Type:
File Name: S1-100172.zip
Source: KDDI
Abstract: This contribution proposes to clarify the text on identifying the network load f
or MTC Devices for the Time Tolerant MTC Feature.
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Reply to LS on Inter UE Transfer with ICS
Doc.Name S1-100173 Allocations: Content Type:
File Name: S1-100173.zip
Source: Research In Motion
Abstract: Reply to LS on Inter UE Transfer with ICS
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is not uploaded
 
DOCUMENT: Simultaneous PLMN Registrations for 3GPP and WLAN
Doc.Name S1-100174 Allocations: Content Type:
File Name: S1-100174.zip
Source: Telcordia, Toshiba Corporation
Abstract: This document discusses scenarios where the UE is simultaneously registered in m
ultiple PLMNs. This scenario may occur when the UE is capable to simultaneously
connect to 3GPP and WLAN accesses
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Simultaneous PLMN Registrations for 3GPP and WLAN
Doc.Name S1-100175 Allocations: Content Type:
File Name: S1-100175.zip
Source: Telcordia, Toshiba Corporation
Abstract: This document provides clarification on issues associated with the UE being simu
ltaneously registered in multiple PLMNs when connected to both 3GPP and WLAN sim
ultaneously
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: Draft Response LS on Inter UE Transfer with ICS
Doc.Name S1-100176 Allocations: Content Type:
File Name: S1-100176.zip
Source: Huawei Technologies
Abstract: This contribution provides the draft response LS to SA2 on Inter UE Transfer wit
h ICS
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
DOCUMENT: TS22.368: 7.2.12 PAM clarification
Doc.Name S1-100177 Allocations: Content Type:
File Name: S1-100177.zip
Source: Samsung
Late Contribution Date: 2010-02-10 23:59:00
Late Contribution Flag: N
The file is uploaded
 
178 Numbers Reserved... (15 Withdrawn)
With 0 Revisions   And   0 Addenda
Last Reservation/Withdrawal On '2010-02-11 at 10:27:52 (GMT +01:00)'

139 Files Uploaded (with Correct Filename)
Last Upload On '2010-02-10 at 23:11:14 (GMT +01:00)'