All The Claims

1. A medical treatment endoscope comprising:
a sheath having a flexibility;
arm members configured to be capable of advancing from and retracting into the sheath, and having a bending part that projects out from a front end of the sheath and performs bending actions;
a wire member configured to bend the bending part;
an openclose mechanism which directs the arm members from a direction along a central axis of the sheath to a rotational direction deviated from the central axis of the sheath around a base axis of the arm members, and from the rotational direction deviated from the central axis of the sheath around the base axis of the arm members to a direction along the central axis of the sheath;
a viewing device and an illuminating member that are disposed to a front end side of the sheath;
the openclose mechanism includes:
an openclose operating member, configured to open the arm members by moving in a proximal end direction of the sheath, the openclose operating member at least partially protrudes from an opening of a distal end of the sheath and inserted in a freely advancing and retracting manner into the sheath;
linking parts, connected to the openclose operating member at a first end thereof and connected to a proximal position of the arm members at a second end thereof, and configured to be capable of turning according to the openclose operating member which advances and retracts for converting an advanceretract action of the arm members into an openclose action around the base axis of the arm members of the openclose mechanism; and
supporting members connected to the linking parts at a first end of the supporting members to be rotatable and connected to the sheath to freely advance and retract so as to support the arm members;

wherein the arm members comprise two arm members that are arranged in a radial direction of the sheath, and at least one part of the openclose operating member is disposed at a position in an area between central axes of the two arm members in a cross-section along the central axis of the sheath.
2. The medical treatment endoscope according to claim 1, wherein front ends of the two arm members are capable of relative displacement with respect to the viewing device and the illuminating member by means of at least one of a bending action of the bending part and a directional transition of the two arm members by the openclose mechanism.
3. The medical treatment endoscope according to claim 2, further comprising;
a frame; and
a bending operating part to which a procedure operating part for a procedure device for performing a procedure in an organ is attachable, for bending the bending part.
4. The medical treatment endoscope according to claim 1, wherein in the cross-section along the central axis of the sheath, the openclose operating member is disposed closer to the central axis of the sheath than a position at which the two arm members are disposed.
5. The medical treatment endoscope according to claim 1, wherein a connecting part for the linking part and the two arm members are provided so as to be positioned between a connecting part for the openclose operating member and the linking part, and the front end of the sheath, while in a state that the linking part is caused the two arm members to approach the central axis of the sheath, as a result of movement of the front end of the openclose operating member in the first direction to approach the central axis of the sheath.
6. The medical treatment endoscope according to claim 5, wherein the openclose operating member is disposed to an area opposite the viewing device, between the two arm members.
7. The medical treatment endoscope according to claim 1, wherein the viewing device is disposed to the distal end of the sheath, and the openclose mechanism opens and closes the two arm members at a more distal position than a position at which the viewing device is disposed.
8. The medical treatment endoscope according to claim 1, wherein a distal end of the openclose operating member which is connected to a front end of the linking parts is disposed at a more distal position of the arm members than that of the second end of the linking parts which is connected to the supporting members such that a pantograph framework is formed by the linking parts and the supporting members.

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 medical probe, comprising:
a flexible insertion tube, having a distal end for insertion into a body cavity of a patient;
a distal tip, which is disposed at the distal end of the flexible insertion tube and is configured to be brought into contact with tissue in the body cavity; and
a coupling member, which couples the distal tip to the distal end of the flexible insertion tube and which comprises a tubular piece of an elastic material having a plurality of intertwined helical cuts therethrough along a portion of a length of the piece.
2. The probe according to claim 1, wherein at least one of the helical cuts comprises an enlarged termination.
3. The probe according to claim 2, wherein the enlarged termination comprises a partial ellipse.
4. The probe according to claim 1, wherein the plurality of intertwined helical cuts comprises n cuts, where n is an integer greater than 1, and wherein the cuts are configured so that the tubular piece has n-fold rotational symmetry about an axis of the piece.
5. The probe according to claim 1, wherein at least one of the helical cuts subtends an angle between 360\xb0 and 720\xb0 about an axis of the tubular piece.
6. The probe according to claim 1, wherein the coupling member is configured to bend in response to pressure exerted on the distal tip when the distal tip engages the tissue, and wherein at least one of the helical cuts has a width chosen so as to provide a predetermined angular limit on initial bending of the coupling member.
7. The probe according to claim 1, wherein the coupling member comprises a tubular part connected by a fixed connection to the tubular piece.
8. The probe according to claim 7, wherein the tubular piece comprises a stem, and wherein the fixed connection comprises the stem welded to the tubular part.
9. The probe according to claim 7, wherein the tubular part and the tubular piece are arranged so as to form a common circumference thereto, and wherein the fixed connection comprises welds on the common circumference absent regions thereon proximal to respective terminations of the helical cuts.
10. The probe according to claim 7, and comprising a position sensor within the tubular piece.
11. The probe according to claim 10, wherein the position sensor is configured to sense a position of the distal tip relative to the distal end of the insertion tube, the position changing in response to deformation of the coupling member.
12. The probe according to claim 10, wherein the position sensor is configured to generate a signal in response to a magnetic field, and wherein the signal is indicative of a position of the distal tip.
13. The probe according to claim 12, and comprising a magnetic field generator within the tubular part for generating the magnetic field.
14. The probe according to claim 1, wherein the insertion tube, the distal tip and the coupling member are configured for insertion through a blood vessel into a heart of a patient.
15. A method for performing a medical procedure, comprising:
inserting into a body cavity of a patient a probe, which comprises a flexible insertion tube and a distal tip, which is disposed at a distal end of the flexible insertion tube, and a coupling member, which couples the distal tip to the distal end of the flexible insertion tube and comprises a tubular piece of an elastic material having a plurality of intertwined helical cuts therethrough along a portion of a length of the piece; and
bringing the distal tip into contact with tissue in the body cavity.
16. The method according to claim 15, wherein inserting the probe comprises passing the probe through a blood vessel into a heart of the patient.
17. The method according to claim 15, and comprising ablating the tissue with which the distal tip is in contact.
18. A method for producing a medical probe, comprising:
providing a flexible insertion tube, having a distal end for insertion into a body cavity of a patient, and a distal tip, which is disposed at the distal end of the flexible insertion tube and which is configured to be brought into contact with tissue in the body cavity; and
coupling the distal tip to the distal end of the flexible insertion tube using a coupling member, which comprises a tubular piece of an elastic material having a plurality of intertwined helical cuts therethrough along a portion of a length of the piece.
19. The method according to claim 18, wherein at least one of the helical cuts comprises an enlarged termination.
20. The method according to claim 19, wherein the enlarged termination comprises a partial ellipse.
21. The method according to claim 18, wherein the plurality of helical cuts comprises n cuts, where n is an integer greater than 1, and comprising configuring the n cuts so that the tubular piece has n-fold rotational symmetry about an axis of the piece.
22. The method according to claim 18, wherein at least one of the helical cuts subtends an angle between 360\xb0 and 720\xb0 about an axis of the tubular piece.
23. The method according to claim 18, comprising configuring the coupling member to bend in response to pressure exerted on the distal tip when the distal tip engages the tissue, and configuring at least one of the helical cuts to have a width chosen so as to provide a predetermined angular limit on initial bending of the coupling member.
24. The method according to claim 18, wherein the coupling member comprises a tubular part connected by a fixed connection to the tubular piece.

