A satellite cluster terminal user information publishing and comment / like interaction system

Abstract

This invention discloses a satellite trunking terminal user information publishing and comment / like interaction system. After a satellite terminal forms a cluster social circle through online cluster grouping and adding friends, in addition to supporting one-call / group calling and real-time SMS services, it will also support value-added services such as terminal users publishing information to their group user circle and friend user circle, and receiving comments and likes. The terminal APP adds two communication sections, group activity and friend activity. Clicking on these sections displays information published by associated users, which can be in the form of SMS messages, data, or status emoticons. Users can comment or like these messages. Users can also actively publish information and receive comments and likes from other users. Associated information is exchanged bidirectionally between the satellite terminal and the ground station core network. The satellite trunking air interface data transmission path ensures the integrity and reliability of the interactive data, allowing users to publish information and comment / like simply by clicking to send to the satellite, adding new application functions to trunking communication.

Description

Technical Field

[0001] This invention belongs to the field of satellite communication, specifically relating to a satellite cluster terminal user information publishing and comment / like interaction system. Background Technology

[0002] A satellite mobile communication system refers to a system that uses the relay or switching functions of geostationary orbit communication satellites to connect mobile terminals (stations) within its coverage area to the core network of a ground gateway station (system) for service exchange to achieve mobile communication. When the services supported by the satellite mobile communication system are point-to-point voice and SMS services, we call them conventional services; when the services supported by the satellite mobile communication system are point-to-multipoint voice and SMS services, we call them trunking services.

[0003] Satellite trunking communication is a one-to-many communication system among a group of satellite users, effectively improving communication efficiency. In emergencies, satellite trunking communication can provide rapid call connections between satellite users for command and control. Satellite mobile communication has advantages such as wide coverage, minimal impact from the ground environment, and suitability for field communication, leading to its increasingly widespread use.

[0004] The essence of satellite trunking supporting real-time communication is that, through trunking call signaling, trunking users share circuit-type service channels. The trunking gateway arbitrates the competition among users requesting to speak, allowing only one user to occupy the uplink service channel at a time, while all other users listen to the trunking downlink service channel. The gateway then switches the uplink voice to the downlink channel, thus realizing trunking group call or individual call communication with shared channels.

[0005] Within the satellite terminal, the cluster app gradually forms four social circles by users continuously creating or joining cluster groups and inviting or being invited to add friends:

[0006] (1) Cluster group call circle

[0007] Each satellite cluster mobile app can initiate the creation of a cluster group. The user creating the group gives it a name consisting of Chinese characters or English letters. The cluster core network selects a unique group number for the new cluster group. The user creating the group adds or deletes group members using the mobile station's international subscriber number (MSISDN), forming a group member list. For each cluster call, the core network obtains the satellite number and beam number currently registered by each group member through the user registration process. The call is made using the group number, and the core network forwards the call to all registered beams in that group, thus realizing the cluster group call service function.

[0008] (2) Cluster single call circle

[0009] Each satellite cluster's mobile app allows users to easily invite friends to use each other's MSISDN numbers. Once the invited user accepts the invitation, the cluster core network obtains two friend numbers and adds them to each user's Address Book. In addition to supporting one-on-one calls between users, the app also supports status and data services. Friends can check the other's online status before a call, avoiding unnecessary failed calls and further enhancing the convenience of communication between users.

[0010] (3) Group user circle

[0011] Each satellite constellation's mobile app can send messages to all its constellation users with a single click. These messages include status information, SMS messages, and data messages, enabling large-scale group message distribution. User profile cards can also be collected and distributed among group users, providing all group users with convenient identification information such as avatars, names, numbers, and notes.

[0012] (4) Friend user circle

[0013] Each satellite constellation mobile app can send messages to all its friends with a single click, including status information, SMS messages, and data messages, enabling large-scale distribution of friend information. User profile cards can also be collected and distributed among friends, providing convenient identification information such as profile pictures, names, phone numbers, and notes.

[0014] Satellite trunking terminal user information dissemination and interaction (such as commenting and liking) occur within group user circles and friend user circles. The group user circle comprises all users in the trunking groups the terminal participates in, while the friend user circle consists of all trunking-specific call contacts in the terminal's phonebook. For trunking professionals, the group user circle is closely related to their work scope; for non-trunking professionals, the friend user circle is closely related to their social life. Both user circles have distinct social characteristics.

[0015] Existing satellite or terrestrial trunking communication systems are unable to provide the aforementioned information publishing and comment / like functions for user terminals due to various reasons such as system architecture, technology, and demand research. Since this involves trunking circuit data services and core network layout, developing this function can provide a useful exploratory example for trunking network design. Summary of the Invention

[0016] To address the aforementioned problems, the present invention aims to provide a satellite cluster terminal user information publishing and comment / like interaction system.

[0017] The specific technical solution for achieving the objective of this invention is as follows:

[0018] A satellite trunking terminal user information publishing and comment / like interaction system includes a status server (STS), a satellite channel controller (SCC), a trunking switching center (MSC Server), a circuit data support node (CDSN), a terminal not arrived data server (NDS), a data message server (DMS), an HLR / VLR server, a group call register (GCR), and a subscriber recovery server (SRS).

[0019] Among them, the information published and comments / likes by satellite trunk terminal users are transmitted to the data message server (DMS) or status server (STS) through the trunk exchange center (MSCServer), circuit data support node (CDSN), or satellite channel controller (SCC).

[0020] The Data Message Server (DMS) or Status Server (STS) transmits information to the terminal that has not yet reached the Data Server (NDS).

[0021] Satellite cluster terminal users download relevant information from the data server NDS, which is not accessible to the terminal, through the circuit data support node CDSN;

[0022] The HLR / VLR server is used to provide group list information query services for information distribution to terminals that have not reached the NDS data server;

[0023] The group call register (GCR) is used to provide a group member list information query service for information distribution when the terminal has not arrived at the data server (NDS).

[0024] The subscriber data recovery server (SRS) is used to provide a one-call user friend list information query service for terminals that have not reached the data server (NDS).

[0025] Furthermore, the information published and the comments / likes posted by the satellite cluster terminal users include:

[0026] Group Dynamics: Information posting and interaction (comments, likes, etc.) within a group user circle based on cluster group call users;

[0027] Friend Activity: Information posting, commenting, and liking interactions based on the friend circle of a user in a cluster-based one-call user;

[0028] The group user circle is the set of users in all cluster groups that the satellite cluster terminal user participates in, and the friend user circle is the set of all cluster-call friends in the phone book of the satellite cluster terminal user.

[0029] Furthermore, the types of information published and comments / likes by the satellite cluster terminal users include cluster SMS information publication, cluster data information publication, and cluster status message information publication;

[0030] The satellite cluster text messages are Chinese characters or symbols expressed in no more than 140 bytes;

[0031] The cluster data consists of short texts, encoded voice, or compressed graphic images expressed in no more than 10KB.

[0032] The cluster status message is encoded information of no more than 55 bits.

[0033] Furthermore, the process for publishing satellite cluster terminal user information and interacting with comments and likes includes:

[0034] Uplink transmission of satellite cluster terminal user information publishing, comments, and likes;

[0035] The transit storage and transshipment of information distributed through the ground station core network;

[0036] Satellite cluster terminal users can access published information, comments, and likes via downlink.

[0037] Furthermore, the uplink transmission path for the satellite cluster terminal user information publishing and commenting / liking includes:

