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-150734 | LS from SA WG1: Reply LS on end-to-end WebRTC-IMS security |
LS in source LS: S1-150212 LS To: SA WG3 |
SA WG1 | Rel-13 |
S2-108 AI: 6.9 |
noted | [WTS] [JSN] | ||
S2-150737 | LS from SA WG3: LS on end-to-end WebRTC-IMS security |
LS in source LS: S3-151162 LS To: SA WG1 |
SA WG3 | Rel-13 |
S2-108 AI: 6.9 |
noted | [WTS] [JSN] | ||
S2-150747 | Enhancements to Solution 2 |
pCR revised to S2-151153 |
Ericsson | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] |
S2-150748 | Evaluation Criteria For Solution 2 |
pCR revised to S2-151169 |
Ericsson | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] |
S2-150749 | High Level Solution 2 Description | pCR | Ericsson | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
available | [WTS] [JSN] |
S2-150885 | Reference update | pCR | China Mobile | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
approved | [WTS] [JSN] |
S2-150908 | Further description on avoiding SRVCC trigger | pCR | Samsung | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
noted | [WTS] [JSN] |
S2-150956 | High Level Description Solution 3 | pCR | Nokia Networks, Huawei | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
available | [WTS] [JSN] |
S2-150957 | Support of Procedures requiring the IMSI | pCR | Nokia Networks | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
available | [WTS] [JSN] |
S2-150958 | Potential reduction of scope of the WID | other | Nokia Networks | Rel-13 |
S2-108 AI: 6.9 |
noted | [WTS] [JSN] | ||
S2-150959 | Resiliency Aspects for Solution 3 | pCR | Nokia Networks | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
approved | [WTS] [JSN] |
S2-150960 | Evaluation of Solution 3 +5 |
pCR revised to S2-151170 |
Nokia Networks, Huawei | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] |
S2-150963 | Evaluation Comparison of Solutions in Section 5 |
pCR revised to S2-151171 |
T-Mobile USA | 23.706 | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] | |
S2-150970 | Clarification on Solution 1 in § 5.2: forking | pCR | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
approved | [WTS] [JSN] |
S2-150971 | Clarification on Solution 1 in § 5.2: routing of terminating sessions | pCR | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
approved | [WTS] [JSN] |
S2-150972 | Clarification on Solution 1 in § 5.2: scalability and service resiliency |
pCR revised to S2-151152 |
Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] |
S2-150973 | Evaluation Criteria For Solution 5.2.1 |
pCR revised to S2-151168 |
Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] |
S2-150974 | Reduction of eWebRTCi scope |
pCR revised to S2-151151 |
Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] |
S2-151007 | Discussion on the how to avoid SRVCC |
pCR revised to S2-151184 |
ZTE | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] |
S2-151008 | Clarification to the solution 4 |
pCR revised to S2-151167 |
ZTE | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] |
S2-151009 | Way forward on the key issue - Architectural aspects for minimizing the need for bearer level protocol conversion |
pCR revised to S2-151185 |
ZTE | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] |
S2-151090 | Avoiding SRVCC in case of webRTC calls | pCR | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | 23.706 | eWebRTCi |
S2-108 AI: 6.9 |
available | [WTS] [JSN] | |
S2-151151 | Reduction of eWebRTCi scope |
pCR revision of S2-150974 |
Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | 23.706 | eWebRTCi |
S2-108 AI: 6.9 |
approved | [WTS] [JSN] | |
S2-151152 | Clarification on Solution 1 in 5.2: scalability and service resiliency |
pCR revision of S2-150972 |
Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | 23.706 | eWebRTCi |
S2-108 AI: 6.9 |
approved | [WTS] [JSN] | |
S2-151153 | Enhancements to Solution 2 |
pCR revision of S2-150747 |
Ericsson | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
approved | [WTS] [JSN] |
S2-151167 | Clarification to the solution 4 |
pCR revision of S2-151008 |
ZTE | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
approved | [WTS] [JSN] |
S2-151168 | Evaluation Criteria For Solution 5.2.1 |
pCR revision of S2-150973 revised to S2-151195 |
Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | 23.706 | eWebRTCi |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] | |
S2-151169 | Evaluation Criteria For Solution 2 |
pCR revision of S2-150748 revised to S2-151197 |
Ericsson | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] |
S2-151170 | Evaluation of Solution 3 +5 |
pCR revision of S2-150960 revised to S2-151198 |
Nokia Networks, Huawei | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] |
S2-151171 | Evaluation Comparison of Solutions in Section 5 |
pCR revision of S2-150963 revised to S2-151196 |
T-Mobile USA | 23.706 | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] | |
S2-151184 | Discussion on the how to avoid SRVCC |
pCR revision of S2-151007 revised to S2-151385 |
ZTE | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] |
S2-151185 | Way forward on the key issue - Architectural aspects for minimizing the need for bearer level protocol conversion |
pCR revision of S2-151009 revised to S2-151386 |
ZTE | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] |
S2-151186 | [DRAFT] Request confirmation on OMR-based solution for end-to-end transparent media in eWebRTCi |
LS out LS To: SA3-LI revised to S2-151387 |
SA WG2 | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] | ||
S2-151187 | Conclusions for key issue 1 | pCR | Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
approved | [WTS] [JSN] |
S2-151195 | Evaluation Criteria For Solution 5.2.1 |
pCR revision of S2-151168 |
Alcatel-Lucent, Alcatel-Lucent ShangHai Bell | 23.706 | eWebRTCi |
S2-108 AI: 6.9 |
noted | [WTS] [JSN] | |
S2-151196 | Evaluation Comparison of Solutions in Section 5 |
pCR revision of S2-151171 |
T-Mobile USA | 23.706 | Rel-13 |
S2-108 AI: 6.9 |
approved | [WTS] [JSN] | |
S2-151197 | Evaluation Criteria For Solution 2 |
pCR revision of S2-151169 |
Ericsson | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
noted | [WTS] [JSN] |
S2-151198 | Evaluation of Solution 3 +5 |
pCR revision of S2-151170 |
Nokia Networks, Huawei | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
noted | [WTS] [JSN] |
S2-151385 | Discussion on the how to avoid SRVCC |
pCR revision of S2-151184 revised to S2-151428 |
ZTE | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
revised | [WTS] [JSN] |
S2-151386 | Way forward on the key issue - Architectural aspects for minimizing the need for bearer level protocol conversion |
pCR revision of S2-151185 |
ZTE | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
approved | [WTS] [JSN] |
S2-151387 | LS on OMR-based solution for end-to-end transparent media in eWebRTCi |
LS out LS To: SA WG3-LI revision of S2-151186 |
SA WG2 | Rel-13 |
S2-108 AI: 6.9 |
approved | [WTS] [JSN] | ||
S2-151428 | Discussion on the how to avoid SRVCC |
pCR revision of S2-151385 |
ZTE | 23.706 | eWebRTCi | Rel-13 |
S2-108 AI: 6.9 |
approved | [WTS] [JSN] |
42 documents (0.37945699691772 seconds)