Method for managing optical fiber connectivity and system for using same

Abstract

The optical fiber connectivity management system includes a non-transitory computer-readable medium configured to store instructions and a processor coupled to the non-transitory computer-readable medium. The processor is configured to execute instructions for receiving optical fiber data related to a plurality of target areas for optical fiber connections. The processor is further configured to execute instructions for preparing a plurality of optical fiber connectivity requests corresponding to the plurality of target areas for optical fiber connections and for generating an optical fiber application based on the plurality of optical fiber connectivity requests. The processor is further configured to execute instructions for directing a transmitter to transmit the optical fiber application to an optical fiber operator and for receiving a response from the optical fiber operator, the response indicating whether the plurality of optical fiber connectivity requests are approved for optical fiber connectivity establishment.

Description

[Technical Field]

[0001] FIELD OF THE INVENTION This specification relates to methods for managing optical fiber connectivity and systems for using same. [Background technology]

[0002] In the telecommunications industry, optical fiber providers install optical fibers for fiber optic communications. Some optical fibers that are not currently used to transmit information in the form of light pulses are called dark fibers. When a telecommunications service provider wishes to expand service in a desired area that currently does not have optical fiber connectivity for optical fiber communications, the telecommunications service provider requests an allocation of dark fiber for optical fiber connectivity between base stations and servers. Once approved, the telecommunications service provider contracts to open a construction line in the desired area to obtain optical fiber connectivity to connect the base station to the rest of the telecommunications network. Summary of the Invention

[0003] In some embodiments, the system includes a non-transitory computer-readable medium configured to store instructions. The system further includes a processor coupled to the non-transitory computer-readable medium. The processor is configured to execute instructions for receiving optical fiber data related to a plurality of target areas for allocating optical fiber connectivity. The processor is further configured to execute instructions for preparing a plurality of optical fiber connectivity requests corresponding to the plurality of target areas. The processor is further configured to execute instructions for generating an optical fiber connectivity application based on the plurality of optical fiber connectivity requests. The processor is further configured to execute instructions for instructing a transmitter to transmit the optical fiber connectivity application to an optical fiber operator. The processor is further configured to execute instructions for receiving a response from the optical fiber operator, the response indicating whether the plurality of optical fiber connectivity requests are approved for optical fiber connectivity construction.

[0004] In some embodiments, a method includes receiving optical fiber data related to a plurality of target areas for allocating optical fiber connectivity. The method further includes preparing a plurality of optical fiber connectivity requests corresponding to the plurality of target areas. The method further includes generating an optical fiber connectivity request based on the plurality of optical fiber connectivity requests. The method further includes instructing a transmitter to transmit the optical fiber connectivity request to an optical fiber operator. The method further includes receiving a response from the optical fiber operator. The response indicates whether the plurality of optical fiber connectivity requests are approved for optical fiber connectivity establishment (establishment of optical fiber connections). In some embodiments, the method further includes updating the optical fiber connectivity request based on the data received from the optical fiber operator. In some embodiments, the method further includes determining whether the response from the optical fiber operator is a positive acknowledgment that the plurality of optical fiber connectivity requests have been approved or a negative acknowledgment that the plurality of optical fiber connectivity requests have not been approved.

[0005] In some embodiments, a non-transitory computer-readable medium is configured to store instructions that cause a processor to execute the instructions to perform a method. The instructions cause the processor to receive optical fiber data related to a plurality of target areas for optical fiber connectivity. The instructions further cause the processor to prepare a plurality of optical fiber connectivity requests corresponding to the plurality of target areas for optical fiber connectivity. The instructions further cause the processor to generate an optical fiber connectivity application based on the plurality of optical fiber connectivity requests. The instructions further cause the processor to command a transmitter to transmit the optical fiber connectivity application to an optical fiber operator. The instructions further cause the processor to receive a response from the optical fiber operator indicating whether the plurality of optical fiber connectivity requests are approved for optical fiber connectivity establishment.

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

[0007] [Figure 1] 1 is a schematic diagram of a telecommunications network, according to some embodiments.

[0008] [Figure 2] 1 is a flowchart of a method for managing fiber optic facilities according to some embodiments.

[0009] [Figure 3] 1 is a flowchart of a method for managing fiber optic connectivity (fiber optic connections) according to some embodiments. [Figure 3C] 3 and is a flowchart of a method for managing optical fiber connectivity according to some embodiments.

[0010] [Figure 4] FIG. 1 is a diagram of a user interface for managing fiber optic connectivity, according to some embodiments.

[0011] [Figure 5] 1 is a block diagram of a system for managing fiber optic connectivity, according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0012] The following disclosure provides many different embodiments or examples for implementing various features of the provided subject matter. To simplify the disclosure, specific examples of components, values, operations, materials, arrangements, etc. are described below. Of course, these are merely examples and are not intended to be limiting. Other components, values, operations, materials, arrangements, etc. are encompassed by the present invention. For example, when a first feature (portion, element, etc.) is formed above or on a second feature (portion, element, etc.) in the following description, this may include embodiments in which the first and second features are formed in direct contact with each other, and may also include embodiments in which an additional feature may be formed between the first and second features such that the first and second features are not in direct contact with each other. Additionally, the present disclosure may repeat reference numerals and / or letters in various examples. This repetition is for the purposes of brevity and clarity and does not, in itself, dictate a relationship between the various embodiments and / or configurations discussed.

[0013] Once a telecommunications service provider selects a desired area for establishing a new base station for its telecommunications network, a request for opening a site construction is submitted to the fiber optic operator. The desired area often includes multiple target sites, and because construction of each target site is approved separately, multiple requests for the multiple target sites are submitted to the fiber optic operator. In such cases, in some approaches, multiple requests are manually prepared and submitted to the fiber optic operator for approval.

