CN108347736B

CN108347736B - Resource sharing control method, execution entity and resource sharing configuration entity

Info

Publication number: CN108347736B
Application number: CN201710056513.8A
Authority: CN
Inventors: 张晨璐; 杨晓东
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2017-01-25
Filing date: 2017-01-25
Publication date: 2020-04-17
Anticipated expiration: 2037-01-25
Also published as: WO2018137499A1; CN108347736A

Abstract

The embodiment of the invention provides a resource sharing control method, an execution entity and a resource sharing configuration entity, wherein the method comprises the following steps: receiving resource sharing configuration information of the network slice, which is sent by a resource sharing configuration entity of the network slice; and controlling the resources used by the network slice according to the resource sharing configuration information of the network slice. The resource sharing control method, the execution entity and the resource sharing configuration entity provided by the embodiment of the invention can realize the resource sharing among the network slices.

Description

Resource sharing control method, execution entity and resource sharing configuration entity

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a resource sharing control method, an execution entity and a resource sharing configuration entity.

Background

Among the numerous fifth generation mobile phone mobile communication standard (5G) key technologies, network slicing (network) is one of the many technologies being discussed. The network slicing technology is a virtual network technology, and can provide characteristic network functions and performances for the vertical industry under the background of development of the 5G network marching vertical industry.

As is well known, different application scenarios have very different requirements in aspects of network function, system performance, security, user experience, and the like, and if the same network is used to provide services, the network is complex and heavy, and cannot meet the limit performance requirement required by the application, and at the same time, the operation and maintenance of the network become quite complex, and the cost of network operation is increased. On the contrary, if a dedicated network is deployed to provide services according to different requirements of different service scenarios, and the network only includes functions required by the application scenario, the efficiency of the services is greatly improved, the network performance required by the application scenario can be guaranteed, the operation and maintenance of the network become simple, and the investment and operation and maintenance costs can be reduced.

The network slicing technology logically divides an operator network into a plurality of network instances (network instances) by using a virtualization technology, and provides services with different requirements respectively. For example, in addition to the traditional voice service and data service of mobile communication, the new 5G industry has application scenarios such as car networking, internet of things, industrial control, remote medical treatment, and the like.

In the previous discussion of the third generation partnership project (3GPP) regarding network slicing techniques, network architecture groups have formed part of the conclusions that the radio interface is required to enable resource sharing between network instances and to guarantee independence between them. In detail, when a network instance is congested, the operation of another entity is not affected, and more flexible resource sharing between instances is also needed.

From the commercial perspective, the network slicing technology actually provides a special network platform for a third-party operator, and realizes that the third-party service is provided for a user by utilizing an operator network. For the operator, the third party operator or the vertical industry operation and maintenance company is actually the user of the operator. In a Long Term Evolution (LTE) system, the Quality of Service provided by a network to a user is guaranteed by Quality of Service (QoS). The personal User (UE) provides a specific service level according to its subscription level, and the network user (external network, i.e. network Access Point (APN)) also provides access services of different levels according to its subscription data.

For the QoS system of LTE, the analysis is here only done from the "Aggregate Maximum Bit Rate (AMBR), i.e. APN-AMBR and UE-AMBR parameters.

Wherein APN-AMBR indicates the cumulative allowed maximum bit rate for all bearers destined for the same APN. The parameter is distributed by a Home Subscriber Server (HSS) and issued to the UE and a Public Data Network (PDN) gateway (PGW, PDN Gate Way).

UE-AMBR represents the cumulative allowed maximum bit rate for all bearers of a certain UE. The parameter is allocated by the HSS according to the subscription level during subscription, and is executed by an evolved Node B (eNB).

AMBR is the maximum allowed rate allocated to a subscriber (network subscriber or individual subscriber) based on the subscription data of the subscriber and the underlying network conditions. Meanwhile, according to the 3GPP protocol, on the premise that the AMBR is not exceeded, resources used by one bearer can be automatically adjusted (on the premise that the requirements of other QoS parameters are met), that is, the current LTE system provides a hierarchical service through the QoS design, and at the same time, flexible resource sharing between users/bearers is realized.

As can be seen, the QoS system only realizes resource sharing of the LTE system, but cannot realize resource sharing between network slices.

Disclosure of Invention

The embodiment of the invention provides a resource sharing control method, an execution entity and a resource sharing configuration entity, which aim to solve the problem that the prior art can not realize resource sharing among network slices.

In a first aspect, an embodiment of the present invention provides a resource sharing control method, which is applied to an execution entity that executes resource sharing control in a network slice, and the method includes:

receiving resource sharing configuration information of the network slice, which is sent by a resource sharing configuration entity of the network slice;

and controlling the resources used by the network slice according to the resource sharing configuration information of the network slice.

In a second aspect, an embodiment of the present invention provides an execution entity for performing resource sharing control in a network slice, where the execution entity includes:

the first receiving module is used for receiving the resource sharing configuration information of the network slice sent by the resource sharing configuration entity of the network slice;

and the control module is used for controlling the resources used by the network slice according to the resource sharing configuration information of the network slice.

In a third aspect, an embodiment of the present invention provides a resource sharing control method, which is applied to a resource sharing configuration entity of a network slice, and the method includes:

determining resource sharing configuration information of a network slice corresponding to an execution entity executing resource sharing control in the network slice;

and sending the resource sharing configuration information of the network slice to an execution entity.

In a fourth aspect, an embodiment of the present invention provides a resource sharing configuration entity for network slicing, where the resource sharing configuration entity includes:

a first determining module, configured to determine resource sharing configuration information of a network slice corresponding to an execution entity that executes resource sharing control in the network slice;

and the third sending module is used for sending the resource sharing configuration information of the network slice to the execution entity.

In this way, in the embodiment of the present invention, the resource sharing configuration information of the network slice, which is sent by the resource sharing configuration entity of the network slice, is received, and the resource used by the network slice is controlled according to the resource sharing configuration information of the network slice, so that the resource sharing between the network slices is realized.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.

FIG. 1 is a flowchart of a method for controlling resource sharing according to a first embodiment of the present invention;

FIG. 2 is a flowchart illustrating a method for controlling resource sharing according to a second embodiment of the present invention;

FIG. 3A is a diagram illustrating interaction between an execution entity and a resource sharing configuration entity according to an embodiment of the present invention;

FIG. 3B is a second exemplary interaction diagram of an executive entity and a resource sharing configuration entity according to the present invention;

FIG. 3C is a third exemplary diagram illustrating interaction between an executive entity and a resource sharing configuration entity according to an embodiment of the present invention;

FIG. 3D is a fourth exemplary interaction diagram illustrating an execution entity and a resource sharing configuration entity according to an embodiment of the present invention;

FIG. 4A is a diagram illustrating resource scheduling according to an embodiment of the present invention;

FIG. 4B is a second schematic diagram illustrating resource scheduling according to an embodiment of the present invention;

FIG. 4C is a third exemplary diagram illustrating resource scheduling according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of a terminal in an embodiment of the present invention;

FIG. 6 is a block diagram of an execution entity according to a third embodiment of the present invention;

FIG. 7 is a second schematic diagram of a third embodiment of an execution entity according to the present invention;

FIG. 8 is a block diagram of an execution entity in a fourth embodiment of the present invention;

FIG. 9 is a flowchart of a resource sharing control method according to a fifth embodiment of the present invention;

FIG. 10 is a diagram illustrating resource sharing configuration information for a network slice in an example of an embodiment of the invention;

FIG. 11 is a diagram illustrating a structure of a resource sharing configuration entity according to a sixth embodiment of the present invention;

FIG. 12 is a second schematic structural diagram of a resource sharing configuration entity according to a sixth embodiment of the present invention;

fig. 13 is a schematic structural diagram of a resource sharing configuration entity in a seventh embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Combined with background research, it has been found that operators provide a characterized service capability according to the subscription level of users (network users and individual users).

The network slicing technology provides public network services for non-traditional services (such as vertical industries), and for mobile network operators, the actual operation and maintenance of the non-traditional services are different from the independent operation and maintenance of the traditional services. For example, a non-traditional service operator rents base station resources of the operator, and allocates partial time frequency resources of the operator to the network slice for use in a paid manner according to the subscription level of the operator. Thus, from a certain point of view, the operation and maintenance company of the network slice is also a company user of the operator. Therefore, it is necessary to design the service quality.

In addition, for a Mobile network access network, to implement flexible and dynamic sharing of resources between network slices, a range problem of resource sharing is involved, for example, in the case of 5G, when network sharing is performed between enhanced Mobile bandwidth (eMBB) network slice resources providing public voice and data services and other non-traditional service slices (e.g., car networking), a range of resource sharing needs to be defined. Such as the maximum number of resources used and/or the minimum number of guaranteed resources used by the non-traditional traffic network slice. Otherwise, when one network slice is congested, the basic requirements of other network slices cannot be guaranteed. Therefore, it is necessary to define a QoS architecture based on network slices to achieve resource sharing between network slices.

First embodiment

As shown in fig. 1, a first embodiment of the present invention provides a resource sharing control method applied to an execution entity that executes resource sharing control in a network slice, where the method includes:

step 101, receiving resource sharing configuration information of a network slice sent by a resource sharing configuration entity of the network slice.

In an embodiment of the present invention, the execution entity is an entity for performing resource sharing control in a network slice, and specifically may be a PGW, a base station, and the like, and it should be noted that the execution entity may correspond to a plurality of network slices (i.e., network instances).

In the embodiment of the present invention, the resource sharing configuration entity is configured to configure resource sharing configuration information for a network slice, and send the configured resource sharing configuration information to an execution entity corresponding to the network slice, so that a subsequent execution entity controls resources used by the network slice. The resource sharing configuration entity may be an HSS, an Operation Administration and Maintenance (OAM), a Policy and Charging Rules Function (PCRF), and the like.

Furthermore, in an embodiment of the present invention, the resource sharing configuration information includes: the execution entity reserves the minimum guaranteed resource for network slice usage and/or the maximum available resource that the execution entity can provide for network slice usage. Specifically, the minimum guaranteed resource includes a minimum guaranteed bandwidth, and the maximum available resource includes a maximum available bandwidth and/or an aggregate maximum bit rate. It should be noted that, in the embodiment of the present invention, after receiving the resource sharing configuration information of the network slice, the execution entity configures the resource sharing configuration information of the network slice, so as to execute the subsequent steps.

And 102, controlling the resources used by the network slice according to the resource sharing configuration information of the network slice.

In the embodiment of the present invention, the network slices in the step 101 and the step 102 are the same network slice, and it should be noted that, for each network slice of the execution entity, the execution entity can execute the step 101 and the step 102, so as to control the resources used by each network slice. It should be further noted that, in the embodiment of the present invention, according to the actual requirement of the network, the executing entity may simultaneously execute the

above steps

101 and 102 for each network slice corresponding to the executing entity, that is, it is equivalent to simultaneously control the resources used by each network slice; of course, the executing entity may also execute the

above steps

101 and 102 for each network slice corresponding thereto (i.e. not at the same time), thereby implementing resource sharing between the network slices.

Therefore, in the embodiment of the present invention, the resource sharing between the network slices is realized by receiving the resource sharing configuration information of the network slices sent by the resource sharing configuration entity of the network slices and controlling the resources used by the network slices according to the resource sharing configuration information of the network slices.

Second embodiment

As shown in fig. 2, a second embodiment of the present invention provides a resource sharing control method, applied to an execution entity that executes resource sharing control in a network slice, where the method includes:

step 201, receiving resource sharing configuration information of a network slice sent by a resource sharing configuration entity of the network slice, where the resource sharing configuration information includes: the execution entity reserves the minimum guaranteed resource for network slice usage and/or the maximum available resource that the execution entity can provide for network slice usage.

The minimum guaranteed resource refers to the minimum quantity of resources allocated to the network slice, and the maximum available resource refers to the maximum quantity of resources allocated to the network slice.

Wherein, the minimum guaranteed resource comprises a minimum guaranteed bandwidth, and the maximum available resource comprises a maximum available bandwidth and/or an aggregated maximum bit rate. It should be noted that, of course, the minimum guaranteed resource may also include a minimum guaranteed time ratio, and the maximum available resource may also include a maximum available time ratio. The minimum guaranteed time ratio refers to how much time is allocated to the network slice at least, and the maximum available time ratio refers to how much time is allocated to the network slice at most, that is, different network slices are distinguished by time domain.

Here, as an example, the aggregated maximum bit rate may be eNB-AMBR, slice-AMBR, or the like. The eNB-AMBR defines a maximum cumulative bit rate provided by a base station to a network slice, which is determined according to the capabilities of the base station (e.g., system bandwidth, antenna configuration, etc.) and the requirements of the network slice (e.g., network slice technical requirements and capability requirements established according to a geographical location). The parameter characterizes the service capability that the base station can provide for a certain network instance, and considering that there are regional characteristics in the operation of non-traditional services (such as car networking), the parameter does not need to be supported at each base station and needs to realize different access capabilities according to different geographic positions, namely, the parameter is the base station characteristic (eNB specific), and the specific value of each base station can be different. slice-AMBR defines the cumulative bit rate allowed for a certain network slice network. This parameter characterizes the total access capacity that a certain network slice possesses. The characteristics will be defined according to the specific requirements of the network slice (e.g., number of users, size of data packet, time delay, etc.) and the subscription data, and different network slices may be different. It should be noted that the eNB-AMBR and the slice-AMBR are respectively divided into two sets of parameters, namely uplink and downlink.

Step 202, controlling the resources used by the network slice according to the resource sharing configuration information of the network slice.

In the embodiment of the present invention, the resource sharing configuration entity is configured to configure resource sharing configuration information for a network slice, and send the configured resource sharing configuration information to an execution entity corresponding to the network slice, so that a subsequent execution entity controls resources used by the network slice. The resource sharing configuration entity may be an HSS, OAM, PCRF, and the like.

In an embodiment of the present invention, before performing step 201, the method further includes the following steps: and sending a request message for requesting the resource sharing configuration information to the resource sharing configuration entity. That is, it is equivalent to that the resource sharing configuration entity may actively send the resource sharing configuration information of the network slice to the execution entity, or may send the resource sharing configuration information of the network slice to the execution entity after receiving the request message for requesting the resource sharing configuration information sent by the execution entity.

Specifically, in the embodiment of the present invention, when the execution entity is initially established, as shown in fig. 3A, the resource sharing configuration entity can send the resource sharing configuration information of the network slice to the execution entity, so that the execution entity executes the step 201; of course, when the execution entity is initially established, as shown in fig. 3B, the execution entity may send a request message for requesting resource sharing configuration information to the resource sharing configuration entity, so that the resource sharing configuration entity sends the resource sharing configuration information of the network slice to the execution entity, and further, the execution entity executes step 201 described above.

In an embodiment of the present invention, a specific implementation manner of the step 201 may be: and receiving the resource sharing configuration information of the network slice forwarded by the resource sharing configuration entity through the core network control node. The core network control node may be a Mobility Management Entity (MME) or the like.

In an embodiment of the present invention, after the step 201 is executed and before the step 202 is executed, the method further includes the following steps: and updating the resource sharing configuration information. In the embodiment of the present invention, the specific implementation manner of updating the resource sharing configuration information may be as follows: and receiving the updated resource sharing configuration information of the network slice sent by the resource sharing configuration entity, and updating the locally configured resource sharing configuration information according to the updated resource sharing configuration information of the network slice. I.e. the resource sharing configuration information of the previous network slice (i.e. the resource sharing configuration information of the network slice in step 201) is replaced by the resource sharing configuration information of the updated network slice. In addition, in the embodiment of the present invention, before the step of receiving the resource sharing configuration information of the updated network slice sent by the resource sharing configuration entity is executed, the method further includes the following steps: and sending a request message for requesting to update the resource sharing configuration information to the resource sharing configuration entity. That is, it is equivalent to that the resource sharing configuration entity may actively modify the resource sharing configuration information of the network slice for some purpose or at the time of subscription data update of the network slice, or may modify the resource sharing configuration information of the network slice after receiving a request message for requesting to update the resource sharing configuration information sent by the execution entity. The request message for requesting to update the resource sharing configuration information may be sent by the execution entity according to a certain requirement, and the execution entity may forward the request message for requesting to update the resource sharing configuration information to the resource sharing configuration entity through a core network control node (e.g., MME).

