1. An information recorder comprising:
a recording medium configured to have data written thereon;
a storage module configured to store data;
a controller; wherein the controller is configured to:
determine whether a position of a head for writing data on the recording medium is off a target track of the recording medium into which the head writes data, based on whether an amount of misalignment between a position of the head indicated by servo data associated with the target track and the target track is larger than a threshold value;
temporarily store in the storage module a data block that is written into a track adjacent to the target track;
read from the storage module, if it is determined that the head is positioned off the target track, the data block that was written in a sector that is among one or more sectors of the track adjacent to the target track that are overwritten as a result of the misalignment; and
write, if it is determined that the head is positioned off the target track, the data block into a sector that is different from the sector into which data are written at the time the head is positioned off the target track.
2. The information recorder of claim 1, wherein
the recording medium comprises a track group in which track width is smaller than a width of the head and in which, when data are written into the target track with the head, data are overwritten in a portion of a track adjacent to the target track at an inner side or an outer side of the track adjacent to the target track in a circumferential direction, and
the controller is further configured to write, if it is determined that the head is positioned off the target track, the data block read by the reader into a sector of a track included in the track group to which data is written at the time the head is positioned off the target track.
3. The information recorder of claim 1, wherein
the controller is configured to further read, if it is determined that the head is positioned off the target track, a second data block written in a sector of the target track at the time the head is positioned off the target track, from the storage module, and
to further write, if it is determined that the head is positioned off the target track, the second data block into a sector of the track adjacent to the target track.
4. The information recorder of claim 2, wherein the controller is further configured to write into the recording medium positional information indicating a position of the sector into which the data block is written.
5. The information recorder of claim 4, wherein the controller is configured to write the positional information into the recording medium after writing into the track group is finished.
6. The information recorder of claim 4, wherein, upon removing inter-track interference by using data read from a track adjacent to the target track on the recording medium while reading data from the target track, the controller is configured to read the data block written in the sector defined by the positional information instead of in the one or more sectors of the track adjacent to the target track that are overwritten as a result of the misalignment, to remove the inter-track interference.
7. The information recorder of claim 1, wherein the sector that is different from the sector into which data are written at the time the head is positioned off the target track, is disposed on the target track.
8. An information recording method for an information recorder comprising a recording medium configured to have data written thereon, a controller, and a storage module configured to temporarily store therein data written into a track adjacent to a track which is being written by a head, the information recording method comprising:
determining using the controller whether a position of a head for writing data on the recording medium is off a target track of the recording medium into which the head writes data, based on whether an amount of misalignment between a position of the head indicated by servo data associated with the target track and the target track is larger than a threshold value;
reading from the storage module, if it is determined that the head is positioned off the target track, a data block that is written in a sector that is among one or more sectors of the track adjacent to the target track that are overwritten as a result of the misalignment; and
writing, if it is determined that the head is positioned off the target track, the data block into a sector that is different from the sector into which data are written at the time the head is positioned off the target track.
9. The information recording method of claim 8, wherein
the recording medium comprises a track group in which track width is smaller than a width of the head and in which, when data are written into the target track with the head, data are overwritten in a portion of a track adjacent to the target track at an inner side or an outer side of the track adjacent to the target track in a circumferential direction is overwritten, and wherein
the writing further writes, if it is determined that the head is positioned off the target track, the data block read by the reading into a sector of a track included in the track group to which data is written at the time the head is positioned off the target track.
10. The information recording method of claim 8, wherein
the reading further reads, if it is determined that the head is positioned off the target track, a second data block written in a sector of the target track at the time the head is positioned off the target track, from the storage module, and
the writing further writes, if it is determined that the head is positioned off the target track, the second data block into a sector of the track adjacent to the target track.
11. The information recording method of claim 9, wherein the writing further writes into the recording medium positional information indicating a position of the sector into which the data block is written.
12. The information recording method of claim 11, wherein the writing writes the positional information into the recording medium after writing into the track group is finished.
13. The information recording method of claim 11, wherein, upon removing inter-track interference by using data read from a track adjacent to the target track on the recording medium while reading data from the target track, the reading further reads the data block written in the sector defined by the positional information instead of in the one or more sectors of the track adjacent to the target track that are overwritten as a result of the misalignment.
14. The information recording method of claim 8, wherein the sector that is different from the sector into which data are written at the time the head is positioned off the target track, is disposed on the target track.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
What is claimed is:
1. A method for checking consistency of data in a communications network configuration defined using managed network objects, comprising:
providing consistency check formulas for checking the consistency of one or more aspects of the communications network configuration, the consistency check formulas each defining a general operation performed on a managed network object;
establishing one or more consistency check rules by applying the consistency check formulas to one or more specific managed network objects; and
using the one or more consistency check rules to check the consistency of the one or more aspects of the communications network configuration.
2. The method in claim 1, wherein the one or more consistency check rules is applied to an attribute of a managed network object.
3. The method in claim 1, wherein each consistency check formula is used to establish plural associated consistency check rules.
4. The method in claim 1, wherein each consistency check formula includes a checkpoint that defines when a corresponding consistency check rule established using the consistency check formula should be executed.
5. The method in claim 4, wherein the checkpoint includes one or more of the following: population of a planned configuration area, modification of a planned configuration area, an operator-initiated consistency check, activation of a planned configuration area, and modification of an activated configuration area.
6. The method in claim 4, wherein when a checkpoint occurs, managed object instances for the consistency check rule to be executed are provided, whereafter the consistency check rule is executed.
7. The method in claim 1, wherein the consistency check formulas include one or more of the following:
Consistency check formula 1: Is X defined in the Y managed object instance of the Z configuration area
where X is an attribute of the Y managed object instance, and each Y managed object instance is delivered when the checkpoint occurs in the Z plannedactive configuration area;
Consistency check formula 2: Is X of the Y object instance unique within all X type attributes for all instances of Y type managed object classes of the Z area
where X is an attribute of the Y managed object instance, and each Y managed object instance is provided via the checkpoint Z;
Consistency check formula 3: Is X of the Y managed object instance of the Z area within the n to k range
where X is an attribute of the Y managed object instance, each Y managed object instance being delivered through the checkpoint Z, and where n is a number smaller than the number k-1; and
Consistency check formula 4: In the X configuration area, does Y have a relation to Z,
where Y and Z are managed object instances, each object instance being delivered through the checkpoint of the X configuration area.
8. The method in claim 1, further comprising: creating, deleting, or changing a consistency check rule using one of the consistency check formulas without performing a software upgrade.
9. The method in claim 1, further comprising:
changing a checkpoint when a consistency check rule is executed without performing a software upgrade.
10. The method in claim 1, wherein a user creates the consistency check rules by inputting certain data values for consistency check formulas by way of a user interface.
11. The method in claim 1, wherein a user creates the consistency check rules by inputting certain data values for variables by providing a data file and correlating the data file with the consistency check formulas.
12. A radio access network (RAN) management node for checking consistency of data in a RAN configuration defined using managed network objects, comprising:
a memory for storing consistency check formulas for checking the consistency of one or more aspects of the communications network configuration, the consistency check formulas each defining a general operation performed on a managed network object, and
consistency checking software executable to:
create one or more consistency check rules by applying the consistency check formulas to one or more specific managed network objects, and
use the one or more consistency check rules to check the consistency of the one or more aspects of the communications network configuration.
13. The RAN management node in claim 12, wherein the one or more consistency check rules is applied to an attribute of a managed network object.
14. The RAN management node in claim 12, wherein the consistency checking software is executable to establish plural associated consistency check rules using one of the consistency check formulas.
15. The RAN management node in claim 12, wherein each consistency check formula includes a checkpoint that defines when a corresponding consistency check rule created using the consistency check formula should be executed.
16. The RAN management node in claim 15, wherein the checkpoint includes one or more of the following: population of a planned configuration area, modification of a planned configuration area, an operator-initiated consistency check, activation of a planned configuration area, and modification of an activated configuration area.
17. The RAN management node in claim 15, wherein when a checkpoint occurs, the consistency checking software is executable to provide managed object instances for the consistency check rule to be executed, and thereafter, to execute the consistency check rule.
18. The RAN management node in claim 12, wherein the consistency check formulas include one or more of the following:
Consistency check formula 1: Is X defined in the Y managed object instance of the Z configuration area
where X is an attribute of the Y managed object instance, and each Y managed object instance is delivered when the checkpoint occurs in the Z plannedactive configuration area;
Consistency check formula 2: Is X of the Y object instance unique within all X type attributes for all instances of Y type managed object classes of the Z area
where X is an attribute of the Y managed object instance, and each Y managed object instance is provided via the checkpoint Z;
Consistency check formula 3: Is X of the Y managed object instance of the Z area within the n to k range
where X is an attribute of the Y managed object instance, each Y managed object instance being delivered through the checkpoint Z, and where n is a number smaller than the number k-1; and
Consistency check formula 4: In the X configuration area, does Y have a relation to Z,
where X and Z are managed object instances, each object instance being delivered through the checkpoint of the X configuration area.
19. The RAN management node in claim 12, wherein the consistency checking software is executable to create, delete, or change a consistency check rule using one of the consistency check formulas without performing a software upgrade.
20. The RAN management node in claim 12, wherein the consistency checking software is executable to change a checkpoint when a consistency check rule is executed without performing a software upgrade.
21. The RAN management node in claim 12, wherein a user creates the consistency check rules by inputting certain data values for consistency check formulas by way of a user interface.
22. The RAN management node in claim 12, wherein a user creates the consistency check rules by inputting certain data values for variables by providing a data file and correlating the data file with the consistency check formulas.