WO2020253343A1 - 一种管理服务的发现方法及装置 - Google Patents

一种管理服务的发现方法及装置 Download PDF

Info

Publication number
WO2020253343A1
WO2020253343A1 PCT/CN2020/084982 CN2020084982W WO2020253343A1 WO 2020253343 A1 WO2020253343 A1 WO 2020253343A1 CN 2020084982 W CN2020084982 W CN 2020084982W WO 2020253343 A1 WO2020253343 A1 WO 2020253343A1
Authority
WO
WIPO (PCT)
Prior art keywords
management
domain name
information
management service
network element
Prior art date
Application number
PCT/CN2020/084982
Other languages
English (en)
French (fr)
Inventor
李卓明
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2020253343A1 publication Critical patent/WO2020253343A1/zh

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/02—Standardisation; Integration
    • H04L41/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]

Definitions

  • This application relates to the field of mobile communication technology, and in particular to a method and device for discovering management services.
  • the management service repository function (MSRF) network element is introduced in order to realize the discovery of management service instances.
  • All management functions register their own management service instance information with MSRF, including the interface access address of the management service instance and the network resources it manages.
  • the network resources managed by the management service instance use the Managed Object Instance (MOI) identification
  • MOI Managed Object Instance
  • MF Management Function
  • the MSRF queries the stored registration information of the management service instance according to the MOI, obtains the interface access address of the management service instance, and then sends the response message to the management function.
  • the management function can discover the network management service instance that manages the network resource identified by the MOI through MSRF, obtain the interface access address, and then call the management service (Management Service, MnS) to modify, delete, subscribe, and notify the network resource. Management actions.
  • MnS Management Service
  • the disadvantage of the above solution is that when a certain network resource needs to be created and deployed, if there are multiple management service instances that support the creation and deployment of network resources, because the management object MOI has not been created yet, it is impossible to know which management service using existing technology The instance can meet the management needs of creating and deploying target network resources.
  • This application provides a method and device for discovering management services, which are used to realize the creation of management object instances based on the desired management capability information of the management function.
  • the present application provides a method for discovering a management service.
  • the method includes: a first network element obtains access information of a management service instance from a server according to expected management capability information.
  • the management capability information matches, and the desired management capability information includes at least one of a management action, a type of management object, or a capability attribute;
  • the first network element is based on the access information of the management service instance and the desired management Capability information, calling a management service to a second network element, where the second network element includes the management service instance;
  • the first network element receives creation deployment information from the second network element, and the creation deployment information includes all
  • the type of the management object corresponds to a management object instance, and the management object instance is used to identify the network resource managed by the management service instance.
  • the server is a management service warehouse function network element; more specifically, the management service warehouse function network element may be a common application programming interface framework (Common Application Program Interface Framework-Core Function, CAPIF). ) In the core function (Core Function, CF), application programming interface opening function (API Exposing Function, AEF), application programming interface publishing function (API Publishing Function.
  • CAPIF Common Application Program Interface Framework-Core Function
  • the first network element obtains the access information of the management service instance from the server according to the desired management capability information, including: the first network element sends the management service warehouse function network element Sending a request message, the request message including the desired management capability information; the first network element receives the access information of the management service instance from the management service warehouse function network element.
  • the server is a domain name server; more specifically, the domain name server is the Internet’s Domain Name System (DNS), or the universal application programming interface framework CAPIF is responsible for publishing, storing and The function of supporting service API information discovery can be realized by DNS; the first network element obtains access information of the management service instance from the server according to the desired management capability information, including: the first network element sends a request to the domain name server Message, the request message includes a query domain name, the query domain name is constructed according to the desired management capability information; the first network element receives from the domain name server a name authority pointer NAPTR record corresponding to the query domain name The authoritative domain name; the first network element obtains the access information of the management service instance from the domain name server according to the authoritative domain name recorded by the NAPTR.
  • DNS Domain Name System
  • the first network element obtains the access information of the management service instance from the domain name server according to the authoritative domain name recorded by the NAPTR, including: the first authoritative domain name recorded by the NAPTR Is the authoritative domain name of the management service instance, the first network element obtains the access information of the management service instance corresponding to the authoritative domain name recorded by the NAPTR from the domain name server; or, the authoritative domain name recorded by the NAPTR
  • the first network element obtains the authoritative domain name of the service SRV record corresponding to the authoritative domain name recorded by the NAPTR from the domain name server, and obtains from the domain name server according to the authoritative domain name of the SRV record Obtain the access information of the management service instance.
  • the first network element is an open control management function network element, and the second network element is a management function network element; or, the first network element is a first management function network element
  • the second network element is a second management function network element, and the network resource managed by the second management function network element is a component of the network resource managed by the first management function network element.
  • the present application provides a management service discovery method, the method includes: a server receives desired management capability information, the desired management capability information includes at least one of a management action, a type of management object, or a capability attribute Item; The server obtains access information of a management service instance according to the desired management capability information, and the management service instance matches the desired management capability information; the server sends the access information of the management service instance. Based on this solution, it is realized that based on the request of the first network element (carrying the desired management capability information), the created management object instance is returned to the first network element, thereby realizing the operation of creating the management object instance.
  • the server is a management service warehouse functional network element;
  • the server receiving desired management capability information includes: the service warehouse functional network element receives a request message, the request message including the Expected management capability information; the server obtains access information of a management service instance according to the expected management capability information, and the management service instance matches the expected management capability information, including: the service warehouse function network element The corresponding relationship between the access information of at least one management service instance and the management capability information is configured on it, and the service warehouse function network element obtains the access information of the management service instance according to the expected management capability information and the corresponding relationship.
  • the service warehouse function network element receives the information of the management object instance, the information of the management object instance includes the management object instance and the relationship between the management object instance and other management object instances,
  • the management object instance is used to identify the network resource managed by the management service instance;
  • the service warehouse function network element updates the management capability information corresponding to the management service instance according to the information of the management object instance.
  • the server is a domain name server;
  • the server receiving the desired management capability information includes: the domain name server receives a request message, the request message queries the domain name, and the query domain name is based on the The desired management capability information is constructed; the server obtains access information of the management service instance according to the desired management capability information, including: the domain name server obtains the authoritative domain name of the NAPTR record corresponding to the query domain name; The domain name server obtains the access information of the management service instance corresponding to the authoritative domain name recorded by the NAPTR.
  • the domain name server acquiring the access information of the management service instance corresponding to the authoritative domain name recorded by the NAPTR includes: the authoritative domain name recorded by the NAPTR is the authority of the management service instance Domain name, the domain name server obtains the access information of the management service instance corresponding to the authoritative domain name of the management service instance; or, the authoritative domain name recorded by the NAPTR is the authoritative domain name of the management service, and the domain name server obtains the The authoritative domain name of the SRV record corresponding to the authoritative domain name of the management service, and the access information of the management service instance is obtained according to the authoritative domain name of the SRV record.
  • the domain name server receives the information of the management object instance, and the information of the management object instance includes the management object instance and the relationship between the management object instance and other management object instances.
  • the object instance is used to identify the network resource managed by the management service instance, the management object instance is the top node within the management capability of the management service instance; the server updates all resources according to the information of the management object instance The NAPTR record corresponding to the management service instance.
  • this application provides a management service discovery method.
  • the method includes: a first network element sends a request message to a domain name server, where the request message includes a query domain name, and the query domain name is constructed based on desired management capability information ,
  • the desired management capability information includes at least one of a management service, a management action, a type of a management object, or a management object instance, and the management object instance is used to identify a network resource managed by the management service instance;
  • a network element receives the authoritative domain name recorded by the name authority pointer NAPTR corresponding to the query domain name from the domain name server; the first network element obtains the management service instance from the server according to the authoritative domain name recorded by the NAPTR The access information; the first network element calls the management service to the second network element that provides the management service according to the access information of the management service instance and the desired management capability information.
  • the management object is a top node within the management capability of the management service instance.
  • the first network element is an open control management function network element, and the second network element is a management function network element; or, the first network element is a first management function network element
  • the second network element is a second management function network element, and the network resource managed by the second management function network element is a component of the network resource managed by the first management function network element.
  • the present application provides a management service discovery method.
  • the method includes: the first network element determines the information object class corresponding to the tenant according to the identifier of the tenant, where one information object class is used to identify a createable The type of network resource; the first network element obtains from the server the information of the creation management service corresponding to the information object class according to the information object class corresponding to the tenant, and the information of the creation management service includes At least one of the creation class management service name, the creation class management action, or the capability attribute; the first network element sends a first message to the tenant, the first message including the information object class corresponding to the tenant and all Describes the available creation management service information.
  • the tenant with information about the information object class corresponding to the tenant and the available creation management services, or to provide the information object class corresponding to the tenant, the management object instance corresponding to the tenant, and the management service that can be provided.
  • the information and the information of the creation management service that can be provided that is, the information that provides the management capability scope of the tenant.
  • the server is a domain name server; the first network element obtains from the server the available creation class management capability information corresponding to the information object class according to the information object class corresponding to the tenant , Including: the first network element sends a request message to the domain name server, the request message includes the information object class, the request message is used to request a NAPTR record; the first network element sends a request from the domain name server Receive the information of the available creation management service.
  • the first network element determines the management object instance corresponding to the tenant according to the identifier of the tenant, wherein one management object instance is used to identify a network resource that can be managed;
  • the network element obtains from the server information about the available management service corresponding to the management object instance according to the management object instance corresponding to the tenant, where the information about the management service includes at least one of a management service or a management action;
  • the first network element sends a second message to the tenant, where the second message includes the management object instance corresponding to the tenant and the information about the available management service.
  • the server is a domain name server; the first network element obtains from the server the management service information corresponding to the managed object instance corresponding to the management object instance corresponding to the tenant.
  • the information includes: the first network element sends a request message to the domain name server, the request message includes the information object class, and the request message is used to request to query NAPTR records;
  • the domain name server receives the information about the available management services.
  • this application provides a management service discovery device, which may be a first network element or a chip used for the first network element.
  • the device has the function of realizing each embodiment of the first aspect described above. This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the present application provides a management service discovery device.
  • the device may be a server or a chip for the server.
  • the device has the function of realizing each embodiment of the second aspect described above. This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • this application provides a management service discovery device.
  • the device may be a first network element or a chip for the first network element.
  • the device has the function of realizing each embodiment of the third aspect. This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the present application provides a management service discovery device.
  • the device may be a first network element or a chip for the first network element.
  • the device has the function of realizing each embodiment of the fourth aspect described above. This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the present application provides a management service discovery device, including: a processor and a memory; the memory is used to store computer execution instructions, and when the device is running, the processor executes the computer execution instructions stored in the memory, So that the device executes the methods described in the above aspects.
  • the present application provides a management service discovery device, including: including units or means for executing each step of the foregoing aspects.
  • the present application provides a management service discovery device, including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit and execute the methods described in the foregoing aspects.
  • the processor includes one or more.
  • the present application provides a management service discovery device, including a processor, configured to be connected to a memory, and configured to call a program stored in the memory to execute the methods described in the foregoing aspects.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • the present application also provides a computer-readable storage medium that stores instructions in the computer-readable storage medium, which when run on a computer, causes a processor to execute the methods described in the foregoing aspects.
  • the present application also provides a computer program product including instructions, which when run on a computer, cause the computer to execute the methods described in the foregoing aspects.
  • the present application also provides a chip system, including a processor, configured to execute the methods described in the foregoing aspects.
  • the present application also provides a communication system, including: a first network element for executing any of the methods described in the first aspect and a server for executing any of the methods described in the second aspect.
  • this application also provides a management service discovery method, including:
  • the first network element sends desired management capability information to the server, where the desired management capability information includes at least one of a management action, a type of management object, or a capability attribute;
  • the server receives the desired management capability information
  • the server obtains access information of a management service instance according to the desired management capability information, and the management service instance matches the desired management capability information;
  • the first network element calls a management service to a second network element according to the access information of the management service instance and the desired management capability information, and the second network element includes the management service instance;
  • the first network element receives creation and deployment information from the second network element, where the creation and deployment information includes a management object instance corresponding to the type of the management object, and the management object instance is used to identify the management service instance managed Network resources.
  • this application also provides a management service discovery system, including:
  • the first network element is configured to: obtain access information of a management service instance from a server according to expected management capability information, where the management service instance matches the expected management capability information, and the expected management capability information includes management actions , At least one of the type of the management object, or the capability attribute; according to the access information of the management service instance and the desired management capability information, call a management service to a second network element, where the second network element includes the Management service instance; receiving creation deployment information from the second network element, the creation deployment information including the management object instance corresponding to the type of the management object, and the management object instance is used to identify the network managed by the management service instance Resources;
  • the server is configured to receive the desired management capability information from the first network element; obtain the access information of the management service instance according to the desired management capability information; and send the management to the first network element Access information of the service instance.
  • Figure 1A is a schematic diagram of a 5G network architecture based on a service-oriented architecture
  • Figure 1B is a schematic diagram of a 5G network architecture based on a point-to-point interface
  • Figure 2 is a schematic diagram of a service-oriented management plane
  • Figure 3 shows the management open control architecture and application scenarios
  • Figure 4 is another schematic diagram of the management plane service architecture
  • FIG. 5 is a schematic flowchart of a management service discovery method provided by this application.
  • FIG. 6 is a schematic flowchart of another method for discovering management services provided by this application.
  • FIG. 7 is a schematic flowchart of another method for discovering management services provided by this application.
  • FIG. 8 is a schematic diagram of a network structure provided by this application.
  • FIG. 9 is a schematic flowchart of another method for discovering management services provided by this application.
  • FIG. 10 is a schematic flowchart of another method for discovering management services provided by this application.
  • Figure 11 is a schematic diagram of the top node MOI and the top node mark within the management scope of the management service instance;
  • FIG. 12 is a schematic flowchart of another method for discovering management services provided by this application.
  • FIG. 13 is a schematic flowchart of another method for discovering management services provided by this application.
  • FIG. 14 is a schematic flowchart of another method for discovering management services provided by this application.
  • FIG. 15 is a schematic diagram of a discovery device for a management service provided by this application.
  • FIG. 16 is a schematic diagram of yet another management service discovery device provided by this application.
  • FIG 17 is a schematic diagram of yet another management service discovery device provided by this application.
  • FIG. 1A it is a schematic diagram of the fifth-generation mobile communication (the 5th-generation, 5G) network architecture based on a service-oriented architecture.
  • the 5G network architecture shown in FIG. 1A may include three parts, namely a terminal equipment part, a data network (DN), and an operator network part.
  • DN data network
  • operator network part The functions of some of the network elements are briefly introduced below.
  • the operator network may include one or more of the following network elements: network exposure function (NEF) network elements, policy control function (PCF) network elements, unified data management (unified data management) , UDM) network element, network function repository function (NRF) network element, application function (AF) network element, authentication server function (authentication server function, AUSF) network element, access and mobility management Function (access and mobility management function, AMF) network element, session management function (session management function, SMF) network element, (radio) access network ((radio) access network, (R) AN), and user plane function (user plane function, UPF) network elements, etc.
  • NEF network exposure function
  • PCF policy control function
  • UDM network element
  • NRF network function repository function
  • AF application function
  • authentication server function authentication server function
  • AUSF access and mobility management Function
  • AMF session management function
  • SMF session management function
  • R radio access network
  • UPF user plane function
  • Terminal equipment also known as user equipment (UE) is a device with wireless transceiver function. It can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as ships). Etc.); It can also be deployed in the air (for example, on airplanes, balloons, and satellites).
  • the terminal device may be a mobile phone, a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, and an industrial control (industrial control) terminal.
  • VR virtual reality
  • AR augmented reality
  • industrial control industrial control
  • Wireless terminals in wireless terminals in self-driving (self-driving), wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety (transportation safety) , Wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the above-mentioned terminal equipment can establish a connection with the operator's network through an interface (such as N1, etc.) provided by the operator's network, and use services such as data and/or voice provided by the operator's network.
  • the terminal device can also access the DN through the operator's network, and use the operator's service deployed on the DN and/or the service provided by a third party.
  • the aforementioned third party may be a service party other than the operator's network and terminal equipment, and may provide other services such as data and/or voice for the terminal equipment.
  • the specific form of expression of the aforementioned third party can be determined according to actual application scenarios, and is not limited here.
  • RAN is a sub-network of an operator's network, and an implementation system between service nodes and terminal equipment in the operator's network.
  • the terminal device To access the operator's network, the terminal device first passes through the RAN, and then can be connected to the service node of the operator's network through the RAN.
  • the RAN device in this application is a device that provides wireless communication functions for terminal devices, and the RAN device is also called an access network device.
  • the RAN equipment in this application includes but is not limited to: the next generation base station (gnodeB, gNB), evolved node B (evolved node B, eNB), radio network controller (RNC), node B in 5G (node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand) unit, BBU), transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), mobile switching center, etc.
  • gnodeB next generation base station
  • gNB next generation base station
  • eNB evolved node B
  • RNC radio network controller
  • node B in 5G node B, NB
  • BSC base station controller
  • BTS base transceiver station
  • home base station for example, home evolved nodeB, or home node B, HNB
  • AMF network element is a control plane network element provided by the operator's network. It is responsible for the access control and mobility management of terminal equipment accessing the operator's network, such as mobile status management, allocation of temporary user identities, authentication and authorization of users, etc. Features.
  • the SMF network element is a control plane network element provided by the operator network, and is responsible for managing the protocol data unit (PDU) session of the terminal device.
  • the PDU session is a channel used to transmit PDUs, and terminal devices need to transmit PDUs to each other through the PDU session and the DN.
  • the PDU session is established, maintained, and deleted by the SMF network element.
  • SMF network elements include session management (such as session establishment, modification and release, including tunnel maintenance between UPF and AN), UPF network element selection and control, service and session continuity (Service and Session Continuity, SSC) mode selection, Session-related functions such as roaming.
  • the UPF network element is a gateway provided by an operator and a gateway for communication between the operator's network and the DN.
  • UPF network elements include user plane-related functions such as data packet routing and transmission, packet inspection, service usage reporting, quality of service (QoS) processing, lawful monitoring, upstream packet inspection, and downstream packet storage.
  • QoS quality of service
  • DN also called packet data network (PDN)
  • PDN packet data network
  • the operator’s network can be connected to multiple DNs, and multiple services can be deployed on the DN to provide terminal equipment. Services such as data and/or voice.
  • DN is the private network of a smart factory.
  • the sensors installed in the workshop of the smart factory can be terminal devices.
  • the control server of the sensor is deployed in the DN, and the control server can provide services for the sensors.
  • the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
  • a DN is an internal office network of a company.
  • the mobile phones or computers of employees of the company can be terminal devices, and the mobile phones or computers of employees can access information and data resources on the company's internal office network.
  • the UDM network element is a control plane network element provided by the operator. It is responsible for storing the subscriber permanent identifier (SUPI), credential, security context, and subscription of subscribers in the operator’s network. Data and other information.
  • the information stored in UDM network elements can be used for authentication and authorization of terminal equipment accessing the operator's network.
  • the contracted users of the above-mentioned operator's network may specifically be users who use the services provided by the operator's network, such as users who use China Telecom's mobile phone core card, or users who use China Mobile's mobile phone core card.
  • the permanent subscription identifier (Subscription Permanent Identifier, SUPI) of the aforementioned subscriber may be the number of the mobile phone core card, etc.
  • the credential and security context of the aforementioned subscriber may be a small file stored such as the encryption key of the mobile phone core card or information related to the encryption of the mobile phone core card for authentication and/or authorization.
  • the aforementioned security context may be data (cookie) or token (token) stored on the user's local terminal (for example, mobile phone).
  • the contract data of the aforementioned subscriber may be the supporting service of the mobile phone core card, such as the data package of the mobile phone core card or the use of the network.
  • permanent identifiers, credentials, security contexts, authentication data (cookies), and tokens are equivalent to information related to authentication and authorization.
  • no distinction or restriction is made for the convenience of description. If no special instructions are given, the embodiments of the present application will be described using a security context as an example, but the embodiments of the present application are also applicable to authentication and/or authorization information in other expression modes.
  • the AUSF network element is a control plane network element provided by the operator, and can usually be used for first-level authentication, that is, the authentication between the terminal device (subscribed user) and the operator's network. After the AUSF network element receives the authentication request initiated by the subscriber, it can authenticate and/or authorize the subscriber through the authentication information and/or authorization information stored in the UDM network element, or generate the authentication and/or authorization of the subscriber through the UDM network element. Or authorization information. The AUSF network element can feed back authentication information and/or authorization information to the subscriber.
  • NEF network elements are control plane network elements provided by operators. NEF network elements open the external interface of the operator's network to third parties in a safe manner. When the SMF network element needs to communicate with a third-party network element, the NEF network element can serve as a relay for the communication between the SMF network element and the third-party network element. When the NEF network element is used as a relay, it can be used as the translation of the identification information of the subscriber and the translation of the identification information of the third-party network element. For example, when NEF sends the SUPI of the subscriber from the operator network to the third party, it can translate the SUPI into its corresponding external identity (identity, ID). Conversely, when the NEF network element sends the external ID (third-party network element ID) to the operator's network, it can be translated into SUPI.
  • ID external identity
  • Application Function (AF) network elements mainly provide application layer services, and also support interaction with the 5G core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side.
  • the AF network element generally refers to a third-party server.
  • the PCF network element is a control plane function provided by the operator to provide a strategy to the network element.
  • the policies may include access control policies, mobility management policies, charging-related policies, QoS-related policies, and authorization-related policies.
  • NRF network element can be used to provide network element discovery function, based on the request of other network elements, provide network element information corresponding to the network element type, such as address information and/or identification information.
  • NRF also provides network element management services, such as network element registration, update, de-registration, and network element status subscription and push.
  • Nnef, Nausf, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers.
  • the meaning of these interface serial numbers can refer to the meaning defined in the 3GPP standard protocol, which is not limited here.
  • FIG. 1B it is a schematic diagram of a 5G network architecture based on a point-to-point interface.
  • FIG. 1A For the introduction of the functions of the network elements therein, reference may be made to the introduction of the functions of the corresponding network elements in FIG. 1A, which will not be repeated.
  • the main difference between Fig. 1B and Fig. 1A is that the interfaces between the various network elements in Fig. 1B are point-to-point interfaces rather than service-oriented interfaces.
  • the interface between the UE and the AMF network element is called the N1 interface
  • the interface between the AMF network element and the RAN device is called the N2 interface
  • the interface between the RAN device and the UPF network element It can be called N3 interface
  • the interface between SMF network element and UPF network element is called N4 interface
  • the interface between PCF network element and AF network element is called N5 interface
  • the interface between UPF network element and DN is called N6 Interface
  • the interface between SMF network element and PCF network element is called N7 interface
  • the interface between AMF network element and UDM network element is called N8 interface
  • the interface between different UPF network elements is called N9 interface
  • UDM network element The interface with SMF network element is called N10 interface
  • the interface between AMF network element and SMF network element is called N11 interface
  • the interface between AUSF network element and AMF network element is called N12 interface
  • AUSF network element and UDM The interface between network elements is called N13 interface
  • the foregoing network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform).
  • a platform for example, a cloud platform.
  • the foregoing network element or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in the embodiment of the present application.
  • the network management system of the 5G network adopts a service-oriented architecture.
  • 3rd generation partnership project 3rd generation partnership project, 3GPP
  • TS 28.533 standard specification as shown in Figure 2, it is a schematic diagram of the management plane service-oriented architecture.
  • the management function can be used as a service provider to provide external management services (MnS), or as a service consumer to call MnS provided by other MFs.
  • the MF here can be, for example, the AMF, SMF, PCF, UPF, AF, AUSF, etc. shown in Figure 1A or Figure 1B, or it can be the management function in future communications such as the 6th-generation (6G) mobile communications. This application is not limited.
  • the MF contains a management service instance (MnS Instance) of MnS, which has management service access information (including interfaces (such as application programming interface (Application Programming Interface, API) call interface), Interface access address, etc.).
  • management service access information including interfaces (such as application programming interface (Application Programming Interface, API) call interface), Interface access address, etc.).
  • the management function MF1 includes two management service instances.
  • the interface for providing management services is the small circle shown in the figure. Each interface has an interface access address and can use the Internet protocol (Internet protocol, IP) address (IPv4 or IPv6), port number, and protocol type are identified, and can also be identified by using a uniform resource identifier (URI) or a uniform resource locator (URL).
  • IP Internet protocol
  • IPv4 or IPv6 IPv4 or IPv6
  • MnS consists of the following three parts:
  • Management actions such as creation, modification, query, deletion, subscription, notification, etc.
  • Management objects objects for management actions, such as network functions, network slices, network slice subnets, etc.
  • the management object can be a type of management object, that is, a Managed Object Class (MOC), or it can be a specific instance of a management object class, that is, a Managed Object Instance (MOI).
  • the type definition of the management object is described by the Information Object Class (IOC), that is, the IOC is used to describe the MOC.
  • IOC Information Object Class
  • MOI is a concrete example of MOC.
  • MOC is an abstract class definition of network resources that can be managed, while MOI is a specific network resource that can be managed.
  • Management data such as alarm information or performance statistics information, etc. Only part of the management service involves management data, so management data is optional.
  • the management service MnS can be composed of management actions plus management objects.
  • the management action is: allocate (allocate) or de-allocate (deAllocate), and the management object is: Network Function (NF), then the management action plus the management object constitutes the network function provisioning and deployment management service (NFProvisioning_ms); another example ,
  • the management action is: allocate (allocate) or de-allocate (deAllocate), and the management object is: NetworkSlice Subnet, then the management action plus the management object form the network slice subnet instance provisioning deployment management service (NSSIProvisioning_ms) .
  • the management service MnS can also be composed of management actions plus management objects and management data.
  • the management action is: performance reporting (performanceReporting)
  • the management object is: 5G core network (5GC, 5G Core) network functions
  • the management data is: 5GC performance information
  • the management action plus the management object plus the managed data It constitutes the network function performance report management service (NFPerformanceReporting_ms).
  • Network slicing is a logical network customized according to different service requirements on a physical or virtual network infrastructure.
  • a network slice can be a complete end-to-end network including terminal devices, access networks, transmission networks, core networks, and application servers, and can provide complete communication services.
  • Network slicing is often provided to tenants in the form of Network Slice as a Service (NSaaS), that is, the operator creates a network slice instance (NSI) to third parties (which can be enterprises, Internet service providers, or Another operator, etc.) provide services.
  • NSaaS Network Slice as a Service
  • NTI network slice instance
  • a network slicing instance is a logical network that can be actually operated and created by an operator to provide network slicing services for specific tenants.
  • a network slice instance can be composed of one or more subnet slice instances (Network Slice Subnet Instance, NSSI), for example, it can be composed of a wireless access subnet slice instance and a core network subnet slice instance.
  • NSSI Network Slice Subnet Instance
  • KPI key performance indicator
  • the tenant of a network slice instance is another operator, in addition to allowing the tenant to obtain certain key indicators of the network slice instance, the tenant is often allowed to obtain alarm information of the network slice instance, and even allows the tenant to perform certain operations, such as allowing Modify the configuration of some network functions in the network slicing instance to enable it to connect with the tenant's own network equipment to facilitate the provision of network services on a larger scale.
  • 3GPP TS 28.533 defines an open control management function (Exposure Government Management Function, EGMF).
  • EGMF Exposure Government Management Function
  • open control architecture and application scenarios for management It can be seen from the figure that the management capability of the network is realized by calling the management service MnS. EGMF, as a management open control function, opens part of the network management action authority to a third party (such as a vertical industry) or another operator, and checks whether the management action requested by the tenant is within the allowed range. If the network management action is allowed, it will call the management service as an agent and provide the result of the management action to the tenant.
  • vertical industry tenants call the management services provided by MnF1 through EGMF1
  • MnF2 of another operator tenant calls the management services provided by MnF1 through EGMF2.
  • the management service warehouse function (MSRF) network element shown in FIG. 4 is introduced in order to realize the discovery of management service instances. All management functions register their own management service instance information with MSRF, including the interface access address of the management service instance and the network resources it manages. Because the network resources managed by the management service instance use the MOI identifier, when the MF3 in Figure 4 needs to perform management actions on a certain network resource (for example, a certain NF), it sends a query request to the MSRF, which carries the MOI of the NF . The MSRF queries the stored registration information of the management service instance according to the MOI, obtains the interface access address of the management service instance, and then sends the response message to the MF3.
  • a certain network resource for example, a certain NF
  • the consumer of the management service can discover the network management service instance that manages the network resource identified by the MOI through MSRF, obtain the interface access address, and then call the management service to perform management actions such as modification, deletion, subscription, and notification to the network resource.
  • the Domain Name Server (DNS) system is a widespread network infrastructure.
  • the URI or URL contains the domain name, and the DNS system is used to map the domain name and IP address to each other, but the prior art does not provide how to use DNS
  • the system conducts discovery of management service instances.
  • the prior art also fails to provide examples of how third-party industries or other operators outside the network can indirectly discover management services that can provide the desired management capabilities through the management of open control functions.
  • the management service instance and its management capability information are registered to MSRF or configured to DNS in the form of NAPRT record.
  • the management service consumer queries DNS or MSRF according to the management capability information to provide instances of creation management services and provide non-creation management services Instance.
  • the management capability information of the created class management service includes at least one of the supported management service name, management action, management object type (MOC or IOC), and capability attribute.
  • the management capability information of the non-created management service includes at least one of the supported management service name, management action, type of management object (MOC or IOC), and MOI of the management object.
  • the management service instance and its management capability information configured to DNS in the form of NAPRT records if the newly created management object instance is the top node within the management capability of the management service instance, set the top node flag for this MOI
  • the management capability information configuration record for adding or refreshing the non-creation management service in the DNS is used, wherein the MOI of the management object included in the management capability information in the configuration record is the management object instance that sets the top-level node flag.
  • the management open control function uses management object information or management object instances that can be managed by third-party industries or other operators to identify the management actions that can be provided by querying all management service instances to DNS or MSRF, and manage object information or management Object instances and the corresponding management actions that can be provided form the scope of management capabilities open to third parties or other operators.
  • FIG. 5 a schematic flow diagram of a management service discovery method provided by this application. This method can be used to implement a management object instance (MOI) that provides a management service instance of the creation class for the first network element.
  • MOI management object instance
  • the method includes the following steps:
  • Step 501 The first network element obtains the access information (such as the access address and API call interface) of the management service instance from the server according to the expected management capability information, and the management service instance matches the expected management capability information.
  • the desired management capability information includes at least one of a management action, a type of management object, or a capability attribute.
  • the first network element here may be, for example, EGMF (such as EGMF1, EGMF2) in FIG. 3, or may also be 5G NF, such as MF1, or MF2, or MF3 in FIG. 2 or FIG.
  • EGMF such as EGMF1, EGMF2
  • 5G NF such as MF1, or MF2, or MF3 in FIG. 2 or FIG.
  • this step is as follows: the server receives the desired management capability information sent by the first network element, and the server obtains the access information of the management service instance according to the desired management capability information. The management capability information matches, and then the server sends the access information of the management service instance to the first network element.
  • Step 502 The first network element invokes a management service from a second network element according to the access information of the management service instance and the desired management capability information, and the second network element includes the management service instance.
  • the second network element here is the network element containing the above-mentioned management service.
  • the access information of the management service instance is obtained by the first network element from the server, and the management service instance can communicate with the desired management sent by the first network element.
  • the capability information matches, or it is understood that the management service instance can provide the management capability corresponding to the desired management capability information.
  • Step 503 The first network element receives the creation deployment information from the second network element, and the creation deployment information includes a management object instance corresponding to the type of the management object in the desired management capability information.
  • a management object instance is a network resource that can be managed, or understood as a management object instance used to identify a network resource managed by a management service instance.
  • management objects include network functions, network slice instances, and so on. After a network slice instance is created and deployed, it becomes a network resource that can be managed.
  • MOI is a specific instance of the management object class MOC.
  • the management object has some attributes, such as certain configuration items that can be modified, a list of the next-level management objects (ie, member management objects), etc. MOC will define which attributes the management object contains, and MOI will contain the specific values of these attributes.
  • MOC Object Class Information
  • NRM Network Resource Modeling
  • the first network element calls the above-mentioned management service of the first network element, so that the above-mentioned management service instance creates a management object instance (ie, network resource), and carries the management object instance in the creation and deployment information and sends it to the first network element, thereby
  • the first network element may obtain the management object instance from the second network element.
  • the first network element is an EGMF network element
  • the second network element is an MF network element
  • the first network element is a first MF network element
  • the second network element is a second MF network element
  • the network resource managed by the second MF network element is the network resource managed by the first MF network element
  • the network resource is identified by the management object instance (MOI).
  • the created management object instance is returned to the first network element based on the request of the first network element (carrying the desired management capability information), thereby implementing the operation of creating the management object instance.
  • the server therein can be an MSRF network element or a DNS. Described below separately.
  • the server is an MSRF network element
  • the management service instance included in the management function can pre-register its own management service access address and management capability information to MSRF, where the management capability information of the management service instance includes one or more of the following supported: Management service name, management action, type information of management object, capability attribute. That is, the corresponding relationship between the access information of at least one management service instance and the management capability information is configured on the MSRF network element.
  • the specific implementation of the above step 501 is: the first network element sends a request message to the MSRF network element, the request message includes the desired management capability information, and then the MSRF network element obtains management according to the desired management capability and the foregoing corresponding relationship.
  • the access information of the service instance, and then the MSRF network element sends the access information of the management service instance to the first network element.
  • the second network element may also send the information of the management object instance to the MSRF network element.
  • the information of the management object instance includes the management object instance and the management object instance and other management objects.
  • the relationship between the instances, the management object instance is used to identify the network resource managed by the management service instance; then, the MSRF network element updates the management capability information corresponding to the management service instance according to the information of the management service instance, for example, the management The object instance and the relationship between the managed object instance and other managed object instances are updated to the management capability information corresponding to the managed object instance.
  • the server is DNS
  • the server is DNS
  • a record that is, the mapping from DNS defined domain name to IPv4 address
  • AAAA record that is, DNS defined domain name to IPv6 address Mapping
  • the management capability information of the management service instance includes one or more of the following supported by it: management service name, management action, management object type information, management Object instance, ability attribute.
  • management service name the management service name
  • management action the management object type information
  • management object instance the management service instance
  • ability attribute the domain name of the management service instance and the management service provided by the SRV (service) record (including the server domain name defined by the DNS and the service provided by the server) into the DNS.
  • the management service provided by the management service instance and the corresponding management capability information are configured to the DNS with an authority pointer (Name Authority Pointer, NAPTR) record, thereby completing a resolution from a query domain name to an authoritative domain name. That is to map a string to another string to complete the domain name rewriting. Construct one or more of the management capability information of the management service instance to form a query domain name, use the management service provided by the management service instance or the domain name of the management service instance as the authoritative domain name, and configure regular expressions or replacement rules to query the domain name
  • One or more items of the management capability information in the management capability information can be mapped to the management service or the authoritative domain name of the management service instance after regular expression or replacement processing.
  • a consumer wants to query and create a certain type of management service instance, he can query the management service or management service instance through the NAPTR record according to the desired management capability information. Further query through the SRV record, A record or AAAA record to obtain the interface information of the management service instance that provides the desired management capability.
  • the specific implementation of the above step 501 is: the first network element sends a request message to the DNS, the request message includes the query domain name, and the query domain name is constructed according to the desired management capability information; DNS acquisition and the query domain name The corresponding authoritative domain name of the NAPTR record; then, the DNS obtains the access information of the management service instance corresponding to the authoritative domain name of the NAPTR record, and then sends the access information of the management service instance to the first network element.
  • the first network element can obtain the access information of the management service instance from the DNS in the following two ways:
  • the first authoritative domain name recorded by the NAPTR is the authoritative domain name of the management service instance, and the first network element obtains the access information corresponding to the authoritative domain name recorded by the NAPTR from the DNS.
  • the first network element after the first network element obtains the authoritative domain name of the NAPTR record, it can directly obtain the corresponding access information in the A record or the AAA record according to the authoritative domain name of the NAPTR record.
  • the authoritative domain name recorded by the NAPTR is the authoritative domain name of the management service, and the first network element obtains the authoritative domain name of the SRV record corresponding to the authoritative domain name of the NAPTR record from the DNS, and obtains access information from the DNS according to the authoritative domain name of the SRV record.
  • the first network element obtains the authoritative domain name of the NAPTR record, it first obtains the authoritative domain name of the SRV record according to the authoritative domain name of the NAPTR record, and then obtains the corresponding A record or AAA record according to the authoritative domain name of the SRV record Access information.
  • the second network element may also send the information of the management object instance to the DNS, and then the DNS updates the NAPTR record corresponding to the management service instance according to the information of the management object instance.
  • the information of the management object instance includes the management object instance and the relationship between the management object instance and other management object instances, and the management object instance is used to identify the network resource managed by the management service instance.
  • the management object instance is the top node within the management capability of the management service instance.
  • FIG. 6 there is a schematic flow diagram of another management service discovery method provided for this application.
  • This method can be used to provide the first network element with a non-created management service instance call, and the server is DNS as an example To illustrate, the solution will be described in detail below.
  • the method includes the following steps:
  • Step 601 The first network element sends a request message to the DNS.
  • the request message includes a query domain name.
  • the query domain name is constructed according to the desired management capability information.
  • the desired management capability information includes management services, management actions, and management. At least one of the type of the object or the management object instance, where the management object instance is used to identify the network resource managed by the management service instance.
  • Step 602 The DNS obtains the authoritative domain name of the NAPTR record corresponding to the query domain name.
  • Step 603 The DNS sends the authoritative domain name of the NAPTR record corresponding to the query domain name to the first network element.
  • Step 604 The first network element obtains access information of the management service instance from the DNS according to the authoritative domain name recorded by the NAPTR.
  • Step 605 The first network element invokes the management service to the second network element that provides the management service according to the access information of the management service instance and the desired management capability information.
  • the above-mentioned management object is the top-level node within the management capability of the above-mentioned management service instance.
  • the first network element is an EGMF network element
  • the second network element is an MF network element
  • the first network element is a first MF network element
  • the second network element is a second MF network element
  • the network resource managed by the second MF network element is the network resource managed by the first MF network element
  • the network resource is identified by the management object instance (MOI).
  • FIG. 7 there is a schematic flow diagram of another management service discovery method provided for this application.
  • This method enables tenants (such as external operators or third-party vertical industries) to query the scope of their authorized management capabilities, namely What network resources are allowed to be managed by the tenant, and what operations are allowed to be performed. The scheme will be described in detail below.
  • the method includes the following steps:
  • Step 701 The first network element determines the information object class corresponding to the tenant according to the identifier of the tenant, where one information object class is used to identify a network resource type that can be created.
  • the first network element obtains from the server the information of the creation class management service corresponding to the information object class corresponding to the information object class corresponding to the tenant.
  • the creation class management service information includes the creation class management service name, Create at least one of class management actions or capability attributes.
  • Step 703 The first network element sends a first message to the tenant, where the first message includes the information object class corresponding to the tenant and the information of the available creation class management service.
  • the first network element determines a management object instance corresponding to the tenant according to the identifier of the tenant, where one management object instance is used to identify network resources that can be managed.
  • Step 705 The first network element obtains from the server information about the available management services corresponding to the management object instance according to the management object instance corresponding to the tenant.
  • the information about the management service includes the management service or the information in the management action. at least one.
  • Step 706 The first network element sends a second message to the tenant, where the second message includes the management object instance corresponding to the tenant and the information about the available management service.
  • the tenant with information about the information object class corresponding to the tenant and the available creation management services, or to provide the information object class corresponding to the tenant, the management object instance corresponding to the tenant, and the management service that can be provided.
  • the information and the information of the creation management service that can be provided that is, the information that provides the management capability scope of the tenant.
  • steps 701 and 704 can be combined into one step
  • step 702 and step 705 can be combined into one step
  • step 703 and step 706 can be combined into one step.
  • the above-mentioned server may be an MSRF network element or a DNS.
  • the above step 702 is specifically implemented as: the first network element sends a request message to the DNS, the request message includes the information object class, and the request message is used to request a NAPTR record; The meta receives the information of the available creation management service from the DNS.
  • the above step 705 is specifically implemented as: the first network element sends a request message to the DNS, the request message includes the information object class, and the request message is used to request to query the NAPTR record; the first network element The information of the available management service is received from the DNS.
  • NSMF Network Slice Management Function
  • eMBB enhanced Mobile Broad Band
  • mMTC massive Machine Type Connection
  • uRLLC ultra-high reliability and low latency connections
  • the network shown in Figure 8 also has two subnet slice management functions (Network Slice Subnet Management Function, NSSMF), among which NSSMF1 can create and manage subnet slices and network functions in network area A, and NSSMF2 can be in network area B Create and manage subnet slices and network functions.
  • NSSMF Network Slice Subnet Management Function
  • Third-party vertical industries or other operators send management requests to EGMF, such as creating network slice instances and obtaining network slice performance statistics.
  • EGMF discovers the management function (ie, management service instance) that can provide the required management service through MSRF or DNS, such as NSMF2 in Figure 8, and then EGMF calls the management service provided by NSMF2 as a consumer of the management service.
  • NSMF2 needs to further invoke the management service provided by other network functions to complete the requested management service
  • NSMF2 will find the management service instance that can provide the required management service through MSRF or DNS according to the required network management, as shown in Figure NSSMF2 in 8.
  • NSMF2 calls the management services provided by NSSMF2.
  • FIG. 9 is a specific application of the embodiment in FIG. 5.
  • the EGMF, NSMF2, and MSRF in the embodiment in FIG. 9 can be regarded as the first network element, the second network element, and the server in the embodiment in FIG. 5, respectively, and the NSMF2, NSSMF2, and MSRF in the embodiment in FIG. 9 can also be regarded as respectively The first network element, the second network element and the server in the embodiment of Fig. 5.
  • the process includes the following steps:
  • Step 900 The management service instance included in the management function registers its own management service access address and management capability information to the MSRF.
  • the management capability information of the management service instance includes one or more of the following supported by it: the management service name, management action, type information of the management object, and capability attributes.
  • the management service name may be the standard name of the management service defined in 3GPP TS 28.531 and TS 28.532.
  • the management service names supported by NSMF1 and NSMF2 may be Provisioning for NSI and Provisioning data report for NSI.
  • the management action may be an operation or notification defined by 3GPP TS 28.531 and TS 28.532, such as allocateNSI, createMOI, subscribe (subscribe), notifyNewAlarm, etc.
  • the type information of the management object is the type of the management object operated by the management action, which can be the management object type MOC or the information object type IOC.
  • the types of management objects supported by NSMF1 and NSMF2 are NetworkSlice, NSSMF1 and NSSMF1 defined in 3GPP TS 28.541 NSSMF2 supports NetworkSliceSubnet, etc.
  • the capability attributes are parameters describing management requirements, such as network slicing, subnet slicing, or network function type requirement parameters, performance requirement parameters, range parameters, and so on.
  • the capability attribute can be the network slice and service type sST in ServiceProfile or SliceProfile defined in TS 28.541, coverageAreaTAList of network slice coverage, latency, terminal mobility level uEMobilityLevel, etc.
  • NSMF2 in FIG. 5 registers the supported uRLLC slice type as a capability attribute to MSRF
  • NSSMF2 registers a tracking area (TA) list corresponding to supported area B as a capability attribute to MSRF.
  • TA tracking area
  • Step 901 An external operator requests to create and deploy a uRLLC-type network slice instance in area B, and send a network slice request message to the open control management function (EGMF) of the operator.
  • the message carries the desired management action (ie Create deployment network slice instance), management object type (ie network slice), desired object attributes (ie uRLLC type and coverage area B).
  • Step 902 The EGMF checks the management authority of the external operator, confirms that the external operator is allowed to create a network slicing instance according to the agreement signed by both parties, and then authorizes the execution of the requested operation.
  • Step 903 EGMF according to the desired management capability information carried in the request message, that is, the desired management action (i.e., the creation of a deployment network slice instance), the type of management object (i.e., network slicing), and the desired object attributes (e.g., uRLLC slice type) )
  • the desired management action i.e., the creation of a deployment network slice instance
  • the type of management object i.e., network slicing
  • the desired object attributes e.g., uRLLC slice type
  • Step 904 The EGMF invokes the management service of allocating network slices provided by NSMF2, which carries the expected management action (ie, creating a deployment network slice instance), the type of management object (ie, the network slice), and the expected management action received in step 901.
  • Object attributes ie uRLLC type and coverage area B).
  • Step 905 According to the processing procedure defined in TS 28.531, the NSMF2 decomposes the request for creating a network slice into subnet slice creation requirements, such as creating a subnet slice instance in coverage area B.
  • Step 906 NSMF2 constructs the desired management capability information according to the creation requirements of the decomposed subnet slices, that is, the desired management action (that is, the creation of a deployment subnet slice instance), the type of management object (that is, the subnet slice), and the desired object Attribute (that is, coverageAreaTAList is area B), query MSRF for management services and access addresses that can meet the expected management capabilities.
  • Step 907 NSMF2 invokes the management service of allocating subnet slices provided by NSSMF2, which carries the creation requirements of decomposed subnet slices.
  • Step 908 NSSMF2 creates a deployment subnet slice instance according to the processing defined in TS 28.531, and creates and configures a MOI for the newly created subnet slice instance, for example, configures the identifier of the newly created subnet slice instance as an attribute in the MOI.
  • Step 909 (This step is optional) NSSMF2 can use the MOI of the newly created subnet slice instance as the management object instance part of the management capability information to update its registration information in the MSRF.
  • the specific operation is similar to step 900.
  • Step 910 NSSMF2 sends the creation result of the subnet slice instance to NSMF2, including the MOI of the newly created subnet slice.
  • Step 911 If the NSMF2 needs to create other subnet slices according to the requirements decomposed in step 905, continue to follow the above steps 906 to 910 to complete the creation of all subnet slice instances included in the network slice instance.
  • Step 912 After NSMF2 completes the creation and deployment of all subnet slices, it creates and configures the MOI of the network slice instance, for example, configures the identifier of the newly created network slice instance as an attribute in the MOI.
  • Step 913 (This step is optional) NSMF2 can use the MOI of the newly created network slice instance as the management object instance part of the management capability information to update its registration information in the MSRF.
  • the specific operation is similar to step 900.
  • Step 914 NSMF2 sends the creation and deployment result of the network slice instance to EGMF, which carries the MOI of the newly created network slice instance.
  • Step 915 The EGMF sends the result of creating the network slice instance to the external operator through a network slice creation response message, which carries the identifier of the newly created network slice instance.
  • the internal management function of the network can discover the creation management services and access addresses that meet the desired management capability information, and external industries or other operators can also indirectly discover the desired management capability information through the management open control function.
  • the creation class management service and access address can find a management service instance that meets the expected management capability information among multiple management service instances that support creation operations.
  • FIG. 10 is a specific application of the embodiment in FIG. 5.
  • the EGMF, NSMF2, and DNS in the embodiment in FIG. 10 can be regarded as the first network element, the second network element, and the server in the embodiment in FIG. 5, respectively
  • the NSMF2, NSSMF2, and DNS in the embodiment in FIG. 10 can also be regarded as respectively The first network element, the second network element and the server in the embodiment of Fig. 5.
  • the process includes the following steps:
  • Step 1000 Configure the domain name and access address of the management service instance in the DNS, for example, with A record (that is, the mapping of domain name to IPv4 address defined by DNS) or AAAA record (that is, the mapping of domain name to IPv6 address defined by DNS).
  • a record that is, the mapping of domain name to IPv4 address defined by DNS
  • AAAA record that is, the mapping of domain name to IPv6 address defined by DNS.
  • the authoritative domain name such as nsmf1.plmn1
  • the access address such as the IPv4 address 100.100.100
  • the management service instance contained in the NSMF1 are configured in the DNS in the form of an A record.
  • the management capability information of the management service instance includes one or more of the following supported by it: management service name, management action, management object type information, management Object instance, ability attribute.
  • the specific content of each item of the management capability information is the same as the description in the embodiment of FIG. 9.
  • Configure the domain name of the management service instance and the management service provided by the SRV record (including the server domain name defined by the DNS and the service provided by the server) into the DNS.
  • NSMF1 (the authoritative domain name is nsmf1.plmn1) supports Provisioning for NSI management services
  • the SRV record can be _nsmf1.plmn1._ProvisioningforNSI.
  • NAPTR Name Authority Pointer (refer to RFC2915), which completes a resolution from a query domain name to an authoritative domain name. That is to map a string to another string to complete the domain name rewriting.
  • One or more items of the management capability information in the management capability information can be mapped to the management service or the authoritative domain name of the management service instance after regular expression or replacement processing.
  • management action allocateNSI
  • NetworkSlice management object type information
  • sST eMBB
  • the query domain name configured to the NAPTR record in DNS can be Is _allocateNSI._NetworkSlice._eMBB
  • the corresponding authoritative domain name can be _nsmf1.plmn1._ProvisioningforNSI
  • the regular expression can be any segment of the matching query domain name.
  • NSSMF1 domain name is nssmf1.plmn1
  • the query domain name recorded by NAPTR can be _NetworkSliceSubnet.
  • _TAI-A the corresponding authoritative domain name can be _nssmf1.plmn1._ProvisioningforNSSI, and the regular expression can match the last segment of the query domain name and any other segment.
  • a consumer wants to query and provide a management service instance for creating a certain type of network slice, he can query the management service or management service instance through the NAPTR record according to the desired management capability information. Further query through the SRV record, A record or AAAA record to obtain the interface information of the management service instance that provides the desired management capability.
  • Step 1001 An external operator requests the creation and deployment of a uRLLC type network slice instance in area B, and the network slice request message is sent to the operator’s open control management function EGMF.
  • the message carries the desired management action (ie, create deployment Network slice instance), management object type (ie network slice), desired object attributes (ie uRLLC type and coverage area B).
  • Step 1002 EGMF checks the management authority of the external operator, confirms that the external operator is allowed to create a network slice instance according to the agreement signed by both parties in advance, and then authorizes the execution of the requested operation.
  • Step 1003 EGMF according to the desired management capability information carried in the request message, that is, the desired management action (i.e., the creation of a deployed network slice instance), the type of management object (i.e., network slicing), and the desired object attributes (e.g., uRLLC slice type) And coverage area B), query the DNS for management services or management service instances that can meet the expected management capabilities.
  • the desired management action i.e., the creation of a deployed network slice instance
  • the type of management object i.e., network slicing
  • the desired object attributes e.g., uRLLC slice type
  • DNS query related records configured in step 1000 through regular expressions or replacement, determine that the NAPTR record configured for NSMF2 in step 1000 can match the query request, for example, query domain name _allocateNSI._NetworkSlice._uRLLC._TAI-B contains the NAPTR record _AllocateNSI._NetworkSlice._uRLLC, that is, the management capability information of NSMF2 matches the expected management capability information carried in the query message, and the authoritative domain name nsmf2.plmn1 of the management service instance of NSMF2 is sent to EGMF as a response message, where the response message The flag of is set to A, that is, the next step can execute A query to obtain the access address according to the authoritative domain name obtained in the response message.
  • the authoritative domain name in the NAPTR record set in step 1000 is the management service _nsmf2.plmn1._ProvisioningforNSI provided by NSMF2, then the flag of the response message is set to S, that is, the next step is obtained according to the response message
  • the authoritative domain name can execute the SRV query to obtain the authoritative domain name nsmf2.plmn1 of the management service instance of NSMF2, and then execute the A query to obtain the access address.
  • the existing DNS system is also supported, and will not be repeated in this embodiment.
  • Step 1004 EGMF uses the authoritative domain name of the management service instance of NSMF2 to query DNS to obtain the access address of the management service instance, that is, the IP address and port information of the access management service interface.
  • Step 1005 EGMF invokes the management service for allocating network slices provided by NSMF2, which carries the desired management action (ie, creating a deployment network slice instance), the type of management object (ie, network slice), and the desired management action received from step 1 Object attributes (ie uRLLC type and coverage area B).
  • desired management action ie, creating a deployment network slice instance
  • type of management object ie, network slice
  • Object attributes ie uRLLC type and coverage area B.
  • Step 1006 NSMF2 decomposes the request for creating a network slice into subnet slice creation requirements according to the processing procedure defined in TS 28.531, such as creating a subnet slice instance in coverage area B.
  • Step 1007 NSMF2 constructs the desired management capability information according to the creation requirements of the decomposed subnet slices, that is, the desired management action (that is, the creation of a deployment subnet slice instance), the type of management object (that is, the subnet slice), and the desired object Attribute (that is, coverageAreaTAList is area B), query DNS for management services or management service instances that can meet the expected management capabilities.
  • the desired management action that is, the creation of a deployment subnet slice instance
  • the type of management object that is, the subnet slice
  • the desired object Attribute that is, coverageAreaTAList is area B
  • query DNS for management services or management service instances that can meet the expected management capabilities.
  • NSMF2 constructs the query domain name _allocateNSSI._NetworkSliceSubnet._TAI-B with the above-mentioned desired management action, and then sends a NAPTR query request to DNS.
  • DNS query step 1000 configures the relevant records, it is determined that the NAPTR record configured for NSSMF2 can match the query request (that is, according to the regular expression operation _allocateNSSI._NetworkSliceSubnet._TAI-B contains _NetworkSliceSubnet._TAI-B), then the NSSMF2 is managed
  • the authoritative domain name nssmf2.plmn1 of the service instance is sent to NSMF as a response message, and the flag of the response message is set to A.
  • Step 1008 NSMF2 uses the authoritative domain name of the management service instance of NSSMF2 to query DNS to obtain the access address of the management service instance.
  • Step 1009 NSMF2 invokes the management service of allocating subnet slices provided by NSSMF2, which carries the creation requirements of decomposed subnet slices.
  • Step 1010 NSSMF2 creates a deployment subnet slice instance according to the processing defined in TS 28.531, and creates and configures an MOI for the newly created subnet slice instance, for example, configures the identifier of the newly created subnet slice instance as an attribute in the MOI.
  • Step 1011-1 (this step is optional): If the newly created MOI is a top-level node within the management capability of the management service instance, set the top-level node flag on the newly created MOI.
  • FIG 11 it is a schematic diagram of the top node MOI and the top node mark within the management scope of the management service instance.
  • the management service instance is NSMF
  • its management scope includes the entire network slice instance. Therefore, the MOI of the newly created network instance (NSI#A and NSI#B in the figure) created by NSMF will be set with the top node mark by NSMF.
  • the MOIs of the subnet slice instances NSSI#1, NSSI#2, NSSI#3, etc. in Figure 11 will be set with the top-level node flag by NSSMF. Because the management service instance in Figure 11 has both NSSMF and NFMF functions, network functions such as NF#1 are not the top nodes within the management scope of the management service instance, so the top node flag is not set.
  • Step 1011-2 (this step is optional): If the newly created MOI is set with the top-level node flag, you can use this MOI as part of the management capability information, update the management capability information of the management service instance, and update the step with the new management capability information 0 NAPTR record configured in DNS.
  • the query domain name corresponding to the management capability information of NSSMF2 was originally _NetworkSliceSubnet._TAI-B, now it is updated to _NetworkSliceSubnet._TAI-B._NSSI-1, or a new NAPTR record is added, and the query domain name is _NetworkSliceSubnet._NSSI-1,
  • the authoritative domain name is the domain name of NSSMF2. In this way, the subsequent query domain name _NSSI-1 constructed using the MOI of the network slicing subnet NSSI#1 can also find the NSSMF2 that manages NSSI#1.
  • Step 1012 NSSMF2 sends the creation result of the subnet slice instance to NSMF2, including the MOI of the newly created subnet slice.
  • Step 1013 If the NSMF2 needs to create other subnet slices according to the requirements after decomposition in step 1005, continue to follow the above steps 1006 to 1012 to complete the creation of all subnet slice instances included in the network slice instance.
  • Step 1014 After NSMF2 completes the creation and deployment of all subnet slices, it creates and configures the MOI of the network slice instance, for example, configures the ID of the newly created network slice instance as an attribute in the MOI.
  • Step 1015 (this step is optional):
  • the MOI of the newly created network slice instance can be used as part of the NSMF2 management capability information, and the configuration in DNS can be updated or newly added, so that subsequent queries can be made through the MOI of the newly created network slice instance To NSMF2, the method is similar to step 1011-1 and step 1011-2.
  • Step 1016 NSMF2 sends the creation and deployment result of the network slice instance to EGMF, which carries the MOI of the newly created network slice instance.
  • Step 1017 The EGMF sends the result of creating the network slice instance to the external operator through a network slice creation response message, which carries the identifier of the newly created network slice instance.
  • the management function inside the network can find the creation management service and access address that meets the desired management capability information, and the external industry or other operators can also indirectly discover the management capability information that meets the expectations through the management open control function.
  • the creation class management service and access address Compared with the prior art, the solution of this embodiment can find a management service instance that meets the expected management capability information among multiple management service instances that support creation operations. Furthermore, it can be compatible with the existing DNS system, and there is no need to add a new MSRF entity, which further reduces the cost of the system.
  • the management object instance of the management service embodiment can be created, and then the management object instance can be used directly in the future.
  • the following further introduces the processing flow when an external operator requests to obtain the performance statistics of the network slice instance created for it, using DNS to perform management services and management capability discovery.
  • FIG. 12 it is a flowchart of another management service discovery method provided by this application.
  • the embodiment in FIG. 12 is a specific example of the embodiment shown in FIG. 6.
  • the EGMF, NSMF2, and DNS in the embodiment in FIG. 12 can be regarded as the first network element, the second network element and the server in the embodiment in FIG. 6, respectively, and the NSMF2, NSSMF2, and DNS in the embodiment in FIG. 12 can also be regarded as respectively The first network element, the second network element and the server in the embodiment of Fig. 6.
  • the method includes the following steps:
  • Step 1201 An external operator requests to obtain the performance statistics of the network slice instance NSI#B, and sends a request message for subscribing to the network slice performance statistics to the EGMF, which carries the IOC (that is, NetworkSlice) and MOI of NSI#B (the MOI is not The MOI of the top node or the MOI of the top node, the MOI is NSI-B).
  • IOC that is, NetworkSlice
  • MOI of NSI#B the MOI is not The MOI of the top node or the MOI of the top node, the MOI is NSI-B).
  • Step 1202 EGMF checks the management authority of the external operator, confirms that the external operator is allowed to obtain the performance data of NSI#B according to the agreement signed in advance by both parties, and then authorizes the execution of the requested operation.
  • Step 1203 EGMF according to the desired management capability information carried in the request message, that is, the desired management service (i.e. performance assurance management service), management action (i.e. subscription), type of management object (i.e. network slice), One or more of MOI (namely NSI-B) queries DNS for management services or management service instances that can meet the expected management capabilities.
  • the EGMF constructs the query domain name _subscribe._NetworkSlice._NSI-B with the aforementioned desired management action, and then sends a NAPTR query request to the DNS.
  • DNS query update or configuration related records through regular expressions or replacement, determine that the NAPTR record configured for NSMF2 can match the query request, then the authoritative domain name nsmf2.plmn1 of the management service instance of NSMF2 is sent to EGMF as a response message, where The flag of the response message is set to A, that is, the next step can execute A query to obtain the access address according to the authoritative domain name obtained in the response message.
  • Step 1204 EGMF uses the authoritative domain name of the management service instance of NSMF2 to query DNS to obtain the access address of the management service instance, that is, the IP address and port information of the access management service interface.
  • Step 1205 EGMF calls the performance statistics management service provided by NSMF2, which carries the expected management action (ie subscription performance statistics data), type of management object (ie network slice), and expected object attributes ( Namely NSI-B).
  • NSMF2 carries the expected management action (ie subscription performance statistics data), type of management object (ie network slice), and expected object attributes ( Namely NSI-B).
  • Step 1206 NSMF2 determines the performance data of subnet slices or network functions to be collected according to the processing procedure defined in TS 28.550, and decomposes it into sub-performance statistics tasks, such as collecting performance statistics of NSSI#3 and NF#4 in Figure 11.
  • Step 1207a For the MOI with the top node mark like NSSI#3, NSMF2 constructs the desired management capability information according to the decomposed subtasks, that is, the desired management action (subscription performance statistics), and the type of management object (ie, sub-network slice) ), the management object MOI (namely NSSI-3), query the DNS for management services or management service instances that can meet the expected management capabilities. Specifically, similar to step 1203, NSMF2 constructs the query domain name _subscribe._NetworkSliceSubnet._NSSI-3 with the above-mentioned desired management action, and then sends a NAPTR query request to DNS.
  • the desired management action subscription performance statistics
  • the type of management object ie, sub-network slice
  • the DNS determines that the NAPTR record configured for NSSMF2 can match the query request according to the related records updated or configured in the second embodiment, and sends the authoritative domain name nssmf2.plmn1 of the management service instance of NSSMF2 as a response message to NSMF2.
  • Step 1207b-1 For the MOI without the top-level node mark like NF#4, NSMF2 uses the target MOI as the starting point to find the first higher-level MOI with the top-level mark. For example, in Figure 11, the first MOI with the top mark found from NF#4 is NSSI-3.
  • Step 1207b-2 NSMF2 uses the top MOI of the management capability scope to construct a DNS query message.
  • the specific method is the same as step 1207a.
  • the management capability range of the management service instance NSSMF2 that can be queried to manage NSSI-3 includes the target MOI (ie NF#4), so you can subsequently request to subscribe to the performance statistics of NF#4 from NSSMF2.
  • Step 1208 NSMF2 uses the authoritative domain name of the management service instance of NSSMF2 to query DNS to obtain the access address of the management service instance.
  • Step 1209 NSMF2 invokes the subnet slice performance data subscription service and network function performance data subscription service provided by NSSMF2 to complete the creation of the performance statistics subtask.
  • Step 1210 So after the subtask is successfully created, NSMF2 creates a performance statistics task of NSI#B, and returns a performance statistics subscription response message to EGMF, which carries the identifier of the newly created performance statistics task.
  • Step 1211 EGMF sends the subscription response message to the external operator.
  • the management object is used as a part of the management capability information to perform DNS query to obtain a management service instance that can support non-creation operations on the management object.
  • FIG. 13 it is a flowchart of another method for discovering management services provided by this application.
  • the embodiment in FIG. 13 is a specific example of the embodiment shown in FIG. Among them, the other operators, EGMF and MSRF in the embodiment of FIG. 13 can be regarded as tenants, the first network element and the server in the embodiment of FIG. 7 respectively.
  • External operators or third-party vertical industries often need to inquire about the scope of their authorized management capabilities, that is, which network resources are allowed to be managed by operators or third parties, and what operations are allowed to be performed.
  • the following is an example of a process in which an external operator requests to obtain its own management capability scope through open management functions.
  • the method includes the following steps:
  • Step 1301 An external operator sends a request message to EGMF, requesting to query the authorized management capability range, and the request message carries the tenant ID.
  • the tenant identifier is an identifier for the third-party vertical industry or tenants of other operators by the operator that provides network opening to the outside world.
  • Step 1302 EGMF checks and determines the identity of the tenant, and then determines the management authority of the tenant according to the agreement signed in advance by both parties. Specifically, determine the type of network resource that the tenant can create, that is, the IOC or its list that the tenant can manage; and determine the network resource that the tenant can manage, that is, the management object MOI or its list.
  • Step 1303 EGMF queries MRSF for the registration information of the management service instance with a certain IOC or IOC list obtained in step 1302, obtains the name of the creation class management service that all available management service instances can provide to the target IOC, and creates a class management action (can be Optional), and ability attributes (optional). EGMF obtains the creation class management service name, creation class management action, and capability attributes that can be provided for each IOC in the above IOC list.
  • Step 1304 EGMF queries the MRSF for the registration information of the management service instance with a certain MOI or MOI list obtained in step 1302, obtains the management service names that all available management service instances can provide to the target MOI, and management actions (optional). EGMF obtains the name of the management service that can be provided for each MOI in the above MOI list, and the management action (optional).
  • Step 1305 EGMF summarizes the results obtained in steps 1303 and 1304, and the query obtained ⁇ Createable IOC, one or more creation class management service names, one or more creation class management actions (optional), capability attributes (optional) ) ⁇ and/or ⁇ Manageable MOI, allowed one or more management service names, allowed one or more management actions (optional) ⁇ as a tenant management capability range.
  • Step 1306 EGMF sends the tenant management capability range obtained in step 1305 as a query result response to the external operator.
  • external operators can know which network resources are allowed to be managed, what operations are allowed to be performed, and so on.
  • the third-party vertical industry or external operator obtains network resources that can be managed by itself and allows operations to be performed.
  • the scope of tenant management capabilities includes the scope of creation operations and the scope of non-creation operations, which is more comprehensive and flexible than existing technologies.
  • FIG. 14 it is a flowchart of yet another management service discovery method provided by this application.
  • the embodiment in FIG. 14 is a specific example of the embodiment shown in FIG. Among them, the other operators, EGMF and DNS in the embodiment of FIG. 14 can be regarded as the tenant, the first network element and the server in the embodiment of FIG. 7 respectively.
  • the method includes the following steps:
  • Step 1400 Configure the management capability record of each management service instance in the DNS system, and the method is the same as the related description of step 1000 in the embodiment of FIG. 10.
  • Step 1401 An external operator sends a request message to EGMF, requesting to query the authorized management capability range, and the request message carries the tenant ID.
  • the tenant identifier is an identifier for the third-party vertical industry or tenants of other operators by the operator that provides network opening to the outside world.
  • Step 1402 EGMF checks and determines the identity of the tenant, and then determines the management authority of the tenant according to the agreement signed in advance by both parties. Specifically, determine the type of network resource that the tenant can create, that is, the IOC or its list that the tenant can manage; and determine the network resource that the tenant can manage, that is, the management object MOI or its list.
  • Step 1403 EGMF queries DNS for the registration information of the management service instance from a certain IOC obtained in step 1402, obtains the name of the creation class management service that all available management service instances can provide to the target IOC, and creates the class management action (optional), And ability attributes (optional).
  • the specific EGMF uses "_IOC” to send a NAPTR query to DNS, and obtains a query response with the replacement management service name and the S flag.
  • the replacement field "_operation._IOC” or “_operation._IOC._capability attribute” is the scope of creation-type operation management capability, and the SVR field is the management service name.
  • EGMF repeats this step with the above information related to each IOC in the above IOC list.
  • Step 1404a (optional step): EGMF may further query the access address of the management service instance obtained in step 1403.
  • Step 1404b (optional step): EGMF sends a message to the management service to detect that the management service instance can be accessed. If it cannot be accessed, the related record is removed from the result obtained in step 1403.
  • Step 1405 For each MOI obtained by obtaining the MOI list in step 1402, find the MOI that sets the top-level flag of the management scope. For the method, refer to the related description of the embodiment in FIG. 12. All the obtained MOIs with the top-level flags are formed into a new list.
  • Step 1406 EGMF performs a NAPTR query for each MOI with the top-level flag in the list obtained in step 1405.
  • the specific query request carries "_MOI”, and a query response with the replacement management service name and the S flag is obtained.
  • the replacement field "_operation._MOI” or “_operation._IOC._MOI” is the scope of non-creation operation management capabilities, and the SVR field is the management service name.
  • EGMF repeats this step for each MOI related to the above information in the above MOI list.
  • Step 1407 Similar to steps 1404a and 1404b, the EGMF queries the service address and detects that the management service instance is accessible. If it cannot be accessed, the related record is excluded from the result obtained in step 1406.
  • Step 1408 EGMF summarizes the results obtained in steps 1403 and 1406, the query obtained ⁇ createable IOC, one or more creation class management service names, one or more creation class management actions (optional), capability attributes (optional) ) ⁇ and/or ⁇ Manageable MOI with top-level logo, allowed one or more management services (optional), allowed one or more management actions (optional) ⁇ as the tenant management capability range .
  • Step 1409 EGMF sends the tenant management capability range obtained in step 1408 as a query result response to the external operator.
  • external operators can know which network resources are allowed to be managed, what operations are allowed to be performed, and so on.
  • the third-party vertical industry or external operator obtains network resources that can be managed by itself and allows operations to be performed.
  • the scope of tenant management capabilities includes the scope of creation operations and the scope of non-creation operations, which is more comprehensive and flexible than existing technologies.
  • it can be compatible with the existing DNS system and obtain the scope of management capabilities through DNS query.
  • the management capability information of the management service instance creation class includes: supported management services, supported operations, type IOC of managed objects, optional capability attributes; non-created management capability information includes: supported management services, support The operation, the type of management object IOC, optional MOI.
  • the above-mentioned management capability information of the management service instance is registered to MSRF or configured to the DNS system.
  • the management capability information of the management service instance is configured to the DNS in the form of a NAPRT record, and it is supported to query the DNS with the capability information to obtain the management service or the domain name of the management service instance.
  • the newly created management object is the top node within the scope of management capability, and a flag is set for the top node MOI within the scope of management capability.
  • the management service consumer uses the target MOI as the starting point to query the MOI with the top node of the management capability range, and then performs DNS NAPTR query to obtain management services or management service instances with "operation + IOC + top MOI" domain name.
  • EGMF uses the tenant-manageable IOC and MOI as the identifier to query the management actions that can be provided by the management service instances that query all available statuses to the MSRF, and the query results form the tenant management capability range.
  • management services can find management services and access addresses that meet the desired management capability information based on expected management actions and management objects, and third-party vertical industries or external operators can also obtain networks that they can manage. Resources and allowed operations.
  • the above technology can also be compatible with the existing DNS system, further reducing the cost of the system.
  • each network element described above includes hardware structures and/or software modules corresponding to each function.
  • the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered as going beyond the scope of the present invention.
  • the apparatus 1500 may exist in the form of software or hardware.
  • the apparatus 1500 may include: a processing unit 1502 and a communication unit 1503.
  • the communication unit 1503 may include a receiving unit and a sending unit.
  • the processing unit 1502 is used to control and manage the actions of the device 1500.
  • the communication unit 1503 is used to support communication between the device 1500 and other network entities.
  • the device 1500 may further include a storage unit 1501 for storing program codes and data of the device 1500.
  • the processing unit 1502 may be a processor or a controller, for example, a general-purpose central processing unit (central processing unit, CPU), a general-purpose processor, a digital signal processing (digital signal processing, DSP), and an application specific integrated circuit (application specific integrated circuit). circuits, ASIC), field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination for realizing computing functions, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the storage unit 1501 may be a memory.
  • the communication unit 1503 is an interface circuit of the device for receiving signals from other devices.
  • the communication unit 1503 is an interface circuit used by the chip to receive signals from other chips or devices, or an interface circuit used by the chip to send signals to other chips or devices.
  • the device 1500 may be the first network element in any of the foregoing embodiments, and may also be a chip for the first network element.
  • the processing unit 1502 may be, for example, a processor
  • the communication unit 1503 may be, for example, a transceiver.
  • the transceiver may include a radio frequency circuit
  • the storage unit may be, for example, a memory.
  • the processing unit 1502 may be, for example, a processor
  • the communication unit 1503 may be, for example, an input/output interface, a pin, or a circuit.
  • the processing unit 1502 can execute computer-executable instructions stored in the storage unit.
  • the storage unit is a storage unit in the chip, such as a register and a cache.
  • the storage unit may also be a storage unit located in the first network element.
  • the storage unit outside the chip such as read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), etc.
  • the communication unit 1503 is configured to obtain access information of a management service instance from a server according to the desired management capability information.
  • the management service instance matches the desired management capability information.
  • the desired management capability information includes at least one of a management action, a type of a management object, or a capability attribute;
  • the processing unit 1502 is configured to send information to the first instance according to the access information of the management service instance and the desired management capability information
  • the management service is invoked by two network elements, and the second network element includes the management service instance;
  • the communication unit 1503 is further configured to receive creation deployment information from the second network element, and the creation deployment information includes the management
  • the type of the object corresponds to the management object instance, and the management object instance is used to identify the network resource managed by the management service instance.
  • the server is a management service warehouse functional network element;
  • the communication unit 1503 is specifically configured to send a request message to the management service warehouse functional network element, and the request message includes the desired Management capability information;
  • the first network element receives the access information of the management service instance from the management service warehouse function network element.
  • the server is a domain name server;
  • the communication unit 1503 is specifically configured to send a request message to the domain name server, the request message includes querying a domain name, and the querying a domain name is based on the The desired management capability information is constructed; the authoritative domain name recorded by the name authority pointer NAPTR corresponding to the query domain name is received from the domain name server; the management service instance is obtained from the domain name server according to the authoritative domain name recorded by the NAPTR Access information.
  • the first authoritative domain name of the NAPTR record is the authoritative domain name of the management service instance
  • the communication unit 1503 is specifically configured to obtain the authoritative domain name of the NAPTR record from the domain name server.
  • the access information of the management service instance corresponding to the domain name; or, the authoritative domain name recorded by the NAPTR is the authoritative domain name of the management service
  • the communication unit 1503 is specifically configured to obtain the authority of the NAPTR record from the domain name server.
  • the authoritative domain name of the service SRV record corresponding to the domain name, and the access information of the management service instance is obtained from the domain name server according to the authoritative domain name of the SRV record.
  • the device is an open control management function network element, and the second network element is a management function network element; or, the device is a first management function network element, and the second network element The element is a second management function network element, and the network resource managed by the second management function network element is a component of the network resource managed by the first management function network element.
  • the communication unit 1503 is configured to send a request message to a domain name server, the request message includes a query domain name, the query domain name is constructed according to the desired management capability information, and the desired management
  • the capability information includes at least one of a management service, a management action, a type of a management object, or a management object instance.
  • the management object instance is used to identify network resources managed by the management service instance; and the query is received from the domain name server.
  • the name authority pointer corresponding to the domain name is the authoritative domain name recorded by the NAPTR; according to the authoritative domain name recorded by the NAPTR, the access information of the management service instance is obtained from the server; and, according to the access information and the expectation of the management service instance The management capability information of, calls the management service to the second network element that provides the management service.
  • the management object is a top-level node within the management capability of the management service instance.
  • the device is an open control management function network element, and the second network element is a management function network element; or, the device is a first management function network element, and the second network element The element is a second management function network element, and the network resource managed by the second management function network element is a component of the network resource managed by the first management function network element.
  • the processing unit 1502 is configured to determine the information object class corresponding to the tenant according to the identifier of the tenant, where one information object class is used to identify a network resource type that can be created;
  • the communication unit 1503 is configured to obtain, from the server, information about the creation management service corresponding to the information object class that can be provided according to the information object class corresponding to the tenant, and the information about the creation management service includes the name of the creation management service At least one of a creation class management action or a capability attribute; and, sending a first message to the tenant, the first message including the information object class corresponding to the tenant and the available creation class management service information.
  • the server is a domain name server;
  • the communication unit 1503 is specifically configured to send a request message to the domain name server, the request message includes the information object class, and the request message uses To request a NAPTR record; receive the information of the available creation management service from the domain name server.
  • the processing unit 1502 is further configured to determine the management object instance corresponding to the tenant according to the identifier of the tenant, wherein one management object instance is used to identify network resources that can be managed;
  • the communication unit 1503 is further configured to obtain from the server information about the available management services corresponding to the management object instance according to the management object instance corresponding to the tenant, and the information about the management service includes management service or management At least one of the actions; and, sending a second message to the tenant, the second message including the management object instance corresponding to the tenant and the information about the available management service.
  • the server is a domain name server
  • the communication unit 1503 is specifically configured to send a request message to the domain name server, the request message includes the information object class, and the request message uses Querying the NAPTR record upon request; and receiving the information of the available management service from the domain name server.
  • the apparatus 1600 may exist in the form of software or hardware.
  • the apparatus 1600 may include: a processing unit 1602 and a communication unit 1603.
  • the communication unit 1603 may include a receiving unit and a sending unit.
  • the processing unit 1602 is used to control and manage the actions of the device 1600.
  • the communication unit 1603 is used to support communication between the device 1600 and other network entities.
  • the device 1600 may further include a storage unit 1601 for storing program codes and data of the device 1600.
  • the processing unit 1602 may be a processor or a controller, for example, a CPU, a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination for realizing computing functions, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the storage unit 1601 may be a memory.
  • the communication unit 1603 is an interface circuit of the device for receiving signals from other devices. For example, when the device is implemented as a chip, the communication unit 1603 is an interface circuit for the chip to receive signals from other chips or devices, or an interface circuit for the chip to send signals to other chips or devices.
  • the device 1600 may be the server in any of the above embodiments, and may also be a chip used for the server.
  • the processing unit 1602 may be a processor
  • the communication unit 1603 may be a transceiver, for example.
  • the transceiver may include a radio frequency circuit
  • the storage unit may be, for example, a memory.
  • the processing unit 1602 may be a processor, for example, and the communication unit 1603 may be an input/output interface, a pin or a circuit, for example.
  • the processing unit 1602 can execute computer-executable instructions stored in the storage unit.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located outside the chip in the server.
  • Storage unit such as ROM or other types of static storage devices that can store static information and instructions, RAM, etc.
  • the communication unit 1603 is configured to receive desired management capability information, where the desired management capability information includes at least one of a management action, a type of management object, or a capability attribute; the processing unit 1602, configured to obtain access information of a management service instance according to the desired management capability information, where the management service instance matches the desired management capability information; the communication unit 1603 is also configured to send the management service Access information for the instance.
  • the device is a functional network element of a management service warehouse; the communication unit 1603 is specifically configured to receive a request message, the request message including the desired management capability information; the service warehouse The functional network element is configured with a corresponding relationship between access information of at least one management service instance and management capability information.
  • the processing unit 1602 is specifically configured to obtain the management service according to the desired management capability information and the corresponding relationship. Access information for the instance.
  • the communication unit 1603 is also configured to receive information about a management object instance, and the information about the management object instance includes the management object instance and the relationship between the management object instance and other management object instances. Relationship, the management object instance is used to identify the network resources managed by the management service instance; the processing unit 1602 is also used to update the management capability information corresponding to the management service instance according to the information of the management object instance .
  • the device is a domain name server;
  • the communication unit 1603 is specifically configured to receive a request message, the request message queries a domain name, and the query domain name is constructed according to the desired management capability information
  • the processing unit 1602 is specifically configured to obtain the authoritative domain name of the NAPTR record corresponding to the query domain name; to obtain the access information of the management service instance corresponding to the authoritative domain name of the NAPTR record.
  • the authoritative domain name recorded by the NAPTR is the authoritative domain name of the management service instance
  • the processing unit 1602 is specifically configured to obtain the management corresponding to the authoritative domain name of the management service instance.
  • Access information of the service instance; or, the authoritative domain name recorded by the NAPTR is the authoritative domain name of the management service
  • the processing unit 1602 is specifically configured to obtain the authoritative domain name of the SRV record corresponding to the authoritative domain name of the management service, and according to The authoritative domain name of the SRV record obtains the access information of the management service instance.
  • the communication unit 1603 is also configured to receive information about a management object instance, and the information about the management object instance includes the management object instance and the relationship between the management object instance and other management object instances. Relationship, the management object instance is used to identify the network resource managed by the management service instance, the management object instance is the top node within the management capability of the management service instance; the processing unit 1602 is also used for According to the information of the management object instance, the NAPTR record corresponding to the management service instance is updated.
  • the apparatus may be the first network element or the server in the above-mentioned embodiment.
  • the device 1700 includes a processor 1702, a communication interface 1703, and a memory 1701.
  • the apparatus 1700 may further include a communication line 1704.
  • the communication interface 1703, the processor 1702, and the memory 1701 may be connected to each other through a communication line 1704;
  • the communication line 1704 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (extended industry standard architecture). , Referred to as EISA) bus and so on.
  • the communication line 1704 can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one thick line is used in FIG. 17, but it does not mean that there is only one bus or one type of bus.
  • the processor 1702 may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits used to control the execution of the program of the present application.
  • Communication interface 1703 which uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), Wired access network, etc.
  • RAN radio access network
  • WLAN wireless local area networks
  • Wired access network etc.
  • the memory 1701 may be ROM or other types of static storage devices that can store static information and instructions, RAM or other types of dynamic storage devices that can store information and instructions, or may be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory).
  • read-only memory EEPROM
  • compact disc read-only memory, CD-ROM
  • optical disc storage including compact discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.
  • magnetic disks A storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory may exist independently and is connected to the processor through a communication line 1704. The memory can also be integrated with the processor.
  • the memory 1701 is used to store computer-executable instructions for executing the solutions of the present application, and the processor 1702 controls the execution.
  • the processor 1702 is configured to execute computer-executable instructions stored in the memory 1701, so as to implement the management service discovery method provided by the foregoing embodiments of the present application.
  • the computer-executable instructions in the embodiments of the present application may also be referred to as application program code, which is not specifically limited in the embodiments of the present application.
  • At least one (piece, species) of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or Multiple.
  • Multiple refers to two or more, and other measure words are similar.
  • "a device” means to one or more such devices.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)), etc.
  • the various illustrative logic units and circuits described in the embodiments of this application can be implemented by general-purpose processors, digital signal processors, application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, Discrete gates or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions.
  • the general-purpose processor may be a microprocessor, and optionally, the general-purpose processor may also be any traditional processor, controller, microcontroller, or state machine.
  • the processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration achieve.
  • the steps of the method or algorithm described in the embodiments of the present application can be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
  • the software unit can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other storage medium in the field.
  • the storage medium may be connected to the processor, so that the processor can read information from the storage medium, and can store and write information to the storage medium.
  • the storage medium may also be integrated into the processor.
  • the processor and the storage medium can be arranged in the ASIC.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Abstract

