Author: claimsbot

1. A client-server type computer system for graphical applications, for displaying data in the form of software units called \u201cwidgets\u201d on display screens called \u201cdisplay units\u201d, each widget being defined by \u201cattributes\u201d, a client being called \u201cuser application\u201d, said system being intended to control the operation of a machine, the machine comprising at least one human-machine interface allowing interaction with the widgets, said system managing critical data or functions, including data or functions that may lead to a serious malfunction of said machine, the widgets being combined in a structure called \u201cmodel\u201d comprising the properties of each widget and their hierarchical organization, said model being created from a client-application definition file, the widgets handling the display of the critical functions being called \u201csecured widgets\u201d, the system further comprising:
a securing engine including provisions for controlling the display of the secured widgets, a first control provision comprising of the first computation of a \u201csignature\u201d of the model of the secured widgets, of the second computation of a \u201csignature\u201d of the secured widgets’ definition file and of the comparison of the two signatures, a signature being a mathematical code associated with the attributes of the secured widgets; a second control provision comprising of algorithms for checking the conformity of the stack of graphical instructions generated by the server with the model of the secured widgets, said algorithm being of \u201cfeedback\u201d type.
2. The client-server type computer system according to claim 1, wherein the securing engine includes at least one provision for controlling the sending of commands and inputs from the user performed by means of the human-machine interface on the secured widgets, said provision being that the secured widgets are of \u201cUA-validation\u201d type, wherein, when a command to change the state of said secured widget is received from the human-machine interface, said secured widget waits for a confirmation message from the client before changing state.
3. The client-server type computer system according to claim 1, wherein the securing engine includes at least first provisions for controlling commands and the input and display of data performed by means of the human-machine interface on the secured widgets, said first provisions being that the secured widgets include either guard mechanisms, or dialogue boxes, a guard mechanism being a graphical object protecting the secured widget that must necessarily be unlocked before accessing said secured widget.
4. The client-server type computer system according to claim 3, wherein the securing engine includes at least second provisions for controlling the input and display of data performed by means of the human-machine interface on the secured widgets, said second provisions ensuring the consistency of the locking of the guard or of the dialogue box with the state of the secured widget.
5. The client-server type computer system according to claim 3, wherein the securing engine includes at least third provisions for controlling commands and the input and display of data performed by means of the human-machine interface on the secured widgets, said third provisions consisting of the association of signatures of the critical widgets with their guards or confirmation buttons and the verification by the client of the pairs of signatures via a mapping table.
6. The client-server type computer system according to claim 3, wherein the securing engine includes at least fourth provisions for controlling the input and display of data performed by means of the human-machine interface on the secured widgets, said fourth provisions ensuring the integrity of the value input by the user by the transmission to the client of the value and of its signature for verification of their consistency by the client.
7. The client-server type computer system according to claim 1, wherein the machine is an aircraft, the computer system is the onboard avionics of said aircraft and the display screens are cockpit display systems and the computer system works according to the ARINC 661 aeronautical standard.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A grate block for an incinerator, the incinerator including a plurality of rows of fixed grate blocks and a plurality of rows of movable grate blocks, the rows of fixed and movable grate blocks being arranged in a stepped configuration creating upper and lower rows relative to each other, the grate block comprising:
an upper wall having a top surface;
a front wall having a front surface extending from the top surface;
a pair of side walls each having an outer surface for engaging adjacent grate blocks and an inner surface, the side walls parallel to each other and spaced from each other, each outer side surface extending from the top surface and the front surface;
at least one of the side walls having a recess adjacent the top surface of the upper wall and also adjacent to the front surface of the front wall, the recess constructed and arranged to direct a stream of air upward, in a direction away from an adjacent, lower row of grate blocks; and
at least one of the side walls having an opening between the inner surface and the outer surface for passage of a stream of air.
2. The grate block of claim 1 wherein the recess has an angle such that the stream of air exits from the grate block and forms an angle between 90 above the plane of the top surface and 14 surface below the plane of the top surface of the grate block.
3. The grate block of claim 1 wherein the recess has an angle such that the stream of air exits from the grate block and projects at an angle above 20 below the surface of the plane of the top surface of the grate block.
4. The grate block of claim 3 wherein the recess has an angle such that the stream of air exits from the grate block and forms an angle between 120 above the plane of the top surface and 14 below the surface of the plane of the top surface of the grate block.
5. The grate block of claim 1 wherein the recess has at least two levels, a shallow recess level and a deeper recess level, wherein the opening is on the deeper recess level, and the shallow recess level is interposed between the upper surface and the openings.
6. The grate block of claim 5 further comprising an angle corner edge surface interposed between the top surface, the front surface, and the pair of side surfaces.
7. The grate block of claim 6 wherein the recess has an angle such that the stream of air exits from the grate block and forms an acute angle between 90 above the plane of the top surface and 14 below the plane of the top surface of the grate block.
8. The grate block of claim 1 wherein the recess includes at least two distinct recesses on the at least one of the side surfaces, and an opening extending through each of the recesses.
9. A grate block for an incinerator, the grate block comprising:
a top wall having a top surface;
a front wall having a front surface;
a pair of side walls, each side wall having an outer surface for engaging the adjacent grate block and extending from the top surface and the front surface;
an angled corner edge wall having an outer surface interposed between the top surface, the front surface, and the pair of side walls: and
at least one groove formed in a the angled corner edge wall, and an opening in the groove for the passage of a stream of air.
10. The grate block of claim 9 wherein the groove has an angle such that the stream of the air exist the grate block and forms an angle between 90 above the plane of the top surface and 14 below the surface of the plane of the top surface of the grate block.
11. The grate block of claim 9 wherein the groove has an angle such that the stream of air exits from the grate block and forms an angle between 120 above the plane of the top surface and 14 below the surface of the plane of the top surface of the grate block.
12. The grate block of claim 9 wherein the groove has at least two levels, a shallow groove level and a deeper groove level, wherein the opening is on the deeper groove level, and the shallow groove level is interposed between the upper surface and the opening.
13. (Canceled)
14. The grate block of claim 12 further comprising a projecting arm extending from the top wall, the projecting arm defining a hook, the projecting arm narrowed from the width of the front wall.
15. An incinerator grate system comprising:
a plurality of rows of fixed grate blocks;
a plurality of rows of movable grate blocks, each row of movable grate blocks interposed between a pair of movable grate blocks;
a reciprocal mechanism connected to each of the rows of moveable grate blocks for moving the rows relative to the rows of the fixed grate blocks;
each of the rows having a plurality of grate blocks;
the grate blocks defining a cavity under the rows;
each of the grate blocks having an upper wall, a front wall, a pair of side walls, each side wall extending from the top wall and the front wall; and a foot carried by the front wall and engaging an upper wall of a grate block; the walls defining a cavity under the upper wall;
each of the side walls of the grate blocks engaging the side wall of the adjacent grate block, each side wall having a recess disposed in an interface where in proximity to the front wall and upper wall meet such that the recess extends from the top wall to the front wall;
the recess defining a gap between the side walls of the adjacent grate blocks; and
an opening through the recess of the sidewall for the flow of air from the cavity within the grate block.
16. The incinerator grate system of claim 15 wherein the recess on the side wall of the grate block has at least two levels, a shallow recess level and a deeper recess level, wherein the opening is on the deeper recess level, and the shallow recess level is interposed between the upper wall and the opening.
17. The incinerator grate system of claim 16 wherein the grate block further comprises an angle corner edge wall interposed between the top wall, the front wall and the pair of side walls.
18. The incinerator grate system of claim 17 wherein the recess has an angle such that the stream of air exits from the grate block and forms an angle between 90 above and 14 below from the top wall of the grate block.
19. The incinerator grate system of claim 15 wherein each side wall has at least three recesses, each recess having an opening through the side wall for flow of air from the cavity within the grate block.
20. The incinerator grate system of claim 19 wherein the grate block further comprises an angle corner edge wall interposed between the top wall, the front wall and the pair of side walls.
21. The incinerator grate system of claim 20 wherein at least one recess on the side wall extends to the front wall, at least another recess on the side wall extends to the top wall, and at least another recess on the side wall extends to the angle corner edge wall.
22. A method of incinerating refuse comprising the steps of:
providing a grate having a plurality of fixed rows and a plurality of moving rows of grate blocks;
moving the moving rows of grate blocks in a back and forth motion to move the refuse along the grate;
creating a void in the refuse by movement of the moving row;
forcing air through an opening in the grate block to the refuse and away from the void; and
directing the air through an opening in the sidewall of the grate block and redirecting the air prior to passing the sidewall.
23. (Canceled)
24. The grate block of claim 1, wherein the recess is disposed in at least on of the sidewalls and extends from the top surface of the upper wall to the front surface of the front wall.

