Machine to Machine Communications

2. The method of claim 1, wherein the connection data comprises one or more server contact information resources and one or more server URI scheme resources.

3. The method of claim 2, wherein a server contact information resource is to identify the location or address of the server.

4. The method of claim 2, wherein the server contact information resource comprises one or more of: a fully qualified domain name; a port number; an internet protocol address and a Short Message Service value.

5. The method of claim 1, wherein a server URI scheme resource is to specify a security binding for communication with the server.

6. The method of claim 5, wherein the security binding specifies security protocol details to establish the secure communication session.

7. The method of claim 5, wherein the security binding specifies one or more further protocol details to establish the secure communication session.

8. The method of claim 7, wherein the one or more further protocol details comprise one or more of: transport protocol details and application protocol details.

10. The method of claim 1, wherein the server connection data specifies one or more properties of the server.

14. The method of claim 13 wherein the first Server Security URI and second Server Security URI are the same or wherein the first Server Security URI and second Server Security URI are different from one another.

15. The method of claim 1, wherein the client device is a lightweight machine to machine (LwM2M) device.

16. The method of claim 1, wherein the server is a LwM2M server and/or wherein the second server is a bootstrap server.

18. A non-transitory computer readable storage medium comprising code which when implemented on a processor causes the processor to carry out the method of claim 1.