Slice setting method, system, server, and storage medium
The method automates IPsec tunnel configuration with SeGWs to achieve efficient end-to-end isolation and protection of network slice data, addressing the inefficiencies in dynamic network slice deployments.
Patent Information
- Application Number
- JP2024531099
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-12-21
- Filing Date
- 2022-12-19
- Publication Date
- 2025-01-17
- Estimated Expiration
- 2042-12-19
AI Technical Summary
Existing 3GPP protocols lack detailed methods for dynamically protecting and separating data flows of different network slices, especially in scenarios where SeGWs need to be dynamically orchestrated and configured, leading to inefficiencies in end-to-end isolation and protection of sliced data over IPsec tunnels.
A method and system for automatically establishing an IPsec tunnel with the SeGW of a core network slice by associating network slice configuration information with IPsec tunnel indices, acquiring SeGW configuration information, and mapping slice configuration to the tunnel, using preconfigured security protocols and dynamic orchestration.
Enables quick end-to-end isolation and protection of network slice data by automating IPsec tunnel configuration, overcoming the limitations of manual configuration and enhancing flexibility in dynamic network slice deployments.
Smart Images

Figure 2025501058000001_ABST
Abstract
Description
[Technical field]
[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a slice setting method, system, server, and storage medium. [Background technology]
[0002] The TS23.501 protocol of the 3rd Generation Partnership Project (abbreviated as 3GPP (registered trademark)) defines the service flow and configuration mode of network slices in detail, and the introduction of network slices makes it possible to divide different logical networks in the same hardware network. The core of network slices is resource separation, which has been widely applied in fields such as industrial control networks and virtual operators, and is an important technical measure for the fifth generation communication network (5th Generation, abbreviated as 5G) to support the development of new services.
[0003] Network slices refer to network elements such as terminals, radio access networks, bearer networks, and core networks, and the network slice identifiers corresponding to network elements and devices in different areas are different, and the separation techniques used are also different. From the perspective of service flow, 3GPP defines in detail the signaling flow format of network slices from the terminal side to the core network, but due to the differentiation of deployment scenarios, 3GPP does not explain in detail how to protect data flows of different slices or how to separate data flows of different slices. Data protection methods in conventional networks are diverse, and different network layers have different security protocols, such as the link layer security protocol (Media Access Control Security, abbreviated as MACSec) at the link layer, the network layer security protocol (Internet Protocol Security, abbreviated as IPsec) at the network layer, and the transport layer security protocol (Transport Layer Security, abbreviated as TLS) at the transport layer. In 3GPP, it is recommended to use the IPsec protocol as the security protection protocol for 5G networks.
[0004] The deployment method recommended by 3GPP is that a base station or edge access network element establishes an IPsec tunnel with a security gateway (SeGW) deployed on the core network side through IPsec protocol, and protects data security from the base station or edge access network element to the core network. However, since the conventional SeGWs are all physical devices, when slices change dynamically according to service needs, the physical SeGW cannot adapt well to the expansion of current services due to limitations in location and configuration. For example, for low-latency application scenarios, the core network needs to be deployed downstream in the edge cloud of the access network, so it is not convenient to relocate a single SeGW device to the edge cloud and synchronize and provision it. The 5G core network uses virtualization technology, and the orchestrator dynamically creates virtual network elements according to service needs. When the SeGW is also virtualized, it can be orchestrated by the same orchestrator together with the core network network elements, thus solving the problem of flexibility in deployment and configuration of physical SeGW. However, the IPsec tunnel is completed by the base station or edge access network element in cooperation with the SeGW, and the SeGW on the core network side needs to support dynamic orchestration, so it is very difficult for the base station or edge access network element to apply the orchestration policy of the dynamic SeGW on the core network side. In addition, most of the base stations or edge access network elements are dedicated devices that do not support virtualization orchestration, and the base station or access network element needs to be manually configured to cooperate with the SeGW dynamic allocation on the core network side, which takes a long time to manually configure and has certain requirements for operators, making it difficult to quickly realize end-to-end isolation and protection of slice data in the IPsec tunnel. Summary of the Invention [Problem to be solved by the invention]
[0005] The embodiments of the present application provide a slice configuration method, a system, a server, and a storage medium, which aim to realize end-to-end isolation and protection of network slice data in an IPsec tunnel by automatically establishing an IPsec tunnel with a SeGW of a core network slice and mapping slice configuration information of the network slice to a corresponding IPsec tunnel. [Means for solving the problem]
[0006] An embodiment of the present application provides a slice configuration method applicable to a base station or an edge access network element, which includes the steps of: when a network slice is successfully created, associating the network slice with IPsec tunnel configuration information corresponding to a preset network layer security protocol IPsec slice tunnel index by the IPsec slice tunnel index; acquiring SeGW configuration information of the SeGW corresponding to the core network slice from the core network corresponding to the base station or the edge access network element based on a preset security gateway SeGW information acquisition method; creating an IPsec tunnel between the base station or the edge access network element and the SeGW based on the IPsec tunnel configuration information and the SeGW configuration information; and acquiring slice configuration information of the network slice, mapping the slice configuration information to the IPsec tunnel, and completing the configuration of the network slice.
[0007] An embodiment of the present application further provides a slice configuration system applied to a base station or an edge access network element, the system including an association module, an acquisition module, a creation module, and a mapping module. The association module is configured to associate the network slice with IPsec tunnel configuration information corresponding to the IPsec slice tunnel index by a preset network layer security protocol IPsec slice tunnel index when the creation of the network slice is successful. The acquisition module is configured to acquire SeGW configuration information of the SeGW corresponding to the core network slice from the core network corresponding to the base station or the edge access network element based on a preset security gateway SeGW information acquisition manner. The creation module is configured to create an IPsec tunnel between the base station or the edge access network element and the SeGW based on the IPsec tunnel configuration information and the SeGW configuration information. The mapping module is configured to acquire slice configuration information of the network slice, and map the slice configuration information to the IPsec tunnel to complete the configuration of the network slice.
[0008] An embodiment of the present application further provides a server including at least one processor and a memory communicatively connected to the at least one processor, the memory storing instructions executable by the at least one processor, the instructions, when executed by the at least one processor, causing the at least one processor to perform the above-mentioned slice setting method.
[0009] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon, the computer-readable storage medium realizing the slice setting method when the computer program is executed by a processor. [Brief description of the drawings]
[0010] [Figure 1] FIG. 1 is a schematic diagram of an application environment of an embodiment of the present application. [Diagram 2] 1 is a flowchart of a slice setting method according to an embodiment of the present application. [Diagram 3] 1 is a flowchart of a slice setting method according to an embodiment of the present application. [Figure 4] 1 is a flowchart of a slice setting method according to an embodiment of the present application. [Diagram 5] 1 is a schematic configuration diagram of a slice setting system according to an embodiment of the present application. [Figure 6] FIG. 2 is a schematic configuration diagram of a server according to an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] In order to clarify the purpose, technical means and advantages of the embodiments of the present application, the embodiments of the present application will be described in detail below with reference to the drawings. However, as will be understood by those skilled in the art, many technical details are provided in the embodiments of the present application to allow the reader to better understand the embodiments of the present application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical means claimed in the embodiments of the present application can be realized. The division of the following embodiments is for ease of explanation and does not impose any limitations on the specific implementation manner of the embodiments of the present application, and the embodiments can be combined and used together as long as they are not inconsistent.
[0012] The application environment of the embodiments of the present application is as shown in FIG. 1. The embodiments of the present application may be applied to a base station, particularly a 5G base station, or may be applied to an edge access network element, where the edge access network element may be an IT device having some base station functions, such as an edge computing device (abbreviated as Mobile Edge Computing, MEC) or a base station local offload gateway, the IPsec function is a protocol module of the base station or the edge access network element, the device connected to the base station or the edge access network element is a core network, particularly a 5G core network, the core network may be disposed in a core computer room, or may be disposed in an edge cloud or an industrial application center, the SeGW is a gateway device disposed in front of the core network and is mainly responsible for the IPsec function of the core network, and the orchestrator is a controller for dynamic resource orchestration management of the virtualized core network.
[0013] One embodiment of the present application relates to a slice setting method, which includes the following steps 101 to 104 as shown in FIG.
[0014] In step 101, if the creation of the network slice is successful, the network slice is associated with IPsec tunnel setting information corresponding to the pre-set network layer security protocol IPsec slice tunnel index by the IPsec slice tunnel index.
[0015] In one exemplary implementation, after a base station or an edge access network element successfully creates a network slice, it obtains a slice identifier of the network slice, which can uniquely represent the network slice, and by filling the slice identifier into a specified position of the IPsec slice tunnel index, it is possible to associate the network slice with IPsec tunnel setting information corresponding to the IPsec slice tunnel index.
[0016] In one exemplary implementation, the IPsec tunnel configuration information may be created after the creation of the network slice or may be pre-configured before the creation of the network slice.
[0017] In step 102, based on a preset security gateway SeGW information acquisition method, SeGW configuration information of the SeGW corresponding to the core network slice is acquired from a core network corresponding to a base station or an edge access network element.
[0018] In an exemplary implementation, the security gateway SeGW corresponding to the core network slice may be a physical arrangement or a logical arrangement, and the reason why the security gateway SeGW configuration information needs to be acquired is that the IPsec configuration information is not defined in the service signaling of 3GPP, and the IPsec tunnel of the security gateway SeGW and the base station or the edge access network element is defined as an external device or module in 3GPP, so when the network slice changes dynamically, it is necessary to be able to acquire the information of the counterpart security gateway SeGW. The pre-configured SeGW information acquisition method in the embodiment of the present application mainly includes a static configuration acquisition method, a primary SeGW acquisition method, a service signaling acquisition method, an orchestrator acquisition method, or a domain name acquisition method, and the SeGW configuration information of the SeGW corresponding to the core network slice may be acquired from the core network corresponding to the base station or the edge access network element by any one of the above SeGW information acquisition methods.
[0019] In an exemplary embodiment, the static configuration acquisition manner includes a user configuring SeGW configuration information of a security gateway SeGW corresponding to a core network slice and synchronizing it with a base station or an edge access network element; the primary SeGW acquisition manner includes acquiring SeGW configuration information from a designated primary SeGW in a core network by a Configuration or Notify payload of a customized IPsec IKE protocol; and the service signaling acquisition manner includes acquiring SeGW configuration information by receiving service signaling sent from a core network, and the core network acquires the SeGW configuration information by synchronizing it with a core network slice. The SeGW configuration information of the SeGW corresponding to the core network slice is set in the service signaling, the orchestrator acquisition method includes acquiring the SeGW configuration information according to interaction information sent from an orchestrator of the core network, the SeGW configuration information is set in the orchestrator, and the SeGW configuration information is stored in the interaction information sent from the orchestrator, and the domain name acquisition method includes acquiring an IP address corresponding to the SeGW corresponding to the core network slice by setting the domain name, connecting to the SeGW corresponding to the core network slice according to a default algorithm, and acquiring the SeGW configuration information from the SeGW corresponding to the core network slice.
[0020] In one exemplary implementation, the acquired SeGW configuration information includes information such as a SeGW address, SeGW service flow information, and a SeGW algorithm set, where the SeGW algorithm set refers to algorithms for processing service flows supported by the security gateway SeGW, such as encryption algorithms, decryption algorithms, encapsulation algorithms, etc., and is not limited thereto. If the SeGW does not configure an algorithm set, it uses a default algorithm set by default.
[0021] In step 103, an IPsec tunnel is created between the base station or edge access network element and the SeGW based on the IPsec tunnel setting information and the SeGW setting information.
[0022] In one exemplary implementation, the IPsec tunnel setting information is information for describing the created IPsec tunnel, and after obtaining the SeGW setting information, a network layer security protocol IPsec tunnel can be created between the base station or edge access network element and the security gateway SeGW based on the IPsec tunnel setting information and the SeGW setting information.
[0023] In step 104, slice configuration information of the network slice is obtained, and the slice configuration information is mapped to the IPsec tunnel to complete the configuration of the network slice.
[0024] In one exemplary implementation, the slice configuration information includes information such as a slice identifier, a network element IP address of the core network corresponding to the slice, slice service flow information, and slice service quality requirements. After obtaining the slice configuration information, based on the slice identifier, the slice configuration information is mapped to a network layer security protocol IPsec tunnel associated with the slice identifier. In fact, mapping means that the network layer security protocol IPsec tunnel processes the service flow of the network slice and transmits it to the security gateway SeGW by filling the slice configuration information into the parameter information of the network layer security protocol IPsec tunnel.
[0025] In this embodiment, in the process of setting a slice on the base station or edge access network element side, if the creation of a network slice is successful, the network slice is associated with IPsec tunnel setting information corresponding to the IPsec slice tunnel index by a preset network layer security protocol IPsec slice tunnel index, and according to a preset security gateway SeGW information acquisition method, SeGW setting information of the SeGW corresponding to the core network slice is acquired from the core network corresponding to the base station or the edge access network element, and an IPsec tunnel is created between the base station or the edge access network element and the core network based on the IPsec tunnel setting information and the SeGW setting information. , obtain the slice setting information of the network slice, map the slice setting information to the IPsec tunnel, complete the setting of the network slice, and actively interact with the SeGW corresponding to the core network slice to automatically establish an IPsec tunnel with the SeGW of the core network slice. By mapping the slice setting information of the network slice to the corresponding IPsec tunnel, end-to-end separation and protection of network slice data in the IPsec tunnel is quickly realized, and the technical problem of not being able to quickly realize end-to-end separation and protection of slice data in the IPsec tunnel by manually configuring the base station or edge access network element and cooperating with the SeGW dynamic allocation on the core network side is solved.
[0026] One embodiment of the present application relates to a slice setting method, which includes the following steps 201 to 205 as shown in FIG.
[0027] In step 201, if the creation of the network slice is successful, the network slice is associated with IPsec tunnel setting information corresponding to the pre-set network layer security protocol IPsec slice tunnel index by the IPsec slice tunnel index.
[0028] In an exemplary embodiment, this step is almost the same as step 101 in the embodiment of the present application, and the description is omitted here.
[0029] In step 202, based on a preset security gateway SeGW information acquisition method, the SeGW configuration information of the SeGW corresponding to the core network slice is acquired from the core network corresponding to the base station or edge access network element.
[0030] In an exemplary embodiment, this step is almost the same as step 102 in the embodiment of the present application, and the description is omitted here.
[0031] In step 203, an IPsec tunnel is created between the base station or edge access network element and the SeGW based on the IPsec tunnel setting information and the SeGW setting information.
[0032] In an exemplary embodiment, this step is almost the same as step 103 in the embodiment of the present application, and the description is omitted here.
[0033] In step 204, slice configuration information of the network slice is obtained, and the slice configuration information is mapped to the IPsec tunnel to complete the configuration of the network slice.
[0034] In an exemplary embodiment, this step is almost the same as step 104 in the embodiment of the present application, and the description is omitted here.
[0035] In step 205, when the network slice or core network slice is changed, the IPsec tunnel is modified based on the change in the network slice or core network slice, and resources of the base station, edge access network element, or core network that were occupied before the change in the network slice or core network slice are released.
[0036] In one exemplary implementation, after establishing a network layer security protocol IPsec tunnel between a network slice of a base station or an edge access network element and a security gateway SeGW corresponding to a core network slice, status monitoring may be performed on the network slice and / or the core network slice, and when the network slice and / or the core network slice are changed (the change may be deletion, termination or other service change), the change occurring in the network slice and / or the core network slice is recorded, and then, based on the recorded change occurring in the network slice and / or the core network slice, the same change is made to the network layer security protocol IPsec tunnel, and further resources of the base station or the edge access network element or the core network that were occupied before the change in the network slice and / or the core network slice need to be released.
[0037] In an embodiment of the present application, based on another embodiment, after a network slice or a core network slice is changed, the IPsec tunnel is synchronously changed in the same manner as the network slice based on the change status of the network slice or the core network slice, thereby always maintaining consistency between the network slice or the core network slice and the IPsec tunnel, releasing resources of the base station or the edge access network element or the core network occupied before the change of the network slice or the core network slice, and improving the resource utilization rate of the base station or the edge access network element or the core network.
[0038] One embodiment of the present application relates to a slice setting method, which includes the following steps 301 to 306 as shown in FIG.
[0039] In step 301, slice planning information of a user is obtained through a human-computer interaction interface, and the slice planning information includes slice setting information, an IPsec slice tunnel index, and an acquisition manner of SeGW information.
[0040] In one exemplary implementation, before a base station or an edge access network element creates a network slice and makes related settings for the network slice, it needs to interact with a user through a human-computer interaction interface, in which information that the user needs to specify is displayed, and based on the user's input in the human-computer interaction interface, the user's slice planning information is obtained, and the information specified by the user includes information such as slice setting information, IPsec slice tunnel index, and SeGW information acquisition method.
[0041] In step 302, a network slice is created based on the slice setting information.
[0042] In one exemplary implementation, after obtaining slice setting information specified by a user through a human-computer interaction interface, a network slice can be created based on the slice setting information specified by the user, and if the network slice is successfully created, subsequent slice setting operations are performed on the created network slice based on the acquisition manner of the IPsec slice tunnel index and SeGW information.
[0043] In step 303, if the network slice is successfully created, the network slice is associated with the IPsec tunnel setting information corresponding to the IPsec slice tunnel index by the IPsec slice tunnel index.
[0044] In an exemplary embodiment, this step is almost the same as step 101 in the embodiment of the present application, and the description is omitted here.
[0045] In step 304, based on a SeGW information acquisition method, the SeGW configuration information of the SeGW corresponding to the core network slice is acquired from the core network corresponding to the base station or the edge access network element.
[0046] In an exemplary embodiment, this step is almost the same as step 102 in the embodiment of the present application, and the description is omitted here.
[0047] In step 305, an IPsec tunnel is created between the base station or edge access network element and the SeGW based on the IPsec tunnel setting information and the SeGW setting information.
[0048] In an exemplary embodiment, this step is almost the same as step 103 in the embodiment of the present application, and the description is omitted here.
[0049] In step 306, slice configuration information of the network slice is obtained, and the slice configuration information is mapped to the IPsec tunnel to complete the configuration of the network slice.
[0050] In an exemplary embodiment, this step is almost the same as step 104 in the embodiment of the present application, and the description is omitted here.
[0051] In an embodiment of the present application, based on another embodiment, a user is interacted with through a human-computer interaction interface to obtain the user's needs for a network slice and specifications for a method of acquiring SeGW information, so that the network slice created in the present application can meet the user's service needs.
[0052] The division of the steps of the above various methods is merely for the purpose of clarity of description, and may be combined into one step in implementation, or some steps may be divided into multiple steps, but as long as they contain the same logical relationship, they are all within the scope of protection of this patent. Adding non-significant changes to the algorithm or process, or introducing non-significant designs, is also within the scope of protection of this patent, as long as it does not change the core design of the algorithm and process.
[0053] Another embodiment of the present application relates to a slice setting system, and the details of the slice setting system of this embodiment will be described in detail below. However, the following content is merely implementation details provided for ease of understanding and is not essential to implementing this example. Figure 5 is a schematic diagram of the slice setting system of this embodiment, including an association module 401, an acquisition module 402, a creation module 403, and a mapping module 404.
[0054] When the creation of the network slice is successful, the association module 401 is configured to associate the network slice with IPsec tunnel setting information corresponding to the IPsec slice tunnel index by a preset network layer security protocol IPsec slice tunnel index.
[0055] The acquisition module 402 is configured to acquire SeGW configuration information of the SeGW corresponding to the core network slice from a core network corresponding to a base station or an edge access network element based on a predetermined security gateway SeGW information acquisition manner.
[0056] The creating module 403 is configured to create an IPsec tunnel between a base station or an edge access network element and a SeGW according to the IPsec tunnel setting information and the SeGW setting information.
[0057] The mapping module 404 is configured to obtain slice configuration information of the network slice, and map the slice configuration information to the IPsec tunnel to complete the configuration of the network slice.
[0058] This embodiment is a system embodiment corresponding to the above method embodiment, and it is easy to understand that this embodiment can be implemented in combination with the above method embodiment. The relevant technical details and technical effects mentioned in the above embodiment are still valid in this embodiment, and will not be described here to reduce duplication. Accordingly, the relevant technical details mentioned in this embodiment may be applied to the above embodiment.
[0059] It should be noted that the embodiment of the system is primarily a description at the software implementation level of the slice setting method according to the embodiment of the method, the implementation of which needs to rely on hardware support, e.g., the functionality of the association module may be located in a processor, whereby the processor executes to realize the corresponding functionality, and the associated data generated by the execution may be stored in memory for subsequent inspection and use.
[0060] In addition, each module in the present embodiment is a logic module, and in practical application, one logic unit may be one physical unit, may be a part of one physical unit, and may be realized by a combination of multiple physical units. In addition, in order to highlight the inventive part of the embodiment of the present application, the embodiment does not introduce a unit that is not closely related to the solution of the technical problem presented in the embodiment of the present application, but this does not mean that there are no other units in the embodiment.
[0061] Another embodiment of the present application relates to a server, and as shown in FIG. 6, the server includes at least one processor 501 and a memory 502 communicatively connected to the at least one processor 501, the memory 502 storing instructions executable by the at least one processor 501, the instructions, when executed by the at least one processor 501, causing the at least one processor 501 to execute the slice setting method of each of the above embodiments.
[0062] The memory and the processor are connected in a bus manner, which may include any number of interconnected buses and bridges, and which connect various circuits of one or more processors and memories. The bus may further connect various other circuits, such as peripherals, voltage regulators, and power management circuits, all of which are well known in the art and will not be described further herein. The bus interface provides an interface between the bus and the transceiver. The transceiver may be a single element or multiple elements, for example including multiple receivers and transmitters, providing a means for communicating with various other devices over a transmission medium. The data processed by the processor is transmitted to a wireless medium via an antenna, which further receives and transmits data to the processor.
[0063] The processor manages the bus and normal processing, and may provide a variety of functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions, and the memory may store data used by the processor in performing operations.
[0064] Another embodiment of the present application relates to a computer readable storage medium having stored thereon a computer program which, when executed by a processor, results in the implementation of the above method embodiment.
[0065] That is, as will be understood by those skilled in the art, the implementation of all or part of the steps in the methods of the above embodiments can be performed by issuing instructions to related hardware by a program, and the program is stored in one storage medium and includes several instructions for causing one device (which may be a one-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps in the methods of the embodiments of the present application. The above-mentioned storage medium includes various media capable of storing program codes, such as a USB flash drive, a removable hard disk, a read-only memory (abbreviated as ROM), a random access memory (abbreviated as RAM), a magnetic disk, or an optical disk.
[0066] As will be understood by those skilled in the art, the above-mentioned embodiments are specific examples for realizing the present application, and in actual application, various changes in form and details can be made without departing from the spirit and scope of the embodiments of the present application.
Claims
1. A slice setting method applied to a base station or an edge access network element, comprising: If the creation of the network slice is successful, by using a preset network layer security protocol IPsec slice tunnel index, the network slice is associated with IPsec tunnel configuration information corresponding to the IPsec slice tunnel index; Acquiring SeGW configuration information of the SeGW corresponding to the core network slice from the core network corresponding to the base station or the edge access network element based on a preset security gateway SeGW information acquisition method; creating an IPsec tunnel between the base station or the edge access network element and the SeGW based on the IPsec tunnel configuration information and the SeGW configuration information; A slice configuration method comprising the steps of obtaining slice configuration information of the network slice, mapping the slice configuration information to the IPsec tunnel, and completing configuration of the network slice.
2. The slice configuration method of claim 1, wherein the method of acquiring the SeGW information includes a static setting acquisition method, a primary SeGW acquisition method, a service signaling acquisition method, an orchestrator acquisition method, or a domain name acquisition method.
3. The static configuration acquisition manner includes: a user configures the SeGW configuration information of the SeGW corresponding to the core network slice and synchronizes with the base station or the edge access network element; The primary SeGW acquisition method includes acquiring the SeGW configuration information from a designated primary SeGW in the core network by a preset payload; The service signaling acquisition method includes acquiring the SeGW configuration information by receiving service signaling transmitted from the core network, and the core network sets the SeGW configuration information of the SeGW corresponding to the core network slice in the service signaling; The acquisition method of the orchestrator includes acquiring the SeGW configuration information by interaction information transmitted from an orchestrator of the core network, the SeGW configuration information is configured in the orchestrator, and the SeGW configuration information is stored in the interaction information transmitted from the orchestrator; The slice configuration method of claim 2, wherein the domain name acquisition method includes acquiring an IP address corresponding to the SeGW corresponding to the core network slice by domain name setting, connecting to the SeGW corresponding to the core network slice by a default algorithm, and acquiring the SeGW configuration information from the SeGW corresponding to the core network slice.
4. After obtaining slice configuration information of the network slice and mapping the slice configuration information to the IPsec tunnel to complete configuration of the network slice, the method includes: The slice setting method according to claim 1, further comprising the step of: when the network slice or the core network slice is changed, changing the IPsec tunnel based on the change in the network slice or the core network slice, and releasing resources of the base station, the edge access network element, or the core network that were occupied before the change in the network slice or the core network slice.
5. The step of associating the network slice with IPsec tunnel configuration information corresponding to a preset IPsec slice tunnel index by the preset IPsec slice tunnel index includes: obtaining a slice identifier of the network slice; The slice setting method according to claim 1 , further comprising filling the slice identifier into a specified position of the IPsec slice tunnel index to complete association of the network slice with the IPsec tunnel setting information.
6. If the creation of the network slice is successful, before associating the network slice with IPsec tunnel configuration information corresponding to a pre-configured network layer security protocol IPsec slice tunnel index, the method includes: Acquiring slice planning information of a user through a human-computer interaction interface, the slice planning information including the slice setting information, the IPsec slice tunnel index, and an acquisition manner of the SeGW information; The slice setting method according to any one of claims 1 to 5, further comprising the step of creating the network slice based on the slice setting information.
7. The slice configuration method according to any one of claims 1 to 5, wherein the SeGW configuration information includes an SeGW address, SeGW service flow information and an SeGW algorithm set, and the slice configuration information includes a slice identifier, a core network element IP address corresponding to the slice, slice service flow information and slice service quality requirements.
8. A slice configuration system applied to a base station or an edge access network element, comprising: an association module, an acquisition module, a creation module, and a mapping module; The association module is configured to, when the creation of the network slice is successful, associate the network slice with IPsec tunnel setting information corresponding to a preset network layer security protocol IPsec slice tunnel index by the preset network layer security protocol IPsec slice tunnel index; The acquisition module is configured to acquire SeGW configuration information of an SeGW corresponding to a core network slice from a core network corresponding to the base station or the edge access network element according to a preset security gateway SeGW information acquisition manner; The creation module is configured to create an IPsec tunnel between the base station or the edge access network element and the SeGW based on the IPsec tunnel configuration information and the SeGW configuration information; A slice configuration system, wherein the mapping module is configured to obtain slice configuration information of the network slice, map the slice configuration information to the IPsec tunnel, and complete configuration of the network slice.
9. At least one processor; a memory in communication with the at least one processor; A server, wherein the memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, cause the at least one processor to execute a slice setting method described in any one of claims 1 to 7.
10. A computer-readable storage medium having a computer program stored thereon, the computer-readable storage medium implementing the slice setting method according to any one of claims 1 to 7 when the computer program is executed by a processor.
Citation Information
Patent Citations
Data security implementation method and related equipment
CN111147273A
Methods for supporting QoS and SMF
JP2020523936A
Apparatus and method for controller and slice-based security gateway for 5g
US20200267623A1
Data protection method and apparatus, and computer storage medium
WO2020025028A1
Method for ensuring data delivery and communication device
WO2020119596A1