Subscription method and device for planned tasks

Abstract

One or more embodiments of the present specification provide a method and device for subscribing to a scheduled task, the method comprising: in response to a subscription instruction initiated by an initiator object for the scheduled task, determining a target subscription object corresponding to the scheduled task among the associated objects of the initiator object; generating a subscription relationship between the scheduled task and the target subscription object according to the subscription instruction; and pushing the scheduled task to the target subscription object based on the subscription relationship.

Description

Technical Field

[0001] The present invention relates to the field of mobile terminal technology, and more particularly to a method and device for subscribing to a planned task. Background Art

[0002] With the progress of society and the development of science and technology, digitalization has gradually penetrated into all walks of life, and people are increasingly relying on electronic production and lifestyle. In related technologies, the schedules and course schedules involved in daily learning and office work are still in paper form. People usually need to take photos or copy down relevant information through mobile devices. This process takes a lot of time and is prone to errors. Summary of the invention

[0003] In view of this, one or more embodiments of the present specification provide a method and device for subscribing to a scheduled task.

[0004] Specifically, one or more embodiments of this specification provide the following technical solutions:

[0005] According to a first aspect of one or more embodiments of this specification, a method for subscribing to a scheduled task is provided, the method comprising:

[0006] In response to a subscription instruction initiated by an initiator object for a planned task, determining a target subscription object corresponding to the planned task in an associated object of the initiator object;

[0007] Generate a subscription relationship between the planned task and the target subscription object according to the subscription instruction;

[0008] Based on the subscription relationship, the planned task is pushed to the target subscription object.

[0009] According to a second aspect of one or more embodiments of this specification, a method for subscribing to a scheduled task is provided, the method comprising:

[0010] Get the subscription instruction for the scheduled task initiated by the initiator object in the target group;

[0011] The subscription instruction is transmitted to a server, and the subscription instruction is used by the server to generate a subscription relationship between the planned task and the group members in the target group, so that the server pushes the planned task to the group members based on the subscription relationship.

[0012] According to a third aspect of one or more embodiments of this specification, a subscription device for a scheduled task is provided, the device comprising:

[0013] a determination unit, configured to determine, in response to a subscription instruction initiated by an initiator object for a planned task, a target subscription object corresponding to the planned task in an associated object of the initiator object;

[0014] A first generating unit, configured to generate a subscription relationship between the planned task and the target subscription object according to the subscription instruction;

[0015] A pushing unit is used to push the planned task to the target subscription object based on the subscription relationship.

[0016] According to a fourth aspect of one or more embodiments of this specification, a subscription device for a scheduled task is provided, the device comprising:

[0017] An acquisition unit, used to acquire a subscription instruction for a planned task initiated by an initiator object in a target group;

[0018] The transmission unit is used to transmit the subscription instruction to the server, and the subscription instruction is used by the server to generate a subscription relationship between the planned task and the group members in the target group, so that the server pushes the planned task to the group members based on the subscription relationship.

[0019] According to a fifth aspect of one or more embodiments of this specification, an electronic device is provided, including:

[0020] processor;

[0021] a memory for storing processor-executable instructions;

[0022] The processor implements the method as described in the first aspect or the second aspect by running the executable instructions.

[0023] According to a sixth aspect of one or more embodiments of the present specification, a computer-readable storage medium is provided, on which computer instructions are stored, and when the instructions are executed by a processor, the steps of the method described in the first aspect or the second aspect are implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 It is a schematic diagram of the architecture of a communication system provided by an exemplary embodiment of this specification.

[0025] Figure 2 It is a flowchart of a method for subscribing to a planned task provided by an exemplary embodiment of this specification.

[0026] Figure 3 It is a flowchart of another method for subscribing to a scheduled task provided by an exemplary embodiment of this specification.

[0027] Figure 4It is a flowchart of another method for subscribing to a scheduled task provided by an exemplary embodiment of this specification.

[0028] Figure 5 It is a schematic diagram of a display interface of an electronic device provided by an exemplary embodiment of this specification.

[0029] Figure 6 It is a schematic diagram of another electronic device display interface provided by an exemplary embodiment of this specification.

[0030] Figure 7 It is a schematic diagram of another electronic device display interface provided by an exemplary embodiment of this specification.

[0031] Figure 8 It is a structural schematic diagram of an electronic device provided by an exemplary embodiment of this specification.

[0032] Fig. 9 It is a block diagram of a subscription device for a planned task provided by an exemplary embodiment of this specification.

[0033] Fig.10 It is a block diagram of another subscription device for a scheduled task provided by an exemplary embodiment of the present specification. DETAILED DESCRIPTION

[0034] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of this specification. Instead, they are merely examples of devices and methods consistent with some aspects of one or more embodiments of this specification as detailed in the appended claims.

[0035] It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the steps included in the method may be more or less than those described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may be combined into a single step for description in other embodiments.

[0036] With the progress of society and the development of science and technology, digitalization has gradually penetrated into all walks of life, and people are increasingly dependent on electronic lifestyles. In related technologies, schedules and course schedules involved in daily learning and office work are still in paper form. People usually need to take photos or copy down relevant information through mobile devices. This process takes a lot of time and is prone to errors. Even electronic schedules and course schedules only have display functions, which are similar to traditional paper schedules and course schedules.

[0037] Therefore, this specification solves the above technical problems existing in the related art by improving the subscription method of the planned task.

[0038] Figure 1 FIG. 1 is a schematic diagram of the architecture of a communication system provided by an exemplary embodiment. Figure 1 As shown, the system may include a server 11, a network 12, and several electronic devices, such as a mobile phone 13, a mobile phone 14, and a mobile phone 15.

[0039] The server 11 may be a physical server including an independent host, or the server 11 may be a virtual server carried by a host cluster. During operation, the server 11 may run a server-side program of a certain application to implement the relevant business functions of the application. For example, when the server 11 runs an instant messaging application program, it may be implemented as the server end of the instant messaging application.

[0040] In this embodiment, the instant messaging application may include a common instant messaging application or an enterprise instant messaging application, and this specification does not limit this. In addition to being able to realize the communication function, the instant messaging application can also serve as an integrated functional platform for many other functions, such as the processing of approval events (such as leave, office supplies application, financial approval events, etc.), attendance events, task events, log events and other group events, and one or more embodiments of this specification do not limit this.

[0041] Mobile phones 13-15 are just one type of electronic device that users can use. In fact, users can obviously also use electronic devices such as tablet devices, laptops, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smart watches, etc.), etc., and one or more embodiments of this specification do not limit this. During operation, the electronic device can run a program on the client side of an application to implement the relevant business functions of the application. For example, when the electronic device runs an instant messaging application program, it can be implemented as a client of the instant messaging application.

[0042] It should be pointed out that the client application of the instant messaging application can be pre-installed on the electronic device so that the client can be started and run on the electronic device; of course, when an online "client" such as HTML5 technology is adopted, the client can be obtained and run without installing the corresponding application on the electronic device.

[0043] The network 12 for interaction between the mobile phones 13-15 and the server 11 may include various types of wired or wireless networks. In one embodiment, the network 12 may include a public switched telephone network (PSTN) and the Internet.

