LTV, VoD, PVR, TsTV … • Convergence services
• Common underlying network control and E2E QoS mechanisms • Unified user profile management • Unified charging and billing • Support for multiple access technologies and different types of
end devices • Support for mobility (roaming/nomadism) • …
NGN could be an ideal foundation architecture for IPTV
3
ITU-T
ITU-T IPTV Global Technical Workshop Seoul, Korea, 12-13 October 2006
IPTV domains
Consumer
Content Provider Service
Provider
Network Provider
Consumer Networks Consumer Devices
Access Metro Core
Control
ManagementDelivery
Content
4
ITU-T
ITU-T IPTV Global Technical Workshop Seoul, Korea, 12-13 October 2006
IPTV Functional Blocks
Consumer
Content Provider
Service Provider
Network Provider
Delivery Network Gateway DNG
Network Interface Hybrid & Storage DRM & Codecs
Client Applications & components
Content Source File off-line
Content Source Stream off-Air
Content Ingestion and encoding
Content Distribution
DRM sub-systems
IPTV Applications
IPTV Portal
Web Portal
Call Centers
Service Scheduling
IPTV Components
IPTV Subscriber Management CRM Billing
VSO Streaming Broadcast & VoD
VHO Streaming Broadcast & VoD
SHE Streaming Broadcast & VoD
Video Serving Office VSO
Video Hub Office VHO
Super Head End SHEAccess
RACS Resource & Admission Control
NASS Network Attachment
ITF
Content Delivery Management
5
ITU-T
ITU-T IPTV Global Technical Workshop Seoul, Korea, 12-13 October 2006
IPTV architecture based on NGN
Transport stratum
Service stratum
Control Media
M an
ag em
en t
Fu nc
tio ns
Management
ANI
Transport Control Functions
Resource and Admission
Control Functions
Network Attachment Control Functions
Network Attachment Control Functions
NNIUNI
Note: UNI/NNI/ANI are not meant to represent any specific interfaces. (...) Application Support Functions & Service Support Functions
Applications
Transport Functions
End-User Functions
Other Networks
Service Control Functions
Service User Profiles
Service User Profiles
Transport User Profiles
Transport User Profiles
common subsystems and components to be shared
providing IPTV supporting functions:
•IPTV Portal •DRM sub-systems •Service scheduling •Content Ingestion and coding •Content Distribution •Others …
providing IPTV service control functions: •Registration, authentication, authorization •Session control •Media distribution and delivery control •Service trigger and routing •charging •Roaming/nomadism management •Handover control …
could be a dedicated IPTV service control component or Extend IMS core to support IPTV Service control
common enablers to be shared:Location,Presence , Message etc.
(...) DSL, 3G, DVB-T/H etc. — Different access technologies share the common IPTV service
control functions and the common applications&services supporting functions.
— Adaptation may be needed for different access technologies.
8
ITU-T
ITU-T IPTV Global Technical Workshop Seoul, Korea, 12-13 October 2006
Issues related to NGN/IMS based IPTV
o Streaming media services, e.g.
Language:English
Score: 471544.2
-
https://www.itu.int/dms_pub/it.../06/16/T06160000060001PDFE.pdf
Data Source: un
Functional requirements and architectures for ubiquitous networking via NGN
Identification of entities, their functions, and reference points, required to provide telecommunications services to support ubiquitous networking. This includes the need for functional reference models, taking into consideration key themes to support ubiquitous environments, and the addition of new functions and/or modification of existing functions. (...) Reference model and functions for customer manageable and home networks
Develop models and functions to allow customers to create, configure, customize, and otherwise customize the network services/resources allocated to them by the network provider, and to allow involvement of third parties in the development of network-supported applications.
Language:English
Score: 471275.24
-
https://www.itu.int/ITU-T/studygroups/com13/sg13-q5.html
Data Source: un
R e s t P r i o r i t y R e s t o r a t io n p r i o r i t y l e v e l s in N G N 0 4 - 2 0 0 7
Y . f l o w r e q R e q u i r e m e n t s f o r t h e s u p p o r t o f s t a t e f u l f lo w - a w a r e t r a n s p o r t t e c h n o l o g y in N G N
0 4 - 2 0 0 7
Y.2111/Y.RACFY.2111/Y.RACF
Y.2171
Y.123.qos
Y.enet
Y.mpmY.RestPriority
Y.e2eqos.1
Y.flowreq
admission priority
restoration priority
performance management
resource request authorization
resource management
resource management
resource management
6
ITU-T
ITU-T/OGF Workshop on Next Generation Networks and Grids Geneva, 23-24 October 2006
Resource and Admission Control Functions
Other Networks
Service Control Functions
Transport stratum
Service stratum
M an
ag em
en t
Fu n
ct io
n s
Service User Profiles
Service User Profiles
Transport User Profiles
Control Media Management
Application/Service Functions
3rd Party Applications ANI
End-User Functions
Transport Control Functions
Resource & Admission Control Functions
Network Attachment
Control Functions
Network Attachment
Control Functions
Transport Functions
NNIUNI
(See ITU(See ITU--T Rec. (...) Y.2012/Y.NGN--FRA)FRA)
Resource and Admission Control Functions (RACF) Provide application-driven, policy-based resource management Bridge service control and packet transport to dynamically guarantee QoS and enforce certain network security measures
7
ITU-T
ITU-T/OGF Workshop on Next Generation Networks and Grids Geneva, 23-24 October 2006
ITU-T RACF Architecture
Policy Decision Functional Entity (PD-FE) o Authorizes resource requests based on policy o Configures the transport to enforce policy
Transport Resource Control Functional Entity (TRC-FE) o Tracks resource usage & network topology o Makes resource-based admission decision
Policy Enforcement Functional Entity (PE-FE) o Enforces policy for NAPT, gating, rate limiting, packet
marking, etc.
typically part of border transport elements (e.g. edge router and
border gateway)
service-independent, transport-dependent,
segment-specific
service-facing, transport-independent
Rs (Diameter)
Rw (H.248, COPS, Diameter)
Service Stratum
Transport Functions
PD-FE TRC-FE
RACF
Transport Stratum
Service Control Functions (IMS or non-IMS)
Rt (Diameter)
Rd Rp
Rc (COPS, SNMP)Rn
(Diameter) Ru
Ri
TRE-FE PE-FE
Network Attachment Control Functions
intra- domain inter-
domain
(See ITU(See ITU--T Rec. (...) Y.2111/Y.RACF)
O ther N
G N
s
8
ITU-T
ITU-T/OGF Workshop on Next Generation Networks and Grids Geneva, 23-24 October 2006
More RACF Specifics
Support for o Relative and absolute QoS, including priority o Endpoints of varied QoS control capabilities o Push and pull modes for policy control o Various resource management methods based on
accounting, measurement and reservation o Existing and emerging transport QoS mechanisms
9
ITU-T
ITU-T/OGF Workshop on Next Generation Networks and Grids Geneva, 23-24 October 2006
Push and Pull Modes
Pull Mode
User Equipment
RACF
Transport Functions
Service Control Functions
1
5
4
2
6
3 Policy
User Equipment
RACF
Transport Functions
Service Control Functions
1
7
3
5
6
2
4
Token
T
Policy
T T
8
Push Mode
Application Signaling RACF Control Transport QoS Signaling
(Token-free operations are also possible.)
10
ITU-T
ITU-T/OGF Workshop on Next Generation Networks and Grids Geneva, 23-24 October 2006
Options for Admission Control in TRC-FE
Depending on operator policy and network specifics: o NULL (such as in over-engineered core networks) o Accounting-based
• Keep track of the consumed resources from a resource pool o Measurement-based (in-band or out-of-band)
• Audit resource use in the transport periodically via SNMP, or • Measure directly network performance edge-to-edge(or end-to-end) via
RTCP or active/passive probes o Part of native transport admission control
• For example, MPLS routers/switches track resource use and LSP map o In conjunction with native transport resource reservation
• Trigger native transport resource reservation and make admission decision based on the reservation result
o A combination of the above • Different solutions according to services and/or network domains
11
ITU-T
ITU-T/OGF Workshop on Next Generation Networks and Grids Geneva, 23-24 October 2006
A Configuration Example
The PE-FE can reside in the o Gateway GPRS Support Node o Packet Data Serving Node o Cable Modem Termination System
o Access Node o Edge Node o Border Gateway
Network Attachment
Control Functions
Ru
Service Control Functions
Access Network
RwRw Rc
Rt
PD-FE
Service Control Functions
TRC-FE
Core Network PE-FE
RwRw Rc
Rt
PD-FE
TRC-FE
Rp
PE-FE
Rs
Access Network
RwRw Rc
Rt
PD-FE
TRC-FE
PE-FEPE-FEPE-FEPE-FE
Network Attachment
Control Functions
Ru
Service Control Functions
Rs
RiRi
Customer Premises
Equipment/ Network
Customer Premises
Equipment/ Network
12
ITU-T
ITU-T/OGF Workshop on Next Generation Networks and Grids Geneva, 23-24 October 2006
Summary
o NGN QoS is an active standardization area in the ITU-T o RACF for dynamic, application-driven resource management plays a
central role • Y.2111/Y.RACF (on the architecture and requirements for Release 1) and
Y.2171/Y.CACPriority about to be approved • RACF protocols are under development in SG 11 • Draft new Recommendations Y.123.qos and Y.enet address the application of
RACF to Ethernet environments o Other aspects are addressed by new draft Recommendations underway
(Y.mpm, Y.e2eqos.1, Y.flowreq, Y.RestPriority, etc.) o Close cooperation among relevant SDOs is essential to the development
of consistent and interoperable standards o Discussion of the impacts of Grids is in order
Language:English
Score: 471044.4
-
https://www.itu.int/ITU-T/work...grid/presentations/s4p1-lu.pdf
Data Source: un
The author functions should continue to be decentralized in the bureaus .
(...) Encl. : 2 annexes per text
In the context of the GoS recommendations, the usage of the word “duplication” signified that two or more functional units may be carrying out identical or similar functions. (...) Sales and Marketing are two functions within the same administrative unit “SC/SAMA”.
Language:English
Score: 470725.93
-
https://www.itu.int/council/CO...stricted1/cog07_04e_rec8-2.doc
Data Source: un
This management response has been prepared by the management of UNICEF in response to the annual report for 2021 on the evaluation function in UNICEF (E/ICEF/2022/17). It comments on progress within the evaluation function in 2021 and assesses trends in performance during the 2018–2021 quadrennium. (...) Management expresses its satisfaction with the progress of the evaluation function in 2021 and reaffirms its commitment to the continued strengthening of the function.
(...) Management requests the evaluation function to continue to steadily enhance the quality of all aspects of evaluations.
Language:English
Score: 470681.2
-
https://www.unicef.org/executi...luation_function_MR-EN-ODS.pdf
Data Source: un
III. Internal Audit Function in UNIDO
Nature and scope of the function
5. (...) Synergies with evaluation function
26. Notwithstanding the different roles and the different nature of the three functions of EIO (internal audit, evaluation, and investigation), there are commonalities and opportunities for synergies, particularly between the internal audit and evaluation functions. The work plans of the internal audit function and the evaluation function shall generally be reconciled to supplement each other and to avoid any unnecessary duplication or overlap.
Language:English
Score: 470681.2
-
https://www.unido.org/sites/de...Audit%20Policy_DGB-2021-12.pdf
Data Source: un
AnnexH H323 Mobile Proposal
Question: Q.13 interim Ad-hoc meeting Nov. 17, 1999
SOURCE*: Mobility Ad-hoc group (Draft Contribution)
TITLE: Annex-H (User, Terminal and Service Mobility in H.323)
SUBJECT: Enhancements to ITU-T Recommendation H.323 to support User Terminal and Service Mobility
Abstract
Need TEXT
· Table Of Contacts
1Abstract
1 Introduction 2
2 Reference 2
2.1 Abbreviations 2
3 Definitions 3
4 Scope 4
5 H.323 Mobility Functional Requirements 4
5.1 Basic Concepts used to provided H.323 Mobility 4
5.2 IMT-2000 Mobility Management Applicable to H.323 5
6 Architecture for H.323 Mobility 5
6.1 Functional Entities 5
6.2 Reference Points 5
1 Introduction
The high level Functional Entities needed for H.323 Mobility agreed on H.323 Mobility functional entities and very high level requirements. New Functions to provide mobility management were identified as Home Location Function (HLF), Visitor Location Function (VLF), Authentication Function (AuF) and Inter-working Function (IWF).
Also respective H.323 Mobility Annex H contributors introduced their documents, as listed in section 2 above, a number of requirements were identified for User, Terminal and Service Mobility capabilities:
· The Mobility Management Functional Entities needed to provide the H.323 Mobility Management are Home Location Function (HLF), Visitor Location Function (VLF), Authentication Functions (AuF) and Inter-working Function (IWF) which reside above the IP layer shown in figure1.
2 Reference
Need TEXT
2.1 Abbreviations
Need TEXT
3 Definitions
User: A person or other entity authorized by a subscriber to use some or all of the services subscribed to by that subscriber.
Language:English
Score: 470519.2
-
https://www.itu.int/wftp3/av-a...2004/Mobility-adhoc/MTD-03.doc
Data Source: un
Although the proposed NGN control functional architecture neither identifies all functionalities required for the support of mobility/nomadism across diverse access networks nor proposes functions to ensure end-to-end QoS across multiple network domains, it is expected that future versions of the proposed baseline NGN control architecture would be enhanced to accommodate these widely recognized NGN features.
(...) The NGN 2004 Project definition currently identifies the following areas
· General framework model
· Functional architecture model
· End-to-end Quality of service
· Service platforms (including APIs)
· Network Management
· Security
It was noted that SG11 would be involved in Functional architecture modelling through the development of the Control plane functional architecture, in the Service/application platforms through the study of the signalling/control requirements and protocols/APIs, and in the definition of E2E QoS functional signalling requirements.
Further, a domain of Signalling and Control functions and protocols should also be identified.
3 Highlights of the discussion
There is a need from ITU-T Sector Members to progress work on NGN, particularly in the areas of Control functional architectures, signalling functional requirements and control protocols.
Language:English
Score: 470382.57
-
https://www.itu.int/ITU-T/worksem/ngn/SG11-info-001.doc
Data Source: un
The chairperson’s of the functional commissions constituting the panel were: H. (...) In view of several chairpersons, the annual sessions of the functional commissions
assumed particular importance in 2005. (...) At present, the work of the functional commissions did not influence the priorities of the UN funds and programmes.
Language:English
Score: 470212.2
-
https://www.un.org/en/ecosoc/m...ogue%20CFC%207%20July%20PM.pdf
Data Source: un
This duty includes the requirement that, while carrying out his/her/its Functions, an Intermediary shall respect the rights of persons as provided by the Statute and the Rules. (...) Any abusiveness, coercion or threats to any person with whom the Intermediary has dealings in the course of his/her/its Functions.
Section 4 Confidentiality
4.1. An Intermediary shall ensure that any dealings with a person with whom the Intermediary has contact in the course of his/her/its Functions respect the contacted person's confidentiality and privacy.
4.2. (...) An Intermediary shall make every effort to conduct himself or herself in a
4
manner that limits the risks to any person with whom the Intermediary has contact in the course of his/her/its Functions, especially when those risks arise in connection with the Intermediary's Functions.
Language:English
Score: 470118.4
-
https://www.icc-cpi.int/sites/default/files/CCI-Eng.pdf
Data Source: un