Pole management for installing network elements based on latitude and longitude

Abstract

A utility pole management is described for installing a network element based on latitude and longitude values. Utility pole data having latitude and longitude values ​​is obtained from a plurality of sources. The utility pole data from the plurality of sources is stored in a central utility pole database. A plurality of utility poles associated with at least a portion of the utility pole data are presented on a map in a graphical user interface based on at least the latitude and longitude values. A first utility pole is selected on the map in consideration of installing a network element for providing wireless service. A geographic boundary is presented on the map for the first utility pole, the geographic boundary encompassing the candidate utility poles. A utility pole is selected from the candidate utility poles inside the geographic boundary for installing a network element for providing wireless service.

Description

[Technical field]

[0001] This description relates to pole management for locating network elements based on latitude and longitude, and methods of use thereof. [Background technology]

[0002] Mobile communication networks provide wireless connectivity to mobile devices. These devices, known as User Equipment (UE), traditionally correspond to smartphones and tablets, but increasingly include automobiles, drones, industrial and agricultural machinery, robots, home appliances, medical equipment, etc. Mobile communication networks include two main subsystems: the Radio Access Network (RAN) and the Mobile Core. The RAN manages the radio spectrum to ensure efficient use and that the provision of user quality of service is met. The network corresponds to a distributed collection of base stations. In 4G, these are called eNodeB (or eNB), which is an abbreviation for evolved Node B. In 5G, the base stations are called gNB, with the "g" standing for next generation.

[0003] In mobile communications networks, as technology evolves, there are different generations of network elements (NEs) operating simultaneously. Multiple deployment options often coexist. For example, there are standalone (SA) 4G and SA 5G sites. Another option is a non-standalone (NSA) deployment where there are 4G and 5G RANs accessing a 4G Evolved Packet Core (EPC). Another possibility involves NSA 4G and 5G RANs accessing a 5G mobile core, called the NG Core. Thus, there are different generations of technology using different equipment to support mobile communications.

[0004] While 4G networks use large cellular towers carrying NEs to create cell sites, 5G uses a type of technology called "small cell" base stations. These base stations are unobtrusive and the NEs are installed in parts of the existing infrastructure allowing for denser coverage. Utility poles often house equipment used to provide various services including power, telephone, cable, wired broadband, and wireless. For example, utility poles are rented for various purposes, one of which is to install various NEs that handle mobile signals between NEs and mobile users. NEs include base stations and antennas. However, no solution exists to obtain utility pole data to determine how many utility poles exist and where such poles are located on a map so that network designers can identify utility poles for installing NEs. Summary of the Invention [Means for solving the problem]

[0005] In at least an embodiment, a method for providing utility pole management for installing network elements includes obtaining utility pole data having latitude and longitude values ​​from a plurality of sources, storing the utility pole data from the plurality of sources in a central utility pole database, presenting on a map in a graphical user interface a utility pole (plurality of utility poles) associated with at least a portion of the utility pole data based on at least the latitude and longitude values, determining a first utility pole on the map in consideration of installing a network element for providing wireless service, presenting a geographical boundary on the map for the first utility pole, the geographical boundary encompassing the candidate utility pole, and selecting a utility pole for installing a network element for providing wireless service from the candidate utility poles inside the geographical boundary.

[0006] In at least one embodiment, a device for providing utility pole management for installing network elements includes a memory storing computer-readable instructions and a processor coupled to the memory, wherein the processor is configured to execute the computer-readable instructions to obtain utility pole data having latitude and longitude values ​​from a plurality of sources, store the utility pole data from the plurality of sources in a central utility pole database, present on a map in a graphical user interface a utility pole(s) associated with at least a portion of the utility pole data based on at least the latitude and longitude values, determine a first utility pole on the map in consideration of installing a network element for providing wireless service, present a geographical boundary on the map for the first utility pole, the geographical boundary encompassing the candidate utility pole, and select a utility pole for installing a network element for providing wireless service from the candidate utility poles inside the geographical boundary.

[0007] In at least one embodiment, a non-transitory computer-readable medium having computer-readable instructions stored thereon that, when executed by a processor, cause the processor to obtain utility pole data having latitude and longitude values ​​from a plurality of sources, store the utility pole data from the plurality of sources in a central utility pole database, present on a map within a graphical user interface a utility pole(s) associated with at least a portion of the utility pole data based on at least the latitude and longitude values, determine a first utility pole on the map in consideration of installing a network element for providing wireless service, present a geographical boundary on the map for the first utility pole, the geographical boundary encompassing the candidate utility pole, and select a utility pole for installing a network element for providing wireless service from the candidate utility poles inside the geographical boundary. [Brief description of the drawings]

[0008] Aspects of the present disclosure are best understood from the following detailed description when read in conjunction with the accompanying drawings, in which: It should be noted that, in accordance with standard industry practice, various features have not been drawn to scale, and in fact the dimensions of various features may be increased or decreased for clarity of illustration.

[0009] [Figure 1] FIG. 1 is a diagram of a system for collecting data in accordance with at least one embodiment. [Diagram 2] 1 is an example of unstructured pole data from a utility company, according to at least one embodiment. [Diagram 3] 1 is an example of structured utility pole data according to at least one embodiment. [Figure 4] 1 is a flowchart of a method for selecting a utility pole for installing a network element (NE) according to at least one embodiment. [Figure 4c] 1 is a flowchart of a method for selecting a utility pole for installing a network element (NE) according to at least one embodiment. [Diagram 5] 1 illustrates a pole map graphical user interface (GUI) showing pole locations based on pole data in a central pole database according to at least one embodiment. [Figure 6] 1 illustrates a utility pole map GUI showing a nominal utility pole selected for installing a NE to establish a cell site, according to at least one embodiment. [Figure 7] 1 illustrates a utility pole get code for requesting utility pole data in accordance with at least one embodiment. [Figure 8] 1 illustrates a response 00 to a utility pole data request in accordance with at least one embodiment. [Figure 9] FIG. 1 illustrates a high-level functional block diagram of a processor-based system according to at least one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] The embodiments described herein illustrate examples of implementing different features of the subject matter provided. To simplify the disclosure, examples of components, values, operations, materials, arrangements, and the like are described below. Of course, these are examples and are not intended to be limiting. Other components, values, operations, materials, arrangements, and the like are contemplated. For example, the formation of a first feature on or above a second feature in the following description includes embodiments in which the first feature and the second feature are formed in direct contact, and includes embodiments in which an additional feature is formed between the first feature and the second feature such that the first feature and the second feature cannot be in direct contact. In addition, the disclosure repeats reference numbers and / or letters in various examples. This repetition is for the purposes of brevity and clarity, and does not in itself dictate a relationship between the various embodiments and / or configurations described.

[0011] Additionally, spatially relative terms such as "beneath," "below," "lower," "above," "upper," and the like are used herein for ease of description to describe the relationship of one element or feature to another element(s) or feature(s) as shown in the figures. The spatially relative terms are intended to encompass different orientations of the device during use or operation in addition to the orientation shown in the figures. The device may be otherwise oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors used herein interpreted accordingly.

[0012] Terms such as "user equipment," "mobile station," "mobile," "mobile device," "subscriber station," "subscriber equipment," "access terminal," "terminal," "handset," and similar terms refer to wireless devices utilized by subscribers or users of wireless communication services to receive or convey data, control, voice, video, sound, games, or data or signaling streaming. The foregoing terms are used interchangeably in this specification and the associated drawings. Terms such as "access point," "base station," "Node B," "evolved Node B (eNodeB)," next generation Node B (gNB), enhanced gNB (en(enhanced)-gNB), Home Node B (HNB), "Home Access Point (HAP)," and the like refer to components or devices of a wireless network that provide and receive data, control, voice, video, sound, games, or data or signaling streaming from a UE.

[0013] The embodiments described herein provide utility pole management for network element installation based on latitude and longitude having one or more advantages. For example, the utility pole data manager provides a graphical user interface (GUI) that helps developers and end users to obtain utility pole site data using latitude and longitude. The site locations are viewed on a map according to the latitude and longitude. The utility pole data manager is used for integration purposes to create candidate sites for installing network elements (NEs) that provide mobile communication services. The utility pole data manager provides an interface to utility pole data from different sources, thereby saving development time and providing more flexibility to developers.

[0014] FIG. 1 is a diagram of a system 100 for collecting data in accordance with at least one embodiment.

[0015] 1, the system 100 includes multiple utility pole data sources 120, 122, 124. In at least one embodiment, the multiple utility pole data sources 120, 122, 124 are different utility companies, such as electric utilities. There are many utility companies 120, 122, 124 and they are located in different regions to serve different businesses.

[0016] Data is provided in different formats by different utility companies 120, 122, 124 and collected by the pole data manager 110 via the cloud 130. The pole data manager 110 includes a display 112 that presents a graphical user interface (GUI) 114 for viewing the collected pole data. The pole data collected from the different utility companies 120, 122, 124 is collected as unstructured data and standardized. For example, in at least one embodiment, common parameters of the pole data from the utility companies 120, 122, 124 are selected for use in determining the locations to use for installing NEs. The parameters selected for use from the different utility companies 120, 122, 124 are identified and the pole data from the different utility companies 120, 122, 124 is consolidated (merged) and integrated into the central pole database 140. The central utility pole database 140 contains the latitude and longitude of utility poles from different utility companies 120 , 122 , 124 .

[0017] FIG. 2 is an example of unstructured utility pole data 200 from a utility company, according to at least one embodiment.

[0018] In FIG. 2, the unstructured utility pole data 200 includes various fields including utility name 210, utility pole number 212, state 214, city 216, utility pole latitude 218, and utility pole longitude 220. The unstructured utility pole data 200 shown in FIG. 2 includes additional data such as branch code 222, city code 224, etc. Utility pole data from different utility companies includes different data under different fields and may have more or less fields than the unstructured utility pole data 200 shown in FIG. 2. The utility pole data depends on the utility company such as NTT, KEPCO, HEPCO, etc. Different utility companies have different utility pole data categorized under different headers. However, the unstructured utility pole data 200 includes at least the utility pole latitude 218 and the utility pole longitude 220 so that the utility poles can be mapped.

[0019] FIG. 3 is an example of structured utility pole data 300 according to at least one embodiment.

[0020] In Figure 3, some fields of the pole data have been removed so that the structured pole data 300 has the same or a common header for the pole data of each utility company. The structured pole data 300 includes the pole latitude 318 and the pole longitude 320. By providing a common header for the pole data from the utilities, the structured pole data 300 can be analyzed and poles can be identified based on the utility company name. It is also possible to merge the structured pole data 300 of one utility company with the pole data of another utility company.

[0021] 4 and 4c (continued) are a flowchart 400 of a method for selecting a utility pole for installing a network element (NE) according to at least one embodiment.

[0022] In Figures 4 and 4c, the method begins by obtaining utility pole data from multiple sources S410, e.g., utility companies. Figure 4 shows that sources of utility pole data S420 include Nippon Telegraph and Telephone East Company (NTT East) S422, Tokyo Electric Power Company (TEPCO) S424, Kansai Electric Power Company (KEPCO) S426, and Hokkaido Electric Power Company (HEPCO) S428. Embodiments are not limited to these utility companies, and different embodiments include a greater or lesser number of companies.

[0023] FIG. 4 shows that the utility pole data from the utility companies S422, S424, S426, S428 includes utility pole data in different formats. The utility pole data obtained from NTT East S422 includes utility pole number, latitude, longitude S432. The utility pole data obtained from TEPCO S424 includes utility pole type, utility pole number, branch ID, area ID, and utility pole ID S434. The utility pole data obtained from KEPCO S426 includes mark name, utility pole number, latitude, longitude S436. The utility pole data obtained from HEPCO S428 includes utility pole number, latitude, longitude S438. The utility pole data is structured and consolidated (merged) into a central utility pole database S440. As new utility pole data sources become available, the new utility pole data is acquired, processed, and entered into the central utility pole database S440.

[0024] An API is called to analyze the pole data in the central pole database S442. The user searches the central pole database by latitude and longitude S444. It is determined whether the latitude and longitude are found in the central pole database S446. In response to the latitude and longitude not being found in the central pole database S448, the candidate pole is not available and the user cannot see (confirm) the pole for selecting a nominal and candidate pole for the longitude and latitude S450. It is determined whether to search for another pole by latitude and longitude S452, and in response to a decision to search for another pole by latitude and longitude S454, a new latitude and longitude for the pole is selected for searching in the central pole database S444. In response to a decision not to search for another pole by latitude and longitude S456, the process ends S490.