[0044] Figure 2 An exemplary embodiment provides a flowchart of a method for subscribing to a scheduled task. Figure 2 As shown, the method can be applied to a server (eg Figure 1 The method may include the following steps:

[0045] Step 202: In response to a subscription instruction initiated by an initiator object for a planned task, a target subscription object corresponding to the planned task in an associated object of the initiator object is determined.

[0046] In one embodiment, the initiator object may be a user of the corresponding electronic device, and the planned task may include a course schedule, a travel plan, and a schedule, etc., which is not limited in this specification. The server may receive a subscription instruction initiated by the initiator object for the planned task, and the server may respond to the subscription instruction to determine the target subscription object corresponding to the planned task in the associated object of the initiator object. Among them, the associated object may be an object that has any association relationship with the initiator object, for example, the associated object and the initiator object belong to the same application user, the associated object and the initiator object belong to the same communication group, or the associated object may be included in the initiator object's address book in the instant messaging application, etc., which is not limited in this specification.

[0047] In one embodiment, if the subscription instruction is initiated by the initiator object in the target group, the server may take at least some of the group members in the target group as the target subscription objects. The server may determine the identity relationship between the initiator object and all the group members in the target group, and take the group members whose corresponding identity relationship matches the preset identity relationship as the target subscription objects, that is, the identity relationship between the at least some of the group members and the initiator object needs to match the preset identity relationship. The identity relationship between the initiator object and the target subscription object may satisfy any of the following: when the initiator object has management authority over the target group, the target subscription object is a group member managed by the initiator object, for example, the initiator object may be a management member of the target group, and the target subscription object may be an ordinary member of the target group; when the target group corresponds to a preset group, the roles of the initiator object and the target subscription object in the preset group satisfy the preset role relationship, for example, when the preset group is a class in a school, the initiator object may be a teacher in the class, and the target subscription object may be a student in the class or a parent of a student, or when the preset group is a hospital, the initiator object may be a doctor in the hospital, and the target subscription object may be a corresponding patient or a family member of the patient, etc., which is not limited in this specification. The target group may be a group in any instant messaging application, such as an enterprise instant messaging application (Enterprise Instant Messaging, EIM), etc., which is not limited in this specification.

[0048] The server can then determine the target subscription object that meets the preset identity relationship based on the identity relationship between the initiator object and the group members in the target group. At this time, the initiator object does not need to manually configure the object identifier of the target subscription object, which can simplify the operation of the initiator object and improve the efficiency of sending subscription instructions. At the same time, it can effectively avoid errors or omissions in manual configuration of the target subscription object.

[0049] In one embodiment, the server may obtain a mapping relationship between a predefined task type and a relationship type. Of course, the mapping relationship may be pre-stored in the server or obtained by the server from other electronic devices, and this specification does not limit this. The server may determine the specific relationship type corresponding to the task type of the planned task based on the mapping relationship, and then the server may select a specific associated object that meets the specific relationship type from the associated objects of the initiator object, and use the selected specific relationship object as the target subscription object, wherein the specific relationship type may include at least one of the following: the target subscription object and the initiator object may belong to the same group, the target subscription object may belong to a specified group, the target subscription object and the initiator object may belong to the same group, the target subscription object may belong to a specified group, etc. For example, assuming that the initiator object is an administrative staff of the company, and the planned task is a work plan of the company's finance department, then the specific relationship type corresponding to the task type of the work plan may be that the target subscription object belongs to the company's finance department, and the server may use all company members belonging to the company's finance department as the target subscription objects.

[0050] The server can directly determine the relationship type according to the task type of the scheduled task, thereby determining the target subscription object that meets the corresponding relationship type. At this time, the initiator object does not need to manually configure the object identifier of the target subscription object, which can simplify the operation of the initiator object and improve the efficiency of sending subscription instructions. In particular, when the number of target subscription objects is large, it saves the time of the initiator object to configure the object identifiers of a large number of target subscription objects, improves the use experience of the initiator object, and can effectively avoid errors or omissions in manual configuration of the target subscription objects.

[0051] In one embodiment, the server may parse the object identifier of at least one specific associated object selected by the initiator object from the associated objects contained in the subscription instruction, so that the specific associated object corresponding to the object identifier may be used as the target subscription object. The object identifier may be the object identifier corresponding to each target subscription object, that is, one target subscription object corresponds to one object identifier; or, the object identifier may also be the set identifier of the object set in which all target subscription objects are located. Of course, the object identifier may be the name or number of each target subscription object, or the name or number of an object set, which is not limited in this specification.

[0052] Step 204: Generate a subscription relationship between the planned task and the target subscription object according to the subscription instruction.

[0053] Step 206: Push the planned task to the target subscription object based on the subscription relationship.

[0054] In one embodiment, the server can generate a subscription relationship between the scheduled task and the target subscription object based on the above-mentioned subscription instruction, so that the scheduled task can be pushed directly to the target subscription object based on the subscription relationship without the target subscription object performing any manual subscription operation. The target subscription object can directly view the corresponding scheduled task on the electronic device, which can improve the reach rate of the scheduled task.

[0055] In one embodiment, the server can automatically generate a subscription relationship between a determined target subscription object and a scheduled task based on a subscription instruction initiated by an initiator object. The initiator object can initiate the process of generating a subscription relationship between the target subscription object and the scheduled task. The initiator object can control the target subscription object corresponding to the scheduled task, which can prevent the scheduled task from being arbitrarily transmitted to any other user, thereby ensuring the privacy of the scheduled task. At the same time, the target subscription object is transparent to the process of generating the subscription relationship, which can prevent the target subscription object from manually subscribing to the scheduled task, simplifying the operation of the target subscription object, and ensuring the success rate of transmitting the scheduled task to the target subscription object through the subscription relationship.

[0056] In one embodiment, when a change is detected in the task content of a scheduled task, the server can synchronously update the task content of the scheduled task that has been pushed to the target subscription object based on the subscription relationship, so that the target subscription object can always view the latest task content of the scheduled task, and the consistency of the task content of the scheduled task obtained by the sender object and the target subscription object can be ensured, thereby realizing real-time update of the task content of the scheduled task and satisfying the corresponding object's update requirements for the scheduled task.

[0057] In one embodiment, the server can push the scheduled task to the calendar application of the target subscription object, so that the target subscription object can associate the task content of the scheduled task with the corresponding date in the display interface corresponding to the calendar application, and the scheduled task can be directly displayed in the corresponding date, which is convenient for the target subscription object to obtain the scheduled task and the corresponding processing time information in time, which can improve the user experience of the target subscription object, and the scheduled task can be directly saved in the calendar application, which can avoid the target subscription object manually adding the scheduled task to the calendar application. Of course, the server can also push the scheduled task to other pre-set applications, which is not limited in this specification.

[0058] In one embodiment, the server pushes the scheduled task to the calendar application of the target subscription object according to the execution cycle and duration of the scheduled task, so that the target subscription object does not need to manually add multiple periodic scheduled tasks and manually set the start time and end time, etc. For example, when the scheduled task is a one-week class schedule, and the duration of the one-week class schedule is from May to June, the server can automatically add the content of the one-week class schedule to each week of May and June in the calendar application, and does not add the one-week class schedule to other months in the calendar application.

[0059] In one embodiment, the server may respond to the received subscription request for the scheduled task from other objects different from the target subscription object, thereby generating a subscription relationship between the other objects and the scheduled task, so that the other objects can also view the scheduled task on the corresponding electronic device. Alternatively, after receiving the subscription request for the scheduled task submitted by other objects, the server may transmit the subscription request to the sender object for approval. After receiving the consent information of the sender object for the subscription request of other objects, the server may generate a subscription relationship between the other objects that submitted the subscription request and the scheduled task, thereby ensuring the privacy of the scheduled task and preventing the scheduled task from being arbitrarily obtained and viewed by any other object. Of course, the server may also send the subscription request to the object with management authority over the scheduled task for approval, which is not limited in this specification.

[0060] Figure 3 An exemplary embodiment provides a flowchart of a method for subscribing to a scheduled task. Figure 3 As shown, the method can be applied to electronic devices (such as Figure 1 The method may include the following steps:

[0061] Step 302: Obtain a subscription instruction for a planned task initiated by an initiator object in a target group.

[0062] In one embodiment, an electronic device may obtain a subscription instruction for a planned task initiated by an initiator object in a target group. The initiator object may be a user of the corresponding electronic device. The planned task may include a course schedule, a travel plan, and a schedule plan, etc., which is not limited in this specification. Among them, the sender may generate a subscription instruction by triggering a subscription option in a display interface of the target group, and the trigger operation may include any form of trigger operation implemented for the subscription option, such as a mouse click operation, a mouse hover operation, a touch operation, a line of sight focus operation, etc. Of course, the initiator object may also initiate a subscription instruction by triggering a physical button on a local device, etc., which is not limited in this specification.

[0063] Step 304: transmit the subscription instruction to the server, where the subscription instruction is used by the server to generate a subscription relationship between the planned task and the group members in the target group, so that the server pushes the planned task to the group members based on the subscription relationship.

[0064] In one embodiment, the electronic device can transmit the acquired subscription instruction to the server, and the server can generate a subscription relationship between the corresponding planned task and the group members in the target group according to the subscription instruction, and the server can push the corresponding planned task to the group members based on the subscription relationship.

[0065] The server can perform the following operations according to the subscription instruction: Figure 2 The embodiment shown is similar, and the implementation details involved can also refer to the above embodiment, and will not be described in detail here.

[0066] For ease of understanding, the following takes the course schedule subscription process as an example to explain the technical solution of the specification in detail. Figure 4 This is a flowchart of a subscription method for a planned task provided by an exemplary embodiment of this specification. Assuming that the home-school contact group A is a group of class A in an instant messaging application, the home-school contact group A includes teacher T1, teacher T2 and the parents of class A; the method may include the following steps:

[0067] Step 401, create a course schedule S.

[0068] In this embodiment, the teacher who is the user of the electronic device can create a corresponding electronic course schedule in the instant messaging application. The electronic course schedule can be created separately in the instant messaging application or the electronic course schedule can be created in a corresponding group, which is not limited in this specification.

[0069] In this embodiment, it is assumed that teacher T1 can create a corresponding course schedule S in the home-school contact group A, such as Figure 5 The diagram shows a display interface of a home-school contact group on an electronic device. The display interface 501 of the home-school contact group A may include a create course schedule option 502 and a subscribe for others option 503. Teacher T1 may establish a corresponding course schedule S by triggering the create course schedule option 502. Of course, the create course schedule option 502 and the subscribe for others option 503 may be integrated into one option, which is not limited in this specification.

[0070] Step 402: receiving a subscription instruction initiated by teacher T1 for the course schedule S.

[0071] In this embodiment, after completing the creation of the course schedule S, teacher T1 can initiate a subscription instruction for the course schedule S in the home-school contact group A. Teacher T1 can trigger Figure 5 After receiving the trigger operation of the teacher T1 for the subscription option 503, the electronic device can also display a corresponding dialog box for the teacher T1 to select. The display interface of the dialog box can be as follows: Figure 6 As shown, the display interface 601 of the dialog box may include a planned task option 6011 and a permission setting option 6012. Then the teacher T1 can configure the planned task option 6011 as a course schedule S, and can configure the permission range of the target subscription object corresponding to the planned task as read-only permission. Of course, the permission range of the target subscription object may include read-only permission, read-write permission, etc., which is not limited in this manual.

[0072] In this embodiment, after receiving the subscription instruction from teacher T1 for the course schedule S, the electronic device may transmit the subscription instruction to the corresponding server for processing.

[0073] Step 403, determining the identity relationship between teacher T1 and each group member in the home-school contact group A.

[0074] Step 404: determine the target subscription object.

[0075] In this embodiment, after receiving the subscription instruction, the server can determine that the identity relationship between teacher T1 and the parents in the home-school contact group A is a "teacher-parent" relationship, and the identity relationship between teacher T1 and teacher T2 is a "teacher-teacher" relationship.

[0076] In this embodiment, it is assumed that the preset identity relationship that matches the subscription instruction of teacher T1 to subscribe to the course schedule S for others is the "teacher-parent" relationship. Then the server can use the group members whose corresponding identity relationship in the home-school contact group matches the "teacher-parent" relationship as the target subscription objects corresponding to the course schedule S, that is, the parents of class A in the home-school contact group A as the target subscription objects.

[0077] Step 405: Generate a subscription relationship.

[0078] Step 406: Push the course schedule S to the target subscription object.

[0079] In this embodiment, after determining the target subscription object corresponding to the course schedule S, the server can generate a subscription relationship between the course schedule S and the target subscription object, and can push the corresponding course schedule S to the calendar application of each target subscription object according to the subscription relationship, so that the content of the course schedule S can be associated with the corresponding date in the display interface of the calendar application of each target subscription object, such as Figure 7 As shown. Then, teacher T1 can subscribe the curriculum schedule S for all parents in the home-school contact group A without the parents having to do anything. This ensures that the corresponding curriculum schedule S content can be displayed in the calendar application corresponding to each parent, thereby improving the reach of the curriculum schedule S.

[0080] Step 407: It is detected that teacher T1 modifies the course schedule S.

[0081] Step 408: synchronously update the course schedule S at each target subscription object.

[0082] In this embodiment, after teacher T1 modifies the content of the electronic course schedule S, the server can monitor that the content of the course schedule S has changed. Then, based on the subscription relationship between the course schedule S and the target subscription object, the server can push the modified course schedule S to the target subscription object again, thereby achieving consistency between the course schedule S corresponding to the electronic device of teacher T1 and the course schedule S corresponding to the electronic device of each target subscription object, thereby avoiding the target subscription object from viewing the course schedule S before it is updated, and ensuring the accuracy and timeliness of information transmission.

[0083] Figure 8 This is a schematic diagram of the structure of an electronic device provided by an exemplary embodiment. Figure 8 At the hardware level, the device includes a processor 802, an internal bus 804, a network interface 806, a memory 808, and a non-volatile memory 810, and may also include hardware required for other services. The processor 802 reads the corresponding computer program from the non-volatile memory 810 into the memory 808 and then runs it, forming a subscription device for the scheduled task at the logical level. Of course, in addition to the software implementation, one or more embodiments of this specification do not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0084] Please refer to Fig. 9 In a software implementation, the subscription device for the planned task may include a determination unit 901, a first generation unit 902, and a push unit 903. Among them:

[0085] The determining unit 901 is configured to determine, in response to a subscription instruction initiated by an initiator object for a planned task, a target subscription object corresponding to the planned task in an associated object of the initiator object;

[0086] A first generating unit 902 is used to generate a subscription relationship between the planned task and the target subscription object according to the subscription instruction;

[0087] The pushing unit 903 is used to push the planned task to the target subscription object based on the subscription relationship.

[0088] Optionally, the determining unit 901 is specifically configured to:

[0089] If the initiator object initiates the subscription instruction in the target group, at least a part of the group members in the target group are used as the target subscription objects.

[0090] Optionally, the determining unit 901 is specifically configured to:

[0091] Determining an identity relationship between the initiator object and group members in the target group;

[0092] The group members whose corresponding identity relationships match the preset identity relationships are used as the target subscription objects.

[0093] Optionally, the identity relationship between the initiator object and the target subscription object includes any one of the following: when the initiator object has management authority over the target group, the target subscription object is a group member managed by the initiator object; when the target group corresponds to a preset group, the roles of the initiator object and the target subscription object in the preset group satisfy a preset role relationship.

[0094] Optionally, the determining unit 901 is specifically configured to:

[0095] Determine the specific relationship type corresponding to the task type of the planned task according to the predefined mapping relationship between the task type and the relationship type;

[0096] A specific associated object that meets the specific relationship type is selected from the associated objects of the initiator object to serve as the target subscription object.

[0097] Optionally, the specific relationship type includes at least one of the following: the target subscription object and the initiator object belong to the same group, the target subscription object belongs to a specified group, the target subscription object and the initiator object belong to the same group, and the target subscription object belongs to a specified group.

[0098] Optionally, the determining unit 901 is specifically configured to:

[0099] parsing the object identifier of at least one specific associated object selected by the initiator object from the associated objects contained in the subscription instruction;

[0100] The specific associated object corresponding to the object identifier is used as the target subscription object.

[0101] Optionally, the object identifier is an object identifier corresponding to each target subscription object; or, the object identifier is a set identifier of an object set in which all target subscription objects are located.

[0102] Optionally, also include:

[0103] The updating unit 904 is configured to synchronously update the task content of the scheduled task that has been pushed to the target subscription object based on the subscription relationship when detecting that the task content of the scheduled task has changed.

[0104] Optionally, the pushing unit 903 is specifically used for:

[0105] The planned task is pushed to the calendar application of the target subscription object, so that the task content of the planned task and the corresponding date are associated and displayed in a display interface corresponding to the calendar application.

[0106] Optionally, also include:

[0107] The second generating unit 905 is configured to generate a subscription relationship between the other object and the scheduled task in response to a received subscription request for the scheduled task from another object different from the target subscription object.

[0108] Optionally, the planned tasks include: a course schedule, a travel plan, and a schedule plan.

[0109] Please refer to Fig.10 In a software implementation, the subscription device for the planned task may include an acquisition unit 1001 and a transmission unit 1002. Wherein:

[0110] The acquisition unit 1001 is used to acquire a subscription instruction for a planned task initiated by an initiator object in a target group;

[0111] The transmission unit 1002 is used to transmit the subscription instruction to the server, and the subscription instruction is used by the server to generate a subscription relationship between the planned task and the group members in the target group, so that the server pushes the planned task to the group members based on the subscription relationship.

[0112] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which may be in the form of a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, a game console, a tablet computer, a wearable device or a combination of any of these devices.

[0113] In a typical configuration, a computer includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0114] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0115] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0116] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0117] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0118] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0119] It should be understood that although the terms first, second, third, etc. may be used to describe various information in one or more embodiments of this specification, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0120] The above description is merely a preferred embodiment of one or more embodiments of the present specification and is not intended to limit one or more embodiments of the present specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of one or more embodiments of the present specification shall be included in the scope of protection of one or more embodiments of the present specification.

