1. The method of lateral turning and repositioning of patients in bed and the prevention and treatment of pressure ulcers, pneumonia and other hazards of immobility in a patient comprising the steps of:
a. turning the patient 30\xb0 in the lateral inclined position in the bed, and
b. supporting the patient in the desired turned position with a patient positioning aid comprising:
a generally wedge-shaped multisided polymeric foam cushion having a length which approximates the length of a patient’s torso, and a height adequate to prevent the rolling of a patient,
the cushion having a caretaker panel, a flat or convex patient panel, and a flat bottom panel,
the angle between the patient panel and the bottom panel being approximately 30\xb0,
the cushion comprised of an inner core of a strong, resilient, high modulus of elasticity foam having a density of 1.4-4.6 pounds per cubic foot and an indention force deflection of 30-80 and an outer layer of soft, compliant, viscoelastic foam having a density of not less than 1.2 pounds per cubic foot and an indention force deflection equal to or less than 30, and
the cushion having a cover comprised of a moisture proof low friction and shear reducing material, the cover having a high friction polyurethane, butyl rubber, or vinyl coating on the portion of the cover covering the bottom panel of the cushion.
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 method of providing a machine-to-machine (M2M) service, the method comprising:
obtaining device identification information on a specific M2M device associated with a requested M2M service;
obtaining device data corresponding to the device identification information;
determining a user interface (UI) template corresponding to the requested M2M service; and
creating an M2M application data by combining the obtained device data and the determined UI template.
2. The method of claim 1, wherein the device identification information is obtained from an application data request received from an application service server.
3. The method of claim 1, wherein the obtaining device data includes:
sending a device data request based on the device identification information, to an M2M server; and
receiving the device data from the M2M server, in response to the device data request.
4. The method of claim 1, wherein the determining includes:
identifying a device type from the device identification information; and
retrieving the UI template corresponding to the identified device type, from a storage unit.
5. The method of claim 2, wherein the determining includes:
obtaining template identification information from an application data request; and
retrieving the UI template corresponding to the obtained template identification information, from a storage unit.
6. The method of claim 5, wherein the retrieving includes:
when the template identification information includes a plurality of template identifiers,
retrieving a plurality of UI templates corresponding to the plurality of template identifiers.
7. The method of claim 6, wherein the creating includes:
creating a plurality of M2M application data by combining each of the plurality of retrieved UI templates and a corresponding device data; and
creating an integral application data by combining the plurality of M2M application data.
8. The method of claim 1, further comprising:
receiving a registration request including at least one UI template, from at least one of a UI template providing system, a user terminal, and a template developer terminal;
determining whether each of the at least one template satisfies a predetermined registration condition; and
storing a UI template which satisfies the predetermined registration condition.
9. The method of claim 8, wherein each of the at least one UI template is configured to include at least one of device identification information, a device type, a device data type, a device data range, a device control type, and graphical user interface (GUI) format information.
10. The method of claim 9, wherein the predetermined registration condition is established in association with at least one of the device data type, the device data range, the device control type, and essential constituent information.
11. The method of claim 1, wherein the method is performed by an application data server coupled to at least one of an M2M server and an application service server through an intranet network.
12. The method of claim 11, further comprising:
sending the created M2M application data to the application service server for transfer of the created M2M application data to a user terminal.
13. A method of registering a user interface (UI) template for a machine-to-machine (M2M) service, the method comprising:
receiving a registration request including at least one UI template;
determining whether each of the at least one UI template satisfies a predetermined registration condition; and
storing a UI template which satisfies the predetermined registration condition.
14. The method of claim 13, wherein each of the at least UI template is configured to include at least one of device identification information, a device data type, a device data range, a device control type, and graphical user interface (GUI) format information.
15. The method of claim 14, wherein the predetermined registration condition is established in association with at least one of the device data type, the device data range, the device control type, and essential constituent information.
16. The method of claim 13, wherein:
the method is performed by an application data server coupled to at least one of an M2M server and an application service server through an intranet network; and
the registration request is received from at least one of a UI template providing system, a user terminal, and a template developer terminal.
17. An apparatus for providing a machine-to-machine (M2M) service, the apparatus comprising:
a template managing unit configured to store at least one user interface (UI) template;
an interworking unit configured to obtain a device data from an M2M server; and
an application data generating unit configured to determine a UI template to accommodate the obtained device data among the at least one stored UI template, and to create an M2M application data by combining the obtained device data and the determined UI template.
18. The apparatus of claim 17, wherein the interworking unit is configured to:
receive an application data request from an application service server;
send a device data request to the M2M server;
receive a corresponding device data from the M2M server; and
send the created M2M application data to the application service server.
19. The apparatus of claim 18, wherein the application data generating unit is configured to:
obtain at least one of device identification information, a requested service content, and a template identifier (ID) from the application data request;
determine the UI template based on at least one the obtained device identification information and the obtained template identifier (ID); and
create the M2M application data by combining the received corresponding device data and the determined UI template.
20. The apparatus of claim 18, wherein the apparatus is an application data server coupled to at least one of the M2M server and the application service server through an intranet network.