[0038] Satellite trunking terminal users use trunking SMS to publish information. The publishing path of the trunking SMS is, in order, the satellite trunking terminal MES, the core network MSC Server, and the data message server DMS.

[0039] Satellite trunk terminal users use trunk data to publish information. The publishing path of the trunk data is, in sequence, the satellite trunk terminal MES, the circuit data support node CDSN, and the data message server DMS.

[0040] Satellite trunking terminal users publish information using trunking status messages. The publication path of these trunking status messages is sequentially: satellite trunking terminal MES, satellite channel controller SCC, and status server STS.

[0041] Furthermore, the uplink transmission process for publishing, commenting, and liking information for satellite cluster terminal users includes:

[0042] (1) The information publisher edits text, short articles, records a voice message, or pastes a compressed image in the group dynamics or friend dynamics of the satellite trunking terminal, starts the information publishing, and clicks send:

[0043] 1) Encapsulate the data to be sent with a 9-bit unique data identifier, Data ID, and fill in the source and destination addresses of the data message. Since the destination address is a group user circle or friend user circle, use the user circle identifier instead of the destination address; fill in the data attribute parameters so that the receiver can parse and form the published data.

[0044] 2) Check the length of the data to be sent. If the length is less than 140 bytes, use the SMS sending process to send the information to the Cluster Exchange Center (MSC) Server. If the data length is more than 140 bytes but less than 10KB, use the data sending process to send the information to the Circuit Data Support Node (CDSN). If the data length is more than 10KB, prompt the user that the data is too long to send and ask the user to re-edit the data.

[0045] 3) When SMS sending is selected, after the satellite trunking terminal obtains dedicated channel resources from the gateway station via satellite, it uses the dedicated accompanying control channel DACCH to submit the SMS to the trunking exchange center MSC Server in the accompanying signaling mode. The trunking exchange center MSC Server then forwards it to the data message server DMS.

[0046] When data transmission is selected, the satellite trunk terminal obtains dedicated channel resources from the gateway station via satellite, and then uses the dedicated service channel DTCH to submit the published data to the Circuit Data Support Node (CDSN) in the form of media data transmission. The Circuit Data Support Node (CDSN) then forwards the data to the Data Message Server (DMS).

[0047] (2) When commenting on a post, the user selects a post from another user's group feed or friend feed in the terminal app and comments on it. The comment is a text or string of characters. To post the comment, click "send".

[0048] 1) Encapsulate the comment data to be sent with a 9-bit unique data identifier (Data ID) for the comment information. Fill in the source and destination addresses of the data message. Since the destination address is a group user circle or friend user circle, use the user circle identifier instead of the destination address. Fill in the data attribute parameter as the comment information. The comment information parameter carries the MSISDN number of the user being commented on so that the receiver can parse it to form the comment posting data.

[0049] 2) Check the length of the comment data to be sent. If the length is less than 140 bytes, use the SMS sending process to send the information to the Cluster Exchange Center (MSC) Server. If the comment data length is more than 140 bytes but less than 10KB, use the data sending process to send the information to the Circuit Data Support Node (CDSN). If the comment data length is more than 10KB, prompt the user that the comment data is too long to send and ask the user to re-edit the data.

[0050] 3) When SMS sending is selected, after the satellite trunk terminal obtains dedicated channel resources from the gateway station via satellite, it uses the dedicated associated control channel DACCH to submit the published comment SMS to the MSC Server in the associated signaling manner. The MSC Server then forwards it to the data message server DMS.

[0051] When data transmission is selected, the satellite trunk terminal obtains dedicated channel resources from the gateway station via satellite, and then uses the dedicated service channel DTCH to submit the published data to the CDSN in the form of media data transmission. The CDSN then forwards it to the data message server DMS.

[0052] (3) The information publisher sends a status emoticon or likes the received information in the group dynamics or friend dynamics section, and clicks send:

[0053] 1) Edit a RACH status message for the status emoticon to be sent. The status message carries the sender's MSISDN number, the encoding number of the target user group user circle or friend user circle and the emoticon encoding, as well as the status message type identifier and status message subtype identifier, totaling 55 bits of status message. Send the RACH to the satellite using the random access procedure.

[0054] 2) Edit a RACH status message for the upcoming like message. The status message carries the MSISDN number of the liked, the Data ID of the publisher of the liked, the target user group user circle or friend user circle identifier, and the status message type identifier and status message subtype identifier, totaling 55 bits of status message. Send the RACH to the satellite using a random access procedure.

[0055] 3) After the status emoticon or like message sent by the satellite cluster terminal via RACH is received by the gateway station's satellite channel controller (SCC), it is submitted to the status server (STS).

[0056] Furthermore, the transit storage and transfer of information distribution in the ground station core network includes information storage and forwarding between functional entities within the core network, as well as the distribution and transit caching of information in the data server NDS before the terminal arrives.

[0057] Furthermore, the information storage and forwarding between functional entities within the core network includes:

[0058] (1) Store-and-forwarding of the core network data message server (DMS):

[0059] 1) The core network data message server (DMS) receives user-posted information and comment SMS messages from the cluster exchange center (MSC) server and stores them according to the sender's MSISDN number to form a history of SMS messages, so as to provide subsequent operation query services;

[0060] 2) The core network data message server (DMS) receives user-posted information and comment data from the circuit data support node (CDSN), stores it according to the sender's MSISDN number, and forms a historical record of the data to provide subsequent operation query services;

[0061] 3) After storing the data according to the sender's MSISDN number, the core network data message server (DMS) forwards the information according to the destination address of the SMS or data. Since the destination address is the user's circle address, the information is forwarded to the terminal before it reaches the data server (NDS) according to the forwarding strategy.

[0062] (2) Store-and-forward functionality of the core network state server (STS):

[0063] 1) After receiving the RACH status message sent by the user from the Satellite Channel Controller (SCC), the Core Network Status Server (STS) stores it according to the 37-bit address carried by the RACH to form a historical record of the RACH, so as to provide subsequent status query services.

[0064] 2) After storing the 37-bit address carried by RACH, the core network state server STS decodes the state messages and forwards the user's emoticon and like information to the NDS (Network Data Server) before the terminal arrives.

[0065] Furthermore, the distribution and relay caching of the information before it reaches the data server NDS includes:

[0066] (1) The terminal has not reached the data server. The NDS receives the forwarded status message from the status server STS, and receives the forwarded SMS or data from the DMS server. It can view the source address and user circle identifier of the information.

[0067] (2) If the user circle is a group user, the terminal does not reach the data server NDS. It queries the HLR / VLR server for the group list of this user using the information source address MSISDN number. After obtaining the group list, it queries the group call register GCR one by one for the member list of each group. The query results are merged to form an NDS distribution list that contains all users and appears only once.

[0068] (3) If the user is a friend user, the terminal does not reach the data server NDS. The terminal queries the subscriber recovery server SRS for the user's one-call friend list using the information source address MSISDN number. After obtaining the list, an NDS distribution list is formed.

[0069] (4) If the terminal does not arrive at the data server, the NDS will package and cache the status, SMS or data of the list users in the Packingbox or Container according to the distribution list, modify the NDR report of the list users, and broadcast the NDR status notification to the relevant users through the cluster exchange center MSC Server, and wait for the users to obtain the data.

[0070] Furthermore, the process for satellite cluster terminal users to obtain published information and comments / likes via downlink includes:

[0071] (1) Group users or friends can obtain their NDR reports through the following means:

[0072] 1) Online users hear the NDR status notification pushed by the NDS (Network Data Server) indicating that the terminal has not arrived at the data server and that the NDS has cached its terminal's data arrival status.

[0073] 2) Offline users did not hear the NDR status notification pushed by the terminal not arriving at the data server NDS. After they powered on and connected to the network, they initiated an NDR query and learned that the terminal had not arrived at the data server NDS had cached its terminal not arriving at the data server status.

[0074] (2) Group users or friends initiate data download after receiving the NDR report:

[0075] 1) After obtaining his own NDR status report, the user learns that the terminal has not arrived at the data server. The NDS caches his terminal's non-arrival data and initiates the data download process.

[0076] 2) After the terminal obtains dedicated channel resources from the gateway station via satellite, it uses the dedicated service channel DTCH to submit the terminal's download request for the NDS (Network Data Support Node) to the Circuit Data Support Node (CDSN) via data call signaling in the form of media data transmission. The CDSN then forwards the request to the NDS, which is not yet reached by the terminal. The NDS then downloads the user's cached data to the requesting terminal using the data cargo transfer protocol through the CDSN.

[0077] 3) After the terminal confirms that it has received the data downloaded from the NDS (Network Data Server), the NDS will clear the NDR (Network Data Report Register) and the user data buffer, and wait for the user to cache the data next time.

[0078] 4) After the terminal confirms that it has received the NDS data downloaded from the terminal's non-reaching data server, it initiates the satellite link release process. After the process ends, the terminal returns to the idle state, unpacks the data downloaded from the NDS server, and transfers the data to the corresponding processing program one by one, submitting it to the UI for display.

[0079] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0080] Satellite trunking communication is essentially narrowband communication. In existing narrowband communication systems, the main design goal is to provide real-time voice group calling and group SMS services. There is a lack of support for non-real-time services based on data services. Especially in the satellite trunking usage environment, since users are often unable to be online via satellite, providing them with non-real-time trunking services has become a key focus for developers.

[0081] This invention enables satellite terminals to form social circles through online clustering and adding friends. In addition to supporting individual and group calls and real-time SMS services, the system also supports value-added services such as users publishing information and receiving comments and likes to their group and friend circles. The terminal cluster app adds two communication sections: group activity and friend activity. Clicking these sections displays information posted by associated users, in the form of SMS messages, data, or status emoticons. Users can comment or like; they can also proactively publish information and receive comments and likes from other users. Associated information interacts bidirectionally between the satellite terminal and the ground station core network. The satellite cluster air interface data transmission path must ensure the integrity and reliability of the interactive data, allowing users to publish information and comment / like simply by clicking to send to the satellite, adding new application functions to cluster communication.

[0082] This invention provides users with a new means of publishing information and commenting and liking, especially since the published information can be widely known by all users in the user's group and circle of friends, and users do not need to be online at all times, which brings convenience to users.

[0083] For ordinary users, the system provides a convenient means for sharing and exchanging information among friends; for professional users, the system provides a new way for information distribution and aggregation in organized groups of users, such as command and dispatch, intelligence sharing, plan issuance, and task handling, which can effectively improve the communication efficiency and reliability of satellite constellations.

[0084] The present invention will be further described below with reference to specific embodiments. Attached Figure Description

[0085] Figure 1This is a schematic diagram of the architecture of the satellite cluster terminal user information publishing, commenting, and liking interaction system of the present invention.

[0086] Figure 2 This is a schematic diagram illustrating the NDS server storage structure and its association with other service entities in the core network according to the present invention.

[0087] Figure 3 This invention provides an information structure for user-generated content, comments, and likes.

[0088] Figure 4 This is a schematic diagram illustrating the user-submitted information and comment SMS submission and system distribution process of the present invention.

[0089] Figure 5 This is a schematic diagram illustrating the user-submitted information and comment data submission and system distribution process of the present invention.

[0090] Figure 6 This is a schematic diagram illustrating the user-submitted information and "like" status submission and system distribution process of the present invention.

[0091] Figure 7 This invention provides a schematic diagram illustrating the process by which users obtain published information and comments / likes. Detailed Implementation

[0092] Example

[0093] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. 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.

[0094] As indicated in this application and claims, unless the context clearly indicates otherwise, the words "a," "an," "an," and / or "the" do not specifically refer to the singular and may also include the plural. Generally speaking, the terms "comprising" and "including" only indicate the inclusion of explicitly identified steps and elements, which do not constitute an exclusive list, and the method or apparatus may also include other steps or elements.

[0095] Unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps described in these embodiments do not limit the scope of this application. It should also be understood that, for ease of description, the dimensions of the various parts shown in the drawings are not drawn to actual scale. Techniques, methods, and devices known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and devices should be considered part of the specification. In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values. It should be noted that similar reference numerals and letters in the following drawings denote similar items; therefore, once an item is defined in one drawing, it need not be further discussed in subsequent drawings.

[0096] The architecture of the satellite trunking terminal user information publishing and comment / like interaction system is as follows: A Circuit Data Supporting Node (CDSN) is deployed in the existing satellite mobile communication system ground station; a State Server (STS) and a Non-Delivered Data Server (NDS) are deployed in the core network; and together with the existing trunking core network switching center entity MSC Server and Data Message Server (DMS), it provides support services for the newly added functions of the terminal user information publishing and comment / like interaction system, such as information reporting, storage, group or friend distribution, and user download.

[0097] In the existing satellite mobile communication system ground stations, the core network adds a satellite cluster subscriber data recovery function entity, "Subscriber Data Recovery Server (SRS)". The SRS communicates with other service function entities through the internal IP network of the gateway station to realize terminal data recovery services. The SRS server stores a friend address book for each user and provides a friend MSISDN number list query service when the NDS server distributes friend user information.

[0098] To enable satellite trunking terminal user information publishing and comment / like interaction functions, the most important consideration is that the core network can remember the group contacts and friend contacts of each trunking user. This data also needs to be dynamically updated based on user additions and deletions during usage. The core network entities associated with remembering group contacts are the HLR / VLR and the Group Call Register (GCR), while the core network functional entity for remembering friend contacts is the Subscriber Data Recovery Server (SRS).

[0099] In the core network of the cluster, the entity that receives and processes SMS messages and data from the sender is the Data Message Server (DMS), and the entity that executes the posting and commenting of user SMS messages and data is the DMS. The entity that receives and processes user status and likes from the sender is the Status Server (STS), and the entity that executes the posting and liking of user status is the STS. The entity that distributes and processes user SMS messages, data, status, and likes to the receiving user is the Terminal Not Received Data Server (NDS), and the NDS plays a very important role as a relay service entity for this function.

[0100] The transmission service entity for cluster users to upload or download data to the core network is the Circuit Data Support Node (CDSN), and the service entity for cluster users to send and receive SMS messages to the core network is the Mobile Switching Center Server (MSC Server).

[0101] The role of the CDSN entity is as follows: On the access network side, using the existing voice service channel time-slot transmission method, each time-slot voice payload is replaced with a data payload as a data piece. Each data piece undergoes transmission verification. Verified data pieces are assembled together to form a data frame, and each data frame is then subjected to frame verification again. If a fragment verification error occurs during transmission, the receiving end instructs the sending end to retransmit the erroneous fragment. The retransmission mechanism uses a sliding window fragment reception Bitmap error identification method to ensure that each fragment arrives correctly at the receiving end. The receiving end assembles the fragments to obtain a data segment, or data frame. If the data frame verification is correct, it is submitted to the application; if the data frame verification is incorrect, the data frame is retransmitted until it is correct.