Specifically, in the embodiment of the present invention, as shown in fig. 3C, the resource sharing configuration entity may actively modify the resource sharing configuration information of the network slice for a certain purpose or when the subscription data of the network slice is updated, and send the updated resource sharing configuration information of the network slice to the execution entity; of course, as shown in fig. 3D, the execution entity may send a request message for requesting to update the resource sharing configuration information to the resource sharing configuration entity according to a certain requirement, so that the resource sharing configuration entity sends the resource sharing configuration information of the updated network slice to the execution entity.

In an embodiment of the present invention, the first specific implementation manner of the step 202 includes the following steps: when the actual scheduling resources of all terminals corresponding to the execution entity and communicating with the network slice meet a first preset condition, resources unused by the network slice are allocated to other network slices of the execution entity, so that flexible resource sharing is realized.

Wherein the first preset condition includes at least one of the following conditions: the actual scheduling resource is greater than or equal to the minimum guaranteed resource reserved by the execution entity for the network slice; the actual scheduling resource is less than or equal to the maximum available resource that the execution entity can provide for the network slice to use.

It should be noted that, when the actual scheduling resources of all terminals corresponding to the execution entity and communicating with the network slice satisfy the first preset condition, the unused resources of the network slice may not be allocated. As an example, in an embodiment of the present invention, when an execution entity needs to allocate resources that are not used by the network slice (for example, when other network slices of the execution entity need more resources), the execution entity may allocate the resources that are not used by the network slice to other network slices of the execution entity, and if the execution entity does not need to allocate the resources that are not used by the network slice, the execution entity may not allocate the resources that are not used by the network slice.

In an embodiment of the present invention, the second specific implementation manner of the step 202 includes the following steps: when the resource sharing configuration information of the network slice cannot match with the actual network requirement, at least one of the following operations is executed: terminals except for the terminal which is accessed to the network slice are forbidden to be accessed to the network slice; reducing the bit rate used by the network slice; and sending a request message for requesting to update the resource sharing configuration information to the resource sharing configuration entity so as to increase the resources of the network slice.

When the resource sharing configuration information of the network slice is the maximum available bandwidth that the execution entity can provide for the network slice to use, the fact that the resource sharing configuration information of the network slice cannot match with the actual network requirement means that: the maximum available bandwidth that the enforcement entity may provide for use by the network slice may not meet the actual network requirements of the network slice, i.e., the maximum available bandwidth that the enforcement entity may provide for use by the network slice may not be sufficient to support the actual traffic requirements of the network slice. When the resource sharing configuration information of the network slice is the maximum aggregate bit rate that the execution entity can provide for the network slice to use, the fact that the resource sharing configuration information of the network slice cannot match with the actual network requirement means that: the aggregate maximum bit rate that the enforcement entity may provide for use by the network slice may not meet the actual network requirements of the network slice, i.e., the aggregate maximum bit rate that the enforcement entity may provide for use by the network slice may not be sufficient to support the actual traffic requirements of the network slice.

In an embodiment of the present invention, the third specific implementation manner of the step 202 includes the following steps: scheduling the air interface resources according to the maximum bit rate of the aggregation which can be provided by the execution entity for the network slice to use; or, according to the maximum available bandwidth which can be provided by the execution entity for the network slice to use, scheduling the air interface resource; or, according to the minimum guaranteed bandwidth reserved by the execution entity for the network slice, the air interface resource is scheduled.

In an embodiment of the present invention, a specific implementation manner of scheduling the air interface resource according to the maximum aggregated bit rate that the execution entity can provide to the network slice for use is as follows: and scheduling resources of all terminals which correspond to the execution entity and communicate with the network slice according to the maximum aggregate bit rate which can be provided by the execution entity for the network slice to use. Wherein the cumulative bit rate of all terminals is less than or equal to the aggregate maximum bit rate that the performing entity can provide for use by the network slice. It should be noted that the accumulated bit rate of the terminal can be obtained as follows: and calculating the effective bit number which can be borne by the scheduling resources of the basic scheduling unit according to the channel quality and the modulation coding format, and calculating the accumulated bit rate which is sent to the network slice by all terminals which correspond to the execution entity and are communicated with the network slice through the effective bit number of the basic scheduling unit and the number of the scheduled basic scheduling units.

In an embodiment of the present invention, a specific implementation manner of scheduling the air interface resource according to the maximum available bandwidth that the execution entity can provide for the network slice to use is as follows: and scheduling resources of all terminals which correspond to the execution entity and communicate with the network slice according to the maximum available bandwidth which can be provided by the execution entity for the network slice to use. And the equivalent bandwidth of the scheduling resource obtained by all the terminals in an accumulated mode is smaller than or equal to the maximum available bandwidth which can be provided by the execution entity for the network slice to use.

In the embodiment of the present invention, the specific implementation manner of scheduling the air interface resource according to the minimum guaranteed bandwidth reserved by the execution entity for the network slice is as follows: and according to the minimum guaranteed bandwidth reserved by the execution entity for the network slice, performing resource scheduling on all terminals which correspond to the execution entity and are communicated with the network slice. And the equivalent bandwidth of the scheduling resources obtained by accumulation of all the terminals is greater than or equal to the minimum guaranteed bandwidth reserved by the execution entity for the network slice.

In an embodiment of the present invention, in order to facilitate resource scheduling for all terminals corresponding to an execution entity and communicating with a network slice, the method further includes: and acquiring the equivalent bandwidth of the scheduling resources obtained by all the terminals in an accumulated manner. In particular, canIs shown in formula B_{s_eq}＝M_s(T) × b (T) the equivalent bandwidth of the scheduling resources cumulatively obtained for all terminals communicating with the network slice S is calculated. Wherein, B_{s_eq}Representing the equivalent bandwidth of the scheduled resource cumulatively obtained by all terminals communicating with the network slice S, b (t) representing the measurement period, which may be an integer multiple of the resource scheduling, M_s(T) represents the physical resource utilization of the network slice S,

M_s1(T) denotes the total number of physical layer resource blocks actually used by all terminals communicating with the network slice S during the measurement period, P_s(T) represents the total number of physical layer resource blocks owned by the system in the measurement period, and M_sThe value of (T) should be between 0 and 100%, and in addition, M_s1(T) is divided into an uplink and a downlink.

It should be noted that, in the embodiment of the present invention, a specific implementation manner of performing resource scheduling on all terminals corresponding to the execution entity and communicating with the network slice is as follows: and according to the time domain multiplexing mode and/or the frequency domain multiplexing mode, performing resource scheduling on all terminals which correspond to the execution entity and are communicated with the network slice, and further realizing resource sharing.

Here, to facilitate a clearer understanding of a specific implementation of resource scheduling for all terminals corresponding to the performing entities and communicating with the network slice, as shown in fig. 4A, 4B and 4C, the specific implementation of the resource scheduling is described by taking the network slice a and the network slice B as an example. Fig. 4A shows resource scheduling performed on all terminals corresponding to the execution entity and communicating with the network slice according to the time domain multiplexing manner; fig. 4B shows resource scheduling for all terminals corresponding to the performing entity and communicating with the network slice according to the frequency domain multiplexing; fig. 4C shows resource scheduling for all terminals corresponding to the performing entity and communicating with the network slice according to the time domain multiplexing method and the frequency domain multiplexing method.

In an embodiment of the present invention, the fourth specific implementation manner of the step 202 includes the following steps: accumulating the total bit rate of all bearers connected to a Public Data Network (PDN) gateway and sent to a network slice; and then detecting whether the total bit rate of all the bearers connected to the PDN gateway and sent to the network slice is greater than the maximum aggregate bit rate which can be provided by the execution entity for the network slice to use, and if the total bit rate of all the bearers connected to the PDN gateway and sent to the network slice is greater than the maximum aggregate bit rate which can be provided by the execution entity for the network slice to use, discarding the bearers meeting a second preset condition. Wherein, satisfying bearing of second preset condition includes: the total bit rate of all bearers connected to the PDN gateway destined for the network slice is made greater than the bearer for which the performing entity can provide the aggregated maximum bit rate available for use by the network slice.

In the embodiments of the present invention, for the convenience of understanding the terminal in the above embodiments, the structure of the terminal is explained herein. Specifically, as shown in fig. 5, the terminal 500 may be a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), or a vehicle-mounted computer.

The terminal 500 in fig. 5 includes a Radio Frequency (RF) circuit 510, a memory 520, an input unit 530, a display unit 540, a processor 560, an audio circuit 570, a wifi (wireless fidelity) module 580, and a power supply 590.

The input unit 530 may be used to receive numeric or character information input by a user and generate signal inputs related to user settings and function control of the terminal 500, among other things. Specifically, in the embodiment of the present invention, the input unit 530 may include a touch panel 531. The touch panel 531, also called a touch screen, can collect touch operations of a user (for example, operations of the user on the touch panel 531 by using a finger, a stylus pen, or any other suitable object or accessory) thereon or nearby, and drive the corresponding connection device according to a preset program. Alternatively, the touch panel 531 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts it to touch point coordinates, sends it to the processor 560, and can receive and execute commands from the processor 560. In addition, the touch panel 531 may be implemented by various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 531, the input unit 530 may further include other input devices 532, and the other input devices 532 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

Among other things, the display unit 540 may be used to display information input by the user or information provided to the user and various menu interfaces of the terminal 500. The display unit 540 may include a display panel 541, and optionally, the display panel 541 may be configured in the form of an LCD or an organic light-emitting diode (OLED), or the like.

It should be noted that the touch panel 531 may cover the display panel 541 to form a touch display screen, and when the touch display screen detects a touch operation thereon or nearby, the touch display screen is transmitted to the processor 560 to determine the type of the touch event, and then the processor 560 provides a corresponding visual output on the touch display screen according to the type of the touch event.

The touch display screen comprises an application program interface display area and a common control display area. The arrangement modes of the application program interface display area and the common control display area are not limited, and can be an arrangement mode which can distinguish two display areas, such as vertical arrangement, left-right arrangement and the like. The application interface display area may be used to display an interface of an application. Each interface may contain at least one interface element such as an icon and/or widget desktop control for an application. The application interface display area may also be an empty interface that does not contain any content. The common control display area is used for displaying controls with high utilization rate, such as application icons like setting buttons, interface numbers, scroll bars, phone book icons and the like.

The processor 560 is a control center of the terminal 500, connects various parts of the entire cellular phone using various interfaces and lines, and performs various functions of the terminal 500 and processes data by operating or executing software programs and/or modules stored in the first memory 521 and calling data stored in the second memory 522, thereby integrally monitoring the terminal 500. Optionally, processor 560 may include one or more processing units.

In an embodiment of the present invention, the processor 560 is configured to communicate the terminal with the network slice according to the scheduling of the executing entity by invoking software programs and/or modules stored in the first memory 521 and/or data stored in the second memory 522.

And in an embodiment of the present invention, the cumulative bit rate of all terminals communicating with the network slice is less than or equal to the aggregate maximum bit rate that the performing entity can provide for use by the network slice; the equivalent bandwidth of scheduling resources obtained by accumulation of all terminals communicating with the network slice is less than or equal to the maximum available bandwidth which can be provided by the execution entity for the network slice to use; the equivalent bandwidth of scheduling resources obtained by accumulation of all terminals communicating with the network slice is greater than or equal to the minimum guaranteed bandwidth reserved by the execution entity for the network slice.

It can be seen that, in the embodiment of the present invention, resource sharing between network slices is implemented by receiving resource sharing configuration information of a network slice (the resource sharing configuration information includes a minimum guaranteed resource reserved by an execution entity for use by the network slice and/or a maximum available resource available for use by the execution entity for the network slice) sent by a resource sharing configuration entity of the network slice, and controlling resources used by the network slice according to the minimum guaranteed resource reserved by the execution entity for use by the network slice and/or the maximum available resource available for use by the execution entity for use by the network slice.

Third embodiment

The above first to second embodiments respectively describe in detail the control method for resource sharing in different scenarios, and the following further describes the corresponding execution entities with reference to fig. 6 and 7.

As shown in fig. 6 to 7, a third embodiment of the present invention provides an execution entity for performing resource sharing control in a network slice, where the execution entity 600 includes:

a first receiving module 601, configured to receive resource sharing configuration information of a network slice sent by a resource sharing configuration entity of the network slice;

the control module 602 is configured to control resources used by the network slice according to the resource sharing configuration information of the network slice.

Optionally, the executing entity further includes:

a first sending module 603, configured to send a request message for requesting resource sharing configuration information to the resource sharing configuration entity.

Optionally, the first receiving module 601 is specifically configured to receive resource sharing configuration information of a network slice, where the resource sharing configuration information is forwarded by the resource sharing configuration entity through the core network control node.

Optionally, the executing entity further includes:

an updating module 604, configured to update the resource sharing configuration information.

Optionally, the updating module 604 includes:

a first updating submodule 6041, configured to receive resource sharing configuration information of an updated network slice sent by a resource sharing configuration entity;

and a second updating sub-module 6042, configured to update the locally configured resource sharing configuration information according to the updated resource sharing configuration information of the network slice.

Optionally, the executing entity further includes:

a second sending module 605, configured to send a request message for requesting to update the resource sharing configuration information to the resource sharing configuration entity.

Optionally, the resource sharing configuration information includes: the execution entity reserves the minimum guaranteed resource for network slice usage and/or the maximum available resource that the execution entity can provide for network slice usage.

Optionally, the control module 602 is specifically configured to, when actual scheduling resources of all terminals corresponding to the execution entity and communicating with the network slice meet a first preset condition, allocate resources that are not used by the network slice to other network slices of the execution entity;

wherein the first preset condition comprises at least one of the following conditions:

the actual scheduling resource is greater than or equal to the minimum guaranteed resource reserved by the execution entity for the network slice;

the actual scheduling resources are less than or equal to the maximum available resources that the execution entity may provide for use by the network slice.

Optionally, the minimum guaranteed resource comprises a minimum guaranteed bandwidth, and the maximum available resource comprises a maximum available bandwidth and/or an aggregated maximum bit rate.

Optionally, the control module 602 is specifically configured to, when the resource sharing configuration information of the network slice cannot match the actual network requirement, perform at least one of the following operations:

terminals except for the terminal which is accessed to the network slice are forbidden to be accessed to the network slice;

reducing the bit rate used by the network slice;

and sending a request message for requesting to update the resource sharing configuration information to the resource sharing configuration entity.

Optionally, the control module 602 includes:

a first control submodule 6021, configured to schedule the air interface resource according to an aggregate maximum bit rate that the execution entity can provide for the network slice to use;

or the second control submodule 6022 is configured to schedule the air interface resource according to the maximum available bandwidth that the execution entity can provide to the network slice for use;

or a third control sub-module 6023, configured to schedule the air interface resource according to the minimum guaranteed bandwidth reserved by the execution entity for the network slice.

Optionally, the first control sub-module 6021 is specifically configured to perform resource scheduling on all terminals corresponding to the execution entity and communicating with the network slice according to the maximum aggregated bit rate that the execution entity can provide to the network slice for use;

wherein the cumulative bit rate of all terminals is less than or equal to the aggregate maximum bit rate that the performing entity can provide for use by the network slice.

Optionally, the second control sub-module 6022 is specifically configured to perform resource scheduling on all terminals corresponding to the execution entity and communicating with the network slice according to a maximum available bandwidth that the execution entity can provide to the network slice for use;

and the equivalent bandwidth of the scheduling resource obtained by all the terminals in an accumulated mode is smaller than or equal to the maximum available bandwidth which can be provided by the execution entity for the network slice to use.

Optionally, the third control sub-module 6023 is specifically configured to perform resource scheduling on all terminals corresponding to the execution entity and communicating with the network slice according to the minimum guaranteed bandwidth reserved by the execution entity for the network slice;

and the equivalent bandwidth of the scheduling resources obtained by accumulation of all the terminals is greater than or equal to the minimum guaranteed bandwidth reserved by the execution entity for the network slice.

Optionally, the executing entity includes:

a scheduling module 606, configured to perform resource scheduling on all terminals corresponding to the execution entity and communicating with the network slice according to the time domain multiplexing mode and/or the frequency domain multiplexing mode.

Optionally, the executing entity further includes:

a calculation module 607 for passing formula B_{s_eq}＝M_s(T) B (T) calculating scheduling resources cumulatively obtained for all terminals communicating with the network slice SAn equivalent bandwidth;

wherein, B_{s_eq}Representing the equivalent bandwidth of the scheduling resources cumulatively obtained by all terminals communicating with the network slice S, B (T) representing the measurement period, M_s(T) represents the physical resource utilization of the network slice S,

M_s1(T) denotes the total number of physical layer resource blocks actually used by all terminals communicating with the network slice S during the measurement period, P_sAnd (T) represents the total number of physical layer resource blocks owned by the system in the measurement period.

Optionally, the control module 602 includes:

a fourth control submodule 6024 configured to accumulate a total bit rate of all bearers connected to the public data network PDN gateway to the network slice;

a fifth control sub-module 6025 configured to detect whether a total bit rate of all bearers connected to the PDN gateway and addressed to the network slice is greater than an aggregated maximum bit rate that the execution entity can provide for the network slice to use, and trigger a sixth control sub-module 6026 if the total bit rate of all bearers connected to the PDN gateway and addressed to the network slice is greater than the aggregated maximum bit rate that the execution entity can provide for the network slice to use;

a sixth control submodule 6026 configured to discard the bearer satisfying the second preset condition according to the triggering of the fifth control submodule 6025;

wherein, satisfying bearing of second preset condition includes: the total bit rate of all bearers connected to the PDN gateway destined for the network slice is made greater than the bearer for which the performing entity can provide the aggregated maximum bit rate available for use by the network slice.

In the third embodiment of the present invention, the execution entity 600 receives the resource sharing configuration information of the network slice sent by the resource sharing configuration entity of the network slice, and controls the resource used by the network slice according to the resource sharing configuration information of the network slice, thereby implementing resource sharing between the network slices.

Fourth embodiment

In order to better achieve the above object, as shown in fig. 8, a fourth embodiment of the present invention provides an execution entity for performing resource sharing control in a network slice, the execution entity comprising: a processor 800; a memory 820 connected to the processor 800 through a bus interface, and a transceiver 810 connected to the processor 800 through a bus interface; the memory 820 is used for storing programs and data used by the processor in performing operations; transmitting data information or pilot frequency through the transceiver 810, and receiving an uplink control channel through the transceiver 810; when the processor 800 calls and executes the program and data stored in the memory 820, it is specifically configured to receive the resource sharing configuration information of the network slice sent by the resource sharing configuration entity of the network slice; and controlling the resources used by the network slice according to the resource sharing configuration information of the network slice.

Optionally, the processor 800 is further configured to: and sending a request message for requesting the resource sharing configuration information to the resource sharing configuration entity.

Optionally, the processor 800 is further configured to: and receiving the resource sharing configuration information of the network slice forwarded by the resource sharing configuration entity through the core network control node.

Optionally, the processor 800 is further configured to: and updating the resource sharing configuration information.

Optionally, the processor 800 is further configured to: receiving resource sharing configuration information of the updated network slice, which is sent by a resource sharing configuration entity; and updating the locally configured resource sharing configuration information according to the updated resource sharing configuration information of the network slice.

Optionally, the processor 800 is further configured to: and sending a request message for requesting to update the resource sharing configuration information to the resource sharing configuration entity.

Optionally, the processor 800 is further configured to: when the actual scheduling resources of all terminals corresponding to the execution entity and communicating with the network slice meet a first preset condition, allocating the resources unused by the network slice to other network slices of the execution entity; wherein the first preset condition comprises at least one of the following conditions: the actual scheduling resource is greater than or equal to the minimum guaranteed resource reserved by the execution entity for the network slice; the actual scheduling resources are less than or equal to the maximum available resources that the execution entity may provide for use by the network slice.

Optionally, the processor 800 is further configured to: when the resource sharing configuration information of the network slice cannot match with the actual network requirement, at least one of the following operations is executed: terminals except for the terminal which is accessed to the network slice are forbidden to be accessed to the network slice; reducing the bit rate used by the network slice; and sending a request message for requesting to update the resource sharing configuration information to the resource sharing configuration entity.

Optionally, the processor 800 is further configured to: scheduling the air interface resources according to the maximum bit rate of the aggregation which can be provided by the execution entity for the network slice to use; or, according to the maximum available bandwidth which can be provided by the execution entity for the network slice to use, scheduling the air interface resource; or, according to the minimum guaranteed bandwidth reserved by the execution entity for the network slice, the air interface resource is scheduled.

Optionally, the processor 800 is further configured to: and scheduling resources of all terminals which correspond to the execution entity and communicate with the network slice according to the maximum aggregate bit rate which can be provided by the execution entity for the network slice to use. Wherein the cumulative bit rate of all terminals is less than or equal to the aggregate maximum bit rate that the performing entity can provide for use by the network slice.

Optionally, the processor 800 is further configured to: and scheduling resources of all terminals which correspond to the execution entity and communicate with the network slice according to the maximum available bandwidth which can be provided by the execution entity for the network slice to use. And the equivalent bandwidth of the scheduling resource obtained by all the terminals in an accumulated mode is smaller than or equal to the maximum available bandwidth which can be provided by the execution entity for the network slice to use.

Optionally, the processor 800 is further configured to: and according to the minimum guaranteed bandwidth reserved by the execution entity for the network slice, performing resource scheduling on all terminals which correspond to the execution entity and are communicated with the network slice. And the equivalent bandwidth of the scheduling resources obtained by accumulation of all the terminals is greater than or equal to the minimum guaranteed bandwidth reserved by the execution entity for the network slice.

Optionally, the processor 800 is further configured to: and according to the time domain multiplexing mode and/or the frequency domain multiplexing mode, performing resource scheduling on all terminals which correspond to the execution entity and are communicated with the network slice.

Optionally, the processor 800 is further configured to: by the formula B_{s_eq}＝M_s(T) × b (T) calculating the equivalent bandwidth of the scheduling resources cumulatively obtained by all terminals communicating with the network slice S; wherein, B_{s_eq}Representing the equivalent bandwidth of the scheduling resources cumulatively obtained by all terminals communicating with the network slice S, B (T) representing the measurement period, M_s(T) represents the physical resource utilization of the network slice S,

Optionally, the processor 800 is further configured to: accumulating the total bit rate of all the bearers connected to the public data network PDN gateway and sent to the network slice; detecting whether the total bit rate of all bearers connected to the PDN gateway and addressed to the network slice is greater than an aggregated maximum bit rate that an enforcement entity can provide to the network slice for use; and if the total bit rate of all the bearers connected to the PDN gateway and sent to the network slice is greater than the maximum aggregate bit rate which can be provided by the execution entity for the network slice, discarding the bearers meeting the second preset condition. Wherein, satisfying bearing of second preset condition includes: the total bit rate of all bearers connected to the PDN gateway destined for the network slice is made greater than the bearer for which the performing entity can provide the aggregated maximum bit rate available for use by the network slice.

A transceiver 810 for receiving and transmitting data under the control of the processor 800.

Where in fig. 8, the bus architecture may include any number of interconnected buses and bridges, with various circuits being linked together, particularly one or more processors represented by processor 800 and memory represented by memory 820. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 810 may be a number of elements including a transmitter and a transceiver providing a means for communicating with various other apparatus over a transmission medium. The processor 800 is responsible for managing the bus architecture and general processing, and the memory 820 may store data used by the processor 800 in performing operations.

In this way, the execution entity receives the resource sharing configuration information of the network slice sent by the resource sharing configuration entity of the network slice, and controls the resources used by the network slice according to the resource sharing configuration information of the network slice, thereby realizing the resource sharing among the network slices.

Fifth embodiment

The first to fourth embodiments respectively describe the control method for resource sharing and the execution entity in the present invention with respect to the execution entity, and the following embodiments further describe the control method for resource sharing of the resource sharing configuration entity of the network slice with reference to the accompanying drawings and specific application scenarios.

As shown in fig. 9, a fifth embodiment of the present invention provides a resource sharing control method, which is applied to a resource sharing configuration entity of a network slice, and the method includes:

step 901, determining resource sharing configuration information of a network slice corresponding to an execution entity executing resource sharing control in the network slice.

In an embodiment of the present invention, the resource sharing configuration information includes: the execution entity reserves the minimum guaranteed resource for network slice usage and/or the maximum available resource that the execution entity can provide for network slice usage. The minimum guaranteed resource refers to the minimum quantity of resources allocated to the network slice, and the maximum available resource refers to the maximum quantity of resources allocated to the network slice.

In an embodiment of the present invention, before the step 901 is executed, the method further includes the following steps: and receiving a request message which is sent by the execution entity and used for requesting the resource sharing configuration information. That is, it is equivalent to that the resource sharing configuration entity may actively send the resource sharing configuration information of the network slice to the execution entity, or may send the resource sharing configuration information of the network slice to the execution entity after receiving the request message for requesting the resource sharing configuration information sent by the execution entity.

Step 902, sending the resource sharing configuration information of the network slice to the execution entity.

In the embodiment of the present invention, the network slices in the step 901 and the step 902 are the same network slice.

In an embodiment of the present invention, a specific implementation manner of the step 902 may be: and sending the resource sharing configuration information of the network slice to an execution entity through the core network control node. The core network control node may be a mobility management entity or the like.

In an embodiment of the present invention, after the step 902 is executed, the method further includes the following steps: and determining the updated resource sharing configuration information of the network slice, and sending the updated resource sharing configuration information of the network slice to an execution entity. The specific implementation manner of sending the updated resource sharing configuration information of the network slice may be the same as the specific implementation manner of step 902.

Furthermore, in an embodiment of the present invention, before the step of determining the resource sharing configuration information of the updated network slice is performed, the method further includes the following steps: and receiving a request message which is sent by the execution entity and used for requesting to update the resource sharing configuration information. That is, it is equivalent to that the resource sharing configuration entity may actively modify the resource sharing configuration information of the network slice for some purpose or at the time of subscription data update of the network slice, or may modify the resource sharing configuration information of the network slice after receiving a request message for requesting to update the resource sharing configuration information sent by the execution entity.

In an embodiment of the present invention, a first specific implementation manner of the step 901 is as follows: and determining resource sharing configuration information of the network slice corresponding to the execution entity according to the signing data of the network slice. The resource sharing configuration information of the network slice on different execution entities is the same or different, and it should be noted that the subscription data may be the same as the subscription data of the current network slice (i.e., the network instance), so that the subscription data is not described in detail herein.

In the embodiment of the present invention, a second specific implementation manner of the step 901 is as follows: and determining resource sharing configuration information of the network slice corresponding to the execution entity according to the position information and/or the time information of the execution entity.

In the embodiment of the present invention, it should be noted that a specific implementation manner of determining the resource sharing configuration information of the updated network slice may be the same as the specific implementation manner of step 901 described above.

To facilitate understanding that the resource sharing configuration information of the network slice is the same or different on different execution entities, a network slice C (assumed to be an eMBB network slice providing common voice and data services) and a network slice D (assumed to be a car networking) are taken as an example for illustration, and in this example, the execution entity is assumed to be a base station, and the resource sharing configuration information of the network slice is an aggregate maximum bit rate that the execution entity can provide to the network slice for use. Specifically, as shown in fig. 10, when the base station is close to the highway, the aggregate maximum bit rate corresponding to the network slice C is smaller than the aggregate maximum bit rate corresponding to the network slice D; when the base station is close to the house, the maximum bit rate of the aggregation corresponding to the network slice C is larger than the maximum bit rate of the aggregation corresponding to the network slice D; when the base station is between the highway and the residence, the aggregate maximum bit rate corresponding to network slice C is substantially the same as the aggregate maximum bit rate corresponding to network slice D. In fig. 10, a dashed box represents an aggregate maximum bit rate corresponding to the network slice C, and a solid box next to the dashed box represents an aggregate maximum bit rate corresponding to the network slice D.

In the embodiment of the invention, the resource sharing configuration information of the network slice corresponding to the execution entity executing the resource sharing control in the network slice is determined, and the resource sharing configuration information of the network slice is sent to the execution entity, so that the execution entity controls the resources used by the network slice according to the resource sharing configuration information of the network slice, and the resource sharing among the network slices is realized.

Sixth embodiment

The above fifth embodiment describes the control method of resource sharing in different scenarios in detail, and the resource sharing configuration entity of the network slice corresponding to the fifth embodiment is further described with reference to fig. 11 to 12.

As shown in fig. 11 to 12, a sixth embodiment of the present invention provides a resource sharing configuration entity of a network slice, where the resource sharing configuration entity 1100 includes:

a first determining module 1101, configured to determine resource sharing configuration information of a network slice corresponding to an execution entity that executes resource sharing control in the network slice;

a third sending module 1102, configured to send the resource sharing configuration information of the network slice to the execution entity.

Optionally, the resource sharing configuration entity further includes:

a second receiving module 1103, configured to receive a request message sent by an execution entity for requesting resource sharing configuration information.

Optionally, the third sending module 1102 is specifically configured to send the resource sharing configuration information of the network slice to the execution entity through the core network control node.

Optionally, the resource sharing configuration entity further includes:

a second determining module 1104, configured to determine resource sharing configuration information of the updated network slice;

a fourth sending module 1105, configured to send the updated resource sharing configuration information of the network slice to the execution entity.

Optionally, the resource sharing configuration entity further includes:

a third receiving module 1106, configured to receive a request message sent by an executing entity for requesting to update the resource sharing configuration information.

Optionally, the first determining module 1101 is specifically configured to determine, according to the subscription data of the network slice, resource sharing configuration information of the network slice corresponding to the execution entity;

the resource sharing configuration information of the network slice on different execution entities is the same or different.

Optionally, the first determining module 1101 is specifically configured to determine, according to the location information and/or the time information of the execution entity, resource sharing configuration information of a network slice corresponding to the execution entity.

In the embodiment of the present invention, the resource sharing configuration entity 1100 controls the resources used by the network slices according to the resource sharing configuration information of the network slices by determining the resource sharing configuration information of the network slices corresponding to the execution entities performing the resource sharing control in the network slices and sending the resource sharing configuration information of the network slices to the execution entities, thereby implementing resource sharing between the network slices.

Seventh embodiment

In order to better achieve the above object, as shown in fig. 13, a seventh embodiment of the present invention provides a resource sharing configuration entity of a network slice, where the resource sharing configuration entity 1300 includes: a processor 1301, a transceiver 1302, a memory 1303, a user interface 1304, and a bus interface, wherein:

the processor 1301 is configured to read the program in the memory 1303, and execute the following processes:

determining resource sharing configuration information of a network slice corresponding to an execution entity executing resource sharing control in the network slice; and sending the resource sharing configuration information of the network slice to an execution entity.

In fig. 13, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 1301 and various circuits of memory represented by memory 1303 linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1302 may be a plurality of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. The user interface 1304 may also be an interface capable of interfacing with a desired device for different user devices, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 1301 is responsible for managing a bus architecture and general processing, and the memory 1303 may store data used by the processor 1301 in performing operations.

Optionally, the processor 1301 is further configured to: and receiving a request message which is sent by the execution entity and used for requesting the resource sharing configuration information.

Optionally, the processor 1301 is further configured to: and sending the resource sharing configuration information of the network slice to an execution entity through the core network control node.

Optionally, the processor 1301 is further configured to: determining updated resource sharing configuration information of the network slice; and sending the updated resource sharing configuration information of the network slice to the execution entity.

