Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
| N4-040861 | Preliminary Agenda for CN4 #24 | Chairman, TSG-CN WG4 | - |
| N4-040862 | Detailed Agenda for CN4 #24 status at document deadline | Chairman, TSG-CN WG4 | - |
| N4-040863 | Detailed Agenda for CN4 #24 status on eve of meeting | Chairman, TSG-CN WG4 | - |
| N4-040864 | Proposed allocation of documents to agenda items for TSG-CN WG4 Meeting #23, status at document deadline | Chairman, TSG-CN WG4 | - |
| N4-040865 | Proposed allocation of documents to agenda items for TSG-CN WG4 Meeting #23, status on eve of meeting | Chairman, TSG-CN WG4 | - |
| N4-040866 | Summary report of CN#24 and SA#24, Seoul, Korea | CN4 Chairman | - |
| N4-040867 | Output Documents | Chairman, TSG-CN WG4 | - |
| N4-040868 | - | - | - |
| N4-040869 | - | - | - |
| N4-040870 | - | - | - |
| N4-040871 | - | - | - |
| N4-040872 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | China Mobile,HUAWEI | - |
| N4-040873 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | HUWEI,China Mobile | - |
| N4-040874 | Add 3 parameters to CollectedDigits | China Mobile , Huawei Technologies | - |
| N4-040875 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | HUWEI,China Mobile | - |
| N4-040876 | Add 1 parameter to VariablePart | China Mobile, Huawei Technologies | - |
| N4-040877 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | HUWEI,China Mobile | - |
| N4-040878 | CR for Enhancing Camel CAP 3 To Implement services based on UIScript | China Mobile, Huawei Technologies Co.,Ltd | - |
| N4-040879 | How to add the DCH | China Mobile, HUAWEI | - |
| N4-040880 | When to apply the DCH parameter | China Mobile, HUAWEI | - |
| N4-040881 | XML versioning | - | - |
| N4-040882 | XML versioning | - | - |
| N4-040883 | Use of regular expressions | - | - |
| N4-040884 | Use of regular expressions | - | - |
| N4-040885 | Triggering initial REGISTER messages | - | - |
| N4-040886 | Addition of cause code mapping to the routing area update procedure | - | - |
| N4-040887 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | HUAWEI | - |
| N4-040888 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | HUAWEI | - |
| N4-040891 | LS on RIM routing addressing between GERAN and UTRAN | TSG GERAN WG2 | - |
| N4-040892 | Reply to LS on mapping of cause codes for no radio resources available and for load higher in target cell | GERAN | - |
| N4-040893 | LS on transparent container field for MBMS | CN1 | - |
| N4-040894 | Reply LS on the flexibility of filtering of register request | CN1 | - |
| N4-040895 | LS on CAMEL open item list | CN2 | - |
| N4-040896 | LS on Re-use of RADIUS attributes within the 3gpp specific vendor id | CN3 | - |
| N4-040897 | Reply LS on Harmonisation of AMR Configurations | RAN WG2 | - |
| N4-040898 | Reply LS on Clarification of TMGI format | RAN2 | - |
| N4-040899 | LS on ‘Generic Routing of RIM/NACC Information’. | TSG RAN3 | - |
| N4-040900 | LS on Trace Issues | RAN3 | - |
| N4-040901 | LS on mapping of cause codes for no radio resources available and for load higher in target cell | RAN3 | - |
| N4-040902 | LS on Evaluation of MOCN redirect alternatives | RAN3 | - |
| N4-040903 | SA1 Comments on Physical Storage of GUP components | SA1 | - |
| N4-040904 | LS on WLAN Charging Identifiers | SA1 | - |
| N4-040905 | LS on the flexibility of filtering of register request | SA2 | - |
| N4-040906 | Reply LS on LS on change in MBMS Multicast Service Deactivation Procedure | SA2 | - |
| N4-040907 | Response to RAN3 Multicast and Broadcast service info to the RAN | SA2 | - |
| N4-040908 | Reply to LS on transparent container field for MBMS | SA2 | - |
| N4-040909 | Reply LS on the Nature of LCS | SA2 | - |
| N4-040910 | Status report of LCS standardisation in 3GPP SA2 | 3GPP TSG-SA WG2 | - |
| N4-040911 | Reply LS to N4-040247 (S3-040208) on use of authentication re-attempt IE | TSG SA3 | - |
| N4-040912 | Liaison Statement on VGCS and VBS security | SA WG3 | - |
| N4-040913 | Reply LS on Request for Comments on Wi-Fi Alliance Public Access MRD draft v1.0 | 3GPP SA WG3 | - |
| N4-040914 | LS on ‘SMS Fraud countermeasures’ | SA3 | - |
| N4-040915 | Reply LS on Requirement for presence of the GAA-Application-Type AVP | SA3 | - |
| N4-040916 | LS on Binding Scenario Information to Mutual EAP Authentication | SA3 | - |
| N4-040917 | LS on GUP Security Progress in SA3 | SA3 | - |
| N4-040918 | LS on Forwards compatibility to TLS based access security in IMS | SA3 | - |
| N4-040919 | LS on Assignment of the Diameter codes and identifiers | SA5 | - |
| N4-040920 | - | - | - |
| N4-040921 | Analysis on Include regulation for insert the AccessRestricationData | China mobile | - |
| N4-040922 | LS on progress of MBMS security | SA3 | - |
| N4-040923 | Optimization of User Profile Download | - | - |
| N4-040924 | Optimization of User Profile Download | - | - |
| N4-040925 | Pre-Paging Resource Optimization | - | - |
| N4-040926 | Pre-Paging Resource Optimization | - | - |
| N4-040927 | Support of User-to-User Information (UUI) in CAMEL InitialDP operation | - | - |
| N4-040928 | Support of User-to-User Information (UUI) in CAMEL InitialDP operation | - | - |
| N4-040929 | Export of UU-Data data type | - | - |
| N4-040930 | When a call is established, the CSE shall be able to instruct the VPLMN of the served subscriber whether to prohibit Call Hold. | Nortel Networks, Siemens | - |
| N4-040931 | Editorial correction | - | - |
| N4-040932 | Correcting status in the procedure CAME_MT_CTR(sheet 4) | - | - |
| N4-040933 | Redundantly modifying call parameter in CAMEL_MT_GMSC_Notify_CF | - | - |
| N4-040934 | Correcting SDL of Process CS_gsmSSF(sheet 7) | - | - |
| N4-040935 | - | - | - |
| N4-040936 | Appended a note in Process CAMEL_ICA_MSC | - | - |
| N4-040937 | - | - | - |
| N4-040938 | Add “CAMEL_Stop_TNRy”in Procedure OG_Call_Setup _MSC (sheet 4) | - | - |
| N4-040939 | Correction of Check_Criteria Procedure names referenced in Process imcnSSF | - | - |
| N4-040940 | Application version control | - | - |
| N4-040941 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Lucent Technologies | - |
| N4-040942 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Lucent Technologies | - |
| N4-040943 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Lucent Technologies | - |
| N4-040944 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Lucent Technologies | - |
| N4-040945 | DISC on Authentication, Authorisation and Accounting protocols used in I^^WLAN | Vodafone, T^^Mobile | - |
| N4-040946 | Alignment and enhancement of the ""RAT Type"" IE | - | - |
| N4-040947 | Protocol impact from providing IMS services via fixed broadband | Siemens | - |
| N4-040948 | Correction of Procedure “Activate Voice Processing Function” | - | - |
| N4-040949 | Correction of Procedure “Activate Voice Processing Function” | - | - |
| N4-040950 | Encoding Considerations for the Mn Interface | Siemens, Nokia | - |
| N4-040951 | TS 29.332, Mn interface, Add transport option, UDP and M3UA/SCTP | Siemens, Nokia | - |
| N4-040952 | TS 29.332, Mn interface, IMS Procedures and Formats and codes | Siemens, Nokia | - |
| N4-040953 | TS 29.332, Mn interface, Non call related Procedures | Siemens, Nokia | - |
| N4-040954 | TS 29.332, Mn interface, Procedures for ISUP terminations | Siemens, Nokia | - |
| N4-040955 | TS 29.332, Mn interface, TDM Procedures | Siemens, Nokia | - |
| N4-040956 | TS 29.332, Mn interface, Procedures for BICC terminations | Siemens, Nokia | - |
| N4-040957 | TS 29.332, Mn interface, proposed change on document structure on 29.332 | Siemens, Nokia | - |
| N4-040958 | [DRAFT][D1] LS on SMS Fraud countermeasures | CN4 | - |
| N4-040959 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Siemens | - |
| N4-040960 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Siemens | - |
| N4-040961 | Corrections to charging information Ies | - | - |
| N4-040962 | Background of and procedures for the "".3gppnetwork.org"" domain name | - | - |
| N4-040963 | Simplification of the User Profile Split concept | - | - |
| N4-040964 | Simplification of the User Profile Split concept | - | - |
| N4-040965 | Simplification of the User Profile Split concept | - | - |
| N4-040966 | Simplification of the User Profile Split concept | - | - |
| N4-040967 | Methods for combating SMS Fraud | Vodafone | - |
| N4-040968 | Methods for combating SMS Fraud | Vodafone | - |
| N4-040969 | Methods for combating SMS Fraud | Vodafone | - |
| N4-040970 | Triggering all/initial REGISTER messages | Nokia | - |
| N4-040971 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Nokia | - |
| N4-040972 | Reply LS on Harmonisation of AMR Configurations | T1 | - |
| N4-040973 | TS 29.240, Security | Ericsson | - |
| N4-040974 | Re-arrangement of table 7.1 in 29.230 | Nortel Networks | - |
| N4-040975 | - | - | - |
| N4-040976 | - | - | - |
| N4-040977 | - | - | - |
| N4-040979 | Accounting Procedures on the Wa interface | Nokia | - |
| N4-040980 | Accounting Procedures on the Wd interface | Nokia | - |
| N4-040981 | Definition for the Routing Policy AVP | Nokia | - |
| N4-040982 | Additional Radius Attributes and Diameter AVPs on the Wa & Wd Interface | Nokia | - |
| N4-040983 | Policy Download to the WAG on the Wg Interface | Nokia | - |
| N4-040984 | WAG initiated Routing policy cancellation Notification/Response using STR/STA | Nokia | - |
| N4-040985 | 3GPP AAA Server/Proxy Routing policy cancellation Request/Response using ASR/ASA | Nokia | - |
| N4-040986 | Wn interface description | Nokia | - |
| N4-040987 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Nokia | - |
| N4-040988 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Nokia | - |
| N4-040989 | Correction of Charging application reference | - | - |
| N4-040990 | Addition of cause code mapping to the routing area update procedure | - | - |
| N4-040991 | Discussion on the protocol implementation of Wd reference pint | China Mobile, Huawei | - |
| N4-040992 | Analysis on RADIUS fulfilling the requirements for 3GPP-WAN interworking system | China Mobile, Huawei | - |
| N4-040993 | Error Indication during an ongoing MBMS data transfer | - | - |
| N4-040994 | Error Indication during an ongoing MBMS data transfer | - | - |
| N4-040995 | Addition of Recovery IE in MBMS | - | - |
| N4-040996 | Restoration of GSNs in MBMS | - | - |
| N4-040997 | 3GUP package corrections | - | - |
| N4-040998 | Rate Control Handling in MGW during Relocation/Handover for TrFO | LM Ericsson | - |
| N4-040999 | TS 29.234, Wm reference point AVPs | Ericsson | - |
| N4-041000 | Introduction of re-authentication identity | - | - |
| N4-041001 | Correction on Visited-Network-Identifier AVP | Ericsson | - |
| N4-041002 | Work Item Description on Trace Management, stage3, network, update | CN4 | - |
| N4-041003 | Open issues in 29.240 | Nokia | - |
| N4-041004 | TS 29.240, Proposal for moving text between chapters | Nokia | - |
| N4-041005 | Updates from SA3 to TS 29.109 | Nokia | - |
| N4-041006 | GAA Domain Data structure | Nokia | - |
| N4-041007 | GAA Domain Data structure | - | - |
| N4-041008 | Applying Application IDs for Zh and Zn | Nokia | - |
| N4-041009 | Are Mandatory GAA AVPs required ? | Nokia | - |
| N4-041010 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Nokia | - |
| N4-041011 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Nokia | - |
| N4-041012 | - | - | - |
| N4-041013 | - | - | - |
| N4-041015 | - | - | - |
| N4-041016 | RIM transparent routing | - | - |
| N4-041017 | - | - | - |
| N4-041018 | - | - | - |
| N4-041019 | Clarification of the Automatic Device Detection feature | - | - |
| N4-041020 | Editorial correction of table definition | - | - |
| N4-041021 | Wrong SDL flow page implemented | - | - |
| N4-041022 | Clarification on the handling of operation invocation when LinkedID is missing although expected | - | - |
| N4-041023 | Clarification on the handling of operation invocation when LinkedID is missing although expected | - | - |
| N4-041024 | Correction to CAP SCI for calls with multiple CAP dialogues | - | - |
| N4-041025 | Correction to usage of ACM for CAP ETC and CAP CTR | - | - |
| N4-041026 | Correction to ICA_MSC1 and CAMEL_ICA_MSC2 | - | - |
| N4-041027 | Removal of Int_O_Exception from CAMEL_OCH_MSC2 and CAMEL_MT_GMSC_DISC5 | - | - |
| N4-041028 | Correction to CAMEL_Modify_CUG_Info | - | - |
| N4-041029 | Correction to Cancel procedure description | - | - |
| N4-041030 | Correction to CAMEL_EXPORT_LEG_MSC procedure | - | - |
| N4-041032 | Correction to CS_gsmSSF for EDS | - | - |
| N4-041033 | Correction to CS_gsmSSF for Tcp expiry | - | - |
| N4-041034 | Correction to Handle_ACR procedure for Tccd timer | - | - |
| N4-041036 | Correction to any Time Interrogation | - | - |
| N4-041037 | Correction to SplitLeg ASN.1 description | - | - |
| N4-041038 | Correction to Apply Charging Report procedure | - | - |
| N4-041039 | Correction to Assist Reqiest Instructions procedure | - | - |
| N4-041040 | Correction to Call Information Request and Report | - | - |
| N4-041041 | Correction to Tssf timer setting for SMS control | - | - |
| N4-041042 | Discussion document proposing introduction of CAMEL DP3 trunk triggering | Nortel Networks | - |
| N4-041043 | Information, Proposition for the Introduction of CAMEL DP3 Trunk Triggering | Nortel Networks | - |
| N4-041044 | [H10] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Ericsson | - |
| N4-041045 | [H10] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Ericsson | - |
| N4-041046 | [H10] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Ericsson | - |
| N4-041047 | [H10] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Ericsson | - |
| N4-041048 | Updated Discussion paper on “Delete PDP Context Correction” | Ericsson | - |
| N4-041050 | SGSN Context Request and IMSI | - | - |
| N4-041051 | Introduction of a transparent container field for MBMS | - | - |
| N4-041052 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | RIM, Fujitsu | - |
| N4-041053 | - | - | - |
| N4-041054 | Provisioning Of Base Root package properties | - | - |
| N4-041055 | Service Change Address | - | - |
| N4-041056 | Use Of Event Buffers | - | - |
| N4-041057 | Digit Maps | - | - |
| N4-041058 | IP secured transport | - | - |
| N4-041059 | Use Of Audit Value | - | - |
| N4-041060 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | LM Ericsson | - |
| N4-041061 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | LM Ericsson | - |
| N4-041062 | Use Of Statistics | - | - |
| N4-041063 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | LM Ericsson | - |
| N4-041064 | Termination Restoration | - | - |
| N4-041065 | Handling of ciphering and integrity keys at inter-SGSN RAU | - | - |
| N4-041066 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Siemens | - |
| N4-041067 | Clarification on Outstanding Request Counter (ORC) handling at EDP-R or TDP-R resumption | - | - |
| N4-041068 | - | - | - |
| N4-041069 | MBMS WID Update | Ericsson | - |
| N4-041070 | Correction of the Application-Id code | - | - |
| N4-041071 | Correction of the Application-Id code | - | - |
| N4-041072 | Correction of the Application-Id code | - | - |
| N4-041073 | Correction of the Application-Id code | - | - |
| N4-041074 | Correction of the Application-Id code | - | - |
| N4-041075 | Triggering initial REGISTER messages | - | - |
| N4-041076 | Enhancements of VGCS in public networks for communication of public authority officials | Siemens | - |
| N4-041077 | Revision of Network Sharing stage 3 | TeliaSonera | - |
| N4-041078 | Inclusion of selected CN operator ID parameter | - | - |
| N4-041079 | GAA Domain Data structure | - | - |
| N4-041080 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Nokia | - |
| N4-041081 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Nokia | - |
| N4-041082 | - | - | - |
| N4-041083 | - | - | - |
| N4-041084 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Orange | - |
| N4-041085 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Orange | - |
| N4-041086 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Orange | - |
| N4-041087 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Orange | - |
| N4-041088 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Orange | - |
| N4-041089 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Orange | - |
| N4-041090 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Orange | - |
| N4-041091 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Orange | - |
| N4-041092 | Editorial Corrections to 29.234 | Nokia | - |
| N4-041093 | Triggering initial REGISTER messages | - | - |
| N4-041095 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | LM Ericsson | - |
| N4-041096 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | China Mobile,HUAWEI | - |
| N4-041097 | Add 3 parameters to CollectedDigits | China Mobile , Huawei Technologies | - |
| N4-041098 | Use of regular expressions | - | - |
| N4-041099 | Use of regular expressions | - | - |
| N4-041100 | Triggering initial REGISTER messages | - | - |
| N4-041101 | - | - | - |
| N4-041102 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Orange | - |
| N4-041103 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Orange | - |
| N4-041104 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Orange | - |
| N4-041105 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Orange | - |
| N4-041106 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Orange | - |
| N4-041107 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Orange | - |
| N4-041108 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Orange | - |
| N4-041109 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Orange | - |
| N4-041110 | [DRAFT][D1] LS Response on LS on Assignment of the Diameter codes and identifiers | CN4 | - |
| N4-041111 | Reply LS on the flexibility of filtering of register request | CN4 | - |
| N4-041114 | DISC 29.234; Re-organization of the AVPs | Ericsson | - |
| N4-041115 | LS on New Cause Code in RANAP for “Traffic load in the target cell higher than in the source cell” | CN4 | - |
| N4-041116 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Nokia | - |
| N4-041117 | Updates from SA3 to TS 29.109 | Nokia | - |
| N4-041118 | Are Mandatory GAA AVPs required ? | Nokia | - |
| N4-041119 | Methods for combating SMS Fraud | Vodafone | - |
| N4-041120 | XML versioning | - | - |
| N4-041121 | XML versioning | - | - |
| N4-041122 | Optimization of User Profile Download | - | - |
| N4-041123 | Response on LS on Assignment of the Diameter codes and identifiers | CN4 | - |
| N4-041124 | Simplification of the User Profile Split concept | - | - |
| N4-041125 | Simplification of the User Profile Split concept | - | - |
| N4-041126 | Removal of User Data Request Type AVP | - | - |
| N4-041127 | Addition of cause code mapping to the routing area update procedure | - | - |
| N4-041128 | Pre-Paging Resource Optimization | - | - |
| N4-041129 | Clarification of the Automatic Device Detection feature | - | - |
| N4-041130 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Nokia | - |
| N4-041131 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Nokia | - |
| N4-041132 | RIM transparent routing | - | - |
| N4-041133 | LS on RIM routing addressing between GERAN and UTRAN | CN4 | - |
| N4-041134 | Clarification on Outstanding Request Counter (ORC) handling at EDP-R or TDP-R resumption | - | - |
| N4-041135 | SGSN Context Request and IMSI | - | - |
| N4-041136 | SGSN Context Request and IMSI | - | - |
| N4-041137 | [DRAFT][D1] LS on Clarification of TMGI format | CN4 | - |
| N4-041138 | Introduction of a transparent container field for MBMS | - | - |
| N4-041139 | Accounting Procedures on the Wa interface | Nokia | - |
| N4-041140 | Definition for the Routing Policy AVP | Nokia | - |
| N4-041141 | Additional Radius Attributes and Diameter AVPs on the Wa & Wd Interface | Nokia | - |
| N4-041142 | Policy Download to the WAG on the Wg Interface | Nokia | - |
| N4-041143 | 3GPP AAA Server/Proxy Routing policy cancellation Request/Response using ASR/ASA | Nokia | - |
| N4-041144 | DISC 29.234; Re-organization of the AVPs | Ericsson | - |
| N4-041145 | Introduction of re-authentication identity | - | - |
| N4-041146 | Editorial Corrections to 29.234 | Nokia | - |
| N4-041147 | TS 29.240, Security | Ericsson | - |
| N4-041148 | LS on Request for end to end example showing how the Liberty Alliance security framework fits the 3GPP GUP security requirements | CN4 | - |
| N4-041149 | - | - | - |
| N4-041150 | - | - | - |
| N4-041151 | CAMEL open issue status list | CN4 Vice-chairman | - |
| N4-041152 | 3GUP package corrections | - | - |
| N4-041153 | 3GUP package corrections | - | - |
| N4-041154 | TS 29.332, Mn interface, Add transport option, UDP and M3UA/SCTP | Siemens, Nokia | - |
| N4-041155 | TS 29.332, Mn interface, IMS Procedures and Formats and codes | Siemens, Nokia | - |
| N4-041156 | - | - | - |
| N4-041157 | Correction of Procedure “Activate Voice Processing Function” | - | - |
| N4-041158 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | LM Ericsson | - |
| N4-041159 | Use Of Statistics | - | - |
| N4-041161 | Simplification of the User Profile Split concept | - | - |
| N4-041162 | Simplification of the User Profile Split concept | - | - |
| N4-041163 | CAMEL open issue status list | CN4 Vice-chairman | - |
| N4-041164 | - | - | - |
| N4-041165 | GAA Domain Data structure | - | - |
| N4-041166 | LS on Generic Authentication Architecture (GAA) | CN4 | - |
| N4-041167 | Are Mandatory GAA AVPs required ? | Nokia | - |
| N4-041168 | - | - | - |
| N4-041170 | LS on mapping tunnels for WLAN 3GPP IP access and W-APNs | SA2 | - |
| N4-041171 | [DRAFT][D1] LS on support of the RADIUS protocol in I^^WLAN | CN4 | - |
| N4-041172 | LS on Supporting RADIUS/DIAMETER Protocol at Wd Interface | SA2 | - |
| N4-041173 | Support of User-to-User Information (UUI) in CAMEL InitialDP operation | - | - |
| N4-041174 | Correction to ERB pre-condition for IM-SSF state | - | - |
| N4-041175 | Clarification on the handling of operation invocation when LinkedID is missing although expected | - | - |
| N4-041176 | Clarification on the handling of operation invocation when LinkedID is missing although expected | - | - |
| N4-041177 | - | - | - |
| N4-041178 | Editorial correction | - | - |
| N4-041179 | Appended a note in Process CAMEL_ICA_MSC | - | - |
| N4-041180 | LS on the flexibility of filtering of register request | SA2 | - |
| N4-041181 | Add “CAMEL_Stop_TNRy”in Procedure OG_Call_Setup _MSC (sheet 4) | - | - |
| N4-041182 | Clarification on Outstanding Request Counter (ORC) handling at EDP-R or TDP-R resumption | - | - |
| N4-041183 | Support of User-to-User Information (UUI) in CAMEL InitialDP operation | - | - |
| N4-041184 | Clarification on the handling of operation invocation when LinkedID is missing although expected | - | - |
| N4-041185 | Clarification on the handling of operation invocation when LinkedID is missing although expected | - | - |
| N4-041186 | Appended a note in Process CAMEL_ICA_MSC | - | - |
| N4-041187 | Renumbering of 3GPP specific AVP codes | - | - |
| N4-041188 | Renumbering of 3GPP specific AVP codes | - | - |
| N4-041189 | Renumbering of 3GPP specific AVP codes | - | - |
| N4-041190 | Renumbering of 3GPP specific AVP codes | - | - |
| N4-041191 | Renumbering of 3GPP specific AVP codes | - | - |
| N4-041192 | [DRAFT][D1] LS on renumbering of 3GPP specific AVP’s in 3GPP TS 23.230 | CN4 | - |
| N4-041193 | LS on SMS Fraud countermeasures | CN4 | - |
| N4-041194 | [DRAFT][D1] LS on Evaluation of the alternatives for SMS fraud countermeasures. | CN4 | - |
| N4-041195 | LS on the Request of Gmb Diameter code values | CN3 | - |
| N4-041196 | Addition of cause code mapping for inter-system handover | - | - |
| N4-041197 | Addition of cause code mapping for inter-system handover | - | - |
| N4-041198 | - | - | - |
| N4-041199 | [DRAFT][D1] LS on support of the RADIUS protocol in I^^WLAN | CN4 | - |
| N4-041200 | Spec Update to 29.234 and open items | Nokia | - |
| N4-041201 | LS on support of the RADIUS protocol in I^^WLAN | CN4 | - |
| N4-041202 | LS on Request for end to end example showing how the Liberty Alliance security framework fits the 3GPP GUP security requirements | CN4 | - |