2 research outputs found

    5G-PPP Software Network Working Group:Network Applications: Opening up 5G and beyond networks 5G-PPP projects analysis, Version 2

    Get PDF
    It is expected that the communication fabric and the way network services are consumed will evolve towards 6G, building on and extending capabilities of 5G and Beyond networks. Service APIs, Operation APIs, Network APIs are different aspects of the network exposure, which provides the communication service providers a way to monetize the network capabilities. Allowing the developer community to use network capabilities via APIs is an emerging area for network monetization. Thus, it is important that network exposure caters for the needs of developers serving different markets, e.g., different vertical industry segments. The concept of “Network Applications” is introduced following this idea. It is defined as a set of services that provides certain functionalities to verticals and their associated use cases. The Network Applications is more than the introduction of new vertical applications that have interaction capabilities. It refers to the need for a separate middleware layer to simplify the implementation and deployment of vertical systems on a large scale. Specifically, third parties or network operators can contribute to Network Applications, depending on the level of interaction and trust. In practice, a Network Application uses the exposed APIs from the network and can either be integrated with (part of) a vertical application or expose its APIs (e.g., service APIs) for further consumption by vertical applications. This paper builds on the findings of the white paper released in 2022. It targets to go into details about the implementations of the two major Network Applications class: “aaS” and hybrid models. It introduces the Network Applications marketplace and put the light on technological solution like CAMARA project, as part of the standard landscape. <br/

    5G-PPP Software Network Working Group:Network Applications: Opening up 5G and beyond networks 5G-PPP projects analysis

    Get PDF
    As part of the 5G-PPP Initiative, the Software Network Working Group prepared this white paper to demystify the concept of the Network Applications. In fact, the Network Application ecosystem is more than the introduction of new vertical applications that have interaction capabilities. It refers to the need for a separate middleware layer to simplify the implementation and deployment of vertical systems on a large scale. Specifically, third parties or network operators can contribute to Network Applications, depending on the level of interaction and trust. Different implementations have been conducted by the different projects considering different API types and different level of trust between the verticals and the owner of 5G platforms. In this paper, the different approaches considered by the projects are summarized. By analysing them, it appears three options of interaction between the verticals and the 5G platform owner: - aaS Model: it is the model where the vertical application consumes the Network Applications as a service. The vertical application deployed in the vertical service provider domain. It connects with the 3GPP network systems (EPS, 5GS) in one or more PLMN operator domain. - Hybrid: it is the model where the vertical instantiates a part of its Vertical App in the operator domain like the EDGE. The other part remains in the vertical domain. A similar approach has been followed in TS 23.286 related to the deployment of V2X server. - Coupled/Delegated: it is the model where the vertical delegates its app to the operator. The Network Applications will be composed and managed by the operator. This approach is the one followed in the platforms like 5G-EVE. In addition, the paper brings an analysis of the different API type deployed. It appears that the abstraction from network APIs to service APIs is necessary to hide the telco complexity making APIs easy to consume for verticals with no telco expertise and to adress data privacy requirements
    corecore