Optionally, the processor 1301 is further configured to: and receiving a request message which is sent by the execution entity and used for requesting to update the resource sharing configuration information.

Optionally, the processor 1301 is further configured to: determining resource sharing configuration information of the network slice corresponding to the execution entity according to the signing data of the network slice; the resource sharing configuration information of the network slice on different execution entities is the same or different.

Optionally, the processor 1301 is further configured to: and determining resource sharing configuration information of the network slice corresponding to the execution entity according to the position information and/or the time information of the execution entity.

The resource sharing configuration entity of the embodiment of the invention controls the resources used by the network slices according to the resource sharing configuration information of the network slices by determining the resource sharing configuration information of the network slices corresponding to the execution entity executing the resource sharing control in the network slices and sending the resource sharing configuration information of the network slices to the execution entity, thereby realizing the resource sharing among the network slices.

Furthermore, it is to be noted that in the device and method of the invention, it is obvious that the individual components or steps can be decomposed and/or recombined. These decompositions and/or recombinations are to be regarded as equivalents of the present invention. Also, the steps of performing the series of processes described above may naturally be performed chronologically in the order described, but need not necessarily be performed chronologically, and some steps may be performed in parallel or independently of each other. It will be understood by those skilled in the art that all or any of the steps or elements of the method and apparatus of the present invention may be implemented in any computing device (including processors, storage media, etc.) or network of computing devices, in hardware, firmware, software, or any combination thereof, which can be implemented by those skilled in the art using their basic programming skills after reading the description of the present invention.

Thus, the objects of the invention may also be achieved by running a program or a set of programs on any computing device. The computing device may be a general purpose device as is well known. The object of the invention is thus also achieved solely by providing a program product comprising program code for implementing the method or the apparatus. That is, such a program product also constitutes the present invention, and a storage medium storing such a program product also constitutes the present invention. It is to be understood that the storage medium may be any known storage medium or any storage medium developed in the future. It is further noted that in the apparatus and method of the present invention, it is apparent that each component or step can be decomposed and/or recombined. These decompositions and/or recombinations are to be regarded as equivalents of the present invention. Also, the steps of executing the series of processes described above may naturally be executed chronologically in the order described, but need not necessarily be executed chronologically. Some steps may be performed in parallel or independently of each other.

While the preferred embodiments of the present invention have been described, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the following claims.

Claims

1. A control method of resource sharing is applied to an execution entity for executing resource sharing control in a network slice, and is characterized in that the method comprises the following steps:

controlling the resources used by the network slice according to the resource sharing configuration information of the network slice;

the resource sharing configuration information includes: the execution entity reserves a minimum guaranteed resource for use by the network slice and/or a maximum available resource that the execution entity may provide for use by the network slice.

2. The method according to claim 1, wherein before the step of receiving the resource sharing configuration information of the network slice sent by the resource sharing configuration entity of the network slice, the method further comprises:

and sending a request message for requesting the resource sharing configuration information to the resource sharing configuration entity.

3. The method according to claim 1, wherein the step of receiving the resource sharing configuration information of the network slice sent by the resource sharing configuration entity of the network slice comprises:

and receiving the resource sharing configuration information of the network slice forwarded by the resource sharing configuration entity through the core network control node.

4. The method according to claim 1, wherein before the step of controlling the resources used by the network slice according to the resource sharing configuration information of the network slice, the method further comprises, after the step of receiving the resource sharing configuration information of the network slice sent by the resource sharing configuration entity of the network slice:

and updating the resource sharing configuration information.

5. The method according to claim 4, wherein the step of updating the resource sharing configuration information comprises:

receiving the updated resource sharing configuration information of the network slice sent by the resource sharing configuration entity;

and updating the locally configured resource sharing configuration information according to the updated resource sharing configuration information of the network slice.

6. The method according to claim 5, wherein before the step of receiving the resource sharing configuration information of the updated network slice sent by the resource sharing configuration entity, the method further comprises:

7. The method according to claim 1, wherein the step of controlling the resources used by the network slice according to the resource sharing configuration information of the network slice comprises:

when actual scheduling resources of all terminals corresponding to the execution entity and communicating with the network slice meet a first preset condition, allocating resources unused by the network slice to other network slices of the execution entity;

wherein the first preset condition comprises at least one of the following:

the actual scheduling resource is greater than or equal to the minimum guaranteed resource reserved by the execution entity for use by the network slice;

the actual scheduled resources are less than or equal to a maximum available resources that the execution entity may provide for use by the network slice.

8. The method of claim 1, wherein the minimum guaranteed resource comprises a minimum guaranteed bandwidth, and wherein the maximum available resource comprises a maximum available bandwidth and/or an aggregate maximum bit rate.

9. The method according to claim 8, wherein the step of controlling the resources used by the network slice according to the resource sharing configuration information of the network slice comprises:

when the resource sharing configuration information of the network slice cannot match with the actual network requirement, at least one of the following operations is executed:

prohibiting terminals except for terminals having access to the network slice from accessing the network slice;

reducing a bit rate used by the network slice;

10. The method according to claim 8, wherein the step of controlling the resources used by the network slice according to the resource sharing configuration information of the network slice comprises:

scheduling air interface resources according to the maximum bit rate which can be provided by the execution entity for the network slice to use;

or scheduling the air interface resources according to the maximum available bandwidth which can be provided by the execution entity for the network slice to use;

or scheduling the air interface resources according to the minimum guaranteed bandwidth reserved by the execution entity for the network slice.

11. The method of claim 10, wherein the step of scheduling the air interface resources according to the aggregate maximum bit rate available to the network slice by the execution entity comprises:

performing resource scheduling on all terminals which correspond to the execution entity and are communicated with the network slice according to the aggregation maximum bit rate which can be provided by the execution entity for the network slice to use;

12. The method of claim 10, wherein the step of scheduling air interface resources according to a maximum available bandwidth available to the network slice by the execution entity comprises:

performing resource scheduling on all terminals which correspond to the execution entity and are communicated with the network slice according to the maximum available bandwidth which can be provided by the execution entity for the network slice to use;

and the equivalent bandwidth of the scheduling resources obtained by all the terminals in an accumulated mode is smaller than or equal to the maximum available bandwidth which can be provided by the execution entity for the network slice to use.

13. The method of claim 10, wherein the step of scheduling air interface resources according to the minimum guaranteed bandwidth reserved by the execution entity for the network slice comprises:

according to the minimum guaranteed bandwidth reserved by the execution entity for the network slice, performing resource scheduling on all terminals which correspond to the execution entity and are communicated with the network slice;

and the equivalent bandwidth of the scheduling resource obtained by accumulation of all the terminals is greater than or equal to the minimum guaranteed bandwidth reserved by the execution entity for the network slice.

14. The method according to claim 11, 12 or 13, wherein the step of scheduling resources for all terminals corresponding to the performing entity and communicating with the network slice comprises:

and according to the time domain multiplexing mode and/or the frequency domain multiplexing mode, performing resource scheduling on all terminals which correspond to the execution entity and are communicated with the network slice.

15. The method according to claim 12 or 13, wherein before the step of controlling the resources used by the network slice according to the resource sharing configuration information of the network slice, the method further comprises, after the step of receiving the resource sharing configuration information of the network slice sent by the resource sharing configuration entity of the network slice:

by the formula B_{s_eq}＝M_s(T) × b (T) calculating the equivalent bandwidth of the scheduling resources cumulatively obtained by all terminals communicating with the network slice S;

wherein, B_{s_eq}Representing the equivalent bandwidth of the scheduling resources cumulatively obtained by all terminals communicating with said network slice S, B (T) representing the measurement period, M_s(T) represents the physical resource utilization of the network slice S,

M_s1(T) denotes the total number of physical layer resource blocks actually used by all terminals communicating with the network slice S during a measurement period, P_sAnd (T) represents the total number of physical layer resource blocks owned by the system in the measurement period.

16. The method according to claim 8, wherein the step of controlling the resources used by the network slice according to the resource sharing configuration information of the network slice comprises:

