Apparatus and method for performing network function management and discovery in wireless network

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Embodiments herein disclose a method for performing network function (NF) management and discovery in a wireless network. The method includes receiving, by a network repository function (NRF) device from a first NF instance entity, a first registration request to register common data in a separate profile, and receiving, by the NRF device from the first NF instance entity, a second registration request to register a NF instance profile. The NF instance configuration file includes a pointer of a configuration file of the NF instance specific data and the common data.

Description

Technical Field

[0001] Embodiments disclosed herein relate to wireless networks, and more particularly, to systems and methods for performing network function management and discovery in wireless networks when network function (NF) instances are deployed in NF sets. Background Art

[0002] The fifth generation (5G) mobile communication technology defines a wide frequency band so that high transmission rates and new services are possible, and can be realized not only in "below 6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands called mmWave including 28 GHz and 39 GHz. In addition, it has been considered to implement 6G mobile communication technology (called super 5G system) in terahertz frequency bands (e.g., 95 GHz to 3 THz frequency bands) in order to achieve a transmission rate fifty times faster than 5G mobile communication technology and an ultra-low latency one-tenth of that of 5G mobile communication technology.

[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine type communication (mMTC), standardization is underway on beamforming and massive MIMO for mitigating radio wave path loss in millimeter waves and increasing radio wave transmission distance, parameter sets supporting dynamic operation for efficient utilization of millimeter wave resources and time slot formats (e.g., operating multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods such as LDPC (low-density parity check) codes for large-volume data transmission and polar codes for highly reliable transmission of control information, L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.

[0004] Currently, in view of the services supported by 5G mobile communication technology, discussions are underway on improvements and performance enhancements of initial 5G mobile communication technology, and there is already physical layer standardization on technologies such as V2X (Vehicle to Everything) for assisting driving determination of autonomous vehicles based on information about the location and status of the vehicle transmitted by the vehicle and for enhancing user convenience, NR-U (New Radio Unlicensed) for system operation intended to comply with various regulatory-related requirements in unlicensed bands, NR UE power saving, non-terrestrial network (NTN) (which is UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable), and positioning.

[0005] In addition, there has been standardization of technologies in air interface architecture / protocols, such as Industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional switching and DAPS (Dual Active Protocol Stack) switching, and two-step random access (two-step RACH for NR) for simplifying the random access process. Standardization is also underway on the 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and the system architecture / service for mobile edge computing (MEC) for receiving services based on UE location.

[0006] As 5G mobile communication systems are commercialized, the number of connected devices, which has been growing exponentially, will be connected to the communication network, and it is therefore expected that enhanced functions and performance of the 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research related to extended reality (XR) is arranged to effectively support AR (augmented reality), VR (virtual reality), MR (mixed reality), etc., to improve 5G performance and reduce complexity by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaspace service support, and drone communication.

[0007] In addition, such development of 5G mobile communication systems will not only serve as a foundation for developing new waveforms for providing terahertz band coverage for 6G mobile communication technology, multi-antenna transmission technologies (such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas), metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technology using OAM (orbital angular momentum) and RIS (reconfigurable smart surface), and full-duplex technology for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for achieving system optimization by utilizing satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for achieving services at a level that exceeds the complexity by reducing the limitations of UE operating capabilities by utilizing ultra-high performance communication and computing resources.

[0008] Therefore, it is desirable to address the above-mentioned disadvantages or other disadvantages, or at least provide a useful alternative to perform network function management and discovery in wireless networks where network function (NF) instances are deployed in NF sets. Summary of the invention

[0009] Technical issues

[0010] Embodiments of the present disclosure relate to apparatus and methods for performing network function management and discovery in a communication network when network function instances are deployed in NF sets.

[0011] Embodiments of the present disclosure relate to how member NF instances of an NF set can register their profiles into an NRF device without having to copy common profile parameters into the profile of each NF instance.

[0012] Embodiments of the present disclosure relate to how an NRF device can provide a configuration file of a NF set containing common configuration file parameters of NF instances belonging to the NF set to a NF consumer.

[0013] Embodiments of the present disclosure relate to how to avoid the need to notify NF consumers via multiple notifications due to configuration file changes of member NF instances when the data changes are in a common parameter set.

[0014] Solution to the problem

[0015] An embodiment of the present disclosure provides a method for performing NF management and discovery in a wireless network. The method includes receiving, by an NRF device, a first registration request for registering common data in a separate configuration file from a first NF instance entity. In addition, the method includes receiving, by the NRF device, a second registration request for registering a NF instance configuration file from the first NF instance entity. The NF instance configuration file includes NF instance specific data and a pointer to a configuration file pointing to common data.

[0016] In an embodiment, common data refers to configuration file information that is common to multiple NF instances.

[0017] In an embodiment, the specific data refers to configuration file information specific to the NF instance.

[0018] In an embodiment, a NF instance belongs to a NF set.

[0019] In an embodiment, common data refers to data that is common to NF instances belonging to a NF set.

[0020] In an embodiment, receiving, by the NRF device, a first registration request for registering common data in a separate configuration file from a first NF instance entity includes: receiving, by the NRF device, a first determination request for determining whether an NF set configuration file of a first NF set exists with the NRF device, sending, by the NRF device based on the determination request, a first response indicating that an NF set configuration file of the first NF set does not exist with the NRF device, and receiving, by the NRF device, a first registration request for registering the common data in a separate configuration file into the NRF device.

[0021] In an embodiment, receiving, by the NRF device, a second registration request for registering a NF instance profile from the first NF instance entity includes: receiving, from the first NF instance entity, a registration request for registering the NF instance profile with the NRF device, sending, by the NRF device, a first response indicating that there is no profile with common data with the NRF device, and receiving, by the NRF device, a registration request for registering common data in a separate profile into the NRF device.

[0022] In an embodiment, Nnrf_NFManagement_NFRegister is used to receive a second registration request for registering a NF instance profile.

[0023] Embodiments of the present disclosure provide a method for performing NF management and discovery in a wireless network. The method includes receiving, by an NRF device, a discovery request for discovering a specific type of NF instance from an NF consumer. In addition, the method includes identifying, by the NRF device, the NF instance based on the discovery request. In addition, the method includes sending, by the NRF device, a discovery response to the NF consumer. The discovery response includes NF instance-specific data of a plurality of NF instances and a pointer to a configuration file containing common data of the plurality of NF instances.

[0024] In an embodiment, a profile pointer to the NF Set profile is included in the discovery response instead of common data.

[0025] In an embodiment, the method includes receiving, by the NRF device, a discovery request for a shared NF set profile from the NF consumer when the NF consumer determines that the NF set profile is not available in the NF consumer. In addition, the method includes sending, by the NRF device, the NF set profile to the NF consumer based on the discovery request.

[0026] In an embodiment, the method includes receiving, by the NRF device, a subscription request associated with a data change notification for a change to a NF Set profile. Furthermore, the method includes determining, by the NRF device, a change to public data associated with the NF Set profile. Furthermore, the method includes sending, by the NRF device, a message to the NF Consumer indicating a change to public data associated with the NF Set profile.

[0027] An embodiment of the present disclosure provides a method for performing NF management and discovery in a wireless network. The method includes classifying NF instance profile data into public data and specific data by a first NF instance entity. In addition, the method includes sending a first registration request by the first NF instance entity to register the public data in a separate profile in an NRF device. In addition, the method includes sending a second registration request by the first NF instance entity to register the NF instance profile with the NRF device. The NF instance profile includes NF instance specific data and a pointer to a profile of the public data.

[0028] In an embodiment, common data is identified and registered as an “NF Set” profile in NRF.

[0029] In an embodiment, the NF instance entity sending a first registration request to register the public data in the separate configuration file in the NRF device includes sending a first determination request by the first NF instance entity to determine whether the NF set configuration file of the first NF set exists with the NRF, receiving a first response by the first NF instance entity based on the determination request indicating that the NF set configuration file of the first NF set does not exist with the NRF device, and sending the first registration request by the NF instance entity to register the public data in the separate configuration file in the NRF device.

[0030] In an embodiment, the NF instance entity sends a second registration request to register the NF instance configuration file with the NRF device, including sending a registration request to register the NF instance configuration file with the NRF device by the first NF instance entity, receiving a first response by the first NF instance entity indicating that there is no configuration file with common data with the NRF device, and sending a third registration request by the NF instance entity to register the common data in the separate configuration file in the NRF device. The NF instance configuration file includes NF instance specific data and a pointer to the configuration file pointing to the common data.

[0031] Embodiments of the present disclosure provide a method for performing NF management and discovery in a wireless network. The method includes sending a discovery request by a NF consumer to an NRF device to discover a NF instance of a specific type. In addition, the method includes receiving a discovery response by the NF consumer from the NRF device, wherein the discovery response includes NF instance-specific data of a plurality of NF instances matching the requested type, and an indicator of a common data profile.

[0032] In an embodiment, the NRF device identifies the NF instance based on the discovery request. The NF instance is associated with the NF instance public data.

[0033] In an embodiment, an indicator of the NF Set Profile is included in the discovery response instead of the common data.

[0034] In an embodiment, the method includes, when determining that the NF set profile is not available in the NF consumer, the NF consumer sends a request to the NRF device to discover the NF set profile. In addition, the method includes receiving the NF set profile from the NRF device by the NF consumer based on the discovery request.

[0035] In an embodiment, the method includes sending, by the NF consumer, a subscription request associated with a data change notification for a change of a NF set configuration file to the NRF device. In addition, the method includes receiving, by the NF consumer, a message indicating a change of the public data associated with the NF set configuration file from the NRF device upon determining a change of the public data associated with the NF set configuration file at the NRF device.

[0036] An embodiment of the present disclosure provides an NRF device, including a NF management and discovery controller coupled to a processor and a memory. The NF management and discovery controller is configured to receive a first registration request from a first NF instance entity to register common data in a separate configuration file. In addition, the NF management and discovery controller is configured to receive a second registration request from the first NF instance entity to register a NF instance configuration file. The NF instance configuration file includes NF instance specific data and a pointer to a configuration file pointing to common data.

[0037] An embodiment of the present disclosure provides an NF instance entity, including an NF management and discovery controller coupled to a processor and a memory. The NF management and discovery controller is configured to classify NF instance profile data into public data and specific data. In addition, the NF management and discovery controller is configured to send a first registration request to register the public data in a separate profile into an NRF device. In addition, the NF management and discovery controller is configured to send a second registration request to register the NF instance profile with the NRF device. The NF instance profile includes NF instance specific data and a pointer to the profile of the public data.

[0038] An embodiment of the present disclosure provides a NF consumer, including a NF management and discovery controller coupled to a processor and a memory. The NF management and discovery controller is configured to send a discovery request to an NRF device to discover a NF instance of a specific type. In addition, the NF management and discovery controller is configured to receive a discovery response from the NRF device. The discovery response includes NF instance-specific data of multiple NF instances matching the requested type, and an indicator of a common data profile.

[0039] An embodiment of the present disclosure provides an NRF device, including a NF management and discovery controller coupled to a processor and a memory. The NF management and discovery controller is configured to receive a discovery request from an NF consumer to discover a specific type of NF instance, and identify the NF instance based on the discovery request. In addition, the NF management and discovery controller is configured to send a discovery response to the NF consumer. The discovery response includes NF instance specific data of multiple NF instances and a pointer to a configuration file containing common data of the multiple NF instances.

[0040] When considered in conjunction with the following description and the accompanying drawings, these and other aspects of the embodiments herein will be better appreciated and understood. However, it should be understood that the following description, although indicating at least one embodiment and many specific details thereof, is provided by way of illustration and not limitation. Without departing from the spirit of the embodiments herein, many changes and modifications may be made within the scope of the embodiments herein, and the embodiments herein include all of these modifications.

[0041] Before proceeding to the following detailed description, it may be helpful to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprising" and their derivatives are meant to include, but are not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean include, be included within, interconnected with, contain, be contained within, connect to or be connected with, be coupled to or be coupled with, be communicative with, cooperate with, interleave, juxtapose, be proximate to, be bound to or be bound with, have, have the property of, etc.; and the term "controller" means any device, system, or portion thereof that controls at least one operation, such device may be implemented in hardware, firmware, or software, or some combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0042] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or a portion thereof that are suitable for implementation in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disk (DVD) or any other type of memory. "Non-transitory" computer-readable media does not include wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store data and rewrite data later, such as rewritable optical disks or erasable memory devices.

[0043] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The embodiments disclosed herein are shown in the accompanying drawings, and the same reference numerals indicate corresponding parts in the various figures throughout the accompanying drawings. The embodiments of the present invention will be better understood from the following description with reference to the accompanying drawings, wherein:

[0045] Figure 1A shows a representation of example NF profile information in an NRF device for different NF instances and NF service instances according to the prior art;

[0046] Figure 1B shows a representation of example NF profile information in an NRF device for different NF instances and NF service instances according to the prior art;

[0047] Figure 2A A representation showing an example of NF profile registration in an NRF device using Nnrf_NFManagement service according to the prior art;

[0048] Figure 2B A representation showing an example of NF profile registration in an NRF device using Nnrf_NFManagement service according to the prior art;

[0049] Figure 3 A representation showing an example of NF configuration file update in an NRF device using Nnrf_NFManagement service according to the prior art;

[0050] Figure 4 shows a representation of an example of NF discovery from an NRF device using the Nnrf_NFDiscovery service by a NF Consumer according to the prior art;

[0051] Figure 5 A representation showing an example of NF profile change notification using Nnrf_NFManagement service to subscribing NF consumers according to the prior art;

[0052] Figure 6 shows an example resource structure of the Nnrf_NFManagement API according to an embodiment of the present disclosure;

[0053] Fig. 7A A representation showing an example of NF profile registration in an NRF device using Nnrf_NFManagement service according to an embodiment of the present disclosure is shown;

[0054] Figure 7BA representation showing an example of NF profile registration in an NRF device using Nnrf_NFManagement service according to an embodiment of the present disclosure is shown;

[0055] Figure 8 shows an example resource structure of the Nnrf_NFDiscovery API according to an embodiment of the present disclosure;

[0056] Fig. 9 A representation showing an example of NF discovery in NRF using Nnrf_NFDiscovery service according to an embodiment of the present disclosure is shown;

[0057] Fig.10 A representation showing an example of notifying a subscribing NF consumer of a NF profile change using the Nnrf_NFManagement service according to an embodiment of the present disclosure;

[0058] Fig.11 Various hardware components of an NRF device according to an embodiment of the present disclosure are shown;

[0059] Fig.12 illustrating various hardware components of a NF instance entity according to an embodiment of the present disclosure;

[0060] Fig.13 illustrating various hardware components of a NF consumer according to an embodiment of the present disclosure;

[0061] Fig.14 A flowchart of a method for performing NF management and discovery in a wireless network implemented by an NRF device according to an embodiment of the present disclosure is shown;

[0062] Fig.15 A flowchart of a method implemented by an NF instance entity for performing NF management and discovery in a wireless network according to an embodiment of the present disclosure is shown;

[0063] Fig.16 A flowchart of a method implemented by an NF consumer for performing NF management and discovery in a wireless network according to an embodiment of the present disclosure is shown; and

[0064] Fig.17 A flowchart of a method implemented by an NRF device for performing NF management and discovery in a wireless network according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0065] Discussed below Figures 1A to 17The various embodiments used to describe the principles of the present disclosure in this patent document are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0066] Before proceeding to the following detailed description, it may be helpful to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprising" and their derivatives are meant to include, but are not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean include, be included within, interconnected with, contain, be contained within, connect to or be connected with, be coupled to or be coupled with, be communicative with, cooperate with, interleave, juxtapose, be proximate to, be bound to or be bound with, have, have the property of, etc.; and the term "controller" means any device, system, or portion thereof that controls at least one operation, such device may be implemented in hardware, firmware, or software, or some combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0067] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or a portion thereof that are suitable for implementation in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disk (DVD) or any other type of memory. "Non-transitory" computer-readable media does not include wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store data and rewrite data later, such as rewritable optical disks or erasable memory devices.

[0068] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

[0069] The embodiments of this article and their various features and advantageous details are explained more fully with reference to the non-limiting embodiments shown in the drawings and described in detail in the following description. The description of known components and processing techniques is omitted so as not to unnecessarily obscure the embodiments of this article. The examples used herein are only intended to facilitate understanding of the manner in which the embodiments of this article can be practiced, and further enable those skilled in the art to practice the embodiments of this article. Therefore, the examples should not be interpreted as limiting the scope of the embodiments of this article.

[0070] Embodiments of the present invention implement a method for performing NF management and discovery in a wireless network. The method includes receiving, by an NRF device, a first registration request for registering common data in a separate configuration file from a first NF instance entity. In addition, the method includes receiving, by the NRF device, a second registration request for registering a NF instance configuration file from the first NF instance entity. The NF instance configuration file includes NF instance specific data and a pointer to a configuration file pointing to common data.

[0071] Referring now to the drawings, and more particularly to Figures 6 to 17 , wherein like reference numerals indicate corresponding features throughout the several views, at least one embodiment is shown.

[0072] This article mentions the following abbreviations:

[0073] a) NRF-network repository function;

[0074] b) NF-Network Function;

[0075] c)3GPP-3rd Generation Partnership Project;

[0076] d) NF-Type - Type of network function (e.g., AMF, SMF, NEF);

