Methods and apparatus for managing RAN nodes in a communication network

[0001] This application is a continuation application, claiming priority under § 365(c), of an International application No. PCT/KR2022/004862, filed on Apr. 5, 2022, which is based on and claims the benefit of an Indian provisional patent application number 202141016784, filed on Apr. 9, 2021, in the Indian Patent Office, and of an Indian Complete patent application number 202141016784, filed on Oct. 8, 2021, in the Indian Patent Office, the disclosure of each of which is incorporated by reference herein in its entirety.

[0002] The disclosure relates to telecommunication. More particularly, the disclosure relates to methods and apparatus for managing radio access network (RAN) nodes in a communication network.

[0003] To meet the demand for wireless data traffic having increased since deployment of 4^th generation (4G) communication systems, efforts have been made to develop an improved 5^th generation (5G) or pre-5G communication system. Therefore, the 5G or pre-5G communication system is also called a ‘Beyond 4G Network’ or a ‘Post long-term evolution (LTE) System’.

[0004] The 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60 GHz bands, so as to accomplish higher data rates. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), Full Dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are discussed in 5G communication systems.

[0005] In addition, in 5G communication systems, development for system network improvement is under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancellation and the like.

[0006] In the 5G system, hybrid frequency shift keying (FSK) and quadrature amplitude modulation (QAM) (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as an advanced access technology have been developed.

[0007] Access and mobility management function (AMF) manages connection and mobility management for user equipment (UEs) in communication networks. In a cloud native design principle, an AMF region comprises multiple sets of AMFs to provide high level of redundancy. This design of AMF region is generally termed as geo-redundancy AMF region. The AMFs in each AMF set are configured with radio access network (RAN) nodes to process context of the UEs. Currently, the AMF is manually configured using identifier of RAN nodes and relative AMF capacity (RAC) value. The RAC value helps in load balancing traffic across the multiple AMFs. The configuration of the RAN nodes includes mapping the identifier of RAN nodes and RAC values for each AMFs. This configuration is installed in the corresponding AMF before the RAN node contacts the AMF for processing context of the UEs. Generally, this manual configuration is a lengthy list and is erroneous. Further, the RAN nodes can change their locality (cell Identity (ID)s/tracking areas) at any point of time. All the AMFs have to be reconfigured, when a RAN node is added or removed, thus leading multiple public land mobile network (PLMN) flexibility to be compromised. It is difficult for each PLMN to enable or disable the AMFs independently.

[0008] The AMFs in an AMF set are interchangeable. i.e., any AMF can handle context of a UE that belongs to the AMF set. This ensures that there is no single point of failure when an AMF fails or when the AMF is removed. The AMF failure or removal is detected via network repository function (NRF) heartbeat mechanism. A NRF server receives packets from the AMFs indicating that the AMFs are in operating condition. The failure or removal of the AMFs is detected when the NRF server does not receive the packets. Hence, the NRF server detects the failure or removal of the AMFs. However, the RAN nodes do not have access to the NRF server, in the existing systems. The RAN nodes detect failure of the AMFs by sending messages to the AMFs and waiting for timeout for all retry attempts. This is a time-consuming process. Further, the RAN nodes perform the same cycle for all the UEs connected via the RAN node. In some existing systems, failure, removal, or addition of the AMFs is notified via operations, administration and maintenance (OAM). However, when the AMF and the RAN node belongs to different operator with different OAM domain, coordination between the operators to manage the RAN nodes on failure, removal, or addition of the AMFs is difficult. Hence, there is a need to overcome one or more limitations of the above-described systems to enhance the geo-redundancy AMF region.

[0009] The above information is presented as background information only to assist with an understanding of the disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the disclosure.

[0010] Aspects of the disclosure are to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide a method and an Access and mobility management function (AMF) in a communication network.

[0011] Additional aspects will be set forth in part in the description which follows and, in part, will be apparent from the description, or may be learned by practice of the presented embodiments.

[0012] In accordance with an aspect of the disclosure, a method for managing radio access network (RAN) nodes in a communication network is provided. The method is performed by an access and mobility management function (AMF) from one or more AMFs of an AMF set. The method includes receiving a tracking area identity (TAI) from each of one or more RAN nodes added to the communication network. The TAI indicates a locality of each of the one or more RAN nodes. Further, the method comprises determining whether the locality of each of the one or more RAN nodes corresponds to one of, one or more primary serving localities of the AMF and one or more secondary serving localities of the AMF, based on a pre-stored TAI list. Furthermore, the method comprises identifying a relative AMF capacity (RAC) value for each of the one or more RAN nodes. Thereafter, the method comprises transmitting respective RAC value to each of the one or more RAN nodes, for configuring each of the one or more RAN nodes with the AMF.

[0013] In accordance with another aspect of the disclosure, a method for notifying status of access and mobility management functions (AMFs) in a communication network is provided. The method is performed by an AMF from one or more AMFs of an AMF set. The method includes transmitting a request to a network repository function (NRF) server, for status of other AMFs in the AMF set. The status may be one of a pre-defined status indicating failure/removal of the AMF in the AMF set or addition of an AMF to the AMF set. The request comprises an identifier of the AMF set. Further, the method comprises receiving a notification indicating the status of the other AMFs in the AMF set, from the NRF server, in response to the request. Thereafter, the method comprises notifying the status of at least one AMF from the other AMFs in the AMF set to one or more radio access network (RAN) nodes associated with the at least one AMF, when the status of the at least one AMF is one of a pre-defined status.

[0014] In accordance with another aspect of the disclosure, an access and mobility management function (AMF) for managing radio access network (RAN) nodes a communication network is provided. The AMF from one or more AMFs of an AMF set includes a processor and a memory. The processor is configured to receive a tracking area identity (TAI) from each of one or more RAN nodes added to the communication network. The TAI indicates a locality of each of the one or more RAN nodes. Further, the processor is configured to determine whether the locality of each of the one or more RAN nodes corresponds to one of, one or more primary serving localities of the AMF and one or more secondary serving localities of the AMF, based on a pre-stored TAI list. Furthermore, the processor is configured to identify a relative AMF capacity (RAC) value for each of the one or more RAN nodes. Thereafter, the processor is configured to transmit respective RAC value to each of the one or more RAN nodes, for configuring each of the one or more RAN nodes with the AMF.

[0015] In accordance with another aspect of the disclosure, an access and mobility management function (AMF) for notifying status of AMFs in a communication network is provided. The AMF from one or more AMFs of an AMF set includes a processor and a memory. The processor is configured to transmit a request to a network repository function (NRF) server, for status of other AMFs in the AMF set. The request comprises an identifier of the AMF set. The status may be one of a pre-defined status indicating failure/removal of the AMF in the AMF set or addition of an AMF to the AMF set. Further, the processor is configured to receive a notification indicating the status of the other AMFs in the AMF set, from the NRF server, in response to the request. Furthermore, the processor is configured to notify the status of at least one AMF from the other AMFs in the AMF set to one or more radio access network (RAN) nodes associated with the at least one AMF, when the status of the at least one AMF is one of a pre-defined status.

[0016] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure.

[0026] It should be appreciated by those skilled in the art that any block diagram herein represents conceptual views of illustrative systems embodying the principles of the subject matter. Similarly, it will be appreciated that any flowcharts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and executed by a computer or processor, whether or not such computer or processor is explicitly shown.

[0027] Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures.

[0028] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

[0029] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the disclosure is provided for illustration purpose only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

[0030] It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces.

[0031] While the disclosure is susceptible to various modifications and alternative forms, specific embodiment thereof has been shown by way of example in the drawings and will be described in detail below. It should be understood, however that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternatives falling within the scope of the disclosure.

[0032] The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by “comprises . . . a” does not, without more constraints, preclude the existence of other elements or additional elements in the system or apparatus.

[0033] Embodiments of the disclosure relate to a method for managing radio access network (RAN) nodes in a communication network. When RAN nodes are added to the communication network, each RAN node sends a tracking area identity (TAI) indicating locality of the RAN node to an access and mobility management function (AMF). The AMF is associated with an AMF set in an AMF region. The AMF determines whether the locality of each RAN node corresponds to primary serving localities or secondary serving localities of the AMF. The primary serving localities or secondary serving localities are identified based on a pre-stored TAI list. Further, the AMF identifies a relative AMF capacity (RAC) value for each RAN node. The RAC value of an AMF is defined as relative processing capacity of the AMF with respect to other AMFs in the AMF set, in order to load-balance AMFs within the AMF set. The RAC value is identified based on whether the locality of each RAN node corresponds to primary serving locality and secondary serving locality. The RAN nodes are configured with the AMF, by transmitting the respective RAC values. Hence, the disclosure provides methods for the AMFs to automatically configure the RAN nodes. Hence, the problems associated with manual configuration of RAN nodes is addressed. The disclosure ensures robustness and faster failure recovery of the AMFs in the AMF region. In addition, errors in configuration of the RAN nodes and maintaining a lengthy list of RAN node identifiers are avoided.

[0034] Further embodiments of the disclosure relate to a method of notifying status of the AMFs in the AMF set in the communication network. All the AMFs in an AMF set transmit a request to a network repository function (NRF) server, for monitoring other AMFs in the AMF set. The request includes an identifier of the AMF set. The NRF server monitors the AMF set with the identifier in the request. The AMFs in the AMF set receives a notification from the NRF server, indicating the status of the other AMFs in the AMF set. The status may be one of a pre-defined status indicating failure/removal of the AMF in the AMF set or addition of an AMF to the AMF set. Each AMF notifies the status of an AMF in the AMF set to RAN nodes associated with the AMF, when the status of the AMF is one of the pre-defined status. Hence, in the disclosure, the RAN nodes are notified of AMF failure, removal, or addition of the AMFs pro-actively. Hence, the time in RAN node contacting a new AMF or other AMF in the AMF set is reduced, thus ensuring a faster communication in case of AMF failure, removal, or addition.

[0035] FIG. 1A illustrates an environment 100 for managing RAN nodes in a communication network, according to an embodiment of the disclosure.

[0036] Referring to FIG. 1A, the communication network comprises one or more AMFs of an AMF set in an AMF region. The environment 100 comprises a user equipment (UE) 101, one or more RAN nodes 102₁, 102₂, . . . , 102_N, and an AMF region 103. The UE 101 may be a handheld device associated with a user. For example, the UE 101 may be a smartphone, a tablet, and the like. The 5G UE 101 may be any computing device, such as a laptop computer, a desktop computer, a personal computer (PC), a notebook, a smartphone, a tablet, e-book readers, a server, a network server, a cloud-based server, Internet of things (IoT) Device, vehicle, and the like. The UE 101 may communicate over a communication network with other UEs for using voice call services, video call services, messaging services, data services and the like. The communication network may be next generation e-NodeB (NG e-NodeB) network or a communication network working on 5G, Advanced 5G, 6^th generation (6G), or the like. The UE 101 connects to a core network via a radio access network (RAN) node. The RAN node may be in a hardware form or software form, any one of legacy base station, virtualized RAN (vRAN), cloud RAN, open RAN (ORAN), transmission point (TRP)/Multi-TRP based topology and the like. The communication network comprises multiple UEs which connect to the core network via one or more RAN nodes 102₁, 102₂, . . . , 102_N.

[0037] FIG. 1A shows a single UE 101, for illustrative purposes only and should not be considered as limiting. Access and mobility management function (AMF) manages connection and mobility management for the UEs in the communication network. In a cloud native design principle, an AMF runs as a set of AMFs to provide a high level of redundancy. The AMF region 103 comprises a plurality of AMF sets 104₁, 104₂, . . . , 104_N. Each AMF set from the plurality of AMF sets 104₁, 104₂, . . . , 104_N comprises one or more AMFs and a data storage.

[0038] Referring to FIG. 1A, it shows an AMF set 104₁ comprising one or more AMFs 105₁₁, 105₁₂, . . . , 105_1N and a data storage 106₁. An AMF set 104₂ comprises one or more AMFs 105₂₁, 105₂₂, . . . , 105_2N and a data storage 106₂. An AMF set 104_N comprises one or more AMFs 105_N1, 105_N2, . . . , 105_NN and a data storage 106_N. The data storage 106₁, 106₂, . . . 106_N may store context of the UEs of respective AMF set from the plurality of AMF sets 104₁, 104₂, . . . , 104_N. The one or more RAN nodes 102₁, 102₂, . . . , 102_N connects with the one or more AMFs 105₁₁, 105₁₂, . . . , 105_1N, 105₂₁, 105₂₂, . . . , 105_2N, . . . 105_N1, 105_N2, . . . , 105_NN to process a request from the UEs. For example, the UE 101 transmits a request for connection or a handover to a RAN node 102₁. The RAN node 102₁ routes the request to an AMF 105₁₁ based on an identifier of the AMF 105₁₁ in the request. The AMF 105₁₁ receives the request and manages connection or handover for the UE 101.

[0039] The one or more RAN nodes 102₁, 102₂, . . . , 102_N are configured with the one or more AMFs 105₁₁, 105₁₂, . . . , 105_1N, 105₂₁, 105₂₂, . . . , 105_2N, . . . 105_N1, 105_N2, . . . , 105_NN to process a request from the UEs. Each of the one or more AMFs 105₁₁, 105₁₂, . . . , 105_1N, 105₂₁, 105₂₂, . . . , 105_2N, . . . 105_N1, 105_N2, . . . , 105_NN may be associated with one or more primary serving localities and one or more secondary serving localities. The one or more primary serving localities of an AMF may comprise localities served by the AMF. The one or more secondary serving localities of an AMF may comprise localities served by the AMF in certain scenarios, such as network failure, AMF failure, and the like. The AMF may be configured as a primary AMF for the one or more RAN nodes 102₁, 102₂, . . . , 102_N in the one or more primary serving localities of the AMF. The AMF may be configured as a secondary AMF for the one or more RAN nodes 102₁, 102₂, . . . , 102_N in the one or more secondary serving localities of the AMF. RAN nodes may be added or removed from the communication network. The AMF in an AMF set has to configure the added RAN node to process the UE context. In the description, the one or more AMFs 105₁₁, 105₁₂, . . . , 105_1N of the AMF set 104₁ is considered hereafter, for explanation purpose only. The one or more AMFs 105₁₁, 105₁₂, . . . , 105_1N in the AMF set 104₁ are also referred as the one or more AMFs 105 hereafter, in the description. An AMF from the one or more AMFs 105 in the AMF set 104₁ configures the one or more RAN nodes 102₁, 102₂, . . . , 102_N added to the communication network.

[0040] Firstly, the AMF receives a tracking area identity (TAI) from each of the one or more RAN nodes added to the communication network. The TAI indicates a locality of each of the one or more RAN nodes. Further, the AMF determines whether the locality of each of the RAN nodes corresponds to one of, the one or more primary serving localities of the AMF and the one or more secondary serving localities of the AMF, based on a pre-stored TAI list. Furthermore, the AMF identifies a relative AMF capacity (RAC) value for each of the one or more RAN nodes. The RAC value is identified based on whether the locality corresponds to the one or more primary serving localities of the AMF and the one or more secondary serving localities of the AMF. Thereafter, the AMF transmits respective RAC value to each of the one or more RAN nodes, for configuring each of the one or more RAN nodes with the AMF. Consider that the RAN node 102₁ is in a primary serving locality 107 of the AMF 105₁₁ and is configured with the AMF 105₁₁ to process the context of the UE 101. Further, a RAN node 102₂ is added to the communication network. The RAN node 102₂ is in the primary serving locality 107 of an AMF 105₁₂. The AMF 105₁₂ determines that the locality of the RAN node 102₂ corresponds to the one or more primary localities of the AMF 105₁₂, upon receiving the TAI from the RAN node 102₂. The AMF 105₁₂ configures the RAN node 102₂ by transmitting an RAC value to the RAN node 102₂. The RAC value may indicate that the AMF 105₁₂ is a primary AMF to the RAN node 102₂. Further, consider a RAN node 102_N is added to communication network. The RAN node 102_N is in a secondary locality 108 of an AMF 105₁₂. The AMF 105₁₂ determines that the locality of the RAN node 102_N corresponds to the one or more secondary localities of the AMF 105₁₂, upon receiving the TAI from the RAN node 102_N. The AMF 105₁₂ configures the RAN node 102_N by transmitting an RAC value to the RAN node 102_N. The RAC value may indicate that the AMF 105₁₂ is a secondary AMF to the RAN node 102₂. The one or more primary localities and the one or more secondary localities are referred as the one or more primary serving localities 107 and the one or more secondary localities 108 hereafter in the description.

[0041] FIG. 1B illustrates an environment 109 for notifying status of AMFs in a communication network, according to an embodiment of the disclosure.

[0042] Referring to FIG. 1B, the communication network comprises one or more AMFs of an AMF set in an AMF region. The environment 109 comprises a UE 101₁, a UE 101₂, a RAN node 102₁, a RAN node 102₂, an AMF set 104₁ comprising one or more AMFs 105₁₁, 105₁₂, 105₁₃, . . . , 105_1N, and a network repository function (NRF) server 110. The communication network comprises multiple UEs.

[0043] FIG. 1B shows only two UEs 101₁, 101₂, for illustrative purposes only and should not be considered as limiting. Each AMF in the AMF set 104₁ may be associated with the one or more RAN nodes 102₁, 102₂, . . . , 102_N, i.e., the one or more RAN nodes 102₁, 102₂, . . . , 102_N are connected RAN nodes to each AMF. Hence, the one or more RAN nodes 102₁, 102₂, . . . , 102_N needs to be notified, upon AMF failure, removal, or addition in the AMF set 104₁.

[0044] An AMF from the one or more AMFs 105 of the AMF set 104₁ is configured to transmit a request to the NRF server 110, for status of other AMFs in the AMF set 104₁. The request comprises an identifier of the AMF set 104₁. The NRF server 110 monitors each AMF in the AMF set 104₁ using NRF heartbeat mechanism. In the NRF heartbeat mechanism, the NRF server 110 receives packets from each AMF continuously, which indicates operating condition of the AMF. When the NRF server 110 does not receive a packet from an AMF, the NRF server 110 detects a failure or removal of the AMF. Further, when a new AMF is added to the AMF set 104₁, the new AMF may transmit an identifier of the new AMF to the NRF server 110. The NRF server 110 may detect the new AMF, based on the identifier of the new AMF. The AMF receives a notification indicating the status of the other AMFs in the AMF set, from the NRF server 110, in response to the request. Further, the AMF notifies the status of at least one AMF from the other AMFs in the AMF set to the one or more RAN nodes 102₁, 102₂, . . . , 102_N associated with the at least one AMF, when the status of the at least one AMF is one of a pre-defined status. The pre-defined status may indicate failure, removal, or addition in the AMF set 104₁. In an example illustrated in FIG. 1B, each of the one or more AMFs 105₁₁, 105₁₂, 105₁₃, . . . , 105_1N transmits the request to the NRF server 110. The NRF server 110 detects the failure of AMF 105₁₂. The one or more AMFs 105 in the AMF set 104₁ may receive the notification from the NRF server 110 indicating the status of the AMF 105₁₂. The RAN nodes 102₁ and 102₂ may be associated with the AMF 105₁₂. The one or more AMFs 105 may notify the status of the AMF 105₁₂ to the RAN nodes 102₁ and 102₂. FIG. 1B shows an AMF 105₁₁ notifying the status of the AMF 105₁₂ to the RAN nodes 102₁ and 102₂. Similarly, the one or more AMFs other than the AMF 105₁₂, for instance, AMF 105₁₃, notifies the status of the AMF 105₁₂ to the RAN nodes 102₁ and 102₂ (not shown in FIGS.). The one or more RAN nodes 102₁, 102₂, . . . , 102_N are also referred as the one or more RAN nodes 102 in the description.

[0045] FIG. 2 shows a flowchart illustrating method operations for managing one or more RAN nodes in a communication network according to an embodiment of the disclosure.

[0046] Referring to FIG. 2, a method 200 may comprise one or more operations. The method 200 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.

[0047] The order in which the method 200 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.

[0048] At operation 201, the AMF from the one or more AMFs of the AMF set 104₁ receives the TAI from each of the one or more RAN nodes 102 added to the communication network. The TAI is an identity used to identify a tracking area of a RAN node. The tracking area of the RAN node indicates a coverage area of the RAN node. The TAI of the RAN node is constructed from mobile country code (MCC), mobile network code (MNC) and tracking area code) (TAC). The TAI of each of the one or more RAN nodes 102 indicates a locality of each of the one or more RAN nodes. In an embodiment of the disclosure, when the one or more RAN nodes 102 are added to the communication network, each of the one or more RAN nodes 102 sends a TAI associated with corresponding RAN node. In another embodiment of the disclosure, a network operator may add the one or more RAN nodes 102 to the communication network and transmit a TAI list to the AMF. In an example, the network operator may remove existing RAN nodes from the communication network and add the one or more RAN nodes 102. In another example, the network operator may add the one or more RAN nodes to the communication network including the existing RAN nodes. The TAI list may comprise the TAI of each of the one or more RAN nodes 102 added to the communication network. The TAI may be received from the one or more RAN nodes 102 during new generation (NG) setup procedure. In the NG setup procedure, application-level data needed for configuration of each RAN node with the AMF is exchanged. Each RAN node may send the TAI in a NG setup request to the AMF. The AMF identifies the locality of each of the one or more RAN nodes 102 from the TAI.

[0049] FIG. 3 shows illustration for managing RAN nodes in a communication network, according to an embodiment of the disclosure.

[0050] Referring to FIG. 3, an AMF 1 receives the TAI from RAN nodes 304₁ and 304₂ added to the communication network. The AMF 1, AMF 2, AMF 3, and AMF 4 may be associated with the AMF region. The AMF 1 may identify the locality of the RAN node 304₁ as the locality 301. Further, the AMF 1 may identify the locality of the RAN node 304₂ as the locality 302. Similarly, AMF 2, AMF 3, and AMF 4 of an AMF set 303 may receive the TAI from the one or more RAN nodes 304₁ and 304₂. It should be noted that the AMF set 303 may comprise a large number of AMFs. FIG. 3 shows only four AMFs, for illustrative purposes only.

[0051] Referring back to FIG. 2, at operation 202, the AMF determines whether the locality of each of the one or more RAN nodes 102 corresponds to one of, the one or more primary serving localities 107 of the AMF and the one or more secondary serving localities 108 of the AMF. The AMF comprises a pre-stored TAI list. The pre-stored TAI list may comprise a first sub-list indicating the one or more primary serving localities 107 of the AMF and a second sub-list indicating the one or more secondary serving localities 108 of the AMF. In an embodiment of the disclosure, the pre-stored TAI list may comprise a range of TAIs defining the one or more primary serving localities 107 of the AMF and the one or more secondary serving localities 108 of the AMF. In an embodiment of the disclosure, the TAI list may be pre-stored in a memory of the AMF. In another embodiment of the disclosure, the TAI list may be pre-stored in a data storage from the data storages 106₁, 106₂, . . . , 106_N, corresponding to the AMF set associated with the AMF. The AMF determines whether the locality of each of the one or more RAN nodes 102 corresponds the one or more primary serving localities 107 or the one or more secondary serving localities 108 of the AMF based on the pre-stored list. The AMF may perform a one-to-one comparison between the locality of each of the one or more RAN nodes 102, and the one or more primary serving localities 107 and the secondary serving localities 108. The AMF may determine that the locality corresponds the one or more primary serving localities 107 or the one or more secondary serving localities 108 of the AMF based on the comparison. A person skilled in the art will appreciate that any methods other than the above-mentioned method may be used to determine whether the locality corresponds the one or more primary serving localities 107 or the one or more secondary serving localities 108 of the AMF, based on the pre-stored list. Referring again to the example 300 of FIG. 3, the AMF 1 may determine whether the locality of each of the RAN nodes 304₁ and 304₂ corresponds to the one or more primary serving localities 107 or the one or more secondary localities 108. The AMF 1 may determine that the locality of the RAN node 304₁ corresponds to a primary locality of the AMF 1. Further, the AMF 1 may determine that the locality of the RAN node 304₂ corresponds to a secondary locality of the AMF 1. Similarly, the AMF 2 may determine that the locality of the RAN node 304₁ and the RAN node 304₂ corresponds to a primary locality and a secondary locality of the AMF 2. This similar process is performed by AMF 3, AMF 4, and other AMFs in the AMF set 303.

[0052] Referring to FIG. 2, at operation 203, the AMF identifies the RAC value for each of the one or more RAN nodes 102. The RAC value helps in load balancing data traffic from the UEs across the AMFs. The RAC value identified for a RAN node from the one or more RAN nodes 102 indicates that the AMF is configured as a primary AMF for the RAN node, when the locality of the RAN node corresponds to the one or more primary serving localities 107 of the AMF. In an embodiment of the disclosure, the RAC value may be a first pre-defined value, indicating that the AMF is configured as the primary AMF for the RAN node. For example, the RAC value may be 100. In another embodiment of the disclosure, the RAC value may be a real-time value, when the locality of the RAN node corresponds to the one or more primary serving localities 107 of the AMF. The real-time value may be a vector comprising one or more values indicating a capacity of each of one or more primary AMFs from the one or more AMFs 105, to process context of the UE 101. In an embodiment of the disclosure, the RAC value is determined based on a current load of the AMF, number of AMFs in the AMF set, and the like. In another embodiment of the disclosure, the RAC value is manually provided by a network operator. A person skilled in the art will appreciate that the RAC value may be determined by any other known methods. For example, the locality of a RAN node may correspond to a primary locality of AMF 1 and AMF 2. Here, the AMF 1 and AMF 2 are the one or more primary AMFs for the RAN node. The data traffic of UEs via the RAN node needs to be distributed among the AMF 1 and AMF 2. The AMF 1 and the AMF 2 may determine the capacity of each of the AMF 1 and the AMF 2 as 60 and 40, respectively, on a scale of 0-100. The real-time value may be a vector comprising values 60 and 40 along with identifiers associated with the AMF 1 and AMF 2, respectively. The RAC value identified for a RAN node from the one or more RAN nodes 102 may indicate that the AMF is configured as a secondary AMF for the RAN node, when the locality of the RAN node corresponds to the one or more secondary serving localities 108 of the AMF. The RAC value may be a second pre-defined value, indicating that the AMF is configured as the secondary AMF for the RAN node. For example, the second pre-defined value may be 0. In a future instance, the RAN node may transmit a TAI for configuring with the secondary AMF, when a primary AMF configured with the RAN node is removed/failed. In such instance, the second pre-defined value may be re-configured to a value, after configuration with the secondary AMF. For example, the second pre-defined value may be 100. In another example, the second pre-defined value may be 60 based on load balancing among the AMFs in the AMF set. A person skilled in the art will appreciate that the RAC value is configurable as a pre-defined value, a real-time value, or any value, based on the implementation. Referring again to the example 300 in FIG. 3, the AMF 1 identifies the RAC value for the RAN node 304₁ as 100. The AMF 2 identifies the RAC value for the RAN node 304₁ as 100. Further, the AMF 2 identifies the RAC value for the RAN node 304₂ as 0. Similarly, the AMF 3 identifies the RAC value for the RAN node 304₂ as 100. The AMF 3 identifies the RAC value for the RAN node 304₁ as 0. The AMF 4 identifies the RAC value for the RAN node 304₂ as 100.

[0053] Referring to FIG. 2, at operation 204, the AMF transmits respective RAC value to each of the one or more RAN nodes 102. The AMF may include the respective RAC value of each of the one or more RAN nodes 102 in a NG setup response. Further, the AMF may transmit the NG setup response to each of the one or more RAN nodes 102, in response to the NG setup request from each of the one or more RAN nodes 102. The AMFs are configured with the one or more RAN nodes 102 as the primary AMFs or the secondary AMFs based on the identified RAC value. Referring again to the example 300 in FIG. 3, the AMF 1 and the AMF 2 are configured as the primary AMFs to the RAN node 304₁. The AMF 3 and AMF 4 are configured as the secondary AMFs to the RAN node 304₂.

[0054] FIG. 4 shows a flowchart illustrating method operations for notifying status of AMFs in the communication network according to an embodiment of the disclosure.

[0055] Referring to FIG. 4, a method 400 may comprise one or more operations. The method 400 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.

[0056] The order in which the method 400 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.

[0057] At operation 401, the AMF from the one or more AMFs 105 of the AMF set 104₁ transmits the request to the NRF server 110, for status of other AMFs in the AMF set 104₁. The method is described by considering the AMF from the AMF set 104₁. The method operations described in FIG. 4 are performed by each of the one or more AMFs of each of the plurality of AMF sets 104₁, 104₂, . . . 104_N. Each of the plurality of AMF sets 104₁, 104₂, . . . 104_N registers or subscribes to the NRF server 110. The AMF may transmit the request to the NRF server 110, upon the registration. The request may comprise an identifier of the AMF set 104₁. The AMF may determine the identifier of the AMF set 104₁ from a unique identifier associated with the AMF. For example, the unique identifier is a globally unique AMF ID (GUAMI) associated with the AMF in a 5G communication network. In another example, the unique identifier is a GUAMI mapped with a long-term evolution (LTE) identifier (such as globally unique MME identifier) in an LTE communication network. The identifier of the AMF set associated with the AMF is a field in the unique identifier of the AMF. The NRF server 110 may continuously monitor the one or more AMFs 105 in the AMF set 104₁, upon receiving the request from the AMF. The NRF server 110 may monitor the one or more AMFs 105 in the AMF set 104, using the NRF heartbeat mechanism. The NRF server 110 receives packets from the AMF continuously to monitor the one or more AMFs.

[0058] At operation 402, the AMF receives a notification indicating the status of the other AMFs in the AMF set 104₁, from the NRF server 110, in response to the request. The NRF server 110 may not receive a packet from an AMF. The NRF server 110 detects a failure or removal of the AMF. Further, when a new AMF is added to the AMF set 104₁, the new AMF may transmit an identifier of the new AMF to the NRF server 110. The NRF server 110 may detect the new AMF, based on the identifier of the new AMF. The NRF server 110 may detect the new AMF by comparing the identifier with stored list of identifiers of the one or more AMFs 105 (existing AMFs). The NRF server 110 may provide the notification indicating the status of the other AMFs in the AMF set 104₁.

[0059] At operation 403, the AMF notifies the status of at least one AMF from the other AMFs in the AMF set 104₁ to the one or more RAN nodes 102 associated with the at least one AMF. The one or more RAN nodes 102 may be connected RAN nodes of the AMF. The one or more RAN nodes 102 may comprise the RAN nodes for which the AMF is serving as a primary AMF or a secondary AMF. The AMF may notify the status of the at least one AMF from the other AMFs, when the status of the at least one AMF is one of a pre-defined status. The pre-defined status of the at least one AMF includes one of, failure of the at least one AMF and removal of the at least one AMF from the AMF set 104₁. Further, the at least one AMF may be a new AMF added to the AMF set 104₁, wherein the pre-defined status of the at least one AMF includes addition of the at least one AMF to the AMF set 104₁. The AMF may receive an acknowledgement from each of the one or more RAN nodes 102, upon notifying the status of the at least one AMF. Further, each AMF in the AMF set 104₁ other than the at least one AMF may notify the status of the at least one AMF. A single acknowledgement may be received from each of the one or more RAN nodes 102, when the one or more AMFs 105 other than the at least one AMF notifies same status of the at least one AMF. The one or more RAN nodes 102 do not send the acknowledgment all the AMFs in the AMF set 104₁, once the one or more RAN nodes 102 sends the acknowledgement to the AMF (first AMF in the AMF set 104₁ notifying the status). This saves time and processing capacity in sending the acknowledgement to all the AMFs. The one or more RAN nodes 102 selects AMFs other than the at least one AMF, when the status of the at least one AMF indicates one of, failure and removal of the at least one AMF. The one or more RAN nodes 102 selects the AMFs for transmitting context of the UE 101 in the communication network. The one or more RAN nodes 102 selects the at least one AMF, when the status of the at least one AMF indicates addition of the at least one AMF, for transmitting context of the UE 101.

[0060] FIGS. 5A and 5B show illustrations for notifying status of AMFs in a communication network according to various embodiments of the disclosure.

[0061] Referring to example 500 in FIG. 5A, at operation 1, the RAN node 102 transmits the context of the UE 101 to AMF 1. The AMF 1 may be in a non-operating condition. At operation 2, the AMF 2 notifies the status of the AMF 1 to the RAN node 102, indicating the failure of the AMF 1. At operation 3, the RAN node 102 may transmit the context of the UE 101 to AMFs other than the AMF 1, in an AMF set associated with the AMF 1. FIG. 5A illustrates the RAN node 102 transmitting the context of the UE 101 to the AMF 2.

[0062] Referring to example 501 in FIG. 5B, the RAN node 102 transmits the context of the UE 101 to AMF 1. The AMF 1 notifies the status of a new AMF added to the AMF set, to the RAN node 102. At operation 3, the RAN node 102 may transmit the context of the UE 101 to the new AMF. The RAN node 102 may transmit the context of the UE 101 to the new AMF for load balancing between the AMFs in the AMF set.

[0063] FIG. 6 illustrates an internal architecture 600 of an AMF for managing RAN nodes 102 in a communication network 103, according to an embodiment of the disclosure.

[0064] Referring to FIG. 6, the internal architecture 600 is applicable for each AMF in the one or more AMFs in each of the plurality of sets 104. Hence, the AMF is also referred as the AMF 105 in explanation of the internal architecture 600.

[0065] The AMF 105 may include central processing units 603 (also referred as “CPUs” or “a processor 603”), an input/output (I/O) interface 601, and a memory 602. In some embodiments of the disclosure, the memory 602 may be communicatively coupled to the processor 603. The memory 602 stores instructions executable by the processor 603, which, on execution, may cause the processor 603 to configure the RAN nodes 102 with the AMF in the AMF region 103. In an embodiment of the disclosure, the memory 602 may include one or more modules 605 and data 604. The one or more modules 605 may be configured to perform the operations of the disclosure using the data 604. In an embodiment of the disclosure, each of the one or more modules 205 may be a hardware unit which may be outside the memory 602 and coupled with the AMF 105. As used herein, the term modules 605 refers to an application specific integrated circuit (ASIC), an electronic circuit, a field-programmable gate arrays (FPGA), programmable system-on-chip (PSoC), a combinational logic circuit, and/or other suitable components that provide described functionality. The one or more modules 605 when configured with the described functionality defined in the disclosure will result in a novel hardware. Further, the I/O interface 601 is coupled with the processor 603 through which an input signal or/and an output signal is communicated.

[0066] In one implementation, the modules 605 may include, for example, a communication module 610, a determination module 611, an identification module 612, and other modules 613. It will be appreciated that such aforementioned modules 605 may be represented as a single module or a combination of different modules. In one implementation, the data 604 may include, for example, TAI data 606, determination data 607, RAC data 608, and other data 609.

[0067] In an embodiment of the disclosure, the communication module 610 may be configured to receive the TAI from each of the one or more RAN nodes 102 added to the communication network. The TAI of each of the one or more RAN nodes 102 indicates the locality of each of the one or more RAN nodes. Each RAN node may send the TAI in a setup request to the communication module 610. The TAI of each of the one or more RAN nodes 102 may be stored as the TAI data 606 in the memory 602.

[0068] In an embodiment of the disclosure, the determination module 611 may be configured to receive the TAI data 606 from the communication module 610. The determination module 611 determines whether the locality of each of the one or more RAN nodes 102 corresponds to one of, the one or more primary serving localities 107 and the one or more secondary serving localities 108 of the AMF 105, based on the pre-stored TAI list. In an embodiment of the disclosure, the TAI list may be pre-stored in the memory 602 of the AMF 105, for efficient processing. In another embodiment of the disclosure, the TAI list may be pre-stored in a data storage from the data storages 106₁, 106₂, . . . , 106_N, corresponding to the AMF set associated with the AMF 105, for improved resiliency. Data related to the determination of whether the locality corresponds to one of, the one or more primary serving localities 107 and the one or more secondary serving localities 108 of the AMF 105 may be stored as the determination data 607 in the memory 602.