[0025] In response to finding the latitude and longitude in the central utility pole database S458, the user views (verifies) utility poles to select nominal and candidate utility poles for the longitude and latitude S460. Based on viewing utility poles to select nominal and candidate utility poles for the longitude and latitude S460, it is determined whether the nominal utility pole has problems or characteristics that are detrimental or unhelpful to providing wireless service S462. Utility poles that have problems include one or more of the following: the correct location of the candidate utility pole is not provided, the utility pole is located between two buildings, there is too much interference present for the utility pole, or the utility pole location is otherwise unacceptable. In response to the nominal utility pole not having problems S464, the nominal utility pole is used to install the network elements S466. The process then ends S490.

[0026] In response to the nominal pole having a problem S468, it is determined whether a candidate pole is available for consideration within a predetermined radius of the nominal pole S470. If a candidate pole is not available for consideration S472 within the predetermined radius of the nominal pole, the user selects a new latitude and longitude of the pole for searching in the central pole database S444.

[0027] In response to a candidate pole being available for consideration within a predetermined radius of the nominal pole S474, a candidate pole is selected S476. It is determined S478 whether the selected candidate pole has a problem. In response to the selected candidate pole having a problem S480, the process returns to determining whether the candidate pole is available for consideration within a predetermined radius of the nominal pole S470. In response to the selected candidate pole not having a problem S482, the selected candidate pole is used to install a network element S484. The process then ends S490. Because there are many poles provided to the central pole database by different utility companies, the probability of finding a latitude and longitude in the central pole database is very high.

[0028] FIG. 5 illustrates a pole map graphical user interface (GUI) 500 showing pole locations based on pole data in a central pole database according to at least one embodiment.

[0029] In FIG. 5, utility pole markers 510 are shown plotted on a utility pole map GUI 500 based on the latitude and longitude values ​​of the utility poles in a central utility pole database. As described above, the utility pole data in the central utility pole database used for the mapped utility poles 520 is obtained from multiple sources, e.g., utility companies. The utility pole data is structured in a common form and consolidated in the central utility pole database. As shown in FIG. 5, the mapping of utility poles 520 in the utility pole map GUI 500 is associated with a 5G utility pole Site Acquisition Request Form (SARF) 530.

[0030] The process of determining which utility pole to install the NE on includes selecting and analyzing a utility pole from the mapped utility poles 520. In response to a selection from the mapped utility poles 520 of a marker associated with the utility pole as a nominal candidate, the longitude and latitude are displayed. For example, a user selects a utility pole on the utility pole map GUI 500 from the mapped utility poles 520. In at least one embodiment, the map is Google Maps. In at least one embodiment, a map other than Google Maps is used.

[0031] FIG. 6 illustrates a utility pole map GUI 600 showing a nominal utility pole selected for installing a NE to establish a cell site, according to at least one embodiment.

[0032] In Fig. 6, a marker for a utility pole 610, a marker for a nominal utility pole 612, and a marker for a candidate utility pole 614 are shown on the top key 616. The utility pole map GUI 600 can be accessed and used anywhere. The utility pole map GUI 600 shows a mapped utility pole 620. The mapped utility pole 620 in the utility pole map GUI 600 is associated with a 5G utility pole site acquisition request form (SARF) 630.

[0033] In FIG. 6, from the mapped utility poles 620, a utility pole is selected as a nominal utility pole 640. A circle 650 is added with a predetermined radius based on the technology of the NE (e.g., whether the site is 4G, 5G, etc.). The NE includes antennas, transmitters, etc. The circle 650 represents a predetermined area covered by the NE installed on the selected nominal utility pole 640. In FIG. 6, the circle 650 has a radius based on the site being a 5G site. The coverage area of ​​the 5G site is smaller than the coverage area of ​​the 4G site because the distance the signal from the 5G site extends is shorter. The signal from the 4G site travels a longer distance and the circle 650 is larger. The radius of the circle 650 is determined by logic executed by a processor to present the utility pole map GUI 600 based on the present technology. For example, in at least one embodiment, the radius of the circle 650 is 250 meters.

[0034] The pole map GUI 600 allows for the selection of a nominal pole 640, and if the nominal pole 640 is not acceptable, candidate poles 660, 662, 664, 666, 668, 670, 672, 674, 676, 678, 680, 682, 684 within a circle 650 are considered. The nominal pole 640 is selected according to latitude and longitude. A circle 650 of a predetermined radius is centered on the nominal pole 640. Around the nominal pole 640 and within the circle 650, candidate poles 660, 662, 664, 666, 668, 670, 672, 674, 676, 678, 680, 682, 684 are displayed. In at least one embodiment, the candidate poles 660, 662, 664, 666, 668, 670, 672, 674, 676, 678, 680, 682, 684 are owned by the same utility company as the nominal pole or by a different utility company. In at least one embodiment, the candidate poles 660, 662, 664, 666, 668, 670, 672, 674, 676, 678, 680, 682, 684 are each owned by a different utility company.

