Master TSM
A master TSM is provided. The master TSM intermediates between entities connected to different TSMs by connecting the TSMs via an interface module which is communicable with a plurality of TSMs. Accordingly, interoperability is possible between entities and clients connected to different TSMs and thus a variety of services can be provided. Therefore, conveniences for all of the entities and clients can be guaranteed from the information processing and service providing aspects.
1. A mobile terminal having a master Trusted Service Manager (TSM), the master TSM comprising:
an interface module configured to communicate with a plurality of TSMs; and a management module configured to connect a first TSM and a second TSM to each other via the interface module, and to intermediate between a first entity connected to the first TSM and a second entity connected to the second TSM; and
a Post Issuance Processor (PIP) module operable to provision information into the mobile terminal by transmitting and receiving messages contained in Application Protocol Data Units (APDUs),
wherein the first TSM is not able to directly access the second entity of the second TSM without passing through the management module,
wherein the second TSM is not able to directly access the first entity of the first TSM without passing through the management module; and
wherein the first TSM provides one or more shared keys to the management module, the shared keys allowing the second entity connected to the second TSM access the shared keys through the management module to conduct one or more transactions with the first entity without being connected to the first TSM.
2. The mobile terminal of claim 1 , wherein the first TSM and the second TSM are owned and operated by different entities.
3. The mobile terminal of claim 1 , wherein the first TSM and the second TSM use different data formats, and
wherein the management module converts the data format used by the first TSM to the data format used by the second TSM, allowing the first TSM to communicate with the second TSM.
4. The mobile terminal of claim 1 , wherein the management module intermediates between the first TSM connected to the first entity and the second TSM connected to the second entity by connecting the first TSM and the second TSM to each other via the interface module by storing and referring to information on the TSMs and information on entities connected to each TSM.
5. The mobile terminal of claim 4 , wherein the management module does not transmit information on the second TSM to the first TSM, and does not transmit information on the first TSM to the second TSM.
6. The mobile terminal of claim 5 , wherein the master TSM operates as the second entity for the first entity, and operates as the first entity for the second entity.
7. The mobile terminal of claim 4 , wherein, when a new TSM is additionally able to communicate, the management module acquires information on the new TSM and information on main entities connected to the TSM.
8. The mobile terminal of claim 1 , wherein the management module intermediate between the first entity connected to the first TSM and a third entity connected to a third TSM by connecting the first TSM and the third TSM to each other via the interface module, and wherein the management module may not intermediate between the second entity connected to the second TSM and the third entity connected to the third TSM, without connecting the second TSM and the third TSM to each other via the interface module.
9. The mobile terminal of claim 1 , wherein the management module relays a certain number of services between the first entity connected to the first TSM and the second entity connected to the second TSM, and does not relay rest of remaining services.
10. The mobile terminal of claim 1 , wherein the first TSM is able to directly access a fourth entity connected to a fourth TSM via the fourth TSM without passing through the management module.
11. The mobile terminal of claim 1 , further comprising a reporting module configured to report on intermediation-related information and intermediation refusal-related information between the first entity connected to the first TSM and the second entity connected to the second TSM.
12. The mobile terminal of claim 1 , further comprising a route management module including a routing table operable to store route information for each TSM, the route information including one or more of a network address, port address, or security access key.
13. The mobile terminal of claim 1 , further comprising a data preparation module operable to determine whether a data format for sending to a receiving TSM is compatible for the receiving TSM.
14. The mobile terminal of claim 13 , wherein the data formats are one of ADPU format, Data Grouping Identifier (DGI) format, or raw data format.
15. The mobile terminal of claim 1 , wherein the interface module is further configured to communicate with one or more connected entities, the connected entities including the TSMs, service providers, Mobile Network Operators (MNOs), or secure elements, and further comprising a relationship management module operable to store connection information of each TSM, service provider, MNO, and secure element.
16. A computer-implemented method for intermediating between connected entities within a mobile communication network, the method comprising:
connecting a first TSM and a second TSM to each other via an interface module which is able to communicate with a plurality of TSMs;
intermediating, via a management module, between a first entity connected to the first TSM and a second entity connected to the second TSM; and
storing, in a routing table, route information for each entity the route information for each entity includes one or more of a network address, port address, or security access key,
wherein the first TSM is not able to directly access the second entity of the second TSM without the intermediating,
wherein the second TSM is not able to directly access the first entity of the first TSM without the intermediating; and
wherein the first TSM provides one or more shared keys to the management module, the shared keys allowing the second entity connected to the second TSM access the shared keys through the management module to conduct one or more transactions with the first entity without being connected to the first TSM.
17. The method of claim 16 , wherein the connected entities include one or more service providers, Mobile Network Operators (MNOs), or secure elements.
18. The method of claim 16 , further comprising determining a data format and determining whether data transfer is compatible between separate TSMs based on the determined data format.
19. The method of claim 18 , further comprising determining a data format in accordance with format requirements of a receiving entity.
20. The method of claim 19 , wherein the data formats are one of ADPU format, Data Grouping Identifier (DGI) format, or raw data format.