26234-450: Transparent end-to-end Packet-switched Streaming Service(PSS); Protocols and codecs
1. System Description
Video, Audio & Speech : RTP/UDP
Still images, Bitmap graphics, Vector graphics & Text : HTTP/TCP
Presentation description : RTSP/UDP or TCP
2. Protocols
Session descriptions : SMIL, SDP, or plain RTSP URL
RTSP :
- shall follow appendix D of RFC-2326 rules for minimal on-demand playback - shall implement the DESCRIBE method - shall implement the Range header field - shall include the Range field in all PLAY responses
SDP : always include the following fields int the SDP
- "a=control:" - "a=range:" - "a=rtpmap:" - "a=fmtp:" - "b=AS:" for bandwidth of the session and the individual media in the presentation
MIME media types
- AMR narrow band & wide band : RFC 3267 - MPEG-4 AAC & video codec : RFC 3016; if "cpresent=0", configuration info. is only carried SDP's "config" parameter - H.263 : ITU-T Recommendation H.263: "Video coding for low bit rate communication". - JPEG : RFC 2046 - GIF : RFC 2046 - XHTML : RFC 3236
3. Data transport
RTP over UDP/IP
- AMR narrow band & wid band : RFC 3267 - MPEG-4 AAC & video codec : RFC 3016 - H.263 : RFC 2429
HTTP over TCP/IP
- Still images(JPEG, JFIF)
a. baseline DCT, non-differential, Huffman coding, ad defined in table B.1, symbol "SOF0' in ITU-T Recommendation T.81 (1991) | ISO/IEC 10918-1 (1992): b. progressive DCT, baseline DCT, non-differential, Huffman coding, ad defined in table B.1, symbol "SOF2' in ITU-T Recommendation T.81 (1991) | ISO/IEC 10918-1 (1992):
- Bitmap graphics
a. GIF87a b. GIF89a
- Text
a. XHTML Basic ; "http://www.w3.org/TR/2000/REC-xhtml-basic-20001219" b. UTF-8 ; "ISO/IEC 10646-1 (2000)" c. UCS-2 ; "The Unicode Standard", Version 3.0 Reading, MA, Addison-Wesley Developers Press, 2000, ISBN 0-201-61633-5.
- It shall be possible to charge separately for each type of medium used (e.g. voice, video, data) in a session and for each service used (e.g. voice call, streaming video, file download);
-It shall be possible to charge for different levels of QoS applied for and/or allocated during a session for each type of medium or service used;
-It shall be possible to charge each “leg” of a session separately. This includes the incoming and outgoing legs and any forwarded/redirected legs.(Note: The legs mentioned here are logical legs, i.e. not necessarily identical to actual signal and traffic flow. Even though tromboning may be avoided by optimal routing, the operator should still be able to charge for the ‘virtual legs’ of the call)
-The user can be charged according to the service used irrespective of the technology used to deliver it. (That is, the charge is not derived from whether 2G or 3G is used);
-The user can be charged according to the technology used to deliver a service. (That is, different charges can be applied on 2G and 3G);
-It shall be possible to charge a user according to the network resources used. For example, if a large bandwidth is required to use high quality video, the user could be charged accordingly. This is related to charging by QoS;
-It shall be possible to charge users flexibly for the use of extra resources (in at least the same network) for all legs of the call. For example, if a video component is added to a voice call the use of extra radio resource at both ends of the call could be paid for by each user in the call or totally by the initiating user.
-It shall be possible to suppress charging for certain types of connection e.g. when a customer receives tones or network announcements or during sessions such as automated pre-pay top-up.
-It shall be possible for the home network to charge its customers while roaming in the same ways as when they are at home.For example, if duration based charging is used for charging for streaming music in the home network, then it shall be possible to apply the same principle when the user is roaming.
-It shall be possible for operators to have the option to apply charging mechanisms that are used in GSM/GPRS. For example for duration of a voice call,for the amount of data transmitted (eg for streaming, file download, browsing) and for an event (one-off charge).
-It shall be possible for a network operator to charge its users for activities while roaming so that the home network will get the capability to raise service charges depending on the roamed to network, e.g. because of inter operator charges for the use of service capabilities within the visited network which will in general depend on the serving network. The ability to supply all the necessary information for all the charging options will depend on the capability of the visited network. For service capabilities which are provided by the home network, however, it is required that the charging information is collected to allow to identify the serving network of the served subscriber.
-It shall be possible for charging to be applied based on location, presence, push services etc
-It shall be possible to charge using pre-pay, post-pay, advice of charge, 3rd party charging techniques.
-It shall be possible for the home network to apply different tariffs to national calls and short messages established/sent by their subscribers while roaming in their Home PLMN depending on whether or not the called subscriber’s Home PLMN equals the calling subscriber’s Home PLMN, rather than on the called subscriber’s MSISDN.
The security of MBMS provides different challenges compared to the security of services delivered over point-to-point services. In addition to the normal threat of eavesdropping, there is also the threat that it may not be assumed that valid subscribers have any interest in maintaining the privacy and confidentiality of the communications, and they may therefore conspire to circumvent the security solution (for example one subscriber may publish the decryption keys enabling non-subscribers to view broadcast content). Countering this threat requires the decryption keys to be updated frequently in a manner that may not be predicted by subscribers while making efficient use of the radio network
하늘을 닮은 호수
Category
(0) 
(0)
