Communication method, electronic device, non-terrestrial network device, chip, and storage medium

Abstract

The present application relates to the technical field of communications, and provides a communication method, an electronic device, a non-terrestrial network (NTN) device, a chip, and a storage medium. When a terminal device camps on an NTN, the method specifically comprises: receiving a paging message, the paging message comprising a first paging identifier of a calling user and a second paging identifier of a called user, and the second paging identifier matching identifier information of the terminal device; and outputting prompt information, the prompt information comprising related information of the calling user corresponding to the first paging identifier and being used for prompting that there is incoming information from the calling user. By means of the technical solution provided in the embodiments of the present application, when a called user is called in an NTN, the called user can learn about, in a paging phase, a calling user from which the current call comes, so as to determine whether to accept the current call by means of a series of operations such as satellite alignment, thereby improving user experience.

Description

Communication methods, electronic devices, non-terrestrial network equipment, chips and storage media

[0001] This application claims priority to Chinese patent application filed on November 20, 2024, with application number 202411671769.6, entitled "Communication Method, Electronic Device, Non-Terrestrial Network Device, Chip and Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method, electronic device, non-terrestrial network device, chip, and storage medium. Background Technology

[0003] For terminal devices residing in non-terrestrial networks (NTNs), signal obstruction may occur in called party scenarios, leading to reduced signal strength. For example, if a terminal device is placed in a backpack or clothing pocket, the received signal strength will be 6-10 dB lower compared to handheld use. Therefore, in called party scenarios, NTN devices (such as satellites) typically first notify the called user of an incoming call via an Alert message on an enhanced paging channel. Subsequently, the called user picks up the device according to the prompts to pair with the satellite, thereby establishing a connection with the NTN device to obtain the caller's information and answer the call.

[0004] However, during the above process, after the called user performs a series of operations such as pairing with a satellite and establishing a connection, they may receive low-value calls, such as advertising or sales calls, resulting in a poor user experience. Summary of the Invention

[0005] This application provides a communication method, electronic device, non-terrestrial network device, chip, and storage medium to solve the problem of poor user experience when a terminal device is called under NTN in the prior art.

[0006] To achieve the above objectives, this application adopts the following technical solution:

[0007] In a first aspect, embodiments of this application provide a communication method applied to a terminal device. When the terminal device is hosted on a non-terrestrial network (NTN), the method specifically includes: receiving a paging message, the paging message including a first paging identifier of the calling user and a second paging identifier of the called user, the second paging identifier matching the identifier information of the terminal device; and outputting a prompt message, the prompt message including relevant information of the calling user corresponding to the first paging identifier, used to indicate that an incoming call has been received from the calling user.

[0008] In the communication method provided in this embodiment, since the paging message includes the calling user's first paging information, when the called user is called under NTN, they can know which calling user the call comes from during the paging phase, and thus decide whether to accept the call through a series of star level operations, thereby improving the user experience. Furthermore, since the terminal device has already received the calling user's information during the paging phase, the NTN device does not need to send the calling user's information to the called user again during subsequent communication, reducing the amount of signaling data during connection and saving NTN air interface resources.

[0009] In some embodiments, the first paging identifier is an identifier obtained by compressing and encoding the first contact identifier (such as a telephone number) of the calling user, and the bit width of the first paging identifier is smaller than that of the first contact identifier. And / or, the second paging identifier is an identifier obtained by compressing the paging identifier of the called user.

[0010] Since the first paging identifier is encoded identification information, the privacy of the calling user can be protected during the paging process. Furthermore, both the first and second paging identifiers are compressed identification information, thus reducing the content of the paging message and consequently reducing the consumption of NTN air interface resources.

[0011] In some embodiments, the sum of the bit widths occupied by the first paging identifier and the second paging identifier is less than the bit width occupied by the uncompressed paging identifier of the called user, for example, less than 48 bits. Compared with existing paging messages, the paging message of this application can not only notify the called user of the relevant information of the calling user, so that the called user can choose whether to control the called device to connect to the satellite and receive the corresponding information, but also reduce the occupation of NTN resources.

[0012] In some embodiments, the calling user is included in a whitelist of called users, which includes the correspondence between the calling user's contact identifier and paging identifier. For example, the whitelist includes the correspondence between the calling user's telephone number and coded information.

[0013] The method provided in this embodiment can filter calling users, which can not only prevent called users from being disturbed by unimportant or low-value incoming call information under NTN, but also reduce the number of paging calls of NTN equipment and save NTN resources.

[0014] In some embodiments, the contact identifier is a telephone number, and the whitelist includes at least one of the following: a public whitelist, which includes the mapping between public telephone numbers and paging identifiers; a private whitelist, which includes the mapping between private telephone numbers set by the called user and paging identifiers; and a dynamic whitelist, which includes the mapping between telephone numbers and paging identifiers that the called user has successfully called under NTN within a preset time period.

[0015] In some embodiments, before receiving a paging message, the method further includes: receiving a public telephone number from a terrestrial network (TN) device, or obtaining a public telephone number from a subscriber identity module (SIM) card; generating and storing a public whitelist based on the public telephone number using a preset compression encoding method; and / or determining a private telephone number based on user actions; generating and storing a private whitelist based on the private telephone number using a preset compression encoding method; and / or determining telephone numbers that the called user has successfully called under the NTN within a preset time period; generating and storing a dynamic whitelist based on the telephone numbers that have successfully called using a preset compression encoding method.

[0016] This embodiment categorizes caller ID numbers into various types, such as public phone numbers, private phone numbers, and dynamic phone numbers, and sets corresponding whitelists for different types of caller ID numbers. This method can not only filter caller ID numbers in multiple dimensions, but also ensure that users have diverse communication needs in the called scenario, resulting in a better user experience.

[0017] In some embodiments, receiving a paging message includes: receiving the paging message on an enhanced paging channel. This method ensures that paging messages are delivered more promptly and effectively, improving communication efficiency, communication quality, and user experience.

[0018] Secondly, embodiments of this application provide a communication method applied to an NTN device or a cloud server, specifically including: sending a paging message, the paging message including a first paging identifier of the calling user and a second paging identifier of the called user, wherein the terminal device used by the called user resides in the NTN.

[0019] In this embodiment, the network-side device (such as an NTN device or a cloud server) can not only notify the called user of the calling user's information and increase the carrying of useful information in the paging message to achieve called user enhancement, but also reduce the disturbance of low-value information to users, save NTN resources, and improve the communication experience of the called user under NTN.

[0020] In some embodiments, the first paging identifier is an identifier obtained by compressing and encoding the first contact identifier of the calling user, and the bit width of the first paging identifier is smaller than that of the contact identifier; and / or, the second paging identifier is an identifier obtained by compressing the paging identifier of the called user.

[0021] In some embodiments, the sum of the bit widths occupied by the first paging identifier and the second paging identifier is less than the bit width occupied by the uncompressed paging identifier of the called user, for example, less than 48 bits.

[0022] In some embodiments, the method further includes receiving a paging message before sending the paging message.

[0023] In some embodiments, if the calling user is connected to a TN (Transportation Network), the method further includes, before sending the paging message, receiving a call request from the TN device and generating a paging message based on the call request. The call request includes a first call identifier of the calling user and a second call identifier of the called user. Generating the paging message based on the call request includes: determining the first paging identifier of the calling user based on the first call identifier; determining the second paging identifier of the called user based on the second call identifier; and generating the paging message based on the first and second paging identifiers.

[0024] In some embodiments, determining the first paging identifier of the calling user based on the first call identifier includes: determining the first contact identifier of the calling user based on the first call identifier, wherein there is a preset correspondence between the call identifier and the contact identifier; and determining the first paging identifier based on the correspondence between the first contact identifier and the first paging identifier in a whitelist. Taking the first paging identifier as the calling user's IMSI and the whitelist including the correspondence between phone numbers and paging identifiers as an example, the process of determining the first paging identifier may include: determining the calling phone number based on the calling device's IMSI, and determining the first paging identifier in the whitelist based on the calling phone number.

[0025] In some embodiments, when the method is applied to an NTN device, determining the first paging identifier based on the correspondence between the first contact identifier and the first paging identifier in the whitelist includes: sending query information to a cloud server, the query information including a first contact identifier (e.g., a phone number) corresponding to the first call identifier (e.g., IMSI), used to query whether the calling user belongs to the private whitelist; receiving a first query result, the first query result indicating that the calling user belongs to the private whitelist, and including the first paging identifier corresponding to the first contact identifier; or, receiving a second query result, the second query result indicating that the calling user does not belong to the private whitelist. In this embodiment, the called user's private whitelist is stored in the cloud server, which can better protect user privacy.

[0026] In some embodiments, the whitelist includes at least one of the following: a public whitelist, which includes the correspondence between public telephone numbers and paging identifiers; a private whitelist, which includes the correspondence between private telephone numbers set by the called user and paging identifiers; and a dynamic whitelist, which includes the correspondence between telephone numbers and paging identifiers that the called user has successfully called under NTN within a preset time period.

[0027] In some embodiments, before sending a paging message, the method further includes: receiving a public telephone number from a TN device; generating and storing a public whitelist based on the public telephone number using a preset compression encoding method; and / or obtaining a private telephone number determined by the user; generating and storing a private whitelist based on the private telephone number using a preset compression encoding method; and / or determining telephone numbers actively called by the called device under the NTN within a preset time period; generating and storing a dynamic whitelist based on the user identifier of the actively called user using a preset compression encoding method.

[0028] In some embodiments, after a preset time has elapsed since the terminal device used by the called user disconnected from the NTN device, the whitelist of called users stored locally is deleted to free up NTN memory resources.

[0029] In some embodiments, when the method is applied to an NTN device, sending a paging message includes: sending a paging message on an enhanced paging channel.

[0030] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method shown in the first aspect above.

[0031] Fourthly, embodiments of this application provide a cloud server, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the method shown in the second aspect above.

[0032] Fifthly, embodiments of this application provide a non-terrestrial network (NTN) device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the method shown in the second aspect above.

[0033] In a sixth aspect, embodiments of this application provide a chip including a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, it implements the methods shown in the first or second aspect above.

[0034] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods shown in the first or second aspect above.

[0035] Eighthly, embodiments of this application provide a computer program product, which includes a computer program that, when executed by an electronic device, causes the electronic device to implement the methods shown in the first or second aspect above.

[0036] It is understood that the beneficial effects of the third to eighth aspects mentioned above can be found in the relevant descriptions in the first or second aspects mentioned above, and will not be repeated here. Attached Figure Description

[0037] Figure 1 is a schematic diagram of the structure of a communication system provided in an embodiment of this application;

[0038] Figure 2 is a schematic flowchart of a communication method provided in an embodiment of this application;

[0039] Figure 3A is a schematic diagram of the public whitelist setting process provided in an embodiment of this application;

[0040] Figure 3B is a schematic diagram of the public whitelist setting process provided in another embodiment of this application;

[0041] Figure 4 is a schematic diagram of the private whitelist setting process provided in an embodiment of this application;

[0042] Figure 5 is a schematic diagram of the dynamic whitelist setting process provided in an embodiment of this application;

[0043] Figure 6 is a flowchart of a communication method provided in another embodiment of this application;

[0044] Figure 7 is a flowchart of a communication method provided in yet another embodiment of this application;

[0045] Figure 8 is a flowchart of deleting a whitelist provided in an embodiment of this application;

[0046] Figure 9 is a schematic diagram of the dynamic whitelist setting process provided in another embodiment of this application;

[0047] Figure 10 is a flowchart of a communication method provided in another embodiment of this application;

[0048] Figure 11 is a schematic diagram of a communication device provided in an embodiment of this application;

[0049] Figure 12 is a schematic diagram of a communication device provided in an embodiment of this application;

[0050] Figure 13 is a schematic diagram of the chip structure provided in an embodiment of this application. Detailed Implementation

[0051] It should be understood that in the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in this document is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone.

[0052] In this embodiment, 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 indicated technical features. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0053] To facilitate understanding of the technical solution of this application, the key terms involved in this application are introduced below. It should be noted that the following introduction is intended for explanation and description, not for limitation.

[0054] (1) Terrestrial networks and non-terrestrial networks

[0055] A terrestrial network (TN) refers to a communication network established between radio communication stations on Earth. In the embodiments of this application, the terrestrial network includes not only mobile communication networks (i.e., cellular networks) but also wireless communication networks. The communication system used by the mobile communication network can be a long-term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, a universal mobile telecommunication system (UMTS), a worldwide interoperability for microwave access (WiMAX) system, a 5th generation (5G) mobile communication system, or a new radio (NR) system, etc. Furthermore, the wireless communication network can be a wireless local area network (WLAN), such as a wireless fidelity (Wi-Fi) network.

[0056] Non-terrestrial networks (NTNs) include, but are not limited to, satellite networks. Satellite networks use satellites as communication nodes to transmit data, enabling global coverage and making them particularly suitable for remote areas, maritime locations, or polar regions where terrestrial networks are difficult to reach. By integrating with terrestrial networks, NTNs can improve signal coverage regardless of terrain, connecting air, space, land, and sea to form an integrated ubiquitous access network, enabling on-demand access in all scenarios.

[0057] (2) Calling user and called user

[0058] A calling (mobile originated, MO) user is a user who actively initiates a call. The calling user proactively sends a call request through their terminal device (also called the calling device), hoping to establish a connection with the other party. Additionally, the calling user can also proactively send text messages, MMS, emails, and instant messaging through their calling device.

[0059] A called (mobile terminated, MT) user is a user who passively receives a call. After receiving a call through their terminal device (also called the called device), the called user displays the caller ID and answers the call and participates in the conversation based on their actions. Additionally, the called user can also receive SMS, MMS, email, and instant messaging services through their terminal device.

[0060] It should be noted that during communication, the role of the same user changes depending on the actions they perform. For example, a user may be the calling user when calling other users, and the called user when being called by other users. Similarly, the role of the same terminal device changes depending on the actions it performs. For example, a terminal device may be the calling device when calling other users, and the called device when being called by other users.

[0061] (3) User ID

[0062] In this embodiment, the user identifier is used to uniquely identify the user's identity information. At different stages of communication, the user may have different identifiers, including contact identifiers, call identifiers, and paging identifiers, etc. See below for details.

[0063] Contact identifiers refer to the identification information actually used by users during communication, such as phone numbers and account IDs.

[0064] Call identification refers to the identification information used by the calling user when calling the called user, or the identification information in the call request sent by the calling device to the network device, such as telephone number, International Mobile Subscriber Identity (IMSI), and account ID.

[0065] Paging identifier refers to the identification information used by network-side devices when paging a called user, or the identification information carried in the paging message sent by the network-side devices.

[0066] It should be noted that the contact identifier, call identifier, and paging identifier of the same user can be completely different, partially the same, or completely different. This application embodiment does not impose any restrictions on this.

[0067] (4) Paging Channel and Enhanced Paging Channel

[0068] A paging channel is a downlink transmission channel used to transmit paging-related data. For example, paging-related data includes the called user's identification information.

[0069] The enhanced paging channel (EPC) is an upgrade to the traditional paging mechanism. The EPC can be enhanced by increasing transmit power, segmented paging, semi-static scheduling, increasing retransmission frequency, adding new modulation and coding schemes, and diversity transmission, thereby increasing the likelihood of the called device being successfully reached.

[0070] When a TN device (such as a base station) or an NTN device (such as a satellite) receives a call request from the calling device, it will page the called user through a paging channel or an enhanced paging channel.

[0071] (5) IMSI, TMSI and S-TMSI

[0072] The International Mobile Subscriber Identity (IMSI) is a globally unique identifier for a user. The IMSI includes the Mobile Country Code (MCC), Mobile Network Code (MNC), and Mobile Subscriber Identification Number (MSIN). The MCC uniquely identifies the country to which the public land mobile network belongs; for example, China's MCC is 460. The MNC identifies the network within that country; an operator can use one or more MNCs to identify its network. For example, China Mobile's MNCs include 00, 02, 04, and 07. The MSIN identifies a mobile subscriber within a public land mobile network (PLMN).

[0073] A Temporary Mobile Subscriber Identity (TMSI) is a temporary subscriber identifier assigned in the Visitor Location Register (VLR) to enhance system security. The TMSI uniquely corresponds to the IMSI within a specific VLR area. The TMSI is the number used by the base station / satellite when calling the subscriber, replacing the IMSI and preventing it from being intercepted during transmission. The total length of the TMSI does not exceed 4 bytes; a 32-bit TMSI is considered invalid if all bits are 1.

[0074] 5G-S-TMSI (S-TMSI for short) is part of the 5G Globally Unique Temporary Identifier (5G-GUTI) and is used to enable more efficient radio signaling procedures. For example, for paging functions, network-side equipment uses S-TMSI to page mobile devices.

[0075] As shown in Table 1, the S-TMSI includes the AMF Set ID, AMF Pointer, and 5G-TMSI. The AMF Set ID uniquely identifies the AMF set within the AMF region and typically occupies 10 bits. The AMF Pointer identifies one or more AMFs within the AMF set and typically occupies 6 bits. The 5G-TMSI typically occupies 32 bits.

[0076] Table 1 S-TMSI Structure

[0077] After introducing the key terms involved in the embodiments of this application, the process of terminal devices communicating based on terrestrial networks and non-terrestrial networks will be described in detail below.

[0078] Figure 1 is a schematic diagram of the structure of a communication system provided in an embodiment of this application. The communication system includes a first terminal device 100, a second terminal device 200, a TN device 300, a cloud server 400, and an NTN device 500.

[0079] Both the first terminal device 100 and the second terminal device 200 support at least one of terrestrial communication and non-terrestrial communication. The first terminal device 100 and the second terminal device 200 can be mobile phones, tablets, desktop computers, laptops, handheld computers, ultra-mobile personal computers (UMPCs), netbooks, cellular phones, personal digital assistants (PDAs), augmented reality (AR) devices, virtual reality (VR) devices, artificial intelligence (AI) devices, wearable devices, in-vehicle devices, and / or smart city devices, etc. This application does not impose special limitations on the specific type of terminal device.

[0080] TN equipment 300 includes access network equipment 310 and cellular core network equipment 320. Details are shown below.

