In our scheme, like the suggestion, we tend to understand revocation through change the private keys of the unrevoked users. however not like that work that trivially concatenates period of time with identity for key generation/update and needs to re-issue the entire private key for unrevoked users, we tend to propose a completely unique collusion-resistant key issue technique: we tend to use a hybrid private key for every user, during which an AND gate is concerned to connect and bound 2 sub-components, specifically the identity part and also the time component. Moreover, we tend to consider realizing revocable IBE with a semi-honest KU-CSP. To realize this goal, we tend to present a security increased construction under the recently formalized Refereed Delegation of Computation (RDoC) model.