[0077] e) PLMN - Public Land Mobile Network; and

[0078] f) ID - identifier.

[0079] This article mentions the following references:

[0080] a) 3GPP TS29.510-Network Capability Repository Service;

[0081] b) 3GPP TS29.500-Technical implementation of service-based architecture;

[0082] c) 3GPP TS29.501 - Principles and guidelines for service definition;

[0083] d) 3GPP TS23.501 - System architecture of 5G systems; and

[0084] e)3GPP TS23.502-5G system procedures.

[0085] The 3rd Generation Partnership Project (3GPP) Release 15 introduced a service-based architecture for the 5G Core, which involves a collection of interconnected network functions (NFs), each of which can be connected via a network repository function (NRF) device (e.g., Figure 4 The NRF device 200) is discovered. The NRF device exposes the Nnrf_NFManagement service, which allows a network function (e.g., NF producer) to register or update its profile in the NRF device. The profile includes information about the NF services provided by the network function, its authorization policy (e.g., which other NFs are allowed to access them, what they are allowed to access, etc.), and other configuration / capability parameters. The NRF device also exposes the Nnrf_NFDiscovery service, which allows a network function (e.g., NF consumer (300)) to discover a network (e.g., 5G network) (e.g., Figure 4 1000), the services they provide, and other configuration / capability parameters. Figure 4 When the NF consumer 300) wishes to utilize the NF service provided by the NF producer, the NF consumer may use the NF service.

[0086] NF consumers can subscribe to notifications from NRF devices to know the operational status of the NF producers they discover. If the profile of the subscribed NF producer changes, the NRF device can send a notification to all subscribed NFs whenever the registered profile information of the NF producer changes. The notification can include at least one of the updated profile of the NF producer and the difference from the previous profile. Each network function can be deployed so that there are several network function instances within the NF set to provide distribution, redundancy, and scalability together as a set of NF instances. For example, if an NF instance fails, another NF instance in the set can take over and thus provide redundancy.

[0087] When multiple member NFs (instances) of a NF set register their profiles into the NRF device, a lot of redundant information may need to be registered because the NFs of the NF set have a lot of common configurations (such as configuration / capability parameters, etc.). Similarly, when a NF consumer discovers a specific type of NF producer instance, a lot of such redundant information may need to be provided in the discovery response. In the worst case, a NF subscribing to changes in NF profile data may be individually notified of the same changes for multiple NF instances.

[0088] Figure 1A and Figure 1BA representation of example NF profile information in an NRF device for different NF instances and NF service instances is shown.

[0089] refer to Figure 1A and Figure 1B , shows an example of multiple network function (NF) sets. Each NF set in the NF set can contain network function instances 1...n, where the configuration file of each NF instance consists of NF instance specific data, NF instance service data and NF instance common data. NF service instances within the NF instance can also be deployed in the service set. Therefore, Figure 1A and Figure 1B It is shown that the NF instance service data can be composed of multiple NF service sets, each NF service set contains multiple NF service instances.

[0090] Figure 2A and Figure 2B A representation showing an example of NF profile registration in an NRF device using the Nnrf_NFManagement service.

[0091] refer to Figure 2A and Figure 2B ,The profile of each NF service instance contains NF service instance specific data and NF service instance common data. Note that ",NF / NF service instance specific data" or "NF / NF service instance common data" do not refer to the already existing classification of NF / NF service profile data (in 3GPP specifications). Instead, they indicate that NF / NF service profile data can be divided into these categories, where specific data refers to profile parameters that are not common in a set, and common data refers to profile parameters that are common in a set.

[0092] In the current state of the art, when NF instances (e.g., NF instance entities) 100a, 100b, 100c, and 100d register their configuration files in the NRF device 200 using the Nnrf_NFManagement service, each NF instance 100a, 100b, 100c, and 100d in the NF set can register its complete configuration file in the NRF device (200). That is, if the NF set has n instances, each instance can register its configuration file, which contains NF instance specific data, NF instance service data, and NF instance common data. In addition, if each NF instance has multiple NF service instances belonging to the same NF service set, for each NF service instance, the NF configuration file can contain a complete NF service configuration file, which contains NF service instance common data and NF service instance specific data.

[0093] Figure 2A and Figure 2B An example of how the problem manifests itself during the registration of NF profiles to the NRF device 200 is shown. Consider that there are 4 NF instances 100a to 100d belonging to the same NF set, which register their profiles into the NRF device 200 by sending Nnrf_NFManagement_NFRegister requests separately at steps S201a, S201b, S201c, and S201d. Each request may contain some duplicate information (common data) across multiple NF instances 100a to 100d belonging to the same NF set, thereby increasing the size of the Hypertext Transfer Protocol (HTTP) payload and thus affecting network performance. In addition, as Figure 2B As shown in block A of FIG. 1 , the NRF device 200 eventually has duplicate information in its database.

[0094] Figure 3 A representation of an example of NF configuration file update in an NRF device using Nnrf_NFManagement service is shown.

[0095] If the NF configuration files of these NF instances 100a to 100d are changed later, and even if the change happens to be in the "common data", each of these NF instances 100a to 100d can end up updating their configuration files in the NRF device 200 by sending a Nnrf_NFManagement_NFUpdate request to the NRF device 200 (e.g. Figure 3 It should be noted that if the changes are in "specific data", these can be updated separately in any way and are not the purpose of this disclosure.

[0096] Figure 4 A representation of an example of NF discovery from an NRF device using the Nnrf_NFDiscovery service by a NF Consumer is shown.

[0097] refer to Figure 4, consider an NF consumer 300 that wants to discover NF instances 100a to 100d of a specific type (e.g., Access and Mobility Management Function (AMF) entity, Session Management Function (SMF) entity, etc.) by sending a Nnrf_NFDiscovery_NFDiscover request to the NRF device 200 (e.g., step S401). The NRF device 200 may determine its database and provide all these 4 profiles to the NF consumer 300 in the Nnrf_NFDiscovery_NFDiscover response (e.g., step S402). The payload body of the response may contain duplicate information (common data) in the profile of each NF, and thus may not only increase the size of the response, but the NF consumer 300 may end up storing a large amount of information in its cache and / or database (e.g., Figure 4 B).

[0098] Figure 5 It is also shown how including common data in the configuration file of each NF instance of a NF set leads to increased signaling during configuration file change notifications.

[0099] refer to Figure 5 , the NF consumer 300 may need to track the configuration file changes of the NF instance entities 100a to 100d. Therefore, at steps S501a, S501b, S501c and S501d, the NF consumer 300 can use the Nnrf_NFManagement_NFStatusSubscribe service operation to subscribe to the NRF device 200 to receive data change notifications. The subscription request is completed for each NF instance 100a to 100d. At step S502, when the NRF device 200 may later detect changes in the configuration files of the NF instances 100a-100d (for example, due to the NF executing such as Figure 3 300). In the example of Nnrf_NFManagement_NFUpdate service operation shown in FIG. 502 , the NRF device 200 may send a notification to the NF consumer 300. Even if the change is in the common data, the change may eventually send 4 notifications to the NF consumer 300 at steps 503a, 503b, 503c, and 503d to update the configuration files of all NF instances 100a to 100d with the same data. It should be noted that if the change is in the "specific data", these may be updated separately in any way and are not the purpose of this disclosure.

[0100] Therefore, existing implementations of the NRF device 200 and NFs result in duplicate storage of information in the NRF device 200 and the NF consumer 300, and increased signaling during registration, update, and notification service operations; thus, reducing the overall efficiency of the wireless network 1000.

[0101] There are other aspects of NF registration, discovery, subscription and notification operations that are important but do not affect the embodiments in this document. Therefore, for clarity of understanding, these are not explicitly shown here.

[0102] It would therefore be desirable to address the above-mentioned or other disadvantages or at least provide a useful alternative.

[0103] The provided method can be used to perform network function management and discovery in a 5G network when network function instances are deployed in a NF set. The embodiments of this document disclose how member NF instances of a NF set can register their profiles into an NRF device without having to copy the common profile parameter information into the profile of each NF instance of the NF set. The embodiments of this document disclose how an NRF device provides a profile of an NF set to an NF consumer, the profile of the NF set containing the common profile parameters of the NF instances belonging to the NF set. The embodiments of this document disclose how it is not necessary to notify the NF consumer via multiple notifications due to profile changes of member NF instances when data changes are in a common parameter set. The embodiments improve the efficiency of the system by proposing alternative implementations in the NRF, NF consumer, and NF producer.

[0104] In an embodiment, it is provided that in the case where NF instances belonging to a NF set register their profiles into an NRF device using the Nnrf_NFManagement service, they first register the "public data" in a separate profile and use an existing or new identifier that is unique at least within a public land mobile network (PLMN) to identify the "public data". The separate profile can be an "NF set" profile, where the NF set can be identified using an existing NF set ID or a new identifier defined in 3GPP TS23.003. Then, the individual NF profiles of the NF instance are registered into the NRF device without "public data". Instead, the individual NF profiles only contain an indication that the information contained in the NF set profile (registered separately and identified using the NF set identifier) ​​is also applicable to the profile of the NF instance.

[0105] Figure 6 FIG. 1 shows an example resource structure of the Nnrf_NFManagement application programming interface (API) according to an embodiment of the present disclosure. Figure 6 The resource structure 600 defined in 3GPP TS 29.510 is extended with a new branch for NF set resource sets shown by the dashed outline in FIG.

[0106] therefore, Fig. 7AIt is shown how this mechanism helps improve the information of multiple NF instances of the same NF set stored in the NRF device 200. To illustrate the solution, assume that 4 NF instances 100a to 100d belong to NF set = A.

[0107] In step S701, when the first NF instance of the NF set (in this illustration, the first NF instance) appears, the first NF instance may first check with the NRF device 200 whether the device already has a configuration file of NF set = A by sending a request to the NRF device 200. This can be done by using an existing or new service operation of the Nnrf_NFManagement service or by defining a new service. For example, Figure 6 As depicted, an HTTP GET service operation may be defined on the / NFSet resource.

[0108] In step S702, the NRF device 200 may respond that the NRF device 200 does not have the configuration file of NF Set = A. For example, the NRF device 200 may send an HTTP error "404 Not Found" to indicate this.

[0109] In step S703, the first NF instance 100a may register the NF set = A profile with the NRF device 200, which contains common data that may have been pre-configured by Operation, Administration and Maintenance (OA&M). This may be done by using an existing or new service operation of the Nnrf_NFManagement service or by defining a new service. For example, an HTTP PUT / POST method may be defined on the / nf-sets or / nf-sets / {nfsetId} resource, such as Figure 6 Depicted.

[0110] In step S704, the first NF instance 100a may then register the NF instance profile in the NRF device (200) using the Nnrf_NFManagement_NFRegister service operation; containing NF instance specific data and NF instance service data. NF instance common data is not included, but only a pointer to the profile of NF set = A is indicated in the NF instance profile. The pointer to the profile of NF set = A may be a resource URI of the / nf-sets / {nfsetId} resource. In an embodiment, if there are multiple NF service instances belonging to a common NF service set, the NF service common data may be registered as part of a separate data structure so as not to repeat the common data multiple times.

[0111] In steps S705a, S705b and S705c, NF instances 100b to 100d may appear and they check with the NRF device (200) whether the device already has a configuration file of NF Set = A (same as step S701).

[0112] In steps S706a, S706b and S706c, since the first NF instance 100a has registered the profile of NF set = A in step S703, the NRF device 200 can respond that the device has the profile and can optionally respond with the profile information of NF set = A.

[0113] At this point in time, optionally, if any NF in the NF (second instance - fourth instance) finds that the configuration file of NF set = A in the NRF device 200 needs to be updated, the device can use the mechanism defined in step S703 to update the configuration file of NF set = A.

[0114] In steps S707a, S707b and S707c), the second, third and fourth NF instances 100b, 100c and 100d can now register their NF instance profiles in the NRF device 200 using the Nnrf_NFManagement_NFRegister service operation; containing NF instance specific data and NF instance service data. NF instance common data is not included, but only a pointer to the profile of NF set = A is indicated in the NF instance profile. The pointer to the profile of NF set = A can be the resource URI of the / nf-sets / {nfsetId} resource. In an embodiment of the present invention, if there are multiple NF service instances belonging to a common NF service set, the NF service common data can be registered as part of a separate data structure so as not to repeat the common data multiple times.

[0115] Therefore, if Figure 7B As shown in box C of , the information stored in the NRF device 200 is neither copied in the signaling from the NF instances 100a to 100d nor in the storage in the NRF device 200.

[0116] In an alternative implementation of step S701 (and steps S705a, S705b, and S705c), instead of each NF instance 100a to 100d querying the NRF device 200 to know whether a profile of NF set = A already exists in the NRF device 200, each NF instance can be locally configured with a profile identifier and an associated profile that is unique at least within the PLMN. Then, when each NF instance 100a to 100d registers or updates its profile in the NRF device 200 using the Nnrf_NFManagement_NFRegister service operation, the device includes NF instance specific data and NF instance service data in the HTTP payload body, but does not include NF instance common data. The NF instance common data is part of the locally configured NF set profile and therefore only includes a pointer to the NF set profile identifier. Upon receiving the message, if the NRF device 200 finds that the device does not have the indicated profile of the NF set, the device sends an indication in response to the Nnrf_NFManagement_NFRegister request, requiring the NF instance to register or update the profile of the NF set. Based on the presence of such indication in the response, the NF instances 100a to 100d may register or update the profile of the NF set into the NRF device 200. However, if the NRF device 200 finds that the device already has the indicated profile of the NF set, the device does not send any such indication in response to the Nnrf_NFManagement_NFRegister request, and thus the NF instances do not need to register or update the profile of the NF set = A into the NRF device 200 again.

[0117] Furthermore, if, for example, the first NF instance 100a is configured with a profile of NF set =A <profile1>, and the second NF instance 100b is configured with a configuration file of NF set =A= <profile2>, then each of the first NF instance 100a and the second NF instance 100b can update the NRF device 200 with a separate configuration file of NF set = A.

[0118] Figure 8 and Fig. 9 shows how this mechanism of defining NF Set profiles can help improve Figure 4 Similar to the problem described in Figure 6 , Figure 8 It is proposed to extend the resource structure 800 of the Nnrf_NFDiscovery API with a new branch of NF Sets.

[0119] Therefore, when the NF consumer 300 sends a request to the NRF device 200 to discover a specific type of network function (e.g., AMF entity, SMF entity, etc.), as shown in FIG. Fig. 9 As shown, the following sequence of events can occur.

[0120] In step S901, the NF consumer 300 may send an Nnrf_NFDiscovery_NFDiscover request to the NRF device 200 to discover a specific type of NF instance.

[0121] In step S902, the NRF device 200 may find 4 NF instances (e.g., NF instances 100a-100d) belonging to a common NF set = A, and return in the Nnrf_NFDiscovery_NFDiscover response, NF instance specific data and NF instance service data of the 4 NF instances (100a-100d). The NF instance common data is not included, but only a pointer to the configuration file of NF set = A is indicated in the configuration file information of the NF instance. The pointer to the configuration file of NF set = A may be a URI of a resource of the configuration file belonging to NF set = A.

[0122] In step S903, upon receiving the response from the NRF device 200, the NF consumer 300 may check whether the device already has a configuration file of NF set = A. If not, the NF consumer 300 may send a request to the NRF device 200 to provide the configuration file of NF set = A. This may be done by using an existing or new service operation of the Nnrf_NFDiscovery service or by defining a new service. For example, a service operation based on the HTTP GET method may be performed in a manner such as Figure 8 Defined on the / NF set resources provided in.

[0123] In step S904, the NRF device 200 may respond using the configuration file of NF set=A.

[0124] Therefore, the payload size of the HTTP response to the discovery request is reduced, and the NF consumer 300 and / or the NRF device 200 does not need to cache duplicate information (such as Fig. 9 as shown in box D).

[0125] The solution provided in Figure 7 also helps to solve Figure 5 The problem described in Fig.10 As shown, since the common data is now stored in a separate NF set configuration file, the NF consumer 300 can subscribe to data change notifications for changes in the configuration file of, for example, NF set = A. Whenever the common data of the configuration files of the various NF instances change, they need to update the configuration file of NF set = A in the NRF device 200. This can result in a single notification generated to the NF consumer 300 (e.g., step S1004).

[0126] refer to Fig.10 , at steps S1001a, S1001b, S1001c and S1001d, the NF consumer 300 may use the first, second, third and fourth Nnrf_NFManagement_NFStatusSubscribe service operations to subscribe to the NRF device 200 to receive data change notifications. The subscription request is completed for each NF instance 100a to 100d. At step S1002, the NF consumer 300 may subscribe to data change notifications, such as changes to the configuration file of NF set = A, through Nnrf_NFManagement_NFStatusSubscribe NF set A. At step S1003, the NRF device 200 may detect, for example, changes in the configuration file of NF set = A due to the NF executing Figure 3 The configuration files of the NF instances 100a-100d may be changed due to the Nnrf_NFManagement_NFUpdate service operation etc. At step S1004, the NRF device 200 may send a notification (eg, Nnrf_NFManagement_NFStatusNotify NF Set A) to the NF consumer 300.

[0127] In the case where common data is registered separately in the NRF device 200 using, for example, an NF set configuration file, a new problem emerges: when the common data changes, which member NF instance can update the NF set configuration file into the NRF device 200? For the same change as an unnecessary behavior, the NF instances 100a to 100d may attempt to update the NF set configuration file at the same time. In order to solve this problem, in an embodiment, a member NF instance is provided to select a master NF instance responsible for updating the NF set configuration file in the NRF device 200 when the common configuration file parameters change. The selection of the master instance can be determined, for example, based on the priority configuration of the NF instance, whereby the highest priority NF instance becomes the master instance based on the configuration, etc. If the highest priority NF instance fails, the next highest priority NF instance plays the role of the master instance. Therefore, unnecessary and repeated updates to the NRF device (200) can be avoided.

[0128] Fig.11 Various hardware components of an NRF device (200) according to an embodiment of the present disclosure are shown. In an embodiment, the NRF device 200 may include at least one of a processor 210, a communicator 220, a memory 230, or a NF management and discovery controller 240. The processor 210 may be coupled with the communicator 220, the memory 230, and the NF management and discovery controller 240. In an embodiment, the NF management and discovery controller 240 may be included in the processor 210 or integrated with the processor 210.

[0129] The NF management and discovery controller 240 may receive a first registration request for registering common data in a separate configuration file from the first NF instance entity 100a. In an embodiment, the common data refers to configuration file information common to multiple NF instances. In another embodiment, the common data refers to data common to NF instances belonging to a NF set.

[0130] In an embodiment, the NF management and discovery controller 240 may receive a first determination request to determine whether there is an NF set profile of the first NF set in the NRF device 200. Based on the determination request, the NF management and discovery controller 240 may send a first response indicating that there is no NF set profile of the first NF set to the NRF device 200. In addition, the NF management and discovery controller 240 may receive a first registration request to register public data in a separate configuration file into the NRF device 200.

[0131] In an embodiment, the NF management and discovery controller 240 may receive a second registration request to register a NF instance profile from the first NF instance entity 100a. The NF instance profile includes NF instance specific data and a pointer to a profile of common data. In an embodiment, the NF instance specific data refers to profile information specific to the NF instance. In an embodiment, the NF instance belongs to a NF set. In an embodiment, the second registration request to register a NF instance profile is received using Nnrf_NFManagement_NFRegister.

[0132] In an embodiment, the NF management and discovery controller 240 may receive a registration request from the first NF instance entity 100a to register the NF instance profile with the NRF device 200. In addition, the NF management and discovery controller 240 may send a first response indicating that there is no profile with common data to the NRF device 200. In addition, the NF management and discovery controller 240 may receive a registration request to register common data in a separate profile into the NRF device 200.

[0133] In an embodiment, the NF management and discovery controller 240 may receive a discovery request to discover a NF instance of a specific type from the NF consumer 300. Based on the discovery request, the NF management and discovery controller 240 may identify the NF instance. In addition, the NF management and discovery controller 240 may send a discovery response to the NF consumer 300. The discovery response may include NF instance specific data of multiple NF instances, and a pointer to a configuration file of a NF set configuration file. A pointer to the configuration file of the NF set configuration file may be included in the discovery response instead of common data.

[0134] In an embodiment, the NF management and discovery controller 240 may receive a discovery request for a shared NF set profile from the NF consumer 300. The NF consumer 300 may determine that the NF set profile is not available in the NF consumer 300. Based on the discovery request, the NF management and discovery controller 240 may send the NF set profile to the NF consumer 300.

[0135] In an embodiment, the NF management and discovery controller 240 may receive a subscription request associated with a data change notification for a change in a NF set configuration file. In addition, the NF management and discovery controller 240 may determine a change in public data associated with the NF set configuration file. In addition, the NF management and discovery controller 240 may send a message indicating a change in public data associated with the NF set configuration file to the NF consumer 300.

[0136] The NF management and discovery controller 240 may be implemented by analog and / or digital circuits, such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc., and may optionally be driven by firmware.

[0137] In an embodiment, the processor 210 may be configured to execute instructions stored in the memory 230 and perform various processes. The communicator 220 may be configured to communicate internally between internal hardware components and communicate with external devices via one or more networks. The memory 230 may also store instructions to be executed by the processor 210. The memory 230 may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or an electrically programmable memory (EPROM) or an electrically erasable programmable (EEPROM) memory. In addition, in some examples, the memory (230) may be considered to be a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier or propagation signal. However, the term "non-transitory" should not be interpreted as the memory 230 being non-removable. In some instances, a non-transitory storage medium may store data that may change over time (e.g., in a random access memory (RAM) or a cache memory).

[0138] although Fig.11 Various hardware components of the NRF device 200 are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, the NRF device 200 may include fewer or more components. In addition, the labels or names of the components are only for illustrative purposes and do not limit the scope of the present disclosure. One or more components can be combined together to perform the same or substantially similar functions in the NRF device 200.

[0139] Fig.12 Various hardware components of the NF instance entity 100 according to an embodiment of the present disclosure are shown. In an embodiment, the NF instance entity 100 may include a processor 110, a communicator 120, a memory 130, or a NF management and discovery controller 140. The processor 110 may be coupled with the communicator 120, the memory 130, and the NF management and discovery controller 140. In an embodiment, the NF management and discovery controller 140 may be included in the processor 110, or integrated with the processor 110.

[0140] The NF management and discovery controller 140 may be configured to classify the NF instance profile data into common data and specific data. The common data is identified and registered as an "NF Set" profile in the NRF device 200. In addition, the NF management and discovery controller 140 may be configured to send a first registration request to register the common data in a separate profile into the NRF device 200.

[0141] In an embodiment, the NF management and discovery controller 140 may send a first determination request to determine whether the NRF device 200 has an NF set profile of the first NF set. Based on the determination request, the NF management and discovery controller 140 may receive a first response indicating that the NRF device 200 does not have an NF set profile of the first NF set. In addition, the NF management and discovery controller 140 may send a first registration request to register public data in a separate profile into the NRF device (200).

[0142] The NF management and discovery controller 140 may send a second registration request to register the NF instance profile with the NRF device 200. The NF instance profile may include NF instance specific data and a pointer to a profile of common data.

[0143] In an embodiment, the NF management and discovery controller 140 may send a registration request to register a NF instance profile with the NRF device 200. The NF instance profile may include NF instance specific data and a pointer to a profile of common data. In addition, the NF management and discovery controller 140 may receive a first response indicating that there is no profile with common data with the NRF device 200. In addition, the NF management and discovery controller 140 may send a second registration request to register the common data in a separate profile into the NRF device 200.

[0144] The NF management and discovery controller 140 may be implemented by analog and / or digital circuits, such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc., and may optionally be driven by firmware.

[0145] The processor 110 may be configured to execute instructions stored in the memory 130 and perform various processes. The communicator 120 may be configured to communicate internally between internal hardware components and communicate with external devices via one or more networks. The memory 130 may also store instructions to be executed by the processor 110. The memory 130 may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or an electrically programmable memory (EPROM) or an electrically erasable programmable (EEPROM) memory. In addition, in some examples, the memory 130 may be considered to be a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier or propagation signal. However, the term "non-transitory" should not be interpreted as the memory 130 being non-removable. In some instances, a non-transitory storage medium may store data that may change over time (e.g., in a random access memory (RAM) or a cache memory).

[0146] although Fig.12 Various hardware components of the NF instance entity 100 are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, the NF instance entity 100 may include fewer or more components. In addition, the labels or names of the components are only for illustrative purposes and do not limit the scope of the present disclosure. One or more components can be combined together to perform the same or substantially similar functions in the NF instance entity 100.

[0147] Fig.13 Various hardware components of the NF consumer 300 according to an embodiment of the present disclosure are shown. In an embodiment, the NF consumer 300 may include at least one of a processor 310, a communicator 320, a memory 330, or a NF management and discovery controller 340. The processor 310 may be coupled with the communicator 320, the memory 330, and the NF management and discovery controller 340. In an embodiment, the NF management and discovery controller 340 may be included in the processor 310 or integrated with the processor 310.

[0148] The NF management and discovery controller 340 may send a discovery request to the NRF device 200 to discover a NF instance of a specific type. The NRF device 200 may identify the NF instance based on the discovery request, and the NF instance is associated with the NF instance common data. In addition, the NF management and discovery controller 340 may receive a discovery response from the NRF device 200. The discovery response may include NF instance specific data of multiple NF instances matching the requested type, and an indicator of a common data profile. An indicator of the NF set profile instead of common data may be included in the discovery response.

[0149] In an embodiment, the NF management and discovery controller 340 may send a request to discover the NF set profile to the NRF device 200 when determining that the NF set profile is not available in the NF consumer 300. Based on the discovery request, the NF management and discovery controller 340 receives the NF set profile from the NRF device 200.

[0150] In an embodiment, the NF Management and Discovery Controller 340 sends a subscription request associated with a data change notification for a change in the NF Set Profile to the NRF Device 200. Upon determining a change in the public data associated with the NF Set Profile at the NRF Device 200, the NF Management and Discovery Controller 340 receives a message indicating the change in the public data associated with the NF Set Profile from the NRF Device 200.

[0151] The NF management and discovery controller 340 may be implemented by analog and / or digital circuits, such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc., and may optionally be driven by firmware.

[0152] In an embodiment, the processor 310 may be configured to execute instructions stored in the memory 330 and perform various processes. The communicator 320 may be configured to communicate internally between internal hardware components and communicate with external devices via one or more networks. The memory 330 may also store instructions to be executed by the processor 310. The memory 330 may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or an electrically programmable memory (EPROM) or an electrically erasable programmable (EEPROM) memory. In addition, in some examples, the memory 330 may be considered to be a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier or propagation signal. However, the term "non-transitory" should not be interpreted as the memory 330 being non-removable. In some instances, a non-transitory storage medium may store data that may change over time (e.g., in a random access memory (RAM) or a cache memory).

[0153] although Fig.13 Various hardware components of the NF consumer 300 are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, the NF consumer 300 may include fewer or more components. In addition, the labels or names of the components are for illustrative purposes only and do not limit the scope of the present disclosure. One or more components may be combined together to perform the same or substantially similar functions in the NF consumer 300.

[0154] Fig.14 A flowchart 1400 of a method for performing NF management and discovery in a wireless network (e.g., 5G network 1000) implemented by the NRF device 200 according to an embodiment of the present disclosure is shown. Steps 1402 and 1404 may be processed by the NF management and discovery controller 240.

[0155] At step 1402, the method may include receiving a first registration request to register common data in a separate configuration file from a first NF instance entity. At step 1404, the method may include receiving a second registration request to register a NF instance configuration file from the first NF instance entity 100. The NF instance configuration file includes NF instance specific data and a pointer to the configuration file of the common data.

[0156] Fig.15 A flowchart 1500 of a method implemented by the NF instance entity 100 for performing NF management and discovery in a wireless network 1000 according to an embodiment of the present disclosure is shown. Steps 1502, 1504, and 1506 may be processed by the NF management and discovery controller 140.

[0157] At step 1502, the method may include classifying NF instance profile data into common data and specific data. At step 1504, the method may include sending a first registration request to register the common data in a separate profile into the NRF device 200. At step 1506, the method may include sending a second registration request to register the NF instance profile with the NRF device 200. The NF instance profile includes the NF instance specific data and a pointer to the profile of the common data.

[0158] Fig.16 A flowchart 1600 of a method implemented by the NF consumer 300 for performing NF management and discovery in the wireless network 1000 according to an embodiment of the present disclosure is shown. Steps 1602 and 1604 may be processed by the NF management and discovery controller 340.

[0159] At step 1602, the method may include sending a discovery request to discover NF instances of a specific type to the NRF device 200. At step 1604, the method may include receiving a discovery response from the NRF device 200. The discovery response includes NF instance specific data of a plurality of NF instances matching the requested type, and an indicator of a common data profile.

[0160] Fig.17 A flowchart 1700 of a method implemented by the NRF device 200 for performing NF management and discovery in the wireless network 1000 according to an embodiment of the present disclosure is shown. Steps 1702, 1704, and 1706 may be processed by the NF management and discovery controller 240.

[0161] At step 1702, the method may include receiving a discovery request to discover NF instances of a specific type from the NF consumer 300. At step 1704, the method may include identifying the NF instance based on the discovery request. At step 1706, the method may include sending a discovery response to the NF consumer 300. The discovery response includes NF instance specific data of the plurality of NF instances and a pointer to a configuration file containing common data of the plurality of NF instances.

[0162] The various actions, actions, blocks, steps, etc. in the flow charts (e.g., 1400, 1500, 1600, and 1700) may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some of the actions, actions, blocks, steps, etc. may be omitted, added, modified, skipped, etc. without departing from the scope of the present disclosure.

[0163] The embodiments disclosed herein may be implemented by at least one software program running on at least one hardware device and performing network management functions to control an element. The element may be at least one of a hardware device or a combination of a hardware device and a software module.

[0164] The foregoing description of specific embodiments will so fully reveal the general nature of the embodiments herein that others can easily modify and / or adapt these specific embodiments for various applications by applying current knowledge without departing from the general concepts, and therefore, these adaptations and modifications should and are intended to be understood to be within the meaning and scope of equivalents of the disclosed embodiments. It should be understood that the wording or terminology employed herein is for descriptive and not limiting purposes. Therefore, although the embodiments herein have been described according to at least one embodiment, those skilled in the art will recognize that the embodiments herein can be practiced by modification within the scope of the embodiments as described herein.

[0165] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. The present disclosure is intended to encompass such changes and modifications as fall within the scope of the appended claims.

Claims

1. A method for performing network function (NF) management and discovery in a wireless network, the method comprising: Receiving, by a Network Repository Function (NRF) device from a first NF instance entity, a first registration request for registering common data in a separate configuration file; as well as A second registration request for registering a NF instance profile is received by the NRF device from the first NF instance entity, wherein the NF instance profile includes NF instance specific data and a pointer to a profile of the common data.

2. The method according to claim 1, wherein: The common data refers to the configuration file information common to multiple NF instances. The NF instance specific data refers to configuration file information specific to the NF instance among the multiple NF instances. Wherein, the NF instance belongs to a NF set, The common data refers to the common data of multiple NF instances belonging to the NF set, and The second registration request for registering the NF instance profile is received using Nnrf_NFManagement_NFRegister.

3. The method according to claim 1, wherein: Receiving the first registration request to register the public data in the separate configuration file includes: The NRF device receives a determination request to determine whether there is an NF set configuration file of a first NF set with the NRF device; The NRF device sends a first response indicating that the NF set configuration file of the first NF set does not exist with the NRF device based on the determination request; and The NRF device receives the first registration request for registering the public data in the separate configuration file in the NRF device.

4. The method according to claim 1, wherein: Receiving the second registration request for registering the NF instance profile includes: receiving, from the first NF instance entity, a registration request for registering the NF instance profile with the NRF device; The NRF device sends a first response indicating that the configuration file having common data with the NRF device does not exist; and A registration request for registering the public data in the separate configuration file into the NRF device is received by the NRF device.

5. The method according to claim 1, further comprising: receiving, by a network repository function (NRF) device, a discovery request from a NF consumer to discover NF instances of a specific type; The NRF device identifies the NF instance based on the discovery request; as well as A discovery response is sent by the NRF device to the NF consumer, wherein the discovery response includes NF instance specific data of multiple NF instances and a pointer to a configuration file containing common data of the NF instances.

6. The method according to claim 5, wherein: A pointer to the configuration file of the NF Set Configuration File is included in the discovery response instead of the common data.

7. The method according to claim 5, further comprising: In a case where the NF consumer determines that the NF set profile is not available in the NF consumer, receiving, by the NRF device, a discovery request for a shared NF set profile from the NF consumer; as well as The NRF device sends the NF set configuration file to the NF consumer based on the discovery request.

8. The method according to claim 5, further comprising: receiving, by the NRF device, a subscription request associated with a data change notification for a change to a NF set configuration file; determining, by the NRF device, a change in the common data associated with the NF Set configuration file; as well as A message indicating a change of the common data associated with the NF Set Profile is sent by the NRF device to the NF Consumer.

9. A method for performing network function (NF) management and discovery in a wireless network, the method comprising: Classifying the NF instance profile data into common data and specific data by the first NF instance entity; The first NF instance entity sends a first registration request to register the public data in a separate configuration file into a network repository function (NRF) device; as well as A second registration request is sent by the first NF instance entity to register a NF instance profile with the NRF device, wherein the NF instance profile includes NF instance specific data and a pointer to a profile of the common data.

10. The method according to claim 9, wherein: The common data refers to the configuration file information common to multiple NF instances. The specific data refers to configuration file information specific to the NF instance. The multiple NF instances belong to a NF set. The common data refers to the common data of multiple NF instances belonging to the NF set, and Wherein, the common data is identified and registered as a NF set profile in the NRF device.

11. The method according to claim 9, wherein: Sending the first registration request to register the public data in the separate configuration file to the NRF device includes: The first NF instance entity sends a determination request to determine whether there is an NF set configuration file of the first NF set with the NRF device; Receiving, by the first NF instance entity based on the determination request, a first response indicating that an NF set configuration file of the first NF set does not exist with the NRF device; and The first registration request is sent by the NF instance entity to register the common data in the separate configuration file into the NRF device.

12. The method according to claim 9, wherein: Sending the second registration request to register the NF instance profile with the NRF device includes: The first NF instance entity sends a registration request to register a NF instance profile with the NRF device, wherein the NF instance profile includes a pointer to a profile of NF instance specific data and the common data; Receiving, by the first NF instance entity, a first response indicating that the configuration file having common data with the NRF device does not exist; and The NF instance entity sends a second registration request to register the public data in the separate configuration file into the NRF device.

13. A method for optimizing network function (NF) management and discovery in a wireless network, the method comprising: A discovery request is sent by the NF consumer to the Network Repository Function (NRF) device to discover NF instances of a specific type; as well as A discovery response is received by the NF consumer from the NRF device, wherein the discovery response includes NF instance specific data of multiple NF instances matching the requested type and an indicator of a common data profile.

14. A network repository function (NRF) device comprising: Memory; as well as A controller is coupled to the memory, the controller being configured to: receiving a first registration request from a first NF instance entity to register common data in a separate configuration file, and A second registration request for registering a NF instance profile is received from the first NF instance entity, wherein the NF instance profile includes NF instance specific data and a pointer to a profile of the common data.

15. The NRF device according to claim 14, wherein: The controller is also configured to: Receive a discovery request from a NF consumer to discover NF instances of a specific type, identifying the NF instance based on the discovery request, and A discovery response is sent to the NF consumer, wherein the discovery response includes NF instance specific data of multiple NF instances and a pointer to a configuration file containing common data of the NF instances.

Images