WO2019062634A1 - Procédé et appareil de communication - Google Patents

Procédé et appareil de communication 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)
Chinese (zh)
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/fr

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

La présente invention concerne un procédé et un appareil de communication. Le procédé comprend les étapes suivantes : un premier dispositif de réseau envoie un premier message de demande à un second dispositif de réseau, le premier message de demande étant utilisé pour demander qu'une instanciation soit exécutée sur une tranche de réseau ou un sous-réseau de tranche de réseau, et le premier message de demande contenant un identifiant d'une instance de tranche de réseau et un identifiant d'une spécification de tranche de réseau, ou le premier message de demande contenant un identifiant d'un sous-réseau de tranche de réseau et un identifiant d'une spécification de sous-réseau de tranche de réseau ; le premier dispositif de réseau reçoit un premier message de réponse, du second dispositif de réseau, le premier message de réponse étant utilisé pour indiquer le résultat de l'instanciation sur la tranche de réseau, ou le premier message de réponse étant utilisé pour indiquer le résultat de l'instanciation sur le sous-réseau de tranche de réseau. L'invention concerne également un appareil correspondant. Comme le premier dispositif de réseau transporte un identifiant d'une instance de tranche et un identifiant de spécification de tranche, dans un message de demande, et que le second dispositif de réseau peut acquérir un modèle de tranche préenregistré d'après l'identifiant de l'instance de tranche, et instancier une tranche en combinaison avec l'identifiant de spécification de tranche, le surdébit de signalisation durant l'instanciation peut être significativement réduit.
PCT/CN2018/106653 2017-09-30 2018-09-20 Procédé et appareil de communication WO2019062634A1 (fr)

Applications Claiming Priority (2)

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

Publications (1)

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

Family

ID=65900799

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/106653 WO2019062634A1 (fr) 2017-09-30 2018-09-20 Procédé et appareil de communication

Country Status (2)

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

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020253344A1 (fr) * 2019-06-17 2020-12-24 华为技术有限公司 Procédé et appareil de contrôle d'autorisation et support de stockage
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 中移(苏州)软件技术有限公司 网络切片的处理方法、装置和存储介质
CN114640588A (zh) * 2020-11-30 2022-06-17 中国移动通信有限公司研究院 一种网络切片业务的处理方法及相关设备

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 (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020253344A1 (fr) * 2019-06-17 2020-12-24 华为技术有限公司 Procédé et appareil de contrôle d'autorisation et support de stockage
CN114025392A (zh) * 2020-07-15 2022-02-08 中移物联网有限公司 网络切片创建方法及相关设备
CN114827980A (zh) * 2021-01-21 2022-07-29 中国移动通信有限公司研究院 Nssi更新方法、装置及nssmf实体

Also Published As

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

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
WO2019062634A1 (fr) Procédé et appareil de communication
WO2018006381A1 (fr) Procédé, appareil et système de gestion de ressource de réseau
US10270648B2 (en) Configuration information management method, device, network element management system and storage medium
US10999740B2 (en) Network slice management method, management unit, and system
WO2019062836A1 (fr) Procédé de gestion de tranches de réseau, et dispositif associé
US10819592B2 (en) Slice instance management method and apparatus
US20180367539A1 (en) Method for Accessing Network by Internet of Things Device, Apparatus, and System
WO2016155394A1 (fr) Procédé et dispositif pour établir une liaison entre des fonctions réseau virtualisées
US10848366B2 (en) Network function management method, management unit, and system
US20190281503A1 (en) Management Method, Management Unit, and System
WO2020087948A1 (fr) Procédé, appareil et dispositif de production de modèle de tranche de réseau et support d'informations
WO2016037479A1 (fr) Procédé, dispositif et système pour optimiser une fonction de réseau virtualisé (vnf)
JP2018530214A (ja) ネットワークサービスをデプロイするための方法及び装置
US11088924B2 (en) Network management method, device, and system
WO2019137516A1 (fr) Procédé et appareil de déploiement de tranche de réseau
WO2019056954A1 (fr) Procédé et dispositif de gestion de tranche de réseau
CN111258627A (zh) 一种接口文档生成方法和装置
WO2016115896A1 (fr) Procédé et dispositif de gestion de fonction de réseau virtuel (vnf)
CN111245634A (zh) 一种虚拟化管理方法及装置
WO2017133020A1 (fr) Procédé et dispositif de transmission de principes dans un système nfv
WO2018127068A1 (fr) Procédé et appareil de gestion de réseau

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