Network slicing method and apparatus

Abstract

The present disclosure relates to the technical field of communications, and in particular to a network slicing method and apparatus. The network slicing method comprises: receiving slicing requirement information corresponding to a first network slice layer, wherein the slicing requirement information is used for indicating resource information for performing network slicing on a resource corresponding to the first network slice layer; on the basis of the slicing requirement information, performing network slicing on the resource corresponding to the first network slice layer, to obtain a network slicing result corresponding to the first network slice layer; and on the basis of the network slicing result corresponding to the first network slice layer, performing network slicing on a resource corresponding to a second network slice layer, to obtain a network slicing result corresponding to the second network slice layer. The present disclosure can improve the matching between network slices and slicing requirement information, thereby improving the accuracy of network slicing, and can achieve the management efficiency of a satellite network, thereby improving the service quality.

Description

Network slicing method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on January 9, 2024, with application number 202410028492.9 and application name “Network Slicing Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present disclosure relates to the field of communication technology, and in particular to a network slicing method and device. Background Art

[0003] In a communications system, a physical network can be segmented to form at least one logically independent virtual network, called a network slice. Different network slices can provide different services. For example, network slices can be obtained by relying on virtual private networks (VPNs) and segment routing (SR) technologies.

[0004] Summary of the Invention

[0005] The present disclosure provides a network slicing method and device to improve the coordination and comprehensiveness of slicing solutions at each layer, improve the adaptability of network slicing, and improve the accuracy of network slicing, which can achieve management efficiency of satellite networks and improve service quality.

[0006] The technical solutions disclosed in this disclosure are as follows:

[0007] According to a first aspect of an embodiment of the present disclosure, a network slicing method is provided, which is applied to a network-side device, including:

[0008] Receive slicing requirement information corresponding to a first network slicing layer, wherein the slicing requirement information is used to indicate resource information for performing network slicing on resources corresponding to the first network slicing layer;

[0009] Perform network slicing on the resources corresponding to the first network slicing layer according to the slicing requirement information, and obtain a network slicing result corresponding to the first network slicing layer;

[0010] According to the network slicing results corresponding to the first network slicing layer, network slicing is performed on the resources corresponding to the second network slicing layer to obtain the network slicing results corresponding to the second network slicing layer.

[0011] According to some embodiments, the receiving slicing requirement information corresponding to the first network slicing layer includes at least one of the following:

[0012] Receive slice management information sent by the slice management layer, wherein the slice management information includes slice requirement information corresponding to the first network slice layer;

[0013] Receive resource request information sent by the second network slicing layer, wherein the resource request information includes slice requirement information corresponding to the first network slicing layer;

[0014] Receive service requirement information sent by the application layer, wherein the service requirement information includes slice requirement information corresponding to the first network slice layer.

[0015] According to some embodiments, the first network slicing layer is a physical layer, and performing network slicing on resources corresponding to the first network slicing layer according to the slicing requirement information, and obtaining a network slicing result corresponding to the first network slicing layer, includes:

[0016] According to the first service requirement, network slicing is performed on the hardware resources corresponding to the physical layer to obtain the physical layer network slicing results.

[0017] According to some embodiments, the first network slicing layer is a link layer, and performing network slicing on resources corresponding to the first network slicing layer according to the slicing requirement information, and obtaining a network slicing result corresponding to the first network slicing layer, includes:

[0018] According to the physical layer network slicing result and / or the second service requirement, network slicing is performed on the link resources corresponding to the link layer to obtain the link layer network slicing result.

[0019] According to some embodiments, the first network slicing layer is a network layer, and performing network slicing on resources corresponding to the first network slicing layer according to the slicing requirement information, and obtaining a network slicing result corresponding to the first network slicing layer, includes:

[0020] According to the link layer network slicing results and / or the third service requirements, network slicing is performed on the network topology and routing information corresponding to the network layer to obtain the network layer network slicing results.

[0021] According to some embodiments, performing network slicing on resources corresponding to the first network slicing layer according to the slicing requirement information, and obtaining a network slicing result corresponding to the first network slicing layer includes:

[0022] Receive status information sent by the third network slicing layer, wherein the status information includes a network slicing result corresponding to the third network slicing layer;

[0023] Perform network slicing on the resources corresponding to the first network slicing layer according to the slicing requirement information and / or the status information, and obtain the network slicing results corresponding to the first network slicing layer.

[0024] According to some embodiments, the method further comprises:

[0025] Information in JSON format is used for information exchange between the first network slicing layer and the second network slicing layer.

[0026] According to some embodiments, the method further comprises:

[0027] Send the network slicing result to the slice management layer.

[0028] According to a second aspect of an embodiment of the present disclosure, a network slicing method is provided, which is applied to a network-side device, including:

[0029] Determine, based on the slice requirement information received by the first network slice layer, to request resource information from the second network slice layer;

[0030] Sending the slicing requirement information to the second network slicing layer;

[0031] Receive the network slicing result corresponding to the resource information sent by the second network slicing layer in response to the slicing requirement information.

[0032] According to some embodiments, the method further comprises at least one of the following:

[0033] receiving slice management information sent by the slice management layer, wherein the slice management information includes the slice requirement information;

[0034] Receiving resource request information sent by a third network slicing layer, wherein the resource request information includes the slicing requirement information;

[0035] Receive service requirement information sent by the application layer, wherein the service requirement information includes the slice requirement information.

[0036] According to some embodiments, the slice management information also includes resource status information, wherein the resource status information is used to indicate the resource status of the second network slice layer or the resource status information is used to indicate the status of the first network slice layer requesting resources from the second network slice layer.

[0037] According to a third aspect of an embodiment of the present disclosure, a network slicing device is provided, including:

[0038] A first transceiver unit is configured to receive slice requirement information corresponding to a first network slice layer, wherein the slice requirement information is used to indicate resource information for performing network slicing on resources corresponding to the first network slice layer;

[0039] A first processing unit is configured to perform network slicing on resources corresponding to the first network slicing layer according to the slicing requirement information, and obtain a network slicing result corresponding to the first network slicing layer;

[0040] The first processing unit is used to perform network slicing on the resources corresponding to the second network slicing layer according to the network slicing results corresponding to the first network slicing layer, and obtain the network slicing results corresponding to the second network slicing layer.

[0041] According to a fourth aspect of an embodiment of the present disclosure, a network slicing device is provided, including:

[0042] A second processing unit is configured to determine, based on the slice requirement information received by the first network slice layer, to request resource information from the second network slice layer;

[0043] A second transceiver unit is configured to send the slicing requirement information to the second network slicing layer;

[0044] The second transceiver unit is used to receive the network slicing result corresponding to the resource information sent by the second network slicing layer in response to the slicing requirement information.

[0045] According to a fifth aspect of an embodiment of the present disclosure, a network-side device is provided, including:

[0046] processor;

[0047] a memory for storing instructions executable by the processor;

[0048] In which, the processor is configured to execute the instructions to implement the network slicing method described in any one of the aforementioned aspects.