1. A handover providing method of a source node base (NodeB) and a target NodeB, the method comprising:
receiving, by the source NodeB from a user equipment, a measurement result with respect to component carriers of a neighboring NodeB or the source NodeB;
determining, by the source NodeB, the target NodeB;
transmitting, by the source NodeB, a handover request message to the target NodeB;
transferring, by the target NodeB, a handover request acknowledgement (ACK) message to the source NodeB; and
transmitting, by the source NodeB to the user equipment, a handover execution command including a handover parameter.
2. The method of claim 1, further comprising:
determining, by the target NodeB, component carrier configuration information,
wherein the target NodeB transfers the component carrier configuration information to the source NodeB using the handover request ACK message, and the handover parameter comprises the component carrier configuration information.
3. The method of claim 2, wherein the component carrier configuration information corresponds to one of single component carrier information, primary component carrier configuration information, and the primary component carrier configuration information and secondary component carrier configuration information.
4. The method of claim 1, wherein the handover request message comprises a measurement result with respect to component carriers of the target NodeB.
5. The method of claim 1, further comprising:
determining, by the target NodeB, an uplink access component carrier,
wherein the target NodeB transfers uplink access component carrier information to the source NodeB using the handover request ACK message, and the handover parameter comprises the uplink access component carrier information.
6. The method of claim 5, further comprising:
determining, by the target NodeB, component carrier configuration information of a primary component carrier and a secondary component carrier; and
transmitting a component carrier configuration and activation control message to the user equipment.
7. The method of claim 5, wherein the component carrier configuration information expresses the primary component carrier and the secondary component carrier together with a downlink component carrier and an uplink component carrier.
8. A handover method of a user equipment, comprising:
transmitting, to a source node base (NodeB), a measurement result with respect to component carriers of a neighboring NodeB or the source NodeB;
receiving, from the source NodeB, a handover execution command comprising a handover parameter;
attempting an access to a target NodeB and an uplink synchronization establishment;
receiving, from the target NodeB, a response with respect to a resource assignment for an uplink access attempt and a synchronization establishment complete; and
transmitting a handover complete report message to the target NodeB.
9. The method of claim 8, wherein the handover parameter comprises component carrier configuration information.
10. The method of claim 9, further comprising:
attempting the access to the target NodeB and the uplink synchronization establishment;
receiving, from the target NodeB, the response with respect to the resource assignment for the uplink access attempt and the synchronization establishment complete; and
transmitting the handover complete report message to the target NodeB.
11. The method of claim 8, wherein the handover parameter comprises uplink access component carrier information.
12. The method of claim 11, further comprising:
attempting the access to the target NodeB and the uplink synchronization establishment using a component carrier based on the uplink access component carrier information;
completing a response to the access and the uplink synchronization establishment;
reporting to the target NodeB about the measurement result with respect to the component carriers of the target NodeB using an uplink radio resource allowed by the target NodeB; and
receiving a component carrier configuration and activation control message from the target NodeB.
13. A method of changing a component, the method comprising:
setting a user equipment to measure a mobility management;
receiving a measurement result obtained by measuring a radio channel quality with respect to component carriers;
determining a handover procedure for changing of a primary component carrier based on the measurement result and a load status of each of the component carriers, and performing a relevant control procedure;
transmitting, to a user equipment, information associated with a component carrier to be configured as a new primary component carrier, and commanding a handover execution for changing of the primary component carrier; and
exchanging control information with the user equipment using the new primary component carrier.
14. The method of claim 13, further comprising:
transmitting, to the user equipment, new primary component carrier information and random access resource assignment information;
receiving a random access preamble from the user equipment using the new primary component carrier; and
transmitting random access response information to the user equipment using the new primary component carrier.
15. The method of claim 13, wherein the handover execution command comprises timing advance reference primary component carrier configuration information and pathloss reference primary component carrier configuration information for uplink transmit power setup.
16. The method of claim 13, further comprising:
transmitting a component carrier configuration message to the user equipment.
17. The method of claim 16, wherein the component carrier configuration message comprises at least one of a primary component carrier index, control information for management of the primary component carrier, at least one secondary component carrier index, and control information for management of a secondary component carrier.
18. A method of changing a component, the method comprising:
measuring a mobility management based on a configuration from a serving node base (NodeB);
transmitting, to the serving NodeB, a measurement result obtained by measuring a radio channel quality with respect to component carriers;
receiving, from the serving NodeB, information associated with a component carrier to be configured as a new primary component carrier; and
exchanging control information with the serving NodeB using the new primary component carrier.
19. The method of claim 18, further comprising:
receiving, from the serving NodeB, new primary component carrier information and random access resource assignment information;
transmitting a random access preamble to the serving NodeB using the new primary component carrier; and
receiving random access response information from the serving NodeB using the new primary component carrier.
20. The method of claim 19, further comprising:
transmitting, to the serving NodeB, a control message indicating a primary component carrier change complete and a secondary component carrier configuration complete.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A smart card operating system including a non-contact communication module, which is characterized in that, said smart card operating system also includes: a communication state control module which connects with said non-contact communication module to detect whether said smart card operating system enters andor leaves the non-contact field or not, and set the communication state of said non-contact communication module based on the detection result;
said non-contact communication module includes a second storage unit to store the sign of the non-contact communication state to identify the communication state of said non-contact communication module.
2. A system as claimed in claim 1, which is characterized in that: said communication state control module includes:
a first detecting sub-module, which detects whether said smart card operating system enters andor leaves the non-contact field or not, and creates interrupt when said smart card operating system enters andor leaves the non-contact field;
a first setting sub-module, which sets the communication state of said non-contact communication module as IDLE based on said interrupt.
3. A system as claimed in claim 2, which is characterized in that: said first detecting sub-module includes: a first storage unit and a first detecting unit,
said first detecting unit detects the non-contact power andor clock, determines, according to the non-contact power andor clock sign stored in said first storage unit, whether the non-contact power andor clock is switching from inexistence to existence or from existence to inexistence, to find out whether the smart card operating system is passing in or out of the non-contact field, and sets respectively said non-contact power andor clock sign when said smart card operating system enters and leaves the non-contact field, and creates interrupt when said smart card operating system enters andor leaves the non-contact field.
4. A system as claimed in claim 1, which is characterized in that: said communication state control module includes:
a second detecting sub-module to periodically detect whether said smart card operating system leaves the non-contact field or not, and to output the detection result;
a second setting sub-module to set the communication state of said non-contact communication module as IDLE based on said detection result.
5. A system as claimed in claim 4, which is characterized in that: said second detecting sub-module includes:
period control unit to output the triggering signal according to the set cycle;
a second detecting unit to periodically detect the non-contact power andor clock according to said triggering signal, and output the detection result when said smart card operating system leaves the non-contact field.
6. A system as claimed in claim 5, which is characterized in that: said system also includes a dormancy control module which connects with said communication state control module; and said non-contact communication module also includes awaking sub-module which connects with said dormancy control module;
after said communication state control module sets the communication state of said non-contact communication module, said dormancy control module will control said communication state into the dormancy state;
said awaking sub-module finds out that said system enters in the non-contact field based on the inquiry from the non-contact terminal equipment to said system, and informs said dormancy control module awaking said communication state control module.
7. A system as claimed in claim 4, which is characterized in that: said system also includes a dormancy control module which connects with said communication state control module; and said non-contact communication module also includes awaking sub-module which connects with said dormancy control module;
after said communication state control module sets the communication state of said non-contact communication module, said dormancy control module will control said communication state into the dormancy state;
said awaking sub-module finds out that said system enters in the non-contact field based on the inquiry from the non-contact terminal equipment to said system, and informs said dormancy control module awaking said communication state control module.
8. A system as claimed in claim 7, which is characterized in that: said system also includes a second initial module to initialize said communication state control module when the system is powered on, and set the state of said communication state control module as dormancy.
9. A system as claimed in claim 1, which is characterized in that: said system also includes a first initial module which respectively connects with said non-contact communication module and said communication state control module, and
when setting the communication state of said non-contact communication module, said communication state control module also informs said first initial module to initialize said non-contact communication module.
10. A smart card operating method, which is characterized in that: the method includes the following steps:
detecting whether said smart card operating system enters andor leaves the non-contact field or not;
setting the non-contact communication state of said smart card operating system based on the detection result; and
storing the sign of the non-contact communication state to identify the communication state of said non-contact communication module.
11. A method as claimed in claim 10, which is characterized in that: said setting the non-contact communication state of said smart card operating system based on the detection result includes:
setting the non-contact communication state of said smart card operating system as IDLE based on the detection result that said smart card operating system enters the non-contact field; andor
setting the non-contact communication state of said smart card operating system as IDLE based on the detection result that said smart card operating system leaves the non-contact field.
12. A method as claimed in claim 11, which is characterized in that:
determining whether said system enters the non-contact field or not according to whether the non-contact power andor clock switches from inexistence to existence or not; andor
determining whether said system leaves the non-contact field or not according to whether the non-contact power andor clock change from existence to inexistence.
13. A method as claimed in claim 11, which is characterized in that: detecting the non-contact power andor clock according to a predetermined cycle, and determining whether said system left the non-contact field or not based on whether there exists the non-contact power andor clock.
14. A method as claimed in claim 10, which is characterized in that:
determining whether said system enters the non-contact field or not according to whether the non-contact power andor clock switches from inexistence to existence or not; andor
determining whether said system leaves the non-contact field or not according to whether the non-contact power andor clock change from existence to inexistence.
15. A method as claimed in claim 10, which is characterized in that: detecting the non-contact power andor clock according to a predetermined cycle, and determining whether said system left the non-contact field or not based on whether there exists the non-contact power andor clock.
16. A method as claimed in claim 15, which is characterized in that: the smart card operating system stops detecting the non-contact power andor clock after its communication state is set, and restarts periodically detect the non-contact power or clock after it finds out that said system enters in the non-contact field based on the inquiry from the non-contact terminal equipment to said system.