[0014] Each request is manually prepared for submission and manually monitored after submission by workers within the service provider until the request is approved by the fiber optic provider. Each request undergoes multiple different levels of review / approval; for example, a request is often reviewed by a team leader, manager, department manager, and then a financial manager before final approval. Failure to timely identify and address new or updated information requests at any of these levels delays final approval and ultimately delays the expansion of the telecommunications network. Delays in the expansion of the telecommunications network adversely affect users of the telecommunications network. In some approaches, fiber optic connectivity requests are managed in a spreadsheet format such as Excel®. If the response from the reviewer / review department is negative, for example, if the task is rejected or requires revision, the worker working on the request manually identifies the negative response, uploads the response details to a spreadsheet form, corrects the information in the spreadsheet form, and resubmits the request. Due to the large number of requests submitted, the manual entry and tracking of fiber optic connectivity is time-consuming and management of fiber optic connectivity requests is inefficient. This lack of efficiency causes delays in planned network expansions, and customers are likely to experience poor quality in areas where the network has not yet been expanded.

[0015] The system provides a workflow along the tracking of fiber optic connectivity requests, improving the efficiency of managing fiber optic connectivity. As soon as a technician determines a site is a target site for construction, the system can initiate a workflow to prepare the fiber optic connectivity request. At the same time, for example, a service provider can discuss lease agreements with businesses that may be interested in renting the fiber optic network that will be established at the target site.

[0016] The system automatically identifies and imports data from non-transitory computer-readable media to prepare optical fiber connectivity requests. The system can directly communicate with external devices, such as an optical fiber provider's server, to retrieve information and report on the progress of the request. Information sent from the external device is automatically stored and recorded in the system. The system also allows for human interaction to modify the optical fiber connectivity request. Furthermore, the system can handle the preparation of bulk optical fiber connectivity requests, generate optical fiber connectivity applications for the bulk optical fiber connectivity requests, send the optical fiber connectivity applications to the optical fiber provider, and monitor the bulk optical fiber connectivity requests in the optical fiber connectivity applications. Once the optical fiber connectivity application is approved, the telecommunications service provider's team can be automatically notified to begin construction at the target site indicated in the optical fiber connectivity request, and the optical fiber will be ready for use. This system allows telecommunications service providers to control the optical fiber connectivity application process with high levels of data security and reduced latency. As a result, telecommunications network expansion becomes more efficient and network customers experience improved quality of service over a wider geographic area.

[0017] 1 is a schematic diagram of a telecommunications network 100 according to some embodiments. The telecommunications network 100 includes multiple base stations 110, multiple group centers 120, and a data center 130. Optical fibers that provide connectivity to customers, i.e., via one or more base stations 110 to the data center 130, are referred to as front haul optical fibers 140. Optical fibers that provide direct connectivity to databases, i.e., the group centers 120, are referred to as back haul optical fibers 150. The back haul optical fibers are used as a medium for connecting one or more group centers 120 to one or more base stations 110 and the data center 130. In some embodiments, the structure of each of the back haul optical fibers 150 is the same as the structure of each of the front haul optical fibers 140. In some embodiments, the structure of at least one back haul optical fiber 150 is different from the structure of at least one front haul optical fiber 140.

[0018] In some embodiments, the location of the proposed new fronthaul optical fiber 140 is available for selection by a telecommunications service provider to expand its telecommunications network. For example, in some embodiments, in response to a decision to add a new base station 110, a new fronthaul optical fiber 140 is selected to connect the new base station 110 to a corresponding group center 120.

[0019] In some embodiments, the group centers 120 are segmented into group centers such as an east region and a west region. Each of the east region and the west region includes a district or prefecture, and each district (region) or prefecture is assigned a predetermined identification number. Each of the group centers 120 includes a processor and a non-transitory computer-readable medium for storing data for the district or prefecture within the corresponding east region or west region. When an area is selected for optical fiber connectivity construction (construction of optical fiber connections), one or more sites included in the area are identified, and a corresponding group center 120 can be selected to provide data for one or more sites included in the area.

[0020] Like group center 120, data center 130 also includes a processor and non-transitory computer-readable media. In some embodiments, data center 130 is integrated with one or more group centers 120. In some embodiments, data center 130 is segmented from each of group centers 120. Data center 130 provides access to information, such as the Internet, to users connected to base stations 110 of the telecommunications network.

[0021] FIG. 2 is a flowchart of a method 200 for managing optical fiber installation, according to some embodiments. In some embodiments, method 200 is implemented to expand telecommunications network 100 ( FIG. 1 ). In some embodiments, method 200 is implemented for a telecommunications network other than telecommunications network 100 ( FIG. 1 ). In some embodiments, method 200 can be implemented by a telecommunications service provider, e.g., a service provider of telecommunications network 100 ( FIG. 1 ), to install or allocate optical fiber connectivity for fronthaul optical fiber 140, with approval from the optical fiber provider, thereby establishing optical fiber connectivity at target sites, e.g., one or more base stations 110 ( FIG. 1 ). Method 200 can collect data from a non-transitory computer-readable medium at one or more group centers, e.g., group center 120 ( FIG. 1 ), prepare one or more requests for one or more target sites, generate a request including the one or more requests, and transmit the generated request to an external device, such as a server at the optical fiber provider. The method 200 can also receive feedback from an external device to update the application until construction of the target site or sites begins.

[0022] Method 200 includes operation 202 in which a fiber optic connectivity request is triggered. In some embodiments, once an area is selected for building an optical fiber communications network, a service provider assigns a technical engineer to visit target sites within the selected area and conduct a technical site survey to determine whether the target sites are candidates for construction. The results of the determination are transmitted to a system capable of implementing method 200. In response to determining the target sites as candidates for construction, a fiber optic connectivity request for the target sites is triggered. In some embodiments, operation 202 is performed automatically in response to receiving information indicating that the target sites are candidates for construction.

[0023] In some embodiments, the selected area includes a plurality of target sites determined as candidates for construction, and a plurality of optical fiber connectivity requests corresponding to one or more of the target sites are triggered. In some embodiments, some of the plurality of target sites are determined as candidates for construction, while other target sites in the same area are still under evaluation, and optical fiber connectivity requests for the plurality of candidate target sites are triggered. Optical fiber connectivity requests for other target sites under evaluation are triggered in response to the other target sites being determined as candidates for construction.

[0024] Method 200 includes an operation 204 in which a request for optical fiber connectivity is prepared for an optical fiber connectivity application. In some embodiments, the request for optical fiber connectivity is prepared by collecting data from one or more group centers 120 corresponding to the target site for which optical fiber connectivity is requested. In some embodiments, the collected data includes information of base stations 110 in a selected area, such as base station name, equipment installed at the base station, base station type, or other suitable information. The collected data further includes information of the target site from the corresponding group center 120, such as, but not limited to, the district or prefecture name, the official name of the city, the commonly known name of the city, the street number, the block number, the building name, the nearest utility pole name, and the name of the optical fiber operator branch.

