3GPP TDocs (written contributions) at meeting
Meeting: N1-08 - 1999-10-25 to 1999-10-29, KOBE
meeting id: N1-08 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
N1‑99B40 | - | - | - |
N1‑99B40 | - | - | - |
N1‑99B41 | Draft Report of TSG SA Meeting #5 - version 0.0.3 | TSG SA Secretary | - |
N1‑99B41 | Draft Report of TSG SA Meeting #5 - version 0.0.3 | TSG SA Secretary | - |
N1‑99B42 | Meeting Report of TSG_CN #5 / SMG3 Plenary | - | - |
N1‑99B42 | Meeting Report of TSG_CN #5 / SMG3 Plenary | - | - |
N1‑99B43 | - | - | - |
N1‑99B43 | - | - | - |
N1‑99B44 | - | - | - |
N1‑99B44 | - | - | - |
N1‑99B45 | Rapporteurs for TSGN WG1 specifications | MCC | - |
N1‑99B45 | Rapporteurs for TSGN WG1 specifications | MCC | - |
N1‑99B46 | Specifications within TSG_CN | Chairman TSG_CN | - |
N1‑99B46 | Specifications within TSG_CN | Chairman TSG_CN | - |
N1‑99B47 | DRAFT - Working Item List for TSG_CN | TSG_CN | - |
N1‑99B47 | DRAFT - Working Item List for TSG_CN | TSG_CN | - |
N1‑99B48 | Response liaison on RAB requirements for CS data and architecture for CS data services | 3GPP TSG SA WG2 | - |
N1‑99B48 | Response liaison on RAB requirements for CS data and architecture for CS data services | 3GPP TSG SA WG2 | - |
N1‑99B49 | - | - | - |
N1‑99B49 | - | - | - |
N1‑99B50 | Clarification of DRX | Ericsson | - |
N1‑99B50 | Clarification of DRX | Ericsson | - |
N1‑99B51 | Liaison Statement on Issues with Multiple PDP Contexts | - | - |
N1‑99B51 | Liaison Statement on Issues with Multiple PDP Contexts | - | - |
N1‑99B52 | - | - | - |
N1‑99B52 | - | - | - |
N1‑99B53 | - | - | - |
N1‑99B53 | - | - | - |
N1‑99B54 | LS on management of TLLI during P-TMSI reallocation procedure | - | - |
N1‑99B54 | LS on management of TLLI during P-TMSI reallocation procedure | - | - |
N1‑99B55 | - | - | - |
N1‑99B55 | - | - | - |
N1‑99B56 | Answer to Liaison statement on LS on the FLUSH-LL procedure defined in GSM 08.18 for GPRS | - | - |
N1‑99B56 | Answer to Liaison statement on LS on the FLUSH-LL procedure defined in GSM 08.18 for GPRS | - | - |
N1‑99B57 | - | - | - |
N1‑99B57 | - | - | - |
N1‑99B58 | - | - | - |
N1‑99B58 | - | - | - |
N1‑99B59 | - | Vodafone | - |
N1‑99B59 | - | Vodafone | - |
N1‑99B60 | - | N2 | - |
N1‑99B60 | - | N2 | - |
N1‑99B61 | - | 3GPP TSG N2 SWG-A | - |
N1‑99B61 | - | 3GPP TSG N2 SWG-A | - |
N1‑99B62 | - | - | - |
N1‑99B62 | - | - | - |
N1‑99B63 | LS on RAB requirements for CS data | TSG-N3 | - |
N1‑99B63 | LS on RAB requirements for CS data | TSG-N3 | - |
N1‑99B64 | - | - | - |
N1‑99B64 | - | - | - |
N1‑99B65 | response to LS on “Definitions for usage of Multi-mode/system terminals” | - | - |
N1‑99B65 | response to LS on “Definitions for usage of Multi-mode/system terminals” | - | - |
N1‑99B66 | Proposed LS on Uplink core network layer 3 message numbering | RAN2 | - |
N1‑99B66 | Proposed LS on Uplink core network layer 3 message numbering | RAN2 | - |
N1‑99B67 | Reply LS on registration areas and on hierarchical tracking concept | RAN2 | - |
N1‑99B67 | Reply LS on registration areas and on hierarchical tracking concept | RAN2 | - |
N1‑99B68 | Proposed liaison statement to SA2, SA3, N1 | Ericsson | - |
N1‑99B68 | Proposed liaison statement to SA2, SA3, N1 | Ericsson | - |
N1‑99B69 | Proposed liaison statement to SA3, CN1, RAN2 | Ericsson | - |
N1‑99B69 | Proposed liaison statement to SA3, CN1, RAN2 | Ericsson | - |
N1‑99B70 | Draft response to "LS on L3 Segmentation" from N1 | Nokia | - |
N1‑99B70 | Draft response to "LS on L3 Segmentation" from N1 | Nokia | - |
N1‑99B71 | - | - | - |
N1‑99B71 | - | - | - |
N1‑99B72 | Multimedia Call Control for UMTS R 99 | - | - |
N1‑99B72 | Multimedia Call Control for UMTS R 99 | - | - |
N1‑99B73 | LS on ciphering of the initial message | TSG SA WG2 | - |
N1‑99B73 | LS on ciphering of the initial message | TSG SA WG2 | - |
N1‑99B74 | Draft Response liaison on RAB requirements for CS data and architecture for CS data services | Ericsson | - |
N1‑99B74 | Draft Response liaison on RAB requirements for CS data and architecture for CS data services | Ericsson | - |
N1‑99B75 | Liaison Statement on UMTS and RAB parameter value ranges and granularity | 3GPP TSG SA WG2 | - |
N1‑99B75 | Liaison Statement on UMTS and RAB parameter value ranges and granularity | 3GPP TSG SA WG2 | - |
N1‑99B76 | - | S2 | - |
N1‑99B76 | - | S2 | - |
N1‑99B77 | - | TSG S2 | - |
N1‑99B77 | - | TSG S2 | - |
N1‑99B78 | - | - | - |
N1‑99B78 | - | - | - |
N1‑99B79 | - | S2 | - |
N1‑99B79 | - | S2 | - |
N1‑99B80 | Liaison statement on the Iu UP protocol framing of NAS user data | 3GPP SA WG2 | - |
N1‑99B80 | Liaison statement on the Iu UP protocol framing of NAS user data | 3GPP SA WG2 | - |
N1‑99B81 | Liaison statement to SMG3 WPA / TSG-CN WG1 in reply to Liaison statement on type approval testing for error case handling (N1-99890) | TSG-T WG1 | - |
N1‑99B81 | Liaison statement to SMG3 WPA / TSG-CN WG1 in reply to Liaison statement on type approval testing for error case handling (N1-99890) | TSG-T WG1 | - |
N1‑99B82 | Response to LS on handover notifications | 3GPP TSG-T2 SWG1 (MExE) | - |
N1‑99B82 | Response to LS on handover notifications | 3GPP TSG-T2 SWG1 (MExE) | - |
N1‑99B83 | 5 or 6 digits IMSI HPLMN | 3GPP TSG-T2 SWG1 (MExE) | - |
N1‑99B83 | 5 or 6 digits IMSI HPLMN | 3GPP TSG-T2 SWG1 (MExE) | - |
N1‑99B84 | - | - | - |
N1‑99B84 | - | - | - |
N1‑99B85 | - | - | - |
N1‑99B85 | - | - | - |
N1‑99B86 | response to LS TSGR2#7(99)D25 on “Definitions for usage of Multi-mode/system terminals” | - | - |
N1‑99B86 | response to LS TSGR2#7(99)D25 on “Definitions for usage of Multi-mode/system terminals” | - | - |
N1‑99B87 | LS on Enhanced User Identity Confidentiality | - | - |
N1‑99B87 | LS on Enhanced User Identity Confidentiality | - | - |
N1‑99B88 | Updating Session Management (SM) for R99 | Nokia | - |
N1‑99B88 | Updating Session Management (SM) for R99 | Nokia | - |
N1‑99B89 | Title | Source | - |
N1‑99B89 | Title | Source | - |
N1‑99b90 | Introduction of Reserved Service Labels in the APN | Ericsson | - |
N1‑99b90 | Introduction of Reserved Service Labels in the APN | Ericsson | - |
N1‑99B91 | Mobile Station Classmark 3 Clarification | Nokia | - |
N1‑99B91 | Mobile Station Classmark 3 Clarification | Nokia | - |
N1‑99B92 | Proposed Broadcast MM System information | Nippon Telecommunications Consulting Co., Ltd. | - |
N1‑99B92 | Proposed Broadcast MM System information | Nippon Telecommunications Consulting Co., Ltd. | - |
N1‑99B93 | Proposed 3rd Generation NAS information | Nippon Telecommunications Consulting CO., LTD. | - |
N1‑99B93 | Proposed 3rd Generation NAS information | Nippon Telecommunications Consulting CO., LTD. | - |
N1‑99B94 | Proposal of Classmark 2 for UMTS | Nippon Telecommunications Consulting CO., LTD. | - |
N1‑99B94 | Proposal of Classmark 2 for UMTS | Nippon Telecommunications Consulting CO., LTD. | - |
N1‑99B95 | Proposal of UMTS/GSM bearer capability | Nippon Telecommunications Consulting, | - |
N1‑99B95 | Proposal of UMTS/GSM bearer capability | Nippon Telecommunications Consulting, | - |
N1‑99B96 | - | - | - |
N1‑99B96 | - | - | - |
N1‑99B97 | - | - | - |
N1‑99B97 | - | - | - |
N1‑99B98 | - | - | - |
N1‑99B98 | - | - | - |
N1‑99C00 | CR to 23.040 for ANSI-136 Teleservices Interoperability | Lucent Technologies | - |
N1‑99C00 | CR to 23.040 for ANSI-136 Teleservices Interoperability | Lucent Technologies | - |
N1‑99C01 | Transaction Identifier Extension | Fujitsu Limited | - |
N1‑99C01 | Transaction Identifier Extension | Fujitsu Limited | - |
N1‑99C02 | Extended Transaction Identifier Reject | Fujitsu Limited | - |
N1‑99C02 | Extended Transaction Identifier Reject | Fujitsu Limited | - |
N1‑99C03 | Realisation of Paging Response Procedure in MM | Fujitsu Limited | - |
N1‑99C03 | Realisation of Paging Response Procedure in MM | Fujitsu Limited | - |
N1‑99C04 | Paging Response as a MM message | Fujitsu | - |
N1‑99C04 | Paging Response as a MM message | Fujitsu | - |
N1‑99C05 | - | - | - |
N1‑99C05 | - | - | - |
N1‑99C07 | Proposed Solution for MS Classmark Open Issues | Fujitsu Limited | - |
N1‑99C07 | Proposed Solution for MS Classmark Open Issues | Fujitsu Limited | - |
N1‑99C08 | Addition of MS Classmark for UMTS Interrogation Procedure in MM | Fujitsu Limited | - |
N1‑99C08 | Addition of MS Classmark for UMTS Interrogation Procedure in MM | Fujitsu Limited | - |
N1‑99C09 | Service Request | Fujitsu | - |
N1‑99C09 | Service Request | Fujitsu | - |
N1‑99C10 | Introduction of Follow-on mechanism for PS | Fujitsu | - |
N1‑99C10 | Introduction of Follow-on mechanism for PS | Fujitsu | - |
N1‑99C11 | Proposed Liaison back to R3 on Security mode control procedure | Fujitsu Limited | - |
N1‑99C11 | Proposed Liaison back to R3 on Security mode control procedure | Fujitsu Limited | - |
N1‑99C12 | - | - | - |
N1‑99C12 | - | - | - |
N1‑99C13 | Addition of further LCS functionality in GSM Release 98 | T1P1.5 | - |
N1‑99C13 | Addition of further LCS functionality in GSM Release 98 | T1P1.5 | - |
N1‑99C14 | LCS CR for GSM 04.71 | - | - |
N1‑99C14 | LCS CR for GSM 04.71 | - | - |
N1‑99C15 | LCS CR for GSM 09.08 | - | - |
N1‑99C15 | LCS CR for GSM 09.08 | - | - |
N1‑99C16 | - | - | - |
N1‑99C16 | - | - | - |
N1‑99C17 | - | - | - |
N1‑99C17 | - | - | - |
N1‑99C18 | Mapping of UMTS BC IE into RAB QoS parameter for speech | Ericsson | - |
N1‑99C18 | Mapping of UMTS BC IE into RAB QoS parameter for speech | Ericsson | - |
N1‑99C19 | Cause 'user busy' in Call Confirmed Message | Ericsson | - |
N1‑99C19 | Cause 'user busy' in Call Confirmed Message | Ericsson | - |
N1‑99C20 | Comments to tdoc N1-99B09 | Ericsson | - |
N1‑99C20 | Comments to tdoc N1-99B09 | Ericsson | - |
N1‑99C21 | Contents of MS CN Classmark | Ericsson | - |
N1‑99C21 | Contents of MS CN Classmark | Ericsson | - |
N1‑99C22 | Feasibility aspects of the Turbo Charger | Alcatel | - |
N1‑99C22 | Feasibility aspects of the Turbo Charger | Alcatel | - |
N1‑99C23 | Proposed Solution for MS Classmark Open Issues | Alcatel | - |
N1‑99C23 | Proposed Solution for MS Classmark Open Issues | Alcatel | - |
N1‑99C24 | Clarification of DTMF Message | - | - |
N1‑99C24 | Clarification of DTMF Message | - | - |
N1‑99C25 | Clarification of DTMF procedure | Vodafone, Siemens | - |
N1‑99C25 | Clarification of DTMF procedure | Vodafone, Siemens | - |
N1‑99C26 | Uplink L3 Message Sequencing | Vodafone | - |
N1‑99C26 | Uplink L3 Message Sequencing | Vodafone | - |
N1‑99C29 | Adaption of MM and GMM messages to incorporate UMTS security parameters | Vodafone | - |
N1‑99C29 | Adaption of MM and GMM messages to incorporate UMTS security parameters | Vodafone | - |
N1‑99C30 | Network Requested PDP Context Activation | Vodafone | - |
N1‑99C30 | Network Requested PDP Context Activation | Vodafone | - |
N1‑99C31 | - | - | - |
N1‑99C31 | - | - | - |
N1‑99C32 | Date:21 October, 1999 | Topic:GPRS | - |
N1‑99C32 | Date:21 October, 1999 | Topic:GPRS | - |
N1‑99C33 | A-bit interpretation contradiction | - | - |
N1‑99C33 | A-bit interpretation contradiction | - | - |
N1‑99C34 | A-bit interpretation contradiction | - | - |
N1‑99C34 | A-bit interpretation contradiction | - | - |
N1‑99C35 | A-bit interpretation contradiction | - | - |
N1‑99C35 | A-bit interpretation contradiction | - | - |
N1‑99C36 | TSGN1 task list to get the GSM/UMTS interworking and MM in UMTS defined as part of | N1 Chairman | - |
N1‑99C36 | TSGN1 task list to get the GSM/UMTS interworking and MM in UMTS defined as part of | N1 Chairman | - |
N1‑99C37 | Title | Source | - |
N1‑99C37 | Title | Source | - |
N1‑99C38 | COMPACT Cell Selection part 1 | SMG2 EDGE WS #111 | - |
N1‑99C38 | COMPACT Cell Selection part 1 | SMG2 EDGE WS #111 | - |
N1‑99C39 | COMPACT Cell Selection part 1 | SMG2 EDGE WS #111 | - |
N1‑99C39 | COMPACT Cell Selection part 1 | SMG2 EDGE WS #111 | - |
N1‑99C40 | COMPACT Cell Selection and Reselection | SMG2 EDGE WS #111 | - |
N1‑99C40 | COMPACT Cell Selection and Reselection | SMG2 EDGE WS #111 | - |
N1‑99C41 | COMPACT Cell Selection Part 1 | UWCC | - |
N1‑99C41 | COMPACT Cell Selection Part 1 | UWCC | - |
N1‑99C42 | COMPACT Cell Selection part 1 | SMG2 EDGE WS #111 | - |
N1‑99C42 | COMPACT Cell Selection part 1 | SMG2 EDGE WS #111 | - |
N1‑99C43 | Title | Source | - |
N1‑99C43 | Title | Source | - |
N1‑99C44 | COMPACT Cell Selection part 2 | EDGE WS #11 *) | - |
N1‑99C44 | COMPACT Cell Selection part 2 | EDGE WS #11 *) | - |
N1‑99C45 | COMPACT Cell Selection part 2 | EDGE WS #11 *) | - |
N1‑99C45 | COMPACT Cell Selection part 2 | EDGE WS #11 *) | - |
N1‑99C46 | COMPACT Cell Selection part 2 | UWCC | - |
N1‑99C46 | COMPACT Cell Selection part 2 | UWCC | - |
N1‑99C47 | Classmark 3 handling at connection establishment | Nokia | - |
N1‑99C47 | Classmark 3 handling at connection establishment | Nokia | - |
N1‑99C48 | Clarification for UE core network classmark contents | Nokia | - |
N1‑99C48 | Clarification for UE core network classmark contents | Nokia | - |
N1‑99C49 | Classmark handling in intersystem handovers | Nokia | - |
N1‑99C49 | Classmark handling in intersystem handovers | Nokia | - |
N1‑99C50 | Draft Technical Report: Turbo-Charger version 0.0.3 | Nortel Networks | - |
N1‑99C50 | Draft Technical Report: Turbo-Charger version 0.0.3 | Nortel Networks | - |
N1‑99C51 | TITLE | MCC | - |
N1‑99C51 | TITLE | MCC | - |
N1‑99C52 | Addition of the Stream Identifier Information Element | NTT COMMUNICATIONWARE | - |
N1‑99C52 | Addition of the Stream Identifier Information Element | NTT COMMUNICATIONWARE | - |
N1‑99C53 | Outline of the stage2 and stage3 specifications for multicall | NTT COMMUNICATIONWARE | - |
N1‑99C53 | Outline of the stage2 and stage3 specifications for multicall | NTT COMMUNICATIONWARE | - |
N1‑99C54 | working schedule of UMTS adaptation of GMM | NTT DoCoMo, NTT Communicationware | - |
N1‑99C54 | working schedule of UMTS adaptation of GMM | NTT DoCoMo, NTT Communicationware | - |
N1‑99C55 | - | - | - |
N1‑99C55 | - | - | - |
N1‑99C56 | Using MM sublayer for PS-SMS message transfer | NTT Communicationware | - |
N1‑99C56 | Using MM sublayer for PS-SMS message transfer | NTT Communicationware | - |
N1‑99C57 | Using MM sublayer for PS-SMS message transfer | NTT Communicationware | - |
N1‑99C57 | Using MM sublayer for PS-SMS message transfer | NTT Communicationware | - |
N1‑99C58 | Title | Source | - |
N1‑99C58 | Title | Source | - |
N1‑99C59 | LLC SAPI handling | Fujitsu | - |
N1‑99C59 | LLC SAPI handling | Fujitsu | - |
N1‑99C60 | - | - | - |
N1‑99C60 | - | - | - |
N1‑99C61 | - | - | - |
N1‑99C61 | - | - | - |
N1‑99C62 | - | - | - |
N1‑99C62 | - | - | - |
N1‑99C63 | - | - | - |
N1‑99C63 | - | - | - |
N1‑99C64 | - | - | - |
N1‑99C64 | - | - | - |
N1‑99C65 | - | - | - |
N1‑99C65 | - | - | - |
N1‑99C66 | Liaison Statement on Issues with Multiple PDP Contexts | - | - |
N1‑99C66 | Liaison Statement on Issues with Multiple PDP Contexts | - | - |
N1‑99C67 | LS to S1 on 3G Services | TSG-CN3 | - |
N1‑99C67 | LS to S1 on 3G Services | TSG-CN3 | - |
N1‑99C68 | LS on Iu UP Protocol Framing of NAS User Data | TSG-CN3 | - |
N1‑99C68 | LS on Iu UP Protocol Framing of NAS User Data | TSG-CN3 | - |
N1‑99C69 | Response to LS on Service/Baseline Implementation Capabilities | - | - |
N1‑99C69 | Response to LS on Service/Baseline Implementation Capabilities | - | - |
N1‑99C70 | Answer to LS on SAT/MExE <-> CAMEL Interworking / Traceability | SMG9 | - |
N1‑99C70 | Answer to LS on SAT/MExE <-> CAMEL Interworking / Traceability | SMG9 | - |
N1‑99C71 | - | - | - |
N1‑99C71 | - | - | - |
N1‑99C72 | MS and GSN-initiated PDP context modification | Ericsson | - |
N1‑99C72 | MS and GSN-initiated PDP context modification | Ericsson | - |
N1‑99C73 | - | - | - |
N1‑99C73 | - | - | - |
N1‑99C74 | MS and GSN-initiated PDP context modification | Ericsson | - |
N1‑99C74 | MS and GSN-initiated PDP context modification | Ericsson | - |
N1‑99C75 | - | - | - |
N1‑99C75 | - | - | - |
N1‑99C76 | Comments to the Technical Report for Multimedia (N1-99977) | Ericsson, NTT DoCoMo | - |
N1‑99C76 | Comments to the Technical Report for Multimedia (N1-99977) | Ericsson, NTT DoCoMo | - |
N1‑99C77 | Comments to Multimedia Technical Report V 0.0.1 (N1-99B99) | Ericsson | - |
N1‑99C77 | Comments to Multimedia Technical Report V 0.0.1 (N1-99B99) | Ericsson | - |
N1‑99C78 | LS on Information about current status on UE idle mode operation | RAN2 | - |
N1‑99C78 | LS on Information about current status on UE idle mode operation | RAN2 | - |
N1‑99C79 | Title | Source | - |
N1‑99C79 | Title | Source | - |
N1‑99C80 | - | 3GPP TSG N1 | - |
N1‑99C80 | - | 3GPP TSG N1 | - |
N1‑99C81 | (Proposed) Reply to LS on Common Identification for Relocation Co-ordination | 3GPP CN WG1 | - |
N1‑99C81 | (Proposed) Reply to LS on Common Identification for Relocation Co-ordination | 3GPP CN WG1 | - |
N1‑99C82 | - | - | - |
N1‑99C82 | - | - | - |
N1‑99C83 | Proposed response on LS on Information about current status on UE idle mode operation | CN1 | - |
N1‑99C83 | Proposed response on LS on Information about current status on UE idle mode operation | CN1 | - |
N1‑99C84 | Turbo-Charger hooks for R99 | Nortel Networks | - |
N1‑99C84 | Turbo-Charger hooks for R99 | Nortel Networks | - |
N1‑99C85 | Addition of the Stream Identifier Information Element | NTT COMMUNICATIONWARE | - |
N1‑99C85 | Addition of the Stream Identifier Information Element | NTT COMMUNICATIONWARE | - |
N1‑99C86 | Cause 'user busy' in Call Confirmed Message | - | - |
N1‑99C86 | Cause 'user busy' in Call Confirmed Message | - | - |
N1‑99C87 | - | - | - |
N1‑99C87 | - | - | - |
N1‑99C88 | Clarification of DTMF procedure | Vodafone, Siemens | - |
N1‑99C88 | Clarification of DTMF procedure | Vodafone, Siemens | - |
N1‑99C89 | Transaction Identifier Extension | Fujitsu Limited | - |
N1‑99C89 | Transaction Identifier Extension | Fujitsu Limited | - |
N1‑99C90 | Extended Transaction Identifier Reject | Fujitsu Limited | - |
N1‑99C90 | Extended Transaction Identifier Reject | Fujitsu Limited | - |
N1‑99C91 | Clarification of DTMF Message Sequencing | - | - |
N1‑99C91 | Clarification of DTMF Message Sequencing | - | - |
N1‑99C92 | Liaison Statement on LCS CRs and GTSs for GSM Release 98 in SMG#30 | - | - |
N1‑99C92 | Liaison Statement on LCS CRs and GTSs for GSM Release 98 in SMG#30 | - | - |
N1‑99C93 | N1 open questions on QoS | NTT DoCoMo, Nokia, Ericsson, Fujitsu | - |
N1‑99C93 | N1 open questions on QoS | NTT DoCoMo, Nokia, Ericsson, Fujitsu | - |
N1‑99C94 | - | - | - |
N1‑99C94 | - | - | - |
N1‑99C95 | Response LS on Service and Baseline Implementation Capabilities | TSG – N2 | - |
N1‑99C95 | Response LS on Service and Baseline Implementation Capabilities | TSG – N2 | - |
N1‑99C96 | - | - | - |
N1‑99C96 | - | - | - |
N1‑99C97 | Response to LS on 5 or 6 digits IMSI HPLMN | 3GPP TSG - N2 | - |
N1‑99C97 | Response to LS on 5 or 6 digits IMSI HPLMN | 3GPP TSG - N2 | - |
N1‑99C98 | Proposal of UMTS Bearer Capability | - | - |
N1‑99C98 | Proposal of UMTS Bearer Capability | - | - |
N1‑99C99 | Comments to tdoc N1-99B09 | Ericsson | - |
N1‑99C99 | Comments to tdoc N1-99B09 | Ericsson | - |
N1‑99D00 | Network Requested PDP Context Activation | Vodafone | - |
N1‑99D00 | Network Requested PDP Context Activation | Vodafone | - |
N1‑99D01 | Brief report of S1 and N3 meeting for Bearer Modification without pre-notification | NEC | - |
N1‑99D01 | Brief report of S1 and N3 meeting for Bearer Modification without pre-notification | NEC | - |
N1‑99D02 | Necessity of the introduction SI-IE to SM protocol in R99 | NTT COMMUNICATIONWARE | - |
N1‑99D02 | Necessity of the introduction SI-IE to SM protocol in R99 | NTT COMMUNICATIONWARE | - |
N1‑99D03 | Technical Report: Turbo-Charger version 0.1.0 | Nortel Networks | - |
N1‑99D03 | Technical Report: Turbo-Charger version 0.1.0 | Nortel Networks | - |
N1‑99D04 | - | - | - |
N1‑99D04 | - | - | - |
N1‑99D05 | Proposal of Classmark 2 for UMTS | - | - |
N1‑99D05 | Proposal of Classmark 2 for UMTS | - | - |
N1‑99D06 | - | N1 | - |
N1‑99D06 | - | N1 | - |
N1‑99D07 | - | TSG-N1 | - |
N1‑99D07 | - | TSG-N1 | - |
N1‑99D08 | - | - | - |
N1‑99D08 | - | - | - |
N1‑99D09 | Proposed 3rd Generation NAS information | Nippon Telecommunications Consulting CO., LTD. | - |
N1‑99D09 | Proposed 3rd Generation NAS information | Nippon Telecommunications Consulting CO., LTD. | - |
N1‑99D10 | - | - | - |
N1‑99D10 | - | - | - |
N1‑99D11 | Service Request Procedure Description for Review | Fujitsu Limited | - |
N1‑99D11 | Service Request Procedure Description for Review | Fujitsu Limited | - |
N1‑99D12 | Correction of Figure A.2 in Annex A | - | - |
N1‑99D12 | Correction of Figure A.2 in Annex A | - | - |
N1‑99D13 | Correction of Figure A.2 in Annex A | - | - |
N1‑99D13 | Correction of Figure A.2 in Annex A | - | - |
N1‑99D14 | Uplink L3 sequence numbering | - | - |
N1‑99D14 | Uplink L3 sequence numbering | - | - |
N1‑99D15 | Uplink L3 sequence numbering | - | - |
N1‑99D15 | Uplink L3 sequence numbering | - | - |
N1‑99D17 | Memory of N1#8 Kobe meeting | A Photographer | - |
N1‑99D17 | Memory of N1#8 Kobe meeting | A Photographer | - |
N1‑99D18 | Transfer of Paging Response message from 04.18 to 24.008 | Fujitsu Limited | - |
N1‑99D18 | Transfer of Paging Response message from 04.18 to 24.008 | Fujitsu Limited | - |
N1‑99D21 | Necessity of the introduction SI-IE to SM protocol in R99 | NTT COMMUNICATIONWARE | - |
N1‑99D21 | Necessity of the introduction SI-IE to SM protocol in R99 | NTT COMMUNICATIONWARE | - |
N1‑99D22 | MS and GSN-initiated PDP context modification | Ericsson | - |
N1‑99D22 | MS and GSN-initiated PDP context modification | Ericsson | - |
N1‑99D23 | - | - | - |
N1‑99D23 | - | - | - |
N1‑99D24 | Clarification of DRX | - | - |
N1‑99D24 | Clarification of DRX | - | - |
N1‑99D25 | Network Requested PDP Context Activation | - | - |
N1‑99D25 | Network Requested PDP Context Activation | - | - |
N1‑99D26 | Introduction of Reserved Service Labels in the APN | - | - |
N1‑99D26 | Introduction of Reserved Service Labels in the APN | - | - |
N1‑99D27 | Proposed response on LS on Information about current status on UE idle mode operation | CN1 | - |
N1‑99D27 | Proposed response on LS on Information about current status on UE idle mode operation | CN1 | - |
N1‑99D28 | Extended Transaction Identifier Reject | - | - |
N1‑99D28 | Extended Transaction Identifier Reject | - | - |
N1‑99D29 | LS on Service/Baseline Implementation Capabilities | TSG CN WG1 | - |
N1‑99D29 | LS on Service/Baseline Implementation Capabilities | TSG CN WG1 | - |
N1‑99D30 | Clarification of DRX | Ericsson | - |
N1‑99D30 | Clarification of DRX | Ericsson | - |
N1‑99D31 | Clarification of DRX | Ericsson | - |
N1‑99D31 | Clarification of DRX | Ericsson | - |
N1‑99D32 | Title | Source | - |
N1‑99D32 | Title | Source | - |
N1‑99D33 | Proposed Liaison statement of Impact to TS24.008 by Out Band Transcoder Control | TSG-N1 | - |
N1‑99D33 | Proposed Liaison statement of Impact to TS24.008 by Out Band Transcoder Control | TSG-N1 | - |
N1‑99D34 | Proposed Plan toward GSM/UMTS interworking Adhoc, 22-24 November | NTTDoCoMo | - |
N1‑99D34 | Proposed Plan toward GSM/UMTS interworking Adhoc, 22-24 November | NTTDoCoMo | - |
N1‑99D35 | - | TSG S2 | - |
N1‑99D35 | - | TSG S2 | - |
N1‑99D36 | Paging Response in UMTS | Fujitsu | - |
N1‑99D36 | Paging Response in UMTS | Fujitsu | - |
N1‑99D37 | Principles for secure GSM-UMTS interoperation | TSG-S2 (forward of a LS from TSG-S3) | - |
N1‑99D37 | Principles for secure GSM-UMTS interoperation | TSG-S2 (forward of a LS from TSG-S3) | - |
N1‑99D38 | Proposed Response to Liaison Statement on Issues with Multiple PDP Contexts | - | - |
N1‑99D38 | Proposed Response to Liaison Statement on Issues with Multiple PDP Contexts | - | - |
N1‑99D39 | Reply to LS on Security Algorithm Information in UE Capability | RAN WG3 | - |
N1‑99D39 | Reply to LS on Security Algorithm Information in UE Capability | RAN WG3 | - |
N1‑99D40 | Proposed Liaison statement of Impact to TS24.008 by Out Band Transcoder Control | TSG-N1 | - |
N1‑99D40 | Proposed Liaison statement of Impact to TS24.008 by Out Band Transcoder Control | TSG-N1 | - |
N1‑99D41 | Paging response in UMTS | - | - |
N1‑99D41 | Paging response in UMTS | - | - |
N1‑99D42 | Transfer of Paging Response message from 04.18 to 24.008 | Fujitsu Limited | - |
N1‑99D42 | Transfer of Paging Response message from 04.18 to 24.008 | Fujitsu Limited | - |
page generated from database: 2024-10-07 07:52:06