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 receives a network slice service subscription request sent by a communication service management function, wherein the network slice service subscription request carries a network slice SLA; if the network slice SLA contains the 5QI parameter, establishing and maintaining a mapping relation of QoS parameters of the cross-domain slice subnet according to the 5QI parameter; and if the network slice SLA does not contain the 5QI parameter, exporting the 5QI parameter according to the network slice SLA, and establishing and maintaining the mapping relation of the QoS parameter of the cross-domain slice subnet according to the exported 5QI parameter. The end-to-end QoS configuration efficiency can be improved, and the configuration accuracy is greatly improved.

Description

Background Art

[0002] Network slicing is an important means to provide top-level guarantees for subscriptions to multi-service services such as 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.

[0003] In the related art, the network operators of each slice subnet negotiate the cross-professional slice docking parameters. However, the manual configuration method is cumbersome, inefficient, and prone to conflicts in docking configurations, with a high error rate.

[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 devices, 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 parameters.

[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, the method comprising: receiving a network slice service subscription request from a communication service management function, wherein the network slice service subscription request carries a network slice service level agreement SLA;

[0008] If the network slice SLA includes a 5G quality identification 5QI parameter, a mapping relationship between cross-domain slice subnet quality of service QoS parameters is established and maintained according to the 5QI parameter;

[0009] If the network slice SLA does not include 5QI parameters, the 5QI parameters are derived according to the network slice SLA, and the mapping relationship between cross-domain slice subnet QoS parameters is established and maintained based on the derived 5QI parameters.

[0010] In one embodiment of the present disclosure, establishing and maintaining a mapping relationship of cross-domain slice subnet QoS parameters according to the 5QI parameters includes at least one of the following:

[0011] The mapping relationship between the QoS parameters of the access network slice subnet instance and the transport network slice subnet instance;

[0012] The mapping relationship between QoS parameters of transport network slice subnet instance message encapsulation layers;

[0013] The mapping relationship between the QoS parameters of the transport network slice subnet instance and the core network slice subnet instance.

[0014] In one embodiment of the present disclosure, the mapping relationship between the access network slice subnet instance and the transport network slice subnet instance QoS parameters includes:

[0015] Mapping of access network 5QI parameters to the differential services code point DSCP value and 802.1P value of the transport network;

[0016] The mapping relationship between the QoS parameters of the transmission network slice subnet instance and the core network slice subnet instance includes:

[0017] Mapping of core network 5QI parameters to transport network DSCP values ​​and 802.1P values.

[0018] In one embodiment of the present disclosure, the mapping relationship between QoS parameters of the transport network slice subnet instance message encapsulation layer includes at least one of the following:

[0019] In the trust mode, when the data plane of the transmission network adopts the IPv4 protocol or the IPv6 protocol, the transmission network slice subnet instance receives the first message entering from the access network slice subnet instance or the core network slice subnet instance, does not modify the DSCP value in the IP header of the first message, and performs message priority scheduling according to the DSCP value in the IP header;

[0020] In the trust mode, when the transport network data plane adopts the segment routing-multi-protocol label switching SR-MPLS protocol, the transport network slice subnet instance receives the second message entering from the access network slice subnet instance or the core network slice subnet instance, does not modify the DSCP value of the IP header of the second message, configures the mapping of the DSCP value of the IP header of the second message to the traffic category TC field of the SR-MPLS encapsulation, and performs message priority scheduling according to the value of the TC field of the SR-MPLS encapsulation;

[0021] In the trust mode, when the transport network data plane adopts the SRv6 protocol, the transport network slice subnet instance receives the third message entering from the access network slice subnet instance or the core network slice subnet instance, does not modify the DSCP value of the IP header of the third message, configures a copy mapping of the DSCP value of the IP header of the third message to the TC field of the SRv6 encapsulation, and performs message priority scheduling according to the value of the TC field of the SRv6 encapsulation;

[0022] In non-trusted mode, when the transport network data plane adopts the IPv4 protocol or the IPv6 protocol, the transport network slice subnet instance modifies the DSCP value of the IP header of the message entering the transport network slice subnet instance from the access network slice subnet instance or the core network slice subnet instance according to the operator policy, performs message priority scheduling according to the modified DSCP value, and restores the IP header of the message going to the access network slice subnet instance or the core network slice subnet instance to the DSCP value before modification;

[0023] In untrusted mode, when the transport network data plane adopts the SR-MPLS protocol, the transport network slice subnet instance maintains the DSCP value of the IP header of the message entering the transport network slice subnet instance from the access network slice subnet instance or the core network slice subnet instance unchanged, sets the corresponding QoS value for the TC field of the SR-MPLS encapsulation according to the operator policy, and performs message priority scheduling according to the QoS value of the TC field of the SR-MPLS encapsulation;

[0024] In non-trusted mode, when the transport network data plane adopts the SRv6 protocol, the transport network slice subnet instance keeps the DSCP value of the IP header of the message entering the transport network slice subnet instance unchanged, sets the corresponding QoS value for the TC field of the SRv6 encapsulation according to the operator policy, and performs message priority scheduling according to the QoS value of the TC field of the SRv6 encapsulation.

[0025] In one embodiment of the present disclosure, the method further includes:

[0026] In non-trusted mode, when the transport network data plane adopts the IPv4 protocol or the IPv6 protocol, the transport network slice subnet instance modifies the DSCP value of the IP header of the message entering the transport network slice subnet instance according to the operator policy, and the modification of the DSCP value is applied to the ingress device of the transport network slice subnet instance; at the same time, the IP header of the message going to the access network slice subnet instance or the core network slice subnet instance is restored to the DSCP value before modification, and the modification of the DSCP value is applied to the egress device of the transport network slice subnet instance.

[0027] In one embodiment of the present disclosure, the method further includes:

[0028] Configure and manage the traffic rate limit parameters for messages from the access network slice subnet instance or the core network slice subnet instance entering the transmission network slice subnet instance.

[0029] In one embodiment of the present disclosure, the configuration management of the traffic rate limit parameters of the message from the access network slice subnet instance or the core network slice subnet instance entering the transmission network slice subnet instance includes:

[0030] Configure the traffic from the access network slice subnet instance or the core network slice subnet instance according to at least one traffic speed limit parameter among the committed information rate CIR parameter and the peak information rate PIR parameter;

[0031] The configuration of the traffic speed limit parameters is applied to the ingress device interface of the transport network network slice instance.

[0032] In one embodiment of the present disclosure, the method further includes:

[0033] The mapping relationship between the QoS parameters of the access network slice subnet instance and the transmission network slice subnet instance, the mapping relationship between the QoS parameters of the transmission network slice subnet instance message encapsulation layer, and the mapping relationship between the QoS parameters of the transmission network slice subnet instance and the core network slice subnet instance 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 configure the corresponding slice subnet instance QoS parameters according to the mapping relationship of the QoS parameters.

[0034] In one embodiment of the present disclosure, deriving 5QI parameters according to the network slice SLA includes:

[0035] The 5QI parameters are derived according to the slice type information in the network slicing SLA, and different 5QI parameters are assigned to different slice type information.

[0036] According to another aspect of the present disclosure, a communication device is provided, which is applied to a network slice management function, including:

[0037] A request receiving module, used to receive a network slice service subscription request from a communication service management function, wherein the network slice service subscription request carries a network slice service level agreement SLA;

[0038] A first mapping module is used to establish and maintain a mapping relationship between cross-domain slice subnet service quality QoS parameters according to the 5QI parameters if the network slice SLA includes a 5G quality identification 5QI parameter;

[0039] The second mapping module is used to export the 5QI parameters according to the network slice SLA if the network slice SLA does not include the 5QI parameters, and establish and maintain the mapping relationship of the cross-domain slice subnet QoS parameters according to the exported 5QI parameters.

[0040] According to another aspect of the present disclosure, a communication system is provided, including a communication service management function and a network slice management function; wherein:

[0041] The communication service management function is used to send the network slice service subscription request to the network slice management function for the user;

[0042] The network slice management function is used to receive the network slice service subscription request, wherein the network slice service subscription request carries the network slice service level agreement SLA; if the network slice SLA includes the 5G quality identification 5QI parameter, then the mapping relationship of the cross-domain slice subnet service quality QoS parameters is established and maintained according to the 5QI parameter; if the network slice SLA does not include the 5QI parameter, then the 5QI parameter is exported according to the network slice SLA, and the mapping relationship of the cross-domain slice subnet QoS parameters is established and maintained according to the exported 5QI parameter.

[0043] 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.

[0044] 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.

[0045] 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.

[0046] In an embodiment of the present disclosure, a network slice management function receives a network slice service subscription request sent from a communication service management function, and the network slice service subscription request carries a network slice SLA; if the network slice SLA includes a 5QI parameter, a mapping relationship between cross-domain slice subnet QoS parameters is established and maintained according to the 5QI parameter; if the network slice SLA does not include a 5QI parameter, the 5QI parameter is derived according to the network slice SLA, and a mapping relationship between cross-domain slice subnet QoS parameters is established and maintained according to the derived 5QI parameter. The present disclosure can improve the end-to-end QoS configuration efficiency and greatly improve the configuration accuracy.

[0047] 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

[0048] 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.

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

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

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

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

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

[0054] Figure 6 A schematic structural diagram of a communication device provided in an embodiment of the present disclosure is shown.

[0055] Figure 7 A schematic structural diagram of an electronic device in an embodiment of the present disclosure is shown.

[0056] Figure 8 A schematic diagram showing the structure of a computer program product in an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0057] 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.

[0058] 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.

[0059] 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:

[0060] QoS: Quality of Service.

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

[0062] 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, so as to guide packet forwarding by segment.

[0063] 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.

[0064] DSCP: Differentiated Service Codepoint, used by QoS tools to mark data.

[0065] ToS: Type of Service, business type, or service type.

[0066] SLA: Service-Level Agreement.

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

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

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

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

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

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

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

[0074] NSSI: Network Slice Subnet Instance, also known as slice subnet instance, including access network slice subnet instance AN NSSI, transmission network slice subnet instance TN NSSI and core network slice subnet instance CN NSSI. A network slice can be composed of multiple network slice subnets (NSS). For example, a rented network slice can be divided into network slice subnets according to different services, or a network slice serves multiple tenants, and different tenants correspond to different network slice subnets. Different NSSIs have isolation requirements for management data, which can be distinguished by network slice subnet instance identification NSSI ID.

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

[0076] like Figure 1As 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.

[0077] 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.

[0078] 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.

[0079] 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.

[0080] 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.

[0081] 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.

[0082] 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.

[0083] 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.

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

[0085] 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).

[0086] 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.

[0087] like Figure 1 As shown in the figure, in the end-to-end slicing architecture of the 5G network, the communication system also includes management functional components such as CSMF, NSMF, wireless access network slicing subnet management function AN-NSSMF, transmission network slicing subnet management function TN-NSSMF, and core network slicing subnet management function CN-NSSMF. A network slice instance consists of three network slice subnet instances of wireless access network, transmission network and core network, and end-to-end slice management is achieved through the network slice management function.

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

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

[0090] In some embodiments, the base station on the RAN side and the transport network access device are docked between the forwarding planes through standard docking identifiers. For example, Ethernet ports and VLAN ID (4) are used as docking identifiers for slice docking, and the QoS parameter mapping between the access network slice and the transport network slice is done by mapping 5QI parameters to DSCP parameters.

[0091] The core network UPF and the transport network edge device are connected between the forwarding planes through standard connection identifiers. For example, Ethernet ports and VLAN ID (5) are used as connection identifiers for slice connection. The QoS parameter mapping between the core network slices and the transport network slices uses 5QI parameter to DSCP parameter mapping connection.

[0092] 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.

[0093] In 5G networks, 3GPP defines 5QI parameters to prioritize different services in wireless access networks and core networks, and achieve differentiated QoS guarantees for multiple services. However, the QoS technology used in 5G bearer networks depends on different transmission protocols. For example, in pure IPv4, IPv6 or SRv6 networks, the DSCP field is used to prioritize service packets, and in SR-MPLS networks, the TC field is used to prioritize service packets. In the end-to-end cross-domain slicing deployment scenario of 5G networks, implementing correct QoS mapping configuration in three different professional networks is a key factor in ensuring that service packets with different SLAs can obtain consistent QoS guarantees when passing through three slice subnets. How to design an end-to-end cross-domain slicing communication method for different SLAs with good QoS consistency has become a technical problem that needs to be solved urgently.

[0094] 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, which can be executed by any electronic device with computing and processing capabilities. In some embodiments, the communication method provided in the embodiment of the present disclosure can be executed by the network slice management function NSMF of the above system architecture.

[0095] 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:

[0096] S202. Receive a network slice service subscription request from the communication service management function CSMF, wherein the network slice service subscription request carries a network slice service level agreement SLA.

[0097] NSMF receives the network slice service subscription request issued by CSMF, decomposes the network slice SLA into the SLA of the network slice subnet, and issues the network slice subnet deployment request to each NSSMF.

[0098] The network slice service subscription request is a request initiated based on the user's business needs, and the network slice service subscription request may include the network slice SLA.

[0099] Network slicing SLA can include parameters such as user bandwidth, latency, packet reliability, throughput, positioning accuracy, isolation, QoS, bandwidth, etc. Different SLAs define different types of communication services. Network slicing SLA is part of the business agreement signed between the operator and the network slicing user. The network slicing SLA includes the network slicing customer's requirements for the services and networks provided by the operator.

[0100] S204. If the network slice SLA contains the 5G quality identification 5QI parameter, the mapping relationship between the cross-domain slice subnet service quality QoS parameters is established and maintained based on the 5QI parameter.

[0101] 5QI is used to identify and control different service priorities and QoS in the system. Different values ​​of the 5QI parameter represent different service types and priorities. For example, 5QI=1 for VONR (ultra-high definition video call application) voice bearer, 5QI=2 for VINR (video call service) video bearer, and 5QI=5 for VONR's Session Initialization Protocol (SIP) signaling bearer, which can ensure the service quality of specific services in the network.

[0102] In one embodiment, a mapping relationship of cross-domain slice subnet QoS parameters is established and maintained based on 5QI parameters, including at least one of the following: a mapping relationship between QoS parameters of an access network slice subnet instance and a transport network slice subnet instance; a mapping relationship between QoS parameters of a transport network slice subnet instance message encapsulation layer; a mapping relationship between QoS parameters of a transport network slice subnet instance and a core network slice subnet instance.

[0103] In one embodiment, the mapping relationship between the QoS parameters of the access network slice subnet instance and the transmission network slice subnet instance includes: the mapping of the access network 5QI parameters with the DSCP value and 802.1P value of the transmission network.

[0104] In one embodiment, the mapping relationship between the QoS parameters of the transmission network slice subnet instance and the core network slice subnet instance includes: the mapping of the core network 5QI parameters to the DSCP value and 802.1P value of the transmission network.

[0105] Among them, DSCP is a field used to identify the priority and service quality of IP packets. It is a 6-bit field with a value range of 0-63. The DSCP value is mapped to different hop-by-hop behavior identification codes to determine the forwarding behavior of the data packet in the network. The transport network slice subnet instance or the core network slice subnet instance can assign different priorities and processing strategies to the data packet based on the DSCP value of the data packet to achieve differentiation by service quality.

[0106] 802.1P can be used for service quality control of Ethernet frames and can be used as a priority field. A 3-bit priority field is defined in the VLAN tag of the Ethernet frame, which can identify 8 different priorities, from 0 to 7. It can also be used for traffic management. Network devices perform traffic management and scheduling based on the 802.1P priority field of the data packet, giving priority to high-priority data packets to ensure smooth transmission of key services and data.

[0107] It should be noted that the 802.1P value and the DSCP value can be determined according to the actual requirements of the message priority, and the present disclosure does not make any specific limitation on this.

[0108] In some embodiments, the mapping relationship between QoS parameters of the transport network slice subnet instance message encapsulation layer includes configuring the mapping of QoS parameters in the inner and outer layer message headers after the transport network slice subnet instance encapsulates the message entering from the access network slice subnet instance or the core network slice subnet instance.

[0109] S206. If the network slice SLA does not include 5QI parameters, the 5QI parameters are exported according to the network slice SLA, and the mapping relationship between the cross-domain slice subnet QoS parameters is established and maintained according to the exported 5QI parameters.

[0110] In some embodiments, when the network slice SLA does not include 5QI parameters, the NSMF can derive appropriate 5QI parameters based on the slice type information carried in the network slice SLA, and can establish and maintain a mapping relationship between cross-domain slice subnet QoS parameters based on the derived 5QI parameters.

[0111] Among them, the slice type information includes but is not limited to slice types such as eMBB, uRRLC, and Internet of Things (IoT).

[0112] It should be noted that for the case where the network slicing SLA does not include 5QI parameters, after exporting the 5QI parameters according to the network slicing SLA, you can refer to the case where the network slicing SLA includes 5QI parameters, and establish and maintain the mapping relationship of cross-domain slice subnet QoS parameters based on the 5QI parameters. The similarities will not be repeated here.

[0113] In an embodiment of the present disclosure, a network slice management function receives a network slice service subscription request sent from a communication service management function, and the network slice service subscription request carries a network slice SLA; if the network slice SLA includes a 5QI parameter, a mapping relationship between cross-domain slice subnet QoS parameters is established and maintained according to the 5QI parameter; if the network slice SLA does not include a 5QI parameter, the 5QI parameter is derived according to the network slice SLA, and a mapping relationship between cross-domain slice subnet QoS parameters is established and maintained according to the derived 5QI parameter. The present disclosure can improve the end-to-end QoS configuration efficiency and greatly improve the configuration accuracy.

[0114] For the mapping relationship of QoS parameters between the message encapsulation layers of the transport network slice subnet instance, the mapping relationship and message priority scheduling strategy can be determined based on the communication protocol type, slice type information, etc. of the transport network data plane.

[0115] In one embodiment, the mapping relationship between QoS parameters of the transport network slice subnet instance message encapsulation layer may include: in trust mode, when the transport network data plane adopts the IPv4 protocol or the IPv6 protocol, the transport network slice subnet instance receives the first message entering from the access network slice subnet instance or the core network slice subnet instance, does not modify the DSCP value in the IP header of the first message, and performs message priority scheduling according to the DSCP value in the IP header.

[0116] The trust model is a trust-based relationship established between network slice instances, between network slice instances and users, and between network slice instances and underlying network resources during the deployment and operation of network slices. The trust relationship relies on a complete security mechanism, authentication mechanism, and authorization mechanism to ensure the integrity, confidentiality, and availability of data. A zero-trust security model can be used to continuously verify and control access to each network slice instance, user, and resource, implement security authentication and key management between network slices, ensure data transmission security between network slices, and establish a secure isolation and access control mechanism between network slices and underlying network resources.

[0117] The above-mentioned not modifying the DSCP value in the IP header of the first message refers to the ToS field of the IP header of IPv4, or the TC field of the IP header of IPv6.

[0118] In one embodiment, the mapping relationship between the QoS parameters of the transport network slice subnet instance message encapsulation layer may include: in the trust mode, when the transport network data plane adopts the segment routing-multi-protocol label switching SR-MPLS protocol, the transport network slice subnet instance receives the second message entering from the access network slice subnet instance or the core network slice subnet instance, does not modify the DSCP value of the IP header of the second message, configures the mapping of the DSCP value of the IP header of the second message to the traffic category TC field of the SR-MPLS encapsulation, and performs message priority scheduling according to the value of the TC field of the SR-MPLS encapsulation.

[0119] It should be noted that the above-mentioned mapping of the DSCP value of the IP header of the second message to the TC field of the SR-MPLS encapsulation means that the message priority level corresponding to the value of the TC field of the SR-MPLS encapsulation is the same as the message priority level corresponding to the DSCP value of the IP header of the second message.

[0120] In one embodiment, the mapping relationship between the QoS parameters of the transport network slice subnet instance message encapsulation layer may also include: in the trust mode, when the transport network data plane adopts the SRv6 protocol based on IPv6 segment routing, the transport network slice subnet instance receives the third message entering from the access network slice subnet instance or the core network slice subnet instance, does not modify the DSCP value of the IP header of the third message, configures a copy mapping of the DSCP value of the IP header of the third message to the TC field of the SRv6 encapsulation, and performs message priority scheduling according to the value of the TC field of the SRv6 encapsulation.

[0121] The above configuration maps the copy of the DSCP value of the IP header of the third message to the TC field of the SRv6 encapsulation, which means that the value of the TC field of the SRv6 encapsulation is assigned to the DSCP value of the IP header of the third message, so that the message priority is scheduled according to the value of the TC field of the SRv6 encapsulation.

[0122] In addition to configuring the mapping relationship between QoS parameters of the transport network slice subnet message instance encapsulation layer for the trust mode, the mapping relationship in the non-trust mode also needs to be considered.

[0123] In one embodiment, the mapping relationship between QoS parameters of the transport network slice subnet instance message encapsulation layer may include: in non-trusted mode, when the transport network data plane adopts the IPv4 protocol or the IPv6 protocol, the transport network slice subnet modifies the DSCP value of the IP header of the message entering the transport network slice subnet instance from the access network slice subnet instance or the core network slice subnet instance according to the operator policy, performs message priority scheduling according to the modified DSCP value, and restores the IP header of the message going to the access network slice subnet instance or the core network slice subnet instance to the DSCP value before modification.

[0124] The non-trust mode means that during the deployment and operation of network slices, no clear trust relationship is established between network slice instances, between network slice instances and users, and between network slice instances and underlying network resources. In the non-trust mode, communication and data transmission between network slice instances may face higher security risks.

[0125] Operator strategy is a strategy adopted to provide users with the required services based on the different application scenarios required by users. It can be implemented through leasing model, hybrid leasing model, slice hosting model, capability opening model, etc.

[0126] Exemplarily, the mapping relationship between QoS parameters of the transport network slice subnet instance message encapsulation layer may also include: in non-trusted mode, when the transport network data plane adopts the IPv4 protocol or the IPv6 protocol, the transport network slice subnet modifies the DSCP value of the IP header of the message entering the transport network slice subnet instance from the access network slice subnet instance or the core network slice subnet instance according to the operator policy, and the modification of the DSCP value is applied to the ingress device of the transport network slice subnet instance; at the same time, the IP header of the message going to the access network slice subnet instance or the core network slice subnet instance is restored to the DSCP value before the modification, and the modification of the DSCP value is applied to the egress device of the transport network slice subnet instance.

[0127] The above-mentioned transmission network slice subnet modifies the DSCP value of the IP header of the message entering the transmission network slice subnet instance from the access network slice subnet instance or the core network slice subnet instance according to the operator policy, and applies the modified DSCP value to the ingress device of the transmission network slice subnet instance, so that the ingress device of the transmission network slice subnet instance performs message priority scheduling according to the modified DSCP value.

[0128] The transport network slice subnet instance will restore the IP header of the message destined for the access network slice subnet instance or the core network slice subnet instance to the DSCP value before modification, and apply the export device of the transport network slice subnet instance to keep the mapping relationship between the QoS parameters of the access network slice subnet instance and the core network slice subnet instance unchanged.

[0129] In one embodiment, the mapping relationship between the QoS parameters of the transport network slice subnet instance message encapsulation layer may include: in non-trust mode, when the transport network data plane adopts the SR-MPLS protocol, the transport network slice subnet keeps the DSCP value of the IP header of the message entering the transport network slice subnet instance unchanged, sets the corresponding QoS value for the TC field of the SR-MPLS encapsulation according to the operator policy, and performs message priority scheduling according to the QoS value of the TC field of the SR-MPLS encapsulation.

[0130] In one embodiment, the mapping relationship between the QoS parameters of the transport network slice subnet instance message encapsulation layer may include: in non-trusted mode, when the transport network data plane adopts the SRv6 protocol, the transport network slice subnet instance keeps the DSCP value of the IP header of the message entering the transport network slice subnet instance unchanged, sets the corresponding QoS value for the TC field of the SRv6 encapsulation according to the operator policy, and performs message priority scheduling according to the QoS value of the TC field of the SRv6 encapsulation.

[0131] For the configuration method of the mapping relationship of QoS parameters between the encapsulation layers of the transport network slice subnet instance in the non-trusted mode using the SR-MPLS protocol or the SRv6 protocol on the transport network data plane, the TC field can be configured with a suitable QoS value according to the corresponding protocol, and the message priority scheduling can be performed through the QoS value of the TC field.

[0132] It should be noted that the configuration method of the mapping relationship of QoS parameters between the encapsulation layers of the transmission network slice under the above-mentioned trust mode or non-trust mode and different communication protocols can be determined according to actual needs, and the present disclosure does not limit this.

[0133] It should be noted that the QoS value set for the TC field of the SR-MPLS encapsulation and the QoS value set for the TC field of the SRv6 encapsulation can be configured with appropriate values ​​according to actual needs, and can be the same or different, and the present disclosure does not make specific limitations on this.

[0134] In the embodiments of the present disclosure, different mapping relationship configuration methods are adopted for different modes and different communication protocols, so as to realize the QoS parameter configuration of each slice subnet instance, thereby greatly simplifying the operation, maintenance and management requirements of the network.

[0135] Figure 3 FIG. 2 shows another flow chart of a communication method provided in an embodiment of the present disclosure. Figure 3 As shown, in one embodiment, the communication method provided by the embodiment of the present disclosure further includes:

[0136] S302. Configure and manage the traffic rate limit parameters for the messages entering the TN NSSI from the access network slice subnet instance or the core network slice subnet instance.

[0137] In one embodiment of the present disclosure, the traffic speed limit parameters of the messages entering the TNNSSI from the access network slice subnet instance or the core network slice subnet instance are configured and managed, including: configuring the traffic from the access network slice subnet instance or the core network slice subnet instance according to at least one traffic speed limit parameter among the committed information rate (CIR) parameter and the peak information rate (PIR) parameter; the configuration of the traffic speed limit parameters is applied to the ingress device interface of the TN NSSI.

[0138] Traffic speed limiting is a traffic control strategy that monitors traffic rules to limit traffic and resource usage. In traffic speed limiting, traffic speed limiting parameters can also include excess burst size, etc. By configuring traffic speed limiting parameters, it is possible to monitor the network traffic rate of the transport network slice subnet instance, thereby limiting the use of traffic and its resources and providing users with better services.

[0139] Figure 4 FIG. 2 shows a flow chart of another communication method provided in an embodiment of the present disclosure. Figure 4 As shown, in one embodiment, the communication method provided by the embodiment of the present disclosure further includes:

[0140] S208. The mapping relationship between the QoS parameters of the access network slice subnet instance and the transmission network slice subnet instance, the mapping relationship between the QoS parameters of the transmission network slice subnet instance message encapsulation layer, and the mapping relationship between the QoS parameters of the transmission network slice subnet instance and the core network slice subnet instance 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 configure the corresponding slice subnet instance NSSIQoS parameters according to the mapping relationship of the QoS parameters.

[0141] Under the 5G end-to-end network slice deployment management architecture, the network slice management function (NSMF) uniformly establishes and maintains the mapping relationship of cross-domain slice subnet QoS parameters, and sends the mapping relationship between the access network slice subnet instance and the transmission network slice subnet instance QoS parameter, the mapping relationship between the internal message encapsulation layer of the transmission network slice subnet instance, and the mapping relationship between the transmission network slice subnet instance and the core network slice subnet instance QoS parameter to the access network, transmission network, and core network slice subnet management functions (AN / TN / CN NSSMF) respectively. The three slice subnet management functions (AN / TN / CN NSSMF) configure the NSSIQoS parameters of their respective managed slice subnet instances according to the mapping relationship of the QoS parameters corresponding to each slice subnet instance issued, thereby realizing the automatic configuration of the mapping relationship of cross-domain slice subnet QoS parameters, greatly improving the efficiency and accuracy of QoS parameter configuration.

[0142] Figure 5 FIG. 2 shows another flow chart of a communication method provided in an embodiment of the present disclosure. Figure 5 As shown, in one embodiment, deriving 5QI parameters according to the network slice SLA in S206 includes:

[0143] S2062. Export 5QI parameters according to the slice type information in the network slicing SLA, and assign different 5QI parameters to different slice type information.

[0144] In one embodiment, the network slicing SQL includes slice type information, and the slice type information includes but is not limited to slice types such as eMBB, uRRLC, and IoT. NSMF can derive appropriate 5QI parameters based on the slice type information, thereby assigning different 5QI parameters to different slice type information.

[0145] It should be noted that the specific values ​​of the 5QI parameters allocated to different slice type information can be determined according to actual needs. For example, the 5QI parameter corresponding to the uRRLC slice type is 1, and the 5QI parameter corresponding to the eMBB slice type is 6.

[0146] In the disclosed embodiment, 5QI parameters are derived through slice type information in the network slicing SLA, and different 5QI parameters are assigned to different slice type information. Then, the mapping relationship between cross-domain slice subnet QoS parameters is automatically established and maintained based on the derived 5QI parameters, thereby improving the configuration efficiency of end-to-end QoS parameters and greatly improving the accuracy of mapping relationship configuration.

[0147] In order to have a deeper understanding of the communication method disclosed herein, a detailed description is given below with reference to specific examples.

[0148] Example 1: The network slicing service subscription request includes the 5QI parameter.

[0149] When NSMF receives the network slice SLA including 5QI parameters carried in the network slice service subscription request from CSMF, NSMF establishes and maintains the mapping relationship of cross-domain slice subnet QoS parameters according to the 5QI parameters in the network slice service request. The above-mentioned mapping relationship of cross-domain slice subnet QoS parameters includes the mapping relationship between the QoS parameters of the access network slice subnet instance and the transmission network slice subnet instance, the mapping relationship between the QoS parameters of the message encapsulation layer of the transmission network slice subnet instance, and the mapping relationship between the QoS parameters of the transmission network slice subnet instance and the core network slice subnet instance.

[0150] (1) The mapping relationship between the QoS parameters of the access network slice subnet instance or the core network slice subnet instance and the transport network slice subnet instance is shown in Table 1.

[0151] Table 1 Mapping relationship between QoS parameters of access network slice subnet instance or core network slice subnet instance and transport network slice subnet instance

[0152] 5QI Value Slice Type DSCP value 802.1P 1 uL 46 5

[0153] As shown in Table 1, the network slicing service subscription request includes a 5QI parameter, which can construct a correspondence between the 5QI value of the access network slice subnet instance or the core network slice subnet instance and the DSCP value and 802.1P to obtain a mapping relationship between the QoS parameters of the access network slice subnet instance or the core network slice subnet instance and the transmission network slice subnet instance.

[0154] (2) In the trust mode, when the data plane of the transport network adopts the pure IPv4 protocol or the IPv6 protocol, the DSCP value of the IP packet entering the transport network slice subnet instance remains unchanged, that is, the DSCP value in the IP header of the packet entering the transport network slice subnet instance is not modified.

[0155] (3) In the trust mode, when the transport network data plane adopts the SR-MPLS protocol, the mapping relationship between the QoS parameters of the internal message encapsulation layer of the transport network slice subnet instance is shown in Table 2.

[0156] Table 2 Mapping relationship between QoS parameters of internal packet encapsulation layers of transport network slice subnet instance

[0157] 5QI Value Slice Type DSCP value (inner layer) TC value (outer layer) 1 uL 46 5

[0158] As shown in Table 2, the network slicing service subscription request includes 5QI parameters. In trust mode, when the transport network data plane adopts the SR-MPLS protocol, the QoS parameters of the internal message encapsulation layer of the transport network slice subnet instance can remain unchanged for the DSCP value of the IP header of the second message received from the access network slice subnet instance or the core network slice subnet instance, and configure the mapping relationship between the DSCP value of the IP header of the second message and the TC field of the SR-MPLS encapsulation, so as to perform message priority scheduling according to the TC value.

[0159] (4) In the trust mode, when the transport network data plane adopts the SRv6 protocol, the mapping relationship of the QoS parameters of the internal message encapsulation layer of the transport network slice subnet instance is shown in Table 3.

[0160] Table 3 Mapping relationship between QoS parameters of internal packet encapsulation layers of transport network slice subnet instance

[0161] 5QI Value Slice Type DSCP value (inner layer) TC value (outer layer) 1 uL 46 46

[0162] As shown in Table 3, the network slicing service subscription request includes 5QI parameters. In trust mode, when the transport network data plane adopts the SRv6 protocol, the QoS parameters of the internal message encapsulation layer of the transport network slice subnet instance can remain unchanged for the DSCP value of the IP header of the third message received from the access network slice subnet instance or the core network slice subnet instance, and at the same time configure a mapping of the DSCP value of the IP header of the third message to the copy of the TC field of the SRv6 encapsulation, so as to perform message priority scheduling according to the TC value of the SRv6 encapsulation.

[0163] (5) In the untrusted mode, when the transport network data plane adopts the IPv4 protocol or the IPv6 protocol, the DSCP value of the IP packet entering the transport network slice subnet instance can be re-modified according to the operator's customized policy. The QoS parameter mapping, that is, the DSCP value of the IP header of the packet entering the transport network slice subnet instance is modified at the ingress device of the transport network slice subnet instance, and the DSCP value of the IP header of the outgoing packet is restored to the DSCP value before the modification at the egress device of the transport network slice subnet instance to the access network slice subnet instance or the core network slice subnet instance. Table 4 shows the DSCP value modification mapping relationship.

