Network slice management method and apparatus, gateway device, and storage medium

Abstract

The application discloses a network slice management method and device, a gateway device and a storage medium, and belongs to the technical field of communication. The method comprises the following steps: acquiring characteristic information of a hanging device, wherein the characteristic information is created by a gateway device based on a networking protocol; and according to the characteristic information, mapping a service data stream of the hanging device into a corresponding network slice for communication. In the application, the gateway device and the hanging device thereof create the characteristic information of the hanging device based on the networking protocol, the gateway device acquires the characteristic information of the hanging device, maps the service data stream of the hanging device into the corresponding network slice, and communicates through the corresponding network slice, so that the data stream of the service data of the hanging device is not needed to be acquired, the amount of data to be processed during network slicing is reduced, and the accuracy and efficiency of the gateway device during network slicing are improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a network slicing management method, apparatus, gateway device, and storage medium. Background Technology

[0002] With the development of science and technology, various terminal devices have appeared in people's daily lives, allowing them to use them for entertainment, work, and other purposes. In daily home life, various terminal devices establish network connections with base stations or network devices through gateway devices to transmit data. For example, a gateway device can be a router, through which various terminal devices establish network connections. Currently, to facilitate communication between different terminal devices, 5G network systems typically employ network slicing for different terminal devices. Examples include eMBB slicing based on Enhanced Mobile Broadband (eMBB), uRLLC slicing based on ultra-reliable and low-latency communication (uRLLC), and mMTC slicing based on massive machine-type communications (mMTC). In these various network slicing implementation schemes, specific identification rules need to be formulated based on the characteristics of the data streams of the service data forwarded by the gateway device to achieve network slicing.

[0003] Typically, the same service of a terminal device will generate multiple data streams. The above solution not only requires processing a large amount of data, but also has low accuracy, resulting in the same terminal device being assigned to different network slices. Summary of the Invention

[0004] To address the problems of existing technologies, reduce the amount of data that needs to be processed during network slicing, and improve the accuracy and efficiency of network slicing on the terminal side, this application provides a network slicing management method, apparatus, gateway device, and storage medium.

[0005] In one aspect, this application provides a network slicing management method applied to a gateway device, wherein the gateway device is connected to downstream devices based on a networking protocol, the method comprising:

[0006] Obtain the characteristic information of the downstream device, wherein the characteristic information is created by the gateway device accessed by the downstream device based on the networking protocol;

[0007] Based on the aforementioned feature information, the service data stream of the downstream device is mapped to the corresponding network slice, and communication is performed through the corresponding network slice.

[0008] In one aspect, this application provides a network slicing management device applied to a gateway device, the gateway device being connected to downstream devices based on a networking protocol, the device comprising:

[0009] The information acquisition module is used to acquire the feature information of the downstream device, wherein the feature information is created by the gateway device that the downstream device accesses based on the networking protocol;

[0010] The network slicing module is used to map the service data stream of the downstream device to the corresponding network slice according to the feature information, and to communicate through the corresponding network slice.

[0011] In another aspect, this application provides a gateway device comprising a processor and a memory, the memory storing a computer program executed by the processor to implement the network slicing management method as described in one aspect.

[0012] In another aspect, this application provides a computer-readable storage medium storing a computer program that is executed by a processor to implement the network slice management method as described in one aspect.

[0013] In this application, the gateway device and its downstream devices, based on the networking protocol, will create characteristic information belonging to the downstream devices. By obtaining the characteristic information of its downstream devices through the gateway device, the service data stream of the downstream devices is mapped to the corresponding network slice, and communication is carried out through the corresponding network slice. Therefore, it is not necessary to obtain the data stream of the service data of the downstream devices. Network slicing is performed directly through the characteristic information created based on the networking protocol, thereby reducing the amount of data that needs to be processed during network slicing and improving the accuracy and efficiency of the gateway device in performing network slicing. Attached Figure Description

[0014] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0015] Figure 1 This is a schematic diagram of the architecture of a network communication scenario provided by an exemplary embodiment of this application;

[0016] Figure 2This is a schematic diagram of a network slicing structure according to an exemplary embodiment of this application;

[0017] Figure 3 This is a flowchart of a network slice management method provided in an exemplary embodiment of this application;

[0018] Figure 4 This is a flowchart of a network slice management method provided in an exemplary embodiment of this application;

[0019] Figure 5 This is a schematic diagram of a conventional Matter network structure under a local area network according to an exemplary embodiment of this application;

[0020] Figure 6 This is a schematic diagram illustrating the working principle of a Matter network according to an exemplary embodiment of this application;

[0021] Figure 7 yes Figure 6 The diagram shows a schematic representation of a Matter network structure at the application layer in an embodiment.

[0022] Figure 8 yes Figure 7 The diagram shows a data interaction structure of one embodiment.

[0023] Figure 9 This is a schematic diagram illustrating the principle of network slicing according to an exemplary embodiment of this application;

[0024] Figure 10 This is a flowchart of a network slice management method provided in an exemplary embodiment of this application;

[0025] Figure 11 This is a structural block diagram of a network slice management device provided in an exemplary embodiment of this application;

[0026] Figure 12 This is a schematic diagram of the structure of a gateway device provided in an exemplary embodiment of this application. Detailed Implementation

[0027] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0028] The solution provided in this application can be used in daily life scenarios where terminal devices connect to the network through a gateway device for network communication. To facilitate understanding, the scenario architecture of the application scenarios involved in the embodiments of this application will be briefly introduced below.

[0029] Please refer to Figure 1 It illustrates an architectural diagram of a network communication scenario provided by an exemplary embodiment of this application, such as... Figure 1 As shown, the network communication scenario may include: several terminal devices 110, gateway devices 120, and base stations 130.

[0030] Terminal device 110 is a wireless communication device capable of transmitting data using wireless access technology. For example, terminal device 110 can support cellular mobile communication technology, such as fourth-generation mobile communication (4G) technology and 5G technology. Alternatively, terminal device 110 can also support the next generation of mobile communication technology after 5G technology.

