3GPP TSG-SA WG1 Meeting #66 S1-141002
Sapporo, Japan, 12th – 16th May 2014 (revision of S1-141001)
(revision of S1-141000)
Title: Draft schedule and agenda with document allocation for for SA1#66
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 = Palace East (on 3F)
Room B: Breakout = Symphony (on 4F) – Wednesday only
|
|
Monday |
Tuesday |
Wednesday |
Thursday |
Friday |
Q0 |
08:00
08:45 |
|
Plenary: 7.5 SRMMTC 6.2 Rel-12 7.3 eWebRTCi 7.4 IOPS |
Drafting 1 (Rm A): 7.2 MCPTT ================= Drafting 2 (Rm B): 8.9 GUSH |
Drafting: 8.7 ECIP |
|
Q1 |
09:00
10:30 |
Plenary: 1. Opening 3. Report/Action Items 4. LS |
Plenary: 7.4 IOPS 8.2 FS_IOPS 8.6 FMSS |
Drafting 1 (Rm A): 7.2 MCPTT ================= Drafting 2 (Rm B): 8.6 FMSS |
Plenary: Revisions 5.2 New WIDs 4. LS 6.1 IMS_Corp2 6.2 Rel-12 7.3 eWebRTCi 8.5 eICBD |
Plenary: Revisions 5.2 New WIDs 8.7 ECIP 8.6 FMSS 7.2 MCPTT |
Q2 |
11:00
12:30 |
Plenary: 5.2 New WIDs 6.1 IMS_Corp2 9.3 SA1 process |
Plenary: 8.6 FMSS 8.9 GUSH |
Drafting 1 (Rm A): 7.2 MCPTT ================= Drafting 2 (Rm B): 8.6 FMSS |
Plenary: Revisions 8.5 eICBD 8.3 MAPN 8.8 MBSP 8.10 UC_SPOOF |
Plenary: Revisions 7.2 MCPTT 4. LS 8.3 MAPN |
|
Lunch |
|
|
|
|
|
Q3 |
14:00
15:30 |
Plenary: 7.2 MCPTT |
Plenary: 8.3 MAPN 8.4 CSIPTO |
Drafting 1 (Rm A): 7.2 MCPTT ================= Drafting 2 (Rm B): 8.7 ECIP |
Plenary: Revisions 7.2 MCPTT (results from offline discussion) 8.6 FMSS 8.9 GUSH 8.1 ACDC 7.1 SEES |
Plenary: Revisions 8.3 MAPN 8.1 ACDC 7.1 SEES 7.4 IOPS/8.2 FS_IOPS 8.5 eICBD 6.2 Rel-12 6.1 IMS_Corp2 8.4 CSIPTO 9.1 WI status update 9.2 Work plan |
Q4 |
16:00
17:30 |
Plenary: 7.2 MCPTT 7.1 SEES |
Plenary: 8.4 CSIPTO 8.5 eICBD 8.8 MBSP |
Drafting 1 (Rm A): 7.1 SEES ================= Drafting 2 (Rm B): 8.1 ACDC |
Plenary: Revisions 7.1 SEES 7.2 MCPTT (drafting) |
Plenary: 9.1 WI status update 9.2 Work plan (close by 16:30) |
Q5 |
17:45
18:30 |
Plenary: 7.1 SEES |
Plenary: 8.8 MBSP 8.10 UC_SPOOF |
Drafting 1 (Rm A): 7.4 IOPS/8.2 FS_IOPS ================= Drafting 2 (Rm B): 8.1 ACDC |
Plenary: Revisions 7.2 MCPTT (drafting) 7.4 IOPS/8.2 FS_IOPS 8.7 ECIP 8.4 CSIPTO (closed at 19:45) |
|
|
|
|
MMS 19:00 – 21:00 |
|
|
|
NOTE:
Slots scheduled based on contributions submitted
Slot allocation is a rough guideline and is subject to change during the meeting week
FS_ECIP and FS_ACDC will be treated directly in drafting
Drafting session chairs:
SEES: Antonella Napolitano (Telecom Italia)
MCPTT: Mark Younge (T-Mobile US)
FS_ACDC: Mona Mustapha (Vodafone)
IOPS: Mark Younge (T-Mobile US)
FS_GUSH: Antonella Napolitano (Telecom Italia)
FS_FMSS: Mona Mustapha (Vodafone)
FS_ECIP: 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), WP (Work Plan)
Conclusion: Agreed, Approved, Revised to S1-14xxxx, 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-14xxxx |
Source |
Title |
Agreed / Approved |
|
CR |
S1-14xxxx |
Source |
Title |
Revised to S1-14xxxx |
|
CR |
S1-14xxxx |
Source |
Title |
Noted |
|
CR |
S1-14xxxx |
Source |
Title |
Withdrawn |
|
CR |
S1-14xxxx |
Source |
Title |
Moved to section xxx |
|
CR |
S1-14xxxx |
Source |
Title |
Rejected |
|
CR |
S1-14xxxx |
Source |
Title |
Postponed |
|
CR |
S1-14xxxx |
Source |
Title |
Email Approval |
|
CR |
S1-14xxxx |
Source |
Title |
Not Handled |
|
|
S1-14xxxx |
|
|
Unallocated / Drafting |
|
AGE |
SA1 Chairman |
Draft agenda for SA1#66 |
Revised to S1-141001 |
|
||||||||
AGE |
SA1 Chairman |
Draft schedule and agenda with document allocation for for SA1#66 |
Revised to S1-141002 |
Revision of S1-141000. |
||||||||
AGE |
SA1 Chairman |
Draft schedule and agenda with document allocation for for SA1#66 |
Approved |
Revision of S1-141000. Revision of S1-141001.
No presentation |
||||||||
|
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/).
|
|
||||||||||
The report of the last meeting will be approved at the start of the meeting.
|
||||||||||||
REP |
MCC |
Draft minutes of SA1#65 |
Revised to S1-141373 |
|
||||||||
REP |
MCC |
Draft minutes of SA1#65 |
Revised to S1-141005 |
Revision of S1-141004. |
||||||||
REP |
MCC |
Draft minutes of SA1#65 |
Approved |
Revision of S1-141004. Revision of S1-141373.
No presentation |
||||||||
REP |
MCC |
2nd Draft minutes of SA1#65 |
Withdrawn |
Replaces S1-141373 |
||||||||
SA1 Delegate Guidelines available at http://www.3gpp.org/SA1-delegates-survival-guide
Draft TR/TS to SA plenary for information: delegates are encouraged to send draft TR/TS for information as soon as there is useful content to be reviewed. Draft TR/TS can be sent to SA plenary for information more than once.
|
||||||||||||
None
|
||||||||||||
For contributions to this Agenda Item, please contact the Chairman in advance of the meeting.
|
||||||||||||
REP |
SA1 Chairman |
SA1-related topics at SA#63 |
Noted |
Thank you to Antonella for presenting the SA1 items at SA plenary! Items to note: - virtualisation/SDN: no consensus for an SA-wide study, decision to be made in June SA - ETSI business trunking specs transferred to 3GPP, SA1 to take care of TS 181 019 into TS 22.519 - I-WLAN is no longer maintained, handling of documentation to be decided in June SA |
||||||||
NFV and SDN |
||||||||||||
CC |
SP-140160 (Vodafone) |
LS on 3GPP activities on Network Functions Virtualisation |
Noted |
SA5 to start some work on management aspects of virtualised 3GPP functions. The scope of a potential 3GPP study on architecture and system level impacts to be assessed in June SA.
No action required |
||||||||
CC |
S2-141481 (Ericsson) |
LS on co-ordination of response LS to ITU JCA-SDN |
Noted |
SA2 asks SA to consider responding to ITU JCA-SDN to provide information on ongoing work on SDN and NFV in 3GPP . No action required |
||||||||
Transfer of ETSI business trunking specifications |
||||||||||||
CC |
CP-140187 (Alcatel-Lucent) |
LS on Transfer of ETSI business trunking specifications |
Noted |
CT indicates that it will take care of ETSI business trunking specifications but that TS 181 019 (Requirements) needs to be transferred to SA1.
Action required. See agenda item 6.1. |
||||||||
CC |
SP-140171 (Alcatel-Lucent) |
Response LS on Transfer of ETSI business trunking specifications |
Noted |
3GPP will transfer the business trunking specification from ETSI to 3GPP.
No action required. |
||||||||
Maintenance of I-WLAN |
||||||||||||
CC |
S2-140554 (Motorola Mobility) |
LS on Maintenance of I-WLAN Solution |
Noted |
SA2 proposes to stop maintaining I-WLAN aspects and provides several reasons. If SA agrees then other WGs need to assess impact to their specifications and that external bodies would need to be notified.
(SA1 impacted spec is 22.234) No action required |
||||||||
CC |
SP-140149 (Broadcom) |
Reply LS on Maintenance of I-WLAN Solution |
Noted |
SA agrees to stop maintaining I-WLAN aspects from Rel-12 onwards. SA to provide guidance on handling documentation in June.
No action required |
||||||||
CR |
Alcatel-Lucent |
22.278 v12.4.0: I-WLAN clean up in 22.278 |
Noted |
WI code TEI12 Rel-12 CR0200R- Cat C Moved from section 6.2 |
||||||||
CR |
Alcatel-Lucent |
22.011 v12.1.0: I-WLAN clean up in 22.011 |
Noted |
WI code TEI12 Rel-12 CR0472R- Cat C Moved from section 6.2 |
||||||||
Removal of option to subscribe for a notification of diversion occurrence |
||||||||||||
TO |
C1-140742 (BlackBerry) |
LS on “Removal of option to subscribe for a notification of diversion occurrence” |
Noted, answer in S1-141382 |
Due to problems completing the work in IETF, CT1 has removed the option to subscribe for a notification of a diversion occurrence.
Action: remove this option from the current release of MMtel |
||||||||
Ericsson |
Reply LS on Removal of option to subscribe for a notification of diversion occurrence |
Revised to S1-141261 |
Response to: LS (C1-140742/S1-141200) on Removal of option to subscribe for a notification of diversion occurrence” from WG CT1 |
|||||||||
LS OUT |
Ericsson |
Reply LS on Removal of option to subscribe for a notification of diversion occurrence |
Revised to S1-141382 |
Response to: LS (C1-140742/S1-141200) on Removal of option to subscribe for a notification of diversion occurrence” from WG CT1 Revision of S1-141024. |
||||||||
LS OUT |
Ericsson |
Reply LS on Removal of option to subscribe for a notification of diversion occurrence |
Approved |
Response to: LS (C1-140742/S1-141200) on Removal of option to subscribe for a notification of diversion occurrence” from WG CT1 Revision of S1-141024. Revision of S1-141261.
No presentation |
||||||||
CR |
Ericsson |
22.173 v8.9.0: Removal of CDIVN service |
Agreed |
WI code TISMMTEL-R8 Rel-8 CR0094R- Cat F |
||||||||
CR |
Ericsson |
22.173 v9.6.0: Removal of CDIVN service |
Agreed |
WI code TISMMTEL-R8 Rel-9 CR0095R- Cat A |
||||||||
CR |
Ericsson |
22.173 v10.5.0: Removal of CDIVN service |
Agreed |
WI code TISMMTEL-R8 Rel-10 CR0096R- Cat A |
||||||||
CR |
Ericsson |
22.173 v11.5.0: Removal of CDIVN service |
Agreed |
WI code TISMMTEL-R8 Rel-11 CR0097R- Cat A |
||||||||
CR |
Ericsson |
22.173 v12.5.0: Removal of CDIVN service |
Agreed |
WI code TISMMTEL-R8 Rel-12 CR0098R- Cat A |
||||||||
SEES |
||||||||||||
TO |
OMA-LS_998 |
LS To 3GPP SA1 about SEES work item |
Noted, answer in S1-141527 |
OMA asks for the latest status of SEES and next steps. OMA also suggests co-operation on any future work on APIs and asks SA1 to send related requirements so they can develop the APIs.
Response required. |
||||||||
LS OUT |
Huawei |
Draft Reply to OMA about SEES work item |
Revised to S1-141383 |
Response to: LS to 3GPP SA1 about SEES work item |
||||||||
LS OUT |
Huawei |
Draft Reply to OMA about SEES work item |
Revised to S1-141527 |
Response to: LS to 3GPP SA1 about SEES work item Revision of S1-141067. For SEES drafting sesssion |
||||||||
LS OUT |
Huawei |
Draft Reply to OMA about SEES work item |
Approved |
Response to: LS to 3GPP SA1 about SEES work item Revision of S1-141067. For SEES drafting sesssion Revision of S1-141383.
No presentation |
||||||||
MTC Device ID for LI |
||||||||||||
TO |
SA3LI14_009r1 (BT) |
MTC Device Identification for LI |
Noted, answer in S1-141384 |
SA3LI asks SA1 to update TS 22.368 to make it explicitly clear that MTC MEs are required to fully support normal ME numbering and identification requirements.
Action required |
||||||||
CC |
C4-140714 (Huawei) |
Reply LS on MTC Device Identification for LI |
Noted |
CT4 informs SA3-LI that enhancing IMEI to cater for larger number of devices will be investigated in future.
No action required. |
||||||||
LS OUT |
Qualcomm |
Reply LS on MTC Device Identification for LI |
Revised to S1-141384 |
Response to: LS (S1-141220) on MTC Device Identification for LI from WGSA 3LI (SA3LI14_009r1) |
||||||||
LS OUT |
Qualcomm |
Reply LS on MTC Device Identification for LI |
Approved |
Response to: LS (S1-141220) on MTC Device Identification for LI from WGSA 3LI (SA3LI14_009r1) Revision of S1-141260. |
||||||||
MCPTT |
||||||||||||
TO |
TCCE (14)000043 |
reply to 3GPP Liaison Statement: Mission-critical Push to Talk over LTE |
Noted |
ETSI TCCE provides their User Requirements Specification for consideration for MCPTT.
Action required |
||||||||
TO |
OMA-LS_1003 (AT&T, Motorola Solutions) |
LS to 3GPP TSG SA, SA1 and SA2 on MCPTT requirements |
Noted, answer in S1-141385 |
OMA provides their Requirements Document for consideration for MCPTT.
Action required. |
||||||||
LS OUT |
UK Home Office |
LS on MCPTT Requirements |
Revised to S1-141530 |
Response to: LS (S1-141227) on MCPTT Requirements from OMA (OMA-LS_1003) |
||||||||
LS OUT |
UK Home Office |
LS on MCPTT Requirements |
Revised to S1-141590 |
Response to: LS (S1-141227) on MCPTT Requirements from OMA (OMA-LS_1003) Answer to S1-141227. Revision of S1-141385. |
||||||||
LS OUT |
UK Home Office |
LS on MCPTT Requirements |
Approved |
Response to: LS (S1-141227) on MCPTT Requirements from OMA (OMA-LS_1003) Answer to S1-141227. Revision of S1-141385. Revision of S1-141530.
No presentation |
||||||||
TO |
TIA TR88-14-024 (Harris, Motorola Solutions) |
TD SP-130727 - LS on Mission Critical Push To Talk over LTE |
Noted |
TIA provides advanced notice of a new document on Priority and QoS Control that they plan to submit the the August SA1 meeting for MCPTT.
No action required |
||||||||
TO |
TCCE 04(14)000035 (UK Home Office) |
LS on Analysis on the scope of GCSE and the PTT Application. |
Moved to section 7.2 |
|
||||||||
GCSE_LTE |
||||||||||||
TO |
S2-140846 (Vodafone) |
LS on GCSE QCIs and connected mode DRX |
Noted |
SA2 indicates that new QCIs will be needed and ask other WGs for feedback.
Action/response required. |
||||||||
CC |
C1-141513 (NSN) |
Reply LS on GCSE QCIs and connected mode DRX |
Noted |
CT1 indicates that a new QCI will impact CT1 specs and asks why the new QCI has higher priority compared with IMS signalling.
No action required |
||||||||
CC |
R3-140950 (Samsung) |
Reply LS on GCSE QCIs and connected mode DRX |
Noted |
RAN3 feedback on SA2 proposal.
No action required |
||||||||
Other topics |
||||||||||||
TO |
S1-140146 / oneM2M-TP-2013-0382R02 |
LS to 3GPP on support of alternate device triggering scheme for non-SMS capable devices |
Noted, answer in S1-141386 |
Postponed from SA1#65 oneM2M asks SA1 to consider requirements for non-SMS MTC triggering.
Action/response required. |
||||||||
LS OUT |
NEC |
LS to 3GPP on support of alternate device triggering scheme for non-SMS capable devices |
Approved |
Postponed from SA1#65 oneM2M asks SA1 to consider requirements for non-SMS MTC triggering.
Action/response required. Answer to S1-141224. |
||||||||
TO |
MSG(14)AdH012r3 (Qualcomm?) |
Migration of eCall Transport |
Postponed |
ETSI MSG asks for feedback on their draft TR Migration of eCall Transport.
Action required |
||||||||
CC |
S2-140449 (Ericsson) |
LS reply on Next hop policy rule use case accepted into WT-300 |
Noted |
SA2 answers questions from BBF related to policy control of the Next hop for a particular service in the IP Edge and how this is supported in Rel-12 PCC specs. SA2 also informs BBF about the SA1 study FS_FMSS.
No action required |
||||||||
CC |
S2-140565 (NEC) |
Reply LS on interaction of oneM2M with Underlying Networks |
Noted |
SA2 provides oneM2M summary of Rel-12 MTCe work item. SA2 also explains that Tsp is the only available reference point to exchange information with external service providers/applications and invites oneM2M to work with SA1 if functionality other than provided by Tsp is needed.
No action required |
||||||||
CC |
S3-131155 (Ericsson) |
Reply LS on LS on interactions of oneM2M with Underlying Networks |
Noted |
SA3 asks oneM2M questions regarding 2 security features from the original incoming LS from oneM2M.
No action required |
||||||||
CC |
S2-140568 (Alcatel-Lucent, Intel) |
LS reply on discovery message size |
Noted |
SA2 provides RAN2 tentative information about the possible content of the discovery message.
No action required |
||||||||
CC |
S3-140226 (Qualcomm) |
Reply to LS on discovery message size |
Noted |
SA3 has not concluded their work and cannot provide any information to RAN2 related to the discovery message content at this time.
No action required |
||||||||
CC |
S2-140494 (Qualcomm) |
Reply LS on ProSe Lawful Interception |
Noted |
SA2 replies to RAN that SA3-LI is responsible for working on lawful intercept aspects.
No action required |
||||||||
CC |
R2-141005 (NTT DOCOMO) |
LS on MMTEL and SMS prioritization |
Noted |
RAN2 informs CT1 their proposed solution for MMTEL/SMS prioritisation and asks CT1 to investigate changes to CT1 specs.
No action required |
||||||||
CC |
C1-141512 (Ericsson) |
Reply LS on MMTEL and SMS prioritization |
Noted |
CT1 informs RAN2 that they will work on a solution but has not agreed one yet.
No action required |
||||||||
CC |
S2-140419 (NSN) |
LS on UE requirements for PSAP callback |
Noted |
SA2 informs CT1 that requirements for special handling of PSAP call back have been removed from Rel-11.
No action required |
||||||||
CC |
S2-140510 (Huawei) |
Reply to Wi-Fi Alliance on LS on Signaling Optimization |
Noted |
SA2 informs WBA that no action can be taken because the text is not available.
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) |
||||||||||||
WID |
China Mobile, Huawei |
Proposed WID for Flexible Mobile Service Steering (FMSS) |
Revised to S1-141375 |
Comment: Section 2.0 – this is a "feature" not "work task", so section 2.2 should be completed and not section 2.4. Section 2.3 second table should cross "Stage 1". Timescale target "for information" and "approval" should be 3 months apart. 4 supporting companies required. |
||||||||
WID |
China Mobile, Huawei |
Proposed WID for Flexible Mobile Service Steering (FMSS) |
Revised to S1-141393 |
Revision of S1-141151. |
||||||||
WID |
China Mobile, Huawei |
Proposed WID for Flexible Mobile Service Steering (FMSS) |
Noted |
Revision of S1-141151. Revision of S1-141375. |
||||||||
WID |
NTT DOCOMO, et al |
WID proposal for Application specific Congestion control for Data Communication (ACDC) |
Revised to S1-141523 |
|
||||||||
WID |
NTT DOCOMO, et al |
WID proposal for Application specific Congestion control for Data Communication (ACDC) |
Agreed |
Revision of S1-141170. |
||||||||
Cont |
Qualcomm Incorporated, NTT DOCOMO |
Consolidation of Potential Requirements from TR 22.806 Study to Normative Text |
Revised to S1-141342 |
Moved from section 8.1 For ACDC drafting session: The session found this document, especially the last two steps of analysis, contains useful information in order to trace each requirement back to each use case, and agreed to keep the content in TR, e.g. in section 7. It was also recommended to reformulate the content so that it fits to a template that we are trying to use now SA1-wide. |
||||||||
Cont |
Qualcomm Incorporated, NTT DOCOMO |
Consolidation of Potential Requirements from TR 22.806 Study to Normative Text |
Agreed |
Moved from section 8.1 For ACDC drafting session: The session found this document, especially the last two steps of analysis, contains useful information in order to trace each requirement back to each use case, and agreed to keep the content in TR, e.g. in section 7. It was also recommended to reformulate the content so that it fits to a template that we are trying to use now SA1-wide. Revision of S1-141109. |
||||||||
Cont |
NTT DOCOMO, Qualcomm Incorporated |
Proposed Text for ACDC Consolidated Requirements |
Revised to S1-141582 |
|
||||||||
Cont |
NTT DOCOMO, Qualcomm Incorporated |
Proposed Text for ACDC Consolidated Requirements |
Agreed |
Revision of S1-141565.
Agreed to be added to the TR No presentation |
||||||||
CR |
NTT DOCOMO, Qualcomm Incorporated, Sony Mobile Communication, NTC, Hitachi, LG Electronics |
22.011 v12.1.0: Requirements for ACDC |
Revised to S1-141340 |
WI code ACDC Rel-13 CR0203R- Cat B Comment: Suggest title is "Access control mechanism for operator-identified applications" |
||||||||
CR |
NTT DOCOMO, Qualcomm Incorporated, Sony Mobile Communication, NTC, Hitachi, LG Electronics |
22.011 v12.1.0: Requirements for ACDC |
Revised to S1-141306 |
WI code ACDC Rel-13 CR0203R- Cat B Revision of S1-141171. For ACDC drafting session: The session agreed to modify (1) a text to be “… ranked in order of importance” and (2) a NOTE to be “…and the categorization is outside of the scope of 3GPP.” The session discussed how many categories operators need. There were different views; 8 or 2. The session further discussed how we proceed in case we cannot decide the number in this meeting. An option is to approve CR now saying “multiple categories”. Another option is to put on hold CR itself. The session decided to escalate this to the SA1 plenary. |
||||||||
CR |
NTT DOCOMO, Qualcomm Incorporated, Sony Mobile Communication, NTC, Hitachi, LG Electronics |
22.011 v12.1.0: Requirements for ACDC |
Agreed |
WI code ACDC Rel-13 CR0203R- Cat B Revision of S1-141171. For ACDC drafting session: The session agreed to modify (1) a text to be “… ranked in order of importance” and (2) a NOTE to be “…and the categorization is outside of the scope of 3GPP.” The session discussed how many categories operators need. There were different views; 8 or 2. The session further discussed how we proceed in case we cannot decide the number in this meeting. An option is to approve CR now saying “multiple categories”. Another option is to put on hold CR itself. The session decided to escalate this to the SA1 plenary. Revision of S1-141340. |
||||||||
WID |
Intel; Samsung; Interdigital; Sony Mobile Communications; T-Mobile USA; KPN; China Mobile; Acer; China Telecom |
Proposed WID for Co-ordinated P-GW change for SIPTO (CSIPTO) |
Revised to S1-141300 |
Moved from section 8.4 Comment: section 10, remove line for new specification (TR xyz) |
||||||||
WID |
Intel; Samsung; Interdigital; Sony Mobile Communications; T-Mobile USA; KPN; China Mobile; Acer; China Telecom |
Proposed WID for Co-ordinated P-GW change for SIPTO (CSIPTO) |
Revised to S1-141301 |
Moved from section 8.4 Comment: section 10, remove line for new specification (TR xyz) Revision of S1-141143. |
||||||||
WID |
Intel; Samsung; Interdigital; Sony Mobile Communications; T-Mobile USA; KPN; China Mobile; Acer; China Telecom |
Proposed WID for Co-ordinated P-GW change for SIPTO (CSIPTO) |
Revised to S1-141566 |
Moved from section 8.4 Comment: section 10, remove line for new specification (TR xyz) Revision of S1-141143. Revision of S1-141300. |
||||||||
WID |
Intel; Samsung; Interdigital; Sony Mobile Communications; T-Mobile USA; KPN; China Mobile; Acer; China Telecom |
Proposed WID for Co-ordinated P-GW change for SIPTO (CSIPTO) |
Agreed |
Moved from section 8.4 Revision of S1-141143. Revision of S1-141300. Revision of S1-141301.
No presentation |
||||||||
Cont |
Intel; Samsung; Sony Mobile Communications; T-Mobile USA; Interdigital; KPN; China Mobile; Acer; China Telecom |
Discussion Paper - Draft CR to add CSIPTO to TS22.101 |
Noted |
Moved from section 8.4 |
||||||||
WID |
Qualcomm Incorporated |
New WID for ProSe Maintenance (ProSeM) |
Revised to S1-141394 |
Comment: Objectives should include a high-level list of items not implemented in Rel-12 that will be considered for Rel-13. 4 supporting companies required. |
||||||||
WID |
Qualcomm Incorporated |
New WID for ProSe Maintenance (ProSeM) |
Revised to S1-141569 |
Revision of S1-141085. |
||||||||
WID |
Qualcomm Incorporated |
New WID for ProSe Maintenance (ProSeM) |
Agreed |
Revision of S1-141085. Revision of S1-141394.
No presentation |
||||||||
Cont |
Qualcomm Incorporated |
Review of ProSe stage-1 fulfilment (TS 22.278) |
Revised to S1-141389 |
|
||||||||
Cont |
Qualcomm Incorporated |
Review of ProSe stage-1 fulfilment (TS 22.278) |
Revised to S1-141539 |
Revision of S1-141086. |
||||||||
Cont |
Qualcomm Incorporated |
Review of ProSe stage-1 fulfilment (TS 22.278) |
Agreed |
Revision of S1-141086. Revision of S1-141389. |
||||||||
WID |
Rapporteur (NSN) |
Rel-13 Maintenance WI for Group Communication System Enablers for LTE |
Revised to S1-141395 |
|
||||||||
WID |
Rapporteur (NSN) |
Rel-13 Maintenance WI for Group Communication System Enablers for LTE |
Revised to S1-141571 |
Revision of S1-141233. |
||||||||
WID |
Rapporteur (NSN) |
Rel-13 Maintenance WI for Group Communication System Enablers for LTE |
Agreed |
Revision of S1-141233. Revision of S1-141395.
No presentation |
||||||||
WID |
Alcatel-Lucent |
New WID for VoLTE Paging Distinction |
Revised to S1-141390 |
Comment: 4 supporting companies required. |
||||||||
WID |
Alcatel-Lucent |
New WID for VoLTE Paging Distinction |
Revised to S1-141524 |
Comment: 4 supporting companies required. Revision of S1-141241. |
||||||||
WID |
Alcatel-Lucent |
New WID for VoLTE Paging Distinction |
Revised to S1-141573 |
Comment: 4 supporting companies required. Revision of S1-141241. Revision of S1-141390. |
||||||||
WID |
Alcatel-Lucent |
New WID for VoLTE Paging Distinction |
Agreed |
Comment: 4 supporting companies required. Revision of S1-141241. Revision of S1-141390. Revision of S1-141524.
No presentation |
||||||||
CR |
Alcatel-Lucent, Verizon, Oracle |
22.228 v12.6.0: Requirements to support differentiated paging for VoLTE |
Revised to S1-141391 |
WI code VoLTE_PPD Rel-13 CR0199R- Cat B Comment: Suggest title changed to "Support for differentiated paging for VoLTE" |
||||||||
CR |
Alcatel-Lucent, Verizon, Oracle |
22.228 v12.6.0: Requirements to support differentiated paging for VoLTE |
Revised to S1-141575 |
WI code VoLTE_PPD Rel-13 CR0199R- Cat B Comment: Suggest title changed to "Support for differentiated paging for VoLTE" Revision of S1-141242. |
||||||||
CR |
Alcatel-Lucent, Verizon, Oracle |
22.228 v12.6.0: Requirements to support differentiated paging for VoLTE |
Agreed |
WI code VoLTE_PPD Rel-13 CR0199R- Cat B Comment: Suggest title changed to "Support for differentiated paging for VoLTE" Revision of S1-141242. Revision of S1-141391.
No presentation |
||||||||
CR |
Alcatel-Lucent, Verizon, Oracle |
22.278 v12.4.0: EPS Requirement to support differentiated paging for VoLTE |
Revised to S1-141392 |
WI code VoLTE_PPD Rel-13 CR0201R- Cat B Comment: Suggest title changed to "EPS support for differentiated paging for VoLTE" |
||||||||
CR |
Alcatel-Lucent, Verizon, Oracle |
22.278 v12.4.0: EPS Requirement to support differentiated paging for VoLTE |
Revised to S1-141576 |
WI code VoLTE_PPD Rel-13 CR0201R- Cat B Comment: Suggest title changed to "EPS support for differentiated paging for VoLTE" Revision of S1-141243. |
||||||||
CR |
Alcatel-Lucent, Verizon, Oracle |
22.278 v12.4.0: EPS Requirement to support differentiated paging for VoLTE |
Agreed |
WI code VoLTE_PPD Rel-13 CR0201R- Cat B Comment: Suggest title changed to "EPS support for differentiated paging for VoLTE" Revision of S1-141243. Revision of S1-141392.
No presentation |
||||||||
Orange |
Discussion Paper SMS-outbox update on mobile |
Noted |
Moved from section 7.6 |
|||||||||
WID |
Orange |
Proposed new WID on SMS-outbox update on Mobile |
Revised to S1-141525 |
Comment: Section 2.3 second table should cross "Stage 1". 4 supporting companies required. |
||||||||
WID |
Orange |
Proposed new WID on SMS-outbox update on Mobile |
Noted |
Comment: Section 2.3 second table should cross "Stage 1". 4 supporting companies required. Revision of S1-141185. |
||||||||
CR |
Orange |
22.101 v13.2.0: SMS-outbox update on Mobile |
Noted |
WI code SMS_OBUD Rel-13 CR0474R- Cat B Moved from section 7.6 |
||||||||
Cont |
III, ITRI |
Discussion on Long Range Cell Operation for Public Safety |
Noted |
|
||||||||
WID |
III, ITRI |
WID proposal: Long Range Cell Operation for Public Safety (LCOPS) |
Revised to S1-141396 |
Comment: Section 2.3 second table should cross "Stage 1". Only one Rapporteur is allowed. 4 supporting companies required. |
||||||||
WID |
III, ITRI |
WID proposal: Long Range Cell Operation for Public Safety (LCOPS) |
Revised to S1-141536 |
Comment: Section 2.3 second table should cross "Stage 1". Only one Rapporteur is allowed. 4 supporting companies required. Revision of S1-141013. |
||||||||
WID |
III, ITRI |
WID proposal: Long Range Cell Operation for Public Safety (LCOPS) |
Noted |
Comment: Section 2.3 second table should cross "Stage 1". Only one Rapporteur is allowed. 4 supporting companies required. Revision of S1-141013. Revision of S1-141396. |
||||||||
Cont |
III, ITRI |
Discussion on Support Long Range Cell Operation for ProSe |
Noted |
|
||||||||
CR |
III, ITRI |
22.278 v12.4.0: Support Long Range Cell Operation for ProSe |
Noted |
WI code TEI13 Rel-13 CR0199Rx Cat B Comment: On cover page, WI code is "LCOPS" (not TEI13), "rev" is "-" (not x), "Clauses affected" is incorrect. In body text, proposed text should be added using revision marks, existing text in the affected clause should be shown to show where new text sits in relation to existing requirements. |
||||||||
Cont |
III, ITRI |
Discussion on Support Long Range Cell Operation for GCSE |
Noted |
|
||||||||
CR |
III, ITRI |
22.468 v12.0.0: Support Long Range Cell Operation for GCSE |
Noted |
WI code TEI13 Rel-13 CR0002Rx Cat B Comment: On cover page, WI code is "LCOPS" (not TEI13), "rev" is "-" (not x), "Clauses affected" is incorrect. In body text, proposed text should be added using revision marks, existing text in the affected clause should be shown to show where new text sits in relation to existing requirements. |
||||||||
WID |
China Telecom |
New study on Requirements for Virtualization of Mobile Networks (FS_RVMN) |
Noted |
Comment: Timescale should be 2014 or later. Timescale target "for information" and "approval" should be 3 months apart. 4 supporting companies required. |
||||||||
Cont |
China Telecom |
Mobile SDN perspective |
Noted |
|
||||||||
WID |
China Unicom |
Study on Enhancements to User Location Reporting Support |
Revised to S1-141379 |
Comment: section 2.2 should not be populated. In objectives, remove phrase "but are not limited to" |
||||||||
WID |
China Unicom |
Study on Enhancements to User Location Reporting Support |
Revised to S1-141562 |
Revision of S1-141172. |
||||||||
WID |
China Unicom |
Study on Enhancements to User Location Reporting Support |
Revised to S1-141577 |
Revision of S1-141172. Revision of S1-141379. |
||||||||
WID |
China Unicom |
Study on Enhancements to User Location Reporting Support |
Agreed |
Revision of S1-141172. Revision of S1-141379. Revision of S1-141562.
No presentation |
||||||||
Cont |
China Unicom |
Discussion on Enhancements to User Location Reporting Support |
Noted |
|
||||||||
Cont |
China Unicom |
Discussion on Enhancements to User Location Reporting Support |
Withdrawn |
Revision of S1-141173. |
||||||||
WID |
KDDI |
New WID for Feasibility Study on Control of Applications when Third party Servers encounter difficulties |
Revised to S1-141397 |
Comment: 4 supporting companies required. |
||||||||
WID |
KDDI |
New WID for Feasibility Study on Control of Applications when Third party Servers encounter difficulties |
Revised to S1-141526 |
Comment: 4 supporting companies required. Revision of S1-141182. |
||||||||
WID |
KDDI |
New WID for Feasibility Study on Control of Applications when Third party Servers encounter difficulties |
Revised to S1-141579 |
Comment: 4 supporting companies required. Revision of S1-141182. Revision of S1-141397. |
||||||||
WID |
KDDI |
New WID for Feasibility Study on Control of Applications when Third party Servers encounter difficulties |
Agreed |
Comment: 4 supporting companies required. Revision of S1-141182. Revision of S1-141397. Revision of S1-141526.
No presentation |
||||||||
6.1 IMS_Corp2 (Rel-12): Transfer of ETSI business trunking specifications [SP-140170] |
||||||||||||
Work status prior to this meeting: TS 22.519 allocated Target completion date: SA#64 (06/2014) Percentage completion: 0%
|
||||||||||||
Alcatel-Lucent |
Summary of actions made to create version 0.0.1 of 3GPP TS 22.519 |
Noted |
|
|||||||||
TS |
Rapporteur |
Draft 3GPP TS 22.519 |
Revised to S1-141398 |
|
||||||||
TS |
Rapporteur |
Draft 3GPP TS 22.519 |
Agreed |
Revision of S1-141149. Agreed as the basis for future contributions Agreed to be sent for information |
||||||||
CP |
Raporteur |
Cover page |
Agreed |
|
||||||||
6.2 Other Rel-12 and earlier contributions |
||||||||||||
CR |
KPN (Rapporteur) |
22.368 v12.3.0: End of Release 12 alignment of M2M service requirements |
Revised to S1-141427 |
WI code MTCe-SRM Rel-12 CR0153R- Cat F |
||||||||
CR |
KPN (Rapporteur) |
22.368 v12.3.0: End of Release 12 alignment of M2M service requirements |
Agreed |
WI code MTCe-SRM Rel-12 CR0153R- Cat F Revision of S1-141245. |
||||||||
CR |
Orange |
22.228 v12.6.0: Clarification on the use of codecs by the WebRTC IMS client |
Revised to S1-141490 |
WI code IMS_WebRTC Rel-12 CR0203R- Cat F |
||||||||
CR |
Orange |
22.228 v12.6.0: Clarification on the use of codecs by the WebRTC IMS client |
Revised to S1-141599 |
WI code IMS_WebRTC Rel-12 CR0203R- Cat F Revision of S1-141129. |
||||||||
CR |
Orange |
22.228 v12.6.0: Clarification on the use of codecs by the WebRTC IMS client |
Agreed |
WI code IMS_WebRTC Rel-12 CR0203R- Cat F Revision of S1-141129. Revision of S1-141490.
No presentation |
||||||||
CR |
Huawei, Alcatel-Lucent |
22.228 v12.6.0: Removable of requirements & use cases to align IMS WebRTC stage 1 with stage 2 |
Revised to S1-141428 |
WI code IMS_WebRTC Rel-12 CR0200R- Cat F |
||||||||
CR |
Huawei, Alcatel-Lucent |
22.228 v12.6.0: Alignment of IMS WebRTC stage 1 with stage 2 |
Agreed |
WI code IMS_WebRTC Rel-12 CR0200R- Cat F Revision of S1-141154.
No presentation |
||||||||
CR |
Huawei, Alcatel-Lucent |
22.228 v12.6.0: Alignment of IMS WebRTC stage 1 Authentication requirements with stage 2 |
Revised to S1-141429 |
WI code IMS_WebRTC Rel-12 CR0201R- Cat F |
||||||||
CR |
Huawei, Alcatel-Lucent |
22.228 v12.6.0: Alignment of IMS WebRTC stage 1 Authentication requirements with stage 2 |
Agreed |
WI code IMS_WebRTC Rel-12 CR0201R- Cat F Revision of S1-141155. |
||||||||
CR |
Alcatel-Lucent |
22.278 v12.4.0: I-WLAN clean up in 22.278 |
Moved to section 4 |
WI code TEI12 Rel-12 CR0200R- Cat C |
||||||||
CR |
Alcatel-Lucent |
22.011 v12.1.0: I-WLAN clean up in 22.011 |
Moved to section 4 |
WI code TEI12 Rel-12 CR0472R- Cat C |
||||||||
7 Rel-13 Work Item contributions |
||||||||||||
7.1 SEES: Service Exposure and Enablement Support [SP-130505] |
||||||||||||
Work status prior to this meeting: Draft TR 22.853 v1.0.0 was sent to SA plenary for information at Taipei SA1#65 Target completion date: SA#65 (09/2014) Percentage completion: 60%s
|
||||||||||||
TR |
KPN, MCC |
Proposed editorial clean-up to TR 22853v100 |
Revised to S1-141281 |
Late document Proposes editorial changes, except: - clause 4.1.2.1: sentence with "must" rewritten as informative text - add to references to the reference section. For SEES drafting session |
||||||||
TR |
KPN, MCC |
Proposed editorial clean-up to TR 22853v100 |
Agreed |
Proposes editorial changes, except: - clause 4.1.2.1: sentence with "must" rewritten as informative text - add to references to the reference section. For SEES drafting session Revision of S1-141257. Agreed in SEES drafting session Agreed as the basis for contributions at this meeting |
||||||||
Ericsson |
Update of the Connection Patterns use case |
Revised to S1-141420 |
|
|||||||||
Cont |
Ericsson |
Update of the Connection Patterns use case |
Revised to S1-141282 |
Revision of S1-141116. For SEES drafting session |
||||||||
Cont |
Ericsson |
Update of the Connection Patterns use case |
Agreed |
Revision of S1-141116. For SEES drafting session Revision of S1-141420. Agreed to be added to the TR |
||||||||
Cont |
Huawei, NEC, KPN |
Clarification of background traffic use case |
Revised to S1-141421 |
|
||||||||
Cont |
Huawei, NEC, KPN |
Clarification of background traffic use case |
Agreed |
Revision of S1-141042. For SEES drafting session Agreed in SEES drafting session Agreed to be added to the TR |
||||||||
Cont |
Huawei, KPN |
Complete “FFS” on Presence/LCS and reason |
Revised to S1-141422 |
|
||||||||
Cont |
Huawei, KPN |
Complete “FFS” on Presence/LCS and reason |
Revised to S1-141283 |
Revision of S1-141048. For SEES drafting session |
||||||||
Cont |
Huawei, KPN |
Complete “FFS” on Presence/LCS and reason |
Agreed |
Revision of S1-141048. For SEES drafting session Revision of S1-141422. Agreed in SEES drafting session Agreed to be added to the TR |
||||||||
Cont |
Huawei, KPN, China Mobile |
Generic requirements on service/capability exposure towards third parties |
Revised to S1-141423 |
|
||||||||
Cont |
Huawei, KPN, China Mobile |
Generic requirements on service/capability exposure towards third parties |
Revised to S1-141284 |
Revision of S1-141043. For SEES drafting session |
||||||||
Cont |
Huawei, KPN, China Mobile |
Generic requirements on service/capability exposure towards third parties |
Revised to S1-141551 |
Revision of S1-141043. For SEES drafting session Revision of S1-141423. Agreed in SEES drafting session |
||||||||
Cont |
Huawei, KPN, China Mobile |
Generic requirements on service/capability exposure towards third parties |
Agreed |
Revision of S1-141043. For SEES drafting session Revision of S1-141423. Agreed in SEES drafting session Revision of S1-141284.
Agreed to be added to the TR No presentation |
||||||||
Cont |
China Unicom |
Use Case on QoS Choice Exposure |
Revised to S1-141425 |
For SEES drafting session |
||||||||
Cont |
China Unicom |
Use Case on Terminal Characteristics Exposure |
Revised to S1-141424 |
|
||||||||
Cont |
China Unicom |
Use Case on Terminal Characteristics Exposure |
Revised to S1-141285 |
Revision of S1-141118. For SEES drafting session |
||||||||
Cont |
China Unicom |
Use Case on Terminal Characteristics Exposure |
Withdrawn |
Revision of S1-141118. For SEES drafting session Revision of S1-141424. |
||||||||
Cont |
Huawei, NEC, KPN, China Mobile |
Consolidation of SEES service/capabilities |
Revised to S1-141425 |
|
||||||||
Cont |
Huawei, NEC, KPN, China Mobile |
Consolidation of SEES service/capabilities |
Revised to S1-141286 |
Revision of S1-141066 and S1-141117. For SEES drafting session |
||||||||
Cont |
Huawei, NEC, KPN, China Mobile |
Consolidation of SEES service/capabilities |
Revised to S1-141545 |
Revision of S1-141066 and S1-141117. For SEES drafting session Revision of S1-141425. |
||||||||
Cont |
Huawei, NEC, KPN, China Mobile |
Consolidation of SEES service/capabilities |
Agreed |
Revision of S1-141066 and S1-141117. For SEES drafting session Revision of S1-141425. Revision of S1-141286. Agreed to be added to the TR |
||||||||
Cont |
KPN, Huawei, NEC, China Mobile |
Proposed SEES conclusion |
Revised to S1-141552 |
For SEES drafting session |
||||||||
Cont |
KPN, Huawei, NEC, China Mobile |
Proposed SEES conclusion |
Agreed |
For SEES drafting session Revision of S1-141121.
Agreed to be added to the TR No presentation |
||||||||
CR |
Huawei, NEC, KPN |
22.115 v13.0.0: Exposure of charging to 3rd party |
Revised to S1-141258 |
WI code SEES Rel-13 CR0073R- Cat B Comment: Re-write text in "reason for change" to describe why the changes are introduced (current text is not suitable) |
||||||||
CR |
Huawei, NEC, KPN |
22.115 v13.0.0: Exposure of charging to 3rd party |
Revised to S1-141302 |
WI code SEES Rel-13 CR0073R- Cat B Comment: Re-write text in "reason for change" to describe why the changes are introduced (current text is not suitable) Revision of S1-141122. |
||||||||
CR |
Huawei, NEC, KPN |
22.115 v13.0.0: Exposure of charging to 3rd party |
Noted |
WI code SEES Rel-13 CR0073R- Cat B Revision of S1-141122. Revision of S1-141258. |
||||||||
CR |
Huawei, KPN, NEC |
22.101 v13.2.0: Exposure of network service and capabilities to 3rd party |
Revised to S1-141259 |
WI code SEES Rel-13 CR0473R- Cat B Comment: Re-write text in "reason for change" to describe technical reasons why the changes are introduced (current text is not suitable). "summary of change" – avoid referring to P-CRs. Mention of "FMSS" – is this correct? |
||||||||
CR |
Huawei, KPN, NEC |
22.101 v13.2.0: Exposure of network service and capabilities to 3rd party |
Revised to S1-141303 |
WI code SEES Rel-13 CR0473R- Cat B Comment: Re-write text in "reason for change" to describe technical reasons why the changes are introduced (current text is not suitable). Revision of S1-141123. |
||||||||
CR |
Huawei, KPN, NEC |
22.101 v13.2.0: Exposure of network service and capabilities to 3rd party |
Noted |
WI code SEES Rel-13 CR0473R- Cat B Revision of S1-141123. Revision of S1-141259. |
||||||||
TR |
Rapporteur |
TR22.853 to include agreements at this meeting |
Agreed |
Agreed as the basis for future contributions Agreed to be sent for approval No presentation |
||||||||
CP |
Rapporteur |
Cover page |
Agreed |
|
||||||||
7.1.1 SEES drafting session information |
||||||||||||
AGE |
Rapporteur/Session chair |
SEES drafting agenda |
Revised to S1-141280 |
|
||||||||
AGE |
Rapporteur/Session chair |
SEES drafting agenda |
Noted |
Revision of S1-141278. |
||||||||
REP |
Rapporteur/Session chair |
SEES drafting report |
Approved |
|
||||||||
Summary of drafting session
The following were agreed: - Editorial modifications accepted as new version of TR (22.853v101) as basis to implement PCRs from this meeting (S1-141281) - Use case updates for Background traffic and Presence/LCS - Generic requirements The following were revised: - Use case updates for Connection Patterns, Terminal characteristics - Use case on QoS was already covered in consolidated requirements - Consolidated requirements
|
||||||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
7.2 MCPTT: Mission Critical Push To Talk over LTE [SP-130728] |
||||||||||||
Work status prior to this meeting: Latest draft: TS 22.179 v0.3.1 Target completion date: SA#65 (09/2014) Percentage completion: 8%
|
||||||||||||
Ad hoc meeting: MCPTT and SRM_GCSE_LTE (Rel-13) only Full approval powers, and reply to LS as required 15/16/17 July 2014
|
||||||||||||
Cont |
Motorola Solutions |
Way forward for MCPTT requirements in TS 22.179 |
Noted |
|
||||||||
Cont |
Motorola Solutions |
Annex with primary requirements for TS 22.179 |
Noted |
|
||||||||
Cont |
Home Office |
Background Document for Group Management in GCSE and MCPTT |
Withdrawn |
|
||||||||
Cont |
Home Office |
Background Document for Group Management in GCSE and MCPTT |
Noted |
Replacement for S1-141191 |
||||||||
TO |
TCCE 04(14)000035 (UK Home Office) |
LS on Analysis on the scope of GCSE and the PTT Application. |
Noted |
Moved from section 4 |
||||||||
Cont |
NSN |
Comparing Group Member States in MCPTT and GCSE |
Noted |
|
||||||||
Cont |
NSN |
Aligning the General Group Call section with GCSE Terminology and clarifying roles of “UE” and “User” in MCPTT Requirements |
Noted |
|
||||||||
Cont |
General Dynamics UK Limited |
Clarification of statements about authorization of actions |
Noted |
|
||||||||
Cont |
UK Home Office |
MCPTT Group Definition |
Noted |
|
||||||||
Cont |
UK Home Office |
Group Management for MCPTT |
Revised to S1-141541 |
|
||||||||
Cont |
UK Home Office |
Group Management for MCPTT |
Withdrawn |
Revision of S1-141190. |
||||||||
Cont |
UK Home Office |
Discussion on Group Management in GCSE and the Relationship to MCPTT |
Noted |
Late document |
||||||||
Cont |
UK Home Office |
Group Management for MCPTT |
Revised to S1-141544 |
Revision of S1-141190. |
||||||||
Cont |
UK Home Office |
Group Management for MCPTT |
Agreed |
Revision of S1-141541.
Agreed to be added to the TS No presentation |
||||||||
Cont |
UK Home Office |
Update terminology in TS according to agreed group definition |
Withdrawn |
|
||||||||
Cont |
US Department of Commerce, General Dynamics UK Ltd, T-Mobile USA Inc., Blackberry |
Service description for Section 4.1, Overview |
Revised to S1-141407 |
|
||||||||
Cont |
US Department of Commerce, General Dynamics UK Ltd, T-Mobile USA Inc., Blackberry |
Service description for Section 4.1, Overview |
Agreed |
Revision of S1-141068. Agreed to be added to the TS |
||||||||
Cont |
US Department of Commerce |
PTT vs MCPTT |
Agreed |
For MCPTT drafting session |
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Additional Floor control requirements, section 4.2 |
Revised to S1-141408 |
|
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Additional Floor control requirements, section 4.2 |
Agreed |
Revision of S1-141069. For MCPTT drafting session Agreed in MCPTT drafting session Agreed to be added to the TS |
||||||||
Cont |
Alcatel-Lucent, US Department of Commerce |
Modifications to a single Floor control requirement on hierarchy in section 4.2 |
Revised to S1-141410 |
|
||||||||
Cont |
Alcatel-Lucent, US Department of Commerce |
Modifications to a single Floor control requirement on hierarchy in section 4.2 |
Agreed |
Revision of S1-141070. For MCPTT drafting session Agreed in MCPTT drafting session Agreed to be added to the TS |
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Additional General Group Call requirements, section 4.3 |
Revised to S1-141411 |
|
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Additional General Group Call requirements, section 4.3 |
Agreed |
Revision of S1-141071. For MCPTT drafting session Agreed in MCPTT drafting session Agreed to be added to the TS |
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for Broadcast / Announcement Group Calls |
Revised to S1-141412 |
|
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for Broadcast / Announcement Group Calls |
Agreed |
Revision of S1-141072. For MCPTT drafting session Agreed in MCPTT drafting session Agreed to be added to the TS |
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for Dynamic Group management |
Revised to S1-141413 |
|
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for Dynamic Group management |
Agreed |
Revision of S1-141073. For MCPTT drafting session Agreed in MCPTT drafting session Agreed to be added to the TS |
||||||||
Cont |
Ericsson |
Q&A about the concept of PTT Session |
Revised to S1-141414 |
|
||||||||
Cont |
Ericsson |
Q&A about the concept of PTT Session |
Noted |
Revision of S1-141115. For MCPTT drafting session |
||||||||
Cont |
Motorola Solutions Inc., Harris Corporation, US Department of Commerce |
Additional Requirements for Audio PTT Call Performance |
Revised to S1-141415 |
|
||||||||
Cont |
Motorola Solutions Inc., Harris Corporation, US Department of Commerce |
Additional Requirements for Audio PTT Call Performance |
Agreed |
Revision of S1-141074. For MCPTT drafting session Agreed in MCPTT drafting session Agreed to be added to the TS |
||||||||
Cont |
Huawei, TD-Tech |
End-to-end PTT setup time performance |
Noted |
|
||||||||
Cont |
Motorola Solutions Inc., Harris Corporation, US Department of Commerce |
Additional Requirements for Late Call Entry Performance |
Revised to S1-141416 |
|
||||||||
Cont |
Motorola Solutions Inc., Harris Corporation, US Department of Commerce |
Additional Requirements for Late Call Entry Performance |
Agreed |
Revision of S1-141146. For MCPTT drafting session Agreed in MCPTT drafting session Agreed to be added to the TS |
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for PTT Priority Requirements |
Revised to S1-141315 |
For MCPTT drafting session |
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for PTT Priority Requirements |
Agreed |
For MCPTT drafting session Revision of S1-141075. Agreed in MCPTT drafting session Agreed to be added to the TS |
||||||||
Cont |
Alcatel-Lucent |
EPS priority management |
Revised to S1-141417 |
|
||||||||
Cont |
Alcatel-Lucent |
EPS priority management |
Revised to S1-141314 |
Revision of S1-141197. For MCPTT drafting session |
||||||||
Cont |
Alcatel-Lucent |
EPS priority management |
Revised to S1-141586 |
Revision of S1-141197. For MCPTT drafting session Revision of S1-141417. |
||||||||
Cont |
Alcatel-Lucent |
EPS priority management |
Agreed |
Revision of S1-141197. For MCPTT drafting session Revision of S1-141417. Revision of S1-141314.
Agreed to be added to the TS No presentation |
||||||||
Cont |
Motorola Solutions |
Add definition of “participant type” to 3.1 |
Revised to S1-141585 |
|
||||||||
Cont |
Motorola Solutions |
Add definition of “participant type” to 3.1 |
Agreed |
Revision of S1-141313.
Agreed to be added to the TS No presentation |
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for Emergency Group Calls |
Revised to S1-141418 |
|
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for Emergency Group Calls |
Agreed |
Revision of S1-141076. For MCPTT drafting session Agreed in MCPTT drafting session Agreed to be added to the TS |
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for Imminent Peril Call |
Revised to S1-141419 |
|
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for Imminent Peril Call |
Agreed |
Revision of S1-141077. For MCPTT drafting session Agreed in MCPTT drafting session Agreed to be added to the TS |
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for personality management |
Revised to S1-141316 |
|
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for personality management |
Agreed |
Revision of S1-141078.
Agreed to be added to the TS No presentation |
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for location |
Revised to S1-141317 |
|
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for location |
Agreed |
Revision of S1-141079.
Agreed to be added to the TS No presentation |
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for security, section 4.10 |
Revised to S1-141312 |
|
||||||||
Cont |
UK Home Office |
Proposed Security Requirements for MCPTT |
Revised to S1-141312 |
|
||||||||
Cont |
UK Home Office |
Proposed Merged Security Requirements for MCPTT |
Revised to S1-141318 |
|||||||||
Cont |
UK Home Office |
Proposed Merged Security Requirements for MCPTT |
Agreed |
Revision of S1-141080 and S1-141030. Revision of S1-141312. Agreed to be added to the TS |
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for interworking with Project 25 |
Revised to S1-141319 |
|
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for interworking with Project 25 |
Revised to S1-141587 |
Revision of S1-141081. |
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for interworking with Project 25 |
Agreed |
Revision of S1-141081. Revision of S1-141319.
Agreed to be added to the TS No presentation |
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for interworking with Legacy Land Mobile Radio |
Revised to S1-141320 |
|
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for interworking with Legacy Land Mobile Radio |
Agreed |
Revision of S1-141082.
Agreed to be added to the TS No presentation |
||||||||
Cont |
French Ministry of Interior |
Inter System Operations Requirements |
Revised to S1-141321 |
|
||||||||
Cont |
French Ministry of Interior |
Inter System Operations Requirements |
Agreed |
Revision of S1-141054.
Agreed to be added to the TS No presentation |
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for Off network |
Revised to S1-141322 |
|
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for Off network |
Noted |
Revision of S1-141083. |
||||||||
Cont |
Intel |
Clarification on MCPTT operation modes |
Noted |
|
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for Emergency Alert |
Revised to S1-141584 |
|
||||||||
Cont |
Harris Corporation, Motorola Solutions Inc., US Department of Commerce |
Requirements for Emergency Alert |
Agreed |
Revision of S1-141084.
Agreed to be added to the TS No presentation |
||||||||
Cont |
Huawei, Td-Tech |
Requirement for service continuity |
Noted |
|
||||||||
Cont |
Huawei, Td-Tech |
Requirements for Interactions between PTT call and telephone call |
Withdrawn |
|
||||||||
Cont |
Motorola Solutions Inc., Harris Corporation, US Department of Commerce |
Requirements for Audio / Voice Quality |
Agreed |
Agreed to be added to the TS
|
||||||||
TS |
Rapporteur |
TS22.179 to include agreements at this meeting |
Agreed |
Agreed as the basis for future contributions No presentation |
||||||||
7.2.1 MCPTT drafting session information |
||||||||||||
AGE |
Rapporteur/Session chair |
MCPTT drafting agenda |
Noted |
|
||||||||
REP |
Rapporteur/Session chair |
MCPTT drafting report |
Approved |
|
||||||||
Summary of drafting session
- Main discussion points o Difficulty understanding user requirements versus solutions based on those requirements. o Word smithing is necessary, even if the result is what was started with. o Is there a need for at least two levels of urgent type calls (i.e.,MCPTT Emergency Group Call and Imminent Peril Call)? o Are the functions relating to priority (call setup, queuing, preempting) user requirements or solution implementation decisions? o Are performance requirements something that can be acted upon by the other groups or can it only be in the context of complete system solutions? o Are priorities directly tied to preexisting priorities within LTE or are they something else? - main agreements o 10 contributions tentatively agreed § ~70 new requirements / covering three existing sections and five new sections
|
||||||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
7.3 eWebRTCi: Enhancements to WebRTC interoperability [SP-140166] |
||||||||||||
Work status prior to this meeting: Target completion date: SA#65 (09/2014) Percentage completion: 0%
|
||||||||||||
CR |
Alcatel-Lucent |
22.228 v12.6.0: Use case for end to end WebRTC bearer support over IMS |
Revised to S1-141430 |
WI code eWebRTCi Rel-13 CR0197R- Cat B Comment: Body text changes-over-changes need to be cleaned up |
||||||||
CR |
Alcatel-Lucent |
22.228 v12.6.0: Use case for end to end WebRTC bearer support over IMS |
Revised to S1-141531 |
WI code eWebRTCi Rel-13 CR0197R- Cat B Revision of S1-141101. |
||||||||
CR |
Alcatel-Lucent |
22.228 v12.6.0: Use case for end to end WebRTC bearer support over IMS |
Agreed |
WI code eWebRTCi Rel-13 CR0197R- Cat B Revision of S1-141101. Revision of S1-141430.
No presentation |
||||||||
CR |
Alcatel-Lucent |
22.228 v12.6.0: Requirements to support end to end WebRTC bearer support over IMS |
Revised to S1-141431 |
WI code eWebRTCi Rel-13 CR0198R- Cat B Comment: Title should exclude the word "requirements". Body text changes-over-changes need to be cleaned up |
||||||||
CR |
Alcatel-Lucent |
22.228 v12.6.0: Requirements to support end to end WebRTC bearer support over IMS |
Revised to S1-141532 |
WI code eWebRTCi Rel-13 CR0198R- Cat B Revision of S1-141102. |
||||||||
CR |
Alcatel-Lucent |
22.228 v12.6.0: Requirements to support end to end WebRTC bearer support over IMS |
Agreed |
WI code eWebRTCi Rel-13 CR0198R- Cat B Revision of S1-141102. Revision of S1-141431.
No presentation |
||||||||
CR |
Huawei |
22.228 v12.6.0: Addition of WebRTC Firewall Traversal requirement |
Noted |
WI code eWebRTCi Rel-13 CR0202R- Cat B Comment: Title should exclude the word "requirement". |
||||||||
7.4 IOPS: Isolated E-UTRAN Operation for Public Safety [SP-140167] |
||||||||||||
Work status prior to this meeting: Target completion date: SA#65 (09/2014) Percentage completion: 0%
|
||||||||||||
General Dynamics UK Ltd |
Definitions and abbreviation in support of normative requirements for Isolated E-UTRAN operation |
Revised to S1-141399 |
|
|||||||||
CR
|
General Dynamics UK Ltd |
22.278 v12.4.0: Definitions and abbreviation in support of normative requirements for Isolated E-UTRAN operation |
Revised to S1-141432 |
Revision of S1-141052. CR#0202 Comment: Title should exclude the word "requirement". At least one box should be checked for "Proposed change affects". "Other specs affected" need to be populated ("N" to all) |
||||||||
CR |
General Dynamics UK Ltd |
22.278 v12.4.0: Definitions and abbreviation for Isolated E-UTRAN operation |
Agreed |
WI code IOPS Rel-13 CR0202R1 Cat B Revision of S1-141052.
No presentation |
||||||||
Cont |
General Dynamics UK Ltd |
Draft service description for Isolated E-UTRAN operation |
Revised to S1-141400 |
|
||||||||
CR |
General Dynamics UK Ltd |
22.278 v12.4.0: Draft service description for Isolated E-UTRAN operation |
Revised to S1-141433 |
Revision of S1-141053. CR#0203 Comment: At least one box should be checked for "Proposed change affects". "Other specs affected" need to be populated ("N" to all) |
||||||||
CR |
General Dynamics UK Ltd |
22.278 v12.4.0: Draft service description for Isolated E-UTRAN operation |
Agreed |
WI code IOPS Rel-13 CR0203R1 Cat B Revision of S1-141053. Revision of S1-141400.
No presentation |
||||||||
Cont |
General Dynamics UK Ltd |
Draft general, subscriber and service management normative requirements for Isolated E-UTRAN operation |
Revised to S1-141401 |
|
||||||||
CR |
General Dynamics UK Ltd |
22.278 v12.4.0: Draft general, subscriber and service management normative requirements for Isolated E-UTRAN operation |
Revised to S1-141434 |
Revision of S1-141055. CR#0204 Comment: Title should exclude the word "requirement". At least one box should be checked for "Proposed change affects". "Other specs affected" need to be populated ("N" to all) |
||||||||
CR |
General Dynamics UK Ltd |
22.278 v12.4.0: Draft general, subscriber and service management aspects for Isolated E-UTRAN operation |
Revised to S1-141556 |
WI code IOPS Rel-13 CR0204R1 Cat B Revision of S1-141055. Revision of S1-141401.
For drafting session |
||||||||
CR |
General Dynamics UK Ltd |
22.278 v12.4.0: Draft general, subscriber and service management aspects for Isolated E-UTRAN operation |
Agreed |
WI code IOPS Rel-13 CR0204R1 Cat B Revision of S1-141055. Revision of S1-141401.
For drafting session Revision of S1-141434.
No presentation |
||||||||
Cont |
French Ministry of Interior |
Minimum set of services for an Isolated E-UTRAN |
Revised to S1-141489 |
Comment: consider whether to include this in TR 22.897 For drafting session |
||||||||
Cont |
French Ministry of Interior |
Minimum set of services for an Isolated E-UTRAN |
Revised to S1-141289 |
Comment: consider whether to include this in TR 22.897 For drafting session Revision of S1-141056. |
||||||||
Cont |
French Ministry of Interior |
Minimum set of services for an Isolated E-UTRAN |
Agreed |
Comment: consider whether to include this in TR 22.897 For drafting session Revision of S1-141056. Revision of S1-141489. Agreed to be added to the TR |
||||||||
Cont |
General Dynamics UK Ltd |
Draft normative requirements for initiation of Isolated E-UTRAN operation |
Revised to S1-141402 |
|
||||||||
CR |
General Dynamics UK Ltd |
22.278 v12.4.0: Draft normative requirements for initiation of Isolated E-UTRAN operation |
Revised to S1-141435 |
Revision of S1-141057. CR#0205 Comment: Title should exclude the word "requirement". At least one box should be checked for "Proposed change affects". "Other specs affected" need to be populated ("N" to all) |
||||||||
CR |
General Dynamics UK Ltd |
22.278 v12.4.0: Draft normative requirements for initiation of Isolated E-UTRAN operation |
Agreed |
WI code IOPS Rel-13 CR0205R1 Cat B Revision of S1-141057. Revision of S1-141402 and S1-141255.
For drafting session |
||||||||
Cont |
General Dynamics UK Ltd |
Draft normative requirements for ongoing Isolated E-UTRAN operation |
Revised to S1-141403 |
|
||||||||
CR |
General Dynamics UK Ltd |
22.278 v12.4.0: Draft normative requirements for ongoing Isolated E-UTRAN operation |
Revised to S1-141476 |
Revision of S1-141059. CR#0206 Comment: Title should exclude the word "requirement". At least one box should be checked for "Proposed change affects". "Other specs affected" need to be populated ("N" to all)
For drafting session |
||||||||
CR |
General Dynamics UK Ltd |
22.278 v12.4.0: Draft normative requirements for ongoing Isolated E-UTRAN operation |
Revised to S1-141557 |
WI code IOPS Rel-13 CR0206R1 Cat B Revision of S1-141059.
For drafting session Revision of S1-141403. |
||||||||
CR |
General Dynamics UK Ltd |
22.278 v12.4.0: Draft normative requirements for ongoing Isolated E-UTRAN operation |
Agreed |
WI code IOPS Rel-13 CR0206R1 Cat B Revision of S1-141059.
For drafting session Revision of S1-141403. Revision of S1-141476.
No presentation |
||||||||
Cont |
General Dynamics UK Ltd |
Draft normative requirements for termination of Isolated E-UTRAN operation |
Revised to S1-141404 |
|
||||||||
CR |
General Dynamics UK Ltd |
22.278 v12.4.0: Draft normative requirements for termination of Isolated E-UTRAN operation |
Revised to S1-141437 |
Revision of S1-141060. CR#0207 Comment: Title should exclude the word "requirement". At least one box should be checked for "Proposed change affects". "Other specs affected" need to be populated ("N" to all) |
||||||||
CR |
General Dynamics UK Ltd |
22.278 v12.4.0: Draft normative requirements for termination of Isolated E-UTRAN operation |
Noted |
WI code IOPS Rel-13 CR0207R1 Cat B Revision of S1-141060. Revision of S1-141404.
For drafting session |
||||||||
Cont |
General Dynamics UK Ltd |
Draft normative requirements for security aspects of Isolated E-UTRAN operation |
Revised to S1-141405 |
|
||||||||
CR |
General Dynamics UK Ltd |
22.278 v12.4.0: Draft normative requirements for security aspects of Isolated E-UTRAN operation |
Revised to S1-141438 |
Revision of S1-141061. CR#0208 Comment: Title should exclude the word "requirement". At least one box should be checked for "Proposed change affects". "Other specs affected" need to be populated ("N" to all) |
||||||||
CR |
General Dynamics UK Ltd |
22.278 v12.4.0: Draft normative requirements for security aspects of Isolated E-UTRAN operation |
Noted |
WI code IOPS Rel-13 CR0208R1 Cat B Revision of S1-141061. Revision of S1-141405.
For drafting session |
||||||||
Cont |
LG Electronics, Inc. |
Discussion Paper – Considerations on Proper Indication on IOPS status to UE’s |
Revised to S1-141435 |
Comment: consider whether to include this in TR 22.897 |
||||||||
Cont |
French Ministry of Interior |
Operational requirements for Isolated E-UTRAN operation |
Revised to S1-141439 |
Moved from section 8.2 Comment: consider whether to include this in TR 22.897. Related with S1-141246 and S1-141247 in section 8.2. |
||||||||
Cont |
French Ministry of Interior |
Operational requirements for Isolated E-UTRAN operation |
Revised to S1-141290 |
Moved from section 8.2 Comment: consider whether to include this in TR 22.897. Related with S1-141246 and S1-141247 in section 8.2. Revision of S1-141058.
For drafting session |
||||||||
Cont |
French Ministry of Interior |
Operational requirements for Isolated E-UTRAN operation |
Agreed |
Moved from section 8.2 Comment: consider whether to include this in TR 22.897. Related with S1-141246 and S1-141247 in section 8.2. Revision of S1-141058.
For drafting session Revision of S1-141439. Agreed to be added to the TR |
||||||||
Cont |
LG Electronics, Inc. |
Discussion on Change of Time Zone in IOPS |
Revised to S1-141440 |
Comment: consider whether to include this in TR 22.897 |
||||||||
Cont |
LG Electronics, Inc. |
Discussion on Change of Time Zone in IOPS |
Noted |
Comment: consider whether to include this in TR 22.897 Revision of S1-141253.
For drafting session |
||||||||
WID |
NSN |
Updated WID on Isolated E-UTRAN Operation for Public Safety (IOPS) |
Revised to S1-141529 |
|
||||||||
WID |
NSN |
Updated WID on Isolated E-UTRAN Operation for Public Safety (IOPS) |
Revised to S1-141558 |
Revision of S1-141486. |
||||||||
WID |
NSN |
Updated WID on Isolated E-UTRAN Operation for Public Safety (IOPS) |
Agreed |
Revision of S1-141486. Revision of S1-141529.
No presentation |
||||||||
TS |
Rapporteur |
Draft TS |
Agreed |
Agreed as the basis for future contributions |
||||||||
7.4.1 IOPS/FS_IOPS drafting session information |
||||||||||||
AGE |
Rapporteur/Session chair |
IOPS/FS_IOPS drafting agenda |
Noted |
|
||||||||
REP |
Rapporteur/Session chair |
IOPS/FS_IOPS drafting report |
Approved |
|
||||||||
Summary of drafting session
S1-141056 and S-1141439 are to be revised to be shown in their proper placement within TR 22.897
|
||||||||||||
|
|
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 |
|
||||||||
7.5 SRMMTC: Service Requirements Maintenance for MTC [SP-130600] |
||||||||||||
Orange |
22.368 v12.3.0: Unexpected data exchange |
Noted |
WI code SRMMTC Rel-13 CR0152R- Cat C Comment: "other spec affected" needs to be populated |
|||||||||
Orange |
22.101 v13.2.0: SMS-outbox update on Mobile |
Moved to section 5.2 |
WI code SMS_OBUD Rel-13 CR0474R- Cat B |
|||||||||
Cont |
Orange |
Discussion Paper SMS-outbox update on mobile |
Moved to section 5.2 |
|
||||||||
8.1 FS_ACDC: Application specific congestion control for data communication [SP-130415] |
||||||||||||
Work status prior to this meeting: Draft TR 22.806 v1.0.0 was sent to SA plenary for information at Taipei SA1#65 Target completion date: SA#64 (06/2014) Percentage completion: 70%
|
||||||||||||
FS_ACDC Rapporteur |
ACDC TR editorial: references |
Agreed |
For ACDC drafting session: The session agreed if there is any conflict between this document and S1-141107, this document takes precedence. Agreed in ACDC drafting session Agreed to be added to the TR |
|||||||||
Cont |
Qualcomm Incorporated, NTT DOCOMO |
Proposed Editorial Changes to TR 22.806 Study on Application specific Congestion control for Data Communication |
Agreed |
For ACDC drafting session Agreed to be added to the TR |
||||||||
Cont |
FS_ACDC Rapporteur |
ACDC TR editorial: to solve Editor’s NOTE on a term “honour” |
Revised to S1-141341 |
For ACDC drafting session: The session found it is better not to use the term “honour”, “apply” was used instead. |
||||||||
Cont |
FS_ACDC Rapporteur |
ACDC TR editorial: to solve Editor’s NOTE on a term “honour” |
Agreed |
For ACDC drafting session: The session found it is better not to use the term “honour”, “apply” was used instead. Revision of S1-141165. Agreed to be added to the TR |
||||||||
Cont |
LG Electronics, Inc. |
Some clarification in the statement of honouring ACDC category |
Revised to S1-141387 |
For ACDC drafting session |
||||||||
Cont |
LG Electronics, Inc. |
Some clarification in the statement of honouring ACDC category |
Noted |
For ACDC drafting session: The session confirmed the existing roaming scheme is the one we have chosen. Revision of S1-141163. |
||||||||
Cont |
NTT DOCOMO |
ACDC TR clean-up: use case 2 and 3, removing overlap with SCM. |
Agreed |
For ACDC drafting session Agreed in ACDC drafting session: (1)“a simplified use case” in the title needs to be removed. (2) “void” is not used even when a sub-section gets deleted. Re-numbering is needed. Taking into account those two points, it was agreed to incorporate this P-CR into TR, without creating another revision. Agreed to be added to the TR |
||||||||
Cont |
NTT DOCOMO, Qualcomm Incorporated |
ACDC TR clean-up: use case 9, removing overlap with SCM. |
Revised to S1-141338 |
For ACDC drafting session: The session agreed to delete the use case 9 and to add a new sub clause in section 6, but found the new text needs further elaboration. “void” should not be used; re-numbering is needed. |
||||||||
Cont |
NTT DOCOMO, Qualcomm Incorporated |
ACDC TR clean-up: use case 9, removing overlap with SCM. |
Revised to S1-141509 |
For ACDC drafting session: The session agreed to delete the use case 9 and to add a new sub clause in section 6, but found the new text needs further elaboration. “void” should not be used; re-numbering is needed. Revision of S1-141167. |
||||||||
Cont |
NTT DOCOMO, Qualcomm Incorporated |
ACDC TR clean-up: use case 9, removing overlap with SCM. |
Agreed |
For ACDC drafting session: The session agreed to delete the use case 9 and to add a new sub clause in section 6, but found the new text needs further elaboration. “void” should not be used; re-numbering is needed. Revision of S1-141167. Revision of S1-141338. Agreed to be added to the TR |
||||||||
|
|
|
Withdrawn |
|
||||||||
Cont |
NTT DOCOMO |
ACDC TR clean-up: use case 16, update of description due to SCM. |
Agreed |
For ACDC drafting session Agreed in ACDC drafting session Agreed to be added to the TR |
||||||||
Cont |
NTT DOCOMO |
ACDC TR clean-up: clause 7, update of the list of
potential requirements |
Agreed |
For ACDC drafting session Agreed in ACDC drafting session Agreed to be added to the TR |
||||||||
Cont |
Qualcomm Incorporated |
ACDC System Overview |
Revised to S1-141339 |
For ACDC drafting session: Comments were as follows: (1) The title needs to be changed to “ACDC background information”. (2) Figure B-1 is too detailed; should be more high-level. (3) Normative wording should not be used. (4) Clarification on “back-off” or “barring-rate”. (5) “Loop” in a sub-title is to be taken out. |
||||||||
Cont |
Qualcomm Incorporated |
ACDC System Overview |
Revised to S1-141550 |
For ACDC drafting session: Comments were as follows: (1) The title needs to be changed to “ACDC background information”. (2) Figure B-1 is too detailed; should be more high-level. (3) Normative wording should not be used. (4) Clarification on “back-off” or “barring-rate”. (5) “Loop” in a sub-title is to be taken out. Revision of S1-141105. |
||||||||
Cont |
Qualcomm Incorporated |
ACDC System Overview |
Agreed |
For ACDC drafting session: Comments were as follows: (1) The title needs to be changed to “ACDC background information”. (2) Figure B-1 is too detailed; should be more high-level. (3) Normative wording should not be used. (4) Clarification on “back-off” or “barring-rate”. (5) “Loop” in a sub-title is to be taken out. Revision of S1-141105. Revision of S1-141339. Agreed to be added to the TR |
||||||||
Cont |
TeliaSonera AB |
Proposal for conclusion on ACDC and Network Sharing (Use Case 15) |
Revised to S1-141336 |
For ACDC drafting session: The session agreed it is useful to add a recommendation on protection of RACH. |
||||||||
Cont |
TeliaSonera AB |
Proposal for conclusion on ACDC and Network Sharing (Use Case 15) |
Revised to S1-141337 |
For ACDC drafting session: The session agreed it is useful to add a recommendation on protection of RACH. Revision of S1-141100. |
||||||||
Cont |
TeliaSonera AB |
Proposal for conclusion on ACDC and Network Sharing (Use Case 15) |
Agreed |
For ACDC drafting session: The session agreed it is useful to add a recommendation on protection of RACH. Revision of S1-141100. Revision of S1-141336. Agreed in ACDC drafting session Agreed to be added to the TR |
||||||||
Cont |
Qualcomm Incorporated |
ACDC: Evaluation of Network Sharing Use Case |
Noted |
For ACDC drafting session: TeliaSonera agrees with the view on RACH, but feels this P-CR lacks an aspect of protecting a core network. |
||||||||
Cont |
Qualcomm Incorporated |
ACDC Use Case: Applicability of ACDC in UE Connected State |
Noted |
For ACDC drafting session: The session confirmed ACDC does not apply to ongoing session. Although ongoing session and the connected mode are not directly linked, the session felt the working assumption has been to apply ACDC only to the idle mode. It was recommended to deal with the connected mode issue separately from a broader perspective. |
||||||||
Cont |
Qualcomm Incorporated, NTT DOCOMO |
Consolidation of Potential Requirements from TR 22.806 Study to Normative Text |
Moved to section 5.2 |
|
||||||||
Cont |
NTT DOCOMO |
Consolidation of Potential requirements |
Moved to section 5.2 |
|
||||||||
TR |
Rapporteur |
TR22.806 to include agreements at this meeting |
Agreed |
Agreed as the basis for future contributions Agreed to be sent for approval No presentation |
||||||||
CP |
Rapporteur |
Cover page |
Revised to S1-141601 |
|
||||||||
CP |
Rapporteur |
Cover page |
Approved |
Revision of S1-141305.
No presentation |
||||||||
8.1.1 FS_ACDC drafting session information |
||||||||||||
AGE |
Rapporteur/Session chair |
FS_ACDC drafting agenda |
Noted |
|
||||||||
REP |
Rapporteur/Session chair |
FS_ACDC drafting report |
Approved |
|
||||||||
Summary of drafting session
- Potential requirements related to network sharing and to “mode” were clarified and agreed. - TR was cleaned up. - CR was reviewed and modified. - No controversial issue is foreseen except for a question on how many categories are needed.
|
||||||||||||
8.2 FS_IOPS: Isolated E-UTRAN operation for Public Safety [SP-130596] |
||||||||||||
Work status prior to this meeting: Draft TR 22.897 v1.0.0 was sent to SA plenary for information at Taipei SA1#65 Target completion date: SA#64 (06/2014) Percentage completion: 90%
|
||||||||||||
General Dynamics UK Ltd |
Aligning the title of the FS_IOPS technical report with MCC drafting rules |
Agreed |
|
|||||||||
Cont |
KPN |
Operational aspects of subscription data for local services in an isolated E-UTRAN |
Noted |
Related to S1-141058 in section 7.4 |
||||||||
Cont |
KPN |
Modification of service requirements for isolated E-UTRAN to reflect operational aspects of local subscription data |
Revised to S1-141441 |
Related to S1-141058 in section 7.4 |
||||||||
Cont |
KPN |
Modification of service requirements for isolated E-UTRAN to reflect operational aspects of local subscription data |
Revised to S1-141559 |
Related to S1-141058 in section 7.4 Revision of S1-141247.
For drafting session |
||||||||
Cont |
KPN |
Modification of service requirements for isolated E-UTRAN to reflect operational aspects of local subscription data |
Agreed |
Related to S1-141058 in section 7.4 Revision of S1-141247.
For drafting session Revision of S1-141441.
Agreed to be added to the TR No presentation |
||||||||
Cont |
III, ITRI |
Deployment on Remote Territory |
Noted |
|
||||||||
TR |
Rapporteur |
TR22.897 to include agreements at this meeting |
Agreed |
Agreed as the basis for future contributions Agreed to be sent for approval No presentation |
||||||||
CP |
Rapporteur |
Cover page |
Agreed |
|
||||||||
Cont |
French Ministry of Interior |
Operational requirements for Isolated E-UTRAN operation |
Moved to section 7.4 |
|
||||||||
8.3 FS_MAPN: Need for multiple APNs [SP-130416] |
||||||||||||
Work status prior to this meeting: Latest draft: TR 22.802 v0.2.1 Target completion date: SA#65 (09/2014) Percentage completion: 50%
|
||||||||||||
Ericsson |
Late provisioning of a selected MNO |
Revised to S1-141473 |
|
|||||||||
Cont |
Ericsson |
Late provisioning of a selected MNO |
Revised to S1-141591 |
Revision of S1-141124. |
||||||||
Cont |
Ericsson |
Network based solution for operator swap use-case |
Revised to S1-141598 |
Revision of S1-141124. Revision of S1-141473. |
||||||||
Cont |
Ericsson |
Network based solution for operator swap use-case |
Agreed |
Revision of S1-141124. Revision of S1-141473. Revision of S1-141591.
Agreed to be added to the TR No presentation |
||||||||
Cont |
Ericsson |
Change of selected MNO |
Revised to S1-141474 |
|
||||||||
Cont |
Ericsson |
Network based solution for operator swap use-case |
Revised to S1-141592 |
Revision of S1-141125. |
||||||||
Cont |
Ericsson |
Network based solution for the in-vehicle user equipment |
Revised to S1-141595 |
Revision of S1-141125. Revision of S1-141474. |
||||||||
Cont |
Ericsson |
Network based solution for the in-vehicle user equipment |
Agreed |
Revision of S1-141125. Revision of S1-141474. Revision of S1-141592.
Agreed to be added to the TR No presentation |
||||||||
|
Ericsson |
Update to existing use case |
Withdrawn |
|
||||||||
Cont |
Ericsson |
Single IP address |
Revised to S1-141472 |
|
||||||||
Cont |
Ericsson |
Single IP address |
Agreed |
Revision of S1-141127. Agreed to be added to the TR |
||||||||
Cont |
Vodafone |
Rationale for provisioning, storage, and management of APN(s) within the (U)SIM on the UICC |
Revised to S1-141254 |
|
||||||||
Cont |
Vodafone |
Rationale for provisioning, storage, and management of APN(s) within the (U)SIM on the UICC |
Noted |
Revision of S1-141184. |
||||||||
Cont |
Alcatel-Lucent |
Advantages of Device management based solution |
Revised to S1-141538 |
|
||||||||
Cont |
Alcatel-Lucent |
Advantages of Device management based solution |
Agreed |
Revision of S1-141192. Agreed to be added to the TR |
||||||||
Cont |
Alcatel-Lucent |
Disadvantages of UICC based solution |
Revised to S1-141537 |
|
||||||||
Cont |
Alcatel-Lucent |
Disadvantages of UICC based solution |
Revised to S1-141596 |
Revision of S1-141193. |
||||||||
Cont |
Alcatel-Lucent, Giesecke & Devrient |
Characteristics of UICC based solution |
Revised to S1-141597 |
Revision of S1-141193. Revision of S1-141537. |
||||||||
Cont |
Alcatel-Lucent, Giesecke & Devrient |
Characteristics of UICC based solution |
Agreed |
Revision of S1-141193. Revision of S1-141537. Revision of S1-141596.
Agreed to be added to the TR No presentation |
||||||||
Cont |
Alcatel-Lucent |
FS_MAPN conclusion |
Noted |
|
||||||||
Cont |
FS_MAPN Rapporteur |
FS_MAPN conclusion |
Withdrawn |
|
||||||||
TR |
Rapporteur |
TR22.802 to include agreements at this meeting |
Agreed |
Agreed as the basis for future contributions No presentation |
||||||||
LS OUT |
Vodafone |
LS to OMA DM on options of usage of OMA DM for APN configuration |
Revised to S1-141589 |
|
||||||||
LS OUT |
Vodafone |
LS to OMA DM on options of usage of OMA DM for APN configuration |
Revised to S1-141594 |
Revision of S1-141534. |
||||||||
LS OUT |
Vodafone |
LS to OMA DM on options of usage of OMA DM for APN configuration |
Approved |
Revision of S1-141534. Revision of S1-141589.
No presentation |
||||||||
Cont |
Rapporteur |
Record editor's notes on items needing further clarification |
Noted |
|
||||||||
8.4 FS_CSIPTO: Co-ordinated P-GW change for SIPTO [SP-130417] |
||||||||||||
Work status prior to this meeting: Draft TR 22.828 v1.0.0 was sent to SA plenary for information at Taipei SA1#65 Target completion date: SA#64 (06/2014) Percentage completion: 65%
|
||||||||||||
Ericsson |
Consideration on CSIPTO complexity and suggested conclusion |
Revised to S1-141381 |
|
|||||||||
Cont |
Ericsson |
Consideration on CSIPTO complexity and suggested conclusion |
Noted |
Revision of S1-141187. |
||||||||
Cont |
Intel |
Response to S1-141187 |
Noted |
|
||||||||
Cont |
Intel (Rapporteur) |
MCC’s Editorial & Formatting Changes to TR 22.828 |
Agreed |
Agreed as the basis for contributions in this meeting |
||||||||
Cont |
Intel (Rapporteur) |
Addition of Requirement Numbers to TR 22.828 |
Agreed |
Agreed to be added to the TR |
||||||||
Cont |
Intel; Samsung; Sony Mobile Communications; T-Mobile USA; Interdigital; China Mobile, KPN; Acer; China Telecom |
Discussion Paper to Consolidate Potential Requirements in Section 6 of TR 22.828 |
Noted |
|
||||||||
Cont |
Intel; Samsung; Sony Mobile Communications; T-Mobile USA; Interdigital; China Mobile; KPN; Acer; China Telecom |
Proposed Text for CSIPTO Consolidated Requirements |
Agreed |
Agreed to be added to the TR |
||||||||
Cont |
Samsung |
P-CR to TR 22.828 to Refine Potential Impacts for Use Cases 3&4 |
Agreed |
Agreed to be added to the TR |
||||||||
Cont |
Orange |
P-CR to TR 22.828 on Section 4 Potential Requirements |
Revised to S1-141477 |
|
||||||||
Cont |
Orange |
P-CR to TR 22.828 on Section 4 Potential Requirements |
Agreed |
Revision of S1-141128.
Agreed to be added to the TR No presentation |
||||||||
Cont |
Intel; Samsung; Sony Mobile Communications; Interdigital; T-Mobile USA; China Mobile; KPN; Acer; China Telecom |
Revision of APN-AMBR Note & Add New requirement |
Revised to S1-141478 |
|
||||||||
Cont |
Intel; Samsung; Sony Mobile Communications; Interdigital; T-Mobile USA; China Mobile; KPN; Acer; China Telecom |
Revision of APN-AMBR Note & Add New requirement |
Agreed |
Revision of S1-141136. |
||||||||
Cont |
Intel; Samsung; Interdigital; Sony Mobile Communications; T-Mobile USA |
Considerations on Security for CSIPTO |
Revised to S1-141479 |
|
||||||||
Cont |
Intel; Samsung; Interdigital; Sony Mobile Communications; T-Mobile USA |
Considerations on Security for CSIPTO |
Agreed |
Revision of S1-141137. |
||||||||
Cont |
Intel; Samsung; Interdigital; Sony Mobile Communications; T-Mobile |
Considerations on Charging for CSIPTO |
Agreed |
Agreed to be added to the TR |
||||||||
Cont |
Intel; Samsung; Interdigital; Sony Mobile Communications; T-Mobile USA |
Considerations on Evolution and Rollout for CSIPTO |
Agreed |
Agreed to be added to the TR |
||||||||
Cont |
Rapporteur |
Revised version for consolidated requirements |
Agreed |
New version of S1-141142 |
||||||||
Cont |
Rapporteur |
Considerations on IMS for CSIPTO |
Revised to S1-141543 |
|
||||||||
Cont |
Rapporteur |
Considerations on IMS for CSIPTO |
Agreed |
Revision of S1-141497. |
||||||||
Cont |
Intel |
Removal of use case 2 and IMS requirements from TR |
Agreed |
|
||||||||
Cont |
Intel |
Proposed conclusion section for TR 22.828 |
Revised to S1-141561 |
|
||||||||
Cont |
Intel |
Proposed conclusion section for TR 22.828 |
Agreed |
Revision of S1-141140.
No presentation |
||||||||
TR |
Rapporteur |
TR22.828 to include agreements at this meeting |
Agreed |
Agreed as the basis for future contributions Agreed to be sent for approval No presentation |
||||||||
CP |
Rapporteur |
Cover page |
Agreed |
|
||||||||
WID |
Intel; Samsung; Interdigital; Sony Mobile Communications; T-Mobile USA; KPN; China Mobile; Acer; China Telecom |
Proposed WID for Co-ordinated P-GW change for SIPTO (CSIPTO) |
Moved to section 5.2 |
Comment: section 10, remove line for new specification (TR xyz) |
||||||||
Cont |
Intel; Samsung; Sony Mobile Communications; T-Mobile USA; Interdigital; KPN; China Mobile; Acer; China Telecom |
Discussion Paper - Draft CR to add CSIPTO to TS22.101 |
Moved to section 5.2 |
|
||||||||
8.5 FS_eICBD: Enhancements for infrastructure based data communication between devices [SP-130418] |
||||||||||||
Work status prior to this meeting: Latest draft: TR 22.807 v0.4.1 Target completion date: SA#65 (09/2014) Percentage completion: 40%
|
||||||||||||
Interdigital, KPN |
Proposed Acronyms for eICBD |
Noted |
|
|||||||||
Cont |
Interdigital, KPN |
Proposed missing requirements for eICBD security use case |
Revised to S1-141480 |
|
||||||||
Cont |
Interdigital, KPN |
Proposed missing requirements for eICBD security use case |
Agreed |
Revision of S1-141238. Agreed to be added to the TR |
||||||||
Cont |
Interdigital, KPN |
Corrections to Service Discovery use case |
Agreed |
Agreed to be added to the TR |
||||||||
Cont |
KPN, Interdigital |
Corrections to IP connection establishment use cases |
Revised to S1-141481 |
|
||||||||
Cont |
KPN, Interdigital |
Corrections to IP connection establishment use cases |
Agreed |
Revision of S1-141240. Agreed to be added to the TR |
||||||||
Cont |
KPN, Interdigital |
eICBD Charging Use Case |
Revised to S1-141482 |
|
||||||||
Cont |
KPN, Interdigital |
eICBD Charging Use Case |
Agreed |
Revision of S1-141244. Agreed to be added to the TR |
||||||||
Cont |
KPN |
Offloading IP connection between devices use case |
Revised to S1-141376 |
|
||||||||
Cont |
KPN |
Offloading IP connection between devices use case |
Revised to S1-141483 |
Revision of S1-141248. |
||||||||
Cont |
KPN |
Offloading IP connection between devices use case |
Agreed |
Revision of S1-141248. Revision of S1-141376.
Agreed to be added to the TR No presentation |
||||||||
TR |
Rapporteur |
TR22.807 to include agreements at this meeting |
Agreed |
Agreed as the basis for future contributions Agreed to be sent for information No presentation |
||||||||
CP |
Rapporteur |
Cover page |
Agreed |
|
||||||||
8.6 FS_FMSS: Flexible Mobile Service Steering [SP-130597] |
||||||||||||
Work status prior to this meeting: Latest draft: TR 22.808 v0.3.1 Target completion date: SA#65 (09/2014) Percentage completion: 30%
|
||||||||||||
Huawei |
FMSS TR Cleanup |
Agreed |
Agreed as the basis for contributions at this meeting |
|||||||||
Cont |
NSN |
The name of the TR |
Noted |
|
||||||||
Cont |
Huawei, China Mobile, Orange, Alcatel-Lucent |
Overview section for FMSS |
Revised to S1-141442 |
|
||||||||
Cont |
Huawei, China Mobile, Orange, Alcatel-Lucent |
Overview section for FMSS |
Revised to S1-141351 |
Revision of S1-141040. For FMSS drafting session: Use "(S)Gi-LAN" to replace "Gi-LAN network". The figure should be aligned with the text. Delete the 3GPP scope in the figure. |
||||||||
Cont |
Huawei, China Mobile, Orange, Alcatel-Lucent |
Overview section for FMSS |
Agreed |
Revision of S1-141040. For FMSS drafting session: Use "(S)Gi-LAN" to replace "Gi-LAN network". The figure should be aligned with the text. Delete the 3GPP scope in the figure. Revision of S1-141442. Agreed in FMSS drafting session Agreed to be added to the TR |
||||||||
Cont |
NSN |
Proposed FMSS Definitions and Overview |
Revised to S1-141426 |
|
||||||||
Cont |
NSN |
Proposed FMSS Definitions and Overview |
Revised to S1-141443 |
Revision of S1-141036. |
||||||||
Cont |
NSN |
Proposed FMSS Definitions and Overview |
Noted |
Revision of S1-141036. Revision of S1-141426. For drafting FMSS session: Too much stage 2 description. Some concerns on the service enabler definition and other definitions. |
||||||||
Cont |
NSN |
Correction to use case on network congestion |
Revised to S1-141444 |
|
||||||||
Cont |
NSN |
Correction to use case on network congestion |
Agreed |
Revision of S1-141023.
No presentation |
||||||||
Cont |
Cisco, Allot Communications |
Traffic steering on network status to be on RAN status |
Noted |
|
||||||||
Cont |
China Mobile, Huawei, Orange |
Generic requirements on service steering |
Revised to S1-141455 |
|
||||||||
Cont |
China Mobile, Huawei, Orange |
Generic requirements on service steering |
Revised to S1-141352 |
Revision of S1-141035. For FMSS drafting session The service enabler is out of scope, so the authorization and the unavalibility of service enabler is out of scope. Some requirements need use case to give more information. |
||||||||
Cont |
China Mobile, Huawei, Orange |
Generic requirements on service steering |
Revised to S1-141542 |
Revision of S1-141035. For FMSS drafting session Revision of S1-141455. |
||||||||
Cont |
China Mobile, Huawei, Orange |
Generic requirements on service steering |
Revised to S1-141547 |
Revision of S1-141035. For FMSS drafting session Revision of S1-141455. Revision of S1-141352. |
||||||||
Cont |
China Mobile, Huawei, Orange |
Generic requirements on service steering |
Agreed |
Revision of S1-141035. For FMSS drafting session Revision of S1-141455. Revision of S1-141352. Revision of S1-141542. Agreed to be added to the TR |
||||||||
Cont |
Juniper Networks, Vodafone Group plc, Telecom Italia, NSN |
Traffic Steering based on operator’s policies or user subscription |
Revised to S1-141256 |
|
||||||||
Cont |
Juniper Networks, Vodafone Group plc, Telecom Italia, NSN |
Traffic Steering based on operator’s policies or user subscription |
Revised to S1-141456 |
Revision of S1-141031. |
||||||||
Cont |
Juniper Networks, Vodafone Group plc, Telecom Italia, NSN |
Traffic Steering based on operator’s policies or user subscription |
Revised to S1-141350 |
Revision of S1-141031. Revision of S1-141256. For FMSS drafting session |
||||||||
Cont |
Juniper Networks, Vodafone Group plc, Telecom Italia, NSN |
Traffic Steering based on operator’s policies or user subscription |
Agreed |
Revision of S1-141031. Revision of S1-141256. For FMSS drafting session Revision of S1-141456. Agreed in FMSS drafting session Agreed to be added to the TR |
||||||||
Cont |
Juniper Networks, Vodafone, Telecom Italia, NSN |
ppt for discussion - Traffic Steering based on Operator's Policies or User Subscription |
Noted |
|
||||||||
Cont |
KDDI |
Change Request to Use Case to Address steering based on status of subscription |
Revised to S1-141436 |
|
||||||||
Cont |
KDDI |
Change Request to Use Case to Address steering based on status of subscription |
Agreed |
Revision of S1-141183. |
||||||||
Cont |
Huawei, China Mobile, Orange, Alcatel-Lucent |
Traffic steering in MVNO scenario |
Revised to S1-141457 |
|
||||||||
Cont |
Huawei, China Mobile, Orange, Alcatel-Lucent |
Traffic steering in MVNO scenario |
Agreed |
Revision of S1-141033. For drafting FMSS session Agreed in FMSS drafting session Agreed to be added to the TR |
||||||||
Cont |
Huawei, China Mobile, Orange |
Traffic steering based on QoS information |
Revised to S1-141500 |
For FMSS drafting session: Add bearer Qos information in the requirement. |
||||||||
Cont |
Huawei, China Mobile, Orange |
Traffic steering based on QoS information |
Agreed |
For FMSS drafting session Add bearer Qos information in the requirement. Revision of S1-141034. Agreed in FMSS drafting session Agreed to be added to the TR |
||||||||
Cont |
NSN |
Proposed FMSS use case on changing the Service Chain during the connection |
Revised to S1-141458 |
|
||||||||
Cont |
NSN |
Proposed FMSS use case on changing the Service Chain during the connection |
Revised to S1-141501 |
Revision of S1-141037. For FMSS drafting session: Requirement should be updated so that focus is to allow steering direction to be modified for ongoing connections. |
||||||||
Cont |
NSN |
Proposed FMSS use case on changing the Service Chain during the connection |
Revised to S1-141548 |
Revision of S1-141037. For FMSS drafting session: Requirement should be updated so that focus is to allow steering direction to be modified for ongoing connections. Revision of S1-141458. |
||||||||
Cont |
NSN |
Proposed FMSS use case on changing the Service Chain during the connection |
Revised to S1-141554 |
Revision of S1-141037. For FMSS drafting session: Requirement should be updated so that focus is to allow steering direction to be modified for ongoing connections. Revision of S1-141458. Revision of S1-141501. |
||||||||
Cont |
NSN |
Proposed FMSS use case on changing the Service Chain during the connection |
Agreed |
Revision of S1-141037. For FMSS drafting session: Requirement should be updated so that focus is to allow steering direction to be modified for ongoing connections. Revision of S1-141458. Revision of S1-141501. Revision of S1-141548. Agreed to be added to the TR |
||||||||
Cont |
NSN |
Proposed FMSS use case on adding new Service Functions to the Service Chaining System |
Noted |
|
||||||||
Cont |
NSN |
Proposed FMSS use case on adding capacity to the Network Service |
Noted |
|
||||||||
Cont |
NSN |
Proposed FMSS use case on adding capacity to the Network Service |
Withdrawn |
For FMSS drafting session Revision of S1-141039. |
||||||||
Cont |
ZTE Corporation, China Mobile, China Unicom, China Telecom, CATR |
Use Case for Service Chain Status update |
Revised to S1-141378 |
|
||||||||
Cont |
ZTE Corporation, China Mobile, China Unicom, China Telecom, CATR |
Use Case for Service Chain Status update |
Revised to S1-141502 |
Revision of S1-141050. For FMSS drafting session: Some modification to the requirement. |
||||||||
Cont |
ZTE Corporation, China Mobile, China Unicom, China Telecom, CATR |
Use Case for Service Chain Status update |
Noted |
Revision of S1-141050. For FMSS drafting session: Some modification to the requirement. Revision of S1-141378. Agreed in FMSS drafting session |
||||||||
Cont |
ZTE, China Mobile, China Telecom, China Unicom, CATT |
Use Case for Flexible Mobile Service Steering – Service Chain Bootstrapping and Auto Re-configuration |
Revised to S1-141377 |
|
||||||||
Cont |
ZTE, China Mobile, China Telecom, China Unicom, CATT |
Use Case for Flexible Mobile Service Steering – Service Chain Bootstrapping and Auto Re-configuration |
Revised to S1-141345 |
Revision of S1-141051. For FMSS drafting session: Service enabler is not in the scope of the study, so the first and third requirement could be removed. The second requirement seems overlap with other use case and should be revised. |
||||||||
Cont |
ZTE, China Mobile, China Telecom, China Unicom, CATT |
Use Case for Flexible Mobile Service Steering – Service Chain Bootstrapping and Auto Re-configuration |
Revised to S1-141583 |
Revision of S1-141051. For FMSS drafting session: Service enabler is not in the scope of the study, so the first and third requirement could be removed. The second requirement seems overlap with other use case and should be revised. Revision of S1-141377. |
||||||||
Cont |
ZTE, China Mobile, China Telecom, China Unicom, CATT |
Use Case for Flexible Mobile Service Steering – Service Chain Bootstrapping and Auto Re-configuration |
Noted |
Revision of S1-141051. For FMSS drafting session: Service enabler is not in the scope of the study, so the first and third requirement could be removed. The second requirement seems overlap with other use case and should be revised. Revision of S1-141377. Revision of S1-141345. |
||||||||
Cont |
Huawei |
Use case on traffic steering based on APN |
Revised to S1-141567 |
For FMSS drafting session: Some discussion on whether APN is a suitable term. Agreed in FMSS drafting session |
||||||||
Cont |
Huawei |
Use case on traffic steering based on APN |
Agreed |
For FMSS drafting session: Some discussion on whether APN is a suitable term. Agreed in FMSS drafting session Revision of S1-141160. Agreed to be added to the TR |
||||||||
Cont |
Huawei |
Use case on traffic steering based on APN |
Noted |
For FMSS drafting session: Some discussion on whether APN is a suitable term. Revision of S1-141160. One suggestion to change APN to "destination PDN". |
||||||||
Cont |
Huawei |
Use case on traffic steering based on time and/or location |
Revised to S1-141503 |
For FMSS drafting session: Some comments that this overlaps with other use cases. |
||||||||
Cont |
Huawei |
Use case on traffic steering based on time and/or location |
Agreed |
For FMSS drafting session: Some comments that this overlaps with other use cases. Revision of S1-141161. Comfirmed there’s no overlaping with other use case. Agreed in FMSS drafting session Agreed to be added to the TR |
||||||||
Cont |
Huawei |
Traffic steering in roaming cases |
Agreed |
For FMSS drafting session: Seems like solution, may be other ways to do this. Agreed to be added to the TR |
||||||||
Cont |
Huawei |
Traffic steering in roaming cases |
Withdrawn |
For FMSS drafting session: Seems like solution, may be other ways to do this. Revision of S1-141162. |
||||||||
Cont |
NEC |
Use case on sub-networking for M2M traffic |
Noted |
For FMSS drafting session |
||||||||
Cont |
China Mobile, Huawei |
FMSS Consolidated requirements |
Revised to S1-141471 |
For FMSS drafting session: Some comments on the term "3GPP network". It’s suggested to say "3GPP network should allow the MNO to define…." |
||||||||
Cont |
China Mobile, Huawei |
FMSS Consolidated requirements |
Revised to S1-141348 |
For FMSS drafting session: Some comments on the term "3GPP network". It’s suggested to say "3GPP network should allow the MNO to define…." Revision of S1-141041. |
||||||||
Cont |
China Mobile, Huawei |
FMSS Consolidated requirements |
Agreed |
For FMSS drafting session: Some comments on the term "3GPP network". It’s suggested to say "3GPP network should allow the MNO to define…." Revision of S1-141041. Revision of S1-141471. Agreed in FMSS drafting session Agreed to be added to the TR |
||||||||
Cont |
Huawei |
Cleanup to align text with in consolidated requirements |
Withdrawn |
|
||||||||
Cont |
China Mobile, Huawei |
Traffic steering Conclusion |
Noted |
For FMSS drafting session: It’s suggested to give the conclusion when completing the consolidated requirements. |
||||||||
Cont |
Huawei |
Consolidation of new requirements agreed in this meeting |
Agreed |
Agreed to be added to the TR |
||||||||
TR |
Rapporteur |
TR22.808 to include agreements at this meeting |
Revised to S1-141604 |
|
||||||||
TR |
Rapporteur |
TR22.808 to include agreements at this meeting |
Agreed |
Revision of S1-141517. Agreed as the basis for future contributions Agreed to be sent for information
No presentation |
||||||||
CP |
Rapporteur |
Cover page |
Revised to S1-141602 |
|
||||||||
CP |
Rapporteur |
Cover page |
Revised to S1-141605 |
Revision of S1-141564. |
||||||||
CP |
Rapporteur |
Cover page |
Approved |
Revision of S1-141564. Revision of S1-141602.
No presentation |
||||||||
8.6.1 FS_FMSS drafting session information |
||||||||||||
AGE |
Rapporteur/Session chair |
FS_FMSS drafting agenda |
Noted |
|
||||||||
REP |
Rapporteur/Session chair |
FS_FMSS drafting report |
Approved |
|
||||||||
Summary of drafting session
5 new use cases and potential requirements (S1-141457, S1-141500, S1-141502, S1-141160, S1-141503) have been agreed to be included in the TR 22.808: - Traffic steering in MVNO scenario - Traffic steering based on QoS information - Service chain status updates - Traffic steering based on APN - Traffic steering based on time/location 1 modification to the existing use case (S1-141456) has been agreed to be included in the TR 22.808. - Traffic Steering based on operator’s policies or user subscription Overview and consolidated requirements have been agreed to be included in the TR 22.808. The main discussion points: - Gi-LAN definition - The interaction between 3GPP network and Gi-LAN is both directions or just one direction - Who defines the steering policy, MNO or 3GPP network
|
||||||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
8.7 FS_ECIP: Enhanced Calling Information Presentation [SP-130598] |
||||||||||||
Work status prior to this meeting: Latest draft: TR 22.810 v0.2.1 Target completion date: SA#65 (09/2014) Percentage completion: 40%
|
||||||||||||
Huawei, China Mobile |
ECIP Introduction |
Revised to S1-141355 |
For ECIP drafting session |
|||||||||
Cont |
Huawei, China Mobile |
ECIP Introduction |
Agreed |
For ECIP drafting session Revision of S1-141157. Agreed in ECIP drafting session Agreed to be added to the TR |
||||||||
Cont |
Huawei, China Mobile |
ECIP Scope |
Agreed |
For ECIP drafting session Agreed in ECIP drafting session |
||||||||
Cont |
Huawei, China Mobile |
ECIP – update to References, Definitions and Abbreviations |
Revised to S1-141356 |
For ECIP drafting session |
||||||||
Cont |
Huawei, China Mobile |
ECIP – update to References, Definitions and Abbreviations |
Agreed |
For ECIP drafting session Revision of S1-141159. Agreed in ECIP drafting session Agreed to be added to the TR |
||||||||
Cont |
NSN, China Mobile, Huawei |
Definition for Enhanced Call Information |
Revised to S1-141357 |
For ECIP drafting session |
||||||||
Cont |
NSN, China Mobile, Huawei |
Definition for Enhanced Call Information |
Agreed |
For ECIP drafting session Revision of S1-141014. Agreed in ECIP drafting session |
||||||||
Cont |
NSN, China Mobile, Huawei |
Clarification of user vs. calling and called party |
Revised to S1-141358 |
For ECIP drafting session |
||||||||
Cont |
NSN, China Mobile, Huawei |
Clarification of user vs. calling and called party |
Agreed |
For ECIP drafting session Revision of S1-141015. Agreed in ECIP drafting session |
||||||||
Cont |
NSN, China Mobile, Huawei |
Clarification on media types |
Agreed |
For ECIP drafting session Agreed in ECIP drafting session |
||||||||
Cont |
China Mobile |
Contents of Enhanced Calling Information |
Revised to S1-141359 |
For ECIP drafting session |
||||||||
Cont |
China Mobile |
Contents of Enhanced Calling Information |
Agreed |
For ECIP drafting session Revision of S1-141175. Agreed in ECIP drafting session |
||||||||
Cont |
NSN, China Mobile, Huawei |
Timing of information transfer |
Agreed |
For ECIP drafting session Agreed in ECIP drafting session |
||||||||
Cont |
NSN |
Clarification on Pre-conditions |
Revised to S1-141360 |
For ECIP drafting session |
||||||||
Cont |
NSN |
Clarification on Pre-conditions |
Withdrawn |
For ECIP drafting session Revision of S1-141018. |
||||||||
Cont |
NSN |
Clarification on Service flows |
Revised to S1-141361 |
For ECIP drafting session |
||||||||
Cont |
NSN |
Clarification on Service flows |
Withdrawn |
For ECIP drafting session Revision of S1-141019. |
||||||||
Cont |
NSN |
Update to Potential Requirements |
Revised to S1-141362 |
For ECIP drafting session |
||||||||
Cont |
NSN |
Update to Potential Requirements |
Withdrawn |
For ECIP drafting session Revision of S1-141020. |
||||||||
Cont |
Orange |
ECIP use case on calling party side – information blocked |
Revised to S1-141445 |
For ECIP drafting session |
||||||||
Cont |
Orange |
ECIP use case on calling party side – information blocked |
Agreed |
For ECIP drafting session Revision of S1-141044. Agreed to be added to the TR |
||||||||
Cont |
Orange |
ECIP use case on calling party side – Text call per call |
Revised to S1-141555 |
|
||||||||
Cont |
Orange |
ECIP use case on calling party side – Text call per call |
Agreed |
Revision of S1-141045. Agreed to be added to the TR |
||||||||
Cont |
Orange |
ECIP use case on calling party side – Important communication information |
Noted |
|
||||||||
Cont |
China Mobile |
Relation with other services |
Noted |
|
||||||||
Cont |
China Mobile |
Conclusion of FS_ECIP |
Noted |
|
||||||||
TR |
Rapporteur |
TR22.810 to include agreements at this meeting |
Revised to S1-141593 |
No presentation |
||||||||
TR |
Rapporteur |
TR22.810 to include agreements at this meeting |
Agreed |
Agreed as the basis for future contributions Agreed to be sent for information Revision of S1-141518.
No presentation |
||||||||
CP |
Rapporteur |
Cover page |
Revised to S1-141603 |
|
||||||||
CP |
Rapporteur |
Cover page |
Agreed |
Revision of S1-141307.
No presentation |
||||||||
8.7.1 FS_ECIP drafting session information |
||||||||||||
AGE |
Rapporteur/Session chair |
FS_ECIP drafting agenda |
Noted |
|
||||||||
REP |
Rapporteur/Session chair |
FS_ECIP drafting report |
Approved |
|
||||||||
Summary of drafting session
The following were agreed: · Introduction, Scope · References, Definitions Abbreviations · Definitions for ECIP · Contents of Enhanced Calling Information · Timing of information transfer · Clarification on media types · Clarification of user vs. calling and called party
|
||||||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
|
|
Tdoc number for allocation in drafting session |
Drafting |
|
||||||||
8.8 FS_MBSP: Multimedia Broadcast Supplement for PWS [SP-130599] |
||||||||||||
Work status prior to this meeting: Latest draft: TR 22.815 v0.2.1 Target completion date: SA#65 (09/2014) Percentage completion: 40%
|
||||||||||||
Cont |
Qualcomm Inc |
Initiation of multimedia broadcast supplemental to PWS |
Revised to S1-141485 |
|
||||||||
Cont |
Qualcomm Inc |
Initiation of multimedia broadcast supplemental to PWS |
Agreed |
Revision of S1-141087. Agreed to be added to the TR |
||||||||
Cont |
Sprint |
PWS multi-media broadcast areas |
Revised to S1-141484 |
|
||||||||
Cont |
Sprint |
PWS multi-media broadcast areas |
Agreed |
Revision of S1-141178. Agreed to be added to the TR |
||||||||
Cont |
Sprint |
PWS multi-media linked messages |
Revised to S1-141487 |
|
||||||||
Cont |
Sprint |
PWS multi-media linked messages |
Agreed |
Revision of S1-141179. Agreed to be added to the TR |
||||||||
Cont |
Sprint |
Multi-media PWS capable UEs in a PLMN only broadcasting text PWS |
Revised to S1-141488 |
|
||||||||
Cont |
Sprint |
Multi-media PWS capable UEs in a PLMN only broadcasting text PWS |
Agreed |
Revision of S1-141196. Agreed to be added to the TR |
||||||||
Cont |
Sprint |
Separated text and multi-media PWS messages |
Revised to S1-141491 |
|
||||||||
Cont |
Sprint |
Separated text and multi-media PWS messages |
Agreed |
Revision of S1-141249. Agreed to be added to the TR |
||||||||
TR |
Rapporteur |
TR22.815 to include agreements at this meeting |
Agreed |
Agreed as the basis for future contributions No presentation |
||||||||
8.9 FS_GUSH: RAN Sharing Enhancements on GERAN and UTRAN [SP-140073] |
||||||||||||
Work status prior to this meeting: Existing TR 22.852 to be updated Target completion date: SA#65 (09/2014) Percentage completion: 0%
|
||||||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 1 (Scope) |
Revised to S1-141460 |
WI code FS_GUSH Rel-13 CR0001R- Cat D |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 1 (Scope) |
Agreed |
WI code FS_GUSH Rel-13 CR0001R- Cat D Revision of S1-141088.
No presentation |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 3 (Definitions, Symbols & Abbreviations) |
Revised to S1-141461 |
WI code FS_GUSH Rel-13 CR0002R- Cat D |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 3 (Definitions, Symbols & Abbreviations) |
Agreed |
WI code FS_GUSH Rel-13 CR0002R- Cat D Revision of S1-141089. For GUSH drafting session Agreed in GUSH drafting session |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 4.1.2 (What Constitutes a Shared RAN) |
Revised to S1-141462 |
WI code FS_GUSH Rel-13 CR0003R- Cat D |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 4.1.2 (What Constitutes a Shared RAN) |
Agreed |
WI code FS_GUSH Rel-13 CR0003R- Cat D Revision of S1-141090.
No presentation |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 4.2 (Scenario and use case 1) |
Revised to S1-141463 |
WI code FS_GUSH Rel-13 CR0004R- Cat C |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 4.2 (Scenario and use case 1, RAN Sharing Monitoring) |
Agreed |
WI code FS_GUSH Rel-13 CR0004R- Cat C Revision of S1-141091. For GUSH drafting session Agreed in GUSH drafting session |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 4.6 (Scenario and use case 5.a) |
Revised to S1-141464 |
WI code FS_GUSH Rel-13 CR0005R- Cat C |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 4.6 (Scenario and use case 5.a, Asymmetric RAN Resource Allocation) |
Agreed |
WI code FS_GUSH Rel-13 CR0005R- Cat C Revision of S1-141092.
No presentation |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 4.9 (Scenario and use case 7) |
Revised to S1-141465 |
WI code FS_GUSH Rel-13 CR0006R- Cat C |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 4.9 (Scenario and use case 7, On-demand Automated Capacity Brokering) |
Agreed |
WI code FS_GUSH Rel-13 CR0006R- Cat C Revision of S1-141093.
No presentation |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 4.14 (Scenario and use case 12) |
Revised to S1-141365 |
WI code FS_GUSH Rel-13 CR0007R- Cat D For GUSH drafting session |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 4.14 (Scenario and use case 12, PLMN selection enhancements towards a shared RAN) |
Agreed |
WI code FS_GUSH Rel-13 CR0007R- Cat D For GUSH drafting session: Note 2 deleted Revision of S1-141094. Agreed in GUSH drafting session |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Add new Section 4.16 (Scenario and use case 14) |
Revised to S1-141466 |
WI code FS_GUSH Rel-13 CR0008R- Cat B |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Add new Section 4.16 (Scenario and use case 14) |
Revised to S1-141366 |
WI code FS_GUSH Rel-13 CR0008R- Cat B Revision of S1-141095. For GUSH drafting session |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Add new Section 4.16 (Scenario and use case 14, Common Network Shared by Multiple Operators) |
Agreed |
WI code FS_GUSH Rel-13 CR0008R- Cat B Revision of S1-141095. For GUSH drafting session Revision of S1-141466. Agreed in GUSH drafting session |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Add new Section 4.17 (Scenario and use case 15) |
Revised to S1-141467 |
WI code FS_GUSH Rel-13 CR0009R- Cat B |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Add new Section 4.17 (Scenario and use case 15) |
Revised to S1-141367 |
WI code FS_GUSH Rel-13 CR0009R- Cat B Revision of S1-141096. For GUSH drafting session |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Add new Section 4.17 (Scenario and use case 15, Interworking between shared RATs) |
Agreed |
WI code FS_GUSH Rel-13 CR0009R- Cat B Revision of S1-141096. For GUSH drafting session Revision of S1-141467. Agreed in GUSH drafting session |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 5 (Considerations) |
Revised to S1-141468 |
WI code FS_GUSH Rel-13 CR0010R- Cat C |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 5 (Considerations) |
Agreed |
WI code FS_GUSH Rel-13 CR0010R- Cat C Revision of S1-141097.
No presentation |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 6 (Potential Requirements) |
Revised to S1-141469 |
WI code FS_GUSH Rel-13 CR0011R- Cat C |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 6 (Potential Requirements) |
Revised to S1-141368 |
WI code FS_GUSH Rel-13 CR0011R- Cat C Revision of S1-141098. For GUSH drafting session |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 6 (Potential Requirements) |
Agreed |
WI code FS_GUSH Rel-13 CR0011R- Cat C Revision of S1-141098. For GUSH drafting session Revision of S1-141469. |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 7 (Conclusion and recommendations) |
Revised to S1-141470 |
WI code FS_GUSH Rel-13 CR0012R- Cat D |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 7 (Conclusion and recommendations) |
Revised to S1-141369 |
WI code FS_GUSH Rel-13 CR0012R- Cat D Revision of S1-141099. For GUSH drafting session |
||||||||
CR |
Telefonica |
22.852 v12.0.0: Update to Section 7 (Conclusion and recommendations) |
Agreed |
WI code FS_GUSH Rel-13 CR0012R- Cat D Revision of S1-141099. For GUSH drafting session: Check the number of UCs Revision of S1-141470. |
||||||||
8.9.1 FS_GUSH drafting session information |
||||||||||||
AGE |
Rapporteur/Session chair |
FS_GUSH drafting agenda |
Noted |
|
||||||||
REP |
Rapporteur/Session chair |
FS_GUSH drafting report |
Approved |
|
||||||||
Summary of drafting session
S1-141094 – It was agreed to remove note 2 since this TR now addresses GERAN and UTRAN
S1-141466 – It was agreed to remove paragraph 2 (“Each participating Operator shall be able to receive…..”) in Requirements section and to replace by new paragraph to say “The Hosting RAN shall be able to provide an indication to each participating operator of how much capacity they have according to the Hosting RAN operator’s setting (Signalling and User traffic may be separately identified).
S1-141467 - Agreed Editor’s Note that was deleted. Agreed to delete Note 1 and to replace it by a statement at the start of the Requirements section to say “The following requirements shall apply only if the UE is in automatic selection mode.”. Agreed to delete Note 2 concerning reference to Use Case 12 since this is now considered as irrelevant. A new Note was agreed to say “It is assumed that there is no impact on the ME”. It was agreed to change the first 2 requirements to say “Based on HPLMN operator policy….” i.e. amended to add “HPLMN”. The revisions are in S1-141367 and were 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 |
|
||||||||
8.10 FS_UC_SPOOF: Service aspects for dealing with User Control over spoofed calls [SP-140074] |
||||||||||||
Work status prior to this meeting: TR 22.898 allocated Target completion date: SA#66 (12/2014) Percentage completion: 0%
|
||||||||||||
TR |
Rapporteur |
Proposed skeleton for UC_SPOOF TR |
Agreed |
Agreed as the basis for contributions at this meeting |
||||||||
Cont |
Sprint |
Proposed TR Scope |
Agreed |
Agreed to be added to the TR |
||||||||
Cont |
Sprint |
Proposed TR Introduction |
Revised to S1-141492 |
|
||||||||
Cont |
Sprint |
Proposed TR Introduction |
Agreed |
Revision of S1-141065.
Agreed to be added to the TR No presentation |
||||||||
Cont |
LG Electronics, Inc. |
Discussion on integrity-protected caller ID |
Noted |
|
||||||||
Cont |
Sprint |
User reporting a spoofed call use case |
Revised to S1-141493 |
|
||||||||
Cont |
Sprint |
User reporting a spoofed call use case |
Agreed |
Revision of S1-141250. Agreed to be added to the TR |
||||||||
Cont |
Sprint |
User reporting a call incorrectly identified as spoofed use case |
Revised to S1-141494 |
|
||||||||
Cont |
Sprint |
User reporting a call incorrectly identified as spoofed use case |
Agreed |
Revision of S1-141251. Agreed to be added to the TR |
||||||||
Cont |
Sprint |
User retrieval of spoofed call history |
Revised to S1-141495 |
|
||||||||
Cont |
Sprint |
User retrieval of spoofed call history |
Agreed |
Revision of S1-141252. Agreed to be added to the TR |
||||||||
TR |
Rapporteur |
TR22.898 to include agreements at this meeting |
Agreed |
Agreed as the basis for future contributions No presentation |
||||||||
No contributions to this agenda item
|
||||||||||||
MCC |
Extract of the 3GPP Work Plan for SA1#66 |
Noted |
|
|||||||||
Rapporteur (Alcatel-Lucent) |
IMS_Corp2 status update |
Approved |
|
|||||||||
REP |
Rapporteur (KPN) |
SEES status update |
Approved |
|
||||||||
REP |
Rapporteur (US Department of Commerce) |
MCPTT status update |
Approved |
|
||||||||
REP |
Rapporteur (Alcatel-Lucent) |
eWebRTCi status update |
Approved |
|
||||||||
REP |
Rapporteur (General Dynamics Broadband) |
IOPS status update |
Approved |
|
||||||||
REP |
Rapporteur (KPN) |
SRMMTC status update |
Withdrawn |
|
||||||||
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 |
Approved |
|
||||||||
REP |
Rapporteur (Intel) |
FS_CSIPTO status update |
Approved |
|
||||||||
REP |
Rapporteur (KPN) |
eICBD status update |
Approved |
|
||||||||
REP |
Rapporteur (China Mobile) |
FS_FMSS status update |
Approved |
Completion at 70% was agreed and not 80% |
||||||||
REP |
Rapporteur (China Mobile) |
FS_ECIP status update |
Approved |
|
||||||||
REP |
Rapporteur (Qualcomm) |
FS_MBSP status update |
Approved |
|
||||||||
REP |
Rapporteur (Telefonica) |
FS_GUSH status update |
Revised to S1-141588 |
|
||||||||
REP |
Rapporteur (Telefonica) |
FS_GUSH status update |
Approved |
Revision of S1-141276. |
||||||||
REP |
Rapporteur (Sprint) |
FS_UC_SPOOF status update |
Approved |
|
||||||||
REP |
Rapporteur |
ACDC status update |
Approved |
|
||||||||
REP |
Rapporteur |
CSIPTO status update |
Approved |
|
||||||||
REP |
Rapporteur |
ProSeM status update |
Approved |
|
||||||||
REP |
Rapporteur |
SRM_GCSE_LTE status update |
Approved |
|
||||||||
REP |
Rapporteur |
VoLTE paging distinction status update |
Approved |
|
||||||||
REP |
Rapporteur |
Enhancements to User Location Reporting status update |
Approved |
|
||||||||
REP |
Rapporteur |
FS_CATS status update |
Approved |
|
||||||||
WG Chairman |
Requirement numbering: updated to include proposal for existing TS under change control |
Noted |
|
|||||||||
No contributions to this agenda item
|
||||||||||||
2014 meetings: 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 San Francisco, USA Mega meeting
2015 meetings: SA1#69 02 – 06 Feb 2015 China (TBD) SA1#70 13 – 17 Apr 2015 North America (TBD) Co-located with SA2 SA1#71 17 – 21 Aug 2015 Belgrade, Serbia (TBC) SA1#72 16 – 20 Nov 2015 North America (TBD) Mega meeting
|
||||||||||||
Close by 16:30 on Friday
|
||||||||||||
13 Withdrawn documents (admin purposes only) |
||||||||||||
|
Alcatel-Lucent |
Disadvantages of UICC based solution |
Withdrawn |
|
||||||||
|
KDDI |
Additional Use Case to Address Third Party OTT Server Issues |
Withdrawn |
|
||||||||
|
Rapporteur |
Addition of Requirement Numbers to TR22.828 |
Withdrawn |
|
||||||||
|
Rapporteur |
Addition of Requirement Numbers to TR22.828 |
Withdrawn |
|
||||||||
|
Rapporteur |
Addition of Requirement Numbers to TR22.828 |
Withdrawn |
|
||||||||
|
NSN |
Correction to use case on network congestion |
Withdrawn |
|
||||||||
|
Sprint |
Proposed UC_SPOOF Scope |
Withdrawn |
|
||||||||
|
KDDI |
Coping with Third Party Server Issues |
Withdrawn |
|
||||||||
|
LG Electronics, Inc. |
Discussion on integrity-protected caller ID |
Withdrawn |
|
||||||||
|
LG Electronics, Inc. |
Discussion on integrity-protected caller ID |
Withdrawn |
|
||||||||
|
NSN |
Proposed LS on WebRTC Security to Sa3 and SA3 LI |
Withdrawn |
Not available |
||||||||
14 Document numbers to be allocated (admin purposes only) |
||||||||||||
|
|
|
Unallocated |
|
||||||||
|
|
|
Unallocated |
|
||||||||
|
|
|
Unallocated |
|
||||||||
|
|
|
Unallocated |
|
||||||||
|
|
|
Mona to allocate |
|
||||||||
|
|
|
Mona to allocate |
|
||||||||
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)
6 Rel-12 and earlier contributions
6.1 IMS_Corp2 (Rel-12): Transfer of ETSI business trunking specifications [SP-140170]
6.2 Other Rel-12 and earlier contributions
7 Rel-13 Work Item contributions
7.1 SEES: Service Exposure and Enablement Support [SP-130505]
7.1.1 SEES drafting session information
7.2 MCPTT: Mission Critical Push To Talk over LTE [SP-130728]
7.2.1 MCPTT drafting session information
7.3 eWebRTCi: Enhancements to WebRTC interoperability [SP-140166]
7.4 IOPS: Isolated E-UTRAN Operation for Public Safety [SP-140167]
7.4.1 IOPS/FS_IOPS drafting session information
7.5 SRMMTC: Service Requirements Maintenance for MTC [SP-130600]
8.1 FS_ACDC: Application specific congestion control for data communication [SP-130415]
8.1.1 FS_ACDC drafting session information
8.2 FS_IOPS: Isolated E-UTRAN operation for Public Safety [SP-130596]
8.3 FS_MAPN: Need for multiple APNs [SP-130416]
8.4 FS_CSIPTO: Co-ordinated P-GW change for SIPTO [SP-130417]
8.5 FS_eICBD: Enhancements for infrastructure based data communication between devices [SP-130418]
8.6 FS_FMSS: Flexible Mobile Service Steering [SP-130597]
8.6.1 FS_FMSS drafting session information
8.7 FS_ECIP: Enhanced Calling Information Presentation [SP-130598]
8.7.1 FS_ECIP drafting session information
8.8 FS_MBSP: Multimedia Broadcast Supplement for PWS [SP-130599]
8.9 FS_GUSH: RAN Sharing Enhancements on GERAN and UTRAN [SP-140073]
8.9.1 FS_GUSH drafting session information
8.10 FS_UC_SPOOF: Service aspects for dealing with User Control over spoofed calls [SP-140074]
8.11 Other Study Item contributions
9.2 Work Item/Study Item status update
9.3 SA1 process improvements/updates
13 Withdrawn documents (admin purposes only)
14 Document numbers to be allocated (admin purposes only)