Dataset Viewer
text
stringlengths 15
6.68k
|
|---|
application rules and requirements: rules and requirements associated to MEC applications, such as required resources, maximum latency, required or useful services, traffic rules, DNS rules, mobility support, etc. B Void. C client application: application software running on a device e. g. UE, laptop with internet connectivity in order to utilize functionality provided by one or more specific MEC application s content provider: entity e. g. a web server, or a content distribution network that provides content to consumers D device application: application running in the device that has the capability to interact with the MEC system via the user application lifecycle management proxy E H Void. I infrastructure provider: entity that provides components into the network infrastructure ranging from compute elements and or platforms to a software component i. e. software component examples include security, virtualisation, controller, etc. J K Void.<|end_of_text|>
|
L lawful interception: action based on the law , performed by a network operator service provider access provider, of making available certain information and providing that information to a law enforcement monitoring facility lifecycle management: set of functions required to manage the instantiation, maintenance and termination of a MEC application instance M MEC application: virtualised software application that can be instantiated and run on virtualisation infrastructure of the MEC system and can potentially provide and or consume MEC services MEC federation: federated model of MEC systems enabling shared usage of MEC services and applications MEC host: entity that contains a MEC platform and a virtualisation infrastructure which provides compute, storage and network resources to MEC applications MEC host level management: components which handle the management of the MEC specific functionality of a particular MEC platform, MEC host and the MEC applications running on it MEC management: MEC system level management and MEC host level management MEC platform: collection of functionality that is required to run MEC applications on a specific MEC host virtualisation infrastructure and to enable them to provide and consume MEC services, and that can provide itself a number of MEC services.<|end_of_text|>
|
<|end_of_text|>
|
MEC service: service provided via the MEC platform either by the MEC platform itself or by a MEC application MEC system: collection of MEC hosts and MEC management necessary to run MEC applications MEC system level management: management components which have the overview of the complete MEC system mobile edge application: MEC application that can be instantiated on a mobile edge host within the mobile edge system and can potentially provide or consume mobile edge services mobile edge host: MEC host that contains a mobile edge platform and a virtualisation infrastructure which provides compute, storage and network resources to mobile edge applications mobile edge host level management: components which handle the management of the mobile edge specific functionality of a particular mobile edge platform, mobile edge host and the mobile edge applications running on it mobile edge management: mobile edge system level management and mobile edge host level management mobile edge platform: MEC platform to run mobile edge applications on a specific mobile edge host virtualisation infrastructure and to enable them to provide and consume mobile edge services, and that can provide itself a number of mobile edge services mobile edge service: MEC service provided via the mobile edge platform either by the mobile edge platform itself or by a mobile edge application mobile edge system: special kind of MEC system that is a collection of mobile edge hosts and mobile edge management necessary to run mobile edge applications within an operator network or a subset of an operator network mobile edge system level management: management components which have the overview of the complete mobile edge system Multi access Edge Computing MEC : system which provides an IT service environment and cloud computing capabilities at the edge of an access network which contains one or more type of access technology, and in close proximity to its users N Network Functions Virtualisation NFV : principle of separating network functions from the hardware they run on by using virtual hardware abstraction, as defined in ETSI GR NFV 003 i.<|end_of_text|>
|
1 network operator: entity that provides a network for the provision of telecommunications services NOTE: If the same entity also offers services it also becomes the service provider. O Q Void. R resource: object with a type, associated data, a set of methods that operate on it, and, if applicable, relationships to other resources NOTE: A resource is a fundamental concept in a RESTful API. Resources are acted upon by the RESTful API using the Methods e. g. POST, GET, PUT, DELETE, etc. . Operations on Resources affect the state of the corresponding managed entities. retained data: set of data elements for a specific subscriber user related to a specific service transaction S service provider: entity providing a service to the end user.<|end_of_text|>
|
T Void. U user application: MEC application that is instantiated in the MEC system in response to a request from a user via a device application user context: application specific runtime data maintained by the MEC application, which is associated with a user of that application User Equipment UE : mobile equipment used to access the operator's mobile network and supporting applications that transmit IP packets over the mobile network NOTE: User Equipment is originally defined in ETSI TS 123 002 i. 2 . For the purpose of the present document, the definition above is used instead. V virtualised resource: compute, storage or network resource provided by the virtualisation infrastructure to a mobile edge application W Z Void. 3. 2 Symbols Void. 3. 3 Abbreviations 0 9 3GPP 3rd Generation Partnership Project 4G 4th Generation 5G 5th Generation 5GS 5G System A F ACK ack ACKnowledgement API Application Programming Interface App app Application application CAPEX CAPital EXpenditure CAPIF Common API Framework for 3GPP northbound APIs CCF CAPIF Core Function DNS Domain Name System E UTRA Evolved Universal Terrestrial Radio Access EPS Evolved Packet System FTP File Transfer Protocol FQDN Fully Qualified Domain Name G GPRS General Packet Radio Service.<|end_of_text|>
|
GR Group Report GRE Generic Routing Encapsulation GS Group Specification GSM Global System for Mobile communications GSMA GSM Association GTP GPRS Tunnelling Protocol GTP U GPRS Tunnelling Protocol User plane GW Gateway H J HTTP Hyper Text Transfer Protocol HTTPS HTTP over TLS IETF Internet Engineering Task Force IP Internet Protocol ISG Industry Specification Group IT Information Technology JSON JavaScript Object Notation K KPI Key Performance Indicator L LAN Local Area Network LCM Life Cycle Management LTE Long Term Evolution M MAC Media Access Control MANO Management And Orchestration MEAO MEC Application Orchestrator MEC Multi access Edge Computing MEF MEC Federator MEFB MEC Federation Broker MEFM MEC Federation Manager MEO MEC Orchestrator MEP MEC Platform MEPM MEC Platform Manager MEPM V MEC Platform Manager NFV MNO Mobile Network Operator MQTT Message Queue Telemetry Transport N NFV Network Functions Virtualisation NFVI Network Functions Virtualisation Infrastructure NFVO Network Functions Virtualisation Orchestrator NGMN Next Generation Mobile Network NR New Radio NS Network Service NSD Network Service Descriptor O Q OEM Original Equipment Manufacturer OSS Operations Support System.<|end_of_text|>
|
PLMN Public Land Mobile Network QCI Quality Class Indicator QoE Quality of Experience QoS Quality of Service R RAN Radio Access Network reconfig reconfiguration ref reference req request REST REpresentational State Transfer RFC Request For Comments RNI Radio Network Information RNIS Radio Network Information Service RPC Remote Procedure Call S T TCP Transmission Control Protocol TLS Transport Layer Security U UE User Equipment UMTS Universal Mobile Telecommunications System UP User Plane UPF User Plane Function URI Uniform Resource Indicator or Uniform Resource Identifier or Universal Resource Identifier UTC Coordinated Universal Time V V2X Vehicle to Everything VIM Virtualised Infrastructure Manager VM Virtual Machine VNF Virtualised Network Function VNFM Virtualised Network Function Manager W Z WLAN Wireless LAN XML eXtensible Markup Language.<|end_of_text|>
|
Annex A: Change History Date Version Information about changes July 2021 3. 0. 1 Base line for phase 3 August 2021 3. 0. 2 MEC 21 000363 MEC001 add some term definitions MEC 21 000365 MEC001 add some abbreviations October 2021 3. 0. 3 MEC 21 000483 MEC001 prepare for stable MEC 21 000490r1 MEC001 capturing short expressions as abbreviations MEC 21 000498 MEC001 postpone abbreviations for federation MEC 21 000502 MEC001 update to the abbreviations November 2021 3. 0. 4 Final for publication as 3. 1. 1 January 2022 3. 1. 2 Base line for v3. 2. 1 January 2022 3. 1. 3 MEC 22 000024 MEC001 restore abbreviations for federation MEC 22 000025r1 MEC001 add missing terms for consistency MEC 22 000030r1 MEC 001 MEC application definition November 2023 3. 1. 4 MEC 23 000366r1 MEC001 addition of new abbreviations MEC 23 000438 MEC001 add abbreviations from contribution 399r1 December 2023 3. 1. 5 Cleanup by EditHelp Removed Editor's note reminding on MEC040 terms Final for MEC Remote Consensus RC review January 2024 3. 1. 6 Final v3. 1. 6 is similar to v3. 1. 5 and is submitted to MEC RC for approval, as there were no comments during the RC for review.<|end_of_text|>
|
3GPP TS 22. 226 version 18. 0. 1 Release 18 10 3GPP TR 21. 905: Vocabulary for 3GPP Specifications . 3 Definitions and abbreviations 3. 1 Definitions Total Conversation: A service offering standardised simultaneous text, video and voice conversation or a subset thereof. Host environment : The session environment where the text component is added. E. g. Circuit switched voice, IP Multimedia etc. Text Conversation: A real time conversation in text with transmission character by character as entered. Further definitions are listed in 3GPP TR 21. 905 10 . 3. 2 Abbreviations For the purposes of this document the following abbreviations apply: EDT European Deaf Telephone GTT Global Text Telephony; The feature that adds real time text conversation to any 3GPP conversational environment GTTFE Global Text Telephony Feature Environment The network components and functions forming GTT TTY Here used as the term for the text telephone type dominating in USA. DTMF Here used as a term for the text telephone type used in Holland, using DTMF tones. VCO Voice Carry Over: Alternating or parallel sending of Speech and receiving Text HCO Hear Carry Over: Alternating or parallel receiving Speech and transmission of Text FCC Federal Communications Commission of United States of America PER Printable character Error Rate MMI Man Machine Interface SIM Subscriber Identification Module ITU International Telecom Standardisation Union GSM Global System for Mobile communication 3GPP Third Generation Partnership Project CS Circuit Switched IP Internet Protocols Further abbreviations are listed in TR 21. 905 10 .<|end_of_text|>
|
4 High level Requirements The following list gives the high level requirements of the GTT. These are requirements which are independent of the user s perception of the feature: Service definition Global Text shall provide a real time conversational text feature. A general definition is found in Recommendation ITU T F. 700 5 . Global Text Telephony host environments A standardised method for Global Text Telephony shall at least be specified for each host environment in the mobile networks that can carry voice. Standards compliant and forward compatible text conversation.<|end_of_text|>
|
3GPP TS 22. 226 version 18. 0. 1 Release 18 Global Text Telephone mechanisms shall provide the capability to support current and evolving text telephony and text conversation features by re using existing standards as far as possible and proposing extensions as necessary to existing standards i. e. the global text telephony feature shall support the evolution of Total Conversation technologies in all networks . Consistent text conversation Regardless of the selected host environment, the far end terminal, the interworking facilities involved, GTT shall be capable of providing a consistent way of handling the conversation. Global Text Telephone access Within the capabilities of networks and terminals, the user shall be provided consistent access to the GTT regardless of the access point. For example: the user shall be capable of accessing the text conversation features through a number of different access points, including networks based on 3GPP specifications, access through dedicated multimedia terminals, and access through combinations of mobile phones combined with text user interface devices. Interoperability Global Text Telephony shall support interoperability with existing and emerging text telephone systems and text conversation features. Global Text Telephony shall support a minimum set of environments where text conversation is supported to ensure full interoperability between different terminals and networks. Emergency calls The implementation of Global Text Telephony shall enable a user to make emergency calls to, and receive calls from, an emergency call centre via a text telephony device used in conjunction with GTT enabled user equipment.<|end_of_text|>
|
5 General Requirements Network operators have many differing requirements, and GTT shall be supported in the network in a manner which allows network operators to consider different configurations depending on their network and commercial requirements. Thus, an identified set of functionalities and protocols shall be standardised to ensure interoperability across networks and terminals to support GTT. The following general requirements shall be supported. 5. 1 Text conversation host environments The protocol environments for text conversation shall be the same as the ones used for other multimedia conversation calls and voice calls. The selected environment for a session is called the host environment. Supported host environments are: Packet switched multimedia Circuit switched multimedia. The text conversation carried by an data transmission procedure, possible to combine with a voice session. Circuit switched voice telephony, with the text conversation carried in band in the voice channel. 5. 2 Text conversation management It shall be possible to allow GTT use without GTT specific subscription.<|end_of_text|>
|
3GPP TS 22. 226 version 18. 0. 1 Release 18 Note: There is no requirement for GTT feature specific subscription, but for normal GTT calls a subscription for telephony is required. For emergency GTT call no subscription of any kind is required. Session start up delay and loss of initial characters should be minimised as far as practicably possible. The text transport method should remain transparent to the network, unless specific functionality is required to provide a satisfactory quality of service. 5. 3 Registration of text conversation capabilities The availability of text conversation capabilities in the user terminal may need to be communicated to the network at call establishment in order to access the GTT service. However, a user is expected to be able to access the GTT service without explicit GTT registration with the operator. 5. 4 Session control The session control call control functions shall use the same procedures as the selected host environment. Additional operations needed to invoke the text component may be automated by the text conversation user interface. It shall be possible to establish text only calls as well as calls with other media components. 5. 5 Invoking text conversation Calls with terminals where text conversation is used shall bemonitored for requests to start the text feature. When either party in a call begins usage of the text feature, an effort shall be made to establish text conversation. It shall be possible to start text conversation during a call already established in voice or video mode by adding the text component.<|end_of_text|>
|
The mode selected for text conversation IP Multimedia, CS Multimedia, Voice path etc. shall be determined according to a prioritised procedure. Modes allowing simultaneous voice and text shall by default have higher priority, while the user shall be given opportunities to prioritise text only modes. The default order shall be: IP Multimedia, CS Multimedia, data path text plus voice, voice path text. The user shall be given call progress information and text invocation progress information in text or other non audible media. 5. 6 Text conversation handling during calls Text transmission shall be done character by character as entered, or in small groups transmitted so, that no character is delayed before transmission more than 0. 5 seconds. as stated in ITU T T. 140 4 The text transmission shall allow a rate of at least 10 characters per second so that human typing speed as well as speech to text methods of generating conversation text can be supported. The end to end delay of characters shall be less than two seconds, measured between two mobile users, or between one mobile user and any interworking fixed network user, assuming that the fixed network does not contribute with more than one second to this figure. The character corruption rate should be less than 1 in conditions where users experience the voice transmission quality to be low but useful. The transmission of the text conversation shall be made according to the character set and operations defined in ITU T T. 140. 4 .<|end_of_text|>
|
This requirement enables smooth interworking with minimal loss of functionality between different text conversation environments. The allowed limitations in character set support specified in ITU T T. 140 shall be obeyed, so that two terminals always have a minimum common character set available for conversation. Figure 2 gives an example of a possible layout of a real time text conversation according to ITU T T. 140.<|end_of_text|>
|
3GPP TS 22. 226 version 18. 0. 1 Release 18 ANNE EVE Hi, this is Anne. Yes, have you heard that I will come to Paris in November? Oh, hello Anne, I am glad you are calling! It was long since we met! No, that was new to me. What brings you here? Figure 2: A possible way to display a conversation with one window each Display of the conversation shall be done according to the principles specified in T. 140, unless the display is provided through interworking with a legacy mode text telephone, when the limitations of that device may govern. NOTE: It shall be noted that support for any written language is possible with T. 140, and that many languages require other writing directions than left to right. 5. 7 Alerting Since many GTT users are deaf or hard of hearing, the terminals used for GTT shall provide an interface that can be used to activate alternative alerting modes e. g. flash or vibration. 5. 8 Addressing GTT shall support the addressing formats of the host environments. to identify the different kinds of endpoints of the call used in the different host environments see section 9, interworking. 5. 9 Roaming Access to the GTT service while roaming is desirable. Note: Operators may consider using a Virtual Home Environment toolkit to provide GTT services to roaming subscribers.<|end_of_text|>
|
It can be expected that the subscriber will need to specifically subscribe to this service and no access to the GTT service will be possible if the visited network does not support the appropriate VHE toolkit. It should also be noted that emergency calls bypass most VHE toolkits, therefore emergency calls will require GTT support in the local network. 6 Security and reliability The user shall be able to use and access GTT in a secure manner. Within the limitations enforced by the host environments, the following apply. It shall be possible for the contents of GTT sessions to be read only by the intended recipient s . The Security Threats and Requirements specified in 22. 133 3 shall not be compromised. 7 Charging It is foreseen that users will not be expected to pay a premium for access to the GTT service. Hence the requirement to capture detailed information relating to the use of GTT is seen as optional. Various charging mechanisms may be supported in addition to what is defined for the host environment, the following charging characteristics may be considered: Text was used in the call. The duration for which text was used in a call.<|end_of_text|>
|
3GPP TS 22. 226 version 18. 0. 1 Release 18 8 External Interfaces 8. 1 External interfaces in the terminal It shall be possible to control and operate GTT from external digital devices, e. g, portable computers. For this purpose interfaces shall be standardised between the terminal and such external digital devices. It shall be possible to control and operate GTT from external analogue text telephones. For this purpose, interfaces shall be standardised between the mobile terminal and such external analogue text telephones. External interfaces specified for controlling and operating GTT between the terminal and an external device should make it possible to use the external device for both Multimedia Messaging and GTT. 8. 2 External interfaces to other networks No new network interfaces shall be specified for GTT, only the necessary elements to accomplish text interworking. These are specified in ITU T H. 248 Annex F, in the Text Conversation and Text Telephone packages 3 . The networks for specified interworking include: PSTN for interworking with PSTN text telephones. IP networks for interworking with IP conversational multimedia terminals and IP text telephones. CS networks for interworking with CS Multimedia terminals. Mobile networks out of scope of the GTT specifications interface through common interworking facilities. 9 Interworking It shall be possible to use GTT to communicate with similar features in other networks as specified in ITU T H. 248 Annex F, in the Text Conversation and Text Telephone packages 3 . This includes: PSTN text telephones, using voice telephony as a carrier according ITU T V.<|end_of_text|>
|
18 6 . IP text telephones, using IP multimedia protocols and text according to ITU T T. 140 4 . IP conversational multimedia terminals using IP multimedia protocols with text according to ITU T T. 140 4 . CS multimedia with text according to ITU T T. 140 4 . There is no requirement that the host environment combinations for interworking shall be extended for GTT support beyond the host environment interworking established for other media. For interworking with text conversation in mobile networks outside the scope of the GTT specifications, interworking shall be specified as for other external networks. For mobile services within scope of the GTT specification, interworking shall be possible between different forms of GTT, within the limits of interworking between the different host environments. GTT shall permit use of the supplementary services defined for the host environment. Users of both GTT and Multimedia Messaging 7 , 8 , should be provided the following interoperation opportunities: If a call with a text component fails, it should be possible to offer the user to send a message to a MultiMedia Messaging facility such that the message may later be delivered in non real time to the destination.<|end_of_text|>
|
3GPP TS 22. 226 version 18. 0. 1 Release 18 External User Equipment interface specifications should enable both GTT and MMS text handling functions to be placed in the same device. Note: In order to fulfil the requirement to give a consistent view of the feature from different access points, it may be of interest to give fixed network text telephone users possibilities to send and receive MMS text messages. This is however outside the scope of this specification. 10 Additional services 10. 1 Emergency services It shall be possible to support emergency service calls with text and voice. If an emergency service centre supports call back to the calling user, then the call back function shall be available for GTT text calls without modification to the existing emergency service centre text telephony equipment. GTT emergency calls shall be possible without the SIM USIM module in the same host environments as such calls are enabled for voice. All information that follows a voice call to the emergency centre, shall also be provided to the centre if GTT text is used in the call. The emergency service requirements shall be possible to fulfil for emergency service centres equipped with PSTN text telephones, operated through a relay operator service or an interworking functions. Support of GTT service for emergency calls shall not jeopardise normal emergency calls. 10. 2 Relay services Relay services offer translation between text and voice. It is most commonly implemented as manned services. Access to relay services shall be possible for GTT users.<|end_of_text|>
|
Establishment of the relay service itself is outside the scope of GTT. GTT shall enable addition of a relay service to the call. The relay service terminates the text path, and translates between text and voice. Addressing the destination and requesting support from the relay service should be possible to do in one operation from the GTT user. Other aspects of implementing relay services are outside the scope of this specification. 11 Network implementation considerations The GTT feature may be implemented in a number of ways. The GTT specifications shall allow cost effective implementations both for networks with a small part of the subscribers using GTT as well as networks with relatively many subscribers using GTT.<|end_of_text|>
|
3GPP TS 22. 226 version 18. 0. 1 Release 18 Annex A informative : Background Text telephone systems were implemented mainly for distant conversation with deaf, hard of hearing, speech impaired and deaf blind users. The text telephone systems offer a real time, character by character, conversation in text, optionally combinable with voice. With proper implementation in mobile systems, the feature is expected to be of interest for any user. The general user needs are described in ETSI ETR 333 Human Factors, Text Telephony; User requirements and Recommendations 2 . In PSTN, seven different, openly specified systems for text telephony exist, and are used in different regions. Some proprietary modes are also used. The open specifications are called Baudot, DTMF, EDT, V. 21, Bell103, Minitel and V. 18. They all use different modem technologies and character coding for the transmission of text. They are briefly described in the annexes of ITU T V. 18 6 . ITU T V. 18 6 is an automoding mechanism that enables communication with all the legacy modes on the modem level. It also detects when both parties have V. 18, and invokes an internationally useful character set, defined in ITU T T. 140, and optionally transmission of text and voice simultaneously. Native modulation for V. 18 is V. 21, while V. 61 is used when simultaneous voice and text is wanted. Other modulations can be negotiated. V. 18 and T. 140 are intended for use in new PSTN text telephones.<|end_of_text|>
|
They are also intended for use in gateways, bridging from the fragmented situation in the PSTN, into new services, designed according to the Total Conversation concept. A. 1 Total Conversation Total Conversation adds text conversation to multimedia protocols in a standardised way, so that simultaneous communication in video, text and voice is accomplished. For the text part, the Unicode based text presentation protocol ITU T T. 140 is used. It is transmitted with a specific standardised transport channel for each environment. Subsets can be used for example for text telephony enabled in the multimedia architectures. Total Conversation is currently defined in the following environments: 1. Packet networks, where the procedures described in ITU T H. 323 Annex G can be used for text conversation sessions, using TCP or RTP T140 for the transport of T. 140. A simple packet text telephone is defined, called Text SET. 2. Packet networks, where the IETF Session Initiation Protocol SIP can be used for setting up and conducting text conversation sessions using RTP T140 for the transport of T. 140 text media. RTP T140 is MIME registered and specified in IETF RFC 2793 9 . 3. The H. 324 multimedia environment in PSTN, ISDN and Mobile networks, where an AL1 channel connected by H. 245 procedures is used for T. 140. 4. The H. 320 multimedia environment, where a H. 224 channel with client ID 2 is specified for transport of T. 140. 5. The T. 120 data conferencing environment, that can be used alone or in conjunction with any of the environments above, where T.<|end_of_text|>
|
134 specifies the application entity and T. 125 the data channel for T. 140. 6. Text Telephony in the PSTN using the ITU T V. 18 modem and T. 140 for the presentation without any further transport protocol. A. 2 Interworking Interworking between these forms of Text Conversation can be achieved through the use of gateways or interworking functions. One gateway mechanism in the process of standardisation is ITU T H. 248, where Annex F, Facsimile, Text conversation and call discrimination packages 3 describes additions for handling text telephony and text conversation.<|end_of_text|>
|
3GPP TS 22. 226 version 18. 0. 1 Release 18 A. 3 Additional services Apart from the basic user to user conversation, the following are examples of important additional services that can be offered text telephone users and Total Conversation users. Emergency services The ability to call to emergency services, announce an emergency situation and discuss the actions can be offered text telephone users and Total Conversation users. Calls from the emergency service with support for text conversation is also needed. Relay services In order to have conversations with users of plain voice telephones, text relay services are established. Currently, manned relay services dominate, offering real time translation between written and spoken language. Automatic and semi automatic versions are emerging. A through connection of the voice channel is usually offered as an option to satisfy users who can benefit from multiple modes. With Total Conversation services, both traditional text relay services and other relay services are established. Examples are sign language relay services with text support during service establishment and speech support relay services with visual enhancement. ;.<|end_of_text|>
|
3GPP TS 22. 226 version 18. 0. 1 Release 18 Annex B informative : Initial requirements This section is informative and specifies the initial requirements that formed the base of definition of GTT. The 3GPP GTT specifications together define what requirements will be met. Most requirements in this chapter are derived from the requirements expressed to be urgent by the FCC and the CTIA TTY forum in USA. The relation with these requirements are documented for each requirement. Many of these requirements are written with the view that a PSTN text telephone is attached to the mobile station for implementation of the basic GTT functionality. B. 1 Transmission Performance A1: The printable character error rate PER shall be less than 1 for stationary calls under nominal radio conditions, i. e. where also speech calls show an acceptable quality TTY FCC 1 . A2: The printable character error rate PER shall be less than 1 for calls with pedestrian speed or typical vehicle speed under nominal radio conditions TTY FCC 13, TTY Forum, extended . A3: An output volume control should be provided in order to allow adaptation to existing Text Telephone equipment for optimal receiving quality TTY FCC 4 . A4: The input range shall be automatically adapted to the proper receiving level new . A5: The Text Telephone shall allow to transmit Speech and Text VCO HCO in an automated way, without user interaction, either by alternating between speech and text mode or by transmitting speech and text in parallel objective TTY FCC 9, extended .<|end_of_text|>
|
A6: The delay of the speech path shall not exceed that of a normal speech call in that situation by more than 40ms in one way, if the text telephone functionality is activated. Otherwise no additional delay shall occur to the speech signal. The delay of the speech path should not vary during a speech phrase. A7: The delay of the text path shall not exceed that of the speech path by more than 1000 ms one way at typing speed of 7 characters per second. The delay of the text path may be variable. A8: The time of switching between Text and Speech mode shall not exceed 1000 ms at normal typing speed. A9: The printable character throughput shall not be smaller than 10 characters per second under nominal radio operating conditions TTY FCC 10, extended . A10: Under impaired radio conditions the character throughput may be reduced in order to achieve the desired printable character error rate TTY FCC 10, modified . A11: The signals used for transmission should pass existing fixed and wireless analogue speech channels with a printable character error rate below 1 under nominal radio conditions, if two devices are connected back to back . A12: The data transmission bit rate should be as high as possible under the given radio conditions with the objective of 300 Bit s with a bit error rate below 10 3 and a residual bit error rate below 10 5 after removing detected bit errors .<|end_of_text|>
|
A13: It shall be possible to transmit both, single characters, as well as long text or data strings from file efficiently. A14: The transmission mechanism should provide data flow control to adapt the source data rate when in file transfer mode to the varying radio transmission conditions, in order not to loose data on the path. A15: The character coding shall allow transmission of characters from any language in a consistent way.<|end_of_text|>
|
3GPP TS 22. 226 version 18. 0. 1 Release 18 B. 2 Man Machine Interface MMI These Requirements and Objectives are to some extent depending on implementation and not on the transmission standard. This list shall by no means restrict the innovation capabilities of vendors, but give guidelines and define a minimum set, against which the transmission standard needs to be checked. B1: The Text Telephone user must be able to monitor all aspects of call progress same or more information as provided to voice users by tones and visualisation TTY FCC 2 . The transmission standard shall provide the necessary monitor information to the MMI. B2: There must be an indication, by tones and visualisation, when the call is connected or disconnected TTY FCC 3 . B3: Call information such as caller identification, where provided in mobile voice services, should also be provided for Text Telephony calls TTY FCC 11 adapted . B4: The Text Telephone system must be able to send Text Tones to a normal telephone user, to indicate that he is using a text telephone, even if the other user has only a normal phone TTY FCC 6 adjusted . B5: The Text Telephone user must have a means of tactile vibrating ring signal indication. TTY FCC 5 , besides an acoustical and optical ring signal indication new . B6: Emergency calls e. g. to 112 or 911 numbers shall not require any further user interaction than for any normal voice call. except to connect the possible additional equipment new .<|end_of_text|>
|
B7: Call back from Emergency Call Centres should not require any further user interaction than for any normal voice call except to connect the possible additional equipment new. B8: Call setup to and from other Text Telephone users of the same type according to the new standard should not require any further user interaction than for any normal voice call new . B9: Call setup to and from other Text Telephone users of an other kind e. g. those defined in ITU V. 18 may require some user activity, like sending a short additional precode e. g. 2. 3 digits or typing a short digit sequence to invoke the service e. g. like 55 or on user s preference the permanent subscription to such a service a capability signalling by the mobile activating a text telephone application others B10: The new standard should allow the usage of ordinary unmodified mobile phones as already available to the user or on the mass market, in order to get the advantage of high volumes price level. B10: The new standard shall allow to hide the intermediate with existing phones necessary user interaction, as described in the items before, in modern equipment automatic service . B11: The use of the Text Telephone for emergency calls with unregistered phones or without SIM USIM shall be possible as for normal voice calls.<|end_of_text|>
|
B12: The interface to the possible adapters shall be exactly specified with mandatory interfaces as to allow interaction to existing Text Telephones and the basic access to the mobile phone and optional interfaces as to connect microphone and loudspeaker, the control port of the mobile phones, B. 3 Compatibility C1: The standard shall be compatible to equipment on the landline side as specified in ITU recommendation V. 18 TTY FCC 12, extended , including all annexes of V. 18 and V. 18 with V. 61 for voice and text simultaneously.<|end_of_text|>
|
3GPP TS 22. 226 version 18. 0. 1 Release 18 C2: The landline party s Text Telephone equipment shall not need modifications or additions in order to be compatible and to achieve the desired error rate TTY FCC 7 . C3: It shall be possible to deploy the Text Telephone standard world wide in all systems based on 3GPP specifications new . C4: The wireless Text Telephone i. e. on the Mobile user side may require modifications or additions or the development of new equipment TTY FCC 8 . The smaller the modifications or additions the better. C5: Roaming between networks of different operators of the same kind of wireless technology shall be possible, provided the operators has installed the service. C6: Is should be possible to connect equipment implementing the standard to any existing mobile phone of any existing wireless standard. C7: Communication between Text Telephones in different kinds of wireless technologies shall be possible. C8: Communication with text between mobile text telephones and multimedia devices with text shall be possible. B. 4 Complexity of Implementation and Roll Out D1: The standard shall allow a fast first step implementation and roll out D2: The standard shall allow integration into the mobile phone or the Text Telephone terminal or integration of everything together into a single device.<|end_of_text|>
|
3GPP TS 22. 226 version 18. 0. 1 Release 18 B. 5 Referenced consumer requirements In the previous sections of this annex, the TTY FCC requirements refer to the points below. They are formulated in November 1999 as the consumer requirements by the TTY Forum administered by CTIA in USA. The comments are inserted here for clarification. 1. The character error rate should approximate that of AMPS, which has been demonstrated at 1 for stationary calls. More research on AMPS performance with TTY would be useful to assist in specifying a range of conditions. 2. The TTY caller must be able to visually monitor all aspects of call progress provided to voice users. Specifically, the ability to pass through sounds on the line to the TTY so that the user can monitor ring, busy, answered in voice, etc. should be provided. 3. There must be a visual indication when the call has been disconnected. 4. A volume control should be provided. Comment: This item is intended to allow the TTY user to adjust volume for better reception of TTY tones into a mobile terminal attached TTY. It has no meaning for other solutions. 5. The TTY user must have a means of tactile vibrating ring signal indication. 6. The caller must be able to transmit TTY tones independent of the condition of the receiving modem. Comment: This is to permit Text Telephone signalling, to let a hearing person know that the incoming call is from a text telephone. 7.<|end_of_text|>
|
The landline party s TTY must not require retrofitting in order to achieve the desired error rate. 8. The wireless party s TTY may require retrofitting, or a new model TTY to be developed, or the use of a portable data terminal such as a personal digital assistant. 9. VCO and HCO should be supported where possible. Comment: VCO Voice carry over. HCO Hearing Carry Over. These are terms for alternating voice and text in the same call. 10. Reduction of throughput partial rate on Baudot is highly undesirable and should not be relied upon to achieve compliance see 7 . It may be useful as a user selectable option to improve accuracy on a given call. 11. Call information such as ANI and ALI, where provided in wireless voice, should also be provided for TTY calls. Comment: ANI Automatic Number Identification, ALI Automatic Location Identification. 12. On the landline side, the solution need not support little used or obsolete TTY models, but in general should support the embedded base of TTY s sold over the past ten years. The landline equipment supported must not be limited to that used in Public Service Answering Points 911 centers . 13. Drive conditions must be supported, again using AMPS as a benchmark.<|end_of_text|>
|
3GPP TS 22. 226 version 18. 0. 1 Release 18 Annex C informative : Change history Document history V. 0. 0. 1 April 2000 First Presented at TSG S1 10th 15th April 00 V. 0. 3. 0 July 2000 Includes changes required by S1 9. V. 0. 3. 1 Aug. 2000 Align with 3GPP doc structure V. 0. 3. 2 Aug. 2000 Comments from Ericsson and Siemens accepted V. 1. 0. 0 Sept. 2000 Updated to version 1. 0. 0 for presentation to SA 9 V. 1. 1. 0 May 2001 Updated with output of GTT ad hoc. To be sent for approval at SA 12 V. 2. 0. 0 May 2001 Raised to version 2. 0. 0 for approval at SA 12 V5. 0. 0 June 2001 Approved at SA 12 V5. 1. 0 Oct. 2001 Creation of 5. 1. 0 by inclusion of CRs at SA 13 Change history TSG SA SA Doc. SA1 Doc Spec CR Rev Rel Cat Subject Comment Old New WI Dec 1999 02. 01 Transferred to 3GPP SA1 8. 1. 0 3. 0. 0 SP 13 SP 010433 S1 010861 22. 226 001 Rel 5 F CR to 22. 226 version 5. 0. 0 GTT Stage 1 as requested by SA 5. 0. 0 5. 1. 0 GTT SP 15 SP 020045 S1 020457 22. 226 002 Rel 5 F Editorial CR to correct terms and references 5. 1. 0 5. 2. 0 CORRECT SP 26 SP 040744 S1 040997 22. 001 Rel 6 Updated from Rel 5 to Rel 6 5. 0. 0 6. 0. 0 SP 36 22.<|end_of_text|>
|
001 Rel 7 Updated from Rel 6 to Rel 7 6. 0. 0 7. 0. 0 SP 42 Rel 8 Updated from Rel 7 to Rel 8 7. 0. 0 8. 0. 0 SP 46 Updated to Rel 9 by MCC 8. 0. 0 9. 0. 0 2011 03 Update to Rel 10 version MCC 9. 0. 0 10. 0. 0 2012 09 Updated to Rel 11 by MCC 10. 0. 0 11. 0. 0 2014 10 Updated to Rel 12 by MCC 11. 0. 0 12. 0. 0 2015 12 Updated to Rel 13 by MCC 12. 0. 0 13. 0. 0 2017 03 Updated to Rel 14 by MCC 13. 0. 0 14. 0. 0 2018 06 Updated to Rel 15 by MCC 14. 0. 0 15. 0. 0 SA 88e Updated to Rel 16 by MCC 15. 0. 0 16. 0. 0 2022 03 Updated to Rel 17 by MCC 16. 0. 0 17. 0. 0 2024 03 Updated to Rel 18 by MCC and issue with v. 18. 0. 0 upload 17. 0. 0 18. 0. 1.<|end_of_text|>
|
16 Recommendation ITU T G. 8251: The control of jitter and wander within the optical transport network OTN . 17 Recommendation ITU T G. 8201: Error performance parameters and objectives for multi operator international paths within optical transport networks . 18 IEEE 802. 3. 1 : IEEE Standard for Management Information Base MIB Definitions for Ethernet . 19 IEEE 802. 1Q : IEEE Standard for Local and metropolitan area networks Bridges and Bridged Networks . 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 included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i. 1 ETSI GR F5G 002 V1. 1. 1 : Fifth Generation Fixed Network F5G ; F5G Use Cases Release 1 . i. 2 ETSI GR F5G 001 V1. 1. 1 : Fifth Generation Fixed Network F5G ; F5G Generation Definition Release 1 . i. 3 ITU T Study Group 15 Q18, G. fin SA: High speed fibre based in premises transceivers system architecture . i. 4 IETF ietf ccamp transport nbi app statement: sport Northbound Interface Applicability Statement . i. 5 IETF ietf teas ietf network slices: Framework for IETF Network Slices . i. 6 IETF ietf teas applicability actn slicing: Applicability of Abstraction and Control of Traffic Engineered Networks ACTN to Network Slicing . i.<|end_of_text|>
|
7 IETF zheng ccamp yang otn slicing: Framework and Data Model for OTN Network Slicing . i. 8 ITU T Study Group 15 Q11 G. osu: Optical Service Unit OSU path layer network . i. 9 IETF ietf teas enhanced vpn: A Framework for Enhanced Virtual Private Network VPN Services . i. 10 IETF bestbar teas ns packet: Realizing Network Slices in IP MPLS Networks . i. 11 ETSI GR IPE 005: IPv6 Enhanced Innovation IPE ; IPE_5G Transport and Cloud and IP network Convergence . i. 12 IETF RFC 8655: Deterministic Networking Architecture . i. 13 IETF RFC 2702: Requirements for Traffic Engineering Over MPLS . i. 14 IETF RFC 3209: RSVP TE: Extensions to RSVP for LSP Tunnels . i. 15 IETF ietf spring resource aware segments: Introducing Resource Awareness to SR Segments . i. 16 IEC 61158: Industrial communication networks Fieldbus specifications . i. 17 ETSI GS F5G 006: End to End Management and Control of F5G Networks .<|end_of_text|>
|
3 Definition of terms, symbols and abbreviations 3. 1 Terms For the purposes of the present document, the following terms apply: application list: list of applications and the associated attributes to identify the application in a network element EtherCAT: Ethernet for Control Automation Technology is an Ethernet based fieldbus system NOTE: The protocol is standardized in IEC 61158 i. 16 and is suitable for both hard and soft real time computing requirements in automation technology. network slice: logical network that achieves specific service requirements 3. 2 Symbols Void. 3. 3 Abbreviations For the present document, the following abbreviations apply: AI Artificial Intelligence API Application Programming Interface ARPU Average Revenue Per User ASG Access Service Gateway BGP Border Gateway Protocol BNG Broadband Network Gateway BSS Business Support System BYOD Bring You Own Device CE Customer Equipment CPE Customer Premises Equipment CPN Customer Premises Network CPN A CPN Agent CPU Central Processing Unit DC Data Centre DC GW Data Center Gateway DSCP Differentiated Services Code Point E2E End to End E CPE Enterprise CPE eFBB enhanced Fixed BroadBand ETH Ethernet EVPN Ethernet VPN FEC Forward Error Correction FFC Full Fibre Connection FlexO Flexible Optical transport network FTTH Fibre To The Home FTTR Fibre To The Room GEM GPON Encapsulation Mode GMPLS Generalized Multi Protocol Label Switching GPON Gigabit Passive Optical Network GRE Guaranteed Reliable Experience ICT Information and Communication Technology IE Industrial Equipment IP RAN IP Radio Access Network IP Internet Protocol IPTV Internet Protocol Television IT Information Technology.<|end_of_text|>
|
L2VPN Layer 2 VPN LAN Local Area Network LSP Link State Protocol MAC Media Access Control MAN Metropolitan Area Network MEF Metro Ethernet Forum MP BGP Multiprotocol Extensions for BGP MPLS Multiprotocol Label Switching MS OTN Multi Service OTN NAT Network Address Translation NFV Network Function Virtualisation NMS Network Management System NSI Network Slice Instance NSP Network Service Provider O M Operation and Maintenance OAM Operation, Administration and Maintenance OAM P Operation, Administration, Maintenance and Provision ODN Optical Distribution Network ODU Optical Data Unit OLT Optical Line Terminal OMCI ONU Management and Control Interface ONU Optical Network Unit OSS Operations Support System OSU Optical Service Unit OTN Optical Transport Network OTU Optical Transport Unit OTUCn Optical Transport Unit Cn pBNG physical Broadband Network Gateway PBX Private Branch Exchange PC Personal Computer PCS Physical Coding Sublayer PDH Plesiochronous Digital Hierarchy PE Provider Edge PHY Physical layer POL Passive Optical LAN PON Passive Optical Network PPPoE Point to Point Protocol over Ethernet QoE Quality of Experience QoS Quality of Service RFC Requests for Comments RG Residential Gateway SDH Synchronous Digital Hierarchy SDN Software Defined Networking SLA Service Level Agreement SME Small and Medium Enterprises SRv6 Segment Routing over IPv6 T CONT Traffic Container TDM Time Division Multiplexing TDMA Time Division Multiple Access TID Traffic IDentifier TOS Type Of Service VCPE virtual Customer Premises Equipment VLAN Virtual LAN VNF Virtual Network Function VNO Virtual Network Operator VPN Virtual Private Network VR Virtual Reality VxLAN Virtual extensible Local Area Network WAN Wide Area Network WDM Wavelength Division Multiplexing WMM Wi Fi multimedia XC Cross Connect.<|end_of_text|>
|
XGS PON 10 Gigabit capable Symmetric PON NOTE: Also known as symmetric 10G PON. YANG Yet Another Next Generation data modelling language 4 Business requirements for network architecture 4. 1 Business requirements overview When implementing a use case, the business requirements may be separated into a Physical Layer, a Network Layer and an Application and Management Layer. The focus of the present document is the F5G network architecture. This clause will summarize the business requirements of the network layer. However, this clause may also illustrate system level requirements essential to network nodes and equipment for the F5G use cases. Other requirements not deduced from the F5G use cases may also be considered, such as network evolution trends. 4. 2 Business requirements driving the F5G architecture Dual Gigabit Networks: The dual Gigabit networks are represented by 5G mobile and fixed multi gigabit optical networks F5G , which provide fixed and mobile gigabit single user access capabilities. The dual Gigabit network features ultra high bandwidth, ultra low latency and enhanced reliability. That means dual 5G and F5G networks need to be built for new application scenarios beyond the traditional applications. It is a key element for developing the digital economy, the digital society and the digital government. Rich set of Applications and Services for Different Market Segments: The F5G architecture needs to support a rich and diverse set of application and service scenarios for a wide range of customers profiles including home users, large, medium, and small enterprises and specific vertical industries.<|end_of_text|>
|
Those applications and services for the different markets are ideally supported on the same infrastructure for improved operational efficiency of communication and networking services. This multi service network shall allow flexible and dynamic service creation, development and deployment. F5G Infrastructure Convergence and Consolidation: In the current fixed network business, the networking services are provided with dedicated networks and shared best effort network infrastructure using copper and fibre based access networks. Consolidating and converging the fixed network infrastructure requires the overall infrastructure to enable a seamless connection between network segments access, aggregation and core and differentiate the services required by the different market segments and applications. The differentiation is expected over several dimensions, including bandwidth, latency, reliability, end to end delay assurance, and convergence through dynamic service awareness on a single, converged and agile management plane. Also, studies show that enterprises from medium to small scale have a very diverse set of networking service requirements and are often co located with other SMEs and residential housing. Sharing infrastructure on various levels is a suitable way of increasing operational efficiency. Converged Application Needs: The line between home and enterprise networks is blurring since many more of those that work from home offices require enterprise grade infrastructure. Also, industries and education institutions have moved more online and have massively digitized their processes, requiring the proper networking technology. On the other hand, some enterprises encourage Bring Your Own Device BYOD , and some applications that the workforce are using are based on what they use at home.<|end_of_text|>
|
Also, enterprise networks are required to support residential oriented methods of working and processes, including on demand ordering of communication services.<|end_of_text|>
|
Shift of Broadband Service Requirements: So far, specifically for the residential markets, the services focus on the Internet Access Bandwidth. Also, in the enterprise markets, an important focus is on network bandwidth and reliability. For F5G, the assumption is that bandwidth is no longer the only dimension and that there is a shift from bandwidth to user experience to improve ARPU. This implies that the network needs to be more service aware. Separation and isolation of user traffic from each other are a necessary mechanism to deal with guaranteed SLAs e. g. through E2E slicing . More experience based network policies are required to support more scenario based broadband products for home, enterprise and verticals. Growing beyond Traditional Telecommunication: The F5G architecture shall enable a wide range of services and functionalities, namely addressing specific vertical industries and other needs that support new business areas. For example, the functionality of E2E slicing and time critical communication enables a larger set of industrial applications. In addition, the F5G architecture should support Passive Optical LAN POL as carrier grade technology for campus and enterprise environments with the benefits of saving equipment rooms, having high quality management capabilities, saving energy through passive optical technologies, removing radiation, and enhancing networking services in the customer premises. Increased Operational Efficiency: The F5G architecture aims to improve operational efficiency by improving the quality of experience and better control over the quality of the services provided, such that potential user requirements are detected early and can be reacted upon.<|end_of_text|>
|
Integrating artificial intelligence and machine learning mechanisms into the F5G architecture will enable improved efficiency and more accurate network planning in terms of quality and capacity extension. The F5G architecture is a unified architecture, which simplifies the O M of the network. Decoupling the service plane and underlay plane using fabric networking simplifies and decouples capacity expansion from the service needs and improves bandwidth efficiency. Automatic operation and model driven management simplify the interaction with different IT systems in the operator domain. Security and Privacy: The fixed network shall be a trusted infrastructure, requiring that the F5G architecture solves security and privacy challenges. Secured and privacy aware networks and services are important for customer's trust in the network and make it a prerequisite for digitalization of industries and the society. NOTE: The present document addresses only peripheral security and privacy topics, but they are addressed in detail by other documents of the ETSI ISG F5G. 5 Network architecture 5. 1 Architecture design principles 5. 1. 1 Multi Service Network Platform Multiple services for multiple customer types can be deployed based on the currently deployed broadband network architecture. However, it is not flexible, the deployment takes time, and the different customer requirements are difficult to fulfil cost effectively. To enable flexible service deployment, SDN and NFV were introduced for network flexibility as tools to migrate fixed network architecture towards an SDN and NFV enabled F5G network architecture. SDN centralizes the control plane function and provides a concentrated network management functions.<|end_of_text|>
|
The management plane is now called the Management, Control and Analytics MCA plane; it enables more flexible and more efficient traffic route selection than a fully distributed control plane. NFV uses the virtualization technologies and cloudification to virtualize entire classes of network node functions into functions that are either stand alone or chained together to provide a communication service. This is especially beneficial for computing based network functions, which can be easily deployed on IT oriented cloud infrastructures.<|end_of_text|>
|
NFV enables more flexibility to run the network functions and makes it easier to upgrade and enhance network services dynamically. The F5G architecture supports processing elements wherever needed including edge computing. However, the network's primary function is transporting bits at high speed, which means the base functionality of networking still requires major hardware support. The multi service network platform needs mechanisms to isolate a certain type of service traffic from other traffic. The platform should support guaranteed quality of service and a wide range of diverse services. 5. 1. 2 Dynamic and Flexible Service Creation The F5G architecture is expected to support eFBB, FFC and GRE, which means ten times more speed, ten times more dense connections and ten times better SLAs. Besides fundamental features like SDN and NFV, the F5G architecture focuses more on flexible service enabling, reliable network performance guarantees, and autonomous service deployment. The assumption is that customers can order or change their services on demand through a user interface portal or API to the OSS BSS, which requires the Service Plane to be more flexible to adapt to a particular customer need. 5. 1. 3 Decoupling Service Plane and Network Plane Therefore, broadband services shall be decoupled from the underlying network infrastructure. The decoupling allows for the independent upgrade of the network infrastructure without any effect or changes on the service plane. Also, the services can be adapted and changed without changing the basic network infrastructure.<|end_of_text|>
|
However, certain interdependencies will still exist, specifically in terms of what resources on the underlay can be used to provide a particular service. Also, in the cases of underlay network failures, these may affect the service quality. 5. 1. 4 AI based Control, Management and Analytics Artificial Intelligence shall be introduced on the Management Control plane, making it a Management, Control Analytics Plane, enabling more intelligent detection of faults and QoE degradation, network behaviour analysis and reaction to poor performing networks. 5. 2 Architecture overview Based on SDN and NFV principles, the F5G network architecture decouples services from the underlying physical network. Figure 1 illustrates an overview of the three planes of the F5G network architecture.<|end_of_text|>
|
Figure 1: F5G network architecture The F5G network architecture comprises three planes, an Underlay Plane, a Service Plane and a Management, Control Analytics MCA Plane. Underlay Plane: This is fundamentally the physical network plane, which comprises physical network nodes. The Underlay Plane provides connections and dynamic programmable path selection under the control of the F5G controller in the MCA Plane. The network switching capacity shall scale without interfering with the Service Plane. The Underlay Plane has four segments, Customer Premises Network CPN , Access Network AN , Aggregation Network and Core Network. Various Technologies are used in the CPN, depending on the end user requirements. For example, in Home Access, Wi Fi 6 and FTTR can be introduced as new technologies, while Enterprise Access can benefit from POL to gain easy deployment and high bandwidth. OTN can also be deployed in the CPN for customers requiring high quality VPN service. The Access Network shall be based on XGS PON technology and OTN, depending on customer type and service delivered. The Aggregation Network has two parallel fabrics, an IP Ethernet fabric and an OTN fabric. The IP Ethernet fabric comprises spine switches, while OTN fabric is comprised of OTN nodes. For the actual deployment of IP Ethernet or OTN fabrics, there could be multiple physical fabrics of the same type co existing in one network. Both fabrics have a common Aggregation Edge handover point to the Core Network. There might be multiple tunnels between Access Network and Aggregation Edge, which go over either the IP Ethernet fabric or the OTN fabric.<|end_of_text|>
|
There may be multiple paths through different nodes for differentiated SLA tunnel instances in one fabric. Typically, there is only one tunnel instance for a certain SLA. The Access Network connects both IP Ethernet fabric and OTN fabric. The Underlay Plane and the associated network nodes shall support network slicing. Service Plane This plane provides service connectivity for customers and the broadband service above. Compared with coarse granularity tunnels of the Underlay Plane, service connections on the Service Plane can be dynamically created when triggered by protocols, e. g. PPPoE, or configured from the MCA Plane.<|end_of_text|>
|
A Service Access Point SAP provides customer service access. A Service Processing Point SPP performs L1 L2 L3 service processing, which may be enhanced by Edge Computing. A Service Mapping Point SMP is where traffic is directed to proper underlay fabric and channels. An Access Network typically contains SAP, SPP and SMP. Besides providing the access function, it also identifies services, adds or removes encapsulations, and directs the traffic to the proper underlay fabric and channels. An Aggregation Edge typically contains SPP and SMP, because it needs to perform service specific processing and egress ingress traffic mapping to appropriate underlay tunnels. A service connection refers to the service pipe between a Service Access Point SAP from the Access Network and the Service Processing Point SPP on the Aggregation Edge. Examples of SPP on the Aggregation Edge are pBNG, wholesale Gateway, VPN PE and VNF for value added services. Internet service pipes between ONU and pBNG are typical service connections. The Service Plane also provides service connections between SPPs, e. g. a service chain between a vCPE instance and a vFirewall instance, a VPN from the OLT to the Aggregation Edge. For IP based services, the SPP in the Access Network can perform subscriber authentication, while pBNG mainly terminates PPPoE services. By defining new SPPs, new services can easily be created by programming service chains with SPPs. The Service Plane is decoupled from the Underlay Plane. The Underlay Plane is unaware of changes in the Service Plane, e. g. adding, deleting and directing service traffic to SAPs and SPPs.<|end_of_text|>
|
The SAP and SPP can be scaled independently. The Service Plane can support multiple services with different SLAs. The requirements for deploying services on the Service Plane include connecting endpoints with guaranteed SLAs. The Service Plane shall negotiate resource requirements with the Underlay Plane, which is coordinated by the MCA Plane. It is unnecessary for the Service Plane to be aware of the creation of paths through network nodes, protection, etc. Management, Control Analytics MCA Plane: MCA Plane is the intelligent core of the network, which is in charge of management, control and analytics of the complete network. It is comprised of three logical components. However, the logical components can be implemented as distributed, centralized or hybrid mode. So the functional allocation to locations in the network topology is for further study: Digital Twin: The digital twin of the network is the model of the network, including available resources and configurations. The digital twin also contains an equivalent model of the running network. A network digital twin is generated through the real time collection of network status and combining that with network resources and configurations. Network statistics are continuously computed. A digital twin is the real time status and configuration of the network, which is the input for autonomous operation and artificial intelligence based analysis. Autonomous Management and Control: This is the main function for network configuration, service deployment, and network operation.<|end_of_text|>
|
Besides the controllers for Service Plane and Underlay Plane, it also contains Intent Engine and Autonomous Engine: Intent Engine: provides an Intent API for the OSS. The Intent API is an interface similar to natural language, describing what I want . It is abstract and decoupled from specific network configurations. The Intent Engine can translate and understand the intent from the interface and drive corresponding operation, validation and feedback. Autonomous Engine: implements operations such as resource management, device management, service deployment and tunnel selections on the Underlay Plane. It also implements resource management, device management and service deployment on the Service Plane. One important function of the Autonomous Engine is the coordinated configuration of the planes, which enables plug and play of network nodes, and programmability of both underlay tunnels and services. AI analyser: analyses network data, identifies, locates and predicts network failures, provides management tools for QoE and analysis tools for network operations. It includes the Analysis Engine and the AI Engine: Analysis Engine: a data management platform and algorithms for analytics. Analysing network digital twin enables optimal tunnel selection on Underlay Plane, identifies and analyses network failures, and drives close loop control of the Autonomous Engine.<|end_of_text|>
|
AI Engine: it performs reasoning and training using Artificial Intelligence. The Analysing Engine leverages the AI Engine for analytics and reasoning, in order to perform prediction of network failure and usage, and failure identification and analysis. 5. 3 Network topology and interfaces 5. 3. 1 Network Overview The F5G network architecture is developed based on the current fixed network deployment and provides more Full Fibre Connections FFC with high quality user experience GRE . Compared with previous generations, the introduction of FTTR will be a major improvement in fibre connection numbers. FTTR is not restricted to residential customers but can also be applied to business customers. This will fundamentally change the network topology, flow model and management. Considering GRE, E2E service quality relies on QoS for each network segment, where network topology and technologies play an important role. For example, for Cloud VR, Cloud VR terminal devices communicate with the Cloud VR Service Platform through the CPN, the Access network and the Aggregation Network. All three segments need to provide good quality to guarantee an E2E high quality user experience. PON can provide on premises network connectivity and is considered part of the CPN use case 4 in IETF RFC 8453 1 . XG S PON is the leading F5G Access Network technology. For the Aggregation Network, IP Ethernet based network has been widely deployed for years. For residential customers, BNG is necessary for subscriber authentication, authorization and accounting. However, for business customers, especially Private Line customers, the BNG may not be required.<|end_of_text|>
|
Provisioning and management of MPLS based VPN is complicated, especially Traffic Engineering TE , which typically needs manual configuration. To improve the flexibility, efficiency and performance of the Aggregation Network in F5G, an OTN network is introduced to complement the IP Ethernet based network and build a full fibre E2E network. F5G requires differentiated carrier capabilities to support high quality services with guaranteed bandwidth and latency, as well as low cost best effort services. The IP Network can be improved with new IP technologies to meet the requirements of GRE and potentially simplify the management. OTN can be used to provide high quality carrier service, which is enhanced by adding fine granularity. There are several benefits with the addition of OTN, including supporting transparent transport, high bandwidth multiplexing, powerful OAM, etc. Figure 2: F5G Network topology.<|end_of_text|>
|
1 FTTR: for now will be viewed as a black box, it is comprised of CPN Agent labelled as CPN A and customer edge devices labelled E CPE. The FTTR block is for further study. 2 Integrated home Optical Network Termination comprising an adaptation function labelled RG Residential Gateway and an Access Network node labelled ONU. 3 Disaggregated home Optical Network Termination comprising an adaptation function labelled RG Residential Gateway and Access Network node labelled ONU. The difference between item 2 and item 3 is that the adaptation function is external. 4 Cellular Backhaul Optical Network Termination comprising an adaptation function labelled WG Wireless Gateway and Access Network node labelled ONU. 5 Small and medium sized business Optical Network Termination comprising an adaptation function labelled CE Customer Equipment , and Access Network node labelled ONU. 6 Industrial Optical Network Termination comprising an adaptation function labelled IE Industrial Equipment , and an Access Network node labelled ONU. 7 Premium Private Line Optical Network Termination differs from item 2 to item 6, and it comprises an adaptation function labelled CE Customer Equipment and Access Network node labelled E O CPE Enterprise OTN Customer Premise Equipment , which is OTN based and not PON bases. Figure 2 shows the F5G network topology. The FTTR case labelled item 1 in Figure 2 is for further study. Items 2 to 5 in Figure 2 have a customer facing adaptation function and an Access Network node. The adaptation function and Access Network node are demarcated by U interface.<|end_of_text|>
|
In the case of premium private line, an OTN CPE O E CPE represents the device that communicates with the OTN edge cross connect on the network side. It is also the aggregation device for enterprise data. The enterprise network labelled CE in Figure 2 and the U' interface demarcates the Access Network. While SDN NFV is considered in F5G, the OLT module in Figure 2 represents the data plane function of OLT and OTN edge cross connect, whereas the control and management function of the OLT is not shown and is out of scope of the present document. A BNG is a typical function in IP Ethernet based Aggregation Networks, which may be directly connected to an OLT or via other nodes. Even though there are some efforts to disaggregate the BNG or create a BNG pool, the module in the figure represents the BNG function. There may be an IP Ethernet Aggregation Network between BNG and Core Network in some cases. OTN technology is an alternative to IP Ethernet for the Aggregation Network. The OTN edge cross connect aggregates the Access OTN traffic and will be a node on the OTN Aggregation Network. The Aggregation Network Edge represents the handover point between the Aggregation Network and Core Network. It needs to identify and direct the traffic in both directions. The local DC and cloud services are getting more and more popular and can be considered an extension that expands the legacy core network.<|end_of_text|>
|
Even though the Core Network is not in the scope of the present document, the interfaces between Aggregation Network and Core Network need to be specified in the present document. The interfaces in Figure 2 are described in clause 5. 3. 2. 5. 3. 2 Definition of Interfaces 5. 3. 2. 1 T interface The T interface is the handover point between E CPE Gateway CE and the customer devices. This includes residential customers, business customers and wireless backhaul. Because of the diversity of customers, besides Ethernet and Wi Fi 6, there might be other types of interfaces like Bluetooth . Such interfaces shall be translated to Ethernet IP protocols on the CE devices. The T interface for FTTR is the same as for FTTH. Other interfaces for FTTR are not addressed in the present document. They are for further study and for future versions of the F5G architecture. For example, the G. fin SA project in ITU T Q18 15 i. 3 is defining the FTTR system architecture.<|end_of_text|>
|
5. 3. 2. 2 T' interface The T' interface is the handover point between the Enterprise customer devices and the CE. The primary interfaces from of Enterprise devices are Ethernet and Wi Fi 6. However, besides Ethernet and Wi Fi, there might be other types of interfaces such as for telephones connecting to a PBX or legacy SDH equipment. 5. 3. 2. 3 T'' interface The T'' interface is the handover point between IE and industrial network devices. There are many types of industrial protocols and interfaces, like EtherCAT, serial interface, etc. They shall be supported by the IE device depending on the scenarios. Such interfaces shall translate industrial protocols to Ethernet IP protocols on the IE devices. 5. 3. 2. 4 U interface The U interface is the handover point between the Access Network and the CPN. For a PON based network, the ONU is considered an extension of the Access Network, even though it physically resides in the CPN. Therefore, the U interface is the user facing interface of an ONU. It could be an internal interface if ONU and RG are integrated into one physical device. 5. 3. 2. 5 U' interface The U' interface is the handover point between the OTN Access Network and the CPN CE. For an OTN Access Network, the E_O_CPE is considered an extension of that OTN Access Network, even though it physically resides in the Enterprise CPN. Therefore, the U' interface is the user facing interface of E_O_CPE. The protocol stacks on the U' interface are depicted in Figure 3.<|end_of_text|>
|
Figure 3: Protocol stacks on U' interface 5. 3. 2. 6 B interface The B interface is the handover point between the OLT Access Network node and the OTN Edge cross connect OTN Edge XC node. This is an Ethernet interface, which will be mapped over an appropriate OTN container. The protocol stacks on the B interface are depicted in Figure 4. Figure 4: Protocol stacks on B interface The B interface is only present in the case of OLT and OTN Edge XC being separated physical network equipment. Otherwise, it is an internal interface and does not necessitate a description. 5. 3. 2. 7 V interface The V interface is the IP Ethernet based handover point between the Access Network and the Aggregation Network. Compared with a legacy IP Ethernet Aggregation Network, SRv6 and VxLAN are the primary technology for the Underlay Plane of IP Ethernet Aggregation Network. At the same time, EVPN is used for the Service Plane. The protocol stacks on the V interface are depicted in Figure 5. STM n Payload E1 Payload ETH MAC Payload ETH PCS ETH PHY ETH MAC Payload ETH PCS ETH PHY ETH PCS Payload ETH PHY.<|end_of_text|>
|
Figure 5: Protocol stacks on V interface 5. 3. 2. 8 Vo interface The Vo interface is the OTN based handover point between OTN Access Network and OTN Aggregation Network. The interface rate is dependent on the OTN bandwidth requirements of this OTN Access Node. The interfaces is either OTUk k 2, 3, 4 for bandwidth requirements between 10 G and 100 G or OTUCn FlexO for bandwidth greater than 100 G. These are the primary technologies for the Underlay Plane of OTN Aggregation Network, while VLAN is used for the Service Plane. Figure 6: Protocol stacks on Vo interface 5. 3. 2. 9 A10 interface The A10 interface is the handover point between the Aggregation Network and the Core Network. Depending on the capability of Core PE, the handover protocol may be selected from EVPN, VxLAN, SRv6, MPLS, etc. Protocol stacks on A10 interface are depicted in Figure 7. Aggregation Edge may be required to implement protocol interworking between the Aggregation Network and the Core Network. PHY for A10 interface may be Ethernet PHY for the legacy network or OTN for a full optical network. Figure 7: Protocol stacks on A10 interface 5. 3. 2. 10 A10' interface A10' interface is the handover point between the Aggregation Network and the Cloud or local DC. This interface is actually the interface between the Aggregation Edge and the DC Gateway. The link could either be Ethernet based or OTN based. Protocol stacks on A10' interface are depicted in Figure 8. ODUk ODUCn Payload OTUk OTUCn FlexO.<|end_of_text|>
|
Figure 8: Protocol stacks on A10' interface 5. 3. 3 OTN Control Interfaces In F5G, the OTN network can be used to carry high quality services. To enable the automatic OTN tunnel creation for these services, the OTN control plane shall be enhanced. The OTN control plane is separated from the data plane, and the interfaces in the OTN control plane are shown in the modified F5G network topology in Figure 9. Unlike the centralized MCA plane, the OTN control plane is a signalling plane running between OTN nodes. The OTN control interfaces transmit the provisioning protocols for the OTN based services. There are two OTN control interfaces types: The C1 interface is used to control the OTN network connections in the Underlay Plane. The C2 and C2' interfaces are used to control the OTN based service connections in the Service Plane. Figure 9: OTN control interfaces The C1 interface is the control plane handover point between two network nodes, where the OTN based links are used. The C1 interface exists between the OTN Edge XC and the OTN Aggregation Network, and between the E O CPE and the OTN Edge XC. For both locations, the C1 interface has the same control functions and is used to exchange the OTN signalling messages to control the OTN network connections across the network segments. The main functions of the C1 interface include: To transmit the signalling messages used to create, modify or delete OTN network connections automatically.<|end_of_text|>
|
The F5G management and control system will trigger this signalling process not shown in Figure 6 for simplicity .<|end_of_text|>
|
To transmit the signalling messages used to adjust the bandwidth of the OTN network connections. A typical network scenario is the use case for premium home broadband service, supported by connecting to multiple clouds. The OTN Aggregation Network is used to transport the services of multiple users. The bandwidth adjustment of the OTN network connection is based on a change in the number of users, an adaptation of the user's bandwidth needs, or a shift in application bandwidth needs. To perform fast OTN connection recovery after network failures, specifically in the case of a large number of connections. The OTN network is being enhanced by the addition of finer granularity containers, therefore the number of connections in the OTN network will increase significantly. At the same time, compared with legacy GMPLS protocol, the C1 interface should also be enhanced with the ability to recover a large number of connections in a short and committed recovery time. This is required to meet the SLA requirements of the OTN based services and ensure high quality customer experience. The C2 and C2' interfaces are the control plane handover points between the two ends of an OTN based service connection in the Service Plane, where the service traffic is mapped into de mapped from an OTN network connection. The C2 interface exists between the OTN Edge XC and the AggN Edge and is mainly applied to the PON on premises use cases see items 1 to 6 in Figure 2 .<|end_of_text|>
|
The C2' interface exists between the E O CPE and the AggN Edge and is mainly applied to the use case of Premium Private Line services see item 7 in Figure 2 . The C2 and C2' interfaces are used to negotiate between and configure the Service Mapping Point SMP in the Service Plane. The C2 and C2' may be different due to the provisioned services. The main functions of the C2 and C2' interfaces include: To learn and exchange the MAC IP addresses between the network endpoints, ,such as between the private networks in both the CPN Access Network side and the Core Network side, signalling endpoints OTN edge nodes . This helps the OTN edge nodes i. e. the E O CPE, the OTN Edge XC and the OTN AggN Edge to generate the appropriate service mapping de mapping rules. Such rules include the mapping of the service traffic into the OTN network connections and the de mapping of the service traffic from the OTN network connections. Note that the exchange of MAC IP addresses is per VPN service, i. e. the address exchange is only within each VPN of a specific service. To identify the destination address of the service traffic and map the service traffic into the appropriated OTN network connections according to the service mapping de mapping rules. Note that, due to the differences of applicable use cases and service provided, the C2 and C2' interfaces may be slightly different in protocol design, although they have similar functions.<|end_of_text|>
|
The protocol design of the C2 and C2' interfaces are out of the scope of the present document. Since the E O CPE is located on customer's premises, and its security may not be under the control of the network operator, the security aspects of the control interfaces C1, C2' connecting the E O CPE and the nodes in the operator's network also need to be considered. This is for further study. 5. 4 Key enabling features 5. 4. 1 Network Slicing 5. 4. 1. 1 Introduction A network slice is a logical network that achieves specific service requirements. Network slicing provides a solution for differentiated services in a mode of operation such that multiple independent instances with different service requirements are provided on a shared infrastructure. With the flexible design of slicing functions in terms of performance, isolation and O M, network service providers can create customized networks based on customers' requirements. Network slicing is an end to end concept that covers all network segments. The F5G architecture end to end slicing includes CPN, Access, Aggregation, and Core networks. It enables the concurrent deployment of multiple end to end logical, self contained, and independent shared or partitioned networks on a common infrastructure platform. In network slicing, forwarding resources are sliced, and network functions shall be sliced or allocated to different slices also. Slicing of network functions in Service Plane, e. g. SAP, SPP and SMP, are for further study.<|end_of_text|>
|
Network Slicing is an important feature for F5G networks, which fulfils a set of high level F5G requirements that are summarized below: 1 The F5G system requires guaranteed network service . The motivation for this requirement is that the service performance requirements will be more dynamic and differentiated. The handling of requirements along a various dimensions is needed to support those different service performances. Services with different SLAs can be carried on the same network through the slicing solution separating the traffic into different slices. 2 The F5G system requires isolation. The motivation for isolation is from a resource perspective to have guaranteed service, and it protects against the mixing of traffic and interference between different business entities and tenants. For example, resource isolation from other tenant networks is a basic privacy requirement for industry production networks. 3 The F5G system requires independent service operation. Network providers need to be able to open network functions to tenants so that tenants can manage, configure, and operate their own network slices for the definition of tenant see the following clause . 4 The F5G system requires end to end slices covering customer premise, Access Network, Aggregation Network and Cloud resources. 5 The F5G system requires end to end slice management, ensuring resource reservation, configuration, protection and O M management. 5. 4. 1. 2 Concepts Network Slice: A network slice is a logical network that achieves specific service requirements. Network Slice Instance NSI : An instantiation of a network slice with particular defined network capabilities e. g. QoS, OAM, reliability and a set of resources.<|end_of_text|>
|
The network slice instance is characterized by multiple parameters and covers management, control, and forwarding requirements of the services. The network slice instance is an end to end concept. Network Slice Template: The template covers the different parameters of the network slice instance's characteristics. Service Slice Type SST : A service slice type refers to an expected network behaviour in terms of features and services e. g. specialized broadband for a particular application of a slice. Tenants: The business entity using and controlling a network slice. The tenant can be different entities depending on the context and business relationship. For example, a tenant can be a Virtual Network Operator VNO or a Network as a Service NaaS user. Dedicated Network D Net : A set of preconfigured paths or tunnels established on a shared networking infrastructure. D Nets operate independently from each other, are fully isolated from other paths and tunnels, and meet the SLA requirements of the tenants. A D Net can be managed by an independent management plane or several D Nets can be managed by a single management plane. Network Service Providers NSPs : The NSP defines a service including the network functions of D Nets and the required E2E network resources including D Net topology, transmission links, and ODN resources that can be exclusively used, and resources such as boards and ports of each Network Element NE . Bearer tunnel: A network connection instance in the Underlay Plane with particular QoS characteristics, transporting the traffic according to the SST requirements. Isolation: There are several levels of isolation possible.<|end_of_text|>
|
On the data level, each instance has its own isolated data instance. On the resource level, it means isolation which includes tenants having their own basic resources like databases, logs, alarms, and networking resources. There is also soft isolation of resources like buffers, queues, control plane processes, forwarding processes and hardware isolation like boards and ports, CPU cores, forwarding chips and sub racks. NOTE 1: Different isolation levels and mechanisms have different characteristics and complexities. Typically, an application or service uses a network slice of a certain slice type. The tenant is the business entity providing the particular service or application to users.<|end_of_text|>
|
eFBB Slice High Bandwidth Slice Type GRE Slice Low Latency High Bandwidth and Low Latency Vertical Network Slice Instances Dedicated Network Service Provider A Whole Sale VNO Smart City Industrial Enterprise X Cloud Gaming Online Cloud VR Smart Home Application Industrial Surveillance Medical Imaging Metering Enterprise Connectivity Massive Fibre Connections IoT Surveillance Broadband Internet Hospital Enterprise Connectivity Mission Critical Figure 10: Network Slicing Concepts Example Figure 10 shows an example of different network slicing concepts. Several slice types exist. In this example, 4 slice types are illustrated eFBB, GRE, Massive Fibre Connections for IoT oriented application, and a combination of high bandwidth and low latency for vertical industry oriented services . Network Slice Instances can be of one of the pre defined slice types. A Dedicated Network D Net belongs to a particular tenant offering services to specific market segments like residential, wholesale, smart city, industrial, hospitals or any other enterprise oriented segment. The Enterprise X in Figure 10 is a placeholder for any enterprise oriented services as described in the use case document. The particular market segment has a set of typical applications, which the Dedicated Network needs to support with the appropriate quality. For example, the residential oriented Dedicated Network supports traditional broadband, Cloud Gaming, Cloud VR, and Smart Home applications. NOTE 2: There are use cases in the F5G use case document ETSI GR F5G 002 i. 1 not shown in Figure 10. For the present document the following characteristics of network slicing are envisioned: 1 A network slice has several network capabilities.<|end_of_text|>
|
The network slice is defined by multiple parameters and covers management, control, and forwarding requirements. 2 A network slice template describes the network slice characteristics. 3 An instance of a network slice that is deployed on a network is referred to as a Network Slice Instance NSI . The network slice instance is a service or service unit that can be independently operated and managed as a whole. 4 Network slice instances are implemented on a unified physical infrastructure, including computing, storage and network resources what is used for providing a service is a matter of slice design . Resource occupation modes include shared priority based scheduling, guaranteed resource reservation which can be occupied by other services when not in use and exclusive resource reservation. 5 A network slicing SLA can be met in several ways. From the perspective of network slicing, unified scheduling of E2E computing, storage and connection resources is important. For example, to meet the ultra low latency requirement, a service can be deployed locally or an ultra low latency hard pipe can be deployed. 6 The network slice SLA includes QoS guarantees.<|end_of_text|>
|
7 A slice includes a data plane component. It consists of end to end logical connections and switching nodes. Logical connections and switching nodes can be classified into three types: shared priority based scheduler, guaranteed resource reservation, and exclusive resource reservation. The switching nodes might include packet and TDM switching. The data plane of the Underlay Plane can have two types of technologies: priority scheduling and guaranteed resource reservation. 5. 4. 1. 3 Network Slicing Applicability Generally, there are two types of E2E slices in F5G. One is slicing the network into dedicated network resources according to SLA requirements for various tenants or operators, which may be applied to multiple industries or scenarios. The other is service oriented slicing, where one network can be shared for different services with isolation and guaranteed QoS: 1 User group oriented slicing: User group oriented slicing refers to virtual operators, which implement the operation, management, and control of network nodes and virtual networks. It refers to several Dedicated Networks, where the virtual operator's network nodes are connected. The user group may be one with all users of the same type, for example, an enterprise user group users of an enterprise or a home broadband user group. It can also be a third party virtual network leaser in a whole sale scenario deploying its own devices connecting to the virtual network. Different user group slices have basic features in terms of operation isolation, including forwarding isolation and management isolation.<|end_of_text|>
|
Implementing user group slicing simplifies communication network management, improves network communication quality and lays the foundation for differentiated services on a virtualized infrastructure. 2 Service oriented slicing: Service oriented slicing refers to the construction of multiple isolated logical networks with different SLA capabilities for different services of the same user group or tenant. The slicing concept is applicable on different levels and might be hierarchical. Several service oriented slice instances can be within one user group oriented slice instance. For example, a home broadband user group uses both common Internet access services and VR services. A service slice is setup for each service. The traffic is separated and associated to its predefined slice type to meet the SLA requirements of common Internet access services and VR services. Different service slices have different SLA capabilities, and service slices have the characteristics of forwarding resource isolation. To illustrate network slicing, an example scenario is shown in Figure 11. It shows three slice instances for residential high quality video, education, and medical industry. Since network slicing is about sharing common infrastructure, the example shows different sharing approaches, depending on the use case: 1 For the residential high quality video scenario, the Wi Fi network, the WAN port of the ONU, the PON network, the OLT, the OTN Nodes and the Gateway are shared but still have appropriate QoS characteristics for high quality video services. This is a more service oriented slice type since the service characteristics are the major influencing factor.<|end_of_text|>
|
2 For the education scenario, the CPN is exclusive for the education site, and the ODN and PON tree are also exclusive. The OLT, OTN nodes, and the gateway are shared, however. Within the CPN, different applications as e whiteboard and teaching equipment, including PC and projectors, might need to share the CPN and need certain QoS characteristics. Depending on the business arrangement and the education administration's willingness to control and manage the slice, it is more a dedicated network oriented slice, which can be sub divided into service oriented slices for the different applications of the administration of the education. Or it can be seen more as a set of services provided by the operator. Then it can be regarded as more a service oriented slice. 3 For the medical application scenario, the traffic from the CPE onwards is isolated from other traffic. Though the OTN nodes are shared, with hard isolation of slice instances from each other. Here the slice is a dedicated network provided to the medical institution with defined network QoS characteristics.<|end_of_text|>
|
Figure 11: Example of Network Slicing 5. 4. 1. 4 F5G Slicing Architecture Figure 12 shows the F5G slicing architecture. Since slicing is end to end at several locations, slicing oriented functionality is needed. This includes the data plane as well as the control and management plane. There are different levels of isolation at the different locations. Figure 12: F5G Slicing Architecture NOTE: The location of feature 3 and 4 in Figure 12 does not impose a particular implementation and only denotes those features available on the nodes. In Figure 12, the following slicing features are shown: 1 Wi Fi 6 RU Radio Unit slicing: The Wi Fi 6 Radio Unit needs slicing functionality for isolating resources on the Wi Fi Radio part of the network. Also, the function for Wi Fi 6 network attachment plays a role in what slice a particular device is connected to. The decision on what slice a Wi Fi terminal is connecting to can be decided by the network or the terminal. Also, it can be transparent to the terminal, and the network can make intelligent decisions on demand within the Customer Premises Network or in the Access Network. 2 In the Access Network, either PON or OTN features isolate traffic from different slices. If there is a need for resource isolation within a slice, the PON network or the OTN based Access Network needs to handle that. 3 In the Access Nodes and AggN Edge nodes the network slices from the various slice types needs to be properly handled such that the service slice type characteristics are guaranteed.<|end_of_text|>
|
Traffic separation within a slice needs the appropriate handling in the Access Node. 4 Also, in the Access Node and the AggN Edge node, the characteristics of the path and the bearer tunnel used are selected. The traffic is steered to use OTN or IP Ethernet depending on the required service characteristics. 5 In the fabric of the Aggregation Network, bearer tunnels have been established to carry the service traffic, guaranteeing the demanded characteristics to the appropriate place in the network. The traffic steering function needs to know what traffic is steered into those bearer tunnels.<|end_of_text|>
|
6 Slice management deals with the creation removal and monitoring of slice instances. Above the MCA plane are the tenant management systems that manage their tenant services and request slice instances. The northbound interfaces of the MCA plane need to be isolated from each other for management independence. A key aspect of network slicing is resource isolation. So the specific functionality on the forwarding plane for resource isolation is the following: 1 The forwarding plane supports two forwarding modes: Packet and TDM. The resources of the two forwarding modes shall be independent. 2 The packet forwarding plane shall support multiple isolated resource pools for isolating the traffic. The TDM forwarding plane supports isolation inherently. 3 Resources in either forwarding planes may be allocated to one or more network slice instances. Currently, independent dedicated networks are usually established for industries with high privacy requirements. An optimized and agile network construction is achievable with enhanced resource isolation and deployment flexibility of network slices. Therefore industries benefit from migrating from these privacy oriented networks to network slices. 5. 4. 1. 5 Network Slice Management The details of the management architecture are out of scope of the present document, but a high level view of the slice management that is divided into layers and is described in this clause. The first layer is the application layer, a service layer module where tenant VNOs can perform machine to machine or human to machine operations on slices and D Nets. Tenants can manage and operate slices independently.<|end_of_text|>
|
The second layer is the network layer, which provides resource management, configuration management, performance management, and status management for network slices. The data in the network layer includes the predefined network function set, initial resource package, current resource data, and the slice running status. The NSP manages the life cycle of tenants, grants and withdraws resources, and grants and modifies network functions. The third layer is the NE management and control layer, which manages the functionalities of each network element. A particular solution of network slice management is given by a standardized architecture, namely the Abstraction and Control of Traffic Engineering Network ACTN , as specified in IETF RFC 8453 1 . ACTN is defined as a multi domain, multi technology network management architecture, as illustrated in the following Figure 13. The Customer Network Controller CNC of ACTN is the top layer, where tenants can manage their slices. Multi Domain Service Coordinator MDSC is the second layer that manages E2E network resources and slice configuration. Provisioning Network Controller PNC is the third layer that manages network elements. Figure 13: ACTN Architecture Source: IETF RFC 8453 1 .<|end_of_text|>
|
The YANG models specified in the IETF are applicable to the ACTN architecture. The IETF ietf ccamp transport nbi app statement i. 4 provides guidelines on how the IETF YANG models are applied on ACTN interfaces for various functionalities including topology learning, tunnel establishment and service delivery. ACTN has been identified by the Framework for IETF Network Slices ietf teas ietf network slices i. 5 as a suitable basis for delivering and realizing IETF network slices. Further discussion on applicability, including YANG models, is ongoing in IETF ietf teas applicability actn slicing i. 6 . Besides the current capability of OTN network management, the IETF is also developing YANG models for OTN slicing by zheng ccamp yang otn slicing i. 7 . It is expected that the ACTN framework can be extended to cover F5G end to end slice management, which creates a lot of synergy among different SDOs. 5. 4. 1. 6 Traffic Steering in the Context of Slicing Traffic steering in the context of slicing deals with what traffic is mapped to what network slice instance. The traffic of different tenants or users is distinguished by some labels tags protocol header information in the service flows. In the network, the traffic is processed based on forwarding rules including QoS processing. The control and management system authenticates and authorizes the access to an end to end slice instance and statically configures the mapping function for traffic to the appropriate network slice instance. The automated mapping function is for further study. For further details on traffic steering, refer to clause 5. 4. 2. 5. 4. 1.<|end_of_text|>
|
7 Wi Fi Slicing In F5G, many of the end user devices in the network are connected to an ONU or Gateway through Wi Fi. Such Wi Fi links in the local area network are service oriented. User traffic is classified with different traffic priority identified by a Traffic IDentifier TID for different service quality requirements. According to the TID, the traffic is mapped to Wi Fi Multimedia WMM queues, in which multiple slicing techniques can be applied to achieve Wi Fi slicing. To implement Wi Fi slicing, the Wi Fi air interface resource is divided into multiple groups and allocated to different users. These slicing techniques are for further study. Figure 14: Overview for Wi Fi Slicing 5. 4. 1. 8 PON Slicing 5. 4. 1. 8. 1 Introduction Aligned with the F5G E2E slicing concept, PON also supports user group oriented slicing and service oriented slicing. These two types of slicing may be combined in a PON Access Network. From the implementation perspective, the OLT node is comprised of PON, IP Ethernet and OTN uplink. This clause will address the slicing of ONU and OLT nodes.<|end_of_text|>
|
Figure 15 depicts an example of a combination of user group oriented slicing and service oriented slicing. A specific user group uses a specific D Net instance D Net1 and D Net2 . Figure 15 shows 2 D Nets with different performance characteristics. The implementation of the differentiated performance characteristics is shown in the pipe symbols labelled D Net1 blue and D Net2 green in Figure 15. Each D Net has two service oriented slices slices 1 to 4 . In each D Net, there are multiple slices with different performance characteristics for different services. For example, in D Net1, Slice 1 and Slice 2 represent two types of services and Slice 2 is shared by two users. Slice 2 and Slice 4 are two different slices but having the same service quality characteristics. Figure 15: Overview for PON Slicing 5. 4. 1. 8. 2 User Group Oriented Slicing In the context of PON, an ONU is part of a single user group, and therefore an ONU is part of a single D Net instance. The user group shall be configured per ONU, and the uplink ports of an OLT shall be configured for all ONUs of the same user group. On the PON port of the OLT, different user groups should perform bandwidth isolation. Each user group exclusively uses its own bandwidth. The OLT allocates the upstream bandwidth of all T CONTs on a PON port in the same user group and isolates the upstream services of the user group. The OLT perform traffic shaping based on the user group of the user side PON port to ensure bandwidth isolation.<|end_of_text|>
|
When VLANs of multiple user groups are planned in the same scheme, the OLT should allow multiple user groups to share an uplink port. For different user groups, the OLT should be able to allocate bandwidth on the uplink port. Each user group exclusively uses its own bandwidth. The upstream port of the OLT supports traffic shaping for user groups to ensure bandwidth isolation. The OLT shall have an independent forwarding domain for each user group. This requires that the forwarding entries of each user group are isolated, and VLANs can be reused across user groups. VLANs are planned independently for each user group. Resource isolation between user groups includes: VLAN ONU Downstream bandwidth of the same OLT PON port Queue resources of the same OLT PON port 5. 4. 1. 8. 3 Service Oriented Slicing The service oriented slicing on PON has finer granularity than the user group oriented slicing. Service oriented slicing can be implemented per ONU, ONU LAN port or application Destination IP address. For upstream services, the OLT classifies service flows based on GEM port IDs and VLANs and maps service flows to service oriented slices. For downstream services, the service flows shall be classified and mapped to slices based on VLANs.<|end_of_text|>
|
For service slicing, upstream bandwidth isolation is based on T CONT time sequence on PON ports, and downstream bandwidth isolation is based on Hierarchical QoS H QoS . Resource isolation between service slices includes: LAN port of the ONU Downstream bandwidth of the same OLT PON port Queue resources of the same OLT PON port The upstream bandwidth of the ETH upstream ports on the OLT 5. 4. 1. 9 OTN Slicing OTN is a TDM technology with no oversubscription or congestion issues, and client data is allocated to their container, and each container is exclusively allocated its bandwidth. By virtue of the fact that OTN is a TDM technology the OTN containers are totally isolated from each other. In OTN, lower order containers are multiplexed into higher order containers. For example, eight lower order ODU0 can be multiplexed into a higher ODU2, or ten lower order ODU2 can be multiplexed into an ODU4. In general, n ODUj are multiplexed into an ODUk where j k. The ODU is the entity that is transported end to end. It may be de multiplexed from ingress high order ODU and switched and multiplexed into a different high order ODU on the egress of an OTN cross connects. So this hop by hop demuxing switching and muxing is the basic mechanism of OTN end to end path connectivity. The OTN management configures, monitors and tears down connections. The characteristics of the connection, such as bandwidth latency and end to end connectivity, are pre configured by the OTN NMS.<|end_of_text|>
|
In addition to an ODU container, ITU T SG15 Q11 i. 8 is developing an additional OTN container called OSU, which will support all client rates below 1G s. In contrast, the ODU will support client rates above 1Gb s. The OSU will be multiplexed into an ODU for transport through an OTN network. Same as ODU, OSU will be de multiplexed switched and multiplexed again on a hop by hop basis. Depending on the capability of the cross connect, it may only support ODU switching or may support both ODU and OSU switching. It depends on where the network switching is done. So an OTN slice is an ODU OSU with specific network characteristics matching the SLA. That ODU OSU could be a single entity end to end, or it could be an ODU that consists of lower order ODU and OSU with the same network characteristics requirement and destined for the same endpoint. As explained above, the higher order ODU may change on a hop by hop basis, but the de multiplexing, switching and muxing again are how the end to end path for a slice is formed. Also mentioned above, the OTN NMS determines the route taken through the OTN network and determines the characteristic of that route to form a slice instance matching the required SLA. An OTN slice instance can originate in two locations in the Access Network. The first source of OTN slicing originates in the E_O_CPE, where client data is mapped into an OTN container such as an OSU.<|end_of_text|>
|
The VLAN tag and physical port are used to delineate the slice type. The user may join several different slice instances by allocating the appropriate traffic stream to the different OSUs ODUs. These OSUs ODUs are multiplexed into a higher order ODUk and transported via an OTUk to from the E_O_CPE to the edge cross connect. These OSU ODUs will be demultiplexed on the ingress of edge cross connect, then switched to an egress line card and multiplexed into a different higher order ODU and transported through the OTN Aggregation Network to the Aggregation edge, where they are either demapped back into client data most likely Ethernet and forwarded to the endpoint, or they may also remain as OTN and get forwarded to the far endpoint CPE for demapping. The second source of OTN slicing may originate in the PON network, where a VLAN tag delineates the slice type. In the OLT the SMP determines which fabric is used to transport the service through the Aggregation Network. In this case SMP directed this traffic to the OTN cross connect, where it is mapped into an OSU or ODU depending on the bandwidth requirements. Then it follows the same process as in the first case in that it is transported through the Aggregation Network. In this case, it may join an existing slice instance that matches its network requirements or start a new slice instance.<|end_of_text|>
|
An important aspect of slicing is its ability to grow or contract depending on the bandwidth requirement of the slice. A slice member can be the originator of the slice formation or may join an existing slice with other members already present. In the latter case, there are two aspects to take into account. Firstly the ability to add a member to the slice by expanding the bandwidth of the slice without interfering or disturbing existing members, so there is a need for hitless slice expansion. The second is the ability to remove a member of the slice without interfering or disturbing existing members, so there is a need for slice bandwidth contraction when the member no longer needs the bandwidth, such as stopping playing a VR game or denial of service for non payment of the service, or whatever reason. The bandwidth needs to be reduced to reduce waste and reduce the cost to the service provider. Again this bandwidth change needs to be done without interfering or disturbing existing members, so there is a need for hitless bandwidth reduction. OTN supports hitless bandwidth upgrades for both OSUs and ODUs, making it an ideal choice for slicing. The example in Figure 16 illustrates OTN slicing. There are five different slices established in the figure, two for VR cloud services, a banking slice, a Data Centre slice, and connectivity to the core slice: 1 The banking slice: There are two separate bank branches labelled 1 and 2 requiring reliable and isolated connection to the headquarters.<|end_of_text|>
|
In bank branches 1, its local OTN CPE maps the client data into two OSUs, similarly in bank branches 2, its local OTN CPE maps the client data into two OSUs. The OSU from bank branches 1 and 2 are carried in an OTU0 to the edge cross connect 2 and 1, respectively. In edge cross connect node 2 bank branches 1 OSUs are muxed into an ODU0 and carried to node 4 via an OTU2, and in edge cross connect node 1 bank branches 2 OSUs are muxed into an ODU0 which is carried to node 3 via an OTU2. Bank branches 1 OSUs are muxed into and ODU0 in node 4 and carried to node 6 via an OTU4, and bank branches 2 OSUs are muxed into, and ODU0 in node 3 and carried to node 6 via an OTU4. In node 6 the four OSUs are multiplexed into an ODU2 and carried to the edge cross connect node 8 via an OTU2, and there they are multiplexed into an ODU2 and transported to the headquarters CPE in an OTU2. 2 Cloud VR slice: There are four home broadband users, and two sets of two share the same OLT. On the top of the diagram, the users are labelled Cloud VR 1 orange and 2 grey , while at the bottom are labelled again labelled Cloud VR 1 green and 2 purple . Green and orange users are associated with the VR rendering 1, while purple and grey are associated with VR rendering 2.<|end_of_text|>
|
Cloud rendering 1 slice formation is described here, but the same principle applies to Cloud rendering 2 slices. Cloud VR 1 orange is attached to OLT1, while Cloud VR 1 green is attached to OLT2. OLT 1 and 2 redirect Cloud VR 1 orange and Cloud VR 1 green to edge cross connect 1 and 2, respectively, where Cloud VR 1 orange is mapped into the orange OSU and Cloud VR 1 green is mapped into the green OSU. The orange OSU is multiplexed into an ODU0 and carried via an OTU2 to node 3, while the green OSU is multiplexed into an ODU0 and carried via an OTU2 to node 4. The orange OSU is multiplexed into an ODU0 and carried via an OTU4 to node 6, while the green OSU is multiplexed into an ODU0 and carried via an OTU4 to node 6. In node 6, the orange and green OSUs are multiplexed together into an ODU0 and carried to node 8 via an OTU2. In node 8, the orange and green OSUs are terminated and demapped, and the user data is transferred to the VR rendering gateway 1 via Ethernet. 3 Enterprise data centre and enterprise core network slides: The enterprise data centre slice formation is described here. The same principle applies to enterprise core network slices. There are two enterprise locations again labelled 1 and 2. They may be the same company in different locations. So like the bank case, the two enterprise entities use an OTN CPE.<|end_of_text|>
|
Enterprise 1 E1 data is mapped into a brown OSU, while Enterprise 2 E2 data is mapped into a yellow OSU. E1's OSU brown is carried to the edge cross connect node 2 in an OTU0, and E2's OSU yellow is carried to the edge cross connect node 1 in an OTU0. In edge cross connect node 2, E1 OSU brown is multiplexed into an ODU0 and carried to node 4 via an OTU2. In edge cross connect node 1, E2 OSU yellow is multiplexed into an ODU0 and carried to node 3 via an OTU2. In node 3, E2 OSU yellow is multiplexed into an ODU0 and carried to node 5 via an OTU4. In node 4, E1 OSU brown is multiplexed into an ODU0 and carried to node 5 via an OTU4. In node 5 E1, and E2 OSUs are multiplexed into the same ODU0 and carried to node 7 via an OTU2. In node 7, the brown and yellow OSUs are terminated and demapped into Ethernet and forwarded to the DC GW.<|end_of_text|>
|
Figure 16: An example illustrating different OTN slices 5. 4. 1. 10 IP AggN Slicing In the present clause, the F5G application area for IP networking is the aggregation network segment implemented by an IP fabric. The SMP on the access network directs traffic to the IP fabric, which needs to support F5G end to end slicing. IETF is currently working on network slicing for IETF networks, which are mainly IP networks. For example the IETF network slicing framework is currently under study by ietf teas ietf network slices i. 5 . Meanwhile, there are several on going activities in IETF to study how to implement slicing in IP network, for example ietf teas enhanced vpn i. 9 and bestbar teas ns packet i. 10 . Today's IP Networks are evolving and adopting IPv6 technology. IPv6 continues to evolve to meet the new requirements such as end to end Network Slicing see ETSI GR IPE 005 i. 11 . IP AggN Slicing is defined to meet the connectivity and performance requirements of different end to end services running over a shared AggN IP fabric. An IP network slice may span multiple IP network domains. As mentioned, the IETF is working on enhanced VPNs i. 9 as a solution for IP network slicing. The purpose is to support the needs for new applications by utilizing an approach that is based on existing VPN and Traffic Engineering TE technologies and adds characteristics that specific services require beyond those provided by traditional VPNs. The requirements of an Enhanced VPN service over the IP fabric are: Performance Guarantees. Isolation between different Enhanced VPN connections.<|end_of_text|>
|
Dynamic Changes, VPNs need to be created, modified, and removed from the network according to service demands. Customized Control and Management of the IP fabric. There are several candidate data plane technologies that provide the required IP isolation and guarantees, and they are: Deterministic Networking: Deterministic Networking DetNet , described in IETF RFC 8655 i. 12 , is a technique developed in the IETF to enhance the ability of Layer 3 networks to deliver packets more reliably and with greater control over the delay.<|end_of_text|>
|
MPLS Traffic Engineering MPLS TE : MPLS TE, described in IETF RFC 2702 i. 13 and IETF RFC 3209 i. 14 , introduces the concept of reserving end to end bandwidth for a TE LSP, which can be used to provide a point to point Virtual Transport Path VTP across the underlay network to support VPNs. Segment Routing: Segment Routing SR , described in IETF RFC 8402 5 , is a method that prepends instructions to packets at the head end of a path. These instructions specify the nodes and links to be traversed and allow the packets to be routed on paths other than the shortest path. With SR, it is possible to introduce such fine grained packet steering by specifying the queues and resources through an SR instruction list. With Segment Routing, the SR instruction list could be used to build a P2P path, and a group of SR SIDs Segment Identifier could also be used to represent an P2MP or MP2MP network. Thus, the SR based mechanism could be used to provide both a Virtual Transport Path VTP and a Virtual Transport Network VTN for enhanced VPN services. Segment Routing is the preferred technology for implementing slicing in the aggregation network. Indeed, SR enables easy end to end per flow SR policies, allows fine granularity, introduces scalability properties as it reduces the amount of state information and supports services like Traffic Engineering and Virtual Private Networks. For Segment Routing, it is possible to define the resource aware SIDs ietf spring resource aware segments i.<|end_of_text|>
|
15 that retain their original forwarding semantics, but with the additional semantics to identify the set of network resources available for the packet processing action. The resource aware SIDs can therefore be used to build SR paths or virtual networks with a set of reserved network resources. The proposed mechanism is applicable to both segment routing with MPLS data plane SR MPLS and segment routing with IPv6 data plane SRv6 . SRv6 takes advantage of the native end to end IPv6 connectivity and introduces the network programmability IETF RFC 8986 6 , enabling Service Function Chaining. This function is specifically for the transport of traffic to different Service Processing Points SPP . Additional details can be found in ETSI GR IPE 005 i. 11 that reports the main SRv6 concepts. 5. 4. 2 Traffic Steering 5. 4. 2. 1 Overview From the network layer perspective, the traffic of different tenants is distinguished by some labels in the service flows. The most commonly used label is a VLAN tag, where different tenants may have different VLAN tags or can use the same VLAN tags in case of deterministic networks which are fully isolated. The Service Mapping Point SMP , typically located in the Access Node, needs to map the traffic with a given label to the bearer tunnel matching the service requirements. In the network, the traffic is processed based on forwarding rules including QoS processing.<|end_of_text|>
|
For example, a video enthusiast tenant focuses on the bandwidth, latency and packet loss rate of the service links and a production enterprise tenants focuses on link latency, reliability and isolation for privacy. Nodes connecting to the Service Access Point SAP need to be capable of identifying available slice types and marking the traffic with the appropriate label such that the SMP can appropriately divert the traffic to the network slice instance that matches the deterministic network requirements. In addition, the traffic needs to be identified and authenticated to be allowed to use a particular service characteristic or service class. The control and management system authenticates and authorizes the access to an end to end slice instance and configures the traffic mapping function to the appropriate network slice instance. The automated mapping function is for further study. 5. 4. 2. 2 Traffic Steering Architecture 5. 4. 2. 2. 1 High level Framework In the present clause, the focus is on the traffic steering functionalities. However, traffic steering has a relationship with and interacts with other functions.<|end_of_text|>
|
Figure 17: Traffic Steering Functional Overview Figure 17 shows the functions related to traffic steering in the F5G architecture. Traffic steering consists of two parts: First, the Management, Control and Analytics MCA plane, which consists of traffic steering related functions, which interact with each other and with domain specific MCA functions. Second, the Network Elements NEs are sub divided into functions in the Access Network domain and the Aggregation Network domain. In the Access and the Aggregation Network Elements NEs , there are functionalities associated with the Underlay Plane and other functionalities associated with the Service Plane. The functions are described in the following clauses. 5. 4. 2. 2. 2 Management Control and Analytics MCA functions The MCA functions are integrated into management, control and analytics systems and further specified in the E2E Management document, ETSI GS F5G 006 i. 17 . The details on what management components have what function are for further study. The management has both technical and business aspects. For example, the MCA uses intent based and autonomous management. The separation of functionality into different management systems is for further study. Traffic Steering Management: Various functions are needed to manage traffic steering. The decisions to be made are based on the tenant, the slice instance, the operator's policies, and the terminating SPP at the AggN edge instance. The traffic steering management function maintains the data for the mapping of such traffic, as well as the requested capabilities.<|end_of_text|>
|
It also interacts with the slice management function in the case of slice update requests or optimizations, and it may expose an interface to other entities being involved in traffic steering decisions. Additionally, it interacts with the subscription management function in terms of authorization, service subscriptions, charging such that relevant actions can be taken. The configuration of network elements for traffic steering is static. The assumption is that the decisions on what traffic is steered to what location over what underlay fabric is static and depend on operator policies and network design choices. Dynamic versions of traffic steering are for further study. Subscription Management: The subscription management function manages all the functions associated with the subscriptions of tenants and users. It is used in the authentication and authorization processes of tenants and users. It also contains information about service level, slice type, service characteristics, which a tenant is using or is allowed to use and charging functionality for the tenant or the service user. Finally, the subscription management function handles the business and policy aspects of service requests and is responsible for issuing the resource policies. Slice Management: The slice management function consists of the slice template design and rollout functionality, the slice types offered by the operator at a particular location. It manages the entire lifecycle of the slice instances, including the creation, monitoring, optimization, adaptation, and release of slice instances. The decision is based on the tenant's service characteristic requirements, the operator policies, and the availability of networking resources.<|end_of_text|>
|
The decision about whether a slice is needed is an operator decision. Tenant Access Control Traffic Identification QoS Traffic Marking Access Network Network Element NE Traffic Steering Slice Bandwidth Management Aggregation Network Slice Traffic Scheduling Management, Control and Analytics MCA Plane Subscription Management Traffic Steering Management Slice Management Traffic Scheduling Traffic Steering.<|end_of_text|>
|
5. 4. 2. 2. 3 Access Network Element Based Functions Tenant Access Control: A tenant or user needs to get authorization to access a network service, which means the tenant or user and its devices need to be authenticated. Additionally the tenant needs to get authorization to use a particular service. In the case of a first time connection of a tenant or its devices CPEs, terminals, etc. to the network and or service, the authorization needs to be checked. There are cases where the tenant access control function needs to react when triggered by the first packet received indicating a new connection. In the case of dynamic service requests, the tenant access control function may receive access requests to the network service. In the static case, an a priori configuration is needed. Additional information used in the interaction with the subscription management component and traffic steering management component are elements such as Line ID, and other logical access information, such as VLAN ID, GEM Port ID, ONU Serial Number, CPE MAC address, IP addresses or IP 5 tuples, etc. There are several possible scenarios, which eventually need different authentication mechanisms and different security measures depending on the service to be accessed. NOTE 1: The security aspects are not addresses here and are for further study. Traffic Identification: When a tenant is authorized, the tenant's traffic needs to be identified in order for the traffic to be handled according to the service characteristics specified.<|end_of_text|>
|
The identification policies for Access Nodes could, for example, be based on tenant VLAN IDs or tenant IP addresses. The information used for identification may be elements such as Line ID, or other logical Access Network information, such as VLAN ID, GEM Port ID, ONU Serial Number, CPE MAC address, IP addresses, IP 5 tuples, etc. NOTE 2: There are scenarios and use cases, where traffic identification is based on application identification. This is for further study. QoS Traffic Marking: The QoS Traffic Marking function marks the incoming traffic according to the specific traffic policies and rules such that it can be handled in the processing stage. In case the marking is needed for QoS, the marking needs to be transported across interface boundaries, which means protocol support for it is required. Typically protocol fields for that function are the Ethernet priority field or IP TOS DSCP for QoS oriented marking. Traffic Steering: The traffic steering function steers the traffic towards the appropriate underlay technology. That is the main function of the Service Mapping Point SMP . Either the function steers the traffic to the appropriate tunnel for the traffic with specific characteristics, or it sends the traffic over the appropriate fabric without tunnelling. The decisions depend on the service requested or the tenant subscription. Traffic Scheduling: Depending on the configuration and dimensioning of the underlay networking technology, traffic from different tenants or different slices can be merged into the same tunnel, in which cases traffic scheduling is needed to manage the congestion cases. 5. 4.<|end_of_text|>
|
End of preview. Expand
in Data Studio
No dataset card yet
- Downloads last month
- 6