Tdoc List
2016-07-15 11:15
Agenda | Topic | TDoc | Title | Source | Type | For | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Opening of the meeting |   | ||||||||||
2 | Approval of the agenda | S5‑164000 | Agenda | WG Chairman | agenda | Yes |
Yes
| approved | No | |||
3 | IPR declaration | S5‑164033 | IPR and legal declaration | WG Chairman | other | Yes |
YesThe attention of the delegates to the meeting of this Technical Specification Group was 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.
The delegates were asked to take note that they were thereby invited:
to investigate whether their organization or any other organization owns IPRs which were, or were likely to become Essential in respect of the work of 3GPP.
to notify their respective Organizational Partners of all potential IPRs, e.g., for ETSI, by means of the IPR Information Statement and the Licensing declaration forms.
The attention of the delegates to the meeting was drawn to the fact that 3GPP activities were subject to all applicable antitrust and competition laws and that compliance with said laws was therefore required by any participant of the meeting, including the Chairman and Vice-Chairmen and were invited to seek any clarification needed with their legal counsel. The leadership would conduct the present meeting with impartiality and in the interests of 3GPP. Delegates were reminded that timely submission of work items in advance of TSG/WG meetings was important to allow for full and fair consideration of such matters.
| noted | No | |||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑164001 | Report from last SA5 meeting | ETSI Secretariat | report | Yes |
Yes
| approved | No | |||
4.2 | Last SA meeting report | S5‑164002 | SA5 status report at last SA meeting | WG Chairman | report | Yes |
Yes
| noted | No | |||
S5‑164003 | SA5 results at last SA meeting | WG Chairman | report | Yes |
Yes
| noted | No | |||||
4.3 | Inter-organizational reports | S5‑164162 | Report of methodology coordination meeting with ITU-T SG2 | Ericsson LM | report | Information | Yes |
Yes
| noted | No | ||
5 | Cross-SWG issues |   | ||||||||||
5.1 | Administrative issues at SA5 level | S5‑164006 | Leaders meeting agenda | WG Chairman | agenda | Yes |
Yes
| noted | No | |||
S5‑164007 | Leaders meeting minutes | WG Chairman | report | Yes |
Yes
| noted | No | |||||
S5‑164011 | SA5 Working Procedures | WG Vice Chair (Huawei) | other | Yes |
Yes
| revised | No | S5‑164179 | ||||
S5‑164179 | SA5 Working Procedures | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| revised | No | S5‑164200 | S5‑164011 | ||
S5‑164200 | SA5 Working Procedures | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| approved | No | S5‑164179 | |||
S5‑164012 | SA5 Meeting Facility Requirements | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||||
S5‑164013 | Process for management of draft TSs/TRs | WG Chairman | other | Yes |
Yes
| noted | No | |||||
S5‑164014 | CR Quality Check | ETSI Secretariat | other | Yes |
Yes
| noted | No | |||||
S5‑164034 | Status of email approvals | WG Vice Chair (Orange) | other | No |
No
| reserved | No | |||||
S5‑164163 | Requirements template (high-level) example | Ericsson LM | other | Approval | Yes |
Yes
| agreed | No | ||||
S5‑164164 | Requirements template (simplified) example | Ericsson LM | other | Approval | Yes |
Yes
| agreed | No | ||||
5.2 | Technical issues at SA5 level |   | ||||||||||
5.3 | Liaison statements at SA5 level | S5‑164159 | LS from SA to SA5 on I-WLAN handling and specification withdrawal | SP-160508 | LS in | Yes |
YesThe Chairman commented that this work was finished at SA5 level. There seems to be a major impact on other groups' work, and there might be some little work left to do in SA5 although Thomas believed that this was unlikely.
| noted | No | |||
5.4 | SA5 meeting calendar | S5‑164010 | SA5 Meeting Calendar | WG Vice Chair(Huawei) | other | Yes |
Yes
| noted | No | |||
5.5 | Review of the Work Plan | S5‑164015 | Deliverables due for the NEXT SA Plenary | ETSI Secretariat | other | Yes |
Yes
| noted | No | |||
S5‑164016 | Ongoing SA5 WIDs and SIDs | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||||
S5‑164017 | SA5 3GPP Work Plan | ETSI Secretariat | other | Yes |
Yes
| noted | No | |||||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑164004 | Time Plan for OAM&P | WG Vice Chair (Huawei) | other | Yes |
Yes
| revised | No | S5‑164247 | ||
S5‑164247 | Time Plan for OAM&P | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| noted | No | S5‑164004 | |||
S5‑164005 | OAM Executive Report from THIS Meeting | WG Vice Chair (Huawei) | report | Yes |
Yes
| noted | No | |||||
S5‑164036 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | Yes |
Yes
| revised | No | S5‑164303 | ||||
S5‑164303 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| noted | No | S5‑164036 | |||
S5‑164046 | LS from ETSI TC NTECH to SA5 on Autonomic Networking applied to 3GPP Core and Backhaul parts | ETSI TC NTECH | LS in | Yes |
YesThis LS was already replied during last meeting.
| noted | No | |||||
S5‑164047 | Liaison Statement to 3GPP SA2 and 3GPP SA5 from ETSI NTECH | ETSI TC NTECH | LS in | Yes |
Yes
| replied to | No | |||||
S5‑164167 | Reply to: Liaison Statement to 3GPP SA2 and 3GPP SA5 from ETSI NTECH | Huawei | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑164048 | Minutes of OAM&P SWG opening session | WG Chairman | report | Information | Yes |
Yes
| noted | No | ||||
S5‑164107 | LS from ATIS to SA5 on Establish a Metric to Determine a Drop in Registered Users in an IP-Based Network | Alliance for Telecommunications Industry Solutions (ATIS) | LS in | Yes |
YesMCC suggested that a WID may be necessary.
Nokia commented that a WID would not be necessary as it would bring too much overheard, a simple CR should do.
The Chairman asked for contributors or supporters to carry this work, it may require just a CR.
| postponed | No | |||||
S5‑164147 | LS from SA4 cc SA5 on QoE reporting for streaming services | S4-160866 | LS in | Yes |
Yes
| noted | No | |||||
S5‑164165 | ETSI NTECH LS TR presentation | Ericsson LM | other | Yes |
Yes
| noted | No | |||||
6.2 | New OAM&P Work Item proposals | S5‑164018 | Minutes of New Work Item proposals - OAM&P | WG Vice Chair (Orange) | report | Yes |
Yes
| noted | No | |||
S5‑164135 | NEW SID Study on management of the virtualized RAN | Intel Corporation (UK) Ltd | SID new | Agreement | Yes |
Yes
| revised | No | S5‑164168 | |||
S5‑164168 | NEW SID Study on management of the virtualized RAN | Intel Corporation (UK) Ltd | SID new | Agreement | Yes |
Yes
| postponed | No | S5‑164135 | |||
S5‑164225 | NEW SID Study on management of the virtualized RAN | Intel Corporation (UK) Ltd | SID new | Agreement | No |
No
| withdrawn | Yes | ||||
S5‑164224 | LS to RAN3 on management of VRAN | Intel | LS out | Approval | Yes |
Yes
| revised | No | S5‑164305 | |||
S5‑164305 | LS to RAN3 on management of VRAN | Intel | LS out | Approval | No |
Yes
| left for email approval | No | S5‑164224 | |||
6.3 | OAM&P Maintenance and Rel-14 small Enhancements | S5‑164019 | Minutes of OAM&P Maintenance and Rel-14 small Enhancements | MCC | report | Yes |
Yes
| noted | No | |||
S5‑164049 | Rel-13 CR 28663 Correction in XML code | MCC | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑164050 | Rel-13 CR 28.656 Correct the link from IRP Solution Set to IRP Information Service | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑164117 | Discussin paper on usage of imported information entities | Nokia, Alcatel-Lucent Shanghai Bell | discussion | Decision | Yes |
Yes
| noted | No | ||||
S5‑164118 | pCR to draft CR 32.157 Add associated informaiton entities to the IS template | Nokia, Alcatel-Lucent Shanghai Bell | draftCR | Approval | Yes |
Yes
| revised | No | S5‑164201 | |||
S5‑164201 | pCR to draft CR 32.157 Add associated informaiton entities to the IS template | Nokia, Alcatel-Lucent Shanghai Bell | draftCR | Approval | Yes |
Yes
| approved | No | S5‑164118 | |||
S5‑164226 | Draft CR 32.157 | Ericsson | draftCR | Approval | No |
Yes
| left for email approval | No | ||||
6.4 | Rel-14 Operations, Administration, Maintenance and Provisioning (OAM&P) |   | ||||||||||
6.4.1 | Management of mobile networks that include virtualized network functions |   | ||||||||||
6.4.1.1 | Management concept, architecture and requirements for mobile networks that include virtualized network functions | S5‑164022 | Minutes for Management concept, architecture and requirements for mobile networks that include virtualized network functions | Rapporteur(China Mobile) | report | Yes |
Yes
| noted | No | |||
S5‑164088 | pCR TS 28.500 Add business level use case of NE deployment in the context of NFV | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164169 | |||
S5‑164169 | pCR TS 28.500 Add business level use case of NE deployment in the context of NFV | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164227 | S5‑164088 | ||
S5‑164227 | pCR TS 28.500 Add business level use case of NE deployment in the context of NFV | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑164169 | |||
S5‑164092 | pCR TS 28.500 Adding business UC and reqs on querying and modification of non-application VNF instance information | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑164171 | |||
S5‑164171 | pCR TS 28.500 Adding business UC and reqs on querying and modification of non-application VNF instance information | NTT DOCOMO, China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑164092 | |||
S5‑164095 | pCR TS 28.500 Clarifications on the description of NM and reference points in the Management Architecture | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑164172 | |||
S5‑164172 | pCR TS 28.500 Clarifications on the description of NM and reference points in the Management Architecture | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑164228 | S5‑164095 | ||
S5‑164228 | pCR TS 28.500 Clarifications on the description of NM and reference points in the Management Architecture | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑164172 | |||
S5‑164096 | pCR TS 28.500 General fixes to terminology used in requirements and adding some references | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑164173 | |||
S5‑164173 | pCR TS 28.500 General fixes to terminology used in requirements and adding some references | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑164229 | S5‑164096 | ||
S5‑164229 | pCR TS 28.500 General fixes to terminology used in requirements and adding some references | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑164173 | |||
S5‑164097 | pCR TS 28.500 Adding business UC and reqs on keeping updated an NS instance | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑164174 | |||
S5‑164174 | pCR TS 28.500 Adding business UC and reqs on keeping updated an NS instance | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑164259 | S5‑164097 | ||
S5‑164259 | pCR TS 28.500 Adding business UC and reqs on keeping updated an NS instance | NTT DOCOMO | pCR | Approval | No |
Yes
| left for email approval | No | S5‑164174 | |||
S5‑164125 | pCR TS 28.500 Adding policy management requirements | China Mobile Com. Corporation | CR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑164127 | pCR TS 28.500 Adding policy management requirements | China Mobile Com. Corporation | pCR | Yes |
Yes
| revised | No | S5‑164175 | ||||
S5‑164175 | pCR TS 28.500 Adding policy management requirements | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| noted | No | S5‑164127 | |||
S5‑164128 | pCR TS 28.500 Adding CM requirements | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑164170 | |||
S5‑164170 | pCR TS 28.500 Adding CM requirements | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑164260 | S5‑164128 | ||
S5‑164260 | pCR TS 28.500 Adding CM requirements | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑164170 | |||
S5‑164129 | pCR TS 28.500 Adding retrieving information requirements | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| merged | No | S5‑164171 | |||
S5‑164265 | Draft TS 28.500 | Rapporteur (ZTE) | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
6.4.1.2 | Configuration Management for mobile networks that include virtualized network functions | S5‑164023 | Minutes for Configuration Management for mobile networks that include virtualized network functions | Rapporteur(ZTE) | report | Yes |
Yes
| noted | No | |||
S5‑164037 | TS 28.510 Add UC NM retrieves VNFs info maintained by mgmt sys | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑164176 | |||
S5‑164176 | TS 28.510 Add UC NM retrieves VNFs info maintained by mgmt sys | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑164261 | S5‑164037 | ||
S5‑164261 | TS 28.510 Add UC NM retrieves VNFs info maintained by mgmt sys | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑164294 | S5‑164176 | ||
S5‑164294 | TS 28.510 Add UC NM retrieves VNFs info maintained by mgmt sys | Ericsson Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑164261 | |||
S5‑164069 | Draft TS 28.512 skeleton | ZTE Corporation | draft TS | Approval | Yes |
Yes
| revised | No | S5‑164177 | |||
S5‑164177 | Draft TS 28.512 skeleton | ZTE Corporation | draft TS | Approval | Yes |
Yes
| approved | No | S5‑164069 | |||
S5‑164070 | pCR TS 28.512 Add introduction and scope | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑164071 | pCR TS 28.512 Add description of Itf-N operation | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑164072 | pCR draft TS 28.511 Add procedure of creating MOI(s) after a VNF is instantiated | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑164073 | pCR draft TS 28.511 Add procedure of deleting MOI(s) corresponding to a VNF instance | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑164089 | Correlation of MO creation and VNF instantiation | Huawei Tech.(UK) Co., Ltd | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑164178 | |||
S5‑164178 | Correlation of MO creation and VNF instantiation | Huawei Tech.(UK) Co., Ltd | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑164202 | S5‑164089 | ||
S5‑164202 | Correlation of MO creation and VNF instantiation | Huawei Tech.(UK) Co., Ltd | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑164223 | S5‑164178 | ||
S5‑164223 | Potential use cases for relationship between MO creation and VNF instantiation | Huawei Tech.(UK) Co., Ltd,Ericsson,Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑164262 | S5‑164202 | ||
S5‑164262 | Potential use cases for relationship between MO creation and VNF instantiation | Huawei Tech.(UK) Co., Ltd,Ericsson,Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑164223 | |||
S5‑164090 | pCR TS 28.511 Adding procedure flow for VNF instantiation triggered by MO creation | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑164093 | pCR TS 28.510 Adding specification UC and reqs on modification of VNF instance non-applicatoin configuration through NFVO as part of NS update | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑164203 | |||
S5‑164203 | pCR TS 28.510 Adding specification UC and reqs on modification of VNF instance non-applicatoin configuration through NFVO as part of NS update | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑164263 | S5‑164093 | ||
S5‑164263 | pCR TS 28.510 Adding specification UC and reqs on modification of VNF instance non-applicatoin configuration through NFVO as part of NS update | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑164203 | |||
S5‑164138 | Relation between create MO and instantiate VNF operations | Ericsson Inc. | other | Discussion | Yes |
Yes
| merged | No | S5‑164202 | |||
S5‑164139 | UCs (on VNF/VNFC realization) requiring NRM support | Ericsson Inc. | other | Discussion | Yes |
Yes
| revised | No | S5‑164204 | |||
S5‑164204 | UCs (on VNF/VNFC realization) requiring NRM support | Ericsson Inc. | other | Endorsement | Yes |
Yes
| revised | No | S5‑164264 | S5‑164139 | ||
S5‑164264 | UCs (on VNF/VNFC realization) requiring NRM support | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑164204 | |||
S5‑164166 | Discussion sequence proposal | ZTE | discussion | discussion | Yes |
Yes
| noted | No | ||||
S5‑164266 | Draft TS 28.510 | Rapprteur(ZTE) | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑164267 | Draft TS 28.512 | Rapporteur(ZTE) | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
6.4.1.3 | Fault Management for mobile networks that include virtualized network functions | S5‑164024 | Minutes for Fault Management for mobile networks that include virtualized network functions | Rapporteur(Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑164038 | Modify UC Virtualization-specific aspect failure detection and notification by VNFM | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑164205 | |||
S5‑164205 | Modify UC Virtualization-specific aspect failure detection and notification by VNFM | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑164269 | S5‑164038 | ||
S5‑164269 | Modify UC Virtualization-specific aspect failure detection and notification by VNFM | Ericsson Inc. | pCR | Approval | Yes |
Yes
| noted | No | S5‑164205 | |||
S5‑164075 | pCR TS 28.515 Remove notes | Huawei Tech.(UK) Co., Ltd | pCR | Yes |
Yes
| approved | No | |||||
S5‑164076 | pCR TS 28.515 Rapporteur changes | Huawei Tech.(UK) Co., Ltd | pCR | Yes |
Yes
| revised | No | S5‑164207 | ||||
S5‑164207 | pCR TS 28.515 Rapporteur changes | Huawei Tech.(UK) Co., Ltd | pCR | - | Yes |
Yes
| approved | No | S5‑164076 | |||
S5‑164077 | pCR TS 28.516 Modification of procedures of NE alarm correlation in the context of NFV | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164208 | |||
S5‑164208 | pCR TS 28.516 Modification of procedures of NE alarm correlation in the context of NFV | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑164077 | |||
S5‑164078 | pCR TS 28.516 Modification of procedures of virtualization-specific aspect failure detection and notification | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164209 | |||
S5‑164209 | pCR TS 28.516 Modification of procedures of virtualization-specific aspect failure detection and notification | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑164078 | |||
S5‑164079 | pCR TS 28.516 Modification of procedure of virtualization-specific aspect healing through operation request to VNFM by EM | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164210 | |||
S5‑164210 | pCR TS 28.516 Modification of procedure of virtualization-specific aspect healing through operation request to VNFM by EM | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164270 | S5‑164079 | ||
S5‑164270 | pCR TS 28.516 Modification of procedure of virtualization-specific aspect healing through operation request to VNFM by EM | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑164210 | |||
S5‑164080 | pCR TS 28.516 Adding alarm data flow | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164211 | |||
S5‑164211 | pCR TS 28.516 Adding alarm data flow | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑164080 | |||
S5‑164081 | pCR TS 28.516 Rapporteur changes | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164212 | |||
S5‑164212 | pCR TS 28.516 Rapporteur changes | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑164081 | |||
S5‑164082 | pCR TS 28.517 Adding VNF alarm reporting stage 2 description on Ve-Vnfm-em | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑164083 | pCR TS 28.517 Adding general descriptions | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164213 | |||
S5‑164213 | pCR TS 28.517 Adding general descriptions | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑164083 | |||
S5‑164084 | pCR TS 28.517 Adding Information Model for Itf-N | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑164085 | Draft TS 28.518 Skeleton proposal | Huawei Tech.(UK) Co., Ltd | draft TS | Approval | Yes |
Yes
| approved | No | ||||
S5‑164086 | pCR TS 28.518 Adding content for introduction and scope | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑164098 | pCR TS 28.515 Adressing Note on recovering virtualization-specific aspect in healing context | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑164206 | |||
S5‑164206 | pCR TS 28.515 Adressing Note on recovering virtualization-specific aspect in healing context | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑164098 | |||
S5‑164268 | Draft TS 28.516 | Rapporteur (Huawei) | draft TS | discussion | No |
Yes
| left for email approval | No | ||||
S5‑164271 | Draft TS 28.515 | Rapporteur (Huawei) | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑164272 | Draft TS 28.517 | Rapporteur (Huawei) | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑164273 | Draft TS 28.518 | Rapporteur (Huawei) | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
6.4.1.4 | Performance management for mobile networks that include virtualized network functions | S5‑164025 | Minutes for Performance management for mobile networks that include virtualized network functions | Rapporteur(Intel) | report | Yes |
Yes
| noted | No | |||
S5‑164039 | Add UC Fetch VNF related VR performance measurements prepared by VNFM | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑164214 | |||
S5‑164214 | Add UC Fetch VNF related VR performance measurements prepared by VNFM | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑164274 | S5‑164039 | ||
S5‑164274 | Add UC Fetch VNF related VR performance measurements prepared by VNFM | Ericsson Inc. | pCR | Approval | Yes |
Yes
| noted | No | S5‑164214 | |||
S5‑164051 | pCR to TR 28.520 Use Case for PM data collection | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑164215 | |||
S5‑164215 | pCR to TR 28.520 Use Case for PM data collection | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑164051 | |||
S5‑164062 | Draft TS 28.522 skeleton | Intel Corporation (UK) Ltd | draft TS | Approval | Yes |
Yes
| revised | No | S5‑164216 | |||
S5‑164216 | Draft TS 28.522 skeleton | Intel Corporation (UK) Ltd | draft TS | Approval | Yes |
Yes
| approved | No | S5‑164062 | |||
S5‑164063 | pCR TS 28.522 add introduction and scope | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑164064 | pCR TS 28.520 correct VNF PM data related to VR terminology | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164217 | |||
S5‑164217 | pCR TS 28.520 correct VNF PM data related to VR terminology | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑164064 | |||
S5‑164065 | pCR TS 28.520 add reference to ETSI GS NFV IFA008 specification | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑164218 | pCR TS 28.520 add reference to ETSI GS NFV IFA008 specification | Intel Corporation (UK) Ltd | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑164066 | pCR TS 28.521 add VR PM data available notification procedure | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164219 | |||
S5‑164219 | pCR TS 28.521 add VR PM data available notification procedure | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164277 | S5‑164066 | ||
S5‑164277 | pCR TS 28.521 add VR PM data available notification procedure | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164299 | S5‑164219 | ||
S5‑164299 | pCR TS 28.521 add VR PM data available notification procedure | Intel Corporation (UK) Ltd | pCR | Approval | No |
Yes
| left for email approval | No | S5‑164277 | |||
S5‑164275 | Draft TS 28.520 | Rapporteur (Intel) | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑164276 | Draft TS 28.522 | Rapporteur (Intel) | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑164304 | Draft TR 28.521 | Rapporteur (Intel) | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.4.1.5 | Lifecycle management for mobile networks that include virtualized network functions | S5‑164026 | Minutes for Lifecycle management for mobile networks that include virtualized network functions | Rapporteur (Nokia Networks) | report | Yes |
Yes
| noted | No | |||
S5‑164052 | pCR to TS 28.525 Delete VNF Package operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑164230 | |||
S5‑164230 | pCR to TS 28.525 Delete VNF Package operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑164052 | |||
S5‑164053 | pCR to TS 28.525 Query VNF Package operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑164054 | pCR to TS 28.525 Subscribe VNF Package operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑164231 | |||
S5‑164231 | pCR to TS 28.525 Subscribe VNF Package operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑164054 | |||
S5‑164055 | pCR to TS 28.525 Use Case on Notify operation on VNF package management interface | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑164056 | pCR to TS 28.525 Fetch VNF Package operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑164232 | |||
S5‑164232 | pCR to TS 28.525 Fetch VNF Package operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑164056 | |||
S5‑164087 | pCR TS 28.525 Adding UC of VNF application software update when application software is not part of VNF Package | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164233 | |||
S5‑164233 | pCR TS 28.525 Adding UC of VNF application software update when application software is not part of VNF Package | Huawei Tech.(UK) Co., Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑164087 | |||
S5‑164099 | pCR TS 28.525 Adding functional requirement related to VNF application software update clause 5.4.4.3.1 | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑164234 | |||
S5‑164234 | pCR TS 28.525 Adding functional requirement related to VNF application software update clause 5.4.4.3.1 | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑164099 | |||
S5‑164100 | pCR TS 28.525 Adding specification UCs and requirements related to updating NS | NTT DOCOMO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑164114 | pCR TS 28.525 Add requirements for NS instance lifecycle change notification | ETRI | pCR | Approval | Yes |
Yes
| revised | No | S5‑164235 | |||
S5‑164235 | pCR TS 28.525 Add requirements for NS instance lifecycle change notification | ETRI | pCR | Approval | Yes |
Yes
| revised | No | S5‑164279 | S5‑164114 | ||
S5‑164279 | pCR TS 28.525 Add requirements for NS instance lifecycle change notification | ETRI | pCR | Approval | Yes |
Yes
| approved | No | S5‑164235 | |||
S5‑164115 | pCR TS 28.525 Use case for NS querying and NS instance termination | ETRI | pCR | Approval | Yes |
Yes
| revised | No | S5‑164116 | |||
S5‑164116 | pCR TS 28.525 Use case for NS querying and NS instance termination | ETRI | pCR | Approval | Yes |
Yes
| revised | No | S5‑164236 | S5‑164115 | ||
S5‑164236 | pCR TS 28.525 Use case for NS querying and NS instance termination | ETRI | pCR | Approval | Yes |
Yes
| revised | No | S5‑164280 | S5‑164116 | ||
S5‑164280 | pCR TS 28.525 Use case for NS querying and NS instance termination | ETRI | pCR | Approval | Yes |
Yes
| revised | No | S5‑164295 | S5‑164236 | ||
S5‑164295 | pCR TS 28.525 Use case for NS querying and NS instance termination | ETRI | pCR | Approval | Yes |
Yes
| approved | No | S5‑164280 | |||
S5‑164131 | pCR TS 28.525 add VNF identifier creation use case and requirements | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164237 | |||
S5‑164237 | pCR TS 28.525 add VNF identifier creation use case and requirements | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164281 | S5‑164131 | ||
S5‑164281 | pCR TS 28.525 add VNF identifier creation use case and requirements | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑164237 | |||
S5‑164132 | pCR TS 28.526 add VNF instantiation procedures | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164239 | |||
S5‑164239 | pCR TS 28.526 add VNF instantiation procedures | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164282 | S5‑164132 | ||
S5‑164282 | pCR TS 28.526 add VNF instantiation procedures | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164297 | S5‑164239 | ||
S5‑164297 | pCR TS 28.526 add VNF instantiation procedures | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164300 | S5‑164282 | ||
S5‑164300 | pCR TS 28.526 add VNF instantiation procedures | Intel Corporation (UK) Ltd | pCR | Approval | No |
Yes
| left for email approval | No | S5‑164297 | |||
S5‑164133 | pCR TS 28.526 add VNF termination procedure | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑164134 | pCR TS 28.526 add VNF scaling procedures | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164240 | |||
S5‑164240 | pCR TS 28.526 add VNF scaling procedures | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164283 | S5‑164134 | ||
S5‑164283 | pCR TS 28.526 add VNF scaling procedures | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑164298 | S5‑164240 | ||
S5‑164298 | pCR TS 28.526 add VNF scaling procedures | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑164283 | |||
S5‑164278 | Draft TS 28.525 | Rapporteur (Nokia) | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑164296 | Draft TS 28.526 | Rapporteur(Nokia) | draft TS | discussion | No |
Yes
| left for email approval | No | ||||
6.4.2 | Filtering of PM measurements and data volume measurements for shared networks | S5‑164027 | Minutes for Filtering of PM measurements and data volume measurements for shared networks | Rapporteur(Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑164113 | pCR TR 32.817 Measurement definitions and PM IRP additions | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑164238 | |||
S5‑164238 | pCR TR 32.817 Measurement definitions and PM IRP additions | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑164113 | |||
S5‑164284 | Draft TR 32.817 | Rapporteur (Ericsson) | draft TR | discussion | No |
Yes
| left for email approval | No | ||||
6.4.3 | OAM support for Licensed Shared Access (LSA) | S5‑164035 | Minutes of OAM support for Licensed Shared Access (LSA) | Rapporteur (Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑164119 | Discussion paper - clarification on NM confirmation | RED Technologies SAS | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑164120 | pCR TS 28 xxx New business level use case - LSA spectrum resource availability change | RED Technologies SAS | other | Approval | Yes |
Yes
| revised | No | S5‑164241 | |||
S5‑164241 | pCR TS 28 xxx New business level use case - LSA spectrum resource availability change | RED Technologies SAS | other | Approval | Yes |
Yes
| approved | No | S5‑164120 | |||
S5‑164121 | pCR TS 28 xxx New business level use case - LC Initialization | RED Technologies SAS | other | Approval | Yes |
Yes
| revised | No | S5‑164242 | |||
S5‑164242 | pCR TS 28 xxx New business level use case - LC Initialization | RED Technologies SAS | other | Approval | Yes |
Yes
| approved | No | S5‑164121 | |||
S5‑164122 | pCR TS 28 xxx New business level use case - Network deployment update | RED Technologies SAS | other | Approval | Yes |
Yes
| revised | No | S5‑164243 | |||
S5‑164243 | pCR TS 28 xxx New business level use case - Network deployment update | RED Technologies SAS | other | Approval | Yes |
Yes
| approved | No | S5‑164122 | |||
S5‑164123 | pCR TS 28 xxx New business level use case - Loss of connectivity with the LR | RED Technologies SAS | other | Approval | Yes |
Yes
| revised | No | S5‑164244 | |||
S5‑164244 | pCR TS 28 xxx New business level use case - Loss of connectivity with the LR | RED Technologies SAS | other | Approval | Yes |
Yes
| approved | No | S5‑164123 | |||
S5‑164124 | pCR TR 28 xxx Definition of interfaces | RED Technologies SAS | other | Approval | Yes |
Yes
| revised | No | S5‑164245 | |||
S5‑164245 | pCR TR 28 xxx Definition of interfaces | RED Technologies SAS | other | Approval | Yes |
Yes
| approved | No | S5‑164124 | |||
S5‑164161 | pCR 28.xxx Add business and specification level requirements incl. use cases | Nokia Networks | other | Yes |
Yes
| revised | No | S5‑164246 | ||||
S5‑164246 | pCR 28.xxx Add business and specification level requirements incl. use cases | Nokia Networks | other | - | Yes |
Yes
| approved | No | S5‑164161 | |||
S5‑164285 | Draft TS 28.301 | Rapporteur (Nokia) | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
6.5 | OAM&P Studies |   | ||||||||||
6.5.1 | Study on OAM support for assessment of energy efficiency in mobile access networks | S5‑164029 | Minutes of Study on OAM support for assessment of energy efficiency in mobile access networks | Rapporteur (Orange) | report | No |
Yes
| withdrawn | Yes | |||
S5‑164044 | Liaison reply from ETSI TC EE to 3GPP SA5 about standard ES 202 336-12 (ICT equipment power, energy and environmental parameters monitoring information model) | ETSI TC EE | LS in | Yes |
Yes
| postponed | No | |||||
S5‑164160 | Liaison from ETSI TC EE to 3GPP SA5 in response to S5-162239 | ETSI TC EE | LS in | Yes |
Yes
| postponed | No | |||||
6.5.2 | Study on OAM aspects of SON for AAS-based deployments | S5‑164028 | Minutes of Filtering of PM measurements and data volume measurements for shared networks | Rapporteur (Ericsson) | report | Yes |
No
| withdrawn | Yes | |||
S5‑164030 | Minutes for Study on OAM aspects of SON for AAS-based deployments | Rapporteur (Nokia Networks) | report | Yes |
Yes
| noted | No | |||||
S5‑164057 | pCR to TR 32.865 Cell splitting merging | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑164248 | |||
S5‑164248 | pCR to TR 32.865 Cell splitting merging | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑164057 | |||
S5‑164058 | pCR to TR 32.865 Geo information from OAM | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑164091 | pCR TR 32.865 Add solutions for OAM aspects of SON for AAS | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑164249 | |||
S5‑164249 | pCR TR 32.865 Add solutions for OAM aspects of SON for AAS | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑164288 | S5‑164091 | ||
S5‑164288 | pCR TR 32.865 Add solutions for OAM aspects of SON for AAS | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | No |
Yes
| left for email approval | No | S5‑164249 | |||
S5‑164286 | Draft TR 32.865 | Rapporteur (Nokia) | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.3 | Study on Implementation for the Partitioning of Itf-N | S5‑164021 | Minutes for Study on Implementation for the Partitioning of Itf-N | Rapporteur(China Mobile) | report | Yes |
Yes
| approved | No | |||
S5‑164137 | pCR TR 32.880 overview of solution sets for Itf-N | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑164250 | |||
S5‑164250 | pCR TR 32.880 overview of solution sets for Itf-N | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑164137 | |||
S5‑164287 | Draft TR 32.880 | Rapporteur (China Mobile) | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.4 | Study on Management and Orchestration Architecture of Next Generation Network and Service | S5‑164020 | Minutes for Study on Management and Orchestration Architecture of Next Generation Network and Service | Rapporteur (Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑164104 | Draft TR 28.800 skeleton proposal | Huawei | draft TR | Approval | Yes |
Yes
| revised | No | S5‑164251 | |||
S5‑164251 | Draft TR 28.800 skeleton proposal | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | S5‑164104 | |||
S5‑164105 | pCR TR 28.800 Adding content for introduction and scope | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑164252 | |||
S5‑164252 | pCR TR 28.800 Adding content for introduction and scope | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑164105 | |||
S5‑164106 | Discussion paper on the management and orchestration terminologies | Huawei | discussion | Agreement | Yes |
Yes
| noted | No | ||||
S5‑164108 | pCR TR 28.800 Adding deployment scenarios of the next generation management system | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑164289 | Draft TR 28.800 | Rapporteur (Huawei) | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.5 | Study on management aspects of next generation network architecture and features | S5‑164032 | Minutes for Study on management aspects of next generation network architecture and features | Rapporteur(Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑164067 | Skeleton of draft TR 28.802 Management aspects of 5G network architecture and features | Nokia Networks | draft TR | Approval | Yes |
Yes
| revised | No | S5‑164253 | |||
S5‑164253 | Skeleton of draft TR 28.802 Management aspects of 5G network architecture and features | Nokia Networks | draft TR | Approval | Yes |
Yes
| approved | No | S5‑164067 | |||
S5‑164068 | pCR Add scope to draft TR 28.802 | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑164254 | |||
S5‑164254 | pCR Add scope to draft TR 28.802 | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑164068 | |||
S5‑164290 | Draft TR 28.802 | Rapporteur (Nokia) | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.6 | Study on Management and Orchestration of Network Slicing | S5‑164031 | Minutes for Study on Management and Orchestration of Network Slicing | Rapporteur (Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑164059 | Discussion of network slicing and ETSI NFV Network Service relationship | Cisco Systems Belgium | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑164060 | Skeleton TR 28.801 Management and Orchestration of Network Slicing | Ericsson | draft TR | Approval | Yes |
Yes
| approved | No | ||||
S5‑164061 | pCR TR 28.801 Introduction and Scope for Management and Orchestration of Network Slicing | Ericsson | other | Yes |
Yes
| revised | No | S5‑164255 | ||||
S5‑164255 | pCR TR 28.801 Introduction and Scope for Management and Orchestration of Network Slicing | Ericsson | other | - | Yes |
Yes
| approved | No | S5‑164061 | |||
S5‑164109 | pCR TR 28.801 Adding full isolated slices management use case | Huawei | other | Approval | Yes |
Yes
| revised | No | S5‑164256 | |||
S5‑164256 | pCR TR 28.801 Adding full isolated slices management use case | Huawei | other | Approval | Yes |
Yes
| revised | No | S5‑164292 | S5‑164109 | ||
S5‑164292 | pCR TR 28.801 Adding Slices Management use case | Huawei | other | Approval | No |
Yes
| left for email approval | No | S5‑164256 | |||
S5‑164110 | pCR TR 28.801 Adding use case for management supoort of network slice resource isolation | Huawei | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑164111 | pCR TR 28.801 Adding management use case of Network Slices with Common and Slice Specific Functions | Huawei | other | Yes |
Yes
| revised | No | S5‑164257 | ||||
S5‑164257 | pCR TR 28.801 Adding management use case of Network Slices with Common and Slice Specific Functions | Huawei | other | - | Yes |
Yes
| noted | No | S5‑164111 | |||
S5‑164112 | pCR TR 28.801 Adding use case for network slice lifecycle management | Huawei | other | Approval | Yes |
Yes
| revised | No | S5‑164258 | |||
S5‑164258 | pCR TR 28.801 Adding use case for network slice lifecycle management | Huawei | other | Approval | Yes |
Yes
| revised | No | S5‑164293 | S5‑164112 | ||
S5‑164293 | pCR TR 28.801 Adding use case for network slice lifecycle management | Huawei | other | Approval | No |
Yes
| left for email approval | No | S5‑164258 | |||
S5‑164126 | pCR TR 28.801 Adding use case for supporting dynamic Lifecycle Management in Network Slices | Huawei Tech.(UK) Co., Ltd | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑164291 | Draft TR 28.801 | Rapporteur (Ericsson) | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑164008 | CH Agenda and Time Plan | CH SWG Chair | agenda | Yes |
Yes
| approved | No | |||
S5‑164009 | CH Executive Report from THIS Meeting | CH SWG Chair | report | Yes |
Yes
| noted | No | |||||
S5‑164040 | Reply LS from CT3 cc SA5 on progress of the work on Diameter Load Control | C3-161313 | LS in | Yes |
Yes
| noted | No | |||||
S5‑164041 | LS from CT4 cc SA5 on Recommendations on AVP code allocation | C4-163248 | LS in | Yes |
Yes
| noted | No | |||||
S5‑164042 | LS from CT4 to SA5 on reply on progress of the work on Diameter Base Protocol Update | C4-163282 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑164043 | LS from CT4 to SA5 on Feasibility Study on the Diameter Base Protocol Update | C4-163283 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑164045 | Resubmitted LS from ETSI TC INT to SA5 on Validation project for the Conformance Test Specifications for the Diameter Protocol over the Rf and the Ro reference points | ETSI TC INT | LS in | Yes |
Yes
| noted | No | |||||
S5‑164094 | LS reply to LS on Feasibility Study on the Diameter Base Protocol Update | Nokia | LS out | Approval | Yes |
Yes
| revised | No | S5‑164180 | |||
S5‑164180 | LS reply to LS on Feasibility Study on the Diameter Base Protocol Update | Nokia | LS out | Approval | Yes |
Yes
| approved | No | S5‑164094 | |||
S5‑164101 | LS on Addition of AVP code definitions | Nokia | LS out | Approval | Yes |
Yes
| revised | No | S5‑164221 | |||
S5‑164221 | LS on Addition of AVP code definitions | Nokia | LS out | Approval | Yes |
Yes
| revised | No | S5‑164301 | S5‑164101 | ||
S5‑164301 | LS on Addition of AVP code definitions | Nokia | LS out | Approval | Yes |
Yes
| approved | No | S5‑164221 | |||
7.2 | New Charging Work Item proposals |   | ||||||||||
7.3 | Charging Maintenance and Rel-14 small Enhancements | S5‑164102 | Rel-12 CR 32.298 Correction on the SubscriberEquipmentType – align with TS 32.299 | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||
S5‑164103 | Rel-13 CR 32.298 Correction on the SubscriberEquipmentType – align with TS 32.299 | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑164185 | |||
S5‑164185 | Rel-14 CR 32.298 Correction on the SubscriberEquipmentType – align with TS 32.299 | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑164103 | |||
S5‑164130 | Rel-13 CR 32.299 Correction on APN Rate Control – Alignment with TS 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑164188 | |||
S5‑164188 | Rel-13 CR 32.299 Correction on APN Rate Control – Alignment with TS 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑164130 | |||
S5‑164136 | Rel-13 CR 32.298 Correction on APN Rate Control – Alignment with TS 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑164190 | |||
S5‑164190 | Rel-13 CR 32.298 Correction on APN Rate Control – Alignment with TS 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑164136 | |||
S5‑164140 | Discussion Paper for Complement of Charging per IP-CAN Session Analysis | Huawei Technologies | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑164141 | Complement of Charging per IP-CAN Session | Huawei Technologies | CR | Yes |
Yes
| revised | No | S5‑164197 | ||||
S5‑164197 | Rel-14 CR 32.251 Complement of Charging per IP-CAN Session | Huawei Technologies | CR | - | Yes |
Yes
| agreed | No | S5‑164141 | |||
S5‑164142 | Complement of Charging per IP-CAN Session | Huawei Technologies | CR | Yes |
Yes
| revised | No | S5‑164198 | ||||
S5‑164198 | Rel-14 CR 32.299 Complement of Charging per IP-CAN Session | Huawei Technologies | CR | - | Yes |
Yes
| agreed | No | S5‑164142 | |||
S5‑164143 | Complement of Charging per IP-CAN Session | Huawei Technologies | CR | Yes |
Yes
| revised | No | S5‑164199 | ||||
S5‑164199 | Rel-14 CR 32.298 Complement of Charging per IP-CAN Session | Huawei Technologies | CR | - | Yes |
Yes
| agreed | No | S5‑164143 | |||
S5‑164148 | Correction of reference to Annex B of TS 32.260 | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑164186 | |||
S5‑164186 | Rel-14 CR 32.281 Correction of reference to Annex B of TS 32.260 | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑164302 | S5‑164148 | ||
S5‑164302 | Rel-14 CR 32.281 Correction of reference to Annex B of TS 32.260 | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑164186 | |||
S5‑164149 | Use of Multiple Operation and Multiple Unit Operation for IEC | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑164187 | |||
S5‑164187 | Rel-13 CR 32.274 Correction on use of Multiple Operation and Multiple Unit Operation for IEC | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑164149 | |||
S5‑164151 | Rel-13 CR 32.253 Correction of trigger conditions description for NIDD submission | Nokia, Alcatel-Lucent Shanghai Bell | CR | Yes |
Yes
| revised | No | S5‑164191 | ||||
S5‑164191 | Rel-13 CR 32.253 Correction of trigger conditions description for NIDD submission | Nokia, Alcatel-Lucent Shanghai Bell | CR | - | Yes |
Yes
| agreed | No | S5‑164151 | |||
S5‑164152 | Rel-13 CR 32.298 Correction of trigger conditions description for NIDD submission | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑164192 | |||
S5‑164192 | Rel-13 CR 32.298 Correction of trigger conditions description for NIDD submission | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑164152 | |||
S5‑164153 | Rel-13 CR 32.299 Correction of trigger conditions description for NIDD submission | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑164193 | |||
S5‑164193 | Rel-13 CR 32.299 Correction of trigger conditions description for NIDD submission | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑164153 | |||
S5‑164154 | Rel-13 CR 32.299 Correction on AVP Code for Serving PLMN Rate Control – alignement with 29.230 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑164195 | |||
S5‑164195 | Rel-13 CR 32.299 Correction on AVP Code for Serving PLMN Rate Control – alignement with 29.230 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑164154 | |||
S5‑164155 | Rel-14 CR 32.299 Introduction of allocated AVPs code ranges-alignement with 29.230 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑164220 | |||
S5‑164220 | Rel-14 CR 32.299 Introduction of allocated AVPs code ranges-alignement with 29.230 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑164155 | |||
S5‑164156 | Rel-14 CR 32.299 Correction of trigger conditions description for NIDD submission | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑164194 | |||
S5‑164194 | Rel-14 CR 32.299 Correction of trigger conditions description for NIDD submission | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑164156 | |||
S5‑164157 | Rel-14 CR 32.299 Correction on AVP Code for Serving PLMN Rate Control- alignement with 29.230 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑164196 | |||
S5‑164196 | Rel-14 CR 32.299 Correction on AVP Code for Serving PLMN Rate Control- alignement with 29.230 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑164157 | |||
S5‑164158 | Rel-14 CR 32.299 Correction on APN Rate Control - Alignment with TS 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑164189 | |||
S5‑164189 | Rel-14 CR 32.299 Correction on APN Rate Control - Alignment with TS 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑164158 | |||
7.4 | Rel-14 Charging |   | ||||||||||
7.4.1 | Resource optimization for PS domain online charging sessions | S5‑164146 | General description for Gy Session Optimization | Huawei Technologies | CR | Yes |
Yes
| not pursued | No | |||
S5‑164181 | Rel-14 dCR 32.251 General description for Gy Session Optimization | Huawei Technologies | draftCR | - | Yes |
Yes
| approved | No | ||||
S5‑164150 | Use of Credit Control Not Applicable for Gy Session Optimization | Ericsson | other | Agreement | Yes |
Yes
| revised | No | S5‑164182 | |||
S5‑164182 | Use of Credit Control Not Applicable for Gy Session Optimization | Ericsson | other | Agreement | Yes |
Yes
| approved | No | S5‑164150 | |||
S5‑164222 | General description for Gy Session Optimization | Huawei | other | Approval | Yes |
Yes
| approved | No | ||||
7.4.2 | Determination of Completeness of Charging Information in IMS |   | ||||||||||
7.4.3 | Charging Aspects of Enhanced Proximity-based Services | S5‑164144 | Add Editor's Notes for ProSe Charging | Huawei Technologies | CR | Agreement | Yes |
No
| withdrawn | Yes | ||
S5‑164145 | Message flow for Announce Request of Prose Restricted Discovery | Huawei Technologies | CR | Agreement | Yes |
Yes
| revised | No | S5‑164183 | |||
S5‑164183 | Rel-14 CR 32.277 Message flow for Announce Request of Prose Restricted Discovery | Huawei Technologies | CR | Agreement | Yes |
Yes
| agreed | No | S5‑164145 | |||
7.4.4 | Charging Aspects of S8 Home Routing Architecture for VoLTE | S5‑164074 | Rel-14 CR 32.240 Add charging principles for roaming architecture for voice over IMS with home routed traffic | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑164184 | |
S5‑164184 | Rel-14 CR 32.240 Add charging principles for roaming architecture for voice over IMS with home routed traffic | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑164074 | |||
7.5 | Charging Studies |   | ||||||||||
7.5.1 | Study on Overload Control for Diameter Charging Applications |   | ||||||||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |