Managing differentiated secure connectivity using intents

The intent management function translates qualitative security expectations into quantifiable requirements, addressing the lack of differentiated security management in mobile networks by enabling adaptive and efficient security control implementation, enhancing automation and observability.

WO2026240691A1PCT designated stage Publication Date: 2026-11-19TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/SE2025/050927
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-14
Filing Date
2025-10-13
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Current intent-based security management systems in mobile networks lack the ability to differentiate security requirements, monitor their fulfillment, and adapt to changing threats, particularly in complex 5G and 6G networks, failing to address functional and non-functional security requirements effectively.

Method used

Implement an intent management function (IMF) that translates qualitative security expectations into quantifiable requirements, using intent objects to determine attack surface coverage and security control metrics, enabling the implementation of differentiated security levels and adaptive security controls based on functional and non-functional requirements.

Benefits of technology

Enables goal-driven security management with increased automation, adaptability, and observability, allowing for flexible and efficient security management across different network domains, supporting various security levels and facilitating monetization of security services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure SE2025050927_19112026_PF_FP_ABST
    Figure SE2025050927_19112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure is related to a method performed by an intent management function (1218) for providing differentiated security in a mobile communication network. The method comprises receiving (1102) an intent-based security expectation associated with a qualitative goal of the security expectation, determining (1108) a non-functional requirement based on the intent objects associated with the intent-based security expectation, determining (1110) that the attack surface coverage goal is fulfilled based on an observed security control coverage metric, the security control coverage metric in turn based on implemented and expected security controls, and implementing (1112) security controls in a network node (1300) based on the security control coverage metric and the non-functional requirement.
Need to check novelty before this filing date? Find Prior Art

Description

MANAGING DIFFERENTIATED SECURE CONNECTIVITY USING INTENTSTECHNICAL FIELD

[0001] The present disclosure relates to methods and systems to manage differentiated secure connectivity using intents in a mobile communications network.BACKGROUND

[0002] Security management is defined as the continuous identification, detection and protection of security threats and reporting of the security status of Network Functions (NFs), infrastructure, and services in a Radio Access Network (RAN) during deployment and operational phases, with continuous risk and trust monitoring of the systems, to provide risk-based decisions.

[0003] The complexity of managing a mobile network such as Fifth Generation (5G) and Sixth Generation (6G) has kept increasing due to the various subsystems, technologies, and services that must be supported. Additionally, there are new emerging and evolving attacks on different computing stacks that are getting more complex, distributed, and targeted. To ensure smooth and resilient operation, proper configuration of the multitude of settings, policies, and service parameters, including those required for secure operations, is required.

[0004] Automation is an increasingly adopted solution to manage the complexity of future networks, enabling the ability to offload workload from administrators to the system itself and to reduce operational costs. Through technological enablers such as software-defined networking, virtualization, and advanced orchestration platforms, it is possible to deliver services faster and more adapted to each use case. Automated management of security activities and functions enables zero-touch security. Zero-touch security enables security operations personnel to define high-level security objectives and constraints and utilizes automation logic to interpret, translate, actuate, and maintain security goals. Additionally, automated security management offers technical means for security operations teams to overcome workforce and skills shortages.

[0005] A further important aspect of security management is to provide the capabilities to dynamically and continuously identify risks and detect threats with the main objective of reducing the mean-time-to-detect (MTTD) in order to reduce the mean-time-to-respond (MTTR), whether the response is carried out by the security team in an open-control loop manner, or the system itself executes the response in a closed-control loop way.

[0006] Additionally, the changing business and technical security goals and Key Performance Indicators (KPIs) need to be fulfilled and provide solutions to close the gap between what is expected as a goal and what is being monitored from the system. Nevertheless, simplified,automated, and scalable provisioning of security controls ensure NFs that are deployed with security controls that comply to an operator’s policy.

[0007] Intent-based management paradigm is foreseen as a main enabler to manage the security complexity and the different increasing requirements whether they are functional or nonfunctional requirements. 3GPP TS 28.312 addresses the intent driven management services for mobile networks. Leveraging intents will allow the network functions to adopt the self-protection capabilities as a characteristic of an autonomous network. The main aim is to allow the system to do the loop and analysis.

[0008] Intents for security can be used for different objectives, ranging from simplifying the deployments and design and the ability to proactively maintain the network function robust towards attacks and possible threats.SUMMARY

[0009] Various embodiments disclosed herein provide for an intent management function and a method performed by the intent management function (IMF) for providing differentiated security in a mobile communication network. An object of present disclosure is to address at least part of the above mentioned issues. A particular object of present disclosure is to consider the intent perspective into security management in a mobile communication network.

[0010] According to a first aspect, there is provided a method performed by an intent management function for providing differentiated security levels. The method comprises: receiving an intent-based security expectation associated with a qualitative goal of the security expectation; parsing the qualitative goal of the security expectation to determine intent objects associated with the intent-based security expectation, wherein the intent objects comprise one or more of a verb, target, target context, expectation, and expectation context; determining a quantifiable mapped requirement associated with an attack surface coverage goal of a mobile communications network based on the intent objects, wherein the quantifiable mapped requirement comprises coverage of one or more entry points of a system comprising one or more of: Orchestration and Management, O&M, services; Third Generation Partnership Program, 3GPP, Internet Protocol, IP, Control Plane; 3GPP IP User Plane; 3GPP Radio Control Plane; 3GPP Radio User Plane; Synchronization; or Data and Subscriber info; determining a non-functional requirement based on the intent objects associated with the intent-based security expectation; determining that the attack surface coverage goal is fulfilled based on an observed security control coverage metric, wherein the security control coverage metric is based on a function of a number of security controls implemented in the mobile communications network and a number of expectedsecurity controls for a required protection level; and implementing one or more security controls in a network node (1300) of the wireless communication system based on the security control coverage metric and the non-functional requirement.

[0011] According to a second aspect, there is provided a network node that implements an intent management function for providing differentiated security levels, the network node configured to receive an intent-based security expectation associated with a qualitative goal of the security expectation. The network node is further configured to parse the qualitative goal of the security expectation to determine intent objects associated with the intent-based security expectation, wherein the intent objects comprise one or more of a verb, target, target context, expectation, and expectation context. The network node is further configured to determine a quantifiable mapped requirement associated with an attack surface coverage goal of a mobile communications network based on the intent objects, wherein the quantifiable mapped requirement comprises coverage of one or more entry points of a system comprising one or more of: Orchestration and Management, O&M, services; Third Generation Partnership Program, 3GPP, Internet Protocol, IP, Control Plane; 3GPP IP User Plane; 3GPP Radio Control Plane; 3GPP Radio User Plane; Synchronization; Data and Subscriber info. The network node is further configured to determine a non-functional requirement based on the intent objects associated with the intentbased security expectation. The network node is further configured to determine that the attack surface coverage goal is fulfilled based on an observed security control coverage metric, wherein the security control coverage metric is based on a function of a number of security controls implemented in the mobile communications network and a number of expected security controls for a required protection level. The network node is further configured to implement one or more security controls in a network node (1300) of the mobile communications network based on the security control coverage metric and the non-functional requirement.

[0012] According to a third aspect, there is provided a computer program for providing differentiated security levels. The computer program comprises computer code which, when run on processing circuitry of a network node (1300), causes the network node to perform the method according to the first aspect.

[0013] According to a fourth aspect, there is provided a computer program product comprising a computer program according to the third aspect, and a computer readable storage medium on which the computer program is stored.

[0014] According to the present disclosure, the IMF may can receive an intent-based security expectation that includes a qualitative description of the security request, parse the request to determine intent objects and translate the intent objects into quantifiable requirements or goalssuch as an atack surface coverage metric and then a security control coverage metric based on the atack surface coverage metric, wherein the security control coverage metric is based on a number of security controls implemented in the mobile communication network and a number of expected security controls for a required protection level. The IMF can then implement the one or more security controls in a network node of the mobile communications network. Additionally, the IMF may receive an intent-based security expectation that includes a quantitative goal of the security expectation such as segmentation, robustness, security state, trust level and availability. Where the goal is observed with one or more security metrics for example, threat level metric, security control effectiveness, trust level metric, vulnerability exploitability metric and others. The IMF can then implement one or more security controls to fulfill the goal or adapt the configuration of existing controls, where the controls can be preventive, detection or response type of controls.BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0016] Figure 1 shows an exemplary mapping of qualitative expectations to quantitative expectations in accordance with some embodiments of the present disclosure;

[0017] Figure 2 shows an exemplary qualitative to quantitative goals mapping and metrics to be observed in accordance with some embodiments of the present disclosure;

[0018] Figure 3 shows an exemplary relationship between performance goals and security capabilities in accordance with some embodiments of the present disclosure;

[0019] Figure 4 shows an exemplary performance requirements with time goals and continuous values or intervals in accordance with some embodiments of the present disclosure;

[0020] Figure 5 shows an exemplary provisioning phase in accordance with some embodiments of the present disclosure;

[0021] Figure 6 shows an exemplary operations phase in accordance with some embodiments of the present disclosure;

[0022] Figure 7 shows an exemplary protection requirement on a service level modeled using TM Forum intent and security ontologies in accordance with some embodiments of the present disclosure;

[0023] Figure 8 shows an exemplary protection requirement as an expectation modeled using Third Generation Partnership Program (3GPP) intent expressions in accordance with some embodiments of the present disclosure;

[0024] Figure 9 shows an exemplary segmentation requirement on a service level modeled using TM Forum intent and security ontologies in accordance with some embodiments of the present disclosure;

[0025] Figure 10 shows an exemplary segmentation requirement on a service level modeled using 3GPP intent expressions in accordance with some embodiments of the present disclosure;

[0026] Figure 11 shows an exemplary method performed by an intent management function for providing differentiated security in accordance with some embodiments of the present disclosure;

[0027] Figure 12 shows an example of a communication system in accordance with some embodiments of the present disclosure;

[0028] Figure 13 shows a network node in accordance with some embodiments of the present disclosure; and

[0029] Figure 14 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.DETAILED DESCRIPTION

[0030] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0031] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0032] There currently exist certain challenge(s). Current work on intent-based security management only covers the domain of the architecture and different components of intents, but does not touch on requirements, even if Security Service Level Agreements (SLAs) are mentioned, it is not clear how security can be differentiated into requirements that can be observed and measured in the network and provide an objective view if the intent is fulfilled or not.

[0033] There has been discussion of the use of intent-based management for the purpose of automating network slice security in Fifth Generation (5G) networks. The work only discussed the architecture and possible method, and advantages of using intent as a management paradigm to reduce impact of attacks on network slices. However, it didn’t discuss what the requirements arethat shall govern the fulfilment or violation of the intent, nor how they can be observed or modeled as intents. Similarly, using security SLA to management transport security for network slices has been proposed, but only with regard to the flow of managing the security SLA and the components of the such method, not defining what are the security requirements that will be part of the service level objective that will be translated into actual policies or configurations nor what are the security metrics that should be observed in the environment to ensure the validation of the intent or its fulfillment.

[0034] However, there are some works that claimed to use intents for some uses cases for example network slicing, but haven’t yet provided different levels of security nor different requirements that can be used. Additionally, the work only focused on functional requirements and not discussing security performance (non-functional ) requirements.

[0035] Security SLA to provision security capabilities for network slices using and intentbased management framework has also been proposed. Provisioning of security capabilities is identified as a functional requirement, however, with no means on how to monitor or validate the intents. Additionally, the work does not cover how to achieve differentiated security SLAs for performance related requirements.

[0036] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The present disclosure proposes a method to manage security in mobile networks simply and efficiently while increasing observability on the security posture of the network functions. The techniques disclosed herein introduce the notions of differentiated secure connectivity, where they provide the enablement to manage security through different levels of security through functional requirements and be able to set requirements on the performance of the security controls and the ability to track the security posture of a network function using nonfunctional security requirements, thus transforming security management to a goal-driven management. Additionally, this enables monetization of security, where different levels of security service level agreements (SecSLAs) can be created and leveraged by Communication Service Providers (CSPs) towards their customers, for example in case of network slices.

[0037] Moreover, to simplify the management of the requirements and enable more automation and adaptation to security, the method proposes using intent-based management to efficiently and simply manage the requirements in a mobile network.

[0038] Some of the techniques disclosed herein include:

[0039] Defining differentiated security levels based on security functional requirements, which are translated into different protection coverage levels:• The protection coverage levels are mapped to the number of entry points (i.e. attack surfaces) that are protected on a network function.• The protection level is a qualitative level that can be mapped to a quantified value, denoted as attack surface coverage.• The required level is mapped into a set of expected security controls to be implemented.

[0040] Defining differentiated security levels based on security non-functional requirements:• Where this kind of requirements are related to the performance behavior of available controls.• Performance behavior can be related but not limited to, robustness of one or more attack surfaces, availability of network function, segmentation, time to detect attacks, etc.• The security performance requirements are quantitative requirements that are measurable objectively using the data collected.

[0041] Expressing the security requirements as intent models:• Simplifying the management of security requirements using intent-based management.• Expressing the requirements into intent expectations (3GPP and TM Forum).

[0042] The intent requirements are observed and monitored during runtime to ensure validation of an intent expectation:• Defining objective metrics to be monitored to ensure the fulfillment of security requirements.• Structure of intent natural language that is used as input to be translated to an intent model.

[0043] Certain embodiments may provide one or more of the following technical advantage(s). One of the advantages is the ability to define and provide differentiated secure connectivity, where different levels of security enable goal-driven security management, thus increasing the level of automation in the system to continuously and dynamically adapt to achieve the security goals. The techniques also enable the system to be proactively equipped with the suitable controls and configurations to prevent attacks or detect attacks or achieve functional requirements.

[0044] Additionally, the proposed method in the disclosure enables a mobile communications network to acquire different security levels in different domains across the network ensuringflexibility and modularity of security; for example, RAN could have different security requirements than transport than core, etc.

[0045] Different levels of granularity are also enabled, where different security requirements can be applied on different components (i.e. assets to be protected) in the same network function, where these components present sub-assets or different attack surfaces to be protected. Examples of the assets could be the platform, Control and user plane on the radio interface, operations and management interfaces, Internet Protocol (IP) control and user plane, where each of those functions may require different levels of security.

[0046] The proposed method also enables a security manager to balance security and its impact on cost where cost can be computational resources, network Key Performance Indicators (KPIs), or cost related to process (e.g., number of days to implement, number of maintenance window, reducing rollbacks, etc.).

[0047] The proposed differentiated security requirements enable monetization of security for CSPs, specifically offering different security levels for network slices.

[0048] The present disclosure proposes to manage security requirements using intent, enabling simplification and efficiency of security management where the security requirements are expressed as intent expectations and the requirements are measurable to evaluate the intent and ensure if its fulfilled or not.

[0049] The present disclosure proposes representing security requirements in a possible method to enhance the adaptation of security. The definition of security requirement is a statement of needed security functionality that ensures one of many different security properties of system is being satisfied. Security requirements are derived from industry standards, applicable laws, and a history of past vulnerabilities. Security requirements define new features or additions to existing features to solve a specific security problem or eliminate a potential vulnerability. Additionally, System security requirements define the protection capabilities provided by the system, the performance and behavioral characteristics exhibited by the system, and the evidence used to determine that the system security requirements have been satisfied.

[0050] Thus, requirements can be categorized as:• Security functional requirements define the security functions and capabilities a system should have to fulfill different security properties. Key properties to be achieved: e.g., confidentiality, isolation, integrity, privacy, authentication, detection, etc. Since functional requirements, represents preventive controls to offer protection to attack surfaces, this category will be referred to as Protection Requirements.• Security non-functional requirements focus on how security controls should perform or behave. Key properties to be achieved: robustness, control performance, detection time, mitigation impact, etc. This category will be referred to as Security Performance Requirements.

[0051] It is also proposed to manage the different security requirements using intent-based management. Where it will simplify the management, enables observability, automation and more efficiency during security operations and even design time. This disclosure provides two examples on how to express the security requirements and levels in an intent model and how they can be measured and evaluated. Although, the examples provided are related to network slicing, but the same can be applied on non-slicing use cases where the communication service provider (CSP) wants to manage the security requirements in the network with the same approach and methodology provided in this invention.

[0052] The first category of security requirements is known as functional security requirements. This is the current known set of security requirements, example of such requirements are confidentiality, integrity, availability, authentication and authorization, etc.. Eventually, the set of capabilities implemented to achieve functional requirements are used to “protect” the system. Thus, reformulating the functional requirements to goal-driven requirements, the goal to be achieved is the “Protection Coverage” required on the system.

[0053] The protection coverage level implies the number of entry points (i.e. attack surfaces) on the system that is required to be protected, additionally will infer the suitable security capabilities to be implemented to protect the attack surfaces to fulfill a need. It is important to highlight that especially in cloud deployments there are a greater number of attack surfaces, and protecting all available attack surface comes at a cost, thus providing a balance of different protection levels and cost is a needed evolution in the domain of security

[0054] Protection requirements are related to the security controls that could prevent malicious access to the different attack surfaces (i.e. entry points

[0055] The coverage of protection controls could range from protecting the perimeter and increasing the granularity level till covering all possible attack surfaces. The different levels of protection requirements can be expressed qualitatively and have quantitively mapping for objective observability.

[0056] Exemplary proposed qualitative protection levels are shown in Figure 1, where the protection levels include:a. ProtectionCoverage-Basicb. ProtectionCoverage-Enhancedc. ProtectionCoverage-Advanced

[0057] One possible definition of the different levels can be as below

[0058] Basic levels, defined as the protection level where the security capabilities that should fulfill the requirement are described as enabled by default, relatively simple to configure and don’t have severe impact on computational resource or other KPIs.

[0059] Enhanced levels, defined as the protection level where the security capabilities that should fulfill the requirement are described as they might be complex in configuring and having dependencies, but they are not expensive in terms of computational resources or require hardware support or handling

[0060] Advanced level is defined as the protection level where the security capabilities that should fulfill the requirement are described as cost expensive, complex and have dependencies or implications on other features.

[0061] As mentioned earlier, an important aspect of continuous monitoring and evaluating the security posture and state of a network function is observability, which entails collecting data and calculating a metric to sequentially evaluate if a requirement is fulfilled or not. Thus, the qualitative protection coverage requirements can be mapped into an observable quantifiable protection level that will be referred to as the Attack Surface Coverage. Each qualitative level is mapped to quantifiable value that represents the ratio of the covered attack surfaces to the total number of known attack surfaces in a network function. The attack surface coverage is fulfilled by a set of expected security controls that are configured on the network function.

[0062] Figure 1 provides an example of a possible mapping, where level protection coverage basic is mapped to a coverage of no less than 20% of the number of available attack surfaces in a network function. Where the enhanced level starts from 40%, and advanced aims to cover all or at least 80% of available attack surfaces.

[0063] Thus, the goal of a protection requirement is to either be provided as a qualitative level or by a protected. Attack surface coverage can be mathematically presented in the numerical value that represent the attack surfaces required to be below formulation:

[0065] Where 45^ presents the attack surface coverage, ASrequiredrepresents the number of attack surfaces required to be protected according to the chosen level and 4SWFrepresents the total number of available attack surfaces in a network function. This represents the value of the goal that the system needs to continuously achieve.

[0066] In order to achieve a goal, a main requirement is the ability to monitor data and observe if the goal is being fulfilled. Since each expected protection level corresponds to a set of expected controls, it is reasonable to measure level of fulfillment and implementation of the security controls to the expected controls for each level. Thus, the proposed metric is defined as Security Control Coverage (SCcy) which is defined as the number of security controls implemented to the number of expected security controls for the required protection level. A possible formulation of the metric is provided below:"

[0068] Figure 2 provides an example of the mapping between the proposed qualitative protection levels and a possible method to derive the quantified goal based on the provided mathematical model of calculating ASCv. Additionally, the table in Figure 2 provides one example of possible mapping of each protection level of the possible attack surfaces that can be covered on a RAN system for example a gNB. The attack surfaces listed in the Figure 2 are only for exemplifying purposes, it may also include other attack surfaces such as node platform.

[0069] Protection requirements can be summarized as the below:• Description: Ensure that the network function (NF) fulfills the functional security requirement by implementing and configuring the needed preventative capabilities• Observability: Security Control Coverage Metric• Differentiation levels: Hybrid (Qualitative - to - Quantitative mapping)

[0070] Non-functional requirements aim to provide more observability on the NF. They are the next step of the current view on security requirements. They shall shape the main goals and requirements for intent-based management. The non-functional requirements should eventually replace the functional requirements and become the main SecSLAs to operate and use as intents. A clear relationship exists between nonfunctional requirements and functional security capabilities. Non-functional requirements infer and deliver the security capabilities required. The functional capabilities shall be continuously monitored and updated to fulfill the goals and requirements.

[0071] Figure 2 shows an exemplary qualitative to quantitative goals mapping and metrics to be observed in accordance with some embodiments of the present disclosure.

[0072] Performance requirements are related to the performance goal and security posture. They are quantifiable requirements that ensure that the security controls are performing effectively to achieve the required goals and continuously evaluate the security posture of the underlyingsystem. Example of different security levels of performance requirements can be expressed quantitively as:• Segmentation level >40%• Radio Robustness level >60%• Mean-time-to-Detect Radio Attacks <200ms

[0073] Leveraging continuous values scale or automation time loops as guiding factors for different tiers (levels) of performance requirements:• Goals and requirements with ranges of values as constraints• Goals and requirements with time constraints, illustrated in Figure 4o ms > t <1 sec,o lsec>t<min,o t >min+

[0074] One possible example of security performance requirements can be “Robustness”. Robustness characterizes the relative strength of mechanisms which provide security services. Setting a target value for robustness allows the system to continuously monitor its environment (specifically threat environment) and evaluate the effectiveness of the security controls. Continuously assuring robustness enables a proactively secure system and allows for the adaptation of the security controls to meet threat environment changes.

[0075] Robustness can then be modeled to be inversely proportional to the potential threat levels in the network; the more threat observed on an attack surface, the less the robustness of this attack surface, an example of a mathematical model can be:i

[0076] Robustness (R) =Threat level (T)

[0077] Threat is the probable activity that can go wrong due to a given context, the context can be how exposed the attack surface is, or how mis-configured the controls that are supposed to ensure robustness are. Thus, threat is coupled to robustness.

[0078] Another possible example of security requirements can be the “Segmentation”. Segmentation in network or between network slices can be achieved a maintained by the different security controls available in a system. The segmentation is still needed even if the slices are deployed in isolated deployments (i.e. dedicated nodes). The nodes are still part of the network and can be still reachable. Ensuring segmentation through security controls allows CSPs / CSC to choose shared deployments (assuming more cost effective). Segmentation can occur at different layers of the node.

[0079] Performance requirements can be summarized as the below• Description: Ensure that the NF fulfills at any time the requested performance goal (e.g., trusted evaluation of all components, effectiveness of implemented controls, threat level calculated)• Observability: goal dependent (e.g., Threat level metric, security control effectiveness, etc..)• Differentiation levels: Quantitative.

[0080] Transforming security management towards goal-driven requirements demands a management paradigm that can express requirements as goals. Intents become the solution, as intents are declarative in nature and provide the “What” to be achieved in the network rather “how”. Intent is the formal specification of all expectations including requirements, goals and constraints given as input to the system, where the system relies on the underlying solution space to choose the right solutions to fulfill the requirements given the constraints if any

[0081] Additionally, the architecture diagrams shown in Figure 5 are illustrating one architecture option that adopts a security Intent Management Function (IMF) to specifically handle the security requirements within the domain. Another possible security intent handling option is that each of the domain IMFs are registered as handlers for security requirements and are equipped with the security capability profile. The security capability profile can include for example, the relevant security ontologies and the security metrics that can be used for observation.

[0082] Within the present disclosure, a structure of the natural language intent is used that ensures capture of the different intent objects that are needed to model the intent afterwards.

[0083] Structure is created based on how Third Generation Partnership Program and TM Forum define what is an intent model. One example of the intent natural language structure can be in the form:

[0084] <verb><target><target_context> <expectation> <expectation_context>• The verb gives an indication of whether the intent is used to deliver a set of requirements and doesn’t have continuous assurance or a continuous monitoring and assurance is required, example of verbso Deliver: used for functional requirements to deliver a set of security capabilities o Ensure: used for performance requirements to monitor and assure non-function requirementsTarget: defines which node is expected to act on this intent, if it’s a specific node or a group of nodes that is defined more by the target context. It is very dependent on the type of intent if it’s a service, resource or a NFTarget Context: provides more information on the target to apply intents on only a group of targets and not the whole network. Follow the target in its dependency towards the type of intento Locationo Cell ID, Physical IDs• Expectation: The requirement to be fulfilled by the target object• Expectation Context: If there are any conditions (validity) for the expectation to be true

[0085] An example use case is to “Deliver a secure service or slice with security capabilities”. The intent expectation to deliver an End to End (E2E) secure service fulfilled by the suitable security capabilities. The security capabilities are to be distributed and aligned across the Radio Access Network (RAN), Terrestrial Network (TN) and Core Network (CN) domains

[0086] This intent expectation simplifies the management of deploying and scaling the required security capabilities• Reducing time to deploy (i.e. a smaller number of maintenance windows scheduled) • Streamlining and reducing planning efforts

[0087] The intent of security expectations in this use case are identified as “Protection Level” requirements.

[0088] Below are possible examples of expressing protection requirements in natural language before submitting to an Intent Management Function (IMF) where it is then translated from natural language to an intent model with a specific data structure according to 3GPP [Error! Reference source not found.] or TMF [Error! Reference source not found.].

[0089] Following the intent natural language structure described previously, below are several examples for intents in natural language to deliver a secure slice• Intent: Deliver a network service for first responders with advanced security protection • Intent: Deliver a RAN network in location 1234 with advanced security protection on Transport Backhaul• Intent: Deliver a gaming service with basic security protection on radio control plane • Intent: Deliver a service with UE authentication and authorization if UE type is NB-IoT

[0090] During the provisioning phase and ordering of a slice or service, the full set of intents for a slice or service is provided to E2E Service domain IMF that is then responsible to identify the security requirements decompose the service intent into security intents and push it towards a security service orchestrator.

[0091] The security orchestrator decomposes the E2E requirements into the sub-domains and pushes it further to the Resource layer security IMF, for example implemented as a rApp .The security automation loop delivering the security requirement is part of the resource operations layer. Figure 5 shows an exemplary provisioning phase in accordance with some embodiments as described above.

[0092] During the operations phase of a service or a slice depicted in Figure 6, there could be a need to update the initial set of intents. In this phase part of the slice life cycle, the security operator submits the updated security requirement for the subnetwork as a resource intent. The security automation loop delivering the security requirement is part of the resource operations layer.

[0093] If requirements are for the service, the operator submits the updated security requirement for the slice as a service intent to the E2E service domain, which then propagates to the rest of service domains.

[0094] If the requirements are for a specific subnetwork (e.g., RAN, Core) the security operator submits a resource (operations) intent type to the resource security IMF

[0095] Figure 7 shows an exemplary protection requirement on a service level modeled using TM Forum intent and security ontologies in accordance with some embodiments of the present disclosure.

[0096] Figure 8 shows an exemplary protection requirement as an expectation modeled using Third Generation Partnership Program (3GPP) intent expressions in accordance with some embodiments of the present disclosure;

[0097] An example use case where performance requirements are used is “Ensuring segmentation guarantees in slices support by security controls”. This use case Ensuring isolation between resources with support of security capabilities has advantages, for example:• Leveraging security capabilities to achieve isolation through segmentation.• Can reduce the deployment cost (i.e less reliance on dedicated deployments if it is not needed).

[0098] Intent expectation with segmentation as a security requirement, continuously assures that:A domain or a NF is equipped with the suitable controls to fulfill the requirement The deployed controls are effectively configured during runtime upon changes in the environment.

[0099] This intent ensures the continuous security control optimization to ensure the required segmentation level. The intent security expectations in this use case are identified as “Segmentation Level” requirements

[0100] Following the intent natural language structure described previously, below are several examples for intents in natural language to deliver a secure slice:• Ensure mission critical service with E2E segmentation level >= 80% for the user plane back haul transport.• Ensure Cloud native AMF in location 1234 platform segmentation not less than 60%. • Ensure cloud native UPF in location 456 data segmentation not less than 60%.

[0101] The handling of the security requirements part of the service intent during operations and provisioning is like the previous use cases.

[0102] Figure 9 shows an exemplary segmentation requirement on a service level modeled using TM Forum intent and security ontologies in accordance with some embodiments of the present disclosure;

[0103] Figure 10 shows an exemplary segmentation requirement on a service level modeled using 3GPP intent expressions in accordance with some embodiments of the present disclosure;

[0104] The present disclosure proposes the standardization of the protection requirements, where the standardization would impact the technical specifications (TS) for the 3 GPP slice Network Resource Model. For example, the update to TS 28.541v 19.3.0 (2025-03-24) “Management and Orchestration; 5G NRM ; Stage 2 and Stage 3” would be the following new datatypes:

[0105] AttackSurfaceProtection «DataType»a. Type: Objectb. Definition: This data type defines required attack surface to be protected, the level of protection and reusing SecFuncList to define the expected security functions and corresponding rules of each function and corresponding rules of each function. It represents the Protected attack Surface information in ServiceProfile, CNSliceSubnetProfile for CN and RANSliceSubnetProfile for RAN

[0106] AttackSurface «DataType»a. Type: Arrayb. Defintion: This data type defines each security control / feature that is expected to be configured in relation to the attack surface scope if provided to limit the features to a set of specific attack surfaces, and the level of coverage of the attack surface

[0107] Data type: « AttackSurfaceProtection »

[0108] Datatype: «AttackSurface»

[0109] The second set of contributions is related to new attributes to capture the protection

[0110] For updates toTS 28.312 vl 9.1.0 (2025-03-21) “Management and orchestration; Intent driven management services for mobile networks” the new contributions are related to the attributes to be defined for security as part of the ExpectationTarget and Object Context. The table below summarizes the contributions:<>

[0111] Figure 11 shows an exemplary method performed by an intent management function for providing differentiated security in accordance with some embodiments of the present disclosure.

[0112] The method can begin, for example, at 1102 where the method includes receiving an intent-based security expectation associated with a qualitative goal of the security expectation.

[0113] At 1104, the method includes the qualitative goal of the security expectation to determine intent objects associated with the intent-based security expectation, wherein the intent objects comprise one or more of a verb, target, target context, expectation, and expectation context.

[0114] At 1106, the method includes determining a quantifiable mapped requirement associated with an attack surface coverage goal of a mobile communications network based on the intent objects, wherein the quantifiable mapped requirement comprises coverage of one or more entry points of a system comprising one or more of: Orchestration and Management, O&M, services; 3GPP Internet Protocol, IP, Control Plane; 3GPP IP User Plane; 3GPP Radio Control Plane; 3GPP Radio User Plane; Synchronization; or Data and Subscriber info. In an embodiment, determining the attack surface coverage comprises mapping qualitative protection coverage requirements to a quantifiable value that represents a ratio of the covered attack surfaces to the total number of known attack surfaces in a network function.

[0115] At 1108, the method includes determining a non-functional requirement based on the intent objects associated with the intent-based security expectation, where in an embodiment, the non-functional requirement can be associated with segmentation assurance.

[0116] At 1110, the method includes determining that the attack surface coverage goal is fulfilled based on an observed security control coverage metric, wherein the security control coverage metric is based on a function of a number of security controls implemented in the mobile communications network and a number of expected security controls for a required protection level.

[0117] At 1110, the method includes implementing one or more security controls in a network node (1300) of the wireless communication system based on the security control coverage metric and the non-functional requirement. In an embodiment, the security controls implemented in the mobile communications network address one or more security requirements associated with the intent-based security request. In an embodiment, the one or more security requirements comprisefunctional security requirements and / or non-functional security requirements. In an embodiment, the one or more security controls are updated in response to updated security requirements.

[0118] In an embodiment, the intent management function 1218 is implemented by the network node 1300 of the wireless communications system. In other embodiments, the IMF 1218 is implemented by a plurality of network nodes of the wireless communications system.

[0119] Figure 12 shows an example of a communication system 1200 in accordance with some embodiments.

[0120] In the example, the communication system 1200 includes a telecommunications network 1202 that includes an access network 1204, such as a radio access network (RAN), and a core network 1206, which includes one or more core network nodes 1208. The IMF 1218 that implements the functionality as described herein and in Figure 11 can be implemented by one or more of the access network nodes 1210 or the core network nodes 1208 or hosts 1216. The access network 1204 includes one or more access network nodes or base stations of various types, access network nodes 1210A and 1210B are depicted (which may be collectively referred to as network nodes 1210), or any other similar 3rdGeneration Partnership Project (3 GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 1204 may include more than one access network technology. The network nodes 1210 of access network 1204 facilitate direct or indirect connection of wireless devices, also referred to as UEs, such as by connecting UEs 1212A, 1212B, 1212C, and 1212D (one or more of which may be generally referred to as UEs 1212) to the core network 1206 over one or more wireless connections.

[0121] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 1202 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 1202 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 1202, including one or more access network nodes 1210 and / or core network nodes 1208.

[0122] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g.,xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.

[0123] The network nodes 1210 facilitate direct or indirect connection of one or more UEs 1212 to the core network 1206 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1200 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1200 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0124] The UEs 1212 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 1210 and other communication devices. Similarly, the network nodes 1208, 1210 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 1202) with the UEs 1212 and / or with other network nodes or equipment in the telecommunications network 1202 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 1202. More specifically, UEs 1212 may send messages, data, and / or other signals to network nodes 1208, 1210 or other elements of the telecommunications network 1202 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 1208, 1210 may send messages, data, andother signals to UEs 12122, other network nodes 1208, 1210, and other devices in telecommunications network 1202 directly or indirectly. As one specific example, a core network node 1208 may transmit a particular message to a UE 1212 by transmitting the message to an access network node 1210 that will then transmit the message to the intended UE 1212. Similarly, a core network node 1208 may receive a particular message from a UE 1212 by receiving the message from an access network node 1210 that itself received the message from the UE 1212.

[0125] In the depicted example, the core network 1206 connects elements of the access network 1204 (e.g., one or more of the network nodes 1210) to one or more host computing systems, such as host 1216. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1206 includes one or more core network nodes (e.g., core network node 1208) of various types, one or more of which may be generally referred to as network nodes 1208. Network nodes 1208 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1208. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0126] The host 1216 may be under the ownership or control of a service provider other than an operator or provider of the access network 1204 and / or the telecommunications network 1202. The host 1216 may be operated by the service provider or on behalf of the service provider. The host 1216 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0127] As a whole, the communication system 1200 of Figure 12 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 1200 may be configured to operate according to predefined rules or procedures, such as specific standardsthat include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 1200 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 1200 supporting different standards, protocols, or rule sets.

[0128] As one example, in certain embodiments, access network 1204 may contain some access network nodes 1210 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 1210 support (or the same access network nodes 1210 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 1202 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 1204 and / or a core network 1206 that supports multiple different standard generations or may include multiple access networks 1204 and / or multiple core networks 1206 with individual networks 1204, 1206 supporting different standard generations.

[0129] Telecommunications network 1202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 1202. For example, the telecommunications network 1202 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0130] In some examples, one or more of the UEs 1212 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1204. Additionally, a UE may be configured for operating in single- or multi-RAT or multi -standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi -radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0131] In the example, the hub 1214 communicates with the access network 1204 to facilitate indirect communication between one or more UEs (e.g., UE 1212C and / or 1212D) and network nodes (e.g., network node 121 OB). In some examples, the hub 1214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1214 may be a broadband router enabling access to the core network 1206 for the UEs. As another example, the hub 1214 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1210, or by executable code, script, process, or other instructions in the hub 1214.

[0132] As another example, the hub 1214 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1214 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1214 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1214 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0133] The hub 1214 may have a constant / persistent or intermittent connection to the network node 1210B. The hub 1214 may also allow for a different communication scheme and / or schedule between the hub 1214 and UEs (e.g., UE 1212C and / or 1212D), and between the hub 1214 and the core network 1206. In other examples, the hub 1214 is connected to the core network 1206 and / or one or more UEs via a wired connection. Moreover, the hub 1214 may be configured to connect to an M2M service provider over the access network 1204 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1210 while still connected via the hub 1214 via a wired or wireless connection. In some embodiments, the hub 1214 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1210B. In other embodiments, the hub 1214 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1210B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0134] Figure 13 shows a network node 1300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in atelecommunications network. In accordance with respective embodiments, network node 1300 may be configured to operate in communication system 1200 of Figure 12, like network nodes 1208 or 1210, or can implement IMF 1218. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0135] Network nodes 1300 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 1300 may be a relay node or a relay donor node controlling a relay. Network nodes 1300 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0136] Other examples of network nodes 1300 include multiple transmission point (multi -TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0137] In particular embodiments, network node 1300 includes a processing circuitry 1302, a memory 1304, a communication interface 1306, and a power source 1308. In general, in a particular embodiment of network node 1300, processing circuitry 1302, memory 1304, communication interface 1306, and power source 1308 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 1300.

[0138] The network node 1300 may be composed of multiple distinct network entities (e.g., a NodeB entity and an RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 1300 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multipleNodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 1304 or portions of memory 1304 for different RATs) and some components may be reused (e.g., a same antenna 1310 may be shared by different RATs). The network node 1300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1300, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1300.

[0139] The processing circuitry 1302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 1304, to provide network node 1300 functionality.

[0140] In some embodiments, the processing circuitry 1302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1302 includes one or more of radio frequency (RF) transceiver circuitry 1312 and baseband processing circuitry 1314. In some embodiments, the RF transceiver circuitry 1312 and the baseband processing circuitry 1314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1312 and baseband processing circuitry 1314 may be on the same chip or set of chips, boards, or units.

[0141] The memory 1304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1302. The memory 1304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1302 andutilized by the network node 1300. The memory 1304 may be used to store any calculations made by the processing circuitry 1302 and / or any data received via the communication interface 1306. In some embodiments, the processing circuitry 1302 and memory 1304 is integrated.

[0142] The communication interface 1306 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 1306 comprises port(s) / terminal(s) 1316 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 1300 may be capable of wireless communication and communication interface 1306 may also include radio front-end circuitry 1318 that may be coupled to, or in certain embodiments a part of, an antenna 1310. Particular embodiments of radio front-end circuitry 1318 include filter(s) 1320 and amplifier(s) 1322. The radio front-end circuitry 1318 may be connected to an antenna 1310 and processing circuitry 1302. The radio front-end circuitry may be configured to condition signals communicated between antenna 1310 and processing circuitry 1302. The radio front-end circuitry 1318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1318 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 1320 and / or amplifiers 1322. The radio signal(s) may then be transmitted via the antenna 1310. Similarly, when receiving data, the antenna 1310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1318. The digital data may be passed to the processing circuitry 1302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0143] In certain alternative embodiments, network node 1300 may be capable of wireless communication but does not include separate radio front-end circuitry 1318, instead, the processing circuitry 1302 includes radio front-end circuitry and is connected to the antenna 1310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1312 is part of the communication interface 1306. In still other embodiments, the communication interface 1306 includes one or more ports or terminals 1316, the radio front-end circuitry 1318, and the RF transceiver circuitry 1312, as part of a radio unit (not shown), and the communication interface 1306 communicates with the baseband processing circuitry 1314, which is part of a digital unit (not shown).

[0144] The antenna 1310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1310 may be coupled to the radio front-end circuitry 1318 and may be any type of antenna capable of transmitting and receiving data and / orsignals wirelessly. In certain embodiments, the antenna 1310 is separate from the network node 1300 and connectable to the network node 1300 through one or more interfaces or ports.

[0145] The antenna 1310, communication interface 1306, and / or the processing circuitry 1302 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 1300. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 1310, the communication interface 1306, and / or the processing circuitry 1302 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 1300. Any information, data and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0146] The power source 1308 provides power to the various components of network node 1300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1300 with power for performing the functionality described herein. For example, the network node 1300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1308. As a further example, the power source 1308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0147] Embodiments of the network node 1300 may include additional components beyond those shown in Figure 13 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1300 may include user interface equipment to allow input of information into the network node 1300 and to allow output of information from the network node 1300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1300.

[0148] Figure 14 is a block diagram illustrating a virtualization environment 1400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or morevirtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1400 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0149] Applications 1402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1300 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0150] Hardware 1404 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 1408A and VM 1408B (which may be collectively referred to as VMs 1408), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1406 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 1408.

[0151] The VMs 1408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 1406. Different embodiments of the instance of a virtual appliance 1402 may be implemented on one or more of VMs 1408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0152] In the context of NFV, each of the VMs 1408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1408, and that part of hardware 1404 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, formsseparate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 1408 on top of the hardware 1404 and corresponds to an application 1402.

[0153] Hardware 1404 may be implemented in a standalone network node with generic or specific components. Hardware 1404 may implement some functions via virtualization. Alternatively, hardware 1404 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1410, which, among others, oversees lifecycle management of applications 1402. In some embodiments, hardware 1404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1412 which may alternatively be used for communication between hardware nodes and radio units.

[0154] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0155] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0156] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

CLAIMS1. A method performed by an intent management function ( 1218) for providing differentiated security levels, the method comprising:receiving (1102) an intent-based security expectation associated with a qualitative goal of the security expectation;parsing (1104) the qualitative goal of the security expectation to determine intent objects associated with the intent-based security expectation, wherein the intent objects comprise one or more of a verb, target, target context, expectation, and expectation context;determining (1106) a quantifiable mapped requirement associated with an attack surface coverage goal of a mobile communications network based on the intent objects, wherein the quantifiable mapped requirement comprises coverage of one or more entry points of a system comprising one or more of:Orchestration and Management, O&M, services;Third Generation Partnership Program, 3GPP, Internet Protocol, IP, Control Plane; 3GPP IP User Plane;3GPP Radio Control Plane;3GPP Radio User Plane;Synchronization; orData and Subscriber info;determining (1108) a non-functional requirement based on the intent objects associated with the intent-based security expectation;determining (1110) that the attack surface coverage goal is fulfilled based on an observed security control coverage metric, wherein the security control coverage metric is based on a function of a number of security controls implemented in the mobile communications network and a number of expected security controls for a required protection level; andimplementing (1112) one or more security controls in a network node (1300) of the wireless communication system based on the security control coverage metric and the nonfunctional requirement.

2. The method of claim 1, wherein the intent management function (1218) is implemented by the network node (1300) of the mobile communications network.

3. The method of claim 1, wherein the intent management function (1218) is implemented bya plurality of network nodes of the mobile communications network.

4. The method of any of claims 1 to 3, wherein the non-functional requirement is associated with segmentation assurance.

5. The method of any of claims 1 to 4, wherein the security controls implemented in the mobile communications network address one or more security requirements associated with the intent-based security expectation.

6. The method of claim 5, wherein the one or more security requirements comprise functional security requirements and / or non-functional security requirements.

7. The method of any of claims 1 to 6, wherein determining the quantifiable mapped requirement comprises mapping qualitative protection coverage requirements to a quantifiable value that represents a ratio of covered attack surfaces to a total number of known attack surfaces in a network function.

8. The method of any of claims 1 to 7, wherein the verb indicates if an intent is used to deliver a set requirements and indicates whether continuous assurance or continuous monitoring is required.

9. The method of any of claims 1 to 8, wherein the target defines a network node expected act on an intent associated with the intent-based security expectation.

10. The method of any of claims 1 to 9, wherein the target context indicates whether an intent associated with the intent-based security expectation applies to a group of targets or an entire network and comprises one or more of location or cell ID, or physical ID.

11. The method of any of claims 1 to 10, wherein the expectation comprises a requirement to be fulfilled by the target context intent object.

12. The method of claim 11, wherein the expectation context indicates if there are any conditions for the expectation to be true.

13. The method of any of claims 1 to 12, wherein the one or more security controls are updated in response to updated security requirements.

14. A network node (1300) that implements an intent management function (1218) for providing differentiated security levels, the network node (1300) configured to:receive (1102) an intent-based security expectation associated with a qualitative goal of the security expectation;parse (1104) the qualitative goal of the security expectation to determine intent objects associated with the intent-based security expectation, wherein the intent objects comprise one or more of a verb, target, target context, expectation, and expectation context;determine (1106) a quantifiable mapped requirement associated with an attack surface coverage goal of a mobile communications network based on the intent objects, wherein the quantifiable mapped requirement comprises coverage of one or more entry points of a system comprising one or more of:Orchestration and Management, O&M, services;Third Generation Partnership Program, 3GPP, Internet Protocol, IP, Control Plane; 3GPP IP User Plane;3GPP Radio Control Plane;3GPP Radio User Plane;Synchronization;Data and Subscriber info;determine (1108) a non-functional requirement based on the intent objects associated with the intent-based security expectation;determine (1110) that the attack surface coverage goal is fulfilled based on an observed security control coverage metric, wherein the security control coverage metric is based on a function of a number of security controls implemented in the mobile communications network and a number of expected security controls for a required protection level; andimplement (1112) one or more security controls in a network node (1300) of the mobile communications network based on the security control coverage metric and the non-functional requirement.

15. The network node (1300) of claim 14, wherein the network node (1300) is further configured to perform any of claims 2 to 13.

16. A network node (1300) that implements an intent management function (1218) for providing differentiated security levels, the network node (1300) comprising processing circuitry that is configured to:receive (1102) an intent-based security expectation associated with a qualitative goal of the security expectation;parse (1104) the qualitative goal of the security expectation to determine intent objects associated with the intent-based security expectation, wherein the intent objects comprise one or more of a verb, target, target context, expectation, and expectation context;determine (1106) a quantifiable mapped requirement associated with an attack surface coverage goal of a mobile communications network based on the intent objects, wherein the quantifiable mapped requirement comprises coverage of one or more entry points of a system comprising one or more of:Orchestration and Management, O&M, services;Third Generation Partnership Program, 3GPP, Internet Protocol, IP, Control Plane; 3GPP IP User Plane;3GPP Radio Control Plane;3GPP Radio User Plane;Synchronization;Data and Subscriber info;determine (1108) anon-functional requirement based on the intent objects associated with the intent-based security expectation;determine (1110) that the attack surface coverage goal is fulfilled based on an observed security control coverage metric, wherein the security control coverage metric is based on a function of a number of security controls implemented in the mobile communications network and a number of expected security controls for a required protection level; andimplement (1112) one or more security controls in a network node (1300) of the mobile communications network based on the security control coverage metric and the non-functional requirement.

17. The network node (1300) of claim 16, wherein the processing circuitry is further configured to perform any of claims 2 to 13.

18. A computer program for providing differentiated security levels, the computer program comprising computer code which, when run on processing circuitry of a network node (1300),causes the network node (1300) to perform the method according to any of claims 1-13.

19. A computer program product comprising a computer program according to claim 18, and a computer readable storage medium on which the computer program is stored.