[0049] According to a sixth aspect of an embodiment of the present disclosure, a storage medium is provided. When instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the network slicing method described in any one of the aforementioned aspects.

[0050] According to a seventh aspect of an embodiment of the present disclosure, a computer program product is provided, comprising a computer program, which implements the method described in any one of the preceding aspects when executed by a processor.

[0051] The technical solutions provided by the embodiments of the present disclosure bring at least the following beneficial effects:

[0052] In some or related embodiments, slicing requirement information corresponding to a first network slicing layer is received, wherein the slicing requirement information is used to indicate resource information for performing network slicing on resources corresponding to the first network slicing layer; network slicing is performed on the resources corresponding to the first network slicing layer according to the slicing requirement information, and a network slicing result corresponding to the first network slicing layer is obtained; and network slicing is performed on the resources corresponding to the second network slicing layer according to the network slicing result corresponding to the first network slicing layer, and a network slicing result corresponding to the second network slicing layer is obtained. Therefore, a multi-layer collaborative network slicing mechanism can be provided to reduce the situation where only network resources are divided, resulting in inaccurate network slicing. The coordination and comprehensiveness of slicing solutions at each layer can be improved, the adaptability of network slicing can be improved, the accuracy of network slicing can be improved, the management efficiency of satellite networks can be achieved, and the service quality can be improved.

[0053] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] The accompanying drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute an improper limitation of the present disclosure.

[0055] FIG1 is a flowchart of a network slicing method according to an exemplary embodiment;

[0056] FIG2 is a flowchart of a network slicing method according to an exemplary embodiment;

[0057] FIG3 is a flowchart of a network slicing method according to an exemplary embodiment;

[0058] FIG4 is a flowchart of a network slicing method according to an exemplary embodiment;

[0059] FIG5 is a flowchart of a network slicing method according to an exemplary embodiment;

[0060] FIG6 is a block diagram of a network slicing device according to an exemplary embodiment;

[0061] FIG7 is a block diagram of a network slicing device according to an exemplary embodiment;

[0062] Fig. 8 is a block diagram showing a network-side device according to an exemplary embodiment. DETAILED DESCRIPTION

[0063] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0064] The present disclosure provides network slicing methods and apparatuses. In some embodiments, the terms "network slicing method," "information processing method," and "communication method" are interchangeable; the terms "network slicing apparatus," "information processing apparatus," and "communication apparatus" are interchangeable; and the terms "information processing system," "communication system," and "information processing system" are interchangeable.

[0065] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0066] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0067] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0068] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0069] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0070] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0071] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The same applies when there are more branches, such as A, B, and C.

[0072] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0073] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0074] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0075] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0076] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0077] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0078] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0079] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0080] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

[0081] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0082] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0083] It should be noted that the terms "first," "second," and the like in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the numbers used in this manner are interchangeable where appropriate so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure as detailed in the appended claims.

[0084] According to some embodiments, network slicing technology can, for example, segment a physical network to form at least one logically independent virtual network, referred to as a network slice. Each network slice can be configured and optimized based on different quality of service (QoS) requirements, latency, throughput, and other metrics. Configuration can also be understood as division, configuration, and so on. Therefore, network slicing technology can meet diverse service and business needs while improving the efficiency of network resource utilization.

[0085] Network slicing has been widely used in the internet and mobile communications sectors, providing specific virtual network environments for a variety of use cases and service scenarios, including but not limited to high-bandwidth video streaming, low-latency remote robotics, and large-scale IoT device connectivity. Network slicing technology enables the creation and management of personalized network environments tailored to these diverse service and application requirements.

[0086] For example, satellite network slicing can rely on virtual private network (VPN) and segment routing (SR) technologies to build and manage multiple logical networks in the same physical network to meet the special needs of various services and applications.

[0087] According to some embodiments, a virtual private network (VPN) creates private communication paths over a public network by leveraging network virtualization and tunneling technologies (e.g., IPSec, MPLS, etc.), thereby building and managing multiple logical networks, or slices, on the same physical network. In satellite network environments, VPNs can be used to create network slices, providing logically independent and isolated network environments for different services and applications. Typically, resource allocation in a VPN is based on pre-set policies and service-level agreements (SLAs), such as allocating network resources based on service type, priority, and bandwidth requirements.

[0088] According to some embodiments, segment routing (SR) technologies (such as SR-MPLS and SRv6) implement network slicing and customize and optimize communication paths for different slices by finely controlling and managing network paths. SR slicing achieves separation of network control and data through software-defined networking (SDN), making network management more flexible and efficient. By programming routing, fine control of communication paths can be achieved, for example, selecting the optimal communication path based on service requirements and network conditions, or implementing traffic engineering and load balancing based on network policies. In SR, resource allocation is usually also based on preset policies and SLAs, for example, selecting the best communication path and resources based on service requirements and network conditions.

[0089] However, satellite network slicing technologies based on virtual private networks (VPNs) and segment routing (SR) have significant limitations. First, these technologies mostly rely on static resource allocation strategies, making them difficult to adapt to the unique dynamic and time-varying nature of satellite networks. Second, the management and optimization strategies of VPN and SR primarily focus on the network layer and may not meet deeper, more refined requirements and optimization goals. Finally, these two network slicing technologies have significant deficiencies in the isolation and allocation of hardware resources, resulting in poor quality of service (QoS).

[0090] FIG1 is a flowchart of a network slicing method according to an exemplary embodiment. As shown in FIG1 , the network slicing method can be used in a communication scenario and includes the following steps:

[0091] In step S11, slice requirement information corresponding to the first network slice layer is received;

[0092] In one embodiment of the present disclosure, the application scheme of the present disclosure can be, for example, a network slicing scenario applied to a low-orbit satellite network. The low-orbit satellite network can be a satellite network. The main difference between a satellite network and a traditional terrestrial network can be, for example, the dynamic and time-varying inter-satellite links.

[0093] According to some embodiments, the execution subject of the embodiments of the present disclosure may be, for example, a network-side device. The first network slice layer does not specifically refer to a fixed network slice layer. The first in the first network slice layer is only used to distinguish it from the remaining network slice layers. The first network slice layer may be, for example, any one of a physical layer, a link layer, or a network layer. Different first network slice layers may receive different slice requirement information.

[0094] In some embodiments, the slice requirement information is used to indicate resource information for performing network slicing on resources corresponding to the first network slice layer, that is, the slice requirement information of the slice demander for the slice, that is, the resource requirement information proposed by the slice demander for the first network slice layer. The slice requirement information does not specifically refer to a fixed information. For example, when the first network slice layer changes, the slice requirement information may also change accordingly. For example, when the sending object corresponding to the slice requirement information changes, the slice requirement information may also change accordingly.

[0095] For example, when a network side device executes a network slicing method, it can receive slicing requirement information corresponding to the first network slicing layer.

[0096] In step S12, network slicing is performed on the resources corresponding to the first network slicing layer according to the slicing requirement information, and a network slicing result corresponding to the first network slicing layer is obtained;

