Method and apparatus for information transmission

Abstract

The application provides a method and device for information transmission, the method comprising: a management service consumer sending network identification and first gateway information to a management service provider of a core network sub-slice, and sending network identification and second gateway information to a management service provider of a bearing network sub-slice. The first gateway information is used to indicate the next hop gateway of the core network sub-slice, the second gateway information is used to indicate the next hop gateway of the bearing network sub-slice, and the network identification is used to indicate the network information configured for the core network sub-slice and the bearing network sub-slice. The method for information transmission provided by the application can realize the mutual connection between different domain sub-slices in the slice deployment process, and is beneficial to keeping the consistent QoS requirement when data is transmitted between different domain sub-slices.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication, and more particularly, to a method and apparatus for information transmission. BACKGROUND

[0002] A network slice instance of a 5G (5th generation) network slice includes a radio access network sub-network slice instance, a bearer network sub-network slice instance, and a core network sub-network slice instance. The core network sub-network slice can be connected with a gateway of the bearer network sub-network slice through an interface of a user plane network element. When the user plane network element is deployed in a data center by virtualization, the user plane network element needs to pass through a gateway of the data center to be connected with an external network.

[0003] The current slice model does not consider the case that the user plane has a gateway in the data center, which leads to the fact that the configuration of the bearer network cannot be completed correctly, so that the core network sub-network slice cannot be connected with the bearer network sub-network slice.

[0004] Therefore, it is necessary to configure the sub-network slices of different domains when deploying the slices, so as to realize the mutual connection between the sub-network slices of different domains. SUMMARY

[0005] The present application provides a method for information transmission, which is used to realize the mutual connection between the sub-network slices of different domains.

[0006] In a first aspect, a method for information transmission is provided, which can be executed by a management service consumer, or can also be executed by a chip or circuit for managing the service consumer, and the present application does not limit this. In order to facilitate description, the following is described by taking the execution by the management service consumer as an example.

[0007] The method comprises:

[0008] The management service consumer sends network identification and first gateway information to a management service provider of a core network sub-slice, the first gateway information being used to indicate a next hop gateway of the core network sub-slice.

[0009] The management service consumer sends network identification and second gateway information to a management service provider of a bearer network sub-slice, the second gateway information being used to indicate a next hop gateway of the bearer network sub-slice, and the network identification being used to indicate network information configured for the core network sub-slice and the bearer network sub-slice.

[0010] In a possible implementation manner, the management service consumer is a network slice management function network element.

[0011] In another possible implementation manner, the management service consumer is a network sub-slice management function network element.

[0012] In a possible implementation, the network identifier is used to indicate network information configured on a next-hop gateway of the core network sub-slice and a next-hop gateway of the bearer network sub-slice.

[0013] The technical scheme provided by the embodiments of the present application is that the management service consumer sends network identifier and first gateway information to the management service provider of the core network sub-slice, and sends network identifier and second gateway information to the management service provider of the bearer network sub-slice, so that the management service provider of the core network sub-slice and the management service provider of the bearer network sub-slice can use the received information to configure the core network sub-slice and the bearer network sub-slice respectively, thereby facilitating the connection of the core network sub-slice and the bearer network sub-slice, the flow between different domains of sub-slices, and the improvement of the overall service quality of the sub-slice network.

[0014] With reference to the first aspect, in some implementations of the first aspect, the management service consumer sends an interface object, the interface object including the network identifier and the first gateway information, and the interface object being associated with an interface of a user plane network element of the core network sub-slice.

[0015] In a possible implementation, the interface object is EP_Transport.

[0016] In a possible implementation, the network identifier is logicInterfaceInfo included in EP_Transport.

[0017] In a possible implementation, the first gateway information is nextHopInfo-CN included in EP_Transport.

[0018] The technical scheme provided by the embodiments of the present application is that the first gateway information and the network identifier are included in an interface object associated with an interface of a user plane network element of the core network sub-slice, and the interface object is sent to the management service provider of the core network sub-slice, which is beneficial to determining the configuration object of the network identifier, thereby facilitating the management service provider of the core network sub-slice to select different configuration schemes to configure the user plane network element of the core network sub-slice or the interface of the user plane network element of the core network sub-slice according to the deployment of the sub-slice, so as to realize the connection of the core network sub-slice and the bearer network sub-slice.

[0019] With reference to the first aspect, in some implementations of the first aspect, the management service consumer sends a quality of service (QoS) mapping relationship to the management service provider of the core network sub-slice, the QoS mapping relationship being a mapping relationship between a QoS identifier of the core network sub-slice and a QoS identifier of the bearer network sub-slice.

[0020] In a possible implementation, the QoS identifier of the core network sub-slice is described by 5QI.

[0021] In a possible implementation, the QoS identifier of the bearer network sub-slice is described by DSCP.

[0022] In a possible implementation, the QoS mapping relationship is a mapping relationship between the 5QI and the DSCP, and is denoted as 5QIDSCPMapping.

[0023] The technical scheme provided by the embodiments of the present application is beneficial to mapping the priority, packet delay budget, and packet error rate of the sub-slice service in the core network sub-slice to the bearer network sub-slice, beneficial to processing the consistent priority and delay of the sub-slice service on the sub-slices in different domains, beneficial to guaranteeing the same service quality of data transmission on the core network sub-slice and the bearer network sub-slice, beneficial to the management of the sub-slice service, beneficial to improving the service quality of the sub-slice service, and beneficial to improving the use experience of the sub-slice service user.

[0024] With reference to the first aspect, in some implementations of the first aspect, the management service consumer sends an interface object, the interface object including the QoS mapping relationship, and the interface object being associated with an interface of a user plane network element of the core network sub-slice.

[0025] In a possible implementation, the interface object is EP_Transport.

[0026] In a possible implementation, the QoS mapping relationship is that the EP_Transport includes 5QIDSCPMapping.

[0027] The technical scheme provided by the embodiments of the present application is beneficial to mapping the priority, packet delay budget, and packet error rate of the sub-slice service in the core network sub-slice to the bearer network sub-slice, beneficial to processing the consistent priority and delay of the sub-slice service on the sub-slices in different domains, beneficial to guaranteeing the same service quality of data transmission on the core network sub-slice and the bearer network sub-slice, beneficial to the management of the sub-slice service, beneficial to improving the service quality of the sub-slice service, and beneficial to improving the use experience of the sub-slice service user.

[0028] With reference to the first aspect, in some implementations of the first aspect, the management service consumer sends configuration information, the configuration information including: network identification, first gateway information, and second gateway information.

[0029] The technical scheme provided by the embodiments of the present application is that the network identification, the first gateway information, and the second gateway information are all included in the configuration information. The management service consumer can send the configuration information to the management service provider of the core network sub-slice and the management service provider of the bearer network sub-slice respectively, without distinguishing the management service providers of the sub-slices of different domains, which is beneficial to improving the information sending efficiency of the management service consumer and the efficiency of the interconnection of the sub-slices of different domains.

[0030] With reference to the first aspect, in some implementations of the first aspect, before sending the QoS mapping relationship, the management service consumer obtains information indicating that the connection of the core network sub-slice and the bearer network sub-slice is completed.

[0031] In a possible implementation, the management service consumer obtains an indication that the core network sub-slice is deployed from the management service provider of the core network sub-slice, so as to determine that the connection of the core network sub-slice and the bearer network sub-slice is completed.

[0032] In a possible implementation, the management service consumer obtains an indication that the bearer network sub-slice is deployed from the management service provider of the bearer network sub-slice, so as to determine that the connection of the core network sub-slice and the bearer network sub-slice is completed.

[0033] The technical scheme provided by the embodiments of the present application is that the management service consumer sends the QoS mapping relationship after obtaining the information indicating that the core network sub-slice is deployed. This is beneficial to reducing the probability of obtaining the deployment QoS mapping relationship when the core network sub-slice and the bearer network sub-slice have not been connected, and is beneficial to realizing the configuration of the QoS mapping relationship on the user plane network element or the session management network element of the core network sub-slice, and is beneficial to improving the efficiency of the deployment of the QoS mapping relationship on the core network sub-slice.

[0034] The second aspect provides a method for information transmission, which can be executed by a management service provider of a core network sub-slice, or can be executed by a chip or circuit for the management service provider of the core network sub-slice, and the present application does not limit this. For ease of description, the following takes the execution by the management service provider of the core network sub-slice as an example for description.

[0035] The method includes:

[0036] The management service provider of the core network sub-slice receives network identification and first gateway information, the first gateway information is used to indicate a next hop gateway of the core network sub-slice, and the network identification is used to indicate network information configured in the core network sub-slice.

[0037] The core network sub-slice management service provider configures the network information for the core network sub-slice.

[0038] The technical scheme provided in the embodiments of the present application is that the management service provider of the core network sub-slice receives network identification and first gateway information, and configures network information indicated by the network identification for the core network sub-slice, which is beneficial to the connection between the core network sub-slice and the bearer network sub-slice and realizes the flow between different sub-slices in different domains.

[0039] With reference to the second aspect, in some implementations of the second aspect, configuring the network information for the core network sub-slice comprises: configuring the network information on a first port of the next hop gateway of the core network sub-slice; or

[0040] The network of the user plane network element of the core network sub-slice is created or modified according to the VNF information of the user plane network element and the network identification of the user plane network element.

[0041] In a possible implementation, the management service provider of the core network sub-slice determines the VNF information of the user plane network element according to the sub-slice identification of the user plane network element of the core network sub-slice, requests the MANO to create or modify the network of the user plane network element, and configures the above network information to the user plane network element.

[0042] The technical scheme provided in the embodiments of the present application can configure the network information indicated by the network identification on the first port of the next hop gateway of the core network sub-slice or create or modify the network of the user plane network element according to the VNF information of the user plane network element, which explicitly indicates the configuration object of the network information indicated by the network identification, is beneficial to realizing the connection between the user plane network element of the core network with different deployments and the bearer network sub-slice, and realizing the flow between different sub-slices in different domains.

[0043] With reference to the second aspect, in some implementations of the second aspect, the management service provider of the core network sub-slice receives an interface object, the interface object comprises network identification and first gateway information, and the interface object is associated with an interface of a user plane network element of the core network sub-slice.

[0044] In a possible implementation, the interface object is EP_Transport.

[0045] In a possible implementation, the network identification is logicInterfaceInfo contained in EP_Transport.

[0046] In a possible implementation, the first gateway information is nextHopInfo-CN contained in EP_Transport.

[0047] The technical solution provided by the embodiments of the present application contains the first gateway information and the network identifier into the interface object associated with the interface of the user plane network element of the core network sub-slice, and causes the management service provider of the core network sub-slice to receive the interface object, which is beneficial for the management service provider of the core network sub-slice to select different configuration schemes to configure the user plane network element of the core network sub-slice or the interface of the user plane network element of the sub-slice according to the deployment of the sub-slice, so as to realize the connection of the core network sub-slice and the bearer network sub-slice.

[0048] With reference to the second aspect, in some implementations of the second aspect, the network identifier and the first gateway information are contained in configuration information, and the configuration information further includes second gateway information, the second gateway information being used to indicate a next-hop gateway of the bearer network sub-slice.

[0049] Receiving the network identifier and the first gateway information includes receiving the configuration information.

[0050] The technical solution provided by the embodiments of the present application contains the network identifier and the first gateway information in the configuration information. After the core network management service provider receives the configuration information, the core network management service provider identifies the network identifier and the first gateway information for the configuration of the core network sub-slice, and then configures the core network sub-slice, so as to realize the connection of the core network sub-slice and the bearer network sub-slice, which is beneficial for improving the efficiency of the connection of the sub-slices of different domains.

[0051] With reference to the second aspect, in some implementations of the second aspect, the management service provider of the core network sub-slice receives a QoS mapping relationship, the QoS mapping relationship being a mapping relationship between the QoS identifier of the core network sub-slice and the QoS identifier of the bearer network sub-slice.

[0052] In a possible implementation, the QoS identifier of the core network sub-slice is described by 5QI.

[0053] In a possible implementation, the QoS identifier of the bearer network sub-slice is described by DSCP.

[0054] In a possible implementation, the QoS mapping relationship is a mapping relationship between the 5QI and the DSCP, and is represented by 5QIDSCPMapping.

[0055] The technical scheme provided by the embodiments of the present application is that the management service provider of the core network sub-slice receives the QoS mapping relationship between the QoS identifier of the core network sub-slice and the QoS identifier of the bearer network sub-slice, and the management service provider of the core network sub-slice can further configure the QoS mapping relationship for the core network sub-slice, which is beneficial to mapping the priority, packet delay budget, and packet error rate of the sub-slice service in the core network sub-slice to the bearer network sub-slice, beneficial to processing the consistent priority and delay of the sub-slice service on the sub-slices in different domains, beneficial to ensuring the same service quality of data transmission on the core network sub-slice and the bearer network sub-slice, beneficial to the management of the sub-slice service, beneficial to improving the service quality of the sub-slice, and beneficial to improving the use experience of the sub-slice service user.

[0056] In combination with the second aspect, in some implementations of the second aspect, the management service provider of the core network sub-slice configures the QoS mapping relationship for the core network sub-slice.

[0057] The technical scheme provided by the embodiments of the present application is that the management service provider of the core network sub-slice configures the QoS mapping relationship to the core network sub-slice, which is beneficial to mapping the priority, packet delay budget, and packet error rate of the sub-slice service in the core network sub-slice to the bearer network sub-slice, beneficial to processing the consistent priority and delay of the sub-slice service on the sub-slices in different domains, beneficial to the management of the sub-slice service, and beneficial to improving the use experience of the sub-slice service user.

[0058] In combination with the second aspect, in some implementations of the second aspect, the management service provider of the core network sub-slice configures the QoS mapping relationship at a user plane network element or a session management network element, and the session management network element is configured to manage the user plane network element.

[0059] It should be understood that the session management network element is configured to manage the transmission and reception of data of the user plane network element. When the QoS mapping relationship is configured to the session management network element, the session management network element can make the data transmitted and received by the user plane network element satisfy the QoS mapping relationship according to the QoS mapping relationship.

[0060] The technical scheme provided by the embodiments of the present application is that the management service provider of the core network sub-slice configures the QoS mapping relationship to the core network sub-slice, which is beneficial to mapping the priority, packet delay budget, and packet error rate of the sub-slice service in the core network sub-slice to the bearer network sub-slice, beneficial to processing the consistent priority and delay of the sub-slice service on the sub-slices in different domains, beneficial to the management of the sub-slice service, and beneficial to improving the use experience of the sub-slice service user.

[0061] With reference to the second aspect, in some implementations of the second aspect, the core network sub-slice management service provider receives an interface object, the interface object including the QoS mapping relationship, the interface object being associated with an interface of a user plane network element of the core network sub-slice.

[0062] In a possible implementation, the interface object is an EP_Transport.

[0063] In a possible implementation, the QoS mapping relationship is a 5QI SCP Mapping included in the EP_Transport.

[0064] The technical solution provided by the embodiments of the present application includes the QoS mapping relationship in the interface object associated with the interface of the user plane network element of the core network sub-slice, and the management service provider of the core network sub-slice can receive the interface object to obtain the QoS mapping relationship. The interface object can be used to determine the user plane network element of the core network sub-slice, and configuring the QoS mapping relationship on the user plane is beneficial to mapping the priority, packet delay budget, and packet error rate of the sub-slice service in the core network sub-slice to the bearer network sub-slice, beneficial to processing the consistent priority and delay of the sub-slice service on different domains of the sub-slice, beneficial to issuing the QoS mapping relationship when the slice is created, beneficial to configuring the QoS mapping relationship corresponding to the slice to the corresponding slice, beneficial to managing the sub-slice service, and beneficial to improving the user experience of the sub-slice service.

[0065] The third aspect provides a method for information transmission, which can be executed by a management service provider of a bearer network sub-slice, or can be executed by a chip or circuit for the management service provider of the bearer network sub-slice, and the present application does not limit this. For the convenience of description, the following will be described by taking the execution of the management service provider of the bearer network sub-slice as an example.

[0066] The method includes:

[0067] The management service provider of the bearer network sub-slice receives network identification and second gateway information, the second gateway information being used to indicate a next-hop gateway of the bearer network sub-slice, and the network identification being used to indicate network information configured in the bearer network sub-slice.

[0068] The management service provider of the bearer network sub-slice configures the network information indicated by the network identification for the bearer network sub-slice.

[0069] The technical solution provided by the embodiments of the present application is that the management service provider of the bearer network sub-slice receives the network identification and the second gateway information, and configures the network information indicated by the network identification for the bearer network sub-slice, which is beneficial to the connection of the bearer network sub-slice and the bearer network sub-slice, and realizes the flow between different domains of the sub-slice.

[0070] In some implementations of the third aspect, in conjunction with the third aspect, the network information is configured for the bearer network sub-slice, including: configuring the network information on a second port of a next hop gateway of the bearer network sub-slice.

[0071] The technical scheme provided by the embodiments of the present application can configure the network information of the network identifier indication on the second port of the next hop gateway of the bearer network sub-slice, which is conducive to the connection of the bearer network sub-slice and the bearer network sub-slice, and realizes the flow between different domain sub-slices.

[0072] In some implementations of the third aspect, in conjunction with the third aspect, the management service provider of the bearer network sub-slice receives configuration information, the configuration information including a network identifier, second gateway information, and first gateway information, the first gateway information being used to indicate a next hop gateway of a core network sub-slice.

[0073] The technical scheme provided by the embodiments of the present application contains the network identifier and the second gateway information in the configuration information. After the management service provider of the bearer network receives the configuration information, the network identifier and the second gateway information for the configuration of the bearer network sub-slice in the configuration information are identified, and then the bearer network sub-slice is configured, realizing the connection of the core network sub-slice and the bearer network sub-slice, which is conducive to improving the efficiency of the connection of different domain sub-slices.

[0074] The technical scheme provided by the embodiments of the present application contains the network identifier, the first gateway information, and the second gateway information in the configuration information, and the management service provider of the bearer network sub-slice can obtain the network identifier and the second gateway information by receiving the configuration information, which is conducive to improving the processing efficiency of the slice service.

[0075] The fourth aspect provides a method for information transmission, including:

[0076] The management service consumer sends a network identifier and first gateway information to a management service provider of a core network sub-slice, the first gateway information being used to indicate a next hop gateway of the core network sub-slice;

[0077] The management service consumer sends a network identifier and second gateway information to a management service provider of a bearer network sub-slice, the second gateway information being used to indicate a next hop gateway of the bearer network sub-slice, and the network identifier being used to indicate network information configured for the core network sub-slice and the bearer network sub-slice.

[0078] The core network sub-slice management network element configures the core network sub-slice according to the network identifier and the first gateway information;

[0079] The management service provider of the bearer network sub-slice configures the bearer network sub-slice according to the network identifier and the second gateway information.

[0080] In a fourth aspect, a management service consumer sends a QoS mapping relationship to a core network sub-slice, the QoS mapping relationship being a mapping relationship between a QoS identifier of the core network sub-slice and a QoS identifier of a bearer network sub-slice.

[0081] The management service provider of the core network sub-slice configures the QoS mapping relationship for the core network sub-slice.

[0082] In a fifth aspect, a communication system is provided, comprising a management service consumer, a management service provider of a core network sub-slice, and a management service provider of a bearer network sub-slice, wherein the management service consumer is configured to perform the method in the first aspect or any possible implementation manner thereof, the management service provider of the core network sub-slice is configured to perform the method in the second aspect or any possible implementation manner thereof, and the management service provider of the bearer network sub-slice is configured to perform the method in the third aspect or any possible implementation manner thereof.

[0083] In a sixth aspect, a communication apparatus is provided, comprising:

[0084] a communication module configured to send, to a management service provider of a core network sub-slice, a network identifier and first gateway information, the first gateway information being used to indicate a next-hop gateway of the core network sub-slice.

[0085] The communication module is further configured to send, to a management service provider of a bearer network sub-slice, the network identifier and second gateway information, the second gateway information being used to indicate a next-hop gateway of the bearer network sub-slice, and the network identifier being used to indicate network information configured for the core network sub-slice and the bearer network sub-slice.

[0086] In a sixth aspect, in some implementations of the sixth aspect, the communication module is further configured to send the interface object, the interface object comprising the network identifier and the first gateway information, and the interface object being associated with an interface of a user plane network element of the core network sub-slice.

[0087] In a sixth aspect, in some implementations of the sixth aspect, the communication module is further configured to send, to the core network sub-slice, a quality of service (QoS) mapping relationship, the QoS mapping relationship being a mapping relationship between a QoS identifier of the core network sub-slice and a QoS identifier of the bearer network sub-slice.

[0088] In a sixth aspect, in some implementations of the sixth aspect, the communication module is further configured to send the interface object, the interface object comprising the QoS mapping relationship.

[0089] In a sixth aspect, in some implementations of the sixth aspect, the communication module is further configured to send, to the management service provider of the core network sub-slice, the configuration information; and,

[0090] send the configuration information to the management service provider of the bearer network sub-slice, the configuration information comprising the network identity, the first gateway information, and the second gateway information.

[0091] With reference to the sixth aspect, in some implementations of the sixth aspect, the communication apparatus further includes:

[0092] The processing module is configured to obtain information indicating that the connection of the core network sub-slice and the bearer network sub-slice is completed before sending the QoS mapping relationship.

[0093] The seventh aspect provides a communication apparatus, comprising:

[0094] The communication module is configured to receive the network identity and the first gateway information, the first gateway information being used to indicate a next hop gateway of the core network sub-slice, and the network identity being used to indicate network information configured for the core network sub-slice.

[0095] The processing module is configured to configure the network information for the core network sub-slice.

[0096] With reference to the seventh aspect, in some implementations of the seventh aspect, the processing module is further configured to: configure the network information on a first port of the next hop gateway of the core network sub-slice; and,

[0097] create or modify a network of a user plane network element of the core network sub-slice according to VNF information of the user plane network element and the network identity.

[0098] With reference to the seventh aspect, in some implementations of the seventh aspect, the communication module is further configured to: receive the interface object, the interface object comprising the network identity and the first gateway information.

[0099] With reference to the seventh aspect, in some implementations of the seventh aspect, the communication module is further configured to: receive the QoS mapping relationship, the QoS mapping relationship being a mapping relationship between a QoS identity of the core network sub-slice and a QoS identity of the bearer network sub-slice.

[0100] With reference to the seventh aspect, in some implementations of the seventh aspect, the processing module is further configured to: configure the QoS mapping relationship for the core network sub-slice.

[0101] With reference to the seventh aspect, in some implementations of the seventh aspect, the processing module is further configured to: configure the QoS mapping relationship at a user plane network element or a session management network element, the session management network element being used to manage the user plane network element.

[0102] With reference to the seventh aspect, in some implementations of the seventh aspect, the communication module is further configured to: receive the interface object, the interface object comprising the QoS mapping relationship.

[0103] The eighth aspect provides a communication apparatus, comprising:

[0104] a communication module, configured to receive network identification and second gateway information, the second gateway information being used to indicate a next-hop gateway of the bearer network sub-slice, and the network identification being used to indicate network information configured in the bearer network sub-slice.

[0105] a processing module, configured to configure the network information for the bearer network sub-slice.

[0106] With reference to the eighth aspect, in some implementations of the eighth aspect, the processing module is further configured to configure the network information on a second port of the next-hop gateway of the bearer network sub-slice.

[0107] With reference to the eighth aspect, in some implementations of the eighth aspect, the communication module is further configured to receive the configuration information, the configuration information comprising: the network identification, the first gateway information, and the second gateway information.

[0108] A ninth aspect provides a communication device, comprising at least one processor, at least one memory coupled with the at least one processor, and the at least one memory configured to store computer programs or instructions, and the at least one processor configured to invoke and run the computer programs or instructions from the at least one memory, so that the communication device performs the method in the first aspect or any possible implementation manner thereof.

[0109] A tenth aspect provides a communication device, comprising at least one processor, at least one memory coupled with the at least one processor, and the at least one memory configured to store computer programs or instructions, and the at least one processor configured to invoke and run the computer programs or instructions from the at least one memory, so that the communication device performs the method in the second aspect or any possible implementation manner thereof.

[0110] An eleventh aspect provides a communication device, comprising at least one processor, at least one memory coupled with the at least one processor, and the at least one memory configured to store computer programs or instructions, and the at least one processor configured to invoke and run the computer programs or instructions from the at least one memory, so that the communication device performs the method in the third aspect or any possible implementation manner thereof.

[0111] A twelfth aspect provides a computer readable storage medium, which stores computer instructions, and when the computer instructions are run on a computer, the method in the first aspect or any possible implementation manner thereof is performed.

[0112] A thirteenth aspect provides a computer readable storage medium, which stores computer instructions, and when the computer instructions are run on a computer, the method in the second aspect or any possible implementation manner thereof is performed.

[0113] In a fourteenth aspect, a computer-readable storage medium is provided, having computer instructions stored therein, which when executed on a computer, cause the method in the second aspect or any possible implementation thereof to be performed.

[0114] In a fifteenth aspect, a computer program product is provided, comprising computer program code which, when executed on a computer, causes the method in the first aspect or any possible implementation thereof to be performed.

[0115] In a sixteenth aspect, a computer program product is provided, comprising computer program code which, when executed on a computer, causes the method in the second aspect or any possible implementation thereof to be performed.

[0116] In a seventeenth aspect, a computer program product is provided, comprising computer program code which, when executed on a computer, causes the method in the third aspect or any possible implementation thereof to be performed.

[0117] In an eighteenth aspect, a chip is provided, comprising a processor configured to read instructions stored in a memory, which when executed by the processor, cause the chip to implement the method in the first aspect to be performed.

[0118] In a nineteenth aspect, a chip is provided, comprising a processor configured to read instructions stored in a memory, which when executed by the processor, cause the chip to implement the method in the second aspect to be performed.

[0119] In a twentieth aspect, a chip is provided, comprising a processor configured to read instructions stored in a memory, which when executed by the processor, cause the chip to implement the method in the third aspect to be performed.

[0120] For the operations of the processor involved in the transmission, sending and acquisition / receiving, if there is no special description, or if it does not contradict the actual role or internal logic in the related description, it can be more generally understood as the processor output and receive, input, etc. Operation, rather than the transmission, sending and receiving operation directly by the radio frequency circuit and the antenna.

[0121] In implementation, the processor can be a dedicated processor for executing these methods, or it can be a processor that executes computer instructions stored in memory to execute these methods, such as a general-purpose processor. The memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or disposed on different chips. This application does not limit the type of memory or the arrangement of the memory and processor. Attached Figure Description

[0122] Figure 1 This is a schematic diagram of a network slicing framework applicable to embodiments of this application.

[0123] Figure 2 This is a schematic diagram of an application scenario according to an embodiment of this application.

[0124] Figure 3 This is a schematic diagram of a method for constructing network slices applicable to embodiments of this application.

[0125] Figure 4 This is a schematic diagram of an information transmission method provided in an embodiment of this application.

[0126] Figure 5 This is a schematic diagram illustrating the process of configuring a core network sub-slice according to an embodiment of this application.

[0127] Figure 6 This is a schematic diagram of another information transmission method provided in an embodiment of this application.

[0128] Figure 7 This is a schematic diagram of another information transmission method provided in the embodiments of this application.

[0129] Figure 8 This is a schematic diagram of another information transmission method provided in the embodiments of this application.

[0130] Figure 9 This is a schematic diagram of another information transmission method provided in the embodiments of this application.

[0131] Figure 10 This is a schematic diagram of another information transmission method provided in the embodiments of this application.

[0132] Figure 11 This is a schematic diagram of a communication device provided in an embodiment of this application.

[0133] Figure 12 This is a schematic diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0134] The technical solutions in the application will be described below with reference to the drawings.

[0135] The technical solutions of the embodiments of the application can be applied to various communication systems, for example, a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) system, a general packet radio service (GPRS), a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD), a universal mobile telecommunication system (UMTS), a worldwide interoperability for microwave access (WiMAX) communication system, a future 5th generation (5G) system or a new radio (NR), etc.

[0136] The terminal device in the embodiments of the application can refer to a user equipment, an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user apparatus. The terminal device can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G network or a terminal device in a future evolved public land mobile network (PLMN), etc., and the embodiments of the application are not limited thereto.

[0137] The network device in the embodiments of the present application can be a device for communicating with a terminal device. The network device can be a base station (base transceiver station, BTS) in a global system of mobile communication (GSM) system or a code division multiple access (CDMA) system, can be a base station (NodeB, NB) in a wideband code division multiple access (WCDMA) system, can be an evolved nodeB (eNB or eNodeB) in an LTE system, can be a wireless controller in a cloud radio access network (CRAN) scenario, or can be a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in a future 5G network, or a network device in a future evolved PLMN network, and the like. The embodiments of the present application are not limited.

[0138] Figure 1 A network slice framework diagram applied to the embodiments of the present application.

[0139] As shown in Figure 1 , the end-to-end network slice framework includes a network slice management domain and a network slice service domain. The following describes each part involved in the network slice management domain. Figure 1

[0140] 1. A communication service management network element, responsible for generating an allocation request of a new network slice instance, mainly providing functions and services for the customer side, and providing management of network slice product information, such as product catalog.

[0141] In the 5G communication system, the communication service management service provider can be a communication service management function (CSMF) network element. In the future communication system, the communication service management service provider can still be a CSMF network element, or can have other names, which are not limited in the present application.

[0142] 2. A slice management service provider, mainly responsible for the management of an end-to-end network slice, including life cycle management, performance management, fault monitoring, and the like, such as decomposing network slice service requirements into wireless / bearer / core network sub-domain slice subnetwork service requirements, and performing the decomposition and distribution to complete the new construction of a network slice instance.

[0143] ​In the 5G communication system, the slice management service provider can be a network slice management function (NSMF) network element. In the future communication system, the slice management service provider can still be the NSMF network element, or can also have other names, which are not limited in the present application.

[0144] 3. A sub-slice management service provider, responsible for the life cycle management, performance management, fault monitoring, etc. of the slice subnetwork of each sub-domain, specifically including an access network sub-slice management service provider, a bearer network sub-slice management service provider, and a core network sub-slice management service provider.

[0145] In the 5G communication system, the sub-slice management service provider can be a network slice subset management function (NSSMF) network element. In the future communication system, the sub-slice management service provider can still be the NSSMF network element, or can also have other names, which are not limited in the present application.

[0146] 4. An access network sub-slice management service provider, responsible for the access of terminal devices, the allocation of radio resources, and the selection of core network elements, etc.

[0147] In the 5G communication system, the access network sub-slice management service provider can be an access network-network slice subset management function (AN-NSSMF) network element. In the future communication system, the access network sub-slice management service provider can still be the AN-NSSMF network element, or can also have other names, which are not limited in the present application.

[0148] 5. A bearer network sub-slice management service provider, used for managing the creation of a bearer network sub-slice, which can be used to connect an access network sub-slice and a core network sub-slice.

[0149] In the 5G communication system, the bearer network sub-slice management service provider can be a transport network-network slice subset management function (TN-NSSMF) network element. In the future communication system, the bearer network sub-slice management service provider can still be the TN-NSSMF network element, or can also have other names, which are not limited in the present application.

[0150] 6、Core network sub-slice management service provider, responsible for session management of terminal equipment, including terminal equipment registration, session establishment and roaming, etc.

[0151] In the 5G communication system, the core network sub-slice management service provider can be a core network sub-slice management function (CN-NSSMF) network element. In future communication systems, the core network sub-slice management service provider can still be a CN-NSSMF network element, or it can also have other names, which are not limited by the present application.

[0152] 7、Terminal equipment: the entrance for mobile users to interact with the network, which can provide basic computing power, storage capacity, display business windows to users, and accept user operation input. It can include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems with wireless communication functions, and various forms of terminals, mobile stations (MS), terminals, user equipment (UE), soft terminals, etc. For example, water meters, electricity meters, sensors, etc.

[0153] 8、(Radio) access network ((R)AN): used to provide network access functions for authorized terminal equipment in a specific area, and can use different quality transmission tunnels according to the level of terminal equipment, service requirements, etc.

[0154] The (R)AN can manage radio resources to provide access services for terminal equipment, and further complete the forwarding of control signals and terminal equipment data between terminal equipment and the core network. The (R)AN network element can also be understood as a base station in the traditional network.

[0155] In the 5G communication system, the access network can be (R)AN. In future communication systems, the access network can still be (R)AN, or it can also have other names, which are not limited by the present application.

[0156] 9、Transport network (TN): also known as transmission network, transport network, bearer network, transmission network or transport network, responsible for connecting the access network and the core network, and transmitting data.

[0157] In the 5G communication system, the bearer network can be TN. In future communication systems, the bearer network can still be TN, or it can also have other names, which are not limited by the present application.

[0158] 10、Core Network (CN): also referred to as core network, responsible for managing data transmitted by a bearer network.

[0159] In the 5G communication system, the core network can be a CN. In the future communication system, the core network can still be a CN, or can also have other names, which are not limited in the present application.

[0160] 11、Data Network (DN): a data network that provides service to users. Generally, the client is located in the UE, and the server is located in the data network. The data network can be a private network, such as a local area network, or an external network not controlled by the operator, such as the Internet, or a dedicated network jointly deployed by the operator, such as a network providing Internet Protocol (IP) Multimedia System (IMS) services.

[0161] In the 5G communication system, the data network can be a DN. In the future communication system, the data network can still be a DN, or can also have other names, which are not limited in the present application.

[0162] It can be understood that the above network elements or functions can be network elements in hardware devices, or software functions running on dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform). The above network elements or functions can be divided into one or more services, and further, services independent of network functions can also appear.

[0163] Further, the NSMF network element is referred to as NSMF, and the NSSMF network element is referred to as NSSMF. That is, the NSMF described in the subsequent application can be replaced by a slice management network element, and the NSSMF can be replaced by a sub-slice management network element.

[0164] Figure 2 The application scenario of the information transmission method provided by the present application is shown.

[0165] As shown in Figure 2 , in the slice deployment process, if the user plane network element of the core network sub-slice is deployed in a data center by virtualization, the user plane network element needs to first pass through the gateway 1 or gateway 2 of the core network sub-slice to realize connection with the external network. Since the bearer network sub-slice also sets the gateway 3, passing through the gateway 1 or gateway 2 and then passing through the gateway 3 can realize the connection between the core network sub-slice and the access network sub-slice.

[0166] The construction method of the network slice applied to the embodiments of the present application is further described below. Figure 3 application.

[0167] Network slice (NS) is a kind of on-demand networking method, which can make the operator separate multiple virtual end-to-end networks on a unified infrastructure, and each network slice is logically isolated from radio access network to bearer network to core network to adapt to various types of applications. In a network slice, at least three parts of access network sub-slice, bearer network sub-slice and core network sub-slice can be divided.

[0168] Figure 3 A network slice construction method is shown, and the functional entities involved in the process mainly include: a communication service management network element, a slice management network element, a sub-slice management network element and management and orchestration (MANO).

[0169] The user subscribes to a communication service on a portal website;

[0170] The communication service management network element completes the conversion of user demand to service level agreement (SLA);

[0171] The slice management network element selects a suitable sub-slice according to the SLA;

[0172] The sub-slice management network element is responsible for completing the resource application of the sub-slice, and performing the life cycle management of the sub-slice;

[0173] The MANO completes the deployment of each sub-slice and the network, computing and storage resources relied on by the sub-slice on the network functions virtualization infrastructure (NFVI);

[0174] The management system will notify the user in reverse that the slice deployment is completed, and the communication service can be used. The user can subsequently optimize and adjust the slice.

[0175] Before introducing the embodiments of the present application, some professional terms that may be used in the following embodiments are first explained.

[0176] Quality of service (QoS): refers to the probability of meeting a given service contract in the field of packet switching network, or refers to the probability of passing through two points in the network. QoS is a control mechanism that provides different priorities for different users or different data streams, or guarantees the performance of data to a certain level according to the requirements of the application program. The guarantee of QoS is very important for the network with limited capacity, especially for streaming multimedia applications.

[0177] Service-level agreement (SLA), also known as service level agreement, is a formal commitment between service providers and customers. Service providers and service users specifically agree on service indicators-quality, availability and responsibility.

[0178] Differentiated services code point (DSCP): a QoS classification standard that uses 6 bits and 2 bits that are not used in the type of service (TOS) identification byte in the IP header of each data packet to distinguish priority by encoding value. DSCP values have two forms of expression, numerical form and keyword form. In numerical form, DSCP contains 6 bits, the decimal interval is 0-63, and 64 priority levels can be defined. In keyword form, the DSCP value is called per-hop behavior (PHB), and there are three types of PHB that have been defined, which are best effort service, guaranteed forwarding and expedited forwarding.

[0179] Single-network slice selection assistance information (S-NSSAI): used to identify a network slice, composed of two parts: slice / service type and slice differentiator.

