EP1100270B1

EP1100270B1 - Terminal supporting signalling used in transmission and reception of MPEG-4 data

Info

Publication number: EP1100270B1
Application number: EP00308920.8A
Authority: EP
Inventors: Yung-Lyul Lee; In-hwan Int.Prop.Team Digital Media R&D Cent Kim; Yoon-Soo Kim
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 1999-10-29
Filing date: 2000-10-10
Publication date: 2015-12-30
Anticipated expiration: 2020-10-10
Also published as: CN1303205A; KR100636110B1; KR20010039215A; US6792048B1; JP2001169261A; EP1100270A3; NO20005363L; EP1100270A2; CN100382548C; NO20005363D0

Description

The present invention relates to a terminal that supports video conferencing, and more particularly to, a terminal in which communication parameters of the Moving Picture Experts Group(MPEG)-4 scheme is registered in a control protocol for supporting video teleconferencing.
In order to realize a video teleconferencing system, the International Telecommunications Union (ITU) developed the Recommendations H. 323 and H.324M. The Internet Engineer Task Force (IETF) recommends the media gateway control protocol (MGCP) for supporting packet-based video data communications over the Internet. Development of MPEG-4 related standards such as the Inter national Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) 14496 allows for enhanced video data processing. However, a conventional terminal has not yet supported the MPEG-4 standard. Thus, a terminal that supports video conferencing is required to support the MPEG-4 standard.
The paper "Video Coding And Multimedia Communications Standards For Internet" authorized by Tsuhan Chen and Published at pages 607-610 of volume 3 of the Proceedings of the IEEE ISLAS Conference 1998 describes developments in video coding and multimedia communications for Internet applications. In the coding aspect, emphasis is given to a number of emerging standards, including H.263 Version 2, H.26L, MPEG-4, and MPEG-7. In the communication aspect, H.323, and ITU-T standard developed for multimedia communications over non-Qos networks, is discussed.
It is an aim of embodiments of the present invention to provide a terminal that supports signaling used in transmission and reception of the Moving Pictures Experts Group (MPEG)-4 data in order to apply the signaling to MPEG-4 video data, audio data and system data.
According to the present invention there is provided an apparatus and method as set forth in the appended claims. Other features of the invention will be apparent from the dependent claims, and the description which follows.
For a better understanding of the invention, and to show how embodiments of the same may be carried into effect, reference will now be made, by way of example, to the accompanying diagrammatic drawings in which:

Figure 1 is a block diagram showing the configuration of a terminal according to an embodiment of the present invention; and
Figure 2 illustrates the sequence of communications between two terminals for explaining the operation of the terminal of Figure 1 in which communication parameters of the Moving Picture Experts Group (MPEG)-4 scheme is registered in a control protocol for supporting multimedia data communications.

Referring to Figure 1, a terminal device according to an embodiment of the present invention includes a video codec 100, an audio codec 102, a multiplexer 104, and a system controller 120. The video codec 100 performs video coding and decoding. The audio codec 102 performs audio coding and decoding. The multiplexer 104 perform multiplexing of encoded data. The system controller 120 performs signaling for negotiating the capability of a terminal. Furthermore, assuming that the terminal device 10 conforms to the H.323 standard, which is a video teleconferencing system related standard defined by the International Telecommunication Union-Terminal Sector (ITU-T), the system controller 120 complies with the H. 245 standard, which provides the control protocol in the system related standard. The system controller 120 also includes a video capability registration unit 130, an audio capability registration unit 140, and a system capability registration unit 150.

The video capability registration unit includes an H.261 video capability registration unit 132, an H.263 video capability registration unit 134, and a Moving Picture Experts Group (MPEG)-4 video capability registration unit 136, and registers parameters to be used in a video communications protocol. Each parameter is registered as follows:

VideoCapability	:: =choice
{
nonStandard	NonStandard Parameters,
h.261VideoCapability	h.261 Video Capability,
h.263VideoCapability	h.263 Video Capability,
	.
	.
	.
MPEG4VideoCapability	MPEG-4 Video Capability
}
MPEG4VideoCapability	:: =SEQUENCE
{
profileAndLevel-NBitL2	BOOLEAN,
profileAndLevel-MainL4	BOOLEAN,
profileAndLevel-MainL2	BOOLEAN,
profileAndLevel-CoreL2	BOOLEAN,
profileAndLevel-CoreL1	BOOLEAN,
profileAndLevel-SimpleScalable	BOOLEAN,
profileAndLevel-SimpleL3	BOOLEAN,
profileAndLevel-SimpleL2	BOOLEAN,
profileAndLevel-SimpleL1	BOOLEAN,
	.
	.
	.
	.
typicalVisualSessionSize	INTEGER,
maximumTotalNumberOfObjects	INTEGER,
maximumNumberPerType	INTEGER,
maximumNumberDifferentQuantizationTable	INTEGER,
maxTotalReferenceMemory	INTEGER,
maximumNumberOfMBsec	INTEGER,
costFunctionEquivalent	INTEGER,
maximumVBVBufferSize	INTEGER,
maxVideoPacketLength	INTEGER,
maxSpriteSize	INTEGER,
waveleteRestrictions	INTEGER,
maxBitrate	INTEGER,
maxEnhancementLayersPerObject	INTEGER,
	.
	.
	.
	.
}

More specifically, initially, in order to determine video capability to be used in communication between two terminals, a plurality of parameters are registered. Here, one among the plurality of parameters registered by "::=choice" is selectively used. In the embodiment, the parameter nonStandard for determining video capability that does not conform to a standard, the parameter h.261VideoCapability for determining video capability that conforms to the H.261 standard, the parameter h.263VideoCapability for determining video capability that conforms to the H.263 standard, and the parameter MPEG4VideoCapability for determining video capability that conforms to the MPEG-4 standard, are registered.
Only the parameter MPEG4VideoCapability, which is a distinctive feature of the present invention, will now be described. Thus, the parameter
MPEG4VideoCapability is defined as "::=SEQUENCE", thereby requiring registrations of all of its particular parameters. The particular parameters are as follows.
A plurality of parameters for determining a visual profile and the level of the visual profile are defined as "BOOLEAN", and one of the parameters is selectively registered. For example, one among the parameters profileAndLevel-NBitL2, profileAndLevel-MainL4, profileAndLevel-MainL2, profileAndLevel-CoreL2, profileAndLevel-CoreL1, profileAndLevel-SimpleScalable, profileAndLevel-SimpleL3, profileandLevel-SimpleL2, and profileAndLevel-SimpleL1 is set to "1", and the remaining parameters are all set to "0". Therefore, one is selected from visual profiles conforming to MPEG-4 Version 1, i.e., NBitL2, MainL4, MainL2, CoreL2, CoreL1, SimpleScalable, SimpleL3, SimpleL2, and SimpleL1.
Furthermore, the particular parameters for the selected visual profile are each registered. Those particular parameters include the parameter typicalVisualSessionSize for determining a session size, the parameter maximumTotalNumberOfObjects for determining a maximum number per type, the parameter maximumNumberDifferentQuantizationTable for determining the maximum number of different quantization tables, the parameter maxTotalReferenceMemory for determining the maximum capacity of a reference memory, the parameter maximumNumberOfMBsec for determining the maximum number of macroblocks transmitted per second, the parameter costFunctionEquivalent for determining the number of macroblocks transmitted per second, the parameter maximumVBVBufferSize for determining the maximum buffer size of a video buffer verifier (VBV), the parameter maxVideoPacketLength for determining the length of a video packet, the parameter maxSpriteSize for determining the size of background image, the parameter waveletRestrictions for determining the characteristic of a wavelet filter, the parameter maxBitrate for determining a maximum bit rate, and the parameter maxEnhancementLayersPerObject for determining the maximum number of enhancement layers per object. These parameters are set to integer values, thereby determining a transmission characteristic of each parameter.

The audio capability registration unit 140 includes an H.261 audio capability registration unit 142, an H.263 audio capability registration unit 144, and an MPEG-4 audio capability unit 146, and registers parameters to be used for an audio communication protocol as follows:

AudioCapability	:: =choice
{
nonStandard	NonStandard Parameters,
g711Alaw64K	INTEGER (1-256),
is13818AudioCapability	IS13818 Audio Capability,
	.
	.
	.
MPEG4AudioCapability	MPEG-4 Audio Capability.
	.
	.
	.
gsmEnhanceFullRate	GSM Audio Capability
}

