WO2019196926A1 - 一种设备切片的处理方法、装置及计算机可读存储介质 - Google Patents

一种设备切片的处理方法、装置及计算机可读存储介质 Download PDF

Info

Publication number
WO2019196926A1
WO2019196926A1 PCT/CN2019/082421 CN2019082421W WO2019196926A1 WO 2019196926 A1 WO2019196926 A1 WO 2019196926A1 CN 2019082421 W CN2019082421 W CN 2019082421W WO 2019196926 A1 WO2019196926 A1 WO 2019196926A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
type
function
slice
identifier
Prior art date
Application number
PCT/CN2019/082421
Other languages
English (en)
French (fr)
Inventor
何中圣
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2019196926A1 publication Critical patent/WO2019196926A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information

Definitions

  • the embodiments of the present application relate to the field of communications technologies, such as a method and an apparatus for processing device slices, and a computer readable storage medium.
  • 5G fifth generation of mobile communication
  • 5G fifth generation of mobile communication
  • Network slicing technology is created to solve this problem.
  • the technology essentially divides the operator's physical network into multiple virtual networks, and according to different service requirements, such as bandwidth, delay, reliability and other requirements. To divide to meet different application scenarios and needs.
  • the node device when used to provide a certain service, it actually runs the device slice corresponding to the service in itself, so when the node device is used to provide other new services, it needs to be re- Obtain the device slice corresponding to the new service, and the new device slice needs to be obtained by running the type program and function program corresponding to the new service from the outside (can be the Internet or other places).
  • the embodiment of the present invention provides a method, a device, and a computer readable storage medium for managing a device slice, which can simplify the process of acquiring a device slice and improve the user experience.
  • An embodiment of the present application provides a method for managing a device slice, including: the node device acquiring an identifier of a user to which the device slice creation instruction belongs, a type and function of a device slice to be created, and using the obtained identifier as the first target identifier.
  • the obtained type is used as the first target type; when there is no corresponding to the first target identifier, the first target type, and the first target function in the node device
  • the corresponding type process file is obtained according to the first target type, and the corresponding function process file is obtained according to the first target function; and the first type is generated according to the obtained type process file and the function process file.
  • the embodiment of the present application further provides a processing device for a device slice, including: a processor and a memory, wherein the memory stores the following instructions executable by the processor: acquiring an identifier of a user to which the device slice creation instruction belongs, and the desired creation The type and function of the device slice, and the obtained identifier is used as the first target identifier, and the obtained type is used as the first target type, and the obtained function is used as the first target function; when the first target is not present in the node device When the first target device slice corresponding to the identifier, the first target type, and the first target function is obtained, acquiring a corresponding type process file according to the first target type, and acquiring corresponding according to the first target function a function process file; generating the first target device slice according to the obtained type process file and the function process file.
  • the embodiment of the present application further provides a computer readable storage medium, where the computer executable instructions are stored on the storage medium, and the computer executable instructions are configured to perform the following steps: acquiring an identifier of a user to which the device slice creation instruction belongs, and an expectation The type and function of the created device slice, and the obtained identifier is used as the first target identifier, and the obtained type is used as the first target type, and the obtained function is used as the first target function; when the node device does not exist and the first And acquiring a corresponding type process file according to the first target type, and acquiring the first target device according to the first target type, and acquiring the corresponding target process file according to the first target type Corresponding functional process file; generating the first target device slice according to the obtained type process file and the function process file.
  • FIG. 1 is a schematic flowchart of a method for processing a device slice according to an embodiment of the present disclosure
  • FIG. 2 is a schematic structural diagram of a software structure of a communication device supporting a network slice according to an embodiment of the present application
  • FIG. 3 is a schematic flowchart of a method for creating a device slice according to an embodiment of the present disclosure
  • FIG. 4 is a schematic flowchart of a method for deleting a device slice according to an embodiment of the present disclosure.
  • An embodiment of the present application provides a method for processing a device slice. As shown in FIG. 1 , the method includes steps 101 to 103.
  • the node device acquires the identifier of the user to which the device slice creation instruction belongs, the type and function of the device slice to be created, and uses the obtained identifier as the first target identifier, and obtains the obtained type as the first target type, which will be obtained.
  • the function serves as the first target function.
  • the node device may be a server or other device capable of creating a device slice, which is not limited in this application.
  • the first target type is a type of the first target device slice to be created by the user, for example, a car network type, a home appliance networking type, etc., and the types may be pre-divided by the node device, and the first target function is The functions of the first target device slice to be created by the user, for example, Bluetooth function, Wireless-Fidelity (Wi-Fi) function, and the like.
  • a device slice can only have one type, but it can have more than one function. For example, a home appliance network device with Bluetooth function and Wi-Fi function is sliced, and the type is home appliance networking type, and the function is Bluetooth function. And Wi-Fi capabilities.
  • the first target type and the first target function may be input by the user in the node device interaction interface, and then acquired by the node device.
  • step 102 when there is no first target device slice corresponding to the first target identifier, the first target type, and the first target function, the corresponding type process file is obtained according to the first target type, and according to The first target function acquires a corresponding function process file.
  • step 103 a first target device slice is generated according to the obtained type process file and the function process file.
  • the processing method of the device slice provided by the embodiment of the present application can obtain the type process file and the function process file of the target device slice according to the first target type and the first target function, thereby avoiding the need to create a new device slice.
  • the cumbersome process of externally finding the corresponding type of process files and functional processes improves the user experience.
  • the acquiring the corresponding type process file according to the first target type, and acquiring the corresponding function process file according to the first target function includes: acquiring the first target type corresponding according to the pre-established first correspondence relationship The type process file is obtained, and the function process file corresponding to the first target function is obtained according to the pre-established second correspondence.
  • the first correspondence is the correspondence between the type of the device slice and the type process file
  • the second correspondence is the correspondence between the function of the device slice and the function process file.
  • the first correspondence may be expressed in the form of a table, and it is assumed that the type of the device slice that exists by itself has a car network type and a home appliance networking type, and the type process file corresponding to the car network type is a file A1, and the home appliance networking type The corresponding type process file is file A2, and the first correspondence may be as shown in Table 1.
  • Type of device slice Type process file Car networking Document A1 Appliance networking Document A2
  • the second correspondence may be expressed in the form of a table. It is assumed that the function of the device slice existing by itself has a remote operation function, a Wi-Fi function, and a Bluetooth function, and the function process file corresponding to the remote operation function is the file B1.
  • the function process file corresponding to the Wi-Fi function is the file B2
  • the function process file corresponding to the Bluetooth function is the file B3, and the second correspondence relationship can be as shown in Table 2.
  • the method further includes: generating prompt information that the device slice that the user desires to establish is already present in the node device.
  • the method before acquiring the type process file corresponding to the first target type according to the pre-established second correspondence, the method further includes: determining, according to the pre-established third correspondence, whether the first target device slice exists in the node device;
  • the third correspondence relationship is a correspondence between the device slice stored in the node device and the identifier of the user to which the device slice belongs, the type of the device slice, and the function of the device slice.
  • the third correspondence may also be represented in the form of a table, assuming that the existing device slice has device slice A, device slice B, and device slice C.
  • the user of device slice A is user A, the type is car networking type, the function is remote operation function and Wi-Fi function;
  • the user of device slice B is user B, the type is home appliance networking type, the function is Bluetooth function;
  • device slice The user of C belongs to user B, the type is car networking type, and the function is remote operation function and bluetooth function, then the third correspondence can be as shown in Table 3.
  • the method further includes: updating the third correspondence according to the correspondence between the first target identifier, the first target type, the first target function, and the first target device slice.
  • determining whether the first target device slice exists in the node device according to the third correspondence that is established in advance includes: determining whether the identifier of the user belonging to the third correspondence is the same as the first target identifier, and the type and the A device slice with the same target type and the same function as the first target.
  • Target device slice if there is no device in the third relationship that has the same identifier as the first target identifier, and the type is the same as the first target type, and the function is the same as the first target function, it is determined that the first target does not exist.
  • Target device slice if there is no device in the third relationship that has the same identifier as the first target identifier, and the type is the same as the first target type, and the function is the same as the first target function, it is determined that the first target does not exist.
  • the case where there is no device slice having the same type as the first target type and having the same function as the first target function in the third relationship includes three cases: the first case is that the non-existence type in the third relationship is the same as the first target type , but there is a device slice with the same function as the first target function; the second case is that the third relationship has the same type as the first target type, but there is no device slice with the same function as the first target function; the third case There is no type in the third relationship that is the same as the first target type, and there is no device slice whose function is the same as the first target function.
  • the method further includes: acquiring a port resource in the node device that can be allocated to the first target device slice.
  • the obtained port resource is marked to indicate that the port resource belongs to the first target device slice.
  • the method before the node device acquires the identifier of the user to which the device slice creation instruction belongs, and the type and function of the device slice to be created, the method further includes: acquiring the device slice deletion instruction, the identifier of the user, and the device that the user desires to delete.
  • the type and function of the slice, and the obtained identifier is used as the second target identifier, and the obtained type is taken as the second target type, and the obtained function is taken as the second target function.
  • the second target device slice exists in the node device, the second target device slice is acquired and deleted.
  • determining, according to the third correspondence, whether there is a second target device slice corresponding to the obtained second target type and the second target function includes: determining whether the user of the third corresponding relationship exists The device slice is the same as the second target identifier, the same type as the second target type, and the function is the same as the second target function.
  • the method further includes: generating prompt information that the device slice that the user desires to delete does not exist in the node device.
  • the method before the second target device slice is acquired and deleted when the second target device slice has the port level protection, the method further includes: triggering a service switching operation of the second target device slice.
  • Acquiring and deleting the second target device slice includes: acquiring the second target device slice, and controlling the second target device slice to exit all applications.
  • the port resource pre-allocated to the second target device slice is reclaimed, and the second target device slice is deleted.
  • the application also provides a schematic diagram of a software structure of a communication device supporting network slicing.
  • the device software mainly includes four modules: device operating system, version management, resource management, and slice management, wherein the operating system provides a system level.
  • Slice technology such as the current common docker technology.
  • the version management module is responsible for the management of all versions of files, such as the correspondence between the slice type and the version file, and can be in the following format:
  • the slice type and the slice function can correspond to one or more files, or file packages, and the slicing function is optional, and the user can select and configure according to his own needs.
  • the resource management module is responsible for the management of physical resources such as boards, ports, memory, and central processing units (CPUs) of the device.
  • the slice management module is responsible for slice management of the entire device, requests version information from the version management module according to the configuration of the user, and requests the relevant resources from the resource management module for the slice.
  • the embodiment of the present application further provides a method for creating a device slice. As shown in FIG. 3, the method includes steps 1 to 5.
  • step 1 when creating a slice, the user will specify a unique keyword for the slice, such as the slice ID.
  • the slice management module will determine whether there is already a slice with the same ID. If yes, go to step 5, otherwise enter the next step.
  • step 2 there is no slice of the same ID on the device, and the slice management module requests the version file information from the version management module according to the slice type and the slice function, and after receiving the response, proceeds to the next step.
  • step 3 the slice management module starts the basic software of the slice according to the requested version information, including slicing its own independent version management client module.
  • step 4 the sliced version management client module downloads the version file according to the version information synchronized from the slice management module, and then runs the corresponding version file, and the slice creation is completed.
  • step 5 if there is already a slice with the same ID, it is judged whether there is an update of the slice function, and if so, the process proceeds to step 4, otherwise the response user slice has been created.
  • the embodiment of the present application further provides a resource allocation method for device slice. As shown in FIG. 4, the method includes steps 1 to 4.
  • step 1 the slice management module receives a command from the user to allocate a physical resource for slice n.
  • step 2 the slice management module requests the resource from the resource management module, and the resource management module determines whether the resource is occupied by other slices, and if so, returns the user resource is unavailable, otherwise proceeds to the next step.
  • the resource management module marks the physical resource with a slice n, such as a slice ID, and saves it to the memory and the storage medium, so as to ensure that the user configuration can be correctly restored after the next startup.
  • step 4 after receiving the success response of the resource management module, the slice management module sends the resource information to the slice n own resource management module, and the slice n saves the resource information into its own database.
  • the embodiment of the present application further provides a method for deleting a device slice, where the method includes steps 1 to 5.
  • step 1 the slice management module receives the slice deletion command sent by the user, and determines whether the slice has protection. If the slice has protection, the service is triggered to be switched first. If there is no protection, the process proceeds to the next step.
  • step 2 the slice management module receives the module that the switchover is completed or is not protected, and the slice management module notifies the slice to perform the exit operation.
  • step 3 after the exit of the application process is completed, the slice management module is acknowledged, and the slice management module exits all the basic applications of the slice, and notifies the resource management module to exit the slice.
  • step 4 the resource management module reclaims all previous resources allocated to the slice, and removes the previous slice designation and then responds to the slice management module.
  • step 5 the slice management module responds to the user deletion success, and the operation is completed.
  • the embodiment of the present application further provides a processing apparatus configured to implement device slicing, including a memory and a processor, wherein the memory stores the following instructions executable by the processor:
  • the corresponding type process file is obtained according to the first target type, and is obtained according to the first target function.
  • Corresponding function process file is obtained according to the first target type, and is obtained according to the first target function.
  • a first target device slice is generated based on the obtained type process file and the function process file.
  • the following instructions are executable by the processor: acquiring a type process file corresponding to the first target type according to the pre-established first correspondence, and acquiring the first according to the pre-established second correspondence.
  • the memory when there is a first target device slice in the node device, the memory further stores the following instructions executable by the processor: generating prompt information that the device slice that the user desires to establish is already present in the node device.
  • the memory further stores: the following instructions executable by the processor: determining, according to the third correspondence that is established in advance, whether the first target device slice exists in the node device; wherein the third correspondence is in the node device
  • the stored device slice corresponds to the identity of the user to which the device slice belongs, the type of the device slice, and the function of the device slice.
  • the memory further stores the following instructions executable by the processor: updating the third correspondence according to the correspondence between the first target identifier, the first target type, the first target function, and the first target device slice.
  • the memory further stores the following instructions executable by the processor: determining whether the identifier of the user belonging to the third correspondence is the same as the first target identifier, the type is the same as the first target type, and the function is The first target has the same device slice.
  • the first target device slice exists in the node device.
  • the memory further stores the following instructions executable by the processor: obtaining port resources in the self that are assignable to the first target device slice.
  • the obtained port resource is marked to indicate that the port resource belongs to the first target device slice.
  • the memory further stores the following instructions executable by the processor: acquiring an identifier of a user to which the device slice deletion instruction belongs, a type and function of the device slice that the user desires to delete, and using the obtained identifier as the second target The identifier, the type obtained is taken as the second target type, and the obtained function is taken as the second target function.
  • the second target device slice exists in the node device, the second target device slice is acquired and deleted.
  • the memory when there is no second target device slice in the node device, the memory further stores the following instructions executable by the processor: generating prompt information that the device slice that the user desires to delete does not exist in the node device.
  • the memory when the second target device slice has port level protection, the memory further stores the following instructions executable by the processor: a service switching operation that triggers the second target device slice.
  • the port resource pre-allocated to the second target device slice is reclaimed, and the second target device slice is deleted.
  • the embodiment of the present application further provides a computer readable storage medium, where the computer executable instructions are stored, and the computer executable instructions are configured to perform the following steps: acquiring an identifier of a user to which the device slice creation instruction belongs, and a device slice desired to be created.
  • the obtained identifier is used as the first target identifier, and the obtained type is used as the first target type, and the obtained function is used as the first target function; when the node device does not exist with the first target identifier and the first target
  • the corresponding type process file is obtained according to the first target type, and the corresponding function process file is obtained according to the first target function; according to the obtained type process file and the function process The file generates a first target device slice.
  • the computer executable instructions are configured to: obtain a type process file corresponding to the first target type according to the pre-established first correspondence, and obtain a first target function corresponding according to the pre-established second correspondence.
  • the function file of the function process wherein the first correspondence is a correspondence between the type of the device slice and the type process file, and the second correspondence is a correspondence between the function of the device slice and the function process file.
  • the computer executable instructions are further arranged to perform the step of generating prompt information that the device slice that the user desires to establish is already present in the node device.
  • the computer executable instructions are further configured to: determine whether the first target device slice exists in the node device according to the pre-established third correspondence; wherein the third correspondence is a device stored in the node device The correspondence between the slice and the function of the user to which the device slice belongs, the type of the device slice, and the function of the device slice.
  • the computer executable instructions are further arranged to perform the step of updating the third correspondence according to a correspondence of the first target identifier, the first target type, the first target function, and the first target device slice.
  • the computer executable instructions are configured to: determine whether the identity of the user belonging to the third correspondence is the same as the first target identifier, the type is the same as the first target type, and the function and the first target function are Same device slice.
  • the first target device slice exists in the node device.
  • the computer executable instructions are further arranged to perform the step of obtaining a port resource in the node device that is assignable to the first target device slice.
  • the obtained port resource is marked to indicate that the port resource belongs to the first target device slice.
  • the computer executable instructions are further configured to: obtain an identifier of a user to which the device slice deletion instruction belongs, a type and function of a device slice that the user desires to delete, and use the obtained identifier as a second target identifier, and The obtained type is used as the second target type, and the obtained function is taken as the second target function.
  • the second target device slice exists in the node device, the second target device slice is deleted.
  • the computer executable instructions are further configured to perform the step of generating prompt information that the device slice that the user desires to delete does not exist in the node device.
  • the computer executable instructions are further configured to perform the following steps: triggering a service switching operation of the second target device slice; acquiring the second target device slice, and controlling the Two target device slices exit all applications.
  • the port resource pre-allocated to the second target device slice is reclaimed, and the second target device slice is deleted.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Stored Programmes (AREA)