[0180] Gateway (GW): refers to a server that forwards communication data of other servers. When receiving a request sent from a client, the gateway can process the request as the source server that owns the resource.

[0181] Network slice instance (NSI): a temporary logical network that spans multiple technology domains and includes group networks, storage, computing and connection relationships.

[0182] Element management system (EMS): refers to a system that manages one or more telecommunication network elements of a specific type.

[0183] Network slice subnet instance distinguished name (NSSIDN): the unique identifier of the NSSI in the system.

[0184] Virtual local area network (VLAN): a network management technology built on local area network switching technology, through which network management can effectively assign ingress and egress local area network packets to the correct ingress and egress port, achieve logical group management of devices in different entity local area networks, and reduce congestion caused by excessive useless packets when a large amount of data flows through the local area network, and improve information security protection of the local area network.

[0185] Virtualized network function (VNF): a software application that provides network functions such as directory services, routers, firewalls, load balancers, etc. Virtual network functions are deployed in the form of virtual machines, and are usually the next step in the digital transformation of telecommunications providers from traditional network equipment physical network functions to proprietary hardware.

[0186] Network function virtualization (NFV) management and orchestration is an architecture framework for managing and orchestrating VNFs and other software components, including three main functional modules: NFV orchestrator, VNF manager, and virtualized infrastructure manager.

[0187] N3 interface (EP_N3): the interface between (R)AN and CN user plane network elements, mainly used for transmitting uplink and downlink user plane data between (R)AN and user plane network elements.

[0188] In the 5G communication system, the interface can be the N3 interface. In future communication systems, the interface can still be the N3 interface, or it can also have other names, which are not limited by the present application.

[0189] Guaranteed bit rate (GBR): refers to the minimum bit rate guaranteed by the system for a bearer, which can be maintained even in the case of network resource shortage.

[0190] Push to talk (PTT): also known as one-key communication, is a communication mode that switches the sending and receiving state by pressing the switch, commonly used in communication channels using half-duplex mode, including two-way radio systems.

[0191] The following Figure 4 The method for transmitting information provided by the embodiments of the present application is described.

[0192] S110: The management service consumer sends network identification and first gateway information.

[0193] In some embodiments, the first gateway information is used to indicate a next hop gateway of the core network sub slice.

[0194] In one embodiment, the first gateway information is next hop information (nextHopInfo-CN) of the core network sub slice.

[0195] In some embodiments, the network identification is used to indicate network information configured in the core network sub slice.

[0196] In some embodiments, the first gateway information includes an IP address of a next hop gateway of the core network sub slice and an exit port number of the next hop gateway of the core network sub slice.

[0197] In some embodiments, the network identification information is a virtual local area network (VLAN) identification (ID).

[0198] In some embodiments, the management service consumer is a NSSMF.

[0199] In some embodiments, the management service consumer is a NSMF.

[0200] The management service consumer sends the network identification and the first gateway information to a management service provider of the core network sub slice, and the management service provider of the core network sub slice can configure the core network sub slice by using the received information, thereby facilitating the connection of the core network sub slice and the bearer network sub slice and the flow of data between different domain sub slices.

[0201] In some embodiments, the management service consumer sends a sub slice service requirement before sending the network identification and the first gateway information, the sub slice service requirement being used to indicate the creation of a sub slice and the allocation of a sub slice identification to the sub slice.

[0202] For example, the management service consumer is a NSMF, and the NSMF sends a sub slice service requirement to a NSSMF, instructing the NSSMF to create a sub slice and allocate a sub slice identification to the newly created sub slice.

[0203] For example, the management service consumer is a NSSMF, and the NSSMF sends a sub slice service requirement to a core network sub slice management network element, instructing the core network sub slice management network element to create a core network sub slice and allocate a sub slice identification to the newly created core network sub slice.

[0204] It should be understood that the sub slice identification is used to identify a sub slice and network resources contained in the sub slice.

[0205] For example, the sub slice identification can be used to identify a core network sub slice contained in the sub slice.

[0206] Exemplarily, the sub-slice identifier can be used to identify a user plane network element in the core network sub-slice contained by the sub-slice.

[0207] Exemplarily, the sub-slice identifier can be used to identify an N3 interface of a user plane network element in the core network sub-slice contained by the sub-slice.

[0208] In some embodiments, the sub-slice identifier is an NSSID N.

[0209] In some embodiments, the management service consumer sends the QoS mapping relationship after sending the network identifier and the first gateway information.

[0210] The management service consumer sends the QoS mapping relationship between the QoS identifier of the core network sub-slice and the QoS identifier of the bearer network sub-slice to the management service provider of the core network sub-slice, which is beneficial to mapping the priority, packet delay budget, and packet error rate of the sub-slice service in the core network sub-slice to the bearer network sub-slice, beneficial to processing the consistent priority and delay of the sub-slice service on different sub-slices in different domains, beneficial to ensuring the same service quality of data transmission on the core network sub-slice and the bearer network sub-slice, beneficial to the management of the sub-slice service, beneficial to improving the service quality of the sub-slice service, and beneficial to improving the user experience of the sub-slice service.

[0211] In some embodiments, the management service consumer obtains information indicating that the connection of the core network sub-slice and the bearer network sub-slice is completed before sending the QoS mapping relationship.

[0212] The management service consumer sends the QoS mapping relationship after obtaining the information indicating that the deployment of the core network sub-slice is completed, which is beneficial to reducing the probability of obtaining the deployment QoS mapping relationship when the core network sub-slice and the bearer network sub-slice have not been connected, beneficial to realizing the configuration of the QoS mapping relationship on the user plane network element or the session management network element of the core network sub-slice, and beneficial to improving the efficiency of deploying the QoS mapping relationship on the core network sub-slice.

[0213] In some embodiments, the QoS mapping relationship is a mapping relationship between the QoS identifier of the core network sub-slice and the QoS identifier of the bearer network sub-slice.

[0214] In one embodiment, the QoS identifier of the core network sub-slice is described by a 5G quality identity (5QI), and the QoS identifier of the bearer network sub-slice is described by a differentiated services code point (DSCP).

[0215] In one embodiment, the QoS mapping relationship is a 5QI DSCP mapping (5QIDSCP Mapping).

[0216] Table 1 is a way of describing different QoSs using 5QI applicable to the present embodiment. Different 5QI values can represent different service types in the core network, corresponding to different transmission requirements (such as packet delay, packet error rate).

[0217] Table 1: Relationship between 5QI value and service type

[0218]

[0219]

[0220] In some embodiments, the management service consumer sends an interface object to the core network sub-slice management service provider, the interface object including: a network identifier and first gateway information, the interface object being associated with an interface of a user plane network element of the core network sub-slice.

[0221] In some embodiments, the management service consumer sends an interface object to the core network sub-slice management service provider, the interface object including a QoS mapping relationship, the interface object being associated with an interface of a user plane network element of the core network sub-slice.

[0222] In one embodiment, the interface of the user plane network element of the core network sub-slice is an N3 interface, the interface object associated with the N3 interface is an endpoint transport object (EP_Transport), the network identifier is logic interface information (logicInterfaceInfo) contained in the EP_Transport, and the first gateway information is nextHopInfo-CN contained in the EP_Transport.

[0223] In some embodiments, the management service consumer sends configuration information to the core network sub-slice management service provider, the configuration information including: a network identifier, first gateway information, and second gateway information, the second gateway information being used to indicate a next hop gateway of a bearer network sub-slice.

[0224] S120: The management service provider of the core network sub-slice receives a network identifier and first gateway information, and configures network information indicated by the network identifier for the core network sub-slice.

[0225] In some embodiments, the management service provider of the core network sub-slice configures network information indicated by the network identifier on a first port of a next hop gateway of the core network sub-slice.

[0226] In some embodiments, the management service provider of the core network sub-slice creates or modifies a network of a user plane network element according to VNF information of the user plane network element of the core network sub-slice and network information indicated by the network identifier.

[0227] Exemplarily, when the user plane network element has not created a network, the management service provider of the core network sub-slice creates a network containing the network information indicated by the network identifier according to the VNF information of the user plane network element of the core network sub-slice and the network information indicated by the network identifier.

[0228] Exemplarily, when the user plane network element has created a network, the management service provider of the core network sub-slice modifies the network created by the user plane network element to a network containing the network information indicated by the network identifier according to the VNF information of the user plane network element of the core network sub-slice and the network information indicated by the network identifier.

[0229] The management service provider of the core network sub-slice configures the network information indicated by the network identifier on the first port of the next hop gateway of the core network sub-slice or creates or modifies the network of the user plane network element according to the VNF information of the user plane network element, which explicitly indicates the configuration object of the network information indicated by the network identifier, and is beneficial to implement the connection between the user plane network element of the core network with different deployments and the bearer network sub-slice and implement the flow between different sub-slices in different domains.

[0230] In some embodiments, the management service provider of the core network sub-slice receives a QoS mapping relationship, which is a mapping relationship between the QoS identifier of the core network sub-slice and the QoS identifier of the bearer network sub-slice.

[0231] The management service provider of the core network sub-slice configures the QoS mapping relationship for the core network sub-slice.

[0232] In some embodiments, the management service provider of the core network sub-slice configures the QoS mapping relationship at the user plane network element of the core network sub-slice.

[0233] In some embodiments, the management service provider of the core network sub-slice configures the QoS mapping relationship at the session management network element of the core network sub-slice.

[0234] In some embodiments, the EMS configures the QoS mapping relationship at the session management network element of the core network sub-slice.

[0235] In some embodiments, the management service provider of the core network sub-slice receives an interface object, which includes: a network identifier and first gateway information.

[0236] In some embodiments, the management service provider of the core network sub-slice receives an interface object, which includes: a network identifier, first gateway information, and a QoS mapping relationship.

[0237] The first gateway information and the network identifier are contained into an interface object associated with an interface of a user plane network element of the core network sub-slice, and the management service provider of the core network sub-slice receives the interface object, so that the management service provider of the core network sub-slice can select different configuration schemes to configure the user plane network element of the core network sub-slice or the interface of the user plane network element of the sub-slice according to the deployment of the sub-slice, thereby realizing the connection between the core network sub-slice and the bearer network sub-slice.

[0238] In some embodiments, the management service provider of the core network sub-slice receives the configuration information, and the configuration information includes the network identifier, the first gateway information, and the second gateway information.

[0239] In S130, the management service consumer sends the network identifier and the second gateway information.

[0240] In some embodiments, the second gateway information is used to indicate a next hop gateway of the bearer network sub-slice.

[0241] In one embodiment, the second gateway information is next hop gateway information (nextHopInfo-TN) of the bearer network sub-slice.

[0242] In some embodiments, the network identifier is used to indicate network information configured in the bearer network sub-slice.

[0243] In some embodiments, the second gateway information includes an IP address of a next hop gateway of the bearer network sub-slice and an exit port number of the next hop gateway of the bearer network sub-slice.

[0244] In some embodiments, the management service consumer is a NSSMF.

[0245] In some embodiments, the management service consumer is a NSMF.

[0246] In some embodiments, before sending the network identifier and the second gateway information, the management service consumer sends a sub-slice service requirement, and the sub-slice service requirement is used to indicate to create a sub-slice and allocate a sub-slice identifier to the sub-slice.

[0247] For example, the management service consumer is a NSMF, and the NSMF sends a sub-slice service requirement to a NSSMF, instructing the NSSMF to create a sub-slice and allocate a sub-slice identifier to the newly created sub-slice.

[0248] For example, the management service consumer is a NSSMF, and the NSSMF sends a sub-slice service requirement to a bearer network sub-slice management network element, instructing the bearer network sub-slice management network element to create a sub-slice and allocate a sub-slice identifier to the newly created sub-slice.

[0249] It should be understood that the sub-slice identifier is used to identify the sub-slice and the network resources contained in the sub-slice.

[0250] For example, a sub-slice identifier can be used to identify the carrier network sub-slice contained in the sub-slice.

[0251] By sending network identifiers and second gateway information to the management service provider of the bearer network subslice, the management service provider can configure the bearer network subslice using the received information. This facilitates the connection between the core network subslice and the bearer network subslice, enabling the flow of data between subslices in different domains.

[0252] In some embodiments, the management service consumer sends configuration information to the bearer network subslice management service provider, which includes: network identifier, first gateway information, and second gateway information.

[0253] S140: The management service provider of the bearer network sub-slice receives the network identifier and the second gateway information, and configures the network information indicated by the network identifier for the bearer network slice.

[0254] In some embodiments, the management service provider of the bearer subslice configures network information indicating a network identifier on the first port of the next-hop gateway of the bearer subslice.

[0255] In some embodiments, the management service provider carrying the sub-slice of the network receives configuration information, which includes: network identifier, first gateway information, and second gateway information.

[0256] The management service provider of the bearer network sub-slice receives the network identifier and the second gateway information, and configures the network information indicated by the network identifier for the bearer network sub-slice. This facilitates the connection between bearer network sub-slices and enables the flow of data between sub-slices in different domains.

[0257] The above combination Figure 4 The method of information transmission provided in the embodiments of this application is explained below, in conjunction with Figure 5 Provide a detailed description of the configuration process for core network sub-slices by the management service provider.

[0258] S121: Receive information sent by the management service consumer.

[0259] In some embodiments, the management service consumer is NSMF, and the core network subslice management service provider receives configuration information sent by NSMF, which includes: network identifier, first gateway information, and second gateway information.

[0260] In some embodiments, the management service consumer is NSSMF, and the core network subslice management service provider receives an interface object sent by NSSMF, which includes a network identifier and first gateway information.

[0261] In some embodiments, the management service consumer is the NSSMF, and the core network sub-slice management service provider receives an interface object sent by the NSSMF, the interface object comprising: a network identifier, first gateway information, and a QoS mapping relationship.

[0262] In some embodiments, the management service consumer is the NSSMF, and the core network sub-slice management service provider receives one or more of the network identifier, the first gateway information, and the QoS mapping relationship sent by the NSSMF.

[0263] S122: Determine the configuration object.

[0264] In some embodiments, the core network sub-slice management service provider determines, according to the first gateway information contained in the configuration information, the first port of the core network sub-slice as the configuration object.

[0265] In some embodiments, the core network sub-slice management service provider determines, according to the first gateway information contained in the interface object, the first port of the core network sub-slice as the configuration object.

[0266] In some embodiments, the core network sub-slice management service provider determines, according to the first gateway information, the first port of the core network sub-slice as the configuration object.

[0267] In some embodiments, the core network sub-slice management service provider determines, according to the interface object, the user plane network element of the core network sub-slice associated with the interface object as the configuration object.

[0268] S123: Configure network information.

[0269] In some embodiments, the core network sub-slice management service provider configures the network information at the first port of the core network sub-slice.

[0270] In some embodiments, the core network sub-slice management service provider determines, according to the sub-slice identifier of the user plane network element, the VNF instance information of the user plane network element. With the network identifier, the creation or modification of the external network of the user plane network element is completed by the MANO.

[0271] The above describes the configuration process of the core network sub-slice management service provider on the core network sub-slice. The following describes the application of the information transmission method provided by the present application in a specific scenario. Figure 5 Figures 6 to 10 The following embodiments involve the same content as the embodiments shown in

[0272] For brevity, the same content as the embodiments shown in Figure 4 will not be repeated, and the specific content can be referred to the corresponding description of the embodiments shown in Figure 4 . ​

[0273] Figure 6 Fig. 1 shows a schematic diagram of an information transmission method according to an embodiment of the present application. Figure 6 In the application scenario shown, the user plane network element of the core network slice subnetwork is deployed in a virtualized manner, and the user plane network element of the core network slice subnetwork needs to pass through a gateway of a data center (DC) to be connected to an external network. The management service consumer is a sub-slice management network element.

[0274] S201: The slice management network element sends a slice subnetwork creation request to the sub-slice management network element.

[0275] S202: The sub-slice management network element creates a first sub-slice and allocates a sub-slice identifier NSSIDN to the first sub-slice.

[0276] S203: The sub-slice management network element sends the sub-slice identifier of the first sub-slice to the slice management network element.

[0277] S204: The slice management network element creates an interface object according to the sub-slice identifier in the first sub-slice, and associates the interface object to an interface of the user plane network element of the first sub-slice.

[0278] S205: The sub-slice management network element sends the network identifier and the first gateway information to the core network sub-slice management network element.

[0279] In some embodiments, the sub-slice management network element sends an interface object to the core network sub-slice management network element, and the interface object contains the network identifier and the first gateway information.

[0280] S206: The core network sub-slice management network element determines a first port of a next-hop gateway of the core network sub-slice according to the first gateway information.

[0281] S207: The core network sub-slice management network element configures the network information indicated by the network identifier to the first port.

[0282] S208: The sub-slice management network element sends the network identifier and the second gateway information to the bearer network sub-slice management network element.

[0283] S209: The bearer network sub-slice management network element determines a second port of a next-hop gateway of the bearer network sub-slice according to the second gateway information.

[0284] S210: The bearer network sub-slice management network element configures the network information indicated by the network identifier to the second port.

[0285] Figure 7 Fig. 2 shows another schematic diagram of an information transmission method according to an embodiment of the present application. Figure 7In the application scenario shown, the management service consumer is a sub-slice management network element. The core network sub-slice management network element creates or modifies the network of the user plane network element according to the VNF information and the network identifier of the user plane network element of the core network sub-slice.

[0286] S301: The slice management network element sends a slice sub-network creation request to the sub-slice management network element.

[0287] S302: The sub-slice management network element creates a first sub-slice and allocates a sub-slice identifier NSSIDN to the first sub-slice.

[0288] S303: The sub-slice management network element sends the sub-slice identifier of the first sub-slice to the slice management network element.

[0289] S304: The slice management network element creates an interface object according to the sub-slice identifier in the first sub-slice and associates the interface object to the N3 interface of the user plane network element of the first sub-slice.

[0290] S305: The sub-slice management network element sends the network identifier and the first gateway information to the core network sub-slice management network element.

[0291] In some embodiments, the sub-slice management network element sends an interface object containing the network identifier and the first gateway information to the core network sub-slice management network element.

[0292] S306: The core network sub-slice management network element determines the user plane network element of the core network sub-slice according to the interface object.

[0293] S307: The network of the user plane network element of the core network sub-slice is created or modified.

[0294] In some embodiments, the core network sub-slice management network element determines the VNF instance information of the user plane network element of the core network sub-slice according to the sub-slice identifier, and according to the received network identifier, the core network sub-slice management network element requests the MANO to create or modify the network of the user plane network element.

[0295] S308: The sub-slice management network element sends the network identifier and the second gateway information to the bearer network sub-slice management network element.

[0296] S309: The bearer network sub-slice management network element determines the second port of the next hop gateway of the bearer network sub-slice according to the second gateway information.

[0297] S310: The bearer network sub-slice management network element configures the network information indicated by the network identifier for the second port.

[0298] Figure 8 This is another information transmission method provided by the embodiments of the present application, in which Figure 8In the shown application scenario, the user plane network element of the core network slice subnetwork is deployed in a virtualized manner, and the user plane network element of the core network slice subnetwork needs to pass through a gateway of a data center to be connected to an external network. The management service consumer is a sub-slice management network element.

[0299] In order to enable the data to have the same QoS when being transmitted in different subnetwork slices, the QoS mapping relationship needs to be configured after the connection of the subnetwork slice is established.

[0300] S401: The slice management network element sends a slice subnetwork creation request to the sub-slice management network element.

[0301] S402: The sub-slice management network element creates a first sub-slice and allocates a sub-slice identifier NSSIDN to the first sub-slice.

[0302] S403: The sub-slice management network element sends the sub-slice identifier of the first sub-slice to the slice management network element.

[0303] S404: The slice management network element creates an interface object according to the sub-slice identifier in the first sub-slice and associates the interface object to an N3 interface of a user plane network element of the first sub-slice.

[0304] S405: The sub-slice management network element sends the interface object to the core network sub-slice management network element.

[0305] In some embodiments, the interface object contains a network identifier, first gateway information, and a QoS mapping relationship.

[0306] S406: The core network sub-slice management network element determines a first port of a next hop gateway of the core network sub-slice according to the first gateway information contained in the interface object.

[0307] S407: The core network sub-slice management network element configures the network information indicated by the network identifier to the first port.

[0308] S408: The sub-slice management network element sends the network identifier and second gateway information to the bearer network sub-slice management network element.

[0309] S409: The bearer network sub-slice management network element determines a second port of a next hop gateway of the bearer network sub-slice according to the second gateway information.

[0310] S410: The bearer network sub-slice management network element configures the network information indicated by the network identifier to the second port.

[0311] S411: The sub-slice management network element sends the interface object and the NSSI DN of the user plane network element associated with the interface object to the core network sub-slice management network element.

[0312] In some embodiments, the interface object contains a QoS mapping relationship.

[0313] S412: The core network sub-slice management network element configures the QoS mapping relationship contained in the interface object on the user plane network element or the session management network element.

[0314] It should be understood that the session management network element is used to manage the transmission and reception of data on the user plane network element.

[0315] In some embodiments, the EMS configures the QoS mapping relationship at the session management network element of the core network sub-slice.

[0316] Figure 9 Fig. 1 shows a schematic diagram of an information transmission method provided by an embodiment of the present application, in which Figure 9 In the application scenario shown, the user plane network element of the core network slice subnetwork is deployed in a virtualized manner, and the user plane network element of the core network slice subnetwork needs to connect to an external network through a gateway of a data center. The management service consumer is a slice management network element.

[0317] S501: The slice management network element sends a slice subnetwork creation request to the sub-slice management network element.

[0318] S502: The sub-slice management network element creates a first sub-slice and allocates a sub-slice identifier NSSIDN to the first sub-slice.

[0319] S503: The sub-slice management network element sends the sub-slice identifier of the first sub-slice to the slice management network element.

[0320] S504: The slice management network element creates an interface object according to the sub-slice identifier in the first sub-slice, and associates the interface object to the N3 interface of the user plane network element of the first sub-slice.

[0321] S505: The slice management network element sends the configuration information to the core network sub-slice management network element.

[0322] In some embodiments, the configuration information contains a network identifier, first gateway information, and second gateway information.

[0323] S506: The core network sub-slice management network element determines the first port of the next hop gateway of the core network sub-slice according to the first gateway information in the configuration information.

[0324] S507: The core network sub-slice management network element configures the network information indicated by the network identifier for the first port.

[0325] S508: The slice management network element sends the configuration information to the bearer network sub-slice management network element.

[0326] S509: The bearer network sub-slice management network element determines the second port of the next hop gateway of the bearer network sub-slice according to the second gateway information in the configuration information.

[0327] S510: The bearer network sub-slice management network element configures network information indicated by the network identifier for the second port.

[0328] Figure 10 Fig. 2 shows another information transmission method provided by an embodiment of the present application. Figure 10 In the application scenario shown, the user plane network element of the core network slice subnetwork is deployed in a virtual manner, and the user plane network element of the core network slice subnetwork needs to pass through the gateway of the data center to be connected to an external network. The management service consumer is a slice management network element.

[0329] In order to enable data to have the same QoS when transmitted in different subnetwork slices, the QoS mapping relationship needs to be configured after the subnetwork slice is established.

[0330] S601: The slice management network element sends a slice subnetwork creation request to the sub-slice management network element.

[0331] S602: The sub-slice management network element creates a first sub-slice and allocates a sub-slice identifier NSSIDN to the first sub-slice.

[0332] S603: The sub-slice management network element sends the sub-slice identifier of the first sub-slice to the slice management network element.

[0333] S604: The slice management network element creates an interface object according to the sub-slice identifier in the first sub-slice and associates the interface object to the N3 interface of the user plane network element of the first sub-slice.

[0334] S605: The slice management network element sends configuration information to the core network sub-slice management network element.

[0335] In some embodiments, the configuration information contains a network identifier, first gateway information, and second gateway information.

[0336] S606: The core network sub-slice management network element determines the first port of the next hop gateway of the core network sub-slice according to the first gateway information in the configuration information.

[0337] S607: The core network sub-slice management network element configures network information indicated by the network identifier for the first port.

[0338] S608: The slice management network element sends configuration information to the bearer network sub-slice management network element.

[0339] S609: The bearer network sub-slice management network element determines the second port of the next hop gateway of the bearer network sub-slice according to the second gateway information in the configuration information.

[0340] S610: The bearer network sub-slice management network element configures network information indicated by the network identifier for the second port.

[0341] S611: The slice management network element sends the QoS mapping relationship and the NSSI DN of the user plane network element associated with the interface object to the core network sub-slice management network element.

[0342] S612: Core network sub-slice management network elements configure QoS mapping relationships on user plane network elements or session management network elements.

[0343] It should be understood that this session management network element is used to manage the sending and receiving of data on the user plane network element.

[0344] In some embodiments, the Network Element Management System (EMS) configures QoS mapping relationships for session management network elements in core network sub-slices.

[0345] Based on the same concept as the above method embodiments, this application also provides a communication device. This communication device can possess the functions of the management service consumer, core network sub-slice management service provider, and bearer network slice management service provider in the above method embodiments, and can be used to execute the steps performed by the functions of the management service consumer, core network slice management service provider, and bearer network slice management service provider in the above method embodiments. The functions can be implemented by hardware, or by software, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0346] In one possible implementation, such as Figure 11 The communication device 1100 shown can act as a management service consumer involved in the above method embodiments and perform the steps performed by the management service consumer in the above method embodiments.

[0347] like Figure 11 As shown, the communication device 1100 may include a communication module 1110 and a processing module 1120, which are coupled to each other.

[0348] Communication module 1110 can be used to support communication device 1100 in communication, for example, performing... Figure 4 , Figure 6 , Figure 7 , Figure 8 , Figure 9 ,and Figure 10 The sending and / or receiving actions performed by the management service consumer in S110, S130, S201, S203, S205, S208, S301, S303, S305, S308, S401, S403, S405, S408, S411, S501, S503, S505, S508, S601, S603, S605, S608, and S611.

[0349] The processing module 1120 can be configured to support the communication device 1100 to perform processing actions in the above method embodiments, for example, to perform the processing actions performed by the management service consumer in S202, S302, S402, S502 and S602 in Figure 6 , Figure 7 , Figure 8 , Figure 9 , and Figure 10 .

[0350] In another possible implementation, the communication device 1100 as shown in Figure 11 may act as a core network sub-slice management service provider involved in the above method embodiments, and perform the steps performed by the core network sub-slice management service provider in the above method embodiments.

[0351] As shown in Figure 11 , the communication device 1100 can include a communication module 1110 and a processing module 1120, which are coupled to each other.

[0352] The communication module 1110 can be configured to support the communication device 1100 to communicate, for example, to perform the sending and / or receiving actions performed by the core network sub-slice management service provider in S110, S121, S205, S305, S405, S411, S505, S605 and S611 in Figure 4 , Figure 5 , Figure 6 , Figure 7 , Figure 8 , Figure 9 , and Figure 10 .

[0353] The processing module 1120 can be configured to support the communication device 1100 to perform processing actions in the above method embodiments, for example, to perform the processing actions performed by the management service provider in S120, S122, S123, S206, S207, S306, S307, S406, S407, S412, S506, S507, S606, S607 and S612 in Figure 4 , Figure 5 , Figure 6 , Figure 7 , Figure 8 , Figure 9 , and Figure 10 .

[0354] In yet another possible implementation, the communication device 1100 as shown in Figure 11The illustrated communication apparatus 1100 can serve as a bearer network sub-slice management service provider involved in the above method embodiments, and perform steps performed by the bearer network sub-slice management service provider in the above method embodiments.

[0355] As shown in Figure 11 , the communication apparatus 1100 can include a communication module 1110 and a processing module 1120, which are coupled to each other.

[0356] The communication module 1110 can be configured to support the communication apparatus 1100 to communicate, for example, to perform the sending and / or receiving actions performed by the bearer network sub-slice management service provider in S130, S208, S308, S408, S508 and S608 of Figure 4 , Figure 6 , Figure 7 , Figure 8 , Figure 9 and Figure 10 .

[0357] The processing module 1120 can be configured to support the communication apparatus 1100 to perform processing actions in the above method embodiments, for example, to perform the processing actions performed by the bearer network sub-slice management service provider in S140, S209, S210, S309, S310, S409, S410, S509, S510, S609 and S610 of Figure 4 , Figure 6 , Figure 7 , Figure 8 , Figure 9 and Figure 10 .

[0358] Optionally, the communication apparatus 1100 can further include a storage module 1130 configured to store program codes and data of the communication apparatus 1100.

[0359] Figure 12 is a schematic block diagram of a communication device 1200 provided by an embodiment of the present application. As shown in the figure, the communication device 1200 includes at least one processor 1210 and a transceiver 1220. The processor 1210 is coupled to the memory and is configured to execute instructions stored in the memory to control the transceiver 1220 to transmit and / or receive signals.

[0360] Optionally, the communication device 1200 further includes a memory 1230 configured to store instructions.

[0361] In some embodiments, the processor 1210 and the memory 1230 can be combined into one processing device, and the processor 1210 is configured to execute the program codes stored in the memory 1230 to implement the above functions. In a specific implementation, the memory 1230 can also be integrated in the processor 1210, or be independent of the processor 1210.

[0362] In some embodiments, the transceiver 1220 can include a receiver (or receiver) and a transmitter (or transmitter).

[0363] The transceiver 1220 can further include an antenna, and the number of antennas can be one or more. The transceiver 1220 can be a communication interface or an interface circuit.

[0364] When the communication device 1200 is a chip, the chip includes a transceiver unit and a processing unit. The transceiver unit can be an input / output circuit or a communication interface, and the processing unit can be a processor or a microprocessor integrated on the chip or an integrated circuit.

[0365] In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in the processor or the instruction in the form of software. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware processor for execution, or executed by a combination of hardware and software modules in the processor. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, or other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method. To avoid repetition, it will not be described in detail here.

[0366] The embodiments of the present application also provide a computer readable storage medium, which stores computer instructions for implementing the method executed by the communication device in the above method embodiments.

[0367] For example, the computer program is executed by the computer, so that the computer can implement the method executed by the communication device in the above method embodiments.

[0368] The explanations and beneficial effects of the related contents in any of the above provided devices can refer to the corresponding method embodiments provided above, and will not be described here.

[0369] Those skilled in the art can clearly understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0370] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0371] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0372] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0373] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically independently, or two or more units can be integrated into one unit.

[0374] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts that contribute to the prior art or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0375] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for information transmission, characterized in that, include: The management service consumer sends a network identifier and first gateway information to the management service provider of the core network subslice, wherein the first gateway information is used to indicate the next-hop gateway of the core network subslice; The management service consumer sends the network identifier and second gateway information to the management service provider of the bearer network sub-slice. The second gateway information is used to indicate the next-hop gateway of the bearer network sub-slice, and the network identifier is used to indicate the network information configured for the core network sub-slice and the bearer network sub-slice.

2. The method according to claim 1, characterized in that, The transmission of the network identifier and the first gateway information includes: Send an interface object, the interface object including the network identifier and the first gateway information, the interface object being associated with the interface of the user plane network element of the core network sub-slice.

3. The method according to claim 1, characterized in that, The method further includes the management service consumer sending a QoS mapping relationship to the management service provider of the core network sub-slice, wherein the QoS mapping relationship is a mapping relationship between the QoS identifier of the core network sub-slice and the QoS identifier of the bearer network slice.

4. The method according to claim 3, characterized in that, Sending the QoS mapping relationship includes: sending an interface object, the interface object including the QoS mapping relationship, and the interface object being associated with the interface of the user plane network element of the core network sub-slice.

5. The method according to any one of claims 1 to 4, characterized in that, The transmission of the network identifier and the first gateway information includes: Send configuration information; Sending the network identifier and second gateway information includes: Send the configuration information; The configuration information includes the network identifier, the first gateway information, and the second gateway information.

6. The method according to claim 3 or 4, characterized in that, Before sending the QoS mapping relationship, the method further includes: The management service consumer obtains information indicating that the connection between the core network sub-slice and the bearer network slice is complete.

7. A method for transmitting information, characterized in that, include: The core network subslice management service provider receives a network identifier and first gateway information, wherein the first gateway information is used to indicate the next-hop gateway of the core network subslice, and the network identifier is used to indicate the network information configured for the core network subslice. The management service provider of the core network sub-slice configures the network information for the core network sub-slice.

8. The method according to claim 7, characterized in that, The configuration of the network information includes: Configure the network information on the first port of the next-hop gateway of the core network sub-slice; or, Based on the VNF information of the user plane network element in the core network sub-slice and the network information, the network of the user plane network element is created or modified.

9. The method according to claim 7 or 8, characterized in that, The receiving network identifier and first gateway information include: A receiving interface object is provided, the interface object including the network identifier and the first gateway information, and the interface object is associated with the interface of the user plane network element of the core network sub-slice.

10. The method according to claim 7 or 8, characterized in that, The receiving network identifier and first gateway information include: Receive configuration information, which includes the network identifier, first gateway information, and second gateway information, wherein the second gateway information is used to indicate the next-hop gateway of the carrying network sub-slice.

11. The method according to claim 7 or 8, characterized in that, The method further includes the management service provider of the core network sub-slice receiving a QoS mapping relationship, wherein the QoS mapping relationship is a mapping relationship between the QoS identifier of the core network sub-slice and the QoS identifier of the bearer network sub-slice.

12. The method according to claim 11, characterized in that, The method further includes: The management service provider of the core network sub-slice configures the QoS mapping relationship for the core network sub-slice.

13. The method according to claim 12, characterized in that, The configuration of the QoS mapping relationship includes: The management service provider of the core network sub-slice configures the QoS mapping relationship in the user plane network element and / or session management network element, and the session management network element is used to manage the user plane network element.

14. The method according to claim 12 or 13, characterized in that, The received QoS mapping relationship includes: A receiving interface object is provided, the interface object including the QoS mapping relationship, and the interface object is associated with the interface of the user plane network element of the core network sub-slice.

15. A method for transmitting information, characterized in that, include: The management service provider of the bearer network subslice receives network identifier and second gateway information, the second gateway information being used to indicate the next-hop gateway of the bearer network slice, and the network identifier being used to indicate the network information configured for the bearer network slice; The management service provider of the bearer network sub-slice configures the network information for the bearer network sub-slice.

16. The method according to claim 15, characterized in that, The configuration of the network information includes: Configure the network identifier on the second port of the next-hop gateway of the carrying network subslice.

17. The method according to claim 15 or 16, characterized in that, The received network identifier and second gateway information include: Receive configuration information, which includes the network identifier, the second gateway information, and the first gateway information, wherein the first gateway information is used to indicate the next-hop gateway of the core network subslice.

18. A method for transmitting information, characterized in that, include: The management service consumer sends a network identifier and first gateway information to the management service provider of the core network subslice, wherein the first gateway information is used to indicate the next-hop gateway of the core network subslice; The management service consumer sends the network identifier and second gateway information to the management service provider of the bearer network subslice. The second gateway information is used to indicate the next-hop gateway of the bearer network subslice, and the network identifier is used to indicate the network information configured in the core network subslice and the bearer network subslice. The management service provider of the core network sub-slice configures the core network slice according to the network identifier and the first gateway information; The management service provider of the bearer network sub-slice configures the bearer network slice according to the network identifier and the second gateway information.

19. The method according to claim 18, characterized in that, The method further includes: The management service consumer sends the Quality of Service (QoS) mapping relationship to the core network subslice; The management service provider of the core network sub-slice configures the QoS mapping relationship for the core network sub-slice; The QoS mapping relationship is the mapping relationship between the QoS identifier of the core network sub-slice and the QoS identifier of the bearer network sub-slice.

20. A communication system, characterized in that, This includes management service consumers, core network sub-slice management service providers, and bearer network sub-slice management service providers. The management service consumer is used to perform the method as described in any one of claims 1 to 6, the management service provider of the core network sub-slice is used to perform the method as described in any one of claims 7 to 14, and the management service provider of the bearer network slice is used to perform the method as described in any one of claims 15 to 17.

21. A communication device, characterized in that, Includes modules for implementing the method as described in any one of claims 1 to 6, 7 to 14, or 15 to 17.

22. A communication device, characterized in that, include: A processor for executing computer instructions stored in memory to cause the apparatus to perform the method as claimed in any one of claims 1 to 6, 7 to 14, or 15 to 17.

23. A computer-readable storage medium, characterized in that, It contains a computer program that is executed by a computer to implement the method as described in any one of claims 1 to 6, 7 to 14, or 15 to 17.

24. A computer program product, characterized in that, The computer program product includes computer program code, and when the computer program code is run on a computer, the method as described in any one of claims 1 to 6, 7 to 14, or 15 to 17 is performed.

25. A chip, characterized in that, include: A processor for reading instructions stored in a memory, and when the processor executes the instructions, causing the chip to implement the method of any one of claims 1 to 6, 7 to 14, or 15 to 17.

Images