Standard

Under Development

Under Development

Under Development

Under Development

The present document contains requirements and test cases that are specific to the UPF network product class. It refers to the Catalogue of General Security Assurance Requirements and formulates specific adaptions of the requirements and test cases. It also specifies the requirements and test cases unique to the UPF network product class.

Standard Document:

https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetai...

The present document contains requirements and test cases that are specific to the UDM network product class. It refers to the Catalogue of General Security Assurance Requirements and formulates specific adaptions of the requirements and test cases. It also specifies the requirements and test cases unique to the UDM network product class.

Standard Document:

https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetai...

The present document contains requirements and test cases that are specific to the SMF network product class. It refers to the Catalogue of General Security Assurance Requirements and formulates specific adaptions of the requirements and test cases given there, as well as specifying requirements and test cases unique to the SMF network product class.

Standard Document:

https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetai...

The COEL Specification provides a clear and robust framework for implementing a distributed system capable of capturing data relating to an individual as discrete events. It facilitates a privacy-by-design approach for personalised digital services, IoT applications where devices are collecting information about identifiable individuals and the coding of behavioural attributes in identity solutions.The COEL Specification contains an extensive and detailed taxonomy of human behaviour. The taxonomy allows data from different systems to be encoded in a common format, preserving the meaning of the data across different applications.This ability to integrate universally at the data level, rather than just the technology level, is known as semantic harmonisation and provides full data portability. The communication protocols needed to support system interoperability across a wide range of implementations are also included.

The Darwin Information Typing Architecture (DITA) is an XML-based architecture for authoring, producing, anddelivering topic-oriented, information-typed content that can be reused and single-sourced in a variety of ways.While DITA historically has been driven by the requirements of large-scale technical documentation authoring,management, and delivery, it is a standard that is applicable to any kind of publication or information that mightbe presented to readers, including interactive training and educational materials, standards, reports, businessdocuments, trade books, travel and nature guides, and more.DITA is designed for creating new document types and describing new information domains based on existingtypes and domains. The process for creating new types and domains is called specialization. Specializationenables the creation of specific, targeted XML grammars that can still use tools and design rules that weredeveloped for more general types and domains; this is similar to how classes in an object-oriented system caninherit the methods of ancestor classes.

This standard specifies conformance clauses in accordance with the OASIS TC Process ([TC-PROC] section 2.2.6 for the KMIP Specification [KMIP-SPEC] for a KMIPserver or KMIP client through profiles that define the use of KMIP objects, attributes, operations, message elements and authentication methods within specific contexts of KMIP server and client interaction.These profiles define a set of normative constraints for employing KMIP within a particular environment or context of use. They may, optionally, require the use of specific KMIP functionality or in other respects define the processing rules to be followed by profile actors.

MQTTisa Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.

The XACML architecture promotes a loose coupling between the component that enforces decisions, the policy enforcement point (PEP), and the component that decides based on XACML policies, the policy decision point (PDP). The XACML standard defines the format of the request and the response between thePEP and the PDP. As the default representation of XACML is XML and is backed by a schema, the request and response 8are typically expressed as XML elements or documents. With the rise in popularity of APIs and its consumerization, it becomes important for XACML to be easily understood in order to increase the likelihood it will be adopted. This profile aims at defining a JSON format for the XACML request and response. It also defines the transport between client (PEP) and service (PDP).