[0069] In an embodiment of the disclosure, the identification module 612 may be configured to receive the determination data 607 from the determination module 611. The identification module 612 identifies the RAC value for each of the one or more RAN nodes 102, based on the determination data 607. The RAC value identified for a RAN node from the one or more RAN nodes 102 indicates that the AMF 105 is configured as a primary AMF for the RAN node, when the locality of the RAN node corresponds to the one or more primary serving localities 107 of the AMF 105. The RAC value may be the first pre-defined value or the real-time value, indicating that the AMF is configured as the primary AMF for the RAN node. The RAC value identified for a RAN node from the one or more RAN nodes 102 may indicate that the AMF is configured as a secondary AMF for the RAN node, when the locality of the RAN node corresponds to the one or more secondary serving localities 108 of the AMF 105. The RAC value may be a second pre-defined value, indicating that the AMF 105 is configured as the secondary AMF for the RAN node. The RAC values identified for each of the one or more RAN nodes 102 may be stored as the RAC data 608 in the memory 602.

[0070] In an embodiment of the disclosure, the communication module 610 may be further configured to receive the RAC data 608 from the identification module 612. The communication module 610 transmits the setup response including the RAC value to each of the one or more RAN nodes 102, for configuring the one or more RAN nodes 102 with the AMF 105.

[0071] The other data 609 may store data, including temporary data and temporary files, generated by the one or more modules 605 for performing the various functions of the AMF 105. The other data 609 may be stored in the memory 602. The one or more modules 605 may also include the other modules 613 to perform various miscellaneous functionalities of the AMF 105. It will be appreciated that the one or more modules 605 may be represented as a single module or a combination of different modules.

[0072] FIG. 7 illustrates an internal architecture 700 of an AMF for notifying status of AMFs in a communication network, according to an embodiment of the disclosure.

[0073] Referring to FIG. 7, in one implementation, the modules 605 of the AMF 105 may include, for example, a communication module 610 and other modules 613. It will be appreciated that such aforementioned modules 605 may be represented as a single module or a combination of different modules. In one implementation, the data 604 may include, for example, identifier data 701, status data 702, and other data 609.

[0074] In an embodiment of the disclosure, the communication module 610 may be configured to transmit the request to the NRF server 110, for status of other AMFs in the AMF set 104₁. The request may comprise the identifier of the AMF set 104₁. The identifier of the AMF set 104₁ may be stored as the identifier data 701 in the memory 602. Further, the communication module 610 may be configured to receive the notification indicating the status of the other AMFs in the AMF set 104₁, from the NRF server 110. The status of the other AMFs may be stored as the status data 702 in the memory 602. Furthermore, the AMF may be configured to notify the status of at least one AMF from the other AMFs in the AMF set 104₁ to the one or more RAN nodes 102 associated with the at least one AMF.

[0075] The disclosure provides methods for the AMFs to automatically configure the RAN nodes. Hence, the problems associated with manual configuration of RAN nodes is addressed. The disclosure ensures robustness and faster failure recovery of the AMFs in the AMF region. In addition, errors in configuration of the RAN nodes and maintaining a lengthy list of RAN node identifiers is avoided.

[0076] The disclosure enables seamless addition or removal of the RAN nodes, without any manual intervention in the AMFs.

[0077] In the disclosure, the RAN nodes are notified of AMF failure, removal, or addition of the AMFs pro-actively. Hence, the time in RAN node contacting a new AMF or other AMF in the AMF set is reduced, thus ensuring a faster communication in case of AMF failure, removal, or addition.

[0078] In the disclosure, the AMF in the AMF set can be seamlessly treated as interchangeable mobility management node, since the failure or removal is notified pro-actively. This provides seamless restoration of context of a UE and hence add service continuity to network. Further, the network operator can choose to provide geo-redundancy per PLMN or at slice level granularity.

[0079] The terms “an embodiment”, “embodiment”, “embodiments”, “the embodiment”, “the embodiments”, “one or more embodiments”, “some embodiments”, and “one embodiment” mean “one or more (but not all) embodiments of the disclosure(s)” unless expressly specified otherwise.

[0080] The terms “including”, “comprising”, “having” and variations thereof mean “including but not limited to”, unless expressly specified otherwise.

[0081] The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a”, “an” and “the” mean “one or more”, unless expressly specified otherwise.

[0082] A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary a variety of optional components are described to illustrate the wide variety of possible embodiments of the disclosure.

[0083] When a single device or article is described herein, it will be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device/article may be used in place of the more than one device or article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the disclosure need not include the device itself.

[0084] The illustrated operations of FIGS. 2 and 4 show certain events occurring in a certain order. In alternative embodiments of the disclosure, certain operations may be performed in a different order, modified, or removed. Moreover, steps may be added to the above-described logic and still conform to the described embodiments. Further, operations described herein may occur sequentially or certain operations may be processed in parallel. Yet further, operations may be performed by a single processing unit or by distributed processing units.

[0085] Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the disclosure be limited not by this detailed description, but rather by any claims that issue on an application based here on. Accordingly, the disclosure of the embodiments of the disclosure is intended to be illustrative, but not limiting, of the scope of the disclosure, which is set forth in the following claims.

[0086] While the disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents.