Satellite cluster terminal access state driving type user business card interaction system

Abstract

The invention discloses a satellite cluster terminal access state driving type user business card interaction system, which takes an RACH (Random Access Channel) coding state of a business initiator terminal accessing a ground station access network satellite channel controller SCC as an interaction drive, and takes user report business card storage and controlled release provided by a ground station core network state server STS as a service main body station. A user circle or individual user business card data collection and sorting cache provided by a terminal non-arriving data server NDS is used as a freight transfer station, a satellite terminal transmission and data cargo transfer protocol provided by a circuit data support node CDSN is used as a carrier junction station, and a cluster switching center MSC Server is assisted to remind and notify user business card collection as a tail end broadcast station. Services such as personal business card reporting, business card distribution, business card collection and point-to-point user business card exchange are provided for the cluster user terminal, and great convenience is brought to cluster function use and user mutual identification.

Description

Technical Field

[0001] This invention belongs to the field of satellite communication, specifically relating to a satellite cluster terminal access status-driven user business card 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] Trunking voice, as a method for exchanging and transmitting streaming media, provides real-time communication functionality. However, streaming media is only suitable for real-time services. The strategy for handling streaming media transmission is to perform protective forward channel encoding and decoding on the data stream to reduce bit errors in the wireless channel, without performing interactive error correction encoding and decoding to ensure end-to-end latency. Streaming media bitstreams cannot avoid the occurrence of bit errors with a small probability.

[0006] The problem this invention aims to solve is how user business cards can be interacted among numerous cluster users. When user business cards are transmitted between satellite and ground, it is essentially packet data communication, not a data streaming service. These packets need to be transmitted between users without errors or loss. Current satellite trunking communication systems only provide streaming media services and lack the ability to exchange and transmit data packets. Summary of the Invention

[0007] To address the aforementioned problems, the present invention aims to provide a satellite cluster terminal access status-driven user business card interaction system.

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

[0009] A satellite trunking terminal access status-driven user card 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, an HLR / VLR server, a group call register GCR, and a subscriber recovery server SRS.

[0010] The State Server (STS) stores the business cards reported by the user based on the user's MSISDN number and performs business card interaction based on the user terminal access status driver. The State Server (STS) transfers the business card data to be distributed to the terminal's unreached data server (NDS) based on the interaction information in the RACH information.

[0011] The Status Server (STS) sends business cards and notifications to the receiving users through the Cluster Exchange Center (MSC Server).

[0012] The Circuit Data Support Node (CDSN) is used as the transmission carrier entity for user business card information. The business card recipient user obtains business card data from the terminal's unreachable data server (NDS) through the Circuit Data Support Node (CDSN).

[0013] The Satellite Channel Controller (SCC) is an access network entity used to provide RACH information related to user business card interaction driving information status.

[0014] The HLR / VLR server is used to provide the State Server (STS) and the Data Server (NDS) with a query service for the group number of the cluster group corresponding to the user terminal, so as to obtain a detailed list of all cluster groups that the user terminal participates in.

[0015] The group call register (GCR) is used to provide a cluster group member list query service for the status server (STS) and the terminal not arriving data server (NDS).

[0016] The Subscriber Recovery Server (SRS) is used to provide a query service for all friend user numbers and address books for the Status Server (STS) and the Terminal Not Arrived Data Server (NDS).

[0017] Furthermore, the user profile includes: user avatar, user name, user satellite phone number, user satellite terminal cluster identifier, and remarks;

[0018] After the user finishes editing the user card, the user card information is uploaded to the state server STS for storage via the circuit data support node CDSN.

[0019] When a user's business card is updated, the updated business card is uploaded to the State Server (STS) via the Circuit Data Support Node (CDSN) for overwriting storage.

[0020] Furthermore, the user terminal access status is the status information carried in the uplink random access request (RACH) information of the user terminal that initiated the business card service from the ground station satellite feed circuit.

[0021] The status information contains a total of 55 bits of encoded information, of which 37 bits are address identifiers, 4 bits are message type, and 14 bits are status encoding information, including three types of status encoding driven by business card service interaction:

[0022] (1) Business card distribution, including 4 bits of message type, 10 bits of user avatar code, 37 bits of publisher MSISDN number, and 4 bits of operation code. The operation code of business card distribution expresses the following: the publisher distributes the business card to his group user circle or friend user circle. The user who receives the business card needs to reset the user avatar or update the business card according to the status code. The purpose of business card distribution is that the publisher has changed the avatar or updated the business card content, and his group users or friend users need to update synchronously.

[0023] (2) Business card collection, including 4 bits of message type, 1 bit of operation code, 4 bits of code number, 9 bits of business card collection sub-code, and 37 bits of requester MSISDN number. The operation code of business card collection expresses the content: the requester collects his group user business cards or friend circle user business cards. The purpose of business card collection is that the requester has established or joined a cluster group and he needs to add business card information for all members of this cluster group.

[0024] (3) Business card exchange, including 4 bits of message type, 1 bit of operation code, 4 bits of counterpart code number, 9 bits of business card exchange sub-code and 37 bits of requester MSISDN number. The business card exchange operation code and business card exchange sub-code together represent the exchange of business cards. Since the RACH information cannot carry all 37 bits of the exchanged party's MSISDN number, the 4 bits of counterpart code number during business card exchange is his / her MSISDN number index. The state server STS further parses to obtain the counterpart's actual number. The requester's MSISDN number is the user number of the initiating party. The purpose of business card exchange is that the requester has established a new user friend relationship and needs to exchange business card information with each other.

[0025] Furthermore, when the user terminal access status is business card distribution, the business card distribution process includes:

[0026] (1) The initiating user terminal uses RACH random access signaling to carry the "business card distribution" status code to access the ground station system via the trunking public channel;

[0027] (2) The satellite channel controller (SCC) entity of the ground station access network uses RRC response to confirm that RACH has been received via downlink through the trunking common channel;

[0028] (3) The satellite channel controller (SCC) attaches a beam identifier to the RACH and submits it to the state server (STS). The state server (STS) parses the state code of the terminal access.

[0029] (4) The State Server (STS) resolves the status code to "business card distribution", retrieves the business card stored by the initiator under its MSISDN number name, delivers it to the terminal's unreached data server (NDS), and notifies it to perform the business card distribution operation.

[0030] (5) If the terminal does not reach the data server NDS, it will use the business card distribution information submitted by the status server STS to query all group numbers of the user from the HLR / VLR using the distributor's MSISDN number, and then query the group member list from the group call register GCR based on the group number; if it is a friend circle distribution, it will use the distributor's MSISDN number to query all single call friend user lists of the user from the subscriber recovery server SRS.

[0031] (6) The terminal does not arrive at the data server. The NDS collects all group numbers and all group member lists of the distributor, constructs a group user list or friend user list, caches the distributor's business card in the packingbox queue of all list users, and updates the user's NDR status.

[0032] (7) The State Server (STS) submits a group broadcast to the Cluster Exchange Center (MSC Server) to notify the recipient user to collect the business card.

[0033] (8) The user receiving the business card executes the download process and obtains the distributor's business card from the terminal's data server NDS through the CDSN data channel.

[0034] Furthermore, when the user terminal is in the business card collection state, the business card collection process includes:

[0035] (1) The initiating user terminal uses RACH random access signaling to carry the "business card collection" status code to access the ground station system via the trunking public channel;

[0036] (2) The satellite channel controller (SCC) entity of the ground station access network uses RRC response to confirm that RACH has been received via downlink through the trunking common channel;

[0037] (3) The satellite channel controller (SCC) attaches a beam identifier to the RACH and submits it to the state server (STS). The state server (STS) parses the state code of the terminal access.

[0038] (4) The State Server STS parses the status code as "business card collection". If it is a group user business card collection, it uses the collector's MSISDN number to query the HLR / VLR for all group numbers of this user, and then queries the group call register GCR for the group member list based on the group number; if it is a friend circle user business card collection, it uses the collector's MSISDN number to query the subscriber recovery server SRS for all friend user lists of this user.

[0039] (5) The State Server (STS) collects all group numbers and all group member lists of the collector, constructs a group user list or friend list, and retrieves the business cards stored under their MSISDN numbers one by one according to the list, and hands over all the retrieved business cards to the terminal's unreachable data server (NDS).

[0040] (6) The terminal has not reached the data server NDS. According to the business card collection information submitted by the status server STS, the terminal caches all the received business card packing boxes in the packing box queue of the collector user and updates the user's NDR status.

[0041] (7) The State Server (STS) broadcasts the user collector's business card collection to the Cluster Exchange Center (MSC Server), notifying the collector that the user has collected the business card.

[0042] (8) The business card collector user's terminal does not reach the data server NDS download process. Through the data channel of the circuit data support node CDSN, the collector obtains all group user business cards.

[0043] Furthermore, when the user terminal access status is business card exchange, it first determines whether the 4-bit counterpart code number in the status information has been bound to the MSISDN number. If it is not bound, the MSISDN number binding is performed. If it is bound, the business card exchange process is initiated using RACH Information.

[0044] Furthermore, the MSISDN number binding process includes:

[0045] (1) Use the unused encoded numbers in the 4-bit encoding in a loop to bind the other party's MSISDN number;

[0046] (2) When all 4 bits of the code are occupied, the original binding is released in a loop and the other party's MSISDN number is used as the replacement binding;

[0047] (3) Pack the entire table of coded numbers into a packaging box and prepare to send it to the State Server (STS);

[0048] (4) Pack the “business card exchange” information, including the other party’s MSISDN number and the local MSISDN number, into a packing box, and put it together with the full table of coded numbers into the data cargo container to be uploaded to the status server STS;

[0049] (5) Using the data cargo transshipment protocol, the data cargo container is transshipped to the Circuit Data Support Node (CDSN);

[0050] (6) The Circuit Data Support Node (CDSN) delivers the data cargo container to the State Server (STS).

[0051] (7) The State Server (STS) stores the packing boxes in the data cargo container and the full table of the coding numbers in the packing boxes.

[0052] Furthermore, the process of initiating a business card exchange using RACH information specifically includes:

[0053] (1) The initiating user uses RACH random access signaling to carry the "business card exchange" information status code to access the ground station system via the trunking public channel;

[0054] (2) The ground station access network satellite channel controller (SCC) entity uses RRC response to confirm that RACH has been received via downlink through the trunking common channel;

[0055] (3) The satellite channel controller (SCC) attaches a beam identifier to the RACH and submits it to the state server (STS). The state server (STS) parses the state code of the terminal access.

[0056] (4) The State Server (STS) parses the status code as "business card exchange" and executes the business card exchange process.

[0057] Furthermore, the business card exchange process includes:

[0058] (1) The State Server (STS) retrieves the business card based on the MSISDN number of the business card initiator and delivers it to the Terminal Data Server (NDS) that has not yet arrived, requesting it to put the business card into the Packingbox queue of the business card exchange recipient's MSISDN.

[0059] (2) The State Server (STS) retrieves the business card of the other party based on the MSISDN number in the business card exchange and hands it to the Terminal Data Server (NDS) which has not yet arrived, requesting it to put the business card into the Packingbox queue of the MSISDN that initiated the business card exchange.

[0060] (3) The State Server (STS) sends a business card exchange broadcast notification to the business card exchange party through the Cluster Exchange Center (MSC Server);

[0061] (4) When both parties receive or do not receive a broadcast notification, they will obtain each other's business card information and complete the business card exchange if the terminal has not yet reached the data server NDS data.

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

[0063] Satellite trunking communication is essentially narrowband communication. In existing narrowband communication systems, there is a lack of the ability for users to exchange basic personal information. Each user manually or by using call records to edit the other user's information, which mainly consists of the other party's phone number and title. This is how existing telephone address books are generated.

[0064] This invention provides users with a new means of distributing, collecting and exchanging basic personal information, especially the member information of a group. If it is manually edited, it will cause great inconvenience to the user. If the user does not edit the group member information, the speaking number during each call will be a string of Arabic numerals, which is difficult for the user to identify.

[0065] When users group satellite constellations, this user card interaction system provides all group members with their avatars, names, phone numbers, constellation numbers, and notes, greatly facilitating the use of constellation functions and user identification.

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

[0067] Figure 1 This is a schematic diagram of the architecture of the satellite cluster terminal access status-driven user business card interaction system of the present invention.

[0068] Figure 2 This is a schematic diagram illustrating the association between the State Server Service (STS) business card storage and the core network service entity according to the present invention.

[0069] Figure 3 This invention provides user profiles and dynamically configured coded number tables edited by the terminal APP.

[0070] Figure 4 This is a schematic diagram illustrating the process by which the terminal submits a registration card and code number table to the Status Server (STS) according to the present invention.

[0071] Figure 5 This is a schematic diagram of the terminal access status-driven business card user circle distribution process of the present invention.

[0072] Figure 6This is a schematic diagram of the terminal access status-driven business card user circle collection process of the present invention.

[0073] Figure 7 This is a schematic diagram of the terminal access status-driven business card exchange process of the present invention.

[0074] Figure 8 This is a schematic diagram of the terminal access status-driven business card collection and download process for the invention. Detailed Implementation

[0075] Example

[0076] 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.

[0077] 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.

[0078] 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.

[0079] To solve the problem of data packet transmission, a data frame transmission link needs to be established from the terminal to the ground station core network. The core problem to be solved in establishing this transmission link is: to solve the problem of data packet transmission at the terminal by adding appropriate data protocol layers on top of the original data streaming media without changing the basic service transmission characteristics of the original data streaming media.

[0080] To address this, at the boundary between the ground station core network and the access network, we propose a new data processing entity called the satellite constellation "Circuit Data Supporting Node (CDSN)" (e.g., ...). Figure 1 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 undergoes frame verification again. When 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 fragmentation reception BIT MAP 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.

[0081] Once the CDSN and its transmission protocol are established, reliable data frame transmission capability is provided from satellite terminals to the ground station core network. Based on this, a unified data cargo transfer protocol is used to upload or download application data.

[0082] The transshipment method is as follows: high-level data is treated as goods to be distributed. Each piece of data needs to be packaged. Goods with fewer than 255 bytes are placed in packing boxes for storage and transshipment; goods with more than 255 but less than 1565 bytes are placed in containers for storage and transshipment; and goods with more than 1565 bytes are placed in multiple containers for storage and transshipment. Each package must be labeled with its byte length and application data type to facilitate sorting, processing, and application integration.

[0083] In addition, Non-Delivered Data Servers (NDS) are deployed in the core network, and together with the existing Cluster Core Network Switching Center (MSC Server), they provide support services for new functions such as user business card status extraction, distribution, reporting, and download.

[0084] In existing satellite mobile communication system ground stations, the core network adds a satellite cluster status service function entity called "State Server (STS)". The STS communicates with other service function entities through the internal IP network of the gateway station to realize terminal status services.

[0085] The Satellite Cluster Status Server (STS) is associated with other service entities in the core network. Together with these entities, the STS reports and stores user business cards, extracts and drives interaction status information, and enables the distribution, collection, exchange, caching, querying, and downloading of user business cards. The relevant cooperating service entities are:

[0086] Based on the above, combined with Figure 1 and Figure 2 This solution proposes a satellite cluster terminal access status-driven user card interaction system. Based on the aforementioned content and the State Server (STS) deployed in the cluster core network, it obtains the original terminal access information data from the ground station access network entity, extracts the terminal status information from the original data, and realizes the status service function through the joint cooperation of other application service entities in the core network.

[0087] Specifically, the associated business card service functional entities include:

[0088] Satellite Channel Control (SCC), Cluster Switching Center (MSC Server), Circuit Data Support Node (CDSN), Non-Delivered Data Server (NDS), HLR / VLR Server, Group Call Register (GCR), and Subscriber Recovery Server (SRS).

[0089] Among them, the Satellite Channel Control (SCC) is an access network entity that provides the business card interaction driving status information in RACH Information;

[0090] The Cluster Switching Center (MSC Server) is the cluster switching control entity that provides satellite cluster broadcast services to the State Server (STS).

[0091] The Circuit Data Support Node (CDSN) is a data transmission and control entity that provides business card download services for receiving users and business card upload services for business card initiators. Through the data frame interface, the NDS can provide user terminal business card query and download services, and the terminal can also report user business cards to the STS server through the CDSN.

[0092] The Non-Delivered Data Server (NDS) is a core network entity that provides buffering and relay services for business card distribution and data exchange.

[0093] HLR / VLR provides user grouping information query service for the status server STS or the terminal not arriving at the data server NDS. The status server STS or the terminal not arriving at the data server NDS can query the group number of the cluster group corresponding to the satellite terminal recorded in HLR / VLR through the MSISDN number received from MES, and obtain a detailed list of all cluster groups that the terminal participates in.

[0094] The Group Call Register (GCR) provides a query service for group member list information for the Status Server (STS) or the Data Server (NDS) when the terminal has not arrived. The Status Server (STS) or the Data Server (NDS) can query the detailed list of all group members recorded in the Group Call Register (GCR) through the group number.

[0095] The Subscriber Recovery Server (SRS) provides a one-call friend user list address book information query service for the Status Server (STS) or the Data Server (NDS) when the terminal has not arrived. The Status Server (STS) or the Data Server (NDS) can query all friend user numbers and address books of the satellite terminal recorded in the SRS using the MSISDN number received from the MES.

[0096] The interface between the State Server (STS) and other functional entities in the core network uniformly adopts the IP network interface protocol.

[0097] The State Server (STS) executes the data cargo transfer protocol across the entire link with the satellite terminal via the CDSN. The data cargo transfer protocol is carried over the CDSN circuit data support node transmission protocol.

[0098] Its general technical approach is as follows:

[0099] The State Server (STS) stores the business cards reported by the user based on the user's MSISDN number. The initiator of the business card interaction uses the RACH process to place the business card interaction request in its status code. The State Server (STS) performs business card interaction based on the user terminal access status. The State Server (STS) parses the RACH encoded status and transfers the required business card data to the terminal's unreached data server (NDS) according to the interaction information in the RACH information.

[0100] The Status Server (STS) sends business cards and notifications to the receiving users through the Cluster Exchange Center (MSC Server).

[0101] The Circuit Data Support Node (CDSN) is used as the transmission carrier entity for user business card information. The business card recipient user obtains business card data from the terminal's unreachable data server (NDS) through the Circuit Data Support Node (CDSN).

[0102] The Satellite Channel Controller (SCC) is an access network entity used to provide RACH Information regarding the status of user card interaction driving information.

[0103] The HLR / VLR server is used to provide the State Server (STS) and the Data Server (NDS) with a query service for the group number of the cluster group corresponding to the user terminal, so as to obtain a detailed list of all cluster groups that the user terminal participates in.

[0104] The group call register (GCR) is used to provide a cluster group member list query service for the status server (STS) and the terminal not arriving data server (NDS).

[0105] The Subscriber Recovery Server (SRS) is used to provide the Status Server (STS) and the Terminal Not Arrived Data Server (NDS) with a query service for the Address Book of all friends' user numbers of the user terminal.

[0106] The user profile includes: user avatar, user name, user satellite phone number, user satellite terminal cluster identifier, and remarks.

[0107] In this embodiment, combined with Figure 3 This is a general business card editing template for satellite cluster terminal apps. The business card template includes the following sections:

[0108] (1) User avatar: The user selects the avatar from the APP avatar library. The avatar is encoded as 10 bits.

[0109] (2) Username, in Chinese or English, to be filled in by the user;

[0110] (3) Satellite phone number, the MSISDN number associated with the SIM card, which will be automatically filled in by the APP;

[0111] (4) Satellite terminal cluster identifier, local cluster physical device TEID identifier, automatically filled in by the APP;

[0112] (5) Remarks, in Chinese or English, to be filled in by the user.

[0113] After a user completes editing their user profile, they can use the app to upload the user profile information to the State Server (STS) via the Circuit Data Support Node (CDSN).

[0114] When a user's business card is updated, the updated business card can also be uploaded to the State Server (STS) via the Circuit Data Support Node (CDSN) for overwriting storage through the APP.

[0115] The coded number table is a 4-bit index number that is bound by the terminal APP according to the communication status. Code 0 is bound to group users by default, code 15 is bound to friend users by default, and other codes (1-14) can be bound to group numbers or user numbers (MSISDN). The terminal can report the coded number table to STS at any time during communication for synchronization. Among them, group users are a list of users in all groups that the terminal participates in, and friend users are a list of individual call numbers formed by the terminal through the friend establishment process. The individual call number table of the terminal is stored in the Address Book of SRS.

[0116] Combination Figure 4 This diagram illustrates the process of a terminal registering a photo and code number table with the STS status server, providing an example of the process.

[0117] In the reporting process 1-2, MES initiates user business card reporting, sets up a data establishment call (Setup Card), and the call request reaches CDSN via SCC.

[0118] In the reporting process 3-4, the CDSN submits the reporter's MSISDN number to the HLR for user legitimacy verification, and the HLR verifies its legitimacy.

[0119] In the reporting process 5-6, the CDSN parses the Setup Card and learns that a satellite terminal identified by an MSISDN number wants to report its business card and coded number table. It then sends a Card Report request to the STS MPU module of the STS server, which carries the MSISDN number of the reporter. The STS server responds with Card Ok, indicating that it is ready to receive the business card.

[0120] In the reporting process 7-8, the CDSN sends a data connection signaling message (Connect) to the reporting terminal MES via the SCC.

[0121] In the reporting process 9-10, MES sends a connection confirmation signal (Connect Ack) back to CDSN via SCC;

[0122] In the reporting process 11, MES transmits user business card data and code number table to STS MPU via CDSN through the data cargo transfer protocol and CDSN transmission protocol;

[0123] In the reporting process 12, the STS MPU sorts out the business card information from the data goods uploaded by the terminal and stores it in the business card storage MY Card of the MSISDN corresponding to the STS server.

[0124] In the reporting process 13, the STS MPU sorts out the code number table from the data goods uploaded by the terminal and stores it in the code number storage of the MSISDN corresponding to the STS server.

[0125] In the reporting process 14, the STS MPU sends a confirmation of completion of transmission back to the user terminal MES through the data cargo transfer protocol and CDSN transmission protocol.

[0126] In the reporting process 15-16, MES sends a data link teardown command Release, which arrives at CDSN via SCC;

[0127] In the reporting process 17-18, the CDSN sends a "Release Complete" command to the MES via the SCC. From this point on, the MES reporting process from the data packet to the STS is completed, the satellite circuit resources are released, and the MES terminal returns to the cluster idle state.

[0128] The user terminal access status is the status information carried in the uplink random access request (RACH) of the user terminal that initiated the business card service from the ground station satellite feed circuit.