accumulating the total bit rate of all the bearers connected to the public data network PDN gateway and sent to the network slice;

detecting whether a total bit rate of all bearers connected to a PDN gateway addressed to the network slice is greater than an aggregated maximum bit rate available to the network slice by the enforcement entity;

if the total bit rate of all the bearers connected to the PDN gateway and addressed to the network slice is greater than the aggregated maximum bit rate that the execution entity can provide to the network slice for use, discarding the bearers satisfying a second preset condition;

wherein, the bearing meeting the second preset condition comprises: causing a total bit rate of all bearers connected to a PDN gateway destined for the network slice to be greater than a bearer for which the performing entity can provide an aggregated maximum bit rate available for use by the network slice.

17. An execution entity for performing resource sharing control in a network slice, the execution entity comprising:

the control module is used for controlling the resources used by the network slice according to the resource sharing configuration information of the network slice;

18. The execution entity of claim 17, wherein the execution entity further comprises:

a first sending module, configured to send a request message for requesting resource sharing configuration information to the resource sharing configuration entity.

19. The execution entity of claim 17, wherein the first receiving module is specifically configured to receive resource sharing configuration information of a network slice forwarded by a resource sharing configuration entity through a core network control node.

20. The execution entity of claim 17, wherein the execution entity further comprises:

and the updating module is used for updating the resource sharing configuration information.

21. The execution entity of claim 20, wherein the update module comprises:

a first updating submodule, configured to receive resource sharing configuration information of an updated network slice sent by the resource sharing configuration entity;

and the second updating submodule is used for updating the locally configured resource sharing configuration information according to the updated resource sharing configuration information of the network slice.

22. The execution entity of claim 21, wherein the execution entity further comprises:

a second sending module, configured to send a request message for requesting to update the resource sharing configuration information to the resource sharing configuration entity.

23. The enforcement entity of claim 17, wherein the control module is specifically configured to allocate resources unused by the network slice to other network slices of the enforcement entity when actual scheduled resources of all terminals corresponding to the enforcement entity and communicating with the network slice satisfy a first preset condition;

wherein the first preset condition comprises at least one of the following:

24. The execution entity of claim 17, wherein the minimum guaranteed resource comprises a minimum guaranteed bandwidth and the maximum available resource comprises a maximum available bandwidth and/or an aggregate maximum bit rate.

25. The entity according to claim 24, wherein the control module is specifically configured to, when the resource sharing configuration information of the network slice cannot match an actual network requirement, perform at least one of the following operations:

reducing a bit rate used by the network slice;

26. The execution entity of claim 24, wherein the control module comprises:

a first control sub-module, configured to schedule an air interface resource according to an aggregate maximum bit rate that the execution entity can provide for the network slice to use;

or the second control submodule is used for scheduling the air interface resources according to the maximum available bandwidth which can be provided by the execution entity for the network slice to use;

or a third control sub-module, configured to schedule the air interface resource according to the minimum guaranteed bandwidth reserved by the execution entity for the network slice.

27. The implementer of claim 26 wherein the first control submodule is configured to schedule resources for all terminals corresponding to the implementer and communicating with the network slice according to an aggregate maximum bit rate that the implementer can provide for the network slice to use;

28. The enforcement entity of claim 26, wherein the second control sub-module is specifically configured to perform resource scheduling on all terminals corresponding to the enforcement entity and communicating with the network slice according to a maximum available bandwidth available to the network slice by the enforcement entity;

29. The implementer of claim 26 wherein the third control sub-module is specifically configured to schedule resources for all terminals that correspond to the implementer and that communicate with the network slice according to a minimum guaranteed bandwidth reserved by the implementer for use by the network slice;

30. The execution entity according to claim 27, 28 or 29, wherein the execution entity comprises:

and the scheduling module is used for scheduling resources of all terminals which correspond to the execution entity and are communicated with the network slice according to a time domain multiplexing mode and/or a frequency domain multiplexing mode.

31. The execution entity according to claim 28 or 29, wherein the execution entity further comprises:

a calculation module for passing formula B_{s_eq}＝M_s(T) × b (T) calculating the equivalent bandwidth of the scheduling resources cumulatively obtained by all terminals communicating with the network slice S;

M_s1(T) denotes the total number of physical layer resource blocks actually used by all terminals communicating with the network slice S during a measurement period, P_s(T) represents the physical layer resources owned by the system during the measurement periodTotal number of blocks.

32. The execution entity of claim 24, wherein the control module comprises:

the fourth control submodule is used for accumulating the total bit rate of all the bearers connected to the public data network PDN gateway and sent to the network slice;

a fifth control sub-module, configured to detect whether a total bit rate of all bearers connected to a PDN gateway and addressed to the network slice is greater than an aggregated maximum bit rate that the execution entity can provide to the network slice for use, and trigger a sixth control sub-module if the total bit rate of all bearers connected to the PDN gateway and addressed to the network slice is greater than the aggregated maximum bit rate that the execution entity can provide to the network slice for use;

the sixth control submodule is used for discarding the load meeting a second preset condition according to the triggering of the fifth control submodule;

33. A resource sharing control method is applied to a resource sharing configuration entity of a network slice, and is characterized in that the method comprises the following steps:

sending the resource sharing configuration information of the network slice to the execution entity;

34. The method according to claim 33, wherein before the step of determining the resource sharing configuration information of the network slice corresponding to the execution entity performing the resource sharing control in the network slice, the method further comprises:

and receiving a request message which is sent by the execution entity and used for requesting the resource sharing configuration information.

35. The method of claim 33, wherein the step of sending the resource sharing configuration information of the network slice to the executing entity comprises:

and sending the resource sharing configuration information of the network slice to the execution entity through a core network control node.

36. The method of claim 33, wherein after the step of sending the resource sharing configuration information of the network slice to the performing entity, the method further comprises:

determining updated resource sharing configuration information of the network slice;

and sending the updated resource sharing configuration information of the network slice to the execution entity.

37. The method of claim 36, wherein before the step of determining resource sharing configuration information of the updated network slice, the method further comprises:

and receiving a request message which is sent by the execution entity and used for requesting to update the resource sharing configuration information.

38. The method according to claim 33, wherein the step of determining the resource sharing configuration information of the network slice corresponding to the execution entity performing the resource sharing control in the network slice comprises:

determining resource sharing configuration information of the network slice corresponding to the execution entity according to the signing data of the network slice;

wherein the resource sharing configuration information of the network slice on different execution entities is the same or different.

39. The method according to claim 33, wherein the step of determining the resource sharing configuration information of the network slice corresponding to the execution entity performing the resource sharing control in the network slice comprises:

and determining resource sharing configuration information of the network slice corresponding to the execution entity according to the position information and/or the time information of the execution entity.

40. A resource sharing configuration entity of a network slice, the resource sharing configuration entity comprising:

a third sending module, configured to send the resource sharing configuration information of the network slice to the execution entity;

41. The resource sharing configuration entity according to claim 40, wherein the resource sharing configuration entity further comprises:

a second receiving module, configured to receive a request message sent by the execution entity and used for requesting resource sharing configuration information.

42. The resource sharing configuration entity of claim 40, wherein the third sending module is specifically configured to send the resource sharing configuration information of the network slice to the execution entity through a core network control node.

43. The resource sharing configuration entity according to claim 40, wherein the resource sharing configuration entity further comprises:

a second determining module, configured to determine resource sharing configuration information of the updated network slice;

and the fourth sending module is used for sending the updated resource sharing configuration information of the network slice to the execution entity.

44. The resource sharing configuration entity according to claim 43, wherein the resource sharing configuration entity further comprises:

a third receiving module, configured to receive a request message sent by the execution entity and used to request to update the resource sharing configuration information.

45. The resource sharing configuration entity according to claim 40, wherein the first determining module is specifically configured to determine, according to subscription data of a network slice, resource sharing configuration information of the network slice corresponding to the execution entity;

46. The resource sharing configuration entity of claim 40, wherein the first determining module is specifically configured to determine the resource sharing configuration information of the network slice corresponding to the execution entity according to the location information and/or the time information of the execution entity.