Tdoc List
2017-10-20 15:17
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‑175000 | Agenda | WG Chairman | agenda | Yes |
Yes
| approved | No | |||
3 | IPR declaration | S5‑175023 | IPR and legal declaration | WG Chairman | other | Yes |
Yes
| noted | No | |||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑175001 | Report from last SA5 meeting | MCC | report | Yes |
Yes
| approved | No | |||
4.2 | Last SA meeting report | S5‑175002 | SA5 status report at last SA meeting | WG Chairman | report | Yes |
Yes
| noted | No | |||
S5‑175003 | 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‑175006 | Leaders meeting agenda | WG Chairman | agenda | Yes |
Yes
| noted | No | |||
S5‑175007 | Leaders meeting minutes | WG Chairman | report | Yes |
Yes
| noted | No | |||||
S5‑175011 | SA5 Working Procedures | WG Vice Chair (Huawei) | other | Yes |
Yes
| approved | No | |||||
S5‑175012 | SA5 Meeting Facility Requirements | WG Vice Chair (Orange) | other | Yes |
Yes
| approved | No | |||||
S5‑175013 | Process for management of draft TSs/TRs | WG Chairman | other | Yes |
Yes
| approved | No | |||||
S5‑175014 | CR Quality Check | MCC | other | Yes |
Yes
| noted | No | |||||
S5‑175024 | Status of email approvals | WG Vice Chair (Orange) | other | No |
No
| reserved | No | |||||
S5‑175290 | TS quality campaign table themes and status | Ericsson LM | other | Action | Yes |
Yes
| noted | No | ||||
S5‑175325 | Additional meeting time considerations | WG Chair | other | discussion | Yes |
YesThe Chair commented that his preference was to have more ad-hoc meetings.
Nokia disagreed with extending the meeting to Saturdays. A whole weekend would be lost just for a small extra time.Working during weekends would be impossible for some companies/individuals due to religious or legal reasons.
Nokia advised to plan as early as possible the ad-hocs or extensions so companies can prepare accordingly.
The Chair clarified that these were options proposed by companies and not offered by the Chair alone.
Ericsson pointed out about the PCG#39 meeting where it was advised not to increase the number of hours of work more than reasonable.Showing the number of meetings of other groups was not helping.
MCC commented that using the weekends should also be out of the question, since there could be legal issues behind, although they could be used for offline discussions.
NTT-Docomo was against extending the work for the next week and proposed to work more efficiently with the prioritization of WIDs. Nokia supported this.
Nokia was in favour of not extending the meetings more than 6 per year. They also insisted on improving the means of advertising SA5's work.
ORANGE preferred to have conference calls with decision power for certain topics that had less supporting companies like RESTful or Energy Efficiency.
Christian (Huawei) commented that there would be a call on November the 8th for a time management proposal. All options are in the time management document and there is no decision. This document had been submitted to SA5#114 and there were no comments.Christian proposed to resubmit the document to the current meeting (tdoc 357) and gather comments offline during the week.
| revised | No | S5‑175358 | |||
S5‑175358 | Additional meeting time considerations | WG Chair | other | discussion | Yes |
Yes
| noted | No | S5‑175325 | |||
S5‑175357 | Time management proposals | Huawei | other | discussion | Yes |
Yes
| noted | No | ||||
5.2 | Technical issues at SA5 level |   | ||||||||||
5.3 | Liaison statements at SA5 level | S5‑175041 | Liaison Statement from ETSI NTECH to 3GPP SA5 and SA2 on GANA instantiation in the Core and Backhaul network parts of the 3GPP Architecture | ETSI TC NTECH AFI | LS in | Yes |
Yes
| postponed | No | |||
S5‑175042 | Reply LS from CT1 cc SA5 on Supported features by 5GC for E-UTRA connected to 5G CN | C1-173571 | LS in | Yes |
Yes
| noted | No | |||||
S5‑175051 | Resubmitted LS from RAN2 to SA5 on supported features by 5GC for E-UTRA connected to 5G CN | R2-1706153 | LS in | Yes |
YesMaryse (Nokia) commented that Charging had a study covering the charging aspects of the SA2 work, but there was also some OAM aspects that should be covered by SA5.
| replied to | No | |||||
S5‑175356 | Reply to: Resubmitted LS from RAN2 to SA5 on supported features by 5GC for E-UTRA connected to 5G CN | Nokia | LS out | approval | Yes |
Yes
| revised | No | S5‑175495 | |||
S5‑175495 | Reply to: Resubmitted LS from RAN2 to SA5 on supported features by 5GC for E-UTRA connected to 5G CN | Nokia | LS out | approval | Yes |
Yes
| approved | No | S5‑175356 | |||
S5‑175047 | LS from TSG CT cc SA5 on Evolution of IMSI format and E.212 Recommendation | CP-172153 | LS in | Yes |
YesNokia commented that this had been discussed in the Charging SWG. It wasn't clear what they had to do with this LS.
It was suggested to note the LS given that CT4 will take initiative and ask SA5 for their comments once they have some input.
| noted | No | |||||
S5‑175050 | Resubmitted LS from GSMA cc SA5 on Network Slicing initiative | GSMA | LS in | Yes |
YesBT commented that the SA5 Chair had the action point to talk with the SA chair about this LS. There had been an email exchange with him. The SA Chair encouraged SA5 to go for this work without any SA coordination.
The SA5 Chair commented that he needed to talk about it further with the SA Chair.
| replied to | No | |||||
S5‑175406 | Reply to: Resubmitted LS from GSMA cc SA5 on Network Slicing initiative | Ericsson | LS out | approval | Yes |
Yes
| revised | No | S5‑175493 | |||
S5‑175493 | Reply to: Resubmitted LS from GSMA cc SA5 on Network Slicing initiative | Ericsson | LS out | approval | No |
Yes
| left for email approval | No | S5‑175406 | |||
S5‑175056 | Resubmitted LS from MEF Forum to SA5 on MEF Forum Work on 5G | MEF Forum | LS in | Yes |
YesOn bullet point 3, Nokia commented that the work of SA5 in 5G was not properly advertised.
Thomas replied that he had written an article on the 3GPP website on SA5's work, and he was planning to write another one. He clarified that the marketing work of SA5 should be coordinated by the 3GPP marketing, although LS could be used to communicate SA5's work.
Nokia commented that ocasional articles were not enough.
The Chair proposed to write an LS to inform MEF about the network slicing work.
| replied to | No | |||||
S5‑175407 | Reply to: Resubmitted LS from MEF Forum to SA5 on MEF Forum Work on 5G | Ericsson | LS out | approval | Yes |
Yes
| noted | No | ||||
S5‑175351 | LS to SA5 on NGMN Paper on 5G End-to-End Architecture Framework | NGMN | LS in | Information | Yes |
Yes
| replied to | No | ||||
S5‑175408 | Reply to: LS to SA5 on NGMN Paper on 5G End-to-End Architecture Framework | Ericsson | LS out | approval | Yes |
Yes
| revised | No | S5‑175494 | |||
S5‑175494 | Reply to: LS to SA5 on NGMN Paper on 5G End-to-End Architecture Framework | Ericsson | LS out | approval | No |
Yes
| left for email approval | No | S5‑175408 | |||
5.4 | SA5 meeting calendar | S5‑175010 | SA5 Meeting Calendar | WG Chairman | other | Yes |
Yes
| revised | No | S5‑175427 | ||
S5‑175427 | SA5 Meeting Calendar | WG Chairman | other | - | No |
Yes
| noted | No | S5‑175010 | |||
5.5 | Review of the Work Plan | S5‑175015 | Deliverables due for the NEXT SA Plenary | MCC | other | Yes |
Yes
| noted | No | |||
S5‑175016 | Ongoing SA5 WIDs and SIDs | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||||
S5‑175017 | SA5 3GPP Work Plan | MCC | other | Yes |
Yes
| noted | No | |||||
S5‑175026 | Work Plan status | WG Chair | other | No |
No
| reserved | No | |||||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑175004 | Time Plan for OAM&P | WG Vice Chair (Huawei) | other | Yes |
Yes
| revised | No | S5‑175349 | ||
S5‑175349 | Time Plan for OAM&P | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| noted | No | S5‑175004 | |||
S5‑175005 | OAM Executive Report | WG Vice Chair (Huawei) | report | Yes |
Yes
| revised | No | S5‑175491 | ||||
S5‑175491 | OAM Executive Report | WG Vice Chair (Huawei) | report | - | No |
No
| reserved | No | S5‑175005 | |||
S5‑175025 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | Yes |
Yes
| revised | No | S5‑175490 | ||||
S5‑175490 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | - | No |
Yes
| left for email approval | No | S5‑175025 | |||
S5‑175027 | Minutes of OAM&P SWG opening session | WG Vice Chair (Huawei) | report | Yes |
Yes
| noted | No | |||||
S5‑175040 | LS from NGMN cc SA5 on requirement of lifecycle management for 3GPP service based architecture | NGMN | LS in | Yes |
Yes
| noted | No | |||||
S5‑175048 | LS from RAN3 to SA5 on support of Trace and MDT in NG-RAN in rel-15 | R3-173422 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑175049 | Reply Lsfrom SA2 to SA5 on progress of Network Slicing related work | S2-176505 | LS in | Yes |
Yes
| noted | No | |||||
S5‑175052 | Resubmitted LS from SA2 to SA5 on EUTRAN sharing enhancement | S2-173701 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑175324 | LSOut reply from ETSI NFV cc SA5 on lifecycle management for 3GPP service based architecture | ETSI ISG NFV | LS in | approval | Yes |
Yes
| postponed | No | ||||
S5‑175461 | Reply to: Resubmitted LS from SA2 to SA5 on EUTRAN sharing enhancement | Ericsson | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑175054 | Resubmitted LS from RAN3 to SA5 on Collection Period correction for MDT M3 measurement in eUTRAN | R3-171382 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑175057 | LSOut reply to 3GPP SA5 on progress of measurement definitions | ETSI ISG NFV | LS in | Yes |
Yes
| noted | No | |||||
S5‑175058 | LSOut reply to 3GPP SA5 on Managing EM IP address provided to VNF | ETSI ISG NFV | LS in | Yes |
Yes
| noted | No | |||||
S5‑175293 | Reply LS from RAN2 cc SA5 to RAN3 on MDT | R2-1712041 | LS in | discussion | Yes |
Yes
| noted | No | ||||
S5‑175348 | LSOut reply to NGMN cc SA5 on lifecycle management for 3GPP service based architecture | ETSI ISG NFV | LS in | discussion | Yes |
Yes
| withdrawn | Yes | ||||
S5‑175459 | Structure of 5G specifications | WG Vice Chair (Huawei) | discussion | Endorsement | Yes |
Yes
| endorsed | No | ||||
6.2 | New OAM&P Work Item proposals | S5‑175018 | Minutes of New Work Item proposals - OAM&P | WG Vice Chair (Orange) | report | Yes |
Yes
| noted | No | |||
S5‑175090 | Organization of future 5G WIDs | WG Vice Chair (Huawei) | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑175462 | |||
S5‑175462 | Organization of future 5G WIDs | WG Vice Chair (Huawei) | discussion | Endorsement | No |
Yes
| left for email approval | No | S5‑175090 | |||
S5‑175150 | New WID on Management of NG-RAN that includes virtualized network functions | Intel | WID new | Approval | Yes |
Yes
| revised | No | S5‑175327 | |||
S5‑175327 | New WID on Management of NG-RAN that includes virtualized network functions | Intel | WID new | Agreement | Yes |
Yes
| revised | No | S5‑175463 | S5‑175150 | ||
S5‑175463 | New WID on Management of NG-RAN that includes virtualized network functions | Intel | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑175327 | |||
S5‑175162 | New WID on Performance assurance of network slicing for 5G networks and services | Intel Corporation, CMCC | WID new | Agreement | Yes |
Yes
| merged | No | S5‑175326 | |||
S5‑175181 | New WID on Fault management of network slicing for 5G networks | ZTE Corporation | WID new | Approval | Yes |
Yes
| revised | No | S5‑175328 | |||
S5‑175328 | New WID on Fault management of network slicing for 5G networks | ZTE Corporation | WID new | Agreement | Yes |
Yes
| revised | No | S5‑175466 | S5‑175181 | ||
S5‑175466 | New WID on Fault management of network slicing for 5G networks | ZTE Corporation | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑175328 | |||
S5‑175190 | New WID on management data definitions for 5G network functions | Nokia Shanghai Bell | WID new | Approval | Yes |
Yes
| revised | No | S5‑175329 | |||
S5‑175329 | New WID on management data definitions for 5G network functions | Nokia Shanghai Bell | WID new | Agreement | Yes |
Yes
| revised | No | S5‑175464 | S5‑175190 | ||
S5‑175464 | New WID on management data definitions for 5G network functions | Nokia Shanghai Bell | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑175329 | |||
S5‑175218 | New WID on Performance Assurance for Network Slicing | CCSA | WID new | Yes |
Yes
| withdrawn | Yes | |||||
S5‑175247 | New Study Item on integration of ONAP DCAE and 3GPP management architecture | AT&T, ORANGE | SID new | Approval | Yes |
Yes
| revised | No | S5‑175331 | |||
S5‑175331 | New Study Item on integration of ONAP DCAE and 3GPP management architecture | AT&T, ORANGE | SID new | Approval | Yes |
Yes
| agreed | No | S5‑175247 | |||
S5‑175269 | New WID on Performance Assurance for Network Slicing | China Mobile | WID new | Approval | Yes |
Yes
| revised | No | S5‑175326 | |||
S5‑175326 | New WID on Performance Assurance for Network Slicing | China Mobile,Intel | WID new | Agreement | Yes |
Yes
| revised | No | S5‑175465 | S5‑175269 | ||
S5‑175465 | New WID on Performance Assurance for Network Slicing | China Mobile,Intel | WID new | Agreement | Yes |
Yes
| revised | No | S5‑175487 | S5‑175326 | ||
S5‑175487 | New WID on Performance Assurance for Network Slicing | China Mobile,Intel | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑175465 | |||
S5‑175270 | New WID on Network Slicing Management Architecture | China Mobile | WID new | Agreement | Yes |
Yes
| noted | No | ||||
S5‑175330 | New WID on Network Slicing Management Architecture | China Mobile | WID new | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑175289 | Minutes conference call on 5G WID organization | OAM&P SWG chairman | report | Information | Yes |
Yes
| noted | No | ||||
6.3 | OAM&P Maintenance and Rel-15 small Enhancements | S5‑175019 | Minutes of OAM&P Maintenance and Rel-15 small Enhancements | MCC | report | Yes |
Yes
| noted | No | |||
S5‑175059 | CR TS 32.450 Uplink E-UTRAN IP Latency KPI Definition | TELECOM ITALIA S.p.A. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑175333 | CR TS 32.450 Uplink E-UTRAN IP Latency KPI Definition | TELECOM ITALIA S.p.A. | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑175060 | CR TS 32.425 E-UTRAN Latency measurement and drop rate in Uplink | TELECOM ITALIA S.p.A. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑175334 | CR TS 32.425 E-UTRAN Latency measurement and drop rate in Uplink | TELECOM ITALIA S.p.A. | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑175061 | CR TS 32.455 Roud Trip Time KPI on S1-U Definition | TELECOM ITALIA S.p.A. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑175335 | CR TS 32.455 Roud Trip Time KPI on S1-U Definition | TELECOM ITALIA S.p.A. | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑175062 | CR TS 32.426 Latency measurement on S1-U | TELECOM ITALIA S.p.A. | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑175336 | CR TS 32.426 Latency measurement on S1-U | TELECOM ITALIA S.p.A. | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑175141 | Rel-14 CR 28622 Missing note in table of Attribute Properties | MCC | CR | Yes |
Yes
| agreed | No | |||||
S5‑175155 | Rel-11 CR 32.422 Collection Period correction for MDT M3 measurement in eUTRAN | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑175337 | Rel-11 CR 32.422 Collection Period correction for MDT M3 measurement in eUTRAN | Ericsson | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑175156 | Rel-12 CR 32.422 Collection Period correction for MDT M3 measurement in eUTRAN | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑175157 | Rel-13 CR 32.422 Collection Period correction for MDT M3 measurement in eUTRAN | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑175158 | Rel-14 CR 32.422 Collection Period correction for MDT M3 measurement in eUTRAN | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑175159 | Rel-15 CR 32.422 Collection Period correction for MDT M3 measurement in eUTRAN | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑175209 | R14 CR 32.130-14.0.0 Correcting requirement tags | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑175219 | Rel-15 CR 28.801 Implement Edithelp and MCC comments | Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑175338 | |||
S5‑175338 | Rel-15 CR 28.801 Implement Edithelp and MCC comments | Ericsson Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑175219 | |||
S5‑175248 | Rel-14 CR 28.632 Remove unused reference | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑175339 | |||
S5‑175339 | Rel-14 CR 28.632 Remove unused reference | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑175248 | |||
S5‑175249 | Rel-14 CR 32.103 Update erroneous references | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑175352 | |||
S5‑175352 | Rel-14 CR 32.103 Update erroneous references | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑175249 | |||
S5‑175250 | Rel-14 CR 32.150 Update erroneous references | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑175340 | |||
S5‑175340 | Rel-14 CR 32.150 Update erroneous references | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑175250 | |||
S5‑175251 | Rel-14 CR 32.153 Update erroneous references | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑175252 | Rel-14 CR 32.155 Update erroneous references | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑175253 | Rel-14 CR 32.182 Update erroneous references | Ericsson LM | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑175254 | Rel-12 CR 28.732 Update erroneous references | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑175341 | |||
S5‑175341 | Rel-12 CR 28.732 Update erroneous references | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑175254 | |||
S5‑175255 | Rel-13 CR 28.732 Update erroneous references | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑175342 | |||
S5‑175342 | Rel-13 CR 28.732 Update erroneous references | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑175255 | |||
S5‑175256 | Rel-14 CR 28.732 Update erroneous references | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑175343 | |||
S5‑175343 | Rel-14 CR 28.732 Update erroneous references | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑175256 | |||
6.4 | Rel-15 Operations, Administration, Maintenance and Provisioning (OAM&P) |   | ||||||||||
6.4.1 | Control and monitoring of Power, Energy and Environmental (PEE) parameters in Radio Access Networks (RAN) | S5‑175034 | Minutes of Control and monitoring of Power, Energy and Environmental (PEE) parameters in Radio Access Networks (RAN) | Rapporteur (ORANGE) | report | Yes |
Yes
| noted | No | |||
S5‑175075 | pCR TS 28.304 Update on Architecture and Clause 6 actor roles, telecom resources and use cases | ORANGE | pCR | Approval | Yes |
Yes
| revised | No | S5‑175359 | |||
S5‑175359 | pCR TS 28.304 Update on Architecture and Clause 6 actor roles, telecom resources and use cases | ORANGE | pCR | Approval | Yes |
Yes
| approved | No | S5‑175075 | |||
S5‑175076 | pCR TS 28.305 Information Model for solution 1 | ORANGE | pCR | Approval | Yes |
Yes
| revised | No | S5‑175360 | |||
S5‑175360 | pCR TS 28.305 Information Model for solution 1 | ORANGE | pCR | Approval | Yes |
Yes
| approved | No | S5‑175076 | |||
S5‑175135 | Draft CR 28.622 Add PEE attribute to IOC ManagedFunction | ORANGE | draftCR | Discussion | Yes |
Yes
| revised | No | S5‑175361 | |||
S5‑175361 | Draft CR 28.622 Add PEE attribute to IOC ManagedFunction | ORANGE | draftCR | Approval | Yes |
Yes
| approved | No | S5‑175135 | |||
S5‑175136 | Draft CR 28.623 Add attribute to IOC ManagedFunction - SS | ORANGE | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175137 | Draft CR 32.425 Add PEE measurements for E-UTRAN | ORANGE | draftCR | Approval | Yes |
Yes
| revised | No | S5‑175362 | |||
S5‑175362 | Draft CR 32.425 Add PEE measurements for E-UTRAN | ORANGE | draftCR | Approval | Yes |
Yes
| approved | No | S5‑175137 | |||
S5‑175138 | pCR TS 28.305 Information Model for solution 2 | ORANGE | pCR | Approval | Yes |
Yes
| revised | No | S5‑175363 | |||
S5‑175363 | pCR TS 28.305 Information Model for solution 2 | ORANGE | pCR | Approval | Yes |
Yes
| approved | No | S5‑175138 | |||
S5‑175468 | Draft TS 28.304 | ORANGE | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑175469 | Draft TS 28.305 | ORANGE | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
6.4.2 | Management of QoE measurement collection | S5‑175035 | Minutes of Management of QoE measurement collection | Rapporteur (Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑175091 | pCR 28.404 Add use case and requirement for QoE collection | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175382 | |||
S5‑175382 | pCR 28.404 Add use case and requirement for QoE collection | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑175091 | |||
S5‑175160 | Rel-15 pCR 28.308 References and System Overview for QoE IRP Information Service | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175161 | Rel-15 pCR 28.308 Information Object Classes and Interface Definition for QoE IRP | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑175402 | |||
S5‑175402 | Rel-15 pCR 28.308 Information Object Classes and Interface Definition for QoE IRP | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑175161 | |||
S5‑175188 | pCR to the TS 28.404 Use case 5.4.1 clarification | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175194 | Skeleton 28.307 | Ericsson | draft TS | Yes |
Yes
| approved | No | |||||
S5‑175195 | Skeleton 28.308 | Ericsson | draft TS | Yes |
Yes
| approved | No | |||||
S5‑175196 | Skeleton 28.405 | Ericsson | draft TS | Yes |
Yes
| approved | No | |||||
S5‑175197 | Skeleton 28.406 | Ericsson | draft TS | Yes |
Yes
| approved | No | |||||
S5‑175198 | R15 pCR 28.307-000 Introduction and scope for QoE IRP requirements | Ericsson | pCR | Yes |
Yes
| revised | No | S5‑175398 | ||||
S5‑175398 | R15 pCR 28.307-000 Introduction and scope for QoE IRP requirements | Ericsson | pCR | - | Yes |
Yes
| approved | No | S5‑175198 | |||
S5‑175200 | R15 pCR 28.307-000 Introduction of specification level use cases and requirements for QoE IRP requirements | Ericsson | pCR | Yes |
Yes
| revised | No | S5‑175399 | ||||
S5‑175399 | R15 pCR 28.307-000 Introduction of specification level use cases and requirements for QoE IRP requirements | Ericsson | pCR | - | Yes |
Yes
| approved | No | S5‑175200 | |||
S5‑175201 | R15 pCR 28.308-000 Introduction and scope for QoE IRP Inormation Service | Ericsson | pCR | Yes |
Yes
| revised | No | S5‑175400 | ||||
S5‑175400 | R15 pCR 28.308-000 Introduction and scope for QoE IRP Inormation Service | Ericsson | pCR | - | Yes |
Yes
| approved | No | S5‑175201 | |||
S5‑175291 | LS from SA4 to SA5 on adding new service type in QMC reporting | S4-170952 | LS in | discussion | Yes |
Yes
| noted | No | ||||
S5‑175292 | LS from RAN2 to SA5 on RAN2 progress of QoE Measurement Collection in LTE | R2-1712035 | LS in | discussion | Yes |
Yes
| noted | No | ||||
S5‑175401 | Draft TS 28.308 | Ericsson | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑175470 | Draft TS 28.307 | Ericsson | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
6.4.3 | Management of Network Slicing in Mobile Networks, Concepts, Use cases and Requirements | S5‑175036 | Minutes of Management of Network Slicing in Mobile Networks, Concepts, Use cases and Requirements | Rapporteur (Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑175092 | pCR 28.530 Add concept and use case of V2X services using network slicing | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑175377 | |||
S5‑175378 | pCR 28.530 Add concept and use case of V2X services using network slicing | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑175093 | pCR 28.530 Adding concept and use case of network slicing with fixed mobile convergence | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175377 | |||
S5‑175377 | pCR 28.530 Add concept and use case of communication services using network slicing | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑175093 | |||
S5‑175094 | pCR 28.530 Add business level use cases of providing communication services with massive IoT connections using network slice | Huawei, CATT, China Unicom | pCR | Approval | Yes |
Yes
| merged | No | S5‑175377 | |||
S5‑175379 | pCR 28.530 Add business level use cases of providing communication services with massive IoT connections using network slice | Huawei, CATT, China Unicom | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑175095 | pCR 28.530 Add concept of services using network slicing | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175380 | |||
S5‑175380 | pCR 28.530 Add concept of services using network slicing | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175397 | S5‑175095 | ||
S5‑175397 | pCR 28.530 Add concept of services using network slicing | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑175380 | |||
S5‑175096 | pCR 28.530 Add managed network slice concept | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175381 | |||
S5‑175381 | pCR 28.530 Add managed network slice concept | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑175096 | |||
S5‑175097 | pCR 28.530 Add managed network slice subnet concept | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175403 | |||
S5‑175403 | pCR 28.530 Add managed network slice subnet concept | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175436 | S5‑175097 | ||
S5‑175436 | pCR 28.530 Add managed network slice subnet concept | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑175403 | |||
S5‑175098 | pCR 28.530 Add definition for managed network slice template | Huawei, China Telecom, CATT, China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑175404 | |||
S5‑175404 | pCR 28.530 Add definition for managed network slice template | Huawei, China Telecom, CATT, China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑175437 | S5‑175098 | ||
S5‑175437 | pCR 28.530 Add definition for managed network slice template | Huawei, China Telecom, CATT, China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑175404 | |||
S5‑175099 | pCR 28.530 Add network slice management related roles description | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175405 | |||
S5‑175405 | pCR 28.530 Add network slice management related roles description | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175467 | S5‑175099 | ||
S5‑175467 | pCR 28.530 Add network slice management related roles description | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175472 | S5‑175405 | ||
S5‑175472 | pCR 28.530 Add network slice management related roles description | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑175467 | |||
S5‑175100 | pCR 28.530 Add network slice management operation description | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑175376 | |||
S5‑175101 | pCR 28.530 Add high level service requirements | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175409 | |||
S5‑175409 | pCR 28.530 Add high level service requirements | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175438 | S5‑175101 | ||
S5‑175438 | pCR 28.530 Add high level service requirements | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑175409 | |||
S5‑175102 | pCR 28.530 Add concept of use of the non-3GPP parts for a slice | Huawei, China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑175410 | |||
S5‑175410 | pCR 28.530 Add concept of use of the non-3GPP parts for a slice | Huawei, China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑175102 | |||
S5‑175103 | pCR 28.530 Clarify Communication Service Instance Lifecycle | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175411 | |||
S5‑175411 | pCR 28.530 Clarify Communication Service Instance Lifecycle | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑175103 | |||
S5‑175104 | pCR 28.530 Add different types of services using network slice concept | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175412 | |||
S5‑175412 | pCR 28.530 Add different types of services using network slice concept | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175439 | S5‑175104 | ||
S5‑175439 | pCR 28.530 Add different types of services using network slice concept | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑175412 | |||
S5‑175105 | pCR 28.530 Add business level use case of policy management for slicing | Huawei, China Unicom | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175106 | pCR 28.530 Add business level general requirements | Huawei, China Telecom, China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑175416 | |||
S5‑175416 | pCR 28.530 Add business level general requirements | Huawei, China Telecom, China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑175473 | S5‑175106 | ||
S5‑175473 | pCR 28.530 Add business level general requirements | Huawei, China Telecom, China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑175416 | |||
S5‑175107 | pCR 28.530 Add business level requirements and use case of the exposure of management functions and management data for network slice as NSP internals case | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175108 | pCR 28.530 Add business level requirements and use case of the exposure of management functions and management data for network slice as a service case | Huawei, China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑175422 | |||
S5‑175422 | pCR 28.530 Add business level requirements and use case of the exposure of management functions and management data for network slice as a service case | Huawei, China Unicom | pCR | Approval | Yes |
Yes
| noted | No | S5‑175108 | |||
S5‑175474 | pCR 28.530 Add business level requirements and use case of the exposure of management functions and management data for network slice as a service case | Huawei, China Unicom | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑175109 | pCR 28.530 Add business level requirements and use case of the exposure of management functions and management data for network slice subnet as a service case | Huawei, China Unicom | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175110 | pCR 28.530 Add SON concept in network slicing | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175413 | |||
S5‑175413 | pCR 28.530 Add SON concept in network slicing | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175475 | S5‑175110 | ||
S5‑175475 | pCR 28.530 Add SON concept in network slicing | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑175413 | |||
S5‑175111 | pCR 28.530 Add use case and requirement for network slice instance priority | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175112 | pCR 28.530 Add concept and use case of MEC | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑175419 | pCR 28.530 Add concept and use case of MEC | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑175113 | pCR 28.530 Add use case for multi-operator slicing | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175151 | pCR Rel-15 TS 28530 Slice management model Requirements | Ericsson Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑175418 | |||
S5‑175418 | pCR Rel-15 TS 28530 Slice management model Requirements | Ericsson Inc. | pCR | Approval | Yes |
Yes
| noted | No | S5‑175151 | |||
S5‑175153 | pCR Relation of NMSF, NSSMF, EM/DM/NM management functions | Ericsson Inc. | pCR | Approval | No |
Yes
| revised | No | S5‑175154 | |||
S5‑175154 | pCR Rel-15 TS 28530 Relation of NMSF, NSSMF, EM/DM/NM management functions | Ericsson Inc. | pCR | Approval | Yes |
Yes
| noted | No | S5‑175153 | |||
S5‑175189 | pCR to the TS 28.530 Network Slice Instance creation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175216 | 5G network slicing management architecture framework principles | NTT DOCOMO | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑175415 | |||
S5‑175415 | 5G network slicing management architecture framework principles | NTT DOCOMO | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑175216 | |||
S5‑175217 | pCR TS 28.530 Network Slicing management framework principles | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑175414 | |||
S5‑175414 | pCR TS 28.530 Network Slicing management framework principles | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑175488 | S5‑175217 | ||
S5‑175488 | pCR TS 28.530 Network Slicing management framework principles | NTT DOCOMO | pCR | Approval | No |
Yes
| left for email approval | No | S5‑175414 | |||
S5‑175223 | S5-175223 Sequence proposal for network slicing concepts use cases and requirements agenda point 6.4.3 | Ericsson Limited | pCR | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑175224 | pCR 28.530 Overview of use cases and requirements for management of network slicing | Ericsson Limited | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑175417 | pCR 28.530 Overview of use cases and requirements for management of network slicing | Ericsson Limited | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
S5‑175226 | pCR 28.530 text proposal for background and concepts | Ericsson Limited | pCR | Approval | Yes |
Yes
| revised | No | S5‑175376 | |||
S5‑175376 | pCR 28.530 text proposal for background and concepts | Ericsson Limited | pCR | Approval | Yes |
Yes
| revised | No | S5‑175476 | S5‑175226 | ||
S5‑175476 | pCR 28.530 text proposal for background and concepts | Ericsson Limited,Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑175376 | |||
S5‑175228 | pCR 28.530 Use case and requirements for activate network slice instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175229 | pCR 28.530 Use case and requirements for activate network slice subnet instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175230 | pCR 28.530 Use case and requirements for create a network slice instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| revised | No | S5‑175420 | |||
S5‑175420 | pCR 28.530 Use case and requirements for create a network slice instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| revised | No | S5‑175477 | S5‑175230 | ||
S5‑175477 | pCR 28.530 Use case and requirements for create a network slice instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| approved | No | S5‑175420 | |||
S5‑175233 | pCR 28.530 Use case and requirements for create a network slice subnet instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| revised | No | S5‑175421 | |||
S5‑175421 | pCR 28.530 Use case and requirements for create a network slice subnet instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| revised | No | S5‑175478 | S5‑175233 | ||
S5‑175478 | pCR 28.530 Use case and requirements for create a network slice subnet instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| approved | No | S5‑175421 | |||
S5‑175234 | pCR 28.530 Use case and requirements for de-activate network slice instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175236 | pCR 28.530 Use case and requirements for de-activate network slice subnet instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175237 | pCR 28.530 Use case and requirements for modify a network slice instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175238 | pCR 28.530 Use case and requirements for modify a network slice subnet instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175239 | pCR 28.530 Use case and requirements for query the network slice instance status | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175240 | pCR 28.530 Use case and requirements for query the network slice subnet instance status | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175241 | pCR 28.530 Use case and requirements for read a network slice instance attribute | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175242 | pCR 28.530 Use case and requirements for read a network slice subnet instance attribute | Ericsson Limited | pCR | Yes |
Yes
| not treated | No | |||||
S5‑175243 | pCR 28.530 Use case and requirements for subscribe to NSMF notifications | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175244 | pCR 28.530 Use case and requirements for subscribe to NSSMF notifications | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175245 | pCR 28.530 Use case and requirements for terminate a network slice instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175246 | pCR 28.530 Use case and requirements for terminate a network slice subnet instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175272 | Add business level requirements of provide network slice as a service with guaranteed quality of service | China Mobile | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175278 | pCR 28.530 Use case and requirements for report performance of a network slice instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175279 | pCR 28.530 Use case and requirements for report performance of a network slice subnet instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175280 | pCR 28.530 Use case and requirements for supervise a network slice instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175281 | pCR 28.530 Use case and requirements for supervise a network slice subnet instance | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175282 | pCR 28.530 Use case and requirements for unsubscribe from NSMF notifications | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175283 | pCR 28.530 Use case and requirements for unsubscribe from NSSMF notifications | Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175435 | Revised WID on Management of Network Slicing in Mobile networks | Ericsson | WID revised | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑175471 | Draft TS 28.530 | Ericsson | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
6.4.4 | Provisioning of network slicing for 5G networks and services | S5‑175037 | Minutes of Provisioning of network slicing for 5G networks and services | Rapporteur (Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑175114 | Draft TS 28.531 Provisioning of network slicing for 5G networks and services | Huawei | draft TS | Approval | Yes |
Yes
| approved | No | ||||
S5‑175115 | pCR 28.531 Adding new skeleton clauses | Huawei, Nokia | pCR | Approval | Yes |
Yes
| revised | No | S5‑175423 | |||
S5‑175423 | pCR 28.531 Adding new skeleton clauses | Huawei, Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑175115 | |||
S5‑175116 | pCR 28.531 Adding content of scope | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑175117 | pCR 28.531 Add potential network slice subnet deployment scenarios | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑175118 | pCR 28.531 Adding use case of utilizing network slice instance for communication service | Huawei | pCR | Approval | Yes |
Yes
| merged | No | S5‑175425 | |||
S5‑175424 | pCR 28.531 Adding use case of utilizing network slice instance for communication service | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑175119 | pCR 28.531 Adding use case of network slice instance creation | Huawei, CATT, China Unicom | pCR | Approval | Yes |
Yes
| revised | No | S5‑175425 | |||
S5‑175425 | pCR 28.531 Adding use case of network slice instance creation | Huawei, CATT, China Unicom | pCR | Approval | Yes |
Yes
| approved | No | S5‑175119 | |||
S5‑175120 | pCR 28.531 Adding use case of network slice subnet instance creation | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175426 | |||
S5‑175426 | pCR 28.531 Adding use case of network slice subnet instance creation | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑175120 | |||
S5‑175121 | pCR 28.531 Adding general description for managed network slice template | Huawei, CATR, China Unicom | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175122 | pCR 28.531 Adding information model for managednetworkslice and managednetworkslicesubnet | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175123 | pCR 28.531 Add network slice related management functions | Huawei, CATR, China Telecom, CATT, China Unicom | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175124 | pCR 28.531 Add general description of provisioning of network slice instance | Huawei | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175152 | pCR Rel-15 28531 Slice management mode | Ericsson Inc. | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑175182 | Discussion paper about Network slice modelling | ZTE Corporation | discussion | Discussion | Yes |
Yes
| not treated | No | ||||
S5‑175479 | Draft TS 28.531 | Huawei | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
6.4.5 | Self-Organizing Networks (SON) for Active Antenna System (AAS) deployment management | S5‑175038 | Minutes of Self-Organizing Networks (SON) for Active Antenna System (AAS) deployment management | Rapporteur (Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑175192 | Rel-15 CR 28.627 Add SON for AAS management requirements | Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑175428 | |||
S5‑175428 | Rel-15 CR 28.627 Add SON for AAS management requirements | Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑175192 | |||
S5‑175193 | Rel-15 CR 28.628 Add SON for AAS management description and attributes | Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑175429 | |||
S5‑175429 | Rel-15 CR 28.628 Add SON for AAS management description and attributes | Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑175440 | S5‑175193 | ||
S5‑175440 | Rel-15 CR 28.628 Add SON for AAS management description and attributes | Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑175429 | |||
S5‑175199 | Rel-15 CR 28.658 Add attribute of E-UTRAN cell IOC to support SON for AAS management requirements | Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑175430 | |||
S5‑175430 | Rel-15 CR 28.658 Add attribute of E-UTRAN cell IOC to support SON for AAS management requirements | Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑175199 | |||
6.5 | OAM&P Studies |   | ||||||||||
6.5.1 | Study on Implementation for the Partitioning of Itf-N | S5‑175021 | Minutes for Study on Implementation for the Partitioning of Itf-N | Rapporteur(China Mobile) | report | Yes |
Yes
| noted | No | |||
S5‑175183 | pCR TR 32.880 Conclusionfor TR32.880 | China Mobile | pCR | Approval | Yes |
Yes
| revised | No | S5‑175431 | |||
S5‑175431 | pCR TR 32.880 Conclusionfor TR32.880 | China Mobile | pCR | Approval | Yes |
Yes
| approved | No | S5‑175183 | |||
S5‑175480 | Draft TR 32.880 | China Mobile | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.2 | Study on Management and Orchestration Architecture of Next Generation Network and Service | S5‑175020 | Minutes for Study on Management and Orchestration Architecture of Next Generation Network and Service | Rapporteur (Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑175125 | pCR 28.800 Remove unnecessary editor note regarding network slicing | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175126 | pCR 28.800 Add skeleton for 5G management architecture aspects | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑175345 | pCR 28.800 Add skeleton for 5G management architecture aspects | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑175127 | pCR 28.800 Management architecture relation between the non-5G NE management functions and the 5G NE management functions | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175346 | |||
S5‑175346 | pCR 28.800 Management architecture relation between the non-5G NE management functions and the 5G NE management functions | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175481 | S5‑175127 | ||
S5‑175481 | pCR 28.800 Add Management architecture option | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑175346 | |||
S5‑175128 | pCR 28 800 Management architecture relation between Service management functions and slicing management functions | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑175347 | pCR 28 800 Management architecture relation between Service management functions and slicing management functions | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑175129 | pCR 28.800 Management architecture relation between slicing management functions and 5G NE management functions | Huawei, CATR, China Unicom | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑175350 | pCR 28.800 Management architecture relation between slicing management functions and 5G NE management functions | Huawei, CATR, China Unicom | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑175130 | pCR 28.800 Management architecture relation between slicing management functions and NFV-MANO | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175353 | |||
S5‑175353 | pCR 28.800 Management architecture relation between slicing management functions and NFV-MANO | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175483 | S5‑175130 | ||
S5‑175483 | pCR 28.800 Management architecture relation between slicing management functions and NFV-MANO | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175489 | S5‑175353 | ||
S5‑175489 | pCR 28.800 Management architecture relation between slicing management functions and NFV-MANO | Huawei | pCR | Approval | Yes |
Yes
| left for email approval | No | S5‑175483 | |||
S5‑175131 | pCR 28 800 Management Architecture for Multiple Operators communication | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175354 | |||
S5‑175354 | pCR 28 800 Management Architecture for Multiple Operators communication | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑175131 | |||
S5‑175167 | pCR TR 28.800 Add 5G network and service management and orchestration architecture option | Intel Finland Oy | pCR | Approval | Yes |
Yes
| merged | No | S5‑175350 | |||
S5‑175180 | Paper to discuss edge computing management issues | Intel | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑175344 | Draft TR 28.800 | Huawei | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
S5‑175367 | Breakout session for way forward for 5G network management architecture | Huawei | report | Information | Yes |
Yes
| noted | No | ||||
S5‑175482 | Draft TR 28.800 | Huawei | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.3 | Study on management aspects of next generation network architecture and features | S5‑175022 | Minutes for Study on management aspects of next generation network architecture and features | Rapporteur(Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑175067 | NR NRM Requirements | Ericsson LM | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑175068 | NR NRM Requirements | Ericsson LM | pCR | Approval | Yes |
Yes
| revised | No | S5‑175365 | |||
S5‑175365 | NR NRM Requirements | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑175068 | |||
S5‑175069 | TR 28.802 Add potential solution for NR NRM | Ericsson LM | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑175366 | TR 28.802 Add potential solution for NR NRM | Ericsson LM | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑175172 | pCR 28.802 add an UC for collecting performance measurements | Intel | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑175355 | pCR 28.802 add an UC for collecting performance measurements | Intel | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑175173 | pCR 28.802 add an UC for detecting faults | Intel | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑175364 | pCR 28.802 add an UC for detecting faults | Intel | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑175204 | Rel-15 pCR 28.802 Add use cases to support management for ng-eNB connected to 5GC and EPC simultaneously | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑175372 | |||
S5‑175372 | Rel-15 pCR 28.802 Add use cases to support management for ng-eNB connected to 5GC and EPC simultaneously | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑175204 | |||
S5‑175205 | Rel-15 pCR 28.802 Add potential NRM solution for gNB with functional split | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑175368 | |||
S5‑175368 | Rel-15 pCR 28.802 Add potential NRM solution for gNB with functional split | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑175205 | |||
S5‑175206 | Rel-15 pCR 28.802 Add potential solution for NR performance management | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑175369 | |||
S5‑175369 | Rel-15 pCR 28.802 Add potential solution for NR performance management | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑175206 | |||
S5‑175207 | Rel-15 pCR 28.802 Add potential solution for NR fault management | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑175370 | |||
S5‑175370 | Rel-15 pCR 28.802 Add potential solution for NR fault management | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑175207 | |||
S5‑175208 | Rel-15 pCR 28.802 Add potential solutions for ng-eNB management | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑175373 | |||
S5‑175373 | Rel-15 pCR 28.802 Add potential solutions for ng-eNB management | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑175208 | |||
S5‑175274 | Rel-15 pCR 28.802 Add conclusion and Recommendations for 5GC management | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑175374 | |||
S5‑175374 | Rel-15 pCR 28.802 Add conclusion and Recommendations for 5GC management | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑175274 | |||
S5‑175275 | Rel-15 pCR 28.802 Add conclusion and Recommendations for NR management | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑175371 | |||
S5‑175371 | Rel-15 pCR 28.802 Add conclusion and Recommendations for NR management | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑175275 | |||
S5‑175276 | Rel-15 pCR 28.802 Add use cases to support trace management in 5GS | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑175375 | |||
S5‑175375 | Rel-15 pCR 28.802 Add use cases to support trace management in 5GS | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑175276 | |||
S5‑175277 | Rel-15 pCR 28.802 Add annex for relationship analysis between existing TSs and 5G NF management solutions | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑175285 | pCR TR 28.802 Add SON automated healing functionality for gNB in 5G-RAN | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑175286 | pCR TR 28.802 Add SON automated optimization functionality for gNB in 5G-RAN | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑175332 | TR 28.802 TDocs discussion sequence proposal for section 6.5.3 | Nokia | other | Information | Yes |
Yes
| noted | No | ||||
S5‑175484 | Draft TR 28.802 | Nokia | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.4 | Study on Management aspects of selected IoT-related features | S5‑175028 | Minutes of Study on Management aspects of selected IoT-related features | Rapporteur (Cisco) | report | Yes |
Yes
| noted | No | |||
S5‑175184 | pCR to the TR 32.857 TB related measurements | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175185 | pCR to the TR 32.857 S1-connection related measurements | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175186 | pCR to the TR 32.857 CQI and TA Distribution | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175187 | pCR to the TR 32.857 Measurements related to Measurement Report | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175432 | Draft TR 32.857 | Cisco | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.5 | Study on a RESTful HTTP-based Solution Set | S5‑175029 | Minutes of Study on a RESTful HTTP-based Solution Set | Rapporteur (Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑175220 | pCR 32.866 Discussion paper presenting considerations and alternatives | Ericsson Limited | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑175221 | pCR 32.866 Alternative solutions for filtering and scoping using hyperlinks | Ericsson Limited | pCR | Approval | Yes |
Yes
| revised | No | S5‑175460 | |||
S5‑175460 | pCR 32.866 Alternative solutions for filtering and scoping using hyperlinks | Ericsson Limited | pCR | Approval | Yes |
Yes
| revised | No | S5‑175485 | S5‑175221 | ||
S5‑175485 | pCR 32.866 Alternative solutions for filtering and scoping using hyperlinks | Ericsson Limited | pCR | Approval | No |
Yes
| left for email approval | No | S5‑175460 | |||
S5‑175257 | pCR 32.866 Add IRP design principles | Nokia Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175258 | pCR 32.866 Add Overview of existing Solution Sets | Nokia Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175259 | pCR 32.866 Add reference for REST | Nokia Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175260 | pCR 32.866 Add missing HTTP method descriptions | Nokia Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175261 | pCR 32.866 Add a new chapter about URI Templates | Nokia Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175262 | pCR 32.866 Add a second possibility for mapping the DN into a URI | Nokia Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175263 | pCR 32.866 Add references for JSON and JSON Schema | Nokia Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175264 | pCR 32.866 Add Usage of HTTP headers and media types | Nokia Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175265 | pCR 32.866 Clarify design patterns | Nokia Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175266 | pCR 32.866 Add new design pattern for iterations | Nokia Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175267 | pCR 32.866 Add Recommendations | Nokia Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑175434 | |||
S5‑175434 | pCR 32.866 Add Recommendations | Nokia Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑175267 | |||
S5‑175433 | Draft TR 32.866 | Nokia | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.6 | Study on management aspects of virtualized network functions that are part of the NR | S5‑175030 | Minutes of Study on management aspects of virtualized network functions that are part of the NR | Rapporteur (Intel) | report | Yes |
Yes
| noted | No | |||
S5‑175165 | pCR TR 32.864 Add UC on providing location information of non-virtualized part of gNB | Intel Finland Oy | pCR | Approval | Yes |
Yes
| revised | No | S5‑175441 | |||
S5‑175441 | pCR TR 32.864 Add UC on providing location information of non-virtualized part of gNB | Intel Finland Oy | pCR | Approval | Yes |
Yes
| approved | No | S5‑175165 | |||
S5‑175166 | pCR TR 32.864 Add potential solution for providing location of non-virtualized part of gNB to NFVO | Intel Finland Oy | pCR | Approval | Yes |
Yes
| revised | No | S5‑175442 | |||
S5‑175442 | pCR TR 32.864 Add potential solution for providing location of non-virtualized part of gNB to NFVO | Intel Finland Oy | pCR | Approval | Yes |
Yes
| approved | No | S5‑175166 | |||
S5‑175174 | pCR 32.864 editor note cleanup | Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑175443 | |||
S5‑175443 | pCR 32.864 editor note cleanup | Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑175174 | |||
S5‑175175 | pCR 32.864 add a UC for connecting gNB-CU to 5GC nodes | Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑175444 | |||
S5‑175444 | pCR 32.864 add a UC for connecting gNB-CU to 5GC nodes | Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑175175 | |||
S5‑175176 | pCR 32.864 alternative solution for transport network requirements update | Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑175445 | |||
S5‑175445 | pCR 32.864 alternative solution for transport network requirements update | Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑175176 | |||
S5‑175177 | pCR 32.864 Add potential solution for adding VNFFGD and adding VNFFGs for the gNB | Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑175446 | |||
S5‑175446 | pCR 32.864 Add potential solution for adding VNFFGD and adding VNFFGs for the gNB | Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑175177 | |||
S5‑175178 | pCR 32.864 add gap related to adding VNFFG | Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑175447 | |||
S5‑175447 | pCR 32.864 add gap related to adding VNFFG | Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑175178 | |||
S5‑175179 | pCR 32.864 revised conclusion | Intel | pCR | Approval | Yes |
Yes
| revised | No | S5‑175448 | |||
S5‑175448 | pCR 32.864 revised conclusion | Intel | pCR | Approval | Yes |
Yes
| approved | No | S5‑175179 | |||
S5‑175284 | pCR TR 32.864 Add UC on scaling the virtualized part of gNB for adapting to the network capacity | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175486 | Draft TR 32.864 | Intel | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.7 | Study on Management Enhancement of CUPS of EPC Nodes | S5‑175031 | Minutes of Study on Management Enhancement of CUPS of EPC Nodes | Rapporteur (Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑175132 | pCR 32.867 Editor's notes cleanup | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175133 | pCR 32.867 Add recommendations | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑175451 | |||
S5‑175451 | pCR 32.867 Add recommendations | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑175133 | |||
S5‑175134 | pCR 32.867 Add conclusions | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175202 | Rel-15 pCR 32.867 Add use cases and requirements for PFCP and GTP-U related measurements On Sxa&Sxb interface | Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175203 | Rel-15 pCR 32.867 Add use cases and requirements for configuration management for S/P-GW with CUPS | Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑175450 | |||
S5‑175450 | Rel-15 pCR 32.867 Add use cases and requirements for configuration management for S/P-GW with CUPS | Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑175203 | |||
S5‑175449 | Draft TR 32.867 | Huawei | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.8 | Study on OAM aspects of LTE and WLAN integration | S5‑175032 | Minutes of Study on OAM aspects of LTE and WLAN integration | Rapporteur (Intel) | report | Yes |
Yes
| noted | No | |||
S5‑175168 | pCR TR 32.868 Add UC on configuration of mobility set for LWA | Intel Finland Oy | pCR | Approval | Yes |
Yes
| revised | No | S5‑175455 | |||
S5‑175455 | pCR TR 32.868 Add UC on configuration of mobility set for LWA | Intel Finland Oy | pCR | Approval | Yes |
Yes
| approved | No | S5‑175168 | |||
S5‑175169 | pCR TR 32.868 Add UC on PM for non-collocated LWA | Intel Finland Oy | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175170 | pCR TR 32.868 Add UC on FM for non-collocated LWA | Intel Finland Oy | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175171 | pCR TR 32.868 Add UC on CM for LWIP | Intel Finland Oy | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175456 | Draft TR 32.868 | Intel | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.9 | Study on network policy management for mobile networks based on NFV scenarios | S5‑175033 | Minutes of Study on network policy management for mobile networks based on NFV scenarios | Rapporteur ( China Mobile) | report | Yes |
Yes
| noted | No | |||
S5‑175139 | pCR TR 32.871 The alignment of NFV policy terms and concept definition with ETSI MANO policy study | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑175457 | |||
S5‑175457 | pCR TR 32.871 The alignment of NFV policy terms and concept definition with ETSI MANO policy study | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑175139 | |||
S5‑175140 | pCR TR 32.871 The terms of NFV policy update | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175458 | Draft TR 32.871 | China Mobile | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.10 | Study on system and functional aspects of Energy Efficiency in 5G networks | S5‑175039 | Minutes of Study on system and functional aspects of Energy Efficiency in 5G networks | Rapporteur (ORANGE) | report | Yes |
Yes
| noted | No | |||
S5‑175070 | pCR TR 32.972 Restructuring clause 5.2 | ORANGE, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175071 | pCR TR 32.972 Additional existing EE KPI definitions | ORANGE, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175072 | pCR TR 32.972 Add existing EE KPI definitions for VNF | ORANGE, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175073 | pCR TR 32.972 – Introduction and Scope | ORANGE | pCR | Approval | Yes |
Yes
| revised | No | S5‑175453 | |||
S5‑175453 | pCR TR 32.972 – Introduction and Scope | ORANGE | pCR | Approval | Yes |
Yes
| approved | No | S5‑175073 | |||
S5‑175074 | pCR TR 32.972 Measurement methods | ORANGE | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175191 | pCR TS 32.972 About power consumption of network elements and functions | ORANGE | pCR | Approval | Yes |
Yes
| revised | No | S5‑175454 | |||
S5‑175454 | pCR TR 32.972 About power consumption of network elements and functions | ORANGE | pCR | Approval | No |
Yes
| left for email approval | No | S5‑175191 | |||
S5‑175452 | Draft TR 32.972 | ORANGE | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑175008 | CH Agenda and Time Plan | CH SWG Chair | agenda | Yes |
Yes
| approved | No | |||
S5‑175009 | CH Executive Report | CH SWG Chair | report | Yes |
Yes
| noted | No | |||||
S5‑175043 | Reply LS from CT1 cc SA5 on request to update maximum data rate values in EPS | C1-173572 | LS in | Yes |
Yes
| noted | No | |||||
S5‑175044 | Reply LS from CT3 to SA5 on Request to update maximum data rate values in EPS | C3-174339 | LS in | Yes |
Yes
| noted | No | |||||
S5‑175045 | Reply LS from CT4 to SA5 on Charging support for Control and User Plane Separation | C4-174324 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑175053 | Resubmitted LS from SA2 to SA5 on Stage 2 completion on introduction of WLAN as alternative technology for ProSe Direct Discovery | S2-172506 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑175299 | Reply to: Resubmitted LS from SA2 to SA5 on Stage 2 completion on introduction of WLAN as alternative technology for ProSe Direct Discovery | Intel | LS out | approval | Yes |
Yes
| approved | No | ||||
7.2 | New Charging Work Item proposals | S5‑175163 | New WID on Charging for WLAN-based Prose Direct Discovery | Intel Corporation | WID new | Approval | Yes |
Yes
| revised | No | S5‑175298 | |
S5‑175298 | New WID on Charging for WLAN-based Prose Direct Discovery | Intel Corporation | WID new | Approval | Yes |
Yes
| revised | No | S5‑175313 | S5‑175163 | ||
S5‑175313 | New WID on Charging for WLAN-based Prose Direct Discovery | Intel Corporation | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑175298 | |||
S5‑175492 | New WID on Charging for WLAN-based Prose Direct Discovery | Intel Corporation | WID new | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑175164 | CR Rel-15 32.277 Add charging description for WLAN-based ProSe direct discovery | Intel Corporation | CR | Approval | Yes |
Yes
| not pursued | No | ||||
7.3 | Charging Maintenance and Rel-15 small Enhancements | S5‑175210 | Rel-13 CR 32.298 Correction where rANNASCause is defined as a sequence | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑175302 | |
S5‑175302 | Rel-13 CR 32.298 Correction where rANNASCause is defined as a sequence | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑175210 | |||
S5‑175211 | Rel-13 CR 32.299 Correction where RAN-NAS-Release-Cause is defined as a sequence | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑175305 | |||
S5‑175305 | Rel-13 CR 32.299 Correction where RAN-NAS-Release-Cause is defined as a sequence | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑175211 | |||
S5‑175212 | Rel-14 CR 32.298 Correction where rANNASCause is defined as a sequence | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑175303 | |||
S5‑175303 | Rel-14 CR 32.298 Correction where rANNASCause is defined as a sequence | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑175212 | |||
S5‑175213 | Rel-14 CR 32.299 Correction where RAN-NAS-Release-Cause is defined as a sequence | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑175306 | |||
S5‑175306 | Rel-14 CR 32.299 Correction where RAN-NAS-Release-Cause is defined as a sequence | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑175213 | |||
S5‑175214 | Rel-15 CR 32.298 Correction where rANNASCause is defined as a sequence | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑175304 | |||
S5‑175304 | Rel-15 CR 32.298 Correction where rANNASCause is defined as a sequence | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑175214 | |||
S5‑175215 | Rel-15 CR 32.299 Correction where RAN-NAS-Release-Cause is defined as a sequence | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑175307 | |||
S5‑175307 | Rel-15 CR 32.299 Correction where RAN-NAS-Release-Cause is defined as a sequence | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑175215 | |||
7.4 | Rel-15 Charging |   | ||||||||||
7.4.1 | Charging Enhancement for eFMSS |   | ||||||||||
7.4.2 | PS Charging enhancements to support 5G New Radio via Dual Connectivity | S5‑175222 | Rel-15 CR 32.251 Data Volume Reporting for Secondary RAT usage | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑175294 | |
S5‑175294 | Rel-15 CR 32.251 Data Volume Reporting for Secondary RAT usage | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑175222 | |||
7.4.3 | Charging Aspects of Northbound APIs for SCEF-SCS/AS Interworking | S5‑175055 | Resubmitted LS from SA3 cc SA5 Reply LS on Security for T8 interface | S3-172076 | LS in | Yes |
Yes
| noted | No | |||
S5‑175078 | R15 CR 32.240 Introduce the Northbound API charging | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement | Yes |
Yes
| revised | No | S5‑175295 | |||
S5‑175295 | R15 CR 32.240 Introduce the Northbound API charging | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement | Yes |
Yes
| agreed | No | S5‑175078 | |||
S5‑175079 | Rel-15 pCR 32.254 Charging Principle for NAPS | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| revised | No | S5‑175296 | |||
S5‑175296 | Rel-15 pCR 32.254 Charging Principle for NAPS | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| approved | No | S5‑175079 | |||
S5‑175080 | Rel-15 pCR 32.254 Basic principle for Online Charging | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| revised | No | S5‑175297 | |||
S5‑175297 | Rel-15 pCR 32.254 Basic principle for Online Charging | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| approved | No | S5‑175080 | |||
S5‑175081 | Rel-15 pCR 32.254 Basic principle for Offline Charging | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| revised | No | S5‑175300 | |||
S5‑175300 | Rel-15 pCR 32.254 Basic principle for Offline Charging | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| approved | No | S5‑175081 | |||
S5‑175301 | Draft TS 32.254 | Huawei | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
7.5 | Charging Studies |   | ||||||||||
7.5.1 | Study on Overload Control for Diameter Charging Applications | S5‑175231 | pCR 32.869 Description of existing overload control mechanism for online | Ericsson LM | pCR | Agreement | Yes |
Yes
| revised | No | S5‑175308 | |
S5‑175308 | pCR 32.869 Description of existing overload control mechanism for online | Ericsson LM | pCR | Agreement | Yes |
Yes
| approved | No | S5‑175231 | |||
S5‑175232 | pCR 32.869 OLR with buffer mechanism as alternative solution for online | Ericsson LM | pCR | Agreement | Yes |
Yes
| revised | No | S5‑175309 | |||
S5‑175309 | pCR 32.869 OLR with buffer mechanism as alternative solution for online | Ericsson LM | pCR | Agreement | Yes |
Yes
| approved | No | S5‑175232 | |||
S5‑175235 | pCR 32.869 OCS with CDR mechanism as alternative solution for online | Ericsson LM | pCR | Agreement | Yes |
Yes
| revised | No | S5‑175310 | |||
S5‑175310 | pCR 32.869 OCS with CDR mechanism as alternative solution for online | Ericsson LM | pCR | Agreement | Yes |
Yes
| approved | No | S5‑175235 | |||
S5‑175271 | OLR with with service specific mechanism as alternative solution for online | Ericsson LM | pCR | Agreement | Yes |
Yes
| revised | No | S5‑175311 | |||
S5‑175311 | pCR 32.869 OLR with with service specific mechanism as alternative solution for online | Ericsson LM | pCR | Approval | Yes |
Yes
| approved | No | S5‑175271 | |||
S5‑175312 | Draft TR 32.869 | Ericsson | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
7.5.2 | Study on forward compatibility for 3GPP Diameter Charging Applications | S5‑175287 | Rel-15 pCR TR 32.870 Solution for Key issues 3-4-5 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑175288 | Rel-15 pCR TR 32.870 Elaborate Solution 1 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑175395 | |||
S5‑175395 | Rel-15 pCR TR 32.870 Elaborate Solution 1 | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑175288 | |||
S5‑175396 | TR 32.870 | Nokia, Nokia Shanghai Bell | draft TR | discussion | No |
Yes
| left for email approval | No | ||||
7.5.3 | Study on Charging Aspects of 5G System Architecture Phase 1 | S5‑175046 | LS from CT3/CT4 to SA5 on Conclusion on Service Based Architecture Protocol Selection | C3-174370,C4-174343 | LS in | Yes |
Yes
| noted | No | |||
S5‑175082 | Rel-15 pCR 32.899 Update of Reference | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| approved | No | ||||
S5‑175083 | Rel-15 pCR 32.899 Update of Network Capability Exposure | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| revised | No | S5‑175314 | |||
S5‑175314 | Rel-15 pCR 32.899 Update of Network Capability Exposure | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| approved | No | S5‑175083 | |||
S5‑175084 | Rel-15 pCR 32.899 PDU session charging – counts in two UPF anchors | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| revised | No | S5‑175319 | |||
S5‑175319 | Rel-15 pCR 32.899 PDU session charging – counts in two UPF anchors | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| approved | No | S5‑175084 | |||
S5‑175085 | Rel-15 pCR 32.899 QoS Flow based Charging | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| revised | No | S5‑175315 | |||
S5‑175315 | Rel-15 pCR 32.899 QoS Flow based Charging | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| approved | No | S5‑175085 | |||
S5‑175086 | Rel-15 pCR 32.899 Charging for removal of additional PDU session Anchor and Branching Point or UL CL | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| revised | No | S5‑175320 | |||
S5‑175320 | Rel-15 pCR 32.899 Charging for removal of additional PDU session Anchor and Branching Point or UL CL | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| approved | No | S5‑175086 | |||
S5‑175087 | Rel-15 pCR 32.899 Charging procedure for UE Served by Multiple NSIs | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| revised | No | S5‑175385 | |||
S5‑175385 | Rel-15 pCR 32.899 Charging procedure for UE Served by Multiple NSIs | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑175087 | |||
S5‑175088 | Rel-15 pCR 32.899 Charging procedure for Network Slicing Tenant based Charging | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑175089 | Rel-15 pCR 32.899 Interworking between 5G System and existing systems - EPS handover 5G | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| revised | No | S5‑175316 | |||
S5‑175316 | Rel-15 pCR 32.899 Interworking between 5G System and existing systems - EPS handover 5G | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑175089 | |||
S5‑175142 | Rel-15 pCR TR 32.899 PDU session charging continuity | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑175317 | |||
S5‑175317 | Rel-15 pCR TR 32.899 PDU session charging continuity | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑175142 | |||
S5‑175143 | Rel-15 pCR TR 32.899 Architecture conclusion for Session management and Service continuity | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175144 | Rel-15 pCR TR 32.899 PDU sessions with BP and ULCL- additional scenarios | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑175321 | |||
S5‑175321 | Rel-15 pCR TR 32.899 PDU sessions with BP and ULCL- additional scenarios | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑175144 | |||
S5‑175145 | Rel-15 pCR TR 32.899 online and offline - solution 9.1 evaluation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175146 | Rel-15 pCR TR 32.899 online and offline charging solution 9.2 evaluation | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175147 | Rel-15 pCR TR 32.899 Online and offline new solution 9.x | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175148 | Rel-15 pCR TR 32.899 Roaming Home routed – charging architecture | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑175323 | |||
S5‑175323 | Rel-15 pCR TR 32.899 Roaming Home routed – charging architecture | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑175148 | |||
S5‑175149 | Rel-15 pCR TR 32.899 registration topic in a new chapter | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑175384 | |||
S5‑175384 | Rel-15 pCR TR 32.899 registration topic in a new chapter | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑175149 | |||
S5‑175225 | pCR 32.899 Solution to key issue #7.1 Service based architecture | Ericsson LM | pCR | Agreement | Yes |
Yes
| revised | No | S5‑175387 | |||
S5‑175387 | pCR 32.899 Solution to key issue #7.1 Service based architecture | Ericsson LM | pCR | Agreement | Yes |
Yes
| approved | No | S5‑175225 | |||
S5‑175227 | pCR 32.899 Solution to key issue #4.2 Network slicing | Ericsson LM | pCR | Agreement | Yes |
Yes
| revised | No | S5‑175386 | |||
S5‑175386 | pCR 32.899 Solution to key issue #4.2 Network slicing | Ericsson LM | pCR | Agreement | Yes |
Yes
| approved | No | S5‑175227 | |||
S5‑175268 | Rel-15 pCR TR 32.899 reporting and quota management – update scenarios | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑175322 | |||
S5‑175322 | Rel-15 pCR TR 32.899 reporting and quota management – update scenarios | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑175268 | |||
S5‑175273 | Discussion paper on 5G Charging work status | Nokia | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑175318 | Rel-15 pCR TR 32.899 Rules for Flows description | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175383 | Rel-15 pCR TR 32.899 Topic 5.9 for HPLMN in roaming and non Roaming | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑175388 | Draft TR 32.899 | Huawei | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
7.5.4 | Study on Volume Based Charging Aspects for VoLTE | S5‑175063 | pCR 32.848 Scope enhancement | China Mobile (Suzhou) Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑175389 | |
S5‑175389 | pCR 32.848 Scope enhancement | China Mobile (Suzhou) Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑175063 | |||
S5‑175064 | pCR 32.848 Potential requirements | China Mobile (Suzhou) Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑175390 | |||
S5‑175390 | pCR 32.848 Potential requirements | China Mobile (Suzhou) Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑175064 | |||
S5‑175065 | pCR 32.848 Charging architecture | China Mobile (Suzhou) Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑175391 | |||
S5‑175391 | pCR 32.848 Charging architecture | China Mobile (Suzhou) Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑175065 | |||
S5‑175066 | pCR 32.848 Key Issue Support of the end user identifier | China Mobile (Suzhou) Software | pCR | Approval | Yes |
Yes
| revised | No | S5‑175392 | |||
S5‑175392 | pCR 32.848 Key Issue Support of the end user identifier | China Mobile (Suzhou) Software | pCR | Approval | Yes |
Yes
| approved | No | S5‑175066 | |||
S5‑175077 | Rel-15 pCR 32.848 Charging for support of CAT | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Agreement | Yes |
Yes
| revised | No | S5‑175393 | |||
S5‑175393 | Rel-15 pCR 32.848 Charging for support of CAT | HUAWEI TECHNOLOGIES Co. Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑175077 | |||
S5‑175394 | Draft TR 32.848 | China Mobile | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |