Security monitoring method and device for network slice, equipment, storage medium and program
By analyzing the 5GMM Cause value in the user access failure message, judging the security trend of network slicing and sending early warnings, the problem of incomplete network slicing security monitoring in the prior art is solved, and comprehensive security management of 5G network slicing is achieved.
Patent Information
- Application Number
- CN202410969498.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-07-26
- Filing Date
- 2024-07-18
- Publication Date
- 2024-11-12
AI Technical Summary
The existing technology only conducts security monitoring of network slices from the operation and maintenance side, which is not comprehensive enough to effectively monitor the security status of network slices. Especially in 5G networks, attacks caused by illegal access and insufficient resources are difficult to be discovered in a timely manner.
By obtaining the user's failure message, extracting the 5GMM Cause value related to network slicing, analyzing the number of reason values to judge the security trend of network slicing, including the trend of being attacked and insufficient resources, and sending early warning information to the operation and maintenance platform for management .
It realizes more comprehensive security monitoring of network slicing, can promptly detect security risks and insufficient resources, prevent illegal access and horizontal movement attacks, and improves the security management capabilities of network slicing.
Smart Images

Figure CN118945697A_ABST
Abstract
Description
[0001] This application claims the priority of the Chinese patent application filed with the China Patent Office on July 26, 2023, with application number 202310930229.4 and application name “A security monitoring method, device, equipment and storage medium for network slicing”, the entire contents of which are incorporated by reference in this application. Technical Field
[0002] The present application relates to the field of communication security, and in particular to a security monitoring method, device, equipment, storage medium and program for network slicing. Background Art
[0003] In order to better meet the needs of various industries for the fifth generation mobile communication technology (5G) network, 5G network introduced network slicing technology, that is, through virtualization technology, various physical resources in the network are abstracted into virtual resources, and based on the specified network functions and the number of access networks to be determined, an end-to-end logical network is built on demand to provide one or more network services.
[0004] The development direction of network slicing technology is mainly security isolation, security management and slice access authentication, among which security management includes security monitoring. At present, the industry mostly conducts security monitoring of the business volume and capacity of network slices from the operation and maintenance side according to the business and online and offline conditions of network slices, and conducts security monitoring and analysis of network slices through the Network Data Analytics Function (NWDAF) network element.
[0005] Security monitoring of network slicing only from the operation and maintenance side is not comprehensive enough. Considering the importance of network slicing technology to 5G networks and industry users, more comprehensive security monitoring of network slicing is needed. Summary of the invention
[0006] The present application provides a network slice security monitoring method, device, equipment, storage medium and program to solve the problem that security monitoring of network slices only from the operation and maintenance side is not comprehensive enough and more comprehensive security monitoring of network slices is needed.
[0007] In a first aspect, the present application provides a network slice security monitoring method, the method comprising:
[0008] Obtaining a user's failure message, which indicates that the user has failed to access the network or that the user has failed to initiate a service;
[0009] Extracting one or more cause values related to the network slice in the failure message;
[0010] Obtain the quantity of at least one cause value among one or more cause values, and analyze the security trend of the network slice based on the quantity of at least one cause value.
[0011] In a possible design, the cause value is a 5GMM Cause value; and the security trend of the network slice includes: at least one of a security trend of being attacked and a security trend of insufficient resources.
[0012] In one possible design, one or more cause values related to the network slice in the failure message are extracted, including:
[0013] From the failure message, extract one or more 5GMM Cause values related to the network slice.
[0014] In one possible design, when the failure cause is no available network slice, the one or more cause values include a 5GMM Cause with a value of 62;
[0015] When the failure cause is that the network data name is not supported or subscribed in the network slice, one or more cause values include 5GMM Cause with a value of 91;
[0016] When the failure cause is insufficient resources for a specific network slice and network data name, one or more cause values include a 5GMM Cause with a value of 67;
[0017] When the cause of failure is insufficient resources in a specific network slice, one or more cause values include 5GMMCause with a value of 69.
[0018] In one possible design, one or more 5GMMCause values related to the network slice are extracted from the failure message, including:
[0019] At least one of a 5GMM Cause value of 62, a 5GMM Cause value of 91, a 5GMM Cause value of 67, and a 5GMM Cause value of 69 is extracted from the failure message.
[0020] In a possible design, obtaining the quantity of at least one cause value among the one or more cause values, and analyzing the security trend of the network slice according to the quantity of the at least one cause value includes:
[0021] Obtain the quantity of at least one 5GMM Cause value among the one or more 5GMM Cause values, and analyze the security trend of the network slice based on the quantity of the at least one 5GMM Cause value.
[0022] In a possible design, the security trend of the network slice is analyzed based on the number of at least one 5GMM Cause value, including:
[0023] The security trend of the network slice being attacked is determined based on the number of 5GMM Cause values with a value of 62 and / or the number of 5GMM Cause values with a value of 91.
[0024] In a possible design, judging the security trend of the network slice being attacked according to the number of 5GMM Cause values having a value of 62 and / or the number of 5GMMCause values having a value of 91 includes:
[0025] When the number of 5GMM Cause values with a value of 62 is greater than the first preset threshold, and / or the number of 5GMM Cause values with a value of 91 is greater than the second preset threshold, the security trend of the network slice being attacked is judged.
[0026] In a possible design, the security trend of the network slice is analyzed based on the number of at least one 5GMM Cause value, including:
[0027] Based on the number of 5GMM Cause values with a value of 67 and / or the number of 5GMM Cause values with a value of 69, the security trend of insufficient network slice resources can be judged.
[0028] In a possible design, judging a security trend of insufficient network slice resources according to the number of 5GMM Cause values having a value of 67 and / or the number of 5GMMCause values having a value of 69 includes:
[0029] When the number of 5GMM Cause values with a value of 67 is greater than the third preset threshold, and / or the number of 5GMM Cause values with a value of 69 is greater than the fourth preset threshold, the security trend of insufficient network slice resources is judged.
[0030] In a possible design, when the security trend of the network slice includes: one of a security trend of being attacked and a security trend of insufficient resources, obtaining the number of at least one cause value among the one or more cause values, and analyzing the security trend of the network slice according to the number of the at least one cause value, including:
[0031] The number of one or two 5GMM Cause values among the one or more 5GMM Cause values is obtained, and the security trend of the network slice is analyzed according to the number of the one or two 5GMM Cause values.
[0032] In a possible design, obtaining a quantity of at least one 5GMM Cause value among the one or more 5GMM Cause values includes:
[0033] The number of each 5GMM Cause value is obtained, wherein the number of 5GMM Cause values with a value of 62 and / or the number of 5GMM Cause values with a value of 91 are used to judge the security trend of the network slice being attacked; the number of 5GMM Cause values with a value of 67 and / or the number of 5GMM Cause values with a value of 69 are used to judge the security trend of insufficient network slice resources.
[0034] In a possible design, obtaining a quantity of at least one 5GMM Cause value among the one or more 5GMM Cause values includes:
[0035] Obtain security trends of the network slices to be analyzed;
[0036] When the security trend of the network slice to be analyzed is a security trend of being attacked, the number of 5GMMCause values with a value of 62 and / or the number of 5GMM Cause values with a value of 91 are obtained; when the security trend of the network slice to be analyzed is a security trend of insufficient resources, the number of 5GMM Cause values with a value of 67 and / or the number of 5GMM Cause values with a value of 69 are obtained.
[0037] In one possible design, after analyzing the security trend of the network slice according to the number of the at least one cause value, the method further includes:
[0038] Send warning information to the operation and maintenance platform so that the operation and maintenance platform can manage the network slices based on the warning information.
[0039] In a second aspect, the present application provides a network slice security monitoring device, including:
[0040] An acquisition module is used to acquire a failure message of a user, where the failure message is used to indicate that the user fails to access the network, or that the user fails to initiate a service;
[0041] An extraction module, used to extract one or more cause values related to the network slice in the failure message;
[0042] The analysis module is used to obtain the number of at least one cause value among one or more cause values, and analyze the security trend of the network slice based on the number of at least one cause value.
[0043] In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;
[0044] Memory stores computer-executable instructions;
[0045] The processor executes computer execution instructions stored in the memory to implement a network slicing security monitoring method according to the first aspect of the invention.
[0046] In a fourth aspect, the present application provides a computer-readable storage medium, which stores computer execution instructions. When the computer execution instructions are executed by a processor, they are used to implement a network slicing security monitoring method according to the invention content of the first aspect.
[0047] In a fifth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, is used to implement a network slicing security monitoring method according to the invention content of the first aspect.
[0048] The present application provides a method, device, equipment, storage medium and program for security monitoring of network slices, which obtains the user's failure message and then extracts one or more cause values related to the network slice in the failure message, so as to analyze the security trend of the network slice according to the number of at least one cause value. The following technical effects are achieved: according to the number of cause values related to the network slice, the security trend of the network slice is analyzed, and a method for analyzing the security trend of the network slice according to signaling data is provided, which solves the problem that the security monitoring of the network slice only from the operation and maintenance side is not comprehensive enough; by analyzing the security trend of the network slice, the network slice with security risks is managed securely, and the problem of illegal access to the network slice and the attack behavior of using the weaknesses in a certain network slice to move horizontally to another network slice is solved; the user's failure message is obtained, and the cause value related to the network slice in the failure message is extracted, which solves the problem of obtaining the cause value. BRIEF DESCRIPTION OF THE DRAWINGS
[0049] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief introduction is given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0050] Figure 1 A schematic diagram of the system architecture of the network slice security monitoring method provided in the embodiment of the present application;
[0051] Figure 2 Schematic diagram of the process of the network slice security monitoring method provided in the embodiment of the present application Figure 1 ;
[0052] Figure 3 Schematic diagram of the process of the network slice security monitoring method provided in the embodiment of the present application Figure 2 ;
[0053] Figure 4 Schematic diagram of the process of the network slice security monitoring method provided in the embodiment of the present application Figure 3 ;
[0054] Figure 5 Schematic diagram of the process of the network slice security monitoring method provided in the embodiment of the present application Figure 4 ;
[0055] Figure 6 A schematic diagram of the structure of a security monitoring device for a network slice provided in an embodiment of the present application;
[0056] Figure 7 A schematic diagram of the structure of the electronic device hardware provided in an embodiment of the present application.
[0057] Reference numerals:
[0058] 110-user terminal; 120-infrastructure layer; 121-access network; 122-transmission network; 123-core network; 130-network slice management layer; 131-security monitoring device; 1311-acquisition module; 1312-extraction module; 1313-analysis module; 132-operation and maintenance platform; 140-network slice layer; 141-eMBB network slice; 142-uRLLC network slice; 143-mMTC network slice;
[0059] 200 - electronic device; 210 - processor; 220 - memory; 230 - communication component; 240 - bus. DETAILED DESCRIPTION
[0060] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.
[0061] In the embodiments of the present application, words such as "first" and "second" are used to distinguish the same or similar items with basically the same functions and effects. For example, the first quantity and the second quantity are only used to distinguish the quantity of different cause values, and do not limit their numerical values. It can be understood by those skilled in the art that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit them to be different. It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way. In the embodiments of the present application, "at least one" refers to one or more, and "more" refers to two or more.
[0062] It should be noted that the "at..." in the embodiment of the present application can be the instant when a certain situation occurs, or it can be a period of time after a certain situation occurs, and the embodiment of the present application does not specifically limit this. In addition, the network slice security monitoring method provided in the embodiment of the present application is only used as an example, and the network slice security monitoring method can also include more or less content.
[0063] In order to clearly describe the technical solutions of the embodiments of the present application, some terms and technologies involved in the embodiments of the present application are briefly introduced below:
[0064] Network Data Analytics Function (NWDAF) network element: It is a network element used for data perception and analysis. NWDAF network element automatically perceives and analyzes the network based on network data, and participates in the entire life cycle of network design, construction, operation and maintenance, network optimization, and operation, making the network easier to maintain and control, improving the efficiency of network resource utilization, and enhancing user service experience.
[0065] 5G mobility management failure cause (5GS mobility management cause, 5GMM Cause): refers to the standard for defining failure causes developed by the 3rd Generation Partnership Project (3GPP) organization for 5G networks. 5GMM Cause includes multiple failure causes, as well as the 5GMMCause value and binary code corresponding to each failure cause.
[0066] Failure cause: refers to the various reasons for the failure of a user to access the network or the failure of a user to initiate a service. In 5GMM Cause, the 5GMM Cause values related to network slicing are 62, 67, 69, and 91.
[0067] Binary code: refers to the code expressed in eight bits of binary. Different failure reasons correspond to different binary codes.
[0068] In the existing technology, the NWDAF network element is used to perform security monitoring on network slices from the operation and maintenance side. Considering the importance of network slicing technology to 5G networks and industry users, more comprehensive security monitoring of network slices is required.
[0069] Network slicing is an important feature for realizing 5G private networks. It detects the signaling related to 5G slicing to prevent illegal access to slices and attacks that exploit weaknesses in a network slice and move laterally to another network slice.
[0070] At present, there is no method to extract key features from signaling information to monitor the security status of network slices. Therefore, according to the standards formulated by the 3GPP organization, the inventors use failure messages as signaling information, extract cause values from failure messages as key technical features, and monitor the security status of network slices by analyzing the cause values. At the same time, the inventors also proposed a method for reporting security warning information and resource warning information, which enriched the content and scope of network slice security monitoring and made up for the problem that network slice security monitoring in the prior art is not comprehensive.
[0071] Based on this, the embodiments of the present application provide a network slice security monitoring method, device, equipment, storage medium and program, which can be used in the field of communication security technology, aiming to solve the problem that the prior art only performs security monitoring of network slices from the operation and maintenance side, which is not comprehensive enough and requires more comprehensive security monitoring of network slices.
[0072] Figure 1 A schematic diagram of the system architecture of the network slice security monitoring method provided in the embodiment of the present application. It should be noted that: Figure 1 What is shown is merely an example of a system architecture to which the embodiments of the present application can be applied, in order to help those skilled in the art understand the technical content of the present application, but it does not mean that the embodiments of the present application cannot be used in other devices, systems, environments or scenarios.
[0073] like Figure 1As shown, the system architecture of the security monitoring method of network slices includes: user terminal 110, infrastructure layer 120, network slice management layer 130 and network slice layer 140. The network slice layer 140 is an example of a network slice running on the infrastructure layer 120. Each network layer can be hardware, or software divided from the function, or a structure that combines the above two.
[0074] In the embodiment of the present application, the user terminal 110 (User Equipment, UE) is a device that accesses the infrastructure layer 120 to obtain network services and thereby provides voice and / or data connectivity to users. The user terminal 110 accesses the network. According to the three major application scenarios of the 5G network, the user terminal 110 can be different types of devices.
[0075] In the application scenario of enhanced mobile broadband (eMBB), the user terminal 110 can be a smart phone, a fixed phone, a virtual reality (VR) glasses, etc., which are used in the fields of high-definition video, VR, augmented reality (AR), and cloud games; in the business scenario of ultra-reliable low-latency communications (uRLLC), the user terminal 110 can be an autonomous driving car, medical equipment, and CNC machine tools, etc., which are used in the fields of telemedicine and industrial automation; in the business scenario of massive machine type communication (mMTC), the user terminal 110 can be a smart parking device, a household electricity meter, and an agricultural sensor, etc., which are used in the fields of smart cities and public safety.
[0076] The infrastructure layer 120 is a structure that provides the required resources and basic capabilities for network slicing. The infrastructure layer 120 includes an access network 121, a transmission network 122, and a core network 123. The access network 121 (Access Network, AN) is responsible for the access of the user terminal 110, the transmission network 122 (Transmission Network, TN) is used to transmit data, and the core network 123 (CoreNetwork, CN) is responsible for managing and sorting data.
[0077] The network slice management layer 130 is responsible for the management of the network slice life cycle and ensures that the network slice instance can meet the business performance-related indicators proposed by the vertical industry. It is a network slice manager (NSM). The network slice management layer 130 includes a security monitoring device 131 and an operation and maintenance platform 132. The security monitoring device 131 can be a server that provides security trend detection services. The security monitoring device 131 is used to perform security monitoring on multiple network slices to analyze the security trends of network slices and send warning information to the operation and maintenance platform 132; the operation and maintenance platform 132 can be a server that provides operation and maintenance services. The operation and maintenance platform 132 is used to perform security management on network slices based on the warning information.
[0078] The network slice layer 140 aggregates the required network functions to form an end-to-end logical network (network slice instance) based on the infrastructure layer 120. According to the three major application scenarios of the 5G network, the network slice layer 140 includes an eMBB network slice 141, a uRLLC network slice 142, and an mMTC network slice 143.
[0079] The features of eMBB network slice 141 are ultra-high transmission data rate and mobility guarantee under wide coverage. eMBB network slice 141 includes but is not limited to smartphone sub-network slice, fixed access sub-network slice and virtual reality sub-network slice.
[0080] uRLLC network slice 142 is characterized by high reliability and low latency connection, etc. uRLLC network slice 142 includes but is not limited to autonomous driving sub-network slice, industrial control sub-network slice and telemedicine sub-network slice, etc.;
[0081] The mMTC network slice 143 is characterized by massive Internet of Things, etc. The mMTC network slice 143 includes but is not limited to smart parking sub-network slices, automatic meter reading sub-network slices, and smart agriculture sub-network slices.
[0082] Figure 2 Schematic diagram of the process of the network slice security monitoring method provided in the embodiment of the present application Figure 1 .
[0083] like Figure 2 As shown, the method includes:
[0084] S101, obtaining a failure message from a user;
[0085] Specifically, the network slice layer includes multiple network slices (the network slice is a sub-network slice in the system architecture), and each network slice is used in at least one field, which can belong to any application scenario. The security monitoring device performs security monitoring of multiple network slices at the same time, and the security monitoring methods of different network slices are the same. Therefore, this embodiment describes the security monitoring of the target network slice in detail. It should be understood that the target network slice is any one of the multiple network slices, and this embodiment does not limit which network slice is used as the target network slice. In the prior art, network slices are monitored through NWDAF network elements. Since the specific monitoring methods of different network slices are different, all network slices cannot be monitored at the same time. Compared with the prior art, the monitoring method of the present technical solution can perform security monitoring on any network slice, which solves the problem of only being able to monitor some network slices.
[0086] The failure message is used to indicate that the user has failed to access the network, or that the user has failed to initiate a service, wherein the user has failed to access the network, specifically, the user's user terminal has failed to access the network; the user has failed to initiate a service, specifically, the user's user terminal has failed to initiate a service; the user's failure message, specifically, refers to the failure message of the user's user terminal. In the target network slice, there may be multiple user terminals requesting to access the network, and when any user terminal fails to access the network, the security monitoring device obtains a failure message indicating that the user terminal has failed to access the network; and / or there may be multiple user terminals initiating services, and when any user terminal fails to initiate a service, the security monitoring device obtains a failure message indicating that the user terminal has failed to initiate a service.
[0087] Optionally, the failure message can be generated by the operation and maintenance platform, in which case the security monitoring device obtains the failure message from the operation and maintenance platform; it can also be generated by a third-party server deployed on the network, in which case the security monitoring device obtains the failure message from the third-party server; it can also be a signaling message for interaction between the user terminal and the network. When the user terminal fails to access the network or fails to initiate a service, the cause of the failure will be indicated by the cause value carried in the failure message. At the same time, the failure message can be a message in different formats, for example, it can be a message in a message format generated by the operation and maintenance platform or a third-party server, or it can be a signaling message.
[0088] S102. Extract one or more cause values related to the network slice in the failure message;
[0089] Specifically, a failure message can indicate that a user terminal fails to access the network or fails to initiate a service. In this case, a failure message carries a reason value. A failure message can also indicate that multiple user terminals fail to access the network or fail to initiate a service. These user terminals can be located in one device cluster or in different device clusters. In this case, a failure message carries the same number of reason values as the user terminals. When one or more user terminals fail to access the network and / or one or more user terminals fail to initiate a service, one or more failure messages are obtained, and one or more reason values can be extracted from these failure messages.
[0090] These cause values may be the same as each other, or each may correspond to its own failure cause or failure type. Therefore, one or more cause values may be extracted from these failure messages, each of which is used to indicate the failure cause or failure type of the user terminal's failure to access the network or the failure to initiate a service. Among the extracted cause values, there may be several cause values that are not related to the network slice, that is, other software, hardware or other reasons outside the network slice directly or indirectly cause the user terminal to fail to access the network or initiate a service, where other reasons may be user terminal authentication and authorization failure or configuration parameter errors, etc. Through these cause values, the security trend of the network slice cannot be analyzed. There may also be several cause values related to the network slice, that is, the network slice directly or indirectly causes the user terminal to fail to access the network or initiate a service. Through these cause values, the current security status of the network slice can be analyzed, and then the security trend of the network slice can be analyzed; or, the security trend of the network slice can be directly analyzed. Since different cause values correspond to different failure causes or failure types, and there may be one or more cause values related to the network slice, the security monitoring device extracts at least one cause value related to the network slice in the failure message.
[0091] Optionally, the cause value is extracted from the failure message according to the formulation standard of the failure message and the data format of the cause value. The failure message may be formulated according to different standards, for example, it may be formulated according to the 5GMM Cause standard of the 3GPP organization, it may be formulated according to the sequence of serial numbers, or it may be formulated according to the failure cause or failure type. The cause value may be in different data formats, for example, it may be in text format, numeric format, or special format, etc.
[0092] Take the failure message as an example, which is formulated according to the 5GMM Cause standard and the cause value is in text format: each time a failure message is obtained, the failure message is parsed according to the 5GMM Cause to obtain the corresponding cause value. 5GMM Cause defines multiple failure causes and the 5GMM Cause value corresponding to each failure cause. Therefore, the 5GMM Cause value is directly used as the cause value. From the multiple failure causes provided by 5GMM Cause, filter the failure causes related to network slicing to facilitate the extraction of the 5GMM Cause value related to network slicing.
[0093] It should be noted that, from the above embodiments, only the cause values related to network slicing can be used to analyze the security trend of network slicing. For the convenience of description, unless otherwise specified, the cause values in the following text refer to the cause values related to network slicing.
[0094] S103. Obtain the number of at least one cause value among the one or more cause values, and analyze the security trend of the network slice according to the number of the at least one cause value;
[0095] Specifically, the failure of a user terminal to access the network or initiate a service may be sporadic, for example, caused by factors such as authentication failure or configuration parameter errors of the user terminal. Therefore, it cannot be said that there are security risks in the network slice. But it may also be widespread, and multiple user terminals accessing a specific network slice all fail to access the network or initiate a service. At this time, the security trend of the network slice can be analyzed based on the number of cause values.
[0096] The number of cause values represents the probability that there are security risks in the network slice. When the number of cause values is small, it means that the probability of security risks in the network slice is low; when the number of cause values is large, it means that the cause value is related to the network slice, and the probability of security risks in the network slice is high.
[0097] Optionally, the security trend of the network slice can be analyzed based on the number of consecutive cause values. Specifically, when the security monitoring module extracts the cause value, it records the generation time of the failure message indicated by each cause value. For any two adjacent cause values, when the difference between their respective corresponding generation times is less than a preset time, the two cause values are determined to be continuous cause values. The security monitoring module analyzes the security trend of the network slice based on the number of consecutive cause values.
[0098] Optionally, the security trend of the network slice can be analyzed according to the number of cause values in a unit time. Specifically, during the period of time when the security of the network slice is at risk, the user terminal will fail to access the network or initiate a service. The security monitoring module analyzes the security trend of the network slice according to the number of cause values in a certain period of time.
[0099] According to the number of cause values, the security trend of the network slice is analyzed, that is, the probability of the network slice having a security risk is high or low. Multiple cause values correspond to the same quantity condition related to quantity, or each corresponds to its own quantity condition related to quantity. When multiple cause values meet the quantity condition, the security trend of the network slice is judged according to the cause value type, which can be a security trend with a high probability of a risk, a security trend with a low probability of a risk, or a prediction of the risk in the future.
[0100] When analyzing security trends, the quantity condition may be that the number of cause values, the continuous number, or the number within a unit time length is greater than a threshold, or that the number of cause values, the continuous number, or the number within a unit time length is within a threshold range, or that the number of cause values, the continuous number, or the number within a unit time length, and the quantity increment within a time period is greater than a threshold. Among them, the threshold can be flexibly configured according to actual needs, and the actual needs here can be the type of cause value, the type of target network slice, or the type of user terminal. For example, when the quantity condition refers to being greater than a threshold, the data size of the threshold can be 100, 500, or 1000, etc., which is not limited in this embodiment.
[0101] Optionally, the potential safety hazard is caused by at least one factor, and there are multiple corresponding relationships between the cause value and the factor. It can be that when the number of one cause value meets the quantity condition, the potential safety hazard is caused by one factor corresponding to the cause value; it can also be that when the number of one cause value meets the quantity condition, the potential safety hazard is caused by multiple factors corresponding to the cause value; it can also be that when the number of multiple cause values meets the quantity condition, the potential safety hazard is caused by one factor corresponding to these cause values; it can also be that when the number of multiple cause values meets the quantity condition, the potential safety hazard is caused by multiple factors, wherein one cause value corresponds to at least one factor.
[0102] When there are security risks in the target network slice, the security monitoring device sends an early warning message to the operation and maintenance platform, instructing the operation and maintenance platform to perform security management on the target network slice.
[0103] In other embodiments, the execution subject is not the safety monitoring device, but other devices mentioned or not mentioned in this embodiment.
[0104] It should be noted that the one or more cause values in S103 are exactly the same as the one or more cause values in S102.
[0105] This embodiment provides a method for monitoring the security of network slices, which obtains the user's failure message and then extracts one or more reason values related to the network slice in the failure message, so as to analyze the security trend of the network slice according to the number of at least one reason value. The following technical effects are achieved: the security trend of the network slice is analyzed according to the number of reason values related to the network slice, and a method for analyzing the security trend of the network slice according to signaling data is provided, which solves the problem that the security monitoring of the network slice only from the operation and maintenance side is not comprehensive enough; by analyzing the security trend of the network slice, the network slice with security risks is managed securely, and the problem of illegal access to the network slice and the attack behavior of using the weaknesses in a certain network slice to move horizontally to another network slice is solved; the user's failure message is obtained, and the reason value related to the network slice in the failure message is extracted, which solves the problem of obtaining the reason value.
[0106] Figure 3 Schematic diagram of the process of the network slice security monitoring method provided in the embodiment of the present application Figure 2 .like Figure 3 As shown, in this embodiment Figure 2 Based on the embodiment, a security monitoring method for network slicing is described in detail. This embodiment provides a security monitoring method for network slicing, including:
[0107] S201, obtaining a failure message from a user;
[0108] S202. Extract at least one of a 5GMM Cause value of 62, a 5GMM Cause value of 91, a 5GMM Cause value of 67, and a 5GMM Cause value of 69 from the failure message;
[0109] Specifically, the failure message is the signaling data of the interaction between the user terminal and the network. When the user terminal fails to access the network or fails to initiate a service, the failure message will carry a 5GMM Cause value to indicate the cause of the failure. At this time, a failure message carries a cause value, and the cause value is the 5GMM Cause value. For example, the failure message can be a registration reject message (REGISTRATION REJECT message), a downlink NAS transport message (DL NAS TRANSPORT message), a deregistration request message (DEREGISTRATION REQUEST message), a service reject message (SERVICE REJECT message) or a security mode reject message (SECURITY MODE REJECT message).
[0110] From the failure message, extract one or more 5GMM Cause values related to the network slice. It should be noted that the one or more 5GMM Cause values here are exactly the same as the one or more cause values in S102. The 5GMM Cause value is pre-selected based on the 5GMM Cause. The 5GMM Cause includes multiple failure causes, and the 5GMM Cause value and binary encoding corresponding to each failure cause, where the 5GMM Cause value is the cause value. Table 1 is a 5GMM Cause screening table for multiple cause values related to network slicing.
[0111] Table 1:
[0112]
[0113] As shown in Table 1, when the failure cause is no available network slices (No network slices available), the corresponding 5GMM Cause value is 62, that is, there is no network slice requested to be accessed by the user terminal or the user terminal has not registered the requested network slice, and the requested service cannot be provided; when the 5GMM Cause value is 62, the 5GMM Cause value is a cause value related to the network slice, and one or more cause values include a 5GMM Cause value of 62.
[0114] When the failure cause is that the network data name is not supported or not subscribed in the network slice (DNN not supported or not subscribed in the slice), the corresponding 5GMM Cause value is 91, that is, the network slice selected by the network does not support or subscribe to the network data name (Data Network Name, DNN) of the user terminal, or the DNN is not supported or subscribed in the network slice indicated by the user terminal, and the requested service cannot be provided; when the 5GMM Cause value is 91, the 5GMMCause value is the cause value related to the network slice, and one or more cause values include a 5GMM Cause value of 91;
[0115] When the failure cause is insufficient resources for specific network slices and network data names (Insufficient resources for specific slice and DNN), the corresponding 5GMM Cause value is 67, that is, the requested service cannot be provided due to insufficient resources for specific network slices and DNN; when the 5GMM Cause value is 67, the 5GMM Cause value is a cause value related to the network slice, and one or more cause values include a 5GMM Cause value of 67;
[0116] When the cause of failure is insufficient resources for a specific network slice (Insufficient resources for a specific slice), the corresponding 5GMM Cause value is 69, that is, the requested service cannot be provided due to insufficient resources for the specific network slice; when the 5GMM Cause value is 69, the 5GMM Cause value is a cause value related to the network slice, and one or more cause values include a 5GMM Cause value of 69.
[0117] The failure causes corresponding to the above four 5GMM Cause values are related to network slicing. It can be understood that, when the number of at least one 5GMM Cause value among the above four 5GMM Cause values meets the quantity condition, it indicates that there are security risks in the network slicing.
[0118] In addition to the failure reasons corresponding to the 5GMM Cause values in Table 1 above, there are also many other failure reasons that are not related to network slicing that are not specified, for example: the failure reason corresponding to the 5GMM Cause value of 73 is Serving network not authorized, the failure reason corresponding to the 5GMM Cause value of 90 is Payload was not forwarded, and the failure reason corresponding to the 5GMM Cause value of 96 is Invalid mandatory information, etc.
[0119] The following is an example of extracting a cause value from a failure message provided by this embodiment:
[0120] For example, when a user terminal attempts to access the network or initiate a service, but fails to access the network or initiate a service for some reason, the security monitoring device may obtain a REGISTRATION REJECT message, a DL NASTRANSPORT message, a DEREGISTRATION REQUEST message, a SERVICE REJECT message, or a SECURITY MODE REJECT message, etc. In these messages, the 5GMM Cause value may be 1, 5, 16, 24, 28, 34 to 37, 50, 62, 67, 69, or 91, etc. The 5GMM Cause values of 62, 67, 69, and 91 are related to network slices, and the number of corresponding 5GMMCause values is increased by one.
[0121] Optionally, the safety monitoring device does not pre-store the failure cause of 5GMM Cause. When the safety monitoring device finds a 5GMM Cause value of 62, 67, 69 or 91 in the failure message through the built-in software code, the number of corresponding 5GMM Cause values is increased by one.
[0122] Furthermore, when the failure message is transmitted, it is represented by an eight-bit binary code, that is, the failure message usually only includes the binary code but not the cause value. The security monitoring module parses the binary code according to the 5GMM Cause and determines the cause value corresponding to each binary code, thereby extracting multiple cause values related to the network slice in the failure message.
[0123] In other embodiments, the security monitoring module extracts at least one binary code related to the network slice from the failure message, and analyzes the security trend of the network slice based on the at least one binary code.
[0124] In other embodiments, the security monitoring module actively extracts at least one 5GMM Cause value related to the network slice from the failure message. Specifically, a technician or a preset computer program actively extracts at least one of the above-mentioned multiple 5GMM Cause values.
[0125] In other embodiments, to facilitate the understanding and memory of technicians, the various cause values related to the network slice are correspondingly set to the first cause value, the second cause value, the third cause value and the fourth cause value. After extracting the 5GMMCause value from the failure message, the 5GMM Cause value of 62 is mapped to the first cause value, the 5GMM Cause value of 91 is mapped to the second cause value, the 5GMM Cause value of 67 is mapped to the third cause value, and the 5GMM Cause value of 69 is mapped to the fourth cause value.
[0126] S203. Obtain the number of at least one cause value among one or more cause values, and analyze the security trend of the network slice based on the number of at least one cause value.
[0127] In one possible design, S203 includes:
[0128] Obtain the quantity of at least one 5GMM Cause value among the one or more 5GMM Cause values, and analyze the security trend of the network slice based on the quantity of the at least one 5GMM Cause value.
[0129] In one possible design, after S203, the method also includes: sending early warning information to the operation and maintenance platform, so that the operation and maintenance platform can manage the network slice according to the early warning information.
[0130] This embodiment achieves the following technical effects: by parsing the failure cause of the failure message, the 5GMM Cause value corresponding to the failure cause is obtained, or by parsing the binary code of the failure message, the 5GMMCause value corresponding to the binary code is obtained, thereby solving the problem of how to determine the cause value corresponding to the failure message.
[0131] Figure 4 Schematic diagram of the process of the network slice security monitoring method provided in the embodiment of the present application Figure 3 In this embodiment Figure 3 Based on the embodiment, analyzing the security trend of network slicing according to the number of at least one 5GMM Cause value is described in detail.
[0132] In one possible design, the security trends of the network slice include: at least one of a security trend of being attacked and a security trend of insufficient resources.
[0133] Specifically, an attack on a network slice may lead to an increase in the number of 5GMM Cause values with a value of 62, or an increase in the number of 5GMM Cause values with a value of 91, or an increase in both values at the same time. Therefore, the number of 5GMM Cause values can be used to judge the security trend of the network slice being attacked; insufficient available resources in the network slice may lead to an increase in the number of 5GMM Cause values with a value of 67 and / or an increase in the number of 5GMM Cause values with a value of 69. Therefore, the security trend of insufficient available resources in the network slice can be judged by the number of 5GMM Cause values.
[0134] One of the above-mentioned multiple 5GMM Cause values may be extracted from the failure message. When the extracted 5GMM Cause value is 62 or 91, S2031 is executed alone; when the extracted 5GMM Cause value is 67 or 69, S2032 is executed alone.
[0135] Optionally, two of the above-mentioned multiple 5GMM Cause values may be extracted from the failure message. When the extracted 5GMMCause values are 62 and 91, S2031 is executed alone; when the extracted 5GMM Cause values are 67 and 69, S2032 is executed alone; when the extracted 5GMM Cause value is one of 62 and 91, and one of 67 and 69, S2031 and S2032 are executed simultaneously.
[0136] Optionally, three or four of the above-mentioned 5GMM Cause values can be extracted from the failure message, and S2031 and S2032 are executed simultaneously.
[0137] If Figure 4 As shown in the figure, the security trend of network slices is analyzed based on the number of at least one 5GMM Cause value, including:
[0138] S2031. Determine, according to the number of 5GMM Cause values having a value of 62 and / or the number of 5GMM Cause values having a value of 91, a security trend of the network slice being attacked;
[0139] Specifically, the method for judging the security trend according to the number of 5GMM Cause values may be that the number of 5GMM Cause values is greater than a preset threshold, or that the number of 5GMM Cause values is within a preset range, or that the increment of the number of 5GMM Cause values per unit time is greater than a preset threshold, or other unlisted methods. Among them, the preset threshold, preset range and unit time may be independently set by the technicians according to their work experience, or may be automatically generated by the security monitoring module according to the connection status of the network slice, which is not limited in this embodiment.
[0140] Optionally, the number of any 5GMM Cause values may be greater than a preset threshold, or the number of both 5GMMCause values may be greater than a preset threshold, and then the network slice is determined to be attacked, wherein the preset thresholds corresponding to the two 5GMM Cause values may be the same or different. For example, when the number of 5GMM Cause values with a value of 62 is greater than a first preset threshold, and / or the number of 5GMM Cause values with a value of 91 is greater than a second preset threshold, the security trend of the network slice being attacked is determined; the number of any 5GMM Cause values may be within a preset range, or the number of both 5GMM Cause values are within a preset range, and then the network slice is determined to be attacked, wherein the preset ranges corresponding to the two 5GMM Cause values may be the same or different; the number of any 5GMM Cause values may have an increment greater than a preset threshold within a unit time, or the number of both 5GMM Cause values may have an increment greater than a preset threshold within a unit time, and then the network slice is determined to be attacked, wherein the unit time and / or preset threshold corresponding to the two 5GMM Cause values may be the same or different; or a 5GMM If the number of Cause values is greater than a preset threshold and the number of another 5GMMCause values is within a preset range, it is determined that the network slice is attacked; other combinations of methods not listed are similar to the above methods and will not be repeated in this embodiment.
[0141] The following is a detailed description of one of the combinations of this embodiment. When the number of 5GMM Cause values with a value of 62 is greater than a preset threshold, it means that a large number of user terminals that are not registered for the target network slice are trying to access the target network slice; when the number of 5GMM Cause values with a value of 91 is greater than a preset threshold, it means that a large number of user terminals request network slices that do not match the DNN. Whether the former situation is met, the latter situation is met, or both situations are met at the same time, it means that relevant information of the target network slice may be leaked, and the target network slice may be subject to network attacks. Therefore, the security monitoring device sends a security warning message to the operation and maintenance platform, and the security warning message is used to warn the network slice security of the target network slice; after receiving the security warning message, the operation and maintenance platform performs security management on the target network slice to ensure the network security of the target network slice.
[0142] This implementation achieves the following technical effects: judging the security trend of network slices being attacked based on the number of 5GMM Cause values with a value of 62 and / or the number of 5GMM Cause values with a value of 91, and solving the problem of how to avoid network attacks when network slices may be attacked.
[0143] Figure 5 Schematic diagram of the process of the network slice security monitoring method provided in the embodiment of the present application Figure 4 .like Figure 5 As shown, in this embodiment Figure 3 and Figure 4 Based on the embodiment, analyzing the security trend of the network slice according to the number of at least one 5GMM Cause value is described in detail. Analyzing the security trend of the network slice according to the number of at least one 5GMM Cause value also includes:
[0144] S2032. Determine a security trend of insufficient network slice resources according to the number of 5GMM Cause values having a value of 67 and / or the number of 5GMM Cause values having a value of 69;
[0145] The method for judging the security trend according to the number of 5GMM Cause values in S3032 is similar to S2031. For example, when the number of 5GMM Cause values with a value of 67 is greater than the third preset threshold, and / or the number of 5GMM Cause values with a value of 69 is greater than the fourth preset threshold, the security trend of insufficient available resources of the network slice is judged. Among them, the numerical values of the first preset threshold, the second preset threshold, the third preset threshold and the fourth preset threshold are independent of each other and do not interfere with each other. The remaining methods are not described in detail in this embodiment.
[0146] The following is a detailed description of one of the combinations of this embodiment. When the number of 5GMM Cause values with a value of 67 is greater than a preset threshold, it means that the resources of the target network slice and DNN are insufficient; when the number of 5GMM Cause values with a value of 69 is greater than a preset threshold, it means that the resources of the target network slice are insufficient. Regardless of whether the former situation is met, the latter situation is met, or both situations are met at the same time, the operation and maintenance platform needs to decide whether to expand the capacity of the network slice and / or DNN resources, or to limit the flow and speed of the user terminal based on the business situation. Therefore, the security monitoring device sends resource warning information to the operation and maintenance platform, and the resource warning information is used to warn the available resources of the target network slice; after receiving the resource warning information, the operation and maintenance platform performs security management on the target network slice, that is, performs relevant disposal according to the above decision results.
[0147] It should be noted that after receiving the security warning information or resource warning information, the operation performed by the operation and maintenance platform is the same as the prior art, which will not be repeated in this embodiment; and the security monitoring device can send security warning information and / or resource warning information only to the operation and maintenance platform, and can also send security warning information and / or resource warning information to the operation and maintenance platform and a third-party server at the same time, which is not limited in this embodiment.
[0148] This implementation achieves the following technical effects: based on the number of 5GMM Cause values with a value of 67 and / or the number of 5GMM Cause values with a value of 69, the security trend of insufficient network slice resources is judged, and the problem of how to avoid insufficient network slice resources is solved.
[0149] In a possible design, when the security trend of the network slice includes: one of a security trend of being attacked and a security trend of insufficient resources, obtaining the number of at least one cause value among the one or more cause values, and analyzing the security trend of the network slice according to the number of the at least one cause value, including:
[0150] The number of one or two 5GMM Cause values among the one or more 5GMM Cause values is obtained, and the security trend of the network slice is analyzed according to the number of the one or two 5GMM Cause values.
[0151] Specifically, when the security trend of the network slice only includes: the security trend of being attacked, this security trend is the security trend to be analyzed, and one or two 5GMM Cause values are: a 5GMM Cause value of 62, and / or a 5GMM Cause value of 91; when the security trend of the network slice only includes: the security trend of insufficient resources, this security trend is the security trend to be analyzed, and one or two 5GMM Cause values are: a 5GMM Cause value of 67, and / or a 5GMM Cause value of 69.
[0152] It should be noted that the one or more 5GMM Cause values here are exactly the same as the one or more cause values in S102.
[0153] This embodiment achieves the following technical effects: when the security trend of the network slice only includes one of the security trends of being attacked and insufficient resources, only the number of corresponding one or two 5GMM Cause values is obtained, thereby reducing the amount of data collected.
[0154] In a possible design, the number of each 5GMM Cause value may be collected first, and then the security trend of the network slice may be analyzed based on the collected number. The number of at least one 5GMM Cause value among one or more 5GMM Cause values may be obtained, including:
[0155] The number of each 5GMM Cause value is obtained, wherein the number of 5GMM Cause values with a value of 62 and / or the number of 5GMM Cause values with a value of 91 are used to judge the security trend of the network slice being attacked; the number of 5GMM Cause values with a value of 67 and / or the number of 5GMM Cause values with a value of 69 are used to judge the security trend of insufficient network slice resources.
[0156] Specifically, the security monitoring device first obtains the number of each 5GMM Cause value related to the network slice, that is, simultaneously obtains the number of 5GMM Cause values of 62, 91, 67 or 69.
[0157] When the security trend of the network slice to be analyzed is a security trend of being attacked, the number of 5GMM Cause values with a value of 62 and / or the number of 5GMM Cause values with a value of 91 are obtained according to the number of each 5GMM Cause value, so as to continue to execute S2031.
[0158] When the security trend of the network slice to be analyzed is a security trend of insufficient resources, the number of 5GMM Cause values with a value of 67 and / or the number of 5GMM Cause values with a value of 69 are obtained according to the number of each 5GMM Cause value, so as to continue to execute S2032.
[0159] This embodiment achieves the following technical effects: the number of each 5GMM Cause value is obtained at the same time, so that according to the network trend to be analyzed, the network trend can be analyzed in time according to the number of each 5GMM Cause value obtained in advance, thereby improving data output efficiency.
[0160] In a possible design, it is also possible to first determine which security trend to analyze, and then obtain the number of corresponding 5GMM Cause values. Then obtaining the number of at least one 5GMM Cause value among one or more 5GMM Cause values includes:
[0161] Obtain security trends of the network slices to be analyzed;
[0162] When the security trend of the network slice to be analyzed is a security trend of being attacked, the number of 5GMMCause values with a value of 62 and / or the number of 5GMM Cause values with a value of 91 are obtained; when the security trend of the network slice to be analyzed is a security trend of insufficient resources, the number of 5GMM Cause values with a value of 67 and / or the number of 5GMM Cause values with a value of 69 are obtained.
[0163] This embodiment achieves the following technical effects: only one or two 5GMMCause values corresponding to the safety trend to be analyzed are obtained, thereby reducing the amount of data collected.
[0164] The embodiment of the present invention can divide the electronic device or the main control device into functional modules according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present invention is schematic and is only a logical function division. There may be other division methods in actual implementation.
[0165] Figure 6 A schematic diagram of the structure of a security monitoring device for a network slice provided in an embodiment of the present application. Figure 6 As shown, the safety monitoring device 131 provided in the embodiment of the present application includes: an acquisition module 1311, an extraction module 1312 and an analysis module 1313;
[0166] The acquisition module 1311 is used to acquire a failure message of the user, where the failure message is used to indicate that the user fails to access the network, or the user fails to initiate a service;
[0167] An extraction module 1312 is used to extract one or more cause values related to the network slice in the failure message;
[0168] The analysis module 1313 is used to obtain the number of at least one cause value among one or more cause values, and analyze the security trend of the network slice based on the number of at least one cause value.
[0169] In a possible design, the cause value is a 5GMM Cause value; and the security trend of the network slice includes: at least one of a security trend of being attacked and a security trend of insufficient resources.
[0170] In one possible design, the extraction module 1312 is used to extract one or more 5GMM Cause values related to the network slice from the failure message.
[0171] In one possible design, when the failure cause is no available network slice, the one or more cause values include a 5GMM Cause with a value of 62;
[0172] When the failure cause is that the network data name is not supported or subscribed in the network slice, one or more cause values include 5GMM Cause with a value of 91;
[0173] When the failure cause is insufficient resources for a specific network slice and network data name, one or more cause values include a 5GMM Cause with a value of 67;
[0174] When the cause of failure is insufficient resources in a specific network slice, one or more cause values include 5GMMCause with a value of 69.
[0175] In one possible design, the extraction module 1312 is used to extract at least one of a 5GMMCause value of 62, a 5GMM Cause value of 91, a 5GMM Cause value of 67, and a 5GMM Cause value of 69 from the failure message.
[0176] In one possible design, the analysis module 1313 is used to obtain the number of at least one 5GMM Cause value among one or more 5GMM Cause values, and analyze the security trend of the network slice based on the number of at least one 5GMM Cause value.
[0177] In one possible design, the analysis module 1313 is used to determine the security trend of the network slice being attacked based on the number of 5GMM Cause values with a value of 62 and / or the number of 5GMM Cause values with a value of 91.
[0178] In one possible design, the analysis module 1313 is used to determine the security trend of the network slice being attacked when the number of 5GMM Cause values with a value of 62 is greater than a first preset threshold and / or the number of 5GMM Cause values with a value of 91 is greater than a second preset threshold.
[0179] In one possible design, the analysis module 1313 is used to judge the security trend of insufficient network slice resources based on the number of 5GMM Cause values with a value of 67 and / or the number of 5GMM Cause values with a value of 69.
[0180] In one possible design, the analysis module 1313 is used to judge the security trend of insufficient network slice resources when the number of 5GMM Cause values with a value of 67 is greater than a third preset threshold and / or the number of 5GMM Cause values with a value of 69 is greater than a fourth preset threshold.
[0181] In a possible design, when the security trend of the network slice includes: one of the security trend of being attacked and the security trend of insufficient resources, the analysis module 1313 is used to obtain the number of one or two 5GMM Cause values among one or more 5GMM Cause values, and analyze the security trend of the network slice based on the number of one or two 5GMM Cause values.
[0182] In a possible design, the analysis module 1313 is used to obtain the number of each 5GMM Cause value, wherein the number of 5GMM Cause values with a value of 62 and / or the number of 5GMM Cause values with a value of 91 are both used to judge the security trend of the network slice being attacked; the number of 5GMM Cause values with a value of 67 and / or the number of 5GMM Cause values with a value of 69 are both used to judge the security trend of insufficient network slice resources.
[0183] In one possible design, the analysis module 1313 includes: a data acquisition module and a trend analysis module;
[0184] A data acquisition module, used to obtain the security trends of the network slices to be analyzed;
[0185] The trend analysis module is used to obtain the number of 5GMM Cause values with a value of 62 and / or the number of 5GMM Cause values with a value of 91 when the security trend of the network slice to be analyzed is a security trend of being attacked; when the security trend of the network slice to be analyzed is a security trend of insufficient resources, obtain the number of 5GMM Cause values with a value of 67 and / or the number of 5GMM Cause values with a value of 69.
[0186] In a possible design, the safety monitoring device 131 further includes: a sending module;
[0187] The sending module is used to send early warning information to the operation and maintenance platform so that the operation and maintenance platform can manage the network slices according to the early warning information.
[0188] A security monitoring device provided in this embodiment can execute a network slicing security monitoring method of the above embodiment. Its implementation principle and technical effects are similar, and this embodiment will not be repeated here.
[0189] In the specific implementation of the aforementioned network slice security monitoring method, each module can be implemented as a processor, and the processor can execute computer execution instructions stored in the memory, so that the processor executes the aforementioned network slice security monitoring method.
[0190] Figure 7 This is a schematic diagram of the structure of the electronic device hardware provided in the embodiment of the present application. Figure 7 As shown, the electronic device 200 includes: at least one processor 210 and a memory 220. The electronic device 200 also includes a communication component 230. The processor 210, the memory 220 and the communication component 230 are connected via a bus 240.
[0191] During the specific implementation process, at least one processor 210 executes computer execution instructions stored in the memory 220, so that at least one processor 210 executes a network slicing security monitoring method as performed on the electronic device side as above.
[0192] The specific implementation process of the processor 210 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.
[0193] In the above embodiments, it should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the invention may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.
[0194] The memory may include a high-speed RAM memory, and may also include a non-volatile storage NVM, such as at least one disk storage.
[0195] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.
[0196] The above-mentioned functions implemented by the electronic device and the main control device introduce the scheme provided by the embodiment of the present invention. It can be understood that in order to implement the above-mentioned functions, the electronic device or the main control device includes a hardware structure and / or software module corresponding to the execution of each function. In combination with the units and algorithm steps of each example described in the embodiment disclosed in the embodiment of the present invention, the embodiment of the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solution of the embodiment of the present invention.
[0197] The present application provides a computer-readable storage medium, which stores computer execution instructions. When the computer execution instructions are executed by a processor, they are used to implement a security monitoring method for a network slice as described above.
[0198] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.
[0199] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist as discrete components in an electronic device or a main control device.
[0200] The present application provides a computer program product, which includes a computer program. The computer program is stored in a readable storage medium. At least one processor of an electronic device can read the computer program from the readable storage medium. At least one processor executes the computer program so that the electronic device executes the solution provided by any of the above embodiments.
[0201] Those skilled in the art can understand that all or part of the steps of the above method embodiments can be completed by hardware related to program instructions. The above program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above method embodiments are executed; and the above storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.
[0202] So far, the technical solution of the present application has been described in conjunction with the preferred embodiments shown in the accompanying drawings. However, it is easy for those skilled in the art to understand that the protection scope of the present application is obviously not limited to these specific embodiments, and the above embodiments are only used to illustrate the technical solution of the present application rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein by equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.
Claims
1. A network slice security monitoring method, characterized in that: The method comprises: Obtaining a failure message from the user, where the failure message is used to indicate that the user has failed to access the network, or that the user has failed to initiate a service; Extracting one or more cause values related to the network slice in the failure message; Obtain the quantity of at least one cause value among the one or more cause values, and analyze the security trend of the network slice based on the quantity of the at least one cause value.
2. The method according to claim 1, characterized in that: The cause value is a 5GMM Cause value; The security trend of the network slice includes: at least one of a security trend of being attacked and a security trend of insufficient resources.
3. The method according to claim 2, characterized in that The extracting one or more cause values related to the network slice in the failure message includes: From the failure message, extract one or more 5GMM Cause values related to the network slice.
4. The method according to claim 2, characterized in that: When the failure cause is no available network slice, the one or more cause values include a 5GMM Cause with a value of 62; When the failure cause is that the network data name is not supported or subscribed in the network slice, the one or more cause values include a 5GMM Cause with a value of 91; When the failure cause is insufficient resources for a specific network slice and network data name, the one or more cause values include a 5GMM Cause with a value of 67; When the cause of failure is insufficient resources of a specific network slice, the one or more cause values include 5GMMCause with a value of 69.
5. The method according to claim 3, characterized in that: Extracting one or more 5GMM Cause values related to the network slice from the failure message includes: At least one of a 5GMM Cause value of 62, a 5GMM Cause value of 91, a 5GMM Cause value of 67, and a 5GMM Cause value of 69 is extracted from the failure message.
6. The method according to any one of claims 2 to 5, characterized in that: The obtaining the quantity of at least one cause value among the one or more cause values, and analyzing the security trend of the network slice according to the quantity of the at least one cause value, includes: Obtain the quantity of at least one 5GMM Cause value among one or more 5GMM Cause values, and analyze the security trend of the network slice based on the quantity of the at least one 5GMM Cause value.
7. The method according to claim 6, characterized in that The analyzing, according to the number of the at least one 5GMM Cause value, a security trend of the network slice includes: According to the number of 5GMM Cause values whose value is 62 and / or the number of 5GMM Cause values whose value is 91, the security trend of the network slice being attacked is judged.
8. The method according to claim 6, characterized in that The analyzing, according to the number of the at least one 5GMM Cause value, a security trend of the network slice includes: According to the number of 5GMM Cause values whose value is 67 and / or the number of 5GMM Cause values whose value is 69, the security trend of insufficient network slice resources is judged.
9. The method according to claim 6, characterized in that When the security trend of the network slice includes: one of a security trend of being attacked and a security trend of insufficient resources, obtaining the number of at least one cause value among the one or more cause values, and analyzing the security trend of the network slice according to the number of the at least one cause value, includes: Obtain the quantity of one or two 5GMM Cause values among the one or more 5GMM Cause values, and analyze the security trend of the network slice based on the quantity of the one or two 5GMM Cause values.
10. The method according to claim 6, characterized in that The obtaining the quantity of at least one 5GMM Cause value among the one or more 5GMM Cause values includes: The number of each 5GMM Cause value is obtained, wherein the number of 5GMM Cause values with a value of 62 and / or the number of 5GMM Cause values with a value of 91 are both used to judge the security trend of the network slice being attacked; the number of 5GMM Cause values with a value of 67 and / or the number of 5GMM Cause values with a value of 69 are both used to judge the security trend of insufficient resources of the network slice.
11. The method according to claim 6, characterized in that The obtaining the quantity of at least one 5GMM Cause value among the one or more 5GMM Cause values includes: Obtain security trends of the network slices to be analyzed; When the security trend of the network slice to be analyzed is a security trend of being attacked, the number of 5GMM Cause values with a value of 62 and / or the number of 5GMM Cause values with a value of 91 are obtained; when the security trend of the network slice to be analyzed is a security trend of insufficient resources, the number of 5GMM Cause values with a value of 67 and / or the number of 5GMM Cause values with a value of 69 are obtained.
12. A network slice security monitoring device, characterized in that: The device comprises: An acquisition module, used to acquire a failure message of a user, wherein the failure message is used to indicate that the user fails to access the network, or that the user fails to initiate a service; An extraction module, used to extract one or more cause values related to the network slice in the failure message; The analysis module is used to obtain the quantity of at least one cause value among the one or more cause values, and analyze the security trend of the network slice based on the quantity of the at least one cause value.
13. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the security monitoring method for network slicing as described in any one of claims 1 to 11.
14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer execution instructions, which, when executed by a processor, are used to implement the network slicing security monitoring method as described in any one of claims 1 to 11.
15. A computer program product, characterized in that The computer program product includes a computer program, which, when executed by a processor, is used to implement the security monitoring method for network slicing as described in any one of claims 1 to 11.
