A message pushing method, an electronic device and a readable storage medium

Abstract

The application provides a message pushing method, an electronic device and a readable storage medium. When the subscription permission information of the MCS server is preset subscription permission information, the authorized information of the user terminal is acquired, the service authorization type is extracted from the authorized information, the data acquisition link corresponding to the service authorization type is determined, the data acquisition link is pushed to the user terminal through a preset message type pushing mode, the data acquisition request when the user terminal accesses the data acquisition link is received, the target data corresponding to the data acquisition request is determined, and the target data is sent to the user terminal. That is, when it is determined that the subscription permission information of the MCS server is preset subscription permission information, the MCS server pushes the data acquisition link to the user terminal through the preset message type pushing mode through the above steps, the user terminal only needs to access the data acquisition link to acquire the target data, and the UE no longer needs to interact with the MCS multiple times, thereby saving communication resources.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and more specifically, to a message push method, an electronic device, and a readable storage medium. Background Technology

[0002] In MCS (Mission Critical Server) services, after completing registration and authorization, the UE (User Equipment) needs to obtain user subscription data and its affiliated group information from the MCS.

[0003] At this point, the UE needs to initiate SIPSUBSCRIBE requests to the modules in the MCS that store the user's subscription data and their home group information, establishing a subscription relationship with each module in the MCS. The modules in the MCS then push the subscription data and their home group information to the UE via SIP NOTIFY messages within the session. This data acquisition method requires multiple interactions between the UE and the MCS, making the interaction complex and wasting resources. Summary of the Invention

[0004] In view of this, the present invention provides a message push method, an electronic device, and a readable storage medium to solve the problem that when the UE obtains user subscription data and its affiliated group information from the MCS, the UE and the MCS interact multiple times, the interaction method is complex, and resources are wasted.

[0005] To solve the above-mentioned technical problems, the present invention adopts the following technical solution:

[0006] A message push method, applied to an MCS server, the message push method includes:

[0007] If it is determined that the subscription permission information of the MCS server is the preset subscription permission information, the authorization information of the user terminal is obtained, and the service authorization type is extracted from the authorization information;

[0008] Determine the data acquisition link corresponding to the business authorization type, and push the data acquisition link to the user terminal through a preset message type push method;

[0009] The system receives a data acquisition request from the user terminal when accessing the data acquisition link, determines the target data corresponding to the data acquisition request, and sends the target data to the user terminal.

[0010] Optionally, the business authorization type can be extracted from the authorization information, including:

[0011] The participant function service module in the MCS server parses the authorization information and extracts the business authorization type.

[0012] Optionally, determining the data retrieval link corresponding to the business authorization type includes:

[0013] The participating party function service module sends a pre-defined message type of contract data acquisition message to the configuration management service module in the MCS server. The contract data acquisition message includes the business authorization type and the user information of the user terminal.

[0014] The configuration management service module stores the first subscription relationship of the business authorization type and the user information, and determines the subscription data acquisition link corresponding to the subscription data acquisition message;

[0015] The participating party function service module sends a group data acquisition message of a preset message type to the group management service module in the MCS server. The group data acquisition message includes the business authorization type and the user information of the user terminal.

[0016] The group management service module stores the business authorization type and the second subscription relationship of the user information, and determines the group data retrieval link corresponding to the group data retrieval message.

[0017] Optionally, receiving a data acquisition request from the user terminal when accessing the data acquisition link, determining the target data corresponding to the data acquisition request, and sending the target data to the user terminal includes:

[0018] The system receives a first data acquisition request from the user terminal when it accesses the contract data acquisition link, determines the user contract data corresponding to the first data acquisition request, and sends the user contract data to the user terminal.

[0019] The system receives a second data acquisition request from the user terminal when accessing the group data acquisition link, determines the belonging group data corresponding to the second data acquisition request, and sends the belonging group data to the user terminal.

[0020] Optionally, it also includes:

[0021] After determining that the user's subscription data on the user terminal has been modified, the configuration management service module queries whether the first subscription relationship exists.

[0022] If it exists, a signing data acquisition link is sent to the user's terminal;

[0023] The system receives a third data acquisition request from the user terminal when accessing the contract data acquisition link, determines the updated user contract data corresponding to the third data acquisition request, and sends the updated user contract data to the user terminal.

[0024] Optionally, it also includes:

[0025] After determining that the user terminal's group data has been modified, the group management service module queries whether the second subscription relationship exists.

[0026] If it exists, a group data retrieval link is sent to the user terminal;

[0027] The system receives a fourth data acquisition request from the user terminal when accessing the group data acquisition link, determines the updated home group data corresponding to the fourth data acquisition request, and sends the updated home group data to the user terminal.

[0028] Optionally, before determining that the subscription permission information of the MCS server is the preset subscription permission information, the method further includes:

[0029] The system receives an initialization configuration information retrieval request sent by a user terminal and determines the preset response information corresponding to the user information of the user terminal. The preset response information includes preset subscription permission information.

[0030] A message push method, applied to a user terminal, the message push method includes:

[0031] The system receives a data acquisition link pushed by the MCS server through a preset message type push method. The data acquisition link is the link through which the MCS server obtains the authorization information of the user terminal and extracts the business authorization type corresponding to the authorization information when it determines that the subscription permission information of the MCS server is the preset subscription permission information.

[0032] When accessing the data acquisition link, a data acquisition request is sent to the MCS server so that the MCS server can determine the target data corresponding to the data acquisition request;

[0033] Receive the target data sent by the MCS server.

[0034] Optionally, a data retrieval request when accessing the data retrieval link is sent to the MCS server, so that the MCS server determines the target data corresponding to the data retrieval request, including:

[0035] When accessing the contract data retrieval link, a first data retrieval request is sent to the MCS server so that the MCS server can determine the user contract data corresponding to the first data retrieval request.

[0036] When accessing the group data retrieval link, a second data retrieval request is sent to the MCS server so that the MCS server can determine the group data to which the second data retrieval request belongs.

[0037] Optionally, it also includes:

[0038] The system receives a subscription data retrieval link sent by the MCS server. This subscription data retrieval link is sent by the configuration management service module in the MCS server when it determines that the user's subscription data on the user terminal has been modified, and the module queries whether a first subscription relationship exists.

[0039] When accessing the contract data acquisition link, a third data acquisition request is sent to the MCS server so that the MCS server can determine the updated user contract data corresponding to the third data acquisition request.

[0040] Receive the updated user subscription data sent by the MCS server.

[0041] Optionally, it also includes:

[0042] Receive the group data retrieval link sent by the MCS server. The group data retrieval link is sent by the group management service module in the MCS server when it queries whether a second subscription relationship exists after the MCS server determines that the user terminal's belonging group data has been modified.

[0043] When accessing the group data retrieval link, a fourth data retrieval request is sent to the MCS server so that the MCS server can determine the updated attribution group data corresponding to the fourth data retrieval request.

[0044] Receive the updated home group data sent by the MCS server.

[0045] Optionally, before receiving the data retrieval link pushed by the MCS server using a preset message type push method, the following is also included:

[0046] An initialization configuration information retrieval request is sent to the MCS server so that the MCS server can determine the preset response information corresponding to the user information of the user terminal. The preset response information includes preset subscription permission information.

[0047] A message push device, applied to an MCS server, the message push device comprising:

[0048] The information acquisition module is used to acquire the authorization information of the user terminal when it is determined that the subscription permission information of the MCS server is the preset subscription permission information, and to extract the service authorization type from the authorization information;

[0049] The data push module is used to determine the data acquisition link corresponding to the business authorization type and push the data acquisition link to the user terminal through a preset message type push method;

[0050] The data sending module is used to receive a data acquisition request when the user terminal accesses the data acquisition link, determine the target data corresponding to the data acquisition request, and send the target data to the user terminal.

[0051] A message push device, applied to a user terminal, the message push device comprising:

[0052] The link acquisition module is used to receive a data acquisition link pushed by the MCS server through a preset message type push method. The data acquisition link is the authorization information of the user terminal obtained by the MCS server when it determines that the subscription permission information of the MCS server is the preset subscription permission information, and the corresponding business authorization type extracted from the authorization information.

[0053] The request sending module is used to send a data acquisition request when accessing the data acquisition link to the MCS server, so that the MCS server can determine the target data corresponding to the data acquisition request.

[0054] The data receiving module is used to receive the target data sent by the MCS server.

[0055] An electronic device includes: a memory and a processor;

[0056] The memory is used to store programs;

[0057] The processor calls the program and executes the message push method described above.

[0058] Compared with the prior art, the present invention has the following beneficial effects:

[0059] This invention provides a message push method, an electronic device, and a readable storage medium. When the subscription permission information of the MCS server is determined to be preset subscription permission information, the method obtains the authorization information of the user terminal, extracts the service authorization type from the authorization information, determines the data acquisition link corresponding to the service authorization type, and pushes the data acquisition link to the user terminal via a preset message type push method. The method receives the data acquisition request from the user terminal when accessing the data acquisition link, determines the target data corresponding to the data acquisition request, and sends the target data to the user terminal. In other words, in this invention, when the subscription permission information of the MCS server is determined to be preset subscription permission information, the MCS server directly pushes the data acquisition link to the user terminal via a preset message type push method through the above steps. The user terminal only needs to access the data acquisition link to obtain the target data, eliminating the need for multiple interactions between the UE and the MCS, thereby saving communication resources. Attached Figure Description

[0060] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0061] Figure 1 A schematic diagram illustrating a scenario for a message push method provided by existing technology;

[0062] Figure 2 A flowchart of a message push method provided in an embodiment of the present invention;

[0063] Figure 3 This is a schematic diagram illustrating a scenario of a message push method provided in an embodiment of the present invention;

[0064] Figure 4 A flowchart of another message push method provided in an embodiment of the present invention;

[0065] Figure 5 A schematic diagram illustrating another message push method provided in an embodiment of the present invention;

[0066] Figure 6 A schematic diagram illustrating another message push method provided in an embodiment of the present invention;

[0067] Figure 7 A schematic diagram illustrating another message push method provided in an embodiment of the present invention;

[0068] Figure 8 This is a schematic diagram of the structure of a message push device provided in an embodiment of the present invention;

[0069] Figure 9 This is a schematic diagram of another message push device provided in an embodiment of the present invention. Detailed Implementation

[0070] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0071] In MCS services, after completing registration and authorization, the UE needs to obtain user subscription data, basic information about its group, and group key from the MCS. To do this, the UE needs to initiate SIP SUBSCRIBE (Session Initiation Protocol) requests for both user and group subscription data to establish a subscription relationship with the MCS. The MCS then pushes the subscription data to the UE via a SIP NOTIFY message within the session. During the subscription period, if the subscription data changes, the MCS will also push the updated subscription data to the UE via a NOTIFY message.

[0072] Specifically, refer to Figure 1 , Figure 1 A standard data push process is presented.

[0073] The user terminal (UE) sends an HTTP request to the CMS (Configuration Management Server) in the MCS to obtain the user initialization configuration information (get ue-init-config). The CMS module then returns a 200 OK response, which carries the user initialization configuration information, namely the ue-init-configxml information.

[0074] Subsequently, the UE sends an authorization request (PUBLISH) to the PF (Participation Function) in the MCS, and the PF module returns a 200 OK response.

[0075] After completing the PUBLISH license:

[0076] 1. The terminal UE sends an explicit SUBSCRIBE user subscription data request to the CMS, and the CMS returns a 00OK response message;

[0077] 2. The CMS sends a NOTIFY message to push the user's subscription data URL (Uniform Resource Locator) and establishes a subscription session;

[0078] 3. The terminal UE retrieves the subscription data via HTTP, that is, the terminal UE sends an HTTP request to Get User-Profile, and the CMS returns the user subscription data XML;

[0079] 4. The terminal UE sends a SUBSCRIBE explicit group information subscription request to GMS (Group Management Server);

[0080] 5. GMS sends the NOTIFY message push group information data URL to establish a subscription session;

[0081] 6. The terminal retrieves group information via HTTP, that is, the terminal UE sends an HTTP request to Get Group-Profile, and GMS returns group information data in XML format.

[0082] Due to the characteristics of SIP subscription sessions, they represent a long-term resource occupied by both the terminal and the server during the subscription period. Their unique state transitions are highly dependent on the timing of requests and responses, meaning they have strict timing requirements. In certain scenarios involving out-of-order messages and packet loss, the subscription relationship can fail, leading to anomalies such as the failure to push subscribed data, basic information about the home group, and group keys. Furthermore, out-of-order and lost messages in the subscription session can also cause the subscription relationship to fail, impacting business stability.

[0083] In addition, the establishment of subscription relationships and the signaling process for push notifications between terminals and servers are relatively complex, resulting in SIP subscription sessions consuming a lot of resources.

[0084] To address the issues of complex interactive signaling processes, high resource consumption, and subscription relationship failures caused by message out-of-order delivery and packet loss, this embodiment of the invention uses a heavyweight session mechanism in the SIP protocol, where both the protocol stack and application layer maintain the subscription relationship, consuming system memory. By not using the SUBSCRIBE / NOTIFY mechanism, the memory resource consumption of the protocol stack is reduced. Therefore, this embodiment does not employ the aforementioned SIP mechanism (session-based SUBSCRIBE / NOTIFY messages) but instead uses a transactional MESSAGE message mechanism to ensure the stability and reliability of the subscription relationship and push notifications. Furthermore, the subscription relationship establishment process is simplified, reducing the complexity of interactive signaling and thus decreasing SIP session resource consumption.

[0085] Specifically, this invention provides a message push method, an electronic device, and a readable storage medium. When the subscription permission information of the MCS server is determined to be preset subscription permission information, the method obtains the authorization information of the user terminal, extracts the service authorization type from the authorization information, determines the data acquisition link corresponding to the service authorization type, and pushes the data acquisition link to the user terminal via a preset message type push method. It also receives the data acquisition request from the user terminal when accessing the data acquisition link, determines the target data corresponding to the data acquisition request, and sends the target data to the user terminal. In other words, in this invention, when the subscription permission information of the MCS server is determined to be preset subscription permission information, the MCS server directly pushes the data acquisition link to the user terminal via a preset message type push method through the above steps. The user terminal only needs to access the data acquisition link to obtain the target data, eliminating the need for multiple interactions between the UE and the MCS, thereby saving communication resources.

[0086] Based on the above, this invention provides a message push method applicable to the POC (PTT Over Cellular) / MCS field. (See also...) Figure 2 It can include:

[0087] S11. If it is determined that the subscription permission information of the MCS server is the preset subscription permission information, obtain the authorization information of the user terminal, and extract the service authorization type from the authorization information.

[0088] In practical applications, refer to Figure 3 Before executing step S11, an initialization configuration information acquisition request sent by a user terminal is received, and the preset response information corresponding to the user information of the user terminal is determined. The preset response information includes preset subscription permission information.

[0089] Specifically, when the terminal makes an HTTP request to obtain initial configuration information (i.e., GET ue-init-config), the server returns a 200 OK response containing preset response information (ue-init-config xml) with extended field tags. <implicit-subscriber-enabled> true< / implicit-subscriber-enabled> .

[0090] This extended field label identifies the implicit subscription switch, where true indicates on and false indicates off. In this embodiment, true indicates preset subscription permission information, meaning the MCS server's subscription permission information is the preset subscription permission information, and the terminal does not need to explicitly subscribe, thus supporting implicit subscription operations and allowing direct push of information to the terminal. If it is false, the implicit subscription switch is off, indicating that the MCS server's subscription permission information is not the preset subscription permission information, and implicit subscription operations are not supported; the terminal will then... Figure 1 The standard procedure for displaying subscriptions involves sending SUBSCRIBE messages to MCS (CMS and GMS (Group Management Server)) to request subscriptions for user subscription data and group data, respectively. The MCS server then establishes and subscribes to these relationships.

[0091] After determining that the subscription permission information of the MCS server is the preset subscription permission information, the authorization information of the user terminal is obtained, and the service authorization type is extracted from the authorization information.

[0092] Specifically, the Participation Function (PF) module in the MCS server parses the authorization information and extracts the business authorization type.

[0093] In detail, after receiving the preset response information, the terminal UE will perform a PUBLISH authorization operation to the PF. This authorization request will carry the user information of the terminal UE and the supported service authorization types, such as mcptt / mcdata / mcvideo (mcptt: key press voice call service, mcdata: key data service, mcvideo: key press video call service). At this time, the PF returns a 200 OK response information and parses it according to the terminal PUBLISH authorization information to obtain the carried service authorization type (mcptt / mcdata / mcvideo).

[0094] S12. Determine the data acquisition link corresponding to the business authorization type, and push the data acquisition link to the user terminal through a preset message type push method.

[0095] In this embodiment, there are two types of data acquisition links: one is the contract data acquisition link, and the other is the group data acquisition link. In this embodiment, acquiring user contract data and acquiring group data are two independent steps that can be executed independently, in parallel, or sequentially. This embodiment does not have any special requirements. Figure 3 The example is to first execute the function to retrieve user subscription data, and then execute the function to retrieve the group data.

[0096] Specifically, refer to Figure 4 Determining the data retrieval link corresponding to the business authorization type may include:

[0097] S21. The participating party function service module sends a contract data acquisition message of a preset message type to the configuration management service module in the MCS server. The contract data acquisition message includes the business authorization type and the user information of the user terminal.

[0098] Specifically, refer to Figure 3 The PF sends a subscription data acquisition message (internal MESSAGE message, UE registration authorization indication) of a preset message type to the CMS, carrying the service authorization type and user information. The CMS returns a 200 OK response.

[0099] S22. The configuration management service module saves the first subscription relationship of the business authorization type and the user information, and determines the subscription data acquisition link corresponding to the subscription data acquisition message.

[0100] Specifically, the CMS stores implicit subscription relationships, that is, it stores the first subscription relationship between the business authorization type and the user information. Then, the CMS pushes the subscription data retrieval link (user subscription data URL) corresponding to the business authorization type to the terminal via MESSAGE. The terminal returns a 200 OK response. After receiving the user subscription data URL, the terminal can retrieve the user subscription data via HTTP (Hypertext Transfer Protocol).

[0101] S23. The participating party function service module sends a group data acquisition message of a preset message type to the group management service module in the MCS server. The group data acquisition message includes the business authorization type and the user information of the user terminal.

[0102] S24. The group management service module saves the second subscription relationship of the business authorization type and the user information, and determines the group data acquisition link corresponding to the group data acquisition message.

[0103] Specifically, similar to the interaction between PF and CMS mentioned above, PF sends a group data acquisition message, i.e. an internal MESSAGE message, to GMS based on the service authorization type (mcptt / mcdata / mcvideo) carried in the terminal PUBLISH authorization message. This message carries the service authorization type and user information. GMS stores an implicit subscription relationship, i.e., a second subscription relationship between the service authorization type and the user information. The first subscription relationship and the second subscription relationship can be the same.

[0104] GMS pushes the group data retrieval link (i.e., the group data information URL) corresponding to the service authorization type to the terminal via MESSAGE. The terminal returns a 200 OK response. After that, the terminal retrieves the group information via HTTP.

[0105] S13. Receive the data acquisition request when the user terminal accesses the data acquisition link, determine the target data corresponding to the data acquisition request, and send the target data to the user terminal.

[0106] Specifically, in practical applications, refer to Figure 3 The system receives a first data acquisition request (i.e., a get User-Profile HTTP request) when the user terminal accesses the contract data acquisition link, determines the user contract data (user contract data xml) corresponding to the first data acquisition request, and sends the user contract data to the user terminal.

[0107] The system receives a second data acquisition request (i.e., a getGroup-Profile HTTP request) when the user terminal accesses the group data acquisition link, determines the belonging group data (group information data xml) corresponding to the second data acquisition request, and sends the belonging group data to the user terminal.

[0108] In this embodiment, when the subscription permission information of the MCS server is determined to be preset subscription permission information, the authorization information of the user terminal is obtained, and the service authorization type is extracted from the authorization information. The data acquisition link corresponding to the service authorization type is determined, and the data acquisition link is pushed to the user terminal through a preset message type push method. The data acquisition request when the user terminal accesses the data acquisition link is received, and the target data corresponding to the data acquisition request is determined and sent to the user terminal. That is, in this invention, when the subscription permission information of the MCS server is determined to be preset subscription permission information, the MCS server directly pushes the data acquisition link to the user terminal through the above steps through a preset message type push method. The user terminal only needs to access the data acquisition link to obtain the target data, simplifying the process. The terminal does not need to send a subscription request, reducing the number of communication times (the SIP subscription process between the UE and the server is reduced, and the two interactions of SUBSCRIBE and NOTIFY are deleted). The server automatically identifies and completes the push of user and group subscription data according to the registration and authorization status and service type, eliminating the need for multiple interactions between the UE and the MCS, thereby saving communication resources.

[0109] In addition, this invention extends the UE initialization response XML to carry an implicit subscription switch field, and is compatible with the current standard process, while also supporting the establishment and maintenance of implicit subscription relationships.

[0110] In addition, the present invention can also achieve the purpose of resource optimization, so that the terminal and server do not need to allocate resources for the subscription session, thereby reducing the resource consumption and occupation of the terminal and server, and at the same time avoiding message out-of-order.

[0111] In another implementation of the present invention, if the network management (O&M) or the terminal modifies the user subscription data and home group data through dynamic reorganization (i.e., performs MODIFY / DELETE User-Profile operation), that is, the aforementioned user subscription data or home group data changes, then it is necessary to push the updated user subscription data or home group data to the terminal.

[0112] Specifically, message push methods also include:

[0113] 1) After determining that the user subscription data of the user terminal has been modified, the configuration management service module queries whether the first subscription relationship exists.

[0114] 2) If it exists, send the contract data acquisition link to the user terminal.

[0115] Specifically, the CMS checks if an implicit subscription relationship exists, i.e., if a primary subscription relationship exists. If it does, it sends a link to retrieve the subscription data. This means a message is sent to the user's subscription data URL, notifying the terminal that the subscription data has changed.

[0116] 3) Receive a third data acquisition request when the user terminal accesses the contract data acquisition link, determine the updated user contract data corresponding to the third data acquisition request, and send the updated user contract data to the user terminal.

[0117] The terminal retrieves new user subscription data via HTTP. The specific process is similar to the process of obtaining user subscription data described above; please refer to the corresponding instructions above.

[0118] Furthermore, the data update method for the group affiliation is similar. Specifically, message push methods also include:

[0119] 1) After determining that the user terminal's group data has been modified, the group management service module queries whether the second subscription relationship exists;

[0120] 2) If it exists, send a group data retrieval link to the user terminal;

[0121] 3) Receive the fourth data acquisition request when the user terminal accesses the group data acquisition link, determine the updated home group data corresponding to the fourth data acquisition request, and send the updated home group data to the user terminal.

[0122] Specifically, refer to Figure 5 GMS queries whether an implicit subscription relationship, i.e. a second subscription relationship, exists. If it exists, it sends a message to push the group information data URL to notify the terminal that the group data has changed. The terminal pulls the new group information via HTTP. The specific process is similar to the above-mentioned process of obtaining the belonging group data. Please refer to the corresponding instructions above.

[0123] In practical applications, refer to Figure 6 If a change notification is not received by the UE due to poor network signal or other reasons, or if the 200 OK response information is lost, then if the following measures are taken... Figure 1 The push process in this embodiment involves a different approach. If an explicit subscription mechanism is used, network instability can lead to message loss or response timeouts causing the explicit subscription relationship in the SIP protocol stack to fail, preventing subsequent push notifications. In this embodiment, a transactional message is used, eliminating the need for a protocol stack-maintained subscription mechanism. The server only needs to know the UE's address to send multiple change notifications to the terminal. A single failed push does not affect subsequent push processes. In other words, due to the establishment of the first and second subscription relationships, a failed change push only affects the current push process; the implicit subscription relationship remains unaffected.

[0124] Subsequently, if the network signal is restored and the connection between the terminal and the server is restored, the implicit subscription relationship remains valid. The server initiates a new message to push to the terminal, and the terminal retrieves the latest subscription data and home group data via HTTP, ensuring the stability and reliability of the business functions.

[0125] In this embodiment, after the data is updated, a data update operation is performed, and anomaly protection is set to solve the problem that when the terminal and server networks are unstable, the explicit subscription relationship will fail due to message loss or response timeout, and subsequent change notifications cannot be pushed.

[0126] Optionally, based on the above-described message push method for MCS servers, another embodiment of the present invention provides a message push method applied to user terminals, referring to... Figure 7 The message push method includes:

[0127] S31. Receive a data acquisition link pushed by the MCS server through a preset message type push method. The data acquisition link is the authorization information of the user terminal obtained by the MCS server when it determines that the subscription permission information of the MCS server is the preset subscription permission information, and the corresponding business authorization type extracted from the authorization information.

[0128] S32. Send the data acquisition request when accessing the data acquisition link to the MCS server, so that the MCS server can determine the target data corresponding to the data acquisition request;

[0129] S33. Receive the target data sent by the MCS server.

[0130] Furthermore, the data retrieval request when accessing the data retrieval link is sent to the MCS server, so that the MCS server can determine the target data corresponding to the data retrieval request, including:

[0131] When accessing the contract data retrieval link, a first data retrieval request is sent to the MCS server so that the MCS server can determine the user contract data corresponding to the first data retrieval request.

[0132] When accessing the group data retrieval link, a second data retrieval request is sent to the MCS server so that the MCS server can determine the group data to which the second data retrieval request belongs.

[0133] Furthermore, it also includes:

[0134] The system receives a subscription data retrieval link sent by the MCS server. This subscription data retrieval link is sent by the configuration management service module in the MCS server when it determines that the user's subscription data on the user terminal has been modified, and the module queries whether a first subscription relationship exists.

[0135] When accessing the contract data acquisition link, a third data acquisition request is sent to the MCS server so that the MCS server can determine the updated user contract data corresponding to the third data acquisition request.

[0136] Receive the updated user subscription data sent by the MCS server.

[0137] Furthermore, it also includes:

[0138] Receive the group data retrieval link sent by the MCS server. The group data retrieval link is sent by the group management service module in the MCS server when it queries whether a second subscription relationship exists after the MCS server determines that the user terminal's belonging group data has been modified.

[0139] When accessing the group data retrieval link, a fourth data retrieval request is sent to the MCS server so that the MCS server can determine the updated attribution group data corresponding to the fourth data retrieval request.

[0140] Receive the updated home group data sent by the MCS server.

[0141] Furthermore, before receiving the data retrieval link pushed by the MCS server using a preset message type push method, it also includes:

[0142] An initialization configuration information retrieval request is sent to the MCS server so that the MCS server can determine the preset response information corresponding to the user information of the user terminal. The preset response information includes preset subscription permission information.

[0143] In this embodiment, when the subscription permission information of the MCS server is determined to be preset subscription permission information, the authorization information of the user terminal is obtained, and the service authorization type is extracted from the authorization information. The data acquisition link corresponding to the service authorization type is determined, and the data acquisition link is pushed to the user terminal through a preset message type push method. The data acquisition request when the user terminal accesses the data acquisition link is received, and the target data corresponding to the data acquisition request is determined and sent to the user terminal. That is, in this invention, when the subscription permission information of the MCS server is determined to be preset subscription permission information, the MCS server directly pushes the data acquisition link to the user terminal through the above steps through a preset message type push method. The user terminal only needs to access the data acquisition link to obtain the target data, eliminating the need for multiple interactions between the UE and the MCS, thereby saving communication resources.

[0144] It should be noted that the specific implementation process of each step in this embodiment is described in the corresponding descriptions in the above embodiments, and will not be repeated here.

[0145] Optionally, based on the above-described embodiments of the message push method applied to an MCS server, another embodiment of the present invention provides a message push device applied to an MCS server, referring to... Figure 8 The message push device includes:

[0146] The information acquisition module 11 is used to acquire the authorization information of the user terminal and extract the business authorization type from the authorization information when it is determined that the subscription permission information of the MCS server is the preset subscription permission information.

[0147] Data push module 12 is used to determine the data acquisition link corresponding to the business authorization type and push the data acquisition link to the user terminal through a preset message type push method;

[0148] The data sending module 13 is used to receive a data acquisition request when the user terminal accesses the data acquisition link, determine the target data corresponding to the data acquisition request, and send the target data to the user terminal.

[0149] Furthermore, when the information acquisition module 11 extracts the business authorization type from the authorization information, it is specifically used for:

[0150] The participant function service module in the MCS server parses the authorization information and extracts the business authorization type.

[0151] Furthermore, when determining the data acquisition link corresponding to the business authorization type, the data push module 12 is specifically used for:

[0152] The participating party function service module sends a pre-defined message type of contract data acquisition message to the configuration management service module in the MCS server. The contract data acquisition message includes the business authorization type and the user information of the user terminal.

[0153] The configuration management service module stores the first subscription relationship of the business authorization type and the user information, and determines the subscription data acquisition link corresponding to the subscription data acquisition message;

[0154] The participating party function service module sends a group data acquisition message of a preset message type to the group management service module in the MCS server. The group data acquisition message includes the business authorization type and the user information of the user terminal.

[0155] The group management service module stores the business authorization type and the second subscription relationship of the user information, and determines the group data retrieval link corresponding to the group data retrieval message.

[0156] Furthermore, the data sending module 13 is specifically used for:

[0157] The system receives a first data acquisition request from the user terminal when it accesses the contract data acquisition link, determines the user contract data corresponding to the first data acquisition request, and sends the user contract data to the user terminal.

[0158] The system receives a second data acquisition request from the user terminal when accessing the group data acquisition link, determines the belonging group data corresponding to the second data acquisition request, and sends the belonging group data to the user terminal.

[0159] Furthermore, it also includes:

[0160] The first determining module is used to query whether the first subscription relationship exists after determining that the user subscription data of the user terminal has been modified.

[0161] The first link sending module is used to send a subscription data acquisition link to the user terminal if it exists.

[0162] The contract information sending module is used to receive a third data acquisition request when the user terminal accesses the contract data acquisition link, determine the updated user contract data corresponding to the third data acquisition request, and send the updated user contract data to the user terminal.

[0163] Furthermore, it also includes:

[0164] The second determining module is used to, after determining that the user terminal's group data has been modified, have the group management service module query whether the second subscription relationship exists.

[0165] The second link sending module is used to send a group data acquisition link to the user terminal if it exists.

[0166] The attribution information sending module is used to receive a fourth data acquisition request when the user terminal accesses the group data acquisition link, determine the updated attribution group data corresponding to the fourth data acquisition request, and send the updated attribution group data to the user terminal.

[0167] Furthermore, it also includes:

[0168] The request receiving module is used to receive an initialization configuration information acquisition request sent by a user terminal, and determine the preset response information corresponding to the user information of the user terminal, wherein the preset response information includes preset subscription permission information.

[0169] In this embodiment, when the subscription permission information of the MCS server is determined to be preset subscription permission information, the authorization information of the user terminal is obtained, and the service authorization type is extracted from the authorization information. The data acquisition link corresponding to the service authorization type is determined, and the data acquisition link is pushed to the user terminal through a preset message type push method. The data acquisition request when the user terminal accesses the data acquisition link is received, and the target data corresponding to the data acquisition request is determined and sent to the user terminal. That is, in this invention, when the subscription permission information of the MCS server is determined to be preset subscription permission information, the MCS server directly pushes the data acquisition link to the user terminal through the above steps through a preset message type push method. The user terminal only needs to access the data acquisition link to obtain the target data, eliminating the need for multiple interactions between the UE and the MCS, thereby saving communication resources.

[0170] It should be noted that the specific implementation process of each module in this embodiment is described in the corresponding descriptions in the above embodiments, and will not be repeated here.

[0171] Optionally, based on the above-described embodiments of the message push method applied to a user terminal, another embodiment of the present invention provides a message push device applied to a user terminal, referring to... Figure 9 The message push device includes:

[0172] The link acquisition module 21 is used to receive a data acquisition link pushed by the MCS server through a preset message type push method. The data acquisition link is the authorization information of the user terminal obtained by the MCS server when it is determined that the subscription permission information of the MCS server is the preset subscription permission information, and the business authorization type extracted from the authorization information.

[0173] Request sending module 22 is used to send a data acquisition request when accessing the data acquisition link to the MCS server, so that the MCS server can determine the target data corresponding to the data acquisition request;

[0174] The data receiving module 23 is used to receive the target data sent by the MCS server.

[0175] Furthermore, the request sending module 22 is specifically used for:

[0176] When accessing the contract data retrieval link, a first data retrieval request is sent to the MCS server so that the MCS server can determine the user contract data corresponding to the first data retrieval request.

[0177] When accessing the group data retrieval link, a second data retrieval request is sent to the MCS server so that the MCS server can determine the group data to which the second data retrieval request belongs.

[0178] Furthermore, it also includes:

[0179] The first receiving module is used to receive the subscription data acquisition link sent by the MCS server. The subscription data acquisition link is sent by the configuration management service module in the MCS server when it determines that the user subscription data of the user terminal has been modified.

[0180] The first sending module is used to send a third data acquisition request when accessing the contract data acquisition link to the MCS server, so that the MCS server can determine the updated user contract data corresponding to the third data acquisition request.

[0181] The second receiving module is used to receive the updated user subscription data sent by the MCS server.

[0182] Furthermore, it also includes:

[0183] The third receiving module is used to receive the group data acquisition link sent by the MCS server. The group data acquisition link is sent by the group management service module in the MCS server when it queries the existence of a second subscription relationship after the MCS server determines that the user terminal's belonging group data has been modified.

[0184] The second sending module is used to send the fourth data acquisition request when accessing the group data acquisition link to the MCS server, so that the MCS server can determine the updated home group data corresponding to the fourth data acquisition request.

[0185] The fourth receiving module is used to receive the updated home group data sent by the MCS server.

[0186] Furthermore, it also includes:

[0187] The third sending module is used to send an initialization configuration information acquisition request to the MCS server so that the MCS server can determine the preset response information corresponding to the user information of the user terminal, and the preset response information includes preset subscription permission information.

[0188] In this embodiment, when the subscription permission information of the MCS server is determined to be preset subscription permission information, the authorization information of the user terminal is obtained, and the service authorization type is extracted from the authorization information. The data acquisition link corresponding to the service authorization type is determined, and the data acquisition link is pushed to the user terminal through a preset message type push method. The data acquisition request when the user terminal accesses the data acquisition link is received, and the target data corresponding to the data acquisition request is determined and sent to the user terminal. That is, in this invention, when the subscription permission information of the MCS server is determined to be preset subscription permission information, the MCS server directly pushes the data acquisition link to the user terminal through the above steps through a preset message type push method. The user terminal only needs to access the data acquisition link to obtain the target data, eliminating the need for multiple interactions between the UE and the MCS, thereby saving communication resources.

[0189] It should be noted that the specific implementation process of each module in this embodiment is described in the corresponding descriptions in the above embodiments, and will not be repeated here.

[0190] Optionally, based on the above-described embodiments of the message push method and apparatus, another embodiment of the present invention provides an electronic device, including: a memory and a processor;

[0191] The memory is used to store programs;

[0192] The processor calls the program and executes the message push method described above.

[0193] Optionally, based on the above-described embodiments of the message push method, apparatus, and electronic device, another embodiment of the present invention provides a readable storage medium storing a computer program thereon, which, when executed by a processor, implements the above-described message push method.

[0194] In this embodiment, when the subscription permission information of the MCS server is determined to be preset subscription permission information, the authorization information of the user terminal is obtained, and the service authorization type is extracted from the authorization information. The data acquisition link corresponding to the service authorization type is determined, and the data acquisition link is pushed to the user terminal through a preset message type push method. The data acquisition request when the user terminal accesses the data acquisition link is received, and the target data corresponding to the data acquisition request is determined and sent to the user terminal. That is, in this invention, when the subscription permission information of the MCS server is determined to be preset subscription permission information, the MCS server directly pushes the data acquisition link to the user terminal through the above steps through a preset message type push method. The user terminal only needs to access the data acquisition link to obtain the target data, eliminating the need for multiple interactions between the UE and the MCS, thereby saving communication resources.

[0195] The above description of the disclosed embodiments enables those 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 invention is not to 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

1. A message push method, characterized in that, Applied to MCS servers, the message push method includes: If it is determined that the subscription permission information of the MCS server is the preset subscription permission information, the authorization information of the user terminal is obtained, and the service authorization type is extracted from the authorization information; The preset subscription permission information is used to indicate support for implicit subscription operations; Determine the data acquisition link corresponding to the business authorization type, and push the data acquisition link to the user terminal through a preset message type push method; wherein, the preset message type push method is a MESSAGE message push method; The system receives a data acquisition request from the user terminal when accessing the data acquisition link, determines the target data corresponding to the data acquisition request, and sends the target data to the user terminal.

2. The message push method according to claim 1, characterized in that, The business authorization type is extracted from the authorization information, including: The participant function service module in the MCS server parses the authorization information and extracts the business authorization type.

3. The message push method according to claim 1, characterized in that, Determining the data retrieval link corresponding to the business authorization type includes: The participant function service module in the MCS server sends a subscription data acquisition message of a preset message type to the configuration management service module in the MCS server. The subscription data acquisition message includes the business authorization type and the user information of the user terminal. The configuration management service module stores the first subscription relationship of the business authorization type and the user information, and determines the subscription data acquisition link corresponding to the subscription data acquisition message; The participant function service module in the MCS server sends a group data acquisition message of a preset message type to the group management service module in the MCS server. The group data acquisition message includes the business authorization type and the user information of the user terminal. The group management service module stores the business authorization type and the second subscription relationship of the user information, and determines the group data retrieval link corresponding to the group data retrieval message.

4. The message push method according to claim 3, characterized in that, Receiving a data acquisition request from a user terminal when accessing the data acquisition link, determining the target data corresponding to the data acquisition request, and sending the target data to the user terminal, includes: The system receives a first data acquisition request from the user terminal when it accesses the contract data acquisition link, determines the user contract data corresponding to the first data acquisition request, and sends the user contract data to the user terminal. The system receives a second data acquisition request from the user terminal when accessing the group data acquisition link, determines the belonging group data corresponding to the second data acquisition request, and sends the belonging group data to the user terminal.

5. The message push method according to claim 3, characterized in that, Also includes: After determining that the user's subscription data on the user terminal has been modified, the configuration management service module queries whether the first subscription relationship exists. If it exists, a signing data acquisition link is sent to the user's terminal; The system receives a third data acquisition request from the user terminal when accessing the contract data acquisition link, determines the updated user contract data corresponding to the third data acquisition request, and sends the updated user contract data to the user terminal.

6. The message push method according to claim 3, characterized in that, Also includes: After determining that the user terminal's group data has been modified, the group management service module queries whether the second subscription relationship exists. If it exists, a group data retrieval link is sent to the user terminal; The system receives a fourth data acquisition request from the user terminal when accessing the group data acquisition link, determines the updated home group data corresponding to the fourth data acquisition request, and sends the updated home group data to the user terminal.

7. The message push method according to claim 1, characterized in that, Before determining that the subscription permission information of the MCS server is the preset subscription permission information, the process also includes: The system receives an initialization configuration information retrieval request sent by a user terminal and determines the preset response information corresponding to the user information of the user terminal. The preset response information includes preset subscription permission information.

8. A message push method, characterized in that, Applied to user terminals, the message push method includes: The system receives a data retrieval link pushed by the MCS server using a preset message type push method. This data retrieval link is used by the MCS server, after determining that its subscription permission information is preset subscription permission information, to obtain the user terminal's authorization information and extract the corresponding business authorization type from that information. The preset message type push method is a MESSAGE message push method. The preset subscription permission information is used to indicate support for implicit subscription operations. When accessing the data acquisition link, a data acquisition request is sent to the MCS server so that the MCS server can determine the target data corresponding to the data acquisition request; Receive the target data sent by the MCS server.

9. The message push method according to claim 8, characterized in that, When accessing the data retrieval link, a data retrieval request is sent to the MCS server, so that the MCS server can determine the target data corresponding to the data retrieval request, including: When accessing the contract data retrieval link, a first data retrieval request is sent to the MCS server so that the MCS server can determine the user contract data corresponding to the first data retrieval request. When accessing the group data retrieval link, a second data retrieval request is sent to the MCS server so that the MCS server can determine the group data to which the second data retrieval request belongs.

10. The message push method according to claim 8, characterized in that, Also includes: The system receives a subscription data retrieval link sent by the MCS server. This subscription data retrieval link is sent by the configuration management service module in the MCS server when it determines that the user's subscription data on the user terminal has been modified, and the module queries whether a first subscription relationship exists. When accessing the contract data acquisition link, a third data acquisition request is sent to the MCS server so that the MCS server can determine the updated user contract data corresponding to the third data acquisition request. Receive the updated user subscription data sent by the MCS server.

11. The message push method according to claim 8, characterized in that, Also includes: Receive the group data retrieval link sent by the MCS server. The group data retrieval link is sent by the group management service module in the MCS server when it queries whether a second subscription relationship exists after the MCS server determines that the user terminal's belonging group data has been modified. When accessing the group data retrieval link, a fourth data retrieval request is sent to the MCS server so that the MCS server can determine the updated attribution group data corresponding to the fourth data retrieval request. Receive the updated home group data sent by the MCS server.

12. The message push method according to claim 8, characterized in that, Before receiving the data retrieval link pushed by the MCS server using a preset message type push method, the following is also included: An initialization configuration information retrieval request is sent to the MCS server so that the MCS server can determine the preset response information corresponding to the user information of the user terminal. The preset response information includes preset subscription permission information.

13. An electronic device, characterized in that, include: Memory and processor; The memory is used to store programs; The processor calls the program and executes the message push method as described in any one of claims 1-7, or executes the message push method as described in any one of claims 8-12.

14. A readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the message push method as described in any one of claims 1-7, or executes the message push method as described in any one of claims 8-12.

Images