An access backhaul channel resource sharing system

Abstract

The application provides an access backhaul channel resource sharing system. The system comprises a wireless backhaul module and a backhaul base station. The wireless backhaul module is used for determining a network slice identifier of a service data stream, determining demand side information to which the service data stream belongs, and filling the demand side information into the network slice identifier to obtain a target network slice identifier carrying the demand side information. The backhaul base station is used for acquiring and analyzing the target network slice identifier to determine a service slice demand and a service slice demand side, and executing a corresponding slice priority strategy based on the service slice demand, the service slice demand side and a current channel resource condition. The access backhaul channel resource sharing system disclosed by the application can take into account the interests of different demand sides while guaranteeing the realization of specific service demands of different demand sides, thereby improving the utilization efficiency of backhaul channel resources.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of wireless communication, and in particular to an access backhaul channel resource sharing system. BACKGROUND

[0002] At present, the access backhaul end-to-end architecture only has one access layer, and the access base station backhaul is usually based on wired transmission. The information obtained by the access base station is only some (or some) slice information of a certain access user terminal. If the access base station is deployed in a mobile scenario, such as a high-speed rail, a subway car, etc., the original access base station backhaul cannot be wired. In the public transport mobile scenario of subway, high-speed rail, etc., due to limited resources, the construction of communication services usually advocates the principle of joint construction and sharing. Even in the double-layer nested access backhaul architecture, due to the more scarce backhaul channel resources (such as spectrum resources, tunnel installation resources, etc.), the demand for backhaul channel sharing is more urgent. In addition to the original access base station of the operator, the subway operator also has its own operation and management control data to be backhauled (such as subway car monitoring data, subway car control data, etc.). Moreover, both the operator and the subway operator have different performance guarantee requirements for their businesses.

[0003] To solve the problem of wireless backhaul, the prior art proposes an IAB (Integrated Access and Backhaul) base station, but the current IAB base station is mainly an integrated architecture, and only has one core control network, which cannot perform mobility management of the backhaul network, is not suitable for mobile scenarios, and cannot perform slice control management of the backhaul network. Therefore, how to consider the interests of different demand parties in the fast mobile scenario, while ensuring the specific business guarantee requirements of different demand parties, and realizing backhaul channel sharing has become a research focus in the field. SUMMARY

[0004] Therefore, the present application provides an access backhaul channel resource sharing system to solve the problem of poor wireless backhaul scheme sharing efficiency and stability and high limitation in the prior art.

[0005] The present application provides an access backhaul channel resource sharing system, comprising: a wireless backhaul module and a backhaul base station.

[0006] The wireless backhaul module is configured to determine the network slice identifier of the service data flow, determine the demand party information to which the service data flow belongs, and fill the demand party information into the network slice identifier to obtain a target network slice identifier carrying the demand party information.

[0007] The backhaul base station is configured to acquire the target network slice identifier for analysis, determine service slice demand and service slice demand party, and perform a corresponding slice priority policy based on the service slice demand, the service slice demand party, and current channel resource conditions.

[0008] In one embodiment, the backhaul base station is specifically configured to perform a channel resource allocation policy based on the rights and interests of the service slice demand party.

[0009] The channel resource allocation policy based on the rights and interests of the service slice demand party includes:

[0010] According to the rights and interests factor of the service slice demand party, the channel resources corresponding to the service slice demand party are proportionally allocated according to a preset scheduling resource group type.

[0011] For the service slice demand party, the service slice demand is scheduled in the channel resources contained in the corresponding scheduling resource group based on network service quality and slice priority.

[0012] In one embodiment, the backhaul base station is specifically configured to perform a channel resource allocation policy based on the scheduling resource group type; the scheduling resource group type includes a private network guarantee scheduling resource group, a priority guarantee scheduling resource group, and a shared scheduling resource group.

[0013] The channel resource allocation policy based on the scheduling resource group type includes:

[0014] The channel resources are divided into a private network guarantee scheduling resource group, a priority guarantee scheduling resource group, and a shared scheduling resource group for allocation.

