3GPP TSG-SA WG1 Meeting #61 S1-131002
Prague, Czech Republic, 28th January
– 1st February 2013
Title: Draft
SA1#61 Agenda with tdoc allocation
Source: SA1 Chairman/SA1 Vice Chairmen/MCC
Contact: Mona Mustapha
[mona.mustapha@vodafone.com]
SA1 DRAFT SCHEDULE
The meeting will start
at 09:00 local time on Monday and will close by 16:30 local time on Friday, at
the latest.
MEETING ROOMS:
Room A:
Plenary/Drafting = Tycho +
Kepler
Room B: Breakout/Drafting = Stella
SA1/SA2
Joint meeting = Meridian
|
|
Monday |
Tuesday |
Wednesday |
Thursday |
Friday |
Q0 |
08:00 09:00 |
|
SA1/SA2
JM1: 9.1 JM1 docs end by 08:50 |
Drafting: 7.2 GCSE_LTE (Rm A) =============== 8.5 FS_ ACDC (Rm B) |
Drafting: ACDC |
|
Q1 |
09:00 10:30 |
Plenary: 1. Opening 3. Report/Action Items 4. LS |
Plenary: 7.1 MTCe-SIMSE 7.4 MTCe-SRM 8.1 FS_MTCe 6. Rel-11 7.8 LangInfo 7.10 TEI12 |
Drafting: 7.2 GCSE_LTE (Rm A) =============== 8.4 FS_RSE (Rm B) |
Plenary: 7.6/8.2 ProSe 8.1 FS_MTCe 4. LS 5. New WIDs 7.6/8.2 ProSe |
Plenary: 7.2 GCSE_LTE 7.6/8.2 ProSe 7.7 IMS_WebRTC 4. LS (San Diego scope) |
Q2 |
11:00 12:30 |
Plenary: 4. LS 5. New WIDs end by 13:00 |
Plenary: 7.2 GCSE_LTE (4. ESID WID + LS to CT1) |
Plenary: 7.5/8.3 UPCON 7.6/8.2 ProSe |
Plenary: 7.7 IMS_WebRTC 7.10 TEI12 7.6/8.2 ProSe |
Plenary: 7.7 IMS_WebRTC 8.5 ACDC 4. LS 10.1 Work plan 10.2 Status update |
|
Lunch |
|
|
13:15 IMS_WebRTC |
12:30 ACDC drafting 13:15 ProSe one-to-one communication review |
|
Q3 |
14:00 15:30 |
Plenary: LS from
SA3 on PWS 7.5/8.3 (FS)UPCON 7.6/8.2 ProSe |
Plenary: (4. ESID WID + LS to CT1) Review SA2
ProSe and UPCON Questions 7.6/8.2 ProSe |
Plenary: (ProSe/GCSE
work focus) 7.2 GCSE_LTE 7.6/8.2 ProSe |
Plenary: 7.6/8.2 ProSe 7.2 GCSE_LTE 6. Rel-11 7.4 MTCe-SRM 7.8 LangInfo |
Plenary: Revisions |
Q4 |
16:00 17:30 |
Plenary: (decision
on location of extra meeting) Drafting session intro (GCSE/ACDC/RSE) 7.7 IMS_WebRTC |
Plenary: 7.6/8.2 ProSe 17:30
review SA1 input to JM2 end by 17:45 |
Plenary: 7.6/8.2 ProSe (Relay
number of hops) end by 18:00 |
Plenary: 8.5 ACDC + new WID (SMS fraud) (Barring premium rate numbers) 7.6/8.2 ProSe |
Plenary: |
Q5 |
17:30 19:00 |
Plenary: 7.7 IMS_WebRTC (drafting
18:15 to 20:00) |
start at 18:00 SA1/SA2
JM2: 9.3 ProSe/UPCON end by 19:30 |
MMS starts 19:00 |
Plenary: 8.4 FS_RSE 7.1 MTCe-SIMSE 7.6/8.2 ProSe |
|
NOTE:
Plenary slots and drafting slots scheduled based
on contributions submitted
Allocation for (FS)ProSe, GCSE_LTE, drafting slots and
other items depend on the results of the ad hoc
Restrictions:
ProSe cannot be in parallel with GCSE_LTE
IMS_WebRTC cannot be in parallel with ProSe
or GCSE_LTE
FS_MTCe requested for plenary session
No ProSe/GCSE_LTE on MonQ4/Q5 to avoid
overlap with SA2 ProSe
Contribution Guidelines
SA1 AGENDA
AGE |
SA1 Chairman |
Draft SA1#61 Agenda |
Revised to S1-131001 |
|
|||
AGE |
SA1 Chairman |
Draft SA1#61 Agenda with tdoc allocation |
Revised to S1-131002 |
Revision of S1-131000. |
|||
AGE |
SA1 Chairman |
Final SA1#61 Agenda with tdoc allocation |
Approved |
Revision of S1-131000. Revision of S1-131001. No presentation |
|||
|
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 |
|
|||||
REP |
ETSI Secretariat |
Draft Minutes of SA1#60 |
Revised to S1-131005 |
|
|||
REP |
ETSI Secretariat |
Draft Minutes of SA1#60 |
Approved |
Revision of S1-131004. No presentation |
|||
REP |
ETSI Secretariat |
Draft Minutes of SA1 GCSE_LTE ad hoc |
Revised to S1-131007 |
|
|||
REP |
ETSI Secretariat |
Draft Minutes of SA1 GCSE_LTE ad hoc |
Approved |
Revision of S1-131006. No presentation |
|||
Cont |
ETSI Secretariat |
SA1 Delegate Guidelines |
Noted |
|
|||
None |
|||||||
Incoming LS from CT1 as
they are meeting the same week (S1-131100, S1-131105 and S1-131106) |
|||||||
REP |
SA1 Chairman |
SA1-related topics at SA#58 |
Noted |
Proposed to be noted without presentation |
|||
3.2 Report from SA1 ProSe and GCSE_LTE ad hoc meeting (23 – 25 January 2013) |
|||||||
TO |
S1-130203 (ETSI Secretariat) |
LS on results of SA1 ad-hoc on GCSE_LTE and ProSe submitted to SA1 (original version) |
Noted |
|
|||
TO |
MCC/Chair |
LS on results of SA1 ad-hoc on GCSE_LTE and ProSe submitted to SA1 (post-meeting revised version) |
Noted |
|
|||
REP |
Rapporteur (Qualcomm) |
ProSe/FS_ProSe Status update |
Approved |
Seen in ad hoc as S1-130201 |
|||
REP |
Rapporteur (Nokia Siemens Networks) |
GCSE_LTE Status update |
Revised to S1-131171 |
Seen in ad hoc as S1-130137 |
|||
REP |
Rapporteur (Nokia Siemens Networks) |
GCSE_LTE Status update |
Approved |
Seen in ad hoc as S1-130137 Revision of S1-131156. No presentation |
|||
TS |
Rapporteur (Nokia Siemens Networks) |
TS 22.468 output of ad hoc |
Agreed |
Ad hoc allocated as S1-130133 Agreed as the basis of contributions for this meeting |
|||
See the following agenda items for
allocation of documents from the ad hoc: -
FS_ProSe: -
8.2.1 for agreed CRs to TR 22.803 -
8.2.2 for reviewed/revised CRs to TR 22.803 -
8.2.3 for untreated documents -
GCSE_LTE: -
7.2.1.1 for reviewed/revised documents -
7.2.1.2 for untreated documents -
Other
documents: -
4. for document related to public safety LS from SA
plenary |
|||||||
REP |
ETSI Secretariat |
Draft Minutes of SA1 ProSe and GCSE_LTE ad hoc |
Noted |
|
|||
Cont |
Rapporteur (Qualcomm) |
ProSe Work Focus |
Revised to S1-131172 |
Seen in ad hoc as S1-130194 |
|||
Cont |
Rapporteur (Qualcomm) |
ProSe Work Focus |
Revised to S1-131251 |
Seen in ad hoc as S1-130194 Revision of S1-131157. |
|||
Cont |
Rapporteur (Qualcomm) |
ProSe Work Focus |
Agreed |
Seen in ad hoc as S1-130194 Revision of S1-131157. Revision of S1-131172. Agreed as the basis for SA1 internal scheduling No presentation |
|||
Cont |
Rapporteur (Nokia Siemens Networks) |
List of GCSE Features |
Revised to S1-131173 |
Seen in ad hoc as S1-130146 |
|||
Cont |
Rapporteur (Nokia Siemens Networks) |
List of GCSE Features |
Revised to S1-131250 |
Seen in ad hoc as S1-130146 Revision of S1-131158. |
|||
Cont |
Rapporteur (Nokia Siemens Networks) |
List of GCSE Features |
Revised to S1-131252 |
Seen in ad hoc as S1-130146 Revision of S1-131158. Revision of S1-131173. |
|||
Cont |
Rapporteur (Nokia Siemens Networks) |
List of GCSE Features |
Agreed |
Seen in ad hoc as S1-130146 Revision of S1-131158. Revision of S1-131173. Revision of S1-131250. Agreed as the basis for SA1 internal scheduling No presentation |
|||
Is an extra meeting in April needed? If yes,
scope and mandate? Yes
and extra meeting is needed. SA1 agreed: a) week of 8 April in San Diego Duration of meeting: 4 days (Monday to Thursday, 8 -11 April 2013) Scope
and mandate: Proposal to have this as an ordinary SA1 meeting
(SA1#61bis) covering only Rel-12 topics, i.e. GCSE_LTE and ProSe Post-meeting clarification: CRs on
ProSe agreed in San Diego require consensus for approval at SA1#62 |
|||||||
Dialled digit information
in Emergency Calls |
|||||||
TO |
S1-124259/C1-124133 (Telecom Italia) |
Postponed LS on Use of Dialled Digit Information in Emergency Calls |
Noted, answer in S1-131214 |
Postponed
from SA1#60 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? Response required |
|||
LS OUT |
Telecom Italia |
LS on Use of Dialled Digit Information in Emergency Calls |
Revised to S1-131224 |
Answer
to S1-131100. |
|||
LS OUT |
Telecom Italia |
LS on Use of Dialled Digit Information in Emergency Calls |
Revised to S1-131227 |
Answer to S1-131100. Revision
of S1-131214. |
|||
LS OUT |
Telecom Italia |
LS on Use of Dialled Digit Information in Emergency Calls |
Approved |
Answer to S1-131100. Revision of S1-131214. Revision
of S1-131224. No
presentation |
|||
Cont |
Telecom Italia |
Discussion Paper Emergency Session Identification WID |
Noted |
Moved from section 5.2 |
|||
WID |
Telecom Italia |
Proposed new WID on Emergency Call Identification |
Agreed |
Moved from section 5.2 |
|||
CR |
Telecom Italia, Huawei, Ericsson,Orange, Qulacomm |
22.101 v12.3.0: Requirement on emergency IM CN service |
Revised to S1-131174 |
Moved from section 5.2 WI code ESID Rel-12 CR0445R- Cat B |
|||
CR |
Telecom Italia, Huawei, Ericsson,Orange, Qulacomm |
22.101 v12.3.0: Requirement on emergency IM CN service |
Revised to S1-131223 |
Moved from section 5.2 WI code ESID Rel-12 CR0445R- Cat B Revision of S1-131054. |
|||
CR |
Telecom Italia, Huawei, Ericsson,Orange, Qulacomm |
22.101 v12.3.0: Requirement on emergency IM CN service |
Revised to S1-131226 |
Moved from section 5.2 WI code ESID Rel-12 CR0445R-
Cat B Revision of S1-131054. Revision of S1-131174. |
|||
CR |
Telecom Italia, Huawei, Ericsson,Orange, Qulacomm |
22.101 v12.3.0: Requirement on emergency IM CN service |
Agreed |
Moved from section 5.2 WI code ESID Rel-12 CR0445R-
Cat B Revision of S1-131054. Revision of S1-131174. Revision of S1-131223. |
|||
PSAP callback |
|||||||
TO |
C1-125000 (Deutsche Telekom) |
LS on PSAP callback requirements |
Postponed |
CT1 asks SA1 if PSAP callback requirements shall be handled: a) in the network and the UE, or Response required |
|||
Cont |
Research In Motion UK Ltd |
Discussion on incoming LS from CT1 (C1-125000/S1-131105) on PSAP call-back |
Noted |
|
|||
CR |
Research In Motion UK Ltd |
22.101 v11.8.0: Alignment of PSAP call-back requirements |
Noted |
WI code NOVES Rel-11 CR0442R- Cat F |
|||
CR |
Research In Motion UK Ltd |
22.101 v12.3.0: Alignment of PSAP call-back requirements |
Noted |
WI code NOVES Rel-11 CR0443R- Cat A |
|||
CR |
Deutsche Telekom |
22.101 v11.8.0: Clarification of callback requirements |
Noted |
WI code TEI11 Rel-11 CR0449R- Cat F |
|||
CR |
Deutsche Telekom |
22.101 v12.3.0: Clarification of callback requirements |
Noted |
WI code TEI11 Rel-12 CR0450R- Cat A Correction needed to cover page: "Proposed change affects": cross
"Core Network" box |
|||
CR |
Deutsche Telekom |
22.173 v11.4.0: Clarification of supplementary services suppression on callbacks |
Noted |
WI code TEI11 Rel-11 CR0089R- Cat F |
|||
CR |
Deutsche Telekom |
22.173 v12.3.0: Clarification of supplementary services suppression on callbacks |
Noted |
WI code TEI11 Rel-12 CR0090R- Cat A |
|||
LS OUT |
Deutsche Telekom |
LS on PSAP callback requirements |
Noted |
Response
to: LS C1-125000 on PSAP callback requirements from CT WG1 |
|||
Barring premium rate
numbers |
|||||||
TO |
C1-125035 (Orange) |
LS Barring of Premium Rate Numbers |
Noted, answer in S1-131296 |
CT1 asks SA1 to clarify the scenarios for outgoing communications to premium rate numbers that are subject to IMS Operator Determined Barring Response required |
|||
LS OUT |
Orange |
Reply LS on Barring of Premium Rate Numbers |
Revised to S1-131180 |
Response to: LS C1-125035 from CT1on Barring of Premium Rate Numbers requirement clarification |
|||
LS OUT |
Orange |
Reply LS on Barring of Premium Rate Numbers |
Revised to S1-131296 |
Response to: LS C1-125035 from CT1on Barring of Premium Rate Numbers requirement clarification Revision of S1-131024. |
|||
LS OUT |
Orange |
Reply LS on Barring of Premium Rate Numbers |
Approved |
Response to: LS C1-125035 from
CT1on Barring of Premium Rate Numbers requirement clarification Revision of S1-131024. Revision of S1-131180. |
|||
CR |
Orange, Alcatel-Lucent |
22.041 v11.1.0: Barring of Premium Rate Numbers |
Revised to S1-131295 |
WI code TEI12 Rel-12 CR0017R- Cat F |
|||
CR |
Orange, Alcatel-Lucent |
22.041 v11.1.0: Barring of Premium Rate Numbers |
Agreed |
WI code TEI11 Rel-11 CR0017R- Cat F Revision of S1-131179. |
|||
Public Safety |
|||||||
TO |
S1-124254/S1-123051/ TCCA CCBG System Architecture Group (EADS) |
Postponed LS on General Architecture Considerations for Critical Communication Systems |
Noted |
Postponed from SA1#60 CCBG describes the
boundary between the 3GPP domain and the Application domain for SA1
consideration. Action required:
analyse and add relevant text to 22.468 (work in progress) Also reviewed at the
ad hoc in S1-130103 |
|||
TO |
S1-124253/S1-123050/ TETRA04(12)000078 (EADS) |
Postponed LS on Potential Implementation of TETRA services over LTE |
Noted |
Postponed from SA1#60 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. Action required: analyse and add relevant text to 22.468 (work in progress) Also reviewed at the ad hoc in S1-130102 |
|||
TO |
S1-123045/S1-122321/ TCCA CCBG System Architecture Group (EADS) |
Postponed LS on LS on Use Cases relevant for the Critical Communication Community |
Noted |
Postponed from SA1#59 Critical
communications use cases provided for SA1 consideration that may need to be
considered for GCSE_LTE: -
Speech Group Call Use Case -
Dispatcher Override Use Case -
Emergency Communication Use Case -
Interoperability Narrow Band - Broad Band Use Case Action required:
analyse and add relevant text to 22.468 (work in progress) Also reviewed at the ad hoc in S1-130100 |
|||
TO |
TETRA04(13)000003 |
LS on TETRA WG4 view on provision of group services over 3GPP networks |
Noted |
Explains the background behind the TC TETRA WG4 working assumption that the application layer holds the intelligence related to group related functions. Also reviewed at the ad hoc in S1-130062 |
|||
TO |
TCCA CCBG System Architecture Group |
LS on Additional Public Safety Use Cases |
Noted |
Also reviewed at the ad hoc in S1-130104 |
|||
TO |
SP-120931 (Vodafone) |
LS on Additional Public Safety and Critical Communications requirements in Release 12. |
Noted |
SA asks SA1 to consider whether or not additional Release 12 requirements need to be defined for Public Safety and Critical Communications beyond ProSe and GCSE_LTE. SA encourages SA1 to agree a corresponding WID if necessary. Response required Also provide RAN an update of ProSe and GCSE_LTE WIDs at the end of the meeting |
|||
LS OUT |
Vodafone |
LS on ProSe and GCSE_LTE status |
Revised to S1-131322 |
|
|||
LS OUT |
Vodafone |
LS on ProSe and GCSE_LTE status |
Approved |
Revision of S1-131182. No presentation |
|||
Cont |
Vodafone |
Network Resilience for Public Safety Communications |
Noted |
Also reviewed at the ad hoc in S1-130080 |
|||
LS OUT |
Vodafone |
Draft LS to CT4 and RAN3 on network resilience |
Approved |
|
|||
PWS-related |
|||||||
TO |
GP-121427 (Ericsson) |
LS on reporting PWS Indication for users in connected mode |
Noted, answer in S1-131278 |
GERAN2 asks SA1 to consider whether Stage 1 requirements should be defined to indicate to UEs in a call or data session should receive a PWS message via CBCH. Response required |
|||
LS OUT |
Ericsson |
LS on reporting PWS Indication for users in connected mode |
Approved |
GERAN2 asks SA1 to consider
whether Stage 1 requirements should be defined to indicate to UEs in a call
or data session should receive a PWS message via CBCH. Response required Answer to S1-131108. |
|||
Cont |
Ericsson |
Discussion regarding incoming LS on PWS indication in connected mode |
Noted |
|
|||
TO |
S3-130225 |
Reply LS on PWS Requirements for UEs in Limited Service State |
Noted |
Response to: S1-124503: Reply LS on PWS Requirements for UEs in Limited Service State Companies invited to provide contributions directly to SA3 for any technical proposals |
|||
MTC-related |
|||||||
TO |
one (KPN) |
LS on Service Layer interworking with 3GPP/3GPP2 defined networks |
Noted, answer in S1-131034 |
oneM2M TP asks 3GPP to: 1) note its scope 2) keep oneM2M informed of 3GPP machine type communication related work Response required |
|||
LS OUT |
KPN |
Reply LS to oneM2M on service-layer interworking |
Approved |
|
|||
LS OUT |
KPN |
LS on bulk charging |
Approved |
|
|||
LS to be noted without
presentation |
|||||||
C6-120613 (Ericsson) |
Rely LS on HPLMN or RPLMN selection UE requirement |
Noted |
CT6 agreed corrections to the Last RPLMN
Selection Indication coding description. The changes have been introduced
from Rel-7 onwards. Proposed to be noted without presentation |
||||
CC |
C1-124996 (NTT DOCOMO) |
Reply LS on Access control for UEs in RRC CONNECTED mode |
Noted |
SA1 already sent a reply to RAN2 at the last SA1 meeting for Rel-11. Proposed to be noted without presentation |
|||
5.1
Revisions
of existing WIDs
(including related contributions) |
|||||||
WID |
Orange |
ECT Blind – MMTel service description |
Noted |
|
|||
CR |
Orange |
22.173 v12.3.0: Blind Call Transfer retrieval |
Revised to S1-131266 |
WI code ECTB Rel-12 CR0088R- Cat B |
|||
CR |
Orange |
22.173 v12.3.0: Blind Call Transfer retrieval |
Noted |
WI code ECTB Rel-12 CR0088R- Cat B Revision of S1-131013. |
|||
WID |
KPN (Rapporteur) |
Update of MTCe-SRM WID after SA prioritization |
Moved to section 7.4 |
|
|||
5.2
New Study
and Work Items (including related contributions) |
|||||||
Application
specific Congestion control for Data Communication |
|||||||
WID |
NTT DOCOMO, et al |
WID proposal for Application specific Congestion control for Data Communication applied to heavy congestion scenarios |
Revised to S1-131183 |
Comment: indicate in section 2.3 table that this is Stage 1 work |
|||
WID |
NTT DOCOMO, et al |
WID proposal for Application specific Congestion control for Data Communication applied to heavy congestion scenarios |
Revised to S1-131291 |
Revision of S1-131028. |
|||
WID |
NTT DOCOMO, et al |
WID proposal for Application and Service Access Control |
Agreed |
Revision of S1-131028. Revision of S1-131183. No presentation |
|||
|
NTT DOCOMO |
Exception sheet for ASAC |
Revised to S1-131317 |
|
|||
|
NTT DOCOMO |
Exception sheet for ASAC |
Agreed |
Revision of S1-131292. No presentation |
|||
CR |
NTT DOCOMO, et al |
22.011 v11.2.0: Requirements applied to heavy congestion scenarios of ACDC |
Revised to S1-131084 |
WI code TBD Rel-12 CR0193R- Cat B |
|||
CR |
NTT DOCOMO, et al |
22.011 v11.2.0: Requirements applied to heavy congestion scenarios of ACDC |
Revised to S1-131143 |
WI code TBD Rel-12 CR0193R- Cat B Revision of S1-131029. |
|||
CR |
NTT DOCOMO, et al |
22.011 v11.2.0: Requirements applied to heavy congestion scenarios of ACDC |
Revised to S1-131270 |
WI code TBD Rel-12 CR0193R- Cat
B Revision of S1-131029. Revision of S1-131084. |
|||
CR |
NTT DOCOMO, et al |
22.011 v11.2.0: Requirements applied to heavy congestion scenarios of ACDC |
Revised to S1-131285 |
WI code TBD Rel-12 CR0193R- Cat
B Revision of S1-131029. Revision of S1-131084. Revision of S1-131143. |
|||
CR |
NTT DOCOMO, et al |
22.011 v11.2.0: Requirements applied to heavy congestion scenarios of ACDC |
Noted |
WI code TBD Rel-12 CR0193R- Cat
B Revision of S1-131029. Revision of S1-131084. Revision of S1-131143. Revision of S1-131270. |
|||
Cont |
LG Electronics, Inc., LG Uplus, KT, SKT |
Need for Prioritization of Voice Services under Operator-Defined Congestion Situations |
Noted |
Moved to from section 8.5.1 |
|||
Cont |
Research In Motion UK Ltd. |
Enhancement of SSAC to include requirements for ACDC |
Noted |
|
|||
CR |
Research In Motion UK Ltd |
22.011 v11.2.0: Enhancement of SSAC to include requirements for ACDC |
Noted |
WI code ACDC Rel-12 CR0196R- Cat C |
|||
LS OUT |
Research In Motion UK Ltd |
LS on ACDC |
Noted |
|
|||
Suppression
of mobile-originating signalling |
|||||||
WID |
NTT DOCOMO, et al |
WID proposal for Suppression of mobile-originating signalling and data traffic for UE in connected mode |
Revised to S1-131184 |
Comment: indicate in section 2.3 table that this is Stage 1 work |
|||
WID |
NTT DOCOMO, et al |
WID proposal for Suppression of mobile-originating signalling and data traffic for UE in connected mode |
Revised to S1-131280 |
Revision of S1-131030. |
|||
WID |
NTT DOCOMO, et al |
WID proposal for Suppression of mobile-originating signalling and data traffic for UE in connected mode |
Agreed |
Revision of S1-131030. Revision of S1-131184. No presentation |
|||
CR |
NTT DOCOMO, et al |
22.011 v11.2.0: Suppression of mobile-originating signalling and data traffic based on the criteria for ACB, SSAC, AC for CSFB, and ACDC |
Revised to S1-131185 |
WI code TBD Rel-12 CR 0194R- Cat B |
|||
CR |
NTT DOCOMO, et al |
22.011 v11.2.0: Suppression of mobile-originating signalling and data traffic based on the criteria for ACB, SSAC, AC for CSFB, and ACDC |
Revised to S1-131279 |
WI code TBD Rel-12 CR 0194R- Cat B Revision of S1-131031. |
|||
CR |
NTT DOCOMO, et al |
22.011 v11.2.0: Suppression of mobile-originating signalling and data traffic based on the criteria for ACB, SSAC, AC for CSFB, and ACDC |
Agreed |
WI code PMOC Rel-12 CR 0194R-
Cat B Revision of S1-131031. Revision of S1-131185. No presentation |
|||
Cont |
NTT DOCOMO |
Q&A exchanges for Rel-12 WI Application specific Congestion control for Data Communication applied to heavy congestion scenarios and for Rel-12 WI Suppression of mobile-originating signalling and data traffic for UE in connected mode. |
Noted |
Late document |
|||
SMS fraud while
roaming |
|||||||
Cont |
Orange |
SMS-Fraud in Roaming |
Revised to S1-131258 |
|
|||
Cont |
Orange |
SMS-Fraud in Roaming |
Noted |
Revision of S1-131080. |
|||
WID |
Orange |
Proposed new WID on SMS Fraud in Roaming |
Revised to S1-131186 |
Comment: indicate in section 2.3 table that this is Stage 1 work, table in section 2.2 – is content correct? |
|||
WID |
Orange |
Proposed new WID on SMS Fraud in Roaming |
Noted |
Revision of S1-131081. |
|||
CR |
ORANGE |
22.088 v11.0.0: Modification of the BOIC and BOICexHC barring for the SMS service |
Revised to S1-131187 |
Moved from section 7.9 WI code ?? Rel-12 CR0005R- Cat C |
|||
CR |
ORANGE |
22.088 v11.0.0: Modification of the BOIC and BOICexHC barring for the SMS service |
Noted |
Moved from section 7.9 WI code ?? Rel-12 CR0005R- Cat C Revision of S1-131082. |
|||
LS OUT |
Orange |
LS to CT4 on SMS Fraud in Roaming |
Noted |
|
|||
Cont |
Telecom Italia |
Discussion Paper Emergency Session Identification WID |
Moved to section 4 |
|
|||
WID |
Telecom Italia |
Proposed new WID on Emergency Call Identification |
Moved to section 4 |
|
|||
CR |
Telecom Italia, Huawei, Ericsson,Orange, Qulacomm |
22.101 v12.3.0: Requirement on emergency IM CN service |
Moved to section 4 |
WI code ESID Rel-12 CR0445R- Cat B |
|||
5.3
Proposals
for new work
(precursor to future Study and Work Items) |
|||||||
No contributions |
|||||||
CR |
Qualcomm Inc, Huawei |
22.011 v11.2.0: Overriding extended access barring |
Revised to S1-131212 |
WI code TEI11 Rel-11 CR0191R- Cat F |
|||
CR |
Qualcomm Inc, Huawei |
22.011 v11.2.0: Overriding extended access barring |
Revised to S1-131287 |
WI code TEI11 Rel-11 CR0191R- Cat F Revision of S1-131017. |
|||
CR |
Qualcomm Inc, Huawei |
22.011 v11.2.0: Overriding extended access barring |
Agreed |
WI code TEI11 Rel-11 CR0191R-
Cat F Revision of S1-131017. Revision of S1-131212. No presentation |
|||
CR |
Qualcomm Inc, Huawei |
22.011 v11.2.0: Overriding extended access barring |
Noted |
WI code TEI11 Rel-12 CR0192R- Cat A Comment: mirror not needed since there is no Rel-12 version of 22.011 |
|||
7 Rel-12 Contributions |
|||||||
7.1 MTCe-SIMSE: Interworking with M2M service enablement layer [SP-120436] |
|||||||
Cont |
KPN (Rapporteur) |
Implications of multiple service enablement frameworks |
Noted |
For joint session with SA2 (JM1) |
|||
Cont |
Telecom Italia |
Multiple service enablement frameworks |
Noted |
For joint session with SA2 (JM1) |
|||
CR |
Telecom Italia |
22.368 v12.0.0: Clarification of requirements for the support of multiple service enablement frameworks |
Revised to S1-131302 |
WI code MTCe-SIMSE Rel-12 CR0148R- Cat D To be reviewed after JM1 |
|||
CR |
Telecom Italia |
22.368 v12.0.0: Clarification of requirements for the support of multiple service enablement frameworks |
Agreed |
WI code MTCe-SIMSE Rel-12 CR0148R-
Cat D To be reviewed after JM1 Revision of S1-131079. No presentation |
|||
7.2 GCSE_LTE: Group communication system enablers for LTE [SP-120876] |
|||||||
7.2.1 GCSE_LTE Contributions |
|||||||
7.2.1.1
Contributions treated in ad hoc
|
|||||||
Cont |
S1-130147 |
Huawei Technologies. Co., Ltd., TD-Tech |
GCSE_LTE: Further discussion on functionality split between 3GPP and Application Layer |
Withdrawn |
To use to update the table to reflect agreement in SA1 (therefore it is not yet revised and not available), sent to SA1#61 via LS |
||
Cont |
U.S. Department of Commerce |
Annex C additional rows for 3GPP |
Noted |
Seen in ad hoc, sent to SA1#61 via LS |
|||
Cont |
Nokia Siemens Networks |
GCSE-LTE: Priority and Pre-emption requirements proposal |
Revised to S1-131149 |
Seen in ad hoc as S1-130187 Drafting session: Discussion of assigning priority and changing
priority during the communication Clarified that the operator shall be able to
configure the priority level with pre-emption capability Decided not to detail how to handle higher
priority levels vs lower priority levels – leaving that to the downstream
groups. Discussion on whether to say sth about queuing or not – contributions are invited |
|||
Cont |
Nokia Siemens Networks |
GCSE-LTE: Priority and Pre-emption requirements proposal |
Agreed |
Seen in ad hoc as S1-130187 Drafting session: Discussion of
assigning priority and changing priority during the communication Clarified that the
operator shall be able to configure the priority level with pre-emption
capability Decided not to detail
how to handle higher priority levels vs lower priority levels – leaving that
to the downstream groups. Discussion on whether to say sth about queuing or not – contributions are invited Revision of S1-131083. Agreed to be added to the TS (editor's note to be added by Rapporteur) |
|||
Cont |
Harris Corporation |
GCSE_LTE Relay – Possible new requirement for 5.2.2 |
Agreed |
Seen in ad hoc as S1-130136 Drafting session: Agreed in drafting session Agreed to be added to the TS |
|||
Cont |
Motorola Solutions UK Ltd |
GCSE-LTE: Speech Group Call use case and requirements proposal |
Noted |
Seen in ad hoc as S1-130192 Drafting session: Noted |
|||
Cont |
Alcatel-Lucent |
GCSE_LTE: Clarification on performance recommendations |
Revised to S1-131150 |
Seen in ad hoc as S1-130193 Drafting session: Decided to have a more general statement on the
performance not going into too much detail. Comments received that this lacks the exact
definition from where to where the time should be measured – contributions
invited. Added reference to TETRA specs Open
still how much of the delay is being attributed to the application |
|||
Cont |
Alcatel-Lucent |
GCSE_LTE: Clarification on performance recommendations |
Revised to S1-131151 |
Seen in ad
hoc as S1-130193 Drafting session: Decided to have a more
general statement on the performance not going into too much detail. Comments received that
this lacks the exact definition from where to where the time should be
measured – contributions invited. Added reference to
TETRA specs Open still how much of the delay is being attributed to the application Revision of S1-131155. |
|||
Cont |
Alcatel-Lucent |
GCSE_LTE: Clarification on performance recommendations |
Agreed |
Seen in ad
hoc as S1-130193 Drafting session: Decided to have a more
general statement on the performance not going into too much detail. Comments received that
this lacks the exact definition from where to where the time should be
measured – contributions invited. Added reference to
TETRA specs Open still how much of
the delay is being attributed to the application Revision of S1-131155. Revision of S1-131150. Agreed to be added to the TS No presentation |
|||
Cont |
Alcatel-Lucent, EADS, ETRI |
New requirement to establish a group communication within a specific area |
Revised to S1-131148 |
Result of discussion in ad hoc but sent to SA1#61 via LS Drafting session: The requirements were changed not refer to the application
anymore but just to require the functionality from the EPS – This allows also
other entities to make use of the requested function "Limited" geo area was changed to
"defined" geo area A requirement to
redefine the area during a Group Communication was added. |
|||
Cont |
Alcatel-Lucent, EADS, ETRI |
New requirement to establish a group communication within a specific area |
Agreed |
Result of discussion in ad hoc but
sent to SA1#61 via LS Drafting session: The requirements were
changed not refer to the application anymore but just to require the
functionality from the EPS – This allows also other entities to make use of
the requested function "Limited"
geo area was changed to "defined" geo area A requirement to redefine the area during a Group Communication was added. Revision of S1-130174. Agreed to be added to the TS |
|||
Cont |
General Dynamics Broadband UK |
Text proposal on ProSe relay dimensioning and relationship with GCSE_LTE |
A revision of S1-130081 seen in ad hoc |
||||
Cont |
General Dynamics Broadband UK |
Text proposal on ProSe relay dimensioning and relationship with GCSE_LTE |
Revised to S1-131313 |
A revision of S1-130081 seen in ad hoc Revision of S1-130199. GCSE_LTE part only |
|||
Cont |
General Dynamics Broadband UK |
Text proposal on ProSe relay dimensioning and relationship with GCSE_LTE |
Agreed |
A revision of S1-130081 seen in
ad hoc Revision of S1-130199. GCSE_LTE part only Revision of S1-131260. Agreed to be added to the TS No presentation |
|||
CR |
General Dynamics Broadband UK |
CR to 22.803 on ProSe relay dimensioning |
Agreed |
Revision of S1-130199 CR#0063 CPR.2yy |
|||
S1-130099 |
EADS |
GCSE-LTE / GCSE-ProSe Dual Watch use case and requirements proposal |
Withdrawn |
Seen in ad hoc, sent to SA1#61 via LS Not available |
|||
Cont |
EADS |
GCSE-LTE / GCSE-ProSe Tactical Operation use case and requirements proposal |
Moved to section 7.2.1.2 |
Not yet seen in ad hoc, sent to SA1#61 via LS |
|||
7.2.1.2 Contributions
not treated in ad hoc
|
|||||||
Cont |
EADS |
GCSE-LTE / GCSE-ProSe Tactical Operation use case and requirements proposal |
Revised to S1-131215 |
Sent to SA1#61 via LS Moved from section 7.2.1.1 |
|||
Cont |
EADS |
GCSE-LTE / GCSE-ProSe Tactical Operation use case and requirements proposal |
Noted |
Sent to
SA1#61 via LS Moved from section 7.2.1.1 Revision of S1-130119. |
|||
Cont |
China Unicom |
Enhancement to operational requirements in GCSE_LTE |
Noted |
Sent to SA1#61 via LS |
|||
Cont |
Home Office |
GCSE_LTE: Fallback from LTE to 3G and 2G |
Revised to S1-131249 |
Sent to SA1#61 via LS |
|||
Cont |
Home Office |
GCSE_LTE: Fallback from LTE to 3G and 2G |
Noted |
Sent to SA1#61 via LS Revision of S1-130031. |
|||
Cont |
Home Office |
GCSE_LTE: Support for TETRA codec |
Noted |
Sent to SA1#61 via LS |
|||
Cont |
Motorola Solutions |
Security requirements for GCSE |
Revised to S1-131216 |
Sent to SA1#61 via LS |
|||
Cont |
Motorola Solutions |
Security requirements for GCSE |
Agreed |
Sent to SA1#61 via LS Revision of S1-130082. Agreed to be added to the TS No presentation |
|||
Cont |
Alcatel-Lucent, ETRI |
GCSE_LTE: Clarification on radio resource efficiency |
Revised to S1-131221 |
Sent to SA1#61 via LS |
|||
Cont |
Alcatel-Lucent, ETRI |
GCSE_LTE: Clarification on radio resource efficiency |
Agreed |
Sent to SA1#61 via LS Revision of S1-130071. Agreed to be added to the TS No presentation |
|||
Cont |
Motorola Solutions |
Resource Management for GCSE |
Revised to S1-131222 |
Sent to SA1#61 via LS |
|||
Cont |
Motorola Solutions |
Resource Management for GCSE |
Noted |
Sent to SA1#61 via LS Revision of S1-130024. |
|||
Cont |
General Dynamics Broadband UK |
GCSE_LTE: Analysis of possible interactions between 3GPP and application layer entities |
Noted |
Sent to SA1#61 via LS Cover items relevant to S1-130076 and S1-130077 only |
|||
Cont |
General Dynamics Broadband UK |
GCSE_LTE: Proposed new "Service Continuity" requirements |
Noted |
Sent to SA1#61 via LS |
|||
Cont |
General Dynamics Broadband UK |
GCSE_LTE: Proposed new "User Perception of Group Communication" requirements |
Revised to S1-131225 |
Sent to SA1#61 via LS |
|||
Cont |
General Dynamics Broadband UK |
GCSE_LTE: Proposed new "User Perception of Group Communication" requirements |
Withdrawn |
Sent to SA1#61 via LS Revision of S1-130077. |
|||
Cont |
Motorola Solutions |
Dynamic control of the setup and hang timers for Group Call |
Noted |
Sent to SA1#61 via LS |
|||
Cont |
Qualcomm Inc |
Functional requirements for TS22.468 |
Noted |
Sent to SA1#61 via LS Cover location based services only |
|||
Cont |
Motorola Solutions UK Ltd |
GCSE-LTE: Network Preference use case and requirements proposal |
Noted |
Sent to SA1#61 via LS |
|||
Cont |
EADS |
GCSE-LTE: Public Safety Definitions for use cases proposal for 'Annex <B>' of 22.468 |
Noted |
Sent to SA1#61 via LS |
|||
7.2.2 GCSE_LTE Drafting Session Information |
|||||||
AGE |
Rapporteur |
GCSE_LTE
Drafting Agenda |
Noted |
|
|||
REP |
Rapporteur |
GCSE_LTE
Drafting Report |
Approved |
|
|||
Summary
of drafting session ·
"Limited" geo area was changed to
"defined" geo area ·
A requirement to redefine the area during a Group
Communication was added. ·
Discussion of assigning priority and changing
priority during the communication and adapting the requirement ·
Clarified that the operator shall be able to
configure the priority level with pre-emption capability ·
Decided not to detail how to handle higher
priority levels vs lower priority levels – leaving that to the downstream
groups. ·
Discussion on whether to say sth about queuing or
not – contributions are invited ·
Decided to have a more general statement on the
performance not going into too much detail. ·
Comments received that this lacks the exact
definition from where to where the time should be measured – contributions
invited. ·
Added reference to TETRA specs |
|||||||
TS |
Rapporteur |
TS
22.468 on GCSE_LTE (output from SA1#61) |
Agreed |
Agreed
as the basis of future contributions No
presentation |
|||
|
Rapporteur |
Exception
sheet for GCSE_LTE |
Revised
to S1-131306 |
|
|||
|
Rapporteur |
Exception
sheet for GCSE_LTE |
Agreed |
Revision
of S1-131298. No
presentation |
|||
|
Rapporteur |
Cover
page |
Noted |
|
|||
|
|
Tdoc
number for allocation in drafting session |
Drafting |
|
|||
|
|
Tdoc
number for allocation in drafting session |
Drafting |
|
|||
|
|
Tdoc
number for allocation in drafting session |
Drafting |
|
|||
7.3 WLAN_NS: WLAN network selection for 3GPP terminals [SP-120259] (SA1 secondary responsibility) |
|||||||
No contributions |
|||||||
7.4 MTCe-SRM: Service requirement maintenance [SP-120541] |
|||||||
WID |
KPN (Rapporteur) |
Update of MTCe-SRM WID after SA prioritization |
Agreed |
Moved from section 5.1 |
|||
CR |
KPN |
22.368 v12.1.0: Clarification and merge of Mobile Terminated Only and Infrequent Mobile Terminated |
Revised to S1-131207 |
WI code MTCe-SRM Rel-12 CR0146R- Cat C |
|||
CR |
KPN |
22.368 v12.1.0: Clarification and merge of Mobile Terminated Only and Infrequent Mobile Terminated |
Revised to S1-131289 |
WI code MTCe-SRM Rel-12 CR0146R- Cat C Revision of S1-131037. |
|||
CR |
KPN |
22.368 v12.1.0: Clarification and merge of Mobile Terminated Only and Infrequent Mobile Terminated |
Agreed |
WI code MTCe-SRM Rel-12
CR0146R- Cat C Revision of S1-131037. Revision of S1-131207. No presentation |
|||
CR |
KPN |
22.368 v12.1.0: Moving MTC Priority Alarm into a generic requirement |
Revised to S1-131208 |
WI code MTCe-SRM Rel-12 CR0147R- Cat C |
|||
CR |
KPN |
22.368 v12.1.0: Moving MTC Priority Alarm into a generic requirement |
Revised to S1-131290 |
WI code MTCe-SRM Rel-12 CR0147R- Cat C Revision of S1-131038. |
|||
CR |
KPN |
22.368 v12.1.0: Moving MTC Priority Alarm into a generic requirement |
Agreed |
WI code MTCe-SRM Rel-12
CR0147R- Cat C Revision of S1-131038. Revision of S1-131208. No presentation |
|||
7.5 UPCON: User plane congestion management [SP-120545] |
|||||||
Cont |
Telecom Italia |
UPCON Normative Requirement derived from Use Case 10 in TR22.805 |
Noted |
|
|||
CR |
Cisco, Allot Communications, NTT DoCoMo |
22.805 v12.1.0: Correction of UPCON use case 10 |
Revised to S1-131242 |
WI code UPCON Rel-12 CR0003R0 Cat F |
|||
CR |
Cisco, Allot Communications, NTT DoCoMo |
22.805 v12.1.0: Correction of UPCON use case 10 |
Noted |
WI code UPCON Rel-12 CR0003R0 Cat F Revision of S1-131188. |
|||
CR |
Intel |
22.101 v12.3.0: Addition of Note to TS22.101 UPCON General Requirement |
Revised to S1-131085 |
WI code UPCON Rel-12 CR0440R- Cat F Corrections needed: Cover page – remove "TS22.101" from title, use a more descriptive title, fill in "clauses affected" Proposed text must be introduced via revision marks, not just by changing the text colour |
|||
CR |
Intel |
22.101 v12.3.0: Addition of Note: Mechanism to Alleviate UPCON Without Affecting user Experience |
Revised to S1-13S1-131090 |
Revision of S1-131021. WI code UPCON Rel-12 CR0440R1 Cat F Corrections needed to cover page: Remove revision marks from cover page |
|||
CR |
Intel |
22.101 v12.3.0: Addition of Note: Mechanism to Alleviate UPCON Without Affecting user Experience |
Noted |
Revision of S1-131021. WI code UPCON Rel-12 CR0440R1
Cat F Revision of S1-131085. |
|||
CR |
NTT DOCOMO, KDDI |
22.101 v12.3.0: Clarification of RAN user plane congestion definition |
Agreed |
WI code UPCON Rel-12 CR0444R- Cat D |
|||
Qualcomm, et al. |
UPCON Normative Requirement derived from Use Case 1 in TR22.805 |
Moved to JM2 |
Review in SA1 first to see if decision can be made. If not, then will be sent to joint session with SA2 (JM2) This document is for the joint meeting in JM2 |
||||
CR |
Telecom Italia |
CR to 22.101 to introduce charging requirement related to Use Case 10 |
Withdrawn |
CR#0451 |
|||
CR |
Qualcomm, et al. |
22.101 v12.3.0: Removal of implied architecture decision from an UPCON normative requirement |
Withdrawn |
WI code UPCON Rel-12 CR0447R- Cat F Depends on discussion of S1-131071. Not for joint session with SA2 |
|||
7.6 ProSe: Proximity-based services [SP-120935] |
|||||||
CR |
Qualcomm |
22.278 v12.1.0: Add definitions and abbreviations |
Revised to S1-131202 |
WI code ProSe Rel-12 CR0122R- Cat B |
|||
CR |
Qualcomm |
22.278 v12.1.0: Add definitions and abbreviations |
Revised to S1-131229 |
WI code ProSe Rel-12 CR0122R- Cat B Revision of S1-131166. |
|||
CR |
Qualcomm |
22.278 v12.1.0: Add definitions and abbreviations |
Revised to S1-131231 |
WI code ProSe Rel-12 CR0122R-
Cat B Revision of S1-131166. Revision of S1-131202. |
|||
CR |
Qualcomm |
22.278 v12.1.0: Add definitions and abbreviations |
Revised to S1-131232 |
WI code ProSe Rel-12 CR0122R-
Cat B Revision of S1-131166. Revision of S1-131202. Revision of S1-131229. |
|||
CR |
Qualcomm |
22.278 v12.1.0: Add definitions and abbreviations |
Revised to S1-131319 |
WI code ProSe Rel-12 CR0122R-
Cat B Revision of S1-131166. Revision of
S1-131202. Revision of S1-131229. Revision of S1-131231. |
|||
CR |
Qualcomm |
22.278 v12.1.0: Add definitions and abbreviations |
Agreed |
WI code ProSe Rel-12 CR0122R-
Cat B Revision of S1-131166. Revision of
S1-131202. Revision of S1-131229. Revision of S1-131231. Revision of S1-131232. No presentation |
|||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of ProSe Common & In-coverage Requirements |
Revised to S1-131204 |
WI code ProSe Rel-12 CR0119R2 Cat B |
|||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of ProSe Common & In-coverage Requirements |
Revised to S1-131241 |
WI code ProSe Rel-12 CR0119R2 Cat B Revision of S1-131167. |
|||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of ProSe Common & In-coverage Requirements |
Noted |
Revision of S1-131204. For offline discussion: S1-131261: CPR.21 |
|||
Cont |
Telecom Italia |
Out of coverage vs in coverage requirements for non-Public safety UEs |
Withdrawn |
|
|||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of ProSe Security, Authorization & Privacy Requirements |
Revised to S1-131203 |
WI code ProSe Rel-12 CR0120R2 Cat B |
|||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of ProSe Security, Authorization & Privacy Requirements |
Revised to S1-131236 |
WI code ProSe Rel-12 CR0120R2 Cat B Revision of S1-131168. |
|||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of ProSe Security, Authorization & Privacy Requirements |
Revised to S1-131255 |
WI code ProSe Rel-12 CR0120R2
Cat B Revision of S1-131168. Revision of S1-131203. For offline discussion: S1-131245: PR.86 S1-131246: CPR.2yy/PR.xx S1-131248: CPR.48/PR.49 S1-131253: CPR.182/PR.89 |
|||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of ProSe Security, Authorization & Privacy Requirements |
Revised to S1-131264 |
WI code ProSe Rel-12 CR0120R2
Cat B Revision of S1-131168. Revision of S1-131203. For offline discussion: S1-131245: PR.86 S1-131246: CPR.2yy/PR.xx S1-131248: CPR.48/PR.49 S1-131253: CPR.182/PR.89 Revision of S1-131236. |
|||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of ProSe Security, Authorization & Privacy Requirements |
Revised to S1-131301 |
WI code ProSe Rel-12 CR0120R2
Cat B Revision of S1-131168. Revision of S1-131203. For offline discussion: S1-131245: PR.86 S1-131246: CPR.2yy/PR.xx S1-131248: CPR.48/PR.49 – still outstanding S1-131253: CPR.182/PR.89 Revision of S1-131236. Revision of S1-131255. Added agreed text in S1-131253 |
|||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of ProSe Security, Authorization & Privacy Requirements |
Revised to S1-131308 |
WI code ProSe Rel-12 CR0120R2
Cat B Revision of S1-131168. Revision of S1-131203. For offline discussion: S1-131245: PR.86 S1-131246: CPR.2yy/PR.xx S1-131248: CPR.48/PR.49 S1-131253: CPR.182/PR.89 Revision of S1-131236. Revision of S1-131255. Added agreed text in S1-131253 Revision of S1-131264. Added agreed text in S1-131300 |
|||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of ProSe Security, Authorization & Privacy Requirements |
Agreed |
WI code ProSe Rel-12 CR0120R2
Cat B Revision of S1-131168. Revision of S1-131203. For offline discussion: S1-131245: PR.86 S1-131246: CPR.2yy/PR.xx S1-131248: CPR.48/PR.49 S1-131253: CPR.182/PR.89 Revision of S1-131236. Revision of S1-131255. Added agreed text in S1-131253 Revision of S1-131264. Added agreed text in S1-131300 Revision of S1-131301. No presentation |
|||
Cont |
Telecom Italia |
Third-party application's preferences for ProSe |
Agreed |
CPR.182 |
|||
Cont |
Telecom Italia |
On the requirement for configuring a UE to use ProSe |
Agreed |
No presentation |
|||
Cont |
Intel |
Subscriber identity, UE identity and privacy in the case of ProSe-assisted WLAN |
Revised to S1-131257 |
PR.xx |
|||
Cont |
Intel |
Subscriber identity, UE identity and privacy in the case of ProSe-assisted WLAN |
Agreed |
Revision of S1-131246. To be incorporated in CR to normative TS for ProSe on security |
|||
Cont |
Telecom Italia |
Clarification to mechanism to authorise 3rd party applications |
Revised to S1-131300 |
CPR.48/PR.49 |
|||
Cont |
Telecom Italia |
Clarification to mechanism to authorise 3rd party applications |
Agreed |
CPR.48/PR.49 Revision of S1-131248. No presentation |
|||
Cont |
US Dept of Commerce |
ProSe definitions |
Noted |
Action items: Unofficial version of TR
22.803 – US Dept of Commerce will analyse requirements to identify which
requirements are 1-to-1, 1-to-many or 1-to-all. To distribute to SA1
reflector. Other companies to review this input and provide their own
analysis. Two options: -
Define
one-to-one ProSe Communication and broaden the current ProSe Communication
definition, or -
In each
requirement add group/broadcast If possible, agree which option before San Diego |
|||
CR |
Deutsche Telekom |
22.278 v12.1.0: General Requirements for Proximity Services |
Revised to S1-131299 |
WI code ProSe Rel-12 CR0123R- Cat B |
|||
CR |
Deutsche Telekom |
22.278 v12.1.0: General Requirements for Proximity Services |
Revised to S1-131307 |
WI code ProSe Rel-12 CR0123R- Cat B Revision of S1-131283. |
|||
CR |
Deutsche Telekom |
22.278 v12.1.0: General Requirements for Proximity Services |
Agreed |
WI code ProSe Rel-12 CR0123R- Cat B Revision of S1-131283. Revision of S1-131299. Take into account agreement in S1-131256 No presentation |
|||
CR |
Deutsche Telekom |
22.278 v12.1.0: Public Safety Specific Requirements for Proximity Services |
Revised to S1-131309 |
WI code ProSe Rel-12 CR0124R- Cat B. |
|||
CR |
Deutsche Telekom |
22.278 v12.1.0: Public Safety Specific Requirements for Proximity Services |
Agreed |
WI code ProSe Rel-12 CR0124R- Cat B. Revision of S1-131284. No presentation |
|||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of EPS WLAN Support for ProSe Communication |
Revised to S1-131297 |
WI code ProSe Rel-12 CR0121R- Cat B |
|||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of EPS WLAN Support for ProSe Communication |
Revised to S1-131310 |
WI code ProSe Rel-12 CR0121R- Cat B Revision of S1-131169. |
|||
CR |
Qualcomm |
22.278 v12.1.0: Incorporation of EPS WLAN Support for ProSe Communication |
Agreed |
WI code ProSe Rel-12 CR0121R-
Cat B Revision of S1-131169. Revision of S1-131297. No presentation |
|||
CR |
Qualcomm |
22.115 v11.6.0: Incorporation of ProSe Charging Requirements |
Revised to S1-131234 |
WI code ProSe Rel-12 CR0067R- Cat B |
|||
CR |
Qualcomm |
22.115 v11.6.0: Incorporation of ProSe Charging Requirements |
Revised to S1-131281 |
WI code ProSe Rel-12 CR0067R- Cat B Revision of S1-131170. |
|||
CR |
Qualcomm |
22.115 v11.6.0: Incorporation of ProSe Charging Requirements |
Revised to S1-131311 |
WI code ProSe Rel-12 CR0067R-
Cat B Revision of S1-131170. Revision of S1-131234. |
|||
CR |
Qualcomm |
22.115 v11.6.0: Incorporation of ProSe Charging Requirements |
Agreed |
WI code ProSe Rel-12 CR0067R-
Cat B Revision of S1-131170. Revision of S1-131234. Revision of S1-131281. No presentation |
|||
|
Qualcomm |
ProSe exception sheet |
Revised to S1-131312 |
|
|||
|
Qualcomm |
ProSe exception sheet |
Agreed |
Revision of S1-131305. No presentation |
|||
7.7 IMS_WebRTC: Web Real Time Communication access to IMS [SP-120892] |
|||||||
|
China Mobile |
IMS_WebRTC exception sheet |
Revised to S1-131320 |
|
|||
|
China Mobile |
IMS_WebRTC exception sheet |
Agreed |
Revision of S1-131315. No presentation |
|||
WID |
Alcatel-Lucent |
IMS_WebRTC WID update |
Noted |
|
|||
Cont |
Ericsson |
Short IMS_WebRTC tutorial |
Noted |
|
|||
CR |
Alcatel-Lucent, Huawei, Orange, AT&T, Intel |
22.228 v12.4.0: IMS_WebRTC: Interoperability use cases |
Revised to S1-131176 |
WI code IMS_WebRTC Rel-12 CR0187R- Cat B Corrections needed on cover page: Use a more descriptive title, remove "IMS_WebRTC" from title |
|||
CR |
Alcatel-Lucent, Huawei, Orange, AT&T, Intel |
22.228 v12.4.0: IMS_WebRTC: Interoperability use cases |
Revised to S1-131199 |
WI code IMS_WebRTC Rel-12
CR0187R- Cat B Revision of S1-131076. Revision of S1-131076. Revision of S1-131176 and S1-131175. CR#0189 |
|||
CR |
Alcatel-Lucent, Huawei, Orange, AT&T, Intel, Telecom Italia, Ericsson, Verizon, China Mobile, NTT, T-Mobile |
22.228 v12.4.0: IMS Interoperability with WebRTC use cases and requirements |
Revised to S1-131282 |
Revision of S1-131076. Revision of S1-131076. Revision of S1-131176 and S1-131175. WI code IMS_WebRTC Rel-12 CR0189R- Cat B |
|||
CR |
Alcatel-Lucent, Huawei, Orange, AT&T, Intel |
22.228 v12.4.0: IMS_WebRTC: Interoperability use cases |
Revised to S1-131314 |
Revision of S1-131076. Revision of S1-131076. Revision of S1-131176 and S1-131175. WI code IMS_WebRTC Rel-12
CR0189R- Cat B Revision of S1-131199. |
|||
CR |
Alcatel-Lucent, Huawei, Orange, AT&T, Intel |
22.228 v12.4.0: IMS_WebRTC: Interoperability use cases |
Noted |
Revision of S1-131076. Revision of S1-131076. Revision of S1-131176 and S1-131175. WI code IMS_WebRTC Rel-12
CR0189R- Cat B Revision of S1-131199. Revision of S1-131282. |
|||
CR |
Alcatel-Lucent, Huawei, Orange, AT&T, Intel |
22.228 v12.4.0: IMS_WebRTC: Interoperability use cases |
Withdrawn |
|
|||
CR |
Alcatel-Lucent, Huawei, Orange, AT&T, Intel |
22.228 v12.4.0: IMS_WebRTC: Interoperability use cases |
Withdrawn |
|
|||
CR |
Alcatel-Lucent, Huawei, Orange, AT&T, Intel |
22.228 v12.4.0: IMS_WebRTC: Interoperability use cases |
Withdrawn |
|
|||
CR |
Alcatel-Lucent, Huawei, Orange, AT&T, Intel |
22.228 v12.4.0: IMS_WebRTC: Interoperability use cases |
Withdrawn |
|
|||
CR |
Alcatel-Lucent, Huawei, Orange, AT&T, Intel |
22.228 v12.4.0: IMS_WebRTC: Interoperability use cases |
Withdrawn |
|
|||
CR |
Alcatel-Lucent, Huawei, AT&T, Intel |
22.228 v12.4.0: IMS_WebRTC: 22.228 requirements |
Revised to S1-131175 |
WI code IMS_WebRTC Rel-12 CR0186R- Cat B Corrections needed on cover page: Use a more descriptive title, remove "IMS_WebRTC" and "22.228" from title |
|||
CR |
Alcatel-Lucent, Huawei, AT&T, Intel |
22.228 v12.4.0: IMS_WebRTC: 22.228 requirements |
Revised to S1-131199 |
WI code IMS_WebRTC Rel-12
CR0186R- Cat B Revision of S1-131075. |
|||
CR |
Alcatel-Lucent, Huawei, AT&T, Intel |
22.101 v12.3.0: IMS_WebRTC: 22.101 requirements |
Revised to S1-131177 |
WI code IMS_WebRTC Rel-12 CR0448R- Cat B Corrections needed on cover page: Use a more descriptive title, remove "IMS_WebRTC" and 22.101 from title |
|||
CR |
Alcatel-Lucent, Huawei, AT&T, Intel |
22.101 v12.3.0: IMS_WebRTC: 22.101 requirements |
Noted |
WI code IMS_WebRTC Rel-12
CR0448R- Cat B Revision of S1-131077. |
|||
CR |
Intel |
22.228 v12.4.0: IMS_WebRTC: additional use case |
Revised to S1-131195 |
WI code IMS_WebRTC Rel-12 CR184R- Cat B Corrections needed to cover page: CR number is 0184 (4 digits) Use a more descriptive title, remove "IMS_WebRTC" from title |
|||
CR |
Intel |
22.228 v12.4.0: IMS_WebRTC: additional use case |
Noted |
WI code IMS_WebRTC Rel-12
CR184R- Cat B Revision of S1-131039. |
|||
CR |
Intel |
22.228 v12.4.0: IMS_WebRTC: 22.228 requirements for the additional use case |
Revised to S1-131196 |
WI code IMS_WebRTC Rel-12 CR185R- Cat B Corrections needed on cover page: CR number is 0185 (4 digits) Use a more descriptive title, remove "IMS_WebRTC" and "22.228" from title "Clauses affected" is wrong For new proposed clause, need to suggest which clause it falls under |
|||
CR |
Intel |
22.228 v12.4.0: IMS_WebRTC: 22.228 requirements for the additional use case |
Noted |
WI code IMS_WebRTC Rel-12
CR185R- Cat B Revision of S1-131040. |
|||
Cont |
China Unicom |
Discussion on two use cases about WebRTC client communicating with IMS terminals of different operators |
Revised to S1-131086 |
Comment use case: Use case requires: Description, Pre-conditions, Service Flows, Post-conditions and Potential Requirements |
|||
Cont |
China Unicom |
Discussion on two use cases about WebRTC client communicating with IMS terminals of different operators |
Noted |
Revision of S1-131014. |
|||
CR |
China unicom |
22.228 v12.4.0: Add scenarioes for Web Real Time Communication (WebRTC) Access to IMS in annex A |
Revised to S1-131087 |
WI code IMS_WebRTC Rel-12 CR0182R1 Cat B Corrections needed to cover page: CR rev number is wrong (should be "-" not "1") "Other specs affected" – change "N" to "X" Comment on use case: Use case requires: Description, Pre-conditions, Service Flows, Post-conditions and Potential Requirements |
|||
CR |
China unicom |
22.228 v12.4.0: Add scenarioes for Web Real Time Communication (WebRTC) Access to IMS in annex A |
Noted |
WI code IMS_WebRTC Rel-12
CR0182R1 Cat B Revision of S1-131016. |
|||
CR |
China unicom |
22.228 v12.4.0: Adding regulatory requirement for Web Real Time Communication (WebRTC) Access to IMS |
Noted |
WI code IMS_WebRTC Rel-12 CR0181R1 Cat B Corrections needed to cover page: CR rev number is wrong (should be "-" not "1") Remove revision marks from cover page "Other specs affected" – change "N" to "X" |
|||
CR |
Ericsson, ST-Ericsson |
22.228 v12.4.0: Support for RTCWeb client access to IMS using Websocket transport |
Noted |
WI code IMS_WebRTC Rel-12 CRCRNumR- Cat B Corrections needed to cover page: CR number is 0183 |
|||
7.8 LangInfo: Language and modality information for communications [SP-120937] |
|||||||
WID |
Orange |
Language and Modality Information for communications |
Agreed |
|
|||
CR |
Orange, France Telecom, Huawei, Qualcomm, Sprint |
22.228 v12.4.0: Language and Modality Information for communications |
Revised to S1-131088 |
WI code LangInfo Rel-12 CR0404R3 Cat B Corrections needed on cover page: CR number is wrong (was for previous CR to 22.101), new CR number is 0188 |
|||
CR |
Orange, France Telecom, Huawei, Qualcomm, Sprint |
22.228 v12.4.0: Language and Modality Information for communications |
Revised to S1-131213 |
WI code
LangInfo Rel-12 CR0404R3 Cat B Revision of S1-131011. WI code LangInfo Rel-12 CR0188R- Cat B |
|||
CR |
Orange, France Telecom, Huawei, Qualcomm, Sprint |
22.228 v12.4.0: Language and Modality Information for communications |
Agreed |
WI code LangInfo
Rel-12 CR0404R3 Cat B Revision of S1-131011. WI code LangInfo Rel-12 CR0188R- Cat B Revision of S1-131088. |
|||
Cont |
Motorola Mobility UK Ltd, Panasonic |
Methods to Access In Case of Emergency Information |
Moved to section 7.10 |
|
|||
CR |
ORANGE |
22.088 v11.0.0: Modification of the BOIC and BOICexHC barring for the SMS service |
Moved to section 5.2 |
WI code ?? Rel-12 CR0005R- Cat C |
|||
Cont |
Research In Motion UK Ltd |
Discussion on ICE access procedure touch gesture mechanism |
Noted |
|
|||
Cont |
Motorola Mobility UK Ltd, Panasonic |
Methods to Access In Case of Emergency Information |
Revised to S1-131206 |
Moved from section 7.9 |
|||
Cont |
Motorola Mobility UK Ltd, Panasonic, Samsung, Intel, LG Electronics Inc. |
Methods to Access In Case of Emergency Information |
Noted |
Moved from section 7.9 Revision of S1-131050. |
|||
CR |
Research In Motion UK Ltd, Vodafone, Sony Mobile |
22.030 v12.0.0: Enhancements to the MMI of the ICE access procedures |
Revised to S1-131113 |
WI code TEI12 Rel-12 CR0016R4 Cat C |
|||
CR |
Research In Motion UK Ltd, Vodafone, Sony Mobile |
22.030 v12.0.0: Enhancements to the MMI of the ICE access procedures |
Noted |
WI code TEI12 Rel-12 CR0016R4 Cat C Revision of S1-131042. |
|||
CR |
Research In Motion UK Ltd |
22.030 v12.0.0: Displaying of PIN and PIN2 entry to the user |
Withdrawn |
WI code TEI12 Rel-12 CR0018R- Cat C |
|||
8.1
FS_MTCe:
Enhancements for Machine-Type Communications [SP-100448] |
|||||||
Cont |
ETRI, ITRI |
Proposed addressing requirements of MTC Gateway Device |
Noted |
|
|||
Cont |
ITRI, Panasonic, ETRI |
Potential Requirement for use cases in TR 22.888 Section 4.1 |
Revised to S1-131201 |
Corrections needed: Use a more descriptive title |
|||
Cont |
ITRI, Panasonic, ETRI |
Potential Requirement for use cases in TR 22.888 Section 4.1 |
Noted |
Corrections needed: Use a more descriptive title Revision of S1-131065. |
|||
Cont |
Huawei |
FS_MTCe proposal for a conclusion |
Revised to S1-131209 |
|
|||
Cont |
Huawei |
FS_MTCe proposal for a conclusion |
Agreed |
Revision of S1-131070. Agreed to be added to the TR No presentation |
|||
TR |
Huawei |
TR 22.888 update |
Revised to S1-131277 |
|
|||
TR |
Huawei |
TR 22.888 update |
Agreed |
Revision of S1-131243. Agreed to be sent to SA plenary for information and approval No presentation |
|||
CP |
Huawei |
Cover page |
Agreed |
|
|||
Huawei |
TR 22.888 update |
Withdrawn |
|
||||
8.2.1 CRs agreed in ad hoc |
|||||||
CR |
Intel |
22.803 v12.0.0: Editorial Updates to Requirements |
Agreed |
WI code FS_ProSe Rel-12 CR0046R2 Cat D Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
Qualcomm |
22.803 v12.0.0: Potential requirements consolidation – editorial changes |
Agreed |
WI code FS_ProSe Rel-12 CR0007R2 Cat D Cover page corrections: CR# rev is "1" Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
Telecom Italia, Deutsche Telecom |
TR 22.803 v12.0.0: Definition of “range class” |
Agreed |
WI code ProSE Rel-12 CR0048R2 Cat F Cover page corrections: CR# rev is "1" WI code: FS_ProSe Remove "TR" from spec number Other specs affected: check all three "N" boxes Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
Motorola Solutions |
22.803 v12.0.0: Range class setting by the discoveree |
Agreed |
WI code FS_ProSE Rel-12 CR0012R2 Cat C Cover page corrections: WI code: FS_ProSe Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
Huawei, Hisilicon |
22.803 v12.0.0: Public Safety end-user visibility of path switch |
Revised to S1-131256 |
WI code FS_ProSe Rel-12 CR0040R2 Cat F Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
Huawei, Hisilicon |
22.803 v12.0.0: Public Safety end-user visibility of path switch |
Agreed |
WI code FS_ProSe Rel-12
CR0040R2 Cat F Agreed in ad hoc, sent to SA1#61 via LS Revision of S1-130155. |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: On the use of the term ‘Public Safety Spectrum Dedicated to ProSe’ in the use cases in sections 5.2.5 and 5.2.6 |
Agreed |
WI code FS_ProSe Rel-12 CR0052R1 Cat F Takes into account changes proposed in S1-130017 Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: On missing statements pertaining to Network coverage (or otherwise) of UEs in the Public Safety use cases |
Agreed |
WI code FS_ProSe Rel-12 CR0053R- Cat F Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
US Department of Commerce |
22.803 v12.0.0: Additional clarifying text for public safety potential requirements |
Agreed |
WI code FS_ProSe Rel-12 CR0054R2 Cat F Takes into account changes proposed in S1-130017 Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
Huawei, Hisilicon |
22.803 v12.0.0: Clarify what “configured” stands for |
Agreed |
WI code FS_ProSe Rel-12 CR0041R1 Cat D Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: UE with Multiple One-to-One Direct User Traffic Sessions in Public Safety Spectrum Dedicated to ProSe - use case potential requirement clarification |
Agreed |
WI code FS_ProSe Rel-12 CR0051R- Cat F Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
Huawei, Hisilicon |
22.803 v12.0.0: The ProSe Communication path is a E-UTRAN path |
Agreed |
WI code FS_ProSe Rel-12 CR0050R2 Cat F Cover page corrections: CR# rev is "-" Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: ProSe Group - use case has orphaned text in the potential requirements section |
Agreed |
WI code FS_ProSe Rel-12 CR0049R- Cat D Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: Remaining details of the Co-existence of ProSe Communication and E-UTRAN communication Public Safety use case |
Agreed |
WI code FS_ProSe Rel-12 CR0055R- Cat F Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
Huawei, Hisilicon, China Mobile |
22.803 v12.0.0: Rewording of “direct link” into proSe Communication |
Revised to S1-131190 |
WI code FS_ProSe Rel-12 CR0044R2 Cat F Comment: should the change be "direct WLAN" instead of "WiFi Direct"? Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
Huawei, Hisilicon, China Mobile |
22.803 v12.0.0: Rewording of “direct link” into proSe Communication |
Revised to S1-131193 |
WI code FS_ProSe Rel-12
CR0044R2 Cat F Agreed in ad hoc, sent to SA1#61 via LS Revision of S1-130166. |
|||
CR |
Huawei, Hisilicon, China Mobile |
22.803 v12.0.0: Rewording of “direct link” into proSe Communication |
Agreed |
WI code FS_ProSe Rel-12
CR0044R2 Cat F Agreed in ad hoc, sent to
SA1#61 via LS Revision of S1-130166. Revision of S1-131190. No presentation |
|||
CR |
China Mobile, ITRI |
22.803 v12.0.0: New WLAN Requirement: Accounting Data Collection |
Agreed |
WI code FS_ProSe Rel-12 CR0031R1 Cat C Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
ETRI, ITRI, Institute for Information Industry (III) |
22.803 v12.0.0: Correction to Control paths for ProSe Communication |
Agreed |
WI code FS_ProSe Rel-12 CR0036R1 Cat F Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: Clarification in discussion of control paths for ProSe Communications in section 4.2 |
Agreed |
WI code FS_ProSe Rel-12 CR0016R1 Cat F Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
Vodafone, Renesas Mobile Europe Ltd |
22.803 v12.0.0: Clarify "network coverage" means "E-UTRAN coverage" |
Agreed |
WI code FS_ProSe Rel-12 CR0005R1 Cat F Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: Service Continuity between Infrastructure and E-UTRA ProSe Communication paths - use case is missing a description section |
Agreed |
WI code FS_ProSe Rel-12 CR0018R1 Cat F Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
Huawei, Hisilicon, China Mobile |
22.803 v12.0.0: Merge similar Potential requirement |
Agreed |
WI code FS_ProSe Rel-12 CR0039R2 Cat D Agreed in ad hoc, sent to SA1#61 via LS |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: FS_ProSe: Operator A uses ProSe to Enhance Location and Presence Services - use case description in 5.1.7.1 is incorrectly phrased |
Agreed |
WI code FS_ProSe Rel-12 CR0019R- Cat F Agreed in ad hoc, sent to SA1#61 via LS |
|||
8.2.2 CRs treated in ad hoc (not yet agreed) |
|||||||
CR |
Qualcomm |
22.803 v12.0.0: Potential requirements consolidation with some clarification |
Revised to S1-131191 |
WI code FS_ProSe Rel-12 CR0008R- Cat F Revised in ad hoc but sent to SA1#61 via LS |
|||
CR |
Qualcomm |
22.803 v12.0.0: Potential requirements consolidation with some clarification |
Revised to S1-131198 |
WI code FS_ProSe Rel-12
CR0008R- Cat F Revised in ad hoc but sent to SA1#61 via LS Revision of S1-130130. |
|||
CR |
Qualcomm |
22.803 v12.0.0: Potential requirements consolidation with some clarification |
Revised to S1-131244 |
WI code FS_ProSe Rel-12
CR0008R- Cat F Revised in ad hoc but sent to
SA1#61 via LS Revision of S1-130130. Revision of S1-131191. |
|||
CR |
Qualcomm |
22.803 v12.0.0: Potential requirements consolidation with some clarification |
Revised to S1-131254 |
WI code FS_ProSe Rel-12
CR0008R- Cat F Revised in ad hoc but sent to
SA1#61 via LS Revision of S1-130130. Revision of S1-131191. Revision of S1-131198. |
|||
CR |
Qualcomm |
22.803 v12.0.0: Potential requirements consolidation with some clarification |
Revised to S1-131263 |
WI code FS_ProSe Rel-12
CR0008R- Cat F Revised in ad hoc but sent to
SA1#61 via LS Revision of S1-130130. Revision of S1-131191. Revision of S1-131198. Revision of S1-131244. |
|||
CR |
Qualcomm |
22.803 v12.0.0: Potential requirements consolidation with some clarification |
Revised to S1-131265 |
WI code FS_ProSe Rel-12
CR0008R- Cat F Revised in ad hoc but sent to
SA1#61 via LS Revision of S1-130130. Revision of S1-131191. Revision of S1-131198. Revision of S1-131244. Revision of S1-131254. |
|||
CR |
Qualcomm |
22.803 v12.0.0: Potential requirements consolidation with some clarification |
Agreed |
WI code FS_ProSe Rel-12
CR0008R- Cat F Revised in ad hoc but sent to
SA1#61 via LS Revision of S1-130130. Revision of S1-131191. Revision of S1-131198. Revision of S1-131244. Revision of S1-131254. Revision of S1-131263. Added the change agreed in S1-131253 No presentation |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: Definitions for ProSe relay types |
Agreed |
WI code FS_ProSe Rel-12 CR0061R- Cat F Revised in ad hoc but sent to SA1#61 via LS |
|||
CR |
Interdigital, Qualcomm, Alcatel-Lucent, Intel, Telecom Italia |
22.803 v12.0.0: FS_ProSe additional clarifying text for security related requirements |
Revised to S1-131194 |
WI code FS_ProSe Rel-12 CR0003R2 Cat F Revised in ad hoc but sent to SA1#61 via LS |
|||
CR |
Interdigital, Qualcomm, Alcatel-Lucent, Intel, Telecom Italia |
22.803 v12.0.0: FS_ProSe additional clarifying text for security related requirements |
Revised to S1-131245 |
WI code FS_ProSe Rel-12
CR0003R2 Cat F Revised in ad hoc but sent to SA1#61 via LS Revision of S1-130165. |
|||
CR |
Interdigital, Qualcomm, Alcatel-Lucent, Intel, Telecom Italia |
22.803 v12.0.0: FS_ProSe additional clarifying text for security related requirements |
Revised to S1-131247 |
WI code FS_ProSe Rel-12
CR0003R2 Cat F Revised in ad hoc but sent to
SA1#61 via LS Revision of S1-130165. Revision of S1-131194. |
|||
CR |
Interdigital, Qualcomm, Alcatel-Lucent, Intel, Telecom Italia |
22.803 v12.0.0: FS_ProSe additional clarifying text for security related requirements |
Revised to S1-131288 |
WI code FS_ProSe Rel-12
CR0003R2 Cat F Revised in ad hoc but sent to
SA1#61 via LS Revision of S1-130165. Revision of S1-131194. Revision of S1-131245. |
|||
CR |
Interdigital, Qualcomm, Alcatel-Lucent, Intel, Telecom Italia |
22.803 v12.0.0: FS_ProSe additional clarifying text for security related requirements |
Agreed |
WI code FS_ProSe Rel-12
CR0003R2 Cat F Revised in ad hoc but sent to
SA1#61 via LS Revision of S1-130165. Revision of S1-131194. Revision of S1-131245. Revision of S1-131247. No presentation |
|||
CR |
Renesas Mobile Europe Ltd |
22.803 v12.0.0: Addition of definitions for Discoverer and Discoveree |
Withdrawn |
WI code FS_ProSe Rel-12 CR0062R- Cat F |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: General corrections to sections 1, 2, and 4 |
Revised to S1-131217 |
WI code FS_ProSe Rel-12 CR0057R- Cat F Revised in ad hoc but sent to SA1#61 via LS |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: General corrections to sections 1, 2, and 4 |
Revised to S1-131272 |
WI code FS_ProSe Rel-12
CR0057R- Cat F Revised in ad hoc but sent to SA1#61 via LS Revision of S1-130167. |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: General corrections to sections 1, 2, and 4 |
Agreed |
WI code FS_ProSe Rel-12
CR0057R- Cat F Revised in ad hoc but sent to
SA1#61 via LS Revision of S1-130167. Revision of S1-131217. No presentation |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: General corrections to section 5.1 |
Revised to S1-131218 |
WI code FS_ProSe Rel-12 CR0058R- Cat F Revised in ad hoc but sent to SA1#61 via LS |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: General corrections to section 5.1 |
Revised to S1-131273 |
WI code FS_ProSe Rel-12
CR0058R- Cat F Revised in ad hoc but sent to SA1#61 via LS Revision of S1-130168. |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: General corrections to section 5.1 |
Agreed |
WI code FS_ProSe Rel-12
CR0058R- Cat F Revised in ad hoc but sent to
SA1#61 via LS Revision of S1-130168. Revision of S1-131218. No presentation |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: General corrections to section 5.2 |
Revised to S1-131219 |
WI code FS_ProSe Rel-12 CR0059R- Cat F Revised in ad hoc but sent to SA1#61 via LS |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: General corrections to section 5.2 |
Agreed |
WI code FS_ProSe Rel-12
CR0059R- Cat F Revised in ad hoc but sent to SA1#61 via LS Revision of S1-130169. |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: General corrections to section 6 |
Revised to S1-131220 |
WI code FS_ProSe Rel-12 CR0060R- Cat F Revised in ad hoc but sent to SA1#61 via LS |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: General corrections to section 6 |
Revised to S1-131274 |
WI code FS_ProSe Rel-12
CR0060R- Cat F Revised in ad hoc but sent to SA1#61 via LS Revision of S1-130170. |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: General corrections to section 6 |
Revised to S1-131286 |
WI code FS_ProSe Rel-12
CR0060R- Cat F Revised in ad hoc but sent to SA1#61
via LS Revision of S1-130170. Revision of S1-131220. No presentation |
|||
CR |
General Dynamics Broadband UK |
22.803 v12.0.0: General corrections to section 6 |
Agreed |
WI code FS_ProSe Rel-12
CR0060R- Cat F Revised in ad hoc but sent to SA1#61
via LS Revision of S1-130170. Revision of S1-131220. No presentation Revision of S1-131274. No presentation |
|||
CR |
Motorola Solutions |
TR 22.803 v12.0.0: “Stabilty of link” requirement for ProSE |
Revised to S1-131275 |
WI code ProSE Rel-12 CR0009R- Cat F Corrections needed to CR cover page: WI code: FS_ProSe Remove "TR" from spec number Other specs affected: check all three "N" boxes Reviewed and should have been revised in ad hoc, sent to SA1#61 via LS |
|||
CR |
Motorola Solutions |
TR 22.803 v12.0.0: “Stabilty of link” requirement for ProSE |
Agreed |
WI code ProSE Rel-12 CR0009R- Cat F Reviewed and should have been revised in ad hoc, sent to SA1#61 via LS Revision of S1-130019. Corrections needed to CR cover page: WI code: FS_ProSe Reason of change needs to be updated No presentation |
|||
CR |
Motorola Solutions |
22.803 v12.0.0: Remove requirement that the id of the 3rd party applications developer needs to be stored |
Agreed |
WI code FS_ProSE Rel-12 CR0010R1 Cat F Corrections needed to CR cover page: WI code: FS_ProSe Revised in ad hoc but sent to SA1#61 via LS |
|||
CR |
Huawei, Hisilicon |
22.803 v12.0.0: Clarification that ProSe capability features are Prose Discovery and ProSe Communication |
Revised to S1-131262 |
WI code FS_ProSe Rel-12 CR0037R2 Cat F Revised in ad hoc in S1-130183 but not yet seen/uploaded, sent to SA1#61 via LS Not available |
|||
CR |
Huawei, Hisilicon |
22.803 v12.0.0: Clarification that ProSe capability features are Prose Discovery and ProSe Communication |
Agreed |
WI code
FS_ProSe Rel-12 CR0037R2 Cat F Revised in ad hoc in S1-130183
but not yet seen/uploaded, sent to SA1#61 via LS Not available Revision of S1-131159. No presentation |
|||
CR |
Intel |
22.803 v12.0.0: Charging Requirement for Service Continuity for ProSe-assisted WiFi Direct |
Revised to S1-131233 |
WI code FS_ProSe Rel-12 CR0047R1 Cat B Revised in ad hoc but sent to SA1#61 via LS |
|||
CR |
Intel |
22.803 v12.0.0: Charging Requirement for Service Continuity for ProSe-assisted WiFi Direct |
Revised to S1-131276 |
WI code FS_ProSe Rel-12
CR0047R1 Cat B Revised in ad hoc but sent to SA1#61 via LS Revision of S1-130185. |
|||
CR |
Intel |
22.803 v12.0.0: Charging Requirement for Service Continuity for ProSe-assisted WiFi Direct |
Agreed |
WI code FS_ProSe Rel-12
CR0047R1 Cat B Revised in ad hoc but sent to
SA1#61 via LS Revision of S1-130185. Revision of S1-131233. No presentation |
|||
8.2.3 Documents not treated in ad hoc |
|||||||
Cont |
Intel |
FS_ProSe Discussion on Revised Section Headings and Re-categorization of Requirements |
Noted |
Sent to SA1#61 via LS |
|||
CR |
Telecom Italia |
22.803 v12.0.0: Requirements clarification, and to ensure ProSe does not impact existing infrastructure services |
Noted |
WI code FS_ProSe Rel-12 CR0030R1 Cat B Sent to SA1#61 via LS |
|||
CR |
Intel |
22.803 v12.0.0: FS_ProSe potential security requirements consolidation |
Noted |
WI code FS_ProSe Rel-12 CR004R- Cat D Corrections needed to CR cover page: CR number: 0004 (must be 4 digits) Proposed changes taken into account in S1-130198 and S1-130195 Sent to SA1#61 via LS |
|||
CR |
Qualcomm, et al. |
22.805 v12.1.0: Removal of implied architecture decision from an FS_UPCON consolidated requirement |
Withdrawn |
WI code FS_UPCON Rel-12 CR0002R- Cat F Corrections needed on cover page: Remove "FS_UPCON" from title |
|||
Cont |
Sprint |
PWS in the shared RAN use case revisited |
Revised to S1-131200 |
|
|||
Cont |
Sprint |
PWS in the shared RAN use case revisited |
Revised to S1-131135 |
Revision of S1-131051. Drafting session: It was clarified that duplicate PWS messages are
exactly the same, arriving at the shared RAN arriving from different
Participating Operators. Actions: 1. “duplicate”
PWS messages should indicate the same PWS message from different
Participating Operators 2. First requirement
should state “connect multiple CBC” Correct verbs (“shall”..) need to be used for requirements |
|||
Cont |
Sprint |
PWS in the shared RAN use case revisited |
Revised to S1-131137 |
Revision of S1-131051. Drafting session: It was clarified that duplicate
PWS messages are exactly the same, arriving at the shared RAN arriving from
different Participating Operators. Actions: 1.
“duplicate”
PWS messages should indicate the same PWS message from different
Participating Operators 2.
First requirement
should state “connect multiple CBC” Correct verbs (“shall”..) need to be used for
requirements Revision of S1-131200. |
|||
Cont |
Sprint |
PWS in the shared RAN use case revisited |
Agreed |
Revision of S1-131051. Drafting session: It was clarified that
duplicate PWS messages are exactly the same, arriving at the shared RAN
arriving from different Participating Operators. Actions: 3.
“duplicate”
PWS messages should indicate the same PWS message from different
Participating Operators 4.
First requirement
should state “connect multiple CBC” Correct verbs (“shall”..) need to be used for
requirements Revision of S1-131200. Revision of S1-131135. Agreed to be added to the TR No presentation |
|||
Cont |
Sprint |
Proposal for removing use case 5 |
Agreed |
Drafting session: Removal of the use case had been agreed to by the author (Clearwire) Agreed in drafting session |
|||
Cont |
Sprint |
Cleanup of roaming explanation and editor’s note in clause 4.1.1.5 |
Agreed |
Agreed in drafting session |
|||
Cont |
Sprint |
Cleanup of editor’s note regarding RAN sharing granularity |
Revised to S1-131133 |
Drafting session: Action: Add “from
operator B” to end of Req. 2 and
“as a roamer”
to end of Req. 3 |
|||
Cont |
Sprint |
Cleanup of editor’s note regarding RAN sharing granularity |
Agreed |
Drafting session: Action: Add “from operator B” to end of Req. 2 and “as a roamer” to end of Req. 3 Revision of S1-131059. Agreed in drafting session |
|||
Cont |
Sprint |
Include Participating Operator weighting in asymmetric resource allocation |
Revised to S1-131134 |
Drafting session: Action: Change “Particpating Operator weighting factor” into “Preagreed
Portion” |
|||
Cont |
Sprint |
Include Participating Operator weighting in asymmetric resource allocation |
Revised to S1-131136 |
Drafting session: Action: Change “Particpating Operator
weighting factor” into “Preagreed Portion” Revision of S1-131061. |
|||
Cont |
Sprint |
Include Participating Operator weighting in asymmetric resource allocation |
Agreed |
Drafting session: Action: Change “Particpating Operator
weighting factor” into “Preagreed Portion” Revision of S1-131061. Revision of S1-131134. Agreed to be added to the TR |
|||
Cont |
Sprint |
Consistency cleanup and clarification in UC 8 & 9 (charging & billing) |
Agreed |
Agreed in drafting session |
|||
Cont |
Sprint |
HeNB in the Shared RAN use case |
Withdrawn |
Not available Late document |
|||
Cont |
Sprint |
Cleanup of OAM access to hosting RAN requirement |
Withdrawn |
Not available Late document |
|||
Cont |
Sprint |
Proposal to address editor's note on application to connected and/or idle mode UEs |
Withdrawn |
Not available Late document |
|||
8.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 - main
discussion points o one
use case 5 (Operational Information Retrieval by RAN
operator)
was agreed to be removed (with consent by author). o one
new use case (S1-131133) clarifies that granularity
of RAN sharing should be cell/sector level o one
new use case (S1-131135) clarifies behaviour of
shared RAN for PWS messages coming from multiple participating operators. o Further
contributions for clarifications and clean-up were provided - main
agreements o It
was agreed that the next meeting should work on finalizing the TR. No new use
cases should be accepted, the meeting should concentrate 2
drafting sessions on 2 different days are requested. |
|||||||
TR |
Rapporteur |
TR 22.852 on FS_RSE
(output from drafting) |
Agreed |
Agreed as the basis of
future contributions V1.2.0 No presentation |
|||
|
|
Tdoc number for
allocation in drafting session |
Drafting |
|
|||
|
|
Tdoc number for
allocation in drafting session |
Drafting |
|
|||
8.5 FS_ACDC: Application specific congestion control for data communication [SP-120546] |
|||||||
8.5.1 FS_ACDC Contributions |
|||||||
Cont |
Qualcomm Incorporated |
Scope of ACDC Study Item: Application specific congestion control for data communication |
Noted |
|
|||
Cont |
LG Electronics, Inc., LG Uplus, KT, SKT |
Need for Prioritization of Voice Services under Operator-Defined Congestion Situations |
Moved to section 5.2 |
|
|||
8.5.2 FS_ACDC Drafting Session Information |
|||||||
AGE |
Rapporteur |
ACDC
drafting Agenda |
Revised
to S1-131197 |
|
|||
AGE |
Rapporteur |
ACDC
drafting Agenda |
Revised
to S1-131267 |
Revision
of S1-131140. |
|||
AGE |
Rapporteur |
ACDC
drafting Agenda |
Noted |
Revision of S1-131140. Revision
of S1-131197. |
|||
REP |
Rapporteur |
ACDC
drafting Report |
Revised
to S1-131268 |
|
|||
REP |
Rapporteur |
ACDC
drafting Report |
Approved |
Revision
of S1-131141. |
|||
Summary
of drafting session main
discussion points -
Definition of application
and service. -
Interaction with other
existing access barring mechanisms. -
Roaming for IMS
voice/video services main
agreements -
The CR was discussed. The requirements for the
case when ASAC is independently used in non-roaming scenario were understood. -
NOTE: at the SA1 plenary,
a new WID “Application and Service Access Control” and its exception sheet
were approved. |
|||||||
TR |
Rapporteur |
TR
22.806 on FS_ACDC (output from drafting) |
Withdrawn |
|
|||
No contributions |
|||||||
REP |
MCC |
Draft SA1-SA2 joint meeting minutes |
Noted |
|
|||
9.1 Agenda |
|||||||
AGE |
SA1/SA2 Chairmen |
Draft SA1-SA2 joint meeting agenda |
Revised to S1-131238 |
|
|||
AGE |
SA1/SA2 Chairmen |
Draft SA1-SA2 joint meeting agenda |
Revised to S1-131239 |
Revision of S1-131205. |
|||
AGE |
SA1/SA2 Chairmen |
Draft SA1-SA2 joint meeting agenda |
Approved |
Revision of S1-131238. No presentation |
|||
9.2
Joint
meeting 1 (JM1) |
|||||||
9.2.1 Multiple M2M service enablement frameworks |
|||||||
Cont |
KPN (Rapporteur) |
Implications of multiple service enablement frameworks |
Not treated in JM1 |
Moved from section 7.1 |
|||
Cont |
Telecom Italia |
Multiple service enablement frameworks |
Not treated in JM1 |
Moved from section 7.1 |
|||
9.3.1 UPCON |
|||||||
Contribution depends on SA1 discussion of S1-131071 |
|||||||
Cont |
Qualcomm, et al. |
UPCON Normative Requirement derived from Use Case 1 in TR22.805 |
Noted |
Noted in JM2 |
|||
9.3.2 ProSe |
|||||||
Cont |
SA WG2 Chairman (Samsung) |
Questions for JM2 SA2 95 / SA1 61 |
Noted |
Noted in JM2 |
|||
Cont |
MCC |
SA1 reply to SA2 questions on ProSe for JM2 SA2 95 / SA1 61 |
Revised to S1-131237 |
|
|||
Cont |
SA1 |
SA1 reply to SA2 questions on ProSe for JM2 SA2 95 / SA1 61 |
Noted |
Revision of S1-131230. Noted in JM2 |
|||
WP |
ETSI Secretariat |
3GPP Work Plan: extract for SA1#60 |
Noted |
|
|||
REP |
Rapporteur (NSN) |
GCSE_LTE Status Update |
Agreed |
|
|||
REP |
Rapporteur (NSN) |
GCSE_LTE Status Update |
Noted |
Revision of S1-131123. |
|||
REP |
Rapporteur (Qualcomm) |
ProSe Status Update |
Revised to S1-131321 |
|
|||
REP |
Rapporteur (Qualcomm) |
ProSe Status Update |
Agreed |
Revision of S1-131122. No presentation |
|||
REP |
Rapporteur (Qualcomm) |
FS_ProSe Status Update |
Withdrawn |
No presentation |
|||
REP |
Rapporteur (KPN) |
MTCe-SRM Status Update |
Approved |
|
|||
REP |
Rapporteur (KPN) |
MTCe- SIMSE Status Update |
Approved |
|
|||
REP |
Rapporteur (KDDI) |
UPCON Status Update |
Agreed |
|
|||
REP |
Rapporteur (Huawei) |
FS_MTCe Status Update |
Agreed |
|
|||
REP |
Rapporteur (NEC) |
FS_RSE Status Update |
Agreed |
|
|||
REP |
Rapporteur (NTT DOCOMO) |
FS_ACDC Status Update |
Agreed |
|
|||
REP |
Rapporteur (NTT DOCOMO) |
ASAC status update |
Revised to S1-131323 |
|
|||
REP |
Rapporteur (NTT DOCOMO) |
ASAC status update |
Agreed |
Revision of S1-131293. No presentation |
|||
REP |
Rapporteur (Orange) |
LangInfo Status Update |
Agreed |
|
|||
REP |
Rapporteur (China Mobile) |
IMS_WebRTC Status Update |
Agreed |
|
|||
REP |
Rapporteur (Orange) |
ECTB status update |
Withdrawn |
|
|||
REP |
Rapporteur (Telecom Italia) |
ESID status update |
Agreed |
|
|||
REP |
Rapporteur (NTT DOCOMO) |
PMOC status update |
Agreed |
|
|||
2013 meetings: SA1#61bis 8 – 11 April 2013 San Diego, USA Scope: ProSe and GCSE_LTE only 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 Sapporo, Japan SA1#67 18 – 22 Aug 2014 North America, TBD SA1#67bis 13 – 17 Oct 2014 TBD Will
be cancelled if not needed SA1#68 17 – 21 Nov 2014 Europe, TBD |
|||||||
Close
by 16:30 on Friday |
|||||||
14 Withdrawn documents (admin purposes only) |
|||||||
|
|
|
Withdrawn |
|
|||
|
|
|
Withdrawn |
|
|||
|
Intel |
|
Withdrawn |
|
|||
|
Intel |
|
Withdrawn |
|
|||
|
|
|
Withdrawn |
|
|||
15 Document numbers to be allocated (admin purposes only) |
|||||||
|
|
|
Mona to allocate |
|
|||
|
|
|
Mona to allocate |
|
|||
|
|
|
Mona to allocate |
|
|||
|
|
|
Unallocated |
|
|||
|
|
|
Unallocated |
|
|||
Contents
1.3 Previous SA1 meeting report
2 Issues for early consideration
3.2 Report from SA1 ProSe and GCSE_LTE ad hoc meeting (23
– 25 January 2013)
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-11 and earlier contributions
7.1 MTCe-SIMSE: Interworking with M2M service enablement
layer [SP-120436]
7.2 GCSE_LTE: Group communication system enablers for LTE
[SP-120876]
7.2.1 GCSE_LTE
Drafting Session Information
7.2.2 GCSE_LTE
Drafting Session Information
7.3 WLAN_NS: WLAN network selection for 3GPP terminals
[SP-120259] (SA1 secondary responsibility)
7.4 MTCe-SRM: Service requirement maintenance [SP-120541]
7.5 UPCON: User plane congestion management [SP-120545]
7.6 ProSe: Proximity-based services [SP-120935]
7.7 IMS_WebRTC: Web Real Time Communication access to IMS
[SP-120892]
7.8 LangInfo: Language and modality information for
communications [SP-120937]
7.9 Other Rel-12 contributions
8.1 FS_MTCe: Enhancements for
Machine-Type Communications [SP-100448]
8.2 FS_ProSe: Proximity-based
Services [SP-110638]
8.3 FS_UPCON: User plane congestion
management [SP-110819]
8.4 FS_RSE: RAN Sharing enhancements
[SP-110820]
8.4.2 FS_RSE
Drafting Session Information
8.5 FS_ACDC: Application specific congestion control for
data communication [SP-120546]
8.5.2 FS_ACDC
Drafting Session Information
8.6 Other Study Item contributions
9.1.1 Multiple
M2M service enablement frameworks
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)