차세대 서비스 오버레이 네트워크 플랫폼 기술

목차
I. 차세대 서비스 환경
II. 서비스 오버레이 네트워크
III. IEEE NGSON 표준동향
IV. ITU-T SIDE 표준동향
V. 관련 국내 활동
Summary

I. 차세대 서비스 환경
스마트 폰 가입자 100만
음성 < 데이터
융합 서비스 – SNS+위치+게임+..

개방+융합
통신 기술 + IT 기술

고객가치
서비스 플랫폼 요구

II. Service Overlay Network 개념
서비스 오버레이 네트워크 (SON)
– 물리적 노드 위에 구성된 논리적 네트워크로서, 서비스 제공을 위한
목적
• 예) No.7 신호망, 지능망, IMS AS, SDP
• 예) P2P, CCN, ..
• 예) dial up 인터넷, VPN,

Application level SON
– Application overlay
– Service overlay
Network level SON
– Service overlay
– Resource overlay

– Application level SON
Service virtualization
–Service virtualization is an emerging trend in the SOA
landscape that focuses on providing a common infrastructure
for building and managing a complex service ecosystem.
–Regardless of the technology, all service virtualization
architectures are centered on the idea of a service
intermediary sitting between the service client and the service
implementation
–A service intermediary is necessary to decouple the client from
the service implementation. In this type of architecture, clients
never interact with service implementations directly; they
always communicate through the service intermediary. The
service intermediary is where the virtual service is hosted and
exposed to consumers.

– Network level SON
Media oriented service composition
– 컴포짓 서비스에 대한 서비스 그래프를 기반으로 미디어 서비스를 위한 네트워크 와이드 서비스 컴포지션

– Service level SON
Enhanced Service delivery platform <- Today’s topic
Mobile P2P

III. IEEE P1903 표준동향
IEEE P1903 NGSON 표준동향
표준 범위 (Scope)
– IP기반 서비스 오버레이 네트워크 프레임워크로서, context-aware,
dynamic adaptive, self-organizing networking capability를 규격화
• Context aware : 요구된 QoS 수준, 서비스 타입 (실시간, 데이터), 데이터 스트림
특성별 (I-frame, B-frame), 단말 종류(TV, PDA) 별
• Dynamic adaptive: 지역 네트워크 등 정보를 활용해서, 네트워크 트래픽 흐름을 발견,
구성, 유지
• Self organizing networking: 고객 요구와 네트워크 능력에 근거해서 네트워크
구조를 재구성
의장단
• Chair : Rick Townsend (IEEE, Huawei)
• Vice-chair: 황진경 (KT), Wu Bin (China Mobile)

NGSON 개념
– IT, CT, Web 상에서의 각 서비스 인프라 기능을 통합
• 사업자급 서비스 지향 인터랙션 패러다임
• NGSON을 통해 서비스 생성 및 제공을 손쉽게 할 수 있어 Time to market 감소

표준 회의 연혁
기능 구조 문서 현황
기능구조

Service Publication and Discovery (SPD) FE
– service publication, service discovery, and service selection
–accepts the service publication requests and stores the static information of service, such
as functional description (interface, provider, service class, service template, service
name, service category), SLA, and QoS capabilities
– accepts the service discovery requests and returns the discovered results. If necessary,
this FE can provide context-aware service discovery

Service Register (SReg) FE
It handle service registration and service dynamic information of the service.
it maintains the dynamic information about the service which includes service state (e.g.
roaming status, activity status), physical address of service and etc.
It routes message for service according to dynamic information of service which is requested.

Service Routing (SR) FE
– provides the service routing capability in NGSON based on static and dynamic service
information.
– supports users or services to request the interaction with other services.
– investigates the message information and utilizes the context information from other
FEs (service directory, service register, IDM, context aware) to provide intelligent
routing.
– provides the control routing capability of internal control messages which are
exchanged between the other FEs.
– All control messages need to be forwarded by control routing capability of Service
Routing FE. At receiving a control message, control routing identifies a target FE, locates
the selected FE, and forwards the incoming message to the FE.

Identity Management (IDM) FE
– provides mechanisms to authenticate and authorize the identities of user and service.
– support to authenticate the identity of users before a user is authorized to use the
service.
– allow the user to use a unified ID to sign in to multiple services, without needing to
create new IDs or passwords, i.e., to achieve single sign on (SSO) ability. In order to
support this, the functionality of ID provider (IDP) should be included in the IDM FE.

Context Information Management (CIM) FE
The context dispatch function
- Providing current information or status of
the context sources to the requesting FE (e.g.,
Other FEs and services)
- The context sources can be a user, device,
network, application, or other NGSON nodes
that provide context information to the CIM FE.
- context information protection mechanisms
such as context resource security and
privacy policy supporting is required.
The context process function
- Modeling of different type of contexts and
reasoning
-In context modeling, the efficiency and
sample data structures used to express and
exchange general context information coming
from various context resources.
-In context reasoning, it derives many highlevel,
implicit contexts information from
various low-level context information.

Content Delivery (CD) FE
– CD FE includes working from a service to another service, from a server to an end
user, from an end user to another end user or from an end user to a server (for user
generated content).
–CD FE receives content from the content provider, stores, processes, and delivers it to
the Service Requestor using the capabilities of the network functions. The CD FE also
performs cache and storage functionalities

Service Portal (SP) FE
– allows users to access NGSON.
– provides interfaces to register the global ID of users,
authenticate the service request, publish user created content
or service, request content delivery, and activate or
deactivate service published in NGSON

Service Policy Decision Function (SPDF) FE
–provide the QoS control in NGSON architecture.
– QoS negotiation and assurance during service interaction.
– extract the service QoS requirement from service request,
and split the service QoS requirement into service related
QoS and transport related QoS.
–It inspects the resource state of the service providers and
enforces the service related QoS in the service level and send
the transport related QoS to the transport level.
– determine an efficient service routing path using the relevant
network context information such as routing distance, link
state, traffic flow, etc.
– The service routing path selected is sent to the underlying
networks.

(1) dynamic service chaining
(2) dynamic service instantiation.
– Depending on the result of Service A, one of the following will be executed:
–Service sequence 1: A-C
–Service sequence 2: A-D-B
–Service sequence 3: A-B
–Dynamic Chaining Specification: (Static) Chaining Order of A-C-D-B with the following
dynamic rules –
–Rule 1 - IF History contains (Service A, Result a), SKIP Service D and Service B
–Rule 2 - IF History contains (Service A, Result b), SKIP Service C
–Rule 3 - IF History contains (Service A, Result c), SKIP Service C and Service D

Service QoS is the total aggregate (end to
end) performance
–Service related QoS issues: service availability, accessibility, response time, throughput,
etc.
–Transport related QoS issues: bandwidth, end-to-end delay, packet loss rate, jitter, etc

In the service phases, there are dynamic
service selection (creation), dynamic service
composition, and dynamic service recomposition.
–The dynamic service provision can be achieved based on the dynamic
information like:
–Dynamic service adaptation by interaction with Context Awareness FE
–Dynamic service adaptation by interaction with S-PDF FE
–Dynamic service adaptation from the request of service user

Capability Information Exchange and Negotiation Function
When a new NGSON Node comes online, it exchanges its
capabilities (e.g., CPU & memory) with the Master Function
via R1 interface. Depending on these capabilities, the Master
Function will decide which NGSON FEs and IMS function to
be assigned to the NGSON Node.
Node Monitoring Function
To allow the Master Function to determine the health of all
NGSON Nodes, the Master Function will engage in a
heartbeat operation with all NGSON Nodes via R1 Interface
regularly. If a response is not forthcoming, the given node is
marked as dead, and its functions will be taken over by the
other nodes.
Role Modification and Re-assignment Function
The Master Function can dynamically modify or re-assign the
functions in an NGSON Node via R1 Interface for various
purposes such as for failure recovery, for load balancing, or
for performace improvement. Such function assignment may
change dynamically. It is thus necessary to have a notification
mechanism when this event happens. The Master Function is
required to notify all the appropriate nodes to allow autoconfiguration
of the network.
To support self-organization in NGSON over IMS, protocol
interactions are also required between the NGSON FE and
IMS Functions such as S-CSCF/P-CSCF (R2 Interface).