[0102] NDS, acting as a transit service entity, executes the satellite cluster data cargo transfer protocol, treating the transferred data as cargo to be distributed. Each piece of cargo requires packaging: cargo with fewer than 255 bytes is placed in a packing box for storage and transfer; cargo with more than 255 but less than 1565 bytes is placed in a container for storage and transfer; and cargo with more than 1565 bytes is placed in multiple containers for storage and transfer. Each package must be labeled with its byte length and the type of data used for processing, facilitating sorting and application integration.

[0103] With the circuit data support node transmission protocol and the data cargo transfer protocol carried on top of it, a reliable application data transmission path is established between the terminal and the core network application function service entity.

[0104] The core network functional entities and satellite terminals together form a satellite cluster terminal user information publishing, commenting, and liking interaction system.

[0105] Combination Figure 1The satellite trunking terminal user information publishing and comment / like interaction system provided in this solution includes a status server STS, a satellite channel controller SCC, a trunking exchange center MSC Server, a circuit data support node CDSN, a terminal not arrived data server NDS, a data message server DMS, an HLR / VLR server, a group call register GCR, and a subscriber recovery server SRS.

[0106] Combination Figure 1 and Figure 2 The diagram illustrates the NDS storage structure of the terminal not reaching the data server and its association with other service entities in the core network. The NDS, together with other associated service entities, jointly completes the publication of terminal user information and the acquisition of comments and likes, realizing information reporting, extraction, collection, caching, container assembly, and data download, including:

[0107] CDSN (Circuit Data Support Node): The Circuit Data Support Node is the bearer entity that transmits published and commented information submitted by end users to the core network; NDS can obtain query and download services for user-published information and comment likes through the CDSN's data frame interface;

[0108] SCC (Satellite Channel Control) is an access network entity that provides the function of reporting the MSISDN publication status and approval information from RACHInformation to the STS server.

[0109] DMS (Data Message Server) is a core network entity that provides storage and forwarding services for user-posted and commented SMS messages or data to NDS.

[0110] STS (State Server) is a core network entity that provides storage and forwarding services to NDS for user-posted status and like information.

[0111] The Subscriber Recovery Server (SRS) is a core network entity that provides friend list and address book query services for NDS user information distribution.

[0112] Among them, the information published and comments / likes by satellite trunk terminal users are transmitted to the data message server (DMS) or status server (STS) through the trunk exchange center (MSCServer), circuit data support node (CDSN), or satellite channel controller (SCC).

[0113] The Data Message Server (DMS) or Status Server (STS) transmits information to the terminal that has not yet reached the Data Server (NDS).

[0114] Satellite cluster terminal users download relevant information from the data server NDS, which is not accessible to the terminal, through the circuit data support node CDSN;

[0115] The HLR / VLR server is used to provide information distribution group list information query service for terminals that have not reached the data server NDS; the information distribution entity NDS can query the group number list of the cluster group corresponding to the satellite terminal recorded in the HLR / VLR through the MSISDN number of the received MES.

[0116] The Group Call Register (GCR) is used to provide a group member list information query service for information distribution when the terminal fails to reach the NDS data server; the SMS information sent by the terminal is submitted to the DMS server through the in-line signaling bearer of the MSC Server, and the MSC Server can send a Terminal Failed Data Report (NDR) broadcast notification to the user according to the NDS request.

[0117] The subscriber data recovery server (SRS) is used to provide a one-call user friend list information query service for terminals that have not reached the data server (NDS).

[0118] The interfaces between NDS and other functional entities in the core network uniformly adopt the IP network interface protocol.

[0119] Both NDS data download and terminal data reporting to DMS are performed via a data cargo transfer protocol executed throughout the entire link between the satellite terminal and the CDSN. The data cargo transfer protocol is carried over the CDSN circuit data support node transmission protocol.

[0120] The information published and comments / likes by the satellite cluster terminal users include:

[0121] Group Dynamics: Information posting and interaction (comments, likes, etc.) within a group user circle based on cluster group call users;

[0122] Friend Activity: Information posting, commenting, and liking interactions based on the friend circle of a user in a cluster-based one-call user;

[0123] The method of implementation is to add two communication sections to the user terminal cluster APP;

[0124] The group user circle is the set of users in all cluster groups that the satellite cluster terminal user participates in, and the friend user circle is the set of all cluster-call friends in the phone book of the satellite cluster terminal user.

[0125] The types of information published and comments / likes by satellite cluster terminal users include cluster SMS information publication, cluster data information publication, and cluster status message information publication.

[0126] The satellite cluster text messages are Chinese characters or symbols expressed in no more than 140 bytes;

[0127] The cluster data consists of short texts, encoded voice, or compressed graphic images expressed in no more than 10KB.

[0128] The cluster status message is encoded information of no more than 55 bits.

[0129] More specifically, the process for publishing and interacting with user comments and likes on satellite cluster terminals includes:

[0130] Uplink transmission of satellite cluster terminal user information publishing, comments, and likes;

[0131] Its methods include:

[0132] Satellite trunking terminal users use trunking SMS to publish information. The publishing path of the trunking SMS is, in order, the satellite trunking terminal MES, the core network MSC Server, and the data message server DMS.

[0133] Satellite trunk terminal users use trunk data to publish information. The publishing path of the trunk data is, in sequence, the satellite trunk terminal MES, the circuit data support node CDSN, and the data message server DMS.

[0134] Satellite trunking terminal users publish information using trunking status messages. The publication path of these trunking status messages is sequentially: satellite trunking terminal MES, satellite channel controller SCC, and status server STS.

[0135] Combination Figure 3 The uplink transmission process includes:

[0136] (1) The information publisher edits text, short articles, records a voice message, or pastes a compressed image in the group dynamics or friend dynamics of the satellite trunking terminal, starts the information publishing, and clicks send:

[0137] 1) Encapsulate the data to be sent with a 9-bit unique data identifier, Data ID, and fill in the source and destination addresses of the data message. Since the destination address is a group user circle or friend user circle, use the user circle identifier instead of the destination address; fill in the data attribute parameters so that the receiver can parse and form the published data.

[0138] 2) Check the length of the data to be sent. If the length is less than 140 bytes, use the SMS sending process to send the information to the Cluster Exchange Center (MSC) Server. If the data length is more than 140 bytes but less than 10KB, use the data sending process to send the information to the Circuit Data Support Node (CDSN). If the data length is more than 10KB, prompt the user that the data is too long to send and ask the user to re-edit the data.

[0139] 3) When SMS sending is selected, after the satellite trunking terminal obtains dedicated channel resources from the gateway station via satellite, it uses the dedicated accompanying control channel DACCH to submit the SMS to the trunking exchange center MSC Server in the accompanying signaling mode. The trunking exchange center MSC Server then forwards it to the data message server DMS.

[0140] When data transmission is selected, the satellite trunk terminal obtains dedicated channel resources from the gateway station via satellite, and then uses the dedicated service channel DTCH to submit the published data to the Circuit Data Support Node (CDSN) in the form of media data transmission. The Circuit Data Support Node (CDSN) then forwards the data to the Data Message Server (DMS).

[0141] (2) When commenting on a post, the user selects a post from another user's group feed or friend feed in the terminal app and comments on it. The comment is a text or string of characters. To post the comment, click "send".

[0142] 1) Encapsulate the comment data to be sent with a 9-bit unique data identifier (Data ID) for the comment information. Fill in the source and destination addresses of the data message. Since the destination address is a group user circle or friend user circle, use the user circle identifier instead of the destination address. Fill in the data attribute parameter as the comment information. The comment information parameter carries the MSISDN number of the user being commented on so that the receiver can parse it to form the comment posting data.

[0143] 2) Check the length of the comment data to be sent. If the length is less than 140 bytes, use the SMS sending process to send the information to the Cluster Exchange Center (MSC) Server. If the comment data length is more than 140 bytes but less than 10KB, use the data sending process to send the information to the Circuit Data Support Node (CDSN). If the comment data length is more than 10KB, prompt the user that the comment data is too long to send and ask the user to re-edit the data.

[0144] 3) When SMS sending is selected, after the satellite trunk terminal obtains dedicated channel resources from the gateway station via satellite, it uses the dedicated associated control channel DACCH to submit the published comment SMS to the MSC Server in the associated signaling manner. The MSC Server then forwards it to the data message server DMS.

[0145] When data transmission is selected, the satellite trunk terminal obtains dedicated channel resources from the gateway station via satellite, and then uses the dedicated service channel DTCH to submit the published data to the CDSN in the form of media data transmission. The CDSN then forwards it to the data message server DMS.

[0146] (3) The information publisher sends a status emoticon or likes the received information in the group dynamics or friend dynamics section, and clicks send:

[0147] 1) Edit a RACH status message for the status emoticon to be sent. The status message carries the sender's MSISDN number, the encoding number of the target user group user circle or friend user circle and the emoticon encoding, as well as the status message type identifier and status message subtype identifier, totaling 55 bits of status message. Send the RACH to the satellite using the random access procedure.

[0148] 2) Edit a RACH status message for the upcoming like message. The status message carries the MSISDN number of the liked, the Data ID of the publisher of the liked, the target user group user circle or friend user circle identifier, and the status message type identifier and status message subtype identifier, totaling 55 bits of status message. Send the RACH to the satellite using a random access procedure.

[0149] 3) After the status emoticon or like message sent by the satellite cluster terminal via RACH is received by the gateway station's satellite channel controller (SCC), it is submitted to the status server (STS).

[0150] The relay storage and transfer of information distribution in the ground station core network includes information storage and forwarding between functional entities within the core network, as well as the distribution and relay caching of information in the data server NDS before the terminal arrives.

[0151] The information storage and forwarding between functional entities within the core network includes:

[0152] (1) Store-and-forwarding of the core network data message server (DMS):

[0153] 1) The core network data message server (DMS) receives user-posted information and comment SMS messages from the cluster exchange center (MSC) server and stores them according to the sender's MSISDN number to form a history of SMS messages, so as to provide subsequent operation query services;

[0154] 2) The core network data message server (DMS) receives user-posted information and comment data from the circuit data support node (CDSN), stores it according to the sender's MSISDN number, and forms a historical record of the data to provide subsequent operation query services;

[0155] 3) After storing the data according to the sender's MSISDN number, the core network data message server (DMS) forwards the information according to the destination address of the SMS or data. Since the destination address is the user's circle address, the information is forwarded to the terminal before it reaches the data server (NDS) according to the forwarding strategy.

[0156] (2) Store-and-forward functionality of the core network state server (STS):

[0157] 1) After receiving the RACH status message sent by the user from the Satellite Channel Controller (SCC), the Core Network Status Server (STS) stores it according to the 37-bit address carried by the RACH to form a historical record of the RACH, so as to provide subsequent status query services.

[0158] 2) After storing the 37-bit address carried by RACH, the core network state server STS decodes the state messages and forwards the user's emoticon and like information to the NDS (Network Data Server) before the terminal arrives.

[0159] The distribution and relay caching of the information before it reaches the data server NDS at the terminal includes:

[0160] (1) The terminal has not reached the data server. The NDS receives the forwarded status message from the status server STS, and receives the forwarded SMS or data from the DMS server. It can view the source address and user circle identifier of the information.

[0161] (2) If the user circle is a group user, the terminal does not reach the data server NDS. It queries the HLR / VLR server for the group list of this user using the information source address MSISDN number. After obtaining the group list, it queries the group call register GCR one by one for the member list of each group. The query results are merged to form an NDS distribution list that contains all users and appears only once.

[0162] (3) If the user is a friend user, the terminal does not reach the data server NDS. The terminal queries the subscriber recovery server SRS for the user's one-call friend list using the information source address MSISDN number. After obtaining the list, an NDS distribution list is formed.

[0163] (4) If the terminal does not arrive at the data server, the NDS will package and cache the status, SMS or data of the list users in the Packingbox or Container according to the distribution list, modify the NDR report of the list users, and broadcast the NDR status notification to the relevant users through the cluster exchange center MSC Server, and wait for the users to obtain the data.

[0164] Satellite cluster terminal users can access published information, comments, and likes via downlink:

[0165] (1) Group users or friends can obtain their NDR reports through the following means:

[0166] 1) Online users hear the NDR status notification pushed by the NDS (Network Data Server) indicating that the terminal has not arrived at the data server and that the NDS has cached its terminal's data arrival status.

[0167] 2) Offline users did not hear the NDR status notification pushed by the terminal not arriving at the data server NDS. After they powered on and connected to the network, they initiated an NDR query and learned that the terminal had not arrived at the data server NDS had cached its terminal not arriving at the data server status.

[0168] (2) Group users or friends initiate data download after receiving the NDR report:

[0169] 1) After obtaining his own NDR status report, the user learns that the terminal has not arrived at the data server. The NDS caches his terminal's non-arrival data and initiates the data download process.

[0170] 2) After the terminal obtains dedicated channel resources from the gateway station via satellite, it uses the dedicated service channel DTCH to submit the terminal's download request for the NDS (Network Data Support Node) to the Circuit Data Support Node (CDSN) via data call signaling in the form of media data transmission. The CDSN then forwards the request to the NDS, which is not yet reached by the terminal. The NDS then downloads the user's cached data to the requesting terminal using the data cargo transfer protocol through the CDSN.

[0171] 3) After the terminal confirms that it has received the data downloaded from the NDS (Network Data Server), the NDS will clear the NDR (Network Data Report Register) and the user data buffer, and wait for the user to cache the data next time.

[0172] 4) After the terminal confirms that it has received the NDS data downloaded from the terminal's non-reaching data server, it initiates the satellite link release process. After the process ends, the terminal returns to the idle state, unpacks the data downloaded from the NDS server, and transfers the data to the corresponding processing program one by one, submitting it to the UI for display.

[0173] In this embodiment, combined with Figure 4 The diagram illustrates the process of user-submitted information and comments via SMS and the distribution of messages to the system, explaining the process of end-users reporting SMS messages to the system and the distribution of messages to the system.

[0174] The initial stage of this process ignores the RACH resource request process. After the user obtains satellite resources, the SMS process is initiated using in-band signaling on the service channel.

[0175] SMS process 1-2: The user MES carries the message to be published in an SMS message and submits it to the system as an SMS Crowd. The SMS Crowd is the message to be published to a group of users. If it is to be published to a group of friends, it is sent as an SMS Friends message. The SMS request arrives at the MSC Server through the SCC.

[0176] In SMS process 3-4, the MSC Server submits the initiator's MSISDN number to the HLR for user legitimacy check (Check MES), and the HLR checks for legitimacy (Check OK).

[0177] In SMS process 5-6, the MSC Server sends an SMS Crowd message to the DMS, and the DMS replies with an SMS Crowd Received message to indicate that the SMS message has been received.

[0178] In SMS process 7-8, the MSC Server sends an SMS receipt confirmation (SMS CrowdReceived) to the terminal MES via SCC. After receiving the confirmation, the MES notifies the user that the SMS has been sent normally.

[0179] SMS process 9-10: The terminal MES sends a service channel disconnection request Release, which arrives at the MSCServer via SCC.

[0180] In SMS process 11-12, the MSC Server agrees to disconnect the service channel and sends back a disconnection completion instruction ReleaseCompete. The instruction reaches the MES via SCC, and both parties jointly disconnect the satellite service channel. The mobile station MES returns to the idle state.

[0181] SMS process 13: After receiving the SMS message submitted by the MSC Server, the DMS server stores it according to the sender's MSISDN number and forwards it to the NDS server as SMS Crowd. The DMS server's work is complete.

[0182] In SMS process 14-15, after the NDS server receives the group SMS Crowd forwarded by the DMS server, it begins to query the user list of the group to which the sender user MSISDN belongs, querying the group list of users in the HLR / VLR sequentially (Query GroupList), and the HLR / VLR sends back the query result (Response Group List).

[0183] SMS process 16-17: The NDS server queries the GCR for the group member list one by one based on the queried group list. The GCR sends back the query result Response Group Member List. The NDS merges all the queried group member lists into a message distribution user list containing all members and each member appears only once, and prepares to distribute the message to the users on the list.

[0184] The following is the process for distributing and querying friend information:

[0185] In SMS process 18-20, after the NDS server receives the SMS Friends message forwarded by the DMS server, it begins to query the friend list of the sender user MSISDN, querying the SRS server one by one. The SRS server replies with the Response Friend List. Based on the query results, the NDS forms a message distribution user list and prepares to distribute the message to the users on the list.

[0186] The friend user list search process has ended.

[0187] In SMS process 21, the NDS server main processor NDS MPU, based on the distribution user list, places the SMS Crowd (or SMS Friends) packaged in the Packingbox into the cache queue of the MSISDN index of each user in the list. Distribute SMS to Everyone By List. At this point, NDS completes the information distribution buffer storage and waits for users to download and retrieve it.

[0188] In SMS process 22-24, the NDS server pushes the NDRNotify report (notified to group users or friends) to the terminal's data not arriving status via the MSC Server and SCC, notifying them to download and obtain the data.

[0189] Combination Figure 5 This diagram illustrates the process of user-submitted information and comments data and its distribution to the system, providing an example of how end-users report data to the system and how the system distributes it.

[0190] The initial stage of this process ignores the RACH resource request process. After the user obtains satellite resources, the data call process is initiated using in-band signaling on the service channel.

[0191] In data flow 1-2, the user MES carries the published information in the data transmission and initiates a data call request Setup Crowd to the system. The data call request arrives at CDSN through SCC. Setup Crowd reports the published information to the group of users. If it is to be published to the friends' group of users, the Setup Friends data call request is used to initiate the call.

[0192] Data flow 3-4: The CDSN submits the initiator's MSISDN number to the HLR for user legitimacy check (CheckMES), and the HLR checks for legitimacy (Check OK).

[0193] In data flow 5-6, CDSN sends Data Crowd to DMS, and DMS sends Data crowd Receive Ready back to inform CDSN to prepare to receive data.

[0194] In the data flow 7-10, the CDSN sends a media connection request (Connect) to the terminal MES via SCC. After receiving the request, the MES agrees to the connection and sends a Connect Ack back. At this point, the media channel connection between the MES and CDSN is completed, and both parties can transmit data on the media connection.

[0195] Data flow 11-12: The terminal sends the user-published data to the CDSN via the media connection. The CDSN forwards it to the DMS server. The DMF server confirms receipt after receiving the user-published data.

[0196] Data flow 13: After receiving the data submitted by the CDSN, the DMS server stores it according to the sender's MSISDN number and forwards it to the NDS server as a Data Crowd. The DMS server's work is now complete.

[0197] Data flow 14-15: After the NDS server receives the group data (Data Crowd) forwarded by the DMS server, it starts querying the user list of the group to which the sender user (MSISDN) belongs, querying the group list (Query GroupList) of the users in the HLR / VLR, and the HLR / VLR sends back the query result (Response Group List).

[0198] Data flow 16-17: The NDS server queries the GCR for the group member list one by one based on the queried group list. The GCR sends back the query result Response Group Member List. The NDS merges all the queried group member lists into an information distribution user list containing all members and each member appears only once, and prepares to distribute the information to the users on the list.

[0199] The following is the process for distributing and querying friend information:

[0200] Data flow 18-20: After the NDS server receives the friend circle data (Data Friends) forwarded by the DMS server, it starts querying the friend user list of the sender user MSISDN, querying the SRS server (Query Friend List). The SRS server replies with a response (Response Friend List). Based on the query results, the NDS server forms an information distribution user list and prepares to distribute information to the users on the list.

[0201] The friend user list search process has ended.

[0202] Data flow 21: The NDS server main processor NDS MPU, based on the distribution user list, places the Data Crowd (or Data Friends) packaged in the container into the cache queue of the MSISDN index of each user in the list. Distribute Data to Everyone By List. At this point, NDS completes the information distribution, buffer storage, and waits for users to download and retrieve it.

[0203] Data flow 22-25: After the data transmission is completed and an acknowledgment is received, the MES initiates the satellite channel release procedure. The terminal MES sends a service channel disconnection request Release. The disconnection request reaches the MSC CDSN via SCC. The CDSN agrees to disconnect the service channel and sends back a disconnection completion instruction Release Compete. The instruction reaches the MES via SCC. Both parties jointly disconnect the satellite service channel, and the mobile station MES returns to the idle state.

[0204] Data flow 26-28: The NDS server pushes the NDRNotify report (notified when data has not arrived at the terminal) to group users or friends via the MSC Server and SCC, notifying them to download and obtain the data.

[0205] Combination Figure 6 This diagram illustrates the process of user-submitted information and "like" status updates, as well as the system's distribution process. It provides an example of how end-users report status messages to the system and how the system distributes them.

[0206] In status flow 1-2, MES sends a status emoticon called RACH Crowd to the group of users. After receiving it, SCC responds to the user with RRC Agch signaling that it has received the message. If MES sends a status emoticon called RACH Friends to the group of users, it sends a RACH a Like message.

[0207] State flow 3: SCC forwards RACH crowd to STS.

[0208] In the status flow 4-5, STS submits the initiator's MSISDN number to HLR for user legitimacy check (CheckMES), and HLR checks for legitimacy (Check OK).

[0209] In state flow 6, after receiving the state message submitted by SCC, the STS server stores it according to the RACH address and forwards it to the NDS server as State Crowd. The STS server's work is now complete.

[0210] In state flow 7-8, after the NDS server receives the group status State Crowd forwarded by the STS server, it begins to query the user list of the group to which the sender user MSISDN belongs, querying the group list of users in the HLR / VLR sequentially (Query GroupList), and the HLR / VLR sends back the query result (Response Group List).

[0211] In the state flow 9-10, the NDS server queries the GCR for the group member list QueryGroup Member List one by one based on the queried group list. The GCR sends back the query result Response Group Member List. The NDS merges all the queried group member lists into an information distribution user list containing all members and each member appears only once, and prepares to distribute the information to the users on the list.

[0212] The following is the process for distributing and querying friend information:

[0213] In the state flow 11-13, after the NDS server receives the State Friends data forwarded by the STS server, it starts querying the friend list of the sender user MSISDN, querying the SRS server one by one (Query FriendList). The SRS replies with Response Friend List. Based on the query results, the NDS forms an information distribution user list and prepares to distribute information to the users on the list.

[0214] The friend user list search process has ended.

[0215] In state flow 14, the NDS server main processor NDS MPU, based on the distribution user list, places the State Crowd (or State Friends) packaged in the Packingbox into the cache queue indexed by the MSISDN of each user in the list. Distribute State to Everyone By List. At this point, NDS completes the information distribution buffer storage and waits for users to download and retrieve it.

[0216] In status flow 15-17, the NDS server pushes the Terminal Not Received Data Status Report (NDRNotify) to group users or friends via the MSC Server and SCC, notifying them to download and obtain it.

[0217] Combination Figure 7 This diagram illustrates the process by which an end user retrieves published information and comments / likes from the system's NDS server.

[0218] The initial stage of this process ignores the RACH resource request process. After the user obtains satellite resources, the data call process is initiated using in-band signaling on the service channel.

[0219] In the acquisition process 1-2, after the MES learns from the NDR list that there is undelivered data cached in its NDS queue, it decides to download this data, so it initiates a data establishment call Setup NDS. The call request arrives at the CDSN through SCC.

[0220] In process 3-4, the CDSN parses the Setup NDS and learns that a satellite terminal identified by an MSISDN number wants to download its NDS data. It then first queries the HLR / VLR for user legitimacy and submits the initiator's MSISDN number to the HLR for user legitimacy check (Check MES). The HLR verifies the legitimacy and sends back Check OK.

[0221] In the acquisition process 5-6, CDSN sends a Request Download MES NDS Queue Cargo request to NDS, and NDS replies with Ready to Download to inform CDSN that it is ready to download the data.

[0222] In the acquisition process 7-8, the CDSN sends a Connect signaling message to the MES via the SCC, requesting the MES to establish a media connection.

[0223] In the acquisition process 9-10, MES sends a Connection Ack signaling back to CDSN via SCC to confirm that the MES media connection has been completed.

[0224] In process 11, the NDS server downloads the user's cached data to the user's MES via the CDSN using a data cargo transfer protocol in a containerized manner.

[0225] In process 12, MES verifies the received data shipments to confirm that all data shipments have been received, and then notifies NDS of receipt of the shipments through the shipment transfer agreement.

[0226] In the acquisition process 13-14, the terminal MES sends a data link teardown command Release, which arrives at the CDSN via SCC.

[0227] In the acquisition process 15-16, the CDSN sends back a "Release Complete" command to complete the data link teardown. This command arrives at the MES via the SCC. From this point on, the NDS data download process is complete, satellite circuit resources are released, the terminal processes the downloaded NDS data, and returns to the cluster idle state.

[0228] The embodiments described above are merely one implementation method of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A satellite cluster terminal user information publishing and comment / like interaction system, characterized in that, This includes the Status Server (STS), Satellite Channel Controller (SCC), Cluster Switching Center (MSC Server), Circuit Data Support Node (CDSN), Terminal Not Arrived Data Server (NDS), Data Message Server (DMS), HLR / VLR Server, Group Call Register (GCR), and Subscriber Recovery Server (SRS). Among them, the information published and comments / likes by satellite trunk terminal users are transmitted to the data message server (DMS) or status server (STS) through the trunk exchange center (MSCServer), circuit data support node (CDSN), or satellite channel controller (SCC). The Data Message Server (DMS) or Status Server (STS) transmits information to the terminal that has not yet reached the Data Server (NDS). Satellite cluster terminal users download relevant information from the data server NDS, which is not accessible to the terminal, through the circuit data support node CDSN; The HLR / VLR server is used to provide group list information query services for information distribution to terminals that have not reached the NDS data server; The group call register (GCR) is used to provide a group member list information query service for information distribution when the terminal has not arrived at the data server (NDS). The subscriber data recovery server (SRS) is used to provide a one-call user friend list information query service for terminals that have not reached the data server (NDS).

2. The satellite cluster terminal user information publishing and comment / like interaction system according to claim 1, characterized in that, The information published and comments / likes by the satellite cluster terminal users include: Group Dynamics: Information posting and interaction (comments, likes, etc.) within a group user circle based on cluster group call users; Friend Activity: Information posting, commenting, and liking interactions based on the friend circle of a user in a cluster-based one-call user; The group user circle is the set of users in all cluster groups that the satellite cluster terminal user participates in, and the friend user circle is the set of all cluster-call friends in the phone book of the satellite cluster terminal user.

3. The satellite cluster terminal user information publishing and comment / like interaction system according to claim 1, characterized in that, The types of information published and comments / likes by satellite cluster terminal users include cluster SMS information publication, cluster data information publication, and cluster status message information publication. The satellite cluster text messages are Chinese characters or symbols expressed in no more than 140 bytes; The cluster data consists of short texts, encoded voice, or compressed graphic images expressed in no more than 10KB. The cluster status message is encoded information of no more than 55 bits.

4. The satellite cluster terminal user information publishing and comment / like interaction system according to claim 1, characterized in that, The process for publishing satellite cluster terminal user information and interacting with comments and likes includes: Uplink transmission of satellite cluster terminal user information publishing, comments, and likes; The transit storage and transshipment of information distributed through the ground station core network; Satellite cluster terminal users can access published information, comments, and likes via downlink.

5. The satellite cluster terminal user information publishing and comment / like interaction system according to claim 4, characterized in that, The uplink transmission methods for user information publishing, commenting, and liking on satellite cluster terminals include: Satellite trunking terminal users use trunking SMS to publish information. The publishing path of the trunking SMS is, in order, the satellite trunking terminal MES, the core network MSC Server, and the data message server DMS. Satellite trunk terminal users use trunk data to publish information. The publishing path of the trunk data is, in sequence, the satellite trunk terminal MES, the circuit data support node CDSN, and the data message server DMS. Satellite trunking terminal users publish information using trunking status messages. The publication path of these trunking status messages is sequentially: satellite trunking terminal MES, satellite channel controller SCC, and status server STS.

6. The satellite cluster terminal user information publishing and comment / like interaction system according to claim 4, characterized in that, The uplink transmission process for publishing, commenting, and liking information for satellite cluster terminal users includes: (1) The information publisher edits text, short articles, records a voice message, or pastes a compressed image in the group dynamics or friend dynamics of the satellite trunking terminal, starts the information publishing, and clicks send: 1) Encapsulate the data to be sent with a 9-bit unique data identifier, Data ID, and fill in the source and destination addresses of the data message. Since the destination address is a group user circle or friend user circle, use the user circle identifier instead of the destination address; fill in the data attribute parameters so that the receiver can parse and form the published data. 2) Check the length of the data to be sent. If the length is less than 140 bytes, use the SMS sending process to send the information to the Cluster Exchange Center (MSC) Server. If the data length is more than 140 bytes but less than 10KB, use the data sending process to send the information to the Circuit Data Support Node (CDSN). If the data length is more than 10KB, prompt the user that the data is too long to send and ask the user to re-edit the data. 3) When SMS sending is selected, after the satellite trunking terminal obtains dedicated channel resources from the gateway station via satellite, it uses the dedicated accompanying control channel DACCH to submit the SMS to the trunking exchange center MSCServer in the accompanying signaling mode. The trunking exchange center MSC Server then forwards it to the data message server DMS. When data transmission is selected, the satellite trunk terminal obtains dedicated channel resources from the gateway station via satellite, and then uses the dedicated service channel DTCH to submit the published data to the Circuit Data Support Node (CDSN) in the form of media data transmission. The Circuit Data Support Node (CDSN) then forwards the data to the Data Message Server (DMS). (2) When commenting on a post, the user selects a post from another user's group feed or friend feed in the terminal app and comments on it. The comment is a text or string of characters. To post the comment, click "send". 1) Encapsulate the comment data to be sent with a 9-bit unique data identifier (Data ID) for the comment information. Fill in the source and destination addresses of the data message. Since the destination address is a group user circle or friend user circle, use the user circle identifier instead of the destination address. Fill in the data attribute parameter as the comment information. The comment information parameter carries the MSISDN number of the user being commented on so that the receiver can parse it to form the comment posting data. 2) Check the length of the comment data to be sent. If the length is less than 140 bytes, use the SMS sending process to send the information to the Cluster Exchange Center (MSC) Server. If the comment data length is more than 140 bytes but less than 10KB, use the data sending process to send the information to the Circuit Data Support Node (CDSN). If the comment data length is more than 10KB, prompt the user that the comment data is too long to send and ask the user to re-edit the data. 3) When SMS sending is selected, after the satellite trunk terminal obtains dedicated channel resources from the gateway station via satellite, it uses the dedicated accompanying control channel DACCH to submit the published comment SMS to the MSC Server in the accompanying signaling manner. The MSC Server then forwards it to the data message server DMS. When data transmission is selected, the satellite trunk terminal obtains dedicated channel resources from the gateway station via satellite, and then uses the dedicated service channel DTCH to submit the published data to the CDSN in the form of media data transmission. The CDSN then forwards it to the data message server DMS. (3) The information publisher sends a status emoticon or likes the received information in the group dynamics or friend dynamics section, and clicks send: 1) Edit a RACH status message for the status emoticon to be sent. The status message carries the sender's MSISDN number, the encoding number of the target user group user circle or friend user circle and the emoticon encoding, as well as the status message type identifier and status message subtype identifier, totaling 55 bits of status message. Send the RACH to the satellite using the random access procedure. 2) Edit a RACH status message for the upcoming like message. The status message carries the MSISDN number of the liked, the Data ID of the publisher of the liked, the target user group user circle or friend user circle identifier, and the status message type identifier and status message subtype identifier, totaling 55 bits of status message. Send the RACH to the satellite using a random access procedure. 3) After the satellite cluster terminal sends a status emoticon or like message via RACH, it is received by the gateway station's satellite channel controller (SCC) and submitted to the status server (STS).

7. The satellite cluster terminal user information publishing and comment / like interaction system according to claim 4, characterized in that, The transit storage and transfer of information distribution in the ground station core network includes information storage and forwarding between functional entities within the core network, as well as the distribution and transit caching of information before the terminal reaches the data server NDS.

8. The satellite cluster terminal user information publishing and comment / like interaction system according to claim 7, characterized in that, The information storage and forwarding between functional entities within the core network includes: (1) Store-and-forwarding of the core network data message server (DMS): 1) The core network data message server (DMS) receives user-posted information and comment SMS messages from the cluster exchange center (MSC) server and stores them according to the sender's MSISDN number to form a history of SMS messages, so as to provide subsequent operation query services; 2) The core network data message server (DMS) receives user-posted information and comment data from the circuit data support node (CDSN), stores it according to the sender's MSISDN number, and forms a historical record of the data to provide subsequent operation query services; 3) After storing the data according to the sender's MSISDN number, the core network data message server (DMS) forwards the information according to the destination address of the SMS or data. Since the destination address is the user's circle address, the information is forwarded to the terminal before it reaches the data server (NDS) according to the forwarding strategy. (2) Store-and-forward functionality of the core network state server (STS): 1) After receiving the RACH status message sent by the user from the Satellite Channel Controller (SCC), the Core Network Status Server (STS) stores it according to the 37-bit address carried by the RACH to form a historical record of the RACH, so as to provide subsequent status query services. 2) After storing the 37-bit address carried by RACH, the core network state server STS decodes the state messages and forwards the user's emoticon and like information to the NDS (Network Data Server) before the terminal arrives.

9. The satellite cluster terminal user information publishing and comment / like interaction system according to claim 7, characterized in that, The distribution and relay caching of the information before it reaches the data server NDS at the terminal includes: (1) The terminal has not reached the data server. The NDS receives the forwarded status message from the status server STS, and receives the forwarded SMS or data from the DMS server. It can view the source address and user circle identifier of the information. (2) If the user circle is a group user, the terminal does not reach the data server NDS. It queries the HLR / VLR server for the group list of this user using the information source address MSISDN number. After obtaining the group list, it queries the group call register GCR one by one for the member list of each group. The query results are merged to form an NDS distribution list that contains all users and appears only once. (3) If the user is a friend user, the terminal does not reach the data server NDS. The terminal queries the subscriber recovery server SRS for the user's one-call friend list using the information source address MSISDN number. After obtaining the list, an NDS distribution list is formed. (4) If the terminal does not arrive at the data server, the NDS will package and cache the status, SMS or data of the list users in the Packingbox or Container according to the distribution list, modify the NDR report of the list users, and broadcast the NDR status notification to the relevant users through the cluster exchange center MSC Server, and wait for the users to obtain the data.

10. The satellite cluster terminal user information publishing and comment / like interaction system according to claim 4, characterized in that, The process for satellite cluster terminal users to obtain published information and comments / likes via downlink includes: (1) Group users or friends can obtain their NDR reports through the following means: 1) Online users hear the NDR status notification pushed by the NDS (Network Data Server) indicating that the terminal has not arrived at the data server and that the NDS has cached its terminal's data arrival status. 2) Offline users did not hear the NDR status notification pushed by the terminal not arriving at the data server NDS. After they powered on and connected to the network, they initiated an NDR query and learned that the terminal had not arrived at the data server NDS had cached its terminal not arriving at the data server status. (2) Group users or friends initiate data download after receiving the NDR report: 1) After obtaining his own NDR status report, the user learns that the terminal has not arrived at the data server. The NDS caches his terminal's non-arrival data and initiates the data download process. 2) After the terminal obtains dedicated channel resources from the gateway station via satellite, it uses the dedicated service channel DTCH to submit the terminal's download request for the NDS (Network Data Support Node) to the Circuit Data Support Node (CDSN) via data call signaling in the form of media data transmission. The CDSN then forwards the request to the NDS, which is not yet reached by the terminal. The NDS then downloads the user's cached data to the requesting terminal using the data cargo transfer protocol through the CDSN. 3) After the terminal confirms that it has received the data downloaded from the NDS (Network Data Server), the NDS will clear the NDR (Network Data Report Register) and the user data buffer, and wait for the user to cache the data next time. 4) After the terminal confirms that it has received the NDS data downloaded from the terminal's non-reaching data server, it initiates the satellite link release process. After the process ends, the terminal returns to the idle state, unpacks the data downloaded from the NDS server, and transfers the data to the corresponding processing program one by one, submitting it to the UI for display.

Images