[0015] The channel resources in different scheduling resource groups are allocated according to the rights and interests of the demand party.

[0016] The channel resources in different scheduling resource groups are allocated according to the rights and interests of the demand party, specifically including:

[0017] If the service slice demand is a private network guarantee demand, the service slice demand party is given weighted priority scheduling in the private network guarantee scheduling resource group according to the rights and interests of the service slice demand party.

[0018] If the service slice demand is a priority guarantee resource demand, the service slice demand party is given weighted priority scheduling in the priority guarantee scheduling resource group according to the rights and interests of the service slice demand party.

[0019] If the service slice demand is a shared resource demand, the service slice demand party is given weighted priority scheduling in the shared guarantee scheduling resource group according to the rights and interests of the service slice demand party.

[0020] In one embodiment, the access backhaul channel resource sharing system further comprises a mobile router configured to convert an access base station address or an access service party address to a wireless backhaul module address, and route the service data flow to the wireless backhaul module based on a corresponding virtual local area network identifier.

[0021] In one embodiment, the access backhaul channel resource sharing system, the backhaul base station is further configured to obtain a slice priority policy issued by a preset backhaul core network module, and execute the slice priority policy based on the service slice demand, the service slice demand party and a current channel resource condition.

[0022] In one embodiment, the wireless backhaul module is specifically configured to perform network slice identifier remapping on the service data flow based on the virtual local area network identifier in a preset mapping relationship between a network slice identifier and a virtual local area network identifier, to obtain a network slice identifier of the service data flow.

[0023] In one embodiment, the wireless backhaul module is specifically configured to determine demand party information to which the service data flow belongs based on an access base station address or an access service party address corresponding to the service data flow.

[0024] In one embodiment, the wireless backhaul module is further configured to obtain an access base station address or an access service party address, and convert the access base station address or the access service party address to a wireless backhaul module address.

[0025] In one embodiment, the wireless backhaul module is specifically configured to fill demand party information through a reserved identifier bit of the network slice identifier and a self-positioning supplement.

[0026] In one embodiment, the service data flow is service demand data initiated by a user end in a mobile space to access a corresponding operator network.

[0027] The access backhaul channel resource sharing system provided by the application determines a network slice identifier of a service data flow through a wireless backhaul module, determines demand party information to which the service data flow belongs, and fills the demand party information into the network slice identifier; a backhaul base station is configured to obtain the target network slice identifier to perform analysis, determine a service slice demand and a service slice demand party, and execute a corresponding slice priority policy based on the service slice demand, the service slice demand party and a current channel resource condition; the application can realize the protection of specific service demands of different demand parties while taking into account the interests of different demand parties, and improves the utilization efficiency and reliability of backhaul channel resources. BRIEF DESCRIPTION OF DRAWINGS

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings described below are only some embodiments of the present application, and the drawings can also be obtained by those skilled in the art without creative effort.

[0029] Figure 1 The structure schematic diagram of the access backhaul channel resource sharing system provided by the embodiment of the present application is shown in the figure.

[0030] Figure 2 The complete structure schematic diagram of the full-duplex cooperative relay system in the access backhaul channel resource sharing system provided by the embodiment of the present application is shown in the figure.

[0031] Figure 3 The schematic diagram of the slice priority scheduling strategy in the access backhaul channel resource sharing system provided by the embodiment of the present application is shown in the figure. DETAILED DESCRIPTION

[0032] In order to make the purpose, technical solutions and advantages of the embodiments of the present application more clear, the following will combine the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative effort are within the protection scope of the present application.

[0033] The present application is based on the original access backhaul system, and by re-embedding a set of access backhaul end-to-end system as the backhaul of the previous original access backhaul system, a kind of access backhaul channel resource sharing system is provided, which includes but is not limited to being applied to mobile space to realize data backhaul channel resource sharing.

[0034] The following will describe the embodiments of the access backhaul channel resource sharing system described in the present application in detail. As shown in the figure, it is the structure schematic diagram of the access backhaul channel resource sharing system provided by the embodiment of the present application, and the implementation process at least includes the following parts: wireless backhaul module and backhaul base station. Figure 1

