CN110830412A

CN110830412A - Method and server for sharing membership permission

Info

Publication number: CN110830412A
Application number: CN201810889770.4A
Authority: CN
Inventors: 刘辽谱
Original assignee: Beijing Youku Technology Co Ltd
Current assignee: Alibaba China Co Ltd
Priority date: 2018-08-07
Filing date: 2018-08-07
Publication date: 2020-02-21
Anticipated expiration: 2038-08-07
Also published as: CN110830412B

Abstract

The embodiment of the application discloses a method and a server for sharing membership rights, wherein the method comprises the following steps: receiving a permission sharing request pointing to a second account sent by a client logging in a first account; the permission sharing request comprises the appointed membership permission of the first account; and canceling the appointed membership right of the first account, and adding the appointed membership right to the second account. The technical scheme provided by the application can enable the non-member user to fully enjoy the membership permission.

Description

Method and server for sharing membership permission

Technical Field

The present application relates to the field of internet technologies, and in particular, to a method and a server for sharing membership rights.

Background

With the rapid development of computer technology and internet technology, various applications on the internet bring great convenience to the life of people. To guide users to become members, these applications typically provide users who have become members with some membership rights, for example, rights to view certain videos or certain electronic books, rights to remove advertisements before video playback, rights to accumulate and use points, and so on. These membership rights typically require the user to pay a fee and become a member before they can be enjoyed.

At present, the methods for applying and popularizing the members are mainly popularized in a mode of trial activities of the members. For example, during a member trial activity, a non-member user may watch video for a certain period of time in video watched only by a member for free, or may enjoy designated member rights for short for free, and the like. However, the way in which the member tries usually results in limitations when the user enjoys the member rights, and the user cannot fully experience the benefits of the member rights. If a user is allowed to pay a fee to become a member in such a situation, most potential users may be given up to become members.

Disclosure of Invention

An object of the present invention is to provide a method and a server for sharing membership rights, which enable a non-member user to fully enjoy the membership rights.

In order to achieve the above object, the present application further provides a method for sharing membership rights, which is provided with; the method comprises the following steps: receiving a permission sharing request pointing to a second account sent by a client logging in a first account; the permission sharing request comprises the appointed membership permission of the first account; and canceling the appointed membership right of the first account, and adding the appointed membership right to the second account.

To achieve the above object, the present application provides a server, which includes a memory and a processor, wherein the memory is used for storing a computer program; the computer program, when executed by the processor, implements the steps of: receiving a permission sharing request pointing to a second account sent by a client logging in a first account; the permission sharing request comprises the appointed membership permission of the first account; and canceling the appointed membership right of the first account, and adding the appointed membership right to the second account.

As can be seen from the above, in the technical scheme provided by the application, the first user can send the permission sharing request pointing to the second account to the server through the client logged in with the first account. Wherein the second account number corresponds to a second user. Since the permission sharing request includes the designated member permission of the first account, after the permission sharing request is received, the server may directly cancel the designated member permission of the first account and add the designated member permission to the second account, so that the designated member permission of the first account is shared with the second account. In this way, although the second user is not a member user, that is, the second account does not have a member right, the second user can still fully enjoy the member right shared by the first user without being limited by the member trial activities, so that the potential user can be developed into a member.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

FIG. 1 is a flow chart of a method for sharing membership rights in an embodiment of the present application;

FIG. 2 is a schematic diagram of an application scenario of a method for sharing membership rights in an embodiment of the present application;

fig. 3 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art without any inventive work based on the embodiments in the present application shall fall within the scope of protection of the present application.

The embodiment of the application provides a method for sharing membership rights, which can be applied to system architectures of a client and a server. The client may be an electronic device for logging in account information of a user. Specifically, the client may be, for example, a desktop computer, a tablet computer, a notebook computer, a smart phone, a digital assistant, a smart wearable device, a television with a network access function, and the like. Alternatively, the client may be software capable of running in the electronic device. The client may also be software capable of running in the electronic device. Specifically, the client may be a mobile application in the electronic device, and the mobile application may be, for example, an arcade, a fox search video, an Tencent video, Acfun, iReader, or the like.

In this embodiment, the server may be a device that stores account information and member authority data. Specifically, the server may be an electronic device having data operation, storage function and network interaction function; software may also be provided that runs in the electronic device to support data processing, storage, and network interaction. The number of servers is not particularly limited in the present embodiment. The server may be one server, several servers, or a server cluster formed by several servers.

The embodiment of the application provides a method for sharing membership rights, which can be applied to the server. Referring to fig. 1, the method for sharing membership rights may include the following steps.

S11: receiving a permission sharing request pointing to a second account sent by a client logging in a first account; the permission sharing request comprises the appointed membership permission of the first account.

In this embodiment, the server may be provided with account information of different accounts and member authority data corresponding to the different accounts. The account information and the member authority data may be disposed on a storage medium in a server. Wherein, the member authority data may include member authority and type of member authority. For example, the member authority may be an authority to watch some videos or some electronic books, an authority to remove advertisements before video playing, an authority to accumulate and use points, and the like within a specified authority duration. Accordingly, the types of the member authority may be a video viewing type, an e-book viewing type, an advertisement removal type, a point type, and the like.

In this embodiment, the first account and the second account may refer to accounts within an application used by the first user and the second user, respectively. Specifically, for example, the application used by the user may be an arcade, a fox search video, an Tencent video, Acfun, iReader, or the like. The account information may include a nickname used by the user on the application, a registered account and a mobile phone number, and a corresponding login password.

In this embodiment, the first account may have at least one member authority. The second account may not have membership rights, or may have at least one membership right.

In this embodiment, the client may display a sharing control associated with the designated membership right. The sharing control can be a text control or a picture control. The first user can call a friend address book by clicking the sharing control, select account information such as a nickname and a mobile phone number of the second account, or call a camera, scan a two-dimensional code associated with the second account and displayed on another client, and then can send a permission sharing request pointing to the second account to the server.

In this embodiment, the indication that the permission sharing request is directed to the second account may indicate that the permission sharing request carries an identifier of the second account. In this way, after receiving the permission sharing request, the server may extract the identifier of the second account from the permission sharing request. After the identifier of the second account is extracted, the server may read account information of the second account having the identifier, so that a member right can be subsequently shared with the second account.

In this embodiment, the permission sharing request may be a character string written according to a preset rule. Wherein the preset rule may be a network communication protocol followed between the client and the server. For example, the rights sharing request may be a string written according to the HTTP protocol.

In this embodiment, the permission sharing request may include a designated member permission of the first account. The designated member authority may be any one of at least one member authority possessed by the first account, or a member authority which the first user selects on the client and wishes to share with the second user. In this way, after receiving the permission sharing request, the server can share the designated member permission of the first account to the second account.

S13: and canceling the appointed membership right of the first account, and adding the appointed membership right to the second account.

In this embodiment, in order to share the member right of the first account with the second account, after receiving the right sharing request, the server may cancel the designated member right of the first account and add the designated member right to the second account. Therefore, the member authority of the first account can be shared with the second account, and the sum of the member authorities of the first account and the second account is ensured to be unchanged. In this way, even though the second account does not have the membership right, that is, the second user is not the member user, the second user can still fully enjoy the membership right shared by the first user.

In a specific application scenario, the client may be a smart phone, and the application logged on the client may be an Tencent video application. For example, as shown in fig. 2, the first user may log into the first account within an Tencent video application on the smartphone. After the first user logs in the first account, a plurality of member permissions of the first account, namely member permission 1, member permission 2, member permission … and member permission n, can be displayed on the smart phone, and correspondingly, a sharing control 1, a sharing control 2, a sharing control … and a sharing control n which are respectively associated with each member permission can be displayed. At this time, if the first user wishes to share the member permission 1 with the second account corresponding to the second user, the sharing control 1 may be clicked, the friend address book may be called, and the nickname "wang XX" corresponding to the second account may be selected from the friend address book, so that a permission sharing request pointing to the second account may be sent to the server. The permission sharing request comprises member permission 1 of the first account. After receiving the permission sharing request, the server may cancel the member permission 1 of the first account, and add the member permission 1 to the second account. In this way, although the second account does not have the membership right, that is, the second user is not the member user, the second user can still fully enjoy the membership right shared by the first user without being limited by the member trial activities.

In an embodiment of the application, a plurality of membership rights of one account can be shared with a plurality of accounts respectively. Specifically, the first account has at least two membership rights. The method may further comprise: the server can receive a permission sharing request pointing to at least two accounts sent by a client logged in with a first account; the permission sharing request comprises at least two membership permissions of the first account; after receiving the permission sharing request, the server may cancel at least two member permissions of the first account and assign the at least two member permissions of the first account to the at least two accounts. And the account pointed by the authority sharing request is distributed with at least one member authority. For example, the first account has four kinds of membership rights, i.e., membership right 1, membership right 2, membership right 3, and membership right 4. The user can click a sharing control 1 and a sharing control 2 related to the member authority 1 and the member authority 2 on the client respectively, an account A is selected from a friend address list called by the sharing control 1, an account B is selected from a friend address list called by the sharing control 2, and an authority sharing request pointing to the account A and the account B can be sent to the server, wherein the authority sharing request comprises the member authority 1 and the member authority 2 of a first account. After receiving the permission sharing request, the server may cancel the member permission 1 and the member permission 2 of the first account, and add the member permission 1 and the member permission 2 to the account a and the account B, respectively. Therefore, the plurality of member authorities of the first account can be shared with the plurality of accounts respectively.

In an embodiment of the application, after the member authority of the first account is shared, the member authority can be recovered to the first account. Specifically, after canceling the designated membership right of the first account and adding the designated membership right to the second account, the method may further include: the server can receive an authority recovery request pointing to the designated membership authority sent by a client logged in with a first account; since the designated member right is shared by the first account to the second account, after receiving the right recovery request, the server may cancel the designated member right of the second account and add the designated member right to the first account. Therefore, even if the member authority of the first account is shared, the member authority can still be recovered to the first account.

In an embodiment of the application, the server may preset that the membership rights of certain membership right types are allowed to be recovered or not allowed to be recovered after being shared. Specifically, after receiving a permission recovery request directed to the designated membership permission from a client logged in with a first account, the method may further include: the server can judge whether the type of the designated membership authority belongs to a preset membership authority type; and if the permission request belongs to the permission recovery request, feeding back rejection information aiming at the permission recovery request to the client. The preset member authority type can be one member authority type or multiple member authority types, and can be specifically set according to the member level of the account.

In one embodiment of the present application, the server may further split the membership right into a plurality of sub-membership rights. Specifically, the designated membership rights are associated with a length of rights. Before receiving a permission sharing request directed to a second account from a client logged in with a first account, the method may further include: the server can receive an authority splitting request which is sent by a client logged in with a first account and points to appointed membership authority; the permission splitting request comprises splitting information associated with permission duration; the splitting information may specifically be a time splitting node in the permission time period of the designated membership permission; after receiving the permission splitting request, the server may split the designated membership permission into at least two sub-membership permissions based on the splitting information. Wherein, the total duration of the at least two sub-member authorities is the same as the duration of the designated member authority. For example, the authority time period of the designated member authority of the first account is from 6/1/2018 to 5/30/2019, the authority duration is one year, the splitting information may be an intermediate time node in the authority time period, and at this time, after receiving the authority splitting request, the server may split the designated member authority into two sub-member authorities at the intermediate time node in the authority time period. Wherein, the authority duration of the two sub-member authorities is half a year.

In this embodiment, after splitting the member authority into a plurality of sub-member authorities, the server may further share the plurality of sub-member authorities with a plurality of accounts. Specifically, after splitting the designated membership right into at least two seed membership rights, the method may further include: the server can receive a permission sharing request pointing to at least two accounts sent by a client logged in with a first account; the authority sharing request comprises at least two seed member authorities of the first account; after receiving the permission sharing request, the server may cancel at least two seed membership permissions of the first account, and allocate the at least two seed membership permissions of the first account to the at least two accounts; and the account pointed by the authority sharing request is distributed with at least one sub-member authority. Therefore, under the condition that the number of the member rights of the first account is limited, the member rights can be divided into a plurality of sub-member rights to be shared by a plurality of accounts.

In an embodiment of the application, in an actual application process, a server may receive permission sharing requests sent by a plurality of clients and directed to the same account, and in the permission sharing requests, at least two permission sharing requests include the same member permission, and permission durations of the same member permission are different. In this case, when the server shares the same member rights with the same account, there is a conflict. To avoid this, the method may further comprise the following steps.

S21: respectively receiving authority sharing requests pointing to target accounts sent by at least two clients; wherein at least two of the permission sharing requests comprise the same member permission; the authority durations of at least two identical member authorities are different.

In this embodiment, the same member authority may refer to member authorities of the same member authority type, for example, the member authority types of the three same member authorities are all video viewing types, but the authority durations are different, and are respectively one month, three months and half a year.

S23: and determining the appointed membership right with the longest permission duration and the appointed account number logged in the corresponding client from the at least two same membership rights.

