The 5G Standard

3GPP TDocs (written contributions) at meeting

Meeting: S3-41 - 2005-11-15 to 2005-11-18, San Diego

meeting id: S3-41 (click id for more info on this meeting)

Click on the Tdoc to open its file.

TDoc Title Source Remarks
S3‑050674 - - imported from 3GU
S3‑050675 - - imported from 3GU
S3‑050676 - - imported from 3GU
S3‑050677 - - imported from 3GU
S3‑050678 - - imported from 3GU
S3‑050679 - - imported from 3GU
S3‑050680 - - imported from 3GU
S3‑050681 - - imported from 3GU
S3‑050682 - - imported from 3GU
S3‑050683 - - imported from 3GU
S3‑050684 - - imported from 3GU
S3‑050685 - - imported from 3GU
S3‑050686 - - imported from 3GU
S3‑050687 - - imported from 3GU
S3‑050688 - - imported from 3GU
S3‑050689 - - imported from 3GU
S3‑050690 - - imported from 3GU
S3‑050691 - - imported from 3GU
S3‑050692 - - imported from 3GU
S3‑050693 - - imported from 3GU
S3‑050694 - - imported from 3GU
S3‑050695 - - imported from 3GU
S3‑050696 - - imported from 3GU
S3‑050697 - - imported from 3GU
S3‑050698 - - imported from 3GU
S3‑050699 - - imported from 3GU
S3‑050700 - - imported from 3GU
S3‑050701 - - imported from 3GU
S3‑050702 - - imported from 3GU
S3‑050703 - - imported from 3GU
S3‑050704 - - imported from 3GU
S3‑050705 - - imported from 3GU
S3‑050706 - - imported from 3GU
S3‑050707 - - imported from 3GU
S3‑050708 - - imported from 3GU
S3‑050709 - - imported from 3GU
S3‑050710 - - imported from 3GU
S3‑050711 - - imported from 3GU
S3‑050712 - - imported from 3GU
S3‑050713 - - imported from 3GU
S3‑050714 - - imported from 3GU
S3‑050715 - - imported from 3GU
S3‑050716 - - imported from 3GU
S3‑050717 - - imported from 3GU
S3‑050718 - - imported from 3GU
S3‑050719 - - imported from 3GU
S3‑050720 - - imported from 3GU
S3‑050721 - - imported from 3GU
S3‑050722 - - imported from 3GU
S3‑050723 - - imported from 3GU
S3‑050724 - - imported from 3GU
S3‑050725 - - imported from 3GU
S3‑050726 - - imported from 3GU
S3‑050727 - - imported from 3GU
S3‑050728 - - imported from 3GU
S3‑050729 - - imported from 3GU
S3‑050730 - - imported from 3GU
S3‑050731 - - imported from 3GU
S3‑050732 - - imported from 3GU
S3‑050733 - - imported from 3GU
S3‑050734 - - imported from 3GU
S3‑050735 - - imported from 3GU
S3‑050736 - - imported from 3GU
S3‑050737 - - imported from 3GU
S3‑050738 - - imported from 3GU
S3‑050739 - - imported from 3GU
S3‑050740 - - imported from 3GU
S3‑050741 - - imported from 3GU
S3‑050742 - - imported from 3GU
S3‑050743 - - imported from 3GU
S3‑050744 - - imported from 3GU
S3‑050745 - - imported from 3GU
S3‑050746 - - imported from 3GU
S3‑050747 - - imported from 3GU
S3‑050748 - - imported from 3GU
S3‑050749 - - imported from 3GU
S3‑050750 - - imported from 3GU
S3‑050751 - - imported from 3GU
S3‑050752 - - imported from 3GU
S3‑050753 - - imported from 3GU
S3‑050754 - - imported from 3GU
S3‑050755 - - imported from 3GU
S3‑050756 - - imported from 3GU
S3‑050757 - - imported from 3GU
S3‑050758 - - imported from 3GU
S3‑050759 - - imported from 3GU
S3‑050760 - - imported from 3GU
S3‑050761 - - imported from 3GU
S3‑050762 - - imported from 3GU
S3‑050763 - - imported from 3GU
S3‑050764 - - imported from 3GU
S3‑050765 - - imported from 3GU
S3‑050766 - - imported from 3GU
S3‑050767 - - imported from 3GU
S3‑050768 - - imported from 3GU
S3‑050769 - - imported from 3GU
S3‑050770 MTK storage rules on UEs - imported from 3GU
S3‑050771 - - imported from 3GU
S3‑050772 - - imported from 3GU
S3‑050773 - - imported from 3GU
S3‑050774 - - imported from 3GU
S3‑050775 - - imported from 3GU
S3‑050776 - - imported from 3GU
S3‑050777 - - imported from 3GU
S3‑050778 - - imported from 3GU
S3‑050779 - - imported from 3GU
S3‑050780 - - imported from 3GU
S3‑050781 - - imported from 3GU
S3‑050782 - - imported from 3GU
S3‑050783 - - imported from 3GU
S3‑050784 - - imported from 3GU
S3‑050785 - - imported from 3GU
S3‑050786 - - imported from 3GU
S3‑050787 - - imported from 3GU
S3‑050788 - - imported from 3GU
S3‑050789 - - imported from 3GU
S3‑050790 - - imported from 3GU
S3‑050791 - - imported from 3GU
S3‑050792 - - imported from 3GU
S3‑050793 - - imported from 3GU
S3‑050794 - - imported from 3GU
S3‑050795 - - imported from 3GU
S3‑050796 - - -
S3‑050797 - - -
S3‑050799 - - -
S3‑050800 - - -
S3‑050801 - - -
S3‑050802 - - -
S3‑050803 - - -
S3‑050804 - - -
S3‑050805 - - -
S3‑050806 - - -
S3‑050807 ^^Reply LS on support of IMS emergency sessions S3 -
S3‑050808 - - -
S3‑050809 LS on the guidelines for HTTP based Zn reference point S3 -
S3‑050810 NAF_Id encoding - -
S3‑050811 NAF_Id encoding - -
S3‑050812 LS on Ua Security Protocol Identifier and Organisation Identifier in Generic Bootstrapping Architecture S3 -
S3‑050813 Informative annex with examples on interoperator GBA usage - -
S3‑050814 LS on Security solutions for push based services S3 -
S3‑050815 Clarification of local policy enforcement - -
S3‑050816 - - -
S3‑050817 - - -
S3‑050818 Alignment of 2G GBA with recent CRs - -
S3‑050819 Addition of information requested by SA plenary on 2G GBA - -
S3‑050820 IMPI obtained from IMSI in 2G GBA - -
S3‑050821 - - -
S3‑050822 - - -
S3‑050823 LS Authentication of fixed network SIP phones in an IMS based network and interactions between Session Border Controllers and the ISC interface S3 -
S3‑050824 Reply LS on improvement of the way to access IMS via I-WLAN S3 -
S3‑050825 Correction of text on negotiation of confidentiality algorithms - -
S3‑050826 Extension of scope to encompass TISPAN NGN by addition of normative annex - -
S3‑050827 - - -
S3‑050828 Correction of CR implementation - -
S3‑050829 Use of IMPU in HTTP header for HTTP security mechanism - -
S3‑050830 Correction of Sh Secure IP Address Binding Information Notification Inconsistency - -
S3‑050831 - - -
S3‑050832 Extension of scope to encompass TISPAN NGN - -
S3‑050833 Clarify key set handling for PS handover - -
S3‑050834 Correction on Keystatus sent by CN node in Security Mode Command - -
S3‑050835 Correction on Keystatus sent by CN node in Security Mode Command - -
S3‑050836 - - -
S3‑050837 IMSI availability at PDG - -
S3‑050838 - - -
S3‑050839 Reply LS on support for simultaneous WLAN direct IP access sessions S3 -
S3‑050840 Reply LS to SA2 on solution for the private NW access from 3GPP I-WLAN access S3 -
S3‑050841 LS on time plan on IMS security extensions S3 -
S3‑050842 Reply LS on Security Requirements for Long Term Evolved RAN/3GPP System Architecture Evolution S3 -
S3‑050843 Reply LS on Security Aspects of Long Term Evolved RAN/3GPP System Architecture Evolution S3 -
S3‑050844 Response LS on WLAN service configuration parameters S3 -
S3‑050845 Reply LS Request for comments on IEEE 802.11u Requirements Document from the IEEE 802.11 Task Group u. S3 -
S3‑050846 Response LS on the Mobile Broadcast Services Specifications S3 -
S3‑050847 ROC synchronization - -
S3‑050848 Correction on MSK processing in case of solicited pull procedure - -
S3‑050849 Handling several status codes in one response message - -
S3‑050850 LS on Handling several status codes in one response message S3 -
S3‑050851 Definition of newer MSK - -
S3‑050852 LS on the development of an Example A8_V algorithm S3 -
S3‑050853 - - -
S3‑050854 - - -
S3‑050855 - - -
S3‑050856 - - -
S3‑050857 LS on Definition of an Liberty Authentication Context S3 -
S3‑050858 - - -
S3‑050859 Reply LS on security considerations regarding Personal Network Management S3 -
S3‑050860 - - -
S3‑050861 - - -
S3‑050862 Removal of possible interoperability problems - -
S3‑050863 LS on Identification of the authentication domains by the HLR S3 -
S3‑050864 - - -
S3‑050865 ASN.1 module cleanup. - -
S3‑050866 Adding definition for ‘Precision’. - -
S3‑050867 Start of interception for already attached UE - -
S3‑050868 Start of interception for already attached UE - -
S3‑050869 Availability of IMSI at PDG - -
S3‑050870 Availability of IMSI at PDG - -
S3‑050871 Wrong references to tables for subaddress - -
S3‑050872 Wrong references to tables for subaddress - -
S3‑050873 Alignment with ETSI TS 101 671 - Clarification on CIN - -
S3‑050874 Security implications of RAN LTE control plane architectural alternatives S3 -

page generated from database: 2024-04-22 07:58:53

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