ATIS 0200001-2010 Service Enabler Characterization Technical Report (Includes Access to Additional Content).pdf

《ATIS 0200001-2010 Service Enabler Characterization Technical Report (Includes Access to Additional Content).pdf》由会员分享，可在线阅读，更多相关《ATIS 0200001-2010 Service Enabler Characterization Technical Report (Includes Access to Additional Content).pdf（28页珍藏版）》请在麦多课文档分享上搜索。

1、 Access to Additional Content for ATIS-0200001, Dated: August 2010 (Click here to view the publication) This Page is not part of the original publication This page has been added by IHS as a convenience to the user in order to provide access to additional content as authorized by the Copyright holde

2、r of this document Click the link(s) below to access the content and use normal procedures for downloading or opening the files. Files associated with ATIS 0200001 Information contained in the above is the property of the Copyright holder and all Notice of Disclaimer for example, within a service pr

3、ovider network, within a 3rdparty SE provider domain (which doesnt have to be a network), within an operations domain, or within User Equipment. A goal is to provide maximum flexibility in where service enablers can be deployed or consumed. This document does not address how SEs get published or dis

4、covered. 2 REFERENCES The following standards contain provisions which, through reference in this text, constitute provisions of this ATIS Standard. At the time of publication, the editions indicated were valid. All standards are ATIS-0200001 2 subject to revision, and parties to agreements based on

5、 this ATIS Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. ATIS IIF WT083R3, IIF XML Guidelines.1ATIS-0800036, XML Schema for ITF Execution Environment.2ATIS-1000035.2009, Next Generation Network (NGN) Identity Management

6、(IdM) Framework.23 DEFINITIONS, ACRONYMS, uri (to be used, e.g., for searching for information on the SE, including the SE Characterization document 2. SE short name, by which it may be familiarly known and that is not necessarily unique among all SEs per SE - SE name; string 3. Keywords for relevan

7、t descriptive terms for the SE useful for searching (e.g., location, charging) pe SE - keywords: string1, , string N ATIS-0200001 4 4. Lifecycle information per SE - SE current version name; string - field ready or beta; field, beta - earliest version to which this version is backward compatible; st

8、ring - immediately prior version name; string - next version name; string - next version backward compatible with current version; yes/no - testing history information; url - in commercial service since; date - anticipated support end date; date - more information on lifecycle; url - certifying enti

9、ty name; string - information on the certifying entitys certification; url 5. Chargeability per SE - consumer of SE charged for use of SE; yes/no - charging/billing information; url NOTE: Chargeability here pertains to information or functionality that is not part of any of the SE consumer interface

10、s but is available through some other interface. The SE itself through one of its own interfaces could have provide charging functionality or information, but that would be included as part of the functional description of the SE interface(s). 4.1.2 Supported Interfaces (subgroup under SE Descriptiv

11、e Information) 6. Interface unique name in the form of hostname component, which is the Interface short name, prepended to the SE unique name per Int - Interface unique name: uri The interface unique name is tightly coupled to a specific service enabler name and is to be unique across all SEs. The i

12、nterface is a defined subset of functions of the service enabler - i.e. a service enabler could have multiple interfaces. NOTE: Interfaces and Service Enablers are both considered services in the TM Forum Information Framework (formerly known as the SID model). The distinction is made here to highli

13、ght the relationship between the interfaces and their function as an aggregate service. In reality, they are each SID services that are essentially useless if delivered separately. 7. Interface short name in the form of hostname component prepended to the SE short name; unique within the interfaces

14、short names of the same SE per Int - Interface short name; uri 8. URI of the Interface (i.e., the address of the actual interface) for consumer use per Int - Interface location; uri ATIS-0200001 5 9. Description of the functionality provided through the SE consumer interface and the type of the inte

15、rface (e.g., SOAP or RESTful) and a location identifier/url for where the formal specification of the interface can be retrieved. This descriptive characteristic does not itself directly contain the formal interface technical specification per Int - SE Consumer interface functional description; url

16、10. SE performance measurements that can be made available on a per-Consumer basis per Int - performance measurements; yes, no - performance measurements information; url NOTE: Performance measurements information may include a list of performance measurement types, location of the interface to acce

17、ss performance measurements, and nature of identity and security to do so. NOTE: Performance measurements here pertains to information or functionality that is not supported over any of the SE consumer interfaces but is available through some other interface. The SE itself through one of its own int

18、erfaces may provide performance information, but that would be included as part of the functional description of the SE interface(s). 11. Additional SE characteristic, not specifically defined here, which could be defined however a SE Provider deems useful per SE - additional characteristic; url 4.1

19、.3 Service-Level information (subgroup under Supported Interfaces) 12. Planned availability per Int - whether planned to be available 24x7; yes/no - more information on availability; url 13. Reliability per Int - % expected up time during availability window; numeric - mean time to repair; numeric -

20、 mean time between failures; numeric - more information on reliability; url 14. Capacity per Int - number of stateful sessions per second, Poisson arrivals; numeric - number of simultaneous open stateful sessions ; numeric - number of stateless transactions per second, Poisson arrivals; numeric - mo

21、re capacity model information; url 15. Response time or possibly other QoS parameters per Int - average response time in milliseconds; numeric - 95% response time in milliseconds; numeric - more response time model information; url 16. Failure/failover/degradation behavior of the SE per Int - curren

22、t session preservation: yes, no - failover/degradation behavior of the SE; url ATIS-0200001 6 4.1.4 Implementation Dependencies (subgroup under Service Level Information) 17. SE consumer interface security policy the nature of the identity and credentials that a user must supply to the SE when consu

23、ming the SE (e.g., as per some identity management/federation scheme) and how to acquire, nature of registration and authentication, encryption options or requirements per Int - document with identity/credentials/registration procedure, encryption options; url 18. User profile dependencies / relatio

24、nships per Int - user profile dependencies; url 19. Consuming entity dependencies (e.g., Operating System, plug-ins, storage, ability to provide location, etc.); dependencies may be physical or logical per Int - consuming entity dependencies information; url 20. Intermediate systems dependencies (e.

25、g., transport characteristics (e.g., bandwidth, latency) for desired quality of service); dependencies may be physical or logical per Int - intermediate system dependencies information; url 21. Test environment nature of a test environment that a potential user of the SE could or must first plug int

26、o to try out/exercise the SE, as opposed to using the SE production environment right off the bat, where there would be greater consequences of harm to service to other users if something bad happened per Int - testing with Consumer before commercial use required; yes, no - types of Test environment

27、s (e.g., functional testing of the interfaces, or load testing of the interfaces); (set of strings) - further information on testing for interface type X (e.g., uri for the test environment interface, security aspects, capacity characteristics, etc.); url 4.1.5 Eligibility 22. Eligibility dependenci

28、es (e.g., consumer must be subscribed to Svc X with Provider A in order to use this SE) per SE - eligibility dependences information; url 4.1.6 Administrative 23. Identity of the entity that created the SE per SE - SE creator name; string - more information about SE creator; url 24. SE Provider cont

29、act information e.g., for tech support including logging of troubles, faqs, or potentially customized use of the SE away from the regular terms and conditions/SLA per SE ATIS-0200001 7 - name of SE Provider; string - SE Provider support information; uri string NOTE: Provider here means the entity of

30、fering the SE to the user 25. Terms and conditions to which the Consumer must agree constraints under which the SE provider allows the SE to be consumed (e.g., might include transaction volume limitations, extent of liability if the SE isnt working right or the SE is turned down, whether the SE prov

31、ider may share the users usage data with other entities, circumstances where the SE may unilaterally terminate interaction with a Consumer and method of notification to the Consumer) per SE - terms and conditions; url 4.2 Relationship to Identity Management Three components of the Service Enabler Ch

32、aracterization overlap with and are related to identity management. Item 15, SE consumer interface security policy, addresses the nature of the users identity and credentials supplied to the SE when consuming the SE. Item 16, User profile dependencies/relationships, identifies profile information re

33、lated to the user identity. Item 22, Identity of the entity that created the SE, may be informational, but this information could also be part of a service catalog where the creating entity is formally related to the service enabler and must authorize use of the enabler. The intent of this document

34、is not to define a separate identity management structure. This document simply specifies the connections between the service enabler and the identities that create and use that service enabler. For a reference Identity Management Framework, please refer to ATIS-1000035.2009, Next Generation Network

35、 (NGN) Identity Management (IdM) Framework. 5 SERVICE ENABLER CHARACTERIZATION METADATA The metadata used to describe the Service Enabler characteristics is based on XML schema definitions. This document provides details of semantics and structure of the metadata defined in the accompanying schema.

36、This document will be modified whenever there is a change in the accompanying schema. In case of any discrepancies found between this document and schema, the XML schema should be used as an authoritative reference. 5.1 Schema Namespace The Service Enabler schema is defined in ATIS-0200001.v001.xsd

37、file. The metadata is defined using the namespace as per the XML schema guidelines TODO: REF. The data model identifier chosen for the service enabler characterization is “se”. 5.2 Legends For the purpose of defining the metadata, this document uses the following notations: ATIS-0200001 8 Schema Art

38、ifacts Example graphical representation elements simpleType complexType sequence documentation attributes 5.3 ServiceEnabler - root element The informal service enabler characterization schema defines a single root element of type ServiceEnablerType. The following diagram describes the structure of

39、the complexType ServiceEnablerType: The semantics of the child elements of the ServerEnablerType are captured in the following table: ATIS-0200001 9 Tag Name R/O Semantic DescriptiveInfo R The descriptive information of the service enabler contains: 1. Service enabler unique name. 2. SE short name.

40、3. Keywords. 4. Lifecycle information. 5. Chargeability. 6. Interface descriptions for each supported interface. ServiceLevelInfo R This type defines service level information for an interface. 1. Planned availability of the system. 2. Reliability information. 3. Capacity information. 4. Information

41、 about response characteristics of SE. 5. Failover related information. Eligibility R The Eligibility type described the implementation dependencies characteristics of the SE. AdministrativeInfo R The administrative information of the SE contains: 1. Information about the SE creator. 2. SE provider

42、contact information. 3. Terms and condition to which consumers of SE must agree. 4. Additional administrative characteristics text and URL. 5.3.1 DescriptiveInfoType The descriptive information of the Service Enabler defines the basic information about the Service Enabler as well as details of suppo

43、rted interfaces. The following diagram describes the structure of DescriptiveInfoType data: ATIS-0200001 10 The semantics of the child elements of the DescriptiveInfoType are captured in the following table: Tag Name R/O Semantics ServiceEnablerUniqueName R A unique name for the Service Enabler enti

44、ty. ServiceEnablerShortName R A short name for the Service Enabler entity. Keywords O Optional keywords of relevant descriptive terms that can be used to define the Service Enabler. LifecycleInfo O Version and compatibility related information about the Service Enabler entity. ChargingInfo O Chargea

45、bility information. SupportedInterface O Information about service interfaces supported by the Service Enabler. AdditionalCharacteristics O Additional characteristics of the Service Enabler not specifically covered in this document, allowing the opportunity for extensibility. 5.3.1.1 ServiceEnablerU

46、niqueName DataType: anyURI 5.3.1.2 ServiceEnablerShortName DataType: string 5.3.1.3 Keywords DataType: string 5.3.1.4 LifecycleInfo The complexType LifecycleInfoType captures the Service Enabler characteristics in terms of version and compatibility information. The following diagram describes its st

47、ructure: ATIS-0200001 11 The semantics of the child elements of the LifecycleInfoType are captured in the following table: ATIS-0200001 12 Tag Name R/O Semantics SECurrentVersion R SE current version name. FieldReady R Field ready or beta. BackwardCompatibleWith O Earliest version to which this vers

48、ion is backward compatible. PreviousVersion O Immediately prior version name. NextVersionName O Next version name. isNextVersionCompatible O Flag to determine if the next version is backward compatible with current version. TestingHistoryURL O Testing history URL for information. InServiceSince O In

49、 commercial service since. SupportEndDate O Anticipated support end date. LifecycleInfoURL O URL for more information on lifecycle. SECertification O Service Enabler certification information. 5.3.1.5 ChargingInfoType The Billing and Chargeability information about the Service Enabler is defined by the ChargingInfoType data structure. The following diagram shows the structure of the ChargingInfoType complexType. The following table defines the child elements of the ChargingInfoType structure: Tag