Dear all,
Please find below the meeting minutes for the meeting on Dec 1, 2020.
In the beginning of the meeting, Sabine/Richard/Kai gave some updates on the
progress of existing WG documents. Richard suggested WG members putting efforts
on implementation and deployment of existing and future extensions.
Gang gave a wonderful talk on cellular extension. His talk listed some typical
applications that can take advantage of cellular information, and also
summarized what information is useful at both the UE level and cell/slice
level, including measured/predicted radio link status, measured loading/traffic
information, and predicted PRB usage. He also demonstrated how such information
can be obtained from two cellular frameworks: 3GPP and O-RAN. For the 3GPP
case, cellular information can be obtained from NEF as proposed in earlier
documents, while for the O-RAN case, such information is first collected by a
Near-RT RIC (RAN Intelligent Controller) through the E2 interface and then fed
to an ALTO server.
Some discussions for the talk:
Richard: What would be the inteface between the ALTO server and the Near-RT RIC
Gang: ALTO server be implemented as an xAPP on top of Near-RT RIC
Richard: How does the E2 interface provide the information? Pub-sub?
Gang: It depends on what xAPP is deployed.
Richard: The RAN does not directly provide information to UEs. The near-rt RIC
plays two roles: information aggregation/filtering and scaling
Richard: Does the ALTO server provide information that is directly translated
from metrics already defined in E2 interface?
Gang: Yes. ALTO server can be a good complement to the near-rt RIC
Richard: Should we invite Young Lee to present on openAPI?
Qin: OpenAPI can use YANG to model metrics but NEF also defines data models
that are not tight to YANG model. For O-RAN, it is related to ONF dealing with
whitebox devices. E2 is related to the telemetry inteface. GMI to support
pub/sub mechanism. SONiC also supports GMI/gRPC interfaces and also supports DB
architecture. They translate from the telemetry interface and the db inteface.
Chunshan: In 3gpp, openAPI is also used widely. Very few information can be
exposed according to 3gpp guidelines. Each UE has different channel status
because of different locations. How to provide this general information for all
the UE? It seems impossible. Only per-UE information is useful for the
application.
Open issues:
- Jensen will talk about the implementation of Path Vector and/or CDNI
- Richard will invite Young Lee to present in the next meeting
- Reserve 15-20 min to continue the discussion on cellular information
- Richard will give a talk on integration of ALTO and GAN-G
Please let me know if anything is missing or misinterpreted.
Best,
Kai
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
