CN114978911B

CN114978911B - Correlation method of network slices, equipment main body, communication module and terminal equipment

Info

Publication number: CN114978911B
Application number: CN202210549530.6A
Authority: CN
Inventors: 魏进武; 周晶; 姜琳
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2022-05-20
Filing date: 2022-05-20
Publication date: 2024-03-08
Anticipated expiration: 2042-05-20
Also published as: CN114978911A; WO2023221451A1

Abstract

The invention provides a method for associating network slices, a device main body, a communication module and terminal equipment, wherein the method comprises the following steps: acquiring a first IP data packet corresponding to a target flow descriptor TD; acquiring a target TAG corresponding to the target TD according to a prestored mapping relation table of the TD and the TAG TAG; marking the first IP data packet according to the target TAG to obtain a second IP data packet; and sending the second IP data packet to a communication module. The method, the equipment main body, the communication module and the terminal equipment can realize the association of the established plurality of network slices with network transmission data of different services or applications on a host (the equipment main body).

Description

Correlation method of network slices, equipment main body, communication module and terminal equipment

Technical Field

The present invention relates to the field of network technologies, and in particular, to a method for associating network slices, an apparatus main body, a communication module, and a terminal device.

Background

Because the 5G network supports mutually independent multi-slice network access and transmission capability, other terminals except the mobile phone terminal, such as the Internet of things terminal, have the communication function realized mostly through the plug-in communication module, so that the requirement that one terminal device is inserted into one 5G communication module in the application scene of other terminals except the mobile phone terminal and a plurality of different 5G slice networks are used at the same time exists. Under normal conditions, the 5G communication module establishes a network slice, and the host (device body) directly performs network transmission based on the network slice, but if a plurality of 5G network slices are established, how to associate the established plurality of network slices with network transmission data of different services or applications on the host (device body) is a problem to be solved in the present day.

Disclosure of Invention

The invention aims to solve the technical problems of the prior art, and provides a network slice association method, an equipment main body, a communication module and terminal equipment, which can be used for associating a plurality of established network slices with network transmission data of different services or applications on a host (equipment main body).

In a first aspect, the present invention provides a method for associating network slices, applied to an apparatus main body, the method comprising:

acquiring a first IP data packet corresponding to a target flow descriptor TD;

acquiring a target TAG corresponding to the target TD according to a prestored mapping relation table of the TD and the TAG TAG;

marking the first IP data packet according to the target TAG to obtain a second IP data packet;

and sending the second IP data packet to a communication module, so that the communication module can query a pre-stored mapping relation table of TAG and network slice identifier NSSAI according to the target TAG after receiving the second IP data packet to obtain a target NSSAI corresponding to the target TAG, and carrying out reduction processing on the second IP data packet to obtain the first IP data packet before marking processing, and routing the first IP data packet to a target network slice corresponding to the target NSSAI.

Further, before the target TAG corresponding to the target TD is obtained according to the pre-stored mapping relationship table of the TD and the TAG, the method further includes:

and receiving and storing the mapping relation table of the TD and the TAG, which is sent by the communication module.

Further, before the receiving and storing the mapping relationship table between the TD and the TAG sent by the communication module, the method further includes:

interacting with an operator slice ordering platform to acquire one or more TD (time division) corresponding to a target user identifier;

and sending one or more TD corresponding to the target user identifier to the communication module, so that the communication module distributes different TAGs for the one or more TD, and generates a mapping relation table of the TD and the TAGs.

Further, if the TD type of the target TD is an APPID type, the method further includes:

monitoring an application program corresponding to the target TD;

when the starting of the application program corresponding to the target TD is monitored, transmitting slice establishment control information carrying a target TAG corresponding to the target TD to the communication module, so that the communication module establishes a target network slice corresponding to the target TAG according to a mapping relation table of the TAG and NSSAI;

And when the application program corresponding to the target TD is monitored to exit, transmitting slice withdrawal control information carrying the target TAG corresponding to the target TD to the communication module, so that the communication module removes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI.

Further, if the TD type of the target TD is an IP triplet type or a fully qualified domain name FQDN type, the method further includes:

monitoring network transmission content;

and transmitting slice establishment control information or slice withdrawal control information carrying a target TAG corresponding to the target TD to the communication module according to a monitoring result, so that the communication module establishes a target network slice corresponding to the target TAG according to a mapping relation table of the TAG and NSSAI, or removes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI.

Further, if the TD type of the target TD is an IP triplet type, the sending, according to the monitoring result, slice establishment control information or slice revocation control information carrying the target TAG corresponding to the target TD to the communication module specifically includes:

When the first access to the target IP address or the target IP address and the target port corresponding to the target TD is monitored, slice establishment control information carrying a target TAG corresponding to the target TD is sent to the communication module, so that the communication module establishes a target network slice corresponding to the target TAG according to a mapping relation table of the TAG and NSSAI;

and when the condition that the target IP address or the network transmission content of the target IP address and the target port corresponding to the target TD is not accessed within a specified period is monitored, transmitting slice revocation control information carrying the target TAG corresponding to the target TD to the communication module, so that the communication module removes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI.

Further, if the TD type of the target TD is FQDN type, the sending, according to the monitoring result, slice establishment control information or slice withdrawal control information carrying the target TAG corresponding to the target TD to the communication module specifically includes:

when a domain name request is monitored to request to access a target domain name corresponding to the target TD, slice establishment control information carrying a target TAG corresponding to the target TD is sent to the communication module, so that the communication module establishes a target network slice corresponding to the target TAG according to a mapping relation table of the TAG and NSSAI;

And when the network transmission content of the target domain name corresponding to the target TD is monitored to be not accessed within a specified period, transmitting slice revocation control information carrying the target TAG corresponding to the target TD to the communication module, so that the communication module removes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI.

Further, if the TD type of the target TD is the data network name DNN type, the method further includes:

monitoring the data network name of the target data network corresponding to the network transmission content;

when a slice establishment request of a target user is received, slice establishment control information carrying a target TAG corresponding to the target TD is sent to the communication module, so that the communication module establishes a target network slice corresponding to the target TAG according to a mapping relation table of the TAG and NSSAI;

and when a slice withdrawal request of a target user is received, slice withdrawal control information carrying a target TAG corresponding to the target TD is sent to the communication module, so that the communication module removes a target network slice corresponding to the target TAG according to a mapping relation table of the TAG and NSSAI.

Further, the marking processing for the first IP packet according to the target TAG includes:

writing the target TAG into a preset field of the first IP data packet, wherein the target TAG is of a digital type, and the preset field is an unused field in the first IP data packet.

Further, the writing the target TAG into the preset field of the first IP packet includes:

if the first IP data packet is an internet protocol version 4IPv4 data packet, writing the target TAG into a service type ToS field or an Option field of the first IP data packet;

if the first IP data packet is an internet protocol version 6IPv6 data packet, writing the target TAG into a communication class TrafficClass field or an EXTENSION packet HEADER data field of an EXTENSION packet HEADER EXTENSION HEADER of the first IP data packet.

Further, the writing the target TAG into the Option field of the first IP packet specifically includes:

and if the head length IHL field value of the first IP data packet header is 20, modifying the value of the IHL field to 24, and writing the target TAG into an Option field of the first IP data packet header extension.

Further, the writing the target TAG into an extended HEADER data field of an EXTENSION HEADER of the first IP packet specifically includes:

modifying the value of the next packet header field of the last extension packet header in the first IP data packet into a first value, wherein the first value is other values except the defined extension packet header type value;

adding a new extension packet header into the first IP data packet;

setting the value of the next packet header field of the new extension packet header to 59, setting the value of the packet header extension length field to a preset multiple of 8, and writing the target TAG into the extension packet header data field of the new extension packet header.