[0129] The status information contains a total of 55 bits of encoded information, of which 37 bits are address identifiers, 4 bits are message type, and 14 bits are status encoding information, including three types of status encoding driven by business card service interaction:

[0130] (1) Business card distribution, including 4 bits of message type, 10 bits of user avatar code, 37 bits of publisher MSISDN number, and 4 bits of operation code. The operation code of business card distribution expresses the following: the publisher distributes the business card to his group user circle or friend user circle. The user who receives the business card needs to reset the user avatar or update the business card according to the status code. The purpose of business card distribution is that the publisher has changed the avatar or updated the business card content, and his group users or friend users need to update synchronously.

[0131] (2) Business card collection, including 4 bits of message type, 1 bit of operation code, 4 bits of code number, 9 bits of business card collection sub-code, and 37 bits of requester MSISDN number. The operation code of business card collection expresses the content: the requester collects his group user business cards or friend circle user business cards. The purpose of business card collection is that the requester has established or joined a cluster group and he needs to add business card information for all members of this cluster group.

[0132] (3) Business card exchange, including 4 bits of message type, 1 bit of operation code, 4 bits of counterpart code number, 9 bits of business card exchange sub-code and 37 bits of requester MSISDN number. The business card exchange operation code and business card exchange sub-code together represent the exchange of business cards. Since the RACH information cannot carry all 37 bits of the exchanged party's MSISDN number, the 4 bits of counterpart code number during business card exchange is his / her MSISDN number index. The state server STS further parses to obtain the counterpart's actual number. The requester's MSISDN number is the user number of the initiating party. The purpose of business card exchange is that the requester has established a new user friend relationship and needs to exchange business card information with each other.

[0133] The service entity that drives the satellite cluster terminal access state mentioned above is the aforementioned satellite cluster "State Server (STS)".

[0134] When the user terminal access status is business card distribution, the business card distribution process includes:

[0135] (1) The initiating user terminal uses RACH random access signaling to carry the "business card distribution" status code to access the ground station system via the trunking common channel;

[0136] (2) The satellite channel controller (SCC) entity of the ground station access network uses RRC response to confirm that RACH has been received via downlink through the trunking common channel;

[0137] (3) The satellite channel controller (SCC) attaches a beam identifier to the RACH and submits it to the state server (STS). The state server (STS) parses the state code of the terminal access.

[0138] (4) The State Server (STS) resolves the status code to "business card distribution", retrieves the business card stored by the initiator under its MSISDN number name, delivers it to the terminal's unreached data server (NDS), and notifies it to perform the business card distribution operation.

[0139] (5) If the terminal does not reach the data server NDS, it will use the business card distribution information submitted by the status server STS to query all group numbers of the user from the HLR / VLR using the distributor's MSISDN number, and then query the group member list from the group call register GCR based on the group number; if it is a friend circle distribution, it will use the distributor's MSISDN number to query all single call friend user lists of the user from the subscriber recovery server SRS.

[0140] (6) The terminal does not arrive at the data server. The NDS collects all group numbers and all group member lists of the distributor, constructs a group user list or friend user list, caches the distributor's business card in the packingbox queue of all list users, and updates the user's NDR status.

[0141] (7) The State Server (STS) submits a group broadcast to the Cluster Exchange Center (MSC Server) to notify the recipient user to collect the business card.

[0142] (8) The user receiving the business card executes the download process and obtains the distributor's business card from the terminal's data server NDS through the CDSN data channel.

[0143] Combination Figure 5 A schematic diagram illustrating the process of distributing business cards to users based on their terminal access status, providing an example of this process.

[0144] Distribution process 1-3: The terminal SCS (Submit Card State) initiates the RACH Distribute MyCard status command, which arrives at the STS server via SCC. The SCC sends back the RRC AGCH Ack that the RACH has been received to the initiating user. The terminal confirms that the system has received the RACH and stops sending it again.

[0145] Distribution process 4: According to the job flow, STS stores the RACH status and sends a business card distribution instruction to the NDS server: Distribute My Card. The NDS Write module receives the instruction. If it is necessary to distribute business cards to friends, proceed to distribution process 5-6. If it is necessary to distribute business cards to group users, proceed to distribution process 7-10.

[0146] Distribution process 5-6: Friend query. The NDS Write module queries the AddressBook from the SRS using the distributor's MSISDN number to obtain the user's friend numbers and form a distribution list.

[0147] Distribution process 7-8: Group user query. The NDS Write module queries the HLR / VLR for all group numbers (Inquiry Groups) of the distributor using the distributor's MSISDN number. The HLR / VLR sends back the query result (Response Groups). The NDS Write module then obtains all the group numbers that the user has participated in.

[0148] In the distribution process 9-10, the NDS Write module queries the GCR for the group member numbers one by one using the group number (Inquiry Group Members). The GCR sends back the query result (Response Group Members). The NDS Write obtains a list of user numbers in all groups that the user has participated in, or his / her group user number list.

[0149] In distribution process 11, after NDS Write obtains the DistributedMembers List of friends or group users, it caches the Cards one by one into the Packingbox queue of the MSISDN index of that user, thus completing the Card distribution.

[0150] Distribution process 12, NDS Write sends Your Card Distributed back to STS;

[0151] In the distribution process 13-15, STS broadcasts the business card distribution information to all distribution users through the MSC Server, reminding users to collect it from their NDS.

[0152] When the user terminal is in the business card collection state, the business card collection process includes:

[0153] (1) The initiating user terminal uses RACH random access signaling to carry the "business card collection" status code to access the ground station system via the trunking public channel;

[0154] (2) The satellite channel controller (SCC) entity of the ground station access network uses RRC response to confirm that RACH has been received via downlink through the trunking common channel;

[0155] (3) The satellite channel controller (SCC) attaches a beam identifier to the RACH and submits it to the state server (STS). The state server (STS) parses the state code of the terminal access.

[0156] (4) The State Server STS parses the status code as "business card collection". If it is a group user business card collection, it uses the collector's MSISDN number to query the HLR / VLR for all group numbers of this user, and then queries the group call register GCR for the group member list based on the group number; if it is a friend circle user business card collection, it uses the collector's MSISDN number to query the subscriber recovery server SRS for all friend user lists of this user.

[0157] (5) The State Server (STS) collects all group numbers and all group member lists of the collector, constructs a group user list or friend list, and retrieves the business cards stored under their MSISDN numbers one by one according to the list, and hands over all the retrieved business cards to the terminal's unreachable data server (NDS).

[0158] (6) The terminal has not reached the data server NDS. According to the business card collection information submitted by the status server STS, the terminal caches all the received business card packing boxes in the packing box queue of the collector user and updates the user's NDR status.

[0159] (7) The State Server (STS) broadcasts the user collector's business card collection to the Cluster Exchange Center (MSC Server), notifying the collector that the user has collected the business card.

[0160] (8) The business card collector user's terminal does not reach the data server NDS download process. Through the data channel of the circuit data support node CDSN, the collector obtains all group user business cards.

[0161] Combination Figure 6 A schematic diagram illustrating the process of collecting user profile cards driven by terminal access status, providing an example of the terminal user status-driven profile card collection process.

[0162] In the collection process 1-3, the terminal SCS (Submit Card State) initiates a RACH Gather Cards status command, which arrives at the STS server via SCC. The SCC sends back the RRC AGCH Ack that the RACH has been received to the initiating user. The terminal confirms that the system has received the RACH and stops sending it again. If collecting the business cards of friends, the process proceeds to the collection process 4-5. If collecting the business cards of group users, the process proceeds to the collection process 6-9.

[0163] Collection process 4-5: Collect friend list. STS queries SRS for all friend numbers of the user in AddressBook based on the collector's MSISDN number, forming the collection list;

[0164] Collection process 6-7: Collect the list of group users. STS queries HLR / VLR for all group numbers of the collector (Inquiry Groups) based on the collector's MSISDN number. HLR / VLR sends back the query result (Response Groups). STS then obtains all the group numbers that the user has participated in.

[0165] In the collection process 8-9, STS queries GCR one by one for the group number, using the group number as Inquiry GroupMembers. GCR sends back the query result, Response Group Members. STS then obtains a list of user numbers in all groups that the user has participated in, or his / her group user number list.

[0166] In collection process 10, after STS obtains the list of friends or group members of the user being collected, it retrieves the card one by one from the MSISDN index card storage of the user on this server and transfers it to the NDS Write module of the NDS server.

[0167] Collection process 11: The NDS Write module writes all collected business cards to the NDS based on the collector's number.

[0168] Packingbox queue;

[0169] Collection process 12: The NDS Write module sends a message back to STS indicating that the collection is complete and Cards have been cached.

[0170] In the collection process 13-15, STS broadcasts the collected business card information to the collector user through the MSC Server, reminding him to collect it from the NDS.

[0171] When the user terminal access status is business card exchange, it first determines whether the 4-bit counterpart code number in the status information has been bound to the MSISDN number. If it has not been bound, the MSISDN number binding is performed. If it has been bound, the business card exchange process is initiated using RACHInformation.

[0172] The process for binding the MSISDN number includes:

[0173] (1) Use the unused 4-bit encoded numbers in a cyclical manner to bind the other party's MSISDN number;

[0174] (2) When all 4 bits of the code are occupied, the original binding of each code is released in a loop, and the MSISDN number of the other party is replaced and bound.

[0175] (3) Pack the entire table of coded numbers into a packaging box and prepare to send it to the State Server (STS);

[0176] (4) Pack the “business card exchange” information, including the other party’s MSISDN number and the local MSISDN number, into a packing box, and put it together with the full table of coded numbers into the data cargo container to be uploaded to the status server STS;

[0177] (5) Using the data cargo transshipment protocol, the data cargo container is transshipped to the Circuit Data Support Node (CDSN);

[0178] (6) The Circuit Data Support Node (CDSN) delivers the data cargo container to the State Server (STS).

[0179] (7) The State Server (STS) stores the packing boxes in the data cargo container and the full table of the coding numbers in the packing boxes.

[0180] The process of initiating a business card exchange using RACH is as follows:

[0181] (1) The initiating user uses RACH random access signaling to carry the "business card exchange" status code to access the ground station system via the trunking public channel;

[0182] (2) The ground station access network satellite channel controller (SCC) entity uses RRC response to confirm that RACH has been received via downlink through the trunking common channel;

[0183] (3) The satellite channel controller (SCC) attaches a beam identifier to the RACH and submits it to the state server (STS). The state server (STS) parses the state code of the terminal access.

[0184] (4) The State Server (STS) parses the status code as "business card exchange" and executes the business card exchange process.

[0185] The business card exchange process includes:

[0186] (1) The State Server (STS) retrieves the business card based on the MSISDN number of the business card initiator and delivers it to the Terminal Data Server (NDS) that has not yet arrived, requesting it to put the business card into the Packingbox queue of the business card exchange recipient's MSISDN.

[0187] (2) The State Server (STS) retrieves the business card of the other party based on the MSISDN number in the business card exchange and hands it to the Terminal Data Server (NDS) which has not yet arrived, requesting it to put the business card into the Packingbox queue of the MSISDN that initiated the business card exchange.

[0188] (3) The State Server (STS) sends a business card exchange broadcast notification to the business card exchange party through the Cluster Exchange Center (MSC Server);

[0189] (4) When both parties receive or do not receive a broadcast notification, they will obtain each other's business card information and complete the business card exchange if the terminal has not yet reached the data server NDS data.

