Communication method and related equipment

Abstract

The invention provides a communication method and related equipment, and relates to the technical field of communication. The method comprises the following steps: a network slice management function collects available slice subnet docking identification information; the life cycle of the slice subnet docking identifier is from a network slice creation stage, a network slice modification stage, a network slice deletion stage to a network slice termination stage, the cross-domain slice subnet docking identifier life cycle management and configuration can be realized, the configuration efficiency is improved, and the user experience is improved. Configuration conflicts of butt-joint parameters of slice subnets are reduced, accuracy is high, and operation, maintenance and management requirements on the network are simplified.

Description

Background Art

[0002] Network slicing is an important means to provide differentiated service subscription agreements (Service-Level Agreement, SLA) for enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (uRLLC), and massive machine type communications (mMTC) for the fifth generation mobile communication technology (5G). The end-to-end slicing of the 5G network is composed of three different sub-slices: the radio access network slicing subnet, the transport network slicing subnet, and the core network slicing subnet. The cross-domain connection.

[0003] In related technologies, one configuration method is for network operators of each slice subnet to negotiate cross-professional slice docking parameters; another configuration method is for the access network and the core network's network slice subnet instance (NSSI) to be uniquely identified by a single network slice selection auxiliary information (S-NSSAI). However, the manual configuration method is cumbersome, inefficient, and prone to conflicts in docking configurations, with a high error rate; the docking method identified by a single network slice selection auxiliary information is complex and inefficient.

[0004] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0005] The present disclosure provides a communication method and related equipment, which at least to a certain extent overcome the problems of low configuration efficiency and high error rate in the existing manual configuration of cross-professional slice docking identifiers.

[0006] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by the practice of the present disclosure.

[0007] According to one aspect of the present disclosure, a communication method is provided, which is applied to a network slice management function, and the method includes: collecting available slice subnet docking identification information; performing lifecycle management on the slice subnet docking identification, wherein the lifecycle of the slice subnet docking identification ranges from a network slice creation stage, a network slice modification stage, a network slice deletion stage to a network slice termination stage.

[0008] In one embodiment of the present disclosure, the available slice subnet docking identification information includes the docking identification between the access network slice subnet and the transmission network slice subnet, and the docking identification between the transmission network slice subnet and the core network slice subnet.

[0009] In one embodiment of the present disclosure, during the network slice creation phase, the lifecycle management of the slice subnet docking identifier includes: allocating a group of slice subnet docking identifiers to the newly created network slice instance NSI from the available slice subnet docking identifier information, and the group of slice subnet docking identifiers becomes unavailable.

[0010] In one embodiment of the present disclosure, during the network slicing modification phase, the lifecycle management of the slice subnet docking identifier includes: if the slice subnet docking identifier needs to be updated, a group of first slice subnet docking identifiers allocated to the NSI is replaced with a group of second slice subnet docking identifiers, the group of first slice subnet docking identifiers is recycled, the first slice subnet docking identifier becomes available, and the second slice subnet docking identifier becomes unavailable.

[0011] In one embodiment of the present disclosure, during the network slice deletion phase, the lifecycle management of the available slice subnet docking identifiers includes: reclaiming a group of slice subnet docking identifiers allocated to the deleted NSI, and the group of slice subnet docking identifiers becoming available.

[0012] In one embodiment of the present disclosure, during the network slicing termination phase, the lifecycle management of the slice subnet docking identifier includes: if it is determined that the NSI is no longer shared by other network slices, deleting the NSI, reclaiming a set of slice subnet docking identifiers allocated to the NSI, and the set of slice subnet docking identifiers becomes available.

[0013] In one embodiment of the present disclosure, the slice subnet docking identifier includes a virtual local area network identifier VLAN ID, a multi-protocol label switching MPLS label, an Internet Protocol version 6 IPv6 address, or a user datagram protocol UDP port number.

[0014] In one embodiment of the present disclosure, the collection of available slice subnet docking identification information includes: collecting the available slice subnet docking identification information reported by the network slice subnet management function NSSMF, or imported from the resource management system, or manually planned.

[0015] In one embodiment of the present disclosure, the method also includes: sending the docking identifier between the access network slice subnet and the transmission network slice subnet, the docking identifier between the transmission network slice subnet and the core network slice subnet, and the slice configuration request information to the access network slice subnet, the transmission network slice subnet management function, and the core network slice subnet management function, respectively, so that the access network slice subnet management function, the transmission network slice subnet management function, and the core network slice subnet management function respectively configure the docking parameters of the corresponding slice subnet instances.

[0016] According to another aspect of the present disclosure, a communication method is provided, which is applied to a network slicing subnet management function, and the method includes: receiving slice configuration request information and a group of slice subnet docking identifiers issued by the network slicing management function, the group of slice subnet docking identifiers including a docking identifier between an access network slice subnet and a transmission network slice subnet and a docking identifier between the transmission network slice subnet and a core network slice subnet; determining a slice subnet instance according to the slice configuration request information, and respectively configuring the docking parameters of the corresponding slice subnet instance according to the docking identifier between the access network slice subnet and the transmission network slice subnet and the docking identifier between the transmission network slice subnet and the core network slice subnet.

[0017] According to another aspect of the present disclosure, a communication device is provided, which is applied to network slice management functions, including: an identification information receiving module, used to collect available slice subnet docking identification information; a lifecycle management module, used to perform lifecycle management of the slice subnet docking identification, wherein the lifecycle of the slice subnet docking identification information is from the network slice creation stage, the network slice modification stage, the network slice deletion stage to the network slice termination stage.

[0018] According to another aspect of the present disclosure, a communication device is provided, which is applied to a network slicing subnet management function, including: a docking identifier receiving module, which is used to receive slice configuration request information and a group of slice subnet docking identifiers issued by the network slicing management function, and the group of slice subnet docking identifiers include the docking identifier between the access network slice subnet and the transmission network slice subnet and the docking identifier between the transmission network slice subnet and the core network slice subnet; a docking parameter configuration module, which is used to determine the slice subnet instance according to the slice configuration request information, and configure the docking parameters of the corresponding slice subnet instance according to the docking identifier between the access network slice subnet and the transmission network slice subnet and the docking identifier between the transmission network slice subnet and the core network slice subnet.

