Method and device for exchanging business cards in cloud address book based on communication network

Abstract

The application discloses a kind of based on the method and device of card exchange in cloud address book of communication network, to solve the privacy disclosure risk, insufficient convenience and lack of traceability etc. existing in prior art digital business card exchange technology.The application constructs exclusive core signaling network by means of operator converged communication RCS protocol, without relying on Internet APP, and transmits business card data through IMS core network.After being authorized by strong identity authentication, call detail record and personal information are encrypted and synchronized to cloud address book, forming personal private cloud space.When exchanging, user can trigger the process by inputting target mobile phone number, and the system completes double confirmation according to preset rules, realizes safe exchange of business card through encrypted channel, and exchange log is recorded in real time.The application supports users without cloud address book to complete exchange through SIM card application, and has both speed and security, providing efficient and secure business card exchange service for users.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a method and apparatus for exchanging business cards in a cloud address book based on a communication network. Background Technology

[0002] Electronic business cards, as an important tool for digital social networking, are widely used in business communication. With the development of communication technology, existing technologies facilitate business card exchange via internet apps or near-field communication (NFC), but these suffer from drawbacks such as privacy leaks, cumbersome operations, and insufficient compliance. Among related technologies, location-based exchange spaces enable multi-person exchanges by generating preview information within a specific physical range, while the MIUI 7 system uses a full contact list scan to trigger the exchange. Specifically, these solutions construct a collaborative system from data collection to transmission, covering key aspects such as SIM card integration, cloud storage, and policy matching. The integration of carrier-grade communication networks and cloud services is becoming an important direction for technological evolution, but existing technologies have not yet formed a complete privacy protection chain.

[0003] However, existing business card exchange methods directly transmit data via the internet without establishing carrier-grade encryption mechanisms. This can lead to man-in-the-middle attacks or data misuse due to a lack of access control policies. Specifically, existing technologies typically acquire data by monitoring user behavior, but this carries the risk of unauthorized data scraping; cloud-stored business card data lacks access control and may be misused by third parties; and end-to-end encryption using internet transmission channels is easily cracked. Therefore, existing solutions struggle to meet GDPR and other compliance requirements in cross-border data transmission scenarios, and the exchange process lacks complete logging, making it impossible to trace data flow. While iOS 26's AirDrop feature enables near-field exchange, it is limited by physical distance; MIUI 7's full contact scan method lacks a minimal data collection strategy, posing a risk of privacy abuse. These technical deficiencies directly impact user trust in electronic business cards, hindering their large-scale application in sensitive industries such as healthcare and finance. Summary of the Invention

[0004] The present invention aims to at least partially solve one of the technical problems in the related art.

[0005] Therefore, the first objective of this invention is to propose a method for exchanging business cards in a cloud address book based on a communication network.

[0006] Another objective of this invention is to provide a device for exchanging business cards in a cloud address book based on a communication network.

[0007] The third objective of this invention is to provide a computer device.

[0008] A fourth objective of this invention is to provide a non-transitory computer-readable storage medium.

[0009] To achieve the above objectives, a first aspect of the present invention proposes a method for exchanging business cards in a cloud address book based on a communication network, comprising:

[0010] S1, build a cloud address book system based on the operator's core signaling network, establish a communication connection with the billing system through the RCS protocol, and form a business card data transmission channel independent of the Internet;

[0011] S2 collects users' personal information through SIM card applications or address book apps and generates encrypted personal business card data. It then synchronizes the encrypted data with call records in the billing system to the user's exclusive cloud space to establish a structured cloud address book.

[0012] S3: When a user enters the target user's mobile phone number, the registration status of the target user's cloud address book and the business card exchange rules are verified through an encrypted query interface. Based on the dual confirmation mechanism, the permission granting operation is performed in the cloud and the business card exchange process is triggered.

[0013] S4 records complete log information of the exchange event, including the exchange time, initiator device identifier, receiver device identifier, and data access permission change records, and achieves traceability of the exchange process through the operator's dedicated channel.

[0014] In one embodiment of the present invention, S2 includes:

[0015] S21, when collecting users' personal information through SIM card applications, adopts a strong identity authentication mechanism, including mobile phone number verification, SMS verification code verification and service password confirmation;

[0016] S22, when synchronizing encrypted personal business card data and billing system call records to the cloud space, uses the AES-256 algorithm to encrypt the data end-to-end and uses the TLS1.3 protocol to ensure the security of the transmission channel.

[0017] In one embodiment of the present invention, S3 includes:

[0018] S31, when the length of the mobile phone number entered by the user meets the requirements... When the input is paused, a query request is sent to the cloud address book service platform via an HTTPS encrypted interface;

[0019] S32, based on the target user's preset business card exchange rules, if set to "confirmation required", will push an encrypted push notification to all of the target user's online devices and wait for the user's authorization response.

[0020] In one embodiment of the present invention, S4 includes:

[0021] S41, when recording complete log information of the exchange event, includes the IP address of the initiating device, the IMEI identifier of the receiving device, and the hash value of the exchange operation;

[0022] When transmitting log data through the operator's dedicated channel, S42 uses timestamp encryption technology to ensure that log records are tamper-proof and traceable.

[0023] To achieve the above objectives, a second aspect of the present invention provides an apparatus for exchanging business cards in a cloud address book based on a communication network, comprising:

[0024] The cloud address book construction module is used to build a cloud address book system based on the operator's core signaling network. It establishes a communication connection with the billing system through the RCS protocol, forming a business card data transmission channel independent of the Internet.

[0025] The user information collection and encryption synchronization module is used to collect users' personal information through SIM card applications or address book APPs and generate encrypted personal business card data. The encrypted data and call records in the billing system are synchronized to the user's exclusive cloud space to establish a structured cloud address book.

[0026] The permission verification and process triggering module is used to verify the registration status of the target user's cloud address book and the business card exchange rules through an encrypted query interface when the user enters the target user's mobile phone number. Based on the double confirmation mechanism, the module performs permission granting operations in the cloud and triggers the business card exchange process.

[0027] The log recording and transmission module is used to record complete log information of the exchange event, including the exchange time, the initiator device identifier, the receiver device identifier, and data access permission change records, and to achieve traceability of the exchange process through the operator's dedicated channel.

[0028] This invention discloses a method and apparatus for exchanging business cards in a cloud address book based on a communication network. By using a cloud address book based on the operator's core signaling network, the exchange of electronic business cards is realized, which effectively protects the privacy, security and compliance of user data during transmission and storage, while improving the convenience and traceability of business card exchange.

[0029] To achieve the above objectives, a third aspect of this application provides a computer device comprising a processor and a memory; wherein the processor runs a program corresponding to the executable program code stored in the memory, for implementing a method for exchanging business cards in a cloud address book based on a communication network as described in the first aspect embodiment.

[0030] To achieve the above objectives, a fourth aspect of this application provides a non-transitory computer-readable storage medium storing a computer program that, when executed by a processor, implements a method for exchanging business cards in a cloud address book based on a communication network as described in the first aspect embodiment.

[0031] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0032] Figure 1 This is a flowchart of a method for exchanging business cards in a cloud address book based on a communication network according to an embodiment of the present invention;

[0033] Figure 2 This is a schematic diagram of the process of exchanging electronic business cards between users A and B according to an embodiment of the present invention;

[0034] Figure 3 This is a flowchart illustrating the synchronization process between communication details and business cards according to an embodiment of the present invention;

[0035] Figure 4 This is a flowchart of the user A / B business card synchronization process according to an embodiment of the present invention;

[0036] Figure 5 This is a flowchart illustrating the process of synchronizing business cards with card applications via SIM card storage according to an embodiment of the present invention.

[0037] Figure 6 This is a structural diagram of a device for exchanging business cards in a cloud address book based on a communication network, according to an embodiment of the present invention.

[0038] Figure 7 It is a computer device according to an embodiment of the present invention. Detailed Implementation

[0039] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

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

[0041] The following describes, with reference to the accompanying drawings, a method and apparatus for exchanging business cards in a cloud address book based on a communication network, according to an embodiment of the present invention.

[0042] Example 1

[0043] Figure 1 This is a flowchart illustrating a method for exchanging business cards in a cloud address book based on a communication network, according to an embodiment of the present invention. Figure 1 As shown, it includes:

[0044] S1 constructs a cloud address book system based on the operator's core signaling network, establishes a communication connection with the billing system through the RCS protocol, and forms a business card data transmission channel independent of the Internet.

[0045] Specifically, this step involves building a cloud-based contact list system based on the operator's core signaling network and establishing a communication connection with the billing system via the RCS protocol, thereby forming a business card data transmission channel independent of the internet. This technical solution utilizes the operator's existing communication infrastructure to achieve efficient and secure transmission of business card data, while ensuring the controllability and compliance of user privacy.

[0046] Furthermore, the RCS protocol, as a communication enhancement standard defined by 3GPP, supports end-to-end transmission of rich media messages, relying on the operator's IMS (IP Multimedia Subsystem) network architecture. By integrating an RCS client into user terminals (such as mobile phones) and deploying an RCS communication gateway on the operator's side, the system can transmit business card data in the form of rich media messages (vCard format) within the communication network. Business card data must be encrypted using AES-256 before sending to ensure anti-eavesdropping and anti-tampering capabilities during transmission. After receiving the message, the receiving end decrypts and parses it using the RCS client and displays it as a clickable electronic business card in the call or SMS interface. Users can save it to their local address book or sync it to their cloud address book with one click.

[0047] Furthermore, the transmission of business card data must meet the QoS (Quality of Service) standards of the operator's network, such as controlling transmission latency within a specified range. Within milliseconds, the message packet loss rate should be lower than Meanwhile, the maximum length of rich media messages supported by the RCS protocol is [not specified]. The data in the business card must be compressed to this limit, typically using the GZIP compression algorithm, which can achieve a compression rate of over 60%. In addition, the system must support a minimum number of concurrent connections. This is to address scenarios where a large number of users simultaneously initiate business card exchange requests.

[0048] Furthermore, this step applies to converged communication services provided by operators, especially in scenarios such as user dialing, SMS recipient input, and contact list editing. The system can monitor the user's input mobile phone number in real time and, if the length condition is met (e.g., ...), ... (position) and anti-shake latency (such as) The business card exchange process is triggered after milliseconds. This process does not rely on third-party internet services and is completed solely through the operator's dedicated signaling channel, making it suitable for scenarios such as government and enterprise users and the financial industry with high data security requirements.

[0049] Furthermore, this step, through the integration of the RCS protocol with the billing system, constructs a highly secure, low-latency, and strongly authenticated business card data transmission channel, effectively resolving the privacy leakage and compliance risks inherent in existing internet address books during data transmission. Simultaneously, the independence of this channel ensures the stability and reliability of the business card exchange process, providing a solid foundation for subsequent mechanisms such as automatic updates and two-way confirmation.

[0050] S2 collects users' personal information through SIM card applications or address book apps and generates encrypted personal business card data. It then synchronizes the encrypted data with call records in the billing system to the user's exclusive cloud space, establishing a structured cloud address book.

[0051] Specifically, in some implementations, user personal information is collected and encrypted personal business card data is generated through SIM card applications or contact apps. This step is based on the converged communication protocols (such as RCS protocol) and SIM card application interfaces (such as USIM card application programming interfaces) provided by the operator to achieve the collection and structured processing of user identity information. Specifically, user information includes, but is not limited to, name, phone number, email address, job title, company name, etc. This information is entered through the local editing interface of the SIM card application or contact app, and after the user completes the editing, the system encapsulates it according to a preset data structure (such as JSON or XML format) to form structured personal business card data.

