Tdoc List
2017-03-31 11:51
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‑171500 | Agenda | WG Chairman | agenda | Yes |
Yes
| approved | No | |||
3 | IPR declaration | S5‑171532 | IPR and legal declaration | WG Chairman | other | Yes |
Yes
| noted | No | |||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑171501 | Report from SA5#111 | MCC | report | Yes |
Yes
| approved | No | |||
S5‑171778 | Report from SA5#111Bis | MCC | report | Yes |
Yes
| approved | No | |||||
4.2 | Last SA meeting report | S5‑171502 | SA5 status report at last SA meeting | WG Chairman | report | Yes |
Yes
| noted | No | |||
S5‑171503 | SA5 results at last SA meeting | WG Chairman | report | Yes |
YesRobert (Ericsson): if SA5 takes the lead in EE, what does this mean for work to be done in other groups?
The Chair commented that this wasn't mentioned in SA but the work can be done with LS.
Christian (Huawei) commented that other groups work with energy efficiency already, SA doesn’t have a global mandate.
Maryse (Nokia) asked for clarification of the WID summary documents. The Chair commented that SA will provide a list of WIDs where they expect summaries to be made.
| revised | No | S5‑171836 | ||||
S5‑171836 | SA5 results at last SA meeting | WG Chairman | report | - | Yes |
Yes
| noted | No | S5‑171503 | |||
4.3 | Inter-organizational reports | S5‑171616 | Report of 3GPP-BBF Workshop Feb 18th 2017 | WG Vice Chair (Huawei) | report | Information | Yes |
Yes
| noted | No | ||
S5‑171779 | 5G Network and Service Management including Orchestration | Cisco,Deutsche Telekom | other | Presentation | Yes |
Yes
| noted | No | ||||
5 | Cross-SWG issues |   | ||||||||||
5.1 | Administrative issues at SA5 level | S5‑171506 | Leaders meeting agenda | WG Chairman | agenda | Yes |
Yes
| noted | No | |||
S5‑171507 | Leaders meeting minutes | WG Chairman | report | Yes |
Yes
| noted | No | |||||
S5‑171511 | SA5 Working Procedures | WG Vice Chair (Huawei) | other | Yes |
Yes
| approved | No | |||||
S5‑171512 | SA5 Meeting Facility Requirements | WG Vice Chair (Orange) | other | Yes |
Yes
| noted | No | |||||
S5‑171513 | Process for management of draft TSs/TRs | WG Chairman | other | Yes |
Yes
| noted | No | |||||
S5‑171514 | CR Quality Check | MCC | other | Yes |
Yes
| noted | No | |||||
S5‑171533 | Status of email approvals | WG Vice Chair (Orange) | other | No |
No
| reserved | No | |||||
S5‑171577 | TS quality campaign table for first theme | Ericsson LM | other | Yes |
Yes
| endorsed | No | |||||
S5‑171610 | Updated Tdoc_template to allow option of reflecting proposed modifications within relevant TS/TR draft document | NEC EUROPE LTD | other | Approval | Yes |
YesTo be clarified further. There were some concerns on having the whole specification acting as a pCR. MCC argued that this would be type DraftTR/TS instead. MCC also recommended to provide input to SA5 working procedures instead of modifying the official 3GPP template. Instead of a cover, the tdoc template could be put on top so as not to have two docs in the pCR file.
| noted | No | ||||
5.2 | Technical issues at SA5 level |   | ||||||||||
5.3 | Liaison statements at SA5 level | S5‑171728 | Liaison Statement from NGMN Alliance Project NWMO to SA5 on creation of "5G Network and Service Management including Orchestration" | NGMN | LS in | Yes |
Yes
| noted | No | |||
S5‑171734 | LS from ONF to SA5 "For information: Publication of ONF TR-540: Orchestration: A More Holistic View" | Open Networking Foundation (ONF) | LS in | Yes |
YesNokia commented that the link shows a specific set of requirements on orchestration that need to be taken account by SA5: they should be accepted, rejected or ignored.
Nokia proposed to keep this LS open in order to analyze it.
It was decided to postpone it to check the document.
| postponed | No | |||||
S5‑171741 | LS from ETSI TC RRS to SA5 on Finalization and approval of TS 103 379 (LSA protocols and information elements) | ETSI TC RRS | LS in | Yes |
Yes
| noted | No | |||||
S5‑171742 | LS from SA2 cc SA5 on standardization of Northbound SCEF API | S2-170647 | LS in | Yes |
YesMaryse (Nokia) commented that this topic was being discussed in the Charging SWG.
| noted | No | |||||
5.4 | SA5 meeting calendar | S5‑171510 | SA5 Meeting Calendar | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||
5.5 | Review of the Work Plan | S5‑171515 | Deliverables due for the NEXT SA Plenary | ETSI Secretariat | other | Yes |
Yes
| noted | No | |||
S5‑171828 | Deliverables due for the NEXT SA Plenary | ETSI Secretariat | other | - | No |
No
| withdrawn | Yes | ||||
S5‑171516 | Ongoing SA5 WIDs and SIDs | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||||
S5‑171517 | SA5 3GPP Work Plan | ETSI Secretariat | other | Yes |
Yes
| noted | No | |||||
S5‑171536 | Work Plan status | WG Chair | other | No |
No
| reserved | No | |||||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑171504 | Time Plan for OAM&P | WG Vice Chair (Huawei) | other | Yes |
Yes
| revised | No | S5‑171780 | ||
S5‑171780 | Time Plan for OAM&P | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| noted | No | S5‑171504 | |||
S5‑171505 | OAM Executive Report from THIS Meeting | WG Vice Chair (Huawei) | report | Yes |
Yes
| revised | No | S5‑172001 | ||||
S5‑172001 | OAM Executive Report from THIS Meeting | WG Vice Chair (Huawei) | report | - | Yes |
Yes
| noted | No | S5‑171505 | |||
S5‑171535 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | Yes |
Yes
| revised | No | S5‑171955 | ||||
S5‑171955 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| noted | No | S5‑171535 | |||
S5‑171537 | Minutes of OAM&P SWG opening session | WG Vice Chair (Huawei) | report | Yes |
Yes
| noted | No | |||||
S5‑171729 | Reply LS rom CT1 to the progress of QoE Measurement Collection for Streaming to RAN3, SA4, SA5 and CT1 | C1-170510 | LS in | Yes |
Yes
| noted | No | |||||
S5‑171730 | Reply LS from CT1 cc SA5 to the progress of QoE Measurement Collection for Streaming | C1-171221 | LS in | Yes |
Yes
| noted | No | |||||
S5‑171731 | LS from CT4 to SA5 on Trace management aspects for CUPS | C4-171416 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑171811 | Reply to: LS from CT4 to SA5 on Trace management aspects for CUPS | Huawei | LS out | approval | Yes |
Yes
| revised | No | S5‑171956 | |||
S5‑171956 | Reply to: LS from CT4 to SA5 on Trace management aspects for CUPS | Huawei | LS out | approval | Yes |
Yes
| approved | No | S5‑171811 | |||
S5‑171736 | Reply LS from RAN2 to the progress of QoE Measurement Collection for Streaming to RAN3, SA4, SA5 and CT1 | R2-1702095 | LS in | Yes |
Yes
| noted | No | |||||
S5‑171737 | Reply LS from RAN2 to SA5 on the progress of QoE Measurement Collection for Streaming | R2-1702096 | LS in | Yes |
Yes
| noted | No | |||||
S5‑171738 | LS on the progress of QoE Measurement Collection for Streaming to RAN3, SA4, SA5 and CT1 | R2-1702098 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑171739 | Reply to SA5 on the reply LS on Flexible eNB-ID and Cell-ID in E-UTRAN | R3-170850 | LS in | Yes |
Yes
| noted | No | |||||
S5‑171740 | Resubmitted LS reply 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 |
Yes
| replied to | No | |||||
S5‑171745 | LS from SA4 to SA5 on the progress of QoE Measurement Collection for Streaming | S4-170157 | LS in | Yes |
Yes
| noted | No | |||||
S5‑171746 | LS from SA4 ccSA5 SA5 on Reply LS on the progress of QoE Measurement Collection for Streaming | S4-170188 | LS in | Yes |
Yes
| noted | No | |||||
S5‑171751 | LS reply to ATIS NRSC on ”Establish a Metric to Determine a Drop in Registered Users in an IP-Based Network” | ORANGE, Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑171812 | |||
S5‑171812 | LS reply to ATIS NRSC on ”Establish a Metric to Determine a Drop in Registered Users in an IP-Based Network” | ORANGE, Huawei | LS out | Approval | Yes |
Yes
| approved | No | S5‑171751 | |||
6.2 | New OAM&P Work Item proposals | S5‑171518 | Minutes of New Work Item proposals - OAM&P | WG Vice Chair (Orange) | report | Yes |
Yes
| noted | No | |||
S5‑171576 | New WID OAM aspects of LTE and WLAN integration | Intel Corporation (UK) Ltd | WID new | Agreement | Yes |
Yes
| revised | No | S5‑171829 | |||
S5‑171829 | New SID Study on OAM aspects of LTE and WLAN integration | Intel Corporation (UK) Ltd | SID new | Agreement | Yes |
Yes
| agreed | No | S5‑171576 | |||
S5‑171608 | new SID study on network policy management for mobile networks based on NFV scenarios | China Mobile Com. Corporation | SID new | Approval | Yes |
Yes
| revised | No | S5‑171813 | |||
S5‑171813 | new WID study on network policy management for mobile networks based on NFV scenarios | China Mobile Com. Corporation | SID new | Approval | Yes |
Yes
| revised | No | S5‑171957 | S5‑171608 | ||
S5‑171957 | new WID study on network policy management for mobile networks based on NFV scenarios | China Mobile Com. Corporation | SID new | Approval | Yes |
Yes
| revised | No | S5‑171992 | S5‑171813 | ||
S5‑171992 | new WID study on network policy management for mobile networks based on NFV scenarios | China Mobile Com. Corporation | SID new | Approval | Yes |
Yes
| agreed | No | S5‑171957 | |||
S5‑171725 | Control and monitoring of Power, Energy and Environmental (PEE) parameters in Radio Access Networks (RAN) | ORANGE | WID new | Approval | Yes |
Yes
| revised | No | S5‑171814 | |||
S5‑171814 | Control and monitoring of Power, Energy and Environmental (PEE) parameters in Radio Access Networks (RAN) | ORANGE | WID new | Approval | Yes |
Yes
| agreed | No | S5‑171725 | |||
S5‑171726 | Skeleton proposal for TS 28.xxx IRP Requirements | ORANGE | other | Approval | Yes |
Yes
| revised | No | S5‑171960 | |||
S5‑171960 | Skeleton proposal for TS 28.xxx IRP Requirements | ORANGE | other | Approval | No |
Yes
| left for email approval | No | S5‑171726 | |||
S5‑171727 | Skeleton proposal for TS 28.yyy IRP IS | ORANGE | other | Approval | Yes |
Yes
| revised | No | S5‑171961 | |||
S5‑171961 | Skeleton proposal for TS 28.yyy IRP IS | ORANGE | other | Approval | No |
Yes
| left for email approval | No | S5‑171727 | |||
S5‑171776 | New WID on Management of QoE data collection | Ericsson LM | WID new | Yes |
Yes
| revised | No | S5‑171815 | ||||
S5‑171815 | New WID on Management of QoE data collection | Ericsson LM | WID new | - | Yes |
Yes
| revised | No | S5‑171962 | S5‑171776 | ||
S5‑171962 | New WID on Management of QoE data collection | Ericsson LM | WID new | - | Yes |
Yes
| agreed | No | S5‑171815 | |||
6.3 | OAM&P Maintenance and Rel-15 small Enhancements | S5‑171519 | Minutes of OAM&P Maintenance and Rel-15 small Enhancements | MCC | report | Yes |
Yes
| noted | No | |||
S5‑171618 | Discussion paper addition of MTT PRB usage performance measurements | Huawei | discussion | Discussion | Yes |
Yes
| revised | No | S5‑171816 | |||
S5‑171816 | Discussion paper addition of MTT PRB usage performance measurements | Huawei | discussion | Discussion | Yes |
Yes
| revised | No | S5‑171959 | S5‑171618 | ||
S5‑171959 | Discussion paper addition of MTT PRB usage performance measurements | Huawei | discussion | Discussion | Yes |
Yes
| revised | No | S5‑171963 | S5‑171816 | ||
S5‑171963 | Discussion on adding use cases for PRB usage and IP Throughput measurements | Huawei | discussion | Discussion | Yes |
Yes
| revised | No | S5‑171994 | S5‑171959 | ||
S5‑171994 | Discussion on adding use cases for PRB usage and IP Throughput measurements | Huawei | discussion | Discussion | No |
Yes
| left for email approval | No | S5‑171963 | |||
S5‑171619 | Discussion paper addition of IP throughput performance measurements | Huawei | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑171620 | Rel-14 CR 32.425 Add MTT PRB performance measurements use case | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑171621 | Rel-14 CR 32.425 Add IP throughput performance measurements use case | Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑171634 | R14 CR 32401-d10 Correction of internal references. Editorial updates. | Ericsson AB | CR | Approval | Yes |
Yes
| revised | No | S5‑171817 | |||
S5‑171817 | R14 CR 32401-d10 Correction of internal references. | Ericsson AB | CR | Approval | Yes |
Yes
| agreed | No | S5‑171634 | |||
S5‑171712 | Discussion on use cases and definition for average number of active UEs | China Telecom, Huawei | discussion | Discussion | Yes |
Yes
| revised | No | S5‑171933 | |||
S5‑171933 | Discussion on use cases and definition for average number of active UEs | China Telecom, Huawei | discussion | Discussion | Yes |
Yes
| revised | No | S5‑171964 | S5‑171712 | ||
S5‑171964 | Discussion on use cases and definition for average number of active UEs | China Telecom, Huawei | discussion | Discussion | Yes |
Yes
| revised | No | S5‑171995 | S5‑171933 | ||
S5‑171995 | Discussion on use cases and definition for average number of active UEs | China Telecom, Huawei | discussion | Discussion | No |
Yes
| left for email approval | No | S5‑171964 | |||
S5‑171713 | Rel-14 CR 32.425 Add use cases and definition for average number of active UEs | China Telecom, Huawei | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑171838 | Rel-8 32.401 Correction of internal reference | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑171839 | Rel-9 32.401 Correction of internal reference | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑171840 | Rel-10 32.401 Correction of internal reference | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑171841 | Rel-11 32.401 Correction of internal reference | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑171842 | Rel-12 32.401 Correction of internal reference | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑171843 | Rel-13 32.401 Correction of internal reference | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑171993 | LS to RAN2 on adding PRB usage distribution and IP Throughput distribution measurements | Huawei | LS out | Approval | No |
Yes
| left for email approval | No | ||||
S5‑171996 | LS to RAN2 on adding average number of total active Ues | Huawei | LS out | Approval | No |
Yes
| left for email approval | No | ||||
6.4 | Rel-15 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‑171522 | Minutes for Management concept, architecture and requirements for mobile networks that include virtualized network functions | Rapporteur(China Mobile) | report | Yes |
Yes
| noted | No | |||
6.4.1.2 | Configuration Management for mobile networks that include virtualized network functions | S5‑171523 | Minutes for Configuration Management for mobile networks that include virtualized network functions | Rapporteur(ZTE) | report | Yes |
Yes
| noted | No | |||
S5‑171547 | Add UC on querying MO attributes that may trigger VNF scaling | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171830 | Add UC on querying MO attributes that may trigger VNF scaling | Intel Corporation (UK) Ltd | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑171548 | Discussion paper on NRMs supporting query of MO attributes that may trigger VNF scaling | Intel Corporation (UK) Ltd | discussion | Agreement | Yes |
Yes
| noted | No | ||||
S5‑171578 | pCR 28.510-Rapporteur Cleanup | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑171579 | discussion paper about solution of enabling-disabling auto-scaling | ZTE Corporation | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑171580 | pCR TS 28510 Add enabling-disabling auto-scaling use case and requirement | ZTE Corporation, Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171581 | pCR TS 28510 Add VNF information sysnchronization use case | ZTE Corporation, Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑171832 | |||
S5‑171832 | pCR TS 28510 Add VNF information sysnchronization use case | ZTE Corporation, Nokia | pCR | Approval | Yes |
Yes
| noted | No | S5‑171581 | |||
S5‑171965 | pCR TS 28510 Add VNF information sysnchronization use case | ZTE Corporation, Nokia | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑171582 | pCR TS 28511 Add procedure of enable-disable autoscaling through Itf-N | ZTE Corporation, Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171583 | pCR TS 28511 Add procedure of VNF instance informaiton synchronization | ZTE Corporation, Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171834 | pCR TS 28511 Add procedure of VNF instance informaiton synchronization | ZTE Corporation, Nokia | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑171584 | discussion paper about solution of creating MOI triggering VNF instantiation | ZTE Corporation, Intel | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑171585 | pCR 28.511-Rapporteur's proposal | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑171845 | |||
S5‑171845 | pCR 28.511-Rapporteur's proposal | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑171585 | |||
S5‑171586 | pCR 28.512-Rapporteur proposal | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑171587 | pCR TS 28512 Add description of interface definition | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑171937 | |||
S5‑171937 | pCR TS 28512 Add description of interface definition | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑171587 | |||
S5‑171588 | R14 CR TS 28.622 Add VNFInfo related attributes in IOC ManagedFunction | ZTE Corporation, Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑171844 | |||
S5‑171844 | R14 CR TS 28.622 Add VNFInfo related attributes in IOC ManagedFunction | ZTE Corporation, Intel | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑171588 | |||
S5‑171641 | pCR TS 28.510 Removing UC and reqs for unsupported VNF instantiation through Itf-N | NTT DOCOMO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171642 | pCR TS 28.510 Removing unsupported scaling notification from EM to NM | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑171833 | |||
S5‑171833 | pCR TS 28.510 Removing unsupported scaling notification from EM to NM | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑171642 | |||
S5‑171643 | pCR TS 28.511 Changing procedure to remove unsupported VNF instantiation indication through Itf-N | NTT DOCOMO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171644 | pCR TS 28.511 Changing procedure to remove unsupported VNF scaling notification through Itf-N | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑171835 | |||
S5‑171835 | pCR TS 28.511 Changing procedure to remove unsupported VNF scaling notification through Itf-N | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑171644 | |||
S5‑171822 | discussion sequence proposal | ZTE | other | Information | Yes |
Yes
| noted | No | ||||
S5‑171831 | Draft TS 28.510 | ZTE | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑171837 | Draft TS 28.512 | ZTE | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑171944 | R14 CR TS 28.622 add auto-scaling switch in IOCManagedFunction | ZTE | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑171966 | 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‑171524 | Minutes for Fault Management for mobile networks that include virtualized network functions | Rapporteur(Huawei) | report | No |
No
| withdrawn | Yes | |||
6.4.1.4 | Performance management for mobile networks that include virtualized network functions | S5‑171525 | Minutes for Performance management for mobile networks that include virtualized network functions | Rapporteur(Intel) | report | Yes |
Yes
| noted | No | |||
S5‑171542 | pCR TS 28.520 Rapporteur update for EditHelp | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑171543 | pCR TS 28.520 removal of editor note | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171544 | pCR TS 28.520 correct the requirement references in the tracibility field | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑171883 | |||
S5‑171883 | pCR TS 28.520 correct the requirement references in the tracibility field | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑171544 | |||
S5‑171545 | pCR TS 28.520 delete unused requirement and change requirement reference | Intel Corporation (UK) Ltd | pCR | Decision | Yes |
Yes
| revised | No | S5‑171873 | |||
S5‑171873 | pCR TS 28.520 delete unused requirement and change requirement reference | Intel Corporation (UK) Ltd | pCR | Decision | Yes |
Yes
| approved | No | S5‑171545 | |||
S5‑171550 | pCR TS 28.520 Correction of NFV PM UCs | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑171876 | |||
S5‑171876 | pCR TS 28.520 Correction of NFV PM UCs | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑171550 | |||
S5‑171872 | Draft TS 28.520 | 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‑171526 | Minutes for Lifecycle management for mobile networks that include virtualized network functions | Rapporteur (Nokia Networks) | report | Yes |
Yes
| revised | No | S5‑171797 | ||
S5‑171797 | Minutes for Lifecycle management for mobile networks that include virtualized network functions | Rapporteur (Nokia Networks) | report | - | Yes |
Yes
| noted | No | S5‑171526 | |||
S5‑171549 | Discussion paper on supporting selection of EM in VNF instantiation | Intel Corporation (UK) Ltd | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑171929 | |||
S5‑171929 | Discussion paper on supporting selection of EM in VNF instantiation | Intel Corporation (UK) Ltd | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑171549 | |||
S5‑171640 | R14 CR TS 28.525 Moving LCM supported use cases and requirements from TS 28.510 | NTT DOCOMO | CR | Agreement | Yes |
Yes
| revised | No | S5‑171877 | |||
S5‑171877 | R14 CR TS 28.525 Moving LCM supported use cases and requirements from TS 28.510 | NTT DOCOMO | CR | Agreement | Yes |
Yes
| agreed | No | S5‑171640 | |||
S5‑171762 | CR TS 28.525 VNF application software update | Gemalto N.V. | CR | Approval | Yes |
Yes
| revised | No | S5‑171878 | |||
S5‑171878 | CR TS 28.525 VNF application software update | Gemalto N.V. | CR | Approval | Yes |
Yes
| revised | No | S5‑171958 | S5‑171762 | ||
S5‑171958 | CR TS 28.525 VNF application software update | Gemalto N.V. | CR | Agreement | Yes |
Yes
| agreed | No | S5‑171878 | |||
6.4.2 | Filtering of PM measurements and data volume measurements for shared networks | S5‑171527 | Minutes for Filtering of PM measurements and data volume measurements for shared networks | Rapporteur(Ericsson) | report | No |
No
| withdrawn | Yes | |||
6.4.3 | OAM support for Licensed Shared Access (LSA) | S5‑171534 | Minutes of OAM support for Licensed Shared Access (LSA) | Rapporteur (Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑171696 | pCR TS 28.301 Modify use cases for LSA scenario 2 | TELECOM ITALIA S.p.A. | pCR | Approval | Yes |
Yes
| revised | No | S5‑171880 | |||
S5‑171880 | pCR TS 28.301 Modify use cases for LSA scenario 2 | TELECOM ITALIA S.p.A. | pCR | Approval | Yes |
Yes
| approved | No | S5‑171696 | |||
S5‑171697 | pCR TS 28.302 LSACell attributes | TELECOM ITALIA S.p.A. | pCR | Approval | Yes |
Yes
| revised | No | S5‑171881 | |||
S5‑171881 | pCR TS 28.302 LSACell attributes | TELECOM ITALIA S.p.A. | pCR | Approval | Yes |
Yes
| approved | No | S5‑171697 | |||
S5‑171708 | pCR 28.302 Add System Context for scenario 2 | Nokia | pCR | Yes |
Yes
| revised | No | S5‑171882 | ||||
S5‑171882 | pCR 28.302 Add System Context for scenario 2 | Nokia | pCR | - | Yes |
Yes
| approved | No | S5‑171708 | |||
S5‑171709 | pCR 28.302 Add model for scenario 2 | Nokia | pCR | Yes |
Yes
| revised | No | S5‑171884 | ||||
S5‑171884 | pCR 28.302 Add model for scenario 2 | Nokia | pCR | - | Yes |
Yes
| revised | No | S5‑171969 | S5‑171709 | ||
S5‑171969 | pCR 28.302 Add model for scenario 2 | Nokia | pCR | - | Yes |
Yes
| approved | No | S5‑171884 | |||
S5‑171710 | pCR 28.302 Add operations and notifications allowing the NM to get LSRAI from the LC | Nokia | pCR | Yes |
Yes
| revised | No | S5‑171885 | ||||
S5‑171885 | pCR 28.302 Add operations and notifications allowing the NM to get LSRAI from the LC | Nokia | pCR | - | Yes |
Yes
| approved | No | S5‑171710 | |||
S5‑171711 | pCR 28.302 Add operations and notifications allowing the LC to get LSRAI confirmation from the NM | Nokia | pCR | Yes |
Yes
| revised | No | S5‑171886 | ||||
S5‑171886 | pCR 28.302 Add operations and notifications allowing the LC to get LSRAI confirmation from the NM | Nokia | pCR | - | Yes |
Yes
| approved | No | S5‑171711 | |||
S5‑171967 | Draft TS 28.301 | Nokia | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑171968 | Draft TS 28.302 | 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‑171528 | Minutes of Study on OAM support for assessment of energy efficiency in mobile access networks | Rapporteur (Orange) | report | Yes |
Yes
| noted | No | |||
S5‑171629 | Discussion paper on EE work in SA5 | ORANGE | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑171733 | Liaison to 3GPP SA5 in response to S5-166351, and S5-171384 | ETSI TC EE | LS in | Yes |
Yes
| noted | No | |||||
S5‑171747 | Resubmitted LS from ITU-T to SA5 on seeking collaboration on draft Recommendation "Energy efficiency Metrics and measurement methodology for 5G solutions" | ITU-T Study Group 5 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑171887 | Cover sheet TR 32.856 | ORANGE | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
6.5.2 | Study on OAM aspects of SON for AAS-based deployments | S5‑171529 | Minutes for Study on OAM aspects of SON for AAS-based deployments | Rapporteur (Nokia Networks) | report | Yes |
Yes
| noted | No | |||
S5‑171591 | pCR to TR 32.865 Clarification of Cell splitting | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑171898 | |||
S5‑171898 | pCR to TR 32.865 Clarification of Cell splitting | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑171952 | S5‑171591 | ||
S5‑171952 | pCR to TR 32.865 Clarification of Cell splitting | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑171898 | |||
S5‑171592 | pCR to TR 32.865 Clarification of Cell merging | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑171899 | |||
S5‑171899 | pCR to TR 32.865 Clarification of Cell merging | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑171953 | S5‑171592 | ||
S5‑171953 | pCR to TR 32.865 Clarification of Cell merging | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑171899 | |||
S5‑171593 | pCR to TR 32.865 Clarification of Cell shaping.doc | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑171900 | |||
S5‑171900 | pCR to TR 32.865 Clarification of Cell shaping.doc | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑171954 | S5‑171593 | ||
S5‑171954 | pCR to TR 32.865 Clarification of Cell shaping.doc | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑171900 | |||
S5‑171594 | pCR to TR 32.865 Hybrid SON for AAS | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171901 | pCR to TR 32.865 Hybrid SON for AAS | Cisco Systems Inc. | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑171611 | pCR TR 32.865 Clause 8 - Conclusions | Nokia Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑171902 | |||
S5‑171902 | pCR TR 32.865 Clause 8 - Conclusions | Nokia Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑171611 | |||
S5‑171612 | pCR TR 32.865 Clause 9 - Recommendations | Nokia Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑171903 | |||
S5‑171903 | pCR TR 32.865 Clause 9 - Recommendations | Nokia Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑171612 | |||
S5‑171970 | Draft TR 32.865 | Nokia | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.3 | Study on Implementation for the Partitioning of Itf-N | S5‑171521 | Minutes for Study on Implementation for the Partitioning of Itf-N | Rapporteur(China Mobile) | report | Yes |
Yes
| noted | No | |||
S5‑171617 | Revised WID Study on Implementation for the Partitioning of Itf-N | China Mobile Com. Corporation | SID revised | Yes |
Yes
| agreed | No | |||||
6.5.4 | Study on Management and Orchestration Architecture of Next Generation Network and Service | S5‑171520 | Minutes for Study on Management and Orchestration Architecture of Next Generation Network and Service | Rapporteur (Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑171555 | pCR TR 28.800 Add architecture option to support network slice management | Intel Corporation (UK) Ltd | pCR | Yes |
Yes
| revised | No | S5‑171904 | ||||
S5‑171904 | pCR TR 28.800 Add architecture option to support network slice management | Intel Corporation (UK) Ltd | pCR | - | Yes |
Yes
| revised | No | S5‑171971 | S5‑171555 | ||
S5‑171971 | pCR TR 28.800 Add architecture option to support network slice management | Intel Corporation (UK) Ltd | pCR | - | Yes |
Yes
| revised | No | S5‑171998 | S5‑171904 | ||
S5‑171998 | pCR TR 28.800 Add architecture option to support network slice management | Intel Corporation (UK) Ltd | pCR | - | Yes |
Yes
| approved | No | S5‑171971 | |||
S5‑171645 | pCR TR 28.800 Text proposal on the Management architecture introduction | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171905 | |||
S5‑171905 | pCR TR 28.800 Text proposal on the Management architecture introduction | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171972 | S5‑171645 | ||
S5‑171972 | pCR TR 28.800 Text proposal on the Management architecture introduction | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑171905 | |||
S5‑171646 | pCR TR 28.800 Adding management functions of next generation networks and services | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171906 | |||
S5‑171906 | pCR TR 28.800 Adding management functions of next generation networks and services | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171973 | S5‑171646 | ||
S5‑171973 | pCR TR 28.800 Adding management functions of next generation networks and services | Huawei | pCR | Approval | No |
Yes
| left for email approval | No | S5‑171906 | |||
S5‑171647 | pCR TR 28.800 Adding use case and requirements for data collection and reporting | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171907 | |||
S5‑171907 | pCR TR 28.800 Adding use case and requirements for data collection and reporting | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171974 | S5‑171647 | ||
S5‑171974 | pCR TR 28.800 Adding use case and requirements for data collection and reporting | Huawei | pCR | Approval | No |
Yes
| left for email approval | No | S5‑171907 | |||
S5‑171648 | pCR TR 28.800 Adding data collection and reporting function | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171649 | pCR TR 28.800 Text proposal on the Management architecture introduction | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑171650 | pCR TR 28.800 Adding management functions of next generation networks and services | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑171651 | pCR TR 28.800 Adding use case and requirements for data collection and reporting | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑171652 | pCR TR 28.800 Adding data collection and reporting function | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑171997 | Draft TR 28.800 | Huawei | draft TR | discussion | No |
Yes
| left for email approval | No | ||||
6.5.5 | Study on Management and Orchestration of Network Slicing | S5‑171530 | Minutes for Study on Management and Orchestration of Network Slicing | Rapporteur (Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑171551 | pCR TR 28.801 Add UC on Self-Creation of NSI | Intel Corporation (UK) Ltd | pCR | Yes |
Yes
| revised | No | S5‑171866 | ||||
S5‑171866 | pCR TR 28.801 Add UC on Self-Creation of NSI | Intel Corporation (UK) Ltd | pCR | - | Yes |
Yes
| noted | No | S5‑171551 | |||
S5‑171552 | pCR TR 28.801 Add UC on Self-reconfiguration of NSI | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑171867 | |||
S5‑171867 | pCR TR 28.801 Add UC on Self-reconfiguration of NSI | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑171552 | |||
S5‑171553 | pCR TR 28.801 Add UC on Self-Optimization of NSI | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑171868 | |||
S5‑171868 | pCR TR 28.801 Add UC on Self-Optimization of NSI | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑171915 | S5‑171553 | ||
S5‑171915 | pCR TR 28.801 Add UC on Self-Optimization of NSI | Huawei, Intel, CATT, CATR, China Telecom | pCR | Approval | Yes |
Yes
| approved | No | S5‑171868 | |||
S5‑171554 | pCR TR 28.801 Add UC on Self-Healing of NSI | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| merged | No | S5‑171910 | |||
S5‑171909 | pCR TR 28.801 Add UC on Self-Healing of NSI | Intel Corporation (UK) Ltd | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑171559 | pCR 28.801 Clean-up of introduction clause | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171560 | pCR 28.801 Clean-up of Network Slice Instance lifecycle description | Nokia | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑171826 | pCR 28.801 Clean-up of Network Slice Instance lifecycle description | Nokia,Huawei | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑171561 | pCR 28.801 Clean-up of Network slice concepts | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑171827 | |||
S5‑171827 | pCR 28.801 Clean-up of Network slice concepts | Nokia,Huawei,Cisco | pCR | Approval | Yes |
Yes
| noted | No | S5‑171561 | |||
S5‑171562 | pCR 28.801 Clean-up of Network slice subnet concepts | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑171846 | |||
S5‑171846 | pCR 28.801 Clean-up of Network slice subnet concepts | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑171975 | S5‑171562 | ||
S5‑171975 | pCR 28.801 Clean-up of Network slice subnet concepts | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑171846 | |||
S5‑171563 | pCR 28.801 Remove invalid UC | Nokia | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑171564 | pCR 28.801 Clean-up Use Case for Management support to the network slicing | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑171912 | |||
S5‑171912 | pCR 28.801 Clean-up Use Case for Management support to the network slicing | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑171564 | |||
S5‑171565 | pCR 28.801 Generalize Use Case for creating NSI | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑171913 | |||
S5‑171913 | pCR 28.801 Generalize Use Case for creating NSI | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑171916 | S5‑171565 | ||
S5‑171916 | pCR 28.801 Generalize Use Case for creating NSI | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑171913 | |||
S5‑171566 | pCR 28.801 Generalize Use Cases for modifying and terminating NSI | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171567 | pCR 28.801 Clean-up Use Case for network slice creation | Nokia | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑171568 | pCR 28.801 Clean-up Use Case for changing capacity of a NSI | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑171914 | |||
S5‑171914 | pCR 28.801 Clean-up Use Case for changing capacity of a NSI | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑171976 | S5‑171568 | ||
S5‑171976 | pCR 28.801 Clean-up Use Case for changing capacity of a NSI | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑171914 | |||
S5‑171569 | pCR 28.801 Clean-up Use Case for changing capacity of a NSSI | Nokia | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑171570 | pCR 28.801 Clean-up requirements for network slice lifecycle management | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑171821 | |||
S5‑171821 | pCR 28.801 Clean-up requirements for network slice lifecycle management | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑171570 | |||
S5‑171571 | pCR 28.801 Clean-up requirements for network slice configuration management | Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑171820 | |||
S5‑171820 | pCR 28.801 Clean-up requirements for network slice configuration management | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑171571 | |||
S5‑171595 | pCR to 28.801 Network slice concepts correction | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑171827 | |||
S5‑171596 | pCR to 28.801 Information model correction | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑171827 | |||
S5‑171597 | pCR to 28.801 Information model correction 2 | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171598 | pCR to 28.801 Network slice subnet concept clarification | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| merged | No | S5‑171846 | |||
S5‑171599 | pCR to 28.801 Clarification of the SON concepts in network slicing | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑171847 | |||
S5‑171847 | pCR to 28.801 Clarification of the SON concepts in network slicing | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑171599 | |||
S5‑171600 | pCR to 28.801 Key issues clarification | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑171863 | |||
S5‑171863 | pCR to 28.801 Key issues clarification | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑171600 | |||
S5‑171624 | pCR 28.801 Proposal for classifying use cases and requirements | ORANGE, Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑171819 | |||
S5‑171635 | pCR TR 28.801 Adding use case for providing network slice service with guaranteed quality of performance | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑171917 | |||
S5‑171917 | pCR TR 28.801 Adding use case for providing network slice service with guaranteed quality of performance | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑171635 | |||
S5‑171636 | pCR TR 28.801 Add requirements related to monitor performance | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑171977 | |||
S5‑171977 | pCR TR 28.801 Add requirements related to monitor performance | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑171636 | |||
S5‑171637 | pCR TR 28.801 Adding use case for flexible deploying NSI based on customer’s service requirement | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑171918 | |||
S5‑171918 | pCR TR 28.801 Adding use case for flexible deploying NSI based on customer’s service requirement | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑171637 | |||
S5‑171638 | pCR TR 28.801 Adding use case for management data isolation with shared AN andor common CN network functions | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑171919 | |||
S5‑171919 | pCR TR 28.801 Adding use case for management data isolation with shared AN andor common CN network functions | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑171638 | |||
S5‑171639 | pCR TS 28 801 Modify UC management for support frequency spectrum use case | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑171920 | |||
S5‑171920 | pCR TS 28 801 Modify UC management for support frequency spectrum use case | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑171999 | S5‑171639 | ||
S5‑171999 | pCR TS 28 801 Modify UC management for support frequency spectrum use case | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑172000 | S5‑171920 | ||
S5‑172000 | pCR TS 28 801 Modify UC management for support frequency spectrum use case | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑171999 | |||
S5‑171655 | pCR TR 28.801 Add network slicing related performance measurement data aggregation solution | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑171656 | pCR TR 28.801 Add network slicing related alarm data aggregation solution | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑171657 | pCR TR 28.801 Add usecase and requirements for configuring CN with slice specific information | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑171921 | |||
S5‑171921 | pCR TR 28.801 Add usecase and requirements for configuring CN with slice specific information | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑171978 | S5‑171657 | ||
S5‑171978 | pCR TR 28.801 Add usecase and requirements for configuring CN with slice specific information | Huawei, China Mobile | pCR | Approval | No |
Yes
| left for email approval | No | S5‑171921 | |||
S5‑171658 | pCR TR 28.801 Add potential solutions for NST and NSST | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑171659 | pCR TR 28.801 Add potential solution for management data isolation when network slice instance is shared by multiple customers | Huawei, CATR | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑171660 | pCR TR 28.801 Update on network slice concepts | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑171827 | |||
S5‑171661 | pCR TR 28.801 Update on network slice subnet concepts | Huawei, CATT | pCR | Approval | Yes |
Yes
| merged | No | S5‑171846 | |||
S5‑171662 | pCR TR 28.801 Adding requirements related to lifecycle management | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171930 | |||
S5‑171930 | pCR TR 28.801 Adding requirements related to lifecycle management | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑171662 | |||
S5‑171663 | pCR TR 28.801 Update the monitor performance related requirement | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171931 | |||
S5‑171931 | pCR TR 28.801 Update the monitor performance related requirement | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑171663 | |||
S5‑171664 | pCR TR 28.801 Configuration of RAN transport network related interfaces | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171922 | |||
S5‑171922 | pCR TR 28.801 Configuration of RAN transport network related interfaces | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171979 | S5‑171664 | ||
S5‑171979 | pCR TR 28.801 Configuration of RAN transport network related interfaces | Huawei | pCR | Approval | No |
Yes
| left for email approval | No | S5‑171922 | |||
S5‑171665 | pCR TR 28.801 Generic customer service provision procedure | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑171666 | pCR TR 28.801 Procedure for nework slice provision | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑171667 | pCR TR 28.801 Update types of slices | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑171668 | pCR TR 28.801 Add use case and requirements for changing topology of a NSI | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171923 | pCR TR 28.801 Add use case and requirements for changing topology of a NSI | Huawei | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑171669 | pCR TR 28.801 Add use case and requirements for changing topology of a NSSI | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171924 | pCR TR 28.801 Add use case and requirements for changing topology of a NSSI | Huawei | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑171670 | pCR TR 28.801 Update the potential solution for management support to facilitate UE roaming between NSIs in different administrative domain | Huawei, China Unicom | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑171671 | pCR TR 28.801 Add potential solution for NSI related service performance measurement | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑171672 | pCR TR 28.801 Add potential solution for NSI supervision | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑171673 | pCR TR 28.801 Add potential solution for NSI activation | Huawei, China Telecom | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑171674 | pCR TR 28.801 Add potential solution for NSI deactivation | Huawei, China Telecom | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑171675 | pCR TR 28.801 Add use case and requirements for NSI Self-Healing | Huawei, China Telecom, CATR, CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑171910 | |||
S5‑171910 | pCR TR 28.801 Add use case and requirements for NSI Self-Healing | Huawei, Intel, CATT, CATR, China Telecom | pCR | Approval | Yes |
Yes
| approved | No | S5‑171675 | |||
S5‑171676 | pCR TR 28.801 Add use case and requirements for NSSI Self-Healing | Huawei, China Telecom, CATR | pCR | Approval | Yes |
Yes
| revised | No | S5‑171911 | |||
S5‑171911 | pCR TR 28.801 Add use case and requirements for NSSI Self-Healing | Huawei, Intel, CATT, CATR, China Telecom | pCR | Approval | Yes |
Yes
| approved | No | S5‑171676 | |||
S5‑171677 | pCR TR 28.801 Add use case and requirements for management support to redundant NSSIs and NSSI constituents | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171925 | pCR TR 28.801 Add use case and requirements for management support to redundant NSSIs and NSSI constituents | Huawei | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑171678 | pCR TR 28.801 Add use case and requirements for NSI self-optimization | Huawei, China Telecom, CATR, CATT | pCR | Approval | Yes |
Yes
| revised | No | S5‑171869 | |||
S5‑171869 | pCR TR 28.801 Add use case and requirements for NSI self-optimization | Huawei, China Telecom, CATR, CATT | pCR | Approval | Yes |
Yes
| merged | No | S5‑171915 | S5‑171678 | ||
S5‑171679 | pCR TR 28.801 Add use case and requirements for NSSI self-optimization | Huawei, China Telecom, CATR | pCR | Approval | Yes |
Yes
| revised | No | S5‑171908 | |||
S5‑171908 | pCR TR 28.801 Add use case and requirements for NSSI self-optimization | Huawei, Intel, CATT, CATR, China Telecom | pCR | Approval | Yes |
Yes
| approved | No | S5‑171679 | |||
S5‑171680 | pCR TR 28.801 Add use case and requirements for resource balancing among NSIs | Huawei, China Mobile | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171926 | pCR TR 28.801 Add use case and requirements for resource balancing among NSIs | Huawei, China Mobile | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑171681 | pCR TR 28.801 Add use case and requirement for network slice priority | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171927 | pCR TR 28.801 Add use case and requirement for network slice priority | Huawei | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑171682 | pCR TR 28.801 Add potential solution of limited level of management exposure for network slicing | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑171683 | pCR TR 28.801 Add use case and requirements for NSI reversion | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171684 | pCR TR 28.801 Update potential solution of modifying a NSI | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑171685 | pCR TR 28.801 Add requirement for network slice management | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171932 | |||
S5‑171932 | pCR TR 28.801 Add requirement for network slice management | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171980 | S5‑171685 | ||
S5‑171980 | pCR TR 28.801 Add requirement for network slice management | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑171932 | |||
S5‑171686 | pCR TR 28.801 Update SON concept | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171864 | |||
S5‑171864 | pCR TR 28.801 Update SON concept | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171981 | S5‑171686 | ||
S5‑171981 | pCR TR 28.801 Update SON concept | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑171864 | |||
S5‑171687 | Discussion on network slicing designing | Huawei | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑171688 | pCR TR 28.801 Add UC on management support for RAN self-configuration for an NSI | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑171908 | |||
S5‑171689 | pCR TR 28.801 Clean up of multi operator use case | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171951 | |||
S5‑171951 | pCR TR 28.801 Clean up of multi operator use case | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑171689 | |||
S5‑171690 | pCR TR 28.801 Add proposed solutions for managed entity lifecycles | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑171691 | pCR TR 28.801 Improve network slice management functions diagram | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171865 | |||
S5‑171865 | pCR TR 28.801 Improve network slice management functions diagram | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑171691 | |||
S5‑171698 | pCR 28.801 Proposed note on roles Network Operator and Communication Service Provider | ORANGE | pCR | Approval | Yes |
Yes
| revised | No | S5‑171982 | |||
S5‑171982 | pCR 28.801 Proposed note on roles Network Operator and Communication Service Provider | ORANGE | pCR | Approval | No |
Yes
| left for email approval | No | S5‑171698 | |||
S5‑171735 | LS Reply from ETSI NFV to 3GPP SA5 on NFV Support to Network Slicing Management | ETSI ISG NFV | LS in | Yes |
Yes
| noted | No | |||||
S5‑171748 | Reply LS from TSG SA to SA5 on management of network slices for transport and virtualization aspects | SP-170276 | LS in | Yes |
Yes
| noted | No | |||||
S5‑171750 | Resubmitted Response from SA2 to SA5 on the clarification of the definition of NSI and the relation to NST (S2-170035/S5-166479) | S2-170598 | LS in | Yes |
Yes
| noted | No | |||||
S5‑171753 | pCR TR 28.801 Add general network slice management requirements to Clause 6 | Ericsson LM | pCR | Yes |
Yes
| revised | No | S5‑171934 | ||||
S5‑171934 | pCR TR 28.801 Add general network slice management requirements to Clause 6 | Ericsson LM | pCR | - | Yes |
Yes
| approved | No | S5‑171753 | |||
S5‑171754 | pCR TR 28 801 Draft conclusions and recommendations | Ericsson LM | pCR | Yes |
Yes
| not treated | No | |||||
S5‑171755 | pCR TR 28 801 Rapporteur update on network slice subnet consistency | Ericsson LM | pCR | Yes |
Yes
| approved | No | |||||
S5‑171756 | pCR TR 28 801 Rapporteur update on requirements | Ericsson LM | pCR | Yes |
Yes
| noted | No | |||||
S5‑171757 | pCR TR 28 801 Rapporteur update on use cases | Ericsson LM | pCR | Yes |
Yes
| revised | No | S5‑171819 | ||||
S5‑171819 | Rapporteur update on use cases | Ericsson LM | discussion | - | Yes |
Yes
| revised | No | S5‑171874 | S5‑171757 | ||
S5‑171874 | Rapporteur update on use cases | Ericsson LM | discussion | - | Yes |
Yes
| endorsed | No | S5‑171819 | |||
S5‑171758 | pCR TR 28 801 Rapporteur update text alignment shared and dedicated | Ericsson LM | pCR | Yes |
Yes
| revised | No | S5‑171825 | ||||
S5‑171825 | pCR TR 28 801 Rapporteur update text alignment shared and dedicated | Ericsson LM | pCR | - | Yes |
Yes
| revised | No | S5‑171871 | S5‑171758 | ||
S5‑171871 | pCR TR 28 801 Rapporteur update text alignment shared and dedicated | Ericsson LM | pCR | - | Yes |
Yes
| approved | No | S5‑171825 | |||
S5‑171759 | pCR TR 28 801 Use case and requirements for NSS capability exposure | Ericsson LM | pCR | Yes |
Yes
| revised | No | S5‑171928 | ||||
S5‑171928 | pCR TR 28 801 Use case and requirements for NSS capability exposure | Ericsson LM | pCR | - | Yes |
Yes
| noted | No | S5‑171759 | |||
S5‑171760 | pCR TR 28.801 Update use case and requirements for activation and de-activation of a NSSI | Ericsson LM | pCR | Yes |
Yes
| noted | No | |||||
S5‑171761 | pCR TR 28.801 Update use case and requirements for change capacity of a NSSI | Ericsson LM | pCR | Yes |
Yes
| noted | No | |||||
S5‑171763 | pCR TR 28.801 Update use case and requirements for creation and termination of NSSI | Ericsson LM | pCR | Yes |
Yes
| noted | No | |||||
S5‑171764 | pCR TR 28.801 Update use case and requirements for modification of a NSSI | Ericsson LM | pCR | Yes |
Yes
| noted | No | |||||
S5‑171765 | pCR TR 28 801 Network slicing solution description | Ericsson LM | pCR | Yes |
Yes
| not treated | No | |||||
S5‑171766 | pCR TR 28 801 Description of the meaning of completeness | Ericsson LM | pCR | Yes |
Yes
| noted | No | |||||
S5‑171767 | Sequence proposal for network slicing 6.5.5 | Ericsson LM | other | Yes |
Yes
| revised | No | S5‑171818 | ||||
S5‑171818 | Sequence proposal for network slicing 6.5.5 | Ericsson LM | other | - | Yes |
Yes
| revised | No | S5‑171875 | S5‑171767 | ||
S5‑171875 | Sequence proposal for network slicing 6.5.5 | Ericsson LM | other | - | Yes |
Yes
| noted | No | S5‑171818 | |||
S5‑171823 | Reorganization of requirements | Ericsson | discussion | Endorsement | No |
No
| withdrawn | Yes | ||||
S5‑171824 | Update of requirements | Ericsson | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑171870 | Draft TR 28.801 | Ericsson | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
S5‑171879 | Report from breakout session | Nokia | report | Information | Yes |
Yes
| noted | No | ||||
6.5.6 | Study on management aspects of next generation network architecture and features | S5‑171531 | Minutes for Study on management aspects of next generation network architecture and features | Rapporteur(Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑171613 | pCR TR 28.802 Clause 4 - add QMC issue description | Nokia Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑171614 | pCR TR 28.802 Clause 4 - add NR and 5GC architecture issue description | Nokia Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑171938 | |||
S5‑171938 | pCR TR 28.802 Clause 4 - add NR and 5GC architecture issue description | Nokia Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑171614 | |||
S5‑171615 | pCR TR 28.802 Add use cases to support management for data storage architectures | Nokia Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑171939 | |||
S5‑171939 | pCR TR 28.802 Add use cases to support management for data storage architectures | Nokia Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑171984 | S5‑171615 | ||
S5‑171984 | pCR TR 28.802 Add use cases to support management for data storage architectures | Nokia Corporation | pCR | Approval | No |
Yes
| left for email approval | No | S5‑171939 | |||
S5‑171654 | pCR TR 28.802 Adding use case for signaling based QoE information collection | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171935 | |||
S5‑171935 | pCR TR 28.802 Adding use case for signaling based QoE information collection | Huawei,Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑171654 | |||
S5‑171774 | pCR R14 28.802 QoE use cases, requirement and solution for collection from individual UE | Ericsson | pCR | Yes |
Yes
| merged | No | S5‑171935 | ||||
S5‑171775 | pCR R14 28.802 QoE conclusions and recommendations | Ericsson | pCR | Yes |
Yes
| revised | No | S5‑171936 | ||||
S5‑171936 | pCR R14 28.802 QoE conclusions and recommendations | Ericsson | pCR | - | Yes |
Yes
| approved | No | S5‑171775 | |||
S5‑171777 | pCR TR 28.802 Add use case to support management for AMF group | Nokia Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171983 | Draft TS 28.802 | Nokia | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
6.5.7 | Study on Management aspects of selected IoT-related features | S5‑171538 | Minutes of Study on Management aspects of selected IoT-related features | Rapporteur (Cisco) | report | Yes |
Yes
| noted | No | |||
S5‑171589 | pCR to TR 32.857 NRSRP NRSRQ measurements | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑171940 | |||
S5‑171940 | pCR to TR 32.857 NRSRP NRSRQ measurements | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑171589 | |||
S5‑171590 | pCR to TR 32.857 eMTC PM measurements | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑171941 | Draft TR 32.857 | Cisco | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.8 | Study on a RESTful HTTP-based Solution Set | S5‑171539 | Minutes of Study on a RESTful HTTP-based Solution Set | Rapporteur (Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑171622 | pCR 32.866 Clause 6.1 Input on usage of REST APIs in other SDOs | ORANGE | pCR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑171633 | pCR 32.866 Clause 6.1 Input on usage of REST APIs in other SDOs | ORANGE, Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑171942 | |||
S5‑171942 | pCR 32.866 Clause 6.1 Input on usage of REST APIs in other SDOs | ORANGE, Nokia | pCR | Approval | No |
Yes
| left for email approval | No | S5‑171633 | |||
S5‑171752 | pCR 32.866 Add common principles and design patterns | Nokia | pCR | Yes |
Yes
| revised | No | S5‑171943 | ||||
S5‑171943 | pCR 32.866 Add common principles and design patterns | Nokia | pCR | - | Yes |
Yes
| approved | No | S5‑171752 | |||
S5‑171985 | Draft TR 32.866 | Nokia | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.9 | Study on management aspects of virtualized network functions that are part of the NR | S5‑171540 | Minutes of Study on management aspects of virtualized network functions that are part of the NR | Rapporteur (Intel) | report | Yes |
Yes
| noted | No | |||
S5‑171546 | pCR TR 32.864 add IFA13 to the reference, and correct reference accordingly | Intel Corporation (UK) Ltd | pCR | Decision | Yes |
Yes
| approved | No | ||||
S5‑171556 | pCR TR 32.864 Add UC on Update of transport network requirements | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑171945 | |||
S5‑171945 | pCR TR 32.864 Add UC on Update of transport network requirements | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑171987 | S5‑171556 | ||
S5‑171987 | pCR TR 32.864 Add UC on Update of transport network requirements | Intel Corporation (UK) Ltd | pCR | Approval | No |
Yes
| left for email approval | No | S5‑171945 | |||
S5‑171557 | pCR TR 32.864 add UC on NS instantiation containing CN VNF and VNF that is part of a gNB | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑171946 | |||
S5‑171946 | pCR TR 32.864 add UC on NS instantiation containing CN VNF and VNF that is part of a gNB | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑171988 | S5‑171557 | ||
S5‑171988 | pCR TR 32.864 add UC on NS instantiation containing CN VNF and VNF that is part of a gNB | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑171946 | |||
S5‑171558 | pCR TR 32 864 Add UC to establish the relation between CN VNF and RAN VNF | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑171947 | |||
S5‑171947 | pCR TR 32 864 Add UC to establish the relation between CN VNF and RAN VNF | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑171989 | S5‑171558 | ||
S5‑171989 | pCR TR 32 864 Add UC to establish the relation between CN VNF and RAN VNF | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑171947 | |||
S5‑171572 | pCR TR 32 864 Add UC on Adding VNFFGs to a NS containing VNF that is part of a gNB | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171573 | pCR TR 32 864 Add UC on On-boarding NSD that references the VNFD of virtualized part of a gNB | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171574 | pCR TR 32.864 Add potential solutions for instantiating the virtualized part of gNB | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑171948 | |||
S5‑171948 | pCR TR 32.864 Add potential solutions for instantiating the virtualized part of gNB | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑171574 | |||
S5‑171575 | pCR TR 32.864 Add NRM options for gNB | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑171949 | |||
S5‑171949 | pCR TR 32.864 Add NRM options for gNB | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑171575 | |||
S5‑171986 | Draft TR 32.864 | Intel | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.10 | Study on Management Enhancement of CUPS of EPC Nodes | S5‑171541 | Minutes of Study on Management Enhancement of CUPS of EPC Nodes | Rapporteur (Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑171692 | pCR TR 32.867 Add use case and requirements for PDN-GW imitated dedicated bearer creation, deletion and modification related measurement in CUPS | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171950 | |||
S5‑171950 | pCR TR 32.867 Add use case and requirements for PDN-GW imitated dedicated bearer creation, deletion and modification related measurement in CUPS | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171990 | S5‑171692 | ||
S5‑171990 | pCR TR 32.867 Add use case and requirements for PDN-GW imitated dedicated bearer creation, deletion and modification related measurement in CUPS | Huawei | pCR | Approval | No |
Yes
| left for email approval | No | S5‑171950 | |||
S5‑171693 | pCR TR 32.867 Add use case and requirements for active EPS bearers related measurement in CUPS | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑171950 | |||
S5‑171694 | pCR TR 32.867 Add use case and requirements for UE requested bearer resource modification related measurements in CUPS | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑171950 | |||
S5‑171695 | pCR TR 32.867 Add use case and requirements for PDN connections related measurements for EPC in CUPS | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑171950 | |||
S5‑171991 | Draft TR 32.867 | Huawei | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑171508 | CH Agenda and Time Plan | CH SWG Chair | agenda | Yes |
Yes
| approved | No | |||
S5‑171509 | CH Executive Report from THIS Meeting | CH SWG Chair | report | Yes |
Yes
| noted | No | |||||
S5‑171706 | [Draft]LSOut to SA2 for TDF support of Presence Reporting Area | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑171783 | |||
S5‑171707 | LSOut to CT1 for support of ProSe Direct one-to-one Communication charging | Huawei | LS out | Agreement | Yes |
Yes
| revised | No | S5‑171784 | |||
S5‑171732 | LS from CT4 to SA5 on Online and Offline Charging support with Control and User Plane Separation | C4-171455 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑171781 | Reply to: LS from CT4 to SA5 on Online and Offline Charging support with Control and User Plane Separation | Nokia | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑171743 | Reply LS from SA2 to SA5 on charging support for V2X Communication | S2-171349 | LS in | Yes |
Yes
| noted | No | |||||
S5‑171749 | Resubmitted LS from SA2 to SA5-CH on implication on charging from eFMSS | S2-164279 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑171782 | Reply to LS from SA2 to SA5-CH on implication on charging from eFMSS | China Telecom | LS out | Approval | Yes |
Yes
| revised | No | S5‑172002 | |||
S5‑172002 | Reply to LS from SA2 to SA5-CH on implication on charging from eFMSS | China Telecom | LS out | Approval | No |
Yes
| left for email approval | No | S5‑171782 | |||
S5‑171862 | New WID study on charging in CUPS architecture | Ericsson | WID new | Agreement | Yes |
Yes
| noted | No | ||||
7.2 | New Charging Work Item proposals | S5‑171609 | New Work Item on Charging Enhancement for eFMSS | China Telecom | WID new | Approval | Yes |
Yes
| revised | No | S5‑171795 | |
S5‑171795 | New Work Item on Charging Enhancement for eFMSS | China Telecom | WID new | Approval | Yes |
Yes
| revised | No | S5‑171893 | S5‑171609 | ||
S5‑171895 | New Work Item on Charging Enhancement for eFMSS | China Telecom | WID new | Approval | No |
No
| withdrawn | Yes | ||||
S5‑171627 | Discussion Paper on NAPS Charging | Huawei Technologies | discussion | Information | Yes |
Yes
| noted | No | ||||
7.3 | Charging Maintenance and Rel-15 small Enhancements | S5‑171607 | Rel-14 CR 32.298 Correction in ASN1 syntax | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑171807 | |
S5‑171807 | Rel-14 CR 32.298 Correction in ASN1 syntax | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑171894 | S5‑171607 | ||
S5‑171894 | Rel-14 CR 32.298 Correction in ASN1 syntax | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | No |
Yes
| left for email approval | No | S5‑171807 | |||
S5‑171717 | Rel-14 CR TS 32.240 Correction of TF abbreviation | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑171718 | Rel-14 CR TS 32.260 Correction of TRF description | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑171808 | |||
S5‑171808 | Rel-14 CR TS 32.260 Correction of TRF description | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑171718 | |||
S5‑171719 | Rel-14 CR TS 32.299 Correction of IMEI and IMEISV handling | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑171809 | |||
S5‑171809 | Rel-14 CR TS 32.299 Correction of IMEI and IMEISV handling | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑171719 | |||
S5‑171720 | Rel-14 CR TS 32.298 Correction of IMEI and IMEISV handling | Ericsson LM | CR | Approval | Yes |
Yes
| noted | No | ||||
S5‑171721 | Rel-14 CR TS 32.276 Correction of ISUP Cause not shown as grouped | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑171722 | Rel-14 CR TS32.299 Correction of ISUP Cause naming | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑171849 | |||
S5‑171849 | Rel-12 CR TS32.299 Correction of ISUP Cause naming | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑171722 | |||
S5‑171783 | LS on TDF support of Presence Reporting Area | Huawei | LS out | Approval | Yes |
Yes
| approved | No | S5‑171706 | |||
S5‑171784 | LSOut to CT1 for support of ProSe Direct one-to-one Communication charging | Huawei | LS out | Approval | Yes |
Yes
| approved | No | S5‑171707 | |||
S5‑171810 | Rel-14 CR TS 32.251 Correction of IMEI and IMEISV handling | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑171848 | Rel-14 CR TS 32.260 Correction of IMEI and IMEISV handling | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑171850 | Rel-13 CR TS32.299 Correction of ISUP Cause naming | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑171851 | Rel-14 CR TS32.299 Correction of ISUP Cause naming | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑171893 | New Work Item on Charging Enhancement for eFMSS | China Telecom | WID new | Agreement | No |
Yes
| left for email approval | No | S5‑171795 | |||
7.4 | Rel-14 Charging |   | ||||||||||
7.4.1 | Resource optimization for PS domain online charging sessions | S5‑171723 | Rel-14 CR TS 32.299 Adding Unused Quota timer to CCA | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑171785 | |
S5‑171785 | Rel-14 CR TS 32.299 Adding Unused Quota timer to CCA | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑171723 | |||
S5‑171786 | Rel-14 CR TS 32.251 Adding Unused Quota timer to CCA | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑171789 | R14 CR 32.277 Charging information for ProSe Direct Communication charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
7.4.2 | Determination of Completeness of Charging Information in IMS |   | ||||||||||
7.4.3 | Charging Aspects of Enhanced Proximity-based Services | S5‑171701 | R14 CR 32.299 Correction on the description of AVPs | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑171787 | |
S5‑171787 | R14 CR 32.299 Correction on the description of AVPs | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑171701 | |||
S5‑171702 | R14 CR 32.277 Addition of the triggers and description for ProSe Direct Communication charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑171788 | |||
S5‑171788 | R14 CR 32.277 Addition of the triggers and description for ProSe Direct Communication charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑171702 | |||
S5‑171703 | R14 CR 32.277 Addition of the fields for ProSe one-to-one communication charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑171790 | |||
S5‑171790 | R14 CR 32.277 Addition of the fields for ProSe one-to-one communication charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑171703 | |||
S5‑171704 | R14 CR 32.298 Addition of the fileds for ProSe one-to-one communication Charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑171791 | |||
S5‑171791 | R14 CR 32.298 Addition of the fileds for ProSe one-to-one communication Charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑171896 | S5‑171704 | ||
S5‑171896 | R14 CR 32.298 Addition of the fileds for ProSe one-to-one communication Charging | Huawei | CR | Agreement | No |
Yes
| left for email approval | No | S5‑171791 | |||
7.4.4 | Charging Aspects of S8 Home Routing Architecture for VoLTE | S5‑171623 | Rel-14 CR 32.260 Implement IMS visited network identifier for S8HR | China Mobile US Research Cente | CR | Yes |
Yes
| revised | No | S5‑171792 | ||
S5‑171792 | Rel-14 CR 32.260 Implement IMS visited network identifier for S8HR | China Mobile US Research Cente | CR | - | Yes |
Yes
| agreed | No | S5‑171623 | |||
S5‑171625 | Rel-14 CR 32.298 Implement IMS visited network identifier for S8HR | China Mobile US Research Cente | CR | Yes |
Yes
| revised | No | S5‑171793 | ||||
S5‑171793 | Rel-14 CR 32.298 Implement IMS visited network identifier for S8HR | China Mobile US Research Cente | CR | - | Yes |
Yes
| agreed | No | S5‑171625 | |||
S5‑171626 | Rel-14 CR 32.299 Implement IMS visited network identifier for S8HR | China Mobile US Research Cente | CR | Yes |
Yes
| revised | No | S5‑171794 | ||||
S5‑171794 | Rel-14 CR 32.299 Implement IMS visited network identifier for S8HR | China Mobile US Research Cente | CR | - | Yes |
Yes
| agreed | No | S5‑171626 | |||
7.4.5 | Charging Aspects of Improvements of Awareness of User Location Change (AULC) | S5‑171628 | Discussion on the Analysis of the Charging Support for AULC | Huawei Technologies | discussion | Information | Yes |
Yes
| noted | No | ||
S5‑171630 | R14 CR 32.251 Addition of the subcription operation for AULC | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑171796 | |||
S5‑171796 | R14 CR 32.251 Addition of the subcription operation for AULC | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑171630 | |||
S5‑171798 | LS to SA2 on Support of PRA for OCS | Huawei | LS out | Approval | Yes |
Yes
| approved | No | ||||
7.4.6 | Charging aspects for Diameter Base Protocol Specification Update |   | ||||||||||
7.4.7 | Charging Aspect of 3GPP PS Data off Function | S5‑171601 | Rel-14 CR 32.260 Introduction of 3GPP Data Off status indication in AS charging | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑171804 | |
S5‑171804 | Rel-14 CR 32.260 Introduction of 3GPP Data Off status indication in AS charging | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑171601 | |||
S5‑171602 | Rel-14 CR 32.298 Introduction of 3GPP Data Off status indication in AS charging | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑171805 | |||
S5‑171805 | Rel-14 CR 32.298 Introduction of 3GPP Data Off status indication in AS charging | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑171897 | S5‑171602 | ||
S5‑171897 | Rel-14 CR 32.298 Introduction of 3GPP Data Off status indication in AS charging | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | No |
Yes
| left for email approval | No | S5‑171805 | |||
S5‑171631 | Discussion on the Charging consideration for 3GPP PS Data Off in Roaming Cases | Huawei | discussion | Yes |
Yes
| noted | No | |||||
S5‑171632 | R14 CR 32.251 Charging enhancement for 3GPP PS Data off in roaming cases | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑171806 | |||
S5‑171806 | R14 CR 32.251 Additional charging trigger for 3GPP PS Data off | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑171632 | |||
7.4.8 | Charging for SMS via T4 | S5‑171603 | Rel-14 CR 32.274 Improve Message flows offline charging for SMS delivery | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑171799 | |
S5‑171799 | Rel-14 CR 32.274 Improve Message flows offline charging for SMS delivery | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑171603 | |||
S5‑171604 | Rel-14 CR 32.274 Introduce additional Message flows offline charging for Device Triggering | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑171800 | |||
S5‑171800 | Rel-14 CR 32.274 Introduce additional Message flows offline charging for Device Triggering | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑171604 | |||
S5‑171605 | Rel-14 CR 32.274 Introduce Message flows online charging for Device Triggering | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑171801 | |||
S5‑171801 | Rel-14 CR 32.274 Introduce Message flows online charging for Device Triggering | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑171605 | |||
S5‑171606 | Rel-14 CR 32.274 Introduce Message flows online charging for MSISDN-less MO-SMS via T4 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑171802 | |||
S5‑171802 | Rel-14 CR 32.274 Introduce Message flows online charging for MSISDN-less MO-SMS via T4 | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑171606 | |||
S5‑171773 | Rel-14 CR 32.274 Introduce new CDR for Device Triggering | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑171803 | |||
S5‑171803 | Rel-14 CR 32.274 Introduce new CDR for Device Triggering | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑171773 | |||
7.5 | Charging Studies |   | ||||||||||
7.5.1 | Study on Overload Control for Diameter Charging Applications | S5‑171714 | pCR 32.869 Update of Scope and References | Ericsson LM | pCR | Agreement | Yes |
Yes
| revised | No | S5‑171852 | |
S5‑171852 | pCR 32.869 Update of Scope and References | Ericsson LM | pCR | Agreement | Yes |
Yes
| approved | No | S5‑171714 | |||
S5‑171715 | pCR 32.869 Update of Definitions, symbols and abbreviations | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑171853 | |||
S5‑171853 | pCR 32.869 Update of Definitions, symbols and abbreviations | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑171715 | |||
S5‑171716 | pCR 32.869 Update of Introduction | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑171854 | |||
S5‑171854 | pCR 32.869 Update of Introduction | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑171716 | |||
S5‑171855 | Draft TR 32.869 | Ericsson | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
S5‑171856 | SID on Overload Control for Diameter Charging Applications | Ericsson | SID revised | Agreement | Yes |
Yes
| agreed | No | ||||
7.5.2 | Study on forward compatibility for 3GPP Diameter Charging Applications |   | ||||||||||
7.5.3 | Study on Charging Aspects of 5G System Architecture Phase 1 | S5‑171653 | R15 DraftTR 32.899 Skeleton of Study on Charging Aspects of 5G System Architecture Phase 1 | Huawei | draft TR | Approval | Yes |
Yes
| revised | No | S5‑171857 | |
S5‑171857 | R15 DraftTR 32.899 Skeleton of Study on Charging Aspects of 5G System Architecture Phase 1 | Huawei | draft TR | Approval | Yes |
Yes
| approved | No | S5‑171653 | |||
S5‑171699 | R15 pCR 32.899 Study on Charging Aspects of 5G System-References | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171858 | |||
S5‑171858 | R15 pCR 32.899 Study on Charging Aspects of 5G System-References | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑171699 | |||
S5‑171700 | R15 pCR 32.899 Study on Charging Aspects of 5G System-Scope | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑171859 | |||
S5‑171859 | R15 pCR 32.899 Study on Charging Aspects of 5G System-Scope | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑171700 | |||
S5‑171705 | Rel-15 pCR 32.899 TR skeleton update | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑171861 | |||
S5‑171861 | Rel-15 pCR 32.899 TR skeleton update | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑171705 | |||
S5‑171724 | Key issues for Charging Aspects of 5G System Architecture Phase 1 | Ericsson LM | other | Discussion | Yes |
Yes
| noted | No | ||||
S5‑171744 | LS from SA3-LI to SA5 on Use of the long-term identities for Charging in the VPLMN for 5G | S3i170043 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑171768 | Rel-15 pCR 32.899 TR skeleton update | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑171769 | Rel-15 pCR 32.899 Scope | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| merged | No | S5‑171859 | |||
S5‑171770 | Rel-15 pCR 32.899 High level charging requirements | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑171888 | |||
S5‑171888 | Rel-15 pCR 32.899 High level charging requirements | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑171770 | |||
S5‑171771 | Rel-15 pCR 32.899 Session management - PDU session | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑171889 | |||
S5‑171889 | Rel-15 pCR 32.899 Session management - PDU session | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑171771 | |||
S5‑171860 | Work Plan for Study TR 32.899 | Nokia | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑171891 | |||
S5‑171891 | Work Plan for Study TR 32.899 | Nokia | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑171860 | |||
S5‑171890 | Reply LS to LS from SA3-LI to SA5 on Use of the long-term identities for Charging in the VPLMN for 5G | Ericsson | LS out | Approval | Yes |
Yes
| approved | No | ||||
S5‑171892 | Draft TR 32.899 | Huawei | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
8 | Any Other Business | S5‑171772 | Discussion paper on process for CRs to TS 32.298 for ASN.1 validation | Nokia, Alcatel-Lucent Shanghai Bell | discussion | Approval | Yes |
Yes
| noted | No | ||
9 | Closing of the meeting |   |