[0025] In some embodiments, when multiple target sites within an area are determined for construction, operation 204 prepares a batch of optical fiber connectivity requests for the target sites simultaneously. Preparing requests for multiple target sites simultaneously increases the efficiency of expanding the telecommunications network and, as a result, increases customer satisfaction.

[0026] Method 200 includes operation 206, in which an optical fiber connectivity request (application for optical fiber connection) is generated. The optical fiber connectivity request is generated to include one or more of the optical fiber connectivity requests prepared in operation 204. In some embodiments, the optical fiber connectivity request is generated as a CSV (Comma Separated Values) file acceptable by the optical fiber operator. In some embodiments, the optical fiber connectivity request is generated in a different format to meet the requirements of the optical fiber operator. In some embodiments, in response to multiple optical fiber connectivity requests being prepared in operation 204, operation 206 generates an optical fiber connectivity request that includes all of the prepared optical fiber connectivity requests. In some embodiments, operation 206 allows a user to select one or more of the optical fiber connectivity requests and generate an optical fiber connectivity request that includes one or more of the selected optical fiber connectivity requests.

[0027] Method 200 includes operation 208, in which the optical fiber connectivity request generated in operation 206 is submitted to an external device, such as an optical fiber operator's server. The optical fiber connectivity request is transmitted to the optical fiber operator's server over an Internet network. In some embodiments, the optical fiber connectivity request is transmitted wirelessly. In some embodiments, the optical fiber connectivity request is transmitted over a wired connection.

[0028] Method 200 includes operation 210, in which a response is received from an external device, such as a fiber optic operator's server. The response includes feedback regarding the fiber optic connectivity application submitted in operation 208. For a fiber optic connectivity application that includes multiple fiber optic connectivity requests, the response from the fiber optic operator includes feedback for each of the fiber optic connectivity requests.

[0029] The response includes the application ID assigned to the fiber optic connectivity application by the fiber optic operator. The application ID is relied upon to monitor or update the fiber optic connectivity application.

[0030] The response further includes one or more unique IDs assigned to each of the one or more optical fiber connectivity requests in the optical fiber connectivity application. The unique IDs can be used to track corresponding requests in the optical fiber connectivity application. For example, if the optical fiber connectivity application contains 10 requests for 10 target sites, the response includes 10 unique IDs corresponding to the 10 requests in the application. Information related to the unique IDs and the corresponding requests is stored in a non-transitory computer-readable medium of a system capable of implementing method 200. In some embodiments, in response to changes made to one or more requests, updates of the changes are automatically provided to the telecommunications service provider.

[0031] Method 200 includes operation 212, in which a determination is made as to whether the response from the fiber optic provider is an affirmative response. In some embodiments, the affirmative response indicates that the fiber optic connectivity application has been approved. In the case of a fiber optic connectivity application that includes multiple fiber optic connectivity requests, the affirmative responses from the fiber optic provider each include approval for the fiber optic connectivity request. In some embodiments, multiple affirmative responses are provided as the fiber optic connectivity application progresses through various levels of approval, for example, from team leaders, managers, department managers, etc. In such cases, in some embodiments, each of the affirmative responses is automatically updated with the fiber optic connectivity application.

[0032] In response to determining at operation 212 that the response is not affirmative, i.e., negative, method 200 proceeds to operation 218. At operation 218, the optical fiber connectivity application is updated to address concerns raised by the negative response received at operation 210. In some embodiments, a negative response indicates, without limitation, that the application is incomplete (e.g., information is missing in one or more optical fiber connectivity requests). In some embodiments, a negative response indicates that the application has been rejected (e.g., one or more target sites identified in the optical fiber connectivity request cannot proceed further). Thus, alternatives are provided for selecting target sites. Operation 218 can identify which requests in the optical fiber connectivity application contain missing information by relying on unique IDs assigned to the optical fiber connectivity requests, and then update the optical fiber connectivity application by entering (filling in) the missing information in the requests. In some embodiments, in operation 218, a notification, such as an email or text message, is generated and sent to the responsible worker prompting them to review the negative response and to modify the fiber optic connectivity application accordingly. In some embodiments, a system capable of implementing method 200 provides recommendation information to address concerns of the negative response or automatically generates a request for additional information prompted by the negative response. In some embodiments, the recommendation information is based on previous applications that experienced denials at a similar stage as the application progressing according to method 200.

[0033] In response to updating the fiber optic connectivity application in operation 218, method 200 proceeds to operation 208, where the updated application is again sent to the fiber optic operator for review and approval.

[0034] In response to determining that the response is affirmative at operation 212, method 200 proceeds to operation 214. The affirmative response indicates that one or more optical fiber connectivity requests in the optical fiber connectivity application have been approved by the optical fiber operator. At operation 214, build dates for the target sites are monitored. In some embodiments, information regarding build dates includes, but is not limited to, possible build dates, team availability dates, expected build dates, build dates, and target site opening dates. In some embodiments, if the build is delayed for any reason, operation 214 can monitor the delay. For example, the reasons causing the delay are imported into a system performing operation 214. In some embodiments, operation 214 tracks information regarding the build costs of one or more of the target sites. For example, a financial manager can review and modify the build costs at operation 214. In some embodiments, in response to a change in the build costs for the target sites requested in the optical fiber connectivity application, operation 214 automatically updates the application. In some embodiments, operation 214 periodically updates the cost information and automatically transmits the updated information to a computer or server, for example, via a transmitter. In some embodiments, operation 214 automatically transmits the updated cost information to a computer or server in response to a projected construction or site launch date that is within a threshold timeframe (a set timeframe) of the current date. In some embodiments, operation 214 automatically transmits the updated cost information to a computer or server in response to a set deadline for completing the delivery of construction costs.

[0035] Method 200 includes operation 216, in which construction is initiated at the target site. At operation 216, commands are transmitted, for example, by a transmitter, to instruct a construction team to begin construction at the target site identified in the approved fiber optic connectivity application. The instructions transmitted to the construction team, in some embodiments, include information such as permits, materials, etc. In some embodiments, the instructions are transmitted wirelessly. In some embodiments, the instructions are transmitted via a wired connection.

[0036] Method 200 provides a workflow from initiation of a fiber optic connectivity request to allocation of fiber optic connectivity at a target site to the construction of the target site. The workflow of method 200 can implement a bulk fiber optic connectivity request for multiple target sites, e.g., 100 target sites, 200 target sites, etc., in a single fiber optic connectivity application.

[0037] 3 is a flowchart of a method 300 for managing optical fiber connectivity, according to some embodiments. Method 300 is similar to method 200 (FIG. 2) with additional operations in managing optical fiber connectivity from initiation of an optical fiber connectivity request for constructing an optical fiber communications network at a target site through construction of the target site. In some embodiments, method 300 is implemented to expand telecommunications network 300 (FIG. 1). In some embodiments, method 200 is implemented for a telecommunications network other than telecommunications network 100 (FIG. 1).

[0038] Method 300 includes an operation 302 similar to operation 202 of method 200 according to some embodiments. In operation 302, a fiber optic connectivity request is triggered in response to determining a target site as a candidate for construction.

[0039] Method 300 includes operation 304. In operation 304, a fiber optic connectivity request is prepared, similar to operation 204 of method 200. In response to the plurality of fiber optic connectivity requests being triggered in operation 303, data for the plurality of fiber optic connectivity requests is imported from a group center(s) corresponding to the target site, such as group center(s) 120 (FIG. 1). In some embodiments, operation 304 can be performed by importing data from a spreadsheet form or a form in another suitable format.

[0040] Method 300 includes an operation 306 in which the fiber optic connectivity request prepared in operation 304 is edited. In some embodiments, the data in the prepared fiber optic connectivity request is edited by a service provider's personnel. In some embodiments, a system capable of implementing method 300 automatically provides some guidance for edits to be made to the request. In some embodiments, a pop-up window or box is provided that contains selectable text or a clickable link to connect to a database.

[0041] Method 300 includes operation 308, in which a determination is made as to whether the prepared optical fiber connectivity request is approved. In some embodiments, each request undergoes multiple different levels of review / approval; for example, requests are often reviewed by a team leader, a manager, a department manager, and then a financial manager before final approval. In some embodiments, a service provider manager reviews and approves the prepared request. In response to the prepared optical fiber connectivity request not being approved, operation 308 proceeds to operation 304 to prepare the optical fiber connectivity request. In some embodiments, the optical fiber connectivity request is not approved at operation 308 because certain documentation or information is missing, and the request is re-prepared at operation 304 by completing the missing information or attaching the missing documentation to the request. In response to the prepared optical fiber connectivity request being approved, operation 308 proceeds to operation 310.

[0042] In operation 310, a group center, e.g., group center 120 in FIG. 1, is selected according to the locations of the target sites included in the prepared optical fiber connectivity request. The group center stores data of the corresponding target sites. Upon selection of one or more group centers, data of the corresponding target sites is imported into the optical fiber connectivity request. In some embodiments, data of the corresponding target sites is automatically imported into the optical fiber connectivity request, e.g., from a database.

[0043] Method 300 includes operation 312 where a determination is made as to whether the prepared fiber optic connectivity request is complete. In response to determining that the prepared fiber optic connectivity request is not complete, operation 312 proceeds to operation 304 to re-prepare the fiber optic connectivity request. In response to determining that the prepared fiber optic connectivity request is complete, operation 312 proceeds to operation 314 where a fiber optic connectivity application is generated.

[0044] Operation 314 of method 300 is similar to operation 206 of method 200 according to some embodiments. Additionally, in some embodiments, a system task is generated in response to generating the fiber optic connectivity request.

[0045] Method 300 includes operation 316, in which the generated optical fiber connectivity request is submitted to an external device, such as an optical fiber operator's server. Operation 316 of method 300 is similar to operation 208 of method 200 according to some embodiments. In some embodiments, operation 316 further includes downloading the generated optical fiber connectivity request. In some cases, a service operator administrator downloads the generated optical fiber connectivity request, e.g., a CSV file, to determine whether further changes are required. In some embodiments, operation 316 includes uploading the optical fiber connectivity request. In some cases, the administrator uploads the optical fiber connectivity request to a computer within the system that implements method 300.

[0046] In some embodiments, the fiber optic connectivity application is generated differently for the east and west regions based on the location of the target site requested in the fiber optic connectivity application.

[0047] Method 300 includes an operation 318 in which a determination is made as to whether group center 120 should be changed. The generated optical fiber connectivity request is requested to build an optical fiber communications network and includes information on one or more target sites corresponding to one or more group centers. In some embodiments, a review is performed to determine whether the group center of the generated optical fiber connectivity request should be changed. For example, if it is determined that the group center selected for the optical fiber connectivity request does not correspond to the target site requested in the build request, the group center is determined to be changed. In some embodiments, a service provider administrator can review the generated optical fiber connectivity request. In some embodiments, the group center is determined to be changed in response to the group center not corresponding to the target site requested in the build request, in response to a new group center being activated that is closer to the target site, or in response to other suitable conditions.

[0048] In response to determining that the group center should be changed, operation 318 proceeds to operation 310 where a group center is selected for completion of the fiber optic connectivity request.

[0049] In response to determining that the group center should not be changed, operation 318 proceeds to operation 320, where a response is received from an external device, such as an optical fiber operator's server. Operation 320 of method 300 is similar to operation 210 of method 200 according to some embodiments.

[0050] Method 300 includes operation 324, in which a determination is made as to whether the system task generated in operation 314 should be canceled. Operation 324 allows the service provider to determine whether to proceed further with the generated fiber optic connectivity request.

[0051] In some embodiments, if the response received from the fiber optic operator indicates that the fiber optic connectivity request has been rejected by the fiber optic operator, operation 324 determines that the system task corresponding to the fiber optic connectivity request should be canceled. In response to determining that the system task has been canceled, operation 324 proceeds in a loop to operation 320 until it is determined that the system task is not canceled.

[0052] In some embodiments, if the response received from the fiber optic operator indicates that the fiber optic connectivity request is not rejected by the fiber optic operator, operation 324 determines that the system task corresponding to the fiber optic connectivity request is canceled, e.g., not approved or continued. In some embodiments, an administrator at the service operator approves the system task.

[0053] In response to determining that the system task is not canceled and is approved, operation 324 proceeds to operation 326, which determines whether the response received from the fiber optic carrier is affirmative.

[0054] In response to a determination that the response is not affirmative, e.g., the group center selected for the optical fiber connectivity request is incorrect, operation 326 proceeds to operation 310 to reselect a group center and complete the optical fiber connectivity request. In some embodiments, in response to operation 326 determining that the response is not affirmative, the result of the determination is automatically updated in the request and recommended information is provided. In response to a determination that the response is affirmative, operation 326 proceeds to operation 328 where an expected optical fiber installation date is set. The expected optical fiber installation date is the date on which optical fiber will be used to transmit information in an optical fiber communications network.

[0055] Operation 328 includes receiving data from an external device, such as a fiber optic provider's server. The received data includes an expected fiber optic installation date corresponding to a target site requested in the fiber optic connectivity application. In some embodiments, the received data includes a plurality of expected installation dates for each of the target sites requested in the fiber optic connectivity application. Additionally, the received data includes a building ID corresponding to the target site requested in the fiber optic connectivity application. In some embodiments, the received data includes a plurality of building IDs for each of the target sites requested in the fiber optic connectivity application.

[0056] Method 300 includes operation 330, in which the schedule for the optical fiber launch is adjusted. After the expected optical fiber launch date is set in operation 328, modifications to the expected optical fiber launch date may be made in operation 330. In some embodiments, operation 330 sends a request to the optical fiber operator to adjust the expected optical fiber launch date. In some embodiments, operation 300 sends several requests to the optical fiber operator to adjust the optical fiber launch date until the optical fiber launch date adjustment is complete, e.g., approved by the optical fiber operator.

[0057] Method 300 includes operation 332, in which a determination is made as to whether the system task created in operation 314 should be canceled. In some embodiments, the determination to cancel the system task is based on different criteria, such as a potential build delay, a lack of sufficient materials, or an unresolved supply chain issue. In some embodiments, a service provider administrator reviews the system task. In some cases, if the administrator does not approve of the fiber laydown date adjusted in operation 330, operation 332 determines that the system task is canceled. In response to determining that the system task is canceled, operation 322 proceeds to operation 330, which adjusts the fiber laydown date. In response to determining that the system task is not canceled, operation 332 proceeds to operation 334, where the build date is set.

[0058] Operation 334 includes receiving data from an external device, such as a fiber optic operator's server. The received data includes a set build date for construction to begin at the target sites requested in the fiber optic connectivity application. In some embodiments, the fiber optic connectivity application automatically updates the received data. In some embodiments, the received data includes multiple build dates for construction at multiple target sites requested in the fiber optic connectivity application, respectively. In some embodiments, the data is received wirelessly from the external device. In some embodiments, the data is received from the external device via a wired connection.

[0059] Method 300 includes operation 336, in which a determination is made as to whether the set build date should be canceled or rescheduled. In some embodiments, the cancellation or rescheduling of system tasks is determined based on different criteria, such as a potential build delay, a lack of sufficient materials, or an unresolved supply chain issue. In some embodiments, a service provider administrator reviews the set build date. In response to determining that the build date is canceled or rescheduled, operation 336 proceeds to operation 330, which coordinates the build date with the fiber optic provider. In response to determining that the build date is not canceled or rescheduled, operation 336 proceeds to operation 338.

[0060] At operation 338, a determination is made as to whether the build and open dates at the target site requested in the optical fiber connectivity application are confirmed. In some embodiments, a service provider administrator reviews and confirms the build and open dates. In response to a determination that at least one of the build and open dates should be changed, operation 338 proceeds to operation 330 to coordinate the build and / or open dates with the optical fiber provider. In response to a determination that the build and open dates will not be changed, the build and open dates are confirmed and operation 338 proceeds to operation 340. In some embodiments, the result of the determination is automatically updated in the corresponding optical fiber connectivity application.

[0061] In operation 340, a command to begin construction is sent to an external device. In some embodiments, the external device is a computer or server that manages construction of the target sites. In some embodiments, operation 340 includes sending, for example, by a transmitter, multiple commands to the external device to prompt the initiation of construction at the multiple target sites. In some embodiments, operation 340 includes sending a message to an administrator responsible for construction to begin construction at one or more target sites. Once construction has begun in operation 340, fiber optic connectivity is complete. In some embodiments, the fiber optic connectivity application is automatically updated with information indicating that construction has begun and / or completed.

[0062] In some embodiments, additional operations are included in method 300. For example, in some embodiments, determining construction costs is included in method 300. In some embodiments, at least one operation is omitted from method 300. For example, in some embodiments, operation 302 for triggering a fiber optic connectivity request is omitted from method 300.

[0063] 4 is an example of a user interface (UI) 400 for managing fiber optic connectivity, according to some embodiments. In some embodiments, UI 400 is a graphical UI (GUI) configured to receive information from a user, for example, via a touchscreen or other input / output (I / O) device.

[0064] User interface 400 provides information processed in some embodiments of method 200 or method 300. In some embodiments, user interface 400 includes a table such as that shown in FIG.

[0065] User interface 400 includes a first section that includes columns 402 and 404. Columns 402 and 404 indicate the status of a fiber optic connectivity application processed in method 200 or method 300. In some embodiments, a fiber optic connectivity application is processed in method 300, and the status of the fiber optic connectivity application from operations 302 through 340 of method 300 is indicated in columns 402 and 404. For example, the status may be "TRIGGERED," "PREPARE OPTICAL FIBER APPLICATION," "PREPARED," "APPROVE OPTICAL FIBER APPLICATION," "APPROVED," "COMPLETE OPTICAL FIBER APPLICATION," "EXPECTED OPENING DATE," "ADJUST SCHEDULE," "SCHEDULE ADJUSTED," "SET CONSTRUCTION DATE," and "CONFIRM CONSTRUCTION."

[0066] The user interface 400 further includes a second section that includes a number of columns 406, 408, 410, 412, 414, and 416. Information corresponding to columns 406, 408, 410, 412, 414, and 416 is imported from an internal device, such as a service provider's computer or server, or an external device, such as a fiber optic provider's server.

[0067] The target site information in column 406 includes information about the target site, such as a candidate ID and the address of the target site (postal code, prefecture / district, city, ward, street address, building name). The base station information in column 408 includes, but is not limited to, the base station type and base station name. The group center information in column 410 includes the device type or device location of the device located at the group center. For example, the device located at the group center is a baseband unit (BBU).

[0068] The status "TRIGGERED" in column 402 indicates that a fiber optic connectivity request for the target site has been triggered. In some embodiments, the fiber optic connectivity request is triggered by operation 202 of method 200 or operation 302 of method 300. The status "PREPARE OPTICAL FIBER APPLICATION" in column 404 indicates the status that follows after a fiber optic connectivity request for the target site has been triggered, e.g., the request is being prepared. In some embodiments, the fiber optic connectivity request is prepared by operation 204 of method 200 or operations 304, 306, 308, and 310 of method 300. When a fiber optic connectivity request for the target site is prepared, the information in columns 406, 408, and 410 is automatically imported. In some embodiments, the administrator can edit the information in columns 406, 408, and 410 in response to determining that the prepared request at operation 308 of method 300 has not been approved, or in response to determining that the prepared request at operation 312 of method 300 has not been completed.

[0069] The status "PREPARED" in column 402 indicates that the optical fiber connectivity request has been prepared. The status "APPROVE OPTICAL FIBER APPLICATION" in column 404 indicates the status that follows after the optical fiber connectivity request has been prepared, i.e., after the optical fiber connectivity application has been generated for approval. In some embodiments, the optical fiber connectivity application is generated by operation 206 of method 200 or operation 314 of method 300.

[0070] The status "APPROVED" in column 402 indicates that the optical fiber connectivity application has been approved. That is, in operation 208 of method 200 or operation 316 of method 300, the optical fiber connectivity application is submitted to a fiber optic provider and a response is received from the fiber optic provider. The response indicates whether the optical fiber connectivity application has been approved. The status "COMPLETE OPTICAL FIBER APPLICATION" in column 404 indicates the status that follows after receiving a response from the fiber optic provider to complete the optical fiber connectivity application. In some embodiments, an administrator can edit the information in columns 406, 408, and 410 in response to determining a negative response received from the fiber optic provider. For example, the group center information in column 410 can be edited in response to a negative response received in operations 326 and 310 of method 300. Additionally, the ID in column 412 is received from the optical fiber provider. In some embodiments, the ID in column 412 includes an application ID corresponding to the optical fiber connectivity application and a unique construction ID corresponding to the target site.

[0071] The status of "EXPECTED OPENING DATE" in column 402 indicates that an expected opening date has been set for the target site. In some embodiments, the expected opening date is set in operation 214 of method 200 or operation 328 of method 300. The status "ADJUST SCHEDULE" indicates the next status (that the expected opening date has been adjusted or is adjustable). In some embodiments, the adjustment of the expected opening date is performed in operation 330 of method 300. For example, the adjustment of the expected opening date is performed in operation 330, e.g., by submitting the adjusted date to a fiber optic carrier server. Additionally, the expected opening date is adjustable in operation 332 in response to the system task being canceled in operation 330. Column 414 of user interface 400 includes the expected opening date.

[0072] The status "SCHEDULE ADJUSTED" in column 402 indicates that the expected opening date has been adjusted. The status "SET CONSTRUCTION DATE" in column 404 indicates the status that follows after the construction date has been set. In some embodiments, the construction date is set in operation 214 of method 200 or operation 330 of method 300. In some embodiments, the construction date can be adjusted in operation 330 in response to the construction date being canceled or rescheduled in operation 336 of method 300. Column 416 of user interface 400 includes the construction date.

[0073] The status "CONFIRM CONSTRUCTION" in column 404 indicates that the construction date of the target site has been confirmed. In some embodiments, the construction date is confirmed at operation 214 of method 200 or operation 338 of method 300.

[0074] According to some embodiments, as shown in user interface 400 of FIG. 4, some information is required and some information is not required (optional) depending on the status of the optical fiber connectivity application. For "PREPARE OPTICAL FIBER APPLICATION" and "APPROVAL OPTICAL FIBER APPLICATION" in column 404, the information in columns 406 and 408 is required, and the information in columns 410, 412, 414, and 416 is not required. For "complete optical fiber application" in column 404, the information in column 410, i.e., group center information, has been changed from optional to required. For "ADJUST SCHEDULE," "SET CONSTRUCTION DATE," and "CONFIRM CONSTRUCTION" in column 404, the information in columns 412, 414, and 416 has been changed from optional to required.

[0075] In some embodiments, the user interface 400 allows an administrator to edit the information in columns 406, 408, 410, 412, 414, and 416 at different stages of a fiber optic connectivity application.

[0076] In some embodiments, user interface 400 includes additional information, which may be required or optional. In some embodiments, responsible party information is displayed in the user interface and is required. In some embodiments, after the opening date is set, a construction delay may occur for some reason. In such cases, information regarding the cause of the delay is displayed in the user interface, but this is optional.

[0077] 5 is a block diagram of a system 500 for managing optical fiber connectivity, according to some embodiments. The system 500 includes a hardware processor 502 and a non-transitory computer-readable storage medium 504 encoded with, i.e., storing, computer program code 506, i.e., a set of executable instructions. The computer-readable storage medium 504 also stores data 508 related to an optical fiber connectivity application. The processor 502 is electrically coupled to the computer-readable storage medium 504 via a bus 510. The processor 502 is also electrically coupled to an I / O interface 512 by the bus 510. A network interface 514 is also electrically connected to the processor 502 via the bus 510. The network interface 514 is connected to a network 516 such that the processor 502 and the computer-readable storage medium 504 can connect to external elements via the network 514. The processor 502 is configured to execute computer program code 506 encoded on the computer-readable storage medium 504 to enable the system 500 to perform some or all of the operations described in method 200 (FIG. 2) or method 300 (FIG. 3).

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

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

[0080] In some embodiments, storage medium 504 stores computer program code 506 configured to cause system 500 to perform some or all of the operations described in method 200 (FIG. 2) or method 300 (FIG. 3). In some embodiments, storage medium 504 also stores information for performing some or all of the operations described in method 200 (FIG. 2) or method 300 (FIG. 3), as well as information generated during the performance of some or all of the operations described in method 200 (FIG. 2) or method 300 (FIG. 3).

[0081] In some embodiments, storage medium 504 stores instructions 507 for interfacing with an external device. Instructions 507 enable processor 502 to generate and receive instructions readable by the external device to effectively perform some or all of the operations described in method 200 (FIG. 2) or method 300 (FIG. 3).

[0082] System 500 includes an I / O interface 512. I / O interface 512 is coupled to external circuitry. In some embodiments, I / O interface 512 includes a keyboard, keypad, mouse, trackball, trackpad, and / or cursor direction keys for communicating information and commands to processor 502.

[0083] The system 500 also includes a network interface 514 coupled to the processor 502. The network interface 514 enables the system 500 to communicate with a network 516 to which one or more other computer systems are connected. The network interface 514 may include a wireless network interface, such as BLUETOOTH, WIFI, WIMAX, GPRS, or WCDMA, or a wired network interface, such as ETHERNET, USB, or IEEE-1394. In some embodiments, the method 200 (FIG. 2) or the method 300 (FIG. 3) is implemented in more than one system 500, and information is exchanged between the different systems 500 via the network 516.

[0084] System 500 includes a display 518. Display 518 is electrically coupled to processor 502, storage medium 504, and I / O 512 via bus 510. Display 518 displays one or more user interfaces, including user interface 400 (FIG. 4).

[0085] One aspect of the present disclosure relates to a system. The system includes a non-transitory computer-readable medium configured to store instructions. The system further includes a processor coupled to the non-transitory computer-readable medium. The processor is configured to execute instructions for receiving optical fiber data related to a plurality of target areas for allocating optical fiber connectivity. The processor is further configured to execute instructions for preparing a plurality of optical fiber connectivity requests corresponding to the plurality of target areas. The processor is further configured to execute instructions for generating an optical fiber connectivity request based on the plurality of optical fiber connectivity requests. The processor is further configured to execute instructions for instructing a transmitter to transmit the optical fiber connectivity request to an optical fiber operator. The processor is further configured to execute instructions for receiving a response from the optical fiber operator, the response indicating whether the plurality of optical fiber connectivity requests are approved for optical fiber connectivity establishment. In some embodiments, the processor is further configured to execute instructions for updating the optical fiber connectivity request based on the data received from the optical fiber operator. In some embodiments, the processor is configured to execute instructions for determining whether the response from the optical fiber operator is a positive response that the plurality of optical fiber connectivity requests have been approved or a negative response that the plurality of optical fiber connectivity requests have not been approved. In some embodiments, in response to determining that the response is a negative response, the processor is configured to execute instructions for updating the optical fiber connectivity request to obtain an updated optical fiber connectivity request, and the processor is configured to execute instructions for instructing the transmitter to transmit the updated optical fiber connectivity request to the optical fiber operator. In some embodiments, in response to determining that the response is a positive response, the processor is configured to execute instructions for instructing the transmitter to transmit the positive response to the server to initiate the optical fiber connectivity establishment.In some embodiments, the processor is configured to execute instructions for selecting one or more group centers corresponding to the plurality of target sites for completing the plurality of optical fiber connectivity requests. In some embodiments, the data from the optical fiber operator includes a plurality of identifications respectively assigned to the plurality of optical fiber connectivity requests. In some embodiments, the processor is further configured to execute instructions for monitoring date information indicating a date of optical fiber connectivity construction or cost information indicating a cost of optical fiber connectivity construction. In some embodiments, in response to receiving a response from the optical fiber operator, the response including a response related to one of the optical fiber connectivity requests, the processor is configured to execute instructions for modifying one of the plurality of optical fiber connectivity requests in the optical fiber connectivity application. In some embodiments, the system further includes a display coupled to the non-transitory computer-readable medium and the processor, the processor further configured to execute instructions for displaying information indicative of a status of the optical fiber connectivity application on the display, the status of the optical fiber connectivity application including at least one of a triggered state, a ready state, or an approved state.

[0086] One aspect of the present disclosure relates to a method. The method includes receiving optical fiber data related to a plurality of target areas for allocating optical fiber connectivity. The method further includes preparing a plurality of optical fiber connectivity requests corresponding to the plurality of target areas. The method further includes generating an optical fiber connectivity request based on the plurality of optical fiber connectivity requests. The method further includes instructing a transmitter to transmit the optical fiber connectivity request to an optical fiber operator. The method includes receiving a response from the optical fiber operator, the response indicating whether the plurality of optical fiber connectivity requests are approved for optical fiber connectivity establishment. In some embodiments, the method further includes updating the optical fiber connectivity request based on the data received from the optical fiber operator. In some embodiments, the method further includes determining whether the response from the optical fiber operator is a positive response that the plurality of optical fiber connectivity requests are approved or a negative response that the plurality of optical fiber connectivity requests are not approved. In some embodiments, the method further includes, in response to determining that the response is a negative response, updating the optical fiber connectivity request to obtain an updated optical fiber connectivity request and instructing the transmitter to transmit the updated optical fiber connectivity request to the optical fiber operator. In some embodiments, the method further includes instructing the transmitter, in response to determining that the response is an affirmative response, to send an affirmative response to the server to initiate optical fiber connectivity establishment. In some embodiments, the method further includes selecting a plurality of group centers corresponding to a plurality of target sites to complete the plurality of optical fiber connectivity requests. In some embodiments, the data from the optical fiber operator includes a plurality of identification information respectively assigned to the plurality of optical fiber connectivity requests. In some embodiments, the method further includes monitoring date information indicating a date of optical fiber connectivity establishment or cost information indicating a cost of optical fiber connectivity establishment.In some embodiments, the method further includes modifying one of the plurality of optical fiber connectivity requests in the optical fiber connectivity application in response to receiving a response from the optical fiber operator, the response including a response related to one of the optical fiber connectivity requests.