In a second aspect, the present invention provides a method for associating network slices, applied to a communication module, the method comprising:

receiving a second IP data packet sent by a device main body, wherein the second IP data packet is obtained by the device main body after obtaining a target TAG corresponding to a target TD according to a pre-stored mapping relation table of a flow descriptor TD and a TAG TAG, and marking a first IP data packet corresponding to the target TD according to the target TAG;

inquiring a mapping relation table of a prestored TAG and a network slice identifier NSSAI according to the target TAG in the second IP data packet to obtain a target NSSAI corresponding to the target TAG;

Performing reduction processing on the second IP data packet to obtain the first IP data packet before marking processing;

and routing the first IP data packet to a target network slice corresponding to the target NSSAI.

Further, before the receiving the second IP packet sent by the device body, the method further includes:

the method comprises the steps of interactively obtaining one or more TD (time division) corresponding to a target user identifier with an operator slice ordering platform, or receiving one or more TD (time division) corresponding to the target user identifier sent by the equipment main body;

allocating different TAGs to the one or more TD, and generating a mapping relation table of the TD and the TAGs;

and sending the mapping relation table of the TD and the TAG to the equipment main body so that the equipment main body stores the mapping relation table of the TD and the TAG.

Further, the method further comprises:

receiving slice establishment control information which is sent by the equipment main body and carries a target TAG corresponding to the target TD;

acquiring a target NSSAI corresponding to the target TAG in a mapping relation table of the TAG and the NSSAI;

and establishing the target network slice according to the target NSSAI.

Further, the method further comprises:

receiving slice revocation control information which is sent by the equipment main body and carries a target TAG corresponding to the target TD;

Acquiring a target NSSAI corresponding to the target TAG in a mapping relation table of the TAG and the NSSAI, and judging whether other TAGs corresponding to the target NSSAI exist in the mapping relation table of the TAG and the NSSAI;

and if other TAGs corresponding to the target NSSAI do not exist in the mapping relation table of the TAGs and the NSSAI, removing the target network slice corresponding to the target NSSAI.

Further, if the target TAG is of a digital type and the second IP packet is an IP version 4IPv4 packet, the performing reduction processing on the second IP packet includes:

replacing the target TAG written in the service type ToS field of the second IP data packet with a default value; or,

deleting the Option field of the second IP data packet header extension, and modifying the value of the header length IHL field of the second IP data packet header to 20.

Further, if the second IP packet is an IP version 6IPv6 packet, the performing the restoration processing on the second IP packet includes:

replacing the target TAG written in the traffic class field of the second IP data packet with a default value; or,

deleting the added extension packet header written with the target TAG in the second IP data packet, and modifying the value of the next packet header field of the last extension packet header in the second IP data packet after deleting the added extension packet header to 59.

In a third aspect, the present invention provides an apparatus body comprising a slice management agent middleware comprising:

the first IP data packet acquisition module is used for acquiring a first IP data packet corresponding to the target flow descriptor TD;

the target TAG acquisition module is connected with the first IP data packet acquisition module and is used for acquiring a target TAG corresponding to the target TD according to a prestored mapping relation table of the TD and the TAG TAG;

the marking processing module is connected with the target TAG acquisition module and is used for marking the first IP data packet according to the target TAG to obtain a second IP data packet;

and the second IP data packet sending module is connected with the marking processing module and is used for sending the second IP data packet to the communication module, so that the communication module can query a pre-stored mapping relation table of the TAG and the network slice identifier NSSAI according to the target TAG after receiving the second IP data packet to obtain a target NSSAI corresponding to the target TAG, and the second IP data packet is subjected to reduction processing to obtain the first IP data packet before marking processing and route the first IP data packet to a target network slice corresponding to the target NSSAI.

In a fourth aspect, the present invention provides an apparatus body comprising a memory having a computer program stored therein and a processor arranged to run the computer program to implement the method of association of network slices of the first aspect.

In a fifth aspect, the present invention provides a communication module, including a slice management service middleware, the slice management service middleware including:

the second IP data packet receiving module is used for receiving a second IP data packet sent by the equipment main body, wherein the second IP data packet is obtained by the equipment main body after obtaining a target TAG corresponding to a target TD according to a pre-stored mapping relation table of a flow descriptor TD and a TAG TAG and marking the first IP data packet corresponding to the target TD according to the target TAG;

the target slice identification inquiring module is connected with the second IP data packet receiving module and is used for inquiring a mapping relation table of a prestored TAG and a network slice identification NSSAI according to the target TAG in the second IP data packet to obtain a target NSSAI corresponding to the target TAG;

the reduction processing module is connected with the target slice identification inquiry module and is used for carrying out reduction processing on the second IP data packet to obtain the first IP data packet before marking processing;

And the route transmission module is connected with the reduction processing module and is used for routing the first IP data packet to the target network slice corresponding to the target NSSAI.

In a sixth aspect, the present invention provides a communications module comprising a memory having a computer program stored therein and a processor arranged to run the computer program to implement the method of association of network slices of the second aspect.

In a seventh aspect, the present invention provides a terminal device, including a device main body and a communication module;

the device body is configured to perform the method for associating network slices according to the first aspect;

the communication module is used for executing the association method of the network slice according to the second aspect.

In an eighth aspect, the present invention provides a computer readable storage medium, on which a computer program is stored, the computer program implementing the method for associating network slices according to the first aspect, when executed by a processor.

In a ninth aspect, the present invention provides a computer readable storage medium, on which a computer program is stored, the computer program implementing the method for associating network slices according to the second aspect.

According to the network slice association method, the equipment main body, the communication module and the terminal equipment, when network transmission data exists in an application or service on the equipment main body, the equipment main body acquires a first IP data packet corresponding to a target TD, acquires the target TAG corresponding to the target TD according to a prestored mapping relation table of the TD and the TAG TAG, then performs marking processing on the first IP data packet according to the target TAG to obtain a second IP data packet, and sends the second IP data packet to the communication module, after receiving the second IP data packet, the communication module inquires a prestored mapping relation table of the TAG and a network slice identifier NSSAI according to the target TAG, obtains a target NSSAI corresponding to the target TAG, and performs reduction processing on the second IP data packet, so that the first IP data packet before marking processing is obtained, and then the first IP data packet is routed to a target network slice corresponding to the target NSSAI, so that the established multiple networks and the equipment main body can be associated with different networks or different network slices can be used in the network, and the network can be more favorably used in the industry, and the network slice can be associated with each other, and the network can be transmitted to the service of the network slice.

Drawings

FIG. 1 is a scene diagram of a method for associating network slices according to embodiment 1 of the present invention;

fig. 2 is a flowchart of a method for associating network slices according to embodiment 1 of the present invention;

fig. 3 is a schematic structural diagram of an IPv4 packet header according to an embodiment of the present invention;

fig. 4 is a schematic structural diagram of an IPv6 packet header according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of an IPv6 packet extension header according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of an extension packet header written with a marking tag according to an embodiment of the present invention;

FIG. 7 is an interactive schematic diagram of a method for associating network slices according to an embodiment of the invention;

FIG. 8 is a flowchart of a method for associating network slices according to embodiment 2 of the present invention;

fig. 9 is a schematic structural view of a device body according to embodiment 3 of the present invention;

fig. 10 is a schematic view of the structure of a device body according to embodiment 4 of the present invention;

fig. 11 is a schematic structural diagram of a communication module according to embodiment 5 of the present invention;

fig. 12 is a schematic structural diagram of a communication module according to embodiment 6 of the present invention;

fig. 13 is a schematic structural diagram of a terminal device in embodiment 7 of the present invention.

Detailed Description

In order to make the technical scheme of the present invention better understood by those skilled in the art, the following detailed description of the embodiments of the present invention will be given with reference to the accompanying drawings.

It is to be understood that the specific embodiments and figures described herein are merely illustrative of the invention, and are not limiting of the invention.

It is to be understood that the various embodiments of the invention and the features of the embodiments may be combined with each other without conflict.

It is to be understood that only the portions relevant to the present invention are shown in the drawings for convenience of description, and the portions irrelevant to the present invention are not shown in the drawings.

It should be understood that each unit and module in the embodiments of the present invention may correspond to only one physical structure, may be formed by a plurality of physical structures, or may be integrated into one physical structure.

It will be appreciated that, without conflict, the functions and steps noted in the flowcharts and block diagrams of the present invention may occur out of the order noted in the figures.

It is to be understood that the flowcharts and block diagrams of the present invention illustrate the architecture, functionality, and operation of possible implementations of systems, apparatuses, devices, methods according to various embodiments of the present invention. Where each block in the flowchart or block diagrams may represent a unit, module, segment, code, or the like, which comprises executable instructions for implementing the specified functions. Moreover, each block or combination of blocks in the block diagrams and flowchart illustrations can be implemented by hardware-based systems that perform the specified functions, or by combinations of hardware and computer instructions.

It should be understood that the units and modules related in the embodiments of the present invention may be implemented by software, or may be implemented by hardware, for example, the units and modules may be located in a processor.

It should be noted that, the scenario diagrams described in the embodiments of the present application are for more clearly describing the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application, and those skilled in the art can know that, with evolution of a network architecture and occurrence of a new service scenario, the technical solutions provided in the embodiments of the present application are applicable to similar technical problems.

As shown in fig. 1, a scene diagram of a network slice association method provided in an embodiment of the present application is shown, where each portion is described as follows:

(1) And (3) a host computer: that is, the device main body generally refers to a part of the terminal device except the communication module, the terminal device may be a POS machine, a vehicle-mounted terminal, a logistics handheld terminal, or the like, a plurality of applications or services on the device main body are respectively carried by corresponding application programs, and the slicing application generally refers to an application program needing to use network slicing, wherein the slicing application needs to follow a certain specification when using the network slicing, in order to associate a plurality of slicing applications on the device main body with a plurality of established network slicing, a slicing management agent middleware is provided on the device main body, and it is required to be noted that the slicing management agent middleware may be developed by an operator and provided for a terminal device manufacturer to integrate in the device main body. The slice management agent middleware is used for receiving and storing a mapping relation table of TD (Traffic Descriptor ) and TAG TAG transmitted by a communication module through USB CDC (Communication Device Class, communication equipment class) equipment drive, acquiring corresponding IP data packets when the slice is applied with network transmission data, wherein each IP data packet has a corresponding target TD, acquiring the target TAG corresponding to the target TD according to the prestored mapping relation table of TD and TAG by the slice management agent middleware, marking the first IP data packet (namely the currently acquired IP data packet) according to the target TAG to obtain a second IP data packet, and transmitting the second IP data packet to the communication module through network drive.

(2) Communication module: the wireless communication module is a modularized assembly integrating a chip, a memory, a power amplifier device, an antenna interface, a functional interface and the like on a circuit board, and achieves the functions of radio wave receiving and transmitting, channel noise filtering, mutual conversion between analog signals and digital signals and the like. Each terminal equipment can access to the network through a wireless communication module, so that the data wireless transmission requirement is met, and the wireless communication module is key equipment for realizing intelligent networking. The communication module comprises a module AP (Application Processor ) and a module modem, wherein the module AP is mainly responsible for running an operating system and an application program, and the module modem is a module CP (coprocessor), also called a baseband, and is mainly responsible for carrying out wireless communication signal modulation and demodulation and related protocol processing. In order to correlate the second IP data packet transmitted by the device main body with the plurality of network slices, a slice management service middleware developed by an operator is provided on the communication module, and the slice management service middleware is used for inquiring a pre-stored mapping relation table of TAG and network slice identifier nsai according to the target TAG in the second IP data packet after receiving the second IP data packet, obtaining a target nsai corresponding to the target TAG, reducing the second IP data packet, obtaining a first IP data packet before marking, and routing the first IP data packet to the target network slice corresponding to the target nsai through a virtual network card.

(3) Operator slice subscription platform: the subscription information of the user is stored on the mobile phone, the subscription information comprises a mapping relation between user identifiers, namely TD-APP, the user identifiers can be mobile phone numbers, IMSI and the like, and the TD can be flexibly configured according to the service subscription condition of the user or according to service requirements. In order to improve the security of the system and reduce the cost of the developer, the slicing management service middleware developed by the operator can obtain the TD of the user, and compared with the method of obtaining the TD by the APP or the OS or the modem/chip, the slicing management service middleware obtains the TD of the user, so that the docking complexity and the development cost are lower.

Based on the scene diagram shown in fig. 1, related embodiments of a network slice association method, an apparatus main body, a communication module, and a terminal device related to the present application are described below.

Example 1:

the embodiment provides a method for associating network slices, which is applied to an equipment main body, as shown in fig. 2, and includes:

step S101: and acquiring a first IP data packet corresponding to the target traffic descriptor TD.

In this embodiment, the device main body stores in advance a mapping relationship between TD and APP or between a user identifier and TD and APP, where the user identifier may specifically be a mobile phone number, and the TD may be flexibly configured according to a service subscription situation of a user or according to a service requirement, and when an application or service on the device main body has network transmission data, the device main body obtains a first IP packet corresponding to a target TD, where the TD is classified into 4 types: APPID, IP triplet, FQDN, DNN. The meanings of these 4 types of TDs are as follows:

(a) The TD of the APPID type indicates that all network transmission data of a certain APP are to be transmitted through the associated slice;

(b) The TD of the IP triplet type indicates that network transmission data to and from a certain target IP address or a target port thereof are transmitted through the associated slice;

(c) The TD of the FQDN type indicates that network transmission data to and from a certain target domain name server are transmitted through the association slice;

(d) The TD of DNN type indicates that network transmission data to be set by a specific data network name (Data Network Name) of a certain operator is transmitted through an association slice, and DNN functions similarly to APN on a mobile phone.

Example information for a TD containing, for example, four types of IP triples, FQDN, APPID, DNN is as follows:

wherein 186XXXXXX is the target user identification, TD of IP triplet type is 192.268.1.100 and fe 80:2a76:64e9:b584:f24b, TD of FQDN type is www.baidu.com, TD of APPID type is com uniicom.

Step S102: and acquiring a target TAG corresponding to the target TD according to a prestored mapping relation table of the TD and the TAG TAG.

In this embodiment, the mapping relation table of TD and TAG is used to store all the TD information of the user and the TAG corresponding to each TD, and the target TAG corresponding to the target TD can be queried through the mapping relation table of TD and TAG.

Optionally, before the target TAG corresponding to the target TD is obtained according to the pre-stored mapping relationship table of the TD and the TAG, the method further includes:

In this embodiment, the mapping relation table of TD and TAG may be generated by the communication module and synchronized to the device main body. Specifically, the communication module may obtain one or more TDs corresponding to the target user identifier in an interaction manner with the operator slice subscription platform, allocate different TAGs to the one or more TDs, and then generate a mapping relationship table of the TDs and the TAGs. Or the equipment main body interacts with the operator slicing ordering platform to acquire one or more TD corresponding to the target user identifier, the one or more TD corresponding to the target user identifier is transmitted to the communication module, and after the communication module receives the one or more TD corresponding to the target user identifier transmitted by the equipment main body, different TAGs are allocated to the one or more TD, and a mapping relation table of the TD and the TAGs is generated. And the communication module sends the mapping relation table of the TD and the TAG to the equipment main body, and the equipment main body stores the mapping relation table of the TD and the TAG.

In the course of research and practice of the prior art, the inventors found that: (1) The TD is acquired from the operator slice ordering platform by the APP, the feasibility is minimum, and the system safety, the docking complexity and the development cost of a developer are involved. (2) The TD is obtained through an OS (i.e. an operating system), the feasibility is low, although the automatic completion of the operating system is the most ideal situation for the APP, industrial cooperation is involved, for example, an operating system development company such as Google is docked with a three-major-operator service platform in China, the operating system automatically obtains, identifies application and matches TD, the difficulty of cooperation and the force of operation Shang Zhangkong face unknown problems, and the feasibility is low. (3) The TD is obtained by a modem/chip manufacturer, and the feasibility is low, as in (2), so that in order to improve the safety of the system and reduce the cost of a developer, the invention is divided into the following two TD obtaining modes from the viewpoint of being beneficial to operators:

1) The operator develops a slice management service middleware which is integrated in the communication module firmware, acquires TD from an operator slice ordering platform according to user subscription information (such as a mobile phone number), then provides the TD to a slice management agent middleware on the equipment main body side upwards, and initiates a subsequent flow;

2) The operator development slice management agent middleware is provided for the terminal equipment manufacturer to be integrated in the terminal equipment main body, the operator development slice management agent middleware acquires TD from the operator slice ordering platform according to user subscription information (such as a mobile phone number), and then is provided for the slice management service middleware on the communication module side downwards, and then a subsequent flow is initiated.

The two modes are that middleware developed by an operator is responsible for acquiring TD information corresponding to a user in an interaction manner with an operator slice ordering platform, and the only difference is that the slice management service middleware integrated in a communication module is acquired from the slice ordering platform or the slice management agent middleware integrated in a terminal equipment main body is acquired from the slice ordering platform. Because the business of the operator, the customer of the operator and the system of the operator are all controlled by the closed loop of the operator, the system has high safety and lower docking complexity and development cost.

Optionally, if the TD type of the target TD is an APPID type, the method further includes:

monitoring an application program corresponding to the target TD;

In this embodiment, after receiving a mapping relation table of TDs and TAGs sent by a communication module, an apparatus main body monitors application programs corresponding to TDs of all APPID types in the mapping relation table, initiates slice establishment control information to the communication module through a USB/CDC apparatus when an APP is monitored to start, and initiates slice withdrawal control information to the communication module through the USB/CDC apparatus when an APP is monitored to withdraw, wherein the slice withdrawal control information carries a target TAG corresponding to a target TD of the APP to start or withdraw. It should be noted that, the slice establishment control information and slice revocation control information may also be actively requested by the application program to establish or revoke the corresponding target network slice.

Optionally, if the TD type of the target TD is an IP triplet type or a fully qualified domain name FQDN type, the method further comprises:

monitoring network transmission content;

In this embodiment, if there is a TD of the IP triplet type or the FQDN type in the mapping relationship table of the TD and the TAG, the network transmission content on the device main body may be monitored, for example, by dynamically monitoring through a netfilter network framework of linux, where the netfilter framework provides a series of network hooks, and an IP packet triggers the hooks to execute functions registered on the hooks when passing through a network protocol stack. I.e. when accessing a certain IP address or domain name, the corresponding mode may be triggered to establish a slice, and when no network access is performed for a specified time, the corresponding slice is revoked.

Specifically, for a target TD of an IP triplet type, when a target IP address or the target IP address and the target port corresponding to the target TD are monitored to be accessed for the first time, slice establishment control information carrying a target TAG corresponding to the target TD is sent to a communication module, so that the communication module establishes a target network slice corresponding to the target TAG according to a mapping relation table of the TAG and NSSAI; similarly, when it is monitored that the target IP address corresponding to the target TD or the network transmission content of the target IP address and the target port is not accessed within a specified period, slice revocation control information carrying the target TAG corresponding to the target TD is sent to the communication module, so that the communication module removes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI.

Specifically, for a target TD of FQDN type, when a domain name request is monitored to request access to a target domain name corresponding to the target TD, slice establishment control information carrying a target TAG corresponding to the target TD is sent to the communication module, so that the communication module establishes a target network slice corresponding to the target TAG according to a mapping relation table of the TAG and NSSAI; similarly, when the network transmission content of the target domain name corresponding to the target TD is monitored to be not accessed within a specified period, slice revocation control information carrying the target TAG corresponding to the target TD is sent to the communication module, so that the communication module removes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI.

Optionally, if the TD type of the target TD is the data network name DNN type, the method further includes:

In this embodiment, the DNN type is a global control type on the terminal device, and for TDs of the DNN type, all data packets on the terminal device are transmitted through a slice, and are not generally used simultaneously with other 3 types of TDs, and when in use, a user usually manually requests to establish a slice or cancel a slice. And after receiving a slice establishment request or a slice withdrawal request of a target user, the terminal equipment main body sends slice establishment control information or slice withdrawal control information to the communication module through the USB/CDC equipment so that the communication module establishes or removes a target network slice corresponding to the target TAG.

In this embodiment, when the communication module receives the slice establishment control information carrying the target TAG corresponding to the target TD sent by the device main body, the target nsai corresponding to the target TAG in the mapping relation table of the TAG and nsai is obtained, and the target network slice is established according to the target nsai. Similarly, when the communication module receives slice withdrawal control information carrying a target TAG corresponding to a target TD sent by the equipment main body, acquiring a target NSSAI corresponding to the target TAG in a mapping relation table of the TAG and the NSSAI, and judging whether other TAGs corresponding to the target NSSAI exist in the mapping relation table of the TAG and the NSSAI; and if other TAGs corresponding to the target NSSAI do not exist in the mapping relation table of the TAGs and the NSSAI, removing the target network slice corresponding to the target NSSAI. It should be noted that, the mapping relationship table of the TAG and the nsai is stored in the communication module in advance, specifically, after different TAGs are allocated to one or more TDs by the communication module, the different TAGs may be allocated according to TAG information, where one nsai may correspond to a plurality of TAGs, for example, the mapping relationship table of the established TAG and nsai may be as follows:

00000001：NSSAI0

00000010：NSSAI1

00000011：NSSAI0

00000100：NSSAI2

……

11111111：NSSAI7

it should be noted that, at present, the 3GPP communication standard and the underlying baseband chip support 8 slices of concurrency at maximum, and the communication module base band establishes 8 slices of concurrency at maximum, so in the example, the maximum nsai is 7, but there are 255x8 mapping relations theoretically.

The control information assumed to be received by the communication module is as follows:

the setup represents control information of a slice establishment type, the target TD of the slice establishment control information is 192.268.1.100, the corresponding target TAG is 00000001, the teardown represents control information of a slice withdrawal type, the target TD of the slice withdrawal control information is com. After the communication module receives the control information, the control information is analyzed and corresponding slice management operation is executed, namely, a target network slice corresponding to NSSAI0 is established, and whether the target network slice corresponding to NSSAI2 is removed or not is judged according to a mapping relation table of TAG and NSSAI. When no mapping relation exists between other TAGs and NSSAI2 in the mapping relation table of the TAGs and the NSSAI, the network slice is used without other IP transmission links, and then the communication module control module baseband removes the network slice corresponding to the NSSAI 2.

Step S103: and marking the first IP data packet according to the target TAG to obtain a second IP data packet.

Specifically, the target TAG may be written into a preset field of the first IP packet to implement marking processing on the first IP packet, where the target TAG is a numeric value, and the preset field is an unused field, i.e., a reserved field or a field filled with a default value, in the first IP packet.

Optionally, the writing the target TAG into a preset field of the first IP packet includes:

In this embodiment, in order to improve the performance of marking and label removal, the device body may perform marking based on the IPv4/IPv 6IP layer protocol, that is, write the target TAG in a field that is not used by the IPv4/IPv6 packet. In the course of research and practice of the prior art, the inventors found that: from the technical point of view, the cost of marking below the IP layer is relatively high, the driver needs to be modified below the network card driver level, and the driver is matched with a chip, so that the marking is difficult to be carried out by the IP layer protocol, and the marking and the disassembly processing performance is relatively high because no interference is caused to the control layer protocol (ICMP/IGMP), the transmission layer protocol (TCP/UDP), the application layer protocol (HTTP, FTP and the like) and no additional calculation work is needed.

In this embodiment, if the first IP packet is an IPv4 packet and the value of the service type field (i.e., TOS field) is a default value 00000000, this indicates that this field is not used, at this time, the first IP packet may be marked by multiplexing the TOS field with 8 bits, as shown in fig. 3, which shows a schematic structure of the packet header of the IPv4 packet, where the IPv4 packet is composed of a packet header and a data portion, the service type field is located in the packet header of the IPv4 packet, as can be seen from fig. 3, the service type occupies 8 bytes, and in theory, the 8 bits are maximally supported to store 2^8-1=255 TAGs (the default value 00000000 is not used as a TAG), because there may be multiple IP transmission links in one APP at the same time, so that, in theory, marking can be performed by simultaneously supporting 255 independent IP layer transmission links.

Optionally, the writing the target TAG into an Option field of the first IP packet specifically includes:

In this embodiment, if the first IP packet is an IPv4 packet and the value of the service type field (i.e., TOS field) is not the default value 00000000, this indicates that the field is already used, for example, when the application layer protocol needs to occupy the TOS field, the value of the TOS field is not the default value, so the TOS field cannot be used as the marking purpose, and at this time, the Option field (i.e., option field) may be used for marking the first IP packet. It should be noted that the Option field is an optional field, which is mainly used for testing, and is rewritten by the originating device according to the need, and the value of the head length (IHL) field is usually 20, that is, indicates that there is no Option, when the head length is 20, the Option field may be used for marking, that is, the value of the IHL is modified to 24, and a shortest Option portion is extended to 4 bytes, which theoretically supports 2+_32= 4294967296 independent IP layer transmission links for marking, as shown in fig. 3, when the value of the head length field is 20, it will not have an optional Option field, and when the value of the head length field is 24, it has an optional Option field of 4 bytes.

In this embodiment, if the first IP packet is an IPv6 packet and the value of the communication field (i.e., the TrafficClass field) is a default value 00000000, this indicates that the field is not used, at this time, the first IP packet may be marked by multiplexing an 8-bit TrafficClass field, which is similar to the ToS field in IPv4, and also maximally supports and stores 255 types of TAG, trafficClass fields located in the header of the IPv6 packet, as shown in fig. 4, which shows a schematic structural diagram of the header of the IPv6 packet.

Optionally, the writing the target TAG into an extended HEADER data field of an EXTENSION HEADER of the first IP packet specifically includes:

adding a new extension packet header into the first IP data packet;

In this embodiment, the IPv6 data packet is composed of a packet header (40 bytes with a fixed length), an extension packet header, and an upper layer protocol data unit, and if the first IP data packet is an IPv6 data packet, the first IP data packet may also be marked by the extension packet header, and fig. 5 shows a schematic structure diagram of the extension packet header of the IPv6 data packet, where each IPv6 data packet may include a plurality of extension packet headers, and each extension packet header includes a next packet header, a packet header extension length, and an extension packet header data field. Wherein the defined extension header type includes: hop-by-Hop option header (Hop-by-Hop Options Header) with a value of 0; a destination option header (Destination Options Header) having a value of 60; a Routing Header (Routing Header) of 43; a Fragment Header (Fragment Header) of 44; an authentication header (Authentication Header) having a value of 51; an encapsulating security payload header (ESP) of 50, etc., the first value may be any other value than the defined extension header type value, e.g., 70, 71, etc., indicating only that the present IP packet has an extension header.

In this embodiment, in order to improve the protocol processing performance, the length of the IPv6 extension packet header is always set to be an integer multiple of 8 bytes, and the present invention is preferably set to be 8. As shown in fig. 6, there is shown a schematic diagram of an extended header written with a TAG (i.e., target TAG), wherein the value of the next header field is set to 59, indicating that there is no next extended header, the header extension length is 8, indicating that this extended header length is 8 bytes newly added, the extended header data field includes a 32bit TAG and a 16bit reserved field, the 32bit TAG is used to store the target TAG, which theoretically supports 2 x 32 = 4294967296 independent IP layer transport links for the TAG,

Step S104: and sending the second IP data packet to a communication module, so that the communication module can query a pre-stored mapping relation table of TAG and network slice identifier NSSAI according to the target TAG after receiving the second IP data packet to obtain a target NSSAI corresponding to the target TAG, and carrying out reduction processing on the second IP data packet to obtain the first IP data packet before marking processing, and routing the first IP data packet to a target network slice corresponding to the target NSSAI.

In this embodiment, after the communication module receives the second IP packet, the corresponding target nsai is obtained, and the second IP packet is restored, specifically, if the second IP packet is an IPv4 packet, the target TAG written in the ToS field of the second IP packet is replaced with a default value (i.e. 00000000); or deleting the Option field of the second IP data packet header extension, and modifying the value of the header length IHL field of the second IP data packet header to 20; if the second IP data packet is an IPv6 data packet, replacing the target TAG written in the traffic class TrafficClass field of the second IP data packet with a default value (namely 00000000); or deleting the added extension packet header written with the target TAG in the second IP data packet, and modifying the value of the next packet header field of the last extension packet header in the second IP data packet after deleting the added extension packet header to 59, thereby obtaining a first IP data packet before marking, and then, the communication module routes the first IP data packet to a target network slice corresponding to the target NSSAI.

In a specific embodiment, referring to fig. 7, an interaction schematic diagram of a method for associating network slices is shown, where slice application refers to an application program running on a device main body and needing to use network slices, slice management agent middleware is set in the device main body, slice management service middleware is set in a communication module, and taking a target user identifier as a mobile phone number as an example, and the method for associating network slices specifically includes the following steps:

step S01: the slice management service middleware requests the TD information corresponding to the mobile phone number in the communication module from the operator slice ordering platform;

step S02: the operator slice ordering platform returns TD information corresponding to the mobile phone number to the slice management service middleware;

step S03: the slice management service middleware distributes different TAGs for different TD information and generates a mapping relation table of TD and TAGs;

step S04: the slice management service middleware synchronizes a mapping relation table of TD and TAG to the slice management agent middleware for marking subsequent IP data packets;

step S05: the slicing application initiates a request for network transmission;

step S06: the slice management agent middleware monitors the running state (start/exit) of a certain application in the TD information;

Step S07: the slice management agent middleware sends slice establishment control information/slice withdrawal control information corresponding to the application to the slice management service middleware;

step S08: the slice management service middleware control module modem establishes/removes a corresponding network slice;

specifically, if the slice revocation control information is received, whether other TAGs corresponding to the target NSSAI exist in a mapping relation table of the TAGs and the NSSAI is judged first, and if the TAGs do not exist, the control module modem disassembles the corresponding network slice.

Step S09: the module modem returns a result and a corresponding slice identifier;

step S10: the slice application transmits the IP data packet;

step S11: the slice management agent middleware performs marking processing on the corresponding IP data packet according to the mapping relation table of the TD and the TAG which are synchronized previously;

step S12: the slice management agent middleware sends the IP data packet after marking to the slice management service middleware;