Claims

1. A subscription method for a planned task, characterized in that: include: In response to a subscription instruction initiated by an initiator object for a planned task, determining a target subscription object corresponding to the planned task in an associated object of the initiator object; Generate a subscription relationship between the planned task and the target subscription object according to the subscription instruction; Based on the subscription relationship, the planned task is pushed to the target subscription object; The step of determining the target subscription object corresponding to the planned task in the associated object of the initiator object includes: If the initiator object initiates the subscription instruction in the target group, the identity relationship between the initiator object and the group members in the target group is determined, and the group members whose corresponding identity relationships match the preset identity relationships are used as the target subscription objects.

2. The method according to claim 1, characterized in that The identity relationship between the initiator object and the target subscription object includes any of the following: When the initiator object has management authority over the target group, the target subscription object is a group member managed by the initiator object; When the target group corresponds to a preset community, the roles of the initiator object and the target subscription object in the preset community satisfy a preset role relationship.

3. The method according to claim 1, characterized in that Determining a target subscription object corresponding to the planned task in an associated object of the initiator object includes: Determine the specific relationship type corresponding to the task type of the planned task according to the predefined mapping relationship between the task type and the relationship type; A specific associated object that meets the specific relationship type is selected from the associated objects of the initiator object to serve as the target subscription object.