[0019] According to another aspect of the present disclosure, a communication system is provided, including a network slice management function and a network slice subnet management function; wherein: the network slice management function is used to collect available slice subnet docking identification information; perform life cycle management on the slice subnet docking identification information, wherein the life cycle of the slice subnet docking identification is from the network slice creation stage, the network slice modification stage, the network slice deletion stage to the network slice termination stage; the slice subnet management function is used to receive slice configuration request information and a group of slice subnet docking identifications issued by the network slice management function, the group of slice subnet docking identifications including the docking identification between the access network slice subnet and the transmission network slice subnet and the docking identification between the transmission network slice subnet and the core network slice subnet; determine the slice subnet instance according to the slice configuration request information, and configure the docking parameters of the corresponding slice subnet instance according to the docking identification between the access network slice subnet and the transmission network slice subnet and the docking identification between the transmission network slice subnet and the core network slice subnet.

[0020] According to another aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the above-mentioned communication method by executing the executable instructions.

[0021] According to another aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the above-mentioned communication method is implemented.

[0022] According to another aspect of the present disclosure, a computer program product is provided, including executable instructions, which are stored in a computer-readable storage medium. A processor of an electronic device reads the executable instructions from the computer-readable storage medium, and the processor executes the executable instructions, so that the electronic device executes the above-mentioned communication method.

[0023] In the embodiment of the present disclosure, the network slice management function collects available slice subnet docking identification information; performs lifecycle management on the slice subnet docking identification, and the lifecycle of the slice subnet docking identification information is from the network slice creation stage, the network slice modification stage, the network slice deletion stage to the network slice termination stage. The present disclosure can realize cross-domain slice subnet docking identification lifecycle management and configuration, improve configuration efficiency, reduce slice subnet docking parameter configuration conflicts, have high accuracy, and simplify network operation, maintenance and management requirements.

[0024] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

[0026] Figure 1 A schematic diagram showing an exemplary system architecture of a communication method in an embodiment of the present disclosure.

[0027] Figure 2 A flow chart of a communication method provided in an embodiment of the present disclosure is shown.

[0028] Figure 3 A flow chart of the communication method in the network slice creation phase provided in an embodiment of the present disclosure is shown.

[0029] Figure 4 A flow chart of the communication method in the network slice modification phase provided in an embodiment of the present disclosure is shown.

[0030] Figure 5 A flow chart of the communication method in the network slice deletion phase provided in an embodiment of the present disclosure is shown.

[0031] Figure 6 A flow chart of the communication method in the network slice termination phase provided in an embodiment of the present disclosure is shown.

[0032] Figure 7 A flow chart of another communication method provided in an embodiment of the present disclosure is shown.

[0033] Figure 8 A flow chart of another communication method provided in an embodiment of the present disclosure is shown.

[0034] Fig. 9 A schematic structural diagram of a communication device provided in an embodiment of the present disclosure is shown.

[0035] Fig.10 A schematic diagram of the structure of another communication device provided in an embodiment of the present disclosure is shown.

[0036] Fig.11 A schematic diagram of the structure of a communication system provided in an embodiment of the present disclosure is shown.

[0037] Fig.12 A schematic structural diagram of an electronic device in an embodiment of the present disclosure is shown.

[0038] Fig.13 A schematic diagram showing the structure of a computer program product in an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0039] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that the disclosure will be more comprehensive and complete and to fully convey the concepts of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0040] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0041] For ease of understanding, before introducing the embodiments of the present disclosure, several terms involved in the embodiments of the present disclosure are first explained as follows:

[0042] QoS: Quality of Service.

[0043] 5QI: 5G QoS Indicator, 5G quality indicator.

[0044] SRv6: Segment Routing v6, based on IPv6 segment routing, is a protocol for forwarding data packets on the network based on source routing. It divides the packet forwarding path into different segments, and then assigns segment identifiers (Segment Identifier, SID) to identify them, thereby guiding packet forwarding by segment.

[0045] SR-MPLS: Segment Routing Multi-Protocol Label Switching, also known as SR, cuts the message forwarding path into different segments and assigns SIDs to them. It inserts segment information into the message at the starting point of the path to guide the message to be correctly forwarded to the destination. It is essentially a label forwarding path established by segment routing technology.

[0046] SLA: Service-Level Agreement.

[0047] NSSMF: Network Slice Subnet Management Function, network slice subnet management function.

[0048] AN NSSMF: Access network slice subnet management function.

[0049] CN NSSMF: core network slice subnet management function.

[0050] TN NSSMF: Transport network slice subnet management function.

[0051] CSMF: Communication Service Management Function, communication service management function.

[0052] NSMF: Network Slice Management Function, network slice management function.

[0053] VLAN ID: Virtual Local Area Network Identifier, used to uniquely identify a VLAN.

[0054] The specific implementation of the embodiment of the present disclosure is described in detail below with reference to the accompanying drawings.

[0055] like Figure 1 As shown, the system architecture includes but is not limited to: a radio access network (Radio Access Network, RAN) 110, a transport network (Transport Network, TN) 120 and a core network (Core Network, CN) 130.

[0056] In some embodiments, the wireless access network 110 is a node or device that accesses the terminal to the wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a NodeB (NB), a base station of a later version (for example, a gNB base station), or a base station in other communication systems (for example, an eNB base station). It should be noted that the specific type of the wireless access network 110 is not limited in the embodiments of the present disclosure.

[0057] In some embodiments, the access network device may be composed of a centralized unit (CU) and a distributed unit (DU), where the CU may also be referred to as a control unit. The CU-DU structure may be used to split the protocol layer of the access network device, with some functions of the protocol layer being centrally controlled by the CU, and the remaining part or all of the functions of the protocol layer being distributed in the DU, and the DU being centrally controlled by the CU, but not limited to this.

[0058] The transmission network 120, also known as the bearer network, is a basic network that provides network connections for the wireless access network 110 and the core network 130. The transmission network 120 is divided into three logical planes: the management plane, the control plane, and the forwarding plane. The management plane completes the basic management function of the bearer network controller on the bearer network equipment, the control plane completes the planning and control of the bearer network forwarding path, and the forwarding plane completes the forwarding function of user messages between wireless access networks (such as base stations) and between the wireless access network and the core network.

[0059] The transmission network 120 is used to carry various business data between the wireless access network 110 and the core network 130. It can be the backbone network of the operator or the internal network of the enterprise. It uses optical fiber as the transmission medium to provide stable, reliable and efficient data transmission services for various businesses. The bearer network can be divided into many types, such as voice bearer network, data bearer network, bandwidth bearer network and Internet bearer network.

[0060] The transmission network 120 includes an access layer, an aggregation layer, and a core layer. Overall, the bearer network, in addition to the fronthaul, is mainly composed of a metropolitan area network and a backbone network. The metropolitan area network is further divided into an access layer, an aggregation layer, and a core layer. For example, a 5G bearer network includes an access router, a metropolitan area edge router, a metropolitan area aggregation edge router, a metropolitan area core router, a core router, and the like.

[0061] In some embodiments, the core network 130 may include at least one core network function network element. The core network function network element may include a policy control function (PCF), a session management function (SMF), a user plane function (UPF), a network exposure function (NEF), an access and mobility management function (AMF), etc.

[0062] Among them, PCF mainly manages the service quality QoS of each service data flow in the 5G core network. SMF mainly manages the service quality QoS of each service data flow in the 5G core network, and is responsible for establishing and managing sessions, terminal Internet Protocol (IP) address allocation and management, etc. UPF is responsible for forwarding traffic, reporting traffic usage, determining QoS policy implementation, etc. NEF is responsible for opening the network function entity of the 5G core network function to a third party or non-3rd Generation Partnership Project (3GPP) environment. AMF is responsible for terminal identity authentication, authorization, registration, mobility management and connection management.

[0063] It should be noted that the core network 130 may also include other network functions, which is not limited in the present disclosure.

[0064] In some embodiments, the core network 130 may be a device including one or more network elements, or may be multiple devices or device groups, and the network element may be virtual or physical. The core network 130 may include at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0065] Network slicing is an on-demand networking method that allows operators to separate multiple virtual end-to-end networks on a unified infrastructure. Each network slice is logically isolated from the wireless access network 110 to the transmission network 120 and then to the core network 130, which has been adapted to various types of applications. In a network slice, it can be divided into at least three parts: access network slice subnet, transmission network slice subnet and core network slice subnet.

[0066] like Figure 1 As shown, in the 5G network end-to-end slicing architecture, the communication system also includes management functional components such as CSMF 140, NSMF 150, and network slice subnet management function NSSMF. Among them, NSSMF includes radio access network slice subnet management function AN-NSSMF 160, transmission network slice subnet management function TN-NSSMF 170, and core network slice subnet management function CN-NSSMF 180. A network slice instance is composed of three network slice subnet instances of radio access network 110, transmission network 120 and core network 130, and end-to-end slice management is achieved through network slice management function NSMF 150.

[0067] CSMF 140 is responsible for user-oriented network slice service subscription requests and network slice service management. NSMF 150 interacts with AN-NSSMF 160 through interface (1), interacts with TN-NSSMF 170 through interface (2), and interacts with CN-NSSMF 180 through interface (3).

[0068] Network slice service requests may include but are not limited to network slice creation requests, network slice modification requests, network slice deletion requests, network slice termination requests, etc.

[0069] AN-NSSMF 160 configures the wireless access network slices directly or indirectly through the network management, TN-NSSMF 170 configures the transmission network slices directly or indirectly through the network management, and CN-NSSMF 180 configures the core network slices directly or indirectly through the network management.

[0070] In some embodiments, the base station on the RAN side and the transport network access device are connected between the forwarding planes through a standard connection identifier, for example, an Ethernet VLAN ID, an MPLS label, an IPv6 address or a UDP port number is used as a connection identifier (4) for slice connection, and the QoS parameter mapping between the access network slice and the transport network slice is connected using a 5QI parameter to a DSCP parameter mapping. In some embodiments, the wireless access network 110 identifies the sub-slice instance of the wireless access network 110, for example, by an AN NSSI ID. Before the wireless access network 110 forwards the data to the transport network 120, it configures the data packet according to the mapping relationship between the AN NSSI ID and the connection identifier of the sub-slice. After receiving the data packet, the transport network 120 identifies the slice by the connection identifier and forwards the data packet to the corresponding TN NSSI.

[0071] The core network 130 UPF and the transport network 120 boundary device are connected between the forwarding planes through a standard connection identifier, for example, the Ethernet VLAN ID, MPLS label, IPv6 address or UDP port number is used as the connection identifier (5) for slice connection, and the QoS parameter mapping between the core network slice and the transport network slice is connected by 5QI parameter to DSCP parameter mapping. In some embodiments, the core network 130 identifies the sub-slice instance of the core network 130 through the CN NSSI ID. When forwarding the message to the transport network 120, the message is configured according to the mapping relationship between the CN NSSI ID and the connection identifier of the sub-slice instance. After receiving the message, the transport network 120 uses the connection identifier to identify the slice and forwards the message to the corresponding TN NSSI.

[0072] In the related technology, currently, network operators of various professions negotiate cross-professional slice docking parameters and implement network parameter configuration of docking interfaces manually or with the help of network management configuration. Due to the large number of wireless base stations and distributed deployment of core network UPF, manual configuration is not only cumbersome and inefficient, but also prone to conflicts in docking configuration and errors.

[0073] In the 3GPP management domain of the 5G network, the network slice subnet instance NSSI of the access network and the core network is uniquely identified by a single network slice selection auxiliary information (S-NSSAI). This identification method is invisible to the transmission network of the non-3GPP management domain. It is necessary to establish a mapping between the NSSI (S-NSSAI) and the slice subnet docking identifier so that the protocol data unit (PDU) message from the AN NSSI or CN NSSI belonging to the same network slice instance (NSI) can be correctly forwarded to the TN NSSI. Therefore, a unified slice management system is required to establish and maintain the docking identifier between the AN NSSI and the TN NSSI, and the docking identifier between the TN NSSI and the CN NSSI, and to perform lifecycle management on the docking identifier between slice subnets.

[0074] Under the above system architecture, in order to at least partially solve the above technical problems, a communication method is provided in an embodiment of the present disclosure, and the network slice management function collects available slice subnet docking identification information; the slice subnet docking identification is managed for life cycle, and the life cycle of the slice subnet docking identification is from the network slice creation stage, the network slice modification stage, the network slice deletion stage to the network slice termination stage. The present disclosure can realize cross-domain slice subnet docking identification life cycle management and configuration, improve configuration efficiency, reduce slice subnet docking parameter configuration conflicts, have high accuracy, and simplify the operation, maintenance and management requirements for the network.

[0075] The method can be executed by any electronic device with computing and processing capabilities. In some embodiments, the communication method provided in the embodiments of the present disclosure can be executed by the network slice management function NSMF of the above system architecture; in other embodiments, the communication method provided in the embodiments of the present disclosure can also be executed by the network slice subnet management function NSSMF of the above system architecture; in other embodiments, the communication method provided in the embodiments of the present disclosure can also be executed by the interaction between the NSMF and NSSMF of the above system architecture.

[0076] Figure 2 A flow chart of a communication method in an embodiment of the present disclosure is shown. Figure 2 As shown, the communication method provided in the embodiment of the present disclosure is applied to the network slice management function NSMF, and the method mainly includes the following steps:

[0077] S202. Collect available slice subnet connection identification information.

[0078] In one embodiment, the available slice subnet docking identification information includes at least one group of slice subnet docking identifications, a group of slice subnet docking identifications including the docking identification between the access network slice subnet and the transmission network slice subnet, and the docking identification between the transmission network slice subnet and the core network slice subnet.

[0079] The above-mentioned available slice subnet docking identification information refers to the slice subnet docking identification that is in an available state in the network. The docking identification between the access network slice subnet and the transmission network slice subnet, and the docking identification between the transmission network slice subnet and the core network slice subnet correspond one to one. The slice subnet docking identification in each group can be the same or different, depending on the actual situation.

[0080] An available slice subnet docking identifier refers to a docking identifier that is not assigned to a network slice instance (NSI). When a slice subnet docking identifier is assigned to an NSI, the usage status of the assigned slice subnet docking identifier is modified to used or unavailable. The usage status of the slice subnet docking identifier is determined according to the actual usage status.

[0081] In one embodiment, in S202, the available slice subnet docking identification information reported by the network slice subnet management function NSSMF, imported from the resource management system, or manually planned is collected. NSSMF includes an access network slice subnet management function, a transmission network slice subnet management function, and a core network slice subnet management function.

[0082] Exemplarily, the available slice subnet docking identification information can be fed back to NSMF in real time through AN NSSMF, TN NSSMF, and CN NSSMF to show the actual usage of the slice subnet docking identification corresponding to NSI, so that NSMF can adjust the usage status of the slice subnet docking identification according to the actual usage of the slice subnet docking identification. In addition, the available slice subnet docking identification information can also be manually planned.

[0083] It should be noted that the slice subnet docking identifier includes the virtual local area network identifier (Virtual Local Area Network Identifier, VLAN ID), the Multi-Protocol Label Switching (Multi-Protocol Label Switching, MPLS) label, the Internet Protocol version 6 IPv6 address or the User Datagram Protocol (User Datagram Protocol, UDP) port number.

[0084] For example, the slice subnet connection identifier can be the VLAN identifier of a subport of the interconnection port, and each interconnection port can be configured with multiple VLAN subinterfaces corresponding to different slice subnet connection identifiers. Thus, when encapsulating data packets, the VLAN ID is used as the slice subnet connection identifier.

[0085] The slice subnet connection identifier can also be an MPLS label. MPLS uses the label Lable for data forwarding. When a packet enters the network, a short label of a fixed length is assigned to the message data, and the label is encapsulated with the packet. During the entire forwarding process, the switching node forwards according to the MPLS label.

[0086] The length of an IPv6 address is 128 bits. An IPv6 address consists of 8 address segments, each of which is 16 bits. The IPv6 address can be used as a docking identifier for cross-domain slice subnets.

[0087] UDP port numbers can be used to identify applications. The port number range is from 0 to 65535, and 0 to 255 are reserved. The UDP port number can be used to define the source port number and the destination port number, which can be used as the docking identifier of the cross-domain slice subnet.

[0088] S204. Perform lifecycle management on the slice subnet docking identifier, where the lifecycle of the slice subnet docking identifier is from the network slice creation stage, the network slice modification stage, the network slice deletion stage to the network slice termination stage.

[0089] The life cycle of the slice subnet docking identifier is determined according to the life cycle of the network slice. The life cycle management of the slice subnet docking identifier refers to the management of the slice subnet docking identifier in the slice subnet docking identifier information, including the management process and method of the slice subnet docking identifier in the network slice creation stage, modification stage, deletion stage, and termination stage.

[0090] In one embodiment, the stage of the network slice's life cycle can be determined based on the slice configuration request information sent by the CSMF, and the slice configuration request information includes information such as a slice creation request, a slice modification request, a slice deletion request, or a slice termination request.

[0091] When NSMF receives the slice configuration request information, it performs lifecycle management on the slice subnet docking identifier according to the corresponding slice configuration request.

[0092] In some cases, the life cycle of a slice subnet docking identifier may only include the network slice creation phase and the termination phase; or, it may also include the network slice modification phase and / or the network slice deletion phase, or other phases in which the network slice is located. This disclosure does not make specific limitations on this.

[0093] In the embodiment of the present disclosure, the network slice management function collects available slice subnet docking identification information; performs lifecycle management on the slice subnet docking identification information. The lifecycle of the slice subnet docking identification ranges from the network slice creation stage, the network slice modification stage, the network slice deletion stage to the network slice termination stage. The present disclosure can realize cross-domain slice subnet docking identification lifecycle management and configuration, improve configuration efficiency, reduce slice subnet docking parameter configuration conflicts, have high accuracy, and simplify network operation, maintenance and management requirements.

[0094] Figure 3 The flow chart of the communication method in the network slice creation phase provided by the embodiment of the present disclosure is shown. Figure 3 As shown, in one embodiment, in the network slice creation stage, the above S204 performs lifecycle management on the slice subnet connection identifier, including:

[0095] S2042. Assign a set of slice subnet docking identifiers to the newly created network slice instance NSI from the available slice subnet docking identifier information, and this set of slice subnet docking identifiers becomes unavailable.

[0096] In one embodiment, when NSMF receives a slice creation request, it can randomly select a group of available slice subnet docking identifiers from the available slice subnet docking identifier information, or determine a group of slice subnet docking identifiers from the available slice subnet docking identifier information according to certain rules. NSMF sends a slice creation request and the group of slice subnet docking identifiers to the network slice subnet management function NSSMF, so that the network slice subnet management function creates a network slice instance NSI according to the slice creation request and the group of slice subnet docking identifiers.

[0097] The following is an example of a network slice docking identifier as a VLAN ID. In the network slice creation stage, NSMF allocates a set of new slice subnet docking identifiers for a newly created NSI from the available slice subnet docking identifier information, for example, the docking identifier between the access network slice subnet and the transmission network slice subnet is VLAN 100, and the docking identifier between the transmission network slice subnet and the core network slice subnet is VLAN 200. Table 1 shows an example of a slice subnet docking identifier in the network slice creation stage of the present disclosure.

[0098] Table 1 Example of slice subnet connection identification in the network slice creation phase

[0099] AN-NSSI ID First docking mark TN-NSSI ID Second docking mark CN-NSSI ID 1 VLAN 100 2 VLAN 200 1

[0100] As shown in Table 1, AN-NSSI ID is the access network slice subnet instance identifier, TN-NSSI ID is the transmission network slice subnet instance identifier, CN-NSSI ID is the core network slice subnet instance identifier, the first docking identifier is the docking identifier between the access network slice subnet and the transmission network slice subnet, and the second docking identifier is the docking identifier between the transmission network slice subnet and the core network slice subnet.

[0101] It should be noted that after a group of slice subnet docking identifiers are allocated to the corresponding NSI, the usage status of this group of slice subnet docking identifiers becomes unavailable.

[0102] In an embodiment of the present disclosure, NSMF allocates a set of available slice subnet docking identifiers to the newly created NSI based on the acquired slice creation request, thereby enabling NSSMF to automatically configure end-to-end network slices based on the slice creation request and the set of slice subnet docking identifiers, thereby improving configuration efficiency and accuracy.

[0103] Figure 4 The flow chart of the communication method in the network slice modification phase provided in the embodiment of the present disclosure is shown. Figure 4 As shown, in one embodiment, in the network slice modification stage, the above S204 performs lifecycle management on the available slice subnet docking identification information, including:

[0104] S2044. If the slice subnet docking identifier needs to be updated, a group of first slice subnet docking identifiers allocated to the NSI will be replaced with a group of second slice subnet docking identifiers, and a group of first slice subnet docking identifiers will be recovered. The first slice subnet docking identifier becomes available, and the second slice subnet docking identifier becomes unavailable.

[0105] It should be noted that the first slice subnet docking identifier refers to the slice subnet docking identifier currently used by the NSI. It can be a set of available slice subnet docking identifiers allocated to the newly created NSI, or it can be the slice subnet docking identifier used by the NSI after the last update. This disclosure does not make specific limitations on this.

[0106] The second slice subnet docking identifier is a group of slice subnet docking identifiers randomly selected from the available slice subnet docking identifier information; it can also be a group of slice subnet docking identifiers determined from the available slice subnet docking identifier information in a certain order, such as in order of priority, or in order of the docking identifier serial number.

[0107] It should be noted that the screening method of a set of first slice subnet docking identifiers and second slice subnet docking identifiers determined from the available slice subnet docking identifier information in the network slice creation stage and the network slice modification stage can be determined according to actual needs, and the present disclosure does not make specific limitations on this.

[0108] Based on the example of the slice subnet docking identifier in the network slice creation phase, when the NSMF obtains a slice update request, it selects a set of second slice subnet docking identifiers from the available slice subnet docking identifiers, and sends the slice update request and the second slice subnet docking identifier to the NSSMF, so that the NSSMF configures the docking parameters of the NSI according to the slice update request and the second slice subnet docking identifier. Table 2 shows an example of a slice subnet docking identifier in the network slice update phase.

[0109] Table 2 Example of slice subnet connection identification in the network slice update phase

[0110] AN-NSSI ID First docking mark TN-NSSI ID Second docking mark CN-NSSI ID 1 VLAN 50 2 VLAN 50 1

[0111] It can be seen from Tables 1 and 2 that in the network slicing modification phase, NSMF replaces the existing slice subnet docking identifiers (VLAN 100 and VLAN 200) with a set of new slice subnet docking identifiers (VLAN 50 and VLAN 50).

[0112] It should be noted that in the network slicing update phase, after the first slice subnet docking identifier is recovered, the usage status of the first slice subnet docking identifier is modified to available, and the usage status of the second slice subnet docking identifier is modified to unavailable.

[0113] In an embodiment of the present disclosure, NSMF reallocates a group of second slice subnet docking identifiers for the NSI to which the first slice subnet docking identifier has been allocated based on the acquired slice update request, thereby enabling NSSMF to automatically configure end-to-end network slices based on the slice update request and the group of second slice subnet docking identifiers, thereby improving configuration efficiency and accuracy.

[0114] Figure 5 The flow chart of the communication method in the network slice deletion phase provided in the embodiment of the present disclosure is shown. Figure 5 As shown, in one embodiment, in the network slice deletion phase, the above S204 performs lifecycle management on the slice subnet connection identifier, including:

[0115] S2046. Reclaim a set of slice subnet docking identifiers allocated to the deleted NSI, and the set of slice subnet docking identifiers becomes available.

[0116] It should be noted that the above-mentioned recovery of a set of slice subnet docking identifiers allocated to the deleted NSI refers to changing the usage status of this group of slice subnets from unavailable to available, so that a set of slice subnet docking identifiers can be added to the available slice subnet docking identifier information to serve other NSIs and improve the effectiveness and reliability of end-to-end network slicing.

[0117] Figure 6The flowchart of the communication method in the network slice termination phase provided in the embodiment of the present disclosure is shown. Figure 6 As shown, in one embodiment, in the network slicing termination stage, the above S204 performs lifecycle management on the slice subnet connection identifier, including:

[0118] S2048. If it is determined that the NSI is no longer shared by other network slices, the NSI is deleted, and a set of slice subnet docking identifiers allocated to the NSI is recovered, and the set of slice subnet docking identifiers becomes available.

