WO2023082244A1

WO2023082244A1 - Group affiliation method and corresponding device

Info

Publication number: WO2023082244A1
Application number: PCT/CN2021/130622
Authority: WO
Inventors: 王雄集; 杨河山
Original assignee: 海能达通信股份有限公司
Priority date: 2021-11-15
Filing date: 2021-11-15
Publication date: 2023-05-19

Abstract

The present application provides a group affiliation method and a corresponding device. After a target group requested by a client to affiliate is determined, in order to avoid forming a longer affiliation request message and increasing the packet loss probability and the time delay of transmission of the affiliation request message in a wireless environment due to the fact that group information of each target group is directly utilized, in the present application a target affiliation identifier met by the target group is obtained, that is, the group information of each target group is replaced with a very short identifier which is pre-configured and indicates that the client is affiliated to all groups or some groups, and an affiliation request message for the target group is generated, so that the length of the affiliation request message is greatly shortened. In this way, the affiliation request message is sent to a server for an affiliation operation in the wireless environment, and the packet loss probability and the time delay of transmission of the affiliation request message are reduced, thereby improving the transmission reliability and efficiency of the affiliation request message.

Description

Group Attachment Method and Corresponding Equipment

technical field

This application mainly relates to the field of MCS clusters, and more specifically relates to a group attachment method and corresponding equipment.

Background technique

In the current MCS (Mission Critical Service, mission-critical server) wide cluster communication application, the MCS standard defines the group attachment standard, that is, the group attachment Affiliation standard. Specifically, the MCS can control the MCC through the group attachment Affiliation standard. (Mission Critical Client) After joining the group, the MCC attached to the group can initiate or receive the group business.

Among them, in the above-mentioned group attach procedure, MCC usually needs to generate an attach request message containing information of all groups that the user is interested in, and send the attach request message to the MCS to perform the attach operation. The attach result message of the group information is fed back to the MCC.

It can be seen that when there are many groups that the user needs to attach to, according to the group attachment method described above, the above-mentioned attachment information exchanged between the MCC and the MCS will be too long, which will easily cause packet loss in transmission and increase the delay. , which reduces the efficiency and reliability of attachment information transmission.

Contents of the invention

In view of this, the application provides the following technical solutions:

In one aspect, the present application proposes a group attachment method, the method comprising:

Determine the target group to which the client requests to attach;

Acquiring the target attachment ID satisfied by the target group; the target attachment ID is used to indicate that the client is attached to all of the multiple groups that currently exist, or that the client is attached to the multiple groups part of a group;

generating an attach request message for the target group by using the target attach identifier; the attach request message at least includes the target attach identifier;

sending the attach request message to the server, so that the server responds to the attach request message and controls the client to perform an attach operation on the target group.

Optionally, the acquiring the target attachment identifiers satisfied by the target group includes:

According to the target relationship between the target group and multiple currently existing groups, select a target attachment ID that matches the target relationship from multiple types of pre-configured attachment IDs;

Wherein, the target relationship is the first relationship that the target group is all of the multiple groups, or the target group is the second relationship of some of the multiple groups. relationship, and the second relationship includes a combination of one or more partial groups.

Optionally, the determining the target group for which the client requests to attach, and obtaining the target attachment identifier satisfied by the target group includes:

In response to a group attach selection operation on a plurality of currently existing groups, determine a target group to which the selected client requests to attach;

In response to the selection operation on the output multiple attachment identifiers, the selected attachment identifier is determined as the target attachment identifier.

Optionally, the method also includes:

According to the uniform resource identifier format stipulated in the group attachment protocol, configure the first attachment identifier used to indicate that the client is attached to all of the multiple groups that currently exist;

According to the uniform resource identifier format, configure a second attachment identifier used to indicate that the client is attached to some of the multiple groups.

Optionally, if the target attachment identifier includes part of the multiple groups that are used to indicate that the client is attached to currently existing groups, generating an attachment for the target group by using the target group attachment identifier request message, including:

Obtaining respective target group identifiers of the target groups;

Construct an attach request message for the target group according to the format of the attach request message and according to the identifier of the target group.

In yet another aspect, the present application also proposes a group attachment method, the method comprising:

Receiving an attach request message for a target group sent by a client; wherein, the target group is at least one of a plurality of currently existing groups; the attach request message uses the target group to satisfy generated by the target attachment ID, at least including the target attachment ID; the target attachment ID is used to indicate that the client is attached to all of the multiple groups that currently exist, or that the client is attached to the multiple groups part of a group;

In response to the attach request message, control the client to perform an attach operation on the target group according to the target attach identifier.

Optionally, the responding to the attach request message, and controlling the client to perform an attach operation on the target group according to the target attach identifier, includes:

Parsing the attach request message to obtain the target attach identifier;

Determine the target group to which the client requests to attach according to the target attachment identifier;

controlling the client to perform an attach operation on the target group.

Optionally, the method also includes:

Constructing an attach notification message for the client attachment group according to the attachment notification message format and according to the target attachment identifier;

Feedback the attachment notification message to the client.

In yet another aspect, the present application also proposes a group attachment device, the device comprising:

A target group determination module, configured to determine the target group to which the client requests to attach;

A target attachment identification acquisition module, configured to acquire a target attachment identification satisfied by the target group; the target attachment identification includes all groups used to indicate that the client is currently attached to a plurality of groups, or the The client is attached to some groups in the plurality of groups;

An attach request message generating module, configured to generate an attach request message for the target group by using the target attach identifier; the attach request message at least includes the target attach identifier;

An attach request message sending module, configured to send the attach request message to a server, so that the server responds to the attach request message and controls the client to perform an attach operation on the target group.

An attach request message receiving module, configured to receive an attach request message for a target group sent by a client; wherein, the target group is at least one group among multiple groups that currently exist; the attach request message is generated by using the target attachment identifier satisfied by the target group, and at least includes the target attachment identifier; the target attachment identifier includes all the groups used to indicate that the client is attached to a plurality of groups that currently exist, or the client is attached to some of the multiple groups;

An attach operation module, configured to control the client to perform an attach operation on the target group according to the target attach identifier in response to the attach request message.

In yet another aspect, the present application also proposes a storage medium on which a computer program is stored, and the computer program is invoked and executed by a processor to implement the above-mentioned group attachment method.

In yet another aspect, the present application also proposes a group attachment system, the system includes at least one terminal and a server, wherein:

The terminal includes at least one first memory and at least one first processor;

The first memory is configured to store a first program implementing the above-mentioned group attachment method on the client side;

The first processor is configured to load and execute the first program stored in the first memory, so as to implement the above-mentioned group attachment method on the client side;

The server includes at least one second memory and at least one second processor;

The second memory is configured to store a second program implementing the above-mentioned group attachment method on the server side;

The second processor is configured to load and execute the second program stored in the second memory, so as to implement the above-mentioned group attachment method on the server side.

It can be seen that the present application provides a group attachment method and corresponding equipment. After determining the target group that the client requests to attach, in order to avoid directly using the group information of each target group, a longer attachment request message is formed. , to increase the packet loss probability and time delay of the attach request message transmission in the wireless environment, this application proposes to obtain the target attach ID that the target group satisfies, that is, the pre-configured very Short identification, to replace the group information of each target group, generate an attach request message for the target group, greatly shorten the length of the attach request message, so that it is sent to the server for attach operation in a wireless environment, The probability of packet loss and time delay in the transmission of the attach request message are reduced, thereby improving the reliability and efficiency of the transmission of the attach request message.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only It is an embodiment of the present invention, and those skilled in the art can also obtain other drawings according to the provided drawings without creative work.

FIG. 1 is a schematic flow diagram of an optional example of a group attachment method applicable to a client proposed in this application;

Figure 2a is an optional example of an attach request message based on the full amount of group information attached by the client in the existing group attach method;

FIG. 2b is an optional example of an attachment request message for the client to attach all groups in the group attachment method applicable to the client proposed by the present application;

FIG. 2c is another optional example of an attach request message based on the full amount of group information attached by the client in the existing group attach method;

FIG. 2d is an optional example of an attach request message for a client to attach a partial group in the group attach method applicable to a client proposed in this application;

FIG. 3 is a schematic flowchart of another optional example of a group attachment method suitable for a client proposed in this application;

FIG. 4 is a schematic flow diagram of an optional example of a group attachment method applicable to a server proposed by the present application;

FIG. 5a is an optional example of an attachment notification message for a client to attach all groups in an existing group attachment method;

FIG. 5b is an optional example of the attachment notification message for the client to attach all groups in the group attachment method applicable to the server proposed by the present application;

FIG. 5c is an optional example of an attachment notification message for a client to attach a part of the group in the group attachment method applicable to the server proposed by the present application;

FIG. 6 is a schematic structural diagram of an optional example of a group attachment device suitable for a client proposed in this application;

FIG. 7 is a schematic structural diagram of an optional example of a group attachment device applicable to a server proposed in this application;

FIG. 8 is a schematic diagram of a hardware structure of an optional example of a group attachment system applicable to the group attachment method and device proposed in this application;

Fig. 9 is a schematic diagram of a hardware structure of another optional example of a terminal applicable to the group attachment method and apparatus proposed in this application.

Detailed ways

Aiming at the technical problems described in the background technology, this application hopes to shorten the connection between the client (that is, the above-mentioned mission-critical client, Mission Critical Client, MCC for short) and the server (that is, the above-mentioned mission-critical client) on the basis of ensuring that the requirements of the client attachment group are met. The length of attachment information exchanged between critical servers (Mission Critical Service, referred to as MCS) to avoid easy loss of transmission data packets in a wireless environment and long delays, resulting in low efficiency and poor reliability of attachment information transmission technical problems.

Based on the above analysis, this application proposes to optimize the application/pidf+xml schema message in the attachment message interacted between MCC and MCS on the basis of following the MCS standard, that is, the message carrying the group information of all groups that the user is interested in , specifically proposed to configure the attachment identifier to replace these group messages, and at the same time enable the client or server receiving the message to know the group that the client wants to attach to or the group that has successfully attached based on the content of the attachment identifier , in this way, in the data interaction process of attach request message/attach notification message between the client and the server, it is not necessary to implement based on the full amount of application/pidf+xml schema messages, especially when the client needs to attach a large number of groups In this case, the processing method proposed by this application to replace the group information of all attachment groups with the attachment identifier greatly shortens the length of the attachment information transmitted between the client and the server, and reduces the packet loss probability of data transmission in the wireless environment. , which reduces the delay, thereby improving the efficiency and reliability of data transmission.

Wherein, the above-mentioned application/pidf+xml schema message is a group attachment standard defined in accordance with the MCS standard, that is, the group attachment Affiliation standard, and the message format (or protocol) requirements for data interaction between the MCC and the MCS are determined, and this application applies to it The specific content is not limited, depending on the situation.

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative work all belong to the protection scope of the present invention.

Referring to FIG. 1, it is a schematic flowchart of an optional example of the group attachment method proposed in this application. This method can be applied to terminals, such as electronic devices that support human-computer interaction functions. Specifically, it can be performed by a client in the electronic device, namely MCC (Mission Critical Client) implements the group attachment method described in this embodiment. This application does not limit the product type of electronic equipment and the application type of MCC, depending on the situation. For the convenience of description, in this application, the mission-critical client is referred to as the client, and the mission-critical server MCS is referred to as the server, and the following embodiments will not be described one by one. As shown in Figure 1, the group attachment method described from the MCC side may include:

Step S11, determining the target group to which the client requests to attach;

In practical applications, in the scenario where the user selects a group of interest to attach to meet the business access requirements of the attached group, the user can start the client in the electronic device and output the group attachment page, the group The attachment page can usually display multiple groups that currently exist, such as all groups to which the user belongs, and the attachment status of each group. After that, the user can select one or more interested groups to attach to. In the embodiment of the application, the group selected by the user is recorded as the target group.

It can be seen that the above-mentioned target group may be one or more groups that the user is interested in, and based on the selection method of the target group described above, step S11 may specifically respond to the group selection of multiple groups that currently exist. The attach selection operation determines the target group to which the selected client requests to attach. However, it should be noted that the method for determining the target group includes but is not limited to the selection method described in this embodiment.

Step S12, obtaining the target attachment identifiers satisfied by the target group;

Combined with the relevant description of the technical concept of this application above, for the length of the obtained message, this application does not want to carry the group information of all groups that the user who logs in to the client is interested in (that is, requests to attach), so, for different group attachment situations , this application pre-configures the corresponding attachment identifier, such as the first attachment identifier used to indicate that the client is attached to all of the multiple groups that currently exist, denoted as Flag1; it is used to indicate that the client is attached to the currently existing multiple groups The second attachment identifier of some of the groups in the groups is denoted as Flag2 and so on. This application does not limit the specific content of Flaga1 and Flag2, such as numbers, characters, etc., depending on the situation.

Wherein, if the currently existing multiple groups refer to multiple groups to which the user belongs, that is, all groups joined by the user belong to a member of the group, then the above-mentioned first attachment flag Flag1 may indicate that the user The clients of the client must attach to all the groups they belong to. It should be understood that the group to which the user belongs does not mean that the user is currently interested in the services of the group. Therefore, the group to which the user belongs does not mean that the user's client is attached to the group. According to MCS Standard, there are usually users who belong to a certain group, but the user is temporarily not interested in the services of the group, and the user's client will not attach to the group, so it cannot initiate service access requests to the group, and cannot Accept the business information fed back by this group.

It can be seen that when the user is interested in all the groups to which the user belongs, that is, all the groups that the above-mentioned target group does not belong to the user's client, that is, all the groups among the multiple groups that currently exist, the obtained The target attachment identifier may be the above-mentioned first attachment identifier Flag1, and the specific acquisition method is not limited.

In practical applications, if the user is only interested in some of the multiple groups to which he belongs, he can choose to attach some of the groups. In order to indicate this situation, the application can also configure the above-mentioned second attachment flag Flag2, using To indicate that the user is interested in the belonging partial group, the user's client requests to attach the belonging partial group. In this case, in order to clarify the group that the user is interested in, that is, the group that the client requests to attach, the target group identifier of the target group, such as the group name, number and other unique identifiers, can usually be obtained. There is no restriction on the content of the group logo, and it depends on the situation.

It should be noted that when configuring the above-mentioned first attachment identifier Flag1 and second attachment identifier Flga2, it needs to be implemented in accordance with the uniform resource identifier (Uniform Resource Identifier, URI) format specified in the group attachment protocol, so that the first attachment identifier Flag1 and the second attachment identifier The second attachment flag Flga2 conforms to the format requirements, and can be used as the content of the attach request message/attach notification message to be exchanged between the MCC and the MCS. Wherein, the group attachment protocol may be the above-mentioned application/pidf+xml, and the format may be the xs:anyURI format specified in application/pidf+xm, and this application does not limit its content.

Based on the above analysis, in this embodiment of the application, the target attachment identifier obtained in step S12 can be used to indicate that the client is attached to all of the multiple groups that currently exist, or the client is attached to any of the multiple groups. A partial group, which may be determined according to the relationship between the determined target group and multiple existing groups. In addition, according to the functions of the above-described attachment identifiers in this application, this application can also configure other attachment identifiers representing other content according to actual needs, such as classifying multiple groups currently existing in a more fine-grained manner, for The attachment identification corresponding to the attachment configuration of different types of groups is no longer limited to the classification method of all/part of the group attachment. The specific classification method depends on the situation. The application methods for different attachment identifications are similar. This application does not make a a detailed description.

In some embodiments, in different scenarios, the group categories contained in these groups may be different. In order for the server to identify which part of the group the client needs to attach to, the category of some groups can also be refined , that is, one-to-one corresponding attachment identifiers can be configured for combinations of different partial groups. Of course, this application can also determine the group identifiers of the groups included in the part of the group to be attached when it is necessary to attach the part of the group after determining the attachment identifier of the unified partial group. This is not limited.

Step S13, using the target attachment identifier to generate an attachment request message for the target group;

As described above, the application obtains the target attachment identifier, which can directly indicate whether the user of the client is currently interested in all the groups or some of the groups to which he belongs. In this way, when the client initiates an attach request message for the target group, it can The obtained target attachment ID replaces the group information of all groups that the user is interested in, and informs the server of each group to be attached by the client. It can be seen that the attach request message may at least include the target attach ID. Due to the length of the target attach ID, the length of group information relative to all interested groups is very short. This method of message generation greatly shortens the The length of the attach request message reduces the probability of packet loss during the transmission of the group attach to the wireless network and the Internet, reduces the delay, and improves the transmission efficiency and reliability of the attach message.

Exemplarily, assuming that the user belongs to five groups A, B, C, D, and E, and the user is interested in all of these five groups, the user client requests to attach all the groups to which the user belongs. The first attachment identifier configured in the above manner may be sip:all-groups@mcs.group.com, compared to the group information carrying the five groups as shown in Figure 2a (the dotted frame area in Figure 2a content in the application/pidf+xml message, that is, the attachment request message, as shown in Figure 2b, this application directly replaces the application/pidf+xml message in the application/pidf+xml message by Flag1 (the content in the dotted box area in Figure 2b) Group messages for five groups.

By comparing the content of the attachment request message shown in Figure 2a and Figure 2b above, for the five groups in this example, according to the traditional attachment request method, as shown in Figure 2a, it is necessary to list the group information of each group that needs to be attached ; and in this application, the method of replacing the corresponding attachment identifier can replace the group information of all groups to be attached by one code, especially in the scenario where the number of groups to be attached by the client is large, this application This processing method greatly shortens the signaling length of the attach request message.

Similarly, if the user is interested in some of the above five groups, such as the user chooses two groups A and B to attach, the second attachment ID can be obtained in the above way to replace the groups that the client wants to attach to Group information (the contents of the dotted frame area in the attach request message as shown in Figure 2c), at this time, the second attach identifier can be sip:part-groups@mcs.group.com, which can indicate that the client wants to attach the user In this case, in order for the server to determine which part of the group the client is attached to, it usually carries the target group identifier of the target group in the attach request message, as shown in the dotted box area in Figure 2d , indicating that the client attaches part of the belonging group this time, and the numbers of this part of the belonging group are A and B, that is, groups numbers="A, B", that is, it can carry the respective group IDs of the part of the group attached this time . The methods for generating attach request messages of other partial groups are similar, and the present application does not describe them in detail here.

In some other embodiments, combined with the above analysis, this application can also pre-configure the corresponding second attachment identifier for the scenario of attaching different partial groups. In this case, the second attachment identifier can not only represent the desired attachment Partial groups can further indicate which one or more groups the partial groups are attached to this time. There is no need to configure additional group identifiers. The server can directly determine the client’s current request based on the second attachment identifier that characterizes the content. Which part of the group is attached, the implementation process is similar, and this application will not describe it in detail.

Based on the content of the attach request message described in the above example, it can be seen that the traditional attach request message is based on the full amount of data operations performed by application/pidf+xml, which leads to the redundant definition of the XML Schema interface field information of application/pidf+xml, namely The more groups the client needs to attach, especially if all groups need to be attached, the length of the application/pidf+xml information will be too long; and the attachment identification proposed in this application does not need to be attached The group information of each group to be attached is listed in the request message one by one, especially in the case of a large number of groups to be attached, the length of the attach request message is greatly shortened, and the reliability of the attach request message transmission is improved sex and efficiency.

Step S14, sending the attach request message to the server, so that the server responds to the attach request message and controls the client to perform an attach operation on the target group.

Combined with the above description of the attach request message, after the server receives the attach request message sent by the client, by parsing the attach request message, it can be determined from the target attachment identifier contained in it that the client requests to attach to all groups. It is also a part of the groups, and which part of the groups. In this way, the client can be controlled to perform an attach operation on these target groups. The specific implementation method of the attach operation will not be described in detail in this application.

To sum up, in the embodiment of this application, after determining the target group that the client requests to attach, in order to avoid directly using the group information of each target group to form a longer attach request message, add the attach request message For the packet loss probability and delay of transmission in a wireless environment, this application proposes to obtain the target attachment ID that the target group satisfies, that is, a pre-configured very short ID indicating that the client is attached to all or part of the group, instead of The group information of each target group generates an attach request message for the target group, which greatly shortens the length of the attach request message. In this way, it is sent to the server for attach operation in a wireless environment, reducing the transmission rate of the attach request message. Packet loss probability and delay, thereby improving the reliability and efficiency of attach request message transmission.

Referring to FIG. 3 , it is a schematic flowchart of another optional example of the group attachment method proposed in this application. This embodiment can be an optional detailed implementation method for the group attachment method described above, but it is not limited The detailed implementation method described in this embodiment. As shown in Figure 3, the method may include:

Step S31, in response to the group attach selection operation on the currently existing groups, determine the target group to which the selected client requests to attach;

As described in the corresponding part of the above embodiment, the user starts the client MCC and outputs the group attachment interface, and can select from among the multiple groups that currently exist on the group attachment interface, such as the multiple groups to which the user belongs. Interested target groups to request that the client attach to these target groups. However, it is not limited to this method of determining the target group.

Step S32, according to the target relationship between the target group and multiple existing groups, select a target attachment ID that matches the target relationship from multiple pre-configured attachment IDs;

In combination with the relevant description of the attachment identifier in the above embodiments, the target relationship in the embodiment of the present application may be the first relationship in which the target group is all of the multiple groups that currently exist, or the target group is the multiple The second relation of the partial groups in the group, and the second relation includes a combination of one or more partial groups, as the case may be. Based on this, if the target relationship is the second relationship, it means that the user is interested in the part of the group to which he belongs, and the pre-configured second attachment ID can be the target attachment ID; if the target relationship is the first relationship, it means that the user feels Interested in all the groups it belongs to, the pre-configured first attachment ID can be selected as the target attachment ID. It should be noted that the manner of determining the target attachment identifier is not limited to the implementation method described in this embodiment.

In some other embodiments, after the user selects the target group, the application can also jump to output the attachment identification selection interface, and display multiple pre-configured attachment identifications in the attachment identification selection interface, and can also target different Attachment ID, output whether the attached group indicated by it is all or part of the attached group, to prompt the user to select an appropriate attached ID as the target attached ID, in this case, the client can respond to multiple attached to the output The identification selection operation determines the selected attachment identification as the target attachment identification.

Of course, the present application can also select the target group of interest and its corresponding attachment ID at the same time in the group attachment interface, which is not limited to the method for selecting the target attachment ID described in some other embodiments above.

In step S33, according to the format of the attach request message, the target attach identifier is used to replace the group information of the target group to form an attach request message for the target group;

In practical applications, according to the group attachment Affiliation standard defined by the MCS standard, the attachment request message sent by the client MCC to the server MCS must follow the corresponding protocol format requirements, which are recorded as the attachment request message format, as shown in Figure 2a to Figure 2d above The format of the attachment request message shown in the figure, so after the client determines the target group that the user is interested in and the target attachment ID that it satisfies, it can generate an attachment request message for the target group according to this format, as shown in the above figure The content in the dotted box in 2b may be replaced by the group information of the target group by the target group identifier to form an attach request message with a small length.

It should be noted that the above-mentioned target attachment ID is the second attachment ID, that is, the user is interested in some belonging groups, and in order to know which part of the belonging group he is interested in, the respective target group IDs of the target groups can be obtained, such as Group name, serial number, etc. Afterwards, as shown in Figure 2d above, the group information of the target group can be replaced by the target group identifier and the target attachment identifier according to the attach request message format to form an attach request for the target group The specific generation process of the message will not be described in detail in this application.

In addition, the content and message format of the attachment request message generated by this application, including but not limited to the content shown in Figure 2b and Figure 2d above, can be determined according to actual protocol requirements and business needs, and this application will not describe them in detail .

Step S34, sending the attach request message to the server, so that the server responds to the attach request message and controls the client to perform an attach operation on the target group.

In practical applications, the server will allow the client to initiate service access to the attached target group after controlling the client to attach the target group according to the target attachment identifier contained in the attach request message, and receive the target group feedback from the server. As for the service information of the group, this application does not describe in detail the implementation process of the client's service access to the attached group.

To sum up, after the user selects the target group of interest from the multiple groups to which he belongs, he can base the target relationship between the target group and the multiple groups, such as the target group being one of the multiple groups Part of the group or all groups, select the target attachment ID related to the target from the pre-configured multiple attachment IDs to indicate that the client attaches part of the group or all of the groups, and then, according to the attachment request message Format, the target attachment identifier replaces the group messages of each target group, generates an attachment request message and sends it to the server, avoids packet loss and time delay caused by too long attachment request message, and improves data transmission efficiency and reliability.

The implementation process of the group attachment method proposed in this application will be described below from the perspective of the MCS. Since the group attachment method is realized by data interaction between the MCC and the MCS, the generation process of the attachment request message sent to the MCS can be referred to the above implementation The description of the corresponding part of the example is not repeated in this application, and the following embodiment describes the steps of the group attachment method performed by the MCS.

Referring to FIG. 4 , it is a schematic flow diagram of another optional example of the group attachment method proposed by this application. This method can be applied to a server MCS, such as a physical server or a cloud server supporting cloud computing. This application applies to the MCS equipment The type is not limited and may vary depending on the situation. As shown in Figure 4, the group attachment methods implemented by the MCS may include:

Step S41, receiving an attach request message for the target group sent by the client;

As can be seen from the above description of the client-side embodiment, the target group may be at least one of the multiple groups that currently exist; the attach request message may be generated using the target attach ID that the target group satisfies. , including at least a target attachment identifier; the target attachment identifier may be used to indicate that the client is attached to all of the multiple groups that currently exist, or the client is attached to some of the multiple groups. Regarding the acquisition process of the attach request message, reference may be made to, but not limited to, the description of the corresponding part of the above embodiment, and details are not described in this embodiment.

Step S42, responding to the attach request message, and controlling the client to perform an attach operation on the target group according to the target attach identifier;

Combined with the above description of the relevant content of the target attachment ID, the server parses the attachment request message, and after obtaining the target attachment ID, it can determine the target group that the client requests to attach based on the target attachment ID, that is, determine that the user of the client is interested in Which groups are selected, so as to control the client to perform an attach operation on the target group, and this application does not describe the specific implementation process of the attach operation in detail.

Step S43, according to the attachment notification message format, the target attachment identifier is used to replace the group information of the client's successful attachment group to form an attachment notification message for the client attachment group;

Step S44, feeding back the attachment notification message to the client.

In the actual application of group attachment, after the server MCS implements the attach operation of the client MCC to the target group, it can inform the client MCC of the attachment result. In this case, the MCS can still determine the The attachment notification message format requires that an attachment notification message containing the group attachment result of the client be generated. In order to shorten the length of the attachment notification message, this application still uses the target attachment identifier to replace the group information of the client's successful attachment group. An attach notification message is composed for a client attachment group.

Exemplarily, the scenario in which the client MCC attached to the five groups A, B, C, D, and E to which it belongs, or the two groups A and B listed in the above embodiment is still used as an example illustrate. Compared with the group information of all the groups that the client is attached to listed in the attachment notification message shown in Figure 5a, the five groups A, B, C, D, and E listed in the dashed box in Figure 5a are the respective groups Information, this application proposes that all-groups@mcs.group.com, the client, attaches the attachment identities of all groups to replace these group information, and constitutes the attachment notification message shown in Figure 5b. From the comparison of the content lengths in the dotted boxes in Figure 5a and Figure 5b, it is obvious that the attachment notification message method proposed by this application greatly shortens the length of the attachment notification message, especially when there are many client attachment groups , which can better reflect the advantages of the attachment notification message generation method of the present application.

Similarly, the generation method of the attachment notification message for the partial group to which the client attaches belongs is similar. It should be noted that it is similar to the above method for generating the attachment request message for the partial belonging group, as shown in Figure 5c For the content in the dotted box, while the attachment identifier of part-groups@mcs.group.com replaces the group information of the part of the attached group, it is necessary to explain the group identifier of this part of the group, that is, groups numbers = "A, B", so that the client can know which part of the group it has successfully attached to.

It can be understood that, in still some embodiments, as analyzed above, in the case that the client requests to attach a partial group, the attach request message sent by the client may include a one-to-one target attachment identifier corresponding to the partial group. In this way, The server can directly determine which group or groups the client requests to attach this time from the target attachment ID. In this case, it is not necessary to add the respective group IDs of these groups in the generated attachment request message , further reducing the length of the attach request message.

It should be noted that in the process of the server controlling the client to attach the target group, it may not succeed in attaching all the target groups. In this case, when the server constructs the attach notification message, the required attach identifier may be different from The target attachment ID in the received attachment request message is different. If the attachment request message is the target attachment ID and is the first attachment ID, the server controls the client to only attach A, B, C, D, and E in five groups. Groups B, C, and D are attached successfully. Then, the attachment notification message fed back by the server will be generated by the second attachment ID instead of the group messages of the four groups A, B, C, and D. The specific implementation process is the same as above. The implementation process of the embodiment described in the embodiment in which all the target groups requesting to attach are successfully attached is similar, and this application will not describe it in detail with examples.

To sum up, in the embodiment of this application, since the attach request message sent by the client is composed of the target attach identifier instead of the group information of the interested target group, it is ensured that the server can quickly and completely obtain the attach request message, In the process of responding to the attach request message, it is possible to directly determine which target groups the client requests to attach based on the target attach identifier, thereby controlling the client to perform attach operations on these target groups, and determining the target groups to which the client successfully attaches. After grouping, in order to ensure that the attachment result is quickly and reliably fed back to the client, the server will replace it with the corresponding target attachment ID. The group information of the client successfully attaching to the group constitutes an attachment notification message for the client attachment group, which greatly shortens the The length of the attachment notification message can be quickly and completely fed back to the client in the transmission of the wireless environment, so that the client can know which target group the client is currently attached to from the target attachment ID contained in it. Group, such as all or part of the group to which the user belongs, so that the user can perform business access operations on the attached target group to meet the user's business access needs.

In combination with the group attachment method described in the above embodiments, in practical applications such as instant messaging, video conferencing, online games, and streaming multimedia distribution, the client MCC and server MCS can be implemented based on SIP (Session Initiation Protocol, Session Initiation Protocol). The data interaction between them meets the communication needs of corresponding applications. Among them, for the data interaction between the client MCC and the server MCS, it can be an extended application defined according to the SIP event notification mechanism specification, that is, a subscription (SUBSCRIBE) for initiating a subscription request, and a subscription (SUBSCRIBE) for notifying the current resource status. Notify (NOTIFY), create a dialogue link between the client MCC and the server MCS.

Based on this, combined with the message content shown in Figure 2a to Figure 2d above, and Figure 5a, Figure 5b, and Figure 5c, the SUBSCRIBE message sent by the client to the server may include a request uniform resource identifier (Request-URI), That is, the URI of the resource to be requested. This application does not display the composition and format requirements of the above-mentioned SUBSCRIBE message and NOTIFY message, and it depends on the situation.

Therefore, after the client MCC is successfully registered, the subscription relationship between the client MCC and the server MCS can be established through the Subscribe method, so as to obtain the group attachment result through the NOTIFY method. Specifically, the client MCC can send a group attachment result SIP Subscribe subscription request to the server MCS, and the server MCS can build a subscription relationship between the server MCS and the client MCC in response to the subscription request. In this way, the subsequent client MCC If the group attachment result changes (such as adding a new group attachment based on the original attachment group, etc.), the subscription relationship can be triggered, and the server MCS can feed back the change to the client through SIP Notify (ie attachment notification message) MCC.

Specifically, the user enters the client MCC group attachment interface, and sees the groups to which the user belongs, the attachment status of the user client to each group (that is, whether the client is attached to the corresponding group), and the services supported by each group. Type and other information, from which you can select all or part of the groups you are interested in (which may include the attached group, the unattached group, etc.), so as to request to attach to the selected group.

Based on the above description of the SIP protocol, in this application, the client MCC can send a SIP SUBSCRIBE message (such as the above-mentioned attachment request message) to the server MCS, carrying the application/pidf composed of the target attachment identifier satisfied by the selected target group of interest. +xml message, the server receives the SIP SUBSCRIBE message, and can feed back a confirmation message, such as a SIP 200OK response message, which can indicate that the subscription has been accepted and the user has been authorized to subscribe to the requested resource. Afterwards, the server MCS can respond to the SIP SUBSCRIBE message in the above-mentioned manner to realize the attachment of the client to the target group, so that the group attachment result of the client changes. Subscription relationship, you can feed back a SIP NOTIFY message to the client MCC, that is, an attachment notification message carrying the target attachment ID. After receiving the SIP NOTIFY message, the client MCC can reply to confirm the arrival of the SIP 200 OK, so that the server MCS knows the client The MCC successfully receives the notification message. For the generation process of the foregoing messages, reference may be made to the descriptions in the corresponding parts of the above embodiments, and the embodiments of the present application will not repeat them here.

It should be noted that the content and format of the SIP 200OK response fed back by the client MCC and the server MCS can be determined according to the SIP protocol specification, and this application does not limit it.

Referring to FIG. 6 , it is a schematic structural diagram of an optional example of the group attachment device proposed in this application. The device can be applied to an electronic device, and more specifically, the device can be a virtual device of a client MCC in an electronic device. As shown in Figure 6, the device may include:

A target group determination module 61, configured to determine the target group to which the client requests to attach;

A target attachment identification acquisition module 62, configured to acquire a target attachment identification satisfied by the target group; the target attachment identification includes all groups used to indicate that the client attachment currently exists in multiple groups, or The client is attached to some groups in the plurality of groups;

An attach request message generating module 63, configured to use the target attach identifier to generate an attach request message for the target group; the attach request message at least includes the target attach identifier;

An attach request message sending module 64, configured to send the attach request message to the server, so that the server responds to the attach request message and controls the client to perform an attach operation on the target group.

In some embodiments, the above-mentioned target attachment identification acquisition module 62 may include:

A first selection unit, configured to select a target attachment identifier that matches the target relationship from a variety of pre-configured attachment identifiers according to the target relationship between the target group and multiple currently existing groups;

In still other embodiments, the above-mentioned target group determination module 61 may include:

A selection determination unit, configured to determine a target group to which the selected client requests to attach in response to a group attachment selection operation on a plurality of currently existing groups;

Based on this, the above-mentioned target attachment identification acquisition module 62 may also include:

The second selection unit is configured to determine the selected attachment ID as the target attachment ID in response to a selection operation on the output multiple attachment IDs.

Based on the device structure described in the above embodiments, the device may also include:

The first configuration unit is configured to configure, according to the uniform resource identifier format specified in the group attachment protocol, the first attachment identifier used to indicate that the client is attached to all of the multiple groups that currently exist;

The second configuration unit is configured to configure, according to the uniform resource identifier format, a second attachment identifier used to indicate that the client is attached to some of the groups in the plurality of groups.

In some embodiments, if the above-mentioned target attachment identifier includes part of the multiple groups used to indicate that the client is attached to currently existing groups, the above-mentioned attach request message generating module 63 may include:

a group identification obtaining unit, configured to obtain the respective target group identifications of the target groups;

The message constituting unit is configured to compose an attach request message for the target group according to the format of the attach request message and according to the target group identifier.

Referring to FIG. 7 , it is a schematic structural diagram of another optional example of the group attachment device proposed in this application. This device can be applied to a server, such as the above-mentioned MCS. As shown in FIG. 7 , the device can include:

An attach request message receiving module 71, configured to receive an attach request message for a target group sent by a client; wherein, the target group is at least one of a plurality of groups that currently exist; the attach request The message is generated by using the target attachment identifier satisfied by the target group, and at least includes the target attachment identifier; the target attachment identifier includes all groups used to indicate that the client is attached to a plurality of groups that currently exist, or the client is attached to some of the multiple groups;

The attach operation module 72 is configured to control the client to perform an attach operation on the target group according to the target attach identifier in response to the attach request message.

Optionally, the attachment operation module 72 may include:

A parsing unit, configured to parse the attach request message to obtain the target attach identifier;

a target group determining unit, configured to determine the target group to which the client requests to attach according to the target attachment identifier;

an attach operation unit, configured to control the client to perform an attach operation on the target group.

In some other embodiments, as shown in Figure 7, the device may also include:

The notification message composition module 73 is configured to compose an attachment notification message for the client attachment group according to the attachment notification message format and according to the target attachment identifier;

A notification message feedback module 74, configured to feed back the attachment notification message to the client.

It should be noted that the various modules, units, etc. in the above-mentioned apparatus embodiments can all be stored as program modules in the memory of the corresponding device (such as electronic equipment, server), and executed by the processor in the device. The above-mentioned program modules in the memory are used to realize corresponding functions. For the functions realized by each program module and its combination, and the technical effect achieved, you can refer to the description of the corresponding part of the above-mentioned method embodiment, and this embodiment will not repeat them.

The present application also provides a computer-readable storage medium on which a computer program can be stored, and the computer program can be invoked and loaded by a processor to implement the group attachment method described in the above-mentioned client-side or server-side embodiments, specifically The implementation process is not described here in this embodiment of the present application.

Referring to FIG. 8 , it is a schematic structural diagram of an optional example of a group attachment system applicable to the group attachment method and device proposed in this application. The system may include at least one terminal (such as the above-mentioned electronic device) 81 and a server 82 ,in:

Terminal 81 may include, but is not limited to, smart phones, tablet computers, wearable devices, personal computers (personal computers, PCs), netbooks, personal digital assistants (personal digital assistants, PDAs), smart watches, augmented reality technology (Augmented Reality , AR) equipment, virtual reality (Virtual Reality, VR) equipment, vehicle-mounted equipment, smart speakers, robots, desktop computers and other electronic equipment, this application does not limit the product type of the terminal 81, it depends on the situation.

In this embodiment of the application, an MCC (Mission Critical Client) can be configured in the terminal 81. In different scenarios, the application type of the MCC may be different, and this application does not limit the application type of the MCC. In combination with the group attachment method described above from the client side, it can be known that the apparatus 81 may include at least one first memory 811 and at least one first processor 812 .

Wherein, the first memory 811 may be used to store the first program implementing the group attachment method described above from the client side; the first processor 812 may be used to load and execute the first program stored in the first memory. program to implement the group attachment method described above from the client side. Only after the specific implementation can refer to the description of the corresponding method embodiment above, and this embodiment will not be repeated here.

In practical applications, the first memory 811 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device or other volatile solid-state storage devices. The first processor 812 may be a central processing unit (Central Processing Unit, CPU), a specific application integrated circuit (application-specific integrated circuit, ASIC), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), and an off-the-shelf Programmable gate array (FPGA) or other programmable logic devices, etc. The present application may determine the types of memory and processor configured on the terminal that support the realization of the above-mentioned client MCC function according to the actual situation, including but not limited to the types of devices listed in this embodiment.

In addition, it can be understood that the structure of the terminal shown in FIG. 8 does not constitute a limitation on the terminal in the embodiment of the present application. In practical applications, the terminal may include more components than those shown in FIG. 8, or combine certain components, As shown in Figure 9, the device can also include communication interfaces of communication modules such as WIFI module, 5G/6G (fifth generation mobile communication network/sixth generation mobile communication network) module, GPRS module, display screen, pickup, microphone , various sensor modules, power management modules, antennas, cameras, and at least one input device and output device, which are not listed here in this application.

The server 82 can support the service device realized by the function of the above-mentioned client MCC, that is, the above-mentioned MCS (Mission Critical Service, mission-critical server). In practical applications, the server 82 can be a physical server, or a service cluster formed by multiple physical servers; it can also be a cloud server supporting cloud computing, and the data exchange with the above-mentioned terminal 81 can be realized through a wired network or a wireless network. Communication, the specific communication method is not limited in this application, it depends on the situation.

In the embodiment of the present application, as shown in FIG. 8, the server 82 may include at least one second memory 821 and at least one second processor 822; The second program of the group attach method; the second processor 822 can be used to load and execute the second program stored in the second memory 821, so as to realize the group attach method described above from the server MCS side, the specific implementation process can refer to The above description of the corresponding method embodiment will not be repeated here in this embodiment.

Among them, regarding the device types of the second memory 821 and the second processor 822, you can refer to the above description of the device types of the first memory 811 and the first processor 812, and the application can determine the second memory 821 and The types of the second processors 822 are not limited in this application.

It should be understood that the structure of the server shown in Figure 8 above does not constitute a limitation on the server in this embodiment of the application. In actual applications, the server may include more components than those shown in Figure 8, or combine certain components , the present application does not enumerate them one by one here.

Finally, it should be noted that, with respect to the above-mentioned embodiments, relative terms such as first, second, etc. are only used to distinguish one operation, unit or module from another operation, unit or module, and not Any such actual relationship or order between these units, operations or modules is necessarily required or implied. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method or system comprising a set of elements includes not only those elements but also other elements not expressly listed. elements, or elements inherent in such a process, method, or system. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method or system comprising said element.

Among them, in the description of the embodiments of this application, unless otherwise specified, "/" means or means, for example, A/B can mean A or B; "and/or" in this article is only a description of associated objects The association relationship of indicates that there may be three kinds of relationships, for example, A and/or B may indicate: A exists alone, A and B exist simultaneously, and B exists independently. In addition, in the description of the embodiments of the present application, "plurality" refers to two or more than two.

Each embodiment in this specification is described in a progressive or parallel manner, each embodiment focuses on the differences from other embodiments, and the same and similar parts of each embodiment can be referred to each other. As for the devices and systems disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple, and for the related parts, please refer to the description of the method part.

The above description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention will not be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

A group attachment method, characterized in that the method comprises:

Determine the target group to which the client requests to attach;

Acquiring the target attachment ID satisfied by the target group; the target attachment ID is used to indicate that the client is attached to all of the multiple groups that currently exist, or that the client is attached to the multiple groups part of a group;

generating an attach request message for the target group by using the target attach identifier; the attach request message at least includes the target attach identifier;

sending the attach request message to the server, so that the server responds to the attach request message and controls the client to perform an attach operation on the target group.
The method according to claim 1, wherein said obtaining the target attachment identifiers satisfied by the target group comprises:

According to the target relationship between the target group and multiple currently existing groups, select a target attachment ID that matches the target relationship from multiple types of pre-configured attachment IDs;

Wherein, the target relationship is the first relationship that the target group is all of the multiple groups, or the target group is the second relationship of some of the multiple groups. relationship, and the second relationship includes a combination of one or more partial groups.
The method according to claim 1, wherein the determining the target group for which the client requests to attach, and obtaining the target attachment identifier satisfied by the target group includes:

In response to a group attach selection operation on a plurality of currently existing groups, determine a target group to which the selected client requests to attach;

In response to the selection operation on the output multiple attachment identifiers, the selected attachment identifier is determined as the target attachment identifier.
The method according to claim 1, further comprising:

According to the uniform resource identifier format stipulated in the group attachment protocol, configure the first attachment identifier used to indicate that the client is attached to all of the multiple groups that currently exist;

According to the uniform resource identifier format, configure a second attachment identifier used to indicate that the client is attached to some of the multiple groups.
The method according to any one of claims 1 to 4, wherein if the target attachment identifier includes part of a plurality of groups used to indicate that the client is currently attached, the use of the target A group attach identifier, generating an attach request message for the target group, including:

Obtaining respective target group identifiers of the target groups;

Construct an attach request message for the target group according to the format of the attach request message and according to the identifier of the target group.
A group attachment method, characterized in that the method comprises:

Receiving an attach request message for a target group sent by a client; wherein, the target group is at least one of a plurality of currently existing groups; the attach request message uses the target group to satisfy generated by the target attachment ID, at least including the target attachment ID; the target attachment ID is used to indicate that the client is attached to all of the multiple groups that currently exist, or that the client is attached to the multiple groups part of a group;

In response to the attach request message, control the client to perform an attach operation on the target group according to the target attach identifier.
The method according to claim 6, wherein the responding to the attachment request message, controlling the client to perform an attachment operation on the target group according to the target attachment identifier, comprises:

Parsing the attach request message to obtain the target attach identifier;

Determine the target group to which the client requests to attach according to the target attachment identifier;

controlling the client to perform an attach operation on the target group.
The method according to claim 6 or 7, characterized in that the method further comprises:

Constructing an attach notification message for the client attachment group according to the attachment notification message format and according to the target attachment identifier;

Feedback the attachment notification message to the client.
A group attachment device, characterized in that the device comprises:

A target group determination module, configured to determine the target group to which the client requests to attach;

A target attachment identification acquisition module, configured to acquire a target attachment identification satisfied by the target group; the target attachment identification includes all groups used to indicate that the client is currently attached to a plurality of groups, or the The client is attached to some groups in the plurality of groups;

An attach request message generating module, configured to generate an attach request message for the target group by using the target attach identifier; the attach request message at least includes the target attach identifier;

An attach request message sending module, configured to send the attach request message to a server, so that the server responds to the attach request message and controls the client to perform an attach operation on the target group.
The device according to claim 9, wherein the target attachment identification acquisition module includes:

A first selection unit, configured to select a target attachment identifier that matches the target relationship from a variety of pre-configured attachment identifiers according to the target relationship between the target group and multiple currently existing groups; Wherein, the target relationship is the first relationship that the target group is all of the multiple groups, or the target group is the second relationship of some of the multiple groups. relationship, and the second relationship comprises a combination of one or more partial groups;

or,

The second selection unit is configured to determine the selected attachment ID as the target attachment ID in response to a selection operation on the output multiple attachment IDs.
The device according to claim 9, wherein the device further comprises:

The first configuration module is configured to configure, according to the uniform resource identifier format specified in the group attachment protocol, the first attachment identifier used to indicate that the client is attached to all of the multiple groups that currently exist;

The second configuration module is configured to configure, according to the uniform resource identifier format, a second attachment identifier used to indicate that the client is attached to some of the groups.
The device according to any one of claims 9-11, wherein if the target attachment identifier includes part of the multiple groups that are used to indicate that the client is attached to the current existing groups, the attachment request message generates modules, including:

a group identification obtaining unit, configured to obtain the respective target group identifications of the target groups;

The message constituting unit is configured to compose an attach request message for the target group according to the format of the attach request message and according to the target group identifier.
A group attachment device, characterized in that the device comprises:

An attach request message receiving module, configured to receive an attach request message for a target group sent by a client; wherein, the target group is at least one group among multiple groups that currently exist; the attach request message is generated by using the target attachment identifier satisfied by the target group, and at least includes the target attachment identifier; the target attachment identifier includes all groups in the plurality of groups used to indicate that the client attaches currently exists, or The client is attached to some groups in the plurality of groups;

An attach operation module, configured to control the client to perform an attach operation on the target group according to the target attach identifier in response to the attach request message.
A storage medium, characterized in that a computer program is stored thereon, and the computer program is invoked and executed by a processor to realize the group attachment method according to any one of claims 1 to 5, or to realize the method according to any one of claims 1-5. The group attachment method described in any one of 6 to 8.
A group attachment system, characterized in that the system includes at least one terminal and a server, wherein:

The terminal includes at least one first memory and at least one first processor;

The first memory is used to store a first program implementing the group attachment method according to any one of claims 1-5;

The first processor is configured to load and execute the first program stored in the first memory, so as to implement the group attachment method according to any one of claims 1-5;

The server includes at least one second memory and at least one second processor;

The second memory is used to store a second program implementing the group attachment method according to any one of claims 6-8;

The second processor is configured to load and execute the second program stored in the second memory, so as to implement the group attachment method according to any one of claims 6-8.