4. The method according to claim 3, characterized in that The specific relationship type includes at least one of the following: the target subscription object and the initiator object belong to the same group, the target subscription object belongs to a specified group, the target subscription object and the initiator object belong to the same group, and the target subscription object belongs to a specified group.

5. The method according to claim 1, characterized in that Determining a target subscription object corresponding to the planned task in an associated object of the initiator object includes: parsing the object identifier of at least one specific associated object selected by the initiator object from the associated objects contained in the subscription instruction; The specific associated object corresponding to the object identifier is used as the target subscription object.

6. The method according to claim 5, characterized in that The object identifier is the object identifier corresponding to each target subscription object; or, the object identifier is the set identifier of the object set where all target subscription objects are located.

7. The method according to claim 1, characterized in that Also includes: When it is detected that the task content of the planned task has changed, the task content of the planned task that has been pushed to the target subscription object is synchronously updated based on the subscription relationship.

8. The method according to claim 1, characterized in that Pushing the planned task to the target subscription object includes: The planned task is pushed to the calendar application of the target subscription object, so that the task content of the planned task and the corresponding date are associated and displayed in a display interface corresponding to the calendar application.

9. The method according to claim 1, characterized in that: Also includes: In response to a received subscription request for the scheduled task from another object different from the target subscription object, a subscription relationship between the other object and the scheduled task is generated.

