3GPP
TSG-SA WG1 Meeting #60 S1-124002
Edinburgh,
UK, 12th – 16th November 2012
Title: SA1 agenda
with document allocation
Source: SA1 Chairman/SA1 Vice
Chairmen/MCC
Contact: Mona Mustapha
[mona.mustapha@vodafone.com]
SA1 AGENDA
1 Opening of the meeting |
||||||
1.1 Agenda and scheduling |
||||||
AGE |
Chairman |
Draft SA1#60 Agenda |
Revised to S1-124001 |
|
||
AGE |
Chairman |
Draft SA1#60 Schedule and Agenda with document allocation |
Revised to S1-124002 |
Revision of S1-124000. |
||
AGE |
Chairman |
Final SA1#60 Schedule and Agenda with document allocation |
Approved |
Revision of S1-124000. Revision of S1-124001. |
||
1.2 IPR |
||||||
|
The attention of the delegates to this meeting is drawn to the fact that 3GPP Individual Members have the obligation under the Members are hereby invited: - to investigate whether their companies owns IPRs which are, or are likely to become essential in respect of the work of 3GPP. - to
notify the Director-General or the Chairman of their Organizational Partners,
of all potential IPRs that their companies may own, by means of the
appropriate |
|
||||
1.3 Previous SA1 meeting report |
||||||
REP |
ETSI Secretariat |
Draft Minutes of SA1#59 |
Revised to S1-124005 |
|
||
REP |
ETSI Secretariat |
Draft Minutes of SA1#59 |
Approved |
Revision of S1-124004. No presentation |
||
1.4 Working agreements |
||||||
None |
||||||
2 Issues for early consideration |
||||||
3.4 Mechanism to disable PWS for Rel-11 4 Liaison Statements ·
MSISDNless SMS ·
SIPTO 5.2 New Work Items ·
Operator Determined
Barring |
||||||
3 Reports and action items |
||||||
3.1 Report from SA |
||||||
REP |
Chairman |
SA1-related topics at SA#57 |
Noted |
Noted without presentation |
||
3.2 Report from SA1 GCSE_LTE ad hoc meeting (8 – 9 November 2012) |
||||||
REP |
Rapporteur (NSN) |
GCSE_LTE ad hoc report to SA1 |
Noted |
|
||
TS |
Rapporteur (NSN) |
Draft TS 22.468 |
Agreed |
Agreed as the basis for future contributions |
||
REP |
ETSI Secretariat |
Draft Minutes of GCSE_LTE Ad Hoc Meeting |
Noted |
|
||
3.3 Authentication for Common IMS |
||||||
Action Item SA1#51/1 (Action Point from SA#48: AP 48/1) SA WG1 were asked to work on updating the harmonized authentication requirements for Common IMS. The authentication requirements were never harmonized to reflect the Common IMS, and this makes almost impossible to contribute on the issue properly. Proposal to close this action item |
||||||
3.4 Mechanism to disable PWS for Rel-11 |
||||||
Action Item SA1#57/7 (unofficial action from SA#54) SA1 to define requirements for disabling PWS in Rel-11, to determine if the requirements can be applicable to frozen releases and to inform other groups of the requirements. See SP-110890 LS from SA on PWS support in 3GPP UEs. |
||||||
TO |
S1-122300/C1-121617/S1-121227 (Vodafone) |
LS on Disabling receipt of PWS Warning Notifications |
Noted, answer in S1-124194 |
Postponed from SA1#58 CT1 asks if scenario where UEs are configured to display secured PWS notifications in HPLMN and also to display unsecured notifications on a VPLMN is needed. |
||
LS OUT |
|
LS on Disabling receipt of PWS Warning Notifications |
Revised to S1-124199 |
Answer to S1-124250. |
||
LS OUT |
|
LS on Disabling receipt of PWS Warning Notifications |
Revised to S1-124440 |
Answer to S1-124250. Revision of S1-124194. |
||
LS OUT |
|
LS on Disabling receipt of PWS Warning Notifications |
Approved |
Answer to S1-124250. Revision of S1-124194. Revision of S1-124199. No presentation |
||
Cont |
Vodafone |
PWS - Proposed revision of USIM settings |
Noted |
|
||
CR |
Vodafone |
22.268 v11.4.0: Disabling receipt of PWS Warning Notifications |
Revised to S1-124331 |
WI code TEI11 Rel-11 CR0039R- Cat F |
||
CR |
Vodafone |
22.268 v11.4.0: Disabling receipt of PWS Warning Notifications |
Revised to S1-124198 |
WI code TEI11 Rel-11
CR0039R- Cat F Revision of S1-124085. |
||
CR |
Vodafone |
22.268 v11.4.0: Disabling receipt of PWS Warning Notifications |
Agreed |
WI code TEI11 Rel-11
CR0039R- Cat F Revision of S1-124085. Revision of S1-124331. |
||
CR |
Vodafone |
22.268 v12.0.0: Disabling receipt of PWS Warning Notifications |
Noted |
WI code TEI11 Rel-11 CR0040R- Cat A |
||
3.5 Public safety work status update |
||||||
Action Item SA1#60/1 (unofficial action from SA#57) SA1 to provide status update of public safety work to RAN from the SA1 Edinburgh meeting. This will allow RAN to plan their Rel-12 work. |
||||||
4 Liaison Statements (including related contributions) |
||||||
TO |
ETSI HF(12)59_016 |
LS on Mandate M 376 on "European accessibility requirements for public procurement of products and services in the ICT domain" |
Noted |
|
||
TO |
S5-122480 (Huawei) |
LS on modification of term “3G” in SA5 specifications |
Noted |
(Action to SA1 has been udpated) SA5 welcomes any comments from SA1 on the replacement of the term “3G” to another more generic term in SA5 specifications |
||
LS OUT |
Bell Canada |
LS to SA2 on PTT |
Withdrawn |
|
||
TO |
S1-122316/S2-123369 (NSN) |
LS on SMS to MSISDN-less IMS UE from a UE |
Noted, answer in S1-124358 |
Postponed from SA1#59 SA2 asks SA1 if MT SMS for MSISDNless UEs is needed, and if so whether any restrictions can be placed upon the user as to the destination address entered. |
||
Cont |
Nokia Siemens Networks |
Handling of SMS from MSISDN-less IMS UE |
Noted |
|
||
CR |
Nokia Siemens Networks |
22.101 v12.2.0: MSISDN-less SMS Handling |
Revised to S1-124346 |
WI code MTCe-SRM Rel-12 CR0433R- Cat C |
||
CR |
Nokia Siemens Networks |
22.101 v12.2.0: MSISDN-less SMS Handling |
Revised to S1-124359 |
WI code MTCe-SRM
Rel-12 CR0433R- Cat C Revision of S1-124079. |
||
CR |
Nokia Siemens Networks |
22.101 v12.2.0: MSISDN-less SMS Handling |
Revised to S1-124453 |
WI code MTCe-SRM
Rel-12 CR0433R- Cat C Revision of S1-124079. Revision of S1-124346. |
||
CR |
Nokia Siemens Networks |
22.101 v12.2.0: MSISDN-less SMS Handling |
Revised to S1-124499 |
WI code MTCe-SRM
Rel-12 CR0433R- Cat C Revision of S1-124079. Revision of S1-124346. Revision of S1-124359. |
||
CR |
Nokia Siemens Networks |
22.101 v12.2.0: MSISDN-less SMS Handling |
Revised to S1-124504 |
WI code MTCe-SRM
Rel-12 CR0433R- Cat C Revision
of S1-124079. Revision of S1-124346. Revision of S1-124359. Revision of S1-124453. |
||
CR |
Nokia Siemens Networks |
22.101 v12.2.0: MSISDN-less SMS Handling |
Agreed |
WI code MTCe-SRM
Rel-12 CR0433R- Cat C Revision
of S1-124079. Revision of S1-124346. Revision of S1-124359. Revision of S1-124453. Revision of S1-124499. No presentation |
||
CR |
Nokia Siemens Networks |
22.101 v11.7.0: MSISDN-less SMS Handling |
Revised to S1-124500 |
WI code TEI-11 Rel-11 CR0439R- Cat F |
||
CR |
Nokia Siemens Networks |
22.101 v11.7.0: MSISDN-less SMS Handling |
Withdrawn |
WI code TEI-11 Rel-11 CR0439R- Cat F Revision of S1-124461. |
||
LS OUT |
Nokia Siemens Networks |
Answer LS on SMS to MSISDN-less IMS UE from a UE |
Revised to S1-124344 |
Response to: LS S1-122316 / S2-123369 on LS on SMS to MSISDN-less IMS UE from a UE from SA2 |
||
LS OUT |
Nokia Siemens Networks |
Answer LS on SMS to MSISDN-less IMS UE from a UE |
Revised to S1-124358 |
Response to: LS S1-122316
/ S2-123369 on LS on SMS to MSISDN-less IMS UE from a UE from SA2 Revision of S1-124078. |
||
LS OUT |
Nokia Siemens Networks |
Answer LS on SMS to MSISDN-less IMS UE from a UE |
Approved |
Response to: LS S1-122316
/ S2-123369 on LS on SMS to MSISDN-less IMS UE from a UE from SA2 Revision of S1-124078. Revision of S1-124344 |
||
LS OUT |
Nokia Siemens Networks |
Answer LS on SMS to MSISDN-less IMS UE from a UE |
Withdrawn |
|
||
LS OUT |
Huawei |
Reply LS on SMS to MSISDN-less IMS UE from a UE |
Noted |
Response to: LS (SA2-123369 / S1-124251) on SMS to MSISDN-less IMS UE from a UE |
||
TO |
S1-122318/S2-123394 (NEC) |
LS on SIPTO Requirement Clarification |
Noted, answer in S1-124442 |
Postponed from SA1#59 SA2 asks SA1 to consider requirement on SIPTO support for pre-Rel-10 UEs to an APN granularity, as per flow offload can only be supported by Rel-12 UEs. |
||
WID |
NEC |
WID proposal for SIPTO Control of HeNBs |
Noted |
|
||
CR |
NEC, Softbank Mobile |
22.220 v11.6.0: Clarifications on SIPTO per IP flow requirements for HeNB |
Revised to S1-124428 |
WI code TEI11 Rel-11 CR0159R- Cat C |
||
CR |
NEC, Softbank Mobile |
22.220 v11.6.0: Clarifications on SIPTO per IP flow requirements for HeNB |
Noted |
WI code TEI11 Rel-11
CR0159R- Cat C Revision of S1-124048. |
||
CR |
Huawei, Intel |
22.101 v10.9.0: SIPTO per APN for pre-Rel 10 UEs |
Revised to S1-124311 |
WI code TEI10 Rel-10 CR0425R1 Cat F |
||
CR |
Huawei, Intel |
22.101 v10.9.0: SIPTO per APN for pre-Rel 10 UEs |
Revised to S1-124443 |
WI code TEI10 Rel-10
CR0425R1 Cat F Revision of S1-124111. |
||
CR |
Huawei, Intel |
22.101 v10.9.0: SIPTO per APN for pre-Rel 10 UEs |
Revised to S1-124496 |
WI code TEI10 Rel-10
CR0425R1 Cat F Revision of S1-124111. Revision of S1-124311. |
||
CR |
Huawei, Intel |
22.101 v10.9.0: SIPTO per APN for pre-Rel 10 UEs |
Agreed |
WI code TEI10 Rel-10
CR0425R1 Cat F Revision of S1-124111. Revision of S1-124311. Revision of S1-124443. No presentation |
||
CR |
Huawei, Intel |
22.101 v11.7.0: SIPTO per APN for pre-Rel 10 UEs |
Revised to S1-124312 |
WI code TEI10 Rel-11 CR0427R1 Cat A |
||
CR |
Huawei, Intel |
22.101 v11.7.0: SIPTO per APN for pre-Rel 10 UEs |
Revised to S1-124444 |
WI code TEI10 Rel-11
CR0427R1 Cat A Revision of S1-124112. |
||
CR |
Huawei, Intel |
22.101 v11.7.0: SIPTO per APN for pre-Rel 10 UEs |
Revised to S1-124497 |
WI code TEI10 Rel-11
CR0427R1 Cat A Revision of S1-124112. Revision of S1-124312. |
||
CR |
Huawei, Intel |
22.101 v11.7.0: SIPTO per APN for pre-Rel 10 UEs |
Agreed |
WI code TEI10 Rel-11
CR0427R1 Cat A Revision of S1-124112. Revision of S1-124312. Revision of S1-124444. No presentation |
||
CR |
Intel, Huawei |
22.101 v12.2.0: SIPTO per APN for pre-Rel 10 UEs |
Revised to S1-124313 |
WI code TEI10 Rel-12 CR0428R1 Cat A |
||
CR |
Intel, Huawei |
22.101 v12.2.0: SIPTO per APN for pre-Rel 10 UEs |
Withdrawn |
WI code TEI10 Rel-12
CR0428R1 Cat A Revision of S1-124113. |
||
LS OUT |
Huawei |
DRAFT Reply LS on SIPTO requirement clarification |
Revised to S1-124442 |
Response to: LS (S2-123394/ S1-122318) on SIPTO requirement clarification |
||
LS OUT |
Huawei |
DRAFT Reply LS on SIPTO requirement clarification |
Revised to S1-124498 |
Response to: LS (S2-123394/ S1-122318) on SIPTO requirement clarification Revision of S1-124110. |
||
LS OUT |
Huawei |
DRAFT Reply LS on SIPTO requirement clarification |
Approved |
Response to: LS (S2-123394/ S1-122318) on SIPTO requirement clarification Revision of S1-124110. Revision of S1-124442. No presentation |
||
Operator
initiated registration |
||||||
TO |
C1-123086 (Deutsche Telekom) |
LS on Operator initiated registration |
Noted, answer in S1-124335 |
On the Stage-1 requirement in 22.228 to allow the network to request a UE to register to IMS has been met, CT1 asks: 1) Whether the requirements in 24.229, subclause L.3.1.2 and B.3.1.2 satisfy the Stage-1 requirement 2) If the answer to Question-1 is "no", then for which use case the Stage-1 requirement is defined |
||
LS OUT |
Deutsche Telekom |
LS on Operator initiated registration |
Revised to S1-124450 |
Answer to S1-124256. |
||
LS OUT |
Deutsche Telekom |
LS on Operator initiated registration |
Approved |
Answer to S1-124256. Revision of S1-124335. No presentation |
||
CR |
Deutsche
Telekom, Nokia Siemens Networks |
22.228 v8.6.0: Removal of operator initiated IMS registration |
Revised to S1-124445 |
WI code TEI8 Rel-8 CR0176R- Cat C |
||
CR |
Deutsche
Telekom, Nokia Siemens Networks |
22.228 v8.6.0: Removal of operator initiated IMS registration |
Agreed |
WI code TEI8 Rel-8
CR0176R- Cat C Revision of S1-124336. No presentation |
||
CR |
Deutsche Telekom,
Nokia Siemens Networks |
22.228 v9.3.0: Removal of operator initiated IMS registration |
Revised to S1-124446 |
WI code TEI8 Rel-9 CR0177R- Cat A |
||
CR |
Deutsche
Telekom, Nokia Siemens Networks |
22.228 v9.3.0: Removal of operator initiated IMS registration |
Agreed |
WI code TEI8 Rel-9 CR0177R- Cat A Revision of S1-124337. No presentation |
||
CR |
Deutsche Telekom,
Nokia Siemens Networks |
22.228 v10.4.1: Removal of operator initiated IMS registration |
Revised to S1-124447 |
WI code TEI8 Rel-10 CR0178R- Cat A |
||
CR |
Deutsche
Telekom, Nokia Siemens Networks |
22.228 v10.4.1: Removal of operator initiated IMS registration |
Agreed |
WI code TEI8 Rel-10 CR0178R- Cat A Revision of S1-124338. No presentation |
||
CR |
Deutsche
Telekom, Nokia Siemens Networks |
22.228 v11.5.0: Removal of operator initiated IMS registration |
Revised to S1-124448 |
WI code TEI8 Rel-11 CR0179R- Cat A |
||
CR |
Deutsche
Telekom, Nokia Siemens Networks |
22.228 v11.5.0: Removal of operator initiated IMS registration |
Agreed |
WI code TEI8 Rel-11 CR0179R- Cat A Revision of S1-124339. No presentation |
||
CR |
Deutsche
Telekom, Nokia Siemens Networks |
22.228 v12.3.0: Removal of operator initiated IMS registration |
Revised to S1-124449 |
WI code TEI8 Rel-12 CR0180R- Cat A |
||
CR |
Deutsche
Telekom, Nokia Siemens Networks |
22.228 v12.3.0: Removal of operator initiated IMS registration |
Agreed |
WI code TEI8 Rel-12 CR0180R- Cat A Revision of S1-124340. No presentation |
||
SA3 |
||||||
TO |
S3-121213 |
LS on PWS Security in GERAN CS |
Noted, answer in S1-124345 |
|
||
LS OUT |
Ericsson |
LS on PWS Security in GERAN CS |
Revised to S1-124451 |
Answer to S1-124328. |
||
LS OUT |
Ericsson |
LS on PWS Security in GERAN CS |
Revised to S1-124505 |
Answer to S1-124328. Revision of S1-124345. |
||
LS OUT |
Ericsson |
LS on PWS Security in GERAN CS |
Approved |
Answer to S1-124328. Revision of S1-124345. Revision of S1-124451. No presentation |
||
TO |
S3-121214 |
LS on Request Clarification of PWS Security Requirements |
Noted, answer in S1-124347 |
|
||
LS OUT |
DOCOMO |
LS on Request Clarification of PWS Security Requirements |
Revised to S1-124467 |
Answer to S1-124329. |
||
LS OUT |
DOCOMO |
LS on Request Clarification of PWS Security Requirements |
Approved |
Answer to S1-124329. Revision of S1-124347. No presentation |
||
CR |
Sprint, AT&T, Vodafone, NTT DOCOMO |
22.268 v12.0.0: Clarification of conditions of PWS Security requirements |
Revised to S1-124468 |
WI code PWS_Sec Rel-12 CR0040R1 Cat F |
||
CR |
Sprint, AT&T, Vodafone, NTT DOCOMO |
22.268 v12.0.0: Clarification of conditions of PWS Security requirements |
Agreed |
WI code PWS_Sec Rel-12 CR0040R1 Cat F Revision of S1-124332. No presentation |
||
TO |
S3-121239 |
LS on iFIRE and SMURF Architecture and Requirements |
Noted, answer in S1-124348 |
|
||
LS OUT |
Ericsson |
LS on iFIRE and SMURF Architecture and Requirements |
Revised to S1-124501 |
Answer to S1-124330. |
||
LS OUT |
Ericsson |
LS on iFIRE and SMURF Architecture and Requirements |
Approved |
Answer to S1-124330. Revision of S1-124348. No presentation |
||
Dialled
digit information in Emergency Calls |
||||||
TO |
C1-124133 (Telecom Italia) |
LS on Use of Dialled Digit Information in Emergency Calls |
Postponed |
CT1 asks SA1: is there a need for the information contained in the dialled digit string from the user to be sent from the UE for an emergency call request in the IMS, to be used by either the public network for routing purposes, or by the PSAP and its own associated network (if any), for routing or other purposes? And if so, for what reason? |
||
LS OUT |
Telecom Italia |
LS on Use of Dialled Digit Information in Emergency Calls |
Revised to S1-124457 |
Answer to S1-124259. |
||
LS OUT |
Telecom Italia |
LS on Use of Dialled Digit Information in Emergency Calls |
Noted |
Answer to S1-124259. Revision of S1-124350. |
||
CR |
Telecom Italia |
22.101 v12.2.0: Requirement on emergency IM CN service |
Revised to S1-124349 |
WI code TEI11 Rel-11 CR0435R- Cat F |
||
CR |
Telecom Italia |
22.101 v12.2.0: Requirement on emergency IM CN service |
Revised to S1-124455 |
WI code TEI11 Rel-11
CR0435R- Cat F Revision of S1-124057. |
||
CR |
Telecom Italia |
22.101 v12.2.0: Requirement on emergency IM CN service |
Noted |
WI code TEI11 Rel-11
CR0435R- Cat F Revision of S1-124057. Revision of S1-124349. |
||
CR |
Telecom Italia |
22.101 v12.2.0: Requirement on emergency IM CN service |
Revised to S1-124456 |
WI code TEI11 Rel-12 CR0438R- Cat A |
||
CR |
Telecom Italia |
22.101 v12.2.0: Requirement on emergency IM CN service |
Noted |
WI code TEI11 Rel-12 CR0438R- Cat A Revision of S1-124441. |
||
Access
control for UEs in RRC CONNECTED mode |
||||||
TO |
R2-124296 (NTT DOCOMO) |
LS on Access control for UEs in RRC CONNECTED mode |
Noted, answer in S1-124458 |
Necessity of controlling burst accesses from UEs already in RRC_CONNECTED mode which might cause signalling / traffic load towards the CN, especially to the IMS node. SA1 has to respond to the question: Are there any requirements due to the fact that UEs stay in connected mode more often nowadays that may be taken into account with respect to access control mechanisms? |
||
Cont |
NTT DOCOMO |
Access control for UEs in RRC CONNECTED mode |
Noted |
|
||
CR |
NTT DOCOMO |
22.011 v11.2.0: SSAC applicable irrespective of RRC modes |
Revised to S1-124177 |
WI code TEI12 Rel-12 CR0189R- Cat B |
||
CR |
NTT DOCOMO |
22.011 v11.2.0: SSAC applicable irrespective of RRC modes |
Noted |
WI code TEI12 Rel-12
CR0189R- Cat B Revision of S1-124115. WI code TEI11 Rel-11 CR0189R1 Cat B |
||
CR |
NTT DOCOMO |
22.011 v11.2.0: Access Control for CSFB applicable irrespective of RRC modes |
Revised to S1-124178 |
WI code TEI12 Rel-12 CR0190R- Cat B |
||
CR |
NTT DOCOMO |
22.011 v11.2.0: Access Control for CSFB applicable irrespective of RRC modes |
Noted |
WI code TEI12 Rel-12
CR0190R- Cat B Revision of S1-124116. WI code TEI11 Rel-11 CR0190R1 Cat B |
||
LS OUT |
NTT DOCOMO |
LS on Access control for UEs in RRC CONNECTED mode |
Revised to S1-124352 |
Response to: LS (S1-124262/R2-124296) on Access control for UEs in RRC CONNECTED mode from 3GPP RAN WG2 |
||
LS OUT |
NTT DOCOMO |
LS on Access control for UEs in RRC CONNECTED mode |
Revised to S1-124458 |
Response to: LS (S1-124262/R2-124296) on Access control for UEs in RRC CONNECTED mode from 3GPP
RAN WG2 Revision of S1-124117. |
||
LS OUT |
NTT DOCOMO |
LS on Access control for UEs in RRC CONNECTED mode |
Approved |
Response to: LS (S1-124262/R2-124296) on Access control for UEs in RRC CONNECTED mode from 3GPP
RAN WG2 Revision of S1-124117. Revision of S1-124352. No presentation |
||
WID |
NTT DOCOMO, NEC |
WID proposal for Suppression of mobile-originating signalling and traffic for UE in connected mode |
Noted |
|
||
PWS
for UE in Limited Service state |
||||||
TO |
R2-125158 (Huawei) |
Response LS on PWS Requirements for UEs in |
Noted, answer in S1-124503 |
RAN2 asks whether a Rel-8/9/10/11 UE in limited service state where there is no security for PWS, required, allowed, or not allowed to receive, process, and display warning messages? |
||
Cont |
NTT DOCOMO, KDDI |
PWS Requirements for UEs in Limited Service State |
Noted |
|
||
LS OUT |
Huawei |
Reply LS on PWS Requirements for UEs in Limited Service State |
Revised to S1-124353 |
Response to: R2-125158: LS on PWS Requirements for UEs in Limited Service State |
||
LS OUT |
Huawei |
Reply LS on PWS Requirements for UEs in Limited Service State |
Revised to S1-124503 |
Response to:
R2-125158: LS on PWS Requirements for UEs in Limited Service State Revision of S1-124062. |
||
LS OUT |
Huawei |
Reply LS on PWS Requirements for UEs in Limited Service State |
Approved |
Response to:
R2-125158: LS on PWS Requirements for UEs in Limited Service State Revision of S1-124062. Revision of S1-124353. No presentation |
||
CR |
Huawei, ST-Ericsson, Ericsson |
22.168 v8.2.0: clarification on enabling ETWS messages in limited service state |
Revised to S1-124502 |
WI code TEI8 Rel-8 CR006R- Cat F |
||
CR |
Huawei, ST-Ericsson, Ericsson |
22.168 v8.2.0: clarification on enabling ETWS messages in limited service state |
Agreed |
WI code TEI8 Rel-8 CR006R- Cat F Revision of S1-124354. No presentation |
||
CR |
Huawei, ST-Ericsson, Ericsson |
22.268 v9.4.0: clarification on enabling PWS messages in limited service state |
Agreed |
WI code TEI9 Rel-9 CR042R- Cat F |
||
CR |
Huawei, ST-Ericsson, Ericsson |
22.268 v10.3.0: clarification on enabling PWS messages in limited state |
Agreed |
WI code TEI9 Rel-10 CR043R- Cat A |
||
CR |
Huawei, ST-Ericsson, Ericsson |
22.268 v11.4.0: clarification on enabling PWS messages in limited state |
Agreed |
WI code TEI9 Rel-11 CR044R- Cat A |
||
M2M |
||||||
TO |
SP-120460/ OMA-LS_955 (KPN) |
LS on White Paper
for |
Noted, answer in S1-124360 |
OMA DM WG requests any information about activities in 3GPP which relate to the M2M device classification White Paper, to consider possible applications of the White Paper and to provide feedback. |
||
LS OUT |
Rapporteur |
LS on OMA M2M device classification |
Revised to S1-124360 |
Response to: LS (S1-124269) on M2M Device classification from OMA |
||
LS OUT |
Rapporteur |
LS on OMA M2M device classification |
Approved |
Response to: LS (S1-124269) on M2M Device classification from OMA Revision of S1-124164. |
||
Public
Safety |
||||||
TO |
TCCA CCBG System Architecture Group (EADS) |
General Architecture Considerations for Critical Communication Systems |
Postponed |
CCBG describes the boundary between the 3GPP domain and the Application domain for SA1 consideration. This is also allocated to the GCSE_LTE ad hoc in S1-123051 |
||
TO |
TETRA04(12)000078 (EADS) |
LS on Potential Implementation of TETRA services over LTE |
Postponed |
ETSI TC TETRA WG4 provides a possible implementation of TETRA services over LTE, illustrating the architectural split between the TETRA application and the underlying LTE transport network for SA1 consideration. This is also allocated to the GCSE_LTE ad hoc in S1-123050 |
||
TO |
SP-120651 (Vodafone) |
LS on Progression of normative ProSe work. |
Noted, answer in S1-124361 |
SA instructs SA1 to make every effort to agree a normative work item for ProSe, at SA1#60. This will allow the urgent needs of the Public Safety and Critical Communications community to be addressed. |
||
LS OUT |
Vodafone |
LS on Progression of normative ProSe work. |
Revised to S1-124515 |
Answer to S1-124261. |
||
LS OUT |
Vodafone |
LS on Progression of normative ProSe work. |
Approved |
Answer to S1-124261. Revision of S1-124361. No presentation |
||
TO |
ITU-R 5D/TEMP/98(Rev.2) (Telecom Italia) |
LS on invitation for material for a preliminary draft new report on “The use of IMT for broadband PPDR applications”. |
Noted |
Seen at Sept SA#57 as SP-120461, postponed to SA#58 in December. ITU-R WP 5D starting work on public safety and requests contributions their working document. |
||
LS
to be noted without presentation |
||||||
CC |
CP-120680 (Huawei) |
LS on DVB-RCS2 access technology |
Noted |
CT1 implemented SA1 IMSSat CR (Rel-12) in Rel-11 and asks SA if this is acceptable. Discussed in SA and considered acceptable (see SA1 chair report in S1-124003 clause 5.2) |
||
CC |
C1-123401 (Ericsson) |
Reply LS to LS (C1-122576/TSGWIF_111) on Publication of GSMA's Recommendations for Minimal Wi-Fi Capabilities of Terminals v1 |
Noted |
CT1 provides GSMA feedback on their WiFi terminal capability document. SA1 noted the original GSMA LS in Chicago in S1-122314. |
||
CC |
C1-123409 (NSN) |
LS on GSMA Application Network Efficiency Task Force “whitepaper and actions” |
Noted |
CT1 response to GSMA white paper actions. SA1 provided feedback to the white paper in S1-122510 in Chicago. |
||
CC |
R2-124349 (Qualcomm) |
LS on GSMA Application Network Efficiency Task Force “whitepaper and actions” |
Noted |
RAN2 response to GSMA white paper actions. |
||
CC |
RP-121454 (Intel, VZ) |
LS on GSMA Application Network Efficiency Task Force “whitepaper and actions” |
Noted |
RAN response to GSMA white paper actions. |
||
CC |
S4-121237 (Ericsson) |
LS on GSMA Application Network Efficiency Task Force “whitepaper and actions” |
Noted |
SA4 response to GSMA white paper actions. |
||
CC |
S5-122172 (Alcatel-Lucent) |
LS on GSMA Application Network Efficiency Task Force “whitepaper and actions” |
Noted |
SA5 response to GSMA white paper actions. |
||
5 Study and Work Items: New and Revisions |
||||||
5.1 Revisions of existing WIDs (including related contributions) |
||||||
5.2 New Study and Work Items (including related contributions) |
||||||
Cont |
NTT DOCOMO |
ODB enhancement to properly support barred VoLTE subscribers |
Noted |
|
||
CR |
NTT DOCOMO |
22.041 v11.0.0: Addition of APN to the condition of the ODB judgment |
Revised to S1-124333 |
WI code IODB Rel-11 CR0016R- Cat B |
||
CR |
NTT DOCOMO |
22.041 v11.0.0: Addition of APN to the condition of the ODB judgment |
Revised to S1-124362 |
WI code IODB Rel-11
CR0016R- Cat B Revision of S1-124064. |
||
CR |
NTT DOCOMO |
22.041 v11.0.0: Addition of APN to the condition of the ODB judgment |
Agreed |
WI code IODB Rel-11
CR0016R- Cat B Revision of S1-124064. Revision of S1-124333. No presentation |
||
LS OUT |
NTT DOCOMO |
LS on ODB enhancement to properly support barred VoLTE subscribers and update of IODB WID |
Revised to S1-124310 |
|
||
LS OUT |
NTT DOCOMO |
LS on ODB enhancement to properly support barred VoLTE subscribers and update of IODB WID |
Revised to S1-124334 |
Revision of S1-124065. |
||
LS OUT |
NTT DOCOMO |
LS on ODB enhancement to properly support barred VoLTE subscribers and update of IODB WID |
Revised to S1-124363 |
Revision of S1-124065. Revision of S1-124310. |
||
LS OUT |
NTT DOCOMO |
LS on ODB enhancement to properly support barred VoLTE subscribers and update of IODB WID |
Revised to S1-124367 |
Revision of S1-124065. Revision of S1-124310. Revision of S1-124334. |
||
LS OUT |
NTT DOCOMO |
LS on ODB enhancement to properly support barred VoLTE subscribers and update of IODB WID |
Approved |
Revision of S1-124065. Revision of S1-124310. Revision of S1-124334. Revision of S1-124363. |
||
Language
and Modality information |
||||||
WID |
Orange |
Language and Modality Information |
Revised to S1-124364 |
|
||
WID |
Orange |
Language and Modality Information |
Revised to S1-124452 |
Revision of S1-124035. |
||
WID |
Orange |
Language and Modality Information |
Agreed |
Revision of S1-124035. Revision of S1-124364. No presentation |
||
CR |
Orange, France Telecom, Huawei, Omnitor, Qualcomm |
22.101 v12.2.0: Language and Modality Information |
Revised to S1-124365 |
WI code Langinfo Rel-12 CR0404R2 Cat B |
||
CR |
Orange, France Telecom, Huawei, Qualcomm |
22.101 v12.2.0: Language and Modality Information |
Revised to S1-124459 |
WI code Langinfo Rel-12 CR0404R2 Cat B Revision of S1-124036. |
||
CR |
Orange, France Telecom, Huawei, Qualcomm |
22.101 v12.2.0: Language and Modality Information |
Agreed |
WI code Langinfo
Rel-12 CR0404R2 Cat B Revision of S1-124036. Revision of S1-124365. |
||
RTCWeb
for IMS |
||||||
Cont |
Alcatel-Lucent, Alcatel-Lucent Shanghai-Bell |
3GPP IMS WebRTC WID Overview |
Revised to S1-124342 |
|
||
Cont |
Alcatel-Lucent, Alcatel-Lucent Shanghai-Bell |
3GPP IMS WebRTC WID Overview |
Noted |
Revision of S1-124147. |
||
WID |
Alcatel-Lucent |
Proposed new WID on WEBRTC interoperability |
Revised to S1-124343 |
|
||
WID |
China Mobile |
WID for RTCWeb client access to IMS |
Revised to S1-124343 |
|
||
WID |
Alcatel-Lucent , China Mobile |
WID for RTCWeb client access to IMS |
Revised to S1-124366 |
|||
WID |
Alcatel-Lucent , China Mobile |
WID for RTCWeb client access to IMS |
Revised to S1-124494 |
Revision of S1-124074 and S1-124150. Revision of S1-124343. |
||
WID |
Alcatel-Lucent , China Mobile |
WID for RTCWeb client access to IMS |
Revised to S1-124511 |
Revision of S1-124074 and S1-124150. Revision of S1-124343. Revision of S1-124366. |
||
WID |
Alcatel-Lucent , China Mobile |
WID for RTCWeb client access to IMS |
Approved |
Revision of S1-124074 and S1-124150. Revision of S1-124343. Revision of S1-124366. Revision of S1-124494. |
||
CR |
China Mobile |
22.228 v12.3.0: Support for RTCWeb client access to IMS |
Noted |
WI code IMS_RTCWeb Rel-12 CR0175R- Cat B |
||
Flexible
Alerting |
||||||
WID |
Orange |
Sequential Flexible Alerting |
Revised to S1-124398 |
|
||
WID |
Orange |
Sequential Flexible Alerting |
Agreed |
Revision of S1-124246. |
||
CR |
ORANGE |
22.173 v12.2.0: Sequential Flexible Alerting in 22.173 |
Revised to S1-124399 |
WI code SEQ_ALERT Rel-12 CR0086R- Cat C |
||
CR |
ORANGE |
22.173 v12.2.0: Sequential Flexible Alerting in 22.173 |
Revised to S1-124424 |
WI code SEQ_ALERT Rel-12
CR0086R- Cat C Revision of S1-124247. |
||
CR |
ORANGE |
22.173 v12.2.0: Sequential Flexible Alerting in 22.173 |
Revised to S1-124481 |
WI code SEQ_ALERT Rel-12
CR0086R- Cat C Revision of S1-124247. Revision of S1-124399. |
||
CR |
ORANGE |
22.173 v12.2.0: Sequential Flexible Alerting in 22.173 |
Revised to S1-124493 |
WI code SEQ_ALERT Rel-12
CR0086R- Cat C Revision of S1-124247. Revision of S1-124399. Revision of S1-124424 |
||
CR |
ORANGE |
22.173 v12.2.0: Sequential Flexible Alerting in 22.173 |
Agreed |
WI code SEQ_ALERT Rel-12
CR0086R- Cat C Revision of S1-124247. Revision of S1-124399. Revision of S1-124424 Revision of S1-124481. No presentation |
||
ProSe/Public
Safety |
||||||
Cont |
Vodafone |
Way forward for normative Public Safety work in Release 12. |
Noted |
|
||
Cont |
Telefonica |
Summary of Requirements for a Public Safety System based on LTE/EPS |
Noted |
From GCSE_LTE ad hoc |
||
Cont |
Telecom Italia |
Public Safety and ProSe Services |
Revised to S1-124321 |
|
||
Cont |
Telecom Italia |
Public Safety and ProSe Services |
Noted |
Revision of S1-124051. |
||
Cont |
Institute for Information Industry, Huawei |
FS_ProSe Public Safety Use Cases with UAV |
Noted |
Revision of S1-124022. |
||
WID |
Vodafone, Telecom Italia, Orange, Telefonica S.A. |
Draft Umbrella WID for Public Safety |
Revised to S1-124308 |
|
||
WID |
Vodafone, Telecom Italia, Orange, Telefonica S.A. |
Draft Umbrella WID for Public Safety |
Revised to S1-124426 |
Revision of S1-124082. |
||
WID |
Vodafone, et al |
Umbrella WID for Public Safety |
Noted |
Revision of S1-124082. Revision of S1-124308. |
||
WID |
Vodafone, Telecom Italia, Orange |
Device to device communication for public safety and critical communications users. |
Revised to S1-124309 |
|
||
WID |
Vodafone, Telecom Italia, Orange |
Device to device communication for public safety and critical communications users. |
Noted |
Revision of S1-124083. |
||
Qualcomm, Inc. |
WID – Proposal for ProSe Normative Work |
Revised to S1-124190 |
|
|||
WID |
Qualcomm, Inc. |
WID – Proposal for ProSe Normative Work |
Revised to S1-124368 |
Revision of S1-124009. |
||
WID |
Qualcomm, Inc. |
WID – Proposal for ProSe Normative Work |
Revised to S1-124394 |
Revision of S1-124009. Revision of S1-124190. |
||
WID |
Qualcomm, Inc. |
WID – Proposal for ProSe Normative Work |
Revised to S1-124396 |
Revision
of S1-124009. Revision
of S1-124190. Revision of S1-124368. |
||
WID |
Qualcomm, Inc. |
WID – Proposal for ProSe Normative Work |
Agreed |
Revision
of S1-124009. Revision
of S1-124190. Revision
of S1-124368. Revision of S1-124394. |
||
LS OUT |
Qualcomm |
LS to SA2 on normative ProSe work |
Revised to S1-124425 |
|
||
LS OUT |
Qualcomm |
LS to SA2 on normative ProSe work |
Approved |
Revision of S1-124196. No presentation |
||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of ProSe General and WLAN Requirements to TS 22.278 |
Revised to S1-124325 |
|
||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of ProSe General and WLAN Requirements to TS 22.278 |
Withdrawn |
Revision of S1-124026. |
||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of ProSe Public Safety Specific Requirements to TS 22.278 |
Revised to S1-124326 |
|
||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of ProSe Public Safety Specific Requirements to TS 22.278 |
Withdrawn |
Revision of S1-124027. |
||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of ProSe Security and Charging |
Revised to S1-124327 |
|
||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of ProSe Security and Charging |
Revision of S1-124028. |
|||
CR |
Qualcomm |
22.278 v12.1.0: ProSe Security Requirements |
Withdrawn |
Revision of S1-124028. Revision of S1-124327. |
||
CR |
Qualcomm |
22.115: ProSe Charging Requirements |
Withdrawn |
Revision of S1-124028. Revision of S1-124327. WI code ProSe Rel-12 CR0067R- Cat B |
||
5.3 Proposals for new work (precursor to future Study and Work Items) |
||||||
Cont |
III, |
Discussion on EPC-less E-UTRAN Operation for Public Safety (EEOp) |
Noted |
|
||
WID |
Institute for Information Industry (III), et al |
Draft Feasibility Study on EPC-less E-UTRAN Operation for Public Safety (FS_EEOp) |
Noted |
|
||
6 Rel-10 and earlier contributions |
||||||
7 Rel-11 contributions |
||||||
7.1 SIMTC: System Improvements to Machine-Type Communications [SP-110877] |
||||||
7.2 Other Rel-11 contributions |
||||||
8 Rel-12 contributions |
||||||
8.1 MTCe-SIMSE: Interworking with M2M service enablement layer [SP-120436] |
||||||
CR |
Intel |
22.368 v12.0.0: Multiple Instances Requirement |
Revised to S1-124373 |
WI code MTCe-SIMSE Rel-12 CR0142R- Cat F |
||
CR |
Intel |
22.368 v12.0.0: Multiple Instances Requirement |
Revised to S1-124460 |
WI code MTCe-SIMSE
Rel-12 CR0142R- Cat F Revision of S1-124132. |
||
CR |
Intel |
22.368 v12.0.0: Multiple Instances Requirement |
Withdrawn |
WI code MTCe-SIMSE
Rel-12 CR0142R- Cat F Revision of S1-124132. Revision of S1-124373. |
||
8.2 GCSE_LTE: Group communication system enablers for LTE [SP-120421] |
||||||
8.2.1 GCSE_LTE contributions |
||||||
WID |
Rapporteur (NSN) |
Updated WID for Group Communication System Enablers for LTE |
Revised to S1-124379 |
|
||
WID |
Rapporteur (NSN) |
Updated WID for Group Communication System Enablers for LTE |
Revised to S1-124491 |
Revision of S1-124307. Agreed in drafting |
||
WID |
Rapporteur (NSN) |
Updated WID for Group Communication System Enablers for LTE |
Agreed |
Revision of S1-124307. Agreed in drafting Revision of S1-124379. |
||
EADS |
EPS and UE
functional requirements for GCSE_LTE |
Agreed |
From GCSE_LTE ad hoc Drafting session: First proposed change for High Level Requirements was revised to Clarify the User's perception when receiving the Group Communication Agreed to be added to TS 22.468 It was concluded that the Tetra LS is too stage 2 minded to include into the annex temporarily. The last para in 4.t on "simultaneous involvement" will be dealt with in the ProSe/GCSE overlap discussions Rest of document was Noted |
|||
Cont |
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
GCSE_LTE: Group Addressing and Subscription Options |
Noted |
From GCSE_LTE ad hoc Drafting session: The level of group awareness needs to be discussed still eg whether 3GPP is completely unaware or knows of groups or whether it even maintains a group – UE relationship and subscription in its domain To be continued by email discussion |
||
Cont |
U.S. Department of Commerce |
GCSE_LTE: Group handling |
Noted |
From GCSE_LTE ad hoc |
||
Cont |
U.S. Department of Commerce |
GCSE_LTE: Incident Commander –Realtime group |
Noted |
From GCSE_LTE ad hoc |
||
Cont |
Nokia Siemens Networks |
Proposed text for a new section 4.3 'Using Groups' of 22.468 |
Noted |
From GCSE_LTE ad hoc |
||
Cont |
U.S. Department of Commerce |
GCSE_LTE: Priority handling |
Noted |
From GCSE_LTE ad hoc |
||
Cont |
Nokia Siemens Networks |
Proposed text for a new section 5 'Interaction with other Services and Functions' of 22.468 |
Noted |
From GCSE_LTE ad hoc |
||
Cont |
Huawei Technologies. Co., Ltd. |
GCSE_LTE: proposed text to support 3GPP transport requirements |
Agreed |
From GCSE_LTE ad hoc Drafting session: Priority section revised taking into account the relevant parts of the QC contribution in S1-124299 and agreed to add this to TS 22.468 Rest of document was Noted |
||
Cont |
Qualcomm Inc |
GCSE_LTE functional and high level requirements |
Agreed |
From GCSE_LTE ad hoc Drafting session: Covers also Group Aspects and Priority 4.1.3 was handled together with Priority section of S1-124298 and Agreed to be added to 22.468 4.1.4 was withdrawn as QC considered this to be more an stage 2 issue 4.1.6 On relation to "classical" emergency calls was Agreed to be added to 22.468 4.1.7 - 4.1.8 QC will discuss with the companies vocal in the discussion on a whether such a requirement is needed – Noted 4.1.9 Agreed to be added to High Level section of 22.468 |
||
8.2.2 GCSE_LTE drafting session information |
||||||
AGE |
Rapporteur |
GCSE_LTE drafting Agenda |
Revised to S1-124378 |
|
||
AGE |
Rapporteur |
GCSE_LTE drafting Agenda |
Noted |
Revision of S1-124375. |
||
REP |
Rapporteur |
GCSE_LTE drafting Report |
Approved |
|
||
TS |
Rapporteur |
TS 22.468 |
Revised to S1-124383 |
Agreed as the basis for future contributions |
||
TS |
Rapporteur |
TS 22.468 |
Agreed |
Revision of S1-124382. Agreed as the basis for future contributions No presentation |
||
TR |
Rapporteur |
TS 22.486 on GCSE_LTE |
Withdrawn |
|
||
|
|
|
Withdrawn |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
8.3 WLAN_NS: WLAN network selection for 3GPP terminals [SP-120259] (SA1 secondary responsibility) |
||||||
8.4 MTCe-SRM: Service requirement maintenance [SP-120541] |
||||||
Cont |
KPN, Panasonic, TeliaSonera |
MTC Features to take forward to Release 13 |
Revised to S1-124322 |
|
||
Cont |
KPN, Panasonic, TeliaSonera |
MTC Features to take forward to Release 13 |
Noted |
Revision of S1-124160. |
||
Cont |
KPN |
Clarification of MTC Time Controlled |
Noted |
|
||
Cont |
Vodafone, et al |
MTC-related requirements for clean-up |
Noted |
|
||
Cont |
KPN (rapporteur) |
Comparison of proposals for deletion / modification 22.368 |
Noted |
MTC Priority Alarm – leave this for now and not change it into a generic requirement as proposed in this document |
||
CR |
KPN (rapporteur) |
22.368 v12.0.0: Clean up of not yet implemented features and requirements |
Revised to S1-124193 |
WI code MTCe-SRM Rel-12 CR0143R- Cat C |
||
CR |
China Mobile |
22.368 v12.0.0: Alarm Restrictions Requirement for Priority Alarm Feature |
Revised to S1-124193 |
WI code MTCe-SRM Rel-12 CR0140R- Cat B |
||
CR |
KPN (rapporteur) |
22.368 v12.0.0: Clean up of not yet implemented features and requirements |
Noted |
WI code MTCe-SRM Rel-12 CR0143R- Cat C |
||
CR |
Intel |
22.368 v12.0.0: Clean-up of Time Controlled Requirement |
Noted |
WI code MTCe-SRM Rel-12 CR0135R- Cat F |
||
CR |
Intel |
22.368 v12.0.0: Clean-up of Time Tolerant Requirement |
Revised to S1-124463 |
WI code MTCe-SRM Rel-12 CR0136R- Cat F |
||
CR |
KPN, Intel |
22.368 v12.0.0: Clean-up of Time Tolerant Requirement |
Revised to S1-124488 |
WI code MTCe-SRM
Rel-12 CR0136R- Cat F Revision of S1-124067. |
||
CR |
KPN, Intel |
22.368 v12.0.0: Clean-up of Time Tolerant Requirement |
Agreed |
WI code MTCe-SRM
Rel-12 CR0136R- Cat F Revision of S1-124067. Revision of S1-124463. |
||
CR |
Intel |
22.368 v12.0.0: Clean-up of Mobile originated only Requirement |
Noted |
WI code MTCe-SRM Rel-12 CR0137R- Cat F |
||
CR |
Intel |
22.368 v12.0.0: Clean-up of Infrequent mobile terminated Requirement |
Noted |
WI code MTCe-SRM Rel-12 CR0138R- Cat F |
||
CR |
Intel |
22.368 v12.0.0: Clean-up of Location specific trigger Requirement |
Revised to S1-124464 |
WI code MTCe-SRM Rel-12 CR0139R- Cat F |
||
CR |
KPN, Intel |
22.368 v12.0.0: Clean-up of Location specific trigger Requirement |
Revised to S1-124489 |
WI code MTCe-SRM
Rel-12 CR0139R- Cat F Revision of S1-124070. |
||
CR |
KPN, Intel |
22.368 v12.0.0: Clean-up of Location specific trigger Requirement |
Agreed |
WI code MTCe-SRM
Rel-12 CR0139R- Cat F Revision of S1-124070. Revision of S1-124464. |
||
CR |
Nokia Siemens Networks |
TS 22.386 v12.0.0: Clarification of the term bulk CDR |
Noted |
WI code MTCe-SRM Rel-12 CR0141R- Cat F To be discussed in a joint session in Prague. Action to Juergen to re-submit this CR in Prague and to bring this for discussion with SA2 |
||
CR |
KPN (rapporteur), Renesas Mobile Europe Ltd |
22.368 v12.0.0: Removal of requirement to be able to count for device initiated signalling |
Agreed |
WI code MTCe-SRM Rel-12 CR0144R- Cat C |
||
CR |
KPN (rapporteur), Renesas Mobile Europe Ltd |
22.368 v12.0.0: Moving MTC Feature Infrequent Transmission into a generic requirement |
Revised to S1-124490 |
WI code MTCe-SRM Rel-12 CR0145R- Cat C |
||
CR |
KPN (rapporteur), Renesas Mobile Europe Ltd |
22.368
v12.0.0: Moving MTC Feature Infrequent Transmission into a generic requirement |
Revised to S1-124512 |
WI code MTCe-SRM Rel-12 CR0145R- Cat C Revision of S1-124466. |
||
CR |
KPN (rapporteur), Renesas Mobile Europe Ltd |
22.368
v12.0.0: Moving MTC Feature Infrequent Transmission into a generic
requirement |
Agreed |
WI code MTCe-SRM
Rel-12 CR0145R- Cat C Revision of S1-124466. Revision of S1-124490. No presentation |
||
8.5 UPCON: User plane congestion management [SP-120545] |
||||||
CR |
KDDI, et al |
22.101 v12.2.0: Addition of UPCON Requirements |
Revised to S1-124389 |
WI code UPCON Rel-12 CR0434R- Cat B |
||
CR |
KDDI, et al |
22.101 v12.2.0: Addition of UPCON Requirements |
Revised to S1-124416 |
WI code UPCON Rel-12 CR0434R- Cat B Revision of S1-124092. |
||
CR |
KDDI, et al |
22.101 v12.2.0: Addition of UPCON Requirements |
Agreed |
WI code UPCON Rel-12 CR0434R- Cat B Revision of S1-124092. Revision of S1-124389. |
||
LS OUT |
KDDI |
LS to SA2 on UPCON Requirements |
Revised to S1-124417 |
|
||
LS OUT |
KDDI |
LS to SA2 on UPCON Requirements |
Approved |
Revision of S1-124411. |
||
Disc |
Qualcomm |
Discussion paper |
Noted |
|
||
CR |
Qualcomm Incorporated, Ericsson, ST-Ericsson |
22.101 v12.2.0: Addition of UPCON Requirements |
Revised to S1-124192 |
WI code UPCON Rel-12 CR0434R- Cat B |
||
CR |
Qualcomm Incorporated, Ericsson, ST-Ericsson |
22.101 v12.2.0: Addition of UPCON Requirements |
Noted |
Revision of S1-124165. Proposed changes have been taken into account in S1-124389 WI code UPCON Rel-12 CR0436R- Cat B |
||
8.6 Other Rel-12 contributions |
||||||
CR |
ORANGE |
22.088 v12.2.0: Modification of the BOIC and BOICexHC barring for the SMS service |
Noted |
WI code ?? Rel-12 CR??R- Cat C |
||
Cont |
Huawei Technologies. Co., Ltd. , Hisilicon |
Network name display & Charging for CSFB with multiple PLMNs |
Noted |
|
||
LS OUT |
Huawei |
Draft LS on Network name display & Charging for CSFB with multiple PLMNs |
Revised to S1-124474 |
|
||
LS OUT |
Huawei |
Draft LS on Network name display & Charging for CSFB with multiple PLMNs |
Revised to S1-124513 |
Revision of S1-124369. |
||
LS OUT |
Huawei |
Draft LS on Network name display & Charging for CSFB with multiple PLMNs |
Approved |
Revision of S1-124369. Revision of S1-124474. No presentation |
||
8.7 TEI12 contributions |
||||||
Cont |
Research In Motion |
Discussion on ICE access procedure touch gesture mechanism |
Noted |
|
||
Cont |
Research In Motion, Vodafone |
Discussion and comments on S1-124127 |
Noted |
|
||
CR |
Research In Motion UK Ltd, Vodafone |
22.030 v12.0.0: Enhancements to the MMI of the ICE access procedures |
Noted |
WI code TEI12 Rel-12 CR0016R3 Cat C |
||
CR |
Sony Mobile Communications |
22.030 v12.0.0: ICE access procedures MMI Enhancement |
Revised to S1-124176 |
WI code TEI12 Rel-12 CR0017R- Cat C |
||
CR |
Sony Mobile Communications |
22.030 v12.0.0: ICE access procedures MMI Enhancement |
Noted |
WI code TEI12 Rel-12 CR0017R- Cat C Revision of S1-124127. |
||
9 Study Item contributions |
||||||
9.1 FS_MTCe: Enhancements for Machine-Type Communications [SP-100448] |
||||||
Cont |
ETRI, ITRI |
Proposed text of a scenario of Communication via MTC Gateway Device |
Noted |
|
||
Cont |
ITRI, ETRI |
Proposed service requirements of MTC Gateway Device |
Revised to S1-124372 |
|
||
Cont |
ITRI, ETRI |
Proposed service requirements of MTC Gateway Device |
Noted |
Revision of S1-124249. |
||
9.2 FS_ProSe: Proximity-based Services [SP-110638] |
||||||
9.2.1 Editorial and other clean-up |
||||||
TR |
Qualcomm Inc |
FS_ProSe - Editorial Updates |
Agreed |
Drafting session Agreed by drafting session to be added to the TR |
||
Cont |
General Dynamics Broadband |
FS_ProSe: Editorial corrections |
Revised to S1-124204 |
Revision of S1-124157. Drafting session |
||
Cont |
General Dynamics Broadband |
FS_ProSe: Editorial corrections |
Agreed |
Revision of S1-124157. Drafting session Revision of S1-124318. Agreed by drafting session to be added to the TR No presentation |
||
Cont |
Alcatel-Lucent, et al |
FS_ProSe: ProSe Editorial Clean up |
Revised to S1-124341 |
|
||
Cont |
Alcatel-Lucent, et al |
FS_ProSe: ProSe Editorial Clean up |
Agreed |
Revision of S1-124030. Drafting session Agreed by drafting session to be added to the TR |
||
Cont |
Alcatel-Lucent, et al |
FS_ProSe: ProSe Editor’s Note Cleanup |
Agreed |
Drafting session Agreed by drafting session to be added to the TR |
||
9.2.2 Terminology and definitions |
||||||
Cont |
Intel |
Updates to Definitions |
Noted |
|
||
Cont |
Institute for Information Industry (III) |
FS_ProSe: ProSe Communication via Relay Node (RN) |
Noted |
|
||
Cont |
Qualcomm Inc., Alcatel-Lucent, US Department of Commerce |
Proximity Criteria for ProSe |
Revised to S1-124404 |
|||
Cont |
Qualcomm Inc., Alcatel-Lucent, US Department of Commerce |
Proximity Criteria for ProSe |
Agreed |
Some overlap with S1-124146, S1-124135 Revision of S1-124023. Agreed to be added to the TR No presentation |
||
Cont |
ITRI |
Proposal for Operator-controlled Proximity Criteria |
Revised to S1-124404 |
|||
Cont |
Huawei, Institute for Information Industry (III) |
ProSe 3.1, 5.1.15 and 5.1.6 Speed and MNO control as real requirements |
Revised to S1-124406 |
Some overlap with S1-124135, S1-124023 Proximity criteria part merged into S1-124404 |
||
Cont |
Huawei, Institute for Information Industry (III) |
ProSe 3.1, 5.1.15 and 5.1.6 Speed and MNO control as real requirements |
Agreed |
Some overlap with S1-124135, S1-124023 Proximity criteria part merged into S1-124404 Revision of S1-124146. Changes to PR5.1.1-7 only Agreed to be added to the TR No presentation |
||
Cont |
Qualcomm Inc., Alcatel-Lucent, US Department of Commerce |
Proximity Criteria for ProSe |
Revised to S1-124471 |
|
||
Cont |
Qualcomm Inc., Alcatel-Lucent, US Department of Commerce |
Proximity Criteria for ProSe |
Agreed |
Revision of S1-124405. Agreed to be added to the TR No presentation Concerns from Renesas and RIM that the examples added are not within SA1 remit. |
||
9.2.3 Public Safety related |
||||||
Cont |
US Department of Commerce |
FS_ProSe: ProSe General Use Case Title and Introductory Text & ProSe Potential Requirements General Title and Introductory Text |
Revised to S1-124390 |
|
||
Cont |
US Department of Commerce |
FS_ProSe: ProSe General Use Case Title and Introductory Text & ProSe Potential Requirements General Title and Introductory Text |
Noted |
Revision of S1-124014. |
||
Cont |
Intel |
ProSe Public Safety Authentication |
Noted |
|
||
Cont |
Intel |
ProSe Public Safety Authentication |
Revised to S1-124391 |
|
||
Cont |
Intel |
ProSe Public Safety Authentication |
Revised to S1-124472 |
Revision of S1-124130. |
||
Cont |
Intel |
ProSe Public Safety Authentication |
Agreed |
Revision of S1-124130. Revision of S1-124391. Agreed to be added to the TR No presentation |
||
Cont |
Institute for Information Industry (III), |
FS_ProSe: Mobility Consideration for Public Safety |
Revised to S1-124392 |
|
||
Cont |
Institute for Information Industry (III), |
FS_ProSe: Mobility Consideration for Public Safety |
Revised to S1-124437 |
Revision of S1-124017. |
||
Cont |
Institute for Information Industry (III), |
FS_ProSe: Mobility Consideration for Public Safety |
Noted |
Revision of S1-124017. Revision of S1-124392. |
||
Cont |
Huawei, Telecom Italia |
ProSe 5.2.2. [pr.5.2.2-54] User policy for PS can bypass MNO policy |
Revised to S1-124393 |
|
||
Cont |
Huawei, Telecom Italia |
ProSe 5.2.2. [pr.5.2.2-54] User policy for PS can bypass MNO policy |
Agreed |
Revision of S1-124144. Agreed to be added to the TR |
||
Cont |
Huawei, Telecom Italia |
ProSe 5.2.5 [PR.5.2.5-59] Network control of PS UEs under network coverage |
Revised to S1-124395 |
|
||
Cont |
Huawei, Telecom Italia |
ProSe 5.2.5 [PR.5.2.5-59] Network control of PS UEs under network coverage |
Revised to S1-124479 |
Revision of S1-124145. |
||
Cont |
Huawei, Telecom Italia |
ProSe 5.2.5 [PR.5.2.5-59] Network control of PS UEs under network coverage |
Revised to S1-124492 |
Revision of S1-124145. Revision of S1-124395. |
||
Cont |
Huawei, Telecom Italia |
ProSe 5.2.5 [PR.5.2.5-59] Network control of PS UEs under network coverage |
Agreed |
Revision of S1-124145. Revision of S1-124395. Revision of S1-124479. Agreed to be added to the TR No presentation |
||
Cont |
Huawei, Telecom Italia |
ProSe 5.1.6.5 [pr.5.1.6-31] Path switch not visible applies only for non PS users |
Revised to S1-124397 |
|
||
Cont |
Huawei, Telecom Italia |
ProSe 5.1.6.5 [pr.5.1.6-31] Path switch not visible applies only for non PS users |
Agreed |
Revision of S1-124148. Agreed to be added to the TR No presentation |
||
Cont |
ITRI |
Requirements for ProSe Communication Use Case |
Revised to S1-124400 |
|
||
Cont |
ITRI |
Requirements for ProSe Communication Use Case |
Revised to S1-124473 |
Revision of S1-124248. |
||
Cont |
ITRI |
Requirements for ProSe Communication Use Case |
Agreed |
Revision of S1-124248. Revision of S1-124400. Agreed to be added to the TR No presentation |
||
Cont |
CATT |
Clarification on ProSe Discovery In/Out of Network Coverage |
Noted |
Late document: (will not be treated as late as there are extenuating circumstances) |
||
Cont |
Huawei, Telecom Italia |
ProSe 5.2.10.5 3GPP policies |
Noted |
|
||
Cont |
Qualcomm Inc |
GCSE_LTE functional and high level requirements (ProSe-related item) |
Revised to S1-124402 |
From GCSE_LTE ad hoc |
||
Cont |
Intel Corporation |
Proposed text to sections 4.3 'High Level Requirements' of 22.468 |
Revised to S1-124402 |
From GCSE_LTE ad hoc |
||
Cont |
Intel Corporation, Qualcomm |
Proposed text to sections 4.3 'High Level Requirements' of 22.468 |
Revised to S1-124487 |
From GCSE_LTE ad hoc |
||
Cont |
Intel Corporation; Qualcomm; Telecom Italia; RIM; EADS; LGE; NSN |
Proposed text to sections 4.3 'High Level Requirements' of 22.468 |
Revised to S1-124506 |
From GCSE_LTE ad hoc Revision of S1-124303 and S1-124300. Revision of S1-124402. |
||
Cont |
Intel Corporation; Qualcomm; Telecom Italia; RIM; EADS; LGE; NSN |
Proposed text to sections 4.3 'High Level Requirements' of 22.468 |
Agreed |
From GCSE_LTE ad hoc Revision of S1-124303 and S1-124300. Revision of S1-124402. Revision of S1-124487. Section 4.X.4 and 4.X.5 agreed to be added to the TS |
||
Cont |
Intel Corporation |
Discussion Paper on Dynamic Group Conferencing via GCSE_LTE & ProSe |
Noted |
From GCSE_LTE ad hoc |
||
Cont |
Intel Corporation |
Discussion Paper on GCSE interworking with ProSe Group Communications |
Noted |
From GCSE_LTE ad hoc |
||
Cont |
ITRI |
Preemption of public safety ProSe group communications |
Noted |
From GCSE_LTE ad hoc |
||
Cont |
ITRI |
Dynamically add or remove ProSe Group members |
Noted |
From GCSE_LTE ad hoc |
||
Cont |
Institute for Information Industry, Huawei |
FS_ProSe Public Safety Use Cases with UAV |
Revised to S1-124403 |
|
||
Cont |
LG Electronics, Inc. |
FS_ProSe: Discovery Use Case for Public Safety Situation |
Noted |
|
||
9.2.4 WLAN aspects |
||||||
Cont |
Intel |
Updates to the “WLAN ProSe Communications” Use Case |
Revised to S1-124407 |
|
||
Cont |
Intel |
Updates to the “WLAN ProSe Communications” Use Case |
Agreed |
Revision of S1-124099. To include proposed requirement change from S1-124314 Agreed to be added to the TR |
||
Cont |
Huawei |
ProSe 5.1.9 [pr.5.1.9-44] Clarifications for Direct WiFi use case |
Revised to S1-124314 |
|
||
Cont |
Huawei |
ProSe 5.1.9 [pr.5.1.9-44] Clarifications for Direct WiFi use case |
Revision of S1-124142. Proposed requirement change in 5.1.9.5 merged into S1-124407 |
|||
Cont |
Huawei |
ProSe 5.1.9 [pr.5.1.9-44] Clarifications for Direct WiFi use case |
Agreed |
Revision of S1-124142. Revision of S1-124314. To update the use case Agreed to be added to the TR |
||
Cont |
Intel |
Updates to the “Service Management and Continuity for ProSe Communication via WLAN” use case |
Overlap with S1-124143 |
|||
Cont |
Intel |
Updates to the “Service Management and Continuity for ProSe Communication via WLAN” use case |
Agreed |
Overlap with S1-124143 Revision of S1-124100. For revising new requirements Agreed to be added to the TR |
||
Cont |
Intel |
Updates to the “Service Management and Continuity for ProSe Communication via WLAN” use case |
Agreed |
Overlap with S1-124143 Revision of S1-124100. For first 2 paragraphs in section 5.1.10.5 Agreed to be added to the TR |
||
Cont |
Huawei, Renesas Mobile Europe Ltd |
ProSe 5.1.10 [pr.5.1.10-46 and 47] No network visibility of WLAN status |
Revised to S1-124315 |
Overlap with S1-124100 |
||
Cont |
Huawei, Renesas Mobile Europe Ltd |
ProSe 5.1.10 [pr.5.1.10-46 and 47] No network visibility of WLAN status |
Noted |
Overlap with S1-124100 Revision of S1-124143. |
||
Cont |
III, ETRI |
FS_ProSe: Concurrent E-UTRAN Infrastructure and WLAN Proximity Communication |
Revised to S1-124412 |
|
||
Cont |
III, ETRI |
FS_ProSe: Concurrent E-UTRAN Infrastructure and WLAN Proximity Communication |
Agreed |
Revision of S1-124018. |
||
Cont |
Motorola Mobility, Intel, III, ETRI, Panasonic |
Network Offloading via WLAN ProSe Communication |
Revised to S1-124413 |
|
||
Cont |
Motorola Mobility, Intel, III, ETRI, Panasonic |
Network Offloading via WLAN ProSe Communication |
Agreed |
Revision of S1-124131. Agreed to be added to the TR No presentation |
||
9.2.5 Identifiers |
||||||
Cont |
Qualcomm Inc., et al |
Usefulness and Identifiers to use with ProSe Discovery |
Revised to S1-124414 |
|
||
Cont |
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Neustar, ETRI |
FS_ProSe: Identifying ProSe-enabled UEs |
Revised to S1-124414 |
Cover identifier changes only here New use case: MNO subscription change to be reviewed in section 9.2.8 Identifier aspect covered in S1-124414 |
||
Cont |
Motorola Solutions |
FS_ProSe: Use case and requirements for Public Safety UE identifiers |
Related with S1-124159 Identifier
aspect covered in S1-124414 |
|||
Cont |
Motorola Solutions |
FS_ProSe: Use case and requirements for Public Safety UE identifiers |
Noted |
Related with S1-124159 Identifier aspect covered in S1-124414 Revision of S1-124158. Use case revised to remove identifier aspect |
||
Cont |
Motorola Solutions |
FS_ProSe: Use case for commercial UE identifiers |
Related with S1-124158 Identifier aspect covered in S1-124414 |
|||
Cont |
Motorola Solutions |
FS_ProSe: Use case for commercial UE identifiers |
Noted |
Related with S1-124158 Identifier aspect covered in S1-124414 Revision of S1-124159. Use case revised to remove identifier aspect |
||
Cont |
Renesas Mobile Europe Ltd |
FS_ProSe: Discovery |
Revised to S1-124414 |
|
||
Cont |
Huawei, Telecom Italia |
ProSe [pr.5.1.1-2] What is Discovery of UEs of interest |
Revised to S1-124316 |
|
||
Cont |
Huawei, Telecom Italia |
ProSe [pr.5.1.1-2] What is Discovery of UEs of interest |
Revised to S1-124414 |
Revision of S1-124156. |
||
Qualcomm Inc., et al |
Usefulness and Identifiers to use with ProSe Discovery |
Revised to S1-124477 |
Revision of S1-124013, S1-124029, S1-124158, S1-124159, S1-124047 and S1-124316. |
|||
Cont |
Qualcomm Inc., et al |
Usefulness and Identifiers to use with ProSe Discovery |
Agreed |
Revision of S1-124013, S1-124029, S1-124158, S1-124159, S1-124047 and
S1-124316. Revision of S1-124414. Agreed to be added to the TR No presentation |
||
9.2.6 Security, privacy and lawful intercept aspects |
||||||
Cont |
Institute for Information Industry (III) |
FS_ProSE: Additional Security Requirements Clean Up |
Revised to S1-124370 |
|
||
Cont |
Institute for Information Industry (III) |
FS_ProSE: Additional Security Requirements Clean Up |
Agreed |
Revision of S1-124020. Agreed to be added to the TR |
||
Cont |
Qualcomm Inc. |
Parties Involved in Authorization to Access ProSe Discovery Information |
Revised to S1-124419 |
|
||
Cont |
Qualcomm Inc. |
Parties Involved in Authorization to Access ProSe Discovery Information |
Revised to S1-124478 |
Revision of S1-124040. |
||
Cont |
Qualcomm Inc. |
Parties Involved in Authorization to Access ProSe Discovery Information |
Revised to S1-124480 |
Revision of S1-124040. Revision of S1-124419. |
||
Cont |
Qualcomm Inc. |
Parties Involved in Authorization to Access ProSe Discovery Information |
Agreed |
Revision of S1-124040. Revision of S1-124419. Revision of S1-124478. Agreed to be added to the TR No presentation |
||
Cont |
Renesas Mobile Europe Ltd |
FS_ProSe: Considerations on application authorization |
Revised to S1-124418 |
|
||
Cont |
Renesas Mobile Europe Ltd |
FS_ProSe: Considerations on application authorization |
Withdrawn |
Revision of S1-124046. Agreed to be added to the TR No presentation |
||
Cont |
Huawei, Telecom Italia |
ProSe 5.1.15 [pr.5.1.1-9] Proximity information provided to applications |
Revised to S1-124420 |
|
||
Cont |
Huawei, Telecom Italia |
ProSe 5.1.15 [pr.5.1.1-9] Proximity information provided to applications |
Revised to S1-124507 |
Revision of S1-124140. |
||
Cont |
Huawei, Telecom Italia |
ProSe 5.1.15 [pr.5.1.1-9] Proximity information provided to applications |
Agreed |
Revision of S1-124140. Revision of S1-124420. No presentation |
||
Cont |
ETRI |
FS_ProSE: Additional security requirements |
Revised to S1-124195 |
|
||
Cont |
ETRI |
FS_ProSE: Additional security requirements |
Noted |
Revision of S1-124108. |
||
Cont |
InterDigital, Intel, Alcatel-Lucent, Qualcomm, Inc. |
Revisit of security requirements for ProSe |
Revised to S1-124421 |
|
||
Cont |
InterDigital, Intel, Alcatel-Lucent, Qualcomm, Inc. |
Revisit of security requirements for ProSe |
Agreed |
Revision of S1-124058. Agreed to be added to the TR No presentation |
||
Cont |
Telecom Italia, Huawei |
FS_ProSe – Additional Security Requirements |
Revised to S1-124422 |
|
||
Cont |
Telecom Italia, Huawei |
FS_ProSe – Additional Security Requirements |
Agreed |
Revision of S1-124054. Agreed to be added to the TR No presentation |
||
LS OUT |
Institute for Information Industry (III) |
LS on Lawful Interception Requirements for Proximity-based Service |
Noted |
|
||
9.2.7 Other clarification and updates |
||||||
Cont |
Telecom Italia, Huawei |
FS_ProSe – Charging related requirements |
Agreed |
Drafting session Agreed by drafting session to be added to the TR |
||
Cont |
ITRI |
Further requirements for Charging on UE Discovery on Different PLMNs |
Noted |
Drafting session |
||
Cont |
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Qualcomm Inc. |
FS_ProSe: Charging clean up |
Revised to S1-124205 |
Drafting session |
||
Cont |
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Qualcomm Inc. |
FS_ProSe: Charging clean up |
Agreed |
Drafting session Revision of S1-124032. Agreed by drafting session to be added to the TR |
||
Cont |
ITRI |
General Charging Requirements for QoS and ProSe Communication Switching |
Revised to S1-124206 |
Drafting session |
||
Cont |
ITRI |
General Charging Requirements for QoS and ProSe Communication Switching |
Revised to S1-124216 |
Drafting session Revision of S1-124136. |
||
Cont |
ITRI |
General Charging Requirements for QoS and ProSe Communication Switching |
Agreed |
Drafting session Revision of S1-124136. Revision of S1-124206. Agreed by drafting session to be added to the TR |
||
Cont |
CATT |
Requirements on charging for ProSe Discovery range class |
Revised to S1-124207 |
Late document (will not be treated as late as there are extenuating circumstances) Drafting session |
||
Cont |
CATT |
Requirements on charging for ProSe Discovery range class |
Noted |
Late document (will
not be treated as late as there are extenuating circumstances) Drafting session Revision of S1-124166. |
||
Cont |
Intel |
Updates to the “Restricted Discovery” Use Case |
Revised to S1-124208 |
Drafting session |
||
Cont |
Intel |
Updates to the “Restricted Discovery” Use Case |
Revised to S1-124218 |
Drafting session Revision of S1-124098. potential merge with S1-124414 |
||
Cont |
Intel |
Updates to the “Restricted Discovery” Use Case |
Agreed |
Drafting session Revision of S1-124098. potential merge with S1-124414 Revision of S1-124208. Agreed to be added to the TR No presentation |
||
Cont |
Telecom Italia, Huawei |
FS_ProSe – Battery Consumption requirements |
Agreed |
Drafting session Agreed by drafting session to be added to the TR |
||
Cont |
Institute for Information Industry (III) |
FS_ProSe: Coverage Class for ProSe Discovery |
Noted |
Drafting session |
||
Cont |
Deutsche Telekom |
VPLMN control of discovery |
Revised to S1-124209 |
Drafting session |
||
Cont |
Deutsche Telekom |
VPLMN control of discovery |
Agreed |
Drafting session Revision of S1-124087. Agreed by drafting session to be added to the TR No presentation |
||
Cont |
Intel |
Updates to the “Discovery with Subscribers from Different PLMNs” Use Case |
Revised to S1-124210 |
Drafting session |
||
Cont |
Intel |
Updates to the “Discovery with Subscribers from Different PLMNs” Use Case |
Noted |
Drafting session Revision of S1-124096. |
||
Cont |
Intel |
Updates to the “EPS ProSe Discovery” Use Case |
Revised to S1-124211 |
Drafting session potential to merge with S1-124141 |
||
Cont |
Huawei, Telecom Italia |
ProSe 5.1.5 [pr.5.1.5-26] Clarification of Use Case and discovery period |
Revised to S1-124211 |
Drafting session potential to merge with S1-124097 |
||
Cont |
Intel |
Updates to the “EPS ProSe Discovery” Use Case |
Revised to S1-124219 |
Drafting session potential to merge with S1-124141 Revision of S1-124097. |
||
Cont |
Intel |
Updates to the “EPS ProSe Discovery” Use Case |
Agreed |
Drafting session potential to merge
with S1-124141 Revision of S1-124097. Revision of S1-124211. Agreed to be added to the TR No presentation |
||
Cont |
ITRI |
Further requirements for infrastructure path and E-UTRA ProSe Communication path switching |
Noted |
Drafting session |
||
Cont |
Deutsche Telekom |
FS_ProSe Clarification of communication requirements |
Revised to S1-124179 |
includes updates to WLAN section |
||
Cont |
Deutsche Telekom |
FS_ProSe Clarification of communication requirements |
Revised to S1-124317 |
Revision of S1-124088. |
||
Cont |
Deutsche Telekom |
FS_ProSe Clarification of communication requirements |
Revised to S1-124212 |
Revision of S1-124088. Revision of S1-124179. Drafting session |
||
Cont |
Deutsche Telekom |
FS_ProSe Clarification of communication requirements |
Revised to S1-124220 |
Revision of S1-124088. Revision of S1-124179. Drafting session Revision of S1-124317. |
||
Cont |
Deutsche Telekom |
FS_ProSe Clarification of communication requirements |
Agreed |
Revision of S1-124088. Revision of S1-124179. Drafting session Revision of S1-124317. Revision of S1-124212. Agreed to be added to the TR No presentation |
||
Cont |
Huawei, Telecom Italia |
ProSe 5.1.6.5 [pr.5.1.6-36/37/38] Switch shall not impact other UEs and no solution |
Revised to S1-124213 |
Drafting session |
||
Cont |
Huawei, Telecom Italia |
ProSe 5.1.6.5 [pr.5.1.6-36/37/38] Switch shall not impact other UEs and no solution |
Agreed |
Drafting session Revision of S1-124151. Agreed by drafting session to be added to the TR |
||
Cont |
ITRI |
UE-oriented UTRAN infrastructure path and ProSe communication path switching |
Noted |
Drafting session |
||
Cont |
China Mobile |
Editorial Corrections to Use Case 5.1.11 (ProSe Application Provided by the Third-Party Application Developer) |
Revised to S1-124214 |
Drafting session |
||
Cont |
China Mobile |
Editorial Corrections to Use Case 5.1.11 (ProSe Application Provided by the Third-Party Application Developer) |
Agreed |
Drafting session Revision of S1-124072. Agreed by drafting session to be added to the TR |
||
Cont |
China Mobile |
Enhancements to Use Case 5.1.11 (ProSe Application Provided by the Third-Party Application Developer) |
Revised to S1-124215 |
Drafting session |
||
Cont |
China Mobile |
Enhancements to Use Case 5.1.11 (ProSe Application Provided by the Third-Party Application Developer) |
Agreed |
Drafting session Revision of S1-124071. Agreed by drafting session to be added to the TR |
||
Cont |
CATT |
Correction on Use Case for ProSe Application Provided by the Third-Party Application Developer |
Noted |
Late document (will not be treated as late as there are extenuating circumstances) Drafting session |
||
Cont |
Institute for Information Industry (III) |
FS_ProSe: Additional ProSe Capability Feature for Third-party ProSe Application |
Revised to S1-124371 |
|
||
Cont |
Institute for Information Industry (III) |
FS_ProSe: Additional ProSe Capability Feature for Third-party ProSe Application |
Noted |
Revision of S1-124021. Drafting session |
||
Cont |
Huawei, Telecom Italia |
ProSe 6.1 Add requirement for continuous network control |
Revised to S1-124223 |
|
||
Cont |
Huawei, Telecom Italia |
ProSe 6.1 Add requirement for continuous network control |
Revised to S1-124508 |
Revision of S1-124153. |
||
Cont |
Huawei, Telecom Italia |
ProSe 6.1 Add requirement for continuous network control |
Agreed |
Revision of S1-124153. Revision of S1-124223. Agreed to be added to the TR No presentation |
||
Cont |
Huawei |
ProSe 6.1 Add requirement on preservation of normal network operation |
Revised to S1-124509 |
|
||
Cont |
Huawei |
ProSe 6.1 Add requirement on preservation of normal network operation |
Agreed |
Revision of S1-124154. Agreed to be added to the TR No presentation |
||
Cont |
Huawei, Telecom Italia |
ProSe 6.2.6.5 [pr 60/78] Requires that the UE supports different paths |
Noted |
|
||
Cont |
General Dynamics Broadband |
Clarifications to TR22.803 - Feasibility Study for Proximity Services |
|
|||
Cont |
General Dynamics Broadband |
FS_ProSe: Technical clarifications |
Noted |
Revision of S1-124157. |
||
Cont |
Qualcomm |
FS_ProSe – Consolidate Potential Requirements |
Revised to S1-124217 |
Drafting session |
||
Cont |
Qualcomm |
FS_ProSe – Consolidate Potential Requirements |
Revised to S1-124222 |
Drafting session Revision of S1-124010. Spent the remaining time trying to agree what a CPR is and how to proceed. No discussion on actual text. Interim compromise: · Keep the discussion table but remove all reference to ultimate CRs · Reduce contributions to just the PR’s that are NOT discussed at all in Edinburgh AND discussed via email Re-open in plenary together with TI contribution S1-124056 and discuss |
||
Cont |
Qualcomm |
FS_ProSe – Consolidate Potential Requirements |
Agreed |
Revision of S1-124217. Agreed to be added to the TR No presentation |
||
Cont |
Telecom Italia |
FS_ProSe – General Requirements |
Noted |
|
||
9.2.8 New use cases |
||||||
Cont |
LG Electronics, Inc. |
FS_ProSe: Discovery Use Case for Enhanced Quality of User Experience |
Revised to S1-124415 |
|
||
Cont |
LG Electronics, Inc. |
FS_ProSe: Discovery Use Case for Enhanced Quality of User Experience |
Noted |
Revision of S1-124034. |
||
Cont |
InterDigital, Alcatel-Lucent, Qualcomm |
Discovery permissions for restricted discovery use case |
Noted |
|
||
Cont |
Renesas Mobile Europe Ltd |
Changes and comments to S1-124042 - Discovery permissions for restricted discovery use case |
Noted |
|
||
Cont |
Bell Canada |
MOCN_GWCN considerations in ProSe Use Cases |
Revised to S1-124423 |
|
||
Cont |
Bell Canada |
MOCN_GWCN considerations in ProSe Use Cases |
Agreed |
Revision of S1-124043. Agreed to be added to the TR No presentation |
||
Cont |
Bell Canada |
MOCN_GWCN_Public_Safety network considerations in ProSe Use Cases |
Noted |
|
||
Cont |
ITRI |
Spectrum Leasing and Management Use Case |
Noted |
|
||
Cont |
ITRI |
ProSe Services for Parking in a Building or Small Area |
Noted |
|
||
Cont |
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Neustar, ETRI |
FS_ProSe: Identifying ProSe-enabled UEs |
Revised to S1-124469 |
Cover new use case only here New use case: MNO subscription change Other changes to be reviewed in section 9.2.5 |
||
Cont |
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Neustar, ETRI |
FS_ProSe: Identifying ProSe-enabled UEs |
Noted |
Cover new use case only here New use case: MNO subscription change Other changes to be reviewed in section 9.2.5 Revision of 'S1-124029. |
||
Cont |
General Dynamics Broadband |
FS_ProSe: A new use case - Co-existence of ProSe Communication and E-UTRAN communication |
Revised to S1-124470 |
Revision
of S1-124157. |
||
Cont |
General Dynamics Broadband |
FS_ProSe: A new use case - Co-existence of ProSe Communication and E-UTRAN communication |
Agreed |
Revision of S1-124157. Revision of S1-124320. Agreed to be added to the TR No presentation |
||
9.2.9 Conclusion |
||||||
Cont |
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Qualcomm Inc. |
FS_ProSe: ProSe conclusion |
Revised to S1-124434 |
|
||
Cont |
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Qualcomm Inc. |
FS_ProSe: ProSe conclusion |
Revised to S1-124510 |
Revision of S1-124033. |
||
Cont |
Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Qualcomm Inc. |
FS_ProSe: ProSe conclusion |
Agreed |
Revision of S1-124033. Revision of S1-124434. Agreed to be added to the TR No presentation |
||
9.2.10 FS_ProSe Drafting Session Information |
||||||
AGE |
Rapporteur |
FS_ProSe drafting Agenda |
Revised to S1-124401 |
|
||
AGE |
Rapporteur |
FS_ProSe drafting Agenda |
Noted |
Revision of S1-124201. |
||
REP |
Rapporteur |
FS_ProSe drafting Report |
Revised to S1-124221 |
|
||
REP |
Rapporteur |
FS_ProSe drafting Report |
Approved |
Revision of S1-124202. |
||
Summary of
drafting session -
Agreed various editorial updates and clean-up - Agreed contributions updating QoS charging, ProSe Communication Switching, VPLMN control of discovery, etc - Identified documents that could be merged on EPS ProSe Discovery, Restricted Discovery, inter-PLMN roaming for ProSe Communications - Interim compromise on consolidated potential requirements: · Keep the discussion table but remove all reference to ultimate CRs · Reduce contributions to just the PR’s that are NOT discussed at all in Edinburgh AND discussed via email · Re-open in plenary together with TI contribution 4056 and discuss |
||||||
TR |
Rapporteur |
TR 22.803 on FS_ProSe |
Agreed |
Agreed as the basis for future contributions |
||
CP |
Rapporteur |
Cover page for TR 22.803 |
Revised to S1-124514 |
|
||
CP |
Rapporteur |
Cover page for TR 22.803 |
Approved |
Revision of S1-124485. Agreed to send the TR to SA for approval Telecom Italia does not agree with the decision to send the TR for approval No presentation |
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
9.3 FS_UPCON: User plane congestion management [SP-110819] |
||||||
TR |
Rapporteur |
TR22.805 12.0.1 Feasibility Study on User Plane Congestion Management |
Noted |
|
||
CR |
KDDI |
22.805 v12.0.1: Update of Consolidated Requirements; Addition of Use Case to Requirements Traceability Annex |
Revised to S1-124388 |
WI code UPCON Rel-12 CR0001R- Cat F |
||
CR |
KDDI |
22.805 v12.0.1: Update of Consolidated Requirements; Addition of Use Case to Requirements Traceability Annex |
Revised to S1-124439 |
WI code UPCON Rel-12
CR0001R- Cat F Revision of S1-124093. |
||
CR |
KDDI |
22.805 v12.0.1: Update of Consolidated Requirements; Addition of Use Case to Requirements Traceability Annex |
Revised to S1-124475 |
WI code UPCON Rel-12
CR0001R- Cat F Revision of S1-124093. Revision of S1-124388. |
||
CR |
KDDI |
22.805 v12.0.1: Update of Consolidated Requirements; Addition of Use Case to Requirements Traceability Annex |
Agreed |
WI code UPCON Rel-12
CR0001R- Cat F Revision of S1-124093. Revision of S1-124388. Revision of S1-124439. No presentation |
||
9.4 FS_RSE: RAN Sharing enhancements [SP-110820] |
||||||
9.4.1 FS_RSE Contributions |
||||||
Cont |
NEC |
Editors corrections to TR 22.852 |
Revised to S1-124187 |
drafting session: This document provides some clarifications / corrections to TR 22.852 provided by the editor |
||
Cont |
NEC |
Editors corrections to TR 22.852 |
Agreed |
Revision of S1-124055. Agreed by drafting session to add to the TR |
||
Cont |
NEC |
Proposed consolidated requirements for TR 22.852 |
Revised to S1-124186 |
drafting session: This document collects and harmonizes the potential requirements expressed from the individual use cases of TR 22.852 |
||
Cont |
NEC |
Proposed consolidated requirements for TR 22.852 |
Agreed |
Revision of S1-124049. Agreed by drafting session to add to the TR |
||
Cont |
Huawei |
Update precondition on implementing MDT for Host Provider |
Revised to S1-124188 |
drafting session: This contribution add a pre-condition for activation of
MDT task from Host provider and modifies the potential requirements. |
||
Cont |
Huawei |
Update precondition on implementing MDT for Host Provider |
Agreed |
Revision of S1-124060. Agreed by drafting session to add to the TR No presentation |
||
Cont |
Huawei |
Update use case on radio resource scheduling in RAN sharing case |
Revised to S1-124189 |
drafting session: This contribution updates the pre-condition for radio resource scheduling in RAN sharing case and modifies the potential requirements. |
||
Cont |
Huawei |
Update use case on radio resource scheduling in RAN sharing case |
Agreed |
Revision of S1-124061. |
||
Cont |
NEC, Intel |
Use case for On-demand Automated Capacity Brokering |
|
|||
Cont |
NEC, Intel |
Use case for On-demand Automated Capacity Brokering |
Revised to S1-124476 |
Revision of S1-124050. |
||
Cont |
NEC, Intel |
Use case for On-demand Automated Capacity Brokering |
Revised to S1-124483 |
Revision of S1-124050. Revision of S1-124197. |
||
Cont |
NEC, Intel |
Use case for On-demand Automated Capacity Brokering |
Agreed |
Revision of S1-124050. Revision of S1-124197. Revision of S1-124476. Agreed to be added to the TR No presentation |
||
Cont |
NEC, Intel |
Use case for On-demand Automated Capacity Brokering |
Agreed |
Revision of S1-124050. drafting session Agreed by drafting session to add to the TR No presentation |
||
Cont |
Huawei, Deutsche Telekom |
New use case on PLMN selection enhancements towards a shared area |
Revised to S1-124184 |
drafting session |
||
Cont |
Huawei, Deutsche Telekom |
New use case on PLMN selection enhancements towards a shared area |
Agreed |
drafting session Revision of S1-124059. Agreed by drafting session to add to the TR No presentation |
||
LS OUT |
Huawei |
LS on PLMN selection enhancements in a shared RAN |
Noted |
|
||
9.4.2 FS_RSE Drafting Session Information |
||||||
AGE |
Rapporteur |
FS_RSE Drafting Agenda |
Noted |
|
||
REP |
Rapporteur |
FS_RSE Drafting Report |
Approved |
|
||
Summary of
drafting session 4 drafting sessions on FS_RSE provided the following results: - One use case on “On-demand Automated Capacity Brokering” agreed - One
use case on “PLMN selection enhancements towards a shared area” agreed in
principle as an optional requirement. - Huawei will draft a LS S1-124185 to CT1 to inform on this decision and ask for further guidance on the requirement (the requirement would be incompatibility with behaviour of old (Rel-6) UEs) - Updates on other use cases - Update on the scope of TR 22.852 to clearly indicate applicability to E-UTRAN only. - Intensive work on consolidating potential requirements. These are in relative good shape now but still need further work The meeting agreed to request sending TR 22.852 for information to SA. (S1-124182) At the next meeting we expect to finalize the TR. (2 sessions needed) There is no intention to create normative work for RSE in
Rel-12. |
||||||
TR |
Rapporteur |
TR 22.852 on FS_RSE |
Revised to S1-124482 |
|
||
TR |
Rapporteur |
TR 22.852 on FS_RSE |
Agreed |
Revision of S1-124182. Agreed as the basis for future contributions No presentation |
||
CP |
Rapporteur |
Cover page for TR 22.852 |
Agreed |
Agree to send TR to SA for information |
||
9.5 FS_ACDC: Application specific congestion control for data communication [SP-120546] |
||||||
9.5.1 FS_ACDC Contributions |
||||||
TR |
NTT DOCOMO |
ACDC TR 22.806 skeleton |
Revised to S1-124276 |
drafting session |
||
TR |
NTT DOCOMO |
ACDC TR 22.806 skeleton |
Agreed |
drafting session Revision of S1-124119. “Consideration” section was changed to “Analysis”. Agreed by drafting session to add to the TR No presentation |
||
Cont |
NTT DOCOMO |
ACDC: Introduction |
Revised to S1-124277 |
drafting session |
||
Cont |
NTT DOCOMO |
ACDC: Introduction |
Agreed |
drafting session Revision of S1-124120. Editorial cleanup
was done. Agreed by drafting session to add to the TR No presentation |
||
Cont |
NTT DOCOMO |
ACDC: Scope |
Revised to S1-124278 |
drafting session |
||
Cont |
NTT DOCOMO |
ACDC: Scope |
Revised to S1-124283 |
drafting session Revision of S1-124121. Also agreed to look
for contributions in the next meeting to further clarify whether the Scope
includes commercial aspects or not. Agreed by drafting session to add to the TR No presentation |
||
Cont |
NTT DOCOMO |
ACDC: Scope |
Agreed |
drafting session Revision of S1-124121. Revision of S1-124278. Agreed to add to the TR No presentation |
||
Cont |
NTT DOCOMO |
ACDC activation for UE-initiated applications |
Revised to S1-124273 |
drafting session: A basic use case: An ACDC policy rule for allowed application lists is in UE. Network activates it. The UE judges whether to allow/restrict the application. (written based on S1-124107) |
||
Cont |
Huawei, Hisilicon |
New use case on ACDC activation for UE in idle mode |
Revised to S1-124273 |
drafting session: A basic use case: Restricted
for idle mode. (The original of S1-124123) |
||
Cont |
Huawei, Hisilicon,
NTT DOCOMO |
New use case on ACDC activation for UE-initiated applications |
Revised to S1-124279 |
drafting session: Revision of S1-124107
and S1-124123 A basic use case: An ACDC policy rule for allowed application lists is in UE. Network activates it. The UE judges whether to allow/restrict the application. Discussion of whether local regulations apply, if so, for which country for a roaming UE. Also, what happens to an ongoing service when ACDC is applied. Relationship with other access control is captured in Editor’s NOTE as FFS. |
||
Cont |
Huawei, Hisilicon, NTT DOCOMO |
New use case on ACDC activation for UE-initiated applications |
Revised to S1-124281 |
drafting session: Revision of S1-124107 and S1-124123 Revision of S1-124273. A
pre-condition “Alice and Bob are not roaming” was added. A sentence “The
network becomes congested” and a similar text were deleted to clarify the
difference from the UPCON type situation. Two Editor’s NOTEs were added to
solicit further contributions for handling on-going services and for roaming scenario. |
||
Cont |
Huawei, Hisilicon, NTT DOCOMO |
New use case on ACDC activation for UE-initiated applications |
Revised to S1-124282 |
drafting session: Revision of S1-124107 and S1-124123 Revision of S1-124273. Revision of S1-124279 and S1-124374. An aspect of dynamic
way of enforcing policy was added. Dependency on regional regulation was
added. Editorial correction was made. Agreed in principle by drafting session to add to the TR No presentation |
||
Cont |
Huawei, Hisilicon, NTT DOCOMO |
New use case on ACDC activation for UE-initiated applications |
Agreed |
drafting session: Revision of S1-124107 and S1-124123 Revision of S1-124273. Revision of S1-124279 and S1-124374. Revision of S1-124281. Agreed to be added to the TR No presentation |
||
Cont |
Huawei, Hisilicon |
New use case on ACDC activation for UE in connected mode |
Revised to S1-124274 |
drafting session: An enhancement of ACDC policies: Different ACDC policies for different subscribers. Restricted for connected mode. Uses the existing connection instead of broadcast. Comment: S1-124104, S1-124109, and S1-124124 could be merged. |
||
Cont |
China Telecom |
User Level Application specific Congestion control |
Revised to S1-124274 |
drafting session: An enhancement of ACDC policies: Different ACDC policies for different subscribers (e.g. normal or platinum subscriber, roaming user) Comment: S1-124104, S1-124109, and S1-124124 could be merged. |
||
Cont |
NTT DOCOMO |
ACDC activation for UE-initiated applications, dependent on subscription |
Revised to S1-124274 |
drafting session: An enhancement of ACDC policies: Different ACDC policies for different subscribers. ACDC is applied for AC0-9 and AC11-15. Comment: S1-124104, S1-124109, and S1-124124 could be merged. |
||
Cont |
China Telecom, NTT
DOCOMO, Huawei, Hisilicon |
User Level Application specific Congestion control |
Revised to S1-124280 |
drafting session: Revision of S1-124104, S1-124109 and S1-124124. A basic use case: An ACDC policy rule for allowed application lists is in UE. Network activates it. The UE judges whether to allow/restrict the application. Discussion on whether some aspects are part of UPCON (or already supported by PCC), whether the Study covers emergency scenarios only or includes other commercial use. An enhancement of ACDC policies: Different ACDC policies for different subscribers. ACDC is applied for AC0-9 and AC11-15. |
||
Cont |
China Telecom, NTT DOCOMO, Huawei, Hisilicon |
User Level Application specific Congestion control |
Noted |
drafting session: Revision of S1-124104, S1-124109 and
S1-124124. Revision of S1-124274. A pre-condition “Alice
and Bob are not roaming” was added. Changed to depending only on user
subscription. A potential requirement on AC was deleted, since it is not
aligned with the use case description. The use case is related to commercial aspect. Concern was expressed for inclusion of commercial aspects. |
||
Cont |
China Telecom |
Different ACDC policy based on network status |
Revised to S1-124275 |
drafting session: An enhancement of ACDC policies: Multiple different ACDC policies per UE. |
||
Cont |
China Telecom |
Different ACDC policy based on network status |
Noted |
drafting session: Revision of S1-124105. Related more to commercial aspect |
||
Cont |
NTT DOCOMO |
ACDC: Considerations |
Withdrawn |
|
||
Cont |
Intel Corporation |
Emergency Use Case for ACDC |
Revised to S1-124374 |
drafting session: Alternative ACDC policy rules: The policy rules are related to RAN user plane congestion. UE judges restriction of application based on that. |
||
Cont |
Intel Corporation |
Emergency Use Case for ACDC |
Revised to S1-124281 |
Revision of S1-124103. drafting session: Alternative ACDC policy rules: The policy
rules are related to emergency. Discussion that there is no need to inform the UE of the emergency case and that the requirements do not need to be specific to emergency. Also, the application does not have to be informed. In the end, there is no need to have a separate use case, dynamic policy aspect now merged into S1-124281 |
||
InterDigital Communications |
UE assisted congestion management based on application type |
Noted |
drafting session: Alternative
service flow “network-controlled method”: Network sends a list of applications to UE to be reported to the network when such application is initiated. UE reports application name to the network. The network judges whether to allow/restrict the application based on network congestion status. Concern was expressed that this mechanism does not work for emergency case, since UEs repeatedly try to make MO requests. |
|||
WID |
NTT DOCOMO |
WID proposal for Application specific Congestion control for Data Communication for situation of disaster |
Noted |
|
||
9.5.2 FS_ACDC Drafting Session Information |
||||||
AGE |
Rapporteur |
ACDC drafting Agenda |
Noted |
|
||
REP |
Rapporteur |
ACDC drafting Report |
Approved |
|
||
Summary of
drafting session - Agreed Skeleton, Introduction, and Scope. - Agreed in principle a baseline Use Case for non-roaming. - Also agreed to look for contributions in the next meeting to further clarify whether the Scope includes commercial aspects or not. - Captured in Editor’s NOTEs as FFS the followings: relationship with other access control, handling of on-going services, a roaming case. -
To
Plenary: S1-124281 was agreed in principle in the Drafting Session, but needs to be agreed
in Plenary to confirm the last-minute clean-up. |
||||||
TR |
Rapporteur |
TR 22.806 on ACDC |
Agreed |
Agreed as the basis for future contributions |
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||
9.6 Other Study Item contributions |
||||||
10 Work planning contributions |
||||||
10.1 Work Plan |
||||||
WP |
ETSI Secretariat |
3GPP Work Plan: extract for SA1#59 |
Noted |
|
||
10.2 Work Item/Study Item status update |
||||||
REP |
Rapporteur (KPN) |
MTCe-SRM Status Update |
Noted |
|
||
REP |
Rapporteur (KPN) |
MTCe- SIMSE Status Update |
Noted |
|
||
REP |
Rapporteur (KDDI) |
UPCON Status Update |
Noted |
|
||
REP |
Rapporteur (Huawei) |
FS_MTCe Status Update |
Noted |
|
||
REP |
Rapporteur (Qualcomm) |
FS_ProSe Status Update |
Noted |
|
||
REP |
Rapporteur (NEC) |
FS_RSE Status Update |
Noted |
|
||
REP |
Rapporteur (NTT DOCOMO) |
FS_ACDC Status Update |
Noted |
|
||
REP |
Rapporteur (Qualcomm) |
ProSe Status Update |
Noted |
|
||
REP |
Rapporteur (Orange) |
SEQ_ALERT Status Update |
Noted |
|
||
REP |
Rapporteur (NSN) |
GCSE_LTE Status Update |
Noted |
|
||
REP |
Rapporteur (Orange) |
LangInfo Status Update |
Noted |
|
||
REP |
Rapporteur (China Mobile) |
IMS_WebRTC |
Noted |
|
||
10.3 Others |
||||||
Guidance for Rel-12 Stage 1
freeze The SA1#61 Prague meeting is our last meeting before the Rel-12 Stage 1 freeze in March. Therefore, SA1#61 in Prague will focus on completion of normative Rel-12 work. As a result, at SA1#61 in Prague: - new Rel-12 normative work items will only allowed with very good justification, and after prior consultation with the SA1 chairman - items below will be given low priority and may not be treated: o study item-related contributions o contributions for Rel-13 onwards -
Rel-12 normative work items that cannot be completed,
and not postponed to Rel-13, will require an Exception Sheet (S1-124008)
to be completed by the Rapporteur |
||||||
Scope and mandate for SA1 ad
hoc in Prague Scope: -
GCSE_LTE
-
completion
of ProSe TR -
preparation
of normative CRs for ProSe Output of ad hoc exempt from the meeting deadline. Meeting name should be updated: SA1 ad hoc on GCSE_LTE and ProSe Ad hoc mandate: to agree contributions within scope. SA1 plenary to review and agree the output of the ad hoc. |
||||||
Is an additional ad hoc
meeting needed for ProSe/GCSE_LTE in March? Decision to be made
by SA1#61 in Prague |
||||||
Cont |
ETSI Secretariat |
SA1 Delegate Guidelines |
Noted |
|
||
Cont |
WG Chairman |
WI Exception Sheet template |
Noted |
|
||
Cont |
WG Chairman |
Proposal for requirement reference numbers |
Noted |
|
||
11 Next meetings |
||||||
11.1 Calendar |
||||||
2013 meetings: SA1 ad hoc on Public Safety Aspects 23 – 25 Jan 2013 Prague, Czech Republic SA1#61 28 Jan – 1 Feb 2013 Prague, Czech Republic Joint meeting with SA2 SA1#62 6 – 10 May 2013 New Delhi, India SA1#63 19 – 23 Aug 2013 Zagreb, Croatia SA1#64 11 – 15 Nov 2013 North America Mega meeting 2014 meetings: SA1#65 20 – 24 Jan 2014 Taiwan? TBD Possible joint meeting with SA2/SA3 SA1#66 12 – 16 May 2014 Japan? TBD SA1#67 18 – 22 Aug 2014 Europe, TBD SA1#68 17 – 21 Nov 2014 North America, TBD Possible mega meeting |
||||||
12 Any other business |
||||||
13 Close |
||||||
Close by 16:00 on Friday |
||||||
14 Withdrawn documents (admin purposes only) |
||||||
|
Delegate |
User level control use case for ACDC |
Withdrawn |
|
||
|
Delegate |
Different ACDC policy based on network status |
Withdrawn |
|
||
|
NTT DOCOMO |
ACDC: Scope |
Withdrawn |
|
||
|
Interdigital, Alcatel-Lucent, Intel |
Revisit of security requirements for ProSe |
Withdrawn |
|
||
|
KDDI |
LS on UPCON Requirements Prioritization |
Withdrawn |
|
||
|
Qualcomm Inc |
FS_ProSe - Revise 'Conclusion & Recommendations' |
Withdrawn |
|
||
|
Intel |
Dynamic RAN Sharing |
Withdrawn |
|
||
|
|
Strangers Discovery Requirement for Use Case 5.1.1 (Restricted ProSe Discovery Use Case) |
Withdrawn |
|
||
15 Document numbers to be allocated (admin purposes only) |
||||||
Contents
1.3 Previous
SA1 meeting report
2 Issues for early consideration
3.2 Report
from SA1 GCSE_LTE ad hoc meeting (8 – 9 November 2012)
3.3 Authentication
for Common IMS
3.4 Mechanism
to disable PWS for Rel-11
3.5 Public
safety work status update
4 Liaison Statements (including related contributions)
5 Study and Work Items: New and Revisions
5.1 Revisions
of existing WIDs (including related contributions)
5.2 New
Study and Work Items (including related contributions)
5.3 Proposals
for new work (precursor to future Study and Work Items)
6 Rel-10 and earlier contributions
7.1 SIMTC:
System Improvements to Machine-Type Communications [SP-110877]
7.2 Other
Rel-11 contributions
8.1 MTCe-SIMSE:
Interworking with M2M service enablement layer [SP-120436]
8.2 GCSE_LTE:
Group communication system enablers for LTE [SP-120421]
8.2.2 GCSE_LTE
drafting session information
8.3 WLAN_NS:
WLAN network selection for 3GPP terminals [SP-120259] (SA1 secondary
responsibility)
8.4 MTCe-SRM:
Service requirement maintenance [SP-120541]
8.5 UPCON:
User plane congestion management [SP-120545]
8.6 Other
Rel-12 contributions
9.1 FS_MTCe:
Enhancements for Machine-Type Communications [SP-100448]
9.2 FS_ProSe:
Proximity-based Services [SP-110638]
9.2.1 Editorial
and other clean-up
9.2.2 Terminology
and definitions
9.2.6 Security,
privacy and lawful intercept aspects
9.2.7 Other
clarification and updates
9.2.10 FS_ProSe
Drafting Session Information
9.3 FS_UPCON:
User plane congestion management [SP-110819]
9.4 FS_RSE:
RAN Sharing enhancements [SP-110820]
9.4.2 FS_RSE
Drafting Session Information
9.5 FS_ACDC:
Application specific congestion control for data communication [SP-120546]
9.5.2 FS_ACDC
Drafting Session Information
9.6 Other
Study Item contributions
10 Work planning contributions
10.2 Work
Item/Study Item status update
14 Withdrawn documents (admin purposes only)
15 Document numbers to be allocated (admin purposes only)