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.