(19) Korean Intellectual Property Office (KR)
`
`(12) Notice of Publication of Registration (A)
`
`(11) Publication No.: 10-2002-0036354
`
`(43) Publication Date: May 16, 2002
`
`(cid:1009)(cid:3)
`
`(51) Int. Cl.7
`
`H04M 3/00
`
`(21) Application No.: 10-2000-0066497
`
`(22) Application Date: November 9, 2000
`
`(cid:1005)(cid:1004)(cid:3)
`
`(71) Applicants: LG Electronics Inc.; Koo Ja-hong; 20, Yeouido-dong,
`
`Yeongdeungpo-gu, Seoul, Republic of Korea
`
`(72) Inventors: Kim Tae-yong; 302, Ejeong villa, Mok 2-dong 534-13, Yancheon-gu,
`
`Seoul, Republic of Korea
`
`(74) Agents: Kim Young-chul
`
`(cid:1005)(cid:1009)(cid:3)
`
`Request Date for Examination: None
`
`(54) Title (EN): METHOD FOR LOADING USING DISTRIBUTED SYSTEM
`
`STARTUPLOADER IN PRIVATE BRANCH EXCHANGE
`
`(54) Title (KR):    
` 

 

 
`
`(cid:1006)(cid:1004)(cid:3)
`
`
`
`
`
`INTEL 1012
`
`

`

`Abstract
`
`The present invention relates to a loading processing method using a distributed
`
`system startup loader in an exchanger. The loading processing method is
`
`(cid:1009)(cid:3)
`
`characterized by including the steps of: (a) transmitting, by a booter of a device in
`
`the exchanger, a loading request message to a system startup loader built in a system
`
`management processor; (b) determining, by the system startup loader, whether the
`
`device that has transmitted the loading request message is a device processor or a
`
`data control device when the loading request message in step (a) is received; (c)
`
`(cid:1005)(cid:1004)(cid:3)
`
`determining, by the system startup loader, whether an SSP to which the device
`
`processor or the data control device belongs is either operating or starting up when
`
`the device that has transmitted the loading request message is the device processor or
`
`the data control device in step (b); (d) delivering, by the system startup loader, the
`
`loading request message to a distributed system startup loader in the SSP when the
`
`(cid:1005)(cid:1009)(cid:3)
`
`SSP is either operating or starting up in step (c), and transmitting, by the distributed
`
`system startup loader, a response message responding to the loading request in step
`
`(a) to the booter; (e) transmitting, by the distributed system startup loader, program
`
`block header information to the booter when a message for requesting the program
`
`block header information is received from the booter; and (f) transmitting, by the
`
`(cid:1006)(cid:1004)(cid:3)
`
`distributed system startup loader, a program block to the booter when a message for
`
`requesting the program block is received from the booter, and transmitting, by the
`
`distributed system startup loader, a loading end message for one block. With the
`
`method according to the present invention, it is possible to prevent an overloading of
`
`a system management processor and block a loss of IPC by distributively processing
`
`
`
`

`

`a loading for a device processor and a loading for a data control device by using the
`
`distributed system startup loader, thereby securing enhancement of the entire
`
`exchanger loading speed and stable execution of application program blocks
`
`Representative Drawing
`
`(cid:1009)(cid:3)
`
`FIG. 5
`
`Keywords
`
`Keywords: distribution, system startup loader, exchanger
`
`Disclosure
`
`Brief Description of Drawings
`
`(cid:1005)(cid:1004)(cid:3)
`
`FIG. 1 shows a loading system configuration of a conventional exchanger.
`
`FIG. 2 shows a configuration of a loading system using a distributed system startup
`
`loader according to a preferred embodiment of the present invention.
`
`FIG. 3 is a flowchart showing a loading procedure of each of a system startup loader
`
`and a booter in a conventional exchange system.
`
`(cid:1005)(cid:1009)(cid:3)
`
`FIG. 4 shows a flowchart of operations of a system startup loader and a booter
`
`according to a preferred embodiment of the present invention.
`
`FIG. 5 is a flowchart showing operations of a distributed system startup loader and a
`
`system startup loader according to a preferred embodiment of the present invention.
`
`Detailed Description of the Invention
`
`(cid:1006)(cid:1004)(cid:3)
`
`Objective of the Invention
`
`The art to which the present invention pertains and related art thereof
`
`
`
`

`

`The present invention relates to a loading processing method using a
`
`distributed system startup loader in an exchanger, and more particularly, to a loading
`
`processing method capable of solving a problem in which a system management
`
`processor assigns loads to all associated devices during loadings by installing a
`
`(cid:1009)(cid:3)
`
`distributed system startup loader in a switching subsystem (hereinafter referred to as
`
`"SSP").
`
`FIG. 1 shows a loading system configuration of a conventional exchanger.
`
`As shown in FIG. 1, the loading system configuration of the conventional
`
`exchanger includes a system management processor 11, a hard disk drive 17, a
`
`(cid:1005)(cid:1004)(cid:3)
`
`plurality of port management assemblies 12, a plurality of main processors 13, a
`
`plurality of SSPs 14, a plurality of device processors 15, and a plurality of data
`
`control devices.
`
`Only the system management processor 11 is directly connected to the hard
`
`disk drive 17, which stores blocks needed to be loaded. The other devices may be
`
`(cid:1005)(cid:1009)(cid:3)
`
`connected to the hard disk drive 17 through inter-processor communications
`
`(hereinafter referred to as "IPC"). In FIG. 1, solid lines indicate paths for loading
`
`requests. As shown in FIG. 1, conventionally, all loading devices request blocks
`
`needed to be loaded through the system management processor. A system startup
`
`loader, which is a loading server, is built in the system management processor to
`
`(cid:1006)(cid:1004)(cid:3)
`
`transmit the needed blocks to a loading device that has requested the blocks. A
`
`loading process will be described in detail below.
`
`First, a booter of each of the SSPs 14 or the main processors 13 requests a
`
`block needed for a processor startup from the system startup loader of the system
`
`management processor. When the request is received, the system startup loader
`
`
`
`

`

`determines from which device the request is transmitted and transmits an appropriate
`
`block to the device. In this case, each of the main processors 13 or the SSPs 14
`
`receives a program loader, program loading data, an operating system (OS), and a
`
`shell, which are blocks suitable for the processors, from the system startup loader.
`
`(cid:1009)(cid:3)
`
`When the main processors and the SSPs start up through the above method, each of
`
`the data processors 15, the port management blocks 12, and the data control devices
`
`16 transmits a loading request to the system startup loader and receives needed
`
`firmware and OS application program blocks from the system startup loader.
`
`FIG. 3 is a flowchart showing a loading procedure of each of a system
`
`(cid:1005)(cid:1004)(cid:3)
`
`startup loader and a booter in a conventional exchange system. The loading
`
`procedure will be described in detail below with reference to FIG. 3.
`
`A booter in a device transmits a loading startup notification message to the
`
`system startup loader in the system management processor (S300). When the
`
`loading startup notification message is received (S301), the system startup loader
`
`(cid:1005)(cid:1009)(cid:3)
`
`transmits a response message responding to the loading startup notification to the
`
`booter that has transmitted the loading startup notification (S302). When the
`
`response message responding to the loading startup notification is received (S303),
`
`the booter transmits a message for requesting program block header information
`
`needed for the loading to the system startup loader (S304). When the message is
`
`(cid:1006)(cid:1004)(cid:3)
`
`received, the system startup loader transmits the program block header information
`
`to the booter (S305). When the header information is received, the booter requests
`
`a program block corresponding to actual program content from the system startup
`
`loader (S307). The system startup loader receives the request from the booter
`
`(S308). The system startup loader transmits the program block to the booter (S309),
`
`
`
`

`

`and transmits a loading end message to the booter after the loading of one block is
`
`complete. When there is a block to be received, the booter returns to step S304 in
`
`which the booter transmits a message for requesting program block header
`
`information needed for the loading to the system startup loader. When there is no
`
`(cid:1009)(cid:3)
`
`longer a block to be received, the booter ends the loading.
`
`The above-described conventional loading method for devices in an
`
`exchanger may have the following problems. When all devices in the exchanger
`
`request loadings at the same time, the load of the system management processor may
`
`increase and thus cause a loss of IPC and a delay of instruction processing. As a
`
`(cid:1005)(cid:1004)(cid:3)
`
`result, the loading for a specific device may be delayed or even stopped. Thus,
`
`blocks executed by the system management processor may not properly work due to
`
`the load for the loading.
`
`Problems to be solved by the Invention
`
`In order to solve the conventional problems described above, the present
`
`(cid:1005)(cid:1009)(cid:3)
`
`invention is intended to propose a loading processing method using a distributed
`
`system startup loader in an exchanger, the loading processing method being capable
`
`of reducing the load while loading is performed by a system management processor,
`
`by installing the distributed system startup loader in an SSP.
`
`Configurations and Actions of the Invention
`
`(cid:1006)(cid:1004)(cid:3)
`
`In order to solve the above-described problems, a loading processing method
`
`using a distributed system startup loader in an exchanger includes the steps of: (a)
`
`transmitting, by a booter of a device in the exchanger, a loading request message to a
`
`system startup loader built in a system management processor; (b) determining, by
`
`
`
`

`

`the system startup loader, whether the device that has transmitted the loading request
`
`message is a device processor or a data control device when the loading request
`
`message in step (a) is received; (c) determining, by the system startup loader,
`
`whether an SSP to which the device processor or data control device belongs is either
`
`(cid:1009)(cid:3)
`
`operating or starting up when the device that has transmitted the loading request
`
`message is the device processor or the data control device in step (b); (d) delivering,
`
`by the system startup loader, the loading request message to a distributed system
`
`startup loader in the SSP when the SSP is either operating or starting up in step (c),
`
`and transmitting, by the distributed system startup loader, a response message
`
`(cid:1005)(cid:1004)(cid:3)
`
`responding to the loading request in step (a) to the booter; (e) transmitting, by the
`
`distributed system startup loader, program block header information to the booter
`
`when a message for requesting the program block header information is received
`
`from the booter; and (f) transmitting, by the distributed system startup loader, a
`
`program block to the booter when a message for requesting the program block is
`
`(cid:1005)(cid:1009)(cid:3)
`
`received from the booter, and transmitting, by the distributed system startup loader, a
`
`loading end message for one block.
`
`The loading processing method may further include, after whether the SSP is
`
`either operating or starting up is determined in step (c): determining, by the system
`
`startup loader, whether the block to be loaded to the device processor or the data
`
`(cid:1006)(cid:1004)(cid:3)
`
`control device that has requested the loading is updated; and setting, by the system
`
`startup loader, information regarding the determination as a reload field and adding,
`
`by the system startup loader, the reload field to the loading request message that is to
`
`be delivered to the distributed system startup loader in step (d).
`
`
`
`

`

`The loading processing method may further include, before the response
`
`message responding to the loading request in step (d) is transmitted, requesting, by
`
`the distributed system startup loader, transmission of the updated block from the
`
`system startup loader, and transmitting, by the system startup loader, the updated
`
`(cid:1009)(cid:3)
`
`block to the distributed system startup loader when the block to be loaded to the
`
`device processor or the data control device is updated.
`
`Hereinafter, a preferred embodiment of a loading processing method using a
`
`distributed system startup loader in an exchanger according to the present invention
`
`will be described in detail with reference to the accompanying drawings.
`
`(cid:1005)(cid:1004)(cid:3)
`
`FIG. 2 shows a configuration of a loading system using a distributed system
`
`startup loader according to a preferred embodiment of the present invention.
`
`According to a preferred embodiment of the present invention, a distributed
`
`system startup loader 24 is built in a switching subsystem (SSP) 23. Accordingly,
`
`FIG. 2 shows only a device processor 25 and a data control device 26 that are
`
`(cid:1005)(cid:1009)(cid:3)
`
`subordinate to the SSP 23 and a system management processor 21 connected to the
`
`SSP 23. The other devices performs loading according to the conventional method.
`
`In FIG. 2, solid lines indicate paths through which the devices in the
`
`exchanger perform loading. As shown in FIG. 2, the SSP 23 performs loading
`
`through the system management processor 21 and inter-processor communications
`
`(cid:1006)(cid:1004)(cid:3)
`
`(IPC) like the conventional art. However, the device processor 25 and the data
`
`control device 26 that are subordinate to the SSP 23 request initial loading from the
`
`system management processor, but the following loading procedure is carried out
`
`through the distributed system startup loader in the SSP 23. However, the data
`
`control device may request the loading even when the SSP does not start up. Thus,
`
`!
`
`

`

`the data control device directly requests the loading from the system management
`
`processor when the SSP does not start up or requests the loading from the SSP after
`
`waiting for a while when the SSP is starting up. Only a single device processor and
`
`a single data control device are shown as belonging to the SSP in FIG. 2. However,
`
`(cid:1009)(cid:3)
`
`when several devices belong to the SSP, all of several device processors or data
`
`control devices perform loading through the distributed system startup loader. The
`
`loading procedure will be described in detail below.
`
`In FIG. 2, dotted lines indicate paths through which a hard disk drive 27
`
`transmits updated blocks to a memory 28 of the SSP 23 in order to synchronize
`
`(cid:1005)(cid:1004)(cid:3)
`
`blocks in the hard disk drive 27 with blocks in the memory 28 of the SSP 23. A
`
`method for the synchronization will be described in detail below.
`
`FIG. 4 shows a flowchart of operations of a system startup loader and a
`
`booter according to a preferred embodiment of the present invention.
`
`Like the conventional art, a booter of a device transmits a loading
`
`(cid:1005)(cid:1009)(cid:3)
`
`notification message to a system startup loader in a system management processor
`
`(S300), and the system startup loader receives the loading notification message from
`
`the booter (S301). When the loading notification message is received, the system
`
`startup loader does not immediately respond to the reception unlike the conventional
`
`art. Instead, in order to determine whether loading should be performed by the
`
`(cid:1006)(cid:1004)(cid:3)
`
`system startup loader or a distributed system startup loader, the system startup loader
`
`determines whether the device that has transmitted the loading notification message
`
`is a data processor or a data control device (S402).
`
`When the device that has transmitted the loading notification message is not
`
`a device processor or a data control device (for example, a main processor or an SSP),
`
`"
`
`

`

`the system startup loader transmits a response message responding to the loading
`
`notification to the booter (S408) and the booter receives the response message from
`
`the system startup loader (S409), like the conventional art. The booter requests
`
`header information of a program block needed for the loading from the system
`
`(cid:1009)(cid:3)
`
`startup loader (S410) and the system startup loader transmits the requested header
`
`information of the block from the booter (S411). The booter transmits a program
`
`block request message for requesting text code or data code, which is an actual
`
`program block, to the system startup loader on the basis of the received header
`
`information of the block (S413). The system startup loader receives the program
`
`(cid:1005)(cid:1004)(cid:3)
`
`block request message (S414) and transmits the requested program block to the
`
`booter (S415). After the block transmission is complete, the system startup loader
`
`transmits a loading end message indicates that the loading of one block ends to the
`
`booter (S416), and the booter determines whether there is a block to be loaded
`
`(S417). When there is a block to be loaded, the booter returns to step S410 in
`
`(cid:1005)(cid:1009)(cid:3)
`
`which the booter requests program header information. When there is no longer a
`
`block to be loaded, the booter ends the loading.
`
`When the device that has transmitted the loading notification message is a
`
`device processor or a data control device, the loading work is performed by the
`
`distributed system startup loader installed in the SSP. To this end, the system
`
`(cid:1006)(cid:1004)(cid:3)
`
`startup loader checks to which of several SSPs that are present in the exchanger the
`
`device processor or data control device that has transmitted the loading notification
`
`message belongs (S403). When the SSP to which the device is belongs is
`
`confirmed, the system startup loader checks whether the SSP is either operating or
`
`starting up (S404).
`
` #
`
`

`

`When the SSP is not operating or starting up, the loading is performed by the
`
`system startup loader because the loading work cannot be performed by the
`
`distributed system startup loader. Accordingly, step S408 in which the system
`
`startup loader transmits a response message responding to the loading notification to
`
`(cid:1009)(cid:3)
`
`the booter is performed, and then the loading work is performed according to the
`
`steps of the above-described loading process.
`
`When the SSP is either operating or starting up, the loading is performed by
`
`the distributed system startup loader installed in the SSP. As shown in FIG. 2,
`
`unlike the system management processor, the SSP having the distributed system
`
`(cid:1005)(cid:1004)(cid:3)
`
`startup loader installed therein is not connected to the hard disk drive and includes a
`
`separate memory. When the loading is performed through the system startup loader,
`
`blocks needed to be loaded to the device processor and the data control device that
`
`belong to the SSP are received from the system startup loader and stored in the
`
`memory. As shown in FIG. 2, a block needed to be loaded to the device processor
`
`(cid:1005)(cid:1009)(cid:3)
`
`refers to "DP_Block," and a block needed to be loaded to the data control device
`
`refers to "DH_Block." Generally, "DP_Block" and "DH_Block" stored in the hard
`
`disk drive have the same details as "DP_Block" and "DH_Block" stored in the
`
`memory of the SSP. However, depending on the case, only "DP_Block" and
`
`"DH_Block" of the hard disk drive may be updated. In this case, a problem occurs
`
`(cid:1006)(cid:1004)(cid:3)
`
`in that when the loading is performed by the distributed system startup loader, the
`
`device processor loads "DP_Block" and "DH_Block" of the memory of the SSP,
`
`which are not uploaded. Accordingly, there is a need for a synchronization process
`
`for matching "DP_Block" and "DH_Block" stored in the hard disk drive with
`
`"DP_Block" and "DH_Block" stored in the memory.
`
`
`
`

`

`Such a synchronization process should be performed before the distributed
`
`system startup loader transmits a needed block to the device processor or the data
`
`control device. Accordingly, when it is confirmed that the SSP to which the device
`
`processor or the data control device belongs is either operating or starting up, the
`
`(cid:1009)(cid:3)
`
`system startup loader determines whether "DP_Block" and "DH_Block" stored in the
`
`hard disk drive are updated (S405). According to a preferred embodiment of the
`
`present invention, whether the blocks are updated is determined through a method of
`
`checking the sizes and checksum information of the blocks. The system startup
`
`loader checks the sizes and checksum information of the blocks to be loaded from
`
`(cid:1005)(cid:1004)(cid:3)
`
`the hard disk drive to the data processor and the data control device and stores the
`
`sizes and checksum information in the memory of the system management processor
`
`whenever the system startup loader starts up. Subsequently, when a loading
`
`notification message is transmitted from the device processor or the data control
`
`device, the system startup loader determines whether to upload the blocks by
`
`(cid:1005)(cid:1009)(cid:3)
`
`comparing the size and checksum information of the block stored in the memory
`
`with the size and checksum information of the block stored in the hard disk drive.
`
`When the information of the hard disk drive is updated later, the size and checksum
`
`information of the block stored in the memory may be different from the size and
`
`checksum information of the block stored in the hard disk drive.
`
`(cid:1006)(cid:1004)(cid:3)
`
`When the block of the hard disk drive is not updated, the system startup
`
`loader delivers a loading notification message including information indicating the
`
`block is not uploaded to the distributed system startup loader in the SSP (S407).
`
`The loading notification message delivered from the system startup loader to the
`
`distributed system startup loader includes a reload field to represent whether the
`
` 
`
`

`

`corresponding block is updated. When the block of the hard disk drive is updated,
`
`the system startup loader sets the reload field to "true" (S406) and transmits a loading
`
`notification message including the reload field to the distributed system startup
`
`loader of the SSP (S407).
`
`(cid:1009)(cid:3)
`
`FIG. 5 is a flowchart showing operations of the distributed system startup
`
`loader and the system startup loader according to a preferred embodiment of the
`
`present invention.
`
`As described above, when a device that has requested a loading is a device
`
`processor or a data control device, the distributed system startup loader receives a
`
`(cid:1005)(cid:1004)(cid:3)
`
`loading notification message including reload information from the system startup
`
`loader (S500). When the loading notification message is received, the distributed
`
`system startup loader checks whether a reload field is set to "true" (S501). When
`
`the reload field is set to "true," "DP_Block" and "DH_Block" stored in the memory
`
`of the SSP are not synchronized with "DP_Block" and "DH_Block" stored in the
`
`(cid:1005)(cid:1009)(cid:3)
`
`hard disk drive. Accordingly, the distributed system startup loader requests
`
`transmission of an updated block from the system startup loader (S502). The
`
`system startup loader receives the request from the distributed system startup loader
`
`(S503) and transmits the uploaded block to the distributed system startup loader
`
`(S504). The distributed system startup loader receives and stores the block in a
`
`(cid:1006)(cid:1004)(cid:3)
`
`memory (S505).
`
`When the reload field is not set to "true" or after the uploaded block is
`
`received from the system startup loader and stored in the memory, the distributed
`
`system startup loader transmits a response message responding to a loading
`
`notification to a device process or a data control device that has transmitted a loading
`
` 
`
`

`

`notification message (S506). Subsequently, the distributed system startup loader
`
`performs the same process as that of the conventional system startup loader. When
`
`program header information is requested from the device, the distributed system
`
`startup loader transmits program block header information (S507). After the header
`
`(cid:1009)(cid:3)
`
`information is transmitted, the distributed system startup loader receives a program
`
`block request message for requesting actual program block data from the device
`
`(S508) and transmits the requested program block (S509). After the loading of one
`
`block is complete, the distributed system startup loader transmits a loading end
`
`message (S510).
`
`(cid:1005)(cid:1004)(cid:3)
`
`Advantageous Effects
`
`As described above, with the loading processing method using the
`
`distributed system startup loader in an exchanger according to the present invention,
`
`it is possible to prevent an overload of a system management processor and block a
`
`loss of IPC by distributively processing a loading for a device processor and a
`
`(cid:1005)(cid:1009)(cid:3)
`
`loading for a data control device by using the distributed system startup loader,
`
`thereby securing enhancement of the entire exchanger loading speed and stable
`
`execution of application program blocks. Also, it is possible to enhance
`
`development speed during development of a test system by developers and enhance a
`
`degree of maintenance service due to shortening of time for reactivating the system
`
`(cid:1006)(cid:1004)(cid:3)
`
`during maintenance.
`
`
`
`(57) Claims
`
`[Claim 1]
`
` 
`
`

`

`A loading processing method using a distributed system startup loader in an
`
`exchanger, the loading processing method comprising the steps of:
`
`(a) transmitting, by a booter of a device in the exchanger, a loading request
`
`message to a system startup loader built in a system management processor;
`
`(cid:1009)(cid:3)
`
`(b) determining, by the system startup loader, whether the device that has
`
`transmitted the loading request message is a device processor or a data control device
`
`when the loading request message is received in step (a);
`
`(c) determining, by the system startup loader, whether an SSP to which the
`
`device processor or data control device belongs is either operating or starting up
`
`(cid:1005)(cid:1004)(cid:3)
`
`when the device that has transmitted the loading request message is the device
`
`processor or the data control device in step (b);
`
`(d) delivering, by the system startup loader, the loading request message to a
`
`distributed system startup loader in the SSP when the SSP is either operating or
`
`starting up in step (c), and transmitting, by the distributed system startup loader, a
`
`(cid:1005)(cid:1009)(cid:3)
`
`response message responding to the loading request in step (a) to the booter;
`
`(e) transmitting, by the distributed system startup loader, program block
`
`header information to the booter when a message for requesting the program block
`
`header information is received from the booter; and
`
`(f) transmitting, by the distributed system startup loader, a program block to
`
`(cid:1006)(cid:1004)(cid:3)
`
`the booter when a message for requesting the program block is received from the
`
`booter, and transmitting, by the distributed system startup loader, a loading end
`
`message for the block.
`
`[Claim 2]
`
`The loading processing method of claim 1, further comprising, after whether
`
`(cid:1006)(cid:1009)(cid:3)
`
`the SSP is either operating or starting up is determined in step (c):
`
` 
`
`

`

`determining, by the system startup loader, whether the block to be loaded to
`
`the device processor or the data control device that requests the loading is updated;
`
`and
`
`setting, by the system startup loader, information regarding the
`
`(cid:1009)(cid:3)
`
`determination as a reload field and adding, by the system startup loader, the reload
`
`field to the loading request message that is to be delivered to the distributed system
`
`startup loader in step (d).
`
`[Claim 3]
`
`The loading processing method of claim 1 or claim 2, further comprising,
`
`(cid:1005)(cid:1004)(cid:3)
`
`before the response message responding to the loading request in step (d) is
`
`transmitted, requesting, by the distributed system startup loader, transmission of the
`
`updated block from the system startup loader, and transmitting, by the system startup
`
`loader, the updated block to the distributed system startup loader when the block to
`
`be loaded to the device processor or the data control device is updated.
`
`(cid:1005)(cid:1009)(cid:3)
`
`[Claim 4]
`
`The loading processing method of claim 2, wherein the determination of
`
`whether the block to be loaded is updated is achieved by performing comparison on
`
`block sizes and checksum information.
`
` 
`
`

`

`FIG. 1(cid:3)
`
`DRAWINGS
`DRAWINGS
`
`
`
`
`
`— MANAGEMENT||MANAGEMENT] + - -|MANAGEMENT+|
`
`
`
`HARD DISK 12_|.|PORT PORT | T
`
`
`
`
`DRIVE ASSEWELY1|__AS: ‘ASSEMBLYn
`
`|
`NY
`-
`12
`
`17
`
`MAIN PROCESSOR 1
`
`r
`
`:
`:
`
`WAIN PROCESSOR n
`
`/
`13
`f
`
`|
`
`!
`
`14
`
`
`
`posaananannabennnnn“SWITCHING SUBSYSTEM] _[———{eS15
`
`
`
`!
`
`[~!—IpRocuSsSOR|
`
`r!
`7
`'
`.
`'
`.
`
`
`
`
`
`
`
`:
`i
`
`"PROCESSOR 1
`
`
`Poonam nanan +------| SRITCHING suBsysTA]
`)
`PROCESSOR 2
`'
`/
`.
`1
`.
`La
`a
`bone nnnnn nnn poncn nn ‘SWITCHING SUBSYSTEM.
`|" PROCESSOR n
`|
`1
`atTATA
`CONTROL
`| DEVICE 1
`{
`
`16~~)
`
`_'—t—pROGHSSOR
`
`t
`
`1 5
`
`.
`/
`
`'
`
`)
`
`
`
`FIG. (cid:1006)(cid:3)
`
`
`
`
`SWITCHING
`SUBSYSTEM
`PROCESSOR
`DISTRIBUTED
`SYSTEN
`ea
`STARTUP LOADER
`
`24--T
`
`
`
`
`HARD DISK DRIVE
`
`
`ck
`DP_Block
`OP BI
`
`DF _Biok
`ODH_Block
`
`
`
`27—~
`
`(cid:1009)(cid:3)
`
`28
`
`vey|MEMORY
`
`
`
`
`23
`
`
`
`DEVICE
`PROCESSOR 0
`
`25
`
`DEVICE 0
`DATA CONTROL
`
`7
`
`26
`
`
`
`17
`
`
`