[0119] When NSMF receives the slice termination request sent by CSMF, the slice termination request includes the NSI identifier to be terminated, and the NSI identifier to be terminated may include AN-NSSI ID, TN-NSSI ID and CN-NSSI ID. NSMF sends the slice termination request and the group of slice subnet docking identifiers to NSSMF so that NSSMF deletes the NSI and the corresponding slice subnet docking identifier. NSMF confirms that the NSI has been deleted and changes the usage status of a group of slice subnet docking identifiers corresponding to the NSI to available.

[0120] Figure 7 Another communication method flow chart provided in the embodiment of the present disclosure is shown. Figure 2 Based on the embodiment, S206 is added after S204 to configure and limit the connection parameters for the slice subnet instance. Figure 7 As shown, in one embodiment, the communication method provided by the embodiment of the present disclosure includes S202 to S206, wherein the method further includes:

[0121] S206. The docking identifier between the access network slice subnet and the transmission network slice subnet, the docking identifier between the transmission network slice subnet and the core network slice subnet, and the slice configuration request information are respectively sent to the access network slice subnet management function, the transmission network slice subnet management function, and the core network slice subnet management function, so that the access network slice subnet management function, the transmission network slice subnet management function, and the core network slice subnet management function can respectively configure the docking parameters of the corresponding slice subnet instances.

[0122] In one embodiment, NSMF can send the docking identifier between the access network slice subnet and the transport network slice subnet to the access network slice subnet management function AN-NSSMF, and AN-NSSMF can implement the docking parameter configuration of the access network slice subnet according to the above docking identifier. Table 3 shows an example of the docking identifier sent by NSMF to AN-NSSMF.

[0123] Table 3 Example of the connection identifier sent from NSMF to AN-NSSMF

[0124] AN-NSSI ID First docking mark TN-NSSI ID 1 VLAN 100 2

[0125] In one embodiment, NSMF can send the docking identifier between the access network slice subnet and the transport network slice subnet, and the docking identifier between the transport network slice subnet and the core network slice subnet to the transport network slice subnet management function TN-NSSMF, and TN-NSSMF can configure the docking parameters of the access network slice subnet according to the above docking identifier. Table 4 shows an example of the docking identifier sent by NSMF to TN-NSSMF.

[0126] Table 4 Example of the connection identifier sent from NSMF to TN-NSSMF

[0127] AN-NSSI ID First docking mark TN-NSSI ID Second docking mark CN-NSSI ID 1 VLAN 100 2 VLAN 200 1

[0128] In one embodiment, NSMF can send the connection identifier between the transport network slice subnet and the core network slice subnet to the core network slice subnet management function CN-NSSMF, and CN-NSSMF can implement the connection parameter configuration of the core network slice subnet according to the above connection identifier. Table 5 shows an example of the connection identifier sent by NSMF to CN-NSSMF.

[0129] Table 5 Example of the connection identifier sent from NSMF to CN-NSSMF

[0130] TN-NSSI ID Second docking mark CN-NSSI ID 2 VLAN 200 1

[0131] It should be noted that in addition to using VLAN ID as the slice subnet docking identifier in the above example, MPLS label, IPv6 address or UDP port number can also be used as the slice subnet docking identifier, which will not be repeated here.

[0132] Figure 8 FIG. 2 shows another flow chart of a communication method provided by an embodiment of the present disclosure. Figure 8 As shown, in one embodiment, a communication method provided by an embodiment of the present disclosure is applied to a network slice subnet management function, and the method includes:

[0133] S802. Receive slice configuration request information and a set of slice subnet connection identifiers issued by the network slice management function, where the set of slice subnet connection identifiers includes a connection identifier between an access network slice subnet and a transport network slice subnet and a connection identifier between a transport network slice subnet and a core network slice subnet;

[0134] S804. Determine the slice subnet instance according to the slice configuration request information, and configure the docking parameters of the corresponding slice subnet instance according to the docking identifier between the access network slice subnet and the transmission network slice subnet and the docking identifier between the transmission network slice subnet and the core network slice subnet.

[0135] In one embodiment, when NSSMF receives the slice configuration request information and slice subnet docking identifier issued by NSMF, it can create a slice subnet instance, delete a slice subnet instance, and other operations according to the slice configuration request information, and configure the docking parameters of the slice subnet instance according to the slice subnet docking identifier.

[0136] Based on the same inventive concept, the present disclosure also provides a communication device, as described in the following embodiments. Since the principle of solving the problem in the device embodiment is similar to that in the above method embodiment, the implementation of the device embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0137] Fig. 9 FIG. 2 is a schematic diagram showing the structure of a communication device in an embodiment of the present disclosure. Fig. 9 As shown, the communication device provided in the embodiment of the present disclosure is applied to the network slice management function, and the device includes an identification information receiving module 910 and a life cycle management module 920. Among them:

[0138] An identification information receiving module 910 is used to collect available slice subnet connection identification information;

[0139] The lifecycle management module 920 is used to perform lifecycle management on the slice subnet docking identifier, wherein the lifecycle of the slice subnet docking identifier ranges from the network slice creation stage, the network slice modification stage, the network slice deletion stage to the network slice termination stage.

[0140] It should be noted that the identification information receiving module 910 and the lifecycle management module 920 correspond to S202 to S204 in the method embodiment, and the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above method embodiment. It should be noted that the above modules, as part of the device, can be executed in a computer system such as a set of computer executable instructions.

[0141] It should be noted that the available slice subnet docking identification information includes the docking identification between the access network slice subnet and the transmission network slice subnet, and the docking identification between the transmission network slice subnet and the core network slice subnet.

[0142] In one embodiment, the lifecycle management module 920 is used to allocate a set of slice subnet docking identifiers to the newly created network slice instance NSI from the available slice subnet docking identifier information during the network slice creation phase, and the set of slice subnet docking identifiers becomes unavailable.

[0143] In one embodiment, the lifecycle management module 920 is used to replace a group of first slice subnet docking identifiers allocated to the NSI with a group of second slice subnet docking identifiers if it is necessary to update the slice subnet docking identifier during the network slice modification phase, and to recycle a group of first slice subnet docking identifiers. The group of first slice subnet docking identifiers becomes available, and the group of second slice subnet docking identifiers becomes unavailable.

[0144] In one embodiment, the lifecycle management module 920 is used to reclaim a set of slice subnet docking identifiers allocated to the deleted NSI during the network slice deletion phase, and the set of slice subnet docking identifiers becomes available.