Abstract

本文公开了一种设备切片的处理方法及节点设备，包括：节点设备获取设备切片创建指令所属用户的标识、期望创建的设备切片的类型和功能；当自身中不存在与获得的标识、类型和功能对应的设备切片时，根据获得的类型获取对应的类型进程文件，根据获得的功能获取对应的功能进程文件；根据获得的类型进程文件和功能进程文件生成设备切片。

Description

一种设备切片的处理方法、装置及计算机可读存储介质
本申请要求在2018年04月13日提交中国专利局、申请号为201810332492.2的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，例如一种设备切片的处理方法、装置及计算机可读存储介质。
背景技术
随着第五代移动通信(5th-Generation，5G)时代的来临，各种连接的数量呈现几何级别的增长，如何避免过多连接造成的网络拥塞，已成为各大设备商、运营商共同关注的焦点问题。网络切片技术正是为解决该问题而产生的，该技术本质上就是将运营商的物理网络划分成多个虚拟网络，并根据不同的服务需求，比如带宽、时延、可靠性等不同的要求来划分，以满足不同的应用场景和需求。
对于网络中单个节点设备来说，当用作提供某种服务时，实际是在自身中运行这种服务对应的设备切片，因此当该节点设备一旦用于提供其他新的服务时，就需要重新获取新服务对应的设备切片，而新的设备切片是需要从外部(可以是互联网或其他地方)获取新的服务对应的类型程序和功能程序后一并运行才能得到的。
因此，整个设备切片的获取过程十分繁琐，用户体验低下。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本申请实施例提供了一种设备切片的管理方法、装置及计算机可读存储介质，能够简化设备切片的获取过程，提高用户体验。
本申请实施例提供了一种设备切片的管理方法方法，包括：节点设备获取设备切片创建指令所属用户的标识、期望创建的设备切片的类型和功能，并将 获得的标识作为第一目标标识，将获得的类型作为第一目标类型，将获得的功能作为第一目标功能；当节点设备中不存在与所述第一目标标识、所述第一目标类型和所述第一目标功能均对应的第一目标设备切片时，根据所述第一目标类型获取对应的类型进程文件，并根据所述第一目标功能获取对应的功能进程文件；根据获得的类型进程文件和功能进程文件生成所述第一目标设备切片。
本申请实施例还提供了一种设备切片的处理装置，包括：处理器和存储器，其中，存储器中存储有以下可被处理器执行的指令：获取设备切片创建指令所属用户的标识、期望创建的设备切片的类型和功能，并将获得的标识作为第一目标标识，将获得的类型作为第一目标类型，将获得的功能作为第一目标功能；当节点设备中不存在与所述第一目标标识、所述第一目标类型和所述第一目标功能均对应的第一目标设备切片时，根据所述第一目标类型获取对应的类型进程文件，并根据所述第一目标功能获取对应的功能进程文件；根据获得的类型进程文件和功能进程文件生成所述第一目标设备切片。
本申请实施例还提供了一种计算机可读存储介质，所述存储介质上存储有计算机可执行指令，所述计算机可执行指令设置为执行以下步骤：获取设备切片创建指令所属用户的标识、期望创建的设备切片的类型和功能，并将获得的标识作为第一目标标识，将获得的类型作为第一目标类型，将获得的功能作为第一目标功能；当节点设备中不存在与所述第一目标标识、所述第一目标类型和所述第一目标功能均对应的第一目标设备切片时，根据所述第一目标类型获取对应的类型进程文件，并根据所述第一目标功能获取对应的功能进程文件；根据获得的类型进程文件和功能进程文件生成所述第一目标设备切片。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图说明
附图用来提供对本申请技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1为本申请实施例提供的一种设备切片的处理方法的流程示意图；
图2为本申请实施例提供的一种支持网络切片的通信设备软件架构示意图；
图3为本申请实施例提供的一种设备切片的创建方法的流程示意图；
图4为本申请实施例提供的一种设备切片的删除方法的流程示意图。
具体实施方式
下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
本申请实施例提供一种设备切片的处理方法，如图1所示，该方法包括步骤101至步骤103。
在步骤101中，节点设备获取设备切片创建指令所属用户的标识、期望创建的设备切片的类型和功能，并将获得的标识作为第一目标标识，将获得的类型作为第一目标类型，将获得的功能作为第一目标功能。
需要说明的是，节点设备可以是服务器，或是其他能够创建设备切片的设备，本申请对此不作限制。
在一实施例中，第一目标类型是用户所要创建的第一目标设备切片的所属类型，例如，车联网类型、家电联网类型等，这些类型可以是节点设备预先划分的，第一目标功能是用户所要创建的第一目标设备切片所具备的功能，例如，蓝牙功能、无线保真(WIreless-Fidelity，Wi-Fi)功能等。一个设备切片的所属类型只能有一个，但所具备的功能可以有多个，例如，具备蓝牙功能和Wi-Fi功能的家电联网设备切片，类型为家电联网类型，所具备的功能为蓝牙功能和Wi-Fi功能。
在一实施例中，第一目标类型和第一目标功能的可以是用户在节点设备交互界面中输入，进而节点设备获取的。
在步骤102中，当节点设备中不存在与第一目标标识、第一目标类型和第一目标功能均对应的第一目标设备切片时，根据第一目标类型获取对应的类型进程文件，并根据第一目标功能获取对应的功能进程文件。
在步骤103中，根据获得的类型进程文件和功能进程文件生成第一目标设备切片。
本申请实施例提供的设备切片的处理方法，由于根据第一目标类型和第一 目标功能就能够获取生成目标设备切片的类型进程文件和功能进程文件，从而避免了创建新的设备切片时需要从外部查找相应类型进程文件和功能进程的繁琐过程，提高了用户体验。
在一实施例中，所述根据第一目标类型获取对应的类型进程文件，并根据第一目标功能获取对应的功能进程文件，包括：根据预先建立的第一对应关系获取第一目标类型对应的类型进程文件，并根据预先建立的第二对应关系获取第一目标功能对应的功能进程文件。
其中，第一对应关系为设备切片的类型与类型进程文件的对应关系，第二对应关系为设备切片的功能与功能进程文件的对应关系。
在一实施例中，第一对应关系可以以表格的形式进行表示，假设自身存在的设备切片的类型有车联网类型和家电联网类型，车联网类型对应的类型进程文件为文件A1，家电联网类型对应的类型进程文件为文件A2，那么第一对应关系可以如表1所示。
设备切片的类型 类型进程文件
车联网 文件A1
家电联网 文件A2
表1
在一实施例中，第二对应关系可以以表格的形式进行表示，假设自身存在的设备切片的功能有远程操作功能、Wi-Fi功能和蓝牙功能，远程操作功能对应的功能进程文件为文件B1，Wi-Fi功能对应的功能进程文件为文件B2，蓝牙功能对应的功能进程文件为文件B3，那么第二对应关系可以如表2所示。
设备切片的功能 功能进程文件
远程操作功能 文件B1
Wi-Fi功能 文件B2
蓝牙功能 文件B3
表2
当节点设备中存在第一目标设备切片时，还包括：生成用户期望建立的设备切片已存在于节点设备中的提示信息。
在一实施例中，根据预先建立的第二对应关系获取第一目标类型对应的类型进程文件之前，还包括：根据预先建立的第三对应关系判断节点设备中是否 存在第一目标设备切片；其中，第三对应关系为节点设备中存储的设备切片分别与设备切片所属用户的标识、设备切片的类型以及设备切片的功能之间的对应关系。
在一实施例中，第三对应关系也可以以表格的形式进行表示，假设存在的设备切片有设备切片A、设备切片B和设备切片C。设备切片A的所属用户为用户甲，类型为车联网类型，功能为远程操作功能和Wi-Fi功能；设备切片B的所属用户为用户乙，类型为家电联网类型，功能为蓝牙功能；设备切片C的所属用户为用户乙，类型为车联网类型，功能为远程操作功能和蓝牙功能，那么第三对应关系可以如表3所示。
Figure PCTCN2019082421-appb-000001
表3
在一实施例中，生成第一目标设备切片之后，还包括：根据第一目标标识、第一目标类型、第一目标功能和第一目标设备切片的对应关系更新第三对应关系。
在一实施例中，根据预先建立的第三对应关系判断节点设备中是否存在第一目标设备切片，包括：判断第三对应关系中是否存在所属用户的标识与第一目标标识相同，类型与第一目标类型相同，且功能与第一目标功能相同的设备切片。
如果第三对应关系中存在类型与第一目标类型相同，且功能与第一目标功能相同的设备切片，确定节点设备中存在第一目标设备切片。
在一实施例中，如果第三关系中不存在所属用户的标识与第一目标标识相同，类型与第一目标类型相同，且功能与第一目标功能相同的设备切片，确定自身不存在第一目标设备切片。第三关系中不存在类型与第一目标类型相同，且功能与第一目标功能相同的设备切片的情况包括三种情形：第一种情形为第 三关系中不存在类型与第一目标类型相同，但存在功能与第一目标功能相同的设备切片；第二种情形为第三关系中存在类型与第一目标类型相同，但不存在功能与第一目标功能相同的设备切片；第三种情形为第三关系中不存在类型与第一目标类型相同，且不存在功能与第一目标功能相同的设备切片。
在一实施例中，生成第一目标设备切片之后，还包括：获取节点设备中可分配给第一目标设备切片的端口资源。
对获得的端口资源进行标记，以表示该端口资源属于第一目标设备切片。
在一实施例中，节点设备获取设备切片创建指令所属用户的标识、期望创建的设备切片的类型和功能之前或之后，还包括：获取设备切片删除指令所述用户的标识、用户期望删除的设备切片的类型和功能，并将获得的标识作为第二目标标识，将获得的类型作为第二目标类型，将获得的功能作为第二目标功能。
根据第三对应关系判断节点设备中是否存在与第二目标标识、第二目标类型和第二目标功能均对应的第二目标设备切片。
当节点设备中存在第二目标设备切片时，获取并删除第二目标设备切片。
在一实施例中，根据第三对应关系判断节点设备中是否存在与获得的第二目标类型和第二目标功能对应的第二目标设备切片，包括：判断第三对应关系中是否存在所属用户的标识与第二目标标识相同，类型与第二目标类型相同，且功能与第二目标功能相同的设备切片。
如果第三对应关系中存在所属用户的标识与第二目标标识相同，类型与第二目标类型相同，且功能与第二目标功能相同的设备切片，确定节点设备中存在第二目标设备切片。
在一实施例中，当节点设备中不存在第二目标设备切片时，还包括：生成用户期望删除的设备切片不存在于节点设备中的提示信息。
在一实施例中，当第二目标设备切片存在端口级别的保护时，获取并删除第二目标设备切片之前，还包括：触发第二目标设备切片的业务倒换操作。
获取并删除第二目标设备切片，包括：获取第二目标设备切片，并控制第二目标设备切片退出所有应用。
将预先分配给第二目标设备切片的端口资源回收，并删除第二目标设备切片。
需要说明的是，控制第二目标设备切片退出的所有应用指的是操作系统本身应用和运行在操作系统上的其他应用。
本申请还提供一种支持网络切片的通信设备软件架构示意图，如图2所示，该设备软件主要包括设备操作系统、版本管理、资源管理、切片管理等四个模块，其中操作系统提供系统级别的切片技术，如当前常用docker技术。版本管理模块负责所有版本的文件的管理，如切片类型与版本文件的对应关系，可以是如下格式：
切片类型1：文件1，文件2，文件3。
切片类型2：文件4，文件5，文件6，文件7。
切片功能1：文件8，文件9。
切片功能2：文件10，文件11。
其中，切片类型和切片功能可以对应一到多个文件，或者文件包，而切片功能为可选项，用户可以根据自己的需求来选择和配置。而资源管理模块主要负责设备的单板、端口、内存、中央处理器(Central Processing Unit，CPU)等物理资源的管理。切片管理模块负责整个设备的切片管理，根据用户的配置向版本管理模块请求版本信息，并从资源管理模块请求切片需要相关的资源。
基于图2对应的实施例提供的通信设备软件架构，本申请实施例还提供一种设备切片的创建方法，如图3所示，该方法包括步骤1至步骤5。
在步骤1中，创建切片时用户，用户会为切片指定一个唯一的关键字，如切片ID，首先，切片管理模块会判断是否已经有相同ID的切片，如果有则进入步骤5，否则进入下一步。
在步骤2中，设备上没有相同ID的切片，切片管理模块根据切片类型和切片功能向版本管理模块请求版本文件信息，收到应答后进入下一步。
在步骤3中，切片管理模块根据请求到的版本信息启动切片的基础软件，包括切片自己独立的版本管理客户端模块。
在步骤4中，切片的版本管理客户端模块根据从切片管理模块同步下来的版本信息下载版本文件，然后运行对应的版本文件，切片创建完成。
在步骤5中，如果已经有相同ID的切片存在，则判断切片功能是否有更新，如果有则进入步骤4，否则应答用户切片已经创建。
基于图2对应的实施例提供的通信设备软件架构，本申请实施例还提供一 种设备切片的资源分配方法，如图4所示，该方法包括步骤1至步骤4。
在步骤1中，切片管理模块收到用户为切片n分配一个物理资源的命令。
在步骤2中，切片管理模块向资源管理模块请求该资源，资源管理模块判断该资源是否被其他切片占用，如果有则返回用户资源不可用，否则进入下一步。
在步骤3中，资源管理模块将该物理资源打上切片n的标示，如切片ID，并保存到内存和存储介质中，这样才能保证下一次启动后能够正确的恢复用户配置。
在步骤4中，切片管理模块收到资源管理模块的成功应答后，将资源的信息发送给切片n自己的资源管理模块，切片n将该资源信息保存到自己的数据库中。
基于图2对应的实施例提供的通信设备软件架构，本申请实施例还提供一种设备切片的删除方法，该方法包括步骤1至步骤5。
在步骤1中，切片管理模块收到用户下发的切片删除的命令，判断该切片是否存在保护，如果该切片存在保护则先触发业务的倒换，如果没有保护则进入下一步。
在步骤2中，切片管理模块收到倒换完成或者本身是没有保护的模块，切片管理模块通知切片进行退出操作。
在步骤3中，切片完成应用进程的退出后应答切片管理模块，切片管理模块将切片的所有基础应用退出，同时通知资源管理模块切片退出。
在步骤4中，资源管理模块将之前所有分配给该切片的资源回收，去掉之前的切片标示后应答切片管理模块。
在步骤5中，切片管理模块应答用户删除成功，操作完成。
本申请实施例还提供一种设置为实现设备切片的处理装置，包括存储器和处理器，其中，存储器中存储有以下可被处理器执行的指令：
获取设备切片创建指令所属用户的标识、期望创建的设备切片的类型和功能，并将获得的标识作为第一目标标识，将获得的类型作为第一目标类型，将获得的功能作为第一目标功能。
当节点设备中不存在与第一目标标识、第一目标类型和第一目标功能均对应的第一目标设备切片时，根据第一目标类型获取对应的类型进程文件，并根 据第一目标功能获取对应的功能进程文件。
根据获得的类型进程文件和功能进程文件生成第一目标设备切片。
在一实施例中，存储器中存储有以下可被处理器执行的指令：根据预先建立的第一对应关系获取第一目标类型对应的类型进程文件，并根据预先建立的第二对应关系获取第一目标功能对应的功能进程文件；其中，第一对应关系为设备切片的类型与类型进程文件的对应关系，第二对应关系为设备切片的功能与功能进程文件的对应关系。
在一实施例中，当节点设备中存在第一目标设备切片时，存储器中还存储有以下可被处理器执行的指令：生成用户期望建立的设备切片已存在于节点设备中的提示信息。
在一实施例中，存储器中还存储有以下可被处理器执行的指令：根据预先建立的第三对应关系判断节点设备中是否存在第一目标设备切片；其中，第三对应关系为节点设备中存储的设备切片分别与设备切片所属用户的标识、设备切片的类型以及设备切片的功能之间的对应关系。
在一实施例中，存储器中还存储有以下可被处理器执行的指令：根据第一目标标识、第一目标类型、第一目标功能和第一目标设备切片的对应关系更新第三对应关系。
在一实施例中，存储器中还存储有以下可被处理器执行的指令：判断第三对应关系中是否存在所属用户的标识与第一目标标识相同，类型与第一目标类型相同，且功能与第一目标功能相同的设备切片。
如果第三对应关系中存在所属用户的标识与第一目标标识相同，类型与第一目标类型相同，且功能与第一目标功能相同的设备切片，确定节点设备中存在第一目标设备切片。
在一实施例中，存储器中还存储有以下可被处理器执行的指令：获取自身中可分配给第一目标设备切片的端口资源。
对获得的端口资源进行标记，以表示该端口资源属于第一目标设备切片。
在一实施例中，存储器中还存储有以下可被处理器执行的指令：获取设备切片删除指令所属用户的标识、用户期望删除的设备切片的类型和功能，并将获得的标识作为第二目标标识，将获得的类型作为第二目标类型，将获得的功能作为第二目标功能。
根据第三对应关系判断节点设备中是否存在与第二目标标识、第二目标类型和第二目标功能均对应的第二目标设备切片。
当节点设备中存在第二目标设备切片时，获取并删除第二目标设备切片。
在一实施例中，当节点设备中不存在第二目标设备切片时，存储器中还存储有以下可被处理器执行的指令：生成用户期望删除的设备切片不存在于节点设备中的提示信息。
在一实施例中，当第二目标设备切片存在端口级别的保护时，存储器中还存储有以下可被处理器执行的指令：触发第二目标设备切片的业务倒换操作。
获取第二目标设备切片，并控制第二目标设备切片退出所有应用。
将预先分配给第二目标设备切片的端口资源回收，并删除第二目标设备切片。
本申请实施例还提供一种计算机可读存储介质，存储介质上存储有计算机可执行指令，计算机可执行指令设置为执行以下步骤：获取设备切片创建指令所属用户的标识、期望创建的设备切片的类型和功能，并将获得的标识作为第一目标标识，将获得的类型作为第一目标类型，将获得的功能作为第一目标功能；当节点设备中不存在与第一目标标识、第一目标类型和第一目标功能均对应的第一目标设备切片时，根据第一目标类型获取对应的类型进程文件，并根据第一目标功能获取对应的功能进程文件；根据获得的类型进程文件和功能进程文件生成第一目标设备切片。
在一实施例中，计算机可执行指令设置为执行以下步骤：根据预先建立的第一对应关系获取第一目标类型对应的类型进程文件，并根据预先建立的第二对应关系获取第一目标功能对应的功能进程文件；其中，第一对应关系为设备切片的类型与类型进程文件的对应关系，第二对应关系为设备切片的功能与功能进程文件的对应关系。
在一实施例中，当节点设备中存在第一目标设备切片时，计算机可执行指令还设置为执行以下步骤：生成用户期望建立的设备切片已存在于节点设备中的提示信息。
在一实施例中，计算机可执行指令还设置为执行以下步骤：根据预先建立的第三对应关系判断节点设备中是否存在第一目标设备切片；其中，第三对应关系为节点设备中存储的设备切片分别与设备切片所属用户的标识、设备切片 的类型以及设备切片的功能之间的对应关系。
在一实施例中，计算机可执行指令还设置为执行以下步骤：根据第一目标标识、第一目标类型、第一目标功能和第一目标设备切片的对应关系更新第三对应关系。
在一实施例中，计算机可执行指令设置为执行以下步骤：判断第三对应关系中是否存在所属用户的标识与第一目标标识相同，类型与第一目标类型相同，且功能与第一目标功能相同的设备切片。
如果第三对应关系中存在所属用户的标识与第一目标标识相同，类型与第一目标类型相同，且功能与第一目标功能相同的设备切片，确定节点设备中存在第一目标设备切片。
在一实施例中，计算机可执行指令还设置为执行以下步骤：获取节点设备中可分配给第一目标设备切片的端口资源。
对获得的端口资源进行标记，以表示该端口资源属于第一目标设备切片。
在一实施例中，计算机可执行指令还设置为执行以下步骤：获取设备切片删除指令所属用户的标识、用户期望删除的设备切片的类型和功能，并将获得的标识作为第二目标标识，将获得的类型作为第二目标类型，将获得的功能作为第二目标功能。
根据第三对应关系判断节点设备中是否存在与第二目标标识、第二目标类型和第二目标功能均对应的第二目标设备切片。
当节点设备中存在第二目标设备切片时，删除第二目标设备切片。
在一实施例中，当节点设备中不存在第二目标设备切片时，计算机可执行指令还设置为执行以下步骤：生成用户期望删除的设备切片不存在于节点设备中的提示信息。
在一实施例中，第二目标设备切片存在端口级别的保护时，计算机可执行指令还设置为执行以下步骤：触发第二目标设备切片的业务倒换操作；获取第二目标设备切片，并控制第二目标设备切片退出所有应用。
将预先分配给第二目标设备切片的端口资源回收，并删除第二目标设备切片。