MPEG4AudioCapability	:: =SEQUENCE
{
profileAndLevel-MainL4	BOOLEAN,
profileAndLevel-MainL3	BOOLEAN,
profileAndLevel-MainL2	BOOLEAN,
profileAndLevel-MainL1	BOOLEAN,
profileAndLevel-ScalableL4	BOOLEAN,
profileAndLevel-ScalableL3	BOOLEAN,
profileAndLevel-ScalableL2	BOOLEAN,
profileAndLevel-ScalableL1	BOOLEAN,
profileAndLevel-SpeechL2	BOOLEAN,
profileAndLevel-SpeechL1	BOOLEAN,
profileAndLevel-SynthesisL3	BOOLEAN,
profileAndLevel-SynthesisL2	BOOLEAN,
profileAndLevel-SynthesisL1	BOOLEAN,
	.
	.

	.

pcu	INTEGER,
rcu	INTEGER,
	.
	.
	.
audioSampling16k	BOOLEAN,
audioSampling22.05k	BOOLEAN,
audioSampling48k	BOOLEAN,
	.
	.
	.
numberOfMonoObjects	INTEGER,
numberOfStereoObjects	INTEGER,
numberOfSpeechObjects	INTEGER,
memoryForData	INTEGER,
lowProcessing	BOOLEAN,
highProcessing	BOOLEAN,
numberOfTTSIObjects	INTEGER,
maxEnhancementLayersPerObject	INTEGER,
	.
	.
	.
	.
}

More specifically, initially, in order to determine audio capability to be used in communication between two terminals, a plurality of parameters are registered. Here, one among the plurality of parameters defined as"::=choice" is selectively used. In the embodiment, the parameter nonStandard for determining audio capability that does not conform to a standard, the parameter g711Alaw64k for determining audio capability conforming to the Alaw option of g711, which is the audio codec related format, and corresponding to a transmission speed of 64 Kbps, the parameter is13818AudioCapability for determining audio capability that conforms to the IS13818 standard, the parameter MPEG4AudioCapability for determining audio capability that conforms to the MPEG-4 standard, and the parameter gsmEnhanceFullRate for determining audio capability that conforms to the GSM (Global System for Mobile Communications) standard, are each registered. Only the parameter MPEG4AudioCapability, which is a distinctive feature of the present invention, will now be described. The parameter
MPEG4AudioCapability is defined as "::=SEQUENCE", requiring registrations of all of its particular parameters. The particular parameters are as follows.
A plurality of parameters for determining an audio profile and the level of the audio profile are defined as "BOOLEAN" , and one of the parameters is selectively registered. For example, one among the parameters profileAndLevel-MainL4, profileAndLevel-MainL3, profileAndLevel-MainL2, profileAndLevel-MainL1, profileAndLevel-ScalableL4, profileAndLevel-ScalableL3, profileAndLevel-ScalableL2, profileAndLevel-ScalableL1, profileAndLevel-SpeechL2, profileAndLevel-SpeechL1, profileAndLevel-SynthesisL3, profileAndLevel-SynthesisL2, and profileAndLevel-SynthesisL1 is set to "1", and the remaining parameters are all set to "0". Therefore, one is selected from audio profiles conforming to the MPEG-4 Version 1, i.e., MainL4, MainL3, MainL2, MainL1, ScalableL4, ScalableL3, ScalableL2, ScalableL1, SpeechL2, SpeechL1, SynthesisL3, SynthesisL2, and SynthesisL1.
Furthermore, the particular parameters for the selected audio profile are each registered. With respect to registration of particular parameters for the audio profile, since it is similar to that of the particular parameters for the visual profile, the description thereof will be omitted.
Meanwhile, the parameter pcu denotes a processor complexity unit in mega operations per second (MOPS) times 1. The parameter rcu denotes a RAM complexity unit. Furthermore, audio sampling frequency is determined by, for example, setting one among the parameters audioSampling16k audioSampling22.05k, and audioSampling48k to "1" and the remaining parameters to "0". With respect to a "scalable" audio profile, the following particular parameters are preferably registered: the parameter numberOfMonoObjects for determining the number of mono objects, the parameter numberOfStereoObjects for determining the number of stereo objects, and the parameter numberOfSpeechObjects for determining the number of speech objects. In addition, the parameter memoryForData for determining the size of a data memory, and the parameters lowProcessing and highProcessing, reserved in association with complexity, are preferably registered. Furthermore, the parameter numberOfTTSIObjects for determining the number of text-to-speech information (TTSI) objects is preferably registered.

The system capability registration unit 150 includes H.261 system capability registration unit 152, H.263 system capability registration unit 154, and MPEG-4 system capability registration unit 156, and registers parameters to be used for system control. Each parameter is registered as follows:

SystemCapability	:: =choice
{
nonStandard	NonStandard Parameters,
	.
	.
	.
MPEG4SystemCapability	MPEG-4 System Capability

	.
	.
	.
}
MPEGSystemCapability	:: =SEQUENCE
{
profileAndLevel-OD	BOOLEAN,
profileAndLevel-SD	BOOLEAN,
}

More specifically, initially, in order to determine system capability to be used in communication between two terminals, a plurality of parameters are registered. Here, one among the plurality of parameters defined as ": :=choice" is selectively used. In the embodiment, the parameter nonStandard for determining system capability that does not conform to a standard, and the parameter MPEG4SystemCapability for determining system capability that conforms to the MPEG-4 standard are registered.
Only the parameter MPEG4SystemCapability, which is a distinctive feature of the present invention, will now be described. The parameter MPEG4SystemCapability is defined as "::=SEQUENCE", requiring registrations of all of its particular parameters. The particular parameters are as follows.
A plurality of parameters for determining a system profile and the level of a system profile are defined as "BOOLEAN", and one of the parameters is selectively registered. The particular parameters are set to integer values or set algebraically, thus determining a system capability characteristic in a signaling process. Since the registration of particular parameters for a system profile is similar to those of the particular parameters for audio and visual profiles, further description will be omitted. Preferably, the MPEG-4 video, MPEG-4 audio, and MPEG-4 system in the embodiment conforms to the standards International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) 14496-2, ISO/IEC 14496-3, and ISO/IEC 14496-1, respectively. Figure 2 illustrates the communication sequence between two terminals for explaining the operation of the terminal of Figure 1 in which MPEG-4 communication parameters are registered in a control protocol for supporting multimedia data communications. Referring to Figure 2, initially, a physical connection is established between two terminals A and B (step 20). More particularly, if the terminal A performs a call setup (step 202), then the terminal B sends a signal Call_Proceeding, indicating that it is turned on and can proceed with a call, to the terminal A (step 204). Furthermore, if the terminal B sends a call alerting signal (step 206) and the terminal A accepts the connection upon receipt of the call alerting signal, the physical connection is established between the two terminals A and B (step 208).
Next, it is determined which terminal of the two terminals A and B will become a master having the final decision right for negotiation and which will become a slave (step 21). For example, the terminal A sends a master slave determination (MSD) signal to the terminal B, thereby requesting the terminal B to determine which terminal is a master and which is a slave (step 212). The terminal B, which receives the MSD signal, sends an acknowledgment signal MSD_Ack to the terminal A (step 214). The terminal A then returns the acknowledgment signal MSD_Ack to the terminal B, thereby completing the determination of master and slave.
For the next step, a process for negotiating the capability of terminals to perform a data transceiving function is performed (step 22). Specifically, when the terminal A is determined to be a master, it sends all its registered terminal capability set data Terminal_Capability_Set to the terminal B (step 222). The device according to the present invention sends all parameters and the particular parameters registered by the video capability registration unit 130, the audio capability registration unit 140, and the system capability registration unit 150 as the capability set data Terminal_Capability_Set, from the terminal A to the terminal B or vice versa. For example, the terminal B sends an acknowledgment signal Terminal_Capability_Set to the terminal A as an indication of its reception capability for the capability set data Terminal_Capability_Set sent from the terminal A.
Next, a logical channel is opened (step 23). More specifically, the terminal A sends a signal Open_Logical_Channel to the terminal B, thereby requesting to open a logical channel according to communication parameters determined during the negotiation process in the step 22 (step 232). In response to the signal Open_Logical_Channel, the terminal B sends an acknowledgment signal Open_Logical_Channel_Ack to the terminal A (step 232), so that a logical channel opens using values corresponding to the negotiated parameters. If the terminals A and B have video capability, audio capability, and system capability that conform to the MPEG-4 scheme such as ISO/IEC 14496-2, ISO/IEC 14496-3, and ISO/IEC 14496-1, the two terminals can perform MPEG-4 compliant audio/visual (A/V) communications.
Here, MEPG-4 compliant A/V data communication is performed through the logical channel (step 24). In this case, as understood by those skilled in the art, the video codec and audio codec provided in the terminals are required to perform video coding/decoding and audio coding/decoding that conform to the MPEG-4 scheme such as ISO/IEC 14996.
Meanwhile, if either terminal desires to end the A/V data communication, the terminal that desires to do so, for example, the terminal A sends a signal Close_Logical_Channel to the terminal B, thereby requesting to close the logical channel (step 252). The terminal B sends an acknowledgment signal Close_Logical_Channel_Ack to the terminal A (step 254), so that the logical channel is closed.
In the terminal according to the present invention, MPEG-4 communication parameters are registered in a control protocol for supporting multimedia data communications in a video teleconferencing system based on protocol standards ITU-T H.323, H.324M, and IETF, also called MGCP, thereby supporting a call setup on which MPEG-4 compliant visual, audio, and system applications are based.
Although the foregoing embodiment has been described with reference to registration of parameters corresponding to characteristics used in MPEG-4 version 1, the present invention will not be restricted thereto, and it is possible to additionally register parameters corresponding to characteristics used in MPEG-4 version 2. Furthermore, although the terminal according to the embodiment has been applied to the Recommendation H.323 which specifies a control protocol in the system related format conforming to Recommendation H.323, the present invention will not be restricted thereto, and it may be adapted to IEFT SDP (Session Description Protocol).
The terminal according to the present invention can perform MPEG-4 signaling on which MPEG-4 visual, audio, system applications are based.

