WO2017045536A1

WO2017045536A1 - Multiparty session processing method and device

Info

Publication number: WO2017045536A1
Application number: PCT/CN2016/097960
Authority: WO
Inventors: 李秋婷
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-09-15
Filing date: 2016-09-02
Publication date: 2017-03-23
Also published as: CN106534054A

Abstract

The invention provides a multiparty session processing method and device. The multiparty session processing method comprises: establishing, on a hosting common service entity (CSE), a subscription resource configured to subscribe to a multiparty session on the hosting CSE or register a multiparty session of an application entity on the hosting CSE. By adopting the technical scheme provided in the invention, the embodiment can resolve a problem of an unsupported interaction procedure in a multihop session in a one machine-to-machine (oneM2M) system in the prior art, expanding applications of an oneM2M system.

Description

Multi-party session processing method and device

Technical field

This application relates to, but is not limited to, the field of communications.

Background technique

The One Machine to Machine (oneM2M) architecture is a resource-based architecture. The capabilities of a terminal device or a terminal device or an application, platform, or application can be regarded as a resource. Application or background application resources are represented by AE (Application Entity), and the terminal device application or platform capability resource is represented by CSE (Common Service Entity). Each AE needs to be registered to at least one CSE, and each CSE. Create a CSEbase (common services entity base) resource tree, which contains multiple different types of sub-resources to describe the resources of the local CSE; at the same time, AE and CSE can be registered to another CSE, and A sub-resource is generated under the CSEbase resource tree in the registered CSE to describe the registered AE and CSE. The CSE registered by the AE is called a hosting CSE (hosting common service entity), and the CSE where the resource to be addressed is also called a hosting CSE.

At present, single-hop point-to-point session management has been implemented in an IoT system, which can be satisfied by current communication management capabilities, and can easily manage the sending and receiving of a message between a point and a point, each time sending and receiving Receives a new connection. However, in the actual Internet of Things scenario, there are also interaction scenarios between points and points, points and multiple points, and multiple points and multiple points. The above multi-hop interaction scene is complex, and the entire interaction process needs to be managed, such as Interaction establishment, state management, etc., which simplifies the interaction process and provides service quality. The IoT system is not yet supported.

In the related art, in the Internet of Things system, an effective technical solution has not been proposed for the problem that the interaction process between multi-hop sessions is not yet supported.

Summary of the invention

The following is an overview of the topics detailed in this document. This summary is not intended to limit the claims The scope of protection.

The present invention provides a multi-party session processing method for establishing a multi-party session between entities by creating and/or updating session resources of a multi-party session.

Optionally, a multi-party session between entities is established by creating and/or updating session resources of the multi-party session, including:

The session management/creation entity requests the hosted general service entity CSE of the invited entity to create a session resource of the multiparty session for the invited entity;

After the session management/creation entity receives the message that the invited entity of the hosted CSE reply of the invited entity agrees to join the multi-party session, updating the created in the managed CSE of the session management/creation entity Session resources for multiparty sessions.

The invited entity is informed that it is invited to join the multi-party session and agrees to join the multi-party conference;

A session resource of the multiparty session is created for the invited entity in a hosted CSE of the invited entity.

Wherein, when the invited entity itself is the hosted CSE of the invited entity:

The inviting entity is informed that the invitation to join the multi-party session may include: receiving, by the session management/creation entity, a request for creating the session resource of the multi-party session for the invited entity;

Creating the session resource of the multi-party session for the invited entity in the managed CSE of the invited entity may include: the invited entity creating a session resource of the multi-party session under resources of the invited entity After that, the invited entity also replies to the session management/creation entity with a message agreeing to join the multiparty session.

Wherein, when the invited entity is an application entity AE:

The inviting entity is informed that the invitation to join the multi-party session may be: receiving a subscription notification sent by the hosted CSE of the invited entity to join the multi-party session;

Creating the session resource of the multi-party session for the invited entity in the hosted CSE of the invited entity may include: the invited entity sending a consent to the hosted CSE of the invited entity Joining the message of the multiparty session, creating a session resource of the multiparty session for the invited entity by the hosted CSE of the invited entity.

The hosted CSE of the invited entity receives a request sent by the session management/creation entity to create the session resource of the multi-party session for the invited entity, and sends a notification of the subscription to the invited entity to join the multi-party session. The invited entity is an AE;

After the hosted CSE of the invited entity receives the message that the invited entity agrees to join the multi-party session, the session resource of the multi-party session is created under the resource corresponding to the invited entity, and is managed to the session. / Create an entity replies to the message that the invited entity agrees to join the multiparty session.

The hosted CSE of the invited entity may first search for the subscription resource created by the invited entity after receiving the request for the session entity to create the session resource of the multi-party session sent by the session entity. If found, the subscription notification is sent; wherein the subscription resource is used to subscribe to the invitation of the multi-party session.

The managed CSE requesting to join the entity requesting session management/creation entity updates the session resources of the multiparty session to join the multiparty session;

After the request joining entity receives the message of the host CSE reply of the session management/creation entity agreeing to join the multi-party session, creating the multi-party session for the request joining entity in the managed CSE of the request joining entity Session resources.

The session management/creation entity learns that the request to join the entity requests to join the multi-party session, and agrees that the request joins the entity to join the multi-party session;

Updating the session resources of the multiparty session in the managed CSE of the session management/creation entity.

Wherein the session management/creation entity itself is the hosting of the session management/creation entity When CSE:

The session management/creation entity learns that the requesting to join the entity to request to join the multi-party session may include: receiving a request sent by the request joining entity to update the session resource of the multi-party session;

Updating the session resource of the multiparty session in the managed CSE of the session management/creation entity may include: the session management/creation entity updating a session resource of the multiparty session; afterwards, the session management/creation entity further The request join entity replies to a message agreeing to join the multiparty session.

Wherein, when the session management/creation entity is AE:

The session management/creation entity learns that the requesting to join the entity to request to join the multi-party session may include: receiving a request sent by the hosted CSE of the session management/creation entity to join the entity to request to join the subscription notification of the multi-party session;

Updating the session resource of the multiparty session in the managed CSE of the session management/creation entity may include: the session management/creation entity sending to the hosted CSE of the session management/creation entity agreeing to the request to join the entity joining site The message of the multiparty session is updated by the session management/creation entity's managed CSE.

After receiving the request to join the entity to update the session resource of the multi-party session, the managed CSE of the session management/creation entity sends a request notification to the session management/creation entity requesting to join the multi-party session, The session management/creation entity is AE;

The managed CSE of the session management/creation entity receives the request that the session management/creation entity agrees to the request to join the entity to join the multi-party session, updates the request for the session resource of the multi-party session, and sends the request to the request The joining entity replies to the message that it joins the multiparty session.

The managed CSE of the session management/creation entity may first search for the subscription resource created by the session management/creation entity after receiving the request to join the entity to update the session resource of the multi-party session; The subscription notification; wherein the subscription resource is used for a request for a subscription entity to join a multiparty session.

Optionally, the session resource of the multi-party session includes attribute information and/or a message sub-resource;

The attribute information of the session resource includes at least one of the following information: a session message, a session identifier, Session topic, session creator, session participant, session entity state, maximum number;

The message sub-resource is used to describe a message transmitted during a multi-party session, and includes at least one of the following information: a message identifier, a message status, a message format, a message sender, a message receiver, and a message sending time.

The present invention also provides a multi-party session processing apparatus, which is applied to a general service entity CSE or an application entity AE as a session management/creation entity, and the processing apparatus includes:

a session invitation module, configured to: request a hosted CSE of the invited entity to create a session resource of the multiparty session for the invited entity;

a resource update module, configured to: after receiving the message that the invited entity of the hosted CSE reply of the invited entity agrees to join the multi-party session, update the created in the managed CSE of the session management/creation entity Session resources for multiparty sessions.

The present invention also provides a multi-party session processing apparatus, which is applied to a CSE as an invited entity, and the processing apparatus includes:

The invitation processing module is configured to: after receiving the request sent by the session management/creation entity to create the session resource of the multi-party session for the invited entity, if agreeing to join the multi-party conference, reply to the session management/creation entity Joining the message of the multiparty session;

The resource creation module is configured to: create a session resource of the multi-party session under the resource of the invited entity, if it is agreed to join the multi-party conference.

The present invention also provides a multi-party session processing apparatus, which is applied to an AE as an invited entity, and the processing apparatus includes:

An invitation receiving module, configured to: receive a subscription notification sent by the hosted CSE of the invited entity to join the multi-party session;

The invitation reply module is configured to: send a message agreeing to join the multiparty session to the hosted CSE of the invited entity when agreeing to join the multiparty conference.

The present invention also provides a processing apparatus for a multi-party session, which is applied to an entity hosting a CSE as an invited entity, the processing apparatus comprising:

a subscription processing module, configured to: after receiving a request sent by the session management/creation entity to create the session resource of the multi-party session for the invited entity, send a subscription notification to the invited entity to invite the join party to join the multi-party session; And after receiving the message that the invited entity agrees to join the multi-party session, replying to the session management/creation entity, the message that the invited entity agrees to join the multi-party session, where the invited entity is an AE;

The resource creation module is configured to: after receiving the message that the invited entity agrees to join the multi-party session, create a session resource of the multi-party session under the resource corresponding to the invited entity.

Optionally, after receiving the request sent by the session management/creation entity to create the session resource of the multi-party session, the subscription processing module first searches for a subscription resource created by the invited entity, such as searching. And sending the subscription notification; wherein the subscription resource is used to subscribe to the invitation of the multi-party session.

The present invention also provides a processing device for a multi-party session, which is applied to a CSE or an AE as a requesting entity, the processing device comprising:

a requesting module, configured to: request a session management/creation entity to host a CSE to update a session resource of the multiparty session to join the multiparty session;

a resource creation module, configured to: after receiving the message that the host CSE reply of the session management/creation entity agrees to join the multi-party session, create the content for the request joining entity in the managed CSE of the request joining entity Session resources for multiparty sessions.

The present invention also provides a multi-party session processing apparatus, which is applied to a CSE as a session management/creation entity, and the processing apparatus includes:

a request processing module, configured to: after receiving the request for adding the session resource of the multi-party session sent by the request joining entity, if the requesting to join the entity joins the multi-party session, agreeing to join the requesting entity The message of the multiparty session;

And a resource update module, configured to: if the request to join the entity joins the multiparty session, update the session resource of the multiparty session.

The present invention also provides a processing apparatus for a multi-party session, which is applied to an AE as a session management/creation entity, the processing apparatus comprising:

a request receiving module, configured to: receive a request sent by the hosted CSE of the session management/creation entity to join a subscription request to join the multi-party session;

The request reply module is configured to: send a message agreeing to the requesting joining entity to join the multiparty session to the managed CSE of the session management/creation entity if the requesting join entity joins the multiparty session.

The present invention also provides a multi-party session processing apparatus, which is applied to an entity that hosts a CSE as a session management/creation entity, and the processing apparatus includes:

a subscription processing module, configured to: after receiving a request to join the entity to update the session resource of the multi-party session, send, to the session management/creation entity, the subscription notification that the request join entity requests to join the multi-party session; and After receiving the message that the session management/creation entity agrees to join the entity to join the multi-party session, the message is sent to the requesting entity to agree to join the multi-party session; the session management/creation entity is AE

The resource update module is configured to: after receiving the message that the session management/creation entity agrees to join the entity to join the multi-party session, update the request for the session resource of the multi-party session.

Optionally, after receiving the request to join the entity to update the session resource of the multi-party session, the subscription processing module first searches for a subscription resource created by the session management/creation entity; if found, sends the subscription notification again. The subscription resource is used to subscribe to a request for an entity to join a multiparty session.

According to another aspect of the present invention, a method for processing a multiparty session is provided, comprising: creating a session resource on a hosted CSE, wherein the session resource is used to describe a multiparty session of the hosted CSE or to be registered on the hosted CSE AE's multiparty conversation.

Optionally, the method for creating a session resource includes one of the following: when the session management/creation entity invites other entities to join the multi-party session, sending a message to the hosted CSE of the other entity to request to create a session resource, where When the other entity is an AE, the hosted CSE needs to notify the AE and obtain its consent to create the session resource; when an entity requests to join the session, send a message to the session management/creation entity to request to update the session. Manage/create session resources for an entity Joining the session, when the session management/creation entity agrees, creating a session resource in the hosted CSE of the entity requesting to join the session;

Optionally, the session management/creation entity invites other entities to join a certain session. When the other entity is an AE, the hosted CSE of the other entity needs to create a subscription resource in advance for subscribing to the invitation of the multi-party session; When the management/creation entity sends a request to create a session resource in the hosted CSE of another entity, it indicates that the session management/creation entity requests to join the session in another entity, and the other entity is notified according to the subscription condition in the implementation subscription resource, and other entities are informed and If the session invitation is agreed, the session resource created by the session management/creation entity is created in the hosted CSE of the other entity; when the other entity is the managed CSE, there is no need to create a subscription resource, and the hosted CSE creates a session according to the analysis. Resource

Optionally, the certain entity requests to join a certain session. When the certain session management/creation entity is an AE, a subscription resource needs to be created in the managed CSE of the session management/creation entity for the subscription entity to join. a request for a session; when the sending message of the certain entity requests to update the session resource of the management/creation entity, indicating that the entity requests to join the session of the management/creation entity, according to the subscription condition in the subscription resource Notifying the session management/creation entity, the session management/creation entity agrees to join and feed back session information to the certain entity, the certain entity creating a session resource in its hosted CSE; when the session is managed/created When the entity is a managed CSE, there is no need to create a subscription resource, and the hosted CSE directly feeds back information to the entity according to the join request analysis, and the entity creates a session resource in its hosted CSE;

Optionally, the method further includes: creating a session resource in a managed CSE of the entity of the entity that is requested to join the multi-party session or inviting an entity to join the entity of the multi-party session, And creating a session resource on the managed CSE of the multi-party session management/creation entity,

Optionally, the session information is described by an attribute of the session resource or a sub-resource of the session resource.

Optionally, the attributes of the session resource include at least one of the following: a message, a multi-party session identifier ID, a multi-party session topic, a multi-party session creator, a multi-party session participant, a multi-party session entity state, and a maximum number.

Optionally, the method further includes: creating a message sub-resource under the session resource, where The message sub-resource is used to describe a message generated during a multi-party session, and the message sub-resource includes at least one of the following: a message ID, a message status, a message format, a message sender, and a message receiver.

According to still another aspect of the present invention, there is also provided a processing apparatus for a multiparty session, comprising: a create/update module for creating/updating a session resource on a managed CSE, wherein the session resource is used to describe the hosted CSE A multiparty session or a multiparty session registered with an AE on the hosted CSE.

Optionally, the session resource creation manner in the creating module includes one of the following: when the session management/creation entity invites other entities to join the multi-party session, the session resource is created in the managed CSE of the other entity, where When the other entity is an AE, the hosted CSE needs to notify the AE and obtain its consent to create the session resource; when an entity requests to join the session, send a message to the session management/creation entity to request to join the a session, when the session management/creation entity agrees, create a session resource in a hosted CSE of an entity requesting to join the session;

Optionally, the device further includes a subscription module, a notification module, an invitation for subscribing to the session, and a request to join, that is, creation/update of the session resource, and the notification module is configured to notify the other session entity to join the session or the session. The session management/creation entity has an entity requesting to join the session;

Optionally, the subscription module creates a subscription resource on the hosted CSE for subscription subscription registration on the hosted CSE to join the session, or a subscription request to join the session registered/created by the AE on the hosted CSE;

Optionally, the notification module is configured to notify an AE registered on the managed CSE, where the notification module includes:

a first sending unit, configured to: when the session management/creation entity invites an AE entity registered on the managed CSE to join the multi-party session, the session management/creation entity sends an invitation request to the hosted CSE registered by the AE entity, The managed CSE sends the invitation request to the AE entity to notify the AE entity that the session management/creation entity invites it to join the multiparty session;

a second sending unit, configured to: when an entity requests to join the multi-party session created by the session management/creation entity, and the session management/creation entity is an AE, the certain entity sends a join request to the a session management/creation of a hosted CSE registered by the entity, the hosted CSE transmitting the join request to the session management/creation entity notifying the registered entity of the following: An entity requests to join a multiparty session created by the registered entity.

The foregoing solution solves the problem that the related technology does not support the interaction process between the multi-hop sessions by creating and/or updating the multi-party session between the entities of the multi-party session, and provides a solution for supporting the multi-party session. The application scenario of the Internet of Things system is expanded.

Other features and advantages of the embodiments of the invention will be set forth in the description in the description in the claims The objectives and other advantages of the embodiments of the present invention can be realized and obtained by the structure of the invention.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

FIG. 1 is a flowchart of a method for processing a multiparty session according to an embodiment of the present invention; FIG.

2 is a structural block diagram of a processing apparatus for a multiparty session according to an embodiment of the present invention;

FIG. 3 is a block diagram showing another structure of a multi-party session processing apparatus according to an embodiment of the present invention; FIG.

4 is a structural block diagram of a processing apparatus of a multiparty session according to an example of the present invention;

FIG. 5 is a structural diagram of a multi-party session resource and its sub-resources according to an embodiment of the present invention; FIG.

6 is a schematic flow chart of inviting a multiparty session according to an embodiment of the present invention;

FIG. 7 is a schematic flowchart of actively joining a multiparty session according to an embodiment of the present invention; FIG.

FIG. 8 is a schematic flowchart of message sending and receiving in a multi-party session according to an embodiment of the present invention.

Preferred embodiment of the invention

Embodiments of the present invention will be described below with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the various manners in the embodiments may be combined with each other without conflict.

In the embodiment of the present invention, a method for processing a multi-party session is provided. FIG. 1 is a flowchart of a method for processing a multi-party session according to an embodiment of the present invention. As shown in FIG. 1, the method includes the following steps:

Step S102: Create/update a session resource in the hosting CSE, where the session resource is used to describe the multi-party session information of the hosting CSE or the AE registered on the hosting CSE;

Step S104, processing the multi-party session according to the creation/update of the session resource.

Through the above steps, by creating or updating the hosting CSE or the multi-party session resource of the AE registered on the hosting CSE on the hosting CSE, the interaction process between the multi-hop sessions in the IoT system is solved in the related art. The problem that is not yet supported provides a solution to support multi-party sessions, extending the application scenario of the IoT system.

The above solution can be summarized as: based on the IoT resource structure, in the Internet of Things, the hosting CSE creates/updates a session resource, and is used to establish a hosting CSE or an AE registered on the hosting CSE with other entities, wherein the The creation/update of session resources is created in the hosting CSE of the entity invited to join the session, and in the hosting CSE of the entity requesting to join the session. Unless otherwise stated, a conversation in the text refers to a multiparty conversation.

In the embodiment of the present invention, the method for creating a session resource includes one of the following: when the session management/creation entity invites other entities to join the multi-party session, sending a message to the hosting CSE of the other entity to request to create a session resource, where When the other entity is an AE, the hosting CSE needs to notify the AE and obtain its consent to create the session resource; when an entity requests to join the session, send a message to the session management/creation entity to request an update. The session resource of the session management/creation entity is added to the session, and when the session management/creation entity agrees, the session resource is created in the hosting CSE of the entity that requests to join the session;

The session management/creation entity invites other entities to join the multi-party session. The session creation entity invites other entities to join the multi-party session during the session creation process. Alternatively, after the session creation is completed, the session management entity invites other entities to join the multi-party. Session; the session management entity and the session creation entity can be the same or different.

The session resource indicates the session information through the attribute and/or the sub-resource of the resource, and the session information is sent by the hosting CSE of the session management/creation entity to the entity invited to join the session or actively requesting to join the session; the attributes of the session resource include at least one of the following: : message, multiparty session ID, multiparty session subject, multiparty session creator, multiparty session participant, multiparty session entity status, maximum number.

The method further includes: creating a message sub-resource under the foregoing session resource, where the message sub-resource is used to describe a message generated during a multi-party session, where the message sub-resource includes at least one of the following: a message ID, a message status , message format, message sender, message receiver.

That is to say, the establishment of an inter-entity session is achieved by creating a session resource in the host's hosting CSE. The creation of a session resource, when an entity is invited to join the session, the session resource is created in the hosting CSE of the invited entity; or when an entity actively requests to join the session, after obtaining the session management/creation entity consent, at a certain Create session resources in the entity's hosting CSE.

The session resources created in the hosting CSE of each entity in the same session indicate that the session information attribute and the sub-resource are basically the same, such as a session ID, a multi-party session topic, and the like.

In order to better understand the above technical solution, the above method further includes:

When the session entity (including the invited session entity and the session management/creation entity) is an AE, a subscription resource is created in the host's hosting CSE for the subscription inviting entity to join the session or the entity requesting to join the session.

In an optional embodiment of the present invention, a subscription resource is created in an hosting CSE of an entity, and the subscription resource describes that when the session management/creation entity invites an entity to join the session, the hosting CSE notifies the invited session entity that The session management/creation entity invites them to join the session;

In another optional embodiment of the present invention, a subscription resource is created in the hosting of the session management/creation entity, and the subscription resource describes a hosting CSE notification session when an entity requests to join the session management/create session. The management/creation entity has an entity requesting to join the session;

When the invited entity agrees to join the invited session or the session management/creation entity agrees that an entity joins its managed/created session, the invited entity or the hosting CSE requesting to join the entity can create the session resource.

It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should understand that the present invention is not limited by the described action sequence. Because certain steps may be performed in other sequences or concurrently in accordance with the present invention. Secondly, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

In the embodiment, a processing device for a multi-party session is also provided, and the processing device is located In the hosting CSE, the above embodiments and preferred embodiments are implemented, and the descriptions of the modules involved in the apparatus will be described below. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated. 2 is a structural block diagram of a processing apparatus for a multiparty session according to an embodiment of the present invention. As shown in Figure 2, the device comprises:

a create/update module 20 for creating/updating a session resource and a subscription resource on the hosting CSE, wherein the session resource is used to describe the session information of the multiparty session of the hosting CSE or the multiparty session of the AE registered on the hosting CSE , the subscription resource is used to subscribe to a session join or a session invitation;

Optionally, the device further includes: a receiving module 22, configured to receive a request and a message sent by a session requester or a session inviter; and a sending module 24, configured to send a session invitation or a join request and a message, and trigger the Subscription notifications are sent to the corresponding session subscribers.

When the session management/creation entity and the entity invited to join the session are AEs, the subscription resources are created in advance in the hosting CSE of the session management/creation entity and the hosting CSE of the entity invited or requesting to join the session, when the receiving module 22 Upon receiving the request and message sent by the session requester or the session inviter, and triggering the subscription condition, the creation/update module 20 sends the subscription notification to the subscribing entity through the sending module 24, notifying that the entity invites the subscribing entity to join or has an entity requesting to join. In one of the sessions; when the invited entity receives the subscription notification message and agrees to join the session, it sends a message to its hosting CSE, indicating that the invited entity agrees to join the session; when the session creation/management entity receives the subscription After the notification message, the requesting entity is added to a session that already exists, the session resource corresponding to the session created in the hosting CSE is updated, and the consent joining message is returned to the requesting entity by the sending module;

When the session management/creation entity and the entity invited or requested to join the session are CSE, there is no need to create a subscription resource. When the receiving module 22 receives the request and message sent by the session requester or the session inviter, the creation/update module 20 may Create/update session resources as needed; when the invited entity agrees to join the session, the hosted CSE creation/update module of the invited entity creates a session resource under the resources of the invited entity; when requesting to join the session management/creation entity session The session management/creation entity's hosting CSE creation/update module updates the session resource of the session and notifies the request to join the entity, requesting to join the entity's hosting CSE creation/update module in the request to join the real Create a session resource under the body resource;

In the embodiment of the present invention, the return message includes one of the following: the code that agrees to join, the basic information of the session resource in the hosting CSE where the session creation/management entity is located; the hosting CSE of the requesting entity receives the returned message through the receiving module, and creates / The update module creates a corresponding session resource on the hosting CSE; a member entity in the session sends a message to other member entities, and the session module creates a message resource (also called a message sub-resource) under the session resource corresponding to the message. Describe some basic information of the message, and then send the message to the hosting CSE where the member entity is located through the sending module of the hosting CSE; after the receiving CSE of the receiving member receives the message through the receiving module, the session module analyzes the corresponding message. That session, and will send the message to the real receiving member entity through the sending module in the form of notification;

Through the combined action of the above various steps, through the multi-party session of the hosting CSE or the resources required for the multi-party session of the AE registered on the hosting CSE, the related art is solved in the IoT system, for the multi-hop session The problem that the interaction process does not support, provides a solution to support multi-party sessions, and extends the application scenario of the Internet of Things system.

In order to better understand the above technical solutions, the following technical solutions are described below in conjunction with the preferred embodiments:

It should be noted that the system architecture in the embodiment of the present invention is based on the resource-oriented architecture of the Internet of Things, that is, all entities in the system are regarded as resources, such as application entities, functional entities, data entities, etc., by operating resources. Implement session management between multiple entities.

The embodiment of the present invention provides a resource-based IoT session method, which enables a message to join a session or invite to join a session, and is transmitted to a management/creator of the session or an invitee of the session to establish a session by creating/updating a session resource. The main steps of the method flow are as follows:

Pre-set conditions, when the entity that is invited to join the session, the session management/creation entity is AE, the subscription resource needs to be created in the hosting CSE of the entity that is invited to join the session, the session management/creation entity, and the message for establishing the session is subscribed;

Step 1: The session management/creation entity sends a message to an entity to invite it to join the session, that is, request to create a session resource under the resource of the entity in the hosting CSE that is invited to join the session entity; Or the entity requesting to join the session sends a request to join the session management/create entity management/created session, that is, requesting to update the session resource corresponding to the session in the hosting CSE of the session management/creation entity;

Step 2: When the entity that is invited to join the session or the session management/creation entity has a resource for the subscription session in the hosting CSE, the request or message for establishing the session is sent to the entity or the session management/creation entity invited to join the session, and the acquisition is obtained. The entity or session management/creation entity that invites to join the session agrees to establish a session; when the entity invited to join the session or the session management/creation entity is the hosting CSE, it is decided directly in the hosting CSE whether to establish or join the session;

Step 3: The entity or the session management/creation entity that is invited to join the session, the hosting CSE confirms that the session is established or joined, and the session resource is created or updated under the entity or the session management/creation entity resource in the hosting CSE; When an entity requests to join the session, a corresponding session resource in the session management/creation entity hosting CSE that requests to join the session is created under the entity resource in the hosting CSE of the requesting entity.

FIG. 5 is a structural diagram of a multi-party session resource and its sub-resources according to an embodiment of the present invention. As shown in FIG. 5, the resource is located in a hosting CSE, which is a CSE registered by a session entity (AE), or a session entity (CSE). In itself, when an entity is invited or requests to join a multiparty session, a session resource is created under the session entity's resource (<AE> or <CSEbase>) to describe the entire process from session establishment to session end. As shown in Table 1 below, the attributes of the session resource contain at least one of the following:

Table I

In the session, the session participant performs one or more message interactions, and needs to manage each interaction under the session. In the session resource, a new sub-resource message needs to be created to describe the current message during the session. , various information about historical news. As shown in Table 2 below, the attributes of the message resource contain at least one of the following:

Table II

In this embodiment, the multi-party session management/creation entity may be an AE or a CSE. When it is an AE, the hosted CSE that needs to register it transmits the message to the AE.

FIG. 6 is a schematic flowchart of inviting a multi-party session according to an embodiment of the present invention. In this example, the invited entity is an AE. As shown in the figure, the process includes the following steps:

Step S602, a multi-party session management/creation entity invites one or more entities to join the managed/created session, and sends a session invitation message to the hosting CSE of the invited entity, requesting the invited entity in the hosting CSE. Creating a session resource of the multiparty session;

The invited entity of this example is AE, the hostingCSE of the activated entity is the CSE registered by the invited entity; if the invited entity is CSE, the hostingCSE is the invited entity itself.

Step S604: After receiving the message, the hosting CSE triggers the invited entity to create a subscription condition in the subscription resource created on the hosting CSE, and sends a subscription notification to the session to be sent to the subscription. Reading entity, the invited entity;

If the hostingCSE is the invited entity itself, the invited entity does not need to trigger the subscription condition of the hostingCSE, and the invited entity directly obtains the invitation message.

The subscription notification includes a session ID, optionally, basic information of the session, including a session type, a session state, and the like, and the invited entity determines whether to join the session according to the analysis;

Step S606, the invited entity receives the notification, and learns that an entity invites it to join a certain multiparty session;

Step S608, when the invited entity agrees to join the session, sending a message to the hosting CSE to join the session;

Step S610, after the hosting CSE creates the session resource successfully, the replying session inviter is invited to join the session.

When the hosting CSE creates a session resource, the session ID is set to the session ID it receives, and the resource attributes are set according to some basic information of the session sent by the session inviter to the session inviter, including the creator of the session and the participation of the session. , the message format of the session, and so on.

Step S612, the session inviter (ie, the session management/creation entity) requests its hostingCSE to update the session resource of the multiparty session.

When the session inviter is the CSE, the hosting CSE is itself. At this time, the session inviter directly updates the session resource of the multi-party session, as shown in step S612' in the figure.

FIG. 7 is a schematic diagram of a process of actively joining a multi-party session according to an embodiment of the present invention. This example takes the case where the session management/creation entity is an AE. As shown in the figure, the process includes the following steps:

Step S702, the requesting joining entity, after obtaining the information of the multi-party session in advance, decides to join the multi-party session, that is, sending a message requesting to join the session to the hosting CSE of the session management/creation entity, specifically, requesting to update the hosting CSE. A session resource of a multiparty session, with a session ID in the message, optionally with information requesting to join the entity;

The session management/creation entity of this example is AE, which is the CSE registered by the session management/creation entity; if the session management/creation entity is CSE, the hostingCSE is the session management/creation entity itself.

Step S704, after receiving the message, the hosting CSE of the session management/creation entity triggers the subscription condition in the subscription resource created by the session management/creation entity on the hosting CSE, and sends the subscription notification message to the subscription entity, that is, the session management/creation entity;

If the hostingCSE is the management/creation entity itself, the management/creation entity does not need to trigger the subscription condition of the hostingCSE, and the management/creation entity directly knows the request to join the message;

In the subscription notification message of this step, optionally, some information about the multiparty session includes the creator of the session, the participant of the session, the message format of the session, and the like.

Step S706, the session management/creation entity receives the subscription notification message, and learns that an entity wants to join a multi-party session managed/created by the entity. When the consent entity joins the session, it sends a consent requester to join the session to the hosting CSE. a message to update a session resource of the multiparty session created in its hosting CSE;

Step S708, the hosting CSE of the session management/creation entity updates the session resource corresponding to the session ID, and sends a message to the joining entity to notify that it has been agreed to join the session;

Step S710, requesting the joining entity to request to create a corresponding session resource in its hosting CSE;

Step S712, the hosting CSE of the requesting entity receives the request to join the entity, and creates the session resource of the multi-party session for the requesting entity, that is, creates the session resource under the resource corresponding to the requesting entity, where The session ID of the newly created session resource is the same as the session ID of the session resource in the hosting CSE of the session management/creation entity. Some attributes need to be corresponding.

If the requesting join entity is a CSE and its hostingCSE is itself, then the session resource is created under the resource corresponding to the CSE.

FIG. 8 is a schematic flowchart of message sending and receiving in a multi-party session according to an embodiment of the present invention. As shown in FIG. 8, the process includes the following steps:

It should be noted that the process is based on the above process, the multi-party session has been created, and the message interaction is performed under the created session.

Step S802: The session creation/management entity sends a message to a member of the multi-party session, and sends the message to the hosting CSE of the session member, where the message carries the session ID, the message ID, and the session participating entity. Etc. At the same time, a message sub-resource is created in the session resource of the session in the hosting CSE of the session creation/management entity, and the specific content of the message is stored;

The hosting CSE may be a CSE registered by a session member entity, or may be a session member entity itself;

Step S804, the hosting CSE of the session member entity receives the message, finds the session resource created by the session member entity in the hosting CSE according to the session ID in the message, determines that the message sender has the right to send a message under the session, and determines the message receiving. The person is the creator corresponding to the session resource;

In step S806, the hosting CSE notifies the session member entity in the form of a notification, or informs the session member entity that there is a session message; if the hosting CSE is the session member entity itself, the session member entity directly obtains the session message sent by the session creation/management entity;

Step S808, the session member entity obtains the session message, analyzes the content of the message to respond, and returns to the hosting CSE where it is located;

Step S810, the hosting CSE returns the return message of the session member entity to the hosting CSE where the session creation/management entity is located, and can perform message aggregation and the like according to the session configuration.

Step S812, the hosting CSE where the creation/management entity is located sends the received message to the creation/management entity in the form of a notification.

The session continues to be maintained, and the creation/management entity can continue to perform message interaction with other session participating members under the session, that is, repeat the above steps, and until the session ends, delete all sessions corresponding to the session created by the session entity in its own hosting CSE. Session resource.

In summary, the embodiments of the present invention solve the problem that the interaction process between multi-hop sessions is not supported in the related art Internet of Things system, and provides a solution for supporting multi-party sessions, and expands the application of the Internet of Things system. Scenes.

In yet another embodiment of the present invention, the following method of processing a multiparty session is provided.

A multi-party session processing method for establishing a multi-party session between entities by creating and/or updating session resources of a multi-party session.

Optionally, establishing a multiparty between entities by creating and/or updating session resources of a multiparty session Words, including:

Wherein, when the invited entity is an application entity AE:

Creating the session resource of the multi-party session for the invited entity in the hosted CSE of the invited entity may include: the invited entity sending a consent to join the multi-party session to a hosted CSE of the invited entity a message, the session resource of the multiparty session is created for the invited entity by the hosted CSE of the invited entity.

Wherein, the session management/creation entity itself is the managed CSE of the session management/creation entity:

Updating a session resource of the multiparty session in the managed CSE of the session management/creation entity, The method includes: the session management/creation entity updates a session resource of the multiparty session; and thereafter, the session management/creation entity further returns a message to the request joining entity to agree to join the multiparty session.

Wherein, when the session management/creation entity is AE:

The attribute information of the session resource includes at least one of the following information: a session message, a session identifier, a session topic, a session creator, a session participant, a session entity state, and a maximum number;

In the following embodiments of the present invention, a processing apparatus for a multiparty session is provided.

a subscription processing module, configured to: after receiving a request sent by the session management/creation entity to create the session resource of the multi-party session for the invited entity, send a subscription notification to the invited entity to invite the join party to join the multi-party session; And receiving the invited entity to agree to join the multiparty After the message, reply to the session management/creation entity that the invited entity agrees to join the multi-party session, the invited entity is an AE;

Requesting a reply module, configured to: if the request is made to join the entity to join the multi-party session, Sending a message to the hosted CSE of the session management/creation entity agreeing to the request to join the entity to join the multiparty session.

In another embodiment, software is also provided for performing the technical solutions described in the above embodiments and preferred embodiments.

In another embodiment, a storage medium is further provided, wherein the software includes the above-mentioned software, including but not limited to: an optical disk, a floppy disk, a hard disk, an erasable memory, and the like.

It should be noted that the terms "comprising" and "having" and any variants thereof are intended to cover a non-exclusive inclusion, for example, a process, method, system, product, or device that comprises a series of steps or units is not necessarily limited Those steps or units listed are included, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

One of ordinary skill in the art will appreciate that all or a portion of the steps of the above-described embodiments can be implemented using a computer program flow, which can be stored in a computer readable storage medium, such as on a corresponding hardware platform (eg, The system, device, device, device, etc. are executed, and when executed, include one or a combination of the steps of the method embodiments.

Alternatively, all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.

The devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.

When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium. The above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

Industrial applicability

The subscription resource is created on the hosting general service entity CSE by using the solution of the embodiment of the present invention, wherein the subscription resource is used to subscribe to the multi-party session of the hosting CSE or the multi-party session of the application entity AE registered on the hosting CSE. A solution that supports multi-party sessions and extends the application scenarios of the Internet of Things system.

Claims

A method for processing a multiparty session, comprising:

A multiparty session between entities is established by creating and/or updating session resources for a multiparty session.
The method of claim 1 wherein:

Establish multi-party sessions between entities by creating and/or updating session resources for multi-party sessions, including:

The session management/creation entity requests the hosted general service entity CSE of the invited entity to create a session resource of the multiparty session for the invited entity;

After the session management/creation entity receives the message that the invited entity of the hosted CSE reply of the invited entity agrees to join the multi-party session, updating the created in the managed CSE of the session management/creation entity Session resources for multiparty sessions.
The method of claim 1 wherein:

Establish multi-party sessions between entities by creating and/or updating session resources for multi-party sessions, including:

The invited entity is informed that it is invited to join the multi-party session and agrees to join the multi-party conference;

A session resource of the multiparty session is created for the invited entity in a hosted CSE of the invited entity.
The method of claim 3 wherein:

The invited entity itself is the hosted CSE of the invited entity;

The invited entity is informed that the invitation to join the multi-party session includes: receiving a request sent by the session management/creation entity to create the session resource of the multi-party session for the invited entity;

Creating the session resource of the multi-party session for the invited entity in the managed CSE of the invited entity, including: the invited entity creating a session resource of the multi-party session under the resource of the invited entity; Thereafter, the invited entity also replies to the session management/creation entity with a message agreeing to join the multiparty session.
The method of claim 3 wherein:

The invited entity is an application entity AE;

The invited entity is informed that the invited party joins the multi-party session, and includes: receiving a subscription notification sent by the hosted CSE of the invited entity to join the multi-party session;

Creating a session resource of the multiparty session for the invited entity in the hosted CSE of the invited entity, comprising: the invited entity sending a message agreeing to join the multiparty session to a hosted CSE of the invited entity Creating a session resource of the multiparty session for the invited entity by the managed CSE of the invited entity.
The method of claim 1 wherein:

Establish multi-party sessions between entities by creating and/or updating session resources for multi-party sessions, including:

The hosted CSE of the invited entity receives a request sent by the session management/creation entity to create the session resource of the multi-party session for the invited entity, and sends a notification of the subscription to the invited entity to join the multi-party session. The invited entity is an AE;

After the hosted CSE of the invited entity receives the message that the invited entity agrees to join the multi-party session, the session resource of the multi-party session is created under the resource corresponding to the invited entity, and is managed to the session. / Create an entity replies to the message that the invited entity agrees to join the multiparty session.
The method of claim 6 wherein:

After the hosted CSE of the invited entity receives the request sent by the session management/creation entity to create the session resource of the multi-party session for the invited entity, first search for the subscription resource created by the invited entity, such as And sending the subscription notification; wherein the subscription resource is used to subscribe to an invitation of the multi-party session.
The method of claim 1 wherein:

Establish multi-party sessions between entities by creating and/or updating session resources for multi-party sessions, including:

The managed CSE requesting to join the entity requesting session management/creation entity updates the session resources of the multiparty session to join the multiparty session;

After the request joining entity receives the message of the host CSE reply of the session management/creation entity agreeing to join the multi-party session, creating the multi-party session for the request joining entity in the managed CSE of the request joining entity Session resources.
The method of claim 1 wherein:

Establish multi-party sessions between entities by creating and/or updating session resources for multi-party sessions, including:

The session management/creation entity learns that the request to join the entity requests to join the multi-party session, and agrees that the request joins the entity to join the multi-party session;

Updating the session resources of the multiparty session in the managed CSE of the session management/creation entity.
The method of claim 9 wherein:

The session management/creation entity itself is the managed CSE of the session management/creation entity;

The session management/creation entity learns that the requesting to join the entity to request to join the multi-party session includes: receiving a request sent by the request joining entity to update the session resource of the multi-party session;

Updating a session resource of the multiparty session in the managed CSE of the session management/creation entity, comprising: the session management/creation entity updating a session resource of the multiparty session; afterwards, the session management/creation entity is further The requesting to join the entity replies to the message agreeing to join the multiparty session.
The method of claim 9 wherein:

The session management/creation entity is an AE;

The session management/creation entity learns that the requesting to join the entity requests to join the multi-party session, including: receiving a request sent by the hosted CSE of the session management/creation entity to join the entity to request to join the subscription notification of the multi-party session;

Updating the session resource of the multiparty session in the managed CSE of the session management/creation entity, comprising: the session management/creation entity transmitting to the hosted CSE of the session management/creation entity agreeing to the request to join an entity to join the The message of the multiparty session, the session resource of the multiparty session is updated by the managed CSE of the session management/creation entity.
The method of claim 1 wherein:

Establish multi-party sessions between entities by creating and/or updating session resources for multi-party sessions, including:

After receiving the request to join the entity to update the session resource of the multi-party session, the managed CSE of the session management/creation entity sends a request notification to the session management/creation entity requesting to join the multi-party session, The session management/creation entity is AE;

The managed CSE of the session management/creation entity receives the request that the session management/creation entity agrees to the request to join the entity to join the multi-party session, updates the request for the session resource of the multi-party session, and sends the request to the request The joining entity replies to the message that it joins the multiparty session.
The method of claim 12 wherein:

After receiving the request for the entity to update the session resource of the multi-party session, the hosted CSE of the session management/creation entity first searches for the subscription resource created by the session management/creation entity; if found, sends the subscription again. a notification; wherein the subscription resource is used to subscribe to a request for an entity to join a multiparty session.
A method as claimed in any one of claims 1 to 13 wherein:

The session resources of the multiparty session include attribute information and/or message sub-resources;

The attribute information of the session resource includes at least one of the following information: a session message, a session identifier, a session topic, a session creator, a session participant, a session entity state, and a maximum number;

The message sub-resource is used to describe a message transmitted during a multi-party session, and includes at least one of the following information: a message identifier, a message status, a message format, a message sender, a message receiver, and a message sending time.
A processing device for a multi-party session is applied to a general service entity CSE or an application entity AE as a session management/creation entity, the processing device comprising:

a session invitation module, configured to: request a hosted CSE of the invited entity to create a session resource of the multiparty session for the invited entity;

a resource update module, configured to: after receiving the message that the invited entity of the hosted CSE reply of the invited entity agrees to join the multi-party session, update the created in the managed CSE of the session management/creation entity Session resources for multiparty sessions.
A multi-party session processing device is applied to a CSE as an invited entity, and the processing device includes:

An invitation processing module, configured to: after receiving a request sent by the session management/creation entity to create the session resource of the multi-party session for the invited entity, if agreeing to join the multi-party conference, to the The session management/creation entity replies to the message agreeing to join the multiparty session;

The resource creation module is configured to: create a session resource of the multi-party session under the resource of the invited entity, if it is agreed to join the multi-party conference.
A multi-party session processing device is applied to an AE as an invited entity, and the processing device includes:

An invitation receiving module, configured to: receive a subscription notification sent by the hosted CSE of the invited entity to join the multi-party session;

The invitation reply module is configured to: send a message agreeing to join the multiparty session to the hosted CSE of the invited entity when agreeing to join the multiparty conference.
A multi-party session processing device is applied to an entity hosting a CSE as an invited entity, the processing device comprising:

a subscription processing module, configured to: after receiving a request sent by the session management/creation entity to create the session resource of the multi-party session for the invited entity, send a subscription notification to the invited entity to invite the join party to join the multi-party session; And after receiving the message that the invited entity agrees to join the multi-party session, replying to the session management/creation entity, the message that the invited entity agrees to join the multi-party session, where the invited entity is an AE;

The resource creation module is configured to: after receiving the message that the invited entity agrees to join the multi-party session, create a session resource of the multi-party session under the resource corresponding to the invited entity.
A processing apparatus according to claim 18, wherein:

After receiving the request for the session entity to create the session resource of the multi-party session, the subscription processing module first searches for the subscription resource created by the invited entity, if found, and then sends the request. The subscription notification; wherein the subscription resource is used to subscribe to an invitation of a multiparty session.
A multi-party session processing device is applied to a CSE or an AE as a request to join an entity, and the processing device includes:

Join the request module, set to: request session management / create entity's managed CSE update as stated a session resource of a party session to join the multiparty session;

a resource creation module, configured to: after receiving the message that the host CSE reply of the session management/creation entity agrees to join the multi-party session, create the content for the request joining entity in the managed CSE of the request joining entity Session resources for multiparty sessions.
A multi-party session processing device is applied to a CSE as a session management/creation entity, the processing device comprising:

a request processing module, configured to: after receiving the request for adding the session resource of the multi-party session sent by the request joining entity, if the requesting to join the entity joins the multi-party session, agreeing to join the requesting entity The message of the multiparty session;

And a resource update module, configured to: if the request to join the entity joins the multiparty session, update the session resource of the multiparty session.
A multi-party session processing device is applied to an AE as a session management/creation entity, the processing device comprising:

a request receiving module, configured to: receive a request sent by the hosted CSE of the session management/creation entity to join a subscription request to join the multi-party session;

The request reply module is configured to: send a message agreeing to the requesting joining entity to join the multiparty session to the managed CSE of the session management/creation entity if the requesting join entity joins the multiparty session.
A processing device for a multi-party session, which is applied to an entity hosting a CSE as a session management/creation entity, the processing device comprising:

a subscription processing module, configured to: after receiving a request to join the entity to update the session resource of the multi-party session, send, to the session management/creation entity, the subscription notification that the request join entity requests to join the multi-party session; and After receiving the message that the session management/creation entity agrees to join the entity to join the multi-party session, the message is sent to the requesting entity to agree to join the multi-party session; the session management/creation entity is AE

The resource update module is configured to: after receiving the message that the session management/creation entity agrees to join the entity to join the multi-party session, update the request for the session resource of the multi-party session.
A processing apparatus according to claim 23, wherein:

After receiving the request for the entity to update the session resource of the multi-party session, the subscription processing module first searches for the subscription resource created by the session management/creation entity; if found, sends the subscription notification; The subscription resource is used to subscribe to a request for an entity to join a multiparty session.