[go: up one dir, main page]

WO2009076843A1 - Partage d'objets parmi plusieurs utilisateurs de mi - Google Patents

Partage d'objets parmi plusieurs utilisateurs de mi Download PDF

Info

Publication number
WO2009076843A1
WO2009076843A1 PCT/CN2008/073284 CN2008073284W WO2009076843A1 WO 2009076843 A1 WO2009076843 A1 WO 2009076843A1 CN 2008073284 W CN2008073284 W CN 2008073284W WO 2009076843 A1 WO2009076843 A1 WO 2009076843A1
Authority
WO
WIPO (PCT)
Prior art keywords
shared object
client
shared
client device
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2008/073284
Other languages
English (en)
Chinese (zh)
Inventor
Shan Lu
Bin Li
Xue QIU
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Publication of WO2009076843A1 publication Critical patent/WO2009076843A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms

Definitions

  • the present invention relates to the field of instant messaging (IM), and in particular to implementing multiple IMs
  • a method and apparatus for sharing objects between users A method and apparatus for sharing objects between users.
  • the multi-person conversation function provided by the tool allows users in different locations to discuss some issues. This provides a platform for multiple users to communicate and communicate with each other, satisfying the multi-person and multi-person communication experience of the user.
  • IM client In this application, will be able to be in the IM user's client (hereafter referred to as IM client or IM)
  • Content shared by client users and performing operations such as editing, modifying, deleting, etc. are collectively referred to as objects or shared objects.
  • a method for realizing sharing of objects between clients including: multiple IMs communicating in communication
  • the client represents at least one shared object; any of the plurality of IM clients
  • the client operates on at least one shared object, according to the operation in multiple IMs
  • the shared object that will be manipulated in the client is updated.
  • an IM client device including:
  • the shared object initiating module issues a request for the IM client device to which it belongs to share the object with the other at least one IM client device; the shared object window management module, the IM to which it belongs
  • the client device provides a shared object window, and the shared object is represented in the shared object window.
  • the shared object window management module is based on IM
  • a representation of a shared object in a client device is a representation of a shared object in a client device.
  • the server includes: a shared service module configured to be from IM
  • the client device receives the shared object and sends the received shared object to multiple IM client devices.
  • a system for implementing sharing of objects comprising a plurality of IM client devices and an IM server in communication with a plurality of IM client devices.
  • IM instant messaging
  • the client device includes a shared object window management module configured to pass IM
  • the server represents the shared object in multiple IM client devices.
  • the client After the client performs operations on the shared object (such as modification, addition, partial deletion, etc.), it can realize the actual sharing of the operation result by multiple IM client users.
  • operations on the shared object such as modification, addition, partial deletion, etc.
  • Figures 1 (a) and (b) are respectively in multiple IMs according to the present invention
  • FIG. 2 is a plurality of IMs according to an embodiment of the present invention.
  • FIG. 3 is a block diagram of an IM client according to an embodiment of the present invention.
  • FIG. 4 shows an example of the shared object window management module 330 shown in FIG. 3 in more detail
  • FIG. 5 is a block diagram of an IM client according to another embodiment of the present invention.
  • FIG. 6 is a block diagram of an IM server according to an embodiment of the present invention.
  • FIG. 7 illustrates the implementation of multiple IMs in accordance with one embodiment of the present invention.
  • FIG. 8 is a flowchart of sub-steps of step S10 shown in FIG. 7;
  • FIG. 9 is a flow chart of the sub-steps of step S20 shown in FIG. 7;
  • FIG. 10 is a flow chart of the sub-steps of step S30 shown in FIG. 7.
  • FIGS. 1(a) and (b), respectively, are examples of user interfaces presented in a method and apparatus for sharing an IM client device (referred to as an IM client in the specification).
  • Figure 10
  • IM clients 300 illustrated by a plurality of IM clients 300 and with these IM clients 300
  • the IM client 300 can include a shared object initiation module 320 and a shared object window management module 330.
  • the shared object window management module 330 is launched afterwards.
  • the shared object initiation module 320 can also initiate the shared object window management module 330 based on a request from the IM server 600 to initiate the shared object.
  • the shared object window management module 330 implements providing a shared object window to the IM client 300.
  • the user performs an operation on the displayed shared object, and the shared object 11 after being operated by the IM client 300 to which it belongs.
  • the IM client 300 further includes a discussion group management module 310.
  • the users of the client can form a discussion group, and the members (users) in the discussion group can perform the actual conversation. And sharing of shared objects and /
  • the discussion group can include an administrator, who can be the initiator of the discussion group or other members of the discussion group.
  • the discussion group management module 310 in the administrator's IM client 300 is multiple
  • the IM client 300 creates a discussion group and implements each IM in the discussion group.
  • Client management such as adding, deleting, etc.
  • Discussion Group Management Module 310
  • the shared object window management module 330 includes a shared object window providing unit 331, a shared object operating unit 332, and a shared object updating unit 333.
  • the shared object rights management unit 334 may also be included.
  • a request list management unit 335 may also be included in another example.
  • Shared object window providing unit 331 provides shared object window 14, and will share object 11
  • the provided shared object window is in the session window provided by the session window management module 310.
  • session window 12 and the shared object window 14 can be displayed simultaneously.
  • any number of shared objects may be included.
  • the shared object operation unit 332 can be configured to perform a user by, for example, FIG. 1(a), (b)
  • the shared object update unit 333 can be configured to update the operated shared object 11 in the IM client to which it belongs.
  • the shared object update unit 333 can be configured to update the operated shared object 11 in the IM client to which it belongs.
  • the operated shared object can also be transferred to the IM server 600 which will be described later, thereby updating each IM.
  • the shared object in the shared object window of the client can be initiated by the initiator of the discussion group or by other members of the discussion group.
  • the shared object update unit 333 can determine the shared object 11 currently displayed in the shared object window 14 every predetermined interval. Whether it is consistent with the shared object that the storage unit has stored. If not, the shared object in the storage unit is updated to the currently displayed shared object, and the updated shared object 11 is sent to the IM server 600 to update the shared object 11 among the other clients.
  • the shared object update unit 333 may also set an operation flag for the shared object (flag
  • This flag is set after the shared object is manipulated. Thus, by checking the operation flag corresponding to the shared object, it can be judged whether or not the shared object is operated. If so, the currently displayed shared object 11 is updated to the processed content.
  • the operation of the shared object 11 can be detected. If the member operates on the shared object 11 in the shared object window 14, the member's IM client 300 requests a connection with the IM server 600, thereby passing the operation of the current shared object 11 through the IM server 600.
  • the shared object window management module 330 may further include a request list management unit 334
  • the IM to which the shared object window management module 330 belongs belongs
  • the client's user can be used as an 'administrator'. Specifically, when an IM client 300
  • the user of the discussion group is the administrator of the discussion group, and the request list management unit 334 of the IM client 300 can present the IM client 300 from other members of the discussion group.
  • the request to occupy the shared object is added to the request list, and the plurality of IM clients 300
  • the request is sorted. Sorting can be done, for example, in tandem with the request. Determine which IM is currently allowed based on the ordering
  • the client occupies a shared object for operation. It should be noted that, in the present embodiment, the request list management unit 334 is included in the IM client 300, but the request list management unit 334 may also be disposed in a server (for example, the IM server 600) in communication with the IM client 300. .
  • the shared object window management module 330 includes a shared object rights management unit 335
  • the authority of the IM client 300 to which it belongs can be further controlled. For example, after the IM client 300 is allowed to operate the shared object, the shared object rights management unit 335 of the IM client 300 sets the shared object window 14 to an operable state; otherwise, it is set to a read-only state. [42] In addition, when the IM client 300 to which the shared object right management unit 335 belongs
  • the administrator can also be configured to be able to assign the IM client 300 of the other members of the discussion group to the operational rights of the shared object.
  • the administrator determines that the IM client 300 that is currently allowed to occupy the shared object, the IM server 600 is sent to carry the IM client 300.
  • the IM server 600 then broadcasts the message to each of the IM clients 300 of the discussion group.
  • the IM client 300 Determine whether the unique user ID in the message is consistent with its unique user ID. After determining that it is consistent, make sure that you are currently allowed to operate on the shared object.
  • the IM client 300
  • the shared object rights management unit 335 will have the IM client 300
  • the shared object window is set to an operational state; otherwise, it is set to a read-only state.
  • FIG. 5 is a block diagram showing another configuration of the IM client 300.
  • IM client 300 includes, in addition to discussion group management module 310, shared object initiation module 320.
  • a shared object window management module 330 further including a session window management module 340
  • the discussion group management module 310, the shared object initiation module 320, and the shared object window management module 330 are the same as explained above, and therefore only the session window management module 340 is hereinafter.
  • the session window management module 340 can also be applied to the IM client of the above described embodiment.
  • the session window management module 340 provides a session window 12 for the IM client 300 (as shown in Figures 1(a) and (b)). User can go to the conversation window 12
  • the session window management module 340 can be configured to enable the shared object window 14 and the session window 12 to be on different pages (only the shared object window 14 is shown in FIG. 1(a)).
  • the switching label 13 shown in Fig. 1 (a) can be used.
  • the session window 12 and the shared object window 14 can also be made.
  • This session window management module 340 There is no need to perform a window switch.
  • an embodiment of the IM server 600 includes a shared service module 630.
  • a group service module 610 and a storage module 620 may also be included.
  • the group service module 610 interacts with the IM client 300 to create a discussion group.
  • the client uses the IM client 300, as described above, and the group service module 610 interacts with the discussion group management module 310 of the IM client 300 to establish a discussion group.
  • the storage module 620 stores the shared objects 11 uploaded by the respective IM clients 300.
  • an IM client When an IM client
  • 300 belongs to multiple discussion groups, storage module 620
  • the storage unit can also be implemented in the IM client 300 to implement the functions of the storage module 620.
  • the storage module 620 can also associate individual IM clients to shared objects 11
  • the events of previous operations are stored as history files, and each history file is assigned a corresponding identifier.
  • the shared service module 630 receives the boot shared object from the IM client 300 11
  • the request to initiate the shared object is also forwarded to each IM client 300 of the discussion group.
  • the shared service module 630 can also be based on from the IM client 300
  • the instruction to end the discussion sends the shared object stored in the storage module 620 to the IM client 300 that initiated the discussion group.
  • step S10 communication communication is established between a plurality of IM clients 300.
  • the IM client 300 that communicates with each other can share the object by establishing a discussion group. This process can be as shown in steps S10-S20 in the figure.
  • step S10 a certain IM client 300 is directed to the IM server 600.
  • an user A's IM client 300 Apply to establish a discussion group. For example, an user A's IM client 300
  • a discussion group is created by interaction between its discussion group management module 310 and the group service module 610 of the IM server 600. The specific interaction steps will be described later in conjunction with FIG.
  • step S20 after the discussion group is successfully established, the IM client 300 of the initiator of the discussion group requests the IM server 600 to share the shared object 11 in the shared area 10 with other IM clients of the group. .
  • the IM client 300 of the member of the discussion group performs the shared area 10
  • step S30 any member of the discussion group passes its IM client 300
  • the initiator of the discussion group (or the administrator of the discussion group) may also be IM.
  • the client can be based on the permissions of different members, the order of the requests, and /
  • step S40 the occupied shared object is activated 11
  • the IM client 300 of the member who initiated the request After the application request is approved, the IM client 300 of the member who initiated the request
  • the shared object operation unit 332 realizes a specific operation on the shared object 11 in its shared object window 14, for example, editing, modifying, and partially deleting the shared object 11.
  • step S50 the IM client 300 completes the sharing of the object 11
  • the operation, and the shared object 11 after the operation is sent to the IM server 600.
  • the IM server 600 updates the operated shared object 11 to the shared object window 14 of the other IM client.
  • the update can be performed as follows: Shared object update unit of IM client 300 333
  • the manipulated object is sent to the IM server 600.
  • Shared service module 630 of IM server 600 The received shared object 11 is sent to the storage module 620 to update the original shared object 11 therein.
  • the received shared object may also be stored in the storage module 620.
  • the shared service module 630 sends the updated shared object 11 to each IM client 300 of the discussion group, and updates its shared object 11 accordingly.
  • the shared service module 630 can transmit the manipulated shared object 11 to other IMs in the discussion group other than the IM client 300 performing the operation.
  • Client can also send to all IM in the discussion group
  • the client, or the shared object 11 after the operation is sent to a specific IM client in the group for updating according to the request of the client operating the object or the setting or control of the discussion group administrator.
  • the above embodiment may further include step S60.
  • step S60 when the current session and the operation of the shared object 11 are to be ended, the current shared object 11 may be saved only in the initiator's IM client 300, or may be saved in each IM of the discussion group member.
  • the client 300 is either stored in the IM client 300 that is required to end the member of the session, or is the IM client 300 as an administrator.
  • the initiator or administrator can choose this. For example, if the IM client selected as the initiator is selected, the IM client 300 of any member is directed to the IM server 600.
  • a request to end the discussion is sent, the request carrying an indication in the IM client 300 that holds the current shared object to at least one user in the discussion group.
  • the IM server 600 transmits the current shared object stored by the storage module 620 to the initiator's IM client 300 for storage.
  • Each history file can be assigned an identifier.
  • the discussion group initiator or a discussion group member who is authorized to view the history information may send a request for carrying the history file identifier to the IM server 600, and the IM server 600 receives the request, and according to the identifier in the received request, the shared object is A history file is updated to the IM client 300 of each discussion group member for discussion of each member of the group.
  • step S10 in FIG. 7 An example of the interaction process described in step S10 in FIG. 7 will be described below with reference to FIG.
  • the IM client 300 and the IM server 600 described above For example, this should not be construed as limiting the invention.
  • step S101 the discussion group management module 310 of the IM client 300 receives from the user A.
  • the request to initiate a discussion group may include recording a list of member information to be added to the discussion group (hereinafter referred to as 'member list') and the corresponding discussion group name.
  • step S102 the discussion group management module 310
  • step S104 the discussion group management module 310 generates the user A including
  • the discussion group of the subscriber number identification, the member list, and the discussion group name initiates the request, and sends the generated request to the IM server 600.
  • the content of the generated request may be organized and encrypted in accordance with an agreed protocol (e.g., UDP protocol) format, and then transmitted to the IM server 600 using a socket specified by the protocol.
  • an agreed protocol e.g., UDP protocol
  • the received request is decrypted and parsed according to the protocol.
  • step S105 after receiving the initiation request, the IM server 600 is served by the group service module 610.
  • a new discussion group number identifier is generated based on the user number and the member list in the received request.
  • Group Service Module 610 is also for User A
  • the identity of the discussion group initiator (in this case, the identity of the administrator) is set, and the generated discussion group number identifier is sent to the IM client 300 of each member in the member list.
  • the session window management module 340 After the returned discussion group identifier, the session window management module 340
  • the shared object window management module 330 can also be utilized to provide a shared object window corresponding to the group identification.
  • the session management module 310 may also send an acknowledgement message to the group service module 610.
  • An example of the processing procedure of step S20 shown in Fig. 7 will be described below with reference to Fig. 9 .
  • step S201 the discussion group initiator is at its own IM client 300.
  • the session window created in step S106 is displayed (for example, through a boot menu or a toolbar of its main window)
  • the request contains the discussion group ID and the application type (AppType)
  • the local object file of the local shared object window 14 is shared object 11
  • the original object file in this example is a picture file.
  • step S202 the IM server 600
  • Accepting the request of the originator's client establishes, for example, a socket connection between the initiator's client and the server. Further, the IM server 600 utilizes the established connection from the IM client 300.
  • the original shared object 11 is received and stored in the storage module 620.
  • IM IM
  • the storage module 620 In the case where the client has multiple discussion groups, the storage module 620
  • mapping relationship between the original object file and the discussion group identifier can also be stored.
  • step S203 the shared service module 630 of the IM server 600
  • AppType After receiving the request, according to the discussion group identifier and the application type included in the request (AppType sends a connection request to establish a shared service module 630 with the server.
  • the shared service module 630 establishes respectively according to the discussion group identifier and the application type (AppType). Individual member's IM client
  • the IM server 600 refers to the IM client 300 of each member of the discussion group. Broadcast the original shared object 11. After the IM client 300 of each member receives the byte stream of the original content of the shared object 11, the session window 12 corresponding to the discussion group identifier is opened.
  • step S20 [79]
  • step S30 in Fig. 7 An example of the process of step S30 in Fig. 7 will be described below with reference to Fig. 10.
  • step S301 any member of the discussion group passes through the IM server 600.
  • step S302 the initiator (or administrator)'s IM client 300
  • the request list management unit 335 After receiving the above request request, the request list management unit 335
  • the initiator or administrator can also prioritize a member based on the urgency of discussing group members in the session, so that the shared object can be prioritized.
  • step S303 the request list management unit of the IM client of the discussion group initiator (or administrator) 335
  • step S304 the shared service module 630
  • the message is forwarded to the IM client 300 of each member of the discussion group corresponding to the discussion group identifier.
  • the shared object rights management unit 334 of each member's IM client 300 obtains the UIN of the member who currently obtains the operation authority from the message, and determines whether the UIN is consistent with the locally logged UIN. If they are consistent, the IM client 300 is determined. Get permission to operate on shared objects. Accordingly, the IM client 300
  • Shared object rights management unit 334 makes it share object window 14
  • the shared object window 14 of the IM client 300 is in a 'read only' state (which can be used as the default state).

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente invention concerne un procédé de partage d'objets parmi plusieurs clients de MI. Le procédé comprend : la configuration d'une connexion de communication entre plusieurs clients de MI ; la promotion d'au moins un objet partagé sur les multiples clients de MI connectés à la communication, n'importe lequel des multiples clients de MI utilisant l'objet partagé ; et mise à jour de l'objet partagé utilisé dans les multiples clients de MI. L'invention concerne également le dispositif client de MI, le serveur de MI et le système pour le partage d'objet. Le procédé, le dispositif et le système peuvent réaliser le partage du résultat d'exploitation parmi plusieurs utilisateurs des clients de MI.
PCT/CN2008/073284 2007-11-30 2008-12-01 Partage d'objets parmi plusieurs utilisateurs de mi Ceased WO2009076843A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2007101882786A CN101163118B (zh) 2007-11-30 2007-11-30 一种多个im用户实时共享对象的方法和装置
CN200710188278.6 2007-11-30

Publications (1)

Publication Number Publication Date
WO2009076843A1 true WO2009076843A1 (fr) 2009-06-25

Family

ID=39297946

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/073284 Ceased WO2009076843A1 (fr) 2007-11-30 2008-12-01 Partage d'objets parmi plusieurs utilisateurs de mi

Country Status (2)

Country Link
CN (1) CN101163118B (fr)
WO (1) WO2009076843A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8225001B2 (en) 2010-01-06 2012-07-17 International Business Machines Corporation Feature propagation
CN112291133A (zh) * 2019-07-22 2021-01-29 腾讯科技（深圳）有限公司 跨端发送文件的方法、装置、设备及介质

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101163118B (zh) * 2007-11-30 2011-04-20 腾讯科技（深圳）有限公司 一种多个im用户实时共享对象的方法和装置
CN101217504B (zh) * 2007-12-27 2010-06-23 腾讯科技（深圳）有限公司 一种共享通信好友的方法及网络通信系统
US20100257239A1 (en) * 2009-04-02 2010-10-07 Qualcomm Incorporated Method and apparatus for establishing a social network through file transfers
CN102857530B (zh) * 2011-06-30 2015-10-28 腾讯科技（深圳）有限公司 一种上传图片的方法及系统
CN103108005A (zh) * 2011-11-11 2013-05-15 上海聚力传媒技术有限公司 在分布式存储系统中实现数据共享的方法、设备与系统
CN102882930A (zh) * 2012-09-03 2013-01-16 常州嘴馋了信息科技有限公司 网页用户信息共享系统
CN104243538A (zh) * 2013-06-24 2014-12-24 腾讯科技（深圳）有限公司 资源分享方法和系统
CN103716227B (zh) * 2013-12-12 2018-03-30 北京京东尚科信息技术有限公司 一种用于即时通讯中进行信息交互的方法和装置
CN104660676B (zh) * 2015-01-15 2018-03-02 小米科技有限责任公司 设备信息分享方法及装置
CN106034114A (zh) * 2015-03-12 2016-10-19 腾讯科技（深圳）有限公司 多媒体信息分享方法及装置
CN106202074B (zh) * 2015-04-29 2021-02-23 中兴通讯股份有限公司 一种处理共享文件的方法及装置
CN104902075B (zh) * 2015-04-29 2017-02-22 努比亚技术有限公司 多屏互动方法及系统
CN106293319B (zh) 2015-06-11 2019-12-06 阿里巴巴集团控股有限公司 业务对象传输方法及装置
CN105099890A (zh) * 2015-07-27 2015-11-25 阿里巴巴集团控股有限公司 即时通讯消息的文件保存方法及装置
CN105187302A (zh) * 2015-09-14 2015-12-23 中合国际知识产权股份有限公司 一种即时通讯中修改对象的方法和系统
CN107453977A (zh) * 2016-06-01 2017-12-08 腾讯科技（深圳）有限公司 一种会话管理的方法及服务器
CN106130887A (zh) * 2016-08-17 2016-11-16 深圳市金立通信设备有限公司 一种文件分享方法及终端
CN106570222A (zh) * 2016-10-18 2017-04-19 中车青岛四方机车车辆股份有限公司 一种三维数据模型的实例更新方法及装置
CN107229526B (zh) * 2017-05-17 2019-03-01 腾讯科技（深圳）有限公司 群会话中的消息处理方法、装置、存储介质和计算机设备
CN107040457B (zh) * 2017-06-20 2020-04-17 北京奇艺世纪科技有限公司 一种即时通信方法和装置
US10791082B2 (en) * 2017-11-21 2020-09-29 D8AI Inc. Systems and methods for delivery and use of interactive objects
CN107864358B (zh) * 2017-11-28 2020-03-17 上海掌门科技有限公司 一种视频通话中的共享对象操作方法
US10936157B2 (en) 2017-11-29 2021-03-02 Snap Inc. Selectable item including a customized graphic for an electronic messaging application
CN110221891A (zh) * 2019-05-17 2019-09-10 北京大米科技有限公司 一种绘图数据获取方法、装置、存储介质以及终端
CN110598381B (zh) * 2019-09-16 2022-04-05 北京字节跳动网络技术有限公司 数据访问方法、装置、设备及存储介质
CN110989951A (zh) * 2019-11-15 2020-04-10 广州市视云信息科技有限公司 电子白板客户端及服务端设备、系统、方法和存储介质
CN111107065A (zh) * 2019-12-05 2020-05-05 视联动力信息技术股份有限公司 电子白板权限管理的方法、装置、设备以及存储介质
CN112054951B (zh) * 2020-08-29 2022-05-10 腾讯科技（深圳）有限公司 资源传输方法、装置、终端及介质
CN116647528A (zh) * 2022-02-16 2023-08-25 北京字跳网络技术有限公司 一种对象的操作方法、装置、电子设备及存储介质
CN115514729B (zh) * 2022-08-31 2024-04-05 同炎数智科技(重庆)有限公司 一种基于三维模型的即时讨论方法及系统
CN119475290A (zh) * 2024-10-28 2025-02-18 广州朗国电子科技股份有限公司 一种电子白板的多角色管理方法、装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003034196A1 (fr) * 2001-10-19 2003-04-24 Dmates As Communication riche via l'internet
CN1744557A (zh) * 2004-08-31 2006-03-08 腾讯科技（深圳）有限公司 基于即时通讯工具的网络存储服务中对象共享的实现方法
CN101163118A (zh) * 2007-11-30 2008-04-16 腾讯科技（深圳）有限公司 一种多个im用户实时共享对象的方法和装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
SG97944A1 (en) * 1999-10-04 2003-08-20 Actv Inc Enhanced video programming apparatus and method providing a shared whiteboard
CN101068190B (zh) * 2006-12-27 2012-03-21 腾讯科技（深圳）有限公司 对象共享方法、对象管理服务器和网络系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003034196A1 (fr) * 2001-10-19 2003-04-24 Dmates As Communication riche via l'internet
CN1744557A (zh) * 2004-08-31 2006-03-08 腾讯科技（深圳）有限公司 基于即时通讯工具的网络存储服务中对象共享的实现方法
CN101163118A (zh) * 2007-11-30 2008-04-16 腾讯科技（深圳）有限公司 一种多个im用户实时共享对象的方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"CollaborateCom 2007. International Conference on", 15 November 2007, ISBN: 978-1-4244..., article SASA JUNUZOVIC ET AL.: "Multicasting in Groupware?, Collaborative Computing: Networking, Applications and Worksharing", pages: 168 - 177 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8225001B2 (en) 2010-01-06 2012-07-17 International Business Machines Corporation Feature propagation
CN112291133A (zh) * 2019-07-22 2021-01-29 腾讯科技（深圳）有限公司 跨端发送文件的方法、装置、设备及介质
CN112291133B (zh) * 2019-07-22 2022-06-28 腾讯科技（深圳）有限公司 跨端发送文件的方法、装置、设备及介质

Also Published As

Publication number Publication date
CN101163118B (zh) 2011-04-20
CN101163118A (zh) 2008-04-16

Similar Documents

Publication Publication Date Title
WO2009076843A1 (fr) Partage d'objets parmi plusieurs utilisateurs de mi
JP5010608B2 (ja) リモートリソースとの安全な対話型接続の生成
US10110520B1 (en) Decentralized authoritative messaging
US7096255B2 (en) System and method for providing a roster list of temporary contacts having expiration periods designated by a user in an instant messaging environment
AU2004211407B2 (en) Systems and methods for collaborative communication
KR20190088063A (ko) 리소스 공유 방법, 장치 및 시스템
US20070124406A1 (en) Using a mobile phone to remotely control a computer via an overlay network
CN103001992A (zh) 虚拟桌面实现系统及其使用方法
JP2005530273A (ja) 情報共有グループ、サーバおよびクライアントグループアプリケーション、およびそれらのための方法
CN102577315A (zh) 设定用户访问虚拟机权限的方法、设备和系统
CN102457816B (zh) 集群信息管理的方法、集群接入网关及相应的集群系统
CN112738559A (zh) 投屏实现方法、装置及系统
EP3215949A1 (fr) Nouveau système de messagerie instantanée (im)
EP3554037A1 (fr) Procédé de commande de transmission multimédia de liaison descendante, et dispositif associé
WO2008071109A1 (fr) Procédé et système de réalisation de gestion de compte de courrier tiers
JP2019086989A (ja) コンテンツ配信システム、コンテンツ配信装置、コンテンツ配信方法及びプログラム
CN109104774B (zh) 数据传输方法和系统
WO2012122914A2 (fr) Procédé et système de mise en œuvre de vvm par ip
EP1567936A2 (fr) Kit de developpement logiciel destine a des applications et a un systeme de communication en temps reel
JPH118615A (ja) データ暗号化システム、情報処理装置、ｉｃカード、記録媒体およびデータの暗号方法
WO2014056387A1 (fr) Procédé, système et dispositif pour transférer une session de conversation sous forme de texte, et client d'agent
CN112153580B (zh) 设置mcptt群组的方法、设备及系统
JP4650626B2 (ja) 発言権管理システム、発言権管理方法、及びプログラム
EP1388789A1 (fr) Systeme de gestion d'informations et procede de gestion d'informations utilisant une image d'informations
JP2019086988A (ja) コンテンツ配信システム、コンテンツ配信装置、コンテンツ配信方法及びプログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08862232

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) OF 131010

122 Ep: pct application non-entry in european phase

Ref document number: 08862232

Country of ref document: EP

Kind code of ref document: A1