Method for identifying accessible node and implementation system thereof

Abstract

A method of identifying accessible nodes for a wireless network, the method comprising: storing in a first device a first list of nodes, where the first list comprises: a corresponding state of each of the nodes in the first list, and the first device is available in a first technology generation of the wireless network. The method further includes updating a second list of nodes in a second device based on the first list of nodes, where the second list does not contain a state of each of the nodes of the second list, and the second device is available in a second technical generation of the wireless network, the second technical generation being different from the first technical generation. The method further includes, in response to receiving a connection request from the user equipment, providing connection information for nodes in the second list of nodes to the user equipment.

Description

TECHNICAL FIELD

[0001] This description relates to a method of identifying accessible nodes for a wireless network and a system for implementing the method. BACKGROUND

[0002] As technology advances for wireless networks, such as radio access networks (RANs), new generations of network devices are developed. In some instances, user equipment (UE), such as mobile phones or other mobile devices, are unable to interact with network devices of the most recently developed generation. In some instances, UEs are directed to connect to network devices of a particular generation based on a user's subscription level or other criteria. In some instances, network devices from multiple generations are used at the same base station, data center, or cluster to provide connectivity for UEs.

[0003] To provide connectivity to a wireless network for a UE, a base station, data center, or cluster connects the UE to one or more nodes. The nodes, in turn, provide connectivity to network services. While some generations of network devices update the status of nodes based on the availability of connecting a UE to the nodes, there is a risk that network devices that do not include automatically updating node status information can experience difficulties in connecting a UE to the network. BRIEF DESCRIPTION OF DRAWINGS

[0004] Aspects of the disclosure are best understood from the following detailed description when read in conjunction with the accompanying drawings. It is noted that, in accordance with standard practice, the various features are not drawn to scale. In fact, the dimensions of the various features can be arbitrarily increased or decreased for clarity of discussion.

[0005] Figure 1 is a schematic diagram of an architecture of a multi-generation network device according to some embodiments.

[0006] Figure 2 is a sequence diagram of communications between components of a multi-generation network device according to some embodiments.

[0007] Figure 3 is a sequence diagram of communications between components of a multi-generation network device according to some embodiments.

[0008] Figure 4 is a sequence diagram of communications between components of a multi-generation network device according to some embodiments.

[0009] Figure 5 is a flow diagram of a method of selecting a node for connecting to a user equipment (UE) according to some embodiments.

[0010] Figure 6 is a block diagram of a system for selecting a node for connecting to a UE according to some embodiments. DETAILED DESCRIPTION

[0011] The following disclosure provides many different embodiments, or examples, for implementing different features of the provided subject matter. Specific examples of components, values, operations, materials, arrangements, etc. are described below to simplify the present disclosure. Of course, these are merely examples and are not intended to be limiting. Other components, values, operations, materials, arrangements, etc. can be

[0012] Rapid development of wireless access networks (RANs) has resulted in an increasing number of network devices being used to support different generations of networks. To increase the efficient use of structures such as cell towers, and to provide access for user equipment (UEs) having different capabilities, network devices from different generations of networks are often used in combination. In some embodiments, the functionality of network devices from different generations of networks is integrated into a single device. In some embodiments, network devices are maintained as independent devices having different functionality for different generations of network devices.

[0013] In some instances, a UE such as a mobile phone or another mobile device is capable of utilizing the functionality of network devices across multiple generations. However, in some instances, the UE is limited in its utilization of functionality across multiple generations. For example, in some instances, the hardware of the UE lacks the ability to communicate with network devices for a recently developed generation such as the fifth generation (5G) or the sixth generation (6G). In some instances, for a recent generation, a service contract associated with the UE limits the ability of the UE to utilize network device functionality. For example, a user operating the UE is provided a lower cost for a service contract to utilize older generation network devices.

[0014] When a UE attempts to access a network, the UE establishes contact with a network device of a particular generation. The network device exchanges information with the UE in order to connect the UE to a node that will allow the UE to access a service of the network. According to some embodiments, the service includes a data service, a voice service, a text service, etc. In some instances, a failure occurs in a node that prevents the UE from properly connecting with the node. However, in some instances, the network device will continue to attempt to connect the UE to the failed node if the network device does not automatically update the status of the node. In some embodiments, the node includes one of a registered state, meaning the node can be discovered and can connect with the UE; a suspended state, meaning the node can be discovered but cannot connect with the UE; or an undiscoverable state, meaning the node cannot be discovered. In some embodiments, the UE can only properly connect with a node that is in the registered state. Thus, attempts to connect the UE to a node that is in the suspended state or the undiscoverable state decreases the likelihood that the UE will properly connect to the network or that the connection with the network will be unreliable. Users of UEs that are unable to effectively connect to the network due to the failed node can experience an increase in dissatisfaction with the network service.

[0015] Further, some newer generation network devices are capable of automatically updating the node status to decrease the risk of attempting to connect the UE to a failed node. In such cases, different UEs with different connection capabilities have an increased risk of having different service experiences for the same base station, data center, or cluster. This situation can exacerbate the dissatisfaction of users of UEs that are unable to effectively connect to the network. The present description provides a method for a network device that provides communication functionality for different generations in order to increase the likelihood of effective connection of a UE to a network regardless of whether the UE is capable of connecting to a more recent generation network device. As described below, the ability to automatically update the node status will help to increase user satisfaction with the network because UEs operated by users are more likely to effectively connect to the network. The description below is based on an example of a combined fourth generation (4G) and 5G architecture. However, one of ordinary skill in the art will recognize that the present description is not limited to only this combination of network devices.

[0016] Figure 1This is a schematic diagram of a multi-generation network device 100 according to some embodiments. The multi-generation network device 100 is configured to allow a user device (UE) 102 to connect to a node to access services of a wireless network. The multi-generation network device 100 includes devices for implementing 4G and 5G functionality. Those skilled in the art will recognize that the use of 4G and 5G is merely exemplary and not a limitation of the present description. In some embodiments, the UE 102 includes a mobile phone or other suitable mobile device capable of accessing a wireless network. In some embodiments, functional components of the multi-generation network device 100 are implemented using separate devices capable of communicating together. In some embodiments, at least one functional component is integrated with another functional component of the multi-generation network device 100 into a single device capable of communicating with other components of the multi-generation network device 100. Anchors for the multi-generation network device 100 include an SMF+PGW-C 160. This device provides connectivity between the UE 102 and network services such as data transfer, voice, SMS, or other suitable services. Although Figure 1 The multi-generation network device 100 includes a single SMF+PGW-C 160, but those skilled in the art will recognize that multiple nodes can be used in the same architecture to provide connectivity for a greater number of UEs 102.

