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-233228 | pCR TR 28.912 enhance service support expectation | pCR | Nokia | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
not treated | [WTS] [JSN] |
| S5-233229 | pCR TR 28.912 intents for slice-based cell configuration | pCR | Nokia | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
not treated | [WTS] [JSN] |
| S5-233230 | pCR TR 28.912 Intent Fullfillment feedback |
pCR revised to S5-233231 |
Nokia | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
revised | [WTS] [JSN] |
| S5-233231 | pCR TR 28.912 Potential Solution on Intent-driven Closed Loop control |
pCR revision of S5-233230 revised to S5-233558 |
Nokia | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
revised | [WTS] [JSN] |
| S5-233274 | pCR TR 28.912 Update the Issue#4.6 Intent-driven closed loop control |
pCR revised to S5-233559 |
Huawei, Deutsche Telekom | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
revised | [WTS] [JSN] |
| S5-233388 | pCR TR 28.912 Add intent fulfilment feasibility information into intent report |
pCR revised to S5-233560 |
ZTE Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
revised | [WTS] [JSN] |
| S5-233389 | pCR TR 28.912 Clarification on Issue 4.1 intent driven approach for RAN energy saving |
pCR revised to S5-233562 |
ZTE Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
revised | [WTS] [JSN] |
| S5-233390 | pCR TR 28.912 Clarification on Issue 4.2 Intent conflicts |
pCR revised to S5-233563 |
ZTE Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
revised | [WTS] [JSN] |
| S5-233392 | pCR TR 28.912 Clarification on Issue 4.5 Intent report | pCR | ZTE Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
noted | [WTS] [JSN] |
| S5-233394 | pCR TR 28.912 Clarification on Issue 4.7 Monitoring intent fulfilment information | pCR | ZTE Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
noted | [WTS] [JSN] |
| S5-233473 | Intent fulfillment feasibility check and corresponding solutions |
pCR revised to S5-233561 |
China Mobile Com. Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
revised | [WTS] [JSN] |
| S5-233474 | Clarifying the use of ObjectContext and defining another value Property for configuration expectations |
pCR revised to S5-233565 |
China Mobile Com. Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
revised | [WTS] [JSN] |
| S5-233475 | issue#4.11 Generic information model definition enhancement | pCR | China Mobile Com. Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
noted | [WTS] [JSN] |
| S5-233476 | issue#4.5.1 Intent report description enhancement |
pCR revised to S5-233564 |
China Mobile Com. Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
revised | [WTS] [JSN] |
| S5-233477 | issue#4.5.1 Intent report potential solution#1 enhancement |
pCR revised to S5-233585 |
China Mobile Com. Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
revised | [WTS] [JSN] |
| S5-233513 | pCR TR 28.912 Add solutions for monitoring intent fulfilment | pCR | China Mobile E-Commerce Co. | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
noted | [WTS] [JSN] |
| S5-233558 | pCR TR 28.912 Potential Solution on Intent-driven Closed Loop control |
pCR revision of S5-233231 |
Nokia | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
approved | [WTS] [JSN] |
| S5-233559 | pCR TR 28.912 Update the Issue#4.6 Intent-driven closed loop control |
pCR revision of S5-233274 |
Huawei, Deutsche Telekom | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
approved | [WTS] [JSN] |
| S5-233560 | pCR TR 28.912 Add intent fulfilment feasibility information into intent report |
pCR revision of S5-233388 |
ZTE Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
approved | [WTS] [JSN] |
| S5-233561 | Intent fulfillment feasibility check and corresponding solutions |
pCR revision of S5-233473 |
China Mobile Com. Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
approved | [WTS] [JSN] |
| S5-233562 | pCR TR 28.912 Clarification on Issue 4.1 intent driven approach for RAN energy saving |
pCR revision of S5-233389 |
ZTE Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
approved | [WTS] [JSN] |
| S5-233563 | pCR TR 28.912 Clarification on Issue 4.2 Intent conflicts |
pCR revision of S5-233390 |
ZTE Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
approved | [WTS] [JSN] |
| S5-233564 | issue#4.5.1 Intent report description enhancement |
pCR revision of S5-233476 |
China Mobile Com. Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
approved | [WTS] [JSN] |
| S5-233565 | Clarifying the use of ObjectContext and defining another value Property for configuration expectations |
pCR revision of S5-233474 |
China Mobile Com. Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
approved | [WTS] [JSN] |
| S5-233585 | issue#4.5.1 Intent report potential solution#1 enhancement |
pCR revision of S5-233477 |
China Mobile Com. Corporation | 28.912 1.2.0 | FS_eIDMS_MN | Rel-18 |
S5-148-e AI: 6.7.3.2 |
approved | [WTS] [JSN] |
25 documents (0.3669171333313 seconds)