step S13: and the slice management service middleware queries a mapping relation table of the TAG and NSSAI according to the marking TAG TAG of the IP data packet, acquires the corresponding NSSAI, restores the IP data packet after marking, and routes the corresponding IP data packet to a correct network slice for transmission.

According to the network slice association method provided by the embodiment, when network transmission data exists in an application or service on an equipment main body, the equipment main body acquires a first IP data packet corresponding to a target TD, acquires the target TAG corresponding to the target TD according to a pre-stored mapping relation table of the TD and the TAG TAG, marks the first IP data packet according to the target TAG to obtain a second IP data packet, and sends the second IP data packet to a communication module, the communication module inquires a pre-stored mapping relation table of the TAG and a network slice identifier NSSAI according to the target TAG in the second IP data packet after receiving the second IP data packet, and reduces the second IP data packet to obtain the first IP data packet before marking, and then routes the first IP data packet to a target network slice corresponding to the target NSSAI, so that the established multiple network slices can be isolated from different services or application network transmission data on the equipment main body, and the multiple network slices can be associated with each other, and the network can be easily carried out in the same industry as the network slice, and the network slice can be transmitted to the service provider.

Example 2:

as shown in fig. 8, the present embodiment provides a method for associating network slices, which is applied to a communication module, and the method includes:

step S201: receiving a second IP data packet sent by a device main body, wherein the second IP data packet is obtained by the device main body after obtaining a target TAG corresponding to a target TD according to a pre-stored mapping relation table of a flow descriptor TD and a TAG TAG, and marking a first IP data packet corresponding to the target TD according to the target TAG;

step S202: inquiring a mapping relation table of a prestored TAG and a network slice identifier NSSAI according to the target TAG in the second IP data packet to obtain a target NSSAI corresponding to the target TAG;

step S203: performing reduction processing on the second IP data packet to obtain the first IP data packet before marking processing;

step S204: and routing the first IP data packet to a target network slice corresponding to the target NSSAI.

Optionally, before the receiving the second IP packet sent by the device body, the method further includes:

Optionally, the method further comprises:

and establishing the target network slice according to the target NSSAI.

Optionally, the method further comprises:

Optionally, if the target TAG is a digital type, and the second IP packet is an internet protocol version 4IPv4 packet, the performing reduction processing on the second IP packet includes:

Optionally, if the second IP packet is an internet protocol version 6IPv6 packet, the performing the restoration processing on the second IP packet includes:

Example 3:

as shown in fig. 9, the present embodiment provides an apparatus main body including a slice management agent middleware 10, the slice management agent middleware 10 including:

a first IP packet obtaining module 11, configured to obtain a first IP packet corresponding to the target traffic descriptor TD;

the target TAG acquisition module 12 is connected with the first IP data packet acquisition module 11 and is used for acquiring a target TAG corresponding to the target TD according to a pre-stored mapping relation table of the TD and the TAG TAG;

The marking processing module 13 is connected with the target TAG acquisition module 12 and is used for marking the first IP data packet according to the target TAG to obtain a second IP data packet;

and the second IP packet sending module 14 is connected to the marking processing module 13, and is configured to send the second IP packet to the communication module, so that after the communication module receives the second IP packet, the communication module queries a mapping relation table of a pre-stored TAG and a network slice identifier nsai according to the target TAG to obtain a target nsai corresponding to the target TAG, and performs reduction processing on the second IP packet to obtain the first IP packet before the marking processing, and routes the first IP packet to a target network slice corresponding to the target nsai.

Optionally, the method further comprises:

and the receiving and storing module is used for receiving and storing the mapping relation table of the TD and the TAG, which is sent by the communication module.

Optionally, the method further comprises:

the platform interaction module is used for interacting with the operator slicing ordering platform and acquiring one or more TD (time division) corresponding to the target user identification;

and the first sending module is used for sending one or more TD corresponding to the target user identifier to the communication module, so that the communication module distributes different TAGs for the one or more TD and generates a mapping relation table of the TD and the TAGs.

Optionally, if the TD type of the target TD is an APPID type, the slice management agent middleware 10 further includes:

the first monitoring module is used for monitoring the application program corresponding to the target TD;

the first control information sending module is used for sending the slice establishment control information carrying the target TAG corresponding to the target TD to the communication module when the application program corresponding to the target TD is monitored to start, so that the communication module establishes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI;

and the second control information sending module is used for sending the slice withdrawal control information carrying the target TAG corresponding to the target TD to the communication module when the application program corresponding to the target TD is monitored to exit, so that the communication module removes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI.

Optionally, if the TD type of the target TD is an IP triplet type or a fully qualified domain name FQDN type, the slice management agent middleware 10 further includes:

the second monitoring module is used for monitoring network transmission content;

and the third control information sending module is used for sending the slice establishment control information or the slice withdrawal control information carrying the target TAG corresponding to the target TD to the communication module according to the monitoring result, so that the communication module establishes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI, or removes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI.

Optionally, if the TD type of the target TD is an IP triplet type, the third control information sending module specifically includes:

the first establishing control information sending unit is used for sending slice establishing control information carrying a target TAG corresponding to the target TD to the communication module when the first access to the target IP address or the target IP address and the target port corresponding to the target TD is monitored, so that the communication module establishes a target network slice corresponding to the target TAG according to a mapping relation table of the TAG and NSSAI;

and the first revocation control information sending unit is used for sending slice revocation control information carrying the target TAG corresponding to the target TD to the communication module when the target IP address corresponding to the target TD or the network transmission content of the target IP address and the target port is not accessed within a specified period of time, so that the communication module removes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI.

Optionally, if the TD type of the target TD is FQDN type, the third control information sending module further includes:

the second establishment control information sending unit is used for sending slice establishment control information carrying a target TAG corresponding to the target TD to the communication module when the request of accessing the target domain name corresponding to the target TD is monitored, so that the communication module establishes a target network slice corresponding to the target TAG according to a mapping relation table of the TAG and NSSAI;

And the second revocation control information sending unit is used for sending the slice revocation control information carrying the target TAG corresponding to the target TD to the communication module when the network transmission content of the target domain name corresponding to the target TD is not accessed within a specified period of time, so that the communication module removes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI.

Optionally, if the TD type of the target TD is the data network name DNN type, the slice management agent middleware 10 further includes:

the third monitoring module is used for monitoring the data network name of the target data network corresponding to the network transmission content;

a fourth control information sending module, configured to send, when receiving a slice establishment request of a target user, slice establishment control information carrying a target TAG corresponding to the target TD to the communication module, so that the communication module establishes a target network slice corresponding to the target TAG according to a mapping relationship table of the TAG and nsai;

and the fifth control information sending module is used for sending the slice withdrawal control information carrying the target TAG corresponding to the target TD to the communication module when receiving the slice withdrawal request of the target user, so that the communication module removes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI.

Optionally, the marking processing module 13 is specifically configured to write the target TAG into a preset field of the first IP packet, where the target TAG is of a digital type, and the preset field is an unused field in the first IP packet.

Optionally, the marking processing module 13 specifically includes:

a first TAG writing module, configured to write, if the first IP packet is an internet protocol version 4IPv4 packet, the target TAG into a service type ToS field or an Option field of the first IP packet;

and the second TAG writing module is used for writing the target TAG into a communication class TrafficClass field or an EXTENSION packet HEADER data field of an EXTENSION packet HEADER EXTENSION HEADER of the first IP data packet if the first IP data packet is an IPv6 data packet of an Internet protocol version 6.

Optionally, the first TAG writing module is specifically configured to write, if the first IP packet is an internet protocol version 4IPv4 packet, the target TAG into a service type ToS field of the first IP packet; or if the value of the header length IHL field of the first IP data packet header is 20, modifying the value of the IHL field to 24, and writing the target TAG into an Option field of the first IP data packet header extension.

