Identical to S2-001386.
Ag. Item
|
Tdoc #
|
Source
|
Title
|
Spec
|
CR #
|
cat
|
Rel
|
Conclusion
|
1
|
S2-001350
|
Chairman
|
Agenda
|
|
|
|
|
Approved.
|
1
|
S2-001351
|
MCC
|
Minutes of S2’s drafting meeting in Vancouver
|
|
|
|
|
Noted (already approved by e-mail).
|
3
|
S2-001381
|
S1-000616
|
LS on Response to comments on TR22.976 (v1.4.0)
|
|
|
|
|
Noted.
|
3
|
S2-001382
|
S1-000609
|
LS Cc S2 on “Priority of ME resources for WAP and SIM toolkit applications”
|
|
|
|
|
Noted.
|
3
|
S2-001384
|
N4-000520
|
Response LS on Terminology of TrFO/TFO and possible interworking scenarios
|
|
|
|
|
Proposed answer in S2-001662.
|
|
S2-001662
|
Ericsson
|
Proposed answer to S2-001384
|
|
|
|
|
For e-mail approval.
|
3
|
S2-001385
|
N4-000507
|
LS on appointment of people to maintain liaison with IGC
|
|
|
|
|
Noted.
|
3
|
S2-001387
|
N4-000515
|
LS (Cc S2) on request for response to N4 LS (N4-000340)
|
|
|
|
|
S2’s chairman has to contact N1’s chairman to check if S2 is still requested to perform some actions.
|
3
|
S2-001388
|
N2-000344
|
LS on IPT Basic Call Handling
|
|
|
|
|
Proposed answer in S2-001515.
|
3
|
S2-001515
|
BT
|
|
|
|
|
|
For e-mail approval.
|
3
|
S2-001390
|
R3-001998
|
LS response on support of AMR via Iu-ps in GERAN
|
|
|
|
|
An answer will be provided in S2-001516.
|
3
|
S2-001516
|
T-Mobil (Oscar)
|
|
|
|
|
|
For e-mail approval.
|
3
|
S2-001391
|
R2-001533
|
LS response (R3-001581) on SRNS Relocation of RT RABs and interaction with PDCP
|
|
|
|
|
Noted.
|
3
|
S2-001412
|
R3-001581
|
LS to R2 and S2 on Relocation interaction with PDCP
|
|
|
|
|
Noted.
|
3
|
S2-001392
|
R1- 000765
|
LS on ‘Proposed changes to 3GPP Release 2000 work plan’
|
|
|
|
|
To be included in the next version of the Work Plan by IGC convenor or by MCC.
|
3
|
S2-001393
|
N2-000194
|
LS on Proposed updates to Work Plan Version 1.0 relating to CAMEL Phase 4 work item
|
|
|
|
|
To be included in the next version of the Work Plan by IGC convenor or by MCC.
|
3
|
S2-001405
|
N1-000639
|
LS to R3 (Cc S2) on including the SAI into the Gs-i/f BSSAP+-LOCATION-UPDATE-REQUEST message as requested in N1-000543
|
|
|
|
|
Noted.
|
3
|
S2-001406
|
N1-000758
|
LS on Removal of Service Accept
|
|
|
|
|
Obsolete: the CR 184 in S2-001638 is already the compromise solution found at last N1 meeting.
|
|
S2-001638
|
N1-000973
|
LS on UMTS Service Request procedure
|
23.060
|
184
|
F
|
R99
|
For e-mail approval.
|
3
|
S2-001420
|
T2M000090
|
LS on Terminal Capability Negotiation
|
|
|
|
|
Noted.
|
3
|
S2-001407
|
N1-000712
|
LS on Terminal capability negotiation including codecs (reply)
|
|
|
|
|
Noted.
|
3
|
S2-001423
|
S1-000658
|
LS (Cc S2) on Guidance on future work for T2 SWG5, Multi-mode terminals
|
|
|
|
|
Noted.
|
3
|
S2-001413
|
R3001649
|
LS Response on hexadecimal IMEI format
|
|
|
|
|
Noted: S1 accepts these changes in S2-001408.
|
3
|
S2-001408
|
N1-000713
|
LS response on hexadecimal IMEI format
|
|
|
|
|
Noted.
|
3
|
S2-001409
|
N1-000793
|
LS to S2 on 23.060 CR “Change of the Cell update procedure”
|
23.060
|
147r1
|
F
|
R99
|
Approved (after checking that it is possible to include it as such in v.3.4).
|
3
|
S2-001411
|
R3-001578
|
LS on Progress of Real-Time PS Domain SRNS Relocation
|
|
|
|
|
Proposed answer in S2-001519.
|
3
|
S2-001519
|
Nokia (Marc)
|
|
|
|
|
|
For e-mail approval.
|
3
|
S2-001414
|
SMG9-00262
|
LS on Priority of ME resources for WAP and SIM toolkit applications
|
|
|
|
|
Noted.
|
3
|
S2-001415
|
S5-000320
|
LS on Protocol Choice for Layer I of MAP Security
|
|
|
|
|
Noted.
|
3
|
S2-001416
|
S5-000322
|
LS on Service Management – New R00 work item proposal under SA5’s responsibility
|
|
|
|
|
Not approved.
|
3
|
S2-001418
|
S3-000478
|
LS to S2 on use of IP for security key distribution
|
|
|
|
|
Noted. To be kept in mind when further progressing the work.
|
3
|
S2-001419
|
T2M000089
|
LS on VHE/OSA presentation
|
|
|
|
|
Too late.
|
3
|
S2-001422
|
S1-000651
|
LS on Re-establish Capability for Emergency call
|
|
|
|
|
Proposed answer in S2-001520.
|
3
|
S2-001520
|
Vodafone (Chris)
|
|
|
|
|
|
For e-mail approval.
|
3
|
S2-001424
|
R2-001859
|
LS on Corrections to relocation procedures in 23.060
|
23.060
|
|
F
|
R99
|
Revised CR in S2-001521.
Proposed LS back in S2-001522.
|
3
|
S2-001521
|
Nokia
|
|
23.060
|
183
|
F
|
R99
|
For e-mail approval.
|
3
|
S2-001522
|
Nokia
|
|
|
|
|
|
For e-mail approval.
|
3
|
S2-001425
|
R2-001817
|
LS response to R3-002198 on Directed signalling connection re-establishment at RRC
|
|
|
|
|
Proposed answer in S2-001527.
|
|
S2-001527
|
|
Response to LS in S2-001425.
|
|
|
|
|
For e-mail approval.
|
3
|
S2-001426
|
R2-001865
|
LS response to S2-001053 on “Two phase resource reservation”
|
|
|
|
|
Noted.
|
3
|
S2-001434
|
N1-000997
|
LS on Answer to Proposal of exchange of the terms “in GSM“ and “in UMTS“
|
|
|
|
|
Accepted. A proposed answer is provided in S2-001528.
|
|
S2-001528
|
Lucent
|
|
|
|
|
|
For e-mail approval.
|
3
|
S2-001427
|
R2-001868
|
LS (Cc S2) on Answer to Proposal of exchange of the terms “in GSM” and “in UMTS”
|
|
|
|
|
Noted.
|
3
|
S2-001428
|
R2-001870
|
LS on Failure during SRNS Relocation
|
|
|
|
|
Proposed answer in S2-001529.
|
|
S2-001529
|
Nokia
|
|
|
|
|
|
For e-mail approval.
|
3
|
S2-001430
|
T3-000470
|
LS on Clarification of UMTS-AKA for GSM R’99 Mobiles
|
|
|
|
|
Noted.
|
3
|
S2-001435
|
N1-001023
|
LS on the introduction of GEA2.
|
|
|
|
|
Approved. The editor should check that this decision does not impact 03.60 and 23.060.
|
|
S2-001658
|
N4-000713
|
LS on SRNS relocation based on global title
|
|
|
|
|
Proposed answer in S2-001658. Linked with S2-001469. Proposed answer in S2-001661
|
|
S2-001661
|
Ericsson
|
|
|
|
|
|
For e-mail approval.
|
3
|
S2-001431
|
Tiphon
|
Presentation of Tiphon
|
|
|
|
|
Noted.
|
3
|
S2-001432
|
Tip 19TD129
|
LS on TIPHON architecture document
|
|
|
|
|
Noted.
|
3
|
S2-001433
|
Tiphon
|
Document DTS-02003v0.10.10
|
|
|
|
|
Noted.
|
4
|
S2-001353
|
Alcatel/CN2
|
Detailed on Camel interworking with SGSN (SGSN CAMEL procedures)
|
23.060
|
169
|
F
|
R99
|
Editorially revised to S2-001530.
|
|
S2-001530
|
Alcatel
|
Detailed on Camel interworking with SGSN (SGSN CAMEL procedures)
|
|
|
|
|
Approved.
|
4
|
S2-001362
|
Vodafone
|
DTM: simultaneous LAU and RAU procedures on an SDCCH
|
23.060
|
170
|
F
|
R99
|
Approved.
|
4
|
S2-001439
|
Siemens
|
Compatibility GTPv0/GTPv1 in case of SGSN change
|
23.060
|
177
|
F
|
R99
|
Editorially revised to S2-001531.
|
|
S2-001531
|
Siemens
|
Compatibility GTPv0/GTPv1 in case of SGSN change
|
23.060
|
177r1
|
F
|
R99
|
Approved.
|
4
|
S2-001491
|
Motorola
|
IP v6 address stateless autoconfiguration
|
23.060
|
180
|
F
|
R99
|
Not approved. Later revised to S2-001543.
|
|
S2-001543
|
Motorola
|
IP v6 address stateless autoconfiguration
|
23.060
|
180r1
|
F
|
R99
|
Not handled.
|
3
|
S2-001525
|
GERAN
|
LS on 23.060 Change Requests for Dual Transfer Mode
|
|
|
|
|
See conclusion on the CRs themselves in the two following tdocs.
|
4
|
S2-001523
|
Vodafone
|
DTM: reuse of the GPRS Suspension procedure in cells with no DTM capabilities
|
23.060
|
171r1
|
F
|
R99
|
Approved.
|
4
|
S2-001524
|
Vodafone
|
DTM: download of the IMSI from the SGSN to the BSC
|
23.060
|
172r1
|
F
|
R99
|
Approved.
|
4
|
S2-001371
|
Ericsson
|
CS Paging procedure in UMTS
|
23.060
|
173
|
F
|
R99
|
Approved.
|
4
|
S2-001372
|
Ericsson
|
Clarification on P-TMSI and P-TMSI signature at Detach
|
23.060
|
174
|
F
|
R99
|
Approved.
|
4
|
S2-001373
|
Ericsson
|
Serving RNS Relocation Procedure
|
23.060
|
175
|
F
|
R99
|
Editorially revised to S2-001532.
|
4
|
S2-001532
|
Ericsson
|
Serving RNS Relocation Procedure
|
23.060
|
175r1
|
F
|
R99
|
Approved.
|
4
|
S2-001374
|
Ericsson
|
DRX and MS network capabilities within UMTS
|
23.060
|
176
|
F
|
R99
|
Editorially revised to S2-001533
|
4
|
S2-001533
|
Ericsson
|
DRX and MS network capabilities within UMTS
|
23.060
|
176r1
|
F
|
R99
|
Approved.
|
4
|
S2-001514
|
Motorola
|
Suspend at UMTS to GSM inter-system change during a CS connection
|
23.060
|
181
|
F
|
R99
|
Not approved. Revised to S2-001534.
|
4
|
S2-001534
|
Motorola
|
Suspend at UMTS to GSM inter-system change during a CS connection
|
23.060
|
181r1
|
F
|
R99
|
For e-mail approval.
|
4
|
S2-001517
|
Motorola
|
Removal of PDP type OSP:IHOSS in R99
|
23.060
|
182
|
F
|
R99
|
To be revised to S2-001536.
The corresponding CR on 03.60 is in S2-001535.
|
4
|
S2-001536
|
Motorola
|
Removal of PDP type OSP:IHOSS in R99
|
23.060
|
182r1
|
F
|
R99
|
For e-mail approval.
|
4
|
S2-001535
|
Motorola
|
Removal of PDP type OSP:IHOSS in R99
|
03.60
|
A188
|
F
|
R98
|
For e-mail approval.
|
4
|
S2-001512
|
Alcatel
|
Correction to Data Retrieve protocol stacks endpoints
|
23.121
|
059r1
|
|
R99
|
Revised to S2-001537.
|
4
|
S2-001537
|
Alcatel
|
Correction to Data Retrieve protocol stacks endpoints
|
23.121
|
059r1r1
|
|
R99
|
For e-mail approval.
|
5.3
|
S2-001513
|
Alcatel
|
Correction to Data Retrieve protocol stacks endpoints
|
23.121
|
060r1
|
|
R00
|
Revised to S2-001538.
|
5.3
|
S2-001538
|
Alcatel
|
Correction to Data Retrieve protocol stacks endpoints
|
23.121
|
060r2
|
|
R00
|
For e-mail approval.
|
4
|
S2-001458
|
NTT Commware
|
Correction on Iu Release Procedure
|
23.060
|
178
|
F
|
R99
|
Revised to S2-001607.
|
4
|
S2-001607
|
NTT
|
Correction on Iu Release Procedure
|
23.060
|
178r1
|
F
|
R99
|
Approved, revised to S2-001654 because of an editorial error.
|
|
S2-001654
|
NTT
|
Correction on Iu Release Procedure
|
23.060
|
178r1
|
F
|
R99
|
Approved.
|
5
|
S2-001459
|
NTT Commware
|
Introduction of Integrated Serving Node
|
23.002
|
021
|
B
|
R00
|
Not approved: information for CN is expected before.
|
5
|
S2-001608
|
NTT
|
|
|
|
|
|
For e-mail approval.
|
3
|
S2-001386
|
N4-000549
|
LS on Architectural Impact of Combined MAP Signaling for Mobility Management
|
|
|
|
|
An answer is generated based on these inputs in S2-001608.
|
5.3
|
S2-001457
|
NTT Commware
|
Draft TR on Feasibility study on architecture for network requested PDP contextactivation with User-ID
|
23.8xx
|
|
|
|
For e-mail approval. Revised later on during this meeting.
|
3
|
S2-001609
|
G00-0374
|
LS on inter-BSC hard handover in GERAN for the packet switched domain
|
|
|
|
|
See conclusions of S2-001397.
|
5
|
S2-001397
|
Alcatel
|
Use of Iur and Iu-ps interfaces – Handovers
|
|
|
|
R00
|
Proposed answer to S2-001609 in S2-001613. To be decided later on, based on its content, whether it has to be sent or not.
For the other questions of S2-001609, a drafting group is established.
|
5
|
S2-001613
|
Alcatel
|
Draft LS to GERAN (Cc R2, R3) on inter-BSC hard handover in GERAN for the packet switched domain
|
|
|
|
|
Editorially revised to S2-001637.
|
|
S2-001637
|
SA2
|
LS to GERAN and R3 (Cc R2) on inter-BSC hard handover in GERAN for the packet switched domain
|
|
|
|
|
Approved.
|
5
|
S2-001398
|
Alcatel
|
Handover and RAN Relocation for the GERAN (companion of S2-001397)
|
23.121
|
058
|
|
R00
|
Withdrawn, due to the lack of agreement on S2-001397.
|
5
|
S2-001485
|
AT&T
|
PS domain multiple RABs Real time HO requirements
|
|
|
|
|
An LS is generated in S2-001614.
|
5
|
S2-001614
|
AT&T
|
|
|
|
|
|
For e-mail approval.
|
5
|
S2-001612
|
Vodafone
|
Initial thoughts on GERAN impacts on overall system architecture
|
|
|
|
|
LS generated on this basis in S2-001615.
|
5
|
S2-001615
|
Vodafone
|
|
|
|
|
|
For e-mail approval.
|
5.1
|
|
|
REGISTRATION
|
|
|
|
|
|
2
|
S2-001375
|
Vice Chairman
|
Status of S2 E-mail approval between S2#13 and S2#14
|
|
|
|
|
Alcatel sent some comments on CSCF discovery, but too late (after the deadline).
S2-001252, 1259 and 1261 were supposed to be approved by e-mail, but they are asked to be approved now: to be approved by Wednesday if no objection is made.
|
5.1
|
S2-001482
|
AT&T
|
Multiple I-CSCF
|
|
|
|
|
Revised to S2-001540, with these changes.
|
5.1
|
S2-001540
|
AT&T
|
Multiple I-CSCF
|
|
|
|
|
Approved.
|
5.1
|
S2-001400
|
Alcatel
|
P-CSCF discovery
|
23.228
|
|
|
R00
|
Not approved: the conclusion is still to use DHCP, as agreed in Vancouver.
|
5.1
|
S2-001438
|
Siemens
|
CSCF Availability at Session Setup
|
|
|
|
|
Not approved as such.
|
5.1
|
S2-001442
|
BT
|
Revised proposal for registration flows
|
|
|
|
|
A general conclusion will be made on all the contributions dealing with registration flow.
|
5.1
|
S2-001452
|
Lucent
|
Serving CSCF Assignment
|
|
|
|
|
Handled by the drafting group on Registration.
|
5.1
|
S2-001462
|
Ericsson
|
Triggering the CSCF Selection Function. Home Network Control case.
|
|
|
|
|
Handled by the drafting group on Registration.
|
5.1
|
S2-001453
|
Lucent
|
Registration/Deregistration Information Flows
|
|
|
|
|
Handled by the drafting group on Registration.
|
5.1
|
S2-001460
|
Ericsson
|
Serving CSCF Selection Function
|
|
|
|
|
Handled by the drafting group on Registration.
|
5.3
|
S2-001469
|
Ericsson
|
HSS Role as VLS
|
|
|
|
|
Not approved. Some written contributions are needed on this subject.
|
5.1
|
S2-001463
|
Ericsson
|
Triggering the CSCF Selection Function. Visited Network Control case.
|
|
|
|
|
Also not approved.
|
5.1
|
S2-001465
|
Ericsson
|
Registration procedures
|
|
|
|
|
Handled by the drafting group on Registration.
|
|
S2-001641
|
Nokia
|
Many to many relationship on Iu interface
|
23.121
|
061
|
B
|
R00
|
|
5.1
|
S2-001476
|
Lucent
|
Registration Models
|
|
|
|
|
Not approved.
|
5.1
|
S2-001541
|
Motorola Inc, Nortel Networks, Siemens, Alcatel, T-Mobil
|
Serving CSCF Selection
|
|
|
|
|
Not approved. Handled by the drafting group on Registration.
|
5.1
|
S2-001508
|
Motorola
|
Serving CSCF Selection Registration Flows
|
|
|
|
|
Handled by the drafting group on Registration.
|
5.1
|
S2-001542
|
AT&T
|
Registration functionality
|
|
|
|
|
Handled by the drafting group on Registration.
|
5.1
|
S2-001547
|
Drafting group
|
Output of the drafting on registration
|
|
|
|
|
Noted. The result is proposed to be incorporated in 23.228 as shown in S2-001616.
|
5.1
|
S2-001616
|
AT&T
|
Text for 23.228 from drafting session on S-CSCF Selection
|
|
|
|
|
Editorially revised to S2-001635.
|
|
S2-001635
|
SA2
|
Text for 23.228 from drafting session on S-CSCF Selection
|
|
|
|
|
Approved.
|
5.1
|
S2-001606
|
Ericsson, Motorola, Lucent, AT&T
|
Registration procedures
|
|
|
|
|
Revised to S2-001610.
|
5.1
|
S2-001610
|
Ericsson
|
Registration procedures
|
|
|
|
|
Editorially revised to S2-001618. The text has to be moved in the main body of 23.228 in S2-001618.
|
5.1
|
S2-001618
|
Ericsson
|
Registration procedures
|
|
|
|
|
Approved.
|
5.1
|
S2-001453
|
Lucent
|
Registration/Deregistration Information Flows
|
|
|
|
|
Not Approved. More contributions are needed on de-registration before a conclusion can be taken. Contributions are invited on this topic at next meeting.
|
5.1
|
S2-001464
|
Ericsson, Nokia, Vodafone
|
Clarification of HSS Role in SIP Registration procedure
|
|
|
|
|
Not approved. The flows need to be elaborated first: the text leads to endless discussions.
|
5.2
|
S2-001484
|
AT&T
|
Template for call flows
|
|
|
|
|
Approved. Used to be decided on a case by case basis.
|
5.2
|
S2-001316
|
Lucent
|
Revised Information Flow Template
|
|
|
|
|
Encompassed by the previous document.
|
5.2
|
S2-001436
|
Telia
|
Ungraceful session termination in the IM domain
|
|
|
|
|
The requirements are expressed in S2-001602, and a LS to N1 is proposed in S2-001603.
|
5.2
|
S2-001602
|
Telia
|
Requirement for handling ungraceful session termination in the IM domain
|
|
|
|
|
Approved.
|
5.2
|
S2-001603
|
Telia
|
|
|
|
|
|
For e-mail approval.
|
5.2
|
S2-001509
|
Motorola
|
Roles of CSCF and SIP versions
|
|
|
|
|
No version number of SIP should be defined by S2.
Concerning the roles, it was said that the flows have to be provided first, and then the exact wording can be found. But the OK with the rough lines.
To be revised to S2-001604.
|
5.2
|
S2-001312
|
Ericsson
|
Introduction of functional elements from 23.821 into 23.002
|
23.002
|
020
|
B
|
R00
|
For e-mail approval.
|
5.2
|
S2-001604
|
Motorola
|
|
|
|
|
|
For e-mail approval.
|
|
|
|
The drafting session on Call flows will be in parallel with the plenary, and it will focus on the first Invite flow
|
|
|
|
|
|
5.2
|
S2-001456
|
Siemens
|
Mobile Terminated Call Routing between IMS and CS
|
|
|
|
|
See conclusion on S2-001396, presenting another solution to the same problem.
|
5.2
|
S2-001396
|
Alcatel
|
Routing (CS/PS) of incoming calls
|
23.228
|
|
|
R00
|
None of these 2 contributions are approved. More discussions are needed.
|
5.2
|
S2-001490
|
Nokia
|
A definition on signalling PDP context
|
23.060
|
179
|
B
|
R00
|
Not approved.
|
5.2
|
S2-001394
|
Alcatel
|
External IP Call Termination Points
|
23.228
|
|
|
R00
|
For Call flow drafting group.
|
5.2
|
S2-001443
|
BT
|
|
|
|
|
|
For Call flow drafting group.
|
5.2
|
S2-001444
|
BT
|
|
|
|
|
|
For Call flow drafting group.
|
5.2
|
S2-001448
|
Marconi
|
Mobile Originated SIP based Call Flows
|
|
|
|
|
For Call flow drafting group.
|
5.2
|
S2-001454
|
Lucent
|
Mobile Origination Information Flows
|
|
|
|
|
For Call flow drafting group.
|
5.2
|
S2-001455
|
Lucent
|
Mobile Termination Information Flows
|
|
|
|
|
For Call flow drafting group.
|
5.2
|
S2-001466
|
Ericsson
|
- not provided -
|
|
|
|
|
For Call flow drafting group.
|
5.2
|
S2-001468
|
Ericsson
|
- not provided -
|
|
|
|
|
For Call flow drafting group.
|
5.2
|
S2-001504
|
Nortel
|
- not provided -
|
|
|
|
|
For Call flow drafting group.
|
5.2
|
S2-001510
|
Motorola
|
- not provided -
|
|
|
|
|
For Call flow drafting group.
|
|
S2-001546
|
3Com
|
Registration call flows
|
|
|
|
|
Handled by Call Flow drafting group.
|
5.2
|
S2-001449
|
AT&T
|
Call Flow Definitions
|
|
|
|
|
For Call flow drafting group.
|
5.2
|
S2-001621
|
AT&T
|
Call Flows
|
|
|
|
|
|
5.2
|
S2-001481
|
AT&T
|
Annex X1 of 23.228 (Editorial update)
|
|
|
|
|
For Call flow drafting group.
|
5.2
|
S2-001620
|
AT&T
|
Annex B.1 update
|
|
|
|
|
|
|
S2-001636
|
Drafting group on Call Flows
|
Result of the drafting on call flows.
|
|
|
|
|
For e-mail approval. 15th of September
|
5
|
S2-001437
|
Siemens
|
CSCF Availability during the SIP Session
|
|
|
|
|
Revised to S2-001632 to keep only the requirements.
|
|
S2-001632
|
Siemens
|
CSCF Availability during the SIP Session
|
|
|
|
|
For e-mail approval.
|
5.2
|
S2-001474
|
Nokia
|
Role of the proxy CSCF after the registration procedure
|
|
|
|
|
Editorially revised to S2-001633
|
|
S2-001633
|
Nokia
|
Role of the proxy CSCF after the registration procedure
|
|
|
|
|
Approved.
|
|
S2-001611
|
Siemens, Mannesmann
|
Multimedia messaging architecture
|
|
|
|
|
Proposed LS to T2 in S2-001631.
|
|
S2-001631
|
Mannesmann
|
|
|
|
|
|
For e-mail approval.
|
5.2
|
S2-001467
|
Ericsson
|
ENUM and TRIP protocols in 3GPP R’00
|
|
|
|
|
Not approved. Ericsson can come back with a contribution on how to bring these protocols in the architecture.
|
5.3
|
S2-001601
|
Nokia
|
Release 2000 Specific Ipv4/Ipv6 Transition Scenarios
|
|
|
|
|
See conclusion in next tdoc.
|
5.3
|
S2-001493
|
Motorola
|
Ipv4/Ipv6 Interworking Scenarios
|
|
|
|
|
Not approved and S2-001601 neither. More time is allowed for Nokia and Motorola to try to align their views.
|
5.3
|
S2-001494
|
Motorola
|
IP Address Management
|
|
|
|
|
Revised to S2-001643.
|
5.3
|
S2-001643
|
Motorola
|
IP Address Management
|
|
|
|
|
For e-mail approval.
|
5
|
S2-001356
|
Hughes network systems
|
Proposal for V.44 Data Compression in SNDCP
|
|
|
|
|
Not approved.
|
5
|
S2-001357
|
Hughes network systems
|
Proposal for V.44 Data Compression in PDCP
|
|
|
|
|
Not approved.
|
6 OSA
|
S2-001358
|
VHE/OSA ad-hoc
Group
|
Minutes of the VHE/OSA Drafting Meeting of Montreal (August)
|
|
|
|
|
Approved. It asks for approval of the three following LSs (S2-001359, 1360 and 1361).
|
6 OSA
|
S2-001359
|
VHE/OSA ad-hoc
Group
|
Proposed LS to S1 and N5 on terminology in OSA specifications
|
|
|
|
|
Editorially revised to S2-001639
|
6
|
S2-001639
|
SA2
|
LS to S1 (Cc N5) on terminology in OSA specifications
|
|
|
|
|
Approved.
|
6 OSA
|
S2-001360
|
VHE/OSA ad-hoc
Group
|
Proposed LS to S1 and N5 on work split between SA 1, SA 2 and CN 5
|
|
|
|
|
Approved.
|
6 OSA
|
S2-001361
|
VHE/OSA ad-hoc
Group
|
Reply LS to S1 ( Cc T2-1, N2, WAP WAG Sync, T3, S3) on Support of VHE User Profiles
|
|
|
|
|
Approved.
|
6 OSA
|
S2-001623
|
OSA
|
Minutes of the OSA drafting group of Bristol
|
23.127
|
|
|
|
Approved. This report asks for approval of the following tdocs: S2-001548, S2-001619, S2-001605, S2-001634, S2-001624, S2-001625, S2-001626, S2-001627, S2-001628, S2-001629, S2-001630
|
6 OSA
|
S2-001548
|
OSA drafting
|
Support of services for roaming users
|
|
|
|
|
Approved.
|
6 OSA
|
S2-001605
|
OSA drafting
|
Service Control Interface Protocols
|
|
|
|
|
Approved.
|
6
|
S2-001619
|
OSA drafting
|
Support of services for roaming users (2)
|
|
|
|
|
Approved.
|
6 OSA
|
S2-001634
|
Ericsson
|
Change of TS 23.127 title for version 4.0 and up
|
23.127
|
011r1
|
D
|
R00
|
Approved.
|
6 OSA
|
S2-001624
|
Siemens
|
CR on Parlay-OSA alignment: basic service interface
|
23.127
|
012
|
F
|
R99
|
Approved.
|
6 OSA
|
S2-001625
|
Siemens
|
CR on Parlay-OSA alignment: initial contact interfaces
|
23.127
|
013
|
F
|
R99
|
Approved.
|
6 OSA
|
S2-001626
|
Siemens
|
CR on Parlay-OSA alignment : access SCF
|
23.127
|
014
|
F
|
R99
|
Approved.
|
6 OSA
|
S2-001627
|
Siemens
|
CR on Parlay-OSA alignment: load manager SCF
|
23.127
|
015
|
F
|
R99
|
Approved.
|
6 OSA
|
S2-001628
|
Siemens
|
CR on Parlay-OSA alignment: fault manager SCF
|
23.127
|
016
|
F
|
R99
|
Approved.
|
6 OSA
|
S2-001629
|
Siemens
|
CR on Parlay-OSA alignment: service factory SCF
|
23.127
|
017
|
F
|
R99
|
Approved.
|
6 OSA
|
S2-001630
|
Siemens
|
CR on Parlay-OSA alignment: authentication interface
|
23.127
|
018
|
F
|
R99
|
Approved.
|
6 OSA
|
S2-001622
|
OSA
|
Discovery of local services in Visited Network
|
23.127
|
|
|
|
Revised to S2-001549.
|
6 OSA
|
S2-001549
|
Alcatel
|
Discovery of local services in Visited Network
|
|
|
|
|
Not approved. Postponed to the next OSA drafting.
|
6OSA
|
S2-001301
|
Lucent
|
Service control architecture
|
|
|
|
|
Handled by OSA drafting group.
|
6OSA
|
S2-001302
|
Lucent
|
Service flow list
|
|
|
|
|
Handled by OSA drafting group.
|
3
|
S2-001380
|
S1-000567
|
LS to VHE/OSA on Support of VHE User Profiles
|
|
|
|
|
Handled by OSA drafting group.
|
3
|
S2-001429
|
T3-000435
|
LS to S2 VHE/OSA on Support of Bookmarks / VHE User Profiles
|
|
|
|
|
Handled by OSA drafting group.
|
6OSA
|
S2-001479
|
Ericsson
|
Change of TS 23.127 title for version 4.0 and up
|
23.127
|
011
|
D
|
R01
|
Handled by OSA drafting group.
|
6OSA
|
S2-001480
|
Ericsson
|
OSA stage 1 requirements to be addressed by S2
|
|
|
|
|
Handled by OSA drafting group.
|
6OSA
|
S2-001492
|
Motorola
|
- not provided -
|
|
|
|
|
Handled by OSA drafting group.
|
5.3
|
S2-001366
|
Ericsson
|
23.226 Global Text telephony, Stage 2
|
23.226
|
|
|
|
Noted.
|
5.3
|
S2-001367
|
Ericsson
|
Global Text Telephony status and planning
|
23.226
|
|
|
|
23.226 cannot be raised to v.1.0. Companies are invited to contribute on the issue.
|
5.3
|
S2-001368
|
Ericsson
|
22.226 Global Text telephony Stage 1
|
22.226
|
|
|
|
Noted.
|
|
S2-001653
|
Ericsson
|
LS on Cellular Text telephone Modem approval from T1P1.3
|
|
|
|
|
Not handled.
|
5.3
|
S2-001495
|
Motorola
|
Push Service
|
23.874
|
|
|
|
|
5.3
|
S2-001496
|
Motorola
|
Push Service Considerations
|
23.874
|
|
|
|
|
|
S2-001647
|
NTT
|
Current status and work plan for the feasibility study of an architecture for push service
|
|
|
|
|
Approved in principle, but the version of the TR will depend of the content of the TR itself.
|
|
S2-001649
|
NTT
|
23.874 v.0.0.3 on Push services
|
23.874
|
|
|
|
Raised in v.1 in S2-001659.
|
|
S2-001659
|
NTT
|
23.874 v.1.0.0 on Push services
|
23.874
|
|
|
|
Approved. To be presented to SA#9.
|
|
S2-001648
|
NTT
|
Proposed change to WI: A feasibility study of an architecture for network requested PDP context activation with User-ID
|
|
|
|
|
Revised to S2-001660.
|
|
S2-001660
|
NTT
|
Proposed change to WI: A feasibility study of an architecture for network requested PDP context activation with User-ID
|
|
|
|
|
Approved. To be presented to SA#9.
|
|
S2-001565
|
QoS Convenor
|
Minutes of the drafting meeting on QoS
|
|
|
|
|
Noted. See individual conclusions bellow.
|
|
S2-001565
|
QoS convenor
|
Minutes of QoS drafting
|
|
|
|
|
|
6QoS 3
|
S2-001379
|
S1-000503
|
LS on Service Modification without Pre-Notification
|
|
|
|
|
For QoS drafting group: handled together with next document.
|
3
|
S2-001410
|
N3-000278
|
LS on Service Modification without pre-notification
|
|
|
|
|
Proposed answer in S2-001518.
|
3
|
S2-001518
|
Nokia
|
LS response to S1, N3 on Service Modification without pre-notification”
|
|
|
|
|
Approved.
|
3
|
S2-001389
|
R3-001963
|
LS on RAB Assignment QoS Negotiation
|
|
|
|
|
Handled together with next LS. Handled by QoS drafting group.
|
3
|
S2-001383
|
S1-000611
|
LS on Applications on external devices (response to Tdoc SP-00353)
|
|
|
|
|
Handled with S2-001505. T2 has answered (we’re missing they reply). The original SA LS has also to be found out.
|
3
|
S2-001503
|
Nortel
|
Related to LS in 1383
|
|
|
|
|
Not handled.
|
3
|
S2-001505
|
Nortel
|
Related to LS in 1389
|
|
|
|
|
Proposed answer to S2-001389 and 1383 (taking into account this tdoc) in S2-001551. Handled by QoS drafting group.
|
|
S2-001551
|
QoS related
|
|
|
|
|
|
Editorially revised to S2-001651.
|
|
S2-001651
|
SA2
|
LS
|
|
|
|
|
For e-mail approval.
|
3
|
S2-001417
|
S5-000353
|
LS on 2G/3G QoS profiles
|
|
|
|
|
Proposed answer in S2-001566. Handled by QoS drafting group.
|
|
S2-001566
|
SA2
|
LS answer to S2-001566
|
|
|
|
|
Approved.
|
|
S2-001550
|
Ericsson
|
QoS End-to-End Functional Architecture
|
23.107
|
|
|
R00
|
Revised to S2-001560. For QoS drafting.
|
|
S2-001560
|
Ericsson
|
QoS End-to-End Functional Architecture
|
23.107
|
|
|
R00
|
Revised to S2-001561.
|
|
S2-001561
|
QoS drafting
|
QoS End-to-End Functional Architecture
|
23.107
|
023r1
|
B
|
R00
|
Not approved: no need yet to raise 23.107 to v.4.
|
|
S2-001561
|
Ericsson
|
QoS End-to-End Functional Architecture
|
23.107
|
023r1
|
|
R00
|
S2 approved the CR from a technical point of view (excluding the technical notes). However, it cannot be approved officially because it is adding too many editorial notes: once a document is in version 3 or above, it cannot contain so many unstable sections as proposed here.
Companies are asked to contribute on the basis of this CR: the S2 intention is to solve all the editorial notes as soon as possible so that the CR can be officially approved.
All the CRs on R00 are not approved, because there is no need to create a Release 2000 version right now because CR023r1 was not approved.
|
6QoS
|
S2-001497
|
Motorola
|
Attribute and parameter terminology
|
23.107
|
026
|
|
R99
|
Revised to S2-001553. Handled by QoS drafting group.: revised to S2-001553.
|
6qos
|
S2-001553
|
Motorola
|
Attribute and parameter
|
23.107
|
026r1
|
|
R99
|
Revised to S2-001562 (CR for R99) and S2-001554 (CR for R00). For QoS drafting group
|
6qos
|
S2-001562
|
Motorola
|
Attribute and parameter
|
23.107
|
026r2
|
|
R99
|
Approved.
|
6qos
|
S2-001554
|
Motorola
|
Attribute and parameter
|
23.107
|
032
|
|
R00
|
Not approved: no need yet to raise 23.107 to v.4.
|
6QoS
|
S2-001498
|
Motorola
|
Informational content on clause 6.2
|
23.107
|
027
|
|
R99
|
Handled by QoS drafting group.
|
6qos
|
S2-001555
|
Motorola
|
Informational content in clause 6.2
|
23.107
|
027r1
|
|
R99
|
Approved.
|
6qos
|
S2-001556
|
Motorola
|
Informational content in clause 6.2
|
23.107
|
031
|
|
R00
|
Not approved: no need yet to raise 23.107 to v.4.
|
6QoS
|
S2-001499
|
Motorola
|
Requirements clarifications
|
23.107
|
028
|
|
R99
|
Revised to S2-001557. Handled by QoS drafting group.
|
6qos
|
S2-001557
|
Motorola
|
Requirements clarifications
|
|
|
|
|
For e-mail approval.
|
6QoS
|
S2-001500
|
Motorola
|
Traffic class editorial corrections
|
23.107
|
029
|
|
R99
|
Revised to S2-001559. Handled by QoS drafting group.
|
6qos
|
S2-001559
|
Motorola
|
Traffic class editorial corrections
|
23.107
|
029r1
|
|
R99
|
Revised to S2-001563 (R99)and S2-001564 (R00)
|
6qos
|
S2-001563
|
Motorola
|
Traffic class editorial corrections
|
23.107
|
029r2
|
|
R99
|
Approved.
|
6qos
|
S2-001564
|
Motorola
|
Traffic class editorial corrections
|
23.107
|
030
|
|
R00
|
Not approved: no need yet to raise 23.107 to v.4.
|
|
S2-001303
|
Lucent
|
SIP with QoS
|
|
|
|
|
Noted by QoS drafting.
|
6QoS
|
S2-001365
|
Nokia
|
End-to-End QoS Notifications between UE and GGSN
|
23.107
|
025
|
B
|
R00
|
Not approved. Handled by QoS drafting group.
|
6QoS
|
S2-001370
|
Fujitsu
|
Introduction of packet delay variation
|
|
|
|
|
Not Approved. Handled by QoS drafting group.
|
6QoS
|
S2-001446
|
Ericsson
|
Resource manager
|
|
|
|
|
Not approved. Handled by QoS drafting group.
|
6QoS
|
S2-001447
|
Ericsson
|
QoS End-to-End Functional Architecture (that is an update of CR23 to 23.107)
|
|
|
|
|
Handled by QoS drafting group.
|
6QoS
|
S2-001511
|
Motorola
|
Streaming delay
|
|
|
|
|
Noted. Handled by QoS drafting group.
|
6qos
|
S2-001539
|
AT&T
|
QoS optionality
|
|
|
|
|
Not approved. Handled by QoS drafting group.
|
|
S2-001552
|
QoS related
|
|
|
|
|
|
|
|
S2-001558
|
QoS related
|
|
|
|
|
|
|
|
S2-001567
|
- 1567 to 1599: not allocated -
|
|
|
|
|
|
|
3
|
S2-001441
|
S1-000679 (not yet approved)
|
LS to RAN2 (Cc S2) regarding Open Interfaces within the UTRAN for LCS Support
|
|
|
|
|
Handled by LCS drafting group.
|
3
|
S2-001470
|
S1-000680 (not agreed yet)
|
LS to TSG-GERAN regarding Open Interfaces within the GERAN for LCS Support
|
|
|
|
|
Handled by LCS drafting group.
|
|
S2-001645
|
LCS convenor
|
Meeting report of the S2 LCS drafting session 7.9.2000
|
|
|
|
|
Noted. See individual conclusions on the tdocs handled by this drafting.
|
|
S2-001646
|
LCS
|
LS to R2 (Cc S1, R3) regarding an open interface between the SMLC and the SRNC within the UTRAN for LCS Support
|
|
|
|
|
For e-mail approval.
To be approved by e-mail by 18th September because some companies had already left the meeting when the LS was presented!
This process is accepted as an exceptional case.
|
|
S2-001644
|
Nokia
|
Communication between the core and access networks
|
23.171
|
?
|
|
|
Editorially revised to S2-001656.
|
|
S2-001656
|
Nokia
|
Communication between the core and access networks
|
23.171
|
004
|
D
|
R99
|
Approved.
|
|
S2-001657
|
Editor
|
|
23.271
|
|
|
|
For e-mail approval. To be presented to SA in version 1. To be sent by e-mail on 11th, deadline for comment 15th.
|
6 LCS
|
S2-001354
|
Siemens
|
Alignment of Geographic Shape Description with ITU-T and ANSI
|
03.32
|
A007
|
F
|
R98
|
Handled by LCS drafting group.
|
6 LCS
|
S2-001355
|
Siemens
|
Alignment of Geographic Shape Description with ITU-T and ANSI
|
23.032
|
002
|
F
|
R99
|
Handled by LCS drafting group.
|
6LCS
|
S2-001376
|
Editor (Nokia)
|
Functional stage 2 description of LCS
|
23.271 v. 0.1.0
|
|
|
|
Handled by LCS drafting group.
|
6LCS
|
S2-001440
|
Qualcomm
|
The support of an open interface to the SMLC within the 3GPP UTRAN LCS
Specifications
|
|
|
|
|
Handled by LCS drafting group.
|
6QoS
|
S2-001445
|
Ericsson
|
IP Specific Elements in PDP Context Activation/Modification
|
|
|
|
|
Handled by QoS drafting group.
|
6LCS
|
S2-001471
|
Nokia
|
Editorial changes to 23.271
|
|
|
|
|
Handled by LCS drafting group.
|
6LCS
|
S2-001472
|
Nokia
|
On changes in PS LCS
|
|
|
|
|
Handled by LCS drafting group.
|
6LCS
|
S2-001473
|
Nokia
|
Moving Iu description from 23.171 to 25.305
|
23.171
|
003
|
|
R99
|
Handled by LCS drafting group.
|
6LCS
|
S2-001486
|
Fujitsu
|
- not provided -
|
|
|
|
|
Handled by LCS drafting group.
|
6LCS
|
S2-001487
|
Fujitsu
|
- not provided -
|
|
|
|
|
Handled by LCS drafting group.
|
6LCS
|
S2-001488
|
Fujitsu
|
- not provided -
|
|
|
|
|
Handled by LCS drafting group.
|
6LCS
|
S2-001489
|
Fujitsu
|
- not provided -
|
|
|
|
|
Handled by LCS drafting group.
|
6LCS
|
S2-001501
|
NTT DoCoMo
|
Proposed Work schedule for Location Service
|
|
|
|
|
Handled by LCS drafting group. Taken into account in the revised version of the work plan.
|
6LCS
|
S2-001617
|
Nokia
|
LCS agenda
|
|
|
|
|
Handled by LCS drafting group.
|
6split
|
S2-001377
|
WI rapporteur (Ericsson)
|
Minutes of Split Architecture Drafting in Stockholm
|
23.873
|
|
|
|
For SGSN split drafting group.
|
|
S2-001640
|
Drafting on Split GSN
|
Minutes of the drafting group
|
|
|
|
|
Revised to S2-001655.
Previous version of 23.873 is in S2-001378.
The next ad-hoc meeting is proposed to take place in Vancouver, hosted by Motorola, 17th to 19th of October.
|
|
S2-001655
|
Split archi convenor
|
|
|
|
|
|
Approved (to be sent by e-mail).
|
6split
|
S2-001378
|
WI rapporteur (Ericsson)
|
TR 23.873 v0.1.0
|
23.873 v0.1.0
|
|
|
|
Approved.
|
|
S2-001652
|
Editor
|
23.873 v.0.2.0
|
|
|
|
|
To be sent by e-mail before 12th and approved by 15th.
|
7
|
S2-001352
|
MCC
|
Work Plan v. Aug. 25
|
|
|
|
|
|
|
S2-001650
|
NTT
|
Invitation for S2#15
|
|
|
|
|
Noted.
|
5.3
|
S2-001450
|
Lucent
|
Term to describe RAN+SGSN+GGSN
|
|
|
|
|
For e-mail approval.
|
|
S2-001642
|
MCC
|
Other term to refer to RAN+SGSN+GGSN
|
|
|
|
|
For e-mail approval.
|
5.3
|
S2-001399
|
Alcatel
|
Removal of unnecessary features of Cx interface
|
23.228
|
|
|
R00
|
For e-mail approval.
|
WI
|
S2-001401
|
Alcatel
|
Impacts of SGSN split
|
|
|
|
R0x
|
|
5.3
|
S2-001402
|
Alcatel
|
|
23.228
|
|
|
R00
|
|
5
|
S2-001404
|
Alcatel
|
Iu user plane in the CS core network
|
|
|
|
|
For e-mail approval.
|
5
|
S2-001451
|
Lucent
|
TS 23.228 V0.1.0 IM Subsystem Stage 2
|
|
|
|
|
|
5.1
|
S2-001461
|
Ericsson
|
Architectural Principles for Release 2000
|
23.121
|
|
B
|
R00
|
|
5.3
|
S2-001475
|
Nokia
|
Introducing flexibility to the Iu interface
|
|
|
|
|
For e-mail approval.
|
5.3
|
S2-001483
|
AT&T
|
Proxy CSCF reassignement
|
|
|
|
|
For e-mail approval.
|
7
|
S2-001502
|
Lucent
|
Title of 23.121
|
23.121
|
|
|
|
For e-mail approval.
|
|
S2-001544
|
3Com
|
Removing Proxy CSCF from signalling path
|
|
|
|
|
For e-mail approval.
|
|
S2-001545
|
3Com
|
CSCF definitions
|
|
|
|
|
For e-mail approval.
|
5.2
|
S2-001600
|
Ericsson
|
Single MS ISDN
|
|
|
|
|
|
4
|
S2-001363
|
Vodafone
|
Withdrawn
|
23.060
|
171
|
?
|
?
|
Revised to S2-001523
|
4
|
S2-001364
|
Vodafone
|
Withdrawn
|
23.060
|
172
|
?
|
?
|
Revised to S2-001524
|
|
S2-001369
|
Korea Telecom
|
Withdrawn
|
|
|
|
|
|
5.3
|
S2-001395
|
Alcatel
|
Local service
|
23.228
|
|
|
R00
|
Withdrawn
|
5.3
|
S2-001403
|
Alcatel
|
Use of Firewall CSCFs (role of I-CSCF)
|
23.228
|
|
|
R00
|
Handled by drafting.
|
3
|
S2-001421
|
N4-000549
|
LS on Architectural Impact of Combined MAP Signaling for Mobility Management
|
|
|
|
|
Withdrawn.
|
4
|
S2-001477
|
Alcatel
|
Correction to Data Retrieve protocol stacks endpoints
|
23.121
|
059
|
|
R99
|
Replaced by 1512
|
5.3
|
S2-001478
|
Alcatel
|
Correction to Data Retrieve protocol stacks endpoints
|
23.121
|
060
|
|
R00
|
Replaced by 1513
|
|
S2-001506
|
Siemens
|
Withdrawn
|
|
|
|
|
|
5.1
|
S2-001507
|
Motorola
|
Withdrawn, replaced by 1541
|
|
|
|
|
|