Method and device for allocating and scheduling slice resources in fixed-mobile-satellite convergence network

Abstract

The invention discloses a slice resource allocation and scheduling method and device in a fixed-mobile-satellite convergence network, and relates to the technical field of B5G / 6G communication, and the method comprises the steps: obtaining an end-to-end service bearing demand through a convergence network controller, generating a service identifier and a service parameter, and transmitting the service identifier and the service parameter to network controllers of a fixed network, a mobile network and a satellite network; each network controller allocates and schedules network slice resources in the next scheduling period according to the current slice service condition; the edge network node allocates access slice resources according to the priority sequence of the service data packets; the network nodes map service parameters carried by the service data packets to corresponding slices for transmission; and the convergence network controller adjusts service parameters in the data packet according to the configuration and operation result of the slice bearer. According to the invention, efficient slice utilization is realized, and the problem of low utilization rate of service-based slice allocation is avoided.

Description

Technical Field

[0001] This application relates to the technical field of B5G / 6G communication, and particularly to a method and device for slice resource allocation and scheduling in a fixed-mobile-satellite integrated network. Background Art

[0002] In a fixed-mobile-satellite integrated network, the fixed network, mobile network, and satellite network are interconnected, and services are transmitted through the three networks or any two of them. Therefore, the fixed-mobile-satellite integrated network is a complex network system composed of multiple heterogeneous subnets, and there are differences in protocols and performance between different subnets, which increases the complexity of network deep integration. For example, different subnets may adopt different protocols and technologies, which requires overcoming problems such as protocol conversion and compatibility during network integration. In addition, different types of service applications also need to meet different service quality level requirements, such as real-time performance, reliability, and security. For example, applications such as high-definition video, remote medical treatment, and real-time monitoring have different requirements for the network and need to be fully considered during network design and optimization. Therefore, when designing a fixed-mobile-satellite integrated network, it is necessary to consider how to meet the diverse and differentiated needs of different types of applications while taking into account the performance of the entire network.

[0003] To overcome these challenges, it is crucial to introduce network slicing technology in the fixed-mobile-satellite integrated network.

[0004] In a fixed-mobile-satellite integrated network, the mobile network can directly access different nodes of the satellite network or fixed network through multiple base stations or mobile phones. Multiple nodes in the satellite network are connected to base stations in the terrestrial network through feeder links. During service transmission, user services access the satellite network through the mobile network and are relayed through the satellite network to access the terrestrial network as an important supplement to network communication. When the existing three networks achieve deterministic service transmission, slice transmission is the most effective way. Network slicing technology divides a physical network into multiple slice virtual networks (referred to as slices), and each slice can be customized according to the needs of different applications, thus realizing the diversification, customization, and elasticity of the network.

[0005] The slice transmission mechanisms of the fixed, mobile, and satellite networks are different. The fixed network performs slice transmission through time-division multiplexing; the mobile network performs slice transmission through frequency-division + time-division of channel resources; in the satellite network, the uplink and downlink between the satellite and the ground, as well as between the medium and high orbits, are microwave links. The slice mechanism is similar to that of the mobile network, and slices are made through frequency-division resources. The inter-satellite link is similar to the fixed network, and the laser link is sliced based on the time-division method. In the fixed-mobile-satellite integrated network, for deterministic slice transmission services, if all networks implement static slice transmission mechanisms, it will not only cause waste of resources but also cannot meet the dynamic changes of the network, such as network load changes and the high-speed movement of satellites. Therefore, it is necessary to implement dynamic triggering of slice resource allocation and scheduling algorithm configuration when deterministic services pass through different networks.

[0006] Currently, in the 5G network, due to the insufficient accuracy of evaluating user application requirements in the slice technology, the competition among multiple users within the same type of slice makes the network service quality guarantee ability not ideal. There is a lack of cross-network resource deployment for satellite nodes in the implementation of slice resource allocation and scheduling in the fixed-mobile-satellite integrated network. Specifically, the slice deployment in the fixed-mobile-satellite integrated network needs to be deployed across different networks, and the current research mainly focuses on slice deployment for a single network or a single domain. Most of the current research on mobile networks only considers user-level access, that is, wireless resources are allocated to users; the fixed network considers the small-grained orchestration and scheduling of services, lacking the joint optimization of fixed-mobile-satellite at the slice level. In addition, adopting end-to-end slice resource reservation based on services results in low utilization of slice resources in the entire network and difficult actual deployment. Summary of the Invention

[0007] This application provides a method and device for slice resource allocation and scheduling in a fixed-mobile-satellite integrated network, which improves the utilization rate of slices allocated to services and enhances the joint optimization of fixed-mobile-satellite.

[0008] In a first aspect, an embodiment of this application provides a method for slice resource allocation and scheduling in a fixed-mobile-satellite integrated network. The method includes:

[0009] Obtain the end-to-end service bearer requirements through the integrated network controller, generate service identifiers and service parameters, and send them to the network controllers of the fixed network, mobile network, and satellite network;

[0010] Each network controller allocates the allocation and scheduling of network slice resources for the next scheduling period according to the current slice service status; the edge network nodes perform access slice resource allocation according to the priority order of service data packets;

[0011] The network nodes map the service parameters carried in the service data packets to the corresponding slices for transmission;

[0012] The integrated network controller adjusts the service parameters in the data packets according to the configuration and operation results of the slice bearer.

[0013] In combination with the first aspect, in one embodiment, obtaining the end-to-end service bearer requirement through the converged network controller, generating service identifiers and service parameters, and distributing them to the network controllers of the fixed network, mobile network, and satellite network includes:

[0014] The converged network controller obtains the service bearer requirement through the management and control interface;

[0015] Generate the service identifiers of the fixed network, mobile network, and satellite network respectively;

[0016] According to the service bearer requirement, generate the service parameters of the slice through the service type field of the data packet, and distribute them to each network node through the network controllers of the fixed network, mobile network, and satellite network.

[0017] In combination with the first aspect, in one embodiment, the allocation and scheduling of network slice resources are performed by the network controller, including allocating the slice resources of the internal interconnection links corresponding to the network and allocating the uplink slice resources to the edge nodes;

[0018] The access slice resources are the link slice resources accessed from other networks, users, or service terminals, and are allocated by each network edge node.

[0019] In combination with the first aspect, in one embodiment, each network controller allocates and schedules the network slice resources for the next scheduling period according to the current slice service status, including:

[0020] Collect the slice transmission service data packet information of the current scheduling period through each node in the network and send it to the corresponding network controller;

[0021] Each network controller calculates the result of maximizing the network slice value according to the service data packet information collected in its own network, generates the configuration of the network slice service for the next scheduling period based on the result, and distributes it, and allocates slice resources for the links between each node in the network.

[0022] In combination with the first aspect, in one embodiment, different types of slices in the network are set with different values, and the slice values are adjusted according to the number of slices;

[0023] The sum of the values of various slices of the network node is the node slice value, and the sum of all node slice values is the network slice value.

[0024] In combination with the first aspect, in one embodiment, the edge network node allocates slice resources according to the priority order of service data packets, including:

[0025] Each network edge node obtains the service parameters of the service data packet, calculates the priority of the data packet according to a preset weight adjustment factor, and allocates the data packet to the corresponding slice resource and schedules the transmission according to the order of the priorities. The service parameters include bandwidth, delay, and jitter information.

[0026] Combined with the first aspect, in an implementation, the network node maps according to the service bearer parameters carried in the service data packet and transmits in the corresponding slice, including:

[0027] The network node analyzes the service parameters carried in the service data packet, maps the service data packet to a matching slice type through a time slot scheduling mechanism that combines wireless links and fixed links, and forwards it through the network node. The service parameters include bandwidth, delay, and jitter information.

[0028] Combined with the first aspect, in an implementation, the time slot scheduling mechanism includes:

[0029] Linearly schedule the two-dimensional slice resources of the wireless link to be consistent with the linear slice resource scheduling of the fixed link; through time slot scheduling, periodically scan various types of slices allocated in different time slots.

[0030] Combined with the first aspect, in an implementation, the converged network controller adjusts the service parameters in the data packet according to the configuration and operation results of the slice bearer, including:

[0031] The converged network controller obtains the slice service statistical information fed back by each network node, analyzes the operation results through artificial intelligence technology and optimizes the service bearer characteristics, sends the adjusted service parameters to the terminal, and updates the data packet.

[0032] In a second aspect, an embodiment of the present application provides a device based on the method for slice resource allocation and scheduling in the fixed-mobile-satellite converged network described in any one of the above, and the device includes:

[0033] A converged network control module, which is used to obtain the end-to-end service bearer requirements through the converged network controller, generate service identifiers and service parameters, and send them to the network controllers of the fixed network, mobile network, and satellite network;

[0034] Three network control modules, which are used for each network controller to allocate and schedule the network slice resources in the next scheduling period according to the current slice service status;

[0035] A resource allocation module, which is used for the edge network node to allocate access slice resources according to the priority order of the service data packet;

[0036] A mapping module, which is used for the network node to map according to the service bearer requirements carried in the service data packet and transmit in the corresponding slice;

[0037] An adjustment module, which is used to fuse the network controller to adjust the service bearer characteristics in the data packet according to the configuration and operation results of the slice bearer.

[0038] The beneficial effects brought by the technical solution provided by the embodiments of the present application include:

[0039] Different from the static allocation of slice resources based on services, the fusion network controller of the present application obtains the end-to-end service bearer requirements, generates service identifiers and service parameters, and distributes them to the network controllers of the fixed network, mobile network, and satellite network. The service bearer requirements of the resources are carried in the data packet, and end-to-end slice scheduling based on data packets is realized.

[0040] In the present application, the satellite node realizes cross-network slice deployment. When allocating slice resources, each network controller allocates and schedules the network slice resources for the next scheduling period according to the current slice service status, realizes efficient slice utilization, avoids the problem of low utilization rate of slices allocated based on services, and improves the joint optimization of fixed, mobile, and satellite.

[0041] Implement a unified scheduling strategy for wireless link and fixed link slice resources, avoid different network slice resource sizes and scheduling mechanisms, and realize end-to-end efficient slice transmission.

[0042] The service parameters include bandwidth, delay, and jitter information. According to the characteristics of the service, the appropriate slice type is allocated to meet different combinations of bandwidth, delay, and jitter requirements; by designing the slice type and scheduling method, services with different QoS requirements can realize on-demand end-to-end slice scheduling. Brief Description of the Drawings

[0043] Figure 1 It is a schematic diagram of the allocation and scheduling of fixed, mobile, and satellite integrated network slices in the embodiments of the present application;

[0044] Figure 2 It is a flowchart of the slice resource allocation and scheduling method in the fixed, mobile, and satellite integrated network in the embodiments of the present application;

[0045] Figure 3 It is a schematic diagram of the slice service identifier in the fixed, mobile, and satellite integrated network in the embodiments of the present application;

[0046] Figure 4 It is a schematic diagram of the service bearer configuration and optimization of the fusion network controller in the embodiments of the present application;

[0047] Figure 5 It is a flowchart of the network slice resource allocation method in the embodiments of the present application;

[0048] Figure 6 It is a flowchart of the access slice resource allocation method in the embodiments of the present application;

[0049] Figure 7 This is the flowchart of network node slice scheduling and implementation in the embodiments of the present application;

[0050] Figure 8 This is the schematic diagram of radio slice resources in the embodiments of the present application;

[0051] Figure 9 This is the schematic diagram of radio resource service bearer of data packets in the embodiments of the present application;

[0052] Figure 10 This is the schematic diagram of service bearer data packets carried by bearer link slices in the embodiments of the present application;

[0053] Figure 11 This is the schematic diagram of bearer link slice and sub - time slot scheduling in the embodiments of the present application. Detailed implementation manners

[0054] In order to enable those skilled in the art to better understand the solution of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present application.

[0055] As a part of high - quality deterministic transmission technology, network slicing technology mainly refers to slicing network resources to form logical sub - networks to provide virtual private network services for services, and solving the problem of how to provide and guarantee differentiated services for different - demand applications on the same physical network. Currently, its application is mainly in 5G networks, providing network slice services for three types of scenarios: enhanced mobile broadband (eMBB), ultra - high - reliability and low - latency communication (URLLC), and massive machine - type communication (mMTC). By introducing network slicing technology into the fixed - mobile - satellite integrated network, the following benefits can be brought:

[0056] Customized services: Network slicing technology can mask the differences in the underlying physical network, customize different services according to user needs on the general physical infrastructure, and provide differentiated service demand guarantees for different types of services. In the fixed - mobile - satellite integrated network, through network slicing technology, network resources can be allocated to different services according to different user needs, and different services can be provided according to different requirements.

[0057] Fine - grained resource allocation: Network slicing technology virtualizes network resources and aggregates them into a slice resource pool, and realizes more fine - grained resource allocation through a centralized controller based on SDN. In the fixed - mobile - satellite integrated network, through network slicing technology, heterogeneous physical network resources can be effectively integrated to provide efficient and fine - grained resource management.

[0058] Resource optimization: Network slicing technology can optimize network resources and improve resource utilization. In the fixed-mobile-satellite integrated network, the network resource utilization of different types of subnets is different. Through network slicing technology, resources can be allocated to different slices as needed, thus optimizing the utilization of network resources.

[0059] Flexibility and programmability: Network slicing technology can make the network more flexible and programmable, supporting the rapid deployment and adjustment of network functions. In the fixed-mobile-satellite integrated network, through network slicing technology, network resources can be dynamically allocated and adjusted according to the needs of different services to meet the service requirements.

[0060] Simplified management: Network slicing technology can separate and manage network resources, simplifying network management. In the fixed-mobile-satellite integrated network, through network slicing technology, the network resources of different services can be separated and managed, making network management more simple and efficient.

[0061] In summary, introducing network slicing technology in the fixed-mobile-satellite integrated network can optimize network resources, improve the customized service ability and flexibility of the network, simplify network management, provide guarantee for the differentiated service requirements of different types of services, thus achieving efficient operation and supporting the development of future networks. However, introducing network slicing technology into the network also brings a series of new challenges, including network resource scheduling and management, slice allocation, interoperability between slices, performance guarantee and quality assurance, as well as security and privacy protection, etc. And one of the key challenges is how to formulate effective slice resource allocation and scheduling.

[0062] First of all, network slicing technology virtualizes physical network resources into multiple slices. The service requirements and quality of service requirements of different slices may be different. Therefore, on-demand resource allocation and scheduling are required to meet the different service requirements of each network slice. At the same time, different slices will compete for the same resources, and an effective slice resource allocation mechanism is needed to balance resource utilization and quality of service. Compared with traditional terrestrial networks, the fixed-mobile-satellite integrated network is extremely complex due to involving multiple different networks, including different types of communication devices, transmission media, and access technologies, etc. How to formulate an effective slice resource allocation strategy in such a complex network environment and meet the needs of users and applications in different slices is a challenging problem.

[0063] Secondly, network slices need to be dynamically adjusted to meet different service transmission requirements. However, how to effectively formulate an adaptive adjustment strategy for network slices to avoid conflicts and errors; at the same time, improve the flexibility and scalability of the network is a challenge that needs to be solved. Due to the complexity and scale of the fixed-mobile-satellite integrated network, the adjustment of network slices has become more complex and difficult.

[0064] Finally, compared with traditional terrestrial networks with a fixed topological structure, due to the mobility of mobile networks and satellite networks, the network connections and topological structures of the fixed-mobile-satellite integrated network are dynamic, that is, they change over time, which makes the corresponding slice allocation strategy more complex.

[0065] Therefore, in order to achieve end-to-end network slice resource allocation and scheduling in the high-quality transmission of the fixed-mobile-satellite integrated network, it is necessary to make a breakthrough in technology, adapt to the characteristics of the fixed-mobile-satellite integrated network, and establish an efficient network slice allocation and scheduling mechanism, which is an urgent problem to be solved by those skilled in the art. Based on this, a method and device for slice resource allocation and scheduling in a fixed-mobile-satellite integrated network are proposed, focusing on realizing the slice resource allocation and scheduling of satellite network nodes, and providing a feasible solution for the high-quality transmission of the fixed-mobile-satellite integrated network.

[0066] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0067] In a first aspect, an embodiment of this application provides a method for slice resource allocation and scheduling in a fixed-mobile-satellite integrated network. As Figure 1 shown, for Figure 1 a schematic diagram of slice allocation and scheduling in a fixed-mobile-satellite integrated network, the method of this embodiment includes:

[0068] Obtain the end-to-end service bearing requirements through the integrated network controller, generate service identifiers and service parameters, and send them to the network controllers of the fixed network, mobile network, and satellite network.

[0069] Each network controller allocates the allocation and scheduling of network slice resources for the next scheduling period according to the current slice service status; the edge network nodes perform access slice resource allocation according to the priority order of service data packets.

[0070] The network nodes map the service parameters carried in the service data packets to the corresponding slices for transmission.

[0071] The integrated network controller adjusts the service parameters in the data packets according to the configuration and operation results of the slice bearers.

[0072] In this embodiment, obtaining the end-to-end service bearing requirements, generating service identifiers and service parameters, and sending them to the network controllers of the fixed network, mobile network, and satellite network, carrying the service bearing requirements of resources in the data packets, and realizing end-to-end slice scheduling based on data packets. When allocating slice resources, each network controller allocates the allocation and scheduling of network slice resources for the next scheduling period according to the current slice service status, realizes efficient slice utilization, avoids the problem of low utilization rate of slices allocated based on services, and improves the joint optimization of fixed-mobile-satellite.

[0073] Further, as Figure 2 shown, a more detailed embodiment of the method for slice resource allocation and scheduling in the fixed-mobile-satellite integrated network is provided. The method includes the following steps:

[0074] S1: The integrated network controller configures and optimizes slice services. For the service bearer in the fixed-mobile-satellite integrated network, the integrated network controller accepts the service bearer requirement configuration from the administrator through the management and control interface, generates the service parameters of the slice through the service type field of the data packet. The integrated network controller also generates the service identifiers of the fixed network, mobile network, and satellite network respectively, and sends the service identifier and service parameters to the network controllers of the fixed network, mobile network, and satellite network; so that when the slice service is transmitted in each network, the network nodes can identify the slice service.

[0075] Meanwhile, the integrated network controller adjusts the service parameters in the data packet according to the service bearer configuration and operation result of the slice. Specifically: The integrated network controller obtains the slice service statistical information fed back by each network node, analyzes the operation result through artificial intelligence technology and optimizes the service bearer requirement, sends the adjusted service parameters to the terminal, and updates the data packet to achieve high-quality transmission of the slice service.

[0076] S2: Each network controller configures slice resource allocation. Specifically, each network controller determines the method of slice allocation for the nodes and links in its own network according to the slice service sent by the integrated network controller. When the fixed-mobile-satellite integrated network bears end-to-end services, the terminal can access from any one of the fixed network, mobile network, and satellite network. In this embodiment, the slice of the end-to-end service can be divided into network slice resource allocation and scheduling, and access slice resource allocation and scheduling; network slice resource allocation and scheduling are adopted for the transmission path within the network, and access slice resource allocation and scheduling are adopted for the link accessing the network. Each network controller sends the service identifier of the slice service, the nodes and link slice methods on the service path to each node in its own network.

[0077] S3: Allocation and scheduling of network slice resources. The slice service transmission links in each network are calculated by their respective network controllers for the allocation of network slice resources in the next scheduling cycle according to the current slice service status, including allocating the slice resources of the internal interconnection links in the corresponding network, allocating the uplink slice resources to the edge nodes, and sending the calculation results to the network nodes for scheduling.

[0078] S4: Allocation and scheduling of access slice resources. For the access slice service, each network node realizes the allocation and scheduling of the slice resources of the access link according to the allocated network slice resources. The access slice resources are the slice resources of the links accessed from other networks, users, or service terminals, and are allocated by the edge nodes of each network.

[0079] S5: Slice scheduling and implementation of network nodes. After the slice services and slice allocation are completed, each network node periodically schedules the allocated slices for service bearer. When transmitting slice services, slice service identifiers and service parameters, etc. are added to the transmitted data packets, and the network nodes map the data packets carrying service parameters to the corresponding slices for transmission.

[0080] Further, the above service identifier can be defined based on features such as the five-tuple of the data packet, or other specific fields can be defined by itself for representation. In this embodiment, 12 bytes of the destination MAC and source MAC of the data packet are used as the slice service identifier. For the transmission of slice services, its MAC address is no longer used as the basis for forwarding, so it is divided into three segments, respectively representing the slice identifiers of the fixed network, mobile network, and satellite network. As Figure 3 shown, it is a schematic diagram of the slice service identifier of the fixed-mobile-satellite integrated network. The slice lengths of the slice identifiers of the fixed network, mobile network, and satellite network are all 4 bytes. For easy identification, the first bit of the Ethernet destination MAC and source MAC is fixed as 1 (less used when the source and destination are both multicast addresses) as the service identifier of the slice. Therefore, for the 4 bytes of the service identifiers of the mobile network and satellite network, only 31 bits are used to represent the slice resource identifier.

[0081] In the above steps, the service parameters are carried by the data packet, specifically using 4 bytes of the type field in the data packet to carry. So that when transmitting slice services, each different network node can analyze the corresponding bearer requirements according to the type field information in the data packet and map it to the corresponding type of slice for transmission, thereby meeting the bearer requirements of slice services.

[0082] For slice services that require high-quality transmission, according to the 5G network scenarios and requirements, in this embodiment, the high-quality transmission service requirements can be divided into 6 major fields with a total of 13 specific types. The service parameters include bandwidth, delay, and jitter information. The service types and service parameters carried by the slice are shown in Table 1.

[0083] Table 1

[0084]

[0085]

[0086] The service parameters are carried in the data packet, and 4 bytes (32 bits) of the service type in the fixed-mobile-satellite network data packet are used to represent, and the specific content is as follows:

[0087] (1) Field: 3 bits, representing 8 fields, actually 6 kinds.

[0088] (2) Application: 3 bits, representing 8 applications, actually at most 5 kinds.

[0089] (3) Traffic bandwidth: 10 bits, with the unit of Mbps.

[0090] (4) Latency unit: 2 bits, indicating the units of milliseconds (ms), microseconds (us), and nanoseconds (ns).

[0091] (5) Latency: 10 bits, representing the specific latency value, combined with the latency unit.

[0092] (6) Jitter: 4 bits, representing the jitter level, with a total of 16 types, including 7 types: ms, us, 10us, 100us, ns, 10ns, and 100ns.

[0093] Further, in one embodiment, as Figure 1 and Figure 4 shown, it is a schematic diagram of the service bearer configuration and optimization by the converged network controller. To meet the requirements of slice services, the slice services of end-to-end bearer are parameter-optimized through artificial intelligence methods. In this embodiment, the above step S1 includes the following steps:

[0094] S101: Information classification. The converged network controller receives the data input by each node in the network through the management and control interface, including management and configuration information, monitoring information, and service bearer requirement information, and stores them in the knowledge base. The converged network controller also receives the service bearer information of each link data packet slice in the previous cycle feedback by each node through the feedback component.

[0095] S102: Evaluation and optimization model. The data is learned and trained, and the learning component uses artificial intelligence to learn and understand the above information to generate a model-based slice resource allocation strategy and configuration.

[0096] S103: Decision-making and judgment. The configuration generation component configures, learns, and reasons according to the service bearer requirements and the slice resource allocation strategy to find the optimal solution of the slice resources that meet the requirements.

[0097] S104: Configuration application. The automatic configuration component forms a specific type of slice resource allocation strategy or configuration according to the optimal solution of the slice resources provided by the configuration generation component, fills the required preset template by calling the template, and distributes it to the nodes in the network for configuration.

[0098] S105: Monitoring and collection. During the operation of the fixed-mobile-satellite converged network, the feedback component obtains the network measurement data related to the slice resource configuration from each node in the network, makes judgments on the goals and expected states of user requirements, etc., and uses the relevant results as the data for system analysis.

[0099] S106: Adjust the service bearer characteristics of the terminal. The converged network controller sends the services whose service bearer requirements need to be adjusted to the terminal. When the terminal sends sliced service data packets, it carries appropriate service characteristics to achieve high-quality transmission of sliced services.

[0100] Further, in one embodiment, the above network slice resource allocation and scheduling are performed by each network controller, and the access slice resource allocation and scheduling are processed by each network edge node. In step S2 above, each network controller sets the slice resources of each node and link in the network according to the transmission path of the sliced service. An example of the slice resource allocation method for some sliced service transmission paths:

[0101] (1) The sliced service path is "user / service terminal → mobile network → satellite network → fixed network → user / service terminal":

[0102] (a) In the mobile network, the access slice resource allocation and scheduling method is used for the link between the user terminal and the mobile network, and the network slice resource allocation and scheduling method is used for the link between the mobile network and the satellite network.

[0103] (b) In the satellite network, the access slice resource allocation and scheduling method is used for the link between the mobile network and the satellite network, and the network slice resource allocation and scheduling method is used for the link between the satellite network and the fixed network.

[0104] (c) In the fixed network, the access slice resource allocation and scheduling method is used for the link between the satellite network and the fixed network, and the network slice resource allocation and scheduling method is used for the fixed network.

[0105] (2) The sliced service path is "user / service terminal → mobile network → star network → mobile network → user / service terminal": Similar to the previous case, the network slice resource allocation and scheduling method is used inside each network, and the access slice resource allocation and scheduling method is used for the network side of the upper connection interface and user access.

[0106] (3) The sliced service path is "user / service terminal → mobile network → fixed network → user / service terminal": Similar to the previous case, the network slice resource allocation and scheduling method is used inside each network, and the access slice resource allocation and scheduling method is used for the NNI (Network-to-Network Interface) side of the upper connection interface and user access.

[0107] (4) The sliced service path is "user / service terminal → mobile network → fixed network → mobile network → user / service terminal": Similar to the previous case, the network slice resource allocation and scheduling method is used inside each network, and the access slice resource allocation and scheduling method is used for the NNI side of the upper connection interface and user access.

[0108] (5) The slice service path is "user / service terminal → satellite network → mobile network → user / service terminal": Similar to the previous case, within each network, the network slice resource allocation and scheduling method is adopted, and the access slice resource allocation and scheduling method is adopted on the NNI side of the upper connection interface and for user access.

[0109] (6) The slice service path is "user / service terminal → satellite network → fixed network → user / service terminal": Similar to the previous case, within each network, the network slice resource allocation and scheduling method is adopted, and the access slice resource allocation and scheduling method is adopted on the NNI side of the upper connection interface and for user access.

[0110] (7) The slice service path is "user / service terminal → fixed network → mobile network → user / service terminal": Similar to the previous case, within each network, the network slice resource allocation and scheduling method is adopted, and the access slice resource allocation and scheduling method is adopted on the NNI side of the upper connection interface and for user access.

[0111] (8) The slice service path is "user / service terminal → fixed network → satellite network → user / service terminal": Similar to the previous case, within each network, the network slice resource allocation and scheduling method is adopted, and the access slice resource allocation and scheduling method is adopted on the NNI side of the upper connection interface and for user access.

[0112] For other cases, they are all similar to the previous cases.

[0113] Further, in one embodiment, in the above step S3, within each network, the slice service transmission chain route calculates the allocation of network slice resources for the next scheduling period according to the current slice service status by its respective network controller, and sends the calculation result to the network nodes for scheduling, including: collecting the slice transmission service data packet information of the current scheduling period through each node in the network and sending it to the corresponding network controller; each network controller calculates the result of maximizing the network slice value according to the service data packet information collected in its own network, generates the configuration of the network slice service for the next scheduling period based on the result and sends it down, and allocates slice resources for the links between nodes in the network.

[0114] Specifically, different values are set for different types of slices in the network, and the slice value is adjusted according to the number of slices; the sum of the values of various slices of a network node is the node slice value, and the sum of all node slice values is the network slice value. To calculate the result of maximizing the network slice value, optimization algorithms such as linear programming can be used to calculate the maximization of the network slice value that meets the constraint conditions and allocate slice resources for the links between nodes in the network.

[0115] Such as Figure 5As shown in the figure, it is a flowchart of a network slice resource allocation method. Combining with the above step S3, in this embodiment, after the mobile network accesses the satellite network and relays through the satellite network to access the terrestrial fixed network to implement end-to-end slice allocation and scheduling, the network slice resource allocation and scheduling in the satellite network are described. Other network processing methods are similar. The method of this embodiment includes:

[0116] S301: The converged network controller configures the value of each slice and network information. According to the types of deterministic services, 13 types of slices are set. Different types of slice services are set with different values m1, m2,..., mn, where n = 13; resource information such as network topology, network nodes, link bandwidth, and time slices is obtained.

[0117] S302: Collect slice information of network nodes. Each satellite node summarizes the packet services carried and destination addresses received in the previous scheduling period and sends them to the controller of the satellite network.

[0118] S303: Calculate the slice value allocated to a single satellite in each scheduling period. The calculation formula is as follows:

[0119]

[0120] where u is the slice value, l is the satellite node number, n represents the slice type, s n is the number of slices of slice n, and m n is the value of slice n.

[0121] The boundary effect function of the slice quantity is represented by f(s n ). The more the quantity of each type of slice, the more resources of the same type are consumed, other resources are wasted, and the benefit decreases. f(s n ) can be selected according to the slice strategy target. For the convenience of engineering processing, it is simplified as follows:

[0122]

[0123] where is the upper limit of the slice quantity where the benefit is proportional to the slice quantity, and is the upper limit of the slice quantity to obtain the benefit. When the slice quantity is less than , the benefit is proportional to the slice quantity; when the slice quantity is between and , the benefit of the slices exceeding is halved; when the slice quantity exceeds , the slices exceeding the part no longer obtain the benefit.

[0124] S304: Satellite network controller slice allocation. Based on information such as the destination address, network topology, and link bandwidth of the satellite node slice requirements, calculate the slice value of all satellite nodes in the entire satellite network, satisfying constraints such as network topology and bandwidth, to maximize the value in the entire satellite network. The calculation formula is as follows:

[0125]

[0126] Among them, l is the satellite node number, B represents the total number of satellite nodes in the satellite network, and the constraints are:

[0127] (a) The radio resource slice capacity of the satellite node feeder link meets the allocated slice;

[0128] (b) The destination is reachable or approaches the destination when entering the next network domain;

[0129] (c) The bandwidth of the satellite uplink feeder link and between network nodes is less than the bandwidth capacity of the node.

[0130] Heuristic optimization algorithms such as linear programming can be used to calculate the optimal slice quantity and slice type of each satellite under the condition of maximum value.

[0131] S305: Controller slice resource distribution. The controller of the satellite network distributes the calculated optimal slice quantity and slice type of the satellite nodes to each node of the satellite network.

[0132] S306: Network node slice resource scheduling. The satellite node forwards data packets according to the allocated slice resources.

[0133] In the above step S4, the allocation of each network edge node refers to the allocation of slice resources by the edge network node according to the priority order of service data packets. Specifically, each network edge node obtains the service parameters of the service data packet, calculates the priority of the data packet according to the preset weight adjustment factor, and allocates the data packet to the corresponding slice resource and schedules the transmission according to the priority order. The service parameters include bandwidth, delay, and jitter information.

[0134] As Figure 6 shown, it is the flowchart of the access slice resource allocation method. In this embodiment, taking the mobile network accessing the satellite network and then relaying through the satellite network to access the ground fixed network to implement end-to-end slice allocation and scheduling as an example, the access slice resource allocation and scheduling in the satellite network are described. Other network processing methods are similar. The specific processing flow is as follows:

[0135] S401: Network node parameter configuration. The satellite node configures parameters such as the weight adjustment factors k1, k2, and k3 for service priorities, which determine the importance of influencing factors for different characteristic services. For example, for delay-sensitive services, the weight of k1 is relatively large; for users with characteristics of bandwidth-sensitive services, the weight of k2 is relatively large; and k1 + k2 + k3 = 1 is satisfied.

[0136] S402: Packet priority calculation. When the satellite node receives a packet, it allocates the corresponding slice and performs scheduling. At the same time, it calculates the packet priority as the basis for slice resource allocation in the next scheduling cycle. The priority P i (t) is calculated by the following formula:

[0137]

[0138] where i is the service number, T i ≤W i (t); r i ≤R i ; J i ≤j i ; W i (t) is the requirement for the transmission waiting delay of service i; T i is the delay target value of the slice of the access type of this service; r i (t) is the requested rate of this service; R i (t) is the average rate of the slice of the access type of this service; j i (t) is the transmission jitter requirement of this service, J i (t) is the jitter information (constraint target value) of the slice of the access type of this service, and t represents the scheduling cycle. k1, k2, and k3 are preset weight adjustment factors.

[0139] S403: Calculate the sum of the priorities of service flows or user packets in this scheduling cycle. After the scheduling cycle ends, calculate the priorities P(t) of all packets allocated to different service flows or users in each access link. The calculation method is as follows:

[0140]

[0141] S404: Allocate for different links of the satellite node, including allocating resources for the incoming interface of the satellite node and also including allocating resources for the outgoing interface of the satellite node.

[0142] Allocate resources for the ingress interface, that is, allocate access service or user slice resources. For example, when a mobile phone directly connects to a satellite network, it mainly allocates slices for the link between the mobile phone and the satellite. In this embodiment, based on the sum of the priorities of all service or user data packets in the previous scheduling period, allocate the mapping of satellite radio link slice resources and network slice resources in the order of priority. If the slice resources corresponding to the uplink of the access node are allocated, forward the subsequent deterministic services as ordinary data packets. The uplink slice resources are allocated by the network slice resource allocation and scheduling method.

[0143] Allocate resources for the egress interface, that is, the network access node allocates link slices in the network. For example, after the satellite node receives the service sent by the mobile phone, it allocates slices inside the satellite network. In this embodiment, the satellite access node allocates network-level uplink slice resources to carry data packets. If the slice resources corresponding to the uplink of the access node are allocated, forward the subsequent deterministic services as ordinary data packets; if the slice resources corresponding to the uplink of the access node are not allocated, allocate the uplink slice resources on a best-effort basis. The uplink slice resources are allocated by the network slice resource allocation and scheduling method.

[0144] It can be seen that when allocating resources for the ingress of the satellite node, it is mainly allocated in the order of priority; when allocating resources for the egress interface of the satellite node, it is allocated on a first-come, first-served basis and on a best-effort basis.

[0145] Furthermore, in step S5 above, the network node maps according to the service bearer parameters carried in the service data packet and transmits it in the corresponding slice, including: the network node analyzes the service parameters carried in the service data packet, and through the time slot scheduling mechanism that integrates the radio link and the fixed link, maps the service data packet to the matching slice type and forwards it through the network node. Specifically, the link slice types in the fixed network, mobile network, and satellite network are divided into two categories: radio link and fixed link. The time slot scheduling mechanism includes: linearizing the scheduling of the two-dimensional slice resources of the radio link, which is consistent with the linear slice resource scheduling of the fixed link; through time slot scheduling, periodically scan various types of slices allocated in different time slots to implement the time slot-based slice scheduling mechanism. When mapping the service data packet to the slice, according to the bandwidth, delay, and jitter information carried in the data packet, when allocating to different slices, it meets the quality metrics of the service characteristics.

[0146] Such as Figure 7As shown in the figure, an embodiment of network node slice scheduling and implementation is provided. The slice scheduling in the network node is divided into relatively large scheduling periods, and each scheduling period is divided into smaller time slots. The interval of the time slots is related to the slice delay size. According to the application requirements, in this embodiment, the slice transmission delays are divided into five types: less than 200 us, 1 ms, 10 ms, 100 ms, and no delay requirement, and the corresponding slice sizes are five types: 2M, 10M, 50M, 100M, and 1G. The network node slice scheduling method includes the following steps:

[0147] S501: Set the time slot scheduling mechanism. According to the delay requirements of different slice types, interval corresponding time slices, check whether there is data packet transmission, and ensure that the transmission delay of each slice can be satisfied. For example, for a 2M slice, monitor whether there is data to be sent every 200 us until the sending is completed or the amount of data sent within this period reaches the upper limit of this slice; for a 50M slice, monitor whether there is data transmission every 10 ms.

[0148] In fixed networks, mobile networks, and satellite networks, the wireless link is between the mobile network user equipment and the satellite network, the feeder link is mainly between the satellite network and the terrestrial fixed network, and the internal of the satellite network and the terrestrial fixed network is mainly a high-bandwidth laser link or optical fiber link. Therefore, the three networks mainly include two types: wireless links and fixed links, and the slice scheduling strategy is scheduled according to the two different links. The linearization scheduling of the two-dimensional slice resources of the wireless link is consistent with the linear slice resource scheduling of the fixed link.

[0149] For the slice resources of the wireless link, the slices in the wireless link are for the division of frequency band resources. The frequency band resources are composed of resource blocks interleaved in the frequency domain and time domain. The unit of frequency band resource allocation is also the resource block. The wireless slice resources are as Figure 8 shown, which is a resource block (RB) defined according to the standard. A resource block contains 12 subcarriers, and 14 symbols can be transmitted in each time slot. The minimum unit for allocating frequency domain resources in the frequency domain is the subcarrier, that is, a section of frequency domain bandwidth. As Figure 9 shown, it is a schematic diagram of the wireless resource slice bearing of the data packet. The slice time slot is a period of time specified in the 3GPP protocol. The 3GPP protocol stipulates that the time slot time of the time slice is related to the subcarrier spacing (frequency). In the 3GPP standard, the number of wireless access subcarriers does not have a fixed value, but is dynamically determined according to factors such as subcarrier spacing, spectrum configuration, and system bandwidth. 3GPP 5G NR supports multiple subcarrier spacings (SCS), such as 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. The relationship between the network subcarrier spacing and the time slot length is shown in Table 2.

[0150] Table 2

[0151]

[0152] A sub - carrier usually contains 14 OFDM symbols in a time slot, and each symbol carries different numbers of bits according to the modulation mode of the signal. The radio link allocates frequency - band resources to specific users in the form of resource blocks to achieve functions such as wireless transmission and channel measurement.

[0153] For a resource block (RB), each resource block consists of a frequency bandwidth and a time slot. The larger the interval, the higher the occupied frequency bandwidth and the shorter the time slot; conversely, the smaller the frequency bandwidth, the longer the time slot. One resource block = 12 sub - carriers × sub - carrier interval × time - slot length. In 3GPP, it is defined that each resource block contains 12 sub - carriers. Under different sub - carrier intervals, the size of the resource block is different:

[0154] When the SCS is 15 kHz, the RB frequency - bandwidth size is 180 kHz (15×12).

[0155] When the SCS is 30 kHz, the RB frequency - bandwidth size is 360 kHz (30×12).

[0156] When the SCS is 60 kHz, the RB frequency - bandwidth size is 720 kHz (60×12).

[0157] When the SCS is 120 kHz, the RB frequency - bandwidth size is 1440 kHz (120×12).

[0158] When the SCS is 240 kHz, the RB frequency - bandwidth size is 2880 kHz (240×12).

[0159] 3GPP 38.101 defines the maximum transmission bandwidth of each UE under different sub - carrier intervals, and the calculation method is as follows:

[0160] The number of resource blocks NRB=(channel bandwidth - 2×guard bandwidth) / bandwidth of one RB

[0161] For SCS = 15 kHz, the bandwidth of one RB is 180 kHz. For a channel bandwidth of 100 MHz and a guard bandwidth of 692.5 kHz, the number of its RBs is:

[0162] NRB=(100×10 3 - 2×692.5) / 180 = 547 resource blocks

[0163] For SCS = 30 kHz, the bandwidth of one RB is 360 kHz. For a channel bandwidth of 100 MHz and a guard bandwidth of 845 kHz, the number of its RBs is:

[0164] NRB=(100×10 3 - 2×845) / 360 = 273 resource blocks

[0165] For SCS = 60 kHz, the bandwidth of one RB is 720 kHz. For a channel bandwidth of 100 MHz and a guard bandwidth of 1370 kHz, the number of RBs is:

[0166] NRB = (100 × 10 3 -2 × 1370) / 720 = 135 resource blocks

[0167] According to 3GPP specifications (such as 38.104), the number of RBs is different under different frequency bandwidths and subcarrier spacings. This flexible configuration method enables 5G NR to optimize signal transmission according to different application scenarios and spectrum conditions.

[0168] A larger subcarrier spacing means that the time length of each OFDM symbol is shorter, reducing the risk of inter-symbol interference, allowing a shorter cyclic prefix (CP), and thus improving spectral efficiency. A larger subcarrier spacing results in shorter time slots, and shorter time slots provide higher scheduling flexibility, enabling faster response to changing channel conditions and dynamic resource allocation according to user needs. Within the same total bandwidth, a larger subcarrier spacing will reduce the total number of resource blocks.

[0169] A time slot is the smallest scheduling unit in the time dimension. Different types of control channels or data channels can be arranged within one time slot. According to different subcarrier spacings, the time slot intervals are also different. The flexibility of time slot configuration enables finer-grained resource partitioning. By flexibly adjusting the subcarrier spacing and time slot allocation, the system can adapt to a highly dynamic network environment and changing service requirements while ensuring high data rates. For example, when mainly providing eMBB services, a smaller subcarrier spacing can be adopted to increase the length of data transmission time slots and improve data throughput; while when supporting URLLC services is required, a higher subcarrier spacing and a smaller time slot interval can be adopted to ensure low latency.

[0170] The implementation method of radio link slice resources is as follows:

[0171] (1) When allocating radio link slice resources, allocate them in the order of subcarriers first and then time slots (column first and row second), and unify them into linear slice resources for scheduling.