本申请提供一种管理服务的发现方法及装置。该方法包括：第一网元根据期望的管理能力信息，从服务器获取管理服务实例的访问信息，管理服务实例与期望的管理能力信息匹配，期望的管理能力信息包括管理动作、管理对象的类型、或能力属性中的至少一个；第一网元根据管理服务实例的访问信息和期望的管理能力信息，向第二网元调用管理服务，第二网元包括上述管理服务实例；第一网元从第二网元接收创建部署信息，创建部署信息包括上述管理对象的类型对应管理对象实例，该管理对象实例用于标识所述管理服务实例所管理的网络资源。该方案实现了基于第一网元的请求，向第一网元返回创建的管理对象实例，从而实现了创建管理对象实例的操作。

Description

一种管理服务的发现方法及装置
相关申请的交叉引用
本申请要求在2019年06月17日提交中国专利局、申请号为201910521531.8、申请名称为“一种管理服务的发现方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信技术领域，尤其涉及一种管理服务的发现方法及装置。
背景技术
在现有技术中，为了实现管理服务实例的发现引入管理服务仓库功能(Management Service Repository Function，MSRF)网元。所有的管理功能都向MSRF注册自身的管理服务实例信息，其中包括管理服务实例的接口访问地址和其管理的网络资源。因为管理服务实例所管理的网络资源使用管理对象实例(Managed Object Instance，MOI)标识，所以管理功能(Management Function，MF)需要对某个网络资源执行管理动作时，就向MSRF发送查询请求，其中携带所述管理功能的MOI。MSRF根据所述MOI查询存储的管理服务实例的注册信息，得到管理服务实例的接口访问地址，然后通过响应消息发送给管理功能。
通过这种方法，管理功能能够通过MSRF发现管理MOI标识的网络资源的网络管理服务实例，获得接口访问地址，然后调用管理服务(Management Service，MnS)对网络资源执行修改、删除、订阅、通知等管理动作。
上述方案存在的缺陷是：当需要创建和部署某个网络资源时，如果有多个管理服务实例支持创建和部署网络资源，因为管理对象MOI还没有被创建，使用现有技术无法知道哪个管理服务实例能够满足创建和部署目标网络资源的管理需求。
发明内容
本申请提供一种管理服务的发现方法及装置，用以实现根据管理功能的期望的管理能力信息，创建管理对象实例。
第一方面，本申请提供一种管理服务的发现方法，该方法包括：第一网元根据期望的管理能力信息，从服务器获取管理服务实例的访问信息，所述管理服务实例与所述期望的管理能力信息匹配，所述期望的管理能力信息包括管理动作、管理对象的类型、或能力属性中的至少一个；所述第一网元根据所述管理服务实例的访问信息和所述期望的管理能力信息，向第二网元调用管理服务，所述第二网元包括所述管理服务实例；所述第一网元从所述第二网元接收创建部署信息，所述创建部署信息包括所述管理对象的类型对应管理对象实例，所述管理对象实例用于标识所述管理服务实例所管理的网络资源。基于该方案，实现了基于第一网元的请求(携带期望的管理能力信息)，向第一网元返回创建的管理对象实例，从而实现了创建管理对象实例的操作。
在一种可能的实现方法中，所述服务器为管理服务仓库功能网元；更具体的，所述管理服务仓储功能网元可以为通用应用编程接口框架(Common Application Program Interface Framework-Core Function，CAPIF)中的核心功能(Core Function，CF)、应用编程接口开放功能(API Exposing Function，AEF)、应用编程接口发布功能(API Publishing Function。APF)或应用编程接口管理功能(APIManagement Function，AMF)中的任意一个或任意多个的组合；所述第一网元根据期望的管理能力信息，从服务器获取管理服务实例的访问信息，包括：所述第一网元向所述管理服务仓库功能网元发送请求消息，所述请求消息包括所述期望的管理能力信息；所述第一网元从所述管理服务仓库功能网元接收所述管理服务实例的访问信息。
在一种可能的实现方法中，所述服务器为域名服务器；更具体的，所述域名服务器为互联网的域名系统(Domain Name System，DNS)，或者通用应用编程接口框架CAPIF中负责发布、存储和支持服务API信息发现的功能可以由DNS实现；所述第一网元根据期望的管理能力信息，从服务器获取管理服务实例的访问信息，包括：所述第一网元向所述域名服务器发送请求消息，所述请求消息包括查询域名，所述查询域名是根据所述期望的管理能力信息构造的；所述第一网元从所述域名服务器接收与所述查询域名对应的名称权威指针NAPTR记录的权威域名；所述第一网元根据所述NAPTR记录的权威域名，从所述域名服务器获取所述管理服务实例的访问信息。
在一种可能的实现方法中，所述第一网元根据所述NAPTR记录的权威域名，从所述域名服务器获取所述管理服务实例的访问信息，包括：所述NAPTR记录的第一权威域名为所述管理服务实例的权威域名，所述第一网元从所述域名服务器获取与所述NAPTR记录的权威域名对应的所述管理服务实例的访问信息；或者，所述NAPTR记录的权威域名为管理服务的权威域名，所述第一网元从所述域名服务器获取与所述NAPTR记录的权威域名对应的服务SRV记录的权威域名，以及根据所述SRV记录的权威域名从所述域名服务器获取所述管理服务实例的访问信息。
在一种可能的实现方法中，所述第一网元为开放控制管理功能网元，所述第二网元为管理功能网元；或者，所述第一网元为第一管理功能网元，所述第二网元为第二管理功能网元，所述第二管理功能网元管理的网络资源是第一管理功能网元管理的网络资源的组成部分。
第二方面，本申请提供一种管理服务的发现方法，该方法包括：服务器接收期望的管理能力信息，所述期望的管理能力信息包括管理动作、管理对象的类型、或能力属性中的至少一项；所述服务器根据所述期望的管理能力信息，获取管理服务实例的访问信息，所述管理服务实例与所述期望的管理能力信息匹配；所述服务器发送所述管理服务实例的访问信息。基于该方案，实现了基于第一网元的请求(携带期望的管理能力信息)，向第一网元返回创建的管理对象实例，从而实现了创建管理对象实例的操作。
在一种可能的实现方法中，所述服务器为管理服务仓库功能网元；所述服务器接收期望的管理能力信息，包括：所述服务仓库功能网元接收请求消息，所述请求消息包括所述期望的管理能力信息；所述服务器根据所述期望的管理能力信息，获取管理服务实例的访问信息，所述管理服务实例与所述期望的管理能力信息匹配，包括：所述服务仓库功能网元上配置有至少一个管理服务实例的访问信息与管理能力信息的对应关系，所述服务仓库功能网元根据所述期望的管理能力信息和所述对应关系，获取所述管理服务实例的访问信 息。
在一种可能的实现方法中，所述服务仓库功能网元接收管理对象实例的信息，所述管理对象实例的信息包括管理对象实例和所述管理对象实例与其他管理对象实例之间的关系，所述管理对象实例用于标识所述管理服务实例所管理的网络资源；所述服务仓库功能网元根据所述管理对象实例的信息，更新所述管理服务实例对应的管理能力信息。
在一种可能的实现方法中，所述服务器为域名服务器；所述服务器接收期望的管理能力信息，包括：所述域名服务器接收请求消息，所述请求消息查询域名，所述查询域名是根据所述期望的管理能力信息构造的；所述服务器根据所述期望的管理能力信息，获取管理服务实例的访问信息，包括：所述域名服务器获取与所述查询域名对应的NAPTR记录的权威域名；所述域名服务器获取与所述NAPTR记录的权威域名对应的所述管理服务实例的访问信息。
在一种可能的实现方法中，所述域名服务器获取与所述NAPTR记录的权威域名对应的所述管理服务实例的访问信息，包括：所述NAPTR记录的权威域名为所述管理服务实例的权威域名，所述域名服务器获取与所述管理服务实例的权威域名对应的所述管理服务实例的访问信息；或者，所述NAPTR记录的权威域名为管理服务的权威域名，所述域名服务器获取与所述管理服务的权威域名对应的SRV记录的权威域名，以及根据所述SRV记录的权威域名获取所述管理服务实例的访问信息。
在一种可能的实现方法中，所述域名服务器接收管理对象实例的信息，所述管理对象实例的信息包括管理对象实例和所述管理对象实例与其他管理对象实例之间的关系，所述管理对象实例用于标识所述管理服务实例所管理的网络资源，所述管理对象实例为所述管理服务实例的管理能力范围内的顶级节点；所述服务器根据所述管理对象实例的信息，更新所述管理服务实例对应的NAPTR记录。
第三方面，本申请提供一种管理服务的发现方法，该方法包括：第一网元向域名服务器发送请求消息，所述请求消息包括查询域名，所述查询域名是根据期望的管理能力信息构造的，所述期望的管理能力信息包括管理服务、管理动作、管理对象的类型、或管理对象实例中的至少一个，所述管理对象实例用于标识管理服务实例所管理的网络资源；所述第一网元从所述域名服务器接收与所述查询域名对应的名称权威指针NAPTR记录的权威域名；所述第一网元根据所述NAPTR记录的权威域名，从所述服务器获取所述管理服务实例的访问信息；所述第一网元根据所述管理服务实例的访问信息和所述期望的管理能力信息，向提供所述管理服务的第二网元调用所述管理服务。基于上述方案，当消费者(如第一网元)希望查询提供非创建某类型管理服务实例，就能够按照期望的管理能力信息(其中包括管理对象实例)通过NAPTR记录查询调用管理服务。
在一种可能的实现方法中，所述管理对象为所述管理服务实例的管理能力范围内的顶级节点。
在一种可能的实现方法中，所述第一网元为开放控制管理功能网元，所述第二网元为管理功能网元；或者，所述第一网元为第一管理功能网元，所述第二网元为第二管理功能网元，所述第二管理功能网元管理的网络资源是第一管理功能网元管理的网络资源的组成部分。
第四方面，本申请提供一种管理服务的发现方法，该方法包括：第一网元根据租户的标识，确定所述租户对应的信息对象类，其中，一个信息对象类用于标识一个可创建的网 络资源类型；所述第一网元根据所述租户对应的信息对象类，从服务器获取所述信息对象类对应的可提供的创建类管理服务的信息，所述创建类管理服务的信息包括创建类管理服务名称、创建类管理动作、或能力属性中的至少一个；所述第一网元向所述租户发送第一消息，所述第一消息包括所述租户对应的信息对象类和所述可提供的创建类管理服务的信息。基于上述方案，实现了为向租户提供该租户对应的信息对象类和可提供的创建类管理服务的信息，或者提供租户对应的信息对象类、租户对应的管理对象实例、可提供的管理服务的信息和可提供的创建类管理服务的信息，即提供了该租户的管理能力范围的信息。
在一种可能的实现方法中，所述服务器为域名服务器；所述第一网元根据所述租户对应的信息对象类，从服务器获取所述信息对象类对应的可提供的创建类管理能力信息，包括：所述第一网元向所述域名服务器发送请求消息，所述请求消息包括所述信息对象类，所述请求消息用于请求NAPTR记录；所述第一网元从所述域名服务器接收所述可提供的创建类管理服务的信息。
在一种可能的实现方法中，所述第一网元根据租户的标识，确定所述租户对应的管理对象实例，其中，一个管理对象实例用于标识可被管理的网络资源；所述第一网元根据所述租户对应的管理对象实例，从所述服务器获取所述管理对象实例对应的可提供的管理服务的信息，所述管理服务的信息包括管理服务、或管理动作中的至少一个；所述第一网元向所述租户发送第二消息，所述第二消息包括所述租户对应的管理对象实例和所述可提供的管理服务的信息。
在一种可能的实现方法中，所述服务器为域名服务器；所述第一网元根据所述租户对应的管理对象实例，从所述服务器获取所述管理对象实例对应的可提供的管理服务的信息，包括：所述第一网元向所述域名服务器发送请求消息，所述请求消息包括所述信息对象类，所述请求消息用于请求查询NAPTR记录；所述第一网元从所述域名服务器接收所述可提供的管理服务的信息。
第五方面，本申请提供一种管理服务的发现装置，该装置可以是第一网元，还可以是用于第一网元的芯片。该装置具有实现上述第一方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第六方面，本申请提供一种管理服务的发现装置，该装置可以是服务器，还可以是用于服务器的芯片。该装置具有实现上述第二方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第七方面，本申请提供一种管理服务的发现装置，该装置可以是第一网元，还可以是用于第一网元的芯片。该装置具有实现上述第三方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第八方面，本申请提供一种管理服务的发现装置，该装置可以是第一网元，还可以是用于第一网元的芯片。该装置具有实现上述第四方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第九方面，本申请提供一种管理服务的发现装置，包括：处理器和存储器；该存储器 用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述各方面所述的方法。
第十方面，本申请提供一种管理服务的发现装置，包括：包括用于执行上述各方面的各个步骤的单元或手段(means)。
第十一方面，本申请提供一种管理服务的发现装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行上述各方面所述的方法。该处理器包括一个或多个。
第十二方面，本申请提供一种管理服务的发现装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行上述各方面所述的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
第十三方面，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得处理器执行上述各方面所述的方法。
第十四方面，本申请还提供一种包括指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第十五方面，本申请还提供一种芯片系统，包括：处理器，用于执行上述各方面所述的方法。
第十六方面，本申请还提供一种通信系统，包括：用于执行上述第一方面任意所述的方法的第一网元和用于执行上述第二方面任意所述的方法的服务器。
第十七方面，本申请还提供一种管理服务的发现方法，包括：
第一网元向服务器发送期望的管理能力信息，所述期望的管理能力信息包括管理动作、管理对象的类型、或能力属性中的至少一个；
所述服务器接收所述期望的管理能力信息；
所述服务器根据所述期望的管理能力信息，获取管理服务实例的访问信息，所述管理服务实例与所述期望的管理能力信息匹配；
所述服务器向所述第一网元发送所述管理服务实例的访问信息；
所述第一网元根据所述管理服务实例的访问信息和所述期望的管理能力信息，向第二网元调用管理服务，所述第二网元包括所述管理服务实例；
所述第一网元从所述第二网元接收创建部署信息，所述创建部署信息包括所述管理对象的类型对应管理对象实例，所述管理对象实例用于标识所述管理服务实例所管理的网络资源。
第十八方面，本申请还提供一种管理服务的发现系统，包括：
第一网元，用于：根据期望的管理能力信息，从服务器获取管理服务实例的访问信息，所述管理服务实例与所述期望的管理能力信息匹配，所述期望的管理能力信息包括管理动作、管理对象的类型、或能力属性中的至少一个；根据所述管理服务实例的访问信息和所述期望的管理能力信息，向第二网元调用管理服务，所述第二网元包括所述管理服务实例；从所述第二网元接收创建部署信息，所述创建部署信息包括所述管理对象的类型对应管理对象实例，所述管理对象实例用于标识所述管理服务实例所管理的网络资源；
服务器，用于从所述第一网元接收所述期望的管理能力信息；根据所述期望的管理能力信息，获取所述管理服务实例的访问信息；向所述第一网元发送所述管理服务实例的访问信息。
附图说明
图1A为基于服务化架构的5G网络架构示意图；
图1B为基于点对点接口的5G网络架构示意图；
图2为管理面服务化架构示意图；
图3为管理开放控制架构和应用场景；
图4为管理面服务化架构又一示意图；
图5为本申请提供的一种管理服务的发现方法流程示意图；
图6为本申请提供的又一种管理服务的发现方法流程示意图；
图7为本申请提供的又一种管理服务的发现方法流程示意图；
图8为本申请提供的一种网络结构示意图；
图9为本申请提供的又一种管理服务的发现方法流程示意图；
图10为本申请提供的又一种管理服务的发现方法流程示意图；
图11为管理服务实例的管理范围内的顶级节点MOI和顶级节点标志示意图；
图12为本申请提供的又一种管理服务的发现方法流程示意图；
图13为本申请提供的又一种管理服务的发现方法流程示意图；
图14为本申请提供的又一种管理服务的发现方法流程示意图；
图15为本申请提供的一种管理服务的发现装置示意图；
图16为本申请提供的又一种管理服务的发现装置示意图；
图17为本申请提供的又一种管理服务的发现装置示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。其中，在本申请的描述中，除非另有说明，“多个”的含义是两个或两个以上。
如图1A所示，为基于服务化架构的第五代移动通信(the 5th-generation，5G)网络架构示意图。图1A所示的5G网络架构中可包括三部分，分别是终端设备部分、数据网络(data network，DN)和运营商网络部分。下面对其中的部分网元的功能进行简单介绍说明。
其中，运营商网络可包括以下网元中的一个或多个：网络开放功能(network exposure function，NEF)网元、策略控制功能(policy control function，PCF)网元、统一数据管理(unified data management，UDM)网元、网络仓库功能(network function repository function，NRF)网元、应用功能(application function，AF)网元、认证服务器功能(authentication server function，AUSF)网元、接入与移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、(无线)接入网((radio)access network，(R)AN)以及用户面功能(user plane function，UPF)网元等。上述运营商网络中，除(无线)接入网部分之外的部分可以称为核心网络部分。为方便说明，后续以(R)AN称为RAN为例进行说明。
终端设备，也可以称为用户设备(user equipment，UE)，是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。所述终端设备可以是手机(mobile  phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
上述终端设备可通过运营商网络提供的接口(例如N1等)与运营商网络建立连接，使用运营商网络提供的数据和/或语音等服务。终端设备还可通过运营商网络访问DN，使用DN上部署的运营商业务，和/或第三方提供的业务。其中，上述第三方可为运营商网络和终端设备之外的服务方，可为终端设备提供他数据和/或语音等服务。其中，上述第三方的具体表现形式，具体可根据实际应用场景确定，在此不做限制。
RAN是运营商网络的子网络，是运营商网络中业务节点与终端设备之间的实施系统。终端设备要接入运营商网络，首先是经过RAN，进而可通过RAN与运营商网络的业务节点连接。本申请中的RAN设备，是一种为终端设备提供无线通信功能的设备，RAN设备也称为接入网设备。本申请中的RAN设备包括但不限于：5G中的下一代基站(g nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(baseBand unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。
AMF网元，是由运营商网络提供的控制面网元，负责终端设备接入运营商网络的接入控制和移动性管理，例如包括移动状态管理，分配用户临时身份标识，认证和授权用户等功能。
SMF网元，是由运营商网络提供的控制面网元，负责管理终端设备的协议数据单元(protocol data unit，PDU)会话。PDU会话是一个用于传输PDU的通道，终端设备需要通过PDU会话与DN互相传送PDU。PDU会话由SMF网元负责建立、维护和删除等。SMF网元包括会话管理(如会话建立、修改和释放，包含UPF和AN之间的隧道维护)、UPF网元的选择和控制、业务和会话连续性(Service and Session Continuity，SSC)模式选择、漫游等会话相关的功能。
UPF网元，是由运营商提供的网关，是运营商网络与DN通信的网关。UPF网元包括数据包路由和传输、包检测、业务用量上报、服务质量(Quality of Service,QoS)处理、合法监听、上行包检测、下行数据包存储等用户面相关的功能。
DN，也可以称为分组数据网络(packet data network，PDN)，是位于运营商网络之外的网络，运营商网络可以接入多个DN，DN上可部署多种业务，可为终端设备提供数据和/或语音等服务。例如，DN是某智能工厂的私有网络，智能工厂安装在车间的传感器可为终端设备，DN中部署了传感器的控制服务器，控制服务器可为传感器提供服务。传感器可与控制服务器通信，获取控制服务器的指令，根据指令将采集的传感器数据传送给控制服务器等。又例如，DN是某公司的内部办公网络，该公司员工的手机或者电脑可为终端设备，员工的手机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
UDM网元，是由运营商提供的控制面网元，负责存储运营商网络中签约用户的用户永久标识符(subscriber permanent identifier，SUPI)、信任状(credential)、安全上下文(security  context)、签约数据等信息。UDM网元所存储的这些信息可用于终端设备接入运营商网络的认证和授权。其中，上述运营商网络的签约用户具体可为使用运营商网络提供的业务的用户，例如使用中国电信的手机芯卡的用户，或者使用中国移动的手机芯卡的用户等。上述签约用户的永久签约标识(Subscription Permanent Identifier，SUPI)可为该手机芯卡的号码等。上述签约用户的信任状、安全上下文可为该手机芯卡的加密密钥或者跟该手机芯卡加密相关的信息等存储的小文件，用于认证和/或授权。上述安全上下文可为存储在用户本地终端(例如手机)上的数据(cookie)或者令牌(token)等。上述签约用户的签约数据可为该手机芯卡的配套业务，例如该手机芯卡的流量套餐或者使用网络等。需要说明的是，永久标识符、信任状、安全上下文、认证数据(cookie)、以及令牌等同认证、授权相关的信息，在本发明本申请文件中，为了描述方便起见不做区分、限制。如果不做特殊说明，本申请实施例将以用安全上下文为例进行来描述，但本申请实施例同样适用于其他表述方式的认证、和/或授权信息。
AUSF网元，是由运营商提供的控制面网元，通常可用于一级认证，即终端设备(签约用户)与运营商网络之间的认证。AUSF网元接收到签约用户发起的认证请求之后，可通过UDM网元中存储的认证信息和/或授权信息对签约用户进行认证和/或授权，或者通过UDM网元生成签约用户的认证和/或授权信息。AUSF网元可向签约用户反馈认证信息和/或授权信息。
NEF网元，是由运营商提供控制面网元。NEF网元以安全的方式对第三方开放运营商网络的对外接口。在SMF网元需要与第三方的网元通信时，NEF网元可作为SMF网元与第三方的网元通信的中继。NEF网元作为中继时，可作为签约用户的标识信息的翻译，以及第三方的网元的标识信息的翻译。比如，NEF将签约用户的SUPI从运营商网络发送到第三方时，可以将SUPI翻译成其对应的外部身份标识(identity，ID)。反之，NEF网元将外部ID(第三方的网元ID)发送到运营商网络时，可将其翻译成SUPI。
应用功能(Application Function，AF)网元，主要提供应用层服务，还支持与5G核心网交互来提供服务，例如影响数据路由决策，策略控制功能或者向网络侧提供第三方的一些服务。在具体应用中，AF网元一般是指第三方服务器。
PCF网元，是由运营商提供的控制面功能，用于向网络网元提供策略。作为一种实现方式，策略可以包括接入控制策略、移动性管理策略、计费相关策略、QoS相关策略和授权相关策略等。
NRF网元，可用于提供网元发现功能，基于其他网元的请求，提供网元类型对应的网元信息，如地址信息和/或标识信息等。NRF还提供网元管理服务，如网元注册、更新、去注册以及网元状态订阅和推送等。
图1A中Nnef、Nausf、Npcf、Nudm、Naf、Namf、Nsmf、N1、N2、N3、N4，以及N6为接口序列号。这些接口序列号的含义可参见3GPP标准协议中定义的含义，在此不做限制。
如图1B所示，为基于点对点接口的5G网络架构示意图，其中的网元的功能的介绍可以参考图1A中对应的网元的功能的介绍，不再赘述。图1B与图1A的主要区别在于：图1B中的各个网元之间的接口是点对点的接口，而不是服务化的接口。
在图1B所示的架构中，其中，UE与AMF网元之间的接口称为N1接口，AMF网元 与RAN设备之间的接口称为N2接口，RAN设备与UPF网元之间的接口可以称为N3接口，SMF网元与UPF网元之间的接口称为N4接口，PCF网元与AF网元之间的接口称为N5接口，UPF网元与DN之间的接口称为N6接口，SMF网元与PCF网元之间的接口称为N7接口，AMF网元与UDM网元之间的接口称为N8接口，不同UPF网元之间的接口称为N9接口，UDM网元与SMF网元之间的接口称为N10接口，AMF网元与SMF网元之间的接口称为N11接口，AUSF网元与AMF网元之间的接口称为N12接口，AUSF网元与UDM网元之间的接口称为N13接口，不同AMF网元之间的接口称为N14接口，AMF网元与PCF网元之间的接口称为N15接口。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选的，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
5G网络的网络管理系统采用服务化的架构，在第三代合作伙伴计划(3rd generation partnership project，3GPP)TS 28.533标准规范中，如图2所示，为管理面服务化架构示意图。管理功能(MF)可以作为服务提供者对外提供管理服务(MnS)，也可以作为服务消费者调用其它MF提供的MnS。这里的MF比如可以图1A或图1B所示的AMF、SMF、PCF、UPF、AF、AUSF等，也可以是未来通信如第六代移动通信(the 6th-generation，6G)中的管理功能，本申请不做限定。
对于一个特定的MnS，MF包含了MnS的管理服务实例(MnS Instance)，所述管理服务实例具有提供管理服务访问信息(包括接口(如应用程序编程接口(Application Programming Interface，API)调用接口)、接口访问地址等)。如图3所示，管理功能MF1包含两个管理服务实例，其提供管理服务的接口即为图中所示的小圆圈，每个接口都具有一个接口访问地址，可以使用因特网协议(internet protocol，IP)地址(IPv4或IPv6)、端口号、协议类型来标识，也可以使用统一资源标识(Uniform Resource Identifier，URI)或统一资源定位符(Uniform Resource Locator，URL)来标识。
在3GPP TS 28.533标准规范中，MnS由以下三个部分组成：
1)、管理动作：例如创建、修改、查询、删除、订阅、通知等。
2)、管理对象：管理动作的对象，例如网络功能，网络切片，网络切片子网等。管理对象可以是一类管理对象，即管理对象类(Managed Object Class，MOC)，也可以是管理对象类的一个具体实例，即管理对象实例(MOI)。管理对象的类型定义使用信息对象类(Information Object Class，IOC)来描述，即使用IOC描述MOC。MOI是MOC的一个具体的实例。MOC是可被管理的网络资源的抽象的类定义，而MOI是具体的可被管理的网络资源。
3)、管理数据：例如告警信息或性能统计信息等。只有一部分管理服务涉及管理数据，因此管理数据是可选的。
在一种实现方法中，管理服务MnS可以由管理动作加上管理对象组成。比如管理动作为：分配(allocate)或取消分配(deAllocate)，管理对象为：网络功能(Network Function,NF)，则管理动作加上管理对象构成了网络功能开通部署管理服务(NFProvisioning_ms)；再比如，管理动作为：分配(allocate)或取消分配(deAllocate)，管理对象为：网络切片子网(NetworkSlice Subnet)，则管理动作加上管理对象构成了网络切片子网实例开通部署管理 服务(NSSIProvisioning_ms)。
在又一种实现方法中，管理服务MnS还可以由管理动作加上管理对象、管理数据组成。比如管理动作为：性能上报(performanceReporting)，管理对象为：5G核心网(5GC，5G Core)网络功能，管理数据为：5GC的性能信息，则管理动作加上管理对象，再加上管理了数据构成了网络功能性能上报管理服务(NFPerformanceReporting_ms)。
随着各种通信业务的不断涌现，不同的通信业务对网络性能的需求存在显著的区别，5G网络引入了网络切片(network slice)来满足不同通信业务对网络性能的差异化需求。网络切片是在物理或者虚拟的网络基础设施上，根据不同的服务需求定制化的逻辑网络。网络切片可以是一个包括了终端设备、接入网、传输网、核心网和应用服务器的完整的端到端网络，能够提供完整的通信服务。网络切片经常以网络切片服务(Network Slice as a Service，NSaaS)方式提供给租户，即运营商创建一个网络切片实例(network slice instance，NSI)向第三方(可以是企业、互联网服务提供商，或者另外一个运营商等)提供服务。网络切片实例是运营商为特定租户提供网络切片业务所创建的一个能够真实运行的逻辑网络。一个网络切片实例可以由一到多个子网切片实例(Network Slice Subnet Instance，NSSI)组成，例如可以由无线接入子网切片实例和核心网子网切片实例组成。
因为网络切片实例是相对隔离的逻辑网络，运营商往往根据业务的需要开放一部分管理动作权限给租户。例如网络切片实例的租户是企业或互联网服务提供商时，常常会允许租户获得网络切片实例的某些关键性能指标(Key Performance Indicator，KPI)数据，比如网络切片的端到端时延等。当网络切片实例的租户是另外一个运营商时，除了允许租户获得网络切片实例的某些关键指标外，还常常会允许租户获得网络切片实例的告警信息，甚至允许租户进行某些操作，比如允许修改网络切片实例内某些网络功能的配置，使其能够和租户自身的网络设备对接，以便于在更大范围内提供网络服务。
为了实现上述对租户的管理开放3GPP TS 28.533定义了开放控制管理功能(Exposure Governance Management Function，EGMF)。如图3所示，为管理开放控制架构和应用场景。从图中可以看出，对网络的管理能力是通过调用管理服务MnS实现的。EGMF作为管理开放的控制功能，向第三方(如垂直行业)或另外一个运营商开放一部分网络管理动作权限，检查租户请求的管理动作是否在被允许的范围内。如果网络管理动作被允许，就作为代理调用管理服务，并提供管理动作结果给租户。如图3所示，垂直行业租户通过EGMF1调用MnF1提供的管理服务，另外一个运营商租户的MnF2通过EGMF2调用MnF1提供的管理服务。
在上述场景中，网络内部的管理功能(例如图2中的MF3)，如何根据管理动作的需求，发现其它能够提供期望的管理能力的管理服务实例(例如图2中的MF1或MF2的管理服务实例)。网络外部的第三方行业或其它运营商如何通过管理开放控制功能(图3中的EGMF，如EGMF1、EGMF2)，间接发现能够提供期望的管理能力的管理服务实例(如图3中的MnF1的管理服务实例)，以及获得向其开放的管理能力(即第三方行业或其它运营商被允许的管理动作和相应的操作范围)。这些都是需要解决的问题。
在现有技术中，为了实现管理服务实例的发现引入如图4所示的管理服务仓库功能(MSRF)网元。所有的管理功能都向MSRF注册自身的管理服务实例信息，其中包括管理服务实例的接口访问地址和其管理的网络资源。因为管理服务实例所管理的网络资源使用MOI标识，所以图4中的MF3需要对某个网络资源(例如某个NF)执行管理动作时， 就向MSRF发送查询请求，其中携带所述NF的MOI。MSRF根据所述MOI查询存储的管理服务实例的注册信息，得到管理服务实例的接口访问地址，然后通过响应消息发送给MF3。
通过这种方法，管理服务的消费者能够通过MSRF发现管理MOI标识的网络资源的网络管理服务实例，获得接口访问地址，然后调用管理服务对网络资源执行修改、删除、订阅、通知等管理动作。
上述方案存在的缺陷是：
1)、当需要创建和部署某个网络资源时，如果有多个管理服务实例支持创建和部署网络资源，因为管理对象MOI还没有被创建，使用现有技术无法知道哪个管理服务实例能够满足创建和部署目标网络资源的管理需求。
2)、域名服务器(Domain Name Server，DNS)系统是广泛存在的网络基础设施，URI或URL包含了域名，使用DNS系统将域名和IP地址相互映射起来，但是现有技术没有给出如何利用DNS系统进行管理服务实例的发现。
4)、现有技术也没有给出网络外部的第三方行业或其它运营商如何通过管理开放控制功能间接发现能够提供期望的管理能力的管理服务实例。
综上所述，本申请将要解决以下技术问题：
1)、网络内部的管理功能(例如图2中的MF3)，如何根据管理动作的需求，发现其它能够提供期望的管理能力的管理服务实例(例如图2中的MF1或MF2的管理服务实例)，尤其是如何创建管理服务实例的管理对象实例(即网络资源)。
2)、如何提供DNS提供管理服务实例的发现。
3)、网络外部的第三方行业或其它运营商如何通过管理开放控制功能(图3中的EGMF，如EGMF1、EGMF2)，间接发现能够提供期望的管理能力的管理服务实例(如图3中的MnF1的管理服务实例)，以及获得向其开放的管理能力(即第三方行业或其它运营商被允许的管理动作和相应的操作范围)。
为解决上述问题，本申请提供以下技术方案：
1)、管理服务实例和其管理能力信息注册到MSRF或者以NAPRT记录形式配置到DNS，管理服务消费者根据管理能力信息向DNS或MSRF查询提供创建类管理服务的实例和提供非创建类管理服务的实例。创建类管理服务的管理能力信息包括：支持的管理服务名称、管理动作、管理对象的类型(MOC或IOC)、能力属性中的至少一个。非创建类管理服务的管理能力信息包括：支持的管理服务名称、管理动作、管理对象的类型(MOC或IOC)、管理对象的MOI中的至少一个。
2)、针对管理服务实例和其管理能力信息以NAPRT记录形式配置到DNS的方案，如果新创建的管理对象实例是管理服务实例的管理能力范围内的顶级节点，就为此MOI设置顶级节点标志，同时在DNS中为新增或刷新非创建类管理服务的管理能力信息配置记录，其中配置记录中管理能力信息包括的管理对象的MOI是所述设置顶级节点标志的管理对象实例。
3)、针对管理服务实例和其管理能力信息以NAPRT记录形式配置到DNS的方案，如果管理服务的消费者期望对目标管理对象实例执行非创建类管理动作时，管理服务的消费者以目标MOI为起点向上查找带有顶级节点标志的MOI，然后使用顶级节点标志的MOI构建管理能力信息，向DNS查询管理能力信息对应的管理服务实例。
4)、管理开放控制功能使用第三方行业或其它运营商可管理的管理对象类信息或管理对象实例为标识向DNS或MSRF查询所有管理服务实例能够提供的管理动作，将管理对象类信息或管理对象实例以及对应的能够提供的管理动作组成第三方或其它运营商开放的管理能力范围。
下面结合附图，对上述技术方案进行具体说明。
如图5所示，为本申请提供的一种管理服务的发现方法流程示意图，该方法可用于实现为第一网元提供创建类的管理服务实例的管理对象实例(MOI)，下面对该方案进行具体说明。
如图5所示，该方法包括以下步骤：
步骤501，第一网元根据期望的管理能力信息，从服务器获取管理服务实例的访问信息(如访问地址和API调用接口)，所述管理服务实例与所述期望的管理能力信息匹配，所述期望的管理能力信息包括管理动作、管理对象的类型、或能力属性中的至少一个。
这里的第一网元例如可以是图3中的EGMF(如EGMF1、EGMF2)，或者还可以是5G NF，如图2或图4中的MF1、或MF2、或MF3。
该步骤的具体实现方式为：服务器接收第一网元发送的期望的管理能力信息，服务器根据所述期望的管理能力信息，获取管理服务实例的访问信息，所述管理服务实例与所述期望的管理能力信息匹配，然后服务器向第一网元发送所述管理服务实例的访问信息。
步骤502，第一网元根据管理服务实例的访问信息和期望的管理能力信息，向第二网元调用管理服务，所述第二网元包括所述管理服务实例。
这里的第二网元即为包含有上述管理服务的网元，该管理服务实例的访问信息是第一网元从服务器获取到的，该管理服务实例能够与第一网元发送的期望的管理能力信息相匹配，或者理解为该管理服务实例可以提供该期望的管理能力信息对应的管理能力。
步骤503，第一网元从第二网元接收创建部署信息，创建部署信息包括期望的管理能力信息中的管理对象的类型对应的管理对象实例。
具体的，管理对象实例是可被管理的网络资源，或者理解为，管理对象实例用于标识管理服务实例所管理的网络资源。管理对象实例例如包括网络功能、网络切片实例等。一个网络切片实例被创建和部署后成为可以被管理的一项网络资源。MOI是管理对象类MOC的一个具体实例。管理对象具有一些属性，例如可修改的某些配置项，下一级的管理对象(即成员管理对象)的列表等。MOC会定义管理对象包含哪些属性，MOI会包含这些属性的具体取值。MOC的描述形式是对象类信息(IOC)，一系列IOC的集合构成了网络资源模型(Network Resource Modeling，NRM)。管理信息数据库(Management Information Base，MIB)是NRM的一个实例，存储了一系列MOI，以及MOI的属性和相互关联关系。
即第一网元通过调用第一网元的上述管理服务，使得上述管理服务实例创建管理对象实例(即网络资源)，并将管理对象实例携带于创建部署信息中发送至第一网元，从而第一网元可以从第二网元获取到管理对象实例。
上述实施例中，在一种实现方法中，第一网元为EGMF网元，第二网元为MF网元。
在又一种实现方法中，第一网元为第一MF网元，第二网元为第二MF网元，其第二MF网元管理的网络资源是第一MF网元管理的网络资源的组成部分，这里的网络资源是通过管理对象实例(MOI)标识的。
基于图5所示的实施例，实现了基于第一网元的请求(携带期望的管理能力信息)， 向第一网元返回创建的管理对象实例，从而实现了创建管理对象实例的操作。
针对图5实施例，其中的服务器可以是MSRF网元，也可以DNS。下面分别说明。
一、服务器为MSRF网元
当服务器为MSRF时，则管理功能包含的管理服务实例可以预先将自身的管理服务访问地址和管理能力信息注册到MSRF，其中管理服务实例的管理能力信息包括其支持的以下一项或多项：管理服务名称，管理动作，管理对象的类型信息，能力属性。即MSRF网元上配置有至少一个管理服务实例的访问信息与管理能力信息的对应关系。
因此，上述步骤501的具体实现方式为：第一网元向MSRF网元发送请求消息，所述请求消息包括期望的管理能力信息，然后MSRF网元根据期望的管理能和上述对应关系，获取管理服务实例的访问信息，然后MSRF网元向第一网元发送管理服务实例的访问信息。
进一步地，第二网元在创建了管理对象实例之后，还可以将管理对象实例的信息发送至MSRF网元，所述管理对象实例的信息包括管理对象实例和所述管理对象实例与其他管理对象实例之间的关系，所述管理对象实例用于标识所述管理服务实例所管理的网络资源；然后，MSRF网元根据管理对象实例的信息，更新管理服务实例对应的管理能力信息，比如将管理对象实例以及该管理对象实例与其他管理对象实例之间的关系更新至该管理对象实例对应的管理能力信息中。
二、服务器为DNS
当服务器为DNS时，则可以预先在DNS中配置管理服务实例的域名和访问信息，例如以A记录(即DNS定义的域名到IPv4地址的映射)或AAAA记录(即DNS定义的域名到IPv6地址的映射)。
在DNS中配置管理服务实例能够提供的管理服务和管理能力信息，其中管理服务实例的管理能力信息包括其支持的以下一项或多项：管理服务名称，管理动作，管理对象的类型信息，管理对象实例，能力属性。将管理服务实例的域名和提供的管理服务以SRV(service)记录(包含DNS定义的服务器域名和服务器提供的服务)配置到DNS中。
将管理服务实例的提供的管理服务和相应的管理能力信息以权威指针(Name Authority Pointer，NAPTR)记录配置到DNS，从而完成一个查询域名到权威域名的解析。即将一个字符串映射到另外一个字符串，完成域名重写。将管理服务实例的管理能力信息中的一项或多项构造形成查询域名，将管理服务实例提供的管理服务或管理服务实例的域名作为权威域名，同时配置正则表达式或替换规则，将查询域名中管理能力信息的一项或多项经过正则表达式或替换处理后，能够映射到管理服务或管理服务实例的权威域名。
通过上述配置，如果消费者希望查询提供创建某类型管理服务实例，就能够按照期望的管理能力信息通过NAPTR记录查询到管理服务或管理服务实例。进一步通过SRV记录、A记录或AAAA记录查询得到提供期望的管理能力的管理服务实例的接口信息。
因此，上述步骤501的具体实现方式为：第一网元向DNS发送请求消息，所述请求消息包括查询域名，所述查询域名是根据期望的管理能力信息构造的；DNS获取与所述查询域名对应的NAPTR记录的权威域名；然后，DNS获取与所述NAPTR记录的权威域名对应的所述管理服务实例的访问信息，然后向第一网元发送管理服务实例的访问信息。
其中，第一网元根据NAPTR记录的权威域名，从DNS获取管理服务实例的访问信息可以有以下两种方法：
方法一，NAPTR记录的第一权威域名为管理服务实例的权威域名，则第一网元从DNS 获取与NAPTR记录的权威域名对应的访问信息。
即第一网元获取到NAPTR记录的权威域名之后，可以直接根据该NAPTR记录的权威域名，获取到A记录或AAA记录中相对应的访问信息。
方法二，NAPTR记录的权威域名为管理服务的权威域名，则第一网元从DNS获取与NAPTR记录的权威域名对应的SRV记录的权威域名，以及根据SRV记录的权威域名从DNS获取访问信息。
即第一网元获取到NAPTR记录的权威域名之后，先根据该NAPTR记录的权威域名，获取到SRV记录的权威域名，然后根据该SRV记录的权威域名，从A记录或AAA记录中获取相对应的访问信息。
进一步地，第二网元在创建了管理对象实例之后，还可以将管理对象实例的信息发送至DNS，然后DNS根据所述管理对象实例的信息，更新所述管理服务实例对应的NAPTR记录。其中，所述管理对象实例的信息包括管理对象实例和所述管理对象实例与其他管理对象实例之间的关系，所述管理对象实例用于标识所述管理服务实例所管理的网络资源，所述管理对象实例为所述管理服务实例的管理能力范围内的顶级节点。
如图6所示，为本申请提供的又一种管理服务的发现方法流程示意图，该方法可用于实现为第一网元提供非创建类的管理服务实例的调用，且以服务器为DNS为例进行说明，下面对该方案进行具体说明。
如图6所示，该方法包括以下步骤：
步骤601，第一网元向DNS发送请求消息，所述请求消息包括查询域名，所述查询域名是根据期望的管理能力信息构造的，所述期望的管理能力信息包括管理服务、管理动作、管理对象的类型、或管理对象实例中的至少一个，所述管理对象实例用于标识管理服务实例所管理的网络资源。
步骤602，DNS获取与查询域名对应的NAPTR记录的权威域名。
步骤603，DNS向第一网元发送与查询域名对应的NAPTR记录的权威域名。
步骤604，第一网元根据NAPTR记录的权威域名，从DNS获取管理服务实例的访问信息。
步骤605，第一网元根据管理服务实例的访问信息和期望的管理能力信息，向提供管理服务的第二网元调用所述管理服务。
在一种实现方法中，上述管理对象为上述管理服务实例的管理能力范围内的顶级节点。
上述实施例中，在一种实现方法中，第一网元为EGMF网元，第二网元为MF网元。
在又一种实现方法中，第一网元为第一MF网元，第二网元为第二MF网元，其第二MF网元管理的网络资源是第一MF网元管理的网络资源的组成部分，这里的网络资源是通过管理对象实例(MOI)标识的。
基于上述方案，当消费者(如第一网元)希望查询提供非创建某类型管理服务实例，就能够按照期望的管理能力信息(其中包括管理对象实例)通过NAPTR记录查询到管理服务或管理服务实例。进一步通过SRV记录、A记录或AAAA记录查询得到提供期望的管理能力的管理服务实例的接口信息。
如图7所示，为本申请提供的又一种管理服务的发现方法流程示意图，该方法可实现租户(如外部运营商或第三方垂直行业)可以查询自身被授权的管理能力的范围，即租户允许管理哪些网络资源，允许执行什么操作等。下面对该方案进行具体说明。
如图7所示，该方法包括以下步骤：
步骤701，第一网元根据租户的标识，确定所述租户对应的信息对象类，其中，一个信息对象类用于标识一个可创建的网络资源类型。
步骤702，第一网元根据租户对应的信息对象类，从服务器获取所述信息对象类对应的可提供的创建类管理服务的信息，所述创建类管理服务的信息包括创建类管理服务名称、创建类管理动作、或能力属性中的至少一个。
步骤703，第一网元向所述租户发送第一消息，所述第一消息包括所述租户对应的信息对象类和所述可提供的创建类管理服务的信息。
进一步地，在上述步骤703之后，还可以包括以下步骤704-步骤706。
步骤704，第一网元根据租户的标识，确定所述租户对应的管理对象实例，其中，一个管理对象实例用于标识可被管理的网络资源。
步骤705，第一网元根据所述租户对应的管理对象实例，从服务器获取所述管理对象实例对应的可提供的管理服务的信息，所述管理服务的信息包括管理服务、或管理动作中的至少一个。
步骤706，第一网元向所述租户发送第二消息，所述第二消息包括所述租户对应的管理对象实例和所述可提供的管理服务的信息。
基于上述方案，实现了为向租户提供该租户对应的信息对象类和可提供的创建类管理服务的信息，或者提供租户对应的信息对象类、租户对应的管理对象实例、可提供的管理服务的信息和可提供的创建类管理服务的信息，即提供了该租户的管理能力范围的信息。
需要说明的是，在具体实现中，上述步骤701和步骤704可以合并为一个步骤，步骤702和步骤705可以合并为一个步骤，步骤703和步骤706可以合并为一个步骤。
其中，上述服务器可以是MSRF网元或DNS。其中，当服务器为DNS时，则上述步骤702具体实现为：第一网元向DNS发送请求消息，所述请求消息包括所述信息对象类，所述请求消息用于请求NAPTR记录；第一网元从DNS接收所述可提供的创建类管理服务的信息。当服务器为DNS时，则上述步骤705具体实现为：第一网元向DNS发送请求消息，所述请求消息包括所述信息对象类，所述请求消息用于请求查询NAPTR记录；第一网元从DNS接收所述可提供的管理服务的信息。
下面结合具体实施例，对上述图5-图7的实施例分别进行具体描述。
如图8所示，为本申请提供的一种网络结构示意图。下面以该图为例进行说明。图8所示的网络中有两个网络切片管理功能(Network Slice Management Function，NSMF)，分别能够管理不同类型的网络切片，例如NSMF1可以创建和管理增强的移动宽带(enhanced Mobile Broad Band，eMBB)和海量机器类型连接(massive Machine Type Connection，mMTC)类型的网络切片，NSMF2可以创建和管理超高可靠性超低时延连接(ultraReliability and Low Latency Connection，uRLLC)类型的网络切片。图8所示的网络中还有两个子网切片管理功能(Network Slice Subnet Management Function，NSSMF)，其中NSSMF1可以在网络区域A内创建和管理子网切片和网络功能，NSSMF2可以在网络区域B内创建和管理子网切片和网络功能。第三方垂直行业或其它运营商向EGMF发送管理请求，例如创建网络切片实例，获得网络切片的性能统计数据等。EGMF根据请求的网络管理通过MSRF或DNS发现能够提供所需管理服务的管理功能(即管理服务实例)，例如图8中的NSMF2，然后EGMF作为管理服务的消费者调用NSMF2提供的管理服务。在上述过程中，如果 NSMF2需要进一步调用其它网络功能提供的管理服务才能完成请求的管理服务，NSMF2就根据所需的网络管理通过MSRF或DNS发现能够提供所需管理服务的管理服务实例，例如图8中的NSSMF2。最后NSMF2调用NSSMF2提供的管理服务。
在图8所示的网络中，其它运营商请求在网络区域B创建一个uRLLC的网络切片，则系统流程如图9所示，其中服务器为MSRF网元。图9实施例是图5实施例的一个具体应用。其中，图9实施例的EGMF、NSMF2和MSRF可以分别看做图5实施例的第一网元、第二网元和服务器，以及，图9实施例的NSMF2、NSSMF2和MSRF也可以分别看做图5实施例的第一网元、第二网元和服务器。
该流程包括以下步骤：
步骤900：管理功能包含的管理服务实例将自身的管理服务访问地址和管理能力信息注册到MSRF。其中管理服务实例的管理能力信息包括其支持的以下一项或多项：管理服务名称，管理动作，管理对象的类型信息，能力属性。
具体的，管理服务名称可以为3GPP TS 28.531和TS 28.532中定义的管理服务的标准名称，例如NSMF1和NSMF2支持的管理服务名称可以为Provisioning for NSI和Provisioning data report for NSI等。
具体的，管理动作可以为3GPP TS 28.531和TS 28.532定义的操作或通知，例如allocateNSI、createMOI、订阅(subscribe)、notifyNewAlarm等。
具体的，管理对象的类型信息是管理动作操作的管理对象的类型，可以为管理对象类MOC或者信息对象类IOC，例如NSMF1和NSMF2支持管理对象的类型为3GPP TS 28.541中定义的NetworkSlice，NSSMF1和NSSMF2支持的为NetworkSliceSubnet等。
具体的，能力属性是描述管理需求的参数，例如网络切片、子网切片或网络功能的类型需求参数，性能需求参数，范围参数等等。能力属性可以是TS 28.541定义的ServiceProfile或SliceProfile中的网络切片和业务类型sST、网络切片覆盖区域coverageAreaTAList、时延latency、终端移动级别uEMobilityLevel，等等。例如图5中的NSMF2将支持的uRLLC切片类型作为能力属性注册到MSRF，NSSMF2将支持的区域B对应的跟踪区(Tracking Area，TA)列表作为能力属性注册到MSRF。
步骤901：某外部运营商请求在区域B创建部署一个uRLLC类型的网络切片实例，创建网络切片请求消息发送到本运营商的开放控制管理功能(EGMF)，消息中携带了期望的管理动作(即创建部署网络切片实例)、管理对象的类型(即网络切片)、期望的对象属性(即uRLLC类型和覆盖区域B)。
步骤902：EGMF检查外部运营商的管理权限，根据双方事先签订的协议，确认允许外部运营商创建网络切片实例，于是授权执行请求的操作。
步骤903：EGMF根据请求消息中携带的期望的管理能力信息，也就是期望的管理动作(即创建部署网络切片实例)、管理对象的类型(即网络切片)、期望的对象属性(例如uRLLC切片类型)，向MSRF查询能够满足期望管理能力的管理服务和访问地址，即管理服务实例提供的管理服务和接口。MSRF查询步骤900各个管理服务实例注册的信息，确定NSMF2注册的管理能力信息和查询消息中携带的期望的管理能力信息匹配，就将NSMF2的管理服务和访问地址作为响应消息发送给EGMF。
步骤904：EGMF调用NSMF2提供的分配网络切片的管理服务，其中携带了从步骤901中收到的期望的管理动作(即创建部署网络切片实例)、管理对象的类型(即网络切片)、 期望的对象属性(即uRLLC类型和覆盖区域B)。
步骤905：NSMF2根据TS 28.531定义的处理过程，将创建网络切片的请求分解为子网切片的创建需求，例如在覆盖区域B创建子网切片实例。
步骤906：NSMF2根据分解后的子网切片的创建需求构造期望的管理能力信息，即期望的管理动作(即创建部署子网切片实例)、管理对象的类型(即子网切片)、期望的对象属性(即coverageAreaTAList为区域B)，向MSRF查询能够满足期望管理能力的管理服务和访问地址。MSRF查询步骤0各个管理服务实例注册的信息，确定NSSMF2注册的管理能力信息和查询消息中携带的期望的管理能力信息匹配，就将NSSMF2的管理服务和访问地址作为响应消息发送给NSMF2。
步骤907：NSMF2调用NSSMF2提供的分配子网切片的管理服务，其中携带了分解的子网切片的创建需求。
步骤908：NSSMF2按照TS 28.531定义的处理创建部署子网切片实例，以及为新创建的子网切片实例创建MOI并进行配置，比如将新创建子网切片实例的标识作为属性配置到MOI中。
步骤909：(该步骤可选)NSSMF2可以将新创建的子网切片实例的MOI作为管理能力信息中的管理对象实例部分对自身在MSRF的注册信息进行更新，具体的操作类似步骤900。
步骤910：NSSMF2将子网切片实例的创建结果发送给NSMF2，其中包括新创建子网切片的MOI。
步骤911：如果根据步骤905分解后的需求，NSMF2还需要创建其它子网切片，就继续按照上述步骤906至步骤910的方法完成网络切片实例包含的所有子网切片实例的创建。
步骤912：NSMF2在完成所有子网切片创建部署后，就创建和配置网络切片实例的MOI，比如将新创建网络切片实例的标识作为属性配置到MOI中。
步骤913：(该步骤可选)NSMF2可以将新创建的网络切片实例的MOI作为管理能力信息中的管理对象实例部分对自身在MSRF的注册信息进行更新，具体的操作类似步骤900。
步骤914：NSMF2将网络切片实例的创建部署结果发送给EGMF，其中携带了新创建网络切片实例的MOI。
步骤915：EGMF将创建网络切片实例的结果通过创建网络切片响应消息发送给外部运营商，其中携带新创建网络切片实例的标识。
基于上述实施例，网络内部的管理功能能够发现满足期望的管理能力信息的创建类管理服务和访问地址，外部的行业或其它运营商也都能够通过管理开放控制功能间接发现满足期望的管理能力信息的创建类管理服务和访问地址。相比现有技术，该实施例的方案能够在多个支持创建操作的管理服务实例中发现满足期望管理能力信息的一个管理服务实例。
在图8所示的网络中，其它运营商请求在网络区域B创建一个uRLLC的网络切片，则系统流程如图10所示，其中服务器为DNS。图10实施例是图5实施例的一个具体应用。其中，图10实施例的EGMF、NSMF2和DNS可以分别看做图5实施例的第一网元、第二网元和服务器，以及，图10实施例的NSMF2、NSSMF2和DNS也可以分别看做图5实施例的第一网元、第二网元和服务器。
该流程包括以下步骤：
步骤1000：在DNS中配置管理服务实例的域名和访问地址，例如以A记录(即DNS定义的域名到IPv4地址的映射)或AAAA记录(即DNS定义的域名到IPv6地址的映射)。例如将NSMF1包含的管理服务实例的权威域名(比如nsmf1.plmn1)和访问地址(比如IPv4地址100.100.100.100)以A记录形式配置到DNS中。
在DNS中配置管理服务实例能够提供的管理服务和管理能力信息，其中管理服务实例的管理能力信息包括其支持的以下一项或多项：管理服务名称，管理动作，管理对象的类型信息，管理对象实例，能力属性。管理能力信息各项的具体内容同图9实施例中的描述。将管理服务实例的域名和提供的管理服务以SRV记录(包含DNS定义的服务器域名和服务器提供的服务)配置到DNS中。例如NSMF1(权威域名为nsmf1.plmn1)支持Provisioning for NSI管理服务，SRV记录可以为_nsmf1.plmn1._ProvisioningforNSI。使用下划线(_)开头的目的是为了防止和日常自然配置的其它DNS标签冲突。将管理服务实例的提供的管理服务和相应的管理能力信息以NAPTR记录配置到DNS。NAPTR代表名称权威指针(Name Authority Pointer，参见RFC2915)，完成一个查询域名到权威域名的解析。即将一个字符串映射到另外一个字符串，完成域名重写。将管理服务实例的管理能力信息中的一项或多项构造形成查询域名，将管理服务实例提供的管理服务或管理服务实例的域名作为权威域名，同时配置正则表达式或替换规则，将查询域名中管理能力信息的一项或多项经过正则表达式或替换处理后，能够映射到管理服务或管理服务实例的权威域名。例如NSMF1支持创建eMBB类型的网络切片，即NSMF1管理能力信息包括：管理动作(allocateNSI)，管理对象的类型信息(NetworkSlice)，能力属性(sST＝eMBB)，配置到DNS中NAPTR记录的查询域名可以为_allocateNSI._NetworkSlice._eMBB，对应的权威域名可以为_nsmf1.plmn1._ProvisioningforNSI，正则表达式可以为匹配查询域名中的任意一段。再例如NSSMF1(域名为nssmf1.plmn1)支持在区域A创建子网切片实例，即NSSMF1管理能力信息包括：管理对象的类型信息(NetworkSliceSubnet)，能力属性(coverageAreaTAList＝TAI-A)，配置到DNS中NAPTR记录的查询域名可以为_NetworkSliceSubnet._TAI-A，对应的权威域名可以为_nssmf1.plmn1._ProvisioningforNSSI，正则表达式可以为匹配查询域名中的最后一段和其它任意一段。
通过上述配置，如果消费者希望查询提供创建某类型网络切片的管理服务实例，就能够按照期望的管理能力信息通过NAPTR记录查询到管理服务或管理服务实例。进一步通过SRV记录、A记录或AAAA记录查询得到提供期望的管理能力的管理服务实例的接口信息。
步骤1001：某外部运营商请求在区域B创建部署一个uRLLC类型的网络切片实例，创建网络切片请求消息发送到本运营商的开放控制管理功能EGMF，消息中携带了期望的管理动作(即创建部署网络切片实例)、管理对象的类型(即网络切片)、期望的对象属性(即uRLLC类型和覆盖区域B)。
步骤1002：EGMF检查外部运营商的管理权限，根据双方事先签订的协议，确认允许外部运营商创建网络切片实例，于是授权执行请求的操作。
步骤1003：EGMF根据请求消息中携带的期望的管理能力信息，也就是期望的管理动作(即创建部署网络切片实例)、管理对象的类型(即网络切片)、期望的对象属性(例如uRLLC切片类型和覆盖区域B)，向DNS查询能够满足期望管理能力的管理服务或管理服 务实例。具体的，EGMF用上述期望的管理动作构造出查询域名_allocateNSI._NetworkSlice._uRLLC._TAI-B，然后向DNS发送NAPTR查询请求。
DNS查询步骤1000配置的相关记录，通过正则表达式或替换，确定步骤1000中为NSMF2配置的NAPTR记录可以和查询请求匹配，例如查询域名_allocateNSI._NetworkSlice._uRLLC._TAI-B包含了NAPTR记录中的_allocateNSI._NetworkSlice._uRLLC，即NSMF2的管理能力信息和查询消息中携带的期望的管理能力信息匹配，就将NSMF2的管理服务实例的权威域名nsmf2.plmn1作为响应消息发送给EGMF，其中响应消息的标志设置为A，即下一步根据响应消息得到的权威域名可以执行A查询获得访问地址。在另一种可能的实现方式中，如果步骤1000设置的NAPTR记录中权威域名是NSMF2提供的管理服务_nsmf2.plmn1._ProvisioningforNSI，则响应消息的标志设置为S，即下一步根据响应消息得到的权威域名可以执行SRV查询获得NSMF2的管理服务实例的权威域名nsmf2.plmn1,然后再执行A查询获得访问地址，现有的DNS系统也是支持的，本实施例不再赘述。
步骤1004：EGMF使用NSMF2的管理服务实例的权威域名查询DNS获得管理服务实例的访问地址，即访问管理服务接口的IP地址和端口信息。
步骤1005：EGMF调用NSMF2提供的分配网络切片的管理服务，其中携带了从步骤1中收到的期望的管理动作(即创建部署网络切片实例)、管理对象的类型(即网络切片)、期望的对象属性(即uRLLC类型和覆盖区域B)。
步骤1006：NSMF2根据TS 28.531定义的处理过程，将创建网络切片的请求分解为子网切片的创建需求，例如在覆盖区域B创建子网切片实例。
步骤1007：NSMF2根据分解后的子网切片的创建需求构造期望的管理能力信息，即期望的管理动作(即创建部署子网切片实例)、管理对象的类型(即子网切片)、期望的对象属性(即coverageAreaTAList为区域B)，向DNS查询能够满足期望管理能力的管理服务或管理服务实例。具体的，类似步骤1003，NSMF2用上述期望的管理动作构造出查询域名_allocateNSSI._NetworkSliceSubnet._TAI-B，然后向DNS发送NAPTR查询请求。
DNS查询步骤1000配置的相关记录，确定为NSSMF2配置的NAPTR记录可以和查询请求匹配(即根据正则表达式运算_allocateNSSI._NetworkSliceSubnet._TAI-B包含_NetworkSliceSubnet._TAI-B)，就将NSSMF2的管理服务实例的权威域名nssmf2.plmn1作为响应消息发送给NSMF，其中响应消息的标志设置为A。
步骤1008：NSMF2使用NSSMF2的管理服务实例的权威域名查询DNS获得管理服务实例的访问地址。
步骤1009：NSMF2调用NSSMF2提供的分配子网切片的管理服务，其中携带了分解的子网切片的创建需求。
步骤1010：NSSMF2按照TS 28.531定义的处理创建部署子网切片实例，以及为新创建的子网切片实例创建MOI并进行配置，比如将新创建子网切片实例的标识作为属性配置到MOI中。
步骤1011-1(该步骤可选)：如果新创建MOI是管理服务实例的管理能力范围内的顶级节点，就在新创建的MOI上设置顶级节点标志。
如图11所示，为管理服务实例的管理范围内的顶级节点MOI和顶级节点标志示意图。如果管理服务实例是NSMF，那么它的管理范围包括整个网络切片实例，因此NSMF新创 建的网络实例(如图中的NSI#A和NSI#B)的MOI就会被NSMF设置顶级节点标志。同样道理，图11中的子网切片实例NSSI#1、NSSI#2、NSSI#3等的MOI就会被NSSMF设置顶级节点标志。因为图11中管理服务实例同时具备NSSMF和NFMF的功能，因此NF#1等网络功能不是管理服务实例管理范围内的顶级节点，因此没有被设置顶级节点标志。
步骤1011-2(该步骤可选)：如果新创建MOI被设置了顶级节点标志，那么可以将该MOI作为一部分管理能力信息，更新管理服务实例的管理能力信息，并用新的管理能力信息更新步骤0在DNS中配置的NAPTR记录。例如NSSMF2的管理能力信息对应的查询域名原来为_NetworkSliceSubnet._TAI-B，现在更新为_NetworkSliceSubnet._TAI-B._NSSI-1，或者新增一条NAPTR记录，查询域名为_NetworkSliceSubnet._NSSI-1，权威域名为NSSMF2的域名。这样，后续使用网络切片子网NSSI#1的MOI构造的查询域名_NSSI-1也能够查到管理NSSI#1的NSSMF2。
步骤1012：NSSMF2将子网切片实例的创建结果发送给NSMF2，其中包括新创建子网切片的MOI。
步骤1013：如果根据步骤1005分解后的需求，NSMF2还需要创建其它子网切片，就继续按照上述步骤1006至1012的方法完成网络切片实例包含的所有子网切片实例的创建。
步骤1014：NSMF2在完成所有子网切片创建部署后，就创建和配置网络切片实例的MOI，比如将新创建网络切片实例的标识作为属性配置到MOI中。
步骤1015(该步骤可选)：可以将新创建的网络切片实例的MOI作为NSMF2管理能力信息中的一部分，并更新或新增DNS中的配置，使得后续可以通过新创建网络切片实例的MOI查询到NSMF2，方法类似步骤1011-1和步骤1011-2。
步骤1016：NSMF2将网络切片实例的创建部署结果发送给EGMF，其中携带了新创建网络切片实例的MOI。
步骤1017：EGMF将创建网络切片实例的结果通过创建网络切片响应消息发送给外部运营商，其中携带新创建网络切片实例的标识。
基于该实施例，网络内部的管理功能能够发现满足期望的管理能力信息的创建类管理服务和访问地址，外部的行业或其它运营商也都能够通过管理开放控制功能间接发现满足期望的管理能力信息的创建类管理服务和访问地址。相比现有技术，该实施例的方案能够在多个支持创建操作的管理服务实例中发现满足期望管理能力信息的一个管理服务实例。进一步地还能够兼容现有的DNS系统，不需要新增MSRF实体，进一步降低系统的成本。
通过图9或图10实施例，可以创建管理服务实施例的管理对象实例，进而后续可以直接使用该管理对象实例。下面基于图10实施例，进一步地介绍外部运营商请求获得为其创建的网络切片实例的性能统计数据时，使用DNS来进行管理服务和管理能力发现时的处理流程。
如图12所示，为本申请提供的又一种管理服务的发现方法流程图，图12实施例是图6所示实施例的一个具体示例。其中，图12实施例的EGMF、NSMF2和DNS可以分别看做图6实施例的第一网元、第二网元和服务器，以及，图12实施例的NSMF2、NSSMF2和DNS也可以分别看做图6实施例的第一网元、第二网元和服务器。
基于图11的网络架构的示例，该方法包括以下步骤：
步骤1201：某外部运营商请求获得网络切片实例NSI#B的性能统计数据，向EGMF发送订阅网络切片性能统计的请求消息，其中携带了NSI#B的IOC(即NetworkSlice)和 MOI(该MOI是非顶级节点的MOI或顶级节点的MOI，该MOI即NSI-B)。
步骤1202：EGMF检查外部运营商的管理权限，根据双方事先签订的协议，确认允许外部运营商获得NSI#B的性能数据，于是授权执行请求的操作。
步骤1203：EGMF根据请求消息中携带的期望的管理能力信息，也就是期望的管理服务(即performance assurance management service)、管理动作(即订阅)、管理对象的类型(即网络切片)、管理对象的MOI(即NSI-B)中的一个或多个，向DNS查询能够满足期望管理能力的管理服务或管理服务实例。具体的，EGMF用上述期望的管理动作构造出查询域名_subscribe._NetworkSlice._NSI-B，然后向DNS发送NAPTR查询请求。
DNS查询更新或配置的相关记录，通过正则表达式或替换，确定为NSMF2配置的NAPTR记录可以和查询请求匹配，就将NSMF2的管理服务实例的权威域名nsmf2.plmn1作为响应消息发送给EGMF，其中响应消息的标志设置为A，即下一步根据响应消息得到的权威域名可以执行A查询获得访问地址。
步骤1204：EGMF使用NSMF2的管理服务实例的权威域名查询DNS获得管理服务实例的访问地址，即访问管理服务接口的IP地址和端口信息。
步骤1205：EGMF调用NSMF2提供的性能统计管理服务，其中携带了从步骤1中收到的期望的管理动作(即订阅性能统计数据)、管理对象的类型(即网络切片)、期望的对象属性(即NSI-B)。
步骤1206：NSMF2根据TS 28.550定义的处理过程，确定需要收集的子网切片或网络功能的性能数据，分解为子性能统计任务，例如收集图11中NSSI#3和NF#4的性能统计数据。
步骤1207a：对于NSSI#3这样带有顶级节点标志的MOI，NSMF2根据分解后的子任务构造期望的管理能力信息，即期望的管理动作(订阅性能统计)、管理对象的类型(即子网络切片)、管理对象MOI(即NSSI-3)，向DNS查询能够满足期望管理能力的管理服务或管理服务实例。具体的，类似步骤1203，NSMF2用上述期望的管理动作构造出查询域名_subscribe._NetworkSliceSubnet._NSSI-3，然后向DNS发送NAPTR查询请求。DNS根据实施例二中更新或配置的相关记录，确定为NSSMF2配置的NAPTR记录可以和查询请求匹配，就将NSSMF2的管理服务实例的权威域名nssmf2.plmn1作为响应消息发送给NSMF2。
步骤1207b-1：对于NF#4这样没有顶级节点标志的MOI，NSMF2以目标MOI为起点向上查找第一个带有顶级标志的上级MOI。例如图11中从NF#4向上查找到的第一个带有顶级标志的MOI是NSSI-3。
步骤1207b-2：NSMF2使用管理能力范围顶层MOI来构造DNS查询消息，具体方法同步骤1207a。查询得到的能够管理NSSI-3的管理服务实例NSSMF2的管理能力范围包含了目标MOI(即NF#4)，因此后续可以向NSSMF2请求订阅NF#4的性能统计数据。
步骤1208：NSMF2使用NSSMF2的管理服务实例的权威域名查询DNS获得管理服务实例的访问地址。
步骤1209：NSMF2调用NSSMF2提供的子网切片性能数据订阅服务和网络功能性能数据订阅服务，完成性能统计子任务的创建。
步骤1210：所以子任务创建成功后，NSMF2创建NSI#B的性能统计任务，并向EGMF返回性能统计订阅响应消息，其中携带了新创建的性能统计任务的标识。
步骤1211：EGMF将订阅响应消息发送给外部运营商。
基于该实施例，将管理对象作为管理能力信息的一部分进行DNS查询，获得能够支持对管理对象进行非创建类操作的管理服务实例。通过转换目标MOI到管理范围顶层MOI，可以实现只有层级MOI的变化才需要同步到DNS，其它MOI变化不影响DNS配置。这样可以大大减少DNS配置记录的数量，也避免DNS记录配置频繁更新。
如图13所示，为本申请提供的又一种管理服务的发现方法流程图，图13实施例是图7所示实施例的一个具体示例。其中，图13实施例的其它运营商、EGMF和MSRF可以分别看做图7实施例的租户、第一网元和服务器。
外部运营商或第三方垂直行业往往需要查询自身被授权的管理能力的范围，也就是运营商或第三方允许管理哪些网络资源，允许执行什么操作等等。下面以外部运营商通过开放管理功能请求获得自身的管理能力范围的流程为例进行说明。
该方法包括以下步骤：
步骤1301：某外部运营商向EGMF发送请求消息，请求查询被授权的管理能力范围，请求消息中携带租户标识。其中租户标识是对外提供网络开放的运营商对第三方垂直行业或其它运营商租户的一个标识。
步骤1302：EGMF检查和确定租户标识，然后根据双方事先签订的协议确定租户的管理权限。具体的，确定租户可以创建的网络资源类型的信息，即租户可管理的IOC或其列表；以及确定租户可以管理的网络资源，即管理对象MOI或其列表。
步骤1303：EGMF以步骤1302获得的某IOC或IOC列表向MRSF查询管理服务实例的注册信息，获得所有可用状态的管理服务实例对目标IOC可以提供的创建类管理服务名称，创建类管理动作(可选)，以及能力属性(可选)。EGMF得到对上述IOC列表中每个IOC可以提供的创建类管理服务名称，创建类管理动作，以及能力属性。
步骤1304：EGMF以步骤1302获得的某MOI或MOI列表向MRSF查询管理服务实例的注册信息，获得所有可用状态的管理服务实例对目标MOI可以提供的管理服务名称，管理动作(可选)。EGMF得到对上述MOI列表中每个MOI可以提供的管理服务名称，管理动作(可选)。
步骤1305：EGMF汇总步骤1303和1304得到的结果，查询得到的{可创建的IOC，一到多个创建类管理服务名称，一到多个创建类管理动作(可选)，能力属性(可选)}和/或{可管理的MOI，允许的一到多个管理服务名称，允许的一到多个管理动作(可选)}组成的列表作为租户管理能力范围。
步骤1306：EGMF将步骤1305获得的租户管理能力范围作为查询结果响应发送给外部运营商。这样外部运营商就可以知道允许管理哪些网络资源，允许执行什么操作等等。
基于上述实施例，第三方垂直行业或外部运营商获得自身能够管理的网络资源，允许执行的操作。租户的管理能力范围包括创建类操作的范围和非创建类操作的范围，相对现有技术更加全面和灵活。
如图14所示，为本申请提供的又一种管理服务的发现方法流程图，图14实施例是图7所示实施例的一个具体示例。其中，图14实施例的其它运营商、EGMF和DNS可以分别看做图7实施例的租户、第一网元和服务器。
该方法包括以下步骤：
步骤1400：DNS系统中配置各个管理服务实例的管理能力记录，方法同图10实施例 的步骤1000的相关描述。
步骤1401：某外部运营商向EGMF发送请求消息，请求查询被授权的管理能力范围，请求消息中携带租户标识。其中租户标识是对外提供网络开放的运营商对第三方垂直行业或其它运营商租户的一个标识。
步骤1402：EGMF检查和确定租户标识，然后根据双方事先签订的协议确定租户的管理权限。具体的，确定租户可以创建的网络资源类型的信息，即租户可管理的IOC或其列表；以及确定租户可以管理的网络资源，即管理对象MOI或其列表。
步骤1403：EGMF以步骤1402获得的某IOC向DNS查询管理服务实例的注册信息，获得所有可用状态的管理服务实例对目标IOC可以提供的创建类管理服务名称，创建类管理动作(可选)，以及能力属性(可选)。具体的EGMF使用“_IOC”向DNS发送NAPTR查询，获得带有替换管理服务名称和S标志的查询响应。其中替换字段“_操作._IOC”或“_操作._IOC._能力属性”为创建类操作管理能力范围，SVR字段为管理服务名称。EGMF通过重复这个步骤上述IOC列表中每个IOC相关的上述信息。
步骤1404a(可选步骤)：EGMF可以进一步查询步骤1403得到的管理服务实例的访问地址。
步骤1404b(可选步骤)：EGMF向管理服务发送消息检测管理服务实例可以被访问。如果不能被访问，就将其相关的记录从步骤1403得到的结果中剔除。
步骤1405：为步骤1402的获得MOI列表得到的每个MOI查找出设置管理范围顶层标志的MOI，方法可参考图12实施例的相关描述。将得到的所有设置顶层标志的MOI组成一个新的列表。
步骤1406：EGMF为步骤1405获得列表中的每个设置顶层标志的MOI进行NAPTR查询，具体的查询请求携带“_MOI”，获得带有替换管理服务名称和S标志的查询响应。其中替换字段“_操作._MOI”或“_操作._IOC._MOI”为非创建类操作管理能力范围，SVR字段为管理服务名称。EGMF通过重复这个步骤上述MOI列表中每个MOI相关的上述信息。
步骤1407(可选步骤)：类似步骤1404a和1404b，EGMF查询服务地址，并且检测管理服务实例可访问。如果不能被访问，就将其相关的记录从步骤1406得到的结果中剔除。
步骤1408：EGMF汇总步骤1403和1406得到的结果，查询得到的{可创建的IOC，一到多个创建类管理服务名称，一到多个创建类管理动作(可选)，能力属性(可选)}和/或{可管理的带有顶层标志的MOI，允许的一到多个管理服务(可选)，允许的一到多个管理动作(可选)}组成的列表作为租户管理能力范围。
步骤1409：EGMF将步骤1408获得的租户管理能力范围作为查询结果响应发送给外部运营商。这样外部运营商就可以知道允许管理哪些网络资源，允许执行什么操作等等。
基于上述实施例，第三方垂直行业或外部运营商获得自身能够管理的网络资源，允许执行的操作。租户的管理能力范围包括创建类操作的范围和非创建类操作的范围，相对现有技术更加全面和灵活。另外，还能够与现有的DNS系统兼容，通过DNS查询获得管理能力范围。
综上所述，本申请提供了以下技术方案：
(1)管理服务实例创建类的管理能力信息包括：支持的管理服务、支持的操作、管理对象的类型IOC、可选的能力属性；非创建类的管理能力信息包括：支持的管理服务、支持的操作、管理对象的类型IOC、可选的MOI。管理服务实例的上述管理能力信息注册 到MSRF或者配置到DNS系统。
(2)管理服务实例的管理能力信息以NAPRT记录形式配置到DNS，支持以能力信息查询DNS得到管理服务或管理服务实例的域名。
(3)新创建的管理对象是管理能力范围内的顶级节点，为管理能力范围的顶级节点MOI设置标志。在DNS中为设置标志的顶级节点配置管理能力NAPTR记录。
(4)如果是DNS查询，管理服务消费者以目标MOI为起点向上查询带有管理能力范围顶层节点的MOI，然后以“操作+IOC+顶层MOI”进行DNS NAPTR查询获得管理服务或管理服务实例的域名。
(5)EGMF以租户可管理的IOC和MOI为标识向MSRF查询所有可用状态的管理服务实例能够提供的管理动作，将查询结果组成租户管理能力范围。
(6)以租户可管理的IOC或顶层MOI进行DNS NAPTR查询获得管理服务实例能够提供的管理范围，将可访问的管理服务实例提供的所述管理范围组成租户管理能力范围。
通过上述技术方案，管理服务的消费者能够根据期望的管理动作和管理对象，发现满足期望的管理能力信息的管理服务和访问地址，第三方垂直行业或外部运营商也能获得自身能够管理的网络资源和允许执行的操作。上述技术还能够兼容现有的DNS系统，进一步降低系统的成本。
上述主要从各个网元之间交互的角度对本申请提供的方案进行了介绍。可以理解的是，上述实现各网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
如图15所示，为本申请所涉及的管理服务的发现装置的一种可能的示例性框图，该装置1500可以以软件或硬件的形式存在。装置1500可以包括：处理单元1502和通信单元1503。作为一种实现方式，该通信单元1503可以包括接收单元和发送单元。处理单元1502用于对装置1500的动作进行控制管理。通信单元1503用于支持装置1500与其他网络实体的通信。装置1500还可以包括存储单元1501，用于存储装置1500的程序代码和数据。
其中，处理单元1502可以是处理器或控制器，例如可以是通用中央处理器(central processing unit，CPU)，通用处理器，数字信号处理(digital signal processing，DSP)，专用集成电路(application specific integrated circuits，ASIC)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包括一个或多个微处理器组合，DSP和微处理器的组合等等。存储单元1501可以是存储器。通信单元1503是一种该装置的接口电路，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该通信单元1503是该芯片用于从其它芯片或装置接收信号的接口电路，或者，是该芯片用于向其它芯片或装置发送信号的接口电路。
该装置1500可以为上述任一实施例中的第一网元，还可以为用于第一网元的芯片。 例如，当装置1500为第一网元时，该处理单元1502例如可以是处理器，该通信单元1503例如可以是收发器。可选的，该收发器可以包括射频电路，该存储单元例如可以是存储器。例如，当装置1500为用于第一网元的芯片时，该处理单元1502例如可以是处理器，该通信单元1503例如可以是输入/输出接口、管脚或电路等。该处理单元1502可执行存储单元存储的计算机执行指令，可选地，该存储单元为该芯片内的存储单元，如寄存器、缓存等，该存储单元还可以是该第一网元内的位于该芯片外部的存储单元，如只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)等。
在第一个实施例中，所述通信单元1503，用于根据期望的管理能力信息，从服务器获取管理服务实例的访问信息，所述管理服务实例与所述期望的管理能力信息匹配，所述期望的管理能力信息包括管理动作、管理对象的类型、或能力属性中的至少一个；所述处理单元1502，用于根据所述管理服务实例的访问信息和所述期望的管理能力信息，向第二网元调用管理服务，所述第二网元包括所述管理服务实例；所述通信单元1503，还用于从所述第二网元接收创建部署信息，所述创建部署信息包括所述管理对象的类型对应管理对象实例，所述管理对象实例用于标识所述管理服务实例所管理的网络资源。
在一种可能的实现方法中，所述服务器为管理服务仓库功能网元；所述通信单元1503，具体用于向所述管理服务仓库功能网元发送请求消息，所述请求消息包括所述期望的管理能力信息；所述第一网元从所述管理服务仓库功能网元接收所述管理服务实例的访问信息。
在一种可能的实现方法中，所述服务器为域名服务器；所述通信单元1503，具体用于向所述域名服务器发送请求消息，所述请求消息包括查询域名，所述查询域名是根据所述期望的管理能力信息构造的；从所述域名服务器接收与所述查询域名对应的名称权威指针NAPTR记录的权威域名；根据所述NAPTR记录的权威域名，从所述域名服务器获取所述管理服务实例的访问信息。
在一种可能的实现方法中，所述NAPTR记录的第一权威域名为所述管理服务实例的权威域名，所述通信单元1503，具体用于从所述域名服务器获取与所述NAPTR记录的权威域名对应的所述管理服务实例的访问信息；或者，所述NAPTR记录的权威域名为管理服务的权威域名，所述通信单元1503，具体用于从所述域名服务器获取与所述NAPTR记录的权威域名对应的服务SRV记录的权威域名，以及根据所述SRV记录的权威域名从所述域名服务器获取所述管理服务实例的访问信息。
在一种可能的实现方法中，所述装置为开放控制管理功能网元，所述第二网元为管理功能网元；或者，所述装置为第一管理功能网元，所述第二网元为第二管理功能网元，所述第二管理功能网元管理的网络资源是第一管理功能网元管理的网络资源的组成部分。
在第二个实施例中，所述通信单元1503，用于向域名服务器发送请求消息，所述请求消息包括查询域名，所述查询域名是根据期望的管理能力信息构造的，所述期望的管理能力信息包括管理服务、管理动作、管理对象的类型、或管理对象实例中的至少一个，所述管理对象实例用于标识管理服务实例所管理的网络资源；从所述域名服务器接收与所述查询域名对应的名称权威指针NAPTR记录的权威域名；根据所述NAPTR记录的权威域名，从所述服务器获取所述管理服务实例的访问信息；以及，根据所述管理服务实例的访问信息和所述期望的管理能力信息，向提供所述管理服务的第二网元调用所述管理服务。
在一种可能的实现方法中，所述管理对象为所述管理服务实例的管理能力范围内的顶 级节点。
在一种可能的实现方法中，所述装置为开放控制管理功能网元，所述第二网元为管理功能网元；或者，所述装置为第一管理功能网元，所述第二网元为第二管理功能网元，所述第二管理功能网元管理的网络资源是第一管理功能网元管理的网络资源的组成部分。
在第三个实施例中，所述处理单元1502，用于根据租户的标识，确定所述租户对应的信息对象类，其中，一个信息对象类用于标识一个可创建的网络资源类型；所述通信单元1503，用于根据所述租户对应的信息对象类，从服务器获取所述信息对象类对应的可提供的创建类管理服务的信息，所述创建类管理服务的信息包括创建类管理服务名称、创建类管理动作、或能力属性中的至少一个；以及，向所述租户发送第一消息，所述第一消息包括所述租户对应的信息对象类和所述可提供的创建类管理服务的信息。
在一种可能的实现方法中，所述服务器为域名服务器；所述通信单元1503，具体用于向所述域名服务器发送请求消息，所述请求消息包括所述信息对象类，所述请求消息用于请求NAPTR记录；从所述域名服务器接收所述可提供的创建类管理服务的信息。
在一种可能的实现方法中，所述处理单元1502，还用于根据租户的标识，确定所述租户对应的管理对象实例，其中，一个管理对象实例用于标识可被管理的网络资源；所述通信单元1503，还用于根据所述租户对应的管理对象实例，从所述服务器获取所述管理对象实例对应的可提供的管理服务的信息，所述管理服务的信息包括管理服务、或管理动作中的至少一个；以及，向所述租户发送第二消息，所述第二消息包括所述租户对应的管理对象实例和所述可提供的管理服务的信息。
在一种可能的实现方法中，所述服务器为域名服务器；所述通信单元1503，具体用于向所述域名服务器发送请求消息，所述请求消息包括所述信息对象类，所述请求消息用于请求查询NAPTR记录；以及，从所述域名服务器接收所述可提供的管理服务的信息。
可以理解的是，该装置用于上述管理服务的发现方法时的具体实现过程以及相应的有益效果，可以参考前述方法实施例中的相关描述，这里不再赘述。
如图16所示，为本申请所涉及的管理服务的发现装置的一种可能的示例性框图，该装置1600可以以软件或硬件的形式存在。装置1600可以包括：处理单元1602和通信单元1603。作为一种实现方式，该通信单元1603可以包括接收单元和发送单元。处理单元1602用于对装置1600的动作进行控制管理。通信单元1603用于支持装置1600与其他网络实体的通信。装置1600还可以包括存储单元1601，用于存储装置1600的程序代码和数据。
其中，处理单元1602可以是处理器或控制器，例如可以是CPU，通用处理器，DSP，ASIC，FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包括一个或多个微处理器组合，DSP和微处理器的组合等等。存储单元1601可以是存储器。通信单元1603是一种该装置的接口电路，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该通信单元1603是该芯片用于从其它芯片或装置接收信号的接口电路，或者，是该芯片用于向其它芯片或装置发送信号的接口电路。
该装置1600可以为上述任一实施例中的服务器，还可以为用于服务器的芯片。例如，当装置1600为服务器时，该处理单元1602例如可以是处理器，该通信单元1603例如可 以是收发器。可选的，该收发器可以包括射频电路，该存储单元例如可以是存储器。例如，当装置1600为用于服务器的芯片时，该处理单元1602例如可以是处理器，该通信单元1603例如可以是输入/输出接口、管脚或电路等。该处理单元1602可执行存储单元存储的计算机执行指令，可选地，该存储单元为该芯片内的存储单元，如寄存器、缓存等，该存储单元还可以是该服务器内的位于该芯片外部的存储单元，如ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM等。
在一个实施例中，所述通信单元1603，用于接收期望的管理能力信息，所述期望的管理能力信息包括管理动作、管理对象的类型、或能力属性中的至少一项；所述处理单元1602，用于根据所述期望的管理能力信息，获取管理服务实例的访问信息，所述管理服务实例与所述期望的管理能力信息匹配；所述通信单元1603，还用于发送所述管理服务实例的访问信息。
在一种可能的实现方法中，所述装置为管理服务仓库功能网元；所述通信单元1603，具体用于接收请求消息，所述请求消息包括所述期望的管理能力信息；所述服务仓库功能网元上配置有至少一个管理服务实例的访问信息与管理能力信息的对应关系，所述处理单元1602，具体用于根据所述期望的管理能力信息和所述对应关系，获取所述管理服务实例的访问信息。
在一种可能的实现方法中，所述通信单元1603，还用于接收管理对象实例的信息，所述管理对象实例的信息包括管理对象实例和所述管理对象实例与其他管理对象实例之间的关系，所述管理对象实例用于标识所述管理服务实例所管理的网络资源；所述处理单元1602，还用于根据所述管理对象实例的信息，更新所述管理服务实例对应的管理能力信息。
在一种可能的实现方法中，所述装置为域名服务器；所述通信单元1603，具体用于接收请求消息，所述请求消息查询域名，所述查询域名是根据所述期望的管理能力信息构造的；所述处理单元1602，具体用于获取与所述查询域名对应的NAPTR记录的权威域名；获取与所述NAPTR记录的权威域名对应的所述管理服务实例的访问信息。
在一种可能的实现方法中，所述NAPTR记录的权威域名为所述管理服务实例的权威域名，所述处理单元1602，具体用于获取与所述管理服务实例的权威域名对应的所述管理服务实例的访问信息；或者，所述NAPTR记录的权威域名为管理服务的权威域名，所述处理单元1602，具体用于获取与所述管理服务的权威域名对应的SRV记录的权威域名，以及根据所述SRV记录的权威域名获取所述管理服务实例的访问信息。
在一种可能的实现方法中，所述通信单元1603，还用于接收管理对象实例的信息，所述管理对象实例的信息包括管理对象实例和所述管理对象实例与其他管理对象实例之间的关系，所述管理对象实例用于标识所述管理服务实例所管理的网络资源，所述管理对象实例为所述管理服务实例的管理能力范围内的顶级节点；所述处理单元1602，还用于根据所述管理对象实例的信息，更新所述管理服务实例对应的NAPTR记录。
可以理解的是，该装置用于上述管理服务的发现方法时的具体实现过程以及相应的有益效果，可以参考前述方法实施例中的相关描述，这里不再赘述。
如图17所示，为本申请提供的一种管理服务的发现装置示意图，该装置可以是上述实施例中的第一网元、或服务器。该装置1700包括：处理器1702、通信接口1703、存储器1701。可选的，装置1700还可以包括通信线路1704。其中，通信接口1703、处理器1702以及存储器1701可以通过通信线路1704相互连接；通信线路1704可以是外设部件 互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。所述通信线路1704可以分为地址总线、数据总线、控制总线等。为便于表示，图17中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
处理器1702可以是一个CPU，微处理器，ASIC，或一个或多个用于控制本申请方案程序执行的集成电路。
通信接口1703，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)，有线接入网等。
存储器1701可以是ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路1704与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器1701用于存储执行本申请方案的计算机执行指令，并由处理器1702来控制执行。处理器1702用于执行存储器1701中存储的计算机执行指令，从而实现本申请上述实施例提供的管理服务的发现方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
本领域普通技术人员可以理解：本申请中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围，也表示先后顺序。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。“至少一个”是指一个或者多个。至少两个是指两个或者多个。“至少一个”、“任意一个”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个、种)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。“多个”是指两个或两个以上，其它量词与之类似。此外，对于单数形式“a”，“an”和“the”出现的元素(element)，除非上下文另有明确规定，否则其不意味着“一个或仅一个”，而是意味着“一个或多于一个”。例如，“a device”意味着对一个或多个这样的device。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、 数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器，数字信号处理器，专用集成电路(ASIC)，现场可编程门阵列(FPGA)或其它可编程逻辑装置，离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器，可选地，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现，例如数字信号处理器和微处理器，多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
本申请实施例中所描述的方法或算法的步骤可以直接嵌入硬件、处理器执行的软件单元、或者这两者的结合。软件单元可以存储于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、可移动磁盘、CD-ROM或本领域中其它任意形式的存储媒介中。示例性地，存储媒介可以与处理器连接，以使得处理器可以从存储媒介中读取信息，并可以向存储媒介存写信息。可选地，存储媒介还可以集成到处理器中。处理器和存储媒介可以设置于ASIC中。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包括这些改动和变型在内。

