WO2019062634A1 - 通信方法及装置 - Google Patents

通信方法及装置 Download PDF

Info

Publication number
WO2019062634A1
WO2019062634A1 PCT/CN2018/106653 CN2018106653W WO2019062634A1 WO 2019062634 A1 WO2019062634 A1 WO 2019062634A1 CN 2018106653 W CN2018106653 W CN 2018106653W WO 2019062634 A1 WO2019062634 A1 WO 2019062634A1
Authority
WO
WIPO (PCT)
Prior art keywords
network slice
network
identifier
instance
management function
Prior art date
Application number
PCT/CN2018/106653
Other languages
English (en)
French (fr)
Inventor
杨水根
孙文琦
陆伟
谭巍
冯珍妮
蒋若冰
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019062634A1 publication Critical patent/WO2019062634A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a communication method and apparatus.
  • next generation mobile communication systems such as fifth-generation (5G) mobile communication systems
  • the network is abstracted as a "network slice.”
  • a network slice satisfies the connection communication service requirements of a certain class or a use case.
  • the entire 5G network consists of a large number of network slices that satisfy different connection capabilities.
  • a unified network platform that utilizes dynamic, secure network slicing to support different functions and quality of service (QoS) connected communication services.
  • QoS quality of service
  • a network slice instance is an instantiation of a network slice, that is, a real-running logical network that satisfies certain network characteristics or service requirements.
  • a network slice instance may provide one or more services.
  • the network slice instance may be created by a network slice management system, as shown in the structure of the network slice management system shown in FIG. 1.
  • the system includes a communication service management function (CSMF) entity 11, and a network slice management function (network slice).
  • CSMF, NSMF, and NSSMF are connected to each other.
  • a network slice management system may create multiple network slice instances and manage them at the same time, for example, modify, terminate, etc. multiple network slice instances.
  • a network slice instance includes a network slice subnet instance (NSSI) and/or a network function.
  • NSSI network slice subnet instance
  • the present application provides a communication method and apparatus for efficiently performing network slice instantiation or network slice subnet instantiation, thereby saving signaling overhead during instantiation.
  • An aspect of the present application provides a communication method, including: a first network device sending a first request message to a second network device, where the first request message is used to request to perform at least one network slice or at least one network slice subnet Instantiating, the first request message includes an identifier of the at least one network slice instance and an identifier of the at least one network slice specification, or the first request message includes an identifier of the at least one network slice subnet instance and An identifier of the at least one network slice subnet specification; the first network device receives a first response message from the second network device, the first response message being used to indicate that the at least one network slice is instantiated As a result, or the first response message is used to indicate a result of instantiating the at least one network slice subnet.
  • the first network device carries the identifier of the slice instance and the slice specification identifier in the request message
  • the second network device may obtain the pre-stored slice template according to the identifier of the slice instance, and combine the slice specification identifier to perform an instance of the slice.
  • the signaling overhead in the instantiation process is greatly saved.
  • each network slice specification represents at least one of the following parameters for each network slice: the structure, configuration, and network capabilities of the network slice; or each network slice subnet specification represents each At least one of the following parameters of the network slicing subnet: the structure, configuration, and network capabilities of the network slicing subnet.
  • the first network device and the second network device pre-store a network slice template or a network slice subnet template, where the network slice template includes a network slice specification corresponding to one or more network slices; the network slice subnet The template contains network slice subnet specifications corresponding to one or more network slice subnets.
  • the first request message further includes an identifier of the reused at least one network slice instance; or the first request message further includes an identifier of the reused at least one network slice subnet instance.
  • the second network device does not need to re-find the structure, configuration, network capability, etc. of the network slice corresponding to the identifier of the network slice specification in the network slice template to instantiate the network slice, but adopts the already An instantiated network slice instance.
  • the second network device may correspond to the identifier of the network slice instance carried in the first request message.
  • the second network device does not need to re-find the structure, configuration, network capability, and the like of the network slice subnet corresponding to the identifier of the network slice subnet specification in the network slice subnet template to instantiate the network slice subnet. Instead, use the network sliced subnet instance that has been instantiated.
  • the second network device may correspond to the identifier of the network slice subnet instance carried in the first request message.
  • the first response message includes at least one of the following information: at least one bit information used to indicate the at least one network slice instantiation result, or the at least one network slice life An identifier of the periodic operation event; or the first response message includes at least one of the following information: at least one bit information used to indicate the at least one network slice subnet instantiation result, or the first response message includes An identifier of the at least one network slice subnet lifecycle operation event.
  • the first network device is a communication service management function or a device having a communication service management function
  • the second network device is a network slice management function or a device having a network slice management function
  • the first network device is a communication service management function or a device having a communication service management function
  • the second network device is a network slice subnet management function or a device having a network slice subnet management function
  • the first network The device is a network slice management function or a device having a network slice management function
  • the second network device is a network slice subnet management function or a device having a network slice subnet management function.
  • a communication device having a function of implementing the behavior of a communication device in the above method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communication device includes: a sending unit, configured to send a first request message to the second network device, where the first request message is used to request to perform at least one network slice or at least one network slice subnet Instantiating, the first request message includes an identifier of the at least one network slice instance and an identifier of the at least one network slice specification, or the first request message includes an identifier of the at least one network slice subnet instance and An identifier of the at least one network slice subnet specification, a receiving unit, configured to receive a first response message from the second network device, where the first response message is used to indicate a result of the at least one network slice instantiation Or the first response message is used to indicate a result of instantiating the at least one network slice subnet.
  • a sending unit configured to send a first request message to the second network device, where the first request message is used to request to perform at least one network slice or at least one network slice subnet Instantiating, the first request message includes an identifier of the at least one network slice instance and an identifie
  • the communication device includes: a receiver, a transmitter, a memory, and a processor; wherein the memory stores a set of program codes, and the processor is configured to invoke the storage in the memory
  • the program code is configured to: control the transmitter to send a first request message to the second network device, where the first request message is used to request instantiation of at least one network slice or at least one network slice subnet, where A request message includes an identifier of the at least one network slice instance and an identifier of the at least one network slice specification, or the first request message includes an identifier of the at least one network slice subnet instance and the at least one network slice An identifier of a subnet specification, the receiver is configured to receive a first response message from the second network device, where the first response message is used to indicate a result of the at least one network slice instantiation, or the first The response message is used to indicate a result of instantiating the at least one network slice subnet.
  • the principle and the beneficial effects of the device can be referred to the method embodiments of the foregoing possible communication devices and the beneficial effects thereof. Therefore, the implementation of the device can refer to the implementation of the method, and the repetition is not Let me repeat.
  • a communication method including: receiving, by a second network device, a first request message from a first network device, where the first request message is used to request at least one network slice or at least one network slice The network is instantiated, the first request message includes an identifier of the at least one network slice instance and an identifier of the at least one network slice specification, or the first request message includes the at least one network slice subnet instance And an identifier of the at least one network slice subnet specification; the second network device sends a first response message to the first network device, where the first response message is used to indicate that the at least one network slice is instantiated The result, or the first response message is used to indicate a result of instantiating the at least one network slice subnet.
  • the first network device carries the identifier of the slice instance and the slice specification identifier in the request message
  • the second network device may obtain the pre-stored slice template according to the identifier of the slice instance, and combine the slice specification identifier to perform an instance of the slice.
  • the signaling overhead in the instantiation process is greatly saved.
  • each network slice specification represents at least one of the following parameters for each network slice: the structure, configuration, and network capabilities of the network slice; or each network slice subnet specification represents each At least one of the following parameters of the network slicing subnet: the structure, configuration, and network capabilities of the network slicing subnet.
  • the first network device and the second network device pre-store a network slice template or a network slice subnet template, where the network slice template includes a network slice specification corresponding to one or more network slices; the network slice subnet The template contains network slice subnet specifications corresponding to one or more network slice subnets.
  • the first request message further includes an identifier of the reused at least one network slice instance; or the first request message further includes an identifier of the reused at least one network slice subnet instance.
  • the second network device does not need to re-find the structure, configuration, network capability, etc. of the network slice corresponding to the identifier of the network slice specification in the network slice template to instantiate the network slice, but adopts the already An instantiated network slice instance.
  • the second network device may correspond to the identifier of the network slice instance carried in the first request message.
  • the second network device does not need to re-find the structure, configuration, network capability, and the like of the network slice subnet corresponding to the identifier of the network slice subnet specification in the network slice subnet template to instantiate the network slice subnet. Instead, use the network sliced subnet instance that has been instantiated.
  • the second network device may correspond to the identifier of the network slice subnet instance carried in the first request message.
  • the first response message includes at least one of the following information: at least one bit information used to indicate the at least one network slice instantiation result, or the at least one network slice life An identifier of the periodic operation event; or the first response message includes at least one of the following information: at least one bit information used to indicate the at least one network slice subnet instantiation result, or the first response message includes An identifier of the at least one network slice subnet lifecycle operation event.
  • the first network device is a communication service management function or a device having a communication service management function
  • the second network device is a network slice management function or a device having a network slice management function
  • the first network device is a communication service management function or a device having a communication service management function
  • the second network device is a network slice subnet management function or a device having a network slice subnet management function
  • the first network The device is a network slice management function or a device having a network slice management function
  • the second network device is a network slice subnet management function or a device having a network slice subnet management function.
  • a communication device having a function of implementing the behavior of a communication device in the above method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communications apparatus includes: a receiving unit, configured to receive a first request message from a first network device, where the first request message is used to request to at least one network slice or at least one network slice subnet Instantiating, the first request message includes an identifier of the at least one network slice instance and an identifier of the at least one network slice specification, or the first request message includes an identifier of the at least one network slice subnet instance And an identifier of the at least one network slice subnet specification; a sending unit, configured to send a first response message to the first network device, where the first response message is used to indicate a result of instantiating the at least one network slice Or the first response message is used to indicate a result of instantiating the at least one network slice subnet.
  • the communication device includes: a receiver, a transmitter, a memory, and a processor; wherein the memory stores a set of program codes, and the processor is configured to invoke the storage in the memory Program code for controlling the receiver to receive a first request message from a first network device, the first request message for requesting instantiation of at least one network slice or at least one network slice subnet,
  • the first request message includes an identifier of the at least one network slice instance and an identifier of the at least one network slice specification, or the first request message includes an identifier of the at least one network slice subnet instance and the at least one network An identifier of the sliced subnet specification
  • the controller is configured to send a first response message to the first network device, where the first response message is used to indicate a result of the at least one network slice instantiation, or the first The response message is used to indicate a result of instantiating the at least one network slice subnet.
  • the principle and the beneficial effects of the device can be referred to the method embodiments of the foregoing possible communication devices and the beneficial effects thereof. Therefore, the implementation of the device can refer to the implementation of the method, and the repetition is not Let me repeat.
  • a communication method including: a first network device sending a first request message to a second network device, where the first request message includes an identifier of at least one network slice template or at least one network slice An identifier of the subnet template; the first network device receives a first response message from the second network device, where the first response message includes an identifier of the at least one network slice instance or at least one network slice subnet instance Logo.
  • the identifier of the at least one network slice instance is created according to the at least one network slice template, and the identifier of the at least one network slice subnet instance is according to the at least one network slice subnet template create.
  • the first network device and the second network device have previously saved the network slice template or the network slice subnet template, and the network slice template is uniquely identified by the identifier of the network slice template, and the network slice subnet template adopts the network slice.
  • the identity of the subnet template is uniquely identified.
  • the first request message further includes a name of the customized at least one network slice instance or a name of the at least one network slice subnet instance, wherein the customized at least one network slice instance The name corresponds to the identifier of the at least one network slice instance, and the name of the customized at least one network slice subnet instance corresponds to the identifier of the at least one network slice subnet instance.
  • the custom name is the name defined by the user according to personal usage habits or preferences.
  • the ID of the subnet instance This makes the name of the instance easy to remember.
  • the first network device is a communication service management function or a device having a communication service management function
  • the second network device is a network slice management function or a device having a network slice management function
  • the first network device is a communication service management function or a device having a communication service management function
  • the second network device is a network slice subnet management function or a device having a network slice subnet management function
  • the first network The device is a network slice management function or a device having a network slice management function
  • the second network device is a network slice subnet management function or a device having a network slice subnet management function.
  • a communication device having a function of implementing the behavior of a communication device in the above method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communications apparatus includes: a sending unit, configured to send a first request message to the second network device, where the first request message includes an identifier of the at least one network slice template or at least one network slice An identifier of the network template, configured to receive a first response message from the second network device, where the first response message includes an identifier of the at least one network slice instance or an identifier of at least one network slice subnet instance .
  • the communication device includes: a receiver, a transmitter, a memory, and a processor; wherein the memory stores a set of program codes, and the processor is configured to invoke the storage in the memory
  • the program code is configured to: control the transmitter to send a first request message to the second network device, where the first request message includes an identifier of the at least one network slice template or an identifier of the at least one network slice subnet template;
  • the receiver receives a first response message from the second network device, the first response message including an identity of the at least one network slice instance or an identification of at least one network slice subnet instance.
  • the principle and the beneficial effects of the device can be referred to the method embodiments of the foregoing possible communication devices and the beneficial effects thereof. Therefore, the implementation of the device can refer to the implementation of the method, and the repetition is not Let me repeat.
  • a communication method comprising: receiving, by a second network device, a first request message from a first network device, where the first request message includes an identifier of at least one network slice template or at least one network An identifier of the sliced subnet template; the second network device sends a first response message to the first network device, where the first response message includes an identifier of the at least one network slice instance or at least one network slice subnet instance logo.
  • the identifier of the at least one network slice instance is created according to the at least one network slice template, and the identifier of the at least one network slice subnet instance is according to the at least one network slice subnet template create.
  • the first network device and the second network device have previously saved the network slice template or the network slice subnet template, and the network slice template is uniquely identified by the identifier of the network slice template, and the network slice subnet template adopts the network slice.
  • the identity of the subnet template is uniquely identified.
  • the first request message further includes a name of the customized at least one network slice instance or a name of the at least one network slice subnet instance, wherein the customized at least one network slice instance The name corresponds to the identifier of the at least one network slice instance, and the name of the customized at least one network slice subnet instance corresponds to the identifier of the at least one network slice subnet instance.
  • the custom name is the name defined by the user according to personal usage habits or preferences.
  • the ID of the subnet instance This makes the name of the instance easy to remember.
  • the first network device is a communication service management function or a device having a communication service management function
  • the second network device is a network slice management function or a device having a network slice management function
  • the first network device is a communication service management function or a device having a communication service management function
  • the second network device is a network slice subnet management function or a device having a network slice subnet management function
  • the first network The device is a network slice management function or a device having a network slice management function
  • the second network device is a network slice subnet management function or a device having a network slice subnet management function.
  • a communication device having a function of implementing the behavior of a communication device in the above method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the communications apparatus includes: a receiving unit, configured to receive a first request message from a first network device, where the first request message includes an identifier of at least one network slice template or at least one network slice An identifier of the subnet template, where the sending unit is configured to send a first response message to the first network device, where the first response message includes an identifier of the at least one network slice instance or an identifier of at least one network slice subnet instance .
  • the communication device includes: a receiver, a transmitter, a memory, and a processor; wherein the memory stores a set of program codes, and the processor is configured to invoke the storage in the memory
  • the program code is configured to: control the receiver to receive a first request message from the first network device, where the first request message includes an identifier of the at least one network slice template or an identifier of the at least one network slice subnet template; And controlling the transmitter to send a first response message to the first network device, where the first response message includes an identifier of the at least one network slice instance or an identifier of at least one network slice subnet instance.
  • the principle and the beneficial effects of the device can be referred to the method embodiments of the foregoing possible communication devices and the beneficial effects thereof. Therefore, the implementation of the device can refer to the implementation of the method, and the repetition is not Let me repeat.
  • Yet another aspect of the present application provides a communication system including the above-described first network device and second network device.
  • Yet another aspect of the present application provides a computer readable storage medium having stored therein instructions that, when executed on a computer, cause the computer to perform the methods described in the above aspects.
  • Yet another aspect of the present application provides a communication chip in which instructions are stored that, when run on a network device or terminal device, cause the computer to perform the methods described in the various aspects above.
  • Yet another aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the various aspects above.
  • FIG. 1 is a schematic structural diagram of a network slice management system
  • FIG. 2 is a schematic diagram of an interaction process of a communication method according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of an interaction process of a communication method between CSMF and NSMF;
  • FIG. 4 is a schematic diagram of an interaction process of a communication method between NSMF and NSSMF;
  • FIG. 5 is a schematic diagram of an interaction process of a communication method between CSMF and NSSMF;
  • FIG. 6 is a schematic diagram of an interaction process of another communication method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram of an interaction process of another communication method between NSMF and NSSMF;
  • FIG. 8 is a schematic diagram of an interaction process of another communication method between CSMF and NSMF;
  • FIG. 9 is a schematic diagram of an interaction process of another communication method between CSMF and NSSMF;
  • FIG. 10 is a schematic structural diagram of a communication apparatus according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of another communication apparatus according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of still another communication apparatus according to an embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of still another communication apparatus according to an embodiment of the present invention.
  • FIG. 14 is a hardware structural diagram of a communication device according to an embodiment of the present invention.
  • the CSMF is mainly responsible for converting the communication service related requirements of the operator and/or the third party customer into the relevant requirements of the network slice, and passing the NSMF and
  • the interface sends the network slice request (such as creating, terminating, modifying the network slice instance request, etc.) to the NSMF, and obtains the management data (such as performance, fault data, etc.) of the network slice from the NSMF, and generates and runs on the network slice instance.
  • the management data of the communication service receives the subscription requirements of the management data of the network slice management data and/or the communication service by the operator and/or the third party customer.
  • CSMF is mainly responsible for translating the communication service related requirements of operators and/or third-party customers into the relevant requirements of the network slicing subnet, and sending the demand for the network slicing subnet to the NSSMF through the interface with the NSSMF (such as creating, terminating, and modifying the network slice subnet instance request, etc., acquiring management data (such as performance, fault data, etc.) of the network slice subnet from the NSSMF, and generating management data of the communication service running on the network slice subnet instance. Receiving the subscription requirements of the management data of the network slice subnet management data and/or the communication service by the operator and/or the third party customer.
  • the NSMF is mainly responsible for receiving the network slice related requirements sent by the CSMF, managing the life cycle, performance, and faults of the network slice instance, orchestrating the composition of the network slice instance, and decomposing the network slice instance requirements for each network sliced subnet instance and/or
  • the network function requires sending a network slice subnet instance management request to each NSSMF.
  • the NSSMF is mainly responsible for receiving the network slicing subnet requirements sent by the NSMF or the CSMF, managing the network slicing subnet instance, and compiling the composition of the network slicing subnet instance.
  • Network slice A different logical network that is customized according to different service requirements.
  • the network slice can be a complete network including a terminal device, an access network, a transmission network, a core network, and an application server, and can provide a complete telecommunication service with certain network capabilities; the network slice can also be the above terminal device and access network.
  • Network slice instance It is an instantiation of a network slice, that is, a real-running logical network that satisfies certain network characteristics or service requirements.
  • a network slice instance can provide one or more services.
  • the network slice instance can be created by the network slice management system.
  • a network slice management system may create multiple network slice instances and manage them at the same time, for example, modify, terminate, etc. multiple network slice instances. When multiple network slice instances coexist, some network resources and network functions can be shared between network slice instances.
  • a complete network slicing instance can provide complete end-to-end network services, while a network slicing instance consists of network slice subnet instances (NSSI) and/or network functions.
  • Network functions may include physical network functions and/or virtual network functions. The following describes physical network functions and/or virtual network functions collectively as network functions.
  • Network slice template describes the structure of a network slice (including components (such as: network slice subnet and / or network function description, etc.) and the connection between each component), configuration, Network capabilities, etc.
  • the network slice template contains network slice specifications corresponding to one or more network slices.
  • Each network slice specification corresponds to an identifier of a network slice specification.
  • the network slice specification corresponding to each network slice represents the structure, configuration, network capability, etc. of the network slice, for example, a key performance indicator (SLA) or a key performance indicator (key performance) representing the network slice.
  • SLA key performance indicator
  • KPI key performance indicator
  • the indicator, KPI KPI
  • the network slice template is also referred to as a network slice descriptor (NSD).
  • Network slice subnet instance The network slice subnet instance does not need to provide a complete end-to-end network service.
  • the network slice subnet instance can be the network function of the same device vendor in the network slice instance.
  • the set may also be a collection of network functions divided by domain, such as a core network network slice subnet instance, an access network network slice subnet instance, or a collection consisting of other ways such as deployment location.
  • a network sliced subnet instance may be shared by multiple network slice instances. The concept of a network slice subnet instance is proposed to facilitate network slice management system management.
  • Network slice subnet template describes the structure of the network slice subnet (including the constituent elements and the connections between the constituent elements), configuration, network capabilities, and so on.
  • the network slice subnet template contains the network slice subnet specifications corresponding to one or more network slice subnets.
  • Each network slice subnet specification corresponds to an identifier of a network slice subnet specification.
  • the network slice subnet specification corresponding to each network slice subnet represents the structure, configuration, network capability, etc. of the network slice subnet, for example, represents the SLA or KPI parameters of the network slice subnet, and provides the SLA. Or the structure, configuration, etc. of the network slice subnet required for the KPI parameter.
  • the network slice subnet template is also referred to as a network slice subnet descriptor (NSSD).
  • system and “network” in the embodiments of the present invention may be used interchangeably.
  • Multiple means two or more, and in view of this, "a plurality” may also be understood as “at least two” in the embodiment of the present invention.
  • the character "/” unless otherwise specified, generally indicates that the contextual object is an "or" relationship.
  • the embodiment of the present invention provides a communication method, where the first network device carries the identifier of the slice instance (for example, an NSI ID or an NSSI ID) and a slice specification identifier (for example, an NS flavor ID or an NSS flavor ID) in the request message.
  • the network device can obtain the pre-stored slice template according to the identifier of the slice instance, and combine the slice specification identifier to instantiate the slice, which greatly saves the signaling overhead in the instantiation process.
  • FIG. 2 is a schematic diagram of an interaction process of a communication method according to an embodiment of the present invention, where the method may include the following steps:
  • the first network device sends a first request message to the second network device.
  • the first request message includes an identifier of the at least one network slice instance and at least one network slice specification identifier (flavor ID); or the first request message includes an identifier of the at least one network slice subnet instance and the at least one network slice The logo of the network specification.
  • the identifier of the network slice instance may be pre-stored in the first network device or the second network device, so that the second network device can know that the need to instantiate when obtaining the identifier of the network slice instance according to the first request message. Which network slice instance is there.
  • the identification of the network slice instance may also be created according to the method shown in the embodiment of FIG. 8 below.
  • the identifier of the network slice subnet instance may be pre-stored in the first network device or the second network device, so that the second network device can obtain the identifier of the network slice subnet instance according to the first request message. Know which network slice subnet instance you need to instantiate.
  • the identity of the network slice subnet instance may also be created according to the method shown in the embodiment of FIG. 7 below.
  • the first request message is used to request instantiation of the at least one network slice or the at least one network slice subnet.
  • the first request message may be referred to as a network slice instantiation request message, or a network slice subnet instantiation request message, or other name, which is not limited herein.
  • the network slice template includes network slice specifications corresponding to one or more network slices.
  • the network slice specification represents the structure, configuration, network capabilities, etc. of the corresponding network slice, for example, the SLA or KPI parameters representing the corresponding network slice, and the structure, configuration, etc. of the network slice required to provide the SLA or KPI parameters.
  • the network slice specification corresponding to each network slice corresponds to an identifier of a network slice specification.
  • the network slice subnet template includes a network slice subnet specification corresponding to one or more network slice subnets.
  • the network slice subnet specification represents the structure, configuration, network capability, etc. of the corresponding network slice subnet, for example, the SLA or KPI parameters representing the network slice subnet, and the network required to provide the SLA or KPI parameters.
  • the network slice subnet specification corresponding to each network slice subnet corresponds to the identifier of a network slice subnet specification.
  • the second network device receives the first request message, and the second network device sends a first response message to the first network device.
  • the first response message is used to indicate an instantiation result of the at least one network slice or the at least one network slice subnet.
  • the first response message may be referred to as a network slice instantiation response message, or a network slice subnet instantiation response message, or other name, which is not limited herein.
  • the first network device receives the first response message.
  • the first network device can learn whether the network slice instantiation or the network slice subnet instantiation is successful according to the first response message; if not, a new request message can be initiated.
  • the network slice template is pre-stored in the first network device and the second network device, and the identifier of the network slice instance is created based on the network slice template, and therefore, when the network slice is instantiated According to the identifier of the network slice specification carried in the first request message, the structure, configuration, network capability, and the like of the network slice corresponding to the identifier of the network slice specification may be found in the network slice template, thereby performing network slice instantiation. .
  • the network slice subnet template is pre-stored in the first network device and the second network device, and the identifier of the network slice subnet instance is created based on the network slice subnet template, and therefore, the network is performed.
  • the network slicing subnet corresponding to the identifier of the network slicing subnet specification may be found in the network slicing subnet template according to the identifier of the network slicing subnet specification carried in the first request message. Structure, configuration, network capabilities, etc., to instantiate the network slice subnet.
  • the first request message may further include an identifier of the at least one network slice instance that is reused.
  • the second network device does not need to re-find the structure, configuration, network capability, and the like of the network slice corresponding to the identifier of the network slice specification in the network slice template to perform network slice instantiation, but adopts The network slice instance that has been instantiated, the network slice instance that has been instantiated is substantially consistent with the structure, configuration, network capability, and the like of the network slice that the current second network device needs to instantiate.
  • the second network device may correspond to the identifier of the network slice instance carried in the first request message, and the existing network slice instance corresponds to two identifiers, that is, the reused network slice instance. The identity of the network slice instance that the current second network device needs to instantiate.
  • the first request message may further include an identifier of the at least one network slice subnet instance that is reused.
  • the second network device does not need to re-find the structure, configuration, network capability, and the like of the network slice subnet corresponding to the identifier of the network slice subnet specification in the network slice subnet template to perform network slice.
  • the subnet is instantiated, but the network slicing subnet instance that has been instantiated, the structure, configuration, network capability, etc. of the network slicing subnet instance that has been instantiated and the network slicing subnet that the current second network device needs to instantiate Basically consistent.
  • the second network device may correspond to the identifier of the network slice subnet instance carried in the first request message, and the existing network slice subnet instance corresponds to two identifiers. That is, the identifier of the existing network slice subnet instance and the identifier of the network slice instance that the current second network device needs to be instantiated.
  • the first network device may be a CSMF entity or other device having a communication service management function
  • the second network device may be an NSMF entity or a device having other network slice management functions.
  • the NSMF instantiates the network slice corresponding to the NSI ID if the first request message includes the NSI ID and the NS flavor ID.
  • the constituent elements for example, the network slice subnet
  • related resources for example, computing resources, storage resources, transmission resources, etc.
  • the network slicing capability represented by the ID (for example, SLA or KPI). If the first request message includes the reused network slice instance, the reused network slice instance is reconfigured to satisfy the network slicing capability represented by the NS flavor ID.
  • FIG. 3 illustrates the communication method proposed by the present application by using the first network device as the CSMF and the second network device as the NSMF.
  • the method may include the following steps:
  • the CSMF sends a first request message to the NSMF.
  • the first request message may be referred to as a network slice instantiation request message.
  • the first request message includes an identifier of a network slice instance, such as an NSI ID, and an identifier NS flavor ID further including a network slice specification.
  • an identification of the reused network slice instance may also be included.
  • the NSMF receives the first request message and sends a first response message to the CSMF.
  • the network slice template is pre-stored in the CSMF and the NSMF, and the identifier of the network slice instance is created based on the network slice template. Therefore, when the network slice is instantiated, according to the identifier of the network slice specification carried in the first request message, The structure, configuration, network capability, and the like of the network slice corresponding to the identifier of the network slice specification are found in the network slice template, thereby performing network slice instantiation.
  • the CSMF receives the first response message. Based on the first response message, the CSMF can learn whether the network slice instantiation is successful; if not, a new request message can be initiated.
  • the first response message may be referred to as a network slice instantiation response message.
  • the first response message is used to indicate the result of instantiation of the network slice.
  • the NSMF instantiates the network slice according to the parameter information in the first request message, and sends a first response message to the CSMF.
  • the first response message is used to indicate the result of instantiation of the network slice.
  • the first response message may include at least one bit information. For example, 1 bit is used to indicate the result of instantiation of the network slice, "0" indicates that the network slice is instantiated, "1" indicates that the network slice is instantiated successfully, or "0" indicates that the network slice is instantiated successfully, and "1" indicates that the network slice is successful. The instantiation was successful.
  • the first response message may include a life cycle operation occurrence id, where the identifier is used to indicate that the NSMF has a lifecycle operation event of network slice instantiation, for example, This ID is an event number.
  • the first network device may be an NSMF entity or a device having a network slice management function
  • the second network device may be an NSSMF entity or a device having a network slice subnet management function
  • the first network The device may be a CSMF entity or a device having a communication service management function
  • the second network device may be an NSSMF entity or a device having a network slice subnet management function.
  • the constituent elements (for example, network functions) of the network slice subnet corresponding to the NSS flavor ID are created and configured with related resources (for example, computing resources, storage resources, transmission resources, etc.) to satisfy the NSS flavor.
  • the network slice subnet capability represented by the ID (for example, SLA or KPI). If the first request message includes the reused network slice subnet instance, the reused network slice subnet instance is reconfigured to meet the network slice subnet capability represented by the NSS flavor ID.
  • the first network device is an NSMF
  • the second network device is an NSSMF.
  • the communication method proposed by the present application is described. The method may include the following steps:
  • the NSMF sends a first request message to the NSSMF.
  • the first request message may be referred to as a network slice subnet instantiation request message.
  • the first request message includes an identifier of a network slice subnet instance, such as an NSSI ID, and an identifier NSS flavor ID further including a network slice subnet specification.
  • an identifier of the reused network slice subnet instance may also be included.
  • the NSSMF receives the first request message, and the NSSMF sends a first response message to the NSMF.
  • the network slice subnet template is pre-stored in the NSMF and the NSSMF, and the identifier of the network slice subnet instance is created based on the network slice subnet template. Therefore, when the network slice subnet is instantiated, the NSSMF is according to the first request message.
  • the identifier of the network slice subnet specification carried in the network slice subnet template can be found in the network slice subnet template, the structure, configuration, network capability, etc. of the network slice subnet corresponding to the identifier of the network slice subnet specification, thereby performing network slice Network instantiation.
  • the NSMF receives the first response message. Based on the first response message, the NSMF can learn whether the network slice subnet instantiation is successful; if it is not successful, it can initiate a new request message.
  • the first response message may be referred to as a network slice subnet instantiation response message.
  • the first response message is used to indicate the result of the network slice subnet instantiation.
  • the first response message is used to indicate the result of the network slice subnet instantiation.
  • the first response message may include at least one bit information. For example, 1 bit is used to indicate the result of instantiation of the network slice subnet, “0” indicates that the network slice subnet instantiation fails, “1” indicates that the network slice subnet is instantiated successfully, or “0” indicates that the network slice subnet is instantiated. Successfully, "1" indicates that the network slice subnet is instantiated successfully.
  • the first response message may include a life cycle operation occurrence id, where the identifier is used to indicate that the NSSMF has a lifetime of network slice subnet instantiation. An action event, such as the ID is an event number.
  • the communication method proposed by the present application is described by using the first network device as the CSMF and the second network device as the NSSMF.
  • the method may include the following steps:
  • the CSMF sends a first request message to the NSSMF.
  • the first request message may be referred to as a network slice subnet instantiation request message.
  • the first request message includes an identification of the network slice subnet instance (e.g., NSSI ID) and an identity (e.g., NSS flavor ID) that also includes a network slice subnet specification.
  • an identifier of the reused network slice subnet instance may also be included.
  • the NSSMF receives the first request message, and the NSSMF sends a first response message to the CSMF.
  • the network slice subnet template is pre-stored in the CSMF and the NSSMF, and the identifier of the network slice subnet instance is created based on the network slice subnet template. Therefore, when the network slice subnet is instantiated, the NSSMF is according to the first request message.
  • the identifier of the network slice subnet specification carried in the network slice subnet template can be found in the network slice subnet template, the structure, configuration, network capability, etc. of the network slice subnet corresponding to the identifier of the network slice subnet specification, thereby performing network slice Network instantiation.
  • the CSMF receives the first response message. Based on the first response message, the CSMF can learn whether the network slice subnet instantiation is successful; if not, a new request message can be initiated.
  • the first response message may be referred to as a network slice subnet instantiation response message.
  • the first response message is used to indicate the result of the network slice subnet instantiation.
  • the first response message is used to indicate the result of the network slice subnet instantiation.
  • the first response message may include at least one bit information. For example, 1 bit is used to indicate the result of instantiation of the network slice subnet, “0” indicates that the network slice subnet instantiation fails, “1” indicates that the network slice subnet is instantiated successfully, or “0” indicates that the network slice subnet is instantiated. Successfully, "1" indicates that the network slice subnet is instantiated successfully.
  • the first response message may include a life cycle operation occurrence id, where the identifier is used to indicate that the NSSMF has a lifetime of network slice subnet instantiation. An action event, such as the ID is an event number.
  • the first network device carries the identifier of the slice instance (for example, an NSI ID or an NSSI ID) and a slice specification identifier (for example, an NS flavor ID or an NSS flavor ID) in the request message
  • the second network device can obtain the pre-stored slice template according to the identifier of the slice instance, and combine the slice specification identifier to instantiate the slice, which greatly saves signaling overhead in the instantiation process.
  • a further embodiment of the present application provides a communication method.
  • NSSMF When creating an NSI ID and an NSSI ID, all parameters of the network slice requirement or all parameters of the network slice subnet requirement may not be sent to the corresponding NSMF. NSSMF, but only needs to send the identifier of the network slice template or the identifier of the network slice subnet template, thereby reducing the overhead of signaling transmission.
  • FIG. 6 is a schematic diagram of an interaction process of another communication method according to an embodiment of the present disclosure, where the method may include the following steps:
  • the first network device sends a second request message to the second network device.
  • the second request message includes an identifier of the at least one network slice template or an identifier of the at least one network slice subnet template.
  • the second request message is used to request to create an identifier of a network slice instance or an identifier for requesting to create a network slice subnet instance.
  • the second request message may be referred to as a network slice identifier creation request message, or a network slice subnet identifier creation request message, and may be other names, which are not limited herein.
  • the first network device and the second network device have previously saved the network slice template or the network slice subnet template, and the network slice template is uniquely identified by the identifier of the network slice template, and the network slice subnet template adopts the identifier of the network slice subnet template. Make a unique identifier. Therefore, the second request message only needs to carry the identifier of the network slice template or the identifier of the network slice subnet template, and does not need to send all parameters of the network slice requirement or all parameters of the network slice subnet requirement to the corresponding NSMF. , NSSMF. Thus, signaling overhead can be saved.
  • the second network device receives a second request message from the first network device, where the second network device sends a second response message to the first network device.
  • the second network device creates an identifier of the network slice instance or creates an identifier of the network slice subnet instance by using the template corresponding to the identifier saved in the second network device according to the identifier of the template carried in the second request message, and
  • the second response message sends the identifier of the network slice instance or the identifier of the network slice subnet instance to the first network device. That is, the second response message includes an identifier of the at least one network slice instance or an identifier of at least one network slice subnet instance.
  • the second response message may be referred to as a network slice identifier creation response message, or a network slice subnet identifier creation response message, and may be other names, which are not limited herein.
  • the response message does not carry the identifier of the created network slice instance or the identifier of the network slice subnet instance, that is, the NSI ID and the NSSI ID. Therefore, the CSMF does not know which NSI and/or NSSI is required to support its communication service related requirements, and the NSMF does not know which NSS or NIMSs to support its network slice related requirements, for subsequent network slice management. bring inconvenience. For example, when a communication service requires multiple NSIs to be completed together and the requirements of the communication service change, the CSMF can only send the corresponding network slice related requirements to the NSMF, and the NSMF decides to update the relevant NSI, and the CSMF cannot decide to update. Which specific NSI.
  • the second network device can provide an accurate network slice-based service by carrying the identifier of the created network slice instance or the identifier of the network sliced subnet instance in the response message.
  • the first network device receives a second response message from the second network device.
  • the identifier of the at least one network slice instance is created according to the at least one network slice template
  • the identifier of the at least one network slice subnet instance is created according to the at least one network slice subnet template.
  • the second request message further includes a name of the customized at least one network slice instance or a name of the at least one network slice subnet instance.
  • the custom name is the name defined by the user according to personal usage habits or preferences.
  • the name of the customized at least one network slice instance corresponds to the identifier of the at least one network slice instance, that is, the name of the customized network slice instance is used as the identifier of the network slice instance;
  • the name of the network sliced subnet instance corresponds to the identifier of the at least one network sliced subnet instance, and the name of the customized network sliced subnet instance is used as the identifier of the network sliced subnet instance. This makes the name of the instance easy to remember.
  • the first network device may be a CSMF entity or a device with a communication service management function
  • the second network device includes an NSMF entity or a device with a network slice management function, and an NSSMF entity or a network slice subnet management function.
  • the first network device includes an NSMF entity or a device having a network slice management function
  • the second network device includes an NSSMF entity or a device having a network slice subnet management function.
  • first and second network devices as the above different functional entities or devices:
  • FIG. 7 illustrates another communication method proposed by the present application by using the first network device as an NSMF entity and the second network device as an NSSMF entity. The method may include the following steps:
  • the NSMF sends a second request message to the NSSMF.
  • the second request message may be referred to as a network slice subnet identity creation request message.
  • the second request message includes an identifier of a network slice subnet template, such as an NSST ID or an NSSD ID.
  • the second request message may further include a name of a customized network slice subnet instance.
  • the NSSMF receives the second request message.
  • the NSSMF sends a second response message to the NSMF.
  • the second response message may be referred to as a network slice subnet identity creation response message.
  • the second response message includes an identifier of the network slice subnet instance, such as an NSSI ID.
  • the NSMF and the NSSMF pre-store a plurality of network slice subnet templates, and the network slice subnet template identifier is used to uniquely identify a network slice subnet template.
  • the NSSMF creates an identifier of the network slice subnet instance according to the network slice subnet template identifier included in the second request message.
  • the NSSMF sends a second response message to the NSMF, where the second response message carries the identifier of the network slice subnet instance.
  • the NSMF receives the second response message. Based on the second response message, the NSMF can learn whether the identifier of the network slice subnet instance is successfully created. If not, the new request message can be initiated.
  • the NSSMF does not need to configure the related resources of the network slicing subnet instance while creating the identifier of the network slicing subnet instance, and then configure the resources when the network slicing subnet instance needs to be used. This can avoid the waste of resources.
  • FIG. 8 illustrates another communication method proposed by the present application, where the first network device is a CSMF entity, and the second network device is an NSMF entity.
  • the method may include the following steps:
  • the CSMF sends a second request message to the NSMF.
  • the second request message may be referred to as a network slice identification creation request message.
  • the second request message includes an identifier of a network slice template, such as an NST ID or an NSD ID.
  • the second request message may further include a name of the customized network slice instance.
  • the NSMF receives the second request message.
  • the NSMF sends a second response message to the CSMF.
  • the second response message may be referred to as a network slice identification creation response message.
  • the second response message includes an identifier of the network slice instance, such as an NSI ID.
  • both the CSMF and the NSMF pre-store a plurality of network slice templates, and the network slice template identifier is used to uniquely identify a network slice template.
  • the NSMF creates an identifier of the network slice instance according to the network slice template identifier included in the second request message.
  • the NSMF sends a second response message to the CSMF, where the second response message carries the identifier of the network slice instance.
  • the CSMF receives the second response message. Based on the second response message, the CSMF can learn whether the identifier of the network slice instance is successfully created. If not, the new request message can be initiated.
  • the NSMF does not need to configure the related resources of the network slice instance at the same time that the identifier of the network slice instance is created, and the resource configuration is performed when the network slice instance needs to be used, thereby avoiding waste of resources. .
  • FIG. 9 illustrates another communication method proposed by the present application by using the first network device as a CSMF entity and the second network device as an NSSMF entity. The method may include the following steps:
  • the CSMF sends a second request message to the NSSMF.
  • the second request message may be referred to as a network slice subnet identity creation request message.
  • the second request message includes an identifier of a network slice subnet template, such as an NSST ID or an NSSD ID.
  • the second request message may further include a name of a customized network slice subnet instance.
  • the NSSMF receives the second request message.
  • the NSSMF sends a second response message to the CSMF.
  • the second response message may be referred to as a network slice subnet identity creation response message.
  • the second response message includes an identifier of the network slice subnet instance, such as an NSSI ID.
  • the CSMF and the NSSMF pre-store a plurality of network slice subnet templates, and the network slice subnet template identifier is used to uniquely identify a network slice subnet template.
  • the NSSMF creates an identifier of the network slice subnet instance according to the network slice subnet template identifier included in the second request message.
  • the NSSMF sends a second response message to the CSMF, where the second response message carries the identifier of the network slice subnet instance.
  • the CSMF receives the second response message. Based on the second response message, the CSMF can learn whether the identifier of the network slice subnet instance is successfully created. If not, the new request message can be initiated.
  • the NSSMF does not need to configure the related resources of the network slicing subnet instance while creating the identifier of the network slicing subnet instance, and then configure the resources when the network slicing subnet instance needs to be used. This can avoid the waste of resources.
  • the NSI ID and the NSSI ID are created, all the parameters required for the network slice or all the parameters of the network slice subnet need not be sent to the corresponding NSMF and NSSMF. Only the identifier of the network slice template or the identifier of the network slice subnet template needs to be sent, thereby reducing the overhead of signaling transmission.
  • FIG. 10 is a schematic structural diagram of a communication apparatus according to an embodiment of the present invention.
  • the communication apparatus 1000 may include: a sending unit 101 and a receiving unit 102;
  • the sending unit 101 is configured to send, to the first network device, a first request message, where the first request message is used to request to instantiate at least one network slice or at least one network slice subnet, where the first request message includes the at least one An identifier of a network slice instance and an identifier of the at least one network slice specification, or the first request message includes an identifier of the at least one network slice subnet instance and an identifier of the at least one network slice subnet specification;
  • the receiving unit 102 is configured to receive a first response message from the first network device, where the first response message is used to indicate a result of the at least one network slice instantiation, or the first response message is used to indicate The result of instantiating the at least one network slice subnet.
  • each network slice specification represents at least one of the following parameters of each network slice: structure, configuration, and network capabilities of the network slice; or each network slice subnet specification represents each network slice subnet At least one of the following parameters: the structure, configuration, and network capabilities of the network slice subnet.
  • the first request message further includes an identifier of the reused at least one network slice instance; or the first request message further includes an identifier of the reused at least one network slice subnet instance.
  • the first response message includes at least one of the following information: at least one bit information used to indicate the at least one network slice instantiation result, or an identifier of the at least one network slice lifecycle operation event; Or the first response message includes at least one of the following information: at least one bit information used to indicate the at least one network slice subnet instantiation result, or the first response message includes the at least one network slice The ID of the subnet lifecycle operation event.
  • the communication device is a communication service management function or a device having a communication service management function
  • the first network device is a network slice management function or a device having a network slice management function
  • the communication device is a communication service management a device or a device having a communication service management function, wherein the first network device is a network slice subnet management function or a device having a network slice subnet management function; or the communication device is a network slice management function or has a network slice management function.
  • the device of the first network device is a network slice subnet management function or a device with a network slice subnet management function.
  • the communication device 1000 carries the identifier of the slice instance and the slice specification identifier in the request message, and the first network device can obtain the pre-stored slice template according to the identifier of the slice instance, and combine the slice specification.
  • the identification, instantiating the slice greatly saves the signaling overhead in the instantiation process.
  • FIG. 11 is a schematic structural diagram of another communication apparatus according to an embodiment of the present invention.
  • the communication apparatus 1100 may include: a receiving unit 111 and a sending unit 112.
  • the receiving unit 111 is configured to receive a first request message from the first network device, where the first request message is used to request to instantiate at least one network slice or at least one network slice subnet, where the first request message includes the An identifier of the at least one network slice instance and an identifier of the at least one network slice specification, or the first request message includes an identifier of the at least one network slice subnet instance and an identifier of the at least one network slice subnet specification;
  • the sending unit 112 is configured to send a first response message to the first network device, where the first response message is used to indicate a result of the at least one network slice instantiation, or the first response message is used to indicate The result of instantiating at least one network slice subnet.
  • each network slice specification represents at least one of the following parameters of each network slice: structure, configuration, and network capabilities of the network slice; or each network slice subnet specification represents each network slice subnet At least one of the following parameters: the structure, configuration, and network capabilities of the network slice subnet.
  • the first request message further includes an identifier of the reused at least one network slice instance; or the first request message further includes an identifier of the reused at least one network slice subnet instance.
  • the first response message includes at least one of the following information: at least one bit information used to indicate the at least one network slice instantiation result, or an identifier of the at least one network slice lifecycle operation event; Or the first response message includes at least one of the following information: at least one bit information used to indicate the at least one network slice subnet instantiation result, or the first response message includes the at least one network slice The ID of the subnet lifecycle operation event.
  • the communication device is a network slice management function or a device having a network slice management function
  • the first network device is a communication service management function or a device having a communication service management function
  • the communication device is a network slicer. a network management function or a device having a network slice subnet management function, the first network device being a communication service management function or a device having a communication service management function; or the communication device is a network slice subnet management function or having a network slice A device of a subnet management function, where the first network device is a network slice management function or a device having a network slice management function.
  • the first network device carries the identifier of the slice instance and the slice specification identifier in the request message, and the communication device 1100 can obtain the pre-stored slice template according to the identifier of the slice instance, and combine the slice specification.
  • the identification, instantiating the slice greatly saves the signaling overhead in the instantiation process.
  • FIG. 12 is a schematic structural diagram of still another communication apparatus according to an embodiment of the present invention.
  • the communication apparatus 1200 may include: a sending unit 121 and a receiving unit 122.
  • the sending unit 121 is configured to send, to the first network device, a first request message, where the first request message includes an identifier of the at least one network slice template or an identifier of the at least one network slice subnet template;
  • the receiving unit 122 is configured to receive a first response message from the first network device, where the first response message includes an identifier of the at least one network slice instance or an identifier of at least one network slice subnet instance.
  • the identifier of the at least one network slice instance is created according to the at least one network slice template
  • the identifier of the at least one network slice subnet instance is created according to the at least one network slice subnet template.
  • the first request message further includes a name of the customized at least one network slice instance or a name of the at least one network slice subnet instance, where the name of the customized at least one network slice instance is related to the at least one Corresponding to the identifier of a network slice instance, the name of the customized at least one network slice subnet instance corresponds to the identifier of the at least one network slice subnet instance.
  • the communication device is a communication service management function or a device having a communication service management function
  • the first network device is a network slice management function or a device having a network slice management function
  • the communication device is a communication service management a device or a device having a communication service management function, wherein the first network device is a network slice subnet management function or a device having a network slice subnet management function; or the communication device is a network slice management function or has a network slice management function.
  • the device of the first network device is a network slice subnet management function or a device with a network slice subnet management function.
  • the communication device 1200 may not need to send all parameters of the network slice requirement or all parameters of the network slice subnet requirement to the A network device only needs to send the identifier of the network slice template or the identifier of the network slice subnet template, thereby reducing the overhead of signaling transmission.
  • FIG. 13 is a schematic structural diagram of still another communication apparatus according to an embodiment of the present invention.
  • the communication apparatus 1300 may include: a receiving unit 131 and a sending unit 132.
  • the receiving unit 131 is configured to receive a first request message from the first network device, where the first request message includes an identifier of the at least one network slice template or an identifier of the at least one network slice subnet template;
  • the sending unit 132 is configured to send a first response message to the first network device, where the first response message includes an identifier of the at least one network slice instance or an identifier of at least one network slice subnet instance.
  • the identifier of the at least one network slice instance is created according to the at least one network slice template
  • the identifier of the at least one network slice subnet instance is created according to the at least one network slice subnet template.
  • the first request message further includes a name of the customized at least one network slice instance or a name of the at least one network slice subnet instance, where the name of the customized at least one network slice instance is related to the at least one Corresponding to the identifier of a network slice instance, the name of the customized at least one network slice subnet instance corresponds to the identifier of the at least one network slice subnet instance.
  • the communication device is a network slice management function or a device having a network slice management function
  • the first network device is a communication service management function or a device having a communication service management function
  • the communication device is a network slicer. a network management function or a device having a network slice subnet management function, the first network device being a communication service management function or a device having a communication service management function; or the communication device is a network slice subnet management function or having a network slice A device of a subnet management function, where the first network device is a network slice management function or a device having a network slice management function.
  • the first network device may not need to send all parameters of the network slice requirement or all parameters of the network slice subnet requirement to The communication device only needs to send the identifier of the network slice template or the identifier of the network slice subnet template, thereby reducing the overhead of signaling transmission.
  • the embodiment of the present invention further provides a communication device, which may be the first network device in the above communication system, and the communication device may adopt the hardware architecture shown in FIG.
  • the communication device can include a receiver, a transmitter, a memory, and a processor, the receiver, transmitter, memory, and processor being interconnected by a bus.
  • the related functions implemented by the transmitting unit 101 in FIG. 10 may be implemented by a transmitter, and related functions implemented by the receiving unit 102 may be implemented by a receiver.
  • the memory includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an Erasable Programmable Read Only Memory (EPROM), or a portable Compact Disc Read-Only Memory (CD-ROM), which is used for related instructions and data.
  • RAM random access memory
  • ROM read-only memory
  • EPROM Erasable Programmable Read Only Memory
  • CD-ROM portable Compact Disc Read-Only Memory
  • the receiver is for receiving data and/or signals
  • the transmitter is for transmitting data and/or signals.
  • the transmitter and receiver can be separate devices or a single device.
  • the processor may include one or more processors, for example, including one or more central processing units (CPUs).
  • CPUs central processing units
  • the CPU may be a single-core CPU, or may be Multi-core CPU.
  • the memory is used to store program code and data of the network device.
  • a transmitter configured to send a first request message to the second network device, for example, performing S201 in the embodiment shown in FIG. 2; and receiving, by the receiver, a first response message from the second network device, for example, executing a map S202 in the illustrated embodiment.
  • the embodiment of the present invention further provides a communication device, which may be a second network device in the above communication system, and the communication device may adopt the hardware architecture shown in FIG.
  • the communication device can include a receiver, a transmitter, a memory, and a processor, the receiver, transmitter, memory, and processor being interconnected by a bus.
  • the related functions implemented by the receiving unit 111 in FIG. 11 can be implemented by a receiver, and the related functions implemented by the transmitting unit 112 can be implemented by a transmitter.
  • Memory includes, but is not limited to, RAM, ROM, EPROM, or CD-ROM for associated instructions and data.
  • the receiver is for receiving data and/or signals
  • the transmitter is for transmitting data and/or signals.
  • the transmitter and receiver can be separate devices or a single device.
  • the processor may include one or more processors, for example including one or more CPUs.
  • the processor may be a single core CPU or a multi-core CPU.
  • the memory is used to store program code and data of the network device.
  • a receiver configured to receive a first request message from the first network device, for example, perform S202 in the embodiment shown in FIG. 2; and a transmitter, configured to send a first response message to the first network device, for example, executing FIG. S202 of the illustrated embodiment.
  • the embodiment of the present invention further provides a communication device, which may be the first network device in the above communication system, and the communication device may adopt the hardware architecture shown in FIG.
  • the communication device can include a receiver, a transmitter, a memory, and a processor, the receiver, transmitter, memory, and processor being interconnected by a bus.
  • the related functions implemented by the transmitting unit 121 in FIG. 12 may be implemented by a transmitter, and related functions implemented by the receiving unit 122 may be implemented by a receiver.
  • Memory includes, but is not limited to, RAM, ROM, EPROM, or CD-ROM for associated instructions and data.
  • the receiver is for receiving data and/or signals
  • the transmitter is for transmitting data and/or signals.
  • the transmitter and receiver can be separate devices or a single device.
  • the processor may include one or more processors, for example including one or more CPUs.
  • the processor may be a single core CPU or a multi-core CPU.
  • the memory is used to store program code and data of the network device.
  • a transmitter configured to send a second request message to the second network device, for example, S601 of the embodiment shown in FIG. 6; and a receiver, configured to receive a second response message from the second network device, for example, executing FIG. S602 of the illustrated embodiment.
  • the embodiment of the present invention further provides a communication device, which may be a second network device in the above communication system, and the communication device may adopt the hardware architecture shown in FIG.
  • the communication device can include a receiver, a transmitter, a memory, and a processor, the receiver, transmitter, memory, and processor being interconnected by a bus.
  • the related functions implemented by the receiving unit 131 in FIG. 13 can be implemented by a receiver, and the related functions implemented by the transmitting unit 132 can be implemented by a transmitter.
  • Memory includes, but is not limited to, RAM, ROM, EPROM, or CD-ROM for associated instructions and data.
  • the receiver is for receiving data and/or signals
  • the transmitter is for transmitting data and/or signals.
  • the transmitter and receiver can be separate devices or a single device.
  • the processor may include one or more processors, for example including one or more CPUs.
  • the processor may be a single core CPU or a multi-core CPU.
  • the memory is used to store program code and data of the network device.
  • a receiver configured to receive a second request message from the first network device, for example, perform S602 of the embodiment shown in FIG. 6; and a transmitter, configured to send a second response message to the first network device, for example, executing FIG. S602 of the illustrated embodiment.
  • Figure 14 only shows a simplified design of the communication device.
  • the communication device may also include other necessary components, including but not limited to any number of transceivers, processors, controllers, memories, etc., and all communication devices that can implement the embodiments of the present invention are in the present invention. Within the scope of protection.
  • Yet another aspect of the present application provides a communication system including the above-described first network device and second network device.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in or transmitted by a computer readable storage medium.
  • the computer instructions may be from a website site, computer, server or data center via a wired (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) Another website site, computer, server, or data center for transmission.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)). )Wait.
  • the foregoing storage medium includes: a read-only memory (ROM) or a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种通信方法及装置。该方法包括：第一网络设备向第二网络设备发送第一请求消息，第一请求消息用于请求对网络切片或网络切片子网进行实例化，第一请求消息包括网络切片实例的标识和网络切片规格的标识，或第一请求消息包括网络切片子网实例的标识和网络切片子网规格的标识；第一网络设备接收来自第二网络设备的第一响应消息，第一响应消息用于指示网络切片实例化的结果，或第一响应消息用于指示网络切片子网实例化的结果。还公开了相应的装置。第一网络设备在请求消息中携带切片实例的标识和切片规格标识，第二网络设备可根据切片实例的标识获取预存的切片模板，并结合切片规格标识，对该切片进行实例化，较大地节省了实例化过程中的信令开销。

Description

通信方法及装置
本申请要求于2017年9月30日提交中国专利局、申请号为2017109449378、发明名称为“通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
随着移动通信的高速发展，数字化转型几乎涉及了所有传统行业。但是，传统蜂窝网络架构只能提供统一的网络服务，难以满足差异性极大的通信需求，包括功能性差异、性能差异等。在下一代移动通信***，例如第五代(fifth-generation，5G)移动通信***中，网络被抽象为“网络切片(network slice)”。一个网络切片满足某一类或一个用例的连接通信服务需求，整个5G网络由满足不同连接能力的大量网络切片组成。统一的网络平台，利用动态的、安全的网络切片支持不同功能和服务质量(quality of service，QoS)的连接通信服务。
网络切片实例(network slice instance，NSI)是对网络切片的实例化，即是一个真实运行的逻辑网络，能满足一定网络特性或服务需求。一个网络切片实例可能提供一种或多种服务。网络切片实例可以由网络切片管理***创建，如图1所示的网络切片管理***的结构示意图，该***包括通信服务管理功能(communication service management function，CSMF)实体11、网络切片管理功能(network slice management function，NSMF)12和网络切片子网管理功能(network slice subnet management function，NSSMF)实体13。CSMF、NSMF和NSSMF互相连接。一个网络切片管理***可能创建多个网络切片实例并同时对它们进行管理，例如，对多个网络切片实例进行修改、终结等。一个网络切片实例包括网络切片子网实例(network slice subnet instance，NSSI)和/或网络功能。
鉴于此，如何高效地进行网络切片实例化或网络切片子网实例化是一个亟待解决的问题。
发明内容
本申请提供了一种通信方法及装置，以高效地进行网络切片实例化或网络切片子网实例化，节省实例化过程中的信令开销。
本申请的一方面，提供了一种通信方法，包括：第一网络设备向第二网络设备发送第一请求消息，第一请求消息用于请求对至少一个网络切片或至少一个网络切片子网进行实例化，所述第一请求消息包括所述至少一个网络切片实例的标识和所述至少一个网络切片规格的标识，或所述第一请求消息包括所述至少一个网络切片子网实例的标识和所述至少一个网络切片子网规格的标识；所述第一网络设备接收来自所述第二网络设备的第一响应消息，所述第一响应消息用于指示所述至少一个网络切片实例化的结果，或所述第一响应消息用于指示所述至少一个网络切片子网实例化的结果。
在该设计中，第一网络设备在请求消息中携带切片实例的标识和切片规格标识，第二网络设备可根据切片实例的标识获取预存的切片模板，并结合切片规格标识，对该切片进行实例化，较大地节省了实例化过程中的信令开销。
在一种可能的设计中，每个网络切片规格代表了每个网络切片的以下参数中的至少一种：网络切片的结构、配置和网络能力；或每个网络切片子网规格代表了每个网络切片子网的以下参数中的至少一种：网络切片子网的结构、配置和网络能力。
在该设计中，第一网络设备和第二网络设备预先存储了网络切片模板或网络切片子网模板，网络切片模板中，包含有一个或多个网络切片对应的网络切片规格；网络切片子网模板中，包含有一个或多个网络切片子网对应的网络切片子网规格。
在另一种可能的设计中，所述第一请求消息还包括重用的至少一个网络切片实例的标识；或所述第一请求消息还包括重用的至少一个网络切片子网实例的标识。
在该设计中，第二网络设备无需重新在网络切片模板中找到与该网络切片规格的标识对应的该种网络切片的结构、配置、网络能力等，来进行网络切片实例化，而是采用已经实例化的网络切片实例。第二网络设备可以将该已经实例化的网络切片实例与第一请求消息中携带的网络切片实例的标识对应。或者，第二网络设备无需重新在网络切片子网模板中找到与该网络切片子网规格的标识对应的该种网络切片子网的结构、配置、网络能力等，来进行网络切片子网实例化，而是采用已经实例化的网络切片子网实例。第二网络设备可以将该已经实例化的网络切片子网实例与第一请求消息中携带的网络切片子网实例的标识对应。
在又一种可能的设计中，所述第一响应消息包括以下信息中的至少一种：用于指示所述至少一个网络切片实例化结果的至少一个比特信息，或所述至少一个网络切片生命周期操作事件的标识；或所述第一响应消息包括以下信息中的至少一种：用于指示所述至少一个网络切片子网实例化结果的至少一个比特信息，或所述第一响应消息包括所述至少一个网络切片子网生命周期操作事件的标识。
在该设计中，给出了第一响应消息的两种指示方式，简单地指示实例化结果。
在又一种可能的设计中，所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备，所述第二网络设备为网络切片管理功能或者具备网络切片管理功能的设备；或所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备，所述第二网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备；或所述第一网络设备为网络切片管理功能或者具备网络切片管理功能的设备，所述第二网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备。
相应地，另一方面，提供了一种通信装置，该通信装置具有实现上述方法中通信装置行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
一种可能的实现方式中，所述通信装置包括：发送单元，用于向第二网络设备发送第一请求消息，第一请求消息用于请求对至少一个网络切片或至少一个网络切片子网进行实例化，所述第一请求消息包括所述至少一个网络切片实例的标识和所述至少一个网络切片规格的标识，或所述第一请求消息包括所述至少一个网络切片子网实例的标识和所述至少 一个网络切片子网规格的标识；接收单元，用于接收来自所述第二网络设备的第一响应消息，所述第一响应消息用于指示所述至少一个网络切片实例化的结果，或所述第一响应消息用于指示所述至少一个网络切片子网实例化的结果。
另一种可能的实现方式中，所述通信装置包括：接收器、发射器、存储器和处理器；其中，所述存储器中存储一组程序代码，且所述处理器用于调用所述存储器中存储的程序代码，执行以下操作：控制所述发射器向第二网络设备发送第一请求消息，第一请求消息用于请求对至少一个网络切片或至少一个网络切片子网进行实例化，所述第一请求消息包括所述至少一个网络切片实例的标识和所述至少一个网络切片规格的标识，或所述第一请求消息包括所述至少一个网络切片子网实例的标识和所述至少一个网络切片子网规格的标识；控制所述接收器接收来自所述第二网络设备的第一响应消息，所述第一响应消息用于指示所述至少一个网络切片实例化的结果，或所述第一响应消息用于指示所述至少一个网络切片子网实例化的结果。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见上述各可能的通信装置的方法实施方式以及所带来的有益效果，因此该装置的实施可以参见方法的实施，重复之处不再赘述。
本申请的又一方面，提供了一种通信方法，包括：第二网络设备接收来自第一网络设备的第一请求消息，第一请求消息用于请求对至少一个网络切片或至少一个网络切片子网进行实例化，所述第一请求消息包括所述至少一个网络切片实例的标识和所述至少一个网络切片规格的标识，或所述第一请求消息包括所述至少一个网络切片子网实例的标识和所述至少一个网络切片子网规格的标识；所述第二网络设备发送第一响应消息给所述第一网络设备，所述第一响应消息用于指示所述至少一个网络切片实例化的结果，或所述第一响应消息用于指示所述至少一个网络切片子网实例化的结果。
在该设计中，第一网络设备在请求消息中携带切片实例的标识和切片规格标识，第二网络设备可根据切片实例的标识获取预存的切片模板，并结合切片规格标识，对该切片进行实例化，较大地节省了实例化过程中的信令开销。
在一种可能的设计中，每个网络切片规格代表了每个网络切片的以下参数中的至少一种：网络切片的结构、配置和网络能力；或每个网络切片子网规格代表了每个网络切片子网的以下参数中的至少一种：网络切片子网的结构、配置和网络能力。
在该设计中，第一网络设备和第二网络设备预先存储了网络切片模板或网络切片子网模板，网络切片模板中，包含有一个或多个网络切片对应的网络切片规格；网络切片子网模板中，包含有一个或多个网络切片子网对应的网络切片子网规格。
在另一种可能的设计中，所述第一请求消息还包括重用的至少一个网络切片实例的标识；或所述第一请求消息还包括重用的至少一个网络切片子网实例的标识。
在该设计中，第二网络设备无需重新在网络切片模板中找到与该网络切片规格的标识对应的该种网络切片的结构、配置、网络能力等，来进行网络切片实例化，而是采用已经实例化的网络切片实例。第二网络设备可以将该已经实例化的网络切片实例与第一请求消息中携带的网络切片实例的标识对应。或者，第二网络设备无需重新在网络切片子网模板中找到与该网络切片子网规格的标识对应的该种网络切片子网的结构、配置、网络能力等， 来进行网络切片子网实例化，而是采用已经实例化的网络切片子网实例。第二网络设备可以将该已经实例化的网络切片子网实例与第一请求消息中携带的网络切片子网实例的标识对应。
在又一种可能的设计中，所述第一响应消息包括以下信息中的至少一种：用于指示所述至少一个网络切片实例化结果的至少一个比特信息，或所述至少一个网络切片生命周期操作事件的标识；或所述第一响应消息包括以下信息中的至少一种：用于指示所述至少一个网络切片子网实例化结果的至少一个比特信息，或所述第一响应消息包括所述至少一个网络切片子网生命周期操作事件的标识。
在该设计中，给出了第一响应消息的两种指示方式，简单地指示实例化结果。
在又一种可能的设计中，所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备，所述第二网络设备为网络切片管理功能或者具备网络切片管理功能的设备；或所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备，所述第二网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备；或所述第一网络设备为网络切片管理功能或者具备网络切片管理功能的设备，所述第二网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备。
相应地，另一方面，提供了一种通信装置，该通信装置具有实现上述方法中通信装置行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
一种可能的实现方式中，所述通信装置包括：接收单元，用于接收来自第一网络设备的第一请求消息，第一请求消息用于请求对至少一个网络切片或至少一个网络切片子网进行实例化，所述第一请求消息包括所述至少一个网络切片实例的标识和所述至少一个网络切片规格的标识，或所述第一请求消息包括所述至少一个网络切片子网实例的标识和所述至少一个网络切片子网规格的标识；发送单元，用于发送第一响应消息给所述第一网络设备，所述第一响应消息用于指示所述至少一个网络切片实例化的结果，或所述第一响应消息用于指示所述至少一个网络切片子网实例化的结果。
另一种可能的实现方式中，所述通信装置包括：接收器、发射器、存储器和处理器；其中，所述存储器中存储一组程序代码，且所述处理器用于调用所述存储器中存储的程序代码，执行以下操作：控制所述接收器接收来自第一网络设备的第一请求消息，第一请求消息用于请求对至少一个网络切片或至少一个网络切片子网进行实例化，所述第一请求消息包括所述至少一个网络切片实例的标识和所述至少一个网络切片规格的标识，或所述第一请求消息包括所述至少一个网络切片子网实例的标识和所述至少一个网络切片子网规格的标识；控制所述发射器发送第一响应消息给所述第一网络设备，所述第一响应消息用于指示所述至少一个网络切片实例化的结果，或所述第一响应消息用于指示所述至少一个网络切片子网实例化的结果。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见上述各可能的通信装置的方法实施方式以及所带来的有益效果，因此该装置的实施可以参见方法的实施，重复之处不再赘述。
本申请的又一方面，提供了一种通信方法，包括：第一网络设备向第二网络设备发送 第一请求消息，所述第一请求消息包括至少一个网络切片模板的标识或者至少一个网络切片子网模板的标识；所述第一网络设备接收来自所述第二网络设备的第一响应消息，所述第一响应消息包括所述至少一个网络切片实例的标识或者至少一个网络切片子网实例的标识。
在该设计中，在创建NSI ID、NSSI ID的时候，可以不需要将网络切片的需求的所有参数，或者网络切片子网的需求的所有参数发送给对应的NSMF、NSSMF，而只需要发送网络切片模板的标识或网络切片子网模板的标识，从而降低了信令传输的开销。
在一种可能的设计中，所述至少一个网络切片实例的标识是根据所述至少一个网络切片模板创建，所述至少一个网络切片子网实例的标识是根据所述至少一个网络切片子网模板创建。
在该设计中，第一网络设备和第二网络设备预先已保存了网络切片模板或网络切片子网模板，且网络切片模板采用网络切片模板的标识进行唯一标识，网络切片子网模板采用网络切片子网模板的标识进行唯一标识。在创建NSI ID、NSSI ID的时候，可以不需要将网络切片的需求的所有参数，或者网络切片子网的需求的所有参数发送给对应的NSMF、NSSMF，而只需要发送网络切片模板的标识或网络切片子网模板的标识，从而降低了信令传输的开销。
在另一种可能的设计中，所述第一请求消息还包括自定义的至少一个网络切片实例的名称或至少一个网络切片子网实例的名称，其中，所述自定义的至少一个网络切片实例的名称与所述至少一个网络切片实例的标识对应，所述自定义的至少一个网络切片子网实例的名称与所述至少一个网络切片子网实例的标识对应。
在该设计中，该自定义的名称即用户根据个人使用习惯或喜好等定义的名称。在创建网络切片实例的标识时，可用自定义的网络切片实例的名称作为网络切片实例的标识；在创建网络切片子网实例的标识时，可用自定义的网络切片子网实例的名称作为网络切片子网实例的标识。这样使得实例的名称易记。
在又一种可能的设计中，所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备，所述第二网络设备为网络切片管理功能或者具备网络切片管理功能的设备；或所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备，所述第二网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备；或所述第一网络设备为网络切片管理功能或者具备网络切片管理功能的设备，所述第二网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备。
相应地，另一方面，提供了一种通信装置，该通信装置具有实现上述方法中通信装置行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
一种可能的实现方式中，所述通信装置包括：发送单元，用于向第二网络设备发送第一请求消息，所述第一请求消息包括至少一个网络切片模板的标识或者至少一个网络切片子网模板的标识；接收单元，用于接收来自所述第二网络设备的第一响应消息，所述第一响应消息包括所述至少一个网络切片实例的标识或者至少一个网络切片子网实例的标识。
另一种可能的实现方式中，所述通信装置包括：接收器、发射器、存储器和处理器； 其中，所述存储器中存储一组程序代码，且所述处理器用于调用所述存储器中存储的程序代码，执行以下操作：控制所述发射器向第二网络设备发送第一请求消息，所述第一请求消息包括至少一个网络切片模板的标识或者至少一个网络切片子网模板的标识；控制所述接收器接收来自所述第二网络设备的第一响应消息，所述第一响应消息包括所述至少一个网络切片实例的标识或者至少一个网络切片子网实例的标识。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见上述各可能的通信装置的方法实施方式以及所带来的有益效果，因此该装置的实施可以参见方法的实施，重复之处不再赘述。
本申请的又一方面，提供了一种通信方法，包括：第二网络设备接收来自第一网络设备的第一请求消息，所述第一请求消息包括至少一个网络切片模板的标识或者至少一个网络切片子网模板的标识；所述第二网络设备向所述第一网络设备发送第一响应消息，所述第一响应消息包括所述至少一个网络切片实例的标识或者至少一个网络切片子网实例的标识。
在该设计中，在创建NSI ID、NSSI ID的时候，可以不需要将网络切片的需求的所有参数，或者网络切片子网的需求的所有参数发送给对应的NSMF、NSSMF，而只需要发送网络切片模板的标识或网络切片子网模板的标识，从而降低了信令传输的开销。
在一种可能的设计中，所述至少一个网络切片实例的标识是根据所述至少一个网络切片模板创建，所述至少一个网络切片子网实例的标识是根据所述至少一个网络切片子网模板创建。
在该设计中，第一网络设备和第二网络设备预先已保存了网络切片模板或网络切片子网模板，且网络切片模板采用网络切片模板的标识进行唯一标识，网络切片子网模板采用网络切片子网模板的标识进行唯一标识。在创建NSI ID、NSSI ID的时候，可以不需要将网络切片的需求的所有参数，或者网络切片子网的需求的所有参数发送给对应的NSMF、NSSMF，而只需要发送网络切片模板的标识或网络切片子网模板的标识，从而降低了信令传输的开销。
在另一种可能的设计中，所述第一请求消息还包括自定义的至少一个网络切片实例的名称或至少一个网络切片子网实例的名称，其中，所述自定义的至少一个网络切片实例的名称与所述至少一个网络切片实例的标识对应，所述自定义的至少一个网络切片子网实例的名称与所述至少一个网络切片子网实例的标识对应。
在该设计中，该自定义的名称即用户根据个人使用习惯或喜好等定义的名称。在创建网络切片实例的标识时，可用自定义的网络切片实例的名称作为网络切片实例的标识；在创建网络切片子网实例的标识时，可用自定义的网络切片子网实例的名称作为网络切片子网实例的标识。这样使得实例的名称易记。
在又一种可能的设计中，所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备，所述第二网络设备为网络切片管理功能或者具备网络切片管理功能的设备；或所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备，所述第二网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备；或所述第一网络设备为网络切片管理功能或者具备网络切片管理功能的设备，所述第二网络设备为网络切 片子网管理功能或者具备网络切片子网管理功能的设备。
相应地，另一方面，提供了一种通信装置，该通信装置具有实现上述方法中通信装置行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
一种可能的实现方式中，所述通信装置包括：接收单元，用于接收来自第一网络设备的第一请求消息，所述第一请求消息包括至少一个网络切片模板的标识或者至少一个网络切片子网模板的标识；发送单元，用于向所述第一网络设备发送第一响应消息，所述第一响应消息包括所述至少一个网络切片实例的标识或者至少一个网络切片子网实例的标识。
另一种可能的实现方式中，所述通信装置包括：接收器、发射器、存储器和处理器；其中，所述存储器中存储一组程序代码，且所述处理器用于调用所述存储器中存储的程序代码，执行以下操作：控制所述接收器接收来自第一网络设备的第一请求消息，所述第一请求消息包括至少一个网络切片模板的标识或者至少一个网络切片子网模板的标识；控制所述发射器向所述第一网络设备发送第一响应消息，所述第一响应消息包括所述至少一个网络切片实例的标识或者至少一个网络切片子网实例的标识。
基于同一发明构思，由于该装置解决问题的原理以及有益效果可以参见上述各可能的通信装置的方法实施方式以及所带来的有益效果，因此该装置的实施可以参见方法的实施，重复之处不再赘述。
本申请的又一方面提供了一种通信***，包括上述第一网络设备和第二网络设备。
本申请的又一方面提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
本申请的又一方面提供了一种通信芯片，其中存储有指令，当其在网络设备或终端设备上运行时，使得计算机执行上述各方面所述的方法。
本申请的又一方面提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
附图说明
为了更清楚地说明本发明实施例或背景技术中的技术方案，下面将对本发明实施例或背景技术中所需要使用的附图进行说明。
图1为一种网络切片管理***的结构示意图；
图2为本发明实施例提供的一种通信方法的交互流程示意图；
图3为CSMF与NSMF之间的一种通信方法的交互流程示意图；
图4为NSMF与NSSMF之间的一种通信方法的交互流程示意图；
图5为CSMF与NSSMF之间的一种通信方法的交互流程示意图；
图6为本发明实施例提供的另一种通信方法的交互流程示意图；
图7为NSMF与NSSMF之间的另一种通信方法的交互流程示意图；
图8为CSMF与NSMF之间的另一种通信方法的交互流程示意图；
图9为CSMF与NSSMF之间的另一种通信方法的交互流程示意图；
图10为本发明实施例提供的一种通信装置的结构示意图；
图11为本发明实施例提供的另一种通信装置的结构示意图；
图12为本发明实施例提供的又一种通信装置的结构示意图；
图13为本发明实施例提供的又一种通信装置的结构示意图；
图14为本发明实施例提供的一种通信装置的硬件结构图。
具体实施方式
下面结合本发明实施例中的附图对本发明实施例进行描述。
在图1所示的网络切片管理***中，关于CSMF的功能，一方面，CSMF主要负责将运营商和/或第三方客户的通信服务相关需求转化为网络切片的相关需求，并通过和NSMF之间的接口向NSMF发送对网络切片的需求(如创建、终结、修改网络切片实例请求等)，从NSMF获取网络切片的管理数据(如性能、故障数据等)，生成运行于网络切片实例之上的通信业务的管理数据，接收运营商和/或第三方客户对网络切片管理数据和/或通信业务的管理数据的订阅需求等。另一方面，CSMF主要负责将运营商和/或第三方客户的通信服务相关需求转化为网络切片子网的相关需求，并通过和NSSMF之间的接口向NSSMF发送对网络切片子网的需求(如创建、终结、修改网络切片子网实例请求等)，从NSSMF获取网络切片子网的管理数据(如性能、故障数据等)，生成运行于网络切片子网实例之上的通信业务的管理数据，接收运营商和/或第三方客户对网络切片子网管理数据和/或通信业务的管理数据的订阅需求等。
NSMF主要负责接收CSMF发送的网络切片相关需求，对网络切片实例的生命周期、性能、故障等进行管理，编排网络切片实例的组成，分解网络切片实例的需求为各网络切片子网实例和/或网络功能的需求，向各NSSMF发送网络切片子网实例管理请求。
NSSMF主要负责接收NSMF或CSMF发送的网络切片子网需求，对网络切片子网实例进行管理，编排网络切片子网实例的组成。
下面对本发明实施例涉及的几个主要术语分别进行描述：
网络切片(network slice)：指根据不同的服务需求定制化的、不同的逻辑网络。网络切片可以是一个包括终端设备、接入网、传输网、核心网和应用服务器的完整的网络，能够提供完整的电信服务，具有一定网络能力；网络切片也可以是上述终端设备、接入网、传输网、核心网和应用服务器中的一个或多个的组合。
网络切片实例(network slice instance，NSI)：是对网络切片的实例化，即是一个真实运行的逻辑网络，能满足一定的网络特性或服务需求。一个网络切片实例可提供一种或多种服务。网络切片实例可以由网络切片管理***创建，一个网络切片管理***可能创建多个网络切片实例并同时对它们进行管理，例如，对多个网络切片实例进行修改、终结等。当多个网络切片实例共存时，网络切片实例之间可以共享部分网络资源和网络功能。一个完整的网络切片实例能够提供完整的端到端的网络服务，而网络切片实例由网络切片子网实例(network slice subnet instance，NSSI)和/或网络功能构成。网络功能可以包括物理网络功能和/或虚拟网络功能。以下将物理网络功能和/或虚拟网络功能统称为网络功能。
网络切片模板(network slice template，NST)：描述网络切片的结构(包含的构成元素(components，例如：网络切片子网和/或网络功能描述等)以及各构成元素之间的连接)、 配置、网络能力等。网络切片模板中，包含有一个或多个网络切片对应的网络切片规格。每个网络切片规格对应一个网络切片规格的标识。每个网络切片对应的网络切片规格代表了该种网络切片的结构、配置、网络能力等，例如，代表了该种网络切片的服务水平协议(key performance indicator，SLA)或者关键绩效指标(key performance indicator，KPI)参数，以及提供该SLA或者KPI参数所需的网络切片的结构、配置等。网络切片模板也称之为网络切片描述(network slice descriptor，NSD)。
网络切片子网实例(network slice subnet instance，NSSI)：网络切片子网实例可以不需要提供完整的端到端的网络服务，网络切片子网实例可以是网络切片实例中同一个设备商的网络功能组成的集合，也可能是按域划分的网络功能的集合，例如核心网网络切片子网实例、接入网网络切片子网实例，或由部署位置等其他方式组成的集合。网络切片子网实例可能被多个网络切片实例共享。提出网络切片子网实例的概念，可以方便网络切片管理***管理。
网络切片子网模板(network slice subnet template，NSST)：描述网络切片子网的结构(包含的构成元素以及各构成元素之间的连接)、配置、网络能力等。网络切片子网模板中，包含有一个或多个网络切片子网对应的网络切片子网规格。每个网络切片子网规格对应一个网络切片子网规格的标识。每个网络切片子网对应的网络切片子网规格代表了该种网络切片子网的结构、配置、网络能力等，例如，代表了该种网络切片子网的SLA或者KPI参数，以及提供该SLA或者KPI参数所需的该网络切片子网的的结构、配置等。网络切片子网模板也称之为网络切片子网描述(network slice subnet descriptor，NSSD)。
需要说明的是，本发明实施例中的术语“***”和“网络”可被互换使用。“多个”是指两个或两个以上，鉴于此，本发明实施例中也可以将“多个”理解为“至少两个”。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，字符“/”，如无特殊说明，一般表示前后关联对象是一种“或”的关系。
本发明实施例提供了一种通信方法，第一网络设备在请求消息中携带切片实例的标识(例如，NSI ID或NSSI ID)和切片规格标识(例如，NS flavor ID或NSS flavor ID)，第二网络设备可根据切片实例的标识获取预存的切片模板，并结合切片规格标识，对该切片进行实例化，较大地节省了实例化过程中的信令开销。
图2为本发明实施例提供的一种通信方法的交互流程示意图，该方法可包括以下步骤：
S201，第一网络设备向第二网络设备发送第一请求消息。其中，该第一请求消息包括至少一个网络切片实例的标识和至少一个网络切片规格的标识(flavor ID)；或该第一请求消息包括至少一个网络切片子网实例的标识和至少一个网络切片子网规格的标识。
示例性地，上述网络切片实例的标识可以预先存储在第一网络设备或者第二网络设备中，以使第二网络设备在根据第一请求消息获得网络切片实例的标识时，能够知悉需要实例化的是哪个网络切片实例。或者，在其它的实施例中，该网络切片实例的标识也可以根据下文图8实施例所示的方法进行创建。
示例性地，上述网络切片子网实例的标识可以预先存储在第一网络设备或者第二网络设备中，以使第二网络设备在根据第一请求消息获得网络切片子网实例的标识时，能够知 悉需要实例化的是哪个网络切片子网实例。或者，在其它的实施例中，该网络切片子网实例的标识也可以根据下文图7实施例所示的方法进行创建。
该第一请求消息用于请求对所述至少一个网络切片或所述至少一个网络切片子网进行实例化。该第一请求消息可以称为网络切片实例化请求消息，或网络切片子网实例化请求消息，或其它的名称，在此不作限制。
其中，网络切片模板中，包含有一个或多个网络切片对应的网络切片规格。网络切片规格代表了对应的网络切片的结构、配置、网络能力等，例如，代表了对应的网络切片的SLA或者KPI参数，以及提供该SLA或者KPI参数所需的网络切片的结构、配置等。每个网络切片对应的网络切片规格对应一个网络切片规格的标识。
其中，网络切片子网模板中，包含有一个或多个网络切片子网对应的网络切片子网规格。网络切片子网规格代表了对应的网络切片子网的结构、配置、网络能力等，例如，代表了该种网络切片子网的SLA或者KPI参数，以及提供该SLA或者KPI参数所需的该网络切片子网的结构、配置等。每个网络切片子网对应的网络切片子网规格对应一个网络切片子网规格的标识。
S202，第二网络设备接收该第一请求消息，所述第二网络设备向所述第一网络设备发送第一响应消息。
其中，该第一响应消息用于指示所述至少一个网络切片或所述至少一个网络切片子网的实例化结果。该第一响应消息可以称为网络切片实例化响应消息，或网络切片子网实例化响应消息，或其它的名称，在此不作限制。
所述第一网络设备接收该第一响应消息。第一网络设备根据该第一响应消息，可以了解网络切片实例化或网络切片子网实例化是否成功；如果没有成功，则可以发起新的请求消息。
具体地，在一种实现方式中，第一网络设备和第二网络设备中预先存储了网络切片模板，而网络切片实例的标识是基于网络切片模板创建的，因此，在进行网络切片实例化时，根据第一请求消息中携带的网络切片规格的标识，可以在网络切片模板中找到与该网络切片规格的标识对应的该种网络切片的结构、配置、网络能力等，从而进行网络切片实例化。
在另一种实现方式中，第一网络设备和第二网络设备中预先存储了网络切片子网模板，而网络切片子网实例的标识是基于网络切片子网模板创建的，因此，在进行网络切片子网实例化时，根据第一请求消息中携带的网络切片子网规格的标识，可以在网络切片子网模板中找到与该网络切片子网规格的标识对应的该种网络切片子网的结构、配置、网络能力等，从而进行网络切片子网实例化。
在又一个实现方式中，该第一请求消息还可以包括重用的至少一个网络切片实例的标识。在该实现方式中，第二网络设备无需重新在网络切片模板中找到与该网络切片规格的标识对应的该种网络切片的结构、配置、网络能力等，来进行网络切片实例化，而是采用已经实例化的网络切片实例，该已经实例化的网络切片实例与当前第二网络设备需要实例化的网络切片的结构、配置、网络能力等基本一致。第二网络设备可以将该已经实例化的网络切片实例与第一请求消息中携带的网络切片实例的标识对应，这时，该已有的网络切片实例对应两个标识，即重用的网络切片实例的标识和当前第二网络设备需要实例化的网 络切片实例的标识。
在又一个实现方式中，该第一请求消息还可以包括重用的至少一个网络切片子网实例的标识。在该实现方式中，第二网络设备无需重新在网络切片子网模板中找到与该网络切片子网规格的标识对应的该种网络切片子网的结构、配置、网络能力等，来进行网络切片子网实例化，而是采用已经实例化的网络切片子网实例，该已经实例化的网络切片子网实例与当前第二网络设备需要实例化的网络切片子网的结构、配置、网络能力等基本一致。第二网络设备可以将该已经实例化的网络切片子网实例与第一请求消息中携带的网络切片子网实例的标识对应，这时，该已有的网络切片子网实例对应两个标识，即已有的网络切片子网实例的标识和当前第二网络设备需要实例化的网络切片实例的标识。
在一个实施例中，第一网络设备可以为CSMF实体或者其它具备通信服务管理功能的设备，第二网络设备可以为NSMF实体或者具备其它网络切片管理功能的设备。NSMF接收到第一请求消息后，若第一请求消息中包括NSI ID和NS flavor ID，则NSMF对NSI ID对应的网络切片进行实例化。具体地，对NS flavor ID所对应的网络切片的构成元素(例如，网络切片子网)创建和配置好相关的资源(例如，计算资源，存储资源，传输资源等)，使其满足该NS flavor ID所代表的网络切片能力(例如，SLA或者KPI)。如果第一请求消息中包含有被重用的网络切片实例，则对该被重用的网络切片实例进行重新配置，使其满足NS flavor ID所代表的网络切片能力。
图3以第一网络设备为CSMF，第二网络设备为NSMF为例，说明本申请所提出的通信方法，该方法可包括以下步骤：
S301，CSMF向NSMF发送第一请求消息。
在这里，该第一请求消息可以称为网络切片实例化请求消息。该第一请求消息包括网络切片实例的标识，例如NSI ID，以及还包括网络切片规格的标识NS flavor ID。可选地，还可包括重用的网络切片实例的标识。
S302，NSMF接收该第一请求消息，并向CSMF发送第一响应消息。
CSMF和NSMF中预先存储了网络切片模板，而网络切片实例的标识是基于网络切片模板创建的，因此，在进行网络切片实例化时，根据第一请求消息中携带的网络切片规格的标识，可以在网络切片模板中找到与该网络切片规格的标识对应的该种网络切片的结构、配置、网络能力等，从而进行网络切片实例化。
CSMF接收该第一响应消息。CSMF根据该第一响应消息，可以了解网络切片实例化是否成功；如果没有成功，则可以发起新的请求消息。
在这里，该第一响应消息可以称为网络切片实例化响应消息。该第一响应消息用于指示网络切片实例化的结果。
NSMF根据第一请求消息中的参数信息，对网络切片进行实例化，并向CSMF发送第一响应消息。该第一响应消息用于指示网络切片实例化的结果。具体地，在一种实现方式中，该第一响应消息可包括至少一个比特信息。例如，采用1bit来指示网络切片实例化的结果，“0”指示网络切片实例化失败，“1”指示网络切片实例化成功，或者“0”指示网络切片实例化成功，“1”指示网络切片实例化成功。在另一种实现方式中，该第一响应消息可包括网络切片生命周期操作事件标识(life cycle operation occurrence id)，该标识用于指示 NSMF发生了网络切片实例化这一生命周期操作事件，例如该标识是一个事件编号。
在另一个实施例中，该第一网络设备可以为NSMF实体或者具备网络切片管理功能的设备，该第二网络设备可以为NSSMF实体或者具备网络切片子网管理功能的设备；或者该第一网络设备可以为CSMF实体或者具备通信服务管理功能的设备，该第二网络设备可以为NSSMF实体或者具备网络切片子网管理功能的设备。第二网络设备接收到第一请求消息后，若第一请求消息中包括NSSI ID和NSS flavor ID，则对NSSI ID对应的网络切片子网进行实例化。具体地，对NSS flavor ID所对应的网络切片子网的构成元素(例如，网络功能)创建和配置好相关的资源(例如，计算资源，存储资源，传输资源等)，使其满足该NSS flavor ID所代表的网络切片子网能力(例如，SLA或者KPI)。如果第一请求消息中包含有被重用的网络切片子网实例，则对该被重用的网络切片子网实例进行重新配置，使其满足NSS flavor ID所代表的网络切片子网能力。
在一个示例中，如图4所示，以第一网络设备为NSMF，第二网络设备为NSSMF为例，说明本申请所提出的通信方法，该方法可包括以下步骤：
S401，NSMF向NSSMF发送第一请求消息。
在这里，该第一请求消息可以称为网络切片子网实例化请求消息。该第一请求消息包括网络切片子网实例的标识，例如NSSI ID，以及还包括网络切片子网规格的标识NSS flavor ID。可选地，还可包括重用的网络切片子网实例的标识。
S402，NSSMF接收该第一请求消息，NSSMF向NSMF发送第一响应消息。
NSMF和NSSMF中预先存储了网络切片子网模板，而网络切片子网实例的标识是基于网络切片子网模板创建的，因此，在进行网络切片子网实例化时，NSSMF根据第一请求消息中携带的网络切片子网规格的标识，可以在网络切片子网模板中找到与该网络切片子网规格的标识对应的该种网络切片子网的结构、配置、网络能力等，从而进行网络切片子网实例化。
NSMF接收该第一响应消息。NSMF根据该第一响应消息，可以了解网络切片子网实例化是否成功；如果没有成功，则可以发起新的请求消息。
在这里，该第一响应消息可以称为网络切片子网实例化响应消息。该第一响应消息用于指示网络切片子网实例化的结果。
该第一响应消息用于指示网络切片子网实例化的结果。具体地，在一种实现方式中，该第一响应消息可包括至少一个比特信息。例如，采用1bit来指示网络切片子网实例化的结果，“0”指示网络切片子网实例化失败，“1”指示网络切片子网实例化成功，或者“0”指示网络切片子网实例化成功，“1”指示网络切片子网实例化成功。在另一种实现方式中，该第一响应消息可包括网络切片子网生命周期操作事件标识(life cycle operation occurrence id)，该标识用于指示NSSMF发生了网络切片子网实例化这一生命周期操作事件，例如该标识是一个事件编号。
在另一个示例中，如图5所示，以第一网络设备为CSMF，第二网络设备为NSSMF为例，说明本申请所提出的通信方法，该方法可包括以下步骤：
S501，CSMF向NSSMF发送第一请求消息。
在这里，该第一请求消息可以称为网络切片子网实例化请求消息。该第一请求消息包 括网络切片子网实例的标识(例如，NSSI ID)，以及还包括网络切片子网规格的标识(例如，NSS flavor ID)。可选地，还可包括重用的网络切片子网实例的标识。
S502，NSSMF接收该第一请求消息，NSSMF向CSMF发送第一响应消息。
CSMF和NSSMF中预先存储了网络切片子网模板，而网络切片子网实例的标识是基于网络切片子网模板创建的，因此，在进行网络切片子网实例化时，NSSMF根据第一请求消息中携带的网络切片子网规格的标识，可以在网络切片子网模板中找到与该网络切片子网规格的标识对应的该种网络切片子网的结构、配置、网络能力等，从而进行网络切片子网实例化。
CSMF接收该第一响应消息。CSMF根据该第一响应消息，可以了解网络切片子网实例化是否成功；如果没有成功，则可以发起新的请求消息。
在这里，该第一响应消息可以称为网络切片子网实例化响应消息。该第一响应消息用于指示网络切片子网实例化的结果。
该第一响应消息用于指示网络切片子网实例化的结果。具体地，在一种实现方式中，该第一响应消息可包括至少一个比特信息。例如，采用1bit来指示网络切片子网实例化的结果，“0”指示网络切片子网实例化失败，“1”指示网络切片子网实例化成功，或者“0”指示网络切片子网实例化成功，“1”指示网络切片子网实例化成功。在另一种实现方式中，该第一响应消息可包括网络切片子网生命周期操作事件标识(life cycle operation occurrence id)，该标识用于指示NSSMF发生了网络切片子网实例化这一生命周期操作事件，例如该标识是一个事件编号。
根据本发明实施例提供的一种通信方法，第一网络设备在请求消息中携带切片实例的标识(例如，NSI ID或NSSI ID)和切片规格标识(例如，NS flavor ID或NSS flavor ID)，第二网络设备可根据切片实例的标识获取预存的切片模板，并结合切片规格标识，对该切片进行实例化，较大地节省了实例化过程中的信令开销。
上面描述了网络切片或网络切片子网实例化的过程，在实例化过程之前，需要创建网络切片实例的标识或网络切片子网实例的标识。
本申请的又一实施例提供一种通信方法，在创建NSI ID、NSSI ID的时候，可以不需要将网络切片的需求的所有参数，或者网络切片子网的需求的所有参数发送给对应的NSMF、NSSMF，而只需要发送网络切片模板的标识或网络切片子网模板的标识，从而降低了信令传输的开销。
图6为本发明实施例提供的另一种通信方法的交互流程示意图，该方法可包括以下步骤：
S601，第一网络设备向第二网络设备发送第二请求消息。其中，该第二请求消息包括至少一个网络切片模板的标识或者至少一个网络切片子网模板的标识。该第二请求消息用于请求创建网络切片实例的标识或用于请求创建网络切片子网实例的标识。该第二请求消息可以称为网络切片标识创建请求消息，或网络切片子网标识创建请求消息，也可以是其它的名称，在此不作限制。
第一网络设备和第二网络设备预先已保存了网络切片模板或网络切片子网模板，且网络切片模板采用网络切片模板的标识进行唯一标识，网络切片子网模板采用网络切片子网 模板的标识进行唯一标识。因而第二请求消息中只需要携带网络切片模板的标识或网络切片子网模板的标识，而不需要将网络切片的需求的所有参数，或者网络切片子网的需求的所有参数发送给对应的NSMF、NSSMF。因而，可以节省信令开销。
S602，第二网络设备接收来自第一网络设备的第二请求消息，所述第二网络设备向所述第一网络设备发送第二响应消息。
第二网络设备根据第二请求消息中携带的模板的标识，采用第二网络设备中保存的与该标识对应的模板，创建网络切片实例的标识或创建网络切片子网实例的标识，并通过第二响应消息发送网络切片实例的标识或网络切片子网实例的标识给第一网络设备。即该第二响应消息包括所述至少一个网络切片实例的标识或者至少一个网络切片子网实例的标识。该第二响应消息可以称为网络切片标识创建响应消息，或网络切片子网标识创建响应消息，也可以是其它的名称，在此不作限制。现有技术中，响应消息中并未携带有创建好的网络切片实例的标识或网络切片子网实例的标识，即NSI ID、NSSI ID。从而造成CSMF不知道支持其通信服务相关需求的是哪一个或哪几个NSI和/或NSSI，NSMF不知道支持其网络切片相关需求的是哪一个或哪几个NSSI，为后续的网络切片管理带来不便。例如，当一个通信服务需要多个NSI共同完成，并且通信服务的需求发生变化时，CSMF只能将相对应的网络切片相关需求发送给NSMF，由NSMF决定更新相关的NSI，而CSMF不能决定更新哪个具体的NSI。本实施例中，第二网络设备通过在响应消息中携带创建好的网络切片实例的标识或网络切片子网实例的标识，从而可以提供准确的基于网络切片的服务。
所述第一网络设备接收来自所述第二网络设备的第二响应消息。
进一步地，所述至少一个网络切片实例的标识是根据所述至少一个网络切片模板创建，所述至少一个网络切片子网实例的标识是根据所述至少一个网络切片子网模板创建。
进一步地，所述第二请求消息还包括自定义的至少一个网络切片实例的名称或至少一个网络切片子网实例的名称。该自定义的名称即用户根据个人使用习惯或喜好等定义的名称。其中，所述自定义的至少一个网络切片实例的名称与所述至少一个网络切片实例的标识对应，即可用自定义的网络切片实例的名称作为网络切片实例的标识；所述自定义的至少一个网络切片子网实例的名称与所述至少一个网络切片子网实例的标识对应，即可用自定义的网络切片子网实例的名称作为网络切片子网实例的标识。这样使得实例的名称易记。
如图1所示的网络切片管理***的结构示意图，CSMF、NSMF和NSSMF之间都可以通信。其中，所述第一网络设备可以为CSMF实体或者具备通信服务管理功能的设备，所述第二网络设备包括NSMF实体或者具备网络切片管理功能的设备，和NSSMF实体或者具备网络切片子网管理功能的设备；或所述第一网络设备包括NSMF实体或者具备网络切片管理功能的设备，所述第二网络设备包括NSSMF实体或者具备网络切片子网管理功能的设备。
下面以第一、第二网络设备分别为以上不同的功能实体或设备进行示例描述：
一种场景下，NSMF需要知道NSI由哪些NSSI所构成。图7以第一网络设备为NSMF实体，第二网络设备为NSSMF实体为例，对本申请所提出的另一种通信方法进行说明，该方法可包括以下步骤：
S701，NSMF发送第二请求消息给NSSMF。
在这里，该第二请求消息可以称为网络切片子网标识创建请求消息。该第二请求消息包括网络切片子网模板的标识，例如NSST ID或NSSD ID。
可选地，该第二请求消息还可包括自定义的网络切片子网实例的名称。
S702，NSSMF接收该第二请求消息。NSSMF发送第二响应消息给NSMF。
在这里，该第二响应消息可以称为网络切片子网标识创建响应消息。该第二响应消息包括网络切片子网实例的标识，如NSSI ID。
具体地，NSMF和NSSMF均预先保存了多个网络切片子网模板，且采用网络切片子网模板标识唯一标识一个网络切片子网模板。NSSMF根据第二请求消息中包括的网络切片子网模板标识，创建网络切片子网实例的标识。NSSMF发送第二响应消息给NSMF，在该第二响应消息中携带网络切片子网实例的标识。
NSMF接收该第二响应消息。NSMF根据该第二响应消息，可以了解网络切片子网实例的标识是否创建成功；如果没有成功，则可以发起新的请求消息。
需要说明的是，NSSMF不需要在创建网络切片子网实例的标识的同时，配置好该网络切片子网实例的相关的资源，而在需要使用该网络切片子网实例时再进行资源的配置，从而可以避免资源的浪费。
另一种场景下，CSMF需要知道通信服务由哪些NSI所构成。图8以第一网络设备为CSMF实体，第二网络设备为NSMF实体为例，对本申请所提出的另一种通信方法进行说明，该方法可包括以下步骤：
S801，CSMF发送第二请求消息给NSMF。
在这里，该第二请求消息可以称为网络切片标识创建请求消息。该第二请求消息包括网络切片模板的标识，例如NST ID或NSD ID。
可选地，该第二请求消息还可包括自定义的网络切片实例的名称。
S802，NSMF接收该第二请求消息。NSMF发送第二响应消息给CSMF。
在这里，该第二响应消息可以称为网络切片标识创建响应消息。该第二响应消息包括网络切片实例的标识，如NSI ID。
具体地，CSMF和NSMF均预先保存了多个网络切片模板，且采用网络切片模板标识唯一标识一个网络切片模板。NSMF根据第二请求消息中包括的网络切片模板标识，创建网络切片实例的标识。NSMF发送第二响应消息给CSMF，在该第二响应消息中携带网络切片实例的标识。
CSMF接收该第二响应消息。CSMF根据该第二响应消息，可以了解网络切片实例的标识是否创建成功；如果没有成功，则可以发起新的请求消息。
需要说明的是，NSMF不需要在创建网络切片实例的标识的同时，配置好该网络切片实例的相关的资源，而在需要使用该网络切片实例时再进行资源的配置，从而可以避免资源的浪费。
又一种场景下，CSMF需要知道通信服务由哪些NSSI所构成。图9以第一网络设备为CSMF实体，第二网络设备为NSSMF实体为例，对本申请所提出的另一种通信方法进行说明，该方法可包括以下步骤：
S901，CSMF发送第二请求消息给NSSMF。
在这里，该第二请求消息可以称为网络切片子网标识创建请求消息。该第二请求消息包括网络切片子网模板的标识，例如NSST ID或NSSD ID。
可选地，该第二请求消息还可包括自定义的网络切片子网实例的名称。
S902，NSSMF接收该第二请求消息。NSSMF发送第二响应消息给CSMF。
在这里，该第二响应消息可以称为网络切片子网标识创建响应消息。该第二响应消息包括网络切片子网实例的标识，如NSSI ID。
具体地，CSMF和NSSMF均预先保存了多个网络切片子网模板，且采用网络切片子网模板标识唯一标识一个网络切片子网模板。NSSMF根据第二请求消息中包括的网络切片子网模板标识，创建网络切片子网实例的标识。NSSMF发送第二响应消息给CSMF，在该第二响应消息中携带网络切片子网实例的标识。
CSMF接收该第二响应消息。CSMF根据该第二响应消息，可以了解网络切片子网实例的标识是否创建成功；如果没有成功，则可以发起新的请求消息。
需要说明的是，NSSMF不需要在创建网络切片子网实例的标识的同时，配置好该网络切片子网实例的相关的资源，而在需要使用该网络切片子网实例时再进行资源的配置，从而可以避免资源的浪费。
根据本发明实施例提供的一种通信方法，在创建NSI ID、NSSI ID的时候，不需要将网络切片的需求的所有参数，或者网络切片子网的需求的所有参数发送给对应的NSMF、NSSMF，而只需要发送网络切片模板的标识或网络切片子网模板的标识，从而降低了信令传输的开销。
上述详细阐述了本发明实施例的方法，下面提供了本发明实施例的装置。
图10为本发明实施例提供的一种通信装置的结构示意图，该通信装置1000可包括：发送单元101和接收单元102；其中：
发送单元101，用于向第一网络设备发送第一请求消息，第一请求消息用于请求对至少一个网络切片或至少一个网络切片子网进行实例化，所述第一请求消息包括所述至少一个网络切片实例的标识和所述至少一个网络切片规格的标识，或所述第一请求消息包括所述至少一个网络切片子网实例的标识和所述至少一个网络切片子网规格的标识；
接收单元102，用于接收来自所述第一网络设备的第一响应消息，所述第一响应消息用于指示所述至少一个网络切片实例化的结果，或所述第一响应消息用于指示所述至少一个网络切片子网实例化的结果。
进一步地，每个网络切片规格代表了每个网络切片的以下参数中的至少一种：网络切片的结构、配置和网络能力；或每个网络切片子网规格代表了每个网络切片子网的以下参数中的至少一种：网络切片子网的结构、配置和网络能力。
进一步地，所述第一请求消息还包括重用的至少一个网络切片实例的标识；或所述第一请求消息还包括重用的至少一个网络切片子网实例的标识。
进一步地，所述第一响应消息包括以下信息中的至少一种：用于指示所述至少一个网络切片实例化结果的至少一个比特信息，或所述至少一个网络切片生命周期操作事件的标识；或所述第一响应消息包括以下信息中的至少一种：用于指示所述至少一个网络切片子网实例化结果的至少一个比特信息，或所述第一响应消息包括所述至少一个网络切片子网 生命周期操作事件的标识。
进一步地，所述通信装置为通信服务管理功能或者具备通信服务管理功能的设备，所述第一网络设备为网络切片管理功能或者具备网络切片管理功能的设备；或所述通信装置为通信服务管理功能或者具备通信服务管理功能的设备，所述第一网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备；或所述通信装置为网络切片管理功能或者具备网络切片管理功能的设备，所述第一网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备。
根据本发明实施例提供的一种通信装置，该通信装置1000在请求消息中携带切片实例的标识和切片规格标识，第一网络设备可根据切片实例的标识获取预存的切片模板，并结合切片规格标识，对该切片进行实例化，较大地节省了实例化过程中的信令开销。
图11为本发明实施例提供的另一种通信装置的结构示意图，该通信装置1100可包括：接收单元111和发送单元112；其中：
接收单元111，用于接收来自第一网络设备的第一请求消息，第一请求消息用于请求对至少一个网络切片或至少一个网络切片子网进行实例化，所述第一请求消息包括所述至少一个网络切片实例的标识和所述至少一个网络切片规格的标识，或所述第一请求消息包括所述至少一个网络切片子网实例的标识和所述至少一个网络切片子网规格的标识；
发送单元112，用于发送第一响应消息给所述第一网络设备，所述第一响应消息用于指示所述至少一个网络切片实例化的结果，或所述第一响应消息用于指示所述至少一个网络切片子网实例化的结果。
进一步地，每个网络切片规格代表了每个网络切片的以下参数中的至少一种：网络切片的结构、配置和网络能力；或每个网络切片子网规格代表了每个网络切片子网的以下参数中的至少一种：网络切片子网的结构、配置和网络能力。
进一步地，所述第一请求消息还包括重用的至少一个网络切片实例的标识；或所述第一请求消息还包括重用的至少一个网络切片子网实例的标识。
进一步地，所述第一响应消息包括以下信息中的至少一种：用于指示所述至少一个网络切片实例化结果的至少一个比特信息，或所述至少一个网络切片生命周期操作事件的标识；或所述第一响应消息包括以下信息中的至少一种：用于指示所述至少一个网络切片子网实例化结果的至少一个比特信息，或所述第一响应消息包括所述至少一个网络切片子网生命周期操作事件的标识。
进一步地，所述通信装置为网络切片管理功能或者具备网络切片管理功能的设备，所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备；或所述通信装置为网络切片子网管理功能或者具备网络切片子网管理功能的设备，所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备；或所述通信装置为网络切片子网管理功能或者具备网络切片子网管理功能的设备，所述第一网络设备为网络切片管理功能或者具备网络切片管理功能的设备。
根据本发明实施例提供的一种通信装置，第一网络设备在请求消息中携带切片实例的标识和切片规格标识，该通信装置1100可根据切片实例的标识获取预存的切片模板，并结合切片规格标识，对该切片进行实例化，较大地节省了实例化过程中的信令开销。
图12为本发明实施例提供的又一种通信装置的结构示意图，该通信装置1200可包括：发送单元121和接收单元122；其中：
发送单元121，用于向第一网络设备发送第一请求消息，所述第一请求消息包括至少一个网络切片模板的标识或者至少一个网络切片子网模板的标识；
接收单元122，用于接收来自所述第一网络设备的第一响应消息，所述第一响应消息包括所述至少一个网络切片实例的标识或者至少一个网络切片子网实例的标识。
进一步地，所述至少一个网络切片实例的标识是根据所述至少一个网络切片模板创建，所述至少一个网络切片子网实例的标识是根据所述至少一个网络切片子网模板创建。
进一步地，所述第一请求消息还包括自定义的至少一个网络切片实例的名称或至少一个网络切片子网实例的名称，其中，所述自定义的至少一个网络切片实例的名称与所述至少一个网络切片实例的标识对应，所述自定义的至少一个网络切片子网实例的名称与所述至少一个网络切片子网实例的标识对应。
进一步地，所述通信装置为通信服务管理功能或者具备通信服务管理功能的设备，所述第一网络设备为网络切片管理功能或者具备网络切片管理功能的设备；或所述通信装置为通信服务管理功能或者具备通信服务管理功能的设备，所述第一网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备；或所述通信装置为网络切片管理功能或者具备网络切片管理功能的设备，所述第一网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备。
根据本发明实施例提供的一种通信装置，在创建NSI ID、NSSI ID的时候，通信装置1200可以不需要将网络切片的需求的所有参数，或者网络切片子网的需求的所有参数发送给第一网络设备，而只需要发送网络切片模板的标识或网络切片子网模板的标识，从而降低了信令传输的开销。
图13为本发明实施例提供的又一种通信装置的结构示意图，该通信装置1300可包括：接收单元131和发送单元132；其中：
接收单元131，用于接收来自第一网络设备的第一请求消息，所述第一请求消息包括至少一个网络切片模板的标识或者至少一个网络切片子网模板的标识；
发送单元132，用于向所述第一网络设备发送第一响应消息，所述第一响应消息包括所述至少一个网络切片实例的标识或者至少一个网络切片子网实例的标识。
进一步地，所述至少一个网络切片实例的标识是根据所述至少一个网络切片模板创建，所述至少一个网络切片子网实例的标识是根据所述至少一个网络切片子网模板创建。
进一步地，所述第一请求消息还包括自定义的至少一个网络切片实例的名称或至少一个网络切片子网实例的名称，其中，所述自定义的至少一个网络切片实例的名称与所述至少一个网络切片实例的标识对应，所述自定义的至少一个网络切片子网实例的名称与所述至少一个网络切片子网实例的标识对应。
进一步地，所述通信装置为网络切片管理功能或者具备网络切片管理功能的设备，所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备；或所述通信装置为网络切片子网管理功能或者具备网络切片子网管理功能的设备，所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备；或所述通信装置为网络切片子网管理 功能或者具备网络切片子网管理功能的设备，所述第一网络设备为网络切片管理功能或者具备网络切片管理功能的设备。
根据本发明实施例提供的一种通信装置，在创建NSI ID、NSSI ID的时候，第一网络设备可以不需要将网络切片的需求的所有参数，或者网络切片子网的需求的所有参数发送给所述通信装置，而只需要发送网络切片模板的标识或网络切片子网模板的标识，从而降低了信令传输的开销。
本发明实施例还提供一种通信装置，该通信装置可以是上述通信***中的第一网络设备，该通信装置可以采用图14所示的硬件架构。该通信装置可以包括接收器、发射器、存储器和处理器，所述接收器、发射器、存储器和处理器通过总线相互连接。图10中的发送单元101所实现的相关功能可以由发射器来实现，接收单元102所实现的相关功能可以由接收器来实现。
存储器包括但不限于是随机存储记忆体(Random Access Memory，RAM)、只读存储器(Read-Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable Read Only Memory，EPROM)、或便携式只读存储器(Compact Disc Read-Only Memory，CD-ROM)，该存储器用于相关指令及数据。
接收器用于接收数据和/或信号，以及发射器用于发送数据和/或信号。发射器和接收器可以是独立的器件，也可以是一个整体的器件。
处理器可以包括是一个或多个处理器，例如包括一个或多个中央处理器(Central Processing Unit，CPU)，在处理器是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。
存储器用于存储网络设备的程序代码和数据。
发射器，用于向第二网络设备发送第一请求消息，例如执行图2所示实施例中的S201；接收器，用于接收来自所述第二网络设备的第一响应消息，例如执行图2所示实施例中的S202。
具体可参见方法实施例中的描述，在此不再赘述。
本发明实施例还提供一种通信装置，该通信装置可以是上述通信***中的第二网络设备，该通信装置可以采用图14所示的硬件架构。该通信装置可以包括接收器、发射器、存储器和处理器，所述接收器、发射器、存储器和处理器通过总线相互连接。图11中的接收单元111所实现的相关功能可以由接收器来实现，发送单元112所实现的相关功能可以由发射器来实现。
存储器包括但不限于是RAM、ROM、EPROM、或CD-ROM，该存储器用于相关指令及数据。
接收器用于接收数据和/或信号，以及发射器用于发送数据和/或信号。发射器和接收器可以是独立的器件，也可以是一个整体的器件。
处理器可以包括是一个或多个处理器，例如包括一个或多个CPU，在处理器是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。
存储器用于存储网络设备的程序代码和数据。
接收器，用于接收来自第一网络设备的第一请求消息，例如执行图2所示实施例的 S202；发射器，用于发送第一响应消息给所述第一网络设备，例如执行图2所示实施例的S202。
具体可参见方法实施例中的描述，在此不再赘述。
本发明实施例还提供一种通信装置，该通信装置可以是上述通信***中的第一网络设备，该通信装置可以采用图14所示的硬件架构。该通信装置可以包括接收器、发射器、存储器和处理器，所述接收器、发射器、存储器和处理器通过总线相互连接。图12中的发送单元121所实现的相关功能可以由发射器来实现，接收单元122所实现的相关功能可以由接收器来实现。
存储器包括但不限于是RAM、ROM、EPROM、或CD-ROM，该存储器用于相关指令及数据。
接收器用于接收数据和/或信号，以及发射器用于发送数据和/或信号。发射器和接收器可以是独立的器件，也可以是一个整体的器件。
处理器可以包括是一个或多个处理器，例如包括一个或多个CPU，在处理器是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。
存储器用于存储网络设备的程序代码和数据。
发射器，用于向第二网络设备发送第二请求消息，例如执行图6所示实施例的S601；接收器，用于接收来自所述第二网络设备的第二响应消息，例如执行图6所示实施例的S602。
具体可参见方法实施例中的描述，在此不再赘述。
本发明实施例还提供一种通信装置，该通信装置可以是上述通信***中的第二网络设备，该通信装置可以采用图14所示的硬件架构。该通信装置可以包括接收器、发射器、存储器和处理器，所述接收器、发射器、存储器和处理器通过总线相互连接。图13中的接收单元131所实现的相关功能可以由接收器来实现，发送单元132所实现的相关功能可以由发射器来实现。
存储器包括但不限于是RAM、ROM、EPROM、或CD-ROM，该存储器用于相关指令及数据。
接收器用于接收数据和/或信号，以及发射器用于发送数据和/或信号。发射器和接收器可以是独立的器件，也可以是一个整体的器件。
处理器可以包括是一个或多个处理器，例如包括一个或多个CPU，在处理器是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。
存储器用于存储网络设备的程序代码和数据。
接收器，用于接收来自第一网络设备的第二请求消息，例如执行图6所示实施例的S602；发射器，用于向所述第一网络设备发送第二响应消息，例如执行图6所示实施例的S602。
具体可参见方法实施例中的描述，在此不再赘述。
可以理解的是，图14仅仅示出了通信装置的简化设计。在实际应用中，通信装置还可以分别包含必要的其他元件，包含但不限于任意数量的收发器、处理器、控制器、存储器等，而所有可以实现本发明实施例的通信装置都在本发明的保护范围之内。
本申请的又一方面提供了一种通信***，包括上述第一网络设备和第二网络设备。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，数字通用光盘(digital versatile disc，DVD))、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：只读存储器(read-only memory，ROM)或随机存储存储器(random access memory，RAM)、磁碟或者光盘等各种可存储程序代码的介质。

