This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
This person has a SecurePRO™ card. Because this person is not a ProZ.com Plus subscriber, to view his or her SecurePRO™ card you must be a ProZ.com Business member or Plus subscriber.
Affiliations
This person is not affiliated with any business or Blue Board record at ProZ.com.
English to Chinese: METHODS AND APPARATUS FOR ARTIFACT REMOVAL FOR BIT DEPTH SCALABILITY General field: Law/Patents Detailed field: Patents
Source text - English METHODS AND APPARATUS FOR ARTIFACT REMOVAL FOR BIT DEPTH SCALABILITY
ABSTRACT
There are provided methods and apparatus for artifact removal for bit depth scalability. The method and apparatus utilize an encoder (100) for encoding an enhancement layer for at least a portion of a picture. A deblocking filter is applied at the enhancement layer for bit depth scalability (500). A decoding method and apparatus are described for decoding an enhancement layer for at least a portion of a picture, wherein the during the decoding process, a deblocking filter is applied at the enhancement layer for bit depth scalability (600). Furthermore, an encoder and method are described for encoding image data for at least one block of a picture, wherein a deblocking filter (117) removes coding artifacts caused by local inverse tone mapping for intra-layer texture prediction for bit depth scalability. A decoding method and apparatus are described for decoding image data for at least one block of a picture, wherein a deblocking filter (230, 237, 435) removes coding artifacts caused by local inverse tone mapping for intra-layer texture prediction for bit depth scalability.
CLAIMS:
1. An apparatus, comprising:
an encoder (100, 300) for encoding an enhancement layer for at least a portion of a picture, wherein
English to Chinese: Remote Site Installation Overview General field: Tech/Engineering Detailed field: Computers (general)
Source text - English
Remote Site Installation Overview
A Remote Site provides remote (from the Master Site) functionality in a Dimetra IP system. There are two types of remote sites: Control Site and EBTS/MBTS Site. A Control Site provides remote dispatch capabilities and remote access to network management functions. The EBTS/MBTS Site contains the base station radio transmitter and receiver equipment that provides the actual over-the-air communication between Mobile Stations (MSs) and the network infrastructure.
Figure 1-1 shows an example of Control Site and EBTS/MBTS Site locations in relation to the Master Site.
Please review Chapter 1 before starting to install either a Control Site or an EBTS/MBTS Site.
Figure 1-1 System Diagram does not apply for a Dimetra SCO system.
Figure 1-1 Dimetra IP System Overview
Figure 1-2 Dimetra SCO System Overview
Figure 1-2 Dimetra SCO System Overview only applies for a Dimetra SCO system.
This page intentionally left blank
Control Sites
A Control Site primarily provides a de-centralized location for performing dispatching functions on the Dimetra IP system. In addition, connections for remote network management clients and third-party equipment are provided at the control site (within the Motorola IP domain).
A control site can be located either within the Motorola IP network domain or in a Customer Enterprise Network (CEN) IP domain.
Control Sites in Motorola IP Domain
A Dimetra SCO system does not contain the Cisco Catalyst 6509 Ethernet LAN switch (LAN switch) and the Nortel® Passport 7480 WAN Switch (WAN Switch). Instead of the Nortel® Passport 7480 WAN Switch, Core Routers are used for this function.
The control site in the Motorola IP domain is considered part of the Dimetra IP network infrastructure. An Ethernet LAN switch is installed and maintains separate LANs for Motorola equipment and third-party equipment located at the control site. The Motorola equipment LAN is connected to the master site via a Gateway Router, while the third-party equipment LAN (and connections to customer enterprise networks (CENs)) are connected to the master site via a Border Router.
For the dispatching function, the control site can be designed with or without a co-located Central Electronics Bank (CEB). With a co-located CEB, the control site contains the following equipment:
• Motorola Centracom Gold Elite Dispatch system, including:
° Console Interface Electronics (CIE)
° Dispatch Console (DC)
° Central Electronics Bank (CEB)
• Network Transport equipment (Ethernet LAN Switch and Routers)
• Network Management Client PCs (optional)
• Third-party equipment (optional)
• Printer (optional)
Figure 2-1 shows an example of a control site with co-located CEB in the Motorola IP domain.
Figure 2-1 Control site with co-located CEB (Motorola IP domain)
As shown in the diagram, an E1 multiplexer can be inserted in case the output from the Border and Gateway routers need to be groomed into one E1 link.
When the Central Electronics Bank (CEB) is not co-located at the control site, the remote dispatch equipment connects to the CEB at the master site via ROCI/CORI modem connection. The following equipment is installed when the Central Electronics Bank (CEB) is not co-located at the control site:
• Motorola Centracom Gold Elite Dispatch system, including:
° Console Interface Electronics (CIE)
° Dispatch Console (DC)
• Network Transport equipment (Ethernet LAN Switch, Routers, and Channel Bank)
• Channel Bank
• Network Management Client PCs (optional)
• Third-party equipment (optional)
• Printer (optional)
Figure 2-2 shows an example of a control site with CORI/ROCI modem connection (no remote CEB) in the Motorola IP domain.
Figure 2-2 Control site with CORI/ROCI Modem Connection to CEB (Motorola IP domain)
Network Transport Equipment Configurations
Network transport equipment connect the required combination of Elite Dispatch Operator positions, third-party clients, network management clients, and printers in local area networks (LANs) at the control site using a Ethernet LAN switch. Connection to the master site is provided from the LAN switch using both Control Site routers (for Motorola equipment) and Border routers (for third-party equipment). The ethernet ports of the Border and Control Site routers are connected to the LAN switch, while the router WAN ports are connected to the master site via Telco lines. For certain configurations, a channel bank is deployed for grooming all connections between the control site and master site. The channel bank grooms these connections and transports them over an E1 link.
Configuration of the LAN switch and routers is dependent on the number of the ports required and types of equipment and applications the control site will be running. Table 2-1 provides a listing of possible control site equipment combinations and the network transport equipment needed for each.
Table 2-1 Network transport equipment configurations
Configuration LAN Switch Control Site Router Border Router
Dispatch equipment, third-party equipment, and network management clients ■ ■ ■
Third-party equipment and network management clients
■ ■ ■
Table 2-1 Network transport equipment configurations (Continued) Configuration
Configuration LAN Switch Control Site Router Border Router
Dispatch equipment and Third-party equipment ■ ■ ■
Dispatch equipment only ■ ■
Network management clients only ■ ■
Dispatch equipment and network management clients ■ ■
Third-party equipment only ■
For the Ethernet LAN switch, configuration is performed via the unit's command line interface (CLI).
Configuration of the dispatch console (DC) at the control site is done at the Elite Console Database Manager (CDM) and Alias Database Manager (ADM) applications located on the Elite Server at the master site. For configuration of the dispatch console, see Chapter 11, "Dispatch Consoles Configuration.", booklet 3, "Master Site Configuration".
In a non-configured LAN switch, all of the ports are defined as untagged and assigned to one VLAN. Ports are then assigned to the appropriate VLANs depending on the system.
Third-Party Equipment Configuration
A separate VLAN is maintained on the LAN switch for third-party applications and equipment located at the control site. Access to the master site (whether from third-party equipment at the control site or from a Customer Enterprise Network (CEN)) is always via a Border router. Using this configuration, access can be provided to the following Dimetra IP network services or APIs:
° Computer Aided Dispatch Interface (CADI)
° Elite API
° Short Data (SD)
° Packet Data (PD)
ATIA access is a special case where the Dimetra IP network is providing Receive Only for customer provided hosts on the Master Site. Receive Only customers hosts are supported by the Dimetra IP network due to security reasons.
The CEN can be connected directly to the DMZ subnet at the Master Site via a Border Router.
Network Management Client Configuration
Network management client PCs at the control site are connected to the LAN switch and are part of the Motorola equipment LAN. Access to the master site is always via a Control Site router.
For configuration of network management client PCs, see Chapter 4, "Network Manager Servers and Clients Configuration.", booklet 3, "Master Site Configuration".
Printer Configuration
Printers at the control site are connected to the LAN switch and are part of the Motorola equipment LAN. Access to the master site is always via a Control Site router.
For configuration of printers, see Chapter 10, "Master Site Switches Hardware Installation", booklet 1, "Master Site Hardware Installation".
Control Sites in Customer Enterprise Network (CEN) IP Domain
The control site in the Customer Enterprise Network (CEN) IP domain is not considered part of the Dimetra IP network infrastructure. Thus, routers are deployed between Motorola and CEN IP domains to provide necessary isolation between the networks. Figure 2-3 illustrates the typical flow of IP packet traffic between the control site (in the CEN IP domain) and the master site (in the Motorola IP domain).
Figure 2-3 IP packet traffic flow
The use of remote dispatching functionality in the CEN requires all Elite Dispatch operator positions and equipment (for the entire system) to be installed in the CEN IP domain. Thus, dispatching operations can be performed exclusively within the Motorola IP domain or CEN IP domain (but not both). Like with a control site in the Motorola IP domain, the Central Electronics Bank (CEB) can be co-located at the control site in the CEN IP domain. With a co-located CEB, the control site contains the following Elite Dispatch system equipment:
• Console Interface Electronics (CIE)
• Dispatch Console (DC)
• Elite Server
• Central Electronics Bank (CEB)
Figure 2-4 shows an example of a control site with co-located CEB in the CEN IP domain.
Figure 2-4 Control site with co-located CEB (CEN IP domain)
When the Central Electronics Bank (CEB) is not co-located at the control site, the remote dispatch equipment connects to the CEB at the master site via ROCI/CORI modem connection. The following equipment is installed when the CEB is not co-located at the control site:
• Console Interface Electronics (CIE)
• Dispatch Console (DC)
• Elite Server
Figure 2-5 shows an example of a control site with CORI/ROCI modem connection (no remote CEB) in the CEN IP domain.
Figure 2-5 Control site with CORI/ROCI Modem Connection (CEN IP Domain)
Elite Server (ADM/CDM) Configuration
An IP communication path must be configured between the Elite Server (containing the Alias Database Manager (ADM) and Console Database Manager (CDM) applications) at the control site and the User Configuration Server (UCS) and Zone Database Server (ZDS) at the master site. This allows the ADM application to synchronize to the UCS, and CDM application to synchronize to the ZDS.
Procedure 2-1 configures the path between these two entities:
Before performing this procedure, ensure that the Elite Server has a Bi-directional One-One NAT IP address established on the appropriate Border router on the system. Similarly, ensure that the Zone Database Server (ZDS) and User Configuration Server (UCS) have Bi-directional One-One NAT IP addresses established on the appropriate Gateway router.
Procedure 2-1 Configuring Elite Server/Zone Database Server path
1 Log on to the Elite Server.
Result: A terminal window with operating system prompt is displayed.
2 Verify that the correct IP address, subnet mask, and default gateway parameters are defined for the Elite Server machine.
3 Open the HOSTS file and add the NAT address of the ZDS machine using the appropriate format.
The HOSTS file is located at C:WINNTsystem32driversetcHOSTS
Procedure 2-1 Configuring Elite Server/Zone Database Server path (Continued)
4 Using the Windows Start menu, select Programs/Administrative Tools/DNS.
Result: The DNS screen appears
5 Right-click on Reverse Lookup Zones.
Result: You see the following window:
Figure 2-6 DNS window
6 Select New Zone from the pop-up menu.
Result: You see the following window:
Figure 2-7 New Zone Wizard window
Procedure 2-1 Configuring Elite Server/Zone Database Server path (Continued)
7 Select Active Directory- integrated and click Next.
Result: You see the following window:
Figure 2-8 Reverse Lookup Zone
8 Enter the ZDS subnet IP address in the Network ID field and click Next.
9 Click Finish.
Result: The DNS server configuration wizard is complete.
10 Repeat step 5 through step 9 for each Customer Enterprise Network (CEN) subnet that contains a control site with Elite dispatch positions/equipment (Elite clients).
11 Reboot the Elite Server.
Elite Dispatch Console PC Configuration
An IP communication path must be configured between each Elite Dispatch Console PC and Elite Server at the control site.
Procedure 2-2 configures the path between these two entities:
Before performing this procedure, ensure that each Elite Dispatch Console PC has a Bi-directional One-One NAT IP address established on the appropriate Border router on the system.
Procedure 2-2 Configuring Elite Server/Elite Dispatch Console PC path
1 Log on to the Elite Dispatch Console PC.
Result: A terminal window with operating system prompt is displayed.
2 Verify that the correct IP address, subnet mask, and default gateway parameters are defined for the Elite Dispatch Console PC.
3 Change the DNS server address of the Elite Dispatch Console PC to point to the IP address of the Elite Server.
The DNS server address of the PC is configured within the Windows network properties dialog box (same location as IP address properties).
4 Reboot the Elite Server.
Radio Control Manager (RCM) Configuration
The Dimetra SCO system consists of one zone in one cluster.
When the Radio Control Manager (RCM) application is installed on an Elite Dispatch Console PC at the control site, an IP communication paths must be configured between each Elite Dispatch Console PC (where the RCM is operated) and the User Configuration Server (UCS) and Zone Database Server (ZDS) at the master site. The RCM application needs to communicate with the UCS to receive cluster information and the ZDS to license and launch the application. Because the RCM application can be operated with any zone in a cluster, the Elite Dispatch Console PC must have IP communication paths to all ZDSs for the cluster.
Procedure 2-3 configures the path between these entities:
Before performing this procedure, ensure that the Cluster UCS Server has a Bi-directional One-One NAT IP address established on the appropriate Gateway router for the zone where the UCS arrives. Similarly, ensure that each Zone Database Server (ZDS) in the cluster has a Bi-directional One-One NAT IP address established on the appropriate Gateway router.
Procedure 2-3 Configuring RCM Application/Zone Database Server and User Configuration Server path
1 Log on to the Elite Dispatch Console PC upon which the RCM application is installed.
Result: A terminal window with operating system prompt is displayed.
2 Open the HOSTS file and add the NAT address of the appropriate Cluster UCS server and each ZDS and License server in the cluster using the appropriate format.
The HOSTS file is located at C:WINNTsystem32driversetcHOSTS
While it is possible to launch the RCM application against any cluster in the nationwide network, it is not recommended for this configuration. If this is required, the NAT address entries for the other clusters and zones must also be added. The default configuration is to configure the RCM application to connect to it's home cluster only.
For a Dimetra SCO system, ignore all references to multiple clusters and zones.
3 Using the Windows Explorer, navigate to the C:Documents and SettingsAll UsersStart MenuProgramsStartup directory.
4 Highlight the filename Motorola Network Mgmt ver DMNM-R11.00.08.02 Backend.lnk in the explorer window.
The version number in the filename will be different depending on the current release of the PRNM application suite.
Procedure 2-3 Configuring RCM Application/Zone Database Server and User Configuration Server path (Continued)
5 Right-click the mouse.
Result: You see the following window:
Figure 2-9 Filename Properties window
6 In the Target field, add the argument -DLOCALDNS="true" .
Result: The resulting string is displayed in the Target field:
"C:Program FilesMotorolaJavaSoftbinjavaw.exe" -DLO-CALDNS="true" -DPNMVERS=%PNMVERS% -DUSERPROFILE="%userprofile%" -DTMPDIR="%MOTOROLA%tmp" -DMOTOROLA="%MOTOROLA%" -cp ".;ap-plauncher.jar" pnm.core.appLauncher.ApplnLauncherMain
7 Reboot the Elite Dispatch Console PC.
8 Once restarted, launch the PRNM application suite.
Result: The PRNM Suite Login window is displayed.
Figure 2-10 Motorola PRNM Suite Login window
9 Change the Server field to reflect the NAT address of the ZDS and login to the PRNM suite.
Result: The PRNM suite is launched and the Motorola icon is displayed in the system tray.
Procedure 2-3 Configuring RCM Application/Zone Database Server and User Configuration Server path (Continued)
10 Right-click on the Motorola icon located in the system tray and select Change Default Server from the pop-up menu.
11 Change the default server to be the NAT address of the ZDS in the local zone.
12 Shutdown and restart the PRNM application suite.
Result: Once restarted, the PRNM Suite Login window now displays the NAT address for the ZDS.
This page intentionally left blank
EBTS/MBTS Sites
Please refer to the EBTS Platform Release 3.0 Manual Set (68P02500U51) for information on EBTS sites. For MBTS sites, please refer to the MBTS 1.0 Installation, Configuration abd Basic Service Manual, (6866538D03).
This page intentionally left blank
Return Authorizations
Dear Customer:
Prior to sending equipment for repair to the European Systems Component Centre (ESCC), please contact the ESCC preferably by email, or otherwise by fax, to request a Return Authorization Number (RAN). This will allow the ESCC staff to check that they support the particular equipment and to identify your equipment upon receival.
When you have your RAN, complete the return authorization form on the following page, write the RAN on the shipping documents and all the relevant paperwork and ship the defective item to the address below.
Always use a static grounding wrist strap to handle any board or module.
The ESCC will not process the return authorization request unless all fields of the return authorization form are fully completed.
Motorola GmbH CGISS
European Systems Component Centre
RAN
Am Borsigturm 130
D-13 507 Berlin
Germany
The above procedure describes the standard warranty conditions. Motorola also offers additional services for customers requiring a more comprehensive support service.
Enquiries for Enhanced Service support packages should be addressed to:
MOTOROLA ESSC, EMEA Systems Support Centre
Jays Close,
Viables Industrial Estate,
Basingstoke,
RG22 4PD.
United Kingdom
Telephone: 44 (0) 1256 484448
在未設定的 LAN 交換器中，所有的埠皆被定義為未標記且指派給一個 VLAN。接著依據系統將埠指派給適當的 VLAN。
第三方設備組態
對於控制站台上的第三方應用程式及設備，會在 LAN 交換器上維護個別的 VLAN。無論是從控制站台處的第三方設備，或是從客戶企業網路 (CEN)，存取主站台時一律會經過邊界路由器。使用此項組態，下列的 Dimetra IP 網路服務或 API 就可以存取主站台：
° 電腦輔助調度介面 (CADI)
° Elite API
° 簡短資料 (SD)
° 封包資料 (PD)
ATIA 存取屬於特殊案例，在此例中，提供的 Dimetra IP 網路僅接收主站台上的客戶主機。基於安全性，Dimetra IP 網路支援僅接收客戶主機。
可以經由邊界路由器將 CEN 直接連接至主站台的 DMZ 子網路。
網路管理用戶端組態
控制站台的網路管理用戶端 PC 連接至 LAN 交換器，並且屬於 Motorola 設備 LAN 部分。一律經由控制站台路由器才能存取主站台。
如需網路管理用戶端 PC 組態相關資訊，請參閱第 3 冊《主控台組態》第 4 章〈Network Manager 伺服器與用戶端組態〉。
印表機組態
控制站台的印表機連接至 LAN 交換器，並且屬於 Motorola 設備 LAN 部分。一律經由控制站台路由器才能存取主站台。
如需印表機組態的相關資訊，請參閱第 1 冊《主站台硬體安裝》第 10 章〈主站台交換器硬體安裝〉。
客戶企業網路 (CEN) IP 網域中的控制站台。
客戶企業網路 (CEN) IP 網域中的控制站台被視為不屬於 Dimetra IP 網路基礎設施部分。因此，會在 Motorola 與 CEN IP 網域之間部署路由器，以便提供必要的網路間隔離。圖 2-3 顯示介於控制站台（在CEN IP 網域中）與主站台（在 Motorola IP 網域中）之間的典型 IP 傳輸封包流程。
圖 2-3 IP 傳輸封包流程
必須在 CEN IP 網域中安裝所有的 Elite 調度操作位置及設備（整個系統），才能在 CEN 中使用遠端調度功能。因此，可在 Motorola IP 網域內或 CEN IP 網域內（但僅限於其中一個網域）以獨佔模式執行調度作業。如同 Motorola IP 網域中的控制站台，中央電子機組 (CEB) 可能與 CEN IP 網域中的控制站台位於同一地點。如果控制站台與 CEB 位於同一地點，則控制站台包含下列 Elite 調度系統設備：
• 主控台介面電子裝置 (CIE)
• 調度主控台 (DC)
• Elite 伺服器
• 中央電子機組 (CEB)
圖 2-4 顯示在 CEN IP 網域中控制站台與 CEB 位於同一地點的範例。
如需 EBTS 站台相關資訊，請參閱《EBTS 平台 3.0 版手冊》(68P02500U51)。如需 MBTS 站台相關資訊，請參閱《MBTS 1.0 Installation, Configuration abd Basic Service Manual》(6866538D03)。
本頁留白
送交回授權單位
客戶敬啟：
將需要維修的設備寄回 European System Component Centre (ESCC) 之前，請先利用電子郵件或傳真聯絡 ESCC，請ESCC 提供「送交回授權單位號碼 (RAN)」。這有助於 ESCC 人員檢查本身支援的特殊設備，並且能夠在收到設備予以識別。
如果您具有 RAN，請填寫下一頁的「送交回授權單位表單」，在運送文件上寫上 RAN 及所有相關的書面資訊，並且將要維修的設備運送至下列地址。
請隨時使用靜電消除腕帶，來處理電路板或模組。
請務必填寫「送交回授權單位表單」上的所有欄位，否則 ESCC 將不予以處理。
Motorola GmbH CGISS
European Systems Component Centre
RAN
Am Borsigturm 130
D-13 507 Berlin
Germany
I am a Professional freelance technical and patent translator with 20 years of translation experience. I have been translated more than millions of words, more than 1000 patent applications, and reviewed millions of translated patent applications in various field. 20 Years' practice in translation exposes me to a variety of materials from product specification, user’s manual, technical specification and standard, patent specification, etc....
Specialized Fields
Technical and patent translation in following areas:
Computer (Application/programming/computing)
Consumer Electronics
Electronics/Electrical Engineering
Electrical/Electrical Engineering
Hardware (Peripherals/Telephone/Television…)
Information System/Technology
IT (software/Operating Systems/Programming/Networks)
Software/ (Engineering/Interfaces/Localization)
Technical manual
Telecommunication/Communication
Keywords: technical and patent translation in following areas:
Computer (Application/programming/computing)
Consumer Electronics
Electronics/Electrical Engineering
Electrical/Electrical Engineering
Hardware (Peripherals/Telephone/Television…)
Information System/Technology
IT (software/Operating Systems/Programming/Networks)
Software/ (Engineering/Interfaces/Localization)
Technical manual
Telecommunication/Communication
Expertise