[0035] The wireless backhaul module 101 is used to determine the network slice identifier of service data stream, and determine the demander information to which the service data stream belongs;And the demander information is filled into the network slice identifier, to obtain the target network slice identifier carrying demander information.

[0036] ​The wireless backhaul module refers to a backhaul CPE (Custom Premise Equipment) preset in a mobile space. The service data is service demand data initiated by a user terminal in the mobile space to access a corresponding operator network. The wireless backhaul module obtains a service data stream by directly connecting with an original access base station, identifies a network slice identifier of the service data stream, and determines demand side information to which the service data stream belongs according to an original access base station address or an access service side address. The original access base station is a building base band unite (BBU). The mobile space can refer to a closed carriage with fast mobility such as a subway or a high-speed rail.

[0037] In the implementation process, the user terminal of different operators accesses a corresponding operator network, initiates service demand, and carries a corresponding network slice identifier (Single Network Slice Selection Assistance Information, S-NSSAI). The network slice identifier is the link of an end-to-end network slice. Through the network slice identifier, the network slice (service slice) can be associated end to end from the user terminal, the original access base station, the backhaul transmission network, the backhaul core network module, and the like, to form a full process of a signaling plane and a management plane. The network slice identifier is used to identify a specific network slice and does not repeat in a PLMN. The original access base station is used to identify the network slice identifier corresponding to the service flow data, and map the network slice identifier to a virtual local area network identifier (VLAN identifier) and a corresponding port.

[0038] In the embodiment of the application, the original access base station can be directly connected with the wireless backhaul module, or can be connected through a mobile router (since the mobile router is deployed in the carriage, it can also be referred to as a vehicle-mounted router). For example, if the original access base station and the wireless backhaul module are in a one-to-many or many-to-many relationship, a mobile router can be further provided. The mobile router is deployed in a mobile space and is used for splitting and converging. Specifically, the mobile router can be used to convert an access base station address or an access service side address to a wireless backhaul module address (CPE address), and route and forward the service data stream to the wireless backhaul module based on the virtual local area network identifier, that is, send to at least one wireless backhaul module by using a preset port. The wireless backhaul module is specifically used to obtain the service data stream sent by the mobile router through the corresponding port. The port can be a physical port or a logical port.

[0039] The wireless backhaul module is configured to perform network slice identification remapping on the service data flow based on the virtual local area network identification in the preset mapping relationship between network slice identification and virtual local area network identification, so as to determine the network slice identification of the service data flow; and determine the demander information to which the service data flow belongs based on the access base station address or the access service provider address corresponding to the service data flow.

[0040] In addition, the wireless backhaul module is further configured to fill the demander information into the network slice identification to obtain a target network slice identification carrying the demander information. Specifically, after the wireless backhaul module identifies the target network slice identification of the service flow and the demander to which the service flow belongs, the demander information (operator information or other service provider information) is supplemented and backfilled based on the obtained S-NSSAI, that is, the demander information is supplemented and backfilled through the reserved identification bits and self-defined bits of the network slice identification. For example, the operator or other service provider information is supplemented through the reserved identification bits. If there are not many demanders, for example, there are only three operators and a subway service provider, only 2 bits are needed for identification. The 5G SA slice ID currently has 32 bits. 8 bits are SST, and 24 bits are slice distinguishing symbols, which are a supplement to the slice type. Therefore, there are many self-defined bits or reserved identification bits that can be defined by the operator, and the information of the demander can be supplemented and backfilled through these self-defined bits or reserved identification bits.

[0041] It should be noted that the mobile router can not be used in actual implementation, and a corresponding address conversion unit can be arranged in the wireless backhaul module, which is specifically configured to obtain the access base station address or the access service provider address and convert the access base station address or the access service provider address to the wireless backhaul module address, so as to realize address conversion and perform subsequent operations of determining the network slice identification of the service data flow and the demander information to which the service data flow belongs.

[0042] The backhaul base station 102 is configured to obtain the target network slice identification and determine the service slice demand and the service slice demander by analyzing the target network slice identification, and perform a corresponding slice priority policy based on the service slice demand, the service slice demander and the current channel resource condition.

[0043] The slice priority policy can be preconfigured in the backhaul base station. After the target network slice identification uploaded by the wireless backhaul module is obtained and the service slice demand and the service slice demander are analyzed, the corresponding slice priority policy can be performed by the base station network management module based on the service slice demand, the service slice demander and the current channel resource condition, that is, the slice demand of the specific service is considered, and the fairness (or weighted interest) of different demanders is also considered.

[0044] In addition, the backhaul base station is further configured to acquire a slice priority policy issued by a preset backhaul core network module, and execute the slice priority policy by a base station network management module based on the service slice demand, the service slice demand party and current channel resource conditions. The target receiving network can be an operator access core network or an industry private network, etc. The backhaul core network module includes an access and mobility management function (AMF), a data network element (The User plane function, UPF) and a backhaul network management server, etc. The backhaul core network module is specifically configured to implement slice request registration in an initial process, identify slice services by NSSAI, and support VLAN identification and corresponding port information configuration based on different NSSAI.

[0045] The slice priority policy includes but is not limited to the following two schemes: scheme one is a channel resource allocation strategy based on the rights and interests of the service slice demand party; and scheme two is a channel resource allocation strategy based on a scheduling resource group type. First, it is assumed that there are three demand parties A, B and C, and the rights and interests factors corresponding to the three demand parties are X, Y and Z respectively, wherein X+Y+Z=1.

[0046] In the implementation process of the scheme one of the present application, the backhaul base station is specifically configured to execute the channel resource allocation strategy based on the rights and interests of the service slice demand party.

[0047] The channel resource allocation strategy based on the rights and interests of the service slice demand party includes:

[0048] According to the rights and interests factor of the service slice demand party, the channel resources corresponding to the service slice demand party are proportionally allocated according to a preset scheduling resource group type.

[0049] For the service slice demand party, the service slice demand is scheduled in the channel resources contained in the corresponding scheduling resource group based on network service quality and slice priority.

[0050] Specifically, as Figure 3The hard pipeline resource is allocated and distributed according to the equity factor corresponding to the business slice demand side first; the hard pipeline resources of each business slice demand side are allocated and distributed in scheduling groups, such as a private network guarantee resource group (dedicated reserved resources), a priority guarantee resource group (priority guarantee resources, which can be scheduled by other businesses when there is remaining resource), and a shared resource group (fairly competitive resources), and the proportion parameters of each scheduling resource group are α, β, and δ, wherein α+β+δ=1. In the specific implementation process, the proportion parameters of the internal scheduling group resources of each business slice demand side can be different, and can be adjusted according to actual needs; each business slice demand side schedules in the respective hard pipeline resources according to the network quality of service (QOS) and the slice priority, needs to reserve dedicated guarantee resources in the private network guarantee resource group for scheduling, needs to schedule in the priority guarantee resource group, and the remaining resources can be scheduled in the shared resource group by other slice demands.

[0051] In the implementation process of the second aspect of the present application, the backhaul base station is specifically configured to execute a channel resource allocation strategy based on scheduling resource group types; the scheduling resource group types include a private network guarantee scheduling resource group, a priority guarantee scheduling resource group, and a shared scheduling resource group.

[0052] The channel resource allocation strategy based on the scheduling resource group types includes:

[0053] The channel resources are allocated by dividing them into the private network guarantee scheduling resource group, the priority guarantee scheduling resource group, and the shared scheduling resource group.

[0054] The channel resources in different scheduling resource groups are allocated according to the rights and interests of demand sides.

[0055] The channel resources in different scheduling resource groups are allocated according to the rights and interests of demand sides, specifically including:

[0056] If the business slice demand is a private network guarantee demand, the business slice demand side is scheduled in the private network guarantee scheduling resource group according to the rights and interests of the business slice demand side.

[0057] If the business slice demand is a priority guarantee resource demand, the business slice demand side is scheduled in the priority guarantee scheduling resource group according to the rights and interests of the business slice demand side.

