EP4142242A1 - Verfahren, vorrichtung und system zum einsatz von netzwerkslices - Google Patents

Verfahren, vorrichtung und system zum einsatz von netzwerkslices Download PDF

Info

Publication number
EP4142242A1
EP4142242A1 EP22185631.3A EP22185631A EP4142242A1 EP 4142242 A1 EP4142242 A1 EP 4142242A1 EP 22185631 A EP22185631 A EP 22185631A EP 4142242 A1 EP4142242 A1 EP 4142242A1
Authority
EP
European Patent Office
Prior art keywords
network slice
traffic information
service
network
service traffic
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
EP22185631.3A
Other languages
English (en)
French (fr)
Inventor
Ruiyue XU
Kai Zhang
Yan Li
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of EP4142242A1 publication Critical patent/EP4142242A1/de
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • 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
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems

Definitions

  • Embodiments of the present invention relate to the field of communications technologies, and in particular, to a method, a device, and a system for deploying a network slice.
  • the 5th-generation (5th-generation, 5G) mobile communications system (may be referred to as a next-generation mobile communications system) adopts the most advanced mobile communications technology, and can provide a bandwidth with a great capacity and provide safer communication for a mobile subscriber.
  • the 5G system adopts a network slice technology to cut one physical network into a plurality of virtual end-to-end networks.
  • Each virtual network may be referred to as a network slice (network slice, NS).
  • Each network slice is logically independent.
  • Each network slice is formed by instantiating an independent network function or a combination of functions.
  • Each network slice is towards different service requirements and services has different function features.
  • a separation of the network slices enables different tenants to avoid affecting each other based on different application scenarios, flexible and dynamic definitions of requirement information, and customized network capability that are of the tenants.
  • an O&M engineer plan based on requirement information in the contract for example, may analyze and plan with O&M engineer of an equipment vendor
  • deploy the network slice based on the network deployment information. Because the deployment manner needs manual analysis and has low efficiency, a requirement of rapidly deploying tenant services cannot be satisfied.
  • Embodiments of the present invention provide a method, a device, and a system for deploying a network slice, to resolve an existing problem of low efficiency in manually deploying the network slice.
  • an embodiment of the present invention provides a method for deploying a network slice.
  • the method may include: receiving, by a first network management (network management, NM) unit, a network slice management request message that carries service traffic information of the network slice; and deploying, by the first network management unit based on the service traffic information of the network slice, the network slice or selecting an available network slice in an existing network.
  • NM network management
  • the service traffic information of the network slice may be obtained based on traffic information of a service requested by a tenant, and the service traffic information of the network slice is used by the first NM to manage the network slice (for example, deploying a new network slice or selecting the available network slice in the existing network).
  • the NM receives the service traffic information of the network slice, and deploys, based on the service traffic information of the network slice, the network slice or selects the available network slice in the existing network.
  • a device performs auto-management on the network slice in real time based on the service traffic information, which prevents a process of manually off-line network planning, improves efficiency in deploying the network slice, and reduces on-boarding time of a service.
  • the service traffic information of the network slice may include at least one of the following information: a quantity of terminal devices, geographic distribution of the terminal devices, a service transmission status of the terminal devices, an activation ratio of the terminal devices, a usage time of a service, a coverage of the service, a moving status of the terminal devices, and a roaming status of the terminal devices.
  • the quantity of terminal devices may mean: a quantity of devices that can obtain or use a service of the tenant.
  • the geographic distribution of the terminal devices may mean: an area deployment status of the devices that can obtain or use a service of the tenant.
  • the service transmission status of the terminal devices may mean: a service usage status of the terminal devices, such as a time period of transmitting and receiving services by the terminal devices, a packet size of the services transmitted and received by the terminal devices, power of the services transmitted and received by the terminal devices, and a bandwidth size of the services transmitted and received by the terminal devices.
  • a service usage status of the terminal devices such as a time period of transmitting and receiving services by the terminal devices, a packet size of the services transmitted and received by the terminal devices, power of the services transmitted and received by the terminal devices, and a bandwidth size of the services transmitted and received by the terminal devices.
  • the activation ratio of the terminal devices may mean: a ratio of a quantity of terminal devices in an activated state to a quantity of all terminal devices, or may mean a ratio of a quantity of terminal devices in an activated state to a quantity of all terminal devices at a moment.
  • the usage time of the service may mean: time in which a tenant uses the terminal devices to use the service. For example, a reading meter service is performed on the last day of every month.
  • the coverage of the service may be used to indicate a coverage status of the service, and may mean a service coverage level or a coverage scenario.
  • the service coverage scenario includes, for example, an in-building coverage, an outdoor coverage, a suburban area coverage, a metro coverage, a tunnel coverage, and the like.
  • the service coverage level may be a heavy coverage, a common coverage, and a weak coverage.
  • the moving status of the terminal devices may include at least one of the following cases: whether the terminal devices move, a quantity of the terminal devices that are in a moving status, and a moving level of the terminal devices.
  • the moving level of the terminal devices may include one or more of the following levels: a fast speed, a middle speed, a low speed, or non-moving.
  • the roaming status of the terminal devices may include at least one of the following cases: whether the terminal devices roam, a quantity of the terminal devices that may roam at different moments, and the like.
  • the deploying, by the first NM based on the received service traffic information of the network slice, the network slice or selecting an available network slice in an existing network may include:
  • the deploying the network slice or selecting the available network slice in the existing network may be implemented based on the foregoing manner, which improves flexibility of network slice deployment.
  • the method may further include: sending, by the first NM, the service traffic information of the network slice to a third NM
  • the third NM is an NM that is not located in a same domain with the NM
  • the method may further include: determining, by the first NM based on the service traffic information of the network slice, whether the first NM is able to provide the network slice to satisfy a requirement of the service traffic information of the network slice, and if the first NM is unable to do so, not deploying, based on the service traffic information of the network slice, the network slice or selecting the available network slice in the existing network, and sending a response message to a sender of the network slice management request message; or otherwise, deploying, by the NM based on the service traffic information of the network slice, the network slice or selecting the available network slice in the existing network.
  • an embodiment of the present invention provides an NM, including:
  • the NM refers to the behavior function of the first NM in the method for deploying a network slice according to the foregoing aspect or possible implementations of the foregoing aspect. Details are not described herein again. Therefore, the NM provided by this aspect may have the same advantageous effect as that of the foregoing aspect.
  • this embodiment of the present invention provides an NM, the NM can implement functions performed by the first NM in the foregoing method embodiments, and the functions may be implemented by using hardware, or may be implemented by using the hardware to execute corresponding software.
  • the hardware or the software includes one or more modules corresponding to the foregoing functions.
  • a structure of the NM includes a processor and a communications interface, and the processor is configured to support the NM in performing the corresponding functions in the foregoing method.
  • the communications interface is configured to support communication between the NM and another network element.
  • the NM may further include a memory, the memory is configured to couple to the processor, and the memory stores a necessary program instruction and data that are both of the NM
  • an embodiment of the present invention provides a computer storage medium, configured to store a computer software instruction used by the foregoing NM, where the computer software instruction includes a program used for executing the solution in the foregoing aspects.
  • an embodiment of the present invention provides a computer program product, where a computer software instruction used by the foregoing first NM is stored in the program product, and the computer software instruction includes a program used for executing the solution in the foregoing aspects.
  • an embodiment of the present invention provides an apparatus, the apparatus exists as a product form of a chip, and a structure of the apparatus includes a processor and a memory, where the memory is configured to couple to the processor and store a necessary program instruction and data that are both of the apparatus, and the processor is configured to execute the program instruction stored in the memory and enables the apparatus to perform the functions corresponding to the NM in the foregoing method.
  • an embodiment of the present invention provides a method for deploying a network slice.
  • the method may include: receiving, by a DM, service traffic information of a network slice subnet from a network management unit NM, and managing the network slice subnet based on the service traffic information of the network slice subnet.
  • the DM receives the service traffic information of the network slice subnet, and manages the network slice subnet based on the service traffic information of the network slice subnet.
  • a device performs auto-management on the network slice in real time based on the service traffic information, which prevents a process of manually off-line network planning, improves efficiency in deploying the network slice, and reduces on-boarding time of a service.
  • the managing, by a DM, the network slice subnet may include at least one of the following manners:
  • information included in the service traffic information of the network slice subnet is the same as information included in the foregoing service traffic information of the network slice, and details are not described herein again.
  • an embodiment of the present invention provides a DM, including:
  • the DM may have the same advantageous effect as that of the foregoing aspects.
  • this embodiment of the present invention provides a DM, the DM can implement functions performed by the DM in the foregoing method embodiments, and the functions may be implemented by using hardware, or may be implemented by using the hardware to execute corresponding software.
  • the hardware or the software includes one or more modules corresponding to the foregoing functions.
  • a structure of the DM includes a processor and a communications interface, and the processor is configured to support the DM in performing the corresponding functions in the foregoing method.
  • the communications interface is configured to support communication between the DM and another network element.
  • the DM may further include a memory, the memory is configured to couple to the processor, and the memory stores a necessary program instruction and data that are both of the DM.
  • an embodiment of the present invention provides a computer storage medium, configured to store a computer software instruction used by the foregoing DM, where the computer software instruction includes a program used for executing the solution in the foregoing aspects.
  • an embodiment of the present invention provides a computer program product, where a computer software instruction used by the foregoing DM is stored in the program product, and the computer software instruction includes a program used for executing the solution in the foregoing aspects.
  • an embodiment of the present invention provides an apparatus, the apparatus exists as a product form of a chip, and a structure of the apparatus includes a processor and a memory, where the memory is configured to couple to the processor and store a necessary program instruction and data that are both of the apparatus, and the processor is configured to execute the program instruction stored in the memory and enables the apparatus to perform the functions corresponding to the DM in the foregoing method.
  • an embodiment of the present invention provides a method for deploying a network slice.
  • the method may include: receiving, by an SMF, a service management request message that carries traffic information of a service, and determining, based on the traffic information of the service, service traffic information or sub-service traffic information of the network slice.
  • the SMF receives the traffic information of the service, and determines the service traffic information of the network slice based on the traffic information of the service.
  • a device performs auto-management on the network slice in real time based on the service traffic information, which prevents a process of manually off-line network planning, improves efficiency in deploying the network slice, and reduces on-boarding time of a service.
  • the method may further include:
  • the network slice may be deployed by the SMF, or the network slice may be deployed by the NM, which improves flexibility of network slice deployment.
  • the determining, by an SMF based on the traffic information of the service, service traffic information of the network slice may include: decomposing, by the SMF, the traffic information of the service into at least one piece of sub-service traffic information, and determining the decomposed at least one piece of sub-service traffic information as the service traffic information of the network slice.
  • information included in the traffic information of the service and in the service traffic information of the network slice is the same as content included in the foregoing service traffic information of the network slice, and details are not described herein again.
  • an SMF including:
  • the SMF For a specific implementation of the SMF, refer to the behavior function of the SMF in the method for deploying a network slice according to the foregoing aspects or the possible implementations of the foregoing aspects. Details are not described herein again. Therefore, the SMF provided by this aspect may have the same advantageous effect as that of the foregoing aspects.
  • this embodiment of the present invention provides an SMF
  • the SMF can implement functions performed by the SMF in the foregoing method embodiments, and the functions may be implemented by using hardware, or may be implemented by using the hardware to execute corresponding software.
  • the hardware or the software includes one or more modules corresponding to the foregoing functions.
  • a structure of the SMF includes a processor and a communications interface, and the processor is configured to support the SMF in performing the corresponding functions in the foregoing method.
  • the communications interface is configured to support communication between the SMF and another network element.
  • the SMF may further include a memory, the memory is configured to couple to the processor, and the memory stores a necessary program instruction and data that are both of the SMF.
  • an embodiment of the present invention provides a computer storage medium, configured to store a computer software instruction used by the foregoing SMF, where the computer software instruction includes a program used for executing the solution in the foregoing aspects.
  • an embodiment of the present invention provides a computer program product, where a computer software instruction used by the foregoing SMF is stored in the program product, and the computer software instruction includes a program used for executing the solution in the foregoing aspects.
  • an embodiment of the present invention provides an apparatus, the apparatus exists as a product form of a chip, and a structure of the apparatus includes a processor and a memory, where the memory is configured to couple to the processor and store a necessary program instruction and data that are both of the apparatus, and the processor is configured to execute the program instruction stored in the memory and enables the apparatus to perform the functions corresponding to the SMF in the foregoing method.
  • an embodiment of the present invention provides a system for deploying a network slice, including: the NM according to the foregoing aspects or any one of possible implementations of the foregoing aspects, the DM according to the foregoing aspects or any one of possible implementations of the foregoing aspects, and the SMF according to the foregoing aspects or any one of possible implementations of the foregoing aspects.
  • Embodiments of the present invention provide a method for deploying a network slice, and a basic principle of the method is: automatically deploying, by a management unit based on service traffic information of the network slice, the network slice or selecting an available network slice in an existing network, to improve efficiency in network slice deployment, and satisfy a requirement of rapidly deploying a tenant service cannot be satisfied.
  • Network slice may alternatively be referred to as a network slice instance, is a combination that is of network function (network function, NF) units and resources and that ensures a bearer service to meet a service level agreement (service level agreement, SLA) requirement. These NFs and resources may perform, based on different requirements, a hard separation (for example, a physical separation), or a soft separation (for example, a logical separation). Each network slice is logically independent.
  • the network slice may at least include a core network (core network, CN) part, an access network (access network, AN) part, and a transport network (transport network, TN) part; or may include any two parts or one part of a CN part, an AN part, or a TN part.
  • the network slice is a wide conception. It may be considered that a conventional network or one dedicated network is also one network slice. Alternatively, it may be considered that a network slice subnet is also one type of network slices.
  • Network slice subnet may be referred to as a network slice subnet instance, is a combination that is of network functions and resources and that ensures a bearer service to meet the SLA requirement.
  • the network slice subnet may be obtained by dividing the network slice, or the network slice may directly act as the network slice subnet.
  • Tenant is a user (such as an enterprise, a factory, a school, and the like) that uses a network slice or a network slice subnet to complete a service function.
  • the method for deploying a network slice may be implemented by using function units in a network architecture shown in FIG. 1 , and the network architecture may be deployed in a 5G system.
  • the network architecture may include: a service management unit (service management function, SMF), a network management (network management, NM) unit, a domain management (domain management, DM) unit, a transport network domain management (transport network manager, TN-DM) unit, and a network function (network function, NF) unit.
  • SMF service management function
  • NM network management
  • domain management domain management
  • TN-DM transport network domain management
  • NF network function
  • Data or a signaling message may be transmitted between the DMs by using the TN-DM.
  • a plurality of NFs may form the network slice or the network slice subnet.
  • FIG. 1 is merely an exemplary architectural diagram.
  • the network architecture may further include other function nodes, and this is not limited hereto in an embodiment of the present invention.
  • the SMF shown in FIG. 1 is mainly used to receive a service requirement of a tenant, convert the service requirement into a requirement of the network slice, and perform service management.
  • the SMF may be deployed inside an operation support system (operation support system, OSS), or may be deployed outside the OSS.
  • the SMF may be a management unit or an operation unit that are of the tenant.
  • the SMF may be deployed independently, or may be integrated in a management unit (for example, a business support system (business support system, BSS), the service management unit, a service orchestration unit, or a service management and orchestration unit).
  • a management unit for example, a business support system (business support system, BSS), the service management unit, a service orchestration unit, or a service management and orchestration unit.
  • BSS business support system
  • the SMF is not limited to names shown in FIG. 1 .
  • the SMF may further be named: a customer service management function (customer service management function, CSMF) unit or a communication service management function (
  • the NM in FIG. 1 includes one or both of an end-to-end network management function or an end-to-end network orchestration function, and may have some or all of the following functions: management of an end-to-end network (for example, life cycle management of a network, management of a network template, fault management of a network, performance management of a network, and configuration management of a network), mapping between an end-to-end network and a sub-network and mapping between an end-to-end network and a network function, coordination of sub-SLAs or network resources that both are provided by different domains (such as an access network domain, a core network domain, and a transport domain), decomposing network requirement information into subnet requirement information, and unified orchestration of network functions and sub-networks that both are provided by all sub-domains, so that subnets or network functions that are both provided by different sub-domains may satisfy a requirement of a target service or of a network (for example, a requirement of an SLA, a requirement of a key performance indicator (
  • the NM may be deployed inside the OSS, or may be deployed outside the OSS.
  • the NM may be independently deployed, or may be integrated in a management unit (for example, a network orchestration unit, a network management and orchestration unit, the service management unit, the service orchestration unit, the service management and orchestration unit, or a network function virtualization orchestrator (network function virtualization orchestrator, NFVO)).
  • a management unit for example, a network orchestration unit, a network management and orchestration unit, the service management unit, the service orchestration unit, the service management and orchestration unit, or a network function virtualization orchestrator (network function virtualization orchestrator, NFVO)
  • NFVO network function virtualization orchestrator
  • the DM in FIG. 1 includes one or both of a subnet management function or an orchestration function, and may include some or all of the following functions: management of a domain (including life cycle management (creating, updating, and deleting) of a subnet, fault management of a subnet, performance management of a subnet, configuration management of a subnet, or the like), management of a service (including life cycle management of a service, fault management of a service, performance management of a service, configuration management of a service, or the like), and coordination of network resources (such as an NF, a network element (network element, NE)), and all the functions are used for unified orchestration.
  • the DM may be deployed inside the OSS, or may be deployed outside the OSS.
  • the DM may be independently deployed, or may be integrated in a management unit (for example, the network management unit, the network orchestration unit, the network management and orchestration unit, a network element management unit, a network function management unit, the service management unit, the service orchestration unit, a domain management unit, the service management and orchestration unit, or the NFVO).
  • a management unit for example, the network management unit, the network orchestration unit, the network management and orchestration unit, a network element management unit, a network function management unit, the service management unit, the service orchestration unit, a domain management unit, the service management and orchestration unit, or the NFVO.
  • a management unit for example, the network management unit, the network orchestration unit, the network management and orchestration unit, a network element management unit, a network function management unit, the service management unit, the service orchestration unit, a domain management unit, the service management and orchestration unit, or the NFVO.
  • the DM is not limited to names shown in FIG. 1 .
  • the DM may
  • a subnet managed by the foregoing DM may include one or more of the following parts: an AN part, a CN part, and a TN part.
  • the subnet management unit may be considered as an AN DM; when the subnet managed by the DM merely includes the CN part, the subnet management unit may be considered as a CN DM; or when the subnet managed by the DM includes the AN and CN part, the subnet management unit may be considered as a Mix DM.
  • the TN-DM in FIG. 1 includes one or both of a transport network management function or a transport network orchestration function, and may include some or all of the following functions: management of a transport network part (including life cycle management (creating, updating, and deleting) of a transport network part, fault management of a transport network part, performance management of a transport network part, configuration management of a transport network part, or the like).
  • management of a transport network part including life cycle management (creating, updating, and deleting) of a transport network part, fault management of a transport network part, performance management of a transport network part, configuration management of a transport network part, or the like.
  • the TN-DM may be deployed inside the OSS, or may be deployed outside the OSS.
  • the TN-DM may be independently deployed, or may be integrated in a management unit (for example, the network management unit, the network orchestration unit, the network management and orchestration unit, the domain management unit, the network element management unit, the service management unit, the service orchestration unit, the domain management unit, the service management and orchestration unit, or the NFVO).
  • a management unit for example, the network management unit, the network orchestration unit, the network management and orchestration unit, the domain management unit, the network element management unit, the service management unit, the service orchestration unit, the domain management unit, the service management and orchestration unit, or the NFVO.
  • the TN-DM is not limited to names shown in FIG. 1 .
  • the TN-DM may further be named: a (transport network) subnet management unit, a network slice transport network manager unit, or the like.
  • FIG. 2 is a schematic composition diagram of a management unit according to an embodiment of the present invention.
  • the management unit may include at least one processor 21, a memory 22, a communications interface 23, and a communications bus 24.
  • the device structure shown in FIG. 2 constitutes no limitation on the management unit, and may include more or fewer components than those shown in the figure, or some components may be combined, or different components may be deployed. This is not limited hereto in an embodiment of the present invention. The following specifically describes the components of the management unit with reference to FIG. 2 .
  • the processor 21 is a control center of the management unit, may be one processor, or may be a collective name of a plurality of processing elements.
  • the processor 21 is a central processing unit (central processing unit, CPU), or may be an application specific integrated circuit (application specific integrated circuit, ASIC), or one or more integrated circuits configured to implement this embodiment of the present invention, for example, one or more microprocessors (digital signal processor, DSP), or one or more field programmable gate arrays (field programmable gate array, FPGA).
  • the processor 21 may perform various functions of the management unit by running or executing a software program stored in the memory 22 and invoking data stored in the memory 22.
  • the processor 21 may include one or more CPUs, for example, a CPU 0 and a CPU 1 shown in FIG. 2 .
  • the management unit may include a plurality of processors, for example, the processor 21 and a processor 25 shown in FIG. 2 .
  • Each of the processors may be a single-core processor (single-CPU) or may be a multi-core processor (multi-CPU).
  • the processor herein may refer to one or more devices, circuits, and/or processing cores configured to process data (such as a computer program instruction).
  • the memory 22 may be a read-only memory (read-only memory, ROM) or another type of static storage device that can store static information and a static instruction; or a random access memory (random access memory, RAM) or another type of dynamic storage device that can store information and an instruction; or may be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc read-only memory (compact disc read-only memory, CD-ROM) or another compact disc storage medium, optical disc storage medium (including a compact disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, or the like) and magnetic disk storage medium or another magnetic storage device, or any other medium that can be configured to carry or store expected program code in a form of an instruction or a data structure and that is accessible to a computer, but is not limited thereto.
  • ROM read-only memory
  • RAM random access memory
  • EEPROM electrically erasable programmable read-only memory
  • the memory 22 may exist independently, and be connected to the processor 21 through the communications bus 24. Alternatively, the memory 22 may be integrated with the processor 21.
  • the memory 22 is configured to store a software program for executing the solution of this embodiment of the present invention, and the executing is controlled by the processor 21.
  • the communications interface 23 is configured to communicate with another device or a communications network such as an Ethernet, a radio access network (radio access network, RAN), or wireless local area networks (wireless local area networks, WLAN), or the like.
  • the communications interface 23 may include a receiving unit for implementing a receiving function and a sending unit for implementing a sending function.
  • the communications bus 24 may be an industry standard architecture (industry standard architecture, ISA) bus, a peripheral component interconnect (peripheral component, PCI) bus, an extended industry standard architecture (extended industry standard architecture, EISA) bus, or the like.
  • the bus may include an address bus, a data bus, a control bus, and the like. For ease of representation, only a bold line is used for representation in FIG. 2 , but it does not represent that there is only one bus or one type of buses.
  • the management unit shown in FIG. 2 is the NM in FIG. 1
  • the management unit may perform functions performed by the NM in a method for deploying a network slice according to this embodiment of the present invention.
  • the communications bus 23 in the management unit may be configured to receive a network slice management request message that carries service traffic information of the network slice
  • the processor 21 in the management unit may be configured to deploy, based on the received service traffic information of the network slice, the network slice or select the available network slice in the existing network.
  • the management unit shown in FIG. 2 is the DM in FIG. 1
  • the management unit may perform functions performed by the DM in a method for deploying a network slice according to this embodiment of the present invention.
  • the communications bus 23 in the management unit may be configured to receive, from the NM, service traffic information of a network slice subnet
  • the processor 21 in the management unit may be configured to manage the network slice subnet based on the received service traffic information of the network slice subnet.
  • the management unit shown in FIG. 2 is the SMF in FIG. 1
  • the management unit may perform functions performed by the SMF in a method for deploying a network slice according to this embodiment of the present invention.
  • the communications bus 23 in the management unit may be configured to receive a service management request message that carries traffic information of a service
  • the processor 21 in the management unit may be configured to determine service traffic information of the network slice based on the received traffic information of the service
  • the communications interface 23 in the management unit may further be configured to send the service traffic information of the network slice to the NM
  • FIG. 3 is a flowchart of a method for deploying a network slice according to an embodiment of the present invention. As shown in FIG. 3 , the method may include the following steps: Step 301: An NM receives a network slice management request message.
  • the foregoing NM may be the NM in FIG. 1
  • the foregoing network slice management request message may be used to request the NM to manage the network slice
  • the network slice management request message may carry service traffic information of the network slice.
  • the foregoing service traffic information of the network slice may be obtained based on traffic information of a service requested by a tenant, the service traffic information of the network slice is used by the NM to manage the network slice (for example, to deploy a new network slice and/or select the available network slice in the existing network), the service traffic information of the network slice may include at least one of the following information: a quantity of terminal devices, geographic distribution of the terminal devices, a service transmission status of the terminal devices, an activation ratio of the terminal devices, a usage time of the service, a coverage of the service, a moving status of the terminal devices, and a roaming status of the terminal devices.
  • a and/or B may include at least one of the following cases: A, B, and A and B.
  • deploying a new network slice and/or selecting the available network slice in the existing network may include three cases: deploying a new network slice, selecting the available network slice in the existing network, and deploying the new network slice and selecting the available network slice in the existing network.
  • the existing network may mean: a network, including a network slice, a network slice subnet, and a network function unit, that is already deployed within a management range of the NM
  • the foregoing tenant may be: a user (such as a factory, a school, and the like) that uses a deployed network slice or a deployed network slice subnet in this embodiment of the present invention to complete a service function.
  • a user such as a factory, a school, and the like
  • the foregoing terminal devices may mean devices that can obtain or use a service of the tenant, and the terminal devices are corresponding to the tenant.
  • a terminal device may be a device such as a meter that records a quantity of electricity used by the tenant, and the like.
  • the service requested by the tenant may be: a service function performed by the terminal devices corresponding to the tenant.
  • a terminal device is the meter that records the quantity of electricity used by the tenant, and the service requested by the tenant may be a reading meter service.
  • the quantity of terminal devices may mean: a quantity of devices that can obtain or use a service of the tenant.
  • the geographic distribution of the terminal devices may mean: an area deployment status of devices that can obtain or use a service of the tenant.
  • the quantity of terminal devices and the geographic distribution status of the terminal devices may be combined to act as one type of information of the service traffic information of the network slice. For example, a quantity of terminal devices in area 1 is 100, and a quantity of terminal devices in area 2 is 200.
  • the service transmission status of the terminal devices may mean: a service usage status of the terminal devices, such as a time period of transmitting and receiving services by the terminal devices, a packet size of the services transmitted and received by the terminal devices, power of the services transmitted and received by the terminal devices, and a bandwidth size of the services transmitted and received by the terminal devices.
  • a terminal device is the meter that records the quantity of electricity used by the tenant
  • the service transmission status of the terminal device is that: the meter transmits a packet once every day, and a size of the transmitted packet is 20 M every time.
  • the activation ratio of the terminal devices may mean: a ratio of a quantity of terminal devices in an activated state to a quantity of all terminal devices, or may mean a ratio of a quantity of terminal devices in an activated state to a quantity of all terminal devices at a moment.
  • the usage time of the service may mean: time in which the terminal devices use the service. For example, a reading meter service is performed on the last day of every month.
  • the coverage of the service may be used to indicate a coverage status of the service, and may mean a service coverage level or a coverage scenario.
  • the service coverage scenario includes, for example, an in-building coverage, an outdoor coverage, a suburban area coverage, a metro coverage, a tunnel coverage, and the like.
  • the service coverage level may be a heavy coverage, a common coverage, and a weak coverage.
  • the moving status of the terminal devices may include at least one of the following cases: whether the terminal devices move, a quantity of the terminal devices that are in a moving status, and a moving level of the terminal devices.
  • the moving level of the terminal devices may include one or more of the following levels: a fast speed, a middle speed, a low speed, or non-moving.
  • the roaming status of the terminal devices may include at least one of the following cases: whether the terminal devices roam, a quantity of the terminal devices that may roam at different moments, and the like.
  • the service traffic information that is received by the NM and that is of the network slice is that: a quantity of terminal devices in Pudong of Shanghai is 2 million, a quantity of terminal devices in Puxi of Shanghai is 3 million, the terminal devices in each location area are evenly distributed, the service transmission status of the terminal device is that: transmission is performed twice every month and is small packet transmission, the activation ratio of the terminal devices is 80%, usage time of the service is the 15 th day and the 30 th day of every month, the moving status of the terminal devices is: non-moving, and the roaming status of the terminal devices is: non-roaming.
  • the foregoing service traffic information of the network slice is not limited to including at least one piece of the foregoing information, and may further include multidimensional data formed by at least one piece of the foregoing information.
  • the service traffic information of the network slice may include at least one of the following multidimensional data: multidimensional data formed by a location area of terminal devices and an activation ratio of the terminal devices in the location area, multidimensional data formed by the location area of the terminal devices and a data transmission status of the terminal devices or a moving status of the terminal devices that are in the location area.
  • the foregoing network slice management request message is not limited to including the service traffic information of the network slice, and may further include other information, such as deployment location information of the network slice, an affinity of the network slice, and a non-affinity of the network slice.
  • the deployment location information of the network slice may be used to indicate a deployment location of the network slice.
  • the affinity of the network slice When the network slice and another network slice can be deployed in a same location area, the network slice and the another network slice have the affinity.
  • the non-affinity of the network slice When the network slice and another network slice cannot be deployed in a same location area, the network slice and the another network slice have the non-affinity.
  • Step 302 The NM deploys, based on the received service traffic information of the network slice, the network slice or selects the available network slice in the existing network.
  • the foregoing deploying the network slice may mean: deploying or selecting existing network resources (including at least one of the following information: a network function, a network slice subnet, and a transmission resource) in a network that are combined to act as a network slice to satisfy the service traffic information of the network slice.
  • the foregoing selecting the available network slice in the existing network may mean: selecting a network slice that is already deployed within a management range of the NM to satisfy the service traffic information of the network slice.
  • the network slice satisfies the service traffic information of the network slice may mean: the network slice may provide a service with the foregoing service traffic information.
  • the word "deploy” may further be replaced by create or instantiate, that is, deploying the network slice may be alternatively referred to as creating the network slice or instantiating the network slice. This is not limited hereto.
  • the NM when there is a network slice in the existing network and the network slice satisfies the service traffic information of the network, or when there is a network slice in the existing network and the network slice may be modified (such as, capacity expansion) to satisfy the service traffic information of the network slice, or when the NM receives a message used to indicate that a network slice in the existing network needs to be reused, the NM selects the available network slice in the existing network, otherwise, the NM deploys the network slice.
  • the NM deploys, based on the received service traffic information of the network slice, the network slice or selects the available network slice in the existing network may include but be not limited to the following implementations.
  • Manner 1 when the network slice is formed by one network slice subnet, the network slice and the network slice subnet may be considered as a same network instance, and the service traffic information of the network slice is equivalent to service traffic information of the network slice subnet.
  • the NM deploys, based on the service traffic information of the network slice subnet, the network slice subnet or selects an available network slice subnet in the existing network.
  • Manner 2 when the network slice is formed by at least two network slice subnets, the NM decomposes the service traffic information of the network slice into service traffic information of the at least two network slice subnets respectively corresponding to the at least two network slice subnets, and deploys, based on the service traffic information of the at least two network slice subnets, the at least two network slice subnets, or selects available network slice subnets in the existing network.
  • Manner 3 when the network slice is formed by at least two network slice subnets, the NM decomposes the service traffic information of the network slice into service traffic information of the at least two network slice subnets respectively corresponding to the at least two network slice subnets, and sends the service traffic information of the network slice subnets to a DM, so that the DM deploys, based on the service traffic information of the network slice subnets, the network slice subnets, or selects available network slice subnets in the existing network.
  • Manner 4 when the network slice is formed by one network slice subnet, the network slice subnet is equivalent to the network slice, that is, the network slice and the network slice subnet may be considered as a same network instance, and the service traffic information of the network slice is equivalent to service traffic information of the network slice subnet.
  • the NM sends the service traffic information of the network slice to a DM, so that the DM deploys, based on the service traffic information of the network slice, the network slice, or selects the available network slice in the existing network.
  • the NM may determine that the network slice is formed by one or at least two network slice subnets in the following manner:
  • the NM may adopt an existing algorithm to decompose the service traffic information of the network slice into service traffic information of the at least two network slice subnets, and details are not described herein again.
  • the NM deploying the network slice subnet may include: deploying or selecting existing network resources (including at least one of the following information: a network function, a network slice subnet, and a transmission resource) in a network that are combined to act as a network slice subnet to satisfy the service traffic information of the network slice subnet.
  • the selecting the available network slice subnet in the existing network may mean: selecting a network slice subnet that is already deployed within a management range of the NM to satisfy the service traffic information of the network slice subnet.
  • the NM or DM deploying, based on the service traffic information of the network slice subnet, the network slice subnet or selecting the available network slice subnet in the existing network may specifically include: when there is a network slice subnet in the existing network and the network slice subnet satisfies the service traffic information of the network, or when there is a network slice subnet in the existing network and the network slice subnet may be modified (such as, capacity expansion) to satisfy the service traffic information of the network slice subnet, or when the NM receives a message used to indicate that a network slice subnet in the existing network needs to be reused, the NM selects the available network slice subnet in the existing network, or otherwise, the NM deploys the network slice subnet. That the network slice subnet satisfies the service traffic information of the network slice subnet may mean that the network slice subnet may provide a service with the foregoing service traffic information of the network slice subnet.
  • service traffic information of a network slice 2 is that: a quantity of terminal devices in Puxi of Shanghai is 3 million, the terminal devices in each location area are evenly distributed, the service transmission status of the terminal device is that: transmission is performed twice every month and is small packet transmission, the activation ratio of the terminal devices is 80%, usage time of the service is the 15 th day and the 30 th day of every month, the moving status of the terminal devices is: non-moving, and the roaming status of the terminal devices is: non-roaming.
  • service traffic information of the network slice 1 is decomposed into service traffic information of a network slice subnet 1 and service traffic information of a network slice subnet 2.
  • the service traffic information of the network slice subnet 1 is that: a quantity of terminal devices in Huangpu district, Pudong of Shanghai is 2 million, the terminal devices in each location area are evenly distributed, the service transmission status of the terminal device is that: transmission is performed twice every month and is small packet transmission, the activation ratio of the terminal devices is 80%, usage time of the service is the 15 th day and the 30 th day of every month, the moving status of the terminal devices is: non-moving, and the roaming status of the terminal devices is: non-roaming.
  • the service traffic information of the network slice subnet 2 is that: a quantity of terminal devices in Jing'an district, Pudong of Shanghai is 1 million, the terminal devices in each location area are evenly distributed, the service transmission status of the terminal device is that: transmission is performed twice every month and is small packet transmission, the activation ratio of the terminal devices is 80%, usage time of the service is the 15 th day and the 30 th day of every month, the moving status of the terminal devices is: non-moving, and the roaming status of the terminal devices is: non-roaming.
  • the NM receives the service traffic information of the network slice, and deploys, based on the service traffic information of the network slice, the network slice or selects the available network slice in the existing network.
  • a device performs auto-management on the network slice in real time based on the service traffic information, which prevents a process of manually off-line network planning, improves efficiency in deploying the network slice, and reduces on-boarding time of a service.
  • the NM may receive the service traffic information of the network slice from a service management unit SMF; or receive the service traffic information of the network slice from a tenant; or receive the service traffic information of the network slice from other NMs.
  • the method further includes: sending, by the NM, the service traffic information of the network slice to other NMs.
  • the other NMs are a network management unit of another operator other than the operator to which the NM belongs, or a network management unit of another region of the operator to which the NM belongs.
  • the solution shown in FIG. 3 may further include: determining, by the NM based on the service traffic information of the network slice, whether the NM is able to provide the network slice to satisfy a requirement of the service traffic information of the network slice, and if the NM is unable to do so, not performing step 302 and returning a response message to a sender of the network slice management request message, or otherwise, performing step 302.
  • FIG. 4 shows another method for deploying a network slice according to an embodiment of the present invention.
  • the method may include the following steps: Step 401: An SMF receives traffic information of a service.
  • the foregoing traffic information of the service is used to describe service requirement information of a tenant, and content included in the traffic information of the service may be the same as content included in the service traffic information of the network slice in the solution shown in FIG. 3 , and details are not described herein again.
  • the SMF receives a service management request message from the tenant, and the service management request message includes the traffic information of the service; or the SMF receives a sub-service management request message from another SMF, where the sub-service management request message includes the traffic information of the service, and the another SMF is a service management unit that is different from the SMF and that is in a network.
  • the traffic information of the service included in the sub-service management request message may be the traffic information that is received by the another SMF and that is of the service, or may be sub-service traffic information obtained after another SMF node decomposes the received traffic information of the service, and this is not limited hereto.
  • content included in the sub-service traffic information refer to related descriptions in the traffic information of the service, and details are not described herein again.
  • Step 402 The SMF determines service traffic information of a network slice based on the received service management request message.
  • the service traffic information of the network slice is the same as descriptions in FIG. 3 , and details are not described herein again.
  • the traffic information of the service carried in the service management request message is the service traffic information of the network slice, or when the service requested by the tenant is borne on at least two network slices, the traffic information of the service carried in the service management request message may be decomposed into at least two pieces of sub-service traffic information, and the decomposed at least two pieces of sub-service traffic information may be determined as service traffic information of the at least two network slices.
  • the SMF may determine that the service requested by the tenant is borne on one or at least two network slices in the following manner:
  • the service requested by the tenant is a reading meter service in Shanghai area
  • traffic information of the service is that: a quantity of terminal devices is 5 million, the terminal devices are evenly distributed, the service transmission status of the terminal device is that: transmission is performed twice every month and is small packet transmission, the activation ratio of the terminal devices is 80%, usage time of the service is the 15 th day and the 30 th day of every month, the moving status of the terminal devices is: non-moving, and the roaming status of the terminal devices is: non-roaming.
  • the traffic information of the service is decomposed into service traffic information of a network slice 1 and service traffic information of a network slice 2.
  • the service traffic information of the network slice 1 is that: a quantity of terminal devices in Pudong of Shanghai is 2 million, the terminal devices in each location area are evenly distributed, the service transmission status of the terminal device is that: transmission is performed twice every month and is small packet transmission, the activation ratio of the terminal devices is 80%, usage time of the service is the 15 th day and the 30 th day of every month, the moving status of the terminal devices is: non-moving, and the roaming status of the terminal devices is: non-roaming.
  • the service traffic information of the network slice 2 is that: a quantity of terminal devices in Puxi of Shanghai is 3 million, the terminal devices in each location area are evenly distributed, the service transmission status of the terminal device is that: transmission is performed twice every month and is small packet transmission, the activation ratio of the terminal devices is 80%, usage time of the service is the 15 th day and the 30 th day of every month, the moving status of the terminal devices is: non-moving, and the roaming status of the terminal devices is: non-roaming.
  • Step 403 The SMF sends the service traffic information of the network slice to an NM
  • the SMF may send the service traffic information of the network slice by using a next generation (next generation, NG) interface between the SMF and the NM.
  • NG next generation
  • the SMF may respectively send the decomposed service traffic information of at least two network slices to at least two NMs, where the at least two NMs may be in one-to-one correspondence to the service traffic information of the at least two network slices.
  • Step 404 The NM receives the service traffic information of the network slice from the SMF, and determines service traffic information of a network slice subnet based on the service traffic information of the network slice.
  • the NM receives the service traffic information of the network slice, and determines service traffic information of the network slice subnet based on the service traffic information of the network slice, refer to the process in the solution in FIG. 3 , and details are not described herein again.
  • Step 405 The NM sends the service traffic information of the network slice subnet to a DM.
  • the NM may send the service traffic information of the network slice subnet by using an NG between the NM and the DM.
  • Step 406 The DM receives the service traffic information of the network slice subnet from the NM, and manages the network slice subnet based on the service traffic information of the network slice subnet.
  • the DM may manage the network slice subnet in at least one of the following manners:
  • the DM may send a management request message to the NF or the management unit of the NF, and the management request message may include the service traffic information of the NF.
  • Content included in the service traffic information of the NF is the same as content included in the service traffic information of the network slice in the solution shown in FIG. 3 , and details are not described herein again.
  • step 404 the NM determines that the service traffic information of the network slice is equivalent to the service traffic information of the network slice subnet
  • step 405 may be replaced by:
  • the NM sends the service traffic information of the network slice to a DM
  • step 406 may be replaced by:
  • the DM receives the service traffic information of the network slice from the NM, and manages the network slice based on the service traffic information of the network slice.
  • the method used by the DM to manage the network slice refer to the manner in which the DM manages the network slice subnet, and the manner includes at least one of the following manners:
  • the SMF may further deploy, based on the service traffic information of the network slice, the network slice or select the available network slice in the existing network, and the SMF does not need to send the service traffic information of the network slice to another function unit. That is, the foregoing steps 403 to 406 may be replaced by: The SMF deploys, based on the service traffic information of the network slice, the network slice or selects the available network slice in the existing network.
  • the SMF deploys, based on the service traffic information of the network slice, the network slice or selects the available network slice in the existing network
  • the NM deploys, based on the service traffic information of the network slice, the network slice or selects the available network slice in the existing network. Details are not described herein again.
  • the NM deploys, based on the service traffic information of the network slice, the network slice subnet or selects the available network slice in the existing network. That is, the foregoing steps 404 to 406 may be replaced by: The NM deploys, based on the service traffic information of the network slice, the network slice or selects the available network slice in the existing network.
  • a manner in which the NM deploys, based on the service traffic information of the network slice, the network slice or selects the available network slice in the existing network is the same as descriptions in FIG. 3 , and details are not described herein again.
  • the foregoing steps 404 to 406 may be replaced by:
  • the NM receives the service traffic information of the network slice from the SMF, the NM sends the service traffic information of the network slice to the DM, and the DM deploys, based on the received service traffic information of the network slice, the network slice or selects the available network slice in the existing network.
  • the DM deploys, based on the service traffic information of the network slice, the network slice or selects the available network slice in the existing network.
  • the SMF, the NM, and the DM are mutually configured to deploy the network slice subnet or select the available network slice subnet in the existing network.
  • a device performs auto-management on the network slice in real time based on the service traffic information, which prevents a process of manually off-line network planning, improves efficiency in deploying the network slice, and reduces on-boarding time of a service.
  • FIG. 5 shows still another method for deploying a network slice according to an embodiment of the present invention.
  • the method may include the following steps.
  • Step 501 A tenant sends a network slice management request message to an NM
  • Step 502 The NM receives service traffic information of a network slice, and determines service traffic information of a network slice subnet based on the service traffic information of the network slice.
  • Step 502 may be performed with reference to step 403, and details are not described herein again.
  • Step 503 The NM sends the service traffic information of the network slice subnet to a DM.
  • Step 503 may be performed with reference to step 405, and details are not described herein again.
  • Step 504 The DM receives the service traffic information of the network slice subnet from the NM, and manages the network slice subnet based on the service traffic information of the network slice subnet.
  • Step 504 may be performed with reference to step 406, and details are not described herein again.
  • the NM and the DM are mutually configured to deploy the network slice subnet or select the available network slice subnet in the existing network.
  • a device performs auto-management on the network slice in real time based on the service traffic information, which prevents a process of manually off-line network planning, improves efficiency in deploying the network slice, and reduces on-boarding time of a service.
  • FIG. 6 shows yet another method for deploying a network slice according to an embodiment of the present invention.
  • the method may include the following steps.
  • Step 601 An SMF receives a service management request message.
  • step 601 For a performing process and the service management request message in step 601, refer to related descriptions in step 401, and details are not described herein again.
  • Step 602 The SMF determines service traffic information of a network slice based on the received service management request message.
  • Step 602 may be performed with reference to step 402, for the service traffic information of the network slice, refer to related descriptions in step 301, and details are not described herein again.
  • Step 603 The SMF sends the service traffic information of the network slice to a first NM
  • step 603 For a performing process of step 603, refer to step 403, and details are not described herein again.
  • Step 604 The first NM receives the service traffic information of the network slice from the SMF, and sends the service traffic information of the network slice to a second NM
  • the service traffic information that is sent by the first NM to the second NM and that is of the network slice may be the service traffic information that is received by the first NM and that is of the network slice, or may be decomposed service traffic information that is of a second network slice and that is determined by the first NM based on the received service traffic information of the network slice. This is not limited hereto in this embodiment of the present invention.
  • Step 605 The second NM receives the service traffic information of the network slice from the first NM, and determines service traffic information of a network slice subnet based on the service traffic information of the network slice.
  • That the first NM determines service traffic information of a network slice subnet based on the service traffic information of the network slice in step 605 may be performed with reference to step 404, and details are not described herein again.
  • Step 606 The second NM sends the service traffic information of the network slice subnet to a DM.
  • Step 606 may be performed with reference to step 405, and details are not described herein again.
  • Step 607 The DM receives the service traffic information of the network slice subnet from the second NM, and manages the network slice subnet based on the service traffic information of the network slice subnet.
  • Step 607 may be performed with reference to step 406, and details are not described herein again.
  • the foregoing steps 603 to 607 may be replaced by:
  • the SMF deploys, based on the service traffic information of the network slice, the network slice or selects the available network slice in the existing network.
  • the SMF deploys based on the service traffic information of the network slice, the network slice or selects the available network slice in the existing network.
  • the NM deploys based on the service traffic information of the network slice, the network slice or selects the available network slice in the existing network. Details are not described herein again.
  • the foregoing steps 605 to 607 may be replaced by:
  • the second NM deploys, based on the service traffic information of the network slice, the network slice or selects the available network slice in the existing network.
  • the second NM deploys, based on the service traffic information of the network slice, the network slice or selects the available network slice in the existing network, refer to related descriptions in step 302, and details are not described herein again.
  • the foregoing steps 605 to 607 may be replaced by:
  • the second NM receives the service traffic information of the network slice from the first NM, the second NM sends the service traffic information of the network slice to the DM, and the DM deploys, based on the received service traffic information of the network slice, the network slice or selects the available network slice in the existing network.
  • the DM deploys, based on the service traffic information of the network slice, the network slice or selects the available network slice in the existing network
  • the NM deploys, based on the service traffic information of the network slice, the network slice or selects the available network slice in the existing network refer to the manner, in FIG. 3 , in which the NM deploys, based on the service traffic information of the network slice, the network slice or selects the available network slice in the existing network, and details are not described herein again.
  • the SMF, the first NM, the second NM, and the DM are mutually configured to deploy the network slice subnet or select the available network slice subnet in the existing network.
  • a device performs auto-management on the network slice in real time based on the service traffic information, which prevents a process of manually off-line network planning, improves efficiency in deploying the network slice, and reduces on-boarding time of a service.
  • each node such as the SMF, the NM, and the DM, includes a corresponding hardware structure and/or a software module for performing each function.
  • each node such as the SMF, the NM, and the DM
  • the present invention may be implemented by hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving hardware depends on particular applications and design constraints of the technical solutions. Persons skilled in the art can use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of the embodiments of the present invention.
  • function modules of the SMF, the NM, and the DM may be divided based on the foregoing method examples.
  • function modules may be divided corresponding to the functions, or two or more functions may be integrated into one processing module.
  • the foregoing integrated module may be implemented in a hardware form or a software function module form. It should be noted that the module division in the embodiments of the present invention is an example, and is merely logical function division. There may be another division manner in an actual implementation.
  • FIG. 7 is a possible schematic composition diagram of an NM, and the NM may be configured to perform the functions of the NM that are related in the foregoing embodiments.
  • the NM may include a receiving unit 70, a deployment unit 71, and a sending unit 72.
  • the receiving unit 70 is configured to support the NM in performing step 301, step 404, step 502, and step 605.
  • the deployment unit 71 is configured to support the NM in performing step 302, step 404, step 502, and step 605.
  • the sending unit 72 is configured to support the NM in performing step 405, step 503, and step 606.
  • the NM provided in this embodiment of the present invention is configured to perform the method for deploying a network slice, and therefore can reach the same effect as that of the foregoing method for deploying a network slice.
  • FIG. 8 shows an apparatus.
  • the apparatus exists as a product form of a chip, and is configured to perform the functions of the NM in the foregoing embodiments.
  • the apparatus may include a processing module 80 and a communications module 81.
  • the processing module 80 is configured to control and manage an action of the apparatus.
  • the processing module 80 is configured to support the apparatus in performing step 302, step 404, step 502, and step 605 and/or other processes used for the technology described in this specification.
  • the communications module 81 is configured to support communication between the apparatus and another network entity, for example, communication between the apparatus and the function module or the network entity shown in FIG. 1 .
  • the apparatus may further include a storage module 82 that is configured to store program code and data that are of the apparatus.
  • the processing module 80 may be a processor or a controller.
  • the processing module 80 may implement or execute various exemplary logical blocks, modules, and circuits described with reference to content disclosed in the present invention.
  • the processor may also be a combination that implements a computing function, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, or the like.
  • the communications module 81 may be a communications interface, a transceiver circuit, a communications interface, or the like.
  • the storage module 82 may be a memory.
  • the apparatus related in an embodiment of the present invention may be the apparatus shown in FIG. 2 .
  • FIG. 9 is a possible schematic composition diagram of a DM, and the DM may be configured to perform the functions of the DM that are related in the foregoing embodiments.
  • the DM may include a receiving unit 90, and a management unit 91.
  • the receiving unit 90 is configured to support the DM in performing step 406, step 504, and step 607.
  • the management unit 91 is configured to support the DM in performing step 406, step 504, and step 607.
  • the DM provided in an embodiment of the present invention is configured to perform the foregoing method for deploying a network slice, and therefore can reach the same effect as that of the foregoing method for deploying a network slice.
  • FIG. 10 shows an apparatus.
  • the apparatus exists as a product form of a chip, and the apparatus is configured to perform the functions of the DM in the foregoing embodiments.
  • the apparatus may include: a processing module 100, and a communications module 101.
  • the processing module 100 is configured to control and manage an action of the apparatus.
  • the processing module 100 is configured to support the apparatus in performing step 406, step 504, and step 607 and/or other processes used for the technology described in this specification.
  • the communications module 101 is configured to support communication between the apparatus and another network entity, for example, communication between the apparatus and the function module or the network entity shown in FIG. 1 .
  • the apparatus may further include a storage module 102 that is configured to store program code and data that are of the apparatus.
  • the processing module 100 may be a processor or a controller.
  • the processing module 100 may implement or execute various exemplary logical blocks, modules, and circuits described with reference to content disclosed in the present invention.
  • the processor may also be a combination that implements a computing function, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, or the like.
  • the communications module 101 may be a communications interface, a transceiver circuit, a communications interface, or the like.
  • the storage module 102 may be a memory.
  • the apparatus related in an embodiment of the present invention may be the apparatus shown in FIG. 2 .
  • FIG. 11 is a possible schematic structural diagram of an SMF.
  • the SMF may include: a receiving unit 110, a determining unit 111, and a sending unit 112.
  • the receiving unit 110 is configured to support the SMF in performing step 401 and step 601.
  • the determining unit 111 is configured to support the SMF in performing step 402 and step 602.
  • the sending unit 112 is configured to support the SMF in performing step 403 and step 603.
  • the SMF provided in this embodiment of the present invention is configured to perform the foregoing method for deploying a network slice, and therefore can reach the same effect as that of the foregoing method for deploying a network slice.
  • FIG. 12 shows an apparatus.
  • the apparatus exists as a product form of a chip, and the apparatus is configured to perform the functions of the SMF in the foregoing embodiments.
  • the apparatus may include: a processing module 120, and a communications module 121.
  • the processing module 120 is configured to control and manage an action of the apparatus.
  • the processing module 120 is configured to support the apparatus in performing step 402 and step 602.
  • the communications module 121 is configured to support communication between the apparatus and another network entity, for example, communication between the apparatus and the function module or the network entity shown in FIG. 1 .
  • the apparatus may further include a storage module 122 that is configured to store program code and data that are of the apparatus.
  • the processing module 120 may be a processor or a controller.
  • the processing module 120 may implement or execute various exemplary logical blocks, modules, and circuits described with reference to content disclosed in the present invention.
  • the processor may also be a combination that implements a computing function, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, or the like.
  • the communications module 121 may be a communications interface, a transceiver circuit, a communications interface, or the like.
  • the storage module 122 may be a memory.
  • the apparatus related in an embodiment of the present invention may be the apparatus shown in FIG. 2 .
  • the disclosed apparatus and method may be implemented in other manners.
  • the described apparatus embodiment is merely exemplary.
  • the module or unit division is merely logical function division and may be other division manners in actual implementation.
  • a plurality of units or components may be combined or integrated into another apparatus, or some features may be ignored or not performed.
  • the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented by using some interfaces.
  • the indirect couplings or communication connections between the apparatuses or units may be implemented in electrical, mechanical, or other forms.
  • the units described as separate parts may or may not be physically separate, and parts displayed as units may be one or more physical units, that is, may be located in one place, or may be distributed on a plurality of different places. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments.
  • functional units in the embodiments of the present invention may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units may be integrated into one unit.
  • the foregoing integrated unit can be implemented in a form of hardware, or can be implemented in a form of a software functional unit.
  • the integrated unit When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a readable storage medium.
  • the software product is stored in a storage medium and includes several instructions for enabling a device (may be a single-chip microcomputer, a chip, or the like) or a processor (processor) to perform all or some of the steps of the methods described in all the embodiments of the present invention.
  • the foregoing storage medium includes: any medium that can store program code, such as a USB flash drive, a removable hard disk, a ROM, a RAM, a magnetic disk, an optical disc, or the like.
  • a method for deploying a network slice comprising:
  • Embodiment 2 The method for deploying a network slice according to embodiment 1, wherein the network slice comprises a network slice subnet, and the method further comprises: determining, by the first network management unit, service traffic information of the network slice subnet based on the service traffic information of the network slice.
  • Embodiment 3 The method for deploying a network slice according to embodiment 2, wherein the deploying, by the first network management unit based on the service traffic information of the network slice, the network slice or selecting an available network slice in an existing network comprises: deploying, by the first network management unit based on the service traffic information of the network slice subnet, the network slice subnet or selecting the available network slice subnet in the existing network.
  • Embodiment 4 The method for deploying a network slice according to embodiment 2, wherein the method further comprises: sending, by the first network management unit, the service traffic information of the network slice subnet to a domain management unit.
  • Embodiment 5 The method for deploying a network slice according to any one of embodiments 1 to 4, wherein the method further comprises:
  • Embodiment 6 The method for deploying a network slice according to any one of embodiments 1 to 5, wherein the method further comprises: sending, by the first network management unit, the service traffic information of the network slice to a third network management unit.
  • Embodiment 7 The method for deploying a network slice according to any one of embodiments 1 to 6, wherein the service traffic information of the network slice comprises at least one of the following information: a quantity of terminal devices, geographic distribution of the terminal devices, a service transmission status of the terminal devices, an activation ratio of the terminal devices, a usage time of a service, a coverage of the service, a moving status of the terminal devices, and a roaming status of the terminal devices.
  • Embodiment 8 A method for deploying a network slice, comprising:
  • Embodiment 9 The method for deploying a network slice according to embodiment 8, wherein the managing, by the domain management unit, the network slice subnet comprises at least one of the following manners:
  • Embodiment 10 The method for deploying a network slice according to embodiment 8 or 9, wherein the service traffic information of the network slice subnet comprises at least one of the following information: a quantity of terminal devices, geographic distribution of the terminal devices, a service transmission status of the terminal devices, an activation ratio of the terminal devices, a usage time of a service, a coverage of the service, a moving status of the terminal devices, and a roaming status of the terminal devices.
  • Embodiment 11 A method for deploying a network slice, comprising:
  • Embodiment 12 The method for deploying a network slice according to embodiment 11, wherein the method further comprises:
  • Embodiment 13 The method for deploying a network slice according to embodiment 11 or 12, wherein the determining, by the service management unit based on the traffic information of the service, service traffic information of the network slice comprises: decomposing, by the service management unit, the traffic information of the service into at least one piece of sub-service traffic information, and determining the decomposed at least one piece of sub-service traffic information as the service traffic information of the network slice.
  • Embodiment 14 The method for deploying a network slice according to any one of embodiments 11 to 13, wherein the traffic information of the service, the service traffic information of the network slice, and the sub-service traffic information comprise at least one of the following information: a quantity of terminal devices, geographic distribution of the terminal devices, a service transmission status of the terminal devices, an activation ratio of the terminal devices, a usage time of the service, a coverage of the service, a moving status of the terminal devices, and a roaming status of the terminal devices.
  • a network management unit comprising:
  • Embodiment 16 The network management unit according to embodiment 15, wherein the network slice comprises a network slice subnet, and the network management unit further comprises: a determining unit, configured to determine service traffic information of the network slice subnet based on the service traffic information of the network slice.
  • Embodiment 17 The network management unit according to embodiment 16, wherein the deployment unit is specifically configured to: deploy, based on the service traffic information of the network slice subnet, the network slice subnet or select the available network slice subnet in the existing network.
  • Embodiment 18 The network management unit according to embodiment 16, wherein the network management unit further comprises: a sending unit, configured to send the service traffic information of the network slice subnet to a domain management unit.
  • Embodiment 19 The network management unit according to any one of embodiments 15 to 18, wherein the receiving unit is specifically configured to:
  • Embodiment 20 The network management unit according to any one of embodiments 15 to 19, wherein the network management unit further comprises: a sending unit, configured to send the service traffic information of the network slice to the another network management unit other than the network management unit.
  • a sending unit configured to send the service traffic information of the network slice to the another network management unit other than the network management unit.
  • Embodiment 21 The network management unit according to any one of embodiments 15 to 20, wherein the service traffic information of the network slice comprises at least one of the following information: a quantity of terminal devices, geographic distribution of the terminal devices, a service transmission status of the terminal devices, an activation ratio of the terminal devices, a usage time of a service, a coverage of the service, a moving status of the terminal devices, and a roaming status of the terminal devices.
  • a domain management unit comprising:
  • Embodiment 23 The domain management unit according to embodiment 22, wherein the management unit is specifically configured to perform at least one of the following methods:
  • Embodiment 24 The domain management unit according to embodiment 22 or 23, wherein the service traffic information of the network slice subnet comprises at least one of the following information: a quantity of and geographic distribution of terminal devices, a service transmission status of the terminal devices, an activation ratio of the terminal devices, a usage time of a service, a moving status of the terminal devices, and a roaming status of the terminal devices.
  • a service management unit comprising:
  • Embodiment 26 The service management unit according to embodiment 25, wherein the service management unit further comprises:
  • Embodiment 27 The service management unit according to embodiment 25 or 26, wherein the determining unit is specifically configured to: decompose the traffic information of the service into at least one piece of sub-service traffic information, and determine the decomposed at least one piece of sub-service traffic information as the service traffic information of the network slice.
  • Embodiment 28 The service management unit according to any one of embodiments 25 to 27, wherein the traffic information of the service, the service traffic information of the network slice, and the sub-service traffic information comprise at least one of the following information: a quantity of terminal devices, geographic distribution of the terminal devices, a service transmission status of the terminal devices, an activation ratio of the terminal devices, a usage time of the service, a coverage of the service, a moving status of the terminal devices, and a roaming status of the terminal devices.
  • Embodiment 29 An apparatus, comprising: at least one processor, and a memory, wherein the memory is configured to store a computer program, and when executed by the at least one processor, the computer program is enabled to implement the method for deploying a network slice according to any one of claims 1 to 7.
  • Embodiment 30 A computer storage medium, storing a computer program, wherein when executed by a processor, the computer program is enabled to implement the method for deploying a network slice according to any one of embodiments 1 to 7.
  • Embodiment 31 An apparatus, comprising: at least one processor, and a memory, wherein the memory is configured to store a computer program, and when executed by the at least one processor, the computer program is enabled to implement the method for deploying a network slice according to any one of claims 8 to 10.
  • Embodiment 32 A computer storage medium, storing a computer program, wherein when executed by a processor, the program is enabled to implement the method for deploying a network slice according to any one of embodiments 8 to 10.
  • Embodiment 33 An apparatus, comprising: at least one processor, and a memory, wherein the memory is configured to store a computer program, and when executed by the at least one processor, the computer program is enabled to implement the method for deploying a network slice according to any one of claims 11 to 14.
  • Embodiment 34 A computer storage medium, storing a computer program, wherein when executed by a processor, the computer program is enabled to implement the method for deploying a network slice according to any one of embodiments 11 to 14.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
EP22185631.3A 2017-07-31 2018-07-13 Verfahren, vorrichtung und system zum einsatz von netzwerkslices Pending EP4142242A1 (de)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN201710642648.2A CN109327319B (zh) 2017-07-31 2017-07-31 部署网络切片的方法、设备及系统
PCT/CN2018/095677 WO2019024671A1 (zh) 2017-07-31 2018-07-13 部署网络切片的方法、设备及系统
EP18840518.7A EP3648404B1 (de) 2017-07-31 2018-07-13 Verfahren, vorrichtung und system zum einsatz von netzwerkslices

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
EP18840518.7A Division EP3648404B1 (de) 2017-07-31 2018-07-13 Verfahren, vorrichtung und system zum einsatz von netzwerkslices
EP18840518.7A Division-Into EP3648404B1 (de) 2017-07-31 2018-07-13 Verfahren, vorrichtung und system zum einsatz von netzwerkslices

Publications (1)

Publication Number Publication Date
EP4142242A1 true EP4142242A1 (de) 2023-03-01

Family

ID=65232207

Family Applications (2)

Application Number Title Priority Date Filing Date
EP18840518.7A Active EP3648404B1 (de) 2017-07-31 2018-07-13 Verfahren, vorrichtung und system zum einsatz von netzwerkslices
EP22185631.3A Pending EP4142242A1 (de) 2017-07-31 2018-07-13 Verfahren, vorrichtung und system zum einsatz von netzwerkslices

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP18840518.7A Active EP3648404B1 (de) 2017-07-31 2018-07-13 Verfahren, vorrichtung und system zum einsatz von netzwerkslices

Country Status (4)

Country Link
US (2) US11490327B2 (de)
EP (2) EP3648404B1 (de)
CN (1) CN109327319B (de)
WO (1) WO2019024671A1 (de)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109906585B (zh) 2016-10-31 2021-02-05 华为技术有限公司 网络切片的管理方法、管理单元及系统
WO2018094667A1 (zh) * 2016-11-24 2018-05-31 华为技术有限公司 一种管理方法、管理单元及系统
CN109327319B (zh) * 2017-07-31 2021-06-08 华为技术有限公司 部署网络切片的方法、设备及系统
US10637753B1 (en) * 2019-04-09 2020-04-28 Verizon Patent And Licensing Inc. Managing a 5G network using extension information
US10708368B1 (en) * 2019-10-30 2020-07-07 Verizon Patent And Licensing Inc. System and methods for generating a slice deployment description for a network slice instance
CN112910668B (zh) * 2019-11-19 2022-09-09 上海华为技术有限公司 一种业务配置方法，业务配置装置以及业务配置设备
US11696184B2 (en) * 2020-05-06 2023-07-04 Accenture Global Solutions Limited Quality of service manager for network slices of a network
CN114422342A (zh) * 2020-10-13 2022-04-29 中国移动通信有限公司研究院 传送网切片的部署方法、装置、设备及可读存储介质

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160352924A1 (en) * 2015-06-01 2016-12-01 Huawei Technologies Co., Ltd. Method and apparatus for customer service management for a wireless communication network

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11632714B2 (en) * 2015-10-15 2023-04-18 Telefonaktiebolaget Lm Ericsson (Publ) Apparatus and method for attaching user equipment to a mobile communications network
CN106657194B (zh) * 2015-11-02 2020-05-08 中兴通讯股份有限公司 一种网络切片能力开放的方法、装置及系统
US10129108B2 (en) * 2015-11-13 2018-11-13 Huawei Technologies Co., Ltd. System and methods for network management and orchestration for network slicing
US20180352501A1 (en) * 2015-12-29 2018-12-06 Telefonaktiebolaget Lm Ericsson (Publ) Method And Apparatus For Virtualized Network Service Provision
WO2017169283A1 (ja) * 2016-03-29 2017-10-05 株式会社Ｎｔｔドコモ スライス情報変更方法および通信システム
KR102633995B1 (ko) * 2016-08-22 2024-02-06 삼성전자 주식회사 무선 통신 시스템에서, 단말과 써드 파티 서버 간의 인증 요청 방법 및, 이를 위한 단말 및 네트워크 슬라이스 인스턴스 관리 장치
WO2018089417A1 (en) * 2016-11-09 2018-05-17 Interdigital Patent Holdings, Inc. Systems and methods to create slices at a cell edge to provide computing services
CN106792739B (zh) * 2016-11-17 2020-01-21 北京邮电大学 网络切片方法、装置和设备
EP3596887A1 (de) * 2017-03-16 2020-01-22 Intel IP Corporation Unterstützung von son-funktionen auf netzwerkslice-instanzen
US10608895B2 (en) * 2017-03-31 2020-03-31 At&T Intellectual Property I, L.P. Quality of service management for dynamic instantiation of network slices and/or applications
WO2018200733A1 (en) * 2017-04-27 2018-11-01 Intel IP Corporation Enhanced network slice management for wireless communications
US10257668B2 (en) * 2017-05-09 2019-04-09 At&T Intellectual Property I, L.P. Dynamic network slice-switching and handover system and method
US10601932B2 (en) * 2017-06-09 2020-03-24 At&T Intellectual Property I, L.P. Next generation mobility core network controller for service delivery
CN109327319B (zh) * 2017-07-31 2021-06-08 华为技术有限公司 部署网络切片的方法、设备及系统

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160352924A1 (en) * 2015-06-01 2016-12-01 Huawei Technologies Co., Ltd. Method and apparatus for customer service management for a wireless communication network

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Study on management and orchestration of network slicing for next generation network (Release 15)", 3GPP STANDARD ; TECHNICAL REPORT ; 3GPP TR 28.801, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. V1.2.0, 31 May 2017 (2017-05-31), pages 1 - 79, XP051298434 *
HUAWEI: "Solution section reorganization", vol. SA WG5, no. West Palm Beach, Florida (US); 20170508 - 20170512, 7 May 2017 (2017-05-07), XP051260045, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/SA5/Docs/> [retrieved on 20170507] *

Also Published As

Publication number Publication date
US11490327B2 (en) 2022-11-01
EP3648404A4 (de) 2020-05-06
US20200163011A1 (en) 2020-05-21
US20230041039A1 (en) 2023-02-09
EP3648404A1 (de) 2020-05-06
CN109327319A (zh) 2019-02-12
WO2019024671A1 (zh) 2019-02-07
CN109327319B (zh) 2021-06-08
US12063594B2 (en) 2024-08-13
EP3648404B1 (de) 2022-08-31

Similar Documents

Publication Publication Date Title
US12063594B2 (en) Method, device, and system for deploying network slice
US11146462B2 (en) Network slice management method, device, and system
US11831509B2 (en) Network service management method, device, and system
US10999740B2 (en) Network slice management method, management unit, and system
US10924966B2 (en) Management method, management unit, and system
CN109391490B (zh) 网络切片的管理方法和装置
CN109600760B (zh) 网络管理方法、设备及系统
US11489737B2 (en) Network performance assurance method and apparatus

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20220719

AC Divisional application: reference to earlier application

Ref document number: 3648404

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20231102