這裡將詳細地對示例性實施例進行說明，其示例表示在附圖中。下面的描述涉及附圖時，除非另有表示，不同附圖中的相同數字表示相同或相似的要素。以下示例性實施例中所描述的實施方式並不代表與本說明書一個或多個實施例相一致的所有實施方式。相反，它們僅是與如所附申請專利範圍中所詳述的、本說明書一個或多個實施例的一些方面相一致的裝置和方法的例子。 需要說明的是：在其他實施例中並不一定按照本說明書示出和描述的順序來執行相應方法的步驟。在一些其他實施例中，其方法所包括的步驟可以比本說明書所描述的更多或更少。此外，本說明書中所描述的單個步驟，在其他實施例中可能被分解為多個步驟進行描述；而本說明書中所描述的多個步驟，在其他實施例中也可能被合併為單個步驟進行描述。 圖1是一示例性實施例提供的一種群組任務系統的架構示意圖。如圖1所示，該系統可以包括伺服器11、網路12、若干電子設備，比如手機13、手機14和手機15等。 伺服器11可以為包含一獨立主機的物理伺服器，或者該伺服器11可以為主機集群承載的虛擬伺服器。在運行過程中，伺服器11可以運行某一應用的伺服器側的程式，以實現該應用的相關業務功能，比如當該伺服器11運行移動化團體辦公平臺的程式時，可以實現為該移動化團體辦公平臺的服務端。而在本說明書一個或多個實施例的技術方案中，可由伺服器11透過與手機13-15上運行的用戶端進行配合，以實現基於群組任務的資訊獲取方案。 在本實施例中，移動化團體辦公平臺不僅可以實現通訊功能，還可以作為諸多其他功能的集成化功能平臺，比如對於審批事件(如請假、辦公物品申領、財務等審批事件)、考勤事件、任務事件、日誌事件等團體內部事件的處理，再比如訂餐、採購等團體外部事件的處理，本說明書一個或多個實施例並不對此進行限制。 較為具體地，移動化團體辦公平臺可以承載於相關技術中的即時通訊應用，比如企業即時通訊(Enterprise Instant Messaging，EIM)應用，例如Skype For Business®
、Microsoft Teams®
、Yammer®
、Workplace®
、Slack®
、企業微信®
、紛享銷客®
、企業飛信®
、企業易信®
等。當然，即時通訊功能僅為移動化團體辦公平臺支援的通訊功能之一，該移動化團體辦公平臺還能夠實現更多諸如上述的其他功能，此處不再贅述。 手機13-15只是用戶可以使用的一種類型的電子設備。實際上，用戶顯然還可以使用諸如下述類型的電子設備：平板設備、筆記型電腦、掌上型電腦(PDAs，Personal Digital Assistants)、可穿戴設備(如智慧眼鏡、智慧手錶等)等，本說明書一個或多個實施例並不對此進行限制。在運行過程中，該電子設備可以運行某一應用的用戶端側的程式，以實現該應用的相關業務功能，比如當該電子設備運行移動化團體辦公平臺的程式時，可以實現為該移動化團體辦公平臺的用戶端。 需要指出的是：移動化團體辦公平臺的用戶端的應用程式可以被預先安裝在電子設備上，使得該用戶端可以在該電子設備上被啟動並運行；當然，當採用諸如HTML5技術的線上“用戶端”時，無需在電子設備上安裝相應的應用程式，即可獲得並運行該用戶端。 而對於手機13-15與伺服器11之間進行交互的網路12，可以包括多種類型的有線或無線網路。在一實施例中，該網路12可以包括公共交換電話網絡(Public Switched Telephone Network，PSTN)和網際網路。同時，手機13-15等電子設備之間也可以透過該網路12進行通訊交互，比如在任意兩台電子設備之間建立單聊會話；或者，多個用戶可以參與同一群組，他們使用的多台電子設備可以參與至該同一群組對應的會話，使得任一使用者可以透過自身的電子設備向該會話中的其他所有使用者發送通訊消息。 圖2是一示例性實施例提供的一種群組任務的資訊獲取方法的流程圖。如圖2所示，該方法應用於電子設備，可以包括以下步驟： 步驟202，透過群組對應的會話發送消息，所述消息包含標識內容和針對所述群組內的群組任務的詢問內容，所述標識內容用於指示伺服器對所述詢問內容予以答覆。 在一實施例中，可以在所述會話對應的會話介面檢測到使用者輸入資訊時，將所述使用者輸入資訊作為所述消息的消息內容進行發送，即消息可由使用者手動輸入得到。 在一實施例中，可以按照使用者設定的消息內容和發送週期，自動發送所述消息，比如該發送週期可以包括每天、每週、每月等，可由使用者根據實際需求進行設定。其中，用戶可以設定一個或多個發送週期，且每一週期對應相同或不同的消息；例如，用戶可以同時設定發送週期為每天和每週，使得每天自動發送第一內容的消息，且每週自動發送第二內容的消息。 在一實施例中，標識內容可以包括預定義的任意內容，本說明書並不對此進行限制。例如，標識內容可以採用“特殊字元+名稱”的形式，比如特殊字元可以為@、#等不常用的字元，而名稱可以為伺服器、機器人等預先約定用於指代伺服器的資訊，因而標識內容可以為諸如“@伺服器”、“#機器人#”等。再例如，標識內容可以直接採用預先約定用於指代伺服器的資訊，比如“群組秘書”等。 在一實施例中，電子設備上可以運行移動化團體辦公平臺的用戶端，該用戶端可以提供群組通訊功能和任務管理功能，由該群組通訊功能實現群組的創建以及群組成員之間的通訊操作，並由該任務管理功能實現任務的管理。 在一實施例中，群組任務區別於其他類型的任務，群組任務可供用戶在與群組相關的功能介面內實現創建、查看等管理操作，便於群組任務的創建者、執行者等關聯用戶之間基於該群組的會話實現快捷溝通。 在一實施例中，群組任務的創建者、執行者等關聯用戶可以均為所述群組的群組成員，使得這些關聯用戶可以基於該群組的會話實現快捷溝通。 在一實施例中，所述群組任務可由所述群組的群組成員在所述群組的關聯功能介面中創建生成。例如，該關聯功能介面可以包括任務管理介面，該任務管理介面可供群組成員創建新的群組任務、查看已創建的群組任務等，且該群組的會話介面可以包括該任務管理介面的入口，以便群組成員在任務管理介面與會話介面之間實現快速切換。當然，關聯功能介面還可以包括與群組相關的其他形式的功能介面，本說明書並不對此進行限制。 在一實施例中，所述群組任務的執行者可由所述群組任務的創建者透過在所述群組的群組成員中實施選取操作而確定，比如該創建者可以選取至少一個群組成員、以作為該群組任務的執行者；其中，當創建者在創建群組任務時，可以僅向該創建者提供該群組的群組成員列表，從而使得創建者與執行者均被限制於該群組的群組成員中。此外，所述群組任務的創建者如果未實施所述選取操作，所述群組的所有群組成員被預設為所述群組任務的執行者。 在一實施例中，當創建者為群組內的群組成員時，該創建者才能夠進入與群組相關的功能介面，以完成對群組任務的創建操作。 在一實施例中，當任一任務的創建介面與所述群組無關，且所述任一任務的創建者、執行者均為所述群組的群組成員時，所述任一任務可以被確定為所述群組內的群組任務。例如，雖然創建者並未在與群組相關的功能介面創建任務，但是如果創建者和被選中的執行者均屬於同一群組，可以將該任務設定為與該同一群組相關的群組任務；其中，該設定操作可以為自動操作，或者可以向創建者發起設定提醒，並在創建者回應於該設定提醒時實施設定操作。 在一實施例中，群組的群組成員可以具有相同的團體歸屬資訊(比如歸屬於同一企業)，即該群組為團體內群組。在一實施例中，群組的群組成員可以具有不完全相同的團體歸屬資訊(比如分別歸屬於多個企業)，即該群組為跨團體群組。在一實施例中，群組可以與團體無關，比如親戚或朋友之間創建的群組等。 步驟204，接收所述伺服器針對所述詢問內容返回的答覆內容，所述答覆內容包括所述群組任務的資訊。 在一實施例中，消息、答覆內容可以採用任意類型，本說明書並不對此進行限制。比如，消息可以包括以下至少之一：文字消息或音訊消息，答覆內容可以包括以下至少之一：文字消息或音訊消息。在一種情況下，消息與答覆內容可以為相同類型，比如當消息採用文字消息時，答覆內容也為文字消息，當消息為音訊消息時，答覆內容也為音訊消息。在另一種情況下，消息與答覆內容可以不存在類型關聯，比如當消息採用文字消息時，答覆內容可以為文字消息、也可以為音訊消息。 在一實施例中，當所述消息包含所述標識內容時，所述消息和所述答覆內容可以僅對所述消息的發送方可見、對所述群組中的其他群組成員不可見，從而在滿足發送方的詢問需求的情況下，避免對其他群組成員造成不必要的干擾。 在一實施例中，可以接收所述伺服器自動發送的針對所述群組任務的通知消息；例如，所述通知消息可以包括以下至少之一：週期性統計資訊、針對尚未完成的群組任務的提示資訊、針對臨近完成期限的群組任務的提示資訊、針對已完成的群組任務的完成提示資訊等，本說明書並不對此進行限制。 在一實施例中，當檢測到針對所述通知消息的觸發操作時，可以切換至與所述通知消息相關的群組任務的資訊展示介面，以便於查看該群組任務的概要資訊或詳情資訊。 在一實施例中，所述群組任務可由創建者透過對群組任務範本進行配置而生成。換言之，可以預先創建若干備選的群組任務範本，比如這些群組任務範本分別適用於不同職位、不同場景、不同行業或不同目的等，使得創建者可以根據實際需求選取恰當的群組任務範本後，透過配置該群組任務範本中的可配置變數，即可快速生成符合實際需求的群組任務，簡化創建者的操作。同時，在創建群組任務的過程中，群組任務範本還可以對創建者起到一定的教學和引導作用，尤其是對於初次或較少創建群組任務的創建者而言，可以協助創建者完成對群組任務的快速創建，從而降低創建者的學習門檻。 在一實施例中，創建者可以隨意使用所有的群組任務範本。在另一實施例中，所述群組任務範本被預先綁定至所述群組，即創建者只能夠對綁定至該群組的群組任務範本進行配置，而不能夠對其他群組任務範本進行隨意使用，從而實現了對群組任務範本的使用管理。 在一實施例中，可由群組的群主、管理員等管理成員對群組任務範本進行管理，比如將群組任務範本綁定至群組，或者將群組任務範本與群組解綁定。相應地，群組成員可以使用被綁定至該群組的群組任務範本，以快速創建相應的群組任務。 在一實施例中，群組任務範本可以由上述的通訊應用或移動化團體辦公平臺的開發方提供，以供該通訊應用或移動化團體辦公平臺的使用者進行獲取和使用。在另一實施例中，群組任務範本可由上述的通訊應用或移動化團體辦公平臺的使用者創建，並分享至其他使用者進行使用；例如，該通訊應用或移動化團體辦公平臺可以提供群組任務範本的共用平臺，使用者可以透過該共用平臺對自己創建的群組任務範本進行共用，也可以獲取其他使用者共用的群組任務範本。 在一實施例中，可以在所述群組內導入任務記錄檔，所述任務記錄檔中記錄有至少一項群組任務的描述資訊；然後，根據所述任務記錄檔中記錄的描述資訊，批量創建與所述群組相關的群組任務。其中，所述任務記錄檔可以包括下述任一：文字檔、表格檔等，本說明書並不對此進行限制。透過預先將群組任務的描述資訊記錄於任務記錄檔中，使得群組成員可以透過向群組中導入該任務記錄檔，快速、批量創建相應的群組任務，而無需群組成員分別、單獨創建每個群組任務，有助於提升對群組任務的創建效率。 在一實施例中，群組成員在導入任務記錄檔時，可以指定採用的群組任務範本，使得創建的群組任務均為基於該群組任務範本而生成，有助於確保生成的群組任務在樣式、格式等方面滿足該群組成員的實際需求。 為了便於理解，以企業即時通訊應用“企業微信”為例，對本說明書一個或多個實施例的技術方案進行說明。假定手機13和手機14上運行有企業微信用戶端、伺服器11上運行有企業微信服務端，手機13上登錄有用戶A的註冊帳號、使得手機13被配置為企業微信用戶端1，手機14上登錄有用戶B的註冊帳號、使得手機14被配置為企業微信用戶端2。其中，假定用戶A、用戶B均為群組AA的群組成員，可以基於該群組AA實現對群組任務的管理操作。 圖3是一示例性實施例提供的一種群組的會話介面的示意圖。假定在手機13運行的企業微信用戶端1上，可以向用戶A呈現出如圖3所示的會話介面300，該會話介面300對應於使用者A所處的群組AA。會話介面300可以包括如圖3所示的群任務圖示301，該群任務圖示301可以作為相應的功能介面的操作入口，使得在檢測到針對該群任務圖示301的觸發操作時，可以切換至如圖4所示的群任務管理介面400。 圖4是一示例性實施例提供的一種群任務管理介面的示意圖。在本說明書的實施例中，群組任務與群任務均為同一類任務的不同叫法，本說明書並不對此進行限制。在如圖4所示的群任務管理介面400中，可以包括群任務創建區域401，該群任務創建區域401可供使用者A在該群組AA內創建新的群任務。群任務管理介面400還可以展示出群組AA內已創建的群任務，比如圖4所示的群任務402、群任務403等。 在一實施例中，群任務402的任務主題為“週二前完成設計方案”、創建者為用戶A、執行者為用戶B、任務創建時間為“10-18 15:30”、截止時間為“10月24日 週二 18:00”、回覆狀態為“暫無回覆”、完成狀態為“B未完成”，當然在其他實施例中可以僅包含上述內容的一部分，或者還可以包含其他類型的任務資訊，本說明書並不對此進行限制。類似地，群任務403的任務主題為“X專案產品方案”、創建者為用戶C、執行者為用戶A等3人、任務創建時間為“10-12 14:20”、截止時間為“10月20日 週五 12:00”、回覆狀態為“2條回覆”、完成狀態為“1/3已完成”。 在一實施例中，圖4中可以僅示出群任務402、群任務403等的部分資訊，而使用者A可以透過觸發該群任務402或群任務403，以查看任務詳情。例如，在群任務403中的“2條回覆”的具體回覆內容、“A等3人”的3個執行者的資訊、“1/3人已完成”中的已完成者和未完成者的資訊等，均可以在任務詳情中予以具體呈現。 在一實施例中，群任務創建區域401的輸入框內可以示出諸如“添加一個群任務…”的提示資訊，以協助使用者A完成群任務的創建操作。例如，圖5是一示例性實施例提供的一種設置群任務的任務主題的示意圖；透過觸發群任務創建區域401的輸入框，用戶A可以在該輸入框內輸入所需創建的群任務的任務主題，比如該任務主題可以為圖5所示的“Y項目設計稿”或其他任意內容。 在一實施例中，群任務創建區域401可以包括執行者設置圖示501，可供使用者A為所需創建的群任務設置執行者。例如，圖6是一示例性實施例提供的一種設置群任務的執行者的示意圖；當檢測到針對執行者設置圖示501的觸發操作後，可以切換至如圖6所示的執行者設置介面600，該執行者設置介面600可以包括右側的備選用戶列表601和左側的已選用戶列表602。其中，備選用戶列表601可以包括群組AA的所有群組成員，比如用戶A、用戶B、用戶C、用戶D和用戶E等；假定用戶A選取用戶B和用戶C為執行者，在用戶B、用戶C在備選用戶列表601中對應的選擇框“○”中將出現選中標記“√”，且使用者B和用戶C將被添加至左側的已選用戶列表602中。當用戶A希望取消對用戶B或用戶C的選擇時，可以重新觸發相應的選擇框“○”；或者，在已選用戶列表602中，用戶B、用戶C均存在對應的刪除標記“×”，可以透過觸發該刪除標記“×”來取消對相應用戶的選擇。 圖7是一示例性實施例提供的一種已設定執行者的群任務管理介面的示意圖。在用戶A實施了對執行者的選取後，可以對如圖5所示的執行者設置圖示501進行替換，以提示用戶A已經實施了該選取操作，避免在實施其他操作後發生遺忘。例如，當用戶A將用戶B、用戶C選取為執行者時，可以將如圖5所示的執行者設置圖示501替換為被選取為執行者的用戶B、使用者C的頭像圖示，以使得使用者A能夠快速確定已選取的至少一部分執行者。當然，由於群任務創建區域401往往有限，因而展示的頭像數量可以存在一定限制，比如限制為不超過3個頭像，而超出的頭像可以不展示或採用“…”予以省略。 在一實施例中，群任務創建區域401可以包括期限設置圖示502，可供使用者A為所需創建的群任務設置截止時間。例如，圖8是一示例性實施例提供的一種設置群任務的截止時間的示意圖；當檢測到針對期限設置圖示502的觸發操作後，可以切換至如圖8所示的期限設置介面800，該期限設置介面600可以包括日期選擇區域和時刻設定區域，可分別供使用者設定作為截止時間的日期和時刻，比如可以設定為圖8所示的2017年10月30日16:00。其中，期限設置介面800可以提供如圖8所示的“無截止時間”選項，從而不為相應的群任務設定截止時間。與執行者設置圖示501相類似的，在用戶A設置了群任務的截止時間後，也可以對期限設置圖示502進行替換，以對用戶A進行提示，此處不再贅述。 圖9是一示例性實施例提供的另一種群任務管理介面的示意圖。基於用戶A的上述操作，創建得到新的群任務可以被展示於如圖9所示的群任務管理介面400中，比如該新的群任務可以為圖9所示的群任務404。其中，群任務404的任務主題為“Y專案設計稿”、創建者為用戶A、執行者為用戶B等2人、任務創建時間為“10-18 17:30”、截止時間為“10月30日 週一 16:00”、回覆狀態為“暫無回覆”、完成狀態為“0/2已完成”。 圖10是一示例性實施例提供的一種基於創建者的會話介面的示意圖。基於用戶A在上述實施例中創建的群任務，企業微信用戶端1可以將該群任務發佈在群組AA的會話介面300中；例如圖10所示，該群任務可以被作為用戶A發出的一條消息，被展示於會話介面300中。當然，使用者A還可以透過觸發會話介面300中的群任務圖示301，切換至如圖9所示的群任務管理介面400，以查看該消息對應的群任務404。 圖11是一示例性實施例提供的一種基於執行者的會話介面的示意圖。假定在手機14運行的企業微信用戶端2上，可以向用戶B呈現出如圖11所示的會話介面1100，該會話介面1100展示出由使用者A發出的消息1101，該消息1101的內容即為如圖9所示的群任務404。當然，由於消息1101的展示區域較小，因而可以僅示出該群任務404的部分資訊，比如任務主題、執行者、截止時間等。 當檢測到使用者B觸發消息1101時，可以向用戶B展示相應群任務的任務詳情。例如，圖12是一示例性實施例提供的一種任務詳情介面的示意圖；基於對消息1101的觸發操作，可以切換至如圖12所示的任務詳情介面1200，以在該任務詳情介面1200上展示出相應群任務的任務詳情，包括任務主題為“Y專案設計稿”、該群任務的創建者為用戶A、創建時刻為“剛剛(如1分鐘之內)”、截止時間為“10月30日 週一 16:00”、剩餘天數為“剩餘12天”、執行者為用戶B和使用者C、完成狀態為“未完成”、相關群組為“群組AA”等。 其中，在任務主題“Y專案設計稿”的左側包括狀態設置選項，該狀態設置選項在圖12中呈現為“□”；當該狀態設置選項展示為如圖12所示時，表明相應的群任務的完成狀態為“未完成”；當使用者B觸發該狀態設置選項時，可以在“□”內添加標記“√”，且相應的群任務的完成狀態切換為“已完成”；當然，用戶B可以透過觸發“已完成”狀態的狀態設置選項，使得“□”內的標記“√”被取消，從而將相應的群任務的完成狀態切換為“未完成”。 在一實施例中，任務詳情介面1200展示的“來自群組：群組AA”可以被設置為可觸發狀態，使得使用者B可以透過觸發該顯示內容，快速切換至群組AA對應的會話介面(比如上述的會話介面1100)。 在一實施例中，任務詳情介面1200可以包括如圖12所示的子任務創建選項(即“+子任務”)，使得用戶B可以據此創建與群任務“Y項目設計稿”相關的一個或多個子任務。 在一實施例中，群組AA的會話介面1100可以包括群任務圖示1102，與上述會話介面300中的群任務圖示301相類似的，用戶B可以透過觸發該群任務圖示1102切換至如圖13所示的群任務管理介面1300，以查看和管理群組AA中的群任務。 在一實施例中，對應於圖11所示的消息1101，群任務管理介面1300可以示出相應的群任務1301，且該群任務管理介面1300還可以示出其他的群任務1302、群任務1303等。其中，群任務管理介面1300可以包括群任務創建區域1304，可供使用者B創建群組AA內的群任務，該過程與用戶A的上述創建過程類似，此處不再贅述。 在一實施例中，群任務管理介面1300可以示出群組AA中所有的群任務，比如群任務1301、群任務1302是用戶B作為執行者的群任務，而群任務1303是與用戶B無關(用戶B既不是創建者，也不是執行者或其他角色)的群任務，但是都可以在該群任務管理介面1300上予以展示。 其中，由於群任務1301-1302與用戶B 相關，因而可以向用戶B提供針對相應群任務的狀態設置選項，該狀態設置選項呈現為與圖12中相同的“□”；當該狀態設置選項展示為如圖13所示時，表明相應的群任務的完成狀態為“未完成”；當使用者B觸發該狀態設置選項時，可以在“□”內添加標記“√”，且相應的群任務的完成狀態切換為“已完成”；當然，用戶B可以透過觸發“已完成”狀態的狀態設置選項，使得“□”內的標記“√”被取消，從而將相應的群任務的完成狀態切換為“未完成”。而由於群任務1303與用戶B無關，因而可以不向用戶B提供針對相應群任務的狀態設置選項，或者向使用者B提供如圖13所示的不可操作的狀態設置選項“■”，以避免用戶B誤操作。 在一實施例中，群任務管理介面1300展示的群任務可以包括多種類型，比如尚未完成的群任務、已完成的群任務、已關閉的群任務等，用戶B可以選擇展示所有類型的群任務，也可以選擇僅展示部分類型的群任務，本說明書並不對此進行限制。例如，圖13中選擇僅展示出尚未完成的群任務，因而遮罩了已完成的群任務、已關閉的群任務等其他類型的群任務。 對於群組AA中的其他群組成員，當作為群任務的創建者時，可以參考上述用戶A的相關描述，而作為群任務的執行者或無關人員時，可以參考上述用戶B的相關描述，此處不再一一贅述。 當群組AA中的群任務數量較多時，如果僅僅依靠查看群組AA的群任務管理介面，可能難以高效地實施群任務管理操作，需要手動翻看各個群任務。因此，本說明書提供了針對群任務的高效管理方案。圖14是一示例性實施例提供的一種實現群任務管理的示意圖；如圖14所示，假定在使用者A對應的會話介面1400中，使用者A可以在該會話介面1400內發出針對群任務的詢問消息1401，該過程與發送消息的過程相同。 在一實施例中，詢問消息1401可以包括兩個部分：標識內容和詢問內容。其中，標識內容用於由企業微信用戶端1或企業微信服務端(由企業微信用戶端1發送至企業微信服務端)進行辨別，以將詢問消息1401與普通的消息予以區分，比如該標識內容可以包括“@群任務”，當然本說明書並不限制該標識內容的具體形式。詢問內容可以包括如圖14所示的“現在群任務進度怎麼樣？”，即用戶A實際希望針對群任務發起詢問的內容。 在一實施例中，當企業微信用戶端1識別出標識內容時，可以將詢問消息1401或詢問內容透過區別於普通的消息的方式(比如添加特定的報文標識、採用特定的傳輸埠、採用特定的傳輸鏈路等，本說明書並不對此進行限制)發送至企業微信服務端，使得企業微信服務端並不將其轉發至其他群組成員，而是針對詢問內容予以解析，並返回相應的詢問結果。在另一實施例中，企業微信服務端在接收到企業微信用戶端1發送的詢問消息1401後，可以自動識別出標識內容和詢問內容，並透過解析該詢問內容，返回相應的詢問結果。 在一實施例中，詢問結果可以被採用消息的形式呈現給使用者A。例如圖14所示，詢問結果可以被包含於消息1402中，由企業微信用戶端1接收並展示於會話介面1400中，而該消息1402的發送方可以被設置為區別於群組AA的群組成員的特殊發送方，比如圖14所示的“機器人”或其他形式，本說明書並不對此進行限制。 在一實施例中，當用戶A向企業微信服務端發起詢問時，詢問消息1401不會被發送至群組AA的其他群組成員，且包含詢問結果的消息1402僅被發送至用戶A、同樣不會被發送至群組AA的其他群組成員，從而避免對其他群組成員造成干擾。當然，在一些實施例中，詢問消息1401和消息1402均可以被發送至所有群組成員，本說明書並不對此進行限制。 使用者A可以詢問與群任務相關的任何內容，企業微信服務端均可以做出相應的解答與回饋。比如除了圖14中較為籠統的總體進度之外，還可以針對特定的一個或多個群組成員進行詢問。例如圖15所示，使用者A在會話介面1500中發出的詢問消息1501可以為“@群任務 B的群任務進度”，包括標識內容“@群任務”和詢問內容“B的群任務進度”，以使得企業微信服務端可以針對使用者B在群組AA中的群任務而確定相應的處理進度資訊，這些資訊可以被包含於消息1502而返回至企業微信用戶端1，由企業微信用戶端1呈現至用戶A。 在一實施例中，可以針對特定類型的群任務進行詢問。例如圖16所示，使用者A在會話介面1600中發出的詢問消息1601可以為“@群任務 未完成的群任務”，包括標識內容“@群任務”和詢問內容“未完成的群任務”，以使得企業微信服務端可以確定群組AA中的未完成群任務，並將相關資訊基於消息1602而返回至企業微信用戶端1，由企業微信用戶端1呈現至用戶A。 在一實施例中，可以針對特定截止期限的群任務進行詢問。例如圖17所示，使用者A在會話介面1700中發出的詢問消息1701可以為“@群任務 截止期限在11月之前的未完成群任務”，包括標識內容“@群任務”和詢問內容“截止期限在11月之前的未完成群任務”，以使得企業微信服務端可以根據群組AA中群任務的截止日期和完成狀態，確定出截止日期早於11月1日且處於未完成狀態的群任務，並將相關資訊基於消息1702而返回至企業微信用戶端1，由企業微信用戶端1呈現至用戶A。 除了對群組成員的主動詢問進行回應之外，企業微信服務端還可以向群組成員主動推送與群任務相關的通知消息，以便於群組成員及時瞭解相關資訊。例如，圖18是一示例性實施例提供的一種主動推送與群任務相關的通知消息的示意圖；如圖18所示，企業微信服務端確定使用者A存在兩個未完成的群任務時，可以向用戶A對應的企業微信用戶端1發送相應的通知消息1801，以由企業微信用戶端1在會話介面1800中示出該通知消息1801，從而實現對用戶A的主動提醒。再例如，圖19是一示例性實施例提供的另一種主動推送與群任務相關的通知消息的示意圖；如圖19所示，企業微信服務端確定使用者B存在一個即將到達截止期限(比如與截止期限相隔不超過3天)的群任務時，可以向用戶B對應的企業微信用戶端2發送相應的通知消息1901，以由企業微信用戶端2在會話介面1900中示出該通知消息1901，從而實現對用戶B的主動提醒。 在如圖18所示的實施例中，通知消息1801可以僅發送至用戶A，而不發送至群組AA中的其他群組成員；而在如圖19所示的實施例中，通知消息1901可以被發送至群組AA的所有群組成員，並透過在該通知消息1901中添加針對使用者B的單獨通知提示標識(如“@B”)，使得即便群組AA被遮罩(比如被啟動“免打擾”功能)，企業微信用戶端2仍然可以向用戶B發出接收提醒，從而避免用戶B由於某些原因而忽略該通知消息1901。 圖20是一示例性實施例提供的又一種主動推送與群任務相關的通知消息的示意圖；如圖20所示，企業微信服務端在接收到諸如用戶B、用戶C等群組成員對於群任務的管理操作時，可以向相關群任務的關聯者(如創建者或其他執行者等)或群組AA的所有群組成員對應的企業微信用戶端發送相應的通知消息，比如企業微信用戶端1可以收到相應的通知消息2001-2002，以由企業微信用戶端1在會話介面2000中示出該通知消息2001-2002，從而實現對用戶A等群組成員的主動提醒。 在一實施例中，當檢測到群組成員觸發上述實施例中的消息1402~1702或通知消息1801~2001時，可以實施下述操作：一種情況下，切換至群組AA的群任務管理介面，由群組成員進行查看；另一種情況下，切換至群組AA的群任務管理介面，並對上述消息中涉及的群任務進行標記，以便於群組成員進行查看；又一種情況下，切換至任務資訊查看介面，僅示出上述消息涉及的群任務的資訊(概要資訊或者詳情資訊)；或者，還可以採用其他方案，本說明書並不對此進行限制。 在一實施例中，除了直接在如圖4所示的群任務創建區域401中進行手動輸入，以創建相應的群任務之外，還可以向群組AA的群組成員提供群任務範本，從而能夠更為快速、便捷地創建群任務。例如，圖21是一示例性實施例提供的一種範本選擇介面的示意圖；群組AA的群組成員可以透過對應的企業微信用戶端，查看到如圖21所示的範本選擇介面2100，該範本選擇介面2100可以包括若干備選的群任務範本對應的範本內容佈局預覽圖。進一步地，還可以透過觸發範本選擇介面2100中的“更多範本”選項，以查看其他暫時未展示的群任務範本。 在一實施例中，群任務範本可以由企業微信的開發方提供，或者由專門的協力廠商提供。在另一實施例中，群任務範本可由企業微信的使用者創建後，上傳至企業微信服務端，並由企業微信服務端展示於範本選擇介面2100中，以供群組AA的群組成員或其他群組的群組成員進行查看、使用。 圖22是一示例性實施例提供的一種範本綁定介面的示意圖。假定群組AA的群組成員選取了範本選擇介面2100中的“XX行業群任務範本”，可以在如圖22所示的範本綁定介面2200中，示出相應的範本內容佈局預覽圖2201，以供該群組成員進行查看。當該群組成員屬於該群組AA中的管理成員時，即該群組成員具備針對該群組AA的群任務範本管理許可權，範本綁定介面2200可以向該群組成員提供綁定選項2202，使得該群組成員可以透過觸發該綁定選項2202，將上述的“XX行業群任務範本”綁定至該群組AA，則該群組AA中的所有群組成員均可以透過該“XX行業群任務範本”快捷地創建相應的群任務。 圖23是一示例性實施例提供的另一種範本綁定介面的示意圖。與圖22類似地，當群組AA的群組成員選取了範本選擇介面2100中的“XX行業群任務範本”時，可以在如圖23所示的範本綁定介面2300中，示出相應的範本內容佈局預覽圖2301，以供該群組成員進行查看。當該群組成員並非該群組AA中的管理成員時，即該群組成員並不具備針對該群組AA的群任務範本管理許可權，範本綁定介面2300可以向該群組成員提供綁定請求選項2302，使得該群組成員可以透過觸發該綁定選項2302，向該群組AA中的管理成員發送綁定請求消息，而該管理成員可以透過觸發該綁定請求消息，將上述的“XX行業群任務範本”綁定至該群組AA，則該群組AA中的所有群組成員均可以透過該“XX行業群任務範本”快捷地創建相應的群任務。 圖24是一示例性實施例提供的另一種群任務管理介面的示意圖。當群組AA存在綁定的群任務範本時，在如圖24所示的群任務管理介面2400中，除了可以向用戶A提供群任務創建區域2401(相當於圖4所示的群任務創建區域401)，使得使用者A可以在該群任務創建區域2401中透過手動輸入而創建相應的群任務，該群任務管理介面2400還可以包括群任務範本觸發選項2402。假定上述的“XX行業群任務範本”被綁定至群組AA，當檢測到使用者A觸發群任務範本觸發選項2402時，可以調用該“XX行業群任務範本”，從而透過對該“XX行業群任務範本”中的變數參數進行配置，即可快捷地創建符合“XX行業”需求的群任務。 在一實施例中，群任務管理介面2400可以包括群任務批量導入選項2403，以供用戶A快速、批量導入群任務，而無需一一手動創建。其中，使用者A可以事先在記事本、表格工具中記載群任務的描述資訊，比如任務主題、任務截止時刻、任務執行者等，並生成記錄有這些描述資訊的檔，比如文字檔、表格檔等；然後，透過觸發群任務批量導入選項2403，並選取上述的文字檔或表格檔，企業微信用戶端1或企業微信服務端可以解析檔中記錄的群任務的描述資訊，並據此批量創建相應的群任務，能夠有效地提升用戶A對群任務的創建效率。 圖25是一示例性實施例提供的一種設備的示意結構圖。請參考圖25，在硬體層面，該設備包括處理器2502、內部匯流排2504、網路介面2506、記憶體2508以及非易失性記憶體2510，當然還可能包括其他業務所需要的硬體。處理器2502從非易失性記憶體2510中讀取對應的電腦程式到記憶體2508中然後運行，在邏輯層面上形成群組任務的資訊獲取裝置。當然，除了軟體實現方式之外，本說明書一個或多個實施例並不排除其他實現方式，比如邏輯器件抑或軟硬體結合的方式等等，也就是說以下處理流程的執行主體並不限定於各個邏輯單元，也可以是硬體或邏輯器件。 請參考圖26，在軟體實施方式中，該群組任務的資訊獲取裝置可以包括： 發送單元2601，透過群組對應的會話發送消息，所述消息包含標識內容和針對所述群組內的群組任務的詢問內容，所述標識內容用於指示伺服器對所述詢問內容予以答覆； 答覆內容接收單元2602，接收所述伺服器針對所述詢問內容返回的答覆內容，所述答覆內容包括所述群組任務的資訊。 可選的，所述發送單元2601具體用於： 當所述會話對應的會話介面檢測到使用者輸入資訊時，將所述使用者輸入資訊作為所述消息的消息內容進行發送； 或者，按照使用者設定的消息內容和發送週期，自動發送所述消息。 可選的， 所述消息包括以下至少之一：文字消息或音訊消息； 所述答覆內容包括以下至少之一：文字消息或音訊消息。 可選的，所述群組任務的創建者、執行者均為所述群組的群組成員。 可選的，所述群組任務由所述群組的群組成員在所述群組的關聯功能介面中創建生成。 可選的，所述群組任務的執行者由所述群組任務的創建者透過在所述群組的群組成員中實施選取操作而確定； 其中，當所述群組任務的創建者未實施所述選取操作時，所述群組的所有群組成員被預設為所述群組任務的執行者。 可選的，當任一任務的創建介面與所述群組無關，且所述任一任務的創建者、執行者均為所述群組的群組成員時，所述任一任務被確定為所述群組內的群組任務。 可選的，當所述消息包含所述標識內容時，所述消息和所述答覆內容僅對所述消息的發送方可見、對所述群組中的其他群組成員不可見。 可選的，還包括： 通知接收單元2603，接收所述伺服器自動發送的針對所述群組任務的通知消息；所述通知消息包括以下至少之一： 週期性統計資訊、針對尚未完成的群組任務的提示資訊、針對臨近完成期限的群組任務的提示資訊、針對已完成的群組任務的完成提示資訊。 可選的，還包括： 切換單元2604，當檢測到針對所述通知消息的觸發操作時，切換至與所述通知消息相關的群組任務的資訊展示介面。 可選的，所述群組任務由創建者透過對群組任務範本進行配置而生成。 可選的，所述群組任務範本被預先綁定至所述群組。 可選的，還包括： 導入單元2605，在所述群組內導入任務記錄檔，所述任務記錄檔中記錄有至少一項群組任務的描述資訊； 創建單元2606，根據所述任務記錄檔中記錄的描述資訊，批量創建與所述群組相關的群組任務。 可選的，所述任務記錄檔包括下述任一：文字檔、表格檔。 上述實施例闡明的系統、裝置、模組或單元，具體可以由電腦晶片或實體實現，或者由具有某種功能的產品來實現。一種典型的實現設備為電腦，電腦的具體形式可以是個人電腦、膝上型電腦、蜂窩電話、相機電話、智慧型電話、個人數位助理、媒體播放機、導航設備、電子郵件收發設備、遊戲控制台、平板電腦、可穿戴設備或者這些設備中的任意幾種設備的組合。 在一個典型的配置中，電腦包括一個或多個處理器 (CPU)、輸入/輸出介面、網路介面和記憶體。 記憶體可能包括電腦可讀媒體中的非永久性記憶體，隨機存取記憶體 (RAM) 和/或非易失性記憶體等形式，如唯讀記憶體 (ROM) 或快閃記憶體(flash RAM)。記憶體是電腦可讀媒體的示例。 電腦可讀媒體包括永久性和非永久性、可移動和非可移動媒體可以由任何方法或技術來實現資訊儲存。資訊可以是電腦可讀指令、資料結構、程式的模組或其他資料。電腦的儲存媒體的例子包括，但不限於相變記憶體 (PRAM)、靜態隨機存取記憶體 (SRAM)、動態隨機存取記憶體 (DRAM)、其他類型的隨機存取記憶體 (RAM)、唯讀記憶體 (ROM)、電可擦除可程式設計唯讀記憶體 (EEPROM)、快閃記憶體或其他記憶體技術、唯讀光碟唯讀記憶體 (CD-ROM)、數位多功能光碟 (DVD) 或其他光學儲存、磁盒式磁帶、磁片儲存、量子記憶體、基於石墨烯的儲存媒體或其他磁性存放裝置或任何其他非傳輸媒體，可用於儲存可以被計算設備訪問的資訊。按照本文中的界定，電腦可讀媒體不包括暫存電腦可讀媒體 (transitory media)，如調製的資料信號和載波。 還需要說明的是，術語“包括”、“包含”或者其任何其他變體意在涵蓋非排他性的包含，從而使得包括一系列要素的過程、方法、商品或者設備不僅包括那些要素，而且還包括沒有明確列出的其他要素，或者是還包括為這種過程、方法、商品或者設備所固有的要素。在沒有更多限制的情況下，由語句“包括一個……”限定的要素，並不排除在包括所述要素的過程、方法、商品或者設備中還存在另外的相同要素。 上述對本說明書特定實施例進行了描述。其它實施例在所附申請專利範圍的範圍內。在一些情況下，在申請專利範圍中記載的動作或步驟可以按照不同於實施例中的順序來執行並且仍然可以實現期望的結果。另外，在附圖中描繪的過程不一定要求示出的特定順序或者連續順序才能實現期望的結果。在某些實施方式中，多工處理和並行處理也是可以的或者可能是有利的。 在本說明書一個或多個實施例使用的術語是僅僅出於描述特定實施例的目的，而非旨在限制本說明書一個或多個實施例。在本說明書一個或多個實施例和所附申請專利範圍中所使用的單數形式的“一種”、“所述”和“該”也旨在包括多數形式，除非上下文清楚地表示其他含義。還應當理解，本文中使用的術語“和/或”是指並包含一個或多個相關聯的列出專案的任何或所有可能組合。 應當理解，儘管在本說明書一個或多個實施例可能採用術語第一、第二、第三等來描述各種資訊，但這些資訊不應限於這些術語。這些術語僅用來將同一類型的資訊彼此區分開。例如，在不脫離本說明書一個或多個實施例範圍的情況下，第一資訊也可以被稱為第二資訊，類似地，第二資訊也可以被稱為第一資訊。取決於語境，如在此所使用的詞語“如果”可以被解釋成為“在……時”或“當……時”或“回應於確定”。 以上所述僅為本說明書一個或多個實施例的較佳實施例而已，並不用以限制本說明書一個或多個實施例，凡在本說明書一個或多個實施例的精神和原則之內，所做的任何修改、等同替換、改進等，均應包含在本說明書一個或多個實施例保護的範圍之內。Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. Implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of this specification. Rather, they are merely examples of apparatuses and methods consistent with aspects of one or more embodiments of the present specification, as detailed in the appended claims. It should be noted that in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or less steps 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; multiple steps described in this specification may also be combined into a single step in other embodiments describe. Fig. 1 is a schematic structural diagram of a group task system provided by an exemplary embodiment. As shown in FIG. 1 , 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 . The server 11 may be a physical server including an independent host, or the server 11 may be a virtual server carried by a cluster of hosts. During operation, the server 11 can run the program on the server side of a certain application to realize the relevant business functions of the application. For example, when the server 11 runs the program of the mobile group office platform, it can The server side of the group office platform. In the technical solution of one or more embodiments of this specification, the server 11 can cooperate with the client terminal running on the mobile phone 13-15 to realize the information acquisition solution based on group tasks. In this embodiment, the mobile group office platform can not only realize the communication function, but also serve as an integrated functional platform for many other functions, such as for approval events (such as leave, application for office supplies, financial and other approval events), attendance events, etc. One or more embodiments of this specification do not limit the processing of group internal events such as , task events, and log events, and the processing of group external events such as meal ordering and purchasing. More specifically, the mobile group office platform can be carried by instant messaging applications in related technologies, such as enterprise instant messaging (Enterprise Instant Messaging, EIM) applications, such as Skype For Business ® , Microsoft Teams ® , Yammer ® , Workplace ® , Slack ® , Enterprise WeChat® , Fenxiang Sales® , Enterprise Fetion® , Enterprise Yixin® , etc. Of course, the instant messaging function is only one of the communication functions supported by the mobile group office platform, and the mobile group office platform can also realize other functions such as the above, which will not be repeated here. Cell phones 13-15 are just one type of electronic device that may be used by a user. In fact, users can obviously also use electronic devices such as the following types: tablet devices, notebook computers, handheld computers (PDAs, Personal Digital Assistants), wearable devices (such as smart glasses, smart watches, etc.), etc., this manual One or more embodiments are not limited in this regard. During operation, the electronic device can run a program on the client side of an application to realize the relevant business functions of the application. For example, when the electronic device runs a program on a mobile group office platform, The client side of the group office platform. It should be pointed out that: the client application program of the mobile group office platform can be pre-installed on the electronic device, so that the client can be started and run on the electronic device; of course, when the online "user When using the "client", the client can be obtained and run without installing the corresponding application program on the electronic device. As for the network 12 that interacts between the mobile phones 13-15 and the server 11, it 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. At the same time, electronic devices such as mobile phones 13-15 can also communicate and interact through the network 12, such as establishing a single chat session between any two electronic devices; or, multiple users can participate in the same group. Multiple electronic devices can participate in the session corresponding to the same group, so that any user can send communication messages to all other users in the session through his electronic device. Fig. 2 is a flow chart of a method for obtaining information on a group task provided by an exemplary embodiment. As shown in Figure 2, the method is applied to electronic devices, and may include the following steps: Step 202, send a message through a session corresponding to the group, the message includes identification content and query content for group tasks in the group , the identification content is used to instruct the server to respond to the inquiry content. In an embodiment, when the session interface corresponding to the session detects the user input information, the user input information may be sent as the message content of the message, that is, the message can be obtained by the user's manual input. In one embodiment, the message can be automatically sent according to the message content and sending cycle set by the user. For example, the sending cycle can include daily, weekly, monthly, etc., which can be set by the user according to actual needs. Among them, the user can set one or more sending cycles, and each cycle corresponds to the same or different messages; A message of the second content is automatically sent. In an embodiment, the identification content may include any predefined content, which is not limited in this specification. For example, the identification content can be in the form of "special character + name". For example, the special character can be @, # and other uncommon characters, and the name can be pre-agreed to refer to the server, such as a server or a robot. Information, so the identification content can be such as "@server", "#编辑#" and so on. For another example, the identification content may directly use pre-agreed information used to refer to the server, such as "group secretary". In one embodiment, the user end of the mobile group office platform can be run on the electronic device, and the user end can provide group communication functions and task management functions, and the group communication function realizes group creation and group member communication Inter-communication operations, and task management is realized by the task management function. In one embodiment, group tasks are different from other types of tasks. Group tasks can be used by users to implement management operations such as creation and viewing in the functional interface related to the group, which is convenient for creators and executors of group tasks. Linked users can communicate quickly based on the conversations of the group. In an embodiment, associated users such as creators and executors of group tasks may all be group members of the group, so that these associated users can realize quick communication based on the conversations of the group. In one embodiment, the group task can be created by the group members of the group in the associated function interface of the group. For example, the associated function interface may include a task management interface, which allows group members to create new group tasks, view created group tasks, etc., and the group session interface may include the task management interface , so that group members can quickly switch between the task management interface and the conversation interface. Of course, the associated functional interface may also include other forms of functional interfaces related to groups, which is not limited in this specification. In an embodiment, the executor of the group task can be determined by the creator of the group task by performing a selection operation among the group members of the group, for example, the creator can select at least one group Members as the executors of the group task; wherein, when the creator is creating a group task, only the group member list of the group can be provided to the creator, so that both the creator and the executor are restricted in the group members of the group. In addition, if the creator of the group task does not perform the selection operation, all group members of the group are preset as executors of the group task. In one embodiment, only when the creator is a group member in the group, the creator can enter the functional interface related to the group to complete the creation operation of the group task. In one embodiment, when the creation interface of any task has nothing to do with the group, and the creator and executor of any task are group members of the group, any task can be Is determined to be a group task within the group. For example, although the creator has not created a task in the functional interface related to the group, if the creator and the selected executor belong to the same group, the task can be set as a group related to the same group task; wherein, the setting operation can be an automatic operation, or a setting reminder can be initiated to the creator, and the setting operation can be implemented when the creator responds to the setting reminder. In an embodiment, group members of a group may have the same group affiliation information (for example, belong to the same enterprise), that is, the group is an intra-group group. In an embodiment, group members of a group may not have identical group affiliation information (for example, they belong to multiple companies), that is, the group is a cross-group group. In an embodiment, the group may have nothing to do with the group, such as a group created between relatives or friends. Step 204, receiving the reply content returned by the server to the inquiry content, the reply content including the information of the group task. In an embodiment, the content of the message and the reply may be of any type, which is not limited in this specification. For example, the message may include at least one of the following: a text message or an audio message, and the reply content may include at least one of the following: a text message or an audio message. In one case, the message and the reply content may be of the same type, for example, when the message is a text message, the reply content is also a text message, and when the message is an audio message, the reply content is also an audio message. In another case, there may be no type association between the message and the reply content. For example, when the message is a text message, the reply content may be a text message or an audio message. In an embodiment, when the message contains the identification content, the message and the reply content may only be visible to the sender of the message, but invisible to other group members in the group, Therefore, unnecessary interference to other group members is avoided while satisfying the inquiry requirement of the sender. In an embodiment, a notification message for the group task automatically sent by the server may be received; for example, the notification message may include at least one of the following: periodic statistical information, group task that has not been completed , reminder information for group tasks that are approaching completion deadlines, completion reminder information for completed group tasks, etc., this manual does not limit this. In an embodiment, when a trigger operation for the notification message is detected, it may switch to the information display interface of the group task related to the notification message, so as to view the summary information or detailed information of the group task . In one embodiment, the group task can be generated by the creator by configuring the group task template. In other words, several alternative group task templates can be created in advance, for example, these group task templates are applicable to different positions, different scenarios, different industries or different purposes, etc., so that the creator can select the appropriate group task template according to actual needs After that, by configuring the configurable variables in the group task template, you can quickly generate a group task that meets the actual needs, simplifying the creator's operation. At the same time, in the process of creating group tasks, the group task template can also play a certain teaching and guiding role for the creators, especially for creators who create group tasks for the first time or rarely, it can assist the creators Complete the rapid creation of group tasks, thereby lowering the learning threshold for creators. In one embodiment, all group task templates are freely available to the creator. In another embodiment, the group task template is pre-bound to the group, that is, the creator can only configure the group task template bound to the group, but not other group task templates. The task templates can be used at will, thus realizing the use management of group task templates. In one embodiment, group task templates can be managed by management members such as group owners and administrators, such as binding the group task template to the group, or unbinding the group task template from the group . Correspondingly, group members can use the group task template bound to the group to quickly create corresponding group tasks. In an embodiment, the group task template may be provided by the developer of the above-mentioned communication application or mobile group office platform for users of the communication application or mobile group office platform to acquire and use. In another embodiment, the group task template can be created by users of the above-mentioned communication application or mobile group office platform, and shared with other users for use; for example, the communication application or mobile group office platform can provide group A sharing platform for group task templates, through which users can share the group task templates created by themselves, and also obtain group task templates shared by other users. In an embodiment, a task record file may be imported into the group, and the task record file records description information of at least one group task; then, according to the description information recorded in the task record file, Create group tasks related to the group in batches. Wherein, the task record file may include any of the following: text file, table file, etc., which is not limited in this specification. By pre-recording the description information of group tasks in the task record file, group members can quickly and batch create corresponding group tasks by importing the task record file into the group, without the need for group members to separate and separate Creating each group task helps to improve the efficiency of creating group tasks. In one embodiment, group members can specify the group task template to be used when importing the task record file, so that the created group tasks are all generated based on the group task template, which helps to ensure that the generated group tasks Tasks meet the actual needs of the group members in terms of style, format, and so on. For ease of understanding, the technical solutions of one or more embodiments of this specification will be described by taking the enterprise instant messaging application "Enterprise WeChat" as an example. Assume that the mobile phone 13 and the mobile phone 14 run on the enterprise WeChat client, and the server 11 runs on the enterprise WeChat server, and the mobile phone 13 is logged in with the registered account of user A, so that the mobile phone 13 is configured as the enterprise WeChat client 1, and the mobile phone 14 The registered account of user B is logged on the mobile phone 14, so that the mobile phone 14 is configured as the enterprise WeChat client terminal 2. Wherein, it is assumed that user A and user B are both group members of group AA, and group task management operations can be realized based on the group AA. Fig. 3 is a schematic diagram of a group conversation interface provided by an exemplary embodiment. Assume that on the enterprise WeChat client terminal 1 running on the mobile phone 13, a conversation interface 300 as shown in FIG. 3 can be presented to user A, and the conversation interface 300 corresponds to the group AA in which user A belongs. The conversation interface 300 may include a group task icon 301 as shown in FIG. Switch to the group task management interface 400 shown in FIG. 4 . Fig. 4 is a schematic diagram of a group task management interface provided by an exemplary embodiment. In the embodiments of this specification, the group task and the group task are different names of the same type of task, which is not limited in this specification. In the group task management interface 400 shown in FIG. 4 , a group task creation area 401 may be included, and the group task creation area 401 is available for the user A to create a new group task in the group AA. The group task management interface 400 can also display the group tasks created in the group AA, such as the group task 402 and the group task 403 shown in FIG. 4 . In one embodiment, the task theme of the group task 402 is "Complete the design proposal before Tuesday", the creator is user A, the executor is user B, the task creation time is "10-18 15:30", and the deadline is "Tuesday, October 24th at 18:00", the reply status is "No reply", and the completion status is "B not completed". Of course, in other embodiments, only part of the above content may be included, or other types may also be included task information, this manual does not limit it. Similarly, the task subject of group task 403 is "Project X Product Solution", the creator is user C, the executor is user A and other 3 people, the task creation time is "10-12 14:20", and the deadline is "10 12:00 on Friday, 20th March", the reply status is "2 replies", and the completion status is "1/3 completed". In an embodiment, FIG. 4 may only show partial information of the group task 402 and the group task 403 , and the user A may view the task details by triggering the group task 402 or the group task 403 . For example, the specific reply content of "2 replies" in the group task 403, the information of the 3 executors of "A and other 3 people", the information of the completed and unfinished ones in "1/3 people have completed". Information, etc., can be presented in detail in the task details. In an embodiment, the input box of the group task creation area 401 may display prompt information such as "add a group task..." to assist user A to complete the operation of creating the group task. For example, FIG. 5 is a schematic diagram of setting the task theme of a group task provided by an exemplary embodiment; by triggering the input box in the group task creation area 401, user A can input the task of the group task to be created in the input box Theme, for example, the task theme can be the "Y project design draft" shown in Figure 5 or any other content. In an embodiment, the group task creation area 401 may include a executor setting icon 501 for the user A to set a executor for the group task to be created. For example, FIG. 6 is a schematic diagram of an executor who sets a group task provided by an exemplary embodiment; when a trigger operation for the executor setting icon 501 is detected, it can switch to the executor setting interface as shown in FIG. 6 600. The executor setting interface 600 may include a candidate user list 601 on the right and a selected user list 602 on the left. Among them, the candidate user list 601 may include all group members of the group AA, such as user A, user B, user C, user D, and user E; assuming that user A selects user B and user C as executors, the user B. User C will have a check mark “√” in the corresponding selection box “○” in the candidate user list 601 , and user B and user C will be added to the selected user list 602 on the left. When user A wishes to cancel the selection of user B or user C, the corresponding selection box "○" can be retriggered; or, in the selected user list 602, user B and user C both have corresponding deletion marks "×" , you can deselect the corresponding user by triggering the delete mark "×". Fig. 7 is a schematic diagram of a group task management interface with set executors provided by an exemplary embodiment. After user A selects the executor, the executor setting icon 501 shown in FIG. 5 can be replaced to remind user A that the selection operation has been performed, so as to avoid forgetting after performing other operations. For example, when user A selects user B and user C as executors, the executor setting icon 501 shown in FIG. In order to enable user A to quickly determine at least a part of the executors that have been selected. Of course, since the group task creation area 401 is often limited, there may be a certain limit to the number of avatars displayed, for example, no more than 3 avatars, and the excess avatars may not be displayed or omitted with "...". In an embodiment, the group task creation area 401 may include a deadline setting icon 502 for user A to set a deadline for the group task to be created. For example, FIG. 8 is a schematic diagram of setting deadlines for group tasks provided by an exemplary embodiment; when a trigger operation on the deadline setting icon 502 is detected, it can switch to the deadline setting interface 800 as shown in FIG. 8 , The deadline setting interface 600 can include a date selection area and a time setting area, which can be used for the user to set the date and time as the deadline respectively, for example, it can be set to 16:00 on October 30, 2017 as shown in FIG. 8 . Wherein, the deadline setting interface 800 may provide an option of "no deadline" as shown in FIG. 8 , so that no deadline is set for the corresponding group task. Similar to the executor setting diagram 501 , after user A sets the deadline for the group task, the deadline setting diagram 502 can also be replaced to remind user A, which will not be repeated here. Fig. 9 is a schematic diagram of another group task management interface provided by an exemplary embodiment. Based on the above operations of user A, the created new group task can be displayed in the group task management interface 400 shown in FIG. 9 , for example, the new group task can be the group task 404 shown in FIG. 9 . Among them, the task theme of group task 404 is "Y project design draft", the creator is user A, the executor is user B and other two people, the task creation time is "10-18 17:30", and the deadline is "October Monday, 30th at 16:00", the reply status is "No reply", and the completion status is "0/2 completed". Fig. 10 is a schematic diagram of a creator-based session interface provided by an exemplary embodiment. Based on the group task created by user A in the above embodiment, the enterprise WeChat client 1 can publish the group task in the conversation interface 300 of group AA; for example, as shown in FIG. A message is displayed in the session interface 300 . Of course, user A can switch to the group task management interface 400 shown in FIG. 9 by triggering the group task icon 301 in the conversation interface 300 to view the group task 404 corresponding to the message. Fig. 11 is a schematic diagram of an actor-based session interface provided by an exemplary embodiment. Assume that on the enterprise WeChat client 2 running on the mobile phone 14, a conversational interface 1100 as shown in FIG. 11 can be presented to user B. The conversational interface 1100 shows a message 1101 sent by user A. It is a group task 404 as shown in FIG. 9 . Of course, since the display area of the message 1101 is small, only part of the information of the group of tasks 404 may be shown, such as task subject, executor, deadline, and the like. When it is detected that the user B triggers the message 1101, the task details of the corresponding group task may be displayed to the user B. For example, FIG. 12 is a schematic diagram of a task details interface provided by an exemplary embodiment; based on a trigger operation on a message 1101, it is possible to switch to the task details interface 1200 shown in FIG. 12 to display on the task details interface 1200 Display the task details of the corresponding group task, including the task subject as "Y project design draft", the creator of the group task as user A, the creation time as "just (such as within 1 minute)", and the deadline as "October 30 Monday at 16:00", the remaining days are "12 days left", the executors are user B and user C, the completion status is "unfinished", the related group is "group AA", etc. Among them, the status setting option is included on the left side of the task theme "Y project design draft", and the status setting option is presented as "□" in Figure 12; when the status setting option is displayed as shown in Figure 12, it indicates that the corresponding group The completion status of the task is "unfinished"; when user B triggers this status setting option, a mark "√" can be added in "□", and the completion status of the corresponding group task is switched to "completed"; of course, User B can cancel the mark "√" in "□" by triggering the status setting option of "completed", thereby switching the completion status of the corresponding group task to "unfinished". In an embodiment, the "from group: group AA" displayed on the task details interface 1200 can be set to a triggerable state, so that user B can quickly switch to the conversation interface corresponding to group AA by triggering the displayed content (such as the above-mentioned session interface 1100). In an embodiment, the task details interface 1200 may include a subtask creation option (namely "+subtask") as shown in FIG. or multiple subtasks. In one embodiment, the conversation interface 1100 of group AA may include a group task icon 1102, which is similar to the group task icon 301 in the conversation interface 300 above, and user B may switch to The group task management interface 1300 shown in FIG. 13 is used to view and manage the group tasks in the group AA. In an embodiment, corresponding to the message 1101 shown in FIG. 11 , the group task management interface 1300 may show the corresponding group task 1301, and the group task management interface 1300 may also show other group tasks 1302 and 1303 Wait. Among them, the group task management interface 1300 may include a group task creation area 1304 for user B to create a group task in the group AA. This process is similar to the above creation process of user A, and will not be repeated here. In an embodiment, the group task management interface 1300 can display all group tasks in group AA, for example, group task 1301 and group task 1302 are group tasks performed by user B, while group task 1303 has nothing to do with user B (User B is neither the creator nor the executor or other roles), but all of them can be displayed on the group task management interface 1300 . Among them, since the group tasks 1301-1302 are related to user B, user B can be provided with a status setting option for the corresponding group task, and the status setting option is presented as the same “□” as in FIG. 12; when the status setting option is displayed As shown in Figure 13, it indicates that the completion status of the corresponding group task is "unfinished"; when user B triggers this status setting option, a mark "√" can be added in "□", and the corresponding group task The completion status of the group task is switched to "Completed"; of course, user B can cancel the mark "√" in "□" by triggering the status setting option of "Completed" status, thereby switching the completion status of the corresponding group task as "unfinished". Since the group task 1303 has nothing to do with user B, user B may not be provided with the status setting option for the corresponding group task, or the inoperable status setting option "■" shown in Figure 13 may be provided to user B to avoid User B made a mistake. In an embodiment, the group tasks displayed on the group task management interface 1300 may include multiple types, such as unfinished group tasks, completed group tasks, closed group tasks, etc. User B can choose to display all types of group tasks , you can also choose to display only some types of group tasks, which is not limited in this manual. For example, in FIG. 13 , only unfinished group tasks are selected, thus covering completed group tasks, closed group tasks, and other types of group tasks. For other group members in group AA, as the creator of the group task, you can refer to the relevant description of the above-mentioned user A, and as the executor of the group task or unrelated personnel, you can refer to the relevant description of the above-mentioned user B, No more details here. When there are a large number of group tasks in group AA, it may be difficult to efficiently implement group task management operations only by viewing the group task management interface of group AA, and you need to manually browse through each group task. Therefore, this manual provides an efficient management solution for group tasks. Fig. 14 is a schematic diagram of implementing group task management provided by an exemplary embodiment; as shown in Fig. 14, suppose that in the session interface 1400 corresponding to user A, user A can issue group tasks in the session interface 1400 Query message 1401, the process is the same as that of sending a message. In an embodiment, the query message 1401 may include two parts: identification content and query content. Among them, the identification content is used to be identified by the enterprise WeChat client 1 or the enterprise WeChat server (sent by the enterprise WeChat client 1 to the enterprise WeChat server), so as to distinguish the inquiry message 1401 from ordinary messages, such as the identification content "@Group Task" may be included, of course, this specification does not limit the specific form of the content of the mark. The content of the inquiry may include "how is the progress of the group task now?" as shown in FIG. In an embodiment, when the enterprise WeChat client terminal 1 recognizes the identification content, the query message 1401 or the content of the query can be passed in a way different from ordinary messages (such as adding a specific message identifier, using a specific transmission port, using Specific transmission links, etc., this manual does not limit this) to the enterprise WeChat server, so that the enterprise WeChat server does not forward it to other group members, but analyzes the query content and returns the corresponding Ask for results. In another embodiment, after receiving the inquiry message 1401 sent by the enterprise WeChat client 1, the WeChat Work server can automatically identify the identification content and the inquiry content, and return the corresponding inquiry result by analyzing the inquiry content. In an embodiment, the inquiry result may be presented to user A in the form of a message. For example, as shown in FIG. 14, the inquiry result can be included in a message 1402, received by the enterprise WeChat client 1 and displayed in the conversation interface 1400, and the sender of the message 1402 can be set as a group different from the group AA The special sender of the member, such as the "robot" or other forms shown in Figure 14, is not limited in this specification. In one embodiment, when user A initiates an inquiry to the enterprise WeChat server, the inquiry message 1401 will not be sent to other group members of group AA, and the message 1402 containing the inquiry result will only be sent to user A. will not be sent to other group members of group AA, so as to avoid causing interference to other group members. Of course, in some embodiments, both the inquiry message 1401 and the message 1402 can be sent to all group members, which is not limited in this description. User A can inquire about any content related to the group task, and the enterprise WeChat server can provide corresponding answers and feedback. For example, in addition to the more general overall progress shown in FIG. 14 , inquiries can also be made for one or more specific group members. For example, as shown in FIG. 15 , the query message 1501 sent by user A in the conversation interface 1500 can be "@group task B's group task progress", including the identification content "@group task" and the query content "B's group task progress" , so that the enterprise WeChat server can determine the corresponding processing progress information for the group tasks of user B in group AA, and these information can be included in the message 1502 and returned to the enterprise WeChat client 1, and the enterprise WeChat client 1 is presented to user A. In one embodiment, queries can be made for specific types of group tasks. For example, as shown in FIG. 16, the query message 1601 sent by user A in the conversation interface 1600 can be "@group task unfinished group task", including the identification content "@group task" and the query content "unfinished group task" , so that the enterprise WeChat server can determine the unfinished group tasks in the group AA, and return relevant information to the enterprise WeChat client 1 based on the message 1602, and the enterprise WeChat client 1 presents it to user A. In one embodiment, queries may be made for group tasks with specific deadlines. For example, as shown in FIG. 17 , the query message 1701 sent by user A in the conversation interface 1700 can be "@group task deadline not completed before November", including the identification content "@group task" and query content " Uncompleted group tasks with a deadline before November", so that the enterprise WeChat server can determine the unfinished tasks with a deadline earlier than November 1 based on the deadline and completion status of group tasks in group AA Group tasks, and return relevant information to the enterprise WeChat client terminal 1 based on the message 1702, and the enterprise WeChat client terminal 1 presents it to user A. In addition to responding to group members' active inquiries, the enterprise WeChat server can also actively push notification messages related to group tasks to group members, so that group members can keep abreast of relevant information. For example, Fig. 18 is a schematic diagram of an exemplary embodiment that actively pushes notification messages related to group tasks; as shown in Fig. 18, when the enterprise WeChat server determines that user A has two unfinished group tasks, it can Send a corresponding notification message 1801 to the corresponding enterprise WeChat client terminal 1 of user A, so that the enterprise WeChat client terminal 1 displays the notification message 1801 in the conversation interface 1800, thereby realizing an active reminder to user A. For another example, FIG. 19 is a schematic diagram of another kind of proactively pushing notification messages related to group tasks provided by an exemplary embodiment; as shown in FIG. For group tasks whose deadlines are separated by no more than 3 days), a corresponding notification message 1901 can be sent to the corresponding enterprise WeChat client 2 of user B, so that the enterprise WeChat client 2 can display the notification message 1901 in the conversation interface 1900, In this way, an active reminder to user B is realized. In the embodiment shown in Figure 18, the notification message 1801 can only be sent to user A, but not to other group members in the group AA; and in the embodiment shown in Figure 19, the notification message 1901 It can be sent to all group members of group AA, and by adding a separate notification prompt identifier (such as "@B") for user B in the notification message 1901, so that even if group AA is masked (such as by Start the "do not disturb" function), the enterprise WeChat client 2 can still send a reminder to user B, so as to prevent user B from ignoring the notification message 1901 for some reasons. Fig. 20 is a schematic diagram of yet another kind of proactively pushing notification messages related to group tasks provided by an exemplary embodiment; as shown in Fig. During the management operation, a corresponding notification message can be sent to the associated person of the relevant group task (such as the creator or other executor, etc.) or all group members of the group AA corresponding to the enterprise WeChat client, such as enterprise WeChat client 1 Corresponding notification messages 2001-2002 can be received, so that the enterprise WeChat client terminal 1 can display the notification messages 2001-2002 in the conversation interface 2000, so as to realize active reminders to group members such as user A. In one embodiment, when it is detected that a group member triggers the messages 1402~1702 or notification messages 1801~2001 in the above embodiment, the following operations can be implemented: In one case, switch to the group task management interface of group AA , to be viewed by group members; in another case, switch to the group task management interface of group AA, and mark the group tasks involved in the above message so that group members can view them; in another case, switch Go to the task information viewing interface, which only shows the information (summary information or detailed information) of the group task involved in the above message; or, other solutions can also be adopted, which is not limited in this manual. In one embodiment, in addition to manually inputting directly in the group task creation area 401 shown in FIG. Create group tasks more quickly and conveniently. For example, FIG. 21 is a schematic diagram of a template selection interface provided by an exemplary embodiment; group members of group AA can view the template selection interface 2100 shown in FIG. 21 through the corresponding enterprise WeChat client, the template The selection interface 2100 may include template content layout preview images corresponding to several alternative group task templates. Further, it is also possible to view other temporarily undisplayed group task templates by triggering the “more templates” option in the template selection interface 2100 . In an embodiment, the group task template may be provided by the developer of WeChat Work, or provided by a specialized third party. In another embodiment, the group task template can be created by the users of the corporate WeChat, uploaded to the corporate WeChat server, and displayed on the template selection interface 2100 by the corporate WeChat server for the group members of the group AA or Group members of other groups can view and use it. Fig. 22 is a schematic diagram of a template binding interface provided by an exemplary embodiment. Assuming that the group members of group AA select the "XX industry group task template" in the template selection interface 2100, the corresponding template content layout preview 2201 can be shown in the template binding interface 2200 as shown in FIG. 22 , for members of the group to view. When the group member belongs to the management member of the group AA, that is, the group member has the group task template management permission for the group AA, the template binding interface 2200 can provide the group member with binding options 2202, so that the group members can bind the above-mentioned "XX industry group task template" to the group AA by triggering the binding option 2202, then all group members in the group AA can use the " XX Industry Group Task Template" to quickly create corresponding group tasks. Fig. 23 is a schematic diagram of another template binding interface provided by an exemplary embodiment. Similar to FIG. 22, when a group member of group AA selects the "XX industry group task template" in the template selection interface 2100, the corresponding template binding interface 2300 shown in FIG. The template content layout preview 2301 is for the group members to view. When the group member is not a management member of the group AA, that is, the group member does not have the group task template management permission for the group AA, the template binding interface 2300 can provide the group member with a binding Set the request option 2302, so that the group member can send a binding request message to the management member in the group AA by triggering the binding option 2302, and the management member can send the above-mentioned binding request message by triggering the binding request message The "XX industry group task template" is bound to the group AA, and all group members in the group AA can quickly create corresponding group tasks through the "XX industry group task template". Fig. 24 is a schematic diagram of another group task management interface provided by an exemplary embodiment. When group AA has a bound group task template, in the group task management interface 2400 shown in FIG. 401 ), so that user A can create a corresponding group task through manual input in the group task creation area 2401 , and the group task management interface 2400 can also include a group task template trigger option 2402 . Assuming that the above-mentioned "XX industry group task template" is bound to group AA, when it is detected that user A triggers the trigger option 2402 of the group task template, the "XX industry group task template" can be invoked, thereby passing the "XX industry group task template" By configuring the variable parameters in the "Industry Group Task Template", you can quickly create a group task that meets the needs of "XX industry". In an embodiment, the group task management interface 2400 may include a group task batch import option 2403 for user A to quickly and batch import group tasks without manually creating one by one. Among them, user A can record the descriptive information of the group task in notepad and form tools in advance, such as task subject, task deadline, task executor, etc., and generate files that record these descriptive information, such as text files and table files etc.; then, by triggering the group task batch import option 2403, and selecting the above-mentioned text file or table file, the enterprise WeChat client 1 or enterprise WeChat server can analyze the description information of the group tasks recorded in the file, and create batches accordingly The corresponding group tasks can effectively improve the efficiency of user A in creating group tasks. Fig. 25 is a schematic structural diagram of a device provided by an exemplary embodiment. Please refer to FIG. 25. At the hardware level, the device includes a processor 2502, an internal bus 2504, a network interface 2506, a memory 2508, and a non-volatile memory 2510. Of course, it may also include hardware required by other services. . The processor 2502 reads the corresponding computer program from the non-volatile memory 2510 into the memory 2508 and then runs it, forming an information acquisition device for group tasks on a logical level. Of course, in addition to software implementations, one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of software and hardware, etc., that is to say, the execution subject of the following processing flow is not limited to Each logic unit may also be hardware or a logic device. Please refer to FIG. 26. In a software implementation, the information acquisition device for the group task may include: a sending unit 2601, which sends a message through a session corresponding to the group, and the message includes identification content and a message for the group in the group; The query content of the group task, the identification content is used to instruct the server to reply to the query content; the reply content receiving unit 2602 receives the reply content returned by the server to the query content, and the reply content includes the information about group tasks. Optionally, the sending unit 2601 is specifically configured to: send the user input information as the message content of the message when the session interface corresponding to the session detects the user input information; or, according to the usage automatically send the message according to the message content and sending period set by the user. Optionally, the message includes at least one of the following: a text message or an audio message; and the reply content includes at least one of the following: a text message or an audio message. Optionally, the creator and executor of the group task are both group members of the group. Optionally, the group task is created and generated by the group members of the group in the associated function interface of the group. Optionally, the executor of the group task is determined by the creator of the group task by performing a selection operation among the group members of the group; wherein, when the creator of the group task does not When performing the selection operation, all group members of the group are preset as executors of the group task. Optionally, when the creation interface of any task has nothing to do with the group, and the creator and executor of any task are group members of the group, the any task is determined as Group tasks within said group. Optionally, when the message contains the identification content, the message and the reply content are only visible to the sender of the message, but not to other group members in the group. Optionally, it also includes: a notification receiving unit 2603, configured to receive a notification message for the group task automatically sent by the server; the notification message includes at least one of the following: periodic statistical information, group tasks that have not yet been completed Reminder information for group tasks, reminder information for group tasks approaching completion deadline, and completion reminder information for completed group tasks. Optionally, the method further includes: a switching unit 2604, configured to switch to an information display interface of a group task related to the notification message when a trigger operation on the notification message is detected. Optionally, the group task is generated by the creator by configuring the group task template. Optionally, the group task template is pre-bound to the group. Optionally, it also includes: an importing unit 2605, importing a task record file into the group, and the task record file records description information of at least one group task; creating unit 2606, according to the task record file Create group tasks related to the group in batches based on the description information recorded in . Optionally, the task record file includes any of the following: a text file, a table file. The systems, devices, modules or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementing device is a computer, which may take the form of a personal computer, laptop computer, cellular phone, camera phone, smart phone, personal digital assistant, media player, navigation device, e-mail device, game control device, etc. desktops, tablets, wearables, or any combination of these. In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory. Memory may include non-permanent memory in computer readable media, random access memory (RAM) and/or nonvolatile memory in the form of read only memory (ROM) or flash memory ( flash RAM). The memory is an example of a computer readable medium. Computer-readable media includes both permanent and non-permanent, removable and non-removable media and can be implemented by any method or technology for storage of information. Information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for computers 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 technologies, compact disc read-only memory (CD-ROM), digital multifunction A compact disc (DVD) or other optical storage, magnetic cassette, magnetic disk storage, quantum memory, graphene-based storage medium or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device . As defined herein, computer readable media does not include transitory computer readable media, such as modulated data signals and carrier waves. It should also be noted that the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes Other elements not expressly listed, or elements inherent in the process, method, commodity, or apparatus are also included. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element. The foregoing describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that in the examples and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. Multiplexing and parallel processing are also possible or may be advantageous in certain embodiments. Terms used in one or more embodiments of the present specification are for the purpose of describing specific embodiments only, and are not intended to limit the one or more embodiments of the present specification. As used in one or more embodiments of this specification and the appended claims, the singular forms "a", "the" and "the" are also intended to include the plural forms unless the context clearly dictates otherwise. It should also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items. It should be understood that although one or more embodiments of the present specification may use the terms first, second, third, etc. to describe various pieces of information, these pieces of information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of one or more embodiments of the present specification, first information may also be called second information, and similarly, second information may also be called first information. Depending on the context, the word "if" as used herein may be interpreted as "at" or "when" or "in response to a determination." The above descriptions are only preferred embodiments of one or more embodiments of this specification, and are not intended to limit one or more embodiments of this specification. Within the spirit and principles of one or more embodiments of this specification, Any modification, equivalent replacement, improvement, etc. should be included in the scope of protection of one or more embodiments of this specification.