[0031] For example, terminal device 110 can be an in-vehicle device, such as a vehicle computer with wireless communication capabilities, or a wireless communication device connected to an external vehicle computer. Alternatively, terminal device 110 can also be a roadside device, such as a street light, traffic light, or other roadside device with wireless communication capabilities. Alternatively, terminal device 110 can also be a user terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, such as a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device. Examples include: Station (STA), subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, user device, or user equipment (UE). Specifically, terminal device 110 can be a mobile terminal such as a smartphone, tablet, or e-book reader, or a smart wearable device such as smart glasses, a smartwatch, or a smart bracelet. Optionally, terminal device 110 is a wireless communication device that supports half-duplex technology. Optionally, several terminal devices 110 can communicate wirelessly through direct connection.

[0032] Optionally, the gateway device 120 can be a mobile router (Mobile WIFI, MIFI), a wireless access point (AP), or a 5G communication terminal with routing and forwarding capabilities, such as a customer premises equipment (CPE). The terminal device 110 establishes a network connection with the gateway device 120, and the gateway device 120 establishes a network connection with the base station 130, thereby enabling data transmission and forwarding between them.

[0033] Optionally, base station 130 can be a network-side device in a wireless communication system. This wireless communication system can be a fourth-generation mobile communication technology system, also known as a Long Term Evolution (LTE) system; or it can be a 5G system, also known as a New Radio (NR) system. Alternatively, it can be the next generation of the 5G system. Base station 130 can be an evolved NB (eNB) used in a 4G system. Alternatively, base station 130 can be a gNB (gNB) using a centralized-distributed architecture in a 5G system. When base station 130 adopts a centralized-distributed architecture, it typically includes a central unit (CU) and at least two distributed units (DUs). The central unit is equipped with a protocol stack of the Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer; the distributed units are equipped with a physical (PHY) layer protocol stack. This disclosure does not limit the specific implementation of base station 130.

[0034] Optionally, the aforementioned wireless communication system may further include a network management device. The base station 130 may be connected to the network management device. The network management device may be a core network device in the wireless communication system, such as a Mobility Management Entity (MME) in an Evolved Packet Core (EPC). Alternatively, the network management device may be other core network devices, such as a Serving Gateway (SGW), a Public Data Network Gateway (PGW), a Policy and Charging Rules Function (PCRF), or a Home Subscriber Server (HSS). The implementation of the network management device is not limited in this embodiment.

[0035] In the above Figure 1 In the scenario depicted, 5G network slicing is a core technology for 5G to empower vertical industries. It divides a physical network into multiple virtual end-to-end networks. Each virtual network, including its devices, access, transmission, and core network, is logically independent. Based on the three major application scenarios of 5G, slicing can be further divided into three types: eMBB slices for enhanced mobile broadband communication, uRLLC slices for ultra-reliable low-latency communication, and mMTC slices for massive machine-type communications. In simple terms, 5G network slicing technology can be understood as a highway with different lanes for vehicles traveling at different speeds. However, to implement network slicing in an end-to-end scenario, collaboration between the terminal side and the operator's network side is required, and both need to support network slicing technology. Currently, network slicing technology is supported on the operator's network side, but there is currently no mature technology on the terminal side for selecting network slices for terminal traffic based on the URSP rules issued by the network side.

[0036] Please refer to Figure 2 This illustrates a schematic diagram of a network slice structure according to an exemplary embodiment of this application. Figure 2 As shown, it includes a terminal device 201, an application 202 running on the terminal device 201, and an operator base station 203.

[0037] In the above Figure 2In the structure shown, the URSP rules defined in the 3GPP 5G protocol mainly consist of two sets of rules. One set describes the Traffic Descriptor parameters, which are attributes of the application (APP) 202 running on the terminal device 201. These parameters include APPId, DNN (Data Network Name), IP Descriptor (IP Triplet), Domain Descriptor (Domain Descriptor), Connection Capabilities, and other parameters. The other set describes the Route Selection Descriptor, which is an attribute of the data bearer. This set includes parameters such as S-NSSAI (Network Slice Selection Auxiliary Information), SSC Mode (Session and Service Continuity Mode), and DNN.

[0038] URSP rules are essentially a mapping between multiple sets of Traffic Descriptors and Route Selection Descriptors. Once a terminal device knows the Traffic Descriptor parameters related to the application, it can naturally find the Route Selection Descriptor related to the data bearer according to the URSP rules. This method is suitable for terminal devices such as 5G phones that only conduct data service communication on their own. It allows the Traffic Descriptor parameters to be directly transmitted between the upper-layer application and the lower-layer radio frequency communication module, thereby directing different application data to different data bearers.

[0039] However, for 5G communication terminals with routing and forwarding capabilities, such as CPE and MiFi terminals, their main data service flows originate from their downstream devices rather than being sent by the terminal itself. The methods for associating the forwarded data flows of downstream devices with parameters such as the APP attribute and Traffic Descriptor in URSP rules to achieve traffic slicing are currently mainly as follows: a) By dividing VLANs, the URSP rules issued by the network side are mapped one-to-one with the VLANs. Devices that need to be forwarded through the same network slice are added to this VLAN, and the relevant traffic is introduced into the network slice by specifying the VLAN's outgoing interface route; b) By using flow identification, information such as the IP 5-tuple, TOS, and DSCP in the terminal's forwarded data is extracted, and the corresponding flows are mapped to URSP rules according to flow matching rules.

[0040] In the first partitioning scheme, VLANs need to be manually partitioned according to URSP rules, and downstream devices need to be added to designated VLANs. This requires a certain level of network expertise. Changing URSP rules and adding / removing devices also require user intervention, making the process cumbersome and inefficient. In the second partitioning scheme, flow identification requires pre-defined flow identification rules based on the characteristics of different forwarding data flows. The accuracy of its traffic redirection depends on the accuracy of the flow matching rules. Since different types of terminal devices and different types of service data flows vary greatly, algorithms for accurately classifying flows based on their characteristics are difficult to implement, making it impossible to accurately classify all flows. Furthermore, the same device and the same service can generate multiple data flows. If each data flow enters different network slices, not only is the amount of data to be processed large, but the accuracy is also low. This can lead to the same terminal device being assigned to different network slices, causing service anomalies.