[0087] One aspect of the present specification relates to a non-transitory computer-readable medium configured to store instructions that cause a processor executing the instructions to perform a method. The instructions cause the processor to receive optical fiber data related to a plurality of target areas for optical fiber connectivity. The instructions further cause the processor to prepare a plurality of optical fiber connectivity requests corresponding to the plurality of target areas for optical fiber connectivity. The instructions further cause the processor to generate an optical fiber connectivity application based on the plurality of optical fiber connectivity requests. The instructions further cause the processor to instruct a transmitter to transmit the optical fiber connectivity application to an optical fiber operator. The instructions further cause the processor to receive a response from the optical fiber operator indicating whether the plurality of optical fiber connectivity requests are approved for optical fiber connectivity establishment.

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

Claims

1. 1. A fiber optic connectivity management system comprising: a non-transitory computer-readable medium configured to store instructions; a processor coupled to the non-transitory computer-readable medium, the processor configured to execute the instructions, whereby: receiving optical fiber data relating to a plurality of areas of interest for optical fiber connectivity; preparing a plurality of optical fiber connectivity requests corresponding to the plurality of target areas for the optical fiber connectivity; generating an optical fiber application based on the plurality of optical fiber connectivity requests; instructing a transmitter to transmit the optical fiber application to an optical fiber operator; receiving a response from the optical fiber operator, the response indicating whether the plurality of optical fiber connectivity requests are approved for optical fiber connectivity establishment.

2. The processor: receiving data from the optical fiber operator; updating the optical fiber application based on the data received from the optical fiber operator; The optical fiber connectivity management system of claim 1 , configured to execute the instructions such that:

3. 2. The optical fiber connectivity management system of claim 1, wherein the processor is configured to execute the instructions such that the step of determining whether the response from the optical fiber operator is a positive response that the plurality of optical fiber connectivity requests has been approved or a negative response that the plurality of optical fiber connectivity requests has not been approved is performed.

4. In response to determining that the response is the negative response, the processor is configured to execute the instructions such that updating the optical fiber application to obtain an updated optical fiber application is performed; 4. The optical fiber connectivity management system of claim 3, wherein the processor is configured to execute the instructions to instruct the transmitter to transmit the updated optical fiber application to the optical fiber operator.

5. 4. The optical fiber connectivity management system of claim 3, wherein the processor is configured to execute the instructions such that, in response to determining that the response is the positive response, the processor executes the instructions to instruct the transmitter to send the positive response to a server to initiate the optical fiber connectivity establishment.

6. the data received from the optical fiber operator includes group center information regarding group centers connected to base stations via optical fibers; The processor: assigning the group center information to an east region and a west region; generating the fiber optic application for the east region or the west region; 3. The optical fiber connectivity management system of claim 2, configured to execute the instructions such that:

7. The optical fiber connectivity management system of claim 2 , wherein the data from the optical fiber operator includes an identifier associated with the optical fiber application.

8. 2. The optical fiber connectivity management system of claim 1, wherein the processor is configured to execute the instructions such that a step of monitoring date information indicating a date of the optical fiber connectivity construction or cost information indicating a cost of the optical fiber connectivity construction is performed.

9. 2. The optical fiber connectivity management system of claim 1, wherein the processor is configured to execute the instructions such that modifying the plurality of optical fiber connectivity requests in the optical fiber application occurs after the optical fiber application is approved.

10. a display coupled to the non-transitory computer-readable medium and the processor; 2. The optical fiber connectivity management system of claim 1, wherein the processor is configured to execute the instructions to cause the display to display information indicating a status of the optical fiber application, the status of the optical fiber application including at least one of a triggered state, a ready state, or an approved state.

11. 1. A method for managing optical fiber connectivity, comprising: receiving optical fiber data relating to a plurality of areas of interest for optical fiber connectivity; preparing a plurality of optical fiber connectivity requests corresponding to the plurality of target areas for the optical fiber connectivity; generating an optical fiber application based on the plurality of optical fiber connectivity requests; instructing a transmitter to transmit the optical fiber application to an optical fiber operator; receiving a response from the optical fiber operator, the response indicating whether the plurality of optical fiber connectivity requests are approved for optical fiber connectivity establishment.

12. receiving data from the optical fiber operator; updating the optical fiber application based on the data received from the optical fiber operator; The fiber optic connectivity management method of claim 11, further comprising:

13. 12. The optical fiber connectivity management method of claim 11, further comprising determining whether the response from the optical fiber operator is a positive acknowledgment that the plurality of optical fiber connectivity requests has been approved or a negative acknowledgment that the plurality of optical fiber connectivity requests has not been approved.

14. updating the optical fiber application to obtain an updated optical fiber application in response to determining that the response is the negative response; instructing the transmitter to transmit the updated optical fiber application to the optical fiber operator; The fiber optic connectivity management method of claim 13, further comprising:

15. 14. The optical fiber connectivity management method of claim 13, further comprising the step of instructing the transmitter, in response to determining that the response is the positive response, to send the positive response to a server to initiate the optical fiber connectivity establishment.

16. the data received from the optical fiber operator includes group center information regarding group centers connected to base stations via optical fibers; The method comprises: assigning the group center information to an east region and a west region; generating the fiber optic application for the east region or the west region; The fiber optic connectivity management method of claim 12, further comprising:

17. The method of claim 12 , wherein the data from the optical fiber operator includes an identifier associated with the optical fiber application.

18. The optical fiber connectivity management method according to claim 11, further comprising the step of monitoring date information indicating a date of the optical fiber connectivity construction or cost information indicating a cost of the optical fiber connectivity construction.

19. 12. The optical fiber connectivity management method of claim 11, wherein the plurality of optical fiber connectivity requirements in the optical fiber application are modifiable after the optical fiber application is approved.

20. 1. A non-transitory computer-readable medium configured to store instructions for causing a processor to execute the instructions to perform a method for managing optical fiber connectivity, the method comprising: receiving optical fiber data relating to a plurality of areas of interest for optical fiber connectivity; preparing a plurality of optical fiber connectivity requests corresponding to the plurality of target areas for the optical fiber connectivity; generating an optical fiber application based on the plurality of optical fiber connectivity requests; instructing a transmitter to transmit the optical fiber application to an optical fiber operator; and receiving a response from the optical fiber operator, the response indicating whether the plurality of optical fiber connectivity requests are approved for optical fiber connectivity establishment.

Images