Method, system, and computer program product for implementing site collocation

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 in particular to site installation in a communication system, for example, for expansion and / or upgrade.

Background Art

[0002] Networking and telecommunications have had a great impact on daily life, and user devices such as smartphones, laptops, tablets, and game consoles are becoming increasingly popular for applications such as work, entertainment, and social networking. To meet the increasing demand for more and / or better services, coverage, bandwidth, speed, service quality, service reliability, network efficiency, etc., communication systems are regularly upgraded. However, the time, effort, and / or cost associated with upgrades are considerations for the operators of communication systems.

Summary of the Invention

Means for Solving the Problems

[0003] In some embodiments, a method of implementing site co-location is at least partially performed 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 co-location candidate site to be co-located with the existing site. The method further includes using the second ID for at least one of installing the co-location candidate site as a co-located site at the physical location of the existing site or communicating with the co-located site upon completion of the 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. When the executable instructions are executed by the at least one processor, the at least one processor is caused to obtain first site information of an existing site corresponding to a nominal site. The first site information includes first identification information (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 co-located 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 to install the co-location candidate site as a co-located site at the physical location of the existing site or communicating with the co-located 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 that, when executed by at least one processor, causes the at least one processor to obtain first site information of an existing site corresponding to a nominal site. The first site information includes first identification information (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 co-located 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 to install the co-location candidate site as a co-location site at the physical location of the existing site or communicating with the co-location 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. In accordance with industry standard practice, various features are not drawn to scale. In fact, the dimensions of the various features may be arbitrarily increased or decreased for clarity of explanation.

Brief Description of the Drawings

[0007]

Figure 1

[0008]

Figure 2A

Figure 2B

Figure 2C

Figure 2D

Figure 2E

Figure 2Ec

Figure 2F

Figure 2G

[0009]

Figure 3A

Figure 3B

Figure 3C

Figure 3D

Figure 3E

Figure 3F

Figure 3G

Figure 3H

Figure 3I

Figure 3J

[0010]

Figure 3H

Figure 3I

Figure 3J

[0011]

Figure 4A

Figure 4B

Figure 4C

[0012]

Figure 5

[0013] The following disclosure includes many different embodiments or examples for implementing different features of the present subject matter. To simplify the present 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, the formation of a first feature above or over a second feature in the following description includes embodiments in which the first feature and the second feature are formed in direct contact, and also includes embodiments in which additional features are formed between the first feature and the second feature so that the first feature and the second feature are not in direct contact. Additionally, the present disclosure repeats reference numerals and / or letters in various examples. This repetition is for the purpose of brevity and clarity and does not in itself determine the relationship between the various embodiments and / or configurations being discussed. Further, spatially relative terms such as "beneath," "below," "lower," "above," "upper," etc. may be used herein to facilitate the description of the relationship of one element or feature to another element or feature as shown in the figures. Spatially relative terms are intended to encompass different directions of the device in use or operation in addition to the orientation shown in the figures. The device may be oriented in other directions (rotated 90 degrees or other directions), and the spatially relative descriptors used herein may likewise be interpreted accordingly.

[0014] In a typical situation with other approaches, an upgrade may be performed in a communication system by planning, surveying, and installing support structures and communication equipment for new sites, such as new base stations, cell towers, access nodes, etc. Such a process is time-consuming, labor-intensive, and / or costly.

[0015] In some embodiments, site collocation is implemented to avoid and / or mitigate one or more of the described drawbacks of other approaches. In the site collocation process, equipment of a new or upgraded communication technology is installed on or in the same support structure of an existing site where equipment of a different existing communication technology is already installed. The new communication technology or upgraded communication technology constitutes a new site collocated with the existing site, but provides the new communication technology or upgraded communication technology for improving performance, customer experience, network efficiency, etc. A simple example of site collocation includes additionally attaching a 5G communication antenna to the cell tower of an existing 4G site, where the 4G communication 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 enables omission of various steps such as site surveys and installation of support structures, thereby saving upgrade time, labor, and / or cost.

[0016] In some embodiments, the site collocation process includes reusing the unique site identification information (ID) of an existing site by changing not all but a part of the site ID of the existing site to obtain the unique site ID of the newly collocated site. The site ID of the newly collocated site is then used for the installation and / or operation of the newly collocated site. In at least one embodiment, the collocation status of the newly collocated site, i.e., the fact that it is collocated with the existing site, is reflected in the site ID of the newly collocated site. As a result, in one or more embodiments, it is possible to speed up, simplify, and / or smooth the site collocation process. Further features and / or advantages are within the scope of various embodiments.

[0017] FIG. 1 is a schematic diagram of an exemplary communication system 100 to which site co-location according to some embodiments is applicable.

[0018] In an exemplary configuration of the communication system 100 of FIG. 1, the consumer's mobile terminal 104 is coupled to the cellular network 102 to receive communication services. In one example, the cellular network 102 includes a plurality of cells (not shown) where cellular services are provided via corresponding base stations or access nodes. Representative base stations 106, 107 are shown in FIG. 1. The base stations constitute a radio access network and are coupled to the core network of the cellular network 102. A representative network device 108 of the core network is shown in FIG. 1. Examples of the cellular network 102 include, but are not limited to, Long-Term Evolution (LTE) networks, 5th Generation (5G) networks, 6th Generation (6G) networks, Non-Standalone (NSA) networks, Standalone (SA) networks, Global System for Mobile Communications (GSM) networks, General Packet Radio Service (GPRS) networks, Code Division Multiple Access (CDMA) networks, Mobitex networks, Enhanced GPRS (EDGE) cellular networks, Wi-Fi (or WIFI) networks, WiMAX networks, and the like. Exemplary configurations of base stations include a support structure 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, and the like. In some embodiments, the support structure further comprises site infrastructure, which includes, but is not limited to, primary and backup power supplies, air conditioning or cooling devices, cables, ducts, shelters, and the like. Examples of the mobile terminal 104 include, but are not limited to, mobile phones, tablets, media players, gaming consoles, personal digital assistants (PDAs), laptops, and other electronic devices configured to transmit and / or receive cellular communication with the base stations of the cellular network 102.Exemplary hardware configurations of the mobile terminal and / or the base station include the computer system described with respect to FIG. 5, with one or more cellular antennas and corresponding cellular transceiver circuits added. Examples of communication technologies for performing cellular communication between the base station and the mobile terminal include, but are not limited to, 2G, 3G, 4G, 5G, 6G, GSM, EDGE, WCDMA (registered trademark), HSPA, CDMA, LTE, DECT, WIFI, WiMAX, and the like. Examples of services provided via cellular communication, referred to herein as cellular communication services, include, but are not limited to, voice calls, data, emails, messages such as SMS and MMS, applications, and control signals. Exemplary components of the core network (or network device 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). Components of the core network are coupled to each other by one or more public and / or private networks and to the base station. An exemplary hardware configuration of a component of the core network or network device 108 includes the computer system described with respect to FIG. 5.

[0019] The communication system 100 further includes 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 a workflow 120 and assigns it to at least one human 122, such as a field technician or engineer. The human 122 uses their mobile device 123 (or another computer system) to display the workflow and / or to 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 regarding one or more operations, functions, components, etc. of the cellular network 102 and collects data and / or measurements. In the exemplary configuration of FIG. 1, the human 122 performs tasks such as surveying (examining), installing, servicing, or checking the operation of the base station 107 according to the requirements, tasks, or steps defined in the workflow 120. When the human 122 performs the tasks required by the workflow 120, the human advances the workflow from the status with the completed tasks to the next status with additional tasks to be performed until the workflow 120 is completed (otherwise aborted, e.g., canceled). In some embodiments, the workflow is assigned to two or more humans to execute by one or more computer systems and / or is automatically executed in cooperation with one or more humans, either wholly or in part.

[0020] In some embodiments, the service system 110 comprises one or more hardware components on which software corresponding to the various algorithms and / or operations described herein is executed. Any one or more hardware configuration examples of the components of the service system 110 include the computer system described with respect to FIG. 5. For example, each of the components of the 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 within the service system 110 and / or its sub-components are implemented on / by a cloud platform. Other hardware configurations are within the scope of the various embodiments.

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

[0022] The communication system 100 further includes one or more databases, schematically represented as database 130. The 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 / input by the human 122 and / or the service system 110, and / or the workflow status described herein. In some embodiments, the 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 the communication system 100 described is an example. Other communication system configurations are within the scope of various embodiments.

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

[0024] In FIG. 2A, when a nominal site is added to the communication system 100, the screen 200A of the user interface is displayed. 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, the site may be any component of the communication system 100 having a support structure on which communication equipment can be installed and / or upgraded. As described herein, in at least one embodiment, the support structure of the site includes not only towers, buildings, utility poles, indoor support structures, etc., but also primary power and backup power (e.g., batteries), air conditioning or cooling devices, cables, ducts, shelters, etc., and a physical structure that can include site infrastructure. In one or more embodiments, the communication equipment includes, but is not limited to, one or more antennas, beam steering mechanisms / systems, transceiver circuits, control circuits, modulation circuits, any other electronic components configured to provide communication services, and / or computer components. In some embodiments, not all communication equipment of the site is installed on towers, buildings, utility poles, etc. In one example, a portion of the communication equipment of the site is installed within a housing (shelter) or on the ground in relation to or connected to the site infrastructure.

[0025] The nominal site is the location or reference point where the installation, construction, or building of the site is planned. In some embodiments, the nominal site is determined by a person, such as 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 as the nominal site considering one or more factors including, but not limited to, the communication technology to be provided or supported, the intended coverage (e.g., considering the coverage areas of adjacent cells or sites), the estimated number of subscribers or customers to be served by the site, etc.

[0026] In the configuration example of FIG. 2A, the screen 200A shows various information of the nominal site to be added. For example, the nominal ID 201, branch ID 202, nominal unique ID 203, pole ID 204, latitude 205, longitude 206, and nominal name 207. In some embodiments, the latitude 205 and longitude 206 are provided by a planning tool. The nominal name 207 is the site name of the nominal site. The nominal unique ID 203 is a unique ID of the nominal site and is generated, for example, by at least one processor. In the example of FIG. 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 canceling the nominal site addition process and an add button 209 for proceeding with the addition of the nominal site.

[0027] In FIG. 2B, the screen 200B of the user interface shows a map 210 of an area including the nominal site 211. The site type 212 "5GmmW Pole" of the nominal site 211 indicates the communication technology provided, that is, "5GmmW". The map 210 includes a plurality of existing physical structures. In the exemplary configuration of FIG. 2B, the existing physical structures include poles (hereinafter referred to as "poles") 214 to 217. In one example, the information about the poles 214 to 217 is obtained from an electric power company and stored in the database 130 for access by the service system 110. For the sake of simplicity of explanation, 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, and indoor support structures are within the scope of various embodiments.

[0028] Some of the poles, such as pole 217, are not available for site installation (i.e., at least the installation of the communication equipment at the site). The remaining poles 214 - 216 are available for site installation. In an ideal or best scenario where an available pole is found to match 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, the available poles 215, 216 within the circle 213 centered on the nominal site 211 are candidates for site installation and are referred to herein as candidate sites. The remaining available poles outside the circle 213, i.e., pole 214, are not considered for site installation because they are 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 is to be actually installed. The radius of the circle 213 depends on various factors such as coverage, quality of service (QoC), transmit power, etc. In the example, the radius of the circle 213 is 1m, 15m, or 30m. Other values for the radius of the 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 for site installation.

[0029] In FIG. 2C, the screen 200C of the user interface includes an exemplary workflow 219 for the candidate site selection process. In some embodiments, the workflow configuration of the workflow 219 includes one or more Extensible Markup Language (XML) documents to be executed by a workflow engine. In the exemplary configuration of FIG. 2C, the workflow 219 complies with 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 a plurality of elements 220-234 arranged in an order determined by a user and / or a workflow template. The elements 220-234 are connected to each other by a plurality of connections (not numbered) and form a flowchart-type diagram that describes a corresponding item sequence to be executed by one or more humans and / or systems (e.g., at least one processor within a mobile device 123, a service system 110, or another computer system). There are several types of elements in workflow 219. For example, elements 222, 224, 226 are user tasks, each indicated by a human icon. In some embodiments, a user task is an activity or operation that can be or is executed by a human. In another example, elements 225, 227, 231 are gateways. In some embodiments, a gateway defines a situation where several options are available and one of the options needs to be selected by a human and / or a system in order to proceed. The described workflow configuration is an example. Other workflow configurations using different connections, and / or events, and types of elements such as other types of gateways and / or tasks are within the scope of various embodiments.

[0031] Workflow 219 starts with element 220 where the 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 information items 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] In element 221, one or more operations in a process called technical site survey (TSS) are performed. For example, a field technician moves to the physical location of the finalized nominal site and determines whether poles or candidate sites at or near the nominal site are suitable for site installation (as described with respect to FIG. 2B). 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 and / or support structures). The database is provided to service system 110 or is accessible via the service system. 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 moves to the physical location of the nominal site and surveys each of the available candidate sites, starting, for example, from the candidate site closest to the nominal site.

[0033] In the TSS process at each candidate site, a number of factors, conditions, and steps are considered / adopted. For example, a field technician can check whether the existing poles at the candidate site are of appropriate height (e.g., a particular transmitter or transceiver needs to be installed at a distance of at least 20 meters from the ground). The field technician can check whether the candidate site is physically accessible to the operator for installation at that particular height and / or whether the azimuth angle of the transmitter can be maintained at a particular level when installed at the candidate site and / or whether there are buildings or obstacles in a particular direction that may interfere with the transmitter's signal, etc. The field technician or another person can check whether permission is required for access to and / or execution of installation at the candidate site (which may potentially be on top of a building), and / or whether the owner (e.g., the owner of the building) agrees to lease the candidate site (e.g., the roof of the building), and / or whether a zoning permit or building permit is required or can be obtained 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 actions 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 at the final stage of the TSS process. For example, the TSSR indicates the candidate site(s) found to be suitable for installation near or at the nominal site. A candidate site near the nominal site is understood as a candidate site within a predetermined distance from the nominal site, as described with respect to Figure 2B.

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

[0036] In element 225, if the first administrator discovers a defect in the TSSR, the process returns to element 222 for the correction and / or update of the TSSR. If the first administrator determines that the TSSR is satisfactory and approves the TSSR, the process proceeds to element 226.

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

