Tdoc List
2016-09-02 11:48
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‑165000 | Agenda | WG Chairman | agenda | Yes |
Yes
| approved | No | |||
3 | IPR declaration | S5‑165032 | IPR and legal declaration | WG Chairman | other | Yes |
Yes
| noted | No | |||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑165001 | Report from last SA5 meeting | ETSI Secretariat | report | Yes |
Yes
| approved | No | |||
4.2 | Last SA meeting report | S5‑165002 | SA5 status report at last SA meeting | WG Chairman | report | Yes |
Yes
| noted | No | |||
S5‑165003 | SA5 results at last SA meeting | WG Chairman | report | Yes |
Yes
| noted | No | |||||
4.3 | Inter-organizational reports |   | ||||||||||
5 | Cross-SWG issues |   | ||||||||||
5.1 | Administrative issues at SA5 level | S5‑165006 | Leaders meeting agenda | WG Chairman | agenda | No |
NoThe Chairman commented that for the time being the leaders meeting will be held via conference calls a week before every SA5 meeting.
| withdrawn | Yes | |||
S5‑165007 | Leaders meeting minutes | WG Chairman | report | No |
No
| withdrawn | Yes | |||||
S5‑165011 | SA5 Working Procedures | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||||
S5‑165012 | SA5 Meeting Facility Requirements | WG Vice Chair (Orange) | other | Yes |
Yes
| noted | No | |||||
S5‑165013 | Process for management of draft TSs/TRs | WG Chairman | other | Yes |
Yes
| revised | No | S5‑165242 | ||||
S5‑165242 | Process for management of draft TSs/TRs | WG Chairman | other | - | Yes |
Yes
| approved | No | S5‑165013 | |||
S5‑165014 | CR Quality Check | ETSI Secretariat | other | Yes |
Yes
| noted | No | |||||
S5‑165033 | Status of email approvals | WG Vice Chair (Orange) | other | No |
No
| reserved | No | |||||
5.2 | Technical issues at SA5 level |   | ||||||||||
5.3 | Liaison statements at SA5 level |   | ||||||||||
5.4 | SA5 meeting calendar | S5‑165010 | SA5 Meeting Calendar | WG Vice Chair (Huawei) | other | Yes |
YesErik (SA Chairman) confirmed that the Rel-15 freeze would be in June 2018. Erik recommended to co-locate with SA2 in order to sync management work with the architecture. There might be interactions with SA3 as well. The October 2017 meeting could be a candidate for this co-location, or August 2017 as well.
| revised | No | S5‑165243 | ||
S5‑165243 | SA5 Meeting Calendar | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| noted | No | S5‑165010 | |||
5.5 | Review of the Work Plan | S5‑165015 | Deliverables due for the NEXT SA Plenary | ETSI Secretariat | other | Yes |
Yes
| noted | No | |||
S5‑165016 | Ongoing SA5 WIDs and SIDs | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||||
S5‑165017 | SA5 3GPP Work Plan | ETSI Secretariat | other | Yes |
Yes
| noted | No | |||||
S5‑165036 | Work Plan status | WG Chair | other | No |
No
| reserved | No | |||||
S5‑165038 | SA5 work plan structure | SA vice chairman | discussion | Discussion | Yes |
YesIt was commented by Erik (SA Chairman)that the purpose is to improve visibility of the 3GPP work, including reports from Rapporteurs that would for example,eventually be directed to the members of the press.
Erik commented that not using TEIx in SA5 is fine if this is for exclusive SA5 work that won’t be continued anywhere else. Everything that is done today is good, but it needs to be "raised up". He also pointed out that TEIx should be used when making corrections that spread throughout all Releases, and not OAMx, CHx, which differs from what is done in the rest of 3GPP groups. On the other hand, if the whole SA5 agreed on this, they could continue.
Any task that lasts longer than a quarter needs plenary approval and would require a WID.
Erik pointed out that the use of OAMx,CHx differs from the TEIx rules that are used in the rest of 3GPP.
Changes in the working methods of SA5 could be applied from Rel-15.
It was decided to note the document with the view of applying a more alignemnt with 3GPP rules from Rel-15. This would also mean that both Charging and OAM CRs would not be distinguishable.
| noted | No | ||||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑165004 | Time Plan for OAM&P | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||
S5‑165005 | OAM Executive Report from THIS Meeting | WG Vice Chair (Huawei) | report | Yes |
Yes
| revised | No | S5‑165374 | ||||
S5‑165374 | OAM Executive Report from THIS Meeting | WG Vice Chair (Huawei) | report | - | No |
Yes
| noted | No | S5‑165005 | |||
S5‑165035 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | Yes |
Yes
| revised | No | S5‑165215 | ||||
S5‑165215 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| revised | No | S5‑165318 | S5‑165035 | ||
S5‑165318 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| noted | No | S5‑165215 | |||
S5‑165037 | Minutes of OAM&P SWG opening session | WG Vice Chair (Huawei) | report | Yes |
Yes
| noted | No | |||||
S5‑165039 | Resubmitted LS from ATIS NRSC to SA5 on RE: Establish a Metric to Determine a Drop in Registered Users in an IP-Based Network | ATIS | LS in | Yes |
Yes
| replied to | No | |||||
S5‑165196 | Reply to: Resubmitted LS from ATIS NRSC to SA5 on RE: Establish a Metric to Determine a Drop in Registered Users in an IP-Based Network | Ericsson | LS out | approval | Yes |
Yes
| revised | No | S5‑165319 | |||
S5‑165319 | Reply to: Resubmitted LS from ATIS NRSC to SA5 on RE: Establish a Metric to Determine a Drop in Registered Users in an IP-Based Network | Ericsson | LS out | approval | Yes |
Yes
| approved | No | S5‑165196 | |||
S5‑165047 | Reply LS from SA2 to ETSI NTECH AFI cc SA5 on Autonomic Networking | S2-164274 | LS in | Yes |
Yes
| noted | No | |||||
S5‑165050 | Potential ad hoc meeting on NFV work items | SA5 vice chairman | discussion | Decision | Yes |
Yes
| noted | No | ||||
S5‑165162 | Revised WID Study on Management and Orchestration of Network Slicing for next generation network | Ericsson LM | other | No |
No
| withdrawn | Yes | |||||
S5‑165192 | LS from BBF to SA5 on Proposed TR-196i2 Corrigendum 3 | BBF | LS in | Yes |
Yes
| replied to | No | |||||
S5‑165199 | Reply to: LS from BBF to SA5 on Proposed TR-196i2 Corrigendum 3 | Ericsson | LS out | approval | Yes |
Yes
| revised | No | S5‑165320 | |||
S5‑165320 | Reply to: LS from BBF to SA5 on Proposed TR-196i2 Corrigendum 3 | Ericsson | LS out | approval | Yes |
Yes
| approved | No | S5‑165199 | |||
S5‑165193 | LS from ETSI NFV to SA5 on NFV Interface and Architecture specifications | ETSI ISG NFV | LS in | Yes |
Yes
| postponed | No | |||||
S5‑165195 | NGMN NWMO presentation | Huawei | other | discussion | Yes |
Yes
| noted | No | ||||
S5‑165198 | Response LS from RAN2 cc SA5 on QoE reporting for streaming services | R2-165972 | LS in | discussion | Yes |
Yes
| noted | No | ||||
S5‑165321 | LS on update of the work plan of stage 3 | Huawei | LS out | Approval | Yes |
Yes
| approved | No | ||||
6.2 | New OAM&P Work Item proposals | S5‑165018 | Minutes of New Work Item proposals - OAM&P | WG Vice Chair (Orange) | report | Yes |
Yes
| noted | No | |||
S5‑165079 | Discussion Paper on 4G network slicing (IoT) management | Cisco Systems Inc. | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑165080 | New WID for Study on Management and Orchestration of Network Slicing (IoT) in 4G | Cisco Systems Inc. | SID new | Approval | Yes |
Yes
| revised | No | S5‑165201 | |||
S5‑165201 | New SID for Study on Management and Orchestration of Network Slicing (IoT) in 4G | Cisco Systems Inc. | SID new | Approval | Yes |
Yes
| revised | No | S5‑165322 | S5‑165080 | ||
S5‑165322 | New SID for Study on Management and Orchestration of Network Slicing (IoT) in 4G | Cisco Systems Inc. | SID new | Approval | Yes |
Yes
| agreed | No | S5‑165201 | |||
S5‑165083 | Discussion paper of the management for supporting RAN virtualization | Intel Corporation (UK) Ltd | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑165084 | NEW SID Study on management aspects of the RAN virtualization | Intel Corporation (UK) Ltd | SID new | Approval | Yes |
Yes
| revised | No | S5‑165202 | |||
S5‑165202 | NEW SID Study on management aspects of the RAN virtualization | Intel Corporation (UK) Ltd | SID new | Approval | Yes |
Yes
| revised | No | S5‑165323 | S5‑165084 | ||
S5‑165323 | New SID Study on management aspects of virtualized network functions that are part of the RAN | Intel Corporation (UK) Ltd | SID new | Agreement | Yes |
YesHuawei: there are some concerns based on RAN3's work. Intel: we know already that some part of the RAN can be virtualized, it's enough to carry on.
Huawei: we still need a reply from RAN3 before agreeing on this.
The Chairman commented that this is a study and the RAN3's feedback can be taken in any time.
Huawei objected to the agreement of this study; this objection was sustained and it was commented that this study could be carried on to plenary and have a decision there.
The Chairman commented that he felt uncomfortable with sending this WID without consensus.It was decided to send the SID to SA and have the discussion there.
| not concluded | No | S5‑165202 | |||
S5‑165123 | New Study on a RESTful HTTP-based Solution Set | Nokia Networks | SID new | Yes |
Yes
| revised | No | S5‑165203 | ||||
S5‑165203 | New Study on a RESTful HTTP-based Solution Set | Nokia Networks | SID new | - | Yes |
Yes
| revised | No | S5‑165324 | S5‑165123 | ||
S5‑165324 | New Study on a RESTful HTTP-based Solution Set | Nokia Networks | SID new | - | Yes |
Yes
| agreed | No | S5‑165203 | |||
S5‑165186 | Discussion of Control and User Plane Split | Huawei Tech.(UK) Co., Ltd | discussion | Yes |
Yes
| noted | No | |||||
6.3 | OAM&P Maintenance and Rel-14 small Enhancements | S5‑165019 | Minutes of OAM&P Maintenance and Rel-14 small Enhancements | MCC | report | No |
No
| withdrawn | Yes | |||
S5‑165081 | Add missing Annex | Ericsson LM | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑165082 | Rel-14 CR 32.103 Alignment with latest SA5 specification list and various enhancements | Huawei, Ericsson | CR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑165188 | Draft CR 32.103 Alignment with latest SA5 specification list and various enhancements | Huawei, Ericsson | draftCR | Approval | Yes |
Yes
| approved | 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‑165022 | Minutes for Management concept, architecture and requirements for mobile networks that include virtualized network functions | Rapporteur(China Mobile) | report | Yes |
Yes
| noted | No | |||
S5‑165110 | pCR TS 28.500 Consistency edits and clarifications | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑165244 | |||
S5‑165244 | pCR TS 28.500 Consistency edits and clarifications | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑165110 | |||
S5‑165111 | pCR TS 28.500 Addressing note about “platform” in NE and VNF relationship | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑165245 | |||
S5‑165245 | pCR TS 28.500 Addressing note about “platform” in NE and VNF relationship | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑165325 | S5‑165111 | ||
S5‑165325 | pCR TS 28.500 Addressing note about “platform” in NE and VNF relationship | NTT DOCOMO,China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑165245 | |||
S5‑165112 | pCR TS 28.500 Aligning requirements and traceability on FM virtualization-specific use case | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑165113 | pCR TS 28.500 Aligning requirements and traceability on certain LCM use cases | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑165247 | |||
S5‑165247 | pCR TS 28.500 Aligning requirements and traceability on certain LCM use cases | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑165113 | |||
S5‑165116 | pCR TS 28.500 UC and requirements on automating different types of configuration | NTT DOCOMO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑165248 | pCR TS 28.500 UC and requirements on automating different types of configuration | NTT DOCOMO | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑165119 | pCR TS 28.500 Updating the NE and VNF concept | China Mobile Com. Corporation | pCR | Yes |
Yes
| revised | No | S5‑165246 | ||||
S5‑165246 | pCR TS 28.500 Updating the NE and VNF concept | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| revised | No | S5‑165326 | S5‑165119 | ||
S5‑165326 | pCR TS 28.500 Updating the NE and VNF concept | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| approved | No | S5‑165246 | |||
S5‑165120 | pCR TS 28.500 Adding the PM collection use case | China Mobile Com. Corporation | pCR | Yes |
Yes
| revised | No | S5‑165250 | ||||
S5‑165250 | pCR TS 28.500 Adding the PM collection use case | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| revised | No | S5‑165331 | S5‑165120 | ||
S5‑165331 | pCR TS 28.500 Adding the PM collection use case | China Mobile Com. Corporation | pCR | - | Yes |
Yes
| approved | No | S5‑165250 | |||
S5‑165121 | Discussion TS 28.500 the collection machenism of VNF PM data related to virtualized resource | China Mobile Com. Corporation | discussion | Yes |
Yes
| noted | No | |||||
S5‑165122 | Revised WID Management concept, architecture and requirements for mobile networks that include virtualized network functions | China Mobile Com. Corporation | WID revised | Yes |
Yes
| revised | No | S5‑165373 | ||||
S5‑165373 | Revised WID Management concept, architecture and requirements for mobile networks that include virtualized network functions | China Mobile Com. Corporation | WID revised | - | Yes |
Yes
| agreed | No | S5‑165122 | |||
S5‑165150 | pCR TS 28.500 Align the usage of term on non-application | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑165251 | pCR TS 28.500 Align the usage of term on non-application | Huawei Technologies | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑165200 | Informal presentation of draft LS NFV(16)000252 - LS OUT to 3GPP SA5 informing about update to application view in IFA015 | Nokia Networks | other | discussion | Yes |
Yes
| noted | No | ||||
S5‑165271 | pCR 28.500-110 update based on the reviews from edithelp | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑165275 | Addressing EditHelp's comments | China Mobile | pCR | discussion | Yes |
No
| withdrawn | Yes | ||||
S5‑165327 | new draft TS 28.500 | China Mobile | 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‑165023 | Minutes for Configuration Management for mobile networks that include virtualized network functions | Rapporteur(ZTE) | report | Yes |
Yes
| noted | No | |||
S5‑165098 | pCR 28.510 Add MOI deletion requirement | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑165252 | |||
S5‑165252 | pCR 28.510 Add MOI deletion requirement | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑165098 | |||
S5‑165099 | pCR 28.510 Add traceabilities of MOI configuration requirements | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑165253 | |||
S5‑165253 | pCR 28.510 Add traceabilities of MOI configuration requirements | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑165332 | S5‑165099 | ||
S5‑165332 | pCR 28.510 Add traceabilities of MOI configuration requirements | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑165253 | |||
S5‑165100 | 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‑165261 | pCR draft TS 28.511 Add procedure of creating MOI(s) after a VNF is instantiated | ZTE Corporation | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑165101 | draft TS 28.513 skeleton | ZTE Corporation | draft TS | Approval | Yes |
Yes
| revised | No | S5‑165254 | |||
S5‑165254 | draft TS 28.513 skeleton | ZTE Corporation | draft TS | Approval | Yes |
Yes
| approved | No | S5‑165101 | |||
S5‑165102 | pCR TS 28.513 Add introduction and scope | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑165103 | Presentation TS 28.510 to SA for information | ZTE Corporation | TS or TR cover | Approval | Yes |
Yes
| revised | No | S5‑165278 | |||
S5‑165278 | Presentation TS 28.510 to SA for information | ZTE Corporation | TS or TR cover | Approval | Yes |
Yes
| approved | No | S5‑165103 | |||
S5‑165105 | Discussion paper- enhancement of NRM to support the VNF | ZTE Corporation | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑165255 | |||
S5‑165255 | Discussion paper- enhancement of NRM to support the VNF | ZTE Corporation | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑165335 | S5‑165105 | ||
S5‑165335 | Discussion paper- enhancement of NRM to support the VNF | ZTE Corporation | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑165255 | |||
S5‑165151 | pCR TS 28.510 Align the usage of term on non-application | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑165257 | pCR TS 28.510 Align the usage of term on non-application | Huawei Technologies | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑165152 | pCR TS 28.510 Modify use case of MO creation after VNF instantiation with VNF instance indentifier | Huawei Technologies | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑165258 | pCR TS 28.510 Modify use case of MO creation after VNF instantiation with VNF instance indentifier | Huawei Technologies | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑165153 | pCR TS 28.510 Adding the requirement and use case for createMO with trigger of VNF instantiation | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165259 | |||
S5‑165259 | pCR TS 28.510 Adding the requirement and use case for createMO with trigger of VNF instantiation | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑165153 | |||
S5‑165154 | pCR TS 28.511 Adding procedure flow for createMO with trigger of VNF instantiation | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165262 | |||
S5‑165262 | pCR TS 28.511 Adding procedure flow for createMO with trigger of VNF instantiation | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165336 | S5‑165154 | ||
S5‑165336 | pCR TS 28.511 Adding procedure flow for createMO with trigger of VNF instantiation | Huawei Technologies | pCR | Approval | No |
Yes
| left for email approval | No | S5‑165262 | |||
S5‑165166 | pCR TS 28.510 add the relationship between VNF termination and MO deletion | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑165260 | pCR TS 28.510 add the relationship between VNF termination and MO deletion | Intel Corporation (UK) Ltd | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑165168 | pCR TS 28.511 add CM procedures for the VNF instantiation | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑165263 | pCR TS 28.511 add CM procedures for the VNF instantiation | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
No
| withdrawn | Yes | ||||
S5‑165169 | pCR TS 28.511 add CM procedures for the VNF termination | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑165264 | |||
S5‑165264 | pCR TS 28.511 add CM procedures for the VNF termination | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑165169 | |||
S5‑165175 | Relation between NRM class and VNF/VNFC (implemented in VNFM) | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑165256 | |||
S5‑165256 | Relation between NRM class and VNF/VNFC (implemented in VNFM) | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑165175 | |||
S5‑165197 | Discussion Sequence Proposal for 6.4.1.2 | ZTE | other | discussion | Yes |
Yes
| noted | No | ||||
S5‑165312 | pCR TS 28.510 Rapporteur proposal | ZTE | pCR | discussion | Yes |
Yes
| approved | No | ||||
S5‑165333 | Draft TS 28.510 | ZTE | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑165334 | Draft TS 28.513 | ZTE | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑165367 | Draft TS 28.511 | 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‑165024 | Minutes for Fault Management for mobile networks that include virtualized network functions | Rapporteur(Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑165155 | pCR TS 28.515 Adding VNF alarm notification subscription requirement on Ve-vnfm-em | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165265 | |||
S5‑165265 | pCR TS 28.515 Adding VNF alarm notification subscription requirement on Ve-vnfm-em | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165337 | S5‑165155 | ||
S5‑165337 | pCR TS 28.515 Adding VNF alarm notification subscription requirement on Ve-vnfm-em | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑165265 | |||
S5‑165156 | pCR TS 28.515 Rapporteur proposal | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑165266 | pCR TS 28.515 Rapporteur proposal | Huawei Technologies | pCR | Approval | Yes |
No
| withdrawn | Yes | ||||
S5‑165157 | Presentation sheet TS 28.515 for information to SA | Huawei Technologies | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S5‑165158 | Presentation sheet TS 28.516 for information to SA | Huawei Technologies | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S5‑165159 | pCR TS 28.517 Adding VNF alarm notification subscription stage 2 on Ve-vnfm-em | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165268 | |||
S5‑165268 | pCR TS 28.517 Adding VNF alarm notification subscription stage 2 on Ve-vnfm-em | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑165159 | |||
S5‑165160 | pCR TS 28.517 Adding alarm Information Model on Ve-Vnfm-em | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165269 | |||
S5‑165269 | pCR TS 28.517 Adding alarm Information Model on Ve-Vnfm-em | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑165160 | |||
S5‑165161 | pCR TS 28.518 Adding stage 3 content | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165270 | |||
S5‑165270 | pCR TS 28.518 Adding stage 3 content | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑165161 | |||
S5‑165173 | Add UC and reqs Virtualization-specific aspect failure detection and notification by VNFM | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑165267 | |||
S5‑165267 | Add UC and reqs Virtualization-specific aspect failure detection and notification by VNFM | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑165341 | S5‑165173 | ||
S5‑165341 | Add UC and reqs Virtualization-specific aspect failure detection and notification by VNFM | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑165368 | S5‑165267 | ||
S5‑165368 | Add UC and reqs Virtualization-specific aspect failure detection and notification by VNFM | Ericsson Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑165341 | |||
S5‑165338 | Draft TS 28.515 | Huawei | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑165339 | Draft TS 28.517 | Huawei | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑165340 | Draft TS 28.518 | 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‑165025 | Minutes for Performance management for mobile networks that include virtualized network functions | Rapporteur(Intel) | report | Yes |
Yes
| noted | No | |||
S5‑165057 | pCR TS 28.520 include comments received from edithelp | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑165058 | Draft TS 28523 skeleton | Intel Corporation (UK) Ltd | draft TS | Approval | Yes |
Yes
| approved | No | ||||
S5‑165059 | pCR TS 28.523 add introduction and scope | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑165272 | |||
S5‑165272 | pCR TS 28.523 add introduction and scope | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑165059 | |||
S5‑165060 | pCR TS 28.522 add stage 2 solutions | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑165274 | |||
S5‑165274 | pCR TS 28.522 add stage 2 solutions | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑165060 | |||
S5‑165061 | pCR TS 28.520 add reference to ETSI GS NFV IFA008 specification | Intel Corporation (UK) Ltd | pCR | Yes |
Yes
| revised | No | S5‑165276 | ||||
S5‑165276 | pCR TS 28.520 add reference to ETSI GS NFV IFA008 specification | Intel Corporation (UK) Ltd | pCR | - | Yes |
Yes
| approved | No | S5‑165061 | |||
S5‑165062 | pCR TS 28.520 change the terminologies related to legacy PM data | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑165277 | |||
S5‑165277 | pCR TS 28.520 change the terminologies related to legacy PM data | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑165344 | S5‑165062 | ||
S5‑165344 | pCR TS 28.520 change the terminologies related to legacy PM data | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑165277 | |||
S5‑165085 | Add virtualized resources related performance measurements | Intel Corporation (UK) Ltd | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑165087 | Discussion paper on direct consumption of VR PM by NM | Nokia Networks | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑165174 | Add UC Fetch VNF related VR PM data produced by VNFM | Ericsson Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑165306 | Cover sheet TS 28.520 | Intel | TS or TR cover | discussion | Yes |
Yes
| approved | No | ||||
S5‑165342 | Draft TS 28.522 | Intel | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑165343 | Draft TS 28.520 | Intel | draft TS | discussion | No |
Yes
| left for email approval | No | ||||
S5‑165345 | Draft TS 28.523 | Intel | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
6.4.1.5 | Lifecycle management for mobile networks that include virtualized network functions | S5‑165026 | Minutes for Lifecycle management for mobile networks that include virtualized network functions | Rapporteur (Nokia Networks) | report | Yes |
Yes
| noted | No | |||
S5‑165049 | Editorial and minor technical changes to TS 28.525 based on EditHelp review | Nokia Networks | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑165069 | pCR 28.525 Fetch use case clarification | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑165070 | pCR 28.525 Fetch On-boarded VNF Package Artifacts operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑165289 | |||
S5‑165289 | pCR 28.525 Fetch On-boarded VNF Package Artifacts operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑165070 | |||
S5‑165071 | pCR 28.525 Abort VNF Package deletion operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑165290 | |||
S5‑165290 | pCR 28.525 Abort VNF Package deletion operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑165071 | |||
S5‑165072 | pCR 28.525 Update NSD operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑165291 | |||
S5‑165291 | pCR 28.525 Update NSD operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑165072 | |||
S5‑165073 | pCR 28.525 Delete NSD operation not in use | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑165292 | |||
S5‑165292 | pCR 28.525 Delete NSD operation not in use | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑165073 | |||
S5‑165074 | pCR 28.525 Delete NSD operation when in use | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑165075 | pCR 28.525 Query NSD operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑165076 | pCR 28.525 On-board PNFD operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑165086 | pCR TS 28.526 add VNF termination procedure | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑165293 | |||
S5‑165293 | pCR TS 28.526 add VNF termination procedure | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑165086 | |||
S5‑165088 | Discussion paper - Considerations for the VNF instantiation requested by EM | Nokia Networks | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑165089 | pCR TS 28.525 Update Use Case VNF instantiation initiated through Itf-N | Nokia Networks | pCR | Approval | Yes |
Yes
| revised | No | S5‑165295 | |||
S5‑165295 | pCR TS 28.525 Update Use Case VNF instantiation initiated through Itf-N | Nokia Networks | pCR | Approval | Yes |
Yes
| revised | No | S5‑165348 | S5‑165089 | ||
S5‑165348 | pCR TS 28.525 Update Use Case VNF instantiation initiated through Itf-N | Nokia Networks | pCR | Approval | Yes |
Yes
| approved | No | S5‑165295 | |||
S5‑165090 | Discussion paper - options for initial configuration data in VNF instantiation | Nokia Networks | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
S5‑165296 | Discussion paper - options for initial configuration data in VNF instantiation | Nokia Networks | discussion | Endorsement | No |
No
| withdrawn | Yes | ||||
S5‑165091 | pCR TS 28.525 Add UCs for initial configuration data in VNF instantiation | Nokia Networks | pCR | Approval | Yes |
Yes
| revised | No | S5‑165297 | |||
S5‑165297 | pCR TS 28.525 Add UCs for initial configuration data in VNF instantiation | Nokia Networks | pCR | Approval | Yes |
Yes
| approved | No | S5‑165091 | |||
S5‑165092 | pCR TS 28.526 Add procedure for initial configuration data in VNF instantiation | Nokia Networks | pCR | Approval | Yes |
Yes
| revised | No | S5‑165298 | |||
S5‑165298 | pCR TS 28.526 Add procedure for initial configuration data in VNF instantiation | Nokia Networks | pCR | Approval | Yes |
Yes
| approved | No | S5‑165092 | |||
S5‑165093 | Discussion paper - scenarios for NS update | Nokia Networks | other | Decision | Yes |
Yes
| noted | No | ||||
S5‑165094 | pCR TS 28.525 Add Use Cases for NS update with add VL and VNF | Nokia Networks | pCR | Approval | Yes |
Yes
| revised | No | S5‑165300 | |||
S5‑165300 | pCR TS 28.525 Add Use Cases for NS update with add VL and VNF | Nokia Networks | pCR | Approval | Yes |
Yes
| revised | No | S5‑165349 | S5‑165094 | ||
S5‑165349 | pCR TS 28.525 Add Use Cases for NS update with add VL and VNF | Nokia Networks | pCR | Approval | Yes |
Yes
| approved | No | S5‑165300 | |||
S5‑165095 | pCR TS 28.525 Add Use Case for NS update with add SAP | Nokia Networks | pCR | Approval | Yes |
Yes
| revised | No | S5‑165301 | |||
S5‑165301 | pCR TS 28.525 Add Use Case for NS update with add SAP | Nokia Networks | pCR | Approval | Yes |
Yes
| revised | No | S5‑165350 | S5‑165095 | ||
S5‑165350 | pCR TS 28.525 Add Use Case for NS update with add SAP | Nokia Networks | pCR | Approval | Yes |
Yes
| approved | No | S5‑165301 | |||
S5‑165096 | pCR TS 28.525 Add Use Case for NS instantiate with existing VNFs and new VL | Nokia Networks | pCR | Approval | Yes |
Yes
| revised | No | S5‑165302 | |||
S5‑165302 | pCR TS 28.525 Add Use Case for NS instantiate with existing VNFs and new VL | Nokia Networks | pCR | Approval | Yes |
Yes
| revised | No | S5‑165351 | S5‑165096 | ||
S5‑165351 | pCR TS 28.525 Add Use Case for NS instantiate with existing VNFs and new VL | Nokia Networks | pCR | Approval | Yes |
Yes
| approved | No | S5‑165302 | |||
S5‑165097 | pCR TS 28.525 Add Use Case for NS instantiate with existing NSs and new VL | Nokia Networks | pCR | Approval | Yes |
Yes
| revised | No | S5‑165303 | |||
S5‑165303 | pCR TS 28.525 Add Use Case for NS instantiate with existing NSs and new VL | Nokia Networks | pCR | Approval | Yes |
Yes
| revised | No | S5‑165352 | S5‑165097 | ||
S5‑165352 | pCR TS 28.525 Add Use Case for NS instantiate with existing NSs and new VL | Nokia Networks | pCR | Approval | Yes |
Yes
| approved | No | S5‑165303 | |||
S5‑165117 | pCR TS 28.525 Adding specification UCs and requirements related to updating NS | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑165304 | |||
S5‑165304 | pCR TS 28.525 Adding specification UCs and requirements related to updating NS | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑165117 | |||
S5‑165176 | Problem of VL instance creation | Ericsson Inc. | discussion | Agreement | Yes |
Yes
| noted | No | ||||
S5‑165177 | Add UC in 28.525 supporting Bulk MOIs creations | Ericsson Inc. | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑165207 | pCR TS 28.525 Rapproteur proposal | Nokia Networks | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑165208 | 28.525 presentation sheet to SA | Nokia Networks | TS or TR cover | discussion | Yes |
Yes
| revised | No | S5‑165305 | |||
S5‑165305 | 28.525 presentation sheet to SA | Nokia Networks | TS or TR cover | Approval | Yes |
Yes
| approved | No | S5‑165208 | |||
S5‑165294 | LS to IFA on the use of un-instantiated VNF instance ID in UpdateNS operation | Noikia Networks | LS out | Approval | Yes |
Yes
| revised | No | S5‑165317 | |||
S5‑165317 | LSout to ETSI ISG NFV IFA WG on the use of un-instantiated VNF instance ID in UpdateNS operation | Noikia Networks | LS out | Approval | Yes |
Yes
| revised | No | S5‑165353 | S5‑165294 | ||
S5‑165353 | LSout to ETSI ISG NFV IFA WG on the use of un-instantiated VNF instance ID in UpdateNS operation | Noikia Networks | LS out | Approval | Yes |
Yes
| approved | No | S5‑165317 | |||
S5‑165299 | LSout to ETSI ISG NFV IFA WG on update NS scenarios | Nokia Networks | LS out | Approval | Yes |
Yes
| revised | No | S5‑165372 | |||
S5‑165372 | LSout to ETSI ISG NFV IFA WG on update NS scenarios | Nokia Networks | LS out | Approval | Yes |
Yes
| approved | No | S5‑165299 | |||
S5‑165346 | Draft TS 28.525 | Nokia | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑165347 | Draft TS 28.526 | 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‑165027 | Minutes for Filtering of PM measurements and data volume measurements for shared networks | Rapporteur(Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑165124 | Corrections according to EditHelp in 32.817 | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑165125 | pCR 32817 Remove Editor’s note about true file name | Ericsson | pCR | Yes |
Yes
| approved | No | |||||
S5‑165126 | pCR Conclusion and Recommendations for TR 32.817 | Ericsson | pCR | Yes |
Yes
| revised | No | S5‑165307 | ||||
S5‑165307 | pCR Conclusion and Recommendations for TR 32.817 | Ericsson | pCR | - | Yes |
Yes
| approved | No | S5‑165126 | |||
S5‑165127 | Presentation of Specification/Report to TSG: TR 32.817, Version 1.0.0 | Ericsson | TS or TR cover | Yes |
Yes
| revised | No | S5‑165308 | ||||
S5‑165308 | Presentation of Specification/Report to TSG: TR 32.817, Version 1.0.0 | Ericsson | TS or TR cover | - | Yes |
Yes
| approved | No | S5‑165127 | |||
S5‑165249 | Revised WID Filtering of PM measurements and data volume measurements for shared networks | Ericsson | WID revised | discussion | Yes |
Yes
| revised | No | S5‑165309 | |||
S5‑165309 | Revised WID Filtering of PM measurements and data volume measurements for shared networks | Ericsson | WID revised | discussion | Yes |
Yes
| agreed | No | S5‑165249 | |||
S5‑165285 | draft TR 32.817 | Ericsson | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.4.3 | OAM support for Licensed Shared Access (LSA) | S5‑165034 | Minutes of OAM support for Licensed Shared Access (LSA) | Rapporteur (Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑165115 | Skeleton for 28.302 "Licensed Shared Access (LSA) Controller (LC) Integration Reference Point (IRP); Information Service" | RED Technologies SAS | draft TS | Approval | Yes |
Yes
| revised | No | S5‑165310 | |||
S5‑165310 | Skeleton for 28.302 "Licensed Shared Access (LSA) Controller (LC) Integration Reference Point (IRP); Information Service" | RED Technologies SAS | draft TS | Approval | Yes |
Yes
| approved | No | S5‑165115 | |||
S5‑165118 | Definition of operations and parameters | RED Technologies SAS | pCR | Approval | Yes |
Yes
| revised | No | S5‑165311 | |||
S5‑165311 | Definition of operations and parameters | RED Technologies SAS | pCR | Approval | Yes |
Yes
| noted | No | S5‑165118 | |||
S5‑165171 | Addition of use cases | Nokia Networks | pCR | Yes |
Yes
| revised | No | S5‑165313 | ||||
S5‑165313 | Addition of use cases | Nokia Networks | pCR | - | Yes |
Yes
| approved | No | S5‑165171 | |||
S5‑165286 | Draft TS 28.302 | Nokia | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑165369 | Draft TS 28.301 | 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‑165028 | Minutes of Study on OAM support for assessment of energy efficiency in mobile access networks | Rapporteur (Orange) | report | Yes |
Yes
| noted | No | |||
S5‑165043 | Resubmitted 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
| replied to | No | |||||
S5‑165044 | Resubmitted Liaison from ETSI TC EE to 3GPP SA5 in response to S5-162239 | ETSI TC EE | LS in | Yes |
Yes
| replied to | No | |||||
S5‑165063 | pCR 32.856 Skeleton for new clause 5 | ORANGE, Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑165064 | pCR 32.856 Proposed text for clause 5.1 | ORANGE, Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑165065 | pCR 32.856 Proposed text for clause 5.2 | ORANGE, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑165130 | |||
S5‑165066 | pCR 32.856 Proposed text for clause 5.3 | ORANGE, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑165131 | |||
S5‑165067 | pCR 32.856 Update Scope | ORANGE, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑165315 | |||
S5‑165315 | pCR 32.856 Update Scope | ORANGE, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑165067 | |||
S5‑165068 | pCR 32.856 Align clause 4 with ES 203 228 v1.1.5 | ORANGE | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑165128 | Reply to ETSI TC EE PS on ES 203 228 | ORANGE | LS out | Approval | Yes |
Yes
| approved | No | ||||
S5‑165129 | Reply to ETSI TC EE 02 on ES 202 336-12 | ORANGE | LS out | Approval | Yes |
Yes
| approved | No | ||||
S5‑165130 | pCR 32.856 Proposed text for clause 5.2 | ORANGE, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑165316 | S5‑165065 | ||
S5‑165316 | pCR 32.856 Proposed text for clause 5.2 | ORANGE, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑165130 | |||
S5‑165131 | pCR 32.856 Proposed text for clause 5.3 | ORANGE, Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑165066 | |||
S5‑165273 | TDoc sequence proposal for 6.5.1 | Orange | other | discussion | Yes |
Yes
| noted | No | ||||
S5‑165287 | Draft TR 32.856 | ORANGE | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.2 | Study on OAM aspects of SON for AAS-based deployments | S5‑165029 | Minutes for Study on OAM aspects of SON for AAS-based deployments | Rapporteur (Nokia Networks) | report | Yes |
Yes
| noted | No | |||
S5‑165077 | pCR 32.865 Cell merging correction | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑165078 | pCR 32.865 Cell splitting correction | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑165330 | Study on OAM aspects of SON for AAS-based deployments | Nokia | SID revised | Agreement | Yes |
Yes
| agreed | No | ||||
6.5.3 | Study on Implementation for the Partitioning of Itf-N | S5‑165021 | Minutes for Study on Implementation for the Partitioning of Itf-N | Rapporteur(China Mobile) | report | Yes |
Yes
| noted | No | |||
S5‑165172 | pCR TR 32.880 overview of protocols based on socket API | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑165314 | |||
S5‑165314 | pCR TR 32.880 overview of protocols based on socket API | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑165172 | |||
S5‑165288 | Draft TR 32.880 | 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‑165020 | Minutes for Study on Management and Orchestration Architecture of Next Generation Network and Service | Rapporteur (Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑165132 | pCR TR 28.800 Add management architecture use case of reusing the existing management system for next generation network | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165204 | |||
S5‑165204 | pCR TR 28.800 Add management architecture use case of reusing the existing management system for next generation network | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑165132 | |||
S5‑165133 | pCR TR 28.800 Add management use case for management and orchestration of the next generation network for build the new standalone management system | Huawei Technologies | pCR | Approval | Yes |
Yes
| merged | No | S5‑165204 | |||
S5‑165134 | pCR TR 28.800 Add terminologies for network management and orchestration layering concept | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165205 | |||
S5‑165205 | pCR TR 28.800 Add terminologies for network management and orchestration layering concept | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165355 | S5‑165134 | ||
S5‑165355 | pCR TR 28.800 Add terminologies for network management and orchestration layering concept | Huawei Technologies | pCR | Approval | No |
Yes
| left for email approval | No | S5‑165205 | |||
S5‑165135 | pCR TR 28.800 Add terminologies for network managmeent and orchestration/resource management and orchestration | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165206 | |||
S5‑165206 | pCR TR 28.800 Add terminologies for network managmeent and orchestration/resource management and orchestration | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165356 | S5‑165135 | ||
S5‑165356 | pCR TR 28.800 Add terminologies for network managmeent and orchestration/resource management and orchestration | Huawei Technologies | pCR | Approval | No |
Yes
| left for email approval | No | S5‑165206 | |||
S5‑165354 | Draft TR 28.800 | Huawei | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.5 | Study on Management and Orchestration of Network Slicing | S5‑165030 | Minutes for Study on Management and Orchestration of Network Slicing | Rapporteur (Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑165051 | Network Slice Use Case Methodology | Cisco Systems Belgium | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑165136 | pCR TR 28.801 Progress overview on network slicing in SA1, SA2, NGMN and analysis of potential management related aspects | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165210 | |||
S5‑165210 | pCR TR 28.801 Progress overview on network slicing in SA1, SA2, NGMN and analysis of potential management related aspects | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑165136 | |||
S5‑165137 | pCR TR 28.801 Adding use case for creating network slices with common and slice specific NFs | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165217 | |||
S5‑165217 | pCR TR 28.801 Adding use case for creating network slices with common and slice specific NFs | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165358 | S5‑165137 | ||
S5‑165358 | pCR TR 28.801 Adding use case for creating network slices with common and slice specific NFs | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑165217 | |||
S5‑165138 | pCR TR 28.801 Adding use case for modifying network slices with common and slice specific NFs | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165218 | |||
S5‑165218 | pCR TR 28.801 Adding use case for modifying network slices with common and slice specific NFs | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165359 | S5‑165138 | ||
S5‑165359 | pCR TR 28.801 Adding use case for modifying network slices with common and slice specific NFs | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑165218 | |||
S5‑165139 | pCR TR 28.801 Adding use case for terminating network slices with common and slice specific NFs | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165219 | |||
S5‑165219 | pCR TR 28.801 Adding use case for terminating network slices with common and slice specific NFs | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165360 | S5‑165139 | ||
S5‑165360 | pCR TR 28.801 Adding use case for terminating network slices with common and slice specific NFs | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑165219 | |||
S5‑165140 | pCR TR 28.801 Adding resource isolation terminologies for network slicing | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165220 | |||
S5‑165220 | pCR TR 28.801 Adding resource isolation terminologies for network slicing | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165361 | S5‑165140 | ||
S5‑165361 | pCR TR 28.801 Adding resource isolation terminologies for network slicing | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑165220 | |||
S5‑165141 | pCR TR 28.801 adding slice management related teminology | Huawei Technologies | pCR | Approval | Yes |
Yes
| merged | No | S5‑165213 | |||
S5‑165142 | Discussion of Network Slicing Descriptor | Huawei Technologies | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑165143 | pCR TR 28.801 Adding definitions for network slicing lifecycle management | Huawei Technologies | pCR | Approval | Yes |
Yes
| merged | No | S5‑165212 | |||
S5‑165144 | pCR TR 28.801 use case for network slice lifecycle management | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165216 | |||
S5‑165216 | pCR TR 28.801 use case for network slice lifecycle management | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165362 | S5‑165144 | ||
S5‑165362 | pCR TR 28.801 use case for network slice lifecycle management | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑165216 | |||
S5‑165145 | pCR TR 28.801 High level use case for creating two new slice instances for different end user services | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165214 | |||
S5‑165214 | pCR TR 28.801 High level use case for creating two new slice instances for different end user services | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165328 | S5‑165145 | ||
S5‑165328 | pCR TR 28.801 High level use case for creating two new slice instances for different end user services | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165363 | S5‑165214 | ||
S5‑165363 | pCR TR 28.801 High level use case for creating two new slice instances for different end user services | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑165328 | |||
S5‑165163 | Revised WID Study on Management and Orchestration of Network Slicing for next generation network | Ericsson LM | SID revised | Yes |
Yes
| agreed | No | |||||
S5‑165164 | Update of Scope | Ericsson LM | pCR | Yes |
Yes
| revised | No | S5‑165209 | ||||
S5‑165209 | Update of Scope | Ericsson LM | pCR | - | Yes |
Yes
| revised | No | S5‑165364 | S5‑165164 | ||
S5‑165364 | Update of Scope | Ericsson LM | pCR | - | Yes |
Yes
| approved | No | S5‑165209 | |||
S5‑165165 | Adding Chapter and content for Concepts and Background | Ericsson LM | pCR | Yes |
Yes
| revised | No | S5‑165212 | ||||
S5‑165212 | Adding Chapter and content for Concepts and Background | Ericsson LM | pCR | - | Yes |
Yes
| revised | No | S5‑165365 | S5‑165165 | ||
S5‑165365 | Adding Chapter and content for Concepts and Background | Ericsson LM | pCR | - | No |
Yes
| left for email approval | No | S5‑165212 | |||
S5‑165167 | Adding Network Slice and related Definitions | Ericsson LM | pCR | Yes |
Yes
| revised | No | S5‑165213 | ||||
S5‑165213 | Adding Network Slice and related Definitions | Ericsson LM | pCR | - | Yes |
Yes
| noted | No | S5‑165167 | |||
S5‑165170 | High level use case for creating two new network slice instances for different end user services | Ericsson LM | pCR | Yes |
Yes
| merged | No | S5‑165214 | ||||
S5‑165194 | Discussion sequence proposal for 6.5.5 | Ericsson LM | discussion | Yes |
Yes
| noted | No | |||||
S5‑165357 | Draft TR 28.801 | Huawei | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.6 | Study on management aspects of next generation network architecture and features | S5‑165031 | Minutes for Study on management aspects of next generation network architecture and features | Rapporteur(Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑165146 | pCR TR 28.802 add use case for supporting cric management case | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165221 | |||
S5‑165221 | pCR TR 28.802 add use case for supporting cric management case | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑165366 | S5‑165146 | ||
S5‑165366 | pCR TR 28.802 add use case for supporting cric management case | Huawei Technologies | pCR | Approval | No |
Yes
| left for email approval | No | S5‑165221 | |||
S5‑165147 | Adding Chapter and content for Concepts and Background | Ericsson LM | other | Yes |
No
| withdrawn | Yes | |||||
S5‑165148 | Adding Network Slice and related Definitions | Ericsson LM | other | No |
No
| withdrawn | Yes | |||||
S5‑165149 | High level use case for creating two new network slice instances for different end user services | Ericsson LM | other | No |
No
| withdrawn | Yes | |||||
S5‑165329 | Study on management aspects of next generation network architecture and features | Nokia | SID revised | discussion | Yes |
Yes
| agreed | No | ||||
S5‑165370 | Draft TS 28.802 | Nokia | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑165008 | CH Agenda and Time Plan | CH SWG Chair | agenda | Yes |
Yes
| approved | No | |||
S5‑165009 | CH Executive Report from THIS Meeting | CH SWG Chair | report | Yes |
YesDue to the absence of the Rapporteur, the Chairman proposed to have new dates for the Study on Overload Control for Diameter Charging Applications: March and June 2017. It was to be consulted whether the current rapporteur, ZTE, would continue the work.
| noted | No | |||||
S5‑165040 | Reply LS from CT3 to SA5 on PDP type extension to non-IP PDN type | C3-162183 | LS in | Yes |
Yes
| noted | No | |||||
S5‑165041 | Resubmitted LS reply from CT4 to SA5 on progress of the work on Diameter Base Protocol Update | C4-163282 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑165042 | Reply LS from CT4 to SA5 on Control Plane CIoT EPS Optimisation Indicator propagated to PGW for charging purpose | C4-164288 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑165045 | Reply LS from SA2 to SA5 for enhancements required for charging of PDN connection to SCEF | S2-163767 | LS in | Yes |
Yes
| noted | No | |||||
S5‑165046 | Response LS from SA2 to SA5 “LS on Control Plane CIoT EPS Optimisation Indicator propagated to PGW for charging purpose” | S2-163768 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑165048 | LS from SA2 to SA5-CH on implication on charging from eFMSS | S2-164279 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑165223 | Reply LS to LS reply from CT4 to SA5 on progress of the work on Diameter Base Protocol Update | Nokia, Alcatel-Lucent Shanghai Bell | LS out | Approval | Yes |
Yes
| approved | No | ||||
S5‑165283 | Meeting co-location with CT WGs in second quarter 2017 for SA5 SWG CH | Charging SWG Chair | other | discussion | Yes |
Yes
| noted | No | ||||
7.2 | New Charging Work Item proposals | S5‑165184 | New WID Charging aspects of Improvements of Awareness of User Location Change | Huawei | WID new | Approval | Yes |
Yes
| revised | No | S5‑165224 | |
S5‑165224 | New WID Charging aspects of Improvements of Awareness of User Location Change | Huawei | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑165184 | |||
S5‑165187 | New WID Study on mandatory AVP for 3GPP Diameter Accounting and Credit-Control Applications | Nokia, Alcatel-Lucent Shanghai Bell | SID new | Agreement | Yes |
Yes
| revised | No | S5‑165222 | |||
S5‑165222 | New WID Study on mandatory AVP for 3GPP Diameter Accounting and Credit-Control Applications | Nokia, Alcatel-Lucent Shanghai Bell | SID new | Agreement | Yes |
Yes
| agreed | No | S5‑165187 | |||
7.3 | Charging Maintenance and Rel-14 small Enhancements | S5‑165052 | Rel-13 CR 32.298 Correction on ASN.1 syntax for IMS, SMS and MONTE CDRs | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||
S5‑165053 | Rel-13 CR 32.251 Correction on Non-IP PDP type - alignement with TS 29.061 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑165233 | |||
S5‑165233 | Rel-13 CR 32.251 Correction on Non-IP PDP type - alignement with TS 29.061 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑165053 | |||
S5‑165054 | Rel-13 CR 32.298 Correction on Non-IP PDP type -alignement with TS 29.061 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑165234 | |||
S5‑165234 | Rel-13 CR 32.298 Correction on Non-IP PDP type -alignement with TS 29.061 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑165054 | |||
S5‑165055 | Rel-13 CR 32.298 Correction on CPDT CDRs ASN.1 description | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑165056 | Rel-13 CR 32.251 Correction on RAT Type for charging SMS in MME | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑165235 | |||
S5‑165235 | Rel-13 CR 32.251 Correction on RAT Type for charging SMS in MME | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑165056 | |||
S5‑165106 | Rel-13 CR 32.251 Correction on Control Plane CIoT EPS Optimisation Indicator in PGW - alignement with 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑165236 | |||
S5‑165236 | Rel-13 CR 32.251 Correction on Control Plane CIoT EPS Optimisation Indicator in PGW - alignement with 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑165106 | |||
S5‑165107 | Rel-13 CR 32.299 Correction on Control Plane CIoT EPS Optimisation Indicator in PGW - alignement with 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑165237 | |||
S5‑165237 | Rel-13 CR 32.299 Correction on Control Plane CIoT EPS Optimisation Indicator in PGW - alignement with 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑165107 | |||
S5‑165108 | Rel-13 CR 32.298 Correction on Control Plane CIoT EPS Optimisation Indicator in PGW - alignement with 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑165238 | |||
S5‑165238 | Rel-13 CR 32.298 Correction on Control Plane CIoT EPS Optimisation Indicator in PGW - alignement with 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑165108 | |||
S5‑165114 | Rel-13 CR 32.253 Remove Editor's Note on parameters over T6a- Alignment with TS 23.282 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑165183 | R14 CR TS32.251 Correction on the General Description | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑165239 | |||
S5‑165239 | R14 CR TS32.251 Correction on the General Description | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑165183 | |||
S5‑165189 | Rel-13 CR 32.251 Correction on "MO exception data" RRC establishment cause in offline charging- alignement with TS 23.401 | Nokia, Alcatel-Lucent Shanghai Bell, Vodafone | CR | Approval | Yes |
Yes
| revised | No | S5‑165240 | |||
S5‑165240 | Rel-13 CR 32.251 Correction on "MO exception data" RRC establishment cause in offline charging- alignement with TS 23.401 | Nokia, Alcatel-Lucent Shanghai Bell, Vodafone | CR | Approval | Yes |
Yes
| agreed | No | S5‑165189 | |||
S5‑165190 | Rel-13 CR 32.299 Correction on "MO exception data" RRC establishment cause in offline charging- alignement with TS 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑165241 | |||
S5‑165241 | Rel-13 CR 32.299 Correction on "MO exception data" RRC establishment cause in offline charging- alignement with TS 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑165190 | |||
S5‑165191 | Rel-13 CR 32.298 Correction on "MO exception data" RRC establishment cause in offline charging- alignement with TS 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑165279 | |||
S5‑165279 | Rel-13 CR 32.298 Correction on "MO exception data" RRC establishment cause in offline charging- alignement with TS 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑165191 | |||
S5‑165280 | Reply LS to Response LSs on Control Plane CIoT Optimisation Indicator propagated to PGW for charging purpose | Nokia, Alcatel-Lucent Shanghai Bell | LS out | Approval | Yes |
Yes
| approved | No | ||||
S5‑165282 | Rel-14 CR 32.299 Correction on Control Plane CIoT EPS Optimisation Indicator in PGW - alignement with 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑165284 | Rel-14 CR 32.299 Correction on "MO exception data" RRC establishment cause in offline charging- alignement with TS 23.401 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
7.4 | Rel-14 Charging |   | ||||||||||
7.4.1 | Resource optimization for PS domain online charging sessions | S5‑165185 | Possibility to terminate the charging session when no quota required | Ericsson LM | other | Agreement | Yes |
Yes
| revised | No | S5‑165225 | |
S5‑165225 | Possibility to terminate the charging session when no quota required | Ericsson LM | other | Approval | Yes |
Yes
| approved | No | S5‑165185 | |||
S5‑165281 | Draft CR General description for Gy Session Optimization | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
7.4.2 | Determination of Completeness of Charging Information in IMS | S5‑165104 | New Section on Determination of Completeness of Charging Information in IMS | Deutsche Telekom AG | CR | Approval | Yes |
Yes
| revised | No | S5‑165226 | |
S5‑165226 | New Section on Determination of Completeness of Charging Information in IMS | Deutsche Telekom AG | CR | Approval | Yes |
Yes
| agreed | No | S5‑165104 | |||
S5‑165109 | Proposed LS to CT1 on DCCII | Deutsche Telekom AG | LS out | Approval | Yes |
Yes
| revised | No | S5‑165227 | |||
S5‑165227 | LS to CT1 on Determination of Completeness of Charging Information in IMS | Deutsche Telekom AG | LS out | Approval | Yes |
Yes
| revised | No | S5‑165371 | S5‑165109 | ||
S5‑165371 | LS to CT1 on Determination of Completeness of Charging Information in IMS | Deutsche Telekom AG | LS out | Approval | Yes |
Yes
| approved | No | S5‑165227 | |||
S5‑165211 | Enhancements to offline charging for IMS | AT&T | discussion | discussion | Yes |
Yes
| noted | No | ||||
7.4.3 | Charging Aspects of Enhanced Proximity-based Services | S5‑165178 | R14 CR TS32.277 Message flow for Direct Communication via UE-to-Network Relay | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑165228 | |
S5‑165228 | R14 CR TS32.277 Message flow for Direct Communication via UE-to-Network Relay | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑165178 | |||
S5‑165179 | R14 CR TS32.277 Message flow for Model B of ProSe Direct Discovery | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑165229 | |||
S5‑165229 | R14 CR TS32.277 Message flow for Model B of ProSe Direct Discovery | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑165179 | |||
S5‑165180 | R14 CR TS32.277 Message flow for ProSe One-to-One Direct Communication | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑165230 | |||
S5‑165230 | R14 CR TS32.277 Message flow for ProSe One-to-One Direct Communication | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑165180 | |||
S5‑165181 | R14 CR TS32.277 Message flow for Restricted Discovery | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑165231 | |||
S5‑165231 | R14 CR TS32.277 Message flow for Restricted Discovery | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑165181 | |||
S5‑165182 | R14 CR TS32.277 Supplement for the ProSe Discovery and Communication | Huawei | CR | Approval | Yes |
Yes
| revised | No | S5‑165232 | |||
S5‑165232 | R14 CR TS32.277 Supplement for the ProSe Discovery and Communication | Huawei | CR | Approval | Yes |
Yes
| agreed | No | S5‑165182 | |||
7.4.4 | Charging Aspects of S8 Home Routing Architecture for VoLTE |   | ||||||||||
7.5 | Charging Studies |   | ||||||||||
7.5.1 | Study on Overload Control for Diameter Charging Applications |   | ||||||||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |