Adaptive Mutual Trust Model for Dynamic and Diversified Multi-Domain Networks

Abstract

Provided is an entity that creates an adaptive trust model by a trust model adapter of a device. The adaptive trust model is configured to establish a trust relationship with another device based on a combination of the trust of the another device obtained from a trust evaluator of the another device and a combination of the trust of the device obtained from a trust evaluator of the device. The entity authenticates the another device based on the adaptive trust model and the policies defined in the adaptive trust model; defines access control rules for the another device based on the adaptive trust model and the policies defined in the adaptive trust model; constructs a secure channel using the another device based on the adaptive trust model and the policies defined in the adaptive trust model; and records the behavior of the another device on the device.

Description

Technical Field

[0001] Some example embodiments may generally relate to mobile or wireless telecommunications systems, such as Long Term Evolution (LTE) or Fifth Generation (5G) radio access technology or New Radio (NR) access technology, or other communication systems. For example, certain embodiments may relate to systems and / or methods for implementing an adaptive mutual trust model for a dynamic and diverse multi-domain network. Background Art

[0002] Examples of mobile or wireless telecommunications systems may include Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), Advanced LTE (LTE-A), MulteFire, LTE-A Pro, and / or Fifth Generation (5G) radio access technology or New Radio (NR) access technology. The 5G wireless system refers to the Next Generation (NG) radio system and network architecture. 5G is mainly built on New Radio (NR), while the 5G (or NG) network is also capable of being built on E-UTRA radio. It is estimated that NR provides a bit rate of about 10 - 20 gigabits or higher and is capable of supporting at least enhanced Mobile Broadband (eMBB) and Ultra-Reliable Low-Latency Communication (URLLC) as well as Massive Machine Type Communication (mMTC). NR is expected to deliver ultra-wideband and ultra-stable low-latency connectivity and massive network connections to support the Internet of Things (IoT). As IoT and Machine-to-Machine (M2M) communication become more widespread, there will be an increasing demand for a network that meets the requirements of low power, low data rate, and long battery life. The Next Generation Radio Access Network (NG-RAN) represents the RAN for 5G, which is capable of providing both NR and LTE radio access. Note that in 5G, a node that can provide radio access functionality to user equipment (i.e., similar to Node B in UTRAN or eNB in LTE) may be called a gNB when built on NR radio and may be called an NG-eNB when built on E-UTRA radio. Summary of the Invention

[0003] According to some embodiments, a method may include: creating, by a trust model adapter of a device, an adaptive trust model configured to establish a trust relationship with another device based on a combination of trust obtained by a trust evaluator of the other device and a combination of trust obtained by a trust evaluator of the device. The method may further include applying security controls between the device and the other device.

[0004] According to some embodiments, a device may include at least one processor and at least one memory, the at least one memory including computer program code. The at least one memory and the computer program code may be configured to, with the at least one processor, cause the device to create an adaptive trust model at least by a trust model adapter of the device, the adaptive trust model being configured to establish a trust relationship with another device based on a combination of trust obtained by a trust evaluator of the other device and a combination of trust obtained by a trust evaluator of the device. The at least one memory and the computer program code may also be configured to, with the at least one processor, cause the device to apply security controls at least between the device and another device.

[0005] According to some embodiments, a device may include means for creating an adaptive trust model by a trust model adapter of the device, the adaptive trust model being configured to establish a trust relationship with another device based on a combination of trust of the other device and a combination of trust of the device. The device may also include means for applying security controls between the device and another device.

[0006] According to some embodiments, a non-transitory computer-readable medium may be encoded with instructions that, when executed in hardware, perform a method. The method may create an adaptive trust model by a trust model adapter of the device, the adaptive trust model being configured to establish a trust relationship with another device based on a combination of trust obtained by a trust evaluator of the other device and a combination of trust obtained by a trust evaluator of the device. The method may also apply security controls between the device and another device.

[0007] According to some embodiments, a method may include: creating an adaptive trust model by a trust model adapter of the device, the adaptive trust model being configured to establish a trust relationship with another device based on a combination of trust obtained by a trust evaluator of the other device and a combination of trust obtained by a trust evaluator of the device. The method may also include applying security controls between the device and another device. The method may also include receiving an indication of a change of the other device from the other device. The method may also include obtaining a new trust model and establishing a new trust relationship to reflect the new trust combination based on the change.

[0008] According to some embodiments, a device may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured to, with the at least one processor, cause the device to create an adaptive trust model at least by a trust model adapter of the device, the adaptive trust model being configured to establish a trust relationship with another device based on a combination of trust obtained by a trust evaluator of the other device and a combination of trust obtained by a trust evaluator of the device. The at least one memory and the computer program code may also be configured to, with the at least one processor, cause the device to apply security controls at least between the device and another device. The at least one memory and the computer program code may also be configured to, with the at least one processor, cause the device to receive at least an indication of a change of another device from the other device. The at least one memory and the computer program code may also be configured to, with the at least one processor, cause the device to obtain at least a new trust model and establish a new trust relationship to reflect a new trust combination based on the change.

[0009] According to some embodiments, a device may include: means for creating an adaptive trust model by a trust model adapter of the device, the adaptive trust model being configured to establish a trust relationship with another device based on a combination of trust obtained by a trust evaluator of the other device and a combination of trust obtained by a trust evaluator of the device. The device may also include means for applying security controls between the device and another device. The device may also include means for receiving an indication of a change of another device from the other device. The device may also include means for obtaining a new trust model and establishing a new trust relationship to reflect a new trust combination based on the change.

[0010] According to some embodiments, a non-transitory computer-readable medium may be encoded with instructions that, when implemented in hardware, implement a method. The method may create an adaptive trust model by a trust model adapter of a device, the adaptive trust model being configured to establish a trust relationship with another device based on a combination of trust obtained by a trust evaluator of the other device and a combination of trust obtained by a trust evaluator of the device. The method may also apply security controls between the device and another device. The method may also receive an indication of a change of another device from the other device. The method may also obtain a new trust model and establish a new trust relationship to reflect a new trust combination based on the change. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Reference should be made to the accompanying drawings to correctly understand the example embodiments, where:

[0012] Figure 1 An example network is illustrated;

[0013] Figure 2 An example zero-touch service and network management framework reference architecture is illustrated;

[0014] Figure 3 Illustrates an example zero - touch service and a network - management - based multi - domain management system;

[0015] Figure 4 Illustrates an example block diagram of a model according to an embodiment;

[0016] Figure 5 Illustrates an example block diagram of a model according to an embodiment;

[0017] Figure 6 Illustrates an example flowchart of a method according to an embodiment; and

[0018] Figure 7 Illustrates an example block diagram of an apparatus according to an embodiment. Detailed Description of the Invention

[0019] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for implementing an adaptive mutual - trust model for a dynamic and diverse multi - domain network is not intended to limit the scope of certain embodiments, but rather represents selected example embodiments.

[0020] The features, structures, or characteristics of the example embodiments described throughout this specification can be combined in any suitable manner in one or more example embodiments. For example, the use of phrases such as "certain embodiments", "some embodiments", or other similar language throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with the embodiments can be included in at least one embodiment. Thus, the appearances of the phrases "in certain embodiments", "in some embodiments", "in other embodiments", or other similar language throughout this specification do not necessarily all refer to the same set of embodiments, and the described features, structures, or characteristics can be combined in any suitable manner in one or more example embodiments.

[0021] Additionally, if necessary, the different functions or processes discussed below can be executed in a different order and / or simultaneously with each other. Furthermore, if necessary, one or more of the described functions or processes can be optional or can be combined. Thus, the following description should be regarded only as illustrative of the principles and teachings of certain example embodiments and not as a limitation thereof.

[0022] Figure 1 Shows an example 5G ecosystem 100 and its technological breakthroughs, such as network slicing, software - driven, and service - based architectures, which enable new business models and value creation across multiple industry domains 101, including vertical industries, mobile network operators, infrastructure service providers, and application providers.

[0023] The disruptive deployment of 5G networks triggers the need for network transformation and fundamental changes in the way networks and services are managed and orchestrated. Figure 2 An example of Zero Touch Service and Network Management (ZSM) 200 is shown, which is a fully end-to-end automation of network and service management frameworks and solutions, designed to manage and orchestrate future services and networks (including 5G networks).

[0024] Mutual trust should be established among entities within a domain or across different domains before they interact with each other for service reservation and consumption, as well as for service, network management, and orchestration, so as to ensure the credibility, integrity, availability, and compliance of each entity.

[0025] To build trust relationships among different entities, traditionally, several trust models are defined to establish trust relationships among different entities, which allow an entity to obtain the trust level required for forming partnerships, collaborating with other organizations, sharing information, or receiving information / services. Conventional trust models are defined in NIST 800-39, including verification trust, direct historical trust, mediated trust, mandatory trust, and hybrid trust. In addition, the European Telecommunications Standards Institute (ETSI) Network Function Virtualization (NFV) breaks down transfer trust into several more refined models, such as direct delegation trust, collaboration trust, transfer trust, and reputation trust. Those trust models can be statically applied to various entities to build different trust levels.

[0026] ETSI NFV introduces the concept of dynamism. However, it still focuses on the relationship between VNF and service virtual infrastructure and always regards virtual infrastructure components (such as TPM on HW), management and orchestration (MANO) entities, or certificate authorities (CA) as the trust root to build a static transfer / collaboration trust model for VNF or MANO entities. Therefore, due to the dynamism of the NFV ecosystem, NFV does not provide a solution to handle potential trust model conversions.

[0027] Figure 1 Illustrated is the openness of the 5G ecosystem 100 involving players from multiple industry domains 101 (such as enterprises, finance, government, network scale, operators, and cloud providers). The trust levels required by different domains vary, and the trust levels of the same domain in different contexts can also be different. Additionally, a cloud-native service-based architecture is adopted by ZSM to facilitate the rapid deployment and update of services, thus meeting the diverse needs of various vertical consumers. The trust context and relationship between management functions within the same domain or different domains can change dynamically with changes in the management functions themselves, their consumers, or their producers.

[0028] The dynamics and diversity of 5G networks and the ZSM framework render existing trust models (either a single trust model or a combination of multiple trust models) insufficient to ensure the credibility, integrity, and availability of 5G network and ZSM services and data.

[0029] Figure 3 An example of a trust relationship 300 between a management function (MnF) C1 301 in the 5G core management domain (MnD) 302 and an MnF V1 303 in the NFV MnD 304 is shown, where the trust relationship between an MnF R1 305 in the 5G RAN MnD 306 and the MnF V1 303 in the NFV MnD 304 can be different because the trust capabilities and assurances of the 5G core MnD 302 and the 5G RAN MnD 306 are different. Additionally, the trust relationship between MnF C1 301 and MnF V1 303 can change from time to time because of changes in MnFs (such as the operational state and security posture of the MnF, packaging upgrades to support new features, scaling to other regions, etc.), its service consumers (such as new consumers from new industry domains, such as large-scale), and its service producers (such as damage to service producers). All of the existing trust models mentioned above cannot be used individually and statically to meet the basic security assurance requirements of the system.

[0030] Figure 4 The figure illustrates an example block diagram of a model according to certain embodiments. As Figure 4 illustrated, examples of certain embodiments introduce a reflection and adaptive mutual trust model 400 to adapt to the dynamics and diversity of 5G network connections and the ZSM framework with a centralized trust evaluator and distributed trust adapters.

[0031] The adaptive mutual trust model 400 may include a trust evaluator 402 based on common knowledge, which acts as an intelligent function block (FB) to evaluate the credibility of cross-domain entities based on an entity's risk chain, trust profile, trust assurance, and other context data.

[0032] A trust evaluator 401 based on distributed knowledge can act as an intelligent FB of the 400 of the adaptive mutual trust model to evaluate the credibility of inter-domain entities based on an entity's risk chain, trust profile, trust assurance, and other context data. One or more trust evaluators can exist in a single domain.

[0033] A trust model adapter 404 based on common knowledge can act as an intelligent FB of the 400 of the adaptive mutual trust model to create trust relationships and trust models between two inter-domain entities based on the trust combination from the trust evaluator.

[0034] The trust model adapter 403 based on distributed knowledge can act as the intelligent FB of the adaptive mutual trust model 400 to create trust relationships and trust models between entities across / domains within two domains based on the trust combination from the trust evaluator. One or more trust model adapters can exist in a single domain.

[0035] The trust combination can be information evaluated by the trust evaluator based on the analysis of the risk chain, trust profile, trust guarantee, and other context data of the entity. The entity can be a service consumer or a service provider or both.

[0036] Figure 5 An example of the functional blocks of the adaptive trust model 500 according to an embodiment is illustrated. Some embodiments provide that the trust evaluator A 502 or the trust evaluator B 507 can be combined with the common trust evaluator 511; the trust model adapter A 503 or the trust model adapter B 508 can be combined with the common trust model adapter 512.

[0037] In some embodiments, the workflow of the adaptive mutual trust model between diverse entities in a dynamic 5G network and a network management system can include the trust model adapter A 503 of the entity A 501 creating an adaptive trust model to establish a trust relationship with the entity B 506 based on the combination of the trust of the entity B 506 and the trust of the entity A 501.

[0038] Based on the trust model and the relevant policies defined in the trust model, the entity A 501 can apply security controls between the device and another device (such as the authentication entity B 506), can define the access control rules of the entity B 506, can utilize the entity B 506 to construct a secure channel, and can record the behavior of the entity B 506 on the entity A 501.

[0039] The entity A 501 and the entity B 506 can be service consumers, service providers, or both. The created trust model can be a verification / direct trust model, a mediated / transferred trust model, a forced trust model, and / or a hybrid trust model, etc.

[0040] The combination of the trust of the entity A 501 mentioned above can be obtained by the trust evaluator A 502 of the entity A 501 according to the risk chain, trust profile, trust guarantee, and other context data of the entity A 501.

[0041] The combination of the trust of the entity B 506 mentioned above can be obtained by the trust evaluator of the entity A 501 according to the risk chain, trust profile, trust guarantee, and other context data of the entity B 506, or directly received from other trusted entities.

[0042] The risk chain mentioned above can be obtained by the trust evaluator of an entity based on the trust profile of the entity, trust assurance, and other service consumer context data chains and service producer chains.

[0043] The service consumer chain discussed above can be a list of the service consumers of an entity including the entity's direct consumers and the consumers of its consumers. A service consumer can be a management function, network function, tenant, operator, or any software or human entity.

[0044] The service producer chain mentioned above can be a list of the service producers of an entity including the entity's direct producers and the producers of its producers. A service producer can be a management function, network function, operator, or any software or hardware.

[0045] The trust profile mentioned above can define the security characteristics (such as security threats and risks, applied countermeasures, security policies, procedures, etc.) and security capabilities (such as available security functions, etc.) of an entity. The trust profile can change according to the following: upgrade, scaling of the entity, or addition / removal / update of the services provided by the entity, addition / removal / change of the entity's consumers or producers, change in the security state and threat surface of the entity itself or its consumers or producers, change in the entity's policies or procedures, etc.

[0046] Trust assurance can define the ability and level of security implementation, verification, monitoring, and compliance of an entity. Trust assurance can change dynamically based on changes in the entity or changes in its trust profile, etc.

[0047] Similarly, the trust model adapter B 508 of entity B 506 can create an adaptive trust model to establish a trust relationship with entity A 501 based on the trust combination of entity B 506 and entity A 501.

[0048] If there is a change in entity A 501, then the trust evaluator A 502 can obtain the new trust combination of entity A 501 based on the change in entity A 501, and can directly or indirectly notify entity B 506 of the change in entity A 501 based on the trust model between entity A 501 and entity B 506.

[0049] To reflect the new trust combination of entity A 501, the trust model adapter A 503 can update / delete the trust model and / or establish a new trust relationship or delete the trust relationship with entity B 506. Similarly, to reflect the change in entity A 501, the trust model adapter B 508 of entity B 506 can update / delete the trust model and / or establish a new trust relationship or delete the trust relationship with entity A 501.

[0050] The changes to the above-mentioned entity A 501 may include entity upgrades, scaling, movement, security status changes, adding / removing the consumers / producers of the entity, changes to the security context of its consumers or producers, changes to the threat surface associated with the entity, and changes to the security policies or procedures associated with the entity, etc.

[0051] Based on the trust model between entity A 501 and entity B 506, the changes to entity A 501 received by entity B 506 include the updated trust portfolio or updated risk chain of entity A 501, the trust profile of entity A 501, and trust assurance.

[0052] Based on the new trust model and the relevant policies defined in the new trust model, entity A 501 and entity B 506 can apply security controls between a device and another device (such as authenticating another entity), define access control rules for another entity, use another entity to build a secure channel, and / or record the behavior of another entity.

[0053] In an example scenario, a trust relationship is established between entity A 501 and entity B 506. As a prerequisite, the management system is a system with a service-based management architecture (SBMA) (such as a system based on the ETSI ZSM framework, a network management system defined in 3GPP Rel15, etc.) or a network with a service-based architecture (SBA) (such as the 5G core defined in 3GPP), and mutual trust should be established between the entity and the framework and between the two entities before the entity can interact with another entity to ensure the credibility, integrity, availability, and compliance of the two entities and the framework.

[0054] In this example, entity A 501 uses the services provided by entity B 506, and both entity A 501 and entity B 506 are deployed in the SBA / SBMA framework. The credibility of the evaluation framework entities (such as the common trust evaluator 511, the common trust model adapter 512) has been self-evaluated, and the relevant trust portfolio has been obtained.

[0055] A one-way trust relationship from entity A 501 and entity B 506 to the framework entities has been established (such as based on the trust root). Given this assumption, entity A 501 and entity B 506 trust the services and information provided by the framework entities (such as the common trust evaluator 511, the common trust model adapter 512, etc.) based on the established trust model, and entity A 501 and entity B 506 allow the framework entities to use their services based on the established trust model.

[0056] The public trust evaluator 511 can obtain trust-related information of an entity in the framework from a trusted third-party entity or from the entity itself after it constructs relevant trust using the entity. In an embodiment, AI / ML technologies can be used on the trust evaluator and the trust model adapter for knowledge-based evaluation and adaptation.

[0057] In an example scenario, before providing any service to entity A 501, the public trust evaluator 511 of the framework evaluates the credibility of entity A 501 based on the risk chain, trust profile, trust assurance, and other context data of entity A 501 from a trusted entity, and obtains the trust portfolio of entity A 501. The trusted entity can be a third-party entity or entity A 501 itself. The third-party entity can be hardware, software, a human, etc.

[0058] Based on the trust portfolio of the public trust evaluator 511 and the trust portfolio of entity A 501, the common trust model adapter 512 creates a relevant trust model to establish a one-sided trust relationship from the public trust evaluator to entity A 501. Similarly, the common trust model adapter 512 creates a relevant trust model to establish a one-sided trust relationship from the public trust evaluator 511 to entity B 506.

[0059] Before using any service provided by entity B 506, the trust evaluator A 502 of entity A 501 utilizes the public trust evaluator 511 to check the credibility of entity B 506. Based on the mutual trust model between entity A 501 and the public trust evaluator 511 and the mutual trust model between entity B 506 and the public trust evaluator 511, the public trust evaluator 511 returns the trust portfolio of entity B 506 to entity A 501, or returns the risk chain, trust profile, trust assurance, and other context data of entity B 506 to entity A 501. In some cases, the public trust evaluator 511 can return an error to entity A 501.

[0060] If the public trust evaluator 511 returns the risk chain, trust profile, trust assurance, and other context data of entity B 506 to entity A 501, then the trust evaluator A 502 evaluates the credibility of entity B 506 based on the risk chain, trust profile, trust assurance, and other context data of entity B 506, and obtains the trust portfolio of entity B 506.

[0061] The trust evaluator A 502 self-evaluates the credibility of entity A 501 based on the risk chain, trust profile, trust guarantee, and other context data of entity A 501, and obtains the trust portfolio of entity A 501. Based on the trust portfolio of entity B 506 and the trust portfolio of entity A 501, the trust model adapter A 503 creates relevant trust models (such as verification / direct trust, mediation / transfer trust, mandatory trust, etc.) to establish a one-way trust relationship from entity A 501 to entity B 506.

[0062] Based on the trust model and the relevant policies defined in the trust model, entity A 501 applies security controls between the device and another device (such as entity A 501 authenticating entity B 506), and uses entity B 506 to build a secure channel to access the services of entity B 506.

[0063] Before providing any services to entity A 501, the trust evaluator B 507 of entity B 506 uses the common trust evaluator 511 to check the credibility of entity A 501.

[0064] Based on the mutual trust model between entity B 506 and the common trust evaluator 511 and the mutual trust model between entity A 501 and the common trust evaluator 511, the common trust evaluator 511 returns the trust portfolio of entity A 501 to entity B 506, or returns the risk chain, trust profile, trust guarantee, and other context data of entity A 501 to entity B 506. In some cases, the common trust evaluator 511 can return an error to entity B 506.

[0065] If the common trust evaluator 511 returns the risk chain, trust profile, trust guarantee, and other context data of entity A 501 to entity B 506, then the trust evaluator B 507 evaluates the credibility of entity A 501 based on the risk chain, trust profile, trust guarantee, and other context data of entity A, and obtains the trust portfolio of entity A 501.

[0066] The trust evaluator B 507 self-evaluates the credibility of entity B 506 based on the risk chain, trust profile, trust guarantee, and other context data of entity B 506, and obtains the trust portfolio of entity B 506.

[0067] Based on the trust portfolio of entity B 506 and the trust portfolio of entity A 501, the trust model adapter B 508 creates relevant trust models (such as verification / direct trust, mediation / transfer trust, mandatory trust, etc.) to establish a one-way trust relationship from entity B 506 to entity A 501.

[0068] Based on the trust model and the relevant policies defined in the trust model, entity B 506 applies security controls between the device and another device (such as entity B 506 authenticating entity A 501), defines the access control rules for entity A 501, uses entity A 501 to build a secure channel to provide services to entity A 501, and records the behavior of entity A 501 on entity B 506.

[0069] In another example scenario, the trust relationship between entity A 501 and entity B 506 changes according to the dynamic changes of entity A 501, entity B 506, or their producers 504, 509 or consumers 505, 510.

[0070] As a prerequisite for this example, the mutual trust between entity A 501 and the public evaluator 511 has been established using a specific trust model, the mutual trust between entity B 506 and the public evaluator 511 has been established using a specific trust model, and the mutual trust between entity A 501 and entity B 506 has been established using a specific trust model.

[0071] In an embodiment, the trust relationship between entities and the relevant trust model can change dynamically based on changes in the entities. The changes in the entities can include one or more of the changes in the entity itself (e.g., entity upgrade, introduction of new features, new services, or use of new technologies, software, or hardware, etc.), the entity can be scaled or moved especially to a new geographical location, the security state of the entity can change (e.g., the entity is compromised or damaged, etc.), the context of the entity changes (e.g., adding / removing consumers / producers of the entity, adding consumers in a specific industry domain), the security context of its consumers or producers can change (e.g., the security policy of its consumers changes), the threat surface associated with the entity changes (e.g., new vulnerabilities may be exposed, or new attack patterns are made public, etc.), and / or the security policies or procedures associated with the entity can change.

[0072] In an example scenario, according to some embodiments, when there are changes in entity A 501, the trust evaluator A 502 re-evaluates the credibility of entity A 501 based on the risk chain, trust profile, trust guarantee, and other context data of entity A 501, and obtains a new trust portfolio for entity A 501.

[0073] Based on the trust relationship between entity A 501 and the public trust evaluator 511, the trust evaluator A 511 can synchronize the changes of entity A 511 using the public trust evaluator 511, and based on the trust relationship between the public trust evaluator 511 and entity A 501 and the trust relationship between the public trust evaluator 511 and entity B 506, the public trust evaluator 511 can also synchronize the changes from entity A 501 to entity B 506.

[0074] Based on the trust relationship between entity A 501 and entity B 506, trust evaluator A 502 can directly utilize entity B 506 to synchronize the changes of entity A 501.

[0075] The synchronized information can be the updated trust portfolio of entity A 501, or the updated risk chain, trust profile, trust guarantee, and other context data of entity A 501, etc.

[0076] To reflect the new trust portfolio of entity A 501, trust model adapter A 503 can update the trust models (such as verification / direct trust, mediation / transfer trust, mandatory trust, etc.) for the new trust relationship to the common trust evaluator 511 and / or entity B 506. Based on the new trust model and the relevant policies defined in the new trust model, entity A 501 applies security controls between the device and another device (such as entity A 501 authenticating entity B 506), and utilizes entity B 506 to build a secure channel to access the services of entity B 506.

[0077] If entity B 506 receives the risk chain, trust profile, and trust guarantee of entity A 501 from the common trust evaluator 511 or entity A 501, then trust evaluator B 507 re-evaluates the credibility of entity A 501 according to the updated risk chain, trust profile, and trust guarantee of entity A 501, and obtains the new trust portfolio of entity A 501. Based on the new trust portfolio of entity A 501, trust model adapter B 508 can update the trust models (such as verification / direct trust, mediation / transfer trust, mandatory trust, etc.) for the new trust relationship from entity B 506 to entity A 501.

[0078] Based on the new trust model and the relevant policies defined in the new trust model, entity B 506 applies security controls between the device and another device (such as entity B 506 authenticating entity A 501), defines the access control rules for entity A 501, utilizes entity A 501 to build a secure channel to provide services to entity A 501, and records the behavior of entity A 501 on entity B 506.

[0079] Figure 6 Illustrated is an example flowchart for implementing an adaptive mutual trust model for a dynamic and diverse multi-domain network according to an embodiment.

[0080] As Figure 6As illustrated in the example of, the method may include: at 601, creating, by a trust model adapter of a device, an adaptive trust model configured to establish a trust relationship with another device based on a combination of trust obtained by a trust evaluator of the other device and a combination of trust obtained by a trust evaluator of the device. The method may further include: at 602, authenticating the other device based on the adaptive trust model and the policies defined in the adaptive trust model, and at 603, the method may include defining access control rules for the other device based on the adaptive trust model and the policies defined in the adaptive trust model.

[0081] In an embodiment, at 604, the method may include constructing a secure channel with the other device based on the adaptive trust model and the policies defined in the adaptive trust model, and at 605, recording the behavior of the other device on the device. As shown, the method may further include authenticating the other device based on the new trust model at 606, defining access control rules for the other device based on the new trust model at 607, constructing a secure channel with the other device based on the new trust model at 608, and recording the behavior of the other device based on the new trust model at 609.

[0082] Figure 7 An example of device 10 according to an embodiment is illustrated. In an embodiment, device 10 may be a communication network, a node, host or server in a network / service management system, or serve such a network. For example, device 10 may be a communication service management function, a network slice management function, a network slice subnet management function, a network function management function, a base station, Node B, evolved Node B (eNB), 5G Node B or access point, next generation Node B (NG-NB or gNB), the CU of a gNB, a WLAN access point, an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), an authentication server function (AUSF), a network repository function (NRF), a network slice selection function (NSSF), a data management entity (e.g., UDM), or other entity associated with a radio access network, such as 5G or NR. In one example, device 10 may represent a management service provider.

[0083] As Figure 7 As illustrated in the example of, device 10 may include a processor 12 for processing information and executing instructions or operations. Processor 12 may be any type of general or special purpose processor. In fact, by way of example, processor 12 may include one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although in Figure 7A single processor 12 is shown in the apparatus 10, but multiple processors may be utilized according to other example embodiments. For example, it should be understood that in certain embodiments, the apparatus 10 may include two or more processors that may form a multiprocessor system (e.g., in this case, the processor 12 may represent a multiprocessor), and the multiprocessor system may support multiprocessing. In certain embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0084] The processor 12 may perform functions associated with the operation of the apparatus 10, which may include, for example, management and coordination as well as overall control of the apparatus 10, including processes related to the management of communication resources.

[0085] The apparatus 10 may also include or be coupled to a memory 14 (internal or external), which may be coupled to the processor 12 for storing information and instructions that may be executed by the processor 12. The memory 14 may be one or more memories and of any type suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 14 can include any combination of random access memory (RAM), read only memory (ROM), static storage devices (such as magnetic disks or optical disks), hard disk drives (HDDs), or any other type of non-transitory machine or computer-readable medium. The instructions stored in the memory 14 may include program instructions or computer program code that, when executed by the processor 12, cause the apparatus 10 to perform the tasks described herein.

[0086] In an embodiment, the apparatus 10 may also include or be coupled to (internal or external) a drive or port configured to accommodate and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store computer programs or software for execution by the processor 12 and / or the apparatus 10.

[0087] In an embodiment, the memory 14 may store software modules that provide functionality when executed by the processor 12. The modules may include, for example, an operating system that provides operating system functionality for the apparatus 10. The memory may also store one or more functional modules (such as applications or programs) to provide additional functionality for the apparatus 10. The components of the apparatus 10 may be implemented in hardware or as any suitable combination of hardware and software.

[0088] According to some embodiments, the processor 12 and the memory 14 may be included or may form part of a processing circuitry or a control circuitry. Additionally, in some embodiments, the transceiver 18 may be included or may form part of a transceiver circuitry.

[0089] As used herein, the term "circuitry" may refer to a pure hardware circuitry implementation (e.g., analog and / or digital circuitry), a combination of hardware circuitry and software, a combination of analog and / or digital hardware circuitry and software / firmware, any part of (a) hardware processor(s) and software (including digital signal processors) that work together to cause a device (e.g., device 10) to perform various functions, and / or (a) hardware circuitry and / or (a) processor(s) or part(s) thereof that use software for operation but where the software may be absent when not needed for operation. As another example, as used herein, the term "circuitry" may also cover an implementation that includes only hardware circuitry or a processor (or processors) or part(s) of a hardware circuitry or a processor and its accompanying software and / or firmware. The term circuitry may also cover a baseband integrated circuit in, for example, a server, a cellular network node or device, or other computing or networking device.

[0090] As described above, in certain embodiments, the device 10 may be a network node or entity, such as a management service producer, etc. According to certain embodiments, the device 10 may be controlled by the memory 14 and the processor 12 to implement functions associated with any of the embodiments described herein. For example, in some embodiments, the device 10 may be configured to execute any one of the flowcharts or signal diagrams described herein (such as Figure 6 ) one or more of the processes depicted in the process.

[0091] Figure 7An example of the apparatus 20 according to an example embodiment is also illustrated. In an example embodiment, the apparatus 20 may be a node or a server associated with a radio access network, a network / service management system (such as an LTE network), 5G or NR, or other radio systems that may benefit from equivalent processes. For example, the apparatus 20 may be a communication service management function, a network slice management function, a network slice subnet management function, a network function management function, a base station, a Node B, an evolved Node B (eNB), a 5G Node B or an access point, a next-generation Node B (NG-NB or gNB), an access & mobility management function (AMF), a session management function (SMF), a user plane function (UPF), an authentication server function (AUSF), a network repository function (NRF), a network slice selection function (NSSF), and / or a DU or CU of a gNB associated with a radio access network, such as 5G or NR. In one example, the apparatus 20 may represent a client, such as a management service consumer, a network function, a network element, or a management function.

[0092] It should be understood that in some example embodiments, the apparatus 20 may include an edge cloud server as a distributed computing system, where the server and the radio node may be independent devices communicating with each other via a wireless circuit path or via a wired connection, or it may be located in the same entity communicating via a wired connection. For example, in some example embodiments where the apparatus 20 represents a gNB, it may be configured in a central unit (CU) and a distributed unit (DU) architecture that divides the gNB functionality. In this architecture, the CU may be a logical node including gNB functions such as transmitting user data, mobility control, radio access network sharing, positioning, and / or session management. The CU may control the operation of the (multiple) DUs over a control front-haul interface. Depending on the function split option, the DU may be a logical node including a subset of the gNB functions. It should be noted that those skilled in the art will understand that the apparatus 20 may include Figure 7 components or features not shown in

[0093] As Figure 7 illustrated in the example of, the apparatus 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations. The processor 22 may be any type of general-purpose or special-purpose processor. In fact, as an example, the processor 22 may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although in Figure 7A single processor 22 is shown in the apparatus 20, but in accordance with other example embodiments, multiple processors may be utilized. For example, it should be understood that in certain example embodiments, the apparatus 20 may include two or more processors that may form a multi-processor system (e.g., in this case, the processor 22 may represent a multi-processor), and the multi-processor system may support multi-processing. In certain example embodiments, the multi-processor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0094] The apparatus 20 may also include or be coupled to a memory 24 (internal or external), which may be coupled to the processor 22 for storing information and instructions that may be executed by the processor 22. The memory 24 may be one or more memories and of any type suitable for a local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 24 can include any combination of random access memory (RAM), read only memory (ROM), static storage devices (such as magnetic disks or optical disks), hard disk drives (HDDs), or any other type of non-transitory machine or computer-readable medium. The instructions stored in the memory 24 may include program instructions or computer program code that, when executed by the processor 22, cause the apparatus 20 to perform tasks as described herein.

[0095] In an example embodiment, the apparatus 20 may also include or be coupled to (internal or external) a drive or port configured to accommodate and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store computer programs or software for execution by the processor 22 and / or the apparatus 20.

[0096] In an example embodiment, the apparatus 20 may also include or be coupled to one or more antennas 25 for receiving downlink signals and for transmitting via an uplink from the apparatus 20. The apparatus 20 may also include a transceiver 28 configured to transmit and receive information. The transceiver 28 may also include a radio interface (e.g., a modem) coupled to the antennas 25.

[0097] In an example embodiment, the memory 24 stores software modules that provide functionality when executed by the processor 22. The modules can include, for example, an operating system that provides operating system functionality for the device 20. The memory can also store one or more functional modules (such as applications or programs) to provide additional functionality for the device 20. The components of the device 20 can be implemented in hardware or as any suitable combination of hardware and software. According to an example embodiment, the device 20 can optionally be configured to communicate with the device 10 via a wireless or wired communication link 70 according to any radio access technology (such as NR).

[0098] According to some example embodiments, the processor 22 and the memory 24 can be included or can form part of a processing circuitry or a control circuitry. Additionally, in some example embodiments, the transceiver 28 can be included or can form part of a transceiver circuitry.

[0099] As described above, in certain embodiments, the device 20 can be a network node or entity, such as a management service provider, etc. According to certain embodiments, the device 20 can be controlled by the memory 24 and the processor 22 to perform functions associated with any of the embodiments described herein. For example, in some embodiments, the device 20 can be configured to perform any one of the flowcharts or signal diagrams described herein (such as Figure 6 ) one or more of the processes depicted in the process.

[0100] In some example embodiments, the functionality of any one of the methods, processes, diagrams, or flowcharts described herein can be implemented by software and / or computer program code or portions of the code stored in a memory or other computer-readable or tangible medium and executed by a processor.

[0101] In some example embodiments, the device can be included or associated with at least one software application, module, unit, or entity configured to perform (multiple) arithmetic operations or configured as a program or a portion thereof (including an added or updated software routine) and executed by at least one operating processor. A program (also referred to as a program product or a computer program) including software routines, applets, and macros can be stored in any device-readable data storage medium and can include program instructions for performing specific tasks.

[0102] A computer program product may include one or more computer-executable components that are configured to perform some example embodiments when the program runs. The one or more computer-executable components may be at least one software code or a portion of the code. Modifications and configurations required to implement the functionality of the example embodiments may be performed as routines, which may be implemented as added or updated software routines. In one example, the software routines may be downloaded to a device.

[0103] As an example, the software or computer program code or a portion of the code may be in source code form, object code form, or in some intermediate form, and it may be stored in a certain type of carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of carrying the program. For example, such carriers may include recording media, computer memories, read-only memories, electro-optical and / or electrical carrier signals, telecommunication signals, and / or software distribution packages. Depending on the required processing power, the computer program may be executed in a single electronic digital computer, or it may be distributed among multiple computers. The computer-readable medium or computer-readable storage medium may be a non-transitory medium.

[0104] In other example embodiments, the functionality may be implemented by hardware or circuitry included in a device (such as device 10 or device 20), for example, by using an application-specific integrated circuit (ASIC), a programmable gate array (PGA), a field-programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality may be implemented as a signal, such as an intangible component, which can be carried by an electromagnetic signal downloaded from the Internet or other networks.

[0105] According to example embodiments, a device (such as a node, a device, or a corresponding component) may be configured as circuitry, a computer, or a microprocessor, such as a single-chip computer element, or may be configured as a chipset, which may at least include a memory for providing storage capabilities for performing arithmetic operations and / or an arithmetic processor for performing arithmetic operations.

[0106] Thus, certain example embodiments provide several technical improvements, enhancements, and / or advantages over existing technology processes and constitute at least an improvement in the technical field of wireless network control and management. For example, according to certain embodiments, the trust model can be applied to dynamic and / or multi-domain networks. Thus, using certain example embodiments results in improved operation of communication networks and their nodes, such as base stations, eNBs, gNBs, and / or UEs or mobile stations.

[0107] Those skilled in the art will readily understand that the above exemplary embodiments can be practiced using the processes in a different order and / or using hardware elements in configurations different from the disclosed configurations. Accordingly, although some embodiments have been described based on these exemplary embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative constructions will be apparent while remaining within the spirit and scope of the exemplary embodiments.

Claims

1. A device for communication, comprising: at least one processor; and at least one memory, including computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to at least: create an adaptive trust model by a trust model adapter of the device, the adaptive trust model being configured to establish a trust relationship with the other device based on a combination of trust obtained by a trust evaluator of another device and a combination of trust obtained by a trust evaluator of the device; and apply security control between the device and the other device based on the adaptive trust model; wherein when there is a change in the device (501), the trust evaluator (503) of the device (501) is configured to, according to the change: obtain a new trust combination of the device (501); and notify the other device (506) of the change in the device (501), wherein the trust evaluator (503) of the device (501) is configured to update the adaptive trust model and establish a new trust relationship to reflect the new trust combination of the device (501).

2. The device according to claim 1, wherein either the device or the other device includes a service consumer and / or a service producer.

3. The device according to claim 1, wherein the adaptive trust model includes at least one of the following: a verification / direct trust model, a mediation / transfer trust model, a mandatory trust model, and / or a hybrid trust model.

4. The device according to claim 1, wherein the combination of the trust of the device is obtained according to at least one of the following: the risk chain of the device, the trust profile of the device, the trust guarantee of the device, and the context data of the device.

5. The device according to claim 1, wherein the combination of the trust of the other device is one of the following: obtained according to at least one of the following: the risk chain of the other device, the trust profile of the other device, the trust guarantee of the other device, and the context data of the other device; or received from other trusted entities.

6. The device according to claim 1, wherein each risk chain is obtained by the trust evaluator of each corresponding device according to the following items: each trust profile of each corresponding device, each trust guarantee of each corresponding device, the service consumer context data chain of each corresponding device, and the service producer context data chain of each corresponding device.

7. The device according to claim 1, wherein each service consumer chain includes the service consumer of each corresponding device and a list of the consumers of the service consumer of each corresponding device.

8. The device according to claim 1, wherein each service producer chain includes the service producer of each corresponding device and a list of the producers of the service producer of each corresponding device.

9. The apparatus according to claim 1, wherein each trust profile defines the security characteristics and security capabilities of each corresponding apparatus, and each trust profile is configured to be changed according to at least one of the following: upgrade, scaling of each corresponding apparatus, or change in the service provided by each corresponding apparatus, change in the service consumer of each corresponding apparatus, change in the service producer of each corresponding apparatus, change in the security state and threat surface of each corresponding apparatus, change in the policy / procedure of each corresponding apparatus.

10. The apparatus according to claim 1, wherein each trust assurance defines the ability of security implementation, the level of security implementation, verification of each corresponding apparatus, monitoring of each corresponding apparatus, and compliance of each corresponding apparatus, and each trust assurance is configured to be dynamically changed based on the change of each corresponding apparatus or the change of each trust profile of each corresponding apparatus.

11. The apparatus according to claim 1, wherein each of the trust model adapters is configured to obtain a new trust model and establish a new trust relationship to reflect the new trust combination.

12. The apparatus according to claim 1, wherein the change of the apparatus includes at least one of the following: upgrade, scaling, movement, change of security state of the apparatus, addition / removal of the consumer or producer of the apparatus, change of the security context of its consumer or producer, change of the threat surface associated with the apparatus, and change of the security policy or procedure associated with the apparatus.

13. The apparatus according to claim 1, wherein the change of the apparatus notified includes at least one of the following: updated trust combination of the apparatus, updated risk chain, updated trust profile, and updated trust assurance.

14. The apparatus according to claim 11, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to, based on the new trust model, at least: authenticate the other apparatus, define access control rules for the other apparatus, utilize the other apparatus to construct a secure channel, and record the behavior of the other apparatus.

15. The apparatus according to claim 1, wherein each of the trust model adapters is configured to delete the trust model and terminate the trust relationship with the other apparatus when the trust level is zero based on the new trust combination or when the other apparatus is terminated.

16. An apparatus for communication, comprising: at least one processor; and at least one memory, including computer program code, the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least: create an adaptive trust model by a trust model adapter of the apparatus, the adaptive trust model being configured to establish a trust relationship with the other apparatus according to the combination of trust obtained by a trust evaluator of the other apparatus and the combination of trust obtained by a trust evaluator of the apparatus; apply security control between the apparatus and the other apparatus based on the adaptive trust model; Receive an indication of a change of the other device from the other device; Obtain a new trust model and establish a new trust relationship to reflect a new trust combination based on the change; Wherein when there is a change in the device (501), the trust evaluator (503) of the device (501) is configured to, according to the change: Obtain a new trust combination of the device (501); And Notify the other device (506) of the change of the device (501), wherein the trust evaluator (503) of the device (501) is configured to update the adaptive trust model and establish a new trust relationship to reflect the new trust combination of the device (501).

17. A communication method, Comprising: Creating an adaptive trust model by a trust model adapter of a device, the adaptive trust model being configured to establish a trust relationship with the other device based on a combination of trust obtained by a trust evaluator of the other device and a combination of trust obtained by a trust evaluator of the device; And Applying security control between the device and the other device based on the adaptive trust model; Wherein when there is a change in the device (501), the trust evaluator (503) of the device (501) is configured to, according to the change: Obtain a new trust combination of the device (501); And Notify the other device (506) of the change of the device (501), wherein the trust evaluator (503) of the device (501) is configured to update the adaptive trust model and establish a new trust relationship to reflect the new trust combination of the device (501).

18. The method according to claim 17, wherein either the device or the other device includes a service consumer and / or a service producer.

19. The method according to claim 17, wherein the adaptive trust model includes at least one of the following: a verification / direct trust model, a mediation / transfer trust model, a mandatory trust model, and / or a hybrid trust model.

20. The method according to claim 17, wherein the combination of the trust of the device is obtained according to at least one of the following: the risk chain of the device, the trust profile of the device, the trust guarantee of the device, and the context data of the device.

21. The method according to claim 17, wherein the combination of the trust of the other device is one of the following: Obtained according to at least one of the following: the risk chain of the other device, the trust profile of the other device, the trust guarantee of the other device, and the context data of the other device; or Received from other trusted entities.

22. The method according to claim 17, wherein each risk chain is obtained by the trust evaluator of each corresponding device according to the following items: each trust profile of each corresponding device, each trust guarantee of each corresponding device, the service consumer context data chain of each corresponding device, and the service producer context data chain of each corresponding device.

23. The method according to claim 17, wherein each service consumer chain includes a list of service consumers of each corresponding device and consumers of the service consumers of each corresponding device.

24. The method according to claim 17, wherein each service producer chain includes a list of service producers of each corresponding device and producers of the service producers of each corresponding device.

25. The method according to claim 17, wherein each trust profile defines the security characteristics and security capabilities of each corresponding device, and each trust profile is configured to be changed according to at least one of the following: upgrade, scaling of each corresponding device, or change of the service provided by each corresponding device, change of the service consumers of each corresponding device, change of the service producers of each corresponding device, change of the security state and threat surface of each corresponding device, change of the policy / procedure of each corresponding device.

26. The method according to claim 17, wherein each trust assurance defines the ability of security implementation, the level of security implementation, verification of each corresponding device, monitoring of each corresponding device, and compliance of each corresponding device, and each trust assurance is configured to be changed dynamically based on the change of each corresponding device or the change of each trust profile of each corresponding device.

27. The method according to claim 25, wherein each of the trust model adapters is configured to obtain a new trust model and establish a new trust relationship to reflect the new trust combination.

28. The method according to claim 25, wherein the change of the device includes at least one of the following: upgrade, scaling, movement, change of the security state of the device, addition / deletion of the consumers or producers of the device, change of the security context of its consumers or producers, change of the threat surface associated with the device, and change of the security policy or procedure associated with the device.

29. The method according to claim 25, wherein the change of the notified device includes at least one of the following: updated trust combination, updated risk chain, updated trust profile, and updated trust assurance of the device.

30. The method according to claim 26, wherein the method further includes: Based on the new trust model, Authenticate the other device, Define access control rules for the other device, Use the other device to construct a secure channel, and Record the behavior of the other device.

31. The method according to claim 25, wherein each of the trust model adapters is configured to delete the trust model and terminate the trust relationship with the other device when the trust level is zero based on the new trust combination or when the other device is terminated.

32. A method of communication, including: Creating an adaptive trust model by a trust model adapter of a device, the adaptive trust model being configured to establish a trust relationship with the other device according to the combination of trust obtained by a trust evaluator of the other device and the combination of trust obtained by a trust evaluator of the device; Apply security control between the device and the other device based on the adaptive trust model; Receive an indication of a change in the other device from the other device; Obtain a new trust model and establish a new trust relationship to reflect a new trust combination based on the change; The combination of the trust of the device is obtained according to at least one of the following: the risk chain of the device, the trust profile of the device, the trust guarantee of the device, and the context data of the device; Wherein when there is a change in the device (501), the trust evaluator (503) of the device (501) is configured to, according to the change: Obtain a new trust combination of the device (501); And Notify the other device (506) of the change in the device (501), wherein the trust evaluator (503) of the device (501) is configured to update the adaptive trust model and establish a new trust relationship to reflect the new trust combination of the device (501).

33. A device for communication, Comprising: Components for creating an adaptive trust model by a trust model adapter of the device, the adaptive trust model being configured to establish a trust relationship with the other device according to a combination of the trust of the other device and a combination of the trust of the device; And Components for applying security control between the device and the other device based on the adaptive trust model; Wherein when there is a change in the device (501), the trust evaluator (503) of the device (501) is configured to, according to the change: Obtain a new trust combination of the device (501); And Notify the other device (506) of the change in the device (501), wherein the trust evaluator (503) of the device (501) is configured to update the adaptive trust model and establish a new trust relationship to reflect the new trust combination of the device (501).

34. A computer-readable medium, comprising program instructions stored thereon for at least performing the following operations: Create an adaptive trust model by a trust model adapter of the device, the adaptive trust model being configured to establish a trust relationship with the other device according to a combination of the trust of the other device and a combination of the trust of the device ； And Apply security control between the device and the other device based on the adaptive trust model; Wherein when there is a change in the device (501), the trust evaluator (503) of the device (501) is configured to, according to the change: Obtain a new trust combination of the device (501); And Notify the other device (506) of the change in the device (501), wherein the trust evaluator (503) of the device (501) is configured to update the adaptive trust model and establish a new trust relationship to reflect the new trust combination of the device (501).

Images