[0164] Table 4 Mapping relationship of modifying DSCP value

[0165]

[0166] As shown in Table 4, the mapping relationship between the QoS parameters of the transport network slice subnet instance message encapsulation layer can be obtained by modifying the DSCP value (i.e., changing the 46 of the access network slice subnet instance or the core network slice subnet instance to 34 inside the transport network instance), and restoring the DSCP of the export device of the transport network slice subnet instance to the DSCP value before modification (i.e., 46 in the last column of Table 4).

[0167] (6) In the untrusted mode, when the transport network data plane adopts the SR-MPLS protocol, the DSCP value of the IP header of the received message of the access network slice subnet instance or the core network slice subnet instance can be kept unchanged, and the appropriate QoS value can be set in the TC field of the SR-MPLS encapsulation of the message according to the operator's customized policy, and the message priority scheduling is performed according to the QoS value. Table 5 shows an example of the mapping relationship between the DSCP value and the TC value.

[0168] Table 5 An example of mapping relationship between DSCP value and TC value

[0169] 5QI Value Slice Type DSCP value (inner layer) TC value (outer layer) 1 uL 46 6

[0170] (7) In untrusted mode, when the data plane of the transport network adopts the SRv6 protocol, the DSCP value of the original IP packet remains unchanged, and an appropriate QoS value is set in the TC field of the IP packet for SRv6 encapsulation according to the operator's customized policy. Table 6 shows an example of the mapping relationship between the inner DSCP value and the outer TC value.

[0171] Table 6 Example of mapping relationship between inner DSCP value and outer TC value

[0172] 5QI Value Slice Type DSCP value (inner layer) TC value (outer layer) 1 uL 46 38

[0173] Example 2: The network slicing service subscription request does not include the 5QI parameter.

[0174] When the network slice SLA carried in the network slice service subscription request received by NSMF from CSMF does not contain 5QI parameters, NSMF can derive appropriate 5QI parameters based on the slice type information in the network slice SLA, and establish and maintain the mapping relationship between cross-domain slice subnet QoS parameters based on the derived 5QI parameters.

[0175] The above-mentioned slice type information may include eMBB, uRRLC, mIoT, etc. For example, when NSMF receives a network slice service subscription request carrying a network slice SLA including an eMBB slice type, NSMF allocates 5QI parameters to the eMBB slice, and establishes and maintains a mapping relationship between cross-domain slice subnet QoS parameters based on the allocated 5QI parameters.

[0176] Table 7 Mapping relationship between QoS parameters of core network slice subnet instance or access network slice subnet instance and transport network slice subnet instance

[0177] 5QI Value Slice Type DSCP value 802.1P 1 eMBB 18 2

[0178] It should be noted that in the above-mentioned mapping relationship of cross-domain slice subnet QoS parameters, the determination of 5QI value, DSCP value (inner layer), TC (outer layer), TC value, 802.1P and other values ​​can be determined according to actual needs. The above examples are only examples provided to illustrate the embodiments of the present disclosure and should not be regarded as limiting the scope of protection of the present disclosure. Different communication protocols can refer to the above examples, which will not be repeated here.

[0179] 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.

[0180] Figure 6 FIG. 2 is a schematic diagram showing the structure of a communication device in an embodiment of the present disclosure. Figure 6As shown, the communication device provided by the embodiment of the present disclosure is applied to the network slice management function, and the device includes a request receiving module 610, a first mapping module 620 and a second mapping module 630. Among them:

[0181] The request receiving module 610 is used to receive a network slice service subscription request from a communication service management function, where the network slice service subscription request carries a network slice service level agreement SLA;

[0182] The first mapping module 620 is used to establish and maintain a mapping relationship between cross-domain slice subnet service quality QoS parameters according to the 5QI parameters if the network slice SLA includes a 5G quality identification 5QI parameter;

[0183] The second mapping module 630 is used to export the 5QI parameters according to the network slice SLA if the network slice SLA does not include the 5QI parameters, and to establish and maintain the mapping relationship of the cross-domain slice subnet QoS parameters according to the exported 5QI parameters.

[0184] It should be noted that the request receiving module 610, the first mapping module 620 and the second mapping module 630 correspond to S202 to S206 in the method embodiment, and the examples and application scenarios implemented by the above modules and the 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.

[0185] In one embodiment, a mapping relationship of cross-domain slice subnet QoS parameters is established and maintained based on 5QI parameters, including at least one of the following: a mapping relationship between QoS parameters of an access network slice subnet instance and a transport network slice subnet instance; a mapping relationship between QoS parameters of a transport network slice subnet instance message encapsulation layer; a mapping relationship between QoS parameters of a transport network slice subnet instance and a core network slice subnet instance.

[0186] It should be noted that the mapping relationship between the QoS parameters of the access network slice subnet instance and the transport network slice subnet instance includes: the mapping of the access network 5QI parameters to the differential service code point DSCP value and 802.1P value of the transport network;

[0187] The mapping relationship between the QoS parameters of the transmission network slice subnet instance and the core network slice subnet instance includes: the mapping of the core network 5QI parameters to the DSCP value and 802.1P value of the transmission network.

[0188] In one embodiment, the mapping relationship between QoS parameters of the transport network slice subnet instance message encapsulation layer includes at least one of the following:

[0189] In the trust mode, when the data plane of the transport network adopts the IPv4 protocol or the IPv6 protocol, the transport network slice subnet instance receives the first message entering from the access network slice subnet instance or the core network slice subnet instance, does not modify the DSCP value in the IP header of the first message, and performs message priority scheduling according to the DSCP value in the IP header;

[0190] In the trust mode, when the data plane of the transport network adopts the SR-MPLS protocol based on segment routing-multi-protocol label switching, the transport network slice subnet instance receives the second message entering from the access network slice subnet instance or the core network slice subnet instance, does not modify the DSCP value of the IP header of the second message, configures the mapping of the DSCP value of the IP header of the second message to the traffic category TC field of the SR-MPLS encapsulation, and performs message priority scheduling according to the value of the TC field of the SR-MPLS encapsulation;

[0191] In the trust mode, when the data plane of the transport network adopts the SRv6 protocol, the transport network slice subnet instance receives the third message from the access network slice subnet instance or the core network slice subnet instance, does not modify the DSCP value of the IP header of the third message, configures the copy mapping of the DSCP value of the IP header of the third message to the TC field of the SRv6 encapsulation, and performs message priority scheduling according to the value of the TC field of the SRv6 encapsulation;