[0052] Furthermore, to ensure data security during transmission and storage, the system employs symmetric encryption algorithms (such as AES-256) or asymmetric encryption algorithms (such as RSA-2048) to encrypt the business card data. The encryption key can be generated based on user identity information (such as a phone number hash) or dynamically allocated through the operator's Security Key Management Service (SKMS). The encrypted business card data then communicates with the billing system via the operator's IMS core network, synchronizing call records and the encrypted business card data to the user's dedicated cloud space. This cloud space is a private cloud storage environment managed by the operator, supporting multi-device synchronization and offline access, and features an encrypted transmission channel based on the HTTPS protocol, ensuring data integrity and confidentiality during the upload process.

[0053] Furthermore, the key length of the encryption algorithm should be no less than 256 bits to meet the current industry's basic requirements for data security (such as the ISO / IEC 18033-3 standard). The synchronization frequency can be set to real-time or periodic (e.g., once every 30 minutes), depending on the operator's network load and user privacy preferences. In addition, to prevent data leakage, the system employs an end-to-end encryption mechanism during synchronization to ensure that data exchange between the billing system and the cloud address book server is not intercepted or tampered with by third parties.

[0054] Furthermore, this step can be deployed on smartphones that support RCS or SIM card applications provided by operators, and is suitable for automatically triggering the business card exchange process in scenarios such as dialing, SMS recipient input, and contact editing. By synchronizing user information and call records to the cloud address book, not only is the centralized management capability of user data improved, but a data foundation is also provided for subsequent business card exchange logic based on the communication network. Furthermore, this step, through encryption and access control mechanisms, effectively avoids the privacy leakage risks caused by direct data retrieval in existing technologies, achieving controllable sharing and secure storage of user data, laying a core foundation for building a traceable and authoritative cloud address book system.

[0055] Furthermore, S2 includes:

[0056] S21 employs a strong authentication mechanism when collecting user personal information through SIM card applications, including verification of the device number, SMS verification code verification, and service password confirmation.

[0057] Specifically, in some implementations, when collecting user personal information through SIM card applications, a strong authentication mechanism is employed, including verification of the user's mobile phone number, SMS verification code verification, and service password confirmation. This technology is based on a carrier-grade security authentication system to ensure the authenticity of the user's identity and the legality of operations during data access and exchange. This step enhances the security of user information collection through multi-factor authentication, preventing unauthorized access and data leakage.

[0058] Furthermore, the device number verification first matches the International Mobile Subscriber Identity (IMSI) embedded in the SIM card with the operator's user database to confirm the consistency between the current device and the user's identity. SMS verification code verification involves the cloud address book service platform sending a one-time verification code to the user's currently bound mobile number. The user must enter this verification code in the SIM card application or the accompanying app to complete the second layer of authentication. Service password confirmation requires the user to enter a service password pre-set with the operator. This password is typically a 6-12 digit or letter combination with high complexity requirements to prevent brute-force attacks.

[0059] Furthermore, the delay in sending SMS verification codes should be controlled within [a certain timeframe]. The validity period of the verification code is usually set to seconds to ensure a smooth user experience; The password must be within a reasonable timeframe, ensuring verification is completed within seconds; the service password's complexity must meet the operator's security standards, such as containing at least [missing information - likely a number]. The character is a bit and needs to be changed regularly (e.g., (Mandatory modification within 1 day). Furthermore, the authentication process must adhere to the security mechanisms defined in the GSMA-defined RCS protocol to ensure that the communication process complies with standards such as 3GPP TS26.234.

[0060] Furthermore, this strong identity authentication mechanism is widely used in critical operations such as initial registration of cloud address books, updating personal information, or triggering business card exchange processes. For example, when a user edits or uploads an electronic business card through the SIM card application, the system will automatically trigger the above-mentioned triple authentication process to ensure that the operation is initiated by the user, thereby effectively preventing malicious tampering or identity theft.

[0061] Furthermore, this step significantly enhances the security of user data collection and business card exchange through a multi-layered authentication mechanism, ensuring that user privacy information is tamper-proof and impersonation-proof during transmission and storage. Simultaneously, this mechanism is closely integrated with the operator's core network, leveraging its existing identity verification infrastructure to reduce system deployment costs and improve overall security, providing a solid foundation for the automation and compliance of subsequent business card exchange processes.

[0062] S22, when synchronizing encrypted personal business card data and billing system call records to the cloud space, uses the AES-256 algorithm to encrypt the data end-to-end and uses the TLS1.3 protocol to ensure the security of the transmission channel.

[0063] Specifically, in some implementations, this invention employs the AES-256 algorithm for end-to-end encryption of encrypted personal business card data and billing system call records during the synchronization process to the cloud space, and uses the TLS 1.3 protocol to ensure the security of the transmission channel. This step is based on the synergistic application of symmetric encryption and transport layer security protocols.

[0064] Furthermore, AES-256 is a widely used symmetric encryption algorithm in the field of data encryption. Its encryption strength reaches a 256-bit key length, conforms to NIST (National Institute of Standards and Technology) standards, and possesses extremely high resistance to attacks. In this solution, both the user's local business card data and call details from the billing system are encrypted using the AES-256 algorithm before being uploaded to the cloud address book server. The encryption process is typically completed on the user's device or in the operator's billing system, using the user's exclusive encryption key to perform block encryption on the data, ensuring that the data is already encrypted before transmission, thus achieving end-to-end encryption.

[0065] Furthermore, the system adopts the TLS 1.3 protocol, the latest transport layer security standard released by the IETF (Internet Engineering Task Force). Compared to TLS 1.2, it has significant optimizations in handshake procedures, cipher suite selection, and forward secrecy mechanisms. TLS 1.3, through the use of modern encryption algorithms such as ECDHE, can complete the handshake within 1-RTT, greatly improving transmission efficiency while ensuring that the communication channel is not eavesdropped on or tampered with by man-in-the-middle (MITM) attacks during transmission.

[0066] Furthermore, the AES-256 encryption block size is 128 bits, and the key length is 256 bits. The encryption process uses modes such as CBC (Cipher Block Chaining) or GCM (Galois / Counter Mode). GCM mode supports simultaneous encryption and authentication, making it suitable for real-time data transmission scenarios with high security requirements. TLS 1.3 supports 0-RTT data transmission during the handshake phase, with handshake latency controllable to within 100ms (depending on network conditions). It also disables insecure encryption algorithms such as RC4 and 3DES by default, ensuring modern security standards for the transmission channel.

[0067] Furthermore, this step is primarily applied to scenarios where users upload local contact information and call logs to the operator's dedicated cloud contact server via SIM card applications or contact apps. For example, after a user completes strong identity authentication (such as their own phone number + SMS verification code + service password) through the operator's app, the system will automatically encrypt and upload their call details and contact data to the cloud. This process supports multi-device synchronization, ensuring that users can access their encrypted communication data on different terminals, while preventing data from being exposed to third-party network nodes during transmission.

[0068] Furthermore, this step, through the combined application of AES-256 and TLS 1.3, not only achieves dual encryption protection for data during storage and transmission, but also ensures the secure isolation and compliance of contact data within the operator's core network. Its innovation lies in applying carrier-grade encryption and transmission mechanisms to the synchronization of personal contact data, thereby constructing a cloud contact system with a privacy protection chain, effectively solving problems such as data leakage, abuse of permissions, and insecure transmission channels in existing technologies.

[0069] S3: When a user enters the target user's mobile phone number, the system verifies the target user's cloud address book registration status and business card exchange rules through an encrypted query interface. Based on a dual confirmation mechanism, the system performs permission granting operations in the cloud and triggers the business card exchange process.

[0070] Specifically, in some implementations, when a user enters a target user's mobile phone number, the system verifies the target user's registration status and business card exchange rules in the cloud address book through an encrypted query interface. This step is based on the collaborative mechanism between the signaling channel of the operator's core communication network and the cloud address book server. Specifically, when user B enters user A's mobile phone number on any input interface (such as the dial pad or new contact window) of their terminal device (such as a mobile phone), the system's integrated input monitoring module detects the input behavior. When the input pauses (e.g., a 300-millisecond anti-shake delay) and the number length reaches a preset threshold (e.g., ... When the bit is reached, the background encrypted query process is triggered.

[0071] Furthermore, this encrypted query interface employs a secure communication protocol provided by the operator. The number segment entered by user B is encrypted using algorithms such as AES-256 or SM4, and then sent to the cloud address book service platform via HTTPS or a dedicated secure channel provided by the operator. Upon receiving the encryption request, the server first performs decryption, then queries the core database to determine if the target number has been registered with a cloud address book account, and verifies whether the account status is "activated" or "exchangeable." Simultaneously, the system reads user A's preset business card exchange rules, such as whether automatic exchange is allowed and whether secondary confirmation is required.

[0072] Furthermore, the response time of the encrypted query interface should be controlled within 500 milliseconds to ensure smooth user interaction; the encryption algorithm must comply with the security standards of the State Cryptography Administration or NIST, and the key length must be no less than 256 bits to ensure the confidentiality and integrity of data during transmission. In addition, the system supports a multi-device synchronous authorization mechanism to ensure that the exchange rules set by user A on any device can be read and executed by the server in real time.

[0073] Furthermore, this step is suitable for users to quickly exchange electronic business cards in daily communication scenarios, such as when dialing, sending text messages, or adding contacts. There's no need to manually open third-party applications or perform complex settings; simply entering the phone number is enough to trigger the business card exchange and confirm permissions. This mechanism is particularly suitable for carrier-grade cloud address book services, and can be deeply integrated with SIM card applications, cloud phone systems, etc., to achieve unified business card management across terminals and networks.

[0074] Furthermore, this step, through encrypted querying and dual confirmation mechanisms, effectively prevents unauthorized access to business cards and data leakage, while improving user convenience and system response efficiency. Its innovation lies in embedding the business card exchange process into the communication network signaling channel, combined with cloud-based access control, achieving a secure, efficient, and automated business card exchange experience without relying on an internet app.

[0075] Furthermore, S3 includes:

[0076] S31, when the length of the mobile phone number entered by the user meets the requirements... When the input pauses, a query request is sent to the cloud address book service platform via an HTTPS encrypted interface.

[0077] Specifically, in some implementations, when the length of the user-input mobile phone number meets the requirements... When the user pauses input, the system sends a query request to the cloud address book service platform via an HTTPS encrypted interface. This step is the key triggering mechanism for the entire business card exchange process. Its technical implementation is based on a collaborative mechanism of input monitoring and conditional judgment. Specifically, when a user enters the target user's mobile phone number in the phone dialer interface, address book editing interface, or SMS recipient field, the system's integrated input monitoring module captures the input event in real time. To avoid frequent query requests, the system employs a debouncing mechanism, setting the input pause threshold to 300 milliseconds. That is, if a user pauses for more than this time interval after continuous input, the system determines that the input is complete and prepares to trigger a query.

[0078] Furthermore, the length of the input number is determined based on the following criteria: This is the minimum identification length set based on the mobile phone number, ensuring that the input content has preliminary number legitimacy. The HTTPS interface uses TLS 1.3 or higher encryption protocol to meet communication security standards (such as IETF RFC 8446). Request messages are encrypted using the AES-256-GCM algorithm to ensure data is protected against eavesdropping and tampering during transmission. The request header includes the user device's IMSI, IMEI, and carrier authentication token for server-side authentication and access control.

[0079] Furthermore, this step caters to users' needs for quickly exchanging business cards in everyday communication scenarios. For example, when entering a number on the dialer, the system can automatically trigger the business card search and exchange process, eliminating the need for users to manually open a dedicated business card application or perform complex operations. This mechanism is particularly suitable for carrier-grade cloud address book services, allowing for deep integration with SIM card applications or IMS communication protocols to achieve unified business card management across devices and terminals.

[0080] Furthermore, this step, through the combination of input monitoring and HTTPS encrypted communication, enables the instant triggering and secure transmission of the business card exchange process, significantly improving the convenience of user interaction and the security of data exchange.

[0081] S32, based on the target user's preset business card exchange rules, if set to "confirmation required", will push an encrypted push notification to all of the target user's online devices and wait for the user's authorization response.

[0082] Specifically, in some implementations, when the target user's preset business card exchange rule is set to "confirmation required," the system will push encrypted push notifications to all of the target user's online devices through a cloud address book platform based on the communication network, awaiting the user's authorization response. The technical implementation principle of this step is based on the carrier-grade Rich Communication Services (RCS) protocol, using a secure signaling channel provided by the IMS core network to achieve end-to-end encrypted communication and the collaborative operation of the user authorization mechanism.

[0083] Furthermore, when user A sets the business card exchange rule to "confirmation required," the cloud address book service platform, upon receiving user B's business card exchange request, will send an encrypted authorization notification to all of user A's online devices (such as mobile phones, tablets, etc.) via push notification services provided by the operator (such as VoLTE / ViLTE signaling channels or RCSPush-to-Talk mechanisms). This notification includes metadata such as the requester's mobile phone number, request timestamp, and request type, and is encrypted using symmetric encryption algorithms such as AES-256 or SM4 to ensure data confidentiality and integrity during transmission. The sending frequency and timeout mechanism of push notifications are configurable; for example, if no response is received from user A within 30 seconds, the request automatically expires, avoiding long waiting times that could negatively impact user experience.

[0084] Furthermore, the encryption strength of push notifications should meet carrier-grade security standards, with an encryption key length of no less than 256 bits, and the transmission latency of push notifications should be controlled within 100ms to ensure real-time response. In addition, the triggering conditions for push notifications include the length of the entered number. Position, input pause time These parameters, such as milliseconds (ms), can be dynamically adjusted based on the user's device's input method behavior to improve recognition accuracy and response efficiency.

[0085] Furthermore, this step applies to users exchanging business cards in remote communication scenarios. For example, when a user enters another person's number on the dial pad, the system automatically triggers the business card exchange process, but requires authorization from the business card holder. This mechanism is particularly suitable for industries with high privacy protection requirements, such as finance and healthcare, ensuring that user data during the business card exchange process is not accessed without authorization.

[0086] Furthermore, this step, through the combination of encrypted push notifications and user authorization mechanisms, achieves two-way confirmation and privacy protection in the business card exchange process, effectively preventing unauthorized data access and abuse, while enhancing users' control over their exchange behavior and strengthening the system's security and compliance.

[0087] S4 records complete log information of the exchange event, including the exchange time, initiator device identifier, receiver device identifier, and data access permission change records, and achieves traceability of the exchange process through the operator's dedicated channel.

[0088] Specifically, in some implementations, the step of "recording complete log information of the exchange event, including the exchange time, the initiator's device identifier, the receiver's device identifier, and data access permission change records, and achieving traceability of the exchange process through the operator's dedicated channel" in this invention ensures that the business card exchange process has complete traceability in terms of time, device, and permission dimensions by building an event log recording mechanism in the cloud address book service platform.

[0089] Furthermore, after User A and User B complete their business card exchange, the cloud address book service platform will automatically record the metadata of the exchange event. This includes: a timestamp of the exchange (recorded in UTC time format with millisecond precision), the unique identifier of the initiating device (such as IMSI, IMEI, or device fingerprint), the unique identifier of the receiving device, and records of data access permission changes during the exchange (such as whether the permissions were "read-only" or "updatable"). This information is transmitted through a dedicated carrier signaling channel (such as SIP message extension fields in the IMS network or specific AVPs in the Diameter protocol), ensuring it does not traverse the public internet, thereby enhancing security.

[0090] Furthermore, this step applies to scenarios where users exchange business cards remotely or near-field via cloud address books. For example, when a user enters the other party's number on the dialer interface, the system automatically triggers the exchange process. After the server completes permission matching and data synchronization, it records the exchange event in the cloud log system. This log can be queried by the user through a carrier-certified app and can also be used for compliance auditing or data traceability.

[0091] Furthermore, this step, by recording a complete log of the exchange event in the operator's dedicated channel, not only ensures the traceability of the business card exchange process but also provides reliable data support for subsequent privacy protection, data compliance review, and user behavior analysis. Moreover, this mechanism ensures users' control over their own data, complies with the requirements of data privacy regulations such as GDPR and CCPA regarding user data access and modification records, thereby enhancing system security and user trust.

[0092] Furthermore, S4 includes:

[0093] S41, when recording complete log information of the exchange event, includes the IP address of the initiating device, the IMEI identifier of the receiving device, and the hash value of the exchange operation.

[0094] Specifically, in the business card exchange process, recording complete log information of the exchange event is a key step in ensuring data traceability and user privacy control. This step ensures that each exchange operation is accurately recorded and used for subsequent auditing or policy adjustments by building a structured logging mechanism in the cloud address book service platform.

[0095] Furthermore, this logging mechanism is designed based on the operator's IMS core network and RCS protocol. When user A and user B complete their business card exchange, the cloud address book service platform automatically generates a log entry containing three core pieces of information: the initiating device's IP address, the receiving device's IMEI identifier, and the hash value of the exchange operation. The IP address identifies the location of the device initiating the exchange request within the network, typically in IPv4 or IPv6 format, and supports obtaining the real address through the operator's NAT traversal mechanism. The IMEI identifier uniquely identifies the receiving mobile device; it is a 15-digit number conforming to the 3GPP TS23.003 standard. The hash value of the exchange operation is generated by digesting the exchanged content using the SHA-256 algorithm, ensuring data integrity and immutability.

[0096] Furthermore, the IP address record must support carrier-grade address resolution and location identification, the IMEI must be validated through the carrier's device authentication interface, and the hash value must meet certain requirements. The encryption strength must be specified to meet the data security requirements of ETSI T103457. Furthermore, the timestamps for log entries must be accurate to the millisecond level to support sequential event tracking in high-concurrency scenarios.

[0097] Furthermore, this logging mechanism is widely applicable to carrier-grade cloud address book services, especially in scenarios involving cross-border data transmission, enterprise-level user management, or compliance auditing, providing a complete operational trajectory for data exchange. For example, when user A sets the exchange policy to "confirmation required," the cloud address book service platform simultaneously records user B's IP and IMEI information while pushing a confirmation notification, facilitating subsequent tracing of the source device and network environment of the exchange request.

[0098] Furthermore, this step, through structured logging, not only enhances the transparency and auditability of the business card exchange process but also provides users with device and network-based privacy controls, thereby effectively preventing unauthorized data access and abuse and enhancing the security and compliance of the entire cloud address book system.

[0099] When transmitting log data through the operator's dedicated channel, S42 uses timestamp encryption technology to ensure that log records are tamper-proof and traceable.

[0100] Specifically, in some implementations, timestamp encryption technology is used when transmitting log data through the operator's dedicated channel. The purpose is to ensure the log records are immutable and traceable during transmission and storage, thereby enhancing the overall security and compliance of the system. This step is technically implemented based on a combination of symmetric encryption and timestamp authentication. The specific operation is as follows: First, after the cloud address book service platform receives an encrypted business card exchange request, the system generates a high-precision timestamp based on the current time (e.g., a millisecond-level timestamp) and binds it to the log data (including the exchange time, the initiator's and receiver's phone numbers, and the exchange status). Subsequently, this timestamp and the log data are transmitted to the cloud through the operator's dedicated channel. During transmission, the data is encrypted using the AES-256 encryption algorithm. The encryption key is dynamically allocated by the operator's Key Management System (KMS), ensuring that an independent session key is used for each transmission, thereby improving resistance to replay attacks and man-in-the-middle attacks.

[0101] Furthermore, the implementation of timestamp encryption technology relies on a trusted time source deployed in the operator's network. Its time synchronization accuracy is typically controlled within ±50ms, conforming to the high-precision time synchronization standards of the IEEE 1588v2 (PTP) or NTP protocols. When log data is written to the cloud database, the system stores the timestamp along with the encrypted log data and performs log integrity verification through a hash chain or Merkle tree structure to ensure that the originality and consistency of the data can be verified during subsequent audits.

[0102] Furthermore, this step is primarily applied to logging and tracking during the business card exchange process, especially in scenarios involving the transmission of user privacy data, such as cross-device synchronization, remote exchange, and billing system data push. Through timestamp encryption, the system can generate a unique and verifiable record for each exchange, facilitating subsequent compliance reviews and data traceability.

[0103] Furthermore, this step not only enhances the credibility and security of log data but also provides users with a traceable exchange history, increasing transparency and control over the data exchange process. Simultaneously, because both timestamps and encryption mechanisms rely on the operator's core network, their security surpasses traditional internet transmission methods, effectively preventing data tampering and forgery.

[0104] The electronic business card privacy protection exchange method based on the communication network of this invention realizes the quick exchange of electronic business cards through the cloud address book based on the communication network, effectively improving the convenience of exchange and enhancing user privacy protection, and solving the security risks and physical distance limitations caused by the reliance on Internet transmission in the prior art.

[0105] Example 2

[0106] This invention provides a cloud address book based on a communication network, and uses the signaling channel used by the operator to establish calls and SMS messages to transmit and synchronize business card data. First, this invention utilizes the operator's converged communication protocol to construct a cloud address book with the operator's dedicated core signaling network, and enables it to connect with the billing system. Second, it utilizes this communication network to implement a method where a user can trigger a business card exchange process by entering the target user's mobile phone number.

[0107] In one embodiment of the invention, a transmission network based on the operator's core network needs to be established first. This network is a core signaling network at the same level as the user's voice and video calls, independent of internet apps, thus enabling secure and fast data exchange. After establishing the network communication protocol, users can edit their personal information through a SIM card application or a contact app. This information can generate personal business card data under the security of the communication network, and simultaneously generate a local contact list based on call records in the billing system. Both are then synchronized to the cloud to generate a cloud contact list. Utilizing the dedicated core network of the cloud contact list based on the communication network, when a user enters another user's mobile phone number, the user's electronic business card stored in the cloud contact list is synchronized to that user, and the user's electronic business card is retrieved. The basic process of exchanging business cards is as follows: Figure 2 As shown.

[0108] In one embodiment of the invention, the RCS protocol is used to establish a communication network for interaction between cloud address books and with the billing system and local storage. This requires the user's mobile phone to have RCS functionality built-in and the service activated. Business card data is transmitted via the operator's IMS core network as a special formatted rich media message, and is ultimately presented as a clickable and saveable electronic business card on the recipient's mobile phone's call / SMS interface. The entire process does not require the participation of other Internet protocols and is completed purely through the communication network signaling channel. The establishment of this protocol can effectively solve the information security problem during the transmission of call data and business card data.

[0109] Furthermore, the established communication network is combined with a cloud-based address book that stores personal contact information and address books in the cloud, and this communication network is used to achieve collaboration between local devices and the cloud address book. The first step is to establish a user data authorization exit point. Users complete strong identity authentication (such as their phone number + SMS verification code + service password) through the operator's provided app or card application, and explicitly authorize a new service: allowing the automatic encryption of the user's call details into a data file, which is then pushed to the user's designated personal cloud space, i.e., the user's cloud address book server. This is equivalent to opening a secure, automated data copy exit point for each authorized user on the billing system side. Subsequently, the data needs to be aggregated to the personal cloud space. The encrypted call and contact information data files are retrieved from the authorized exit point using the communication network, decrypted, structured, and actively uploaded to the same cloud space through the operator's dedicated channel. At this point, a complete data copy has been aggregated in the user's cloud address book server and supports synchronization to the card applications on all of the user's terminals and devices. This step, through a dedicated channel for authorization, also effectively solves the problem of user privacy protection. The specific synchronization process is as follows... Figure 3 As shown.

[0110] In one embodiment of the present invention, after obtaining call details from the cloud address book, the user selects the target user to exchange business cards with, and then enters the target user's mobile phone number to complete the business card exchange. The specific process is as follows: First, user B starts entering user A's mobile phone number on any input interface of the mobile phone (such as the dial pad, the new contact window, or the SMS recipient field). The mobile phone input method or address book module integrated with this service in the cloud address book and card application system will monitor the input box in real time. When an input pause is detected (such as a 300-millisecond delay for anti-shake) and the number length meets the conditions (such as ≥7 digits), a background query is triggered. Then, user B's mobile client encrypts the currently entered number fragment and sends it to the "cloud address book service platform" via the Internet for query. Subsequently, the cloud address book communication network service platform receives the encryption request, decrypts it, and obtains the number to be queried. The server queries its core database to see if the number has been registered and bound to a valid personal cloud address book account (i.e., user A's account), and checks whether the account stores exchangeable electronic business cards. At the same time, the service platform will read the business card exchange rules pre-set by user A.

[0111] If a match is successful and User A's policy allows for the exchange, the server will formally initiate an exchange request to User A's cloud address book account. If User A is set to "Auto-agree": the server automatically simulates User A and authorizes the exchange. If User A is set to "Confirmation Required": the server will push an encrypted notification to all of User A's online devices, such as mobile phones and tablets, for example: "User B wishes to exchange business cards with you. Do you agree?" After User A authorizes, they click the agreement notification on their device, and the authorization instruction is encrypted and returned to the cloud address book service platform. After obtaining authorization from both parties, the platform executes the core exchange operation. In addition, the platform will record the time of the exchange event, the exchange partner, and other information in both parties' account logs, establishing a connection for future possible functions such as "business card information update push."

[0112] After entering the phone number, if User B receives confirmation, it means they have triggered a business card exchange and received User A's business card. Clicking on the confirmation allows User B to further share their own business card. At this point, both User B and User A have each other's detailed information stored in their local phone contacts, and this data is fully backed up in the cloud and can be synchronized across all their devices. The entire process is completed within seconds; User B only needs to enter the number and click confirm once. The specific process is as follows... Figure 4 As shown.

[0113] The "Cloud Contacts Service Platform" is not only a business card database but also a server for managing users' personal cloud contacts accounts. Each user has their own private cloud space for storing contact lists, business cards, and other data. Furthermore, this solution ensures clear ownership of personal data. User A's business card data always belongs to A's cloud space; B only receives an authorized copy. A can update information in their cloud space at any time and choose whether to notify previously exchanged contacts. To ensure that users A and B can still exchange business cards using this simplified process even without a cloud contact list, the communication network can utilize a card application to synchronize business card information to the other user's SIM card storage space. The process is similar to... Figure 4 The steps are the same. If a user does not currently have their own cloud address book, the business card exchange can be completed using the card application during the confirmation process after entering the user's mobile phone number. Specific steps are as follows: Figure 5 As shown.

[0114] This invention also offers the following technical advantages: It achieves rapid business card exchange through a cloud communication network based on a communication network. The innovations of this solution include: using the communication network to build a cloud address book containing user call data and personal business cards; and utilizing the network's functionality to trigger business card exchange when a user inputs and stores another user's phone number. Business card data is always stored in the owner's personal cloud space. The essence of the exchange is granting the other party real-time and effective access, rather than simple data copying, which provides a foundation for future information updates. The exchange process strictly adheres to the "double confirmation" principle, especially respecting the business card owner's pre-set exchange rules, preventing any service provider or user from unauthorized information capture. All complex matching, strategy judgment, and exchange logic in this process are completed in the cloud; the mobile terminal is mainly responsible for triggering, confirming, and final presentation, resulting in a clear architecture and a smooth user experience. The cloud address book built on the operator's communication network possesses strong identity authentication and encrypted transmission capabilities from the network layer to the application layer. Its security is equivalent to or even superior to ordinary internet channels, ensuring that data is protected against eavesdropping and tampering during transmission. This invention uses a special business card interaction channel to form a dedicated cloud address book, which can securely implement a fast and smooth electronic business card exchange by entering a mobile phone number and confirming.

[0115] Example 3

[0116] To achieve the above embodiments, such as Figure 6 As shown, this embodiment also provides a device 10 for exchanging business cards in a cloud address book based on a communication network, including:

[0117] The cloud address book construction module 100 is used to build a cloud address book system based on the operator's core signaling network. It establishes a communication connection with the billing system through the RCS protocol, forming a business card data transmission channel independent of the Internet.

[0118] The user information collection and encryption synchronization module 200 is used to collect user personal information through SIM card application or address book APP and generate encrypted personal business card data. The encrypted data and call records in the billing system are synchronized to the user's exclusive cloud space to establish a structured cloud address book.

[0119] The permission verification and process triggering module 300 is used to verify the registration status of the target user's cloud address book and the business card exchange rules through an encrypted query interface when the user enters the target user's mobile phone number. Based on the double confirmation mechanism, it performs permission granting operations in the cloud and triggers the business card exchange process.

[0120] The log recording and transmission module 400 is used to record complete log information of the exchange event, including the exchange time, the initiator device identifier, the receiver device identifier, and data access permission change records, and to achieve traceability of the exchange process through the operator's dedicated channel.

[0121] Furthermore, the user information collection and encryption synchronization module 200 is also used for:

[0122] When collecting users' personal information through SIM card applications, a strong authentication mechanism is adopted, including verification of the device number, verification of SMS verification code, and confirmation of service password.

[0123] The AES-256 algorithm is used to perform end-to-end encryption on encrypted personal business card data and billing system call records, and the TLS 1.3 protocol is used to ensure the security of the transmission channel.

[0124] Furthermore, the permission verification and process triggering module 300 is also used for:

[0125] When the length of the mobile phone number entered by the user meets the requirements When the input is paused, a query request is sent to the cloud address book service platform via an HTTPS encrypted interface;

[0126] Based on the target user's preset business card exchange rules, if "confirmation required" is set, an encrypted push notification will be sent to all of the target user's online devices, awaiting the user's authorization response.

[0127] Furthermore, the log recording and transmission module 400 is also used for:

[0128] When recording complete log information for an exchange event, the information includes the IP address of the initiating device, the IMEI of the receiving device, and the hash value of the exchange operation.

[0129] When transmitting log data through the operator's dedicated channel, timestamp encryption technology is used to ensure that the log records are tamper-proof and traceable.

[0130] This invention discloses a device for exchanging business cards in a cloud address book based on a communication network. By using a cloud address book based on the operator's core signaling network, the device enables the exchange of electronic business cards, effectively ensuring the privacy, security, and compliance of user data during transmission and storage, while also improving the convenience and traceability of business card exchange.

[0131] Example 4

[0132] To implement the methods of the above embodiments, the present invention also provides a computer device, such as... Figure 7 As shown, the computer device 600 includes a memory 601 and a processor 602; wherein, the processor 602 reads the executable program code stored in the memory 601 to run a program corresponding to the executable program code, so as to implement the various steps of the above-described method for exchanging business cards in a cloud address book based on a communication network.

[0133] Example 5

[0134] To implement the above embodiments, this application also proposes a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements a method for exchanging business cards in a cloud address book based on a communication network as described in the foregoing embodiments.

[0135] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0136] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

Claims

1. A method for exchanging business cards in a cloud address book based on a communication network, characterized in that, include: S1. Construct a cloud address book system based on the operator's core signaling network, establish a communication connection with the billing system through the RCS protocol, and form a business card data transmission channel independent of the Internet. The business card data is transmitted in the transmission channel in the form of rich media messages. S2 collects users' personal information through SIM card applications or address book apps and generates encrypted personal business card data. It then synchronizes the encrypted data with call records in the billing system to the user's exclusive cloud space in the cloud address book system, establishing a structured cloud address book. S3: When a user enters the target user's mobile phone number, the registration status of the target user's cloud address book and the business card exchange rules are verified through an encrypted query interface. Based on the dual confirmation mechanism of the initiator's confirmation and the recipient's authorization, the permission granting operation is performed in the cloud and the business card exchange process is triggered. S4 records complete log information of the exchange event, including the exchange time, initiator device identifier, receiver device identifier, and data access permission change records, and achieves traceability of the exchange process through the operator's dedicated channel.

2. The method as described in claim 1, characterized in that, The S2 includes: S21, when collecting users' personal information through SIM card applications, adopts a strong identity authentication mechanism, including mobile phone number verification, SMS verification code verification and service password confirmation; S22, when synchronizing encrypted personal business card data and billing system call records to the cloud space, uses the AES-256 algorithm to encrypt the data end-to-end and uses the TLS1.3 protocol to ensure the security of the transmission channel.

3. The method as described in claim 1, characterized in that, The S3 includes: S31, when the length of the mobile phone number entered by the user meets the requirements... When the input is paused, a query request is sent to the cloud address book service platform via an HTTPS encrypted interface; S32, based on the target user's preset business card exchange rules, if set to "confirmation required", will push an encrypted push notification to all of the target user's online devices and wait for the user's authorization response.

4. The method as described in claim 1, characterized in that, The S4 includes: S41, when recording complete log information of the exchange event, includes the IP address of the initiating device, the IMEI identifier of the receiving device, and the hash value of the exchange operation; When transmitting log data through the operator's dedicated channel, S42 uses timestamp encryption technology to ensure that log records are tamper-proof and traceable.

5. A device for exchanging business cards in a cloud address book based on a communication network, characterized in that, include: The cloud address book construction module is used to build a cloud address book system based on the operator's core signaling network. It establishes a communication connection with the billing system through the RCS protocol to form a business card data transmission channel independent of the Internet. The business card data is transmitted in the form of rich media messages within the transmission channel. The user information collection and encryption synchronization module is used to collect users' personal information through SIM card applications or address book APPs and generate encrypted personal business card data. The encrypted data and call records in the billing system are synchronized to the user's exclusive cloud space in the cloud address book system to establish a structured cloud address book. The permission verification and process triggering module is used to verify the registration status of the target user's cloud address book and the business card exchange rules through an encrypted query interface when the user enters the target user's mobile phone number. Based on the dual confirmation mechanism of the initiator's confirmation and the recipient's authorization, the module performs permission granting operations in the cloud and triggers the business card exchange process. The log recording and transmission module is used to record complete log information of the exchange event, including the exchange time, the initiator device identifier, the receiver device identifier, and data access permission change records, and to achieve traceability of the exchange process through the operator's dedicated channel.

6. The apparatus as claimed in claim 5, characterized in that, The user information collection and encryption synchronization module is also used for: When collecting users' personal information through SIM card applications, a strong authentication mechanism is adopted, including verification of the device number, verification of SMS verification code, and confirmation of service password. The AES-256 algorithm is used to perform end-to-end encryption on encrypted personal business card data and billing system call records, and the TLS 1.3 protocol is used to ensure the security of the transmission channel.

7. The apparatus as claimed in claim 5, characterized in that, The permission verification and process triggering module is also used for: When the length of the mobile phone number entered by the user meets the requirements When the input is paused, a query request is sent to the cloud address book service platform via an HTTPS encrypted interface; Based on the target user's preset business card exchange rules, if "confirmation required" is set, an encrypted push notification will be sent to all of the target user's online devices, awaiting the user's authorization response.

8. The apparatus as claimed in claim 5, characterized in that, The log recording and transmission module is also used for: When recording complete log information for an exchange event, the information includes the IP address of the initiating device, the IMEI of the receiving device, and the hash value of the exchange operation. When transmitting log data through the operator's dedicated channel, timestamp encryption technology is used to ensure that the log records are tamper-proof and traceable.

9. A computer device, characterized in that, Including processor and memory; The processor reads executable program code stored in the memory to run a program corresponding to the executable program code, so as to implement a method for exchanging business cards in a cloud address book based on a communication network as described in any one of claims 1-4.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by the processor, the program implements a method for exchanging business cards in a cloud address book based on a communication network, as described in any one of claims 1-4.

Images