Claims (30)

  1. 一种管理服务的发现方法，其特征在于，包括：
    第一网元根据期望的管理能力信息，从服务器获取管理服务实例的访问信息，所述管理服务实例与所述期望的管理能力信息匹配，所述期望的管理能力信息包括管理动作、管理对象的类型、或能力属性中的至少一个；
    所述第一网元根据所述管理服务实例的访问信息和所述期望的管理能力信息，向第二网元调用管理服务，所述第二网元包括所述管理服务实例；
    所述第一网元从所述第二网元接收创建部署信息，所述创建部署信息包括所述管理对象的类型对应管理对象实例，所述管理对象实例用于标识所述管理服务实例所管理的网络资源。
  2. 如权利要求1所述的方法，其特征在于，所述服务器为管理服务仓库功能网元；
    所述第一网元根据期望的管理能力信息，从服务器获取管理服务实例的访问信息，包括：
    所述第一网元向所述管理服务仓库功能网元发送请求消息，所述请求消息包括所述期望的管理能力信息；
    所述第一网元从所述管理服务仓库功能网元接收所述管理服务实例的访问信息。
  3. 如权利要求1所述的方法，其特征在于，所述服务器为域名服务器；
    所述第一网元根据期望的管理能力信息，从服务器获取管理服务实例的访问信息，包括：
    所述第一网元向所述域名服务器发送请求消息，所述请求消息包括查询域名，所述查询域名是根据所述期望的管理能力信息构造的；
    所述第一网元从所述域名服务器接收与所述查询域名对应的名称权威指针NAPTR记录的权威域名；
    所述第一网元根据所述NAPTR记录的权威域名，从所述域名服务器获取所述管理服务实例的访问信息。
  4. 如权利要求3所述的方法，其特征在于，所述第一网元根据所述NAPTR记录的权威域名，从所述域名服务器获取所述管理服务实例的访问信息，包括：
    所述NAPTR记录的第一权威域名为所述管理服务实例的权威域名，所述第一网元从所述域名服务器获取与所述NAPTR记录的权威域名对应的所述管理服务实例的访问信息；或者，
    所述NAPTR记录的权威域名为管理服务的权威域名，所述第一网元从所述域名服务器获取与所述NAPTR记录的权威域名对应的服务SRV记录的权威域名，以及根据所述SRV记录的权威域名从所述域名服务器获取所述管理服务实例的访问信息。
  5. 如权利要求1-4任一所述的方法，其特征在于，所述第一网元为开放控制管理功能网元，所述第二网元为管理功能网元；或者，所述第一网元为第一管理功能网元，所述第二网元为第二管理功能网元，所述第二管理功能网元管理的网络资源是第一管理功能网元管理的网络资源的组成部分。
  6. 一种管理服务的发现方法，其特征在于，包括：
    服务器接收期望的管理能力信息，所述期望的管理能力信息包括管理动作、管理对象 的类型、或能力属性中的至少一项；
    所述服务器根据所述期望的管理能力信息，获取管理服务实例的访问信息，所述管理服务实例与所述期望的管理能力信息匹配；
    所述服务器发送所述管理服务实例的访问信息。
  7. 如权利要求6所述的方法，其特征在于，所述服务器为管理服务仓库功能网元；
    所述服务器接收期望的管理能力信息，包括：
    所述管理服务仓库功能网元接收请求消息，所述请求消息包括所述期望的管理能力信息；
    所述服务器根据所述期望的管理能力信息，获取管理服务实例的访问信息，包括：
    所述管理服务仓库功能网元上配置有至少一个管理服务实例的访问信息与管理能力信息的对应关系，所述管理服务仓库功能网元根据所述期望的管理能力信息和所述对应关系，获取所述管理服务实例的访问信息。
  8. 如权利要求7所述的方法，其特征在于，还包括：
    所述管理服务仓库功能网元接收管理对象实例的信息，所述管理对象实例的信息包括管理对象实例和所述管理对象实例与其他管理对象实例之间的关系，所述管理对象实例用于标识所述管理服务实例所管理的网络资源；
    所述管理服务仓库功能网元根据所述管理对象实例的信息，更新所述管理服务实例对应的管理能力信息。
  9. 如权利要求6所述的方法，其特征在于，所述服务器为域名服务器；
    所述服务器接收期望的管理能力信息，包括：
    所述域名服务器接收请求消息，所述请求消息查询域名，所述查询域名是根据所述期望的管理能力信息构造的；
    所述服务器根据所述期望的管理能力信息，获取管理服务实例的访问信息，包括：
    所述域名服务器获取与所述查询域名对应的NAPTR记录的权威域名；
    所述域名服务器获取与所述NAPTR记录的权威域名对应的所述管理服务实例的访问信息。
  10. 如权利要求9所述的方法，其特征在于，所述域名服务器获取与所述NAPTR记录的权威域名对应的所述管理服务实例的访问信息，包括：
    所述NAPTR记录的权威域名为所述管理服务实例的权威域名，所述域名服务器获取与所述管理服务实例的权威域名对应的所述管理服务实例的访问信息；或者，
    所述NAPTR记录的权威域名为管理服务的权威域名，所述域名服务器获取与所述管理服务的权威域名对应的SRV记录的权威域名，以及根据所述SRV记录的权威域名获取所述管理服务实例的访问信息。
  11. 如权利要求9或10所述的方法，其特征在于，还包括：
    所述域名服务器接收管理对象实例的信息，所述管理对象实例的信息包括管理对象实例和所述管理对象实例与其他管理对象实例之间的关系，所述管理对象实例用于标识所述管理服务实例所管理的网络资源，所述管理对象实例为所述管理服务实例的管理能力范围内的顶级节点；
    所述服务器根据所述管理对象实例的信息，更新所述管理服务实例对应的NAPTR记录。
  12. 一种管理服务的发现方法，其特征在于，包括：
    第一网元根据租户的标识，确定所述租户对应的信息对象类，其中，一个信息对象类用于标识一个可创建的网络资源类型；
    所述第一网元根据所述租户对应的信息对象类，从服务器获取所述信息对象类对应的可提供的创建类管理服务的信息，所述创建类管理服务的信息包括创建类管理服务名称、创建类管理动作、或能力属性中的至少一个；
    所述第一网元向所述租户发送第一消息，所述第一消息包括所述租户对应的信息对象类和所述可提供的创建类管理服务的信息。
  13. 如权利要求12所述的方法，其特征在于，所述服务器为域名服务器；
    所述第一网元根据所述租户对应的信息对象类，从服务器获取所述信息对象类对应的可提供的创建类管理能力信息，包括：
    所述第一网元向所述域名服务器发送请求消息，所述请求消息包括所述信息对象类，所述请求消息用于请求NAPTR记录；
    所述第一网元从所述域名服务器接收所述可提供的创建类管理服务的信息。
  14. 如权利要求12所述的方法，其特征在于，还包括：
    所述第一网元根据租户的标识，确定所述租户对应的管理对象实例，其中，一个管理对象实例用于标识可被管理的网络资源；
    所述第一网元根据所述租户对应的管理对象实例，从所述服务器获取所述管理对象实例对应的可提供的管理服务的信息，所述管理服务的信息包括管理服务或管理动作中的至少一个；
    所述第一网元向所述租户发送第二消息，所述第二消息包括所述租户对应的管理对象实例和所述可提供的管理服务的信息。
  15. 如权利要求14所述的方法，其特征在于，所述服务器为域名服务器；
    所述第一网元根据所述租户对应的管理对象实例，从所述服务器获取所述管理对象实例对应的可提供的管理服务的信息，包括：
    所述第一网元向所述域名服务器发送请求消息，所述请求消息包括所述信息对象类，所述请求消息用于请求查询NAPTR记录；
    所述第一网元从所述域名服务器接收所述可提供的管理服务的信息。
  16. 一种管理服务的发现装置，其特征在于，包括：通信单元和处理单元；
    所述通信单元，用于根据期望的管理能力信息，从服务器获取管理服务实例的访问信息，所述管理服务实例与所述期望的管理能力信息匹配，所述期望的管理能力信息包括管理动作、管理对象的类型、或能力属性中的至少一个；
    所述处理单元，用于根据所述管理服务实例的访问信息和所述期望的管理能力信息，向第二网元调用管理服务，所述第二网元包括所述管理服务实例；
    所述通信单元，还用于从所述第二网元接收创建部署信息，所述创建部署信息包括所述管理对象的类型对应管理对象实例，所述管理对象实例用于标识所述管理服务实例所管理的网络资源。
  17. 如权利要求16所述的装置，其特征在于，所述服务器为管理服务仓库功能网元；
    所述通信单元，具体用于向所述管理服务仓库功能网元发送请求消息，所述请求消息包括所述期望的管理能力信息；所述第一网元从所述管理服务仓库功能网元接收所述管理 服务实例的访问信息。
  18. 如权利要求16所述的装置，其特征在于，所述服务器为域名服务器；
    所述通信单元，具体用于向所述域名服务器发送请求消息，所述请求消息包括查询域名，所述查询域名是根据所述期望的管理能力信息构造的；从所述域名服务器接收与所述查询域名对应的名称权威指针NAPTR记录的权威域名；根据所述NAPTR记录的权威域名，从所述域名服务器获取所述管理服务实例的访问信息。
  19. 如权利要求18所述的装置，其特征在于，所述NAPTR记录的第一权威域名为所述管理服务实例的权威域名，所述通信单元，具体用于从所述域名服务器获取与所述NAPTR记录的权威域名对应的所述管理服务实例的访问信息；或者，
    所述NAPTR记录的权威域名为管理服务的权威域名，所述通信单元，具体用于从所述域名服务器获取与所述NAPTR记录的权威域名对应的服务SRV记录的权威域名，以及根据所述SRV记录的权威域名从所述域名服务器获取所述管理服务实例的访问信息。
  20. 如权利要求16-19任一所述的装置，其特征在于，所述装置为开放控制管理功能网元，所述第二网元为管理功能网元；或者，
    所述装置为第一管理功能网元，所述第二网元为第二管理功能网元，所述第二管理功能网元管理的网络资源是第一管理功能网元管理的网络资源的组成部分。
  21. 一种管理服务的发现装置，其特征在于，包括：通信单元和处理单元；
    所述通信单元，用于接收期望的管理能力信息，所述期望的管理能力信息包括管理动作、管理对象的类型、或能力属性中的至少一项；
    所述处理单元，用于根据所述期望的管理能力信息，获取管理服务实例的访问信息，所述管理服务实例与所述期望的管理能力信息匹配；
    所述通信单元，还用于发送所述管理服务实例的访问信息。
  22. 如权利要求21所述的装置，其特征在于，所述装置为管理服务仓库功能网元；
    所述通信单元，具体用于接收请求消息，所述请求消息包括所述期望的管理能力信息；
    所述服务仓库功能网元上配置有至少一个管理服务实例的访问信息与管理能力信息的对应关系，所述处理单元，具体用于根据所述期望的管理能力信息和所述对应关系，获取所述管理服务实例的访问信息。
  23. 如权利要求22所述的装置，其特征在于，所述通信单元，还用于接收管理对象实例的信息，所述管理对象实例的信息包括管理对象实例和所述管理对象实例与其他管理对象实例之间的关系，所述管理对象实例用于标识所述管理服务实例所管理的网络资源；
    所述处理单元，还用于根据所述管理对象实例的信息，更新所述管理服务实例对应的管理能力信息。
  24. 如权利要求21所述的装置，其特征在于，所述装置为域名服务器；
    所述通信单元，具体用于接收请求消息，所述请求消息查询域名，所述查询域名是根据所述期望的管理能力信息构造的；
    所述处理单元，具体用于获取与所述查询域名对应的NAPTR记录的权威域名；获取与所述NAPTR记录的权威域名对应的所述管理服务实例的访问信息。
  25. 如权利要求24所述的装置，其特征在于，所述NAPTR记录的权威域名为所述管理服务实例的权威域名，所述处理单元，具体用于获取与所述管理服务实例的权威域名对应的所述管理服务实例的访问信息；或者，
    所述NAPTR记录的权威域名为管理服务的权威域名，所述处理单元，具体用于获取与所述管理服务的权威域名对应的SRV记录的权威域名，以及根据所述SRV记录的权威域名获取所述管理服务实例的访问信息。
  26. 如权利要求24或25所述的装置，其特征在于，所述通信单元，还用于接收管理对象实例的信息，所述管理对象实例的信息包括管理对象实例和所述管理对象实例与其他管理对象实例之间的关系，所述管理对象实例用于标识所述管理服务实例所管理的网络资源，所述管理对象实例为所述管理服务实例的管理能力范围内的顶级节点；
    所述处理单元，还用于根据所述管理对象实例的信息，更新所述管理服务实例对应的NAPTR记录。
  27. 一种管理服务的发现装置，其特征在于，包括：通信单元和处理单元；
    所述处理单元，用于根据租户的标识，确定所述租户对应的信息对象类，其中，一个信息对象类用于标识一个可创建的网络资源类型；
    所述通信单元，用于根据所述租户对应的信息对象类，从服务器获取所述信息对象类对应的可提供的创建类管理服务的信息，所述创建类管理服务的信息包括创建类管理服务名称、创建类管理动作、或能力属性中的至少一个；以及，向所述租户发送第一消息，所述第一消息包括所述租户对应的信息对象类和所述可提供的创建类管理服务的信息。
  28. 如权利要求27所述的装置，其特征在于，所述服务器为域名服务器；
    所述通信单元，具体用于向所述域名服务器发送请求消息，所述请求消息包括所述信息对象类，所述请求消息用于请求NAPTR记录；从所述域名服务器接收所述可提供的创建类管理服务的信息。
  29. 如权利要求27所述的装置，其特征在于，所述处理单元，还用于根据租户的标识，确定所述租户对应的管理对象实例，其中，一个管理对象实例用于标识可被管理的网络资源；
    所述通信单元，还用于根据所述租户对应的管理对象实例，从所述服务器获取所述管理对象实例对应的可提供的管理服务的信息，所述管理服务的信息包括管理服务、或管理动作中的至少一个；以及，向所述租户发送第二消息，所述第二消息包括所述租户对应的管理对象实例和所述可提供的管理服务的信息。
  30. 如权利要求29所述的装置，其特征在于，所述服务器为域名服务器；
    所述通信单元，具体用于向所述域名服务器发送请求消息，所述请求消息包括所述信息对象类，所述请求消息用于请求查询NAPTR记录；以及，从所述域名服务器接收所述可提供的管理服务的信息。
PCT/CN2020/084982 2019-06-17 2020-04-15 一种管理服务的发现方法及装置 WO2020253343A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910521531.8 2019-06-17
CN201910521531.8A CN112104468B (zh) 2019-06-17 2019-06-17 一种管理服务的发现方法及装置

Publications (1)

Publication Number Publication Date
WO2020253343A1 true WO2020253343A1 (zh) 2020-12-24

Family

ID=73749342

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/084982 WO2020253343A1 (zh) 2019-06-17 2020-04-15 一种管理服务的发现方法及装置

Country Status (2)

Country Link
CN (1) CN112104468B (zh)
WO (1) WO2020253343A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115277458B (zh) * 2021-04-30 2023-11-17 阿里巴巴新加坡控股有限公司 服务提供方法、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018084975A1 (en) * 2016-11-02 2018-05-11 Intel IP Corporation Lifecycle management parameter modeling for virtual network functions
CN108632058A (zh) * 2017-03-18 2018-10-09 华为技术有限公司 网络切片的管理方法和装置
CN109379206A (zh) * 2017-08-07 2019-02-22 华为技术有限公司 网络功能信息的管理方法及相关设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103595551B (zh) * 2012-08-17 2016-12-21 杭州华三通信技术有限公司 基于mqc实现网络虚拟化的网络管理方法和装置
US10250694B2 (en) * 2016-08-19 2019-04-02 Ca, Inc. Maintaining distributed state among stateless service clients
CN109391592B (zh) * 2017-08-08 2021-12-24 华为技术有限公司 网络功能服务的发现方法及设备
CN109257440A (zh) * 2018-10-29 2019-01-22 南京南瑞信息通信科技有限公司 一种基于服务注册中心的服务发现和客户端负载均衡方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018084975A1 (en) * 2016-11-02 2018-05-11 Intel IP Corporation Lifecycle management parameter modeling for virtual network functions
CN108632058A (zh) * 2017-03-18 2018-10-09 华为技术有限公司 网络切片的管理方法和装置
CN109379206A (zh) * 2017-08-07 2019-02-22 华为技术有限公司 网络功能信息的管理方法及相关设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP: "Management and orchestration of networks and network slicing; Provisioning; Stage 2 and stage 3 (Release 15)", 3GPP TS 28.532 V0.3.0, 31 May 2018 (2018-05-31), DOI: 20200702195018A *
HUAWEI: "pCR 28.532 clean-up update network slice subnet related procedures", 3GPP TSG SA WG5 (TELECOM MANAGEMENT) MEETING #119 AD-HOC S5-184080, 28 June 2018 (2018-06-28), XP051470836, DOI: 20200702194810A *
HUAWEI: "pCR 28.533 Utilization of management service registration and discovery", 3GPP TSG SA WG5 (TELECOM MANAGEMENT) MEETING #120 S5-185153, 24 August 2018 (2018-08-24), XP051543004, DOI: 20200702194455X *

Also Published As

Publication number Publication date
CN112104468B (zh) 2021-12-03
CN112104468A (zh) 2020-12-18

Similar Documents

Publication Publication Date Title
WO2020224463A1 (zh) 一种数据分析方法及装置
CN111953576B (zh) 虚拟网络通信方法、设备及系统
JP7139522B2 (ja) ローカルエリアネットワーク通信方法、装置、およびシステム
WO2019242574A1 (zh) 一种物联网业务路由的方法
US20200128614A1 (en) Session processing method and device
WO2019029525A1 (zh) 网络功能信息的管理方法及相关设备
US20230171618A1 (en) Communication method and apparatus
WO2021135663A1 (zh) 应用实例确定的方法、装置及系统
EP4016961A1 (en) Information obtaining method and device
WO2021017550A1 (zh) 一种事件报告的发送方法、装置及系统
JP2020532243A (ja) データ伝送方法、デバイス、およびシステム
WO2023280121A1 (zh) 一种获取边缘服务的方法和装置
WO2020015634A1 (zh) 一种mec信息获取方法及装置
JP2022544488A (ja) ネットワーク機能サービスディスカバリのための方法および装置
CN113132897A (zh) 应用实例确定的方法、装置及系统
WO2020238411A1 (en) Method and apparatus for network exposure function discovery and selection
WO2023011217A1 (zh) 一种通信方法及装置
WO2021051420A1 (zh) 一种dns缓存记录的确定方法及装置
WO2021212939A1 (zh) 通信方法、装置及系统
WO2020220799A1 (zh) 一种通信方法、装置及系统
KR20220018555A (ko) 논리적 tsn 브리지를 위한 방법 및 장치
US20240056496A1 (en) Method and Apparatus for Selecting Edge Application Server
WO2020253343A1 (zh) 一种管理服务的发现方法及装置
JP2024511907A (ja) ネットワーク機能登録方法、発見方法、装置、デバイス及び媒体
WO2022222745A1 (zh) 一种通信方法及装置

Legal Events

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

Ref document number: 20827167

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20827167

Country of ref document: EP

Kind code of ref document: A1