Abstract: A plurality of pieces of to-be-processed data are obtained, and a plurality of groups corresponding to the plurality of pieces of to-be-processed data are further obtained. Watermarks are added to to-be-processed data in the target group by using the target group as a granularity. Because watermarks are added to the plurality of pieces of to-be-processed data by using the group as the granularity, although the to-be-processed data in the group is modified due to watermark adding, the to-be-processed data changes within a range of a small amount of to-be-processed data included in the target group, and does not change within a range of the to-be-processed data, thereby alleviating a problem that the data is severely distorted after watermark adding. When to-be-processed data with similar semantics is placed in a same group, semantics of the to-be-processed data in the target group has a relatively small change after watermark adding.

Abstract: A heat pump system, a heat management method and a vehicle are provided. The heat pump system includes an integrated heat exchanger integrated with a superconducting liquid flow passage and a refrigerant flow passage. The refrigerant flow passage is provided inside an on-board refrigerant circulation loop and is used for cooling and/or heating to adjust the temperature within a passenger compartment of a vehicle. The superconducting liquid flow passage is in communication with a motor heat dissipating conduit, for absorbing the heat generated by an on board motor and transferring the heat to the integrated heat exchanger by means of phase change heat transfer. The heat pump system can increase the energy utilization rate for the vehicle and reduce the allowable ambient temperature of the heat pump system.

Abstract: Granular inventory management with conflict resolution at a target is provided. A client receives inventory management requests, as default settings and/or from a server. Each request includes action instance(s), which have an action key, action type, action detail(s), a precedence, and a sequence number. The client identifies a conflict if two instances have the same action type but incompatible detail(s). The client resolves the conflict, based on precedence and sometimes also on sequence numbers. The client performs the resulting action instance(s), and results are sent back for inclusion in an inventory report. Action details may specify a schedule for recurring actions. A precedence may be specified by an administrator or be built-in. Default and other requests may be defined by viewing inventory classes in a graphical user interface, entering an action based on inventory class(es), and entering target device group selection(s). Inventory classes may be captured from a live system.

Abstract: Granular inventory management with conflict resolution at a target is provided. A client receives inventory management requests, as default settings and/or from a server. Each request includes action instance(s), which have an action key, action type, action detail(s), a precedence, and a sequence number. The client identifies a conflict if two instances have the same action type but incompatible detail(s). The client resolves the conflict, based on precedence and sometimes also on sequence numbers. The client performs the resulting action instance(s), and results are sent back for inclusion in an inventory report. Action details may specify a schedule for recurring actions. A precedence may be specified by an administrator or be built-in. Default and other requests may be defined by viewing inventory classes in a graphical user interface, entering an action based on inventory class(es), and entering target device group selection(s). Inventory classes may be captured from a live system.