The 5G Standard

3GPP TDocs (written contributions) at meeting

Meeting: N5-15 - 2001-11-26 to 2001-11-30, Cancun

meeting id: N5-15 (click id for more info on this meeting)

Click on the Tdoc to open its file.

TDoc Title Source Remarks
N5‑010918 - - -
N5‑011100 - - -
N5‑011102 - - -
N5‑011103 - - -
N5‑011104 - - -
N5‑011107 - - -
N5‑011110 - - -
N5‑011111 - - -
N5‑011112 - - -
N5‑011113 - - -
N5‑011114 - - -
N5‑011115 - - -
N5‑011116 - - -
N5‑011117 - - -
N5‑011118 - - -
N5‑011119 - - -
N5‑011120 - - -
N5‑011123 - - -
N5‑011124 - - -
N5‑011125 - - -
N5‑011126 - - -
N5‑011130 - - -
N5‑011131 - - -
N5‑011132 - - -
N5‑011133 - - -
N5‑011135 - - -
N5‑011136 Removal of time based charging property - -
N5‑011137 - - -
N5‑011138 Correction of description of sendInfoRes() - -
N5‑011139 - - -
N5‑011140 Correction to handling of deassign on related object - -
N5‑011141 - - -
N5‑011142 - - -
N5‑011143 - - -
N5‑011144 - - -
N5‑011145 Make attachMedia() and detachMedia() asynchronous - -
N5‑011146 Correction of treatment datatype in superviseReq on call leg - -
N5‑011147 Correction of method getLastRedirectionAddress - -
N5‑011152 - - -
N5‑011153 - - -
N5‑011154 - - -
N5‑011155 - - -
N5‑011156 - - -
N5‑011157 - - -
N5‑011158 - - -
N5‑011159 Liaison Statement on the Support of Up to Date Encryption Algorithms in the OSA Framework N5 -
N5‑011160 LS reply on Confirmation of OSA Support for VASP MMS Connectivity N5 -
N5‑011161 LS reply to request clarification on SA1's CR stating that OSA APIs do not require Service Capability Features to be 3GPP standardized entities N5 -
N5‑011167 - - -
N5‑011168 - - -
N5‑011169 - - -
N5‑011170 - - -
N5‑011171 - - -
N5‑011172 Liaison Statement on Retrieval of Network Capabilities Requirement N5 -
N5‑011192 - - -
N5‑011197 - - -
N5‑011198 - - -
N5‑011199 - - -
N5‑011200 - - -
N5‑011201 - - -
N5‑011202 - - -
N5‑011203 - - -
N5‑011206 - - -
N5‑011207 - - -
N5‑011208 - - -
N5‑011211 - - -
N5‑011226 - - -
N5‑011227 - - -
N5‑011228 - - -
N5‑011229 - - -
N5‑011230 - - -
N5‑011231 - - -
N5‑011232 - - -
N5‑011233 - - -
N5‑011234 - - -
N5‑011235 - - -
N5‑011236 - - -
N5‑011237 - - -
N5‑011238 - - -
N5‑011239 - - -
N5‑011240 Correction to Common Data (CD) - -
N5‑011241 Correctionto Framework (FW) - -
N5‑011242 - - -
N5‑011243 Correction to Exceptions Raised in UI - -
N5‑011244 Corrections and alignment additions to the Data Session Control SCF - -
N5‑011245 - - -
N5‑011246 Corrections to Call Control Data Types - -
N5‑011247 - - -
N5‑011248 - - -
N5‑011249 - - -
N5‑011250 Correction to Call Control (CC) - -
N5‑011251 Correction of references to 3GPP specifications - -
N5‑011252 - - -
N5‑011253 - - -
N5‑011254 - - -
N5‑011255 - - -
N5‑011256 - - -
N5‑011257 - - -
N5‑011258 Amend the Generic Call Control introductory part - -
N5‑011259 - - -
N5‑011260 Correction in TpCallEventType - -
N5‑011261 - - -
N5‑011262 Addition of missing description of RouteErr() - -
N5‑011263 - - -
N5‑011264 - - -
N5‑011265 - - -
N5‑011266 - - -
N5‑011267 - - -
N5‑011268 Misleading description of createAndRouteCallLegErr() - -
N5‑011269 Correction to values of TpAddressPlan - -
N5‑011270 Correction to values of TpCallNotificationType, TpCallLoadControlMechanismType - -
N5‑011271 Correction to values of TpUIInfoType - -
N5‑011272 Correction to callback interface reference in method IpTriggeredUserLocation.triggeredLocationReportingStartReq - -
N5‑011273 - - -
N5‑011274 - - -
N5‑011300 - - -

page generated from database: 2024-04-13 13:51:47

Get news. Get knowledge. Get involved
Get news.
Get knowledge.
Get involved.
Image
The 5G Standard
3GPP General Enquiries:
info@3gpp.org 


Connect:

Quick Links