All The Claims

1. A robot arm system, comprising:
a support base;
a first robot arm rotatably connected to the support base;
a first driving mechanism driving the first robot arm to rotate around a first rotation axis relative to the support base;
a second robot arm rotatably connected to the first robot arm;
a second driving mechanism driving the second robot arm to rotate around a second rotation axis relative to the first robot arm;
a wrist assembly connected to the second robot arm;
a first wheel positioned on the support base;
a second wheel positioned on the second robot arm;
a third wheel positioned on the wrist assembly and rotatably connected to the second robot arm;
a first flexible belt connecting the first wheel with the second wheel; and
a second flexible belt connecting the third wheel with the second wheel, wherein the first wheel, the second wheel, and the third wheel have a substantially same radius.
2. The robot arm system of claim 1, further comprising a first pre-tighten assembly pressing against the first flexible belt.
3. The robot arm system of claim 2, wherein the first pre-tighten assembly comprises a pressure wheel pressing on the first flexible belt and a support pole connecting with the pressure wheel.
4. The robot arm system of claim 2, further comprising a second pre-tighten assembly pressing against the second flexible belt.
5. The robot arm system of claim 1, wherein the first driving mechanism comprises a first motor, a first worm, and a first worm gear, the first motor is positioned on the support base and drives the first worm to rotate, and the first worm meshes with the first worm gear, thereby driving the first robot arm to rotate around the first rotation axis.
6. The robot arm system of claim 5, wherein the first worm gear forms a first torque adjusting portion to offset a load torque effect of the robot arm system.
7. The robot arm system of claim 1, wherein the second driving mechanism comprises a second motor, a second worm, a second worm gear, a belt transmission assembly, the second motor is positioned on the support base and drives the second worm to rotate, the second worm meshes with the second worm gear, and the belt transmission assembly connects the second worm gear to the second worm, thereby driving the second robot arm to rotate around the second rotation axis.
8. The robot arm system of claim 7, wherein the second worm gear forms a first torque adjusting portion to offset a load torque effect of the robot arm system.
9. The robot arm system of claim 1, wherein the first wheel is positioned on the support base via an amounting base, the second wheel is positioned on a first end of the second robot arm, and the third wheel is positioned on the wrist assembly, and is rotatably connected to a second end of the second robot arm.
10. The robot arm system of claim 1, further comprising a bottom base rotatably connected to the support base.
11. The robot arm system of claim 10, further comprising a third driving mechanism driving the support base to rotate around a third rotation axis relative to the bottom base, wherein the third driving mechanism comprises a third motor, a first gear, and a second gear, the first gear is meshed with the second gear, and the third motor drives the first gear to rotate.
12. The robot arm system of claim 7, wherein the first flexible belt and the second flexible belt are synchronous belts, steel ropes, or flat belts.
13. The robot arm system of claim 1, wherein a central axis of the first wheel is aligned with the first rotation axis in a straight line, and a central axis of the second wheel is aligned with the second rotation axis in a straight line.
14. A robot arm system, comprising:
a support base;
a first robot arm rotatably connected to the support base;
a first driving mechanism driving the first robot arm to rotate around a first rotation axis relative to the support base;
a second robot arm rotatably connected to the first robot arm;
a second driving mechanism driving the second robot arm to rotate around a second rotation axis relative to the first robot arm; and
a wrist assembly connected to the second robot arm;
wherein the first driving mechanism comprises a first motor, a first worm, and a first worm gear, the first motor is positioned on the support base and drives the first worm to rotate, the first worm meshes with the first worm gear, thereby driving the first robot arm to rotate around the first rotation axis.
15. The robot arm system of claim 14, wherein the first worm gear forms a first torque adjusting portion to offset a load torque effect of the robot arm system.
16. The robot arm system of claim 14, wherein the second driving mechanism comprises a second motor, a second worm, a second worm gear, a belt transmission assembly, the second motor is positioned on the support base and drives the second worm to rotate, the second worm meshes with the second worm gear, and the belt transmission assembly connects the second worm gear to the second worm, thereby driving the second robot arm to rotate around the second rotation axis.
17. The robot arm system of claim 16, wherein the second worm gear forms a first torque adjusting portion, used to offset the effect of a load torque of the robot arm system.
18. The robot arm system of claim 14, further comprising a bottom base rotatably connected to the support base.
19. The robot arm system of claim 18, further comprising a third driving mechanism driving the support base to rotate around a third rotation axis relative to the bottom base, the third driving mechanism comprises a third motor, a first gear, and a second gear, the first gear is meshed with the second gear, and the third motor drives the first gear to rotate.

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 computer system securely transmitting and verifying a two-party agreement, said system comprising:
a first device, operated by the first party, developing and transmitting a first view of the two-party agreement based upon first device respective non-transmitted and transmitted transaction time dependent and device dependent parameters, the first view including an encrypted part based upon the first device non-transmitted time dependent and device dependent parameters and an unencrypted plaintext part including the first device transmitted transaction time dependent and device dependent parameters,
wherein the first device encrypts the encrypted part of the first view using a first device encryption key according to a deterministic algorithm based on a non-stored Private Identification Entry (PIE) input to the first device and a deterministic algorithm based on the first device non-transmitted transaction time dependent and device dependent parameters:
a second device, operated by the second party, developing and transmitting a second view of the two-party agreement, the second view including an encrypted part encrypted by a second device encryption key and an unencrypted plaintext part including second device transmitted transaction time dependent and device dependent parameters: and
a third device comprising a verification party
receiving the first view and the second view,
generating the first device encryption key based upon the first device transmitted transaction time dependent and device dependent parameters and information known by the third device about the first device PIE and the first device non-transmitted time dependent and device dependent parameters,
generating the second device encryption key based upon the second device transmitted transaction time dependent and device dependent parameters,
decrypting the encrypted part of the first and second views, based upon the respective first and second device encryption keys,
comparing the first view with the second view, and
transmitting a signal based on the comparing,

wherein the first device PIE and the first and second device encryption keys are not communicated among the first, second and third devices.
2. The computer system as in 1, wherein either the first device transmits the first view to the third device and the second device independently transmits the second view to the third device, or the first device transmits the first view to the second device and the second device concatenates the first view and the second view and transmits the concatenated view to the third device.
3. The computer system as in claim 2, wherein the third device transmits a response to the first device and the second device either if the third device determines that the decrypted part of the first view matches the decrypted part of the second view for the agreement or if the third device determines that the decrypted part of the first view does not match the decrypted part of the second view for the agreement.
4. The computer system as in claim 3, wherein the plaintext part of the view of the first device includes a device identification of the first device and a transaction timestamp at the first device as the first device transmitted transaction time dependent and device dependent parameters, and the encrypted part includes data corresponding to an agreement and a device identification of the second device as the second device transmitted device dependent parameter.
5. The computer system as in claim 4, wherein the plaintext portion optionally includes a transaction ID and the encrypted portion optionally includes one or more of the transaction ID, a message digest, the transaction timestamp, a user ID of a user of the first device and padding data.
6. The computer system as in claim 3, wherein the response from the third device to the first device comprises a plaintext part and an encrypted part, wherein the plaintext part of the response includes the first device transmitted device dependent parameter and a third device transaction timestamp and optionally includes a transaction ID, and the encrypted part includes data corresponding to a response to the agreement and optionally includes one or more of the first device transmitted device dependent parameter, the second device transmitted device dependent parameter, the transaction ID, a message digest, the transaction timestamp, a user ID of a user of the first device and padding data.
7. The computer system of claim 6, in which the encrypted part of the response of the third device to the first device is encrypted using a third device encryption key and a cryptographic algorithm in which the third device encryption key is not communicated either between the first device and the second device or the first device and the third device.
8. The computer system of claim 7 in which the third device encryption key used by the third device to encrypt the encrypted portion of the response to the first device is generated according to a deterministic algorithm based on the first device PIE and the third device non-transmitted transaction time dependent parameter.
9. The computer system of claim 8 in which each of the third device and the first device comprises a known pseudo-random number generator, a known hash function and a known transformation function and deterministically produce the first device encryption key by:
the pseudo-random number generator receives as input a seed and a base timestamp, as the information known by the first device and the third device about the first device non-transmitted time dependent and device dependent parameters and receiving as input the transmitted first device transaction timestamp and device dependent parameters, and producing as output a random number;
the transformation function taking as input said random number and the information known by the third device about the first device PIE or the non-stored PIE input to the first device and producing as output a number; and
the hash function taking as input said number and produces as output the first device encryption key.
10. The computer system as in claim 3, wherein the plaintext part of the view of the second device includes a device identification of the second device and a transaction timestamp at the second device as the second device transmitted transaction time dependent and device dependent parameters, and the encrypted part includes data corresponding to an agreement, and a device identification of the first device as the first device transmitted device dependent parameter of the first device.
11. The computer system as in claim 10, wherein the plaintext portion optionally includes a transaction ID and the encrypted portion optionally includes one or more of the transaction ID, a message digest, the transaction timestamp, a user ID of a user of the second device and padding data.
12. The computer system as in claim 3, wherein the response from the third device to the second device comprises a plaintext part and an encrypted part, wherein the plaintext part of the response includes the second device transmitted device dependent parameter and a third device transaction timestamp and optionally includes a transaction ID, and the encrypted part includes data corresponding to a response to the agreement and optionally includes one or more of the second device transmitted device dependent parameter, the first device transmitted device dependent parameter, the transaction ID, a message digest, the transaction timestamp, a user ID of a user of the second device and padding data.
13. The computer system of claim 12, in which the encrypted part of the response of the third device to the second device is encrypted using a third device encryption key and a cryptographic algorithm in which the third device encryption key is not communicated either between the first device and the second device or the second device and the third device.
14. The computer system of claim 13 in which the third device encryption key used by the third device to encrypt the encrypted part of the response is generated according to a deterministic algorithm based on the second device PIE and the third device non-transmitted transaction time dependent parameter.
15. The computer system of claim 14 in which each of the third device and the second device comprises a known pseudo-random number generator, a known hash function and a known transformation function and deterministically produce the second device encryption key by:
the pseudo-random number generator receiving as input a seed and a base timestamp, as information known by the second device and the third device about the second device non-transmitted time dependent and device dependent parameters and receiving as input the transmitted second device transaction timestamp and device dependent parameters and producing as output a random number;
the transformation function taking as input said random number and information known by the third device about the second device PIE or the non-stored second device PIE and producing as output a number; and
the hash function taking as input said number and producing as output the second device encryption key.
16. The computer system of claim 1 in which each of the first device and the third device comprises a known pseudo-random number generator, a known hash function and a known transformation function to deterministically produce, by the first device, the first device encryption key and to deterministically produce, by the third device, the first device encryption key by:
the pseudo-random number generator receiving as input a seed and a base timestamp, as the information known by the first device and the third device about the first device non-transmitted time dependent and device dependent parameters and receiving as input the transmitted first device transaction timestamp and device dependent parameters, and producing as output a random number;
the transformation function taking as input said random number and the information known by the third device about the first device PIE or the non-stored PIE input to the first device and producing as output a number; and
the hash function taking as input said number and producing as output the first device encryption key.
17. The computer system of claim 1 in which the second encryption key used by the second device to encrypt the view is generated according to a deterministic algorithm based on a non-stored Private Identification Entry (PIE) input to the second device and second device non-transmitted transaction time dependent and device dependent parameters, wherein the second device PIE is known only to the user of the second device and is not stored on the second device and is also known to the third device that receives the encrypted view developed by the second device.
18. The computer system of claim 17 in which each of the second device and the third device comprises a known pseudo-random number generator, a known hash function and a known transformation function and deterministically produce the second device encryption key by:
the pseudo-random number generator receiving as input a seed and a base timestamp, as information known by the second device and the third device about the second device non-transmitted time dependent and device dependent parameters and receiving as input the transmitted second device transaction timestamp and device dependent parameters and producing as output a random number;
the transformation function taking as input said random number and information known by the third device about the second device PIE or the non-stored second device PIE and producing as output a number; and
the hash function taking as input said number and producing as output the second device encryption key.
19. A computer system securely transmitting and verifying a multi-party agreement among N parties where N is larger than or equal to two, said computer system comprising:
a collection of N devices, each device operated by a party to the agreement, developing and transmitting its view of the multi-party agreement based upon non-transmitted and transmitted transaction time dependent and device dependent parameters, each view including an encrypted part based upon the device non-transmitted time dependent and device dependent parameters and an unencrypted plaintext part including the device transmitted transaction time dependent and device dependent parameters,
wherein each device encrypts the encrypted part of its view using a device encryption key according to a deterministic algorithm based on a respective non-stored Private Identification Entry (PIE) input to each device and the device non-transmitted transaction time dependent and device dependent parameters: and
an N+1-st device comprising a verification party receiving the views from the N agreement parties,
generating the device encryption keys of the N agreement parties based upon the device transmitted transaction time dependent and device dependent parameters and information known by the N+1-st device about the PIE and the device non-transmitted time dependent and device dependent parameters,
decrypting the encrypted part of each view based upon the device encryption keys,
comparing the views from the N agreement parties, and
transmitting a response signal based on the comparing,

wherein the PIE and the device encryption keys are not communicated among the N agreement.
20. The computer system as in 19, wherein either each of the N devices independently transmits its view to the N+1-st device comprising the verification party, or, each of the N devices concatenates its view to a list of views until all N views are collected so that each view appears once in the list and the list is then transmitted to the N+1-st device.
21. The computer system as in claim 20, wherein the N+1-st device transmits a response to each of the N devices in the multi-party agreement either if it decides that the decrypted part of all N views from the N devices in the multi-party agreement match each other for the purposes of the agreement or if it decides that the decrypted part of all N views from the N devices in the multi-party agreement do not match each other for the purposes of the agreement.
22. The computer system as in claim 21, wherein the plaintext part of the view of a device includes a device identification and a transaction timestamp at each device as the device transmitted transaction time dependent and device dependent parameters, and the encrypted part includes data corresponding to a multi-party agreement and a device identification for each of other devices in the multi-party agreement as the device transmitted device dependent parameter of the other devices.
23. The computer system as in claim 22, wherein the plaintext portion of a view from a device optionally includes a transaction ID, a number of parties in the agreement and the encrypted portion optionally includes one or more of the transaction ID, the number of parties in the agreement, a message digest, the transaction timestamp, a user ID of a user of the device and padding data.
24. The computer system as in claim 20, wherein the response from the N+1-st device to a device in the multi-party agreement comprises of a plaintext part and an encrypted part, wherein the plaintext part of the response includes the device identification of the device as the device transmitted device dependent parameter and a N+1-st device transaction timestamp and optionally includes a transaction ID, and the encrypted part includes data corresponding to a response to the agreement and optionally includes one or more of a device identification of the andor device identification of the other devices of the parties in the agreement as the device transmitted device dependent parameters, the transaction ID, the number of parties in the agreement, a message digest, the transaction timestamp, the user ID of the user of the device and padding data.
25. The computer system of claim 24, in which the encrypted part of the response of the N+1-st device to a device in the multi-party agreement is encrypted using a N+1-st device encryption key and a cryptographic algorithm in which the N+1-st device encryption key is not communicated among the devices and the N+1-st device.
26. The computer system of claim 25 in which the encryption key used by the N+1-st device to encrypt the response to a device in the multi-party agreement is generated according to a deterministic algorithm based on the PIE and the device non-transmitted transaction time dependent parameter.
27. The computer system of claim 26 in which a device in the multi-party agreement and the N+1-st device comprises a known pseudo-random number generator, a known hash function and a known transformation function and deterministically produce the identical of the N+1-st device encryption keys by:
the pseudo-random number generator receiving as input a seed and a base timestamp, as the information known by each device and the N+1-st device about the device non-transmitted time dependent and device dependent parameters and receiving as input the transmitted device transaction timestamp and device dependent parameters, and producing as output a random number;
the transformation function taking as input said random number and the information known by the N+1-st device about the PIE or the non-stored PIE input to the device and producing as output a number; and
the hash function taking as input said number and producing as output the N+1-st device encryption key.
28. The computer system of claim 19, in which a device in the multi-party agreement and the N+1-st device comprises a known pseudo-random number generator, a known hash function and a known transformation function and deterministically produce the identical of the device encryption keys by:
the pseudo-random number generator receiving as input a seed and a base timestamp, as the information known by each device and the N+1-st device about the device non-transmitted time dependent and device dependent parameters and receiving as input the transmitted device transaction timestamp and device dependent parameters, and producing as output a random number;
the transformation function taking as input said random number and the information known by the N+1-st device about the PIE or the non-stored PIE input to the device and producing as output a number; and
the hash function taking as input said number and producing as output the device encryption key.
29. A method of securely transmitting and verifying a two-party agreement in a computer system, said method comprising:
developing and transmitting, by a first device operated by a first party, a first view of the two-part agreement based upon first device respective non-transmitted and transmitted transaction time dependent and device dependent parameters, the first view including an encrypted part based upon the first device non-transmitted time dependent and device dependent parameters and an unencrypted plaintext part including the first device transmitted transaction time dependent and device dependent parameters,
wherein the encrypted part is encrypted using a first device encryption key according to a deterministic algorithm based on a non-stored Private Identification Entry (PIE) input to the first device and the first device non-transmitted transaction time dependent and device dependent parameters:
developing and transmitting, by a second device operated by a second party, a second view of the two-party agreement, the second view including an encrypted part encrypted by a second device encryption key and an unencrypted plaintext part including second device transmitted transaction time dependent and device dependent parameters; and
receiving, by a third device comprising a verification party, the first view and the second view, generating the first device encryption key based upon the first device transmitted transaction time dependent and device dependent parameters and information known by the third device about the PIE and the first device non-transmitted time dependent and device dependent parameters, generating the second device encryption key based upon the second device transmitted transaction time dependent and device dependent parameters, decrypting the encrypted part of the first and second views, based upon the respective first and second device encryption keys, comparing the first view with the second view transmitting a signal based on the comparing,
wherein the PIE and the first and second device encryption keys are not communicated among the first, second and third devices.
30. A method securely transmitting and verifying a multi-party agreement among N parties where N is larger than or equal to two, in a computer system, said method comprising:
developing and transmitting, by a collection of N devices each device operated by a party to the agreement, its view of the multi-party agreement based upon non-transmitted and transmitted transaction time dependent and device dependent parameters, each view including an encrypted part based upon the device non-transmitted time dependent and device dependent parameters and an unencrypted plaintext part including the device transmitted transaction time dependent and device dependent parameters,
wherein the encrypted part is encrypted using a device encryption key according to a deterministic algorithm based upon a respective non-stored Private Identification Entry (PIE) input to each device and the device non-transmitted transaction time dependent and device dependent parameters: and
receiving, by an N+1-st device comprising a verification party, the views from the N agreement parties, generating the respective device encryption keys of the N agreement parties based upon the device transmitted transaction time dependent and device dependent parameters and information known by the N+1-st device about the PIE and the device non-transmitted time dependent and device dependent parameters, decrypting the encrypted part of each view based upon the device encryption keys, comparing the views from the N agreement parties and transmitting a response signal based on the comparing,
wherein the PIE and the device encryption keys are not communicated among the N agreement parties.
31. A computer readable storage controlling a computer to securely transmit and verify a two-party agreement, by the functions comprising:
developing and transmitting, by a first device operated by the first party, a first view of the two-party agreement based upon first device respective non-transmitted and transmitted transaction time dependent and device dependent parameters, the first view including an encrypted part based upon the first device non-transmitted time dependent and device dependent parameters and an unencrypted plaintext part including the first device transmitted transaction time dependent and device dependent parameters,
wherein the encrypted part is encrypted using a first device encryption key according to a deterministic algorithm based on a non-stored Private Identification Entry (PIE) input to the first device and the first device non-transmitted transaction time dependent and device dependent parameters;
developing and transmitting, by a second device operated by the second party, a second view of the two-party agreement, the second view including an encrypted part encrypted by a second device encryption key and an unencrypted plaintext part including second device transmitted transaction time dependent and device dependent parameters; and
receiving, by a third device comprising a verification party, the first view and the second view, generating the first device encryption key based upon the first device transmitted transaction time dependent and device dependent parameters and information known by the third device about the PIE and the first device non-transmitted time dependent and device dependent parameters, generating the second device encryption key based upon the second device transmitted transaction time dependent and device dependent parameters, decrypting the encrypted part of the first and second views, based upon the respective first and second device encryption keys, comparing the first view with the second view and transmitting a signal based on the comparing,
wherein the PIE and the first and second device encryption keys are not communicated among the first, second and third devices.
32. A computer readable storage controlling a computer to securely transmit and verify a multi-party agreement among N parties where N is larger than or equal to two, by the functions comprising:
developing and transmitting, by a collection of N devices each device operated by a party to the agreement, its view of the multi-party agreement based upon non-transmitted and transmitted transaction time dependent and device dependent parameters, each view including an encrypted part based upon the device non-transmitted time dependent and device dependent parameters and an unencrypted plaintext part including the device transmitted transaction time dependent and device dependent parameters,
wherein the encrypted part is encrypted using a first device encryption key according to a deterministic algorithm based on a respective non-stored Private Identification Entry (PIE) input to each device and the first device non-transmitted transaction time dependent and device dependent parameters: and
receiving, by an N+1-st device comprising a verification party, the views from the N agreement parties, generating the respective device encryption keys of the N agreement parties based upon the transmitted device transaction time dependent and device dependent parameters and information known by the N+1-st device about the PIE and the device non-transmitted time dependent and device dependent parameters, decrypting the encrypted part of each view based upon the device encryption keys, comparing the views from the N agreement parties and transmitting a response signal based on the comparing,
wherein the PIE and the device encryption keys are not communicated among the N agreement parties.

1. A method for minimization of drive tests (MDT), comprising:
in a process of activating a MDT task, checking, by an evolved Node B (eNB), a consent type of a user corresponding to a selected terminal, wherein the consent type of the user comprises a consent type of the user indicating whether the terminal user agrees to report position information andor a desired positioning mode for the MDT task if the terminal user agrees to execute the MDT task, wherein the desired positioning mode comprises one of a mode of GPS and a mode of obtaining position information by cell position;
sending, by the eNB, a MDT task activation command to the selected terminal according to a check result of the consent type; and
after receiving measured data reported by the selected terminal, performing, by the eNB, an operation according to the check result of the consent type, wherein the checking, by the eNB, the consent type of a user corresponding to the selected terminal, sending the MDT task activation command to the selected terminal according to the check result of the consent type, and after receiving the measured data reported by the selected terminal, performing the operation according to the check result of the consent type, comprise:
checking, by the eNB, whether the selected terminal user agrees to report position information andor specifies the desired positioning mode if the selected terminal user agrees to report the position information;
if the check result is that the selected terminal user agrees to report position information and allows the use of the specified desired positioning mode, sending, by the eNB, an MDT activation command to the terminal andor assisting the terminal in a positioning query; or
if the check result is that the selected terminal user does not agree to report position information but allows the use of the specified desired positioning mode, sending, by the eNB, a corresponding MDT task activation command to the terminal, wherein the MDT task activation command does not support related positioning query, and returning a check failure and a failure type number corresponding to the failure to an Operations, Administration, and Maintenance (OAM) entity, so that the OAM entity learns the consent type that fails to pass the check.
2. The method according to claim 1, wherein before the checking, by the eNB, the consent type of a user corresponding to the selected terminal, the method further comprises:
obtaining, by the eNB, the consent type of the user corresponding to the selected terminal.
3. The method according to claim 2, wherein the obtaining, by the eNB, the consent type of the user corresponding to the selected terminal comprises:
sending, by the eNB, a temporary identifier of the terminal to a mobility management entity (MME), querying a consent type of the user corresponding to the temporary identifier, and receiving the consent type of the user corresponding to the temporary identifier returned by the MME.
4. The method according to claim 2, wherein the obtaining, by the eNB, the consent type of the user corresponding to the selected terminal comprises:
receiving, by the eNB, the consent type of the terminal from a mobility management entity (MME), wherein the consent type is queried locally by the MME according to the user identifier of the terminal when the terminal accesses a network.
5. The method according to claim 2, wherein the obtaining, by the eNB, the consent type of the terminal comprises:
receiving, by the eNB, a consent type of the terminal reported by the terminal, wherein the consent type is carried in a setup complete message after the selected terminal initiates a connection setup request and sets up a connection with the eNB.
6. The method according to claim 2, wherein the obtaining, by the eNB, the consent type of the terminal comprises:
receiving, by the eNB, the consent type of the terminal that the source base station of the terminal carries in a handover request.
7. The method according to claim 1, wherein before the eNB checks the consent type of the user corresponding to the selected terminal, the method further comprises:
determining, by the eNB, whether the selected terminal is in a roaming state according to a notification received from an MME or a report received from the terminal; and
if the selected terminal is not in a roaming state, selecting, by the eNB, the terminal as a terminal to execute the MDT task.
8. The method according to claim 1, wherein the consent type of the user further comprises a limitation of a geographical area andor duration.
9. A network element, comprising:
an evolved Node B (eNB), comprising:
a checking module, configured to: in a process of activating a minimization of drive tests (MDT) task, check, a consent type of a user corresponding to a selected terminal, wherein the consent type of the user comprises a consent type of the user indicating whether the terminal user agrees to report position information andor a desired positioning mode for the MDT task if the terminal user agrees to execute the MDT task, wherein the desired positioning mode comprises one of a mode of GPS and a mode of obtaining position information by cell position; and
an executing module, configured to: send an MDT task activation command to the selected terminal according to a check result of the consent type; and after receiving measured data reported by the terminal, execute an operation according to the check result of the consent type, wherein the modules configured to check, by the eNB, the consent type of a user corresponding to the selected terminal, send the MDT task activation command to the selected terminal according to the check result of the consent type, and after receiving the measured data reported by the selected terminal, execute the operation according to the check result of the consent type, further configured to:
check whether the selected terminal user agrees to report position information andor specifying a positioning desired mode if the selected terminal user agrees to report the position information; and
if the check result is that the selected terminal user agrees to report position information and allows the use of the specified desired positioning mode, send an MDT activation command to the terminal andor assisting the terminal in a positioning query; or
if the check result is that the selected terminal user does not agree to report position information but allows the use of the specified desired positioning mode, send a corresponding MDT task activation command to the terminal, wherein the MDT task activation command does not support related positioning query, and to return a check failure and a failure type number corresponding to the failure to an Operations, Administration, and Maintenance (OAM) entity, so that the OAM entity learns the consent type that fails to pass the check.
10. The network element according to claim 9, wherein the eNB further comprises:
an obtaining module, configured to: before checking the consent type of the user corresponding to the selected terminal, obtain the consent type of the user corresponding to the selected terminal.
11. The network element according to claim 9, wherein the eNB further comprising:
a receiving module, configured to receive a notification from a mobility management entity (MME) or a report from the selected terminal, and learn whether the selected terminal is in a roaming state; and
a determining module, configured to: before the network element checks the consent type of the user corresponding to the selected terminal, determine whether the selected terminal is in a roaming state; if the selected terminal is not in a roaming state, select the terminal not in a roaming state as a terminal executing the MDT task.
12. The network element according to claim 9, wherein the modules further configured to before the check, by the eNB, the consent type of a user corresponding to the selected terminal, obtain, by the eNB, the consent type of the user corresponding to the selected terminal by sending, by the eNB a temporary identifier of the terminal to a mobility management entity (MME), querying a consent type of the user corresponding to the temporary identifier, and receiving the consent type of the user corresponding to the temporary identifier returned by the MME.
13. The network element according to claim 9, wherein the modules further configured to before the check, by the eNB, the consent type of a user corresponding to the selected terminal, obtain, by the eNB, the consent type of the user corresponding to the selected terminal by receiving, by the eNB, the consent type of the terminal from a mobility management entity (MME), wherein the consent type is queried locally by the MME according to the user identifier of the terminal when the terminal accesses a network.
14. The network element according to claim 9, wherein the modules further configured to before the check, by the eNB, the consent type of a user corresponding to the selected terminal, obtain, by the eNB, the consent type of the user corresponding to the selected terminal by receiving, by the eNB, a consent type of the terminal reported by the terminal, wherein the consent type is carried in a setup complete message after the selected terminal initiates a connection setup request and sets up a connection with the eNB.
15. The network element according to claim 9, wherein the modules further configured to before the check, by the eNB, the consent type of a user corresponding to the selected terminal, obtain, by the eNB, the consent type of the user corresponding to the selected terminal by receiving, by the eNB, the consent type of the terminal that the source base station of the terminal carries in a handover request.
16. The network element according to claim 9, wherein the consent type of the user further comprises a limitation of a geographical area andor duration.
17. A method for minimization of drive tests (MDT), comprising:
in a process of activating a MDT task, checking, by an evolved Node B (eNB), a consent type of a user corresponding to a selected terminal, wherein the consent type of the user comprises a consent type of the user indicating whether the terminal user agrees to report position information andor a specifies desired positioning mode for the MDT task if the terminal user agrees to execute the MDT task, wherein the desired positioning mode comprises one of a mode of GPS and a mode of obtaining position information by cell position;
sending, by the eNB, a MDT task activation command to the selected terminal according to a check result of the consent type; and
after receiving measured data reported by the selected terminal, performing, by the eNB, an operation according to the check result of the consent type, wherein the consent type of the user further comprises a limitation of a geographical area andor duration, wherein the checking, by an eNB, the consent type of a user corresponding to the selected terminal and sending the MDT task activation command to the selected terminal according to the check result of the consent type, comprise:
checking, by the eNB, whether local conditions meet the limitation of the geographical area andor duration in the consent type;
if the check result is that the local conditions meet the limitation of the geographical area andor duration in the consent type, determining, by the eNB, that the consent type requirement is valid, and sending, by the eNB, an MDT task activation command to a terminal executing the MDT task according to the check result of the consent type; or
if the check result is that the local conditions do not meet the limitation of the geographical area andor duration in the consent type, determining, by the eNB, that the consent type is invalid and all check results based on the consent type are negative; reporting, by the eNB, the check failure and a failure type number to an MDT data collection device; sending, by the eNB, an MDT task activation command to a terminal executing the MDT task according to a consent type that passes the check.
18. A network element comprising:
an evolved Node B (eNB), comprising:
a checking module, configured to: in a process of activating a minimization of drive tests (MDT) task, check, a consent type of a user corresponding to a selected terminal, wherein the consent type of the user comprises a consent type of the user indicating whether the terminal user agrees to report position information andor a desired positioning mode for the MDT task if the terminal user agrees to execute the MDT task, wherein the desired positioning mode comprises one of a mode of GPS and a mode of obtaining position information by cell position; and
an executing module, configured to: send an MDT task activation command to the selected terminal according to a check result of the consent type; and after receiving measured data reported by the terminal, execute an operation according to the check result of the consent type, wherein the consent type of the user further comprises a limitation of a geographical area andor duration, wherein modules configured to check, by the eNB, the consent type of a user corresponding to the selected terminal and send the MDT task activation command to the selected terminal according to the check result of the consent type, further configured to:
check, by the eNB, whether local conditions meet the limitation of the geographical area andor duration in the consent type;
if the check result is that the local conditions meet the limitation of the geographical area andor duration in the consent type, determine, by the eNB, that the consent type requirement is valid, and send, by the eNB, an MDT task activation command to a terminal executing the MDT task according to the check result of the consent type; or
if the check result is that the local conditions do not meet the limitation of the geographical area andor duration in the consent type, determine, by the eNB, that the consent type is invalid and all check results based on the consent type are negative; report, by the eNB, the check failure and a failure type number to an MDT data collection device; send, by the eNB, an MDT task activation command to a terminal executing the MDT task according to a consent type that passes the check.
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 safety switch comprising a transverse cam, a sliding cam which acts on the transverse cam to move it from a first position in which said transverse cam enables a power supply to a second position in which said transverse cam acts to cut said power supply, wherein said sliding cam has connecting means to connect to a cable, tension means to provide a predetermined tension in a connected cable and moving means to move said sliding cam when said applied predetermined tension varies, wherein said sliding cam is moveable in a first plane and said transverse cam movement is in a second plane transversely disposed to said first plane, and wherein the switch further comprises means to releasably retain the transverse cam in said first or second position and the means to retain comprises at least one fixed structure comprising at least one detent or spring loaded plunger, the other of which is carried on a surface of the transverse cam, with the spring loaded plunger being adapted to be releasably retained in the detent.
2. A safety switch according to claim 1, wherein there are two pairs of oppositely disposed detents which are spaced apart in a plane parallel to said second plane, and a pair of oppositely disposed said plungers, wherein in said first position of said transverse cam the oppositely disposed plungers extend into a respective first of said pair of detents and in said second position the plungers extend into respective said second pair of said detents.
3. A safety switch according to claim 2, wherein the second pair of detents are arranged so as to be deeper than said first pair.
4. A safety switch according to claim 1, wherein the means to releasably retain the transverse cam in the second position comprises mating abutments on the sliding cam and the transverse cam which are adapted to be aligned to prevent movement of the transverse cam when the sliding cam is moved when applied tension is varied and move out of aligned enabling movement of the transverse cam when said predetermined tension is restored.
5. A safety switch according to claim 1, wherein the switch is provided with a manually operable reset plunger which act on the transverse cam in the opposite direction to the sliding cam.
6. A safety switch according to claim 1, in which the switch is provided with an emergency stop button which has means to move the transverse cam to said second position thereof.
7. A safety switch according to claim 6, wherein the transverse cam has a protrusion and the emergency button has means to act on said protrusion.
8. A safety switch according to claim 6, wherein the switch is provided with at least two mountings for said emergency button.
9. A safety switch according to claim 1, wherein the connecting and moving means includes a shaft on which the sliding cam is mounted.
10. A safety switch according to claim 9, wherein an eyelet is mounted to the shaft.
11. A safety switch according to claim 9, wherein the shaft is spring loaded to provide said tension means.
12. A safety switch according to claim 1, wherein the means to enable the power supply comprises an abutment profile on the surface of the transverse cam for the switching mechanaism.
13. A safety switch according to claim 12, wherein the switching mechanism is of the type comprising a contact block wherein the switching contact is a spring loaded plunger.
14. A safety switch according to claim 12, wherein the switching contact is a spring loaded plunger of a contact block which is biased for movement out of the contact block, wherein said abutment profile has means to move the plunger into the contact block when in said first or second position of the transverse cam.
15. A safety switch according to claim 13, wherein the spring loaded plunger is biased out of the contact block to enable power to be supplied, said power being cut when the plunger is moved into the contact block, wherein the means on the abutment profile to move the plunger into the contact block operates the plunger when the transverse cam is in said second position.
16. A safety switch according to claim 12, wherein the switch incorporates said switching mechanism.
17. A safety switch according to claim 1, wherein the surface of the sliding cam or transverse cam facing the other of the transverse cam or sliding cam has an abutment profile comprising a well with ramped sides, whilst the other of the transverse cam or sliding cam has a projection which extends into the well when the transverse cam is in said first position, wherein said means to move said sliding cam is adapted to move the sliding cam in a first direction in said plane when said cable tension exceeds said predetermined tension and enable the projection to abut a first of the ramped sides to move the transverse cam to said second position, and said means is adapted to move the sliding cam in the opposite direction in said plane when said cable tension is less than said predetermined tension and to enable the projection to abut the second of the ramped sides to move the transverse cam to said second position.
18. A safety switch as claimed in claim 17 wherein the rim of the well provides the or a mating abutment which prevents movement of the transverse cam to the first position by blocking movement of the protection back into the well.
19. A safety switch according to claim 1, further comprising two of said sliding cams each of which can act on the transverse cam to move it from its said first to second position, each sliding cam having respective connecting means to connect to a respective cable and respective moving means.