Tdoc List
2016-11-18 12:15
Agenda | Topic | TDoc | Title | Source | Type | For | Avail | Treated | Decision | Wdrn | Replaced-by | Replaces |
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Opening of the meeting |   | ||||||||||
2 | Approval of the agenda | S5‑166000 | Agenda | WG Chairman | agenda | Yes |
Yes
| approved | No | |||
3 | IPR declaration | S5‑166032 | IPR and legal declaration | WG Chairman | other | Yes |
Yes
| noted | No | |||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑166001 | Report from last SA5 meeting | ETSI Secretariat | report | Yes |
Yes
| approved | No | |||
4.2 | Last SA meeting report | S5‑166002 | SA5 status report at last SA meeting | WG Chairman | report | Yes |
Yes
| noted | No | |||
S5‑166003 | SA5 results at last SA meeting | WG Chairman | report | Yes |
Yes
| noted | No | |||||
4.3 | Inter-organizational reports | S5‑166053 | 3GPP SA5 Presentation for 2016 SON conference | SA5 Vice Chairman | report | Information | Yes |
YesIt was commented that the concept of PLMN is a bit difficult to understand outside 3GPP. This was changed apparently in the slide about 32.101.
| noted | No | ||
S5‑166254 | Report from methodology coordination meeting with ITU-T SG2 | Ericsson LM | other | No |
No
| withdrawn | Yes | |||||
S5‑166280 | Invitation to Network and Service Management workshop | WG Chair | other | Information | Yes |
Yes
| noted | No | ||||
S5‑166281 | Invitation to Information Modelling workshop | WG Chair | other | discussion | Yes |
YesZou Lan (Huawei) has volunteered to attend the workshop on information modelling in Bonn hosted by DT.
Main objective is to find a common model for NFV management.
| noted | No | ||||
5 | Cross-SWG issues |   | ||||||||||
5.1 | Administrative issues at SA5 level | S5‑166006 | Leaders meeting agenda | WG Chairman | agenda | Yes |
Yes
| noted | No | |||
S5‑166007 | Leaders meeting minutes | WG Chairman | report | Yes |
YesThe Chair asked the attendees about the possibility of having extra meetings to cope with the work overload. This was taken into account and to be considered for 2017. Some extra time could be taken to work on the quality of the specifications before their approval.
Ericsson and Intel welcomed the idea.
Nokia asked whether the quality process covered only the drafting rules. The Chair commented that not only that but also the writing style and content. Maryse didn’t find it necessary for the case of Charging specs.
Olaf argued about the limited amount of time to do such work.Additional meetings for this can take time from the real technical work. Additional time for preparation of the meetings derives into better quality of work. Conference calls, electronic meetings have never worked. These should last longer; e.g four hours during two days. This case has worked well in MEC.
Ericsson argued that the time difference would be a big handicap here.
Anatoly (Nokia) commented that making more meetings for improving the quality would not make the work more efficient: a waste of money and time.
| noted | No | |||||
S5‑166011 | SA5 Working Procedures | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||||
S5‑166012 | SA5 Meeting Facility Requirements | WG Vice Chair (Orange) | other | Yes |
Yes
| noted | No | |||||
S5‑166013 | Process for management of draft TSs/TRs | WG Chairman | other | Yes |
Yes
| noted | No | |||||
S5‑166014 | CR Quality Check | ETSI Secretariat | other | Yes |
Yes
| noted | No | |||||
S5‑166033 | Status of email approvals | WG Vice Chair (Orange) | other | No |
No
| reserved | No | |||||
S5‑166069 | SA5 LS handling process | SA5 vice chairman | discussion | Decision | No |
No
| withdrawn | Yes | ||||
S5‑166452 | Launch of TS quality campaign | WG Chair | other | Information | No |
Yes
| left for email approval | No | ||||
5.2 | Technical issues at SA5 level |   | ||||||||||
5.3 | Liaison statements at SA5 level | S5‑166047 | LS from SA2 cc SA5 on I-WLAN handling and specification withdrawal | S2-165026 | LS in | Yes |
Yes
| noted | No | |||
S5‑166050 | LS from TSG SA cc SA5 on Cooperation on NGS FMC | SP-160743 | LS in | Yes |
Yes
| noted | No | |||||
S5‑166120 | LS from NGMN to SA5 on Update to NGMN Description of Network Slicing Concept | NGMN Alliance | LS in | Yes |
YesMaryse (Nokia) asked about the relationship between the NGMN requirements and 3GPP work. Are there any charging requirements from NGMN?
Thomas (Chair) commented that he wasn't aware of any.
| noted | No | |||||
S5‑166253 | LS from IMT2020 to SA5 on Collaborative Design of 5G Architecture and the Platform | IMT2020 | LS in | Yes |
YesEricsson: time plan stops activities in 2017, it will be difficult the colaboration this way.
The Chair commented that there will be no colaboration with the study but later in the standardization phase.
| noted | No | |||||
S5‑166257 | LS from NGMN cc SA5 on First set of Architecture Principles from the NGMN P1 E2E Architecture Framework project | NGMN | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑166259 | LS from SA3 cc SA5 on Reply LS on I-WLAN handling and specification withdrawal | S3-162017 | LS in | Information | Yes |
Yes
| noted | No | ||||
S5‑166396 | LS to SA5 on reply to 3GPP SA5 on use of un-instantiated VNF instance ID in UpdateNS operation | ETSI ISG NFV | LS in | discussion | Yes |
Yes
| postponed | No | ||||
S5‑166474 | LS to SA5 on the progress of QoE Measurement Collection for Streaming to RAN3, SA4, SA5 and CT1 | R2-168917 | LS in | discussion | Yes |
Yes
| postponed | No | ||||
5.4 | SA5 meeting calendar | S5‑166010 | SA5 Meeting Calendar | WG Vice Chair (Huawei) | other | Yes |
YesMarch meeting in Guilin (China). Huawei will also host a meeting for NGMN in march as well, before the SA5 meeting.
May meeting is in US but the location is not decided yet.
It's being checked whether there could be a co-location with SA2 in August in Japan.
October meeting will be held in South Korea: Busan most likely.
2018 meeting dates were proposed
| noted | No | |||
5.5 | Review of the Work Plan | S5‑166015 | Deliverables due for the NEXT SA Plenary | ETSI Secretariat | other | Yes |
Yes
| noted | No | |||
S5‑166016 | Ongoing SA5 WIDs and SIDs | WG Vice Chair (Huawei) | other | Yes |
Yes
| noted | No | |||||
S5‑166017 | SA5 3GPP Work Plan | ETSI Secretariat | other | Yes |
Yes
| noted | No | |||||
S5‑166036 | Work Plan status | WG Chair | other | No |
No
| reserved | No | |||||
S5‑166068 | SA5 work plan structure | SA5 vice chairman | discussion | Decision | Yes |
YesSA5 working procedures will be modified according to this document.
| endorsed | No | ||||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑166004 | Time Plan for OAM&P | WG Vice Chair (Huawei) | other | Yes |
Yes
| revised | No | S5‑166258 | ||
S5‑166258 | Time Plan for OAM&P | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| noted | No | S5‑166004 | |||
S5‑166005 | OAM Executive Report from THIS Meeting | WG Vice Chair (Huawei) | report | Yes |
YesIt was agreed to have an adhoc meeting on NFV and 5G for February 2017. Documents that can't be agreed or treated could be resubmitted to the adhoc in order to avoid email approvals.
Intel proposed to add NR as a topic for the meeting. Given the the timelines of this WID, Christian commented that this was not an urgent topic. He wasn't against the idea, though. A couple of contributions could be reviewed.
The objective is to help to have all the 5G studies ready for Rel-14. Christian commented that there is only one meeting left and even with the adhoc SA5 will not make it for March.
The addhoc will have decision power.
Mirko (MCC) commented that the meeting could have MCC support given the guidelines from PCG to provide support for 5G related adhoc meetings. This had to be confirmed.
The Chair asked for hosts for this meeting. ETSI HQ would be the backup option.
Maryse commented that Charging SWG could also benefit from this adhoc.
The host should be decided by the end of November.
| revised | No | S5‑166476 | ||||
S5‑166476 | OAM Executive Report from THIS Meeting | WG Vice Chair (Huawei) | report | - | Yes |
Yes
| noted | No | S5‑166005 | |||
S5‑166035 | OAM SWG action list | WG Vice Chair (Huawei) | other | Yes |
Yes
| revised | No | S5‑166327 | ||||
S5‑166327 | OAM SWG action list | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| revised | No | S5‑166408 | S5‑166035 | ||
S5‑166408 | OAM SWG action list | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| noted | No | S5‑166327 | |||
S5‑166037 | Minutes of OAM&P SWG opening session | WG Vice Chair (Huawei) | report | Yes |
Yes
| noted | No | |||||
S5‑166424 | Reply to: Resubmitted LS from ETSI NFV to SA5 on NFV Interface and Architecture specifications | Huawei | LS out | approval | No |
Yes
| left for email approval | No | ||||
S5‑166044 | LS from ETSI ISG NFV on informing about update to application view in IFA015 | ETSI ISG NFV | LS in | Yes |
Yes
| noted | No | |||||
S5‑166045 | LS from ETSI TC LI cc SA5 on Target Location | ETSI TC LI | LS in | Yes |
Yes
| noted | No | |||||
S5‑166046 | LS from ETSI ISG NFV to SA5 on Response to 3GPP on ETSI NFV Interface and Architecture specifications | ETSI ISG NFV | LS in | No |
No
| withdrawn | Yes | |||||
S5‑166049 | LS from SA4 to SA5 on QoE reporting for streaming services | S4-161126 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑166463 | Reply to: LS from SA4 to SA5 on QoE reporting for streaming services | Ericsson | LS out | approval | No |
Yes
| left for email approval | No | ||||
S5‑166051 | LS from ETSI ISG NFV on NFV-based solutions for next generation mobile networks | ETSI ISG NFV | LS in | Yes |
Yes
| replied to | No | |||||
S5‑166260 | Reply to: LS from ETSI ISG NFV on NFV-based solutions for next generation mobile networks | Huawei | LS out | approval | Yes |
Yes
| revised | No | S5‑166409 | |||
S5‑166409 | Reply to: LS from ETSI ISG NFV on NFV-based solutions for next generation mobile networks | Huawei | LS out | approval | Yes |
Yes
| revised | No | S5‑166464 | S5‑166260 | ||
S5‑166464 | Reply to: LS from ETSI ISG NFV on NFV-based solutions for next generation mobile networks | Huawei | LS out | approval | Yes |
Yes
| approved | No | S5‑166409 | |||
S5‑166052 | LS from ITU-T SG2 to SA5 on M.3020 upgrade (reply to S5-162323) | ITU-T | LS in | Yes |
Yes
| noted | No | |||||
S5‑166062 | LS reply to ATIS 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‑166262 | |||
S5‑166262 | LS reply to ATIS 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‑166062 | |||
S5‑166103 | Completion of Rel-14 NFV work | SA5 vice chairman | discussion | Decision | Yes |
Yes
| noted | No | ||||
S5‑166122 | LS from ITU-T to 3GPP on seeking collaboration on draft Recommendation “Energy efficiency Metrics and measurement methodology for 5G solutions | ITU-T | LS in | Yes |
No
| withdrawn | Yes | |||||
S5‑166123 | Reply LS from RAN2 cc SA5 on QoE reporting for streaming services | R2-167245 | LS in | Yes |
Yes
| noted | No | |||||
S5‑166124 | Reply LS from RAN3 to SA5 on the study of the management of RAN virtualized network functions | R3-162617 | LS in | Yes |
Yes
| noted | No | |||||
S5‑166125 | LS from RAN3 to SA5 on Flexible eNB-ID and Cell-ID in E-UTRAN | R3-162637 | LS in | Yes |
YesEricsson commented that eNodeB id in SA5 specs is not readable.How do you know whether it is long or short?
| replied to | No | |||||
S5‑166304 | Reply to: LS from RAN3 to SA5 on Flexible eNB-ID and Cell-ID in E-UTRAN | Ericsson | LS out | approval | Yes |
Yes
| revised | No | S5‑166410 | |||
S5‑166410 | Reply to: LS from RAN3 to SA5 on Flexible eNB-ID and Cell-ID in E-UTRAN | Ericsson | LS out | approval | Yes |
Yes
| approved | No | S5‑166304 | |||
S5‑166207 | LS from BBF to SA5 on Publication of TR-196i2 Corrigendum 3 | BBF | LS in | Yes |
Yes
| noted | No | |||||
S5‑166220 | LS from ETSI NFV to SA5 on SOL WG work plan schedule | ETSI ISG NFV | LS in | Yes |
Yes
| replied to | No | |||||
S5‑166263 | Reply to: LS from ETSI NFV to SA5 on SOL WG work plan schedule | Huawei | LS out | approval | Yes |
Yes
| revised | No | S5‑166411 | |||
S5‑166411 | Reply to: LS from ETSI NFV to SA5 on SOL WG work plan schedule | Huawei | LS out | approval | Yes |
Yes
| revised | No | S5‑166465 | S5‑166263 | ||
S5‑166465 | Reply to: LS from ETSI NFV to SA5 on SOL WG work plan schedule | Huawei | LS out | approval | Yes |
Yes
| approved | No | S5‑166411 | |||
6.2 | New OAM&P Work Item proposals | S5‑166018 | Minutes of New Work Item proposals - OAM&P | WG Vice Chair (Orange) | report | Yes |
Yes
| noted | No | |||
S5‑166189 | New SID Study of Management of CUPS | Huawei Technologies | SID new | Approval | Yes |
Yes
| noted | No | ||||
S5‑166462 | WID on Management Enhancement of CUPS | Huawei | WID new | Agreement | Yes |
Yes
| revised | No | S5‑166471 | |||
S5‑166471 | WID on Management Enhancement of CUPS | Huawei | WID new | Agreement | Yes |
YesLate submission by Huawei taking into account the changes in SA2's work.
Vodafone, Deutsche Telekom also supported this work.
Ericsson, Cisco didn’t agree with the WID.
Ericsson: The work hasn't finished in SA2.
Cisco proposed a Study phase.
It was agreed to send it for email approval.
Nokia: why the rush? Why the dates are so ambitious?
| revised | No | S5‑166475 | S5‑166462 | ||
S5‑166475 | WID on Management Enhancement of CUPS | Huawei | WID new | Agreement | No |
Yes
| left for email approval | No | S5‑166471 | |||
6.3 | OAM&P Maintenance and Rel-14 small Enhancements | S5‑166019 | Minutes of OAM&P Maintenance and Rel-14 small Enhancements | MCC | report | Yes |
Yes
| noted | No | |||
S5‑166054 | Rel-8 CR 32.412 Correction of the information type for input parameter priority of the operation “Create measurement job” | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166055 | Rel-9 CR 32.412 Correction of the information type for input parameter priority of the operation “Create measurement job” | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166056 | Rel-10 CR 32.412 Correction of the information type for input parameter priority of the operation “Create measurement job” | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166057 | Rel-11 CR 32.412 Correction of the information type for input parameter priority of the operation “Create measurement job” | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166058 | Rel-12 CR 32.412 Correction of the information type for input parameter priority of the operation “Create measurement job” | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166059 | Rel-13 CR 32.412 Correction of the information type for input parameter priority of the operation “Create measurement job” | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166063 | Rel-11 CR 28.622 Clarification on the need to show VsDataContainer self-containing itself several times | ORANGE, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166064 | Rel-12 CR 28.622 Clarification on the need to show VsDataContainer self-containing itself several times | ORANGE, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166065 | Rel-13 CR 28.622 Clarification on the need to show VsDataContainer self-containing itself several times | ORANGE, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166101 | Draft CR 32.103 Alignment with latest SA5 specification list and various enhancements | Huawei, Ericsson | draftCR | Approval | Yes |
Yes
| revised | No | S5‑166264 | |||
S5‑166264 | CR 32.103 Alignment with latest SA5 specification list and various enhancements | Huawei, Ericsson | draftCR | Approval | Yes |
Yes
| revised | No | S5‑166329 | S5‑166101 | ||
S5‑166329 | CR 32.103 Alignment with latest SA5 specification list and various enhancements | Huawei, Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | S5‑166264 | |||
S5‑166165 | Add information to description of Management reference model in TS 32.101 | Ericsson | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑166265 | |||
S5‑166265 | Add information to description of Management reference model in TS 32.101 | Ericsson | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑166330 | S5‑166165 | ||
S5‑166330 | Add information to description of Management reference model in TS 32.101 | Ericsson | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑166265 | |||
S5‑166193 | Rel-14 CR 32.150 Correct wrong reference | Ericsson LM | CR | Yes |
Yes
| revised | No | S5‑166266 | ||||
S5‑166266 | Rel-14 CR 32.150 Update reference to model repertoire | Ericsson LM | CR | - | Yes |
Yes
| agreed | No | S5‑166193 | |||
S5‑166198 | Entities with multiple roles | Ericsson | discussion | Yes |
Yes
| revised | No | S5‑166267 | ||||
S5‑166267 | Entities with multiple roles | Ericsson | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑166198 | |||
S5‑166199 | Entities with multiple roles | Ericsson | discussion | No |
No
| withdrawn | Yes | |||||
S5‑166213 | Rel-13 pCR for dCR 32156 Minor corrections | Ericsson LM | other | Yes |
Yes
| agreed | No | |||||
S5‑166214 | pCR for dCR 32157 Include Interface IRP template | Ericsson LM | other | Yes |
Yes
| revised | No | S5‑166268 | ||||
S5‑166268 | pCR for dCR 32157 Include Interface IRP template | Ericsson LM | other | - | Yes |
Yes
| approved | No | S5‑166214 | |||
S5‑166215 | Rel-13 CR 28.732 Correct the usage of isNullable and multiplicity property | Ericsson LM | CR | Yes |
Yes
| agreed | No | |||||
S5‑166255 | Proposals from ITU-T SG2 | Ericsson | discussion | Yes |
Yes
| noted | No | |||||
S5‑166269 | LS to ITU-T SG2 on methodology coordination questions | Ericsson | LS out | Approval | No |
Yes
| approved | No | ||||
S5‑166283 | CR 32.103 Alignment with latest SA5 specification list and various enhancements | Huawei, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166361 | Rel-14 Draft CR 32.156 Add missing Annex | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑166362 | Rel-14 Draft CR 32.157 Include Interface IRP template | Ericsson | draftCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑166363 | Rel-14 CR 32.156 Add missing Annex | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166364 | Rel-14 CR 32.157 Include Interface IRP template | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.4 | Rel-14 Operations, Administration, Maintenance and Provisioning (OAM&P) |   | ||||||||||
6.4.1 | Management of mobile networks that include virtualized network functions |   | ||||||||||
6.4.1.1 | Management concept, architecture and requirements for mobile networks that include virtualized network functions | S5‑166022 | Minutes for Management concept, architecture and requirements for mobile networks that include virtualized network functions | Rapporteur(China Mobile) | report | Yes |
Yes
| noted | No | |||
S5‑166168 | Presentation TS 28.500 to SA for approval | China Mobile Com. Corporation | report | Approval | Yes |
Yes
| approved | No | ||||
S5‑166169 | pCR TS 28.500 techenical and editorial update on 28500-120 | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑166270 | |||
S5‑166270 | pCR TS 28.500 techenical and editorial update on 28500-120 | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑166169 | |||
S5‑166418 | Draft TS 28.500 | China Mobile | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑166419 | Rel-14 CR 32.101 (pending name) | China Mobile | CR | Agreement | No |
Yes
| left for email approval | No | ||||
6.4.1.2 | Configuration Management for mobile networks that include virtualized network functions | S5‑166023 | Minutes for Configuration Management for mobile networks that include virtualized network functions | Rapporteur(ZTE) | report | Yes |
Yes
| noted | No | |||
S5‑166137 | pCR draft TS 28.510 change the version of the IFA specs | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑166138 | pCR draft TS 28.510 remove the editor's notes | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑166272 | |||
S5‑166272 | pCR draft TS 28.510 remove the editor's notes | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑166384 | S5‑166138 | ||
S5‑166384 | pCR draft TS 28.510 remove the editor's notes | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑166272 | |||
S5‑166139 | pCR draft TS 28.510 move one requirement to business level | ZTE Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑166271 | |||
S5‑166271 | pCR draft TS 28.510 move one requirement to business level | ZTE Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑166139 | |||
S5‑166140 | pCR draft TS 28.511 Add procedure of creating MOI(s) after a VNF is instantiated | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑166141 | pCR draft TS 28.512 Add description about interface definition | ZTE Corporation | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑166142 | Discussion paper - enhancement of NRM to support the VNF | ZTE Corporation, Intel | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑166399 | |||
S5‑166399 | Discussion paper - enhancement of NRM to support the VNF | ZTE Corporation, Intel | discussion | Endorsement | Yes |
Yes
| noted | No | S5‑166142 | |||
S5‑166143 | R14 CR TS 28.621 Adding the generic configuration requirement to support management of VNFs | ZTE Corporation, Intel | CR | Agreement | Yes |
Yes
| revised | No | S5‑166279 | |||
S5‑166279 | R14 CR TS 28.621 Adding the generic configuration requirement to support management of VNFs | ZTE Corporation, Intel | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166143 | |||
S5‑166144 | R14 CR TS 28.622 Adding an attribute for ManagedElement to support management of virtualized NE | ZTE Corporation, Intel | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑166145 | R14 CR TS 28.623 Adding an attribute for ManagedElement to support management of virtualized NE | ZTE Corporation, Intel | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑166162 | pCR TS 28.510 Adding requirement and use case for createMO with VNF instance identifier | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑166273 | |||
S5‑166273 | pCR TS 28.510 Adding requirement and use case for createMO with VNF instance identifier | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑166413 | S5‑166162 | ||
S5‑166413 | pCR TS 28.510 Adding requirement and use case for createMO with VNF instance identifier | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑166273 | |||
S5‑166163 | pCR TS 28.511 Adding procedure flow for createMO with VNF instance identifier | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑166275 | |||
S5‑166275 | pCR TS 28.511 Adding procedure flow for createMO with VNF instance identifier | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑166414 | S5‑166163 | ||
S5‑166414 | pCR TS 28.511 Adding procedure flow for createMO with VNF instance identifier | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑166275 | |||
S5‑166177 | pCR TS 28.511 Procedure of querying VNF instance information through Os-Ma-nfvo | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑166276 | |||
S5‑166178 | pCR TS 28.511 Procedure of querying VNF instance information through Ve-Vnfm-em | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑166277 | |||
S5‑166179 | pCR TS 28.511 Procedures of modifying non-application VNF instance information and configuration through Os-Ma-nfvo | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑166278 | |||
S5‑166196 | 28.512 Discussion paper on LCM parameters modeling for VNF instantiation triggered by MO creation | Intel Corporation (UK) Ltd | discussion | Agreement | Yes |
Yes
| noted | No | ||||
S5‑166202 | Add relation between Modify MO attributes and VNF Scaling | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑166274 | |||
S5‑166203 | pCR 28.511 procedure of modify MO attributes | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑166308 | pCR 28.511 procedure of modify MO attributes | Intel Corporation (UK) Ltd | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑166261 | Discussion Sequence Proposal | ZTE | other | discussion | Yes |
Yes
| noted | No | ||||
S5‑166416 | Revised WID CM | ZTE | WID revised | Agreement | Yes |
Yes
| revised | No | S5‑166466 | |||
S5‑166466 | Revised WID CM | ZTE | WID revised | Agreement | Yes |
Yes
| agreed | No | S5‑166416 | |||
S5‑166417 | Draft TR 28.510 | ZTE | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
S5‑166473 | Draft TR 28.511 | ZTE | draft TR | discussion | No |
Yes
| left for email approval | No | ||||
6.4.1.3 | Fault Management for mobile networks that include virtualized network functions | S5‑166024 | Minutes for Fault Management for mobile networks that include virtualized network functions | Rapporteur(Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑166164 | pCR TS 28.517 Rapporteur changes | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑166180 | pCR TS 28.516 Procedure of VNF Healing through Ve-Vnfm-em | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑166282 | |||
S5‑166282 | pCR TS 28.516 Procedure of VNF Healing through Ve-Vnfm-em | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑166180 | |||
S5‑166182 | pCR TS 28.515 Adding missing traceability between use case and requirements | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑166420 | Revised WID FM | Huawei | WID revised | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166421 | Draft TS 28.515 | Huawei | draft TS | discussion | No |
Yes
| left for email approval | No | ||||
S5‑166422 | Draft TS 28.516 | Huawei | draft TS | discussion | No |
Yes
| left for email approval | No | ||||
S5‑166423 | Draft TS 28.517 | Huawei | draft TS | discussion | No |
Yes
| left for email approval | No | ||||
6.4.1.4 | Performance management for mobile networks that include virtualized network functions | S5‑166025 | Minutes for Performance management for mobile networks that include virtualized network functions | Rapporteur(Intel) | report | Yes |
Yes
| noted | No | |||
S5‑166042 | Resubmitted LS from ETSI NFV to SA5 on NFV Interface and Architecture specifications | ETSI ISG NFV | LS in | Yes |
Yes
| replied to | No | |||||
S5‑166136 | pCR TS 28.520 revision of a requirement | Intel Corporation (UK) Ltd | pCR | Yes |
Yes
| revised | No | S5‑166312 | ||||
S5‑166312 | pCR TS 28.520 revision of a requirement | Intel Corporation (UK) Ltd | pCR | - | Yes |
Yes
| approved | No | S5‑166136 | |||
S5‑166205 | Enrichment of use case on performance measurement collection of VNF PM data related to VR | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑166425 | Revised WID PM | Intel | WID revised | Agreement | Yes |
Yes
| revised | No | S5‑166467 | |||
S5‑166467 | Revised WID PM | Intel | WID revised | Agreement | Yes |
Yes
| agreed | No | S5‑166425 | |||
S5‑166426 | 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‑166026 | Minutes for Lifecycle management for mobile networks that include virtualized network functions | Rapporteur (Nokia Networks) | report | Yes |
Yes
| noted | No | |||
S5‑166105 | pCR to TR 28.525 Create NS Identifier | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑166313 | |||
S5‑166313 | pCR to TR 28.525 Create NS Identifier | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑166105 | |||
S5‑166106 | pCR to TR 28.525 Create a new version of already on-boarded PNFD | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑166314 | |||
S5‑166314 | pCR to TR 28.525 Create a new version of already on-boarded PNFD | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑166106 | |||
S5‑166107 | pCR to TR 28.525 Update the user defined data on PNFD | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑166315 | |||
S5‑166315 | pCR to TR 28.525 Update the user defined data on PNFD | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑166107 | |||
S5‑166108 | pCR to TR 28.525 Delete the PNFD | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑166316 | |||
S5‑166316 | pCR to TR 28.525 Delete the PNFD | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑166108 | |||
S5‑166109 | pCR to TR 28.525 Query the PNFD | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑166317 | |||
S5‑166317 | pCR to TR 28.525 Query the PNFD | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑166109 | |||
S5‑166110 | pCR to TR 28.525 Subscribe to NSD changes notifications | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑166318 | |||
S5‑166318 | pCR to TR 28.525 Subscribe to NSD changes notifications | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑166110 | |||
S5‑166111 | pCR to TR 28.525 Notify on NSD Management changes operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑166319 | |||
S5‑166319 | pCR to TR 28.525 Notify on NSD Management changes operation | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑166111 | |||
S5‑166127 | pCR to TS 28.525 alignment with published ETSI NFV specifications | Nokia Networks | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑166128 | pCR to TS 28.526 alignment with published ETSI NFV specifications | Nokia Networks | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑166129 | pCR to TS 28.526 add scope section | Nokia Networks | pCR | Approval | Yes |
Yes
| revised | No | S5‑166320 | |||
S5‑166320 | pCR to TS 28.526 add scope section | Nokia Networks | pCR | Approval | Yes |
Yes
| approved | No | S5‑166129 | |||
S5‑166130 | pCR to TS 28.527 add introduction section | Nokia Networks | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑166131 | pCR to TS 28.527 add scope section | Nokia Networks | pCR | Approval | Yes |
Yes
| revised | No | S5‑166321 | |||
S5‑166321 | pCR to TS 28.527 add scope section | Nokia Networks | pCR | Approval | Yes |
Yes
| approved | No | S5‑166131 | |||
S5‑166132 | pCR to TS 28.528 add introduction section | Nokia Networks | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑166133 | pCR to TS 28.528 add scope section | Nokia Networks | pCR | Approval | Yes |
Yes
| revised | No | S5‑166322 | |||
S5‑166322 | pCR to TS 28.528 add scope section | Nokia Networks | pCR | Approval | Yes |
Yes
| approved | No | S5‑166133 | |||
S5‑166170 | pCR TS 28.526 Procedure of VNF instantiation through Os-Ma-nfvo | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑166323 | |||
S5‑166323 | pCR TS 28.526 Procedure of VNF instantiation through Os-Ma-nfvo | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑166170 | |||
S5‑166173 | pCR TS 28.526 Procedure of NS instantiation | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑166324 | |||
S5‑166324 | pCR TS 28.526 Procedure of NS instantiation | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑166173 | |||
S5‑166174 | pCR TS 28.526 Procedure of updating an NS instance to correspond to a different NSD version | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑166325 | |||
S5‑166325 | pCR TS 28.526 Procedure of updating an NS instance to correspond to a different NSD version | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑166174 | |||
S5‑166175 | pCR TS 28.526 Procedure of VNF scaling through Os-Ma-nfvo | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑166326 | |||
S5‑166326 | pCR TS 28.526 Procedure of VNF scaling through Os-Ma-nfvo | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑166175 | |||
S5‑166276 | pCR TS 28.526 Procedure of querying VNF instance information through Os-Ma-nfvo | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑166366 | S5‑166177 | ||
S5‑166366 | pCR TS 28.526 Procedure of querying VNF instance information through Os-Ma-nfvo | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑166276 | |||
S5‑166277 | pCR TS 28.526 Procedure of querying VNF instance information through Ve-Vnfm-em | NTT DOCOMO | pCR | Approval | Yes |
Yes
| revised | No | S5‑166367 | S5‑166178 | ||
S5‑166367 | pCR TS 28.526 Procedure of querying VNF instance information through Ve-Vnfm-em | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑166277 | |||
S5‑166278 | pCR TS 28.526 Procedures of modifying non-application VNF instance information and configuration through Os-Ma-nfvo | NTT DOCOMO | pCR | Approval | Yes |
Yes
| approved | No | S5‑166179 | |||
S5‑166181 | pCR TS 28.525 Addressing Note in use case clause 6.4.1.3.1 | NTT DOCOMO | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑166328 | pCR TS 28.525 Addressing Note in use case clause 6.4.1.3.1 | NTT DOCOMO | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑166274 | pCR 28.525 Update of the use case on VNF Scaling | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑166202 | |||
S5‑166206 | Add use case on designating managing NM and managing EM for VNFs | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑166306 | pCR on 28525 text inclusion regarding LCM operations use parameter | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166385 | |||
S5‑166385 | pCR on 28525 text inclusion regarding LCM operations use parameter | Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166431 | S5‑166306 | ||
S5‑166431 | pCR on 28525 text inclusion regarding LCM operations use parameter | Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑166385 | |||
S5‑166415 | revised WID LCM | Nokia | WID revised | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166427 | Draft TS 28.525 | Nokia | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑166428 | Draft TS 28.526 | Nokia | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑166429 | Draft TS 28.527 | Nokia | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
S5‑166430 | Draft TS 28.528 | Nokia | draft TS | Approval | No |
Yes
| left for email approval | No | ||||
6.4.2 | Filtering of PM measurements and data volume measurements for shared networks | S5‑166027 | Minutes for Filtering of PM measurements and data volume measurements for shared networks | Rapporteur(Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑166060 | Rel-13 CR 32.130 Add use cases and requirements for Management of measurements for cross-operator accounting based on data volume and QoS | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑166400 | |||
S5‑166400 | Rel-13 CR 32.130 Add use cases and requirements for Management of measurements for cross-operator accounting based on data volume and QoS | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑166440 | S5‑166060 | ||
S5‑166440 | Rel-13 CR 32.130 Add use cases and requirements for Management of measurements for cross-operator accounting based on data volume and QoS | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166400 | |||
S5‑166061 | Rel-14 CR 32.425 Add measurements for cross-operator accounting based on data volume and QoS | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑166401 | |||
S5‑166401 | Rel-14 CR 32.425 Add measurements for cross-operator accounting based on data volume and QoS | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166061 | |||
S5‑166066 | Rel-13 CR 32.412 Add parameters for operation “Create measurement job” related to measurement filtering and measurement job reliability level | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑166402 | |||
S5‑166402 | Rel-13 CR 32.412 Add parameters for operation “Create measurement job” related to measurement filtering and measurement job reliability level | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166066 | |||
S5‑166067 | Rel-13 CR 32.416 Add attributes corresponding to updated IS for operation “Create measurement job” related to measurement job reliability level | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑166204 | Replacing the reference to LS with reference to TS 36.300 | Ericsson | CR | Yes |
Yes
| revised | No | S5‑166305 | ||||
S5‑166305 | Replacing the reference to LS with reference to TS 36.300 | Ericsson | CR | - | Yes |
Yes
| agreed | No | S5‑166204 | |||
S5‑166433 | Revised WID filtering PM | Ericsson | WID revised | Agreement | Yes |
No
| withdrawn | Yes | ||||
6.4.3 | OAM support for Licensed Shared Access (LSA) | S5‑166034 | Minutes of OAM support for Licensed Shared Access (LSA) | Rapporteur (Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑166190 | Scope update | RED Technologies SAS | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑166309 | Scope update | RED Technologies SAS | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑166191 | Exemplary flows | RED Technologies SAS | pCR | Approval | Yes |
Yes
| revised | No | S5‑166307 | |||
S5‑166307 | Exemplary flows | RED Technologies SAS | pCR | Approval | Yes |
Yes
| noted | No | S5‑166191 | |||
S5‑166192 | IOC definition | RED Technologies SAS | pCR | Approval | Yes |
Yes
| revised | No | S5‑166310 | |||
S5‑166310 | IOC definition | RED Technologies SAS | pCR | Approval | Yes |
Yes
| revised | No | S5‑166434 | S5‑166192 | ||
S5‑166434 | IOC definition | RED Technologies SAS | pCR | Approval | Yes |
Yes
| approved | No | S5‑166310 | |||
S5‑166194 | Cell parameters definition | RED Technologies SAS | pCR | Approval | Yes |
Yes
| revised | No | S5‑166311 | |||
S5‑166311 | Cell parameters definition | RED Technologies SAS | pCR | Approval | Yes |
Yes
| revised | No | S5‑166435 | S5‑166194 | ||
S5‑166435 | Cell parameters definition | RED Technologies SAS | pCR | Approval | No |
Yes
| left for email approval | No | S5‑166311 | |||
S5‑166216 | pCR 28.302 – Add System Context for interface between LC and NM | Nokia Networks | pCR | Yes |
Yes
| revised | No | S5‑166372 | ||||
S5‑166372 | pCR 28.302 – Add System Context for interface between LC and NM | Nokia Networks | pCR | - | Yes |
Yes
| approved | No | S5‑166216 | |||
S5‑166217 | pCR 28.302 - Add operations for scenario 1 | Nokia Networks | pCR | No |
No
| withdrawn | Yes | |||||
S5‑166454 | Draft TR 28.302 | Nokia | draft TR | 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‑166028 | Minutes of Study on OAM support for assessment of energy efficiency in mobile access networks | Rapporteur (Orange) | report | Yes |
Yes
| noted | No | |||
S5‑166043 | LS from ETSI TC EE to 3GPP SA5 on Energy Efficiency in Mobile Networks | ETSI TC EE | LS in | Yes |
Yes
| noted | No | |||||
S5‑166070 | pCR 32.856 Proposed text for clause 4 – Update some support status and add title to tables | ORANGE | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑166071 | pCR 32.856 proposed text for clause 4.4.3.3 Determination of coverage area | ORANGE | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑166072 | pCR 32.856 proposed text for clause 4.6 Assessment report | ORANGE | pCR | Approval | Yes |
Yes
| revised | No | S5‑166331 | |||
S5‑166331 | pCR 32.856 proposed text for clause 4.6 Assessment report | ORANGE | pCR | Approval | Yes |
Yes
| approved | No | S5‑166072 | |||
S5‑166102 | pCR 32.856 Proposed text for clause 4.7 Conclusion | ORANGE | pCR | Approval | Yes |
Yes
| revised | No | S5‑166347 | |||
S5‑166347 | pCR 32.856 Proposed text for clause 4.7 Conclusion | ORANGE | pCR | Approval | Yes |
Yes
| approved | No | S5‑166102 | |||
S5‑166114 | pCR 32.856 Proposed text for clause 5.2 Analysis of control-monitoring information | ORANGE, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑166348 | |||
S5‑166348 | pCR 32.856 Proposed text for clause 5.2 Analysis of control-monitoring information | ORANGE, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑166114 | |||
S5‑166115 | pCR 32.856 Proposed text for clause 5.3 Potential use cases | ORANGE, Deutsche Telekom, Huawei, Vodafone | pCR | Approval | Yes |
Yes
| revised | No | S5‑166349 | |||
S5‑166349 | pCR 32.856 Proposed text for clause 5.3 Potential use cases | ORANGE, Deutsche Telekom, Huawei, Vodafone,Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑166115 | |||
S5‑166116 | pCR 32.856 Proposed text for clause 5.4 Potential requirements | ORANGE | pCR | Approval | Yes |
Yes
| revised | No | S5‑166350 | |||
S5‑166350 | pCR 32.856 Proposed text for clause 5.4 Potential requirements | ORANGE | pCR | Approval | Yes |
Yes
| approved | No | S5‑166116 | |||
S5‑166117 | LS on ES 202 336-12 – Comments on Figure 1 and clarification needed on potential use case | ORANGE | LS out | Approval | Yes |
Yes
| revised | No | S5‑166351 | |||
S5‑166351 | LS on ES 202 336-12 – Comments on Figure 1 and clarification needed on potential use case | ORANGE | LS out | Approval | Yes |
Yes
| revised | No | S5‑166477 | S5‑166117 | ||
S5‑166477 | LS on ES 202 336-12 – Comments on Figure 1 and clarification needed on potential use case | ORANGE | LS out | Approval | Yes |
Yes
| approved | No | S5‑166351 | |||
S5‑166252 | LS on seeking collaboration on draft Recommendation “Energy efficiency Metrics and measurement methodology for 5G solutions | ITU-T | LS in | Yes |
Yes
| postponed | No | |||||
S5‑166407 | Presentation of draft TR 32.856 to SA for Information | ORANGE | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S5‑166436 | Draft TR 32.856 | ORANGE | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.2 | Study on OAM aspects of SON for AAS-based deployments | S5‑166029 | Minutes for Study on OAM aspects of SON for AAS-based deployments | Rapporteur (Nokia Networks) | report | Yes |
Yes
| noted | No | |||
S5‑166118 | pCR to TR 32.865 Cell splitting correction | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑166352 | pCR to TR 32.865 Cell splitting correction | Cisco Systems Inc. | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑166119 | pCR to TR 32.865 Management of SP-Cells | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑166353 | |||
S5‑166353 | pCR to TR 32.865 Management of SP-Cells | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑166119 | |||
S5‑166146 | Update the description of architecture options for TR 32.865 | Nokia Networks Oy | pCR | Yes |
Yes
| revised | No | S5‑166183 | ||||
S5‑166183 | pCR for TR 32.865 Update description of potential architecture options | Nokia Networks Oy | pCR | Approval | Yes |
Yes
| revised | No | S5‑166354 | S5‑166146 | ||
S5‑166354 | pCR for TR 32.865 Update description of potential architecture options | Nokia Networks Oy | pCR | Approval | Yes |
Yes
| approved | No | S5‑166183 | |||
S5‑166185 | pCR for TR 32.865 update clause of Conclusion and Recommendations | Nokia Networks Oy | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑166186 | Presentation TR 32.865 to SA for information | Nokia Networks Oy | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
S5‑166438 | Draft TR 32.865 | Nokia | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
S5‑166478 | Revised WID OAM aspects of SON for AAS | Nokia | WID revised | Agreement | Yes |
Yes
| revised | No | S5‑166480 | |||
S5‑166480 | Revised WID OAM aspects of SON for AAS | Nokia | WID revised | Agreement | Yes |
Yes
| agreed | No | S5‑166478 | |||
6.5.3 | Study on Implementation for the Partitioning of Itf-N | S5‑166021 | Minutes for Study on Implementation for the Partitioning of Itf-N | Rapporteur(China Mobile) | report | Yes |
Yes
| noted | No | |||
S5‑166104 | pCR TR 32.880 Comparative analysis of protocols on complexity and performance | China Mobile Com. Corporation | pCR | Yes |
Yes
| approved | No | |||||
S5‑166439 | Draft TR 32.880 | China Mobile | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.4 | Study on Management and Orchestration Architecture of Next Generation Network and Service | S5‑166020 | Minutes for Study on Management and Orchestration Architecture of Next Generation Network and Service | Rapporteur (Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑166147 | pCR TR 28.800 Add terminologies for management and orchestration of network function and resource | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑166355 | |||
S5‑166355 | pCR TR 28.800 Add terminologies for management and orchestration of network function and resource | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑166437 | S5‑166147 | ||
S5‑166437 | pCR TR 28.800 Add terminologies for management and orchestration of network function and resource | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑166441 | S5‑166355 | ||
S5‑166441 | pCR TR 28.800 Add terminologies for management and orchestration of network function and resource | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑166437 | |||
S5‑166171 | pCR TR 28.800 Add use case for management support of UDM | Huawei Technologies | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑166356 | pCR TR 28.800 Add use case for management support of UDM | Huawei Technologies | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑166172 | pCR TR 28 800 Add management architecture use case | Huawei Technologies | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑166184 | pCR TR 28.800 – Model of roles, use cases and architecture for network slice management | ORANGE | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑166472 | Draft TR 28.800 | Huawei | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.5 | Study on Management and Orchestration of Network Slicing | S5‑166030 | Minutes for Study on Management and Orchestration of Network Slicing | Rapporteur (Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑166148 | pCR TR 28.801 Add use case for service request for a slice instance | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑166375 | |||
S5‑166375 | pCR TR 28.801 Add use case for service request for a slice instance | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑166432 | S5‑166148 | ||
S5‑166432 | pCR TR 28.801 Add use case for service request for a slice instance | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑166442 | S5‑166375 | ||
S5‑166442 | pCR TR 28.801 Add use case for service request for a slice instance | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑166432 | |||
S5‑166149 | pCR TR 28.801 Add network slice sharing use case | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166376 | |||
S5‑166376 | pCR TR 28.801 Add network slice sharing use case | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166443 | S5‑166149 | ||
S5‑166443 | pCR TR 28.801 Add network slice sharing use case | Huawei Technologies, Ericsson | pCR | Approval | No |
Yes
| left for email approval | No | S5‑166376 | |||
S5‑166150 | pCR TR 28.801 Adding use case and requirements for E2E network slice supporting end user services | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑166377 | |||
S5‑166377 | pCR TR 28.801 Adding use case and requirements for E2E network slice supporting end user services | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑166444 | S5‑166150 | ||
S5‑166444 | pCR TR 28.801 Adding use case and requirements for E2E network slice supporting end user services | Huawei Technologies | pCR | Approval | Yes |
Yes
| approved | No | S5‑166377 | |||
S5‑166151 | pCR TR 28.801 Adding management support use case for slice selection | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑166152 | pCR TR 28.801 Add use case for policy configuration | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑166378 | |||
S5‑166378 | pCR TR 28.801 Add use case for policy configuration | Huawei Technologies | pCR | Approval | Yes |
Yes
| noted | No | S5‑166152 | |||
S5‑166153 | pCR TR 28.801 Add requirements and use case for informing network slice instance change | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑166370 | pCR TR 28.801 Add requirements and use case for informing network slice instance change | Huawei Technologies, Ericsson | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑166154 | pCR TR 28.801 Add requirements and update use case for creating a network slice instance | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166371 | |||
S5‑166371 | pCR TR 28.801 Add requirements and update use case for creating a network slice instance | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166445 | S5‑166154 | ||
S5‑166445 | pCR TR 28.801 Add requirements and update use case for creating a network slice instance | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑166371 | |||
S5‑166155 | pCR TR 28.801 Add requirements and update use case for modifying a network slice instance | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166373 | |||
S5‑166373 | pCR TR 28.801 Add requirements and update use case for modifying a network slice instance | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166412 | S5‑166155 | ||
S5‑166412 | pCR TR 28.801 Add requirements and update use case for modifying a network slice instance | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166446 | S5‑166373 | ||
S5‑166446 | pCR TR 28.801 Add requirements and update use case for modifying a network slice instance | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166468 | S5‑166412 | ||
S5‑166468 | pCR TR 28.801 Add requirements and update use case for modifying a network slice instance | Huawei Technologies, Ericsson | pCR | Approval | No |
Yes
| left for email approval | No | S5‑166446 | |||
S5‑166156 | pCR TR 28.801 Add requirements and update use case for terminating a network slice instance | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166374 | |||
S5‑166374 | pCR TR 28.801 Add requirements and update use case for terminating a network slice instance | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166447 | S5‑166156 | ||
S5‑166447 | pCR TR 28.801 Add requirements and update use case for terminating a network slice instance | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166469 | S5‑166374 | ||
S5‑166469 | pCR TR 28.801 Add requirements and update use case for terminating a network slice instance | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑166447 | |||
S5‑166157 | pCR TR 28.801 Add general requirements for network slice lifecycle management | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166379 | |||
S5‑166379 | pCR TR 28.801 Add general requirements for network slice lifecycle management | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166448 | S5‑166157 | ||
S5‑166448 | pCR TR 28.801 Add general requirements for network slice lifecycle management | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑166379 | |||
S5‑166158 | pCR TR 28.801 Network slice type impact on network management system | Huawei Technologies | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑166381 | pCR TR 28.801 Network slice type impact on network management system | Huawei Technologies | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑166159 | pCR TR 28.801 Possible network slice creation methods with shared NFs | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑166383 | |||
S5‑166383 | pCR TR 28.801 Possible network slice creation methods with shared NFs | Huawei Technologies | pCR | Approval | Yes |
Yes
| noted | No | S5‑166159 | |||
S5‑166160 | pCR TR 28.801 Possible network slice creation methods without shared NFs | Huawei Technologies | pCR | Approval | Yes |
Yes
| revised | No | S5‑166382 | |||
S5‑166382 | pCR TR 28.801 Possible network slice creation methods without shared NFs | Huawei Technologies | pCR | Approval | Yes |
Yes
| noted | No | S5‑166160 | |||
S5‑166161 | pCR TR 28.801 Update on the Network slice instance lifecycle | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166359 | |||
S5‑166359 | pCR TR 28.801 Update on the Network slice instance lifecycle | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S5‑166450 | S5‑166161 | ||
S5‑166450 | pCR TR 28.801 Update on the Network slice instance lifecycle | Huawei Technologies, Ericsson | pCR | Approval | Yes |
Yes
| approved | No | S5‑166359 | |||
S5‑166195 | pCR 28.801 add Introduction chapter 6 | Ericsson LM | pCR | Yes |
Yes
| revised | No | S5‑166357 | ||||
S5‑166357 | pCR 28.801 add Introduction chapter 6 | Ericsson LM | pCR | - | Yes |
Yes
| revised | No | S5‑166451 | S5‑166195 | ||
S5‑166451 | pCR 28.801 add Introduction chapter 6 | Ericsson LM | pCR | - | Yes |
Yes
| approved | No | S5‑166357 | |||
S5‑166197 | pCR TR 28.801 Terminology update | Ericsson LM,Huawei | pCR | Yes |
Yes
| revised | No | S5‑166358 | ||||
S5‑166358 | pCR TR 28.801 Terminology update | Ericsson LM,Huawei | pCR | - | Yes |
Yes
| revised | No | S5‑166453 | S5‑166197 | ||
S5‑166453 | pCR TR 28.801 Terminology update | Ericsson LM,Huawei | pCR | - | Yes |
Yes
| revised | No | S5‑166470 | S5‑166358 | ||
S5‑166470 | pCR TR 28.801 Terminology update | Ericsson LM,Huawei | pCR | - | No |
Yes
| left for email approval | No | S5‑166453 | |||
S5‑166208 | pCR 28.801 Use case and Requirement Monitor performance of a network slice instance | Ericsson LM, Huawei | pCR | Yes |
Yes
| revised | No | S5‑166360 | ||||
S5‑166360 | pCR 28.801 Use case and Requirement Monitor performance of a network slice instance | Ericsson LM, Huawei | pCR | - | Yes |
Yes
| noted | No | S5‑166208 | |||
S5‑166209 | pCR 28.801 Use case and Requirement Supervise network slice instance | Ericsson LM,Huawei | pCR | Yes |
Yes
| revised | No | S5‑166365 | ||||
S5‑166365 | pCR 28.801 Use case and Requirement Supervise network slice instance | Ericsson LM,Huawei | pCR | - | Yes |
Yes
| noted | No | S5‑166209 | |||
S5‑166210 | pCR 28.801 Use case and Requirement Uplift network slice instance | Ericsson LM | pCR | Yes |
Yes
| noted | No | |||||
S5‑166368 | pCR 28.801 Use case and Requirement Uplift network slice instance | Ericsson LM | pCR | - | No |
No
| withdrawn | Yes | ||||
S5‑166211 | pCR 28.801 Use case and Requirements for Prepare introduction of new feature in a network slice instance | Ericsson LM | pCR | Yes |
Yes
| noted | No | |||||
S5‑166369 | pCR 28.801 Use case and Requirements for Prepare introduction of new feature in a network slice instance | Ericsson LM | pCR | - | No |
No
| withdrawn | Yes | ||||
S5‑166212 | pCR TR 28.801 Add general requirements for network slice subnet lifecycle management | Ericsson LM | pCR | Yes |
Yes
| noted | No | |||||
S5‑166380 | pCR TR 28.801 Add general requirements for network slice subnet lifecycle management | Ericsson LM | pCR | - | No |
No
| withdrawn | Yes | ||||
S5‑166256 | Discussion sequence proposal for agenda point 6.5.5 | Ericsson LM | discussion | Yes |
Yes
| noted | No | |||||
S5‑166449 | LS to SA2 on clarification of clarification of network slice template | Ericsson | LS out | Approval | Yes |
Yes
| revised | No | S5‑166479 | |||
S5‑166479 | LS to SA2 on clarification of clarification of network slice template | Ericsson | LS out | Approval | Yes |
Yes
| approved | No | S5‑166449 | |||
S5‑166455 | Draft TR 28.801 | Ericsson | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.6 | Study on management aspects of next generation network architecture and features | S5‑166031 | Minutes for Study on management aspects of next generation network architecture and features | Rapporteur(Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑166176 | pCR TR 28.802 Add use case for supporting cric management case | Huawei Technologies | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑166387 | pCR TR 28.802 Add use case for supporting cric management case | Huawei Technologies | pCR | Approval | No |
No
| withdrawn | Yes | ||||
S5‑166187 | pCR for TR 28.802 Add a use case to support management of Service Hosting Environment | Nokia Networks Oy | pCR | Approval | Yes |
No
| withdrawn | Yes | ||||
S5‑166188 | pCR for TR 28.802 Add use cases to support management for New RAN architecture | Nokia Networks Oy | pCR | Approval | Yes |
Yes
| revised | No | S5‑166398 | |||
S5‑166398 | pCR for TR 28.802 Add use cases to support management for New RAN architecture | Nokia Networks Oy | pCR | Approval | Yes |
Yes
| revised | No | S5‑166456 | S5‑166188 | ||
S5‑166456 | pCR for TR 28.802 Add use cases to support management for New RAN architecture | Nokia Networks Oy | pCR | Approval | No |
Yes
| left for email approval | No | S5‑166398 | |||
S5‑166200 | Discussion on Service Performance Reporting (SPR) mechanism in NR | Ericsson | discussion | Yes |
Yes
| noted | No | |||||
S5‑166201 | End user service PM information via the UE | Ericsson | pCR | Yes |
Yes
| revised | No | S5‑166403 | ||||
S5‑166403 | End user service PM information via the UE | Ericsson | pCR | - | Yes |
Yes
| revised | No | S5‑166457 | S5‑166201 | ||
S5‑166457 | End user service PM information via the UE | Ericsson | pCR | - | Yes |
Yes
| approved | No | S5‑166403 | |||
S5‑166458 | Draft TR 28.802 | Nokia | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
6.5.7 | Study on Management aspects of selected IoT-related features | S5‑166038 | Minutes of Study on Management aspects of selected IoT-related features | Rapporteur (Cisco) | report | Yes |
Yes
| noted | No | |||
S5‑166112 | Discussion Paper on possible IoT Management Use Cases | Cisco Systems Inc. | discussion | Discussion | Yes |
Yes
| noted | No | ||||
S5‑166113 | pCR to TR 32.857 Scope section | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| revised | No | S5‑166404 | |||
S5‑166404 | pCR to TR 32.857 Scope section | Cisco Systems Inc. | pCR | Approval | Yes |
Yes
| approved | No | S5‑166113 | |||
S5‑166459 | Draft TR 32.857 | Cisco | draft TR | discussion | No |
Yes
| left for email approval | No | ||||
6.5.8 | Study on a RESTful HTTP-based Solution Set | S5‑166039 | Minutes of Study on a RESTful HTTP-based Solution Set | Rapporteur (Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑166218 | Skeleton for 32.866 | Nokia Networks | draft TR | Yes |
Yes
| approved | No | |||||
6.5.9 | Study on management aspects of virtualized network functions that are part of the NR | S5‑166040 | Minutes of Study on management aspects of virtualized network functions that are part of the NR | Rapporteur (Intel) | report | Yes |
Yes
| noted | No | |||
S5‑166134 | Draft TR 32.864 Skeleton proposal | Intel Corporation (UK) Ltd | draft TR | Approval | Yes |
Yes
| revised | No | S5‑166405 | |||
S5‑166405 | Draft TR 32.864 Skeleton proposal | Intel Corporation (UK) Ltd | draft TR | Approval | Yes |
Yes
| approved | No | S5‑166134 | |||
S5‑166135 | pCR TR 32.864 adding introduction and scope | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑166406 | |||
S5‑166406 | pCR TR 32.864 adding introduction and scope | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑166460 | S5‑166135 | ||
S5‑166460 | pCR TR 32.864 adding introduction and scope | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑166406 | |||
S5‑166461 | Draft TR 32.864 | Intel | draft TR | discussion | No |
Yes
| left for email approval | No | ||||
7 | Charging |   | ||||||||||
7.1 | Charging Plenary | S5‑166008 | CH Agenda and Time Plan | CH SWG Chair | agenda | Yes |
Yes
| approved | No | |||
S5‑166009 | CH Executive Report from THIS Meeting | CH SWG Chair | report | Yes |
Yes
| noted | No | |||||
S5‑166041 | Resubmitted LS from SA2 to SA5-CH on implication on charging from eFMSS | S2-164279 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑166048 | LS from SA2 to SA5 on Informing charging system about 3GPP PS Data off status | S2-165432 | LS in | Yes |
Yes
| noted | No | |||||
S5‑166121 | LS from IETF to SA5 on clarification on RFC 4006 for Diameter Base Protocol | IETF DIME WG | LS in | Yes |
Yes
| noted | No | |||||
S5‑166126 | LS from SA6 to SA5 on Charging for Mission Critical Services | S6-161256 | LS in | Yes |
Yes
| postponed | No | |||||
S5‑166219 | LS reply to LS on Informing charging system about 3GPP PS Data off status | Huawei Technologies | LS out | Yes |
Yes
| revised | No | S5‑166299 | ||||
S5‑166299 | LS reply to LS on Informing charging system about 3GPP PS Data off status | Huawei Technologies | LS out | - | Yes |
Yes
| agreed | No | S5‑166219 | |||
7.2 | New Charging Work Item proposals | S5‑166221 | New WID Charging for SMS via T4 | Nokia, Alcatel-Lucent Shanghai Bell | WID new | Agreement | Yes |
Yes
| revised | No | S5‑166285 | |
S5‑166285 | New WID Charging for SMS via T4 | Nokia, Alcatel-Lucent Shanghai Bell | WID new | Agreement | Yes |
Yes
| revised | No | S5‑166397 | S5‑166221 | ||
S5‑166397 | New WID Charging for SMS via T4 | Nokia, Alcatel-Lucent Shanghai Bell | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑166285 | |||
S5‑166222 | New WID Charging aspects for Diameter Base Protocol Specification Update | Nokia, Alcatel-Lucent Shanghai Bell | WID new | Agreement | Yes |
Yes
| revised | No | S5‑166286 | |||
S5‑166286 | New WID Charging aspects for Diameter Base Protocol Specification Update | Nokia, Alcatel-Lucent Shanghai Bell | WID new | Agreement | Yes |
Yes
| agreed | No | S5‑166222 | |||
S5‑166232 | Revised WID on Charging Aspects of S8 Home Routing Architecture for VoLTE | China Mobile Com. Corporation | WID revised | Agreement | Yes |
Yes
| revised | No | S5‑166287 | |||
S5‑166287 | Revised WID on Charging Aspects of S8 Home Routing Architecture for VoLTE | China Mobile Com. Corporation | WID revised | Agreement | Yes |
YesThis WID will go to SA for approval.
| agreed | No | S5‑166232 | |||
S5‑166290 | New Work Item on Charging aspects for 3GPP PS Data off | Huawei Technologies | WID new | Agreement | Yes |
Yes
| agreed | No | ||||
7.3 | Charging Maintenance and Rel-14 small Enhancements | S5‑166073 | Rel-14 CR 32.298 Correction on P-CSCF and IBCF for ATCF specific fields | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||
S5‑166074 | Rel-10 CR 32.298 Correction on OMR attributes per media in IMS Charging | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑166391 | |||
S5‑166391 | Rel-10 CR 32.298 Correction on OMR attributes per media in IMS Charging | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166074 | |||
S5‑166075 | Rel-11 CR 32.298 Correction on OMR attributes per media in IMS Charging | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑166392 | |||
S5‑166392 | Rel-11 CR 32.298 Correction on OMR attributes per media in IMS Charging | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166075 | |||
S5‑166076 | Rel-12 CR 32.298 Correction on OMR attributes per media in IMS Charging | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑166393 | |||
S5‑166393 | Rel-12 CR 32.298 Correction on OMR attributes per media in IMS Charging | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166076 | |||
S5‑166077 | Rel-13 CR 32.298 Correction on OMR attributes per media in IMS Charging | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑166394 | |||
S5‑166394 | Rel-13 CR 32.298 Correction on OMR attributes per media in IMS Charging | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166077 | |||
S5‑166078 | Rel-14 CR 32.298 Correction on OMR attributes per media in IMS Charging | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166079 | Rel-9 CR 32.260 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166080 | Rel-10 CR 32.260 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166081 | Rel-11 CR 32.260 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166082 | Rel-12 CR 32.260 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166083 | Rel-13 CR 32.260 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166084 | Rel-9 CR 32.299 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑166344 | |||
S5‑166344 | Rel-9 CR 32.299 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166084 | |||
S5‑166085 | Rel-10 CR 32.299 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑166345 | |||
S5‑166345 | Rel-10 CR 32.299 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166085 | |||
S5‑166086 | Rel-11 CR 32.299 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑166346 | |||
S5‑166346 | Rel-11 CR 32.299 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166086 | |||
S5‑166087 | Rel-12 CR 32.299 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑166388 | |||
S5‑166388 | Rel-12 CR 32.299 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166087 | |||
S5‑166088 | Rel-13 CR 32.299 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑166389 | |||
S5‑166389 | Rel-13 CR 32.299 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166088 | |||
S5‑166089 | Rel-14 CR 32.299 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑166390 | |||
S5‑166390 | Rel-14 CR 32.299 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166089 | |||
S5‑166090 | Rel-9 CR 32.298 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166091 | Rel-10 CR 32.298 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166092 | Rel-11 CR 32.298 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166093 | Rel-12 CR 32.298 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166094 | Rel-13 CR 32.298 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166095 | Rel-14 CR 32.298 Correction on Requested Party Address for Emergency IMS session | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166096 | Rel-13 CR 32.298 Correction on ASN.1 in PS domain CDRs | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑166338 | |||
S5‑166338 | Rel-13 CR 32.298 Correction on ASN.1 in PS domain CDRs | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166096 | |||
S5‑166097 | Rel-14 CR 32.298 Correction on ASN.1 in PS domain CDRs | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑166339 | |||
S5‑166339 | Rel-14 CR 32.298 Correction on ASN.1 in PS domain CDRs | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166097 | |||
S5‑166098 | Rel-14 CR 32.240 Correction on NOTE related to Inter Operator Identification (IOI) | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166099 | Rel-13 CR 32.299 Correction on duplicate values for Change-Condition | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166100 | Rel-14 CR 32.299 Correction on duplicate values for Change-Condition | Nokia, Alcatel-Lucent Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑166166 | Discussion on volume based charging of VoLTE | China Mobile Com. Corporation | discussion | Yes |
Yes
| noted | No | |||||
S5‑166230 | Discussion Paper on the charging enhancement for 3GPP PS Data off | Huawei Technologies | discussion | Yes |
Yes
| noted | No | |||||
S5‑166231 | Rel-14 CR 32.251 Charging enhancement for 3GPP PS Data off | Huawei Technologies | CR | Yes |
Yes
| not pursued | No | |||||
S5‑166234 | Implication on charging from eFMSS | China Telecommunications | discussion | Approval | Yes |
Yes
| noted | No | ||||
S5‑166239 | Rel-14 CR 32.260 Not possible to record RAT change with the time in P-CSCF | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑166302 | |||
S5‑166302 | Rel-14 CR 32.260 Correction on Access Network Info change with the time in offline | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑166239 | |||
S5‑166240 | Rel-14 CR 32.299 Not possible to record RAT change with the time in P-CSCF | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑166303 | |||
S5‑166303 | Rel-14 CR 32.299 Correction on Access Network Info change with the time in offline | Ericsson LM | CR | Agreement | Yes |
Yes
| agreed | No | S5‑166240 | |||
S5‑166242 | Rel-14 CR 32.260 AS serving the forwarding party | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑166332 | |||
S5‑166332 | Rel-14 CR 32.260 Correction on Role-Of-node for AS serving the forwarding | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑166242 | |||
S5‑166243 | Rel-14 CR 32.299 AS serving the forwarding party | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑166333 | |||
S5‑166333 | Rel-14 CR 32.299 Correction on Role-Of-node for AS serving the forwarding party | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑166243 | |||
S5‑166244 | Rel-14 CR 32.260 Correction of Number portability Routing information | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑166334 | |||
S5‑166334 | Rel-14 CR 32.260 Correction of Number portability Routing information | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑166244 | |||
S5‑166245 | Rel-14 CR 32.299 Correction of Number-Portability-Routing-Information | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑166335 | |||
S5‑166335 | Rel-14 CR 32.299 Correction of Number-Portability-Routing-Information | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑166245 | |||
S5‑166246 | Rel-14 CR 32.274 Correction SMS Delivery handling | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑166340 | |||
S5‑166340 | Rel-14 CR 32.274 Correction SMS Delivery handling | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑166246 | |||
S5‑166247 | Rel-14 CR 32.298 Missing value in SM Message Type | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑166341 | |||
S5‑166341 | Rel-14 CR 32.298 Correction of value in SM Message Type | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑166247 | |||
S5‑166248 | Rel-14 CR 32.299 Called-Party-Address and Requested-Party-Address usage unclear | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑166336 | |||
S5‑166336 | Rel-14 CR 32.299 Correction of Called-Party-Address and Requested-Party-Address | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑166248 | |||
S5‑166249 | Rel-14 CR 32.299 Correction of Change-Time to include Access Transfer Time | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑166337 | |||
S5‑166337 | Rel-14 CR 32.299 Correction of Change-Time to include Access Transfer Time | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑166249 | |||
S5‑166251 | Use of User-Equipment-Info for IMEI in 32.299 | Ericsson LM | other | Discussion | Yes |
Yes
| noted | No | ||||
S5‑166284 | IMS Offline Charging Improvement – Use Cases | AT&T | other | Presentation | Yes |
Yes
| noted | No | ||||
S5‑166395 | Latest draft TR 32.870 “study on forward compatibility Diameter Charging applications” | Nokia | draft TR | Approval | No |
Yes
| left for email approval | No | ||||
7.4 | Rel-14 Charging |   | ||||||||||
7.4.1 | Resource optimization for PS domain online charging sessions | S5‑166241 | Rel-14 draftCR TS32.251 General Description for Gy session optimization | Ericsson LM | draftCR | Approval | Yes |
Yes
| revised | No | S5‑166288 | |
S5‑166288 | Rel-14 draftCR TS32.251 General Description for Gy session optimization | Ericsson LM | draftCR | Approval | Yes |
Yes
| approved | No | S5‑166241 | |||
S5‑166250 | Rel-14 TS32.251 Midsession pausing for session optimization | Ericsson LM | other | Agreement | Yes |
Yes
| noted | No | ||||
S5‑166289 | Rel-14 CR 32.251 Introduction of Gy session optimization based on unused quota timer | Ericsson LM | 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‑166226 | Rel-14 CR 32.277 Correction on the ProSe offline Charging | Huawei Technologies | CR | Yes |
Yes
| revised | No | S5‑166291 | ||
S5‑166291 | Rel-14 CR 32.277 Correction on the ProSe offline Charging | Huawei Technologies | CR | - | Yes |
Yes
| agreed | No | S5‑166226 | |||
S5‑166227 | Rel-14 CR 32.277 Addition of session based charging for ProSe one-to-one communication | Huawei Technologies | CR | Yes |
Yes
| revised | No | S5‑166293 | ||||
S5‑166293 | Rel-14 CR 32.277 Addition of session based charging for ProSe one-to-one communication | Huawei Technologies | CR | - | Yes |
Yes
| agreed | No | S5‑166227 | |||
S5‑166228 | Rel-14 CR 32.277 Addtion of the triggers for ProSe charging | Huawei Technologies | CR | Yes |
Yes
| revised | No | S5‑166292 | ||||
S5‑166292 | Rel-14 CR 32.277 Addtion of the triggers for ProSe charging | Huawei Technologies | CR | - | Yes |
Yes
| agreed | No | S5‑166228 | |||
S5‑166229 | Rel-14 CR 32.277 Addition of Message flow for ProSe Direct Discovery for Public Safety use | Huawei Tech.(UK) Co., Ltd | CR | Yes |
Yes
| revised | No | S5‑166294 | ||||
S5‑166294 | Rel-14 CR 32.277 Addition of Message flow for ProSe Direct Discovery for Public Safety use | Huawei Tech.(UK) Co., Ltd | CR | - | Yes |
Yes
| agreed | No | S5‑166229 | |||
7.4.4 | Charging Aspects of S8 Home Routing Architecture for VoLTE | S5‑166167 | Rel-13 CR 32.260 Add charging support for roaming architecture for voice over IMS with home routed traffic | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑166295 | |
S5‑166295 | Rel-14 CR 32.260 Add charging support for roaming architecture for voice over IMS with home routed traffic | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑166167 | |||
S5‑166223 | Rel-13 CR 32.260 Clarification on location of P-CSCF and CDF in message flows | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑166296 | |||
S5‑166296 | Rel-14 CR 32.260 Clarification on location of P-CSCF and CDF in message flows | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑166223 | |||
7.4.5 | Charging Aspects of Improvements of Awareness of User Location Change (AULC) | S5‑166224 | Rel-14 CR 32.251 Addition of charging support for Mulitiple PRAs | Huawei Technologies | CR | Yes |
Yes
| revised | No | S5‑166300 | ||
S5‑166300 | Rel-14 CR 32.251 Addition of charging support for Mulitiple PRAs | Huawei Technologies | CR | - | Yes |
Yes
| agreed | No | S5‑166224 | |||
S5‑166225 | Rel-14 CR 32.298 Addition of charging support for Mulitiple PRAs | Huawei Technologies | CR | Yes |
Yes
| revised | No | S5‑166301 | ||||
S5‑166301 | Rel-14 CR 32.298 Addition of charging support for Mulitiple PRAs | Huawei Technologies | CR | - | Yes |
Yes
| agreed | No | S5‑166225 | |||
7.5 | Charging Studies |   | ||||||||||
7.5.1 | Study on Overload Control for Diameter Charging Applications |   | ||||||||||
7.5.2 | Study on forward compatibility for 3GPP Diameter Charging Applications | S5‑166233 | Rel-14 pCR 32.870 skeleton study on forward compatibility Diameter Charging applications | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||
S5‑166235 | Rel-14 pCR TR 32.870 Study 3GPP Diameter Charging Applications - Scope and References | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑166342 | |||
S5‑166342 | Rel-14 pCR TR 32.870 Study 3GPP Diameter Charging Applications - Scope and References | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| agreed | No | S5‑166235 | |||
S5‑166236 | Rel-14 pCR TR 32.870 Study 3GPP Diameter Charging Applications - Clause 3 | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑166237 | Rel-14 pCR TR 32.870 Study 3GPP Diameter Charging Applications - Clause 4.1 | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑166343 | |||
S5‑166343 | Rel-14 pCR TR 32.870 Study 3GPP Diameter Charging Applications - Clause 4.1 | Nokia, Alcatel-Lucent Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑166237 | |||
8 | Any Other Business | S5‑166238 | Proposed Topics for Joint SA5/CT4/CT3 Discussion | Nokia | other | Decision | Yes |
Yes
| revised | No | S5‑166297 | |
S5‑166297 | Joint SA5/CT4/CT3 Discussion | SA5 SWG Chair | other | Decision | Yes |
Yes
| endorsed | No | S5‑166238 | |||
S5‑166298 | Joint SA5/CT4/CT3 Discussion – Supported Features | SA5 SWG Chair | other | Endorsement | Yes |
Yes
| endorsed | No | ||||
9 | Closing of the meeting |   |