[0035] The pole map GUI 600 shows poles 620 mapped from pole data provided by each utility company. Heretofore, diagrams of poles 620 of different utility companies have not been available. In response to the nominal pole 640 being identified as having problems unfavorable to the installation of NEs, poles for consideration are selected from the candidate poles 660, 662, 664, 666, 668, 670, 672, 674, 676, 678, 680, 682, 684 within the circle 650. For example, the pole 680 is selected because the nominal pole 640 has problems unfavorable to the installation of NEs. In at least one embodiment, the poles having problems include one or more of the following: the correct location of the candidate pole is not provided, the pole is located between two buildings, there is too much interference for the pole, or the location of the pole is otherwise unacceptable.

[0036] In response to selecting a candidate pole 680 for consideration, a manual review of the candidate pole 680 is performed. For example, a photo is uploaded, characteristics of the candidate pole 680 are inspected, or a checklist for filtering the candidate poles is completed.

[0037] In response to the candidate pole 680 not being suitable, a new candidate pole is selected from the candidate poles 660, 662, 664, 666, 668, 670, 672, 674, 676, 678, 682, 684. This process is repeated until an acceptable candidate pole is selected. In response to the candidate pole 680 being determined to be acceptable, the candidate pole 680 is confirmed for use in locating the NE. In response to the candidate pole 680 not being suitable, a new candidate pole is selected from the candidate poles 660, 662, 664, 666, 668, 670, 672, 674, 676, 678, 682, 684 within the circle 650. This process is repeated until an acceptable candidate pole is selected. In response to no acceptable pole being present, i.e., no other candidate pole being present, the location is removed from consideration. In Figure 6, the nominal utility pole 640 is along a road, so there are also many candidate utility poles. Therefore, it is very rare to have an unacceptable utility pole.

[0038] At least one embodiment of a method for providing utility pole management for installing network elements includes obtaining utility pole data having latitude and longitude values ​​from a plurality of sources, storing the utility pole data from the plurality of sources in a central utility pole database, presenting on a map in a graphical user interface a utility pole (plurality of utility poles) associated with at least a portion of the utility pole data based on at least the latitude and longitude values, determining a first utility pole on the map in consideration of installing a network element for providing wireless service, presenting a geographical boundary on the map for the first utility pole, the geographical boundary encompassing the candidate utility pole, and selecting a utility pole for installing a network element for providing wireless service from the candidate utility poles inside the geographical boundary.

[0039] In at least one embodiment, the utility pole data manager provides a graphical user interface (GUI) that helps developers and end users to obtain utility pole site data using longitude and latitude. The site locations are viewed on a map according to the latitude and longitude. The utility pole data manager is used for integration purposes to create candidate sites for installing network elements (NEs) that provide mobile communication services. The utility pole data manager provides an interface to utility pole data from different sources, thereby saving development time and providing more flexibility to developers.

[0040] FIG. 7 illustrates a get pole code 700 for requesting pole data, according to at least one embodiment.

[0041] In Figure 7, the pole data is associated with the interior of the boundary defined by "NELatlong" 710 and "SWLatlong" 740. The northeast latitude ("lat") is 35.16967761850738 712 and the northeast longitude ("lng") is 136.93458616733554 714. The southwest latitude ("lat") is 35.168243664202535 742 and the southwest longitude ("lng") is 136.92603528499606 744.

[0042] FIG. 8 illustrates a response 800 to a utility pole data request in accordance with at least one embodiment.

[0043] In Figure 8, the response provides the latitude and longitude of the utility pole within the bounding coordinates provided by the utility pole get code 700 of Figure 7. For example, the utility pole is within circle 650 as shown in Figure 6. The response 800 includes, for example, “id”:3391818 810, “poleUniqueId”:“129_00” 814, “branchcode”:“129” 818, “poleNumber”:“00993” 822, latitude 35.1698278921275 826, longitude 136.928326566405 830, city “TOKAI” 834, prefecture “Aichi” 838, “poleRegionId”:48 842, “polePrefectureId”:2106 846, “poleCityId”:944 850, and “companyName”:“Chubu Electric Power” 854.

[0044] In at least one embodiment, additional data is provided including, for example, "xCoordinate": -21438.103 and "yCoordinate": -92421.985. The pole data can be used to identify the source of the pole data (e.g., which company the pole belongs to) and which poles are located inside a defined boundary (as shown in FIG. 6, the boundary is shown as a circle 650). Once the pole is located in the central pole database, the GUI draws a radius circle based on the technique. Within the radius, available candidate poles from the central pole database are displayed within the circle.

[0045] FIG. 9 is a high-level functional block diagram of a processor-based system 900 in accordance with at least one embodiment.

[0046] In at least one embodiment, the processing circuit 900 provides a pole data manager for selecting a pole for installing a network element according to at least one embodiment. The processing circuit 900 uses the processor 902 to implement the pole data manager for selecting a pole for installing a network element according to at least one embodiment. The processing circuit 500 also includes a non-transitory computer-readable storage medium 904 used to implement the pole data manager for selecting a pole for installing a network element according to at least one embodiment. The storage medium 904 stores, among other things, computer program code encoded with instructions 906, i.e., executed by the processor 902, that causes the processor 902 to provide a pole data manager for selecting a pole for installing a network element according to at least one embodiment. The execution of the instructions 906 by the processor 902 represents (at least in part) a network visualization application that implements at least a portion of the methods described herein (hereinafter, the described processes and / or methods) according to one or more embodiments.

[0047] The processor 902 is electrically coupled to the computer-readable storage medium 904 via a bus 908. The processor 902 is electrically coupled to an input / output (I / O) interface 910 by the bus 908. A network interface 912 is also electrically connected to the processor 902 via the bus 908. The network interface 912 is connected to a network 914 such that the processor 902 and the computer-readable storage medium 904 connect to external elements via the network 914. The processor 902 is configured to execute the instructions 906 encoded in the computer-readable storage medium 904 to enable the processing circuit 900 to perform at least a portion of a process and / or method. In one or more embodiments, the processor 902 is a central processing unit (CPU), a multiprocessor, a distributed processing system, an application specific integrated circuit (ASIC), and / or other suitable processing unit.

[0048] The processing circuit 900 includes an I / O interface 910. The I / O interface 910 is coupled to external circuitry. In one or more embodiments, the I / O interface 910 includes a keyboard, a keypad, a mouse, a trackball, a trackpad, a touch screen, and / or cursor direction keys for communicating information and commands to the processor 902.

[0049] The processing circuit 900 also includes a network interface 912 coupled to the processor 902. The network interface 912 enables the processing circuit 900 to communicate with a network 914 to which one or more other computer systems are connected. The network interface 912 includes a wireless network interface, such as, for example, Bluetooth, Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), General Packet Radio Service (GPRS), or Wideband Code Division Multiple Access (WCDMA), or a wired network interface, such as, for example, Ethernet, Universal Serial Bus (USB), Institute of Electrical and Electronics Engineers (IEEE) 864, etc.

[0050] The processing circuit 900 is configured to receive information via an I / O interface 910. The information received via the I / O interface 910 includes one or more of instructions, data, design rules, libraries of cells, and / or other parameters for processing by the processor 902. The information is transferred to the processor 902 via a bus 908. The processing circuit 900 is configured to receive information related to a user interface (UI) via the I / O interface 910. The information is stored in the computer-readable medium 904 as a UI 922.

[0051] In one or more embodiments, one or more non-transitory computer-readable storage media 904 having stored thereon instructions (in compressed or uncompressed form) that can be used to program a computer, processor, or other electronic device to perform the processes or methods described herein. The one or more non-transitory computer-readable storage media 904 include one or more of an electronic storage medium, a magnetic storage medium, an optical storage medium, a quantum storage medium, and the like. For example, the computer-readable storage medium may include, but is not limited to, a hard drive, a floppy diskette, an optical disk, a read-only memory (ROM), a random access memory (RAM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a flash memory, a magnetic or optical card, a solid-state memory device, or other type of physical medium suitable for storing electronic instructions. In one or more embodiments using an optical disk, the one or more non-transitory computer-readable storage media 904 include a compact disk read-only memory (CD-ROM), a compact disk read / write (CD-R / W), and / or a digital video disk (DVD).

[0052] In one or more embodiments, the storage medium 904 stores computer program code 906 configured to cause the processing circuitry 900 to implement at least a portion of a process and / or method for selecting a utility pole on a map according to a longitude and latitude for installing a network element according to at least one embodiment. In one or more embodiments, the storage medium 904 also stores information such as algorithms that facilitate implementation of at least a portion of a process and / or method for selecting a utility pole on a map according to a longitude and latitude for installing a network element according to at least one embodiment. Thus, in at least one embodiment, the processor circuitry 900 implements a method for selecting a utility pole on a map according to a longitude and latitude for installing a network element according to at least one embodiment. The process of obtaining utility pole data having latitude and longitude values ​​from multiple sources, storing the utility pole data from the multiple sources in a central utility pole database, presenting utility pole(s) associated with at least a portion of the utility pole data based on at least the latitude and longitude values ​​on a map in a graphical user interface, determining a first utility pole on the map in consideration of installing a network element to provide wireless service, presenting a geographical boundary on the map for the first utility pole, the geographical boundary encompassing the candidate utility pole, and selecting a utility pole for installing a network element to provide wireless service from the candidate utility poles inside the geographical boundary provides at least the advantage of providing a utility pole data manager that presents a map of utility pole data combined from multiple sources such as utility companies on a graphical user interface, assisting developers and end users in obtaining utility pole site data and selecting utility poles for installing network elements using longitude and latitude. The site locations are viewed on the map according to the latitude and longitude. The utility pole data manager is used for integration purposes to create candidate sites for installing network elements (NEs) for providing wireless telecommunication services. The utility pole data manager provides an interface to utility pole data from different sources, thereby saving development time and providing more flexibility to developers.

[0053] Separate instances of these programs may be executed or distributed on any number of separate computer systems. Thus, although particular steps are described as being performed by particular devices, software programs, processes, or entities, this is not necessarily the case. Various alternative implementations will be appreciated by those skilled in the art.

[0054] Moreover, those skilled in the art will readily recognize that the above-described techniques can be utilized in a variety of devices, environments, and contexts. Although the embodiments have been described in language specific to structural features or methodological acts, the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claims.

Claims

1. 1. A method for providing pole management for installing network elements, comprising: acquiring utility pole data having latitude and longitude values ​​from a plurality of sources; storing the utility pole data from the plurality of sources in a central utility pole database; presenting on a map within a graphical user interface a plurality of utility poles associated with at least a portion of the utility pole data based on at least the latitude and longitude values; determining a first utility pole on the map in consideration of installing a network element for providing wireless service; presenting a geographic boundary on the map for the first utility pole, the geographic boundary encompassing the candidate utility pole; and selecting, from the candidate utility poles within the geographic boundary, a utility pole for installing the network element to provide the wireless service.

2. Obtaining the utility pole data from the plurality of sources includes: acquiring unstructured utility pole data from said plurality of sources; structuring the unstructured utility pole data from the multiple sources according to a data model to generate structured data; The method of claim 1 , further comprising aggregating the structured data into a common database for storage within the central utility pole database.

3. The method of claim 1 , wherein presenting the geographic boundary comprises presenting a circle having a predetermined radius centered on the first utility pole.

4. Presenting the circle having the predetermined radius may include: determining a technology associated with said network elements deployed to provide wireless service; and determining a radius based on the technology associated with the network element to be installed.

5. selecting, from the candidate utility poles within the geographic boundary, the utility pole for installing the network element to provide the wireless service, determining that the selected utility pole has a problem that makes it useless for providing the wireless service; selecting a replacement pole from the candidate poles within the geographic boundary; determining that the alternative utility pole is acceptable for providing the wireless service.

6. Determining that the selected utility pole has the problem of being useless for providing the wireless service includes:

6. The method of claim 5, comprising determining at least one of: the selected utility pole is not associated with a location for providing the wireless service; the selected utility pole is located between structures that attenuate signals for providing the wireless service; and the selected utility pole is subject to electromagnetic interference.

7. Presenting, on the map within the graphical user interface, a plurality of utility poles associated with at least a portion of the utility pole data based on at least the latitude and longitude values, identifying one of the plurality of utility poles as a nominal utility pole; identifying utility poles within the geographic boundary as the candidate utility poles; and identifying utility poles outside the geographic boundary as utility poles not considered for installing the network elements for providing wireless service.

8. 1. A device for providing pole management for installing network elements, comprising: a memory storing computer readable instructions; a processor coupled to the memory, the processor executing computer readable instructions to: Obtaining utility pole data having latitude and longitude values ​​from a plurality of sources; storing said utility pole data from said plurality of sources in a central utility pole database; presenting, on a map within a graphical user interface, a plurality of utility poles associated with at least a portion of said utility pole data based on at least said latitude values ​​and said longitude values; determining a first utility pole on the map in consideration of installing a network element for providing wireless service; presenting a geographic boundary on the map for the first utility pole, the geographic boundary encompassing the candidate utility pole; a processor configured to select, from the candidate utility poles within the geographic boundary, a utility pole for installing the network element to provide the wireless service; A device comprising:

9. The processor, acquiring unstructured utility pole data from said plurality of sources; structuring the unstructured utility pole data from the multiple sources according to a data model to generate structured data; 9. The device of claim 8, further configured to obtain the utility pole data from the multiple sources by: aggregating the structured data into a common database for storage in the central utility pole database.

10. The device of claim 8 , wherein the processor is further configured to present the geographic boundary by presenting a circle having a predetermined radius centered on the first utility pole.

11. The processor, determining a technology associated with said network elements deployed to provide wireless service; 11. The device of claim 10, further configured to present the circle having the predetermined radius centered on the first utility pole by: determining a radius based on the technology associated with the network element to be installed.

12. The processor, determining that the selected utility pole has a problem that makes it useless for providing the wireless service; selecting a replacement pole from the candidate poles within the geographic boundary; determining that the alternative utility pole is acceptable for providing the wireless service; 10. The device of claim 8, further configured to select the utility pole for installing the network element to provide the wireless service from the candidate utility poles inside the geographic boundary by:

13. 13. The device of claim 12, wherein the processor is further configured to determine that the selected utility pole has the problem of being useless for providing the wireless service by determining at least one of: the selected utility pole is not associated with a location for providing the wireless service, the selected utility pole is located between structures that attenuate signals for providing the wireless service, and the selected utility pole is subject to electromagnetic interference.

14. The processor, displaying, on the map within the graphical user interface, a number of utility poles associated with at least a portion of the utility pole data based on at least the latitude and longitude values; identifying one of the plurality of utility poles as a nominal utility pole; identifying utility poles within said geographic boundary as said candidate utility poles; and identifying utility poles outside said geographic boundary as utility poles not being considered for installation of said network elements for providing wireless service; The device of claim 8 , further configured to present the signal by:

15. When executed by a processor, the processor: acquiring utility pole data having latitude and longitude values ​​from a plurality of sources; storing the utility pole data from the multiple sources in a central utility pole database; presenting, on a map within a graphical user interface, a plurality of utility poles associated with at least a portion of the utility pole data based on at least the latitude and longitude values; determining a first utility pole on the map in consideration of installing a network element for providing wireless service; presenting a geographic boundary on the map for the first utility pole, the geographic boundary encompassing the candidate utility pole; and selecting, from the candidate utility poles within the geographic boundary, a utility pole for installing the network element to provide the wireless service.

16. obtaining the utility pole data from the plurality of sources, acquiring unstructured utility pole data from said plurality of sources; structuring the unstructured utility pole data from the multiple sources according to a data model to generate structured data; 16. The non-transitory computer readable medium of claim 15, further comprising aggregating the structured data into a common database for storage within the central utility pole database.

17. 16. The non-transitory computer-readable medium of claim 15, wherein presenting the geographic boundary includes presenting a circle having a predetermined radius centered on the first utility pole.

18. presenting the circle having the predetermined radius, determining a technology associated with said network elements deployed to provide wireless service; and determining the radius based on the technology associated with the network element to be installed.

19. selecting, from the candidate utility poles within the geographic boundary, a utility pole for installing the network element to provide the wireless service; determining that the selected utility pole has a problem that makes it useless for providing the wireless service; selecting a replacement pole from the candidate poles within the geographic boundary; and determining that the alternative utility pole is acceptable for providing the wireless service.

20. presenting, on the map within the graphical user interface, a number of utility poles associated with at least a portion of the utility pole data based on at least the latitude and longitude values; identifying one of the plurality of utility poles as a nominal utility pole; identifying utility poles within the geographic boundary as the candidate utility poles; and identifying utility poles outside the geographic boundary as utility poles not considered for installing the network elements for providing wireless service.

Images