Claims (32)

  1. 一种通信方法，其特征在于，包括：
    第一网络设备向第二网络设备发送第一请求消息，第一请求消息用于请求对至少一个网络切片或至少一个网络切片子网进行实例化，所述第一请求消息包括所述至少一个网络切片实例的标识和所述至少一个网络切片规格的标识，或所述第一请求消息包括所述至少一个网络切片子网实例的标识和所述至少一个网络切片子网规格的标识；
    所述第一网络设备接收来自所述第二网络设备的第一响应消息，所述第一响应消息用于指示所述至少一个网络切片实例化的结果，或所述第一响应消息用于指示所述至少一个网络切片子网实例化的结果。
  2. 一种通信方法，其特征在于，包括：
    第二网络设备接收来自第一网络设备的第一请求消息，第一请求消息用于请求对至少一个网络切片或至少一个网络切片子网进行实例化，所述第一请求消息包括所述至少一个网络切片实例的标识和所述至少一个网络切片规格的标识，或所述第一请求消息包括所述至少一个网络切片子网实例的标识和所述至少一个网络切片子网规格的标识；
    所述第二网络设备发送第一响应消息给所述第一网络设备，所述第一响应消息用于指示所述至少一个网络切片实例化的结果，或所述第一响应消息用于指示所述至少一个网络切片子网实例化的结果。
  3. 如权利要求1或2所述的方法，其特征在于，每个网络切片规格代表了每个网络切片的以下参数中的至少一种：网络切片的结构、配置和网络能力；或每个网络切片子网规格代表了每个网络切片子网的以下参数中的至少一种：网络切片子网的结构、配置和网络能力。
  4. 如权利要求1～3任一项所述的方法，其特征在于，所述第一请求消息还包括重用的至少一个网络切片实例的标识；或所述第一请求消息还包括重用的至少一个网络切片子网实例的标识。
  5. 如权利要求1～4任一项所述的方法，其特征在于，所述第一响应消息包括以下信息中的至少一种：用于指示所述至少一个网络切片实例化结果的至少一个比特信息，或所述至少一个网络切片生命周期操作事件的标识；或所述第一响应消息包括以下信息中的至少一种：用于指示所述至少一个网络切片子网实例化结果的至少一个比特信息，或所述第一响应消息包括所述至少一个网络切片子网生命周期操作事件的标识。
  6. 一种通信方法，其特征在于，包括：
    第一网络设备向第二网络设备发送第一请求消息，所述第一请求消息包括至少一个网络切片模板的标识或者至少一个网络切片子网模板的标识；
    所述第一网络设备接收来自所述第二网络设备的第一响应消息，所述第一响应消息包括所述至少一个网络切片实例的标识或者至少一个网络切片子网实例的标识。
  7. 一种通信方法，其特征在于，包括：
    第二网络设备接收来自第一网络设备的第一请求消息，所述第一请求消息包括至少一 个网络切片模板的标识或者至少一个网络切片子网模板的标识；
    所述第二网络设备向所述第一网络设备发送第一响应消息，所述第一响应消息包括所述至少一个网络切片实例的标识或者至少一个网络切片子网实例的标识。
  8. 如权利要求6或7所述的方法，其特征在于，所述至少一个网络切片实例的标识是根据所述至少一个网络切片模板创建，所述至少一个网络切片子网实例的标识是根据所述至少一个网络切片子网模板创建。
  9. 如权利要求6～7任一项所述的方法，其特征在于，所述第一请求消息还包括自定义的至少一个网络切片实例的名称或至少一个网络切片子网实例的名称，其中，所述自定义的至少一个网络切片实例的名称与所述至少一个网络切片实例的标识对应，所述自定义的至少一个网络切片子网实例的名称与所述至少一个网络切片子网实例的标识对应。
  10. 如权利要求1～9任一项所述的方法，其特征在于，所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备，所述第二网络设备为网络切片管理功能或者具备网络切片管理功能的设备；或所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备，所述第二网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备；或所述第一网络设备为网络切片管理功能或者具备网络切片管理功能的设备，所述第二网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备。
  11. 一种通信装置，其特征在于，包括：
    发射器，用于向第一网络设备发送第一请求消息，第一请求消息用于请求对至少一个网络切片或至少一个网络切片子网进行实例化，所述第一请求消息包括所述至少一个网络切片实例的标识和所述至少一个网络切片规格的标识，或所述第一请求消息包括所述至少一个网络切片子网实例的标识和所述至少一个网络切片子网规格的标识；
    接收器，用于接收来自所述第一网络设备的第一响应消息，所述第一响应消息用于指示所述至少一个网络切片实例化的结果，或所述第一响应消息用于指示所述至少一个网络切片子网实例化的结果。
  12. 如权利要求11所述的通信装置，其特征在于，每个网络切片规格代表了每个网络切片的以下参数中的至少一种：网络切片的结构、配置和网络能力；或每个网络切片子网规格代表了每个网络切片子网的以下参数中的至少一种：网络切片子网的结构、配置和网络能力。
  13. 如权利要求11或12所述的通信装置，其特征在于，所述第一请求消息还包括重用的至少一个网络切片实例的标识；或所述第一请求消息还包括重用的至少一个网络切片子网实例的标识。
  14. 如权利要求11～13任一项所述的通信装置，其特征在于，所述第一响应消息包括以下信息中的至少一种：用于指示所述至少一个网络切片实例化结果的至少一个比特信息，或所述至少一个网络切片生命周期操作事件的标识；或所述第一响应消息包括以下信息中的至少一种：用于指示所述至少一个网络切片子网实例化结果的至少一个比特信息，或所述第一响应消息包括所述至少一个网络切片子网生命周期操作事件的标识。
  15. 如权利要求11～14任一项所述的通信装置，其特征在于，所述通信装置为通信服务管理功能或者具备通信服务管理功能的设备，所述第一网络设备为网络切片管理功能或 者具备网络切片管理功能的设备；或所述通信装置为通信服务管理功能或者具备通信服务管理功能的设备，所述第一网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备；或所述通信装置为网络切片管理功能或者具备网络切片管理功能的设备，所述第一网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备。
  16. 一种通信装置，其特征在于，包括：
    接收器，用于接收来自第一网络设备的第一请求消息，第一请求消息用于请求对至少一个网络切片或至少一个网络切片子网进行实例化，所述第一请求消息包括所述至少一个网络切片实例的标识和所述至少一个网络切片规格的标识，或所述第一请求消息包括所述至少一个网络切片子网实例的标识和所述至少一个网络切片子网规格的标识；
    发射器，用于发送第一响应消息给所述第一网络设备，所述第一响应消息用于指示所述至少一个网络切片实例化的结果，或所述第一响应消息用于指示所述至少一个网络切片子网实例化的结果。
  17. 如权利要求16所述的通信装置，其特征在于，每个网络切片规格代表了每个网络切片的以下参数中的至少一种：网络切片的结构、配置和网络能力；或每个网络切片子网规格代表了每个网络切片子网的以下参数中的至少一种：网络切片子网的结构、配置和网络能力。
  18. 如权利要求16或17所述的通信装置，其特征在于，所述第一请求消息还包括重用的至少一个网络切片实例的标识；或所述第一请求消息还包括重用的至少一个网络切片子网实例的标识。
  19. 如权利要求16～18任一项所述的通信装置，其特征在于，所述第一响应消息包括以下信息中的至少一种：用于指示所述至少一个网络切片实例化结果的至少一个比特信息，或所述至少一个网络切片生命周期操作事件的标识；或所述第一响应消息包括以下信息中的至少一种：用于指示所述至少一个网络切片子网实例化结果的至少一个比特信息，或所述第一响应消息包括所述至少一个网络切片子网生命周期操作事件的标识。
  20. 如权利要求16～19任一项所述的通信装置，其特征在于，所述通信装置为网络切片管理功能或者具备网络切片管理功能的设备，所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备；或所述通信装置为网络切片子网管理功能或者具备网络切片子网管理功能的设备，所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备；或所述通信装置为网络切片子网管理功能或者具备网络切片子网管理功能的设备，所述第一网络设备为网络切片管理功能或者具备网络切片管理功能的设备。
  21. 一种通信装置，其特征在于，包括：
    发射器，用于向第一网络设备发送第一请求消息，所述第一请求消息包括至少一个网络切片模板的标识或者至少一个网络切片子网模板的标识；
    接收器，用于接收来自所述第一网络设备的第一响应消息，所述第一响应消息包括所述至少一个网络切片实例的标识或者至少一个网络切片子网实例的标识。
  22. 如权利要求21所述的通信装置，其特征在于，所述至少一个网络切片实例的标识是根据所述至少一个网络切片模板创建，所述至少一个网络切片子网实例的标识是根据所述至少一个网络切片子网模板创建。
  23. 如权利要求21或22所述的通信装置，其特征在于，所述第一请求消息还包括自定义的至少一个网络切片实例的名称或至少一个网络切片子网实例的名称，其中，所述自定义的至少一个网络切片实例的名称与所述至少一个网络切片实例的标识对应，所述自定义的至少一个网络切片子网实例的名称与所述至少一个网络切片子网实例的标识对应。
  24. 如权利要求21～23任一项所述的通信装置，其特征在于，所述通信装置为通信服务管理功能或者具备通信服务管理功能的设备，所述第一网络设备为网络切片管理功能或者具备网络切片管理功能的设备；或所述通信装置为通信服务管理功能或者具备通信服务管理功能的设备，所述第一网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备；或所述通信装置为网络切片管理功能或者具备网络切片管理功能的设备，所述第一网络设备为网络切片子网管理功能或者具备网络切片子网管理功能的设备。
  25. 一种通信装置，其特征在于，包括：
    接收器，用于接收来自第一网络设备的第一请求消息，所述第一请求消息包括至少一个网络切片模板的标识或者至少一个网络切片子网模板的标识；
    发射器，用于向所述第一网络设备发送第一响应消息，所述第一响应消息包括所述至少一个网络切片实例的标识或者至少一个网络切片子网实例的标识。
  26. 如权利要求25所述的通信装置，其特征在于，所述至少一个网络切片实例的标识是根据所述至少一个网络切片模板创建，所述至少一个网络切片子网实例的标识是根据所述至少一个网络切片子网模板创建。
  27. 如权利要求25或26所述的通信装置，其特征在于，所述第一请求消息还包括自定义的至少一个网络切片实例的名称或至少一个网络切片子网实例的名称，其中，所述自定义的至少一个网络切片实例的名称与所述至少一个网络切片实例的标识对应，所述自定义的至少一个网络切片子网实例的名称与所述至少一个网络切片子网实例的标识对应。
  28. 如权利要求25～27任一项所述的通信装置，其特征在于，所述通信装置为网络切片管理功能或者具备网络切片管理功能的设备，所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备；或所述通信装置为网络切片子网管理功能或者具备网络切片子网管理功能的设备，所述第一网络设备为通信服务管理功能或者具备通信服务管理功能的设备；或所述通信装置为网络切片子网管理功能或者具备网络切片子网管理功能的设备，所述第一网络设备为网络切片管理功能或者具备网络切片管理功能的设备。
  29. 一种通信装置，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其特征在于，所述处理器执行所述计算机程序时实现如权利要求1至10中任一项所述的方法。
  30. 一种通信装置，其特征在于，包括处理器，所述处理器用于与存储器耦合，并读取存储器中的指令，并根据所述指令实现如权利要求1至10中任一项所述的方法。
  31. 一种计算机程序产品，用于当在计算设备上执行时，执行根据权利要求1至10中任一项所述的方法。
  32. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，该程序被处理器执行时实现如权利要求1至10中任一项所述的方法。