1. A computer-implemented method for managing multiple services, comprising:
generating a first service operation module for a first service provided by a first network device, wherein the first service operation module (a) supports a set of functions that are invokable by a management module and (b) acts as an interface between the management module and the first service provided by the first network device;
in response to the management module invoking, with respect to the first service operation module, a first function of the set of functions, the first service operation module for the first service providing, to the management module that is separate from the first service operation module, first operation data that specifies one or more first operations that the first service is configured to perform;
the management module receiving, from a client, a request for a first operation that one of the multiple services is configured to perform;
in response to the management module receiving the request from the client, the management module determining, based upon the first operation data, whether the first service is configured to perform the first operation specified in the request;
in response to the management module determining that the first service is configured to perform the first operation specified in the request, the management module invoking a second function of the set of functions to provide, to the first service operation module, the request for the first operation;
in response to the first service operation module receiving the request, the first service operation module sending the first operation to the first service;
discovering a second service that is different than the first service;
after discovering the second service:
generating a second service operation module for the second service, wherein the second service operation module is different than the first service operation module and is separate from the management module,
wherein the second service operation module (c) supports the set of functions that are invokable by the management module and (d) acts as an interface between the management module and the second service, and
registering the second service module with the management module;

in response to the management module invoking, with respect to the second service operation module, the first function of the set of functions, the second service operation module for the second service providing, to the management module, second operation data that specifies one or more second operations that the second service is configured to perform;
the management module receiving, from a second client, a request for a second operation that one of the multiple services is configured to perform;
in response to the management module receiving the request for the second operation, the management module determining, based upon the second operation data, whether the second service is configured to perform the second operation;
in response to the management module determining that the second service is configured to perform the second operation, the management module invoking the second function of the set of functions to provide, to the second service operation module, the request for the second operation; and
in response to the second service operation module receiving the request for the second operation, the second service operation module sending the second operation to the second service.
2. The method of claim 1, wherein:
the second service is provided by a second network device that is different than the first network device.
3. The method of claim 1, further comprising:
discovering a new service provided by the first network device;
updating the first service operation module for the first network device to allow the client to request the new service via the first service operation module; and
providing, to the management module, from the first service operation module for the network device, new data that specifies one or more operations that the new service is configured to perform.
4. The method of claim 1, further comprising:
receiving an event notification;
based on a rule associated with the event notification, the management module sending, to the first service operation module for the first network device, an operation that corresponds to the rule and that is supported by a service hosted on the first network device; and
in response to receiving the operation from the management module, the first service operation module sending the operation to the first network device, wherein the first network device performs the operation.
5. A computer-implemented method for correlating network events and operations provided by network devices in a network, the method comprising:
generating a first service operation module for a first service provided by a first network device, wherein the first service operation module (a) supports a set of functions that are invokable by a management module and (b) acts as an interface between the management module and the first network device;
in response to the management module invoking, with respect to the first service operation module, a first function of the set of functions, the first service operation module for the first service providing, to the management module that is separate from the service operation module, operation data that specifies a set of one or more operations that the first service is configured to perform;
receiving event data that indicates a set of one or more network events that a second network device is configured to generate;
an event handler module receiving, from a user, a rule specifying an operation from the set of operations to be performed upon an occurrence of a network event from the set of network events;
in response to the event handler module receiving a notification of an occurrence of the network event from the second network device, determining whether to trigger the rule;
in response to determining to trigger the rule, the management module sending the operation to the first service operation module;
in response to receiving the operation from the management module, the first service operation module sending, to the first network device, the operation to be performed by the first service, wherein the first network device is either the same device as the second network device or a different device than the second network device;
generating a second service operation module for a second service provided by the second network device, wherein the second service operation module (a) supports the set of functions that are invokable by the management module and (b) acts as a second interface between the management module and the second network device; and
the second service operation module for the second network device providing, to the management module, second operation data that specifies a set of one or more second operations that the second service is configured to perform.
6. A volatile or non-volatile computer-readable storage medium storing instructions for managing a network device, which instructions, when processed by one or more processors, cause:
generating a first service operation module for a first service provided by a first network device, wherein the first service operation module (a) supports a set of functions that are invokable by a management module and (b) acts as an interface between the management module and the first service provided by the first network device;
in response to the management module invoking, with respect to the first service operation module, a first function of the set of functions, the first service operation module for the first service providing, to the management module that is separate from the first service operation module, first operation data that specifies one or more first operations that the first service is configured to perform;
the management module receiving, from a client, a request for a first operation that one of the multiple services is configured to perform;
in response to the management module receiving the request from the client, the management module determining, based upon the first operation data, whether the first service is configured to perform the first operation specified in the request;
in response to the management module determining that the first service is configured to perform the first operation specified in the request, the management module invoking a second function of the set of functions to provide, to the first service operation module, the request for the first operation;
in response to the first service operation module receiving the request, the first service operation module sending the first operation to the first service;
discovering a second service that is different than the first service;
after discovering the second service:
generating a second service operation module for the second service, wherein the second service operation module is different than the first service operation module and is separate from the management module,
wherein the second service operation module (c) supports the set of functions that are invokable by the management module and (d) acts as an interface between the management module and the second service, and
registering the second service module with the management module;