[0081] Access network device 310 is mainly used to implement functions such as wireless physical layer functions, resource scheduling and wireless resource management, wireless access control, and mobility management. In this embodiment, access network device 310 can be an access network (AN) or a radio access network (RAN) device. In this embodiment, the access network device 310 includes, but is not limited to: evolved node B (eNB), radio network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home network device (e.g., home evolved Node B, or home Node B, HNB), baseband unit (BBU), access point (AP), wireless relay node, wireless backhaul node, transmission and reception point (TRP), transmission point (TP) in a wireless fidelity (WIFI) system, etc.; it can also be a device used in 5G, 6G and other systems, such as gNB in ​​NR system, or transmission point (TRP or TP), one or a group (including multiple antenna panels) of antenna panels of network device in 5G system, or it can also be a network node constituting gNB or transmission point, such as baseband unit (BBU), or distributed unit (distributed unit). RSU (Remote Unit) in the context of vehicle-to-everything (V2X) or intelligent driving scenarios.

[0082] The cellular core network equipment 320 includes functional units such as access and mobility management (AMF), session management (SMF), policy control (PCF), and operation, administration, and maintenance (OAM). These functional units can work independently or be combined to implement certain control functions. For example, AMF, SMF, and PCF can work together to complete access control and mobility management functions such as access authentication, security encryption, and location registration for terminal devices, as well as session management functions such as establishing, releasing, and modifying user plane transmission paths, and analyzing data related to network slices and terminal devices. In this embodiment, the core network equipment only needs to implement the above-mentioned network element functions; this embodiment does not limit the specific network element deployment method in the core network equipment.

[0083] The cloud server 400 can provide communication services to terminal devices, such as audio and video calls, SMS and email sending. Terminal devices can connect to the cloud server 400 via cellular data or wireless local area network (WLAN) (e.g., wireless fidelity, Wi-Fi).

[0084] NTN equipment 500 includes satellite 510, gateway station 520, and satellite core network equipment 530. Satellite 510 can be a low Earth orbit (LEO), medium Earth orbit (MEO), or geostationary orbit (GEO) satellite, etc., and this embodiment does not impose specific limitations. Gateway station 520 is a relay station connecting satellite 510 and satellite core network equipment 530, responsible for the distribution and collection of satellite communication service data, and also has functions such as network management and operation control, capable of resource scheduling, system equipment management, and user service management. Satellite core network equipment 530 is mainly responsible for call connection, billing, mobility management, and data distribution for satellite terminal equipment (such as the first terminal equipment 100).

[0085] Based on the above communication system, when the second terminal device 200 is hosted on an NTN, there are multiple communication pathways between the first terminal device 100 and the second terminal device 200. For example, when the first terminal device 100 is hosted on a TN, it can communicate with the second terminal device 200 through the TN device 300 and the NTN device 500. Alternatively, when the first terminal device 100 is hosted on an NTN, it can communicate with the second terminal device 200 through the NTN device 500. Or, when the first terminal device 100 is connected to the cloud server 400, it can communicate with the second terminal device 200 through the cloud server 400 and the NTN device 500.

[0086] When the second terminal device 200 is hosted on NTN, voice calls are an important communication scenario. Taking NTN as an example, the specific call process is as follows.

[0087] When the second terminal device 200 is the calling device, the user first needs to pick up the calling device to search for satellites (i.e., satellite search) and align it with satellites (i.e., satellite alignment). By searching for satellites, the calling device can search for and connect to satellites in space. By aligning with satellites, the calling device can adjust the direction and angle of its antenna to precisely point it at the satellite it is using, ensuring optimal signal quality and transmission efficiency. Only then can the user use the terminal device to call other electronic devices.

[0088] When the second terminal device 200 is the called device, signal obstruction may occur, resulting in reduced signal strength. For example, if the called device is placed in a backpack or pocket, the signal strength will be reduced by approximately 6-10 dB compared to handheld use. Therefore, according to the Geostationary Earth Orbit Mobile Radio Interface (GMR) protocol, in called scenarios, the NTN device (such as a satellite) typically first notifies the called device of an incoming call via an Alert message on the enhanced paging channel. This Alert message includes the called user's identification information (e.g., UE-ID) but not the calling user's identification information (e.g., Paging ID). Subsequently, after receiving an Alert message matching its own identification information, the called device prompts the called user to pick up the terminal device and perform satellite pairing. After pairing, the called device establishes a radio resource control (RRC) connection with the satellite and obtains the calling user's identification information. Finally, the called device displays the incoming call interface, which includes the calling number.

[0089] However, in the above process, since the Alert message does not include the caller's identification information, in order not to miss any valuable calls, the called user needs to perform a star pairing after receiving each Alert message to obtain the caller's number and answer the call. However, in daily life, low-value callers frequently call the called user, such as telemarketing numbers calling the terminal device. In the above process, the user cannot perceive the value of the caller's number before star pairing, which leads to the user frequently performing useless star pairing operations, consuming NTN resources and resulting in a poor user experience.

[0090] Therefore, this application provides a communication method. Based on this method, when paging a called user, the NTN device can notify the called user of the relevant information of the calling user, so that the called user can selectively receive information according to their needs, avoid the called user being frequently disturbed by low-value information under NTN, and improve the user experience.

[0091] Next, the communication method provided in the embodiments of this application will be described in detail with reference to the accompanying drawings.

[0092] Figure 2 is a schematic flowchart of a communication method provided in an embodiment of this application. The method relates to the process by which an NTN device pages a called user when the called device is camped on an NTN, specifically including the following steps S201 to S202.

[0093] S201, the NTN device sends a paging message to the called device, which includes the first paging identifier of the calling user and the second paging identifier of the called user.

[0094] In this embodiment, the paging message is used by the NTN device to page the called user. The NTN device can send the paging message to the called device using either a normal paging channel or an enhanced paging channel; this embodiment does not impose any limitations on this. Furthermore, compared to existing paging messages that only include the called user's paging identifier, the paging message in this embodiment includes both the called user's second paging identifier and the calling user's first paging identifier, so that the called user can understand the calling user's relevant information after receiving the paging message.

[0095] The first paging identifier, also known as the Pager ID, is an identifier obtained by compressing and encoding the caller's first contact identifier (such as a phone number). The bit width of this first paging identifier is smaller than that of the first contact identifier. Taking the phone number "135...1234" as an example, the first paging identifier obtained after compression and encoding can be the binary number "0001". It can be seen that the number of bits occupied by this first paging identifier is much smaller than that of the phone number.

[0096] It should be noted that paging messages are typically generated by network-side devices (such as NTN devices or cloud servers). In some implementations, the network-side device pre-stores a whitelist of called users, which includes the mapping between contact identifiers and paging identifiers that are allowed to be paged by the called user. After receiving a call request from the calling user, the network-side device can determine the calling user's first paging identifier based on the mapping in the whitelist.

[0097] Since users typically use and store their contact identifiers on their terminal devices, the called user, upon receiving a paging message, can parse the first paging identifier to obtain the first contact identifier (such as a phone number), thereby identifying the calling user. Furthermore, the first paging identifier provided in this embodiment is obtained through compressed encoding, which not only protects the calling user's privacy but also reduces the paging message's impact on NTN resources.

[0098] Alternatively, the first paging identifier can also be the identifier obtained by encrypting the first contact identifier using a preset encryption algorithm. Or, the first paging identifier can also be the identifier obtained by compressing or encrypting other unique identifier information of the calling user. This application embodiment does not limit the content of the first paging identifier. The network-side device (such as an NTN device or cloud server) and the called user can agree on a unique encryption / decryption rule. The network-side device encrypts the calling user's first contact identifier according to this encryption rule to obtain the first paging identifier. The called user decrypts the first paging identifier according to the corresponding decryption rule to obtain the first contact identifier, thereby identifying the calling user.

[0099] The second paging identifier is the identifier obtained by compressing the paging identifier of the called user into smaller bits. The second paging identifier can reduce the occupation of NTN air interface resources.

[0100] Typically, the paging identifier of the called user in the paging message is the unique identifier assigned to the terminal device by the AMF in the 5G system after the called user registers on the 5G network, based on the network the terminal device is connected to and the terminal device's IMSI. This identifier is the S-TMSI, as shown in Table 1. Because the number of AMF Sets (AMF sets) and AMF Pointers (one or more AMFs in an AMF set) in the 5G network is large, and there are many stationary terminal devices, the bit width occupied by the AMF Set ID, AMF Pointer, and 5G-TMSI in existing technologies is relatively large. Typically, S-TMSI = AMF Set ID (10 bits) + AMF Pointer (6 bits) + 5G-TMSI (32 bits).

[0101] Under NTN, the number of terminal devices residing in the AMF Set, AMF, and NTN is relatively small. Therefore, when paging terminal devices residing in the NTN, NTN devices can reduce the bit width occupied by identifiers such as AMF Set ID, AMF Pointer, and 5G-TMSI, thereby compressing the called party identifier. For example, the AMF Set ID can be compressed from 10 bits to 6-8 bits, the AMF Pointer from 5 bits to 4-5 bits, and the 5G-TMSI from 32 bits to 20-28 bits, thus compressing the overall S-TMSI from 48 bits to 30-41 bits, reducing the occupation of NTN resources during paging. The bit-width compressed S-TMSI can use existing NTN communication protocols and architectures.

[0102] In some embodiments, the total bit width occupied by the first paging identifier and the second paging identifier in the paging message can be less than 48 bits, that is, less than the bit width occupied by the paging identifier in existing paging messages, such as 48 bits. Based on this, compared with existing paging messages, the paging message of this application can not only notify the called user of the relevant information of the calling user, so that the called user can choose whether to control the called device to connect to the satellite and receive the corresponding information, but also reduce the occupation of NTN resources.

[0103] In other embodiments, to prevent users from being disturbed by low-value information under NTN, the NTN device can filter the calling user through the called user's whitelist when paging the called user. In other words, if the calling user's first contact identifier belongs to the called device's whitelist, then the network-side device will page the called user. If the calling user's first contact identifier does not belong to the called device's whitelist, then the network-side device will not page the called device.

[0104] S202, the called device outputs a prompt message, which includes relevant information of the calling user corresponding to the first paging identifier, to indicate that there is an incoming call from the calling user.

[0105] After receiving a paging message, the called device compares the second paging identifier carried in the paging message with its own paging identifier. If they match, the called device determines that it is the recipient of this paging. Subsequently, the called device notifies the user of an incoming call through a prompt message and displays relevant information about the caller. For example, the called device can output the prompt message through a communication prompt box, a prompt tone, etc., and this application embodiment does not impose any limitations on this. Furthermore, the relevant information about the caller can be the caller's first contact identifier, such as the phone number "135…1234"; or it can be the username corresponding to the first contact identifier in the called device's address book, such as the username "Zhang San" corresponding to the phone number "135…1234".

[0106] The communication method provided in this application not only allows the NTN device to notify the called user of the calling user's information, increasing the carrying capacity of useful information in the paging message and achieving called user enhancement, but also reduces the disturbance of low-value information to users, saves NTN resources, and improves the communication experience of the called user under NTN. Furthermore, since the NTN device has already sent the calling user's information to the called user during the paging phase, it does not need to send the calling user's information to the called user again via signaling (such as IMS signaling) during subsequent communication, thus reducing the amount of signaling data during call connection and saving NTN air interface resources.

[0107] During the process of a calling user calling a called user, the terminal device used by the calling user (i.e., the calling device) may be hosted on an operator's network (such as NT or NTN) or connected to a cloud server via a wireless network. The communication method provided in this application embodiment will be described in detail below, taking into account different network connection scenarios of the calling device.

[0108] (a) The calling user calls the called user based on the operator's network.

[0109] The embodiments of this application mainly involve three aspects, including: (1-1) setting a whitelist, (1-2) the NTN device paging the called user based on the whitelist, and (1-3) deleting the whitelist. The details are as follows.

[0110] (1-1) Setting up a whitelist

[0111] In this embodiment, each user needs to set a whitelist after registering with the NTN. This whitelist includes contact identifiers (such as phone numbers) of callers allowed to call the user, and each contact identifier uniquely corresponds to a paging identifier (such as coded information). The bit width of the paging identifier is smaller than that of the contact identifier. Registering with the NTN refers to the user's tracking area update (TAU) identifier being registered with the NTN.

[0112] In this embodiment, the whitelist includes a public whitelist (PubWhiteList), a private whitelist (PerWhiteList), and a dynamic whitelist (DynamicWhiteList). The following explanation details the setup process for each whitelist, using telephone numbers as the contact identifier and coded information as the paging identifier.

[0113] (1-1-a) Setting up a public whitelist

[0114] In this embodiment, the public whitelist includes the correspondence between public phone numbers and coded information. For example, public phone numbers include those allowed to be called in emergencies, such as 110 and 120. Taking the coded information as 4 bits, the public whitelist can be seen in Table 1, where public phone number 1 corresponds to coded information "0000", public phone number 2 corresponds to coded information "0001", public phone number 3 corresponds to coded information "0010", and public phone number 4 corresponds to coded information "0011".

[0115] Table 1 Public Whitelist

[0116] For terminal devices:

[0117] In some embodiments, public phone numbers can be pre-installed in the SIM card in sequence. After registering with the NTN, the terminal device can retrieve the pre-stored public phone numbers from the SIM card and encode them using a preset encoding rule to obtain a public whitelist. For example, Adaptive Huffman coding can be used to encode "public phone number 1 to public phone number 4" sequentially to obtain the encoded information "0000 to 0011", thereby obtaining the public whitelist.

[0118] In other embodiments, as shown in Figure 3A, after successful TN registration, the TN device (such as a base station) sends the operator-configured public whitelist to the terminal device, which then receives and stores the public whitelist. Additionally, the TN device can instruct the terminal device to update the public whitelist.

[0119] For NTN devices:

[0120] In some embodiments, referring to Figure 3B, after the terminal device successfully registers with the NTN, the NTN device sends a whitelist retrieval request to the TN device. Based on the whitelist retrieval request, the TN device sends the operator-configured public whitelist to the NTN device. The NTN device receives and stores the terminal device's public whitelist.

[0121] (1-1-b) Setting up a private whitelist

[0122] In this embodiment, the private whitelist includes the correspondence between user-set private phone numbers and coded information. These private phone numbers can be numbers the user frequently contacts, important phone numbers, or phone numbers of family members, etc. Taking the coded information as 3 bits as an example, the private whitelist can be seen in Table 2, where private phone number 1 corresponds to coded information "000", private phone number 2 corresponds to coded information "001", private phone number 3 corresponds to coded information "010", and private phone number 4 corresponds to coded information "011".

[0123] Table 2 Private Whitelist

[0124] Referring to Figure 4, the terminal device determines several private phone numbers based on the user's settings and encodes them using preset rules (such as adaptive Huffman coding) to generate a private whitelist. Additionally, after successful NTN registration, the terminal device sends the user-determined private phone numbers to the NTN device. The NTN device encodes these private phone numbers using the same encoding rules (such as adaptive Huffman coding) as the terminal device, thereby generating and storing the user's private whitelist.

[0125] In some embodiments, to protect user privacy, the terminal device does not send the private phone number to the NTN device, but instead sends the private phone number to the cloud server under the user's personal account. The cloud server encodes these private phone numbers using the same encoding rules as the terminal device (such as adaptive Huffman coding), thereby generating and storing the user's private whitelist.

[0126] It is understandable that there is a one-to-one correspondence between users and their private whitelists, and for the same user, the private whitelist is the same on both the terminal device and the NTN device / cloud server side. The NTN device and cloud server can also update the private whitelist based on instructions from the terminal device.

[0127] (1-1-c) Setting a dynamic whitelist

[0128] In this embodiment, the dynamic whitelist includes the correspondence between phone numbers (hereinafter referred to as historical call numbers) and their encoding information that the terminal device has successfully completed communication under NTN within a preset time period. For example, a phone number that has successfully completed communication can be a phone number that has made an initiating call, or a phone number that has successfully sent SMS messages, emails, instant messages, etc. The preset time period can be one day, one week, etc., and this embodiment does not impose any limitations on this.

[0129] Taking the 6-bit encoding information as an example, the dynamic whitelist can be seen in Table 3. The encoding information corresponding to historical call number 1 is "000000", the encoding information corresponding to historical call number 2 is "000001", the encoding information corresponding to historical call number 3 is "000010", and the encoding information corresponding to historical call number 4 is "000011".

[0130] Table 3 Dynamic Whitelist

[0131] In some embodiments, after successfully calling a target number, the terminal device compresses and encodes the target number locally to generate encoded information and establishes a correspondence between the target number and the encoded information. On one hand, the terminal device stores this correspondence in a local dynamic whitelist; on the other hand, the terminal device sends this correspondence to the NTN device, which stores it in its own dynamic whitelist. In the method provided in this embodiment, there is no need for cumbersome and complex signaling interactions between the terminal device and the NTN device, and the update process of the dynamic whitelist is relatively simple.

[0132] In some other embodiments, as shown in Figure 5, after the terminal device successfully registers with the NTN, the NTN device and the terminal device generate, update and store a dynamic whitelist through the following steps S500 to S511.

[0133] In S500, the NTN device sends a first synchronization message to the terminal device. This first synchronization message is used to synchronize the encoding status of the dynamic whitelist.

[0134] After the terminal device successfully registers with NTN, the NTN device can send the first synchronization message to the terminal device.

[0135] In some embodiments, both the NTN device and the terminal device employ adaptive Huffman coding to encode historical call numbers to generate a dynamic whitelist. Based on this, during the encoding process, since the encoding object is the user's historical call numbers under the NTN, the number of these historical call numbers gradually increases as the user uses the terminal device. Correspondingly, the number of encoded phone numbers in the dynamic whitelist also gradually increases. To synchronize the encoding status between the NTN device and the terminal device, the NTN device also needs to configure an encoding ID for the latest encoded phone number and encoding information based on the number of encoded phone numbers in the dynamic whitelist. For example, as shown in Table 3, after the terminal device encodes historical call number 3 and generates encoding information 000010, the number of encoded phone numbers is 3. Therefore, encoding ID = 3 is configured for historical call number 3 and encoding information 000010.