S25: and canceling the appointed membership right of the appointed account number, and adding the appointed membership right to the second account number.

For example, after receiving permission sharing requests directed to a target account sent by three clients, the three permission sharing requests all include one same member permission, which is a member permission 1, a member permission 2 and a member permission 3, the member permission types of the three same member permissions are all video viewing types, and the permission durations are one month, three months and half a year respectively. The server can determine the member authority 3 with the longest authority duration and the account number logged in on the corresponding client from the three same member authorities. After determining the account, the server may cancel the member authority 3 of the account and add the member authority 3 to the second account.

In an embodiment of the application, when sharing the membership rights, the sharing duration can be selected, so that the membership rights sharing mode can be flexibly selected. Specifically, the designated membership rights are associated with a length of rights. The permission sharing request can also comprise sharing duration. And the sharing duration is less than the authority duration of the appointed membership authority. After receiving a permission sharing request directed to a second account from a client logged in with a first account, the method may further include: the server can cancel the designated membership right of the first account and add the designated membership right to the second account; after the sharing duration, the server may cancel the designated membership right of the second account and add the designated membership right to the first account. For example, the permission duration of the designated member permission is half a year, and the sharing duration may be set to one month, so that the server may return the designated member permission from the second account to the first account after the time for sharing the designated member permission of the first account with the second account reaches one month.

In this embodiment, the functions implemented in the above method steps may be implemented by a computer program, and the computer program may be stored in a computer storage medium. In particular, the computer storage medium may be coupled to a processor, which may thereby read the computer program from the computer storage medium. The computer program, when executed by a processor, may implement the steps of:

s11: receiving a permission sharing request pointing to a second account sent by a client logging in a first account; the permission sharing request comprises the appointed membership permission of the first account;

In one embodiment, the first account has at least two membership rights; the computer program, when executed by a processor, further implements the steps of:

receiving a permission sharing request pointing to at least two accounts sent by a client logged in with a first account; the permission sharing request comprises at least two membership permissions of the first account;

canceling at least two kinds of membership rights of the first account, and distributing the at least two kinds of membership rights of the first account to the at least two accounts; and the account pointed by the authority sharing request is distributed with at least one member authority.

In one embodiment, the computer program, when executed by a processor, further performs the steps of:

receiving an authority recovery request pointing to the appointed membership authority sent by a client logging in a first account;

and canceling the appointed membership right of the second account, and adding the appointed membership right to the first account.

judging whether the type of the appointed membership authority belongs to a preset membership authority type or not; and if the permission request belongs to the permission recovery request, feeding back rejection information aiming at the permission recovery request to the client.

In one embodiment, the specified membership rights are associated with a length of rights; the computer program, when executed by a processor, further implements the steps of:

receiving an authority splitting request pointing to appointed membership authority sent by a client logging in a first account; the permission splitting request comprises splitting information associated with permission duration;

splitting the designated membership right into at least two sub-membership rights based on the splitting information; wherein, the total duration of the at least two sub-member authorities is the same as the duration of the designated member authority.

receiving a permission sharing request pointing to at least two accounts sent by a client logged in with a first account; the authority sharing request comprises at least two seed member authorities of the first account;

canceling at least two seed membership rights of the first account, and distributing the at least two seed membership rights of the first account to the at least two accounts; and the account pointed by the authority sharing request is distributed with at least one sub-member authority.

respectively receiving authority sharing requests pointing to target accounts sent by at least two clients; wherein at least two of the permission sharing requests comprise the same member permission; the authority durations of at least two same member authorities are different;

determining a designated member authority with the longest authority duration and a designated account number logged in a corresponding client from the at least two same member authorities;

and canceling the appointed membership right of the appointed account number, and adding the appointed membership right to the second account number.

In one embodiment, the specified membership rights are associated with a length of rights; the permission sharing request further comprises sharing duration; the sharing duration is less than the authority duration of the designated member authority; the computer program, when executed by a processor, further implements the steps of:

canceling the appointed membership permission of the first account, and adding the appointed membership permission to the second account;

and after the sharing duration, canceling the designated membership permission of the second account, and adding the designated membership permission to the first account.

It should be noted that, the functions that can be realized by the computer program in the computer storage medium can all refer to the foregoing method implementation embodiments, and the technical effects achieved are also similar to the technical effects achieved in the foregoing method implementation embodiments, and are not described here again.