in response to the management module invoking, with respect to the second service operation module, the first function of the set of functions, the second service operation module for the second service providing, to the management module, second operation data that specifies one or more second operations that the second service is configured to perform;
the management module receiving, from a second client, a request for a second operation that one of the multiple services is configured to perform;
in response to the management module receiving the request for the second operation, the management module determining, based upon the second operation data, whether the second service is configured to perform the second operation;
in response to the management module determining that the second service is configured to perform the second operation, the management module invoking the second function of the set of functions to provide, to the second service operation module, the request for the second operation; and
in response to the second service operation module receiving the request for the second operation, the second service operation module sending the second operation to the second service.
7. The volatile or non-volatile computer-readable medium of claim 6, wherein:
the second service is provided by a second network device that is different than the first network device.
8. The volatile or non-volatile computer-readable storage medium of claim 6, wherein the instructions, when processed by the one or more processors, further cause:
discovering a new service provided by the first network device;
updating the first service operation module for the first network device to allow the client to request the new service via the first service operation module; and
providing, to the management module, from the first service operation module for the network device, new data that specifies one or more operations associated with the new service.
9. The volatile or non-volatile computer-readable storage medium of claim 6, wherein the instructions, when processed by the one or more processors, further cause:
receiving an event notification;
based on a rule associated with the event notification, the management module sending, to the first service operation module for the first network device, an operation that corresponds to the rule and that is supported by a service hosted on the first network device; and
in response to receiving the operation from the management module, the first service operation module sending the operation to the first network device, wherein the first network device performs the operation.
10. A volatile or non-volatile computer-readable storage medium storing instructions for correlating network events and operations provided by network devices in a network, which instructions, when processed by one or more processors, cause:
generating a first service operation module for a first service provided by a first network device, wherein the first service operation module (a) supports a set of functions that are invokable by a management module and (b) acts as an interface between the management module and the first network device;
in response to the management module invoking, with respect to the first service operation module, a first function of the set of functions, the first service operation module for the first service providing, to the management module that is separate from the service operation module, operation data that specifies a set of one or more operations that the first service is configured to perform;
receiving event data that indicates a set of one or more network events that a second network device is configured to generate;
an event handler module receiving, from a user, a rule specifying an operation from the set of operations to be performed upon an occurrence of a network event from the set of network events;
in response to the event handler module receiving a notification of an occurrence of the network event from the second network device, determining whether to trigger the rule;
in response to determining to trigger the rule, the management module sending the operation to the first service operation module;
in response to receiving the operation from the management module, the first service operation module sending, to the first network device, the operation to be performed by the first service, wherein the first network device is either the same device as the second network device or a different device than the second network device;
generating a second service operation module for a second service provided by the second network device, wherein the second service operation module (a) supports the set of functions that are invokable by the management module and (b) acts as a second interface between the management module and the second network device; and
the second service operation module for the second network device providing, to the management module, second operation data that specifies a set of one or more second operations that the second service is configured to perform.
11. The method of claim 5, wherein the first network device is a different device than the second network device.
12. The method of claim 5, wherein:
the first network device is the same device as the second network device; and
the one or more operations that the first service is configured to perform are different than the one or more operations that the second service is configured to perform.
13. The volatile or non-volatile computer-readable storage medium of claim 10, wherein the first network device is a different device than the second network device.
14. The volatile or non-volatile computer-readable storage medium of claim 10, wherein:
the first network device is the same device as the second network device; and
the one or more operations that the first service is configured to perform are different than the one or more operations that the second service is configured to perform.
15. The method of claim 1, wherein the second service is provided by the first network device.
16. The volatile or non-volatile computer-readable storage medium of claim 6, wherein the second service is provided by the first network device.

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. An energy management system, comprising:
a memory to store electricity consumption amount of a target object separately for each one of a plurality of operational status of the target object, the electricity consumption amount being measured by an electricity measurement unit; and
a processor to obtain information indicating the operational status of the target object for each day in the future from a calendar, and
predict future electricity consumption amount for each day in the future, using the operational status of the target object for each day and the electricity consumption amount stored for each operational status.
2. The energy management system according to claim 1, wherein the processor predicts electricity bill in units of day based on the predicted electricity consumption amount and electricity bill previously charged in units of month.
3. The energy management system according to claim 2, wherein the processor calculates a reduction target of the electricity consumption amount in units of day.
4. The energy management system according to claim 3, wherein the processor calculates a reduction target of the electricity consumption amount for each time zone within a day based on the calculated reduction target of the electricity consumption amount in units of day.
5. The energy management system according to claim 4, wherein the processor calculates an upper limit value of the electricity consumption amount in units of hour based on the calculated reduction target of the electricity consumption amount for each time zone, the units of hour being defined by a base rate set by an electric company.
6. The energy management system according to claim 3, wherein the operational statuses include workdays when overtime is not recommended, normal workdays, special workdays, and holidays, and the reduction targets of the electricity consumption amount in units of day are configured, respectively, for the operational statuses in the descending order, the workdays when overtime is not recommended, the normal workdays, the special workdays, and the holidays
7. An energy management method, comprising:
storing electricity consumption amount of a target object separately for each one of a plurality of operational status of the target object, the electricity consumption amount being measured by an electricity measurement unit;
obtaining information indicating the operational status of the target object for each day in the future from a calendar; and
predicting future electricity consumption amount for each day in the future, using the operational status of the target object for each day and the electricity consumption amount stored for each operational status.
8. A non-transitory, computer-readable recording medium storing a program that, when executed by a processor, causes the processor to implement an energy management method, the method comprising the steps of:
storing electricity consumption amount of a target object separately for each one of a plurality of operational status of the target object, the electricity consumption amount being measured by an electricity measurement unit;
obtaining information indicating the operational status of the target object for each day in the future from a calendar; and
predicting future electricity consumption amount for each day in the future, using the operational status of the target object for each day and the electricity consumption amount stored for each operational status.