Claims

A terminal including a video codec (100) for performing video coding/decoding, an audio codec (102) for performing audio coding/decoding, a multiplexer (104) for performing multiplexing on encoded data, and a system controller (120); characterised in that the system controller (120) arranged to perform signaling for negotiating the terminal capability, wherein the system controller comprises:
a video capability registration unit (130) for registering a plurality of parameters for determining video capability, at least one of which is a parameter for determining video capability that conforms to the Moving Picture Experts Group (MPEG)-4 standard;

an audio capability registration unit (140) for registering a plurality of parameters for determining audio capability, at least one of which is a parameter for determining audio capability that conforms to the MPEG-4 standard; and

a system capability registration unit (150) for registering a plurality of parameters, at least one of which is a parameter for determining system capability that conforms to the MPEG-4 standard.
The terminal of claim 1, wherein parameters for determining the video capability, audio capability, and system capability that conform to the MPEG-4 standard are each defined in the standards International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) 14496-2, ISO/IEC 14496-3, and ISO/IEC 14496-1.
The terminal of claim 1 or 2, wherein, the terminal complies with the H.323 standard, which is a video teleconferencing system related standard defined by the International Telecommunication Union-Terminal Sector (ITU-T), the system controller is based on the H.245 standard which specifies a control protocol in the system related standard.
The terminal of claim 1 or 2, wherein the system controller (120) is based on
the session description protocol (SDP) in the media gateway control protocol (MGCP) for supporting packet-based video data communications over the Internet, which is defined by the Internet Engineer Task Force (IETF).
The terminal of any of the preceding claims, wherein, in order to determine a visual profile and the level of the visual profile that conform to the MPEG-4 standard, the video capability registration unit defines a protocol element comprising at least one among the parameters profileAndLevel-NBitL2, profileAndLevel-MainL4, profileAndLevel-MainL2, profileAndLevel-CoreL2, profileandLevel-CoreL1, profileAndLevel-SimpleScalable, profileAndLevel-SimpleL3, profileandLevel-SimpleL2, and profileAndLevel-SimpleL1 corresponding to NBitL2, MainL4, MainL2, CoreL2, CoreL1, SimpleScalable, SimpleL3, SimpleL2, and SimpleL1 which are visual profiles defined by the ISO/IEC 14496-2 standard which conforms to MPEG-4 Version 1.
The terminal of claim 5, wherein the parameters are defined as "BOOLEAN", and one of the parameters is selectively registered.
The terminal of claim 5 or 6, wherein the video capability registration unit (130) defines a protocol element further comprising at least one of a parameter typicalVisualSessionSize for determining a session size, a parameter maximumTotalNumberOfObjects for determining a maximum number per type, a parameter maximumNumberDifferentQuantizationTable for determining the maximum number of different quantization tables, a parameter maxTotalReferenceMemory for determining the maximum capacity of a reference memory, a parameter maximumNumberOfMBsec for determining the maximum number of macroblocks transmitted per second, a parameter costFunctionEquivalent for determining the number of macroblocks transmitted per second, a parameter maximumVBVBufferSize for determining the maximum buffer size of a video buffer verifier (VBV), a parameter maxVideoPacketLength for determining the length of a video packet, a parameter for determining the size of background image, a parameter waveletRestrictions for determining the characteristic of a wavelet filter, a parameter maxBitrate for determining a maximum bit rate, and a parameter maxEnhancementLayersPerObject for determining the maximum number of enhancement layers per object, which is defined by the ISO/IEC 14496-2 which conforms to MPEG-4 Version 1.
The terminal of any preceding claim, wherein, in order to determine an audio profile and the level of the audio profile which conform to the MPEG-4 standard, the audio capability registration unit defines a protocol element comprising at least one of the parameters profileAndLevel-MainL4, profileAndLevel-MainL3, profileAndLevel-MainL2, profileAndLevel-MainL1, profileAndLevel-ScalableL4, profileAndLevel-ScalableL3, profileAndLevel-ScalableL2, profileAndLevel-ScalableL1, profileAndLevel-SpeechL2, profileAndLevel-SpeechL1, profileAndLevel-SynthesisL3, profileAndLevel-SynthesisL2, and profileAndLevel-SynthesisL1 corresponding to MainL4, MainL3, MainL2, MainL1, ScalableL4, ScalableL3, ScalableL2, ScalableL1, SpeechL2, SpeechL1, SynthesisL3, SynthesisL2, and SynthesisL1 which are audio profiles defined in the ISO/IEC 14496-1 which conforms to MPEG-4 Version 1.
The terminal of claim 8, wherein the parameters are defined as "BOOLEAN", and one of the parameters is selectively registered.
The terminal of any preceding claim, wherein the audio capability registration unit (140) defines a protocol element further comprising at least one of a parameter pcu for denoting a processor complexity unit in mega operations per second (MOPS) times 1, and a parameter rcu for denoting a RAM complexity unit, which are defined in the ISO/IEC 14496-1 which conforms to MPEG-4 Version 1.
The terminal of claim 10, wherein the audio capability registration unit (140) defines a protocol element further comprising at least one of the parameters audioSampling16k, audioSampling22.05k, and audio Sampling48k for determining audio sampling frequency, the parameters being defined in the ISO/IEC 14496-1 which conforms to MPEG-4 Version 1.
The terminal of claim 10, wherein the audio capability registration unit (140) defines a protocol element further comprising at least one of a parameter numberOfMonoObjects for determining the number of mono objects, a parameter numberOfStereoObjects for determining the number of stereo objects, and a parameter numberOfSpeechObjects for determining the number of speech objects which are defined in the ISO/IEC 14496-1 which conforms to MPEG-4 Version 1.
The terminal of claim 10, wherein the audio capability registration unit (140) defines a protocol element further comprising at least one of a parameter memoryForData for determining the size of data memory, parameters lowProcessing and highProcessing, which are reserved in association with complexity, and a parameter numberOfTTSIObjects for determining the number of text-to-speech information (TTSI) objects which are defined in the ISO/IEC 14496-1 which conforms to MPEG-4 Version 1.
The terminal of any preceding claim wherein, in order to determine an MPEG compliant system profile which conforms to MPEG-4 Version 1 and the level of the system profile, a plurality of parameters defined in the ISO/IEC 14496-1 are defined as "BOOLEAN", thereby registering one selected from the plurality of parameters.
The terminal of any preceding claim, wherein the video codec (100) and the audio codec (102) comprise an MPEG-4 video codec means for performing video coding/decoding, and an MPEG-4 audio codec means for performing audio coding/decoding.
The terminal of claim 15, wherein the MPEG-4 video codec means and MPEG-4 audio codec means perform the video and audio coding/decoding defined in the ISO/IEC 14496 standard.