[0145] In one embodiment, the lifecycle management module 920 is used to delete the NSI and reclaim a set of slice subnet docking identifiers allocated to the NSI during the network slicing termination phase if it is determined that the NSI is no longer shared by other network slices, and the set of slice subnet docking identifiers becomes available.

[0146] It should be noted that the slice subnet docking identifier includes the virtual local area network identifier VLAN ID, the multi-protocol label switching MPLS label, the Internet Protocol version 6 IPv6 address or the user datagram protocol UDP port number.

[0147] In one embodiment, the identification information receiving module 910 is used to collect available slice subnet docking identifiers reported by the network slice subnet management function NSSMF, or imported from the resource management system, or manually planned. NSSMF includes access network slice subnet management function, transmission network slice subnet management function and core network slice subnet management function.

[0148] In one embodiment, the device also includes a docking identifier sending module not shown in the accompanying drawings, and the docking identifier sending module is used to send the docking identifier between the access network slice subnet and the transmission network slice subnet, the docking identifier between the transmission network slice subnet and the core network slice subnet, and the slice configuration request information to the access network slice subnet management function, the transmission network slice subnet management function, and the core network slice subnet management function, respectively, so that the access network slice subnet management function, the transmission network slice subnet management function, and the core network slice subnet management function can respectively configure the docking parameters of the corresponding slice subnet instances.

[0149] In the embodiment of the present disclosure, the network slice management function collects available slice subnet docking identification information; performs life cycle management on the slice subnet docking identification. The life cycle of the slice subnet docking identification ranges from the network slice creation stage, the network slice modification stage, the network slice deletion stage to the network slice termination stage. The present disclosure can realize cross-domain slice subnet docking identification life cycle management and configuration, improve configuration efficiency, reduce slice subnet docking parameter configuration conflicts, have high accuracy, and simplify network operation, maintenance and management requirements.

[0150] Fig.10 FIG. 2 is a schematic diagram showing the structure of another communication device in an embodiment of the present disclosure. Fig.10 As shown, the communication device provided in the embodiment of the present disclosure is applied to the network slice subnet management function, including a docking identification receiving module 1010 and a docking parameter configuration module 1020, wherein:

[0151] The docking identifier receiving module 1010 is used to receive the slice configuration request information and a group of slice subnet docking identifiers issued by the network slice management function, where the group of slice subnet docking identifiers includes the docking identifier between the access network slice subnet and the transmission network slice subnet and the docking identifier between the transmission network slice subnet and the core network slice subnet;

[0152] The docking parameter configuration module 1020 is used to determine the slice subnet instance according to the slice configuration request information, and configure the docking parameters of the corresponding slice subnet instance according to the docking identifier between the access network slice subnet and the transmission network slice subnet and the docking identifier between the transmission network slice subnet and the core network slice subnet.

[0153] refer to Fig.11 The communication system provided by the embodiment of the present disclosure includes a network slice management function 150 and a network slice subnet management function 1110; wherein: the network slice management function 150 is used to collect available slice subnet docking identification information; the slice subnet docking identification is managed for life cycle, wherein the life cycle of the slice subnet docking identification is from the network slice creation stage, the network slice modification stage, the network slice deletion stage to the network slice termination stage; the network slice subnet management function 1110 is used to receive the slice configuration request information and a group of slice subnet docking identifications issued by the network slice management function 150, wherein the group of slice subnet docking identifications includes the docking identification between the access network slice subnet and the transmission network slice subnet and the docking identification between the transmission network slice subnet and the core network slice subnet; the slice subnet instance is determined according to the slice configuration request information, and the docking parameters of the corresponding slice subnet instance are configured according to the docking identification between the access network slice subnet and the transmission network slice subnet and the docking identification between the transmission network slice subnet and the core network slice subnet.

[0154] It will be appreciated by those skilled in the art that various aspects of the present invention may be implemented as a system, method or program product. Therefore, various aspects of the present invention may be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to herein as a "circuit", "module" or "system".

[0155] Refer to the following Fig.12 The electronic device 1200 according to this embodiment of the present invention is described. Fig.12 The electronic device 1200 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0156] like Fig.12 As shown, the electronic device 1200 is in the form of a general computing device. The components of the electronic device 1200 may include but are not limited to: at least one processing unit 1210, at least one storage unit 1220, and a bus 1230 connecting different system components (including the storage unit 1220 and the processing unit 1210).

[0157] The storage unit stores program codes, which can be executed by the processing unit 1210, so that the processing unit 1210 executes the steps according to various exemplary embodiments of the present invention described in the above “Exemplary Method” section of this specification. For example, the processing unit 1210 can execute the following steps: Figure 2 The network slice management function shown in the figure obtains the available slice subnet docking identification information; performs life cycle management on the slice subnet docking identification, wherein the life cycle of the slice subnet docking identification is from the network slice creation stage, the network slice modification stage, the network slice deletion stage to the network slice termination stage.

[0158] The processing unit 1210 may also perform the following steps: Figure 8 The network slice subnet management function shown in receives the slice configuration request information and a set of slice subnet docking identifiers issued by the network slice management function, the set of slice subnet docking identifiers including the docking identifier between the access network slice subnet and the transmission network slice subnet and the docking identifier between the transmission network slice subnet and the core network slice subnet; determines the slice subnet instance according to the slice configuration request information, and configures the docking parameters of the corresponding slice subnet instance according to the docking identifier between the access network slice subnet and the transmission network slice subnet and the docking identifier between the transmission network slice subnet and the core network slice subnet.

[0159] The storage unit 1220 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 12201 and / or a cache storage unit 12202 , and may further include a read-only storage unit (ROM) 12203 .

[0160] The storage unit 1220 may also include a program / utility 12204 having a set (at least one) of program modules 12205, such program modules 12205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0161] Bus 1230 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0162] The electronic device 1200 may also communicate with one or more external devices 1240 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), one or more devices that enable a user to interact with the system, and / or any device that enables the electronic device 1200 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 1250. Furthermore, the system may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 1260. Fig.12 As shown, the network adapter 1260 communicates with other modules of the electronic device 1200 via the bus 1230. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device 1200, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0163] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0164] In an exemplary embodiment of the present disclosure, a computer-readable storage medium is further provided, on which a program product capable of implementing the above method of the present specification is stored. Fig.13 FIG. 1 is a schematic diagram of a computer-readable storage medium 1300 provided by an embodiment of the present disclosure. Fig.13 As shown, a program product capable of implementing the above method of the present disclosure is stored on the computer-readable storage medium 1300. In some possible implementations, various aspects of the present disclosure may also be implemented in the form of a program product, which includes a program code. When the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps according to various exemplary implementations of the present invention described in the above "Exemplary Method" section of this specification.

