RGB network and device

Abstract

A network can include a client device, a provider device, and a database array. The network can be configured for RGB formatted data. The client device processes client input and converts it into rows of a client data column in a composite database stored in a storage device. The client data rows include transcoded RGB format of the client input. The provider device processes provider input. The database array or the provider device can process the provider input into rows of a provider data column in transcoded RGB format of the provider input. Collimation of the client and provider RGB formatted data can produce complementary indicia of the client and provider input.

Description

Technical Field

[0001] This application provides networks and devices formatted for RGB data transmission. Background Technology

[0002] Network equipment suffers from a lack of security. Many technologies (such as encryption and hashing) have been developed to try to make it difficult for spyware or ransomware to obtain sensitive information. This makes network users hesitant to choose network providers. There is a desire to increase the security of user information on the network.

[0003] Furthermore, there is a desire to enhance the ease of access to network providers. Typically, users avoid activities such as self-care or casual dates due to the difficulty of selection. Agency services can coordinate such bookings, but using intermediaries requires time and repeated interventions. Summary of the Invention

[0004] The network described in this paper provides a new method for encoding, storing, exchanging, sending, decoding, and receiving data.

[0005] Networks offer alternative solutions to the problem of unintended limitations on individual or collective resonance. A first system in the network transforms existing technology into the secure delivery of goods and services to individuals. Conversely, a second system transforms existing technology into the virtual extension of individuals to goods or services. Finally, the combination of systems forms the intentional basis for optical wireless networks. Optical wireless networks may include photonic transcoding micro-LED displays and data center equipment.

[0006] Mobile applications on client or provider devices can be characterized by the 3Ws (WHAT, WHERE, and WHEN) for searching. Unique RGB color encoding and transmission match physical work, virtual work, or things, relaying availability to clients and providers. Clients access mobile applications with improved data security, privacy, and efficiency. Clients input the subject [“request” or WHAT], location [“access” or WHERE], and time [“scheduling” or WHEN]. While devices such as touchscreens, keyboards, or mice can be used to input client information, this input can be digitally processed on the client device. However, algorithms stored and processed on the client device can transform the digital data. Client input can be encoded as color or frequency. Then, the client input is similar to the format applied to pixels and can be referred to as RGB formatted. Client input can be synchronized with a database array configured for 3W. Multiple locations, languages, and time zones can now be synchronized in the database array to provide separate but simultaneous output to client devices. Client 3W searches and preferences can be retained on the client device via a smart calendar. The synthesizer can operate on a synthesized database to match geographic time RGB formatted data to find complementary matches to customer input. Simultaneous searches for providers complementary to customer preferences can be performed for all scenarios.

[0007] The network can connect to Product Information Management (“PIM”) data and pre-employment surveys to retain customer consumer data on client devices. This differs from other networks where customer consumer data is shared, hacked, sold, mined, and otherwise insecurely distributed. Automatic synchronization between the 3W RGB database array and client devices generates customer (buyer) and provider (seller) matching notifications, including tags on the client devices. Matching can be done for things an individual needs or wants to accomplish during a time window specified on their smart calendar for providing or receiving services. As outlined in this paper, this alleviates the burden on customers of making numerous phone calls, searching multiple databases, submitting numerous queries, or hiring intermediaries to do the same. In addition to automating this tedious task, a security layer is applied that cannot be achieved using traditional phone calls and database searches. Instead of explaining parameters to human agents or subjecting customers to extended cookies, privacy breaches, password and account collection for simple queries, the network described in this paper can be configured so that a customer's identity does not leave the client device until a booking is made with the provider. It's possible to obfuscate preferences, search history, and other private information from the web to mitigate violations of customer privacy. Now, the mental paralysis of procrastination can be lifted, enabling users to engage in productive and non-intrusive business and leisure activities.

[0008] The network may include client devices, provider devices, and database arrays. The network can be configured for RGB-formatted data. Client devices process client input and convert it into rows of client data columns in a synthetic database stored on storage devices. The client data rows include the transcoded RGB format of the client input. Provider devices process provider input. The database array or provider device can process provider input into rows of provider data columns in transcoded RGB format. Collimation of the client RGB-formatted data and the provider RGB-formatted data can produce complementary markers for the client and provider inputs.

[0009] The network includes client devices configured to communicate bidirectionally with the network and to receive, store, and process client input within client computing devices that include at least a client processor and client storage. The client input includes at least client request data, client access data, and client scheduling data that are digitally processed within the client computing device. The client device processes the client input in its processor using a stored client algorithm from the stored storage device, the stored client algorithm being configured to transform the client input into rows of client data columns in a synthetic database stored in the storage device, the client data rows including the transcoded RGB format of the client input.

[0010] The network may include a database array comprising at least a red database, a green database, and a blue database corresponding to RGB-formatted data. The red data database can be configured to store client input in red RGB format and provider input in red RGB format. The green data database can be configured to store client input in green RGB format and provider input in green RGB format. The blue data database can be configured to store client input in blue RGB format and provider input in blue RGB format.

[0011] The network can be configured such that a client device is further configured to receive, store, and process network input in a computing device. The network input includes at least provider request data, provider access data, and provider scheduling data. The client device can be configured to process the network input in a client processor using a client algorithm configured to associate the network input with rows of a provider data column in a synthesis database. These rows of provider data include the RGB format of the network input. The rows of the client data column can be synthesized with the rows of the provider data column. Synthesis may include collimating the RGB-formatted network input with the RGB-formatted client input to produce a collimated pixel value row. The network can be configured to discard the collimated pixel value row when it includes one or more pixel values ​​outside a predetermined range of pixel values ​​or when it includes non-white pixel values. Alternatively, the network can be configured such that when the collimated pixel value row is collimated within a predetermined range or when it is collimated to all white pixel values, the collimated pixel value row is stored in one or more of the client device or database array and a matching marker is displayed on the client display device.

[0012] The network may include a provider device configured to communicate bidirectionally with the network and digitally receive, store, and process provider input in a provider computing device that includes at least a provider processor and provider storage. The provider input may include at least provider request data, provider access data, and provider scheduling data. The provider device may be configured to process the provider input in the provider processor using a stored provider algorithm stored in the provider storage. The provider algorithm may be configured to transcode the digital provider input into provider RGB formatted data. Provider request data may include red, green, and blue provider request data pixels. Provider access data may include red, green, and blue provider access data pixels. Provider scheduling data may include red, green, and blue provider scheduling data pixels. The provider device may transmit the RGB formatted data to a database array. Alternatively, the provider device may forward the digital provider input to a server of the database array for RGB formatting.

[0013] Additional objects and advantages will be set forth in part in the description which follows, and in part will be apparent from the description, or may be learned by practice of this disclosure. Objects and advantages will also be realized and obtained by means of the elements and combinations particularly pointed out in the appended claims.

[0014] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only, and not intended to limit the claimed invention. Attached Figure Description

[0015] Figure 1 It is a view of global time zones.

[0016] Figure 2A and Figure 2B It is the view of the user's device.

[0017] Figure 3 It is a representation of a finite state reader used for survey data.

[0018] Figure 4 It is a representation of a synthetic database.

[0019] Figure 5A and Figure 5B It is a diagram of RGB formatted client input, RGB formatted provider input, and composite data including collimated pixel values.

[0020] Figure 6A and Figure 6B This illustrates aspects of a two-way communication network.

[0021] Figures 7A to 7C It represents the access pixel spectrum.

[0022] Figure 8A and Figure 8B It is a representation of the scheduling pixel spectrum.

[0023] Figure 9 This is an example of a remote access reservation. Detailed Implementation

[0024] Referring now to the examples shown in the accompanying drawings. Wherever possible, the same reference numerals will be used throughout the drawings to refer to the same or similar parts. Directional references such as "left" and "right" are used for ease of reference in the drawings. As a bidirectional system, multiple aspects will be described according to one approach, and additional approaches can be understood and inferred by studying the drawings and examples. The customer described herein may be a provider, and therefore, a client device may include additional aspects of a provider device. Similarly, a provider may be a customer, and therefore, a provider device may include additional aspects of a client device.

[0025] Users, including customers and providers, value their time. Providers may offer goods or services ("requests" or "WHATs") at selected times ("scheduling" or "WHEN") and at one or more selected locations ("access" or "WHERE"), based on the access parameters. For customers to be able to use or access these goods or services at the same time they are available, based on the access parameters, customers need to be transparent with the provider's WHAT, WHERE, and WHEN ("3Ws"). Simultaneously, users need to protect their network presence.

[0026] Time can be used as an aspect of the search method. Figure 1 This facilitates understanding in this area. The time available to a seller or worker to provide goods or services can be conceived as complementary to the time a buyer or employer must receive them. Time complementarity matching between two users is performed by assigning complementary colors between users who have time to give them and users who have time to receive them. Figure 1 The Earth is represented as a common circle. Time zones are distributed globally. The intersections of smaller circles represent time zones and the associated RGB-formatted scheduling data. At the bottom of the Earth, at the zero time axis TZ, the baseline zero time is given. Time changes in one-hour increments as the Earth is traversed. Other time increments, such as minutes, quarter-hours, etc., can be selected. The increments can vary like the pixel values ​​in the pixel spectrum used to represent time. Using red, green, and blue (“RGB”) formatting, 16 million pixel values ​​are available for dividing global time.

[0027] Users can specify the times available for providing goods or services and their complementary colors, and can also mark the times available for receiving goods or services. For example, a customer can specify that +9 hours are unavailable for providing work or receiving services. In RGB format, this would mean the circle from +23:00 to +08:00 is shaded green. From +08:00 to +16:00, the customer can specify that they are available to provide goods or services. In RGB format, this would mean the corresponding circle is shaded yellow. Another color, blue, can be used to specify that the customer is available to receive goods or services (another person's work). For the -7 hours from +16:00 to +23:00, the corresponding circle could be shaded blue.

[0028] Complementary colors are pairs of colors that cancel each other out when combined. Using additive color mixing as a guide, RGB-formatted data can be synthesized based on digital collimation so that complementary colors can be combined to represent white. Therefore, when complementary colors match, a matching marker is created and the user of the complementary color is notified.

[0029] In Figure 1In a complementary example, global time could also be mapped, where we could assign either monochrome or RGB format, with one color used for every fifteen (15) minutes of a 24-hour period across all thirty-eight (38) time zones. Its complementary color would then be assigned to match within the same time zone. The ninety-six (96) Greenwich Mean Time colors could be part of a color code. When users, such as providers, indicate the times when they can provide goods and services, these times could be in RGB format complementary to the client's RGB format. Figure 1 Providers of goods and services can have the same Figure 1 The timing of overlapping customer appointments can be considered. For example, at +20:00, a provider might have a gap in their schedule to offer, for example, a writing service. The provider's calendar uses a yellow shading, which complements the blue shading used on the customer's calendar. Even though the users are not in the same location, the customer can know that the provider is available for hiring. The synthesis of blue and yellow RGB formatted scheduling (WHEN) data produces a white pixel value. The matching tag can be forwarded to the customer for acceptance. A global approach can be implemented to allow matching users in different time zones. For example, a user in Tokyo could have a complementary RGB format like a user in Los Angeles. A user in Tokyo could hire or provide services to a user in Los Angeles. Therefore, matching can be performed between users across all time zones.

[0030] This invention eliminates time as a barrier to achieving personal goals. By mapping time in this way, people can see that the end of one day in their own time zone is the beginning of a new day in another. This opens up the potential for work / life balance structures for multiple global teams. For example, a team of three (3) people can perform a non-overlapping work relay every eight hours. On the other hand, a team of four (4) people can work eight hours a day, with two (2) hours overlapping at one end of the workday or one (1) hour overlapping at either end. In addition, a variety of part-time work relay methods are available. As remote work unexpectedly becomes the international norm, easy time synchronization between people with different lifestyles and schedules across multiple time zones will also contribute to workflows and work-life balance.

[0031] Early risers and night owls can work comfortably simultaneously in different time zones. Or, within the same time zone, early risers can pass the work to night owls. By understanding time as a framework for observing the Earth's movements, we can begin to use the Earth's motion to our advantage. When combined with technology, we can increase our mobility and reduce the paralysis of procrastination.

[0032] Figure 2A and Figure 2BFurther explanation is provided. It is understood that a user can be both a customer and a provider, and the device shown can be either a user device or a provider device. Assignment programming, for example, can be used to separate the algorithmic processing discussed herein. For instance, the storage device of a smartphone (or tablet, computer, or other network-ready device) can be partitioned to store customer input as a client storage device and provider input as a provider storage device. The processor can be both a client processor and a provider processor, such as an algorithm-controlled one. The stored client algorithm and the stored provider algorithm can classify user input as either client input or provider input.

[0033] Figure 2A A combined calendar view is displayed. The 4th and 5th days of the month indicate that the user has completed their booked service. The 7th and 22nd days of the month indicate that the user can now receive services from others. The 9th, 13th, 17th, 21st, and 30th days indicate that the user is available to provide services. The 18th, 23rd, and 31st days of the month indicate that the user is reserved for providing services. The user interacts with input devices such as touchscreens, microphones, keyboards, and other devices to provide scheduling data, including customer scheduling data and provider scheduling data.

[0034] Figure 2B Conceptually built in an alternative visual format. The user input screen allows the user to select the density of time slots to fill. Time slots at 6:00 AM and 6:15 PM are indicated by color or other markers as open for receiving goods or services. Time slots at 12:00 PM and 8:00 PM are indicated as open for providing goods or services. Matching markers are provided, including sunburst shapes. Three matches are available for most available time slots, while there are no matches for the 12:00 PM time slot. Therefore, the user can choose from three providers as a customer to receive services and from three customers as a provider. Checkmarks can indicate that a matching marker has been reviewed to start a discard timer that counts down to data clearing mode. A color change to red indicates that a reservation has been made. Other times in the user's calendar are unavailable to the network. Unavailable times can be saved locally so that the network does not include more user knowledge than is needed to receive or provide goods or services. Optionally, calendar integration can be implemented to integrate calendar information saved locally or on the network (Outlook, iCal, or Google Calendar, etc.) with the user's device calendar as illustrated.

[0035] Users can participate in surveys that can be forwarded via the network. This facilitates the setting of user calendars. Customer and provider input can be received, stored, and processed. Much of the processing can be performed digitally in a traditional manner.

[0036] User input may include user input instructing the user to "open for accepting suggestions." Time slots can be designated as open via customer or provider access data, and customer or provider suggestions can be made with or without considering other information about the user. Alternatively, customer or provider access data can be combined with other information about the user to facilitate finding suggested matches.

[0037] Networked client devices can be configured to communicate bidirectionally with the network. Client devices can receive, store, and process client input within a client computing device that includes at least a client processor and client storage. Client input can include, at least, client request data, client access data, and client scheduling data that are digitally processed within the client computing device. Additional client input may include data collected via surveys or other fillable forms.

[0038] Customer request data (WHAT) can be derived from a list of things people procrastinate on or things they need to schedule in advance. Surveys can ask registered individuals whether the following items fall under the NEED, WANT, DREAM, MAYBE, or NEVER category.

[0039] Inferential surveys for provider request data can ask users whether they are eligible to be providers of any of the listed services. If so, they can ask whether they are interested in providing services from their current practice / office, from a future office, from their home office, and / or virtually or in person “home visits.” Table 1 provides a ranking tool for categorizing the survey data.

[0040] Table 1

[0041]

[0042] Table 2 provides example services as an example, not an exhaustive list. Additional services (such as beauty, self-care, home maintenance, professional services, medical appointments, part-time jobs, internet access, bucket list items, leisure activities, etc.) may be included as part of the survey. Goods may be included in the survey, such as shopping, prescription refills, takeout, household goods, etc.

[0043] Table 2

[0044]

[0045]

[0046] Customers can prioritize these things on the list, such as finding a dog walker so they can get to work on time; buying an alarm clock to wake up on time; arranging dry cleaning delivery to get to work on time, etc.

[0047] Much like spectral mapping for time zones and locations, goods and services can also be formatted in RGB. Pixel values ​​can be assigned to customer request data for each request category. Complementary pixel values ​​can be assigned to providers based on their ability to satisfy that request category. The RGB format allows for 16 million monochrome assignments for pixel values.

[0048] Scheduling data can be associated with each user's request. Customers can specify anniversaries, quarterly accounting consultations, weekly laundry services, bi-weekly meal services, and so on.

[0049] Of course, accessibility is a limitation. Users travel the world. Not all places are always accessible to users for all purposes. As disclosed in this paper, it is advantageous for users to plan their presence in a certain location in advance. Even while traveling, customers can now fulfill requests such as haircuts or leisure activities (WHAT). RGB formatting makes it clear what providers are available at what location and time. Similarly, travel providers can indicate availability so they can book multiple customers during their trip. Now, users can easily search for matches outside their home in their time zone and geographic area. Given that existing search systems are entangled in time zones, RGB formatting and calendar creation simplify the visualization and optimization of users' time. Replacing the use of time zone converters, local search syntax, international dialing codes, currency converters, geographically restricted banking and credit systems, and all other manual steps of accessing and verifying bookings, the synthetic database and collimation in this paper can seamlessly inform users of matches. Customer and provider survey results eliminate incompatibility issues in ways that previous systems could not accomplish. Therefore, it is advantageous to further specify user and provider access data (WHERE).

[0050] During this global pandemic, users no longer travel or book venues as they used to. However, performers and venues around the world remain available. The benefit of a global calendar is noting that your availability indication leads to matching in other locations (WHERE). By indicating that users are willing to access virtually, users can book remote equipment and access remote clients and providers. Figure 9 This example is provided. Arenas, stadiums, theaters, planetariums, museums, zoos, or other venues may include access areas such as standing rooms, seating areas, observation decks, etc. Customers can reserve virtual seats or viewing devices 9 at that location and participate remotely. If the provider provides an access point on the viewing device 9, it is possible to watch panda cubs, sunsets, orchestras, ballets, or sporting events. Figure 9The illustration shows a seating arrangement 90 filled with users 19 maintaining social distancing. Pricing schemes can be overlaid on the seating areas for virtual or in-person seating. In this case, virtual access points are provided by viewing devices 9 installed in the seats. The viewing devices can be installed on the ceiling or floor, and many other options are available. Users on one side of the world can access the concert in the other part of the world by accessing the viewing devices 9.

[0051] Due to the binary nature of user input, surveys and other user input interfaces operate under an RGB formatting scheme. Users are either interested in the request (WHAT) or not. They are either available (WHEN) or unavailable. They exist somewhere (WHERE) or do not exist. Many types of finite state machines are compatible with the teachings of this paper. Figure 3 An example of a finite state machine 30 is shown. User inputs (such as customer access data, customer request data, and customer scheduling data) are entered at cells 31, 33, 35, and 37. User inputs result in the selection of RGB pixel value bundles in rows 32, 34, 36, and 38. Some user inputs are passed down to other rows. For example, a customer request data input may cause a specific red customer request data pixel to be applied to a cascading row. Other inputs (such as benefit data, language data, cost data, voucher data, rating data, etc.) can be entered along with customer access data and customer scheduling data to create various profiles of what the customer wants the provider to satisfy. As an example, a customer may enter "pet service" as customer request data in their user device. Now, a specific decision tree emerges with time, location, voucher, pet service type, etc. Rows can organize the customer input for the "pet service" request as the user selects from veterinarian, groomer, walker, babysitter, etc. As the final output, red, blue, and green data rows are defined for the user inputs.

[0052] Providers, as complementary users, also input complementary details, showing what they offer (provider request data), when they are available (provider scheduling data), and where they provide or sell services or goods (provider access data). They can also input advantages, language, cost, credentials, ratings, and other data. As the final output, red, blue, and green data rows are designated for the provider inputs.

[0053] As discussed above, RGB formatted pixel values ​​are designed to produce complementary combinations of pixel values ​​so that when a user is looking for a specific provider, that provider has pixel values ​​that produce white pixel values ​​when collimated with the user's RGB formatted data. Alternatively, in the case surveyed in Table 1, the provider can be within a range that meets the customer's desires and needs. Non-white pixel values ​​can be within a computable range and still meet the user parameters.

[0054] To visualize the synthesis of user input and provider input, Figure 4 The diagram illustrates a representation of lens 40. The upper lens 41 can be analogous to a collimating lens for red pixel values. The middle lens 42 can be analogous to a collimating lens for green pixel values. The bottom lens 43 can be analogous to a collimating lens for blue pixel values. In a real optical system, white light is produced when red, blue, and green wavelengths are added together. Similarly, for lens 40, white or black units can be produced when red, blue, and green pixel values ​​are added together. Rows 47 and 49 are the most similar. If row 47 represents the client and row 49 represents the provider, then forwarding the matching tag to the client device would be logical. Rows 43 and 45 would include too many different collimated pixel values ​​to be forwarded.

[0055] Figure 5A , Figure 5B , Figure 6A and Figure 6B Additional diagrams are provided for visualizing customer input and provider input. Figure 5A and Figure 5BIn this diagram, the customer has entered various customer inputs, including 3W, via a smartphone, computer keyboard, touchscreen, or other input device. Five customer inputs 51 are shown. For explanation, customer input 51 can be customer request data, customer access data, customer scheduling data, benefit data, and voice data, but other customer inputs can be replaced, added, or deleted. Client device 61 processes customer input 51 in processor 612 using a stored customer algorithm from a stored storage device 611. The stored customer algorithm is configured to convert customer input 51 into rows of customer data columns in transcoded RGB format, including the customer input. For explanation, customer request data may include red pixel value 255, green pixel value 255, and blue pixel value 0. Customer access data may include red pixel value 255, green pixel value 178, and blue pixel value 102. Customer scheduling data may include red pixel value 255, green pixel value 0, and blue pixel value 0. Benefit data may include red pixel value 0, green pixel value 255, and blue pixel value 0. Language data may include a red pixel value of 0, a green pixel value of 0, and a blue pixel value of 255. These RGB-formatted client inputs 51 can be stored in separate client data rows in client databases 511, 512, 513 in the storage device 61 of the client device 61, or they can be stored in client data rows in the database array 64 of the network 60. It can be said that at least the request column receives each pixel value for the RGB-formatted client request data, such that red client request data pixels are stored in red client data rows, green client request data pixels are stored in green client data rows, and blue client request data pixels are stored in blue client data rows.

[0056] The customer data rows must include at least the red customer data rows in the red customer database 511 or the red database RDB, the green customer data rows in the green customer database 512 or the green database GDB, and the blue customer data rows in the blue customer database 513 or the blue database BDB. Specifically, each of the customer request data, customer access data, and customer scheduling data includes the pixel value in a row corresponding to a client data column in each of the red, green, and blue customer data rows. The use of pixel values ​​and RGB format provides unique security for customer input. If any of the customer databases 511-513 or the network databases RDB, GDB, or BDB are hacked or otherwise compromised, the data in that database is useless to the hacker without corresponding additional pixel values. All customer databases 511-513 need to be hacked simultaneously. Alternatively, all network databases RDB, GDB, or BDB need to be hacked simultaneously to collect any useful information.

[0057] like Figure 5A and Figure 5B As indicated by the double-headed arrow, customer input 51 can be stored in a customer database in memory 611 or a network database 64 for later processing. Alternatively, customer input can be fed directly to a synthesis database 53. The synthesis database 53 can be formed within processor 612 to perform the functions of lens 40. It is designed to collimate customer input 51 with provider input 52 to determine when a customer-provider match occurs. Figure 5A and Figure 5B The diagram shows that the synthetic database 53 contains all white pixel values ​​indicating a perfect match between the client and the provider.

[0058] Many aspects of provider input 52 can be similarly processed in provider device 62. Network 60 may include provider device 62 configured to communicate bidirectionally with network 60. Provider device 62 may digitally receive, store, and process provider input 52 in a provider computing device that includes at least provider processor 622 and provider storage device 621. Provider input 52 may include at least provider request data, provider access data, and provider scheduling data that are complementary to client input 51.

[0059] Provider device 52 can use a stored provider algorithm stored in provider storage to process provider input 52 in provider processor 622. The provider algorithm can be configured to transcode digital provider input received from a touchscreen, keyboard, or other provider input device into provider RGB formatted data. This transcoding can be performed directly on provider device 62 to give the provider input RGB-related security features that are applied to client input 51. Alternatively, digital provider input 52 can be forwarded to server 63 for RGB formatting and distribution in database array 64.

[0060] For explanation, provider request data may include red pixel value 0, green pixel value 0, and blue pixel value 255. Therefore, it can be said that provider request data includes red provider request data pixels, green provider request data pixels, and blue provider request data pixels. Provider access data may include red pixel value 0, green pixel value 77, and blue pixel value 153. Therefore, it can be said that provider access data includes red provider access data pixels, green provider access data pixels, and blue provider access data pixels. Provider scheduling data may include red pixel value 0, green pixel value 255, and blue pixel value 255. Therefore, it can be said that provider scheduling data includes red provider scheduling data pixels, green provider scheduling data pixels, and blue provider scheduling data pixels. Advantage data may include red pixel value 255, green pixel value 0, and blue pixel value 255. Language data may include red pixel value 255, green pixel value 255, and blue pixel value 0. The received RGB-formatted provider inputs 52 can be stored in provider data rows of separate provider databases 521, 522, 523 in storage device 62 of provider device 62, or the RGB-formatted provider inputs can be stored in provider data rows of database array 64 of network 60.

[0061] exist Figure 6A In this example, provider device 62 is configured to communicate with database array 64 via network 60. Provider device 62 is configured to transmit red provider request data pixels, red provider access data pixels, and red provider scheduling data pixels to the red data database RDB in database array 64 via the first network spectrum. That is, provider device 62 can be configured with various bidirectional communication tools. A communication cloud is typically shown at 65. Icons for various communication network spectrums are shown, including satellite, wireless such as 4G or 5G, laser, radar, and traditional wired. As a security measure for both provider device communication and client device communication, each data line transmitted over the network can be completed by client device 61 and provider device 62 on different network spectrums (fiber optic, telephone, wireless, WIFI, etc.). Alternatively, only one of the red, green, or blue lines may be transmitted on a different network spectrum, while the other two lines use the same network spectrum.

[0062] To continue this example, green provider request data pixels, green provider access data pixels, and green provider scheduling data pixels are sent to the green data database GDB in database array 64 on the second network spectrum. Blue provider request data pixels, blue provider access data pixels, and blue provider scheduling data pixels are sent to the blue data database BDB in database array 64 on the third network spectrum. Network 60 can be configured such that the first network spectrum is different from the second and third network spectra, and the second network spectrum is different from the third network spectrum.

[0063] Similarly, the database array can be configured to communicate bidirectionally with client device 61 via communication cloud 65 of network 60. Client device 61 can transmit RGB-formatted client input 51 to the red data database on the fourth network spectrum, to the green data database on the fifth network spectrum, and to the blue data database on the sixth network spectrum. The client network spectrum may differ from the provider network spectrum.

[0064] To find a match between a customer and a provider, the provider database array needs to be searched, either in the provider data rows of individual provider databases 521, 522, and 523 stored in storage device 621 of provider device 62, or in the provider data rows of database array 64 stored in network 60. The database array is also configured to communicate bidirectionally with client device 61 via communication cloud 65 of network 60. The client device can be configured to transmit customer input, which includes at least customer request data formatted in RGB to include red, green, and blue customer request data pixels; customer access data formatted in RGB to include red, green, and blue customer access data pixels; and customer scheduling data formatted in RGB to include red, green, and blue customer scheduling data pixels. In accordance with the aforementioned security measures, all red customer data pixels can be sent as a single stream, all green customer data pixels as a separate second stream, and all blue customer data pixels as a third separate stream. Each stream can be on a different network spectrum. The database array can be configured to compare client input with provider input to search the database array for complementary pixel values ​​that sum to white pixel values. Alternatively, pixel values ​​within a range can be searched.

[0065] The database array can also be configured to transmit provider input 52 as RGB formatted data to client device 61 when provider request data is in complementary RGB format to client request data, provider access data is in complementary RGB format to client access data, and provider scheduling data is in complementary RGB format to client scheduling data.

[0066] like Figure 2B As described, client device 51 receives a matching notification and displays a matching flag to the user. In the example, a sunburst flag is shown along with the number of returned matches. The user can tap to view the provider data. A checkmark can be used as a marker indicating that a match result has been reviewed. Once reviewed, a timer can be run. When the timer expires, storage device 61 is de-listed from the provider data associated with the match. However, if user device 61 receives acceptance data from the user indicating complementary provider request data, provider access data, and provider scheduling data, the customer acceptance data is forwarded to provider device 62. This constitutes a booking. Provider request data, provider access data, and provider scheduling data can be deleted from the database array because they are related to the booking. Many customer inputs 51 can be retained on the client device as a customer-specific security mechanism. Limited customer information (such as an initial deposit) can be sent to provider device 62 to confirm the booking at the provider. Personal identification information can be retained until the booking needs to be completed, such as during ticket collection, registration, or final sale.

[0067] Returning to the aspect of the synthesis database 53, it can be said that the client device 61 is configured to receive, store, and process network input within its computing device. The network input can be provider input, such as that forwarded via the communication cloud 65, whether directly from provider 62 or from the database array 64. The processor 612, including the synthesizer 613, can receive network input that includes at least provider request data, provider access data, and provider scheduling data. The client device 61 processes the network input within the client processor at the synthesizer 613. A client algorithm is configured to associate the network input with rows of provider data columns in the synthesis database 53, the rows of which include the RGB format of the network input. The synthesizer can synthesize the rows of client data columns with the rows of provider data columns, including collimating the RGB-formatted network input with the RGB-formatted client input to produce collimated pixel value rows. Collimated pixel value rows may be discarded if they include one or more pixel values ​​outside a predetermined range of pixel values ​​or if they include one or more non-white pixel values. The processor can display a matching marker on the client display device when the collimated pixel value row is collimated within a predetermined range via a client algorithm, or when the collimated pixel value row is collimated to all white pixel values.

[0068] In an alternative embodiment, client device 61 is also configured to receive, store, and process network input within its computing device. The network input may include transcoded RGB-formatted provider input, which includes at least provider request data, provider access data, and provider scheduling data. Transcoding occurs when the numerical representation of the user input is replaced with an RGB-formatted representation of pixel values. The client device processes the network input in client processor 612 using a client algorithm configured to transform the network input into rows of provider data columns in a synthetic database 53, the rows of which include the RGB format of the network input. The provider data rows include at least a red provider data row, a green provider data row, and a blue provider data row. Each of the provider request data, provider access data, and provider scheduling data includes pixel values ​​in rows of client data columns corresponding to each of the red, green, and blue client data rows. At least the request column receives each pixel value of the provider request data in RGB format, such that red provider request data pixels are stored in the red provider data row, green provider request data pixels are stored in the green provider data row, and blue provider request data pixels are stored in the blue provider data row. This alternative allows the client algorithm to also be configured to collimate the RGB formatted client request data column with the RGB formatted provider request data column to form collimated request data. The collimated request data can be discarded if it forms a non-white pixel value. Alternatively, when the collimated request data forms a white pixel value, the collimated request data can be stored and a matching marker can be displayed on the client display device. Similar to provider input data cleanup, the client algorithm can be configured to discard the stored collimated request data if no client-accepted marker is received. Alternatively, when the client inputs accepted data, the accepted data can be forwarded to network 60, and the client request data can be deleted from the request column.

[0069] As described above, client input can be stored in client databases 511-513 as RGB formatted on client device 61, and provider input can be stored in provider databases 521-523 as RGB formatted on provider device 62. Alternatively, database array 64 may include: a red data database RDB for storing red RGB formatted client input and red RGB formatted provider input; a green data database GDB for storing green RGB formatted client input and green RGB formatted provider input; and a blue data database BDB for storing blue RGB formatted client input and blue RGB formatted provider input. Regardless of the storage technology used, a network processor (such as server 63) can be configured to perform spectral shifting on database array 64 and on each of client databases 511-513 and provider databases 521-523. Spectral shifting may include adjusting the RGB formatted client input by a client spectral offset and adjusting the RGB formatted provider input by the opposite provider spectral offset. For example, each pixel value associated with the client input may be increased by 5, while each pixel value associated with the provider input may be decreased by 5. This could cause the client-requested data to change the red pixel value from 255 to 4, the green pixel value from 255 to 4, and the blue pixel value from 0 to 5. The provider-requested data could change the red pixel value from 0 to 251, the green pixel value from 0 to 251, and the blue pixel value from 255 to 250. Extrapolating this technique, the red pixel value can be changed by one spectral offset, the green pixel value can be changed by a different spectral offset, and the blue pixel value can be changed by a third different spectral offset.

[0070] Figure 6BNetwork device 160 is particularly useful for spectrum shifting technology. This network device 160 is configured for optical communication. It can be a client device or a provider device, and for simplicity, will be referred to as a user device. User input is readily formatted in RGB and stored in corresponding red database RDB, green database GDB, and blue database BDB in database array 164. Database array 164 can be internal to network device 160. Transmission synthesizer 163 combines user request data by collimating user request pixels RX1, GX1, and BX3 to produce a first pixel value 1. User access data produces a second pixel value 2 by collimating user access pixels RY1, GY2, and BY2. User scheduling data produces a third pixel value 3 by collimating scheduling data pixels RZ1, GZ2, and BZ2. Coupler 162 can convert the resulting first pixel value 1, second pixel value 2, and third pixel value 3 into transmittable optical values ​​that can be transmitted over an optical network, for example, via dense wavelength division multiplexing (DWDM) 161. Spectrum shifting techniques can be applied to pixels in a database array of 164 as easily as they can be applied to wavelengths transmitting the first to third pixel values ​​1-3. When combined with... Figure 9 When combined with these teachings, a particularly advantageous combination is created. Network device 160 can, for example, be used as part of the stadium seating arrangement for viewing device 9 and the provider. During the event, network device 160 can share the event with clients. After the event, devices with optical DWDM capabilities can form an optical communication network similar to a telecommunications cabinet within the event space. Now, the provider's viewing device 9 is a source of active revenue during the event and a source of passive telecommunications revenue when the venue is not in use.

[0071] Returning to the concept of a pixel spectrum, as described above, it can be selected from 16 million pixel values. Therefore, the client algorithm can be configured to transcode the client request data into RGB format by mapping the client request data to the request pixel spectrum and assigning request pixel values ​​from the request pixel spectrum. Upon receiving the client request data, at least frequency data and category data can be collected as coordinates for the mapping. As mentioned above, the frequency data can include the frequency at which the request will be fulfilled, and the category can be any enumerated category in Table 2, etc. A database of pixel values ​​associated with the provider's category can be assembled. Then, proportionally to alternative security measures, the request pixel spectrum can be shifted in its coordinates by a value equivalent to the wavelength, based on a shift timing. Very similar to the spectral shift discussed above, the database of provider request data can be adjusted to protect the provider request data, with a corresponding spectral shift of the client request data.

[0072] Figures 7A to 7CThis helps in understanding complementary pixel values ​​and spectral shifts, as they are related to the access (WHERE) data. The client algorithm can also be configured to transcode client access data to RGB format by mapping client access data to the access pixel spectrum and allocating access pixel values ​​from the access pixel spectrum. Figure 7A and Figure 7B In the example, an icosahedron is used as a tool to represent the Earth in a convenient coordinate system. If folded along the principal axis, the two-dimensional representation can be folded into a three-dimensional object, also known as a "Bucky sphere." Locations around the world are associated with the coordinate system, including the equator, the prime meridian, the North Pole, and the South Pole. The client geodesic matrix 71 includes a first color scheme. RGB pixel values ​​are clearly assigned globally, with 16 million options available. The provider geodesic matrix 72 has a complementary color scheme so that when a client requests access to a provider located at a specific location, the alignment of the location data (WHERE) produces white or near-white pixel values ​​from the collimation of the pixel values. This coordinate system also facilitates spectral shifting for the security of client and provider data.

[0073] exist Figure 7C In this design, a Cartesian coordinate system is used instead of an icosahedron. The Earth is now divided along the X, Y, and Z axes. Eight quadrants, Q1-Q8, are colored using RGB pixel values. This coordinate system also facilitates spectral shifting for the security of customer and provider data.

[0074] In two coordinate systems, icosahedral and Cartesian, the client can be mapped to RGB pixel values. The provider is then mapped to complementary RGB pixel values. Upon receiving client and provider access data, at least the location data of the user and provider can be collected, and this location data can be correlated with latitude and longitude data as the coordinates for mapping.

[0075] Just as we begin with time (WHEN), Figure 8A and Figure 8B Returning to the concept of time, like other data, scheduling data can be formatted in RGB. Client scheduling data can be transcoded to RGB format by mapping it to a scheduling pixel spectrum and assigning scheduling pixel values ​​from that spectrum. Figure 8A and Figure 8B The client scheduling pixel spectrum is shown. The provider scheduling pixel spectrum can be created by inverting the color scheme displayed in the key. This coordinate system also facilitates spectral shifting for the security of both client and provider data. When client scheduling data is received, at least one of the start time, stop time, and duration can be collected as additional coordinates for the mapping. Figure 2BAs shown, users can control the granularity of their 3Ws—5 minutes, 15 minutes, 1 hour, 5 miles, 15 meters, 1 block, 1 week, 2 months, and 1 year. The selected granularity affects the range of pixel values ​​applied to each coordinate system. Granularity can also affect the priority of the W selection (WHAT, WHERE, or WHEN).

[0076] Other implementations will be apparent to those skilled in the art upon consideration of the specification and the examples disclosed herein.

Claims

1. A network comprising: The client device is configured as follows: Perform bidirectional communication with the network; as well as The client computing device receives, stores, and processes client input, and the client computing device includes at least a client processor and a client storage device. The customer input includes at least customer request data, customer access data, and customer scheduling data that are digitally processed within the client computing device. The client device processes the client input in the client processor using a stored client algorithm from the client storage device. The stored client algorithm is configured to convert the client input into rows of client data columns in a synthetic database stored in the client storage device. The rows of the client data columns include the transcoded RGB format of the client input. The rows of the customer data column include at least red customer data rows, green customer data rows, and blue customer data rows, and Each of the customer request data, the customer access data, and the customer scheduling data includes pixel values ​​in the row of the customer data column corresponding to each of the red customer data row, the green customer data row, and the blue customer data row.

2. The network according to claim 1, wherein, The request column receives each of the pixel values ​​for RGB formatted customer request data, such that red customer request data pixels are stored in the red customer data row, green customer request data pixels are stored in the green customer data row, and blue customer request data pixels are stored in the blue customer data row.

3. The network according to claim 1, wherein: The client device is also configured to receive, store, and process network inputs within the client computing device, the network inputs including at least provider request data, provider access data, and provider scheduling data. The client device processes the network input in the client processor using the client algorithm, wherein the client algorithm is configured as follows: The network input is associated with a row in the provider data column of the synthesis database. The rows of the provider data column include the RGB format of the network input; The process of combining rows of the customer data column with rows of the provider data column includes collimating RGB-formatted network input with RGB-formatted customer input to generate collimated pixel value rows. as well as When the collimated pixel value row includes one or more pixel values ​​outside a predetermined range of pixel values, the collimated pixel value row is discarded; or When the collimated pixel value row is collimated within the predetermined range, the collimated pixel value row is stored and a matching mark is displayed on the client display device.

4. A network comprising: The client device is configured as follows: Perform bidirectional communication with the network; The client computing device receives, stores, and processes client input, and the client computing device includes at least a client processor and a client storage device. The client computing device receives, stores, and processes network inputs, which include at least provider request data, provider access data, and provider scheduling data. The client inputs include at least client request data, client access data, and client scheduling data that are digitally processed within the client computing device. The client device processes the client input in the client processor using a stored client algorithm from the client storage device. The stored client algorithm is configured to convert the client input into rows of client data columns in a synthetic database stored in the client storage device. The rows of the client data columns include the transcoded RGB format of the client input. The client device is configured to process the network input in the client processor using the client algorithm, wherein the client algorithm is configured as follows: The network input is associated with a row in the provider data column of the synthesis database, the row of the provider data column including the RGB format of the network input; The process of combining rows from the customer data column and rows from the provider data column includes collimating RGB-formatted network input with RGB-formatted customer input to generate collimated pixel value rows; and When the collimated pixel value row includes one or more non-white pixel values, the collimated pixel value row is discarded; or When the collimated pixel value row is aligned with all white pixel values, the collimated pixel value row is stored and the matching marker is displayed on the client display device.

5. The network according to claim 2, wherein: The client device is also configured to receive, store, and process network input within the client computing device, the network input including transcoded RGB-formatted provider input, which includes at least provider request data, provider access data, and provider scheduling data. The client device processes the network input in the client processor using the client algorithm, wherein the client algorithm is configured as follows: The network input is converted into rows of the provider data column in the synthesis database, the rows of which include the RGB format of the network input. The provider data column includes at least three rows: a red provider data row, a green provider data row, and a blue provider data row. Each of the provider request data, the provider access data, and the provider scheduling data includes pixel values ​​in the row of the provider data column corresponding to each of the red customer data row, the green customer data row, and the blue customer data row. The request column receives each of the pixel values ​​of the provider request data for RGB formatting, such that red provider request data pixels are stored in the red provider data row, green provider request data pixels are stored in the green provider data row, and blue provider request data pixels are stored in the blue provider data row.

6. The network according to claim 5, wherein, The client algorithm is also configured as follows: Align the columns of the RGB-formatted customer request data with the columns of the RGB-formatted provider request data to form aligned request data; When the collimation request data forms a non-white pixel value, the collimation request data is discarded; or When the collimation request data forms a white pixel value, the collimation request data is stored and a matching marker is displayed on the client display device.

7. The network according to claim 6, wherein, The client algorithm is also configured as follows: If no acceptance flag is received from the client, the stored collimation request data is discarded; or When the customer inputs acceptance data, the acceptance data is forwarded to the network, and the customer request data is deleted from the requested column.

8. The network of claim 2, further comprising a database array, which includes: A database for storing red data in red RGB formatted client input and red RGB formatted provider input; A green data database used to store green RGB formatted customer input and green RGB formatted provider input; as well as A blue data database used to store blue RGB formatted customer input and blue RGB formatted provider input.

9. The network according to claim 8, further comprising: A network processor configured to perform spectrum shifting on the database array, the spectrum shifting comprising: adjusting RGB-formatted client inputs by a client spectrum offset, and adjusting RGB-formatted provider inputs by the opposite provider spectrum offset.

10. The network according to claim 8, wherein, The database array is configured to communicate bidirectionally with the client device via the network, and wherein the client device receives RGB-formatted client input: The data is transmitted to the red data database via the first network spectrum. Transmitted to the green data database via the second network spectrum; and The data is transmitted to the Blue Data Database via the third network spectrum. Wherein, the spectrum of the first network is different from the spectrum of the second network and the spectrum of the third network, and The spectrum of the second network is different from that of the third network.

11. A network comprising: The client device is configured as follows: Perform bidirectional communication with the network; as well as The client computing device receives, stores, and processes client input, and the client computing device includes at least a client processor and a client storage device. The customer input includes at least customer request data, customer access data, and customer scheduling data that are digitally processed within the client computing device. The client device processes the client input in the client processor using a stored client algorithm from the client storage device. The stored client algorithm is configured to convert the client input into rows of client data columns in a synthetic database stored in the client storage device. The rows of the client data columns include the transcoded RGB format of the client input. The client algorithm is further configured as follows: The customer request data is transcoded into RGB format by mapping the customer request data to a request pixel spectrum and assigning request pixel values ​​from the request pixel spectrum. Receiving the customer request data includes: collecting at least frequency data and category data as coordinates for the mapping.

12. The network according to claim 11, wherein, The client algorithm is also configured to shift the requested pixel spectrum at its coordinates by a value equivalent to the wavelength, according to the shift timing.

13. A network comprising: The client device is configured as follows: Perform bidirectional communication with the network; as well as The client computing device receives, stores, and processes client input, and the client computing device includes at least a client processor and a client storage device. The customer input includes at least customer request data, customer access data, and customer scheduling data that are digitally processed within the client computing device. The client device processes the client input in the client processor using a stored client algorithm from the client storage device. The stored client algorithm is configured to convert the client input into rows of client data columns in a synthetic database stored in the client storage device. The rows of the client data columns include the transcoded RGB format of the client input. The client algorithm is further configured as follows: By mapping the customer access data to an access pixel spectrum and allocating access pixel values ​​from the access pixel spectrum, the customer access data is transcoded into RGB format. Receiving the customer access data includes: at least collecting location data, and associating the location data with latitude and longitude data as coordinates for the mapping.

14. A network comprising: The client device is configured as follows: Perform bidirectional communication with the network; as well as The client computing device receives, stores, and processes client input, and the client computing device includes at least a client processor and a client storage device. The customer input includes at least customer request data, customer access data, and customer scheduling data that are digitally processed within the client computing device. The client device processes the client input in the client processor using a stored client algorithm from the client storage device. The stored client algorithm is configured to convert the client input into rows of client data columns in a synthetic database stored in the client storage device. The rows of the client data columns include the transcoded RGB format of the client input. The client algorithm is further configured as follows: The client scheduling data is transcoded into RGB format by mapping the client scheduling data to a scheduling pixel spectrum and allocating scheduling pixel values ​​from the scheduling pixel spectrum. Receiving the customer scheduling data includes collecting at least one of the start time, stop time, and duration as coordinates for the mapping.

15. The network according to claim 1, comprising: The provider device is configured as follows: Perform bidirectional communication with the network; as well as The provider computing device digitally receives, stores, and processes provider input, and the provider computing device includes at least a provider processor and a provider storage device. The provider input includes at least provider request data, provider access data, and provider scheduling data; and Database array; The provider device processes the provider input in the provider processor using a stored provider algorithm stored in the provider storage device. The provider algorithm is configured to transcode the provider input into provider RGB formatted data such that: The provider request data includes red provider request data pixels, green provider request data pixels, and blue provider request data pixels; The provider access data includes red provider access data pixels, green provider access data pixels, and blue provider access data pixels; and The provider scheduling data includes red provider scheduling data pixels, green provider scheduling data pixels, and blue provider scheduling data pixels. The database array is configured to compare the client input with the provider input to search for complementary pixel values ​​in the database array that sum to white pixel values.

16. The network of claim 15, further comprising a database array, wherein, The provider device is configured to communicate with the database array via the network, and wherein the provider device is configured to: The red provider request data pixel, the red provider access data pixel, and the red provider scheduling data pixel are transmitted to the red data database in the database array via the first network spectrum; The green provider request data pixel, the green provider access data pixel, and the green provider scheduling data pixel are transmitted to the green data database in the database array via the second network spectrum; and The blue provider request data pixel, the blue provider access data pixel, and the blue provider schedule data pixel are transmitted in the third network spectrum to the blue data database in the database array; Wherein, the spectrum of the first network is different from the spectrum of the second network and the spectrum of the third network, and The spectrum of the second network is different from that of the third network.

17. The network according to claim 16, wherein, The database array is further configured to communicate bidirectionally with client devices via the network, and wherein the client devices are configured to transmit client input, the client input including at least: Client request data formatted in RGB to include red client request data pixels, green client request data pixels, and blue client request data pixels; Client access data formatted in RGB format, including red client access data pixels, green client request data pixels, and blue client request data pixels; and Client scheduling data formatted in RGB to include red, green, and blue client scheduling data pixels; and The database array is configured to compare the client input with the provider input to search for complementary pixel values ​​in the database array that sum to white pixel values.

18. The network according to claim 17, wherein, The database array is also configured to transmit the provider input to the client device in the following situations: The provider request data is a complementary RGB format of the customer request data; The provider access data is a complementary RGB format to the customer access data; and The provider scheduling data is a complementary RGB format to the client scheduling data.

19. The network according to claim 18, wherein, When the client device receives acceptance data indicating complementary provider request data, provider access data, and provider scheduling data, the acceptance data is forwarded to the provider device, and the provider request data, provider access data, and provider scheduling data are deleted from the database array.

Images