IN-DOOR MAP SERVER

• US 20140149474A1
• Filed: 11/01/2013
• Published: 05/29/2014
• Est. Priority Date: 11/23/2012
• Status: Abandoned Application

• Current Assignee: Hyundai Mnsoft, Inc. (Hyundai Mobis Co., Ltd.)
• Original Assignee: Hyundai Mnsoft, Inc. (Hyundai Mobis Co., Ltd.)
• Inventors: LEE, Seok Ho, YANG, Hyun Jong
• Application Number:
  US14/069,511
• Publication Number:
  US 20140149474A1
• Time in Patent Office: Days
• US Class Current: 707/825
• CPC Class Codes: G01C 21/206 specially adapted for indoor navigation
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G09B 29/003 Maps

Abstract

A server for storing an indoor map, the server comprising: a first storage area configured to store network data, the network data including node data and link data that constitute a building; and a second storage area configured to store floor data, the floor data including space data representing logical division space for each floor and geometry data representing a physical separation space.

Claims

1. A server for storing an indoor map, the server comprising:

a first storage area configured to store network data, the network data including node data and link data that constitute a building; and

a second storage area configured to store floor data, the floor data including space data representing logical division space for each floor and geometry data representing a physical separation space.

2. The server of claim 1, wherein the first storage area is further configured to store time-constraint data having information about a restricted passage depending on the variation of time.

3. The server of claim 1, wherein the second storage area is further configured to store 2D geometry data and 3D geometry data.

4. The server of claim 1, further comprising:

a third storage area configured to store the type of data that is stored in the first and second storage areas.

5. The server of claim 4, wherein the third storage area is configured to store any one of a floor format version, network data version, plane spatial region including lower right information and lower left information having absolute coordinates of a polygon area corresponding to an indoor map region, minimum spatial region of data including information of the lowest floor of a building and a reference height of the building, POI ID, a network data frame offset indicating a value of locations where the network data is stored in the indoor map data or file, a network data frame in which attribute values of the network data is stored, data size, the number of floor data frames, a total data size of floor data frames, and a list of floor data frame offsets which are locations in data or file where each floor data is stored when the building has a plurality of floors.

6. The server of claim 1, wherein the network data further includes a network data frame header and time-constraint detail data.

7. The server of claim 6, wherein the network data frame header includes:

a start offset of the node data indicative of location information in data or file, a data size of the node data, an start offset of the link data, a data size of the link data, a start offset of the time-constraint detail data, and a data size of the time-constraint detail.

8. The server of claim 1, wherein the node data includes:

a node data header, node data record columns, and connecting link data record columns.

9. The server of claim 1, wherein the link data includes:

a link data header, link data record columns, and a coordinate record column of interpolation point, which is a node formed at an intermediate of a link, except for both end nodes of the link.

10. The server of claim 6, wherein the time-constraint detail data includes:

a time-constraint detail header, record columns of time-constraint matching information which corresponds to matching information to connect a link ID and the time-constraint detail, and record columns of the time-constraint detail.

11. The server of claim 1, wherein the space data includes:

a space data header and space data record columns.

12. The server of claim 6, wherein the 2D geometry data includes:

a 2D geometry data header, 2D object index data which is record column in which an object is stored, and 2D space node data.

13. The server of claim 6, wherein the 3D geometry data includes:

a 3D geometry data header, 3D object index data which is record column in which an object is stored, and 3D space node data.

14. A server for storing an indoor map, wherein the indoor map comprises one file of the indoor map on a building basis,

wherein the file is composed of a network data frame and a floor data frame,

wherein the network data frame includes node data, link data, and time-constraint data, and

wherein the floor data frame includes space data, 2D geometry data and 3D geometry data.