hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
819f32b0ea5df47c17e5f4c41f79b63d | 103 427 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
819f32b0ea5df47c17e5f4c41f79b63d | 103 427 | 3 Definition of terms, symbols and abbreviations | |
819f32b0ea5df47c17e5f4c41f79b63d | 103 427 | 3.1 Terms | For the purposes of the present document, the terms given in Recommendation ITU-T Q.3960 [1] apply. |
819f32b0ea5df47c17e5f4c41f79b63d | 103 427 | 3.2 Symbols | Void. |
819f32b0ea5df47c17e5f4c41f79b63d | 103 427 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in Recommendation ITU-T Q.3960 [1] apply. ETSI ETSI TS 103 427 V1.1.1 (2019-11) 6 |
819f32b0ea5df47c17e5f4c41f79b63d | 103 427 | 4 Endorsement notice | All elements of Recommendation ITU-T Q.3960 [1] apply. Recommendation ITU-T Q.3960 [1] is contained in archive ts_103427v010101p0.zip which accompanies the present document. ETSI ETSI TS 103 427 V1.1.1 (2019-11) 7 History Document history V1.1.1 November 2019 Publication |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 1 Scope | The present document presents SAREF4EHAW, an extension of SAREF for the eHealth/Ageing-well Domain. |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 2 References | |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 3 Definition of terms, symbols and abbreviations | |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 3.1 Terms | For the purposes of the present document, the following terms apply: ontology: formal specification of a conceptualization, used to explicit capture the semantics of a certain reality |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 3.2 Symbols | Void. |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: aECG annotated ECG API Application Programming Interface BAN Body Area Network DICOM Digital Imaging and Communications in Medicine EC European Commission ECG ElectroCardioGram EHAW eHealth and Ageing Well EHR Electronic Health Record ETSI Eur... |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 4 SAREF4EHAW ontology and semantics | |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 4.1 Introduction and overview | The objective of SAREF4EHAW is to extend SAREF ontology (see ETSI TS 103 264 [1]) for the eHealth/Ageing-well (EHAW) vertical. Clause 4.1 of the present document shortly introduces a high level view of the envisioned SAREF4EHAW semantic model and modular ontology, with the retained concepts (i.e. classes) and their rel... |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 4.2 SAREF4EHAW | |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 4.2.1 Introduction | As already introduced in clause 4.1 of the present document SAREF4EHAW is an OWL-DL ontology and shall be designed using the modularity principle (see ETSI TR 103 509 [i.7]) and can thus be mainly described by the following self-contained knowledge modules: • HealthActor module that models eHealth system actors, i.e. c... |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 4.2.2 HealthActor module | A detailed view of SAREF4EHAW HealthActor module is depicted in Figure 2. ETSI ETSI TS 103 410-8 V2.1.1 (2024-09) 12 Figure 2: Detailed view of SAREF4EHAW HealthActor module ETSI ETSI TS 103 410-8 V2.1.1 (2024-09) 13 SAREF4EHAW HealthActor module models the eHealth system actors, i.e. responsible parties (the legal ent... |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 4.2.3 Ban module | A detailed view of SAREF4EHAW Ban module is depicted in Figure 3. ETSI ETSI TS 103 410-8 V2.1.1 (2024-09) 14 Figure 3: Detailed view of SAREF4EHAW Ban module ETSI ETSI TS 103 410-8 V2.1.1 (2024-09) 15 A BAN (Ban class depicted in Figure 3) is mainly used for collecting, aggregating and relaying patient or user vital pa... |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 4.2.4 HealthDevice module | A detailed view of SAREF4EHAW HealthDevice module is depicted in Figure 4. ETSI ETSI TS 103 410-8 V2.1.1 (2024-09) 16 Figure 4: Detailed view of SAREF4EHAW HealthDevice module ETSI ETSI TS 103 410-8 V2.1.1 (2024-09) 17 As depicted in Figure 4, an HealthDevice is a sub-class of SAREF Device class (rdfs:subClassOf relati... |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 4.2.5 FunctionalDevice module | FunctionalDevice are non-purely eHealth/ageing-well devices that can be used for modelling/detecting activities or behaviours of patients/users, like for example beacons that can detect indoor positioning of a patient in a house. A functional device is a sub-class of SAREF Device class (rdfs:subClassOf relation) and sh... |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 4.2.6 Function module | A detailed view of SAREF4EHAW Function module is depicted in Figure 5. ETSI ETSI TS 103 410-8 V2.1.1 (2024-09) 18 Figure 5: Detailed view of SAREF4EHAW Function module SAREF4EHAW Function module models the observation and actuation functions (see Figure 5). As shown in Figure 5, a function has: • Command (e.g. an actua... |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 4.3 Instantiating SAREF4EHAW | 4.3.1 Monitoring and support of healthy lifestyles for citizens, in the context of Covid-19 This use case is about a patient of around 50 years old, Bob, with overeating habit. In the context of Covid-19, Bob as a risky patient is thus remotely followed/monitored/controlled by a caregiver, Dr. Knock, for Covid-19 signs... |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 4.3.2 Early Warning System (EWS) for Cardiovascular Accidents | This example describes how a cardiovascular Early Warning System (EWS) instantiates SAREF4EHAW. In this use case, the EWS collects data from an e-Health solution that allows monitoring the ECG data of a person (the patient) using the device. The chosen ECG solution for this example includes the Shimmer3 ECG, which is a... |
4e734a491e698561b521f3b5ed2400a3 | 103 410-8 | 4.4 Discussion | In the following, several observations about the SAREF4EHAW ontology and its usage are mentioned. The hierarchies and individuals defined for SAREF4EHAW extension in the present document should not be considered as exhaustive. It might be needed to extend the hierarchies and lists of individuals for particular use case... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 1 Scope and purpose of the present document | The use of Wireless Home Area Networks (WHANs) will expand with the advent of Smart Home services to enable energy management, home automation etc. In many scenarios it is appropriate to use a smart home gateway (HG) to connect the devices and various systems in the house (e.g. lighting, thermostats; heating systems an... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 2 References | |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 3 Definitions, symbols and abbreviations | |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Cloud: network of remote servers hosted on the Internet and used to store, manage, and process data in place of local servers or personal computers Coordinator: device in a WHAN, which (a) converts any commands (or requests for data) f... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 3.2 Abbreviations | HG Home Gateway HGI Home Gateway Initiative WHAN Wireless Home Area Network(s) ETSI ETSI TS 103 425 V1.1.1 (2016-11) 7 |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 4 Purpose of the present document | |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 4.1 Rationale | Network providers (i.e. telecommunication carriers) have begun developing and deploying Smart Home services. To realize these services, it is useful to work with other industry players such as device manufacturers, service providers and platform operators to develop communities of interest and construct ecosystems for ... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 4.2 Problem statement | Wireless in-home connectivity is an essential element in providing Smart Home services; installing new wiring just for a Smart Home service is usually unacceptable being difficult, costly and aesthetically displeasing. However, although there are many types of wireless technologies available, none can currently satisfy... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 4.3 Benefits for the industry | The current status of WHAN technologies is hampering the development of the Smart Home market. The lack of a ubiquitous, plug and play wireless technology is a major barrier to mass-market adoption of Smart Home services. None of the operational entities [i.3], from service provider to user, can be sure which technolog... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 4.4 Roles and responsibilities | The manufacturer produces equipment for the home, such as sensors, actuators, smart appliances, and other sub-systems (alarm, home automation), and smart HGs. The manufacturer integrates the chipset, software stack, and the application programming interfaces. In some cases, they may also directly produce devices. Some ... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 5 Key WHAN attributes | |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 5.1 Installation and configuration of devices | One of the most important elements in driving widespread deployment of user-friendly Smart Home services is that installation and configuration of the WHAN should be very easy. With wireless networks, it is potentially easy to eavesdrop or to spoof, so "man in the middle attacks" shall be prevented especially during th... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 5.2 WHAN performance | |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 5.2.1 Reliable wireless communication | To provide reliable service over the WHAN, service providers need to consider issues affecting wireless performance, such as radio interference and coverage, and also ensure that the WHAN does not send data to the wrong device (e.g. switch on/off the wrong light, or connect to devices in a neighbour's apartment). For e... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 5.2.2 Management, configuration and maintenance | To provide services via the WHAN, it may be necessary for all the interested parties (i.e. the service customer, service provider and platform operator - hereinafter "all parties"), to have some management visibility and/or control, however the well-known problem of multiple management entities with regard to conflicti... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 5.3 Network Security | Wireless networks are vulnerable to eavesdropping and spoofing. Therefore the WHAN shall support security functions to protect sensitive data such as billing related information. This means that the WHAN has to authenticate all devices, protect data integrity and privacy (e.g. by encryption) and provide protection agai... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 6 Functional and technical requirements | |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 6.1 Installation and configuration of devices | Table 1 N° Requirement R7.1.1 Interoperability WHAN devices carrying the same certification logo or technology logo SHALL be interoperable regardless of the vendor or manufacturer. R7.1.2 Certification The platform operator or service provider SHALL specify, in a format accessible to the service customer the type of WH... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 6.2 Reliable performance | Table 2 N° Requirement R7.2.1 Minimization of interference with other radio systems The WHAN SHALL minimize the impact of interference from other systems. The WHAN SHALL minimize the generation of potential interference to other radio systems. R7.2.2 Channel selection The WHAN technology SHALL be able to be used in env... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 6.3 Management and maintenance of devices | Table 3 N° Requirement R7.3.1 Device management The WHAN SHALL support the reporting of all devices associated with a given network. This information SHALL be available to the management software running on the HG. R7.3.2 Hardware ID Each WHAN device SHALL have a hardware-ID which is globally unique for a given technol... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 6.4 Connectivity Management | Table 4 N° Requirement R7.4.1 Connectivity management Where a WHAN supports meshing, it SHALL also support direct management of routes between devices (i.e. override automatically selected routing). The coordinator and permanently powered devices SHALL support periodic checking of their connectivity. For devices that d... |
eb89d4698eb35e53446f6b4414ae323f | 103 425 | 6.5 Proven security | Table 5 N° Requirement R7.5.1 Freshness Any WHAN technology devices designed for use in a security related application SHALL provide protection against delay attacks. R7.5.2 Integrity The WHAN SHALL guarantee the integrity of data packets R7.5.3 Authentication The WHAN SHALL NOT allow communication with unauthorized de... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 1 Scope | The rapid increase in the number of smart devices in the home, from entertainment systems to appliances and medical devices and the now near ubiquitous broadband connectivity have created a significant new potential market for service providers. However, in order to exploit this market and provide an integrated custome... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 2 References | |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 3 Definitions, symbols and abbreviations | |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in Open Platform 2.0 [i.1] and the following apply: action: A function that can be executed by an appliance. appliance: A domestic electrical/mechanical machine which accomplishes some function used in smart home services. data point: A property ... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAL Ambient Assisted Living NOTE: Home automation to assist aged/infirm persons. API Application Program Interface CPE Consumer Premises Equipment CWMP CPE WAN Management Protocol DAL Device Abstraction Layer HAN Home Area Network HG Home Gate... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 3.3 Relationship with other HGI Specifications | The present document contains requirements over and above those in the HGI Residential Profile [i.6], Open Platform 2.0 [i.5] and Wireless HAN Services [i.2]. All the requirements of those documents still apply, except that support of Open Platform 2.0 is only mandatory with regard to clause 5.3 "HG with specific Softw... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 4 Business requirements and Use Cases | The business requirements and use cases used as the basis for the architecture described in the present document are described in [i.4]. |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 5 Architecture | The architecture is described first in terms of the entities and interfaces of the smart home eco-system and then in terms of the software execution environment within the HG. There is a particular focus on the Device Abstraction Layer (DAL) which mediates between high-level applications and the specific local area net... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 6 Overview | In the HGI context, the Home Gateway is considered to be the heart of the smart home - it connects and controls the home appliances and serves as the main entry point for communication with the operators, service providers and utilities in the cloud. The end user has access to their services in the home either via the ... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 6.1 High-level view of smart home architecture | Figure 2 shows a schematic view of the high level entities and reference points of the HGI smart home architecture. This Figure depicts the smart home functions as a black box, deferring the discussion of the way in which remote requests from WAN or LAN side clients are translated to actions on smart home appliances. O... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 7.1 Detailed HG software stack architecture | A more detailed view of the HG shows the software modules within the smart home software, including the reference points RP1, RP2 and RP8. The general requirements on the HG software stack (modularity, rights management, etc.) are explained in ETSI TS 103 426 [i.1]. HOME NETWORK WAN HG Software Stack Smart Home Softwar... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 7.2 Access Control and Policies | Applications' access to appliance software interfaces and therefore implicitly the user's access, may need to be controlled, but this shall not limit physical user access in the home (e.g. via a wall switch). Additionally access control provides a way to manage concurrent access to the same appliance. The implementatio... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 7.3 Appliance States | The following section describes the possible states of the internal representation of appliances in the DAL. When an appliance is initially detected by a HAN controller or on an IP interface, the DAL generates a notification at RP1 and (usually) the appliance transitions by means of a pairing/configuration process to t... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 7.4 Grouping of Appliances | HGI members found that there are various common approaches to the grouping of appliances. For example: • A number of separate "smart" lamps might be considered as a group, to be switched on/off together. • The "on" state of (any) lamps in a house might be considered as a single input for a burglar detection system. • I... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 8 Functional requirements | The following sections contain functional requirements for the different reference points of the system. |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 8.1 Requirements for RP1 Device Abstraction Layer | NOTE: All occurrences of "appliance" in table 9 also include "virtual appliance". Table 9 N° Requirement ARCH1. a The API at RP1 SHALL support all the mandatory requirements in [i.9] "HG and Home Network Diagnostics" clause 8.12 Device Discovery, §8.14 Topology Discovery, clause 8.15 Connectivity Testing ARCH2. The API... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 8.2 Requirements for RP1 Access Control | Table 10 N° Requirement ARCH14. RP1 SHALL support appliance access control. ARCH15. Access control SHALL be able to be invoked per application. ARCH16. The same access control policy SHOULD be able to be applied to a specified list of applications. ARCH17. Access control for a given application SHALL be able to be invo... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 8.3 Requirements for DAL | Table 11 N° Requirement ARCH19. The DAL SHALL be able to support additional HAN technologies without changes to the API at RP1 and SHOULD NOT • require a complete reboot • interrupt services e.g. a burglar alarm service while doing so. ARCH20. Changes to the DAL SHOULD NOT • require a complete reboot • interrupt servic... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 8.4 Requirements for RP2 Appliance Driver Interface | Note that the present document does not consider specific requirements for the profiling of particular HAN protocols, so that they can be integrated on the HG. Examples of such detailed requirements would be the minimum level of security that the protocol has to support, or a specific function that is required for the ... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 8.5 Requirements for RP4 Remote Representation | Table 13 N° Requirement ARCH30. RP4 SHALL support the remote command and control of smart home appliances. ARCH31. RP4 SHALL support the remote reading and writing of appliance data points. ARCH32. RP4 SHALL support subscribing, unsubscribing to and forwarding of "data point change" and "change of state" event notifica... |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 8.6 Requirements for RP5 Local representation of appliances | Requirements for the RP5 interface are out of scope of the current version of the present document. |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 8.7 Requirements for RP6 Native Driver Interface | The requirements for this interface are out of scope for the current version of the present document. |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 8.8 Requirements for RP7 Reference point in the cloud | The specific requirements for this interface are out of scope for the current version of the present document. |
95bab7221c0cdeb1a635ffe9e50678d6 | 103 424 | 8.9 Requirements for RP8 WAN Network Connectivity Interface | The specific requirements for the RP8 interface may be elaborated in a future version of the present document. Here it is sufficient to note that, if the broadband WAN access is cellular then HG smart home applications may need to detect which cellular network characteristics apply, e.g. whether data goes via GSM or 4G... |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 1 Scope | The present document presents the engineering and operational requirements for the application of the IPv6 transition technology NAT64 as defined by ETSI TS 101 569-1 [1] (IPv6 Transition Requirements) implemented within an integrated broadband cable network end to end across its network domains. The present document i... |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 2 References | |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 3 Definitions and abbreviations | |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: 4in6: encapsulation of IPv4 packets within IPv6 packet format NAT44: network address translation from an IPv4 address to another IPv4 address P Router: label switching router acting as a transit router in the core network of an MPLS ne... |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 6PE IPv6 Provider Edge 6RD IPv6 Rapid Deployment 6VPE IPv6 VPN Provider Edge AAA Authentication, Authorization and Accounting AAAA Quad-A Resource Record ALG Application Layer Gateway ALTS Application-Level Transport Service AMPS Amplifiers AS... |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 4 General Considerations | |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 4.1 Background | The present document is part of a multi-part series specifying requirements to engineer and operate the NAT64 transition technology end to end across a cable operator's network. Its implementation would ensure the network provider can continue to provide business continuity throughout the depletion of publicly routable... |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 4.2 General Overview | The present document uses network address translation IPv6 to IPv4 (NAT64) technology to provide a seamless internet experience to users accessing IPv4 internet services from an IPv6 only client through a cable network enabling service providers to transparently deliver and enable new and existing services to IPv6 inte... |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 4.3 Vendor Considerations | Generally there are many equipment manufacturers (vendors) in the market place delivering NAT64 as it is used heavily in the mobile market. However, its utilization in the MSO market has been limited even in the cable operators MVNO arena. NAT64 within a cable network requires the engineering of several ALGs to functio... |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 5 Gap Analysis | |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 5.1 Consideration | The engineering and operational requirements applying ETSI TS 101 569-1 [1] need to be specified with the following design objective to define the logical and physical parameters to allow for IPv6 customers to access IPv4 services across the public IPv6 internet network using NAT64. NAT64 is to be deployed such that it... |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 5.2 Overview | There are two main methodologies within NAT64, stateful and stateless, explained below. The cable operators internal requirements would govern which option they decide to deploy. In a stateful NAT64 configuration, an LSN shall be configured as a NAT64 gateway, engineered to enable IPv6-only clients and IPv4 resources t... |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 6 Domain Functionality | |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 6.1 End to End Network Domains | In order to operate the IPv6 transition technology it has to be engineered and verified end to end across the cable broadband network addressing each of the domains as illustrated in figure 2. ETSI ETSI TS 103 443-2 V1.1.1 (2016-08) 14 Figure 2: Illustration of the Cable Broadband Network Domains |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 6.2 CPE Home Network Domain | Customer's devices shall be V6 only, and customer device that is V4 is not supported with this technology. Functionality to be engineered in the cable network: • The cable residential gateway device shall be capable of IPv6 connectivity only. • The DOCSIS management between the Cable Modem and CMTS may be IPv4 or IPv6. |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 6.3 Access Network Domain | Functionality to be engineered in the cable network: • The cable headend CMTS shall be capable of IPv6 connectivity for customer traffic. • The DOCSIS management between the Cable Modem and CMTS may be IPv4 or IPv6. NOTE: There are no additional requirements on the HFC distribution network i.e. AMPS, taps, etc. |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 6.4 Core Network Domain | Functionality to be engineered in the cable network: • The core network routers shall support IPv6 routing and forwarding capabilities. • NAT64 gateway shall be implemented as specified by IETF RFC 6146 [19] for further information on its operation refer also to IETF RFC 7269 [20]. ETSI ETSI TS 103 443-2 V1.1.1 (2016-0... |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 6.5 Data Centre Domain | Functionality to be engineered in the cable network: • The DNS64 shall be implemented when operating IPv6 transition technology NAT64. The requirements for DNS64 shall be in accordance with IETF RFC 6147 [18]. • The DSN64 functionality replaces the exiting DNS caching server within the cable network. Operation: For an ... |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 6.6 DMZ Service Domain | Functionality to be engineered in the cable network: • There are no specific operational requirements for the DMZ however it is strongly recommended that all services within the DMZ are IPv6 capable either by dual stack configuration or the use of V6/V4 load balancing. • V6/V4 load balancers allow V6 access to existing... |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 6.7 Transit and Peering Service Domain | Functionality to be engineered in the cable network: There are no changes to be engineered when considering the transit and peering domain since the transmit and peering links are dual stack and support both IPv6 and IPv4 packets simultaneously and therefore no specific additional requirements are needed to be defined ... |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 6.8 Management and Monitoring Domain | Functionality to be engineered in the cable network: • DOCSIS management between the CMTS and Cable Modem may remain deployed either using IPv4 or IPv6 addresses. • There is the additional functionality to monitor and manage the NAT64 gateway and DNS64 server in order to provide sufficient capacity to scale with the tr... |
c544ddd04169ee8321a7fa755c943122 | 103 443-2 | 6.9 Security Domain | Functionality to be engineered in the cable network: • The cable modem packet classifiers shall be updated to support IPv6 filtering. • The continuity of the security of the end to end service shall be maintained when operating NAT64, however the operational implications from NAT64 shall be minimized as specified in IE... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.