Tdoc List
2019-11-25 11:54
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‑197000 | Agenda | WG Chairman | agenda | Yes |
Yes
| approved | No | |||
3 | IPR and legal declaration | S5‑197001 | IPR and legal declaration | WG Chairman | other | Yes |
Yes
| noted | No | |||
4 | Meetings and activities reports |   | ||||||||||
4.1 | Last SA5 meeting report | S5‑197002 | Report from last SA5 meeting | MCC | report | Yes |
Yes
| approved | No | |||
4.2 | Last SA meeting report | S5‑197015 | SA5 status report at last SA meeting | WG Chairman | report | No |
Yes
| withdrawn | Yes | |||
S5‑197016 | SA5 results at last SA meeting | WG Chairman | report | No |
Yes
| withdrawn | Yes | |||||
4.3 | Inter-organizational reports |   | ||||||||||
5 | Cross-SWG issues |   | ||||||||||
5.1 | Administrative issues at SA5 level | S5‑197003 | Leaders meeting agenda | WG Chairman | agenda | Yes |
YesChairman presented the contribution.
Ericsson pointed out SA5 need a instruction to handle the Publication of separate code file for the OpenAPI problem.
Nokia commented how to handle the code in SA5, it need to check with MCC to decide the solution for SA5.
Orange pointed out CT WGs using ETSI forge to store the code and Orange has contribution on how to capture the code file, however the situation is difference for SA5.
Chairman suggested to check offline with MCC about the procedure for this issue.
Chairman pointed out that the Conditional CRs which agreed in last meeting need to be concluded.
| noted | No | |||
S5‑197004 | Leaders meeting minutes | WG Chairman | report | Yes |
Yes
| noted | No | |||||
S5‑197005 | SA5 Working Procedures | WG Chairman | other | Yes |
Yes
| noted | No | |||||
S5‑197006 | SA5 Meeting Facility Requirements | WG Vice Chair (Nokia) | other | Yes |
Yes
| approved | No | |||||
S5‑197007 | Process for management of draft TSs/TRs | WG Chairman | other | Yes |
Yes
| noted | No | |||||
S5‑197008 | CR Quality Check | MCC | other | Yes |
Yes
| noted | No | |||||
S5‑197009 | Status of email approvals | WG Chairman | other | No |
No
| reserved | No | |||||
5.2 | Technical issues at SA5 level |   | ||||||||||
5.3 | Liaison statements at SA5 level | S5‑197139 | Resubmitted reply LS from SA6 ccSA5 on 3GPP SA6 Study on Edge Computing | S6-191841 | LS in | Yes |
Yes
| noted | No | |||
S5‑197149 | Reply LS ccSA5 on NG.116 GST publication and cooperation with 3GPP SA WG2 | S2-1910807 | LS in | Yes |
YesNokia: need to clarify how NEST make available by SA2 with this working assumption.
Ericsson: The diagram shows that how the information translated to SA2Agreed to have a reply for this LS.
Huawei: has 2 related LSs (S5-196891 and S5-196868) in SA5#127, but S5-196868 was not sent to SA2, maybe SA5 could re-use S5-196868 as basis to reply.
Vice Chair(Maryse): Charing group is also instereting with this issue.
Chairman concluded that SA5 decide to reply this LS on Wednesday.
| replied to | No | |||||
S5‑197540 | Reply to: Reply LS ccSA5 on NG.116 GST publication and cooperation with 3GPP SA WG2 | current meeting | LS out | approval | Yes |
Yes
| revised | No | S5‑197715 | |||
S5‑197715 | Reply to: Reply LS ccSA5 on NG.116 GST publication and cooperation with 3GPP SA WG2 | SA5 | LS out | approval | Yes |
Yes
| approved | No | S5‑197540 | |||
5.4 | SA5 meeting calendar | S5‑197010 | SA5 Meeting Calendar | WG Chairman | other | Yes |
Yes
| noted | No | |||
5.5 | Review of the Work Plan | S5‑197011 | 3GPP SA5 Work Plan | MCC | other | Yes |
Yes
| noted | No | |||
6 | OAM&P |   | ||||||||||
6.1 | OAM&P Plenary | S5‑197012 | Time Plan for OAM&P | WG Chairman | other | No |
YesNokia, Ericsson, Huawei, Intel, CMCC etc. commented that delegates can not attend the paralle meeting for the topics which they are instereted. The delegates got agreement finally.
| noted | No | |||
S5‑197013 | OAM Executive Report | WG Vice Chair (Huawei) | report | No |
Yes
| noted | No | |||||
S5‑197014 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | Yes |
YesVice Chair(Zou Lan) presented the action list for SA5, Zou Lan proposes to close 118.1.
Intel commented that the owner of 127.1 should be Huawei.
Vice Chair(Zou Lan) will update the owner of the action points.
| revised | No | S5‑197547 | ||||
S5‑197547 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | - | Yes |
Yes
| revised | No | S5‑197753 | S5‑197014 | ||
S5‑197753 | OAM&P SWG action list | WG Vice Chair (Huawei) | other | - | No |
Yes
| noted | No | S5‑197547 | |||
S5‑197141 | Resubmitted LS from ITU-T to SA5 on cooperation on methodology harmonization and REST-based network management framework (reply to 3GPPTSGSA5-S5-185553 and 3GPP TSG SA5 - S5-187340) | ITU-T SG2 | LS in | Yes |
YesChairman pointed out that SA5 could reply what SA5 knows.
| replied to | No | |||||
S5‑197541 | Reply to: Resubmitted LS from ITU-T to SA5 on cooperation on methodology harmonization and REST-based network management framework (reply to 3GPPTSGSA5-S5-185553 and 3GPP TSG SA5 - S5-187340) | SA5 | LS out | approval | No |
Yes
| email approval | No | ||||
S5‑197147 | Reply LS ccSA5 on LS on the IAB-indication to core network | S2-1910281 | LS in | Yes |
Yes
| noted | No | |||||
S5‑197148 | LS to SA5 on whether new 5QI needs for IAB OAM traffic | S2-1910347 | LS in | Yes |
YesHuawei commented that SA5 need some clarifications about what is OAM traffic types.
Intel: Clarify whether existing 5QI is sufficient. Check whether IAB has special requirements for OAM data to be transferred in real-time.
Nokia suggested that reply to SA2 only thank them for pointing out the problem, SA5 needs more time to analyse this issue.
| replied to | No | |||||
S5‑197542 | Reply to: LS to SA5 on whether new 5QI needs for IAB OAM traffic | Intel | LS out | approval | Yes |
Yes
| revised | No | S5‑197814 | |||
S5‑197814 | Reply to: LS to SA5 on whether new 5QI needs for IAB OAM traffic | SA5 | LS out | approval | Yes |
Yes
| approved | No | S5‑197542 | |||
S5‑197150 | Reply LS to SA5 on QoE Measurement Collection | S4-191234 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑197543 | Reply to: Reply LS to SA5 on QoE Measurement Collection | SA5 | LS out | approval | No |
Yes
| email approval | No | ||||
S5‑197151 | LS to SA5 on O-RAN – 3GPP Cooperation on Management Services | O-RAN | LS in | Yes |
YesNokia presented the LS and would like to reply this LS.
Ericsson commented that the bullet for gNB DU NRM is ambiguous. How consumer make use of ORAN DU spec and 3GPP spec DU?
Chairman reply that it's out of this LS and should be discussed offline
Intel: clarify the meaning of fileready..
Orange has a related LS out S5-197476.
Offline discussion.
| replied to | No | |||||
S5‑197237 | LS to SA5 on O-RAN – 3GPP Cooperation on Management Services | O-RAN Alliance | LS in | Yes |
YesEricsson pointed out that SA5 is positive for the issue described in this LS.
| replied to | No | |||||
S5‑197546 | Reply to: LS to SA5 on O-RAN – 3GPP Cooperation on Management Services | SA5 | LS out | approval | Yes |
Yes
| revised | No | S5‑197815 | |||
S5‑197815 | Reply to: LS to SA5 on O-RAN – 3GPP Cooperation on Management Services | SA5 | LS out | approval | Yes |
Yes
| revised | No | S5‑197839 | S5‑197546 | ||
S5‑197839 | Reply to: LS to SA5 on O-RAN – 3GPP Cooperation on Management Services | SA5 | LS out | approval | Yes |
Yes
| approved | No | S5‑197815 | |||
S5‑197285 | Overview of the 5G specification structure | HiSilicon Technologies Co. Ltd | other | Information | Yes |
YesEricsson suggested to take a look at 28.532 for the SA5 specification structure and need to add Trace specs
Chairman pointed out that SA5 needs some improvement about the structure.
Nokia commented that 28.632 is missing in Generic service.
Intel: 28.544 is removed.
Offline discussion.
| revised | No | S5‑197548 | |||
S5‑197548 | Overview of the 5G specification structure | HiSilicon Technologies Co. Ltd | other | Information | Yes |
Yes
| endorsed | No | S5‑197285 | |||
S5‑197287 | Potential Rel-17 SA5 OAM work area | HiSilicon Technologies Co. Ltd | discussion | Endorsement | Yes |
YesHuawei presented the contribution. SA5 should freeze the stage 1 in this meeting.
Samsung commented that eCOSLA should be restricted in R16.
Intel: what's the pricinple of potiental main focus aspects .
Ericsson: this issue should be discussed in SA and need to sync up the timeplan with SA2, or even sync stage1 with SA1 schedule.
Huawei: SA2 has already start R17 work, if SA5 still use the R16 WID, the work will be difficult. SA5 only has three R17 WIDs now.
Nokia: Does Huawei will take this to SA. Huawei(Zoulan): YES.
Nokia: the R-17 SA#85 prioritized items list is strong related with SA2, not for other SA WGs, SA5 also need to provide some information of SA5 to SA, such as add the related WID in SA2/RAN.
Chairman: it's hard to modify it by SA5 along, SA5 needs to contact with other SA WGs.
Intel: the other SA WGs need to involved into the discussion of the prioritized items, not only lead by SA2. SA5 also have some features need to be supported by other WGs. Intel agree that the contribution from Zoulan, SA5 needs our own contribution and take it to SA.
Chairman: SA5 starts this discussion very late, SA5 needs to find a smart way to propose SA5's proposals.
Ericssion: SA2 has started the discussion of the prioritize items, SA5 needs to do it also. SA5 needs to show what SA5 has already done and send contribution to SA.
Samsung: the prioritized items has been endorsed by SA. Without OAM group supports this, these WID can't not work.
Chairman: however there are not too many SA5 R17 WIDs.
Orange: a WID is not in the list of prioritized items.
Offline discussion.
| revised | No | S5‑197549 | |||
S5‑197549 | Potential Rel-17 SA5 OAM work area | HiSilicon Technologies Co. Ltd | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑197801 | S5‑197287 | ||
S5‑197801 | Potential Rel-17 SA5 OAM work area | HiSilicon Technologies Co. Ltd | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑197816 | S5‑197549 | ||
S5‑197816 | Potential Rel-17 SA5 OAM work area | HiSilicon Technologies Co. Ltd | discussion | Endorsement | Yes |
YesSA5 could accept to keep the information of this contribution for SA discussion.
Ericssion: if SA5 endorsed this Tdoc, is that means some companies could not say they don't want to proceed these WIDs in the list.
Huawei: it's better that SA5 has some contribution for Dec. SA meeting.
| noted | No | S5‑197801 | |||
S5‑197363 | SA5#128_agenda_with_Tdocs_sequence_proposal_OAM | SA5 Vice Chairman (Huawei) | other | Yes |
Yes
| noted | No | |||||
S5‑197476 | LS reply to LS on O-RAN – 3GPP Cooperation on Management Services | SA5 | LS out | Approval | Yes |
YesEricsson: this LS could be used as the basis to reply S5-197151. How does SA5 collaborate with O-RAN?
E///, Nokia, Samsung, Intel would like to join the offline discussion and reply this LS.
| revised | No | S5‑197545 | |||
S5‑197545 | LS reply to LS on O-RAN – 3GPP Cooperation on Management Services | SA5 | LS out | Approval | Yes |
Yes
| email approval | No | S5‑197476 | |||
S5‑197479 | LS on Application Architecture for enabling Edge Applications | S6-192399 | LS in | discussion | Yes |
YesProbably need OAM requirment and solution for this architecture as well.
Samsung could send a reply to SA6 to show what OAM relates group to do for this work.
Intel: SA5 maybe better to start a related work item in SA5 first.
Nokia, Huawei: if Samsung would like to start a WID and be the rapporteur, Nokia and huawei will support.
Samsung volunteer to draft a reply LS.
| replied to | No | ||||
S5‑197601 | Reply to: LS on Application Architecture for enabling Edge Applications | current meeting | LS out | approval | Yes |
Yes
| revised | No | S5‑197752 | |||
S5‑197752 | Reply to: LS on Application Architecture for enabling Edge Applications | SA5 | LS out | approval | Yes |
Yes
| approved | No | S5‑197601 | |||
S5‑197550 | Chair notes on OAM sessions | WG Chair | report | Information | Yes |
Yes
| noted | No | ||||
S5‑197784 | Handling of separate code files | Chairman | other | Endorsement | No |
Yes
| email approval | No | ||||
S5‑197785 | Reply LS on clarification of OAM requirements for RIM | R3-197540 | LS in | - | Yes |
Yespostponed to next meeting
| postponed | No | ||||
6.2 | New OAM&P Work Item proposals | S5‑197084 | New WID on end-to-end procedure of slicing management | AsiaInfo | discussion | Decision | Yes |
YesAsiaInfo presented the New WID.
Chairman: it should only have one rappoteur, not two rappoteurs.
Nokia: CMCC has an SLA WID, is there any differece with the objective of this WID. The TS listed in this contribution is not introducing the related functions.
Intel: Justification shows you need a procedure, but the objective doesn't show that you need a procedure. The title of this WID is 'end to end', however some layers below are not covered. We need to know what's the relation with the existing WID.
Orange: Take a look at 28.531 on the slicing journey..
CMCC: clarifying that the 5G_SLA is not the end to end translation between BSS and OSS.
Nokia disagreed with this clarification from CMCC.
Ericsson: larification relation with TMF work? The figure is not correct, hard to understand.
AsiaInfo: TMF forum didn't defined the procedure of end to end procedure of slicing management. Huawei's WID only cover OSS, not BSS. So AsiaInfo try to propose this WID.
Vice Chair(Maryse) Notes: Charging description/billing needs to be removed. Check existing charging WID (comments to be communicated to OAM)
| noted | No | S5‑196575 | |
S5‑197716 | New WID on 5G management capabilities | AT&T, Orange | WID new | Approval | Yes |
Yes
| revised | No | S5‑197817 | |||
S5‑197817 | New WID on 5G management capabilities | AT&T, Orange | WID new | Approval | No |
Yes
| email approval | No | S5‑197716 | |||
6.3 | OAM&P Maintenance and Rel-16 small Enhancements | S5‑197053 | [Resubmitted] Rel-15 CR 28.550 Add stream information management related operations | Intel Finland Oy | CR | Agreement | Yes |
Yes
| revised | No | S5‑197731 | S5‑196331 |
S5‑197731 | [Resubmitted] Rel-15 CR 28.550 Add stream information management related operations | Intel Finland Oy | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197053 | |||
S5‑197054 | [Resubmitted] Rel-16 CR 28.550 Add stream information management related operations | Intel Finland Oy | CR | Agreement | Yes |
Yes
| revised | No | S5‑197732 | S5‑196332 | ||
S5‑197732 | [Resubmitted] Rel-16 CR 28.550 Add stream information management related operations | Intel Finland Oy | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197054 | |||
S5‑197055 | [Resubmitted] Rel-16 CR 28.552 Add measurements related to QoS flow modification in NG-RAN | Intel Finland Oy | CR | Agreement | Yes |
Yes
| agreed | No | S5‑196610 | |||
S5‑197059 | Rel-16 CR TS 28.541 XML Solution Set for 5GC | CATT,Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197730 | S5‑196296 | ||
S5‑197730 | Rel-16 CR TS 28.541 XML Solution Set for 5GC | CATT,Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197059 | |||
S5‑197079 | Correct NR TAC attribute property | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑196155 | |||
S5‑197080 | Correct NR TAC attribute property | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑197754 | S5‑196241 | ||
S5‑197754 | Correct NR TAC attribute property | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑197080 | |||
S5‑197081 | CR Rel-15 28.532 v1530 correct event time defn | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑197736 | |||
S5‑197736 | CR Rel-15 28.532 v1530 correct event time defn | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑197081 | |||
S5‑197082 | Correct event time defn | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑197737 | |||
S5‑197737 | Correct event time defn | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑197082 | |||
S5‑197083 | Add notifyAlert | Ericsson Inc. | CR | Approval | Yes |
Yes
| revised | No | S5‑197740 | |||
S5‑197740 | Add notifyAlert | Ericsson Inc. | CR | Approval | Yes |
Yes
| agreed | No | S5‑197083 | |||
S5‑197085 | Add configurable FM | Ericsson Inc. | CR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑197086 | Rel-15 CR TS 28.533 Correction on example of MnS deployment scenario in clause 4.5 | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197725 | |||
S5‑197725 | Rel-15 CR TS 28.533 Correction on example of MnS deployment scenario in clause 4.5 | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197755 | S5‑197086 | ||
S5‑197755 | Rel-15 CR TS 28.533 Correction on example of MnS deployment scenario in clause 4.5 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197725 | |||
S5‑197087 | Rel-16 CR TS 28.533 Correction on example of MnS deployment scenario in clause 4.5 | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197726 | |||
S5‑197726 | Rel-16 CR TS 28.533 Correction on example of MnS deployment scenario in clause 4.5 | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197756 | S5‑197087 | ||
S5‑197756 | Rel-16 CR TS 28.533 Correction on example of MnS deployment scenario in clause 4.5 | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197726 | |||
S5‑197088 | Rel-16 CR TS 28.533 Add example of utilization of MnS(s) for different network deployment scenarios | Huawei | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑197104 | Rel-16 CR TS 28.533 Some correction on the reference in Clause 5.3 | Huawei Technologies Japan K.K. | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑197105 | Add managedNFProfile definition for ngc NRM - stage3 | CATT | CR | Approval | Yes |
Yes
| revised | No | S5‑197757 | |||
S5‑197757 | Add managedNFProfile definition for ngc NRM - stage3 | CATT | CR | Approval | Yes |
Yes
| agreed | No | S5‑197105 | |||
S5‑197106 | Concept clarification for Network Slice | Nokia Korea | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑197156 | Rel-15 CR TS 28.530 Fix inconsistencies in the usage of word instance | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197738 | |||
S5‑197738 | Rel-15 CR TS 28.530 Fix inconsistencies in the usage of word instance | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197758 | S5‑197156 | ||
S5‑197758 | Rel-15 CR TS 28.530 Fix inconsistencies in the usage of word instance | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197738 | |||
S5‑197157 | Rel-16 CR TS 28.530 Fix inconsistencies in the usage of word instance | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197739 | |||
S5‑197739 | Rel-16 CR TS 28.530 Fix inconsistencies in the usage of word instance | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197759 | S5‑197157 | ||
S5‑197759 | Rel-16 CR TS 28.530 Fix inconsistencies in the usage of word instance | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197739 | |||
S5‑197158 | 15 CR TS 28.531 Fix inconsistencies in the usage of word instance | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197722 | |||
S5‑197722 | 15 CR TS 28.531 Fix inconsistencies in the usage of word instance | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑197158 | |||
S5‑197159 | Rel-16 CR TS 28.531 Fix inconsistencies in the usage of word instance | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197723 | |||
S5‑197723 | Rel-16 CR TS 28.531 Fix inconsistencies in the usage of word instance | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑197159 | |||
S5‑197171 | Fix merging errors of the specification | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
YesEricsson(Ping Jing): The change of Figure 5.2.1.1-1 of this CR is dependant on CR 0184 (S5-196702). If CR 0184 (S5-196702) is agreed, please ignore the change on Figure 5.2.1.1-1 of this CR.
MCC: if CR 0184 (S5-196702) is agreed you need to revise this CR, otherwise a clash will happen and the CR will be rejected.
Ping Jing said she has check with Mirko last meeting and got the agreement that MCC will do the merging work. So the revision of this CR is not needed.
| agreed | No | S5‑196468 | |||
S5‑197249 | Discussion paper on resolution of Editors note in TS 32.160 clause W4.3 | L.M. Ericsson Limited | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑197250 | CR Rel-16 32.160 Resolution of Editors Note in clause W4.3 Class definitions | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑197744 | |||
S5‑197744 | CR Rel-16 32.160 Resolution of Editors Note in clause W4.3 Class definitions | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑197772 | S5‑197250 | ||
S5‑197772 | CR Rel-16 32.160 Resolution of Editors Note in clause W4.3 Class definitions | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑197744 | |||
S5‑197251 | CR Rel-16 32.156 Update attribute properties table in clause 5.2.1.1 | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑197743 | |||
S5‑197743 | CR Rel-16 32.156 Update attribute properties table in clause 5.2.1.1 | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑197771 | S5‑197251 | ||
S5‑197771 | CR Rel-16 32.156 Update attribute properties table in clause 5.2.1.1 | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑197824 | S5‑197743 | ||
S5‑197824 | CR Rel-16 32.156 Update attribute properties table in clause 5.2.1.1 | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑197840 | S5‑197771 | ||
S5‑197840 | CR Rel-16 32.156 Update attribute properties table in clause 5.2.1.1 | L.M. Ericsson Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑197824 | |||
S5‑197274 | Rel-15 CR TS 28.622 update the definition of attribute measurementsList | ZTE Corporation, Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑197733 | |||
S5‑197733 | Rel-15 CR TS 28.622 update the definition of attribute measurementsList | ZTE Corporation, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197274 | |||
S5‑197275 | Rel-16 CR TS 28.622 Add measurementsList attribute into related IOCs | ZTE Corporation, Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑197276 | Rel-15 CR TS 28.623 update the definition of attribute measurementsList | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑197734 | |||
S5‑197734 | Rel-15 CR TS 28.623 update the definition of attribute measurementsList | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197276 | |||
S5‑197277 | Rel-16 CR TS 28.623 Add the definition of attribute measurementsList | ZTE Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑197735 | |||
S5‑197735 | Rel-16 CR TS 28.623 Add the definition of attribute measurementsList | ZTE Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197277 | |||
S5‑197291 | Correct Network slice NRM | CATT | CR | Agreement | Yes |
Yes
| revised | No | S5‑197724 | |||
S5‑197724 | Correct Network slice NRM | CATT | CR | Agreement | Yes |
Yes
| revised | No | S5‑197760 | S5‑197291 | ||
S5‑197760 | Correct Network slice NRM | CATT | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197724 | |||
S5‑197321 | Update Stage 3 SEPP definition in 5GC NRM | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| email approval | No | ||||
S5‑197327 | Rel15 Refine NRM JSON structure | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197331 | Rel16 Refine NRM JSON structure | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197409 | Rel-16 CR 32.533 Clarify numerous definitions | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑197728 | |||
S5‑197728 | Rel-16 CR 28.533 Clarify numerous definitions | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑197409 | |||
S5‑197418 | CR 32.158 Clarify design pattern for scoping and filtering | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑197720 | S5‑196433 | ||
S5‑197720 | CR 32.158 Clarify design pattern for scoping and filtering | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑197825 | S5‑197418 | ||
S5‑197825 | CR 32.158 Clarify design pattern for scoping and filtering | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑197720 | |||
S5‑197420 | CR 32.158 Clarify design pattern for attribute field selection | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑197721 | S5‑196446 | ||
S5‑197721 | CR 32.158 Clarify design pattern for attribute field selection | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| email approval | No | S5‑197420 | |||
S5‑197428 | Rel-16 CR 28.532 Make scoping and filtering optional in CRUD operations | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑197761 | S5‑196439 | ||
S5‑197761 | Rel-16 CR 28.532 Make scoping and filtering optional in CRUD operations | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑197428 | |||
S5‑197429 | CR 28.532 Correct and update the RESTful HTTP-based solution set of provisioning | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑197762 | S5‑196451 | ||
S5‑197762 | CR 28.532 Correct and update the RESTful HTTP-based solution set of provisioning | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑197429 | |||
S5‑197432 | Correction of definition and reference | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑197443 | Add New Trace data Requirement | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑197444 | Correct schema to reflect location in the specifications | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑197741 | |||
S5‑197741 | Correct schema to reflect location in the specifications | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑197444 | |||
S5‑197445 | Correct XML Schema for consistency and clarity | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| revised | No | S5‑197742 | |||
S5‑197742 | Correct XML Schema for consistency and clarity | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑197445 | |||
S5‑197447 | Removing not used reference and add reference to definition | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑197729 | Rel-16 CR 28.533 Clarify numerous definitions | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
6.4 | Rel-16 Operations, Administration, Maintenance and Provisioning (OAM&P) |   | ||||||||||
6.4.1 | Management of QoE measurement collection | S5‑197017 | Minutes of Management of QoE measurement collection | Rapporteur (Ericsson) | report | Yes |
Yes
| noted | No | |||
6.4.2 | Energy Efficiency of 5G | S5‑197018 | Minutes of Energy effciency of 5G | Rapporteur (ORANGE) | report | Yes |
Yes
| revised | No | S5‑197652 | ||
S5‑197652 | Minutes of Energy effciency of 5G | Rapporteur (ORANGE) | report | - | Yes |
Yes
| noted | No | S5‑197018 | |||
S5‑197142 | Resubmitted LS/r on Energy Efficiency on 5G (3GPP TSG SA5-S5-195667) | ITU-T SG5 | LS in | Yes |
Yes
| noted | No | |||||
S5‑197308 | pCR 28.310 Cleanup proposal | Huawei, Orange | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑197346 | Revised WID on energy efficiency of 5G | Orange | WID revised | Approval | Yes |
Yes
| revised | No | S5‑197613 | |||
S5‑197613 | Revised WID on energy efficiency of 5G | Orange | WID revised | Approval | Yes |
Yes
| agreed | No | S5‑197346 | |||
S5‑197359 | discussion on introducing network data analysis for wireless energy saving | China Telecom Corporation Ltd., CATT | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑197679 | |||
S5‑197679 | discussion on introducing network data analysis for wireless energy saving | China Telecom Corporation Ltd., CATT | discussion | Endorsement | Yes |
YesSA5 agreed to take MDA assisted energy saving into account in the Rel-17 Study on enhancement of MDAS
| noted | No | S5‑197359 | |||
S5‑197364 | LS to SA2 on Energy Efficiency of 5G | China Telecom Corporation Ltd. | LS out | Approval | Yes |
Yes
| noted | No | ||||
S5‑197383 | Terms correction for 5G energy saving | Ericsson France S.A.S | pCR | Approval | Yes |
Yes
| revised | No | S5‑197614 | |||
S5‑197614 | Terms correction for 5G energy saving | Ericsson France S.A.S | pCR | Approval | Yes |
Yes
| approved | No | S5‑197383 | |||
S5‑197470 | Differentiate centralized, distributed and hybrid ES solution approaches | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑197471 | Add use case on Automatic Cell Clustering for Energy Saving | Nokia | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑197842 | Draft TS 28.310 | Orange | draft TS | Approval | No |
No
| reserved | No | ||||
6.4.3 | Network policy management for mobile networks based on NFV scenarios | S5‑197019 | Minutes of Network policy management for mobile networks based on NFV scenarios | Rapporteur (China Mobile) | report | Yes |
Yes
| revised | No | S5‑197783 | ||
S5‑197783 | Minutes of Network policy management for mobile networks based on NFV scenarios | Rapporteur (China Mobile) | report | - | Yes |
Yes
| noted | No | S5‑197019 | |||
S5‑197290 | pCR 28.311 Add information Object Classes | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑197615 | S5‑196656 | ||
S5‑197615 | pCR 28.311 Add information Object Classes | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑197763 | S5‑197290 | ||
S5‑197763 | pCR 28.311 Add information Object Classes | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑197615 | |||
S5‑197292 | pCR 28.311 Add XML definition | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑197618 | |||
S5‑197618 | pCR 28.311 Add XML definition | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑197764 | S5‑197292 | ||
S5‑197764 | pCR 28.311 Add XML definition | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑197618 | |||
S5‑197294 | pCR 28.311 Add SOAP Solutions Set | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑197619 | |||
S5‑197619 | pCR 28.311 Add SOAP Solutions Set | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑197765 | S5‑197294 | ||
S5‑197765 | pCR 28.311 Add SOAP Solutions Set | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑197619 | |||
S5‑197303 | Revised WID on network policy management for mobile networks based on NFV scenarios | China Mobile Com. Corporation | WID revised | Yes |
Yes
| revised | No | S5‑197616 | S5‑196834 | |||
S5‑197616 | Revised WID on network policy management for mobile networks based on NFV scenarios | China Mobile Com. Corporation | WID revised | - | Yes |
Yes
| agreed | No | S5‑197303 | |||
S5‑197305 | Presentation of TS 28.311 for Information and approval to SA#86 | China Mobile Com. Corporation | TS or TR cover | Yes |
Yes
| revised | No | S5‑197620 | ||||
S5‑197620 | Presentation of TS 28.311 for Information and approval to SA#86 | China Mobile Com. Corporation | TS or TR cover | Approval | Yes |
Yes
| approved | No | S5‑197305 | |||
S5‑197347 | pCR 28.311 Rewrite Interface definition | China Mobile Com. Corporation | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197371 | pCR 28.311 Rewrite interface identifaction | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑197617 | |||
S5‑197617 | pCR 28.311 Rewrite interface identifaction | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| revised | No | S5‑197766 | S5‑197371 | ||
S5‑197766 | pCR 28.311 Rewrite interface identifaction | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| approved | No | S5‑197617 | |||
S5‑197843 | Draft TS 28.311 | China Mobile | draft TS | Approval | No |
No
| reserved | No | ||||
6.4.4 | Intent driven management service for mobile networks | S5‑197020 | Minutes of Intent driven management service for mobile networks | Rapporteur (Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑197091 | pCR 28.812 Add the relation between IDMS and SON | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197607 | S5‑196835 | ||
S5‑197607 | pCR 28.812 Add the relation between IDMS and SON | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197091 | |||
S5‑197093 | pCR 28.812 Add the potential requirements for existing scenarios | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197609 | |||
S5‑197609 | pCR 28.812 Add the potential requirements for existing scenarios | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197767 | S5‑197093 | ||
S5‑197767 | pCR 28.812 Add the potential requirements for existing scenarios | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197609 | |||
S5‑197094 | pCR 28.812 Add the potential requirements for intent lifecycle management | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197610 | |||
S5‑197610 | pCR 28.812 Add the potential requirements for intent lifecycle management | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197768 | S5‑197094 | ||
S5‑197768 | pCR 28.812 Add the potential requirements for intent lifecycle management | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197610 | |||
S5‑197095 | pCR 28.812 Update area-based management scenario | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197611 | |||
S5‑197611 | pCR 28.812 Update area-based management scenario | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197095 | |||
S5‑197096 | pCR 28.812 Add potential solution for area based radio network deployment | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197612 | |||
S5‑197612 | pCR 28.812 Add potential solution for area based radio network deployment | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197096 | |||
S5‑197097 | pCR 28.812 Update clause 6.2 operation and notification for intent | Huawei | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑197297 | Rel-16 pCR 28.812 Solution for CSI deployemnt at the edge | Samsung Electronics France SA | pCR | Agreement | Yes |
Yes
| revised | No | S5‑197608 | S5‑196537 | ||
S5‑197608 | Rel-16 pCR 28.812 Solution for CSI deployemnt at the edge | Samsung Electronics France SA | pCR | Agreement | Yes |
Yes
| revised | No | S5‑197769 | S5‑197297 | ||
S5‑197769 | Rel-16 pCR 28.812 Solution for CSI deployemnt at the edge | Samsung Electronics France SA | pCR | Agreement | Yes |
Yes
| approved | No | S5‑197608 | |||
S5‑197844 | Draft TR 28.812 | Huawei | draft TR | Approval | No |
No
| reserved | No | ||||
6.4.5 | Enhancement of performance assurance for 5G networks including network slicing | S5‑197021 | Minutes of Enhancement of performance assurance for 5G networks including network slicing | Rapporteur (Intel) | report | Yes |
Yes
| noted | No | |||
S5‑197043 | Add definitions of PDCP end user throughput measurements | Nokia Solutions & Networks (I) | CR | Agreement | Yes |
Yes
| revised | No | S5‑197565 | |||
S5‑197565 | Add definitions of PDCP end user throughput measurements | Nokia Solutions & Networks (I) | CR | Agreement | No |
Yes
| not pursued | No | S5‑197043 | |||
S5‑197060 | Rel-16 CR 28.552 Add measurements related to NF service registration and update | Intel Corporation SAS | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑197061 | Rel-16 CR 28.552 Add measurements related to NF service discovery | Intel Corporation SAS | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑197062 | Rel-16 CR 28.552 Add measurements related to UE policy association | Intel Corporation SAS | CR | Agreement | Yes |
YesNo comments.
| agreed | No | ||||
S5‑197063 | Rel-16 CR 28.552 Add measurements related to PFD management | Intel Corporation SAS | CR | Agreement | Yes |
YesNo comments.
| agreed | No | ||||
S5‑197064 | Rel-16 CR 28.552 Add measurements related to QoS flow release in the untrusted non-3GPP access | Intel Corporation SAS | CR | Agreement | Yes |
YesNo comments.
| agreed | No | ||||
S5‑197065 | Rel-16 CR 28.552 Add measured object NRCellRelation to the HO related measurements | Intel Corporation SAS | CR | Agreement | Yes |
Yes
| revised | No | S5‑197564 | |||
S5‑197564 | Rel-16 CR 28.552 Add measured object NRCellRelation to the HO related measurements | Intel Corporation SAS | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197065 | |||
S5‑197144 | Reply LS to SA5 on PDCP end user throughput measurements | R2-1914089 | LS in | Yes |
Yes
| noted | No | |||||
S5‑197155 | Rel-16 CR TS 28.552 Adding measurement of packets out-of-order | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197600 | |||
S5‑197600 | Rel-16 CR TS 28.552 Adding measurement of packets out-of-order | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197770 | S5‑197155 | ||
S5‑197770 | Rel-16 CR TS 28.552 Adding measurement of packets out-of-order | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197826 | S5‑197600 | ||
S5‑197826 | Rel-16 CR TS 28.552 Adding measurement of packets out-of-order | Huawei | CR | Agreement | Yes |
Yes
| email approval | No | S5‑197770 | |||
S5‑197322 | Rel-16 CR TS 28.552 Packet Drop Rate measurements update | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑197566 | |||
S5‑197566 | Rel-16 CR TS 28.552 Packet Drop Rate measurements update | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑197322 | |||
S5‑197323 | Rel-16 CR TS 28.552 Packet Loss Rate measurements update | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑197567 | |||
S5‑197567 | Rel-16 CR TS 28.552 Packet Loss Rate measurements update | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑197323 | |||
S5‑197325 | Rel-16 CR TS 28.552 PDCP Data Volume measurements update | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑197568 | |||
S5‑197568 | Rel-16 CR TS 28.552 PDCP Data Volume measurements update | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑197325 | |||
S5‑197329 | Rel-16 CR TS 28.552 UE Throughput measurements update | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑197569 | |||
S5‑197569 | Rel-16 CR TS 28.552 UE Throughput measurements update | Ericsson LM | CR | Approval | Yes |
Yes
| agreed | No | S5‑197329 | |||
S5‑197332 | Add use case and definitions of UL user plane packet delay measurement from UE to UPF | ETRI | CR | Approval | Yes |
Yes
| not pursued | No | ||||
6.4.6 | Discovery of management services in 5G | S5‑197022 | Minutes of Discovery of management services in 5G | Rapporteur (Huawei) | report | No |
Yes
| noted | No | |||
S5‑197160 | Discussion about MnS instance discovery | Huawei | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑197161 | Rel-16 CR TS 28.533 Get MnS instance URI | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197603 | |||
S5‑197603 | Rel-16 CR TS 28.533 Get MnS instance URI | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑197161 | |||
S5‑197162 | Rel-16 CR TS 28.532 Discover MnS instance | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197604 | |||
S5‑197604 | Rel-16 CR TS 28.532 Discover MnS instance | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑197162 | |||
S5‑197163 | Rel-16 CR TS 28.532 Add stage 2 and 3 for MnS discovery service | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197398 | Rel-16 CR 32.533 Introduce a MnS profile | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑197606 | |||
S5‑197606 | Rel-16 CR 32.533 Introduce a MnS profile | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑197398 | |||
S5‑197399 | Rel-16 CR 32.533 Add MnS discovery | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑197605 | Rel-16 CR 32.533 Add MnS discovery | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197400 | TD Using feature identifiers in MnS profiles | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑197746 | |||
S5‑197746 | TD Using feature identifiers in MnS profiles | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| not pursued | No | S5‑197400 | |||
6.4.7 | NRM enhancements | S5‑197023 | Minutes of NRM enhancements | Rapporteur (Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑197089 | Rel-16 CR TS 28.541 Correct the parameter sNSSAIList | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197634 | S5‑196221 | ||
S5‑197634 | Rel-16 CR TS 28.541 Correct the parameter sNSSAIList | Huawei | CR | Agreement | Yes |
Yes
| conditionally agreed | No | S5‑197089 | |||
S5‑197090 | Rel-16 CR TS 28.541 Update on RRMPolicy | Huawei | CR | Agreement | Yes |
YesMerged into S5-197638.
| merged | No | S5‑197638 | S5‑196223 | ||
S5‑197121 | Rel-16 CR TS 28.540 Update the requirements for remote interference management | Huawei | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑197122 | Rel-16 CR TS 28.541 Add the RIM parameters of mapping relations for remote interference management | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197123 | Rel-16 CR TS 28.541 Add the RIM monitoring parameters for remote interference management | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197644 | |||
S5‑197644 | Rel-16 CR TS 28.541 Add the RIM monitoring parameters for remote interference management | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197773 | S5‑197123 | ||
S5‑197773 | Rel-16 CR TS 28.541 Add the RIM monitoring parameters for remote interference management | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197827 | S5‑197644 | ||
S5‑197827 | Rel-16 CR TS 28.541 Add the RIM monitoring parameters for remote interference management | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197773 | |||
S5‑197136 | Resubmitted LS from RAN3 Reply on radio resource management policy | R3-194550 | LS in | Yes |
YesSA5 decided to use S5-197637 to reply S5-197136 and S5-197137.
| replied to | No | |||||
S5‑197637 | Reply to: Resubmitted LS from RAN3 Reply on radio resource management policy | S5 | LS out | approval | No |
Yes
| email approval | No | ||||
S5‑197137 | Resubmitted LS from RAN2 to SA5 on radio resource management policy | R2-1911791 | LS in | Yes |
YesSA5 decided to use S5-197637 to reply S5-197136 and S5-197137.
| replied to | No | |||||
S5‑197168 | Update SEPP Stage 2 definition in 5GC NRM | Nokia Korea | CR | Agreement | Yes |
YesEmail approval with same package of S5-197321.
| email approval | No | S5‑196843 | |||
S5‑197169 | Update definition of attributes related to RRMPolicy | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑197639 | |||
S5‑197639 | Update definition of attributes related to RRMPolicy | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197169 | |||
S5‑197170 | Update definition of attributes related to RRMPolicy | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yesmerged into S5-197638.
| merged | No | S5‑197638 | |||
S5‑197236 | YANG_Netconf CM Notifications | Ericsson España S.A. | CR | Approval | Yes |
Yes
| revised | No | S5‑197717 | S5‑196449 | ||
S5‑197717 | YANG_Netconf CM Notifications | Ericsson España S.A.,Telecom Italia, Orange, China Mobile | CR | Approval | Yes |
Yes
| not pursued | No | S5‑197236 | |||
S5‑197247 | YANG_Netconf Operations | Ericsson España S.A. | CR | Approval | Yes |
Yes
| revised | No | S5‑197718 | S5‑196791 | ||
S5‑197718 | YANG_Netconf Operations | Ericsson España S.A., Huawei, China Mobile, Teleom Italia, Orange | CR | Approval | Yes |
YesNokia object.
| not pursued | No | S5‑197247 | |||
S5‑197253 | Additions to YANG style Guide | Ericsson España S.A. | CR | Approval | Yes |
Yes
| revised | No | S5‑197719 | |||
S5‑197719 | Additions to YANG style Guide | Ericsson España S.A. | CR | Approval | Yes |
Yes
| revised | No | S5‑197774 | S5‑197253 | ||
S5‑197774 | Additions to YANG style Guide | Ericsson España S.A. | CR | Approval | Yes |
Yes
| agreed | No | S5‑197719 | |||
S5‑197262 | Add support of Configurable FM | Ericsson LM | CR | Approval | Yes |
Yes
| not pursued | No | S5‑196598 | |||
S5‑197264 | MF-ME relation with VNF | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑197645 | |||
S5‑197645 | MF-ME relation with VNF | Ericsson Inc. | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑197264 | |||
S5‑197333 | Rel-16 CR TS 28.540 Add requirement on NR active antenna system (AAS) configuration | Ericsson LM | CR | Approval | Yes |
Yes
| revised | No | S5‑197598 | |||
S5‑197598 | Rel-16 CR TS 28.540 Add requirement on NR active antenna system (AAS) configuration | Ericsson LM, Huawei | CR | Approval | No |
Yes
| email approval | No | S5‑197333 | |||
S5‑197334 | Rel-16 CR TS 28.541 Add NRM Info Model definitions for active antenna systems (AAS) | Ericsson LM | CR | Approval | Yes |
Yesmerged with S5-190463 into S5-197642
| merged | No | S5‑197642 | |||
S5‑197386 | Add heartbeat NRM fragment | Ericsson Inc., Nokia, Nokia Shanghai Bell, Orange | CR | Approval | Yes |
YesS5-197386 merged with S5-197401 into S5-197646
| merged | No | S5‑197646 | |||
S5‑197401 | Rel-16 CR 28.622 Add heartbeat control NRM fragment | Ericsson, Nokia, Nokia Shanghai Bell. Orange | CR | Approval | Yes |
YesS5-197386 merged with S5-197401 into S5-197646
| revised | No | S5‑197646 | |||
S5‑197646 | Rel-16 CR 28.622 Add heartbeat control NRM fragment | Ericsson, Nokia, Nokia Shanghai Bell. Orange | CR | Approval | Yes |
Yes
| revised | No | S5‑197828 | S5‑197401 | ||
S5‑197828 | Rel-16 CR 28.622 Add heartbeat control NRM fragment | Ericsson, Nokia, Nokia Shanghai Bell. Orange | CR | Approval | Yes |
Yes
| agreed | No | S5‑197646 | |||
S5‑197402 | Rel-16 CR 28.622 Add subscription control NRM fragment | Ericsson, Nokia, Nokia Shanghai Bell, Orange | CR | Approval | Yes |
Yes
| revised | No | S5‑197649 | |||
S5‑197649 | Rel-16 CR 28.622 Add subscription control NRM fragment | Ericsson, Nokia, Nokia Shanghai Bell, Orange | CR | Approval | Yes |
Yes
| revised | No | S5‑197829 | S5‑197402 | ||
S5‑197829 | Rel-16 CR 28.622 Add subscription control NRM fragment | Ericsson, Nokia, Nokia Shanghai Bell, Orange | CR | Approval | Yes |
Yes
| agreed | No | S5‑197649 | |||
S5‑197403 | Rel-16 CR 28.541 Add NRM fragment for resource allocation and deallocation | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑197635 | Rel-16 CR 28.541 Add NRM fragment for resource allocation and deallocation | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197405 | Rel-16 CR 28.531 Update allocation and deallocation procedures | Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑197636 | Rel-16 CR 28.531 Update allocation and deallocation procedures | Nokia, Nokia Shanghai Bell | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197419 | Discussion paper around RRM Policy | Ericsson LM | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑197427 | Rel-16 CR 28.541 Update of RRM Policy | Ericsson LM | CR | Agreement | Yes |
Yes
| revised | No | S5‑197638 | S5‑196447 | ||
S5‑197638 | Rel-16 CR 28.541 Update of RRM Policy | Ericsson LM | CR | Agreement | Yes |
Yes
| conditionally agreed | No | S5‑197427 | |||
S5‑197433 | Rel-16 CR TS 28.541 Stage 3 for Add NRM Info Model definitions for active antenna systems (AAS) | Ericsson LM | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197434 | Rel-16 CR TS 28.541 Stage 3 for Add NRM Info Model definitions for active antenna systems (AAS) | Ericsson LM | CR | Approval | Yes |
YesS5-197434 merged into S5-197643.
| merged | No | S5‑197643 | |||
S5‑197461 | Rel-15 CR TS 28.541 Add NRM Info Model definitions for beam managed object classes | Pivotal Commware, Intel, ZTE, P.I. Works, China Mobile, Verizon, BT, AT&T, Cisco, Deutsche Telekom, Orange | CR | Agreement | Yes |
Yes
| revised | No | S5‑197640 | S5‑196845 | ||
S5‑197640 | Rel-15 CR TS 28.541 Stages 2 Add NRM Info Model definitions for beam managed object classes | Pivotal Commware, Intel, ZTE, P.I. Works, China Mobile, Verizon, BT, AT&T, Cisco, Deutsche Telekom, Orange | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197461 | |||
S5‑197462 | Rel-15 CR TS 28.541 Stage 3 Add NRM Info Model definitions for beam managed object classes | Pivotal Commware, Intel, Ericsson, ZTE, P.I. Works, China Mobile, Verizon, BT, AT&T, Cisco, Deutsche Telekom, Orange | CR | Agreement | Yes |
Yes
| revised | No | S5‑197641 | S5‑196489 | ||
S5‑197641 | Rel-15 CR TS 28.541 Stage 3 Add NRM Info Model definitions for beam managed object classes | Pivotal Commware, Intel, Ericsson, ZTE, P.I. Works, China Mobile, Verizon, BT, AT&T, Cisco, Deutsche Telekom, Orange | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197462 | |||
S5‑197463 | Rel-16 CR TS 28.541 Stages 2 and 3 Add NRM Info Model definitions for beam managed object classes for Rel-15 Mirror | Pivotal Commware, Intel, Ericsson, ZTE, P.I. Works, China Mobile, Verizon, BT, AT&T, Cisco, Deutsche Telekom, Orange | CR | Agreement | Yes |
Yes
| revised | No | S5‑197642 | |||
S5‑197642 | Rel-16 CR TS 28.541 Stages 2 Add NRM Info Model definitions for beam managed object classes for Rel-15 Mirror | Pivotal Commware, Intel, Ericsson, ZTE, P.I. Works, China Mobile, Verizon, BT, AT&T, Cisco, Deutsche Telekom, Orange, Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197463 | |||
S5‑197643 | Rel-16 CR TS 28.541 Stages 3 Add NRM Info Model definitions for beam managed object classes for Rel-15 Mirror | Pivotal Commware, Intel, Ericsson, ZTE, P.I. Works, China Mobile, Verizon, BT, AT&T, Cisco, Deutsche Telekom, Orange, Huawei | CR | discussion | Yes |
Yes
| agreed | No | ||||
S5‑197647 | (reserved) | Ericsson, Nokia, Nokia Shanghai Bell, Orange | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑197648 | (reserved) | Ericsson, Nokia, Nokia Shanghai Bell, Orange | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑197650 | LS on update of touchpoints | SA5 | LS out | Approval | Yes |
Yes
| approved | No | ||||
6.4.8 | Trace Management in the context of Services Based Management Architecture | S5‑197024 | Minutes of Trace Management in the context of Services Based Management Architecture | Rapporteur (Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑197238 | Rel-16 CR TS 32.421 terminology clean-up | Nokia Japan | CR | Approval | Yes |
Yes
| revised | No | S5‑197570 | |||
S5‑197570 | Rel-16 CR TS 32.421 terminology clean-up | Nokia Japan | CR | Approval | Yes |
Yes
| agreed | No | S5‑197238 | |||
S5‑197241 | Rel-16 CR TS 32.422 new references | Nokia Japan | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑197243 | Rel-16 CR TS 32.422 addition of general management activation mechanisms for 5GS | Nokia Japan | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑197245 | Rel-16 CR TS addition of general signalling activation mechanisms for 5GS | Nokia Japan | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑197248 | Rel-16 CR TS 32.422 Update 5GS deactivation mechanisms | Nokia Japan | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑197252 | Rel-16 CR TS 32.422 update trace recording session start-stop | Nokia Japan | CR | Approval | Yes |
Yes
| agreed | No | ||||
6.4.9 | Integration of ONAP and 3GPP 5G management framework | S5‑197025 | Minutes of Integration of ONAP and 3GPP 5G management framework | Rapporteur (AT&T)) | report | Yes |
Yes
| noted | No | |||
S5‑197044 | Rel-16 CR 28.532 Repair broken links in References | AT&T, Deutsche Telekom, Orange | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑196539 | |||
S5‑197052 | Rel-16 CR 28.532 Introduce Heartbeat MnS | AT&T, Deutsche Telekom, Orange | CR | Approval | Yes |
Yes
| revised | No | S5‑197597 | |||
S5‑197597 | Rel-16 CR 28.532 Introduce Heartbeat MnS | AT&T, Deutsche Telekom, Orange | CR | Approval | Yes |
Yes
| revised | No | S5‑197775 | S5‑197052 | ||
S5‑197775 | Rel-16 CR 28.532 Introduce Heartbeat MnS | AT&T, Orange | CR | Approval | Yes |
Yes
| agreed | No | S5‑197597 | |||
S5‑197098 | Discussion on potential ways for integration of ONAP and 3GPP MnS | Huawei | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑197674 | |||
S5‑197674 | Discussion on potential ways for integration of ONAP and 3GPP MnS | Huawei | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑197776 | S5‑197098 | ||
S5‑197776 | Discussion on potential ways for integration of ONAP and 3GPP MnS | Huawei | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑197830 | S5‑197674 | ||
S5‑197830 | Discussion on potential ways for integration of ONAP and 3GPP MnS | Huawei | discussion | Endorsement | Yes |
YesSA5 get agreement to endorse page 9 and page 10 of this discussion paper.
| endorsed | No | S5‑197776 | |||
S5‑197191 | Rel-16 CR 28.532 RESTful PM file-based notifications for integration with ONAP VES | AT&T, Ericsson, Orange | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑197255 | Discussion on options for integrating 3GPP fault notifications into ONAP VES | AT&T, Orange | discussion | Endorsement | Yes |
YesMerged into S5-197776.
| merged | No | S5‑197776 | |||
S5‑197426 | Draft management services TS 28aaa-000 | AT&T GNS Belgium SPRL | other | Yes |
Yes
| revised | No | S5‑197599 | ||||
S5‑197599 | Draft management services TS 28aaa-000 | AT&T GNS Belgium SPRL | other | - | Yes |
Yes
| revised | No | S5‑197778 | S5‑197426 | ||
S5‑197778 | Draft management services TS 28aaa-000 | AT&T GNS Belgium SPRL | other | Approval | Yes |
Yes
| approved | No | S5‑197599 | |||
S5‑197777 | LS to ONAP on 3GPP MnS integration with VES | SA5 | LS out | Approval | Yes |
Yes
| revised | No | S5‑197831 | |||
S5‑197831 | LS to ONAP on 3GPP MnS integration with VES | SA5 | LS out | Approval | Yes |
Yes
| approved | No | S5‑197777 | |||
6.4.10 | Closed loop SLS Assurance | S5‑197026 | Minutes of Closed loop SLS Assurance | Rapporteur (Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑197295 | Rel-16 CR TS 28.533 Add the description of data analytics utilization in closed loop SLA assurance | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement | Yes |
Yes
| revised | No | S5‑197580 | S5‑196850 | ||
S5‑197580 | Rel-16 CR TS 28.533 Add the description of data analytics utilization in closed loop SLA assurance | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement | Yes |
Yes
| revised | No | S5‑197779 | S5‑197295 | ||
S5‑197779 | Rel-16 CR TS 28.533 Add the description of data analytics utilization in closed loop SLA assurance | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement | Yes |
Yes
| revised | No | S5‑197832 | S5‑197580 | ||
S5‑197832 | Rel-16 CR TS 28.533 Add the description of data analytics utilization in closed loop SLA assurance | HUAWEI TECHNOLOGIES Co. Ltd. | CR | Agreement | No |
Yes
| email approval | No | S5‑197779 | |||
S5‑197304 | pCR TS 28.535 Add concepts related to close loop assurance | HiSilicon Technologies Co. Ltd | pCR | Yes |
Yesmerged into S5-197583
| merged | No | S5‑197583 | ||||
S5‑197581 | pCR TS 28.535 Add concepts related to close loop assurance | HiSilicon Technologies Co. Ltd | pCR | - | No |
Yes
| withdrawn | Yes | ||||
S5‑197309 | pCR 28.535 Interaction with core network for service assurance | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197584 | |||
S5‑197584 | pCR 28.535 Interaction with core network for service assurance | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197786 | S5‑197309 | ||
S5‑197786 | pCR 28.535 Interaction with core network for service assurance | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197833 | S5‑197584 | ||
S5‑197833 | pCR 28.535 Interaction with core network for service assurance | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197786 | |||
S5‑197310 | pCR 28.535 use case for obtaining resource requirements for a communication service | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197585 | |||
S5‑197585 | pCR 28.535 use case for obtaining resource requirements for a communication service | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197310 | |||
S5‑197311 | pCR 28.535 Add analytics scenario introduction | Huawei | pCR | Approval | Yes |
Yes
| noted | No | S5‑197747 | S5‑196267 | ||
S5‑197747 | pCR 28.535 Add analytics scenario introduction | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197328 | pCR 28.535 Add UC on analytical data enablement | Samsung Electronics GmbH | pCR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑197748 | pCR 28.535 Add UC on analytical data enablement | Samsung Electronics GmbH | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197406 | Add description of communication service lifecycle prepareation phase | CCSA | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑197430 | Add description of communication service lifecycle prepareation phase | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑197583 | |||
S5‑197583 | Add description of communication service lifecycle prepareation phase | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑197834 | S5‑197430 | ||
S5‑197834 | Add description of communication service lifecycle prepareation phase | China Mobile E-Commerce Co. | pCR | Approval | No |
Yes
| email approval | No | S5‑197583 | |||
S5‑197448 | Discussion paper on CSA loop entities | L.M. Ericsson Limited | discussion | Endorsement | Yes |
Yes
| noted | No | ||||
S5‑197651 | Discussion paper on CSA loop entities | L.M. Ericsson Limited | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
S5‑197449 | pCR 28.535 Service quality assurance and optimization | L.M. Ericsson Limited | pCR | Approval | Yes |
Yes
| revised | No | S5‑197749 | |||
S5‑197749 | pCR 28.535 Service quality assurance and optimization | L.M. Ericsson Limited | pCR | Approval | Yes |
Yes
| revised | No | S5‑197787 | S5‑197449 | ||
S5‑197787 | pCR 28.535 Service quality assurance and optimization | L.M. Ericsson Limited | pCR | Approval | Yes |
Yes
| approved | No | S5‑197749 | |||
S5‑197450 | pCR 28.535 Add use case and requirements for CSA PM services - overview | L.M. Ericsson Limited | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑197451 | pCR 28.535 Add use case and requirements for CS assurance measurement job control service | L.M. Ericsson Limited | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197452 | pCR 28.535 Add use case and requirements for CS assurance data reporting service | L.M. Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑197453 | pCR 28.535 Add text for clause 4.2 Management control loops | L.M. Ericsson Limited | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑197455 | pCR 28.536 Add Overview of interfaces | L.M. Ericsson Limited | pCR | Approval | Yes |
Yes
| revised | No | S5‑197653 | |||
S5‑197653 | pCR 28.536 Add Overview of interfaces | L.M. Ericsson Limited | pCR | Approval | Yes |
Yes
| revised | No | S5‑197788 | S5‑197455 | ||
S5‑197788 | pCR 28.536 Add Overview of interfaces | L.M. Ericsson Limited | pCR | Approval | Yes |
Yes
| approved | No | S5‑197653 | |||
S5‑197477 | pCR 28.535 Communication service assurance scenario | L.M. Ericsson Limited | pCR | Approval | Yes |
Yes
| revised | No | S5‑197582 | |||
S5‑197582 | pCR 28.535 Communication service assurance scenario | L.M. Ericsson Limited | pCR | Approval | Yes |
Yes
| approved | No | S5‑197477 | |||
S5‑197478 | Presentation of TS 28.535 for information to SA#86 | L.M. Ericsson Limited | TS or TR cover | Information | Yes |
Yes
| revised | No | S5‑197789 | |||
S5‑197789 | Presentation of TS 28.535 for information to SA#86 | L.M. Ericsson Limited | TS or TR cover | Information | Yes |
Yes
| approved | No | S5‑197478 | |||
S5‑197845 | Draft TS 28.535 | Ericsson | draft TS | Approval | No |
No
| reserved | No | ||||
S5‑197846 | Draft TS 28.536 | Ericsson | draft TS | Approval | No |
No
| reserved | No | ||||
6.4.11 | Streaming trace reporting | S5‑197027 | Minutes of Streaming trace reporting | Rapporteur (Nokia) | report | Yes |
Yes
| noted | No | |||
S5‑197254 | Rel-16 CR TS 32.422 update trace configuration parameters | Nokia Japan | CR | Approval | Yes |
Yes
| revised | No | S5‑197587 | |||
S5‑197587 | Rel-16 CR TS 32.422 update trace configuration parameters | Nokia Japan | CR | Approval | Yes |
Yes
| agreed | No | S5‑197254 | |||
S5‑197256 | Rel-16 CR TS 32.422 add streaming trace reporting description | Nokia Japan | CR | Approval | Yes |
Yes
| revised | No | S5‑197588 | |||
S5‑197588 | Rel-16 CR TS 32.422 add streaming trace reporting description | Nokia Japan | CR | Approval | Yes |
Yes
| agreed | No | S5‑197256 | |||
6.4.12 | KPI reporting | S5‑197028 | Minutes of KPI reporting | Rapporteur (ZTE) | report | Yes |
Yes
| noted | No | |||
S5‑197240 | Rel-16 CR TS 28.550 Add UC and requirements for KPI job control | China Telecommunications, ZTE | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑197278 | Rel-16 CR TS 28.550 Enhace performance data report related operations | ZTE Corporation, China Telecom | CR | Agreement | Yes |
Yes
| revised | No | S5‑197572 | |||
S5‑197572 | Rel-16 CR TS 28.550 Enhace performance data report related operations | ZTE Corporation, China Telecom | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197278 | |||
S5‑197279 | Rel-16 CR TS 28.622 Add configurable KPI control NRM | ZTE Corporation, China Telecom | CR | Agreement | Yes |
Yes
| revised | No | S5‑197573 | |||
S5‑197573 | Rel-16 CR TS 28.622 Add configurable KPI control NRM | ZTE Corporation, China Telecom | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑197279 | |||
S5‑197280 | Rel-16 CR TS 28.623 Add configurable KPI control NRM | ZTE Corporation, China Telecom | CR | Agreement | Yes |
Yes
| revised | No | S5‑197574 | |||
S5‑197574 | Rel-16 CR TS 28.623 Add configurable KPI control NRM | ZTE Corporation, China Telecom | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑197280 | |||
S5‑197286 | Rel-16 CR TS 28.550 Add UC and requirements for NF KPI job control | China Telecommunications, ZTE | CR | Agreement | Yes |
Yes
| revised | No | S5‑197571 | S5‑196853 | ||
S5‑197571 | Rel-16 CR TS 28.550 Add UC and requirements for NF KPI job control | China Telecommunications, ZTE | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197286 | |||
S5‑197296 | Rel-16 CR TS 28.554 Update the template of KPI definition for TS 28.554 | Huawei, ZTE, China Telecom | CR | Approval | Yes |
Yes
| revised | No | S5‑197575 | |||
S5‑197575 | Rel-16 CR TS 28.554 Update the template of KPI definition for TS 28.554 | Huawei, ZTE, China Telecom | CR | Approval | Yes |
Yes
| agreed | No | S5‑197296 | |||
6.4.13 | Self-Organizing Networks (SON) for 5G networks | S5‑197029 | Minutes of Self-Organizing Networks (SON) for 5G networks | Rapporteur (Intel) | report | Yes |
Yes
| noted | No | |||
S5‑197069 | pCR 28.313 D-SON PCI configuration use case | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑197555 | |||
S5‑197555 | pCR 28.313 D-SON PCI configuration use case | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑197790 | S5‑197069 | ||
S5‑197790 | pCR 28.313 D-SON PCI configuration use case | Intel Corporation (UK) Ltd, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197555 | |||
S5‑197070 | pCR 28.313 C-SON PCI configuration use case | Intel Corporation (UK) Ltd, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197593 | |||
S5‑197593 | pCR 28.313 C-SON PCI configuration use case | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑197791 | S5‑197070 | ||
S5‑197791 | pCR 28.313 C-SON PCI configuration use case | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑197593 | |||
S5‑197071 | pCR 28.313 D-SON PCI configuration procedure | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑197590 | |||
S5‑197590 | pCR 28.313 D-SON PCI configuration procedure | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑197792 | S5‑197071 | ||
S5‑197792 | pCR 28.313 D-SON PCI configuration procedure | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑197590 | |||
S5‑197072 | pCR 28.313 C-SON PCI configuration procedure | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑197594 | |||
S5‑197594 | pCR 28.313 C-SON PCI configuration procedure | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑197793 | S5‑197072 | ||
S5‑197793 | pCR 28.313 C-SON PCI configuration procedure | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑197594 | |||
S5‑197073 | pCR 28.313 D-SON PCI configuration information | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑197592 | |||
S5‑197592 | pCR 28.313 D-SON PCI configuration information | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑197794 | S5‑197073 | ||
S5‑197794 | pCR 28.313 D-SON PCI configuration information | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑197835 | S5‑197592 | ||
S5‑197835 | pCR 28.313 D-SON PCI configuration information | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑197794 | |||
S5‑197074 | pCR 28.313 C-SON PCI configuration information | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑197595 | |||
S5‑197595 | pCR 28.313 C-SON PCI configuration information | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑197795 | S5‑197074 | ||
S5‑197795 | pCR 28.313 C-SON PCI configuration information | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑197836 | S5‑197595 | ||
S5‑197836 | pCR 28.313 C-SON PCI configuration information | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | S5‑197795 | |||
S5‑197075 | pCR 28.313 LBO use cases | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑197596 | |||
S5‑197596 | pCR 28.313 LBO use cases | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | S5‑197075 | |||
S5‑197076 | pCR 28.313 LBO procedures | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑197750 | |||
S5‑197750 | pCR 28.313 LBO procedures | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | S5‑197076 | |||
S5‑197077 | pCR 28.313 LBO information | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| revised | No | S5‑197751 | |||
S5‑197751 | pCR 28.313 LBO information | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| noted | No | S5‑197077 | |||
S5‑197092 | pCR 28.313 Add usecase and requirements for establishment of new NF in network | Huawei,China Telecommunications | pCR | Approval | Yes |
Yes
| revised | No | S5‑197551 | S5‑196362 | ||
S5‑197551 | pCR 28.313 Add usecase and requirements for establishment of new NF in network | Huawei,China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | S5‑197092 | |||
S5‑197099 | pCR 28.313 Add procedures for establishment of new NE in network | Huawei,China Telecommunications | pCR | Approval | Yes |
Yes
| revised | No | S5‑197586 | |||
S5‑197586 | pCR 28.313 Add procedures for establishment of new NE in network | Huawei,China Telecommunications | pCR | Approval | Yes |
Yes
| approved | No | S5‑197099 | |||
S5‑197125 | pCR 28.313 Add procedures for establishment of new NE in network | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197126 | pCR 28.313 Add use case for NCR remove blacklisting and whitelisting | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑197127 | pCR 28.313 Update the requirements for ANR management in NG-RAN | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197552 | |||
S5‑197552 | pCR 28.313 Update the requirements for ANR management in NG-RAN | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197818 | S5‑197127 | ||
S5‑197818 | pCR 28.313 Update the requirements for ANR management in NG-RAN | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197552 | |||
S5‑197128 | pCR 28.313 Add solutions for ANR management | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197553 | |||
S5‑197553 | pCR 28.313 Add solutions for ANR management | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197819 | S5‑197128 | ||
S5‑197819 | pCR 28.313 Add solutions for ANR management | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197553 | |||
S5‑197129 | pCR 28.313 Use case for Centralized PCI configuration | Huawei | pCR | Approval | Yes |
Yesmerged into S5-197791
| merged | No | S5‑197791 | |||
S5‑197130 | pCR 28.313 Requirements for Centralized PCI configuration | Huawei | pCR | Approval | Yes |
Yesmerged into S5-197791
| merged | No | S5‑197791 | |||
S5‑197131 | pCR TS 28.313 Solutions for centriliazed PCI configuration | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197132 | pCR 28.313 Use case for distributed PCI configuration | Huawei | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑197556 | pCR 28.313 Use case for distributed PCI configuration | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197133 | pCR 28.313 Requirements for distributed PCI configuration | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197591 | |||
S5‑197591 | pCR 28.313 Requirements for distributed PCI configuration | Huawei | pCR | Approval | Yes |
Yesmerged into S5-197790
| merged | No | S5‑197790 | S5‑197133 | ||
S5‑197134 | pCR TS 28.313 Solutions for distributed PCI configuration | Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197244 | pCR 28.313 Add Concept for Establishment of new NE in network | China Telecommunications, Huawei | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197263 | pCR 28.313 Add use case and requirements for cross-slice network resource optimization | KPN N.V. | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑197293 | pCR 28.313 Add Concept for Establishment of new NE in network | China Telecommunications, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197602 | S5‑196400 | ||
S5‑197602 | pCR 28.313 Add Concept for Establishment of new NE in network | China Telecommunications, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197796 | S5‑197293 | ||
S5‑197796 | pCR 28.313 Add Concept for Establishment of new NE in network | China Telecommunications, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197602 | |||
S5‑197421 | CR 28.541 Management of NR ANR, Stage 2 | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| revised | No | S5‑197554 | |||
S5‑197554 | CR 28.541 Management of NR ANR, Stage 2 | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| revised | No | S5‑197837 | S5‑197421 | ||
S5‑197837 | CR 28.541 Management of NR ANR, Stage 2 | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| agreed | No | S5‑197554 | |||
S5‑197422 | CR 28.541 Management of NR ANR, Stage 3 | Ericsson France S.A.S | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑197727 | Rel-16 CR 28.552 Add use case of monitoring of PCI to detect PCI collision or confusion | Intel | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑197847 | Draft TS 28.313 | Intel | draft TS | Approval | No |
No
| reserved | No | ||||
6.4.14 | Enhancement of 3GPP management system for multiple tenant environment support | S5‑197030 | Minutes of Enhancement of 3GPP management system for multiple tenant environment support | Rapporteur (Huawei) | report | Yes |
Yes
| noted | No | |||
S5‑197164 | Discussion paper about multi-tenancy use cases in 3GPP management system | Huawei | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑197576 | |||
S5‑197576 | Discussion paper about multi-tenancy use cases in 3GPP management system | Huawei | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑197797 | S5‑197164 | ||
S5‑197797 | Discussion paper about multi-tenancy use cases in 3GPP management system | Huawei | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑197841 | S5‑197576 | ||
S5‑197841 | Discussion paper about multi-tenancy use cases in 3GPP management system | Huawei | discussion | Endorsement | Yes |
Yes
| endorsed | No | S5‑197797 | |||
S5‑197165 | Rel-16 CR TS 28.541 Add tenant information to support multiple tenants environment | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197577 | |||
S5‑197577 | Rel-16 CR TS 28.541 Add tenant information to support multiple tenants environment | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑197165 | |||
S5‑197166 | Rel-16 CR TS 28.545 Enhance fault management service for tenant support | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197167 | Rel-16 CR TS 28.550 Enhance performance management service for tenant support | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197320 | TD tenant information to support multi-tenancy environment | Nokia, Nokia Shanghai Bell | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑197578 | |||
S5‑197578 | TD tenant information to support multi-tenancy environment | Nokia, Nokia Shanghai Bell | discussion | Endorsement | No |
Yes
| noted | No | S5‑197320 | |||
6.4.15 | Management Aspects of 5G Service-Level Agreement | S5‑197031 | Minutes of Management Aspects of 5G Service-Level Agreement | Rapporteur (China Mobile) | report | Yes |
Yes
| noted | No | |||
S5‑197100 | Rel-16 CR TS 28.541 Update on slice model | Huawei, China Mobile, Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑197621 | S5‑196642 | ||
S5‑197621 | Rel-16 CR TS 28.541 Update on slice model | Huawei, China Mobile, Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
YesHuawei: there is a CR package (CR 0177, CR0198 and CR 0199) for TS 28.541 for stage 2 and stage 3. These CRs need to be approved or noted together.
| agreed | No | S5‑197100 | |||
S5‑197101 | Rel-16 CR TS 28.541 Update XML definitions of ServiceProfile NRM | Huawei, China Mobile, Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
YesNokia, Samsung, Huawei support that next meeting could be one week and a half.
Need offline discussion.
| revised | No | S5‑197589 | |||
S5‑197589 | Rel-16 CR TS 28.541 Update XML definitions of ServiceProfile NRM | Huawei, China Mobile, Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
YesHuawei: there is a CR package (CR 0177, CR0198 and CR 0199) for TS 28.541 for stage 2 and stage 3. These CRs need to be approved or noted together.
| agreed | No | S5‑197101 | |||
S5‑197102 | Rel-16 CR TS 28.541 Update JSON definitions of ServiceProfile NRM | Huawei, China Mobile, Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| revised | No | S5‑197622 | |||
S5‑197622 | Rel-16 CR TS 28.541 Update JSON definitions of ServiceProfile NRM | Huawei, China Mobile, Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
YesHuawei: there is a CR package (CR 0177, CR0198 and CR 0199) for TS 28.541 for stage 2 and stage 3. These CRs need to be approved or noted together.
| revised | No | S5‑197798 | S5‑197102 | ||
S5‑197798 | Rel-16 CR TS 28.541 Update JSON definitions of ServiceProfile NRM | Huawei, China Mobile, Nokia, Nokia Shanghai Bell | CR | Approval | Yes |
Yes
| agreed | No | S5‑197622 | |||
S5‑197152 | Add attribute to describe different types of isolation for network slice | China Mobile | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑197153 | Add attributes for network slice supports IMS and SSC mode | China Mobile | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑197270 | Add attribute properties for network slice supports IMS and SSC mode | China Mobile | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑197271 | Add attribute to describe different types of isolation for network slice | China Mobile | CR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑197272 | Add requirements of network slicing management for creation of a network slice instance or network slice subnet instance according to the template | China Mobile | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑197273 | Add requirements of network slicing management for activation or deactivation of a communication service supported in the network slice instance | China Mobile | CR | Agreement | Yes |
Yes
| withdrawn | Yes | ||||
S5‑197283 | Add attribute properties for network slice supports IMS and SSC mode | China Mobile | CR | Agreement | Yes |
Yes
| revised | No | S5‑197474 | |||
S5‑197284 | Add attribute properties for attribute isolationLevel,physicalIsolation and logicalIsolation | China Mobile | CR | Agreement | Yes |
Yes
| revised | No | S5‑197475 | |||
S5‑197306 | Living document of review of GSMA GST SA5#128 | Huawei, China Mobile | other | Approval | Yes |
Yes
| revised | No | S5‑197629 | |||
S5‑197629 | Living document of review of GSMA GST SA5#128 | Huawei, China Mobile | other | Approval | Yes |
Yes
| approved | No | S5‑197306 | |||
S5‑197307 | LS out on GSMA GST | Huawei, China Mobile | LS out | Approval | Yes |
Yes
| revised | No | S5‑197630 | |||
S5‑197630 | LS out on GSMA GST | Huawei, China Mobile | LS out | Approval | Yes |
Yes
| revised | No | S5‑197802 | S5‑197307 | ||
S5‑197802 | LS out on GSMA GST | SA5 | LS out | Approval | Yes |
Yes
| revised | No | S5‑197853 | S5‑197630 | ||
S5‑197853 | LS out on GSMA GST | SA5 | LS out | Approval | Yes |
Yes
| approved | No | S5‑197802 | |||
S5‑197396 | WI_Exception_Management Aspects of 5G Service-Level Agreement | China Mobile E-Commerce Co. | WI exception request | Approval | Yes |
Yes
| revised | No | S5‑197633 | |||
S5‑197633 | WI_Exception_Management Aspects of 5G Service-Level Agreement | China Mobile E-Commerce Co. | WI exception request | Approval | Yes |
Yes
| revised | No | S5‑197823 | S5‑197396 | ||
S5‑197823 | WI_revised_Management Aspects of 5G Service-Level Agreement | China Mobile E-Commerce Co. | WID revised | Approval | Yes |
Yes
| agreed | No | S5‑197633 | |||
S5‑197626 | Add Automatic CSI to NSI mapping use case | China Mobile E-Commerce Co. | pCR | Approval | Yes |
YesWI change to MA5SLA.
| revised | No | S5‑197803 | S5‑197404 | ||
S5‑197803 | Add Automatic CSI to NSI mapping use case | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| approved | No | S5‑197626 | |||
S5‑197407 | Modification to the existed provisioning procedure after considering SLA requirements | China Mobile E-Commerce Co | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑197632 | Discussion of Modification to the existed provisioning procedure after considering | China Mobile E-Commerce Co | discussion | Endorsement | Yes |
YesCMCC revised the CR to Discussion paper without informing MCC, the original CR is noted, the revision Tdoc number as a new number for discussion paper.
| endorsed | No | ||||
S5‑197410 | Add attribute properties for isolationLevelCN, isolationLevelTN and isolationLevelAN | China Mobile E-Commerce Co | CR | Approval | Yes |
YesS5-197410 and S5-197411 merged into S5-197623
| merged | No | S5‑197623 | |||
S5‑197411 | Add attribute to describe different types of isolation for network slice | China Mobile E-Commerce Co | CR | Approval | Yes |
YesS5-197410 and S5-197411 merged into S5-197623
| not pursued | No | ||||
S5‑197623 | Discussion of isolation levels definition in SA5 | China Mobile, China Southern Power Grid Co. , Huawei | discussion | Endorsement | Yes |
YesCMCC revised the CR to Discussion paper without informing MCC, the original CR is noted, the revision Tdoc number as a new number for discussion paper.
| noted | No | ||||
S5‑197412 | Add attribute property of coverage type | China Mobile E-Commerce Co | CR | Approval | Yes |
YesS5-197412 and S5-197414 merged into S5-197624
| merged | No | S5‑197624 | |||
S5‑197414 | Add attribute to describe different coverage types of network slice | China Mobile E-Commerce Co | CR | Approval | Yes |
YesS5-197412 and S5-197414 merged into S5-197624
| revised | No | S5‑197624 | |||
S5‑197624 | Add attribute to describe different coverage types of network slice | China Mobile E-Commerce Co | CR | Approval | No |
Yesmerged into S5-197621
| merged | No | S5‑197621 | S5‑197414 | ||
S5‑197456 | TD R16 Combinations of GST attributes | Ericsson | discussion | Endorsement | Yes |
Yes
| revised | No | S5‑197625 | |||
S5‑197625 | TD R16 Combinations of GST attributes | Ericsson | discussion | Endorsement | No |
Yes
| email approval | No | S5‑197456 | |||
S5‑197474 | Add attribute properties for network slice supports IMS and SSC mode | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| not treated | No | S5‑197283 | |||
S5‑197475 | Add attribute properties for attribute isolationLevel,physicalIsolation and logicalIsolation | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| not treated | No | S5‑197284 | |||
6.4.16 | Network policy management for 5G mobile networks based on NFV scenarios (preliminary work before SA approval) | S5‑197032 | Minutes of Network policy management for 5G mobile networks based on NFV scenarios (preliminary work before SA approval) | Rapporteur (China Mobile) | report | No |
Yes
| noted | No | |||
6.4.17 | Management of MDT in 5G (preliminary work before SA approval) | S5‑197033 | Minutes of Management of MDT in 5G (preliminary work before SA approval) | Rapporteur (Ericsson) | report | Yes |
Yes
| noted | No | |||
S5‑197438 | New structure for 5G MDT requirements | Ericsson India Private Limited | other | Approval | Yes |
YesNo CR number, the type of Tdoc is incorrect. Revised to S5-197705 to fix this issue.
| revised | No | S5‑197705 | |||
S5‑197705 | Update MDT requirement to include support of MDT in 5G | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑197438 | |||
S5‑197441 | Add MDT Use Cases | Ericsson India Private Limited | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑197442 | Add MDT business level requirements | Ericsson India Private Limited | other | Approval | Yes |
YesNo CR number, the type of Tdoc is incorrect. Revised to S5-197706 to fix this issue.
| revised | No | S5‑197706 | |||
S5‑197706 | Add MDT business level requirements | Ericsson India Private Limited | CR | Approval | Yes |
Yes
| agreed | No | S5‑197442 | |||
6.5 | OAM&P Studies |   | ||||||||||
6.5.1 | Study on protocol enhancement for real time communication | S5‑197034 | Minutes of Study on protocol enhancement for real time communication | Rapporteur(Nokia) | report | No |
Yes
| noted | No | |||
6.5.2 | Study on Self-Organizing Networks (SON) for 5G | S5‑197035 | Minutes of Study on Self-Organizing Networks (SON) for 5G | Rapporteur (Intel) | report | No |
Yes
| noted | No | |||
S5‑197078 | pCR 28.861 cleanup | Intel Corporation (UK) Ltd | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑197404 | Add Automatic CSI to NSI mapping use case | China Mobile E-Commerce Co. | pCR | Approval | Yes |
Yes
| revised | No | S5‑197626 | |||
S5‑197423 | pCR 28.861 Remove work not in Rel-16 | Ericsson France S.A.S | pCR | Approval | Yes |
Yes
| revised | No | S5‑197628 | |||
S5‑197628 | pCR 28.861 Remove work not in Rel-16 | Ericsson France S.A.S | pCR | Approval | Yes |
Yes
| approved | No | S5‑197423 | |||
S5‑197424 | pCR 28.861 Trace and MDT | Ericsson France S.A.S | pCR | Approval | Yes |
Yes
| revised | No | S5‑197627 | |||
S5‑197627 | pCR 28.861 Trace and MDT | Ericsson France S.A.S | pCR | Approval | Yes |
Yes
| approved | No | S5‑197424 | |||
S5‑197464 | Add cell neighbour relationship indication | Nokia | pCR | Approval | Yes |
Yes
| noted | No | S5‑196178 | |||
S5‑197465 | Update ANR optimization use case to allow for use of deployment data | Nokia | pCR | Approval | Yes |
Yes
| noted | No | S5‑196180 | |||
S5‑197466 | Add requirement for NR indication to ANR optimization usecase | Nokia | pCR | Approval | Yes |
Yes
| noted | No | S5‑196182 | |||
S5‑197467 | pCR 28.861 remove duplicated clause in Multi-aspect / multi-domain resource optimization use case | Nokia | pCR | Approval | Yes |
Yes
| approved | No | S5‑196175 | |||
S5‑197468 | Update SON coordination use case | Nokia | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑197469 | Update reporting for SON coordination use case | Nokia | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑197472 | Allow for service-centric load redistribution | Nokia | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑197473 | Update requirements for Load Balancing Optimization to allow for service centric resource optimization | Nokia | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑197631 | Presentation of TS 28.861 for approval to SA#86 | Intel | other | Approval | Yes |
Yes
| revised | No | S5‑197804 | |||
S5‑197804 | Presentation of TS 28.861 for approval to SA#86 | Intel | other | Approval | Yes |
Yes
| approved | No | S5‑197631 | |||
S5‑197848 | Draft TR 28.861 | Intel | draft TR | Approval | No |
No
| reserved | No | ||||
6.5.3 | Study on non-public networks management | S5‑197036 | Minutes of Study on non-public networks management | Rapporteur (Huawei) | report | Yes |
Yes
| revised | No | S5‑197782 | ||
S5‑197782 | Minutes of Study on non-public networks management | Rapporteur (Huawei) | report | - | Yes |
Yes
| noted | No | S5‑197036 | |||
S5‑197312 | pCR 28.807 Clean-up for roles related to NPN management | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197557 | |||
S5‑197557 | pCR 28.807 Clean-up for roles related to NPN management | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197312 | |||
S5‑197313 | pCR 28.807 Clarification on NPN use cases | Huawei | pCR | Approval | Yes |
YesNo comments.
| approved | No | ||||
S5‑197314 | pCR 28.807 Add potential requirements for management of NPN | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197558 | |||
S5‑197558 | pCR 28.807 Add potential requirements for management of NPN | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197314 | |||
S5‑197315 | Network sharing with NPN | Huawei | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑197316 | LS on network sharing with non-public networks | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑197559 | |||
S5‑197559 | LS on network sharing with non-public networks | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑197805 | S5‑197316 | ||
S5‑197805 | LS on network sharing with non-public networks | SA5 | LS out | Approval | Yes |
Yes
| approved | No | S5‑197559 | |||
S5‑197317 | pCR 28.807 Add clauses for solutions and conclusions | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197563 | |||
S5‑197563 | pCR 28.807 Add clauses for solutions and conclusions | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197317 | |||
S5‑197318 | CAG management | Huawei | other | Approval | Yes |
Yes
| noted | No | ||||
S5‑197319 | LS on CAG | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑197560 | |||
S5‑197560 | LS on CAG | Huawei | LS out | Approval | Yes |
Yes
| revised | No | S5‑197806 | S5‑197319 | ||
S5‑197806 | LS on CAG | SA5 | LS out | Approval | Yes |
Yes
| approved | No | S5‑197560 | |||
S5‑197391 | Add NPN management use cases | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑197395 | Add potential requirements for management of NPN | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑197435 | Add NPN management use case | China Mobile Com. Corporation, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197561 | |||
S5‑197561 | Add NPN management use case | China Mobile Com. Corporation, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197435 | |||
S5‑197437 | Add potential requirement for management of NPN | China Mobile Com. Corporation, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197562 | |||
S5‑197562 | Add potential requirement for management of NPN | China Mobile Com. Corporation, Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197800 | S5‑197437 | ||
S5‑197800 | Add potential requirement for management of NPN | China Mobile Com. Corporation, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197562 | |||
S5‑197849 | Draft TR 28.807 | Huawei | draft TR | Approval | No |
No
| reserved | No | ||||
6.5.4 | Study on management and orchestration aspects with integrated satellite components in a 5G network | S5‑197037 | Minutes of Study on management and orchestration aspects with integrated satellite components in a 5G network | Rapporteur (Thales) | report | Yes |
Yes
| noted | No | |||
S5‑197242 | Add already approved missing requirement from TSG WD SA5#127 from use case for creation of a network slice instance associated with a Satellite RAN and a Terrestrial RAN | THALES (Rapporteur), TNO | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑197326 | Add use case for multi-RAT load-balancing associated with a Satellite RAN and a Terrestrial RAN | ETRI | pCR | Approval | Yes |
Yes
| approved | No | ||||
S5‑197382 | pCR 28.808 Add solution to allow a network slice instance to be associated with both a Satellite RAN and a Terrestrial RAN | TNO | pCR | Approval | Yes |
Yes
| revised | No | S5‑197579 | |||
S5‑197579 | pCR 28.808 Add solution to allow a network slice instance to be associated with both a Satellite RAN and a Terrestrial RAN | TNO | pCR | Approval | Yes |
Yes
| approved | No | S5‑197382 | |||
S5‑197850 | Draft TR 28.808 | Thales | draft TR | Approval | No |
No
| reserved | No | ||||
6.5.5 | Study on enhancement of Management Data Analytics Service | S5‑197038 | Minutes of Study on enhancement of Management Data Analytics Service | Rapporteur (Intel) | report | Yes |
Yes
| noted | No | |||
S5‑197056 | pCR Add MDA role in the management loop | Intel Corporation SAS | pCR | Approval | Yes |
Yes
| revised | No | S5‑197708 | |||
S5‑197708 | pCR Add MDA role in the management loop | Intel Corporation SAS | pCR | Approval | Yes |
Yes
| revised | No | S5‑197807 | S5‑197056 | ||
S5‑197807 | pCR Add MDA role in the management loop | Intel Corporation SAS | pCR | Approval | Yes |
Yes
| approved | No | S5‑197708 | |||
S5‑197057 | pCR Add possible solution on coverage issue analysis | Intel Corporation SAS | pCR | Approval | Yes |
Yes
| revised | No | S5‑197710 | |||
S5‑197710 | pCR Add possible solution on coverage issue analysis | Intel Corporation SAS, Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197057 | |||
S5‑197058 | pCR Add UC on resource utilization analysis | Intel Corporation SAS | pCR | Approval | Yes |
Yes
| revised | No | S5‑197711 | |||
S5‑197711 | pCR Add UC on resource utilization analysis | Intel Corporation SAS | pCR | Approval | Yes |
Yes
| approved | No | S5‑197058 | |||
S5‑197138 | Resubmitted Ls from RAN3 Reply on User Data Congestion Analytics | R3-194749 | LS in | Yes |
YesResubmitted this LS to next meeting.
| postponed | No | |||||
S5‑197145 | Reply LS to SA5 on User Data Congestion Analytics | S2-1910210 | LS in | Yes |
YesResubmitted this LS to next meeting.
| postponed | No | |||||
S5‑197298 | pCR 28.809 Update the overview descriptions of MDAS | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197707 | |||
S5‑197707 | pCR 28.809 Update the overview descriptions of MDAS | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197298 | |||
S5‑197299 | pCR 28.809 Update the use case of RAN user plane congestion | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197709 | |||
S5‑197709 | pCR 28.809 Update the use case of RAN user plane congestion | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197299 | |||
S5‑197300 | pCR 28.809 Update the use case of coverage issue analysis | Huawei | pCR | Approval | Yes |
Yesmerged into S5-197710
| merged | No | S5‑197710 | |||
S5‑197301 | pCR 28.809 Add the use case of E2E latency analysis as one of the SLS assurance related issues | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197714 | |||
S5‑197714 | pCR 28.809 Add the use case of E2E latency analysis as one of the SLS assurance related issues | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197301 | |||
S5‑197302 | pCR 28.809 Add the use case of alarm incident analysis as one of the fault management related issues | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197712 | |||
S5‑197712 | pCR 28.809 Add the use case of alarm incident analysis as one of the fault management related issues | Huawei | pCR | Approval | Yes |
Yes
| revised | No | S5‑197808 | S5‑197302 | ||
S5‑197808 | pCR 28.809 Add the use case of alarm incident analysis as one of the fault management related issues | Huawei | pCR | Approval | Yes |
Yes
| approved | No | S5‑197712 | |||
S5‑197324 | pCR 28.809 Add UC on handover optimization | Samsung Electronics GmbH | pCR | Approval | Yes |
Yes
| revised | No | S5‑197713 | |||
S5‑197713 | pCR 28.809 Add UC on handover optimization | Samsung Electronics GmbH | pCR | Approval | Yes |
Yes
| revised | No | S5‑197809 | S5‑197324 | ||
S5‑197809 | pCR 28.809 Add UC on handover optimization | Samsung Electronics GmbH | pCR | Approval | Yes |
Yes
| approved | No | S5‑197713 | |||
S5‑197454 | Discussion paper on MDAS capabilities | L.M. Ericsson Limited | discussion | Endorsement | No |
Yes
| withdrawn | Yes | ||||
S5‑197680 | pCR Add UC on MDA assisted energy saving | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S5‑197781 | |||
S5‑197781 | pCR Add UC on MDA assisted energy saving | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| revised | No | S5‑197810 | S5‑197680 | ||
S5‑197810 | pCR Add UC on MDA assisted energy saving | China Telecom Corporation Ltd. | pCR | Approval | Yes |
Yes
| approved | No | S5‑197781 | |||
S5‑197851 | Draft TR 28.809 | Intel | draft TR | Approval | No |
No
| reserved | No | ||||
6.5.6 | Study on autonomous network levels | S5‑197039 | Minutes of Study on autonomous network levels | Rapporteur (China Mobile) | report | Yes |
Yes
| noted | No | |||
S5‑197330 | pCR 28.810 addition of multi-domain/layer/technology orchestration automation use case and requirement | ETRI | pCR | Approval | Yes |
Yes
| revised | No | S5‑197701 | |||
S5‑197701 | pCR 28.810 addition of multi-domain/layer/technology orchestration automation use case and requirement | ETRI | pCR | Approval | Yes |
Yes
| revised | No | S5‑197811 | S5‑197330 | ||
S5‑197811 | pCR 28.810 addition of multi-domain/layer/technology orchestration automation use case and requirement | ETRI | pCR | Approval | Yes |
Yes
| approved | No | S5‑197701 | |||
S5‑197351 | pCR 28.810 Add concept of network autonomy | Huawei, China Mobile, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| revised | No | S5‑197677 | |||
S5‑197677 | pCR 28.810 Add concept of network autonomy | Huawei, China Mobile, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| revised | No | S5‑197820 | S5‑197351 | ||
S5‑197820 | pCR 28.810 Add concept of network autonomy | Huawei, China Mobile, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S5‑197677 | |||
S5‑197352 | pCR 28.810 Add concept of network autonomy level | Huawei, China Mobile, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| revised | No | S5‑197678 | |||
S5‑197678 | pCR 28.810 Add concept of network autonomy level | Huawei, China Mobile, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| revised | No | S5‑197821 | S5‑197352 | ||
S5‑197821 | pCR 28.810 Add concept of network autonomy level | Huawei, China Mobile, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S5‑197678 | |||
S5‑197353 | pCR 28.810 pCR 28.810 Add potential dimensions for classification of network autonomy level | Huawei, China Mobile, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| revised | No | S5‑197745 | |||
S5‑197745 | pCR 28.810 pCR 28.810 Add potential dimensions for classification of network autonomy level | Huawei, China Mobile, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| revised | No | S5‑197822 | S5‑197353 | ||
S5‑197822 | pCR 28.810 pCR 28.810 Add potential dimensions for classification of network autonomy level | Huawei, China Mobile, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S5‑197745 | |||
S5‑197354 | pCR 28.810 Add coverage optimization scenario exampe for classification of network autonomy levels | Huawei, China Mobile, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| revised | No | S5‑197703 | |||
S5‑197703 | pCR 28.810 Add coverage optimization scenario exampe for classification of network autonomy levels | Huawei, China Mobile, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| revised | No | S5‑197812 | S5‑197354 | ||
S5‑197812 | pCR 28.810 Add coverage optimization scenario exampe for classification of network autonomy levels | Huawei, China Mobile, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S5‑197703 | |||
S5‑197355 | pCR 28.810 Add NE deployment scenario exampe for classification of network autonomy levels | Huawei, China Mobile, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| revised | No | S5‑197704 | |||
S5‑197704 | pCR 28.810 Add NE deployment scenario exampe for classification of network autonomy levels | Huawei, China Mobile, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| revised | No | S5‑197813 | S5‑197355 | ||
S5‑197813 | pCR 28.810 Add NE deployment scenario exampe for classification of network autonomy levels | Huawei, China Mobile, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S5‑197704 | |||
S5‑197384 | Add background of relevant study in other SDOs or industry parties | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑197388 | Add significance for levels of autonomous network | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑197394 | Add potential solution for network autonomy level | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑197397 | Add fault RCA and recovery scenario example for network autonomy level | China Mobile Com. Corporation | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
S5‑197415 | Add background of relevant study in other SDOs or industry parties | China Mobile Com. Corporation, Huawei, China Unicom, ZTE | pCR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197416 | Add background of relevant study in other SDOs or industry parties | China Mobile Com. Corporation, Huawei, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| revised | No | S5‑197675 | |||
S5‑197675 | Add background of relevant study in other SDOs or industry parties | China Mobile Com. Corporation, Huawei, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| revised | No | S5‑197780 | S5‑197416 | ||
S5‑197780 | Add background of relevant study in other SDOs or industry parties | China Mobile Com. Corporation, Huawei, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S5‑197675 | |||
S5‑197417 | Add significance for levels of autonomous network | China Mobile Com. Corporation, Huawei, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| revised | No | S5‑197676 | |||
S5‑197676 | Add significance for levels of autonomous network | China Mobile Com. Corporation, Huawei, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S5‑197417 | |||
S5‑197425 | Add potential solution for network autonomy level | China Mobile Com. Corporation, Huawei, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| revised | No | S5‑197799 | |||
S5‑197799 | Add potential solution for network autonomy level | China Mobile Com. Corporation, Huawei, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S5‑197425 | |||
S5‑197838 | Add potential solution for network autonomy level | China Mobile Com. Corporation, Huawei, China Unicom, ZTE | pCR | Approval | No |
Yes
| withdrawn | Yes | S5‑197799 | |||
S5‑197431 | Add fault RCA and recovery scenario example for network autonomy level | China Mobile Com. Corporation, Huawei, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| revised | No | S5‑197702 | |||
S5‑197702 | Add fault RCA and recovery scenario example for network autonomy level | China Mobile Com. Corporation, Huawei, China Unicom, ZTE | pCR | Approval | Yes |
Yes
| approved | No | S5‑197431 | |||
S5‑197852 | Draft TR 28.810 | China Mobile | draft TR | Approval | No |
No
| reserved | No | ||||
6.5.7 | Study on on network slice management enhancements (preliminary work before SA approval) | S5‑197040 | Minutes of Study on on network slice management enhancements (preliminary work before SA approval) | Rapporteur (Huawei) | report | No |
Yes
| noted | No | |||
7 | Charging | S5‑197698 | (reserved) | charging | other | discussion | No |
Yes
| withdrawn | Yes | ||
S5‑197699 | (reserved) | charging | other | discussion | No |
Yes
| withdrawn | Yes | ||||
S5‑197700 | (reserved) | charging | other | discussion | No |
Yes
| withdrawn | Yes | ||||
7.1 | Charging Plenary | S5‑197041 | CH Agenda and Time Plan | CH SWG Chair | agenda | Yes |
Yes
| approved | No | |||
S5‑197042 | CH Executive Report | CH SWG Chair | report | No |
Yes
| noted | No | |||||
S5‑197140 | Resubmitted LS from GSMA to SA2 and SA5 on VoWiFi – VoLTE handover | GSMA | LS in | Yes |
YesSA5 is aware of existing solution solving this situation: UE level configuration to block VoWifi in roaming.
| replied to | No | |||||
S5‑197480 | Reply to: Resubmitted LS from GSMA to SA2 and SA5 on VoWiFi – VoLTE handover | SA5 | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑197143 | Resubmitted LS to SA5 and SA2 on 5G Cell ID(s) in the 3GPP SA5 billing system, related to Retained Data regulations | ETSI TC LI | LS in | Yes |
YesReply: considered in AMF WID.
Check potiential answers from SA2 on MME
| replied to | No | |||||
S5‑197481 | Reply to: Resubmitted LS to SA5 and SA2 on 5G Cell ID(s) in the 3GPP SA5 billing system, related to Retained Data regulations | SA5 | LS out | approval | Yes |
Yes
| approved | No | ||||
S5‑197146 | LS Reply to SA5 on Introduction of CHF Address from PCF | S2-1910224 | LS in | Yes |
Yes
| replied to | No | |||||
S5‑197154 | Revision of SA5 ToR - charging part | CH SWG Chair | ToR | Yes |
Yes
| revised | No | S5‑197482 | ||||
S5‑197482 | Revision of SA5 ToR - charging part | CH SWG Chair | ToR | - | Yes |
YesSA5 consider that the ToR of charging part should merge with ToR of OAM part as the final version to submit to SA.
| noted | No | S5‑197154 | |||
S5‑197697 | SA5#128 CH Agreed & Approved | CH SWG Chair | other | Agreement | Yes |
Yes
| agreed | No | ||||
7.2 | New Charging Work Item proposals |   | ||||||||||
7.3 | Charging Maintenance and Rel-16 small Enhancements | S5‑197051 | Rel-16 CR 32.255 Correction of handover triggers | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑197685 | |
S5‑197685 | Rel-16 CR 32.255 Correction of handover triggers | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197051 | |||
S5‑197107 | Rel-15 CR 32.298 Correction of references to 5G | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑197529 | |||
S5‑197529 | Rel-15 CR 32.298 Correction of references to 5G | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197107 | |||
S5‑197108 | Rel-16 CR 32.298 Correction of references to 5G | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑197530 | |||
S5‑197530 | Rel-16 CR 32.298 Correction of references to 5G | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197108 | |||
S5‑197109 | Rel-15 CR 32.298 Correction of abnormal release trigger | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑197110 | Rel-16 CR 32.298 Correction of abnormal release trigger | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑197124 | Rel-15 CR 32.298 Correction of Serving Node change | China Mobile Com. Corporation | CR | Yes |
Yes
| revised | No | S5‑197531 | ||||
S5‑197531 | Rel-15 CR 32.298 Correction of Serving Node change | China Mobile Com. Corporation | CR | - | Yes |
Yes
| agreed | No | S5‑197124 | |||
S5‑197135 | Rel-16 CR 32.298 Correction of Serving Node change | China Mobile Com. Corporation | CR | Yes |
Yes
| revised | No | S5‑197532 | ||||
S5‑197532 | Rel-16 CR 32.298 Correction of Serving Node change | China Mobile Com. Corporation | CR | - | Yes |
Yes
| agreed | No | S5‑197135 | |||
S5‑197192 | Rel-15 CR 32.255 Correction of Unit Count Inactivity Timer | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197533 | |||
S5‑197533 | Rel-15 CR 32.255 Correction of Unit Count Inactivity Timer | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197192 | |||
S5‑197193 | Rel-15 CR 32.298 Addition of Furnish Charging Information | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197537 | |||
S5‑197537 | Rel-15 CR 32.298 Addition of Furnish Charging Information | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197193 | |||
S5‑197194 | Rel-15 CR 32.255 Addition of Furnish Charging Information | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197535 | |||
S5‑197535 | Rel-15 CR 32.255 Addition of Furnish Charging Information | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197194 | |||
S5‑197195 | Rel-15 CR 32.255 Clarify on the limit for multiple UPFs | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197655 | |||
S5‑197655 | Rel-15 CR 32.255 Clarify on the limit for multiple UPFs | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197195 | |||
S5‑197196 | Rel-15 CR 32.255 Clarify on the SSC mode and triggers for time and volume | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197539 | |||
S5‑197539 | Rel-15 CR 32.255 Clarify on the SSC mode and triggers for time and volume | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197196 | |||
S5‑197197 | Rel-15 CR 32.290 Correction on Notify response | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197657 | |||
S5‑197657 | Rel-15 CR 32.290 Correction on Notify response | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197197 | |||
S5‑197198 | Rel-15 CR 32.291 Correction on Notify response | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197659 | |||
S5‑197659 | Rel-15 CR 32.291 Correction on Notify response | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197198 | |||
S5‑197199 | Rel-15 CR 32.255 Clarify the Category in message format | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197200 | Rel-15 CR 32.290 Clarify the Category in message format | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197201 | Rel-15 CR 32.291 Clarify the Category in message format | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197202 | Rel-15 CR 32.298 Clarify the Category in message format | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197203 | Rel-15 CR 32.274 Clarify the Category in message format | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197204 | Rel-15 CR 32.291 Correction of ChargingDataResponse description | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197694 | |||
S5‑197694 | Rel-15 CR 32.291 Correction of ChargingDataResponse description | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197204 | |||
S5‑197205 | Rel-15 CR 32.255 Add the uniqueness message identifier | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197206 | Rel-15 CR 32.274 Add the uniqueness message identifier | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197207 | Rel-15 CR 32.290 Add the uniqueness message identifier | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197208 | Rel-15 CR 32.291 Add the uniqueness message identifier | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197209 | Rel-15 CR 32.291 Correction on the Resource URI | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197663 | |||
S5‑197663 | Rel-15 CR 32.291 Correction on the Resource URI | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197209 | |||
S5‑197210 | Rel-15 CR 32.255 Add the access type | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197211 | Rel-15 CR 32.291 Add the access type | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197212 | Rel-15 CR 32.298 Add the access type | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197213 | Rel-15 CR 32.274 Correction on Applicable Triggers in the SMSF | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197693 | |||
S5‑197693 | Rel-15 CR 32.274 Correction on Applicable Triggers in the SMSF | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑197213 | |||
S5‑197214 | Rel-15 CR 32.274 Correction on SMS Submission - ECUR flow | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197692 | |||
S5‑197692 | Rel-15 CR 32.274 Correction on SMS Submission - ECUR flow | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑197214 | |||
S5‑197215 | Rel-16 CR 32.255 Correction of Unit Count Inactivity Timer | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑197534 | |||
S5‑197534 | Rel-16 CR 32.255 Correction of Unit Count Inactivity Timer | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197215 | |||
S5‑197216 | Rel-16 CR 32.298 Addition of Furnish Charging Information | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197538 | |||
S5‑197538 | Rel-16 CR 32.298 Addition of Furnish Charging Information | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197216 | |||
S5‑197217 | Rel-16 CR 32.255 Addition of Furnish Charging Information | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197536 | |||
S5‑197536 | Rel-16 CR 32.255 Addition of Furnish Charging Information | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197217 | |||
S5‑197218 | Rel-16 CR 32.255 Clarify on the limit for multiple UPFs | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197656 | |||
S5‑197656 | Rel-16 CR 32.255 Clarify on the limit for multiple UPFs | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197218 | |||
S5‑197219 | Rel-16 CR 32.255 Clarify on the SSC mode and triggers for time and volume | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197654 | |||
S5‑197654 | Rel-16 CR 32.255 Clarify on the SSC mode and triggers for time and volume | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197219 | |||
S5‑197220 | Rel-16 CR 32.290 Correction on Notify response | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197658 | |||
S5‑197658 | Rel-16 CR 32.290 Correction on Notify response | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197220 | |||
S5‑197221 | Rel-16 CR 32.291 Correction on Notify response | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197660 | |||
S5‑197660 | Rel-16 CR 32.291 Correction on Notify response | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197221 | |||
S5‑197222 | Rel-16 CR 32.255 Clarify the Category in message format | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197223 | Rel-16 CR 32.290 Clarify the Category in message format | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197224 | Rel-16 CR 32.291 Clarify the Category in message format | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197225 | Rel-16 CR 32.298 Clarify the Category in message format | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197226 | Rel-16 CR 32.291 Correction of ChargingDataResponse description | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197695 | |||
S5‑197695 | Rel-16 CR 32.291 Correction of ChargingDataResponse description | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197226 | |||
S5‑197227 | Rel-16 CR 32.255 Add the uniqueness message identifier | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197228 | Rel-16 CR 32.290 Add the uniqueness message identifier | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197229 | Rel-16 CR 32.291 Add the uniqueness message identifier | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197230 | Rel-16 CR 32.291 Correction on the Resource URI | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197664 | |||
S5‑197664 | Rel-16 CR 32.291 Correction on the Resource URI | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197230 | |||
S5‑197231 | Rel-16 CR 32.255 Add the access type | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197232 | Rel-16 CR 32.291 Add the access type | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197233 | Rel-16 CR 32.298 Add the access type | Huawei | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197234 | Rel-16 CR 32.298 Add the Qos Characteristics | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197686 | |||
S5‑197686 | Rel-16 CR 32.298 Add the Qos Characteristics | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197234 | |||
S5‑197235 | Rel-16 CR 32.290 Add the group id for CHF registration | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197687 | |||
S5‑197687 | Rel-16 CR 32.290 Add the group id for CHF registration | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197235 | |||
S5‑197239 | Rel-16 CR 32.298 Correction of handover triggers | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197268 | Rel-15 CR 32.291 Clarify the QoS change trigger | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197665 | S5‑196622 | ||
S5‑197665 | Rel-15 CR 32.291 Clarify the QoS change trigger | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197268 | |||
S5‑197269 | Rel-16 CR 32.291 Clarify the QoS change trigger | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197666 | S5‑196623 | ||
S5‑197666 | Rel-16 CR 32.291 Clarify the QoS change trigger | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197269 | |||
S5‑197281 | Rel-15 CR 32.291 Add Session-AMBR change trigger | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197667 | |||
S5‑197667 | Rel-15 CR 32.291 Add Session-AMBR change trigger | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197281 | |||
S5‑197282 | Rel-16 CR 32.291 Add Session-AMBR change trigger | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197668 | |||
S5‑197668 | Rel-16 CR 32.291 Add Session-AMBR change trigger | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197282 | |||
S5‑197288 | Rel-15 CR 32.298 Correction on unused quota timer | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197669 | |||
S5‑197669 | Rel-15 CR 32.298 Correction on unused quota timer | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197288 | |||
S5‑197289 | Rel-16 CR 32.298 Correction on unused quota timer | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑197350 | Rel-15 CR 32.291 Correction to tariffTimeChange with UTC format | Ericsson | CR | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑197360 | Rel-16 CR 32.291 Correction to tariffTimeChange with UTC format | Ericsson | CR | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑197376 | Rel-15 CR 32.290 Correction to NF consumer identification | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑197670 | |||
S5‑197670 | Rel-15 CR 32.290 Correction to NF consumer identification | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑197376 | |||
S5‑197377 | Rel-16 CR 32.290 Correction to NF consumer identification | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑197671 | |||
S5‑197671 | Rel-16 CR 32.290 Correction to NF consumer identification | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑197377 | |||
S5‑197378 | Rel-15 CR 32.291 Correction to NF consumer identification | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑197379 | Rel-16 CR 32.291 Correction to NF consumer identification | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑197380 | Rel-15 CR 32.298 Correction to NF consumer identification | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑197672 | |||
S5‑197672 | Rel-15 CR 32.298 Correction to NF consumer identification | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑197380 | |||
S5‑197381 | Rel-16 CR 32.298 Correction to NF consumer identification | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑197673 | |||
S5‑197673 | Rel-16 CR 32.298 Correction to NF consumer identification | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑197381 | |||
S5‑197385 | Rel-15 CR 32.291 Correction of binding for 5G data connectivity | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑197681 | |||
S5‑197681 | Rel-15 CR 32.291 Correction of binding for 5G data connectivity | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑197385 | |||
S5‑197387 | Rel-16 CR 32.291 Correction of binding for 5G data connectivity | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑197682 | |||
S5‑197682 | Rel-16 CR 32.291 Correction of binding for 5G data connectivity | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑197387 | |||
S5‑197389 | Rel-15 CR 32.255 Correction of charging rule base name | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑197683 | |||
S5‑197683 | Rel-15 CR 32.255 Correction of charging rule base name | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑197389 | |||
S5‑197390 | Rel-16 CR 32.255 Correction of charging rule base name | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑197684 | |||
S5‑197684 | Rel-16 CR 32.255 Correction of charging rule base name | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑197390 | |||
S5‑197392 | Rel-16 CR 32.290 Definition of state machine | Ericsson | CR | Agreement | Yes |
Yes
| noted | No | S5‑196380 | |||
S5‑197393 | Rel-16 CR 32.290 Correction of redirect at termination | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | S5‑196381 | |||
S5‑197408 | Rel-16 CR 32.291 Correction OpenAPI syntax | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑197661 | Rel-15 CR 32.240 Clarify the Category across specifications | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑197662 | Rel-16 CR 32.240 Clarify the Category across specifications | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | ||||
7.4 | Rel-16 Charging |   | ||||||||||
7.4.1 | Volume Based Charging Aspects for VoLTE | S5‑197356 | Rel-16 CR 32.251 Introduce description of volume based charging for VoLTE in PS | China Mobile Com. Corporation | CR | Approval | Yes |
YesClarify whether the categorization of RG, RG+SI is needed beyond the VolTE bearer
| revised | No | S5‑197483 | |
S5‑197483 | Rel-16 CR 32.251 Introduce description of volume based charging for VoLTE in PS | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑197356 | |||
S5‑197357 | Rel-16 CR 32.251 Introduce description of volume based charging for VoLTE in PS | China Mobile Com. Corporation | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197358 | Rel-16 CR 32.251 Add Caller and Callee information | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑197484 | |||
S5‑197484 | Rel-16 CR 32.251 Add Caller and Callee information | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑197358 | |||
S5‑197361 | Rel-16 CR 32.298 Add Caller and Callee information | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑197485 | |||
S5‑197485 | Rel-16 CR 32.298 Add Caller and Callee information | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑197361 | |||
S5‑197362 | Rel-16 CR 32.299 Add Caller and Callee information | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| revised | No | S5‑197486 | |||
S5‑197486 | Rel-16 CR 32.299 Add Caller and Callee information | China Mobile Com. Corporation | CR | Approval | Yes |
Yes
| agreed | No | S5‑197362 | |||
S5‑197696 | LS on Addition of AVP code definition | SA5 | LS out | Approval | Yes |
Yes
| approved | No | ||||
7.4.2 | Network Exposure Charging in 5G System Architecture | S5‑197365 | Rel-16 CR 32.291 Addition of binding for exposure function northbound API | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑197496 | |
S5‑197496 | Rel-16 CR 32.291 Addition of binding for exposure function northbound API | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑197365 | |||
S5‑197367 | Rel-16 CR 32.291 Addition of attributes in yaml for exposure function northbound API | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑197497 | |||
S5‑197497 | Rel-16 CR 32.291 Addition of attributes in yaml for exposure function northbound API | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑197367 | |||
S5‑197368 | Rel-16 CR 32.298 Addition of CHF CDR for exposure function northbound API | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | ||||
7.4.3 | Charging AMF in 5G System Architecture Phase 1 | S5‑197111 | Rel-16 pCR 32.256 Solve Editor's Note on new triggers activation by CHF | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
YesComments on triggers activation/deactivation at AMF functionality level.
| revised | No | S5‑197487 | |
S5‑197487 | Rel-16 pCR 32.256 Solve Editor's Note on new triggers activation by CHF | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| agreed | No | S5‑197111 | |||
S5‑197112 | Rel-16 pCR 32.256 Solve Editor's Note Multiple Unit Usage | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑197488 | |||
S5‑197488 | Rel-16 pCR 32.256 Solve Editor's Note Multiple Unit Usage | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑197112 | |||
S5‑197113 | Rel-16 pCR 32.256 Introduce PSCELL in location charging | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑197114 | Rel-16 pCR 32.256 Remove Editor's Note event offline scenario | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑197115 | Rel-16 pCR 32.256 Update Registration Charging Information IEs | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑197489 | |||
S5‑197489 | Rel-16 pCR 32.256 Update Registration Charging Information IEs | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| approved | No | S5‑197115 | |||
S5‑197116 | Rel-16 pCR 32.256 Introduce Message flows for roaming | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑197490 | |||
S5‑197490 | Rel-16 pCR 32.256 Introduce Message flows for roaming | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| agreed | No | S5‑197116 | |||
S5‑197117 | Rel-16 pCR 32.256 Introduce Charging information for roaming | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑197118 | Rel-16 CR 32.298 Introduce AMF CHF CDRs | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
YesS5-197440 is merged into S5-197118.
To be checked if S5-197440 does not impact other CRs on ASN.1
Tag nb for NEFinformation is 17 (to be considered here)
| revised | No | S5‑197493 | |||
S5‑197493 | Rel-16 CR 32.298 Introduce AMF CHF CDRs | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197118 | |||
S5‑197119 | Rel-16 CR 32.291 Introduce OpenAPI for AMF charging | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | ||||
S5‑197120 | Rel-16 CR 32.291 Introduce AMF in Nchf Converged Charging | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑197492 | S5‑196253 | ||
S5‑197492 | Rel-16 CR 32.291 Introduce AMF in Nchf Converged Charging | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197120 | |||
S5‑197246 | LS Reply to LS Reply to LS to SA2 Introduction of CHF Address from PCF | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| revised | No | S5‑197495 | |||
S5‑197495 | LS Reply to LS Reply to LS to SA2 Introduction of CHF Address from PCF | SA5 | LS out | Approval | Yes |
Yes
| approved | No | S5‑197246 | |||
S5‑197335 | Rel-16 pCR 32.256 Align detailed message format for charging information | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| revised | No | S5‑197491 | |||
S5‑197491 | Rel-16 pCR 32.256 Align detailed message format for charging information | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| agreed | No | S5‑197335 | |||
S5‑197413 | Rel-16 CR 32.291 Introduction of Binding for AMF Charging | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| revised | No | S5‑197494 | |||
S5‑197494 | Rel-16 CR 32.291 Introduction of Binding for AMF Charging | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197413 | |||
S5‑197440 | Rel-16 CR 32.298 Improvement of ASN.1 chapter CHF CDR | Nokia, Nokia Shanghai Bell | CR | Agreement | Yes |
YesS5-197440 is merged into S5-197118.
To be checked if S5-197440 does not impact other CRs on ASN.1
| merged | No | S5‑197493 | |||
S5‑197498 | TS 32.256 email | Nokia, Nokia Shanghai Bell | other | discussion | No |
No
| reserved | No | ||||
S5‑197499 | TS 32.256 cover sheet for SA approval | Nokia, Nokia Shanghai Bell | TS or TR cover | Approval | Yes |
Yes
| approved | No | ||||
7.4.4 | IMS Charging in 5G System Architecture | S5‑197185 | Rel-16 CR 32.260 CHF selection for IMS charging | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197500 | |
S5‑197500 | Rel-16 CR 32.260 CHF selection for IMS charging | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197185 | |||
S5‑197186 | Rel-16 CR 32.260 IMS charging general description | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197501 | |||
S5‑197501 | Rel-16 CR 32.260 IMS charging general description | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197186 | |||
S5‑197187 | Rel-16 CR 32.260 IMS charging trigger | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197502 | |||
S5‑197502 | Rel-16 CR 32.260 IMS charging trigger | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197187 | |||
S5‑197369 | Rel-16 CR 32.275 Addition of converged flows for TIP, TIR, HOLD and CB | Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑197370 | Rel-16 CR 32.281 Addition of converged flows | Ericsson | CR | Approval | Yes |
Yes
| not pursued | No | ||||
S5‑197503 | Rel-16 CR 32.281 Addition of convergent flows | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑196548 | |||
7.4.5 | Charging aspects of Enhancing Topology of SMF and UPF in 5G Networks | S5‑197045 | Rel-16 CR 32.255 PDU session modification procedure with I-SMF | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑197504 | |
S5‑197504 | Rel-16 CR 32.255 PDU session modification procedure with I-SMF | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑197045 | |||
S5‑197046 | Rel-16 CR 32.255 PDU session release procedure with I-SMF involvement | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑197505 | |||
S5‑197505 | Rel-16 CR 32.255 PDU session release procedure with I-SMF involvement | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑197046 | |||
S5‑197047 | Rel-16 CR 32.255 Charging procedure with I-SMF insertion/change/removal | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑197506 | |||
S5‑197506 | Rel-16 CR 32.255 Charging procedure with I-SMF insertion/change/removal | Ericsson | CR | Approval | No |
Yes
| email approval | No | S5‑197047 | |||
S5‑197048 | Rel-16 CR 32.255 Addition of PSA and UL CL or BP controlled by I-SMF | Ericsson | CR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑197049 | Rel-16 CR 32.255 Removal of PSA and UL CL or BP controlled by I-SMF | Ericsson | CR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑197050 | Rel-16 CR 32.255 Change of PSA for UL CL or BP controlled by I-SMF | Ericsson | CR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑197066 | Rel-16 CR 32.255 5GS to EPS handover using N26 interface with I-SMF | Ericsson | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197067 | Rel-16 CR 32.255 EPS to 5GS handover using N26 interface with I-SMF | Ericsson | CR | Approval | No |
Yes
| withdrawn | Yes | ||||
S5‑197103 | Rel-16 CR 32.255 Adding I-SMF triggers related actions in SMF | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑197507 | |||
S5‑197507 | Rel-16 CR 32.255 Adding I-SMF triggers related actions in SMF | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑197103 | |||
S5‑197188 | Rel-16 CR 32.255 Add I-SMF charging message flow | Huawei | CR | Agreement | Yes |
Yesmerged into S5-197506
| merged | No | S5‑197506 | |||
S5‑197189 | Rel-16 CR 32.255 Add CDR trigger condition for change of I-SMF | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197509 | |||
S5‑197509 | Rel-16 CR 32.255 Add CDR trigger condition for change of I-SMF | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197189 | |||
S5‑197190 | Rel-16 CR 32.255 Add charging ID assigned by SMF with I-SMF | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197510 | |||
S5‑197510 | Rel-16 CR 32.255 Add charging ID assigned by SMF with I-SMF | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197190 | |||
S5‑197257 | Rel-16 CR 32.255 Adding I-SMF controlled UPF triggers & related actions in SMF | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S5‑197508 | |||
S5‑197508 | Rel-16 CR 32.255 Adding I-SMF controlled UPF triggers & related actions in SMF | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑197257 | |||
S5‑197258 | Rel-16 CR 32.291 Adding I-SMF Identifier | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197259 | Rel-16 CR 32.291 adding I-SMF controlled UPF information | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197260 | Rel-16 CR 32.291 adding I-SMF related trigger type | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑197511 | |||
S5‑197511 | Rel-16 CR 32.291 adding I-SMF related trigger type | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197260 | |||
S5‑197261 | Rel-16 CR 32.298 adding I-SMF related SMFTrigger | Ericsson | CR | Agreement | Yes |
Yes
| revised | No | S5‑197514 | |||
S5‑197514 | Rel-16 CR 32.298 adding I-SMF related SMFTrigger | Ericsson | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197261 | |||
S5‑197265 | Rel-16 CR 32.291 Add data type for I-SMF | Huawei | CR | Agreement | Yes |
Yes
| revised | No | S5‑197512 | |||
S5‑197512 | Rel-16 CR 32.291 Add data type for I-SMF | Huawei | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197265 | |||
S5‑197266 | Rel-16 CR 32.291 Add trigger types in the schema for I-SMF | Huawei | CR | Agreement | Yes |
Yesmerged into S5-197511
| merged | No | S5‑197511 | |||
S5‑197267 | Rel-16 CR 32.298 Add trigger types in abstract syntax definition of CHF-CDR for I-SMF | Huawei | CR | Agreement | Yes |
Yesmerged into S5-197514
| merged | No | S5‑197514 | |||
S5‑197366 | Rel-16 CR 32.298 adding I-SMF controlled UPF information | Ericsson | CR | Agreement | Yes |
Yes
| not pursued | No | ||||
S5‑197372 | Rel-16 CR 32.255 Adding ETSUN architecture with I-SMF insertion | Ericsson | CR | Approval | Yes |
Yes
| agreed | No | S5‑196427 | |||
S5‑197436 | Rel-16 CR 32.298 Add NetworkFunctionality for I-SMF | China Mobile Com. Corporation | CR | Yes |
Yes
| revised | No | S5‑197515 | ||||
S5‑197515 | Rel-16 CR 32.298 Add NetworkFunctionality for I-SMF | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197436 | |||
S5‑197439 | Rel-16 CR 32.291 Add serving node information | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| revised | No | S5‑197513 | |||
S5‑197513 | Rel-16 CR 32.291 Add serving node information | China Mobile Com. Corporation | CR | Agreement | Yes |
Yes
| agreed | No | S5‑197439 | |||
S5‑197446 | Rel-16 CR 32.255 Remove Editor's note of PDU Session establishment with I-SMF insertion | Ericsson. | CR | Agreement | Yes |
Yes
| not treated | No | ||||
S5‑197544 | Add I-SMF charging message flow for handover | Huawei | CR | Agreement | Yes |
Yes
| not treated | No | ||||
7.4.6 | Network Slice Performance and Analytics Charging in 5G System | S5‑197173 | Discussion paper on charging information | Huawei | discussion | Agreement | Yes |
Yes
| noted | No | ||
S5‑197174 | Rel-16 pCR 28.201 Add high level 5G System architecture to clause 4.1 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑197516 | |||
S5‑197516 | Rel-16 pCR 28.201 Add high level 5G System architecture to clause 4.1 | Huawei | pCR | Agreement | Yes |
Yes
| agreed | No | S5‑197174 | |||
S5‑197175 | Rel-16 pCR 28.201 Add charging architecture to clause 4.1 | Huawei | pCR | Agreement | Yes |
Yesmerged into S5-197517
| merged | No | S5‑197517 | |||
S5‑197176 | Rel-16 pCR 28.201 Add charging requirements to clause 5.1 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑197519 | |||
S5‑197519 | Rel-16 pCR 28.201 Add charging requirements to clause 5.1 | Huawei | pCR | Agreement | Yes |
Yes
| agreed | No | S5‑197176 | |||
S5‑197177 | Rel-16 pCR 28.201 Add information description to clause 5.1 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑197520 | |||
S5‑197520 | Rel-16 pCR 28.201 Add information description to clause 5.1 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑197177 | |||
S5‑197178 | Rel-16 pCR 28.201 Add discovery and selection to clause 5.1 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑197521 | |||
S5‑197521 | Rel-16 pCR 28.201 Add discovery and selection to clause 5.1 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑197178 | |||
S5‑197179 | Rel-16 pCR 28.201 Add service consumer | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑197180 | Rel-16 pCR 28.201 Add basic principles to clause 5.2 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑197522 | |||
S5‑197522 | Rel-16 pCR 28.201 Add basic principles to clause 5.2 | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | S5‑197180 | |||
S5‑197181 | Rel-16 pCR 28.201 Add applicable triggers to clause 5.2 | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑197182 | Rel-16 pCR 28.201 Add NWDAF message flows to clause 5.2 | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑197183 | Rel-16 pCR 28.201 Add message flow | Huawei | pCR | Agreement | Yes |
Yes
| noted | No | ||||
S5‑197184 | Rel-16 pCR 28.201 Add CDR generation to clause 5.2 | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑197523 | |||
S5‑197523 | Rel-16 pCR 28.201 Add CDR generation to clause 5.2 | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑197184 | |||
S5‑197348 | Rel-16 pCR TS 28.201 Add high level description | Huawei | pCR | Agreement | No |
Yes
| withdrawn | Yes | ||||
S5‑197349 | Rel-16 pCR TS 28.201 Add high level description | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑197518 | |||
S5‑197518 | Rel-16 pCR TS 28.201 Add high level description | Huawei | pCR | Agreement | Yes |
Yes
| agreed | No | S5‑197349 | |||
S5‑197373 | Rel-16 pCR 28.201 Architecture considerations | Ericsson | pCR | Agreement | Yes |
Yes
| revised | No | S5‑197517 | |||
S5‑197517 | Rel-16 pCR 28.201 Architecture considerations | Ericsson | pCR | Agreement | Yes |
Yes
| agreed | No | S5‑197373 | |||
S5‑197524 | TS 28.201 email | charging | other | discussion | No |
No
| reserved | No | ||||
7.4.7 | Network Slice Management Charging in 5G System | S5‑197068 | Add Architecture Considerations | Openet Telecom | pCR | Approval | Yes |
Yes
| noted | No | ||
S5‑197343 | Rel-16 pCR 28.202 Introduce Scope and references | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑197344 | Rel-16 pCR 28.202 Introduce Architecture | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| noted | No | ||||
S5‑197345 | Rel-16 pCR 28.202 Introduce Charging principles | Nokia, Nokia Shanghai Bell | pCR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑197374 | Rel-16 pCR 28.202 Architecture considerations | Ericsson | pCR | Agreement | Yes |
Yes
| noted | No | ||||
7.4.8 | Charging Access Traffic Steering, Switching and Splitting in 5G system architecture (preliminary work before SA approval) |   | ||||||||||
7.4.9 | Charging Aspect for 5WWC (preliminary work before SA approval) | S5‑197336 | Rel-16 draftCR 32.255 Add 5WWC architecture diagram | Huawei | draftCR | Yes |
Yes
| revised | No | S5‑197688 | ||
S5‑197688 | Rel-16 draftCR 32.255 Add 5WWC architecture diagram | Huawei | draftCR | - | Yes |
Yes
| agreed | No | S5‑197336 | |||
S5‑197337 | Rel-16 draftCR 32.255 Add 5WWC charging requirements | Huawei | draftCR | Yes |
Yes
| revised | No | S5‑197689 | ||||
S5‑197689 | Rel-16 draftCR 32.255 Add 5WWC charging requirements | Huawei | draftCR | - | Yes |
Yes
| agreed | No | S5‑197337 | |||
S5‑197338 | Rel-16 draftCR 32.255 Add precedure for 5G RG scenario | Huawei | draftCR | Yes |
Yes
| revised | No | S5‑197690 | ||||
S5‑197690 | Rel-16 draftCR 32.255 Add precedure for 5G RG scenario | Huawei | draftCR | Approval | Yes |
Yes
| approved | No | S5‑197338 | |||
S5‑197339 | Rel-16 draftCR 32.255 Add precedure for FN RG scenario | Huawei | draftCR | Yes |
Yes
| not treated | No | |||||
S5‑197340 | Rel-16 draftCR 32.255 Add handover of a PDU Session for 5G RG | Huawei | draftCR | Yes |
Yes
| not treated | No | |||||
S5‑197341 | Rel-16 draftCR 32.255 Add description on identifier in a PDU session for 5G RG and FN RG | Huawei | draftCR | Yes |
Yes
| revised | No | S5‑197691 | ||||
S5‑197691 | Rel-16 draftCR 32.255 Add description on identifier in a PDU session for 5G RG and FN RG | Huawei | draftCR | - | Yes |
Yes
| approved | No | S5‑197341 | |||
S5‑197342 | Rel-16 draftCR 32.255 Add description on charging information | Huawei | draftCR | Yes |
Yes
| not treated | No | |||||
7.4.10 | CHF-controlled quota management (preliminary work before SA approval) | S5‑197375 | Rel-16 Discussion on quota management control | Ericsson | discussion | Discussion | Yes |
Yes
| not treated | No | ||
S5‑197457 | Introduce CHF-Controlled Quota Management | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑197458 | Add CHF-Controlled Quota Management functionality | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑197459 | Add Quota Management Suspend and Resume Result Codes | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| not treated | No | ||||
S5‑197460 | Add Quota Management Suspend and Resume Result Codes in yaml | Amdocs Software Systems Ltd | CR | Approval | Yes |
Yes
| not treated | No | ||||
7.5 | Charging Studies |   | ||||||||||
7.5.1 | Study on Charging Aspects of Network Slicing | S5‑197172 | Rel-16 pCR TR 32.845 Remove the editor's note about capacity based charging | Huawei | pCR | Agreement | Yes |
Yes
| revised | No | S5‑197525 | |
S5‑197525 | Rel-16 pCR TR 32.845 Remove the editor's note about capacity based charging | Huawei | pCR | Agreement | Yes |
Yes
| approved | No | S5‑197172 | |||
S5‑197526 | Rel-16 pCR TR 32.845 Conclusion of the study | Huawei | pCR | Approval | Yes |
Yes
| agreed | No | ||||
S5‑197527 | TR 32.845 email | Huawei | draft TR | Approval | No |
No
| reserved | No | ||||
S5‑197528 | TR 32.845 cover sheet SA approval | Huawei | TS or TR cover | Information | Yes |
Yes
| agreed | No | ||||
8 | Any Other Business |   | ||||||||||
9 | Closing of the meeting |   |