Công Nghệ Thông Tin, it, phầm mềm, website, web, mobile app, trí tuệ nhân tạo, blockchain, AI, machine learning - Công Nghệ Thông Tin, it, phầm mềm, website, web, mobile app, trí tuệ nhân tạo, blockchain, AI, machine learning - Điện - Điện tử - Viễn thông AMDOCS NETWORK SERVICE EXPOSURE PLATFORM White Paper 2 White PaperAmdocs Network Service Exposure Platform Table of contents 01 Introduction 03 Page Business context 02 04 Amdocs Network Service Exposure Platform (NSEP) 03 06 Summary 04 09 3 Introduction To maximize the variety of their service offerings to both internal users and external partners, CSPs require a platform that can manage service agility and network complexity, as well as expose service infrastructure capabilities via APIs. Moreover, to support the use cases demanded by digital customers, such a platform must also be aligned with and support network standards that include 3GPP, TMF, CAMARA, TIP and more, and have the flexibility to expand beyond standard APIs so that they can uniquely customize the required capabilities. Network-as-a-platform (NaaP) was created to address the stringent needs to provide low latency, accurate device monitoring, optimum functions app placement, strong privacy and security, all while conforming with cloud-native and disaggregation principles. Furthermore, with its future-proofed service infrastructure, applications’ cloud-native character and ability to consume basic network services via abstract APIs and data models, it is able to support B2B and B2B2X collaboration. NaaP is built on three design principles. The first is the need for a unified service model and catalog that can serve as a single source of truth across the business, IT, and network layers. The second is the ability to abstract network APIs from serviceproduct APIs to enable independent development, testing and integration in both IT and network domains, as well as with partners. Importantly, these must be able to occur in parallel, as well as in a decoupled manner, to allow for service velocity and scale. At the same time, it must conform as closely as possible with open standards to minimize silo creation and technical debt accrual. The third principle is having highly configurable data model-driven decomposition and orchestration , which enables the NaaP and isolation layer to not only support B2B and B2C communication services, but also services that support B2C, B2B and B2B2X. To comply, network service providers must do the following in a safe and agile manner: Open their network menu Expose APIs to consumers, businesses and partners in an application developer-friendly manner Create a service creation ecosystem for developers Expose new network and IT capabilities White PaperAmdocs Network Service Exposure Platform 4 White Paper Amdocs Network Service Exposure Platform This whitepaper addresses factors for boosting network service velocity, strategies for extracting maximum value from a traditional network- or service-centric strategy, and as a result delivering enhanced NaaP capabilities. As customers demand new, differentiated 5G services, and as CSPs strive to achieve vertical specialization and extended businessoperational footprints through hyperscaler and metaverse ecosystems, the pressure on CSPs has never been greater. To achieve these objectives, these players are constantly on the search for agile business operating models and partnerships. Yet such models and partnerships must be able to provide solutions to support a network whose complexity far surpasses that of 4G: with more layers, more network functions, as well as a shift to software and cloud-native principles and tools, while being programable and self-configurable. Business context DOCSIS Fiber Deep Mobile 4G Mobile 5G Mobile CBRS Partners Network Elements Clouds User Devices Operations Monitoring, Assurance Analytics Design Design, Model, Onboarding Fulfillment Service Ordering, Orchestration, Configuration Monetization Revenue Management Exposure Network-as-a-Service (NaaS) Layer TMF APIs MEF LSO APIs OPEN APIs Proprietary APIsCAMARA APIs Platform Users AggregatorDeveloper Enterprise Marketplace Internal Telco Other telcos Expose Network Principles The answer lies in deploying an intermediate software layer both between IT and the network, as well as between the customer and operator – forming an end-to-end solution comprising an environment that has the power to support the simple creation and consumption of bundled capabilities. The benefits of this “as a platform” concept range from scalability and lightweight operational capability management, all the way to reduced integration costs. The ability to leverage such benefits becomes particularly crucial in any environment where the diversity and scale of tech demands are constantly growing and evolving. Examples include the need 5 White Paper Amdocs Network Service Exposure Platform to adjust network behavior in real time, support drone networks for equipment maintenance (e.g., in farming and engineering use cases) and AR VR applications. Inevitably, such complexity will only grow with the next wave of consumer and enterprise services on the horizon, with autonomous vehicles, electric flying vehicles (eVTOL) and smart cities, all of which will require high bandwidth, carrier-grade reliability, and cost efficiencies. Support too will need to be found for evolving customer expectations. While previously, services on-demand would suffice, demand is now growing for online services, coupled with new connectivity options (including 5G), as well as support for highly accurate visibility and monitoring. To ensure full lifecycle management for such solutions, enterprise partners will need to build their own services and make them available within the network operator ecosystems. For a glimpse into this future reality, we need look no further than verticals, such as retail and entertainment, that have already adopted this approach with the following outcomes: New services created to meet new demands in days rather than months Easy, rapid creation and integration of new services that can be charged for in simple and in novel ways Ability for app providers to leverage network capabilities: − Extract information from network − Control networking, applications, services, and functions on demand New business models that support offer bundling, including: − Leveraging the network, cloud-native functions, and vertical applications − Shuffled as a platform − Available on demand − Ability to support industry-specific use cases − Made available through API exposure Yet to realize these benefits, these players first had to evolve their service infrastructure to become more cloud native-driven, flexible, self-optimized and specialized. On the flipside, such capabilities came at the cost of introducing multi-dimensional complexities resulting from the diversity of network suppliers, function and testingvalidation, and evolution requirements. In addition to the above, CSPs in pursuing similar goals, will also face industry-specific 5G challenges such as massive traffic volumes and growing numbers of connected devices. In their favor, standards bodies from TMF, ETSI, O-RAN Alliance, TIP and Linux Foundation (CAMARA project) are already addressing this problem with prescribed open interfaces and reference implementations. Based on our long-standing involvement in these bodies, as well as our established leadership in BSS and OSS, Amdocs is frequently approached by the operator community for our experience and expertise in bridging the gaps between IT and network. 6 White PaperAmdocs Network Service Exposure Platform Amdocs Network Service Exposure Platform (NSEP) Network Service Exposure Platform (NSEP) Amdocs’ vision uses software engineering techniques to build a networ...
Trang 1SERVICE EXPOSURE PLATFORM
Trang 2Table of contents
Page
Business context
Amdocs Network Service Exposure Platform (NSEP)
Summary
Trang 3Introduction
To maximize the variety of their service offerings
to both internal users and external partners, CSPs
require a platform that can manage service agility
and network complexity, as well as expose service
infrastructure capabilities via APIs
Moreover, to support the use cases demanded by
digital customers, such a platform must also be
aligned with and support network standards that
include 3GPP, TMF, CAMARA, TIP and more, and
have the flexibility to expand beyond standard APIs
so that they can uniquely customize the required
capabilities
Network-as-a-platform (NaaP) was created to
address the stringent needs to provide low latency,
accurate device monitoring, optimum functions/
app placement, strong privacy and security, all while
conforming with cloud-native and disaggregation
principles Furthermore, with its future-proofed
service infrastructure, applications’ cloud-native
character and ability to consume basic network
services via abstract APIs and data models, it is able
to support B2B and B2B2X collaboration
NaaP is built on three design principles The first is
the need for a unified service model and catalog
that can serve as a single source of truth across the business, IT, and network layers
The second is the ability to abstract network APIs from service/product APIs to enable independent
development, testing and integration in both IT and network domains, as well as with partners Importantly, these must be able to occur in parallel,
as well as in a decoupled manner, to allow for service velocity and scale At the same time, it must conform as closely as possible with open standards
to minimize silo creation and technical debt accrual
The third principle is having highly configurable data model-driven decomposition and orchestration,
which enables the NaaP and isolation layer to not only support B2B and B2C communication services, but also services that support B2C, B2B and B2B2X
To comply, network service providers must do the following in a safe and agile manner:
• Open their network menu
• Expose APIs to consumers, businesses and partners in an application developer-friendly manner
• Create a service creation ecosystem for developers
• Expose new network and IT capabilities
Trang 4This whitepaper addresses factors for boosting
network service velocity, strategies for extracting
maximum value from a traditional network- or
service-centric strategy, and as a result delivering
enhanced NaaP capabilities
As customers demand new, differentiated 5G
services, and as CSPs strive to achieve vertical
specialization and extended business/operational
footprints through hyperscaler and metaverse
ecosystems, the pressure on CSPs has never been
greater To achieve these objectives, these players
are constantly on the search for agile business/
operating models and partnerships
Yet such models and partnerships must be able
to provide solutions to support a network whose
complexity far surpasses that of 4G: with more
layers, more network functions, as well as a shift
to software and cloud-native principles and tools,
while being programable and self-configurable
Business context
Operations Monitoring, Assurance Analytics
Design Design, Model,
Onboarding
Fulfillment Service Ordering, Orchestration, Configuration
Monetization Revenue Management
Exposure Network-as-a-Service (NaaS) Layer
TMF APIs MEF LSO APIs OPEN APIs CAMARA APIs Proprietary APIs
Platform Users Developer Enterprise Aggregator Marketplace Internal Telco Other telcos
Expose Network Principles
The answer lies in deploying an intermediate software layer both between IT and the network,
as well as between the customer and operator – forming an end-to-end solution comprising
an environment that has the power to support the simple creation and consumption of bundled capabilities The benefits of this “as a platform” concept range from scalability and lightweight operational capability management, all the way to reduced integration costs
The ability to leverage such benefits becomes particularly crucial in any environment where the diversity and scale of tech demands are constantly growing and evolving Examples include the need
Trang 5to adjust network behavior in real time, support
drone networks for equipment maintenance (e.g.,
in farming and engineering use cases) and AR/
VR applications Inevitably, such complexity will
only grow with the next wave of consumer and
enterprise services on the horizon, with autonomous
vehicles, electric flying vehicles (eVTOL) and smart
cities, all of which will require high bandwidth,
carrier-grade reliability, and cost efficiencies
Support too will need to be found for evolving
customer expectations While previously, services
on-demand would suffice, demand is now growing
for online services, coupled with new connectivity
options (including 5G), as well as support for highly
accurate visibility and monitoring To ensure full
lifecycle management for such solutions, enterprise
partners will need to build their own services and
make them available within the network operator
ecosystems
For a glimpse into this future reality, we need
look no further than verticals, such as retail and
entertainment, that have already adopted this
approach with the following outcomes:
• New services created to meet new demands in
days rather than months
• Easy, rapid creation and integration of new
services that can be charged for in simple and in
novel ways
• Ability for app providers to leverage network
capabilities:
− Extract information from network
− Control networking, applications, services, and
functions on demand
• New business models that support offer
bundling, including:
− Leveraging the network, cloud-native functions,
and vertical applications
− Shuffled as a platform
− Available on demand
− Ability to support industry-specific use cases
− Made available through API exposure
Yet to realize these benefits, these players first had
to evolve their service infrastructure to become more cloud native-driven, flexible, self-optimized and specialized On the flipside, such capabilities came at the cost of introducing multi-dimensional complexities resulting from the diversity of network suppliers, function and testing/validation, and evolution requirements
In addition to the above, CSPs in pursuing similar goals, will also face industry-specific 5G challenges such as massive traffic volumes and growing numbers of connected devices In their favor, standards bodies from TMF, ETSI, O-RAN Alliance, TIP and Linux Foundation (CAMARA project) are already addressing this problem with prescribed open interfaces and reference implementations Based on our long-standing involvement in these bodies, as well as our established leadership in BSS and OSS, Amdocs is frequently approached
by the operator community for our experience and expertise in bridging the gaps between IT and network
Trang 6Amdocs Network
Service Exposure
Platform (NSEP)
Amdocs’ vision uses software engineering
techniques to build a network abstraction and
exposure layer that modularizes and decouples the
network from IT This ensures ordering issues remain
with IT, while network teams provide the “how” of
creating a service
Meanwhile, partner capabilities can be used to
compose or enrich network service capabilities,
which can be subsequently exposed alongside other
network APIs to formalize customer end-to-end
solutions
As part of the network abstraction layer, we provide
the following key capabilities:
• Service catalog to define network services,
validation rules and API parameters
Trang 7• API management of the integration layer,
providing access to network capabilities via a
variety of APIs
• Network services & edge orchestration for highly
configurable, data model-driven decomposition
and orchestration
• Service fabric including access to the network
service topology with network capability
definitions
• Event monitoring & analytics framework
• Charging trigger component that triggers new
chargeable events to update billing
• Security for access & usage policies
• Operational portals for CSP NetOps and
partners
Taking this approach a step further, our broad
view of service lifecycle management addresses
the requirements of network, service and IT, as
well as the delivery of data and control via
pre-programmed service behaviors (also known as
“intents”) This ensures relevant requests are routed
to relevant functions via closed-loop automation,
based on the scope of each request So for
example, while a request to change session quality
would be sent directly to the network, a QoS
request to change the entire service for all users
would be routed through the network abstraction
layer
Illustrative steps for presenting a service to customers
Use case example:
network service edge and lifecycle management
5G services, such as network slicing and mobile private networks, can be extremely complex and span several domains, including those of solution partners Their definition and management must
be designed to handle partial failure and therefore incorporate either open or closed loops (for
autonomous corrective behavior) Some illustrative steps for presenting such services are provided in the diagram below
The following is an example for 5G service monetization
• Network catalog and network orchestration
− Onboard network functions and network applications are required for end-to-end service creation
− Define and design new services with all service elements, including 5G slice definition
− Define service lifecycle management operational and orchestration policies
− Deploy service definition across network ecosystem
− Expose new service definition from network catalog to IT service catalog
Trang 8• IT product catalog and customer order
orchestration
− Define sellable product, price it, define offering
and discounts (e.g low latency connectivity)
− Export sellable product specification into service
catalog
• ITservice catalog and service orchestration
− Import network service definition from network
catalog
− Import sellable product specification from
commercial catalog
− Define customer-facing services and use those
definitions as mapping between commercial
products and network services; define mapping
and re-use policies
This unique, unified approach across IT and network, enables integrated, yet decoupled single orchestration responsibilities – from catalog and design tooling to IT service order orchestration and network service orchestration Furthermore,
by enabling varied cadences and model-driven integration, such a separation also avoids the need for further operational costs
Trang 9Summary
Network exposure comes in a variety of shapes
and formats that seek to meet the expanding and
evolving requirements of the business, as well as
those of collaborative partners like wholesale CSPs
and hyperscalers/metaverse ecosystems
Meanwhile, 5G exposure is rooted in the NEF
(Network Exposure Function) and its ability to
expose and facilitate collaboration with trusted
and untrusted B2B and B2B2X partners, while
also safeguarding the exchange with the other 5G
network functions Furthermore, it also interfaces
with PCC (policy, control and charging), within which
PCF and CHF play key roles
Another aspect of network exposure is
Network-as-a-Service (NaaS), which enables CSPs/MNOs to
provide a finer definition of a turnkey solution based
primarily on an underlay/overlay connection offering
such as carrier-ethernet, MPLS-TE & SR-VPN or
SD-WAN Connectivity is then supplemented with other
capabilities, such as the edge with MEC devices and
edge-based applications, security with SASE and
zero-trust framework, vertical applications and even
customer-located functions such as vCPE or uCPE
Yet it’s “network-as-a-platform” that takes
the crown for complexity And it’s precisely this
complexity that allows it to support solutions on an
entirely other level
With a unique and innovative approach incorporating all of the above, Amdocs Network Service Exposure Platform provides CSPs and their partners with a wealth of benefits that include:
• Network catalog-integrated API management,
service fabric and orchestration
• Network API exposure management supporting a
variety of API options
• Service decomposition and orchestration to
support service lifecycle management
• Federated service fabric with support for the
network, cloud and edge service topology
• Single developer and operational portal
• Service integration services designed to help
customize Amdocs NSEP (Network Service Exposure Platform), uniquely defining the face of your business and market positioning and empowering to meet your customers’
expectations Yet it’s “network-as-a-platform” that takes the crown for complexity And it’s precisely this complexity that allows it to support solutions on an entirely other level:
• Ability to expand standard APIs as required by customers and use cases
• Independence and flexibility for constant evolution, testing, and validation (CI/CD methodologies)
• Ability to drive new revenue models with enterprise and developer communities
• An entirely new level of differentiated services that ensure a truly enhanced user experience
Trang 10degree to which the enterprise wishes to manage its network operations
Leveraging our vendor experience, flexible
solution blueprints, and mobile private network deployment experience, we provide a single point
of accountability for committed SLAs, while
minimizing risks associated with mobile private network implementations Meanwhile, our global delivery and support organization – spanning RAN, core, cloud, IT, system integration, transport, security, and software domains – enables us to manage all the complexities of an end-to-end mobile private network solution
With our combination of deployment and
automation, mobile private network management portal, and AI-enabled operations services, we lead the industry in enhancing the customer experience, while improving overall operational efficiencies
To learn more, visit Amdocs Networks and discover
our other exposure solutions