`

`(cid:38)(cid:47)(cid:39)(cid:856)(cid:3)(cid:1007)(cid:3)
`FIG. 3
`
`$301
`
`~
`
`$302
`
`$305
`
`$308
`
`SYSTEM STARTUP»)
`Osa)
`RECEIVE {oxpry
`AR’
`P
`NOTIFICATION
`
`.
`
`a
`\ Rom )
`/TRANSMIT LOADING
`ontttton
`_
`NOUissies
`
`$200
`a
`531
`S800
`
`$303
`
`__y
`BLOCK HEADER
`INFORMATION
`
`$30
`
`4
`
`S306—-
`
`RECEIVE PROGRAM
`INFORMATION
`BLOCK HEADER
`
`|
`
`
`
`s309~
`
`3307 RSHPROGRAM
`
`—
`
`/aewsar
`ING END
`
`$310
`
`S3i
`
`a=
`~~ 18 THRE
`> Bae
`LOK?
`NO
`
`YES
`
`FIG. (cid:1008)(cid:3)
`
`
`
`
`
`
`
`
`
`
`(soma)
`yo
`S400~—{aiTUP NOTIBICATI
`MESSAGE
`|
`
`
`
`$402
`
`1S DEVICE EER
`DEVICE PROCESSOR OR
`OAOONTROL,
`
`CAPE LOADING |
`
`(wae
`
`a
`|g
`DETERMINE TO WCE
`aH |--s408
`SAUCES BELONGS
`
`-—]
`
`6409
`$409
`
`rE Y
`NOTIFICATION
`MESSAGE
`
`
`
`18
` !
`
`

`

`FIG. (cid:1009)(cid:3)
`FIG. 5
`
`
`DISTRIBUTED.
`SYSTEM STARTUP LOADER
`
`
`
`NOTATION AESSAGE
`S500-—
`INCLUDING
`RELOAD FIELD
`
`
`
`
`—
`L
`|
`ANOADNG
`S506-— (onaAace 4
`
`
`RECEIVE BLOGK
`
`$503-—~
`
`$504-~
`
`-S5C
`
`$505
`
`19
` "
`
`

`

`
`
`oy.Multiling tuncconsonarion
`
`180 NORTH UNIVERSITY AVE.
`Suite 600
`PROVO, UT 84601-4474
`
`VOICE (801) 377-2000
`FAX (801) 377-7085
`
`TRANSLATOR’S CERTIFICATE OF TRANSLATION
`
`Translation from Korean to English.
`MultiLing Project Number: WH1730001HQ
`Client: Wilmer Hale.
`
`MultiLing Corporation, a Delaware corporation, which has its principal office at 180 North
`University Avenue, Suite 600, Provo, UT 84601-4474, USA,certifies that
`
`(a) it is a professional translation company of multiple languages including English and
`Korean;
`(b) it has translated from the original documentto the translated document identified below,
`and to the best of its knowledge, information,andbelief the translation of that documentis
`accurate as a publication quality translation; and further,
`(c) these statements were made with the knowledge that willful false statements and the like
`so madeare punishable by fine or imprisonment, or both, under Section 1001 of Title 18
`of the United States Code.
`
`Original Document Identifier: ATTACHMENT4 KR 2002-0036354.pdf and
`ATTACHMENT6 KR 2009-0036339.pdf
`Translated DocumentIdentifier: WH1730001HQ-ATTACHMENT4en-US.doc and
`WH1730001HQ-ATTACHMENT®6_en-US.doc
`
`
`\day of September, 2017,
`Signed thi
`
`
`Michael Degn,
`nt Management
`
`ACKNOWLEDGMENT BEFORE NOTARY
`
`State of Utah
`
`County of Utah
`
`}ss,
`
`On this 28" day of September, 2017 before me, the undersigned Notary Public, personally appeared Michael Degn,
`whoproved onthe basis of satisfactory evidence to be the person whose name is subscribed to this Translator’s
`Certificate of Translation and who acknowledgedthat he or she executed the same for the purposesstatedtherein.
`IN WITNESS WHEREOF,I hereunto set my hand andofficialseal.
`
` Notary Public, residing at Lehi, UT
`
`Certificate of Translation - WH1730001HQ.docx
`
`173353
`
`20
`
`20
`
`