Please enter the search related information in the fields below. Partial information works, e.g. "SP-21" in the "tdoc" field lists all TSG SA documents from 2021. Regular expressions mostly work in all fields (e.g. "2[34].501" in the "Spec" field lists all documents related to 23.501 and 24.501. Capitalization is disregarded, i.e. "3GPP" gives the same results as "3gpp".
Download results in JSON format
| tdoc | Title | Type / Revs | Source | Spec / CR | S/WID | Release | Meeting | Status | Links |
|---|---|---|---|---|---|---|---|---|---|
| S5-202024 | LS reply ccSA5 on initiation of a new work item Y.IMT2020-NSC “IMT-2020 network slice configuration | LS in | GSMA |
S5-ah-35870 AI: 6.4.5 |
noted | [WTS] [JSN] | |||
| S5-202033 | Discussion on restructure RRMPolicyRatio | discussion | Huawei, Ericsson,CATT,China Telecom, China Mobile | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
endorsed | [WTS] [JSN] | |
| S5-202034 | Rel-16 CR TS 28.541 Update on RRMPolicyRatio |
CR revised to S5-202368 |
Huawei, Ericsson,CATT,China Telecom, China Mobile | 28.541 16.4.1 CR#259 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202086 | YANG-Push Notifications | CR | Ericsson Hungary Ltd | 28.532 16.3.0 CR#108 catB | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
not pursued | [WTS] [JSN] |
| S5-202101 | Rel-16 CR 28.541 Add IOC for control of QoS monitoring per QoS flow per UE |
CR revised to SP-200603 |
Intel Finland Oy | 28.541 16.4.1 CR#261 catB | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202103 | Rel-16 CR 28.541 Add IOC for control of GTP-U path QoS monitoring |
CR revised to SP-200604 |
Intel Finland Oy | 28.541 16.4.1 CR#262 catB | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202182 | Rel-16 CR 28.623 Add OpenAPI definitions for the FM control fragment |
CR revised to S5-203242 |
Nokia, Nokia Shanghai Bell | 28.623 16.3.2 CR#46 catB | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202183 | Rel-16 CR TS 28.541 Add NRPhysicalCellDU and NRCarrier NRM to support Multi-SSBs and network sharing | CR | ZTE Corporation | 28.541 16.4.1 CR#266 catB | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
not pursued | [WTS] [JSN] |
| S5-202184 | Rel-16 CR 28.623 Correct OpenAPI definition for notificationTypes |
CR revised to S5-202375 |
Nokia, Nokia Shanghai Bell | 28.623 16.3.2 CR#47 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202190 | Discussion paper clarification on network slice related identifiers |
discussion revised to S5-202364 |
Huawei | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] | |
| S5-202191 | Rel-16 CR 28.541 Clarification on network slice related identifiers |
CR revised to S5-202365 |
Huawei | 28.541 16.4.1 CR#269 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202192 | Rel-16 CR 28.530 Clarification on network slice related identifiers | CR | Huawei | 28.53 16.1.0 CR#24 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202193 | Rel-16 CR 28.531 Clarification on network slice related identifiers |
CR revised to S5-202367 |
Huawei | 28.531 16.5.0 CR#47 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202194 | Rel-16 CR 28.541 Stage 3 update for clarification on network slice related identifiers | CR | Huawei | 28.541 16.4.1 CR#270 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202195 | LS to SA2 on network slice identifiers |
LS out LS To: SA2 |
Huawei | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
withdrawn | [WTS] [JSN] | |
| S5-202201 | Discussion paper on non-binary description of neighbor cell relations | CR | Nokia Germany | 28.541 16.4.1 CR#271 catB | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
withdrawn | [WTS] [JSN] |
| S5-202203 | Rel-16 CR TS 28.622 Add TOP_ as parent class |
CR revised to S5-202376 |
ZTE Corporation | 28.622 16.3.0 CR#74 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202204 | Rel-16 CR 28.541 Extend description of NRCellRelation | CR | Nokia, Nokia Shanghai Bell | 28.541 16.4.1 CR#272 catB | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
not pursued | [WTS] [JSN] |
| S5-202205 | Discussion paper on non-binary description of neighbor cell relations | discussion | Nokia, Nokia Shanghai Bell | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
noted | [WTS] [JSN] | |
| S5-202206 | Rel-16 CR TS 28.541 Add TOP_ as parent class | CR | ZTE Corporation | 28.541 16.4.1 CR#273 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
not pursued | [WTS] [JSN] |
| S5-202207 | Rel-16 CR TS 28.541 Correct sNSSAI definition in XML solution |
CR revised to S5-202380 |
ZTE Corporation | 28.541 16.4.1 CR#274 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202212 | Update YANG Guidelines |
CR revised to S5-202381 |
Ericsson Hungary Ltd | 32.16 16.2.0 CR#8 catB | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202219 | CR TS 28.622 Update concept of ME and MF |
CR revised to S5-202377 |
Huawei Technologies (Korea) | 28.622 16.3.0 CR#75 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202235 | Rel-16 CR TS 28.622 Update the attribute priorityLabel for several IOCs | CR | Huawei | 28.622 16.3.0 CR#76 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202236 | Rel-16 CR TS 28.541 Clarify the NR NRM used for different deployment scenarios |
CR revised to S5-202379 |
Huawei,China Mobile | 28.541 16.4.1 CR#275 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202250 | Discussion on the NRM of MF contains other MF | discussion | China Mobile E-Commerce Co., Huawei | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
noted | [WTS] [JSN] | ||
| S5-202253 | Rel-16 CR TS 28.622 Updated MF description with nested clarification |
CR revised to S5-202378 |
China Mobile E-Commerce Co., Huawei | 28.622 16.3.0 CR#77 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202262 | Rel-16 CR 28.541 Add missing notification types to the definition of common notifications | CR | Nokia, Nokia Shanghai Bell | 28.541 16.4.1 CR#278 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202269 | Rel-16 CR TS 28.541 Update on NRCellDU |
CR revised to S5-202371 |
Huawei | 28.541 16.4.1 CR#279 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202270 | Rel-15 CR TS 28.541 Update on NRCellDU |
CR revised to S5-202372 |
Huawei | 28.541 15.5.0 CR#280 catA | eNRM | Rel-15 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202271 | Rel-16 CR TS 28.541 Update Clause 4.2.1.2 Inheritance UML diagram |
CR revised to S5-202373 |
Huawei | 28.541 16.4.1 CR#281 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202272 | Rel-15 CR TS 28.541 Update Clause 4.2.1.2 Inheritance UML diagram |
CR revised to S5-202374 |
Huawei | 28.541 15.5.0 CR#282 catA | eNRM | Rel-15 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202281 | TD proposal of NRM change to support RIM |
discussion revised to S5-202369 |
Nokia, Nokia Shanghai Bell | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] | |
| S5-202282 | new NRM fragment to support RIM stage 2 |
CR revised to S5-202370 |
Nokia, Nokia Shanghai Bell | 28.541 16.4.1 CR#283 catB | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202283 | new NRM fragment to support RIM stage 3 |
CR revised to S5-202342, S5-203329 |
Nokia, Nokia Shanghai Bell | 28.541 16.4.1 CR#284 catB | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
revised | [WTS] [JSN] |
| S5-202297 | Update stage3 on the RRMpolicyRatio | CR | Huawei,Ericsson, CATT, China Telecom, China Mobile | 28.541 16.4.1 CR#285 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202342 | new NRM fragment to support RIM stage 3 |
CR revision of S5-202283 |
Nokia, Nokia Shanghai Bell | 28.541 16.4.1 CR#2841 catB | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202364 | Discussion paper clarification on network slice related identifiers |
discussion revision of S5-202190 |
Huawei, Nokia, Nokia Shanghai Bell | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
endorsed | [WTS] [JSN] | |
| S5-202365 | Rel-16 CR 28.541 Clarification on network slice related identifiers |
CR revision of S5-202191 |
Huawei, Nokia, Nokia Shanghai Bell | 28.541 16.4.1 CR#2691 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202367 | Rel-16 CR 28.531 Clarification on network slice related identifiers |
CR revision of S5-202193 |
Huawei | 28.531 16.5.0 CR#471 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202368 | Rel-16 CR TS 28.541 Update on RRMPolicyRatio |
CR revision of S5-202034 |
Huawei, Ericsson,CATT,China Telecom, China Mobile | 28.541 16.4.1 CR#2591 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202369 | TD proposal of NRM change to support RIM |
discussion revision of S5-202281 |
Nokia, Nokia Shanghai Bell | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
endorsed | [WTS] [JSN] | |
| S5-202370 | new NRM fragment to support RIM stage 2 |
CR revision of S5-202282 revised to S5-203390 |
Nokia, Nokia Shanghai Bell | 28.541 16.4.1 CR#2831 catB | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202371 | Rel-16 CR TS 28.541 Update on NRCellDU |
CR revision of S5-202269 |
Huawei | 28.541 16.4.1 CR#2791 catA | NETSLICE-5GNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202372 | Rel-15 CR TS 28.541 Update on NRCellDU |
CR revision of S5-202270 |
Huawei | 28.541 15.5.0 CR#2801 catF | NETSLICE-5GNRM | Rel-15 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202373 | Rel-16 CR TS 28.541 Update Clause 4.2.1.2 Inheritance UML diagram |
CR revision of S5-202271 |
Huawei | 28.541 16.4.1 CR#2811 catA | NETSLICE-5GNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202374 | Rel-15 CR TS 28.541 Update Clause 4.2.1.2 Inheritance UML diagram |
CR revision of S5-202272 |
Huawei | 28.541 15.5.0 CR#2821 catF | NETSLICE-5GNRM | Rel-15 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202375 | Rel-16 CR 28.623 Correct OpenAPI definition for notificationTypes |
CR revision of S5-202184 |
Nokia, Nokia Shanghai Bell | 28.623 16.3.2 CR#471 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202376 | Rel-16 CR TS 28.622 Add TOP_ as parent class |
CR revision of S5-202203 |
ZTE Corporation | 28.622 16.3.0 CR#741 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202377 | CR TS 28.622 Update concept of ME and MF |
CR revision of S5-202219 |
Huawei Technologies (Korea) | 28.622 16.3.0 CR#751 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202378 | Rel-16 CR TS 28.622 Updated MF description with nested clarification |
CR revision of S5-202253 |
China Mobile E-Commerce Co., Huawei | 28.622 16.3.0 CR#771 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202379 | Rel-16 CR TS 28.541 Clarify the NR NRM used for different deployment scenarios |
CR revision of S5-202236 |
Huawei,China Mobile | 28.541 16.4.1 CR#2751 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202380 | Rel-16 CR TS 28.541 Correct sNSSAI definition in XML solution |
CR revision of S5-202207 |
ZTE Corporation | 28.541 16.4.1 CR#2741 catF | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
| S5-202381 | Update YANG Guidelines |
CR revision of S5-202212 |
Ericsson Hungary Ltd | 32.16 16.2.0 CR#81 catB | eNRM | Rel-16 |
S5-ah-35870 AI: 6.4.5 |
agreed | [WTS] [JSN] |
54 documents (0.34778499603271 seconds)