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

Core network aspects                                            1


            5)      While the end user moves to the DAN elements on the path, the user is able to receive the NDOs
                    required for automated driving.

            Figure 7-8 is a procedural diagram of DAN functions for automated driving service.
































                                    Figure 7-8 – Use case of automated driving with DAN
            1)      The end user sends the service provider a request for interactive data, e.g., position and traffic
                    NDOs, together with an expected route for automated driving.
            2)      The service provider informs all related DAN elements about the arrival of the authenticated vehicle
                    and requests interactive NDOs with the vehicle for its automated driving (labelled 2-1 in Figure 7-8).
                    The service provider offers the DAN elements (WAPs) its public key, which authorizes the DAN
                    elements to serve the requested NDOs.
            3)      Then the updated NDO is pushed to the DAN element from its connected sensors or newly pass
                    through  vehicles  if  some  special  events  occur,  e.g.,  an  accident  or  traffic  jam.  In  other  words,
                    updated NDOs may be uploaded by sensors or taken from new state information from in-vehicle
                    devices close to the DAN elements. Therefore, the updated NDO is available in DAN elements for
                    automated driving support (2-2).
            4)      The DAN element provides the end user with the desired NDO interactively when the end user
                    passes through the respective DAN element on a road. The NDO may be processed before being
                    served, in order to fit the capability of the end user's in-vehicle device.

            7.4.1   Benefits
            In order to detect hidden objects beyond a sightline, e.g., a child running around a corner or a car pulling out
            of an occluded driveway, an automated vehicle can communicate with static infrastructure, such as sensors
            on the road, which is connected to DAN elements (e.g., WAPs), or even with other vehicles in the vicinity. For
            vehicular ad-hoc networks used in current communication between vehicles, it is necessary to identify their
            locations  based  on  the  Internet  protocol  (IP).  However,  for  efficient  automated  capability,  the  whole
            communication system should focus on accessing content (rather than a particular destination) that can be
            supported by DAN.
            The user of automated driving can benefit from DAN due to its simple method of uploading and accessing an
            NDO via sensors. The automated vehicle only needs to specify the name or ID of the sensor data and send
            them to a connected DAN element, regardless of the final destination of the sensor data. The user of sensor
            data does not need to specify the location or address of the DAN elements. The service provider and network



                                                                                                           61
   66   67   68   69   70   71   72   73   74   75   76