Configuration of fixed radio access deployments

Abstract

The invention relates to configuration of fixed radio access (FWA) deployments. A distribution point unit (DPU) is associated with an FWA deployment. The DPU identifies configuration information indicating respective correspondences between a plurality of ports of the DPU and address identifiers of a plurality of access point devices. The DPU determines that a plurality of ports of the DPU are connected to the plurality of access point devices, and performs an authentication operation to determine that the plurality of access point devices are connected to the plurality of ports according to the configuration information. The DPU obtains respective Internet Protocol (IP) addresses associated with the plurality of access point devices based on the configuration information. The DPU sends respective IP addresses to the plurality of access point devices via respective connections between the plurality of ports of the DPU and the plurality of access point devices.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to Indian Patent Application No. 202441016233 filed on March 7, 2024, entitled “Optimal Fixed Wireless Access (FWA) Deployments”. The disclosure of that prior application is considered a part of this patent application and is incorporated herein by reference. Technical Field

[0003] The present disclosure relates to the field of communications, and more particularly to configuration of fixed wireless access deployments. Background Art

[0004] Fixed wireless access (FWA) provides wireless broadband connectivity between two fixed points (e.g., between a network base station and an FWA device in a customer's home). FWA uses radio waves to send high-speed signals that provide data transmission to and from consumer devices (e.g., user equipment). Summary of the Invention

[0005] In some implementations, a distribution point unit (DPU) associated with an FWA deployment includes one or more memories; and one or more processors for: identifying configuration information indicating corresponding correspondences between multiple ports of the DPU and address identifiers of multiple access point devices; obtaining corresponding Internet Protocol (IP) addresses associated with the multiple access point devices based on the configuration information; and sending the corresponding IP addresses to the multiple access point devices via corresponding connections between the multiple ports of the DPU and the multiple access point devices.

[0006] In some implementations, a non-transitory computer-readable medium stores an instruction set comprising one or more instructions that, when executed by one or more processors of a DPU associated with an FWA deployment, causes the DPU to: identify configuration information indicating respective correspondences between multiple ports of the DPU and address identifiers of multiple access point devices; determine that the multiple ports of the DPU are connected to multiple access point devices; and perform a verification operation to determine, based on the configuration information, that the multiple access point devices are connected to the multiple ports.

[0007] In some implementations, a method includes obtaining, by a distribution point unit (DPU) associated with a fixed wireless access (FWA) deployment, respective Internet Protocol (IP) addresses associated with a plurality of access point devices connected to a plurality of ports of the DPU; and sending, by the DPU, the respective IP addresses to the plurality of access point devices via respective connections between the plurality of ports of the DPU and the plurality of access point devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1A-1E is a diagram of an example implementation associated with a configuration of a FWA deployment;

[0009] Figure 2 is a diagram of an example environment in which the systems and / or methods described herein may be implemented;

[0010] Figure 3 is a diagram of example components of equipment associated with a configuration of a FWA deployment;

[0011] Figure 4 is a diagram of example components of equipment associated with a configuration of a FWA deployment; and

[0012] Figure 5 is a flow diagram of an example process associated with configuration of a FWA deployment. DETAILED DESCRIPTION

[0013] The following detailed description of example implementations refers to the accompanying drawings, in which the same reference numerals in different drawings may identify the same or similar elements.

[0014] In FWA deployments, such as with multi-dwelling units (MDUs), multiple customer premises equipment (CPEs) are each associated with a dwelling of the MDU, and connections can be established between a wireless network (e.g., a core network) and the devices associated with the dwellings. In some cases, the CPEs can also provide physical layer terminations in broadband deployments (e.g., utilizing passive optical network (PON) technology or Data over Cable System Interface Specification (DOCSIS) technology). In addition, the CPEs (e.g., when provided and / or controlled by an operator of the broadband deployment) can be remotely managed (e.g., using proprietary methods and / or methods defined in Broadband Forum (BBF) Technical Report 069 (TR-069)).

[0015] In many cases, in FWA deployments, each CPE is connected to an access point device (AP) at a premises (e.g., a network device including a wired and / or wireless router, such as a WiFi router) and is configured to provide Internet services to the premises, such as for a local area network (LAN) at the premises. However, both the CPE and the AP typically apply network address translation (NAT) and network address and port translation (NAPT) to data packets traversing the device, which can increase the latency associated with data packets traversing the device (e.g., due to repeated translation processes and / or the need for an application layer gateway (ALG) to assist in the translation process).

[0016] Furthermore, in an FWA deployment, multiple CPEs are connected to a DPU, which is connected to an FWA gateway (FWA-GW) (e.g., an FWA resident gateway or a similar type of FWA device), which provides wireless connectivity, such as via a radio link, between the DPU and the RAN associated with the core network. This enables communication between multiple APs and the core network. Thus, the DPU is configured (e.g., as a layer 2 switch) to aggregate traffic to and from the resident APs of the MDUs. However, it is worth noting that in order for the AP to communicate with the core network, the traffic must pass between the AP and the FWA-GW via both the DPU and the corresponding CPE (e.g., configured to provide only a termination point for the AP).

[0017] Some implementations described herein allow for configuring a FWA deployment, such as for an MDU, that includes a DPU, multiple access points (connected to multiple ports of the DPU via corresponding connections), and a FWA-GW associated with a core network. The DPU identifies configuration information indicating corresponding correspondences between multiple ports of the DPU and address identifiers of multiple APs. The DPU then obtains (e.g., based on the configuration information) corresponding IP addresses associated with the multiple APs, such as by communicating with one or more devices associated with the core network. The DPU then sends the corresponding IP addresses to multiple access point devices (e.g., via corresponding connections between the multiple ports of the DPU and the multiple access point devices).

[0018] In this manner, the configuration of the FWA deployment eliminates the need for a CPE (e.g., for multi-residence scenarios associated with an MDU), such as by enhancing the capabilities of the DPU (e.g., by enhancing the DPU's capabilities to include more than just the ability to aggregate traffic to and from the MDU's resident APs). For example, the DPU is enhanced to acquire the IP addresses of multiple APs that are directly connected to the DPU. In turn, this conserves computing resources (e.g., processing resources, memory resources, communication resources, and / or power resources, etc.), network resources, and / or other resources that would otherwise be consumed by including a CPE in the configuration of the FWA deployment. Furthermore, only the AP needs to apply NAT and NAPT to data packets transmitted by the AP, which reduces latency associated with the data packets (e.g., because there is no CPE to perform repeated translation processes and / or no ALG is required to assist in the translation process).

[0019] Furthermore, because the DPU has enhanced functionality (e.g., Dynamic Host Configuration Protocol (DHCP) relay functionality) that associates the DPU's ports with the AP's IP address, it is easier to identify traffic associated with a particular residency of the MDU at the DPU for special processing (e.g., for billing purposes, accounting purposes, legal purposes, and / or other purposes). For example, some implementations allow for identification at the DPU of traffic associated with a residency that will be the subject of lawful intercept analysis, and thus only traffic associated with a particular port of the DPU needs to be intercepted and analyzed (rather than intercepting all traffic processed by the DPU to identify the traffic of interest). This improves the performance of the DPU and maintains the confidentiality and security of traffic that is not the subject of lawful intercept analysis.

[0020] Furthermore, in some implementations, the DPU can be dynamically configured by an operator (e.g., an operator of the configuration of the FWA deployment), such as via a remote client device, which reduces the need to manually configure the DPU. Furthermore, the DPU can provide telemetry data to the client device (e.g., in real time or near real time), which can enable the client device to remotely identify faults (e.g., faults associated with the configuration of the DPU and / or the FWA deployment).

[0021] In some implementations, the DPU can perform a verification operation (e.g., before obtaining corresponding IP addresses) to determine that multiple access point devices are connected to multiple ports based on configuration information. In this way, the DPU implements a security function to ensure that multiple APs are properly connected to the DPU before attempting to obtain corresponding IP addresses. This improves the security of the multiple APs, the DPU, and the core network.

[0022] In some implementations, a DPU may be able to connect to multiple FWA-GWs that are each associated with a different core network. This is not possible with a non-enhanced DPU in a typical configuration of an FWA deployment. Therefore, the configuration information may also indicate that address identifiers of a first set of one or more APs in the plurality of APs are associated with a first core network, address identifiers of a second set of one or more APs in the plurality of APs are associated with a second core network, and so on. Then, based on this configuration, the DPU may communicate with the first core network (e.g., via a first FWA-GW) to obtain a first set of one or more IP addresses, may communicate with the second core network (e.g., via a second FWA-GW) to obtain a second set of one or more IP addresses, and so on. The DPU may thus send the first set of one or more IP addresses to the first set of one or more APs, may send the second set of one or more IP addresses to the second set of one or more APs, and so on. In this way, the DPU may support communication between multiple APs and multiple core networks, which would otherwise not be possible using a single DPU.

[0023] Figure 1A-1E is a diagram of an example implementation 100 associated with a configuration for a FWA deployment. Figure 1A-1E As shown, the example implementation 100 includes a plurality of APs (shown as AP 1 to AP N, where N>1), a DPU, and one or more FWA GWs associated with a FWA deployment (e.g., to provide wireless broadband connections to user devices connected to the plurality of APs). In addition, Figure 1A-Figure 1C A single core network and related equipment associated with a single FWA-GW (e.g., RAN, customer premises equipment, and Broadband Network Gateway (BNG)) are shown, and Figure 1D-1E The first core network (core network A) and the second core network (core network B) associated with the first FWA-GW (FWA-GW A) and the second FWA-GW (FWA-GW B) are shown. These devices and core networks will be combined below. Figure 2-Figure 4 Describe in more detail.

[0024] like Figure 1A-1E As shown, multiple APs are associated with an MDU (shown as a multi-story building for illustrative purposes). For example, each AP can be associated with a location on the MDU. Each AP can have an address identifier (e.g., an address identifier that uniquely identifies the AP). The address identifier can be, for example, a media access control (MAC) address or another type of address identifier.

[0025] like Figure 1A-1EAs further shown, the DPU may include multiple ports (shown as port 1 to port M, where M ≥ N), and multiple APs may be connected to the multiple ports of the DPU via corresponding connections (e.g., wired connections) between the multiple ports of the DPU and the multiple APs. For example, connection 1 may connect AP 1 to port 1 of the DPU, and connection N may connect AP N to port M of the DPU.

[0026] like Figure 1A-Figure 1C As further shown, the DPU may be connected to the FWA-GW (e.g., such that the DPU and the FWA-GW are located at or within a radius of the MDU). The DPU may be connected via a connection (e.g., a wired connection) between the DPU and the FWA-GW. Figure 1A-Figure 1C As further shown, the FWA-GW may be associated with a core network and, therefore, may be associated with a RAN that communicates (e.g., wirelessly) with the core network. Thus, the FWA-GW may communicate (e.g., wirelessly) with the RAN to communicate with the core network. Figure 1A-Figure 1C As further shown, the client device and the BNG may be associated with the RAN and / or core network to allow the FWA-GW to communicate with the client device and the BNG, as further described herein.

[0027] like Figure 1A As shown in FIG102 , the DPU may obtain configuration information. For example, the DPU may obtain configuration information (e.g., configuration information associated with a FWA deployment) from a client device. The client device may send (e.g., wirelessly send) the configuration information to the FWA-GW via the RAN (and optionally, to the RAN via the core network), and the FWA-GW may send the configuration information to the DPU (e.g., via a connection between the DPU and the FWA-GW). The DPU may thereby obtain the configuration information by receiving the configuration information (e.g., from the client device via the RAN and the FWA-GW). As another example, the DPU may obtain the configuration information via an input component of the DPU (e.g., by an administrator of the DPU interacting with the input component to enter the configuration information into the DPU). Configuration information will be discussed herein with respect to Figure 1B Further description.

[0028] like Figure 1B As shown at 104, the DPU may identify the configuration information (e.g., based on obtaining the configuration information). For example, the DPU may process (e.g., parse and / or read) the configuration information (e.g., after obtaining the configuration information) to allow the DPU to identify the configuration information.

[0029] In some implementations, the configuration information may indicate the corresponding relationship between multiple ports of the DPU and address identifiers of multiple APs. As a specific example, Figure 1BAs shown, the configuration information may indicate the correspondence between the address identifier of AP 1 (shown as "AP 1ID") and port 1 of the DPU, and the correspondence between the address identifier of AP N (shown as "AP NID") and port 4 of the DPU. The configuration information may be represented in a data structure, such as a table, a database, or a key-value structure.

[0030] The DPU may determine that the plurality of ports of the DPU are connected to a plurality of APs, as indicated by reference numeral 106. For example, the DPU may use a link detection technique and / or another type of technique to determine that the plurality of ports of the DPU are connected to a plurality of APs (e.g., via respective connections between the plurality of ports of the DPU and the plurality of APs).

[0031] As indicated at 108, the DPU may perform a verification operation (eg, based on determining that multiple ports of the DPU are connected to multiple APs). In some implementations, the DPU may perform a verification operation to determine that multiple APs are connected to multiple ports based on configuration information.

[0032] For example, as a result of determining that multiple ports of the DPU are connected to multiple APs, the DPU may determine, for each port of the DPU, an address identifier of the AP connected to the DPU via the port. The DPU may then determine whether the address identifier of the AP connected to the port matches (e.g., is the same as) the address identifier of the AP of the port indicated by the configuration information. For example, for Figure 1B The DPU can determine whether the address identifier of AP 1 connected to port 1 of the DPU matches the address identifier AP 1ID of port 1 indicated by the configuration information. Therefore, when the DPU determines that there is a match for each port of the DPU (for example, determining that the physical configuration of multiple APs and multiple ports of the DPU match the configuration information), the DPU can determine that multiple APs are connected to multiple ports based on the configuration information, and thus the DPU can perform the operations described herein. Figure 1C Alternatively, when the DPU determines that there is no match for at least one port of the DPU (e.g., at least one physical configuration of the plurality of APs and the plurality of ports of the DPU do not match the configuration information), the DPU may determine, based on the configuration information, that the plurality of APs are not connected to the plurality of ports, and thus the DPU may avoid performing the operations described herein with respect to Figure 1C Any of the operations described.

[0033] like Figure 1CAs shown in FIG. 110 , the DPU may obtain corresponding IP addresses associated with the plurality of APs (e.g., based on configuration information). In some implementations, the DPU may communicate with the core network (and / or one or more devices associated with the core network), such as via the FWA-GW (and the RAN and the core network), to obtain corresponding IP addresses associated with the plurality of APs. For example, the DPU may be configured as a DHCP relay agent or a similar type of agent, i.e., an agent that communicates with the core network or one or more devices associated with the core network (such as a BNG) to obtain corresponding IP addresses.

[0034] In a specific example, to obtain a specific IP address for a specific AP that is connected to a specific port of the DPU (and therefore has an address identifier corresponding to the specific port, as indicated by configuration information), the DPU may send (e.g., to the core network and / or to one or more devices associated with the core network) a first DHCP message (e.g., a DHCP discover message, a DHCP request message, or another type of DHCP message). The first DHCP message may include information indicating the specific port of the DPU. The DPU (e.g., based on sending the first DHCP message, such as in response to the first DHCP message) may then receive (e.g., from the core network and / or from one or more devices associated with the core network) a second DHCP message (e.g., a DHCP offer message, a DHCP announce message, or another type of DHCP message). The second DHCP message may include a specific IP address (e.g., to be provided to a specific AP). In this manner, the DPU can obtain the IP address of each AP.

[0035] As shown by reference numeral 112, the DPU may send corresponding IP addresses to multiple APs. In some implementations, the DPU may send corresponding IP addresses to multiple APs via corresponding connections between multiple ports of the DPU and the multiple APs. As a specific example, Figure 1C As shown, the DPU can send IP address 1 (e.g., obtained for AP 1) via connection 1 between AP 1 and port 1 of the DPU, and the DPU can send IP address N (e.g., obtained for AP N) via connection N between AP N and DPU port M.

[0036] In some implementations, the DPU may be connected to multiple FWA-GWs instead of a single FWA-GW. Figure 1D-1EAs shown, the DPU may be connected to at least a first FWA-GW (FWA-GW A) associated with a first core network (core network A) and a second FWA-GW (FWA-GW B) associated with a second core network (core network B) (e.g., different from the first core network). Therefore, the DPU may identify that the DPU is connected to at least the first FWA-GW and the second FWA-GW (e.g., in the same manner as described herein with respect to Figure 1B and in a similar manner as described with reference numeral 106).

[0037] Therefore, if Figure 1D As shown in FIG. 114, the DPU may identify configuration information (e.g., in a manner consistent with the Figure 1B and similarly as described with reference numeral 104). The configuration information may indicate respective correspondences between a plurality of ports of the DPU and address identifiers of a plurality of APs (e.g., as described elsewhere herein), and may further indicate that a first set of address identifiers of one or more of the plurality of APs is associated with a first core network, a second set of address identifiers of one or more of the plurality of APs is associated with a second core network, and so on. As a specific example, Figure 1D As shown, the configuration information may indicate a correspondence between the address identifier of AP 1 (shown as “AP 1 ID”) and port 1 of the DPU, a correspondence between the address identifier of AP N (shown as “AP N ID”) and port M of the DPU, and may also indicate that the address identifier of AP 1 is associated with the first core network (“Core Network A”) and the address identifier of AP N is associated with the second core network (“Core Network B”).

[0038] In some implementations, the DPU may determine that multiple ports of the DPU are connected to multiple APs and may perform a verification operation (e.g., in the same manner as described herein with respect to Figure 1B and similar manner as described with reference numerals 106 and 108). Thus, the DPU can determine from the configuration information that multiple APs are connected to multiple ports, and thus the DPU can perform the operations described herein with respect to Figure 1E Alternatively, the DPU may determine based on the configuration information that the multiple APs are not connected to the multiple ports, and therefore the DPU may avoid performing the operations described herein with respect to Figure 1E Any of the actions described.

[0039] like Figure 1E As shown, the DPU can obtain the corresponding IP addresses associated with multiple APs (e.g., based on configuration information), such as in the manner described herein with respect to Figure 1CFor example, as shown by reference numerals 116 and 118, the DPU may communicate with the first core network (and / or one or more devices associated with the first core network), such as via the first FWA-GW (and the first RAN "RAN A" and the first core network), to obtain (among the corresponding IP addresses) a first set of one or more IP addresses for a first set of one or more APs; may communicate with the second core network (and / or one or more devices associated with the second core network), such as via the second FWA-GW (and the second RAN "RAN B" and the second core network), to obtain (among the corresponding IP addresses) a second set of one or more IP addresses for a second set of one or more APs; and so on.

[0040] like Figure 1E As further shown, the DPU may send corresponding IP addresses to multiple APs (e.g., based on configuration information), such as in the manner described herein with respect to Figure 1C For example, as shown at 120 and 122, the DPU may send (e.g., based on configuration information) a first set of one or more IP addresses to a first set of one or more APs, may send (e.g., based on configuration information) a second set of one or more IP addresses to a second set of one or more APs, and so on. In a specific example, the DPU may send IP address 1 (e.g., acquired for AP 1 and associated with a first core network) via connection 1 between AP 1 and port 1 of the DPU, and the DPU may send IP address N (e.g., acquired for AP N and associated with a second core network) via connection N between AP N and port M of the DPU.

[0041] As mentioned above, Figure 1A-1E Provided as an example only. Other examples may be Figure 1A-1E Different from what is described in . Figure 1A-1E The number and arrangement of the devices shown are provided as examples. In practice, Figure 1A-1E There may be more devices, fewer devices, different devices, or differently arranged devices than shown. Figure 1A-1E Two or more of the devices shown may be implemented in a single device, or Figure 1A-1E The single device shown may be implemented as multiple distributed devices. Additionally or alternatively, Figure 1A-1E The illustrated set of devices (e.g., one or more devices) may perform the operations described as being performed by Figure 1A-1E Another group of devices is shown performing one or more functions.

[0042] Figure 2 2 is a diagram of an example environment 200 in which the systems and / or methods described herein may be implemented. Figure 2 As shown, example environment 200 may include a plurality of APs 205, DPUs 210, FWA-GWs 215, RANs 220, BNGs 225, core networks 230, data networks 285, and client devices 290. The devices and / or networks of example environment 200 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0043] Each AP 205 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information (such as the information described herein). For example, the AP 205 may include a network device (e.g., a router, a switch, or another type of network device) that provides wireless and / or wired signaling to user devices. The AP 205 may be connected to a port of the DPU 210 via a connection (e.g., a wired connection), which allows the AP 205 to obtain an IP address and communicate with the core network 230.

[0044] The DPU 210 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information, such as the information described herein. For example, the DPU 210 may include a network device (e.g., a router, a switch, or another type of network device) that serves as an aggregation point for traffic from multiple different APs 205. The DPU 210 may include an infrastructure processing unit (IPU), an intelligent network interface card (NIC), a system-on-chip (SoC)-based NIC (which may perform processing and analysis of the network, security, storage of data sets), and the like. The DPU 210 may include a programmable computer processor that tightly integrates a general-purpose central processing unit (CPU) with network interface hardware. The DPU 210 may be used to perform encryption / decryption, act as a firewall, process protocols, process network requests, act as a hypervisor or storage controller, and the like.

[0045] The FWA-GW 215 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information, such as the information described herein. For example, the FWA-GW 215 may include a network device (e.g., a router, a switch, or another type of network device), a mobile hotspot device, a FWA device, a FWA channel service unit, a FWA data service unit, a FWA router, a FWA wireless access point (WAP) device, a FWA modem, a FWA set-top box, or a similar type of device. The FWA-GW 215 may provide wireless connectivity between two fixed points (e.g., the DPU 210 and the RAN 220), such as via a radio link, to enable communication with the core network 230.

[0046] The RAN 220 may support, for example, a cellular radio access technology (RAT). The RAN 220 may include one or more base stations (e.g., base transceiver stations, radio base stations, Node Bs, eNodeBs (eNBs), gNodeBs (gNBs), base station subsystems, cell sites, cell towers, access points, transmit receive points (TRPs), radio access nodes, macrocell base stations, microcell base stations, picocell base stations, femtocell base stations, or similar types of devices), and other network entities that may support wireless communications. The RAN 220 may transfer traffic between user equipment (e.g., using a cellular RAT), one or more other RANs 220 (e.g., using a wireless interface or a backhaul interface, such as a wired backhaul interface), and / or the core network 230. The RAN 220 may provide one or more cells covering a geographic area.

[0047] In some implementations, the RAN 220 may perform scheduling and / or resource management for the FWA-GW 215 covered by the RAN 220 (e.g., for the FWA-GW 215 covered by the cell provided by the RAN 220). In some implementations, the RAN 220 may be controlled or coordinated by a network controller, which may perform load balancing, network-level configuration, etc. The network controller may communicate with the RAN 220 via a wireless or wired backhaul. In some implementations, the RAN 220 may include a network controller, a self-organizing network (SON) module or component, or similar modules or components. In other words, the RAN 220 may perform network control, scheduling, and / or network management functions (e.g., for uplink, downlink, and / or sidelink communications of the FWA-GW 215 covered by the RAN 220).

[0048] The BNG 225 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information, such as the information described herein. For example, the BNG 225 can be configured as a DHCP server and can provide DHCP services to multiple APs 205, DPUs 210, and / or FWA-GWs 215 (e.g., associated with the core network 230). In some implementations, the BNG 225 provides user devices with access to a broadband network and connects subscribers to a service provider network. The BNG 225 can aggregate traffic from multiple user devices and can route the traffic to the service provider network.

[0049] In some implementations, the core network 230 may include an example functional architecture in which the systems and / or methods described herein may be implemented. For example, the core network 230 may include an example architecture of a fifth generation (5G) next generation (NG) core network included in a 5G wireless telecommunications system. Figure 2The example architecture of the core network 230 shown may be an example of a service-based architecture, but in some implementations, the core network 230 may be implemented as a reference point architecture, a 4G core network, or the like.

[0050] like Figure 2 As shown, the core network 230 may include multiple functional elements. The functional elements may include, for example, a network slice selection function (NSSF) 235, a network exposure function (NEF) 240, an authentication server function (AUSF) 245, a unified data management component (UDM) 250, a policy control function (PCF) 255, an application function (AF) 260, an access and mobility management function (AMF) 265, a session management function (SMF) 270, a user plane function (UPF) 275, etc. These functional elements may be communicatively connected via a message bus 280. Figure 2 Each functional element shown is implemented on one or more devices associated with a wireless telecommunications system. In some implementations, one or more functional elements may be implemented on a physical device, such as an access point, a base station, a gateway, etc. In some implementations, one or more functional elements may be implemented on a computing device in a cloud computing environment.

[0051] The NSSF 235 includes one or more devices that select network slice instances for multiple APs 205. By providing network slicing, the NSSF 235 allows operators to deploy multiple, essentially independent end-to-end networks that potentially have the same infrastructure. In some implementations, each slice can be customized for different services.

[0052] The NEF 240 includes one or more devices that support exposing capabilities and / or events in the wireless telecommunication system to help other entities in the wireless telecommunication system discover network services.

[0053] The AUSF 245 comprises one or more devices that act as an authentication server and support the process of authenticating multiple APs 205 in a wireless telecommunications system.

[0054] The UDM 250 includes one or more devices that store user data and profiles in a wireless telecommunications system. The UDM 250 can be used for fixed access, mobile access, etc. in the core network 230.

[0055] PCF 255 includes one or more devices that provide a policy framework that includes network slicing, roaming, packet processing, mobility management, etc.

[0056] The AF 260 includes one or more devices that support application influence on traffic routing, access to the NEF 240, policy control, etc.

[0057] The AMF 265 includes one or more devices that act as a termination point for non-access stratum (NAS) signaling, mobility management, and the like.

[0058] The SMF 270 includes one or more devices that support the establishment, modification, and release of communication sessions in a wireless telecommunications system. For example, the SMF 270 can configure service steering policies at the UPF 275, implement user equipment IP address allocation and policies, and so on.

[0059] The UPF 275 includes one or more devices that serve as anchor points for intra-RAT and / or inter-RAT mobility. The UPF 275 can apply rules to packets, such as rules related to packet routing, traffic reporting, handling user plane quality of service (QoS), and the like.

[0060] The message bus 280 represents a communication structure for communication between functional elements. In other words, the message bus 280 can allow communication between two or more functional elements.

[0061] The data network 285 includes one or more wired and / or wireless data networks. For example, the data network 285 may include an IP Multimedia Subsystem (IMS), a Public Land Mobile Network (PLMN), a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a private network such as a company intranet, an ad hoc network, the Internet, a fiber-based network, a cloud computing network, a third-party service network, an operator service network, and / or a combination of these or other types of networks.

[0062] The client device 290 may include one or more devices capable of receiving, generating, storing, processing, and / or providing information (such as configuration information), as described elsewhere herein. The client device 290 may include a communication device and / or a computing device. For example, the client device 290 may include a wireless communication device, a mobile phone, a user device, a laptop computer, a tablet computer, a desktop computer, a wearable communication device (e.g., a smartwatch, smart glasses, a head-mounted display, or a virtual reality headset), or a similar type of device.

[0063] Figure 2 The number and arrangement of devices and networks shown are provided as examples. Figure 2 There may be more devices and / or networks, fewer devices and / or networks, different devices and / or networks, or differently arranged devices and / or networks than shown. Figure 2 Two or more of the devices shown may be implemented in a single device, or Figure 2The single device shown may be implemented as multiple distributed devices. Additionally or alternatively, one set of devices (eg, one or more devices) of the example environment 200 may perform one or more functions described as being performed by another set of devices of the example environment 200.

[0064] Figure 3 FIG2 is a diagram of example components of a device 300 associated with a configuration of an FWA deployment. The device 300 may correspond to a plurality of APs 205, a DPU 210, an FWA-GW 215, a RAN 220, a BNG 225, a NSSF 235, a NEF 240, an AUSF 245, a UDM 250, a PCF 255, an AF 260, an AMF 265, an SMF 270, a UPF 275, and / or client devices 290. In some implementations, a plurality of APs 205, DPUs 210, FWA-GW 215, RAN 220, BNG 225, NSSF 235, NEF 240, AUSF 245, UDM 250, PCF 255, AF 260, AMF 265, SMF 270, UPF 275, and / or client devices 290 may include one or more devices 300 and / or one or more components of devices 300. Figure 3 As shown, device 300 may include a bus 310 , a processor 320 , a memory 330 , an input component 340 , an output component 350 , and / or a communication component 360 .

[0065] The bus 310 may include one or more components that enable wired and / or wireless communication between components of the device 300. The bus 310 may include one or more components that enable wired and / or wireless communication between components of the device 300. Figure 3 The two or more components of the computer system are coupled together, such as via operational coupling, communication coupling, electronic coupling and / or electrical coupling. For example, the bus 310 may include electrical connections (e.g., wires, traces and / or leads) and / or wireless buses. The processor 320 may include a central processing unit, a graphics processing unit, a microprocessor, a controller, a microcontroller, a digital signal processor, a field programmable gate array, an application specific integrated circuit and / or other types of processing components. The processor 320 may be implemented in hardware, firmware, or a combination of hardware and software. In some implementations, the processor 320 may include one or more processors that can be programmed to perform one or more operations or processes described elsewhere herein.

[0066] The memory 330 may include volatile and / or non-volatile memory. For example, the memory 330 may include random access memory (RAM), read-only memory (ROM), a hard drive, and / or another type of memory (e.g., flash memory, magnetic memory, and / or optical memory). The memory 330 may include internal memory (e.g., RAM, ROM, or hard drive) and / or removable memory (e.g., removable via a universal serial bus connection). The memory 330 may be a non-transitory computer-readable medium. The memory 330 may store information related to the operation of the device 300, one or more instructions, and / or software (e.g., one or more software applications). In some implementations, the memory 330 may include one or more memories coupled (e.g., communicatively coupled) to one or more processors (e.g., processor 320), such as via bus 310. The communicatively coupled between the processor 320 and the memory 330 may enable the processor 320 to read and / or process information stored in the memory 330 and / or store information in the memory 330.

[0067] The input component 340 can enable the device 300 to receive input, such as user input and / or sensory input. For example, the input component 340 can include a touch screen, a keyboard, a keypad, a mouse, a button, a microphone, a switch, a sensor, a global positioning system sensor, a global navigation satellite system sensor, an accelerometer, a gyroscope and / or an actuator. The output component 350 can enable the device 300 to provide an output, such as via a display, a speaker and / or a light emitting diode. The communication component 360 can enable the device 300 to communicate with other devices via a wired connection and / or a wireless connection. For example, the communication component 360 can include a receiver, a transmitter, a transceiver, a modem, a network interface card and / or an antenna.

[0068] The device 300 can perform one or more operations or processes described herein. For example, a non-transient computer-readable medium (e.g., memory 330) can store an instruction set (e.g., one or more instructions or codes) for execution by the processor 320. The processor 320 can execute the instruction set to perform one or more operations or processes described herein. In some implementations, the execution of the instruction set by one or more processors 320 causes one or more processors 320 and / or the device 300 to perform one or more operations or processes described herein. In some implementations, hard-wired circuitry can be used instead of instructions or in combination with instructions to perform one or more operations or processes described herein. Additionally or alternatively, the processor 320 can be configured to perform one or more operations or processes described herein. Therefore, the implementation described herein is not limited to any particular combination of hardware circuitry and software.

[0069] Figure 3The number and arrangement of components shown are provided as examples. Figure 3 Device 300 may include more components, fewer components, different components, or differently arranged components than shown. Additionally or alternatively, one or more components of device 300 may perform one or more functions described as being performed by another group of components of device 300.

[0070] Figure 4 FIG4 is a diagram of example components of a device 400 associated with a configuration of an FWA deployment. The device 400 may correspond to a plurality of APs 205, a DPU 210, an FWA-GW 215, a RAN 220, a BNG 225, an NSSF 235, a NEF 240, an AUSF 245, a UDM 250, a PCF 255, an AF 260, an AMF 265, an SMF 270, a UPF 275, and / or client devices 290. In some implementations, a plurality of APs 205, DPUs 210, FWA-GW 215, RAN 220, BNG 225, NSSF 235, NEF 240, AUSF 245, UDM 250, PCF 255, AF 260, AMF 265, SMF 270, UPF 275, and / or client devices 290 may include one or more devices 400 and / or one or more components of devices 400. Figure 4 As shown, the device 400 may include one or more input components 410-1 to 410-B (B≥1) (hereinafter collectively referred to as input component 410, and individually referred to as input component 410), a switch component 420, one or more output components 430-1 to 430-C (C≥1) (hereinafter collectively referred to as output component 430, and individually referred to as output component 430), and a controller 440.

[0071] The input component 410 can be one or more attachment points for a physical link and can be one or more entry points for incoming traffic (such as packets). The input component 410 can process incoming traffic, such as by performing data link layer encapsulation or decapsulation. In some implementations, the input component 410 can transmit and / or receive packets. In some implementations, the input component 410 can include an input line card that includes one or more packet processing components (e.g., in the form of an integrated circuit), such as one or more interface cards (IFCs), a packet forwarding component, a line card controller component, an input port, a processor, a memory, and / or an input queue. In some implementations, the device 400 can include one or more input components 410.

[0072] The switch component 420 can interconnect the input component 410 with the output component 430. In some implementations, the switch component 420 can be implemented via one or more crossbar switches, via a bus, and / or using shared memory. The shared memory can act as a temporary buffer to store packets from the input component 410 before they are ultimately scheduled for delivery to the output component 430. In some implementations, the switch component 420 can enable the input component 410, the output component 430, and / or the controller 440 to communicate with each other.

[0073] The output component 430 can store packets and can schedule packets for transmission on an output physical link. The output component 430 can support data link layer encapsulation or decapsulation, and / or various higher-level protocols. In some implementations, the output component 430 can transmit packets and / or receive packets. In some implementations, the output component 430 can include an output line card that includes one or more packet processing components (e.g., in the form of an integrated circuit), such as one or more IFCs, packet forwarding components, line card controller components, output ports, processors, memories, and / or output queues. In some implementations, the device 400 can include one or more output components 430. In some implementations, the input component 410 and the output component 430 can be implemented by the same set of components (e.g., the input / output component can be a combination of the input component 410 and the output component 430).

[0074] The controller 440 includes a processor in the form of, for example, a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor, a controller, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and / or another type of processing component. The processor is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, the controller 440 may include one or more processors that can be programmed to perform functions.

[0075] In some implementations, the controller 440 may include RAM, ROM, and / or another type of dynamic or static storage device (eg, flash memory, magnetic memory, optical memory, etc.) that stores information and / or instructions for use by the controller 440 .

[0076] In some implementations, the controller 440 can communicate with other devices, networks, and / or systems connected to the device 400 to exchange information about the network topology. The controller 440 can create a routing table based on the network topology information, can create a forwarding table based on the routing table, and can forward the forwarding table to the input component 410 and / or the output component 430. The input component 410 and / or the output component 430 can use the forwarding table to perform routing lookups for incoming and / or outgoing packets.

[0077] The controller 440 may perform one or more of the processes described herein. The controller 440 may perform these processes in response to executing software instructions stored by a non-transitory computer-readable medium. A computer-readable medium is defined herein as a non-transitory memory device. A memory device may include memory space within a single physical storage device or memory space distributed across multiple physical storage devices.

[0078] The software instructions may be read from another computer-readable medium or from another device via a communication interface into a memory and / or storage component associated with the controller 440. When executed, the software instructions stored in the memory and / or storage component associated with the controller 440 may cause the controller 440 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, the implementations described herein are not limited to any specific combination of hardware circuitry and software.

[0079] Figure 4 The number and arrangement of components shown are provided as examples. Figure 4 Device 400 may include more components, fewer components, different components, or differently arranged components than shown. Additionally or alternatively, one or more components of device 400 may perform one or more functions described as being performed by another group of components of device 400.

[0080] Figure 5 is a flow diagram of an example process 500 associated with configuration of a FWA deployment. In some implementations, Figure 5 One or more process blocks of are performed by a DPU (e.g., DPU 210) associated with a FWA deployment. In some implementations, Figure 5 One or more process blocks of the process blocks are performed by another device or group of devices separate from or including the DPU, such as an AP (e.g., 205), a FWA-GW (e.g., FWA-GW 215), a RAN (e.g., RAN 220), a BNG (e.g., BNG 225), one or more functions of a core network (e.g., core network 230), and / or a client device (e.g., client device 290). Additionally or alternatively, Figure 5 One or more process blocks may be performed by one or more components of device 300, such as processor 320, memory 330, input component 340, output component 350, and / or communication component 360; by one or more components of device 400, such as input component 410, switch component 420, output component 430, and / or controller 440; and / or by another device.

[0081] like Figure 5 As shown, process 500 may include identifying configuration information (block 510). For example, the DPU may identify the configuration information, as described above. The configuration information may indicate a corresponding relationship between a plurality of ports of the DPU and address identifiers of a plurality of access point devices.

[0082] like Figure 5 As further shown, process 500 may include obtaining respective IP addresses associated with the plurality of access point devices (block 520). For example, the DPU may obtain respective IP addresses associated with the plurality of access point devices based on configuration information, as described above.

[0083] like Figure 5 As further shown, process 500 may include sending the respective IP addresses to the plurality of access point devices (block 530). For example, the DPU may send the respective IP addresses to the plurality of access point devices via respective connections between the plurality of ports of the DPU and the plurality of access point devices, as described above.

[0084] Process 500 may include additional implementations, such as any single implementation or any combination of implementations described below and / or implementations related to one or more other processes described elsewhere herein.

[0085] In a first implementation, process 500 includes obtaining configuration information from a client device associated with a FWA deployment.

[0086] In a second implementation, alone or in combination with the first implementation, process 500 includes determining that multiple ports of the DPU are connected to multiple access point devices, and before obtaining corresponding IP addresses, performing a verification operation to determine that the multiple access point devices are connected to the multiple ports based on configuration information.

[0087] In a third implementation, alone or in combination with one or more of the first and second implementations, each access point device of the plurality of access point devices is associated with a residence of multiple residence units.

[0088] In a fourth implementation, alone or in combination with one or more of the first to third implementations, process 500 includes sending a first DHCP message to one or more devices associated with a core network, the DHCP message including information indicating a specific port among multiple ports of a DPU; and based on sending the first DHCP message, receiving a second DHCP message from one or more devices associated with the core network, the second DHCP message including a specific IP address among the corresponding IP addresses, wherein the specific IP address will be provided to a specific access point device among multiple access point devices having an address identifier corresponding to the specific port of the DPU as indicated by the configuration information.

[0089] In a fifth implementation, alone or in combination with one or more of the first to fourth implementations, the DPU is connected to at least a first FWA gateway associated with the first core network and a second FWA gateway associated with the second core network.

[0090] In a sixth implementation, alone or in combination with one or more of the first to fifth implementations, process 500 includes communicating with one or more devices via a first FWA gateway to obtain a first set of one or more IP addresses in corresponding IP addresses, the one or more devices being associated with the first core network; and communicating with one or more second devices via a second FWA gateway to obtain a second set of one or more IP addresses in corresponding IP addresses, the one or more second devices being associated with the second core network.

[0091] In a seventh implementation, alone or in combination with one or more implementations of the first to sixth implementations, the configuration information further indicates that address identifiers of a first set of one or more access point devices among the multiple access point devices are associated with the first core network, and address identifiers of a second set of one or more access point devices among the multiple access point devices are associated with the second core network, wherein in order to send the corresponding IP addresses, the one or more processors are used to: send a first set of one or more IP addresses to the first set of one or more access point devices based on the configuration information, and send a second set of one or more IP addresses to the second set of one or more access point devices based on the configuration information.

[0092] although Figure 5 Example blocks of process 500 are shown, but in some implementations, Figure 5 Process 500 may include more blocks, fewer blocks, different blocks, or differently arranged blocks than shown. Additionally or alternatively, two or more blocks of process 500 may be performed in parallel.

[0093] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementation to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementation.

[0094] As used herein, a service or content may include a set of packets. A packet may refer to a communication structure for transmitting information, such as a protocol data unit (PDU), a service data unit (SDU), a network packet, a datagram, a segment, a message, a block, a frame (e.g., an Ethernet frame), a portion of any of the above, and / or another type of formatted or unformatted data unit capable of being sent via a network.

[0095] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, or a combination of hardware and software. It is apparent that the systems and / or methods described herein can be implemented in various forms of hardware, firmware, or / and a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the implementation. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code—it should be understood that software and hardware can be used to implement the systems and / or methods based on the description herein.

[0096] Although particular feature combinations are referenced in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various implementations. In fact, many of these features can be combined in ways that are not specifically referenced in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of the various implementations includes the combination of each dependent claim with every other claim in the claim set. As used herein, the phrase "at least one" in a list of referenced items refers to any combination of these items, including single members. For example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as multiple combinations of the above items.

[0097] When a “processor” or “one or more processors” (or another device or component, such as a “controller” or “at least one controller”) is described or claimed (either within a single claim or across multiple claims) as performing or being configured to perform multiple operations, the language is intended to broadly encompass a variety of processor architectures and environments. For example, unless expressly required otherwise (e.g., via the use of “a first processor” and “a second processor” or other language in the claims that distinguishes between processors), the language is intended to encompass a single processor that performs or is configured to perform all of the operations, a group of processors that collectively perform or are configured to perform all of the operations, a first processor that performs or is configured to perform a first operation and a second processor that performs or is configured to perform a second operation, or any combination of processors that perform or are configured to perform operations. For example, when a claim has the form “one or more processors that: perform X; perform Y; and perform Z,” the claim should be interpreted to mean “one or more processors that perform X; one or more (possibly different) processors that perform Y; and one or more (possibly different) processors that perform Z.”

[0098] Any element, action or instruction used in this article should not be interpreted as key or necessary, unless clearly described as such.In addition, as used in this article, article " one (a) " and " one (an) " are intended to include one or more projects, and can be used interchangeably with " one or more ".In addition, as used in this article, article " this (the) " is intended to include one or more projects quoted in conjunction with article " this (the) ", and can be used interchangeably with " one or more ".In addition, as used in this article, term " set (set) " is intended to include one or more projects (for example, related project, unrelated project or the combination of related and unrelated project), and can be used interchangeably with " one or more ".If only intend to use one, then use phrase " only one (only one) " or similar language.In addition, as used in this article, term " have (has) ", " have (have) ", " have (having) " etc. are intended to be open term.In addition, unless otherwise clearly stated, phrase " based on " is intended to represent " at least partially based on ". Furthermore, as used herein, the term "or" is intended to be inclusive when used in a serial form and is used interchangeably with "and / or" unless expressly stated otherwise (e.g., if used in conjunction with "any one" or "only one of").

Claims

1. A distribution point unit (DPU) associated with a fixed wireless access (FWA) deployment, comprising: one or more memories; as well as One or more processors for: Identification configuration information, the configuration information indicating corresponding correspondences between multiple ports of the DPU and address identifiers of multiple access point devices; obtaining corresponding Internet Protocol (IP) addresses associated with the plurality of access point devices based on the configuration information; as well as The respective IP addresses are sent to the plurality of access point devices via respective connections between the plurality of ports of the DPU and the plurality of access point devices.

2. The DPU of claim 1 , wherein the one or more processors are further configured to: The configuration information is obtained from a client device associated with the FWA deployment.

3. The DPU of claim 1 , wherein the one or more processors are further configured to: determining that the plurality of ports of the DPU are connected to the plurality of access point devices; and Before acquiring the corresponding IP addresses, a verification operation is performed to determine, based on the configuration information, that the plurality of access point devices are connected to the plurality of ports.

4. The DPU of claim 1, wherein each of the plurality of access point devices is associated with a residency of a multi-residence unit.

5. The DPU of claim 1 , wherein to obtain the corresponding IP address, the one or more processors are configured to: sending a first Dynamic Host Configuration Protocol (DHCP) message to one or more devices associated with a core network, the DHCP message including information indicating a specific port among the plurality of ports of the DPU; and Based on sending the first DHCP message, receiving a second DHCP message from the one or more devices associated with the core network, the second DHCP message including a specific IP address among the corresponding IP addresses, The specific IP address, as indicated by the configuration information, will be provided to a specific access point device among the multiple access point devices that has an address identifier corresponding to the specific port of the DPU.

6. The DPU of claim 1, wherein the DPU is connected to at least a first FWA gateway associated with a first core network and a second FWA gateway associated with a second core network.

7. The DPU of claim 6, wherein to obtain the corresponding IP address, the one or more processors are configured to: communicating with one or more devices via the first FWA gateway to obtain a first set of one or more IP addresses among the corresponding IP addresses, the one or more devices being associated with the first core network; and Communicate with one or more second devices via the second FWA gateway to obtain a second set of one or more IP addresses among the corresponding IP addresses, the one or more second devices being communicatively associated with the second core network.

8. The DPU of claim 6 , wherein the configuration information further indicates that a first set of address identifiers of one or more access point devices in the plurality of access point devices are associated with the first core network, and a second set of address identifiers of one or more access point devices in the plurality of access point devices are associated with the second core network. Wherein, in order to send the corresponding IP address, the one or more processors are configured to: sending the first set of one or more IP addresses to a first set of the one or more access point devices based on the configuration information; and The second set of one or more IP addresses is sent to a second set of the one or more access point devices based on the configuration information.

9. A non-transitory computer-readable medium storing an instruction set, the instruction set comprising: One or more instructions that, when executed by one or more processors of a distribution point unit (DPU) associated with a fixed wireless access (FWA) deployment, cause the DPU to: Identification configuration information, the configuration information indicating corresponding correspondences between multiple ports of the DPU and address identifiers of multiple access point devices; determining that the plurality of ports of the DPU are connected to the plurality of access point devices; as well as A verification operation is performed to determine, based on the configuration information, that the plurality of access point devices are connected to the plurality of ports.

10. The non-transitory computer-readable medium of claim 9, wherein the one or more instructions, when executed by the one or more processors, further cause the DPU to: The configuration information is obtained from a client device associated with the FWA deployment.

11. The non-transitory computer-readable medium of claim 9, wherein the one or more instructions, when executed by the one or more processors, further cause the DPU to: Obtaining corresponding Internet Protocol (IP) addresses associated with the plurality of access point devices based on the configuration information; and The respective IP addresses are sent to the plurality of access point devices via respective connections between the plurality of ports of the DPU and the plurality of access point devices.

12. The non-transitory computer-readable medium of claim 11 , wherein the one or more instructions that cause the DPU to obtain the corresponding IP address cause the DPU to: Sending a first Dynamic Host Configuration Protocol (DHCP) message to a core network, the DHCP message including information indicating a specific port among the multiple ports of the DPU; and Based on sending the first DHCP message, a second DHCP message is received from the core network, wherein the second DHCP message includes a specific IP address among the corresponding IP addresses, and the specific IP address will be provided to a specific access point device among the multiple access point devices having an address identifier corresponding to the specific port of the DPU.

13. The non-transitory computer-readable medium of claim 9, wherein the one or more instructions, when executed by the one or more processors, further cause the DPU to: It is identified that the DPU is connected to at least a first FWA gateway associated with a first core network and a second FWA gateway associated with a second core network.

14. The non-transitory computer-readable medium of claim 13 , wherein the configuration information further indicates that a first set of address identifiers of one or more of the plurality of access point devices are associated with the first core network, and a second set of address identifiers of one or more of the plurality of access point devices are associated with the second core network, wherein the one or more instructions, when executed by the one or more processors, further cause the DPU to: communicating with the first core network via the first FWA gateway and acquiring a first set of one or more IP addresses for the first set of one or more access point devices based on the configuration information; and Communicate with the second core network via the second FWA gateway, and obtain a second set of one or more IP addresses for the second set of one or more access point devices based on the configuration information.

15. The non-transitory computer-readable medium of claim 14, wherein the one or more instructions, when executed by the one or more processors, further cause the DPU to: sending the first set of one or more IP addresses to a first set of the one or more access point devices; and The second set of one or more IP addresses is sent to a second set of the one or more access point devices.

16. A method comprising: Obtaining, by a distribution point unit (DPU) associated with a fixed wireless access (FWA) deployment, respective Internet Protocol (IP) addresses associated with a plurality of access point devices connected to a plurality of ports of the DPU; as well as The respective IP addresses are sent by the DPU to the plurality of access point devices via respective connections between the plurality of ports of the DPU and the plurality of access point devices.

17. The method according to claim 16, further comprising: Before acquiring the corresponding IP addresses, a verification operation is performed to determine that the multiple access point devices are connected to the multiple ports according to configuration information, the configuration information indicating corresponding correspondences between the multiple ports of the DPU and address identifiers of the multiple access point devices.

18. The method according to claim 16, wherein obtaining the corresponding IP address comprises: sending a first Dynamic Host Configuration Protocol (DHCP) message, the DHCP message including information indicating a specific port among the plurality of ports of the DPU; as well as Based on sending the first DHCP message, a second DHCP message is received, wherein the second DHCP message includes a specific IP address among the corresponding IP addresses, and the specific IP address will be provided to a specific access point device among the multiple access point devices having an address identifier corresponding to the specific port of the DPU.

19. The method according to claim 16, wherein obtaining the corresponding IP address comprises: communicating via a first FWA gateway associated with the first core network to obtain a first set of one or more IP addresses among the corresponding IP addresses; as well as Communicate via a second FWA gateway associated with a second core network to obtain a second set of one or more IP addresses among the corresponding IP addresses.

20. The method of claim 19, wherein sending the corresponding IP address comprises: sending the first set of one or more IP addresses to a first set of one or more access point devices associated with the first core network among the plurality of access point devices; as well as The second set of one or more IP addresses is sent to a second set of one or more access point devices of the plurality of access point devices that are associated with the second core network.

Images