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 |
|---|---|---|---|---|---|---|---|---|---|
| S6-244215 | Skeleton for new TR 23.700-35 |
draft TR revised to S6-244531 |
Huawei, Hisilicon | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] | |
| S6-244216 | Scope for new TR 23.700-35 |
pCR revised to S6-244532 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244217 | References information in new TR 23.700-35 | pCR | Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
approved | [WTS] [JSN] |
| S6-244218 | 3GPP system architecture supporting SEAL services |
pCR revised to S6-244533 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244219 | Layered representation of 3GPP network exposure |
pCR revised to S6-244534 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244220 | Requirements for API invoker friendly |
pCR revised to S6-244535 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244221 | key issue of SEAL services for API invoker friendly |
pCR revised to S6-244536 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244222 | Solution for API invoker friendly criterial |
pCR revised to S6-244537 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244223 | Key issue for linking SEAL services to target maketing |
pCR revised to S6-244538 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244224 | Solution for linking LMS to target marketing | pCR | Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
withdrawn | [WTS] [JSN] |
| S6-244225 | key issue of the Role of location management client | pCR | Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
noted | [WTS] [JSN] |
| S6-244226 | Solution for the Role of location management client |
pCR revised to S6-244539 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244227 | The roles of SEAL clients |
pCR revised to S6-244540 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244291 | pCR on new KI on NRM XR API |
pCR revised to S6-244541 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244292 | pCR on new solution to KI on NRM XR API | pCR | Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
postponed | [WTS] [JSN] |
| S6-244304 | Solution for linking LMS to target marketing |
pCR revised to S6-244542 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244531 | Skeleton for new TR 23.700-35 |
draft TR revision of S6-244215 |
Huawei, Hisilicon | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
approved | [WTS] [JSN] | |
| S6-244532 | Scope for new TR 23.700-35 |
pCR revision of S6-244216 revised to S6-244653 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244533 | 3GPP system architecture supporting SEAL services |
pCR revision of S6-244218 revised to S6-244657 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244534 | Layered representation of 3GPP network exposure |
pCR revision of S6-244219 revised to S6-244658 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244535 | Requirements for API invoker friendly |
pCR revision of S6-244220 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
approved | [WTS] [JSN] |
| S6-244536 | key issue of SEAL services for API invoker friendly |
pCR revision of S6-244221 revised to S6-244659 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244537 | Solution for API invoker friendly criterial |
pCR revision of S6-244222 revised to S6-244660 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244538 | Key issue for linking SEAL services to target maketing |
pCR revision of S6-244223 revised to S6-244675 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244539 | Solution for the Role of location management client |
pCR revision of S6-244226 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
postponed | [WTS] [JSN] |
| S6-244540 | The roles of SEAL clients |
pCR revision of S6-244227 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
postponed | [WTS] [JSN] |
| S6-244541 | pCR on new KI on NRM XR API |
pCR revision of S6-244291 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
approved | [WTS] [JSN] |
| S6-244542 | Solution for linking LMS to target marketing |
pCR revision of S6-244304 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
postponed | [WTS] [JSN] |
| S6-244622 | Clarification on signalling transmission connection establishment |
pCR revised to S6-244702 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
revised | [WTS] [JSN] |
| S6-244623 | Clarification on low latency signalling transmission connection establishment | pCR | Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
postponed | [WTS] [JSN] |
| S6-244624 | SEALDD enabled Bandwidth guarantee transmission connection establishment | pCR | Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
postponed | [WTS] [JSN] |
| S6-244625 | SEALDD enabled reliable guarantee data transmission connection establishment | pCR | Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
postponed | [WTS] [JSN] |
| S6-244626 | SEALDD enabled Bandwidth guarantee transmission connection establishment | pCR | Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
postponed | [WTS] [JSN] |
| S6-244653 | Scope for new TR 23.700-35 |
pCR revision of S6-244532 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
approved | [WTS] [JSN] |
| S6-244657 | 3GPP system architecture supporting SEAL services |
pCR revision of S6-244533 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
approved | [WTS] [JSN] |
| S6-244658 | Layered representation of 3GPP network exposure |
pCR revision of S6-244534 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
approved | [WTS] [JSN] |
| S6-244659 | key issue of SEAL services for API invoker friendly |
pCR revision of S6-244536 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
approved | [WTS] [JSN] |
| S6-244660 | Solution for API invoker friendly criterial |
pCR revision of S6-244537 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
approved | [WTS] [JSN] |
| S6-244675 | Key issue for linking SEAL services to target maketing |
pCR revision of S6-244538 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
approved | [WTS] [JSN] |
| S6-244702 | Clarification on signalling transmission connection establishment |
pCR revision of S6-244622 |
Huawei, Hisilicon | 23.700-35 0.0.0 | FS_SEAL_Ph4 | Rel-19 |
S6-63 AI: 8.9 |
approved | [WTS] [JSN] |
40 documents (0.39863920211792 seconds)