Local/remote modification of electronically alterable operating system firmware resident in redundant flash memory of remote unit for testing/conditioning subscriber line circuits

Claim 2

For use with a communication system having one or more remote sites at which respective programmable test devices are located, a respective programmable test device employing an operating system for monitoring and testing network lines and subscriber termination equipment coupled thereto, said communication system further including at least one data terminal unit which has the capability of accessing said programmable test device and causing a modification of said operating system, said respective programmable test device containing first and second memory systems, which contain respective first and second versions of said operating system, a method of controlling which of said first and second versions of said operating system is executed by said programmable test device when said programmable test device is placed in operation, comprising the steps of: (a) processing the contents of a prescribed portion of said first and second memory systems to verify operational validity thereof; and (b) causing one of said first and second versions of said operating system contained in said first and second memory systems, for which step (a) has verified operational validity, which has the latest revision level and is not in a downgraded status, to be executed by said programmable test device.

Claim 3

A method according to claim 1, wherein step (b) comprises causing one of said first and second versions of said operating system stored in said first and second memory systems for which step (a) has verified operational validity, which has the latest revision level, but which is in a downgraded status, to be rendered inactive, and causing another of said first and second versions of said operating system contained in said first and second memory systems to be executed by said programmable test device.

Claim 4

A method according to claim 1, wherein step (b) comprises causing one of said first and second versions of said operating system stored in said first and second memory systems for which step (a) has failed to verify operational validity to be rendered inactive, and causing another of said first and second versions of said operating system contained in said first and second memory systems to be executed by said programmable test device.

Claim 5

A method according to claim 1, further including the preliminary step (c), prior to step (a), of loading a preliminary section of an inactive one of said first and second memory systems with an instruction sequence that effectively prevents the operating system version contained in said inactive one of said first and second memory systems from being booted up, until steps (a) and (b) have verified that the operating system version contained in said inactive one of said first and second memory systems is operationally valid.

Claim 6

A method according to claim 4, further including the step (d), in response to steps (a) and (b) having verified that the operating system version contained in said inactive one of said first and second memory systems is operationally valid, modifying said instruction sequence that has been loaded in step (c) into said preliminary section of said inactive one of said first and second memory systems, so as to allow the operating system version contained in said inactive one of said first and second memory systems to be executed by said programmable test device.

Claim 7

A method according to claim 4, wherein step (c) comprises forcing a version of said operating system contained in the inactive one of said first and second memory systems, if execution is initiated, to perform a continuous no operation loop and, in response to said no operation loop being performed for a prescribed time out period, causing another version of said operating system contained in said first and second memory systems to be executed by said programmable test device.

Claim 8

A method according to claim 6, further including step (d), in response to steps (a) and (b) having verified that the operating system version contained in the inactive one of said first and second memory systems is operationally valid, modifying said instruction sequence that has been loaded in step (c) into said preliminary section of said inactive one of said first and second memory systems, so as to effectively remove said no operation loop and allow the operating system version contained in said inactive one of said first and second memory systems to be executed by said programmable test device.

Claim 9

A method according to claim 1, wherein each of said first and second memory systems is comprised of electronically reprogrammable flash memory.

Claim 10

For use with a communication system having one or more remote sites at which respective programmable test devices are located, a respective programmable test device employing an operating system for monitoring and testing network lines and subscriber termination equipment coupled thereto, said communication system further including at least one data terminal unit which has the capability of accessing said programmable test device and causing a modification of said operating system, said respective programmable test device containing first and second memory systems, which contain respective first and second versions of said operating system, a method of controlling which of said first and second versions of said operating system is executed by said programmable test device when said programmable test device is placed in operation, comprising the steps of: (a) establishing a communication path between a data terminal unit and said programmable test device; (b) via said data terminal unit, modifying the version of the operating system contained in an inactive one of said first and second memory systems of said programmable test device with an upgraded version of the operating system to be employed by said programmable test device as a replacement for the currently employed version of the operating system contained in an active one of said first and second memory systems; (c) causing said programmable test device to be reset, and default to the operating system contained in one of said first and second memory systems; (d) processing the contents of a prescribed portion of said first and second memory systems to verify operational validity; and (e) in response to step (d) having verified operational validity of the prescribed portion of one of said first and second memory systems containing said upgraded version of said operating system, causing said upgraded version of said operating system to be executed by said programmable test device.

Claim 11

For use with a communication system having one or more remote sites at which respective programmable test devices are located, a respective programmable test device employing an operating system for monitoring and testing network lines and subscriber termination equipment coupled thereto, said communication system further including at least one data terminal unit which has the capability of accessing said programmable test device and causing a modification of said operating system, said respective programmable test device containing first and second memory systems, which contain respective first and second versions of said operating system, a method of controlling which of said first and second versions of said operating system is executed by said programmable test device when said programmable test device is placed in operation, comprising the steps of: (a) establishing a communication path between a data terminal unit and said programmable test device; (b) via said data terminal unit, modifying the version of the operating system contained in an inactive one of said first and second memory systems of said programmable test device with an upgraded version of the operating system to be employed by said programmable test device as a replacement for the currently employed version of the operating system contained in an active one of said first and second memory systems; (c) causing said programmable test device to be reset, and default to the operating system contained in one of said first and second memory systems; (d) processing the contents of a prescribed portion of said first and second memory systems to verify operational validity; and (e) in response to step (d) having verified operational validity of the prescribed portion of one of said first and second memory systems containing said upgraded version of said operating system, causing said upgraded version of said operating system to be executed by said programmable test device.

Claim 12

A method according to claim 9, wherein step (e) further comprises communicating, from said programmable test device to said data terminal unit, information representative of the contents of said prescribed portion of said first and second memory systems so as to verify the functional capability of said upgraded version of said operating system for execution by said programmable test device.

Claim 13

A method according to claim 9, wherein step (e) comprises causing a version of the operating system in said first and second memory systems, for which step (d) has verified operational validity of said prescribed portion, which has the latest revision level, but which is in a downgraded status, to be rendered inactive, and causing another version of said operating system contained in said first and second memory systems to be executed by said programmable test device.

Claim 14

A method according to claim 9, wherein step (e) comprises causing a version of the operating system in said first and second memory systems, for which step (d) has failed to verify operational validity of said prescribed portion, to be rendered inactive and causing another version of said operating system contained in said first and second memory systems to be executed by said programmable test device.

Claim 15

A method according to claim 9, wherein step (c) further includes loading a preliminary section of an inactive one of said first and second memory systems with an instruction sequence that effectively prevents the operating system version contained in said inactive one of said first and second memory systems from being booted up, until steps (d) and (e) have verified that the operating system version contained in the inactive one of said first and second memory systems is operationally valid.

Claim 16

A method according to claim 13, further including the step (f), in response to steps (d) and (e) having verified that the operating system version contained in the inactive one of said first and second memory systems is operationally valid, modifying said instruction sequence that has been loaded in step (c) into said preliminary section of said inactive one of said first and second memory systems, so as to allow the operating system version contained in said inactive one of said first and second memory systems to be executed by said programmable test device.

Claim 17

A method according to claim 14, wherein step (c) further comprises forcing a version of the operating system contained in the inactive one of said first and second memory systems, if execution thereof is initiated, to perform a continuous no operation loop and, in response to said no operation loop being performed for a prescribed time out period, causing another version of said operating system contained in said first and second memory systems to be executed by said programmable test device.

Claim 18

A method according to claim 15, further including the step (f), in response to steps (d) and (e) having verified that the operating system version contained in an inactive one of said first and second memory systems is operationally valid, modifying said instruction sequence that has been loaded in step (c) into said preliminary section of said inactive one of said first and second memory systems, so as to effectively remove said no operation loop therein and allow the operating system version contained in said inactive one of said first and second memory systems to be executed by said programmable test device.

Claim 19

A method according to claim 9, wherein each of said first and second memory systems is comprised of electronically reprogrammable flash memory.

Claim 20

For use with a communication system having one or more remote sites at which respective programmable test devices are located, a respective programmable test device having an operating system for monitoring and testing network lines and subscriber termination equipment coupled thereto, said system further including at least one data terminal unit which has the capability of accessing said programmable test device and causing a modification of said operating system, a respective programmable test device containing memory in which first and second versions of said operating system are storable, a method of controlling which of said first and second versions of said operating system is executed by said programmable test device when said programmable test device is placed in operation comprising the steps of: (a) verifying operational validity of said memory; and (b) causing one of said first and second versions of said operating system, memory for which has been verified as being operationally valid in step (a), and which has the latest revision level, to be executed by said programmable test device.

Claim 21

For use with a communication system having one or more remote sites at which respective programmable test devices are located, a respective programmable test device having an operating system for monitoring and testing network lines and subscriber termination equipment coupled thereto, said system further including at least one data terminal unit which has the capability of accessing said programmable test device and causing a modification of said operating system, a respective programmable test device containing memory in which first and second versions of said operating system are storable, a method of controlling which of said first and second versions of said operating system is executed by said programmable test device when said programmable test device is placed in operation comprising the steps of: (a) verifying operational validity of said memory; and (b) causing one of said first and second versions of said operating system, memory for which has been verified as being operationally valid in step (a), and which has the latest revision level, to be executed by said programmable test device.

Claim 22

A method according to claim 18, wherein step (b) comprises causing a version of said operating system, memory for which has been verified as being operationally valid in step (a), which has the latest revision level, but which is in a downgraded status, to be rendered inactive and causing another version of said operating system to be executed by said programmable test device.

Claim 23

A method according to claim 18, wherein step (b) comprises causing a version of the operating system, memory for which has not be verified as being operationally valid in step (a), to be rendered inactive, and causing another version of said operating system to be executed by said programmable test device.

Claim 24

A method according to claim 18, further including the preliminary step (c), prior to step (a), of loading a preliminary section of an inactive memory space with an instruction sequence that effectively prevents the operating system version contained in said inactive memory space from being booted up, until steps (a) and (b) have verified that the operating system version contained in said inactive memory space is operationally valid.

Claim 25

A method according to claim 21, further including the step (d), in response to steps (a) and (b) having verified that the operating system version contained in said inactive memory space is operationally valid, modifying said instruction sequence that has been loaded in step (c) into said preliminary section of said inactive memory space, so as to allow the operating system version contained in said inactive memory space to be executed by said programmable test device.

Claim 26

A method according to claim 21, wherein step (c) comprises forcing the operating system in said inactive memory space, if execution thereof is initiated, to perform a continuous no operation loop and, in response to said no operation loop being performed for a prescribed time out period, causing the other version of said operating system to be executed by said programmable test device.

Claim 27

A method according to claim 23, further including step (d), in response to steps (a) and (b) having verified that the operating system version contained in said inactive memory space is operationally valid, modifying said instruction sequence that has been loaded in step (c) into said preliminary section of said inactive memory space, so as to effectively remove said no operation loop therein and allow the operating system version in said inactive memory space to be executed by said programmable test device.

Claim 28

A method according to claim 18, wherein said memory space includes electronically reprogrammable flash memory.

Claim 29

For use with a communication system having one or more remote sites at which respective programmable test devices are located, a programmable test device employing an operating system for monitoring and testing network lines and subscriber termination equipment coupled thereto, said communication system further including at least one data terminal unit which has the capability of accessing said programmable test device and causing a modification of said operating system, said programmable test device containing memory in which first and second versions of said operating system are storable, a method of controlling which of said first and second operating systems is executed by said programmable test device when said programmable test device is placed in operation comprising the steps of: (a) establishing a communication path between a data terminal unit and said programmable test device; (b) via said data terminal unit, modifying a version of said operating system contained in an inactive portion of said memory of said programmable test device with another version of said operating system to be employed by said programmable test device as a replacement for the currently employed version of the operating system contained in an active portion of said memory; (c) causing said programmable test device to be reset, and thereby default to one of said first and second versions of said operating system; (d) verifying operational validity of memory; and (e) in response to step (d) having verified operational validity of a portion of memory containing said another version of said operating system, causing said another version of said operating system to be executed by said programmable test device.

Claim 30

For use with a communication system having one or more remote sites at which respective programmable test devices are located, a programmable test device employing an operating system for monitoring and testing network lines and subscriber termination equipment coupled thereto, said communication system further including at least one data terminal unit which has the capability of accessing said programmable test device and causing a modification of said operating system, said programmable test device containing memory in which first and second versions of said operating system are storable, a method of controlling which of said first and second operating systems is executed by said programmable test device when said programmable test device is placed in operation comprising the steps of: (a) establishing a communication path between a data terminal unit and said programmable test device; (b) via said data terminal unit, modifying a version of said operating system contained in an inactive portion of said memory of said programmable test device with another version of said operating system to be employed by said programmable test device as a replacement for the currently employed version of the operating system contained in an active portion of said memory; (c) causing said programmable test device to be reset, and thereby default to one of said first and second versions of said operating system; (d) verifying operational validity of memory; and (e) in response to step (d) having verified operational validity of a portion of memory containing said another version of said operating system, causing said another version of said operating system to be executed by said programmable test device.

Claim 31

A method according to claim 26, wherein step (e) further comprises communicating, from said programmable test device to said data terminal unit, information representative of the contents of said memory so as to verify the functional capability of said another version of said operating system for execution by said programmable test device.

Claim 32

A method according to claim 26, wherein step (e) comprises causing a version of said operating system, for which step (d) has verified memory operational validity, which has the latest revision level, but which is in a downgraded status, to be rendered inactive and causing a further version of said operating system to be executed by said programmable test device.

Claim 33

A method according to claim 26, wherein step (e) comprises causing a version of said operating system, for which step (d) has failed to verify memory operational validity, to be rendered inactive and causing a further version of said operating system to be executed by said programmable test device.

Claim 34

A method according to claim 26, wherein step (c) further includes loading a preliminary section of an inactive portion of said memory with an instruction sequence that effectively prevents the operating system version contained in said inactive portion of memory from being booted up, until steps (d) and (e) have verified that the operating system version contained in said inactive portion of memory is operationally valid.

Claim 35

A method according to claim 30, further including the step (f), in response to steps (d) and (e) having verified that the operating system version contained in said inactive portion of memory is operationally valid, modifying said instruction sequence that has been loaded in step (c) into said preliminary section of said inactive portion of memory, so as to allow the operating system version contained in said inactive portion of memory to be executed by said programmable test device.

Claim 36

A method according to claim 31, wherein step (c) further comprises forcing an operating system version contained in said inactive portion of memory, if execution thereof is initiated, to perform a continuous no operation loop and, in response to said no operation loop being performed for a prescribed time out period, causing a further version of said operating system to be executed by said programmable test device.

Claim 37

A method according to claim 32, further including the step (f), in response to steps (d) and (e) having verified that the operating system version contained in said inactive portion of memory is operationally valid, modifying said instruction sequence that has been loaded in step (c) into said preliminary section of said inactive portion of memory, so as to effectively remove said no operation loop therein and allow the operating system version contained in said inactive portion of memory to be executed by said programmable test device.

Claim 38

A method according to claim 26, wherein said memory includes electronically reprogrammable flash memory.