[0017] The multi-generation network equipment 100 includes a next-generation radio access network (NG-RAN) 105, which is configured to facilitate connectivity between the UE 102 and nodes using 5G technology. The NG-RAN 105 helps manage radio resources and controls the radio bearers used to establish communication with the UE 102.

[0018] The multigenerational network device 100 also includes an Access and Mobility Management Function (AMF) 110. AMF 110 is configured to establish an N2 interface with NG-RAN 105. AMF 110 is configured to process Non-Access Stratum (NAS) messages from UE 102 to establish, maintain, or release connections between UE 102 and the network. Additional functionality of AMF 110 is discussed below regarding its interface with Network Storage Function (NRF) 120.

[0019] The multigenerational network device 100 also includes an NRF 120. The NRF 120 is configured to allow the AMF 110 to discover which nodes (such as SMF+PGW-C 160) are available to connect to the UE 102. The NRF 120 maintains a node list based on Network Function (NF) registration data. In some embodiments, the NRF 120 is configured to automatically notify the AMF 110 in response to a state change in one of the nodes. In some embodiments, the NRF 120 is configured to communicate with the AMF 110 using 3GPP protocols.

[0020] The multigenerational network equipment 100 also includes an evolved universal terrestrial radio access (E-UTRAN) 125. The E-UTRAN 125 is configured to facilitate connectivity between the UE 102 and nodes using 4G technology. The E-UTRAN 125 helps manage radio resources and controls the radio bearers used to establish communication with the UE 102.

[0021] The multi-generation network device 100 also includes a Mobility Management Entity (MME) 130. MME 130 is configured to establish an S1-MME interface with E-UTRAN 125. MME 130 is configured to manage UE 102 to establish, maintain, or release connections between UE 102 and the network. MME 130 is also configured to establish N26 with AMF 110 for exchanging management services between the 4G and 5G networks. Additional functionality of MME 125 for connecting to Domain Name System (DNS) 140 is discussed below.

[0022] The multigenerational network device 100 also includes a DNS 140. The DNS 140 is configured to allow the MME 130 to discover which nodes (such as SMF+PGW-C 160) can be used to connect to the UE 102. Unlike the NRF 120, the DNS 140 only maintains a list of nodes and does not include information related to node status. In some embodiments, the DNS 140 is configured to communicate with the MME 130 using 3GPP protocols.

[0023] The multigenerational network device 100 also includes a disconnect gateway (SGW) 145. SGW 145 assists in routing and forwarding data packets between UE 102 and the network. SGW 145 is configured as an S1-U from E-UTRAN 125 for handover of UE 102 between nodes during handover procedures. SGW 145 is also configured to establish an S11 interface with MME 130 to manage data sessions of UE 102 connected to the network.

[0024] The multi-generation network device 100 also includes integrated user plane functionality and a packet data network gateway-user plane (UPF+PGW-U) 150. The UPF+PGW-U 150 is configured to connect data to the Internet over the network. The UPF+PGW-U 150 is configured to establish an S5-U interface with the SGW 145 to provide Internet Protocol (IP) services to the UE 102. The UPF+PGW-U is configured to establish an N3 interface with the NG-RAN 105 for handover of the UE 102 between nodes during handover procedures.

[0025] The multi-generation network device 100 also includes integrated session management functionality and a packet data network gateway control plane (SMF+PGW-C) 160. The SMF+PGW-C 160 is configured to relay session-related messages between devices in the network. The SMF+PGW-C 160 is also configured to assign IP addresses and establish, modify, and release connections between UE 102 and the network. The SMF+PGW-C 160 is configured to establish an N4 interface with the UPF+PGW-U 140 for session management, including service redirection and event reporting. The SMF+PGW-C 160 is configured to establish an S5-C interface with the SGW 145 for providing IP services to the control plane. The SMF+PGW-C 160 is also configured to establish an N10 interface with the HSS+UDM 180 for managing connection sessions for UE 102. The SMF+PGW-C160 is configured to establish an N11 interface with the AMF 110 for triggering the addition, modification, or deletion of data sessions during the connection between the UE 102 and the network.

[0026] The multi-generation network device 100 also includes an integrated policy control function (PCF) 170. PCF 170 is configured to establish and maintain rules for data flows through the network. PCF 170 is configured to establish an N7 interface with SMF+PGW-C 160 for establishing, maintaining, and updating policies for data flows. PCF 170 is configured to establish an N15 interface with AMF 110 for controlling policies for data flows to UE 102.

[0027] The multi-generation network device 100 also includes an integrated Home Subscriber Server and Unified Data Management (HSS+UDM) 180. HSS+UDM 180 is configured to store subscriber-related information, such as authentication information and a list of available services. HSS+UDM 180 is configured to establish an S6a interface with MME 130 for accessing user authentication, location, and reservation information. HSS+UDM 180 is configured to establish an N8 interface with AMF 110 for accessing user data stored in HSS+UDM 180.

[0028] During operation, the multigenerational network device 100 is configured to collect node status information using the NRF 120. The NRF 120 can communicate the node status information to the AMF 110, allowing the AMF 110 to reliably connect the UE 102 to the node, thereby allowing the UE 102 to access the network. The DNS 140 only maintains a list of nodes without corresponding information related to node status. If a node is experiencing a failure, the node will continue to appear in the node list in the DNS 140 in other ways. However, in some embodiments, in the multigenerational network device 100, the NRF 120 can communicate with the DNS 140 to update the node list in the DNS 140 to include only nodes in an accessible state. In some embodiments, the NRF 120 can communicate with the DNS 140 to generate and update an exclusion list that includes a list of failed nodes. That is, through communication between the DNS 140 and the NRF 120, the DNS 140 can maintain one or more lists that allow the DNS 140 to accurately notify the MME 130 of nodes available for connection. Therefore, compared to other methods, the multi-generation network device 100 can reduce or eliminate the risk of the MME 130 attempting to connect the UE 102 to a faulty node. Consequently, the reliability of the connection between the UE 102 and the network is increased, thereby improving customer satisfaction with the network.