[0097] According to some embodiments, the network slicing result may be, for example, the result obtained after network slicing the resources of the first network slicing layer. The network slicing result does not specifically refer to a fixed result. For example, when the slicing requirement information changes, the network slicing result may also change accordingly. For example, when the first network slicing layer changes, the network slicing result may also change accordingly.

[0098] In some embodiments, network slicing is performed on resources corresponding to the first network slicing layer according to slicing requirement information to obtain network slicing results corresponding to the first network slicing layer.

[0099] In step S13, according to the network slicing result corresponding to the first network slicing layer, network slicing is performed on the resources corresponding to the second network slicing layer to obtain the network slicing result corresponding to the second network slicing layer.

[0100] In some embodiments, the second network slicing layer may be, for example, a different network slicing layer than the first network slicing layer. The network slicing result may be used, for example, to optimize slicing decisions. Different first network slicing layers may correspond to different second network slicing layers. The second network layer may be, for example, a network slicing layer adjacent to the first network slicing layer.

[0101] According to some embodiments, when the network slicing result corresponding to the first network slicing layer is obtained, network slicing can be performed on the resources corresponding to the second network slicing layer based on the network slicing result corresponding to the first network slicing layer to obtain the network slicing result corresponding to the second network slicing layer.

[0102] In some or related embodiments, slicing requirement information corresponding to a first network slicing layer is received, wherein the slicing requirement information is used to indicate resource information for performing network slicing on resources corresponding to the first network slicing layer; network slicing is performed on the resources corresponding to the first network slicing layer according to the slicing requirement information, and a network slicing result corresponding to the first network slicing layer is obtained; and network slicing is performed on the resources corresponding to the second network slicing layer according to the network slicing result corresponding to the first network slicing layer, and a network slicing result corresponding to the second network slicing layer is obtained. Therefore, a multi-layer collaborative network slicing mechanism can be provided to reduce the situation where only network resources are divided, resulting in inaccurate network slicing. This can improve the coordination and comprehensiveness of slicing solutions at each layer, improve the adaptability of network slicing, improve the accuracy of network slicing, achieve management efficiency of satellite networks, and improve service quality.

[0103] FIG2 is a flowchart of a network slicing method according to an exemplary embodiment. As shown in FIG2 , the network slicing method can be used in a communication scenario and includes the following steps:

[0104] In step S21, slice requirement information corresponding to the first network slice layer is received;

[0105] The specific process is as described above and will not be repeated here.

[0106] According to some embodiments, receiving slice requirement information corresponding to the first network slice layer includes at least one of the following:

[0107] Receive slice management information sent by the slice management layer, where the slice management information includes slice requirement information corresponding to the first network slice layer;

[0108] Receive resource request information sent by the second network slicing layer, where the resource request information includes slice requirement information corresponding to the first network slicing layer;

[0109] Receive service requirement information sent by the application layer, wherein the service requirement information includes slice requirement information corresponding to the first network slicing layer. Therefore, the slice requirement information can be received in different ways and matched with the network slice, thereby improving the accuracy of receiving the slice requirement information and improving the accuracy of the network slice.

[0110] Among them, the slicing requirement information is used to indicate the resource information for network slicing the resources of the first network slicing layer.

[0111] According to some embodiments, receiving slice requirement information may, for example, include receiving slice management information sent by the slice management layer, wherein the slice management information includes slice requirement information corresponding to the first network slice layer, and the slice requirement information is used to indicate resource information for performing network slicing on resources of the first network slice layer.

[0112] According to some embodiments, receiving slice requirement information corresponding to the first network slice layer may, for example, include receiving resource request information sent by the second network slice layer, wherein the resource request information includes slice requirement information corresponding to the first network slice layer.

[0113] According to some embodiments, receiving slice requirement information corresponding to the first network slice layer may, for example, include receiving service requirement information sent by the application layer, wherein the service requirement information includes slice requirement information corresponding to the first network slice layer.

[0114] In step S22, network slicing is performed on the resources corresponding to the first network slicing layer according to the slicing requirement information, and a network slicing result corresponding to the first network slicing layer is obtained;

[0115] The specific process is as described above and will not be repeated here.

[0116] According to some embodiments, performing network slicing on resources corresponding to the first network slicing layer according to the slicing requirement information, and obtaining a network slicing result corresponding to the first network slicing layer includes:

[0117] Based on the first service requirement, network slicing is performed on the hardware resources corresponding to the physical layer to obtain the physical layer network slicing results. This can provide a physical layer network slicing mechanism, clarify the physical layer network slicing method, improve the accuracy of network slicing, and improve service quality while reducing interference between services, thereby improving service quality.

[0118] In some embodiments, the name of the hardware resource is not limited. For example, the hardware resource can be referred to as a physical resource. Hardware resources include, but are not limited to, processors, memory, storage, and intersatellite link communication resources. Specifically, in the context of an intersatellite laser link, a physical layer slice can be the management and allocation of laser link communication resources. Laser link communication resources include, but are not limited to, wavelength, power, and optical link time slots.

[0119] In some embodiments, the first physical slicing layer may be, for example, a physical layer, and network slicing is performed on resources corresponding to the first network slicing layer according to the slicing requirement information. Obtaining the network slicing result corresponding to the first network slicing layer may include, for example:

[0120] Divide the link time slots according to the slice demand information corresponding to the first network slice layer to obtain a time slot set, where one network slice corresponds to one time slot;

[0121] According to the network slice demand information corresponding to any network slice, the time slot corresponding to any network slice is determined in the time slot set.

[0122] According to some embodiments, a time slot set refers to a collection of at least one time slot obtained by dividing a link time slot. This time slot set does not specifically refer to a fixed set. For example, when the available time resources of a link change, the time slot set may also change accordingly. For example, when the primary service requirements of the application layer change, the time slot set may also change accordingly. One network slice corresponds to one time slot, that is, one time slot is allocated to one network slice so that the network slice transmits data within the specified time slot.

[0123] In some embodiments, after the time slots are divided into time slot sets, the time slots in the time slot sets can be allocated to different network slices. The time slots can be allocated to each network slice based on network slice requirement information of each network slice. The network slice requirement information includes, but is not limited to, service requirements, priorities, network policies and constraints, etc., wherein the service requirements include, but are not limited to, data rate, latency, reliability, etc.

[0124] According to some embodiments, the method may further include, for example: scheduling the time slots of any network slice to control any network slice to complete data transmission within the allocated time slots. For example, when the slice demand information of any network slice changes, the time slots of any network slice may also change accordingly. For example, when the link of any network slice changes, the time slots of any network slice may also change accordingly. For example, when the service demand of any network slice changes, the time slots of any network slice may also change accordingly. Therefore, since the network is dynamic and uncertain, the technical solution disclosed in the present invention can dynamically adjust the allocation and scheduling of time slots according to changes in the network, and can improve the service quality of any network slice.

[0125] In some embodiments, the method may further include optimizing the time slots of any network slice to improve link resource utilization and service performance. During time slot optimization, for example, a prediction and optimization algorithm may be employed. For example, the service demand and link status of any network slice may be predicted, and the planning, allocation, and scheduling of time slots may be dynamically adjusted to improve data transmission efficiency and service performance for any network slice.

[0126] In some embodiments, when the first network slice layer is a physical layer, the second network slice layer may be, for example, a link layer. When the first network slice layer is a physical layer, receiving the slice requirement information corresponding to the first network slice layer may include, for example, at least one of the following:

[0127] Receive slice management information sent by the slice management layer, where the slice management information includes slice requirement information corresponding to the physical layer;

[0128] Receive resource request information sent by the link layer, where the resource request information includes slice requirement information corresponding to the physical layer;

[0129] Receive service requirement information sent by the application layer, where the service requirement information includes the slice requirement information corresponding to the physical layer. Therefore, the slice requirement information can be received in different ways and matched with the network slice, improving the accuracy of the slice requirement information reception and the accuracy of the network slice.

[0130] According to some embodiments, the first network slicing layer is a link layer, performing network slicing on resources corresponding to the first network slicing layer according to slicing requirement information, and obtaining a network slicing result corresponding to the first network slicing layer includes:

[0131] Based on the physical layer network slicing results and / or the second service requirements, network slicing is performed on the corresponding link layer resources to obtain the link layer network slicing results. This provides a link layer network slicing mechanism, clarifies the link layer network slicing method, enables dynamic monitoring and management of link resources, and improves the adaptability of resource prediction, estimation, and allocation.

[0132] According to some embodiments, link layer resources include but are not limited to link status, link capacity, data packets, and error control strategies. Partitioning link layer resources includes but is not limited to allocation of link capacity, scheduling of data packets, and error control.

[0133] Predict the link capacity of any network slice and obtain the link capacity of any network slice;

[0134] Allocate link capacity from the transmission capacity of the link to any network slice;

[0135] According to the scheduling information of any network slice, the data packet scheduling information of any network slice is determined.

[0136] In some embodiments, each starlight link can be determined to have a specific transmission capacity based on the physical characteristics and link status of the starlight link. Physical characteristics include, but are not limited to, laser power, wavelength, and optical system performance. Link status can include, for example, link distance.

[0137] Among them, the technical solution of the embodiment of the present disclosure can, for example, also predict the link capacity of any network slice at preset time intervals, and can also include predicting the link capacity of any network slice based on the service requirements of any network slice.

[0138] In one embodiment of the present disclosure, the scheduling information may be, for example, information used to determine data packets for any network slice. The scheduling information includes, but is not limited to, priority, fairness, and scheduling policy. For example, the data packet scheduling information may be determined based on a scheduling algorithm corresponding to the scheduling information. For example, the transmission order corresponding to any network slice may be determined based on the scheduling information, and the data packet scheduling information for any network slice may be determined based on this information.

[0139] According to some embodiments, the data packet scheduling information is used to indicate information for scheduling data packets, and is used to indicate data packets of any network slice.

[0140] According to some embodiments, dividing link layer resources and obtaining link layer slicing results further includes at least one of the following:

[0141] When it is determined that data transmission of any network slice fails, obtaining an error control strategy corresponding to any network slice, and obtaining an error correction code corresponding to the error control strategy;

[0142] When it is determined that data transmission of any network slice fails, the strength of the error correction code is adjusted according to the slice information and link status of any network slice.

[0143] According to some embodiments, data transmission errors may occur in intersatellite links due to various factors. These factors may include, for example, optical alignment errors. Each network slice may correspond to a different error control strategy, for example. Different error control strategies correspond to different error correction codes. For example, the strength of the error correction code may be dynamically adjusted based on service requirements and link status.

[0144] The link layer slicing results can also be used to partition resources at other layers to optimize slicing decisions. These other layers include, but are not limited to, the network layer and the application layer. Slicing link resources can improve their utilization efficiency, reduce waste due to irrational allocation, and meet dynamically changing service demands. Furthermore, link resource allocation can improve the accuracy of link slicing results and enhance the data transmission efficiency and reliability of any network slice.

[0145] In some embodiments, when the first network slice layer is a link layer, the second network slice layer may be, for example, a network layer. When the first network slice layer is a link layer, receiving the slice requirement information corresponding to the first network slice layer may include, for example, at least one of the following:

[0146] Receive slice management information sent by the slice management layer, where the slice management information includes slice requirement information corresponding to the link layer;

[0147] Receive resource request information sent by the network layer, where the resource request information includes slice requirement information corresponding to the link layer;

[0148] Receive service requirement information sent by the application layer, where the service requirement information includes slice requirement information corresponding to the link layer.

[0149] According to some embodiments, when the first network slicing layer is a link layer, when the second network slicing layer may be, for example, a network layer, performing network slicing according to slicing requirement information and obtaining a network slicing result include:

[0150] Receive status information sent by the third network slicing layer, where the status information includes a network slicing result corresponding to the third network slicing layer;

[0151] Perform network slicing on the resources corresponding to the link layer according to the slicing requirement information and / or status information to obtain the network slicing results.

[0152] According to some embodiments, wherein the first network slicing layer is a network layer, performing network slicing on resources corresponding to the first network slicing layer according to slicing requirement information, and obtaining a network slicing result corresponding to the first network slicing layer includes:

[0153] Based on the link layer network slicing results and / or the third service requirements, the network topology and routing information corresponding to the network layer are network sliced ​​to obtain the network layer network slicing results. Therefore, slicing requirement information can be received in different ways, matched with network slices, and the accuracy of slicing requirement information reception can be improved. The network topology and routing information can be managed and optimized, and the adaptability to changes in satellite motion and environmental factors can be improved, thereby improving the stability of the system.

[0154] According to some embodiments, network resources include, but are not limited to, network topology and communication environment. These resources can dynamically change with satellite movement and changes in the space environment. The communication environment includes, but is not limited to, routing information and traffic flow information. This allows adaptation to the dynamic and changing nature of satellite networks and the fulfillment of diverse service requirements. Furthermore, combining network layer slicing results with physical layer slicing and link layer slicing results can enhance the comprehensiveness of network resource management and service optimization.

[0155] According to some embodiments, performing network slicing on the network topology corresponding to the network layer and obtaining the network slicing result of the network layer includes:

[0156] Obtain the change information of the network topology of any network slice, and determine the communication path of any network slice based on the change information.

[0157] According to some embodiments, in low-orbit satellite networks, the dynamic movement of satellites can cause rapid changes in network topology. Therefore, communication paths can be determined based on network topology change information, meeting the service requirements of any network slice and improving the service quality of any network slice. Acquiring network topology change information can specifically include topology discovery and tracking, thereby reducing the acquisition time of the current network architecture, predicting network topology changes based on the current network architecture, improving the accuracy of change information acquisition, and improving the accuracy of communication path determination.

[0158] According to some embodiments, determining a communication path for any network slice includes:

[0159] According to the current network state and the predicted network state, determine the communication path that meets the requirements in the communication path set, and use the communication path that meets the requirements as the communication path of any network slice;

[0160] Based on the network slice requirements and current network status of any network slice, routing information is adjusted, and the communication path for any network slice is re-determined based on the adjusted routing information. Therefore, optimizing routing strategies can improve the matching of communication paths with service requirements and increase the accuracy of communication path determination. The dynamic topology and spatial variations of satellite networks can affect routing strategies, so optimizing routing strategies can improve their matching with current service requirements and network conditions, thereby improving service quality.

[0161] In some embodiments, using a communication path that meets the requirements as the communication path of any network slice may specifically include, for example, using the path with the highest path score among the communication paths as the communication path of any network slice. In the case where the path with the highest path score among the communication paths is not an idle path, using a communication path that meets the requirements as the communication path of any network slice may specifically include, for example, using the path with the second highest path score among the communication paths as the communication path of any network slice.

[0162] In some embodiments, adjusting routing information may include, for example, adjusting at least one of a priority of a route and a weight of a route.

[0163] According to some embodiments, the method further comprises:

[0164] Based on the service requirements and current network status of any network slice, the sending and receiving information of the data flow of any network slice is determined, and the sending rate and / or window size of the data flow are determined. Therefore, the traffic of any network slice can be controlled, the probability of network congestion can be reduced, the data transmission efficiency can be improved, and the service quality can be improved.

[0165] In some embodiments, when the first network slice layer is a network layer, the second network slice layer may be, for example, an application layer. When the first network slice layer is a network layer, receiving the slice requirement information corresponding to the first network slice layer may include, for example, at least one of the following:

[0166] Receive slice management information sent by the slice management layer, where the slice management information includes slice requirement information corresponding to the network layer;

[0167] Receive resource request information sent by the application layer, where the resource request information includes slice requirement information corresponding to the network layer;

[0168] Receive service requirement information sent by the application layer, where the service requirement information includes the slice requirement information corresponding to the network layer. Therefore, the slice requirement information can be received in different ways and matched with the network slice, thereby improving the accuracy of the slice requirement information reception and the accuracy of the network slice.

[0169] According to some embodiments, where the first network slicing layer is a network layer, the second network slicing layer may be, for example, an application layer, performing network slicing on resources corresponding to the first network slicing layer according to slicing requirement information, and obtaining a network slicing result corresponding to the first network slicing layer includes:

[0170] Receive status information sent by the third network slicing layer, where the status information includes a network slicing result corresponding to the third network slicing layer;

[0171] Perform network slicing on the network resources corresponding to the network layer according to the slicing requirement information and / or status information, and obtain the network slicing results corresponding to the network layer.

[0172] The network slicing result of the third network slicing layer may include, for example, slicing results of multiple network slicing layers. The network slicing result corresponding to the third network slicing layer may be, for example, hardware resource information, link status and link capacity, network topology and routing information, etc. Specifically, for example, it may be the allocation of resources or the remaining resources after resource allocation.

[0173] In step S23, according to the network slicing result corresponding to the first network slicing layer, network slicing is performed on the resources corresponding to the second network slicing layer to obtain the network slicing result corresponding to the second network slicing layer;

[0174] The specific process is as described above and will not be repeated here.

[0175] In some embodiments, when the first network slicing layer is a physical layer, the second network slicing layer may be, for example, a link layer. When the first network slicing layer is a physical layer, sending the physical layer network slicing result to the second network slicing layer may, for example, send the physical layer network slicing result to the link layer, and perform network slicing on resources corresponding to the link layer based on the physical layer network slicing result to obtain a link layer network slicing result.

[0176] In some embodiments, when the first network slicing layer is a link layer, the second network slicing layer may be, for example, a network layer. When the first network slicing layer is a link layer, sending the link layer network slicing result to the second network slicing layer may, for example, send the link layer network slicing result to the network layer, and perform network slicing on resources corresponding to the network layer based on the link layer network slicing result to obtain a network layer network slicing result.

[0177] In some embodiments, when the first network slicing layer is a network layer, the second network slicing layer may be, for example, an application layer. When the first network slicing layer is a network layer, sending the network layer network slicing result to the second network slicing layer may be, for example, sending the network layer network slicing result to the application layer.

[0178] According to some embodiments, the method further comprises:

[0179] Information exchange between the first network slice layer and the second network slice layer is carried out using information in the JavaScript Object Notation (JSON) format. Therefore, the inconvenience of information exchange between each layer of slices due to the diversity of information types or content can be reduced, and the convenience of information exchange can be improved.

[0180] According to some embodiments, FIG3 is a flowchart of a network slicing method according to an exemplary embodiment. As shown in FIG3 , for example, the following JSON format code can be used:

[0181] Among them, sourceLayer: the name or ID of the source slice layer, indicating the sender of any information.

[0182] targetLayer: The name or ID of the target slice layer, indicating the recipient of any information.

[0183] timestamp: The time when any information is sent, used to track and record the timing of any information.

[0184] messageType: The type of any message, for example, resource request, status update, warning message, etc. This type determines how any message is handled.

[0185] messageContent: The specific content of any message. This is a set of key-value pairs, where the key is the attribute name of the message and the value is the attribute value of the message. The specific keys and values ​​depend on the type and content of the message.

[0186] According to some embodiments, an inter-process communication (IPC) mechanism may be used between different slices of the same satellite node. The communication mechanism includes, but is not limited to, message queues, shared memory, pipes, sockets, etc. Different satellite nodes may communicate with the slice manager using a Hypertext Transfer Protocol (HTTP) or WebSocket network protocol.

[0187] According to some embodiments, the communication mechanism may be, for example, a message queue, wherein the messages and information of the embodiments of the present disclosure may be interchangeable. For example, when a message queue is used as an IPC mechanism for information exchange, it may be:

[0188] Define the information format: Use JSON format to encapsulate the information to be transmitted.

[0189] Create a message queue: Each slice layer creates a message queue to receive messages from other layers. The message queue can be named after the slice layer name or ID to facilitate finding and accessing by other layers.

[0190] Sending messages: When a slice layer needs to send information to other layers, it first encapsulates the information into JSON format and then sends the JSON string to the message queue of the target layer. This process can be completed through system calls or library functions.

[0191] Receiving messages: The slice layer receives messages from other layers by listening to the message queue corresponding to the slice layer. After receiving the message, it parses the information from JSON format back to the original format and then processes the message.

[0192] Parsing the message: After receiving the message, the target slice layer parses the message and understands the content of the message.

[0193] Processing messages: For each type of information, the slice layer needs to define a processing function or processing module to process the received information. The specific implementation of the processing function depends on the type of information and the function of the slice layer.

[0194] Send response: After the target slice layer processes the message, it sends a response to the source slice layer to confirm that the message has been received and processed.

[0195] Processing response: After the source slice layer receives the response from the target slice layer, it performs corresponding processing.

[0196] In step S24, the network slicing result is sent to the slice management layer.

[0197] According to some embodiments, when the network slicing result is obtained, the network slicing result can be sent to the slice management layer.

[0198] In some or related embodiments, the network slicing results can be sent to the slice management layer. Since the slice management layer is responsible for coordinating the resource allocation and management of slices at each layer, it can handle dependencies and conflicts between slices, and respond to changes in service requirements and network conditions to perform dynamic and adaptive resource allocation and management, thereby improving the comprehensiveness and adaptability of network slicing.

[0199] FIG4 is a flowchart of a network slicing method according to an exemplary embodiment. As shown in FIG4 , the network slicing method can be used in a communication scenario and includes the following steps:

[0200] In step S31, based on the slice requirement information received by the first network slice layer, it is determined to request resource information from the second network slice layer;

[0201] According to some embodiments, the execution subject of the embodiments of the present disclosure may be, for example, a network-side device. The first network slice layer does not specifically refer to a fixed network slice layer. The first in the first network slice layer is only used to distinguish it from the remaining network slice layers. The first network slice layer may be, for example, any one of an application layer, a link layer, or a network layer.

[0202] In some embodiments, when the first network slicing layer executes the network slicing method, it can determine to request resource information from the second network slicing layer based on the slicing requirement information received by the first network slicing layer.

[0203] For example, the method also includes: the network layer device can, for example, determine whether to request resource information from the second network slice layer.

[0204] According to some embodiments, the method further comprises at least one of the following:

[0205] Receive slice management information sent by the slice management layer, where the slice management information includes slice requirement information;

[0206] Receive resource request information sent by the third network slicing layer, where the resource request information includes slicing requirement information;

[0207] Receive service requirement information sent by the application layer, where the service requirement information includes slice requirement information.

[0208] According to some embodiments, for example, slice management information sent by a slice management layer may be received, wherein the slice management information includes slice requirement information, and resource information is requested from the second network slice layer based on the received slice management information.

[0209] According to some embodiments, for example, resource request information sent by the third network slicing layer may be received, wherein the resource request information includes slicing requirement information; and resource information is requested from the second network slicing layer based on the received resource request information.

[0210] According to some embodiments, for example, service requirement information sent by an application layer may be received, wherein the service requirement information includes slice requirement information. Determining to request resource information from the second network slice layer based on the received service requirement information.

[0211] According to some embodiments, the slice management information may also include resource status information, wherein the resource status information is used to indicate the resource status of the second network slice layer or the resource status information is used to indicate the status of the first network slice layer requesting resources from the second network slice layer.

[0212] According to some embodiments, the slice management information may also include resource status information, wherein the resource status information is used to indicate the resource status of the second network slice layer.

[0213] According to some embodiments, the slice management information may also include resource status information, wherein the resource status information is used to indicate the status of the first network slice layer requesting resources from the second network slice layer.

[0214] In step S32, the slicing requirement information is sent to the second network slicing layer;

[0215] According to some embodiments, for example, when determining to request resource information from the second network slice layer, it can be determined to request resource information from the second network slice layer; and send slice requirement information to the second network slice layer.

[0216] In step S33, the network slicing result corresponding to the resource information sent by the second network slicing layer in response to the slicing requirement information is received.

[0217] According to some embodiments, after sending the slicing requirement information to the second network slicing layer, for example, a network slicing result corresponding to the resource information sent by the second network slicing layer for the slicing requirement information can be received.

[0218] In some embodiments, after sending the slicing requirement information corresponding to the resource information to the second network slicing layer, for example, network slicing can be performed on the resources corresponding to the second network slicing layer according to the slicing requirement information, and the network slicing result can be obtained and sent to the first network slicing layer.

[0219] According to some embodiments, the first network slicing layer may be, for example, an application layer, and the second network application may be, for example, a network layer. For example, the application layer may determine to request resource information from the second network slicing layer, send slicing requirement information to the network layer, and receive a network slicing result sent by the network layer in response to the slicing requirement information. Therefore, the network slicing result may be optimized using the information obtained by the application layer, thereby improving service quality, service availability, and reducing service latency.

[0220] Figure 5 is a flowchart illustrating a network slicing method according to an exemplary embodiment. As shown in Figure 5, for example, hardware resources can be partitioned to obtain physical layer slicing results. The partitioned hardware resources can, for example, provide basic resources and performance guarantees for other layers. The physical layer network slicing results are used by the link layer, network layer, and application layer to optimize slicing decisions. Therefore, slicing can be performed at the physical, link, network, and application layers, achieving adaptive resource prediction, estimation, and allocation based on the dynamic and changing nature of satellite networks. This further enhances the system's adaptability to changing environments and improves the comprehensiveness of network slicing.

[0221] Link layer network slicing, for example, can rely on the hardware resources provided by the physical layer to allocate and manage link resources and obtain link layer slicing results. Link layer network slicing results, such as link status and link capacity, will be used by the network layer and application layer to optimize network management and service quality. Among them, link resource allocation and management may include, for example, allocation and management of link resources such as bandwidth and time slots.

[0222] For example, network layer network slicing can rely on the link resources provided by the link layer, and perform dynamic and adaptive network management and routing optimization to obtain network layer slicing results based on service requirements and network conditions. Network layer network slicing results such as network topology and routing information will be used by the application layer to optimize service resource allocation and management.

[0223] Application layer network slices rely on the network resources provided by network layer slices and perform dynamic and adaptive service management and optimization based on service requirements and user behavior. Application layer network slices not only rely on information from slices at other layers, but also the service requirements and user behavior information of the application layer will be fed back to the network layer, link layer, and physical layer to optimize the allocation and management of network, link, and physical resources. The transmission of service requirements can be, for example, from top to bottom. For example, when the application layer receives service requirements, they can be gradually transmitted to the lower layers. For example, when network slicing is implemented at each layer, it can be optimized based on the status information of the lower layer. The status information of the lower layer can be collected by the slice manager or received from the lower layer.

[0224] The slice management layer coordinates resource allocation and management across slice layers, handles dependencies and conflicts between slices, and responds to changes in service requirements and network conditions. For example, the slice manager collects and processes information about slices at each layer, such as resource usage, service requirements, and performance metrics. Based on this information, it performs dynamic and adaptive resource allocation and management.

[0225] In some or related embodiments, it is possible to determine, based on the slice requirement information received by the first network slicing layer, to request resource information from the second network slicing layer; send the slice requirement information to the second network slicing layer; and receive a network slicing result corresponding to the resource information sent by the second network slicing layer in response to the slice requirement information. Therefore, it can be determined that when resource information is requested from the second network slicing layer, the network slicing result is obtained, which can improve the matching between the network slicing result and the slice requirement information. In the case of multi-layer collaborative slicing, the adaptability of the system to changes and components is improved, thereby improving the quality of service.

[0226] FIG6 is a block diagram of a network slicing device according to an exemplary embodiment. Referring to FIG6 , the device 600 includes:

[0227] The first transceiver unit 601 is configured to receive slice requirement information corresponding to a first network slice layer, where the slice requirement information is used to indicate resource information for performing network slicing on resources corresponding to the first network slice layer;

[0228] The first processing unit 602 is configured to perform network slicing on resources corresponding to the first network slicing layer according to the slicing requirement information, and obtain a network slicing result corresponding to the first network slicing layer;

[0229] The first processing unit 602 is used to perform network slicing on the resources corresponding to the second network slicing layer according to the network slicing results corresponding to the first network slicing layer, and obtain the network slicing results corresponding to the second network slicing layer.

[0230] According to some embodiments, the first transceiver unit 601 is configured to receive slice requirement information corresponding to the first network slice layer, specifically for at least one of the following:

[0231] Receive slice management information sent by the slice management layer, where the slice management information includes slice requirement information corresponding to the first network slice layer;

[0232] Receive resource request information sent by the second network slicing layer, where the resource request information includes slice requirement information corresponding to the first network slicing layer;

[0233] Receive service requirement information sent by the application layer, wherein the service requirement information includes slice requirement information corresponding to the first network slice layer.

[0234] According to some embodiments, the first network slicing layer is a physical layer, and the first processing unit 602 is used to perform network slicing on resources corresponding to the first network slicing layer according to the slicing requirement information, and obtain the network slicing result corresponding to the first network slicing layer, specifically for:

[0235] According to the first service requirement, network slicing is performed on the hardware resources corresponding to the physical layer to obtain the physical layer network slicing results.

[0236] According to some embodiments, the first network slicing layer is a link layer, and the first processing unit 602 is used to perform network slicing on resources corresponding to the first network slicing layer according to the slicing requirement information, and obtain the network slicing result corresponding to the first network slicing layer, specifically for:

[0237] According to the physical layer network slicing results and / or the second service requirements, network slicing is performed on the link resources corresponding to the link layer to obtain the link layer network slicing results.

[0238] According to some embodiments, the first network slicing layer is a network layer, and the first processing unit 602 is used to perform network slicing on resources corresponding to the first network slicing layer according to the slicing requirement information, and obtain the network slicing result corresponding to the first network slicing layer, specifically for:

[0239] According to the link layer network slicing results and / or the third service requirements, network slicing is performed on the network topology and routing information corresponding to the network layer to obtain the network layer network slicing results.

[0240] According to some embodiments, the first processing unit 602 is configured to perform network slicing on resources corresponding to the first network slicing layer according to the slicing requirement information, and obtain the network slicing result corresponding to the first network slicing layer, specifically for:

[0241] Receive status information sent by the third network slicing layer, where the status information includes a network slicing result corresponding to the third network slicing layer;

[0242] Perform network slicing on the resources corresponding to the first network slicing layer according to the slicing requirement information and / or status information, and obtain the network slicing results corresponding to the first network slicing layer.

[0243] According to some embodiments, the first transceiver unit 601 is further configured to:

[0244] Information in JSON format is used for information exchange between the first network slicing layer and the second network slicing layer.

[0245] According to some embodiments, the first transceiver unit 601 is further configured to:

[0246] Send network slicing results to the slice management layer.

[0247] Regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0248] In some or related embodiments, a first transceiver unit is used to receive slicing requirement information corresponding to a first network slicing layer, wherein the slicing requirement information is used to indicate resource information for performing network slicing on resources corresponding to the first network slicing layer; a first processing unit is used to perform network slicing on the resources corresponding to the first network slicing layer according to the slicing requirement information, and obtain a network slicing result corresponding to the first network slicing layer; and the first transceiver unit is used to send the network slicing result to a second network slicing layer. Therefore, a multi-layer collaborative network slicing mechanism can be provided, reducing the situation where only network resources are divided, resulting in inaccurate network slicing. This can improve the coordination and comprehensiveness of slicing solutions at each layer, improve the adaptability of network slicing, improve the accuracy of network slicing, achieve satellite network management efficiency, and improve service quality.

[0249] FIG7 is a block diagram of a network slicing device according to an exemplary embodiment. Referring to FIG7 , the device 700 includes:

[0250] The second processing unit 701 is configured to determine, based on the slice requirement information received by the first network slice layer, whether to request resource information from the second network slice layer;

[0251] The second transceiver unit 702 is used to send slice requirement information to the second network slice layer;

[0252] The second transceiver unit 702 is used to receive the network slicing result corresponding to the resource information sent by the second network slicing layer in response to the slicing requirement information.

[0253] According to some embodiments, the second processing unit 701 is further configured to:

[0254] Receive slice management information sent by the slice management layer, where the slice management information includes slice requirement information;

[0255] Receive resource request information sent by the third network slicing layer, where the resource request information includes slicing requirement information;

[0256] Receive service requirement information sent by the application layer, where the service requirement information includes slice requirement information.

[0257] According to some embodiments, the slice management information also includes resource status information, wherein the resource status information is used to indicate the resource status of the second network slice layer or the resource status information is used to indicate the status of the first network slice layer requesting resources from the second network slice layer.

[0258] Regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0259] In some or related embodiments, the second processing unit is configured to determine, based on the slicing requirement information received by the first network slicing layer, whether to request resource information from the second network slicing layer; the second transceiver unit is configured to send the slicing requirement information to the second network slicing layer; and the second transceiver unit is configured to receive a network slicing result corresponding to the resource information sent by the second network slicing layer in response to the slicing requirement information. Therefore, it can be determined that when requesting resource information from the second network slicing layer, the network slicing result is obtained, which can improve the matching between the network slicing result and the slicing requirement information. In the case of multi-layer collaborative slicing, the adaptability of the system to changes and replacements can be improved, thereby improving the quality of service.

[0260] FIG8 is a block diagram of a network-side device 800 provided in an embodiment of the present disclosure. For example, the network-side device 800 can be provided as a network-side device. Referring to FIG8 , the network-side device 800 includes a processing component 822, which further includes at least one processor, and a memory resource represented by a memory 832 for storing instructions that can be executed by the processing component 822, such as an application. The application stored in the memory 832 may include one or more modules, each of which corresponds to a set of instructions. In addition, the processing component 822 is configured to execute instructions to perform any of the aforementioned methods applied to the network-side device.

[0261] The network side device 800 may further include a power supply component 826 configured to perform power management of the network side device 800, a wired or wireless network interface 850 configured to connect the network side device 800 to a network, and an input / output (I / O) interface 858. The network side device 800 may operate based on an operating system stored in the memory 832, such as Windows Server™, Mac OS X™, Unix™, Linux™, Free BSD™, or the like.

[0262] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0263] The program code for implementing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that when the program code is executed by the processor or controller, the functions / operations specified in the flow chart and / or block diagram are implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0264] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, device or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0265] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0266] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), the Internet, and a blockchain network.

[0267] A computer system may include a client and a server. The client and server are generally remote from each other and typically interact via a communication network. This client-server relationship is established by computer programs running on the respective computers, establishing a client-server relationship. The server may be a cloud server, also known as a cloud computing server or cloud host, a host product within the cloud computing service ecosystem that addresses the management difficulties and limited scalability of traditional physical hosts and VPS services ("Virtual Private Servers" or simply "VPS"). The server may also be a server in a distributed system or a server integrated with blockchain.

[0268] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this disclosure can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved. This is not a limitation herein.

[0269] The above specific embodiments do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure shall be included within the scope of protection of this disclosure.

Claims

1. A network slicing method, characterized in that Applied to a network-side device, including: Receiving slice requirement information corresponding to a first network slice layer, where the slice requirement information is used to indicate resource information for performing network slicing on resources corresponding to the first network slice layer, and the slice requirement information includes at least one of the following: slice requirement information of the slice management layer for the first network slice layer, slice requirement information of a second network slice layer for the first network slice layer, and slice requirement information of the application layer for the first network slice layer; Performing network slicing on resources corresponding to the first network slice layer according to the slice requirement information, and obtaining a network slicing result corresponding to the first network slice layer; Performing network slicing on resources corresponding to the second network slice layer according to the network slicing result corresponding to the first network slice layer, and obtaining a network slicing result corresponding to the second network slice layer; where when the first network slice layer is the physical layer, the second network slice layer is the link layer, when the first network slice layer is the link layer, the second network slice layer is the network layer, and when the first network slice layer is the network layer, the second network slice layer is the application layer.

2. The method according to claim 1, wherein The receiving slice requirement information corresponding to the first network slice layer includes at least one of the following: Receiving slice management information sent by the slice management layer, where the slice management information includes the slice requirement information corresponding to the first network slice layer; Receiving resource request information sent by the second network slice layer, where the resource request information includes the slice requirement information corresponding to the first network slice layer; Receiving service requirement information sent by the application layer, where the service requirement information includes the slice requirement information corresponding to the first network slice layer.

3. The method according to claim 1 or 2, characterized in that, Where When the first network slice layer is the physical layer, the performing network slicing on resources corresponding to the first network slice layer according to the slice requirement information and obtaining a network slicing result corresponding to the first network slice layer includes: Performing network slicing on the hardware resources corresponding to the physical layer according to a first service requirement, and obtaining a physical layer network slicing result.

4. The method according to claim 1 or 2, characterized in that, Where When the first network slice layer is the link layer, the performing network slicing on resources corresponding to the first network slice layer according to the slice requirement information and obtaining a network slicing result corresponding to the first network slice layer includes: Performing network slicing on the link resources corresponding to the link layer according to the physical layer network slicing result and / or a second service requirement, and obtaining a link layer network slicing result.

5. The method according to claim 1 or 2, characterized in that, Where When the first network slice layer is the network layer, the performing network slicing on resources corresponding to the first network slice layer according to the slice requirement information and obtaining a network slicing result corresponding to the first network slice layer includes: Performing network slicing on the network topology and routing information corresponding to the network layer according to the link layer network slicing result and / or a third service requirement, and obtaining a network layer network slicing result.

6. The method according to claim 5, wherein The performing network slicing on resources corresponding to the first network slice layer according to the slice requirement information and obtaining a network slicing result corresponding to the first network slice layer includes: Receive the status information sent by the third network slice layer, where the status information includes the network slice result corresponding to the third network slice layer; Perform network slicing on the resources corresponding to the first network slice layer according to the slice requirement information and / or the status information, and obtain the network slice result corresponding to the first network slice layer.

7. The method according to claim 1, characterized in that, The method further includes: Use the information in JSON format for information interaction between the first network slice layer and the second network slice layer.

8. The method according to claim 1, characterized in that The method further includes: Send the network slice result to the slice management layer.

9. A network slicing method, characterized in that, Applied to network-side devices, including: According to the slice requirement information received by the first network slice layer, determine to request resource information from the second network slice layer, where the slice requirement information includes at least one of the following: the slice requirement information of the slice management layer for the first network slice layer, the slice requirement information of the third network slice layer for the first network slice layer, and the slice requirement information of the application layer for the first network slice layer; Send the slice requirement information to the second network slice layer; where when the first network slice layer is the link layer, the second network slice layer is the physical layer, when the first network slice layer is the network layer, the second network slice layer is the link layer, and when the first network slice layer is the application layer, the second network slice layer is the network layer; Receive the network slice result corresponding to the resource information sent by the second network slice layer in response to the slice requirement information.

10. The method according to claim 9, wherein The method further includes at least one of the following: Receive the slice management information sent by the slice management layer, where the slice management information includes the slice requirement information; Receive the resource request information sent by the third network slice layer, where the resource request information includes the slice requirement information; Receive the service requirement information sent by the application layer, where the service requirement information includes the slice requirement information.

11. The method according to claim 10, wherein The slice management information further includes resource status information, where the resource status information is used to indicate the resource status of the second network slice layer or the resource status information is used to indicate the status of the first network slice layer requesting resources from the second network slice layer.

12. A network slicing device, characterized in that, Includes: A first transceiver unit, configured to receive the slice requirement information corresponding to the first network slice layer, where the slice requirement information is used to indicate the resource information for performing network slicing on the resources corresponding to the first network slice layer, and the slice requirement information includes at least one of the following: the slice requirement information of the slice management layer for the first network slice layer, the slice requirement information of the second network slice layer for the first network slice layer, and the slice requirement information of the application layer for the first network slice layer; A first processing unit, configured to perform network slicing on the resources corresponding to the first network slice layer according to the slice requirement information, and obtain the network slice result corresponding to the first network slice layer; The first processing unit is configured to perform network slicing on the resources corresponding to the second network slice layer according to the network slice result corresponding to the first network slice layer, and obtain the network slice result corresponding to the second network slice layer. When the first network slice layer is the physical layer, the second network slice layer is the link layer; when the first network slice layer is the link layer, the second network slice layer is the network layer; when the first network slice layer is the network layer, the second network slice layer is the application layer.

13. A network slicing device, characterized in that, It includes: A second processing unit is configured to determine to request resource information from the second network slice layer according to the slice requirement information received by the first network slice layer. The slice requirement information includes at least one of the following: the slice requirement information of the slice management layer for the first network slice layer, the slice requirement information of the third network slice layer for the first network slice layer, and the slice requirement information of the application layer for the first network slice layer. A second transceiver unit is configured to send the slice requirement information to the second network slice layer. When the first network slice layer is the link layer, the second network slice layer is the physical layer; when the first network slice layer is the network layer, the second network slice layer is the link layer; when the first network slice layer is the application layer, the second network slice layer is the network layer. The second transceiver unit is configured to receive the network slice result corresponding to the resource information sent by the second network slice layer in response to the slice requirement information.

14. A network-side device, characterized in that, It includes: A processor; A memory for storing executable instructions of the processor; Wherein, the processor is configured to execute the instructions to implement the network slicing method according to any one of claims 1 to 8 or 9 to 11.

15. A storage medium, when the instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to execute the network slicing method according to any one of claims 1 to 8 or 9 to 11.

Images