CN102143125B - Access method of converged internet protocol messaging (CPM) session history record and message storage server - Google Patents

Abstract

The invention discloses an access method of a converged internet protocol messaging (CPM) session history record and a message storage server. In the method, the message storage server receives an access instruction from a client; the message storage server analyzes the access instruction so as to acquire a file catalog identification to be accessed, and acquiring linkage metadata information corresponding to the file catalog identification; and the message storage server executes an access operation corresponding to the access instruction. According to the technical scheme provided by the invention, multiple views are provided for a user while a user-defined management operation of the user on the recorded resources stored on the message storage server are met; and good service experience is provided for the user on the premise of reducing the management expenditure of the message storage server to the greatest extent.

Description

The access method of CPM meeting history record and message storage server

Technical field

The present invention relates to the communications field, in particular to a kind of access method and message storage server of IP message (Converged IP Messaging, referred to as CPM) meeting history record of fusion.

Background technology

IP message (the Converged IP Messaging merged, referred to as CPM) enabler be by OMA organize propose one can cross over different Access Network, framework is on unified IP kernel heart net, with support terminal user one to one, one-to-many and and multiple application between the communication of various medium types (such as, text, picture, audio/video fragment, binary file, audio/video stream).

In the message communication environment merged, CPM enabler provides CPM business to user in units of CPM talks, make it to carry out information interaction, user wishes that in the process of communication the history mutual information of the CPM talks that oneself can be participated in is undertaken recording and storing by network side, thus realization can by sending request the history intersection record information having access to the CPM talks oneself once participated in when needing to network side server, the overall process of talks that once participated in of reappearing user truly, and the meeting history record information belonging to this user oneself that network side server stores is managed.

CPM message storage server provides the function of above-mentioned storage CPM meeting history record for CPM user, and CPM message stores client is conducted interviews by access message storage server to the CPM meeting history record and relevant content that belong to this CPM user and manages, and resolved by the meeting history record information obtained from network side, view and the content of talks is shown to CPM user.

CPM talks describe between communication parties and utilize CPM enabler functional entity to carry out the operation of information interaction, and CPM talks are made up of the mutual outward CPM message of the session of arbitrary number, CPM file and CPM session.Wherein, CPM message is the imformosome that can comprise multiple discrete (discontinuous) media (such as, text, picture, audio fragment, video segment etc.).CPM file is the one or more files carrying content of multimedia exchanged between participant, and after recipient user agrees to receive file, document transmission process can start.CPM session refers to that the logic continued for some time between two or more participant connects, and can be used for participant and exchanges continuous media in real time, also can be used for exchanging discrete media and file.CPM interacting message, CPM file transfer can be carried out in CPM session, also can carry out outside CPM session.It is generally acknowledged, each CPM talks only comprise a CPM session in special time, the multiple CPM talks of participation but user can walk abreast.

CPM meeting history record is that the storage of CPM talks represents.Authorized person liable can obtain and store the information that they exchange in CPM talks process, and above-mentioned information is stored in the message storage server that CPM service provider provides as CPM meeting history record.Now, the mutual outward CPM message of CPM session is stored as a CPM Message Record, and the CPM file transfer of carrying out outside CPM session is stored as a CPM file transfer historical record.CPM session is then stored as a CPM conversation history record (comprising in session the data such as continuous media fragment mutual in CPM file transfer in CPM message, session and session).Therefore, from storage list signal justice, CPM meeting history record can be described as the set of CPM Message Record, CPM file transfer historical record and CPM conversation history record.Specifically can see Fig. 1.

Fig. 1 is CPM talks and the relation of CPM meeting history record and the schematic diagram of institute's content thereof.In fact CPM meeting history record function is exactly carry out record to CPM message mutual in CPM talks process, CPM file transfer and the CPM session carried out.In order to realize meeting history record function, need have a CPM functional entity to be positioned in signaling plane and media plane in communication process at network side simultaneously, as all signaling messages and media information in B2BUA received communication process, by resolving the information therefrom extracting and need record, record is carried out: be a CPM Message Record file by mutual for a CPM session CPM Message Record outward according to certain form, CPM file record CPM session transmitted outward is a CPM file transfer history file, be a CPM conversation history log file by a CPM conversation recording.CPM participates in function server and completes above-mentioned meeting history record function, and above-mentioned log file is submitted to CPM message storage server, carries out permanent storage.

As physical file actual storage in message storage server is the CPM Message Record, CPM file transfer historical record and the CPM conversation history record that comprise in CPM meeting history record.Message storage server should the resource relevant to the meeting history record stored manage, and supports following function:

(1) store CPM Message Record, CPM file transfer historical record, CPM conversation history record, CPM meeting history record, comprise any media object as CPM Message Record and a CPM conversation history record part;

(2) according to CPM user preference or service provider's strategy, this locality has been deposited resource and carried out synchronous with the resource that message stores client this locality stores, be included in the management by synchronization under many device contexts;

(3) to management (such as, copy, deletion etc.) and the access of depositing resource; Inquiry deposits resource; Based on service provider's strategy and user preference, the operation that record person liable performs network memory (such as, upload/download/revise/delete CPM message, CPM file transfer historical record, CPM conversation history, CPM talk history, and as the particular items such as media object of CPM message and a CPM conversation history part) etc.

In correlation technique, in order to storing message, the memory model scheme based on conditional electronic mailbox configuration can see Fig. 2.Each user has one piece by the pre-assigned storage area of service provider, under this catalogue, (such as, inbox, waste box, outbox etc.) are pressed from both sides and user presss from both sides (as Folder1, Folder2 etc.) composition from the unique file created by a series of unique file of being pre-defined by system.Use this memory model, under Message Record and conversation history record can be stored in any catalogue, the content of storage can move by user between file in manual operation.

But there is following shortcoming in such scheme:

(1) CPM Message Record and CPM conversation history record can be distributed in arbitrary file, in order to CPM talks view can be provided to user, by using extra metadata, the CPM Message Record be dispersed under each catalogue, CPM conversation history record and the CPM belonging to them talks must be associated.

(2) because CPM Message Record and CPM conversation history record can be distributed in arbitrary file, server end cannot support that message stores client is that meeting history record builds linear view by IMAP/THREAD order ([RFC5256]) request server, but for the mobile device calculated and storage resources is limited, complete the operation building linear view and can bring larger expense and burden, response speed may be caused slow etc. to be unfavorable for the impact of user's experience.

(3) owing to belonging to the CPM Message Record of CPM talks, CPM conversation history record may be distributed in different files, then message stores client is when the content that acquisition CPM meeting history record is relevant, need constantly to choose a file by IMAP/SELECT order, then the log file stored under just obtaining this file by IMAP/FETCH order, and then another file of SELECT again, obtain the log file that this file stores, continuous repetition is until get all the elements of this CPM talks, the operation of continuous use SELECT order opened file folder adds the command interaction number of times between message stores client and server, there is overhead, especially for mobile device, the command interaction of frequent redundancy can increase the data traffic on wave point, adding users uses the expense of business, reduce the experience that user uses business.

(4) some bookkeepings of user may destroy CPM and to talk linear view.Under above-mentioned memory model, user can carry out arbitrary bookkeeping to the resource of the storage in message storage server, such as, deletes certain Message Record file, but the result caused is the reply relation destroyed between message, thus destroy the linear view of CPM talks.

In correlation technique, also there is the memory model scheme based on CPM talks structure, specifically can see Fig. 3.As shown in Figure 3, the program designs the message stores model of CPM based on the design feature that CPM talks: namely according to CPM meeting history record, inclusion relation between CPM Message Record and CPM conversation history record, is stored in by the record resource file that each CPM meeting history record comprises and independently talks in sub-folder.

In this memory model scheme, message storage server is that each CPM user distributes one piece of exclusive storage area, for a corresponding talks sub-folder is set up in each CPM talks under this storage area, this CPM talk each session of comprising outward CPM message be stored in this talks sub-folder as independently Message Record file, each CPM session as independently CPM conversation history record.The establishment of talks file is completed by system, and the administration authority of user is limited, is merely able to the resource of checking in message storage server, destroys CPM talks view to prevent the operation of user.

The message stores model of structure of talking based on CPM, by belonging to the record Resource Storage of CPM talks in same talks file, saving the metadata of incidence relation between record CPM meeting history record and its record resource comprised and safeguarding the bookkeeping expense of this incidence relation.And the establishment of talks file is performed by CPM enabler, the operating right of user is limited, therefore ensure that view that CPM talks can not destroy by the operation of user.

But, there is following shortcoming in such scheme, because talks file is managed by message storage server, user does not have operating right, cause user cannot carry out bookkeeping to the resource that message storage server stores, user-defined file folder cannot be created ,/copy message record, conversation history log file cannot be moved, can only check with view of talking, poor user experience.

Summary of the invention

When the overhead brought for the operation building linear view in correlation technique and user carry out bookkeeping to the resource that message storage server stores, the problems such as CPM protocol can be destroyed and propose the present invention, for this reason, main purpose of the present invention is access method and the message storage server of the CPM meeting history record providing a kind of improvement, to solve the problem one of at least.

According to an aspect of the present invention, a kind of access method of CPM meeting history record is provided.

Access method according to CPM meeting history record of the present invention comprises: message storage server receives the access instruction coming from client; Message storage server is resolved access instruction and is obtained the file directory mark needing access, and obtains link metadata information corresponding to file directory mark; Message storage server performs the accessing operation corresponding with access instruction according to link metadata information.

According to a further aspect in the invention, a kind of message storage server is provided.

Message storage server according to the present invention comprises: the first receiving element, for receiving the access instruction coming from client; Resolve acquiring unit, obtain for resolving access instruction the file directory mark needing access, and obtain link metadata information corresponding to file directory mark; Performance element, for performing the accessing operation corresponding with access instruction according to link metadata information.

According to the present invention, for the meeting history record in converged message service communication environment defines a kind of message stores model of himself feature suitable, and form complete scheme by the relevant metadata of definition and relevant storage management operations, the feature of CPM talks can be met, meet user to outside the self-defined bookkeeping of the record resource that message storage server stores simultaneously, multiple view can also be provided for user, under the prerequisite as far as possible reducing message storage server administration overhead, good business experience can be provided for user.

Accompanying drawing explanation

Accompanying drawing described herein is used to provide a further understanding of the present invention, and form a application's part, schematic description and description of the present invention, for explaining the present invention, does not form inappropriate limitation of the present invention.In the accompanying drawings:

Fig. 1 is CPM talks and the relation of CPM meeting history record and the schematic diagram of institute's content thereof;

Fig. 2 is the schematic diagram based on the message stores model of conditional electronic mailbox configuration in correlation technique;

Fig. 3 is the schematic diagram based on the message stores model of talks structure in correlation technique;

Fig. 4 is the flow chart of the access method of CPM meeting history record according to the embodiment of the present invention;

Fig. 5 is the structural representation of the message stores model scheme according to the embodiment of the present invention;

Fig. 6 is the command schematic diagram obtaining Access Control List (ACL) operation according to the user of the embodiment of the present invention;

Fig. 7 is the command schematic diagram arranging Access Control List (ACL) operation according to the user of the embodiment of the present invention;

Fig. 8 is the command schematic diagram deleting Access Control List (ACL) operation according to the user of the embodiment of the present invention;

Fig. 9 is the command schematic diagram operated according to user's gain access of the embodiment of the present invention;

Figure 10 arranges according to user's request of the embodiment of the present invention command schematic diagram enlivening portfolio operations;

Figure 11 selects according to the user of the embodiment of the present invention file of talking, and checks the command schematic diagram of CPM protocol list;

Figure 12 selects a meeting history record according to the user of the embodiment of the present invention, checks the command schematic diagram of the detailed content of this CPM meeting history record;

Figure 13 is the command flow chart asking to create portfolio operations according to the user of the embodiment of the present invention;

Figure 14 is the command flow chart adding operation in record object to user-defined file folder according to the user of the embodiment of the present invention;

Figure 15, when checking the content operation in user-defined file folder according to the user of the embodiment of the present invention, obtains the command flow chart of record object identifier information;

Figure 16, when checking the content operation in user-defined file folder according to the user of the embodiment of the present invention, obtains the command flow chart of the meeting history record content stored in message server;

Figure 17 is the command flow chart deleting meeting history record operation according to the user of the embodiment of the present invention;

Figure 18 is the flow chart deleting MSS process when meeting history record operates according to the user of the embodiment of the present invention;

Figure 19 deletes according to the user of the embodiment of the present invention command flow chart linking Object Operations in user-defined file folder;

Figure 20 is the command flow chart moving the linked object operation in user-defined file folder according to the user of the embodiment of the present invention;

Figure 21 is the structured flowchart of the message storage server according to the embodiment of the present invention;

Figure 22 is the structured flowchart of message storage server according to the preferred embodiment of the invention.

Embodiment

Hereinafter also describe the present invention in detail with reference to accompanying drawing in conjunction with the embodiments.It should be noted that, when not conflicting, the embodiment in the application and the feature in embodiment can combine mutually.

According to the embodiment of the present invention, provide a kind of access method of IP message CPM meeting history record of fusion.

Fig. 4 is the flow chart of the access method of CPM meeting history record according to the embodiment of the present invention.As shown in Figure 4, following process (step S402-step S406) is comprised according to the access method of the CPM meeting history record of the embodiment of the present invention:

Step S402: message storage server receives the access instruction coming from client;

Step S404: message storage server is resolved access instruction and obtained the file directory mark needing access, and obtain link metadata information corresponding to file directory mark;

Step S406: message storage server performs the accessing operation corresponding with access instruction according to link metadata information.

Adopt said method, by storing link metadata information in the storage area of message storage server, associate to the accessing operation in user management region with the CPM meeting history record stored in system management region, solve in correlation technique overhead that the operation that builds linear view brings and user when bookkeeping is carried out to the resource that message storage server stores, the problem of CPM protocol can be destroyed, can meet user to the self-defined bookkeeping of the record resource that message storage server stores while, multiple view can also be provided for user.

Preferably, before message storage server reception comes from the access instruction of client, following process can also be comprised:

(1) in message storage server, create system management region, wherein, system management region comprises the first memory cell of storage meeting history record information, the second memory cell of storage system predefine fileinfo;

(2) in message storage server, create user management region, wherein, user management region comprises the 3rd memory cell storing customized information.

Preferably, above-mentioned meeting history record information comprises: talks metadata information and recorded information, wherein, recorded information comprises: at least one CPM Message Record information, at least one CPM file transfer history information, at least one CPM conversation history recorded information;

Preferably, said system predefine fileinfo comprises: the link metadata information of the predefined file directory subordinate of the predefined file directory of system, system;

Preferably, above-mentioned customized information comprises: the link metadata information of User Defined file directory, user-defined file directory subordinate.

Wherein, above-mentioned customized information can also comprise: the local record fileinfo of client upload.

Preferably, above-mentioned talks metadata information includes but not limited to following three classes: talks information metadata information, message/transfer file history information, conversation history record metadata information.

The memory model example architecture created in above-mentioned message storage server can see Fig. 5.As shown in Figure 5, for each legal user distributes an exclusive memory space (as " Root-User " file in message storage server, i.e. root), the resource record that the meeting history record had for storing user is correlated with, and provide management function to user.User-specific memory space (corresponding with " Root-User " catalogue) is divided into two parts: system management region and User Defined management area.

Wherein, system management region is made up of the predefined file of MSS, and " Conversation-History " (meeting history record file), " ReceivedBox " (inbox), " SendBox " (outbox) etc. are as shown in Figure 4 all by the predefined file of MSS.Wherein, meeting history record file is exclusively used in and stores the relevant record resource of meeting history record, and on MSS, maintains unique backup, for user provides talks view.Other system folder then by the content of " link metadata " association store in meeting history record file, thus provides some systems predefined view, as outbox view, inbox view etc. for user.

Wherein, User Defined management area is made up of user folder, and " Folder1 ", " Folder2 " as shown in Figure 4 etc. are all the files created voluntarily by user.User can by interested or feel important CPM Message Record, CPM file transfer record, CPM conversation history record or a part wherein, or CPM meeting history record " adds to " in self-defining file, carry out personal management, user-defined dynamic view is provided.User folder by the content of " link metadata " association store in " Conversation-History " file, thus provides user-defined dynamic view.In addition, user can also upload local log file in the User Defined file in message storage server, and is moved between different user folders by these log files uploaded.

In this memory model scheme, the log file that request CPM meeting history record comprises in order to avoid MSC to MSS is (as Message Record, file transfer record or meeting history record) time, need the drawback of constantly being ordered the overhead choosing destination folder to bring to obtain file by IMAP4/SELECT ([RFC 3501]), this programme adopts relevant file (the namely all Message Records of all CPM meeting history records, file transfer historical record, conversation history record) be all directly stored in " Conversation-History " file under, and the relevant information by adopting " talks metadata " to record CPM talks, maintain CPM meeting history record and the CPM Message Record belonging to these talks, incidence relation between CPM file transfer historical record and CPM conversation history record.

Wherein, system management region is managed by MSS, is mainly used to storage and maintenance CPM talks view, and the Access Management Access operation of user is limited; In user management region, user has administration authority completely, can press from both sides the Classification Management realized meeting history record content by user-defined file, to provide multiple different user self-definition view.

Wherein, the storage object related in this message stores model comprises following five classes:

The first kind: CPM Message Record object: be namely used for the outer CPM Message Record (comprising all media object that this message is carried) of storage session;

Equations of The Second Kind: CPM file transfer historical record object: the file transfer historical record be namely used for outside storage session;

3rd class: CPM conversation history record object: be namely used for the history information (comprise the session state information of this CPM session, and all CPM message mutual in this session, the CPM file of transmission and mutual continuous media flow object) of a storage CPM session;

4th class: metadata record object (i.e. metadata information): be namely used for adopting metadata information to provide managerial ability flexibly, generally speaking, the metadata of two types can be comprised:

Talks metadata (i.e. above-mentioned talks metadata information): the descriptor of record CPM meeting history record, and the incidence relation maintained between CPM Message Record, CPM file transfer historical record and CPM conversation history record and affiliated CPM talks, to provide talks view;

Link metadata (i.e. above-mentioned link metadata information): maintain the incidence relation between CPM conversation content and the file (can be system folder or user folder) be linked to, thus multiple systems default view and user self-definition view can be provided neatly.

The present invention adopts the framework setting up metadata schema, and can provide managerial ability flexibly, wherein, metadata comprises: talks metadata, link metadata.Below describe metadata schema in detail.

Such as, as shown in Figure 5, metadata store of talking is under meeting history record file.Under link metadata being stored in respectively inbox, outbox and user-defined file.

Wherein, for talks metadata, meeting history record file needs maintenance three class metadata, to record respectively and CPM talks, information that CPM message (CPM file transfer) is relevant with CPM session.Talks metadata can record obj ect file from each relevant to these talks and extract, and as metadata store, when MSC request presents talks view time, need first to MSS request talks metadata, then obtained the descriptor of the CPM talks that MSS stores by these metadata, thus provide talks view to user.CPM message (transfer files), CPM conversation metadata are then mainly used to recording messages (file transfer) with the summary info of CPM session object and by information such as which user folder associate, for the Content Management on MSS and query manipulation provide useful information.

Preferably, when MSS often receives a CPM Message Record, CPM file transfer historical record or CPM conversation history record, all to resolve it, extract relevant information, the metadata table of three types is upgraded.

Wherein, for link metadata, preferably, can be " SendBox ", system predefine files such as " ReceivedBox ", and each user-defined user folder creates " link metadata " information table, for CPM meeting history record being added to " SendBox " when system, system predefine files such as " ReceivedBox ", or user is by certain CPM Message Record object, CPM file transfer historical record object, CPM conversation history record object, when CPM meeting history record object or a certain partial content wherein " add to " in self-defining user folder, for these objects are set up corresponding " link metadata " under destination folder, namely in " the link metadata information table " of corresponding document folder, corresponding list item record is increased, record " Conversation-ID " of the CPM meeting history record be associated, or the CPM Message Record be associated, CPM file transfer historical record, unique location identifier (UID) of CPM conversation history record and associated No. part.

Particularly, record above-mentioned metadata information, being the store path information in order to preserve related record objects under this file, being equivalent to for they establish " link ", and without the record object that repeated storage is correlated with, to save memory space.In addition, use link metadata can be associated with a certain partial content (as certain media attachment etc.) in the record object be actually stored in talks file, this be use traditional carry out copying in units of file/document manipulation of movement cannot realize.

Below talks metadata and link metadata are described in detail.

1, talks metadata

Maintenance three class metadata is needed, to record respectively and CPM talks, information that CPM message (CPM file transfer) is relevant with CPM session in meeting history record file.Wherein, CPM talks metadata is particularly important, because CPM meeting history record is the concept of a logic, the file that it does not have actual physical storage is corresponding with it, so the descriptor that each CPM talks must be provided by metadata.Talks metadata can record obj ect file from each relevant to these talks and extract, and as metadata store, when MSC request presents talks view time (having which talks information etc. as this user), need first to MSS request talks metadata, then obtained the descriptor of the CPM talks that MSS stores by these metadata, thus provide talks view to user.CPM message (transfer files), CPM conversation metadata are then mainly used to recording messages (file transfer) with the summary info of CPM session object and by information such as which user folder associate, for the Content Management on MSS and query manipulation provide useful information.

When MSS often receives a CPM Message Record, CPM file transfer historical record or CPM conversation history record, all to resolve it, extract relevant information, these following three kinds of metadata tables are upgraded.Introduce three kinds of metadata tables below.

(1) CPM talks information metadata table

The organization definition of CPM talks information metadata is as shown in table 1 below, first row " field name " illustrates due field in talks information metadata table, the explanation that secondary series " explanation " provides corresponding field illustrates, the 3rd row " citing " provide this list item and should insert illustrating of content.

MSS receives the CPM Message Record that CPM participates in function submission, CPM file transfer historical record, during CPM conversation history record, should first resolve it, obtain the talks identifier of these record objects, " Conversation-ID " field of inquiry " CPM talks information metadata table ", if do not find metadata record of talking accordingly, then illustrate that this is new CPM talks, need to increase a line metadata information newly for this CPM talks in CPM talks information metadata table, and from the historical record object received, extract relevant information to fill in the respective field of this meeting history record corresponding element data record.

Table 1 CPM talks information metadata table (Conversation)

Field name	Explanation	Citing
			Conversation-ID	Talks identifier, identifies CPM talks uniquely	Conversation1
Start-Time	The talks time started	2008/3/27 7:30
			End-Time	The talks end time	2008/3/27 8:30
Subject	Talks theme	Meeting for CPM
			Initiator	The originator address of talks	bob@example.co m

participants	talks participant addresses	bob@example.co m; tina@example.co m;
			content-UI D	unique location identifier (UID) of the CPM Message Record that this CPM meeting history record comprises, CPM file transfer historical record or CPM conversation history log file	1,5,6..
thread-Resu lt	store the result of these talks being carried out to linear ordering	(2) (3 6 (4 23) (44 7 96))
			tag	the connective marker of meeting history record, the i.e. name of the user folder that this meeting history record is associated.	working, Important
deleted	whether performed deletion action by user, Boolean type	true or False

" talks information metadata table " as shown in table 1, with identifier of talking for major key, each line item stores the relevant descriptor of CPM talks.

Promoter (Initiator) information, participant (Participants) information of the time (Start-Time) that talks start, end time (End-Time), talks theme (Subject), talks;

Content-UID: the UID (UID is distributed by MSS, file action scope) of the log file that these talks comprise;

Thread-Result: the result character string of namely this meeting history record being carried out to linear ordering.Owing to adopting the scheme all meeting history record contents be stored under " Conversation-History ", therefore client cannot use THREAD order to server request linear ordering result, in order to address this problem, this entry is increased in talks metadata information table, server is carried out the result of linear ordering as metadata store to these talks, and such message stores client just can get the linear ordering result to specifying talks by GETMETADATA order.

tag: " Tag " information of this meeting history record, namely identifies this meeting history record and has been associated with which user folder.This meeting history record " adds to " in his self-defining " working " file and " Important " file by such as user, in then corresponding in talks information table Tag entry, add title (working and Important of these two files, with CSV), this part of meeting history record also can be found easily by which user folder to be associated by talks information table like this;

deleted: mark whether this meeting history record is performed deletion action " Deleted " field by user, default setting is " False ".If user is when browsing the talks view under talks file, have selected and delete this meeting history record, but when this talks meeting history record is associated by other user folders again, then this field is set to " True ", represents that user performs the deletion action of meeting history record under talks file.Then when MSC is to MSS request " talks view ", the information that " Deleted " field can not be set to the meeting history record of " True " by MSS returns to MSC.

(2) CPM message/transfer file history information metadata table

MSS often receives a CPM Message Record file submitted to by CPM PF or CPM file transfer historical record, just it is resolved, extract relevant information (as contribution identifier, affiliated talks talks identifier, whether be the message or file, timestamp, sender, recipient etc. transmitted in session) upgrade CPM message/transfer file information table, add corresponding record.

The structure of CPM message/file transmission history recorded information metadata table is as shown in table 2 below:

Table 2 CPM message/file transmission history record metadata table

(Message_File)

field	explanation	citing
			contribution-ID	the contribution identifier of CPM message or file transfer, this object of unique identification.	message2 or File1
belong-to-Conv-I D	the talks identifier of CPM talks belonging to this message or file transfer.	conversation1
			belong-to-Session-ID	whether this message or file transfer belong to CPM session, if belong in session, then record the contribution identifier of CPM session belonging to it, if do not belong to CPM session, then put sky (NULL).	session1
uID	the unique identifier of CPM message or file transfer object.If this is object outside a CPM session, then record the UID of this object; If this is object in a CPM session, then record the UID of CPM conversation history record object belonging to this message or file transfer.	23
			timeStamp	the timestamp of this message or file transfer.	2008/3/27

		8:30
			sender	the sender of this message or file transfer.	alice@example .com
receiver	the recipient of this message or file transfer.	bob@example. com
			subject	the theme of this message or file transfer.
tag	the connective marker of this message (or wherein certain is a part of) or file transfer, namely records the name of the user folder be associated with this message (or certain part) or file transfer.	Interest Message/2， Working/3

The structure of " CPM message/file transmission log information metadata table " as shown in table 2, with the contribution identifier of this record object for major key, each line item stores a CPM message or the relevant descriptor of CPM file transfer, such as,

Contribution identifier (the Belonged-to-Session-ID of contribution mark (Contribution-ID) of this CPM message or file transfer, the talks identifier (Belonged-Conv-ID) that affiliated CPM talks, affiliated CPM session, if the object outside session, then this field is put sky), unique location identifier (UID) of being distributed by MSS, timestamp (TimeStamp), sender (Sender), recipient (Receiver), theme (Subject);

" Tag " field: the connective marker of this record object, the name of those user folders be namely associated with this CPM message or CPM file transfer, such as, the Part 2 (annex 1) of this CPM message is associated with user-defined " InterestMessage " file by user, the then title of object file and associated No. part (separating by "/") under this field record, as " Interest Message/2 "; If the Part3 (annex 2) of this CPM message is associated with user-defined " Working " file by user, then the title of object file and associated No. part under this field record, as " Working/3 ".

(3) CPM conversation history recorded information metadata table

MSS often receives a CPM conversation history record submitted to by CPM PF, just it is resolved, extract the relevant information (as the information such as talks identifier, session establishment time, end time, session initiator, participant that the contribution identifier of session, belonging CPM talk) in conversation history record object, upgrade CPM session information table, add corresponding record, store relevant metadata so that afterwards find and search operation.Particular content is as shown in table 3 below:

Table 3 CPM conversation history record metadata table (Session)

Field	Explanation	Citing
			Contribution -ID	The contribution identifier of this CPM session, identifies this CPM session uniquely	Sessi on1
Belong-to-Co nversation-ID	The talks identifier of CPM talks belonging to this CPM session	Conv ersation1
			StartTime	The time of this CPM session start	2008/ 3/27 8:30
EndTime	The time of this CPM conversation end	2008/ 3/27 8:38
			Initiator	The promoter of this CPM session	alice @cpm.co m
Participants	The participant of this CPM session	bob@

		cpm.com
			uID	this CPM conversation history record unique location identifier on the server
tag	the connective marker of this CPM conversation history log file, the name of the user folder be namely associated with this CPM conversation history record (or wherein certain is a part of).	Worki ng/2， Important/ 3

The structure of " CPM conversation history recorded information metadata table " as shown in table 3, with the contribution identifier of this conversation history record for major key, each line item stores the relevant descriptor of a CPM conversation history record, such as,

The talks identifier (Belonged-Conv-ID) that contribution mark (Contribution-ID) of this CPM conversation history record, affiliated CPM talk, the unique location identifier (UID) distributed by MSS, session start time (StartTime), conversation end time (End-Time), promoter (Initiator), participant (Participants).

" Tag " field: the connective marker of this CPM conversation history record, the title of those user folders be namely associated with this CPM conversation history record (or wherein certain is a part of), such as user is by the audio fragment (part2) of this CPM conversation history record, under being associated with user-defined " Working " file by name, the then title of object file and associated No. Part under this field record, as " Working/2 "; If the Part3 (annex 2) of this CPM conversation history record is associated with user-defined " Important " file by user, the then title of object file and associated No. part under this field record, as " Important/3 ".

2, metadata is linked

For " SendBox ", system predefine files such as " ReceivedBox ", and each user-defined user folder creates " link metadata " information table, for CPM meeting history record being added to " SendBox " when system, system predefine files such as " ReceivedBox ", or user is by certain CPM Message Record object, CPM file transfer historical record object, CPM conversation history record object, when CPM meeting history record object or a certain partial content wherein " add to " in these self-defining user folders, for these objects are set up corresponding " link metadata " under destination folder, namely in " the link metadata information table " of corresponding document folder, corresponding list item record is increased, record " Conversation-ID " of the CPM meeting history record be associated, or the CPM Message Record be associated, CPM file transfer historical record, unique location identifier (UID) of CPM conversation history record and associated No. part.

Record such metadata information, being the store path information in order to preserve related record objects under this file, being equivalent to for they establish " link ", and without the record object that repeated storage is correlated with, to save memory space.In addition, use link metadata can be associated with a certain partial content (as certain media attachment etc.) in the record object be actually stored in talks file, this be use traditional carry out copying in units of file/document manipulation of movement cannot realize.

The particular content of link metadata information table is as shown in table 4 below:

Table 4 link information metadata table (Relevance)

field name	explanation	citing
			seq	the sequence number of link information metadata record, increases progressively distribution by client according to up-to-date link metadata record information on the server obtained, can identify a link information uniquely.	1，2，3…

link

be used to indicate the associated type of record object and the identifier of this object.

message/11/2 or File/12 or Session/22/3 or Conversation/ conv3

The structure of " link metadata information table " as shown in table 4, two fields are included in this table, i.e. " Seq " field and " Link " field, wherein " Seq " field is major key, for identifying a link information uniquely, and " Link " field is for recording the relevant information of associated object, is character string type, the value of this field, for the difference of affiliated partner type, specifically has different forms:

If the type of affiliated partner is CPM Message Record object (or wherein certain part) or CPM file transfer record object or CPM conversation history record object (or certain part wherein), then carry out record according to the form of " Type/UID/Part-Number ", wherein " Type " represents affiliated partner type, " UID " represents unique location identifier of affiliated partner log file, and " Part-Number " represents which part of affiliated partner.As the annex 1 (i.e. Part2) of to be UID the be CPM message of 11 of association, then under this field, increase the entry of " Message/11/2 " newly; The annex 4 (Part3) of to be UID the be conversation history record object of 22 of association, then in table, newly-increased " Link " value is the entry of " Session/22/3 ";

If association is whole CPM meeting history record, then carry out record according to the form of " Conversation/Conversation-ID ", wherein " Conversation " indicates affiliated partner to be CPM meeting history record, and " Conversation-ID " indicates the talks identifier of this meeting history record.As association be talks identifier be the meeting history record of " conv3 ", then in table, increase the entry that " Link " value is " Conversation/conv3 " newly.

After creating above-mentioned metadata schema, when needs are accessed, following process can be taked:

Process 1: obtain the metadata that specified folder is relevant

The metadata that MSC is correlated with to MSS acquisition request specified folder by IMAP4/GETMETADATA order ([RFC 5464]), if the file of specifying is " Conversation-History " file, then can get relevant metadata from the metadata table of " CPM talks information metadata table ", " CPM message/transfer file history information metadata table ", " CPM conversation history record metadata table " this three types.If the file of specifying is other system folder (as " SendBox " or " ReceivedBox " file) or user folder, then can obtain relevant link metadata from " link information metadata table ".The form following (carrying three parameters) of this order:

GETMETADATA< " title of specified folder " >< (option) >< (metadata table of specifying or the field name in showing) >

The title > parameter of < specified folder, provide the title that MSC wishes the destination folder obtaining metadata, as MSC wish obtain talks descriptor time, this file will be specified for " Conversation-History ", when user wishes to check the content in self-defined " Working " file, this file will be specified for " Working ";

< (option) > parameter: use DEPTH option, expansion returns the scope of metadata, when DEPTH option is set to " Infinity ", represents the value returning all fields of specifying in metadata table.

< (field name in the metadata table of specifying or table) > parameter: form be " value of/shared/ table name/major key/concrete field ", is used to specify which field that MSC wishes in the title of the target metadata table of acquisition metadata and this table.Relevant metadata table and corresponding table name are (concrete field name please refer to table 1,2,3,4):

CPM talks information metadata table: Conversation

CPM message/transfer file record information metadata table: Message_File

CPM conversation history recorded information metadata table: Session

Link information metadata: Relevance

Being described below in conjunction with example, example (1), when MSC asks all metadata of CPM meeting history record to MSS, using as issued orders:

GETMETADATA“Conversation-History”(DEPTH Infinity)(/shared/conversation/)

Example (2), if MSC only wishes the metadata information of the some fields obtaining specific entry, as hope obtains the talks subject information that talks identifier is the meeting history record of " Conv3 ", then MSC can use as issued orders:

GETMETADATA“Conversation-History”(/shared/conversation/conv3/Subject)

Example (3), when MSC asks the link metadata in " SendBox " file to MSS, uses as issued orders:

GETMETADATA“SendBox”(DEPTH Infinity)(/shared/Relevance/)

Example (4), when MSC asks the all-links metadata in User Defined file (as " Working " file) to MSS, uses as issued orders:

GETMETADATA“Working”(DEPTH Infinity)(/shared/Relecance/)

Process 1: the metadata that specified folder is relevant is set

MSC also revises the relevant metadata of specified folder by IMAP4/SETMETADATA order ([RFC 5464]) to MSS request.The metadata table be associated due to system folder is managed by MSS, MSC haves no right to ask retouching operation, therefore the content of " the link metadata information table " of relevant three metadata tables of " Conversation-History " file and the system folder such as " SendBox ", " ReceivedBox " should be managed by MSS, MSC can not modify, and is merely able to conduct interviews with only read states.

Therefore MSC can only be arranged the link metadata in " the link information metadata table " of user folder.The form of this order is as follows:

SETMETADATA< " title of specified folder " >< (value that the metadata table of specifying or the field name in showing are arranged) >

The title > parameter of < specified folder, provides the title that MSC wishes to arrange the user folder of metadata;

< (value that the metadata table of specifying or the field name in showing are arranged) > parameter: be the value pair of a shape as (entry value), wherein " entry " specifies the table at metadata place and the field name of correspondence of MSC desired modifications, and " value " represents the value wishing to arrange.The concrete form of " entry " part is " value of/shared/ table name/field name/field ".

Example (1), MSC wishes an affiliated partner under deletion user folder (" Working "), the link information sequence number of this affiliated partner is 12, i.e. the chained record of the value " 12 " of " Seq " field in " link metadata table ", then MSC uses as issued orders:

SETMETADATA“Working”(/shared/Relevance/12/LinkNIL)

5th class: folder object (i.e. file directory): the combination storage container of above object, the content that different file stores is not identical.

Wherein, CPM message object record, CPM file transfer historical record, CPM conversation history record exist as " leaf node " liking, can not be nested.And in folder object, user folder can be nested, to provide different packet layers.

In specific implementation process, create above-mentioned message stores model and mainly comprise following process:

(1) in system management region by the predefined file of MSS generation system, and under leaving top-level director in.

Such as, MSS generates meeting history record case, inbox, outbox.

Wherein, " Conversation-History " file (meeting history record case), be specifically designed to and store the content relevant with CPM talks, under the Message Record object that namely all CPM talk and are correlated with, file transfer historical record object, conversation history record object are all directly stored in this file;

" SendBox " file (outbox), for providing " outbox view " in units of CPM meeting history record.Namely this CPM Client-initiated CPM meeting history record should be included into " outbox view " by MSS, wherein, comprise in outbox " link metadata ", need to add a record in " the link metadata " of " SendBox " file, incidence relation between the CPM meeting history record of foundation is stored in " Conversation-History " file and " SendBox " file, for user provides system predefined outbox view;

" ReceivedBox " file (inbox): provide in units of CPM meeting history record " inbox view ".Namely the CPM meeting history record that this CPM user should be participated in (not initiator) by MSS is included into " inbox view ", wherein, comprise in inbox " link metadata ", namely in " the link metadata " of " ReceivedBox " file, a record is added, CPM meeting history record in foundation is stored in " Conversation-History " file and the incidence relation between " ReceivedBox " file, for user provides system predefined Inbox view.

Therefore, the predefined file of said system, the three kinds of system predefine views provided by MSS are provided, i.e. " talks view ", " outbox view ", " inbox view ", these three kinds of views are all in units of CPM meeting history record, for user provides the membership credentials of the predefined storage content of system.

Preferably, the bookkeeping of user to system folder (such as, " Conversation-History " file, " SendBox " file and " ReceivedBox " file) is limited.Such as, user is not allowed to create sub-folder under system folder; Do not allow user to delete, copy, move, rename system folder; Do not allow user's upload file to system folder; Only permission user checks the content in system folder, only allows a user to delete meeting history record in units of talks.

(2) above-mentioned meeting history record case is on MSS, be specifically designed to the file storing the content that CPM meeting history record is correlated with, that is, under all Message Record objects, file transfer historical record object and conversation history record object being all directly stored in " Conversation-History " file.

Preferably, talks view is maintained by " talks metadata " information.Namely the record object in meeting history record case and they separately belonging to CPM talks between incidence relation maintained by " talks metadata " information.

Preferably, due to the concept of a CPM talks inherently logic, not actual physical entity corresponds, so the descriptor of talking about each CPM needs to be provided by metadata, therefore " talks metadata " needs the descriptor that provides CPM to talk.

(3) one or more user-defined file folder (can be nested) is set up in user's actual need in user management region, and by using " link metadata " to set up the incidence relation between actual conversation content and user folder be stored in meeting history record file, thus provide user self-definition view.

Preferably, Message Record file, file transfer history file or conversation history log file (or certain partial content of log file) that this locality can store by user upload in the User Defined file in message storage server, and these files can be moved between different User Defined files.That is, for user-defined file, user has administration authority completely, can create sub-folder, rename, movement, deletes, copy user folder and file.

Preferably, user can also upload local record file in the user-defined file folder in message storage server, and can be moved by file between different user folders.That is, for user-defined file, user has administration authority completely, can create sub-folder, rename, movement, deletes, copy user folder and file.

Preferably, after execution step S402, said method can also comprise following process:

(1) authority of client to the fileinfo of request access checks by message storage server;

(2) fileinfo of message storage server determination client to request has access control right.

Wherein, the access control right of client define user can to the access of institute's storage resources under the file in message storage server and this file and manipulation ability.When user's request manipulates the resource that message storage server stores (when performing different operational orders), all need to check the access control right of respective resources this requesting party, only has satisfied certain authority, message storage server just can perform relevant operation, otherwise message storage server is by the request command of refusal requesting party, and returns error response message.

According to the definition in [RFC 4314 ACL expands], above-mentioned access control right can see Access Control List (ACL) (ACL), wherein, ACL is one group of <Access Identifiers, rights> value is right, " Access Identifiers " identifies person liable, and " rights " identifies corresponding person liable which access control right.An ACL is applied to " mailbox " (i.e. a file).

[RFC 4314] access control right that to be the file on IMAP4 server and the resources definition under file following, and identified by different jurisdiction identifier, such as:

L:lookup, represents that file can list, namely can by LIST, LSUB, SUBSCRIBE command access;

R:read, represents that file is readable, can by SELECT, STATUS command access;

S: keep seen/unseen label information in a session, namely by STORE command set or removing SEEN mark;

W:write, represents that file can be write, and namely arranges by STORE or removes other marks except SEEN and DELETED, or being arranged other marks except SEEN and DELETED by APPEND, COPY order;

I:insert, represents that file can by APPEND, COPY command operation;

K:create mailboxes, represents and can use CREATE order under this file, create the word file of arbitrary levels, or moves/rename operation by RENAME order to this file;

X:delete mailboxes, represents that this file is deleted by DELETE order, or can be deleted source folder by RENAME order;

T:delete Messages, is arranged or removing DELETED mark the file under this file by STORE operation, is marked by APPEND/COPY Ming Lingshezhi DELETED;

E: by EXPUNGE command execution deletion action;

A:administer, can perform the order that SETACL, DELETEACL, GETACL, LISTRIGHTS etc. manage Access Control List (ACL);

In specific implementation process, file in message storage server can be divided into two kinds of different types: (1) is by the file of system creation, as " Root-User " root file, and " Conversation-History " meeting history record file; (2) file created by User Defined, as " Folder1 ", " Folder2 " etc.;

Will be first the authority that this folder allocation is certain when MSS creates a file, user should perform according to authority the operation of this file afterwards.Certainly, the file created according to system request and user ask the difference of the file created, and MSS is that the authority that it distributes is not identical yet.

Such as, for system-level folder allocation user access control authority, CPM user mainly checks behavior to system folder, should limit other as amendment, delete, the operating right such as mobile, prevent the misoperation of user to the destruction of CPM meeting history record integrality.So for system-level file, following access rights can be distributed: l, r etc.System folder can not distribute following access rights: x, k etc.

When for User Defined folder allocation access control right, because user has access control right completely to the file that oneself creates, all jurisdiction identifier can be distributed, and user can also according to the regulation of [RFC 4314] and flow process, managed the various access control rights of user-defined file folder by orders such as SETACL, DELETEACL, GETACL, LISTRIGHTS, be the ability that other CPM user gives the associated rights of calling party user-defined file folder.

Respectively user's " operation of acquisition Access Control List (ACL) ", " arranging Access Control List (ACL) operation ", " deleting Access Control List (ACL) operation " and " gain access operation " are described below in conjunction with four embodiments, wherein, aforesaid operations all carries out for user folder, system folder is due to for security consideration, do not distribute " a " (administer) authority to user, therefore user cannot the Access Control List (ACL) of management system file.

Embodiment one: user obtains Access Control List (ACL) operation

If user wants the Access Control List (ACL) obtaining certain user folder, then according to the regulation in [RFC4314], construct IMAP4/GETACL order by MSC, the title of intended target file, to the Access Control List (ACL) of MSS request target file, specifically can see Fig. 6.

User asks the Access Control List (ACL) of " Working " user folder to MSS, and MSS checks after receiving this order whether requesting party user has " a " authority to destination folder, namely whether can obtain the authority of Access Control List (ACL).If have this authority, then MSS backward reference in the response message to GETACL order controls list, as shown above, show in Access Control List (ACL), user " Fred " has " rwipslxetad " authority to destination folder, and user " Chris " has " lrswi " authority to destination folder.

If requesting party user does not have " a " authority to destination folder, then MSS should use failed response message to refuse the GETACL order of requesting party.

Embodiment two: user arranges Access Control List (ACL) operation

If user wishes to arrange the Access Control List (ACL) of certain user folder, such as give some authority for other user, then should according to the flow process of regulation in [RFC 4314], IMAP4/SETACL order is constructed by MSC, request MSS is the access control right that intended target file adds to certain user, specifically can see Fig. 7.

User is the access control right " cda " that other user " Chris " increases to destination folder " Working " to MSS request.After MSS receives this order, first should check whether requesting party user has " a " authority to destination folder, if requesting party user has " a " authority to destination folder, so MSS is by according to the request in SETACL order, in Access Control List (ACL) for destination folder " Working ", increase " cda " authority of " Chris " user; If requesting party user does not have " a " authority to destination folder, then MSS should use failed response message to refuse the SETACL order of requesting party.

Embodiment three: user deletes Access Control List (ACL) operation

If user wishes to delete the Access Control List (ACL) of another user to certain user folder, then should according to the flow process of regulation in [RFC 4314], construct " IMAP4/DELETEACL " by MSC to order, designated user is deleted the access control right list of destination folder by request MSS, specifically can see Fig. 8.

User deletes other user " Fred " to the access control right list of destination folder " Working " to MSS request.After MSS receives this order, first should check whether requesting party user has " a " authority to destination folder; If requesting party user has " a " authority to destination folder, so MSS is by according to the request in DELETEACL order, in the Access Control List (ACL) for destination folder " Working ", deletes all access control rights of " Fred " user; If requesting party user does not have " a " authority to destination folder, then MSS should use failed response message to refuse the DELETEACL order of requesting party.

Embodiment four: user's gain access operates

If user wants to obtain the user folder that certain specific user creates oneself have which access control right, then can according to the regulation in [RFC 4314], construct " IMAP4/LISTRIGHTS " by MSC to order, request MSS returns the access control right list of designated user to destination folder, specifically can see Fig. 9.

User obtains certain user " Smith " to the access control right list of destination folder " Working " to MSS request.After MSS receives this order, first should check whether requesting party user has " a " authority to destination folder; If requesting party user has " a " authority to destination folder, so MSS is by according to the request in LISTRIGHTS order, in the Access Control List (ACL) of destination folder " Working ", search all access control rights of " Smith " user, and return in the response message to LISTRIGHTS order; If requesting party user does not have " a " authority to destination folder, then MSS should use failed response message to refuse the LISTRIGHTS order of requesting party.

User carries out message stores accessing operation and mainly comprises following process (operation one to operation ten):

In specific implementation process, when CPM user wishes to check the content that MSS stores, MSC (i.e. above-mentioned client) first will be used to log in MSS (i.e. message storage server).

Step 1, user use MSC to log in MSS;

Wherein, MSC by according to the regulation of [RFC 3501] and flow process by using IMAP4/AUTHENTICATE order or carrying out certification between IMAP4/LOGIN order and MSS, only has authentication success, MSC just can access the resource on MSS, if authentification failure, MSC cannot access the resource on MSS.

Preferably, AUTHENTICATE order allows MSC not send the user name and password of text formatting, but uses other authentication mechanism to log in MSS.When using this order, MSC must according to the regulation in [RFC 3501] and flow process, construct an effective AUTHENTICATE order, and use specific authentication mechanism in <authentication mechanism name> parameter.

Can return a prompt strings after step 2:MSS receives this order, prompting MSC selects suitable authentication method, if MSS does not support the authentication method that MSC advises, will return NO response message.At this moment MSC must attempt using other authentication methods, until use LOGIN order.

Wherein, LOGIN order allows MSC to use the user name and password of text mode to log in MSS, although this is not a good method, is all spendable unique method between MSC and MSS sometimes.When using this order, MSC must according to the regulation in [RFC 3501] and flow process, construct an effective LOGIN order, in <user name> parameter, use the user name of MSC, in <password> parameter, use password.

After step 3:MSS receives LOGIN order, use the user name and password to carry out certification, if authentication success, then return OK response message, authentification failure then returns NO response message, if parameter error, returns BAD response message.

After user's log messages memory, if user selects certain file (can be system folder, also can be user folder) check, so first MSC carries the name of this file by structure IMAP4/SELECT order ([RFC 3501]), and request MSS chooses this file.After MSS receives this order, destination folder is set to enliven file.

As shown in Figure 10, if user selects " Conversation-History " file, then the SELECT order that MSC is constructed as follows asks this file sandwiched to be set to enliven file to MSS.

Equally, user can also choose user folder to be set to enliven file.

Operation one, user choose meeting history record case, check the list of CPM meeting history record;

After user logs in MSS by MSC, first the file available folder list on server can be obtained, user sees on interface " Conversation-History " file (meeting history record case), when there being which meeting history record under user wishes to check meeting history record file, MSC will ask the relevant information of meeting history record to MSS.

Preferably, when user needs to check meeting history record information, method can also comprise following process:

(1) message storage server receives the talks metadata information request instruction coming from client, and wherein, talks metadata information request instruction carries the catalogue identification information of talks belonging to metadata information;

(2) talks metadata information is sent to client to carry out resolving and presenting by message storage server.