PCT/CN2018/106653 2017-09-30 2018-09-20 通信方法及装置 WO2019062634A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710944937.8A CN109600769B (zh) 2017-09-30 2017-09-30 通信方法及装置
CN201710944937.8 2017-09-30

Publications (1)

Publication Number Publication Date
WO2019062634A1 true WO2019062634A1 (zh) 2019-04-04

Family

ID=65900799

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/106653 WO2019062634A1 (zh) 2017-09-30 2018-09-20 通信方法及装置

Country Status (2)

Country Link
CN (1) CN109600769B (zh)
WO (1) WO2019062634A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020253344A1 (zh) * 2019-06-17 2020-12-24 华为技术有限公司 一种授权控制的方法、装置以及存储介质
CN114025392A (zh) * 2020-07-15 2022-02-08 中移物联网有限公司 网络切片创建方法及相关设备
CN114827980A (zh) * 2021-01-21 2022-07-29 ***通信有限公司研究院 Nssi更新方法、装置及nssmf实体

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114071657A (zh) * 2020-07-31 2022-02-18 中移(苏州)软件技术有限公司 网络切片的处理方法、装置和存储介质
CN114640588B (zh) * 2020-11-30 2024-05-31 ***通信有限公司研究院 一种网络切片业务的处理方法及相关设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170142591A1 (en) * 2015-11-13 2017-05-18 Huawei Technologies Co., Ltd. System and methods for network management and orchestration for network slicing
CN107155187A (zh) * 2016-03-03 2017-09-12 华为技术有限公司 通信方法、终端设备和网络侧设备

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106550410B (zh) * 2015-09-17 2020-07-07 华为技术有限公司 一种通信控制方法和控制器、用户设备、相关装置
CN106549806B (zh) * 2016-10-26 2019-06-18 清华大学 一种网络切片管理器及其管理方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170142591A1 (en) * 2015-11-13 2017-05-18 Huawei Technologies Co., Ltd. System and methods for network management and orchestration for network slicing
CN107155187A (zh) * 2016-03-03 2017-09-12 华为技术有限公司 通信方法、终端设备和网络侧设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"TSG-SA Study on Management and Orchestration of Network Slicing for Next Generation Network", 3GPP TR 28.801 V2.0.1, 7 September 2017 (2017-09-07), XP051681235 *
"TSG-SA Study on Management and Orchestration of Network Slicing for Next Generation Network", 3GPP TR 28.801 VI.0.0, 20 March 2017 (2017-03-20) *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020253344A1 (zh) * 2019-06-17 2020-12-24 华为技术有限公司 一种授权控制的方法、装置以及存储介质
CN114025392A (zh) * 2020-07-15 2022-02-08 中移物联网有限公司 网络切片创建方法及相关设备
CN114827980A (zh) * 2021-01-21 2022-07-29 ***通信有限公司研究院 Nssi更新方法、装置及nssmf实体
CN114827980B (zh) * 2021-01-21 2024-06-07 ***通信有限公司研究院 Nssi更新方法、装置及nssmf实体

Also Published As

Publication number Publication date
CN109600769B (zh) 2022-01-11
CN109600769A (zh) 2019-04-09

Similar Documents

Publication Publication Date Title
CN109845303B (zh) 网络切片的管理方法及管理单元
CN109560955B (zh) 网络的部署信息确定方法及设备
JP7105930B2 (ja) 警報方法および警報装置
US11297601B2 (en) Resource allocation method and orchestrator for network slicing in the wireless access network
WO2018006381A1 (zh) 一种网络资源的管理方法、装置及***
US10999740B2 (en) Network slice management method, management unit, and system
US10924966B2 (en) Management method, management unit, and system
WO2019062634A1 (zh) 通信方法及装置
US10270648B2 (en) Configuration information management method, device, network element management system and storage medium
WO2019062836A1 (zh) 网络切片管理方法及其装置
US10819592B2 (en) Slice instance management method and apparatus
US20180367539A1 (en) Method for Accessing Network by Internet of Things Device, Apparatus, and System
US10848366B2 (en) Network function management method, management unit, and system
WO2016155394A1 (zh) 一种虚拟网络功能间链路建立方法及装置
WO2020087948A1 (zh) 网络切片模板生成方法、装置、设备及存储介质
EP3672314B1 (en) Network management method, device and system
WO2016037479A1 (zh) 虚拟化网络功能vnf优化方法、装置及***
JP2018530214A (ja) ネットワークサービスをデプロイするための方法及び装置
WO2019137516A1 (zh) 网络切片部署方法及其装置
CN111258627A (zh) 一种接口文档生成方法和装置
WO2019056954A1 (zh) 管理网络切片的方法和装置
WO2016115896A1 (zh) 虚拟网络功能vnf的管理方法及装置
CN114489954A (zh) 基于虚拟化平台的租户创建方法、租户访问方法及设备
WO2018127068A1 (zh) 网络管理方法和装置
CN114726789A (zh) 流量管理、配置流量管理策略的方法、装置、设备及介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18861139

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18861139

Country of ref document: EP

Kind code of ref document: A1