Mash-up Map Permalink Generation with Layered Identifiers

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing map data services cannot generate permalinks for mash-up map data that include various information such as advertisements and user-generated content, limiting the sharing and distribution of such data across different platforms and locations.

Innovation Solution

A system and method for generating a permalink for mash-up map data that combines identifiers for the base map layer and additional service layers, including advertisement and user-generated data layers, using a delimiter to create a universal resource locator (URL) that can be used to share and distribute mash-up map data across various platforms like blogs and emails.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional permalink systems are used for basic map data, then simple map locations can be shared, but mash-up map data with multiple information layers cannot be properly distributed

Engineering Contradiction:

Improvecompatibility with mash-up map dataVSAvoidadditional service data

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The permalink is segmented into multiple distinct components: base map information (server address, map number, coordinates) and additional service information (advertisement layer ID, user-generated data layer ID, etc.). Each segment is separated by delimiters, allowing the system to preserve and transmit multiple types of information layers independently while maintaining overall permalink functionality.

Inventive Principle:

Principle #1Segmentation

2Loss of information

If mash-up map data with multiple layers is shared using conventional methods, then basic location information can be transmitted, but real-time additional service data cannot be included

Engineering Contradiction:

Improveadditional service dataVSAvoidpermalink structure

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The permalink system is designed with universal structure that can handle both basic map data and complex mash-up map data with multiple information layers. The standardized format with delimiters and layer identifiers allows the same permalink mechanism to serve multiple functions: simple location sharing, advertisement distribution, user-generated content sharing, and real-time data transmission across different platforms.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If permalinks include multiple information layers, then comprehensive map data can be shared, but the permalink structure becomes complex

Engineering Contradiction:

Improveinformation layers includedVSAvoidpermalink structure

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Delimiters serve as intermediary elements that separate and organize different information layers within the permalink structure. These delimiters act as mediators between the base map data and additional service data, enabling the system to handle complex multi-layer information while maintaining a standardized, parseable format that can be processed by the permalink providing system.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS8271490B2System for generating permalink of mash-up map

Publication Date: 2012.09.18 NHN CORP

AI summary

A system and method for generating a unique link (i.e., map permalink) of mash-up map data including various information are provided. The system receives a request for generation of the map permalink of specific mash-up map data, and generates a map URL including map information in response to the request for generation of the map permalink. Also, the system generates at least one of an advertisement layer identifier, an additional service data identifier, and a user-generated data identifier, combines the generated identifier with the map URL, and stores the combined identifier together with related data.