[0136] Based on this, the first synchronization message is used to synchronize the largest coded ID in the dynamic whitelist of the NTN device, which is M. That is, it informs the terminal device that the total number of historical call numbers currently coded on the NTN side is M. For example, in S501, if the largest coded ID on the NTN device side is 3, then the NTN device will notify the terminal device of coded ID = 3 through the first synchronization message.

[0137] Through the first synchronization message, the NTN device and the terminal device can maintain the consistency of the current dynamic whitelist encoding status, so that when the dynamic whitelist is updated in the future, the dynamic whitelists on both sides can still be kept consistent.

[0138] S501, the terminal device calls the target number through the NTN device.

[0139] S502, the terminal device sends a first indication message to the NTN device, the first indication message being used to indicate that the target number is a dynamic number.

[0140] For example, the first indication information may be a call request sent by the terminal device when calling the target number, or other communication messages between the terminal device and the NTN device. This embodiment does not limit this.

[0141] Optionally, the terminal device can first determine the type of the target number. If the target number is a dynamic number, the terminal device sends a first indication message to the NTN device during or after calling the target number. This first indication message indicates that the target number is a dynamic number or instructs the NTN device to add the number to the dynamic whitelist. If the target number is not a dynamic number, the first indication message is not sent. Here, a dynamic number can be interpreted as a phone number that needs to be encoded and added to the dynamic whitelist.

[0142] S503, the NTN device sends a second indication message to the terminal device, which indicates that the target number has been successfully called.

[0143] It should be noted that "the target number has been successfully called" means that the terminal device corresponding to the target number has successfully displayed the call notification interface. This embodiment does not restrict whether the call was successfully answered. In this case, if the called user does not answer the call in time, the called user's phone number can also be added to the dynamic whitelist so that the called user can call back to call that user.

[0144] S504, the terminal device sends a response message to the NTN device, which indicates that the terminal device has received the second indication information.

[0145] S505, NTN devices determine whether the target number is a dynamic number.

[0146] S506, if the target number is a dynamic number, the NTN device will compress and encode the target number to obtain encoded information.

[0147] In some embodiments, the NTN device uses adaptive Huffman coding to compress and encode the target number according to the encoding ID = M+1 to obtain the corresponding encoding information.

[0148] S507, the NTN device sends a second synchronization message to the terminal device, which is used to resynchronize the encoding status of the dynamic whitelist.

[0149] In some embodiments, the second synchronization message is used to synchronize the largest encoded ID in the dynamic whitelist of the NTN device, which is M+1. For example, if the encoded ID in the first synchronization message in S500 is 3, then after the processes of S502 to S506, the encoded ID in the second synchronization message is 4.

[0150] S508, NTN device startup timer.

[0151] For example, the duration of the timer can be 1 minute, 3 minutes, or 5 minutes, etc., and this application embodiment does not limit this.

[0152] S509: After receiving the second synchronization message, the terminal device compresses and encodes the target number to obtain encoded information, and stores the correspondence between the target number and the encoded information in the dynamic whitelist.

[0153] In some embodiments, the terminal device uses the same encoding method as the NTN device, compressing the target number according to the encoding ID = M+1. Therefore, the correspondence between the encoding ID, the target number, and the encoding information is the same on both the NTN device and the terminal device side. Consequently, the dynamic whitelists of the NTN device and the terminal device are also the same.

[0154] Depending on the encoding of the target number and the communication status of the terminal device, the specific implementation of S510 is S510a, S510b, or S510c.

[0155] S510a, the terminal device sends a third indication message to the NTN device, which is used to indicate that the target number encoding was successful.

[0156] In other words, after successfully encoding the target information, the terminal device notifies the NTN device. Additionally, the terminal device shuts down its timer upon receiving the third instruction.

[0157] S510b, the terminal device sends a fourth indication message to the NTN device, which is used to indicate that the target number encoding has failed.

[0158] In other words, the terminal device notifies the NTN device after failing to encode the target information. Additionally, the terminal device shuts down the timer upon receiving the fourth instruction.

[0159] S510c, NTN device detected a timer expiration.

[0160] In other words, the NTN device did not receive the third instruction message or the fourth instruction message from the terminal device within the preset time.

[0161] Depending on the specific implementation of S510, the specific implementation of S511 will also differ. S511 can be either S511a or S511b. Specifically, after S510a, the NTN device executes S511a; while after S510b or S510c, the NTN device executes S511b.

[0162] S511a, NTN devices store the correspondence between target numbers and their encoding information in a dynamic whitelist.

[0163] S511b, the NTN device deletes the encoding information of the target number.

[0164] Through steps S501 to S511, each time a user actively calls a dynamic number under the NTN, both the terminal device and the NTN can add the dynamic number to the user's dynamic whitelist. This method not only ensures that the dynamic whitelists of the terminal device and the NTN are completely identical, but also avoids the correspondence between phone numbers and encoding information transmitted over the air interface, thus providing better information security.

[0165] It should be noted that for public whitelists, private whitelists, and dynamic whitelists, conditional constraints can be applied to the encoding information of different whitelists to ensure that the encoding information of each phone number in each whitelist is different, thus maintaining a one-to-one correspondence between phone numbers and encoding information. For example, the encoding information in the public whitelist can be configured to be 4 bits, the encoding information in the private whitelist to be configured to be 3 bits, and the encoding information in the dynamic whitelist to be configured to be 6 bits. Alternatively, different ranges can be configured for the values ​​(i.e., decimal values) of the encoding information in different whitelists, such as controlling the value of the encoding information in the public whitelist to be 0-15, controlling the value of the encoding information in the private whitelist to be 16-23, and controlling the value of the encoding information in the dynamic whitelist to be 14-63, etc.

[0166] In summary, the embodiments of this application categorize caller ID numbers into various types such as public phone numbers, private phone numbers, and dynamic phone numbers, and set corresponding whitelists for different types of caller ID numbers. This enables multi-dimensional filtering of caller ID numbers and ensures that users have diverse communication needs in the called scenario, resulting in a better user experience.

[0167] (1-2) NTN devices page called users based on a whitelist.

[0168] Figure 6 is a flowchart of a communication method provided in another embodiment of this application. The method relates to a scenario where a calling device calls a called device under a TN, and specifically includes the following steps S601 to S605.

[0169] S601, the calling device sends a call request to the TN device, the call request including the first call identifier of the calling user and the second call identifier of the called user.

[0170] In this embodiment, the first call identifier is used to uniquely identify the calling user, and the second call identifier is used to uniquely identify the called user. For example, the first call identifier is the IMSI of the calling device, and the second call identifier is the telephone number of the called device, such as 150...6789.

[0171] S602, when the called user is registered with NTN, the TN device sends the paging request to the NTN device.

[0172] Upon receiving a call request, the TN device first looks up the Visiting Location Register (DRG) based on the second call identifier (such as the called phone number) to determine the current location area of ​​the called user, and then forwards the call request to the network device corresponding to that location area. For example, if the called device is camped on an NTN, the TN device will forward the call request to the corresponding NTN device.

[0173] The S603 NTN device filters calling users based on the called user's whitelist.

[0174] After receiving a call request, the NTN device determines a whitelist of called users based on a second call identifier (such as the called phone number), and filters the calling user based on the first call request and the whitelist. Filtering the calling user can also be interpreted as filtering the call request itself, to prevent the called user from being disturbed by unimportant or low-value calls or messages under the NTN.

[0175] In one example, the whitelist stores the mapping between phone numbers and coded information, and the first call identifier carried in the call request is the calling user's IMSI. Based on this, the NTN device can convert the calling user's IMSI into the calling phone number. If the called user's whitelist includes the mapping between the calling phone number and coded information, the NTN device proceeds to the next step S604. If the called user's whitelist does not include the mapping between the calling phone number and coded information, the NTN device does not perform subsequent steps, i.e., it does not page the called user.

[0176] In this embodiment, the whitelist of the called user includes a public whitelist, a private whitelist, and a dynamic whitelist, as shown in Tables 1 to 3 above, and will not be repeated here.

[0177] In some embodiments, the public whitelist, private whitelist, and dynamic whitelist are all stored locally on the NTN device. Based on this, the NTN device can filter calling users locally according to each whitelist.

[0178] In other embodiments, the public and private whitelists are stored locally on the NTN device, while the dynamic whitelist is stored on a cloud server to protect the privacy of called users. Based on this, the NTN device filters calling users locally using the public and private whitelists, and uses the dynamic whitelist on the cloud server side to filter calling users.

[0179] Regarding the use of dynamic whitelists by NTN devices to filter calling users on the cloud server side, for example, the NTN device first sends a query request to the cloud server. This query request carries the calling user's first contact identifier (such as a phone number), which is determined based on the first caller ID (such as IMSI). After receiving the query request, the cloud server uses the dynamic whitelist to filter calling users based on the calling phone number in the query request. If the dynamic whitelist includes the calling phone number, the cloud server sends a first response message to the NTN device, which includes the encoding information corresponding to the calling phone number. If the dynamic whitelist does not include the calling phone number, the cloud server sends a second response message to the NTN device.

[0180] S604, the NTN device sends a paging message on the enhanced paging channel according to the call request. The paging message includes the first paging identifier of the calling user and the second paging identifier of the called user.

[0181] In some embodiments, the first paging identifier is the compressed, encoded contact identifier of the calling user. The NTN device can determine the first paging identifier based on the called user's whitelist. For example, if the first paging identifier corresponds to public telephone number 1, then according to the public whitelist shown in Table 1, the first paging identifier is 0001, occupying only 4 bits. As another example, if the first paging identifier corresponds to private telephone number 2, then according to the private whitelist shown in Table 2, the first paging identifier is 001, occupying only 3 bits. Yet another example, if the first paging identifier corresponds to dynamic telephone number 3, then according to the private whitelist shown in Table 3, the first paging identifier is 000010, occupying only 6 bits.

[0182] In other embodiments, the second paging identifier is the called user's paging identifier after bandwidth compression, such as the bandwidth-compressed S-TMSI. Taking the called user's original S-TMSI = AMF Set ID (10 bits) + AMF Pointer (6 bits) + 5G-TMSI (32 bits), which occupies a total of 48 bits, as an example, the bandwidth-compressed S-TMSI = AMF Set ID (6 bits) + AMF Pointer (4 bits) + 5G-TMSI (20 bits), which occupies a total of 30 bits, the bandwidth occupied is significantly reduced.

[0183] In this embodiment, the NTN device can control the first paging identifier and the second paging identifier to within 48 bits, thereby reducing the occupation of NTN resources during the paging process.

[0184] Optionally, if there is no one-to-one correspondence between the phone number and the paging identifier, the paging message must also include the identifier information of the whitelist in which the first paging identifier belongs. For example, if the first paging identifier belongs to a dynamic whitelist, the paging message must carry the identifier information of the dynamic whitelist so that the terminal device can look up the phone number corresponding to the first paging identifier in the dynamic whitelist after receiving the paging message.

[0185] S605 After receiving a paging message, the called device outputs a prompt message, which includes relevant information about the calling user and indicates that there is an incoming call from the calling user.

[0186] After receiving a paging message, the called device first checks whether the second paging identifier matches its own paging identifier. If they match, the called device determines itself to be the target of this paging. Subsequently, the called device decodes the first paging identifier according to its local whitelist, restores it to the caller's phone number, and outputs a prompt message based on the caller's phone number.

[0187] For example, there is a one-to-one correspondence between phone numbers and paging identifiers. Based on the first paging identifier being 000010, the called device can determine that the calling phone number is dynamic phone number 3 by searching all local whitelists, and output a prompt message based on dynamic phone number 3.

[0188] For example, there is no one-to-one correspondence between phone numbers and paging identifiers, but the paging message carries the identifier information of the whitelist in which the first paging identifier is located, such as the identifier information of the dynamic whitelist. Then, based on the first paging identifier being 000010, the called device can determine that the calling phone number is dynamic phone number 3 by looking up the dynamic whitelist, and output a prompt message based on dynamic phone number 3.

[0189] In some embodiments, the prompt message may be text displayed on the called device's interface and / or a prompt tone played by the called device. Additionally, the incoming call from the calling user may be a telephone call, SMS, or email; this example does not limit this. For example, the prompt message may be the text message "You have a phone call from 135…1234. Please pick up your phone and point it at the satellite to receive this call." Alternatively, if the contact name stored in the called device for 135…1234 is Zhang San, then the prompt message may be the text message "You have a phone call from Zhang San. Please pick up your phone and point it at the satellite to receive this call."

[0190] If the called user needs to receive this call, they must hold their terminal device and point it at the NTN device (such as a satellite) to establish an RRC connection and answer the call. If the called user does not want to receive this call, they can ignore or turn off this notification message.

[0191] Figure 7 is a flowchart of a communication method provided in another embodiment of this application. The method relates to a scenario where a calling device calls a called device under an NTN, and specifically includes the following steps S701 to S704.

[0192] S701, the calling device sends a call request to the NTN device, which carries the first call identifier of the calling user and the second call identifier of the called user.

[0193] It should be noted that, since the calling device is connected to the NTN device (such as a satellite), the calling device directly sends a call request to the NTN device. The specific content of this call request is detailed in S601 and will not be repeated here.

[0194] The S702 NTN device filters the calling user based on the called user's whitelist.

[0195] S703, the NTN device sends a paging message on the enhanced paging channel according to the call request. The paging message includes the first paging identifier of the calling user and the second paging identifier of the called user.

[0196] S704: After receiving a paging message, the called device outputs a prompt message to indicate that there is an incoming call from the calling user.

[0197] It should be noted that the implementation process of S702 to S704 is detailed in S603 to S605, and will not be repeated here.

[0198] (1-3) Remove from whitelist

[0199] Typically, the TN (Trunk Network) has a larger coverage area, and terminal devices mostly reside on the TN, not on the NTN (Network Telephone Network). To prevent terminal devices from occupying NTN resources for extended periods, the NTN device removes the whitelist stored in the NTN device after a preset time (e.g., 10 minutes, 1 hour, 1 day, or 3 days) to free up storage space. It should be noted that this embodiment does not impose a limit on this preset time.

[0200] In some embodiments, after the NTN device detects that a terminal device has left the NTN, it starts a timer. For example, the duration of this timer can be 10 minutes, 1 hour, 1 day, 3 days, etc., and this application embodiment does not impose any limitations on this. If the NTN device does not detect that the terminal device has re-entered the NTN before the timer expires, it deletes the device from the locally stored whitelist.

[0201] In other embodiments, as shown in Figure 8, after detecting that the terminal device is registered on the TN, the TN device sends a deregistration notification to the NTN device to instruct the NTN device to deregister the called user from the whitelist. Upon receiving the deregistration notification, the NTN device starts a timer. For example, the timer duration can be 10 minutes, 1 hour, 1 day, 3 days, etc. If the NTN device does not detect that the terminal device is registered on the NTN again before the timer expires, it deletes the locally stored whitelist.

[0202] Optionally, in the above embodiments, if the NTN device detects that the terminal device is re-entering the NTN before the timer expires, the timer is turned off and the local whitelist is not deleted.

[0203] In addition, the called device can also delete the various whitelists stored locally after residing in the TN for a preset time, or only delete the dynamic whitelist while retaining the public and private whitelists, in order to reduce the memory usage of the terminal device.

[0204] It should be noted that since the TAU can identify the network registration location of the terminal device, NTN devices, TN devices, and terminal devices can determine the network access status of the terminal device based on the terminal device's current TAU ​​and the TAU before the update, such as whether it has changed from NTN to TN, or whether it has reconnected to NTN, etc.

[0205] The communication method provided in this application provides several advantages. Firstly, the NTN device can notify the called user of the calling user's identification information during paging, allowing the called user to understand which calling user the call originated from and decide whether to accept the call through a series of star level operations, thus improving user experience. Secondly, the NTN device can filter calling users, preventing called users from being disturbed by unimportant or low-value incoming calls and reducing the number of paging attempts, thereby conserving NTN resources. Thirdly, during the paging process, the NTN device can compress the calling and called user identifiers in the paging message, reducing the paging message's impact on NTN air interface resources.

[0206] (ii) The calling user calls the called user based on a cloud server.

[0207] The method provided in this application can be applied to scenarios where the calling user actively communicates with the called user through applications such as Connect and iMessage. Unlike communication scenarios based on carrier networks, in this embodiment, the cloud server filters the calling user and generates the paging message, while the NTN device only sends the paging message.

[0208] This embodiment mainly involves three aspects, including (2-1) setting a whitelist, (2-2) the cloud server paging the called user based on the whitelist, and (2-3) deleting the whitelist.

[0209] (2-1) Setting up a whitelist

[0210] In this embodiment, the whitelist includes a public whitelist, a private whitelist, and a dynamic whitelist. It should be noted that the process of setting up a whitelist locally on the terminal device is the same in both Content (II) and Content (I), therefore, it will not be described in detail in Content (II). The process of setting up a whitelist on a cloud server will be described in detail below.

[0211] (2-1-a) Setting up a public whitelist

[0212] In some embodiments, after detecting that a user has successfully registered with the NTN, the TN device can send the user's whitelist to the cloud server in advance, and the cloud server receives and stores the whitelist.

[0213] (2-1-b) Setting up a private whitelist

[0214] In some embodiments, after a terminal device successfully registers with the NTN, it sends the user-defined private phone number to the cloud server. The cloud server encodes these private phone numbers using the same encoding rules as the terminal device (such as adaptive Huffman coding), thereby generating a private whitelist that stores the user.

[0215] It's understandable that for the same user, the private whitelist is the same on both the terminal device and the server side. The cloud server can also update the private whitelist based on instructions from the terminal device.

[0216] (2-1-c) Setting up a dynamic whitelist

[0217] As shown in Figure 9, after the terminal device successfully registers with the NTN, the cloud server updates and stores the dynamic whitelist through the NTN device and the terminal device via the following steps S901 to S911. It should be noted that in this communication scenario, since the terminal device is under the NTN, all communication between it and the cloud server needs to be relayed through the NTN device.

[0218] S900, the cloud server sends a first synchronization message to the terminal device, which is used to synchronize the encoding status of the dynamic whitelist.

[0219] For example, the cloud server can determine whether a terminal device is residing on an NTN based on notifications from the terminal device or the NTN device. After detecting that the terminal device is residing on the NTN, the cloud server can send a first synchronization message to the terminal device. In some embodiments, both the cloud server and the terminal device use adaptive Huffman coding to generate a dynamic whitelist. Based on this, the first synchronization message is used to synchronize the largest encoded ID (ID = M) in the cloud server's dynamic whitelist.

[0220] For example, the cloud server can encode each historical call number according to the order in which user calls were successfully made. For instance, the encoding IDs of historical call numbers are 1, 2, 3, 4, 5, etc., according to the order of successful calls. Based on this, in S901, if the encoding ID on the NTN device side is 3, then the first synchronization message will notify the terminal device that the encoding ID = 3.

[0221] Through the first synchronization message, the cloud server and the terminal device can maintain the consistency of the current dynamic whitelist encoding status, so that when the cloud server and the terminal device update the dynamic whitelist in the future, the consistency of the dynamic whitelist on both sides can still be maintained.

[0222] S901, the terminal device calls the target number through the NTN device.

[0223] S902, the terminal device sends a first indication message to the cloud server through the NTN device, the first indication message being used to indicate that the target number is a dynamic number.

[0224] For example, the first indication information may be a call request sent by the terminal device during the process of calling the target number, or other communication messages between the terminal device and the cloud server. This embodiment does not limit this.

[0225] In some embodiments, the terminal device may first determine the type of the target number. If the target number is a dynamic number, the terminal device sends a first indication message to the cloud server during or after calling the target number. This first indication message indicates that the target number is a dynamic number or instructs the cloud server to add the number to a dynamic whitelist. If the target number is not a dynamic number, the first indication message is not sent.

[0226] S903, the cloud server sends a second indication message to the terminal device through the NTN device. This second indication message is used to indicate that the target number has been successfully called.

[0227] It should be noted that "the target number has been successfully called" means that the terminal device corresponding to the target number has successfully displayed the incoming call reminder interface. This embodiment does not limit whether the call was successfully answered.

[0228] S904, the terminal device sends a response message to the cloud server through the NTN device. This response message is used to indicate that the terminal device has received the second indication information.

[0229] S905, the cloud server determines whether the target number is a dynamic number.

[0230] S906, if the target number is a dynamic number, the cloud server will compress and encode the target number to obtain the encoded information.

[0231] In some embodiments, the cloud server uses adaptive Huffman coding to compress and encode the target number according to the encoding ID = M+1 to obtain the corresponding encoding information.

[0232] S907, the cloud server sends a second synchronization message to the terminal device through the NTN device. This second synchronization message is used to resynchronize the encoding status of the dynamic whitelist.

[0233] In some embodiments, the second synchronization message is used to synchronize the largest encoded ID in the dynamic whitelist of the cloud server, which is M+1. For example, if the encoded ID in the first synchronization message in S900 is 3, then the encoded ID in the second synchronization message is 4.

[0234] S908, cloud server startup timer.

[0235] For example, the duration of the timer can be 1 minute, 3 minutes, or 5 minutes, etc., and this application embodiment does not limit this.

[0236] S909: After receiving the second synchronization message, the terminal device compresses and encodes the target number to obtain the encoded information, and stores the correspondence between the target number and its encoded information in the dynamic whitelist.

[0237] In some embodiments, the terminal device uses the same encoding method as the NTN device, compressing the target number according to the encoding ID = M+1. Therefore, the correspondence between the encoding ID, the target number, and the encoding information is the same on both the NTN device and the terminal device side. Consequently, the dynamic whitelists of the NTN device and the terminal device are also the same.

[0238] Depending on the encoding of the target number and the communication status of the terminal device, the specific implementation of S910 is S910a, S910b, or S910c.

[0239] S910a, the terminal device sends a third indication message to the cloud server through the NTN device. This third indication message is used to indicate that the target number encoding was successful.

[0240] In other words, after successfully encoding the target information, the terminal device notifies the cloud server via the NTN device. Additionally, the terminal device will disable the timer upon receiving the third instruction.

[0241] In S910b, the terminal device sends a fourth indication message to the cloud server through the NTN device. This fourth indication message is used to indicate that the target number encoding has failed.

[0242] In other words, after the terminal device fails to encode the target information, it notifies the cloud server via the NTN device. Additionally, the terminal device will shut down the timer after receiving the fourth instruction.

[0243] S910c, the cloud server detected that the timer has expired.

[0244] In other words, the cloud server did not receive the third instruction message or the fourth instruction message from the terminal device within the preset time.

[0245] Depending on the specific implementation of S910, the specific implementation of S911 will also differ; S911 can be either S911a or S911b. Specifically, after S910a, the NTN device executes S911a; while after S910b or S910c, the NTN device executes S911b.

[0246] S911a: The cloud server stores the correspondence between target numbers and their encoding information in a dynamic whitelist.

[0247] S911b, the cloud server deletes the encoding information of the target number.

[0248] Through the above steps S901 to S911, each time the terminal device actively calls a dynamic number under NTN, the terminal device and the cloud server can add it to the corresponding user's dynamic whitelist respectively. This method not only ensures that the whitelists on the terminal device and the cloud server are completely identical, but also avoids the correspondence between telephone numbers and encoding information transmitted over the air interface, thus having better information security.

[0249] (2-2) Cloud server paging of called users based on whitelist

[0250] Figure 10 is a flowchart of a communication method provided in another embodiment of this application. The method involves a scenario where a calling user calls a called device through a cloud server, and specifically includes the following steps S1001 to S1005.

[0251] S1001, the calling device sends a call request to the cloud server, which carries the first call identifier of the calling user and the second call identifier of the called user.

[0252] For example, the first call identifier is the calling user's phone number or IMSI, and the second call identifier is the called user's phone number, such as "150……6789".

[0253] S1002, when the called user resides in NTN, the cloud server filters the calling user based on the called user's whitelist.

[0254] After receiving a call request, the cloud server determines the whitelist of called users locally based on the second call identifier, and then filters the calling user according to this whitelist. In this embodiment, the whitelist of called users includes a public whitelist, a private whitelist, and a dynamic whitelist, as shown in Tables 1 to 3 above, and will not be repeated here. Since the public whitelist, private whitelist, and dynamic whitelist are all stored locally on the cloud server, the cloud server can filter the calling user locally according to each whitelist.

[0255] Taking the mapping between phone numbers and coded information in a whitelist as an example, the cloud server can determine the calling phone number based on the calling user's first call identifier. If the calling phone number is included in the called user's dynamic whitelist, the cloud server will proceed with subsequent steps and call the user. If the calling phone number is not included in the dynamic whitelist, the cloud server will not proceed with subsequent steps, that is, it will not respond to the calling user's call request, or in other words, it will not call the called device, to avoid the called user being disturbed by low-value information under NTN.

[0256] S1003, the cloud server sends a paging message to the NTN device. The paging message includes the first paging identifier of the calling user and the second paging identifier of the called user.

[0257] After receiving a call request, the cloud server first looks up the location register based on the second call identifier to determine the current location area of ​​the called device, and then sends the paging message to the network device corresponding to that location area. For example, if the called device is registered with an NTN, the cloud server sends the paging message to the corresponding NTN device. The specific content of the paging message is described in section S604 and will not be repeated here.

[0258] S1004, the NTN device sends the paging message on the enhanced paging channel.

[0259] In this embodiment, the NTN device sends the paging message through the enhanced paging channel, which can ensure that the paging message is delivered to the called device more timely and effectively, thereby improving communication efficiency, communication quality and user experience.

[0260] S1005: After receiving the paging message, the called device outputs a prompt message to indicate that a message from the calling user has arrived. See S605 for details, which will not be repeated here.

[0261] The communication method provided in this application addresses scenarios where a called device is called via an instant messaging application (such as MeeTime or iMessage) under NTN. Firstly, the cloud server can notify the called user of the calling user's information during the paging process through the NTN device. This allows the called user to understand which calling user the call originated from and decide whether to accept the call through a series of star level operations, thus improving the user experience. Secondly, the cloud server can filter calling users, preventing the called user from being disturbed by unimportant or low-value incoming calls and reducing the number of paging attempts by the NTN device, saving NTN resources. Thirdly, during the paging process through the NTN device, the cloud server can compress the calling and called user identifiers in the paging message, reducing the paging message's impact on NTN air interface resources.

[0262] (2-3) Remove from whitelist

[0263] In some embodiments, the cloud server starts a timer after detecting that a terminal device has left the NTN. For example, the timer duration is 1 day, 3 days, etc. If the cloud server does not detect that the terminal device re-enters the NTN network before the timer expires, it does not delete the locally stored whitelist. Optionally, in the above embodiments, if the NTN device detects that the terminal device re-enters the NTN before the timer expires, it shuts down the timer.

[0264] In other embodiments, the called device may also delete the various whitelists stored locally after residing on the TN for a preset time. Alternatively, only the dynamic whitelist may be deleted, while the public and private whitelists are retained to reduce the memory usage of the terminal device.

[0265] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0266] Based on the same concept, as an implementation of the above method, this application provides a communication device. This device embodiment corresponds to the aforementioned method embodiment. For ease of reading, this device embodiment will not repeat the details of the aforementioned method embodiment one by one, but it should be clear that the device in this embodiment can implement all the contents of the aforementioned method embodiment.

[0267] Figure 11 is a schematic diagram of a communication device provided in an embodiment of this application. As shown in Figure 11, the device is applied to a terminal device and includes a receiving module 1101, an output module 1102, and a whitelist management module 1103.

[0268] The receiving module 1101 is used to receive a paging message, which includes a first paging identifier of the calling user and a second paging identifier of the called user, wherein the second paging identifier is matched with the identification information of the terminal device.

[0269] The output module 1102 is used to output a prompt message, which includes relevant information of the calling user corresponding to the first paging identifier, and is used to indicate that there is an incoming call from the calling user.

[0270] Optionally, the device also includes a whitelist management module 1103, used to generate and store a public whitelist based on public phone numbers from a TN device or a terminal device SIM card, using a preset compression encoding method. And / or, using a preset compression encoding method, to generate and store a private whitelist based on private phone numbers determined by user operations. And / or, using a preset compression encoding method, to generate and store a dynamic whitelist based on phone numbers successfully called by the called user under the NTN within a preset time period.

[0271] Figure 12 is a schematic diagram of a communication device provided in another embodiment of this application. As shown in Figure 12, the device, applied to an NTN device or a cloud server, includes a sending module 1201, a receiving module 1202, an information generation module 1203, and a whitelist management module 1204.

[0272] The sending module 1201 is used to send a paging message, which includes a first paging identifier of the calling user and a second paging identifier of the called user, and the terminal device used by the called user is camped on the NTN.

[0273] In some embodiments, the receiving module 1202 is configured to receive a paging message before sending the paging message.

[0274] In other embodiments, the receiving module 1202 is configured to receive a call request before sending a paging message, the call request including a first call identifier of the calling user and a second call identifier of the called user.

[0275] The information generation module 1203 is used to determine the first paging identifier of the user based on the first call identifier; determine the second paging identifier of the called user based on the second call identifier; and generate a paging message based on the first paging identifier and the second paging identifier.

[0276] The whitelist management module 1204 is used to generate and store a public whitelist based on public phone numbers from TN devices using a preset compression encoding method. And / or, it generates and stores a private whitelist based on private phone numbers from terminal devices using a preset compression encoding method. And / or, it generates and stores a dynamic whitelist based on phone numbers successfully called by the called user under the NTN within a preset time period using a preset compression encoding method.

[0277] This application also provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it can implement the communication method executed by the called device as described in the above embodiments.

[0278] This application also provides an NTN device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it can implement the communication method performed by the NTN device in the above embodiments.

[0279] This application also provides a cloud server, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it can implement the communication method executed by the cloud server in the above embodiments.

[0280] This application also provides a chip, as shown in FIG13. The chip includes a processor and a memory. The memory stores a computer program. When the computer program is executed by the processor, it implements the communication methods executed by the called device, cloud server or NTN device in the above embodiments.

[0281] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the communication methods performed by the called device, cloud server, or NTN device in the above embodiments.

[0282] This application also provides a computer program product, which includes a computer program that, when run by an electronic device, enables the electronic device to implement the communication methods executed by the called device, cloud server, or NTN device in the above embodiments.

[0283] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0284] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0285] In the embodiments provided in this application, the division of each framework or module is only a logical functional division. In actual implementation, there may be other division methods. For example, multiple frameworks or modules may be combined or integrated into another system, or some features may be ignored or not executed.

[0286] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0287] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0288] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0289] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A communication method, characterized in that, Applied to terminal devices, where the terminal devices reside on a non-terrestrial network (NTN), the method includes: Receive a paging message, the paging message including a first paging identifier of the calling user and a second paging identifier of the called user, the second paging identifier being matched with the identification information of the terminal device; Output a prompt message, which includes relevant information about the calling user corresponding to the first paging identifier, to indicate that there is an incoming call from the calling user.

2. The method according to claim 1, characterized in that, The first paging identifier is an identifier obtained by compressing and encoding the first contact identifier of the calling user, and the bit width of the first paging identifier is smaller than that of the first contact identifier. And / or, The second paging identifier is the identifier information obtained by compressing the bit width of the paging identifier of the called user.

3. The method according to claim 2, characterized in that, The combined bit width of the first paging identifier and the second paging identifier is less than 48 bits.

4. The method according to any one of claims 1 to 3, characterized in that, The calling user belongs to the whitelist of the called user, and the whitelist includes the correspondence between the calling user's contact identifier and paging identifier.

5. The method according to claim 4, characterized in that, The contact identifier is a telephone number, and the whitelist includes at least one of the following: A public whitelist, which includes the correspondence between public telephone numbers and paging identifiers; Private whitelist, which includes the correspondence between the private phone number set by the called user and the paging identifier; The dynamic whitelist includes the correspondence between the phone numbers and paging identifiers that the called user has successfully called under the NTN within a preset time period.

6. The method according to claim 5, characterized in that, Prior to receiving the paging message, the method further includes: The public telephone number can be received from a terrestrial network (TN) device or obtained from a subscriber identification module (SIM) card. The public whitelist is generated and stored based on the public phone numbers using a preset compression encoding method. And / or, The private phone number is determined based on user actions; The private whitelist is generated and stored based on the private phone number using a preset compression encoding method. And / or, Determine the phone numbers that the called user has successfully called under the NTN within a preset time period; The dynamic whitelist is generated and stored based on the phone numbers that have been successfully called using a preset compression encoding method.

7. The method according to any one of claims 1 to 6, characterized in that, Receiving the paging message includes: receiving the paging message in an enhanced paging channel.

8. A communication method, characterized in that, Applied to non-terrestrial network (NTN) devices or cloud servers, the method includes: A paging message is sent, the paging message including a first paging identifier of the calling user and a second paging identifier of the called user, and the terminal device used by the called user is camped on NTN.

9. The method according to claim 8, characterized in that, The first paging identifier is an identifier obtained by compressing and encoding the first contact identifier of the calling user, and the bit width of the first paging identifier is smaller than that of the contact identifier; And / or, The second paging identifier is the identifier information obtained by compressing the bit width of the paging identifier of the called user.

10. The method according to claim 9, characterized in that, The combined bit width of the first paging identifier and the second paging identifier is less than 48 bits.

11. The method according to any one of claims 8 to 10, characterized in that, Prior to sending the paging message, the method further includes: Receive the paging message; or, Receive a call request, the call request including the first call identifier of the calling user and the second call identifier of the called user; The first paging identifier of the calling user is determined based on the first call identifier; The second paging identifier of the called user is determined based on the second call identifier; The paging message is generated based on the first paging identifier and the second paging identifier.

12. The method according to claim 11, characterized in that, Determining the first paging identifier of the calling user based on the first call identifier includes: Based on the first call identifier, the first contact identifier of the calling user is determined; wherein, there is a preset correspondence between the call identifier and the contact identifier; The first paging identifier is determined based on the correspondence between the first contact identifier and the first paging identifier in the whitelist.

13. The method according to claim 12, characterized in that, When the method is applied to an NTN device, determining the first paging identifier based on the correspondence between the first contact identifier and the first paging identifier in the whitelist includes: Send query information to the cloud server. The query information includes a first contact identifier corresponding to the first call identifier, which is used to query whether the calling user belongs to the private whitelist. Receive a first query result, which indicates that the calling user belongs to the private whitelist and includes the first paging identifier corresponding to the first contact identifier; or, Receive a second query result, which indicates that the calling user is not in the private whitelist.

14. The method according to any one of claims 11 to 13, characterized in that, The contact identifier is a telephone number, and the whitelist includes at least one of the following: A public whitelist, which includes the correspondence between public telephone numbers and paging identifiers; Private whitelist, which includes the correspondence between the private phone number set by the called user and the paging identifier; The dynamic whitelist includes the correspondence between the phone numbers and paging identifiers that the called user has successfully called under the NTN within a preset time period.

15. The method according to claim 14, characterized in that, Prior to sending the paging message, the method further includes: Receive the public telephone number from the TN device; The public whitelist is generated and stored based on the public phone numbers using a preset compression encoding method. And / or, Obtain the private phone number specified by the user; The private whitelist is generated and stored based on the private phone number using a preset compression encoding method. And / or, Determine the phone numbers that the called device has actively called under the NTN within a preset time period; The dynamic whitelist is generated and stored based on the user identifiers of those who have made active calls, using a preset compression encoding method.

16. The method according to any one of claims 12 to 15, characterized in that, The method further includes: After a preset time has elapsed since the terminal device used by the called user disconnected from the NTN device, the whitelist of the called user stored locally is deleted.

17. The method according to any one of claims 8 to 16, characterized in that, When the method is applied to an NTN device, sending the paging message includes: sending the paging message on an enhanced paging channel.

18. An electronic device, characterized in that, The method includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method as described in any one of claims 1 to 7.

19. A cloud server, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method as described in any one of claims 8 to 12 and 14 to 17.

20. A non-terrestrial network (NTN) device, characterized in that, The method includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method as described in any one of claims 8 to 17.

21. A chip, characterized in that, The chip includes a processor and a memory, the memory storing a computer program that, when executed by the processor, implements the method as described in any one of claims 1 to 17.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method as described in any one of claims 1 to 17.

23. A computer program product, characterized in that, The computer program product includes a computer program that, when run by an electronic device, causes the electronic device to perform the method as described in any one of claims 1 to 17.

Images