[0172] (2) Design the subcarrier spacing based on the latency requirements. For each radio link, the subcarrier spacing includes 15 KHZ, 30 KHZ, 60 KHZ, 120 KHZ, and 240 KHZ, corresponding to 5 types of slice transmission latency requirements: no latency requirement, 100 ms, 10 ms, 1 ms, and less than 200 us; the corresponding slice sizes are 2M, 10M, 50M, 100M, and 1G, etc. When scheduling, schedule according to the subcarrier order and time interval.

[0173] For the bearer link slice resources, which are generally laser links or optical fiber links, etc., the slicing is divided with reference to the small-granularity slicing mechanism of the bearer network. The bearer link slice bears data packets as Figure 10 shown. After receiving the slice data packet in the slicing transport layer (STL) of the PE device in the bearer network, it is recognized as a slice data packet. In the slicing channel layer (SCL), each slice is reorganized into a packet data packet, and then the egress interface is found according to the information such as ETH / MPLS / IP / SR in the data packet. Small-granularity slicing is performed in the slicing channel layer of the egress interface, and the transport layer transmits the small-granularity slices according to time slots. The slicing bearer mechanism of small granules adopts the time-division mechanism, and the small-granularity slice (FGU) frames are cyclically sent at a fixed period. The number and position of time slots included in each frame are strictly fixed. Therefore, the sending period of each time slot is also deterministic. As Figure 11 shown, it is a schematic diagram of bearer link slice and sub-time slot scheduling.

[0174] (1) In the bearer link slice, a scheduling period is a multi-frame, which contains 20 FGU basic frames ( Figure 10 only FGU basic frame 1 and FGU basic frame 2 are shown in it). Each FGU basic frame supports 24 time slots. The SPN channel is 5 Gbit / s. For a 5 Gbps granule, 480 time slots are supported. When slicing a 5G link, each time slot transmits a 66B code block, with an average of 10 Mbps per time slot, which can be further divided into 4 granules with a bandwidth of 2 Mbps.

[0175] (2) When performing slice allocation and scheduling for the bearer link, the number of various granule slices within a unit period is evenly distributed to each sub-time slot as the upper limit carried by that sub-time slot.

[0176] S502: Cross-network packet reception or packet slice allocation on the receiving end side. When a node receives a data packet forwarded by another network or a user data packet, for example, when a satellite node receives a data packet sent by a directly connected satellite phone, it selects the type with the highest slice quality and allocates it to the received data packet. According to the bandwidth, delay, and jitter information in the service parameters carried by the data packet, the different slice qualities are calculated according to the following formula:

[0177]

[0178] where b is the bandwidth requirement in the data packet, B is the bandwidth of the slice time slot allocated by scheduling, t is the delay requirement of the data packet, T is the transmission delay of the time slot allocated by scheduling, j is the jitter requirement of the data packet, and J is the slice transmission jitter allocated by scheduling; to satisfy the data packet transmission, it is necessary to satisfy b ≤ B, t ≥ T, and j ≥ J.

[0179] In addition, in slice transmission, the satisfaction degree of jitter information is strongly correlated with the product of the bandwidth and delay satisfaction degrees. For example, if a data packet is transmitted in 1 slice, the jitter is half of the time slice transmission delay; if it is transmitted in n slices, the jitter is (n - 0.5) times the time slice transmission delay. The jitter information J of the slice can be determined according to the delay information T of the slice transmission.

[0180] Therefore, when receiving a data packet on a wireless link, the slice with the highest quality level matching the data packet and the wireless link resources is selected and assigned to the subcarriers in the corresponding interval for carrying. When receiving a data packet on a bearer link, the corresponding slice resources are allocated according to the maximum link quality of the data packet, and the data packet is filled into the corresponding slice; if it cannot be satisfied, a slice with a close quality of service is selected for allocation.

[0181] S503: Determine whether the slice resources in this scheduling period are sufficient. If so, it means that the access slice resources corresponding to the data packet in this period are sufficient, and go to S504; if not, it means that the access slice corresponding to the data packet in this period has been used up, and go to S505.

[0182] S504: Select the slice resources with the optimal slice quality for forwarding, and go to S506.

[0183] S505: Use the largest slice for transmission. When the largest slice cannot meet the delay requirement, use the remaining gaps after other slice scheduling for transmission.

[0184] S506: Forward the slice data packet on the access side. When sending the data packet slice, during each sub-slot scheduling, scan from the smallest slice to the largest to check if there is a corresponding slice data packet. If there is, then forward it.

[0185] S507: Set the slice resource allocation and scheduling for the data packet on the network side. After the access satellite node receives the data packet transmitted by the user side slice and forwards it to the network side link, allocate slices with the same slice quality for mapping and carrying. If this type of slice has been used up, use the largest slice for default transmission. Since the access side is scheduled in the order of priority, it can ensure that high-priority data packets meet the slice allocation and transmission requirements.

[0186] S508: Forward the slice data packet on the network side. When sending the data packet slice, during each sub-slot scheduling, scan from the smallest slice to the largest to check if there is a corresponding slice data packet. If there is, then forward it.

[0187] In the above steps, steps S502 - S506 illustrate the allocation and transmission of slices on the access side of the network edge node; steps S507 - S508 illustrate the slice allocation and transmission within the network (including the uplink of the edge node and the internal links of the network). S505 - S506 are for the slice transmission of the access, such as a mobile phone directly connecting to a satellite network, mainly for the slice transmission of the link between the mobile phone and the access satellite; S507 - S508 are for the internal transmission on the network side, such as after the satellite node receives the service sent by the mobile phone, it performs slice transmission within the satellite network.

[0188] In addition, in each scheduling period, the slice sizes and quantities required for the access - side and network - side data packets, as well as the actually allocated slice sizes and quantities, are counted and used as the basis for slice allocation in the network - level slice resource allocation and scheduling and the access - level slice resource allocation and scheduling in the next scheduling period. It can also be calculated based on the weighted average of multiple periods to avoid drastic changes in slice requirements.

[0189] In a second aspect, a device for the slice resource allocation and scheduling method in a fixed - mobile - satellite integrated network is provided to implement the slice resource allocation and scheduling method in the fixed - mobile - satellite integrated network. In this embodiment, the device includes a fusion network control module, a resource allocation module, a mapping module, an adjustment module, and three network control modules; among them, the three network control modules are a fixed - network control module, a mobile - network control module, and a satellite - network control module respectively.

[0190] The fusion network control module is used for the fusion network controller to obtain the end - to - end service bearer requirements, generate service identifiers and service parameters, and send them to the network controllers of the fixed network, mobile network, and satellite network.

[0191] The three network control modules are used for each network controller to allocate the allocation and scheduling of network slice resources in the next scheduling period according to the current slice service status. Specifically, the fixed - network control module is used for the fixed - network controller to allocate the allocation and scheduling of network slice resources in the next scheduling period according to the current slice service status; the mobile - network control module is used for the mobile - network controller to allocate the allocation and scheduling of network slice resources in the next scheduling period according to the current slice service status; the satellite - network control module is used for the satellite - network controller to allocate the allocation and scheduling of network slice resources in the next scheduling period according to the current slice service status.

[0192] The resource allocation module is used for the edge network node to allocate access slice resources according to the priority order of service data packets.

[0193] The mapping module is used for the network node to map the service bearer requirements carried by the service data packet to the corresponding slice for transmission.

[0194] An adjustment module for adjusting the service bearer characteristics in a data packet according to the configuration and operation results of the slice carried by the fusion network controller.

[0195] In this embodiment, the fusion network control module is used to enable the fusion network controller to obtain the end-to-end service bearer requirements, generate service identifiers and service parameters, and send them to the network controllers of the fixed network, mobile network, and satellite network, and carry the service bearer requirements of the resources in the data packet. Through three network control modules, each network controller realizes the allocation and scheduling of network slice resources in the next scheduling period according to the current slice service status, achieving efficient slice utilization, avoiding the problem of low utilization rate of slices allocated based on services, and improving the joint optimization of fixed, mobile, and satellite networks.

[0196] The terms "including" and "having" and any variations thereof in the description of the specification, claims, and the above drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally further include steps or units not listed, or may optionally further include other steps or units inherent to these processes, methods, products, or devices. The descriptions of terms such as "first", "second", and "third" are used to distinguish different objects, etc., and do not represent a sequential order, nor do they limit that "first", "second", and "third" are different types.

[0197] In the description of the embodiments of this application, words such as "exemplary", "for example", or "for illustration purposes" are used to indicate examples, illustrations, or explanations. Any embodiment or design solution described as "exemplary", "for example", or "for illustration purposes" in the embodiments of this application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary", "for example", or "for illustration purposes" is intended to present related concepts in a specific manner.

[0198] In the description of the embodiments of this application, unless otherwise specified, " / " means "or". For example, A / B may mean A or B; the "and / or" in the text is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B may mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "a plurality of" means two or more than two.

[0199] In some processes described in the embodiments of the present application, there are multiple operations or steps that appear in a specific order. However, it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or may be executed in parallel. The serial numbers of the operations are only used to distinguish different operations, and the serial numbers themselves do not represent any execution order. Additionally, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

[0200] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-described embodiment methods can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases, the former is a better implementation method. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium as described above (such as ROM / RAM, magnetic disk, optical disc) and includes several instructions for causing a terminal device to execute the methods described in the various embodiments of the present application.

[0201] The above are only the preferred embodiments of the present application, and do not limit the patent scope of the present application. Any equivalent structural or equivalent process transformation made by using the content of the specification and drawings of the present application, or directly or indirectly applied in other related technical fields, shall be equally included in the patent protection scope of the present application.

Claims

1. A method for slice resource allocation and scheduling in a fixed-mobile convergence network, characterized in that The method includes: Obtaining end-to-end service bearer requirements through a converged network controller, generating service identifiers and service parameters, and sending them to the network controllers of the fixed network, mobile network, and satellite network; Each network controller allocates and schedules network slice resources for the next scheduling period according to the current slice service status; the edge network nodes allocate access slice resources according to the priority order of service data packets; The network nodes map the service parameters carried in the service data packets to the corresponding slices for transmission; The converged network controller adjusts the service parameters in the data packets according to the configuration and operation results of the slice bearer.

2. The method for slice resource allocation and scheduling in the fixed-mobile convergence network according to claim 1, wherein The step of obtaining end-to-end service bearer requirements through a converged network controller, generating service identifiers and service parameters, and sending them to the network controllers of the fixed network, mobile network, and satellite network includes: The converged network controller obtains service bearer requirements through the management and control interface; Generating service identifiers for the fixed network, mobile network, and satellite network respectively; According to the service bearer requirements, generating service parameters for the slice through the service type field of the data packet, and sending them to each network node through the network controllers of the fixed network, mobile network, and satellite network.

3. The method for allocating and scheduling slice resources in the fixed-mobile-satellite converged network according to claim 1, wherein: The allocation and scheduling of network slice resources are performed by the network controller, including allocating slice resources for the internal interconnection links of the corresponding network and allocating uplink slice resources for the edge nodes; The access slice resources are the link slice resources accessed from other networks, users, or service terminals, and are allocated by each network edge node.

4. The method for slice resource allocation and scheduling in the fixed-mobile convergence network according to claim 3, wherein Each network controller allocates and schedules network slice resources for the next scheduling period according to the current slice service status, including: Collecting slice transmission service data packet information of the current scheduling period through each node in the network and sending it to the corresponding network controller; Each network controller calculates the result of maximizing the value of the network slice based on the service data packet information collected in its own network, generates the configuration of the network slice service for the next scheduling period based on the result, and sends it down to allocate slice resources for the links between nodes in the network.

5. The method for allocating and scheduling slice resources in the fixed-mobile-satellite converged network according to claim 4, wherein: Setting different values for different types of slices in the network and adjusting the slice values according to the number of slices; The sum of the values of various slices of a network node is the node slice value, and the sum of all node slice values is the network slice value.

6. The method for slice resource allocation and scheduling in the fixed-mobile convergence network according to claim 3, wherein The step of allocating slice resources by the edge network nodes according to the priority order of service data packets includes: Each network edge node obtains the service parameters of the service data packet, calculates the priority of the data packet according to a preset weight adjustment factor, and allocates the data packet to the corresponding slice resource and schedules the transmission according to the priority order. The service parameters include bandwidth, delay, and jitter information.

7. The method for slice resource allocation and scheduling in the fixed-mobile integrated network according to claim 1, characterized in that, The step of the network nodes mapping the service bearer parameters carried in the service data packets to the corresponding slices for transmission includes: The network node analyzes the service parameters carried in the service data packet, maps the service data packet to a matching slice type through a time slot scheduling mechanism that integrates the wireless link and the fixed link, and forwards it through the network node. The service parameters include bandwidth, delay, and jitter information.

8. The method for slice resource allocation and scheduling in the fixed-mobile convergence network according to claim 7, wherein The time slot scheduling mechanism includes: Linearize the scheduling of the two-dimensional slice resources of the wireless link to be consistent with the linear slice resource scheduling of the fixed link; through time slot scheduling, periodically scan various types of slices allocated in different time slots.

9. The method for slice resource allocation and scheduling in the fixed-mobile convergence network according to claim 1, characterized in that The converged network controller adjusts the service parameters in the data packet according to the configuration and operation results carried by the slice, including: The converged network controller obtains the slice service statistics feedback by each network node, analyzes the operation results through artificial intelligence technology and optimizes the service bearing characteristics, sends the adjusted service parameters to the terminal, and updates the data packet.

10. An apparatus for a slice resource allocation and scheduling method in a fixed-mobile convergence network according to any one of claims 1-9, characterized in that, The device includes: A converged network control module, which is used to obtain the end-to-end service bearing requirements through the converged network controller, generate service identifiers and service parameters, and send them to the network controllers of the fixed network, mobile network, and satellite network; Three network control modules, which are used for each network controller to allocate and schedule the network slice resources in the next scheduling cycle according to the current slice service status; A resource allocation module, which is used for the edge network node to allocate access slice resources according to the priority order of the service data packet; A mapping module, which is used for the network node to map the service bearing requirements carried in the service data packet to the corresponding slice for transmission; An adjustment module, which is used for the converged network controller to adjust the service bearing characteristics in the data packet according to the configuration and operation results carried by the slice.

Images