Hi Qin， For TS 23.501, TS 29.522, there have been latest version as follows and "h" means version 17. All of them have been approved by 3GPP plenary in June 2022 thus can be considered stable. https://www.3gpp.org/ftp/Specs/archive/23_series/23.501/23501-h50.zip https://www.3gpp.org/ftp/Specs/archive/29_series/29.522/29522-h60.zip
Regarding to how ALTO related to NEF or AF, I think NEF or AF is entity which can receive the exposed cellular network parameters (which is also the concern of current MoWIE draft). Whether NEF or AF can act as ALTO client or server, which is up to IETF to study and there is not constraints from 3GPP specs you listed. If NEF or AF can act as ALTO client, ALTO server maybe deployed in other place instead of the figure you pasted. These are quite much related to ALTO protocol design and I would like to hear more views and guidance from ALTO experts:-) Thanks a lot! Br, Yixue from Tencent Qin Wu <bill...@huawei.com> 于2022年7月20日周三 11:57写道： > Richard, Yiyue: > > I think two relevant 3GPP standard are 3GPP TS 23.501 version 15.3.0 > release 15, 3GPP TS 29.522 version 15.3.0 release 15, In 3GPP TS 23.501, > there is NEF architecture, > > N33 is specified by 3GPP TS 29.522, for C2 component, my impression, it > seems relevant to 3GPP interface in the above figure, might be not. > > So we need to understand how ALTO is related NEF N33 interface? Is ALTO > one of N33 implementation? Where ALTO server is placed in this figure? > > > > -Qin > > *发件人:* alto [mailto:alto-boun...@ietf.org] *代表 *Eric > *发送时间:* 2022年7月20日 10:13 > *收件人:* Y. Richard Yang <yang.r.y...@yale.edu> > *抄送:* IETF ALTO <alto@ietf.org> > *主题:* Re: [alto] Cellular information exposure discussion (Fwd: New > Version Notification for draft-huang-alto-mowie-for-network-aware-app-04.txt > > > > Hi Richard and Med, > > > > This is Yixue from Tencent who works in 3GPP for 15 years but new to > IETF.___^ . But actually from years ago, even in my Ph. D study, I like > reading some IETF and IRTF drafts and several years ago,I have noticed > ALTO WG in IETF as in Tencent my research and standard interests are > focusing on how application and network could coordinate. > > > > Regarding to the Med's question on whether the proposed extensions are > being discussed in 3GPP, let me try to give a brief answer. > > > > As we know, 3GPP has continuous efforts on network exposure even from 4G. > In 5G, network exposure is a native feature and in Rel-17 and Rel-18 there > are particular interest on how network exposure is utilized to optimized > advanced interactive services (like cloud gaming, AR, VR etc). From our > point of view, the main technical reason is that for these application, > there are more challenges which require more collaboration between > application layer and network layer to overcome. Just as we summarized in > MoWIE draft 04, 3GPP and also ETSI are working on some mechanism to enable > network exposure in a step-wise approach. > > > > Meanwhile, 3GPP is mainly focusing on standards within 5G system, in many > cases, there is inevitable case that the application servers may be > deployed at the data network outside 5G system gateway (i.e. UPF), to > achieve end-to-end application optimization, have some corresponding > standard work in IETF is also important from our view. > > > > To be more specific, by doing some cellular information exposing work in > 3GPP, in addition to the parameters within 5G system, some 3GPP > defined functionalities like AF, NEF, can have some ALTO related functions > to support cellular network information exposure to applications. How > application layer utilize the exposed information to optimize user > experience is not standardized in 3GPP which I also think may be considered > in IETF. I think this has been reflected by C1~C3 which Richard has listed > in previous e-mail. > > > > Thanks a lot! > > Br, Yixue from Tencent > > > > Y. Richard Yang <yang.r.y...@yale.edu> 于2022年7月20日周三 04:02写道： > > Hi Med, > > > > There are some efforts in 3GPP; the mowie draft discussed related 3GPP > efforts. I will let Tencent team (Yannis, Yixue, Yuhang) to give more info. > I do not believe there are related efforts in W2; that is, shorten the > feedback loop from passthrough-bounce to direct send. Zili can give an > update. I see that we need coordination with 3GPP, and we will reach out to > include those at 3GPP with related efforts and include them in the email > thread. Is this you would suggest? > > > > Thanks! > > Richard > > > > On Tue, Jul 19, 2022 at 12:19 PM <mohamed.boucad...@orange.com> wrote: > > Hi Richard, > > > > Thanks for this information. > > > > Just out of curiosity, are the proposed extensions currently discussed in > the 3GPP? > > > > Cheers, > > Med > > > > *De :* alto <alto-boun...@ietf.org> *De la part de* Y. Richard Yang > *Envoyé :* mardi 19 juillet 2022 20:14 > *À :* IETF ALTO <alto@ietf.org> > *Objet :* [alto] Cellular information exposure discussion (Fwd: New > Version Notification for draft-huang-alto-mowie-for-network-aware-app-04.txt > > > > > > Hi ALTO WG, > > > > During the weekly meeting today, the design team discussed about the > document, and suggested that the authors update the WG on a new version of > the MOWIE draft, which was uploaded last week and focuses on cellular > network information exposure to network-aware applications. The links to > the new version and the diff showing the updates can be found below. Any > comments, feedback, or interests in working together are welcome and > greatly appreciated. > > > > Using this email, we also want to include that there are two quite > relevant pieces of work: > W1. PBE-CC: Congestion Control via Endpoint-Centric, Physical-Layer > Bandwidth Measurements (https://arxiv.org/abs/2002.03475), by Yaxiong > Xie, Prof. Jamieson, and Prof. Rexford; > > W2. Achieving Consistent Low Latency for Wireless Real-Time Communications > with the Shortest Control Loop (paper to be made public soon), by Zili, and > Prof. Mingwei and team. > > > > It helps to use this email to point out a bigger picture of the problem > space and related work. One perspective is that the problem space consists > of 3 components: > > C1. What cellular-network information should be collected to be sent to > the applications? > > C2. How is the cellular information sent to the applications? > > C3. How do the applications use the information? > > > > It is important to note that the full exploration of the problem space is > not included in the current charter. However, this is an important problem > space and hence it helps to keep track of the progress and potential > impacts on ALTO. > > > > For C1, the impact will be the list of performance metrics. For C3, the > current ALTO charter does not include items to define application > behaviors, but it can be a point of discussion related to deployment. > > > > The most relevant component is C2. We discussed the following design > points for C2: > > D-broadcast: network broadcasts its state > > D-pass-bounce: network marks its state on pass-through packets and the > receiver bounces the state back to the sender > > D-direct-send: network sends its state to app directly > > Here by state it can be transformed state. > > > > Current ALTO is designed as D-direct-send. Due to lacking of deployment of > D-direct-send in cellular network, aforementioned W1 uses D-broadcast; the > D-pass-bounce design need at least a round trip time and couples network > feedback flow with data flow, leading to the aforementioned W2 work. > > > > Many of us feel that the time is ready for introducing a highly efficient, > flexible channel for network state exposure to applications, led by IETF, > and the ALTO team can be a good starting point. As a first step, a > systematic evaluation, which (1) surveys the design space and (2) > introduces the use cases/benchmarking scenarios, can be a good starting > point. > > > > If there is time available in the coming 114 meeting, we can discuss more > during the presentation. Otherwise, on-list discussion is a good starting > point. We will follow up with more analysis on the list soon but use this > email to get the conversation started. > > > > Thanks, > > > > Richard on behalf of Tuesday meeting team > > > > > > > > ---------- Forwarded message --------- > From: <internet-dra...@ietf.org> > Date: Mon, Jul 11, 2022 at 2:14 PM > Subject: New Version Notification for > draft-huang-alto-mowie-for-network-aware-app-04.txt > To: Y. Richard Yang <yang.r.y...@yale.edu>, Gang Li < > ligan...@chinamobile.com>, Sabine Randriamasy < > sabine.randriam...@nokia-bell-labs.com>, Yixue Lei <yixue...@tencent.com>, > Yuhang Jia <tony...@tencent.com>, Yunbo Han <yunbo...@tencent.com>, > Yunfei Zhang <yanniszh...@tencent.com> > > > > > A new version of I-D, draft-huang-alto-mowie-for-network-aware-app-04.txt > has been successfully submitted by Y. Richard Yang and posted to the > IETF repository. > > Name: draft-huang-alto-mowie-for-network-aware-app > Revision: 04 > Title: MoWIE for Network Aware Applications > Document date: 2022-07-11 > Group: Individual Submission > Pages: 25 > URL: > https://www.ietf.org/archive/id/draft-huang-alto-mowie-for-network-aware-app-04.txt > Status: > https://datatracker.ietf.org/doc/draft-huang-alto-mowie-for-network-aware-app/ > Htmlized: > https://datatracker.ietf.org/doc/html/draft-huang-alto-mowie-for-network-aware-app > Diff: > https://www.ietf.org/rfcdiff?url2=draft-huang-alto-mowie-for-network-aware-app-04 > > Abstract: > With the quick deployment of 5G networks in the world, cloud-based > interactive applications (services) such as cloud gaming have gained > substantial attention and are regarded as potential killer > applications. To ensure users' quality of experience (QoE), a cloud > interactive service may require not only high bandwidth (e.g., high- > resolution media transmission) but also low delay (e.g., low latency > and low lagging). However, the bandwidth and delay experienced by a > mobile and wireless user can be dynamic, as a function of many > factors, and unhandled changes can substantially compromise the > user's QoE. In this document, we investigate network-aware > applications (NAA), which realize cloud based interactive services > with improved QoE, by efficient utilization of a solution named > Mobile and Wireless Information Exposure (MoWIE). In particular, > this document demonstrates, through realistic evaluations, that > mobile network information such as MCS (Modulation and Coding Scheme) > can effectively expose the dynamicity of the underlying network and > can be made available to applications through MoWIE; using such > information, the applications can then adapt key control knobs such > as media codec scheme, encapsulation, and application layer > processing to minimize QoE deduction. Based on the evaluations, we > discuss how the MoWIE features can define extensions of the ALTO > protocol, to expose more lower-layer and finer grain network > dynamics. > > > > > The IETF Secretariat > > > > -- > > Richard > > -- > > Richard > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete > this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > > Thank you. > > -- > > Richard > > _______________________________________________ > alto mailing list > alto@ietf.org > https://www.ietf.org/mailman/listinfo/alto > >
_______________________________________________ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
