What is claimed is:
1. A communication data format for use in communicating data between applications for storage and retrieval, comprising:
a data field for conveying a data item; and
a plurality of attributes associated with said data field, said plurality of attributes including,
a data type identifier for use in determining an executable procedure to be used in processing said data item, and
at least one other attribute used in determining particular operations to be applied in processing said data item by said executable procedure.
2. A communication data format according to claim 1, wherein
said data field is used for conveying a data item comprising at least one of, (a) a name of an individual person, (b) a patient name, and (c) patient associated data.
3. A communication data format according to claim 1, wherein
said data type identifier identifies said data item as a particular object type to be processed by particular executable procedures and as having associated particular object properties determining data items associated with said data type.
4. A communication data format according to claim 1, wherein
said at least one other attribute includes one or more attributes used by said executable procedure and comprises one or more of, (a) a characteristic to be used in filtering information to derive said data item, (b) placeholder data to be replaced by an acquired data item, (c) an indicator indicating said data item comprises a list of items to be provided and (d) an indicator indicating said data item is read only.
5. A communication data format according to claim 4, wherein
said list of items is a hierarchical list of items.
6. A communication data format according to claim 1, wherein
said data format is coded according to Extensible Markup Language (XML).
7. A communication data format according to claim 1, wherein
said at least one other attribute comprises one or more of, (a) an indicator identifying a maximum data length of said data item, and (b) an indicator identifying said data item as containing null data for subsequent replacement by acquired data.
8. A communication data format according to claim 1, wherein
said at least one other attribute is identified as being subsequently determined following completion of an event.
9. A communication data format according to claim 1, wherein
said at least one other attribute determines said data type following completion of an event.
10. A communication data request format for use by a first application in acquiring data from a second application, comprising:
a data field for conveying a data item provided by said second application; and
a plurality of attributes associated with said data field for use by said second application in providing said data item in response to receiving said data request format, said plurality of attributes including,
a data type identifier for use in determining an executable procedure to be used by said second application in providing said data item, and
at least one other attribute, for use by said second application in deriving said data item, said at least one other attribute comprising one or more of, (a) a characteristic for use in filtering information to derive said data item, (b) placeholder data to be replaced by a desired data item, (c) an indicator indicating said data item comprises a list of items to be provided by said second application and (d) an indicator indicating said data item is read only.
11. A communication data request format according to claim 10, wherein
said data field is used for conveying a data item comprising at least one of, (a) a name of an individual person, (b) a patient name, and (c) patient associated data.
12. A communication data request format according to claim 10, wherein
said data type identifier identifies said data item as a particular object type to be processed by particular executable procedures and as having associated particular object properties determining data items associated with said data type.
13. A communication data request format according to claim 10, wherein
said characteristic for use in filtering information to derive said data item comprises an expression used for identifying a parameter.
14. A communication data update format for use by a first application in updating data acquired from a second application and communicating said updated data to said second application, comprising:
a data field for conveying a data item to said second application; and
a plurality of attributes associated with said data field for use by said second application in using said data item in updating a stored corresponding data item in response to receiving said data update format, said plurality of attributes including,
a data type identifier for use in determining an executable procedure to be used by said second application in updating said stored corresponding data item, and
at least one other attribute, for use by said second application in updating said stored corresponding data item, said at least one other attribute comprising one or more of, (a) an indicator identifying said data item conveyed to said second application as being a modified version of a data item previously acquired from said second application and (b) an indicator identifying said data item conveyed to said second application as being a new data item for storage.
15. A communication data update format according to claim 14, wherein
said at least one other attribute is identified as being subsequently determined following completion of an event.
16. A communication data update format according to claim 14, wherein
said at least one other attribute identifies a particular stored data item to be updated of a plurality of stored data items.
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 monitoring scheduling information in a wireless communication system, the method comprising:
monitoring, by a user equipment, a first physical downlink control channel (PDCCH) having first scheduling information; and
monitoring, by the user equipment, a second PDCCH having second scheduling information on the basis of the first scheduling information,
wherein the second scheduling information includes a resource assignment for a plurality of serving cells.
2. The method of claim 1, wherein the first PDCCH and the second PDCCH are monitored in the same subframe of the same serving cell.
3. The method of claim 1, wherein the first scheduling information includes information indicating the plurality of serving cells.
4. The method of claim 1, wherein the first scheduling information includes information regarding a payload size of the second scheduling information.
5. The method of claim 1, wherein the first scheduling information includes information for monitoring the second PDCCH.
6. The method of claim 5, wherein the first scheduling information includes information indicating a radio resource to which the second PDCCH is assigned.
7. The method of claim 1, wherein a cyclic redundancy check (CRC) of the first scheduling information and a CRC of the second scheduling information are masked with different identifiers.
8. The method of claim 1, wherein the resource assignment in the second scheduling information includes a resource assignment for a plurality of physical downlink shared channel (PDSCHs) for a plurality of serving cells.
9. The method of claim 1, wherein the resource assignment in the second scheduling information includes a resource assignment for a plurality of physical uplink shared channel (PUSCHs) for a plurality of serving cells.
10. The method of claim 1, wherein the first PDCCH and the second PDCCH are monitored in a primary cell.
11. An apparatus for monitoring scheduling information in a wireless communication system, the apparatus comprising:
a radio frequency (RF) unit configured to transmit and receive a radio signal; and
a processor operably coupled to the RF unit and configured to:
monitor a first physical downlink control channel (PDCCH) having first scheduling information; and
monitor a second PDCCH having second scheduling information on the basis of the first scheduling information,
wherein the second scheduling information includes a resource assignment for a plurality of serving cells.
12. The apparatus of claim 11, wherein the first PDCCH and the second PDCCH are monitored in the same subframe of the same serving cell.
13. The apparatus of claim 11, wherein the first scheduling information includes information indicating the plurality of serving cells.
14. The apparatus of claim 11, wherein the first scheduling information includes information regarding a payload size of the second scheduling information.
15. The apparatus of claim 11, wherein the first scheduling information includes information for monitoring the second PDCCH.