EP3664372B1 - Procédé de gestion de réseau, et dispositif associé - Google Patents

Procédé de gestion de réseau, et dispositif associé Download PDF

Info

Publication number
EP3664372B1
EP3664372B1 EP18851568.8A EP18851568A EP3664372B1 EP 3664372 B1 EP3664372 B1 EP 3664372B1 EP 18851568 A EP18851568 A EP 18851568A EP 3664372 B1 EP3664372 B1 EP 3664372B1
Authority
EP
European Patent Office
Prior art keywords
amf
ids
nsi
nssi
corresponds
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.)
Active
Application number
EP18851568.8A
Other languages
German (de)
English (en)
Other versions
EP3664372A4 (fr
EP3664372A1 (fr
Inventor
Shuigen Yang
Wei Lu
Wenqi SUN
Wei Tan
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 EP3664372A1 publication Critical patent/EP3664372A1/fr
Publication of EP3664372A4 publication Critical patent/EP3664372A4/fr
Application granted granted Critical
Publication of EP3664372B1 publication Critical patent/EP3664372B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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/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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • 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
    • 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/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Definitions

  • Embodiments of the present invention relate to the field of communications technologies, and in particular, to a network management method and a related device.
  • a 5th generation (5th Generation, 5G) communications network is oriented to different application scenarios, for example, an ultra-high-definition video, virtual reality, the massive internet of things, and the internet of vehicles. Different scenarios have different requirements on mobility, security, a latency, reliability, and even a charge mode of a network.
  • a future network needs to have a capability of being customized based on a requirement.
  • a network slice needs to be flexibly configured.
  • a physical network is sliced into a plurality of virtual network slices, and the virtual network slices are oriented to different application scenario requirements.
  • One network slice meets a communications service requirement of one type of use case or one use case, and an entire 5G communications network includes a large quantity of network slices that meet different service requirements.
  • a network slice is created and applied in a form of a network slice instance and/or a network slice subnet instance.
  • each user equipment User Equipment, UE can support one or more network slice instances and/or network slice subnet instances.
  • a network slice selection function (Network Slice Selection Function, NSSF) is introduced into the telecommunications network to select a network slice instance and/or a network slice subnet instance for the UE, and a network function repository function (Network Function Repository Function, NRF) is introduced to select an access and mobility management function (Access and Mobility management Function, AMF) corresponding to the network slice instance and/or the network slice subnet instance.
  • NRF Network Function Repository Function
  • AMF Access and Mobility management Function
  • the NSSF needs to determine an AMF corresponding to the network slice instance and/or the network slice subnet instance. Therefore, how to select a unique access and mobility management function corresponding to a network slice instance and/or a network slice subnet instance is a technical problem that needs to be currently resolved.
  • NSSF and slice selection during the registration procedures 3GPP draft; S2-175216_WAS4992_WAS4202 REG PROC CORR INCL NSSF SA122 is a standardization document dealing with network slice selection in communication systems.
  • Embodiments of the present invention provide a network management method and a related device, to efficiently select a unique access and mobility management function corresponding to a network slice instance and/or a network slice subnet instance.
  • Network slices are different logical networks customized based on different service requirements.
  • a network slice may be a complete end-to-end network including a terminal, an access network, a transport network, a core network, and an application server.
  • the network slice can provide a complete telecommunication service and has a particular network capability.
  • the network slice may be any combination of the terminal, the access network, the transport network, the core network, and the application server.
  • the network slice instance (Network Slice Instance, NSI) is instantiation for the NS.
  • the network slice instance is an actually running logical network, and can meet a particular network feature or service requirement.
  • One network slice instance may provide one or more services.
  • the network slice instance may be created by a network slice management function device.
  • One network slice management function device may create and manage a plurality of network slice instances, for example, perform performance monitoring and fault management in a running process of the network slice instances. When a plurality of network slice instances coexist, the network slice instances may share some network resources and network functions.
  • the network slice instance may be created from a network slice template, or may not be created from a network slice template.
  • a complete network slice instance can provide a complete end-to-end network service
  • a network slice instance may include a network slice subnet instance (Network Slice Subnet Instance, NSSI) and/or a network function.
  • the network function may include a physical network function and/or a virtual network function.
  • the physical network function and/or the virtual network function are/is collectively referred to as the network function below.
  • One network slice instance may be divided into several network slice subnet instances, to facilitate management performed by a network management system.
  • the network slice subnet instance may not need to provide a complete end-to-end network service.
  • the network slice subnet instance may be a set of network functions of a same device vendor in the network slice instance; or may be a set of network functions obtained through domain-based division, for example, a core network slice subnet instance and an access network slice subnet instance; or may be a set formed based on a deployment location or in another manner.
  • One network slice subnet instance may be shared by a plurality of network slice instances.
  • the network function (Network function, NF) is a processing function in a network, and defines a functional behavior and interface.
  • the network function may be implemented by using special-purpose hardware, or may be implemented by running software on special-purpose hardware, or may be implemented in a form of a virtual function on a general-purpose hardware platform. Therefore, from a perspective of implementation, the network function may be classified into a physical network function and a virtual network function. From a perspective of use, the network function may be classified into a dedicated network function and a shared network function. Specifically, a plurality of network slice instances/network slice subnet instances may independently use different network functions, and these network functions are referred to as dedicated network functions. Alternatively, a plurality of network slice instances/network slice subnet instances may share a same network function, and the network function is referred to as a shared network function.
  • One network management system may create and manage a plurality of network slice instances, for example, modify and terminate the plurality of network slice instances, and perform performance monitoring and fault management on the plurality of network slice instances in a running process of the network slice instances.
  • a complete network slice instance can provide a complete end-to-end network service, and a network slice instance may include a network slice subnet instance and/or a network function.
  • a network slice instance is identified by a network slice instance identifier (Network Slice Instance ID, NSI ID).
  • NSI ID Network Slice Instance ID
  • NSSI ID Network Slice Subnet Instance ID
  • the NSI ID and the NSSI ID may be character strings, or may be names that can be understood by human beings.
  • the network When user equipment is registered with a telecommunications network, the network needs to select a unique network slice instance/network slice subnet instance for the user equipment based on single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI) corresponding to the user equipment. In addition, the network further needs to select an appropriate access and mobility management function (Access and Mobility management Function, AMF) for the user equipment based on the selected network slice instance/network slice subnet instance.
  • AMF Access and Mobility management Function
  • the AMF is a core network element, and is mainly responsible for signaling processing, namely, control plane functions, including functions such as access control, mobility management, attachment, detachment, and gateway selection.
  • FIG. 1 is a schematic architectural diagram of a network system according to an embodiment of the present invention. As shown in FIG. 1 , the network system 100 includes a first network device 101 and a second network device 102.
  • the first network device 101 is mainly responsible for managing a lifecycle, performance, a fault, a configuration, and the like of an NSI/NSSI, and orchestrating components of the NSI/NSSI.
  • the lifecycle management, performance management, fault management, configuration management, orchestration, and the like of the NSI/NSSI and the components (for example, a slice subnet instance and a network function) of the NSI/NSSI are collectively referred to as management.
  • the first network device 101 may be a network manager (Network Manager, NM), a domain manager (Domain Manager, DM), an element manager (Element Manager, EM), a network slice management function (Network Slice Management Function, NSMF), a network slice subnet management function (Network Slice Subnet Management Function, NSSMF), a communication service management function (Communication Service Management Function, CSMF), a network functions virtualization orchestration (Network Function Virtualization Orchestration, NFVO) function, or a virtualized network function manager (Virtualized Network Function Manager, VNFM), or may be any combination of the foregoing modules, for example, a combination of the NSMF and the EM, or a combination of the NSSMF and the EM.
  • Network Manager Network Manager
  • NM Network Manager
  • DM Domain Manager
  • EM element manager
  • NSMF Network Slice Management Function
  • NSSMF Network Slice Subnet Management Function
  • CSMF Communication Service Management Function
  • NFVO Network Function Virtualization Orchestration
  • VNFM
  • a name of the first network device 101 includes, but is not limited to, network slice management and orchestration (Network Slice Management and Orchestration, NSMAO).
  • a name of the second network device 102 includes, but is not limited to, a network function repository function (Network Function Repository Function, NRF).
  • Main functions of the second network device 102 include: supporting a service discovery function, providing related NF instance information, maintaining information between an available NF instance and a service supported by the NF instance, and being responsible for selecting, based on an identifier of an NSI/NSSI, an AMF associated with the NSI/NSSI.
  • the first network device 101 may be any device that has the functions of the first network device 101
  • the second network device 102 may be any device that has the functions of the second network device 102.
  • FIG. 2 is a flowchart of a network management method according to an embodiment of the present invention.
  • the network management method includes, but is not limited to, the following steps S201 to S203.
  • the first network device obtains a configuration parameter, where the configuration parameter includes a network slice instance identifier and an access and mobility management function identifier corresponding to the network slice instance identifier, and/or a network slice subnet instance identifier and an access and mobility management function identifier corresponding to the network slice subnet instance identifier.
  • the first network device may store a capability of supporting a specific NSI/NSSI by each AMF, and the first network device may determine, based on the capability of each AMF, an AMF corresponding to each NSI ID/NSSI ID.
  • An AMF corresponding to an NSI ID means that the AMF has a capability of providing the NSI
  • an AMF corresponding to an NSSI ID means that the AMF has a capability of providing the NSSI.
  • the configuration parameter is used to be configured on the second network device.
  • the first network device may be an NSMAO.
  • the second network device may be an NRF.
  • the first network device generates the configuration parameter or obtains the configuration parameter from another network device, or a network administrator enters the configuration parameter into the first network device.
  • the configuration parameter includes a correspondence between the NSI ID and the AMF ID. In another embodiment, the configuration parameter includes a correspondence between the NSSI ID and the AMF ID. In another embodiment, the configuration parameter includes a correspondence between the NSI ID and the AMF ID and a correspondence between the NSSI ID and the AMF ID. In another embodiment, the configuration parameter includes a correspondence between the NSI ID, the NSSI ID, and the AMF ID.
  • the AMF ID includes a GUAMI corresponding to an AMF or an IP address.
  • the GUAMI is used to identify a globally unique AMF identity.
  • the AMF Region ID is used to identify a region.
  • the AMF Set ID is used to uniquely identify an AMF set in the region.
  • the AMF Pointer is used to uniquely identify an AMF in the set.
  • the GUAMI may be a fully qualified domain name (Fully Qualified Domain Name, FQDN).
  • each NSI ID/NSSI ID in the configuration parameter may correspond to only one AMF.
  • one NSI ID/NSSI ID corresponds to one AMF ID
  • content included in the configuration parameter and formats of the content may be, for example, shown in any one of Table 1 to Table 6.
  • an NSI 1 whose NSI ID is 1 corresponds to an identifier 001 of an AMF 1
  • an NSI 2 whose NSI ID is 2 corresponds to an identifier 002 of an AMF 2
  • an NSI 3 whose NSI ID is 3 corresponds to an identifier 003 of an AMF 3.
  • an NSI 1 whose NSI ID is 1 corresponds to an identifier 224.000.0.1 of an AMF 1
  • an NSI 2 whose NSI ID is 2 corresponds to an identifier 225.000.0.1 of an AMF 2
  • an NSI 3 whose NSI ID is 3 corresponds to an identifier 226.000.0.1 of an AMF 3.
  • an NSSI 1 whose NSSI ID is 01 corresponds to an identifier 001 of an AMF 1
  • an NSSI 2 whose NSSI ID is 02 corresponds to an identifier 002 of an AMF 2
  • an NSSI 3 whose NSSI ID is 03 corresponds to an identifier 003 of an AMF 3.
  • an NSSI 1 whose NSSI ID is 01 corresponds to an identifier 224.000.0.1 of an AMF 1
  • an NSSI 2 whose NSSI ID is 02 corresponds to an identifier 225.000.0.1 of an AMF 2
  • an NSSI 3 whose NSSI ID is 03 corresponds to an identifier 226.000.0.1 of an AMF 3.
  • the configuration parameter includes both a correspondence between an NSI ID and an AMF ID and a correspondence between an NSSI ID and an AMF ID.
  • the configuration parameter includes both a correspondence between an NSI ID and an AMF IP and a correspondence between an NSSI ID and an AMF IP.
  • the second network device can uniquely determine, based on the NSI ID/NSSI ID, an AMF corresponding to the NSI ID/NSSI ID.
  • each NSI ID/NSSI ID in the configuration parameter may correspond to two or more AMFs.
  • one NSI ID/NSSI ID corresponds to at least two AMF IDs, and content included in the configuration parameter and formats of the content may be, for example, shown in any one of Table 7 to Table 12.
  • an NSI 1 whose NSI ID is 1 corresponds to an identifier 001 of an AMF 1 and an identifier 002 of an AMF 2
  • an NSI 2 whose NSI ID is 2 corresponds to the identifier 001 of the AMF 1 and an identifier 003 of an AMF 3
  • an NSI 3 whose NSI ID is 3 corresponds to the identifier 001 of the AMF 1, the identifier 002 of the AMF 2 and the identifier 003 of the AMF 3.
  • an NSI 1 whose NSI ID is 1 corresponds to an identifier 224.000.0.1 of an AMF 1 and an identifier 225.000.0.1 of an AMF 2
  • an NSI 2 whose NSI ID is 2 corresponds to the identifier 224.000.0.1 of the AMF 1 and an identifier 226.000.0.1 of an AMF 3
  • an NSI 3 whose NSI ID is 3 corresponds to the identifier 224.000.0.1 of the AMF 1, the identifier 225.000.0.1 of the AMF 2, and the identifier 226.000.0.1 of the AMF 3.
  • an NSSI 1 whose NSSI ID is 01 corresponds to an identifier 001 of an AMF 1 and an identifier 002 of an AMF 2
  • an NSSI 2 whose NSSI ID is 02 corresponds to the identifier 001 of the AMF 1 and an identifier 003 of an AMF 3
  • an NSSI 3 whose NSSI ID is 03 corresponds to the identifier 001 of the AMF 1, the identifier 002 of the AMF 2 and the identifier 003 of the AMF 3.
  • an NSSI 1 whose NSSI ID is 01 corresponds to an identifier 224.000.0.1 of an AMF 1 and an identifier 225.000.0.1 of an AMF 2
  • an NSSI 2 whose NSSI ID is 02 corresponds to the identifier 224.000.0.1 of the AMF 1 and an identifier 226.000.0.1 of an AMF 3
  • an NSSI 3 whose NSSI ID is 03 corresponds to the identifier 224.000.0.1 of the AMF 1, the identifier 225.000.0.1 of the AMF 2, and the identifier 226.000.0.1 of the AMF 3.
  • the configuration parameter includes both a correspondence between an NSI ID and an AMF ID and a correspondence between an NSSI ID and an AMF ID.
  • the configuration parameter includes both a correspondence between an NSI ID and an AMF IP and a correspondence between an NSSI ID and an AMF IP.
  • the second network device can determine, based on the NSI ID/NSSI ID, at least two AMFs corresponding to the NSI ID/NSSI ID.
  • the configuration parameter may further include assistance information corresponding to AMFs, and the assistance information is used to instruct the second network device to select the AMF IDs.
  • the assistance information includes, but is not limited to, one or any combination of a priority, location information, access technology information, traffic load, and a quantity of access users.
  • the priority is used to indicate a priority of an AMF ID.
  • the location information includes one or any combination of a tracking area identity (Tracking Area Identity, TAI), a routing area identity (Routing Area Identity, RAI), and an evolved-universal mobile telecommunications system terrestrial radio access network cell global identifier (Evolution-Universal Mobile Telecommunications System Terrestrial Radio Access Network Cell Global Identity, ECGI).
  • TAI Track Area Identity
  • RAI routing Area Identity
  • ECGI evolved-universal mobile telecommunications system terrestrial radio access network cell global identifier
  • the access technology information is used to indicate an access technology used when user equipment accesses a network slice instance and/or a network slice subnet instance.
  • the assistance information may alternatively be any combination of the priority, the location information, the access technology information, the traffic load, and the quantity of access users.
  • the first network device and the second network device may negotiate in advance that a smaller priority sequence number indicates a higher priority, and a larger priority sequence number indicates a lower priority. Therefore, priorities of the AMF 001 to the AMF 003 are the AMF 001, the AMF 002, and the AMF 003 in descending order.
  • a same AMF may have different priorities for different NSIs/NSSIs.
  • a priority of an AMF whose AMF ID is 001 is 1, and a priority of an AMF whose AMF ID is 002 is 2; and for an NSI ID 3, a priority of the AMF whose AMF ID is 001 is 3, and a priority of the AMF whose AMF ID is 002 is 2.
  • Table 14 NSI ID AMF ID AMF priority 1 001 1 1 002 2 2 001 1 2 003 2 3 001 3 3 002 2 3 003 1
  • the first network device sends the configuration parameter to the second network device.
  • the first network device may add the configuration parameter to a management request or a configuration request, and send the management request or the configuration request to the second network device.
  • the first network device may send a management request to the second network device for a plurality of times, where the management request sent each time includes one correspondence.
  • Table 1 there are three correspondences: a correspondence between the NSI ID 1 and the AMF ID 001, a correspondence between the NSI ID 2 and the AMF ID 002, and a correspondence between the NSI ID 3 and the AMF ID 003.
  • the first network device may send a management request to the second network device for three times.
  • the management request sent for the first time carries the correspondence between the NSI ID 1 and the AMF ID 001
  • the management request sent for the second time carries the correspondence between the NSI ID 2 and the AMF ID 002
  • the management request sent for the third time carries the correspondence between the NSI ID 3 and the AMF ID 003.
  • the first network device may send a management request to the second network device for only one time, and the management request includes a plurality of correspondences. Using Table 1 as an example, there are three correspondences.
  • the first network device may send a management request to the second network device for only one time.
  • the management request carries the correspondence between the NSI ID 1 and the AMF ID 001, the correspondence between the NSI ID 2 and the AMF ID 002, and the correspondence between the NSI ID 3 and the AMF ID 003.
  • the second network device configures the configuration parameter.
  • the second network device when receiving a selection request used to select an AMF, determines, based on a network slice instance identifier/network slice subnet instance identifier carried in the selection request and the correspondence, a target AMF corresponding to the network slice instance identifier and/or the network slice subnet instance identifier.
  • a target AMF ID corresponding to the network slice instance identifier/network slice subnet instance identifier may be a GUAMI corresponding to the target AMF, or may be an IP address of the target AMF. If the target AMF ID is the IP address of the target AMF, the second network device may send the IP address of the target AMF to an NSSF, and then the NSSF sends the IP address of the target AMF to an initial AMF. In this way, the initial AMF can directly obtain the IP address of the target AMF.
  • the NSSF sends the GUAMI of the target AMF to the initial AMF, and then the AMF obtains, by using a domain name system (Domain Name System, DNS), the IP address corresponding to the GUAMI of the target AMF, this manner enables the initial AMF to directly obtain the IP address of the target AMF instead of further parsing the AMF ID, so that a processing procedure of the initial AMF is reduced, and signaling overheads are reduced.
  • DNS Domain Name System
  • each network slice instance identifier/network slice subnet instance identifier corresponds to one AMF ID.
  • the second network device may uniquely determine, by searching the configuration parameter based on the network slice instance identifier/network slice subnet instance identifier, an AMF ID corresponding to the network slice instance identifier/network slice subnet instance identifier.
  • Table 1 as an example, if the network slice instance identifier is 1, the second network device may determine, by searching the configuration parameter shown in Table 1, that a target AMF ID corresponding to 1 is 001.
  • the second network device may determine, by searching the configuration parameter shown in Table 2, that a target AMF ID corresponding to 1 is 224.000.0.1.
  • Table 3 if the network slice subnet instance identifier is 01, the second network device may determine, by searching the configuration parameter shown in Table 3, that a target AMF ID corresponding to 01 is 001.
  • Table 4 if the network slice subnet instance identifier is 01, the second network device may determine, by searching the configuration parameter shown in Table 4, that a target AMF ID corresponding to 01 is 224.000.0.1.
  • each network slice instance identifier/network slice subnet instance identifier corresponds to two or more AMF IDs. Because one network slice instance identifier/network slice subnet instance identifier corresponds to at least two AMF identifiers, the second network device needs to determine a target AMF ID from the at least two AMF IDs with reference to the assistance information sent by the first network device, where the assistance information is used by the second network device to select one of a plurality of AMF IDs corresponding to the network slice instance identifier/network slice subnet instance identifier.
  • the second network device After obtaining the assistance information, and when receiving the selection request used to select an AMF, the second network device determines, based on the network slice instance identifier/network slice subnet instance identifier carried in the selection request, the correspondence, and the assistance information, the target AMF corresponding to the network slice instance identifier/network slice subnet instance identifier. For example, after receiving the NSI ID/NSSI ID, the second network device selects, based on priorities of AMFs, an AMF with a highest priority from the AMFs corresponding to the NSI ID/NSSI ID.
  • the second network device obtains location information of the user equipment, and selects an AMF that is in AMFs corresponding to the NSI ID/NSSI ID and whose location information is consistent with the location information of the user equipment.
  • the second network device obtains an access technology of the user equipment, and selects an AMF that is in AMFs corresponding to the NSI ID/NSSI ID and whose access technology is consistent with the access technology of the user equipment.
  • the second network device obtains current traffic load of each of AMFs corresponding to the NSI ID/NSSI ID, and selects an AMF with smallest traffic load.
  • the second network device obtains a quantity of users currently accessing each of AMFs corresponding to the NSI ID/NSSI ID, and selects an AMF with a smallest quantity of access users.
  • the second network device may determine, by searching the configuration parameter shown in Table 14, that AMF IDs corresponding to 1 include 001 and 002, and a priority of the AMF 001 is higher than that of the AMF 002. In this case, the second network device finally determines that a target AMF ID corresponding to 1 is 001.
  • the assistance information is used to select the target AMF based on current traffic load of an AMF.
  • the second network device may determine, by searching the configuration parameter shown in Table 8, that AMF IDs corresponding to 1 include 224.000.0.1 and 225.000.0.1, and the second network device learns that traffic load of the AMF 1 corresponding to 224.000.0.1 is 90% and traffic load of the AMF 2 corresponding to 225.000.0.1 is 10%. In this case, the second network device finally determines that a target AMF ID corresponding to 1 is 225.000.0.1.
  • the assistance information is used to select the target AMF based on a quantity of users accessing an AMF.
  • the second network device may determine, by searching the configuration parameter shown in Table 9, that AMF IDs corresponding to 01 include 001 and 002, and the second network device learns that a quantity of users accessing the AMF 1 corresponding to 001 is 1000 and a quantity of users accessing the AMF 2 corresponding to 002 is 10. In this case, the second network device finally determines that a target AMF ID corresponding to 01 is 002.
  • the second network device may further send a configuration result to the first network device, where the configuration result is used to indicate a completion status of configuring the configuration parameter by the second network device.
  • This embodiment of the present invention is implemented, so that the first network device sends the correspondence between the access and mobility management function identifier and the network slice instance identifier and/or the network slice subnet instance identifier.
  • the second network device may determine, based on the network slice instance identifier and/or the network slice subnet instance identifier carried in the selection request and the correspondence, the access and mobility management function corresponding to the network slice instance identifier and/or network slice subnet instance identifier. Therefore, the access and mobility management function corresponding to the network slice instance and/or the network slice subnet instance can be efficiently selected. If there are a plurality of access and mobility management functions corresponding to the network slice instance and/or the network slice subnet instance, the second network device may further determine one of the plurality of access and mobility management functions with reference to the assistance information sent by the first network device.
  • the present invention further provides a related device configured to implement the foregoing method.
  • FIG. 3 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • a first network device 30 includes a processor 301 and a transceiver 303.
  • the first network device 30 may further include a memory 302.
  • the processor 301, the memory 302, and the transceiver 303 may be connected through a bus or in another manner.
  • an example in which the processor 301, the memory 302, and the transceiver 303 may be connected through a bus 304 is used for description.
  • the first network device 30 may further include a module not shown in FIG. 3 .
  • the processor 301 may be a general-purpose processor such as a central processing unit (Central Processing Unit, CPU), or may be a digital signal processor (Digital Signal Processing, DSP), 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.
  • the processor 301 may process data that is received by using the transceiver 303.
  • the processor 301 may further process data that is to be sent to the transceiver 303.
  • the memory 302 is configured to store a program instruction and/or data, and transmit the program instruction to the CPU.
  • the memory 302 may include a volatile memory (Volatile Memory), for example, a random access memory (Random Access Memory, RAM).
  • the memory 302 may also include a non-volatile memory (Non-volatile Memory), for example, a read-only memory (Read-Only Memory, ROM), a flash memory (Flash Memory), a hard disk drive (Hard Disk Drive, HDD), or a solid-state drive (Solid-State Drive, SSD).
  • the memory 302 may alternatively include a combination of the foregoing types of memories.
  • the memory 302 is connected to the processor 301 through the bus.
  • the transceiver 303 is configured to perform data communication between the first network device 30 and another device, for example, perform data communication with a second network device.
  • the processor 301 is configured to invoke the program instruction and data that are stored in the memory 302, to perform the following operations:
  • the configuration parameter further includes assistance information, and the assistance information is used to instruct the second network device to select the access and mobility management function identifier.
  • the assistance information includes one or any combination of a priority, location information, access technology information, traffic load, and a quantity of access users.
  • the priority is used to indicate a priority of the access and mobility management function identifier.
  • the location information includes one or any combination of a tracking area identity TAI, a routing area identity RAI, and an evolved-universal mobile telecommunications system terrestrial radio access network cell global identifier ECGI.
  • the access technology information is used to indicate an access technology used when user equipment accesses a network slice instance and/or a network slice subnet instance.
  • the processor 301 is further configured to obtain, by using the transceiver 303, a configuration result sent by the second network device, where the configuration result is used to indicate a completion status of configuring the configuration parameter by the second network device.
  • the access and mobility management function identifier includes a globally unique access and mobility management function identifier corresponding to an access and mobility management function or an internet protocol address of the access and mobility management function.
  • the first network device 30 is one or any combination of a network manager NM, a domain manager DM, an element manager EM, a network slice management function NSMF, a network slice subnet management function NSSMF, a communication service management function CSMF, a network functions virtualization orchestration NFVO function, and a virtualized network function manager VNFM.
  • the first network device 30 is the foregoing NSMAO, and the second network device is an NRF.
  • FIG. 4 is a schematic structural diagram of another network device according to an embodiment of the present invention.
  • a second network device 40 may include a processor 401 and a transceiver 403.
  • the second network device 40 may further include a memory 402.
  • the processor 401, the memory 402, and the transceiver 403 may be connected through a bus or in another manner.
  • an example in which the processor 401, the memory 402, and the transceiver 403 may be connected through a bus 404 is used for description.
  • the second network device 40 may further include a module not shown in FIG. 4 .
  • the processor 401 may be a general-purpose processor such as a CPU, or may be a DSP, an ASIC, or one or more integrated circuits configured to implement this embodiment of the present invention.
  • the processor 401 may process data that is received by using the transceiver 403.
  • the processor 401 may further process data that is to be sent to the transceiver 403.
  • the memory 402 is configured to store a program instruction and/or data, and transmit the program instruction to the CPU.
  • the memory 402 may include a volatile memory, for example, a RAM.
  • the memory 402 may also include a non-volatile memory, for example, a ROM, a flash memory, an HDD, or an SSD. Alternatively, the memory 402 may include a combination of the foregoing types of memories.
  • the memory 402 is connected to the processor 401 through the bus.
  • the transceiver 403 is configured to perform data communication between the second network device 40 and another device, for example, perform data communication with a first network device.
  • the processor 401 is configured to invoke the program instruction and data that are stored in the memory 402, to perform the following operations:
  • the configuration parameter further includes assistance information, and the assistance information is used to instruct the second network device 40 to select the access and mobility management function identifier.
  • the assistance information includes one or any combination of a priority, location information, access technology information, traffic load, and a quantity of access users.
  • the priority is used to indicate a priority of the access and mobility management function identifier.
  • the location information includes one or any combination of a tracking area identity TAI, a routing area identity RAI, and an evolved-universal mobile telecommunications system terrestrial radio access network cell global identifier ECGI.
  • the access technology information is used to indicate an access technology used when user equipment accesses a network slice instance and/or a network slice subnet instance.
  • the processor 401 is further configured to: send a configuration result to the first network device by using the transceiver 403, where the configuration result is used to indicate a completion status of configuring the configuration parameter by the second network device 40.
  • the access and mobility management function identifier includes a globally unique access and mobility management function identifier corresponding to an access and mobility management function or an internet protocol address of the access and mobility management function.
  • the first network device is one or any combination of a network manager NM, a domain manager DM, an element manager EM, a network slice management function NSMF, a network slice subnet management function NSSMF, a communication service management function CSMF, a network functions virtualization orchestration NFVO function, and a virtualized network function manager VNFM.
  • the first network device is the foregoing NSMAO
  • the second network device 40 is an NRF.
  • FIG. 5 is a schematic structural diagram of another network device according to an embodiment of the present invention.
  • a first network device 50 includes an obtaining unit 501 and a sending unit 502.
  • the obtaining unit 501 is configured to obtain a configuration parameter, where the configuration parameter includes a network slice instance identifier and an access and mobility management function identifier corresponding to the network slice instance identifier, and/or a network slice subnet instance identifier and an access and mobility management function identifier corresponding to the network slice subnet instance identifier; and the sending unit 502 is configured to send the configuration parameter to a second network device.
  • the first network device 50 is presented in a form of functional units.
  • the "unit" herein may be an ASIC, a processor executing one or more software or firmware programs and a memory, an integrated logic circuit, and/or another component that can provide the foregoing functions.
  • the first network device 50 may be in a form shown in FIG. 3 .
  • the obtaining unit 501 may be implemented by the processor 301 in FIG. 3 .
  • the sending unit 502 may be implemented by the transceiver 303 in FIG. 3 .
  • the configuration parameter further includes assistance information, and the assistance information is used to instruct the second network device to select the access and mobility management function identifier.
  • the assistance information includes one or any combination of a priority, location information, access technology information, traffic load, and a quantity of access users.
  • the priority is used to indicate a priority of the access and mobility management function identifier.
  • the location information includes one or any combination of a tracking area identity TAI, a routing area identity RAI, and an evolved-universal mobile telecommunications system terrestrial radio access network cell global identifier ECGI.
  • the access technology information is used to indicate an access technology used when user equipment accesses a network slice instance and/or a network slice subnet instance.
  • the obtaining unit 501 is further configured to: after the sending unit 502 sends the configuration parameter to the second network device, obtain a configuration result sent by the second network device, where the configuration result is used to indicate a completion status of configuring the configuration parameter by the second network device.
  • the access and mobility management function identifier includes a globally unique access and mobility management function identifier corresponding to an access and mobility management function or an internet protocol address of the access and mobility management function.
  • the first network device 50 is one or any combination of a network manager NM, a domain manager DM, an element manager EM, a network slice management function NSMF, a network slice subnet management function NSSMF, a communication service management function CSMF, a network functions virtualization orchestration NFVO function, and a virtualized network function manager VNFM.
  • the first network device 50 may be the foregoing NSMAO, and the second network device may be an NRF.
  • FIG. 6 is a schematic structural diagram of another network device according to an embodiment of the present invention.
  • a second network device 60 includes an obtaining unit 601 and a configuration unit 602.
  • the obtaining unit 601 is configured to obtain a configuration parameter sent by a first network device, where the configuration parameter includes a network slice instance identifier and an access and mobility management function identifier corresponding to the network slice instance identifier, and/or a network slice subnet instance identifier and an access and mobility management function identifier corresponding to the network slice subnet instance identifier; and the configuration unit 602 is configured to configure the configuration parameter.
  • the second network device 60 is presented in a form of functional units.
  • the "unit” herein may be an ASIC, a processor executing one or more software or firmware programs and a memory, an integrated logic circuit, and/or another component that can provide the foregoing functions.
  • the second network device 60 may be in a form shown in FIG. 4 .
  • the obtaining unit 601 may be implemented by the transceiver 403 in FIG. 4 .
  • the configuration unit 602 may be implemented by the processor 401 in FIG. 4 .
  • the configuration parameter further includes assistance information, and the assistance information is used to instruct the second network device 60 to select the access and mobility management function identifier.
  • the assistance information includes one or any combination of a priority, location information, access technology information, traffic load, and a quantity of access users.
  • the priority is used to indicate a priority of the access and mobility management function identifier.
  • the location information includes one or any combination of a tracking area identity TAI, a routing area identity RAI, and an evolved-universal mobile telecommunications system terrestrial radio access network cell global identifier ECGI.
  • the access technology information is used to indicate an access technology used when user equipment accesses a network slice instance and/or a network slice subnet instance.
  • the second network device 60 further includes a sending unit.
  • the sending unit is configured to: after the configuration unit 602 configures the configuration parameter, send a configuration result to the first network device, where the configuration result is used to indicate a completion status of configuring the configuration parameter by the second network device.
  • the access and mobility management function identifier includes a globally unique access and mobility management function identifier corresponding to an access and mobility management function or an internet protocol address of the access and mobility management function.
  • the first network device is one or any combination of a network manager NM, a domain manager DM, an element manager EM, a network slice management function NSMF, a network slice subnet management function NSSMF, a communication service management function CSMF, a network functions virtualization orchestration NFVO function, and a virtualized network function manager VNFM.
  • the first network device is the foregoing NSMAO
  • the second network device 60 is an NRF.
  • FIG. 7 is a schematic structural diagram of an apparatus according to an embodiment of the present invention.
  • an apparatus 70 may include a processor 701 and one or more interfaces 702 coupled to the processor 701.
  • the processor 701 may be configured to read and execute a computer-readable instruction.
  • the processor 701 may mainly include a controller, an arithmetic unit, and a register.
  • the controller is mainly responsible for decoding an instruction, and sending a control signal for an operation corresponding to the instruction.
  • the arithmetic unit is mainly responsible for performing a fixed-point or floating-point arithmetic operation, a shift operation, a logical operation, and the like, and may also perform an address operation and an address conversion.
  • the register is mainly responsible for saving a register operand, an intermediate operation result, and the like that are temporarily stored during instruction execution.
  • a hardware architecture of the processor 701 may be an application-specific integrated circuit (Application Specific Integrated Circuits, ASIC) architecture, or the like.
  • the processor 701 may be single-core or multi-core.
  • the interface 702 may be configured to input to-be-processed data to the processor 701, and may output a processing result of the processor 701.
  • the processor 701 may be configured to invoke, from a memory, a program for implementing, on a first network device side, the network management method provided in one or more embodiments of this application, and execute an instruction included in the program.
  • the interface 702 may be configured to output an execution result of the processor 701.
  • functions respectively corresponding to the processor 701 and the interface 702 may be implemented by using a hardware design, may be implemented by using a software design, or may be implemented in a combination of software and hardware. This is not limited herein.
  • FIG. 8 is a schematic structural diagram of another apparatus according to an embodiment of the present invention.
  • an apparatus 80 may include a processor 801 and one or more interfaces 802 coupled to the processor 801.
  • the processor 801 may be configured to read and execute a computer-readable instruction.
  • the processor 801 may mainly include a controller, an arithmetic unit, and a register.
  • the controller is mainly responsible for decoding an instruction, and sending a control signal for an operation corresponding to the instruction.
  • the arithmetic unit is mainly responsible for performing a fixed-point or floating-point arithmetic operation, a shift operation, a logical operation, and the like, and may also perform an address operation and an address conversion.
  • the register is mainly responsible for saving a register operand, an intermediate operation result, and the like that are temporarily stored during instruction execution.
  • a hardware architecture of the processor 801 may be an application-specific integrated circuit (Application Specific Integrated Circuits, ASIC) architecture, or the like.
  • the processor 801 may be single-core or multi-core.
  • the interface 802 may be configured to input to-be-processed data to the processor 801, and may output a processing result of the processor 801.
  • the processor 801 may be configured to invoke, from a memory, a program for implementing, on a second network device side, the network management method provided in one or more embodiments of this application, and execute an instruction included in the program.
  • the interface 802 may be configured to output an execution result of the processor 801.
  • functions respectively corresponding to the processor 801 and the interface 802 may be implemented by using a hardware design, may be implemented by using a software design, or may be implemented in a combination of software and hardware. This is not limited herein.
  • the software program instruction may include a corresponding software module.
  • the software module may be stored in a RAM, a flash memory, a ROM, an erasable programmable read-only memory (Erasable Programmable ROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), a register, a hard disk, a mobile hard disk, a compact disc read-only memory (CD-ROM), or any other form of storage medium well-known in the art.
  • a storage medium is coupled to a processor, so that the processor can read information from the storage medium and write information into the storage medium.
  • the storage medium may be a component of the processor.
  • the processor and the storage medium may be located in an ASIC.
  • the ASIC may be located in a transceiver or a relay device.
  • the processor and the storage medium may exist as discrete components in a first network device or a second network device.
  • the computer-readable medium includes a computer storage medium and a communications medium, where the communications medium includes any medium that enables a computer program to be transmitted from one place to another.
  • the storage medium may be any available medium accessible to a general-purpose or special-purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Small-Scale Networks (AREA)

Claims (8)

  1. Procédé de gestion de réseau réalisé par un premier dispositif de réseau, le procédé comprenant les étapes consistant à :
    ∘ obtenir (S201) un paramètre de configuration, le paramètre de configuration comprenant :
    ▪ des informations d'assistance, les informations d'assistance étant utilisées pour donner l'instruction à un second dispositif de réseau de sélectionner un identifiant de fonction de gestion d'accès et de mobilité (ID AMF) cible ; et
    ▪ une première correspondance entre de multiples identifiants d'instance de tranche de réseau (ID NSI) de multiples NSI et de multiples ID AMF de multiples AMF ou une seconde correspondance entre de multiples identifiants d'instance de sous-réseau de tranche de réseau (ID NSSI) et les multiples ID AMF, dans lequel :
    • selon une première variante,
    ▪ dans la première correspondance, chaque ID NSI parmi les multiples ID NSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID NSI parmi les multiples ID NSI et pour chaque ID AMF parmi les au moins deux ID AMF, une priorité de l'ID AMF parmi de multiples priorités,
    pour chaque ID NSI parmi les multiples ID NSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à une priorité différente parmi les multiples priorités, ou
    ▪ dans la seconde correspondance, chaque ID NSSI parmi les multiples ID NSSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID NSSI parmi les multiples ID NSSI et pour chaque ID AMF parmi les au moins deux ID AMF, une priorité de l'ID AMF parmi de multiples priorités,
    pour chaque ID NSSI parmi les multiples ID NSSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à une priorité différente parmi les multiples priorités ;
    • selon une deuxième variante,
    ▪ dans la première correspondance, chaque ID NSI parmi les multiples ID NSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID AMF parmi les multiples ID AMF, une charge de trafic d'une AMF correspondant à l'ID AMF parmi de multiples charges de trafic,
    pour chaque ID NSI parmi les multiples ID NSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à une charge de trafic différente d'une AMF avec l'ID AMF parmi les multiples charges de trafic, ou
    ▪ dans la seconde correspondance, chaque ID NSSI parmi les multiples ID NSSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID AMF parmi les multiples ID AMF, une charge de trafic d'une AMF correspondant à l'ID AMF parmi de multiples charges de trafic,
    pour chaque ID NSSI parmi les multiples ID NSSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à une charge de trafic différente d'une AMF avec l'ID AMF parmi les multiples charges de trafic ;
    • selon une troisième variante,
    ▪ dans la première correspondance, chaque ID NSI parmi les multiples ID NSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID AMF parmi les multiples ID AMF, un nombre d'utilisateurs accédant à une AMF correspondant à l'ID AMF parmi de multiples nombres d'utilisateurs,
    pour chaque ID NSI parmi les multiples ID NSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à un nombre différent d'utilisateurs accédant à une AMF avec l'ID AMF parmi les multiples nombres d'utilisateurs, ou
    ▪ dans la seconde correspondance, chaque ID NSSI parmi les multiples ID NSSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID AMF parmi les multiples ID AMF, un nombre d'utilisateurs accédant à une AMF correspondant à l'ID AMF parmi de multiples nombres d'utilisateurs,
    pour chaque ID NSSI parmi les multiples ID NSSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à un nombre différent d'utilisateurs accédant à une AMF avec l'ID AMF parmi les multiples nombres d'utilisateurs ;
    • selon une quatrième variante,
    ▪ dans la première correspondance, chaque ID NSI parmi les multiples ID NSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID AMF parmi les multiples ID AMF, des informations de technologie d'accès d'une AMF correspondant à l'ID AMF,
    pour chaque ID NSI parmi les multiples ID NSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à des informations de technologie d'accès différentes d'une AMF avec l'ID AMF, les informations de technologie d'accès étant utilisées pour indiquer une technologie d'accès utilisée lorsqu'un équipement d'utilisateur accède à une instance de tranche de réseau avec un ID NSI, parmi les multiples ID NSI, auquel correspond la technologie d'accès, ou
    ▪ dans la seconde correspondance, chaque ID NSSI parmi les multiples ID NSSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID AMF parmi les multiples ID AMF, des informations de technologie d'accès d'une AMF correspondant à l'ID AMF,
    pour chaque ID NSSI parmi les multiples ID NSSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à des informations de technologie d'accès différentes d'une AMF avec l'ID AMF, les informations de technologie d'accès étant utilisées pour indiquer une technologie d'accès utilisée lorsqu'un équipement d'utilisateur accède à une sous-instance de tranche de réseau avec un ID NSSI, parmi les multiples ID NSSI, auquel correspond la technologie d'accès ;
    • selon une cinquième variante,
    ▪ dans la première correspondance, chaque ID NSI parmi les multiples ID NSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID AMF parmi les multiples ID AMF, une identité de zone de routage (RAI) parmi de multiples RAI ou un identifiant global de cellule de réseau d'accès radio terrestre de système universel de télécommunication mobile évolué (ECGI) parmi de multiples ECGI,
    pour chaque ID NSI parmi les multiples ID NSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à une RAI différente parmi les multiples RAI ou à un ECGI différent parmi les multiples ECGI, ou
    ▪ dans la seconde correspondance, chaque ID NSSI parmi les multiples ID NSSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID AMF parmi les multiples ID AMF, une identité de zone de routage (RAI) parmi de multiples RAI ou un identifiant global de cellule de réseau d'accès radio terrestre de système universel de télécommunication mobile évolué (ECGI) parmi de multiples ECGI,
    pour chaque ID NSSI parmi les multiples ID NSSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à une RAI différente parmi les multiples RAI ou à un ECGI différent parmi les multiples ECGI ;
    ∘ envoyer (S202) le paramètre de configuration au second dispositif de réseau.
  2. Procédé selon la revendication 1, dans lequel chaque ID AMF parmi les multiples ID AMF comprend un identifiant de fonction de gestion d'accès et de mobilité globalement unique correspondant à une fonction de gestion d'accès et de mobilité ou une adresse sur protocole Internet de la fonction de gestion d'accès et de mobilité.
  3. Procédé selon l'une quelconque des revendications 1 et 2, dans lequel le premier dispositif de réseau est un élément ou une combinaison quelconque d'éléments parmi un gestionnaire de réseau (NM), un gestionnaire de domaine (DM), un gestionnaire d'élément (EM), une fonction de gestion de tranche de réseau (NSMF), une fonction de gestion de sous-réseau de tranche de réseau (NSSMF), une fonction de gestion de service de communication (CSMF), une fonction d'orchestration de virtualisation de fonctions de réseau (NFVO) et un gestionnaire de fonction de réseau virtualisée (VNFM).
  4. Procédé de gestion de réseau réalisé par un second de réseau, le procédé comprenant les étapes consistant à :
    ∘ recevoir (S202) un paramètre de configuration en provenance d'un premier dispositif de réseau, le paramètre de configuration comprenant :
    ▪ des informations d'assistance, les informations d'assistance étant utilisées pour donner l'instruction au second dispositif de réseau de sélectionner un identifiant de fonction de gestion d'accès et de mobilité (ID AMF) cible ; et
    ▪ une première correspondance entre de multiples identifiants d'instance de tranche de réseau (ID NSI) de multiples NSI et de multiples ID AMF de multiples AMF ou une seconde correspondance entre de multiples identifiants d'instance de sous-réseau de tranche de réseau (ID NSSI) et les multiples ID AMF, dans lequel :
    • selon une première variante,
    ▪ dans la première correspondance, chaque ID NSI parmi les multiples ID NSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID NSI parmi les multiples ID NSI et pour chaque ID AMF parmi les au moins deux ID AMF, une priorité de l'ID AMF parmi de multiples priorités,
    pour chaque ID NSI parmi les multiples ID NSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à une priorité différente parmi les multiples priorités, ou
    ▪ dans la seconde correspondance, chaque ID NSSI parmi les multiples ID NSSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID NSSI parmi les multiples ID NSSI et pour chaque ID AMF parmi les au moins deux ID AMF, une priorité de l'ID AMF parmi de multiples priorités,
    pour chaque ID NSSI parmi les multiples ID NSSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à une priorité différente parmi les multiples priorités ;
    • selon une deuxième variante,
    ▪ dans la première correspondance, chaque ID NSI parmi les multiples ID NSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID AMF parmi les multiples ID AMF, une charge de trafic d'une AMF correspondant à l'ID AMF parmi de multiples charges de trafic,
    pour chaque ID NSI parmi les multiples ID NSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à une charge de trafic différente d'une AMF avec l'ID AMF parmi les multiples charges de trafic, ou
    ▪ dans la seconde correspondance, chaque ID NSSI parmi les multiples ID NSSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID AMF parmi les multiples ID AMF, une charge de trafic d'une AMF correspondant à l'ID AMF parmi de multiples charges de trafic,
    pour chaque ID NSSI parmi les multiples ID NSSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à une charge de trafic différente d'une AMF avec l'ID AMF parmi les multiples charges de trafic ;
    • selon une troisième variante,
    ▪ dans la première correspondance, chaque ID NSI parmi les multiples ID NSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID AMF parmi les multiples ID AMF, un nombre d'utilisateurs accédant à une AMF correspondant à l'ID AMF parmi de multiples nombres d'utilisateurs,
    pour chaque ID NSI parmi les multiples ID NSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à un nombre différent d'utilisateurs accédant à une AMF avec l'ID AMF parmi les multiples nombres d'utilisateurs, ou
    ▪ dans la seconde correspondance, chaque ID NSSI parmi les multiples ID NSSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID AMF parmi les multiples ID AMF, un nombre d'utilisateurs accédant à une AMF correspondant à l'ID AMF parmi de multiples nombres d'utilisateurs,
    pour chaque ID NSSI parmi les multiples ID NSSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à un nombre différent d'utilisateurs accédant à une AMF avec l'ID AMF parmi les multiples nombres d'utilisateurs ;
    • selon une quatrième variante,
    ▪ dans la première correspondance, chaque ID NSI parmi les multiples ID NSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID AMF parmi les multiples ID AMF, des informations de technologie d'accès d'une AMF correspondant à l'ID AMF,
    pour chaque ID NSI parmi les multiples ID NSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à des informations de technologie d'accès différentes d'une AMF avec l'ID AMF, les informations de technologie d'accès étant utilisées pour indiquer une technologie d'accès utilisée lorsqu'un équipement d'utilisateur accède à une instance de tranche de réseau avec un ID NSI, parmi les multiples ID NSI, auquel correspond la technologie d'accès, ou
    ▪ dans la seconde correspondance, chaque ID NSSI parmi les multiples ID NSSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID AMF parmi les multiples ID AMF, des informations de technologie d'accès d'une AMF correspondant à l'ID AMF,
    pour chaque ID NSSI parmi les multiples ID NSSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à des informations de technologie d'accès différentes d'une AMF avec l'ID AMF, les informations de technologie d'accès étant utilisées pour indiquer une technologie d'accès utilisée lorsqu'un équipement d'utilisateur accède à une sous-instance de tranche de réseau avec un ID NSSI, parmi les multiples ID NSSI, auquel correspond la technologie d'accès ;
    • selon une cinquième variante,
    ▪ dans la première correspondance, chaque ID NSI parmi les multiples ID NSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID AMF parmi les multiples ID AMF, une identité de zone de routage (RAI) parmi de multiples RAI ou un identifiant global de cellule de réseau d'accès radio terrestre de système universel de télécommunication mobile évolué (ECGI) parmi de multiples ECGI,
    pour chaque ID NSI parmi les multiples ID NSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à une RAI différente parmi les multiples RAI ou à un ECGI différent parmi les multiples ECGI, ou
    ▪ dans la seconde correspondance, chaque ID NSSI parmi les multiples ID NSSI correspond à au moins deux ID AMF parmi les multiples ID AMF,
    les informations d'assistance contenant, pour chaque ID AMF parmi les multiples ID AMF, une identité de zone de routage (RAI) parmi de multiples RAI ou un identifiant global de cellule de réseau d'accès radio terrestre de système universel de télécommunication mobile évolué (ECGI) parmi de multiples ECGI,
    pour chaque ID NSSI parmi les multiples ID NSSI, chaque ID AMF parmi les au moins deux ID AMF correspondant à une RAI différente parmi les multiples RAI ou à un ECGI différent parmi les multiples ECGI ;
    ∘ recevoir une demande de sélection, la demande de sélection contenant un certain ID NSI ou un certain ID NSSI ;
    ∘ déterminer (S203) l'ID AMF cible, la détermination de l'ID AMF cible comprenant les étapes suivantes consistant à :
    • selon la première variante :
    ∘ déterminer, sur la base de la première correspondance et sur la base du certain ID NSI reçu ou bien sur la base de la seconde correspondance et sur la base du certain ID NSSI reçu, les ID AMF correspondant au certain ID NSI ou au certain ID NSSI ;
    ∘ déterminer, parmi les ID AMF déterminés et sur la base des informations d'assistance, un ID AMF dont l'AMF a une priorité maximale en tant qu'ID AMF cible ;
    • selon la deuxième variante :
    ∘ déterminer, sur la base de la première correspondance et sur la base du certain ID NSI reçu ou bien sur la base de la seconde correspondance et sur la base du certain ID NSSI reçu, les ID AMF correspondant au certain ID NSI ou au certain ID NSSI ;
    ∘ déterminer, parmi les ID AMF déterminés et sur la base des informations d'assistance, un ID AMF dont l'AMF a une charge de trafic minimale en tant qu'ID AMF cible ;
    • selon la troisième variante :
    ∘ déterminer, sur la base de la première correspondance et sur la base du certain ID NSI reçu ou bien sur la base de la seconde correspondance et sur la base du certain ID NSSI reçu, les ID AMF correspondant au certain ID NSI ou au certain ID NSSI ;
    ∘ déterminer, parmi les ID AMF déterminés et sur la base des informations d'assistance, un ID AMF dont l'AMF a un nombre minimal d'utilisateurs accédant à l'AMF ;
    • selon la quatrième variante :
    ∘ obtenir une technologie d'accès d'un certain équipement d'utilisateur ;
    ∘ déterminer, sur la base de la première correspondance et sur la base du certain ID NSI reçu ou bien sur la base de la seconde correspondance et sur la base du certain ID NSSI reçu, les ID AMF correspondant au certain ID NSI ou au certain ID NSSI ;
    ∘ déterminer, parmi les ID AMF déterminés et sur la base des informations d'assistance, un ID AMF dont l'AMF a une même technologie d'accès que la technologie d'accès du certain équipement d'utilisateur ;
    • selon la cinquième variante :
    ∘ obtenir une RAI ou un ECGI d'un certain équipement d'utilisateur ;
    ∘ déterminer, sur la base de la première correspondance et sur la base du certain ID NSI reçu ou bien sur la base de la seconde correspondance et sur la base du certain ID NSSI reçu, les ID AMF correspondant au certain ID NSI ou au certain ID NSSI ;
    ∘ déterminer, parmi les ID AMF déterminés et sur la base des informations d'assistance, un ID AMF dont l'AMF a une même RAI ou un même ECGI que la RAI ou l'ECGI du certain équipement d'utilisateur.
  5. Premier dispositif de réseau (50) configuré pour réaliser l'un quelconque des procédés selon les revendications 1 à 3.
  6. Second dispositif de réseau (60) configuré pour réaliser le procédé selon la revendication 4.
  7. Produit-programme informatique comprenant une instruction, le produit-programme informatique, lorsqu'il est exécuté sur un ordinateur d'un premier dispositif de réseau, permettant à l'ordinateur de réaliser le procédé selon l'une quelconque des revendications 1 à 3.
  8. Produit-programme informatique comprenant une instruction, le produit-programme informatique, lorsqu'il est exécuté sur un ordinateur d'un second dispositif de réseau, permettant à l'ordinateur de réaliser le procédé selon la revendication 4.
EP18851568.8A 2017-08-28 2018-08-21 Procédé de gestion de réseau, et dispositif associé Active EP3664372B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710753317.6A CN109428749B (zh) 2017-08-28 2017-08-28 网络管理方法及相关设备
PCT/CN2018/101470 WO2019042186A1 (fr) 2017-08-28 2018-08-21 Procédé de gestion de réseau, et dispositif associé

Publications (3)

Publication Number Publication Date
EP3664372A1 EP3664372A1 (fr) 2020-06-10
EP3664372A4 EP3664372A4 (fr) 2020-07-15
EP3664372B1 true EP3664372B1 (fr) 2023-06-07

Family

ID=65502680

Family Applications (1)

Application Number Title Priority Date Filing Date
EP18851568.8A Active EP3664372B1 (fr) 2017-08-28 2018-08-21 Procédé de gestion de réseau, et dispositif associé

Country Status (4)

Country Link
US (1) US11258667B2 (fr)
EP (1) EP3664372B1 (fr)
CN (1) CN109428749B (fr)
WO (1) WO2019042186A1 (fr)

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018094667A1 (fr) * 2016-11-24 2018-05-31 华为技术有限公司 Procédé de gestion, unité de gestion, et système
CN109600400A (zh) * 2017-09-29 2019-04-09 索尼公司 无线通信系统中的电子设备、方法和无线通信系统
US10993177B2 (en) * 2018-12-13 2021-04-27 Verizon Patent And Licensing Inc. Network slice instance creation
CN114375069B (zh) * 2018-12-26 2024-04-12 腾讯科技（深圳）有限公司 一种通信方法和网络设备
CN110086652B (zh) * 2019-03-25 2023-04-18 北京天地互连信息技术有限公司 一种针对5g核心网中服务网元的管理系统及其方法
CN113785535B (zh) * 2019-05-06 2023-07-18 华为技术有限公司 数据处理实体
US11108636B2 (en) * 2019-10-23 2021-08-31 Cisco Technology, Inc. Integrity verification for managing network configurations
CN112737808A (zh) * 2019-10-28 2021-04-30 中兴通讯股份有限公司 一种网络切片实例配置方法和装置
CN111092752B (zh) * 2019-11-27 2021-03-16 中盈优创资讯科技有限公司 跨多个网络切片的故障定位方法及装置
WO2021142844A1 (fr) * 2020-01-19 2021-07-22 Oppo广东移动通信有限公司 Procédés d'accès à une cellule, dispositif électronique et support d'enregistrement
CN113329417B (zh) * 2020-02-28 2023-07-18 华为技术有限公司 一种网络配置方法及装置
CN114071657A (zh) * 2020-07-31 2022-02-18 中移(苏州)软件技术有限公司 网络切片的处理方法、装置和存储介质
WO2022151030A1 (fr) * 2021-01-13 2022-07-21 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil de configuration automatique d'une interface de plan de commande ng
CN113259499B (zh) * 2021-03-31 2022-10-28 航天东方红卫星有限公司 一种面向跨域网络的编址方法
CN113382432B (zh) * 2021-08-13 2021-11-23 新华三技术有限公司 一种5g网络服务提供方法、装置及设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106341832B (zh) * 2015-07-07 2020-11-06 中国移动通信集团公司 网络切片的管理及选择方法、系统、基站、路由交换设备
CN106550410B (zh) * 2015-09-17 2020-07-07 华为技术有限公司 一种通信控制方法和控制器、用户设备、相关装置
US10129108B2 (en) * 2015-11-13 2018-11-13 Huawei Technologies Co., Ltd. System and methods for network management and orchestration for network slicing
CN106713406B (zh) * 2015-11-18 2020-01-24 中国移动通信集团公司 接入切片网络的方法及系统
CN106982458B (zh) * 2017-03-09 2019-12-17 华为技术有限公司 一种网络切片的选择方法及装置

Also Published As

Publication number Publication date
WO2019042186A1 (fr) 2019-03-07
US20200195511A1 (en) 2020-06-18
CN109428749B (zh) 2022-04-22
US11258667B2 (en) 2022-02-22
EP3664372A4 (fr) 2020-07-15
EP3664372A1 (fr) 2020-06-10
CN109428749A (zh) 2019-03-05

Similar Documents

Publication Publication Date Title
EP3664372B1 (fr) Procédé de gestion de réseau, et dispositif associé
AU2021277736B2 (en) Pdu type setting method, ue policy setting method, and related entity
EP3512233B1 (fr) Procédé de gestion de tranche de réseau et unité de gestion
EP3291499B1 (fr) Procédé et appareil pour extension de capacité de service de réseau
KR102259679B1 (ko) 네트워크 슬라이스 관리 방법, 유닛 및 시스템
US10999740B2 (en) Network slice management method, management unit, and system
AU2015419073B2 (en) Life cycle management method and device for network service
US10924966B2 (en) Management method, management unit, and system
US20190261184A1 (en) Information Sending Method, Unit, and System
CN109548178B (zh) 一种通信方法和网络设备
US9465641B2 (en) Selecting cloud computing resource based on fault tolerance and network efficiency
CN107222324B (zh) 网络服务的业务配置方法和装置
CN114025021B (zh) 一种跨Kubernetes集群的通信方法、系统、介质和电子设备
US10848366B2 (en) Network function management method, management unit, and system
CN105095023B (zh) 一种云主机创建装置、方法和计算设备
CN109842895B (zh) 一种网络可靠性配置方法、信息传输方法和装置以及系统
JP6616957B2 (ja) 通信システム及び通信方法
JP6555676B2 (ja) リソース管理方法および装置
US20180004563A1 (en) Orchestrator apparatus, system, virtual machine creation method, and computer-readable recording medium
EP3531619A1 (fr) Procédé, dispositif et système de programmation de fonction
EP3468105A1 (fr) Procédé et appareil d'agencement de ressources de réseau
CN107534678B (zh) 建立vnfm与vim之间的连接的方法、装置及系统
JP6460743B2 (ja) 設定情報生成システム及び設定情報生成方法
US20230105269A1 (en) Virtualized network service deployment method and apparatus
WO2022141293A1 (fr) Procédé et appareil de mise à l'échelle souple

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

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: 20200305

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

AX Request for extension of the european patent

Extension state: BA ME

A4 Supplementary search report drawn up and despatched

Effective date: 20200615

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 24/04 20090101ALI20200608BHEP

Ipc: H04L 12/24 20060101AFI20200608BHEP

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
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: 20210208

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602018051537

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012240000

Ipc: H04L0041080600

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 24/04 20090101ALI20221114BHEP

Ipc: H04L 41/0895 20220101ALI20221114BHEP

Ipc: H04L 41/0806 20220101AFI20221114BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20230105

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

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

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 1578108

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230615

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602018051537

Country of ref document: DE

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230524

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20230607

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230907

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1578108

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230607

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230908

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20230703

Year of fee payment: 6

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231007

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231009

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231007

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602018051537

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230821

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230821

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230607

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20230831

26N No opposition filed

Effective date: 20240308

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A