[0192] In non-trusted mode, when the transport network data plane adopts the IPv4 protocol or the IPv6 protocol, the transport network slice subnet instance modifies the DSCP value of the IP header of the message entering the transport network slice subnet instance from the access network slice subnet instance or the core network slice subnet instance according to the operator's policy, and performs message priority scheduling according to the modified DSCP value. At the same time, the IP header of the message going to the access network slice subnet instance or the core network slice subnet instance is restored to the DSCP value before the modification;

[0193] In untrusted mode, when the transport network data plane adopts the SR-MPLS protocol, the transport network slice subnet instance keeps the DSCP value of the IP header of the message entering the transport network slice subnet instance from the access network slice subnet instance or the core network slice subnet instance unchanged, sets the corresponding QoS value for the TC field of the SR-MPLS encapsulation according to the operator policy, and performs message priority scheduling according to the QoS value of the TC field of the SR-MPLS encapsulation;

[0194] In non-trusted mode, when the transport network data plane adopts the SRv6 protocol, the transport network slice subnet instance keeps the DSCP value of the IP header of the message entering the transport network slice subnet instance unchanged, sets the corresponding QoS value for the TC field of the SRv6 encapsulation according to the operator policy, and performs message priority scheduling according to the QoS value of the TC field of the SRv6 encapsulation.

[0195] In one embodiment, in non-trusted mode, when the transport network data plane adopts the IPv4 protocol or the IPv6 protocol, the transport network slice subnet instance modifies the DSCP value of the IP header of the message entering the transport network slice subnet instance according to the operator policy, and the modification of the DSCP value is applied to the ingress device of the transport network slice subnet instance; at the same time, the IP header of the message going to the access network slice subnet instance or the core network slice subnet instance is restored to the DSCP value before the modification, and the modification of the DSCP value is applied to the egress device of the transport network slice subnet instance.

[0196] In one embodiment, the device also includes a parameter configuration module not shown in the accompanying drawings, and the parameter configuration module is used to configure and manage traffic rate limit parameters for messages from an access network slice subnet instance or a core network slice subnet instance entering a transmission network network slice subnet instance.

[0197] In one embodiment, a parameter configuration module is specifically used to configure the traffic from an access network slice subnet instance or a core network slice subnet instance according to at least one traffic limit parameter among a committed information rate CIR parameter and a peak information rate PIR parameter; the configuration of the traffic limit parameter is applied to the ingress device interface of the transport network network slice subnet instance.

[0198] In one embodiment, the device includes a mapping relationship sending module not shown in the accompanying drawings, and the mapping relationship sending module is used to send the mapping relationship between the access network slice subnet instance and the transmission network slice subnet instance QoS parameters, the mapping relationship between the transmission network slice subnet instance message encapsulation layer QoS parameters, and the mapping relationship between the transmission network slice subnet instance and the core network slice subnet instance QoS parameters 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 configure the QoS parameters of the corresponding slice subnet management function according to the mapping relationship of the QoS parameters.

[0199] In one embodiment, the second mapping module is specifically used to derive 5QI parameters according to the slice type information in the network slicing SLA and assign different 5QI parameters to different slice type information.

[0200] In an embodiment of the present disclosure, a network slice management function receives a network slice service subscription request sent from a communication service management function, and the network slice service subscription request carries a network slice SLA; if the network slice SLA includes a 5QI parameter, a mapping relationship between cross-domain slice subnet QoS parameters is established and maintained according to the 5QI parameter; if the network slice SLA does not include a 5QI parameter, the 5QI parameter is derived according to the network slice SLA, and a mapping relationship between cross-domain slice subnet QoS parameters is established and maintained according to the derived 5QI parameter. The present disclosure can improve the end-to-end QoS configuration efficiency and greatly improve the configuration accuracy.

[0201] Continue to refer Figure 1 The communication system provided by the embodiment of the present disclosure includes a communication service management function 140 and a network slice management function 150; wherein: the communication service management function 140 is used for user-oriented network slice service subscription requests, and sends the network slice service subscription requests to the network slice management function 150; the network slice management function 150 is used to receive network slice service subscription requests, wherein the network slice service subscription request carries a network slice service level agreement SLA; if the network slice SLA includes a 5G quality identification 5QI parameter, a mapping relationship between cross-domain slice subnet service quality QoS parameters is established and maintained according to the 5QI parameter; if the network slice SLA does not include a 5QI parameter, the 5QI parameter is derived according to the network slice SLA, and a mapping relationship between cross-domain slice subnet QoS parameters is established and maintained according to the derived 5QI parameter.

[0202] 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".

[0203] Refer to the following Figure 7 An electronic device 700 according to this embodiment of the present invention will be described. Figure 7 The electronic device 700 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.

[0204] like Figure 7 As shown, the electronic device 700 is in the form of a general computing device. The components of the electronic device 700 may include but are not limited to: at least one processing unit 710, at least one storage unit 720, and a bus 730 connecting different system components (including the storage unit 720 and the processing unit 710).

[0205] The storage unit stores program codes, which can be executed by the processing unit 710, so that the processing unit 710 performs 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 710 can perform the following steps: Figure 2 As shown in , a network slice service subscription request is received from a communication service management function, wherein the network slice service subscription request carries a network slice service level agreement SLA; if the network slice SLA includes a 5G quality identification 5QI parameter, a mapping relationship between cross-domain slice subnet service quality QoS parameters is established and maintained according to the 5QI parameter; if the network slice SLA does not include a 5QI parameter, the 5QI parameter is exported according to the network slice SLA, and a mapping relationship between cross-domain slice subnet QoS parameters is established and maintained according to the exported 5QI parameter.

[0206] The storage unit 720 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 7201 and / or a cache storage unit 7202 , and may further include a read-only storage unit (ROM) 7203 .

[0207] The storage unit 720 may also include a program / utility 7204 having a set (at least one) of program modules 7205, such program modules 7205 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.

[0208] Bus 730 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.

[0209] The electronic device 700 may also communicate with one or more external devices 740 (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 700 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 750. 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 760. Figure 7As shown, the network adapter 760 communicates with other modules of the electronic device 700 via the bus 730. 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 700, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0210] 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.

[0211] 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. Figure 8 FIG. 8 is a schematic diagram of a computer-readable storage medium 800 provided by an embodiment of the present disclosure. Figure 8 As shown, a program product capable of implementing the above method of the present disclosure is stored on the computer-readable storage medium 800. 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.

[0212] 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.

[0213] 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.

[0214] 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.

[0215] 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.

[0216] 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).

[0217] 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.

[0218] 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.

[0219] 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.

[0220] 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: Receive a network slice service subscription request from a communication service management function, wherein the network slice service subscription request carries a network slice service level agreement SLA; If the network slice SLA includes a 5G quality identification 5QI parameter, a mapping relationship between cross-domain slice subnet quality of service QoS parameters is established and maintained according to the 5QI parameter; If the network slice SLA does not include 5QI parameters, the 5QI parameters are derived according to the network slice SLA, and the mapping relationship between cross-domain slice subnet QoS parameters is established and maintained based on the derived 5QI parameters.

2. The method according to claim 1, characterized in that The establishing and maintaining a mapping relationship of cross-domain slice subnet QoS parameters according to the 5QI parameters includes at least one of the following: The mapping relationship between the QoS parameters of the access network slice subnet instance and the transport network slice subnet instance; The mapping relationship between QoS parameters of transport network slice subnet instance message encapsulation layers; The mapping relationship between the QoS parameters of the transport network slice subnet instance and the core network slice subnet instance.

3. The method according to claim 2, characterized in that The mapping relationship between the access network slice subnet instance and the transport network slice subnet instance QoS parameters includes: Mapping of access network 5QI parameters to the differential services code point DSCP value and 802.1P value of the transport network; The mapping relationship between the QoS parameters of the transmission network slice subnet instance and the core network slice subnet instance includes: Mapping of core network 5QI parameters to transport network DSCP values ​​and 802.1P values.

4. The method according to claim 2, characterized in that The mapping relationship between the QoS parameters of the transport network slice subnet instance packet encapsulation layer includes at least one of the following: In the trust mode, when the data plane of the transmission network adopts the IPv4 protocol or the IPv6 protocol, the transmission network slice subnet instance receives the first message entering from the access network slice subnet instance or the core network slice subnet instance, does not modify the DSCP value in the IP header of the first message, and performs message priority scheduling according to the DSCP value in the IP header; In the trust mode, when the transport network data plane adopts the segment routing-multi-protocol label switching SR-MPLS protocol, the transport network slice subnet instance receives the second message entering from the access network slice subnet instance or the core network slice subnet instance, does not modify the DSCP value of the IP header of the second message, configures the mapping of the DSCP value of the IP header of the second message to the traffic category TC field of the SR-MPLS encapsulation, and performs message priority scheduling according to the value of the TC field of the SR-MPLS encapsulation; In the trust mode, when the transport network data plane adopts the SRv6 protocol, the transport network slice subnet receives the third message entering from the access network slice subnet instance or the core network slice subnet instance, does not modify the DSCP value of the IP header of the third message, configures a copy mapping of the DSCP value of the IP header of the third message to the TC field of the SRv6 encapsulation, and performs message priority scheduling according to the value of the TC field of the SRv6 encapsulation; In non-trusted mode, when the transport network data plane adopts the IPv4 protocol or the IPv6 protocol, the transport network slice subnet instance modifies the DSCP value of the IP header of the message entering the transport network slice subnet instance from the access network slice subnet instance or the core network slice subnet instance according to the operator policy, performs message priority scheduling according to the modified DSCP value, and restores the IP header of the message going to the access network slice subnet instance or the core network slice subnet instance to the DSCP value before modification; In untrusted mode, when the transport network data plane adopts the SR-MPLS protocol, the transport network slice subnet instance maintains the DSCP value of the IP header of the message entering the transport network slice subnet instance from the access network slice subnet instance or the core network slice subnet instance unchanged, sets the corresponding QoS value for the TC field of the SR-MPLS encapsulation according to the operator policy, and performs message priority scheduling according to the QoS value of the TC field of the SR-MPLS encapsulation; In non-trusted mode, when the transport network data plane adopts the SRv6 protocol, the transport network slice subnet instance keeps the DSCP value of the IP header of the message entering the transport network slice subnet instance unchanged, sets the corresponding QoS value for the TC field of the SRv6 encapsulation according to the operator policy, and performs message priority scheduling according to the QoS value of the TC field of the SRv6 encapsulation.

5. The method according to claim 4, characterized in that The method further comprises: In non-trusted mode, when the transport network data plane adopts the IPv4 protocol or the IPv6 protocol, the transport network slice subnet instance modifies the DSCP value of the IP header of the message entering the transport network slice subnet instance according to the operator policy, and the modification of the DSCP value is applied to the ingress device of the transport network slice subnet instance; at the same time, the IP header of the message going to the access network slice subnet instance or the core network slice subnet instance is restored to the DSCP value before modification, and the modification of the DSCP value is applied to the egress device of the transport network slice subnet instance.

6. The method according to claim 1, characterized in that The method further comprises: Configure and manage the traffic rate limit parameters for messages from the access network slice subnet instance or the core network slice subnet instance entering the transmission network slice subnet instance.

7. The method according to claim 6, characterized in that The configuration management of the flow rate limit parameters for the message of the access network slice subnet instance or the core network slice subnet instance entering the transmission network slice subnet instance includes: Configure the traffic from the access network slice subnet instance or the core network slice subnet instance according to at least one traffic speed limit parameter among the committed information rate CIR parameter and the peak information rate PIR parameter; The configuration of the traffic speed limit parameters is applied to the ingress device interface of the transmission network slice subnet instance.

8. The method according to claim 2, characterized in that: The method further comprises: The mapping relationship between the QoS parameters of the access network slice subnet instance and the transmission network slice subnet instance, the mapping relationship between the QoS parameters of the transmission network slice subnet instance message encapsulation layer, and the mapping relationship between the QoS parameters of the transmission network slice subnet instance and the core network slice subnet instance 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 configure the corresponding slice subnet instance QoS parameters according to the mapping relationship of the QoS parameters.

9. The method according to any one of claims 1 to 8, characterized in that: The deriving 5QI parameters according to the network slice SLA includes: The 5QI parameters are derived according to the slice type information in the network slicing SLA, and different 5QI parameters are assigned to different slice type information.

10. A communication device, characterized in that: Applied to network slice management functions, including: A request receiving module, used to receive a network slice service subscription request from a communication service management function, wherein the network slice service subscription request carries a network slice service level agreement SLA; A first mapping module is used to establish and maintain a mapping relationship between cross-domain slice subnet service quality QoS parameters according to the 5QI parameters if the network slice SLA includes a 5G quality identification 5QI parameter; The second mapping module is used to export the 5QI parameters according to the network slice SLA if the network slice SLA does not include the 5QI parameters, and establish and maintain the mapping relationship of the cross-domain slice subnet QoS parameters according to the exported 5QI parameters.

11. A communication system, characterized in that: Including communication service management functions and network slice management functions; among which: The communication service management function is used to send the network slice service subscription request to the network slice management function for the user; The network slice management function is used to receive the network slice service subscription request, wherein the network slice service subscription request carries the network slice service level agreement SLA; if the network slice SLA includes the 5G quality identification 5QI parameter, then the mapping relationship of the cross-domain slice subnet service quality QoS parameters is established and maintained according to the 5QI parameter; if the network slice SLA does not include the 5QI parameter, then the 5QI parameter is exported according to the network slice SLA, and the mapping relationship of the cross-domain slice subnet QoS parameters is established and maintained according to the exported 5QI parameter.

12. 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 by executing the executable instructions.

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

Images