Page 83 - 5G Basics - Core Network Aspects
P. 83

Core network aspects                                            1


            Figure 7-20 is a procedural diagram of DAN functions for this scenario.

            1)      The service provider transmits the QoS requirements of the NDOs to the DAN network with labels
                    in the names of the NDOs, e.g., "/Phone/" or "/FDS/".
            2)      The end user requests an NDO from its service provider with the names, e.g., "/Phone/NDO" or
                    "/FDS/NDO".
            3)      The traffic control functions of the intermediate DAN elements identify the required QoS of the
                    request by the name and inform its content delivery function how to forward the requested NDO to
                    the end user.
            4)      The service provider forwards the requested NDO to the DAN network.
            5)      The DAN network determines a route based on the QoS requirement of the requested NDO and the
                    information of DAN networks, e.g., traffic and topology. The NDO is forwarded to the end user
                    following the determined route.
































                                      Figure 7-20 – Use case of traffic engineering DAN
            7.10.1  Benefits

            The properties of data objects are exposed to DAN elements in the form of the names or the attributes of
            the data objects, which is known as the data awareness of DAN. The properties enable DAN elements to treat
            individual data flows differently according to their requirements, e.g., delay sensitive or network conditions.
            While such an awareness feature in DAN is supported in a native manner by the architecture, conventional
            networks need a technology, e.g., deep packet inspection (DPI), to be aware of data flows.

            Moreover,  conventional  networks  secure  connection,  not  the  data  object  individually.  For  instance,  the
            hypertext  transfer  protocol –  secure  (HTTPS)  widely  adopted  in  recent  years  disables  the  awareness  by
            encrypting data flows from one end to the other. Thus, even though different types of data objects, e.g.,
            cacheable or non-cacheable, are transferred through the secure connection, it is not possible to differentiate
            the data objects and cache them selectively. On the other hand, DAN deals with individual data objects
            selectively for caching or processing because its security mechanism is applied for each data object rather
            than the connection.
            With this service scenario, network operators can use the network resource more efficiently by enforcing
            data flows to follow less utilized paths in the network. At the same time, network operators can also provide
            more elaborated service for end users since they can identify data flows and treat them differently based on
            the requirements. This service scenario shows a potential possibility of how DAN can be operated within the




                                                                                                           73
   78   79   80   81   82   83   84   85   86   87   88