Method, system, and computer program product for implementing site co-location

Abstract

A method of implementing site collocation is performed, at least in part, by at least one processor and includes obtaining first identification information (ID) of an existing site corresponding to a nominal site. The method further includes modifying a first portion of the first ID while maintaining a second portion of the first ID to obtain a second ID of a collocation candidate site to be collocated with the existing site. The method further includes using the second ID in at least one of installing the collocation candidate site as a collocated site at a physical location of the existing site or communicating with the collocated site upon completion of the installation.

Description

[Technical Field]

[0001] The present disclosure relates to telecommunications, and more particularly to site installation, for example, for expansions and / or upgrades, in communication systems. [Background technology]

[0002] Networking and telecommunications have a profound impact on everyday life, with user devices such as smartphones, laptops, tablets, gaming consoles, etc. becoming increasingly prevalent for work, entertainment, social networking, etc. To meet the growing demand for more and / or better services, coverage, bandwidth, speed, service quality, service reliability, network efficiency, etc., communication systems undergo periodic upgrades. However, the time, effort, and / or cost associated with upgrades are a consideration for communication system operators. Summary of the Invention [Means for solving the problem]

[0003] In some embodiments, a method for implementing site colocation, executed at least in part by at least one processor, includes obtaining a first identification (ID) of an existing site corresponding to a nominal site. The method further includes modifying a first portion of the first ID while maintaining a second portion of the first ID to obtain a second ID of a colocation candidate site to be colocated at the existing site. The method further includes using the second ID to at least one of installing the colocation candidate site as a colocation site at the physical location of the existing site or communicating with the colocation site upon completion of installation.

[0004] In some embodiments, a system for implementing site co-location comprises at least one processor and at least one computer-readable storage medium coupled to the at least one processor and configured to store executable instructions. The executable instructions, when executed by the at least one processor, cause the at least one processor to obtain first site information of an existing site corresponding to a nominal site. The first site information includes a first identification (ID) of the existing site. The first ID indicates a first communication technology supported by the existing site. The at least one processor is further caused to at least partially generate second site information of a co-location candidate site to be collocated with the existing site. The second site information includes a second ID of the co-location candidate site. The second ID is based on the first ID and indicates a second communication technology supported by the co-location candidate site. The second communication technology is different from the first communication technology. The at least one processor is further caused to use the second ID in at least one of instructing the collocation candidate site to be installed as a collocation site at the physical location of the existing site or communicating with the collocation site upon completion of the installation.

[0005] In some embodiments, a computer program product comprises a non-transitory tangible computer-readable storage medium storing a computer program, the computer program, when executed by at least one processor, causing the at least one processor to obtain first site information of an existing site corresponding to a nominal site. The first site information includes a first identification (ID) of the existing site. The first ID indicates a first communication technology supported by the existing site. The at least one processor is further caused to at least partially generate second site information of a colocation candidate site to be collocated with the existing site. The second site information includes a second ID of the colocation candidate site. The second ID is based on the first ID and indicates a second communication technology supported by the colocation candidate site. The second communication technology is different from the first communication technology. The at least one processor is further caused to use the second ID in at least one of instructing installation of the colocation candidate site as a colocation site at a physical location of the existing site or communicating with the colocation site upon completion of the installation.

[0006] Aspects of the present disclosure are best understood from the following detailed description when read in conjunction with the accompanying drawings. According to standard industry practice, various features are not drawn to scale. In fact, the dimensions of various features may be arbitrarily increased or decreased for clarity of illustration. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a schematic diagram of an exemplary communication system in which site collocation according to some embodiments is applicable.

[0008] [Figure 2A] FIG. 2A is a schematic diagram illustrating various screens of a user interface in a system for implementing site co-location according to some embodiments. [Figure 2B]FIG. 2B is a schematic diagram illustrating various screens of a user interface in a system for implementing site co-location according to some embodiments. [Figure 2C] FIG. 2C is a schematic diagram illustrating various screens of a user interface in a system for implementing site co-location according to some embodiments. [Figure 2D] FIG. 2D is a schematic diagram illustrating various screens of a user interface in a system for implementing site co-location according to some embodiments. [Figure 2E] FIG. 2E is a schematic diagram illustrating site IDs in a system for implementing site co-location according to some embodiments. [Figure 2Ec] FIG. 2Ec is a diagram illustrating various tables. [Figure 2F] FIG. 2F is a schematic diagram illustrating various screens of a user interface in a system for implementing site co-location according to some embodiments. [Figure 2G] FIG. 2G is a schematic diagram illustrating various screens of a user interface in a system for implementing site co-location according to some embodiments.

[0009] [Figure 3A] FIG. 3A is a schematic diagram illustrating various screens of a user interface in a system for implementing site co-location according to some embodiments. [Figure 3B] FIG. 3B is a schematic diagram illustrating various screens of a user interface in a system for implementing site co-location according to some embodiments. [Figure 3C] FIG. 3CA is a schematic diagram illustrating various screens of a user interface in a system for implementing site co-location according to some embodiments. [Figure 3D]FIG. 3D is a schematic diagram illustrating various examples of site IDs and modified site IDs in a system for implementing site co-location according to some embodiments. [Figure 3E] FIG. 3E is a schematic diagram illustrating various screens of a user interface in a system for implementing site co-location according to some embodiments. [Figure 3F] FIG. 3F is a schematic diagram illustrating various screens of a user interface in a system for implementing site co-location according to some embodiments. [Figure 3G] FIG. 3G is a schematic diagram illustrating various screens of a user interface in a system for implementing site co-location according to some embodiments. [Figure 3H] FIG. 3H is a schematic diagram illustrating various screens of a user interface in a system for implementing site co-location according to some embodiments. [Figure 3I] FIG. 3I is a schematic diagram illustrating various examples of site IDs and modified site IDs in a system for implementing site co-location according to some embodiments. [Figure 3J] FIG. 3J is a schematic diagram illustrating various screens of a user interface in a system for implementing site co-location according to some embodiments.

[0010] [Figure 3H] FIG. 3H is a schematic diagram illustrating various screens of a user interface in a system for implementing site co-location according to some embodiments. [Figure 3I] FIG. 3I is a schematic diagram illustrating site IDs and modified site IDs in a system for implementing site co-location according to some embodiments. [Figure 3J] FIG. 3J is a schematic diagram illustrating various screens of a user interface in a system for implementing site co-location according to some embodiments.

[0011] [Figure 4A] FIG. 4A is a flowchart of various processes for implementing site co-location according to some embodiments. [Figure 4B] FIG. 4B is a flowchart of various processes for implementing site co-location according to some embodiments. [Figure 4C] FIG. 4C is a flowchart of various processes for implementing site co-location according to some embodiments.

[0012] [Figure 5] FIG. 5 is a schematic block diagram of a computer system according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0013] The following disclosure includes many different embodiments or examples for implementing different features of the present subject matter. To simplify the disclosure, specific examples of components, values, operations, materials, arrangements, etc. are described below. Of course, these are merely examples and are not intended to be limiting. Other components, values, operations, materials, arrangements, etc. are contemplated. For example, a reference to forming a first feature on or above a second feature in the following description includes embodiments in which the first and second features are formed in direct contact with each other, as well as embodiments in which an additional feature is formed between the first and second features such that the first and second features are not in direct contact with each other. Additionally, the present 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 discussed. Furthermore, spatially relative terms such as “below,” “below,” “below,” “on the bottom,” “on top,” and “above” may be used herein to describe a relationship between one element or feature and another, as shown in the figures, for ease of description. 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 that may also be used herein interpreted accordingly.

[0014] In a typical situation with other approaches, upgrades may be performed in a communications system by planning, surveying, and installing support structures and communications equipment for new sites, e.g., new base stations, cell towers, access nodes, etc. Such processes can be time-consuming, laborious, and / or costly.

[0015] In some embodiments, site collocation is implemented to avoid and / or mitigate one or more described drawbacks of other approaches. In a site collocation process, equipment for a new or upgraded communications technology is installed in or on the same support structure of an existing site where equipment for a different existing communications technology is already installed. The new or upgraded communications technology constitutes a new site collocated with the existing site, but providing the new or upgraded communications technology to improve performance, customer experience, network efficiency, etc. A simple example of site collocation includes installing an additional 5G communications antenna on the cell tower of an existing 4G site, where the 4G communications antenna is already installed on the cell tower. Other examples of site collocation are within the scope of various embodiments. In at least one embodiment, site collocation allows for the omission of various steps, such as site surveys and support structure installation, thereby saving time, effort, and / or cost of the upgrade.

[0016] In some embodiments, the site collocation process includes reusing a unique site identification (ID) of an existing site by modifying some, but not all, of the existing site's site ID to obtain a unique site ID for the new collocated site. The site ID of the new collocated site is then used in the installation and / or operation of the new collocated site. In at least one embodiment, the collocation status of the new collocated site, i.e., the fact that it is collocated with an existing site, is reflected in the site ID of the new collocated site. As a result, in one or more embodiments, the site collocation process can be accelerated, simplified, and / or facilitated. Additional features and / or advantages are within the scope of various embodiments.

[0017] FIG. 1 is a schematic diagram of an exemplary communication system 100 in which site collocation is applicable in accordance with some embodiments.

[0018] In the exemplary configuration of the communication system 100 of FIG. 1, a consumer mobile terminal 104 is coupled to a cellular network 102 to receive communication services. In one example, the cellular network 102 includes multiple cells (not shown) in which cellular service is provided through corresponding base stations or access nodes. Exemplary base stations 106, 107 are shown in FIG. 1. The base stations comprise a radio access network and are coupled to a core network of the cellular network 102. An exemplary network device 108 of the core network is shown in FIG. 1. Examples of the cellular network 102 include, but are not limited to, a Long Term Evolution (LTE) network, a fifth generation (5G) network, a sixth generation (6G) network, a non-standalone (NSA) network, a stand-alone (SA) network, a Global System for Mobile Communications (GSM) network, a General Packet Radio Service (GPRS) network, a Code Division Multiple Access (CDMA) network, a Mobitex network, an Enhanced GPRS (EDGE) cellular network, a Wi-Fi (or WIFI) network, a WIMAX network, etc. An exemplary configuration of a base station includes a support structure, each having one or more cellular antennas, a set of transmitter / receiver transceivers, a digital signal processor, control electronics, and a Global Positioning System (GPS) receiver for timing (e.g., for CDMA2000 / IS-95 or GSM systems). Examples of support structures include, but are not limited to, cell towers, buildings, utility poles, indoor support structures, etc. In some embodiments, the support structure further comprises site infrastructure, including, but not limited to, primary and backup power sources, air conditioning or cooling equipment, cables, ducts, shelters, etc. Examples of mobile terminals 104 include, but are not limited to, mobile phones, tablets, media players, game consoles, personal digital assistants (PDAs), laptops, and other electronic devices configured to transmit and / or receive cellular communications to and from base stations of the cellular network 102.An exemplary hardware configuration of a mobile terminal and / or base station includes the computer system described with respect to FIG. 5 , with the addition of one or more cellular antennas and corresponding cellular transceiver circuitry. Example communication technologies for cellular communication between a base station and a mobile terminal include, but are not limited to, 2G, 3G, 4G, 5G, 6G, GSM, EDGE, WCDMA, HSPA, CDMA, LTE, DECT, WIFI, WiMAX, etc. Examples of services provided via cellular communication, referred to herein as cellular communication services, include, but are not limited to, voice calls, data, email, messages such as SMS and MMS, applications, and control signals. Example components of the core network (or network devices 108) include, but are not limited to, a serving gateway (SGW), a high-rate packet data serving gateway (HSGW), a packet data network gateway (PGW), a packet data serving node (PDSN), a mobility management entity (MME), a home subscriber server (HSS), and a policy control and rules function (PCRF). The components of the core network are coupled to each other and to base stations by one or more public and / or private networks. An exemplary hardware configuration of a core network component or network device 108 includes the computer system described with respect to FIG.

[0019] The communication system 100 further comprises a service system 110 configured to create, manage, and / or monitor various tickets (also referred to herein as workflows) within the communication system 100. An exemplary workflow 120 is shown in FIG. 1. The service system 110 creates the workflow 120 and assigns it to at least one human 122, such as a field technician or technician. The human 122 uses his or her mobile device 123 (or another computer system) to view the workflow and / or advance the workflow through various statuses as described herein with respect to the example of FIG. 2C . In some embodiments, in addition to advancing the workflow through various statuses, the human 122 performs one or more tasks required by the workflow 120. For example, the human 122 performs a site survey and collects data and / or measurements regarding one or more operations, functions, components, etc. of the cellular network 102. In the exemplary configuration of FIG. 1, the human 122 performs tasks such as surveying, installing, servicing, or checking the operation of the base station 107 according to the requirements, tasks, or steps defined in the workflow 120. As a human 122 performs the tasks required by workflow 120, the human evolves the workflow from a status with completed tasks to a next status with additional tasks to be performed until workflow 120 is completed (or otherwise aborted, e.g., canceled). In some embodiments, a workflow is assigned to more than one human for execution by one or more computer systems and / or is executed automatically, in whole or in part, in collaboration with one or more humans.

[0020] In some embodiments, service system 110 comprises one or more hardware components upon which software corresponding to the various algorithms and / or operations described herein executes. An example hardware configuration of any one or more of the components of service system 110 includes the computer system described with respect to FIG. 5. For example, each of the components of service system 110 and / or their corresponding modules includes executable instructions stored in at least one memory and executed by at least one processor. In some embodiments, one or more of the components in service system 110 and / or its subcomponents are implemented on / by a cloud platform. Other hardware configurations are within the scope of various embodiments.

[0021] The service system 110 is configured to provide a user interface (UI) to a user. In some embodiments, the UI includes a graphic user interface (GUI). The UI is visually presented to a user to assist the user in interacting with the service system 110, for example, during the site co-location process described herein. In some embodiments, an example of a visual presentation of one or more screens of the UI includes displaying the UI screen on a display such as a monitor or touchscreen. The display may be a display of a computer system implementing one or more components of the service system 110 or a remote display coupled to one or more components of the service system 110 via a network or communication link. Other methods for visually presenting information, such as projection onto a screen, or three-dimensional (3D) projection using glasses and / or other head-mounted devices, or any other method for presenting information that a user can visually perceive, are within the scope of various embodiments. For simplicity, the following description may use "display" or "displayed" as exemplary methods for visually presenting information. Other methods for visual presentation are not excluded as discussed herein. A user can interact with the displayed information by a pointing device (e.g., a mouse), a touch screen, non-touch gestures, voice commands, or other visually presented information.

[0022] Communication system 100 further comprises one or more databases, represented generally as database 130. Database 130 is configured to store workflow data generated during and / or as a result of the execution of one or more workflows, data such as site information collected / generated / entered by humans 122 and / or service system 110, and / or workflow status as described herein. In some embodiments, database 130 comprises one or more non-transitory computer-readable storage media and / or is configured as part of one or more computer systems. Other database configurations are within the scope of various embodiments. The configuration of communication system 100 described is an example. Other communication system configurations are within the scope of various embodiments.

[0023] 2A-2D and 2F-2G are schematic diagrams illustrating various screens of a user interface in a system for implementing site co-location, according to some embodiments, and FIG. 2E is a schematic diagram illustrating a site ID. In some embodiments, one or more of the UI screens of FIGS. 2A-2D and 2F-2G and / or the site ID of FIG. 2E are generated by and / or used in service system 110. Furthermore, one or more operations described herein are performed by at least one hardware processor and / or computer system in which one or more of the components and / or modules of service system 110 are implemented. For ease of explanation, such operations are referred to as being performed by the system.

[0024] In FIG. 2A , user interface screen 200A is displayed when a nominal site is added to communications system 100. In some embodiments, the site is a base station or an access node. However, other site configurations are within the scope of various embodiments. For example, in one or more embodiments, a site may be any component of communications system 100 having a support structure upon which communications equipment can be installed and / or upgraded. As described herein, in at least one embodiment, a site's support structure includes physical structures such as towers, buildings, utility poles, indoor support structures, etc., as well as site infrastructure such as primary and backup power sources (e.g., batteries), air conditioning or cooling equipment, cables, ducts, shelters, etc. In one or more embodiments, communications equipment includes, but is not limited to, one or more antennas, beam steering mechanisms / systems, transmit and receive circuitry, control circuitry, modulation circuitry, any other electronic components configured to provide communications services, and / or computer components, etc. In some embodiments, not all communications equipment at a site is installed on towers, buildings, utility poles, etc. In one example, some of the communications equipment at a site is installed within an enclosure (shelter) or on the ground in association with or connected to the site infrastructure.

[0025] A nominal site is a location or reference point where a site is planned to be installed, constructed, or built. In some embodiments, the nominal site is determined by a human, e.g., an engineer, and / or by a computer system using a planning tool (e.g., planning software). In one example, the planning tool is configured to determine the best possible location for the nominal site, taking into account one or more factors, including, but not limited to, the communications technology offered or supported, the intended coverage (e.g., considering the coverage area of ​​adjacent cells or sites), the estimated number of subscribers or customers to be served by the site, etc.

[0026] In the example configuration of FIG. 2A , screen 200A shows various information for the nominal site being added, such as nominal ID 201, branch ID 202, nominal unique ID 203, pole ID 204, latitude 205, longitude 206, and nominal name 207. In some embodiments, latitude 205 and longitude 206 are provided by a planning tool. Nominal name 207 is the site name of the nominal site. Nominal unique ID 203 is a unique ID for the nominal site, generated, for example, by at least one processor. 2A , the nominal unique ID 203 “129_01X371_35.1716782417182_136.938299917042” is generated by combining the branch ID 202 “129,” the nominal name 207 “01X371,” the latitude 205 “35.1716782417182,” and the longitude 206 “136.938299917042.” Other methods or rules for generating the nominal unique ID 203 are within the scope of various embodiments. The screen 200A further includes a cancel button 208 for aborting the nominal site addition process and an add button 209 for proceeding to add the nominal site.

[0027] In FIG. 2B , user interface screen 200B shows a map 210 of an area including a nominal site 211. The site type 212, “5GmmW Pole,” of nominal site 211 indicates the communications technology offered, i.e., “5GmmW.” Map 210 includes multiple existing physical structures. In the exemplary configuration of FIG. 2B , the existing physical structures include utility poles (hereinafter “poles”) 214-217. In one example, information about poles 214-217 is obtained from a power company and stored in database 130 for access by service system 110. For ease of explanation, utility poles are used as examples of existing physical structures and / or support structures for site installation. Other types of existing physical structures and / or support structures, such as cell towers, buildings, indoor support structures, etc., are within the scope of various embodiments.

[0028] Some of the poles, e.g., pole 217, are unavailable for site installation (i.e., installation of at least the site's communications equipment). The remaining poles 214-216 are available for site installation. In an ideal or best-case scenario, where an available pole is found that matches the nominal site 211 and meets one or more requirements, that pole is selected for site installation, and the candidate site selection process described herein is omitted. However, in practice, the nominal site 211 may not match any of the available poles. In such a situation, available poles 215 and 216 within a circle 213 centered on the nominal site 211 are candidates for site installation and are referred to herein as candidate sites. The remaining available pole outside the circle 213, i.e., pole 214, is not considered for site installation because it is too far from the desired location of the nominal site 211. The radius of the circle 213 corresponds to the maximum allowable distance between the nominal site 211 and the location where the site should actually be installed. The radius of circle 213 depends on various factors such as coverage, quality of service (QoC), transmit power, etc. In examples, the radius of circle 213 is 1 m, 15 m, or 30 m. Other values ​​for the radius of circle 213 are within the scope of various embodiments. As a result of the candidate site selection process described herein, pole 216 is selected as the final candidate site where site installation will occur.

[0029] In Figure 2C, screen 200C of the user interface includes an exemplary workflow 219 for a candidate site selection process. In some embodiments, the workflow configuration of workflow 219 includes one or more Extensible Markup Language (XML) documents to be executed by a workflow engine. In the exemplary configuration of Figure 2C, workflow 219 conforms to the Business Project Management Notation (BPMN) specification. Other workflow configurations and / or specifications and / or programming languages ​​or codes are within the scope of various embodiments.

[0030] Workflow 219 includes multiple elements 220-234 arranged in an order determined by a user and / or a workflow template. Elements 220-234 are connected to one another by multiple connectors (unnumbered) to form a flowchart-type diagram describing a corresponding sequence of items to be performed by one or more humans and / or systems (e.g., mobile device 123, service system 110, or at least one processor in another computer system). There are several types of elements in workflow 219. For example, elements 222, 224, and 226 are user tasks, each represented by a person icon. In some embodiments, a user task is an activity or work that can be performed or is performed by a human. In another example, elements 225, 227, and 231 are gateways. In some embodiments, a gateway defines a situation in which several options are available and a human and / or system must select one of the options to proceed. The described workflow configuration is an example. Other workflow configurations using different types of elements, such as different connections and / or events, other types of gateways and / or tasks, are within the scope of various embodiments.

[0031] Workflow 219 begins at element 220 where a nominal site has been finalized. In some embodiments, the latitude and longitude of the nominal site are output by a planning tool, and one or more other items of information related to the nominal site are provided by a human and / or a system to add / finalize the nominal site, as described with respect to FIGS. 2A-2B.

[0032] Element 221 performs one or more operations in a process called a technical site survey (TSS). For example, a field technician travels to the physical location of the finalized nominal site to determine whether a pole or candidate site at or near the nominal site (as described with respect to FIG. 2B ) is suitable for site installation. In at least one embodiment, the field technician obtains a list of available candidate sites within a predetermined distance (e.g., the radius of circle 213) from the nominal site. For example, the field technician executes software or a script or an application programming interface (API) call to access a database of utility poles (or other types of physical structures and / or support structures). The database is provided to or accessible through service system 110. The executed software, script, or API call returns a list of available candidate sites within a predetermined distance (e.g., 15 m) from the nominal site. The field technician travels to the physical location of the nominal site and surveys each of the available candidate sites, for example, starting with the candidate site closest to the nominal site.

[0033] Numerous factors, conditions, and steps are considered / employed during the TSS process at each candidate site. For example, a field engineer may verify whether the existing pole at the candidate site is of an appropriate height (e.g., a particular transmitter or transceiver must be installed at least 20 meters from the ground). The field engineer may check whether the candidate site is physically accessible to workers for installation at that specific height, and / or whether the azimuth angle of the transmitter can be maintained at a specific level when installed at the candidate site, and / or whether there are buildings or obstacles in a specific direction that may interfere with the transmitter's signal. The field engineer or another person may check whether a permit is required to access and / or perform installation at the candidate site (e.g., potentially the top of a building), and / or whether an owner (e.g., a building owner) agrees to lease the candidate site (e.g., the roof of a building), and / or whether a zoning permit or building permit is required or can be secured for installation at the candidate site. If the current candidate site is found to be unsatisfactory during the TSS process, the next candidate site is considered. The described list of actions to be performed in the TSS process is an example. Other operations for the TSS process are within the scope of various embodiments.

[0034] In elements 222 and 223, a TSS report (TSSR) is created and submitted to the final stage of the TSS process. For example, the TSSR indicates candidate sites that have been found to be suitable for installation at or near the nominal site. Candidate sites near the nominal site are understood to be candidate sites within a predetermined distance from the nominal site, as described with respect to FIG. 2B.

[0035] In element 224, the TSSR is considered for approval, for example, by a first administrator.

[0036] If, at element 225, the first administrator finds the TSSR to be defective, the process returns to element 222 for correction and / or updating of the TSSR. If the first administrator finds the TSSR satisfactory and approves the TSSR, the process proceeds to element 226.

[0037] In element 226, the TSSR is considered for approval by a second manager, for example, at a higher level or in another department.

[0038] If, in element 227, the second administrator finds the TSSR to be flawed but correctable, the process returns to element 224 for correction and / or updating of the TSSR. If the second administrator finds a satisfactory TSSR and approves the TSSR, the process proceeds to element 228. In a third situation, for example, if all available candidate sites around the nominal site are found to be unsuitable, the second administrator decides to withdraw the nominal site, and the process proceeds to element 231.

[0039] In element 228, the TSSR is marked as approved, and candidate sites indicated in the approved TSSR as suitable for the installation of the nominal site are considered final candidate sites.

[0040] At element 229, a TSSR application report is issued.

[0041] In element 230, various operations are performed at the final candidate site, for example, to prepare for or perform installation of support structures, site infrastructure, and / or communications equipment.

[0042] In element 231, i.e., once it is decided that no further construction (e.g., base station or access node) at the nominal site will be considered, several actions occur in elements 232, 233, 234 to correspondingly withdraw the nominal site, notify the relevant parties of the decision to withdraw the nominal site, and terminate activity (e.g., investigation) at the nominal site.

[0043] While workflow 219 is being implemented or executed, different statuses of various stages (or elements) are visually presented in correspondingly different distinctive formats, e.g., different colors. In the exemplary configuration of FIG. 2C , stages or elements 220 and 221 are completed and displayed in green, stage or element 222 is currently running (i.e., active) and displayed in blue, and the remaining stages or elements are new (i.e., not yet started / opened) and displayed in a neutral color, e.g., white. Alternatively, the progress and / or status of various stages of workflow 219 can be monitored on a separate screen (not shown) that does not include workflow 219. The described workflow 219, including various elements, is an example. Other workflows for candidate site selection are within the scope of various embodiments.

[0044] In FIG. 2D , screen 200D of the user interface illustrates a method for downloading site information for a candidate site that corresponds to (i.e., is at or near) a nominal site. For example, when download button 243 is selected or operated by a user, an API call is made to access a database of utility poles (or other types of physical structures and / or support structures) to return a list of available candidate sites within a predetermined distance (e.g., 15 m) from the nominal site. The list can include multiple candidate sites. For simplicity, screen 200D shows one candidate site 249 returned from the database. The other site 248 displayed in screen 200D is the nominal site itself. The site information for candidate site 249 includes latitude 244 (abbreviated), longitude 245 (abbreviated), pole name 246, and distance from the nominal site 247 (in meters). The full latitude and longitude of candidate site 249 are also included in its pole name, i.e., "35.1716982484451" and "136.938445433287." In one example, nominal site 248 corresponds to site 211 in Figure 2B, and candidate site 249 corresponds to pole 216 in Figure 2B. Once candidate site 249 is selected as a final candidate site, as described with respect to Figure 2C, a unique site ID is generated for final candidate site 249, as described with respect to Figure 2E.

[0045] 2E is a schematic diagram illustrating a site ID 250 of a final candidate site in a system for implementing site co-location, according to some embodiments. The site ID 250 includes a plurality of symbols 251-259. In one or more embodiments described herein, each of the symbols 251-259 is alphanumeric. However, other symbols, such as Chinese characters or non-alphanumeric characters, are within the scope of various embodiments.

[0046] Symbol 251 designates the design or operation of the finalist site. For example, symbol 251 designates the operator of the finalist site, e.g., the telecommunications company that operates the finalist site. Examples of names of various operators and corresponding codes are detailed in table 261. For example, if symbol 251 contains the letter or code R, it indicates that the operator of the finalist site is Operator R.

[0047] Symbol 252 designates the vendor that will work on the shortlisted site, e.g., perform site installation at the shortlisted site. Examples of various vendor names and corresponding codes are detailed in table 262. For example, if symbol 252 contains the letter or code A, it indicates that the vendor associated with the shortlisted site is Vendor A.

[0048] Symbol 253 indicates the region in which the final candidate site is physically located. Examples of various region names and corresponding codes are detailed in Table 263. In these examples, the region is in Japan and is referred to as the Jurisdiction. For example, if symbol 253 contains the letter or code C, it indicates that the final candidate site is physically located within the Tokai region or Jurisdiction (Japan).

[0049] Symbols 254 and 255 together specify a subregion in which the final candidate site will be physically located. A subregion is a smaller region within the region specified by symbol 253. Examples of various subregion names and corresponding codes are detailed in table 264. For simplicity, table 264 is partially shown in FIG. 2E, and table 264 includes other subregions and corresponding codes not shown. In these examples, the subregions are in Japan and are called prefectures. For example, if symbols 254 and 255 together indicate code 23, this indicates that the final candidate site will be physically located in Aichi Prefecture (Japan), a prefecture within the Tokai Jurisdiction. Symbols 253-255 collectively specify information about the physical location of the final candidate site. Other types of regions and subregions are within the scope of various embodiments. For example, in one or more embodiments applicable to the United States, regions are states and subregions are counties.

[0050] Symbol 256 specifies the class of the final candidate site. In some embodiments, this class is defined by the site information of the nominal site. Examples of names and corresponding codes for various classes are detailed in table 266. For example, if symbol 256 contains the letter or code 2, it indicates that the class of the final candidate site is Outdoor Micro.

[0051] Symbol 257 designates the frequency band of the final candidate site. In some embodiments, this frequency band is defined by the site information of the nominal site. Examples of names and corresponding codes for various frequency bands are detailed in table 267. For example, if symbol 257 contains the letter or code 3, it indicates that the frequency band of the final candidate site is 28G (28 GHz).

[0052] A frequency band is one example of a communication technology supported by a site (e.g., a base station or an access node). If a site, i.e., its communication equipment, is configured to support or perform communications at a higher frequency band, communication speeds will be faster and services will be provided to customers with a different level of experience and / or quality. Other examples of communication technologies supported by a site are within the scope of various embodiments. For example, in some embodiments, the communication technology supported by a site includes one or more of a network generation (e.g., 3G, 4G, 5G, 6G, etc.), an antenna design (e.g., unidirectional, omnidirectional, etc.), etc. If a site is upgraded or co-located with a new or different communication technology described herein, the communication technology conversion / upgrade may be a network generation conversion / upgrade (e.g., from 4G to 5G), and / or an antenna design conversion / upgrade (e.g., from a unidirectional antenna to an omnidirectional antenna), and / or a frequency band conversion / upgrade (with or without conversion to a different network generation). The listed examples of communication technologies are non-exhaustive.

[0053] According to some embodiments, in addition to communication technology, network generations are also considered. One network generation differs from another network generation in one or more aspects, including, but not limited to, frequency spectrum, peak (or maximum) speed, latency, connection density (e.g., the number of simultaneously serviceable users within a unit area), etc. Some examples of different network generations are provided herein: 3G, 4G, 5G, 6G, etc. Other network generations are within the scope of various embodiments. For example, Wi-Fi is a different network generation from 3G, 4G, 5G, and 6G. An example of site co-location within the same network generation but with different communication technologies is described with reference to Figures 3D-3G. Further examples of site co-location with different network generations, and of course with different communication technologies, are described with reference to Figures 3H-3J.

[0054] A series of symbols 258, 259 designates a sequence number for identification and / or management purposes. In some embodiments, this sequence number is generated automatically by the system.

[0055] The described site ID 250 is an example. Other site IDs are within the scope of various embodiments. For example, each of the design / operation, vendor, region, class, and frequency band may be represented by two or more symbols, and / or a subregion may be represented by two other symbols, and / or the sequence number may include other than six symbols. In some embodiments, all symbols in the site ID 250 are automatically generated by the system. In at least one embodiment, at least a portion of the site ID 250 is provided or designated by a human.

[0056] In FIG. 2F, a user interface screen 200F shows various site information items 270-274 for the final candidate site 249. In particular, the final candidate site 249 is assigned the following site ID 273, "RAC2323000686," which corresponds to the site ID 250 described with reference to FIG. 5E. The site ID 273, "RAC2323000686," indicates the following information about the final candidate site 249: operator R, vendor A, physically located in the Tokai region (jurisdiction) and the Aichi subregion (prefecture), class 2 (Outdoor Micro), frequency band 28 GHz, and sequence number 000686. Other site information items for the final candidate site 249 include a TSS status 271, comments 272, and a photo 274 of the actual site at the final candidate site 249. One or more of the site information items 270 are automatically generated or input by the system from a database (e.g., database 130). Comments 272 and photos 274 are provided by humans, such as field technicians. The site information items described are examples. Other possible items in the site information are within the scope of various embodiments.

[0057] In FIG. 2G , screen 200G of the user interface illustrates sites created or managed by the system. For simplicity, nominal site 281 and corresponding finalist site 282 are shown in screen 200G, while other sites are omitted. Nominal site 281 corresponds to nominal site 248 and / or 211 and is shown in the corresponding row of screen 200G. Corresponding finalist site 282 corresponds to finalist site 249 and / or 216 and is shown in the corresponding row of screen 200G. Various information items are shown for each site, including site name / ID 283, phase 284, stage 285, site type 286, region 287, subregion 288, and vendor 289. When a corresponding action icon 290 is selected, a pop-up menu, for example, displays one or more actions to be performed on the site.

[0058] Nominal site 281 has site name 291 "01X371" and unique site ID 292 "129_01X371_35.1716782417182_136.938299917042," which corresponds to nominal name 207 and nominal unique ID 203 described with respect to Figure 2A. Nominal site 281 also has site type "5 GmmW Pole," which corresponds to site type 212 described with respect to Figure 2B.

[0059] Final candidate site 282 has a site name 293 corresponding to the pole name of candidate site 249 described with reference to FIG. 2D . Final candidate site 282 further has a unique ID 294, “RAC2323000686,” as described with reference to FIG. 2F . Final candidate site 282 also has a site type, “5G mmW Pole Site,” generated based on the site type, “5G mmW Pole,” of nominal site 281. Nominal site 281 is a planned site. The “Site” portion of the site type of final candidate site 282 indicates that the final candidate site is an actual site corresponding to the planned nominal site and is configured / installed to provide communication services. As described with reference to FIGS. 2F-2G , site information for nominal site 281 and the corresponding final candidate site 282 is stored in a database, such as database 130. Site installation is performed at the physical location of final candidate site 282, installing communications equipment with the necessary support structures or site infrastructure, and configuring final candidate site 282 as an operational site providing communications services to customers. For example, the system directs site installation at final candidate site 282 according to the site information of final candidate site 282. Once site installation is complete, final candidate site 282 is referred to as the existing site. In some embodiments, a unique ID, e.g., "RAC2323000686," is used to identify final candidate site 282 during site installation and / or during communication by / with the existing site after site installation is complete.

[0060] 3A-3C, 3E-3H, and 3J are schematic diagrams illustrating various screens of a user interface, and 3D and 3I are schematic diagrams illustrating various examples of site IDs and modified site IDs in a system for implementing site co-location, according to some embodiments. In some embodiments, one or more of the UI screens of FIGS. 3A-3C, 3E-3H, and 3J and / or the site IDs of FIGS. 3D and 3I are generated and / or used by service system 110 in the co-location process. Furthermore, one or more operations described herein are performed by at least one hardware processor and / or computer system on which one or more of the components and / or modules of service system 110 are implemented. For clarity, such operations are referred to as being performed by the system.

[0061] In FIG. 3A , screen 300A of the user interface is displayed at the start of the colocation process. Screen 300A is an example of a first input area for receiving user input of a nominal site and the colocation process (or workflow) to be executed for the nominal site. Specifically, screen 300A allows a user to input and / or search for nominal sites that meet specific criteria. Screen 300A includes drop-down menus 301, 302, and 303 that allow a user to select various menu items (not shown) to narrow the search corresponding to site type, site technology, state (or sub-region), etc. Alternatively or additionally, a user can use search field 304 to directly search for a desired nominal site based on site ID. One or more nominal sites that correspond to the selected menu item (not shown) of drop-down menus 301, 302, and 303 and / or that satisfy the search query entered by the user in search field 304 are displayed in area 306. For clarity, nominal site 308 is displayed in detail in area 306, while the other nominal sites in area 306 are omitted. In the example of Figure 3A, nominal site 308 corresponds to nominal site 281 and has the same site name "01X371" and the same unique site ID "129_01X371_35.1716782417182_136.938299917042" as nominal site 281. Screen 300A shows that nominal site 308 (i.e., nominal site 281) has been selected by the user.

[0062] Screen 300A further includes a search field 305 that allows a user to search for a desired project or workflow to be executed for the selected nominal site 281. Area 307 displays one or more projects that satisfy the search query entered by the user in search field 305. For clarity, colocation workflow 309 “5G Sub6 Pole Collocation” in area 307 is displayed in detail, while other projects or workflows in area 307 are omitted. Screen 300A indicates that colocation workflow 309 has been selected by the user. When the user proceeds by operating or selecting item 310 on screen 300A, colocation workflow 309 is executed for nominal site 281. In this example, the site type “5G mmW Pole” selected via drop-down menu 301 indicates that the network generation of nominal site 281 is 5G, and colocation workflow 309 “5G Sub6 Pole Collocation” indicates that the network generation of the candidate colocation site to be collocated with nominal site 281 is also 5G. In other words, this is an example of site co-location within the same network generation, i.e., 5G, but with different communication technologies, i.e., a 5G Sub6 (below 6 GHz) site will be co-located with a 5G mmW (mmWave above 24 GHz) site.

[0063] In FIG. 3B , screen 300B of the user interface is displayed, allowing a user to download or obtain site information for a colocation candidate site corresponding to a selected nominal site 281 by operating or selecting item 312 on screen 300B. For example, an API call is made to access database 130 to retrieve site information for an existing site corresponding to the selected nominal site 281. The existing site corresponding to the selected nominal site 281 serves as the basis for configuring a colocation candidate site to be colocated with the existing site. Screen 300B is an example of a second input area, which is visually presented upon user input (or selection) of nominal site 308 and colocation workflow 309 in the first input area of ​​screen 300A and receives user instructions to search for an existing site corresponding to the nominal site and obtain site information for the existing site.

[0064] In FIG. 3C, a user interface screen 300C is displayed to show the download result, i.e., the downloaded site name 314 of the existing site. In the example of FIG. 3C, the site name 314 of the collocation candidate site corresponds to the selected nominal site 281 and is the same as the site name of the site 282 that became the existing site after site installation was completed, as described with reference to FIGS. 2A-2G. The existing site 282 serves as the basis for configuring the collocation candidate site. In addition to the displayed site name, other items in the site information of the existing site 282 are also downloaded or obtained, as described with reference to FIG. 2F. The downloaded or obtained site information includes the unique site ID 250 of the existing site 282, which is partially reused and partially modified to obtain the site ID of the collocation candidate site, as described with reference to FIGS. 3D and 3I.

[0065] In some embodiments, if the nominal site selected or entered by the user on screen 300A does not yet have a corresponding existing site, the system is configured to search for an existing site (e.g., an operational site with already constructed support structure and / or site infrastructure) that is closest to the selected nominal site and meets one or more predetermined conditions, such as those defined in the colocation workflow 309. The search is performed in database 130 in a manner similar to that described with respect to FIG. 2A , except that the search returns a list of one or more existing sites (not just utility poles) within a predetermined distance from the selected nominal site. In the returned list, the existing site closest to the selected nominal site is considered first to determine whether it meets one or more predetermined conditions, such as whether there are any tall buildings around the existing site that may obstruct wireless signals. If the nearest existing site meets the predetermined conditions, it is selected as a colocation candidate site; if not, the next-closest existing site in the returned list is considered to determine whether it meets the predetermined conditions and can be selected as a colocation candidate site, and so on. The co-location candidate sites determined in this process are further processed in the example of site co-location within the same network generation but with different communication technologies, as described with respect to Figures 3D-3G.

[0066] FIG. 3D is a schematic diagram showing the site ID 250 of a final candidate site that becomes an existing site 282 after completion of site installation at the final candidate site, in accordance with some embodiments, and the site ID 350 of a colocation candidate site 380 that is to be collocated at the same physical location as the existing site 282, e.g., on the same support structure.

[0067] The site ID 250 of the existing site 282 includes a plurality of symbols 251-259, as described with reference to Figure 2E. In the example of Figure 3D, specific characters are shown for the corresponding symbols 251-259, corresponding to the site ID "RAC2323000686" described with reference to Figure 2F.

[0068] Site ID 350 of collocation candidate site 380 includes multiple symbols 351-359. In this example of site collocation within the same network generation, symbols 351-359 correspond to symbols 251-259 of site ID 250. The specific letters or codes of symbols 351-359 are defined in tables 261-267 described with respect to Figure 2E.

[0069] In some embodiments, site ID 350 of collocation candidate site 380 is obtained by modifying a portion of site ID 250 but maintaining another portion of site ID 250. For example, the portion of site ID 250 that remains in site ID 350 includes information about the physical location of existing site 282 because collocation candidate site 380 and existing site 282 are to be colocated. Thus, the characters in symbols 253-255 of site ID 250 are the same as the characters in symbols 353-355 of site ID 350. The portion of site ID 250 that remains in site ID 350 further includes a class symbol. Thus, the characters in symbol 256 of site ID 250 are the same as the characters in symbol 356 of site ID 350.

[0070] 3D , the letters in symbol 251 of site ID 250 are the same as the letters in symbol 351 of site ID 350, indicating that the same operator operates both existing site 282 and collocation candidate site 380. In some embodiments, the letters in symbol 251 of site ID 250 are different from the letters in symbol 351 of site ID 350, indicating that different operators operate existing site 282 and collocation candidate site 380.

[0071] 3D , the characters in symbol 252 of site ID 250 are different from the characters in symbol 352 of site ID 350, indicating that different vendors are associated with existing site 282 and candidate co-location site 380. In some embodiments, the characters in symbol 252 of site ID 250 are the same as the characters in symbol 352 of site ID 350, in which case the same vendor is associated with both existing site 282 and candidate co-location site 380.

[0072] The portion of site ID 250 that was modified to obtain the corresponding portion of site ID 350 includes information regarding the different communication technologies supported by existing site 282 and colocation candidate site 380, respectively. In the example of FIG. 3D , the character in symbol 257 of site ID 250 and the character in symbol 357 of site ID 350 are different, indicating that existing site 282 and colocation candidate site 380 support different communication technologies. Specifically, with reference to table 267 of FIG. 2E , the character “2” in symbol 357 of site ID 350 indicates that the frequency band of colocation candidate site 380 is 3.7 GHz. This information is consistent with and defined by colocation workflow 309, which targets the colocation of 5G Sub-6 (below 6 GHz) sites. The character "3" in symbol 257 of site ID 250 indicates, with reference to table 267 in FIG. 2E, that the frequency band of existing site 282 is 28 GHz, i.e., a communication technology that is different from the sub 6 GHz communication technology of collocation candidate site 380.

[0073] The portion of site ID 250 that is modified to obtain the corresponding portion in site ID 350 includes symbols 258-259, which specify the sequence number of site ID 250. The corresponding sequence number of site ID 350 includes symbols 358-359, which correspond to symbols 258-259. One or more of symbols 359 in site ID 350 are different from the corresponding one or more of symbols 259 in site ID 250. That is, the sequence number of site ID 350 (e.g., "000900") is different from the sequence number of site ID 250 (e.g., "000686"). The total number of symbols in site ID 350 is the same as the total number of symbols in site ID 250. As a result, in at least one embodiment, the system does not require significant conversion to accommodate a new or changed format of site ID 350.

[0074] In the example of Figure 3D, the collocation candidate site 380 is assigned a unique site ID "REC 2322000900." This site ID indicates the following information about the collocation candidate site 380: operator R, vendor E, physically located in the Tokai region (jurisdiction) and the Aichi sub-region (prefecture), class 2 (Outdoor Micro), frequency band 3.7 GHz, and sequence number 000900. To indicate the collocation status of the collocation candidate site 380 and the existing site 282, a collocation flag is generated by the system, as described with respect to Figure 3G.

[0075] In some embodiments, the site ID 350 of the collocation candidate site 380 is automatically generated by the system. In at least one embodiment, the site ID 350 of the collocation candidate site 380 is specified, in whole or in part, by a user. In some embodiments, site installation is performed at the physical location of the existing site 282, and communications equipment of the collocation candidate site 380 is installed on the support structure and / or using the site infrastructure of the existing site 282. The communications equipment of the collocation candidate site 380 supports a communications technology different from the communications technology supported by the communications equipment of the existing site 282. The installed communications equipment of the collocation candidate site 380 configures the collocation candidate site 380 as an operational site providing communications services to customers using a communications technology different from that supported by the existing site 282. For example, the system directs site installation at the collocation candidate site 380 according to the site information of the collocation candidate site 380. When site installation is complete, the collocation candidate site 380 may be referred to as a co-located site. In some embodiments, the unique site ID 350 of the colocation candidate site 380 is used to identify the colocation candidate site 380 during site installation at the same physical location as the existing site 282 and / or during communication by / with the colocated site after site installation is complete.

[0076] In FIG. 3E, screen 300E of the user interface shows various site information 370-375 for colocation candidate site 380. Screen 300E is similar to screen 200F and includes various site information items 370-375 for colocation candidate site 380. Site information items 370-374 correspond to site information items 270-274 described with reference to FIG. 2F. In particular, colocation candidate site 380 is assigned site ID 373, which corresponds to site ID 350 described with reference to FIG. 3D. Other site information items for colocation candidate site 380 include TSS status 371, comments 372, a photo 374 of the actual site at colocation candidate site 380, and site type 375. One or more of site information items 370 are automatically generated or entered by the system from a database (e.g., database 130). Comments 372 and photo 374 are provided by a human, such as a field technician. Site type 375 "5G Sub6 Pole Site" corresponds to and is defined by colocation workflow 309, which targets the colocation of a 5G Sub6 pole. The site information items described are examples. Other possible items in the site information are within the scope of various embodiments.

[0077] In FIG. 3F, screen 300F of the user interface shows sites created or managed by the system. Screen 300F is similar to screen 200G and includes the various items 281-294 described with reference to FIG. 2G. For clarity, screen 300F shows nominal site 281, existing site 282 corresponding to nominal site 281, and collocation candidate site 380 corresponding to nominal site 281 and colocated with existing site 282, but omits other sites. Compared to screen 200G, screen 300F also shows collocation candidate site 380. The site name 381 of collocation candidate site 380 is the same as the site name 293 of existing site 282 because collocation candidate site 380 and existing site 282 are colocated in the same physical location. The site ID 382 of the collocation candidate site 380 corresponds to the site ID 350 and is obtained by modifying the site ID 294 / 250 of the existing site 282 described in FIG. 3D. As described with respect to FIGS. 3E-3F, the site information of the collocation candidate site 380 is stored in a database, such as database 130. Site installation is performed at the physical location of the existing site 282, and communication equipment of the collocation candidate site 380 is installed on and / or using the support structure of the existing site 282. For example, the system directs site installation at the existing site 282 according to the site information of the collocation candidate site 380. Once the site installation is complete, the collocation candidate site 380 becomes an operational site and is referred to as a collocated site. In some embodiments, the unique ID 350, for example, "REC23222000900," is used to identify the colocation candidate site 380 during site installation at the physical location of the existing site 282 and / or during communication by / with the colocation site after site installation is complete.

[0078] In FIG. 3G , user interface screen 300G shows basic details of existing site 282, including its site name 293 and site ID 294, the site ID 292 of the corresponding nominal site 281, the site ID 382 of the co-located site (or pre-site co-location candidate site) 380, physical location information 393, and a co-location flag 396. The physical location information 393 includes the latitude and longitude of the existing site 282 (or pre-site co-location candidate site 249), as described in FIG. 2D . The co-location flag 396 may be Yes or No depending on whether or not there is a site collocated at the existing site 282. In the example of FIG. 3G , the co-location flag 396 is Yes, corresponding to the presence of the co-located site (or co-location candidate site) 380 at the existing site 282. In some embodiments, the co-location flag 396 “Yes” is automatically generated by the system, for example, when the co-location workflow 309 is executed.

[0079] As described herein, Figures 3D-3G provide examples of site co-location within the same network generation but with different communication technologies. Further examples of site co-location with different network generations and with different communication technologies will now be described with respect to Figures 3H-3J.

[0080] In some embodiments, a site colocation process with a different network generation also begins with a screen similar to screen 300A of FIG. 3A , except that the user input of a nominal site and the colocation process (or workflow) to be executed for the nominal site include a different network generation. For example, a user selects a 4G Outdoor Small Cell (ODSC) site as the nominal site via drop-down menu 301 and / or input area 306 and further selects a 5G mmW colocation process (or workflow) via input area 307 of screen 300A. As a result, a colocation process is executed to colocate a 5G mmW site with an existing 4G ODSC site. The colocation process then proceeds to allow the user to download or obtain site information for existing sites corresponding to the nominal site, as described with respect to FIGS. 3B and 3C .

[0081] In FIG. 3H, a screen 300H of the user interface is displayed to show some details of the site information of an existing site 332 corresponding to a nominal site selected by a user input. Specifically, screen 300H shows that the existing site 332 has a site name 323 and a site ID 324 that correspond to the site name 293 and site ID 294 described in connection with FIGS. 3F-3G. Screen 300H also shows a unique site ID 322 of the nominal site selected by the user and corresponding to the existing site 332. The unique site ID 322 is similar to the unique site ID 292 described in FIGS. 3F-3G. Screen 300H also shows a site type 325 of the existing site 332: "ODSC," i.e., the existing site 332 is an existing 4G ODSC site.

[0082] FIG. 3I is a schematic diagram showing the site ID 324 of an existing site 332 and the site ID 360 of a collocation candidate site 340 to be collocated in the same physical location as the existing site 332, e.g., on the same support structure, according to some embodiments.

[0083] The site ID 324 of the existing site 332 includes a plurality of symbols 251-259, as described with respect to Figure 2E. In the example of Figure 3I, the specific characters corresponding to the site ID 324 are "RAC2321000478" and are shown relative to the corresponding symbols 251-259.

[0084] Site ID 360 of collocation candidate site 340 includes multiple symbols 351-357, 348, and 359. Symbols 351-357 and 359 correspond to symbols 251-257 and 259 of site ID 324. Specific letters or codes for symbols 351-357 are defined in tables 261-267, described with respect to FIG. 2E. Specific examples of letters or codes for symbol 348 are defined in table 368, as described herein.

[0085] In some embodiments, site ID 360 of collocation candidate site 340 is obtained by modifying a portion of site ID 324 but maintaining another portion of site ID 324. For example, the portion of site ID 324 that remains in site ID 360 includes information about the physical location of existing site 332 because collocation candidate site 340 and existing site 332 are colocated. Thus, the characters in symbols 253-255 of site ID 324 are the same as the characters in symbols 353-355 of site ID 360. The portion of site ID 324 that remains in site ID 360 also includes a class symbol. Thus, the characters in symbol 256 of site ID 324 are the same as the characters in symbol 356 of site ID 360.

[0086] In the example of Figure 3I, the characters in symbols 251, 252 of site ID 324 are identical to the characters in symbols 351, 352 of site ID 360, indicating that the same operator and vendor are associated with both existing site 332 and colocation candidate site 340. In some embodiments, the characters in symbols 251 and / or 252 of site ID 324 are different from the characters in symbols 351 and / or 352 of site ID 360 if different operators and / or vendors are associated with existing site 332 and colocation candidate site 340.

[0087] The portion of site ID 324 that was modified to obtain the corresponding portion of site ID 360 includes information regarding the different communication technologies supported by existing site 332 and colocation candidate site 340, respectively. In the example of FIG. 3I, the character in symbol 257 of site ID 324 and the character in symbol 357 of site ID 360 are different, indicating that existing site 332 and colocation candidate site 340 support different communication technologies. Specifically, with reference to table 267 of FIG. 2E, the character "3" in symbol 357 of site ID 360 indicates that the frequency band of colocation candidate site 340 is 28 GHz. This information coincides with and is defined by the 5G mmW colocation process (or workflow) selected by the user on screen 300A. The letter "1" in symbol 257 of site ID 324 indicates, with reference to table 267 of FIG. 2E, that the frequency band of existing site 332 is 1.7 GHz, i.e., a different communication technology from the 5 GmmW (28 GHz) communication technology of collocation candidate site 340.

[0088] The portion of site ID 324 that is modified to obtain the corresponding portion in site ID 360 includes the first symbol 258 of symbols 258-259, which specifies the sequence number of site ID 324. Symbol 258 is often unused because it is unlikely that all six symbols (approximately 1 million sequence numbers) 258-259 are needed to identify all sites within a subregion. Symbol 348 in site ID 360 corresponds to the unused symbol 258 in site ID 324 and is not used as part of the sequence number of site ID 360. Instead, symbol 348, also referred to herein as the colocation flag (or colocation class) symbol, specifies the colocation status of the site. As shown in table 368, if the character in symbol 348 is a "0," the corresponding site is not colocated; if the character in symbol 348 is a "6" (or some other character other than a "0"), the corresponding site is colocated.

[0089] The sequence number for site ID 360 is composed of five symbols 359, one fewer than the sequence number for site ID 324 (six symbols). The characters "00478" in symbol 359 are the same as the characters "00478" in symbol 259 for site ID 324. That is, except for the first symbols 258 and 348, the sequence numbers are the same for site ID 324 and site ID 360 (symbols 259 and 359). The total number of symbols for site ID 360 remains the same as the total number of symbols for site ID 324. As a result, in at least one embodiment, the system does not require significant conversion to accommodate the new or changed format of site ID 360.

[0090] In the example of FIG. 3I, the colocation candidate site 340 is assigned a unique site ID "RAC2323600478." This site ID indicates the following information about the colocation candidate site 340: operator R, vendor A, physical location in the Tokai region (jurisdiction) and the Aichi subregion (prefecture), class 2 (Outdoor Micro), frequency band 28 GHz, colocation status Yes, and sequence number 00478. Site ID 360 "RAC2323600478" and site ID 324 "RAC2321000478" differ in two symbols: symbol 357 (frequency band) and symbol 348 (colocation flag or colocation class).

[0091] In some embodiments, the site ID 360 of the collocation candidate site 340 is automatically generated by the system. In at least one embodiment, the site ID 360 of the collocation candidate site 340 is specified, in whole or in part, by a user. In some embodiments, the unique site ID 360 of the collocation candidate site 340 is used to identify the collocation candidate site 380 during site installation in the same physical location as the existing site 332 and / or during communications by / with the collocated site after site installation is complete, as described herein with respect to site ID 350 and / or collocation candidate site 340.

[0092] FIG. 3J displays screen 300J, a user interface similar to screen 300G, to show basic details of colocation candidate site 340 (or the resulting collocated site). Specifically, screen 300J shows that colocation candidate site 340 has a site name 343 identical to site name 323 of existing site 332, a site ID 360 as described in FIG. 3I, and the unique site ID 322 of the corresponding nominal site. Screen 300J also displays site type 345 of colocation candidate site 340: "5G mmW Pole ODSC," meaning that colocation candidate site 340 is a 5G mmW site. Screen 300J also displays physical location information 346 of colocation candidate site 340, including the latitude and longitude of existing site 332. Screen 300J does not display a colocation flag. A colocation flag is not required because the colocation status of a colocation candidate site 340 is reflected in the site ID 360 itself, for example, by a colocation flag symbol 348. In some embodiments, site colocation with different network generations is similar to site colocation within the same network generation as described with respect to Figures 3D-3G, except that the site ID (e.g., 324) of a colocation candidate site (e.g., 340) has a different format and there is no colocation flag.

[0093] In a further example of site collocation with different network generations (not shown), a collocation process is performed to collocate a 5G Sub6 site with an existing 4G ODSC site. The existing site has a unique site ID "RAA 1322600999" that is changed to obtain the unique site ID of the collocation candidate site, "REA 1321000999." Compared to the unique site ID of the existing site, the unique site ID of the collocation candidate site indicates that the vendor has been converted from "A" to "E," the frequency band has been converted from "1" (4G) to "2" (5G), and a collocation flag has been used to indicate the collocation status. The remaining symbols, including the sequence number (the last five symbols), remain unchanged.

[0094] In some embodiments, when site co-location is performed within the same network generation (e.g., a 5G Sub6 site is collocated with a 5G mmW site as described with respect to Figures 3D-3F), the site ID (e.g., 250) of the existing site (e.g., 282) and the site ID (e.g., 350) of the co-location candidate site (e.g., 380) have the same format (e.g., as described with respect to Figure 2E). A separate co-location flag (e.g., 396) outside the site ID is generated to indicate the co-location status of the existing site and the co-location candidate site.

[0095] In some embodiments, when site colocation is performed for different network generations (e.g., a 5G site is collocated with a 4G site as described with respect to Figures 3H-3J), the site ID (e.g., 324) of the existing site (e.g., 332) and the site ID (e.g., 360) of the colocation candidate site (e.g., 340) have different formats (e.g., as described with respect to Figure 3I). A separate colocation flag outside the site ID is not needed because the colocation flag symbol (e.g., 348) in the site ID (e.g., 360) of the colocation candidate site (e.g., 340) is used to indicate the colocation status of the colocation candidate site.

[0096] In some embodiments, by implementing site colocation, new or upgraded technologies may be added to an existing site, saving the cost and time of site surveys and / or construction of support structures and / or site infrastructure. Existing configurations, e.g., support structures and / or site infrastructure, may be used to facilitate the new technology's telecommunications signals for customers. In a simple example, a new 5G antenna and corresponding circuitry may be installed on a pole or tower of an existing 4G site. In a further example, a 5G antenna and corresponding circuitry for a first communication technology (e.g., Sub6) may be installed on a pole or tower of an existing 5G site using the same network generation but a different second communication technology (e.g., mmW), or vice versa. As described with respect to FIG. 2C , the time and cost of the site survey or TSS process and the construction of the pole or tower and / or associated site infrastructure may be saved.

[0097] In one or more embodiments, the site colocation process includes reusing a unique site ID of an existing site by modifying some, but not all, of the site ID to obtain a unique site ID for the new collocated site. The site ID of the new collocated site is then used for installation and / or operation of the new collocated site. In at least one embodiment, the size (e.g., number of symbols) of the site ID of the collocated site remains the same as that of the existing site, allowing the site colocation process to occur in a quick and easy manner without causing major changes to the system. Additional features and / or advantages are within the scope of various embodiments.

[0098] 4A is a flowchart of a process 400A for implementing site co-location, according to some embodiments. In some embodiments, process 400A is performed, at least in part, by at least one processor implementing one or more components of service system 110 and includes one or more of the operations and / or functions described with respect to FIGS. 2A-3I. Process 400A includes operations 402-409.

[0099] A nominal site is created or added in operation 402. For example, a nominal site is added manually using the latitude and longitude provided by the planning tool, as described with respect to Figure 2A.

[0100] One or more candidate sites corresponding to the nominal site are determined in operation 403. For example, available candidate sites near the nominal site are determined and downloaded by an API call, as described with respect to Figures 2B and 2D.

[0101] In operations 404-405, a site survey is performed, and based on the results of the site survey, a final candidate site is selected for site installation. For example, as described with respect to FIG. 2C, one or more humans, such as field technicians and / or managers, follow a workflow to perform the candidate site selection process and determine the final candidate site.

[0102] In operation 406, site IDs for the final candidate sites are generated, e.g., as described with respect to FIG. 2E. In some embodiments, the site IDs are generated by the system. Other site information items for the final candidate sites and / or the nominal site are generated and stored, e.g., as described with respect to FIGS. 2F-2G. In some embodiments, site information for the final candidate sites, including the site IDs, is generated by the system. As described herein, site installation is performed to configure the final candidate sites to become operational sites, which correspond to the nominal sites and are now referred to as existing sites.

[0103] In operation 407, the colocation process is initiated and a co-located site is created. For example, a user selects a nominal site and a co-location project (or co-location workflow) to be executed for the nominal site, as described with respect to FIG. 3A.

[0104] In operation 408, a candidate collocation site is selected. For example, an existing site corresponding to the nominal site is downloaded by an API call as described with respect to Figures 3B and 3C. This existing site serves as the basis for constructing the candidate collocation site.

[0105] In operation 409, a site ID for the colocation candidate site is generated, e.g., as described with respect to Figures 3D and / or 3I. In some embodiments, the site ID is generated by the system. Other site information items for the colocation candidate site are generated and stored, e.g., as described with respect to Figures 3E-3H and 3J. In some embodiments, the site information for the colocation candidate site, including the site ID, is generated by the system. As described herein, site installation is performed to configure the colocation candidate site to become an active site using new or upgraded communication technology, and the active site is now referred to as a colocated site that is in the same physical location as an existing site corresponding to the nominal site.

[0106] 4B is a flowchart of a process 400B for implementing site co-location, according to some embodiments. In some embodiments, process 400B is performed, at least in part, by at least one processor implementing one or more components of service system 110 and includes one or more of the operations and / or functions described with respect to FIGS. 3A-3J. Process 400B includes operations 422-426.

[0107] A first ID of an existing site corresponding to the nominal site is obtained in operation 422. For example, site ID 250 of existing site 282 corresponding to nominal site 281 is obtained as described with respect to Figures 3A-3D and 3H-3I.

[0108] In operation 424, a first portion of the first ID is modified while maintaining the second portion of the first ID to obtain a second ID of the colocation candidate site to be collocated at the existing site. For example, as described with reference to FIGS. 3D and 3I, the first portion of the site ID 250, 324 includes at least information about the communication technology supported by the existing site 282, 332 and / or an unused symbol. This first portion of the site ID 250, 324 is modified to include information about a different communication technology supported by the colocation candidate site 380, 340 and / or information about the colocation status of the colocation candidate site 340. The second portion of the site ID 250, 324 includes at least information about the physical location of the existing site 282, 332 and / or information about the class of the existing site 282, 332. This second portion remains unchanged. Other information in the site ID 250 may or may not be modified depending on the specific situation. Such other information includes information about the vendor and operator. Sequence numbers are generated for the collocation candidate sites 380, 340. As a result, the site IDs 350, 360 of the collocation candidate sites 380, 340 are generated completely or at least in part by the system.

[0109] In operation 426, the second ID is used, as described herein, for example, to at least one of install the candidate colocation site as a co-located site at the physical location of the existing site or to communicate with the co-located site upon completion of installation.

[0110] 4C is a flowchart of a process 400C for implementing site co-location, according to some embodiments. In some embodiments, process 400C is performed, at least in part, by at least one processor implementing one or more components of service system 110 and includes one or more of the operations and / or functions described with respect to FIGS. 3A-3J. Process 400C includes operations 442-450.

[0111] In operation 442, first site information of an existing site corresponding to the nominal site is obtained, the first site information including a first ID of the existing site, where the first ID indicates a first communication technology supported by the existing site. For example, as described with reference to Figures 3B and 3C, site information of an existing site 282 corresponding to the nominal site 281 is obtained. The site information includes site IDs 250 and 324 of the existing sites 282 and 332, as described with reference to Figures 3D and 3I, where the site IDs 250 and 324 indicate a first communication technology supported by the existing sites 282 and 332, such as frequency band "3" in site ID 250 or frequency band "1" in site ID 324.

[0112] In operation 444, second site information for a colocation candidate site to be collocated with the existing site is at least partially generated. The second site information includes a second ID of the colocation candidate site. The second ID is based on the first ID and indicates a second communication technology supported by the colocation candidate site, where the second communication technology is different from the first communication technology. For example, the site information for a colocation candidate site 380 to be collocated with the existing site 282 is at least partially generated as described with reference to FIGS. 3D and 3E. The site information for the colocation candidate sites 380 and 340 includes the site IDs 350 and 360 of the colocation candidate sites 380 and 340. Site ID 350, 360 is based on site ID 250, 324 and indicates a second communication technology supported by the co-location candidate site, where the second communication technology, e.g., frequency band “2” for site ID 350 or frequency band “3” for site ID 360, is different from the first communication technology, e.g., frequency band “3” for site ID 250 or frequency band “1” for site ID 324. Operation 444 further includes operation 446 or operation 448 depending on the network generation of the existing site and the co-location candidate site.

[0113] In operation 446, a separate co-location flag is generated outside the second ID in response to the first communication technology and the second communication technology being of the same network generation. For example, as described with respect to Figures 3D-3F, when site co-location is performed within the same network generation 5G, a separate co-location flag 396 is generated outside the site ID to indicate the co-location status of the existing site and the co-location candidate site.

[0114] In operation 448, in response to the first communication technology and the second communication technology being of different network generations, a co-location flag symbol is included in the second ID instead of an unused symbol. For example, as described with respect to Figures 3H-3J, when site co-location is performed to co-locate a 5G site with an existing 4G site, a co-location flag symbol 348 is included in the site ID 360 instead of the unused symbol 258 of the site ID 324.

[0115] In operation 450, the second ID is used, for example, in at least one of directing installation of the candidate colocation site as a co-located site at the physical location of the existing site or in communicating with the co-located site upon completion of installation, as described herein. In at least one embodiment, one or more advantages described herein can be realized in one or more of processes 400A, 400B, 400C.

[0116] The described methods and algorithms include example operations, which do not necessarily have to be performed in the order presented. Operations may be added, substituted, reordered, and / or deleted as appropriate in accordance with the spirit and scope of the embodiments of the present disclosure. Embodiments combining different features and / or different embodiments are within the scope of the present disclosure and will be apparent to those skilled in the art after reviewing the present disclosure.

[0117] 5 is a schematic block diagram of a computer system 500, according to some embodiments. Examples of computer system 500 include, but are not limited to, desktops, laptops, tablets, smartphones, servers, etc.

[0118] Computer system 500 includes a hardware processor 502 and a non-transitory computer-readable storage medium 504. Among other things, storage medium 504 is encoded with, i.e., stores, computer program code 506, i.e., executable instruction sets for one or more algorithms, programs, applications, etc., systems, components, and / or modules, as described with respect to Figures 1A-4. Execution of instructions 506 by hardware processor 502 implements some or all of the methods described herein, according to one or more embodiments (hereinafter, processes and / or methods).

[0119] The processor 502 is coupled to a non-transitory computer-readable storage medium 504 via a bus 508. The processor 502 is also coupled to an I / O interface 510 by the bus 508. A network interface 512 is connected to the processor 502 via the bus 508. The network interface 512 is connected to a network 514, thereby enabling the processor 502 and the computer-readable storage medium 504 to be connected to external elements or devices via the network 514. The processor 502 is configured to execute computer program code 506 encoded on the computer-readable storage medium 504 to enable the computer system 500 to perform some or all of the described processes and / or methods. In one or more embodiments, the processor 502 includes a central processing unit (CPU), a multiprocessor, a distributed processing system, an application-specific integrated circuit (ASIC), and / or other suitable hardware processing unit.

[0120] In one or more embodiments, computer-readable storage medium 504 includes an electronic, magnetic, optical, electromagnetic, infrared, and / or semiconductor system (or apparatus or device). For example, computer-readable storage medium 504 includes semiconductor or solid-state memory, magnetic tape, removable computer diskette, random access memory (RAM), read-only memory (ROM), rigid magnetic disk, and / or optical disk. In one or more embodiments using an optical disk, computer-readable storage medium 504 includes a compact disk-read-only memory (CD-ROM), compact disk-read / write (CD-R / W), and / or digital video disk (DVD).

[0121] In one or more embodiments, the storage medium 504 stores computer program code 506 configured to enable the computer system 500 to perform some or all of the described processes and / or methods. In one or more embodiments, the storage medium 504 also stores information or data 507, such as event data, consumer data, enterprise data, policies, component configurations, etc., used in some or all of the described processes and / or methods.

[0122] The I / O interface 510 is coupled to external circuitry. In one or more embodiments, the I / O interface 510 includes a keyboard, keypad, mouse, trackball, trackpad, touchscreen, and / or cursor direction keys for communicating information and commands to the processor 502. The computer system 500 is configured to receive information via the I / O interface 510. The information received via the I / O interface 510 includes one or more of instructions, data, policies, configurations, and / or other parameters for processing by the processor 502. The information is transferred to the processor 502 via the bus 508. The computer system 500 is configured to receive information related to a user interface via the I / O interface 510. The information is stored in the computer-readable storage medium 504 as a user interface (UI) 542.

[0123] The network interface 512 allows the computer system 500 to communicate with a network 514 to which one or more other computer systems are connected. The network interface 512 includes a wireless network interface such as BLUETOOTH, WIFI, WIMAX, GPRS, LTE, 5G, 6G, WCDMA, etc., or a wired network interface such as ETHERNET, USB, IEEE-864, etc. In one or more embodiments, some or all of the described processes and / or methods are implemented in more than one computer system 500.

[0124] In some embodiments, some or all of the described processes and / or methods are implemented as stand-alone software applications for execution by one or more hardware processors. In some embodiments, some or all of the described processes and / or methods are implemented as software applications that are part of additional software applications. In some embodiments, some or all of the described processes and / or methods are implemented as plug-ins to a software application.

[0125] In some embodiments, some or all of the described processes and / or methods are implemented as program functions stored in a non-transitory computer-readable recording medium. A computer-readable recording medium having a program stored therein is a computer program product. Examples of non-transitory computer-readable recording media include, but are not limited to, one or more of external / removable storage and / or internal / built-in storage or memory units, for example, optical disks such as DVDs, magnetic disks such as hard disks, and semiconductor memories such as ROMs, RAMs, and memory cards.

[0126] The foregoing outlines features of some embodiments so that those skilled in the art may better understand aspects of the present disclosure. Those skilled in the art will readily appreciate that this disclosure may be used as a basis for designing or modifying other processes and structures to carry out the same purposes and / or achieve the same advantages of the embodiments introduced herein. Those skilled in the art will also recognize that such equivalent constructions do not depart from the spirit and scope of the present disclosure, and that various changes, substitutions, and alterations may be made herein without departing from the spirit and scope of the present disclosure.

Claims

1. 1. A method for implementing site co-location, the method being at least partially executed by at least one processor, the method comprising: Obtain a first identification (ID) of an existing site corresponding to the nominal site; modifying the first portion of the first ID while maintaining the second portion of the first ID to obtain a second ID of a collocation candidate site to be collocated with the existing site; and establishing the candidate colocation site as a collocated site at the physical location of the existing site; or communicating with said co-located site upon completion of said installing; using the second ID for at least one of method.

2. the first portion of the first ID includes first information indicating a first communication technology supported by the existing site; In the modifying, the first information is converted into second information within the second ID, the second information indicating a second communication technology supported by the colocation candidate site, the second communication technology being different from the first communication technology. The method of claim 1.

3. the first portion of the first ID includes first information indicative of a first vendor associated with the existing site; In the modifying, the first information is converted into second information within the second ID, the second information indicating a second vendor associated with the co-location candidate site, the second vendor being different from the first vendor. The method of claim 1.

4. the first communication technology and the second communication technology are of the same network generation; the modifying includes generating a second sequence number for the second ID, the second sequence number being different from the first sequence number for the first ID; The method further includes generating a co-location flag external to the second ID, the co-location flag indicating that the existing site and the co-location candidate site are co-located in the same physical location. The method of claim 2.

5. the second portion of the first ID includes information about the physical location of the existing site, remains unchanged within the second ID, and indicates that the colocation candidate site has the same physical location as the existing site. The method of claim 1.

6. The modifying includes: changing a first symbol in the first ID to a different second symbol in the second ID, the first symbol indicating a first communication technology of a first network generation and supported by the existing site, and the second symbol indicating a second communication technology of a second network generation and supported by the co-location candidate site, the second communication technology being different from the first communication technology, and the second network generation being different from the first network generation; converting unused symbols in a first sequence number of the first ID to a co-location flag symbol in the second ID, the co-location flag symbol indicating a co-location status of the co-location candidate site; and keeping the remaining symbols in the first sequence number of the first ID unchanged and making the remaining symbols in the first sequence number a second sequence number of the second ID, where the number of symbols in the second sequence number is one less than the number of symbols in the first sequence number; The method of claim 1.

7. the first ID and the second ID contain the same number of symbols; The method of claim 6.

8. Each of the first ID and the second ID is: a symbol indicating the operator of the corresponding existing site or potential colocation site; a symbol indicating the vendor associated with said corresponding existing site or potential colocation site; a symbol indicating an area that includes the physical locations of the existing site and the potential colocation site; two symbols representing a sub-region that includes the physical locations of the existing site and the potential colocation site; symbols indicating classes of said existing sites and potential colocation sites; a symbol indicating the frequency band of the corresponding existing site or candidate co-location site; and a series of symbols indicating the sequence numbers of the corresponding existing sites or co-location candidate sites; the series of symbols of the first ID includes a first symbol and remaining symbols; The series of symbols of the second ID is: a collocation flag symbol and the remaining symbols in the series of symbols of the first ID, where the collocation flag symbol corresponds to the first symbol in the series of symbols of the first ID and indicates the collocation status of the collocation candidate site; or one or more symbols corresponding to and different from the remaining symbols of the series of symbols of the first ID; The method of claim 1.

9. in response to a user input of the nominal site and a colocation process to be performed for the nominal site; obtaining first site information of the existing site corresponding to the nominal site, the first site information including the first ID of the existing site; generating second site information for the colocation candidate site after modifying the first ID to obtain the second ID, the second site information including the second ID; and and directing the installation at the collocation candidate site according to the second site information. The method of claim 1.

10. The existing site comprises: a support structure; and a first communications device supporting a first communications technology and mounted on the support structure; and the installing includes installing second communications equipment at the candidate colocation site on the support structure of the existing site, the second communications equipment supporting a second communications technology different from the first communications technology.

10. The method of claim 9.

11. obtaining one or more candidate sites within a predetermined radius from the nominal site; conducting a site survey to determine a candidate site for installation of the nominal site from among the one or more candidate sites; generating the first ID for the determined candidate site; and and instructing installation of the determined candidate site to acquire the existing site corresponding to the nominal site. The method of claim 1.

12. and, upon completion of the establishing of the existing site, using the first ID for communication with the existing site. The method of claim 11.

13. 1. A system for implementing site colocation, comprising: at least one processor; and at least one computer-readable storage medium coupled to the at least one processor and configured to store executable instructions; The executable instructions, when executed by the at least one processor, cause the at least one processor to: obtaining first site information of an existing site corresponding to a nominal site, the first site information including a first identification (ID) of the existing site, the first ID indicating a first communication technology supported by the existing site; generating at least partial second site information for a collocation candidate site to be collocated with the existing site, the second site information including a second ID of the collocation candidate site, the second ID being based on the first ID and indicating a second communication technology supported by the collocation candidate site, the second communication technology being different from the first communication technology; and Directing the establishment of the candidate collocation site as a collocated site at the physical location of the existing site; or communicating with said co-located site upon completion of said installing; using the second ID in at least one of the following: system.

14. The executable instructions, when executed by the at least one processor, cause the at least one processor to: visually presenting a first input area for receiving user input of the nominal site and a colocation process to be performed on the nominal site; and acquiring the first site information of the existing site corresponding to the nominal site based on the nominal site input in the first input area; The system of claim 13.

15. The executable instructions, when executed by the at least one processor, cause the at least one processor to: visually presenting a second input area to receive a user instruction to search for the existing site corresponding to the nominal site and obtain the first site information of the existing site upon user input of the nominal site and the colocation process in the first input area; The system of claim 14.

16. The executable instructions, when executed by the at least one processor, cause the at least one processor to: in response to a user command received in the second input area, causing a search for the existing site as a site that is closest to the nominal site and that satisfies one or more conditions defined in the colocation process; The system of claim 15.

17. The executable instructions, when executed by the at least one processor, cause the at least one processor to: visually presenting the second ID obtained by modifying a first portion of the first ID while maintaining a second portion of the first ID, wherein: the first portion of the first ID includes a first symbol indicative of the first communications technology supported by the existing site, the first symbol being transformed into a different second symbol of the second ID, the second symbol indicative of the different second communications technology supported by the co-location candidate site; the second portion of the first ID includes information about the physical location of the existing site and remains unchanged in the second ID to indicate that the colocation candidate site has the same physical location as the existing site; The system of claim 13.

18. the first communication technology and the second communication technology are of different network generations; The executable instructions, when executed by the at least one processor, cause the at least one processor to, on the same screen: Unique IDs of the nominal sites corresponding to the existing site and the candidate colocation site; Information regarding the physical locations of the existing site and the candidate colocation site; and visually presenting the second ID of the collocation candidate site, the second ID including a collocation flag symbol indicating a collocation status of the collocation candidate site; The system of claim 13.

19. the first communication technology and the second communication technology are of the same network generation; The executable instructions, when executed by the at least one processor, cause the at least one processor, within the same screen, to: the first ID of the existing site; information regarding the physical locations of the existing site and the potential colocation site; Unique IDs of the nominal sites corresponding to the existing site and the candidate colocation site; the second ID of the colocation candidate site; and visually presenting a co-location flag indicating that the existing site and the co-location candidate site are co-located at the same physical location; The system of claim 13.

20. A computer program product comprising a non-transitory tangible computer-readable storage medium storing a computer program; The computer program, when executed by at least one processor, causes the at least one processor to: obtaining first site information of an existing site corresponding to a nominal site, the first site information including a first identification (ID) of the existing site, the first ID indicating a first communication technology supported by the existing site; generating second site information for at least a portion of the collocation candidate sites to be collocated with the existing site, the second site information including a second ID of the collocation candidate site, the second ID being based on the first ID and indicating a second communication technology supported by the collocation candidate site, the second communication technology being different from the first communication technology; and directing the establishment of said candidate collocation site as a collocated site at the physical location of said existing site; or communicating with said co-located site upon completion of said installing; and using the second ID in at least one of Computer program products.

Images