790
社区成员
发帖
与我相关
我的任务
分享有关MMS的FAQ(三)（ From nokia forum）
2. TECHNOLOGY-RELATED QUESTIONS
2.1 How can you transmit MMS using an SMS channel?
Although the MMS user experience is similar to SMS, MMS is not transmitted via the SMS transmission channel. The SMS transmission channel is too narrow band for transmitting multimedia content. The data speed in the networks must be at least 14.4 kbit/s for carrying MMS messages.
2.2 What bearer does MMS use?
MMS is transported using the WAP Wireless Service Protocol WSP. The WAP browser is not involved in MMS - only the WAP transport protocols are used for MMS. The network bearer can be any wireless network capable of carrying data at a speed of at least 14.4 kbit/s.
2.3 Why does MMS not use the WAP browser?
WAP is used only as a message bearer for MMS, that is why the WAP browser is not needed. There is a separate MMS application in the MMS supporting devices for MMS.
2.4 What addressing modes are supported in MMS?
The MMS standard includes support for phone number addressing and e-mail addressing.
2.5 What content types does MMS support?
The standard recommends the following supported media types: JPEG, GIF, text, AMR voice and some other formats. The MMS interoperability document, which can be found in the Forum Nokia MMS documents, describes the minimum set of supported formats in more detail.
In the future, a limited set of mandated content formats may be standardized.
2.6 How big can an MMS message be?
The standard does not specify a maximum size for an MMS message. This is done to ensure future interoperability, to avoid the SMS dilemma, where the 160-character limit has been problematic because the message length has usually been limited to 160 characters.
The message size is, therefore, an implementation issue. It is also dependent on operator preferences, if they want to have a standardized message size for charging purposes. Nokia foresees that initially the MMS messages will be between 30 kb and 100 kb in size.
2.7 What is SMIL?
Synchronized Multimedia Integration Language (SMIL) is a proposed specification of the World Wide Web Consortium (W3C) for a powerful way of choreographing rich, interactive multimedia content for real-time delivery over the World Wide Web, even over low bandwidth connections. SMIL was developed by a group representing the CD-ROM, interactive television, Web, and audio- and video-streaming industries. The companies involved include Digital Equipment, Lucent, Microsoft, Netscape, Philips, and RealNetworks, as well as research organizations such as Columbia University, CWI, and INRIA.
SMIL is a layout language that allows easy creation of multimedia presentations consisting of multiple elements of compelling music, voice, images, text, video, and graphics in a common, synchronized timeline. As a simple but powerful markup language, SMIL is easy to learn because it does not require a programming language and can be authored using a simple text editor. Visually, SMIL is strikingly similar to HTML in its syntax and constructs. An example of an SMIL multimedia layout file consists of a news video, emphasizing specific news stories with text headlines, and displaying, for example, a stock ticker at the bottom of the screen.
2.8 What is a Store and automatic Forward service?
If your MMS phone is on-line and active, the MMSC immediately transfers the MMS message to your phone. If your phone is not on-line, the MMSC will store your messages for you and when your phone comes on-line will automatically send you all the stored messages. The store function is there to cover for the time when the receiving client is unreachable.
2.9 Which WAP release does MMS require?
MMS requires WAP 1.2.1 specification for the transmission protocols. From WAP 2.0, the following specifications are directly related to the MMS: Multimedia Messaging Service Architecture Overview (WAP-205-MMSArchOverview-20010425-a), Multimedia Messaging Service Client Transaction Specification (WAP-206-MMSCTR-20010612-a) and Multimedia Messaging Service Encapsulation Specification (WAP-209-MMSEncapsulation-20010601-a). Also, WAP 2.0 must provide the WAP Push specifications that are needed to define the MMS notification functionality.
2.10 How can an MMS service be created?
Nokia will provide several tools and emulators so that content providers and developers will be able to create MMS content and applications. Tools and emulators will enable simulation of Nokia products before they are actually shipped to the market place and they will be available during the first half of 2002. The degree of tool sophistication will vary depending on different development needs and application purposes. Consumers will be able to create their personal messages with a simple web-based tool allowing combination of different media types into one message entity. A more advance tool including an emulator will be available for service developers. The third tool is seamlessly integrated into leading publishing and design tools for creating rich messaging content and it is targetd at media houses and content providers.
2.1 How can you transmit MMS using an SMS channel?
Although the MMS user experience is similar to SMS, MMS is not transmitted via the SMS transmission channel. The SMS transmission channel is too narrow band for transmitting multimedia content. The data speed in the networks must be at least 14.4 kbit/s for carrying MMS messages.
2.2 What bearer does MMS use?
MMS is transported using the WAP Wireless Service Protocol WSP. The WAP browser is not involved in MMS - only the WAP transport protocols are used for MMS. The network bearer can be any wireless network capable of carrying data at a speed of at least 14.4 kbit/s.
2.3 Why does MMS not use the WAP browser?
WAP is used only as a message bearer for MMS, that is why the WAP browser is not needed. There is a separate MMS application in the MMS supporting devices for MMS.
2.4 What addressing modes are supported in MMS?
The MMS standard includes support for phone number addressing and e-mail addressing.
2.5 What content types does MMS support?
The standard recommends the following supported media types: JPEG, GIF, text, AMR voice and some other formats. The MMS interoperability document, which can be found in the Forum Nokia MMS documents, describes the minimum set of supported formats in more detail.
In the future, a limited set of mandated content formats may be standardized.
2.6 How big can an MMS message be?
The standard does not specify a maximum size for an MMS message. This is done to ensure future interoperability, to avoid the SMS dilemma, where the 160-character limit has been problematic because the message length has usually been limited to 160 characters.
The message size is, therefore, an implementation issue. It is also dependent on operator preferences, if they want to have a standardized message size for charging purposes. Nokia foresees that initially the MMS messages will be between 30 kb and 100 kb in size.
2.7 What is SMIL?
Synchronized Multimedia Integration Language (SMIL) is a proposed specification of the World Wide Web Consortium (W3C) for a powerful way of choreographing rich, interactive multimedia content for real-time delivery over the World Wide Web, even over low bandwidth connections. SMIL was developed by a group representing the CD-ROM, interactive television, Web, and audio- and video-streaming industries. The companies involved include Digital Equipment, Lucent, Microsoft, Netscape, Philips, and RealNetworks, as well as research organizations such as Columbia University, CWI, and INRIA.
SMIL is a layout language that allows easy creation of multimedia presentations consisting of multiple elements of compelling music, voice, images, text, video, and graphics in a common, synchronized timeline. As a simple but powerful markup language, SMIL is easy to learn because it does not require a programming language and can be authored using a simple text editor. Visually, SMIL is strikingly similar to HTML in its syntax and constructs. An example of an SMIL multimedia layout file consists of a news video, emphasizing specific news stories with text headlines, and displaying, for example, a stock ticker at the bottom of the screen.
2.8 What is a Store and automatic Forward service?
If your MMS phone is on-line and active, the MMSC immediately transfers the MMS message to your phone. If your phone is not on-line, the MMSC will store your messages for you and when your phone comes on-line will automatically send you all the stored messages. The store function is there to cover for the time when the receiving client is unreachable.
2.9 Which WAP release does MMS require?
MMS requires WAP 1.2.1 specification for the transmission protocols. From WAP 2.0, the following specifications are directly related to the MMS: Multimedia Messaging Service Architecture Overview (WAP-205-MMSArchOverview-20010425-a), Multimedia Messaging Service Client Transaction Specification (WAP-206-MMSCTR-20010612-a) and Multimedia Messaging Service Encapsulation Specification (WAP-209-MMSEncapsulation-20010601-a). Also, WAP 2.0 must provide the WAP Push specifications that are needed to define the MMS notification functionality.
2.10 How can an MMS service be created?
Nokia will provide several tools and emulators so that content providers and developers will be able to create MMS content and applications. Tools and emulators will enable simulation of Nokia products before they are actually shipped to the market place and they will be available during the first half of 2002. The degree of tool sophistication will vary depending on different development needs and application purposes. Consumers will be able to create their personal messages with a simple web-based tool allowing combination of different media types into one message entity. A more advance tool including an emulator will be available for service developers. The third tool is seamlessly integrated into leading publishing and design tools for creating rich messaging content and it is targetd at media houses and content providers.
...全文
请发表友善的回复…
发表回复
