DSP数字信号处理器对数字图像进行压缩，压缩后的图像信号其中一路送入（）中。

A:存储器 B:CCD C:DSP信号处理器 D:CMOS

下列关于DSP命令和LST命令说法正确的是（）。

A:DSP是查询某对象的当前状态信息 B:LST是查询某对象在BAM数据库中的信息，非当前状态的信息 C:LST查询某对象的当前状态信息 D:DSP查询某对象在BAM数据库中的信息，非当前状态的信息

支持HSDPA业务的基带板TBPE的DSP根据实现功能的不通，分为4类，在DSP监控工具中，我们需要选择对应的DSP来进行相应的信息获取。以下说法正确的是（）

A:dsp0完成3载波的下行符号级处理，包括HSDPA的处理 B:dsp5完成3载波的上行符号级处理 C:dsp11完成3载波的同步接入流程处理 D:其余基带板协同完成3载波chip级处理，互为备份

TBPE的DSP软件模块可以划分为四个软件子模块，对于他们的功能，下列说法正确的有（）

A:MAC_DLSRDSP，完成HSDPAFP帧的处理、MAC-hs的处理、HSDPA相关信道和普通业务信道的下行编码以及信令的处理和转发 B:ULSR DSP，完成所有上行信道的上行解码和上行FP帧处理 C:ULSYNC DSP，完成所有载波的上行同步时隙（UpPTS）的处理 D:CR DSP，完成各载波时隙的调制或解调处理以及HS-SICH的解码

以下DSP监控工具说法错误的有（）

A:透明通道是NodeB前台提供的RRU与后台之间的接口，提供部分操作维护功能 B:DSP监控工具提供基带部分的一些测量信息和打印 C:DSP监控工具提供查看的RTWP只能在上行时隙有效 D:DSP监控工具可以同时对NodeB下所有基带资源的情况进行查询

CD机中，微处理器向DSP发出控制指令，开始工作的同时（）向微处理器传送工作状态信号

A:DSP B:DAC C:OPU D:CPU

The software architecture is a set of software components, subsystems, relationships, interactions, the properties of each of these elements, and the set of guiding principles that together constitute the fundamental properties and constraints of a software system or set of systems. （1）defines a general set of element types and their interactions. The examples include Pipes and Filters, Model-View-Controller, and Reflection. A （2）in software architecture is a representation used to understand or document one or more aspects of a problem or solution. Architecture is usually used in conjunction with many adjunct terms. The（3） defines the key strategies, organization, goals and related processes of the enterprise. At the enterprise level, the （4）may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise. The （5）, which describes the high-level set of elements involved in application from a particular domain along with their interactions, is often used to focus on subsystem definition rather than application process level definition.

A:model B:domain C:component D:subsystem

The software architecture is a set of software components, subsystems, relationships, interactions, the properties of each of these elements, and the set of guiding principles that together constitute the fundamental properties and constraints of a software system or set of systems. (1) defines a general set of element types and their interactions. The examples include Pipes and Filters, Model-View-Controller, and Reflection. A (2) in software architecture is a representation used to understand or document one or more aspects of a problem or solution. Architecture is usually used in conjunction with many adjunct terms. The (3) defines the key strategies, organization, goals and related processes of the enterprise. At the enterprise level, the (4) may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise. The (5) , which describes the high-level set of elements involved in application from a particular domain along with their interactions, is often used to focus on subsystem definition rather than application process level definition.

A:model B:domain C:component D:subsystem

The software architecture is a set of software components, subsystems, relationships, interactions, the properties of each of these elements, and the set of guiding principles that together constitute the fundamental properties and constraints of a software system or set of systems. (71) defines a general set of element types and their interactions. The examples include Pipes and Filters, Model-View-Controller, and Reflection. A (72) in software architecture is a representation used to understand or document one or more aspects of a problem or solution. Architecture is usually used in conjunction with many adjunct terms. The (73) defines the key strategies, organization, goals and related processes of the enterprise. At the enterprise level, the (74) may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise. The (75) , which describes the high-level set of elements involved in application from a particular domain along with their interactions, is often used to focus on subsystem definition rather than application process level definition.

A:model B:domain C:component D:subsystem

The software architecture is a set of software components, subsystems, relationships,interactions, the properties of each of these elements, and the set of guiding principles that together constitute the fundamental properties and constraints of a software system or set of systems. （） defines a general set of element types and their interactions. The examples include Pipes and Filters, Model-View-Controller, and Reflection. A （） in software architecture is a representation used to understand or document one or more aspects of a problem or solution. Architecture is usually used in conjunction with many adjunct terms. The （） defines the key strategies, organization, goals and related processes of the enterprise. At the enterprise level, the （） may be more of a set of guidelines on how the various software architectures should be constructed consistently across the enterprise. The （）, which describes the high-level set of elements involved in application from a particular domain along with their interactions, is often used to focus on subsystem definition rather than application process level definition.

A:model B:domain C:component D:subsystem