hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.31 Link_Amf_Uaaf | |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.31.1 Definition | This IOC models the a3 reference point as defined in ES 282 004 [5]. |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.32 Link_Aracf_Clf | |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.32.1 Definition | This IOC models the e4 reference point as defined in ES 282 003 [4]. |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.33 Link_Aracf_Rcef | |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.33.1 Definition | This IOC models the Re reference point as defined in ES 282 003 [4]. |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.34 Link_Aracf_Spdf | |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.34.1 Definition | This IOC models the Rq reference point as defined in ES 282 003 [4]. ETSI ETSI TS 188 005-2 V2.1.1 (2009-02) 27 |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.35 Link_Bgf_Spdf | |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.35.1 Definition | This IOC models the Ia reference point as defined in ES 282 003 [4]. |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.36 Link_CamelImSsfAs_Upsf | |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.36.1 Definition | This IOC models the Si reference point between ASF Type 2 CAMEL IM-SSF Application Server and UPSF as defined in ES 282 007 [7]. |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.37 Link_Clf_Clf | |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.37.1 Definition | This IOC models the e2 reference point as defined in ES 282 004 [5]. |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.38 Link_Clf_Nacf | |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.38.1 Definition | This IOC models the a2 reference point as defined in ES 282 004 [5]. |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.39 Link_Clf_Pcscf | |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.39.1 Definition | This IOC models the e2 reference point as defined in ES 282 004 [5]. |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.40 Link_Clf_Uaaf | |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.40.1 Definition | This IOC models the a4 reference point as defined in ES 282 004 [5]. |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.41 Link_OsaScsAs_Upsf | |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.41.1 Definition | This IOC models the Sh reference point between ASF Type 2 OSA SCS Application Server and UPSF as defined in ES 282 007 [7]. |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.42 Link_Pcscf_Spdf | |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.42.1 Definition | This IOC models the Gq' reference point as defined in ES 282 003 [4]. ETSI ETSI TS 188 005-2 V2.1.1 (2009-02) 28 |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.43 Link_Pdbf_Uaaf | |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.43.1 Definition | This IOC models the reference point between PDBF and UAAF as defined in ES 282 004 [5]. |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.44 Link_SipAs_Upsf | |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.3.44.1 Definition | This IOC models the Sh reference point between ASF Type 2 SIP Application Server and UPSF as defined in ES 282 007 [7]. |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.4 Information relationship definitions | Void. |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.5 Information attribute definitions | |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.5.1 Definition and legal values | The following table defines the attributes that are present in several information object classes of the present document. Attribute Name Definition Legal Values agcfFunctionId An attribute whose "name+value" can be used as an RDN when naming an instance of the IOC. This RDN uniquely identifies the object instance with... |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.5.2 Constraints | Name Definition - - ETSI ETSI TS 188 005-2 V2.1.1 (2009-02) 30 |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.6 Common notifications | Void. |
9c52842ceb1d62db2a87c77bbbc3cd90 | 188 005-2 | 5.7 Particular information configurations | Not applicable. ETSI ETSI TS 188 005-2 V2.1.1 (2009-02) 31 Annex A (informative): Mapping to 3GPP and TMF SID As noted in the scope, this version the NRM is linked to 3GPP NRM using naming and inheritance, however a need to link the NRM to the TeleManagement Forum's Shared Information Data Model (SID) has been identifi... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 1 Scope | The present document defines the security architecture of NGN Release 1. The definition complies with the requirements of ITU-T Recommendation I.130 [32] at stage 2. The present document addresses the security architecture required to fulfil the NGN R1 security requirements defined in TS 187 001 [1] and includes the de... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 187 001: "Telecommunications and Internet con... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 2.2 Informative references | [48] ETSI TR 182 005: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Organization of user data". [49] ETSI TR 187 002 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); TISPAN NGN Security (NGN-SEC); Threa... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 3 Definitions and abbreviations | |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Authentication Service (AUTH): See ITU-T Recommendation X.811 [34]. Authorization Service (AUTHOR): See ITU-T Recommendation X.812 [35]. Confidentiality Service (CONF): See ITU-T Recommendation X.814 [36]. data: any information conveye... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3G 3rd Generation 3GPP 3rd Generation Partnership Project AAA Authentication, Authorization, Accounting AF Application Functions AGCF Access Gateway Control Function AGW Access GateWay AKA Authentication and Key Agreement AMF Access Management... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 4 NGN Security | This clause provides an overview of the NGN security document. The entire document can be seen as a documented output of a security process that loops through several stages; see figure 1, where arrows indicate logical steps and dependencies. ETSI ETSI TS 187 003 V1.7.1 (2008-02) 12 The present document assumes existen... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 4.1 NGN security architecture | The NGN R1 security architecture basically consists of the following major parts: • NGN security domains (see clause 4.3). • Security services (see clause 5): - authentication; - authorization; - policy enforcement; - key management; - confidentiality; and - integrity. • Security protocols including those contained in:... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 4.2 Security domains | A security domain (see ISO/IEC 10181-1 [30] and ITU-T Recommendation X.810 [33]) is a set of elements under a given security policy administered by a single security authority for some specific security relevant activities. The activities of a security domain involve one or more elements from that domain, however at le... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 4.3 NASS and RACS security architecture | Figure 4 shows a high-level view of the NASS and RACS subsystems as mapped to the five NGN security domains. Visited NGN Network Security Domain Home NGN Network Security Domain UE RACS APPL Access Network Security Domain NASS 3rd party ASP Network Security Domain NASS RACS NASS RACS APPL 3rd party ASP Network Security... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 4.3.1 NASS-IMS Bundled security | Please refer to clause 4.4.1. ETSI ETSI TS 187 003 V1.7.1 (2008-02) 18 |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 4.4 IMS security architecture | The IMS security architecture for both 3G environments and for NGN environments is defined in TS 133 203 [8]. UPSF Home NGN I-CSCF Visited NGN P-CSCF Generic IP Transport soft ISIM NGN-UE MM IP networks S-CSCF 1 2 5 3 3 4/5 4/5 UA GE GE Figure 7: IMS Security architecture in an NGN environment (TS 133 203 [8]) Figure 7... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 4.4.1 NASS-IMS Bundled security | The NASS Bundled Authentication (NBA) works by extending the successful authentication in the NASS layer to the service layer. During the network attachment, the NASS authenticates the UE and allocates an IP address. It stores the layer-2 and layer-3 identities in the NASS profile. When UE registers with the P-CSCF, th... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 4.5 PES Security architecture | |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 4.5.1 Security for H.248 within PES | Figure 11 depicts the security architecture for using H.248.1 for PSTN/ISDN service over IP according to ES 283 002 [20]. Access Gateway (AGW), Residential Gateway (RGW), the control subsystem (AGCF with MGC) and the control protocols are considered to belong entirely to a single operator's security domain as indicated... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 4.5.2 IMS-based PES security | TS 182 012 [41] defines the functional architecture for the IMS-based PSTN/ISDN emulation subsystem. The MGCF maps the encapsulated ISUP information within SIP messages sent/received to/from the BGCF (Mj interface) and to/from the I/S-CSCF (Mg interface) to the ISDN/PSTN network. The MGCF implements the role of a PES I... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 4.6 Application security architecture | The AS architecture enables the user to manage information related to his services, such as creation and assignment of Public Service Identities, management of authorization policies that are used e.g. by Presence service, conference policy management, etc. The XCAP architecture and security architecture is endorsed by... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 5.1 Security services in NGN R1 security architecture | This clause defines the mapping of security services within the NGN R1 security architecture through security functions. Clause 4.2.3 provides a mapping of security services to NGN FEs. The following security services are identified for NGN: • Authentication. • Authorization. • Confidentiality. • Integrity. Tables 1 to... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 5.2 Security Services in NGN FEs | Table 5 identifies the security services with the security mechanism(s) and countermeasures for each NGN FE. NOTE: Security functions of security services may actually be specified in documents that are referenced indirectly only. Table 5: Security services and countermeasures provided by NGN FEs NGN FE Security Servic... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 5.3 Security Services on NGN Interfaces | Table 6 identifies the security services (AUTH, INT, CONF, KMF) with the security mechanism(s) and countermeasures for each NGN interface. NOTE 1: Interfaces are not listed in this clause where no security functions are identified. NOTE 2: Security functions of the security services may actually be specified in documen... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 5.4 Mapping of 3GPP security FEs to NGN FEs | NGN shall re-use 3GPP security entities (AuC, HLR and HSS; see TS 123 002 [46]) as follows; see also figure 13 that illustrates a mapping of 3GPP FEs to NGN FEs: • The PDBF at the NASS level shall conceptually encompass the same functionality that is provided by the AuC, see TS 123 002 [46] clause 4.1.1.1.2. Additional... |
0a98bab50a099f255f6286b5bbf73a67 | 187 003 | 6 NGN IMS Residential Gateway | User may gain access to NGN IMS services by using a non-ISIM capable SIP UA via a NGN IMS Residential Gateway (IRG). NGN IMS Residential Gateway is an optional functional element within the NGN architecture and serves the purpose to securely connect legacy, non-NGN UE equipment to the NGN that does not have the capabil... |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 1 Scope | The present document identifies NGN OSS requirements and consolidates and categorizes them. Annex B contains an unstructured list of requirements as identified and extracted from numerous sources. Annex A contains a list of consolidated requirements. These requirements represent a first analysis of the requirements cap... |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • ... |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 3 Definitions and abbreviations | |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: access network: collection of network entities and interfaces that provides the underlying IP transport connectivity between the device and the NGN entities NOTE: An example of an "Access Network" is ADSL. ETSI ETSI TS 188 003 V1.1.2 (... |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ALC Automatic Level Control CCV Common Communications Vehicle CMIP Common Management Information Protocol CORBA Common Object Request Broker Architecture DSL Digital Subscriber Line ebXML e-business XML ENUM Electronic Number (RFC 2916) IAD In... |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4 Structured requirements | In this clause the unstructured requirements contained in annex A are structured as follows: • At the highest level, the requirements are grouped into Business Vision requirements, Customer Centric requirements, Technology requirements, Operational requirements and Regulatory requirements (level 0). • The more general ... |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.1 Customer Centric requirements | Req Requirement Release 1 Comments A15 Management systems shall be capable of supporting customer segmentation in the 10 000's. A25 Products codes shall not be tied 1 to 1 with specific tariffs. Y 4.1.1 Access to services at any time, any place, through any chosen access mechanism and terminal (user equipment) Req Requ... |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.1.3 Security of personal information | Req Requirement Release 1 Comments A33 Management of the subscription related aspects of the user profile (subscription profile) including ownership of components. Y subscription profile components will be needed for: data related to subscription identification and numbering. E.g. private identity, public identity, reg... |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.1.9 Single Sign On | Req Requirement Release 1 Comments A89 Single sign on |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.1.10 Mobility | Req Requirement Release 1 Comments A5 Management of Mobility Y (see note) Only nomadism required for release 1 (i.e. no support for hand-over of communications sessions between access networks). NOTE: There are significant impacts in the security and personalization aspects of the services. |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.2 Business Vision Requirements | 4.2.1 Support Value Chains of Multiple Service Providers: Multiple Trading Partners with Complex Value Chains and Business Models Req Requirement Release 1 Comments A10 Management of storage distribution of applications and content using Digital Rights. These shall cover access control, user and content owners policy a... |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.2.2 Support for a wide range of services, applications and mechanisms | Req Requirement Release 1 Comments A9 Supporting the management Parlay v 4.0 APIs. A18 Service Detail Records and Product codes need to be managed in the 1 000's. 4.2.3 Support of real time/streaming/non-real time and multimedia services Req Requirement Release 1 Comments A11 Management of end to end VPN solutions. Y A... |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.2.5 Shortened product lifecycle | Req Requirement Release 1 Comments A20 Management processes shall support and automate Product Lifecycle Management. Y |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.3 Technology requirements | |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.3.1 Multi-media services over packet-based transfer | Req Requirement Release 1 Comments A2 Management of end to end connectivity (Transport). Y ETSI ETSI TS 188 003 V1.1.2 (2006-03) 13 |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.3.2 Independence of service-related functions from underlying transport | Req Requirement Release 1 Comments A8 Management of NGN Service Layer entities. Y A82 Integrating an abstracted view on Resources (network, computing and application), which is hiding complexity and multiplicity of technologies and domains in the resource layer. Y |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.3.3 Separation of control functions | Req Requirement Release 1 Comments A4 Management of Session Control, Media Control and Bearer Control. Y |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.3.4 Broadband capabilities | Req Requirement Release 1 Comments A85 Support TISPAN Release 1 Services. Y |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.3.5 Interworking with legacy networks via open interfaces | Req Requirement Release 1 Comments A81 Allowing the management of hybrid networks comprising NGN and non-NGN (e.g. PSTN, cable network) resources. Y |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.3.6 Support of multiple last mile technologies | Req Requirement Release 1 Comments A3 Support of multiple access technologies (including, as a minimum, Integrated access devices (IAD), DSL and WLAN access, gigabit Ethernet metro core networks). Y |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.3.7 Convergence of fixed and mobile, TDM and packet-based services | Req Requirement Release 1 Comments A2 Management of end to end connectivity (Transport). Y ETSI ETSI TS 188 003 V1.1.2 (2006-03) 14 |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.3.8 Support a variety of identification schemes | Req Requirement Release 1 Comments A64 From the unique identifier (E164, ENUM etc.), to be able to trace, where applicable, current: log on name and password; network endpoint IP address and hardware address; terminal (user equipment) IP address and hardware address. And the reverse. To be able to identify the function... |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.3.9 Terminal (user equipment) Management | Req Requirement Release 1 Comments A1 Management of User Equipment (including configuration and downloading of applications and QoS). Y |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.4 Operational requirements | |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.4.1 End-to-end QoS | Req Requirement Release 1 Comments A12 Management of IP QoS across technical sub-domains and between operators. Y Interfaces between operators shall not assume a single end to end technical solution for IP QoS. A13 Support the use of protection mechanisms in the Access, core, metro, backhaul and with OLOs. 4.4.2 Subscr... |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.4.4 Perfect touch and zero fall-out | Req Requirement Release 1 Comments A88 Perfect touch and zero fall-out. |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.4.5 Automated Service Creation processes | Req Requirement Release 1 Comments A19 Management processes shall support flexible, transport technology agnostic, service creation environments. Y A20 Management processes shall support and automate Product Lifecycle Management. Y A28 The service creation process shall support the creation of (software) components who... |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.4.6 Management of NGN resources (physical and logical) | Req Requirement Release 1 Comments A41 To claim to be NGN compliant management interfaces shall be open and use industry standard solutions. Y A55 To be able to discover the current policy decision and policy enforcement points for a given access segment/given customer. Y A56 To be able to validate the current policy e... |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.5 Regulatory requirements | |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.5.1 Emergency communications | Req Requirement Release 1 Categorized in paragraph Comments A14 Support national emergency services and international Emergency Telecommunications Services. 4.5.1 |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.5.2 Security | Req Requirement Release 1 Comments A5 Management of Mobility. Y (see note) Only nomadism required for release 1 (i.e. no support for hand-over of communications sessions between access networks). A21 Management processes shall support the User Access control and trust Processes. Y A42 Access to customer information sha... |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.5.3 Privacy | Req Requirement Release 1 Comments A17 Processes for distribution and synchronization of User Profile information shall enforce policies set by regulation, applicable data protection laws, users and operators. Y A39 Interfaces between trading partners shall meet the commercial and legal standards required for the busin... |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.5.4 Lawful interception | Req Requirement Release 1 Comments A86 Lawful interception. Y ETSI ETSI TS 188 003 V1.1.2 (2006-03) 19 |
1cf49c4f9f97334122e3126a02a4f904 | 188 003 | 4.5.5 Unrestricted access by users to different service providers | Req Requirement Release 1 Comments A87 Unrestricted access by users to different service providers. Y ETSI ETSI TS 188 003 V1.1.2 (2006-03) 20 Annex A (normative): Unordered List of Consolidated NGN Management Requirements This annex provides a single unordered list of numbered consolidated requirements. This list is t... |
102966fe8d7c74cf46752c05d8b3d701 | 188 002-3 | 1 Scope | The purpose of the SuM Functional Architecture is the design of the NGN OSS Service Interfaces (NOSIs) needed for the management of a specific Subscriber, User, Service Profile and User Services within TISPAN NGN. The SuM Functional Architecture shall deliver the necessary NOSIs for the Resource Provisioning and Servic... |
102966fe8d7c74cf46752c05d8b3d701 | 188 002-3 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
102966fe8d7c74cf46752c05d8b3d701 | 188 002-3 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 188 001: "Telecommunications and Internet Con... |
102966fe8d7c74cf46752c05d8b3d701 | 188 002-3 | 2.2 Informative references | [11] ETSI TS 132 101: "Universal Mobile Telecommunications System (UMTS); Telecommunication management; Principles and high level requirements (3GPP TS 32.101)". [12] ETSI TS 132 150: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunication management;... |
102966fe8d7c74cf46752c05d8b3d701 | 188 002-3 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AS Application Server CLF Connectivity session Location and repository Function GUP Generic User Profile IOC Information Object Class IRP Integration Reference Point IS Information Service NASS Network Attachment SubSystem NGN FE NGN Functiona... |
102966fe8d7c74cf46752c05d8b3d701 | 188 002-3 | 4 SuM Functional Architecture | |
102966fe8d7c74cf46752c05d8b3d701 | 188 002-3 | 4.1 Overview | Subscription Management is paramount for the NGN service delivery within TISPAN NGN. It aims to define an end- to-end information model and a functional architecture that allows service providers to provision their NGN functional entities with all the mandatory/optional information specific to a subscriber and its user... |
102966fe8d7c74cf46752c05d8b3d701 | 188 002-3 | 4.2 Service Configuration and Activation | For the specification of the SCA NOSIs, it is necessary to list all the required capabilities that need to be supported or offered by the NOSIs with respect to SuM requirements, eTOM and to the use cases defined in [2]. There is no assumption on the relations between the required capabilities and the NOSIs that support... |
102966fe8d7c74cf46752c05d8b3d701 | 188 002-3 | 4.3 Resource Provisioning | This clause consists in a description of all the capabilities required for SuM within the Resource Provisioning process group with respect to the Subscription Management Requirements and to eTOM. For the specification of the RP NOSIs, it is necessary to list all the required capabilities that need to be supported or of... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.