Sabine, Very interesting direction. As wireless is already a main and future direction of settings of networking access, it makes sense to better support the settings.
Adding support, for example, a new address space, makes sense. One issue to elaborate more is use cases. A first use case coming to mind is access network selection. Do we do the design in an existing network setting (LTE), or target a more emerging network (e.g., in the context of 5G)? We have quite some wireless expertise from some members in the group, at least from the past. It will be interesting to hear their feedback. Richard On Sun, Mar 12, 2017 at 2:40 PM, Yichen Qian <[email protected]> wrote: > Hi Sabine, > > It is interesting to have such extensions to wireless network. I think > wireless network is not so stable as wired network. Many factors can > influence the cost between a UE and a connection node (such as channels). > So it may be difficult to get the accurate cost. Also a UE may have a lot > of moments in wireless network which makes it more difficult to get the > accurate cost. Is there some ways to solve the problem? > > Thanks, > Yichen > > > On Mar 10, 2017, at 9:30 PM, Randriamasy, Sabine (Nokia - FR) < > [email protected]> wrote: > > Hi all, > > Any thoughts in the WG on the following? > Thanks, > Sabine > > Pursuant to previous ALTO work on wireless networks and relating to the WG > item on ALTO metrics, there are a number of abstracted metrics reporting on > cellular and wireless networks worth considering. For instance, > applications on UEs may like to know about the connection costs associated > to the cells it is likely to connect to. These costs may for instance be > impacted by the cell load, see section 2.1 of [draft-randriamasy-alto-cost- > context]. > > Using cellular costs requires introducing a new address type and a new > identifier namespace for cells. Based on 3GPP standards, we may opt for the > name space "ECGI" and the related address format as suggested in section 4 > of [draft-rauschenbach-alto-wireless-access] that also proposes that to > map cells to PIDs covering cell IDs. > > Cellular connection costs (CCC for short) can be conveyed by for instance > the (Filtered) Cost Map (FCM) service or an extension of the Endpoint > Property (EPS) that could be added to [draft-roome-alto-unified-props]. > > A PID in a Network Map can cover a cell with an address from the address > space "ECGI". A PID thus hides the underlying technical aspects. The CCC in > a F/CM between a UE and a cell/PID can be encoded in the bi-directional, > uplink and downlink directions, within or across PIDs. A UE can retrieve > its “serving PID” via the Endpoint Property "PID" applied to its service > cell ID. > > _______________________________________________ > alto mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/alto > > > > _______________________________________________ > alto mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/alto > > -- -- ===================================== | Y. Richard Yang <[email protected]> | | Professor of Computer Science | | http://www.cs.yale.edu/~yry/ | =====================================
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