Claims (12)

  1. 一种设备切片的处理方法，包括：
    节点设备获取设备切片创建指令所属用户的标识、期望创建的设备切片的类型和功能，并将获得的标识作为第一目标标识，将获得的类型作为第一目标类型，将获得的功能作为第一目标功能；
    在节点设备中不存在与所述第一目标标识、所述第一目标类型以及所述第一目标功能对应的第一目标设备切片的情况下，根据所述第一目标类型获取与所述第一目标类型对应的类型进程文件，并根据所述第一目标功能获取与所述第一功能类型对应的功能进程文件；
    根据获得的类型进程文件和功能进程文件生成所述第一目标设备切片。
  2. 根据权利要求1所述的处理方法，其中，所述根据第一目标类型获取与所述第一目标类型对应的类型进程文件，并根据第一目标功能获取与所述第一功能类型对应的功能进程文件，包括：
    根据预先建立的第一对应关系获取所述第一目标类型对应的类型进程文件，并根据预先建立的第二对应关系获取所述第一目标功能对应的功能进程文件；其中，所述第一对应关系为设备切片的类型与类型进程文件的对应关系，所述第二对应关系为设备切片的功能与功能进程文件的对应关系。
  3. 根据权利要求1所述的处理方法，在所述节点设备中存在所述第一目标设备切片的情况下，还包括：
    生成用户期望建立的设备切片已存在于所述节点设备中的提示信息。
  4. 根据权利要求1所述的处理方法，所述根据预先建立的第二对应关系获取所述第一目标类型对应的类型进程文件之前，还包括：
    根据预先建立的第三对应关系判断所述节点设备中是否存在所述第一目标设备切片；其中，所述第三对应关系为所述节点设备中存储的设备切片分别与设备切片所属用户的标识、设备切片的类型以及设备切片的功能之间的对应关系。
  5. 根据权利要求4所述的处理方法，所述生成第一目标设备切片之后，还包括：
    根据所述第一目标标识、所述第一目标类型、所述第一目标功能和所述第一目标设备切片的对应关系更新所述第三对应关系。
  6. 根据权利要求4所述的处理方法，其中，所述根据预先建立的第三对应 关系判断节点设备中是否存在第一目标设备切片，包括：
    判断所述第三对应关系中是否存在所属用户的标识与所述第一目标标识相同，类型与所述第一目标类型相同，且功能与所述第一目标功能相同的设备切片；
    基于所述第三对应关系中存在所属用户的标识与所述第一目标标识相同，类型与所述第一目标类型相同，且功能与所述第一目标功能相同的设备切片的判断结果，确定所述节点设备中存在所述第一目标设备切片。
  7. 根据权利要求1所述的处理方法，所述生成第一目标设备切片之后，还包括：
    获取所述节点设备中可分配给所述第一目标设备切片的端口资源；
    对获得的端口资源进行标记，以表示该端口资源属于所述第一目标设备切片。
  8. 根据权利要求4所述的处理方法，所述节点设备获取设备切片创建指令所属用户的标识、期望创建的设备切片的类型和功能之前或之后，还包括：
    获取设备切片删除指令所属用户的标识、所述用户期望删除的设备切片的类型和功能，并将获得的标识作为第二目标标识，将获得的类型作为第二目标类型，将获得的功能作为第二目标功能；
    根据所述第三对应关系判断所述节点设备中是否存在与所述第二目标标识、所述第二目标类型和所述第二目标功能对应的第二目标设备切片；
    在所述节点设备中存在所述第二目标设备切片的情况下，删除所述第二目标设备切片。
  9. 根据权利要求8所述的处理方法，在所述节点设备中不存在所述第二目标设备切片的情况下，还包括：
    生成用户期望删除的设备切片不存在于所述节点设备中的提示信息。
  10. 根据权利要求8所述的处理方法，在所述第二目标设备切片存在端口级别的保护的情况下，所述获取并删除第二目标设备切片之前，还包括：
    触发所述第二目标设备切片的业务倒换操作；
    所述删除第二目标设备切片，包括：
    获取所述第二目标设备切片，并控制所述第二目标设备切片退出所有应用；
    将预先分配给所述第二目标设备切片的端口资源回收，并删除所述第二目 标设备切片。
  11. 一种设备切片的处理装置，其中，包括：处理器和存储器，其中，存储器中存储有以下可被处理器执行的指令：
    获取设备切片创建指令所属用户的标识、期望创建的设备切片的类型和功能，并将获得的标识作为第一目标标识，将获得的类型作为第一目标类型，将获得的功能作为第一目标功能；
    在节点设备中不存在与所述第一目标标识、所述第一目标类型和所述第一目标功能对应的第一目标设备切片的情况下，根据所述第一目标类型获取与所述第一目标类型对应的类型进程文件，并根据所述第一目标功能获取与所述第一功能类型对应的功能进程文件；
    根据获得的类型进程文件和功能进程文件生成所述第一目标设备切片。
  12. 一种计算机可读存储介质，所述存储介质上存储有计算机可执行指令，所述计算机可执行指令设置为执行以下步骤：
    获取设备切片创建指令所属用户的标识、期望创建的设备切片的类型和功能，并将获得的标识作为第一目标标识，将获得的类型作为第一目标类型，将获得的功能作为第一目标功能；
    在节点设备中不存在与所述第一目标标识、所述第一目标类型和所述第一目标功能均对应的第一目标设备切片的情况下，根据所述第一目标类型获取与所述第一目标类型对应的类型进程文件，并根据所述第一目标功能获取与所述第一功能类型对应的功能进程文件；
    根据获得的类型进程文件和功能进程文件生成所述第一目标设备切片。
