3GPP TDocs (written contributions) at meeting
Meeting: S1-61b - 2013-04-08 to 2013-04-11, San Diego
meeting id: S1-61b (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
S1‑132002 | Final Schedule and Agenda with document allocation for SA1#61bis | WG Chairman | - |
S1‑132078 | Clarify that there is a potential interaction with the user or the application | Huawei | - |
S1‑132080 | Clarification for communication paths in the presence of ProSe | LG Electronics, Inc. | - |
S1‑132093 | - | - | - |
S1‑132094 | - | - | - |
S1‑132095 | - | - | - |
S1‑132096 | - | - | - |
S1‑132097 | - | - | - |
S1‑132098 | - | - | - |
S1‑132099 | - | - | - |
S1‑132100 | - | - | - |
S1‑132101 | - | - | - |
S1‑132102 | - | - | - |
S1‑132103 | - | - | - |
S1‑132104 | - | - | - |
S1‑132112 | - | - | - |
S1‑132113 | - | - | - |
S1‑132114 | - | - | - |
S1‑132115 | - | - | - |
S1‑132116 | - | - | - |
S1‑132117 | - | - | - |
S1‑132118 | - | - | - |
S1‑132119 | - | - | - |
S1‑132120 | - | - | - |
S1‑132121 | - | - | - |
S1‑132122 | - | - | - |
S1‑132123 | - | - | - |
S1‑132124 | - | - | - |
S1‑132125 | - | - | - |
S1‑132126 | - | - | - |
S1‑132127 | - | - | - |
S1‑132128 | - | - | - |
S1‑132129 | - | - | - |
S1‑132130 | - | - | - |
S1‑132131 | - | - | - |
S1‑132132 | - | - | - |
S1‑132133 | - | - | - |
S1‑132134 | Indicate TR is no longer maintained for Rel-12 and add references to normative specifications | Qualcomm | - |
S1‑132135 | - | - | - |
S1‑132136 | - | - | - |
S1‑132137 | - | - | - |
S1‑132138 | - | - | - |
S1‑132139 | - | - | - |
S1‑132140 | Replace WiFi Direct with WLAN direct communications | Intel, LG Electronics | - |
S1‑132141 | - | - | - |
S1‑132142 | - | - | - |
S1‑132143 | - | - | - |
S1‑132144 | - | - | - |
S1‑132145 | Clarify what means off network ProSe | Huawei | - |
S1‑132146 | Deleting a duplicate Public Safety requirement arising from the ProSe Group use case | General Dynamics Broadband UK Limited | - |
S1‑132147 | - | - | - |
S1‑132148 | - | - | - |
S1‑132149 | - | - | - |
S1‑132150 | Addition of an agreed requirement in the Public Safety Specific Requirements for Proximity Services | US Department of Commerce | - |
S1‑132151 | - | - | - |
S1‑132152 | - | - | - |
S1‑132153 | Correcting Service Continuity Requirement in UE-to-Network Relay Scenarios | Intel | - |
S1‑132155 | - | - | - |
S1‑132156 | - | - | - |
S1‑132157 | - | - | - |
S1‑132158 | - | - | - |
S1‑132159 | - | - | - |
S1‑132160 | - | - | - |
S1‑132161 | - | - | - |
S1‑132162 | - | - | - |
S1‑132163 | - | - | - |
S1‑132164 | - | - | - |
S1‑132165 | Infrastructure path corrections | LG Electronics, Inc., Renesas Mobile Europe Ltd | - |
S1‑132166 | Clarification to interactions between ProSe relaying, ProSe Communication and ProSe Group Communication | General Dynamics Broadband UK Limited | - |
S1‑132167 | - | - | - |
S1‑132168 | - | - | - |
S1‑132169 | Clarifying the Requirement on Authorizing ProSe Data Sessions in Public Safety Scenarios | Intel | - |
S1‑132170 | - | - | - |
S1‑132171 | LS on Feedback on Proximity Services and Lawful Interception | S1 | - |
S1‑132172 | - | - | - |
S1‑132173 | - | - | - |
S1‑132174 | - | - | - |
S1‑132175 | - | - | - |
S1‑132176 | - | - | - |
S1‑132177 | - | - | - |
S1‑132178 | - | - | - |
S1‑132179 | - | - | - |
S1‑132180 | - | - | - |
S1‑132181 | - | - | - |
S1‑132182 | - | - | - |
S1‑132183 | - | - | - |
S1‑132184 | - | - | - |
S1‑132185 | - | - | - |
S1‑132186 | - | - | - |
S1‑132187 | - | - | - |
S1‑132188 | - | - | - |
S1‑132189 | - | - | - |
S1‑132190 | - | - | - |
S1‑132191 | - | - | - |
S1‑132192 | - | - | - |
S1‑132193 | Addition of a new requirement in the Public Safety Specific Requirements for Proximity Services for the use of direct radio signals | US Department of Commerce | - |
S1‑132194 | - | - | - |
S1‑132196 | - | - | - |
S1‑132199 | ProSe material agreed at SA1#61bis | S1 | - |
S1‑132200 | - | - | - |
page generated from database: 2024-09-26 11:02:35