CN112822719A - Network slice scheduling method and congestion scheduling system - Google Patents
Network slice scheduling method and congestion scheduling system Download PDFInfo
- Publication number
- CN112822719A CN112822719A CN202110039280.7A CN202110039280A CN112822719A CN 112822719 A CN112822719 A CN 112822719A CN 202110039280 A CN202110039280 A CN 202110039280A CN 112822719 A CN112822719 A CN 112822719A
- Authority
- CN
- China
- Prior art keywords
- slice
- overflow
- congestion
- users
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0289—Congestion control
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a network slice scheduling method, which comprises the following steps: determining whether slice congestion occurs based on the number of current access users and the maximum subscription number; under the condition that the slice congestion is determined, sending an overflow user request to a slice management system; determining current overflow users based on the current access users and the maximum subscription number; and switching the service connection of the current overflow user to the idle slice based on the overflow feedback message returned by the slice management system. The method can improve the flexibility of slice resource scheduling, avoid slice network congestion and improve user experience. The application also discloses a congestion scheduling system.
Description
Technical Field
The invention relates to the technical field of communication, in particular to a network slice scheduling method and a congestion scheduling system.
Background
The network slice is a logical network characterized by end-to-end, customized and isolated according to needs, and can provide differentiated network services for different services or user groups through flexible design of functions, performance, connection relation, operation and maintenance and the like. Wherein, end-to-end means that the network slice not only needs a core network, but also needs an access network, a transmission network, a management network and the like; the on-demand customization means that the service, function, capacity, service quality and connection relation of the network slice can be customized as required, and meanwhile, the life cycle management of the slice can be carried out as required; the isolation includes security isolation, resource isolation, operation maintenance isolation and the like.
Network slicing improves the experience of operator network deployment and user usage, and introduces more complex service operation problems. The automation of ordering, arranging and deploying of 5G Network end-to-end slices is realized through CSMF (Communication Service Management Function), NSMF (Network Slice Management Function), NSSMF (Network Slice Management Function) and MANO (Management and organization). The tenants order the network slices through the CSMF and submit related requirements, such as the number of online users, network bandwidth, time delay and the like. The NSMF is responsible for converting the CSMF requirements into SLAs (Service Level Agents) required by the slices, and decomposing the CSMF requirements into the requirements of each sub-slice. NSSMF is responsible for the orchestration and deployment of subnets, deployed through MANOs.
Under the mechanism, when a tenant orders a slice, the number of users that the slice can access is limited to ensure that the SLA index of the slice network meets the requirements of the tenant, so that more users are not facilitated to enjoy the services of the slice network. For example, for B2C service, an operator proposes an online video slicing service in conjunction with an internet video APP, and provides a 5G eMBB (Enhanced Mobile Broadband) large-bandwidth smooth download service product. When the service has obvious positive market feedback, the subscription amount of the user exceeds the expectation (the number of users exceeding the slice setting), or in the early stage of product promotion, the operator hopes to lead more users who actively try to subscribe to access the slice experience so as to cultivate potential slice tenant groups.
However, current slice management mechanisms are not suitable for more flexible resource scheduling configurations to meet the variety of business scenarios that may occur in the future.
Disclosure of Invention
Therefore, the invention provides a network slice scheduling method and a congestion scheduling system, which aim to solve the problem that in the prior art, a slice management mechanism is not suitable for more flexible resource scheduling configuration, so that the slice management mechanism is not suitable for popularization and application.
In order to achieve the above object, a first aspect of the present invention provides a network slice scheduling method, including:
determining whether slice congestion occurs based on the number of current access users and the maximum subscription number;
sending an overflow user request to a slice management system under the condition that the slice congestion is determined to occur;
determining current overflow users based on the current access users and the maximum subscription number;
and switching the service connection of the current overflow user to an idle slice based on the overflow feedback message returned by the slice management system.
Wherein the determining whether slice congestion occurs before based on the current number of access users and the maximum number of subscriptions comprises:
and periodically acquiring the number of the current access users monitored by the slice management system.
Wherein, after determining whether slice congestion occurs based on the number of current access users and the maximum subscription number, the method further comprises:
in case it is determined that the slicing congestion does not occur, it is continuously determined whether the slicing congestion occurs based on the number of current access users and the maximum number of subscriptions.
The overflow user request is used for obtaining an overflow user identifier, a service connection identifier corresponding to the overflow user identifier and an idle switching identifier with the same service type as the overflow user identifier.
Wherein, after the switching the service connection of the current overflow user to an idle slice based on the overflow feedback message returned by the slice management system, the method further comprises:
and under the condition that the slice congestion is still determined based on the number of the current access users and the maximum subscription number, switching the overflow users with the previous slice congestion to the original slices, and reselecting the overflow users.
Wherein, under the condition that slice congestion is still determined based on the number of the current access users and the maximum subscription number, after the overflow users with the previous slice congestion are switched to the original slice, the method further comprises the following steps:
and continuing to determine whether slice congestion occurs based on the number of the current access users and the maximum subscription number.
The maximum subscription number refers to the maximum limit number of users configured by the service level agreement at the time of subscription.
An embodiment of the present application further provides a congestion scheduling system, including:
the judging module is used for determining whether slice congestion occurs or not based on the number of the current access users and the maximum order number;
a user access control module, configured to control the slice accessed by the currently accessed user, where the user access control module includes:
a sending unit, configured to send an overflow user request to a slice management system when it is determined that the slice congestion occurs;
a determining unit, configured to determine a current overflow user based on the current access user and the maximum subscription number;
and the switching unit is used for switching the service connection of the current overflow user to an idle slice based on the overflow feedback message returned by the slice management system.
The user access control module is further configured to switch the overflow user with the previous slice congestion to the original slice under the condition that it is determined that the slice congestion still occurs based on the number of the current access users and the maximum subscription number.
Wherein, still include:
and the acquisition module is used for periodically acquiring the number of the current access users monitored by the slice management system.
The invention has the following advantages:
according to the network slice scheduling method provided by the invention, under the condition that the congestion of the slices is determined based on the number of the current access users and the maximum order number, an overflow user request is sent to the slice management system, and the service connection of the current overflow user is switched to the idle slice based on the overflow feedback message returned by the slice management system, so that the flexibility of slice resource scheduling is improved, the network congestion of the slices is avoided, and the user experience is improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention.
Fig. 1 is an architecture diagram of a slice management system and a congestion scheduling system provided in an embodiment of the present application;
fig. 2 is a flowchart of a network slice scheduling method according to an embodiment of the present application;
fig. 3 is a flowchart of another network slice scheduling method provided in an embodiment of the present application;
fig. 4 is a schematic block diagram of a congestion scheduling system according to an embodiment of the present application.
Detailed Description
The following detailed description of embodiments of the invention refers to the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the present invention, are given by way of illustration and explanation only, not limitation.
When a tenant subscribes a network slice, the number of accessed users is usually limited to ensure that the SLA (Service-Level agent) index of the slice network meets the requirements of the tenant. Although limiting the number of users of the slice network may improve the quality of service, it is not conducive to fostering potential users due to the inflexibility of the slice management mechanism. For example, in the early stage of product promotion, an operator may want more users to actively try subscription, however, the number of subscribed users is limited due to the limitation of the number of subscriptions.
The network slice scheduling method provided by the embodiment of the application is implemented based on a slice management system and a congestion scheduling system. Fig. 1 is an architecture diagram of a slice management system and a congestion scheduling system according to an embodiment of the present application. Referring to fig. 1, a slice management system 10 includes a slice creation module 11, a slice execution module 12, and a slice update module 13, where the slice creation module 11 is configured to create a slice, the slice execution module 12 is configured to manage execution of the slice, and the slice update module 13 is configured to update the slice. Congestion scheduling system 20 schedules access users and slices.
The embodiment provides a network slice scheduling method, which can be applied to a congestion scheduling system and used for scheduling a slice network so as to avoid congestion of the slice network.
Fig. 2 is a flowchart of a network slice scheduling method according to an embodiment of the present application. As shown in fig. 2, the network slice scheduling method includes:
The number of currently accessed users refers to the number of users currently accessed in a slice. The maximum subscription number is the number of the largest access users that the tenant subscribes to in the slice network. For example, the maximum number of subscriptions refers to the maximum number of restrictions on the number of users configured by the service level agreement at the time of subscription.
In some embodiments, when the number of users accessed by the current slice exceeds the maximum subscription number, it is determined that the current slice is congested. And if the number of the users accessed to the current slice is less than or equal to the maximum subscription number, determining that the current slice is not congested.
In some embodiments, upon determining that a slice network is congested with slices, the congestion scheduling system issues an overflow user request to the slice management system. The overflow user request is used to obtain more slices to the slice management system.
And after receiving the overflow user request, the slice management system returns an overflow user identifier, a service connection identifier corresponding to the overflow user identifier and an idle switching identifier with the same service type as the overflow user identifier to the congestion scheduling system. The overflow user identifier refers to an identifier corresponding to an access user exceeding the maximum subscription number subscribed by the tenant. The service connection identifier refers to a connection identifier of a service type corresponding to the overflow user identifier. The service types include, but are not limited to, eMBB (Enhanced mobile Broadband), urrllc (Ultra-reliable and Low Latency Communication), mtc (Massive machine type Communication). The subdivision service types include but are not limited to video types, Internet of vehicles types and meter reading types; the application service type includes, but is not limited to, app id (application id), FQDN (full qualified Domain Name), IP (Internet Protocol Address) Address triplet, and the like. The idle handoff identification is an identification of the slice in an idle state provided by the slice management system.
In some embodiments, the slice management system randomly or periodically selects the overflow user identifier and the service connection identifier corresponding to the overflow user identifier to return to the congestion scheduling system.
And after the number of the currently accessed users is larger than the maximum subscription number, the access users exceeding the maximum subscription number are overflow users.
In some embodiments, the overflow users are determined by the time the access user accesses the slice. For example, the access users are sorted according to the time sequence, in the sorting result, the access users which are sorted in the front and are consistent with the maximum subscription number are normal users, and the access users which are sorted in the back and exceed the maximum subscription number are overflow users. In other words, the access subscribers before the value are normal subscribers and the access subscribers after the value are overflow subscribers, with the maximum number of subscriptions as the boundary.
In some embodiments, the spillover user is randomly selected from among the access users.
And step 204, switching the service connection of the current overflow user to an idle slice based on the overflow feedback message returned by the slice management system.
The overflow feedback message comprises an overflow user identifier, a service connection identifier corresponding to the overflow user identifier and an idle switching identifier with the same service type as the overflow user identifier.
And after receiving the overflow feedback message returned by the slice management system, the congestion scheduling system switches the overflow user to an idle slice based on the overflow user identifier, the service connection identifier corresponding to the overflow user identifier and the idle switching identifier with the same service type as the overflow user, wherein the idle slice is the slice corresponding to the idle switching identifier.
In some embodiments, before determining whether slice congestion occurs based on the current number of access users and the maximum number of subscriptions in step 201, the method further includes: and periodically acquiring the number of current access users monitored by the slice management system.
The slice management system monitors current access users of the access slices and counts the number of the current access users, the congestion scheduling system periodically obtains the number of the current access users, and then whether slice congestion occurs or not is determined based on the number of the current access users and the maximum subscription number.
In some embodiments, after determining whether slice congestion occurs based on the number of current access users and the maximum subscription number in step 201, the method further includes:
in case it is determined that no slicing congestion occurs, step 201 is performed, i.e. it is determined whether slicing congestion occurs based on the number of current access users and the maximum subscription number.
In some embodiments, after switching the traffic connection of the current overflow user to the idle slice based on the overflow feedback message returned by the slice management system in step 204, the method further includes:
and under the condition that the slice congestion still occurs based on the number of the current access users and the maximum subscription number, switching the overflow users with the slice congestion in the previous batch to the original slice.
In this embodiment, after obtaining the idle slice of the overflow user from the slice management system, the congestion scheduling system switches the overflow user of the current batch to the idle slice. Wherein, the current batch refers to the current cycle. The congestion scheduling system periodically reads the slice current access users. The previous overflow user is a previous batch overflow user, which is relative to the overflow user of the current batch.
Fig. 3 is a flowchart of another network slice scheduling method according to an embodiment of the present application. As shown in fig. 3, the network slice scheduling method includes:
The number of currently accessed users refers to the number of users currently accessed in a slice. The maximum subscription number is the number of the largest access users that the tenant subscribes to in the slice network. For example, the maximum number of subscriptions refers to the maximum number of restrictions on the number of users configured by the service level agreement at the time of subscription.
In some embodiments, when the number of users accessed by the current slice exceeds the maximum subscription number, it is determined that the current slice is congested. And if the number of the users accessed to the current slice is less than or equal to the maximum subscription number, determining that the current slice is not congested.
In some embodiments, upon determining that a slice network is congested with slices, the congestion scheduling system issues an overflow user request to the slice management system. The overflow user request is used to obtain more slices to the slice management system.
And after receiving the overflow user request, the slice management system returns an overflow user identifier, a service connection identifier corresponding to the overflow user identifier and an idle switching identifier with the same service type as the overflow user identifier to the congestion scheduling system. The overflow user identifier refers to an identifier corresponding to an access user exceeding the maximum subscription number subscribed by the tenant. The service connection identifier refers to a connection identifier of a service type corresponding to the overflow user identifier. The idle handoff identification is an identification of the slice in an idle state provided by the slice management system.
In some embodiments, the slice management system randomly or periodically selects the overflow user identifier and the service connection identifier corresponding to the overflow user identifier to return to the congestion scheduling system.
And after the number of the currently accessed users is larger than the maximum subscription number, the access users exceeding the maximum subscription number are overflow users.
In some embodiments, the overflow users are determined by the time the access user accesses the slice. For example, the access users are sorted according to the time sequence, in the sorting result, the access users which are sorted in the front and are consistent with the maximum subscription number are normal users, and the access users which are sorted in the back and exceed the maximum subscription number are overflow users. In other words, the access subscribers before the value are normal subscribers and the access subscribers after the value are overflow subscribers, with the maximum number of subscriptions as the boundary.
In some embodiments, the spillover user is randomly selected from the access users.
The overflow feedback message comprises an overflow user identifier, a service connection identifier corresponding to the overflow user identifier and an idle switching identifier with the same service type as the overflow user identifier.
And after receiving the overflow feedback message returned by the slice management system, the congestion scheduling system switches the overflow user to an idle slice based on the overflow user identifier, the service connection identifier corresponding to the overflow user identifier and the idle switching identifier with the same service type as the overflow user, wherein the idle slice is the slice corresponding to the idle switching identifier.
And 305, under the condition that the slice congestion is still determined to occur based on the number of the current access users and the maximum subscription number, switching the overflow users with the previous slice congestion to the original slice, and reselecting the overflow users.
In this embodiment, after obtaining the idle slice from the slice management system, the congestion scheduling system switches the current overflow user to the idle slice. The current overflow user refers to the overflow user in the current period. The congestion scheduling system periodically reads the slice current access users.
In the present embodiment, after step 305, step 301 to step 305 are continued.
According to the network slice scheduling method provided by the embodiment of the invention, under the condition that the congestion of the slices is determined based on the number of the current access users and the maximum order number, an overflow user request is sent to the slice management system, and the service connection of the current overflow user is switched to the idle slice based on the overflow feedback message returned by the slice management system, so that the flexibility of slice resource scheduling is improved, the network congestion of the slices is avoided, and the user experience is improved.
The embodiment of the application also provides a congestion scheduling system, which is used for scheduling the slice network so as to avoid congestion of the slice network.
Fig. 4 is a schematic block diagram of a congestion scheduling system according to an embodiment of the present application. As shown in fig. 4, the congestion scheduling system 400 includes:
a determining module 401, configured to determine whether slice congestion occurs based on the number of current access users and the maximum subscription number.
The number of currently accessed users refers to the number of users currently accessed in a slice. The maximum subscription number is the number of the largest access users that the tenant subscribes to in the slice network. For example, the maximum number of subscriptions refers to the maximum number of restrictions on the number of users configured by the service level agreement at the time of subscription.
In some embodiments, when the number of users accessed by the current slice exceeds the maximum subscription number, it is determined that the current slice is congested. And if the number of the users accessed to the current slice is less than or equal to the maximum subscription number, determining that the current slice is not congested.
A user access control module 402, configured to control the slice accessed by the currently accessed user.
In some embodiments, the user access control module 402 includes:
a sending unit 41, configured to issue an overflow user request to the slice management system in a case where it is determined that the slice congestion occurs.
In some embodiments, upon determining that a slice network is congested with slices, the congestion scheduling system issues an overflow user request to the slice management system. The overflow user request is used to obtain more slices to the slice management system.
And after receiving the overflow user request, the slice management system returns an overflow user identifier, a service connection identifier corresponding to the overflow user identifier and an idle switching identifier with the same service type as the overflow user identifier to the congestion scheduling system. The overflow user identifier refers to an identifier corresponding to an access user exceeding the maximum subscription number subscribed by the tenant. The service connection identifier refers to a connection identifier of a service type corresponding to the overflow user identifier. The service types include, but are not limited to, eMBB (Enhanced mobile Broadband), urrllc (Ultra-reliable and Low Latency Communication), mtc (Massive machine type Communication). The subdivision service types include but are not limited to video types, Internet of vehicles types and meter reading types; the application service type includes, but is not limited to, app id (application id), FQDN (full qualified Domain Name), IP (Internet Protocol Address) Address triplet, and the like. The idle handoff identification is an identification of the slice in an idle state provided by the slice management system.
In some embodiments, the slice management system randomly or periodically selects the overflow user identifier and the service connection identifier corresponding to the overflow user identifier to return to the congestion scheduling system.
A determining unit 42, configured to determine a current overflow user based on the current access user and the maximum subscription number.
And after the number of the currently accessed users is larger than the maximum subscription number, the access users exceeding the maximum subscription number are overflow users.
In some embodiments, the overflow users are determined by the time the access user accesses the slice. For example, the access users are sorted according to the time sequence, in the sorting result, the access users which are sorted in the front and are consistent with the maximum subscription number are normal users, and the access users which are sorted in the back and exceed the maximum subscription number are overflow users. In other words, the access subscribers before the value are normal subscribers and the access subscribers after the value are overflow subscribers, with the maximum number of subscriptions as the boundary.
In some embodiments, the spillover user is randomly selected from among the access users.
A switching unit 43, configured to switch the service connection of the current overflow user to an idle slice based on the overflow feedback message returned by the slice management system.
The overflow feedback message comprises an overflow user identifier, a service connection identifier corresponding to the overflow user identifier and an idle switching identifier with the same service type as the overflow user identifier.
And after receiving the overflow feedback message returned by the slice management system, the congestion scheduling system switches the overflow user to an idle slice based on the overflow user identifier, the service connection identifier corresponding to the overflow user identifier and the idle switching identifier with the same service type as the overflow user, wherein the idle slice is the slice corresponding to the idle switching identifier.
In some embodiments, the user access control module 402 is further configured to switch the overflow user with the previous slice congestion to the original slice in the case that it is determined that the slice congestion still occurs based on the number of the current access users and the maximum subscription number.
In this embodiment, after obtaining the idle slice of the overflow user from the slice management system, the congestion scheduling system switches the overflow user of the current batch to the idle slice. Wherein, the current batch refers to the current cycle. The congestion scheduling system periodically reads the slice current access users. The previous overflow user is a previous batch overflow user, which is relative to the overflow user of the current batch.
In some embodiments, the congestion scheduling system further comprises:
and the acquisition module is used for periodically acquiring the number of the current access users monitored by the slice management system.
According to the congestion scheduling system provided by the embodiment of the application, under the condition that the judgment module determines that the slice is congested, the user access control module sends an overflow user request to the slice management system, and the overflow feedback message returned by the slice management system switches the current service connection of the overflow user to an idle slice, so that the flexibility of slice resource scheduling is improved, the network congestion of the slice is avoided, and the user experience is improved.
It will be understood that the above embodiments are merely exemplary embodiments taken to illustrate the principles of the present invention, which is not limited thereto. It will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the spirit and substance of the invention, and these modifications and improvements are also considered to be within the scope of the invention.
Claims (10)
1. A network slice scheduling method, comprising:
determining whether slice congestion occurs based on the number of current access users and the maximum subscription number;
sending an overflow user request to a slice management system under the condition that the slice congestion is determined to occur;
determining current overflow users based on the current access users and the maximum subscription number;
and switching the service connection of the current overflow user to an idle slice based on the overflow feedback message returned by the slice management system.
2. The method of claim 1, wherein determining whether slice congestion occurs before based on the current number of access users and the maximum number of subscriptions comprises:
and periodically acquiring the number of the current access users monitored by the slice management system.
3. The method of claim 1, wherein after determining whether slice congestion occurs based on the number of current access users and the maximum subscription number, further comprising:
in case it is determined that the slicing congestion does not occur, it is continuously determined whether the slicing congestion occurs based on the number of current access users and the maximum number of subscriptions.
4. The method of claim 1, wherein the overflow user request is used to obtain an overflow user identifier, a service connection identifier corresponding to the overflow user identifier, and an idle handoff identifier having the same service type as the overflow user identifier.
5. The method of claim 1, wherein after switching the traffic connection of the current overflow user to an idle slice based on the overflow feedback message returned by the slice management system, the method further comprises:
and under the condition that the slice congestion is still determined based on the number of the current access users and the maximum subscription number, switching the overflow users with the previous slice congestion to the original slices, and reselecting the overflow users.
6. The method of claim 5, wherein in the case that it is still determined that the slice congestion is caused based on the number of current access users and the maximum subscription number, after switching the overflow users with the previous slice congestion to the original slice, further comprising:
and continuing to determine whether slice congestion occurs based on the number of the current access users and the maximum subscription number.
7. The method according to any of claims 1-6, wherein the maximum number of subscriptions refers to the maximum number of users configured by the service level agreement at the time of subscription.
8. A congestion scheduling system, comprising:
the judging module is used for determining whether slice congestion occurs or not based on the number of the current access users and the maximum order number;
a user access control module, configured to control the slice accessed by the currently accessed user, where the user access control module includes:
a sending unit, configured to send an overflow user request to a slice management system when it is determined that the slice congestion occurs;
a determining unit, configured to determine a current overflow user based on the current access user and the maximum subscription number;
and the switching unit is used for switching the service connection of the current overflow user to an idle slice based on the overflow feedback message returned by the slice management system.
9. The congestion scheduling system of claim 8, wherein the user access control module is further configured to switch the overflowing user with the previous slice congestion to an original slice if it is determined that the slice congestion still occurs based on the number of current access users and the maximum subscription number.
10. The congestion scheduling system of claim 8, further comprising:
and the acquisition module is used for periodically acquiring the number of the current access users monitored by the slice management system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110039280.7A CN112822719B (en) | 2021-01-12 | 2021-01-12 | Network slice scheduling method and congestion scheduling system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110039280.7A CN112822719B (en) | 2021-01-12 | 2021-01-12 | Network slice scheduling method and congestion scheduling system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112822719A true CN112822719A (en) | 2021-05-18 |
| CN112822719B CN112822719B (en) | 2023-02-24 |
Family
ID=75868954
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110039280.7A Active CN112822719B (en) | 2021-01-12 | 2021-01-12 | Network slice scheduling method and congestion scheduling system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112822719B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114531662A (en) * | 2022-04-20 | 2022-05-24 | 国网浙江省电力有限公司信息通信分公司 | Terminal intelligent access authentication management method based on electric power 5G virtual private network |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106549806A (en) * | 2016-10-26 | 2017-03-29 | 清华大学 | A kind of network section manager and its management method |
| CN107580360A (en) * | 2016-07-04 | 2018-01-12 | 中国移动通信有限公司研究院 | A kind of network is cut into slices method, equipment and the network architecture of selection |
| WO2018131413A1 (en) * | 2017-01-10 | 2018-07-19 | 株式会社Ｎｔｔドコモ | Mobile communication system and congestion control method |
| CN109120426A (en) * | 2017-06-26 | 2019-01-01 | 中兴通讯股份有限公司 | A kind of network slice management method, device and computer readable storage medium |
| WO2019064542A1 (en) * | 2017-09-29 | 2019-04-04 | 富士通株式会社 | Communication system, base station device, terminal device, and communication method |
| US20200137621A1 (en) * | 2018-10-29 | 2020-04-30 | Verizon Patent And Licensing Inc. | Method and system for admission control with network slice capability |
| WO2020251435A1 (en) * | 2019-06-12 | 2020-12-17 | Telefonaktiebolaget Lm Ericsson (Publ) | User prioritization during congestion based on mobile money revenue information |
-
2021
- 2021-01-12 CN CN202110039280.7A patent/CN112822719B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107580360A (en) * | 2016-07-04 | 2018-01-12 | 中国移动通信有限公司研究院 | A kind of network is cut into slices method, equipment and the network architecture of selection |
| CN106549806A (en) * | 2016-10-26 | 2017-03-29 | 清华大学 | A kind of network section manager and its management method |
| WO2018131413A1 (en) * | 2017-01-10 | 2018-07-19 | 株式会社Ｎｔｔドコモ | Mobile communication system and congestion control method |
| CN109120426A (en) * | 2017-06-26 | 2019-01-01 | 中兴通讯股份有限公司 | A kind of network slice management method, device and computer readable storage medium |
| WO2019064542A1 (en) * | 2017-09-29 | 2019-04-04 | 富士通株式会社 | Communication system, base station device, terminal device, and communication method |
| US20200137621A1 (en) * | 2018-10-29 | 2020-04-30 | Verizon Patent And Licensing Inc. | Method and system for admission control with network slice capability |
| WO2020251435A1 (en) * | 2019-06-12 | 2020-12-17 | Telefonaktiebolaget Lm Ericsson (Publ) | User prioritization during congestion based on mobile money revenue information |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114531662A (en) * | 2022-04-20 | 2022-05-24 | 国网浙江省电力有限公司信息通信分公司 | Terminal intelligent access authentication management method based on electric power 5G virtual private network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112822719B (en) | 2023-02-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109600768B (en) | Method, device and system for managing network slices | |
| US20220103443A1 (en) | Methods and devices for operation of a network data analytics function | |
| EP3955523A1 (en) | Network analysis component and method for providing network analysis and/or prediction information about network slice instances of a mobile communication network | |
| EP3163843A1 (en) | Method and device for providing network service, evaluating policy rule and selecting service assembly | |
| CN110326345B (en) | Method, device and system for configuring network slice | |
| CN111512652A (en) | Method, network function entity and computer readable medium for data collection | |
| CN111903094B (en) | Quota management in Session Management Function (SMF) for online charging | |
| CN114615154B (en) | Method and device for managing service quality and communication system | |
| US20220405153A1 (en) | Report application programming interface (api) capability change based on api filter | |
| EP2086173A1 (en) | A method, system and network device for resource management | |
| CN109391498B (en) | Management method of network component and network equipment | |
| CN1732667A (en) | Transmission of application information and commands using presence technology | |
| JP2009135916A (en) | Method and system for managing information | |
| CN112822719B (en) | Network slice scheduling method and congestion scheduling system | |
| CN113573332A (en) | Information processing method, device, equipment and readable storage medium | |
| EP1589706A1 (en) | Control of multicast traffic | |
| CN110087105B (en) | Method and device for switching IPTV multicast to unicast | |
| CN116491169A (en) | Implementing service level agreements in identity federation | |
| CN113453252A (en) | Communication method and device | |
| CN114079999A (en) | Communication control method, network element and storage medium | |
| CN112492660B (en) | Network switching method, management platform and gateway | |
| EP4245062A1 (en) | First node, third node, and methods performed thereby, for handling quality of service in a communications network | |
| CN117204043A (en) | Apparatus and method for network slice admission control | |
| CN115865686A (en) | Channel management method, device, equipment, system and storage medium | |
| CN117223268A (en) | Communication network arrangement and method providing a machine learning model for performing a communication network analysis |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |