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 |
---|---|---|---|---|---|---|---|---|---|
S2-2201974 | New Solution to KI#3: URSPs into PCO for EPC. |
pCR revised to S2-2203121 |
Ericsson | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202060 | New Solution on KI#6: Traffic Category with existing mechanism. |
pCR revised to S2-2203125 |
Huawei, HiSilicon | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202066 | Solution for Key Issue#1: Provisioning V-URSP rules for roaming scenario. | pCR | Samsung | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
noted | [WTS] [JSN] |
S2-2202067 | Solution for Key Issue #2: URSP compliance verification. |
pCR revised to S2-2203113 |
Samsung | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202265 | Solution for KI#2: PSI reporting for awareness of URSP enforcement. |
pCR revised to S2-2203114 |
China Unicom | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202415 | KI#3, New Solution: Provisioning consistent URSP to UE across 5GS and EPS for Single PCF Deployment |
pCR revised to S2-2203122 |
Intel | 23.700-33 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202444 | Solution for KI#4: UE provisioned/configured with a mapping of application traffic to traffic categories. |
pCR revised to S2-2203126 |
Lenovo | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202452 | 23.700-85: Solution for KI#3; Indication of applicability of URSP to UE in EPS. | pCR | Nokia, Nokia Shanghai Bell | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2202453 | 23.700-85: Solution for KI#4; Support standardized and operator-specific traffic categories in URSP. |
pCR revised to S2-2203127 |
Nokia, Nokia Shanghai Bell | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202454 | 23.700-85: Solution for KI#1; URSP provisioning when a UE is not served by its home operator. |
pCR revised to S2-2203610 |
Nokia, Nokia Shanghai Bell | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202467 | Solution for KI#2: Per-PDU session awareness of URSP enforcement. |
pCR revised to S2-2203115 |
Lenovo | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202469 | Solution for KI#1: VPLMN influencing URSP rules creation in an HPLMN. |
pCR revised to S2-2203609 |
Lenovo | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202474 | Solution for the KI#4: Introduction of Traffic Category into URSP rules. |
pCR revised to S2-2203128 |
Vivo | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202475 | Solution for the KI#2: Network based URSP rules enforcement feedback. | pCR | Vivo | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2202476 | TR 23.700-85: New solution for URSP provisioning and updating in roaming. | pCR | Vivo | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2202545 | Solution for KI#3 consistent URSP provisioning to UE across 5GS and EPS. | pCR | OPPO | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
merged | [WTS] [JSN] |
S2-2202549 | Solution for KI#2 5GC awareness of URSP enforcement. |
pCR revised to S2-2203116 |
OPPO | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202556 | Solution for 5GC awareness of URSP enforcement. |
pCR revised to S2-2203117 |
Huawei, HiSilicon | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202557 | Solution for URSP in VPLMN. | pCR | Huawei, HiSilicon | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2202574 | KI#1, New Sol: URSP determination based on service parameter obtained from VPLMN. |
pCR revised to S2-2203112 |
LG Electronics | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202699 | EUEPO solution for Key Issue 2. |
pCR revised to S2-2203118 |
China Telecom | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202701 | KI#4, New Sol: Support standardized and operator-specific traffic categories in URSP. | pCR | China Telecom | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2202744 | Solution: KI#3 Provision consistent URSP to UE across 5GS and EPS |
pCR revised to S2-2203123 |
NEC | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202762 | KI#2, New Sol: 5GC awareness of URSP rule evaluation and verification of network slice usage. |
pCR revised to S2-2203119 |
Orange | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202771 | TR 23.700-85: KI#1, new solution proposal on URSP in VPLMN. |
pCR revised to S2-2203594 |
Qualcomm Incorporated, Intel | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202808 | Solution for KI#3: Provision consistent URSP to UE across 5GS and EPS. |
pCR revised to S2-2203124 |
Samsung | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202860 | KI#2 new Solution X: UE URSP enforcement validation by the network. |
pCR revised to S2-2203120 |
NEC | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202887 | New Sol for KI#1: Influencing the determination of USRP rules with VPLMN URSP Guidance. | pCR | Apple | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
noted | [WTS] [JSN] |
S2-2202940 | 23.700-85: Solution for KI #4 Traffic categories based on 5G QoS characteristics. |
pCR revised to S2-2203129 |
Apple | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
revised | [WTS] [JSN] |
S2-2202941 | 23.700-85: Solution for KI #3 URSP in EPS. | pCR | Apple | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
merged | [WTS] [JSN] |
S2-2203112 | KI#1, New Sol: URSP determination based on service parameter obtained from VPLMN. |
pCR revision of S2-2202574 |
LG Electronics | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203113 | Solution for Key Issue #2: URSP compliance verification. |
pCR revision of S2-2202067 |
Samsung | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203114 | Solution for KI#2: PSI reporting for awareness of URSP enforcement. |
pCR revision of S2-2202265 |
China Unicom | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203115 | Solution for KI#2: Per-PDU session awareness of URSP enforcement. |
pCR revision of S2-2202467 |
Lenovo | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203116 | Solution for KI#2 5GC awareness of URSP enforcement. |
pCR revision of S2-2202549 |
OPPO | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203117 | Solution for 5GC awareness of URSP enforcement. |
pCR revision of S2-2202556 |
Huawei, HiSilicon | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203118 | EUEPO solution for Key Issue 2. |
pCR revision of S2-2202699 |
China Telecom | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203119 | KI#2, New Sol: 5GC awareness of URSP rule evaluation and verification of network slice usage. |
pCR revision of S2-2202762 |
Orange | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203120 | KI#2 new Solution X: UE URSP enforcement validation by the network. |
pCR revision of S2-2202860 |
NEC | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203121 | New Solution to KI#3: URSPs into PCO for EPC. |
pCR revision of S2-2201974 |
Ericsson | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203122 | KI#3, New Solution: Provisioning consistent URSP to UE across 5GS and EPS for Single PCF Deployment |
pCR revision of S2-2202415 |
Intel | 23.700-33 0.1.0 | FS_5G_ProSe_Ph2 | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203123 | Solution: KI#3 Provision consistent URSP to UE across 5GS and EPS |
pCR revision of S2-2202744 |
NEC | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203124 | Solution for KI#3: Provision consistent URSP to UE across 5GS and EPS. |
pCR revision of S2-2202808 |
Samsung | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203125 | New Solution on KI#6: Traffic Category with existing mechanism. |
pCR revision of S2-2202060 |
Huawei, HiSilicon | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203126 | Solution for KI#4: UE provisioned/configured with a mapping of application traffic to traffic categories. |
pCR revision of S2-2202444 |
Lenovo | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203127 | 23.700-85: Solution for KI#4; Support standardized and operator-specific traffic categories in URSP. |
pCR revision of S2-2202453 |
Nokia, Nokia Shanghai Bell | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203128 | Solution for the KI#4: Introduction of Traffic Category into URSP rules. |
pCR revision of S2-2202474 |
Vivo | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203129 | 23.700-85: Solution for KI #4 Traffic categories based on 5G QoS characteristics. |
pCR revision of S2-2202940 |
Apple | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203594 | TR 23.700-85: KI#1, new solution proposal on URSP in VPLMN. |
pCR revision of S2-2202771 |
Qualcomm Incorporated, Intel | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203609 | Solution for KI#1: VPLMN influencing URSP rules creation in an HPLMN. |
pCR revision of S2-2202469 |
Lenovo | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
S2-2203610 | 23.700-85: Solution for KI#1; URSP provisioning when a UE is not served by its home operator. |
pCR revision of S2-2202454 |
Nokia, Nokia Shanghai Bell | 23.700-85 0.1.0 | FS_eUEPO | Rel-18 |
S2-150-e AI: 9.22 |
approved | [WTS] [JSN] |
51 documents (0.31955194473267 seconds)