10. The method according to claim 1, characterized in that The planning tasks include: course schedule, itinerary plan, and schedule plan.

11. A method for subscribing to a planned task, characterized in that: include: Get the subscription instruction for the scheduled task initiated by the initiator object in the target group; Determine the identity relationship between the initiator object and the group members in the target group, and use the group members whose corresponding identity relationship matches the preset identity relationship as target subscription objects; The subscription instruction is transmitted to a server, and the subscription instruction is used by the server to generate a subscription relationship between the planned task and the target subscription object in the target group, so that the server pushes the planned task to the target subscription object based on the subscription relationship.

12. A subscription device for a planned task, characterized in that: include: a determination unit, configured to determine, in response to a subscription instruction initiated by an initiator object for a planned task, a target subscription object corresponding to the planned task in an associated object of the initiator object; A first generating unit, configured to generate a subscription relationship between the planned task and the target subscription object according to the subscription instruction; A push unit, configured to push the planned task to the target subscription object based on the subscription relationship; The determining unit is further configured to determine the identity relationship between the initiator object and group members in the target group if the initiator object initiates the subscription instruction in the target group, and use the group members whose corresponding identity relationships match the preset identity relationships as the target subscription objects.

13. A subscription device for a planned task, characterized in that: include: An acquisition unit, used to acquire a subscription instruction for a planned task initiated by an initiator object in a target group; A determination unit, configured to determine the identity relationship between the initiator object and the group members in the target group, and to use the group members whose corresponding identity relationship matches the preset identity relationship as target subscription objects; The transmission unit is used to transmit the subscription instruction to the server, and the subscription instruction is used by the server to generate a subscription relationship between the planned task and the target subscription object in the target group, so that the server pushes the planned task to the target subscription object based on the subscription relationship.

14. An electronic device, characterized in that: include: processor; a memory for storing processor-executable instructions; The processor implements the method according to any one of claims 1 to 11 by running the executable instructions.

15. A computer-readable storage medium having computer instructions stored thereon, characterized in that: When the instruction is executed by a processor, the steps of the method according to any one of claims 1 to 11 are implemented.

Images