A Global
Partnership

The Mobile
Broadband
Standard

3GPP TDocs (written contributions) at meeting

Meeting: N5-26 - 2004-02-16 to 2004-02-20, Atlanta

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

Click on the Tdoc to open its file.

TDoc Title Source Remarks
N5_26_Doc - - -
N5‑020000 Draft Agenda JWG Chair -
N5‑020001 Document Allocation JWG Chair -
N5‑020002 report_Monday JWG Chair -
N5‑020003 report_Tuesday JWG Chair -
N5‑020004 report_Wednesday JWG Chair -
N5‑020005 report_Thursday JWG Chair -
N5‑020006 report_Friday JWG Chair -
N5‑020007 Draft Report of CN5#25 JWG Chair -
N5‑020008 Report of CN5#25 Joint-API-group -
N5‑020009 Report of last 3GPP CN meeting MCC -
N5‑020010 Report of last 3GPP SA meeting MCC -
N5‑020011 CN5 Report to CN#21 plenary, Sep 2003 (NP-030437) CN5 Chair -
N5‑020012 IETF status report & 3GPP IETF Dependencies and Priorities (SP-030504) TSG CN Chairman -
N5‑020013 Presentation of 3GPP Work Plan status at the end of SA#21 (09/2003) MCC -
N5‑020014 3GPP Work Plan filtered on OSA issues (CN5, SA1/2 etc.) MCC -
N5‑020015 CN5 (OSA Stage 3) Work Item Description(s) - WID(s) CN#21 (NP-030353) -
N5‑020016 Full 3GPP meeting calendar including workshops MCC -
N5‑020017 SA_SAx_CN_CNx meeting calendar MCC -
N5‑040000 - - imported from 3GU
N5‑040001 - - imported from 3GU
N5‑040002 - - imported from 3GU
N5‑040003 - - imported from 3GU
N5‑040004 - - imported from 3GU
N5‑040005 - - imported from 3GU
N5‑040006 report_Friday JWG Chair -
N5‑040007 - - imported from 3GU
N5‑040008 Approved Report of this CN5 meeting JWG -
N5‑040009 - - imported from 3GU
N5‑040010 - - imported from 3GU
N5‑040011 - - imported from 3GU
N5‑040012 - - imported from 3GU
N5‑040013 - - imported from 3GU
N5‑040014 - - imported from 3GU
N5‑040015 - - imported from 3GU
N5‑040016 - - imported from 3GU
N5‑040017 - - imported from 3GU
N5‑040018 - - imported from 3GU
N5‑040019 - - imported from 3GU
N5‑040020 - - imported from 3GU
N5‑040021 - - imported from 3GU
N5‑040022 - - imported from 3GU
N5‑040023 - - imported from 3GU
N5‑040024 - - imported from 3GU
N5‑040025 - - imported from 3GU
N5‑040026 LS on Clarifications concerning OSA High Availability discussion N5 imported from 3GU
N5‑040027 - - imported from 3GU
N5‑040028 - - imported from 3GU
N5‑040029 - - imported from 3GU
N5‑040030 - - imported from 3GU
N5‑040031 - - imported from 3GU
N5‑040032 - - imported from 3GU
N5‑040033 - - imported from 3GU
N5‑040034 - - imported from 3GU
N5‑040035 - - imported from 3GU
N5‑040036 - - imported from 3GU
N5‑040037 - - imported from 3GU
N5‑040038 - - imported from 3GU
N5‑040039 - - imported from 3GU
N5‑040040 - - imported from 3GU
N5‑040041 - - imported from 3GU
N5‑040042 - - imported from 3GU
N5‑040043 - - imported from 3GU
N5‑040044 - - imported from 3GU
N5‑040045 Correct Java Rulebook to support API design pattern introduced by PAM SCS - imported from 3GU
N5‑040046 - - imported from 3GU
N5‑040047 - - imported from 3GU
N5‑040048 - - imported from 3GU
N5‑040049 - - imported from 3GU
N5‑040050 - - imported from 3GU
N5‑040051 - - imported from 3GU
N5‑040052 - - imported from 3GU
N5‑040053 - - imported from 3GU
N5‑040054 Account Management missing needed features - imported from 3GU
N5‑040055 Correct Java Rulebook to introduce UI service naming rule - imported from 3GU
N5‑040056 Add ability to identify when a client app/service contract/service profile is being used - Align between ETSI/Parlay and 3GPP - imported from 3GU
N5‑040057 Add ability to identify when a client app/service contract/service profile is being used - Align between ETSI/Parlay and 3GPP - imported from 3GU
N5‑040058 Correct alignment between ETSI/Parlay version of OSA and the 3GPP OSA, by clarifying erroneous field in TpServiceProfileDescription - imported from 3GU
N5‑040059 Correct alignment between ETSI/Parlay version of OSA and the 3GPP OSA, by clarifying erroneous field in TpServiceProfileDescription - imported from 3GU
N5‑040060 Introduce a ServiceID field to TpServiceProfileDescription - imported from 3GU
N5‑040061 Introduce a ServiceID field to TpServiceProfileDescription - imported from 3GU
N5‑040062 Add events to allow an entop to identify when a client app/service contract/service profile is being used - imported from 3GU
N5‑040063 Deadline for contributions is 5 working days before the meeting starts. Consideration of later contributions cannot be guaranteed MCC -
N5‑040064 - - imported from 3GU
N5‑040065 - - imported from 3GU
N5‑040066 Correct alignment between ETSI/Parlay version of OSA and the 3GPP OSA, by clarifying erroneous field in TpServiceProfileDescription - imported from 3GU
N5‑040067 - - imported from 3GU
N5‑040068 - - imported from 3GU
N5‑040069 - - imported from 3GU
N5‑040070 - - imported from 3GU
N5‑040071 - - imported from 3GU
N5‑040072 - - imported from 3GU
N5‑040073 - - imported from 3GU
N5‑040074 - - imported from 3GU
N5‑040075 - - imported from 3GU
N5‑040076 - - imported from 3GU
N5‑040077 - - imported from 3GU
N5‑040078 Correction of Digital Signature with NO signing algorithm - imported from 3GU
N5‑040079 - - imported from 3GU
N5‑040080 Add missing Supervise Report value to support QoS parameter change reports - imported from 3GU
N5‑040081 - - imported from 3GU
N5‑040082 - - imported from 3GU
N5‑040083 - - imported from 3GU
N5‑040084 - - imported from 3GU
N5‑040085 - - imported from 3GU
N5‑040086 - - imported from 3GU
N5‑040087 - - imported from 3GU
N5‑040088 - - imported from 3GU
N5‑040089 - - imported from 3GU
N5‑040090 Do NOT reserve Tdoc# from this point on & bring the contribution to the meeting and contact MCC MCC -
N5‑040091 - - -
N5‑040092 - - -
N5‑040093 - - -
N5‑040094 Remove P_FIXED, TpFixed - -
N5‑040095 - - -
N5‑040096 - - -
N5‑040097 - - -
N5‑040098 Correction of continueProcessing method for Generic Call Control Service (GCCS) - -
N5‑040099 Correction of continueProcessing method for Generic Call Control Service (GCCS) - -
N5‑040101 Correction of continueProcessing method for Generic Call Control Service (GCCS) - -
N5‑040102 - - -
N5‑040103 - - -
N5‑040104 - - -
N5‑040105 - - -
N5‑040106 Reply LS to SA2 on Request for clarification on the scope of the Ut interface towards the OSA-SCS N5 -
N5‑040107 LS reply on "Extended MM7 and Messaging Integration Broker" N5 -
N5‑040108 - - -
N5‑040109 - - -
N5‑040110 Correction of introduction of PAM Provisioning Interfaces - -
N5‑040111 - - -
N5‑040112 Correction of description in superviseRes - Align with Rel-5 - -
N5‑040113 Correction of description in superviseVolumeRes - Align with Rel-5 - -
N5‑040114 Correction of method references in MMCC - Align with Rel-5 - -
N5‑040115 - - -
N5‑040116 - - -
N5‑040117 Correct List vs Set semantics in User Interaction - -
N5‑040118 Correct alignment between ETSI/Parlay OSA and the 3GPP OSA by adding user binding data types - -
N5‑040119 Correct Java Rulebook to support API design pattern introduced by PAM SCS - -
N5‑040120 - - -
N5‑040121 - - -
N5‑040122 - - -
N5‑040123 LS on Clarifications concerning OSA High Availability discussion N5 -

page generated from database: 2020-10-01 08:07:30