[0041] To address the problems existing in the aforementioned related technologies, reduce the amount of data that needs to be processed during network slicing, and improve the accuracy and efficiency of network slicing on the terminal side, this application provides a network slicing management method. This method uses the feature information created by the gateway device accessed by the downstream device based on the networking protocol to perform network slicing management on the downstream device, thereby reducing the amount of data that needs to be processed.

[0042] Please refer to Figure 3 It illustrates a flowchart of a network slice management method provided in an exemplary embodiment of this application, which can be applied to the above-mentioned... Figure 1 In the scenario architecture, the gateway device connects to downstream devices based on networking protocols. For example... Figure 3 As shown, the network slice management method may include the following steps:

[0043] Step 301: Obtain the characteristic information of the downstream device. The characteristic information is created by the gateway device that the downstream device accesses based on the networking protocol.

[0044] Among them, the downstream device is any terminal device in the access gateway device, and the terminal device can be one of the above. Figure 1 In this scenario, terminal devices, downstream devices, and gateway devices establish network connections based on supported networking protocols.

[0045] Optionally, the networking protocol can be a protocol that has the function of creating attribute data for downstream devices. For example, when a downstream device connects to the gateway device, the gateway device can create characteristic information belonging to the downstream device based on the requirements of the networking protocol and the attribute data of the downstream device. Optionally, the characteristic information can be one or more of the attribute data of the downstream device.

[0046] Step 302: Based on the feature information, map the service data stream of the downstream device to the corresponding network slice, and communicate through the corresponding network slice.

[0047] Optionally, the gateway device obtains the characteristic information of the downstream devices, performs network slicing on the downstream devices based on the characteristic information, and maps the service data streams of the downstream devices to the corresponding network slices, thereby realizing network slice management of the downstream devices.

[0048] In summary, in this application, the gateway device and its downstream devices, based on the networking protocol, will create characteristic information belonging to the downstream devices. By obtaining the characteristic information of the downstream devices through the gateway device, the service data streams of the downstream devices are mapped to the corresponding network slices, and communication is carried out through the corresponding network slices. Therefore, it is not necessary to obtain the service data streams of the downstream devices. Network slicing is performed directly through the characteristic information created based on the networking protocol, thereby reducing the amount of data that needs to be processed during network slicing and improving the accuracy and efficiency of the gateway device in performing network slicing.

[0049] In one possible implementation, the gateway device can pre-configure a first correspondence between different device clusters and different URSP rules. When performing network slicing based on feature information, the gateway device can assign downstream devices to the corresponding device clusters based on the feature information and obtain the URSP rules corresponding to the device clusters to complete the network slicing.

[0050] Please refer to Figure 4 It illustrates a flowchart of a network slice management method provided in an exemplary embodiment of this application, which can be applied to the above-mentioned... Figure 1 In the scenario architecture, the gateway device connects to downstream devices based on networking protocols. For example... Figure 4 As shown, the network slice management method may include the following steps:

[0051] Step 401: Obtain the characteristic information of the downstream device. The characteristic information is created by the gateway device that the downstream device accesses based on the networking protocol.

[0052] Optionally, when performing network slicing on its various downstream devices, the gateway device can obtain characteristic information of one or more downstream devices. Specifically, for any downstream device connected to the gateway device, the gateway device creates characteristic information for the downstream device based on supported networking protocols. For example, when a downstream device connects to the gateway device, the gateway device can automatically create characteristic information belonging to that downstream device based on the requirements of the networking protocol and the attribute data of the downstream device. Optionally, the attribute data can be network establishment data sent to the gateway device when the downstream device connects, and the characteristic information can be one or more of the attribute data of the downstream device.

[0053] In one possible implementation, before step 401, when the downstream device and the gateway device establish a network connection based on the networking protocol, the gateway device can obtain the network establishment data sent by the downstream device to the gateway device; based on the network establishment data, a standard data model is established for the downstream device; when the gateway device needs to obtain the feature information of the downstream device, the gateway device obtains the feature information of the downstream device from the standard data model.

[0054] Optionally, after each terminal device becomes a downstream device after accessing the gateway device, the gateway device can create a standard data model for each downstream device based on the networking protocol. The structure of this standard data model can be predefined by the developers of the networking protocol.

[0055] Taking Matter, a local area network (LAN) protocol, as an example, please refer to... Figure 5 This illustrates a schematic diagram of a conventional Matter network structure under a local area network according to an exemplary embodiment of this application. Figure 5 As shown, this includes a peripheral network 501 and a hub network 502. Each node in the peripheral network 501 and hub network 502 can include AP, BR, ED, R, SED, STA, etc. Here, AP represents a wireless access point; BR represents a border router between IP subnets; ED represents a thread end node; R represents a thread internal router; SED represents a thread sleepy end node; and STA represents a WiFi station. In a Matter network topology, each terminal device and each gateway device in the network can act as a node in the aforementioned star network topology.

[0056] Please refer to Figure 6 This illustrates a schematic diagram of the working principle of a Matter network according to an exemplary embodiment of this application. Figure 6 As shown, it includes an application layer 601, a transport layer 602, a network layer 603, and a bottom layer 604. (As...) Figure 6 As shown: The Matter protocol primarily operates at the application layer, with TCP / UDP at the transport layer, IPv6 at the network layer, and IPv6-compatible protocols at the lower layers (Ethernet, Wi-Fi, Thread). Therefore, terminal devices supporting the Matter protocol can access the network via Ethernet, Wi-Fi, Thread, etc., forming the above-mentioned... Figure 5 The star network topology shown is shown.

[0057] In the above Figure 6 In the context of the Matter protocol, the application layer can be further divided into 7 layers. Please refer to [link / reference needed]. Figure 7 , it is Figure 6 The illustrated embodiment presents a schematic diagram of a Matter network structure at the application layer. Figure 7 As shown, it includes an application layer 701, a data model layer 702, an interaction model layer 703, an action framework layer 704, a security layer 705, a message framework and routing layer 706, and an IP framework and transmission management layer 707.

[0058] The application layer 701 corresponds to the specific business interaction logic of the underlying devices. For example, a light application includes specific features such as switching and color adjustment. The data model layer 702 corresponds to some basic data and element models that support application functions. When device interaction is required, the application operates on these data models. The interaction model layer 703 defines a set of interactions performed between the client and server devices. For example, reading or writing attributes on the server device corresponds to application behavior on the device. These interactions act on the elements defined in the data model layer. The action framework layer 704 serializes an action constructed using the interaction model layer into a binary data packet for encoded transmission over the network. This process is handled in the action framework layer. The security layer 705 encodes action frames where data encoded in the previous layers needs to be processed and encoded: messages are encrypted and appended with a message verification code. These operations ensure secure data transmission between the sender and receiver, guaranteeing that the data will not be tampered with. The Message Framework and Routing Layer 706, following the interactions described above, ensures that the data is now serialized, encrypted, and signed. The Message Layer constructs the payload format using required and optional header fields that specify message attributes and logical routing information. The IP Framework and Transport Management 707, after the Message Layer has built the final payload, sends it to the underlying transport protocol (TCP or Matter's message reliability protocol) for IP management of the data.

[0059] As can be seen from the above, since the Matter protocol has defined a standard data model (data model layer 702 in the diagram above), the gateway device can obtain the standard data model of the downstream devices in the entire Matter network. Typically, each downstream device can be abstracted as a Matter Node (standard data model).

[0060] Please refer to Figure 8 , it is Figure 7 The illustrated embodiment is a schematic diagram of a data interaction structure. Figure 8As shown, it includes a data model layer 800, a meta-model framework unit 801, an instance behavior unit 802, an interaction model unit 803, a transmission encoding unit 804, and a subsequent model layer 805.

[0061] The meta-model framework unit 801 may include fields such as node, device, cluster, attribute, command, data type, and report; the instance behavior unit 802 may include fields such as thermostat, light, switch, user, and room; the interaction model unit 803 may include fields such as read, write, and report; and the sending and encoding unit 804 may forward and encode application messages sent by the subsequent model layer 805.

[0062] Optionally, when the downstream device and the gateway device establish a network connection based on the networking protocol, the network establishment data sent by the downstream device to the gateway device is obtained. This network establishment data may include the above-mentioned... Figure 8 The subsequent model layer 805 interacts with the downstream device in the application layer using application data. Based on this application data, the gateway device can process the downstream device according to the above... Figure 8 The structure shown establishes a standardized data model with a unified structure. When it is necessary to obtain the characteristic information of the downstream device, the characteristic information of the downstream device is obtained from the standardized data model. Optionally, the gateway device can obtain fields such as cluster and attribute from the above-mentioned standardized data model.

[0063] Step 402: Based on the feature information and preset division rules, the downstream devices are divided into corresponding device clusters. Each downstream device in a device cluster has the same feature information.

[0064] Optionally, the gateway device can divide the downstream devices according to the acquired feature information and a preset division rule. Typically, the gateway device can acquire the feature information of all downstream devices at once. The gateway device can then divide the downstream devices based on their individual feature information, grouping those devices with the same feature information into a single device cluster. This can result in multiple device clusters; therefore, the downstream devices within the same device cluster will have identical feature information.

[0065] When the gateway device executes the process of this solution for a single downstream device that is connected later, if the gateway device has previously divided other connected downstream devices, the gateway device can compare the feature information of the downstream device with the feature information of the downstream devices in each of the divided device clusters, and divide the downstream device into a device cluster with the same feature information, thus completing the division of the device cluster.

[0066] In one possible implementation, the preset partitioning rules are determined based on the device types of the downstream devices connected to the gateway device. Based on the feature information and the preset partitioning rules, the downstream devices are assigned to corresponding device clusters, including: determining the device type of the downstream device based on the feature information; and grouping downstream devices of the same device type into the same device cluster based on the device type and the preset partitioning rules. That is, the gateway device can also determine the device type of the downstream device based on the aforementioned feature information; and group the downstream device into a device cluster with the same device type as the downstream device based on the device type and the preset partitioning rules. For example, the Matter protocol specification defines some common device types, such as electrical / lighting, HVAC control, television, door locks, and security sensors. The gateway device determines the device type of the downstream device through feature information and groups the downstream device into a device cluster with the same device type as the downstream device.

[0067] Step 403: Determine the first network slice based on the first correspondence between the device cluster and the user routing policy URSP rules.

[0068] Optionally, the first correspondence can be predefined and stored in the gateway device by the gateway device developers. After the gateway device determines the device cluster of the downstream devices, it determines the corresponding URSP rules through the one-to-one correspondence between the device cluster and the URSP rules, thereby determining the first network slice.

[0069] For example, determining the first network slice based on the first correspondence between device clusters and user routing policy URSP rules includes: determining the first target URSP rule corresponding to the device cluster based on the first correspondence between device clusters and user routing policy URSP rules; and determining the first network slice based on the first target URSP rule.

[0070] Please refer to Table 1, which shows a schematic table illustrating the first correspondence between a device cluster and user routing policy URSP rules according to an exemplary embodiment of this application.

[0071] Table 1: First Correspondence Between Device Clusters and User Routing Policy URSP Rules

[0072] Device Cluster URSP rules Device Cluster 1 URSP Rule 1 Equipment Cluster 2 URSP Rule 2 Equipment Cluster Three URSP Rule 3 …… ……

[0073] As shown in Table 1, different device clusters correspond to different URSP rules. When the gateway device assigns the above-mentioned downstream devices to device cluster two, the corresponding URSP rule can be obtained by querying Table 1. Then, URSP rule two is the first target URSP rule. The gateway device determines the first network slice based on URSP rule two.

[0074] Optionally, the first correspondence described above is exemplified by being pre-defined in the gateway device. In another possible implementation, the first correspondence can also be established by the gateway device itself. For example, before determining the first network slice based on the first correspondence between device clusters and user routing policy URSP rules, the gateway device receives various URSP rules issued by the network device; determines the number of URSP rules; and establishes the correspondence between device clusters with different service quality requirements and each URSP rule. Here, the network device is a device used to provide network communication to the gateway device, such as the one described above. Figure 1 Base stations, etc.

[0075] For example, gateway device developers or operations personnel can pre-configure the required Quality of Service (QoS) requirements for different device clusters in the gateway device. After receiving various URSP rules from network devices, the gateway device, based on the number of received URSP rules, determines the same number of device clusters with different QoS requirements and establishes a mapping between each device cluster with different QoS requirements and each URSP rule. For instance, similar device types often have the same Quality of Service (QoS) requirements. Developers, based on some standard device types defined by the Matter specification, determine the QoS for each device type and configure it in the gateway device. After receiving various URSP rules, the gateway device then establishes corresponding URSP rules for each device cluster.

[0076] In one possible implementation, when the number of QoS rules set by the developer exceeds the number of received URSP rules, the gateway device can appropriately merge the QoS rules. For example, if the developer sets four QoS rules, corresponding to four device clusters, and three URSP rules are received, the gateway device can merge the two closest QoS rules into one. That is, instead of two QoS rules corresponding to two device clusters, it can adjust the configuration to one QoS rule corresponding to two device clusters, thus satisfying the requirement of three QoS rules corresponding to three device clusters and three URSP rules. Alternatively, the extra QoS rule can be assigned to one of the three default URSP rules, which can be preset by the developer.

[0077] Optionally, if the first correspondence mentioned above has been preset in the gateway device, and the number of received URSP rules is greater than the number of URSP rules included in Table 1, the gateway device can divide the device cluster according to the URSP rules corresponding to each device cluster. If the number of received URSP rules is less than the number of URSP rules included in Table 1, the extra device cluster can be divided according to the default URSP rule. The default URSP rule is one of the URSP rules sent by the network device. This default selection method can be set by the developers.

[0078] In one possible implementation, the correspondence between the aforementioned device clusters and service quality requirements can be pre-stored. Each different service quality requirement corresponds to a different URSP rule. The gateway device determines the service quality requirement corresponding to the device cluster through the device cluster of the downstream devices, and determines the corresponding URSP rule through the service quality requirement.

[0079] Step 404: Map the service data of the downstream device to the first network slice.

[0080] Optional, please refer to Figure 9 The diagram illustrates a schematic representation of a network slicing principle according to an exemplary embodiment of this application. Figure 9 Taking the Matter protocol in a local area network as an example, in... Figure 9 The network slicing consists of different device clusters 901, gateway device 902, and network side 903. Network side 903 is equivalent to the aforementioned network devices. Gateway device 902 can partition each downstream device according to Matter Nodes created based on the Matter protocol. Within the same device cluster, the characteristic information of each Matter Node is identical. Following a one-to-one correspondence between the device cluster and each URSP rule, data service communication with network side 903 is ultimately achieved using PDU sessions corresponding to the URSP rules. This allows data services from different device clusters to run on different bearers, thus realizing end-to-end network slicing.

[0081] Step 405: Communicate via the first network slice.

[0082] Optionally, after determining the required URSP rules for the downstream devices as described above, the gateway device maps the service data streams of the downstream devices to the corresponding network slices and communicates through the corresponding network slices. For example, as described in the above embodiments, the gateway device can classify the downstream devices into device clusters of the same cluster based on the characteristic information of the downstream devices. After mapping the device clusters to the same URSP rule, data service communication is achieved using Protocol Data Unit (PDU) sessions corresponding to the determined URSP rule. This allows data services from different clusters to run on different bearers, thereby achieving end-to-end network slicing.

[0083] Optionally, the gateway device can also map the service data streams of downstream devices to corresponding network slices based on feature information, and after communication through the corresponding network slices, obtain the communication quality of the downstream devices. When the communication quality is lower than the communication quality threshold of the network slice to which the downstream device belongs, a new network connection is established with the downstream device, and the step of obtaining the feature information of the downstream device is repeated. In this application, after completing network slicing, the gateway device can obtain and detect the communication quality of the downstream devices. When it is detected that the communication quality of the downstream device is lower than the communication quality threshold of the network slice to which the downstream device belongs, it indicates that the communication quality of the downstream device in the PDU session process corresponding to the previously determined URSP rule cannot meet the communication requirements, and network slicing needs to be re-performed for the downstream device. Therefore, the gateway device can obtain the feature information of the downstream device again and perform network slicing again. The communication quality threshold can be preset in the gateway device by the developers.

[0084] In summary, in this application, the gateway device and its downstream devices, based on the networking protocol, will create characteristic information belonging to the downstream devices. By obtaining the characteristic information of the downstream devices through the gateway device, the service data streams of the downstream devices are mapped to the corresponding network slices, and communication is carried out through the corresponding network slices. Therefore, it is not necessary to obtain the service data streams of the downstream devices. Network slicing is performed directly through the characteristic information created based on the networking protocol, thereby reducing the amount of data that needs to be processed during network slicing and improving the accuracy and efficiency of the gateway device in performing network slicing.

[0085] Furthermore, this application flexibly adjusts the number of USRP rules issued by the network side to adjust the stored first correspondence, which can flexibly meet the requirements of different network sides and improve the accuracy of network slicing. By subsequently obtaining the communication quality of the downstream devices and detecting the relationship with the preset quality threshold, network slicing errors can be corrected in a timely manner, and network slicing can be re-performed, which can also improve the accuracy of network slicing.

[0086] In addition, this solution combines the Matter protocol in the local area network with the terminal network slicing scheme. Devices that access 5G routing terminals in the local area network via the Matter protocol have a unified standard data model. Devices with the same characteristic information in the standard data model can be grouped into a device cluster. By mapping the device clusters with URSP rules, network slicing is achieved.

[0087] In one possible implementation, the gateway device can be pre-configured with a second correspondence between different feature information and different URSP rules. The gateway device can query the corresponding second correspondence based on the feature information to obtain the corresponding URSP rules, thereby performing network slicing.

[0088] Please refer to Figure 10 It illustrates a flowchart of a network slice management method provided in an exemplary embodiment of this application, which can be applied to the above-mentioned... Figure 1 In the scenario architecture, the gateway device connects to downstream devices based on networking protocols. For example... Figure 10 As shown, the network slice management method may include the following steps:

[0089] Step 1001: Obtain the feature information of the downstream device. The feature information is created by the gateway device that the downstream device accesses based on the networking protocol.

[0090] The method for obtaining feature information in step 1001 can be referred to the description in step 401 above, and will not be repeated here.

[0091] Step 1002: Determine the second network slice based on the second correspondence between the feature information and the user routing policy URSP rules.

[0092] Optionally, in this embodiment, the gateway device pre-stores a second correspondence between feature information and user routing policy URSP rules. The gateway device queries the second correspondence by obtaining the feature information of the downstream devices, obtains the corresponding URSP rules, and thus determines the network slice.

[0093] For example, a second network slice is determined based on the second correspondence between feature information and user routing policy (URSP) rules. This includes: determining the second target URSP rule corresponding to the feature information based on the second correspondence between feature information and user routing policy (URSP) rules; and determining the second network slice based on the second target URSP rule.

[0094] Please refer to Table 2, which shows a schematic table illustrating a second correspondence between feature information and user routing policy URSP rules according to an exemplary embodiment of this application.

[0095] Table 2: Second Correspondence Between Feature Information and User Routing Policy URSP Rules

[0096] Feature information URSP rules Feature Information 1 URSP Rule 1 Feature Information 2 URSP Rule 2 Feature Information 3 URSP Rule 3 …… ……

[0097] As shown in Table 2, different feature information corresponds to different URSP rules. When the gateway device assigns the above-mentioned downstream device to feature information two, the corresponding URSP rule can be obtained by querying Table 2. Then, URSP rule two is the second target URSP rule. The gateway device determines the second network slice according to URSP rule two.

[0098] Optionally, the second correspondence mentioned above is an example of one that is preset in the gateway device. In another possible implementation, the second correspondence can also be established by the gateway device itself. The establishment method can refer to the method of establishing the first correspondence independently in step 403 above, which will not be repeated here.

[0099] Step 1003: Map the service data of the downstream device to the second network slice.

[0100] Step 1004: Communicate via the second network slice.

[0101] Optionally, the implementation of steps 1003 to 1004 can refer to the description in steps 404 to 405 above, and will not be repeated here.

[0102] It should be noted that, Figure 4 or Figure 10 In addition to the Matter protocol shown as an example, the network protocols supported in the scheme can also be other network protocols that can establish data models for downstream devices to classify them, such as the SSDP protocol. The data models established by different network protocols may be different, but the process of network slicing by directly using the feature information in the data model created by the network protocol is similar, and will not be elaborated here.

[0103] In summary, the network slicing management method in this application, based on the networking protocol, involves the gateway device creating characteristic information belonging to its downstream devices. By obtaining the characteristic information of its downstream devices through the gateway device, the service data streams of the downstream devices are mapped to the corresponding network slices, and communication is conducted through the corresponding network slices. Therefore, it is not necessary to obtain the service data streams of the downstream devices. Network slicing is performed directly based on the characteristic information created according to the networking protocol, thereby reducing the amount of data that needs to be processed during network slicing and improving the accuracy and efficiency of the gateway device in performing network slicing.

[0104] In addition, most of the application scenarios of 5G gateway devices such as CPE serve smart home scenarios, and almost all smart homes have begun to support the Matter protocol. Combining network slicing with the Matter protocol is also highly adaptable and feasible. This solution is simpler and more reliable than the flow classification method and does not require manual intervention. When the downstream device accesses through the Matter protocol, it can be automatically mapped to the corresponding URSP rule based on the feature information at the gateway node.

[0105] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0106] Please refer to Figure 11 This diagram illustrates a structural block diagram of a network slice management apparatus provided in an exemplary embodiment of this application. The network slice management apparatus 1100 can be used in the above-described... Figure 1 In the scenario architecture, the gateway device connects to downstream devices based on networking protocols. This is to execute... Figure 3 , Figure 4 ,or Figure 10 The method provided in the illustrated embodiment includes all or part of the steps performed by the gateway device. The network slice management device 1100 includes:

[0107] The information acquisition module 1101 is used to acquire the feature information of the downstream device, wherein the feature information is created by the gateway device that the downstream device accesses based on the networking protocol;

[0108] The network slicing module 1102 is used to map the service data stream of the downstream device to the corresponding network slice according to the feature information, and to communicate through the corresponding network slice.

[0109] In summary, the network slicing management device in this application, based on the networking protocol, creates characteristic information belonging to the downstream devices through the gateway device. By obtaining the characteristic information of its downstream devices through the gateway device, the service data streams of the downstream devices are mapped to the corresponding network slices, and communication is carried out through the corresponding network slices. Therefore, it is not necessary to obtain the data streams of the service data of the downstream devices. Network slicing is performed directly through the characteristic information created based on the networking protocol, thereby reducing the amount of data that needs to be processed during network slicing and improving the accuracy and efficiency of the gateway device in performing network slicing.

[0110] Optionally, the network slicing module includes: a first partitioning unit, a first determining unit, and a first slicing unit;

[0111] The first division unit is used to divide the downstream devices into corresponding device clusters according to the feature information and the preset division rules. Each downstream device in a device cluster has the same feature information.

[0112] The first determining unit is used to determine the first network slice based on the first correspondence between the device cluster and the user routing policy URSP rules;

[0113] The first slicing unit is used to map the service data of the downstream device to the first network slice.