[0190] Combination Figure 7 A schematic diagram illustrating the terminal access status-driven business card exchange process, with an example to illustrate the terminal user status-driven business card exchange process.

[0191] In the exchange process 1-3, the terminal SCS (Submit Card State) initiates the RACH Exchange Card status command, which arrives at the STS server via SCC. The SCC sends back the RRC AGCH Ack that the RACH has been received to the initiating user. The terminal confirms that the system has received the RACH and stops sending it again.

[0192] In the exchange process 4, STS submits Card1 with number MSISDN 1 to the NDS Write module, instructing it to put the card into the MSISDN 2 Packingbox queue for caching;

[0193] In the exchange process 5, the NDS Write module writes the business card into the MSISDN 2 Packingbox queue;

[0194] In the exchange process 6, STS submits Card2 (MSISDN 2) to the NDS Write module, instructing it to place the card in the MSISDN 1 Packingbox queue for caching.

[0195] In the exchange process 7, the NDS Write module writes the business card into the MSISDN 1 Packingbox queue;

[0196] In the exchange process 8, the NDS Write module sends a message to STS confirming that the card exchange is complete.

[0197] In the exchange process 9-11, STS broadcasts the business card exchange information to the user through the MSC Server, reminding him to retrieve it from his NDS.

[0198] Combination Figure 5-7 The process of business card distribution, collection, and exchange involves changing the NDR status of each end user involved in the business card interaction, prompting the user to download NDS data. Once the user downloads their NDS data, they obtain the user business card information they need.

[0199] Combination Figure 8 This diagram illustrates the process of downloading and collecting business cards from NDS, driven by terminal access status.

[0200] 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.

[0201] 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.

[0202] 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.

[0203] 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.

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

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

[0206] 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.

[0207] 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.

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

[0209] 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, obtains the collected user business cards, and returns to the cluster idle state.

[0210] 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 trunking terminal access status-driven user business card 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), HLR / VLR Server, Group Call Register (GCR), and Subscriber Recovery Server (SRS). The State Server (STS) stores the business cards reported by the user based on the user's MSISDN number and performs business card interaction based on the user terminal access status driver. The State Server (STS) transfers the business card data to be distributed to the terminal's unreached data server (NDS) based on the interaction information in the RACH information. The Status Server (STS) sends business cards and notifications to the receiving users through the Cluster Exchange Center (MSC Server). The Circuit Data Support Node (CDSN) is used as the transmission carrier entity for user business card information. The business card recipient user obtains business card data from the terminal's unreachable data server (NDS) through the Circuit Data Support Node (CDSN). The Satellite Channel Controller (SCC) is an access network entity used to provide RACH information related to user business card interaction driving information status. The HLR / VLR server is used to provide the status server STS and the data server NDS (where the terminal has not arrived) with a query service for the group number of the cluster group corresponding to the user terminal, so as to obtain a detailed list of all cluster groups that the user terminal participates in. The group call register (GCR) is used to provide a cluster group member list query service for the status server (STS) and the terminal not arriving data server (NDS). The subscriber recovery server (SRS) is used to provide a query service for all friend user numbers and address books for the status server (STS) and the terminal not arrived data server (NDS).

2. The satellite cluster terminal access status-driven user business card interaction system according to claim 1, characterized in that, The user profile includes: user avatar, user name, user satellite phone number, user satellite terminal cluster identifier, and remarks. After the user finishes editing the user card, the user card information is uploaded to the state server STS for storage via the circuit data support node CDSN. When a user's business card is updated, the updated business card is uploaded to the State Server (STS) via the Circuit Data Support Node (CDSN) for overwriting storage.

3. The satellite cluster terminal access status-driven user business card interaction system according to claim 1, characterized in that, The user terminal access status is the status information carried in the uplink random access request (RACH) information of the user terminal that initiated the business card service from the ground station satellite feeder circuit. The status information contains a total of 55 bits of encoded information, of which 37 bits are address identifiers, 4 bits are message type, and 14 bits are status encoding information, including three types of status encoding driven by business card service interaction: (1) Business card distribution, including 4 bits of message type, 10 bits of user avatar code, 37 bits of publisher MSISDN number, and 4 bits of operation code. The operation code of business card distribution expresses the following: the publisher distributes the business card to his group user circle or friend user circle. The user who receives the business card needs to reset the user avatar or update the business card according to the status code. The purpose of business card distribution is that the publisher has changed the avatar or updated the business card content, and his group users or friend users need to update synchronously. (2) Business card collection, including 4 bits of message type, 1 bit of operation code, 4 bits of code number, 9 bits of business card collection sub-code, and 37 bits of requester MSISDN number. The operation code of business card collection expresses the content: the requester collects his group user business cards or friend circle user business cards. The purpose of business card collection is that the requester has established or joined a cluster group and he needs to add business card information for all members of this cluster group. (3) Business card exchange, including 4 bits of message type, 1 bit of operation code, 4 bits of counterpart code number, 9 bits of business card exchange sub-code and 37 bits of requester MSISDN number. The business card exchange operation code and business card exchange sub-code together represent the exchange of business cards. Since the RACH information cannot carry all 37 bits of the exchanged party's MSISDN number, the 4 bits of counterpart code number during business card exchange is his / her MSISDN number index. The state server STS further parses to obtain the counterpart's actual number. The requester's MSISDN number is the user number of the initiating party. The purpose of business card exchange is that the requester has established a new user friend relationship and needs to exchange business card information with each other.

4. The satellite cluster terminal access status-driven user business card interaction system according to claim 3, characterized in that, When the user terminal access status is business card distribution, the business card distribution process includes: (1) The initiating user terminal uses RACH random access signaling to carry the "business card distribution" status code to access the ground station system via the trunking common channel; (2) The satellite channel controller (SCC) entity of the ground station access network uses RRC response to confirm that RACH has been received via downlink through the trunking common channel; (3) The satellite channel controller (SCC) attaches a beam identifier to the RACH and submits it to the state server (STS). The state server (STS) parses the state code of the terminal access. (4) The State Server (STS) parses the status code as "business card distribution", retrieves the business card stored by the initiator under its MSISDN number name, delivers it to the terminal's unreached data server (NDS), and notifies it to perform the business card distribution operation. (5) If the terminal does not reach the data server NDS, it will use the business card distribution information submitted by the status server STS to query all group numbers of the user from the HLR / VLR using the distributor's MSISDN number, and then query the group member list from the group call register GCR based on the group number; if it is a friend circle distribution, it will use the distributor's MSISDN number to query all single call friend user lists of the user from the subscriber recovery server SRS. (6) The terminal does not arrive at the data server. The NDS collects all group numbers and all group member lists of the distributor, constructs a group user list or friend user list, caches the distributor's business card in the packingbox queue of all list users, and updates the user's NDR status. (7) The State Server (STS) submits a group broadcast to the Cluster Exchange Center (MSC Server) to notify the recipient user to collect the business card. (8) The user receiving the business card executes the download process and obtains the distributor's business card from the terminal's data server NDS through the CDSN data channel.

5. The satellite cluster terminal access status-driven user business card interaction system according to claim 3, characterized in that, When the user terminal is in the business card collection state, the business card collection process includes: (1) The initiating user terminal uses RACH random access signaling to carry the "business card collection" status code to access the ground station system via the trunking public channel; (2) The satellite channel controller (SCC) entity of the ground station access network uses RRC response to confirm that RACH has been received via downlink through the trunking common channel; (3) The satellite channel controller (SCC) attaches a beam identifier to the RACH and submits it to the state server (STS). The state server (STS) parses the state code of the terminal access. (4) The State Server STS resolves the status code to "business card collection". If it is a group user business card collection, it uses the collector's MSISDN number to query the HLR / VLR for all group numbers of this user, and then queries the group call register GCR for the group member list based on the group number; if it is a friend circle user business card collection, it uses the collector's MSISDN number to query the subscriber recovery server SRS for all friend user lists of this user. (5) The State Server (STS) collects all group numbers and all group member lists of the collector, constructs a group user list or friend list, and retrieves the business cards stored under their MSISDN numbers one by one according to the list, and hands over all the retrieved business cards to the terminal's unreachable data server (NDS). (6) The terminal has not reached the data server NDS. According to the business card collection information submitted by the status server STS, the terminal caches all the received business card packing boxes in the packing box queue of the collector user and updates the user's NDR status. (7) The State Server (STS) broadcasts the user collector's business card collection to the Cluster Exchange Center (MSC Server), notifying the collector that the user has collected the business card. (8) The business card collector user's terminal does not reach the data server NDS download process. Through the data channel of the circuit data support node CDSN, the collector obtains all group user business cards.

6. The satellite cluster terminal access status-driven user business card interaction system according to claim 3, characterized in that, When the user terminal access status is business card exchange, it first determines whether the 4-bit counterpart code number in the status information has been bound to the MSISDN number. If it is not bound, the MSISDN number binding is performed. If it is bound, the business card exchange process is initiated using RACH.

7. The satellite cluster terminal access status-driven user business card interaction system according to claim 6, characterized in that, The process for binding the MSISDN number includes: (1) Use the unused encoded numbers in the 4-bit encoding in a loop to bind the other party's MSISDN number; (2) When all 4 bits of the code are occupied, the original binding is released in a loop and the other party's MSISDN number is used as the replacement binding; (3) Pack the entire table of coded numbers into a packaging box and prepare to send it to the State Server (STS); (4) Pack the "business card exchange" information, including the other party's MSISDN number and the local MSISDN number, into a packing box, and put it together with the full table of coded numbers into the data cargo container to be uploaded to the status server STS; (5) Using the data cargo transshipment protocol, the data cargo container is transshipped to the Circuit Data Support Node (CDSN); (6) The Circuit Data Support Node (CDSN) delivers the data cargo container to the State Server (STS). (7) The State Server (STS) stores the packing boxes in the data cargo container and the full table of the coding numbers in the packing boxes.

8. The satellite cluster terminal access status-driven user business card interaction system according to claim 6, characterized in that, The process of initiating a business card exchange using RACH information is as follows: (1) The initiating user uses RACH random access signaling to carry "business card exchange" information status code to access the ground station system via the trunking public channel; (2) The ground station access network satellite channel controller (SCC) entity uses RRC response to confirm that RACH has been received via downlink through the trunking common channel; (3) The satellite channel controller (SCC) attaches a beam identifier to the RACH and submits it to the state server (STS). The state server (STS) parses the state code of the terminal access. (4) The State Server (STS) parses the status code as "business card exchange" and executes the business card exchange process.

9. The satellite trunking terminal access status-driven user business card interaction system according to claim 6, characterized in that, The business card exchange process includes: (1) The State Server (STS) retrieves the business card based on the MSISDN number of the business card initiator and delivers it to the Terminal Data Server (NDS) that has not yet arrived, requesting it to put the business card into the Packingbox queue of the business card exchange recipient's MSISDN. (2) The State Server (STS) retrieves the business card of the other party based on the MSISDN number in the business card exchange and hands it to the Terminal Data Server (NDS) which has not yet arrived, requesting it to put the business card into the Packingbox queue of the MSISDN that initiated the business card exchange. (3) The State Server (STS) sends a business card exchange broadcast notification to the business card exchange party through the Cluster Exchange Center (MSC Server); (4) When both parties receive or do not receive a broadcast notification, they will obtain each other's business card information and complete the business card exchange if the terminal has not yet reached the data server NDS data.

Images