WO2019029525A1 - 网络功能信息的管理方法及相关设备 - Google Patents

网络功能信息的管理方法及相关设备 Download PDF

Info

Publication number
WO2019029525A1
WO2019029525A1 PCT/CN2018/099179 CN2018099179W WO2019029525A1 WO 2019029525 A1 WO2019029525 A1 WO 2019029525A1 CN 2018099179 W CN2018099179 W CN 2018099179W WO 2019029525 A1 WO2019029525 A1 WO 2019029525A1
Authority
WO
WIPO (PCT)
Prior art keywords
instance
nrf
information
message
management
Prior art date
Application number
PCT/CN2018/099179
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 华为技术有限公司
Priority to EP18844495.4A priority Critical patent/EP3664370B1/en
Publication of WO2019029525A1 publication Critical patent/WO2019029525A1/zh
Priority to US16/783,326 priority patent/US11277306B2/en

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • 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/04—Network management architectures or arrangements
    • 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/04—Network management architectures or arrangements
    • H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to a method for managing network function information and related devices.
  • next-generation network needs to meet the different requirements of different industries and different users for the network, and provide personalized network services for different users in a targeted manner.
  • the service architecture of the network is an important technical means to achieve this goal.
  • the network side can dynamically adjust the network route according to the service request of the terminal or the real-time situation of the network at the same time, thereby satisfying the service request of the terminal.
  • NRF network repository function
  • An NRF instance is a logical entity used to store and maintain information about network function (NF) instances.
  • the NF instance may determine the next hop route by querying the NRF instance for the NF instance of the network service that can provide the user request.
  • NRF instance In an existing network service architecture, only one NRF instance exists.
  • the NF instance can directly initiate registration, query, and other processes to the NRF instance.
  • the embodiment of the present application describes a method for managing network function information and related devices, in order to optimize the service architecture of the network.
  • the embodiment of the present application provides a method for managing network function information, where the method includes: the management network element acquires the identifier information of the NRF instance of the network warehouse function, the information of the network function NF instance in the NRF instance, and the identifier of the NRF instance. The information is used to indicate the NRF instance associated with the NF instance; then, the management network element sends a first message to the NF instance or the management unit of the NF instance, the first message includes the identification information of the NRF instance; and then the NF instance determines the association according to the first message. NRF instances, and register, update, or query information about other NF instances.
  • the management network element may indicate the NRF instance associated with the NF instance to the NF instance, so that the NF instance can directly register with the NRF instance and update the information of the NF instance. Optimize the configuration process; or, the NF instance can determine which NRF instance to query for information about other NF instances.
  • the method includes:
  • the management network element obtains the identifier information of the NRF instance of the network warehouse function, and the NRF instance stores the information of the network function NF instance.
  • the identifier information of the NRF instance is used to indicate the NRF instance associated with the NF instance.
  • the management network element is identified according to the identifier of the NRF instance.
  • Information establishes the association between the NF instance and the NRF instance.
  • the identifier information of the NRF instance is obtained to establish an association relationship between the NF instance and the NRF instance, so as to facilitate subsequent indication that the NF instance registers, updates, or queries other NFs to the NRF instance. Instance information.
  • the foregoing first message further includes information about the NF instance.
  • the management network element configures the identifier information of the NRF instance in the management object of the NF instance.
  • the foregoing manner of obtaining the identifier information of the network warehouse function NRF instance may include one or all of the following: receiving a management request message, where the management request message includes identifier information of the NRF instance or an indication of the NRF instance.
  • the information, the indication information of the NRF instance is used to obtain the identifier information of the NRF instance, or the identifier information of the NRF instance or the indication information of the NRF instance is used to obtain the identifier information of the NRF instance.
  • the indication information of the foregoing NRF instance may include at least one of the following: isolation requirement information, security information, location information, user information, and network information.
  • the foregoing first message includes information of an NF instance
  • the management request message may further include information of an NF instance.
  • the foregoing first message further includes registration indication information, where the registration indication information is used to indicate whether the NF instance is registered with the NRF instance.
  • the identifier information of the foregoing NRF instance may include at least one of the following: an identifier of the NRF instance, a name of the NRF instance, or a network address of the NRF instance.
  • the information about the NF instance may include at least one of the following: an instance type, address information, domain name information, slice information of a network slice to which it belongs, a service area, an NF group information, or a discovery policy.
  • the embodiment of the present application provides another method for managing network function information, where the method includes: the NF instance receives the first message, where the first message includes the identifier information of the NRF instance that stores the information of the NF instance, and the NRF instance The identifier information is used to indicate the NRF instance that is associated with the NF instance.
  • the NF instance sends a second message to the NRF instance, where the second message includes information of the NF instance, and the second message is used to indicate the NRF instance.
  • the information of the NF instance is saved or updated.
  • the NF instance sends a third message to the NRF instance, where the third message is used to query the NRF instance for information of other NF instances.
  • the management NE when there are multiple NRF instances, sends a first message to the NF instance to indicate the NRF instance associated with the NF instance, so that the NF instance can directly send the second message to the NRF instance. Register and update the information of the NF instance to optimize the configuration process. Alternatively, the NF instance can determine which NRF instance to send to the NRF instance to query the information of other NF instances.
  • the foregoing first message further includes information of an NF instance.
  • the foregoing second message is a registration request message of the service corresponding to the NF instance or the NF instance
  • the NF instance may further receive the activation request message and the activation request message before the NF instance sends the second message to the NRF instance.
  • the service corresponding to the NF instance or the NF instance is activated to trigger the NF instance to send a registration request message to the NRF instance.
  • the NF instance may further send a fourth message to the NRF instance, where the fourth message is used to indicate that the NRF instance deletes the information of the NF instance or sets the information of the NF instance to be unavailable.
  • the fourth message is a deregistration request message of the service corresponding to the NF instance or the NF instance, and the NF instance may further receive the deactivation request message before the NF instance sends the fourth message to the NRF instance.
  • the activation request message is used to deactivate the service corresponding to the NF instance or the NF instance to trigger the NF instance to send a registration request message to the NRF instance.
  • the embodiment of the present application provides a management network element, which has the function of managing the behavior of the network element in the design of the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the management network element includes a processor configured to support the management network element to perform the corresponding functions in the above methods. Further, the management network element may further include a communication interface, which is used to support communication between the management network element and the NF instance, the management unit of the NF instance, the NRF instance, other management network elements, or other devices. Further, the management network element may further include a memory for coupling with the processor, which stores program instructions and data necessary for managing the network element.
  • an embodiment of the present application provides an NF instance, where the NF instance has a function of implementing an NF instance behavior in the foregoing method design.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the NF instance includes a processor configured to support the NF instance to perform the corresponding functions in the above methods. Further, the NF instance may further include a communication interface for supporting communication between the NF instance and the management network element, the management unit of the NRF instance or the NF instance, or other units. Further, the NF instance can also include a memory for coupling with the processor that holds the program instructions and data necessary for the NF instance.
  • an embodiment of the present application provides an NRF instance, where the NRF instance has a function of implementing an NRF instance behavior in the foregoing method design.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the NRF instance includes a processor configured to support an NRF instance to perform corresponding functions in the methods described above. Further, the NRF instance may further include a communication interface for supporting communication between the NRF instance and a management network element, an NF instance, or a management unit of the NF instance or other device. Further, the NRF instance can also include a memory for coupling with the processor that holds the program instructions and data necessary for the NRF instance.
  • the embodiment of the present application provides a management unit of an NF instance, where the management unit of the NF instance has a function of implementing a management unit behavior of an NF instance in the foregoing method design.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the management unit of the NF instance includes a processor configured to support a management unit of the NF instance to perform corresponding functions in the above methods. Further, the management unit of the NF instance may further include a communication interface for supporting communication between the management unit of the NF instance and the management network element, the NRF instance or the NF instance or other devices. Further, the management unit of the NF instance may further include a memory for coupling with the processor, which stores program instructions and data necessary for the management unit of the NF instance.
  • the embodiment of the present application provides a communication system, where the communication system includes the management network element and the NF instance, and the communication system includes the management network element, the NF instance, and the NRF instance.
  • the communication system includes the management network element, the NF instance, the management unit of the NF instance, and the NRF instance described in the above aspects.
  • embodiments of the present application provide a computer readable storage medium having instructions stored therein that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • an embodiment of the present application provides a computer program product comprising instructions that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • the management network element can indicate the NRF instance associated with the NF instance to the NF instance, or the management network element can establish an association relationship between the NF instance and the NRF instance, thereby The information about which NF instances are stored and maintained by each NRF instance can be determined, which facilitates the process of registering, querying, and the like by the NF instance to the NRF instance.
  • FIG. 1 is a schematic diagram of a possible network structure provided by an embodiment of the present application.
  • FIG. 2 is a schematic structural diagram of an OAM system according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of communication of a method for managing network function information provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of communication of another method for managing network function information provided by an embodiment of the present application.
  • FIG. 5A is a schematic diagram of communication of another method for managing network function information according to an embodiment of the present application.
  • FIG. 5B is a schematic diagram of communication of another method for managing network function information according to an embodiment of the present application.
  • FIG. 6A is a schematic diagram of communication of another method for managing network function information according to an embodiment of the present application.
  • FIG. 6B is a schematic diagram of communication of another method for managing network function information according to an embodiment of the present application.
  • FIG. 7 is a schematic flowchart diagram of still another method for managing network function information according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a management network element according to an embodiment of the present disclosure.
  • FIG. 8B is a schematic structural diagram of another management network element according to an embodiment of the present application.
  • 9A is a schematic structural diagram of an example of a network function according to an embodiment of the present application.
  • FIG. 9B is a schematic structural diagram of another network function example according to an embodiment of the present disclosure.
  • FIG. 10A is a schematic structural diagram of an example of a network warehouse function according to an embodiment of the present application.
  • FIG. 10B is a schematic structural diagram of another network warehouse function example according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a management unit of a network function instance according to an embodiment of the present application.
  • FIG. 11B is a schematic structural diagram of a management unit of another network function instance according to an embodiment of the present disclosure.
  • FIG. 1 is a schematic diagram of a possible network architecture provided by an embodiment of the present application, including an operation administration and maintenance (OAM) system, a network function (NF) instance, and a network warehouse function. (network repository function, NRF) instance.
  • OAM operation administration and maintenance
  • NF network function
  • NRF network repository function
  • the OAM system is a unified name for various network entities used by operators to perform network management.
  • the functions of the OAM system mainly include: analysis, prediction, planning, and configuration of daily network and services; daily operations for testing and fault management of the network and its services.
  • An NF instance refers to a separate virtual or physical logical network function that performs computing, storage, and network communication functions.
  • the NF instance involved in the embodiment of the present application may refer to an NF instance of a core network (CN), such as an access management function instance (AMF Instance), and a session management function instance (session management function instance, SMF Instance, etc., may also refer to an NF instance of an access network (AN), such as a 5G node B function instance, an eLTE eNB function instance, an eNB function instance, and the like.
  • CN core network
  • AMF Instance access management function instance
  • SMF Instance session management function instance
  • AN access network
  • An NRF instance also known as a network function warehouse function instance, is a logical entity for storing and maintaining information of an NF instance.
  • the NF instance can obtain a user request by querying the NRF instance.
  • Other NF instances of the network service to determine the next hop route.
  • the OAM system manages at least one NF instance (NF1, NF2, NF3, and NF4 are shown in Figure 1) and at least one NRF instance (NRF1 and NRF2 are shown in Figure 1) and They communicate interactively.
  • the NF instance and its corresponding NRF instance can also communicate with each other.
  • NF1 and NF2 shown in FIG. 1 are associated with NRF1, that is, NRF1 saves and maintains information of NF1 and NF2, and then NF1 and NF2 can be combined with NRF1, respectively.
  • Conduct communication interactions are associated with NRF1, that is, NRF1 saves and maintains information of NF1 and NF2, and then NF1 and NF2 can be combined with NRF1, respectively.
  • the present application is also applicable to a scenario in which multiple NF instances are uniformly managed by a management unit of an NF instance.
  • the management message may be sent to the at least one NF instance by the management unit of the NF instance.
  • the management unit of the NF instance may be an element manager (EM) unit, a network function manager (NFM) unit, or a domain management (DM) unit. Specifically limited.
  • FIG. 2 is a schematic structural diagram of an OAM system according to an embodiment of the present application, including a business support system (BSS), a network management (NM) unit, and a domain management ( Domain management, DM) unit, where:
  • BSS business support system
  • NM network management
  • DM domain management
  • a service support system or a service management (SM) unit is configured to receive service requirements of related tenants and convert them into network slice related requirements, and then perform business related management.
  • SM service management
  • the network management unit which may also be referred to as a network slice management function (NSMF) unit, includes one or both of end-to-end network management functions or end-to-end network orchestration functions, and may have some or all of the following functions:
  • NSMF network slice management function
  • End-to-end network management eg, network lifecycle management, network template management, network fault management, network performance management, and network configuration management
  • end-to-end network and sub-network and network function mapping different domains Network resources or sub-service level agreement (sub-SLA) coordination provided by (for example, access network domain, core network domain, and transmission domain); decomposition network requirement information is subnet requirement information;
  • the sub-network and network functions provided by the domain are uniformly arranged so that subnets or network functions provided by different sub-domains can meet the requirements of the target service or network, for example, SLA requirements, key performance indicators (KPIs) Requirements and quality of service (QoS) requirements.
  • SLA Service Level Agreement
  • KPIs key performance indicators
  • QoS quality of service
  • the NM unit is used to indicate the network unit having the above functions, and does not impose any restrictions on the name of the NM unit. It may also be a cross-domain management unit, a cross-domain network slice management unit, or other network units.
  • the NM unit may be an independent management unit, or may be a logical entity in any one of the management units, such as a network orchestration unit, a network management and orchestration unit, a service management unit, a service orchestration unit, a service management, an orchestration unit, or a network.
  • the NM unit may be included in the operation support system (OSS) or may not be included in the OSS.
  • OSS operation support system
  • the network may also be referred to as a network slice or an end-to-end (E2E) network slice, and may include at least a core network (CN) part, an access network (AN) part, and a transport network (TN) portion; or the network may include any one of a CN portion, an AN portion, or a TN portion; or, the network may represent a network of the CN portion, a network of the AN portion, or a network of the TN portion .
  • the above network includes at least one network subnet. Logically, a network is a collection of network functions. The network subnet here can also be called a network slice subnet.
  • the domain management unit which may also be referred to as a network slice subnet management function (NSSMF) unit, includes one or all of the subnet management functions or the orchestration functions, and may have some or all of the following functions:
  • Domain management including subnet lifecycle management (create, update, delete), subnet fault management, subnet performance management, subnet configuration management, etc.; business management, including business lifecycle management, business fault management, and business Performance management, business configuration management, etc.; coordination of network resources (for example, NF) for unified orchestration.
  • subnet lifecycle management create, update, delete
  • subnet fault management subnet performance management
  • subnet configuration management etc.
  • business management including business lifecycle management, business fault management, and business Performance management, business configuration management, etc.
  • coordination of network resources for example, NF
  • the DM unit is used to indicate the network unit having the above functions, and does not impose any restrictions on the DM name. It may also be a domain slice management unit, a network slice subnet management unit, or other network elements.
  • the DM unit may be an independent management unit, or may be a logical entity in any one of the management units, such as a network management unit, a network orchestration unit, a network management and orchestration unit, a network element functional unit, a service management unit, and a service orchestration. Unit, domain management unit, business management and orchestration unit or NFVO.
  • the DM unit may or may not be included in the OSS.
  • the subnet referred to above may include one or more of the following: an AN portion, a CN portion, and a TN portion.
  • the subnet management unit can be considered as an AN DM unit.
  • the subnet management unit may be considered as a CN DM unit.
  • the subnet management unit can be considered as a Mix DM unit.
  • the management network element may be an NM unit or a DM unit, and may have different possibilities according to different implementation scenarios.
  • the embodiment of the present application may directly manage and interact with at least one NF instance and at least one NRF instance through an NM unit, or may indirectly manage at least one NF instance and at least one NRF instance and perform communication interaction by the NM unit through the DM unit.
  • the specific implementation method is described in detail in the following embodiments.
  • the management message may be sent to the at least one NF instance by the management unit of the NF instance. That is, the NM unit or the DM unit may send a message to the management unit of the NF instance, and then send it to the NF instance by the management unit of the NF instance. Since the destination terminal of the route is consistent, the following embodiment directly reflects that the NM unit or the DM unit sends a message to the NF instance, which may be considered to include the case where the message is sent to the NF instance through the management unit of the NF instance.
  • the embodiment of the present application provides a method for managing network function information, and a device and system based on the method.
  • the method includes: the management network element obtains the identifier information of the network warehouse function NRF instance, the NRF instance stores the information of the network function NF instance, the NRF instance identifier information is used to indicate the NRF instance associated with the NF instance, and the management network element is directed to the NF instance or
  • the management unit of the NF instance sends a first message, where the first message includes the identifier information of the NRF instance; or the management network element establishes an association relationship between the NF instance and the NRF instance according to the identifier information of the NRF instance.
  • the method may be as shown in FIG. 3, wherein the method shown in FIG.
  • the management network element may indicate the NRF instance associated with the NF instance to the NF instance, or may establish an association relationship between the NF instance and the NRF instance, so that the NF instance registers and updates with the NRF instance. Or query for information about other NF instances.
  • the NF instance may send a second message to the NRF instance, where the second message includes information about the NF instance, and the second message is used to indicate that the NRF instance saves or updates the NF instance. Information; or, the NF instance may send a third message to the NRF instance, and the third message is used to query the NRF instance for information of other NF instances.
  • the management unit of the NF instance may send the identifier information of the NRF instance to the NF instance.
  • the NF instance may send a second message to the NRF instance, where the second message includes information about the NF instance, and the second message is used to indicate that the NRF instance saves or updates the information of the NF instance; or
  • the NF instance may send a third message to the NRF instance, where the third message is used to query the NRF instance for information of other NF instances.
  • the NRF instance may save or update the information of the NF instance according to the second message; or the NRF instance may receive the third message according to the third message. Query information about other NF instances.
  • FIG. 4 is a schematic diagram of communication of another method for managing network function information according to an embodiment of the present application.
  • the management unit in FIG. 4 may be an NM unit, or may be a DM unit, or may be an EM unit or an NF Manager unit.
  • the method includes but is not limited to the following steps:
  • the management network element acquires the identifier information of the NRF instance, and the NRF instance stores the information of the NF instance.
  • the NRF instance is a network element for storing information of the NF instance, and the identification information of the NRF instance is information for uniquely indicating an NRF instance, and may include at least one of an identifier, a name, or a network address of the NRF instance.
  • the method for obtaining the identifier information of the NRF instance may be obtained from other network units, or may be determined from information stored by the NM unit or the DM unit itself, which is not limited herein.
  • the manner in which the NM unit obtains the identifier information of the NRF instance may be: receiving a management request message, where the management request message carries the identifier information of the NRF instance or the indication information of the NRF instance, where the NRF instance The indication information is used to obtain identification information of the NRF instance.
  • the management request message may be a creation request message of the NF instance (also referred to as an instantiation request message of the NF), a modification request message of the NF instance, or a configuration request message of the NF instance, or may be a network to which the NF instance belongs.
  • the configuration request message of the NF instance may be a creation request message of the management object corresponding to the NF instance, or may be a configuration request message of the management object corresponding to the NF instance; the configuration request message of the network slice or the network slice subnet may be a network.
  • the manner in which the NM unit obtains the identifier information of the NRF instance may be: obtaining the identifier information of the NRF instance described in the network template or the indication information of the NRF instance, where the indication information of the NRF instance is used to obtain the identifier information of the NRF instance.
  • the network template may be a network slice template, a network slice subnet template, or a network function template. It should be noted that the name of the network template is not limited herein, and the network template may also be referred to as a network descriptor, a blueprint, or the like.
  • the manner in which the NM unit obtains the identifier information of the NRF instance may be: determining the identifier information of the NRF instance according to the selection information of the NRF instance preset by the NM unit. For example, the NRF instance corresponding to the instance type of the NF instance is preset in the selection information of the NRF instance, and the NRF instance corresponding to the current configuration or the type of the created NF instance is determined, and the identifier information of the NRF instance is obtained.
  • the indication information of the NRF instance may include at least one of isolation requirement information, security information, location information, user information, and network information. That is, the NM unit determines the NRF instance that matches the indication information of the NRF instance and obtains the identification information of the NRF instance through the indication information of the NRF instance, or creates an NRF instance that conforms to the indication information of the NRF instance and acquires the identification information of the NRF instance.
  • the DM unit may obtain the identifier information of the NRF instance by receiving the management request message sent by the NM unit, where the management request message carries the identifier information of the NRF instance.
  • the management request message may be a modification request message of the NF instance or a configuration request message of the NF instance, or may be a creation request message, an instantiation request message, a modification request message, or a configuration request message of the network slice subnet to which the NF instance belongs. .
  • the configuration request message of the NF instance may be a creation request message of the management object corresponding to the NF instance, or may be a configuration request message of the management object corresponding to the NF instance;
  • the configuration request message of the network slice or the network slice subnet may be a network.
  • the creation request message of the management object corresponding to the slice or the network slice subnet or may be a configuration request message of the management object corresponding to the network slice or the network slice subnet.
  • the management network element may also establish an association relationship between the NF instance that needs to be configured and the NRF instance, so that when the related message including the first message is sent to the NF instance, The NRF instance associated with the NF instance can be directly obtained.
  • the form of the association relationship is not specifically limited, as long as it can indicate that the NF instance is associated with the NRF instance.
  • an association relationship table may be established, where the table includes the identification information of the NF instance and the identifier of the associated NRF instance. information.
  • the identification information of the NRF instance may be configured in the management object of the NF instance of the NM unit to indicate that the NF instance is associated with the NRF instance.
  • the management object of the NF instance is a log file that stores management information of the NF instance.
  • step S202, and steps S203 and S204 are optional steps, step S202 may be performed, or steps S203 and S204 may be performed.
  • the management network element sends a first message to the NF instance, where the first message includes the identifier information of the NRF instance.
  • the first message may be configured with a request message carrying the identification information of the NRF instance, and the identifier information of the NRF instance is used to indicate the NRF instance associated with the NF instance. That is, the NRF instance stores information of the NF instance, and the NF instance queries the NRF instance for information of other NF instances.
  • the information of the NF instance may also be carried in the first message.
  • the information of the NF instance includes at least one of an instance type, address information, domain name information, slice information of a network slice to which it belongs, a service area, or a discovery policy.
  • the management request message may further include information about the NF instance.
  • the first message may further include registration indication information, where the registration indication information is used to indicate whether the NF instance registers with the NRF instance.
  • the first message may further include access security information, and the access security information is used for access security verification of the NF instance by the NRF instance.
  • the management network element sends a first message to the management unit of the NF instance, where the first message includes the identifier information of the NRF instance.
  • the content of the first message may refer to the introduction in step S202, and details are not described herein again.
  • the management unit of the NF instance sends the identifier information of the NRF instance to the NF instance.
  • the management unit of the NF instance may send the first message including the identifier information of the NRF instance to the NF instance after receiving the first message; or the management unit of the NF instance may send the NRF to the NF instance by other means.
  • the identification information of the instance for example, the management unit of the NF instance may send the identification information of the NRF instance to the NF instance through other messages.
  • the management unit of the NF instance may also establish an association relationship between the NF instance that needs to be configured and the NRF instance, so as to send the related message including the second message to the NF instance.
  • the NRF instance associated with the NF instance can be obtained directly.
  • the form of the association relationship is not specifically limited, as long as it can indicate that the NF instance is associated with the NRF instance.
  • an association relationship table may be established, where the table includes the identification information of the NF instance and the identifier of the associated NRF instance. information.
  • the identifier information of the NRF instance may be configured in the management object of the NF instance maintained by the management network element to indicate that the NF instance is associated with the NRF instance.
  • the management object of the NF instance is a log file that stores management information of the NF instance.
  • steps S205 and S206, and steps S207 and S208 are optional steps, steps S205 and S206 may be performed, or steps S207 and S208 may be performed, or steps S205 and S206 and steps S207 and S208 may be performed. In the last case, the order of execution of steps S205 and S206, and steps S207 and S208 is not limited.
  • the NF instance sends a second message to the NRF instance, where the second message includes information of the NF instance.
  • the second message may be a registration request message or an update request message, the second message includes information of the NF instance, and the second message is used to instruct the NRF instance to save or update the information of the NF instance.
  • the second message may further include access security information, where the access security information is used for access security verification of the NF instance by the NRF instance.
  • the NF instance is triggered to send a registration request message to the NRF instance.
  • the method further includes:
  • the NF instance receives the activation request message, and the activation request message is used to activate the service corresponding to the NF instance or the NF instance to trigger the NF instance to send a registration request message to the NRF instance.
  • the method may further include:
  • the NF instance sends a fourth message to the NRF instance, where the fourth message is used to instruct the NRF instance to delete the information of the NF instance or set the information of the NF instance to be unavailable.
  • the fourth message is a de-registration request message of the service corresponding to the NF instance or the NF instance, and before the NF instance sends the fourth message to the NRF instance, the method further includes:
  • the NF instance receives the deactivation request message, and the deactivation request message is used to deactivate the service corresponding to the NF instance or the NF instance to trigger the NF instance to send a deregistration request message to the NRF instance.
  • the NRF instance saves or updates the information of the NF instance according to the second message.
  • the NRF instance saves the information of the NF instance.
  • the NRF instance updates the information of the NF instance.
  • the NF instance can directly register or update the information of the NF instance to the NRF instance, save the configuration time of the network function information, and optimize the configuration process.
  • the NF instance sends a third message to the NRF instance, where the third message is used to query the NRF instance for information of other NF instances.
  • the third message may be a query request message, and the third message may carry the service information that needs to be queried, and is used to query the NRF instance for information of other NF instances.
  • the method may further include:
  • the management network element sends a fifth message to the NRF instance, where the fifth message includes information of the NF instance.
  • the method may further include:
  • the terminal sends a service request to the NF instance to trigger the NF instance to send a third message to the NRF instance according to the service request.
  • the NRF instance queries information about other NF instances according to the third message.
  • the NRF instance queries and obtains information about an NF instance that can process the service corresponding to the service information according to the service information in the third message.
  • the NF instance can learn the NRF instance associated with itself and determine the information to query the NRF instance for other NF instances.
  • FIG. 5A is a schematic diagram of communication of another method for managing network function information according to an embodiment of the present application.
  • the management network element is an NM unit as an example.
  • the NM unit can directly communicate with the NF instance to manage the configuration of the NF instance.
  • the method includes but is not limited to the following steps:
  • the NM unit acquires the identifier information of the NRF instance, and the NRF instance stores the information of the NF instance.
  • the NRF instance is a network element for storing information of the NF instance, and the identification information of the NRF instance is information for uniquely indicating an NRF instance, and may include at least one of an identifier, a name, or a network address of the NRF instance.
  • the method for obtaining the identifier information of the NRF instance may be obtained from other network units, or may be determined from information stored by the NM unit or the DM unit itself, which is not limited herein.
  • the information of the NF instance may include at least one of an instance type, address information, domain name information, slice information of a network slice to which it belongs, a service area, an affiliated NF group information, or a discovery policy.
  • the address information of the NF instance may be an Internet Protocol (IP) address, a port address, or the like; the domain name information of the NF instance may be a fully qualified domain name (FQDN), and the full name domain name may be logically and accurately represented. Where the host is located, it can be said that the full name is a complete representation of the host name; the slice information of the network slice to which the NF instance belongs may include the network slice or the identification information of the network slice subnet, and may also include the network slice to which the NF instance belongs.
  • the subnet instance of the NF instance is the information of the area where the NF instance can provide services. That is, only the terminal or network unit in the service area can invoke the service provided by the NF instance; the discovery policy of the NF instance refers to the situation.
  • the next NF instance is able to be used by other terminals or networks.
  • the unit finds and calls, for example, when the load of the NF instance exceeds 80%, it cannot be called by other terminals or network units to provide services; the NF group information of the NF instance is used to identify the same type of the NF instance.
  • a collection of NF instances; an instance type of an NF instance can be any of the following:
  • AMF - access and mobility management function
  • DN - data network
  • operator services for example, operator services, Internet access or 3rd party services
  • 3rd party services for example, operator services, Internet access or 3rd party services
  • SDSF structured data storage network function
  • UDSF unstructured data storage network function
  • NEF network repository function
  • PCF policy control function
  • SMS session management function
  • gNBF generation node function
  • 5G base station function 5G base station function
  • eNBF evolved node B function
  • LTE eNBF evolved LTE evolved node B function
  • NBF Node B function
  • the NM unit determines to configure an NF instance, and may create an NRF instance or select an NRF instance in the existing NRF instance as an NRF instance that stores information of the NF instance, and obtain the Identification information of the NRF instance.
  • the manner in which the NM unit obtains the identification information of the NRF instance may be as follows:
  • the NM unit receives a management request message, and the management request message carries identification information of the NRF instance.
  • the management request message may be a creation request message of the NF instance (which may also be referred to as an instantiation request message of the NF), a modification request message of the NF instance, or a configuration request message of the NF instance.
  • the NM unit may determine the NF instance to be configured, and obtain the identifier information of the NRF instance associated with the NF instance, that is, the management request message carries the identifier of the NRF instance.
  • the NM unit may create an NF instance and obtain the identifier information of the NRF instance associated with the NF instance, that is, the management request message carries the identifier information of the NRF instance.
  • the NM unit receives a management request message, and the management request message carries indication information of the NRF instance.
  • the indication information of the NRF instance may include at least one of isolation requirement information, security information, location information, user information, and network information.
  • the isolation requirement information refers to the isolation requirement of the NRF instance or the isolation requirement of the network to which the NRF instance belongs (for example, complete isolation, hard isolation, soft isolation, etc.);
  • the security information refers to the security of the network to which the NRF instance or the NRF instance belongs.
  • the management request message may be a creation request message of the NF instance (which may also be referred to as an instantiation request message of the NF), a modification request message of the NF instance, or a configuration request message of the NF instance.
  • the NM unit may create an NRF instance that conforms to the indication information according to the indication information of the NRF instance or determine an NRF instance that matches the indication information in the existing NRF instance.
  • the NM unit may determine the NF instance to be configured, determine and obtain the identification information of the NRF instance associated with the NF instance according to the indication information, and receive the NF by the NM unit.
  • the request message is created, the NF instance may be created, and the identifier information of the NRF instance associated with the NF instance is determined and obtained according to the indication information.
  • the NM unit can select different NRF instances in the existing NRF instance according to the isolation requirement information, for example, the isolation requirement is high, and the isolation is good. For an NRF instance, the isolation requirement is low, and the NRF instance with weak isolation is selected.
  • the NM unit can also decide whether to create a new NRF instance or reuse an existing NRF instance according to the isolation requirement information. For example, if the isolation requirement is high, a new NRF instance is created. If the isolation requirement is low, an existing NRF instance that is already in use is reused.
  • the manner of determining the NRF instance based on the security information is similar to the method of determining the NRF instance according to the isolation requirement information, that is, the NRF instance with good security performance is selected when the security level is high, and the NRF instance with low security performance is selected when the security level is low; or the security level is high. Create a new NRF instance with a lower security level and reuse an existing NRF instance that is already in use.
  • the NM unit may select or create an NRF instance that is in the vicinity of the NF instance according to the deployment location of the NF instance.
  • the NM unit may store the information of all the NF instances of the same user on the same NRF instance according to the user information, or may be based on the user priority/level indicated by the user information.
  • a user with a high user priority/class selects a NRF instance with good performance, and selects a low-performance NRF instance for a user with a lower priority/lower rank.
  • the NM unit may select or create an NRF instance that can match the network information according to different network information.
  • the NM unit may comprehensively select or create a suitable NRF instance according to the indication information of the multiple NRF instances.
  • the NM unit obtains the identifier information of the NRF instance in the network template, where the network template describes the type or deployment information of a certain type of network, and is used to create or instantiate the network slice, the network slice subnet, or NF instance.
  • the network template can be a network slice template, a network slice subnet template, or a network function template.
  • the NM unit may pre-store the network template, and obtain the identifier information of the NRF instance corresponding to the NF instance from the network template when determining the configuration of an NF instance.
  • the NM unit obtains indication information of the NRF instance in the network template. Similar to the second possible case, the NM unit may create an NRF instance that conforms to the indication information according to the indication information of the NRF instance or determine an NRF instance that matches the indication information in the existing NRF instance.
  • the NM unit may determine the identification information of the NRF instance according to the selection information of the NRF instance preset by the NM unit. For example, the NRF instance corresponding to the instance type of the NF instance is preset in the selection information of the NRF instance, and the NRF instance corresponding to the current configuration or the type of the created NF instance is determined, and the identifier information of the NRF instance is obtained.
  • the NM unit decides to create a network slice or a network slice subnet, and the network slice or network slice subnet includes at least one NF instance, which is in a network slice or a network slice subnet.
  • the at least one NF instance creates a new NRF instance or selects an NRF instance in the existing NRF instance as an NRF instance that stores information of at least one NF instance.
  • the information of the at least one NF instance may be stored by one NRF instance in a unified manner, or may be stored by multiple NRF instances, which is not specifically limited herein.
  • the manner in which the NM unit obtains the identification information of the NRF instance may also be as follows:
  • the NM unit receives a management request message, and the management request message carries identification information of the NRF instance.
  • the management request message may be a creation request message, an instantiation request message, a modification request message, or a configuration request message of a network slice.
  • the NM unit may create or configure a network slice according to a network slice creation request message, an instantiation request message, a modification request message, or a configuration request message, where the network slice includes at least one NF instance, and acquires an NRF instance associated with at least one NF instance.
  • the identification information that is, the management request message carries the identification information of the NRF instance.
  • the NM unit receives a management request message, and the management request message carries indication information of the NRF instance.
  • the NM unit may create an NRF instance that conforms to the indication information according to the indication information of the NRF instance or determine an NRF instance that matches the indication information in the existing NRF instance.
  • the management request message may be a network slice creation request message, an instantiation request message, a modification request message, or a configuration request message.
  • the network slice is created or configured, the network slice includes at least one NF instance, and the at least one NF is determined and acquired according to the indication information. Identification information of the NRF instance associated with the instance. For a specific method, refer to the second possible case in the first possible implementation scenario.
  • the third to fifth possible cases are similar to the third to fifth possible cases in the first possible implementation scenario, and are not described here.
  • the NM unit may also establish an association relationship between the NF instance that needs to be configured and the NRF instance, so that when the related message including the first message is sent to the NF instance, Get the NRF instance associated with the NF instance directly.
  • the form of the association relationship is not specifically limited, as long as it can indicate that the NF instance is associated with the NRF instance.
  • an association relationship table may be established, where the table includes the identification information of the NF instance and the identifier of the associated NRF instance. information.
  • the identification information of the NRF instance may be configured in a management object of the maintained NF instance of the NM unit to indicate that the NF instance is associated with the NRF instance.
  • the management object of the NF instance is a log file that stores management information of the NF instance.
  • the NM unit sends a first message to the NF instance, where the first message includes the identifier information of the NRF instance.
  • the first message includes the identifier information of the NRF instance, and the identifier information of the NRF instance is used to indicate the NRF instance associated with the NF instance. That is, the information of the NF instance is saved and maintained by the NRF instance, and the NF instance can perform operations such as registration and inquiry to the NRF instance.
  • the first message can be a configuration request message.
  • the first message may further include information of the NF instance, and the information of the NF instance may be carried in the management request message.
  • the first message may further include registration indication information, where the registration indication information is used to indicate whether the NF instance registers with the NRF instance.
  • the first message carries the registration indication information, indicating that the NF instance is registered with the NRF instance; the first message does not carry the registration indication information, indicating that the NF instance does not register with the NRF instance.
  • the first message necessarily carries the registration indication information, and the registration indication message may be a bit that can indicate two indication states, for example, when set to 1, the NF instance is registered to the NRF instance, and is set to 0. Indicates that the NF instance is not registered with the NRF instance.
  • the first message does not carry the registration indication information, and the default NF instance is registered with the NRF instance.
  • the first message carries the registration indication information, and the NF instance is determined according to the indication of the registration indication information. Register with the NRF instance.
  • the NM unit can control whether the NF instance registers with the NRF instance, so that the NM instance cannot monitor the registration of the NF instance and is not convenient to manage.
  • the first message may further include access security information, and the access security information is used for access security verification of the NF instance by the NRF instance.
  • the access security information can be regarded as the key that the NF instance registers with the NRF instance.
  • the management unit of the NF instance may also establish the current information after obtaining the identification information of the NRF instance.
  • the association between the NF instance and the NRF instance is configured, so that when the related message including the second message is sent to the NF instance, the NRF instance associated with the NF instance can be directly obtained.
  • association relationship is not specifically limited, as long as it can indicate that the NF instance is associated with the NRF instance.
  • an association relationship table may be established, where the table includes the identification information of the NF instance and the identifier of the associated NRF instance. information.
  • the identification information of the NRF instance may be configured in the management object of the NF instance maintained by the NM unit to indicate that the NF instance is associated with the NRF instance.
  • the management object of the NF instance is a log file that stores management information of the NF instance.
  • the NF instance sends a second message to the NRF instance, where the second message includes information of the NF instance.
  • the second message may be a registration request message, which is used to indicate that the NRF instance saves the information of the NF instance. Further, when the information of the NF instance is included in the first message, the information of the NF instance included in the second message may be received from the first message; when the information of the NF instance is not included in the first message, The information of the NF instance included in the second message may be queried by the NF instance itself.
  • the NRF instance saves the information of the NF instance according to the second message.
  • the NF instance can directly register or update the information of the NF instance to the NRF instance, save the configuration time of the network function information, and optimize the configuration process.
  • S305 may also be included:
  • the NRF instance sends a first response message to the NF instance.
  • the first response message may be a registration request response message, which is used to indicate that the information storage of the NF instance by the NRF instance is completed.
  • S306 may also be executed before S303:
  • the NM unit sends an activation request message to the NF instance.
  • the activation request message is used to activate the service corresponding to the NF instance or the NF instance to trigger the NF instance to execute S203 to send a registration request message to the NRF instance. It can be considered that, in this case, the service corresponding to the NF instance or the NF instance is not activated before.
  • the NM unit sends an activation request message to the NF instance, the service corresponding to the NF instance or the NF instance is activated. Initiate registration with the NRF instance.
  • the NF instance is a logical entity that can provide related network services.
  • the activation request message can directly activate the NF instance, and can also activate the corresponding service provided by the NF instance.
  • the NF instance is registered with the NRF instance in the active state to prevent the NRF instance from indicating the route to the inactive NF instance when the service query is performed, causing the service to fail.
  • S307 or S305 may further perform S307-S308:
  • the NF instance sends a second message to the NRF instance, where the second message includes information of the NF instance.
  • the second message may be sent to the NRF instance.
  • the second message may be a first update request message, used to instruct the NRF instance to update the information of the NF instance.
  • the information of the NF instance refers to the update information of the NF instance
  • the update information may be the information of the updated complete NF instance, or may be the information of the NF instance currently stored in the NRF instance (for example, S304).
  • the differentiated information of the information of the saved NF instance is not specifically limited herein.
  • the information of the NF instance may include the updated slice information and a complete NF instance of other information such as instance type, address information, domain name information, service area, or discovery policy;
  • the information of the instance may also include only the updated slice information, that is, the differentiated information.
  • the NRF instance updates the information of the NF instance according to the second message.
  • S309 can also be executed:
  • the NM unit sends a fifth message to the NF instance, where the fifth message includes information of the NF instance.
  • the fifth message may be sent to the NF instance.
  • the fifth message may be a second update request message for indicating that the NF instance updates the information to the NRF unit.
  • the information of the NF instance herein also refers to the update information of the NF instance, and the update information may be the information of the updated complete NF instance, or may be the information of the NF instance currently stored in the NRF instance (for example, The differentiated information of the information of the NF instance stored in S304 is not specifically limited herein.
  • S310 may also be performed:
  • the NRF instance sends a second response message to the NF instance.
  • the second response message may be an update request response message for indicating that the information update of the NRF instance to the NF instance is completed.
  • S311-S312 can also be executed:
  • the NF instance sends a fourth message to the NRF instance.
  • the fourth message is a message for instructing the NRF instance to delete the NF instance or set the information of the NF instance to be unavailable.
  • the fourth message may be a deregistration request message or a deletion request message, etc. limited.
  • S312 The NRF instance deletes the information of the NF instance or sets the information of the NF instance to be unavailable.
  • the route will not be instructed to the NF instance when the service query is performed.
  • S313 can also be executed:
  • the NM unit sends a deactivation request message to the NF instance.
  • the deactivation request message is used to deactivate the service corresponding to the NF instance or the NF instance to trigger the NF instance to perform S308 to send the fourth message to the NRF instance. It can be considered that in this case, the service corresponding to the NF instance or the NF instance has been previously activated.
  • the NM unit sends a deactivation request message to the NF instance, the service corresponding to the NF instance or the NF instance is deactivated. Send a fourth message to the NRF instance.
  • the NRF instance is triggered to delete the information of the NF instance or set the information of the NF instance to be unavailable, preventing the NF instance from being found to be incorrect or unavailable.
  • S314 may also be included:
  • the NRF instance sends a third response message to the NF instance.
  • the third response message may be a deregistration request response message or a deletion request response message, etc., for explaining that the NRF instance deletes the information of the NF instance or sets the operation to be unavailable.
  • FIG. 5B is a schematic diagram of communication of another method for managing network function information according to an embodiment of the present application.
  • the management network element is an NM unit as an example.
  • the NM unit communicates with the NF instance through the DM unit to manage the configuration of the NF instance.
  • the method includes but is not limited to the following steps:
  • the NM unit acquires the identifier information of the NRF instance, and the NRF instance stores the information of the NF instance.
  • the NM unit sends a sixth message to the DM unit, where the sixth message includes identifier information of the NRF instance.
  • the sixth message includes the identifier information of the NRF instance, and may be a modification request message of the NF instance or a configuration request message of the NF instance, or may be a creation request message, an instantiation request message, a modification request message, or a configuration request of the network slice subnet.
  • the configuration request message of the NF instance may be a creation request message of the management object corresponding to the NF instance; or may be a configuration request message of the management object corresponding to the NF instance; the configuration request message of the network slice or the network slice subnet may be a network
  • the NM unit determines to configure an NF instance
  • the sixth message is a modification request message of the NF instance or a configuration request message of the NF instance, and may carry the identifier information of the NRF instance and the identifier information of the NF instance. And indicating that the DM unit sends the first message to the NF instance to establish an association between the NF instance and the NRF instance.
  • the configuration request message of the NF instance may be a creation request message of the management object corresponding to the NF instance, or may be a configuration request message of the management object corresponding to the NF instance.
  • the NM unit decides to create a network slice or a network slice subnet
  • the sixth message is a network slice subnet creation request message, an instantiation request message, a modification request message, or a configuration request message.
  • the identifier information of the NRF instance and the identifier information of the network slice subnet created by the NM unit (for example, a network slice subnet identifier (NSSI), which is used to indicate that the DM unit creates or configures the network slice subnet.
  • NSSI network slice subnet identifier
  • the configuration request message of the network slice or the network slice subnet may be a network slice or a network slice subnet.
  • the creation request message of the corresponding management object may be a configuration request message of a management object corresponding to the network slice or the network slice subnet.
  • the NM unit or the DM unit may also establish an association relationship between the NF instance that needs to be configured and the NRF instance, so as to send the related message including the first message to the NF instance.
  • the NRF instance associated with the NF instance can be obtained directly.
  • the form of the association relationship is not specifically limited, as long as it can indicate that the NF instance is associated with the NRF instance.
  • an association relationship table may be established, where the table includes the identification information of the NF instance and the identifier of the associated NRF instance. information.
  • the identification information of the NRF instance may be configured in the management object of the NF instance maintained by the NM unit to indicate that the NF instance is associated with the NRF instance.
  • the management object of the NF instance is a log file that stores management information of the NF instance.
  • the DM unit sends a first message to the NF instance, where the first message includes identifier information of the NRF instance.
  • the management unit of the NF instance may also establish the current configuration after obtaining the identification information of the NRF instance.
  • association relationship is not specifically limited, as long as it can indicate that the NF instance is associated with the NRF instance.
  • an association relationship table may be established, where the table includes the identification information of the NF instance and the identifier of the associated NRF instance. information.
  • the identification information of the NRF instance may be configured in the management object of the NF instance maintained by the DM unit to indicate that the NF instance is associated with the NRF instance.
  • the management object of the NF instance is a log file that stores management information of the NF instance.
  • the NF instance sends a second message to the NRF instance, where the second message includes information of the NF instance.
  • the NRF instance saves the information of the NF instance according to the second message.
  • S406 may also be included:
  • the NRF instance sends a first response message to the NF instance.
  • S407-S408 is also included:
  • the NM unit sends a first activation request message to the DM unit.
  • the first activation request message may carry the identifier information of the NF instance, and may also carry the identifier information of the network slice subnet. Specifically, when the NM unit activates the service corresponding to the NF instance or the NF instance, the first activation request message may carry the identifier information of the NF instance; when the NM unit activates at least one NF instance included in the network slice subnet. When the service corresponding to the at least one NF instance is used, the first activation request message may carry the identifier information of the network slice subnet.
  • the DM unit sends a second activation request message to the NF instance according to the first activation request message.
  • the DM unit determines the corresponding NF instance according to the identifier information of the NF instance or the identifier information of the network slice subnet carried in the first activation request message, and sends a second activation request message to the NF instance.
  • the second activation request message is used to activate the NF instance or the service corresponding to the NF instance to trigger the NF instance to send a registration request message to the NRF instance.
  • S408 refer to S306, and details are not described herein again.
  • S405 or S406 may further perform S409-S410:
  • the NF instance sends a second message to the NRF instance, where the second message includes information of the NF instance.
  • the NRF instance updates the information of the NF instance according to the second message.
  • the NM unit sends a seventh message to the DM unit, where the seventh message includes information of the NF instance.
  • the seventh message may be sent to the DM instance.
  • the seventh message may be a third update request message, configured to instruct the DM unit to send a fifth message to the NF instance to trigger the NF instance to update the information to the NRF instance.
  • the DM unit sends a fifth message to the NF instance, where the fifth message includes information of the NF instance.
  • S413 may also be executed:
  • the NRF instance sends a second response message to the NF instance.
  • S414-S415 can also be executed:
  • the NF instance sends a fourth message to the NRF instance.
  • the NRF instance deletes the information of the NF instance or sets the information of the NF instance to be unavailable.
  • S415-S416 can also be executed:
  • the NM unit sends a first deactivation request message to the DM unit.
  • the first deactivation request message may carry the identifier information of the NF instance, and may also carry the identifier information of the network slice subnet. Specifically, when the NM unit deactivates the service corresponding to the NF instance or the NF instance, the first activation request message may carry the identifier information of the NF instance; when the NM unit deactivates at least one of the network slice subnets When the NF instance or the at least one NF instance corresponds to the service, the first activation request message may carry the identifier information of the network slice subnet.
  • the DM unit sends a second deactivation request message to the NF instance.
  • the DM unit determines the corresponding NF instance according to the identifier information of the NF instance or the identifier information of the network slice subnet carried in the first deactivation request message, and sends a second deactivation request message to the NF instance.
  • the second deactivation request message is used to deactivate the NF instance or the service corresponding to the NF instance to trigger the NF instance to send a fourth message to the NRF instance.
  • S416 refer to S313, and details are not described herein again.
  • S417 may also be included:
  • the NRF instance sends a third response message to the NF instance.
  • FIG. 6A is a schematic diagram of communication of another method for managing network function information according to an embodiment of the present application.
  • the management network element is an NM unit as an example.
  • the NM unit can directly communicate with the NF instance to manage the configuration of the NF instance.
  • the method includes but is not limited to the following steps:
  • the NM unit acquires the identifier information of the NRF instance and the information of the NF instance, where the NRF instance stores the information of the NF instance.
  • the information of the NF instance may be carried in the received management request message.
  • the NM unit sends a first message to the NF instance, where the first message includes the identifier information of the NRF instance.
  • the first message includes the identifier information of the NRF instance, and the identifier information of the NRF instance is used to indicate the NRF instance associated with the NF instance. That is, the information of the NF instance is saved and maintained by the NRF instance, and the NF instance can perform operations such as registration and inquiry to the NRF instance.
  • the first message may be a second configuration request message.
  • the NM unit can indicate to the NF instance the NRF instance associated with the NF instance.
  • the NM unit sends an eighth message to the NRF instance, where the eighth message includes information of the NF instance.
  • the eighth message may be a third configuration request message, where the information of the NF instance is used to indicate that the NRF saves the information of the NF instance.
  • the NRF instance saves the information of the NF instance according to the eighth message.
  • the terminal sends a service request message to the NF instance.
  • the service request message is used to request one or more network services from the NF instance. Since the current NF instance cannot provide all the network services requested by the terminal, the terminal needs to query the NRF for other NF instances that can provide the service requested by the terminal.
  • the NF instance sends a third message to the NRF instance according to the service request message.
  • the third message may be an NF instance query request message, configured to query the NRF instance for information of other NF instances according to the service request message.
  • the third message may carry the service information requested in the service request message.
  • the NRF instance queries information about other NF instances according to the third message.
  • the NRF instance queries, according to the third message, information of the other NF instances that can provide the service of the third message request in the information of the stored at least one NF instance.
  • the NRF instance sends the query result to the NF instance.
  • the NNF instance may send the information such as the network address of the NF instance to the NF instance, so that the NF instance routes the service request message to other NF instances.
  • FIG. 6B is a schematic diagram of communication of another method for managing network function information according to an embodiment of the present application.
  • the management network element is an NM unit as an example.
  • the NM unit communicates with the NF instance through the DM unit to manage the configuration of the NF instance.
  • the method includes but is not limited to the following steps:
  • the NM unit acquires the identifier information of the NRF instance, and the NRF instance stores the information of the NF instance.
  • the NM unit sends a seventh message to the DM unit, where the seventh message includes identifier information of the NRF instance.
  • the seventh message may be a first configuration request message including identification information of the NRF instance and information of the NF instance. It should be noted that the information of the NF instance may be obtained by the NM unit, and the information of the NF instance may be carried in the seventh message; the information of the NF instance may also be obtained in advance by the DM unit. You may not carry the information of the NF instance.
  • the DM unit sends a first message to the NF instance, where the first message includes identifier information of the NRF instance.
  • the NM unit can indicate to the NF instance through the DM unit the NRF instance associated with the NF instance.
  • the DM unit sends a ninth message to the NRF instance, where the ninth message includes information of the NF instance.
  • the ninth message may be a fourth configuration request message, where the information of the NF instance is used to indicate that the NRF saves the information of the NF instance.
  • the NRF instance saves the information of the NF instance according to the ninth message.
  • the terminal sends a service request message to the NF instance.
  • the NF instance sends a third message to the NRF instance according to the service request message.
  • the NRF instance queries information about other NF instances according to the third message.
  • the NRF instance sends the query result to the NF instance.
  • FIG. 7 is a schematic flowchart diagram of still another method for managing network function information according to an embodiment of the present application.
  • the management unit in FIG. 7 may be an NM unit or a DM unit.
  • the method includes but is not limited to the following steps:
  • the management network element acquires the identifier information of the NRF instance, and the NRF instance stores the information of the NF instance.
  • the management network element establishes an association relationship between the NF instance and the NRF instance according to the identifier information of the NRF instance.
  • the management network element can establish an association relationship between the NF instance and the NRF instance that needs to be configured, so that when the related message including the first message is sent to the NF instance, the information can be directly obtained.
  • An NRF instance associated with an NF instance It should be noted that the form of the association relationship is not specifically limited, as long as it can indicate that the NF instance is associated with the NRF instance. For example, an association relationship table may be established, where the table includes the identification information of the NF instance and the identifier of the associated NRF instance. information.
  • the management network element may configure the identifier information of the NRF instance in the management object of the NF instance, and the identifier information of the NRF instance is used to indicate the NRF instance associated with the NF instance.
  • the management object of the NF instance is a log file for managing management information of the NF instance in the management network element.
  • the management network element can establish an association relationship between the NF instance and the NRF instance, so that the NF instance can be instructed to register, update, or query information of other NF instances to the NRF instance.
  • the management network element may further send a first message to the NF instance, where the first message includes the identifier information of the NRF instance.
  • the first message may be configured with a request message carrying the identification information of the NRF instance, and the identifier information of the NRF instance is used to indicate the NRF instance associated with the NF instance. That is, the NRF instance stores information of the NF instance, and the NF instance queries the NRF instance for information of other NF instances.
  • the NF instance can directly register or update the information of the NF instance to the NRF instance, save the configuration time of the network function information, and optimize the configuration process.
  • the solution provided by the embodiment of the present application is mainly introduced from the perspective of interaction between different management units.
  • the management unit of the management network element, the NF instance, the NRF instance, and the NF instance includes corresponding hardware structures and/or software modules for performing the respective functions in order to implement the above functions.
  • the embodiments of the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements of the examples and algorithm steps described in the embodiments disclosed in the application. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the technical solutions of the embodiments of the present application.
  • the embodiments of the present application may perform functional module division on a management network element, an NF instance, an NRF instance, a management unit of an NF instance, and the like according to the foregoing method example.
  • each functional module may be divided according to each function, or two or two may be divided. More than one function is integrated in one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 8A shows a possible schematic block diagram of a management network element involved in the embodiment of the present application.
  • the management network element 800 includes a processing module 802 and a communication module 803.
  • the processing module 802 is configured to control and manage the action of the management network element.
  • the processing module 802 is configured to support the management network element 800 or support the management network element 800 through the communication module 803 to perform the processes S101-S103 in FIG. Process S201-S203, process S301, S302, S306, S309, S313 in FIG. 5A, processes S401-S403, S407, S408, S411, S412, S415, S416 in FIG. 5B, process S501-S503 in FIG.
  • the communication module 803 is configured to support communication between the management network element 800 and the NF instance, the management unit of the NF instance, the NRF instance, other management network elements, or other devices.
  • the management network element 800 may further include a storage module 801 for storing program codes and data of the management network element 800.
  • the processing module 802 can be a processor or a controller, and can be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 803 can be a communication interface, a transceiver, or a transceiver circuit.
  • the communication interface is a generic name.
  • the communication interface can include multiple interfaces, for example, the management network element 800 and the NF instance, and the NF.
  • the storage module 801 can be a memory.
  • the management network element involved in the embodiment of the present application may be the management network element 810 shown in FIG. 8B.
  • the management network element 810 includes a processor 812, a communication interface 813, and a memory 811.
  • the management network element 810 may further include a bus 814.
  • the communication interface 813, the processor 812, and the memory 811 may be connected to each other through a bus 814.
  • the bus 814 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 814 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 8B, but it does not mean that there is only one bus or one type of bus.
  • the management network element shown in FIG. 8A and FIG. 8B above may be "NM unit/NSMF unit” or "DM unit/NSSMF unit” in FIG. 2.
  • FIG. 9A shows a possible schematic block diagram of an NF instance involved in the embodiment of the present application.
  • the NF instance 900 includes a processing module 902 and a communication module 903.
  • the processing module 902 is configured to perform control management on the actions of the NF instance 900.
  • the processing module 902 is configured to support the NF instance 900 by the communication module 903 to perform processes S205 and S207 in FIG. 4, processes S303, S307, and S311 in FIG. 5A.
  • the communication module 903 is configured to support communication between the NF instance 900 and a management unit, an NRF instance, or a management unit of an NF instance.
  • the NF instance 900 can also include a storage module 901 for program code and data for the NF instance 900.
  • the processing module 902 can be a processor or a controller, such as a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 903 can be a communication interface, a transceiver or a transceiver circuit, etc., wherein the communication interface is a collective name.
  • the communication interface can include multiple interfaces, for example, the NF instance 900 and the management network element, and the NRF.
  • the storage module 901 can be a memory.
  • the processing module 902 is a processor
  • the communication module 903 is a communication interface
  • the storage module 901 is a memory
  • the NF instance involved in the embodiment of the present application may be the NF instance shown in FIG. 9B.
  • the NF instance 910 includes a processor 912, a communication interface 913, and a memory 911.
  • the NF instance 910 can also include a bus 914.
  • the communication interface 913, the processor 912, and the memory 911 may be connected to each other through a bus 914; the bus 914 may be a PCI bus or an EISA bus or the like.
  • the bus 914 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9B, but it does not mean that there is only one bus or one type of bus.
  • the NF instance shown in FIGS. 9A and 9B above may be the NF instance in FIG. 1.
  • An embodiment of the present application further provides an NRF instance.
  • the structure of the NRF is similar to the structure of the NF instance, as shown in FIG. 10A and FIG. 10B.
  • the module or device included in the NRF example may perform the operations performed by the NRF instance involved in the foregoing method, and details are not described herein.
  • the embodiment of the present application further provides a management unit of an NF instance.
  • the structure of the management unit of the NF instance is similar to the structure diagram of the management network element, as shown in FIG. 11A and FIG. 11B.
  • the module or device included in the management unit of the NF instance may correspond to the operations performed by the management unit of the NF instance involved in the foregoing method, and details are not described herein.
  • the steps of the method or algorithm described in connection with the disclosure of the embodiments of the present application may be implemented in a hardware manner, or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC.
  • the ASIC can be located in a management unit of a management network element, an NF instance, an NRF instance, or an NF instance.
  • the processor and the storage medium may also exist as discrete components in the management unit of the management network element, the NF instance, the NRF instance, or the NF instance.
  • the functions described in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the processes or functions described in accordance with embodiments of the present application are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital video disc (DVD)), or a semiconductor medium (for example, a solid state disk (SSD)). )Wait.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a digital video disc (DVD)
  • DVD digital video disc
  • SSD solid state disk

Landscapes

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

Abstract

本申请实施例公开一种网络功能信息的管理方法及相关设备。方法包括：管理网元获取NRF实例的标识信息，NRF实例中存储NF实例的信息，其中，该标识信息用于指示与NF实例关联的NRF实例；管理网元向NF实例或NF实例的管理单元发送第一消息，第一消息包括NRF实例的标识信息；或者，管理网元根据NRF实例的标识信息，建立NF实例与NRF实例的关联关系。本申请实施例的方案，有利于NF实例向该NRF实例注册、更新或查询其他NF实例的信息。

Description

网络功能信息的管理方法及相关设备 技术领域
本申请实施例涉及通信领域，尤其涉及一种网络功能信息的管理方法及相关设备。
背景技术
随着通信技术的发展，人们对下一代网络的要求也越来越高。例如，下一代网络需要满足不同行业、不同用户对网络的不同要求，有针对性地为不同用户提供个性化的网络服务。网络的服务化架构就是实现这一目标的重要技术手段。基于网络的服务化架构，网络侧可以根据终端的业务请求或者同时结合网络的实时情况，动态地调整网络路由，从而满足终端的业务请求。
为了实现网络的服务化架构，引入了网络仓库功能(network repository function，NRF)实例。NRF实例是用于保存和维护网络功能(network function，NF)实例的信息的逻辑实体。当收到用户的业务请求时，NF实例可以通过向NRF实例查询能够提供用户请求的网络业务的NF实例，从而确定下一跳路由。
现有网络的服务化架构中，通常只存在一个NRF实例，NF实例可以直接向该NRF实例发起注册、查询等流程。然而，随着服务化架构的不断进步，希望采用多个NRF实例来存储NF实例的信息，以便不同网络、地域等特性的NF实例的信息可以隔离存储在不同的NRF实例中。在这种情况下，如何确定每个NRF实例负责存储和维护哪些NF实例的信息，目前成为了优化网络的服务化架构中亟待解决的问题。
发明内容
本申请实施例描述了一种网络功能信息的管理方法及相关设备，以期优化网络的服务化架构。
一方面，本申请实施例提供了一种网络功能信息的管理方法，该方法包括：管理网元获取网络仓库功能NRF实例的标识信息，NRF实例中存储网络功能NF实例的信息，NRF实例的标识信息用于指示与NF实例关联的NRF实例；然后，管理网元向NF实例或者NF实例的管理单元发送第一消息，第一消息包括NRF实例的标识信息；然后NF实例根据第一消息确定关联的NRF实例，并向NRF实例进行注册、更新，或查询其他NF实例的信息。本申请实施例的方案中，在存在多个NRF实例时，管理网元可以向NF实例指示与该NF实例关联的NRF实例，从而NF实例可以直接向NRF实例进行注册、更新NF实例的信息，优化配置流程；或者，NF实例可以确定向哪一个NRF实例查询其他NF实例的信息。
或者，该方法包括：
管理网元获取网络仓库功能NRF实例的标识信息，NRF实例中存储网络功能NF实例的信息，NRF实例的标识信息用于指示与NF实例关联的NRF实例；然后，管理网元根据NRF实例的标识信息，建立NF实例与NRF实例的关联关系。本申请实施例的方案中，在存在多个NRF实例时，获取NRF实例的标识信息以建立NF实例与NRF实例的关联关系，从而便于后续指示NF实例向该NRF实例注册、更新或查询其他NF实例的信息。
在一种可能的实施方式中，上述第一消息还包括所述NF实例的信息。
在一种可能的实施方式中，管理网元在NF实例的管理对象中配置NRF实例的标识信息。
在一种可能的实施方式中，上述获取网络仓库功能NRF实例的标识信息的方式可以包括以下之一或全部：接收管理请求消息，所述管理请求消息包括NRF实例的标识信息或NRF实例的指示信息，NRF实例的指示信息用于获取NRF实例的标识信息；或者，获取网络模板中描述的NRF实例的标识信息或NRF实例的指示信息，NRF实例的指示信息用于获取NRF实例的标识信息。
在一种可能的实施方式中，上述NRF实例的指示信息可以包括以下至少一项：隔离需求信息、安全信息、位置信息、用户信息以及网络信息。
在一种可能的实施方式中，上述第一消息包括NF实例的信息，上述管理请求消息还可以包括NF实例的信息。
在一种可能的实施方式中，上述第一消息还包括注册指示信息，注册指示信息用于指示NF实例是否向NRF实例注册。
在一种可能的实施方式中，上述NRF实例的标识信息可以包括以下至少一项：NRF实例的标识、NRF实例的名称或NRF实例的网络地址。
在一种可能的实施方式中，上述NF实例的信息可以包括以下至少一项：实例类型、地址信息、域名信息、所属网络切片的切片信息、服务区域、所属NF组信息或发现策略。
另一方面，本申请实施例提供了另一种网络功能信息的管理方法，该方法包括：NF实例接收第一消息，第一消息包括存储NF实例的信息的NRF实例的标识信息，NRF实例的标识信息用于指示与所述NF实例关联的所述NRF实例；NF实例接收第一消息后，向NRF实例发送第二消息，第二消息包括NF实例的信息，第二消息用于指示NRF实例保存或更新NF实例的信息；或者，NF实例接收第一消息后，向NRF实例发送第三消息，第三消息用于向NRF实例查询其他NF实例的信息。本申请实施例的方案中，在存在多个NRF实例时，管理网元向NF实例发送第一消息以指示与NF实例关联的NRF实例，从而NF实例可以直接向NRF实例发送第二消息以进行注册、更新NF实例的信息，优化配置流程；或者，NF实例可以确定向哪一个NRF实例并向NRF实例发送第三消息查询其他NF实例的信息。
在一种可能的实施方式中，上述第一消息还包括NF实例的信息。
在一种可能的实施方式中，上述第二消息为NF实例或NF实例对应的服务的注册请求消息，NF实例向NRF实例发送第二消息之前，NF实例还可以接收激活请求消息，激活请求消息用于激活NF实例或者NF实例对应的服务，以触发NF实例向NRF实例发送注册请求消息。
在一种可能的实施方式中，NF实例还可以向NRF实例发送第四消息，第四消息用于指示NRF实例删除NF实例的信息或将NF实例的信息设置为不可用。
在一种可能的实施方式中，上述第四消息为NF实例或NF实例对应的服务的去注册请求消息，NF实例向NRF实例发送第四消息之前，NF实例还可以接收去激活请求消息，去激活请求消息用于去激活NF实例或者NF实例对应的服务，以触发NF实例向NRF实例发送去注册请求消息。
又一方面，本申请实施例提供一种管理网元，该管理网元具有实现上述方法设计中管 理网元行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，管理网元包括处理器，所述处理器被配置为支持管理网元执行上述方法中相应的功能。进一步的，管理网元还可以包括通信接口，所述通信接口用于支持管理网元与NF实例、NF实例的管理单元、NRF实例、其他管理网元或其他设备之间的通信。进一步的，管理网元还可以包括存储器，所述存储器用于与处理器耦合，其保存管理网元必要的程序指令和数据。
又一方面，本申请实施例提供一种NF实例，该NF实例具有实现上述方法设计中NF实例行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，该NF实例包括处理器，所述处理器被配置为支持NF实例执行上述方法中相应的功能。进一步的，该NF实例还可以包括通信接口，所述通信接口用于支持NF实例与管理网元、NRF实例或NF实例的管理单元或其他单元之间的通信。进一步的，NF实例还可以包括存储器，所述存储器用于与处理器耦合，其保存NF实例必要的程序指令和数据。
又一方面，本申请实施例提供一种NRF实例，该NRF实例具有实现上述方法设计中NRF实例行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，该NRF实例包括处理器，所述处理器被配置为支持NRF实例执行上述方法中相应的功能。进一步的，该NRF实例还可以包括通信接口，所述通信接口用于支持NRF实例与管理网元、NF实例或NF实例的管理单元或其他设备之间的通信。进一步的，NRF实例还可以包括存储器，所述存储器用于与处理器耦合，其保存NRF实例必要的程序指令和数据。
又一方面，本申请实施例提供一种NF实例的管理单元，该NF实例的管理单元具有实现上述方法设计中NF实例的管理单元行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，该NF实例的管理单元包括处理器，所述处理器被配置为支持NF实例的管理单元执行上述方法中相应的功能。进一步的，该NF实例的管理单元还可以包括通信接口，所述通信接口用于支持NF实例的管理单元与管理网元、NRF实例或NF实例或其他设备之间的通信。进一步的，NF实例的管理单元还可以包括存储器，所述存储器用于与处理器耦合，其保存NF实例的管理单元必要的程序指令和数据。
再一方面，本申请实施例提供一种通信系统，该通信系统包括上述方面所述的管理网元和NF实例；或者，该通信系统包括上述方面所述的管理网元、NF实例和NRF实例；或者，该通信系统包括上述方面所述的管理网元、NF实例、NF实例的管理单元和NRF实例。
再一方面，本申请实施例提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
再一方面，本申请实施例提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
相较于现有技术，本申请实施例的方案中，管理网元能够向NF实例指示与NF实例关联的NRF实例，或者，管理网元能够建立NF实例与NRF实例之间的关联关系，从而能够确定每个NRF实例负责存储和维护哪些NF实例的信息，有利于NF实例向该NRF实例发起注册、查询等流程。
附图说明
图1是本申请实施例提供的一种可能的网络结构示意图；
图2是本申请实施例提供的一种OAM系统的结构示意图；
图3是本申请实施例提供的一种网络功能信息的管理方法的通信示意图；
图4是本申请实施例提供的另一种网络功能信息的管理方法的通信示意图；
图5A是本申请实施例提供的又一种网络功能信息的管理方法的通信示意图；
图5B是本申请实施例提供的又一种网络功能信息的管理方法的通信示意图；
图6A是本申请实施例提供的又一种网络功能信息的管理方法的通信示意图；
图6B是本申请实施例提供的又一种网络功能信息的管理方法的通信示意图；
图7是本申请实施例提供的又一种网络功能信息的管理方法的流程示意图；
图8A为本申请实施例提供的一种管理网元的结构示意图；
图8B为本申请实施例提供的另一种管理网元的结构示意图；
图9A为本申请实施例提供的一种网络功能实例的结构示意图；
图9B为本申请实施例提供的另一种网络功能实例的结构示意图；
图10A为本申请实施例提供的一种网络仓库功能实例的结构示意图；
图10B为本申请实施例提供的另一种网络仓库功能实例的结构示意图；
图11A为本申请实施例提供的一种网络功能实例的管理单元的结构示意图；
图11B为本申请实施例提供的另一种网络功能实例的管理单元的结构示意图。
具体实施方式
下面结合本申请实施例中的附图对本申请实施例进行描述。
请参见图1，图1是本申请实施例提供的一种可能的网络架构的示意图，包括操作管理维护(operation administration and maintenance，OAM)系统、网络功能(network function，NF)实例和网络仓库功能(network repository function，NRF)实例。
其中，OAM系统，是对运营商用来进行网络管理的各种网络实体的统一称呼。OAM系统的功能主要包括：完成日常网络和业务进行的分析、预测、规划和配置工作；对网络及其业务的测试和故障管理等进行的日常操作活动。
NF实例，是指独立的可执行计算、存储、网络通信功能的虚拟或者物理逻辑网络功能。本申请实施例所涉及的NF实例，可以指核心网(core network，CN)的NF实例，例如接入管理功能实例(access management function instance，AMF Instance)，会话管理功能实例(session management function instance，SMF Instance)等，也可以指接入网(access network，AN)的NF实例，比如5G基站功能实例(5G nodeB function instance)，eLTE eNB function实例，eNB function实例等。
NRF实例，也被称为网络功能仓库功能实例，是用于保存和维护NF实例的信息的逻辑 实体，当收到用户的业务请求时，NF实例可以通过向NRF实例查询获取能够提供用户请求的网络业务的其他NF实例，从而确定下一跳路由。
在图1所示的网络架构中，OAM系统管理至少一个NF实例(图1中展示出了NF1、NF2、NF3和NF4)以及至少一个NRF实例(图1中展示出了NRF1和NRF2)并与它们进行通信交互。其中，NF实例与其对应的NRF实例之间也可以进行通信交互，例如图1所示的NF1和NF2分别与NRF1关联，即NRF1保存和维护NF1和NF2的信息，那么NF1和NF2分别可以与NRF1进行通信交互。
需要说明的是，如图1所示，本申请还适用于多个NF实例由NF实例的管理单元统一管理的场景。在该场景中，OAM系统管理至少一个NF实例时，可以通过NF实例的管理单元向至少一个NF实例发送管理消息。其中，NF实例的管理单元可以为网元管理(element manager，EM)单元，也可以为网络功能管理(network function manager，NFM)单元，也可以是域管理(domain management，DM)单元，这里不作具体限定。
进一步的，请参见图2，图2是本申请实施例提供的一种OAM系统的结构示意图，包括业务支撑系统(business support system，BSS)、网络管理(network management，NM)单元以及域管理(domain management，DM)单元，其中：
业务支撑系统或业务管理(service management，SM)单元，用于接收相关租户的业务需求并转换为网络切片相关的需求，然后进行业务相关的管理。
网络管理单元，也可以称为网络切片管理功能(network slice management function，NSMF)单元，包括端到端网络管理功能或者端到端网络编排功能之一或者全部，可以具备以下部分或者全部功能：
端到端网络的管理(例如，网络的生命周期管理、网络模板的管理、网络的故障管理、网络的性能管理和网络的配置管理)；端到端网络和子网络以及网络功能的映射；不同域(例如接入网域、核心网域和传输域)提供的网络资源或者子服务水平协议(sub-service level agreement，sub-SLA)的协调；分解网络需求信息为子网需求信息；对各子域提供的子网络和网络功能的统一编排，以使得不同子域提供的子网或者网络功能可以满足目标业务或者网络的需求，例如，SLA的要求，关键性能指标(key performance indicator，KPI)的要求以及服务质量(quality of service，QoS)的要求。
需要说明的是，NM单元是用于表示具有上述功能的网络单元，并不对NM单元的名称作任何限制，还可以是跨域管理单元、跨域网络切片管理单元或者其他网络单元。这里，NM单元可以是独立的管理单元，也可以是在任意一个管理单元中的逻辑实体，例如网络编排单元、网络管理和编排单元、业务管理单元、业务编排单元、业务管理和编排单元或者网络功能虚拟化编排器(network function virtualization orchestrator，NFVO)中的逻辑实体。NM单元可以包括在运营支撑系统(operation support system，OSS)内，也可以不包括在OSS内。
其中，上述网络也可以称为网络切片或者称为端到端(end to end，E2E)网络切片，可以至少包括核心网(core network，CN)部分、接入网(access network，AN)部分和传输网(transport network，TN)部分；或者，上述网络可以包括CN部分、AN部分或TN部分中的任意两项；或者，上述网络可以表示CN部分的网络、AN部分的网络或TN部分的 网络。上述网络至少包括一个网络子网。从逻辑上看，网络是一组网络功能的集合。这里的网络子网也可以称为网络切片子网。
域管理单元，也可以称为网络切片子网管理(network slice subnet management function，NSSMF)单元包括子网管理功能或者编排功能之一或者全部，可以具备以下部分或者全部功能：
域的管理，包括子网的生命周期管理(创建、更新、删除)、子网故障管理、子网性能管理、子网配置管理等；业务的管理，包括业务生命周期管理、业务故障管理、业务性能管理、业务配置管理等；网络资源(例如，NF)的协调，用于统一编排。
需要说明的是，DM单元是用于表示具有上述功能的网络单元，并不对DM名字作任何限制，还可以是域切片管理单元、网络切片子网管理单元或者其他网络单元。这里，DM单元可以是独立的管理单元，也可以是在任意一个管理单元中的逻辑实体，例如网络管理单元、网络编排单元、网络管理和编排单元、网元功能单元、业务管理单元、业务编排单元、域管理单元、业务管理和编排单元或者NFVO。DM单元可以包括在OSS内，也可以不包括在OSS内。
对于上述所说的子网可以包括以下中的一个或者多个：AN部分、CN部分和TN部分。当DM单元管理的子网只包括AN部分时，可以认为该子网管理单元为AN DM单元。当DM单元管理的子网只包括CN部分时，可以认为该子网管理单元为CN DM单元。当DM管理的子网包括AN和CN部分时，可以认为该子网管理单元为Mix DM单元。
结合图1和图2，本申请实施例中，管理网元可以为NM单元，也可以为DM单元，根据不同的实施场景有不同的可能。本申请实施例可以通过NM单元直接管理至少一个NF实例以及至少一个NRF实例并与它们进行通信交互，也可以由NM单元通过DM单元间接管理至少一个NF实例以及至少一个NRF实例并进行通信交互，具体实现方法在下面的实施例中详细描述。
在多个NF实例由NF实例的管理单元统一管理的场景中，NM单元或DM单元管理至少一个NF实例时，可以通过NF实例的管理单元向至少一个NF实例发送管理消息。也就是说，NM单元或DM单元可以向NF实例的管理单元发送消息后，再由NF实例的管理单元发送给NF实例。由于路由的目的终端是一致的，以下实施例中直接体现为NM单元或DM单元向NF实例发送消息，可以认为这种情况是包括通过NF实例的管理单元向NF实例发送消息的情况的。
下面将基于上面所述的本申请实施例涉及的共性方面，对本申请实施例进一步详细说明。
本申请实施例提供一种网络功能信息的管理方法，和基于方法的装置和系统。方法包括：管理网元获取网络仓库功能NRF实例的标识信息，NRF实例中存储网络功能NF实例的信息，NRF实例的标识信息用于指示与NF实例关联的NRF实例；管理网元向NF实例或NF实例的管理单元发送第一消息，第一消息包括NRF实例的标识信息；或者，管理网元根据所述NRF实例的标识信息，建立NF实例与NRF实例的关联关系。例如，该方法可以如图3所示，其中，图3所示的方法可以包括步骤S101和步骤S102，或者可以包括步骤S101和步骤S103，或者可以包括步骤S101-步骤S103。从而，在存在多个NRF实例时，管理网元 可以向NF实例指示与该NF实例关联的NRF实例，或者可以建立NF实例与NRF实例的关联关系，以便于NF实例向该NRF实例注册、更新或查询其他NF实例的信息。
在一种可能的实施方式中，NF实例在接收第一消息后，可以向NRF实例发送第二消息，第二消息包括NF实例的信息，第二消息用于指示NRF实例保存或更新NF实例的信息；或者，NF实例可以向NRF实例发送第三消息，第三消息用于向NRF实例查询其他NF实例的信息。
在另一种可能的实施方式中，NF实例的管理单元在接收第一消息后，可以向NF实例发送NRF实例的标识信息。相应的，NF实例在接收NRF实例的标识信息后，可以向NRF实例发送第二消息，第二消息包括NF实例的信息，第二消息用于指示NRF实例保存或更新NF实例的信息；或者，NF实例可以向NRF实例发送第三消息，第三消息用于向NRF实例查询其他NF实例的信息。
在上述两种可能的实施方式中，NRF实例在接收第二消息后，可以根据第二消息，保存或更新NF实例的信息；或者，NRF实例在接收第三消息后，可以根据第三消息，查询其他NF实例的信息。
下面结合附图4，对本申请的实施例提供的方案进行说明。
请参见图4，图4是本申请实施例提供的另一种网络功能信息的管理方法的通信示意图。图4中的管理单元可以是NM单元，也可以是DM单元,也可以是EM单元或者NF Manager单元。该方法包括但不限于如下步骤：
S201，管理网元获取NRF实例的标识信息，NRF实例中存储NF实例的信息。
NRF实例是用于存储NF实例的信息的网络单元，NRF实例的标识信息是用于唯一指示一个NRF实例的信息，可以包括NRF实例的标识、名称或网络地址中的至少一个。在本申请实施例中，NRF实例的标识信息的获取方式既可以是从其他网络单元中获取到的，也可以是从NM单元或DM单元自身存储的信息中确定得到，这里不作限定。
在管理网元为NM单元的实施场景中，NM单元获取NRF实例的标识信息的方式可以为：接收管理请求消息，管理请求消息携带NRF实例的标识信息或NRF实例的指示信息，其中，NRF实例的指示信息用于获取NRF实例的标识信息。具体的，管理请求消息可以是NF实例的创建请求消息(也可以称为，NF的实例化请求消息)、NF实例的修改请求消息或者NF实例的配置请求消息，也可以是NF实例所属的网络切片或者网络切片子网的创建请求消息、实例化请求消息、修改请求消息或者配置请求消息。具体的，NF实例的配置请求消息可以是NF实例对应的管理对象的创建请求消息，或者可以是NF实例对应的管理对象的配置请求消息；网络切片或者网络切片子网的配置请求消息可以是网络切片或者网络切片子网对应的管理对象的创建请求消息；或者可以是网络切片或者网络切片子网对应的管理对象的配置请求消息。NM单元获取NRF实例的标识信息的方式也可以为：获取网络模板中描述的NRF实例的标识信息或NRF实例的指示信息，其中，NRF实例的指示信息用于获取NRF实例的标识信息。具体的，网络模板可以为网络切片模板、网络切片子网模板或网络功能模板。需要说明的是，这里不对网络模板的名称进行限定，网络模板也可以被称为网络描述符、网络蓝图(blueprint)等。
NM单元获取NRF实例的标识信息的方式还可以为：根据NM单元本地预设的NRF实例 的选择信息确定NRF实例的标识信息。例如，NRF实例的选择信息中预设了各种NF实例的实例类型对应的NRF实例，则可以根据当前配置或创建的NF实例的类型，确定其对应的NRF实例并获取NRF实例的标识信息。
这里，NRF实例的指示信息可以包括隔离需求信息、安全信息、位置信息、用户信息以及网络信息中的至少一个。也即NM单元通过NRF实例的指示信息确定与NRF实例的指示信息匹配的NRF实例并获取NRF实例的标识信息，或者，新建符合NRF实例的指示信息的NRF实例并获取NRF实例的标识信息。
在管理网元为DM单元的实施场景中，DM单元获取NRF实例的标识信息的方式可以为：接收NM单元发送的管理请求消息，管理请求消息携带NRF实例的标识信息。具体的，管理请求消息可以是NF实例的修改请求消息或者NF实例的配置请求消息，也可以是NF实例所属的网络切片子网的创建请求消息、实例化请求消息，修改请求消息或者配置请求消息。具体的，NF实例的配置请求消息可以是NF实例对应的管理对象的创建请求消息，或者可以是NF实例对应的管理对象的配置请求消息；网络切片或者网络切片子网的配置请求消息可以是网络切片或者网络切片子网对应的管理对象的创建请求消息，或者可以是网络切片或者网络切片子网对应的管理对象的配置请求消息。
进一步地，在获取到NRF实例的标识信息后，管理网元还可以建立当前需要配置的NF实例与NRF实例的关联关系，以便于之后向NF实例发送包括第一消息在内的相关消息时，可以直接获取到与NF实例关联的NRF实例。需要说明的是，关联关系的形式不作具体限定，只要能够表明NF实例与NRF实例相关联即可，例如，可以建立关联关系表，表中包括NF实例的标识信息以及其关联的NRF实例的标识信息。又例如，可以在NM单元的NF实例的管理对象中配置NRF实例的标识信息，以表明该NF实例的与NRF实例关联。其中，NF实例的管理对象是存储NF实例的管理信息的一种日志文件。
下述步骤S202，以及步骤S203和S204为可选的步骤，可以执行步骤S202，或者可以执行步骤S203和S204。
S202，管理网元向NF实例发送第一消息，所述第一消息包括NRF实例的标识信息。
第一消息可以配置请求消息，携带NRF实例的标识信息，NRF实例的标识信息用于指示与NF实例关联的NRF实例。也即，NRF实例存储该NF实例的信息，且NF实例向NRF实例查询其他NF实例的信息。
可选的，第一消息中还可以携带NF实例的信息。NF实例的信息包括实例类型、地址信息、域名信息、所属网络切片的切片信息、服务区域或发现策略中的至少一个。
可选的，当第一消息中还携带NF实例的信息时，管理请求消息中可以还包括NF实例的信息。
进一步地，第一消息中还可以包括注册指示信息，注册指示信息用于指示NF实例是否向NRF实例注册。
进一步地，第一消息中还可以包括接入安全信息，接入安全信息用于NRF实例对NF实例的接入安全验证。
S203，管理网元向NF实例的管理单元发送第一消息，所述第一消息包括NRF实例的标识信息。
需要说明的是，本步骤中，有关第一消息的内容可以参考步骤S202中的介绍，此处不再赘述。
S204，NF实例的管理单元向NF实例发送NRF实例的标识信息。
示例性的，NF实例的管理单元可以在接收第一消息后，将包括NRF实例的标识信息的第一消息发送给NF实例；或者，NF实例的管理单元也可以通过其他方式向NF实例发送NRF实例的标识信息，例如，NF实例的管理单元可以通过其他消息向NF实例发送NRF实例的标识信息。
进一步地，NF实例的管理单元在获取到NRF实例的标识信息后，也可以建立当前需要配置的NF实例与NRF实例的关联关系，以便于之后向NF实例发送包括第二消息在内的相关消息时，可以直接获取到与NF实例关联的NRF实例。需要说明的是，关联关系的形式不作具体限定，只要能够表明NF实例与NRF实例相关联即可，例如，可以建立关联关系表，表中包括NF实例的标识信息以及其关联的NRF实例的标识信息。又例如，可以在管理网元维护的NF实例的管理对象中配置NRF实例的标识信息，以表明该NF实例的与NRF实例关联。其中，NF实例的管理对象是存储NF实例的管理信息的一种日志文件。
下述步骤S205和S206，以及步骤S207和S208为可选的步骤，可以执行步骤S205和S206，或者可以执行步骤S207和S208，或者可以执行步骤S205和S206以及步骤S207和S208。其中，在最后一种情形下，步骤S205和S206，以及步骤S207和S208的执行顺序不作限制。
S205，NF实例向NRF实例发送第二消息，所述第二消息包括NF实例的信息。
第二消息可以为注册请求消息或者更新请求消息，第二消息包括NF实例的信息，第二消息用于指示NRF实例保存或更新NF实例的信息。
进一步地，第二消息中还可以包括接入安全信息，接入安全信息用于NRF实例对NF实例的接入安全验证。
可选的，第一消息中包括注册指示信息且指示注册时，触发NF实例向NRF实例发送注册请求消息。
可选的，NF实例向NRF实例发送第二消息之前，还包括：
NF实例接收激活请求消息，激活请求消息用于激活NF实例或者NF实例对应的服务，以触发NF实例向NRF实例发送注册请求消息。
进一步地，该方法还可以包括：
NF实例向NRF实例发送第四消息，第四消息用于指示NRF实例删除NF实例的信息或将NF实例的信息设置为不可用。
可选的，第四消息为NF实例或NF实例对应的服务的去注册请求消息，NF实例向NRF实例发送第四消息之前，还包括：
NF实例接收去激活请求消息，去激活请求消息用于去激活NF实例或者NF实例对应的服务，以触发NF实例向NRF实例发送去注册请求消息。
S206，NRF实例根据第二消息，保存或更新NF实例的信息。
第二消息可以为注册请求消息时，NRF实例保存NF实例的信息。第二消息为更新请求消息时，NRF实例更新NF实例的信息。
从而，NF实例可以直接向NRF实例注册或更新NF实例的信息，节约网络功能信息的配置时间，优化配置流程。
S207，NF实例向NRF实例发送第三消息，所述第三消息用于向NRF实例查询其他NF实例的信息。
第三消息可以为查询请求消息，第三消息可以携带需要查询的业务信息，用于向NRF实例查询其他NF实例的信息。
可选的，NF实例向NRF实例发送第三消息之前还可以包括：
管理网元向NRF实例发送第五消息，所述第五消息包括NF实例的信息。
可选的，NF实例向NRF实例发送第三消息之前还可以包括：
终端向NF实例发送业务请求，以触发NF实例根据业务请求向NRF实例发送第三消息。
S208，NRF实例根据第三消息，查询其他NF实例的信息。
NRF实例根据第三消息中的业务信息，查询并获取可以处理该业务信息对应的业务的NF实例的信息。
从而，在存在多个NRF实例时，NF实例可以获知与自身关联的NRF实例，并确定向该NRF实例查询其他NF实例的信息。
请参阅图5A，图5A是本申请实施例提供的又一种网络功能信息的管理方法的通信示意图。图5A所示的方案中，以管理网元为NM单元为例进行描述。其中，NM单元可以直接与NF实例通信，管理NF实例的配置。该方法包括但不限于如下步骤：
S301，NM单元获取NRF实例的标识信息，NRF实例中存储NF实例的信息。
NRF实例是用于存储NF实例的信息的网络单元，NRF实例的标识信息是用于唯一指示一个NRF实例的信息，可以包括NRF实例的标识、名称或网络地址中的至少一个。在本申请实施例中，NRF实例的标识信息的获取方式既可以是从其他网络单元中获取到的，也可以是从NM单元或DM单元自身存储的信息中确定得到，这里不作限定。
NF实例的信息可以包括实例类型、地址信息、域名信息、所属网络切片的切片信息、服务区域、所属的NF组信息或发现策略中的至少一个。
其中，NF实例的地址信息可以为互联网协议(Internet Protocol，IP)地址、端口地址等；NF实例的域名信息可以为全称域名(fully qualified domain name，FQDN)，全称域名可以从逻辑上准确地表示出主机在什么地方，也可以说全称域名是主机名的一种完全表示形式；NF实例所属网络切片的切片信息可以包括网络切片或者网络切片子网的标识信息，也可以包括NF实例所属网络切片的租户信息，网络切片类型信息，网络切片选择辅助信息(single-network slice selection assistance information，s-NSSAI)等，其中，网络切片也可以称为网络切片实例，网络切片子网也可以称为网络切片子网实例；NF实例的服务区域是指NF实例可以提供服务的区域的信息，即仅服务区域中的终端或者网络单元可以调用NF实例提供的服务；NF实例的发现策略是指在什么情况下NF实例是能够被其他终端或者网络单元发现并调用的，例如，当NF实例的负载超过80％时，就不能够被其他终端或者网络单元再调用来提供服务；NF实例的所属NF组信息用于标识NF实例所属的同类型的NF实例所组成的集合；NF实例的实例类型可以为以下任意一种：
-鉴权服务功能(authentication server function，AUSF)；
-接入管理功能(access and mobility management function，AMF)；
-数据网络(data network，DN)，例如，operator services，Internet access or 3rd party services；
-结构化数据存储网络功能(structured data storage network function，SDSF)；
-非结构化数据存储网络功能(unstructured data storage network function，UDSF)；
-网络开放功能(network exposure function，NEF)；
-网络仓库功能(network repository function，NRF)，也可以表示为network function repository function；
-策略控制功能(policy control function，PCF)；
-会话管理功能(session management function，SMF)；
-统一数据管理(unified data management，UDM)；
-用户面功能(user plane function，UPF)；
-应用功能(application function，AF)；
-下一代基站功能(generation nodeB function，gNBF)或者5G基站功能；
-演进型基站功能(evolved node B function，eNBF)；
-演进型LTE演进型基站功能(evolved LTE evolved node B function，eLTE eNBF)；
-基站功能(node B function，NBF)。
在第一种可能的实施场景中，NM单元决定配置一个NF实例，则可以新建一个NRF实例或者在现有的NRF实例中选择一个NRF实例作为存储该NF实例的信息的NRF实例，并获取该NRF实例的标识信息。
在该实施场景中，NM单元获取NRF实例的标识信息的方式可以有以下几种：
在第一种可能的情况中，NM单元接收管理请求消息，管理请求消息携带NRF实例的标识信息。这里，管理请求消息可以是NF实例的创建请求消息(也可以称为，NF的实例化请求消息)、NF实例的修改请求消息或者NF实例的配置请求消息。NM单元接收到NF实例的配置请求消息或NF实例的修改请求消息时，可以确定需要配置的NF实例，并获取与该NF实例关联的NRF实例的标识信息，即管理请求消息携带NRF实例的标识信息；NM单元接收到NF实例的创建请求消息时，可以创建NF实例，并获取与该NF实例关联的NRF实例的标识信息，即管理请求消息携带NRF实例的标识信息。
在第二种可能的情况中，NM单元接收管理请求消息，管理请求消息携带NRF实例的指示信息。这里，NRF实例的指示信息可以包括隔离需求信息、安全信息、位置信息、用户信息以及网络信息中的至少一个。其中，隔离需求信息是指NRF实例的隔离需求或者NRF实例所属的网络的隔离需求(例如，完全隔离，硬隔离，软隔离等)；安全信息是指NRF实例的或者NRF实例所属的网络的安全方面的相关信息，例如安全等级；位置信息是指NF实例的部署位置；用户信息是指租用该NF实例或租用该NF实例所提供的业务的用户的信息；网络信息是指NF实例所属网络的需求信息，比如带宽、时延等。管理请求消息可以是NF实例的创建请求消息(也可以称为，NF的实例化请求消息)、NF实例的修改请求消息或者NF实例的配置请求消息。
NM单元根据NRF实例的指示信息可以创建符合指示信息的NRF实例或者在现有的NRF 实例中确定出与指示信息匹配的NRF实例。NM单元接收到NF实例的配置请求消息或NF实例的修改请求消息时，可以确定需要配置的NF实例，根据指示信息确定并获取与该NF实例关联的NRF实例的标识信息；NM单元接收到NF实例的创建请求消息时，可以创建NF实例，根据指示信息确定并获取与该NF实例关联的NRF实例的标识信息。
具体举例来说，若NRF实例的指示信息为隔离需求信息，NM单元可以根据隔离需求信息的不同，在现有的NRF实例中选择不同的NRF实例，比如隔离要求高的，选择隔离性好的NRF实例，隔离要求低的，选择隔离性较弱的NRF实例；NM单元也可以根据隔离需求信息的不同，决定创建一个新的NRF实例还是复用一个现有的NRF实例。比如隔离要求高，就创建一个新的NRF实例，如果隔离要求低，复用一个现有的已经在使用的NRF实例。
根据安全信息确定NRF实例的方式与根据隔离需求信息确定NRF实例的方式相似，即安全等级高则选择安全性能好的NRF实例，安全等级低则选择安全性能低的NRF实例；或，安全等级高就创建一个新的NRF实例，安全等级低则复用一个现有的已经在使用的NRF实例。
若NRF实例的指示信息为位置信息，NM单元可以根据NF实例的部署位置，选择或者创建一个处于NF实例附近的NRF实例。
若NRF实例的指示信息为用户信息，NM单元可以根据用户信息，将同一用户的所有NF实例的信息都存储在同一NRF实例上；也可以根据用户信息指示的用户优先级/等级的高低，为用户优先级/等级高的用户选择性能好的NRF实例，为用户优先级/等级低的用户选择性能低的NRF实例。
若NRF实例的指示信息为网络信息，NM单元可以根据不同的网络信息选择或创建能够匹配网络信息的NRF实例。
需要说明的是，NM单元可以根据以上多个NRF实例的指示信息来综合选择或创建出合适的NRF实例。
在第三种可能的情况中，NM单元在网络模板中获取NRF实例的标识信息，网络模板描述了某一类型网络的类型或者部署信息，用于创建或者实例化网络切片、网络切片子网或NF实例。其中，网络模板可以为网络切片模板、网络切片子网模板或网络功能模板。NM单元可以预先存储网络模板，在决定配置一个NF实例时，从网络模板中获取NF实例对应的NRF实例的标识信息。
在第四种可能的情况中，NM单元在网络模板中获取NRF实例的指示信息。与第二种可能的情况相似的，NM单元可以根据NRF实例的指示信息创建符合指示信息的NRF实例或者在现有的NRF实例中确定出与指示信息匹配的NRF实例。
在第五种可能的情况中，NM单元可以根据NM单元本地预设的NRF实例的选择信息确定NRF实例的标识信息。例如，NRF实例的选择信息中预设了各种NF实例的实例类型对应的NRF实例，则可以根据当前配置或创建的NF实例的类型，确定其对应的NRF实例并获取NRF实例的标识信息。
在第二种可能的实施场景中，NM单元决定创建一个网络切片或者一个网络切片子网，网络切片或网络切片子网中包含了至少一个NF实例，则为网络切片或网络切片子网中的至少一个NF实例新建NRF实例或者在现有的NRF实例中选择NRF实例作为存储至少一个NF 实例的信息的NRF实例。需要说明的是，这里的至少一个NF实例的信息可以统一都由一个NRF实例存储，也可以分别由多个NRF实例存储，这里不作具体限定。
同理地，在该实施场景中，NM单元获取NRF实例的标识信息的方式也可以有以下几种：
在第一种可能的情况中，NM单元接收管理请求消息，管理请求消息携带NRF实例的标识信息。这里，管理请求消息可以是网络切片的创建请求消息、实例化请求消息、修改请求消息或者配置请求消息。NM单元可以根据网络切片的创建请求消息、实例化请求消息、修改请求消息或者配置请求消息，创建或配置网络切片，网络切片中包含至少一个NF实例，并获取与至少一个NF实例关联的NRF实例的标识信息，即管理请求消息携带NRF实例的标识信息。
在第二种可能的情况中，NM单元接收管理请求消息，管理请求消息携带NRF实例的指示信息。NM单元根据NRF实例的指示信息可以创建符合指示信息的NRF实例或者在现有的NRF实例中确定出与指示信息匹配的NRF实例。管理请求消息可以是网络切片的创建请求消息、实例化请求消息、修改请求消息或者配置请求消息。NM单元接收到网络切片的创建请求消息、实例化请求消息、修改请求消息或者配置请求消息时，创建或配置网络切片，网络切片中包含至少一个NF实例，根据指示信息确定并获取与至少一个NF实例关联的NRF实例的标识信息。具体方法可以参见第一种可能的实施场景中的第二种可能的情况。
第三种到第五种可能的情况与前文第一种可能的实施场景中的第三种到第五种可能的情况相似，这里不再赘述。
进一步地，在获取到NRF实例的标识信息后，NM单元还可以建立当前需要配置的NF实例与NRF实例的关联关系，以便于之后向NF实例发送包括第一消息在内的相关消息时，可以直接获取到与NF实例关联的NRF实例。需要说明的是，关联关系的形式不作具体限定，只要能够表明NF实例与NRF实例相关联即可，例如，可以建立关联关系表，表中包括NF实例的标识信息以及其关联的NRF实例的标识信息。又例如，可以在NM单元的维护的NF实例的管理对象中配置NRF实例的标识信息，以表明该NF实例的与NRF实例关联。其中，NF实例的管理对象是存储NF实例的管理信息的一种日志文件。
S302，NM单元向NF实例发送第一消息，所述第一消息包括NRF实例的标识信息。
第一消息中包括NRF实例的标识信息，NRF实例的标识信息用于指示与NF实例关联的NRF实例。也即，NF实例的信息由该NRF实例保存和维护，NF实例可以向该NRF实例进行注册和询问等操作。第一消息可以为配置请求消息。可选的，第一消息还可以包括NF实例的信息，NF实例的信息可以是管理请求消息中携带的。
第一消息中还可以包括注册指示信息，注册指示信息用于指示NF实例是否向NRF实例注册。在一种可能的实施场景中，第一消息中携带注册指示信息，指示NF实例向NRF实例注册；第一消息中未携带注册指示信息，指示NF实例不向NRF实例注册。在另一种可能的实施场景中，第一消息中必然携带注册指示信息，注册指示消息可以是能够表示两种指示状态的比特位，例如，置1时指示NF实例向NRF实例注册，置0时指示NF实例不向NRF实例注册。在又一种可能的实施场景中，第一消息中未携带注册指示信息，则默认NF实例向NRF实例注册；第一消息中携带注册指示信息，则依据注册指示信息的指示，确定NF实例是否向NRF实例注册。
从而，NM单元可以控制NF实例是否向NRF实例注册，避免NM实例无法监控到NF实例的注册情况而不便于管理。
进一步可选的，第一消息还可以包括接入安全信息，接入安全信息用于NRF实例对NF实例的接入安全验证。接入安全信息可以认为是NF实例向NRF实例注册的密钥，NRF实例对NF实例发送的接入安全信息验证成功时，才会对NF实例的信息进行注册，从而避免其他网络单元的非法接入。
进一步地，在NM单元通过NF实例的管理单元(例如，EM，NFM)向NF实例发送第一消息的实施场景中，NF实例的管理单元在获取到NRF实例的标识信息后，也可以建立当前需要配置的NF实例与NRF实例的关联关系，以便于之后向NF实例发送包括第二消息在内的相关消息时，可以直接获取到与NF实例关联的NRF实例。
需要说明的是，关联关系的形式不作具体限定，只要能够表明NF实例与NRF实例相关联即可，例如，可以建立关联关系表，表中包括NF实例的标识信息以及其关联的NRF实例的标识信息。又例如，可以在NM单元维护的NF实例的管理对象中配置NRF实例的标识信息，以表明该NF实例的与NRF实例关联。其中，NF实例的管理对象是存储NF实例的管理信息的一种日志文件。
S303，NF实例向NRF实例发送第二消息，所述第二消息包括NF实例的信息。
在该步骤中，第二消息可以为注册请求消息，用于指示NRF实例保存NF实例的信息。进一步的，当第一消息中包括NF实例的信息时，第二消息中包含的NF实例的信息可以是从第一消息中接收到的；当第一消息中不包括NF实例的信息时，第二消息中包含的NF实例的信息可以是NF实例本身查询到的。
S304，NRF实例根据第二消息，保存NF实例的信息。
从而，NF实例可以直接向NRF实例注册或更新NF实例的信息，节约网络功能信息的配置时间，优化配置流程。
进一步的，S304之后，还可以包括S305：
S305，NRF实例向NF实例发送第一响应消息。
第一响应消息可以是注册请求响应消息，用于说明NRF实例对NF实例的信息保存完成。
可选的，S303之前还可以执行S306：
S306，NM单元向NF实例发送激活请求消息。
激活请求消息用于激活NF实例或者NF实例对应的服务，以触发NF实例执行S203向NRF实例发送注册请求消息。可以认为在该种情况下，NF实例或者NF实例对应的服务在之前并未被激活使用，当NM单元向NF实例发送激活请求消息时，NF实例或者NF实例对应的服务才处于激活状态，可以向NRF实例发起注册。
需要说明的是，NF实例是可以提供相关网络服务的逻辑实体，激活请求消息可以直接激活NF实例，也可以激活NF实例提供的对应的服务。
从而，NF实例在激活状态下才向NRF实例注册，避免NRF实例在进行业务查询时将路由指示到未激活的NF实例，造成服务提供失败。
进一步的，当NF实例的信息需要更新时，S304或S305之后还可以执行S307-S308：
S307，NF实例向NRF实例发送第二消息，所述第二消息包括NF实例的信息。
当NF实例自身或者通过其他方式获取到NF实例的信息需要更新时，可以向NRF实例发送第二消息。在该步骤中，第二消息可以为第一更新请求消息，用于指示NRF实例更新NF实例的信息。在该实施场景中，NF实例的信息是指NF实例的更新信息，更新信息可以是更新后的完整的NF实例的信息，也可以是与当前存储在NRF实例的NF实例的信息(例如，S304中保存的NF实例的信息)的差异化信息，这里不作具体限定。
例如，NF实例更新了所属网络切片的切片信息，那么NF实例的信息可以包括更新后的切片信息以及实例类型、地址信息、域名信息、服务区域或发现策略等其他信息的完整的NF实例；NF实例的信息也可以仅包括更新后的切片信息，即差异化信息。
S308，NRF实例根据第二消息，更新NF实例的信息。
可选的，S307之前，还可以执行S309：
S309，NM单元向NF实例发送第五消息，所述第五消息包括NF实例的信息。
当NM单元确定NF实例的信息需要更新时，可以向NF实例发送第五消息。第五消息可以为第二更新请求消息，用于指示NF实例向NRF单元更新信息。与S307一致的，这里的NF实例的信息也是指NF实例的更新信息，更新信息可以是更新后的完整的NF实例的信息，也可以是与当前存储在NRF实例的NF实例的信息(例如，S304中保存的NF实例的信息)的差异化信息，这里不作具体限定。
进一步的，S308之后，还可以执行S310：
S310，NRF实例向NF实例发送第二响应消息。
第二响应消息可以是更新请求响应消息，用于说明NRF实例对NF实例的信息更新完成。
可选的，S304或S305之后，还可以执行S311-S312：
S311，NF实例向NRF实例发送第四消息。
第四消息是用于指示NRF实例删除NF实例的信息或将NF实例的信息设置为不可用的消息，例如，第四消息可以是去注册请求消息，也可以是删除请求消息等，这里不作具体限定。
S312，NRF实例删除NF实例的信息或将NF实例的信息设置为不可用。
NRF实例删除NF实例的信息或将NF实例的信息设置为不可用后，在后续再进行业务查询时，就不会再将路由指示到NF实例。
可选的，S311之前，还可以执行S313：
S313，NM单元向NF实例发送去激活请求消息。
在该实施场景中，去激活请求消息用于去激活NF实例或者NF实例对应的服务，以触发NF实例执行S308向NRF实例发送第四消息。可以认为在该种情况下，NF实例或者NF实例对应的服务在之前已经被激活使用，当NM单元向NF实例发送去激活请求消息时，NF实例或者NF实例对应的服务被取消激活状态，因此向NRF实例发送第四消息。
从而，NF在未激活的状态时，触发NRF实例删除NF实例的信息或将NF实例的信息设置为不可用，防止发现错误或者不可用的NF实例。
进一步的，S312之后，还可以包括S314：
S314，NRF实例向NF实例发送第三响应消息。
第三响应消息可以是去注册请求响应消息或者删除请求响应消息等，用于说明NRF实 例对NF实例的信息的删除或者设为不可用的操作完成。
请参阅图5B，图5B是本申请实施例提供的又一种网络功能信息的管理方法的通信示意图。图5B所示的方案中，以管理网元为NM单元为例进行描述。其中，NM单元通过DM单元与NF实例通信，管理NF实例的配置。该方法包括但不限于如下步骤：
S401，NM单元获取NRF实例的标识信息，NRF实例中存储NF实例的信息。
S401的具体实现方式可以参考S301，此处不再赘述。
S402，NM单元向DM单元发送第六消息，所述第六消息包括NRF实例的标识信息。
第六消息包括NRF实例的标识信息，具体可以为NF实例的修改请求消息或者NF实例的配置请求消息，也可以为网络切片子网的创建请求消息、实例化请求消息，修改请求消息或者配置请求消息。具体的，NF实例的配置请求消息可以是NF实例对应的管理对象的创建请求消息；或者可以是NF实例对应的管理对象的配置请求消息；网络切片或者网络切片子网的配置请求消息可以是网络切片或者网络切片子网对应的管理对象的创建请求消息，或者可以是网络切片或者网络切片子网对应的管理对象的配置请求消息。
在第一种可能的实施场景中，NM单元决定配置一个NF实例，则第六消息为NF实例的修改请求消息或者NF实例的配置请求消息，可以携带NRF实例的标识信息以及NF实例的标识信息，用于指示DM单元向NF实例发送第一消息以建立NF实例与NRF实例的关联。具体的，NF实例的配置请求消息可以是NF实例对应的管理对象的创建请求消息，或者可以是NF实例对应的管理对象的配置请求消息。
在另一种可能的实施场景中，NM单元决定创建一个网络切片或者一个网络切片子网，则第六消息为网络切片子网的创建请求消息、实例化请求消息，修改请求消息或者配置请求消息，可以携带NRF实例的标识信息以及NM单元创建的网络切片子网的标识信息(例如，网络切片子网标识(network slice subnet identifier，NSSI)，用于指示DM单元创建或配置网络切片子网中包含的至少一个NF实例，并向至少一个NF实例发送第一消息以建立NF实例与NRF实例的关联。具体的，网络切片或者网络切片子网的配置请求消息可以是网络切片或者网络切片子网对应的管理对象的创建请求消息，或者可以是网络切片或者网络切片子网对应的管理对象的配置请求消息。
进一步地，在获取到NRF实例的标识信息后，NM单元或DM单元还可以建立当前需要配置的NF实例与NRF实例的关联关系，以便于之后向NF实例发送包括第一消息在内的相关消息时，可以直接获取到与NF实例关联的NRF实例。需要说明的是，关联关系的形式不作具体限定，只要能够表明NF实例与NRF实例相关联即可，例如，可以建立关联关系表，表中包括NF实例的标识信息以及其关联的NRF实例的标识信息。又例如，可以在NM单元维护的NF实例的管理对象中配置NRF实例的标识信息，以表明该NF实例的与NRF实例关联。其中，NF实例的管理对象是存储NF实例的管理信息的一种日志文件。
S403，DM单元向NF实例发送第一消息，所述第一消息包括NRF实例的标识信息。
进一步地，在DM单元通过NF实例的管理单元(例如，NFM)向NF实例发送第一消息的实施场景中，NF实例的管理单元在获取到NRF实例的标识信息后，也可以建立当前需要配置的NF实例与NRF实例的关联关系，以便于之后向NF实例发送包括第二消息在内的相关消息时，可以直接获取到与NF实例关联的NRF实例。
需要说明的是，关联关系的形式不作具体限定，只要能够表明NF实例与NRF实例相关联即可，例如，可以建立关联关系表，表中包括NF实例的标识信息以及其关联的NRF实例的标识信息。又例如，可以在DM单元维护的NF实例的管理对象中配置NRF实例的标识信息，以表明该NF实例的与NRF实例关联。其中，NF实例的管理对象是存储NF实例的管理信息的一种日志文件。
S403的其他具体实现方式可以参考S302，此处不再赘述。
S404，NF实例向NRF实例发送第二消息，所述第二消息包括NF实例的信息。
S404的具体实现方式可以参考S303，此处不再赘述。
S405，NRF实例根据第二消息，保存NF实例的信息。
进一步的，S405之后，还可以包括S406：
S406，NRF实例向NF实例发送第一响应消息。
S406的具体实现方式可以参考S305，此处不再赘述。
可选的，S404之前，还包括S407-S408：
S407，NM单元向DM单元发送第一激活请求消息。
第一激活请求消息中可以携带NF实例的标识信息，也可以携带网络切片子网的标识信息。具体来说，当NM单元激活的是NF实例或者NF实例对应的服务时，第一激活请求消息中可以携带NF实例的标识信息；当NM单元激活的是网络切片子网包含的至少一个NF实例或者至少一个NF实例对应的服务时，第一激活请求消息中可以携带网络切片子网的标识信息。
S408，DM单元根据第一激活请求消息，向NF实例发送第二激活请求消息。
DM单元根据第一激活请求消息中所携带的NF实例的标识信息或网络切片子网的标识信息，确定出相应的NF实例，并向NF实例发送第二激活请求消息。第二激活请求消息用于激活NF实例或者所述NF实例对应的服务，以触发NF实例向NRF实例发送注册请求消息。S408的具体实现方式可以参考S306，此处不再赘述。
进一步的，当NF实例的信息需要更新时，S405或S406之后还可以执行S409-S410：
S409，NF实例向NRF实例发送第二消息，所述第二消息包括NF实例的信息。
S410，NRF实例根据第二消息，更新NF实例的信息。
S409-S410的具体实现方式可以参考S307-S308，此处不再赘述。
可选的，S409之前，还可以执行S411-S412：
S411，NM单元向DM单元发送第七消息，所述第七消息包括NF实例的信息。
当NM单元确定NF实例的信息需要更新时，可以向DM实例发送第七消息。第七消息可以为第三更新请求消息，用于指示DM单元向NF实例发送第五消息，以触发NF实例向NRF实例更新信息。
S412，DM单元向NF实例发送第五消息，所述第五消息包括NF实例的信息。
S412的具体实现方式可以参考S309，此处不再赘述。
进一步的，S410之后，还可以执行S413：
S413，NRF实例向NF实例发送第二响应消息。
S413的具体实现方式可以参考S310，此处不再赘述。
可选的，S405或S406之后，还可以执行S414-S415：
S414，NF实例向NRF实例发送第四消息。
S415，NRF实例删除NF实例的信息或将NF实例的信息设置为不可用。
S414-S415的具体实现方式可以参考S311-S312，此处不再赘述。
可选的，S414之前，还可以执行S415-S416：
S415，NM单元向DM单元发送第一去激活请求消息。
第一去激活请求消息中可以携带NF实例的标识信息，也可以携带网络切片子网的标识信息。具体来说，当NM单元去激活的是NF实例或者NF实例对应的服务时，第一激活请求消息中可以携带NF实例的标识信息；当NM单元去激活的是网络切片子网包含的至少一个NF实例或者至少一个NF实例对应的服务时，第一激活请求消息中可以携带网络切片子网的标识信息。
S416，DM单元向NF实例发送第二去激活请求消息。
DM单元根据第一去激活请求消息中所携带的NF实例的标识信息或网络切片子网的标识信息，确定出相应的NF实例，并向NF实例发送第二去激活请求消息。第二去激活请求消息用于去激活NF实例或者所述NF实例对应的服务，以触发NF实例向NRF实例发送第四消息。S416的具体实现方式可以参考S313，此处不再赘述。
进一步的，S415之后，还可以包括S417：
S417，NRF实例向NF实例发送第三响应消息。
S417的具体实现方式可以参考S314，此处不再赘述。
请参阅图6A，图6A是本申请实施例提供的又一种网络功能信息的管理方法的通信示意图。图6A所示的方案中，以管理网元为NM单元为例进行描述。其中，NM单元可以直接与NF实例通信，管理NF实例的配置。该方法包括但不限于如下步骤：
S501，NM单元获取NRF实例的标识信息以及NF实例的信息，NRF实例中存储NF实例的信息。
S501关于NM单元获取NRF实例的标识信息的方法可以参考S201，此处不再赘述。NF实例的信息可以是接收到的管理请求消息中携带的。
S502，NM单元向NF实例发送第一消息，所述第一消息包括NRF实例的标识信息。
第一消息中包括NRF实例的标识信息，NRF实例的标识信息用于指示与NF实例关联的NRF实例。也即，NF实例的信息由该NRF实例保存和维护，NF实例可以向该NRF实例进行注册和询问等操作。第一消息可以为第二配置请求消息。
从而，在存在多个NRF实例时，NM单元可以向NF实例指示与该NF实例关联的NRF实例。
S503，NM单元向NRF实例发送第八消息，所述第八消息包括NF实例的信息。
第八消息可以为第三配置请求消息，其中包括NF实例的信息，用于指示NRF保存NF实例的信息。
S504，NRF实例根据第八消息，保存NF实例的信息。
S505，终端向NF实例发送业务请求消息。
业务请求消息用于向NF实例请求一种或多种网络服务，由于当前的NF实例不能提供 终端请求的所有网络服务，此时终端需要向NRF查询其他可以提供终端请求的服务的NF实例。
S506，NF实例根据业务请求消息，向NRF实例发送第三消息。
第三消息可以为NF实例查询请求消息，用于根据业务请求消息向NRF实例查询其他NF实例的信息。第三消息中可以携带业务请求消息中请求的服务信息。
S507，NRF实例根据第三消息，查询其他NF实例的信息。
NRF实例根据第三消息，在存储的至少一个NF实例的信息中查询能够提供第三消息请求的服务的其他NF实例的信息。
S508，NRF实例向NF实例发送查询结果。
NRF实例若查询到能够提供第三消息请求的服务的其他NF实例的信息，则可以将该NF实例的网络地址等信息发送给NF实例，以使NF实例将业务请求消息路由到其他NF实例。
请参阅图6B，图6B是本申请实施例提供的又一种网络功能信息的管理方法的通信示意图。图6B所示的方案中，以管理网元为NM单元为例进行描述。其中，NM单元通过DM单元与NF实例通信，管理NF实例的配置。该方法包括但不限于如下步骤：
S601，NM单元获取NRF实例的标识信息，NRF实例中存储NF实例的信息。
S601的具体实现方式可以参考S201，此处不再赘述。
S602，NM单元向DM单元发送第七消息，所述第七消息包括NRF实例的标识信息。
第七消息可以是第一配置请求消息，其中包括NRF实例的标识信息以及NF实例的信息。需要说明的是，NF实例的信息可以是NM单元获取到的，此时第七消息中可以携带NF实例的信息；NF实例的信息也可以是DM单元预先获取到的，此时第七消息中可以不携带NF实例的信息。
S603，DM单元向NF实例发送第一消息，所述第一消息包括NRF实例的标识信息。
第一消息的描述可以参考S502，此处不再赘述。
从而，在存在多个NRF实例时，NM单元可以通过DM单元向NF实例指示与该NF实例关联的NRF实例。
S604，DM单元向NRF实例发送第九消息，所述第九消息包括NF实例的信息。
第九消息可以为第四配置请求消息，其中包括NF实例的信息，用于指示NRF保存NF实例的信息。
S605，NRF实例根据第九消息，保存NF实例的信息。
S606，终端向NF实例发送业务请求消息。
S607，NF实例根据业务请求消息，向NRF实例发送第三消息。
S608，NRF实例根据第三消息，查询其他NF实例的信息。
S609，NRF实例向NF实例发送查询结果。
S605-S609的具体实现方式可以参考S504-S508，此处不再赘述。
请参见图7，图7是本申请实施例提供的又一种网络功能信息的管理方法的流程示意图。图7中的管理单元可以是NM单元，也可以是DM单元。该方法包括但不限于如下步骤：
S701，管理网元获取NRF实例的标识信息，NRF实例中存储NF实例的信息。
S701的具体实现方式可以参考S201，此处不再赘述。
S702，管理网元根据NRF实例的标识信息，建立NF实例与NRF实例的关联关系。
在获取到NRF实例的标识信息后，管理网元可以建立当前需要配置的NF实例与NRF实例的关联关系，以便于之后向NF实例发送包括第一消息在内的相关消息时，可以直接获取到与NF实例关联的NRF实例。需要说明的是，关联关系的形式不作具体限定，只要能够表明NF实例与NRF实例相关联即可，例如，可以建立关联关系表，表中包括NF实例的标识信息以及其关联的NRF实例的标识信息。
在一种可选的实施场景中，管理网元可以在NF实例的管理对象中配置NRF实例的标识信息，NRF实例的标识信息用于指示与NF实例关联的NRF实例。其中，NF实例的管理对象是管理网元中存储NF实例的管理信息的一种日志文件。
从而，在存在多个NRF实例时，管理网元可以建立NF实例与NRF实例的关联关系，以便于后续可以指示NF实例向该NRF实例注册、更新或查询其他NF实例的信息。
进一步地，管理网元还可以向NF实例发送第一消息，所述第一消息包括NRF实例的标识信息。
第一消息可以配置请求消息，携带NRF实例的标识信息，NRF实例的标识信息用于指示与NF实例关联的NRF实例。也即，NRF实例存储该NF实例的信息，且NF实例向NRF实例查询其他NF实例的信息。
从而，NF实例可以直接向NRF实例注册或更新NF实例的信息，节约网络功能信息的配置时间，优化配置流程。
上述主要从不同管理单元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，管理网元、NF实例、NRF实例、NF实例的管理单元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。结合本申请中所公开的实施例描述的各示例的单元及算法步骤，本申请实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能，但是这种实现不应认为超出本申请实施例的技术方案的范围。
本申请实施例可以根据上述方法示例对管理网元、NF实例、NRF实例、NF实例的管理单元等进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的模块的情况下，图8A示出了本申请实施例中所涉及的管理网元的一种可能的示意性框图。管理网元800包括：处理模块802和通信模块803。处理模块802用于对管理网元的动作进行控制管理，例如，处理模块802用于支持管理网元800或通过通信模块803支持管理网元800执行图3中的过程S101-S103，图4中的过程S201-S203，图5A中的过程S301、S302、S306、S309、S313，图5B中的过程S401-S403、S407、S408、S411、S412、S415、S416，图6A中的过程S501-S503，图6B中的过程S601-S604，图7中的过程S701-S702，和/或用于本文所描述的技术的其它过程。通信模块803用于支持管理网元800与NF实例、NF实例的管理单元、NRF实例、其他管理网元或其他设备之间的通信。 管理网元800还可以包括存储模块801，用于存储管理网元800的程序代码和数据。
其中，处理模块802可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块803可以是通信接口、收发器或收发电路等，其中，该通信接口是统称，在具体实现中，该通信接口可以包括多个接口，例如可以包括：管理网元800与NF实例、NF实例的管理单元、NRF实例、其他管理网元之间的接口和/或与其他设备之间的接口。存储模块801可以是存储器。
当处理模块802为处理器，通信模块803为通信接口，存储模块801为存储器时，本申请实施例所涉及的管理网元可以为图8B所示的管理网元810。
参阅图8B所示，该管理网元810包括：处理器812、通信接口813、存储器811。可选的，管理网元810还可以包括总线814。其中，通信接口813、处理器812以及存储器811可以通过总线814相互连接；总线814可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等。所述总线814可以分为地址总线、数据总线和控制总线等。为便于表示，图8B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
上述图8A和图8B所示的管理网元可以是图2中的“NM单元/NSMF单元”或“DM单元/NSSMF单元”。
在采用集成的模块的情况下，图9A示出了本申请实施例中所涉及的NF实例的一种可能的示意性框图。NF实例900包括：处理模块902和通信模块903。处理模块902用于对NF实例900的动作进行控制管理，例如，处理模块902用于通过通信模块903支持NF实例900执行图4中的过程S205和S207，图5A中的过程S303、S307和S311，图5B中的过程S404、S409和S414，图6A中的过程S506，图6B中的过程S607，和/或用于本文所描述的技术的其它过程。通信模块903用于支持NF实例900与管理网元、NRF实例或NF实例的管理单元之间的通信。NF实例900还可以包括存储模块901，用于NF实例900的程序代码和数据。
其中，处理模块902可以是处理器或控制器，例如可以是CPU，通用处理器，DSP，ASIC，FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块903可以是通信接口、收发器或收发电路等，其中，该通信接口是统称，在具体实现中，该通信接口可以包括多个接口，例如可以包括：NF实例900与管理网元、NRF实例或NF实例的管理单元之间的接口和/或其他接口。存储模块901可以是存储器。
当处理模块902为处理器，通信模块903为通信接口，存储模块901为存储器时，本 申请实施例所涉及的NF实例可以为图9B所示的NF实例。
参阅图9B所示，该NF实例910包括：处理器912、通信接口913、存储器911。可选的，NF实例910还可以包括总线914。其中，通信接口913、处理器912以及存储器911可以通过总线914相互连接；总线914可以是PCI总线或EISA总线等。所述总线914可以分为地址总线、数据总线和控制总线等。为便于表示，图9B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
上述图9A和图9B所示的NF实例可以是图1中的NF实例。
本申请实施例还提供一种NRF实例，该NRF实例的结构示意图类似于上述NF实例的结构示意图，如图10A和图10B所示。该NRF实例包括的模块或器件可以对应执行上述方法中所涉及的NRF实例所完成的动作，此处不作赘述。
本申请实施例还提供一种NF实例的管理单元，该NF实例的管理单元的结构示意图类似于上述管理网元的结构示意图，如图11A和图11B所示。该NF实例的管理单元包括的模块或器件可以对应执行上述方法中所涉及的NF实例的管理单元所完成的动作，此处不作赘述。
结合本申请实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于管理网元、NF实例、NRF实例或NF实例的管理单元中。当然，处理器和存储介质也可以作为分立组件存在于管理网元、NF实例、NRF实例或NF实例的管理单元中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请实施例所描述的功能可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(Digital Video Disc，DVD))、或者半导体介质(例如，固态硬盘(Solid State Disk，SSD))等。
以上所述的具体实施方式，对本申请实施例的目的、技术方案和有益效果进行了进一 步详细说明，所应理解的是，以上所述仅为本申请实施例的具体实施方式而已，并不用于限定本申请实施例的保护范围，凡在本申请实施例的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请实施例的保护范围之内。

Claims (29)

  1. 一种网络功能信息的管理方法，其特征在于，包括：
    管理网元获取网络仓库功能NRF实例的标识信息，其中，所述NRF实例中存储网络功能NF实例的信息，所述NRF实例的标识信息用于指示与所述NF实例关联的所述NRF实例；
    所述管理网元向所述NF实例或者所述NF实例的管理单元发送第一消息，所述第一消息包括所述NRF实例的标识信息；或者，所述管理网元根据所述NRF实例的标识信息，建立所述NF实例与所述NRF实例的关联关系。
  2. 如权利要求1所述的方法，其特征在于，所述第一消息还包括所述NF实例的信息。
  3. 如权利要求1所述的方法，其特征在于，所述管理网元根据所述NRF实例的标识信息，建立所述NF实例与所述NRF实例的关联关系，包括：
    所述管理网元在所述NF实例的管理对象中配置所述NRF实例的标识信息。
  4. 如权利要求1-3任一项所述的方法，其特征在于，所述管理网元获取网络仓库功能NRF实例的标识信息，包括：
    所述管理网元接收管理请求消息，所述管理请求消息包括所述NRF实例的标识信息或所述NRF实例的指示信息，所述NRF实例的指示信息用于获取所述NRF实例的标识信息；
    或者，
    所述管理网元获取网络模板中描述的所述NRF实例的标识信息或所述NRF实例的指示信息，所述NRF实例的指示信息用于获取所述NRF实例的标识信息。
  5. 如权利要求4所述的方法，其特征在于，所述NRF实例的指示信息包括隔离需求信息、安全信息、位置信息、用户信息或网络信息中的至少一个。
  6. 如权利要求4或5所述的方法，其特征在于，当所述第一消息包括所述NF实例的信息时，所述管理请求消息还包括所述NF实例的信息。
  7. 如权利要求1-6任一项所述的方法，其特征在于，所述第一消息还包括注册指示信息，所述注册指示信息用于指示所述NF实例是否向所述NRF实例注册。
  8. 如权利要求1-7任一项所述的方法，其特征在于，所述NRF实例的标识信息包括所述NRF实例的标识、所述NRF实例的名称或所述NRF实例的网络地址中的至少一个。
  9. 如权利要求1-8任一项所述的方法，其特征在于，所述NF实例的信息包括实例类型、地址信息、域名信息、所属网络切片的切片信息、服务区域、所属NF组信息或发现策略中的至少一个。
  10. 一种网络功能信息的管理方法，其特征在于，包括：
    网络功能NF实例从管理网元接收第一消息，所述第一消息包括存储所述NF实例的信息的NRF实例的标识信息，所述NRF实例的标识信息用于指示与所述NF实例关联的所述NRF实例；
    所述NF实例向所述NRF实例发送第二消息，所述第二消息包括所述NF实例的信息，所述第二消息用于指示所述NRF实例保存或更新所述NF实例的信息；
    或者，所述NF实例向所述NRF实例发送第三消息，所述第三消息用于向所述NRF实例查询其他NF实例的信息。
  11. 如权利要求10所述的方法，其特征在于，所述第一消息还包括所述NF实例的信息。
  12. 如权利要求10或11所述的方法，其特征在于，所述第二消息为所述NF实例或所述NF实例对应的服务的注册请求消息；
    所述NF实例向所述NRF实例发送第二消息之前，还包括：
    所述NF实例从所述管理网元接收激活请求消息，所述激活请求消息用于激活所述NF实例或者所述NF实例对应的服务，以触发所述NF实例向所述NRF实例发送所述注册请求消息。
  13. 如权利要求10-12任一项所述的方法，其特征在于，所述方法还包括：
    所述NF实例向所述NRF实例发送第四消息，所述第四消息用于指示所述NRF实例删除所述NF实例的信息或将所述NF实例的信息设置为不可用。
  14. 如权利要求13所述的方法，其特征在于，所述第四消息为所述NF实例或所述NF实例对应的服务的去注册请求消息；
    所述NF实例向所述NRF实例发送第四消息之前，还包括：
    所述NF实例从所述管理网元接收去激活请求消息，所述去激活请求消息用于去激活所述NF实例或者NF实例对应的服务，以触发所述NF实例向所述NRF实例发送所述去注册请求消息。
  15. 一种管理网元，其特征在于，所述管理网元包括处理模块和通信模块，
    所述处理模块用于获取网络仓库功能NRF实例的标识信息，其中，所述NRF实例中存储网络功能NF实例的信息，所述NRF实例的标识信息用于指示与所述NF实例关联的所述NRF实例；以及用于通过所述通信模块向所述NF实例或者所述NF实例的管理单元发送第一消息，所述第一消息包括所述NRF实例的标识信息；
    或者，所述管理网元包括处理模块，
    所述处理模块用于获取网络仓库功能NRF实例的标识信息，其中，所述NRF实例中存储网络功能NF实例的信息，所述标识信息用于指示与所述NF实例关联的所述NRF实例；以及用于根据所述NRF实例的标识信息，建立所述NF实例与所述NRF实例的关联关系。
  16. 如权利要求15所述的管理网元，其特征在于，所述第一消息还包括所述NF实例的信息。
  17. 如权利要求15所述的管理网元，其特征在于，所述处理模块具体用于在所述NF实例的管理对象中配置所述NRF实例的标识信息。
  18. 如权利要求15-17任一项所述的管理网元，其特征在于，
    所述通信模块具体用于接收管理请求消息，所述管理请求消息包括所述NRF实例的标识信息或所述NRF实例的指示信息，所述NRF实例的指示信息用于获取所述NRF实例的标识信息；
    或者，
    所述处理模块具体用于获取网络模板中描述的所述NRF实例的标识信息或所述NRF实例的指示信息，所述NRF实例的指示信息用于获取所述NRF实例的标识信息。
  19. 如权利要求18所述的管理网元，其特征在于，所述NRF实例的指示信息包括隔离 需求信息、安全信息、位置信息、用户信息以及网络信息中的至少一个。
  20. 如权利要求18或19所述的管理网元，其特征在于，当所述第一消息包括所述NF实例的信息时，所述管理请求消息还包括所述NF实例的信息。
  21. 如权利要求15-20任一项所述的管理网元，其特征在于，所述第一消息还包括注册指示信息，所述注册指示信息用于指示所述NF实例是否向所述NRF实例注册。
  22. 如权利要求15-21任一项所述的管理网元，其特征在于，所述NRF实例的标识信息包括所述NRF实例的标识、所述NRF实例的名称或所述NRF实例的网络地址中的至少一个。
  23. 如权利要求15-22任一项所述的管理网元，其特征在于，所述NF实例的信息包括实例类型、地址信息、域名信息、所属网络切片的切片信息、服务区域或发现策略中的至少一个。
  24. 一种网络功能NF实例，其特征在于，包括处理模块和通信模块，
    所述处理模块用于通过通信模块从管理网元接收第一消息，所述第一消息包括存储所述NF实例的信息的NRF实例的标识信息，所述NRF实例的标识信息用于指示与所述NF实例关联的所述NRF实例；以及用于通过所述通信模块向所述NRF实例发送第二消息，所述第二消息包括所述NF实例的信息，所述第二消息用于指示所述NRF实例保存或更新所述NF实例的信息；或者，用于通过所述通信模块向所述NRF实例发送第三消息，所述第三消息用于向所述NRF实例查询其他NF实例的信息。
  25. 如权利要求24所述的NF实例，其特征在于，所述第一消息还包括所述NF实例的信息。
  26. 如权利要求24或25所述的NF实例，其特征在于，所述第二消息为所述NF实例或所述NF实例对应的服务的注册请求消息；所述处理模块还用于在通过所述通信模块向所述NRF实例发送所述第二消息之前，通过所述通信模块从所述管理网元接收激活请求消息，所述激活请求消息用于激活所述NF实例或者所述NF实例对应的服务，以触发所述NF实例向所述NRF实例发送所述注册请求消息。
  27. 如权利要求24-26任一项所述的NF实例，其特征在于，所述处理模块还用于通过所述通信模块向所述NRF实例发送第四消息，所述第四消息用于指示所述NRF实例删除所述NF实例的信息或将所述NF实例的信息设置为不可用。
  28. 如权利要求27所述的NF实例，其特征在于，所述第四消息为所述NF实例或所述NF实例对应的服务的去注册请求消息；所述处理模块还用于在通过所述通信模块向所述NRF实例发送所述第四消息之前，通过所述通信模块从所述管理网元接收去激活请求消息，所述去激活请求消息用于去激活所述NF实例或者NF实例对应的服务，以触发所述NF实例向所述NRF实例发送所述去注册请求消息。
  29. 一种通信系统，其特征在于，所述通信系统包括如权利要求15-23任一项所述的管理网元和如权利要求24-28任一项所述的网络功能NF实例；或者，所述通信系统包括网络仓库功能NRF实例、如权利要求15-23任一项所述的管理网元和如权利要求24-28任一项所述的NF实例；或者，所述通信系统包括NRF实例、NF实例的管理单元、如权利要求15-23任一项所述的管理网元和如权利要求24-28任一项所述的网络功能NF实例。
PCT/CN2018/099179 2017-08-07 2018-08-07 网络功能信息的管理方法及相关设备 WO2019029525A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18844495.4A EP3664370B1 (en) 2017-08-07 2018-08-07 Network function information management method and related device
US16/783,326 US11277306B2 (en) 2017-08-07 2020-02-06 Sending information of a network repository function instance storing network function instance information

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710665551.3 2017-08-07
CN201710665551.3A CN109379206B (zh) 2017-08-07 2017-08-07 网络功能信息的管理方法及相关设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/783,326 Continuation US11277306B2 (en) 2017-08-07 2020-02-06 Sending information of a network repository function instance storing network function instance information

Publications (1)

Publication Number Publication Date
WO2019029525A1 true WO2019029525A1 (zh) 2019-02-14

Family

ID=65273349

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/099179 WO2019029525A1 (zh) 2017-08-07 2018-08-07 网络功能信息的管理方法及相关设备

Country Status (4)

Country Link
US (1) US11277306B2 (zh)
EP (1) EP3664370B1 (zh)
CN (1) CN109379206B (zh)
WO (1) WO2019029525A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020169173A1 (en) * 2019-02-18 2020-08-27 Huawei Technologies Co., Ltd. Entities for providing an external service to a network
CN112788085A (zh) * 2019-11-11 2021-05-11 华为技术有限公司 一种数据缓存方法和装置
RU2784441C1 (ru) * 2019-02-18 2022-11-24 Хуавей Текнолоджиз Ко., Лтд. Объекты для предоставления внешних сервисов для сети связи

Families Citing this family (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109391592B (zh) * 2017-08-08 2021-12-24 华为技术有限公司 网络功能服务的发现方法及设备
US11271846B2 (en) 2018-10-22 2022-03-08 Oracle International Corporation Methods, systems, and computer readable media for locality-based selection and routing of traffic to producer network functions (NFs)
WO2020146327A1 (en) * 2019-01-08 2020-07-16 Mavenir Networks, Inc. Optimal network function data path discovery for 5g core
CN110086652B (zh) * 2019-03-25 2023-04-18 北京天地互连信息技术有限公司 一种针对5g核心网中服务网元的管理系统及其方法
CN111835802B (zh) * 2019-04-18 2021-08-27 大唐移动通信设备有限公司 一种通信方法及装置
CN111901367B (zh) * 2019-05-06 2022-04-29 华为技术有限公司 一种网络数据分析方法及装置
CN112087770B (zh) * 2019-06-13 2022-05-17 华为技术有限公司 一种通知服务状态的方法、通信系统和通信装置
CN112104468B (zh) * 2019-06-17 2021-12-03 华为技术有限公司 一种管理服务的发现方法及装置
US11159359B2 (en) 2019-06-26 2021-10-26 Oracle International Corporation Methods, systems, and computer readable media for diameter-peer-wide egress rate limiting at diameter relay agent (DRA)
US11252093B2 (en) 2019-06-26 2022-02-15 Oracle International Corporation Methods, systems, and computer readable media for policing access point name-aggregate maximum bit rate (APN-AMBR) across packet data network gateway data plane (P-GW DP) worker instances
US11323413B2 (en) 2019-08-29 2022-05-03 Oracle International Corporation Methods, systems, and computer readable media for actively discovering and tracking addresses associated with 4G service endpoints
CN113055535B (zh) * 2019-12-26 2022-06-24 中国电信股份有限公司 用于生成5g端到端话单的方法和系统
US11224009B2 (en) 2019-12-30 2022-01-11 Oracle International Corporation Methods, systems, and computer readable media for enabling transport quality of service (QoS) in 5G networks
CN113067844B (zh) * 2020-01-02 2022-08-12 中国移动通信有限公司研究院 服务发现方法、装置及hnrf
EP4101131A1 (en) * 2020-02-05 2022-12-14 Telefonaktiebolaget Lm Ericsson (Publ) Identifying an instance of a virtual network function
CN111314944B (zh) * 2020-02-13 2020-11-13 广州爱浦路网络技术有限公司 一种基于顶级nrf的管理5g核心网中nrf的方法
CN113329417B (zh) * 2020-02-28 2023-07-18 华为技术有限公司 一种网络配置方法及装置
CN111416827B (zh) * 2020-03-25 2021-09-21 广州爱浦路网络技术有限公司 根据安全等级发现网络功能nf的方法
US11438828B2 (en) 2020-07-29 2022-09-06 Oracle International Corporation Methods, systems, and computer readable media for providing network function discovery service enhancements
US11528334B2 (en) 2020-07-31 2022-12-13 Oracle International Corporation Methods, systems, and computer readable media for preferred network function (NF) location routing using service communications proxy (SCP)
US11290549B2 (en) * 2020-08-24 2022-03-29 Oracle International Corporation Methods, systems, and computer readable media for optimized network function (NF) discovery and routing using service communications proxy (SCP) and NF repository function (NRF)
US11483694B2 (en) * 2020-09-01 2022-10-25 Oracle International Corporation Methods, systems, and computer readable media for service communications proxy (SCP)-specific prioritized network function (NF) discovery and routing
US11570262B2 (en) 2020-10-28 2023-01-31 Oracle International Corporation Methods, systems, and computer readable media for rank processing for network function selection
US11470544B2 (en) 2021-01-22 2022-10-11 Oracle International Corporation Methods, systems, and computer readable media for optimized routing of messages relating to existing network function (NF) subscriptions using an intermediate forwarding NF repository function (NRF)
US11589298B2 (en) * 2021-03-05 2023-02-21 Oracle International Corporation Methods, systems, and computer readable media for selecting multiple network function types using a single discovery request
US11496954B2 (en) 2021-03-13 2022-11-08 Oracle International Corporation Methods, systems, and computer readable media for supporting multiple preferred localities for network function (NF) discovery and selection procedures
US11888946B2 (en) 2021-06-02 2024-01-30 Oracle International Corporation Methods, systems, and computer readable media for applying or overriding preferred locality criteria in processing network function (NF) discovery requests
US11895080B2 (en) 2021-06-23 2024-02-06 Oracle International Corporation Methods, systems, and computer readable media for resolution of inter-network domain names
US12022316B2 (en) 2021-06-23 2024-06-25 Oracle International Corporation Methods, systems, and computer readable media for optimizing network traffic distribution using timeslot-based tracked producer network function (NF) performance during producer NF selection
US11950178B2 (en) 2021-08-03 2024-04-02 Oracle International Corporation Methods, systems, and computer readable media for optimized routing of service based interface (SBI) request messages to remote network function (NF) repository functions using indirect communications via service communication proxy (SCP)
US11930083B2 (en) 2021-08-09 2024-03-12 Oracle International Corporation Methods, systems, and computer readable media for processing network function (NF) discovery requests at NF repository function (NRF) using prioritized lists of preferred locations
US11871309B2 (en) 2021-09-28 2024-01-09 Oracle International Corporation Methods, systems, and computer readable media for network function discovery using preferred-locality information
CN113825134A (zh) * 2021-09-29 2021-12-21 新华三技术有限公司 一种网络服务授权方法、装置及设备
US11849506B2 (en) 2021-10-08 2023-12-19 Oracle International Corporation Methods, systems, and computer readable media for routing inter-public land mobile network (inter-PLMN) messages related to existing subscriptions with network function (NF) repository function (NRF) using security edge protection proxy (SEPP)
US11888957B2 (en) 2021-12-07 2024-01-30 Oracle International Corporation Methods, systems, and computer readable media for locality and serving scope set based network function (NF) profile prioritization and message routing
US11917720B2 (en) 2021-12-14 2024-02-27 Oracle International Corporation Methods, systems, and computer readable media for enabling forwarding of subsequent network function subscription updates
US11652895B1 (en) 2022-02-15 2023-05-16 Oracle International Corporation Methods, systems, and computer readable media for dynamic optimized network function discovery for consumer network functions

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105247826A (zh) * 2013-01-11 2016-01-13 华为技术有限公司 网络设备的网络功能虚拟化
WO2016121834A1 (ja) * 2015-01-29 2016-08-04 日本電気株式会社 ネットワーク機能仮想化管理方法とシステムと装置とプログラム

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5664126A (en) * 1992-07-24 1997-09-02 Kabushiki Kaisha Toshiba Human interface system for communicating networked users
CN102377629B (zh) 2010-08-20 2014-08-20 华为技术有限公司 终端穿越私网与ims核心网中服务器通信的方法、装置及网络系统
CN102547804B (zh) * 2010-12-15 2015-08-26 上海贝尔股份有限公司 一种用于对无线接入网络进行网络管理的运行维护系统
US10171939B2 (en) * 2014-07-15 2019-01-01 Belkin International, Inc. Control based on geo-dependent conditions
CN105376083B (zh) * 2014-08-25 2018-12-14 华为技术有限公司 节能控制方法、管理服务器和网络设备
JP2016082521A (ja) * 2014-10-21 2016-05-16 富士通株式会社 情報処理装置、及び、情報処理方法
US10334468B2 (en) * 2015-10-05 2019-06-25 Cisco Technology, Inc. Scalable control plane
WO2017075757A1 (zh) * 2015-11-03 2017-05-11 华为技术有限公司 选择网络功能服务的方法、装置和系统
WO2017143047A1 (en) * 2016-02-16 2017-08-24 Idac Holdings, Inc. Network slicing operation
US10142994B2 (en) * 2016-04-18 2018-11-27 Electronics And Telecommunications Research Institute Communication method and apparatus using network slicing
WO2018008980A1 (ko) * 2016-07-05 2018-01-11 엘지전자(주) 무선 통신 시스템에서 사용자가 선호하는 자원 운용 선택 방법 및 이를 위한 장치
EP3276518B1 (de) * 2016-07-29 2018-09-19 Deutsche Telekom AG Mobiles kommunikationsgerät mit mehrzahl über eine pin freischaltbarer anwendungen
CN109565746B (zh) * 2016-08-16 2021-10-19 Idac控股公司 Wtru以及wtru中实施的用于无线通信的方法
EP3525545B1 (en) * 2016-10-07 2021-07-14 LG Electronics Inc. Methods for selecting session and service continuity mode in a wireless communication system
KR20180038716A (ko) * 2016-10-07 2018-04-17 삼성전자주식회사 단말의 시그널링 메시지를 Network Function 간 전달하는 방안
CN108632312B (zh) * 2017-03-20 2020-01-17 中国移动通信有限公司研究院 网络功能信息交互方法及装置
KR102620149B1 (ko) * 2017-05-08 2024-01-03 모토로라 모빌리티 엘엘씨 데이터 접속을 재구성하기 위한 방법들 및 장치들
US10820185B2 (en) * 2017-05-08 2020-10-27 Qualcomm Incorporated Mobility between areas with heterogeneous network slices
HUE046372T2 (hu) * 2017-05-08 2020-03-30 Ntt Docomo Inc Eljárás hálózati funkcióknak mobil rádiós kommunikációs hálózat hálózati szeletpéldányaival való társításához
US11316923B2 (en) * 2017-07-21 2022-04-26 Telefonaktiebolaget Lm Ericsson (Publ) Unstructured data storage function (UDSF) services

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105247826A (zh) * 2013-01-11 2016-01-13 华为技术有限公司 网络设备的网络功能虚拟化
WO2016121834A1 (ja) * 2015-01-29 2016-08-04 日本電気株式会社 ネットワーク機能仮想化管理方法とシステムと装置とプログラム

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CHINA MOBILE ET AL.: "23.501: High Level Description of NF Service Registration", SA WG2 MEETING #S2-120 S 2-172359, 3 April 2017 (2017-04-03), XP051257926 *
See also references of EP3664370A4 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020169173A1 (en) * 2019-02-18 2020-08-27 Huawei Technologies Co., Ltd. Entities for providing an external service to a network
RU2784441C1 (ru) * 2019-02-18 2022-11-24 Хуавей Текнолоджиз Ко., Лтд. Объекты для предоставления внешних сервисов для сети связи
EP4300920A3 (en) * 2019-02-18 2024-03-20 Huawei Technologies Co., Ltd. Entities for providing an external service to a network
US11963124B2 (en) 2019-02-18 2024-04-16 Huawei Technologies Co., Ltd. Entities for providing an external service to a network
CN112788085A (zh) * 2019-11-11 2021-05-11 华为技术有限公司 一种数据缓存方法和装置
CN112788085B (zh) * 2019-11-11 2022-08-09 华为技术有限公司 一种数据缓存方法和装置

Also Published As

Publication number Publication date
CN109379206A (zh) 2019-02-22
EP3664370A1 (en) 2020-06-10
EP3664370A4 (en) 2020-08-12
CN109379206B (zh) 2022-04-22
US20210044481A1 (en) 2021-02-11
US11277306B2 (en) 2022-03-15
EP3664370B1 (en) 2022-03-09

Similar Documents

Publication Publication Date Title
EP3664370B1 (en) Network function information management method and related device
JP7139522B2 (ja) ローカルエリアネットワーク通信方法、装置、およびシステム
CN111436160B (zh) 一种局域网通信方法、装置及系统
US11026080B2 (en) Policy control function determining method, apparatus, and system
KR102478442B1 (ko) Ｐｄｕ 유형 설정 방법, ｕｅ 정책 설정 방법 및 관련 엔티티
WO2018006784A1 (zh) 一种网络切片选择方法、设备及系统
CN111901135B (zh) 一种数据分析方法及装置
EP3358887A1 (en) User equipment registration method for network slice selection and network controller and network communication system using the same
EP3648432B1 (en) Discovery method and device for network function service
WO2018232570A1 (zh) 一种注册及会话建立的方法、终端和amf实体
WO2021037175A1 (zh) 一种网络切片的管理方法及相关装置
US20220060881A1 (en) Group management method, apparatus, and system
WO2019196811A1 (zh) 通信方法和相关装置
WO2019029268A1 (zh) 网络切片的部署方法和装置
WO2018024121A1 (zh) 一种网络功能nf管理方法及nf管理设备
CN112533177A (zh) 一种提供、发现移动边缘计算的方法及设备、装置、介质
CN111770123B (zh) 通信方法、设备及存储介质
WO2021052109A1 (zh) 通信方法及装置
WO2023236497A1 (zh) 鉴权方法、装置、存储介质和电子设备
WO2020253343A1 (zh) 一种管理服务的发现方法及装置
WO2021115464A1 (zh) 一种网络切片选择方法及相关装置
JP2024519311A (ja) データ入手方法およびシステム、ならびにその装置
US20140173073A1 (en) Proactive M2M Framework Using Device-Level vCard for Inventory, Identity, and Network Management
CN112153584A (zh) 一种策略和计费控制的实现方法及装置
WO2018126483A1 (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: 18844495

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018844495

Country of ref document: EP

Effective date: 20200303