CN112131017B

CN112131017B - Interface design method for calendar service

Info

Publication number: CN112131017B
Application number: CN202010976528.8A
Authority: CN
Inventors: 黄政
Original assignee: Beijing Zhidemai Technology Co ltd
Current assignee: Beijing Zhidemai Technology Co ltd
Priority date: 2020-09-15
Filing date: 2020-09-15
Publication date: 2024-06-14
Anticipated expiration: 2040-09-15
Also published as: CN112131017A

Abstract

The invention discloses an interface design method of calendar service, comprising the following steps: analyzing a message for a calendar function in an abstract rfc5545 protocol; converting the message of the calendar function abstracted by the S1, and replacing the message by a json format; the Token authentication mode based on JWT is used for replacing the existing http+basic interface authentication mode; exposing a new restful interface style; each type of client uses the calendar service interface according to the new interface style; the invention uses protocol simplification as a core, simplifies the complex rfc5545 message protocol into json format to express, and greatly improves the access convenience of calendar service; the http stateless distributed technology is used, so that the stability and reliability of the whole system are greatly ensured, and meanwhile, the http stateless distributed system can be easily handled in the aspects of horizontal capacity expansion and capacity reduction.

Description

Interface design method for calendar service

Technical Field

The invention relates to the technical field of computer networks, in particular to an interface design method of calendar service.

Background

With the development of internet technology, online office work and mobile office work are also becoming popular. As an indispensable module of an office OA system, the calendar provides very convenient functions, such as various event reminding, alarm clock, travel setting and the like. There is an increasing demand for calendar services by various systems outside and inside the enterprise. The design of the calendar service interface is particularly important for more efficient, more convenient and safer access to the calendar service.

Existing calendar service design-like technologies also provide interfaces in compliance with the rfc5545 protocol specification, windows, mac, iOS, and android, and various calendar clients of mail need to interface with the calendar service in compliance with the aforementioned protocols.

The method for presenting the calendar with the publication number of CN104408607B comprises the following steps: acquiring a user name; updating a database according to the user name, establishing a longitudinal month time axis, a week time axis and a year time axis, and displaying the week time axis of the current week in a display window; switching a month time axis, a week time axis and a year time axis by rotating the time axis; the system event interface generated by pushing the user event interface and the Internet remote server is arranged. The design of a longitudinal time axis is adopted, and month, week and day time are adopted in a fulcrum way, so that compared with the calendar in the current table form, the calendar has good user embodiment; user events and system events generated by pushing by an Internet remote server are set in the calendar.

The creation of calendars using the rfc5545 protocol specification described in the above manner is not very developer friendly, updating and deleting calendars, and the obsolete messaging protocol presents a significant impediment to systems requiring calendar services in the current state of the art. Meanwhile, the method is a comparatively simple http+basic mode in the aspect of security authentication. Hidden danger is brought to the stability of the calendar service system.

Disclosure of Invention

The embodiment of the invention provides an interface design method of calendar service. The following presents a simplified summary in order to provide a basic understanding of some aspects of the disclosed embodiments. This summary is not an extensive overview and is intended to neither identify key/critical elements nor delineate the scope of such embodiments. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

According to an embodiment of the present invention, there is provided an interface design method for calendar service, including:

S1: analyzing a message for a calendar function in an abstract rfc5545 protocol;

S2: converting the message of the calendar function abstracted by the S1, and replacing the message by a json format;

s3: the Token authentication mode based on JWT is used for replacing the existing http+basic interface authentication mode;

S4: exposing a new restful interface style;

S5: the types of clients use the calendar service interface according to the new interface style.

Preferably, the analysis abstracts the rfc5545 protocol: according to the rfc5545 protocol, a four-layer data structure may be abstracted, calendar attribution, calendar attributes, and time attributes.

Preferably, the four-layer data structure can abstract the following three models, namely a calendar model, a schedule model schedule and a time model.

Preferably, the calendar attribution comprises, creating a calendar and deleting a calendar.

Preferably, the schedule includes newly adding a schedule, modifying a schedule, and deleting a schedule.

Preferably, the schedule attribute includes a schedule name, a location, a time, an invitee, notes, and url, an accessory.

Preferably, the time attributes include a start time, an end time, a repetition, a travel time, and a reminder.

Preferably, the JWT is a string, and is composed of payload, header, and signature, where payload and header are spliced together after base64, and then encrypted by HS256 algorithm to generate signature.

The technical scheme provided by the embodiment of the invention can have the following beneficial effects:

(1) The invention uses protocol simplification as a core, and simplifies the complex rfc5545 message protocol into json format for expression. The access convenience of calendar service is greatly improved. In current mobile offices, the various calendar clients involved can be accessed quickly.

(2) The invention ensures the stability of the interface using calendar service through the adjustment of the security authentication strategy.

(3) The invention uses http stateless distributed technology, and the stability and reliability of the whole system are greatly ensured. Meanwhile, the horizontal expansion and contraction can be easily handled.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention as claimed.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.

FIG. 1 is a flow diagram illustrating a method of interface design for a calendar service according to an exemplary embodiment;

FIG. 2 is a schematic diagram of an analysis abstraction process flow, shown in accordance with an example embodiment;

FIG. 3 is a block diagram of an interface design method for a calendar service, shown in accordance with an exemplary embodiment;

FIG. 4 is a diagram illustrating a jwt character string component structure, according to one example embodiment;

Detailed Description

The following description and the drawings sufficiently illustrate specific embodiments of the invention to enable those skilled in the art to practice them. The embodiments represent only possible variations. Individual components and functions are optional unless explicitly required, and the sequence of operations may vary. Portions and features of some embodiments may be included in, or substituted for, those of others. The scope of embodiments of the invention encompasses the full ambit of the claims, as well as all available equivalents of the claims. Embodiments may be referred to herein, individually or collectively, by the term "invention" merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed. Various embodiments are described herein in a progressive manner, each embodiment focusing on differences from other embodiments, and identical and similar parts between the various embodiments are sufficient to be seen with each other. The structures, products and the like disclosed in the embodiments correspond to the parts disclosed in the embodiments, so that the description is relatively simple, and the relevant parts refer to the description of the method parts.

It should be noted that: the relative arrangement of the components and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless it is specifically stated otherwise.

It should be noted that although the steps of the methods of the present disclosure are illustrated in a particular order in the figures, this does not require or imply that the steps must be performed in that particular order or that all of the illustrated steps must be performed in order to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform, etc.

The invention is further described below with reference to the accompanying drawings and examples:

a method of interface design for a calendar service, as shown in fig. 1 and 3, includes,

S4: exposing a new restful interface style;

According to the above scheme, further, as shown in fig. 2, the analysis abstract rfc5545 protocol: according to the rfc5545 protocol, a four-layer data structure may be abstracted, calendar attribution, calendar attributes, and time attributes.

According to the scheme, the four-layer data structure can abstract the following three models, namely a calendar model, a schedule model schedule and a time model, perform mutual conversion from a complex protocol message to a simple protocol, express the three data models by json data format and then convert the data models into rfc5545 protocol for storage.

According to the scheme, further, the calendar attribution comprises creating a calendar and deleting the calendar; the schedules comprise newly-added schedules, modified schedules and deleted schedules; the schedule attribute comprises a schedule name, a position, time, invitees, notes and url and accessories; the time attributes include, start time, end time, repetition, travel time, and reminder.

According to the above scheme, further, in the http+basic mode, the user name and the password are stored in the message header after passing through the base64, so that hidden danger is brought to sensitive information leakage, as shown in fig. 4, the JWT is a character string and consists of payload, header and signature, the payload and the header are spliced together after passing through the base64, and then the signature is generated by the HS256 algorithm encryption, so that the interface is sufficiently safe and stable.

It is to be understood that the invention is not limited to the arrangements and instrumentality shown in the drawings and described above, and that various modifications and changes may be made without departing from the scope thereof. The scope of the invention is limited only by the appended claims.

Claims

1. A method for designing an interface of a calendar service, comprising,

S1: the analysis abstract rfc5545 protocol message for calendar functions includes: according to the rfc5545 protocol, a four-layer data structure, calendar attribution, schedule attribute and time attribute are abstracted, wherein the four-layer data structure abstracts the following three models, namely a calendar model, a schedule model schedule and a time model;

The calendar attribution comprises, creating a calendar and deleting the calendar;

The schedules comprise newly-added schedules, modified schedules and deleted schedules;

s2: converting the calendar function abstracted in the step S1 into a message, replacing the message with a json format, and converting the message into an rfc5545 protocol for storage;

S4: exposing a new restful interface style;

2. The interface design method of calendar service according to claim 1, wherein the calendar attribute includes calendar name, location, time, invitees, notes and url, attachment.

3. The interface design method of calendar service according to claim 1, wherein the time attributes include a start time, an end time, a repetition, a travel time, and a reminder.

4. The interface design method of calendar service according to claim 1, wherein the JWT is a string composed of payload, header, and signature, and the payload and header are spliced together after base64 and then encrypted by HS256 algorithm to generate the signature.