Mmtc network slice mapping method and system based on group authentication
By introducing group authentication and dynamic traffic models into mMTC network slice mapping, the access and resource mapping of MTC devices are optimized, and the access efficiency and poor resource mapping are solved due to the neglect of group authentication requirements in the prior art. The problem has achieved more efficient resource utilization and disaster recovery capabilities.
Patent Information
- Application Number
- PCT/CN2023/139994
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-30
- Filing Date
- 2023-12-19
- Publication Date
- 2024-12-05
AI Technical Summary
The establishment and resource mapping scheme of existing mMTC network slices ignore group authentication requirements, resulting in low access authentication efficiency and poor resource mapping for large-scale IoT devices when entering the network.
Using the mMTC network slice mapping method based on group authentication, we can obtain slice requests, perform group leader elections of MTC devices, judge service types, build a dynamic slice request traffic model, and perform node-to-link mapping to meet different service types QoS requirements, optimize resource deployment and mapping strategies.
It effectively reduces the slice blocking rate, balances the resource consumption of optical network bandwidth resources and edge node processing, improves the practicality of resource deployment and mapping, and adapts to massive IoT device access and network disaster recovery scenarios.
Smart Images

Figure CN2023139994_05122024_PF_FP_ABST
Abstract
Description
A mMTC network slice mapping method and system based on group authentication Technical Field
[0001] The present invention relates to the field of wireless communication networks, and in particular to an mMTC network slice mapping method based on group authentication. Background Art
[0002] The rapid development of 5G technology is fueled by the increasingly widespread use of the Internet of Things (IoT). Massive Machine-Type Communications (mMTC) is closely related to IoT technology and has attracted considerable attention from researchers as one of the three key 5G application scenarios. To provide customized network services while controlling CapEx (Capital Expenditure) and OpEx (Operating Expenditure), operators are considering using network slicing to partition the physical network into multiple logical virtual networks to carry mMTC services. The basic performance indicators for mMTC services, as defined by the IMT-2020 (5G) Promotion Group, include a connection density of 106 devices / km², a device battery life of 15 years, and an end-to-end latency of 3-10ms. Therefore, the authentication and access of large-scale IoT devices to the network must be a key consideration in the corresponding mMTC network slice mapping mechanism.
[0003] In the LTE system, the EPS-AKA mechanism is used for access authentication and key negotiation of various terminals. In the 5G system, although the authentication mechanisms for MTC (multi-task computing) devices and HTC (high-throughput computing) devices have not yet been further differentiated, it is a consensus that solutions based on group authentication can effectively improve the access authentication efficiency of MTC devices (Internet of Things devices) and alleviate signaling congestion. The mainstream idea is to build multiple IoT devices under a unified home network into a managed group and select a trusted group leader for it. The mobile management entity (MME) verifies the managed group by verifying the aggregate signature generated by the group leader on behalf of all group members. Therefore, the mMTC network slice mapping process that carries these devices should be different from other general slice mapping processes that only consider the allocation of heterogeneous network resources. In other words, this group authentication requirement has a profound impact on the construction and mapping process of the corresponding mMTC network slice.
[0004] To address the slice authentication and mapping issues in IoT services, existing technologies generally adopt two solutions: first, using generative adversarial networks to implement deep network slicing, and based on SDN (Software-defined Networking) technology and NFV (Network Function Virtualization) technology for network slice mapping and resource management, and using Markov decision simulation for context-based authentication; second, establishing mMTC network slicing by simplifying the authentication process and simulating small data packet aggregation, and then building a physical hardware platform and experimentally verifying the performance of the proposed system in dynamically creating, adjusting, and deleting slices.
[0005] However, existing solutions tend to focus on network slicing frameworks or systems that include access authentication in order to improve overall communication performance. While these solutions consider some of the characteristics of mMTC network slicing, mMTC slicing itself serves only as a validation scheme for the secure slicing paradigm, rather than as a primary research topic. Furthermore, existing solutions overlook the design of mMTC slicing models that require group authentication, and thus the impact of group authentication mechanisms on the slice mapping process.
[0006] Summary of the Invention
[0007] The technical problem to be solved by the present invention is that the current mMTC network slice establishment and resource mapping solutions lack attention to group authentication requirements. An mMTC network slice mapping method and system based on group authentication are proposed to solve the above technical problems.
[0008] In order to solve the above technical problems, the present invention adopts the following technical solutions:
[0009] A method for mapping mMTC network slices based on group authentication is used to implement slice deployment with multiple groups of MTC devices having trusted access to a core network, comprising the following steps:
[0010] Step S1: Obtain a slice request S of an mMTC network slice and obtain the latency requirement of the slice request S;
[0011] Step S2: Electing a group leader for the MTC device;
[0012] Step S3: determining the service type of the mMTC network slice according to the latency requirement, and matching different service types with different slice processing paths;
[0013] Step S4, construct a dynamic slice request traffic model, input the slice request S of the mMTC network slice into the dynamic slice request traffic model, and perform node mapping and link mapping for each slice request S in turn according to the slice arrival order output by the dynamic slice request traffic model.
[0014] The existing technology mainly uses a general network slice resource deployment and slice mapping method for the three types of slice application scenarios: uRLLC, eMBB, and mMTC. That is, it adopts heuristic algorithms or machine learning methods, takes network settings as input, and takes the QoS (Quality of Service) requirements of different types of slices as the basis. The objective function is designed to optimize network resources and ultimately output a slice mapping deployment plan, while ignoring the specific scenarios of slice use and the corresponding slice mapping problems. This application is designed for the wide-connected characteristics of mMTC network slicing. It elects the group leader of the MTC device before slice mapping. Compared with the traditional general slice mapping method, it takes into account the group authentication requirements when large-scale IoT devices join the network.
[0015] The QoS requirements of slices can be summarized into the following three aspects: (1) Bandwidth requirements: Different types of network applications require different bandwidths. For example, streaming applications require high-bandwidth network support, while email requires lower bandwidth. Therefore, network service providers need to provide appropriate bandwidth resources based on the type of application and user needs. (2) Delay requirements: Some applications are very sensitive to delay, such as online games, cloud office applications, etc. Therefore, network service providers need to provide low-latency services, such as using shorter network paths, limiting network congestion, etc. (3) Reliability requirements: For some mobile applications, the network connection must remain stable and reliable, such as online payment and video conferencing. Therefore, network service providers need to provide highly stable network connections. Therefore, this application determines the service type of the mMTC network slice based on the delay requirements, and matches different service types with different slice processing paths, so that differentiated processing path planning can be performed for the delay requirements of the target slice, thereby effectively reducing the slice blocking rate and balancing the optical network bandwidth resources and edge node processing resource consumption, which has certain practical application reference value.
[0016] Moreover, the existing technologies mostly use static network traffic scenarios in slice resource deployment and slice mapping. This application constructs a dynamic slice request traffic model to simulate the traffic changes of real network slice requests, thereby improving the practicality of mMTC network slicing related resource deployment and mapping strategies, and has certain reliability and creativity.
[0017] Preferably, the method for obtaining the slice request S of the mMTC network slice in step S1 includes:
[0018] Constructing a network model for accessing multiple groups of MTC devices, the network model including a plurality of radio units and a central office, the radio units and the central office being connected via optical fiber links;
[0019] A group of MTC devices randomly access several radio units and initiate a slice request S;
[0020] The radio unit counts the radio resource blocks required by each cell and records the identity information of the connected MTC devices;
[0021] Based on the total number of radio resource blocks of the cells to which each slice request S belongs as its coverage, the slice requests S are sorted in descending order, and the sorted set is recorded as a slice iteration set S'.
[0022] Preferably, the central office includes several access central offices, several main central offices and a core central office, multiple radio units are connected to one access central office, multiple access central offices form an access ring, each access ring is connected to a main central office, multiple main central offices form a convergence ring, and the convergence ring is connected to the core central office.
[0023] Preferably, the method for performing group leader election of the MTC device in step S2 includes:
[0024] Determine whether the radio units randomly accessed by a group of MTC devices belong to the same main central office. If they belong to the same main central office, the main central office is elected as the group leader. If they belong to different main central offices, the comprehensive evaluation index Fn of each main central office is calculated, and the main central office with the largest comprehensive evaluation index Fn is elected as the group leader.
[0025] Preferably, the calculation method of the comprehensive evaluation index Fn is:
[0026] The comprehensive evaluation index Fn is the weighted sum of the remaining processing resources of the master central office node, the remaining bandwidth of the optical port of the master central office node, the average distance from the home radio unit set to the master central office node, and the number of home MTC device connections.
[0027] Preferably, the access central office and the main central office are both deployed with distributed units, the main central office is also deployed with a centralized unit, and the core central office is deployed with a mobile edge computing entity, then step S3 specifically includes:
[0028] Determining whether the value of the delay requirement exceeds a preset threshold; if the value of the delay requirement does not exceed the preset threshold, classifying the service type of the mMTC network slice as delay-sensitive; if the value of the delay requirement exceeds the preset threshold, classifying the service type of the mMTC network slice as delay-tolerant;
[0029] For latency-sensitive mMTC network slices, the distributed units of the mMTC network slice are processed in the access central office, and the centralized units of the mMTC network slice are processed in the master central office elected as the group leader;
[0030] For delay-tolerant mMTC network slices, both the distributed units and the centralized units of the mMTC network slice are processed in the master central office elected as the group leader.
[0031] Preferably, the input of the dynamic slice request traffic model is the slice request S in the slice iteration set S', wherein the duration of a single slice request S is simulated by a negative exponential distribution, and the interval time for the arrival of the next slice request S is simulated by a Poisson distribution, and the output of the dynamic slice request traffic model is a sequence of slice requests with different slice arrival orders.
[0032] Preferably, the method further includes the following steps before step S4:
[0033] Receiving aggregate signature information of a group of MTC devices, the group leader performs group authentication based on the aggregate signature information and distributes the key to each MTC device;
[0034] Determine the candidate paths for node mapping and link mapping for each slice request S, and sequentially search for nodes and network resources in the candidate paths that meet the slice service requirements;
[0035] Perform network resource allocation in nodes that meet the slice service requirements.
[0036] Preferably, the method for performing network resource allocation includes:
[0037] Check the available network resources of the corresponding node and the remaining bandwidth resources of the corresponding optical fiber link. If the corresponding node has available network resources and the corresponding optical fiber link has remaining bandwidth resources, the slice request S will allocate network resources within the slice service time and release the corresponding network resources after the slice service time ends. If the corresponding node does not have available network resources and the corresponding optical fiber link does not have remaining bandwidth resources, the slice request S will be blocked.
[0038] An mMTC network slice mapping system based on group authentication, comprising:
[0039] A slice acquisition unit, configured to acquire a slice request S for an mMTC network slice and acquire a latency requirement for the slice request S;
[0040] Group leader election unit, used to elect group leaders for MTC devices;
[0041] A slice processing unit, configured to determine the service type of the mMTC network slice according to the latency requirement, and match different service types with different slice processing paths;
[0042] A dynamic slice request traffic model for outputting the slice request S of the mMTC network slice as a sequence of slice requests with different slice arrival orders;
[0043] A mapping unit is used to perform node mapping and link mapping for each slice request S in turn according to the slice arrival order output by the dynamic slice request traffic model.
[0044] The beneficial technical effects of the present invention include: adopting a group authentication-based mMTC network slice mapping method and system, designing an mMTC network slice mapping method based on the wide connectivity characteristics of mMTC network slices, and performing group leader election for MTC devices before slice mapping. Compared with traditional general slice mapping methods, this method takes into account the group authentication requirements when large-scale IoT devices join the network;
[0045] By using a group leader election method based on the upper-layer ownership of the base station to which MTC devices access, mMTC network slicing can first consider the latency loss cost caused by the long transmission distance in the main central office node. When this cost is unavoidable, the processing node can be determined based on the comprehensive evaluation index Fn. This greatly frees up network resources, reduces the deployment pressure of slice requests S, and completes the network's maximum number of slices while meeting slice deployment requirements.
[0046] By incorporating the number of connected MTC devices into the calculation of the comprehensive evaluation index Fn, the system can not only adapt to the large-scale access of massive IoT devices, but also adaptively avoid selecting attacked nodes in network disaster recovery scenarios (i.e., when a node is attacked, resulting in insufficient bandwidth and computing resources). This means that access requests from a large number of MTC devices are not allocated to such nodes, thus alleviating pressure on the nodes.
[0047] The delay requirement is used to categorize the service types of mMTC network slices into delay-sensitive and delay-tolerant types. Different service types are matched to different slice processing paths. This allows for differentiated processing path planning based on the latency requirements of the target slices, effectively reducing the slice blocking rate and balancing the consumption of optical network bandwidth resources and edge node processing resources. This approach has certain practical application reference value.
[0048] By constructing a dynamic slice request traffic model, the arrival and end processes of the slice request S are made to present an irregular order, which is different from the static network traffic scenario in which the slice request S is first-come, first-served in the prior art. This enables the simulation of the traffic changes of real network slice requests, thereby improving the practicality of the mMTC network slicing-related resource deployment and mapping strategy proposed in this application, and having certain reliability and creativity.
[0049] Other features and advantages of the present invention will be disclosed in detail in the following specific embodiments and drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0050] The present invention will be further described below with reference to the accompanying drawings:
[0051] FIG1 is a flow chart of an mMTC network slice mapping method based on group authentication according to an embodiment of the present invention.
[0052] FIG2 is a flow chart of a method for obtaining a slice request S for an mMTC network slice according to an embodiment of the present invention.
[0053] FIG3 is a schematic diagram of the structure of a network model according to an embodiment of the present invention.
[0054] Figure 4 is a schematic diagram of the structure of an mMTC network slice mapping system based on group authentication according to an embodiment of the present invention.
[0055] Among them: 1. Radio unit, 2. Access ring, 3. Convergence ring, 4. Slice acquisition unit, 5. Group leader election unit, 6. Slice processing unit, 7. Dynamic slice request traffic model, 8. Mapping unit. DETAILED DESCRIPTION
[0056] The following is an explanation and description of the technical solutions of the embodiments of the present invention in conjunction with the drawings of the embodiments of the present invention. However, the following embodiments are only preferred embodiments of the present invention and are not exhaustive. Based on the embodiments in the implementation manner, other embodiments obtained by those skilled in the art without creative work are all within the scope of protection of the present invention.
[0057] In the following description, terms such as "inside", "outside", "up", "down", "left", "right", etc. that indicate directions or positional relationships are only used to facilitate the description of the embodiments and simplify the description, and do not indicate or imply that the device or element referred to must have a specific direction, be constructed and operate in a specific direction. Therefore, they should not be understood as limiting the present invention.
[0058] This application provides an mMTC network slice mapping method based on group authentication, which is used to implement slice deployment with multiple groups of MTC devices having trusted access to the core network. Please refer to Figure 1, which includes the following steps:
[0059] Step S1) obtains a slice request S of the mMTC network slice and obtains the latency requirement of the slice request S.
[0060] Furthermore, in this embodiment, the latency requirement of the slice request S is defined as the sum of the data propagation delay and exchange delay and the computational delay required to perform the corresponding baseband processing.
[0061] Step S2) Electing a group leader of the MTC devices.
[0062] Step S3) Determine the service type of the mMTC network slice based on the latency requirements, and match different service types with different slice processing paths.
[0063] Step S4) constructs a dynamic slice request traffic model, inputs the slice request S of the mMTC network slice into the dynamic slice request traffic model, and performs node mapping and link mapping for each slice request S in turn according to the slice arrival order output by the dynamic slice request traffic model.
[0064] The existing technology mainly uses a general network slice resource deployment and slice mapping method for the three types of slice application scenarios: uRLLC, eMBB, and mMTC. That is, it adopts heuristic algorithms or machine learning methods, takes network settings as input, and takes the QoS (Quality of Service) requirements of different types of slices as the basis. The objective function is designed to optimize network resources and ultimately output a slice mapping deployment plan, while ignoring the specific scenarios of slice use and the corresponding slice mapping problems. The embodiment of the present application is designed for the wide-connectivity characteristics of mMTC network slicing. It performs group leader election for MTC devices before slice mapping. Compared with the traditional general slice mapping method, it takes into account the group authentication requirements when large-scale IoT devices join the network.
[0065] The QoS requirements of slices can be summarized into the following three aspects: (1) Bandwidth requirements: Different types of network applications require different bandwidths. For example, streaming applications require high-bandwidth network support, while email requires lower bandwidth. Therefore, network service providers need to provide appropriate bandwidth resources based on the type of application and user needs. (2) Delay requirements: Some applications are very sensitive to delay, such as online games, cloud office applications, etc. Therefore, network service providers need to provide low-latency services, such as using shorter network paths, limiting network congestion, etc. (3) Reliability requirements: For some mobile applications, the network connection must remain stable and reliable, such as online payment and video conferencing. Therefore, network service providers need to provide highly stable network connections. Therefore, the embodiment of the present application determines the service type of the mMTC network slice based on the delay requirements, and matches different service types with different slice processing paths, so that differentiated processing path planning can be performed for the delay requirements of the target slice, thereby effectively reducing the slice blocking rate and balancing the optical network bandwidth resources and edge node processing resource consumption, which has certain practical application reference value.
[0066] Moreover, the existing technologies mostly adopt static network traffic scenarios in slice resource deployment and slice mapping. The embodiments of the present application construct a dynamic slice request traffic model to simulate the traffic changes of real network slice requests, thereby improving the practicality of mMTC network slice-related resource deployment and mapping strategies, and have certain reliability and creativity.
[0067] On the other hand, in this embodiment, referring to FIG. 2 , the method for obtaining a slice request S for an mMTC network slice in step S1 includes:
[0068] Step S101) A network model for accessing multiple groups of MTC devices is constructed, the network model including several radio units 1 and a central office, the radio units 1 being connected to the central office via an optical fiber link.
[0069] This embodiment constructs a metropolitan optical network model based on dense wavelength division multiplexing, wherein several radio units 1 responsible for collecting mMTC network slice service traffic are distributed in a certain physical area and interconnected with the central office via optical fiber links to achieve data transmission.
[0070] Step S102) A group of MTC devices randomly access several radio units 1 and initiate a slice request S.
[0071] Among them, the MTC devices carried on a network slice request S are randomly collected in a certain physical area. At this time, the base stations accessed by the MTC devices may be in different cells. Therefore, the slice request S in this embodiment can process the access of MTC devices across cells.
[0072] Step S103) The radio unit 1 counts the radio resource blocks required by each cell and records the identity information of the connected MTC devices.
[0073] For example, the radio unit 1 may implement the method of counting radio resource blocks required by each cell as follows:
[0074] (1) Measuring signal strength: The radio unit 1 measures the signal quality and strength of each cell to determine the cell that the MTC device accesses. This can be achieved by measuring the received signal strength indicator (RSSI). Generally speaking, the MTC device connects to the cell with the strongest signal.
[0075] (2) Requesting the device's Quality of Service (QoS) requirements. After the MTC device connects to the cell, the radio unit 1 sends a specific control signal to the MTC device to request the MTC device to send its QoS requirements. This can be achieved by sending a request to the MTC device, in which the MTC device includes its required bandwidth, latency, and reliability indicators.
[0076] (3) Resource Block Allocation Algorithm: Based on the device's quality of service requirements, the radio unit 1 can calculate the number of radio resource blocks required for each cell. This can be achieved by utilizing a resource block allocation algorithm, which can consider dynamically allocating resource blocks to meet the different quality of service requirements of different cells.
[0077] (4) Establishing a resource block allocation table, the radio unit 1 records the number of resource blocks required for each cell and the identity information of each MTC device. This can be achieved by establishing a resource block allocation table that records the resource block requirements of each cell and the number of resource blocks allocated to each MTC device, as well as the identity information of each MTC device.
[0078] Step S104) The slice requests S are sorted in descending order based on the total number of radio resource blocks of the cells to which each slice request S belongs, and the sorted set is recorded as a slice iteration set S'.
[0079] It is generally believed that the revenue of IoT slices has a certain positive correlation with the IoT devices they carry. Therefore, this embodiment arranges the slice requests S in descending order based on the total number of radio resource blocks of the cells to which each slice request S covers, which helps to first meet the relatively high-priority slice service needs with higher economic benefits.
[0080] On the other hand, in this embodiment, the central office includes several access central offices, several main central offices and a core central office, multiple radio units 1 are connected to one access central office, multiple access central offices constitute an access ring 2, each access ring 2 is connected to a main central office, multiple main central offices constitute a convergence ring 3, and the convergence ring 3 is connected to the core central office.
[0081] Referring to FIG. 3 , in this embodiment, the central offices can be divided into multiple stages based on their position in the aggregation hierarchy. Specifically, at the lowest network stage (e.g., stage 0), radio units 1 (RU) exist, while stages 1 and 2 are composed of access central offices (Access COs) and main central offices (Main COs), respectively. The core central office (Core CO) serves as an Internet access point and represents the interface to the 5G core network segment. Radio units 1 are evenly distributed across the access central offices. An access central office may be connected to multiple radio units 1. Multiple access central offices form an access ring 2. Each access ring 2 has a main central office. Multiple main central offices form a convergence ring 3 and are connected to the core central office. The central offices in the network model of this embodiment are organized in a ring topology and are equipped with optical and IP layer switching capabilities to support the conversion of optical and electrical signals, enabling flexible forwarding and service diversion functions.
[0082] Specifically, this embodiment models the network as G(V m , E n ), used to represent the ring topology of DWDM transmission in 5G RAN, where V m Refers to the set of nodes in the network at various levels, such as radio unit 1, access central office, main central office and core central office, E n is the collection of all fiber links in the network, e i,j ∈E n Used to represent the optical fiber link from node i to node j, the link length is d i,j , the number of wavelengths that can be accommodated by the optical fiber link is w, and the maximum carrying bandwidth of each wavelength is B (bps). The symbols and symbol definitions of the network model are shown in Table 1.
[0083] Table 1 Symbols and symbol definitions of network models
[0084] On the other hand, in this embodiment, the method for performing group leader election of MTC devices in step S2 includes:
[0085] Determine whether the radio units 1 randomly accessed by a group of MTC devices belong to the same main central office. If they do, the main central office is elected as the group leader. If they belong to different main central offices, calculate the comprehensive evaluation index Fn of each main central office, and elect the main central office with the largest comprehensive evaluation index Fn as the group leader.
[0086] The group leader election method proposed in this embodiment is divided according to the upper-layer affiliation of the base station to which the MTC device accesses. Therefore, the mMTC network slice can first consider the delay loss cost caused by the long-distance transmission distance in the main central office node. When this cost cannot be avoided, the processing node judgment can be made based on the comprehensive evaluation index Fn, which greatly releases network resources, reduces the deployment pressure of the slice request S, and completes the network's maximum number of slice carrying while meeting the slice deployment requirements.
[0087] On the other hand, in this embodiment, the calculation method of the comprehensive evaluation index Fn is:
[0088] The comprehensive evaluation index Fn is the weighted sum of the remaining processing resources of the master central office node, the remaining bandwidth of the optical port of the master central office node, the average distance from the home radio unit set 1 to the master central office node, and the number of home MTC device connections.
[0089] Compared with the existing technology, this embodiment introduces the influencing factor of the number of connected MTC devices into the calculation of the comprehensive evaluation index Fn. This not only adapts to the application scenario of large-scale access of massive IoT devices, but also can adaptively avoid selecting attacked nodes in network disaster recovery scenarios (i.e., nodes are attacked, resulting in insufficient corresponding bandwidth and computing resources). In other words, it avoids allocating access requests from a large number of MTC devices to such nodes, thereby alleviating the pressure on the nodes. In addition, this technical solution can also balance the load distribution of mMTC network nodes, and has a certain degree of robustness and potential benefits for scenarios where the mMTC network carries other types of slices or service applications.
[0090] For example, the comprehensive evaluation index Fn can be expressed by the following formula: n =αU n +βB n +γH n +δQ n
[0091] α+β+γ+δ=1
[0092] Among them, Fn is the comprehensive evaluation index of the main central office node n, N is the total number of main central office nodes, Un is defined as the remaining processing resources of n∈N, and Bn is defined as the remaining bandwidth resources of all optical ports of n∈N. n =∑ p∈P(n)Bw(p) is calculated from Bn, where p is the optical port of the master central office node and Bw(p) is the remaining bandwidth of each optical port of the master central office node n∈N. In addition, Un, Bn and Bw(p) are all normalized. At the same time, considering the deployment cost of the optical fiber link and the delay caused by the transmission distance, Hn is defined as the average physical distance between the target node in the mMTC slice request and all connected radio units 1 of the slice request. Using the formula H n =∑ r∈R Hn is calculated as dis(r) / |R|, where dis(r) is the shortest transmission distance between the master central office node n and each cell, obtained using the shortest path search algorithm, and R represents all cellular nodes in the mMTC network slice request S. Qn is the number of homed MTC device connections for n∈N. α, β, γ, and δ are preset coefficients of the relevant factors, with α+β+γ+δ=1, which is used to balance the relative influence of the four factors.
[0093] The adjustments to the four preset coefficients, α, β, γ, and δ, are determined by the different slice QoS requirements and optimization goals. For example, for a computationally intensive slice with weak bandwidth requirements, a larger α value results in nodes with more computational resources being more likely to be selected as mapping targets, while a larger β value results in nodes with abundant bandwidth resources being more considered when making node ranking decisions.
[0094] On the other hand, in this embodiment, the access central office and the main central office are both deployed with distributed units, the main central office is also deployed with a centralized unit, and the core central office is deployed with a mobile edge computing entity. Step S3 specifically includes:
[0095] Determine whether the value of the delay requirement exceeds a preset threshold. If the value of the delay requirement does not exceed the preset threshold, classify the service type of the mMTC network slice as delay-sensitive. If the value of the delay requirement exceeds the preset threshold, classify the service type of the mMTC network slice as delay-tolerant.
[0096] For latency-sensitive mMTC network slices, the distributed units of the mMTC network slice are processed in the access central office, and the centralized units of the mMTC network slice are processed in the master central office elected as the group leader;
[0097] For delay-tolerant mMTC network slices, both the distributed units and the centralized units of the mMTC network slice are processed in the master central office elected as the group leader.
[0098] Please refer to Figure 3. In this embodiment, the central office has the corresponding baseband processing capabilities for hosting RAN functions. In order to place the radio functions, the baseband unit protocol stack is functionally divided according to the 3GPP three-layer RAN architecture. The distributed unit (DU) function is deployed on the access central office and the main central office node, the centralized unit (CU) function is deployed on the main central office node, and the mobile edge computing (MEC) function is deployed on the core central office node. The interface between the radio unit 1 and the distributed unit is defined as eCPRI, and the link connecting the radio unit 1 and the distributed unit is called the fronthaul path. The interface between the distributed unit and the centralized unit is called F1. The transmission capacity requirement of F1 is similar to that of the conventional backhaul interface capacity. The link connecting the centralized unit and the distributed unit is called the midhaul path. The interface between the centralized unit and the mobile edge computing is called S1, and the link connecting the centralized unit and the mobile edge computing entity is called the backhaul path.
[0099] Furthermore, based on the Network Function Virtualization (NFV) technology, both the centralized unit and the distributed unit can be used as virtual containers vDU and virtual containers vCU to perform virtualized resource deployment on commercial servers. The server of each central office node can accommodate multiple virtual containers vCU or virtual containers vDU in varying quantities according to different computing capabilities. Therefore, through such logical isolation, the mapping process of each mMTC slice needs to include a set of heterogeneous resources. The implementation steps of this method include: first, allocating radio unit 1 to perform signal acquisition for the slice request S; second, allocating bandwidth resources for eCPRI, F1, and S1 interface communications; and finally, allocating computing resources for the slice execution, that is, allocating the computing complexity required to complete the vDU and vCU functions in turn.
[0100] mMTC network slicing services often involve a large number of devices performing uplink transmission at low user data rates, but they also face some delay-sensitive service requirements. This embodiment divides the service types of mMTC network slices into delay-sensitive and delay-tolerant types based on the numerical value of the delay requirement, and matches different service types with different slice processing paths, thereby enabling differentiated processing path planning for the delay requirements of the target slice, thereby effectively reducing the slice blocking rate, balancing the consumption of optical network bandwidth resources and edge node processing resources, and providing a basis for the subsequent corresponding wavelength allocation and routing forwarding of mMTC network slices based on the shortest path selection principle. It has certain practical application reference value.
[0101] On the other hand, in this embodiment, the input of the dynamic slice request traffic model is the slice request S in the slice iteration set S', where the duration of a single slice request S is simulated by a negative exponential distribution, and the interval time for the arrival of the next slice request S is simulated by a Poisson distribution. The output of the dynamic slice request traffic model is a sequence of slice requests with different slice arrival orders.
[0102] Specifically, this embodiment models the dynamic slice request traffic model as (C S , R S , L S , B S , G S ). The symbol description and symbols of the dynamic slice request traffic model are shown in Table 2.
[0103] Table 2 Symbol description and symbol table of dynamic slice request traffic model
[0104] This embodiment constructs a dynamic slice request traffic model so that the arrival and end processes of the slice request S are in an irregular order, which is different from the static network traffic scenario in the prior art where the slice request S is first-come-first-out. It simulates the traffic changes of real network slice requests, thereby improving the practicality of the mMTC network slicing-related resource deployment and mapping strategy proposed in this embodiment, and has certain reliability and creativity.
[0105] On the other hand, in this embodiment, the following steps are further included before step S4:
[0106] Receive the aggregate signature information of a group of MTC devices, the group leader performs group authentication based on the aggregate signature information and distributes the key to each MTC device;
[0107] Determine the candidate paths for node mapping and link mapping for each slice request S, and search the candidate paths for nodes and network resources that meet the slice service requirements.
[0108] Perform network resource allocation in nodes that meet the slice service requirements.
[0109] The identity information of the MTC device, the identity information of the radio unit 1 randomly accessed by the MTC device, and the identity information of the access central office itself are combined to form the aggregate signature information.
[0110] Among them, the network resources required for the slice service of each mMTC network include the range of radio unit 1 connected by the slice coverage, the wireless side traffic load of radio unit 1, the latency requirements and bandwidth requirements of the slice in the fronthaul, midhaul and backhaul links, and the computational complexity required to complete the corresponding virtual function centralized unit, distributed unit and mobile edge computing.
[0111] For an MTC device, the key step in its network access process is identity authentication. Specifically, the access authentication process of the MTC device needs to follow the current standardized methods, such as the Evolved Packet System Authentication and Key Agreement (EPS-AKA). When multiple MTC devices request to access the network at the same time, each MTC device needs to independently perform a complete access authentication process with the network to ensure MTC security. This single authentication method may cause signaling overload on the relevant 5G transmission network. In severe cases, the network may choose to refuse to provide services. In this context, in order to avoid congestion of massive IoT device connections in the mobile communication network, the group leader in the network model proposed in this embodiment is responsible for receiving and authenticating the aggregate signature information.
[0112] On the other hand, in this embodiment, the method for performing network resource allocation includes:
[0113] Check the available network resources of the corresponding node and the remaining bandwidth resources of the corresponding optical fiber link. If the corresponding node has available network resources and the corresponding optical fiber link has remaining bandwidth resources, the slice request S will allocate network resources within the slice service time and release the corresponding network resources after the slice service time ends. If the corresponding node does not have available network resources and the corresponding optical fiber link does not have remaining bandwidth resources, the slice request S will be blocked.
[0114] It should be noted that, in this embodiment, the values of the available network resources of the corresponding node and the remaining bandwidth resources of the corresponding optical fiber link are zero or less than the required resources, which belongs to the latter situation where there are no available network resources for the corresponding node and no remaining bandwidth resources for the corresponding optical fiber link. In this case, the slicing request S will be blocked.
[0115] In this embodiment, multiple master central office nodes or access central offices can be used to provide the network resources required for various slice services, and the selection of processing nodes is determined by comprehensively considering the network resource status of the corresponding nodes and the deployment requirements of the slice services themselves. This is different from the existing technology that always selects the master central office node or access central office node with the closest optical fiber transmission distance for a certain independent optimization indicator (such as latency constraint). In this way, when the available network resources of the target node are insufficient or the corresponding optical interface bandwidth resources are scarce, the existing technology adopts a single optimization target strategy that is more likely to block the slice request. Therefore, this embodiment can effectively reduce the slice blocking rate. In addition, this embodiment makes full use of the network resources of the master central office node in the convergence ring 3 through group leader election, thereby realizing the reasonable planning of network resources on the basis of meeting the group authentication requirements of the mMTC network slice mapping.
[0116] On the other hand, the present application also provides an mMTC network slice mapping system based on group authentication, as shown in FIG4 , including:
[0117] The slice acquisition unit 4 is used to obtain a slice request S of the mMTC network slice and obtain the latency requirement of the slice request S;
[0118] A group leader election unit 5 is used to elect a group leader for MTC devices;
[0119] Slice processing unit 6, used to determine the service type of the mMTC network slice according to the latency requirement and match different service types with different slice processing paths;
[0120] a dynamic slice request traffic model 7 for outputting a slice request S of an mMTC network slice as a sequence of slice requests with different slice arrival orders;
[0121] The mapping unit 8 is used to perform node mapping and link mapping for each slice request S in turn according to the slice arrival order output by the dynamic slice request traffic model.
[0122] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Those skilled in the art will understand that the present invention includes, but is not limited to, the contents described in the drawings and the above specific embodiments. Any modifications that do not deviate from the functional and structural principles of the present invention are intended to be included within the scope of the claims.
Claims
1. A mMTC network slice mapping method based on group authentication, used to implement slice deployment with multiple groups of MTC devices with trusted access to the core network, It is characterized in that The following steps are involved: Step S1, obtaining a slice request S of an mMTC network slice, and obtaining a latency requirement of the slice request S; Step S2, electing a group leader of the MTC device; Step S3, determining the service type of the mMTC network slice according to the latency requirement, and matching different service types with different slice processing paths; Step S4, construct a dynamic slice request traffic model, input the slice request S of the mMTC network slice into the dynamic slice request traffic model, and perform node mapping and link mapping for each slice request S in turn according to the slice arrival order output by the dynamic slice request traffic model.
2. The mMTC network slice mapping method based on group authentication as claimed in claim 1, It is characterized in that The method for obtaining the slice request S of the mMTC network slice in step S1 includes: Constructing a network model for accessing multiple groups of MTC devices, the network model comprising a plurality of radio units and a central office, the radio units and the central office being connected via an optical fiber link; A group of MTC devices randomly access several radio units and initiate a slice request S; The radio unit counts the radio resource blocks required for each cell and records the identity information of the connected MTC devices; Based on the total number of radio resource blocks of cells to which each slice request S belongs, the slice requests S are sorted in descending order, and the sorted set is recorded as a slice iteration set S'.
3. The mMTC network slice mapping method based on group authentication as claimed in claim 2, It is characterized in that The central office includes several access central offices, several main central offices and a core central office. Multiple radio units are connected to an access central office. Multiple access central offices form an access ring. Each access ring is connected to a main central office. Multiple main central offices form a convergence ring. The convergence ring is connected to the core central office.
4. The mMTC network slice mapping method based on group authentication as claimed in claim 3, It is characterized in that The method for electing a group leader of the MTC device in step S2 includes: Determine whether a group of radio units randomly accessed by MTC devices belong to the same main central office. If they belong to the same main central office, the main central office is elected as the group leader. If they belong to different main central offices, the comprehensive evaluation index Fn of each main central office is calculated, and the main central office with the largest comprehensive evaluation index Fn is elected as the group leader.
5. The mMTC network slice mapping method based on group authentication as claimed in claim 4, It is characterized in that The calculation method of the comprehensive evaluation index Fn is: The comprehensive evaluation index Fn is the weighted sum of the remaining processing resources of the master central office node, the remaining bandwidth of the optical port of the master central office node, the average distance from the belonging radio unit set to the master central office node, and the number of belonging MTC device connections.
6. The mMTC network slice mapping method based on group authentication as claimed in claim 4, It is characterized in that The access central office and the main central office are both deployed with distributed units, the main central office is also deployed with a centralized unit, and the core central office is deployed with a mobile edge computing entity, then step S3 specifically includes: Determine whether the value of the delay requirement exceeds a preset threshold; if the value of the delay requirement does not exceed the preset threshold, classify the service type of the mMTC network slice as delay-sensitive; if the value of the delay requirement exceeds the preset threshold, classify the service type of the mMTC network slice as delay-tolerant; For latency-sensitive mMTC network slices, the distributed units of the mMTC network slice are processed in the access central office, and the centralized units of the mMTC network slice are processed in the master central office elected as the group leader; For the delay-tolerant mMTC network slice, both the distributed units and the centralized units of the mMTC network slice are processed in the master central office elected as the group leader.
7. The mMTC network slice mapping method based on group authentication as claimed in claim 2, It is characterized in that The input of the dynamic slice request traffic model is the slice request S in the slice iteration set S', wherein the duration of a single slice request S is simulated by a negative exponential distribution, and the interval time for the arrival of the next slice request S is simulated by a Poisson distribution, and the output of the dynamic slice request traffic model is a sequence of slice requests with different slice arrival orders.
8. The mMTC network slice mapping method based on group authentication according to any one of claims 1 to 7, It is characterized in that Before step S4, the method further includes the following steps: Receiving aggregate signature information of a group of MTC devices, the group leader performs group authentication according to the aggregate signature information and distributes the key to each MTC device; Determine a candidate path for node mapping and link mapping for each slice request S, and search the candidate paths for nodes and network resources that meet the slice service requirements in turn; Perform network resource allocation in nodes that meet the slice service requirements.
9. The mMTC network slice mapping method based on group authentication as claimed in claim 8, It is characterized in that The method of performing network resource allocation includes: Check the available network resources of the corresponding node and the remaining bandwidth resources of the corresponding optical fiber link. If the corresponding node has available network resources and the corresponding optical fiber link has remaining bandwidth resources, the slice request S allocates network resources within the slice service time and releases the corresponding network resources after the slice service time ends; if the corresponding node does not have available network resources and the corresponding optical fiber link does not have remaining bandwidth resources, the slice request S is blocked.
10. An mMTC network slice mapping system based on group authentication, It is characterized in that include: A slice acquisition unit, used to obtain a slice request S of an mMTC network slice and obtain a latency requirement of the slice request S; A group leader election unit is used to elect a group leader for MTC devices; The slice processing unit is used to determine the service type of the mMTC network slice according to the delay requirement and to Type matches different slice processing paths; A dynamic slice request traffic model for outputting a slice request S of an mMTC network slice as a sequence of slice requests with different slice arrival orders; A mapping unit is used to perform node mapping and link mapping for each slice request S in turn according to the slice arrival order output by the dynamic slice request traffic model.
Citation Information
Patent Citations
Reliability based 5G network slice online mapping method
CN108566659A
Network slice management method, device and equipment
CN110391920A
Network slice mapping method and device, server and storage medium
CN110958133A
5G network slice resource allocation method and system
CN113784395A
Virtual power plant aggregation regulation and control communication network flow balancing method and device
CN114785692A
Cited By
Network slice access control method based on connection density adaptive evaluation
CN120676407A