In framework shown in above-mentioned Fig. 2, all record objects are dispersed in arbitrary file, do not define corresponding mechanism to represent " meeting history record ".And in the storage architecture shown in Fig. 5, talks view can be provided by talks metadata.

Particularly, MSC can use IMAP4/GETMETADATA order ([RFC5464]), the name of intended target file is called " Conversation-History ", to meeting history record file acquisition request " talks information metadata table " all meeting history record metadata informations of MSS.MSC, after getting the relevant descriptor of talks, carries out resolving and represents talks view in client.(note: MSC presented to by those CPM that " deleted field " is set to " True " talks view that can not be provided by system of talking.)

Be described below in conjunction with example.

If user selects CPM talks file (i.e. " Conversation-History "), wish to check CPM protocol information, then MSC should send IMAP4/GETMETADATA order ([RFC 5464]) to MSS, obtain the CPM talks metadata information that " Conversation-History " file is associated, as the descriptor of CPM talks, represent in client.

Because CPM talks are logical concept, not actual physical storage entity corresponds, summary info (as initiated time, end time, talks theme, the participant etc.) information of that is CPM talks all come from these talks the CPM message that comprises or CPM file transfer historical record or CPM conversation history record.When MSC is to MSS request talks summary info, MSS can not go to resolve CPM Message Record file or CPM file transfer history file or CPM conversation history log file at every turn, thus obtain the relevant information of CPM talks, and these information can be recorded preferably by metadata.Therefore the GETMETADATA order that use [RFC 5264] is expanded is to obtain talks information metadata, specifically see Figure 11.

As shown in figure 11, after this GETMETADATA request command, perform following steps:

Step 1: resolve this order, extract < destination folder title > parameter for " Conversation-History ", < option > parameter is " DEPTH infinity ", and <entry> parameter is after "/shared/Conversation/ ";

Step 2: according to metadata table " Conversation " by name, MSS inquires about " the CPM talks information metadata table " of meeting history record file, obtain all that " Deleted " field in this table and be set to that the record of " False " is capable (represents that user did not perform those records of protocol deletion action, i.e. effective meeting history record information) all fields and the value of correspondence, returned to MSC by the acknowledgement command of GETMETADATA.

As seen from the figure, obtain effective CPM that MSS stores in the response message of GETMETADATA order that MSS returns to talk all information of information metadata table.A series of value that what GETMETADATA order as shown in Figure 6 returned is is to <entry, value>, and wherein, entry indicates the field in metadata table, and the value value that to be this field corresponding.Such as "/shared/conversation/convID1/StartTime " 2009/05/22 18:00 " " represents in talks information table that the talks time started (" StartTime ") that identifier of talking is the CPM meeting history record of " ConvID1 " is " 2009/05/22 18:00 ".Such MSC just can get on MSS to store which talks, and the summary info of these talks, and MSC just can be represented by boundary's user oriented.Such as, after user have selected talks file, the summary info of all CPM talks stored under unit shows this talks file will be recorded as with a line in the viewing area on right side.

Operation two, user select a meeting history record, check the particular content of this meeting history record;

Preferably, after checking meeting history record information, method can also comprise following process:

(1) message storage server receives the record object id information coming from client;

(2) the part or all of information of record object corresponding for record object id information is sent to client to present by message storage server.

In specific implementation process, when user is after acquisition talks list, the relevant metadata information of these talks has been got by order, wherein, this information includes the value of <Content-UID> field, this CPM just of this field value record talks all CPM Message Records comprised, CPM file transfer historical record, the UID (the unique location identifier on MSS) of CPM conversation history log file, use these UID, MSC just can obtain header information or the content information of the relevant all log files of this CPM talks to MSS by the corresponding command, present in this locality.

Be described below in conjunction with example.

When CPM user views talks information list, a wherein CPM meeting history record may be selected, check its detailed record content.Because MSC has got the title of CPM meeting history record meeting history record sub-folder corresponding on MSS by LIST order, then MSC can choose corresponding meeting history record sub-folder by IMAP4/SELECT order, relevant all log files of talking to this CPM under this file are obtained again by IMAP4/FETCH order, specifically can see Figure 12.

As shown in figure 12, after MSC chooses corresponding meeting history record sub-folder by IMAP4/SELECT order ([RFC 3501]), the head of CPM Message Record file, CPM file transfer history file and the CPM conversation history log file that just can be comprised to these talks of MSS acquisition request by IMAP4/FETCH order ([RFC 3501]) or body part information, after MSS receives this order, get relevant information and returned to MSC by FETCH acknowledgement command.

MSC states information on local storage, and resolves, and represents the content of this CPM meeting history record to user.

User browses CPM meeting history record content, if wish the content of checking the media attachment that certain CPM message or CPM conversation history record carry, then MSC carries the part numbering of wishing the Message Record file at media attachment place or the UID of CPM conversation history log file and the media attachment obtained by FETCH order, to MSS request msg.MSS resolves after receiving this order, obtains corresponding data return to MSC according to UID and No. Part, and MSC stores in this locality and carries out parsing and presents.

In specific implementation process, above-mentioned User Defined file (User Defined file directory) is that user creates in the user management region of MSS.Due to the restriction of operating right, user haves no right to create file in system management region, is merely able in user management region, create user-defined file folder.

MSC creates User Defined file by structure IMAP4/CREATE order ([RFC 3501]) request MSS, and in <mailbox name> parameter in CREATE order, carry the title of the file that this user will create, the designator standardization path naming rule of this file, uses oblique line (/) as level separator.

As shown in figure 13, MSC uses CREATE order to create the file of " working/ims/cpm " by name, and this path is not when existing, first MSS will create working file and ims file under the login directory of user, then creates cpm file under working/ims path.

When MSC receives the OK acknowledgement command from MSS, represent that creating portfolio operations is successfully completed, MSC presents the new file created in this locality.If when MSC receives from the NO acknowledgement command of MSS or BAD acknowledgement command, represent and create portfolio operations failure, can not create the file of specifying, then MSC returns miscue information to user.

Operate three, when part or all of meeting history record information is added to user-defined file catalogue (namely user adds CPM Message Record (or wherein certain is a part of), CPM file transfer historical record, CPM conversation history record (or wherein certain is a part of) or CPM meeting history record in user-defined file folder) by access instruction instruction, above-mentioned steps S406 may further include following process:

(1) message storage server is added on needing the entry of association in link metadata information, is associated with User Defined file directory to make the part or all of information of entry;

(2) message storage server upgrades the associate field of talks metadata information according to the type of entry.

In specific implementation process, user is when browsing CPM meeting history record, may to certain part (as certain picture, audio frequency, video) in certain CPM Message Record/CPM file transfer historical record/CPM conversation history record or log file or interested in this whole piece CPM meeting history record, wish them to add in self-defining file to carry out Classification Management, carry out Classification Management, thus build personalized view.Then perform following process:

Step 1: user performs " adding operation ", MSC, by " the link metadata information table " of structure IMAP4/SETMETADATA order ([RFC 5464]) modifying target user folder, increases the entry of this record object of association.

After step 2:MSS receives this request command, first carry out resolving the title obtaining destination folder, then the link metadata information table of this file is inquired about, increase corresponding entry in the table, certain part of the record of specifying be actually stored in meeting history record file or record is associated with this file.

Step 3:MSS is according to the classification of affiliated partner, correspondingly upgrade " Tag " field in talks information metadata table, message/transfer file history metadata table, conversation history record metadata table, add the title of destination subscriptions folder and/or associated No. Part, to add incidence relation.

Be described below in conjunction with example.

User is when browsing CPM meeting history record content, may to certain part (as certain picture, audio frequency, video) or interested in whole CPM meeting history record in certain CPM Message Record, CPM file transfer historical record or certain CPM meeting history record or these records, wish them to add in self-defining file to carry out Classification Management, then user performs " adding linked object operation ".

In traditional messaging service (as Email), under adopting IMAP4/COPY order to copy source file to destination folder in units of file, if use this order, then user is merely able to be recorded as unit with an entire message record, conversation history.And in this technological invention scheme, MSC is by " the link metadata information table " of structure IMAP4/SETMETADATA order modify target file folder, increase the entry relevant to associated record object, certain part (as certain picture, audio frequency, video etc.) in association CPM meeting history record or a log file or log file can be realized neatly.

As shown in figure 14, MSC is before initiation " adds linked object operation ", first to be obtained up-to-date " linking metadata " that server is associated with destination subscriptions folder by IMAP4/GETMETADATA order, can correctly to modify operation to " the link metadata " on MSS.

As shown in figure 14, MSC has had 9 linked objects under having known user folder on MSS " Working ", then when the Part 2 (annex 1) that the UID stored under talks file is the CPM Message Record of 2 adds in user-defined " Working " file by MSC request, link metadata sequence number increments should be set to 10.

MSS receives this order and performs following operation afterwards:

Step 1, to resolve, obtain the name of destination subscriptions folder;

Step 2, find the link metadata table " Relevance " of " Working " file, the record that value is " 10 " is searched in " Seq " field in the table, if found, there is the chained record that sequence number is 10 under this file is described, then MSS returns wrong responses; If there is no this record, then the record that increase sequence number is " 10 " adds in this metadata table by MSS, and <Link> field is set to " Message/2/2 ";

Step 3, in successful operation situation, MSS returns successful respond to MSC.

Step 4, MSS upgrade " the CPM message/file transmission history record metadata table " of " Conversation-History " file, find UID be 2 that record, then in " Tag " field of this record, add " Working/2 " character string, represent that Part 2 part of this Message Record and Working file are associated.

In like manner, if the CPM conversation history record that it is 13 that MSC wishes the UID stored under talks file adds in user-defined " My Favorite " file, then first MSC should ask current up-to-date " link metadata " information of user folder " My Favorite " to MSS, 10 linked objects are had under knowing this file current, then the sequence number increments of link metadata is set to 11 by MSC, and uses following order:

SETMETADATA“My Favorite”(/shared/Relevance/11/Link“Session/13”)

MSS receives after this order resolves, first (11 are added in " link metadata information table " (Relevance) of " My Favorite " file, Session/13) after record row, also need " the conversation history record metadata table " that upgrade " Conversation-History " file, find UID be 13 that record, then in " Tag " field of this entry, add the title of " My Favorite " file, show that this conversation history log file and " My Favorite " file are associated.

Preferably, if MSC wishes a CPM meeting history record to add in user-defined " Working " file, then following order is used:

SETMETADATA“working”(/shared/Relevance/12/Link“Conversation/convID1”)

MSS receives after this order resolves, first (12 are added in " link metadata information table " (Relevance) of " Working " file, Conversation/conID1) after record row, also need " the CPM talks information metadata table " that upgrade " Conversation-History " file, talks identifier is found to be that record of convID1, then in " Tag " field of this entry, add the title of " Working " file, show that this meeting history record file and " Working " file are associated.

Operate four, when information corresponding for system predefine file directory carries out presenting (namely user checks the content in the systemic presupposition file such as " SendBox ", " ReceivedBox ") by access instruction instruction, message storage server perform the accessing operation corresponding with access instruction according to link metadata information and comprises:

(1) the first meeting history record identification information that system predefine file directory associates is sent to client by message storage server;

(2) when the first identification information of whole log files corresponding to the first meeting history record identification information is preserved in client this locality, message storage server receives all or part of first identification information coming from client;

Preferably, when the identification information of whole log files corresponding to meeting history record identification information is not preserved in client this locality, method can also comprise:

(2.1) message storage server receives the identification request instruction coming from client;

(2.2) identification information of whole log files corresponding for meeting history record identification information is sent to client by message storage server;

(2.3) message storage server receives the identification information coming from all or part of whole log file of client, and recorded information corresponding for the identification information of all or part of whole log file is sent to client to present.

(3) recorded information corresponding for all or part of first identification information is sent to client to present by message storage server.

In specific implementation process, MSC obtains user's request, by " the link metadata " of IMAP4/GETMETADATA order to MSS request target file, thus obtains the talks identifier information of all meeting history records associated by this file.

Wherein, MSC obtains " SendBox " or after the talks identifier of meeting history record associated by " ReceivedBox " file, comprise following two kinds of processing modes:

Mode 1: if the descriptor of talks is preserved in this locality, the i.e. UID information (as obtained when by checking " Conversation-History " folder content) of all log files that comprises of these talks, then MSC is first by SELECT command selection " Conversation-History " file, then these UID are used, by the particular content of IMAP4/FETCH order to the request relative recording file of MSS;

Mode 2: if the descriptor of talks is not preserved in MSC this locality, then MSC is first by the content of IMAP4/GETMETADATA order to " Content-UID " field of the request talks metadata of MSS, obtain the UID information of all log files that these talks comprise, and then by SELECT command selection " Conversation-History " file, finally use above-mentioned UID, asked the particular content of relative recording file by IMAP4/FETCH order to MSS.

Operate five, when information corresponding for User Defined file directory carries out presenting (namely user checks the content in user-defined file folder) by access instruction instruction, message storage server perform the accessing operation corresponding with access instruction according to link metadata information and can also comprise:

(1) the second meeting history record identification information that User Defined file directory associates by message storage server is sent to client;

(2) when the second identification information of whole log files corresponding to the second meeting history record identification information is preserved in client this locality, message storage server receives all or part of second identification information coming from client;

(3) recorded information corresponding for all or part of second identification information is sent to client to present by message storage server.

In specific implementation process, check when user selects user-defined file to press from both sides, in above-mentioned file except linked object, also may store the log file that user uploads from this locality.Therefore, first MSC chooses user folder by SELECT order, the UID of the physical record file stored under obtaining this file, then by FETCH order, above-mentioned user is uploaded content retrieval this locality of log file.Then, MSC is asked to MSS by IMAP4/GETMETADATA order " the link metadata " of this user folder again, thus obtains the UID information of the all-links object associated by this file.Concrete process comprises following three kinds of situations:

Situation one: if association is whole meeting history record, then MSC will obtain the talks identifier of this meeting history record, and in the talks information using this talks identifier to store in this locality (obtaining when checking talks list operation), inquire about the UID of the relative recording file that these talks comprise, then use these UID by the particular content of IMAP4/FETCH order to these talks of meeting history record file request of MSS;

Situation two: if association is complete Message Record, file transfer historical record or a conversation history log file, then MSC will obtain the UID of this log file, and then MSC uses this UID by the particular content of IMAP4/FETCH order to this log file of meeting history record file request of MSS;

Situation three: if association is certain part (as certain media object of carrying) of a piece of news log file or conversation history log file, then MSC will obtain the UID of corresponding record file and indicate the <Part-Number> of this part, and then MSC uses this UID and <Part-Number> by the particular content of IMAP/FETCH order to this part of meeting history record file request of MSS.

Then, MSC chooses " Conversation-History " file by SELECT order, and use the UID information of the record object of the association obtained, by FETCH operation, the content retrieval of affiliated partner is local, therefore user just can view the content in user-defined file folder.

Be described below in conjunction with example.

User browses when have selected self-defining file (as " Working "), then first MSC needs MSS to send SELECT order to choose destination folder " Working ", and the UID of log file that the user stored under getting this file in the acknowledgement command returned at MSS uploads.Then these are recorded content retrieval this locality by FETCH UID order by MSC.Then MSC uses " link metadata " information of GETMETADATA command request " Working " file, can obtain the identifier information of all CPM Message Record, CPM file transfer historical record, CPM conversation history record or CPM meeting history record object associated by this file.

As shown in figure 15, MSC is according to [RFC 5464] structure GETMETADATA order, Offered target folder name is the User Defined folder name " Working " wishing to check, < option > parameter is set for " DEPTH infinity ", expression obtains all records in metadata table, <entry> parameter is set for "/shared/Relevance ", represents the record during hope obtains " link metadata information table ".

After MSS receives this order, obtain the parameter value entrained by GETMETADATA order, then go to obtain all entries in " the link metadata information table " of destination folder, and returned to MSC by the response message of GETMETADATA order.MSC by resolve acknowledgement command just can obtain under this file associated by all CPM conversation history records, CPM Message Record, CPM file transfer historical record UID or UID+<Part-Number>, or the talks identifier of CPM meeting history record.

Then MSC performs SELECT order, choose talks file, then use FETCH order to go MSS obtains the record content of actual storage by the various UID that obtains and relevant <Par-Number>, as shown in figure 16, MSC asks acquisition UID to be the Part 2 of the log file of 2 to MSS, request UID is the Part 3 of the log file of 12, request UID is 1,2,4, the head of the log file of 5,6 and body part.MSC presents to user in this locality and checks after obtaining these record contents.

Operation six, user delete meeting history record

When user needs to delete a whole piece meeting history record information in described system management region, described method can also comprise following process:

(1) message storage server obtains the identification information of the whole log files corresponding to a whole piece meeting history record information;

(2) when the associate field of information metadata information of talking is empty, message storage server deletes the entry corresponding to a whole piece meeting history record information;

(3) when the associate field of message/transfer file history information or conversation history record metadata information is empty, message storage server deletes entry corresponding to the identification information of the whole log files corresponding to a whole piece meeting history record information.

In specific implementation process, MSC receives the removal request of user, MSC uses " IMAP4/STORE [UID-List]+FLAG (Deleted) " order, and (UID-List indicates those to wish the UID list of the log file deleted, being separated with comma) request MSS deletes this meeting history record, and all log files that this meeting history record comprises.

Following process should be performed after MSS receives this order.

Step 1:MSS uses " Content-UID " field of " the talks information metadata table " of UID list query " Conversation-History " file obtained from STORE order, find corresponding meeting history record item, then check that whether " Tag " field of this entry is empty, if be empty, then perform step 2; If be not sky, perform step 3;

Step 2: if this CPM meeting history record does not have to associate with other user folder, performs following steps:

Step 2.1: delete capable for the record of the correspondence of this meeting history record from " talks information metadata table ";

Step 2.2: use UID list to inquire about " UID " field of " CPM message/file transmission history record metadata table " and " CPM conversation history record metadata table " respectively, find corresponding record;

Step 2.3: check that whether " Tag " field of this record is empty, if be empty, illustrate that this record does not have to associate with any other User Defined file, can delete, perform following steps: the FLAG label ([RFC3501]) of the log file representated by this UID is set to (DELETE) state; The recorded information row of this message object is deleted from corresponding metadata table; Upgrade " the link metadata table " of " ReceivedBox " or " SendBox ", the link information representated by this UID is deleted, to upgrade " inbox " and " outbox " view.

Step 2.4: if " Tag " field is not empty, illustrate that this record object is also associated with other User Defined file, then " Belonged-to-Conv-ID " field of this record object is set to sky, represent that this meeting history record belonging to record object is deleted, this record object no longer associates with talks, and exists as independently recording object.

Repeat 2.3 and 2.4 steps, go over until all UID items in UID list are all examined.

Step 3: if this CPM meeting history record associates with other user folder, then this CPM all log files comprised of talking all can not be deleted by reality, that record that this CPM in information table that then talked by CPM talks corresponding " deleted field " is set to " True ", represents that user performed deletion action.

Execute above-mentioned step, if successful operation, MSS returns successful operation response message to MSC, and MSC upgrades local talks view, is no longer shown the content of this CPM meeting history record by talks file.

Be described below in conjunction with example.

User is when checking meeting history record list information, as shown in figure 17, if wish to delete certain CPM meeting history record, then first choose this CPM meeting history record, because MSC is when checking the list of CPM protocol, by GETMETADATA order get CPM talk all log files comprised UID (by " Content-UID " field) obtain, then MSC use STORE [UID-List]+FLAG (Deleted) order to delete (UID-List indicates those to wish the UID list of the log file deleted, be separated with comma).

When MSC asks MSS to delete certain CPM meeting history record, MSC obtains the UID of all log files that this meeting history record comprises, and constructs STORE order, asks deletion action to MSS.Command interaction flow process between MSC and MSS is as shown below:

Following handling process should be performed after MSS receives this order, specifically can see Figure 18.

Step 1:MSS uses the UID list (1 obtained from STORE order, 2,3,5,6) inquire about " Content-UID " field of " the CPM talks information metadata table " of " Conversation-History " file, find corresponding meeting history record item, then check that whether " Tag " field of this entry is empty, if be empty, then perform step 2, if be not sky, perform step 3;

Step 2: this CPM meeting history record does not have to associate with other user folder, then perform following steps:

Step 2.1: delete capable for the record of the correspondence of this meeting history record from " talks information metadata table ";

Step 2.2: use UID list (1,2,3,5,6) to inquire about " UID " field of " CPM message/file transmission history record metadata table " and " CPM conversation history record metadata table " respectively, find corresponding record;

Step 2.3: " Tag " field checking this record, if " Tag " field is empty, then performs following steps: the FLAG label ([RFC3501]) of the log file representated by this UID is set to (DELETE) state; The recorded information row of this message object is deleted from corresponding metadata table; Upgrade " the link metadata table " of " SendBox " or " ReceivedBox ", the link information representated by this UID is deleted, to upgrade " Inbox " and " outbox folder " view.If this field is not empty, then perform step 2.4;

Step 2.4: " Tag " field is not empty, illustrate that this record object is also associated with other User Defined file, can not delete, then capable for this record corresponding " Belonged-to-Conv-ID " field is being set to sky, illustrate deleted for the meeting history record belonging to this record object, this record object no longer associates with talks, and as independently log file existence.

Step 2.5: constantly repeated execution of steps 2.3 and 2.4, goes over until all UID items in UID list are all examined.

Step 3: this CPM meeting history record associates with other user folder, then this CPM all log files comprised of talking all can not be deleted (because this meeting history record is associated with in self-defining file by user by reality, he thinks that this is important information), then in CPM talks information table, " deleted field " of that record that this CPM talks corresponding is set to " True ", represents that user performed deletion action.Note, those CPM talks that " deleted field " is set to " True " can not return to MSC and present.

When MSC receives the response of the deletion meeting history record successful operation that MSS returns, think that this CPM meeting history record is deleted successfully, then MSC upgrades local view, no longer under talks file, shows the relevant information of these talks.

Operation seven, access instruction instruction by link metadata information corresponding for User Defined file directory partly or entirely carry out delete (namely user delete user-defined file folder in linked object) time, message storage server according to link metadata information execution the accessing operation corresponding with access instruction comprise:

(1) entry needing to delete is deleted, to make part or all of information and the User Defined file directory onrelevant of entry by message storage server in link metadata information;

(2) message storage server deletes the identification information of User Defined file directory in the associate field of talks metadata information according to the type of entry.

In specific implementation process, MSC obtains user's removal request, uses IMAP4/SETMETADATA order, the value of the link metadata of destination object is set to " NIL ".

Following process will be performed after MSS receives this order:

Step 1: in " the link metadata table " of destination subscriptions folder, finds the record of that link metadata of specifying, is then deleted by this line item;

Step 2: the type checking the chained record object that will delete, if CPM Message Record (or wherein certain is a part of), CPM file transfer historical record or CPM conversation history record (or wherein certain is a part of), then performs step 3; If CPM meeting history record object, then perform step 4:

Step 3: " the CPM message/file transmission history record metadata table " or " CPM conversation history record metadata table " that find meeting history record file, find " Tag " field of that record of request disassociation relation, first the title of destination folder is removed from the value of " Tag " field, then check whether this field is empty, if be sky, performs step 3.1; Otherwise, perform step 3.2;

Step 3.1: this record object is not associated by any user folder again, checks " Belonged-to-Conv-ID field ", if this field is empty, then performs step a; Otherwise, then step b is performed;

Step a: illustrate that the meeting history record at this record object place is deleted, it is a unique file, can be deleted, then perform following steps: the metadata of this log file by actually from meeting history record file for this log file deleting (arrange its FLAG be DELETE), and is deleted by MSS from corresponding metadata table; Upgrade " the link metadata table " of " ReceivedBox " or " SendBox ", by the linked object information deletion representated by this UID, to upgrade " inbox " and " outbox " view;

Step b: illustrate that the meeting history record at this record object place also exists, then this log file can not be deleted, then end operation;

This record object is also associated with other user folder, can not delete, end operation;

Find " the CPM talks information metadata table " of meeting history record file, find " Tag " field of that record of request disassociation relation, first the title of destination folder is removed from the value of " Tag " field, then check whether this field is empty, if be sky, performs step 4.1; If be not empty, then perform step 4.2.

Step 4.1: this protocol object is not associated by any user folder again, checks " Deleted " field, if this field is set to " True ", then performs step a, if this field is set to " False ", then performs step b:

Step a: illustrate that this meeting history record is performed deletion action by user, can be deleted, then metadata record row corresponding for meeting history record is deleted by MSS from talks information metadata table, and according to description relevant in " (5) user deletes CPM meeting history record ", check that log file that these talks comprise is the need of being deleted simultaneously;

Step b: illustrate that this meeting history record is not also performed deletion action by user, then this meeting history record can't be deleted, end operation;

Step 4.2: this record object also associates with other user folder, then this record object can not be deleted, end operation;

Execute above-mentioned step, if successful operation, MSS returns successful operation response message to MSC, and MSC upgrades local talks view, is no longer shown the content of this record by this user folder.

Be described below in conjunction with example.

User, when browsing the content under user-defined file folder, if feel not wish certain record object to be placed in this file, wants it to delete, then should perform following step.

Note, owing to may there is the record object that user uploads in user folder, also likely there is linked object, for these two kinds different objects, the deletion action of MSC is also different.Because MSC is when obtaining the content stored under user folder, the record object (by SELECT+FETCH order) uploaded of user and linked object (by GETMETADATA+FETCH order) is obtained exactly by different operations, so for MSC, it can distinguish the different object of this two class under user folder, and when performing deletion action, adopt different orders, as shown in figure 13.

If what delete is the log file that user uploads, then use IMAP/STORE order that this file is set to (Deleted) state;

If what delete is linked object, then use SETMETADATA order, as shown in figure 13.

Order as shown in fig. 13 that, will the incidence relation between Part 2 that Working file and UID are the CPM Message Record file of 2 be removed.

Following process will be performed after MSS receives this order:

Step 1: in " link metadata information table " (Relevance) of Working file, finds <Link> field value to be that record of "/Message/2/2 ", is then deleted by this line item;

Step 2: in " the CPM message/file transmission log metadata table " of " Conversation-History " file, find <UID> field be 2 that record, then perform following steps:

Step 2.1: check and first remove this " Tag " field recorded " working/2 " character string information from this field, if after removing, " Tag " field is empty, then perform step 2.2); If after removing, " Tag " field is not empty, then perform step 2.3);

Step 2.2: this record object no longer associates with other user folder, then check " Belonged-to-ConID " field:

If this field is empty, then illustrates that this record object has relieved with CPM talks and associate, be a unique file, do not have again other user folder associate with it again, then should delete from MSS, the FLAG that MSS arranges this log file is " DELETE "; And upgrade " the link metadata table " of " SendBox Folder " or " ReceivedBox Folder ", the link information representated by this UID is deleted, to upgrade " Inbox " and " outbox folder " view;

If this field is not empty, illustrates that this record object is also talked with CPM and be associated, can not be deleted by reality, then end operation;

Step 2.3: illustrate that this object is also associated by other user folder, can not delete, then end operation.

If perform in above-mentioned process log file actual deletion action (by this log file FLAG mark be set to "/Deleted ", then also should upgrade the link metadata information table of " Inbox ", " outbox folder ", the link metadata of this deleted log file deleted from table, namely deleted log file can not occur in " inbox " or " outbox " view.

Operate eight, when User Defined file directory carries out deleting (namely user deletes self-defining user folder) by access instruction instruction, message storage server perform the accessing operation corresponding with access instruction according to link metadata information and comprises:

(1) message storage server obtains the identification information that whole log files that these talks comprise are referred in the meeting of link corresponding to metadata information;

(2) when the associate field of information metadata information of talking is empty, the entry of talks in message storage server, is deleted;

(3) when the associate field of message/transfer file history information or conversation history record metadata information is empty, the entry that the identification information of all or part of whole log file is corresponding in message storage server, is deleted.

In specific implementation process, MSC obtains user's request, uses IMAP4/DELETE order ([RFC 3501]) to be deleted by the user folder of specifying.MSS resolves after receiving this DELETE order, extracts the title of the destination folder that will delete, then performs following steps:

Step 1: check and " link metadata information table " that destination subscriptions folder is relevant obtain UID and the Part information of all record objects associated by this user folder;

Step 2: to each the linked object record in " link metadata information table ", perform the corresponding operating described in " (6) user deletes the linked object in user-defined file folder " respectively, according to different classes of (may be meeting history record, Message Record, file transfer historical record or conversation history record) of these linked objects, check, determine whether the log file can deleting actual storage.

Step 3: after processing above process, deletes corresponding for this destination folder " link metadata table ";

Step 4: this user folder is deleted.

MSS returns successfully response message to MSC after performing above successful operation, and MSC upgrades local view, no longer shows deleted self-defined user folder.

Be described below in conjunction with example.

User, when browsing the content under user-defined file folder, if feel not wish certain record object to be placed in this file, wants it to delete, then should perform following step.

Note, owing to may there is the record object that user uploads in user folder, also likely there is linked object, for these two kinds different objects, the deletion action of MSC is also different.Because MSC is when obtaining the content stored under user folder, the record object (by SELECT+FETCH order) uploaded of user and linked object (by GETMETADATA+FETCH order) is obtained exactly by different operations, so for MSC, it can distinguish the different object of this two class under user folder, and when performing deletion action, adopt different orders, as shown in figure 13.

If what delete is the log file that user uploads, then use IMAP/STORE order that this file is set to (Deleted) state;

If what delete is linked object, then use SETMETADATA order, as shown in figure 13.

Order as shown in figure 19, will remove the incidence relation between Part 2 that Working file and UID are the CPM Message Record file of 2.

Following process will be performed after MSS receives this order:

Step 1: in " link metadata information table " (Relevance) of Working file, finds <Link> field value to be that record of "/Message/2/2 ", is then deleted by this line item;

Step 2: in " the CPM message/file transmission log metadata table " of " Conversation-History " file, find <UID> field be 2 that record, then perform following steps:

Step 2.1: check and first remove this " Tag " field recorded " working/2 " character string information from this field, if after removing, " Tag " field is empty, then perform step 2.2); If after removing, " Tag " field is not empty, then perform step 2.3);

Step 2.2: this record object no longer associates with other user folder, then check " Belonged-to-ConID " field:

If this field is empty, then illustrates that this record object has relieved with CPM talks and associate, be a unique file, do not have again other user folder associate with it again, then should delete from MSS, the FLAG that MSS arranges this log file is " DELETE "; And upgrade " the link metadata table " of " SendBox Folder " or " ReceivedBox Folder ", the link information representated by this UID is deleted, to upgrade " Inbox " and " outbox folder " view;

If this field is not empty, illustrates that this record object is also talked with CPM and be associated, can not be deleted by reality, then end operation;

Step 2.3: illustrate that this object is also associated by other user folder, can not delete, then end operation.

If perform in above-mentioned process log file actual deletion action (by this log file FLAG mark be set to "/Deleted ", then also should upgrade the link metadata information table of " Inbox ", " outbox folder ", the link metadata of this deleted log file deleted from table, namely deleted log file can not occur in " inbox " or " outbox " view.

Operate nine, when User Defined file directory carries out deleting (namely user deletes user-defined file folder) by access instruction instruction, message storage server perform the accessing operation corresponding with access instruction according to link metadata information and comprises following process:

(1) message storage server obtains the identification information that whole log files that these talks comprise are referred in the meeting of link corresponding to metadata information;

(2) when the associate field of information metadata information of talking is empty, the entry of talks in message storage server, is deleted;

(3) when the associate field of message/transfer file history information or conversation history record metadata information is empty, the entry that the identification information of all or part of whole log file is corresponding in message storage server, is deleted.

In specific implementation process, if user wishes to be copied to by certain linked object in object file from source folder, then this linked object is added in the link metadata information table of destination folder by IMAP4/SETMETADATA command request by MSC.

After MSS receives SETMETADATA order, link the renewal rewards theory of metadata information table accordingly, and correspondingly upgrade content in " Tag " field of CPM talks information metadata table, CPM message/file transmission history record metadata table or CPM conversation history record metadata table.

MSS successful operation, returns successfully response message to MSC.

Be described below in conjunction with example.

If user wishes to delete self-defining file, but there is again the log file object be associated in this file, then client should reminding user, " this file non-NULL; this file is emptied and deletes? " if user determines to perform deletion action, then MSC should use IMAP4/DELETE ([RFC 3501]) to order the file deletion of will specify.

If user wishes to delete user-defined file folder " Working ", then MSC structure " DELETE " Working " " order.MS S resolves after receiving this DELETE order, extracts the title (" Working ") of the destination folder that will delete, then performs following steps:

Step 1: " link metadata information table " that query aim file is corresponding, obtain all record row in this table, every a line represents an affiliated partner;

Step 2: the type checking the affiliated partner of every a line, if association is CPM Message Record (or wherein certain is a part of), CPM file transfer historical record or CPM conversation history record (or wherein certain is a part of), then performs step 3; If association is CPM meeting history record, then perform step 4:

Step 3: " the CPM message/file transmission history record metadata table " or " CPM conversation history record metadata table " that find meeting history record file, find " Tag " field of that record of request disassociation relation, first the title of destination folder is removed from the value of " Tag " field, then check whether this field is empty, if be sky, performs step 3.1; If be not empty, perform step 3.2;

Step 3.1: this record object is not associated by any user folder again, checks " Belonged-to-Conv-ID field ", if this field is empty, then performs step a; If this field is not empty, then perform step b;

Step a: illustrate that the meeting history record at this record object place is deleted, it is a unique file, can be deleted, then this log file is deleted (arrange its FLAG be DELETE) by MSS from meeting history record file, and the metadata of this log file is deleted from corresponding metadata table; And upgrade " the link metadata table " of " SendBox " or " ReceivedBox ", the link information representated by this UID is deleted, to upgrade " inbox " and " outbox " view;

Step b: illustrate that the meeting history record at this record object place also exists, then this log file can not be deleted, end operation;

Step 3.2: this record object is also associated with other user folder, can not delete, end operation;

Step 4: " the CPM talks information metadata table " that find meeting history record file, find " Tag " field of that record of request disassociation relation, first the title of destination folder is removed from the value of " Tag " field, then check whether this field is empty, if be sky, performs step 4.1); If be not empty, then perform step 4.2):

Step 4.1: this record object is not associated by any user folder again, checks " Deleted " field, if this field is set to " True ", then performs step a, if this field is set to " False ", then performs step b:

Step a: illustrate that this meeting history record is performed deletion action by user, can be deleted, then metadata record row corresponding for meeting history record is deleted by MSS from talks information metadata table, and according to description relevant in " (5) user deletes CPM meeting history record ", check that log file that these talks comprise is the need of being deleted simultaneously;

Step b: illustrate that this meeting history record is not also performed deletion action by user, then this meeting history record can't be deleted, end operation;

Step 4.2: this record object also associates with other user folder, then this record object can not be deleted, end operation;

Continuous repetition step 2,3,4, until all record row checking out in " the link metadata information table " of destination subscriptions folder.After processing above process, should " link metadata information table " delete;

Step 6: this user folder is deleted.

Aforesaid operations success, MSS returns DELETE order successful respond message to MSC, thinks that all the elements of this user folder and association thereof are deleted on the server after MSC receives, then more new user interface, to user's display operation result.

Operate ten, when linked object carries out copying (i.e. user's replication link object) by access instruction instruction, message storage server perform the accessing operation corresponding with access instruction according to link metadata information and comprises following process:

(1) message storage server is by linked object from link metadata information corresponding to source file catalogue, is copied in link metadata information corresponding to object file directory;

(2) message storage server upgrades the associate field of talks metadata information according to the type of linked object.

In specific implementation process, if user wishes to be copied to by certain linked object in object file from source folder, then this linked object is added in the link metadata information table of destination folder by IMAP4/SETMETADATA command request by MSC.

After MSS receives SETMETADATA order, link the renewal rewards theory of metadata information table accordingly, and correspondingly upgrade content in " Tag " field of CPM talks information metadata table, CPM message/file transmission history record metadata table or CPM conversation history record metadata table.

MSS successful operation, returns successfully response message to MSC.

Operate 11, when linked object moves by access instruction instruction, message storage server perform the accessing operation corresponding with access instruction according to link metadata information and comprises:

(1) message storage server is by linked object from link metadata information corresponding to source file catalogue, moves in link metadata information corresponding to object file directory;

(2) message storage server upgrades the associate field of talks metadata information according to the type of linked object.

In specific implementation process, if user wishes to be moved to by certain linked object in object file from source folder, then first this linked object is added in the link metadata information table of destination folder by SETMETADATA command request by MSC, and then uses SETMETADATA command request to delete the metadata information of this linked object in source folder.

After MSS receives SETMETADATA order, link the renewal rewards theory of metadata information table accordingly, and correspondingly upgrade content in " Tag " field of CPM talks information metadata table, CPM message/file transmission history record metadata table or CPM conversation history record metadata table.

MSS successful operation, returns successfully response message to MSC.

Be described below in conjunction with example.

If user wishes certain linked object to move on in another user-defined file, then first this link is added to another file " link metadata information table " in, and then perform the metadata information deletion action of source folder, as shown in figure 20.

After order that MSS receives " SETMETADATA "/My Favorite " (/shared/Relevance/15/Link " Message/2/2 ") ", perform following steps (as 3.2.3 trifle " user adds chained record " operation):

First in the metadata table of " My Favorite " file, add chained record that <Seq> field be " 15 " and (suppose that MSC has operated to be informed in link metadata information up-to-date in object file " My Favorite " by GETMETADATA and has 14 records, then construct SETMETADATA order interpolation the 15th chained record), the value of the <Link> field of this chained record is " Message/2/2 ";

Then in the CPM Message Record metadata table of " Conversation-History ", find UID be 2 entry, in " Tag " field of this entry, add " MyFavorite/2 " information.

After order that MSS receives " SETMETADATA "/Working " (/shared/link/message/2/2 NIL) ", perform associative operation according to " user deletes linked object " described in operation seven.

According to the embodiment of the present invention, additionally provide a kind of access means of IP message (CPM) meeting history record of fusion.

Figure 21 is the structured flowchart of the message storage server according to the embodiment of the present invention.As shown in figure 21, comprise according to the access means of the CPM meeting history record of the embodiment of the present invention: the first receiving element 1, parsing acquiring unit 2, performance element 3.

First receiving element 1, for receiving the access instruction coming from client;

Resolve acquiring unit 2, obtain for resolving access instruction the file directory mark needing access, and obtain link metadata information corresponding to file directory mark;

Performance element 3, for performing the accessing operation corresponding with access instruction according to link metadata information.

In the storage area of above-mentioned message storage server, store link metadata information, associate to the accessing operation in user management region with the CPM meeting history record stored in system management region, can meet user to the self-defined bookkeeping of the record resource that message storage server stores while, multiple view can also be provided for user.

Preferably, as shown in figure 22, said apparatus can also comprise: the first creating unit 4, for creating system management region in message storage server, wherein, system management region comprises the first memory cell of storage meeting history record information, the second memory cell of storage system predefine fileinfo; Second creating unit 5, for creating user management region in message storage server, wherein, user management region comprises the 3rd memory cell storing customized information.

Preferably, as shown in figure 22, said apparatus can also comprise: the second receiving element 6, for receiving the local record fileinfo coming from client upload.

Preferably, as shown in figure 22, said apparatus can also comprise: authenticating unit 7, for the authority of client to the fileinfo of request access being checked; Determining unit 8, for determining that the fileinfo of client to request has access control right.

The working method that in said apparatus, each unit be combined with each other, see the description of Fig. 4 to Figure 20, can repeat no more herein.

In sum, pass through the above embodiment of the present invention, for the meeting history record in converged message service communication environment defines the memory model of its feature suitable, and form a whole set of complete scheme by the relevant metadata of definition and relevant storage management operations, except the feature of CPM talks can be met, meet user to outside the self-defined bookkeeping of the record resource that message storage server stores simultaneously, multiple view can also be provided for user, as view of talking (checking meeting history record in units of CPM talks), the linear view (view built according to the relation of replying-being responded) of talks, and system predefine view (as according to transmitting-receiving relational view, subject classification view) and user self-definition view (User Defined file, and the partial content in interested log file or log file is added in user-defined file folder), under the prerequisite as far as possible reducing message storage server administration overhead, good business experience can be provided for user.

Obviously, those skilled in the art should be understood that, above-mentioned of the present invention each module or each step can realize with general calculation element, they can concentrate on single calculation element, or be distributed on network that multiple calculation element forms, alternatively, they can realize with the executable program code of calculation element, thus, they can be stored and be performed by calculation element in the storage device, and in some cases, step shown or described by can performing with the order be different from herein, or they are made into each integrated circuit modules respectively, or the multiple module in them or step are made into single integrated circuit module to realize.Like this, the present invention is not restricted to any specific hardware and software combination.

The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.

Claims (21)

1. an access method for the IP message CPM meeting history record merged, is characterized in that, comprising:

Message storage server receives the access instruction coming from client;

Described message storage server is resolved described access instruction and is obtained the file directory mark needing access, and obtains link metadata information corresponding to described file directory mark;

Described message storage server performs the accessing operation corresponding with described access instruction according to described link metadata information;

Wherein, described link metadata information is for maintaining the incidence relation between CPM conversation content and the file be linked to.

2. method according to claim 1, is characterized in that, before message storage server reception comes from the described access instruction of client, described method also comprises:

In described message storage server, create system management region, wherein, described system management region comprises the first memory cell of storage meeting history record information, the second memory cell of storage system predefine fileinfo;

In described message storage server, create user management region, wherein, described user management region comprises the 3rd memory cell storing customized information;

Wherein, described user management region is the region that in memory space, user has complete administration authority.

3. method according to claim 2, is characterized in that,

Described meeting history record information comprises: talks metadata information and record object information, wherein, described record object information comprises: at least one CPM Message Record information, at least one CPM file transfer history information, at least one CPM conversation history recorded information;

Described system predefine fileinfo comprises: the link metadata information of the predefined file directory subordinate of the predefined file directory of system, described system;

Described customized information comprises: the link metadata information of User Defined file directory, described user-defined file directory subordinate.

4. method according to claim 3, is characterized in that, described User Defined fileinfo also comprises:

The local record fileinfo of described client upload.

5. method according to claim 3, is characterized in that, described talks metadata information comprises:

Talks information metadata information, message/transfer file history information, conversation history record metadata information.

6. method according to any one of claim 1 to 5, is characterized in that, after described message storage server reception comes from the access instruction of client, described method also comprises:

The authority of described client to the fileinfo of request access checks by described message storage server;

Described message storage server determines that the fileinfo of described client to described request has access control right.

7. method according to claim 3, is characterized in that, before message storage server reception comes from the access instruction of client, when user needs to check described meeting history record information, described method also comprises:

Described message storage server receives the talks metadata information request instruction coming from described client, and wherein, described talks metadata information request instruction carries the catalogue identification information belonging to described talks metadata information;

Described talks metadata information is sent to described client to carry out resolving and presenting by described message storage server.

8. method according to claim 7, is characterized in that, after checking described meeting history record information, described method also comprises:

Described message storage server receives the record object id information coming from described client;

The part or all of information of record object corresponding for described record object id information is sent to described client to present by described message storage server.

9. method according to claim 5, is characterized in that, when user needs to delete a whole piece meeting history record information in described system management region, described method also comprises:

Described message storage server obtains the identification information of the whole log files corresponding to a described whole piece meeting history record information;

When the associate field of described talks information metadata information is empty, described message storage server deletes the entry corresponding to a described whole piece meeting history record information;

When the associate field of described message/transfer file history information or described conversation history record metadata information is empty, described message storage server deletes entry corresponding to the identification information of the whole log files corresponding to a described whole piece meeting history record information.

10. method according to claim 3, it is characterized in that, when described access instruction instruction adds part or all of described meeting history record information to user-defined file catalogue, described message storage server performs the accessing operation corresponding with described access instruction according to described link metadata information and comprises:

Described message storage server is added in described link metadata information by needing the entry of association, is associated with described User Defined file directory to make the part or all of information of described entry;

Described message storage server upgrades the associate field of described talks metadata information according to the type of described entry.

11. methods according to claim 3, it is characterized in that, undertaken in current in described access instruction instruction by information corresponding for described system predefine file directory, described message storage server performs the accessing operation corresponding with described access instruction according to described link metadata information and comprises:

The first meeting history record identification information that described system predefine file directory associates is sent to described client by described message storage server;

When the first identification information of whole log files corresponding to described first meeting history record identification information is preserved in described client this locality, described message storage server receives all or part of described first identification information coming from described client;

Recorded information corresponding for all or part of described first identification information is sent to described client to present by described message storage server.

12. methods according to claim 11, is characterized in that, when the identification information of whole log files corresponding to described meeting history record identification information is not preserved in described client this locality, described method also comprises:

Described message storage server receives the identification request instruction coming from described client;

The identification information of whole log files corresponding for described meeting history record identification information is sent to described client by described message storage server;

Described message storage server receives the identification information coming from all or part of described whole log file of described client, and recorded information corresponding for the identification information of all or part of described whole log file is sent to described client to present.

13. methods according to claim 3, it is characterized in that, undertaken in current in described access instruction instruction by information corresponding for described User Defined file directory, described message storage server performs the accessing operation corresponding with described access instruction according to described link metadata information and comprises:

The second meeting history record identification information that described User Defined file directory associates by described message storage server is sent to described client;

When the second identification information of whole log files corresponding to described second meeting history record identification information is preserved in described client this locality, described message storage server receives all or part of described second identification information coming from described client;

Recorded information corresponding for all or part of described second identification information is sent to described client to present by described message storage server.

14. methods according to claim 3, it is characterized in that, when the instruction of described access instruction is by partly or entirely the deleting of link metadata information corresponding for described User Defined file directory, described message storage server performs the accessing operation corresponding with described access instruction according to described link metadata information and comprises:

Described message storage server is deleted needing the entry of deleting, to make the part or all of information of described entry and described User Defined file directory onrelevant in described link metadata information;

Described message storage server deletes the identification information of described User Defined file directory according to the type of described entry in the associate field of described talks metadata information.

15. methods according to claim 3, it is characterized in that, when described User Defined file directory is deleted by described access instruction instruction, described message storage server performs the accessing operation corresponding with described access instruction according to described link metadata information and comprises:

The identification information of whole log files that these talks comprise is referred in the meeting obtained corresponding to described link metadata information of described message storage server;

When the associate field of described talks information metadata information is empty, in described message storage server, delete the entry of described talks;

When the associate field of described message/transfer file history information or described conversation history record metadata information is empty, described message storage server deletes entry corresponding to the identification information of all or part of described whole log file.

16. methods according to claim 3, is characterized in that, when linked object copies by described access instruction instruction, described message storage server performs the accessing operation corresponding with described access instruction according to described link metadata information and comprises:

Described linked object from link metadata information corresponding to source file catalogue, is copied in link metadata information corresponding to object file directory by described message storage server;

Described message storage server upgrades the associate field of described talks metadata information according to the type of described linked object.

17. methods according to claim 3, is characterized in that, when linked object moves by described access instruction instruction, described message storage server performs the accessing operation corresponding with described access instruction according to described link metadata information and comprises:

Described linked object from link metadata information corresponding to source file catalogue, moves in link metadata information corresponding to object file directory by described message storage server;

Described message storage server upgrades the associate field of described talks metadata information according to the type of described linked object.

18. 1 kinds of message storage server, is characterized in that, comprising:

First receiving element, for receiving the access instruction coming from client;

Resolve acquiring unit, obtain for resolving described access instruction the file directory mark needing access, and obtain link metadata information corresponding to described file directory mark;

Performance element, for performing the accessing operation corresponding with described access instruction according to described link metadata information;

Wherein, described link metadata information is for maintaining the incidence relation between CPM conversation content and the file be linked to.

19. message storage server according to claim 18, is characterized in that, described message storage server also comprises:

First creating unit, for creating system management region in described message storage server, wherein, described system management region comprises the first memory cell of storage meeting history record information, the second memory cell of storage system predefine fileinfo;

Second creating unit, for creating user management region in described message storage server, wherein, described user management region comprises the 3rd memory cell storing customized information;

Wherein, described user management region is the region that in memory space, user has complete administration authority.

20. message storage server according to claim 18, is characterized in that, described message storage server also comprises:

Second receiving element, for receiving the local record fileinfo coming from client upload.

21., according to claim 18 to the message storage server described in 20 any one, is characterized in that, described message storage server also comprises:

Authenticating unit, for checking the authority of described client to the fileinfo of request access;

Determining unit, for determining that the fileinfo of described client to described request has access control right.