[0165] A program product for implementing the above method according to an embodiment of the present invention is described, which can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto, and in this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus or a device.

[0166] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0167] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0168] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0169] Program code for performing the operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., through the Internet using an Internet service provider).

[0170] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0171] In addition, although the steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0172] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0173] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any modification, use or adaptation of the present disclosure, which follows the general principles of the present disclosure and includes common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the appended claims.

Claims

1. A communication method, characterized in that: Applied to the network slice management function, the method includes: Collect available slice subnet connection identification information; The slice subnet docking identifier is managed for its life cycle, wherein the life cycle of the slice subnet docking identifier ranges from the network slice creation stage, the network slice modification stage, the network slice deletion stage to the network slice termination stage.

2. The method according to claim 1, characterized in that The available slice subnet docking identification information includes the docking identification between the access network slice subnet and the transmission network slice subnet, and the docking identification between the transmission network slice subnet and the core network slice subnet.

3. The method according to claim 2, characterized in that In the network slice creation phase, the lifecycle management of the slice subnet connection identifier includes: From the available slice subnet docking identification information, a set of slice subnet docking identifications is allocated to the newly created network slice instance NSI, and the set of slice subnet docking identifications becomes unavailable.

4. The method according to claim 2, characterized in that: In the network slice modification stage, the lifecycle management of the slice subnet connection identifier includes: If the slice subnet docking identifier needs to be updated, a group of first slice subnet docking identifiers assigned to the NSI will be replaced with a group of second slice subnet docking identifiers, and the group of first slice subnet docking identifiers will be recovered. The group of first slice subnet docking identifiers will become available, and the group of second slice subnet docking identifiers will become unavailable.

5. The method according to claim 2, characterized in that: In the network slice deletion phase, the lifecycle management of the slice subnet connection identifier includes: A set of slice subnet docking identifiers allocated to the deleted NSI is recovered, and the set of slice subnet docking identifiers becomes available.

6. The method according to claim 2, characterized in that In the network slicing termination phase, the lifecycle management of the slice subnet connection identifier includes: If it is determined that the NSI is no longer shared by other network slices, the NSI is deleted, and a set of slice subnet docking identifiers allocated to the NSI is recovered, and the set of slice subnet docking identifiers becomes available.

7. The method according to claim 2, characterized in that The slice subnet docking identifier includes a virtual local area network identifier VLAN ID, a multi-protocol label switching MPLS label, an Internet Protocol version 6 IPv6 address or a user datagram protocol UDP port number.

8. The method according to any one of claims 1 to 7, characterized in that: The collecting of available slice subnet connection identification information includes: Collect the available slice subnet docking identification information reported by the network slice subnet management function NSSMF, imported from the resource management system, or manually planned.

9. The method according to claim 8, characterized in that The method further comprises: The docking identifier between the access network slice subnet and the transmission network slice subnet, the docking identifier between the transmission network slice subnet and the core network slice subnet, and the slice configuration request information are respectively sent to the access network slice subnet management function, the transmission network slice subnet management function, and the core network slice subnet management function, so that the access network slice subnet management function, the transmission network slice subnet management function, and the core network slice subnet management function can respectively configure the docking parameters of the corresponding slice subnet instances.

10. A communication method, characterized in that: Applied to the network slicing subnet management function, the method includes: Receive slice configuration request information and a set of slice subnet docking identifiers issued by the network slice management function, wherein the set of slice subnet docking identifiers includes a docking identifier between an access network slice subnet and a transmission network slice subnet and a docking identifier between the transmission network slice subnet and a core network slice subnet; Determine the slice subnet instance according to the slice configuration request information, and configure the docking parameters of the corresponding slice subnet instance according to the docking identifier between the access network slice subnet and the transmission network slice subnet and the docking identifier between the transmission network slice subnet and the core network slice subnet.

11. A communication device, characterized in that: Applied to network slice management functions, including: An identification information receiving module, used to collect available slice subnet connection identification information; The lifecycle management module is used to perform lifecycle management on the slice subnet docking identification, wherein the lifecycle of the slice subnet docking identification information is from the network slice creation stage, the network slice modification stage, the network slice deletion stage to the network slice termination stage.

12. A communication device, characterized in that: Applied to network slicing subnet management functions, including: A docking identifier receiving module, used to receive slice configuration request information and a group of slice subnet docking identifiers issued by the network slice management function, wherein the group of slice subnet docking identifiers includes a docking identifier between the access network slice subnet and the transmission network slice subnet and a docking identifier between the transmission network slice subnet and the core network slice subnet; The docking parameter configuration module is used to determine the slice subnet instance according to the slice configuration request information, and configure the docking parameters of the corresponding slice subnet instance according to the docking identifier between the access network slice subnet and the transmission network slice subnet and the docking identifier between the transmission network slice subnet and the core network slice subnet.

13. A communication system, characterized in that: It includes network slice management function and network slice subnet management function; among which: The network slice management function is used to collect available slice subnet docking identification information; perform life cycle management on the slice subnet docking identification, wherein the life cycle of the slice subnet docking identification information is from the network slice creation stage, the network slice modification stage, the network slice deletion stage to the network slice termination stage; The slice subnet management function is used to receive slice configuration request information and a group of slice subnet docking identifiers issued by the network slice management function, wherein the group of slice subnet docking identifiers include the docking identifier between the access network slice subnet and the transmission network slice subnet and the docking identifier between the transmission network slice subnet and the core network slice subnet; determine the slice subnet instance according to the slice configuration request information, and configure the docking parameters of the corresponding slice subnet instance according to the docking identifier between the access network slice subnet and the transmission network slice subnet and the docking identifier between the transmission network slice subnet and the core network slice subnet.

14. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to execute the communication method according to any one of claims 1 to 9, or the communication method according to claim 10, by executing the executable instructions.

15. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, it implements the communication method according to any one of claims 1 to 9, or implements the communication method according to claim 10.

Images