PCT/CN2019/082421 2018-04-13 2019-04-12 一种设备切片的处理方法、装置及计算机可读存储介质 WO2019196926A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810332492.2 2018-04-13
CN201810332492.2A CN110380885A (zh) 2018-04-13 2018-04-13 一种设备切片的处理方法、装置及计算机可读存储介质

Publications (1)

Publication Number Publication Date
WO2019196926A1 true WO2019196926A1 (zh) 2019-10-17

Family

ID=68163068

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/082421 WO2019196926A1 (zh) 2018-04-13 2019-04-12 一种设备切片的处理方法、装置及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN110380885A (zh)
WO (1) WO2019196926A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112954668B (zh) * 2019-12-11 2022-07-12 华为技术有限公司 通信方法、装置及设备
CN115580881A (zh) * 2021-06-18 2023-01-06 中兴通讯股份有限公司 网络切片业务不中断的升级方法及装置、存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107295609A (zh) * 2016-03-30 2017-10-24 中兴通讯股份有限公司 网络切片处理方法及装置、终端、基站
CN107306438A (zh) * 2016-04-23 2017-10-31 华为技术有限公司 一种无线接入网切片的生成方法、无线接入网及切片管理器
WO2018038489A1 (ko) * 2016-08-22 2018-03-01 삼성전자 주식회사 무선 통신 시스템에서, 단말과 써드 파티 서버 간의 인증 요청 방법 및, 이를 위한 단말 및 네트워크 슬라이스 인스턴스 관리 장치
CN107889169A (zh) * 2016-09-29 2018-04-06 华为技术有限公司 网络切片的建立方法和装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106657194B (zh) * 2015-11-02 2020-05-08 中兴通讯股份有限公司 一种网络切片能力开放的方法、装置及系统
CN107317712A (zh) * 2017-06-30 2017-11-03 广东工业大学 一种网络切片的创建方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107295609A (zh) * 2016-03-30 2017-10-24 中兴通讯股份有限公司 网络切片处理方法及装置、终端、基站
CN107306438A (zh) * 2016-04-23 2017-10-31 华为技术有限公司 一种无线接入网切片的生成方法、无线接入网及切片管理器
WO2018038489A1 (ko) * 2016-08-22 2018-03-01 삼성전자 주식회사 무선 통신 시스템에서, 단말과 써드 파티 서버 간의 인증 요청 방법 및, 이를 위한 단말 및 네트워크 슬라이스 인스턴스 관리 장치
CN107889169A (zh) * 2016-09-29 2018-04-06 华为技术有限公司 网络切片的建立方法和装置

