TDoc | Title | Source |
---|---|---|
S5-251200 | Agenda | WG Chair |
TDoc | Title | Source |
---|---|---|
S5-251201 | IPR and legal declaration | WG Chair |
TDoc | Title | Source |
---|---|---|
S5-251202 | Report from last SA5 meeting | MCC |
TDoc | Title | Source |
---|---|---|
S5-251203 | Time Plan for SA5 Plenary and OAM sessions | WG Chair |
S5-251204 | agenda_with_Tdocs_sequence_Plenary&OAM | WG Chair |
S5-251205 | SA5 working procedures | WG Chair |
S5-251206 | SA5 Meeting facility requirements | WG Chair |
S5-251208 | Post meeting email approval status | WG Vice Chair (Ericsson) |
S5-251211 | Plenary and OAM Chair notes and conclusions | WG Chair |
S5-251214 | Rel-19 SA5 work plan TU table | WG Chair |
S5-251218 | Latest SA5 Rel-19 WIs-SIs | WG Chair |
S5-251219 | Rel-19 SA5 work planning | WG Chair |
S5-251220 | Rel-20 SA5 work planning | WG Chair |
S5-251413 | Maintenance of TSs in SA5 | Ericsson |
S5-251758 | Selecting the Release for the SA5 OAM and Charging aspects | SA5 leadership & MCC |
S5-251766 | Rel-19 SA5 work planning | WG Chair |
S5-251767 | Rel-20 SA5 work planning | WG Chair |
S5-251769 | Maintenance of TSs in SA5 | Ericsson |
S5-251770 | Selecting the Release for the SA5 OAM and Charging aspects | SA5 leadership & MCC |
S5-252112 | SA5 working procedures | WG Chair |
S5-252122 | Rel-19 SA5 work plan TU table | WG Chair |
TDoc | Title | Source |
---|---|---|
S5-251328 | LS on Ambient IoT progress of RAN3 | RAN3 |
S5-251330 | Publication of ETSI NFV group report on architectural support for NFV evolution | ETSI ISG NFV |
S5-251409 | Reply LS on per-UE UE performance metrics | SA5 |
S5-251768 | LS to SA for guidance of maintenance of specifications | SA5 |
S5-251771 | LS response on Ambient IoT progress of RAN3 | SA5 |
S5-252049 | LS reply to ETSI NFV for the publication of NFV-IFA054 | SA5 |
S5-252056 | Reply LS on per-UE UE performance metrics | SA5 |
S5-252123 | LS to SA for guidance of maintenance of specifications | SA5 |
TDoc | Title | Source |
---|---|---|
S5-251207 | SA5 meeting calendar | WG Chair |
TDoc | Title | Source |
---|---|---|
S5-251316 | New Study on AI/ML management enhancements | NEC, Intel |
S5-251366 | New WID on OAM for XR and media services (XRM) | ZTE Corporation |
S5-251387 | New SID on energy efficiency and energy saving aspects of 5G Advanced | Huawei |
S5-251453 | SA5 Rel-20 5GA 25Q1 moderated discussion – ISAC management | ZTE Corporation |
S5-251489 | New SID on SBMA enhancement phase 4 | Moderator (Huawei) |
S5-251498 | New SID on Management aspect of Network Digital Twins phase 2 | China Mobile |
S5-251558 | New SID Study on intent driven management services for mobile network phase 4 | Moderator (Huawei, Ericsson) |
S5-251593 | WID on Study on Management Data Analytics (MDA) – Phase 4 | Huawei Tech. Japan, K.K. |
S5-251634 | New SID on cloud aspects of management and orchestration phase 2 | China Mobile |
S5-251652 | New SID on Semantic-based Network Management | Moderator(China Unicom, Samsung) |
S5-251740 | New SID on Study for Data management phase 3 | Nokia |
S5-251772 | New Study on AI/ML management enhancements | NEC, Intel |
S5-251773 | New WID on OAM for XR and media services (XRM) | ZTE Corporation |
S5-251774 | New SID on energy efficiency and energy saving aspects of 5G Advanced | Huawei |
S5-251775 | New SID on SBMA enhancement phase 4 | Moderator (Huawei) |
S5-251776 | New SID on Management aspect of Network Digital Twins phase 2 | China Mobile |
S5-251777 | New SID Study on intent driven management services for mobile network phase 4 | Moderator (Huawei, Ericsson) |
S5-251778 | WID on Study on Management Data Analytics (MDA) – Phase 4 | Huawei Tech. Japan, K.K. |
S5-251779 | New SID on cloud aspects of management and orchestration phase 2 | China Mobile |
S5-251780 | New SID on Semantic-based Network Management | Moderator(China Unicom, Samsung) |
S5-251781 | New SID on Study for Data management phase 3 | Nokia, Verizon |
S5-252124 | New SID on Study for Data management phase 3 | Nokia, Verizon |
TDoc | Title | Source |
---|---|---|
S5-251209 | OAM action list | WG Vice Chair (Nokia) |
S5-251210 | OAM Exec Report | WG Vice Chair (Nokia) |
S5-251212 | Collection of useful endorsed documents in OAM | WG Vice Chair (Nokia) |
S5-251213 | Collection of external communication documents in OAM | WG Vice Chair (Nokia) |
S5-251221 | OAM breakout notes | WG Chair |
S5-251222 | Support Continuous MDT on reply to RAN3 incoming LS (R3-250788) | Ericsson, AT&T, CMCC, Deutsche Telekom |
S5-251223 | Reply LS to LS on Continuous MDT | SA5 |
S5-251226 | LS on the new NGMN Publication: ‘MLOps for Highly Autonomous Network’ | NGMN Alliance |
S5-251314 | Reply LS to ITU-T SG2 on methodology coordination | SA5 |
S5-251322 | LS on 5G Trace to support UE level measurement (SA5#159) | CT4 |
S5-251323 | LS reply to LS on energy information collection from OAM to EIF | CT |
S5-251324 | LS on per-UE UE performance metrics (SA5#159) | RAN3 |
S5-251325 | Reply LS on MBS Communication Service Type | RAN3 |
S5-251326 | LS on Continuous MDT | RAN3 |
S5-251327 | Reply LS on OAM requirements to support regenerative payload transport links | RAN3 |
S5-251331 | LS on the initiation of a new Technical Report ITU-T TR.M.rnscesnr “Requirements of network service consistency evaluation for shared network resources” | ITU-T SG2 |
S5-251332 | LS/r on methodology harmonization update (reply to 3GPP TSG SA5-244109 - LS57) | ITU-T SG2 |
S5-251372 | LS on the consent of Recommendation ITU-T M. 3042(ex. M.fcnhe): "Framework of communication network health evaluation" | ITU-T SG2 |
S5-251615 | LS reply to LS on 5G Trace to support UE level measurement | SA5 |
S5-251741 | Continuous MDT Discussion | Nokia |
S5-251742 | Reply LS on Continuous MDT | SA5 |
S5-251990 | LS to SA3 on management of secure backhaul for NTN | SA5 |
S5-252050 | Support Continuous MDT on reply to RAN3 incoming LS (R3-250788) | Ericsson, AT&T, CMCC, Deutsche Telekom, ZTE |
S5-252051 | Reply LS to LS on Continuous MDT | SA5 |
S5-252052 | Continuous MDT Discussion | Nokia |
S5-252053 | Reply LS to RAN3 LS on Continuous MDT | SA5 |
S5-252055 | LS reply to LS on 5G Trace to support UE level measurement | SA5 |
S5-252113 | LS reply to LS on 5G Trace to support UE level measurement | SA5 |
S5-252114 | Reply LS to RAN3 LS on Continuous MDT | SA5 |
TDoc | Title | Source |
---|---|---|
S5-251230 | Revised WID on 5G performance measurements and KPIs phase 4 | Ericsson LM |
S5-251627 | Rel-19 Revised WID on Management Aspects of NTN Phase 2 | CATT, China Unicom |
S5-252022 | Rel-19 Revised WID on Management Aspects of NTN Phase 2 | CATT, China Unicom |
TDoc | Title | Source |
---|---|---|
S5-251529 | Revised WID on Management Aspects of NTN Phase 2 | Samsung R&D Institute UK |
TDoc | Title | Source |
---|---|---|
S5-251664 | Rel-17 CR TS 28.310 Clarify information of service | Ericsson, Deutsche Telekom |
S5-251665 | Rel-18 CR TS 28.310 Clarify information of service | Ericsson, Deutsche Telekom |
S5-251666 | Rel-19 CR TS 28.310 Clarify information of service | Ericsson, Deutsche Telekom |
S5-252102 | Rel-17 CR TS 28.310 Clarify information of service | Ericsson, Deutsche Telekom |
TDoc | Title | Source |
---|---|---|
S5-251429 | Rel-16 CR 28.541 Update for allowed value ueAccProbabilityDist (stage3, yang) | Ericsson Canada Inc. |
S5-251430 | Rel-17 CR 28.541 Update for allowed value ueAccProbabilityDist (stage3, yang) | Ericsson Canada Inc. |
S5-251431 | Rel-18 CR 28.541 Update for allowed value ueAccProbabilityDist (stage3, yang) | Ericsson Canada Inc. |
S5-251432 | Rel-19 CR 28.541 Update for allowed value ueAccProbabilityDist (stage3, yang) | Ericsson Canada Inc. |
S5-252103 | Rel-17 CR 28.541 Update for allowed value ueAccProbabilityDist (stage3, yang) | Ericsson Canada Inc. |
S5-252104 | Rel-19 CR 28.541 Update for allowed value ueAccProbabilityDist (stage3, yang) | Ericsson Canada Inc. |
TDoc | Title | Source |
---|---|---|
S5-251667 | Rel-16 CR TS 28.530 Clarify tenant information concept | Ericsson, Deutsche Telekom |
S5-251668 | Rel-17 CR TS 28.530 Clarify tenant information concept | Ericsson, Deutsche Telekom |
S5-251669 | Rel-18 CR TS 28.530 Clarify tenant information concept | Ericsson, Deutsche Telekom |
S5-251670 | Rel-19 CR TS 28.530 Clarify tenant information concept | Ericsson, Deutsche Telekom |
TDoc | Title | Source |
---|---|---|
S5-251295 | Rel19 CR TS28.541 correction to inconsistency between stage 2 and stage 3 concerning SubNetwork and ManagedElement containment | Nokia, Nokia Shanghai Bell |
S5-251296 | Rel18 CR TS28.541 correction to inconsistency between stage 2 and stage 3 concerning SubNetwork and ManagedElement containment | Nokia, Nokia Shanghai Bell |
S5-251297 | Rel18 CR TS28.541 correction to stage 3 of SatelliteBackhaulInfo | Nokia, Nokia Shanghai Bell |
S5-251298 | Rel19 CR TS28.541 correction to stage 3 of SatelliteBackhaulInfo | Nokia, Nokia Shanghai Bell |
S5-251418 | Rel-17 CR 28.622 Change dnPrefix properties | Ericsson India Private Limited |
S5-251419 | Rel-17 CR 28.622 Change dnPrefix properties | Ericsson India Private Limited |
S5-251420 | Rel-18 CR 28.622 Change dnPrefix properties | Ericsson India Private Limited |
S5-251421 | Rel-19 CR 28.622 Change dnPrefix properties | Ericsson India Private Limited |
S5-251424 | Rel-17 CR 28.623 Change dnPrefix properties | Ericsson India Private Limited |
S5-251425 | Rel-18 CR 28.623 Change dnPrefix properties | Ericsson India Private Limited |
S5-251426 | Rel-19 CR 28.623 Change dnPrefix properties | Ericsson India Private Limited |
S5-251595 | Rel-17 CR TS 28.541 Fix invalid reference | Huawei |
S5-251703 | Rel15 CR TS 32.156 Enhancement of the description of the “isNotifyable” attribute property | Nokia |
S5-251704 | Rel16 CR TS 32.156 Enhancement of the description of the “isNotifyable” attribute property and correction of the default value for the “isReadable” attribute property | Nokia |
S5-251705 | Rel17 CR TS 32.156 Enhancement of the description of the “isNotifyable” attribute property and correction of the default value for the “isReadable” attribute property | Nokia |
S5-251706 | Rel18 CR TS 32.156 Enhancement of the description of the “isNotifyable” attribute property and correction of the default value for the “isReadable” attribute property | Nokia |
S5-251707 | Rel19 CR TS 32.156 Enhancement of the description of the “isNotifyable” attribute property and correction of the default value for the “isReadable” attribute property | Nokia |
S5-252096 | Rel-19 CR TS 28.541 Fix invalid reference | Huawei |
S5-252105 | Rel19 CR TS28.541 correction to inconsistency between stage 2 and stage 3 concerning SubNetwork and ManagedElement containment | Nokia, Nokia Shanghai Bell |
S5-252106 | Rel19 CR TS28.541 correction to stage 3 of SatelliteBackhaulInfo | Nokia, Nokia Shanghai Bell |
S5-252107 | Rel19 CR TS 32.156 Enhancement of the description of the “isNotifyable” attribute property and correction of the default value for the “isReadable” attribute property | Nokia |
TDoc | Title | Source |
---|---|---|
S5-251349 | Rel19 CR TS28.104 correction to reference | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
S5-251673 | Rel-18 CR TS 28.317 Correct import table | Ericsson, Deutsche Telekom |
S5-251674 | Rel-19 CR TS 28.317 Correct import table | Ericsson, Deutsche Telekom |
TDoc | Title | Source |
---|---|---|
S5-251624 | Rel 18 CR TS 28.104 Correct References for MDA reporting | Ericsson |
S5-251625 | Rel 19 CR TS 28.104 Correct References for MDA reporting | Ericsson |
S5-252057 | Rel 19 CR TS 28.104 Correct References for MDA reporting | Ericsson |
TDoc | Title | Source |
---|---|---|
S5-251352 | Rel-18 CR TS 28.105 Correction on the isWritable propoerty of AIMLInferenceName in the MLTrainingRequest | ZTE Corporation, Intel, Huawei |
S5-251353 | Rel-19 CR TS 28.105 Correction on the isWritable propoerty of AIMLInferenceName in the MLTrainingRequest | ZTE Corporation, Intel, Huawei |
TDoc | Title | Source |
---|---|---|
S5-251671 | Rel-18 CR TS 28.312 Correct import table | Ericsson, Deutsche Telekom |
S5-251672 | Rel-19 CR TS 28.312 Correct import table | Ericsson, Deutsche Telekom |
S5-252058 | Rel-18 CR TS 28.312 Correct import table | Ericsson, Deutsche Telekom |
S5-252059 | Rel-19 CR TS 28.312 Correct import table | Ericsson, Deutsche Telekom |
TDoc | Title | Source |
---|---|---|
S5-251416 | Rel-18 CR 28.111 How to use notifyPotentialFaultyAlarmList | Ericsson India Private Limited |
S5-251417 | Rel-19 CR 28.111 How to use notifyPotentialFaultyAlarmList | Ericsson India Private Limited |
S5-251438 | Rel-19 CR 28.622 Remove deprecated notification | Ericsson India Private Limited |
S5-251439 | Rel-19 CR 28.541 Remove deprecated notification | Ericsson India Private Limited |
S5-251451 | Rel-18 CR 28.623 Modify YANG mapping of Subnetwork | Ericsson India Private Limited |
S5-251452 | Rel-19 CR 28.623 Modify YANG mapping of Subnetwork | Ericsson India Private Limited |
S5-251459 | Rel-18 CR 28.541 Modify YANG mapping of Subnetwork | Ericsson India Private Limited |
S5-251461 | Rel-19 CR 28.541 Modify YANG mapping of Subnetwork | Ericsson India Private Limited |
S5-251479 | Rel-18 CR TS 28.111 Add missing solution components | Huawei |
S5-251480 | Rel-19 CR TS 28.111 Add missing solution components | Huawei |
S5-251481 | Rel-18 CR TS 28.111 Correction on reliability of alarm lists | Huawei |
S5-251482 | Rel-19 CR TS 28.111 Correction on reliability of alarm lists | Huawei |
S5-251543 | Rel 18 CR TS 28.532 correct the format of scope parameter to align with stage3 | HUAWEI |
S5-251544 | Rel 19 CR TS 28.532 correct the scope operation parameter in stage 3 | Huawei |
S5-251562 | Rel-18 CR TS 28.111 Clarify notifyChangedAlarmGeneral | Huawei, Ericsson |
S5-251563 | Rel-19 CR TS 28.111 Clarify notifyChangedAlarmGeneral | Huawei, Ericsson |
S5-251564 | Rel-18 CR TS 28.111 Add missing ThresholdInfo dataType and related definition | Huawei |
S5-251565 | Rel-19 CR TS 28.111 Add missing ThresholdInfo dataType and related definition | Huawei |
S5-251730 | Rel-19 CR 28.622 Add new generic type KeyValueList | Ericsson India Private Limited |
S5-251938 | Rel-19 CR 28.622 Add new generic type KeyValueList | Ericsson India Private Limited |
S5-252060 | Rel-18 CR 28.111 How to use notifyPotentialFaultyAlarmList | Ericsson India Private Limited |
S5-252061 | Rel-19 CR 28.111 How to use notifyPotentialFaultyAlarmList | Ericsson India Private Limited |
S5-252062 | Rel-19 CR 28.622 Remove deprecated notification | Ericsson India Private Limited |
S5-252063 | Rel-19 CR 28.541 Remove deprecated notification | Ericsson India Private Limited |
S5-252064 | Rel-18 CR TS 28.111 Correction on reliability of alarm lists | Huawei |
S5-252065 | Rel-19 CR TS 28.111 Correction on reliability of alarm lists | Huawei |
S5-252066 | Rel 18 CR TS 28.532 correct the format of scope parameter to align with stage3 | HUAWEI |
S5-252067 | Rel 19 CR TS 28.532 correct the scope operation parameter in stage 3 | Huawei |
S5-252068 | Rel-18 CR TS 28.111 Add missing ThresholdInfo dataType and related definition | Huawei, Nokia, Ericsson |
S5-252069 | Rel-19 CR TS 28.111 Add missing ThresholdInfo dataType and related definition | Huawei, Nokia |
TDoc | Title | Source |
---|---|---|
S5-251616 | Rel-18 CR 32.422 Clarification on SMF obtaining Trace control and measurement parameters from UDM | Huawei |
S5-251617 | Rel-18 CR 32.422 Clarification on SMF obtaining trace control and configuration parameters from UDM | Huawei |
S5-252070 | Rel-19 CR 32.422 Clarification on SMF obtaining Trace control and measurement parameters from UDM | Huawei, Ericsson |
S5-252071 | Rel-19 CR 32.422 Clarification on SMF obtaining trace control and configuration parameters from UDM | Huawei, Ericsson |
TDoc | Title | Source |
---|---|---|
S5-251234 | Rel-18 CR TS 28.552 Corrections of subcounters and filters | Ericsson, Rakuten Mobile, Samsung |
S5-251235 | Rel-19 CR TS 28.552 Corrections of subcounters and filters | Ericsson, Rakuten Mobile, Samsung |
S5-251236 | Rel-18 CR TS 28.552 Distribution of UE throughput | Ericsson |
S5-251237 | Rel-19 CR TS 28.552 Distribution of UE throughput | Ericsson |
S5-251587 | Rel-19 CR 28.532 Enhance notifyFilePreparationError definition | Ericsson Canada Inc. |
S5-251597 | Rel-18 CR TS 28.552 PLMN name inconsistency | Ericsson |
S5-251598 | Rel-19 CR TS 28.552 PLMN name inconsistency | Ericsson |
S5-251692 | Rel-18 CR TS28.552 Add missing EP_N9 for GTP capacity related measurements | ZTE Corporation |
S5-251693 | Rel-19 CR TS28.552 Add missing EP_N9 for GTP capacity related measurements | ZTE Corporation |
S5-251737 | Rel-19 CR TS 28.558 Correction on the UE identifer | Nokia |
S5-251738 | Rel-19 CR TS 28.552 Corrections on Filter Definition | Nokia |
S5-251739 | Rel-19 CR TS 28.552 Corrections on Filter Definition | Nokia |
S5-252072 | Rel-18 CR TS 28.552 Corrections of subcounters and filters | Ericsson, Rakuten Mobile, Samsung, Nokia |
S5-252073 | Rel-19 CR TS 28.552 Corrections of subcounters and filters | Ericsson, Rakuten Mobile, Samsung, Nokia |
S5-252074 | Rel-19 CR 28.532 Enhance notifyFilePreparationError definition | Ericsson Canada Inc. |
S5-252075 | Rel-18 CR TS 28.552 PLMN name inconsistency | Ericsson |
S5-252076 | Rel-19 CR TS 28.552 PLMN name inconsistency | Ericsson |
S5-252077 | Rel-19 CR TS 28.558 Correction on the UE identifer | Nokia, Ericsson |
TDoc | Title | Source |
---|---|---|
S5-251350 | Rel-18 CR TS 28.541 Typo corrections and missing definitions | ZTE Corporation, Orange |
S5-251351 | Rel-19 CR TS 28.541 Typo corrections and missing definitions | ZTE Corporation, Orange |
S5-251659 | Rel-19 CR 28.541 Align predefinedPccRuleSet attributes with the definitions in TS 29.512 | Ericsson, Deutsche Telekom |
S5-251689 | Rel-19 CR TS28.541 Fix isOrdered and isUnique Attribute properties | ZTE Corporation |
S5-252078 | Rel-18 CR TS 28.541 Typo corrections and missing definitions | ZTE Corporation, Orange, Nokia |
S5-252079 | Rel-19 CR TS 28.541 Typo corrections and missing definitions | ZTE Corporation, Orange, Nokia |
S5-252080 | Rel-19 CR 28.541 Align predefinedPccRuleSet attributes with the definitions in TS 29.512 | Ericsson, Deutsche Telekom |
TDoc | Title | Source |
---|---|---|
S5-251591 | Rel-18 CR 28541 Correct support qualifier condition for ephemerisInfoSetRef | Ericsson |
S5-251690 | Rel-18 CR TS28.541 Fix nTNTAClist for stage 3 OpenAPI | ZTE Corporation |
S5-251691 | Rel-19 CR TS28.541 Fix nTNTAClist for stage 3 OpenAPI | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
S5-251561 | Rel-18 CR TS 28.557 Update procedure of management of tenant to align with access control solution | Huawei |
S5-251729 | Rel-18 CR TS 28.557 Fix wrong references and correct solution for NPN-SC mgmt | Ericsson GmbH, Eurolab |
S5-252081 | Rel-18 CR TS 28.557 Update procedure of management of tenant to align with access control solution | Huawei, Ericsson |
S5-252082 | Rel-18 CR TS 28.557 Fix wrong references and correct solution for NPN-SC mgmt | Ericsson GmbH, Eurolab |
TDoc | Title | Source |
---|---|---|
S5-251716 | Rel-18 CR TS 28.318 Fix affectedArea attribute for DSO service outage use case | Ericsson GmbH, Eurolab |
S5-251717 | Rel-19 CR TS 28.318 Fix affectedArea attribute for DSO service outage use case | Ericsson GmbH, Eurolab |
TDoc | Title | Source |
---|---|---|
S5-251233 | Rel-18 CR TS 32.404 Corrections on measurement name size | Ericsson |
S5-251282 | Rel-18 CR 28.111 YANG stage-3 corrections | Ericsson India Private Limited |
S5-251283 | Rel-19 CR 28.111 YANG stage-3 corrections | Ericsson India Private Limited |
S5-251284 | Rel-18 CR 28.623 YANG stage-3 corrections | Ericsson India Private Limited |
S5-251285 | Rel-19 CR 28.623 YANG stage-3 corrections | Ericsson India Private Limited |
S5-251286 | Rel-18 CR 28.623 YANG stage-3 corrections | Ericsson India Private Limited |
S5-251289 | Rel-18 CR 28.541 YANG stage-3 corrections | Ericsson India Private Limited |
S5-251290 | Rel-19 CR 28.541 YANG stage-3 corrections | Ericsson India Private Limited |
S5-251406 | Rel-18 CR TS 28.111 Correction on Alarm Definition | NTT DOCOMO, Ericsson |
S5-251407 | Rel-19 CR TS 28.111 Correction on Alarm Definition | NTT DOCOMO, Ericsson |
S5-252083 | Rel-18 CR 28.111 YANG stage-3 corrections | Ericsson India Private Limited |
S5-252084 | Rel-19 CR 28.111 YANG stage-3 corrections | Ericsson India Private Limited |
TDoc | Title | Source |
---|---|---|
S5-251239 | Rel-19 CR TS 28.560 Corrections on networkInterfaceTypeList | Ericsson, Vodafone |
S5-251240 | Rel-19 CR TS 28.560 Corrections on PCAPNG header | Ericsson, Vodafone |
S5-251287 | Addressing ENs in TS 28.560 | Vodafone, Ericsson |
S5-251288 | Removal of already addressed Editor's Note | Vodafone |
S5-251380 | Rel-19 CR TS 28.622 Correct misalignment issue for notificationTypes in stage2 and stage3 | Huawei |
S5-251382 | Rel-19 CR TS 28.623 Update the YANG definition for notificationTypes to align with stage 2 definition | Huawei |
S5-251383 | Rel-19 CR TS 28.533 Correct wrong references | Huawei |
S5-251384 | Rel-19 CR TS 28.533 Fix errors in clause 4.5 | Huawei |
S5-251385 | Rel-19 CR TS 28.533 Correct note in clause 3.1 | Huawei |
S5-251389 | Rel-19 CR TS 28.623 Implement the writeOnly property for triggerHeartbeatNtf | Huawei |
S5-251390 | Rel-19 CR TS 28.622 Update Attribute constraints for TimeWindow | Huawei |
S5-251391 | Rel-19 CR TS 28.537 Correct procedures for heartbeat | Huawei |
S5-251414 | Addressing EN for supporting type of signalling | Vodafone, Samsung |
S5-251415 | Removal of Editor's Note on encoding | Vodafone |
S5-251500 | Rel-19 CR TS 28.622 Corrections of Trace Reference Notifications | Nokia |
S5-251557 | Rel-19 CR 28.541 Add control attribute for LTM cell switch | Ericsson |
S5-251621 | Rel 19 CR TS 28.541 Remove support qualifier from attribute constraints for NR NRM | Ericsson |
S5-251622 | Rel 19 CR TS 28.541 Remove support qualifier from attribute constraints for Network Slice NRM | Ericsson |
S5-251623 | Rel 19 CR TS 28.541 Remove support qualifier from attribute constraints for 5GC NRM | Ericsson |
S5-251628 | Rel-19 CR TS 28.541 Correction on wrong attribute property definition.docx | CATT |
S5-251649 | Correct the description of maximum number of PDU sessions of network slice | Huawei |
S5-251726 | Rel-19 CR TS 28.622 Correction of Area Scope Parameter | Nokia |
S5-251727 | Rel-19 CR TS 32.422 Correction of Area Scope Parameter | Nokia |
S5-252085 | Rel-19 CR TS 28.560 Corrections on networkInterfaceTypeList | Ericsson, Vodafone |
S5-252086 | Rel-19 CR TS 28.560 Corrections on PCAPNG header | Ericsson, Vodafone |
S5-252087 | Addressing ENs in TS 28.560 | Vodafone, Ericsson, Nokia, Deutsche Telekom |
S5-252088 | Removal of already addressed Editor's Note | Vodafone, Nokia, Ericsson, Deutsche Telekom |
S5-252089 | Addressing EN for supporting type of signalling | Vodafone, Samsung, Ericsson |
S5-252090 | Removal of Editor's Note on encoding | Vodafone |
S5-252092 | Rel-19 CR TS 28.623 Update the YANG definition for notificationTypes to align with stage 2 definition | Huawei |
S5-252093 | Rel-19 CR TS 28.533 Corrections | Huawei |
S5-252094 | Rel-19 CR TS 28.622 Update Attribute constraints for TimeWindow | Huawei |
S5-252095 | Rel-19 CR 28.541 Add control attribute for LTM cell switch | Ericsson |
S5-252097 | Rel 19 CR TS 28.541 Remove support qualifier from attribute constraints for NR NRM | Ericsson |
S5-252098 | Rel 19 CR TS 28.541 Remove support qualifier from attribute constraints for Network Slice NRM | Ericsson |
S5-252099 | Rel 19 CR TS 28.541 Remove support qualifier from attribute constraints for 5GC NRM | Ericsson |
S5-252100 | Rel-19 CR TS 28.541 Correction on wrong attribute property definition.docx | CATT |
S5-252101 | Correct the description of maximum number of PDU sessions of network slice | Huawei |
S5-252115 | Rel-19 CR TS 28.623 Update the YANG definition for notificationTypes to align with stage 2 definition | Huawei |
TDoc | Title | Source |
---|---|---|
S5-251258 | Input to draftCR TS28.105 Coordination AIML inference | Nokia |
S5-251259 | Input to draftCR TS28.105 Enhance AIML inference emulation | Nokia |
S5-251260 | Input to draftCR TS28.105 NRM for AIML emulation environment | Nokia |
S5-251261 | Input to draftCR TS28.105 NRM for ML-Knowledge-based TL | Nokia |
S5-251354 | Input to DraftCR Rel-19 TS 28.105 Add Management Scenario for RL | ZTE Corporation, NEC, Intel |
S5-251355 | Input to DraftCR Rel-19 TS 28.105 Add Procedure Diagram for FL Server selection and determination | ZTE Corporation,NEC, Intel |
S5-251356 | Input to DraftCR Rel-19 TS 28.105 Add Procedure Diagram for FL Client selection | ZTE Corporation,NEC, Intel |
S5-251357 | Input to DraftCR Rel-19 TS 28.105 Update the UC and Req of Reinforcement Learning | ZTE Corporation |
S5-251358 | Input to DraftCR Rel-19 TS 28.105 Add New Use Case and Requirements of Sustainable AIML for ML training | ZTE Corporation |
S5-251359 | Input to DraftCR Rel-19 TS 28.105 Add Solution for Sustainable AIML for ML training | ZTE Corporation |
S5-251360 | Input to DraftCR Rel-19 TS 28.105 Enhancement on AIMLSupportedFunction to support inference in LMF | ZTE Corporation |
S5-251361 | Rel-19 CR TS 28.541 Enhancement on LMF NRM to Support the Inference Functionality in LMF | ZTE Corporation |
S5-251362 | Input to DraftCR Rel-19 TS 28.105 Add New AI/ML functionalities management scenario for LMF | ZTE Corporation |
S5-251363 | Input to DraftCR Rel-19 TS 28.105 Add Solution for Distributed Learning | ZTE Corporation |
S5-251364 | DP on the NRM Design for AIMLInferenceFunction | ZTE Corporation |
S5-251365 | Input to DraftCR Rel-19 CR TS 28.105 Enhancement on AIMLInferenceFunction NRM | ZTE Corporation |
S5-251410 | Input to draftCR TS 28.105 Add NRMs on LCM for Federated Learning | Intel, NEC, ZTE, Samsung, Nokia |
S5-251411 | Input to draftCR TS 28.105 Add NRMs on LCM for Reinforcement Learning | Intel, ZTE, NEC |
S5-251412 | Input to draftCR TS 28.105 Enhance UC for management of Reinforcement Learning | Intel, NEC |
S5-251444 | Rel19 input to DraftCR TS28.105 New use case on Coordination between the ML capabilities | Nokia, Nokia Shanghai Bell, China mobile, TELUS |
S5-251496 | Input to DraftCR Rel-19 TS 28.105 Add UC for prediction latency | China Mobile |
S5-251497 | Input to DraftCR Rel-19 TS 28.105 Add UC for AIML explainability | China Mobile |
S5-251506 | Input to draftCR TS 28.105 Pre-specialized training and Fine-tuning | China Mobile, ZTE |
S5-251507 | Input to Draft CR Rel-19 CR TS 28.105 Add solution for Pre-specialized training and fine-tuning | China Mobile, ZTE |
S5-251530 | Rel-19 InputToDraftCR 28.105 solution for Impact management | Samsung R&D Institute UK |
S5-251541 | Rel-19 InputToDraftCR 28.105 RL UC and Requirements | Samsung R&D Institute UK |
S5-251545 | Rel-19 InputToDraftCR TS 28.105 enhance the description for managing AIML based capabilities | Huawei |
S5-251546 | Rel-19 InputToDraftCR TS 28.105 add procedure of management of AIML capabilities for NG-RAN and MDA | Huawei |
S5-251547 | Rel-19 InputToDraftCR TS 28.105 Update the description for managing ML models in use in a live network | Huawei |
S5-251548 | Rel-19 InputToDraftCR TS 28.105 add solution for exploration in reinforcement learning | Huawei |
S5-251549 | Rel-19 InputToDraftCR TS 28.105 Add use case and requirements for reinforcement learning conflict management | Huawei |
S5-251550 | Rel-19 InputToDraftCR TS 28.105 Add solutions of training conflict management for reinforcement learning | Huawei |
S5-251551 | Rel-19 InputToDraftCR TS 28.105 add use case for Management of Local explanation in AIML inference | Huawei |
S5-251552 | Rel-19 InputToDraftCR TS 28.105 add solution for Management of Local explanation in AIML inference | Huawei |
S5-251553 | Rel-19 InputToDraftCR TS 28.105 update the ML model lifecycle management capabilities | Huawei |
S5-251606 | Input to draftCR Rel-19 TS 28.105 Use case on AIML prediction latency in inference | Nokia, Nokia Shanghai Bell |
S5-251607 | Input to draftCR Rel-19 TS 28.105 Use case on AIML prediction latency in training | Nokia, Nokia Shanghai Bell |
S5-251608 | Input to draftCR Rel-19 TS 28.105 Use case on ML explainability for inference | Nokia, Nokia Shanghai Bell |
S5-251609 | Input to draftCR Rel-19 TS 28.105 Use case on ML explainability for training | Nokia, Nokia Shanghai Bell |
S5-251610 | Input to draftCR Rel-19 TS 28.105 Solution on model confidence requirement | Nokia, Nokia Shanghai Bell |
S5-251611 | Input to draftCR Rel-19 TS 28.105 Solution on sustainable AIML training | Nokia, Nokia Shanghai Bell |
S5-251612 | Input to draftCR Rel-19 TS 28.105 Use case on model confidence requirement | Nokia, Nokia Shanghai Bell |
S5-251613 | Input to draftCR Rel-19 TS 28.105 Use case on sustainable AIML training | Nokia, Nokia Shanghai Bell |
S5-251614 | Input to draftCR Rel-19 TS 28.105 Add RL NRMs | Nokia, Nokia Shanghai Bell |
S5-251633 | Rel-19 Input to draftCR TS 28.105 Add NRMs on distributed training | CATT |
S5-251713 | Input to DraftCR Rel-19 TS 28.105 Fix wrong reference and add RRC report | Ericsson GmbH, Eurolab |
S5-251755 | pCR DraftCR Rel-19 TS 28.105 Editorials corrections to the requirements of Managing ML models in use in a live network | NEC Europe Ltd |
S5-251756 | Input to Draft CR Rel-19 CR TS 28.105 Pre-specialized training and Fine-tuning | NEC, Intel |
S5-251757 | Input to draft CR TS 28.105 add NRM for ML pre-training and fine-tuning | NEC, Intel |
S5-251764 | Rel-19 draftCR TS28.105 | NEC |
S5-251782 | Input to Draft CR Rel-19 CR TS 28.105 Pre-specialized training and Fine-tuning | NEC, Intel, China Mobile, ZTE |
S5-251783 | Input to draft CR TS 28.105 add NRM for ML pre-training and fine-tuning | NEC, Intel, China Mobile, ZTE, Huawei |
S5-251784 | Input to draftCR TS 28.105 Add NRMs on LCM for Federated Learning | Intel, NEC, ZTE, Samsung, Nokia |
S5-251785 | Input to DraftCR Rel-19 TS 28.105 Add Procedure Diagram for FL Server selection and determination | ZTE Corporation,NEC, Intel |
S5-251786 | Rel-19 InputToDraftCR TS 28.105 Add use case and requirements for reinforcement learning conflict management | Huawei |
S5-251787 | Rel-19 InputToDraftCR 28.105 RL UC and Requirements | Samsung R&D Institute UK, Ericsson |
S5-251788 | Input to DraftCR Rel-19 TS 28.105 Update the UC and Req of Reinforcement Learning | ZTE Corporation, Ericsson |
S5-251789 | Rel-19 Input to draftCR TS 28.105 Add NRMs on distributed training | CATT, ZTE, Samsung, Ericsson |
S5-252040 | Rel-19 InputToDraftCR TS 28.105 add solution for exploration in reinforcement learning | Huawei, Samsung, Nokia, Intel, NEC, ZTE |
S5-252041 | Input to draftCR TS28.105 NRM for ML-Knowledge-based TL | Nokia |
S5-252042 | Input to draftCR Rel-19 TS 28.105 Use case on model confidence requirement | Nokia, Nokia Shanghai Bell |
S5-252043 | Input to draftCR Rel-19 TS 28.105 Solution on sustainable AIML training | Nokia, Nokia Shanghai Bell |
S5-252044 | Input to DraftCR Rel-19 TS 28.105 Add New Use Case and Requirements of Sustainable AIML for ML training | ZTE Corporation |
S5-252045 | Input to draftCR Rel-19 TS 28.105 Use case on AIML prediction latency in training | Nokia, Nokia Shanghai Bell |
S5-252046 | Rel-19 InputToDraftCR TS 28.105 Update the description for managing ML models in use in a live network | Huawei, NEC, Ericsson |
S5-252047 | Rel-19 InputToDraftCR TS 28.105 add use case for Management of Local explanation in AIML inference | HUAWEI, Orange, CMCC, Nokia, Verizon,NTT DOCOMO |
S5-252048 | Input to DraftCR Rel-19 TS 28.105 Add New AI/ML functionalities management scenario for LMF | ZTE Corporation, Ericsson |
S5-252108 | Rel-19 InputToDraftCR 28.105 solution for Impact management | Samsung R&D Institute UK, ZTE, Ericsson |
S5-252133 | Input to draftCR TS28.105 NRM for ML-Knowledge-based TL | Nokia |
TDoc | Title | Source |
---|---|---|
S5-251317 | Add the use case and requirements for edge application deployment location analysis | AsiaInfo, ZTE |
S5-251318 | Add the use case and requirements for edge computing performance analysis | AsiaInfo, ZTE |
S5-251319 | Add the use case and requirements for traffic congestion prediction analytics based on UE throughput | AsiaInfo, ZTE |
S5-251320 | Rel-19 CR TS 28.104 Add solution for edge application deployment location analysis | AsiaInfo, ZTE |
S5-251321 | Rel-19 CR TS 28.104 add solutions for edge computing performance analysis | AsiaInfo, ZTE |
S5-251440 | Rel19 CR TS28.104 add solution on management data correlation analytics | Nokia, Nokia Shanghai Bell |
S5-251441 | Rel19 CR TS28.104 add solution on correlation analytics for NF Scaling and dimensioning | Nokia, Nokia Shanghai Bell |
S5-251442 | Rel19 CR TS28.104 add solution on management data correlation analytics for threshold assessment and adjustment | Nokia, Nokia Shanghai Bell |
S5-251443 | Rel19 CR TS28.104 add solution on management data collection recommendation for predicted failures | Nokia, Nokia Shanghai Bell |
S5-251462 | Rel-19 CR TS 28.104 Add solutions for traffic congestion prediction analysis based on UE throughput | AsiaInfo, ZTE |
S5-251539 | Rel-19 CR 28.104 software upgrade validation | Samsung R&D Institute UK |
S5-251554 | Rel-19 CR TS 28.104 update MDA type for UE throughput anlaysis | Huawei |
S5-251555 | Rel-19 CR TS 28.104 add stage3 solution for mobility performance analysis | Huawei, Samsung |
S5-251596 | Rel-19 CR TS 28.104 Improvements to failure prediction | Huawei |
S5-251618 | Rel-19 CR 28.104 adding statics information in failure prediction output | Huawei |
S5-251619 | Rel-19 CR 28.104 clarification on resource management | Huawei |
S5-251620 | Rel-19 CR 28.104 topology information as enabling data is missing | Huawei |
S5-251626 | Rel 19 CR TS 28.104 Clarify definition of confidenceDegree attribute | Ericsson |
S5-251715 | Rel-19 CR TS 28.104 Fix wrong reference and add RRC report | Ericsson GmbH, Eurolab |
S5-251736 | Rel-19 CR TS 28.104 Multi Domain Resource Optimization | Nokia |
S5-251790 | Add the use case and requirements for edge application deployment location analysis | AsiaInfo, ZTE |
S5-251791 | Rel-19 CR TS 28.104 Add solution for edge application deployment location analysis | AsiaInfo, ZTE |
S5-251792 | Add the use case and requirements for edge computing performance analysis | AsiaInfo, ZTE |
S5-251793 | Rel-19 CR TS 28.104 add solutions for edge computing performance analysis | AsiaInfo, ZTE |
S5-251794 | Rel-19 CR TS 28.104 Multi Domain Resource Optimization | Nokia |
S5-251795 | Rel19 CR TS28.104 add solution on management data correlation analytics | Nokia, Nokia Shanghai Bell, Orange |
S5-251796 | Rel19 CR TS28.104 add solution on correlation analytics for NF Scaling and dimensioning | Nokia, Nokia Shanghai Bell, Orange |
S5-251797 | Rel19 CR TS28.104 add solution on management data correlation analytics for threshold assessment and adjustment | Nokia, Nokia Shanghai Bell |
S5-251798 | Add the use case and requirements for traffic congestion prediction analytics based on UE throughput | AsiaInfo, ZTE, Orange |
S5-251799 | Rel-19 CR TS 28.104 Add solutions for traffic congestion prediction analysis based on UE throughput | AsiaInfo, ZTE |
S5-251880 | Rel-19 CR TS 28.104 update MDA type for UE throughput anlaysis | Huawei |
S5-251881 | Rel19 CR TS28.104 add solution on management data collection recommendation for predicted failures | Nokia, Nokia Shanghai Bell, Orange |
S5-251882 | Rel-19 CR TS 28.104 Fix wrong reference and add RRC report | Ericsson GmbH, Eurolab, Nokia, Nokia Shanghai Bell |
S5-251883 | Rel-19 CR 28.104 adding statics information in failure prediction output | Huawei |
S5-251884 | Rel-19 CR 28.104 topology information as enabling data is missing | Huawei |
S5-251885 | Rel-19 CR 28.104 software upgrade validation | Samsung R&D Institute UK, Orange |
S5-251886 | Rel 19 CR TS 28.104 Clarify definition of confidenceDegree attribute | Ericsson |
S5-252116 | Rel-19 CR 28.104 software upgrade validation | Samsung R&D Institute UK, Orange |
TDoc | Title | Source |
---|---|---|
S5-251241 | Enhancing Enablers for Intent Fulfilment | Nokia, Samsung |
S5-251272 | Rel-19 CR TS 28.312 Update the solution for Intent capability exposure | Huawei, Deutsche Telekom, Nokia |
S5-251273 | Rel-19 CR TS 28.312 Update the solution for intent negotiation report | Huawei |
S5-251274 | Rel-19 CR TS 28.312 Enhance the use case and solution to support radio network support for UAV pre-flight preparation | Huawei, Deutsche Telekom |
S5-251275 | Rel-19 CR TS 28.312 Add procedure for intent exploration | Huawei, Deutsche Telekom |
S5-251276 | Rel-19 CR TS 28.312 Update procedures for intent report management to support implicit intent report subscription | Huawei |
S5-251277 | Rel-19 CR TS 28.312 Update 5.3.1 Intent handling capability obtaining | Huawei |
S5-251278 | Rel-19 CR TS 28.312 Add missing abbreviation and definition | Huawei, Deutsche Telekom |
S5-251279 | Rel-19 CR TS 28.312 Enhance the definition for intentMgmtPurpose | Huawei, Deutsche Telekom |
S5-251280 | Rel-19 CR TS 28.312 Enhance the solution for RadioServiceExpectation | Huawei, Deutsche Telekom |
S5-251281 | Rel-19 Address the implementation issue for CR 0277 and CR 0304 | Huawei |
S5-251367 | Rel-19 CR TS 28.312 Enhance the use case and solution to support MOCN undifferentiated radio service in a specified area | China Unicom |
S5-251392 | Rel-19 CR TS 28.312 Update clause 6.1 and 7.1 to support intent negotiation | Huawei, Deutsche Telekom |
S5-251408 | Rel-19 CR TS 28.312 Add Stage-3 Solution for intent driven management of network maintenance | NTT DOCOMO |
S5-251422 | Rel-19 CR 28.312 Add generic utility function support (stage 2) | Ericsson Inc. |
S5-251445 | Rel-19 CR TS 28.312 Add requirements and solutions for refusing to intent negotiation | China Mobile Com. Corporation |
S5-251446 | Rel-19 CR TS 28.312 Add description of excavating of implicit intent | China Mobile Com. Corporation |
S5-251449 | Rel-19 CR TS 28.312 Update on Intent Negotiation Use Case | ZTE Corporation |
S5-251450 | Rel-19 CR TS 28.312 Update on Intent Negotiation NRM | ZTE Corporation |
S5-251458 | Rel-19 CR TS 28.312 Add requirements and solutions for triggering intent negotiation | China Mobile Com. Corporation |
S5-251460 | Rel-19 CR TS 28.312 Add description of excavating of implicit intent | China Mobile Com. Corporation |
S5-251494 | Rel-19 CR TS 28.312 Modify the Generic Information model definition | China Mobile, Huawei |
S5-251495 | Rel-19 CR TS 28.312 Update solution for intent exploration | China Mobile, Huawei |
S5-251532 | Rel-19 CR TS 28.312 Add use case and requirement for intent related intents | NTT DOCOMO |
S5-251534 | Rel-19 CR TS 28.312 Add an example to support intent report based on condition | Huawei |
S5-251559 | Rel-19 CR TS 28.312 Correction on introduction in clause 5.1.9.1 | NTT DOCOMO |
S5-251577 | Rel-19 CR TS 28.312 Correction on introduction for intent fulfilment feasibility check | NTT DOCOMO |
S5-251603 | Rel-19 CR 28.312 Clarifications on negotiation of intent fulfillment | Ericsson Canada Inc. |
S5-251660 | Rel-19 CR TS 28.312 Introduce mapping table | Ericsson, Deutsche Telekom |
S5-251661 | Rel-19 CR TS 28.312 Update UML diagram for intent | Ericsson, ZTE |
S5-251750 | Rel-19 CR 28.312 Add generic utility function support (stage 2) | Ericsson Canada Inc. |
S5-251913 | Rel-19 CR TS 28.312 Enhance the use case and solution to support radio network support for UAV pre-flight preparation | Huawei, Deutsche Telekom |
S5-251914 | Rel-19 CR TS 28.312 Enhance the use case and solution to support MOCN undifferentiated radio service in a specified area | China Unicom |
S5-251915 | Rel-19 CR 28.312 Clarifications on negotiation of intent fulfillment | Ericsson Canada Inc., ZTE |
S5-251916 | Rel-19 CR TS 28.312 Update the solution for intent negotiation report | Huawei, China Mobile, ZTE |
S5-251917 | Rel-19 CR TS 28.312 Add procedure for intent exploration | Huawei, Deutsche Telekom, ZTE |
S5-251918 | Rel-19 CR TS 28.312 Enhance the definition for intentMgmtPurpose | Huawei, Deutsche Telekom, ZTE |
S5-251919 | Rel-19 CR TS 28.312 Update clause 6.1 and 7.1 to support intent negotiation | Huawei, Deutsche Telekom, ZTE |
S5-251920 | Rel-19 CR TS 28.312 Correction on introduction for intent fulfilment feasibility check | NTT DOCOMO |
S5-251921 | Rel-19 CR 28.312 Add generic utility function support (stage 2) | Ericsson Canada Inc. |
S5-251922 | Rel-19 CR TS 28.312 Update procedures for intent report management to support implicit intent report subscription | Huawei, ZTE, Deutsche Telekom |
S5-251923 | Rel-19 CR TS 28.312 Add an example to support intent report based on condition | Huawei |
S5-251924 | Rel-19 CR TS 28.312 Update the solution for Intent capability exposure | Huawei, Deutsche Telekom, Nokia |
S5-251925 | Rel-19 CR TS 28.312 Update 5.3.1 Intent handling capability obtaining | Huawei |
S5-251926 | Rel-19 CR TS 28.312 Add missing abbreviation and definition | Huawei, Deutsche Telekom |
S5-251927 | Rel-19 CR TS 28.312 Introduce mapping table | Ericsson, Deutsche Telekom |
S5-252054 | Rel-19 CR TS 28.312 Add description of excavating of implicit intent | China Mobile Com. Corporation |
S5-252117 | Rel-19 CR TS 28.312 Introduce mapping table | Ericsson, Deutsche Telekom |
TDoc | Title | Source |
---|---|---|
S5-251334 | TS28.536 CR update Assurace CCL model | Nokia Americas |
TDoc | Title | Source |
---|---|---|
S5-251242 | CCL Goal-targets and actions conflicts | Nokia, Samsung |
S5-251243 | CCL network & time scope conflicts | Nokia |
S5-251244 | CCL Trigger conflicts | Nokia, Samsung |
S5-251245 | CCL Indirect target conflicts | Nokia |
S5-251246 | CCL-impact assessment and resolution | Nokia, Samsung |
S5-251247 | CCL decision escalation | Nokia |
S5-251248 | Coordinating CCLs with other functions | Nokia |
S5-251249 | CCL General NRM | Nokia |
S5-251250 | DP on CCL and ACCL modelling relationship | Nokia |
S5-251251 | CCL coordination NRM | Nokia |
S5-251252 | Informative Annex on conflict handling approach | Nokia |
S5-251527 | Rel-19 pCR 28.567 Triggered CCL UC and Requirements | Samsung R&D Institute UK |
S5-251536 | pCR TS 28.567 Add use case and requirements for network performance problem recovery | Huawei, Deutsche Telekom |
S5-251662 | Rel-19 CR TS 28.536 Clarify generic use of closed control loop | Ericsson, Deutsche Telekom |
S5-251663 | pCR on TS 28.567 introduce imported information elements | Ericsson, Deutsche Telekom |
S5-251749 | Rel-19 pCR TS 28.567 Procedure and metrics for CCL performance monitoring | Samsung Electronics GmbH |
S5-251760 | Draft TS28.567 | Nokia |
S5-251904 | Rel-19 pCR 28.567 Triggered CCL UC and Requirements | Samsung R&D Institute UK, Nokia, Deutsche Telekom, China Unicom |
S5-251905 | CCL Trigger conflicts | Nokia, Samsung |
S5-251906 | CCL Goal-targets and actions conflicts | Nokia, Samsung |
S5-251907 | CCL Indirect target conflicts | Nokia |
S5-251908 | CCL network & time scope conflicts | Nokia |
S5-251909 | Informative Annex on conflict handling approach | Nokia |
S5-251910 | CCL-impact assessment and resolution | Nokia, Samsung |
S5-251911 | CCL decision escalation | Nokia |
S5-251912 | pCR TS 28.567 Add use case and requirements for network performance problem recovery | Huawei, Deutsche Telekom, Nokia |
S5-252029 | DP on CCL and ACCL modelling relationship | Nokia, Samsung |
S5-252030 | CCL General NRM | Nokia, Samsung |
S5-252031 | Rel-19 CR TS 28.536 Clarify generic use of closed control loop | Ericsson, Deutsche Telekom |
S5-252032 | pCR on TS 28.567 introduce imported information elements | Ericsson, Deutsche Telekom |
S5-252033 | Rel-19 pCR TS 28.567 Procedure and metrics for CCL performance monitoring | Samsung Electronics GmbH |
S5-252034 | Coordinating CCLs with other functions | Nokia |
S5-252035 | CCL coordination NRM | Nokia |
TDoc | Title | Source |
---|---|---|
S5-251253 | NDT concept and scope | Nokia, Ericsson |
S5-251254 | NDT relation to automation | Nokia, Ericsson |
S5-251255 | NDTs for verification | Nokia, Ericsson |
S5-251256 | NDT support to Automation | Nokia, Ericsson |
S5-251257 | NDT NRM | Nokia |
S5-251423 | Discussion Paper Justification for the Inclusion of Nested NDT Definition in the TS 28.561 | FiberCop, Deutsche Telekom, Telecom Italia |
S5-251427 | Pseudo-CR on TS 28.561 Nested NDT Definition | FiberCop, Deutsche Telekom, Telecom Italia |
S5-251447 | Rel-19 pCR TS 28.561 Generic NDT NRM | ZTE Corporation |
S5-251448 | Rel-19 pCR TS 28.561 Add Requirements for Network failure and risk prediction | ZTE Corporation |
S5-251490 | TS28.561 Add the NDT concept and scope | China Mobile |
S5-251491 | TS28.561 NDT support for network automation | China Mobile, Huawei |
S5-251492 | pCR Add UC and requirements of using NDT to generate customer experience data for TS 28.561 | China Mobile, Huawei |
S5-251493 | pCR Add solution of Using NDT to generate ML training data for TS 28.561 | China Mobile |
S5-251538 | Rel-19 pCR 28.561 adding requirement of network issue inducement capability | NTT DOCOMO, SK Telecom |
S5-251540 | Rel-19 pCR 28.561 NDT overview | NTT DOCOMO, SK Telecom |
S5-251542 | Rel-19 CR 28.561 NDT Inducement Requirements | Samsung R&D Institute UK |
S5-251566 | Pseudo-CR on TS 28.561 Use case of RAN energy saving policy verification | Huawei |
S5-251567 | Pseudo-CR on TS 28.561 NDT NRMs | Huawei |
S5-251568 | Pseudo-CR on TS 28.561 Remove abbreviations in clause 5.1 | Huawei |
S5-251569 | Pseudo-CR on TS 28.561 Add requirements for NDT supporting data generation | Huawei |
S5-251570 | Pseudo-CR on TS 28.561 Procedure for consuming NDT capability | Huawei |
S5-251599 | Rel-19 pCR TS 28.561 General improvements to use cases and requirements | Huawei Tech. Japan, K.K. |
S5-251601 | TS28.561 Add the NDT concept and scope | China Mobile, FiberCop |
S5-251602 | TS28.561 NDT support for network automation | China Mobile, Huawei, FiberCop |
S5-251648 | Pseudo-CR on TS 28.561 Update use case for NDT support analysis of failure events including signaling storm | Huawei |
S5-251657 | Pseudo-CR on TS 28.561 Nested NDT Definition | FiberCop, Deutsche Telekom, Telecom Italia, Orange |
S5-251759 | Draft TS28.561 | China Mobile |
S5-251896 | NDT concept and scope | Nokia, Ericsson |
S5-251897 | TS28.561 Add the NDT concept and scope | China Mobile, FiberCop, Orange, Nokia, Huawei, NTT DOCOMO, SK Telecom, Ericsson |
S5-251898 | NDT relation to automation | Nokia, Ericsson |
S5-251899 | TS28.561 NDT support for network automation | China Mobile, Huawei, FiberCop, Nokia, Ericsson, ZTE, Huawei, NTT DOCOMO, SK Telecom, Samsung |
S5-251900 | NDT support to Automation | Nokia, Ericsson |
S5-251901 | NDTs for verification | Nokia, Ericsson, Huawei |
S5-251902 | Pseudo-CR on TS 28.561 Use case of RAN energy saving policy verification | Huawei |
S5-251903 | Pseudo-CR on TS 28.561 Add requirements for NDT supporting data generation | Huawei, Nokia, Ericsson, China Mobile |
S5-252017 | Pseudo-CR on TS 28.561 Nested NDT Definition | FiberCop, Deutsche Telekom, Telecom Italia, Orange, NTT Docomo , Nokia , China Mobile, Ericsson |
S5-252018 | Discussion Paper Justification for the Inclusion of Nested NDT Definition in the TS 28.561 | FiberCop, Deutsche Telekom, Telecom Italia |
S5-252019 | Rel-19 pCR TS 28.561 General improvements to use cases and requirements | Huawei Tech. Japan, K.K., Ericsson |
S5-252020 | Pseudo-CR on TS 28.561 NDT NRMs | Huawei |
S5-252021 | Pseudo-CR on TS 28.561 Procedure for consuming NDT capability | Huawei |
S5-252118 | Pseudo-CR on TS 28.561 NDT NRMs | Huawei, Nokia, CMCC, ZTE, Orange, Ericsson |
S5-252119 | Pseudo-CR on TS 28.561 Procedure for consuming NDT capability | Huawei |
S5-252120 | Pseudo-CR on TS 28.561 Nested NDT Definition | FiberCop, Deutsche Telekom, Telecom Italia, Orange, NTT Docomo , Nokia , China Mobile, Ericsson |
TDoc | Title | Source |
---|---|---|
S5-251262 | pCR TR 28.869 Annex example for CRD based deployment | Rakuten Mobile, Inc |
S5-251263 | pCR TR 28.869 LCM changes for declarative descriptor | Rakuten Mobile, Inc |
S5-251537 | pCR TR 28.869 Add potential solution for VNF configuration management | Huawei, Deutsche Telekom, Ericsson, Nokia |
S5-251560 | R19 pCR TR 28.869 enhance observability requirements (Use case 7) | Orange, AT&T |
S5-251571 | Pseudo-CR on TR 28.869 Add an example in Annex B | Huawei |
S5-251572 | Pseudo-CR on TR 28.869 Add conclusion for management data streaming solution based on message bus | Huawei |
S5-251578 | pCR Add evaluation for solutions in clause 5.2.1.3 | China Mobile,NTT DOCOMO |
S5-251579 | pCR Add solution and evaluation statement for usecase Placement of cloud native NFs | China Mobile |
S5-251583 | pCR TR 28.869 Cloud-native VNF policy management evaluation | NTT DOCOMO |
S5-251584 | pCR TR 28.869 3GPP management architecture evolution based on PaaS | NTT DOCOMO, China Mobile |
S5-251594 | pCR Add evaluation for some LCM solutions and update the clause 5.2.6 | China Mobile |
S5-251600 | pCR Add general conclusion and some recommendations | China Mobile |
S5-251639 | pCR Add terminology | China Mobile |
S5-251718 | pCR TR 28.869 Adopt NF Deployment terminology in scaling use case | Ericsson Telecomunicazioni SpA |
S5-251719 | pCR TR 28.869 Detail procedure flow for creation of NF Deployment | Ericsson Telecomunicazioni SpA |
S5-251722 | pCR TR 28.869 Specification structure for LCM of NF Deployment | Ericsson Telecomunicazioni SpA |
S5-251725 | pCR TR 28.869 Update Annex D for example scenario for creation of NF Deployment instance | Ericsson Telecomunicazioni SpA |
S5-251744 | DP cloud native NF data streaming - connection based vs pub-sub based | Rakuten Mobile, Inc |
S5-251746 | Pseudo-CR on enhance annex examples for data streaming for cloud native network function | Rakuten Mobile, Inc |
S5-251747 | Pseudo-CR on Add evaluation and conclusion for management data streaming based on message bus | Rakuten Mobile, Inc |
S5-251763 | Draft TR28.869 | China Mobile |
S5-251887 | pCR TR 28.869 LCM changes for declarative descriptor | Rakuten Mobile, Inc, Orange |
S5-251888 | pCR TR 28.869 Detail procedure flow for creation of NF Deployment | Ericsson Telecomunicazioni SpA |
S5-251889 | pCR TR 28.869 Add potential solution for VNF configuration management | Huawei, Deutsche Telekom, Ericsson, Nokia, Samsung |
S5-251890 | pCR TR 28.869 Cloud-native VNF policy management evaluation | NTT DOCOMO |
S5-251891 | R19 pCR TR 28.869 enhance observability requirements (Use case 7) | Orange, AT&T |
S5-251892 | pCR Add evaluation for solutions in clause 5.2.1.3 | China Mobile,NTT DOCOMO |
S5-251893 | pCR TR 28.869 Annex example for CRD based deployment | Rakuten Mobile, Inc, Orange |
S5-251894 | pCR TR 28.869 Update Annex D for example scenario for creation of NF Deployment instance | Ericsson Telecomunicazioni SpA |
S5-251895 | pCR TR 28.869 3GPP management architecture evolution based on PaaS | NTT DOCOMO, China Mobile |
S5-252009 | DP cloud native NF data streaming - connection based vs pub-sub based | Rakuten Mobile, Inc, AT&T, \tOrange, NTT DOCOMO, \tChina Mobile, China Unicom, \tFiberCop |
S5-252010 | Pseudo-CR on TR 28.869 Add an example in Annex B | Huawei, Rakuten Mobile, Inc. |
S5-252011 | pCR Add evaluation for some LCM solutions and update the clause 5.2.6 | China Mobile |
S5-252012 | pCR TR 28.869 Adopt NF Deployment terminology in scaling use case | Ericsson Telecomunicazioni SpA |
S5-252013 | Pseudo-CR on TR 28.869 Add conclusion for management data streaming solution based on message bus | Huawei |
S5-252014 | pCR Add general conclusion and some recommendations | China Mobile |
S5-252015 | pCR Add terminology | China Mobile |
S5-252016 | pCR TR 28.869 Specification structure for LCM of NF Deployment | Ericsson Telecomunicazioni SpA |
S5-252121 | Pseudo-CR on TR 28.869 Add conclusion for management data streaming solution based on message bus | Huawei |
TDoc | Title | Source |
---|---|---|
S5-251333 | Rel-19 CR 28.532 Add new notifications for reliability | Ericsson India Private Limited |
S5-251393 | Rel-19 CR TS 28537 Add requirements for discovering management capabilities of MnS instances based on area of interest | Huawei, Deutsche Telekom |
S5-251394 | Rel-19 CR TS 28.622 Extend the MnsScope to support area of interest (Stage2) | Huawei, Deutsche Telekom |
S5-251395 | Rel-19 CR TS 28.623 Extend the MnsScope to support area of interest (Stage3) | Huawei, Deutsche Telekom |
S5-251396 | Rel-19 CR TS 28.622 Enhance the MnSInfo to support discovery of management capabilities of MnS supported by a MnS Producer (Stage2) | Huawei, Deutsche Telekom |
S5-251397 | Rel-19 CR TS 28.623 Enhance the MnSInfo to support discovery of management capabilities of MnS supported by a MnS Producer (Stage3) | Huawei, Deutsche Telekom |
S5-251486 | Rel-19 CR TS 28.111 Update terms and concepts overview | Huawei |
S5-251487 | Rel-19 CR TS 28.111 Update references and abbreviations | Huawei |
S5-251488 | Rel-19 CR TS 28.111 Update scope | Huawei |
S5-251581 | Rel-19 CR 32.158 Add details for MnS API versioning | Ericsson Canada Inc. |
S5-251582 | Rel-19 CR 28.537 Add details for MnS API versioning | Ericsson Canada Inc. |
S5-251675 | Discussion paper on adding information in entry point specifications | Ericsson, Huawei, Deutsche Telekom |
S5-251676 | Rel-19 CR TS 28.310 Add entry point information | Ericsson, Huawei, Deutsche Telekom |
S5-251677 | Rel-19 CR TS 28.313 Add entry point information | Ericsson, Huawei, Deutsche Telekom |
S5-251678 | Rel-19 CR TS 28.314 Add entry point information | Ericsson, Huawei, Deutsche Telekom |
S5-251679 | Rel-19 CR TS 28.404 Add entry point information | Ericsson, Huawei, Deutsche Telekom |
S5-251680 | Rel-19 CR TS 28.531 Add entry point information | Ericsson, Huawei, Deutsche Telekom |
S5-251681 | Rel-19 CR TS 28.532 Add entry point information | Ericsson, Huawei, Deutsche Telekom |
S5-251682 | Rel-19 CR TS 28.535 Add entry point information | Ericsson, Huawei, Deutsche Telekom |
S5-251683 | Rel-19 CR TS 28.537 Add entry point information | Ericsson, Huawei, Deutsche Telekom |
S5-251684 | Rel-19 CR TS 28.540 Add entry point information | Ericsson, Huawei, Deutsche Telekom |
S5-251685 | Rel-19 CR TS 28.555 Add entry point information | Ericsson, Huawei, Deutsche Telekom |
S5-251686 | Rel-19 CR TS 28.622 Add entry point information | Ericsson, Huawei, Deutsche Telekom |
S5-251687 | Rel-19 CR TS 28.130 Add entry point information | Ericsson, Huawei, Deutsche Telekom |
S5-251688 | Rel-19 CR TS 32.421 Add entry point information | Ericsson, Huawei, Deutsche Telekom |
S5-251724 | Rel-19 CR TS 28.533 Update Annex E | Ericsson GmbH, Eurolab |
S5-251733 | Rel-19 CR 28.532 Add new notifications for reliability | Ericsson India Private Limited |
S5-251743 | Rel-19 CR 28.532 Update notifications with common header | Ericsson India Private Limited |
S5-251752 | Rel-19 CR 28.622 Reliable notification transfer | Ericsson Hungary Ltd |
S5-251928 | Rel-19 CR TS 28537 Add requirements for discovering management capabilities of MnS instances based on area of interest | Huawei, Deutsche Telekom |
S5-251929 | Rel-19 CR TS 28.622 Extend the MnsScope to support area of interest (Stage2) | Huawei, Deutsche Telekom |
S5-251930 | Rel-19 CR TS 28.623 Extend the MnsScope to support area of interest (Stage3) | Huawei, Deutsche Telekom |
S5-251931 | Rel-19 CR TS 28.622 Enhance the MnSInfo to support discovery of management capabilities of MnS supported by a MnS Producer (Stage2) | Huawei, Deutsche Telekom, Nokia |
S5-251932 | Rel-19 CR TS 28.623 Enhance the MnSInfo to support discovery of management capabilities of MnS supported by a MnS Producer (Stage3) | Huawei, Deutsche Telekom, Nokia |
S5-251933 | Rel-19 CR TS 28.111 Update terms and concepts overview | Huawei |
S5-251934 | Rel-19 CR 32.158 Add details for MnS API versioning | Ericsson Canada Inc. |
S5-251935 | Rel-19 CR 28.537 Add details for MnS API versioning | Ericsson Canada Inc. |
S5-251936 | Rel-19 CR 28.537 Add details for MnS API versioning | Ericsson Canada Inc. |
S5-251937 | Rel-19 CR TS 28.533 Update Annex E | Ericsson GmbH, Eurolab, Deutsche Telekom, Huawei, Orange |
S5-251939 | Rel-19 CR 28.532 Add new notifications for reliability | Ericsson India Private Limited |
S5-251940 | Rel-19 CR 28.622 Reliable notification transfer | Ericsson Hungary Ltd |
TDoc | Title | Source |
---|---|---|
S5-251635 | Rel-19 pCR TS 28.572 Improve clauses on Planned configuration concepts | Nokia |
S5-251636 | Rel-19 pCR TS 28.572 Improve clauses on Managing planned configurations | Nokia |
S5-251637 | Rel-19 pCR TS 28.572 Improve clause Information model | Nokia |
S5-251638 | Rel-19 pCR TS 28.572 Improve clause RESTful HTTP-based solution set | Nokia |
S5-251694 | Rel-19 pCR TS 28.572 Allow recursive Planned configuration groups | Ericsson India Private Limited |
S5-251751 | Rel-19 pCR TS 28.572 Plan Configuration Examples | Ericsson India Private Limited |
S5-251753 | Rel-19 pCR TS 28.572 Plan Activation Results | Ericsson India Private Limited |
S5-251754 | Discussion paper on: Long Running Configuration Reads | Ericsson India Private Limited |
S5-251761 | Draft TS28.572 | Nokia |
S5-251950 | Rel-19 pCR TS 28.572 Improve clauses on Planned configuration concepts | Nokia |
S5-251951 | Rel-19 pCR TS 28.572 Improve clauses on Managing planned configurations | Nokia |
S5-251952 | Rel-19 pCR TS 28.572 Improve clause Information model | Nokia |
S5-251953 | Rel-19 pCR TS 28.572 Improve clause RESTful HTTP-based solution set | Nokia |
S5-251954 | Rel-19 pCR TS 28.572 Allow recursive Planned configuration groups | Ericsson India Private Limited |
TDoc | Title | Source |
---|---|---|
S5-251499 | Input to Draft CR 28.622 External Management Data | Nokia |
S5-251765 | Rel-19 draftCR TS28.622 | Nokia |
S5-251955 | Input to Draft CR 28.622 External Management Data | Nokia, Deutsche Telekom, \tEricsson, Huawei |
S5-251956 | Draft CR MADCOL TS 28.622 | Nokia |
S5-251957 | Draft CR MADCOL TS 28.622 | Nokia |
S5-252125 | Draft CR MADCOL TS 28.622 | Nokia |
TDoc | Title | Source |
---|---|---|
S5-251231 | Rel-19 CR TS 28.405 QoE Reference Uniqueness | Ericsson |
S5-251232 | Rel-19 CR TS 32.422 Trace Reference Uniqueness | Ericsson, CATT |
S5-251401 | Rel-19 CR TS 32.422 Introduction of new Trace Depth “Micro” for Optimised Tracing | Jio Platforms Ltd (JPL) |
S5-251501 | Rel-19 CR TS 32.421 Enhancement to Trace Reference | Nokia |
S5-251502 | Rel-19 CR TS 32.422 Enhancement to Trace Reference | Nokia |
S5-251503 | Rel-19 CR TS 32.423 Enhancement to Trace Reference | Nokia |
S5-251504 | Rel-19 CR TS 28.622 Enhancement to Trace Reference | Nokia |
S5-251505 | Rel-19 CR TS 28.623 Enhancement to Trace Reference | Nokia |
S5-251524 | Rel-19 CR TS 32.422 Introduction of new Trace Depth “Micro” for Optimised Tracing | Jio Platforms Ltd (JPL) |
S5-251958 | Rel-19 CR TS 28.405 QoE Reference Uniqueness | Ericsson, CATT |
S5-251959 | Rel-19 CR TS 32.422 Trace Reference Uniqueness | Ericsson, CATT |
TDoc | Title | Source |
---|---|---|
S5-251224 | Rel-19 CR TS 28.532 PM File extension | Ericsson LM |
S5-251225 | Rel-19 CR 28.558 misaligned 5GC UE level measurement procedure | Ericsson |
S5-251227 | Rel-19 CR TS 28.552 Cell Unavailable Time performance measurement | Ericsson, AT&T, Samsung |
S5-251228 | Rel-19 CR TS 32.401 PM Counter Metadata | Ericsson |
S5-251229 | Rel-19 CR TS 32.404 PM Counter Metadata | Ericsson |
S5-251653 | Rel-19 CR TS 28.552 Correction of Distribution of time interval | Esurfing IoT |
S5-251654 | Rel-19 CR TS 28.552 Add Multicast Group Paging records for MBS measurement | Esurfing IoT |
S5-251658 | Rel-19 CR TS 28.552 add measurement of coverage satisfaction ratio | CMCC, Huawei, ZTE, CATT |
S5-251709 | Rel-19 CR TS 28.554 add measurement of coverage satisfaction ratio | CMCC, Huawei, ZTE, CATT |
S5-251710 | Rel-19 CR TS 28.552 add measurement of coverage satisfaction ratio | CMCC, Huawei, ZTE, CATT |
S5-251712 | Rel-19 CR TS 28.552 add measurement of coverage ratio | CMCC, Huawei, ZTE, CATT |
S5-251714 | Rel-19 CR TS 28.554 add measurement of coverage ratio | CMCC, Huawei, ZTE, CATT |
S5-251735 | Rel-19 CR TS 28.532 PM File extension | Ericsson LM |
S5-251960 | Rel-19 CR 28.558 misaligned 5GC UE level measurement procedure | Ericsson |
S5-251961 | Rel-19 CR TS 28.552 Cell Unavailable Time performance measurement | Ericsson, AT&T, Samsung |
S5-251962 | Rel-19 CR TS 32.401 PM Counter Metadata | Ericsson |
S5-251963 | Rel-19 CR TS 32.404 PM Counter Metadata | Ericsson |
S5-251964 | Rel-19 CR TS 28.552 Correction of Distribution of time interval | Esurfing IoT |
S5-251965 | Rel-19 CR TS 28.552 Add Multicast Group Paging records for MBS measurement | Esurfing IoT |
S5-251966 | Rel-19 CR TS 28.552 add measurement of coverage ratio | CMCC, Huawei, ZTE, CATT |
S5-252023 | Rel-19 CR TS 28.532 PM File extension | Ericsson LM |
TDoc | Title | Source |
---|---|---|
S5-251292 | Rel19 CR TS28.541 NRM enhancements to ManagedNFProfile | Nokia, Nokia Shanghai Bell, ZTE Corporation, Orange |
S5-251293 | Rel19 CR TS28.541 change the dataType concerning HostAddr | Nokia, Nokia Shanghai Bell |
S5-251294 | Rel19 CR TS28.538 change the dataType concerning HostAddr | Nokia, Nokia Shanghai Bell |
S5-251398 | Rel-19 CR TS 28.541 update the naming convention in TS28541_NrNrm.yaml to align with stage 2 definition | Huawei |
S5-251399 | Rel-19 CR TS 28.622 Address the misalignment issues for vnfParametersList and peeParametersList (stage2) | Huawei |
S5-251400 | Rel-19 CR TS 28.623 Address the misalignment issues for vnfParametersList and peeParametersList (stage3) | Huawei |
S5-251402 | Rel-19 CR TS 28.622 Enhance the definition for schedulerStatus and conditionStatus with default values (stage2) | Huawei |
S5-251403 | Rel-19 CR TS 28.623 Enhance the definition for schedulerStatus and conditionStatus with default values (stage3) | Huawei |
S5-251404 | Rel-19 CR TS 28.540 Enhance the requirement description | Huawei |
S5-251573 | Rel-19 CR TS 28.540 Add requirements for management of Ambient IoT | Huawei |
S5-251574 | Rel-19 CR TS 28.541 Add AIOTF and ADM IOC to support management of Ambient IoT | Huawei, China Unicom |
S5-251575 | Rel-19 CR TS 28.538 Update the procedure 5GC NF Provisioning | Huawei |
S5-251589 | Rel-19 CR 28.662 Update sector equipment and antenna function definitions | Ericsson Canada Inc. |
S5-251590 | Rel-19 CR 28.541 Update sector equipment and antenna function definitions | Ericsson Canada Inc. |
S5-251711 | Rel-19 CR 28.623 Update sector equipment and antenna function definitions | Ericsson Canada Inc. |
S5-251720 | DP on Solution-agnostic request for service provisioning | Ericsson GmbH, Eurolab |
S5-251721 | Rel-19 CR TS 28.541 Enhance network slicing model to support solution-agnostic service provisioning request. | Ericsson GmbH, Eurolab |
S5-251723 | Rel-19 CR TS 28.531 Add requirements to support solution-agnostic request for service provisioning | Ericsson GmbH, Eurolab |
S5-251728 | Rel-19 CR TS 28.622 Remove stage-3 clarifications for Float datatype | Ericsson GmbH, Eurolab |
S5-251731 | Rel-19 CR 28.663 Update sector equipment and antenna function definitions | Ericsson Canada Inc. |
S5-251967 | Rel19 CR TS28.541 NRM enhancements to ManagedNFProfile | Nokia, Nokia Shanghai Bell, ZTE Corporation, Orange |
S5-251968 | Rel-19 CR TS 28.538 Update the procedure 5GC NF Provisioning | Huawei |
S5-251969 | Rel-19 CR TS 28.540 Enhance the requirement description | Huawei |
S5-251970 | Rel-19 CR TS 28.540 Add requirements for management of Ambient IoT | Huawei, China Unicom |
S5-251971 | Rel-19 CR TS 28.541 Add AIOTF and ADM IOC to support management of Ambient IoT | Huawei, China Unicom |
S5-251972 | Rel-19 CR TS 28.541 update the naming convention in TS28541_NrNrm.yaml to align with stage 2 definition | Huawei, Nokia |
S5-251973 | Rel-19 CR TS 28.622 Remove stage-3 clarifications for Float datatype | Ericsson GmbH, Eurolab, Nokia |
S5-251974 | Rel-19 CR TS 28.622 Enhance the definition for schedulerStatus and conditionStatus with default values (stage2) | Huawei |
S5-251975 | Rel-19 CR TS 28.623 Enhance the definition for schedulerStatus and conditionStatus with default values (stage3) | Huawei |
S5-251976 | Rel-19 CR TS 28.622 Address the misalignment issues for vnfParametersList and peeParametersList (stage2) | Huawei |
S5-251977 | Rel-19 CR TS 28.623 Address the misalignment issues for vnfParametersList and peeParametersList (stage3) | Huawei |
S5-251978 | Rel19 CR TS28.541 change the dataType concerning HostAddr | Nokia, Nokia Shanghai Bell |
S5-251979 | Rel19 CR TS28.538 change the dataType concerning HostAddr | Nokia, Nokia Shanghai Bell |
S5-251980 | Rel-19 CR 28.662 Update sector equipment and antenna function definitions | Ericsson Canada Inc. |
S5-251981 | Rel-19 CR 28.541 Update sector equipment and antenna function definitions | Ericsson Canada Inc. |
S5-251982 | Rel-19 CR 28.623 Update sector equipment and antenna function definitions | Ericsson Canada Inc. |
S5-251983 | Rel-19 CR 28.663 Update sector equipment and antenna function definitions | Ericsson Canada Inc. |
TDoc | Title | Source |
---|---|---|
S5-251238 | Rel-19 CR TS 32.423 Corrections on Trace Record Format | Ericsson, AT&T |
S5-251375 | Introduction of Sequence Number in Trace Record Header | Jio Platforms Ltd (JPL) |
S5-251378 | Rel-19 CR TS 32.423 Introduction of Sequence Number in Trace Record Header | Jio Platforms Ltd (JPL) |
S5-251388 | Additional NFs added in Trace Record contents | Jio Platforms Ltd(JPL) |
S5-251405 | Introduction of Summary Code in Trace Record Header for Optimised Tracing | Jio Platforms Ltd (JPL) |
S5-251525 | Rel-19 CR TS 32.423 Introduction of Summary Code in Trace Record Header for Optimised Tracing | Jio Platforms Ltd (JPL) |
S5-251984 | Rel-19 CR TS 32.423 Corrections on Trace Record Format | Ericsson, AT&T |
TDoc | Title | Source |
---|---|---|
S5-251454 | Rel-19 CR TS 28.541 Add attributes to support MEC deployment on board the NTN | ZTE Corporation |
S5-251528 | CR 28.657 Add requirements for SnF support | Samsung R&D Institute UK |
S5-251556 | Rel-19 CR TS 28.540 Add new requirements for management of NTN | China Unicom |
S5-251576 | Rel-19 CR TS 28.541 add YAML stage 3 for NTN time based solution | Huawei |
S5-251585 | Rel-19 CR 28.540 Add secure backhaul requirements for NTN | Ericsson Canada Inc. |
S5-251586 | Rel-19 CR 28.541 Add solution for NTN time-based IP configuration | Ericsson Canada Inc. |
S5-251588 | Rel-19 CR 28.540 Add NTN regenerative concepts and requirements | Ericsson |
S5-251629 | Rel-19 CR TS 28.658 Add attributes to support Store and Forward Satellite operation for eNB | CATT |
S5-251630 | Rel-19 CR TS 28.658 Add attributes to support Store and Forward Satellite operation for eNB stage3 | CATT, Samsung |
S5-251631 | Rel-19 CR TS 28.708 Add attributes to support Store and Forward Satellite operation for EPC | CATT |
S5-251632 | Rel-19 CR TS 28.709 Add attributes to support Store and Forward Satellite operation for EPC stage3 | CATT |
S5-251985 | Rel-19 CR TS 28.541 Add attributes to support MEC deployment on board the NTN | ZTE Corporation |
S5-251986 | CR 28.657 Add requirements for SnF support | Samsung R&D Institute UK |
S5-251987 | Rel-19 CR 28.540 Add secure backhaul requirements for NTN | Ericsson Canada Inc. |
S5-251988 | Rel-19 CR 28.314 Add secure backhaul requirements for NTN | Ericsson Canada Inc. |
S5-251989 | Rel-19 CR 28.315 Add secure backhaul requirements for NTN | Ericsson Canada Inc. |
S5-251991 | Rel-19 CR 28.541 Add solution for NTN time-based IP configuration | Ericsson Canada Inc. |
S5-252024 | Rel-19 CR 28.540 Add NTN regenerative concepts and requirements | Ericsson |
S5-252025 | Rel-19 CR TS 28.658 Add attributes to support Store and Forward Satellite operation for eNB | CATT, Samsung |
S5-252026 | Rel-19 CR TS 28.659 Add attributes to support Store and Forward Satellite operation for eNB stage3 | CATT, Samsung |
S5-252027 | Rel-19 CR TS 28.708 Add attributes to support Store and Forward Satellite operation for EPC | CATT, Samsung |
S5-252028 | Rel-19 CR TS 28.709 Add attributes to support Store and Forward Satellite operation for EPC stage3 | CATT, Samsung |
S5-252110 | Rel-19 CR TS 28.541 add YAML stage 3 for NTN time based solution | Huawei |
TDoc | Title | Source |
---|---|---|
S5-251656 | Requirements for IAB-node connects to management system | Ericsson |
S5-251695 | Use case IAB-node connects to management system | Ericsson |
S5-251708 | Procedure IAB-node connects to management system | Ericsson |
S5-251992 | Requirements for IAB-node connects to management system | Ericsson |
S5-251993 | Procedure IAB-node connects to management system | Ericsson |
TDoc | Title | Source |
---|---|---|
S5-251455 | Rel-19 CR TS28.552 Enhance RRC connection resuming related measurements for RedCap UEs | ZTE Corporation |
S5-251456 | Rel-19 CR TS28.552 Enhance PRB Usage related measurements for RedCap UEs | ZTE Corporation |
S5-251457 | Rel-19 CR TS28.552 Enhance Number of Active UEs related measurements for RedCap UEs | ZTE Corporation |
S5-251745 | Rel-19 CR TS 28.540 Adding requirement to control RedCap and e-RedCap UEs access based on network conditions | Samsung Electronics GmbH |
S5-251748 | Rel-19 CR TS 28.541 Enhancing NR NRM to control RedCap and e-RedCap UEs access | Samsung Electronics GmbH |
S5-251994 | Rel-19 CR TS28.552 Enhance RRC connection resuming related measurements for RedCap UEs | ZTE Corporation, China Unicom, Ericsson |
S5-251995 | Rel-19 CR TS28.552 Enhance PRB Usage related measurements for RedCap UEs | ZTE Corporation, China Unicom, Ericsson |
S5-251996 | Rel-19 CR TS28.552 Enhance Number of Active UEs related measurements for RedCap UEs | ZTE Corporation, China Unicom, Ericsson |
S5-251997 | Rel-19 CR TS 28.540 Adding requirement to control RedCap and e-RedCap UEs access based on network conditions | Samsung Electronics GmbH |
S5-252111 | Rel-19 CR TS 28.541 Enhancing NR NRM to control RedCap and e-RedCap UEs access | Samsung Electronics GmbH |
TDoc | Title | Source |
---|---|---|
S5-251336 | Rel-19 CR 28.552 Add a new measurement related to efficiency of data collection from NFs performed by NWDAF | China Telecom |
S5-251337 | Rel-19 CR 28.552 Add a new measurement related to efficiency of data collection from DCCF or NWDAF hosting DCCF performed by NWDAF | China Telecom |
S5-251338 | Rel-19 CR 28.552 Add a new measurement related to transmission rate related to the data collection from NFs performed by NWDAF | China Telecom |
S5-251339 | Rel-19 CR 28.552 Add a new measurement related to transmission rate related to the data collection from DCCF or NWDAF hosting DCCF performed by NWDAF | China Telecom |
S5-251340 | Rel-19 CR 28.552 Add use case descriptions on monitoring of NWDAF data collection | China Telecom |
S5-251998 | Rel-19 CR 28.552 Add a new measurement related to efficiency of data collection from NFs performed by NWDAF | China Telecom, Ericsson |
S5-251999 | Rel-19 CR 28.552 Add a new measurement related to efficiency of data collection from DCCF or NWDAF hosting DCCF performed by NWDAF | China Telecom |
S5-252000 | Rel-19 CR 28.552 Add a new measurement related to transmission rate related to the data collection from NFs performed by NWDAF | China Telecom, Ericsson |
S5-252001 | Rel-19 CR 28.552 Add a new measurement related to transmission rate related to the data collection from DCCF or NWDAF hosting DCCF performed by NWDAF | China Telecom |
S5-252002 | Rel-19 CR 28.552 Add use case descriptions on monitoring of NWDAF data collection | China Telecom, Ericsson |
TDoc | Title | Source |
---|---|---|
S5-251374 | Rel-19 CR TS 32.130 Enhance the service-based management architecture for MOCN | Huawei, China Unicom |
S5-251376 | Rel-19 CR TS 32.130 Enhance Indirect Network Sharing scenario description | Huawei, China Unicom |
S5-251377 | Rel-19 CR TS 32.130 Clarify MOCN and GWCN scenarios description | Huawei, China Unicom |
S5-251379 | Rel-19 CR TS 32.130 Categorize requirements for the management support for Indirect Network Sharing scenario | Huawei, China Unicom |
S5-251381 | Rel-19 CR TS 32.130 Separate business-level requirements from specification-level requirements | Huawei, China Unicom |
S5-251650 | Rel-19 CR TS 28.541 Add support of RAN configurations for Indirect Network Sharing | China Unicom |
S5-251651 | Rel-19 CR TS 32.130 Update abbreviations for Indirect Network Sharing | China Unicom, China Telecom |
S5-251655 | Rel-19 CR TS 28.541 Add solution to support RAN configurations for Indirect Network Sharing | China Unicom, China Telecom |
S5-251732 | Rel-19 CR TS 32.130 Add PLMN granularity performance measurement requirements for Indirect Network Sharing | Esurfing IoT, China Unicom |
S5-252003 | Rel-19 CR TS 32.130 Enhance the service-based management architecture for MOCN | Huawei, China Unicom |
S5-252004 | Rel-19 CR TS 32.130 Enhance Indirect Network Sharing scenario description | Huawei, China Unicom |
S5-252005 | Rel-19 CR TS 32.130 Clarify MOCN and GWCN scenarios description | Huawei, China Unicom |
S5-252006 | Rel-19 CR TS 32.130 Categorize requirements for the management support for Indirect Network Sharing scenario | Huawei, China Unicom |
S5-252007 | Rel-19 CR TS 32.130 Update abbreviations for Indirect Network Sharing | China Unicom, China Telecom |
S5-252008 | Rel-19 CR TS 32.130 Add PLMN granularity performance measurement requirements for Indirect Network Sharing | Esurfing IoT, China Unicom |
TDoc | Title | Source |
---|---|---|
S5-251264 | Rel-19 CR TS 28.310 Introduce energy supply, carbon emission and renewable energy information elements | Nokia |
S5-251265 | Rel-19 CR TS 28.622 Add GenericCollection to support grouping of objects for energy related information - Stage 2 | Nokia |
S5-251266 | Rel-19 CR TS 28.623 Add GenericCollection to support grouping of objects for energy related information - Stage 3 | Nokia |
S5-251267 | Rel-19 CR TS 28.532 Introduce energy supply, carbon emission and renewable energy information elements - stage 3 impacts | Nokia |
S5-251268 | Rel-19 CR TS 28.310 Multi-carrier RAN energy saving optimization | Nokia |
S5-251269 | Rel-19 CR TS 28.104 Enhance the MDA assisted Energy Saving use case for handling of power shortages | Nokia |
S5-251270 | Discussion on modelling of energy-related information | Nokia |
S5-251271 | DP on TS 28.554 KPIs related to NF Energy Consumption | Nokia |
S5-251335 | Incorporation of conclusions from TR 28.880 | Vodafone |
S5-251386 | Rel-19 CR TS 28.310 Add information model definitions for energy related information | Huawei |
S5-251941 | Rel-19 CR TS 28.310 Introduce energy supply, carbon emission and renewable energy information elements | Nokia, Huawei, Orange, AT&T |
S5-251942 | Rel-19 CR TS 28.623 Add GenericCollection to support grouping of objects for energy related information - Stage 3 | Nokia |
S5-251943 | Incorporation of conclusions from TR 28.880 | Vodafone |
S5-251944 | Rel-19 CR TS 28.104 Enhance the MDA assisted Energy Saving use case for handling of power shortages | Nokia |
S5-251945 | Rel-19 CR TS 28.310 Multi-carrier RAN energy saving optimization | Nokia |
S5-252109 | Rel-19 CR TS 28.623 Update stage 3 to support energy information NRM | Nokia, Huawei, Orange, AT&T |
TDoc | Title | Source |
---|---|---|
S5-251373 | Rel-19 pCR TS 28.579 Introduce definition of External MnS consumer | Huawei |
S5-251483 | pCR TS 28.579 Add concepts content | Huawei, Nokia, Samsung |
S5-251484 | DP on management services exposure | Huawei |
S5-251485 | pCR TS 28.579 Introduce MSEDF | Huawei |
S5-251696 | Discussion paper on MSED components, requirements and naming | Nokia Hungary |
S5-251697 | Rel-19 pCR TS 28.579 Add use case and requirements for registration of the MSED into the CCF | Nokia Hungary |
S5-251698 | Rel-19 pCR TS 28.579 Add use case solution for registration of the MSED into the CCF | Nokia Hungary |
S5-251699 | Rel-19 pCR TS 28.579 Add use case requirements for publishing of management services to the CCF | Nokia Hungary |
S5-251700 | Rel-19 pCR TS 28.579 Add use case solution to enable the publishing management services to the CCF | Nokia Hungary |
S5-251701 | Rel-19 pCR TS 28.579 Add use case requirements for logging of management service APIs invocations to the CCF | Nokia Hungary |
S5-251702 | Rel-19 pCR TS 28.579 Add use case solution for logging the management service API invocations to the CCF | Nokia Hungary |
S5-251762 | Draft TS28.579 | Nokia |
S5-251946 | Rel-19 pCR TS 28.579 Introduce definition of External MnS consumer | Huawei |
S5-251947 | pCR TS 28.579 Add concepts content | Huawei, Nokia, Samsung, AT&T, Ericsson |
S5-251948 | Discussion paper on MSED components, requirements and naming | Nokia, Huawei, AT&T, Ericsson |
S5-251949 | Rel-19 pCR TS 28.579 Add use case and requirements for registration of the MSED into the CCF | Nokia Hungary |
S5-252036 | Rel-19 pCR TS 28.579 Add use case solution for registration of the MSED into the CCF | Nokia Hungary |
S5-252037 | Rel-19 pCR TS 28.579 Add use case requirements for publishing of management services to the CCF | Nokia Hungary |
S5-252038 | Rel-19 pCR TS 28.579 Add use case solution to enable the publishing management services to the CCF | Nokia Hungary |
S5-252039 | Rel-19 pCR TS 28.579 Add use case requirements for logging of management service APIs invocations to the CCF | Nokia Hungary |
S5-252126 | Rel-19 pCR TS 28.579 Introduce definition of External MnS consumer | Huawei, Ericsson, Nokia, Deutsche Telekom |
S5-252127 | Rel-19 pCR TS 28.579 Add use case and requirements for registration of the MSED into the CCF | Nokia Hungary, AT&T |
S5-252128 | Rel-19 pCR TS 28.579 Add use case solution for registration of the MSED into the CCF | Nokia Hungary, AT&T |
S5-252129 | Rel-19 pCR TS 28.579 Add use case requirements for publishing of management services to the CCF | Nokia Hungary, AT&T |
S5-252130 | Rel-19 pCR TS 28.579 Add use case solution to enable the publishing management services to the CCF | Nokia Hungary, AT&T |
S5-252131 | Rel-19 pCR TS 28.579 Add use case requirements for logging of management service APIs invocations to the CCF | Nokia Hungary, AT&T |
S5-252132 | Rel-19 pCR TS 28.579 Add use case solution for logging the management service API invocations to the CCF | Nokia Hungary, AT&T |
TDoc | Title | Source |
---|---|---|
S5-251734 | Correction of the description of the attribute stmTargetUri | Nokia Germany |
S5-252091 | Correction of the description of the attribute stmTargetUri | Nokia Germany, Ericsson |
TDoc | Title | Source |
---|---|---|
S5-251215 | agenda_with_Tdocs_sequence_CH | SWG CH Chair (MATRIXX Software) |
S5-251216 | Charging exec report | SWG CH Chair (MATRIXX Software) |
S5-251217 | Collection of useful contributions and external communication documents in CH | SWG Vice Chair (Huawei Tech.(UK) Co.. Ltd) |
S5-251329 | Reply LS on Usage of Charging Characteristics and CHF Group ID | SA2 |
S5-251800 | agenda_with_Tdocs_sequence_CH | SWG CH Chair (MATRIXX Software) |
TDoc | Title | Source |
---|---|---|
S5-251368 | Revised WID on on Charging aspects of next generation real time communication services phase 2 | China Mobile |
S5-251433 | Rel-20 DP Moderator update on Charging Aspects of CAPIF | Nokia |
S5-251463 | Moderated R20 topic discussion on use cases for charging reliability enhancement | Huawei |
S5-251533 | Revised WID on Charging for Uncrewed Aerial Systems Phase 3 | China Mobile Com. Corporation |
S5-251535 | Discussion paper on objective for UAS_Ph3-CH | China Mobile Com. Corporation |
S5-251801 | Revised WID on Charging for Uncrewed Aerial Systems Phase 3 | China Mobile Com. Corporation |
S5-251857 | Revised WID on on Charging aspects of next generation real time communication services phase 2 | China Mobile |
TDoc | Title | Source |
---|---|---|
S5-251291 | Correct bindings information for 5G ProSe Charging | China Telecom |
S5-251301 | Discussion on NSPA charging information correction | Huawei |
S5-251302 | Rel-18 CR 28.201 Correction on NSPA charging information | Huawei |
S5-251303 | Rel-19 CR 28.201 Correction on NSPA charging information | Huawei |
S5-251304 | Rel-18 CR 28.201 Correction on NSPA charging information | Huawei |
S5-251305 | Rel-19 CR 28.201 Correction on NSPA charging information | Huawei |
S5-251306 | Rel-18 CR 32.298 Correction on NSPA charging information | Huawei |
S5-251307 | Rel-19 CR 32.298 Correction on NSPA charging information | Huawei |
S5-251371 | Rel-19 CR 28.851 Cleanup | China Mobile |
S5-251434 | Rel-19 CR 28.849 EditHelp Editorial Changes | Nokia |
S5-251508 | Rel-19 DP Handling of un-reported usage information after failure | Ericsson |
S5-251526 | Rel-19 CR 28.851 Addressing editHelp comments | China Mobile |
S5-251531 | Correction of reference | China Mobile Com. Corporation |
S5-251604 | Rel-18 CR 32.298 Correction of API Information | Amdocs |
S5-251605 | Rel-19 CR 32.298 Correction of API Information | Amdocs Software Systems Ltd |
S5-251847 | Correct bindings information for 5G ProSe Charging | China Telecom |
S5-251850 | Rel-19 CR 28.849 EditHelp Editorial Changes | Nokia |
S5-251851 | Rel-19 CR 28.851 Addressing editHelp comments | China Mobile |
S5-251852 | Correction of reference | China Mobile Com. Corporation |
S5-251853 | Rel-18 CR 32.298 Correction of API Information | Amdocs |
S5-251854 | Rel-19 CR 32.298 Correction of API Information | Amdocs Software Systems Ltd |
TDoc | Title | Source |
---|---|---|
S5-251464 | Discussion on the charging domain for NRF registration and discovery | Huawei |
S5-251465 | Rel-19 CR 32.291 Add charging domain for NRF registration and discovery | Huawei |
S5-251509 | Rel-19 CR 32.291 Addition of domain features | Ericsson |
S5-251510 | Rel-19 CR 32.274 Addition of charging characteristics | Ericsson |
S5-251802 | Rel-19 CR 32.291 Addition of domain features | Ericsson |
S5-251803 | Rel-19 CR 32.274 Addition of charging characteristics | Ericsson |
TDoc | Title | Source |
---|---|---|
S5-251299 | Correct bindings information for 5G ProSe Charging | China Telecom |
S5-251300 | Correct bindings information for 5G ProSe Charging | China Telecom |
S5-251312 | Add layer 3 multi-hop ProSe UE-to-Network relay communication related attributes | China Telecom |
S5-251313 | Add layer 3 multi-hop ProSe UE-to-Network relay communication related CDR parameters | China Telecom |
S5-251315 | Add information flows of Layer-3 ProSe UE-to-UE direct communication | China Telecom Corporation Ltd. |
S5-251804 | Add layer 3 multi-hop ProSe UE-to-Network relay communication related CDR parameters | China Telecom |
S5-251848 | Correct bindings information for 5G ProSe Charging | China Telecom |
S5-251849 | Correct bindings information for 5G ProSe Charging | China Telecom |
S5-251856 | Add layer 3 multi-hop ProSe UE-to-Network relay communication related attributes | China Telecom |
TDoc | Title | Source |
---|---|---|
S5-251466 | Rel-19 CR 32.255 Addition of the Satellite Roaming Charging Principle | Huawei |
S5-251580 | Update Business roles for Support of Satellite charging | CSCN, CATT |
S5-251592 | Update Charging principles and architecture references for MVNOs charging | CSCN |
S5-251640 | Introduce the support of store and forward satellite operation and UE-satellite-UE communication | CATT |
S5-251641 | Add charging principle for store and forward satellite operation | CATT |
S5-251642 | Add charging information for store and forward satellite operation of SMS service | CATT |
S5-251643 | Add charging trigger for store and forward satellite operation with UP CIoT | CATT |
S5-251644 | Add charging information for store and forward satellite operation with UP CIoT | CATT |
S5-251645 | Add charging principle for UE-satellite-UE communication | CATT |
S5-251646 | Add charging trigger and charging information for UE-satellite-UE communication | CATT |
S5-251647 | Update reference for the TR | CATT |
S5-251805 | Update Charging principles and architecture references for MVNOs charging | CSCN |
S5-251806 | Introduce the support of store and forward satellite operation and UE-satellite-UE communication | CATT |
S5-251807 | Rel-19 CR 32.255 Addition of the Satellite Roaming Charging Principle | Huawei |
S5-251808 | Add charging principle for store and forward satellite operation | CATT |
S5-251809 | Add charging information for store and forward satellite operation of SMS service | CATT |
S5-251810 | Add charging trigger for store and forward satellite operation with UP CIoT | CATT |
S5-251811 | Add charging information for store and forward satellite operation with UP CIoT | CATT |
S5-251812 | Add charging principle for UE-satellite-UE communication | CATT |
S5-251813 | Add charging trigger and charging information for UE-satellite-UE communication | CATT |
S5-251855 | Update reference for the TR | CATT |
TDoc | Title | Source |
---|---|---|
S5-251428 | CR 32.254 CAPIF Converged charging Architecture | Nokia |
S5-251435 | Rel-19 CR 32.240 CAPIF Logical Charging Architecture | Nokia |
S5-251436 | Rel-19 CR 32.240 CAPIF Service Charging | Nokia |
S5-251437 | Rel-19 CR 32.240 CAPIF Reference Point | Nokia |
S5-251467 | Rel-19 CR 32.254 Addition of the CAPIF Charging Architecture | Huawei |
S5-251468 | Rel-19 CR 32.254 Addition of the CAPIF Charging Principle and Scenarios | Huawei |
S5-251469 | Rel-19 CR 32.254 Addition of CAPIF charging support | Huawei |
S5-251511 | Rel-19 DP Charging architecture considerations for CAPIF | Ericsson |
S5-251512 | Rel-19 CR 32.254 Addition of charging architecture for CAPIF | Ericsson |
S5-251513 | Rel-19 CR 32.254 Addition of charging principles for CAPIF | Ericsson |
S5-251814 | Rel-19 CR 32.240 CAPIF Logical Charging Architecture | Nokia |
S5-251815 | Rel-19 CR 32.240 CAPIF Service Charging | Nokia |
S5-251816 | Rel-19 CR 32.254 Addition of charging architecture for CAPIF | Ericsson |
S5-251817 | Rel-19 CR 32.254 Addition of charging principles for CAPIF | Ericsson |
S5-251818 | Rel-19 CR 32.254 Addition of CAPIF charging support | Huawei |
TDoc | Title | Source |
---|---|---|
S5-251369 | Rel-19 CR 32.255 Support volume-based charging for standalone IMS data channel | China Mobile |
S5-251370 | Rel-19 CR 32.260 Support duration-based charging for standalone IMS data channel | China Mobile |
S5-251470 | Rel-19 CR 32.260 Charging architecture for IMS DC application download charging charging | Huawei |
S5-251471 | Rel-19 CR 32.260 Charging principle for IMS DC application download charging | Huawei |
S5-251472 | Rel-19 CR 32.260 Charging information for IMS DC application download charging | Huawei |
S5-251473 | Rel-19 CR 32.291 Charging information for IMS DC application download charging | Huawei |
S5-251474 | Rel-19 CR 32.298 Charging information for IMS DC application download charging | Huawei |
S5-251475 | Rel-19 CR 32.260 Add duration based charging principle for DC application usage | Huawei |
S5-251476 | Rel-19 CR 32.255 Add volume based charging principle for DC application download and usage | Huawei |
S5-251477 | Rel-19 CR 32.255 Add volume based charging principle to support IMS DC as a PS Data Off Exempt Service | Huawei |
S5-251478 | Rel-19 CR 32.254 Add charging principle for IMS network capabilities exposure | Huawei |
S5-251819 | Rel-19 CR 32.255 Support volume-based charging for standalone IMS data channel | China Mobile |
S5-251820 | Rel-19 CR 32.255 Add volume based charging principle for DC application download and usage | Huawei |
S5-251821 | Rel-19 CR 32.255 Add volume based charging principle to support IMS DC as a PS Data Off Exempt Service | Huawei |
S5-251822 | Rel-19 CR 32.260 Support duration-based charging for standalone IMS data channel | China Mobile |
S5-251823 | Rel-19 CR 32.260 Charging architecture for IMS DC application download charging charging | Huawei |
S5-251824 | Rel-19 CR 32.260 Charging principle for IMS DC application download charging | Huawei |
S5-251825 | Rel-19 CR 32.260 Charging information for IMS DC application download charging | Huawei |
S5-251826 | Rel-19 CR 32.291 Charging information for IMS DC application download charging | Huawei |
S5-251827 | Rel-19 CR 32.298 Charging information for IMS DC application download charging | Huawei |
S5-251828 | Rel-19 CR 32.254 Add charging principle for IMS network capabilities exposure | Huawei |
TDoc | Title | Source |
---|---|---|
S5-251514 | Rel-19 DP Format of user identity | Ericsson |
S5-251515 | Rel-19 CR 32.255 Addition of user identifiers | Ericsson |
TDoc | Title | Source |
---|---|---|
S5-251341 | Extend the scope and charging architecture to support 5G LCS converged charging | China Telecom |
S5-251342 | Extend basic priciples, CDR generation and handling for 5G LCS converged charging | China Telecom |
S5-251343 | Add message flow of converged charging for 5GC-MT-LR | China Telecom |
S5-251344 | Add message flow of converged charging for 5GC-MO-LR | China Telecom |
S5-251345 | Extend data description for 5G LCS converged charging | China Telecom |
S5-251346 | Extend charging information and bindings for 5G LCS converged charging | China Telecom |
S5-251347 | Extend Data Type for 5G LCS converged charging | China Telecom |
S5-251348 | Extend CHF-CDR for 5G LCS converged charging | China Telecom |
S5-251516 | Rel-19 CR 32.271 Addition of LCS architecture | Ericsson |
S5-251517 | Rel-19 CR 32.271 Addition of charging architecture for LCS | Ericsson |
S5-251518 | Rel-19 CR 32.271 Addition of charging principles for LCS | Ericsson |
S5-251829 | Extend the scope and charging architecture to support 5G LCS converged charging | China Telecom |
S5-251830 | Extend basic priciples, CDR generation and handling for 5G LCS converged charging | China Telecom |
S5-251831 | Rel-19 CR 32.271 Addition of LCS architecture | Ericsson |
S5-251832 | Add message flow of converged charging for 5GC-MT-LR | China Telecom |
S5-251833 | Add message flow of converged charging for 5GC-MO-LR | China Telecom |
S5-251834 | Extend data description for 5G LCS converged charging | China Telecom |
S5-251835 | Extend charging information and bindings for 5G LCS converged charging | China Telecom |
S5-251836 | Extend Data Type for 5G LCS converged charging | China Telecom |
S5-251837 | Extend CHF-CDR for 5G LCS converged charging | China Telecom |
TDoc | Title | Source |
---|---|---|
S5-251308 | Rel-19 CR 32.240 Add charging support for AIoT service | Huawei |
S5-251309 | Rel-19 CR 32.254 Add charging support for AIoT service | Huawei |
S5-251310 | Rel-19 CR 32.291 Add charging support for AIoT service | Huawei |
S5-251311 | Rel-19 CR 32.298 Add charging support for AIoT service | Huawei |
S5-251838 | Rel-19 CR 32.240 Add charging support for AIoT service | Huawei |
S5-251839 | Rel-19 CR 32.254 Add charging support for AIoT service | Huawei |
S5-251840 | Rel-19 CR 32.291 Add charging support for AIoT service | Huawei |
S5-251841 | Rel-19 CR 32.298 Add charging support for AIoT service | Huawei |
TDoc | Title | Source |
---|---|---|
S5-251519 | Rel-19 CR 32.240 Addition of MOCN network sharing | Ericsson |
S5-251520 | Rel-19 CR 32.255 Addition of architecture for MOCN | Ericsson |
S5-251521 | Rel-19 CR 32.256 Addition of architecture for network sharing | Ericsson |
S5-251522 | Rel-19 CR 32.255 Addition of charging architecture for MOCN | Ericsson |
S5-251523 | Rel-19 CR 32.255 Addition of charging requirements for MOCN | Ericsson |
S5-251842 | Rel-19 CR 32.240 Addition of MOCN network sharing | Ericsson |
S5-251843 | Rel-19 CR 32.255 Addition of architecture for MOCN | Ericsson |
S5-251844 | Rel-19 CR 32.255 Addition of charging architecture for MOCN | Ericsson |
S5-251845 | Rel-19 CR 32.255 Addition of charging requirements for MOCN | Ericsson |
S5-251846 | Rel-19 CR 32.256 Addition of architecture for network sharing | Ericsson |