1.-17. (canceled)
18. A device for stacking plate-like products each with an upper side and an underside and at least two lateral surfaces located some distance apart into a straight, cylindrical stack, comprising:
a lower deflection device;
an upper deflection device;
at least one traction mechanism of a traction mechanism drive that revolves between the lower and the upper deflection device configured to be brought into contact with each lateral surface of the plate-like products;
a back stop of the traction mechanism drive configured to prevent downward movement of the traction mechanism resting against the stack of the plate-like products;
a movable counterholding unit configured to be brought into contact with the upper side of the stack; and
a lifting arrangement for at least one plate-like product that can be moved in the direction of the underside of the stack and can be moved between a receiving position located below the lower deflection device of each traction mechanism drive and a delivery position located above it.
19. The device in accordance with claim 18, wherein each traction mechanism drive has support rollers for the revolving traction mechanism.
20. The device in accordance with claim 18, wherein each traction mechanism drive has a conveyor belt as the traction mechanism.
21. The device in accordance with claim 18, wherein each traction mechanism drive has a chain as the traction mechanism.
22. The device in accordance with claim 18, wherein the moveable counterholding unit is weighted.
23. The device in accordance with claim 18, wherein the moveable counterholding unit is connected with a drive at least for the application of force to the upper side of the stack.
24. The device in accordance with claim 18, wherein at least one of the traction mechanism drives on one of the two lateral surfaces of the stack is provided with a device configured to develop contact pressure of the traction mechanism on the lateral surface of the stack.
25. The device in accordance with claim 18, wherein at least one of the traction mechanism drives on one of the two lateral surfaces of the stack can be completely moved away from the stack.
26. The device in accordance with claim 18, wherein the moveable counterholding unit has a plate with a recess configured to engage an arm of an extraction device.
27. The device in accordance with claim 18, wherein the device has a guide configured to guide the stack at least on its rear side.
28. The device in accordance with claim 27, wherein the guide is a guide rods.
29. The device in accordance with claim 25, further comprising:
at least one locking element configured to rotate about an axis having a stop face configured to be temporarily brought into contact with the edge of the underside of the stack.
30. A method for stacking plate-like products with an upper side and an underside and at least two lateral surfaces located some distance apart into a straight, cylindrical stack, comprising:
lifting the plate-like products into a stack in a stack nest from below against the force of gravity;
holding the plate-like products in the stack by applying force at least to the lateral surfaces of the stack to prevent dropping in the direction of the force of gravity; and
adding additional plate-like products to the stack in the stack nest from the underside while the application of force is maintained.
31. The method in accordance with claim 30, wherein force is applied to the stack from its upper side by a counterholding unit.
32. The method in accordance with claim 30, wherein the plate-like products are lifted into the stack nest by a lifting arrangement.
33. The method in accordance with claim 30, wherein the products are delivered to the lifting arrangement from a product stock reserve.
34. The method in accordance with claim 30, further comprising:
bringing an extraction device into contact with the upper side and the underside of the stack, and
temporarily suspending the application of force to the lateral surfaces of the stack and the application of force by the counterholding unit.
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 for differentiating between at least two types of Protocol data Units (PDU) in a Device to Device (D2D) communication network, the method comprising:
transmitting, by a transmitting UE of the D2D communication network, at least one PDU to at least one receiving UE;
identifying, by the receiving UE, a PDU type of the at least one PDU received from the transmitting UE, wherein the PDU type is identified based on a unique data in the header of the at least one received PDU; and
processing, by the receiving UE, the at least one received PDU using at least one data processing function, wherein the data processing function is selected based on the PDU type of the PDU.
2. The method as claimed in claim 1, wherein transmitting the at least one PDU by the transmitting UE further comprises:
receiving, by the transmitting UE, the at least one PDU to be transmitted from a higher layer protocol;
identifying, by the transmitting UE, a PDU type of the at least one PDU;
mapping, by the transmitting UE, the PDU to at least one D2D radio bearer, wherein the D2D radio bearer handles PDU of at least the identified PDU type of the PDU; and
processing, by the transmitting UE, the at least one PDU using at least one data processing function, wherein the processing of the at least one PDU comprises associating the unique data that indicates the PDU type of the data to the processed PDU.
3. The method as claimed in claim 2, wherein associating the at least one unique data that indicates the PDU type of the at least one PDU further comprises:
selecting at least one Logical Channel ID (LCID) that matches the PDU type of the at least one PDU, by the transmitting UE wherein one or more LCIDs indicates the PDU type;
assigning the selected LCID to the at least one D2D radio bearer that handles the at least one PDU, by the transmitting UE; and
adding the selected LCID in an LCID field in header field of the at least one PDU.
4. The method as claimed in claim 2, wherein associating the at least one unique data that indicates the PDU type of the at least one PDU further comprises adding PDU type in a PDU type field in a header field of the at least one PDU.
5. The method as claimed in claim 1, wherein the PDU type is one of Internet Protocol PDU (IP PDU), Address Resolution Protocol PDU (ARP PDU), Discovery PDU, Relay PDU and Signaling PDU.
6. The method as claimed in claim 1, wherein the PDU type of the at least one PDU is Address Resolution Protocol (ARP PDU), wherein differentiating the at least one ARP PDU further comprises:
assigning, by the transmitting UE, an LCID for ARP Packets to the D2D radio bearer that handles the at least one ARP PDU being transmitted, wherein the LCID for ARP Packets is at least one LCID reserved for ARP PDU;
transmitting, by the transmitting UE, the at least one ARP PDU with the LCID for ARP Packets to at least one receiving UE; and
identifying, by the receiving UE, PDU type of a received PDU as ARP if the LCID for ARP Packets is associated with the received PDU.
7. The method as claimed in claim 1, wherein the PDU type of the at least one PDU is Address Resolution Protocol (ARP PDU), wherein differentiating the ARP PDU further comprises:
adding, by the transmitting UE, a PDU type field in a header field of the at least one PDU, wherein the PDU type field is set to a value indicating an ARP PDU;
transmitting, by the transmitting UE, the at least one ARP PDU with the PDU Type field to at least one receiving UE; and
identifying, by the receiving UE, PDU type of a received PDU as ARP, if value of PDU type field in the header of the received PDU indicates ARP PDU.
8. The method as claimed in claim 1, wherein the PDU type of the at least one PDU is Address Resolution Protocol (ARP PDU), wherein differentiating the ARP PDU further comprises:
assigning, by the transmitting UE, an LCID for Non-IP Packets to the D2D radio bearer that handles the at least one ARP PDU being transmitted;
adding, by the transmitting UE, PDU type field in a header field of the at least one ARP PDU, wherein the PDU type field is set to a value indicating ARP PDU;
transmitting, by the transmitting UE, the at least one ARP PDU with the LCID for Non-IP Packets and PDU type in the header of the at least one PDU to at least one receiving UE; and
identifying, by the receiving UE, PDU type of a received PDU as ARP if LCID field in header equals LCID for Non-IP Packets and PDU type field is set to ARP in received PDU.
9. A system for differentiating between at least two types of Protocol data Units (PDU) in a Device to Device (D2D) communication network, the system configured to:
transmit, by a transmitting UE of the D2D communication network, at least one PDU to at least one receiving UE;
identify, by the receiving UE, a PDU type of the at least one PDU received from the transmitting UE, wherein the PDU type is identified based on a unique data in the header of the at least one received PDU; and
process, by the receiving UE, the at least one PDU using at least one data processing function, wherein the data processing function is selected based on the PDU type of the data.
10. The system as claimed in claim 9, wherein the transmitting UE is configured to transmit the at least one PDU by:
receiving, by a transmitter module of the transmitting UE, the at least one PDU to be transmitted from a higher layer protocol module of the transmitting UE;
identifying, by the transmitter module, a PDU type of the at least one PDU;
mapping, by the transmitter module, the at least one PDU to at least one D2D radio bearer, wherein the D2D radio bearer is configured to handle PDU of at least the identified PDU type of the at least one PDU; and
processing, by the transmitter module, the at least one PDU using at least one data processing function, wherein the processing of the at least one PDU comprises associating the unique data that indicates the PDU type of the data to the processed PDU.
11. The system as claimed in claim 10, wherein the transmitter module of the transmitting UE is configured to associate the at least one unique data that indicates the PDU type of the at least one PDU by:
selecting at least one Logical Channel ID (LCID) that matches the PDU type of the at least one PDU, wherein one or more LCIDs indicates the PDU type;
assigning the selected LCID to the at least one D2D radio bearer that handles the at least one PDU; and
adding the selected LCID in an LCID field in header field of the at least one PDU.
12. The system as claimed in claim 10, wherein the transmitter module is configured to associate the at least one unique data that indicates the PDU type of the at least one PDU by adding PDU type in a PDU type field in a header field of the at least one PDU.
13. The system as claimed in claim 9, wherein the system is configured to differentiate an Address Resolution Protocol PDU (ARP PDU) by:
assigning, by a transmitter module of the transmitting UE, an LCID for ARP Packets to the D2D radio bearer that handles the ARP PDU being transmitted, wherein the LCID for ARP Packets is at least one LCID reserved for ARP PDU;
transmitting, by the transmitter module of the transmitting UE, the ARP PDU with the LCID for ARP Packets to at least one receiving UE; and
identifying, by receiver module of the receiving UE, PDU type of a received PDU as ARP if the LCID of ARP Packets is associated with the received PDU.
14. The system as claimed in claim 9, wherein the system is configured to differentiate an Address Resolution Protocol PDU (ARP PDU) by:
assigning, by a transmitter module of the transmitting UE, an LCID for Non-IP Packets to the D2D radio bearer that handles the ARP PDU being transmitted;
adding, by the transmitter module of the transmitting UE, PDU type field in a header field of the PDU wherein the PDU type field is set to a value indicating ARP PDU;
transmitting, by the transmitter module of the transmitting UE, the ARP PDU with the LCID for Non-IP Packets and PDU type in the header of the PDU to at least one receiving UE; and
identifying, by a receiver module of the receiving UE, PDU type of a received PDU as ARP if LCID field in header equals the LCID for Non-IP Packets and PDU type field is set to ARP in received PDU.
15. The system as claimed in claim 9, wherein the system is configured to differentiate an Address Resolution Protocol PDU (ARP PDU) by:
adding, by a transmitter module of the transmitting UE, a PDU type field in a header field of the PDU, wherein the PDU type field is set to a value indicating an ARP PDU;
transmitting, by the transmitter module of the transmitting UE, the ARP PDU with the PDU Type field to at least one receiving UE; and
identifying, by a receiver module of the receiving UE, PDU type of a received PDU as ARP if value of PDU type field in the header of the received PDU indicates ARP PDU.
16. A receiving user equipment (UE) capable of a Device to Device (D2D) communication, comprising:
a receiver configured to receive at least one PDU from a transmitting UE;
a controller configured to:
identify a PDU type of the at least one PDU received from the transmitting UE, wherein the PDU type is identified based on a unique data in the header of the at least one received PDU; and
process the at least one PDU using at least one data processing function, wherein the data processing function is selected based on the PDU type of the data.
17. A transmitting user equipment (UE) capable of a Device to Device (D2D) communication, comprising:
a higher layer protocol module; and
a transmitter module configured to:
receive at least one PDU to be transmitted from the higher layer protocol module;
identify a PDU type of the at least one PDU;
map the at least one PDU to at least one D2D radio bearer, wherein the D2D radio bearer is configured to handle PDU of at least the identified PDU type of the at least one PDU;
process the at least one PDU using at least one data processing function, wherein the processing of the at least one PDU comprises associating the unique data that indicates the PDU type of the data to the processed PDU; and
transmit the processed at least one PDU to a receiving UE.
18. The transmitting UE of claim 17, wherein the transmitter module is configured to associate the at least one unique data that indicates the PDU type of the at least one PDU by:
selecting at least one Logical Channel ID (LCID) that matches the PDU type of the at least one PDU, wherein one or more LCIDs indicates the PDU type;
assigning the selected LCID to the at least one D2D radio bearer that handles the at least one PDU; and
adding the selected LCID in an LCID field in header field of the at least one PDU.
19. The transmitting UE of claim 17, wherein the transmitter module is configured to associate the at least one unique data that indicates the PDU type of the at least one PDU by adding PDU type in a PDU type field in a header field of the at least one PDU.