Method and apparatus for management of network slices based on cloud control platform

Abstract

The application relates to a method and device for managing network slices based on a cloud control platform, wherein the cloud control platform allocates cloud cards meeting corresponding network slice demand information to each terminal device, so as to meet the requirement of quickly replacing network slice resources for the terminal device, to meet different network requirements of the device in different application scenarios, and to have strong executability and be capable of adaptive processing of bursty services; and the cloud cards of different network slice resources are arranged in the cloud control platform, the cloud control platform can match corresponding cloud cards according to trigger information sent by the terminal device and allocate the cloud cards to the terminal device; the design can effectively improve the utilization rate of overall network resources and the success rate and accuracy of network slice resource replacement; and the application can effectively guarantee more rational use of resources, convenient operation and better use experience of users.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a method and apparatus for managing network slices based on a cloud control platform. Background Technology

[0002] Fifth-generation mobile communication technology (5G) is a new generation of broadband mobile communication technology characterized by high speed, low latency, and massive connectivity. 5G communication infrastructure serves as the network infrastructure for realizing the interconnection of humans, machines, and things. 5G technology supports three main application scenarios: enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (uRLLC), and massive machine-type communications (mMTC). eMBB, uRLLC, and mMTC can provide different services in different application scenarios. They complement each other, collectively forming the comprehensive capabilities of the 5G network to meet diverse application needs and jointly drive the development and application of 5G technology.

[0003] To better provide network services, network slicing technology is employed to meet diverse service needs and offer customized, flexible network services for different application scenarios. As the next-generation mobile communication network, 5G networks rely heavily on network slicing technology. Network slicing technology can divide the same hardware infrastructure into multiple virtual networks, enabling on-demand resource allocation and flexible capability combination, thereby precisely meeting the diverse needs of various services. Existing technologies define corresponding network slice types for the aforementioned application scenarios: eMBB slices, mMTC slices, and uRLLC slices, to meet the requirements of different application scenarios.

[0004] In the past, to meet the usage requirements of relevant application scenarios, devices typically used firmware flashing or built-in SIM cards that were strongly bound to the slice type to configure the corresponding network slice. However, these solutions have the following drawbacks:

[0005] Firmware flashing mode: In this mode, firmware of a specific network slice type is pre-flashed at the factory to meet relevant Internet access requirements. It can flash a single network slice type or multiple network slice types. However, the application scope of flashing a single network slice type is small and the flexibility of use is poor. If the product is customized for different slices, the number of versions and workload will increase several times, resulting in low overall network resource utilization and increased version control costs and risks. At the same time, this firmware flashing mode has problems such as poor flexibility, firmware upgrades require returning to the factory for re-flashing, inability to adapt to sudden business scenarios, long return time, and poor operability.

[0006] SIM Card and Slice Type Binding Mode: This mode primarily categorizes devices based on different physical cards (such as URLLC cards and eMBB cards). Specifically, it customizes dedicated SIM cards for different slice type devices, then inserts the corresponding SIM card into the device. For detailed setup instructions, please refer to [link / reference]. Figure 1 As shown, Figure 1 As shown, in this mode, the corresponding SIM card type can be inserted manually. This method requires pre-installation of multiple SIM card types, which increases costs, and manual card replacement is prone to errors.

[0007] In addition, existing technologies also employ a passive monitoring method on the operator side to switch network slice types. The identification mechanism is based on the IMSI (International Mobile Subscriber Identity) number segment or APN (Access Network Protocol) configuration to identify the device type, and the switching is triggered by manually adjusting the slice policy through the core network management system. This method still relies on manual policy configuration for switching, which results in low monitoring efficiency and low success rate of switching in emergency scenarios. Furthermore, in order to be compatible with multiple scenarios, all slices need to be pre-activated, resulting in low resource utilization. Idle slices cannot be dynamically released, leading to low overall network resource utilization. Summary of the Invention

[0008] In view of the above-mentioned deficiencies of the prior art, the present invention provides a method and apparatus for managing network slices based on a cloud control platform, which has fast switching speed, better cross-scenario adaptability of devices, good flexibility, higher resource utilization, effectively reduces manual operation and maintenance costs, and has a wide range of applications.

[0009] In a first aspect, the present invention provides a method for managing network slices based on a cloud control platform, characterized in that it includes:

[0010] In response to the triggering information sent by the terminal device, determine the network slicing requirement information of the terminal device corresponding to the triggering information;

[0011] Match a corresponding cloud card to be allocated to the terminal device. The cloud card to be allocated must at least meet the following requirements: the cloud card to be allocated includes network slice resources that match the network slice requirement information.

[0012] The matched cloud cards to be allocated form user identification cards to be used, which are then sent to the terminal devices.

[0013] The terminal device activates the user identification card to be used.

[0014] The method for managing network slices based on the cloud control platform further includes:

[0015] The triggering information includes the device identification information of the terminal device, real-time registration network information, and real-time signal status information.

[0016] The network slicing requirement information is determined based on the device identification information, real-time registered network information, and real-time signal status information of the terminal device.

[0017] The method for managing network slices based on the cloud control platform further includes:

[0018] When the triggering information includes network slicing instruction information, the network slicing requirement information is determined based on the network slicing instruction information; when the triggering information does not include the network slicing instruction information, the network slicing requirement information is determined based on the device identification information, real-time registered network information, and real-time signal status information of the terminal device.

[0019] The network slicing instruction information includes at least one of the following trigger signals generated according to the instruction: a switching eMBB network slice trigger signal, a switching mMTC network slice trigger signal, and a switching URLLC network slice trigger signal.

[0020] When determining the network slicing requirement information based on the device identification information, real-time registered network information, and real-time signal status information of the terminal device, the method further includes the following operations:

[0021] Perform a slice requirement detection operation, which includes: detecting the real-time registered network information and real-time signal status information, and determining the network slice required by the terminal device;

[0022] If the real-time registered network information and real-time signal status information meet the first triggering condition preset by the system, then the network slice required by the terminal device is determined to be an eMBB network slice, so as to generate the corresponding network slice requirement information and return the above slice requirement detection operation.

[0023] If the real-time registered network information and real-time signal status information meet the second triggering condition preset by the system, then the network slice required by the terminal device is determined to be an mMTC network slice, so as to generate the corresponding network slice requirement information and return the above slice requirement detection operation.

[0024] If the real-time registered network information and real-time signal status information meet the third triggering condition preset by the system, then the network slice required by the terminal device is determined to be a URLLC network slice, so as to generate the corresponding network slice requirement information and return the above slice requirement detection operation.

[0025] The method for managing network slices based on the cloud control platform further includes:

[0026] In response to the triggering information sent by the terminal device, determine the location information of the terminal device corresponding to the triggering information;

[0027] The cloud card to be assigned must also meet the following requirement: the preset coverage area of ​​the cloud card to be assigned must cover the area corresponding to the location information of the terminal device.

[0028] The triggering information also includes the expected tariff information of the terminal device;

[0029] The cloud card to be allocated must also meet the following requirement: the tariff of the cloud card to be allocated must match the expected tariff information of the terminal device.

[0030] The method for managing network slices based on the cloud control platform further includes:

[0031] Based on the correspondence between preset device identification information and initial network slicing requirement information, the initial network slicing requirement information of the terminal device is determined according to the device identification information of the terminal device in the trigger information.

[0032] The device identification information includes at least one of the device SN number or IMEI number.

[0033] The method for managing network slices based on the cloud control platform further includes:

[0034] Detect whether the terminal device includes a user identification card corresponding to the network slicing requirement information;

[0035] If the terminal device does not contain a user identification card corresponding to the network slice requirement information, the triggering information is sent to the operation and control platform to request the allocation of a user identification card to be used; if the terminal device contains a user identification card corresponding to the network slice requirement information, the user identification card contained in the terminal device corresponding to the network slice requirement information is used to form the user identification card to be used.

[0036] The method for managing network slices based on the cloud control platform further includes:

[0037] When the idle time of the user identification card (UIC) consisting of cloud cards in the terminal device exceeds a preset idle threshold period, the cloud card that has exceeded the preset idle threshold period is either released as a resource or the UIC in the terminal device is replaced based on the system's preset replacement logic.

[0038] Secondly, the present invention also provides a method for allocating network slices, the main feature of which is that it includes:

[0039] In response to the triggering information sent by the terminal device, determine the network slicing requirement information of the terminal device corresponding to the triggering information;

[0040] A corresponding cloud card to be allocated is matched for the terminal device. The cloud card to be allocated must at least meet the following requirements: the cloud card to be allocated includes network slice resources that match the network slice requirement information.

[0041] The method for allocating network slices further includes:

[0042] In response to the triggering information sent by the terminal device, determine the location information of the terminal device corresponding to the triggering information;

[0043] The cloud card to be assigned must also meet the following requirement: the preset coverage area of ​​the cloud card to be assigned must cover the area corresponding to the location information of the terminal device.

[0044] The triggering information also includes the expected tariff information of the terminal device;

[0045] The cloud card to be allocated must also meet the following requirement: the tariff of the cloud card to be allocated must match the expected tariff information of the terminal device.

[0046] The method for allocating network slices further includes:

[0047] When the idle time of the user identification card (UIC) consisting of cloud cards in the terminal device exceeds a preset idle threshold period, the cloud card that has exceeded the preset idle threshold period is either released as a resource or the UIC in the terminal device is replaced based on the system's preset replacement logic.

[0048] Thirdly, the present invention also provides a method for obtaining network slices based on a cloud control platform, the main features of which include:

[0049] The terminal device sends trigger information to the cloud control platform, the trigger information including the network slicing requirement information of the terminal device;

[0050] Obtain a user identification card to be used, which is composed of cloud cards to be allocated, from the cloud control platform. The cloud cards to be allocated must at least meet the following requirements: the cloud cards to be allocated include network slice resources that match the network slice requirement information.

[0051] The terminal device activates the user identification card to be used.

[0052] Fourthly, the present invention also provides a network slice allocation device, characterized in that it includes:

[0053] The signal receiving module is used to receive trigger information sent by the terminal device;

[0054] The cloud card pool includes several cloud cards to be allocated to meet different internet access needs;

[0055] The network slice matching module is used to determine the network slice requirement information of the terminal device corresponding to the trigger information based on the trigger information, and to match the corresponding cloud card to be allocated from the cloud card pool for the terminal device. The cloud card to be allocated must at least meet the following requirements: the cloud card to be allocated includes network slice resources that match the network slice requirement information.

[0056] The network slice distribution module is used to construct the matched cloud cards to be allocated into user identification cards and distribute them to the terminal devices.

[0057] Fifthly, the present invention also provides a network slice acquisition device, characterized in that it includes:

[0058] A trigger information generation module is used to generate trigger information based on the status of the terminal device, wherein the trigger information includes network slicing requirement information of the terminal device.

[0059] The trigger information sending module is used to send the trigger information to the cloud control platform;

[0060] The network slice acquisition module is used to receive the user identification card to be used, which is composed of cloud cards to be allocated, matched by the cloud control platform, so as to obtain network slice resources that match the network slice requirement information. The cloud card to be allocated must at least meet the following requirement: the cloud card to be allocated includes network slice resources that match the network slice requirement information.

[0061] The trigger information generation module includes:

[0062] The slice demand monitoring unit is used to perform slice demand detection operations to generate a corresponding network slice demand detection signal based on the detected state of the terminal device.

[0063] The slice request receiving unit is used to receive externally input slice request instructions in order to generate corresponding network slice instruction information.

[0064] The trigger signal generation module is used to generate corresponding trigger information based on the network slice demand detection signal or the network slice instruction information, wherein the priority of the network slice demand detection signal is lower than the priority of the network slice instruction information. When the terminal device receives the slice demand instruction, the network slice demand information is generated from the network slice instruction information; when the terminal device does not receive the slice demand instruction, the network slice demand information is generated from the network slice demand detection signal.

[0065] In a sixth aspect, the present invention also provides an electronic device including a processor, a memory connected to the processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method as described in the first aspect when executing the computer program.

[0066] In a seventh aspect, the present invention also provides a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the method as described in the first aspect.

[0067] As can be seen, the above technical solution allocates cloud cards that meet the corresponding network slice requirements to each terminal device through a cloud control platform. This enables rapid network slice resource replacement for terminal devices, thus meeting the diverse network needs of devices in different application scenarios. It is highly executable and can adaptively handle sudden surges in traffic. Furthermore, this solution includes a cloud card pool containing cloud cards with different network slice resources. The cloud control platform can match and allocate the corresponding cloud card to the terminal device based on the trigger information sent by the terminal device. This design effectively improves the overall utilization of network resources and increases the success rate and accuracy of network slice resource replacement. This solution effectively ensures more rational resource utilization, is easy to operate, and provides users with a better user experience. Attached Figure Description

[0068] The following will further explain the concept, specific structure, and technical effects of the present invention in conjunction with the accompanying drawings, so as to fully understand the purpose, features, and effects of the present invention.

[0069] Figure 1This is a schematic diagram of the operation mode for matching the corresponding network slice to the device in the existing technology of SIM card and slice type binding mode.

[0070] Figure 2 This is a schematic diagram illustrating the operational logic of a network slice management method based on a cloud control platform according to an embodiment of the present invention. Detailed Implementation

[0071] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0072] It should be noted that in this article, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0073] To accommodate different application scenarios, various network slice types (eMBB slice, mMTC slice, and uRLLC slice) are defined to meet the needs of different application scenarios. Existing technologies typically pre-configure the corresponding network slice type in the device to meet the device's application requirements. However, this overlooks the fact that for some devices, a single network slice type cannot meet their operational needs in different modes. For example, some devices may prioritize low latency during daily use, but require high speeds during system updates. A single pre-configured network slice type cannot simultaneously meet the network needs of both scenarios, resulting in poor flexibility. For some mass-production equipment application scenarios, the current technology's inability to flexibly and quickly adjust the network slice type within the equipment can lead to serious economic losses. For example, some smart factories may deploy hundreds of industrial sensors. Based on the daily usage needs of industrial sensors, their initial configuration is mMTC slice. However, when the factory needs to perform remote equipment maintenance, the demand for video monitoring surges. But because the equipment's fixed configuration cannot be dynamically switched to eMBB slice, it will result in low maintenance efficiency, excessive production line downtime, and consequently, economic losses.

[0074] However, if network slice resources that meet all network usage needs are preset in the device in advance, it will lead to excessive idle network resources and low network resource utilization.

[0075] To address these issues, improve network deployment flexibility, enhance switching efficiency, and increase network resource utilization, this invention provides a method and apparatus for managing network slices based on a cloud control platform. The following detailed description, in conjunction with specific embodiments, further illustrates this approach:

[0076] In a first aspect, the present invention provides a method for managing network slices based on a cloud control platform, and the technical solution will be described below in conjunction with specific embodiments.

[0077] The method for managing network slices based on a cloud control platform according to the present invention includes the following steps:

[0078] Based on the correspondence between preset device identification information and initial network slice requirement information, the initial network slice requirement information of the terminal device is determined according to the device identification information of the terminal device in the trigger information, and a cloud card (i.e. a virtual user identification card) including corresponding network slice resources is allocated to each terminal device.

[0079] The terminal device determines whether it has received network slicing instruction information. If it has not received network slicing instruction information, it determines the network slicing requirement information based on the terminal device's device identification information, real-time registered network information, and real-time signal status information. If it receives network slicing instruction information, it determines the network slicing requirement information based on the network slicing instruction information.

[0080] The network slicing instruction information includes at least one trigger signal selected from the following: a switching eMBB network slice trigger signal, a switching mMTC network slice trigger signal, and a switching URLLC network slice trigger signal. The network slicing instruction information includes trigger signals generated from user-inputted slicing request instructions, specifically:

[0081] When the network slicing instruction information includes a switch to eMBB network slice trigger signal, the network slice required by the terminal device is determined to be an eMBB network slice, and corresponding network slice requirement information is generated; when the network slicing instruction information includes a switch to mMTC network slice trigger signal, the network slice required by the terminal device is determined to be an mMTC network slice, and corresponding network slice requirement information is generated; when the network slicing instruction information includes a switch to URLLC network slice trigger signal, the network slice required by the terminal device is determined to be a URLLC network slice, and corresponding network slice requirement information is generated.

[0082] Specifically, when the network slicing requirement information is determined based on the device identification information, real-time registered network information, and real-time signal status information of the terminal device, the following operations are performed:

[0083] Perform a slice requirement detection operation, which includes: detecting the real-time registered network information and real-time signal status information, and determining the network slice required by the terminal device;

[0084] If the real-time registered network information and real-time signal status information meet the first triggering condition preset by the system, then the network slice required by the terminal device is determined to be an eMBB network slice, so as to generate the corresponding network slice requirement information and return the above slice requirement detection operation.

[0085] If the real-time registered network information and real-time signal status information meet the second triggering condition preset by the system, then the network slice required by the terminal device is determined to be an mMTC network slice, so as to generate the corresponding network slice requirement information and return the above slice requirement detection operation.

[0086] If the real-time registered network information and real-time signal status information meet the third triggering condition preset by the system, then the network slice required by the terminal device is determined to be a URLLC network slice, so as to generate the corresponding network slice requirement information and return the above slice requirement detection operation.

[0087] The terminal device sends a trigger message to the operation and control platform to request the corresponding network slice resources;

[0088] The cloud control platform responds to the trigger information sent by the terminal device and determines the network slicing requirement information of the terminal device corresponding to the trigger information;

[0089] The triggering information includes the terminal device's device identification information, real-time registration network information, real-time signal status information, device location information, and the terminal device's expected tariff information; the device identification information includes at least one of the device's SN number or IMEI number.

[0090] To match the terminal device with a corresponding cloud card to be assigned, the cloud card to be assigned must at least meet the following requirements:

[0091] The cloud cards to be allocated include network slice resources that match the network slice demand information;

[0092] The preset coverage area of ​​the cloud card to be allocated includes the area corresponding to the location information of the terminal device;

[0093] The tariff of the cloud card to be allocated is matched with the expected tariff information of the terminal device.

[0094] The matched cloud cards to be allocated form user identification cards to be used, which are then sent to the terminal devices.

[0095] The terminal device activates the user identification card to be used.

[0096] This embodiment utilizes a cloud SIM card terminal and a cloud SIM card server to replace network slices. Without physical operation, it enables real-time cloud updates of terminal device slice configurations, achieving dynamic adaptation. A hybrid detection mechanism—automatic KPI monitoring combined with user-initiated reporting—triggers slice switching. The automatic KPI monitoring mechanism is an automated monitoring operation performed based on the detected device identification information, real-time registered network information, and real-time signal status information of the terminal device to determine the network slice requirement. The user-initiated reporting mechanism generates network slice command information through user-triggered responses to determine the network slice requirement. The combined use of these two triggering methods makes the overall switching process more intelligent. The related technical design better meets the network usage needs of terminal devices at different stages of use. Furthermore, this solution allows for elastic resource allocation based on traffic prediction, effectively reducing network resource waste and achieving resource optimization.

[0097] Meanwhile, during implementation, when the idle time of the user identification card (UIC) composed of cloud cards in the terminal device exceeds a preset idle threshold period, the cloud card that exceeds the preset idle threshold period will be released as a resource or the UIC in the terminal device will be replaced based on the system's preset replacement logic (e.g., the original cloud card can be automatically downgraded).

[0098] Before executing the cloud card allocation request, the terminal device also performs the following operations:

[0099] Detect whether the terminal device includes a user identification card corresponding to the network slicing requirement information;

[0100] If the terminal device does not contain a user identification card corresponding to the network slice requirement information, the triggering information is sent to the operation and control platform to request the allocation of a user identification card to be used; if the terminal device contains a user identification card corresponding to the network slice requirement information, the user identification card contained in the terminal device corresponding to the network slice requirement information is used to form the user identification card to be used.

[0101] The network slice management method based on a cloud control platform of this invention effectively solves the problems of poor cross-scenario adaptability and high manual maintenance costs of existing 5G devices due to factory-fixed slice request types, reliance on passive identification by operators, and strong binding between physical SIM cards and slice types. In this embodiment, network slice resource switching is achieved through the cooperation of cloud SIM card terminals and cloud SIM card servers. That is, the cloud SIM card terminal (i.e., the terminal device) achieves dynamic configuration of network slices through the cloud platform (i.e., the cloud control platform). At the same time, a hybrid detection triggering mechanism is set up to cooperate with the setting and switching of intelligent slices. Thus, while achieving automatic switching, a higher-priority manual triggering mode is also used to better meet the needs of end users. The network slice resource replacement achieved by allocating cloud SIM cards in this technical solution can also reduce the waste of network resources and minimize the cost and risk of version control.

[0102] The relevant operational logic of this embodiment can also be found in [the documentation / reference]. Figure 2 As shown, combined with Figure 2 It can be seen that the implementation process mainly includes the following stages:

[0103] Phase 1: Cloud Platform Configuration Management

[0104] Terminal device information is entered into the cloud control platform. Through the cloud control platform, different network slice types can be configured and issued according to various rules such as the entered device SN number, IMEI number or device type. That is, the data setting operation of the correspondence between device identification information and initial network slice requirement information is performed.

[0105] Phase Two: Terminal Authentication and Configuration Distribution of Network Slice Types

[0106] 1. Seed Card Authentication

[0107] The cloud card terminal uses the seed card network to authenticate and interact with the cloud card server, and reports the current device SN number, IMEI number and other device information, as well as the registration network, signal quality and location information. If there is a GPS (Global Positioning System) device, the GPS device can report accurate location information.

[0108] 2. Strategy matching and distribution

[0109] The cloud control platform matches the device identifier with the preset slice type and sends the authentication information to the terminal (e.g., SN=100000000000-10000010000-Configure mMTC slice type).

[0110] At the same time, the cloud control platform obtains the current country code based on the reported network to determine the location information (GPS information can be obtained if GPS is synchronized for more accurate positioning). Based on the slice type and country code configured by the device, it matches the corresponding cloud card pool resources. Then, it simultaneously matches and distributes cloud SIM cards that support the current slice type to terminals suitable for the device based on multiple dimensions such as the precise location area, cloud card tariff, and the current registered network signal quality.

[0111] 3. Terminal startup: Assigned cloud card and set slice type.

[0112] After receiving the slice type configuration returned by the authentication, the cloud card terminal switches the settings, starts the assigned cloud card, and reports to the network side.

[0113] Phase 3: Dual-mode detection mechanism

[0114] 1. Automatic Mode: Real-time monitoring of network KPIs (determined based on real-time registered network information and real-time signal status), automatically switching slice types, or reporting to the platform switching card:

[0115] To facilitate understanding, examples from Table 1 are provided below to illustrate the automatic switching mechanism, enabling those skilled in the art to comprehend it:

[0116]

[0117] Table 1

[0118] It should be noted that the examples in Table 1 are for illustrative purposes only, and the actual triggering conditions and switching methods are not limited to these.

[0119] 2. User-triggered mode: The open API (i.e., application programming interface) allows the application layer to actively report business needs (such as an emergency button triggering a URLLC request), and users can generate network slicing instruction information by triggering the corresponding button.

[0120] Phase 4: Comprehensive Analysis and Flexible Resource Allocation

[0121] 1. Based on the automatic mode detection results and user-triggered mode switching requirements, and combined with the current card configuration information, determine whether to switch the slice type, or request the server to replace the card with one that supports slices. The relevant policies are fed back to the cloud platform server.

[0122] 2. After comprehensive analysis and judgment determine that the slice cloud card needs to be replaced, the cloud platform server elastic resource module should complete the relevant resource scheduling: predict the slice card resource demand for the next hour based on historical traffic patterns (daily / weekly / monthly cycles) and real-time trends; at the same time, dynamically allocate the best SIM card from the cloud card pool according to the device's geographical location, tariff policy, and slice type requirements; automatically downgrade or release resources for slice instances that have been idle for a certain period of time, achieve dynamic resource reclamation, and ensure that the cloud server card resources can meet the actual business switching needs.

[0123] like Figure 2 As shown, when making a network slice allocation request in this invention, the cloud card 3 can be obtained through seed card authentication to acquire the corresponding network slice resources. Simultaneously, the cloud card pool can be filtered using the country code, and the preferred base station group can be selected using location coordinates. During the matching process, the tariff strategy is obtained to perform package matching, thereby matching the optimal cloud card for the network slice resources. This cloud card is then used as a user identification card and distributed to achieve the configuration of the slice resources.

[0124] In other embodiments, in addition to using the aforementioned pricing strategies, location information and network slicing demand information to manage network slicing resources, cloud card matching can also be performed in combination with other configuration conditions, and is not limited to the embodiments described above.

[0125] Secondly, the present invention provides a method for allocating network slices, comprising:

[0126] In response to the triggering information sent by the terminal device, determine the network slicing requirement information of the terminal device corresponding to the triggering information;

[0127] A corresponding cloud card to be allocated is matched for the terminal device. The cloud card to be allocated must at least meet the following requirements: the cloud card to be allocated includes network slice resources that match the network slice requirement information.

[0128] The method for allocating network slices also includes:

[0129] In response to the triggering information sent by the terminal device, determine the location information of the terminal device corresponding to the triggering information;

[0130] The cloud card to be assigned must also meet the following requirement: the preset coverage area of ​​the cloud card to be assigned must cover the area corresponding to the location information of the terminal device.

[0131] The triggering information also includes the expected tariff information of the terminal device;

[0132] The cloud card to be allocated must also meet the following requirement: the tariff of the cloud card to be allocated must match the expected tariff information of the terminal device.

[0133] When the idle time of the user identification card (UIC) consisting of cloud cards in the terminal device exceeds a preset idle threshold period, the cloud card that has exceeded the preset idle threshold period is either released as a resource or the UIC in the terminal device is replaced based on the system's preset replacement logic.

[0134] The network slice allocation method adopted in this embodiment can better assist the switching operation of network slices in terminal devices, thereby providing a better network application environment.

[0135] Thirdly, the present invention provides a method for obtaining network slices based on a cloud control platform, comprising:

[0136] The terminal device sends trigger information to the cloud control platform, the trigger information including the network slicing requirement information of the terminal device;

[0137] Obtain a user identification card to be used, which is composed of cloud cards to be allocated, from the cloud control platform. The cloud cards to be allocated must at least meet the following requirements: the cloud cards to be allocated include network slice resources that match the network slice requirement information.

[0138] The terminal device activates the user identification card to be used.

[0139] This method enables rapid switching of network slice resources to meet users' network needs. In addition, when implementing this cloud-based network slice acquisition method, a dual-mode detection mechanism can be used locally to select the network slice type, and then corresponding trigger information can be generated to apply for network slice resources that match the requirements.

[0140] Specifically, when a trigger command input by the user into the terminal device is received, corresponding network slicing command information can be generated to determine the network slicing demand information based on the network slicing command information; when no trigger command input by the user into the terminal device is received, the network slicing demand information can be determined based on the terminal device's device identification information, real-time registered network information, and real-time signal status information.

[0141] The network slicing instruction information includes at least one of the following trigger signals generated according to the instruction: a switching eMBB network slice trigger signal, a switching mMTC network slice trigger signal, and a switching URLLC network slice trigger signal.

[0142] When determining the network slicing requirement information based on the device identification information, real-time registered network information, and real-time signal status information of the terminal device, the method further includes the following operations:

[0143] Perform a slice requirement detection operation, which includes: detecting the real-time registered network information and real-time signal status information, and determining the network slice required by the terminal device;

[0144] If the real-time registered network information and real-time signal status information meet the first triggering condition preset by the system, then the network slice required by the terminal device is determined to be an eMBB network slice, so as to generate the corresponding network slice requirement information and return the above slice requirement detection operation.

[0145] If the real-time registered network information and real-time signal status information meet the second triggering condition preset by the system, then the network slice required by the terminal device is determined to be an mMTC network slice, so as to generate the corresponding network slice requirement information and return the above slice requirement detection operation.

[0146] If the real-time registered network information and real-time signal status information meet the third triggering condition preset by the system, then the network slice required by the terminal device is determined to be a URLLC network slice, so as to generate the corresponding network slice requirement information and return the above slice requirement detection operation.

[0147] The dual-mode detection mechanism can adapt to the detection of network usage needs under different conditions, thus better meeting users' network usage needs.

[0148] Fourthly, the present invention provides a network slice allocation apparatus, comprising:

[0149] The signal receiving module is used to receive trigger information sent by the terminal device;

[0150] The cloud card pool includes several cloud cards to be allocated to meet different internet access needs;

[0151] The network slice matching module is used to determine the network slice requirement information of the terminal device corresponding to the trigger information based on the trigger information, and to match the corresponding cloud card to be allocated from the cloud card pool for the terminal device. The cloud card to be allocated must at least meet the following requirements: the cloud card to be allocated includes network slice resources that match the network slice requirement information.

[0152] The network slice distribution module is used to construct the matched cloud cards to be allocated into user identification cards and distribute them to the terminal devices.

[0153] By using this network slice allocation device, network slice resources can be allocated, enabling terminal devices to use more suitable network slice resources in more application scenarios and achieve higher work efficiency.

[0154] Fifthly, the present invention includes a network slice acquisition device, comprising:

[0155] A trigger information generation module is used to generate trigger information based on the status of the terminal device, wherein the trigger information includes network slicing requirement information of the terminal device.

[0156] The trigger information sending module is used to send the trigger information to the cloud control platform;

[0157] The network slice acquisition module is used to receive the user identification card to be used, which is composed of cloud cards to be allocated, matched by the cloud control platform, so as to obtain network slice resources that match the network slice requirement information. The cloud card to be allocated must at least meet the following requirement: the cloud card to be allocated includes network slice resources that match the network slice requirement information.

[0158] In this embodiment, the trigger information generation module includes:

[0159] The slice demand monitoring unit is used to perform slice demand detection operations to generate a corresponding network slice demand detection signal based on the detected state of the terminal device.

[0160] The slice request receiving unit is used to receive externally input slice request instructions and generate corresponding network slice instruction information. The slice request receiving unit can perform the following operation steps:

[0161] Perform a slice requirement detection operation, which includes: detecting the real-time registered network information and real-time signal status information, and determining the network slice required by the terminal device;

[0162] If the real-time registered network information and real-time signal status information meet the first triggering condition preset by the system, then the network slice required by the terminal device is determined to be an eMBB network slice, so as to generate the corresponding network slice requirement information and return the above slice requirement detection operation.

[0163] If the real-time registered network information and real-time signal status information meet the second triggering condition preset by the system, then the network slice required by the terminal device is determined to be an mMTC network slice, so as to generate the corresponding network slice requirement information and return the above slice requirement detection operation.

[0164] If the real-time registered network information and real-time signal status information meet the third triggering condition preset by the system, then the network slice required by the terminal device is determined to be a URLLC network slice, so as to generate the corresponding network slice requirement information and return the above slice requirement detection operation.

[0165] A trigger signal generation module is used to generate corresponding trigger information based on the network slice demand detection signal or the network slice instruction information. The network slice demand detection signal has a lower priority than the network slice instruction information. When the terminal device receives the slice demand instruction, the network slice demand information is generated from the network slice instruction information. When the terminal device does not receive the slice demand instruction, the network slice demand information is generated from the network slice demand detection signal. The network slice instruction information includes at least one trigger signal based on a switching eMBB network slice trigger signal, a switching mMTC network slice trigger signal, and a switching URLLC network slice trigger signal used for instruction generation. Specifically, the trigger signal included in the network slice instruction information is generated from a user-input slice demand instruction.

[0166] When the network slicing instruction information includes a switch to eMBB network slice trigger signal, the network slice required by the terminal device is determined to be an eMBB network slice, and corresponding network slice requirement information is generated; when the network slicing instruction information includes a switch to mMTC network slice trigger signal, the network slice required by the terminal device is determined to be an mMTC network slice, and corresponding network slice requirement information is generated; when the network slicing instruction information includes a switch to URLLC network slice trigger signal, the network slice required by the terminal device is determined to be a URLLC network slice, and corresponding network slice requirement information is generated.

[0167] This network slice acquisition device enables the execution of a cloud-based network slice acquisition method, allowing for faster network slice replacement. This effectively avoids the problems of lengthy factory returns, poor operability, and inability to adapt to sudden business surges. It also reduces costs, eliminates the need for pre-configuring multiple SIM card types, minimizes overall network resource utilization, and boasts a high detection rate, resulting in a higher success rate for handover in emergency scenarios. Furthermore, the dual-mode detection mechanism better meets the needs of users in different states, offering improved adaptability.

[0168] To better demonstrate the advantages of the technical solution of this invention, further analysis is provided below in conjunction with some typical application scenarios:

[0169]

Application Scenario 1: Smart Healthcare

[0170] During the switching process, given the uncertainty of the timing of surgical operations and the necessity of network mode selection, network slices can be selected by manually issuing network slice command information to ensure low network latency during the surgical robot's operation. When no surgical operation is required, the selected network slice resources can be adjusted by automatic monitoring or manual operation to ensure automatic switching can be achieved even if the user forgets to adjust, effectively saving resources.

[0171]

Application Scenario 2: Intelligent Logistics

[0172] In this application scenario, the rapid replacement of network slice resources can effectively meet the network usage needs of terminal devices under different states. By adopting the method of this invention, the replacement of network slices can be achieved by quickly replacing cloud cards, which can ensure the speed of switching and effectively improve the operating efficiency of the factory.

[0173]

Application Scenario 3: Automatic Switching Between Production and Cross-border Commercial Slices

[0174] In this application scenario, the corresponding network slice can be matched by combining the different location information of the device to meet the needs of use in different states. The switching of cloud cards can also reduce roaming costs, better ensure the use of the device in different environments, and meet the user's needs.

[0175] In a sixth aspect, the present invention also provides an electronic device including a processor, a memory connected to the processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method as described in the first aspect.

[0176] In a seventh aspect, the present invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in the first aspect.

[0177] For example, machine-readable storage media can include, but are not limited to, various known and unknown types of non-volatile memory.

[0178] Those skilled in the art will understand that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can implement the described functions in different ways for each specific application, but such implementation should not be considered beyond the scope of this application.

[0179] In the embodiments of this application, the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the division of units is merely a logical functional division, and other division methods may exist in actual implementation. For example, multiple units or components may be combined or integrated into another system. Furthermore, the coupling between the various units can be direct coupling or indirect coupling. Additionally, the functional units in the embodiments of this application can be integrated into a processing unit, or they can exist as separate physical entities, etc.

[0180] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0181] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a machine-readable storage medium. Therefore, the technical solution of this application can be embodied in the form of a software product, which can be stored in a machine-readable storage medium. This software product may include several instructions to cause an electronic device to execute all or part of the processes of the technical solution described in the embodiments of this application. The aforementioned storage medium may include various media capable of storing program code, such as ROM, RAM, removable disk, hard disk, magnetic disk, or optical disk.

[0182] This invention allocates cloud cards that meet the corresponding network slice requirements to each terminal device through a cloud control platform. This enables rapid network slice resource replacement for terminal devices, thus meeting the diverse network needs of devices in different application scenarios. It is highly executable and can adaptively handle sudden surges in traffic. Furthermore, this solution includes a cloud card pool containing cloud cards with different network slice resources. The cloud control platform can match and allocate the corresponding cloud card to the terminal device based on the trigger information sent by the terminal device. This design effectively improves the overall utilization of network resources and increases the success rate and accuracy of network slice resource replacement. This solution effectively ensures more rational use of resources, effectively reduces operation and maintenance costs, is easy to operate, improves the flexibility of device terminal-level network resource usage, and provides users with a better user experience.

[0183] The preferred embodiments of the present invention have been described in detail above. It should be understood that those skilled in the art can make numerous modifications and variations based on the concept of the present invention without creative effort. Therefore, all technical solutions that can be obtained by those skilled in the art based on the concept of the present invention through logical analysis, reasoning, or limited experimentation on the basis of existing technology should be within the scope of protection defined by the claims.

Claims

1. A method for management of network slices based on a cloud control platform, characterized in that, include: In response to the triggering information sent by the terminal device, determine the network slicing requirement information of the terminal device corresponding to the triggering information; Match a corresponding cloud card to be allocated to the terminal device. The cloud card to be allocated must at least meet the following requirements: the cloud card to be allocated includes network slice resources that match the network slice requirement information. The matched cloud cards to be allocated form user identification cards to be used, which are then sent to the terminal devices. The terminal device activates the user identification card to be used; The triggering information includes the device identification information of the terminal device, real-time registration network information, and real-time signal status information. The network slicing requirement information is determined based on the device identification information, real-time registered network information, and real-time signal status information of the terminal device. When the triggering information includes network slicing instruction information, the network slicing requirement information is determined based on the network slicing instruction information; when the triggering information does not include the network slicing instruction information, the network slicing requirement information is determined based on the device identification information, real-time registered network information, and real-time signal status information of the terminal device. The network slicing instruction information includes at least one of the following trigger signals generated according to the instruction: a switching eMBB network slice trigger signal, a switching mMTC network slice trigger signal, and a switching URLLC network slice trigger signal. 2.The method for cloud control platform based network slice management according to claim 1, characterized in that, When determining the network slicing requirement information based on the device identification information, real-time registered network information, and real-time signal status information of the terminal device, the method also... Includes the following operations: Perform a slice requirement detection operation, which includes: detecting the real-time registered network information and real-time signal status information, and determining the network slice required by the terminal device; If the real-time registered network information and real-time signal status information meet the first triggering condition preset by the system, then the network slice required by the terminal device is determined to be an eMBB network slice, so as to generate the corresponding network slice requirement information and return the above slice requirement detection operation. If the real-time registered network information and real-time signal status information meet the second triggering condition preset by the system, then the network slice required by the terminal device is determined to be an mMTC network slice, so as to generate the corresponding network slice requirement information and return the above slice requirement detection operation. If the real-time registered network information and real-time signal status information meet the third triggering condition preset by the system, then the network slice required by the terminal device is determined to be a URLLC network slice, so as to generate the corresponding network slice requirement information and return the above slice requirement detection operation.

3. The method for cloud control platform based network slice management according to claim 1 or 2, characterized in that, The method for managing network slices based on the cloud control platform also includes: In response to the triggering information sent by the terminal device, determine the location information of the terminal device corresponding to the triggering information; The cloud card to be assigned must also meet the following requirement: the preset coverage area of ​​the cloud card to be assigned must cover the area corresponding to the location information of the terminal device.

4. The method for cloud control platform based network slice management according to claim 1 or 2, characterized in that, The triggering information also includes the expected tariff information of the terminal device; The cloud card to be allocated must also meet the following requirement: the tariff of the cloud card to be allocated must match the expected tariff information of the terminal device. 5.The method for cloud control platform based network slice management according to claim 1, characterized in that, The method for managing network slices based on the cloud control platform also includes: Based on the correspondence between preset device identification information and initial network slicing requirement information, the initial network slicing requirement information of the terminal device is determined according to the device identification information of the terminal device in the trigger information. 6.The method for cloud control platform based network slice management according to any one of claims 1, 2, 4, wherein, The device identification information includes at least one of the device SN number or IMEI number. 7.The method for cloud control platform based network slice management according to claim 1, characterized in that, The method for managing network slices based on the cloud control platform also includes: Detect whether the terminal device includes a user identification card corresponding to the network slicing requirement information; If the terminal device does not contain a user identification card corresponding to the network slice requirement information, the triggering information is sent to the operation and control platform to request the allocation of a user identification card to be used; if the terminal device contains a user identification card corresponding to the network slice requirement information, the user identification card contained in the terminal device corresponding to the network slice requirement information is used to form the user identification card to be used. 8.The method for cloud control platform based network slice management according to claim 1, characterized in that, The method for managing network slices based on the cloud control platform also includes: When the idle time of the user identification card (UIC) consisting of cloud cards in the terminal device exceeds a preset idle threshold period, the cloud card that has exceeded the preset idle threshold period is either released as a resource or the UIC in the terminal device is replaced based on the system's preset replacement logic. 9.A method of allocation of network slices, the method comprising: include: In response to the triggering information sent by the terminal device, determine the network slicing requirement information of the terminal device corresponding to the triggering information; Match a corresponding cloud card to be allocated to the terminal device. The cloud card to be allocated must at least meet the following requirements: the cloud card to be allocated includes network slice resources that match the network slice requirement information. The triggering information includes the device identification information of the terminal device, real-time registration network information, and real-time signal status information. The network slicing requirement information is determined based on the device identification information, real-time registered network information, and real-time signal status information of the terminal device. When the triggering information includes network slicing instruction information, the network slicing requirement information is determined based on the network slicing instruction information; when the triggering information does not include the network slicing instruction information, the network slicing requirement information is determined based on the device identification information, real-time registered network information, and real-time signal status information of the terminal device. The network slicing instruction information includes at least one of the following trigger signals generated according to the instruction: a switching eMBB network slice trigger signal, a switching mMTC network slice trigger signal, and a switching URLLC network slice trigger signal.

10. The method of allocating network slices of claim 9, wherein, The method for allocating network slices also includes: In response to the triggering information sent by the terminal device, determine the location information of the terminal device corresponding to the triggering information; The cloud card to be assigned must also meet the following requirement: the preset coverage area of ​​the cloud card to be assigned must cover the area corresponding to the location information of the terminal device.

11. The method of allocating network slices of claim 9, wherein, The triggering information also includes the expected tariff information of the terminal device; The cloud card to be allocated must also meet the following requirement: the tariff of the cloud card to be allocated must match the expected tariff information of the terminal device.

12. The method of allocating network slices of claim 9, wherein, The method for allocating network slices also includes: When the idle time of the user identification card (UIC) consisting of cloud cards in the terminal device exceeds a preset idle threshold period, the cloud card that has exceeded the preset idle threshold period is either released as a resource or the UIC in the terminal device is replaced based on the system's preset replacement logic. 13.A method for obtaining a network slice based on a cloud control platform, characterized in that, include: The terminal device sends trigger information to the cloud control platform, the trigger information including the network slicing requirement information of the terminal device; Obtain a user identification card to be used, which is composed of cloud cards to be allocated, from the cloud control platform. The cloud cards to be allocated must at least meet the following requirements: the cloud cards to be allocated include network slice resources that match the network slice requirement information. The terminal device activates the user identification card to be used; The triggering information includes the device identification information of the terminal device, real-time registration network information, and real-time signal status information. The network slicing requirement information is determined based on the device identification information, real-time registered network information, and real-time signal status information of the terminal device. When the triggering information includes network slicing instruction information, the network slicing requirement information is determined based on the network slicing instruction information; when the triggering information does not include the network slicing instruction information, the network slicing requirement information is determined based on the device identification information, real-time registered network information, and real-time signal status information of the terminal device. The network slicing instruction information includes at least one of the following trigger signals generated according to the instruction: a switching eMBB network slice trigger signal, a switching mMTC network slice trigger signal, and a switching URLLC network slice trigger signal.

14. A network slice allocation device, characterized in that, include: The signal receiving module is used to receive trigger information sent by the terminal device; The cloud card pool includes several cloud cards to be allocated to meet different internet access needs; The network slice matching module is used to determine the network slice requirement information of the terminal device corresponding to the trigger information based on the trigger information, and to match the corresponding cloud card to be allocated from the cloud card pool for the terminal device. The cloud card to be allocated must at least meet the following requirements: the cloud card to be allocated includes network slice resources that match the network slice requirement information. The network slice distribution module is used to construct the matched cloud cards to be allocated into user identification cards and distribute them to the terminal devices; The triggering information includes the device identification information of the terminal device, real-time registration network information, and real-time signal status information. The network slicing requirement information is determined based on the device identification information, real-time registered network information, and real-time signal status information of the terminal device. When the triggering information includes network slicing instruction information, the network slicing requirement information is determined based on the network slicing instruction information; when the triggering information does not include the network slicing instruction information, the network slicing requirement information is determined based on the device identification information, real-time registered network information, and real-time signal status information of the terminal device. The network slice instruction information comprises at least one of a switching eMBB network slice trigger signal, a switching mMTC network slice trigger signal and a switching URLLC network slice trigger signal according to a switching instruction generation.

15. An apparatus for acquiring a network slice, the apparatus comprising: Comprise: A trigger information generation module configured to generate trigger information based on a state of a terminal device, the trigger information comprising network slice requirement information of the terminal device; A trigger information sending module configured to send the trigger information to a cloud control platform; A network slice acquisition module configured to receive a to-be-used user identification card composed of a to-be-allocated cloud card matched out by the cloud control platform to acquire a network slice resource matched with the network slice requirement information, wherein the to-be-allocated cloud card at least needs to satisfy: the to-be-allocated cloud card comprises a network slice resource matched with the network slice requirement information; The trigger information comprises device identification information, real-time registration network information and real-time signal state information of the terminal device; The network slice requirement information is determined based on the device identification information, the real-time registration network information and the real-time signal state information of the terminal device; When the trigger information comprises network slice instruction information, the network slice requirement information is determined based on the network slice instruction information; when the trigger information does not comprise the network slice instruction information, the network slice requirement information is determined based on the device identification information, the real-time registration network information and the real-time signal state information of the terminal device; The network slice instruction information comprises at least one of a switching eMBB network slice trigger signal, a switching mMTC network slice trigger signal and a switching URLLC network slice trigger signal according to a switching instruction generation.

16. An electronic device comprising a processor, a memory connected to the processor, and a computer program stored in the memory and loadable onto the processor, characterized in that, The processor executes the computer program to realize the method for managing a network slice based on a cloud control platform according to any one of claims 1 to 8.

17. A computer-readable storage medium, the computer-readable storage medium storing a computer program, characterized in that, The computer program is executed by the processor to realize the method for managing a network slice based on a cloud control platform according to any one of claims 1 to 8.

Images