Also Published As

Publication number Publication date
CN110380885A (zh) 2019-10-25

Similar Documents

Publication Publication Date Title
US11146453B2 (en) Method and apparatus for creating network slice, and communications system
US10728135B2 (en) Location based test agent deployment in virtual processing environments
US10061613B1 (en) Idempotent task execution in on-demand network code execution systems
US9999030B2 (en) Resource provisioning method
WO2018149221A1 (zh) 一种设备管理方法及网管系统
WO2019007345A1 (zh) 网络切片的选择方法、装置及系统、存储介质
JP2020530722A (ja) Ｐｄｕタイプ設定方法、ｕｅポリシー設定方法、および関連エンティティ
US11687354B2 (en) Virtual machine management using onboarding operations and openstack control
WO2017020612A1 (zh) 一种容器部署方法及装置
CN110149409B (zh) 云主机元数据服务管理方法、系统、设备及存储介质
CN113037794B (zh) 计算资源配置调度方法、装置及系统
US20210320845A1 (en) Network function nf management method and nf management device
WO2021227954A1 (zh) 基于容器集群的应用访问请求处理
WO2018218977A1 (zh) 一种编排软件定义网络的方法及sdn控制器
WO2014101475A1 (zh) 云平台应用部署方法及装置
CN111061432B (zh) 一种业务迁移方法、装置、设备及可读存储介质
WO2021109750A1 (zh) 节点管理方法、装置、设备、存储介质和系统
EP3879875A1 (en) Resource change method and device, apparatus, and storage medium
WO2019196926A1 (zh) 一种设备切片的处理方法、装置及计算机可读存储介质
WO2017054533A1 (zh) 云互通的外部资源管理方法、装置及系统
CN105897865B (zh) 一种协议无关的网络文件服务管理系统和方法
US9898273B1 (en) Dynamically updating APIS based on updated configuration file of a computing system
WO2019034091A1 (zh) 分布式数据计算的分配方法、装置、服务器及存储介质
US20150079966A1 (en) Methods for facilitating telecommunication network administration and devices thereof
EP3435626B1 (en) Table connection method in distributed database system, and distributed database system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19785226

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 12/02/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19785226

Country of ref document: EP

Kind code of ref document: A1