Class Notebook API Guest Access Link Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing classroom notebook applications lack efficient mechanisms for managing permissions and providing guest access to specific sections of a class notebook, making it difficult for teachers to share student work with parents or guardians without compromising the security of the entire notebook.

Innovation Solution

The implementation of application programming interfaces (APIs) that allow teachers to generate guest access links for specific student sections, enabling read-only access without authentication, and manage permissions through post, get, and delete APIs for section groups, thereby controlling access to individual student content within the class notebook.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If guest access link is provided for student content, then accessibility for parents/guardians is improved, but security control over specific sections becomes more complex

Engineering Contradiction:
Improveaccessibility for parents/guardiansVSAvoidpermission management complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system segments the class notebook into distinct section groups, each representing a specific student's content. Guest access links can be generated for individual section groups rather than the entire notebook, allowing granular control over what content parents or guardians can view. This segmentation enables selective sharing of student work while maintaining security over other sections.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism (guest access link system) that mediates between the need for easy parent access and security requirements. The guest link acts as a controlled gateway that provides read-only access to specific section groups without compromising the overall notebook security structure or requiring full authentication for guests.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If read-only access is provided without authentication, then ease of access for guests is improved, but security control over notebook content deteriorates

Engineering Contradiction:
Improveguest access convenienceVSAvoidsecurity control
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system divides the notebook content into separate section groups, each with its own guest access link. This segmentation allows read-only access to be granted conveniently to specific students' content while maintaining security control at the section level rather than requiring comprehensive authentication for the entire notebook.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different security qualities are applied to different section groups. Each section group can have its own permission settings, allowing the teacher to designate certain sections as accessible to guests with read-only permissions while maintaining stricter security controls on other sections. This local quality approach enables tailored security for different content areas.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If permission management is implemented at section group level, then fine control over student content is improved, but system complexity increases

Engineering Contradiction:
Improvefine control over student contentVSAvoidpermission management system
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system organizes notebook content into section groups that correspond to individual students or specific content categories. This segmentation structure enables fine-grained permission control where teachers can manage access to each section group independently through dedicated APIs, providing adaptability for different sharing scenarios while maintaining a manageable organizational structure.

Inventive Principle:
Principle #1Segmentation

4Shape

If class notebook is structured with section groups for individual students, then content organization is improved, but access management complexity increases

Engineering Contradiction:
Improvenotebook structure organizationVSAvoidaccess management structure
Core Design Contradiction:
ShapeVSDevice complexity

Solution Approach 1:

The class notebook is segmented into section groups, where each section group represents a specific student's content or a particular content category. This segmentation improves content organization and makes it easier to manage access on a per-section basis rather than treating the entire notebook as a single unit, thereby balancing structural organization with manageable access control.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11468190B2Application programming interfaces for notebook settings
Publication Date: 2022.10.11 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11468190B2 patent drawing
  • US11468190B2 patent drawing
  • US11468190B2 patent drawing

AI summary

Application programming interfaces (API) are provided for notebook settings, for example, classroom notebook settings. The APIs allow for a teacher or other user of a class notebook to manage permissions to the class notebooks, and particularly allow for fine control over parts of the class notebook through a class notebook application. An API for generating a guest access link is provided. APIs for creating permission groups for a collaboration space are provided. A post permission API is provided that creates or updates the permission for a section group. A get permission API is provided that retrieves permission information of a section group. A delete permission API is provided that removes permission for a user of a section group.