[0114] Optionally, the preset partitioning rule is determined based on the device type of the downstream device connected to the gateway device. The first partitioning unit includes: a first determining subunit and a first partitioning subunit.

[0115] The first determining subunit is used to determine the equipment type of the attached device based on the feature information;

[0116] The first partitioning subunit is used to partition the downstream devices into a device cluster of the same type according to the device type and preset partitioning rules.

[0117] Optionally, the network slice management device also includes:

[0118] The first receiving module is used to receive various URSP rules issued by the network device before determining the first network slice based on the first correspondence between the device cluster and the user routing policy URSP rules. The network device is a device used to provide network communication to the gateway device.

[0119] The first determining module is used to determine the number of URSP rules;

[0120] The first module is used to establish the correspondence between device clusters with different service quality requirements and various URSP rules.

[0121] Optionally, the network slicing module includes: a second determining unit and a second slicing unit;

[0122] The second determining unit is used to determine the second network slice based on the second correspondence between the feature information and the user routing selection policy URSP rules;

[0123] The second slicing unit is used to map the service data of the downstream device to the second network slice.

[0124] Optionally, the network slice management device also includes:

[0125] The data acquisition module is used to acquire network establishment data sent by the downstream device to the gateway device when the downstream device and the gateway device establish a network connection based on the networking protocol before acquiring the characteristic information of the downstream device;