[0038] In element 227, if the second administrator discovers that the TSSR has a defect but is correctable, the process returns to element 224 for the correction and / or update of the TSSR. If the second administrator finds a satisfactory TSSR and approves the TSSR, the process proceeds to element 228. In a third scenario, for example, if it is determined that all available candidate sites around the nominal site are inappropriate, the second administrator decides to remove the nominal site and the process proceeds to element 231.

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

[0040] In 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 carry out the installation of support structures, site infrastructure, and / or communication equipment.

[0042] In element 231, that is, when it is decided not to consider construction (e.g., base station or access node) at the nominal site any further, the nominal site is accordingly removed, the decision to remove the nominal site is notified to the relevant parties, and several actions occur in elements 232, 233, 234 to end activities (e.g., surveys) at the nominal site.

[0043] While workflow 219 is being implemented or executed, the different statuses of the various stages (or elements) are visually presented in corresponding different specific formats, such as different colors. In the exemplary configuration of FIG. 2C, stages or elements 220, 221 are complete and are displayed in green, stage or element 222 is currently executing (i.e., active) and is displayed in blue, and the remaining stages or elements are new (i.e., not yet started / opened) and are displayed in an intermediate color, such as white. Alternatively, it is possible to monitor the progress and / or status of the various stages of workflow 219 on a separate screen (not shown) that does not include workflow 219. Workflow 219 described with various elements is an example. Other workflows for candidate site selection are within the scope of the various embodiments.

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

[0045] FIG. 2E is a schematic diagram showing the site ID 250 of the final candidate site in a system for implementing site collocation 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 final candidate site. For example, symbol 251 designates the operator of the final candidate site, such as a communications company that operates the final candidate site. Examples of the names of various operators and the corresponding codes are detailed in Table 261. For example, if symbol 251 includes the letter or code R, it indicates that the operator of the final candidate site is Operator R.

[0047] Symbol 252 designates the vendor that works at the final candidate site, for example, the vendor that performs site installation at the final candidate site. Examples of the names of various vendors and the corresponding codes are detailed in Table 262. For example, if symbol 252 includes the letter or code A, it indicates that the vendor associated with the final candidate site is Vendor A.

[0048] Symbol 253 indicates the region where the final candidate site is physically located. Examples of the names of various regions and the corresponding codes are detailed in Table 263. In these examples, the region is in Japan and is called a jurisdiction area. For example, if symbol 253 includes the letter or code C, it indicates that the final candidate site is physically located within the Tokai region or jurisdiction area (Japan).

[0049] Symbols 254 and 255 both specify the sub-region where the final candidate site is physically located. The sub-region is a smaller region within the region specified by Symbol 253. Examples of the names and corresponding codes of various sub-regions are detailed in Table 264. For simplicity, Table 264 is partially shown in Figure 2E, and Table 264 includes other sub-regions and corresponding codes not shown in other figures. In these examples, the sub-region is in Japan and is called a prefecture. For example, if Symbols 254 and 255 both indicate Code 23, it indicates that the final candidate site is physically located in Aichi Prefecture (Japan), a prefecture within the jurisdiction of the Tokai region. Symbols 253 to 255 collectively specify information regarding the physical location of the final candidate site. Other types of regions and sub-regions are within the scope of various embodiments. For example, in one or more embodiments applicable to the United States, the region is a state and the sub-region is a county.

[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 the names and corresponding codes of various classes are detailed in Table 266. For example, if Symbol 256 includes the character or code 2, it indicates that the class of the final candidate site is Outdoor Micro.

[0051] Symbol 257 specifies 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 the names and corresponding codes of various frequency bands are detailed in Table 267. For example, if Symbol 257 includes the character or code 3, it indicates that the frequency band of the final candidate site is 28G (28 GHz).

[0052] A frequency band is an example of a communication technology supported by a site (e.g., a base station or an access node). If the site, i.e., its communication equipment, is configured to support or perform communication in a higher frequency band, the communication speed will be faster and the service will be provided to customers with different levels 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 network generations (e.g., 3G, 4G, 5G, 6G, etc.), antenna design (e.g., unidirectional, omnidirectional, etc.), and the like. When a site is upgraded or collocated by a new or different communication technology described herein, the conversion / upgrade of the communication technology can be a conversion / upgrade of the network generation (e.g., from 4G to 5G), and / or a conversion / upgrade of the antenna design (e.g., from a unidirectional antenna to an omnidirectional antenna), and / or a conversion / upgrade of the frequency band (with or without conversion to a different network generation). The examples of communication technologies described are non-exhaustive.

[0053] According to some embodiments, in addition to the communication technology, the network generation is further considered. In one or more aspects including, but not limited to, frequency spectrum, peak (or maximum) speed, latency, connection density (e.g., the number of users that can be served simultaneously within a unit area), etc., one network generation is different from another network generation. Some examples of different network generations, i.e., 3G, 4G, 5G, 6G, etc. are shown herein. Other network generations are within the scope of various embodiments. For example, Wi-Fi is a network generation different from 3G, 4G, 5G, 6G. An example of site collocation within the same network generation but with different communication technologies will be described with respect to FIGS. 3D to 3G. Further examples of site collocation with different network generations and, of course, with different communication technologies will be described with respect to FIGS. 3H to 3J.

[0054] A series of symbols 258, 259 specify a sequence number for identification and / or management purposes. In some embodiments, this sequence number is automatically generated 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 design / operation, vendor, region, class, frequency band may be represented by two or more symbols, and / or a sub-region may be represented by two other symbols, and / or the sequence number may include symbols other than six. In some embodiments, all symbols within the site ID 250 are automatically generated by the system. In at least one embodiment, at least a part of the site ID 250 is provided or specified by a human.

[0056] In FIG. 2F, the screen 200F of the user interface shows various items 270-274 of the site information of the final candidate site 249. In particular, the final candidate site 249 is assigned the following site ID 273 "RAC2323000686" corresponding to the site ID 250 described with respect to FIG. 5E. The site ID 273 "RAC2323000686" indicates the following information regarding the final candidate site 249, namely, operator R, vendor A, physically located in the sub-region (prefecture) Aichi in the Tokai region (jurisdiction), class 2 (Outdoor Micro), frequency band 28 GHz, sequence number 000686. Other site information items of the final candidate site 249 include the TSS status 271, comment 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 into the system by the system from a database (e.g., database 130). The comment 272 and the photo 274 are provided by a human such as a field engineer. The described site information items are an example. Other possible items in the site information are within the scope of various embodiments.

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

[0058] The nominal site 281 has a site name 291 “01X371” and a unique site ID 292 “129_01X371_35.1716782417182_136.938299917042” corresponding to the nominal name 207 and the nominal unique ID 203 described with respect to FIG. 2A. The nominal site 281 further has a site type “5 GmmW Pole” corresponding to the site type 212 described with respect to FIG. 2B.

[0059] The final candidate site 282 has a site name 293 corresponding to the pole name of the candidate site 249 described with respect to FIG. 2D. The final candidate site 282 further has a unique ID 294, "RAC2323000686", as described with respect to FIG. 2F. The final candidate site 282 also has a site type, "5G mmW Pole Site", generated based on the site type of the nominal site 281, "5G mmW Pole". The nominal site 281 is a planned site. The "Site" part of the site type of the final candidate site 282 indicates that the final candidate site is the actual site corresponding to the planned nominal site and is configured / installed to provide communication services. As described with respect to FIGS. 2F-2G, the site information of the nominal site 281 and the corresponding final candidate site 282 is stored in a database such as the database 130. The site installation is performed at the physical location of the final candidate site 282, installing communication equipment using the necessary support structures or site infrastructure, and configuring the final candidate site 282 as an operating site to provide communication services to customers. For example, the system instructs the site installation to the final candidate site 282 according to the site information of the final candidate site 282. When the site installation is completed, the final candidate site 282 is called an existing site. In some embodiments, a unique ID, such as "RAC2323000686", is used to identify the final candidate site 282 during site installation and / or during communication by / with the existing site after the site installation is completed.

[0060] FIGS. 3A-3C, 3E-3H, and 3J are schematic diagrams showing various screens of the user interface, and FIGS. 3D and 3I are schematic diagrams showing various examples of site IDs and modified site IDs in a system for implementing site collocation according to some embodiments. In some embodiments, one or more of the UI screens of FIGS. 3A-3C, 3E-3H, 3J, and / or the site IDs of FIGS. 3D, 3I are generated and / or used by the service system 110 in the collocation process. Further, one or more of the 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 the service system 110 are implemented. For clarity, such operations are referred to as being performed by the system.

[0061] In FIG. 3A, a screen 300A of a user interface is displayed at the start of the collocation process. Screen 300A is an example of a first input area for receiving user input of a nominal site and a collocation process (or workflow) to be executed on the nominal site. Specifically, screen 300A enables a user to input and / or search for a nominal site that meets specific conditions. Screen 300A includes dropdown menus 301, 302, 303 that enable the user to select various menu items (not shown) and narrow down the search according to the site type, site technology, prefecture (or sub-region). Alternatively or additionally, the user can directly search for a desired nominal site based on the site ID using the search field 304. One or more nominal sites that correspond to the selected menu items (not shown) of dropdown menus 301, 302, 303 and / or satisfy the search query entered by the user in the search field 304 are displayed in area 306. For clarity, the nominal site 308 in area 306 is displayed in detail, while other nominal sites in area 306 are omitted. In the example of FIG. 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 indicates that nominal site 308 (i.e., nominal site 281) has been selected by the user.

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

[0063] In FIG. 3B, a screen 300B of the user interface is displayed, and the user can download or acquire site information of a collocation candidate site corresponding to the selected nominal site 281 by operating or selecting an item 312 on the screen 300B. For example, an API call is made to access the database 130 to search for site information of an existing site corresponding to the selected nominal site 281. The existing site corresponding to the selected nominal site 281 functions as a basis for configuring a collocation candidate site so as to be collocated with the existing site. The screen 300B is an example of a second input area, and is visually presented when the user inputs (or selects) the nominal site 308 and the collocation workflow 309 in the first input area of the screen 300A, and receives a user command to search for an existing site corresponding to the nominal site and acquire the site information of the existing site.

[0064] In FIG. 3C, a screen 300C of the user interface is displayed to show the download result, that is, the site name 314 of the downloaded 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 an existing site after the site installation, as described with respect to FIGS. 2A to 2G. The existing site 282 serves as a 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 acquired, as described with respect to FIG. 2F. The downloaded or acquired 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 respect to FIGS. 3D and 3I.

[0065] In some embodiments, if there is no existing site corresponding to the nominal site selected or input by the user on screen 300A, the system searches for an existing site (e.g., an operating site having a support structure and / or site infrastructure that has already been constructed) that is closest to the selected nominal site and meets one or more predetermined conditions, such as the conditions defined in the collocation workflow 309. The search is performed in the database 130 in a manner similar to the method 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, and it is determined whether it meets one or more predetermined conditions, such as whether there are no tall buildings around the existing site that could interfere with the radio signal. If the closest existing site meets the predetermined conditions, it is selected as a collocation candidate site; if not, the next closest existing site in the returned list is considered to determine whether it meets the predetermined conditions or can be selected as a collocation candidate site, and so on. The collocation candidate site determined in this process is further processed in an example of site collocation with different communication technologies within the same network generation, as described with respect to FIGS. 3D-3G.

[0066] FIG. 3D is a schematic diagram showing, according to some embodiments, the site ID 250 of the final candidate site that has become the existing site 282 after completion of the site installation at the final candidate site, and the site ID 350 of the collocation candidate site 380 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 respect to FIG. 2E. In the example of FIG. 3D, for the corresponding symbols 251-259, specific characters corresponding to the site ID "RAC2323000686" described with respect to FIG. 2F are shown.

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

[0069] In some embodiments, the site ID 350 of the co-location candidate site 380 is obtained by changing a part of the site ID 250 while maintaining another part of the site ID 250. For example, the part of the site ID 250 remaining in the site ID 350 includes information regarding the physical location of the existing site 282 because the co-location candidate site 380 and the existing site 282 are to be co-located. Thus, the characters within the symbols 253-255 of the site ID 250 are the same as the characters within the symbols 353-355 of the site ID 350. The part of the site ID 250 remaining in the site ID 350 further includes a class symbol. Thus, the characters within the symbol 256 of the site ID 250 are the same as the characters within the symbol 356 of the site ID 350.

[0070] In the example of FIG. 3D, the characters within the symbol 251 of the site ID 250 are the same as the characters within the symbol 351 of the site ID 350, indicating that the same operator operates both the existing site 282 and the co-location candidate site 380. In some embodiments, the characters within the symbol 251 of the site ID 250 are different from the characters within the symbol 351 of the site ID 350, in which case different operators operate the existing site 282 and the co-location candidate site 380.

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

[0072] The portion of site ID 250 that has been modified to obtain the corresponding portion of site ID 350 includes information regarding different communication technologies correspondingly supported by existing site 282 and co-location candidate site 380. In the example of FIG. 3D, the characters within symbol 257 of site ID 250 are different from the characters within symbol 357 of site ID 350, indicating that existing site 282 and co-location candidate site 380 support different communication technologies. Specifically, referring to Table 267 of FIG. 2E, the character "2" within symbol 357 of site ID 350 indicates that the frequency band of co-location candidate site 380 is 3.7 GHz. This information is consistent with and defined by co-location workflow 309 targeting co-location of 5G Sub6 (below 6 GHz) sites. The character "3" within symbol 257 of site ID 250 indicates, referring to Table 267 of FIG. 2E, that the frequency band of existing site 282 is 28 GHz, i.e., a different communication technology from the sub 6 GHz communication technology of co-location candidate site 380.

[0073] The portion of Site ID 250 that has been changed to obtain the corresponding portion within Site ID 350 includes symbols 258 - 259 that specify the sequence number of Site ID 250. The corresponding sequence number of Site ID 350 includes symbols 358 - 359 that correspond to symbols 258 - 259. One or more of symbols 359 of Site ID 350 are different from the corresponding one or more of symbols 259 of 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 of Site ID 350 is the same as the total number of symbols of Site ID 250. As a result, in at least one embodiment, the system does not require a major conversion to adapt to the new or changed format of Site ID 350.

[0074] In the example of FIG. 3D, the collocation candidate site 380 is assigned a unique site ID "REC 2322000900". This site ID indicates the following information regarding the collocation candidate site 380: namely, operator R, vendor E, physically located in the Aichi prefecture in the Tokai region (jurisdiction), class 2 (Outdoor Micro), frequency band 3.7 GHz, 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 FIG. 3G.

[0075] In some embodiments, the site ID 350 of the co-location candidate site 380 is automatically generated by the system. In at least one embodiment, the site ID 350 of the co-location candidate site 380 is wholly or partly specified by the user. In some embodiments, site installation is performed at the physical location of the existing site 282, and the communication equipment of the co-location candidate site 380 is installed on the support structure of the existing site 282 and / or using the site infrastructure. The communication equipment of the co-location candidate site 380 supports a communication technology different from the communication technology supported by the communication equipment of the existing site 282. The installed communication equipment of the co-location candidate site 380 constitutes the co-location candidate site 380 as an operating site that provides communication services to customers using a communication technology different from that of the existing site 282. For example, the system instructs site installation at the co-location candidate site 380 according to the site information of the co-location candidate site 380. When the site installation is completed, the co-location candidate site 380 may be referred to as a co-located site. In some embodiments, the unique site ID 350 of the co-location candidate site 380 is used to identify the co-location candidate site 380 during site installation at the same physical location as the existing site 282 and / or during communication with / by the co-located site after the site installation is completed.

[0076] In FIG. 3E, the screen 300E of the user interface shows various site information 370 - 375 of the collocation candidate site 380. The screen 300E is similar to the screen 200F and includes various items 370 - 375 of the site information of the collocation candidate site 380. The site information items 370 - 374 correspond to the site information items 270 - 274 described with respect to FIG. 2F. In particular, the collocation candidate site 380 is assigned a site ID 373 corresponding to the site ID 350 described with respect to FIG. 3D. Other site information items of the collocation candidate site 380 include the TSS status 371, the comment 372, a photo 374 of the actual site at the collocation candidate site 380, and the site type 375. One or more of the site information items 370 are automatically generated or input into the system by the system from a database (for example, the database 130). The comment 372 and the photo 374 are provided by a person such as a field engineer. The site type 375 "5G Sub6 Pole Site" matches and is defined by a collocation workflow 309 targeting the collocation of 5G Sub6 poles. The described site information items are an example. Other possible items in the site information are within the scope of various embodiments.

[0077] In FIG. 3F, the screen 300F of the user interface shows sites created or managed by the system. The screen 300F is similar to the screen 200G and includes various items 281 to 294 described with respect to FIG. 2G. For clarity, a nominal site 281, an existing site 282 corresponding to the nominal site 281, and a co-location candidate site 380 corresponding to the nominal site 281 and co-located with the existing site 282 are shown on the screen 300F, while other sites are omitted. Compared with the screen 200G, the screen 300F further shows the co-location candidate site 380. The site name 381 of the co-location candidate site 380 is the same as the site name 293 of the existing site 282 because the co-location candidate site 380 and the existing site 282 are co-located at the same physical location. The site ID 382 of the co-location candidate site 380 corresponds to the site ID 350 and is obtained by changing the site ID 294 / 250 of the existing site 282 described in FIG. 3D. As described with respect to FIGS. 3E to 3F, the site information of the co-location candidate site 380 is stored in a database such as the database 130. Site installation is performed at the physical location of the existing site 282, and the communication devices of the co-location candidate site 380 are installed on the support structure of the existing site 282 and / or using the site infrastructure. For example, the system instructs site installation at the existing site 282 according to the site information of the co-location candidate site 380. When the site installation is completed, the co-location candidate site 380 becomes an operating site and is referred to as a co-located site. In some embodiments, a unique ID 350, such as "REC23222000900", is used to identify the co-location candidate site 380 during site installation at the physical location of the existing site 282 and / or during communication with / by the co-located site after the site installation is completed.

[0078] In FIG. 3G, the user interface screen 300G shows the basic details of the 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 collocate site (or the collocation candidate site before site installation) 380, the physical location information 393, and the collocation flag 396. The physical location information 393 includes the latitude and longitude of the existing site 282 (or the candidate site 249 before site installation) as described in FIG. 2D. The collocation flag 396 may be Yes or No depending on the presence or absence of a site collocated with the existing site 282. In the example of FIG. 3G, the collocation flag 396 is Yes, corresponding to the existence of a collocate site (or a collocation candidate site) 380 at the existing site 282. In some embodiments, the collocation flag 396 "Yes" is automatically generated by the system, for example, when the collocation workflow 309 is executed.

[0079] As described herein, FIGS. 3D - 3G provide examples of site collocation within the same network generation but with different communication technologies. Next, further examples of site collocation with different network generations and with different communication technologies will be described with respect to FIGS. 3H - 3J.

[0080] In some embodiments, the site collocation process with different network generations also starts with a screen similar to screen 300A in FIG. 3A, except that the user input for the nominal site and the collocation process (or workflow) executed for the nominal site include different network generations. For example, the user selects a 4G ODSC (Outdoor Small Cell) site as the nominal site via the drop-down menu 301 and / or the input area 306, and further selects a 5G mmW collocation process (or workflow) via the input area 307 of screen 300A. As a result, the collocation process is executed to collocate a 5G mmW site with an existing 4G ODSC site. The collocation process further proceeds to enable the user to download or obtain the site information of the existing site 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 the existing site 332 corresponding to the nominal site selected by user input. Specifically, screen 300H shows that the existing site 332 has a site name 323 and a site ID 324 corresponding to the site name 293 and the site ID 294 described in connection with FIGS. 3F-3G. Screen 300H further 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 further shows the site type 325 “ODSC” of the existing site 332, that is, the existing site 332 is an existing 4G ODSC site.

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

[0083] As described with respect to FIG. 2E, the site ID 324 of the existing site 332 includes a plurality of symbols 251 to 259. In the example of FIG. 3I, the specific characters corresponding to the site ID 324 are "RAC2321000478", which are shown for the corresponding symbols 251 to 259.

[0084] The site ID 360 of the collocation candidate site 340 includes a plurality of symbols 351 to 357, 348, and 359. The symbols 351 to 357, and 359 correspond to the symbols 251 to 257, and 259 of the site ID 324. The specific characters or codes of the symbols 351 to 357 are defined in Tables 261 to 267 described with respect to FIG. 2E. An example of the specific characters or codes of the symbol 348 is defined in Table 368 as described herein.

[0085] In some embodiments, the site ID 360 of the collocation candidate site 340 is obtained by changing a part of the site ID 324 while maintaining another part of the site ID 324. For example, the part of the site ID 324 remaining in the site ID 360 includes information regarding the physical location of the existing site 332 because the collocation candidate site 340 and the existing site 332 are collocated. Accordingly, the characters within the symbols 253 to 255 of the site ID 324 are the same as the characters within the symbols 353 to 355 of the site ID 360. The part of the site ID 324 remaining in the site ID 360 further includes a class symbol. Accordingly, the characters within the symbol 256 of the site ID 324 are the same as the characters within the symbol 356 of the site ID 360.

[0086] In the example of FIG. 3I, the characters within symbols 251, 252 of site ID 324 are the same as the characters within symbols 351, 352 of site ID 360, indicating that the same operator and vendor are associated with both the existing site 332 and the co-location candidate site 340. In some embodiments, if different operators and / or vendors are associated with the existing site 332 and the co-location candidate site 340, the characters within symbol 251 and / or symbol 252 of site ID 324 are different from the characters within symbol 351 and / or symbol 352 of site ID 360.

[0087] The portion of site ID 324 that has been changed to obtain the corresponding portion of site ID 360 contains information regarding different communication technologies correspondingly supported by the existing site 332 and the co-location candidate site 340. In the example of FIG. 3I, the characters within symbol 257 of site ID 324 are different from the characters within symbol 357 of site ID 360, indicating that the existing site 332 and the co-location candidate site 340 support different communication technologies. Specifically, referring to Table 267 of FIG. 2E, the character "3" within symbol 357 of site ID 360 indicates that the frequency band of the co-location candidate site 340 is 28 GHz. This information is consistent with and defined by the 5G mmW co-location process (or workflow) selected by the user on screen 300A. Referring to Table 267 of FIG. 2E, the character "1" within symbol 257 of site ID 324 indicates that the frequency band of the existing site 332 is 1.7 GHz, i.e., a communication technology different from the 5G mmW (28 GHz) communication technology of the co-location candidate site 340.

[0088] The portion of Site ID 324 that has been changed to obtain the corresponding portion within Site ID 360 includes the first symbol 258 out of symbols 258 - 259 that specify the sequence number of Site ID 324. Symbol 258 is often not used because it is unlikely that all six symbols (about one million sequence numbers) 258 - 259 are required to identify all sites within a sub-region. Symbol 348 of Site ID 360 corresponds to the unused symbol 258 of 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 collocation flag (or collocation class) symbol, specifies the collocation status of a site. As shown in Table 368, when the character within symbol 348 is '0', the corresponding site is not collocated, and when the character within symbol 348 is '6' (or any other character other than '0'), the corresponding site is collocated.

[0089] The sequence number of Site ID 360 is composed of five symbols 359, which is one less than the sequence number (six symbols) of Site ID 324. The character '00478' within symbol 359 is the same as the character '00478' within symbol 259 of Site ID 324. That is, except for the first symbols 258 and 348, the sequence numbers are the same between Site ID 324 and Site ID 360 (between symbol 259 and symbol 359). The total number of symbols of Site ID 360 remains the same as the total number of symbols of Site ID 324. As a result, in at least one embodiment, the system does not require a large conversion to adapt to the new or changed format of Site ID 360.

[0090] In the example of FIG. 3I, the collocation candidate site 340 is assigned a unique site ID "RAC2323600478". This site ID indicates the following information regarding the collocation candidate site 340: namely, operator R, vendor A, physically located in Aichi Prefecture, the sub-region (prefecture) in the Tokai region (jurisdiction), class 2 (Outdoor Micro), frequency band 28 GHz, collocation status Yes, and sequence number 00478. The site ID 360 "RAC2323600478" and the site ID 324 "RAC2321000478" differ in two symbols: symbol 357 (frequency band) and symbol 348 (collocation flag or collocation 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 wholly or partly specified by the 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 installation of the site at the same physical location as the existing site 332 and / or during communication with the collocated site after the site installation is complete, as described herein with respect to the collocation candidate site 340 and / or the site ID 350.

[0092] In FIG. 3J, a screen 300J with a user interface similar to that of screen 300G is displayed to show the basic details of the collocation candidate site 340 (or the collocated site after site installation). Specifically, screen 300J shows that the collocation candidate site 340 has the same site name 343 as the site name 323 of the existing site 332, the site ID 360 described in FIG. 3I, and the unique site ID 322 of the corresponding nominal site. Screen 300J further shows the site type 345 “5G mmW Pole ODSC” of the collocation candidate site 340, that is, the collocation candidate site 340 is a 5G mmW site. Screen 300J further shows the physical location information 346 of the collocation candidate site 340 including the latitude and longitude of the existing site 332. The collocation flag is not shown on screen 300J. Since the collocation status of the collocation candidate site 340 is reflected in the site ID 360 itself, for example, by the collocation flag symbol 348, the collocation flag is unnecessary. In some embodiments, the format of the site ID (e.g., 324) of the collocation candidate site (e.g., 340) is different, and except for the absence of the collocation flag, the site collocation with different network generations is similar to the site collocation within the same network generation described with respect to FIGS. 3D to 3G.

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

[0094] In some embodiments, when site collocation 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 FIGS. 3D - 3F), the site ID (e.g., 250) of the existing site (e.g., 282) and the site ID (e.g., 350) of the collocation candidate site (e.g., 380) have the same format (e.g., as described with respect to FIG. 2E). To indicate the collocation status of the existing site and the collocation candidate site, another collocation flag (e.g., 396) is generated outside the site ID.

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

[0096] In some embodiments, by implementing site collocation, new or upgraded technologies may be added to an existing site, saving the cost and time of site surveys and / or constructing support structures and / or site infrastructure. Existing arrangements, such as support structures and / or site infrastructure, may be used to facilitate telecommunications signals for new customer - facing technologies. 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 that uses a different second communication technology (e.g., mmW) within the same network generation, or vice versa. As described with respect to FIG. 2C, the time and cost of site surveys or the TSS process, as well as the time and cost of constructing poles or towers and / or related site infrastructure, can be saved.

[0097] In one or more embodiments, the site collocation process includes reusing the unique site ID of an existing site by changing only a part, rather than all, of the site ID in order to obtain the unique site ID of the newly collocated site. The site ID of the newly collocated site is then used for the installation and / or operation of the newly collocated site. In at least one embodiment, the size (e.g., the number of symbols) of the site ID of the collocated site remains the same as that of the existing site, enabling the site collocation process to be carried out in a quick and easy manner without causing major changes to the system. Further features and / or advantages are within the scope of various embodiments.

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

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

[0100] In operation 403, one or more candidate sites corresponding to the nominal site are determined. For example, available candidate sites near the nominal site are determined and downloaded via an API call, as described with respect to FIGS. 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 administrators, execute a candidate site selection process according to a workflow to determine a final candidate site.

[0102] In operation 406, for example, as described with respect to FIG. 2E, a site ID for the final candidate site is generated. In some embodiments, the site ID is generated by the system. Other site information items for the final candidate site and / or the nominal site are generated and stored, for example, as described with respect to FIGS. 2F-2G. In some embodiments, the site information for the final candidate site including the site ID is generated by the system. As described herein, site installation is performed to configure the final candidate site as an operating site, and the operating site corresponds to the nominal site and is in turn referenced as an existing site.

[0103] In operation 407, a collocation process is initiated and a collocated site is created. For example, the user selects a nominal site and a collocation project (or collocation workflow) to be performed on the nominal site, as described with respect to FIG. 3A.

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

[0105] In operation 409, for example, as described with respect to FIGS. 3D and / or 3I, a site ID of a collocation candidate site is generated. In some embodiments, the site ID is generated by the system. Other site information items of the collocation candidate site are generated and stored, for example, as described with respect to FIGS. 3E-3H, 3J. In some embodiments, the site information of the collocation candidate site including the site ID is generated by the system. As described herein, site installation is performed to configure a collocation candidate site to be an operating site using a new or upgraded communication technology, and the operating site is then referred to as a collocated site at the same physical location as the existing site corresponding to the nominal site.

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

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

[0108] In operation 424, in order to obtain the second ID of the co-location candidate site to be co-located with the existing site, while maintaining the second part of the first ID, the first part of the first ID is changed. For example, as described with respect to FIGS. 3D and 3I, the first part of site IDs 250, 324 includes at least information on the communication technology supported by the existing sites 282, 332 and / or unused symbols. This first part of site IDs 250, 324 is changed to include information on a different communication technology supported by the co-location candidate sites 380, 340 and / or information on the co-location status of the co-location candidate site 340. The second part of site IDs 250, 324 includes at least information on the physical location of the existing sites 282, 332 and / or information on the class of the existing sites 282, 332. This second part remains unchanged. Other information within site ID 250 may or may not be changed depending on the specific situation. Such other information includes information on the vendor and operator. A sequence number is generated for the co-location candidate sites 380, 340. As a result, the site IDs 350, 360 of the co-location candidate sites 380, 340 are generated completely or at least partially by the system.

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

[0110] FIG. 4C is a flowchart of a process 400C for implementing site co-location according to some embodiments. In some embodiments, process 400C is executed by at least one processor that implements at least one component of the service system 110 and includes one or more 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 includes a first ID of the existing site, and the first ID indicates a first communication technology supported by the existing site. For example, as described with respect to FIGS. 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 respect to FIGS. 3D and 3I, and the site IDs 250 and 324 indicate a first communication technology supported by the existing sites 282 and 332, such as, for example, frequency band "3" within site ID 250 or frequency band "1" within site ID 324.

[0112] In operation 444, second site information of a collocation candidate site to be collocated with the existing site is at least partially generated. The second site information includes a second ID of the collocation candidate site. The second ID is based on the first ID and indicates a second communication technology supported by the collocation candidate site, and the second communication technology is different from the first communication technology. For example, site information of a collocation candidate site 380 to be collocated with the existing site 282 is at least partially generated, as described with respect to FIGS. 3D and 3E. The site information of the collocation candidate sites 380 and 340 includes site IDs 350 and 360 of the collocation candidate sites 380 and 340. The site IDs 350 and 360 are based on the site IDs 250 and 324 and indicate a second communication technology supported by the collocation candidate sites, where the second communication technology, such as, for example, frequency band "2" of site ID 350 or frequency band "3" of site ID 360, is different from the first communication technology, such as, for example, frequency band "3" of site ID 250 or frequency band "1" of site ID 324. Operation 444 further includes operation 446 or operation 448 according to the network generations of the existing site and the collocation candidate site.

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

[0114] In operation 448, in response to the first communication technology and the second communication technology being of different network generations, a collocation flag symbol is included in the second ID instead of an unused symbol. For example, as described with respect to FIGS. 3H - 3J, when site collocation is performed to collocate a 5G site with an existing 4G site, a collocation 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, as described herein, the second ID is used, for example, when instructing to install a collocation candidate site as a collocated site at the physical location of an existing site or when communicating with the collocated site upon completion of the installation. In at least one embodiment, one or more of the advantages described herein can be realized in one or more of processes 400A, 400B, 400C.

[0116] The methods and algorithms described include exemplary operations, but they do not necessarily have to be executed in the order shown. The operations may be added, replaced, reordered, and / or deleted as necessary, 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 considering the present disclosure.

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

[0118] The computer system 500 includes a hardware processor 502 and a non-transitory computer-readable storage medium 504. In particular, the storage medium 504 is encoded by, i.e., stores, computer program code 506, which is a set of executable instructions, such as one or more algorithms, programs, applications, etc., and is a set of executable instructions for a system, component, and / or module. Execution of the instructions 506 by the hardware processor 502 implements some or all of the methods described herein according to one or more embodiments (hereinafter, the described processes and / or methods).

[0119] The processor 502 is coupled to the 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. Since the network interface 512 is connected to a network 514, the processor 502 and the computer-readable storage medium 504 can be connected to external elements or devices via the network 514. The processor 502 is configured to execute the computer program code 506 encoded in the computer-readable storage medium 504 to enable the use of the computer system 500 for executing 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 a suitable hardware processing device.

[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 memory or solid-state memory, magnetic tape, removable computer diskettes, random access memory (RAM), read-only memory (ROM), rigid magnetic disks, and / or optical disks. In one or more embodiments using optical disks, computer-readable storage medium 504 includes 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, storage medium 504 stores computer program code 506 configured to enable computer system 500 to be used to execute part or all of the described processes and / or methods. In one or more embodiments, storage medium 504 also stores information or data 507 such as event data, consumer data, enterprise data, policies, component configurations, etc., used in part or all of the described processes and / or methods.

[0122] The I / O interface 510 is coupled to an external circuit. In one or more embodiments, the I / O interface 510 includes a keyboard, keypad, mouse, trackball, trackpad, touch screen, 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 the 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 enables 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, or a wired network interface such as ETHERNET, USB, IEEE-864. In one or more embodiments, some or all of the described processes and / or methods are implemented on two or more computer systems 500.

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

[0125] In some embodiments, some or all of the described processes and / or methods are realized as the functions of a program stored in a non-transitory computer-readable recording medium. A computer-readable recording medium storing a program 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 a memory unit, such as an optical disk like a DVD, a magnetic disk like a hard disk, a semiconductor memory like a ROM, a RAM, a memory card.

[0126] The foregoing outlines the features of some embodiments so that those skilled in the art may better understand aspects of the present disclosure. It should be understood that those skilled in the art can readily use the present disclosure as a basis for designing or modifying other processes and structures for carrying out the same purposes of the embodiments introduced herein and / or achieving the same advantages. Those skilled in the art should also recognize that such equivalent configurations do not depart from the spirit and scope of the present disclosure and that various conversions, substitutions, and modifications can be made herein without departing from the spirit and scope of the present disclosure.

Claims

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

2. The first part of the first ID includes first information indicating a first communication technology supported by the existing site, in the changing, the first information is converted into second information within the second ID, the second information indicating a second communication technology supported by the co-location candidate site, the second communication technology being different from the first communication technology, The method according to claim 1.

3. The first part of the first ID includes first information indicating a first vendor associated with the existing site, in the changing, 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 according to claim 1.

4. The first communication technology and the second communication technology are of the same network generation, the changing includes generating a second sequence number of the second ID, the second sequence number being different from a first sequence number of 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 at the same physical location, The method according to claim 2.

5. The second part of the first ID includes information regarding the physical location of the existing site, remains unchanged within the second ID, and indicates that the co-location candidate site has the same physical location as the existing site. The method according to claim 1.

6. Said changing includes the following: Changing a first symbol within the first ID to a different second symbol within the second ID, wherein the first symbol indicates a first communication technology of a first network generation, is supported by the existing site, the second symbol indicates a second communication technology of a second network generation, is supported by the co-location candidate site, the second communication technology is different from the first communication technology, and the second network generation is different from the first network generation; Converting an unused symbol within the first sequence number of the first ID to a co-location flag symbol within the second ID, wherein the co-location flag symbol indicates the co-location status of the co-location candidate site; and Maintaining the remaining symbols within the first sequence number of the first ID unchanged and making the remaining symbols within the first sequence number the second sequence number of the second ID, where the number of symbols within the second sequence number is one less than the number of symbols within the first sequence number. The method according to claim 1.

7. The first ID and the second ID include the same number of symbols. The method according to claim 6.

8. Each of the first ID and the second ID: A symbol indicating the operator of the corresponding existing site or co-location candidate site; A symbol indicating the vendor associated with the corresponding existing site or co-location candidate site; A symbol indicating the region including the physical locations of the existing site and the co-location candidate site; Two symbols indicating the sub-regions including the physical locations of the existing site and the co-location candidate site; A symbol indicating the class of the existing site and the co-location candidate site; A symbol indicating the frequency band of the corresponding existing site or co-location candidate site; and a series of symbols indicating the sequence numbers of the corresponding existing site or co-location candidate site, the series of symbols of the first ID includes a first symbol and the remaining symbols, the series of symbols of the second ID are: a co-location flag symbol and the remaining symbols within the series of symbols of the first ID, where the co-location flag symbol corresponds to the first symbol within the series of symbols of the first ID and indicates the co-location status of the co-location candidate site, or, one or more symbols corresponding to and different from the remaining symbols among the series of symbols of the first ID, The method according to claim 1.

9. in response to user input of the nominal site and a co-location process to be performed on the nominal site, obtaining first site information of the existing site corresponding to the nominal site, where the first site information includes the first ID of the existing site; after changing the first ID to obtain the second ID, generating second site information of the co-location candidate site, where the second site information includes the second ID; and, further including instructing the installation at the co-location candidate site according to the second site information. The method according to claim 1.

10. the existing site comprises: a support structure; and, a first communication device that supports a first communication technology and is installed on the support structure, and, the installation includes installing a second communication device of the co-location candidate site on the support structure of the existing site, where the second communication device supports a second communication technology different from the first communication technology. The method according to claim 9.

11. obtaining one or more candidate sites within a predetermined radius from the nominal site; performing 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, further comprising instructing installation of the determined candidate site to obtain the existing site corresponding to the nominal site The method according to claim 1

12. further comprising using the first ID for communication with the existing site upon completion of the installation of the existing site The method according to claim 11

13. A system for implementing site co-location, 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 wherein 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 including a first identification information (ID) of the existing site, the first ID indicating a first communication technology supported by the existing site; generate at least partial second site information of a co-location candidate site to be co-located with the existing site, the second site information including a second ID of the co-location candidate site, the second ID indicating a second communication technology supported by the co-location candidate site based on the first ID, the second communication technology being different from the first communication technology; and instruct installation of the co-location candidate site as a co-located site at a physical location of the existing site, or communicate with the co-located site upon completion of the installation such that in at least one of them, the second ID is used System

14. The executable instructions, when executed by the at least one processor, cause the at least one processor to: visually present a first input area for receiving user input of the nominal site and a co-location process to be performed on the nominal site; and obtain 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 according to claim 13

15. When the executable instructions are executed by the at least one processor, the at least one processor is caused to: visually present a second input area for receiving user instructions for retrieving the existing site corresponding to the nominal site and obtaining first site information of the existing site when the user inputs the nominal site and the user input of the collocation process in the first input area; The system according to claim 14.

16. When the executable instructions are executed by the at least one processor, the at least one processor is caused to: in response to the user instructions received in the second input area, search for the existing site as a site that is closest to the nominal site and satisfies one or more conditions defined in the collocation process; The system according to claim 15.

17. When the executable instructions are executed by the at least one processor, the at least one processor is caused to: visually present the second ID obtained by changing the first part of the first ID while maintaining the second part of the first ID, where the first part of the first ID includes a first symbol indicating the first communication technology supported by the existing site, the first symbol is converted into a different second symbol of the second ID, and the second symbol indicates the different second communication technology supported by the collocation candidate site; the second part of the first ID includes information regarding the physical location of the existing site and remains unchanged in the second ID to indicate that the collocation candidate site has the same physical location as the existing site; The system according to claim 13.

18. The first communication technology and the second communication technology are of different network generations, When the executable instructions are executed by the at least one processor, the at least one processor is caused to, on the same screen: the unique ID of the nominal site corresponding to the existing site and the collocation candidate site; information regarding the physical locations of the existing site and the collocation candidate 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 according to claim 13

19. The first communication technology and the second communication technology are of the same network generation When the executable instructions are executed by the at least one processor, the at least one processor is caused to, within the same screen: the first ID of the existing site information regarding physical locations of the existing site and the collocation candidate site unique IDs of the nominal sites corresponding to the existing site and the collocation candidate site the second ID of the collocation candidate site; and visually presenting a collocation flag indicating that the existing site and the collocation candidate site are collocated at the same physical location The system according to claim 13

20. A computer program product comprising a non-transitory and tangible computer-readable storage medium storing a computer program When the computer program is executed by at least one processor, the computer program causes the at least one processor to: obtain first site information of an existing site corresponding to a nominal site, the first site information including a first identification information (ID) of the existing site, the first ID indicating a first communication technology supported by the existing site generate second site information of at least a part of 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 indicating a second communication technology supported by the collocation candidate site based on the first ID, the second communication technology being different from the first communication technology instruct installation of the collocation candidate site as a collocated site at a physical location of the existing site, or communicate with the collocated site upon completion of the installation execute using the second ID in at least one of the above A computer program product

Images