WO2023082244A1 - Procédé d'affiliation à un groupe et dispositif correspondant - Google Patents

Procédé d'affiliation à un groupe et dispositif correspondant Download PDF

Info

Publication number
WO2023082244A1
WO2023082244A1 PCT/CN2021/130622 CN2021130622W WO2023082244A1 WO 2023082244 A1 WO2023082244 A1 WO 2023082244A1 CN 2021130622 W CN2021130622 W CN 2021130622W WO 2023082244 A1 WO2023082244 A1 WO 2023082244A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
attachment
group
client
attach
Prior art date
Application number
PCT/CN2021/130622
Other languages
English (en)
Chinese (zh)
Inventor
王雄集
杨河山
Original Assignee
海能达通信股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 海能达通信股份有限公司 filed Critical 海能达通信股份有限公司
Priority to PCT/CN2021/130622 priority Critical patent/WO2023082244A1/fr
Publication of WO2023082244A1 publication Critical patent/WO2023082244A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/08—Trunked mobile radio systems

Definitions

  • This application mainly relates to the field of MCS clusters, and more specifically relates to a group attachment method and corresponding equipment.
  • 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.
  • 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.
  • the present application proposes a group attachment method, the method comprising:
  • 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;
  • the attach request message at least includes the target attach identifier
  • the acquiring the target attachment identifiers satisfied by the target group includes:
  • 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 determining the target group for which the client requests to attach, and obtaining the target attachment identifier satisfied by the target group includes:
  • the selected attachment identifier is determined as the target attachment identifier.
  • the method also includes:
  • 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;
  • 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 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:
  • the present application also proposes a group attachment method, the method comprising:
  • 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
  • control the client 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 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:
  • the method also includes:
  • 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.
  • the present application also proposes a group attachment device, the device comprising:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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 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.
  • 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.
  • MCC Mobility Critical Client
  • This application does not limit the product type of electronic equipment and the application type of MCC, depending on the situation.
  • the mission-critical client is referred to as the client
  • the mission-critical server MCS is referred to as the server, and the following embodiments will not be described one by one.
  • the group attachment method described from the MCC side may include:
  • Step S11 determining the target group to which the client requests to attach
  • 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.
  • the group selected by the user is recorded as the target group.
  • 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.
  • 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
  • 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.
  • 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.
  • the target attachment identifier may be the above-mentioned first attachment identifier Flag1, and the specific acquisition method is not limited.
  • 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.
  • 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.
  • first attachment identifier Flag1 and second attachment identifier Flga2 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.
  • the group attachment protocol may be the above-mentioned application/pidf+xml
  • the format may be the xs:anyURI format specified in application/pidf+xm, and this application does not limit its content.
  • 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.
  • 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.
  • the group categories contained in these groups may be different.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • the methods for generating attach request messages of other partial groups are similar, and the present application does not
  • this application can also pre-configure the corresponding second attachment identifier for the scenario of attaching different partial groups.
  • 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.
  • 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.
  • the server 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.
  • 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.
  • 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.
  • 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;
  • 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.
  • 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;
  • 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.
  • 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.
  • the manner of determining the target attachment identifier is not limited to the implementation method described in this embodiment.
  • 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.
  • 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.
  • 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;
  • 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.
  • 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.
  • 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 attach request message will not be described in detail in this application.
  • the content and message format of the attachment request message generated by this application 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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;
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • the attachment identifier of part-groups@mcs.group.com replaces the group information of the part of the attached group
  • groups numbers "A, B”
  • the attach request message sent by the client may include a one-to-one target attachment identifier corresponding to the partial group.
  • 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.
  • the server may not succeed in attaching all the target groups.
  • 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.
  • 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.
  • the server 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.
  • the server 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.
  • the client MCC and server MCS can be implemented based on SIP (Session Initiation Protocol, Session Initiation Protocol).
  • SIP Session Initiation Protocol
  • the data interaction between them meets the communication needs of corresponding applications.
  • 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 create a dialogue link between the client MCC and the server MCS.
  • 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.
  • Request-URI uniform resource identifier
  • 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.
  • 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.
  • 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.
  • SIP Notify ie attachment notification message
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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;
  • 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 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • augmented reality technology Augmented Reality , AR
  • VR Virtual Reality
  • VR 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.
  • an MCC (Mission Critical Client) can be configured in the terminal 81.
  • the application type of the MCC may be different, and this application does not limit the application type of the MCC.
  • the apparatus 81 may include at least one first memory 811 and at least one first processor 812 .
  • 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.
  • 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.
  • the structure of the terminal shown in FIG. 8 does not constitute a limitation on the terminal in the embodiment of the present application.
  • the terminal may include more components than those shown in FIG. 8, or combine certain components
  • 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.
  • 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).
  • MCS Mobility Critical Service, mission-critical server
  • 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.
  • 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.
  • 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.
  • the structure of the server shown in Figure 8 above does not constitute a limitation on the server in this embodiment of the application.
  • 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.
  • 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.
  • the description is relatively simple, and for the related parts, please refer to the description of the method part.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente demande concerne un procédé d'affiliation à un groupe et un dispositif correspondant. Après qu'un groupe cible auquel un client a demandé de s'affilier est déterminé, afin d'éviter de former un message de demande d'affiliation plus long et d'augmenter la probabilité de perte de paquet et le retard temporel de transmission du message de demande d'affiliation dans un environnement sans fil en raison du fait que des informations de groupe de chaque groupe cible sont directement utilisées, dans la présente demande, un identifiant d'affiliation cible satisfait par le groupe cible est obtenu, c'est-à-dire que les informations de groupe de chaque groupe cible sont remplacées par un identificateur très court qui est préconfiguré et indique que le client est affilié à tous les groupes ou à certains groupes, et un message de demande d'affiliation pour le groupe cible est généré, de telle sorte que la longueur du message de demande d'affiliation est considérablement raccourcie. De cette manière, le message de demande d'affiliation est envoyé à un serveur pour une opération d'affiliation dans l'environnement sans fil, et la probabilité de perte de paquet et le retard temporel de transmission du message de demande d'affiliation sont réduits, ce qui permet d'améliorer la fiabilité et l'efficacité de transmission du message de demande d'affiliation.
PCT/CN2021/130622 2021-11-15 2021-11-15 Procédé d'affiliation à un groupe et dispositif correspondant WO2023082244A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/130622 WO2023082244A1 (fr) 2021-11-15 2021-11-15 Procédé d'affiliation à un groupe et dispositif correspondant

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/130622 WO2023082244A1 (fr) 2021-11-15 2021-11-15 Procédé d'affiliation à un groupe et dispositif correspondant

Publications (1)

Publication Number Publication Date
WO2023082244A1 true WO2023082244A1 (fr) 2023-05-19

Family

ID=86334935

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/130622 WO2023082244A1 (fr) 2021-11-15 2021-11-15 Procédé d'affiliation à un groupe et dispositif correspondant

Country Status (1)

Country Link
WO (1) WO2023082244A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101248642A (zh) * 2005-05-17 2008-08-20 斯比德航海有限公司 信令压缩/解压缩
CN101300764A (zh) * 2005-09-02 2008-11-05 北方电讯网络有限公司 Sip报头缩减
CN111935633A (zh) * 2020-08-17 2020-11-13 海能达通信股份有限公司 一种群组附着方法及相应装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101248642A (zh) * 2005-05-17 2008-08-20 斯比德航海有限公司 信令压缩/解压缩
CN101300764A (zh) * 2005-09-02 2008-11-05 北方电讯网络有限公司 Sip报头缩减
CN111935633A (zh) * 2020-08-17 2020-11-13 海能达通信股份有限公司 一种群组附着方法及相应装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
PRICE R., C. BORMANN, CHRISTOFFERSSON BREMEN J, HANNU H, LIU ERICSSON Z, ROSENBERG NOKIA J: "Signaling Compression (SigComp)", IETF, 31 January 2003 (2003-01-31), pages 1 - 62, XP093065459, Retrieved from the Internet <URL:https://www.rfc-editor.org/rfc/pdfrfc/rfc3320.txt.pdf> [retrieved on 20230719] *
马庆 等 (MA, QING ET AL.): "SIP信令压缩动态字典方案 (Dynamic Dictionary Scheme in SIP Signaling Compression)", 计算机工程 (COMPUTER ENGINEERING), vol. 35, no. 24, 20 December 2009 (2009-12-20) *
黄志海 等 (HUANG, ZHIHAI ET AL.): "SIP信令压缩技术 (Signaling Compression for SIP)", 南京邮电大学学报(自然科学版) (JOURNAL OF NANJING UNIVERSITY OF POSTS AND TELECOMMUNICATIONS(NATURAL SCIENCE)), vol. 28, no. 02, 30 April 2008 (2008-04-30), XP009546215 *

Similar Documents

Publication Publication Date Title
CN103348663B (zh) 用于多用户设备的消息推送通知客户端改善
US8234410B2 (en) Subscriber driven media agnostic content delivery across networks
US8447808B2 (en) Virtual presence server
WO2016127793A1 (fr) Procédé, appareil, système et serveur d&#39;envoi de messages
US10496245B2 (en) Method for interactive response and apparatus thereof
US8019822B2 (en) Personalized storage accounts in an electronic file delivery system
US20180234371A1 (en) Method, system and computer program product for providing interactive elements in messages
US9426108B2 (en) Method for storing conversation upon user&#39;s request in CPM system, and system thereof
CN102176763B (zh) 广播电视系统及信息交互方法
EP2560329B1 (fr) Procédé et système de traitement pour acheminer une demande de message
US9934519B2 (en) Dynamic, subscriber driven charging models for media distribution
EP1513302B1 (fr) Messagerie en temps réel dans des environnements de réseau collaboratifs
CN114449458B (zh) 一种5g消息回落方法、系统、计算设备和存储介质
US20090106437A1 (en) Method and device for handling different addressing schemes in session initiation protocol communication
US9473316B2 (en) Resource consumption reduction via meeting affinity
WO2009009981A1 (fr) Procédé, système de communication et dispositif associé pour établir une relation d&#39;accès à des ressources multimédias
JP2015502613A (ja) 連絡先情報の購読を招待する装置及び方法
US10009388B2 (en) Method and system for establishing integrated group ISC session based on content interest
WO2023082244A1 (fr) Procédé d&#39;affiliation à un groupe et dispositif correspondant
US20120005362A1 (en) Streaming data delivery system and method thereof
CN1972279B (zh) 一种会话发起协议资源事件包获取方法
WO2019201111A1 (fr) Procédé, appareil et dispositif de traitement d&#39;informations, et support de stockage lisible par ordinateur
CN114020363B (zh) 群组附着方法及相应设备
CN116627666A (zh) 通知消息的处理方法、装置、计算机设备和存储介质
CN112511884B (zh) 一种音视频流的混流控制方法、系统和存储介质

Legal Events

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

Ref document number: 21963691

Country of ref document: EP

Kind code of ref document: A1