3GPP TSG-SA WG1 Meeting #64 S1-135002
Title: Draft Schedule and Agenda with document allocation for SA1#64
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 = Plaza B (lobby level)
Room B: Breakout = Union Square 1/2 (level 4) - Wednesday only
|
|
|
Monday |
Tuesday |
Wednesday |
Thursday |
Friday |
|
Q0 |
08:00
09:00 |
|
|
Drafting 2 (Rm B) 8.1 RSE |
|
|
|
Q1 |
09:00
10:30 |
Plenary: 1. Opening 3. Report/Action Items 4. LS 5.2 New WIDs |
Plenary: 9.1 FS_ACDC 5.2 New WIDs (PTT) 9.2 FS_REOPS |
Drafting 1 (Rm A): 9.5 FS_eICBD ================= Drafting 2 (Rm B) 8.1 RSE |
Plenary: 5.2 New WIDs 4. LS 8.1 RSE |
Plenary: 9.5 FS_eICBD 5.2 New WIDs 4. LS 7.3. Rel-12 other 11.3 SA1 improvements |
|
Q2 |
11:00
12:30 |
Plenary: 5.2 New WIDs 5.3 New work proposals |
Plenary: 9.2 FS_REOPS |
Drafting 1 (Rm A): 9.5 FS_eICBD ================= Drafting 2 (Rm B) 9.1 FS_ACDC |
Plenary: 8.1 RSE 9.1 FS_ACDC 9.5 FS_eICBD |
Plenary: 8.1 RSE 9.1 FS_ACDC 8.2 SEES 9.4 FS_CSIPTO 9.3 FS_MAPN 9.2 FS_REOPS |
|
|
Lunch |
|
13:30 RSE JM input |
|
|
|
|
Q3 |
14:00
15:30 |
Plenary: 11.3 SA1 improvements 8.2 SEES |
Plenary: 9.3 FS_MAPN 9.4 FS_CSIPTO |
Drafting 1 (Rm A): 9.4 FS_CSIPTO ================= Drafting 2 (Rm B) 9.1 FS_ACDC |
Plenary: 11.3 SA1 improvements 9.4 FS_CSIPTO 8.2 SEES |
Plenary: Revisions |
|
Q4 |
16:00
17:30 |
Plenary: 8.2 SEES 8.1 RSE |
Plenary: 9.4 FS_CSIPTO 6. Rel-11 7.3. Rel-12 other Summary SA1/SA5 JM Drafting summary: ACDC, REOPS, RSE, SEES, MAPN, eICBD, CSIPTO Elections (end by 17:15) |
Drafting 1 (Rm A): 8.2 SEES ================= Drafting 2 (Rm B) 9.2 FS_REOPS |
Plenary: 8.2 SEES 9.3 FS_MAPN 9.2 FS_REOPS |
Plenary: 11.2 WI status update 11.1 Work plan (close by 16:30) |
|
Q5 |
17:40
19:00 |
Plenary: 8.1 RSE 10. SA1/SA5 JM docs 9.5 FS_eICBD |
(start at 17:30) Plenary: 10. SA1/SA5 JM (Rm A) |
Drafting 1 (Rm A): 9.3 FS_MAPN ================= Drafting 2 (Rm B) 9.2 FS_REOPS |
Plenary: Revisions (close by 20:00 latest) |
|
|
|
|
|
MMS Starts 20:00 Urban Tavern (lobby) |
|
|
|
NOTE:
Slots scheduled based on contributions submitted
Slot allocation is a rough guideline and is subject to change during the meeting week
Drafting session chairs:
RSE: Joerg Swetina (NEC)
FS_ACDC: Atsushi Minokuchi (NTT DOCOMO)
FS_REOPS: Mark Younge (T-Mobile US)
FS_CSIPTO: Mark Younge (T-Mobile US)
FS_eICBD: Mark Younge (T-Mobile US)
FS_MAPN: Mona Mustapha (Vodafone)
SEES: Antonella Napolitano (Telecom Italia)
Contribution Guidelines
SA1 AGENDA
LEGEND
Doc Type: CR (Change request), TS (Technical Specification), TR (Technical Report), LS OUT(Outgoing Liaison Statement), TO (Incoming Liaison Statement To SA1), CC (Incoming Liaison Statement Copied to SA1), REP (Report), AGE (Agenda), Cont (Contribution)
Conclusion: Agreed, Approved, Revised to S1-13xxxx, Noted, Withdrawn, Moved to section xxx, Rejected, Postponed, Email Approval, Not Handled, Unallocated, Drafting
|
Doc Type |
Tdoc number |
Sourcing company(ies) |
Document Title |
Conclusion |
Comments |
|
CR |
S1-13xxxx |
Source |
Title |
Agreed / Approved |
|
|
CR |
S1-13xxxx |
Source |
Title |
Revised to S1-13xxxx |
|
|
CR |
S1-13xxxx |
Source |
Title |
Noted |
|
|
CR |
S1-13xxxx |
Source |
Title |
Withdrawn |
|
|
CR |
S1-13xxxx |
Source |
Title |
Moved to section xxx |
|
|
CR |
S1-13xxxx |
Source |
Title |
Rejected |
|
|
CR |
S1-13xxxx |
Source |
Title |
Postponed |
|
|
CR |
S1-13xxxx |
Source |
Title |
Email Approval |
|
|
CR |
S1-13xxxx |
Source |
Title |
Not Handled |
|
|
|
S1-13xxxx |
|
|
Unallocated / Drafting |
|
|
AGE |
SA1 Chairman |
Draft agenda for SA1#64 |
Revised to S1-135001 |
|
|||
|
AGE |
SA1 Chairman |
Draft Schedule and Agenda with document allocation for SA1#64 |
Revised to S1-135002 |
Revision of S1-135000. |
|||
|
AGE |
SA1 Chairman |
Final Schedule and Agenda with document allocation for SA1#64 |
|
Revision of S1-135000. Revision of S1-135001. |
|||
|
|
The attention of the delegates to this meeting is drawn to the fact that 3GPP Individual Members have the obligation under the IPR Policies of their respective Organizational Partners to inform their respective Organizational Partners of Essential IPRs they become aware of. 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 IPR Statement and the Licensing declaration forms (e.g. see the ETSI IPR forms http://webapp.etsi.org/Ipr/).
|
|
|||||
|
As mentioned on the SA1 reflector, the report of the last meeting will be approved at the start of the meeting.
|
|||||||
|
REP |
ETSI Secretariat |
Draft minutes of SA1#63 |
Revised to S1-135005 |
|
|||
|
REP |
ETSI Secretariat |
Minutes of SA1#63 |
Approved |
Revision of S1-135004.
No presentation |
|||
|
SA1 Delegate Guidelines available at http://www.3gpp.org/SA1-delegates-survival-guide
|
|||||||
|
None
|
|||||||
|
For contributions to this Agenda Item, please contact the Chairman in advance of the meeting.
|
|||||||
|
SA1 Chairman |
SA1-related topics at SA#61 |
Noted |
Proposed to be noted without presentation. Take note: - input contributions can use docx/pptx format, but draft TSs/TRs and CRs must use doc format - minimise references to external documents. If needed, the references must refer to a specific version of the external document - Rapporteurs to review their specs to check point above |
||||
|
S1-134079 / RCPG 09_010 (Huawei) |
Response LS to 3GP SA1 on CSFB charging |
Noted |
Postponed from SA1#63 GSMA explains that the LTE roaming scenario provided by SA1, where UE roams to an LTE network for PS service and a different PLMN's 3G/2G network for CS services, is not expected to be widely adopted. A few possible issues that need to be resolved was also included.
LS was also sent to SA2, no action required by SA1. |
||||
|
TO |
S1-134089 / SG Doc 88_03 (Orange) |
LS to 3GPP SA1 re SMS Barring |
Noted, answer in S1-135305 |
Postponed from SA1#63 GSMA SG provides background information on the SMS fraud and barring issue.
CRs agreed in SA1#63 and sent with an LS to CT WGs requesting feedback. Awaiting response from CT WGs. |
|||
|
LS OUT |
Orange |
LS to 3GPP SA1 re SMS Barring |
Revised to S1-135339 |
Postponed from SA1#63 GSMA SG provides background information on the SMS fraud and barring issue.
CRs agreed in SA1#63 and sent with an LS to CT WGs requesting feedback. Awaiting response from CT WGs. Answer to S1-135018. |
|||
|
LS OUT |
Orange |
LS to 3GPP SA1 re SMS Barring |
Approved |
Postponed from SA1#63 GSMA SG provides background information on the SMS fraud and barring issue.
CRs agreed in SA1#63 and sent with an LS to CT WGs requesting feedback. Awaiting response from CT WGs. Answer to S1-135018. Revision of S1-135305.
No presentation |
|||
|
TO |
C4-132279 |
LS on SMS Barring |
Noted |
|
|||
|
TO |
S1-134086 / GSMA Wi-Fi Roaming Task Force (Orange) |
LS on Wi-Fi Roaming Task Force - Signalling Optimisation |
Postponed |
Postponed from SA1#63 GSMA asks 3GPP to specify operator policy to dynamically control WLAN authentication/association attempts that require the use of SIM based authentication. Additional information provided by Wi-Fi Alliance in S1-135104 below.
Review and update/add SA1 requirements as needed. Send any SA1 requirements to SA3 ASAP. |
|||
|
TO |
Wi-Fi Alliance (Huawei) |
Reply to WBA LS on Signaling Optimization |
Noted |
See S1-135020 above. Wi-Fi Alliance provides some additional information. An online form must be completed to access the document. |
|||
|
TO |
S1-134070 / S1-133124 / ITU COM 15 - LS 012 (Alcatel-Lucent) |
LS on Impact of traffic localization on the transport network |
Noted, answer in S1-135237 |
Postponed from SA1#62 ITU asks if SA1 work on "traffic localisation" where traffic does not traverse the core network will have any impact on the transport network – if yes then they will address this.
Response required. Awaiting any SA2 architectural decisions on this. |
|||
|
LS OUT |
Alcatel-Lucent |
Reply LS re Impact of traffic localization on the transport network |
Revised to S1-135237 |
Response to: LS COM 15 – LS 012 – E Impact of traffic localization on the transport network |
|||
|
LS OUT |
Alcatel-Lucent |
Reply LS re Impact of traffic localization on the transport network |
Revised to S1-135297 |
Response to: LS COM 15 – LS 012 – E Impact of traffic localization on the transport network Revision of S1-135040. |
|||
|
LS OUT |
Alcatel-Lucent |
Reply LS re Impact of traffic localization on the transport network |
Revised to S1-135306 |
Response to: LS COM 15 – LS 012 – E Impact of traffic localization on the transport network Revision of S1-135040. Revision of S1-135237. |
|||
|
LS OUT |
Alcatel-Lucent |
Reply LS re Impact of traffic localization on the transport network |
Approved |
Response to: LS COM 15 – LS 012 – E Impact of traffic localization on the transport network Revision of S1-135040. Revision of S1-135237. Revision of S1-135297.
No presentation |
|||
|
TO |
S1-134078 / GSMA RCPG 08_0xx (KPN) |
Response liaison statement to 3GPP SA1 on bulk charging (response to RCPG 8_006 / S1-131068) |
Noted, answer in S1-135333 |
Postponed from SA1#63 GSMA explains that there may be benefits to bulk charging.
Agreement in SA1#63 that bulk charging is to be removed 22.368 and added to 22.115 so that it is generic and does not apply specifically to the MTC case. |
|||
|
CR |
KPN (rapporteur) |
22.368 v12.2.0: Removal of group based charging requirements |
Agreed |
Moved from section 7.3 WI code MTCe-SRM Rel-12 CR0151R- Cat F Comment: Overlap with changes in S1-135106. |
|||
|
CR |
KPN (rapporteur) |
22.368 v12.2.0: Removal of group based charging requirements |
Withdrawn |
Moved from section 7.3 WI code MTCe-SRM Rel-12 CR0151R- Cat F Comment: Overlap with changes in S1-135106. Revision of S1-135102. |
|||
|
CR |
KPN (rapporteur) |
22.115 v12.2.0: Bulk charging records for roaming, interconnect, conveyance and usage charging, and charging to third parties |
Revised to S1-135239 |
WI code MTCSRM Rel-13 CR0072R- Cat B |
|||
|
CR |
KPN (rapporteur) |
22.115 v12.2.0: Bulk charging records for roaming, interconnect, conveyance and usage charging, and charging to third parties |
Revised to S1-135307 |
WI code MTCSRM Rel-13 CR0072R- Cat B Revision of S1-135136. |
|||
|
CR |
KPN (rapporteur) |
22.115 v12.2.0: Bulk charging records for roaming, interconnect, conveyance and usage charging, and charging to third parties |
Agreed |
WI code MTCSRM Rel-13 CR0072R- Cat B Revision of S1-135136. Revision of S1-135239. |
|||
|
CR |
NSN |
22.368 v12.2.0: Clarification of the term bulk CDR |
Noted |
Moved from section 7.3 WI code MTCe-SRM Rel-12 CR0141R1 Cat F (original version of CR was in S1-124089) Comment: Overlap with changes in S1-135136. "other specs affected" cross all "N" boxes |
|||
|
LS OUT |
KPN |
DRAFT LS on Bulk Charging |
Revised to S1-135240 |
Response to: LS (S1-135022 / RCPG 09_004) on Bulk charging from GSMA BARG RCPG |
|||
|
LS OUT |
KPN |
DRAFT LS on Bulk Charging |
Revised to S1-135333 |
Response to: LS (S1-135022 / RCPG 09_004) on Bulk charging from GSMA BARG RCPG Revision of S1-135137. |
|||
|
LS OUT |
KPN |
DRAFT LS on Bulk Charging |
Approved |
Response to: LS (S1-135022 / RCPG 09_004) on Bulk charging from GSMA BARG RCPG Revision of S1-135137. Revision of S1-135240.
No presentation |
|||
|
TO |
R1-133984 (US DoC) |
LS on notifying for information of including Annex about Public Safety ProSe Communication in TR 36.843 |
Noted, answer in S1-135273 |
RAN1 asks SA1 to review the informative Annex about Public Safety ProSe Communication in the RAN1 spec TR 36.843. Note: some of the text may have been superseded by the result of the Rel-12 prioritisation
Action required. |
|||
|
LS OUT |
Telecom Italia |
LS on notifying for information of including Annex about Public Safety ProSe Communication in TR 36.843 |
Revised to S1-135308 |
RAN1 asks SA1 to review the informative Annex about Public Safety ProSe Communication in the RAN1 spec TR 36.843. Note: some of the text may have been superseded by the result of the Rel-12 prioritisation
Action required. Answer to S1-135016. |
|||
|
LS OUT |
Telecom Italia |
LS on notifying for information of including Annex about Public Safety ProSe Communication in TR 36.843 |
Approved |
RAN1 asks SA1 to review the informative Annex about Public Safety ProSe Communication in the RAN1 spec TR 36.843. Note: some of the text may have been superseded by the result of the Rel-12 prioritisation
Action required. Answer to S1-135016. Revision of S1-135273.
No presentation |
|||
|
TO |
S5-131531 (Alcatel-Lucent) |
Reply LS to SA1 on OAM for Network Sharing |
Noted |
SA5 agrees to a joint meeting. See section 10 on the joint meeting agenda. No further action required. |
|||
|
TO |
S4-131404 (Huawei) |
LS on Clarifications on service requirements of MBMS on demand |
Postponed |
|
|||
|
CC |
SP-130504 (Orange) |
Reply LS on WBA Carrier Wi-Fi |
Noted |
Proposed to be noted without presentation
No action required |
|||
|
5.1 Revisions of existing WIDs (including related contributions) |
|||||||
|
No contributions to this agenda item.
|
|||||||
|
5.2 New Study and Work Items (including related contributions) |
|||||||
|
Alcatel-Lucent |
Proposed new WID for enhancements to support webRTC interworking |
Revised to S1-135241 |
|
||||
|
WID |
Alcatel-Lucent |
Proposed new WID for enhancements to support webRTC interworking |
Noted |
Revision of S1-135041. |
|||
|
Cont |
US Department of Commerce |
Push to talk and its relationship with group communications |
Noted |
|
|||
|
WID |
U.S. Department of Commerce, Home Office (UK), et al |
Proposed New WID on Mission Critical Push To Talk over LTE (MCPTToLTE) |
Revised to S1-135242 |
|
|||
|
WID |
U.S. Department of Commerce, Home Office (UK), et al |
Proposed New WID on Mission Critical Push To Talk over LTE (MCPTToLTE) |
Revised to S1-135268 |
Revision of S1-135056. |
|||
|
WID |
U.S. Department of Commerce, Home Office (UK), et al |
Proposed New WID on Mission Critical Push To Talk over LTE (MCPTToLTE) |
Revised to S1-135298 |
Revision of S1-135056. Revision of S1-135242. |
|||
|
WID |
U.S. Department of Commerce, Home Office (UK), et al |
Proposed New WID on Mission Critical Push To Talk over LTE (MCPTToLTE) |
Revised to S1-135330 |
Revision of S1-135056. Revision of S1-135242. Revision of S1-135268. |
|||
|
WID |
U.S. Department of Commerce, Home Office (UK), et al |
Proposed New WID on Mission Critical Push To Talk over LTE (MCPTToLTE) |
Agreed |
Revision of S1-135056. Revision of S1-135242. Revision of S1-135268. Revision of S1-135298.
No presentation |
|||
|
TS |
US Department of Commerce |
TS skeleton for Mission Critical Push to Talk over LTE |
Noted |
|
|||
|
Cont |
China Mobile, Huawei |
Discussion paper on Flexible Mobile Service Orchestration |
Noted |
|
|||
|
WID |
China Mobile |
New WID on Flexible Mobile Service Orchestration |
Revised to S1-135243 |
Comment: missing "X" entry for Stage 1 in 2nd table in clause 2.3. Normative WID with a study phase is not recommended practice in SA1 –this WID can be either a study item or normative WID. |
|||
|
WID |
China Mobile |
New SID on Flexible Mobile Service Steering |
Revised to S1-135300 |
Revision of S1-135080. |
|||
|
WID |
China Mobile |
New SID on Flexible Mobile Service Steering |
Agreed |
Revision of S1-135080. Revision of S1-135243. |
|||
|
WID |
China Telecom |
New study on Requirement for Virtualization and Programmable of Mobile Networks (FS_RVPMNs) |
Noted |
Moved from section 5.3 Comment: remove "requirement for" from title |
|||
|
Cont |
Acer, Intel, ITRI, III |
Discussion paper on "Calling User Importance Status Identification" |
Noted |
|
|||
|
WID |
Acer, Inc. |
Draft WID on Calling User Importance Status Identification |
Revised to S1-135244 |
Comment: clean-up is needed (removal of "??"), additional technical detail required in the objectives section – what technical aspects will be covered? |
|||
|
WID |
Acer, Inc. |
Draft WID on Calling User Importance Status Identification |
Noted |
Comment: clean-up is needed (removal of "??"), additional technical detail required in the objectives section – what technical aspects will be covered? Revision of S1-135086. |
|||
|
WID |
Sprint |
New WID proposal on service aspects for dealing with spoofed calls |
Revised to S1-135245 |
Comment: For study, "X" entry for Stage 1 in 2nd table in clause 2.3 is not needed |
|||
|
WID |
Sprint |
New WID proposal: Study on service aspects for dealing with spoofed calls |
Revised to S1-135301 |
Comment: For study, "X" entry for Stage 1 in 2nd table in clause 2.3 is not needed Revision of S1-135113. |
|||
|
WID |
Sprint |
New WID proposal: Study on service aspects for dealing with spoofed calls |
Noted |
Revision of S1-135113. Revision of S1-135245. |
|||
|
Cont |
China Mobile |
Discussion paper on Enhancement of Calling Presentation |
Noted |
|
|||
|
WID |
China Mobile |
Study on Enhancement of Supplementary Services |
Revised to S1-135140 |
Comment: For study, "X" entry for Stage 1 in 2nd table in clause 2.3 is not needed. In objectives section: - do not use "specify" – this is for normative work, not a study - use of "scope" – the scope needs to be defined in this section In clause 10: - SA1 TRs should be 22.8xx and target dates need to be for SA plenary, not SA1. - For a study, CRs to existing specs cannot be generated (remove 22.004, 22.081 and 22.096) |
|||
|
WID |
China Mobile |
Study on Enhanced Calling Information Presentation |
Revised to S1-135302 |
Revision of S1-135083. |
|||
|
WID |
China Mobile |
Study on Enhanced Calling Information Presentation |
Revised to S1-135331 |
Revision of S1-135083. Revision of S1-135140. |
|||
|
WID |
China Mobile |
Study on Enhanced Calling Information Presentation |
Agreed |
Revision of S1-135083. Revision of S1-135140. Revision of S1-135302.
No presentation |
|||
|
WID |
Qualcomm Incorporated et al. |
New WID for Study on Multimedia Broadcast Supplement for PWS (FS_MBSP) |
Revised to S1-135246 |
Moved from section 5.3 |
|||
|
WID |
Qualcomm Incorporated et al. |
New WID for Study on Multimedia Broadcast Supplement for PWS (FS_MBSP) |
Revised to S1-135291 |
Moved from section 5.3 Revision of S1-135105. |
|||
|
WID |
Qualcomm Incorporated et al. |
New WID for Study on Multimedia Broadcast Supplement for PWS (FS_MBSP) |
Revised to S1-135303 |
Moved from section 5.3 Revision of S1-135105. Revision of S1-135246. |
|||
|
WID |
Qualcomm Incorporated et al. |
New WID for Study on Multimedia Broadcast Supplement for PWS (FS_MBSP) |
Revised to S1-135332 |
Moved from section 5.3 Revision of S1-135105. Revision of S1-135246. Revision of S1-135291. |
|||
|
WID |
Qualcomm Incorporated et al. |
New WID for Study on Multimedia Broadcast Supplement for PWS (FS_MBSP) |
Agreed |
Moved from section 5.3 Revision of S1-135105. Revision of S1-135246. Revision of S1-135291. Revision of S1-135303.
No presentation |
|||
|
WID |
KPN |
Draft WID on Service Requirement Maintenance for MTC |
Revised to S1-135247 |
To be treated together with S1-135059 (section 11.3) |
|||
|
WID |
KPN |
Draft WID on Service Requirement Maintenance for MTC |
Revised to S1-135304 |
To be treated together with S1-135059 (section 11.3) Revision of S1-135096. |
|||
|
WID |
KPN |
Draft WID on Service Requirement Maintenance for MTC |
Agreed |
To be treated together with S1-135059 (section 11.3) Revision of S1-135096. Revision of S1-135247. |
|||
|
Cont |
Telefónica |
Contribution to the Technical Report (TR22.xxx) on Study of Need of Multiple APNs |
Moved to section 9.3 |
|
|||
|
5.3 Proposals for new work (precursor to future Study and Work Items) |
|||||||
|
NSN |
Thoughts on Rel-13 work for GCSE |
Noted |
|
||||
|
WID |
China Telecom |
New study on Requirement for Virtualization and Programmable of Mobile Networks (FS_RVPMNs) |
Moved to section 5.2 |
|
|||
|
WID |
Qualcomm Incorporated et al. |
New WID for Study on Multimedia Broadcast Supplement for PWS (FS_MBSP) |
Moved to section 5.2 |
|
|||
|
Deutsche Telekom |
22.278 v12.4.0: Clarification to Annex B1 on EPS-applicable specifications |
Noted |
Moved from section 7.3 WI code SAE Rel-12 CR0190R- Cat D Comment: decision needed on earliest release to apply changes to. Earliest release CR will be Cat D and WI code TEIx to be used according to earliest release. Other mirror CRs will be Cat A. |
||||
|
CR |
Deutsche Telekom |
22.278 v12.4.0: Clarification to Annex B1 on EPS-applicable specifications |
Withdrawn |
Moved from section 7.3 WI code SAE Rel-12 CR0190R- Cat D Comment: decision needed on earliest release to apply changes to. Earliest release CR will be Cat D and WI code TEIx to be used according to earliest release. Other mirror CRs will be Cat A. Revision of S1-135009. |
|||
|
CR |
Deutsche Telekom |
22.278 (Rel-11): Clarfication to Annex B1 - Mirror CR |
Withdrawn |
Not available – mirror CR to be created at the meeting CR# 0191 |
|||
|
CR |
Deutsche Telekom |
22.278 (Rel-10): Clarfication to Annex B1 - Mirror CR |
Withdrawn |
Not available – mirror CR to be created at the meeting CR# 0192 |
|||
|
CR |
Deutsche Telekom |
22.278 (Rel-9): Clarfication to Annex B1 - Mirror CR |
Withdrawn |
Not available – mirror CR to be created at the meeting CR# 0193 |
|||
|
CR |
Deutsche Telekom |
22.278 (Rel-8): Clarfication to Annex B1 |
Withdrawn |
Not available – mirror CR to be created at the meeting CR# 0194 |
|||
|
CR |
Orange |
22.067 v11.0.0: TS reference corrections |
Revised to S1-135287 |
WI code TEI11 Rel-11 CR0009R- Cat D Comment: decision needed on earliest release to apply changes to. Earliest release CR will be Cat D and WI code TEIx to be used according to earliest release. Other mirror CRs will be Cat A. |
|||
|
CR |
Orange |
22.067 v11.0.0: TS reference corrections |
Agreed |
WI code TEI11 Rel-11 CR0009R- Cat D Comment: decision needed on earliest release to apply changes to. Earliest release CR will be Cat D and WI code TEIx to be used according to earliest release. Other mirror CRs will be Cat A. Revision of S1-135124.
No presentation |
|||
|
CR |
Deutsche Telekom |
22.105 v11.0.1: Correction of external references |
Revised to S1-135288 |
WI code TEI11 Rel-11 CR0056R- Cat D |
|||
|
CR |
Deutsche Telekom |
22.105 v11.0.1: Correction of external references |
Agreed |
WI code TEI11 Rel-11 CR0056R- Cat D Revision of S1-135230.
No presentation |
|||
|
CR |
Deutsche Telekom |
22.240 v11.0.0: Correction of external references |
Revised to S1-135289 |
WI code TEI11 Rel-11 CR0009R- Cat D |
|||
|
CR |
Deutsche Telekom |
22.240 v11.0.0: Correction of external references |
Agreed |
WI code TEI11 Rel-11 CR0009R- Cat D Revision of S1-135231.
No presentation |
|||
7 Rel-12 Contributions |
|||||||
7.1 GCSE_LTE: Group communication system enablers for LTE [SP-130397] |
|||||||
|
No contributions to this agenda item
|
|||||||
7.2 ProSe: Proximity-based services [SP-130030] |
|||||||
|
No contributions to this agenda item
|
|||||||
|
Cont |
NII Holdings |
Discussion: Roaming issues near international borders |
Noted |
|
|||
|
CR |
NII Holdings |
22.011 v12.0.0: Clarification of scanning option |
Revised to S1-135251 |
WI code TEI12 Rel-12 CRnum R- Cat Comment: CR number required, CR category required, "Reason for change" more detailed explanation required |
|||
|
CR |
NII Holdings |
22.011 v12.0.0: Clarification of scanning option |
Revised to S1-135143 |
WI code TEI12 Rel-12 CR0195R1 Cat C Revision of S1-135131. |
|||
|
CR |
NII Holdings |
22.011 v12.0.0: Clarification of scanning option |
Noted |
WI code TEI12 Rel-12 CR0195R1 Cat C Revision of S1-135131. Revision of S1-135251. |
|||
|
CR |
Deutsche Telekom |
22.278 v12.4.0: Clarification to Annex B1 on EPS-applicable specifications |
Moved to section 6 |
WI code SAE Rel-12 CR0190R- Cat D |
|||
|
CR |
KPN (rapporteur) |
22.368 v12.2.0: Removal of group based charging requirements |
Moved to section 4 |
WI code MTCe-SRM Rel-12 CR0151R- Cat F |
|||
|
CR |
NSN |
22.368 v12.2.0: Clarification of the term bulk CDR |
Moved to section 4 |
WI code MTCe-SRM Rel-12 CR0141R1 Cat F |
|||
8 Rel-13 Contributions |
|||||||
|
8.1 RSE: RAN Sharing Enhancements [SP-130330], includes FS_RSE [SP-110820] |
|||||||
|
CR |
Alcatel-Lucent |
22.101 v13.0.0: Editorial fixes to RAN Sharing Enhancements |
Revised to S1-135258 |
WI code RSE Rel- CR0464R- Cat F Comment: "editorial" fix is Cat D, Cat F changes require one "Proposed change affects" box to be crossed, "Release" is Rel-13, "Reason for change" has spurious "also", "other specs affected" cross all "N" boxes |
|||
|
CR |
Alcatel-Lucent |
22.101 v13.0.0: Editorial fixes to RAN Sharing Enhancements |
Revised to S1-135293 |
WI code RSE Rel- CR0464R- Cat F Revision of S1-135038. |
|||
|
CR |
Alcatel-Lucent |
22.101 v13.0.0: Editorial fixes to RAN Sharing Enhancements |
Agreed |
WI code RSE Rel- CR0464R- Cat F Revision of S1-135038. Revision of S1-135258. |
|||
|
CR |
Telefónica |
22.101 v13.0.0: Extending RAN Sharing Requirements to GERAN and UTRAN |
Noted |
WI code RSE Rel-13 CR0467R- Cat B |
|||
|
Cont |
NEC |
Motivational slides for missing RSE requirements on Load balancing and On-demand capacity negotiation |
Noted |
For RSE drafting session |
|||
|
CR |
Alcatel-Lucent, Sprint, SoftBank Mobile, Bell Mobility, Rogers Wireless, NEC |
22.101 v13.0.0: Support for Load Balancing in Hosting E-UTRAN |
Revised to S1-135259 |
WI code RSE Rel- CR0465R- Cat B Overlap with S1-135043 Comment: at least one "Proposed change affects" box needs to be crossed, "Release" is Rel-13, "other specs affected" cross all "N" boxes |
|||
|
CR |
Alcatel-Lucent, Sprint, SoftBank Mobile, Bell Mobility, Rogers Wireless, NEC |
22.101 v13.0.0: Support for Load Balancing in Hosting E-UTRAN |
Revised to S1-135161 |
WI code RSE Rel- CR0465R- Cat B Overlap with S1-135043 Comment: at least one "Proposed change affects" box needs to be crossed, "Release" is Rel-13, "other specs affected" cross all "N" boxes Revision of S1-135039. For RSE drafting session |
|||
|
CR |
Alcatel-Lucent, Sprint, SoftBank Mobile, Bell Mobility, Rogers Wireless, NEC |
22.101 v13.0.0: Support for Load Balancing in Hosting E-UTRAN |
Revised to S1-135309 |
WI code RSE Rel- CR0465R- Cat B Overlap with S1-135043 Revision of S1-135039. For RSE drafting session Revision of S1-135259. Agreed in drafting session |
|||
|
CR |
Alcatel-Lucent, Sprint, SoftBank Mobile, Bell Mobility, Rogers Wireless, NEC |
22.101 v13.0.0: Support for Load Balancing in Hosting E-UTRAN |
Agreed |
WI code RSE Rel- CR0465R- Cat B Overlap with S1-135043 Revision of S1-135039. For RSE drafting session Revision of S1-135259. Agreed in drafting session Revision of S1-135161.
No presentation |
|||
|
CR |
Telefonica |
22.101 v13.0.0: Additional RAN Sharing Requirements |
Revised to S1-135260 |
WI code RSE Rel-13 CR0466R- Cat B Load balancing overlap with S1-135039 |
|||
|
CR |
Telefonica |
22.101 v13.0.0: Additional RAN Sharing Requirements |
Revised to S1-135295 |
WI code RSE Rel-13 CR0466R- Cat B Load balancing overlap with S1-135039 Revision of S1-135043. For RSE drafting session |
|||
|
CR |
Telefonica |
22.101 v13.0.0: Additional RAN Sharing Requirements |
Revised to S1-135310 |
WI code RSE Rel-13 CR0466R- Cat B Load balancing overlap with S1-135039 Revision of S1-135043. For RSE drafting session Revision of S1-135260. Agreed in drafting session |
|||
|
CR |
Telefonica |
22.101 v13.0.0: Additional RAN Sharing Requirements |
Agreed |
WI code RSE Rel-13 CR0466R- Cat B Load balancing overlap with S1-135039 Revision of S1-135043. For RSE drafting session Revision of S1-135260. Agreed in drafting session Revision of S1-135295. |
|||
|
CR |
NEC |
22.101 v13.0.0: S1-135052 CR to 22.101 Requirement for On-demand capacity negotiation for RSE |
Revised to S1-135261 |
WI code RSE Rel-13 CR0470R- Cat B Comment: change title to "On-demand capacity negotiation in a shared E-UTRAN", source should be "NEC", "Reason for change" needs to be changed to a justification for the functionality introduced. |
|||
|
CR |
NEC |
22.101 v13.0.0: S1-135052 CR to 22.101 Requirement for On-demand capacity negotiation for RSE |
Revised to S1-135160 |
WI code RSE Rel-13 CR0470R- Cat B Comment: change title to "On-demand capacity negotiation in a shared E-UTRAN", source should be "NEC", "Reason for change" needs to be changed to a justification for the functionality introduced. Revision of S1-135052. For RSE drafting session |
|||
|
CR |
NEC |
22.101 v13.0.0: S1-135052 CR to 22.101 Requirement for On-demand capacity negotiation for RSE |
Revised to S1-135162 |
WI code RSE Rel-13 CR0470R- Cat B Comment: change title to "On-demand capacity negotiation in a shared E-UTRAN", source should be "NEC", "Reason for change" needs to be changed to a justification for the functionality introduced. Revision of S1-135052. For RSE drafting session Revision of S1-135261. |
|||
|
CR |
NEC, NSN, Softbank Mobile, Sprint, Alcatel-Lucent, Bell Canada |
22.101 v13.0.0: Requirement for On-demand capacity negotiation for RSE |
Revised to S1-135312 |
WI code RSE Rel-13 CR0470R- Cat B Comment: change title to "On-demand capacity negotiation in a shared E-UTRAN" Revision of S1-135052. For RSE drafting session Revision of S1-135261. Revision of S1-135160. Agreed in drafting session |
|||
|
CR |
NEC, NSN, Softbank Mobile, Sprint, Alcatel-Lucent, Bell Canada |
22.101 v13.0.0: Requirement for On-demand capacity negotiation for RSE |
Agreed |
WI code RSE Rel-13 CR0470R- Cat B Comment: change title to "On-demand capacity negotiation in a shared E-UTRAN" Revision of S1-135052. For RSE drafting session Revision of S1-135261. Revision of S1-135160. Agreed in drafting session Revision of S1-135162.
No presentation |
|||
|
CR |
NEC |
22.101 v13.0.0: Adding explanatory text to requirements on E-UTRAN Sharing |
Revised to S1-135262 |
WI code RSE Rel-13 CR0469R- Cat C Comment: source should be "NEC" |
|||
|
CR |
NEC |
22.101 v13.0.0: Adding explanatory text to requirements on E-UTRAN Sharing |
Revised to S1-135296 |
WI code RSE Rel-13 CR0469R- Cat C Comment: source should be "NEC" Revision of S1-135049. For RSE drafting session |
|||
|
CR |
NEC |
22.101 v13.0.0: Adding explanatory text to requirements on E-UTRAN Sharing |
Revised to S1-135313 |
WI code RSE Rel-13 CR0469R- Cat C Comment: source should be "NEC" Revision of S1-135049. For RSE drafting session Revision of S1-135262. Agreed in drafting session |
|||
|
CR |
NEC |
22.101 v13.0.0: Adding explanatory text to requirements on E-UTRAN Sharing |
Agreed |
WI code RSE Rel-13 CR0469R- Cat C Revision of S1-135049. For RSE drafting session Revision of S1-135262. Agreed in drafting session Revision of S1-135296.
No presentation |
|||
|
CR |
Huawei, Orange |
22.101 v13.0.0: Clarification of Hosting E_UTRAN Operator role |
Revised to S1-135277 |
WI code RSE Rel-13 CR0468R- Cat C Comment: To be considered as input to the SA1/SA5 JM, but to be reviewed in SA1 first. For RSE drafting session |
|||
|
CR |
Huawei, Orange, NEC |
22.101 v13.0.0: Clarification of Hosting E_UTRAN Operator role |
Revised to S1-135159 |
WI code RSE Rel-13 CR0468R- Cat C Comment: To be considered as input to the SA1/SA5 JM, but to be reviewed in SA1 first. For RSE drafting session Revision of S1-135091. |
|||
|
CR |
Huawei, Orange, NEC |
22.101 v13.0.0: Clarification of Hosting E_UTRAN Operator role |
Revised to S1-135294 |
WI code RSE Rel-13 CR0468R- Cat C Comment: To be considered as input to the SA1/SA5 JM, but to be reviewed in SA1 first. For RSE drafting session Revision of S1-135091. Revision of S1-135277. |
|||
|
CR |
Huawei, Orange, NEC |
22.101 v13.0.0: Clarification of Hosting E_UTRAN Operator role |
Agreed |
WI code RSE Rel-13 CR0468R- Cat C For RSE drafting session Revision of S1-135091. Revision of S1-135277. Revision of S1-135159. Agreed in drafting session |
|||
8.1.1 RSE drafting session information |
|||||||
|
AGE |
Rapporteur |
RSE drafting agenda |
Noted |
|
|||
|
REP |
Rapporteur |
RSE drafting report |
Approved |
|
|||
|
Summary of drafting session
Percentage of Work Item Completion: 99% • Progress made at this meeting: • Changed requirements on OA&M access (now aligned to SA5) • Added requirements on load balancing and “on-demand capacity negotiation” • Added explanatory text to existing requirements • Aligned with SA5 definitions Rapporteur will create editorial CR (changing “Hosting E-UTRAN” to “Shared E-UTRAN”) at next meeting to avoid overlapping CRs Planning of future activities: · No further work in SA1 foreseen, except: Action to the rapporteur to provide editorial CR at next meeting.
|
|||||||
8.2 SEES: Service Exposure and Enablement Support [SP-130505] |
|||||||
|
TR |
Rapporteur (KPN) |
Draft TR skeleton for SEES |
Revised to S1-135167 |
For SEES drafting session |
|||
|
TR |
Rapporteur (KPN) |
Draft TR skeleton for SEES |
Agreed |
For SEES drafting session Revision of S1-135097. Agreed in drafting session Agreed as the basis for future contributions |
|||
|
TR |
Rapporteur (KPN) |
TR 22.853 |
Agreed |
No presentation Agreed as the basis for future contributions |
|||
|
Cont |
Huawei |
Relationship of SEES work with MOSAP and OMA |
Revised to S1-135250 |
|
|||
|
Cont |
Huawei |
Relationship of SEES work with MOSAP and OMA |
Agreed |
Revision of S1-135117. For SEES drafting session Agreed in drafting session Agreed to be added to the TR |
|||
|
Cont |
NEC |
Use Case on interworking with M2M Service providers |
Revised to S1-135252 |
Comment: please use a more descriptive title |
|||
|
Cont |
NEC |
Use Case on interworking with M2M Service providers |
Revised to S1-135168 |
Comment: please use a more descriptive title Revision of S1-135048. For SEES drafting session |
|||
|
Cont |
NEC |
Use Case on interworking with M2M Service providers |
Withdrawn |
Comment: please use a more descriptive title Revision of S1-135048. For SEES drafting session Revision of S1-135252. |
|||
|
Cont |
Huawei |
SEES Use Case on background traffic |
Revised to S1-135253 |
|
|||
|
Cont |
Huawei |
SEES Use Case on background traffic |
Revised to S1-135169 |
Revision of S1-135126. For SEES drafting session |
|||
|
Cont |
Huawei |
SEES Use Case on background traffic |
Revised to S1-135316 |
Revision of S1-135126. For SEES drafting session Revision of S1-135253. |
|||
|
Cont |
Huawei |
SEES Use Case on background traffic |
Agreed |
Revision of S1-135126. For SEES drafting session Revision of S1-135253. Revision of S1-135169. Agreed to be added to the TR |
|||
|
Cont |
China Telecom |
Use Case on user data rate exposure |
Revised to S1-135254 |
Note: Originally, S1-135068 was allocated for "Use Case on user RAT type exposure" and S1-135069 for "Use Case on user data rate exposure" but this has been swapped. |
|||
|
Cont |
China Telecom |
Use Case on user data rate exposure |
Revised to S1-135172 |
Note: Originally, S1-135068 was allocated for "Use Case on user RAT type exposure" and S1-135069 for "Use Case on user data rate exposure" but this has been swapped. Revision of S1-135068. For SEES drafting session |
|||
|
Cont |
China Telecom |
Use Case on user RAT type exposure |
Revised to S1-135255 |
Note: Originally, S1-135068 was allocated for "Use Case on user RAT type exposure" and S1-135069 for "Use Case on user data rate exposure" but this has been swapped. |
|||
|
Cont |
China Telecom |
Use Case on user RAT type exposure |
Revised to S1-135172 |
Note: Originally, S1-135068 was allocated for "Use Case on user RAT type exposure" and S1-135069 for "Use Case on user data rate exposure" but this has been swapped. Revision of S1-135069. For SEES drafting session |
|||
|
Cont |
China Telecom |
Use Case on user RAT type exposure |
Revised to S1-135328 |
Note: Originally, S1-135068 was allocated for "Use Case on user RAT type exposure" and S1-135069 for "Use Case on user data rate exposure" but this has been swapped. Revision of S1-135069. For SEES drafting session |
|||
|
Cont |
China Telecom |
Use Case on user RAT type exposure |
Agreed |
Note: Originally, S1-135068 was allocated for "Use Case on user RAT type exposure" and S1-135069 for "Use Case on user data rate exposure" but this has been swapped. Revision of S1-135069. For SEES drafting session Revision of S1-135255 and S1-135254. Revision of S1-135172. Agreed to be added to the TR |
|||
|
Cont |
Huawei |
Use Case on real-time population movement exposure |
Revised to S1-135256 |
|
|||
|
Cont |
Huawei |
Use Case on real-time population movement exposure |
Revised to S1-135170 |
Revision of S1-135119. For SEES drafting session |
|||
|
Cont |
Huawei |
Use Case on real-time population movement exposure |
Revised to S1-135317 |
Revision of S1-135119. For SEES drafting session Revision of S1-135256. |
|||
|
Cont |
Huawei |
Use Case on real-time population movement exposure |
Revised to S1-135144 |
Revision of S1-135119. For SEES drafting session Revision of S1-135256. Revision of S1-135170. |
|||
|
Cont |
Huawei |
Use Case on real-time population movement exposure |
Agreed |
Revision of S1-135119. For SEES drafting session Revision of S1-135256. Revision of S1-135170. Revision of S1-135317. Agreed to be added to the TR |
|||
|
Cont |
Huawei |
Use Case on exposure of charging model choice |
Revised to S1-135257 |
|
|||
|
Cont |
Huawei |
Use Case on exposure of charging model choice |
Revised to S1-135171 |
Revision of S1-135125. For SEES drafting session |
|||
|
Cont |
Huawei |
Use Case on exposure of charging model choice |
Revised to S1-135334 |
Revision of S1-135125. For SEES drafting session Revision of S1-135257. Agreed in drafting session |
|||
|
Cont |
Huawei |
Use Case on exposure of charging model choice |
Agreed |
Revision of S1-135125. For SEES drafting session Revision of S1-135257. Agreed in drafting session Revision of S1-135171. Agreed to be added to the TR |
|||
8.2.1 SEES drafting session information |
|||||||
|
AGE |
Rapporteur/Session Chair |
SEES drafting agenda |
Noted |
|
|||
|
REP |
Rapporteur/Session Chair |
SEES drafting report |
Revised to S1-135173 |
|
|||
|
REP |
Rapporteur/Session Chair |
SEES drafting report |
Approved |
Revision of S1-135166. |
|||
|
Summary of drafting session
Skeleton and scope for new TR22.853 agreed Agreed to use the extended use case template for use cases, i.e. add sub-heading “Potential Impacts or Interactions with Existing Services/Features 5 use cases were discussed; four use cases revised, one agreed. One use case tdoc not handled
S1-135252 Remove “Time Controlled”, SA2 power consumption discussion. Focus on Use case only à5168 S1-135253 Clarify the use case. Unclear the benefit for the third parties to background data delivery à 5169 S1-135256 clarify realtime snapshot of UE, secure information: authorised third party agreement, location (LBS) à5170 S1-135257 Sponsor replaced by Third Party. Introduction of a new section “Potential Impacts or Interactions with Existing Services/Features” à 5171 agreed S1-135255 user datarate vs RAT type à 5172 S1-135254 not handled. Proposal to merge it with 5255.
|
|||||||
|
No contributions to this agenda item
|
|||||||
9.1 FS_ACDC: Application specific congestion control for data communication [SP-130415] |
|||||||
|
TR |
Rapporteur |
ACDC TR: editorial changes from MCC |
Agreed |
For ACDC drafting session Agreed in drafting session Agreed as the basis for future contributions |
|||
|
TR |
Rapporteur |
ACDC TR 22.806 |
Agreed |
No presentation Agreed as the basis for future contributions |
|||
|
Cont |
Rapporteur |
ACDC TR: editorial changes from Rapporteur |
Agreed |
For ACDC drafting session Agreed in drafting session Agreed to be added to the TR |
|||
|
Cont |
NTT DOCOMO |
ACDC TR: clean-up of Editor's notes |
Withdrawn |
For ACDC drafting session Agreed in drafting session |
|||
|
Cont |
NTT DOCOMO |
ACDC introduction: alignment to the updated WID |
Agreed |
For ACDC drafting session Agreed in drafting session Agreed to be added to the TR |
|||
|
Cont |
NTT DOCOMO |
ACDC (for information): 'Disaster Message Services', observed in the web site of Japan's Ministry of Internal Affairs and Communication |
Noted |
|
|||
|
Cont |
Sony Mobile Communication |
Discussion paper on ACDC Terminology |
Replaced by S1‑135138 |
|
|||
|
Cont |
Sony Mobile Communication |
Discussion paper on ACDC Terminology |
Noted |
Replacement for S1-135007. For ACDC drafting session The term “ACDC category” is mainly to be used in FS_ACDC TR. See notes for S1-135060. |
|||
|
Cont |
Qualcomm Incorporated |
ACDC Gap Analysis and Backwards Compatibility with Existing Access Control Mechanisms |
Noted |
|
|||
|
Cont |
NTT DOCOMO |
ACDC use case: further clarification on interaction with other forms of access control - ACB |
Revised to S1-135265 |
|
|||
|
Cont |
NTT DOCOMO |
ACDC use case: further clarification on interaction with other forms of access control - ACB |
Revised to S1-135177 |
Revision of S1-135074. For ACDC drafting session The session in principle agreed. The last part of the second potential requirement needs to be moved to NOTE. Rewording of the NOTE is needed. Only the NOTE should be agreed, before agreeing the whole P-CR. |
|||
|
Cont |
NTT DOCOMO |
ACDC use case: further clarification on interaction with other forms of access control - ACB |
Revised to S1-135183 |
Revision of S1-135074. For ACDC drafting session The session in principle agreed. The last part of the second potential requirement needs to be moved to NOTE. Rewording of the NOTE is needed. Only the NOTE should be agreed, before agreeing the whole P-CR. Revision of S1-135265. In principle agreed in the drafting session: a NOTE in the requirement section needs to be checked. |
|||
|
Cont |
NTT DOCOMO |
ACDC use case: further clarification on interaction with other forms of access control - ACB |
Agreed |
Revision of S1-135074. For ACDC drafting session The session in principle agreed. The last part of the second potential requirement needs to be moved to NOTE. Rewording of the NOTE is needed. Only the NOTE should be agreed, before agreeing the whole P-CR. Revision of S1-135265. In principle agreed in the drafting session: a NOTE in the requirement section needs to be checked. Revision of S1-135177.
No presentation Agreed to be added to the TR |
|||
|
Cont |
NTT DOCOMO |
ACDC use case: further clarification on interaction with other forms of access control - SSAC |
Agreed |
For ACDC drafting session Agreed to be added to the TR |
|||
|
Cont |
NTT DOCOMO |
ACDC use case: further clarification on interaction with other forms of access control - EAB |
Noted |
For ACDC drafting session |
|||
|
Cont |
Qualcomm Incorporated |
ACDC Use Case: Roaming Compatibility |
Noted |
For ACDC drafting session The term “ACDC category” is mainly to be used in FS_ACDC TR, with other related terms e.g. “list” being used around it. Relevant contributions are solicited to clean up TR in the next meeting. Limitation in 3GPP spec to describe about the application layer was understood. An intermediate conclusion on a roaming scheme is: (1) technically feasible schemes are foreseen, (1-1) if restricted to the level of the “category”. (1-2) if (a) we assume a roaming-in UE acts like a legacy UE[, and (b) we restrict applications to particular, operator-defined ones]. (2) from a standpoint of regulation or deployment, (2-1) the fact that a home operator cannot control allowed applications causes a problem. (2-2) there needs a lot of work outside of 3GPP in order to align “applications” among operators [or to talk with regulators]. |
|||
|
Cont |
Sony Mobile Communication |
ACDC List provisioning |
Revised to S1-135181 |
For ACDC drafting session The intention is understandable. It’s not needed to mention “roaming”. “current” network needs to be changed to “serving” network. |
|||
|
Cont |
Sony Mobile Communication |
ACDC List provisioning |
Revised to S1-135311 |
For ACDC drafting session The intention is understandable. It’s not needed to mention “roaming”. “current” network needs to be changed to “serving” network. Revision of S1-135008. In principle agreed in the drafting session: the requirement needs to be checked. |
|||
|
Cont |
Sony Mobile Communication |
ACDC List provisioning |
Agreed |
For ACDC drafting session The intention is understandable. It’s not needed to mention “roaming”. “current” network needs to be changed to “serving” network. Revision of S1-135008. In principle agreed in the drafting session: the requirement needs to be checked. Revision of S1-135181. Agreed to be added to the TR |
|||
|
Cont |
NTT DOCOMO |
ACDC use case: control range and proportionality |
Revised to S1-135267 |
|
|||
|
Cont |
NTT DOCOMO |
ACDC use case: control range and proportionality |
Revised to S1-135179 |
Revision of S1-135077. For ACDC drafting session |
|||
|
Cont |
NTT DOCOMO |
ACDC use case: control range and proportionality |
Agreed |
Revision of S1-135077. For ACDC drafting session Revision of S1-135267. Agreed in drafting session Agreed to be added to the TR |
|||
|
Cont |
Qualcomm Incorporated |
ACDC Use Case: Control of ACDC |
Revised to S1-135266 |
|
|||
|
Cont |
Qualcomm Incorporated |
ACDC Use Case: Control of ACDC |
Revised to S1-135178 |
Revision of S1-135061. For ACDC drafting session The session in principle agreed with the above two potential requirements. But rewording of those is needed. “not” should not be used. |
|||
|
Cont |
Qualcomm Incorporated |
ACDC Use Case: Control of ACDC |
Revised to S1-135182 |
Revision of S1-135061. For ACDC drafting session The session in principle agreed with the above two potential requirements. But rewording of those is needed. “not” should not be used. Revision of S1-135266. In principle agreed in the drafting session: two requirements need to be checked. |
|||
|
Cont |
Qualcomm Incorporated |
ACDC Use Case: Control of ACDC |
Revised to S1-135335 |
Revision of S1-135061. For ACDC drafting session The session in principle agreed with the above two potential requirements. But rewording of those is needed. “not” should not be used. Revision of S1-135266. In principle agreed in the drafting session: two requirements need to be checked. Revision of S1-135178. |
|||
|
Cont |
Qualcomm Incorporated |
ACDC Use Case: Control of ACDC |
Agreed |
Revision of S1-135061. For ACDC drafting session The session in principle agreed with the above two potential requirements. But rewording of those is needed. “not” should not be used. Revision of S1-135266. In principle agreed in the drafting session: two requirements need to be checked. Revision of S1-135178. Revision of S1-135182.
No presentation Agreed to be added to the TR |
|||
|
Cont |
NTT DOCOMO |
ACDC use case: graceful return to normal state |
Revised to S1-135180 |
For ACDC drafting session The requirement is good. The use case scenario is not good enough. |
|||
|
Cont |
NTT DOCOMO |
ACDC use case: graceful return to normal state |
Withdrawn |
For ACDC drafting session The requirement is good. The use case scenario is not good enough. Revision of S1-135078. |
|||
|
Cont |
LG Electronics, Inc. |
Discussion and Use case for provisioning end-user experience of IMS Service in ACDC |
Noted |
For ACDC drafting session The session understood as follows: This aspect is critical and supported by Korean, Japanese, and a few European operators. This aspect is being addressed in Rel-12 in RAN2 SI SCM and should be addressed in Rel-12. No intervention by SA1 for SCM is needed. However, for the moment, FS_ACDC does not explicitly exclude this aspect. At least when finalizing FS_ACDC TR, the progress of RAN2 SCM is checked and SA1 decides how to treat this aspect. To that end, specific contributions are needed. |
|||
|
MediaTek |
ACDC Use Case "User Preference for Application Prioritization" |
Noted |
Late document For ACDC drafting session Seemingly not so relevant to ACDC |
||||
9.1.1 FS_ACDC drafting session information |
|||||||
|
AGE |
Rapporteur |
FS_ACDC drafting agenda |
Revised to S1-135283 |
|
|||
|
AGE |
Rapporteur |
FS_ACDC drafting agenda |
Noted |
Revision of S1-135175. |
|||
|
REP |
Rapporteur |
FS_ACDC drafting report |
Approved |
|
|||
|
Summary of drafting session
- The session agreed as follows: The aspect of MMTEL bypassing ACB is critical and needs to be addressed in Rel-12 i.e. in RAN2 SCM. No intervention by SA1 for SCM is needed. (In the meantime, FS_ACDC does not explicitly exclude this aspect.) - The session agreed to use mainly the term “ACDC category” in TR. - The following potential requirement was agreed: “ACDC overrides ACB.”
|
|||||||
|
|
|
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.2 FS_REOPS: Resilient E-UTRAN operation for Public Safety [SP-130240] |
|||||||
|
WID |
General Dynamics Broadband UK |
Updates to the Work Item Description for a Feasibility Study on Isolated E-UTRAN operation |
Agreed |
|
|||
|
TR |
Rapporteur |
Reflecting MCC's tidy up of TR22.897 V0.1.0 |
Agreed |
For REOPS drafting session Agreed as a basis for future contributions |
|||
|
TR |
Rapporteur |
TR22.897 |
Revised to S1-135336 |
No presentation Agreed as a basis for future contributions |
|||
|
TR |
Rapporteur |
TR22.897 |
Agreed |
No presentation Agreed as a basis for future contributions Revision of S1-135141. Agreed as a basis for future contributions |
|||
|
Cont |
General Dynamics Broadband UK |
Review and clarification of terminology related to Isolated E-UTRAN operation |
Revised to S1-135269 |
|
|||
|
Cont |
General Dynamics Broadband UK |
Review and clarification of terminology related to Isolated E-UTRAN operation |
Revised to S1-135193 |
Revision of S1-135108. For REOPS drafting session |
|||
|
Cont |
General Dynamics Broadband UK |
Review and clarification of terminology related to Isolated E-UTRAN operation |
Agreed |
Revision of S1-135108. For REOPS drafting session Revision of S1-135269. Agreed in drafting session Agreed to be added to the TR |
|||
|
Cont |
General Dynamics Broadband UK |
Review and clarification of terminology related to Isolated E-UTRAN operation |
Withdrawn |
Revision of S1-135108. For REOPS drafting session Revision of S1-135269. Agreed in drafting session Agreed to be added to the TR Revision of S1-135193. |
|||
|
Cont |
French Ministry of Interior |
Resilient operations for public safety General approach |
Noted |
|
|||
|
Cont |
French Ministry of Interior for TCCA-CCBG |
Local fall back at enodeB group call use case |
Revised to S1-135270 |
Some overlap with S1-135116 |
|||
|
Cont |
French Ministry of Interior for TCCA-CCBG |
Local fall back at enodeB group call use case |
Agreed |
Some overlap with S1-135116 Revision of S1-135046. For REOPS drafting session Agreed in drafting session Agreed to be added to the TR |
|||
|
Cont |
French Ministry of Interior for TCCA-CCBG |
Local fall back at enodeB individual call use case |
Revised to S1-135271 |
For REOPS drafting session Some overlap with S1-135116 |
|||
|
Cont |
French Ministry of Interior for TCCA-CCBG |
Local fall back at enodeB individual call use case |
Revised to S1-135194 |
For REOPS drafting session Some overlap with S1-135116 Revision of S1-135047. For REOPS drafting session |
|||
|
Cont |
French Ministry of Interior for TCCA-CCBG |
Local fall back at enodeB individual call use case |
Agreed |
For REOPS drafting session Some overlap with S1-135116 Revision of S1-135047. For REOPS drafting session Revision of S1-135271. Agreed in drafting session Agreed to be added to the TR |
|||
|
Cont |
General Dynamics Broadband UK |
Overview of mobile cell sites and their applicability to Public Safety |
Noted |
For REOPS drafting session |
|||
|
Cont |
General Dynamics Broadband UK |
Isolated E-UTRAN operation use case: Local routing |
Revised to S1-135274 |
Some overlap with S1-135063 |
|||
|
Cont |
General Dynamics Broadband UK |
Isolated E-UTRAN operation use case: Local routing |
Revised to S1-135196 |
Some overlap with S1-135063 Revision of S1-135112. For REOPS drafting session |
|||
|
Cont |
General Dynamics Broadband UK |
Isolated E-UTRAN operation use case: Local routing |
Agreed |
Some overlap with S1-135063 Revision of S1-135112. For REOPS drafting session Revision of S1-135274. Agreed in drafting session Agreed to be added to the TR |
|||
|
Cont |
General Dynamics Broadband UK |
Isolated E-UTRAN operation use case: A limited backhaul connection |
Revised to S1-135197 |
For REOPS drafting session |
|||
|
Cont |
General Dynamics Broadband UK |
Isolated E-UTRAN operation use case: A limited backhaul connection |
Agreed |
For REOPS drafting session Revision of S1-135114. Agreed in drafting session Agreed to be added to the TR |
|||
|
Cont |
General Dynamics Broadband UK |
Isolated E-UTRAN operation use case: A wide area Isolated E-UTRAN |
Agreed |
Agreed to be added to the TR |
|||
|
Cont |
General Dynamics Broadband UK |
Isolated E-UTRAN operation use case: Service restoration |
Revised to S1-135272 |
||||
|
Cont |
General Dynamics Broadband UK |
Isolated E-UTRAN operation use case: Service restoration |
Revised to S1-135195 |
Some overlap with S1-135046 and S1-135047 Revision of S1-135116. For REOPS drafting session |
|||
|
Cont |
General Dynamics Broadband UK |
Isolated E-UTRAN operation use case: Service restoration |
Agreed |
Some overlap with S1-135046 and S1-135047 Revision of S1-135116. For REOPS drafting session Revision of S1-135272. Agreed in drafting session Agreed to be added to the TR |
|||
|
ITRI |
Use case and associated requirement for Isolated E-UTRAN |
Noted |
Comment: please use a more descriptive title |
||||
|
Cont |
InterDigital |
Use cases for FS_REOPS: Alternative backhaul |
Revised to S1-135275 |
Some overlap with S1-135112 |
|||
|
Cont |
InterDigital |
Use cases for FS_REOPS: Alternative backhaul |
Withdrawn |
Some overlap with S1-135112 Revision of S1-135063. For REOPS drafting session |
|||
|
Cont |
III |
Use Cases and Requirements for Isolated EUTRAN Operation |
Revised to S1-135276 |
Comment: please use a more descriptive title |
|||
|
Cont |
III |
Use Cases and Requirements for Isolated EUTRAN Operation |
Noted |
Comment: please use a more descriptive title Revision of S1-135024. |
|||
9.2.1 FS_REOPS drafting session information |
|||||||
|
AGE |
Rapporteur/Session chair |
FS_REOPS drafting agenda |
Withdrawn |
|
|||
|
AGE |
Rapporteur/Session chair |
FS_REOPS drafting agenda |
Noted |
|
|||
|
REP |
Rapporteur/Session chair |
FS_REOPS drafting report |
Withdrawn |
|
|||
|
REP |
Rapporteur/Session chair |
FS_REOPS drafting report |
Approved |
|
|||
|
Summary of drafting session
- 11 documents on the drafting session agenda - Agreed a revision to the TR22.897 v0.1.1 to include editorial comments from MCC - MCP is now Mobile eNB (MeNB) - Agreed the addition of four definitions: MeNB, Isolated E-UTRAN operation, Network resiliency, and Network redundancy - Agreed the addition of 7 use cases considering the following: - local fallback (group and individual) - local routing - limited backhaul - moving from Isolated to fully connected E-UTRAN - wide area multi eNB - aerial platform
|
|||||||
|
|
|
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_MAPN: Need for multiple APNs [SP-130416] |
|||||||
|
TR |
Rapporteur |
FS_MAPN - TR skeleton |
Agreed |
For MAPN drafting session Agreed in drafting session Agreed as the basis for future contributions |
|||
|
TR |
Rapporteur |
TR 22.802 |
Agreed |
No presentation Agreed as the basis for future contributions |
|||
|
Cont |
Rapporteur |
FS_MAPN - TR Introduction |
Withdrawn |
Overlap with S1-135132 |
|||
|
Cont |
Ericsson |
Study of need for Multiple APN - Introduction |
Revised to S1-135278 |
Overlap with S1-135031 |
|||
|
Cont |
Ericsson |
Study of need for Multiple APN - Introduction |
Agreed |
Overlap with S1-135031 Revision of S1-135132.
No presentation |
|||
|
Cont |
Rapporteur |
FS_MAPN - TR Scope |
Withdrawn |
Overlap with S1-135133 |
|||
|
Cont |
Ericsson |
Study of need for multiple APN - Scope |
Revised to S1-135279 |
Overlap with S1-135032 |
|||
|
Cont |
Ericsson |
Study of need for multiple APN - Scope |
Revised to S1-135318 |
Overlap with S1-135032 Revision of S1-135133. |
|||
|
Cont |
Ericsson |
Study of need for multiple APN - Scope |
Agreed |
Overlap with S1-135032 Revision of S1-135133. Revision of S1-135279.
No presentation Agreed to be added to the TR |
|||
|
Cont |
Alcatel-Lucent |
Discussion: What is the benefit of the FS_MAPN work study item? |
Noted |
|
|||
|
Cont |
Ericsson |
Study of need for multiple APN - use case In-vehicle |
Revised to S1-135280 |
|
|||
|
Cont |
Ericsson |
Study of need for multiple APN - use case In-vehicle |
Agreed |
Revision of S1-135134.
No presentation |
|||
|
Cont |
Giesecke & Devrient, Vodafone |
FS_MAPN - Use Case In-Vehicle UE |
Revised to S1-135319 |
|
|||
|
Cont |
Giesecke & Devrient, Vodafone |
FS_MAPN - Use Case In-Vehicle UE |
Agreed |
Revision of S1-135033. Agreed to be added to the TR |
|||
|
Cont |
Telefónica |
Contribution to the Technical Report (TR22.xxx) on Study of Need of Multiple APNs |
Revised to S1-135207 |
Moved from section 5.2 For MAPN drafting session Giesecke & Devrient asked whether the use case agreed in doc S1-135280 includes the scenario presented by Telefonica. Telefonica replies that the scenario is included. Ericsson encouraged to include the text proposed by Telefonica into the TR. |
|||
|
Cont |
Telefónica |
Contribution to the Technical Report (TR22.xxx) on Study of Need of Multiple APNs |
Revised to S1-135210 |
Moved from section 5.2 For MAPN drafting session Giesecke & Devrient asked whether the use case agreed in doc S1-135280 includes the scenario presented by Telefonica. Telefonica replies that the scenario is included. Ericsson encouraged to include the text proposed by Telefonica into the TR. Revision of S1-135014. |
|||
|
Cont |
Telefónica |
Contribution to the Technical Report (TR22.xxx) on Study of Need of Multiple APNs |
Agreed |
Moved from section 5.2 For MAPN drafting session Giesecke & Devrient asked whether the use case agreed in doc S1-135280 includes the scenario presented by Telefonica. Telefonica replies that the scenario is included. Ericsson encouraged to include the text proposed by Telefonica into the TR. Revision of S1-135014. Revision of S1-135207.
No presentation Agreed to be added to the TR |
|||
|
Cont |
Ericsson |
Study of need for multiple APN - use case automotive |
Revised to S1-135208 |
For MAPN drafting session Two proposals: i) to agree two different use case sections with the same “use case description” but different “service flows” sections; ii) to agree a single use case section and point out two (or more) service flows under the “service flows” section, depending on the specific technical solution to fulfill the use case; Agreement to have a single use case section and two (or more) descriptions under the “service flows” section. The chairman proposed to merge the Ericsson contribution (S1-135135) and the G&D contribution (S1-135034) into a single document (S1-135208). |
|||
|
Cont |
Rapporteur |
Study of need for multiple APN - use case automotive |
Revised to S1-135211 |
For MAPN drafting session Discussion for S1-135135 Two proposals: i) to agree two different use case sections with the same “use case description” but different “service flows” sections; ii) to agree a single use case section and point out two (or more) service flows under the “service flows” section, depending on the specific technical solution to fulfill the use case; Agreement to have a single use case section and two (or more) descriptions under the “service flows” section. The chairman proposed to merge the Ericsson contribution (S1-135135) and the G&D contribution (S1-135034) into a single document (S1-135208).
Discussion for S1-135034 Agreement to clarify the “best effort” / QoS / SLA concepts for the two distinct service flows. Agreement to delete the first operational scenario (“only one application…”) and keep the second scenario (“all the applications can be active at the same time”) because it is more generic than the first one. Agreement to change the section title from “potential new requirements” into “potential new solution” and have a description of the new solution rather than a list of requirements. Agreement to introduce an additional section dealing with a potential new ME-based solution, Rapporteur will add a new heading for this
|
|||
|
Cont |
Rapporteur |
Study of need for multiple APN - use case automotive |
Agreed |
For MAPN drafting session Discussion for S1-135135 Two proposals: i) to agree two different use case sections with the same “use case description” but different “service flows” sections; ii) to agree a single use case section and point out two (or more) service flows under the “service flows” section, depending on the specific technical solution to fulfill the use case; Agreement to have a single use case section and two (or more) descriptions under the “service flows” section. The chairman proposed to merge the Ericsson contribution (S1-135135) and the G&D contribution (S1-135034) into a single document (S1-135208).
Discussion for S1-135034 Agreement to clarify the “best effort” / QoS / SLA concepts for the two distinct service flows. Agreement to delete the first operational scenario (“only one application…”) and keep the second scenario (“all the applications can be active at the same time”) because it is more generic than the first one. Agreement to change the section title from “potential new requirements” into “potential new solution” and have a description of the new solution rather than a list of requirements. Agreement to introduce an additional section dealing with a potential new ME-based solution, Rapporteur will add a new heading for this
Revision of S1-135135 and S1-135034. Revision of S1-135208.
No presentation Agreed to be added to the TR |
|||
|
Cont |
Giersecke & Devrient, Vodafone |
FS_MAPN - Use Case Multiple APNs |
Revised to S1-135208 |
For MAPN drafting session Agreement to clarify the “best effort” / QoS / SLA concepts for the two distinct service flows. Agreement to delete the first operational scenario (“only one application…”) and keep the second scenario (“all the applications can be active at the same time”) because it is more generic than the first one. Agreement to change the section title from “potential new requirements” into “potential new solution” and have a description of the new solution rather than a list of requirements. Agreement to introduce an additional section dealing with a potential new ME-based solution, Rapporteur will add a new heading for this |
|||
9.3.1 FS_MAPN drafting session information |
|||||||
|
AGE |
Rapporteur/Session chair |
FS_MAPN drafting agenda |
Noted |
|
|||
|
REP |
Rapporteur/Session chair |
FS_MAPN drafting report |
Approved |
|
|||
|
Summary of drafting session
During the drafting session, the companies agreed the following: · the technical report skeleton; · the contribution by Telefonica; · the common parts of the G&D and Ericsson contributions (use case description, pre-conditions and post-conditions); · the Service Flow and the existing technical solution section in the Ericsson contribution (an additional note about the QCI deployment in the market will be added at the next meeting); · to reword the “potential new requirement” section in the G&D doc; · to add an ME-based solution; · to clarify the QoS / SLA concept;
|
|||||||
9.4 FS_CSIPTO: Co-ordinated P-GW change for SIPTO [SP-130417] |
|||||||
|
TR |
Rapporteur |
CSIPTO TR Skeleton |
Agreed |
For CSIPTO drafting session Agreed in drafting session Agreed as the basis for future contributions |
|||
|
TR |
Rapporteur |
TR 22.828 |
Agreed |
No presentation Agreed as the basis for future contributions |
|||
|
Cont |
Rapporteur |
CSIPTO TR Introduction |
Agreed |
Editorial clean-up needed |
|||
|
Cont |
Rapporteur |
CSIPTO TR Scope |
Agreed |
|
|||
|
Cont |
Intel |
CSIPTO for Non-IMS |
Revised to S1-135281 |
|
|||
|
Cont |
Intel |
CSIPTO for Non-IMS |
Revised to S1-135214 |
Revision of S1-135029. For CSIPTO drafting session |
|||
|
Cont |
Intel |
CSIPTO for Non-IMS |
Agreed |
Revision of S1-135029. For CSIPTO drafting session Revision of S1-135281. Agreed in drafting session Agreed to be added to the TR |
|||
|
Cont |
Intel |
CSIPTO for IMS |
Revised to S1-135282 |
|
|||
|
Cont |
Intel |
CSIPTO for IMS |
Revised to S1-135215 |
Revision of S1-135028. For CSIPTO drafting session |
|||
|
Cont |
Intel |
CSIPTO for IMS |
Agreed |
Revision of S1-135028. For CSIPTO drafting session Revision of S1-135282. Agreed in drafting session Agreed to be added to the TR |
|||
|
Cont |
Samsung Electronics, Intel, NEC, Acer, ITRI |
CSIPTO Always-on Dual PDN Connection |
Revised to S1-135284 |
|
|||
|
Cont |
Samsung Electronics, Intel, NEC, Acer, ITRI |
CSIPTO Always-on Dual PDN Connection |
Agreed |
Revision of S1-135051. For CSIPTO drafting session Agreed in drafting session Agreed to be added to the TR |
|||
|
Cont |
Samsung Electronics, Intel, NEC, Acer, ITRI |
CSIPTO On-Demand Dual PDN Connection |
Revised to S1-135285 |
|
|||
|
Cont |
Samsung Electronics, Intel, NEC, Acer, ITRI |
CSIPTO On-Demand Dual PDN Connection |
Revised to S1-135216 |
Revision of S1-135054. For CSIPTO drafting session |
|||
|
Cont |
Samsung Electronics, Intel, NEC, Acer, ITRI |
CSIPTO On-Demand Dual PDN Connection |
Agreed |
Revision of S1-135054. For CSIPTO drafting session Revision of S1-135285. Agreed in drafting session Agreed to be added to the TR |
|||
9.4.1 FS_CSIPTO drafting session information |
|||||||
|
AGE |
Rapporteur/Session chair |
FS_CSIPTO drafting agenda |
Revised to S1-135290 |
|
|||
|
AGE |
Rapporteur/Session chair |
FS_CSIPTO drafting agenda |
Noted |
Revision of S1-135212. |
|||
|
REP |
Rapporteur/Session chair |
FS_CSIPTO drafting report |
Approved |
|
|||
|
Summary of drafting session
- Skeleton Agreed - All Revised documents agreed
|
|||||||
|
|
|
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.5 FS_eICBD: Enhancements for infrastructure based data communication between devices [SP-130418] |
|||||||
|
Rapporteur |
Draft TR skeleton for FS_eIBCD |
Revised to S1-135219 |
For eICBD drafting session |
||||
|
TR |
Rapporteur |
Draft TR skeleton for FS_eIBCD |
Agreed |
For eICBD drafting session Revision of S1-135098. Agreed in drafting session Agreed as the basis of future contributions |
|||
|
TR |
Rapporteur |
TR 22.807 |
Agreed |
No presentation Agreed as the basis of future contributions |
|||
|
Cont |
Rapporteur |
Draft scope statement for TR on FS_eIBCD |
Agreed |
For eICBD drafting session Agreed in drafting session Agreed to be added to the TR |
|||
|
Cont |
InterDigital |
eICBD Discussion paper |
Revised to S1-135264 |
Comment: please use a more descriptive title |
|||
|
Cont |
InterDigital |
eICBD Discussion paper |
Revised to S1-135224 |
Comment: please use a more descriptive title For eICBD drafting session Revision of S1-135066. |
|||
|
Cont |
InterDigital |
eICBD Discussion paper |
Agreed |
Comment: please use a more descriptive title For eICBD drafting session Revision of S1-135066. Revision of S1-135264. Agreed to be added to the TR |
|||
|
Cont |
InterDigital |
eICBD Overview: Data Paths |
Noted |
|
|||
|
Cont |
KPN |
Use cases on service discovery for FS_eIBCD |
Noted |
For eICBD drafting session |
|||
|
Cont |
KPN |
Use cases for device-to-device data transfer for FS_eIBCD |
Noted |
For eICBD drafting session |
|||
|
Cont |
InterDigital |
Proposed use cases for eICBD – General and Limited Backhaul |
Revised to S1-135220 |
For eICBD drafting session |
|||
|
Cont |
InterDigital |
Proposed use cases for eICBD – General and Limited Backhaul |
Revised to S1-135226 |
For eICBD drafting session Revision of S1-135064. |
|||
|
Cont |
InterDigital |
Proposed use cases for eICBD – General and Limited Backhaul |
Revised to S1-135146 |
For eICBD drafting session Revision of S1-135064. Revision of S1-135220. |
|||
|
Cont |
InterDigital |
Proposed use cases for eICBD – General and Limited Backhaul |
Agreed |
For eICBD drafting session Revision of S1-135064. Revision of S1-135220. Revision of S1-135226. Agreed to be added to the TR |
|||
|
Cont |
Intel |
eICBD use case: UE requests a Public IP Address from its MNO |
Revised to S1-135263 |
For eICBD drafting session |
|||
|
Cont |
Intel |
eICBD use case: UE requests a Public IP Address from its MNO |
Revised to S1-135221 |
Revision of S1-135127. For eICBD drafting session |
|||
|
Cont |
Intel |
eICBD use case: UE requests a Public IP Address from its MNO |
Revised to S1-135314 |
Revision of S1-135127. For eICBD drafting session Revision of S1-135263. Agreed to be added to the TR |
|||
|
Cont |
Intel |
eICBD use case: UE requests a Public IP Address from its MNO |
Agreed |
Revision of S1-135127. For eICBD drafting session Revision of S1-135263. Agreed to be added to the TR Revision of S1-135221. |
|||
|
Cont |
Intel |
eICBD use case: UE requests its MNO to help create IP connection to another UE |
Revised to S1-135222 |
For eICBD drafting session |
|||
|
Cont |
Intel |
eICBD use case: UE requests its MNO to help create IP connection to another UE |
Agreed |
For eICBD drafting session Revision of S1-135128. Agreed to be added to the TR |
|||
|
Cont |
Intel |
eICBD use case: Automated IP Connection Establishment for UEs with Private IP Addresses |
Revised to S1-135223 |
For eICBD drafting session |
|||
|
Cont |
Intel |
eICBD use case: Automated IP Connection Establishment for UEs with Private IP Addresses |
Agreed |
For eICBD drafting session Revision of S1-135129. Agreed to be added to the TR |
|||
|
Cont |
LG Electronics, Inc. |
Use case for indoor data communication in eICBD |
Noted |
|
|||
|
Cont |
LG Electronics, Inc. |
Use case for low-energy indoor discovery for eICBD |
Noted |
|
|||
9.5.1 FS_eICBD drafting session information |
|||||||
|
AGE |
Rapporteur/Session chair |
FS_eICBD drafting agenda |
Noted |
|
|||
|
REP |
Rapporteur/Session chair |
FS_eICBD drafting report |
Approved |
|
|||
|
Summary of drafting session
- Skeleton and Scope agreed (rapporteur will add enhanced use case format) - 5121 –Limiting to Indoor, Ownership - 5122 – Outside scope of eICBD - 5100- Why do we need to discover devices we already know are on the network - 5101- Possible dependencies on SA2 ProSe work - 5064-1st use case cut, rework to make less ProSesque, cut last potential requirement, revised in 5220 - 5263, 5128, 5129, Make Potential Requirements TBD, include Extended Use Case Interdependencies
|
|||||||
|
No contributions to this agenda item
|
|||||||
10 Joint meeting on RAN sharing with SA5 |
|||||||
|
Draft agenda available in S1-135023/ S5-131939
2.1. Opening - Introductions - Approval of the agenda and objectives of the joint session
2.2 SA1: - Brief presentation of SA1 work (RSE) - Agreement on common definitions (basis of the discussion will be the LS from SA1 in S1-134181) - Information exchange/feedback on the requirements already agreed in SA1 on OAM aspects and accounting (approved in SP-130413). Specifically, for SA5 to review the list of items provided on OAM and accounting (clause 28.2.2 and 28.2.3), and to clarify whether both lists sufficiently capture all the capabilities required or whether other capabilities need to be added to the lists. - Company contributions (if any)
2.3. SA5 - Brief presentation of the SA5 (FS_OAM_SHARE/TR 32.851) work on RAN sharing - Overlap/gap analysis between SA1 and SA5 work - Gap analysis with NGMN requirements - Company contributions (if any)
2.4. Closing - Summary of decisions - Summary of action points - Next steps
|
|||||||
|
WG Chairman |
Draft agenda for SA1/SA5 Joint Meeting on RAN sharing |
Replaced by S1‑135139 |
Identical to S5-131939 |
||||
|
AGE |
WG Chairman |
Draft agenda for SA1/SA5 Joint Meeting on RAN sharing |
Revised to S1-135292 |
Replacement for S1-135023. Identical to S1-132078 |
|||
|
AGE |
WG Chairman |
Draft agenda for SA1/SA5 Joint Meeting on RAN sharing |
Noted |
Replacement for S1-135023. Identical to S1-132078 Revision of S1-135139. |
|||
|
LS |
ETSI Secretariat |
Definitions discussion (LS to SA5 on OAM for Network Sharing S1-134181) |
Noted |
Identical to S5-132082 |
|||
|
CR |
ETSI Secretariat |
Approved SA1 requirements on RAN Sharing Enhancements |
Noted |
Identical to S5-132083 |
|||
|
Cont |
NEC (Rapporteur) |
Brief presentation of SA1 work on RAN Sharing Enhancements (RSE) |
Noted |
Identical to S5-132080 |
|||
|
Cont |
Huawei, Orange, Alcatel-Lucent |
SA5 Presentation for Network Sharing Management (OAM) |
Noted |
Identical to S5-132040 |
|||
|
Cont |
Huawei, Orange, Alcatel-Lucent |
Network sharing management-SA1/SA5/NGCOR gap analysis |
Noted |
Identical to S5-131948 |
|||
|
Cont |
Orange |
Introduction to NGMN Requirements-OA&M for network sharing |
Noted |
Identical to S5-131946 |
|||
|
CR |
Huawei, Orange |
22.101 v13.0.0: Clarification of Hosting E_UTRAN Operator role |
Noted |
WI code RSE Rel-13 CR0468R- Cat C Comment: To be considered as input to the SA1/SA5 JM, but to be reviewed in SA1 first. For RSE drafting session Revision of S1-135091. |
|||
|
REP |
ETSI Secretariat |
Minutes of SA1/SA5 Joint Meeting on RAN Sharing |
Approved |
|
|||
|
ETSI Secretariat |
Extract of the 3GPP Work Plan for SA1#64 |
Noted |
|
||||
|
REP |
Rapporteur (NEC) |
RSE status update |
Approved |
|
|||
|
REP |
Rapporteur (KPN) |
SEES status update |
Revised to S1-135163 |
|
|||
|
REP |
Rapporteur (KPN) |
SEES status update |
Approved |
Revision of S1-135151.
No presentation |
|||
|
REP |
Rapporteur (NTT DOCOMO) |
FS_ACDC status update |
Approved |
|
|||
|
REP |
Rapporteur (General Dynamics Broadband) |
FS_IOPS status update |
Approved |
|
|||
|
REP |
Rapporteur (G&D) |
FS_MAPN status update |
Revised to S1-135337 |
|
|||
|
REP |
Rapporteur (G&D) |
FS_MAPN status update |
Approved |
Revision of S1-135154.
No presentation |
|||
|
REP |
Rapporteur (Intel) |
FS_CSIPTO status update |
Approved |
|
|||
|
REP |
Rapporteur (KPN) |
FS_eICBD status update |
Approved |
|
|||
|
REP |
Rapporteur (US DoC) |
MCPTToLTE status update |
Approved |
|
|||
|
REP |
Rapporteur (China Mobile) |
FS_FMSS status update |
Approved |
|
|||
|
REP |
Rapporteur (Sprint) |
FS_UC_SPOOF status update |
Withdrawn |
|
|||
|
REP |
Rapporteur (China Mobile) |
FS_ECIP status update |
Approved |
|
|||
|
REP |
Rapporteur (Qualcomm) |
FS_MBSP status update |
Revised to S1-135338 |
|
|||
|
REP |
Rapporteur (Qualcomm) |
FS_MBSP status update |
Approved |
Revision of S1-135324.
No presentation |
|||
|
REP |
Rapporteur (KPN) |
SRMMTC status update |
Approved |
|
|||
|
WG Chairman |
Proposal for handling WIDs spanning more than two releases |
Revised to S1-135248 |
To be reviewed together with S1-135096 (section 5.2) |
||||
|
Cont |
WG Chairman |
Proposal for handling WIDs spanning more than two releases |
Revised to S1-135145 |
To be reviewed together with S1-135096 (section 5.2) Revision of S1-135059. |
|||
|
Cont |
WG Chairman |
Proposal for handling WIDs spanning more than two releases |
Noted |
To be reviewed together with S1-135096 (section 5.2) Revision of S1-135059. Revision of S1-135248. |
|||
|
Cont |
WG Chairman |
SA1 output improvement proposals |
Revised to S1-135249 |
|
|||
|
Cont |
WG Chairman |
SA1 output improvement proposals |
Revised to S1-135315 |
Revision of S1-135037. |
|||
|
Cont |
WG Chairman |
SA1 output improvement proposals |
Noted |
Revision of S1-135037. Revision of S1-135249. |
|||
|
Cont |
SA WG2 Chairman |
Improved SA1-SA2 Coordination |
Noted |
For information, document submitted to SA2 as S2-134049 Late document |
|||
|
Cont |
NEC, NSN |
How to prioritize in SA1 |
Noted |
|
|||
|
No contributions to this agenda item
|
|||||||
|
2013 meetings: SA1#64 11 – 15 Nov 2013 San Francisco, USA Mega meeting
2014 meetings: SA1#65 20 – 24 Jan 2014 Taipei, Taiwan Possible joint meeting with SA2/SA3 SA1#66 12 – 16 May 2014 Sapporo, Japan Co-located with SA3 and SA5 SA1#67 18 – 22 Aug 2014 Sophia Antipolis, France Co-located with SA5 SA1#67bis 13 – 17 Oct 2014 Cancelled SA1#68 17 – 21 Nov 2014 North America Mega meeting
2015 meetings: SA1#69 02 – 06 Feb 2015 TBD SA1#70 13 – 17 Apr 2015 TBD Co-located with SA2 SA1#71 17 – 21 Aug 2015 TBD SA1#72 16 – 20 Nov 2015 TBD Mega meeting
|
|||||||
|
Elections will be held for the position of Chairman and 2 Vice Chairmen Please refer to this link for the latest list of candidates: http://www.3gpp.org/SA1-64-Elections-11-to-15-November
|
|||||||
|
No contributions to this agenda item
|
|||||||
|
Close by 16:30 on Friday
|
|||||||
16 Withdrawn documents (admin purposes only) |
|||||||
|
|
|
|
Withdrawn |
|
|||
|
|
Huawei, Orange |
Clarification of Hosting E_UTRAN Operator role |
Withdrawn |
|
|||
|
|
Huawei, Orange |
Clarification of Hosting E_UTRAN Operator role |
Withdrawn |
|
|||
|
|
Huawei, Orange |
Clarification of Hosting E_UTRAN Operator role |
Withdrawn |
|
|||
|
|
Huawei, Orange |
Clarification of Hosting E_UTRAN Operator role |
Withdrawn |
|
|||
|
|
Huawei, Orange |
Clarification of Hosting E_UTRAN Operator role |
Withdrawn |
|
|||
|
|
Giesecke & Devrient |
FS_MAPN - potential technical solution APN storage in the UICC |
Withdrawn |
|
|||
|
|
Giesecke & Devrient |
FS_MAPN - potential technical solution APN list storage in the UICC |
Withdrawn |
|
|||
|
Cont |
Intel |
[REOPS] Autonomous eNodeB Use Case |
Withdrawn |
|
|||
|
Samsung, Intel |
CSIPTO Always-on Dual PDN Connection Use Case |
Withdrawn |
|
||||
|
Cont |
Samsung, Intel |
CSIPTO On-Demand Dual PDN Connection Use Case |
Withdrawn |
|
|||
|
|
|
|
Withdrawn |
|
|||
17 Document numbers to be allocated (admin purposes only) |
|||||||
|
|
|
|
Mona to allocate |
|
|||
|
|
|
|
Mona to allocate |
|
|||
|
|
|
|
Mona to allocate |
|
|||
|
|
|
|
Unallocated |
|
|||
Contents
1.3 Previous SA1 meeting report
2 Issues for early consideration
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 GCSE_LTE: Group communication system enablers for LTE [SP-130397]
7.2 ProSe: Proximity-based services [SP-130030]
7.3 Other Rel-12 contributions
8.1 RSE: RAN Sharing Enhancements [SP-130330], includes FS_RSE [SP-110820]
8.1.1 RSE drafting session information
8.2 SEES: Service Exposure and Enablement Support [SP-130505]
8.2.1 SEES drafting session information
9.1 FS_ACDC: Application specific congestion control for data communication [SP-130415]
9.1.1 FS_ACDC drafting session information
9.2 FS_REOPS: Resilient E-UTRAN operation for Public Safety [SP-130240]
9.2.1 FS_REOPS drafting session information
9.3 FS_MAPN: Need for multiple APNs [SP-130416]
9.3.1 FS_MAPN drafting session information
9.4 FS_CSIPTO: Co-ordinated P-GW change for SIPTO [SP-130417]
9.4.1 FS_CSIPTO drafting session information
9.5 FS_eICBD: Enhancements for infrastructure based data communication between devices [SP-130418]
9.5.1 FS_eICBD drafting session information
9.6 Other Study Item contributions
10 Joint meeting on RAN sharing with SA5
11 Work planning contributions
11.2 Work Item/Study Item status update
11.3 SA1 process improvements/updates
16 Withdrawn documents (admin purposes only)
17 Document numbers to be allocated (admin purposes only)