Network planning tool support for 3d data
Claim Score by NHIP
Abstract
A telecommunication network planning method, system, and computer readable medium support accessing point cloud data and a corresponding image of a location. The point cloud data indicates positions of physical objects visible in the image. A network planning function may be performed. The network planning function may include modifying an outside plant asset object visible in the image, obtaining a metric of an outside plant asset object visible in the image, and adding a virtual outside plant asset to a location. The point cloud data may be associated with the image within an interface that depicts the image to facilitate visualization of the outside plant assets in the surrounding environment.

Term
9.5 yearsto projected expiry
Projected expiry 20 March 2036, counted from filing; an application has no term until it is granted.
- Priority and filed
- Published
- Today
- Projected expiry
20 claims: 3 independent, 17 dependent
- 1Broadest claimClaim Score 65, broad(NHIP)A network planning method, comprising:accessing an image of a location and point cloud data associated with the image, wherein the point cloud data includes a plurality of n-tuples, each n-tuple associated with a corresponding point in the image and each n-tuple indicating a three dimensional position of an object located at the point;and performing a network planning function selected from the group consisting of: identifying existing outside plant assets at the location;modifying an existing outside plant asset object visible in the image;obtaining a metric of an outside plant asset object visible in the image;and adding a virtual outside plant asset to the location.
- 13A network planning system, comprising:a processor;and computer readable memory including processor executable instructions that, when executed by the processor cause the processor to perform operations comprising: accessing an image of a location and point cloud data associated with the image, wherein the point cloud data includes a plurality of n-tuples, each n-tuple associated with a corresponding point in the image and each n-tuple indicating a three dimensional position of an object located at the point;and performing a network planning function selected from the group consisting of: identifying existing outside plant assets at the location;modifying an existing outside plant asset object visible in the image;obtaining a metric of an outside plant asset object visible in the image;and adding a virtual outside plant asset to the location.
- 18A computer readable memory device including processor executable program instructions that, when executed by a processor, cause the processor to perform operations, comprising:accessing an image of a location and point cloud data associated with the image, wherein the point cloud data includes a plurality of n-tuples, each n-tuple associated with a corresponding point in the image and each n-tuple indicating a three dimensional position of an object located at the point;and performing a network planning function selected from the group consisting of: identifying existing outside plant assets at the location;modifying an existing outside plant asset object visible in the image;obtaining a metric of an outside plant asset object visible in the image;and adding a virtual outside plant asset to the location.
Independent claims3
73 paragraphs in 3 sections, as filed
BACKGROUND
00011. Field of the Disclosure
0002Disclosed subject matter is in the field of telecommunication networks and more specifically, network planning tools for telecommunications networks.
00032. Description of the Related Art
0004In the field of telecommunications, network planning tools enable network administrators, engineers, technicians, and others to manage the placement and configuration of telecommunication assets, also sometimes referred to as outside plant assets (outside plant assets) or simply outside plant. Historically, network planning tools have provided a two dimensional (2D) context and leveraged 2D data such as geographic information service (GIS) data to map outside plant assets in a 2D domain, e.g., latitude and longitude or street address. Various features and applications have been developed to facilitate network planning within the historical 2D context. Constrained to two dimensions, however, conventional network planning tools are limited in their ability to provide a user with a meaningful “view” of existing and proposed outside plant assets in their actual environments.
BRIEF DESCRIPTION OF THE DRAWINGS
0005A network planning tool disclosed herein provides a planning environment in which three dimensional (3D) data objects defined by highly accurate 3D position coordinates are synchronized with a visually rich image of a location in conjunction with traditional network planning tool features and 3D extensions of those features for managing existing and proposed outside plant assets. In some embodiments, a 3D network planning tool may generate, obtain, or otherwise access highly accurate point cloud data, produced by light-based radar (LIDAR) or another suitable imaging technology, indicating 3D coordinates of points on the surfaces of objects at the location. This raw point cloud data may be post-processed to identify point cloud objects corresponding to distinct physical objects at the location. The point cloud objects are associated with a high resolution image of the location to facilitate a variety of network planning functions and features including, as examples, visualizing existing and proposed installations of various network elements, measuring and taking other metrics of outside plant assets at a remote location, and visualizing a secondary point cloud representing, for example, a small cell generated by an antenna or transmitter.
0006In addition to enabling network planners, administrators, engineers, field technicians, and others to visualize existing and proposed installations of outside plant assets in three dimensional space juxtaposed with an actual image of the adjacent environment, objects representing virtual and existing outside plant assets may be tagged and assigned attributes that facilitate group reports indicating the location of various existing and proposed outside plant assets.
0007<figref idref="DRAWINGS">FIG. 1</figref> illustrates elements of a network planning method;
0008<figref idref="DRAWINGS">FIG. 2</figref> illustrates elements of a network planning platform;
0009<figref idref="DRAWINGS">FIG. 3</figref> illustrates a user interface of a network planning tool depicting a map of a geographic area that includes a location selected by a user;
0010<figref idref="DRAWINGS">FIG. 4</figref> illustrates a streetview image of the location of <figref idref="DRAWINGS">FIG. 3</figref>;
0011<figref idref="DRAWINGS">FIG. 5</figref> illustrates a feature for indicating outside plant assets in the map of <figref idref="DRAWINGS">FIG. 3</figref>;
0012<figref idref="DRAWINGS">FIG. 6</figref> illustrates a feature for displaying attributes of a selected outside plant asset;
0013<figref idref="DRAWINGS">FIG. 7</figref> illustrates a feature for interacting with point cloud data associated with an image of the location;
0014<figref idref="DRAWINGS">FIG. 8</figref> illustrates a feature for adding an outside plant asset to the location depicted in the image;
0015<figref idref="DRAWINGS">FIG. 9</figref> illustrates a feature for adding a metrocell to a selected location;
0016<figref idref="DRAWINGS">FIG. 10</figref> illustrates features for indicating a proposed metrocell, a corresponding secondary point cloud indicating coverage provided by the metrocell, and attributes of the metrocell;
0017<figref idref="DRAWINGS">FIG. 11</figref> illustrates a feature for indicating and displaying a map for a rural location;
0018<figref idref="DRAWINGS">FIG. 12</figref> illustrates an image of the rural location including an outside plant asset in the form of a utility pole;
0019<figref idref="DRAWINGS">FIG. 13</figref> illustrates a feature for interacting with a point cloud corresponding to the image of the rural location;
0020<figref idref="DRAWINGS">FIG. 14</figref> illustrates a feature for using the point cloud data and the corresponding image to measure a dimension of the outside plant asset;
0021<figref idref="DRAWINGS">FIG. 15</figref> illustrates a feature for using the point cloud data and the corresponding image to measure a second dimension of the outside plant asset;
0022<figref idref="DRAWINGS">FIG. 16</figref> illustrates a feature for using the point cloud data and the corresponding image to measure an angle of orientation or slope of a cable;
0023<figref idref="DRAWINGS">FIG. 17</figref> illustrates a feature for adding an antenna and corresponding point cloud data to an image of a location; and
0024<figref idref="DRAWINGS">FIG. 18</figref> illustrates a feature for adding a virtual asset and a corresponding point cloud to an image of an existing location.
DESCRIPTION OF EMBODIMENTS
0025Embodiments of subject matter disclosed herein include embodiments directed to a network planning method that includes accessing an image of a location and point cloud data associated with the image. The point cloud data may include a plurality of n-tuples, each n-tuple associated with a corresponding point in the image and each n-tuple indicating a three dimensional position of an object located at the point. The three dimensional position may be indicated in a rectangular coordinate system, including X, Y, and Z coordinates, or in another coordinate system such as a spherical coordinate system in which points are identified with two angles and a displacement, or in any other suitable coordinate system. The method may further include performing a network planning function. Network planning functions may include, as non-limiting examples, identifying and depicting existing outside plant assets at the location, modifying an existing outside plant asset object visible in the image, obtaining a metric of an outside plant asset object visible in the image, and adding a virtual outside plant asset to the location. The point cloud data may include post-processed point cloud data including a plurality of point cloud objects, each point cloud object representing a physical object depicted in the image.
0026Accessing the image of the location may include selecting a streetview icon from a map interface or another type of 2D representation of the location or a geographic region that includes the location. The streetview user interface may be provided as a pop up window overlying the map interface. The map interface may include functionality to selectively display existing outside plant assets located within the application geographic region. The method may include assigning one or more attributes to one or more outside plant assets included in the user interface and functionality for generating asset reports, which may be filtered in accordance with one or more of the assigned attributes. In embodiments applicable to telecommunications networks, outside plant assets may include, as non-limiting examples: metrocell transmitters, utility poles, communication cables, switch boxes, and so forth.
0027In some embodiments, existing outside plant assets of a first type and virtual assets of the first type may be differentiated by color or another visible characteristic. Similarly, two different types of assets may be indicated by two different types of icons, colors, or other suitable characteristics.
0028In some cases, an outside plant asset may be associated with a primary point cloud, representing the asset itself, and a secondary point cloud indicative of a characteristic of the outside plant asset. In the case of a metrocell transmitter, as an example, the transmitter may be associated with a primary point cloud indicating the location of the transmitter and a secondary point cloud indicative of coverage provided by the metrocell transmitter.
0029The point cloud data for an entity's outside plant assets may be stored and subsequently accessed for application to a second image of the location. The second image of the location may have been created after the point cloud data. Following a natural disaster, for example, an image of the location may be employed in conjunction with the archived point cloud data to perform preliminary assessment of damages. In addition, the point cloud data may be suitable for use in the event that an image of a location is rendered in a format that differs from the original image of the location.
0030In some embodiments, obtaining a metric of an outside plant asset includes measuring a linear dimension of an outside plant asset, measuring an area of a surface of an outside plant asset, measuring an orientation angle of an outside plant asset, and the like.
0031Other embodiments may include computers and other system, which may include image capture and image processing devices including lasers, cameras, and the like to acquire or access raw point cloud data and one or more images for a location, and hardware and software to perform post processing of the raw point cloud data to identify objects in the image and associate the objects with corresponding point cloud data objects.
0032Referring to <figref idref="DRAWINGS">FIG. 1</figref>, selected elements of a network planning method <b>100</b> are illustrated. The network planning method illustrated in <figref idref="DRAWINGS">FIG. 1</figref> includes acquiring (block <b>102</b>) raw point cloud data and at least one image of a geographical location. In at least one embodiment, raw point cloud data includes a set of 3D space coordinates indicative of or otherwise associated with physical objects present at the location. The point cloud data may be generated using LIDAR or another suitable 3D imaging technology. In some embodiments, the point cloud data includes highly accurate X, Y, and Z coordinates corresponding to points on the surfaces of the applicable objects. In the case of LIDAR generated point cloud data, each point cloud data point may be assigned by determining the distance between the source of the laser and a corresponding point on the surface of an object, which can be determined based on the time required to receive a reflected signal back from the surface point. Given the position of the laser source and the direction of the laser, the raw point cloud data points can be resolved in three dimensions based on the calculated distance.
0033The point cloud data acquired in (block <b>102</b>) may be referred to as raw point cloud data because the data points are not associated with any physical particular object. Instead, the raw point cloud data may include, as an example, a data point representing a point on the surface of a first structure adjacent to a data point corresponding to a point on the surface of a second structure. In the embodiment of method <b>100</b> illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, the raw point cloud data is post processed (block <b>104</b>) to identify individual physical objects present at the location. Post processing of point cloud data may be performed according to any of a variety of point cloud processing algorithms beyond the scope of this disclosure. See, e.g., Euclideon, a 3D graphics engine which makes use of a point cloud search algorithm to render images, MeshLab, an open source tool for managing point clouds and converting them into 3D triangular meshes, CloudCompare, an open source tool for viewing, editing and processing high density 3D point clouds, PCL (Point Cloud Library), a comprehensive BSD open source library for n-D Point Clouds and 3D geometry processing, and TAMU 3D Point Cloud Editor, a GUI application developed at Texas A&M University for interactively editing and visualizing point clouds stored in various file formats.
0034In at least one embodiment, post processing of raw point cloud data organizes the data points into groups where each group represents an individual object. Data points may be grouped based on proximity and other factors. The set of data points corresponding to a single physical object may be referred to herein as point cloud object data. Point cloud object data indicates the shape and 3D position of the surface of the applicable object.
0035In at least one embodiment, post processing of the raw point cloud data generates point cloud object data corresponding to each of the distinct physical objects in the image. In some embodiments, the acquisition of raw point cloud data in block <b>102</b> and the post processing of raw point cloud data in block <b>104</b> may each be performed by an entity that is different than an entity that uses the post processed data in conjunction with a specific application.
0036The method <b>100</b> illustrated in <figref idref="DRAWINGS">FIG. 1</figref> includes accessing (block <b>106</b>) point cloud object data and a corresponding image of a location. The point cloud object data includes 3D position data corresponding to a plurality of physical objects visible in the image. The image may include outdoor plant assets of a telecommunication provider or network, and outdoor plant assets of a competitor telecommunication service provider, as well as non-assets, i.e., physical objects not part of a telecommunications network.
0037In some embodiments, attributes may be assigned to individual objects associated with each point cloud object. Attributes may be used to differentiate the assets of a telecommunications service provider from like or similar assets of a competitor and from non-asset objects including, as examples, buildings, streets, vehicles, and so forth. The point cloud data corresponding to a service provider's assets may be extracted from and recorded or otherwise preserved apart from the remainder of the data. In at least one such embodiment, the service provider may then re-use the point cloud data for its assets apart from the original image and the set of point cloud objects. If, for example, a subsequent image of the location is generated, the service provider may apply the point cloud object data for its assets to the new image. If the new image differs substantially from the original image such as following a natural disaster, an initial assessment of the impact to the provider's assets may be obtained.
0038The network planning method <b>100</b> illustrated in <figref idref="DRAWINGS">FIG. 1</figref> includes generating (block <b>108</b>) a user interface that includes the image of the location and is associated with the point cloud object data corresponding to objects depicted in the image. As an example of the association between the image and the point cloud data objects, the user interface may display the image and, when a cursor is moved over the image, the cursor may indicate the presence of point cloud data underlying the image or with a specific object visible in the image. For example, the cursor could, in some embodiments, depict a cloud-like icon that approximately corresponds in size and shape to the applicable point cloud data object. In other embodiments, the cursor may simply change in appearance to indicate to the user that point cloud data is associated with the image or a portion of the image over which the cursor is currently located. In at least one embodiment, the user interface referenced in block <b>108</b> is accessed as a value added feature or extension of an existing or legacy network planning tool to provide support for 3D extensions of the feature.
0039In at least one embodiment, a network planning tool generates a 2D interface depicting a street map or another other suitable two dimensional representation of a portion of a location. The 2D interface may include, emphasize, or otherwise depict existing outdoor plant assets located within the region encompassed by the map. In at least some embodiments, the 2D interface may include selectable elements enabling the user to show or hide various types of assets.
0040The 2D interface may include a tab, menu item, icon or another element for accessing 3D features. The user who wishes to access 3D features may click on the 3D extension element and, in at least one embodiment, the network planning tool will display an image of the applicable location and identify or access point cloud object data corresponding to the location depicted in the image. The 3D interface may appear as a pop-up window or otherwise external to or apart from the traditional network planning tool or, in other embodiments, the 3D user interface may appear as a window in the network planning tool, either replacing or in addition to the original window. Although block <b>108</b> is illustrated in <figref idref="DRAWINGS">FIG. 1</figref> as an operation of method <b>100</b>, other embodiments may omit the actual generation of the user interface and, instead, provide the user interface and the associated point cloud object data to an external network planning application.
0041The network planning method <b>100</b> illustrated in <figref idref="DRAWINGS">FIG. 1</figref> further includes performing, (block <b>110</b>) a network planning function for either an existing outside plant asset or a virtual outside plant asset. Virtual outside plant assets may represent proposed or future assets being considered for inclusion within the network at the indicated location. The existing outside plant assets may include outside plant assets of the service provider as well as outside plant assets of a competitor service provider.
0042In at least one embodiment, the network planning functions that may be performed in conjunction with the 3D interface include a function for modifying (block <b>120</b>) an existing outside plant asset object that is visible in the image. In at least one embodiment, modifying an existing outside plant asset object may include modifying a position or location of an existing outside plant asset, modifying a configuration of an existing outside plant asset, or supplementing an existing outside plant asset with point cloud data or 3D features. As an example of supplementing an asset with point cloud data, the network planning tool may have access to a legacy database of outside plant assets generally represented in two dimensions. In these embodiments, supplementing an existing outside plant asset may include generating more accurate <b>2</b>D data as well as adding a third dimension to the existing outside plant asset. For example, a cellular telephone tower or other type of antenna or transmitter may be indicated in a 2D network planning database with X and Y coordinates. In these embodiments, the antenna may be visible in an image of the applicable location and the point cloud data generated in conjunction with the image may provide, in addition to the X and Y coordinates of the antenna, a Z coordinate indicating the elevation or height of the antenna.
0043The network planning functions illustrated in <figref idref="DRAWINGS">FIG. 1</figref> also include a function for measuring or otherwise obtaining (block <b>123</b>) a metric or other data pertaining to an existing or virtual outside plant asset. As an example, in at least one embodiment, the network planning tool may present an image that includes a piece of existing outside plant asset such as a utility pole. The network planning tool may include conventional control elements for zooming, panning, and selecting portions of an image. In these embodiments, the network planning tool may permit the operator to zoom into an existing outside plant asset for purposes of obtaining one or more measurements or metrics associated with the asset. In the case of a utility pole, for example, at least one embodiment of the network planning tool includes a measurement feature that enables a user to measure one or more dimensions of an outside plant asset depicted in the image of a location. The user interface may include a control element such as, for example, a selectable button depicting an image of a ruler or other measurement device as a means for invoking the measurement feature. After a user zooms, pans, or otherwise trains or focuses the 3D interface on a desired object, the user may select the measurement icon or control element to invoke the measurement feature. In at least some embodiments, the cursor may change in appearance to acknowledge that the network planning tool has transitioned to a feature measurement mode. The operator of the network planning tool may then click on the measurement tool and, using a mouse or other suitable input device, trace the asset of interest. As the user moves the cursor over the image and then over the particular outdoor plant asset, the network planning tool may identify point cloud data corresponding to the beginning point and ending point of the trace made by the user over the applicable object. From the point cloud data, the network planning tool may calculate the distance between the end point and the beginning point. Using this feature, a user may measure the utility pole or characteristics of the utility pole from a remote location, thereby beneficially saving the time and energy required to send a field representative to the location of the utility pole, especially if the utility pole is located in a rural or remote area. With this feature, for example, the network planning tool may enable a user to measure the length of a utility pole or the distance between two assets attached to a utility pole. For example, the user may invoke the network planning tool to determine a distance between a cable box and a transformer attached to the utility pole.
0044In still another example, the measurement tool may support a feature in which an orientation or angle of an outdoor plant asset is determined. For example, using substantially the same procedure used to measure dimensions of an outdoor plant asset, a user may trace a line or other shape between two points of an outdoor plant asset and then invoke an angle or orientation feature of the measurement interface to determine the orientation, angle, or slope of an existing asset. For example, this feature might be employed to determine the slope of a telephone wire or another suitable wire or cable extending from a utility pole. Although the measurement tool is described herein using a utility pole as the asset, the tool is equally applicable to other types of assets.
0045In addition to modifying existing outside plant assets and measuring or obtaining metrics pertaining to an existing outside plant asset, the network planning functions represented by reference <b>110</b> include adding (block <b>126</b>) a virtual outside plant asset to a location. The network planning tool may have access to one or more previously designed and supported 3D objects that may be used to generate planning scenarios by adding proposed elements to a location and then visually reviewing an image of the location revised to include the proposed asset. In at least one embodiment, the types of outside plant assets available to a user include a library of pre-existing asset types and may further include user-defined asset types.
0046Although not strictly required, the embodiment of method <b>100</b> illustrated in <figref idref="DRAWINGS">FIG. 1</figref> includes creating (block <b>128</b>) a virtual outside plant asset type. In an embodiment supporting a virtual asset creation feature, a user may generate a virtual outside plant asset type by effectively copying the point cloud object data corresponding to point cloud object data for an existing asset. For example, a virtual utility pole type may be created, if one were not available in a virtual object library, by copying point cloud object data associated with an existing utility pole. The point cloud object data for a virtual asset type may modify the data copied from the existing outside plant asset. For example, the point cloud object data for an existing utility pole may include data identifying the location as well as the shape of the utility pole. However, when creating a virtual asset type, it is desirable to remove any data corresponding to a particular location, thereby leaving behind point cloud object data identifying just the shape of the outside plant asset. In this manner, new instances of virtual outside plant assets may be provided to a location and the network planning tool may simply translate the point cloud object data for the virtual asset type in accordance with the position and orientation selected by the user.
0047In at least one embodiment, outside planning assets are represented by point cloud object data supplemented with attribute data that may include, as non-limiting examples, a tag or field to indicate whether the asset is existing or proposed, a tag or field to indicate an owner or operator of the asset, and one or more configuration settings that may influence the performance of a proposed or existing asset. The types of assets that may be employed within a network planning tool may include conventional network planning assets such as fiber cables, local network service (LNS) cables, VRADs, LUs, and other suitable telecommunication network assets.
0048In at least one embodiment, a virtual outside plant asset associated with point cloud object data may generate or otherwise be associated with a secondary point cloud representing coverage or other another attribute associated with the asset. In at least one embodiment, a virtual outside plant asset includes a transmitter or antenna configured to provide a metrocell, small cell, or another suitable hotspot. In these embodiments, the outside plant asset may include point cloud object data representing the physical structure of the outside plant asset as well as a coverage point cloud indicating the extent of the hotspot or other network characteristic generated by the virtual outside plant asset. In at least one such environment, the virtual outside plant asset may further include configuration settings that influence the behavior or structure of the secondary point cloud. In the case of a metrocell antenna, the outside plant asset may include a configuration setting for an orientation of an antenna or another feature that may influence the resulting secondary point cloud. In at least one embodiment, the network planning tool may generate a visual representation of the secondary point cloud generated by the corresponding outside plant asset to enable the user to visualize, not only the placement of the antenna, but also the resulting coverage. The secondary point cloud may be determined and/or influenced by factors such as the location, orientation, and composition of adjacent structures. The embodiment of method <b>100</b> illustrated in <figref idref="DRAWINGS">FIG. 1</figref> includes a refresh operation (block <b>134</b>) that is performed after each network planning function is performed.
0049Referring now to <figref idref="DRAWINGS">FIG. 2</figref>, a network planning platform <b>200</b> suitable for supporting point cloud data and performing the method <b>100</b> illustrated in <figref idref="DRAWINGS">FIG. 1</figref> is disclosed. The network planning platform <b>200</b> depicted in <figref idref="DRAWINGS">FIG. 2</figref> includes an acquisition device <b>210</b> that includes a camera <b>220</b> and a laser <b>230</b> coupled to an acquisition computer <b>240</b>. Acquisition device <b>210</b> may be stationary or, in other embodiments, affixed to a movable platform such as an automobile or other motor vehicle. Camera <b>220</b> and laser <b>230</b> generate data corresponding to a location <b>201</b>. In at least one embodiment, camera <b>220</b> takes one or more pictures of location <b>201</b> to create location image <b>225</b>. Location image <b>225</b> comprises data corresponding to one or more images of location <b>201</b>. Laser <b>230</b> is configured to scan the location <b>201</b> and to generate raw point cloud data <b>235</b> by any suitable mechanism including the mechanisms described with respect to <figref idref="DRAWINGS">FIG. 1</figref>. Acquisition computer <b>240</b> is configured to operate camera <b>220</b> and laser <b>230</b> in synchronicity such that the raw point cloud data <b>235</b> generated by laser <b>230</b> can be mapped or otherwise associated with the location image <b>225</b> generated by camera <b>220</b>. Acquisition computer <b>240</b> may also control operation of camera <b>220</b>, laser <b>230</b>, or both.
0050In at least one embodiment, raw point cloud data <b>235</b> includes a large number of data points where each data point includes, at least, 3D coordinate information indicating, in 3D space, the location of a point of location <b>201</b>. Acquisition computer <b>240</b> may operate in conjunction with laser <b>230</b> to assign 3D position data to each pulse of laser <b>230</b>. Generally, the 3D position data may be determined based upon the location of the laser, the orientation of the laser, and the distance traveled by the laser and back to the laser after reflecting off of an object within location <b>201</b>.
0051The raw point cloud data <b>235</b> may be associated with location image <b>225</b> by assigning or otherwise generating a relationship between each piece of raw point cloud data and a pixel or other sub element of location image <b>225</b>. Illustrating the association between location image <b>225</b> and raw point cloud data <b>235</b>, at least one embodiment may associate each piece of location information included in the raw point cloud data <b>235</b> with a pixel or other sub element of location image <b>225</b>. More generally however, the association between location image <b>225</b> and raw point cloud data <b>235</b> assigns X and Y image coordinates, corresponding to specific XY coordinates within the two dimensional image <b>225</b>, to each piece of raw point cloud data <b>235</b> corresponding to location <b>201</b>.
0052Network planning platform <b>200</b> includes post processing computer <b>250</b> that accesses or otherwise retrieves location image <b>225</b> and raw point cloud data <b>235</b>. Post processing computer <b>250</b> is configured with hardware, software, or both to identify distinct physical objects depicted in location image <b>225</b>. Post processing computer <b>250</b> may identify objects depicted in location image <b>225</b> and represented in raw point cloud data <b>235</b> by a proximity-based algorithm in which two points that are located in close proximity to one another according to their XYZ data are assumed to be of the same physical object. Post processing of 3D imaging information is known to those of skill in the field of three-dimensional graphics and three-dimensional video and is beyond the scope of this disclosure.
0053In the embodiment of platform <b>200</b> illustrated in <figref idref="DRAWINGS">FIG. 2</figref>, post processing computer <b>250</b> generates network planning data <b>260</b> including location image <b>262</b> and point cloud object data <b>264</b>. <figref idref="DRAWINGS">FIG. 2</figref> illustrates and emphasizes that, in the depicted embodiments, location image <b>262</b> is associated with point cloud object data <b>264</b>. Point cloud object data <b>264</b> represents the data generated by post processing computer <b>250</b> based on raw point cloud data <b>235</b>.
0054Network planning platform <b>200</b> as illustrated in <figref idref="DRAWINGS">FIG. 2</figref> further includes a network planning tool <b>280</b> that includes support for 3D representations of physical objects such as the physical objects depicted in an image of a location of interest. The network planning tool <b>280</b> may be implemented as a computer system that includes a processor, memory, a display device and I/Odevices such as keyboards, point devices, and the like for receiving user input. The memory may be implemented with volatile memory devices, non-volatile memory devices, or both. Processor executable program instructions may be stored in the memory of network planning tool <b>280</b>. When executed by the processor, the program instructions may cause the processor to perform any of the network planning methods described herein. The network planning tool <b>280</b> depicted in <figref idref="DRAWINGS">FIG. 2</figref> may have access to a network planning database <b>270</b> that includes a library <b>272</b> of legacy maps and network planning tools, typically conveying or supporting two dimensional data as well as a 3D outside planning asset library <b>284</b>, which may include point cloud data for one or more virtual object types.
0055Referring now to <figref idref="DRAWINGS">FIG. 3</figref> through <figref idref="DRAWINGS">FIG. 17</figref>, exemplary user interfaces are illustrated to emphasize functionality of a network planning tool that includes three-dimensional support. The user interfaces illustrated in <figref idref="DRAWINGS">FIG. 3</figref> through <figref idref="DRAWINGS">FIG. 17</figref> emphasize the use of a 3D tool in conjunction with a traditional network planning application that employs, for example, a geographic information systems (GIS). Although the various features illustrated herein emphasize 3D support for and extensions of a GIS based planning tool, the 3D features illustrated herein may be implemented in a standalone application.
0056Referring to <figref idref="DRAWINGS">FIG. 3</figref>, user interface <b>300</b> represents one type of user interface a network planner may interact with during a network planning session. User interface <b>300</b> may include features similar to features included in conventional two dimensional GIS mapping tools that will be familiar to those of skill in the art. As depicted in <figref idref="DRAWINGS">FIG. 3</figref>, user interface <b>300</b> includes a GIS map <b>301</b> and emphasizes a feature for finding or locating a particular address. As illustrated in <figref idref="DRAWINGS">FIG. 3</figref>, a find address feature displays a pop-up window <b>302</b> and includes a window <b>303</b> in which a user may enter a desired address. The user interface <b>300</b> illustrated in <figref idref="DRAWINGS">FIG. 3</figref> displays a pushpin <b>305</b> on GIS map <b>301</b> to indicate a location <b>304</b> corresponding to the address entered by the user in window <b>303</b>.
0057The GIS map <b>301</b> of user interface <b>300</b> includes an additional features icon <b>308</b> for overlaying or otherwise displaying additional information including, as a non-limiting example, information indicating the type and/or position of various types of outside plant assets of a service provider.
0058The user interface <b>300</b> illustrated in <figref idref="DRAWINGS">FIG. 3</figref> includes a toolbar <b>309</b> containing icons for various tools accessible from user interface <b>300</b>. As illustrated in <figref idref="DRAWINGS">FIG. 3</figref>, toolbar <b>309</b> includes, in addition to other elements, a streetview icon <b>310</b> that provides support for 3D features and extensions. As depicted in <figref idref="DRAWINGS">FIG. 3</figref>, a user has entered an address in window <b>303</b> and the planning tool, which may include features of or access to a GIS application, displays GIS map <b>301</b> or another 2D representation of an area that includes the address entered by the user.
0059<figref idref="DRAWINGS">FIG. 4</figref> illustrates the selection of streetview icon <b>310</b> from the user interface <b>300</b> of <figref idref="DRAWINGS">FIG. 3</figref>. As depicted in <figref idref="DRAWINGS">FIG. 4</figref>, user selection of streetview icon <b>310</b> generates a pop-up window <b>320</b> that includes an image <b>340</b> of location <b>304</b> (<figref idref="DRAWINGS">FIG. 3</figref>). In some embodiments, an azimuth (not visible in the figures) or another suitable indicator of direction is appended to the pushpin <b>340</b> in GIS map <b>301</b> when pop up window <b>320</b> is displayed. In these embodiments, the azimuth indicates, on GIS map <b>301</b>, the direction of view corresponding to the image <b>340</b>. In at least one embodiment, pop up window <b>320</b> includes, in addition to the image <b>340</b> of location <b>304</b>, point cloud object data associated with image <b>340</b>. Although the point cloud data underlying image <b>340</b> is not itself visible in pop-up window <b>320</b>, some embodiments may indicate the presence of point cloud data and the association between the point cloud data and the image <b>340</b> by altering the appearance of a cursor when the cursor is positioned over an image <b>340</b> or a portion of image <b>340</b> with which point cloud data is associated. The pop-up window <b>320</b> of <figref idref="DRAWINGS">FIG. 4</figref> further includes various functionality controls <b>344</b> for performing one or more point cloud supported network planning functions. <figref idref="DRAWINGS">FIG. 4</figref> also illustrates a directional indicator <b>327</b> overlaying or incorporated into image <b>340</b>. The directional indicator <b>327</b> may represent an optional or user selectable feature that is generated within three-dimensional support pop-up window <b>320</b> when applicable.
0060<figref idref="DRAWINGS">FIG. 5</figref> depicts user interface <b>300</b> after assertion of additional information icon <b>308</b>. In the embodiment illustrated in <figref idref="DRAWINGS">FIG. 5</figref>, assertion of additional information icon <b>308</b> generates an additional information drop-down list <b>350</b> including a plurality of selectable elements. The elements selected for inclusion in the user interface <b>300</b> include a target metrocell, AT&T fibers, and an LNS cable. With the selection of each of these types of assets, user interface <b>300</b> incorporates visibly detectable elements representing the locations of corresponding types of outdoor plant assets. The AT&T fibers selected in drop-down list <b>350</b>, for example, may be illustrated as colored lines <b>352</b> of a first color while the LNS cables selected in drop down list <b>350</b> are illustrated as colored lines <b>353</b> of a second color in GIS map <b>301</b> of user interface <b>300</b>.
0061The three-dimensional pop-up window <b>320</b> illustrated in <figref idref="DRAWINGS">FIG. 5</figref> includes an identify icon <b>354</b> that enables the user to obtain information regarding various outdoor plant assets represented in the GIS map <b>300</b> of <figref idref="DRAWINGS">FIG. 5</figref>. Referring to <figref idref="DRAWINGS">FIG. 6</figref>, assertion of identify icon <b>354</b> generates an identification window <b>360</b>. The illustrated identification window <b>360</b> displays various attributes <b>362</b> and corresponding values <b>364</b> of an outside plant asset displayed in GIS map <b>301</b> and selected by the user. The identification window illustrated in <figref idref="DRAWINGS">FIG. 6</figref> is representative of an identification window suitable for telecommunication fiber assets, but it will be readily appreciated that each type of outside plant asset may have its own corresponding information window <b>360</b>.
0062Referring now to <figref idref="DRAWINGS">FIG. 7</figref>, an add new feature function corresponding to an add new feature icon <b>374</b> in functionality controls <b>344</b> within three dimensional support pop-up window <b>320</b> is shown. The user interface <b>300</b> illustrated in <figref idref="DRAWINGS">FIG. 7</figref> includes a point cloud data icon <b>376</b>. In at least one embodiment, point cloud data icon <b>376</b> appears whenever the cursor is located overlying an image <b>340</b> with which point cloud data has been associated. In any such embodiments, the presence of a point cloud icon <b>376</b> conveys to the user that the location depicted in image <b>340</b> has been scanned with a laser and that the resulting point cloud data has been processed and associated with the image <b>340</b> of location <b>304</b>. In the user interface <b>300</b> illustrated in <figref idref="DRAWINGS">FIG. 7</figref>, an add new feature window <b>372</b> pops up in response to assertion of add new feature icon <b>374</b>. The add new feature window <b>372</b> includes a drop down list <b>373</b> listing at least a portion of the types of assets a user may add.
0063In <figref idref="DRAWINGS">FIG. 8</figref>, the drop-down list <b>373</b> associated with add new feature window <b>372</b> is expanded to indicate a number of features or assets that may be added. The user may select any of the elements listed in drop-down list <b>373</b>. In <figref idref="DRAWINGS">FIG. 9</figref>, the user has selected the target metrocell item <b>375</b> from drop down list <b>373</b> as the feature to be added. <figref idref="DRAWINGS">FIG. 9</figref> also illustrates the user repositioning the point cloud icon <b>376</b> to a position within pop-up window <b>320</b> where the user would like to add the identified asset, which is a metrocell in the illustrated example.
0064Referring now to <figref idref="DRAWINGS">FIG. 10</figref>, user interface <b>300</b> as shown illustrates the addition of a proposed metrocell asset, denoted by metrocell icon <b>412</b>, at location <b>413</b> in pop window <b>320</b>. The user may select the newly added metrocell icon <b>412</b> and view or edit identification information associated with the proposed asset by selecting identification icon <b>354</b> to display identification window <b>410</b>. Identification window <b>410</b> displays attributes <b>362</b> and their corresponding values <b>364</b>, if any. The user enters additional identification information into the identification window <b>410</b>. The user may enter information including, as one non-limiting example illustrated in <figref idref="DRAWINGS">FIG. 10</figref>, information pertaining to an estimated completion data attribute <b>414</b>. This feature emphasizes the ability for a user to indicate to others that the asset is not currently online while at the same time indicating an expected date at which time the asset will hopefully become usable.
0065<figref idref="DRAWINGS">FIG. 10</figref> illustrates a secondary point cloud <b>415</b> associated with metrocell icon <b>412</b>. The secondary point cloud <b>415</b> for a metrocell asset indicates, in at least one embodiment, a projected region of wireless coverage provided by the applicable metrocell <b>412</b>. The secondary point cloud may be determined based on one or more attributes of metrocell <b>412</b> as well as the presence and attributes of objects located in proximity to metrocell <b>412</b>. Metrocell <b>412</b> may include one or more attributes that impact the location and/or size of secondary point cloud <b>415</b>. For example, metrocell <b>412</b> may include an antenna orientation attribute and a transmission power attribute that impact the location and size of secondary point cloud <b>415</b>. In some embodiments, secondary point cloud <b>415</b> is tightly bound to metrocell <b>412</b> such that, for example, a representation of metrocell <b>412</b> inherently depicts the secondary point cloud <b>415</b>.
0066In <figref idref="DRAWINGS">FIG. 11</figref>, user interface <b>300</b> has been trained to a different address indicated in window <b>303</b> of pop-up window <b>302</b> as described previously. Whereas the address indicated by the user in <figref idref="DRAWINGS">FIG. 3</figref> was a street address corresponding to a city or other developed area, the location identified in window <b>303</b> of pop-up window <b>302</b> in <figref idref="DRAWINGS">FIG. 11</figref> corresponds to a rural setting where, for example, there may be no conventional street and number address. In this example, the location may be indicated within window <b>303</b> by GPS coordinates <b>422</b> and GIS map <b>301</b> represents a map of a geographic area at the center of which is a pushpin <b>305</b> indicating a location <b>304</b>.
0067<figref idref="DRAWINGS">FIG. 12</figref> illustrates pop-up window <b>320</b> depicting an image <b>340</b> of location <b>304</b> (see <figref idref="DRAWINGS">FIG. 11</figref>) corresponding to the GPS coordinates <b>422</b> entered in window <b>303</b> of pop-up window <b>302</b> of <figref idref="DRAWINGS">FIG. 11</figref>. As can be seen in <figref idref="DRAWINGS">FIG. 12</figref>, the location depicted in pop-up window <b>320</b> appears to be located in a remote region and includes an outdoor plant asset in the form of a utility pole <b>425</b>.
0068In <figref idref="DRAWINGS">FIG. 13</figref>, the user has selected a measurement feature icon <b>431</b> from functionality controls <b>344</b>. User selection of measurement feature icon <b>431</b> generates a measurement pop up window and enables the user to trace a measurement line overlying image <b>340</b> and, more specifically, overlying the portion of the asset to be measured. In <figref idref="DRAWINGS">FIG. 14</figref>, a user has generated measurement line <b>437</b> tracing the length of utility pole <b>425</b> while the measurement pop up window <b>433</b> reports the length of the measurement line <b>437</b>. <figref idref="DRAWINGS">FIG. 14</figref> thus illustrates the use of accurate remote measurement capabilities made possible when point cloud data is associated with a corresponding image of an outside plant asset. In at least one embodiment, the measurement information is generated based upon the point cloud data underlying the image <b>340</b>. For example, the measurement tool may identify the XY image coordinates of the endpoints of line <b>437</b>, access the point cloud data associated with image <b>340</b> to determine 3D coordinates corresponding to the endpoints of line <b>437</b>, and calculate a straight line distance between the two points. Because the point cloud data is based on highly accurate laser scanning methods in at least some embodiments, the measurement generated based off of the point cloud data is or may be accurate to within a few centimeters.
0069<figref idref="DRAWINGS">FIG. 15</figref> depicts a use of the measurement feature of <figref idref="DRAWINGS">FIG. 14</figref> to measure the distance between two outside plant assets attached to utility pole <b>425</b>, namely a transformer <b>441</b> and a cable box <b>443</b>. In <figref idref="DRAWINGS">FIG. 15</figref>, the user has zoomed into the image <b>340</b> of <figref idref="DRAWINGS">FIG. 14</figref> until the displacement between transformer <b>441</b> and cable box <b>443</b> is readily visible, enabling the user to draw a measurement line <b>439</b> extending between transformer <b>441</b> and a cable box <b>443</b> while measurement window <b>433</b> again displays the straight line distance between endpoints of the measurement line <b>439</b> as calculated from point cloud data corresponding to the endpoints of measurement line <b>439</b>.
0070In some embodiments, measurement functionality includes features in addition to straight line distance measurements. <figref idref="DRAWINGS">FIG. 16</figref> illustrates the use of measurement window <b>433</b> to measure the orientation or slope of one or more features depicted in image <b>340</b>. In <figref idref="DRAWINGS">FIG. 16</figref>, a user has selected a slope feature <b>451</b> from measurement window <b>433</b> and drawn a measurement line <b>453</b> extending from utility pole <b>425</b> along a wire <b>455</b> attached to utility pole <b>425</b>. The planning tool again determines XY image coordinates of the endpoints of line <b>453</b>, retrieves or otherwise accesses point cloud data underlying image <b>340</b> to determine three dimensional coordinates of the endpoints of line <b>453</b>, and calculates a slope of line <b>453</b>. In at least one embodiment, the slope calculated represents the slope relative to a theoretical plane oriented parallel to the earth's surface such that the slope of line <b>453</b> would be the same or substantially the same regardless of the particular viewing angle presented in image <b>340</b>. Measurement functionality supported by the planning tool may further include features to measure the length of curved or non-linear line segments, the measurement of the area enclosed by one or more user-drawn lines or shapes, and dimensions associated with outer measurable features.
0071Referring now to <figref idref="DRAWINGS">FIG. 17</figref>, an image <b>340</b> of a location is depicted in an interface <b>461</b> while a corresponding map or other 2D view of the location is illustrated in a picture in picture window <b>463</b>. The picture in picture window <b>463</b> includes a colored dot <b>465</b> or other visible detectable overlay feature indicating an outdoor plant asset, a flashy antenna <b>467</b> in this example, that is visible within image <b>340</b> at its actual position, elevated from the ground and in contact with a building <b>462</b> in interface <b>461</b>. Point cloud data associated with the image <b>340</b> illustrated in <figref idref="DRAWINGS">FIG. 17</figref> thus includes a point cloud data object corresponding to flashy antenna <b>467</b>, indicating the height or elevation of flashy antenna <b>467</b>. At least one beneficial feature encompassed by the interface <b>461</b> depicted in <figref idref="DRAWINGS">FIG. 17</figref> is the use of a 3D planning tool to provide third coordinate information to pre-existing assets stored or otherwise catalogued in a legacy planning tool database. Thus, for example, if flashy antenna <b>467</b> is recorded in a pre-existing asset database for a 2D planning tool the coordinates would convey, for example, the street address at which the antenna was located. However, embodiments of the 3D planning tool enable a user to access a streetview image of a location and a corresponding map that indicates one or more outside plant assets. The user may then select an outside plant asset indicated in the map and view any attribute information associated with the asset. The user may then append an appropriate icon to the appropriate location within the street view image and associate the streetview image icon with the corresponding asset such that the outside plant asset inherits all of the attributes of the asset from the 2D database and supplements the information with elevation information or other information suitable to indicate a position of the asset within a 3D coordinate space.
0072<figref idref="DRAWINGS">FIG. 18</figref> illustrates a virtual asset feature in which a proposed asset is represented by a virtual object including virtual point cloud data. The virtual object may be appended to or otherwise associated with an image <b>340</b> of a location to provide a visualization of the proposed asset as located in the proposed location. In <figref idref="DRAWINGS">FIG. 18</figref>, a virtual asset is illustrated in the form of a virtual utility pole object <b>481</b>. Virtual utility pole object <b>481</b> includes an icon representing an image of the propose asset and virtual point cloud data associated with the proposed asset. The virtual point cloud data indicates 3D coordinates of a virtual asset relative to a virtual origin. When a virtual asset is dragged and dropped or otherwise appended to an image <b>340</b> of a location, 3D coordinates may be assigned to the virtual origin of the virtual asset. After coordinates are associated with the origin of a virtual asset, the virtual assets remaining coordinates may be resolved based on the 3D coordinate of the asset's origin and the virtual point cloud data. Once a virtual asset is appended to an image <b>340</b> as a proposed asset, the proposed asset may be manipulated with the planning tool in the same manner as any other asset. Thus, for example, a user may perform a “walk around” of the proposed asset by zooming and panning the interface, measure the asset using the previously described measurement features, and so forth.
0073To the maximum extent allowed by law, the scope of the present disclosure is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited to the specific embodiments described in the foregoing detailed description.
Contents3
11 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11
Every citation, both ways
| Document | Relation | Office | Category | Cited during | Relevant claims |
|---|---|---|---|---|---|
| US11025889B2 | Cited by | United States of America | – | Applicant | – |
| US12108260B2 | Cited by | United States of America | – | Applicant | – |
| US11502917B1 | Cited by | United States of America | – | Search report | – |
| US9699671B1 | Cited by | United States of America | – | Search report | – |
| US11115833B1 | Cited by | United States of America | – | Applicant | – |
| US12264933B2 | Cited by | United States of America | – | Applicant | – |
| WO2024047861A1 | Cited by | World Intellectual Property Organization (WIPO) | – | International search | – |
| US11788856B2 | Cited by | United States of America | – | Search report | – |
| GB2602344A | Cited by | United Kingdom | – | Search report | – |
| US12211251B2 | Cited by | United States of America | – | Search report | – |
| US11916610B2 | Cited by | United States of America | – | Search report | – |
| US2022166527A1 | Cited by | United States of America | – | Search report | – |
| CN106488465A | Cited by | China | – | Search report | – |
| US10397799B2 | Cited by | United States of America | – | Search report | – |
| US11323890B2 | Cited by | United States of America | – | Applicant | – |
| US11350288B1 | Cited by | United States of America | – | Search report | – |
| US2023326180A1 | Cited by | United States of America | – | Search report | – |
| US2016147408A1 | Cited by | United States of America | – | Pre-grant | – |
| US10687230B2 | Cited by | United States of America | – | Applicant | – |
| US11310480B2 | Cited by | United States of America | – | Applicant | – |
| US10397798B2 | Cited by | United States of America | – | Search report | – |
| EP4020919A1 | Cited by | European Patent Office (EPO) | – | Applicant | – |
| US12081999B1 | Cited by | United States of America | – | Applicant | – |
| US2018350073A1 | Cited by | United States of America | – | Search report | – |
| US12136163B2 | Cited by | United States of America | – | Search report | – |
| US2022104029A1 | Cited by | United States of America | – | Search report | – |
| US10484889B2 | Cited by | United States of America | – | Applicant | – |
| JP2024047828A | Cited by | Japan | – | Search report | – |
| JPWO2024047861A1 | Cited by | Japan | – | Search report | – |
| US11463680B2 | Cited by | United States of America | – | Search report | – |
| US2022004779A1 | Cited by | United States of America | – | Search report | – |
| US11228501B2 | Cited by | United States of America | – | Search report | – |
| US10432913B2 | Cited by | United States of America | – | Search report | – |
| US2002013837A1 | Cites | United States of America | A | Pre-grant | – |
| US2002013837A1 | Cites | United States of America | A | Search report | – |
| US2007088709A1 | Cites | United States of America | Y | Search report | 1-7, 10-16, 18 |
| US2007088709A1 | Cites | United States of America | Y | Pre-grant | 1-7, 10-16, 18 |
| US2009323121A1 | Cites | United States of America | Y | Search report | 11 |
| US2013159862A1 | Cites | United States of America | – | Pre-grant | – |
| US2013228620A1 | Cites | United States of America | Y | Search report | 10 |
| US2014141788A1 | Cites | United States of America | Y | Search report | 1-7, 10-16, 18 |
| US7317456B1 | Cites | United States of America | A | Pre-grant | – |
| US7317456B1 | Cites | United States of America | A | Search report | – |
| US7477360B2 | Cites | United States of America | A | Pre-grant | – |
| US7477360B2 | Cites | United States of America | A | Search report | – |
| US8179393B2 | Cites | United States of America | A | Pre-grant | – |
| US8179393B2 | Cites | United States of America | A | Search report | – |
| US9384399B2 | Cites | United States of America | A | Pre-grant | – |
| US9384399B2 | Cites | United States of America | A | Search report | – |
2 members in 1 office
Members2
| Document | Office | Kind | |
|---|---|---|---|
| US2016037356A1 | United States of America | A1 | |
| US10412594B2 | United States of America | B2 |
83 transactions on the USPTO file
Allowed after 3 non-final rejections, 1 final rejection and 1 RCE.
- Non-final rejections
- 3
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Correspondence Address ChangeC.AD | C.AD | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Workflow - Drawings FinishedDRWF | DRWF | |
| Email NotificationEML_NTR | EML_NTR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mailing Corrected Notice of AllowabilityMCNOA | MCNOA | |
| Corrected Notice of AllowabilityCNOA | CNOA | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail PUB other miscellaneous communication to applicantMM327-D | MM327-D | |
| PUB Other miscellaneous communication to applicantM327-D | M327-D | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Mail Notice of Rescinded AbandonmentAbandonedMNRAB | MNRAB | |
| Notice of Rescinded Abandonment in TCsAbandonedNRAB | NRAB | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Mail Abandonment for Failure to Respond to Office ActionAbandonedMABN2 | MABN2 | |
| Aband. for Failure to Respond to O. A.AbandonedABN2 | ABN2 | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Request for Classification Division DecisionTI1054 | TI1054 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Sent to Classification ContractorPGPC | PGPC | |
| FITF set to YES - revise initial settingFTFS | FTFS | |
| Application Is Now CompleteCOMP | COMP | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Application Is Now CompleteCOMP | COMP | |
| Cleared by OIPE CSRL194 | L194 | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Patent Term Adjustment - Ready for ExaminationPTA.RFE | PTA.RFE | |
| Applicants have given acceptable permission for participating foreignAPPERMS | APPERMS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Entity status set to undiscounted (initial default setting or status change)BIG. | BIG. | |
| Initial Exam Team nnIEXX | IEXX |
8 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| Information on status: patent application and granting procedure in generalPUBLICATIONS -- ISSUE FEE PAYMENT VERIFIEDSTPP | STPP | |
| Information on status: patent application and granting procedure in generalAWAITING TC RESP., ISSUE FEE NOT PAIDSTPP | STPP | |
| Information on status: patent application and granting procedure in generalNOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONSSTPP | STPP | |
| Information on status: patent application and granting procedure in generalRESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINERSTPP | STPP | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication
- 20160037356
- Application
- 14448601
Titles
- English
- NETWORK PLANNING TOOL SUPPORT FOR 3D DATA
Patent term adjustment
- A delay
- +365 daysthe office missed an examination deadline
- B delay
- +462 dayspendency past three years
- Overlap
- −9 daysdelays counted once
- Applicant delay
- −220 days
- Net adjustment
- 598 days
Classification
- CPC, 5
- H04W16/18
- H04W64/003
- H04L41/22
- G06T19/006
- G06T2215/16
- IPC, 4
- H04W16 18
- G06T19 00
- H04L12 24
- H04W64 00
- USPC, 1
- 455446000