[0058] If the business slice demand is a shared resource demand, the business slice demand side is scheduled in the shared guarantee scheduling resource group according to the rights and interests of the business slice demand side.

[0059] Specifically, as Figure 3As shown. First, the channel resource area is divided into dedicated network guarantee scheduling resource group, priority guarantee scheduling resource group and shared scheduling resource group for allocation, such as dedicated guarantee resource group, priority guarantee resource group, shared resource group, and the proportion parameters of each scheduling resource group are a, b, d, where a+b+d=1. The proportion parameter is adjustable. Then, the resources of each scheduling resource group are allocated according to the business slice demand side interests: if the business slice demand is a dedicated network guarantee demand, each business slice demand side is allocated in the dedicated network guarantee resource group according to the corresponding interests (X, Y, Z, where: X+Y+Z=1) of the business slice demand side; for guarantee demand, if there is a surplus of resources of the business slice demand side, it can be shared with other demand sides; if the business slice demand is a priority guarantee resource demand, each business slice demand side can be weighted and prioritized in the priority guarantee resource group according to the demand side interests, such as the same priority originally, but after weighting according to the demand side interests, the priority will be differentiated; similarly, if the business slice demand is a shared resource demand, each business slice demand side can be weighted and scheduled in the shared resource group according to the demand side interests, such as originally based on QOS fair competition, but can be differentiated and scheduled after weighting according to the business slice demand side interests.

[0060] The following is described taking the mobile scenarios of subway tunnels and high-speed rails as examples. In a complete implementation, the overall system architecture is as shown in Figure 2 The system includes wireless backhaul module 101 and backhaul base station 102, backhaul core network module 103, original access core network 104, mobile router 105, original access base station 106, access user end 107 (UE), mobile space 108 (such as high-speed rail carriages or subway carriages), backhaul network management server 1031, access network management server 1041. Between the original access user end 107 (UE), the original access base station 106 (including baseband and radio frequency, etc.), the original access core network 104, a set of access backhaul end-to-end system, i.e. access backhaul channel resource sharing system, is further embedded, which at least includes: wireless backhaul module 101, backhaul base station 102 (including baseband and radio frequency, etc.). In addition, a corresponding mobile router 105 (shunting, converging, etc.) can also be set.

[0061] The radio frequency of the backhaul base station can be deployed along the subway track (which can be the tunnel wall or the external outdoor station installation form); the frequency band of the backhaul base station can be the same as or different from the frequency band of the original access base station. If the frequency bands of the backhaul base station and the original access base station are different, the interference is small, the backhaul frequency band is flexible, and the backhaul capacity is large; if the frequency bands of the backhaul base station and the original access base station are the same, the interference of the two frequency bands needs to be considered and solved, but the spectrum utilization can be improved. The original access base station, the wireless backhaul module, the mobile router and the like are generally deployed in the carriage.

[0062] In the implementation process, the radio frequency unit of the original access base station can be distributed and deployed in each carriage to improve the coverage effect. The antenna of the wireless backhaul module can be external or internal (for example, above the glass of the driver's cabin at the front and rear of the train, which has been tested to have small penetration loss), and the wireless backhaul module can also be used to reduce the inter-cell interference between the wireless backhaul modules deployed at the front and rear of the carriage by using the spatial isolation in the carriage, so as to achieve the effect of doubling the capacity of two cells in the case of the same frequency, thereby doubling the backhaul capacity of the whole carriage. The functions of the original access base station, the wireless backhaul module and the mobile router can be integrated into one device, or can be distributed and deployed.

[0063] In the above scenario, if multiple operators or subway demand parties need to share the transmission channel resources of the backhaul, and the users of each operator have different quality of service (or slice) requirements, how to consider the different slice requirements of the access user end and combine the interests of different operators and demand parties when sharing the backhaul is the key content to be solved by the present application.

[0064] The following is only one embodiment of the present application based on the subway scenario of multiple operators and the sharing of the backhaul of the subway demand party. The present application can also be applied to other access backhaul sharing systems and application scenarios, which are not limited here.

[0065] Specifically, an access backhaul channel resource sharing system is given below, which is as follows: different operator user ends UE access the corresponding operator network, initiate service requirements, carry the corresponding network slice identifier, and interact with the original access base station for service data flow. The original access base station identifies the network slice identifier of the service data flow, and maps different NSSAI to the corresponding VLAN identifier and corresponding port.

[0066] The original access base station and the wireless backhaul module can be directly connected or connected through a mobile router. If the original access base station and the wireless backhaul module are in a one-to-many or many-to-many relationship, a mobile router (also referred to as a vehicle-mounted router because it is deployed in a vehicle compartment) is inserted to mainly perform the functions of distribution and convergence. Specifically, the mobile router completes address conversion of the original access base station (or other access service provider addresses) and the wireless backhaul CPE, and performs routing forwarding based on VLAN identification. The original access base station address and the access service provider address correspond to different service data flow demanders, respectively, that is, the original access base station address and the access service provider address can be used to determine the demander information of the service data flow. In addition, to further enhance the security and isolation of the backhaul channel, the mobile router can also start a security tunnel function (such as an IP-SEC tunnel or a GRE tunnel) to encapsulate the service flow data of the original access base station through a tunnel protocol.

[0067] The original access base station is connected with the wireless backhaul module (which can be multiple wireless backhaul module devices) through a direct mobile router, each wireless backhaul module device has a WAN port address, which is allocated by a backhaul core network module (the backhaul core network module allocates a fixed address to an access user terminal UE) and transmitted to the mobile router by the wireless backhaul module, and the mobile router establishes a tunnel between the address and the remote router. Since the mobile router cannot identify network slice information, after the wireless backhaul module obtains the service data flow input by the original access base station (or through the mobile router), the wireless backhaul module can perform NSSAI reverse mapping according to the virtual local area network identification in the preset network slice identification mapping and virtual local area network identification mapping table, that is, the network slice identification is restored through twice mapping, and then different slice requirements of different operators (or other service providers) are obtained. The virtual local area network identification is a VLAN identification, which corresponds to an IP port. The IP port can be a physical port or a logical port.

[0068] The wireless backhaul module can identify the network slice identifier of the service data stream and the demand side to which the service data stream belongs, and can supplement the corresponding demand side information (such as operator or other business side information) based on the obtained S-NSSAI. Specifically, the operator or other business side information can be supplemented by reserving an identification bit or customizing a bit. If there are not many demand sides, for example, only three operators and a subway business side, only 2 bits are needed for identification. The 5G SA slice ID currently has 32 bits. 8 bits are SST, and 24 bits are slice distinguishing symbols, which are a supplement to the slice type. Therefore, the custom bit or the reserved identification bit can be determined by the operator, and the information of the demand side to which the service data stream belongs can be supplemented and filled back through the custom bit or the reserved identification bit. That is, the wireless backhaul module initiates a service request, and the requested NSSAI carries the supplemented demand side source to determine the NSSAI from different operators or other business sides.

[0069] The backhaul base station can obtain the NSSAI (i.e., the target network identifier) after the wireless backhaul module fills in the demand side information, and can analyze and obtain the different demand side sources of the service slice demand. In this way, the backhaul base station obtains both the specific service slice demand information and the demand side information to which the specific service slice belongs. After obtaining the above information, the backhaul base station can perform a slice priority strategy based on the obtained information (service slice demand information and service slice demand side information) and according to its own resource situation, so as to consider the specific service slice demand and take into account the fairness (or weighted interests) of different demand sides.

[0070] The access backhaul channel resource sharing system provided by the application can determine the network slice identifier of the service data stream and the demand side to which the service data stream belongs through the wireless backhaul module, fill the demand side information into the network slice identifier, and set the backhaul base station to obtain the target network slice identifier for analysis, determine the service slice demand and the service slice demand side, and execute a corresponding slice priority strategy based on the service slice demand, the service slice demand side, and the current channel resource situation. The application can take into account the interests of different demand sides while guaranteeing the specific service demand of different demand sides, and improves the utilization efficiency and reliability of backhaul channel resources in a mobile space scenario.

[0071] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the application, and not to limit them; although the application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can modify the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some technical features; and these modifications or substitutions do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the application.

Claims

1. A resource sharing system for accessing backhaul channels, characterized in that, include: Wireless backhaul module and backhaul base station; The wireless backhaul module is used to determine the network slice identifier of the service data stream and to determine the demand side information to which the service data stream belongs. The demand-side information is then filled into the network slice identifier to obtain a target network slice identifier carrying the demand-side information. The backhaul base station is used to obtain and parse the target network slice identifier to determine the service slice requirements and the service slice requester. Based on the business slice requirements, the business slice requesters, and the current channel resource status, the corresponding slice priority strategy is executed to achieve backhaul channel sharing in fast-moving scenarios.

2. The access backhaul channel resource sharing system according to claim 1, characterized in that, The backhaul base station is specifically used to execute a channel resource allocation strategy based on the rights and interests of the service slice demander; The channel resource allocation strategy based on the rights and interests of the business slice demander includes: Based on the rights and interests of the business slice demanders, the channel resources corresponding to the business slice demanders are allocated proportionally according to the preset scheduling resource group type. For the service slice requester, the service slice request is scheduled within the channel resources included in the corresponding scheduling resource group based on network service quality and slice priority.

3. The access backhaul channel resource sharing system according to claim 1, characterized in that, The backhaul base station is specifically used to execute a channel resource allocation strategy based on the scheduling resource group type; The types of scheduling resource groups include dedicated network guaranteed scheduling resource groups, priority guaranteed scheduling resource groups, and shared scheduling resource groups. The channel resource allocation strategy based on scheduling resource group type includes: Channel resources are allocated by classifying them into dedicated network guarantee scheduling resource group, priority guarantee scheduling resource group, and shared scheduling resource group; Channel resources within different scheduling resource groups are allocated according to the rights and interests of the demanders. Specifically, the channel resources within different scheduling resource groups are allocated according to the rights and interests of the demand side, including: If the service slice requirement is a private network guarantee requirement, then the service slice requester will be scheduled with weighted priority within the private network guarantee scheduling resource group according to the rights and interests of the service slice requester. If the business slice requirement is a priority resource requirement, then the business slice requester will be scheduled with weighted priority based on the rights and interests of the business slice requester within the priority scheduling resource group. If the service slice requirement is a shared resource requirement, then the service slice requester will be scheduled with weighted priority within the shared scheduling resource group according to the rights and interests of the service slice requester.

4. The access backhaul channel resource sharing system according to claim 1, characterized in that, Also includes: A mobile router is used to translate the address of the access base station or the address of the access service provider to the address of the wireless backhaul module, and to route the service data stream to the wireless backhaul module based on the corresponding virtual LAN identifier.

5. The access backhaul channel resource sharing system according to claim 1, characterized in that, The backhaul base station is also used to obtain the slice priority policy issued by the preset backhaul core network module, and execute the slice priority policy based on the service slice requirements, the service slice requester, and the current channel resource status.

6. The access backhaul channel resource sharing system according to claim 1, characterized in that, The wireless backhaul module is specifically used to perform network slice identifier inverse mapping on the service data stream based on the virtual local area network identifier in the preset mapping relationship between network slice identifier mapping and virtual local area network identifier mapping, so as to obtain the network slice identifier of the service data stream.

7. The access backhaul channel resource sharing system according to claim 1, characterized in that, The wireless backhaul module is specifically used to determine the demand party information to which the service data stream belongs based on the access base station address or access service provider address corresponding to the service data stream.

8. The access backhaul channel resource sharing system according to claim 1, characterized in that, The wireless backhaul module is also used to obtain the access base station address or the access service provider address, and convert the access base station address or the access service provider address to the wireless backhaul module address.

9. The access backhaul channel resource sharing system according to claim 1, characterized in that, The wireless backhaul module is specifically used to supplement and backfill the demand party information by using the reserved identifier bit of the network slice identifier and self-location.

10. The access backhaul channel resource sharing system according to claim 1, characterized in that, The service data stream refers to the service request data initiated by the user terminal accessing the corresponding operator's network within the mobile space.

Images