Referring to fig. 3, the present application further provides a server. The server comprises a memory and a processor, the memory being operable to store a computer program and; the computer program, when executed by the processor, implements the steps of:

In this embodiment, the memory may include a physical device for storing information, and typically, the information is digitized and then stored in a medium using an electrical, magnetic, or optical method. The memory according to this embodiment may further include: devices that store information using electrical energy, such as RAM, ROM, etc.; devices that store information using magnetic energy, such as hard disks, floppy disks, tapes, core memories, bubble memories, usb disks; devices for storing information optically, such as CDs or DVDs. Of course, there are other ways of memory, such as quantum memory, graphene memory, and so forth.

In this embodiment, the processor may be implemented in any suitable manner. For example, the processor may take the form of, for example, a microprocessor or processor and a computer-readable medium that stores computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, an embedded microcontroller, and so forth.

In one embodiment, the first account has at least two membership rights; the computer program, when executed by the processor, further implements the steps of:

In one embodiment, the computer program, when executed by the processor, further implements the steps of:

In one embodiment, the specified membership rights are associated with a length of rights; the computer program, when executed by the processor, further implements the steps of:

In one embodiment, the specified membership rights are associated with a length of rights; the permission sharing request further comprises sharing duration; the sharing duration is less than the authority duration of the designated member authority; the computer program, when executed by the processor, further implements the steps of:

The specific functions implemented by the memory and the processor of the server provided in the embodiments of the present specification may be explained in comparison with the foregoing embodiments in the present specification, and can achieve the technical effects of the foregoing embodiments, and thus, no further description is provided herein.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardsradware (Hardware Description Language), vhjhd (Hardware Description Language), and vhigh-Language, which are currently used in most popular applications. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

Those skilled in the art will also appreciate that, in addition to implementing a client, server as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the client, server are in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a client, server may be considered as a hardware component, and the means included therein for implementing various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present application may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the embodiments or some parts of the embodiments of the present application.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, embodiments for a computer storage medium, a server, and a client can all be explained with reference to the introduction of embodiments of the aforementioned method.

The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

Although the present application has been described in terms of embodiments, those of ordinary skill in the art will recognize that there are numerous variations and permutations of the present application without departing from the spirit of the application, and it is intended that the appended claims encompass such variations and permutations without departing from the spirit of the application.

Claims

1. A method for sharing membership rights, the method comprising:

receiving a permission sharing request pointing to a second account sent by a client logging in a first account; the permission sharing request comprises the appointed membership permission of the first account;

and canceling the appointed membership right of the first account, and adding the appointed membership right to the second account.

2. The method of claim 1, wherein the first account number has at least two membership rights; the method comprises the following steps:

3. The method of claim 1, wherein after canceling the designated membership rights of the first account and adding the designated membership rights to the second account, the method comprises:

4. The method of claim 1, wherein after receiving a rights recovery request directed to the designated membership rights from a client registered with a first account, the method further comprises:

5. The method of claim 1, wherein the specified membership rights are associated with a length of rights; before receiving a permission sharing request which is sent by a client logged in with a first account and points to a second account, the method comprises the following steps:

6. The method of claim 5, wherein after splitting the designated membership rights into at least two seed membership rights, the method further comprises:

7. The method of claim 1, further comprising:

8. The method of claim 1, wherein the specified membership rights are associated with a length of rights; the permission sharing request further comprises sharing duration; the sharing duration is less than the authority duration of the designated member authority; after receiving a permission sharing request which is sent by a client logged in with a first account and points to a second account, the method further comprises the following steps:

9. A server, comprising a memory and a processor, the memory operable to store a computer program and; the computer program, when executed by the processor, implements the steps of:

10. The server of claim 9, wherein the first account has at least two membership rights; the computer program, when executed by the processor, further implements the steps of:

11. The server according to claim 9, wherein the computer program, when executed by the processor, further performs the steps of:

12. The server according to claim 9, wherein the computer program, when executed by the processor, further performs the steps of:

13. The server according to claim 9, wherein the specified membership rights are associated with a length of rights; the computer program, when executed by the processor, further implements the steps of:

14. The server according to claim 13, wherein the computer program, when executed by the processor, further performs the steps of:

15. The server according to claim 9, wherein the computer program, when executed by the processor, further performs the steps of:

16. The server according to claim 9, wherein the specified membership rights are associated with a length of rights; the permission sharing request further comprises sharing duration; the sharing duration is less than the authority duration of the designated member authority; the computer program, when executed by the processor, further implements the steps of: