_standard_header _standard_header.cfm
     Conversation History             1969-1984
... 668/3347 ...
January 2019    Dennis R. DuBe'     668/3347

$s$ .description ()

19730912_fleenor.jpg ()

20110508_fairplay.jpg ()

20110508_fairplay_vortex.jpg ()

20110810_pedigree_1.jpg ()

20110823_the_end_of_trust.jpg ()

20111122_DSCN7995.JPG structure permissions ()

20111122_truman_view.jpg ()

20111206_trends_try.jpg ()

20111221_real_world_games.jpg ()

20120117_Permissions.jpg ()

20120222_info_slope.jpg ()

20120326_Dark_Net.jpg ()

20120326_Scott_Protocol_Stack.jpg ()

20120410_magic_glasses.jp ()

20120412_How_to_kill_Facdbook.jpg ()

20120412_Kill_facebook_1. ()

20120412_Sharing_Moment.jpg ()

20120625_next_paradigm.jpg ()



20120627_Privacy_is_BAD.jpg ()

20120627_sit_there_and_twitch_cafe.jpg ()

20120712_How_to_reveal_structure.jpg ()

20120719_Can_you_phrase_3 ()

20120719_can_you_phrase_A...jpg ()

20120719_phrase_as_a_question.jpg ()

20120724_Closed_Pond_Comforts.jpg ()

20120724_Forbin_Project.jpg ()

20120724_Residue_of_Attention.jpg ()

20120726_attention_presence.jpg ()

20120802_how_to_kill_faceook_2.jpg ()

20120807_attention_produced_realities.jpg ()

20120809_attention_field_goals.jpg ()

20120821_black_hole_pay_your_own_way.jpg ()

20120821_velcroed_consumers.jpg ()

20120911_levels_of_content.jpg ()

20120911_SM_As_Attention_Layer.jpg ()

20120912_deconstructing_apple.jpg ()

20120918_Follow_The_money.jpg ()

20120918_Velcroed_Into_Mindless.jpg ()

20120926_An_API_For_Structure.jpg ()

20120926_API_for_theory.jpg ()

20120926_Consulting_plan.jpg ()

20120926_Structure_Content_Behavior.jpg ()

20121003_What_is_attention_field.jpg ()

20121010_triangles_of_property.jp ()

20121022_Structure_Dog.jpg ()

20121022_zen_of_privacy.jpg ()

20121024_Attention_vs_privacy.jpg ()

20121024_privacy_becmes_attention.jpg ()

20121105_The_Before_Time.jpg ()

20121105_What_Do_People_Want_of_Media.jpg ()

20121107_creation_of_property.jpg ()

20121107_Fanboy_Analysis.jpg ()

20121114_moment_of_consumption.jpg ()

20121114_structure_content_triangle.jpg ()

20121119_Binding_and_Un_Binding.jpg ()

20121119_Fanboys_Progress.jpg ()

20121119_fanboy_bindings.jpg ()

20121119_Gigapop_Power_Rangers.jpg ()

20121119_totem_characteristics.jpg ()

20130110_fanboy_ecosystem.jpg ()

20130110_fanboy_the_movie.jpg ()

20130118_Then_Now.jpg ()


Related Publishers:
736 Aftermath
710 Behavior
772 Catalogs
748 CFS -- Walter Beckert
459 Colorado Rocks
739 Consulting
669 Consulting
709 Content
707 Dennis R. DuBe'
741 Drafts
650 Energy News
344 HTML and Web Skills
742 Key Concepts
716 LFU test
717 LFU Test 2
729 My Latest Clippings
649 New Courses
744 News Panels
721 Position
658 PPV & Gadgets
77 Rocky Mountain Ghost Mines
708 Structure
731 Synthesis
726 Thesis Notes
666 _Aggregation
702 _Determinisms and authors
728 _Papers by Others
668 __Whiteboards
698 ___FanBoy (The Movie)
718 ___Gamification
     Privacy issues can be managed if users can grant connection permissions at the moment of subscription. An independent service would be required to round up the details.
           #3347   Created 04/26/2013   Updated 04/26/2013

Absract: A service which manages the granting of permissions from mobile device users to commercial entities that allow remote identification of, and communications with, users' mobile devices. Such a service would buffer the relationship among device owners, communications carriers, and commercial entities, facilitating the transfer of permissions information among carriers, Apps on devices, and commercial services. ----

A friend came up with the great question, which he later blamed on me, of how to use the GPS and communications capabilities of mobile devices to configure "ad-hoc networks", virtual private networks cobbled together on the backs of he cellular carriers, cable companies, and Ma Bell

It took me a while to parse the brilliance of his vision, but the idea of "self-configuring networks" kept returning (he kept bringing it up), wherein networks are created by the voluntary agreement of the nodes, instead of being created through the gathering of nodes by an administration.

The core of the idea involves users giving permissions to business entities to contact ("call") them under specific circumstances, for the purpose of linking their mobile devices into a temporary collection of individual devices to form a network.

The purpose of such an ad-hoc network would be the purpose of any physical network, that is, to provide services to users. Back in the old days, such services had names like "hosting" and "email" and "storage". That is, the services were content-centric, devoted to the details of 'where' data lives, and 'how' it is disseminated.

So, what are they called here in the Re-PostModern age? The content-centric nature of the old days determined the nature of the network's services; it was all about content: carrying it, storing it, vending it.

The relationship-centric trend of modern media suggests that the content of the ad-hoc network is relationships and permissions.

Dig this: A business purposes can be imagined that can take advantage of this combination of permissions from user:

--the permission to contact them on their device,

--the permission to know where they are, and

--the permission to utilize the other sensors on their mobile device for commercial purposes.

The missing link is the ability to recognize mobile devices in a geographic area, and back track to the identities of the humans. It is technically possible, but requires the permission of the carriers (phone companies) to query for the data. Carriers are probably reluctant to cooperate on such schemes on an ad-hoc basis, and it would always require the permission of the account holder.

Permissions, again. Further, these permissions must be given in advance, but utilized on-the-fly.

So, the primary administrative question is how to accommodate the interests of the carriers (it's their network), the users (it's their phone and account), and the business partners (the ones who want to use the network service).

A possible answer is to create the permission-granting process as part of the device user's normal subscription relationship with their provider. We envision a "permission management" service that manages relationships among:

--entities with applications the utilize the ability to communicate with consumers in known locations;

--carriers that have provider relationships with those consumers;

--the consumers.

The administrative aspect of the operation is the installation of the appropriate "app" onto mobile devices, that would allow the functionality desired by the business partners. With such a network capability, business models can be constructed that take advantage of these services.

An example (but not necessarily a good one), is the ability of a newspaper to take advantage of its subscriber relationships. As part of the subscription process, a subscriber can agree to participate in a program, giving permission for the publishing company to:

--see which subscribers are within a discrete geographic area;

--contact those subscribers via text or voice;

--communicate with those subscribers for commercial purposes;

--utilize the sensors on the subscriber's mobile device, with permission to re-use the captured live content;

Another example (equally dicey) is the ability of an event organizer (The Denver Broncos) to know the location and identities of certain classes of ticket holders within their stadium facility, and to push features and services to them as data, or to promote other feather to them through media.

A third example (probably true) is the ability of commercial airports to know the identity of large numbers of people who enter into airport facilities, by back-tracking device identities to commercial subscriber relationships.



Copyright Dennis R. DuBe'. All rights reserved. PageTwister and PubSource are registered trademarks.