Tech-invite3GPPspecsGlossariesIETFRFCsGroupsSIPABNFsWorld Map



 

Here   Top   Up   Prev   Next
1…      6…   7…   8.3…   A…     

 

 

8.3  Solutions for direct discovery (non-Public Safety)
8.3.1  Solution #8.3.1: Authorisation for restricted ProSe direct discovery
8.3.2  Solution #8.3.2: Security for restricted discovery
8.3.3  Solution #8.3.3 ProSe Restricted Discovery in Model B with Match Report procedures initiated by Discoveree UE and Discoverer UE
8.3.4  Solution #8.3.4: Integrity protection of the ProSe code for restricted discovery (Model A)Word-p. 159
8.3.5  Solution #8.3.5 ProSe Restricted Discovery in Model B with Match Report procedure initiated by Discoverer UE onlyWord-p. 160
8.3.6  Solution #8.3.6 ProSe Restricted Discovery in Model B with local MIC CheckingWord-p. 165
8.3.7  Solution #8.3.7: Security for Restricted ProSe Direct DiscoveryWord-p. 170
8.3.8  Solution #8.3.8: Security for Restricted ProSe Direct Discovery (Model B)Word-p. 172
8.3.9  Solution #8.3.9 Obtaining the security parameters needed for ProSe Restricted Discovery
8.3.10  Solution #8.3.10: Confidentiality of ProSe identifiers in PC5 interfaceWord-p. 181
8.3.11  Solution #8.3.11 Protecting a Restricted Discovery Message (Model A and Model B)
8.3.12  Solution #8.3.12: Security for PC2 interface in Restricted Direct Discovery
8.3.14  Solution #8.3.14: Hint of scrambling keyWord-p. 190
8.3.15  Solution #8.3.15 Protecting a Restricted Discovery Message (Model A and Model B)Word-p. 191
8.3.16  Solution #8.3.16: Masked UTC counterWord-p. 195
8.4  Solutions for Direct Discovery (public safety use)Word-p. 196Up

Up   Top   ToC