Recommendation ITU-T X.1040 analyses the main features and typical threats faced by e‑commerce service ecosystems, and provides a security reference architecture for lifecycle management of e-commerce business data.
SAML is an XML-based framework for exchanging security information. This security information is expressed in the form of assertions about subjects, where a subject is an entity (either human or computer) that has an identity in some security domain. A single assertion might contain several different internal statements about authentication, authorization and attributes. This Recommendation defines a protocol by which clients can request assertions from SAML authorities and get a response from them. This protocol, consisting of XML-based request and response message formats, can be bound to many different underlying communications and transport protocols; SAML currently defines one binding to SOAP over HTTP. In creating their responses, SAML authorities can use various sources of information, such as external policy stores and assertions that were received as input in requests. This Recommendation defines SAML assertions elements, subjects, conditions, processing rules and statements. Additionally, it develops a comprehensive SAML metadata profile that includes associated namespace, common data types, processing rules and signature processing. Several protocol bindings such as SOAP, PAOS (reverse SOAP), HTTP redirect, HTTP POST, among others, are also developed. This Recommendation provides a comprehensive list of SAML profiles such as web browser SSO profile and single logout profile to enable the wide adoption of SAML 2.0 in the industry. Guidelines for authentication context and conformance are also provided.This Recommendation is technically equivalent and compatible with the OASIS SAML 2.0 standard.
The document is a technical report capturing the study on application architecture for enabling edge applications over 3GPP networks. The aspects of the study include identifying architecture requirements (e.g. discovery of edge services, authentication of the clients), supporting application layer functional model and corresponding solutions to enable the deployment of applications on the edge of 3GPP networks, with no impact to edge-unaware applications on the UE and minimal impact to edge-aware applications on the UE.
The present document focuses on the UE Identity functionality. It describes the related application policy information (including authorization, access control and traffic rule pattern format), information flows, required information and service aggregation patterns. The present document specifies the necessary API, data model and data format, considering existing API(s) if applicable.
The document focuses on the MEC Location Service. It describes the related application policy information including authorization and access control, information flows, required information and service aggregation patterns. The document specifies the necessary API with the data model and data format. It is to be noted that the actual data model and data format which is functional for the present API re-uses the definitions in "RESTful Network API for Zonal Presence" and "RESTful Network API for Terminal Location" published by the Open Mobile Alliance.
The present document specifies a conformance assessment methodology for consumer IoT devices, their relation to associated services and corresponding relevant processes against ETSI TS 103 645 / ETSI EN 303 645, addressing the mandatory and recommended provisions as well as conditions and complements ETSI TS 103 645 / ETSI EN 303 645 by defining test cases and assessment criteria for each provision.
The document focuses on the support of regulatory requirements for Lawful Interception (LI) and Retained Data (RD) when implementing MEC into the network. It describes the problems, constraints, interfaces and additional capabilities needed for the different deployment scenarios, to ensure full support of LI and RD regulatory requirements when implementing MEC.
The document provides a glossary of terms relating to the conceptual, architectural and functional elements within the scope of work on Multi-access Edge Computing. The purpose of this glossary is to ensure that all terminology defined in the document is used in a consistent way by all ETSI MEC deliverables as well as in wider industry discussions on Multi-access Edge Computing.
The Technical Report studies and performs evaluations of potential architecture enhancements to support Edge Computing (EC) in the 5G Core network (5GC). Specifically, two objectives are included: a) to study the potential system enhancements for enhanced Edge Computing support, and b) to provide deployment guidelines for typical Edge Computing use cases, e.g. URLLC, V2X, AR/VR/XR, UAS, 5GSAT, CDN, etc.
The document studies: a) the complete harmonization and merger of the policy control and flow based charging architecture and procedures; b) possible architectures and solutions for adding end-user subscription differentiation and general policy control aspects to the policy- and charging control; c) alternative solutions for binding bearers to services (provided today by the authorization token). This includes studying solutions for the network to control bearer usage by service flows.
The document specifies the application layer architecture, procedures and information flows necessary for enabling edge applications over 3GPP networks. It includes architectural requirements for enabling edge applications, application layer architecture fulfilling the architecture requirements and procedures to enable the deployment of edge applications.