Interface Further Study in DVB-H (CBMS1 ~ CBMS7)
1). Overall Protocol Stack:
http://docs.google.com/View?id=ddh56dhg_171fd5gqkf2
1.1). Service Access Points on the broadcast network
Solution | Service Access Points on the broadcast network Description | Service Access Points on the broadcast network Description |
DVB-H | DVB Signalling | Access point mainly used by tuning and mobility management enablers to obtain relevant configuration information. |
Streaming | AV Streaming | Access Point for all Audio/Video streams delivered over the Broadcast network |
Download | File/Data Download | Access Point for all data delivered over the Broadcast network via FLUTE (one time or carousel based) |
IP MC | IP Multicast | Access point to IP multicast for application specific usage of IP multicast. |
UDP MC | UDP Multicast | Access point to UDP multicast for application specific usage of IP multicast datagram services. |
1.2). Protocol Stack - Interface Used in DVB-H (CBMS)
http://docs.google.com/View?id=ddh56dhg_205g5bmqbg7
2). Reference Points / Interface and Fucntions:
2.1). Protocols over reference point CBMS-1
Ref Point | End Points | Usage |
CBMS-1 | From Broadcast network To Terminal | Broadcast network-specific singnalling, PSI/SI signalling in DVB-H. |
http://docs.google.com/View?id=ddh56dhg_207gxbf8ghc
§ Reference point CBMS-1 is between broadcast network and terminal.
§ It is used to signal IP streams (TS) with PSI/SI information (or tables) over the broadcast bearer.
§ These protocols are subject of TS 102 470
2.2). Protocols over reference point CBMS-2
Ref Point | End Points | Usage |
CBMS-2 | From Service Application To Terminal | Content Flow, including: |
http://docs.google.com/View?id=ddh56dhg_209fmqd9kfh
§ Reference point CBMS-2 is between service application and terminal.
§ It is used for content delivery over the broadcast network.
§ Both Stream Delivery (via RTP/UDP) and File Delivery (via FLUTE/ALC) are considered.
§ The contribution side for streams an encapsulation may be used as part of the head-end interface.
§ An RTP in TCP encapsulation method is defined in RFC 2326
§ These CDP protocols (Content Delivery Protocols) are subject of TS 102 472
2.3). Protocols over reference point CBMS-3
Ref Point | End Points | Usage |
CBMS-3 | From Service Management To Terminal | Electronic Service Guide (metadata, point-to-multipoint delivery). |
http://docs.google.com/View?id=ddh56dhg_211f5jmd2g3
§ Reference point CBMS-3 is between service management and terminal.
§ The ESG is delivered (via FLUTE/ALC) on this reference point.
§ ESGC: Encoded ESG information is transported in ESG fragment containers.
§ L4/L5 protocol levels at the head-end side are subject of further study.
§ The ESG is subject of document “IP Datacast over DVB-H: Electronic Service Guide (ESG)”, the FLUTE/ALC/LCT delivery protocols are subject of TS 102 472
2.4). Protocols over reference point CBMS-4
Ref Point | End Points | Usage |
CBMS-4 | Between Service Management and Terminal (only for the interactive network) | • Electronic Service Guide (metadata, point-to-point delivery). • Access Control to service applications. |
http://docs.google.com/View?id=ddh56dhg_213fsrfptgj
§ Reference point CBMS-4 is between service management (Logical ESG Aggregator) and terminal (Service and content description handler) over the interaction channel.
§ This reference point is optional. If available in the Terminal and configured for in the Service Management, it is used for ESG post delivery repair.
§ This reference point may be used e.g. to retrieve ESG information via the interaction channel. The current IP Datacast over DVB-H specification does not yet provide for this.
2.5). Protocols over reference point CBMS-5
Ref Point | End Points | Usage |
CBMS-5 | Between Service Application and Terminal (only for the interactive network) | • Point-to-point transport services (SMS/MMS, IP connectivity). |
http://docs.google.com/View?id=ddh56dhg_215fvh5s4hp
§ Reference point CBMS-5 is between service application and terminal via the interaction network.
§ This reference point is optional for terminals.
§ It is used for general interaction between terminal service applications.
§ In IP Datacast only for File Post Delivery Repair (via HTTP) it is defined up the application level.
§ File Post Delivery Repair is subject of TS 102 472
2.6). Protocols over reference point CBMS-6
Ref Point | End Points | Usage |
CBMS-6 | From Service Management To Broadcast network | Configuration of the DVB-H transport (number of services, allocated bandwidth, etc.). |
http://docs.google.com/View?id=ddh56dhg_217cx9rctwv
§ Reference point CBMS-6 is between service management (resource provisioning and scheduling) and broadcast network (DVB-H service handler).
§ CBMS-6 comprises head-end interfaces. Therefore, mention of Muxconfig, SOAP, and SNMP are non-normative.
2.7). Protocols over reference point CBMS-7
Ref Point | End Points | Usage |
CBMS-7 | Between Service Application and Service Management | • Service Application Declaration. |
http://docs.google.com/View?id=ddh56dhg_2198bpxf7c5
Reference point CBMS-7 is between service application and service management.
§ CBMS-7 comprises head-end interfaces. Therefore, mention of SOAP is non-normative
沒有留言:
張貼留言