1. A method for supporting machine-to-machine communications, the method performed by a set of servers, the method comprising:
receiving a first message that includes a module identity and a first source Internet protocol address and port (IP:port) number, wherein the module identity is verified using at least one of a shared secret key and a module digital signature;
sending a response to the first source IP:port number, wherein the response includes a set of cryptographic parameters for deriving a public key and a private key;
receiving a series of different module public keys for the module identity;
receiving via a secure connection a module instruction and the module identity; and,
waiting until after (a) receiving a second message, wherein the second message includes a second source IP:port number and the module identity, before (b) sending the module instruction within a server encrypted data to the second source IP:port number, wherein the server encrypted data is ciphered using a module public key from the series.
2. The method of claim 1, wherein the set of cryptographic parameters includes at least one of (i) an elliptic curve cryptography (ECC) named curve, (ii) a value for an ECC defining equation, (iii) a modulus for an RSA algorithm, (iv) a time-to-live value, (v) a value for a random number seed, (vi) a value for a module public key identity, (vii) a value for a module random seed file.
3. The method of claim 1, further comprising encrypting the set of cryptographic parameters with a symmetric key, and sending the encrypted set of cryptographic parameters in the response.
4. The method of claim 1, wherein the set of servers includes at least a first server and a second server, wherein the first server receives the first message and the second server receives the second message, wherein the set of servers includes a shared module database, wherein the shared module database receives the module instruction, and wherein the second server queries the shared module database for the module instruction after receiving the second message.
5. The method of claim 1, wherein a module with the module identity sends (i) the first and the second messages, and (ii) the series of different module public keys, and wherein the module derives the series of different module public keys using at least a set of cryptographic algorithms and the set of cryptographic parameters.
6. The method of claim 6, wherein the module comprises at least one of a mobile phone and a payment terminal, wherein one of the mobile phone and the payment terminal includes a universal integrated circuit card (UICC), wherein the UICC records an initial module private key, and wherein the set of servers records the initial module public key and uses the initial module public key to verify the module identity.
7. The method of claim 1, wherein the series of different module public keys comprises at least a first module public key and a second module public key, wherein the first module public key is received before the second module public key, and wherein the second module public key is authenticated using the first module public key.
8. The method of claim 1, further comprising:
receiving the module instruction from an application server;
decrypting the module instruction using a first server public key, wherein the first server public key is processed using an RSA algorithm; and,
ciphering the server encrypted data using a second server public key, wherein the second server public key is processed using an ECC algorithm.
9. The method of claim 1, wherein the module identity in the first message comprises a first string, and wherein the module identity in the second message comprises a second string, and wherein the first string and the second string are associated with a serial number of a module.
10. The method of claim 1, wherein ciphering the server encrypted data using a module public key from the series further comprises ciphering the server encrypted data with a symmetric key, wherein the symmetric key is shared by using at least one of (i) the module public key from the series and a key derivation function, (ii) an asymmetric ciphering algorithm and the module public key from the series to encrypt the symmetric key, wherein the set of servers sends the symmetric key, and (iii) a digital signature verified with the module public key from the series, wherein the set of servers receives the symmetric key and the digital signature.
11. A method for supporting machine-to-machine communications, the method performed by a set of servers, the method comprising:
using a first server private key to establish a secure connection with at least one application server;
receiving a message, wherein the message includes a module identity and a module digital signature, wherein the module digital signature is verified using a first module public key;
sending a response, wherein the response includes a server digital signature processed using a second server private key;
sending a set of cryptographic parameters for deriving a second module public key;
receiving the second module public key, wherein the second module public key is verified using the first module public key, wherein the second module public key is used to decrypt a module encrypted data, and wherein the module encrypted data includes a sensor data; and,
sending the sensor data and the module identity to the application server.
12. The method of claim 11, wherein the module identity in the first message comprises a first string, and wherein the module identity sent with the sensor data comprises a second string, and wherein the first string and the second string are associated with a serial number of a module.
13. The method of claim 11, wherein the set of servers includes at least a first server and a second server, wherein (i) the first server receives the message and sends the response, and (ii) the second server receives the module encrypted data, wherein the set of servers includes a shared module database, wherein the shared module database records the module identity, the first module public key, and the second module public key.
14. The method of claim 11, wherein the set of cryptographic parameters includes at least one of (i) an elliptic curve cryptography (ECC) named curve, (ii) a value for an ECC defining equation, (iii) a modulus for an RSA algorithm, (iv) a time-to-live value, (v) a value for a random number seed, (vi) a value for a module public key identity, (vii) a value for a module random seed file.
15. The method of claim 11, wherein a module for the module identity sends the message and the second module public key, and wherein the module derives the second module public key using at least a set of cryptographic algorithms and the set of cryptographic parameters.
16. The method of claim 15, wherein the module comprises at least one of a mobile phone and a payment terminal, wherein one of the mobile phone and the payment terminal includes a universal integrated circuit card (UICC), wherein the UICC records a module private key associated with the first module public key, and wherein the set of servers records the first module public key and the module identity.
17. The method of claim 11, wherein the first and second server private keys are different, wherein the first server private key is processed using an RSA algorithm and the second server private key is processed using an ECC algorithm.
18. The method of claim 11, further comprising:
receiving a module instruction and the module identity; and,
waiting until after receiving a third message before sending the module instruction within a server encrypted data, wherein the server encrypted data is ciphered using the second module public key.
19. The method of claim 11, wherein decrypting the module encrypted data using the second module public key further comprises decrypting the module encrypted data with a symmetric key, and at least one of (i) sending the symmetric key using an asymmetric ciphering algorithm and the second module public key, (ii) deriving the symmetric key using a key derivation function and the second module public key, and (iii) receiving (a) the symmetric key using an asymmetric ciphering algorithm and (b) a digital signature, wherein the digital signature is verified using the second module public key.
20. The method of claim 11, wherein verifying the second module public key using the first module public key comprises at least one of (i) receiving the second module public key with a digital signature, where the digital signature is verified with the first module public key, and (ii) receiving an encrypted data with the second module public key, wherein the encrypted data is decrypted using the first module public key.
21. A system for supporting machine-to-machine communications, the system comprising:
A module controller for monitoring a first Internet protocol address and port (IP:port) number, for receiving a first message comprising a module public key, a module identity, a set of cryptographic parameters, and a first source IP:port number, for sending a server digital signature, for receiving a second message comprising the module identity and a second source IP:port number, and for sending a response to the second message, wherein the response comprises (i) a module instruction and (ii) the second source IP:port number as a destination IP:port number;
An application interface for monitoring a second IP:port number, for receiving a module instruction and the module identity, wherein the module instruction with the module identity is received after the first message and before the second message;
A shared module database for recording a shared secret key, the module identity, the module public key, and the set of cryptographic parameters; and,
A set of cryptographic algorithms for using the shared secret key to verify the received module public key is associated with the recorded module identity, and for processing the server digital signature using a server private key.
22. The system of claim 21, further comprising:
a set of servers, wherein the set of servers includes the module controller and the application interface, wherein the application interface uses a first IP address to receive the application message and the module controller uses a second IP address to receive the second message; and,
the cryptographic algorithms for decrypting at least one of the first module public key and the set of cryptographic parameters.
23. The system of claim 21, wherein verifying the module public key using the shared secret key comprises using the shared secret key and at least one of (i) a message digest algorithm, (ii) a module digital signature, wherein the module digital signature was processed using the shared secret key, and (iii) a symmetric ciphering algorithm, wherein the symmetric ciphering algorithm uses the shared secret key.
24. The system of claim 21, further comprising the set of cryptographic algorithms for using a first server public key with the application interface, and a second public key with the module controller, wherein the first server public key is associated with an RSA algorithm, and wherein the second public key is associated with an elliptic curve cryptography (ECC) algorithm.
25. The system of claim 21, wherein the set of cryptographic parameters includes at least one of (i) an elliptic curve cryptography (ECC) named curve, (ii) a value for an ECC defining equation, (iii) a modulus for an RSA algorithm, (iv) a time-to-live value, and (v) a value for a module public key identity.
26. The system of claim 21, wherein the second message includes a server instruction, wherein the server instruction is received in a module encrypted data, wherein the module encrypted data includes a security token, and at least one of a sensor measurement, a registration message, and an acknowledgement, and wherein the module encrypted data is processed using the set of cryptographic parameters.
27. The system of claim 21, further comprising the module controller for receiving a series of different module public keys with the module identity after receiving the first message, wherein each of the different module public keys in the series is verified using a prior module public key in the series.
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 touch-and-close fastener part (32) comprising:
a functional layer (2, 2\u2032) which fixes a backing surface (8) that is formed from a thread system (10, 10\u2032) with at least two line elements (12a-12d, 14a-14c) which form meshes (16a-16b\u2033, 20a-20a\u2033) and which are connected to one another,
at least one further individual functional layer which has formed andor formable connecting elements (30a-30b\u2033; 30, 30\u2033), formed from a further thread system which is incorporated at least in individual sections into the thread system (10, 10\u2032),
characterized in that the thread systems (10, 10\u2032) are connected to one another with the formation of passage sites (24a-24d; 24\u2032, 24\u2033) whose free cross-sectional area takes up more than 20% of the corresponding backing area (8).
2. The touch-and-close fastener part according to claim 1, characterized in that one thread system (10, 10\u2032) which forms a functional layer (2, 2\u2032) comprises a series arrangement of at least two line elements (12a-12d, 14a-14c, 26a-26c, 26\u2032, 26\u2033) which are adjacent to one another and which run in a longitudinal direction (4), the line elements (12a-12d, 14a-14c, 26a-26c, 26\u2032, 26\u2033) each forming a sequence of essentially identical meshes (16a-16b\u2033, 20a-20b\u2033, 28a-28b, 28\u2032, 28\u2033) which face in a transverse direction (6) and are arranged without offset to one another in the longitudinal direction (4), and one or more meshes (16a-16b\u2033, 20a-20b\u2033, 28a-28b, 28\u2032, 28\u2033) of at least one line element (12a-12d, 14a-14c, 26a-26c, 26\u2032, 26\u2033) extending through or around the corresponding meshes (16a-16b\u2033, 20a-20b\u2033, 28a-28b, 28\u2032, 28\u2033) of the respectively adjacent line element (12a-12d, 14a-14c, 26a-26c, 26\u2032, 26\u2033).
3. The touch-and-close fastener part according to claim 1, characterized in that the thread system which forms the further functional layer comprises at least one line element (26a-26b, 26\u2032, 26\u2033) which runs in the longitudinal direction (4) with a sequence of essentially identical meshes (28a-28b, 28\u2032, 28\u2033), facing in the transverse direction (6), which are at least partially, especially regularly, separable andor separated for the formation of connecting elements (30a-30b\u2033, 30, 30\u2032).
4. The touch-and-close fastener part according to claim 2, characterized in that the at least one line element (26a-26b, 26\u2032, 26\u2033) of the further functional layer following the path of a corresponding line element (12a-12d) is located in the backing surface (8) and is incorporated via meshes (16a-16b\u2033, 20a-20b\u2033).
5. The touch-and-close fastener part according to claim 1, characterized in that the meshes (16a-16b\u2033, 20a-20b\u2033) of adjacent line elements (12a-12d, 14a-14c) have essentially the same extension andor sequence in the longitudinal direction (4) andor in the transverse direction (6).
6. The touch-and-close fastener part according to claim 1, characterized in that the thread system (10, 10\u2032) which forms the backing surface (8) has a series arrangement of alternating first and second line elements (12a-12d, 14a-14c), the first meshes (16a-16b\u2033) of the first line elements (12a-12d) in the transverse direction (6) having a greater extension than the second meshes (20a-20b\u2033) of the second line elements (14a-14c).
7. The touch-and-close fastener part according to claim 1, characterized by a pattern which repeats at regular intervals in the transverse direction (6) andor longitudinal direction (4), composed of essentially identically made andor arranged line elements (12a-12d, 14a-14c, 26a-26c) of the thread systems (10).
8. The touch-and-close fastener part according to claim 1, characterized in that the passage openings (24a-24d, 24\u2032, 24\u2033) are made in the shape of a parallelogram, especially diamond-shaped or rectangular, andor polygonal, especially hexagonal.
9. The touch-and-close fastener part according to claim 1, characterized in that the touch-and-close fastener part (32) is produced from a preferably thermoplastic material, especially polyamide or preferably isotactic polypropylene.
10. The touch-and-close fastener part according to claim 1, characterized in that the line elements (12a-12d, 14a-14c, 26a-26c, 26\u2032, 26\u2033) are made as monofilaments, multifilaments, andor yarns.
11. The touch-and-close fastener part according to claim 1, characterized in that the connecting elements (30a-30b\u2033, 30, 30\u2032) have at least in part interlocking heads andor are made mushroom-like.
12. The touch-and-close fastener part according to claim 1, characterized in that the connecting elements (30a-30b\u2033, 30, 30\u2032) are or can be arranged on one side of the touch-and-close fastener part (32).
13. Use of a touch-and-close fastener part according to claim 1 for fastening a grinding wheel to an abrasive holder andor for forming and executing and arranging an abrasive.
14. A method for producing a touch-and-close fastener part (32), comprising a functional layer (2, 2\u2032) which fixes a backing surface (8), which layer is formed from a thread system (10, 10\u2032) with at least two line elements (12a-12d, 14a-14c) which form meshes (16a-16b\u2033, 20a-20b\u2033) and which are connected to one another and at least one individual further functional layer which has formed andor formable connecting elements (30a-30b\u2033, 30, 30\u2032), formed from one further thread system which is incorporated at least in individual sections into the thread system (10, 10\u2032), characterized in that the thread systems (10, 10\u2032) are connected to one another with the formation of passage sites (24a-24d, 24\u2032, 24\u2033) such that their free cross-sectional area takes up more than 20% of the corresponding backing area (8).
15. The method according to claim 14, characterized in that meshes (28a-28b, 28\u2032, 28\u2033) which are provided on at least one line element (26a-26c, 26\u2032, 26\u2033) of the further thread system are separated and connecting elements (30a-30b\u2033, 30, 30\u2032) are formed.
16. The method according to claim 15, characterized in that the meshes (28a-28b, 28\u2032, 28\u2033) are clipped and the free end of the separated meshes (28a-28b, 28\u2032, 28\u2033) are melted on to form mushroom head-like thickenings, especially by singeing.