[0029] Figure 2 This is a sequence diagram of communication 200 between components of a multi-generation network device according to some embodiments. Communication 200 occurs between SMF+PGW-C 160 and NRF 120, and between NRF 120 and AMF 110. Although the reference numerals refer to multi-generation network device 100 (… Figure 1 The components of the communication 200 are not limited to the multi-generation network device 100, but those skilled in the art will understand that the features of the communication 200 are not limited to those of the multi-generation network device 100. Figure 1 Communication 200 includes multiple scenarios 230, 240, and 250. Each scenario in 230 and 240 indicates a situation where a node is identified as faulty. Scenario 250 indicates a situation where a node's profile is removed from NRF 120. In a non-limiting example of communication 200, SMF+PGW-C 160 is the anchor point of the network and is considered a node. In some embodiments, messages of communication 200 are transmitted via a wired connection. In some embodiments, at least one message of communication 200 is transmitted wirelessly.

[0030] In message 205, SMF+PGW-C 160 sends a Network Function (NF) registration request to NRF 120. The NF registration request is used to register the node in NRF 120, making the node discoverable by AMF 110 for use with UEs (e.g., UE 102). Figure 1Connecting to the network. In some embodiments, message 205 includes information about the node's capabilities and identification information about the node, allowing NRF 120 to later provide address and capability information to AMF 110 in communication 200. In some embodiments, message 205 is automatically sent by SMF+PGW-C 160 in response to a node being added to a base station, data center, or cluster. In some embodiments, message 205 is sent in response to SMF+PGW-C 160 receiving instructions from a network operator.

[0031] In message 210, NRF 120 sends an NF registration response to SMF+PGW-C 160. The NF registration response informs SMF+PGW-C 160 whether the node has been correctly registered with NRF 120. In some embodiments, message 210 includes an acknowledgment of the request and an indication of successful registration. In some embodiments where registration fails, message 210 includes information such as an error code indicating the reason for the node's registration failure.

[0032] In message 215, SMF+PGW-C 160 sends an NF update request to NRF 120. The NF update request provides NRF 120 with information about the node's update. In some embodiments, the update information includes information related to the node's functionality. In some embodiments, the update information includes information related to the node's updated address. In some embodiments, the update information includes information related to the node's updated status. In some embodiments, message 215 is automatically sent by SMF+PGW-C 160 in response to a node being rebooted, updated, relocated within the network hierarchy, or other suitable changes to the node. In some embodiments, message 215 is sent in response to SMF+PGW-C 160 receiving instructions from the network operator.

[0033] In message 220, NRF 120 sends an NF update response to SMF+PGW-C 160. The NF update response informs SMF+PGW-C 160 whether the node has been correctly updated in NRF 120. In some embodiments, message 220 includes an acknowledgment of the request and an indication of a successful update. In some embodiments where the update is unsuccessful, message 220 includes information indicating why the node's update failed, such as an error code.

[0034] In scenario 230, NRF 120 determines that a heartbeat timeout (TO) 235 has occurred. That is, the node cannot provide a scheduled heartbeat to NRF 120. A heartbeat is used to indicate that the node is functioning normally. In some embodiments, a predetermined interval for the node to provide a heartbeat is determined based on message 205 or message 215. In some embodiments, the predetermined interval for the node to provide a heartbeat is determined by NRF 120 and assigned to the node during node information registration or update; and the interval is notified to the node via message 210 or message 220. In response to NRF 120 failing to receive a heartbeat signal from the node within the predetermined interval, heartbeat TO 235 is determined. In this case, the node is determined to be faulty, and the node's state is updated in NRF 120 to indicate that the node should be transferred to AMF 110 for connection to the UE. In some embodiments, in response to determining heartbeat TO 235, the node's state is changed to suspended. In some embodiments, the node remains in a faulty state until NRF 120 receives a heartbeat from the node. In some embodiments, the node remains in a fault state until the NRF 120 receives update information for the node, for example, using message 215. In some embodiments, the node remains in a fault state until the NRF 120 receives a new registration request from the node, for example, using message 210.

[0035] In scenario 240, NRF 120 receives an update request indicating that a node is blocked. In message 242, SMF+PGW-C160 sends an NF update request to NRF 120. Similar to message 215, the NF update request provides NRF 120 with update information about the node. In the case of message 242, the node's update status is indicated as blocked. That is, the node is currently unable to facilitate the UE (e.g., UE 102). Figure 1 The connection between the node and the network. In some embodiments, message 242 is automatically sent by the SMF+PGW-C 160 in response to a node losing power, a software failure, or other suitable changes to the node. In some embodiments, message 242 is sent in response to the SMF+PGW-C 160 receiving an instruction from the network operator.

[0036] In response to receive message 242, in operation 244, NRF 120 updates the node's state to faulty. In some embodiments, the node's state is updated to paused or undiscoverable.

[0037] In message 246, NRF 120 sends an NF update response to SMF+PGW-C 160. The NF update response informs SMF+PGW-C 160 about whether the node has been correctly updated in NRF 120. In some embodiments, message 246 includes an acknowledgment of the request and an indication of a successful update. In some embodiments where the update is unsuccessful, message 246 includes information such as an error code indicating the reason for the node update failure. In some embodiments, message 246 also includes information indicating the update status of the node in NRF 120.

[0038] In scenario 250, NRF 120 receives a deregistration request instructing that the node should be removed from the NRF 120 list of available nodes. In message 252, SMF+PGW-C 160 sends an NF deregistration request to NRF 120. The NF deregistration request includes information for removing the node from NRF 120. In some embodiments, message 252 is sent in response to a replacement of the hardware associated with the node. In some embodiments, message 252 is sent in response to assigning the node's functionality to another purpose.

[0039] In response to receive message 252, in operation 254, NRF 120 transfers the node from, for example, UE 102 ( Figure 1 The node is removed from the list of possible nodes for the UE to connect to. In contrast to operation 244 (where the node's state is updated to prevent attempts to connect to the node), operation 254 completely removes the node from the NRF 120 as an option for connecting to the UE. In some embodiments, message 252 is automatically sent by the SMF+PGW-C 160 in response to the node being removed from the network, reassigned within the network, or other suitable changes to the node. In some embodiments, message 252 is sent in response to the SMF+PGW-C 160 receiving instructions from the network operator.

[0040] In message 256, NRF 120 sends an NF deregistration response to SMF+PGW-C 160. The NF deregistration response informs SMF+PGW-C 160 whether the node has been correctly removed from NRF 120. In some embodiments, message 256 includes an acknowledgment of the request and an indication of successful deregistration. In some embodiments where deregistration is unsuccessful, message 256 includes information indicating the reason for the node deregistration failure, such as an error code.

[0041] Those skilled in the art will understand that scenarios 230, 240, and 250 are not necessarily required. In some embodiments, none of scenarios 230, 240, or 250 occur. For simplicity and ease of understanding of instances used to change the state of a node in NRF 120 and / or remove a registered node from NRF 120, various scenarios 230, 240, and 250 are shown in a single communication 200. Utilizing registration, updates, and the possible occurrence of any of scenarios 230, 240, and 250, NRF 120 is able to generate and maintain connections for UEs (such as UE 102). Figure 1 The list of available nodes, and the status of each node that allows the AMF 110 to attempt to connect the UE to that node.

[0042] In message 260, AMF 110 sends an NF discovery request to NRF 120. The NF discovery request requests information from NRF 120 regarding which nodes in the network are associated with, and the status of each node. In some embodiments, in response to AMF 110 receiving information from, for example, UE 102 (… Figure 1 When a UE receives a connection request, message 260 is automatically sent. In some embodiments, message 260 is sent periodically to allow the AMF 110 to maintain an up-to-date list of available nodes, facilitating faster connection for the UE in future connection requests. In some embodiments, message 260 is sent in response to the AMF 110 receiving instructions from the network operator (such as in response to hardware or software updates to a base station, data center, or cluster; restoration of power to a base station, data center, or cluster; or other suitable events).

[0043] In message 265, NRF 120 sends an NF discovery response to AMF 110. The NF discovery response informs AMF 110 about which nodes are available and the current status of each node stored in NRF 120. In some embodiments, message 265 includes an acknowledgment of the request and node information. In some embodiments where the discovery request is unsuccessful, message 265 includes information indicating the reason for the discovery request failure, such as an error code.

[0044] Using communication 200, AMF 110 can accurately and precisely determine which nodes are available to be assigned to UEs, such as UE 102 ( Figure 1 This allows the AMF 110 to provide the UE with accurate data for connecting to the network. The increased accuracy of the data provided to the UE increases the likelihood of the UE successfully and reliably connecting to the network, and helps maintain user satisfaction with the network.

[0045] Figure 3This is a sequence diagram of communication 300 between components of a multi-generation network device according to some embodiments. Communication 300 occurs between DNS 140 and NRF 120, and between DNS 140 and MME 130. Although the reference numerals refer to multi-generation network device 100 (… Figure 1 The components of the communication 300 are not limited to the multi-generation network device 100, but those skilled in the art will understand that the features of the communication 300 are not limited to those of the multi-generation network device 100. Figure 1 In some embodiments, messages of communication 300 are transmitted via a wired connection. In some embodiments, at least one message of communication 300 is transmitted wirelessly.

[0046] In message 305, DNS 140 sends an NF state subscription to NRF 120. The NF state subscription is used to register DNS 140 with NRF 120, enabling NRF 120 to notify DNS 140 in response to changes in node availability within the network. Node availability within the network changes based on node registration, node deregistration, changes in node state, or other suitable events. In some embodiments, message 305 includes a request for periodic updates, regardless of node state changes, to help DNS 140 maintain an accurate list of available nodes. In some embodiments, message 305 is automatically sent by DNS 140 in response to DNS 140 being added to a base station, data center, or cluster. In some embodiments, message 305 is sent in response to DNS 140 receiving an instruction from a network operator.

[0047] In message 310, NRF 120 sends an NF subscription response to DNS 140. The NF subscription response informs DNS 140 whether DNS 140 has correctly subscribed to the information in NRF 120. In some embodiments, message 310 includes an acknowledgment of the request and an indication of a successful subscription. In some embodiments where the subscription is unsuccessful, message 310 includes information indicating the reason for the DNS 140's subscription failure, such as an error code.

[0048] In operation 315, the NF state of at least one node in the node list of NRF 120 changes. In some embodiments, the state of at least one node changes due to scenarios 230, 240, and 250 ( Figure 2 The state of at least one node changes as a new node is registered in the NRF 120.

[0049] In response to NF state change 235, message 320 is sent from NRF 120 to DNS 140. The NF state update provides updated information about the node stored in NRF 120. In some embodiments, the updated information includes information related to the node's functionality. In some embodiments, the updated information includes information related to the node's updated address. In some embodiments, the updated information includes information related to the node's updated state. In some embodiments, message 320 is automatically sent by NRF 120 in response to operation 315. In some embodiments, message 320 is sent in response to NRF 120 receiving an instruction from a network operator.

[0050] In operation 325, the notification from message 320 is stored in DNS 140. In some embodiments, DNS 140 stores a list of accessible nodes and updates the list based on the information received in message 320. With the updated list of available nodes, DNS 140 can accurately notify MME 130 of nodes available for connection to the UE (e.g., UE 102). Figure 1 In some embodiments, DNS 140 stores a list of nodes connected to the network; and updates an exclusion list of nodes in a faulty state in response to message 320. Through the combination of the list and the exclusion list, DNS 140 can accurately inform MME 130 which nodes are currently available to connect to the UE, for example, UE 102 (…). Figure 1 As described above, unlike NRF 120, DNS 140 stores only a list of nodes, not the states of the nodes. Therefore, in some embodiments, during operation 325, the list of available nodes in DNS 140 is updated to remove any faulty nodes, such as those in a suspended or undiscoverable state. Alternatively, in some embodiments, during operation 325, the list of excluded nodes in DNS 140 is updated to include any faulty nodes, such as those in a suspended or undiscoverable state. By updating the list of available nodes and / or the list of excluded nodes, DNS 140 reduces the likelihood of providing the MME 130 with nodes that are currently unable to connect to the UE (such as UE 102). Figure 1 The risk of potential connected nodes.

[0051] In message 330, DNS 140 sends an NF update confirmation to NRF 120. The NF update confirmation notifies NRF 120 whether the node's information is correctly stored in DNS 140. In some embodiments, message 330 includes an acknowledgment of the request and an indication of a successful update. In some embodiments where the update is unsuccessful, message 330 includes information indicating the reasons for the update failure, such as an error code.

[0052] In message 335, MME 130 sends a DNS query to DNS 140. The DNS query request is sent by MME 130 to the UE (e.g., UE 102). Figure 1 The system provides a list of nodes for connecting the UE to the network. In some embodiments, in response to the MME 130, nodes such as UE102 (…) are provided. Figure 1 When a UE receives a connection request, message 335 is automatically sent. In some embodiments, message 335 is sent periodically to allow the MME 130 to maintain an up-to-date list of available nodes, facilitating faster connection for the UE in future connection requests. In some embodiments, message 335 is sent in response to the MME 130 receiving instructions from the network operator (such as, in response to hardware or software updates to a base station, data center, or cluster; restoring power to a base station, data center, or cluster; or other suitable events).

[0053] In operation 340, DNS 140 retrieves an exclusion list or a list of available nodes. As described above, in some embodiments, DNS 140 maintains an exclusion list indicating which nodes are in a faulty state. This exclusion list can be used to notify MME 130 which nodes should avoid attempting to communicate with the UE (e.g., UE 102). Figure 1 In some embodiments, DNS 140 maintains a list of connectable nodes, which can be used to inform MME 130 about which UE (e.g., UE 102) should attempt to connect. Figure 1 Which nodes to connect to. Compared to other methods, any type of list helps increase the likelihood of successfully establishing a connection between the UE and the nodes.

[0054] In message 345, DNS 140 sends a DNS response to MME 130. The DNS response informs MME 130 which nodes are available for connection. In some embodiments, message 345 includes an acknowledgment of the request and a list of nodes. In some embodiments where the query is unsuccessful, message 345 includes information indicating the reason for the query failure, such as an error code.

[0055] Using communication 300, MME 130 can accurately and precisely determine which nodes can be used for allocation to UEs, such as UE 102 ( Figure 1This allows the MME 130 to provide the UE with accurate data for connecting to the network. Increased accuracy of the data provided to the UE increases the likelihood of a successful and reliable network connection, and helps maintain user satisfaction with the network. Furthermore, the ability to automatically transmit node information between the NRF 120 and DNS 140 helps avoid reliance on manual updates to the lists in DNS 140 compared to other methods. Other methods, including manual updates to the lists in DNS 140, carry an increased risk of user dissatisfaction due to the increased risk of inaccurate or outdated information in the lists. For example, in the event of a node going offline or failing, such as due to a power outage, the network operator may be assigned the task of restoring the node to correct operation. Therefore, the network operator faces an increased risk of delaying updates to the lists in DNS 140, which in turn increases the likelihood that the MME 130 will attempt to connect the UE to the failed node. Moreover, the risk of the network operator incorrectly entering data into the lists in DNS 140 is higher than with automatic updates of the lists performed using communication 300.

[0056] Figure 4 This is a sequence diagram of communication 400 between components of a multi-generation network device according to some embodiments. Communication 400 occurs between the integrated DNS+NRF 410 and MME 130. Although the reference numerals refer to multi-generation network device 100 ( Figure 1 The components of the communication 400 are not limited to the multi-generation network device 100, but those skilled in the art will understand that the features of the communication 400 are not limited to the multi-generation network device 100. Figure 1 ). with Communication 300 ( Figure 3 In contrast, Communication 400 utilizes integrated DNS and NRF. That is, the DNS 140 and NRF 120 of Communication 300 are implemented in a single device. The processing and storage of information within a single DNS+NRF 410 is similar to that described above regarding Communication 300. Figure 3 As discussed herein; however, messages are not transmitted between individual devices. In some embodiments, messages of communication 400 are sent via a wired connection. In some embodiments, at least one message of communication 400 is sent wirelessly.

[0057] In message 435, MME 130 sends a DNS query to DNS+NRF 410. The DNS query request is sent by MME 130 to the UE (e.g., UE 102). Figure 1 The system provides a list of nodes for connecting the UE to the network. In some embodiments, in response to the MME 130, nodes such as UE 102 (…) are used to connect the UE to the network. Figure 1When a UE receives a connection request, message 435 is automatically sent. In some embodiments, message 435 is sent periodically to allow the MME 130 to maintain an up-to-date list of available nodes, facilitating faster connection for the UE in future connection requests. In some embodiments, message 435 is sent in response to the MME 130 receiving instructions from the network operator (such as in response to hardware or software updates to a base station, data center, or cluster; restoring power to a base station, data center, or cluster; or other suitable events).

[0058] In operation 440, DNS+NRF 410 retrieves an exclusion list or a list of available nodes. In some embodiments, DNS+NRF 410 maintains an exclusion list indicating which nodes are in a faulty state. This exclusion list can be used to notify MME 130 which nodes should avoid attempting to communicate with the UE (e.g., UE 102). Figure 1 In some embodiments, the DNS+NRF 410 maintains a list of connectable nodes, which can be used to inform the MME 130 about which nodes the MME 130 should attempt to connect to the UE (e.g., UE 102). Figure 1 Which nodes to connect to. Compared to other methods, any type of list helps increase the likelihood of successfully establishing a connection between the UE and the nodes.

[0059] In message 445, DNS+NRF 410 sends a DNS response to MME 130. The DNS response informs MME 130 which nodes are available for connection. In some embodiments, message 445 includes an acknowledgment of the request and a list of nodes. In some embodiments where the query is unsuccessful, message 445 includes information indicating the reason for the query failure, such as an error code.

[0060] Using communication 400, the MME 130 can accurately and precisely determine which nodes are available for allocation to UEs, such as UE 102 ( Figure 1 This allows the MME 130 to provide the UE with accurate data for connecting to the network. Improved accuracy of the data provided to the UE increases the likelihood of a successful and reliable network connection and helps maintain user satisfaction with the network. Furthermore, the ability to automatically process and store information in the DNS+NRF 410, compared to other methods, helps avoid relying on manual updates to the lists in the DNS 140. Other methods, including manual updates to the lists in the DNS, carry an increased risk of user dissatisfaction, as mentioned above, due to the increased risk of inaccurate or outdated information in the lists within the DNS.

[0061] Figure 5This is a flowchart of a method 500 for selecting a node to connect to a user equipment (UE) according to some embodiments. For clarity, the following description refers to a multi-generation network device 100 ( Figure 1 ), Communication 200 ( Figure 2 ), Communication 300 ( Figure 3 ), or communication 400 ( Figure 4 The accompanying drawings are referenced by the numerals 100. However, those skilled in the art will understand that method 500 is not limited to these examples. In some embodiments, a multi-generation network device 100 is used. Figure 1 ) or System 600 ( Figure 6 This implements at least a portion of method 500. In some embodiments, a multi-generation network device 100 is used ( Figure 1 ) or system ( Figure 6 Method 500 is implemented by one or more devices other than communication 200. In some embodiments, communication 200 is used to implement method 500. Figure 2 ), Communication 300 ( Figure 3 ), or communication 400 ( Figure 4 This implements at least a portion of method 500. In some embodiments, communication 200 is used in addition to... Figure 2 ), Communication 300 ( Figure 3 ), or communication 400 ( Figure 4 Method 500 is implemented through communication processes other than those described above.

[0062] In operation 505, node accessibility is determined. Node accessibility includes information related to the node's status in accepting UE connections. In some embodiments, this is based on node registration, for example, using message 205 ( Figure 2 ) to determine node accessibility. In some embodiments, this is based on updated information about the node, for example, using message 215 ( Figure 2 ) to determine node accessibility. In some embodiments, based on scenario 230, 240, or 250 ( Figure 2 Node accessibility is determined based on one or more of the following: NRF 120 (…). In some embodiments, accessibility is determined based on data received from the network operator to the NRF 120 (…). Figure 1 The input is used to determine the node's accessibility.

[0063] In Operation 510, node accessibility is stored in NRF 120 ( Figure 1 In ) NRF 120 ( Figure 1 ) stores node information and node status, indicating whether the node can access and connect to the UE (e.g., UE 102 ( Figure 1 In some embodiments, the state is stored in memory, such as memory 640. Figure 6 In some embodiments, operation 510 includes updating the data stored in the NRF 120 (…).Figure 1 The state of the nodes in ). In some embodiments, operation 510 includes, for example, due to scenario 250 ( Figure 2 And remove the storage stored in NRF 120 ( Figure 1 ) nodes.

[0064] In Operation 515, node accessibility is communicated to DNS 140 ( Figure 1 In some embodiments, communication 300 is used. Figure 3 The message described conveys node accessibility to DNS 140 ( Figure 1 In some embodiments, operation 515 is omitted. In some embodiments, when DNS 140 ( Figure 1 ) and NRF 120 ( Figure 1 It is integrated into systems such as DNS+NRF 410 ( Figure 4 When in a single device, operation 515 is omitted.

[0065] In Operation 520, node accessibility is used in DNS 140 ( Figure 1 The information is stored or updated using a list stored in the ). In some embodiments, communication 300 ( Figure 3 To achieve DNS 140 ( Figure 1 The storage or update of the list in ). In some embodiments, operation 520 is omitted. In some embodiments, when DNS 140 ( Figure 1 ) and NRF 120 ( Figure 1 It is integrated into systems such as DNS+NRF 410 ( Figure 4 In a single device, operation 520 is omitted. In some embodiments where DNS+NRF 410 is used, operation 520 is combined with operation 510.

[0066] In operation 525, a connection request is received from the UE. (e.g., UE 102) Figure 1 Based on the technology used by the UE to communicate with the network, AMF 110 ( Figure 1 ) or MME 130 ( Figure 1 The UE provides a connection request. In some embodiments, the UE uses 5G to communicate with the network, and is powered by the AMF 110 ( Figure 1 The AMF 110 receives a connection request. In response to the connection request, the AMF 110 utilizes the NRF 120 ( Figure 1 The AMF 110 receives information to determine which nodes are available for connection with the UE. In some embodiments, the AMF 110 uses communication 200 ( Figure 2 This determines which nodes are available for connection with the UE.

[0067] In some embodiments, the UE uses 4G to communicate with the network, and is powered by the MME 130 ( Figure 1 The MME 130 receives connection requests. In response to the connection request, the MME 130 utilizes DNS 140 ( Figure 1 The MME 130 receives information to determine which nodes are available for connection with the UE. In some embodiments, the MME 130 uses communication 300 ( Figure 3 ) or communication 400 ( Figure 4 This determines which nodes are available for connection with the UE.

[0068] In operation 530, connection information is provided to the UE. In some embodiments, the connection information is provided by MME 130 ( Figure 1 ) or AMF 110 ( Figure 1 ) is provided to the UE, for example, UE 102 ( Figure 1 In some embodiments, based on NRF 120 ( Figure 1 The information received from DNS 140 provides connection information to the UE. In some embodiments, this is based on the information received from DNS 140. Figure 1 The received information provides connection information to the UE.

[0069] Those skilled in the art will understand that modifications to method 500 are within the scope of this specification. In some embodiments, at least one operation is added to method 500. For example, in some embodiments, method 500 further includes adding a new node to the network. In some embodiments, at least one operation is omitted from method 500. For example, in some embodiments, operation 515 is omitted from method 500. In some embodiments, the order of operations of method 500 is adjusted. For example, in some embodiments, operations 510 and 520 are performed simultaneously.

[0070] Figure 6 This is a block diagram of a system 600 for selecting a node to connect to a UE, according to some embodiments. System 600 includes a hardware processor 602 and a non-transitory computer-readable storage medium 604 encoded (i.e., stored) with computer program code 606 (i.e., a set of executable instructions). The computer-readable storage medium 604 also encodes instructions 607 for interfacing with external devices. Processor 602 is electrically coupled to computer-readable storage medium 604 via bus 608. Processor 602 is also electrically coupled to input / output (I / O) interface 610 via bus 608. Network interface 612 is also electrically connected to processor 602 via bus 608. Network interface 612 is connected to network 614, enabling processor 602 and computer-readable storage medium 604 to be connected to external components via network 614. Processor 602 is configured to execute the computer program code 606 encoded in computer-readable storage medium 604, so that system 600 can be used to perform operations such as those in multi-generation network device 100 (…).Figure 1 ), Communication 200 ( Figure 2 ), Communication 300 ( Figure 3 ), Communication 400 ( Figure 4 ), or method 500 ( Figure 5 Some or all of the operations described in ).

[0071] In some embodiments, processor 602 is a central processing unit (CPU), a multiprocessor, a distributed processing system, an application-specific integrated circuit (ASIC), and / or a suitable processing unit.

[0072] In some embodiments, computer-readable storage medium 604 is an electrical, magnetic, optical, electromagnetic, infrared, and / or semiconductor system (or apparatus or device). For example, computer-readable storage medium 504 includes semiconductor or solid-state memory, magnetic tape, removable computer disk, random access memory (RAM), read-only memory (ROM), hard disk, and / or optical disk. In some embodiments using optical disk, computer-readable storage medium 604 includes optical disc read-only memory (CD-ROM), optical disc read / write (CD-R / W), and / or digital video disc (DVD).

[0073] In some embodiments, storage medium 604 is configured to cause system 600 to perform operations as in multigenerational network device 100 ( Figure 1 ), Communication 200 ( Figure 2 ), Communication 300 ( Figure 3 ), Communication 400 ( Figure 4 ), or method 500 ( Figure 5 Part or all of the computer program code 606 described in the document. In some embodiments, storage medium 604 also stores some or all of the computer program code 606 for performing operations as described in multi-generation network device 100. Figure 1 ), Communication 200 ( Figure 2 ), Communication 300 ( Figure 3 ), Communication 400 ( Figure 4 ), or method 500 ( Figure 5 Information on some or all of the operations described in the document, as well as information on the execution of operations such as those in multi-generation network device 100 ( Figure 1 ), Communication 200 ( Figure 2 ), Communication 300 ( Figure 3 ), Communication 400 ( Figure 4 ), or method 500 ( Figure 5 Information generated during part or all of the operations described in the document, such as NF status parameter 616, and exclusion list parameter 618, and / or information used to perform operations such as in multi-generation network device 100 ( Figure 1 ), Communication 200 ( Figure 2 ), Communication 300 ( Figure 3 ), Communication 400 (Figure 4 ), or method 500 ( Figure 5 The set of executable instructions for some or all of the operations described in ().

[0074] In some embodiments, storage medium 604 stores instructions 607 for interfacing with external devices. Instructions 607 enable processor 602 to generate instructions that can be read by external devices to efficiently implement, as in multi-generation network device 100 (… Figure 1 ), Communication 200 ( Figure 2 ), Communication 300 ( Figure 3 ), Communication 400 ( Figure 4 ), or method 500 ( Figure 5 Some or all of the operations described in ().

[0075] System 600 includes an I / O interface 610. The I / O interface 610 is coupled to external circuitry. In some embodiments, the I / O interface 610 includes a keyboard, keypad, mouse, trackball, trackpad, and / or cursor arrow keys for transmitting information and commands to processor 602.

[0076] System 600 also includes a network interface 612 coupled to processor 602. Network interface 612 allows system 600 to communicate with a network 614 connected to one or more other computer systems. Network interface 612 includes a wireless network interface such as BLUETOOTH, WIFI, WIMAX, GPRS, or WCDMA; or a wired network interface such as ETHERNET, USB, or IEEE-1394. In some embodiments, such as in multi-generation network device 100 (… Figure 1 ), Communication 200 ( Figure 2 ), Communication 300 ( Figure 3 ), Communication 400 ( Figure 4 ), or method 500 ( Figure 5 Some or all of the operations described in the document are implemented in two or more systems 600, and information such as NF status parameter 616 or exclusion list 618 is exchanged between different systems 600 via network 614.

[0077] The above description refers to SMF+PGW-C 160 ( Figure 1 This is considered as a node. However, those skilled in the art will recognize that this description is not limited to using only the SMF+PGW-C 160 as a node. In some embodiments, the AMF 110 can be used as a node. For example, during the 4G to 5G handover process, communication 200 ( Figure 2 ), Communication 300 ( Figure 3 ) and / or communication 400 ( Figure 4 ) can be used to update information about available AMF 110 ( Figure 5MME 130 ( Figure 1 ), used to establish UE (e.g., UE 102 ( Figure 2 The connection between the AMF 110 and the AMF 110. Those skilled in the art will understand that the above description can be modified to include the AMF 110 as a node. Figure 3 This will include sending to NRF 120 ( Figure 4 Register AMF 110, and similar to communication 300 ( Figure 5 ) and / or communication 400 ( Figure 1 The method described in ) to DNS 140 ( Figure 2 Figure 3 Figure 4 Figure 5 Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 1 Figure 2 Figure It conveys status information about one or more AMF 110s.

[0078] Supplementary Note 1

[0079] A method for identifying accessible nodes for a wireless network, the method comprising: storing a first list of nodes in a first device, wherein the first list includes a corresponding state for each node in the first list, and the first device is available in a first technology generation of the wireless network. The method further comprises updating a second list of nodes in a second device based on the first list of nodes, wherein the second list does not contain the state of each node in the second list, and the second device is available in a second technology generation of the wireless network, the second technology generation being different from the first technology generation. The method further comprises providing connection information for nodes in the second list of nodes to a user equipment in response to receiving a connection request from a user equipment.

[0080] Supplementary Note 2

[0081] According to the method in Supplementary Note 1, the first technology generation includes the fifth generation (5G), and the second technology generation includes the fourth generation (4G).

[0082] Supplementary Note 3

[0083] According to the method in Supplementary Note 1, updating the second list includes: in response to the first list indicating that the state of a node is faulty, removing the node from the second list.

[0084] Supplementary Note 4

[0085] According to the method in Supplementary Note 1, updating the second list includes: adding the node to the second list in response to the first list indicating that the node's status is accessible and the node is not in the second list.

[0086] Supplementary Note 5

[0087] According to the method in Supplementary Explanation 1, the first device and the second device are separate.

[0088] Supplementary Note 6

[0089] According to the method in Supplementary Explanation 1, the first device is integrated with the second device.

[0090] Supplementary Note 7

[0091] According to the method in Supplementary Note 1, the first device includes a network storage function (NRF), and the second device includes a domain name system (DNS).

[0092] Supplementary Note 8

[0093] A system for identifying accessible nodes for a wireless network, the system comprising: a non-transitory computer-readable medium configured to store instructions thereon. The system further comprises a processor connected to the non-transitory computer-readable medium. The processor is configured to execute instructions to instruct the non-transitory computer-readable medium to store a first list of nodes in a first device, wherein the first list includes: a corresponding state of each node in the first list, and the first device is available in a first technology generation of the wireless network. The processor is further configured to execute instructions to update a second list of nodes in a second device based on the first list of nodes, wherein the second list does not contain the state of each node in the second list, and the second device is available in a second technology generation of the wireless network, the second technology generation being different from the first technology generation. The processor is also configured to execute instructions to provide connection information for nodes in the second list of nodes to a user equipment in response to receiving a connection request from a user equipment.

[0094] Supplementary Note 9

[0095] According to Supplementary Note 8, the first technology generation includes the fifth generation (5G), and the second technology generation includes the fourth generation (4G).

[0096] Supplementary Note 10

[0097] According to Supplementary Note 8, the system in which the processor is configured to execute instructions to update the second list by removing the node from the second list in response to the first list indicating that the node's state is faulty.

[0098] Supplementary Note 11

[0099] According to Supplementary Note 8, the system wherein the processor is configured to execute instructions to update the second list by adding the node to the second list in response to the first list indicating that the node's status is accessible and the node is not in the second list.

[0100] Supplementary Note 12

[0101] According to Supplementary Note 8, the first device and the second device are separate.

[0102] Supplementary Note 13

[0103] According to the method in Supplementary Explanation 8, the first device is integrated with the second device.

[0104] Supplementary Note 14

[0105] According to the method in Supplementary Note 8, the first device includes a network storage function (NRF), and the second device includes a domain name system (DNS).

[0106] Supplementary Note 15

[0107] A non-transitory computer-readable medium is configured to store instructions thereon for causing a processor to: instruct the non-transitory computer-readable medium to store a first list of nodes in a first device, wherein the first list includes: a corresponding state of each node in the first list, and the first device is available in a first technology generation of a wireless network. The instructions are also configured to cause the processor to: update a second list of nodes in a second device based on the first list of nodes, wherein the second list does not contain the state of each node in the second list, and the second device is available in a second technology generation of a wireless network, different from the first technology generation. The instructions are further configured to cause the processor to: in response to receiving a connection request from a user equipment, provide the user equipment with connection information for nodes in the second list of nodes.

[0108] Supplementary Note 16

[0109] According to Supplementary Note 15, the non-transitory computer-readable medium includes a first technology generation including the fifth generation (5G) and a second technology generation including the fourth generation (4G).

[0110] Supplementary Note 17

[0111] According to the non-transitory computer-readable medium of Supplementary Note 15, the instructions are also configured to cause the processor to update the second list by removing the node from the second list in response to the first list indicating that the node's state is faulty.

[0112] Supplementary Note 18

[0113] According to the non-transitory computer-readable medium of Supplementary Note 15, the instructions are further configured to cause the processor to update the second list by adding the node to the second list in response to the first list indicating that the node's status is accessible and the node is not in the second list.

[0114] Supplementary Note 19

[0115] According to Supplementary Note 15, the non-transitory computer-readable medium in which the first device and the second device are separate.

[0116] Supplementary Note 20

[0117] According to Supplementary Note 15, the non-transitory computer-readable medium wherein the first device is integrated with the second device.

[0118] The foregoing has outlined features of several embodiments to enable those skilled in the art to better understand aspects of this disclosure. Those skilled in the art will understand that this disclosure can be readily used as a basis for designing or modifying other processes and structures for achieving the same purposes and / or advantages of the embodiments described herein. Those skilled in the art will also recognize that such equivalent constructions do not depart from the spirit and scope of this disclosure, and that various changes, substitutions, and modifications can be made herein without departing from the spirit and scope of this disclosure.

Claims

1. A method for identifying an accessible node for a wireless network, the method comprising: A first list of nodes is stored in a first device, wherein the first list includes: the corresponding state of each node in the first list, and the first device is available in a first technology generation of the wireless network; The second list of nodes in the second device is updated based on the first list of nodes, wherein the second list does not contain the state of each node in the second list, and the second device is available in a second technology generation of the wireless network, which is different from the first technology generation; and In response to receiving a connection request from a user equipment, the user equipment is provided with connection information for nodes in the second list of nodes.

2. The method according to claim 1, wherein the first technology generation includes the fifth generation (5G), and the second technology generation includes the fourth generation (4G).

3. The method of claim 1, wherein updating the second list comprises: In response to the first list indicating that a node's status is faulty, the node is removed from the second list.

4. The method of claim 1, wherein updating the second list comprises: In response to the first list indicating that the node's status is accessible and the node is not in the second list, the node is added to the second list.

5. The method of claim 1, wherein the first device and the second device are separate.

6. The method of claim 1, wherein the first device is integrated with the second device.

7. The method of claim 1, wherein the first device includes a network storage function (NRF) and the second device includes a domain name system (DNS).

8. A system for identifying an accessible node for a wireless network, the system comprising: A non-transitory computer-readable medium configured to store instructions thereon; as well as A processor connected to the non-transitory computer-readable medium, wherein the processor is configured to execute the instructions for: The non-transitory computer-readable medium is instructed to store a first list of nodes in a first device, wherein the first list includes: a corresponding state of each node in the first list, and the first device is available in a first technology generation of the wireless network; The second list of nodes in the second device is updated based on the first list of nodes, wherein the second list does not contain the state of each node in the second list, and the second device is available in a second technology generation of the wireless network, which is different from the first technology generation; and In response to receiving a connection request from a user equipment, the user equipment is provided with connection information for nodes in the second list of nodes.

9. The system of claim 8, wherein the first technology generation includes the fifth generation (5G) and the second technology generation includes the fourth generation (4G).

10. The system of claim 8, wherein the processor is configured to execute the instructions to update the second list by removing the node from the second list in response to the first list indicating that the node's state is faulty.

11. The system of claim 8, wherein the processor is configured to execute the instructions to update the second list by adding the node to the second list in response to the first list indicating that the node's state is accessible and the node is not in the second list.

12. The system of claim 8, wherein the first device and the second device are separate.

13. The system of claim 8, wherein the first device is integrated with the second device.

14. The system of claim 8, wherein the first device includes a network storage function (NRF) and the second device includes a domain name system (DNS).

15. A non-transitory computer-readable medium configured to store instructions thereon for causing a processor to: The non-transitory computer-readable medium indicates a first list of nodes stored in the first device, wherein the first list includes: The corresponding status of each node in the first list, and the availability of the first device in the first technology generation of the wireless network; The second list of nodes in the second device is updated based on the first list of nodes, wherein the second list does not contain the state of each node in the second list, and the second device is available in a second technology generation of the wireless network, which is different from the first technology generation; as well as In response to receiving a connection request from a user equipment, the user equipment is provided with connection information for nodes in the second list of nodes.

16. The non-transitory computer-readable medium of claim 15, wherein the first technology generation includes the fifth generation (5G) and the second technology generation includes the fourth generation (4G).

17. The non-transitory computer-readable medium of claim 15, wherein the instructions are further configured to cause the processor to update the second list by removing the node from the second list in response to the first list indicating that the node's state is faulty.

18. The non-transitory computer-readable medium of claim 15, wherein the instructions are further configured to cause the processor to update the second list by adding the node to the second list in response to the first list indicating that the node's state is accessible and the node is not in the second list.

19. The non-transitory computer-readable medium of claim 15, wherein the first device and the second device are separate.

20. The non-transitory computer-readable medium of claim 15, wherein the first device is integrated with the second device.

Images