Optionally, the second TAG writing module is specifically configured to write the target TAG into a service type ToS field of the first IP packet if the first IP packet is an internet protocol version 4IPv4 packet; or, modifying the value of the next packet header field of the last extension packet header in the first IP data packet to a first value, where the first value is other values except the value of the defined extension packet header type; adding a new extension packet header into the first IP data packet; and setting the value of the next packet header field of the new extension packet header to 59, setting the value of the packet header extension length field to a preset multiple of 8, and writing the target TAG into an extension packet header data field of the new extension packet header.

Example 4:

as shown in fig. 10, the present embodiment provides an apparatus main body including a memory 31 and a processor 32, the memory 31 storing a computer program therein, the processor 32 being configured to run the computer program to perform the network slice association method in embodiment 1.

The memory 31 is connected to the processor 32, the memory 31 may be a flash memory, a read-only memory, or other memories, and the processor 32 may be a central processing unit or a single chip microcomputer.

Example 5:

as shown in fig. 11, the present embodiment provides a communication module, including a slice management service middleware 20, where the slice management service middleware 20 includes:

a second IP packet receiving module 21, configured to receive a second IP packet sent by a device main body, where the second IP packet is obtained by obtaining, by the device main body, a target TAG corresponding to a target TD according to a mapping relationship table of a pre-stored traffic descriptor TD and a TAG, and performing marking processing on a first IP packet corresponding to the target TD according to the target TAG;

the target slice identifier query module 22 is connected with the second IP data packet receiving module 21, and is configured to query a mapping relationship table of a prestored TAG and a network slice identifier nsai according to the target TAG in the second IP data packet to obtain a target nsai corresponding to the target TAG;

the restoration processing module 23 is connected with the target slice identification query module 22 and is used for carrying out restoration processing on the second IP data packet to obtain the first IP data packet before marking processing;

and the route transmission module 24 is connected with the reduction processing module 23 and is used for routing the first IP data packet to the target network slice corresponding to the target NSSAI.

Optionally, the method further comprises:

the control information establishment receiving module is used for receiving slice establishment control information which is sent by the equipment main body and carries a target TAG corresponding to the target TD;

an NSSAI acquisition module, configured to acquire a target NSSAI corresponding to the target TAG in a mapping relationship table of the TAG and NSSAI;

and the network slice establishing module is used for establishing the target network slice according to the target NSSAI.

Optionally, the method further comprises:

the revocation control information receiving module is used for receiving slice revocation control information which is sent by the equipment main body and carries a target TAG corresponding to the target TD;

The judging module is used for acquiring a target NSSAI corresponding to the target TAG in the mapping relation table of the TAG and the NSSAI and judging whether other TAGs corresponding to the target NSSAI exist in the mapping relation table of the TAG and the NSSAI or not;

and the dismantling module is used for dismantling the target network slice corresponding to the target NSSAI if other TAGs corresponding to the target NSSAI do not exist in the mapping relation table of the TAGs and the NSSAI.

Optionally, the target TAG is of a digital type, and if the second IP packet is an IP version 4IPv4 packet, the restoration processing module 23 includes:

the ToS field restoring module is used for replacing the target TAG written in the service type ToS field of the second IP data packet with a default value;

and the Option field restoration module is used for deleting the Option field of the second IP data packet header extension and modifying the value of the header length IHL field of the second IP data packet header to 20.

Optionally, if the second IP packet is an internet protocol version 6IPv6 packet, the restoration processing module 23 further includes:

the TrafficClass field restoring module is used for replacing the target TAG written in the traffic class TrafficClass field of the second IP data packet with a default value;

And the extension packet header restoring module is used for deleting the extension packet header added in the second IP data packet and written with the target TAG, and modifying the value of the next packet header field of the last extension packet header in the second IP data packet after deleting the added extension packet header to 59.

Example 6:

as shown in fig. 12, the present embodiment provides a communication module, including a memory 41 and a processor 42, wherein the memory 41 stores a computer program, and the processor 42 is configured to execute the computer program to perform the network slice association method in embodiment 2.

The memory 41 is connected to the processor 42, the memory 41 may be a flash memory, a read-only memory, or other memories, and the processor 42 may be a central processing unit or a single chip microcomputer.

Example 7:

as shown in fig. 13, the present embodiment provides a terminal device including a device main body 51 and a communication module 52;

the apparatus main body 51 is for performing the association method of network slices in embodiment 1;

the communication module 52 is configured to perform the association method of network slices in embodiment 2.

Example 8:

the present embodiment provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the network slice association method in embodiment 1 described above.

Computer-readable storage media include volatile or nonvolatile, removable or non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, computer program modules or other data. Computer-readable storage media includes, but is not limited to, RAM (Random Access Memory ), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory, charged erasable programmable Read-Only Memory), flash Memory or other Memory technology, CD-ROM (Compact Disc Read-Only Memory), digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.

Example 9:

the present embodiment provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the network slice association method in embodiment 2 described above.

In the network slice association method, the device main body, the communication module and the terminal device provided in embodiments 2 to 9, when network transmission data exists in an application or service on the device main body, the device main body obtains a first IP data packet corresponding to a target TD, obtains a target TAG corresponding to the target TD according to a pre-stored mapping relationship table of the TD and the TAG, and then performs marking processing on the first IP data packet according to the target TAG to obtain a second IP data packet, and sends the second IP data packet to the communication module, after receiving the second IP data packet, the communication module queries a pre-stored mapping relationship table of the TAG and a network slice identifier NSSAI according to the target TAG therein to obtain a target NSSAI corresponding to the target TAG, and performs reduction processing on the second IP data packet, thereby obtaining the first IP data packet before marking processing, and then routing the first IP data packet to a target network slice corresponding to the target sansi, so that the established multiple network slices and the application or service on the device main body can be isolated from each other, and the network can be easily associated with each other, and the network can be transmitted to the service on the network slice, and the service can be isolated from the service carrier 5.

It is to be understood that the above embodiments are merely illustrative of the application of the principles of the present invention, but not in limitation thereof. Various modifications and improvements may be made by those skilled in the art without departing from the spirit and substance of the invention, and are also considered to be within the scope of the invention.

Claims

1. The method is characterized by being applied to a slice management agent middleware in a device main body, wherein the device main body is a part of terminal equipment except a communication module, and the terminal equipment is externally hung with the communication module, and the method comprises the following steps:

acquiring a first IP data packet corresponding to a target flow descriptor TD;

the second IP data packet is sent to a slice management service middleware in a communication module, so that the slice management service middleware can query a pre-stored mapping relation table of TAG and a network slice identifier NSSAI according to the target TAG in the second IP data packet after receiving the second IP data packet to obtain a target NSSAI corresponding to the target TAG, and perform reduction processing on the second IP data packet to obtain the first IP data packet before marking processing, and route the first IP data packet to a target network slice corresponding to the target NSSAI;

The marking processing for the first IP packet according to the target TAG includes:

writing the target TAG into a preset field of the first IP data packet IP layer, wherein the target TAG is of a numerical value type, and the preset field is an unused field in the first IP data packet IP layer.

2. The method according to claim 1, wherein before the obtaining the target TAG corresponding to the target TD according to the pre-stored mapping relationship table of the TD and the TAG, the method further comprises:

and receiving and storing the mapping relation table of the TD and the TAG, which is sent by the slice management service middleware.

3. The method according to claim 2, wherein before receiving and storing the mapping relationship table between the TDs and TAGs sent by the slice management service middleware, the method further comprises:

and sending one or more TD (time division) corresponding to the target user identifier to the slice management service middleware, so that the slice management service middleware distributes different TAGs for the one or more TD, and generates a mapping relation table of the TD and the TAGs.

4. The method of associating network slices according to claim 1, wherein if the TD type of the target TD is an APPID type, the method further comprises:

monitoring an application program corresponding to the target TD;

when the starting of the application program corresponding to the target TD is monitored, slice establishment control information carrying a target TAG corresponding to the target TD is sent to the slice management service middleware, so that the slice management service middleware establishes a target network slice corresponding to the target TAG according to a mapping relation table of the TAG and NSSAI;

and when the application program corresponding to the target TD is monitored to exit, transmitting slice withdrawal control information carrying the target TAG corresponding to the target TD to the slice management service middleware, so that the slice management service middleware removes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI.

5. The method of claim 1, wherein if the TD type of the target TD is an IP triplet type or a fully qualified domain name FQDN type, the method further comprises:

monitoring network transmission content;

And transmitting slice establishment control information or slice withdrawal control information carrying a target TAG corresponding to the target TD to the slice management service middleware according to a monitoring result, so that the slice management service middleware establishes a target network slice corresponding to the target TAG according to a mapping relation table of the TAG and NSSAI, or removes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI.

6. The method according to claim 5, wherein if the TD type of the target TD is an IP triplet type, the sending, according to the monitoring result, slice establishment control information or slice revocation control information carrying a target TAG corresponding to the target TD to the slice management service middleware specifically includes:

when the first access to the target IP address or the target IP address and the target port corresponding to the target TD is monitored, slice establishment control information carrying a target TAG corresponding to the target TD is sent to the slice management service middleware, so that the slice management service middleware establishes a target network slice corresponding to the target TAG according to a mapping relation table of the TAG and NSSAI;

And when the condition that the target IP address or the network transmission content of the target IP address and the target port corresponding to the target TD is not accessed within a specified period is monitored, transmitting the slice revocation control information carrying the target TAG corresponding to the target TD to the slice management service middleware, so that the slice management service middleware removes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI.

7. The method according to claim 5, wherein if the TD type of the target TD is FQDN type, the sending, according to the monitoring result, slice establishment control information or slice withdrawal control information carrying the target TAG corresponding to the target TD to the slice management service middleware specifically includes:

when a domain name request is monitored to request to access a target domain name corresponding to the target TD, slice establishment control information carrying a target TAG corresponding to the target TD is sent to the slice management service middleware, so that the slice management service middleware establishes a target network slice corresponding to the target TAG according to a mapping relation table of the TAG and NSSAI;

and when the network transmission content of the target domain name corresponding to the target TD is monitored to be not accessed within a specified period, transmitting slice withdrawal control information carrying the target TAG corresponding to the target TD to the slice management service middleware, so that the slice management service middleware removes the target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI.

8. The method of associating network slices according to claim 1, wherein if the TD type of the target TD is a data network name DNN type, the method further comprises:

when a slice establishment request of a target user is received, slice establishment control information carrying a target TAG corresponding to the target TD is sent to the slice management service middleware, so that the slice management service middleware establishes a target network slice corresponding to the target TAG according to a mapping relation table of the TAG and NSSAI;

and when receiving a slice withdrawal request of a target user, transmitting slice withdrawal control information carrying a target TAG corresponding to the target TD to the slice management service middleware, so that the slice management service middleware removes a target network slice corresponding to the target TAG according to the mapping relation table of the TAG and NSSAI.

9. The method of associating network slices according to claim 1, wherein writing the target TAG into a preset field of the first IP packet IP layer comprises:

10. The method for associating network slices according to claim 9, wherein the writing the target TAG into the Option field of the first IP packet specifically comprises:

11. The method for associating network slices according to claim 9, wherein writing the target TAG into an extended HEADER data field of an EXTENSION HEADER of the first IP packet specifically comprises:

adding a new extension packet header into the first IP data packet;

12. A method for associating network slices, which is applied to slice management service middleware in a communication module, the method comprising:

receiving a second IP data packet sent by a slice management agent middleware in a device main body, wherein the second IP data packet is obtained by the slice management agent middleware obtaining a target TAG corresponding to a target TD according to a pre-stored mapping relation table of a flow descriptor TD and the TAG TAG and marking the first IP data packet corresponding to the target TD according to the target TAG, wherein the device main body is a part of terminal equipment except a communication module, and the terminal equipment is externally hung with the communication module;

routing the first IP data packet to a target network slice corresponding to the target NSSAI;

the marking processing of the first IP packet corresponding to the target TD according to the target TAG includes:

13. The method of claim 12, wherein prior to receiving the second IP packet sent by the slice management agent middleware within the device host, the method further comprises:

the method comprises the steps of interactively obtaining one or more TD (time division) corresponding to a target user identifier with an operator slice ordering platform, or receiving one or more TD (time division) corresponding to the target user identifier sent by the slice management agent middleware;

and sending the mapping relation table of the TD and the TAG to a slice management agent middleware so that the slice management agent middleware stores the mapping relation table of the TD and the TAG.

14. The method of association of network slices according to claim 12, further comprising:

receiving slice establishment control information which is sent by the slice management agent middleware and carries a target TAG corresponding to the target TD;

and establishing the target network slice according to the target NSSAI.

15. The method of association of network slices according to claim 12, further comprising:

receiving slice withdrawal control information which is sent by the slice management agent middleware and carries a target TAG corresponding to the target TD;

16. The method according to claim 12, wherein if the second IP packet is an IP version 4IPv4 packet, the performing the restoration processing on the second IP packet includes:

17. The method according to claim 16, wherein if the second IP packet is an IP version 6IPv6 packet, the performing the restoration processing on the second IP packet includes:

18. An apparatus main body, wherein the apparatus main body is a part of a terminal apparatus other than a communication module, the terminal apparatus is externally hung with the communication module, the apparatus main body includes a slice management agent middleware, and the slice management agent middleware includes:

the second IP data packet sending module is connected with the marking processing module and is used for sending the second IP data packet to a slice management service middleware in the communication module, so that the slice management service middleware can inquire a mapping relation table of a prestored TAG and a network slice identifier NSSAI according to the target TAG in the second IP data packet after receiving the second IP data packet to obtain a target NSSAI corresponding to the target TAG, and the second IP data packet is subjected to reduction processing to obtain the first IP data packet before marking processing and route the first IP data packet to a target network slice corresponding to the target NSSAI;

the marking processing module is specifically configured to write the target TAG into a preset field of the first IP packet IP layer, where the target TAG is of a numeric type, and the preset field is an unused field in the first IP packet IP layer.

19. An apparatus body comprising a memory and a processor, the memory having stored therein a computer program, the processor being arranged to run the computer program to implement the method of association of network slices as claimed in any of claims 1-11.

20. A communication module comprising slice management service middleware, the slice management service middleware comprising:

the second IP data packet receiving module is used for receiving a second IP data packet sent by a slice management agent middleware in a device main body, wherein the second IP data packet is obtained by the slice management agent middleware obtaining a target TAG corresponding to the target TD according to a pre-stored mapping relation table of a flow descriptor TD and a TAG TAG and then marking the first IP data packet corresponding to the target TD according to the target TAG, the device main body is a part of terminal equipment except a communication module, and the terminal equipment is externally hung with the communication module;

The route transmission module is connected with the reduction processing module and is used for routing the first IP data packet to a target network slice corresponding to the target NSSAI;

21. A communication module comprising a memory and a processor, the memory having stored therein a computer program, the processor being arranged to run the computer program to implement the method of association of network slices as claimed in any of claims 12-17.

22. The terminal equipment is characterized by comprising an equipment main body and a communication module;

the device body for performing the association method of network slices of any one of claims 1-11;

the communication module is configured to perform the method of association of network slices of any one of claims 12-17.

23. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the method of association of network slices according to any of claims 1-11.

24. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the method of association of network slices according to any of claims 12-17.