NGSON over IMS

NGSON over P2P
§ NGSON based Self Organization in P2P
– P2P node consists of NGSON FEs.
– NGSON can provide context-awareness function
to P2P networks like user context, device context
to enhance the sharing capabilities of P2P.
– NGSON can provide dynamic content adaptation
function to P2P networks to adapt content to suit
various devices of the users.
§ NGSON overlaying P2P
– Get content from P2P network
– Get resource from P2P network
– Enhance context awareness capabilities of
NGSON from P2P networks for efficient content
delivery functions.

P2P as NGSON services
1.P2P is registered as a service in NGSON.
2.Services/Users can get content from P2P network
3.Services/Users can get resource from P2P network
4.The End User or the Service can make P2P Service
requests to utilize the P2P Service.
5.Services/Users can experience enhanced context awareness
capabilities of NGSON from P2P networks for efficient
content delivery functions.

Interaction model:
–The interaction control function could be different for different resources. E.g. For web
services it may require NGSON to support WS-Security, WS-Agreement, WSInteraction,
etc.
–NGSON with Web requires SR FE to provide functions to support the control of service
interaction or access of service/service enablers.
§Delivery Model:
–blend the services from various industries and may optionally deliver it through a web
application.
§Composition Model:
–compose services available on Web and allow service/resource interfaces from Web to
be composable in NGSON.

IV. ITU-T 표준동향
Y. NGN-SIDE: Requirements for NGN Service Integration and
Delivery Environment
§NGN-SIDE provides an environment that enables the
development of applications that fully leverage all IP network
capabilities such as:
– enables developers to create compelling applications (e.g. mobile) that take
full advantage of all a device (e.g. smart phones, super phones ) has to
offer;
–provides access to a wide range of tools and technologies that can be used to
develop rich applications;

NGN-SIDE capabilities
8.1 NGN-SIDE capabilities related to integration layer
8.1.1 Service registry
8.1.2 Service orchestration
8.2 NGN-SIDE capabilities specific to integration
8.3 Relationship of NGN-SIDE capabilities with [ITU-T Y.2201]
capabilities
8.4 Relationship of NGN-SIDE capabilities with NGN-SIDE
framework
8.5 NGN-SIDE capabilities related to adaptation layer
8.5.1 Adaptation of capabilities offered by NGN
8.5.2 Adaptation of capabilities offered by non-NGN
8.6 NGN-SIDE capabilities related to service capability interface
8.7 NGN-SIDE capabilities related to cloud computing

Application layer
–supports in-house applications. In-house
applications may directly interact with the
capabilities of NGN or 3rd parties.
§Integration layer
– processes the service requests received
from service capability interface (e.g.
ANI/UNI/SNI) according to the service
requests’ communication needs.
§Adaptation layer
– performs adaptation based on integration
layer’s outcome to fulfill the service
requests.
– Adaptation includes control protocol and
media format adaptation, to access
capabilities from NGN and Non-NGN. These
capabilities can be specific network
functions, enablers or external service
delivery platforms

NGN-SIDE positioning within the NGN reference architecture

General Requirements
–NGN-SIDE is required to provide access control of third party
applications.
–NGN-SIDE is required to support the following cloud
computing service provisioning models :
• Software as a Service (SaaS);
• Platform as a Service (PaaS);
• IaaS (Infrastructure as a Service).
–NGN-SIDE can optionally support specific service brokering
capabilities for provisioning of the various cloud service
models in different deployment models.
–Support the exposure of underlying capabilities

Service brokering capability
– position in the adaptation layer of NGN-SIDE. It provides the interaction between
applications and enablers for the downward invocation of enablers and upward
triggering of applications.

서비스 시나리오 예 (enhanced conference)
1. The capabilities (mobile streaming capability of mobile streaming system, video
conference capability of video conference system, EPG and streaming capabilities of
IPTV system) are registered to NGN-SIDE by NGN provider so that developers can find
them and make use of them.
2. The Application provider develops a new application using the capabilities offered by NGN and NGN-SIDE, e.g. mobile streaming capability, EPG capability, IPTV streaming capability, video conference capability, storage capability, content adaptation capability and user profile capability, and using the service creation tools offered by NGN-SIDE. The Application provider publishes the application to NGN-SIDE.
3. User A can order a video conference through the App portal facilities. User A invites his/her team including User B, User C, User D, User E and User F to join the conference.
4. When the conference has been successfully created, the application sends the conference notification to the participants and the NGN-SIDE selects the notification method (e.g. SMS, IM, E-mail or the initiating a call) according to the participants’ presence and preference using the “management of role related information” capability offered by NGN-SIDE and the presence capability.
5. User C, User D and User F receive the invitation and join the conference, and the conference room becomes full.
6. User B, using a mobile phone, is notified that the conference room is full. The App server asks User B if he/she wants to watch the live meeting.
7. User E, using a Set Top Box (STB) to watch TV, is notified that the conference room is full. The App server asks User E if he/she wants to watch the live meeting.
8. When User B and User E select ‘Yes’, the App server uses the storage capability offered by NGN-SIDE to record the meeting’s real-time media.
9. The App server asks NGN-SIDE to convert the real-time media from video conference format to mobile streaming format to User B. The Mobile streaming system lives the video meeting to User B.
10. The App server asks NGN-SIDE to convert the real-time media from video conference format to IPTV streaming format to User E. User E receives a
notification, and a new channel of the conference appears on his/her STB’s service guide (EPG). User E selects the live meeting

V. 관련 국내 활동
KT 오픈 매쉬업 플랫폼
– KT 플랫폼 자원을 이용하여 서비스 컴포넌트의 매쉬업을 위한 Open API를 생성, 실행, 관리하기 위한 환경 제공 플랫폼 (MSP)
– 상황 정보 수집 API제공, 상황 관리 서버와 연동을 통한 개인화된 서비스 제공 예정

Future Network 2020
FN 2020 포럼 = 방송통신 + 지능형융합 + 지능형 SoC + 사물통신 + 미래인터넷
= Super Forum for Future New Network in Korea
서비스,응용 committee = 방송통신 + 지능형SoC + 융합서비스 + 무선인터넷
= 수많은 비즈니스를 가능하게 하는, 사회적인 기반이 되는 서비스
지능형 융합서비스 sub-committee (NGSON 국내 adhoc)
= 인프라형 융합서비스 연구 및 ICT/산업간 융합구조제시

Summary
차세대 서비스 플랫폼 요구사항
– 이용자, 단말, 네트워크, 서비스로부터 수집한 상황 정보 기반 intelligent service제공
– 서비스 오버레이 네트워크는 서비스 계층에서 융합을 위한 프레임워크를 의미
관련 표준기술 소개
– IEEE P1903
– ITU-T SIDE
통신망으로부터 Service overlay, 융합 서비스 기술로 접근
– Smart phone, Cloud computing 기술을 언급,포함
– 표준화가 잘 정리되는 ITU, IEEE에서 접근 시작
– 중국이 주도 하고 ITU/IEEE 에서 프레임워크 표준과 더불어 OMA, W3C 와 연계하여 진행
– 서비스 프레임워크 표준화에 국내 참여 필요