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
S3-240208 Elaborated LS reply to S3-234350 on Roaming Hub requirements as applicable to the Modified PRINS solution LS in

LS reply in S3-240887, S3-240887

GSMA S3-115

AI: 4.1.14

replied to [WTS] [JSN]
S3-240209 Elaborated LS reply to S3-234350 on IPX Service Hub requirements as applicable to the Modified PRINS solution LS in

LS reply in S3-240888, S3-240888

GSMA S3-115

AI: 4.1.14

replied to [WTS] [JSN]
S3-240210 LS to 3GPP CT4 on in-path and in-query parameters LS in GSMA S3-115

AI: 4.1.14

noted [WTS] [JSN]
S3-240211 LS on nested JSON structures and reply to LS S3-235067 LS in GSMA S3-115

AI: 4.1.14

noted [WTS] [JSN]
S3-240212 LS to 3GPP on data plane control by roaming hubs LS in GSMA S3-115

AI: 4.1.14

noted [WTS] [JSN]
S3-240213 LS to 3GPP on PRINS security profiles LS in GSMA S3-115

AI: 4.1.14

noted [WTS] [JSN]
S3-240221 Reply LS on N32 Race conditions and recovery LS in C4-235586 S3-115

AI: 4.1.14

noted [WTS] [JSN]
S3-240256 LS reply to S3-233786 and S3-234296 on the introduction of the domain ""ipxnetwork.org"" and clarifications of the Outsourced SEPP and Hosted SEPP deployment scenarios LS in

LS reply in S3-240886, S3-240886

GSMA S3-115

AI: 4.1.14

replied to [WTS] [JSN]
S3-240288 LS reply to S3-240256 on the introduction of the domain ""ipxnetwork.org"" LS out

LS is reply to S3-240256

LS To: GSMA 5GMRR

revised to S3-240886

BSI (DE) S3-115

AI: 4.1.14

revised [WTS] [JSN]
S3-240313 AI from SA: Mapping modified PRINS CR to previous releases discussion SA3 Chair S3-115

AI: 4.1.14

endorsed [WTS] [JSN]
S3-240544 Discussion on how to back track the 5G roaming related changes to earlier releases discussion Huawei, HiSilicon, Vodafone S3-115

AI: 4.1.14

endorsed [WTS] [JSN]
S3-240545 Living document for backtracking 5G Roaming changes - Modification of PRINS to enable Roaming Hubs draftCR

revised to S3-240882

Huawei, HiSilicon, Vodafone TEI16 Rel-16 S3-115

AI: 4.1.14

revised [WTS] [JSN]
S3-240546 Placeholder for collecting new changes related to the 5G roaming WID other

revised to S3-240883

Huawei, HiSilicon, Vodafone Rel-16 S3-115

AI: 4.1.14

revised [WTS] [JSN]
S3-240550 Clarification on the usage of N32-f context ID and N32-f message ID CR

revised to S3-241036

Huawei, HiSilicon 33.501 18.4.0 CR#1924 catF Roaming5G Rel-18 S3-115

AI: 4.1.14

revised [WTS] [JSN]
S3-240551 Modification on the definition of Roaming Hub CR

revised to S3-240891

Huawei, HiSilicon 33.501 18.4.0 CR#1925 catF Roaming5G Rel-18 S3-115

AI: 4.1.14

revised [WTS] [JSN]
S3-240555 Reply LS on Roaming Hub requirements as applicable to the Modified PRINS solution LS out

LS To: SA

revised to S3-240887

Huawei, HiSilicon Rel-19 S3-115

AI: 4.1.14

revised [WTS] [JSN]
S3-240556 Reply LS on IPX Service Hub requirements as applicable to the Modified PRINS solution LS out

LS To: SA

revised to S3-240888

Huawei, HiSilicon Rel-19 S3-115

AI: 4.1.14

revised [WTS] [JSN]
S3-240737 Security profiles for PRINS CR

revision of S3-234865

revised to S3-240889

Nokia, Nokia Shanghai Bell 33.501 18.4.0 CR#18891 catF Roaming5G Rel-18 S3-115

AI: 4.1.14

revised [WTS] [JSN]
S3-240815 Alignments on terminology for roaming intermediaries CR

revised to S3-240890

Nokia, Nokia Shanghai Bell 33.501 18.4.0 CR#1964 catF Roaming5G Rel-18 S3-115

AI: 4.1.14

revised [WTS] [JSN]
S3-240882 Living document for backtracking 5G Roaming changes - Modification of PRINS to enable Roaming Hubs draftCR

revision of S3-240545

Huawei, HiSilicon, Vodafone TEI16 Rel-16 S3-115

AI: 4.1.14

approved [WTS] [JSN]
S3-240883 Placeholder for collecting new changes related to the 5G roaming WID other

revision of S3-240546

Huawei, HiSilicon, Vodafone Rel-16 S3-115

AI: 4.1.14

approved [WTS] [JSN]
S3-240884 Backtracking 5G Roaming changes - Modification of PRINS to enable Roaming Hubs CR Huawei, HiSilicon, Vodafone, Deutsche Telekom 33.501 16.17.0 CR#1968 catB TEI16 Rel-16 S3-115

AI: 4.1.14

endorsed [WTS] [JSN]
S3-240885 Backtracking 5G roaming changes CR Huawei 33.501 17.12.0 CR#1969 catB TEI17 Rel-17 S3-115

AI: 4.1.14

endorsed [WTS] [JSN]
S3-240886 LS reply to S3-240256 on the introduction of the domain ""ipxnetwork.org"" LS out

LS is reply to S3-240256

LS To: GSMA 5GMRR

revision of S3-240288

BSI (DE) S3-115

AI: 4.1.14

approved [WTS] [JSN]
S3-240887 Reply LS on Roaming Hub requirements as applicable to the Modified PRINS solution LS out

LS is reply to S3-240208

LS To: SA

revision of S3-240555

Huawei, HiSilicon Rel-19 S3-115

AI: 4.1.14

approved [WTS] [JSN]
S3-240888 Reply LS on IPX Service Hub requirements as applicable to the Modified PRINS solution LS out

LS is reply to S3-240209

LS To: SA

revision of S3-240556

Huawei, HiSilicon Rel-19 S3-115

AI: 4.1.14

approved [WTS] [JSN]
S3-240889 Security profiles for PRINS CR

revision of S3-240737

Nokia, Nokia Shanghai Bell 33.501 18.4.0 CR#18892 catF Roaming5G Rel-18 S3-115

AI: 4.1.14

agreed [WTS] [JSN]
S3-240890 Alignments on terminology for roaming intermediaries CR

revision of S3-240815

Nokia, Nokia Shanghai Bell 33.501 18.4.0 CR#19641 catF Roaming5G Rel-18 S3-115

AI: 4.1.14

agreed [WTS] [JSN]
S3-240891 Modification on the definition of Roaming Hub CR

revision of S3-240551

Huawei, HiSilicon 33.501 18.4.0 CR#19251 catF Roaming5G Rel-18 S3-115

AI: 4.1.14

agreed [WTS] [JSN]
S3-241036 Clarification on the usage of N32-f context ID and N32-f message ID CR

revision of S3-240550

Huawei, HiSilicon 33.501 18.4.0 CR#19241 catF Roaming5G Rel-18 S3-115

AI: 4.1.14

agreed [WTS] [JSN]
S3-241037 LS on backtracking 5G roaming changes LS out

LS To: SA

Huawei S3-115

AI: 4.1.14

approved [WTS] [JSN]

31 documents (0.31190299987793 seconds)