[0126] The second module is used to establish a standard data model for the downstream devices based on the network data.

[0127] The information acquisition module is also used to obtain the feature information of the downstream devices from the standard data model.

[0128] Optionally, the network slice management device also includes:

[0129] The quality acquisition module is used to map the service data stream of the downstream device to the corresponding network slice based on the feature information, and obtain the communication quality of the downstream device after communication through the corresponding network slice.

[0130] The re-execution module is used to re-establish a network connection with the downstream device and re-execute the steps of obtaining the downstream device's feature information when the communication quality is lower than the communication quality threshold of the network slice to which the downstream device belongs.

[0131] Please refer to Figure 12 This illustration shows a schematic diagram of the structure of a gateway device provided in an exemplary embodiment of this application. Figure 12 As shown, the gateway device includes a processor 1210, a transceiver 1220, and a display unit 1270. The display unit 1270 may include a display screen.

[0132] Optionally, the gateway device may also include a memory 1230. The processor 1210, transceiver 1220, and memory 1230 can communicate with each other via internal connections to transmit ranging data. The memory 1230 stores computer programs, and the processor 1210 retrieves and runs the computer programs from the memory 1230. The gateway device may be a 5G communication terminal with routing and forwarding capabilities.

[0133] The processor 1210 and memory 1230 can be combined into a single processing device, but more commonly they are independent components. The processor 1210 executes the program code stored in memory 1230 to achieve the above functions. In specific implementations, the memory 1230 can be integrated into the processor 1210, or it can be independent of the processor 1210.

[0134] Understandable Figure 12The gateway device shown may include one or more processing units. For example, processor 1210 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors.

[0135] The processor 1210 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 1210 is a cache memory. This memory can store instructions or data that the processor 1210 has just used or that are used repeatedly. If the processor 1210 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 1210, and thus improves the efficiency of the system.

[0136] In some embodiments, the processor 1210 may include one or more interfaces. Interfaces may include inter-integrated circuit (IC) interfaces, inter-integrated circuit sound (IS) interfaces, pulse code modulation (PCM) interfaces, universal asynchronous receiver / transmitter (UART) interfaces, mobile industry processor interfaces (MIPI), general-purpose input / output (GPIO) interfaces, subscriber identity module (SIM) interfaces, and / or universal serial bus (USB) interfaces, etc.

[0137] The UART interface is a universal serial data bus used for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 1210 and the transceiver 1220. For example, the processor 1210 communicates with the Bluetooth module in the transceiver 1220 via the UART interface to implement Bluetooth functionality.

[0138] The MIPI interface can be used to connect the processor 1210 to peripheral devices such as the display unit 1270. The MIPI interface includes a camera serial interface (CSI) and a display serial interface (DSI). In some embodiments, the processor 1210 and the display unit 1270 communicate via the DSI interface to realize the display function of the gateway device.

[0139] The GPIO interface can be configured via software. It can be configured as a control signal or a data signal. In some embodiments, the GPIO interface can be used to connect the processor 1210 to the display unit 1270, transceiver 1220, etc. The GPIO interface can also be configured as an IC interface, IS interface, UART interface, MIPI interface, etc.

[0140] Transceiver 1220 can provide solutions for wireless communication applications on gateway devices, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. Transceiver 1220 can be one or more devices integrating at least one communication processing module; for example, it may include a Bluetooth module.

[0141] The memory 1230 can be used to store computer executable program code, which includes instructions. The memory 1230 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of the gateway device (such as location data), etc. Furthermore, the memory 1230 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. The processor 1210 executes various functional applications and data processing of the gateway device by running instructions stored in the memory 1230 and / or instructions stored in memory disposed in the processor.

[0142] In addition, to further enhance the functionality of the gateway device, it may also include one or more of the following: power supply 1250, input unit 1260, audio circuit 1280, and sensor 1202.

[0143] Power supply 1250 is used to provide power to various devices or circuits in the gateway device. Preferably, power supply 1250 can be logically connected to processor 1210 through a power management device, thereby enabling functions such as charging, discharging, and power consumption management through the power management device.

[0144] The input unit 1260 can be used to receive input numerical or character information, and to generate key signal inputs related to user settings and function control of the gateway device. Specifically, the input unit 1260 may include a touch panel and other input devices. The touch panel, also known as a touchscreen, can collect touch operations performed by the user on or near it, such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel, and drive the corresponding connected devices according to a pre-set program. Optionally, the touch panel may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, sends it to the processor 1210, and can receive and execute commands from the processor 1210. Furthermore, the touch panel can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel, the input unit 1260 may also include other input devices. Specifically, other input devices may include, but are not limited to, one or more of function keys, trackballs, joysticks, etc.

[0145] Display unit 1270 can be used to display information input by the user or information provided to the user, as well as various menus of the gateway device. Display unit 1270 may include a display panel, optionally configured as a Liquid Crystal Display (LCD), Organic Light-Emitting Diode (OLED), or similar display panel. Furthermore, a touch panel may cover the display panel. When the touch panel detects a touch operation on or near it, it transmits the information to processor 1210 to determine the type of touch event. Subsequently, processor 1210 provides corresponding visual output on the display panel based on the type of touch event.

[0146] The gateway device may also include at least one sensor 1202, such as a gyroscope sensor, a motion sensor, and other sensors. Specifically, the gyroscope sensor can be used to determine the motion attitude of the gateway device. In some embodiments, the angular velocity of the gateway device about three axes (i.e., the x, y, and z axes) can be determined by the gyroscope sensor. The gyroscope sensor can also be used for navigation and motion-sensing game scenarios. As a type of motion sensor, an accelerometer can detect the magnitude of acceleration in various directions (i.e., the x, y, and z axes), and when stationary, it can detect the magnitude and direction of gravity. It can be used for applications that identify the attitude of the gateway device (such as landscape / portrait switching, related games, magnetometer attitude calibration), vibration recognition-related functions (such as pedometers, tapping), etc. Other sensors that may be configured on the gateway device, such as pressure gauges, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0147] The audio circuit 1280 may include a speaker and a microphone, providing an audio interface between the user and the gateway device. The audio circuit 1280 can convert received audio data into electrical signals and transmit them to the speaker, where the speaker converts them into sound signals for output. Conversely, the microphone converts collected sound signals into electrical signals, which are then received by the audio circuit 1280, converted back into audio data, and processed by the processor 1210 before being transmitted via RF circuitry to, for example, another gateway device, or output to the memory 1230 for further processing.

[0148] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the gateway device. In other embodiments of this application, the gateway device may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0149] This application also provides a computer-readable medium storing a computer program that is executed by a processor to implement all or part of the steps performed by a gateway device in the network slicing management methods of the above embodiments.

[0150] This application also provides a computer program product that stores a computer program that is executed by a processor to implement the network slicing management method of the above embodiments, including all or part of the steps performed by a gateway device.

[0151] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules when controlling computer equipment. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0152] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments. Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware, or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0153] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A network slice management method, characterized in that, Applied to a gateway device, wherein the gateway device connects to downstream devices based on a networking protocol, the method includes: Obtain the characteristic information of the downstream device, wherein the characteristic information is created by the gateway device accessed by the downstream device based on the networking protocol; Based on the aforementioned feature information, the service data stream of the downstream device is mapped to the corresponding network slice, and communication is performed through the corresponding network slice. Before obtaining the feature information of the attached device, the method further includes: When the downstream device and the gateway device establish a network connection based on the networking protocol, the network establishment data sent by the downstream device to the gateway device is obtained. The networking protocol is a protocol with the function of creating attribute data of the downstream device. The gateway device is used to create feature information belonging to the downstream device based on the requirements in the networking protocol and the attribute data of the downstream device. The feature information is one or more of the attribute data of the downstream device. Based on the network data, a standard data model is established for the downstream device; Obtain the characteristic information of the downstream device, including: The feature information of the attached device is obtained from the standard data model.

2. The method according to claim 1, characterized in that, The step of mapping the service data stream of the downstream device to the corresponding network slice based on the feature information includes: Based on the feature information and the preset division rules, the downstream devices are divided into corresponding device clusters, and the feature information of each downstream device in a device cluster is the same. The first network slice is determined based on the first correspondence between the device cluster and the user routing policy URSP rules; The service data of the downstream device is mapped to the first network slice.

3. The method according to claim 2, characterized in that, The preset partitioning rule is determined based on the device type of the downstream devices connected to the gateway device; the step of partitioning the downstream devices into corresponding device clusters based on the feature information and the preset partitioning rule includes: Based on the aforementioned feature information, the device type of the downstream device is determined; Based on the device type and the preset partitioning rules, the downstream devices with the same device type are grouped into the same device cluster.

4. The method according to claim 2, characterized in that, Before determining the first network slice based on the first correspondence between the device cluster and the user routing policy URSP rules, the method further includes: Receive each of the URSP rules issued by the network device, which is a device used to provide network communication to the gateway device; Determine the number of URSP rules; Establish the correspondence between device clusters with different service quality requirements and each of the URSP rules.

5. The method according to claim 1, characterized in that, The step of mapping the service data stream of the downstream device to the corresponding network slice based on the feature information includes: The second network slice is determined based on the second correspondence between the feature information and the user routing policy URSP rules; The service data of the connected device is mapped to the second network slice.

6. The method according to any one of claims 1 to 5, characterized in that, After mapping the service data stream of the downstream device to the corresponding network slice based on the feature information, and communicating through the corresponding network slice, the method further includes: Obtain the communication quality of the connected device; When the communication quality is lower than the communication quality threshold of the network slice to which the downstream device belongs, a new network connection is established with the downstream device, and the step of obtaining the characteristic information of the downstream device is executed again.

7. A network slicing management device, characterized in that, Applied to a gateway device, the gateway device is connected to downstream devices based on a networking protocol, the device includes: The information acquisition module is used to acquire the feature information of the downstream device, wherein the feature information is created by the gateway device that the downstream device accesses based on the networking protocol; The network slicing module is used to map the service data stream of the downstream device to the corresponding network slice according to the feature information, and to communicate through the corresponding network slice; The network slice management device also includes: The data acquisition module is used to acquire network establishment data sent by the downstream device to the gateway device when the downstream device and the gateway device establish a network connection based on a networking protocol before acquiring the feature information of the downstream device. The networking protocol is a protocol with the function of creating attribute data of the downstream device. The gateway device is used to create feature information belonging to the downstream device based on the requirements in the networking protocol and the attribute data of the downstream device. The feature information is one or more of the attribute data of the downstream device. The second module is used to establish a standard data model for the downstream devices based on the network data. The information acquisition module is also used to obtain the feature information of the downstream devices from the standard data model.

8. A gateway device, characterized in that, The gateway device includes a processor and a memory, the memory storing a computer program that is executed by the processor to implement the network slice management method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, which is executed by a processor to implement the network slice management method as described in any one of claims 1 to 6.

Images