WO2021135602A1

WO2021135602A1 - Number privacy protection method, network device and computer storage medium

Info

Publication number: WO2021135602A1
Application number: PCT/CN2020/125205
Authority: WO
Inventors: 王冲; 叶筠
Original assignee: 华为技术有限公司
Priority date: 2020-01-04
Filing date: 2020-10-30
Publication date: 2021-07-08
Also published as: CN113079258A

Abstract

The present application is applicable to the technical field of software applications, and provides a number privacy protection method, a network device and a computer storage medium. Said method can be applied to an artificial intelligence (AI) terminal. Said method comprises: a network device acquiring a call request sent by a first terminal device, the call request comprising a verification token and a first phone number of a first calling party; the network device verifying the first phone number according to the verification token; and if the verification of the first phone number is passed, the network device acquiring a second phone number associated with the verification token, and establishing call connection between the first phone number and the second phone number. The present application can solve the problem in the prior art that the privacy security of a user is affected due to easy leakage of the user's number.

Description

Number privacy protection method, network equipment and computer storage medium

This application claims the priority of a Chinese patent application filed with the State Intellectual Property Office, the application number is 202010007477.8, and the application name is "number privacy protection method, network equipment and computer storage medium" on January 4, 2020, the entire content of which is by reference Incorporated in this application.

Technical field

This application belongs to the technical field of software applications, and in particular relates to a number privacy protection method, network equipment and computer storage media.

Background technique

In daily work and life, sometimes users need to share their phone numbers with some organizations or individuals so that others can contact them in time. However, some organizations or individuals may arbitrarily share or sell other people's phone numbers, causing users to receive a large number of harassing calls, such as product promotion calls, fraud calls, etc., which affects users' privacy and security.

Summary of the invention

In view of this, the embodiments of the present application provide a number privacy protection method, network equipment, and computer storage medium to solve the problem that existing user numbers are easy to leak and affect user privacy and security.

The first aspect of the embodiments of the present application provides a number privacy protection method, including:

The network device obtains a call request sent by the first terminal device, where the call request includes a verification token and the first phone number of the first calling party;

The network device verifies the first phone number according to the verification token;

If the first phone number is verified, the network device obtains the second phone number associated with the verification token, and establishes a call connection between the first phone number and the second phone number.

It should be noted that the first calling party does not directly use the called party's second phone number to make a call, but uses a verification token to make a call, which means that the called party does not need to show the second phone directly when showing the contact information. Instead, just show the verification token, so as to realize the anonymization of the called party’s phone number and prevent the called party’s second phone number from being leaked unintentionally or maliciously.

In addition, the verification token is associated with the phone number of the designated user. When the calling party calls the called party through the verification token, the network device will check the first phone number of the first calling party according to the verification token. Perform verification. Only when the first calling party is the designated user, the verification token can pass the verification. Therefore, even if the verification token is leaked, other non-designated users cannot call the called party through the verification token.

In a possible implementation manner of the first aspect, before the network device obtains the call request sent by the first terminal device, the method further includes:

Acquiring, by the network device, a first creation request sent by a second terminal device, where the first creation request includes the second phone number and the third phone number of the second calling party;

The network device creates the verification token according to the second phone number and the third phone number;

The network device sends the verification token to the designated recipient.

It should be noted that when creating a verification token, if the called party can directly obtain the third phone number of the second calling party, the network device can directly create a verification order based on the second phone number and the third phone number. The creation process of the verification token is relatively convenient.

In another possible implementation manner of the first aspect, before the network device obtains the call request sent by the first terminal device, the method further includes:

Acquiring, by the network device, an identity request sent by a third terminal device, where the identity request includes the third telephone number of the second calling party;

The network device creates a first identity corresponding to the third telephone number, and returns the first identity to the third terminal device;

Acquiring, by the network device, a first creation request sent by a second terminal device, where the first creation request includes the second phone number and the first identity;

The network device queries a third phone number corresponding to the first identity identifier, and creates the verification token according to the second phone number and the third phone number;

The network device sends the verification token to the designated recipient.

It should be noted that if the second calling party is worried that the third phone number will be leaked, the second calling party may also show the first identity to the called party. At this time, the called party can know the first identity, but cannot know the third phone number, so that the third phone number is anonymized. When the network device obtains the first creation instruction, it queries the third phone number corresponding to the first identity, and then creates a verification token based on the second phone number and the third phone number.

It can be seen from the above that this verification token creation method is relatively cumbersome, but it can realize the anonymization of the third phone number and prevent the third phone number from being leaked.

In a possible implementation manner of the first aspect, sending, by the network device, the verification token to a designated recipient includes:

The network device sends the verification token to the second terminal device, or sends the verification token to the third terminal device.

It should be noted that the network device may directly send the verification token to the third-end device, or the network device may also send the verification token to the second terminal device, and the called party will show the verification token to the second terminal device. The second calling party.

In a possible implementation manner of the first aspect, if the first phone number is verified, the network device obtains a second phone number associated with the verification token, and establishes the first phone number. The call connection between a phone number and the second phone number includes:

If the first phone number is consistent with the third phone number, the network device obtains the second phone number associated with the verification token, and establishes the first phone number and the second phone number Call connection.

It should be noted that when the first phone number is verified according to the verification token, the third phone number corresponding to the verification token can be obtained, and it is determined whether the first phone number is consistent with the third phone number.

If the first phone number is consistent with the third phone number, it means that the first calling party and the second calling party are the same user, and the first calling party has the right to call the second phone number.

If the first phone number is not consistent with the third phone number, it means that the first calling party and the second calling party are not the same user, and the first calling party does not have the authority to call the second phone number.

In a possible implementation of the first aspect, the network device acquiring a second phone number associated with the verification token, and establishing a call connection between the first phone number and the second phone number includes :

The network device obtains the second phone number associated with the verification token, and sends the first phone number and the second phone number to the teleconference server to instruct the teleconference server to transfer the first A phone number and the second phone number are pulled into the same conference call.

It should be noted that in the process of establishing a call connection between the first phone number and the second phone number, the call connection between the first phone number and the second phone number may be established in the form of a conference call. At this time, even if the operator network of the first calling party and the operator network of the called party are different, the above solution can be implemented smoothly.

Moreover, when a call connection in the form of a conference call is used, the numbers displayed on the first terminal device and the second terminal device are the conference number of the conference call, not the real number of the first phone number or the real number of the second phone number, Thereby protecting the privacy of the first phone number and the second phone number.

The second aspect of the embodiments of the present application provides a network device, including:

A call request module, configured to obtain a call request sent by a first terminal device, the call request including a verification token and the first phone number of the first calling party;

A number verification module, configured to verify the first phone number according to the verification token;

A call connection module, configured to obtain a second phone number associated with the verification token if the first phone number is verified, and establish a call connection between the first phone number and the second phone number .

In a possible implementation manner of the second aspect, the network device further includes:

A creation request module, configured to obtain a first creation request sent by a second terminal device, where the first creation request includes the second phone number and the third phone number of the second calling party;

A token creation module, configured to create the verification token according to the second phone number and the third phone number;

The token sending module is used to send the verification token to the designated receiver.

An identity request module, configured to obtain an identity request sent by a third terminal device, where the identity request includes the third phone number of the second calling party;

An identity module, configured to create a first identity corresponding to the third phone number, and return the first identity to the third terminal device;

A creation request module, configured to obtain a first creation request sent by a second terminal device, the first creation request including the second phone number and the first identity;

A token creation module, configured to query a third phone number corresponding to the first identity identifier, and create the verification token according to the second phone number and the third phone number;

In another possible implementation manner of the second aspect, the token sending module is specifically configured to send the verification token to the second terminal device, or send the verification token To the third terminal device.

In a possible implementation of the second aspect, the call connection module is specifically configured to, if the first phone number is consistent with the third phone number, obtain the first phone number associated with the verification token. Two phone numbers, establishing a call connection between the first phone number and the second phone number.

In a possible implementation manner of the second aspect, the call connection module includes:

The teleconference submodule is used to obtain the second telephone number associated with the verification token, and send the first telephone number and the second telephone number to the telephone conference server to instruct the telephone conference server to The first phone number and the second phone number are pulled into the same conference call.

The third aspect of the embodiments of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and running on the processor. When the processor executes the computer program, Implement the steps as described above.

The fourth aspect of the embodiments of the present application provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the foregoing method are implemented.

The fifth aspect of the embodiments of the present application provides a computer program product, which when the computer program product runs on a terminal device, enables the terminal device to implement the steps of the above-mentioned method.

Compared with the prior art, the embodiments of this application have the following beneficial effects:

The embodiment of the application provides a number privacy protection method. When the first terminal device as the first calling party wants to call the called party, it sends a call request to the network device. The call request includes the verification token and the first terminal device. The first phone number of a calling party. The network device verifies the first phone number according to the verification token. If the first phone number is verified, the second phone number associated with the verification token is obtained, and a call connection between the first phone number and the second phone number is established.

That is to say, in the method of this example, the first calling party does not directly make a call through the called party’s second phone number, but makes a call through a verification token. When the called party shows the contact information, It is not necessary to directly show the second phone number, but just show the verification token, so as to realize the anonymization of the called party's phone number and avoid the called party's second phone number from being unintentionally or maliciously leaked.

In addition, the verification token is associated with the phone number of the designated user. When the calling party calls the called party through the verification token, the network device will check the first phone number of the first calling party according to the verification token. Perform verification to determine whether the call of the first calling party is legal. Only when the first calling party is the designated user, the verification token can pass the verification. Therefore, even if the verification token is leaked, other non-designated users cannot call the called party through the verification token, which prevents the called party from frequently receiving harassing calls due to the leak of the verification token, which improves the user’s privacy and security. It has strong ease of use and practicality.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only of the present application. For some embodiments, those of ordinary skill in the art can obtain other drawings based on these drawings without creative work.

FIG. 1 is a schematic flowchart of a method for protecting number privacy according to an embodiment of the present application;

Figure 2 is a signaling diagram of an application scenario provided by an embodiment of the present application;

Figure 3 is a signaling diagram of another application scenario provided by an embodiment of the present application;

Figure 4 is a signaling diagram of another application scenario provided by an embodiment of the present application;

Figure 5 is a signaling diagram of another application scenario provided by an embodiment of the present application;

Figure 6 is a signaling diagram of another application scenario provided by an embodiment of the present application;

Figure 7 is a signaling diagram of another application scenario provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a network device provided by an embodiment of the present application;

Fig. 9 is a schematic structural diagram of another network device provided by an embodiment of the present application.

Detailed ways

In the following description, for the purpose of illustration rather than limitation, specific details such as a specific system structure and technology are proposed for a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application can also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid unnecessary details from obstructing the description of this application.

In order to illustrate the technical solutions described in the present application, specific embodiments are used for description below.

It should be understood that when used in this specification and the appended claims, the term "comprising" indicates the existence of the described features, wholes, steps, operations, elements and/or components, but does not exclude one or more other features , The existence or addition of a whole, a step, an operation, an element, a component, and/or a collection thereof.

It should also be understood that the terms used in the specification of this application are only for the purpose of describing specific embodiments and are not intended to limit the application. As used in the specification of this application and the appended claims, unless the context clearly indicates other circumstances, the singular forms "a", "an" and "the" are intended to include plural forms.

It should be further understood that the term "and/or" used in the specification and appended claims of this application refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations .

As used in this specification and the appended claims, the term "if" can be interpreted as "when" or "once" or "in response to determination" or "in response to detection" depending on the context . Similarly, the phrase "if determined" or "if detected [described condition or event]" can be interpreted as meaning "once determined" or "in response to determination" or "once detected [described condition or event]" depending on the context ]" or "in response to detection of [condition or event described]".

The number privacy protection method provided in the embodiments of the present application can be applied to network equipment. The network device can be any device with data transmission and reception and data processing functions, including but not limited to smart phones, tablets, wearable devices, vehicle-mounted devices, augmented reality (AR)/virtual reality (VR) Equipment, laptops, ultra-mobile personal computers (UMPC), netbooks, personal digital assistants (PDAs), artificial intelligence (AI) terminals and other network equipment. The embodiments of this application do not impose any restrictions on the specific types of network devices.

For example, the network device may be a station (STAION, ST) in a WLAN, a cell phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, Personal Digital Assistant (PDA) devices, handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, in-vehicle devices, car networking terminals, computers, laptop computers, handheld communication devices , Handheld computing devices, satellite wireless devices, customer premise equipment (CPE) and/or other devices used to communicate on wireless systems, and next-generation communication systems, such as mobile terminals in 5G networks or the future Mobile terminals in the evolved Public Land Mobile Network (PLMN) network.

In addition, in the description of this application, the terms "first", "second", "third", etc. are only used to distinguish the description, and cannot be understood as indicating or implying relative importance.

In daily work and life, sometimes users need to share their phone numbers with some organizations or individuals so that others can contact them in time. However, some organizations or individuals may arbitrarily share or sell others' phone numbers, causing users to receive a large number of harassing calls, such as product promotion calls and fraudulent calls.

In order to reduce the interference of harassing calls, users can block some harassing phone numbers through the blacklist function of the mobile phone to ensure that they will not receive calls and messages from these blocked numbers in the future.

This method is a passive defense method that relies on each user to mark the number of the harassing call. In addition, many harassing calls are now dialed through virtual dialing software, using virtual numbers. Even if the user pulls the virtual number into the blacklist, the harasser can change the virtual number to continue the harassment. The blacklist has the effect of blocking harassing calls limited.

In this regard, when sharing phone numbers, other users will share very frequently used phone numbers (commonly known as "small numbers") with institutions or individuals that cannot be fully trusted, so as to avoid frequent harassing calls to their frequently used phone numbers.

However, if the user's very frequently used phone number is maliciously leaked, the user will still receive a large number of harassing calls. This method can only protect the user's frequently used phone number and play a certain anonymous role. If users frequently update unused phone numbers to reduce nuisance calls, the unused phone numbers are not suitable for organizations or individuals who need to keep in touch for a long time and cannot be fully trusted.

In other number privacy protection schemes, users can enter their real phone number into the scan code and call the front desk. Scan the QR code to call the front desk to generate a QR code based on the user's real phone number, store the user information and the QR code in the relational database, and return the QR code to the user. When users need to share their contact information with others, they can show the QR code as the contact information. Later, when the caller needs to call the user, he can scan the QR code to access the scan code to call the front desk, and the scan code to call the front desk returns the middle number assigned by the middle number platform to the caller. The caller dials the intermediate number, and the operator roams to the intermediate number platform, and the intermediate number platform is transferred to the user's real number, so that the caller can call the user.

In this way, the user number can be anonymized. However, if the above two-dimensional code is maliciously shared, users will still receive a large number of harassing calls. At the same time, if the above two-dimensional code is set with an expiration time, it is not suitable for some organizations or individuals who need to stay in contact for a long time and cannot be fully trusted. In addition, the implementation of the above solution relies on the support of operator network roaming, and it is difficult to implement the above solution when the operator network of the caller and the user are different.

In summary, none of the existing user number privacy protection solutions can effectively prevent users from receiving harassing calls. In view of this, the embodiment of the application provides a number privacy protection method. When the first terminal device as the first calling party wants to call the called party, it sends a call request to the network device, and the call request includes verification. The token and the first phone number of the first caller. The network device verifies the first phone number according to the verification token. If the first phone number is verified, the second phone number associated with the verification token is obtained, and a call connection between the first phone number and the second phone number is established.

In addition, the verification token is associated with the phone number of the designated user. When the calling party calls the called party through the verification token, the network device will check the first phone number of the first calling party according to the verification token. Perform verification to determine whether the call of the first calling party is legal. Only when the first calling party is the designated user, the verification token can pass the verification. Therefore, even if the verification token is leaked, other non-designated users cannot call the called party through the verification token, which prevents the called party from frequently receiving harassing calls due to the leak of the verification token.

Therefore, the number privacy protection method provided in this embodiment solves the problem that existing user numbers are easy to leak and affect user privacy and security.

Next, from the perspective of a network device, the content of the number privacy protection method provided in this embodiment will be described. Please refer to the flowchart of the number privacy protection method shown in Figure 1. The method includes:

S101. A network device obtains a call request sent by a first terminal device, where the call request includes a verification token and the first phone number of the first calling party.

In the following content of this embodiment, the first terminal device is the terminal device of the first calling party, the second terminal device is the terminal device of the called party, and the third terminal device is the terminal device of the second calling party.

The first calling party is a user who wants to call the called party, and the second calling party is a user who interacts with the called party. It is understandable that the first calling party and the second calling party may be the same user or different users.

If the first calling party wants to call the called party, the first calling party can send a call request to the network device through the first terminal device.

The network device receives the call request sent by the first terminal device, and performs subsequent operations according to the content contained in the call request.

The content included in the call request can be set according to the actual situation. In some possible implementations, the call request may include the verification token and the first phone number of the first calling party. In other possible implementation manners, in addition to the verification token and the first phone number of the first calling party, the call request may also include one or more of information such as dialing location and dialing time.

The generation method of the verification token can be set according to the actual situation. In some possible implementations, when the called party leaves the contact information for the second calling party, the second calling party can be asked to show the third phone number.

After obtaining the third phone number of the second calling party, the called party sends the first creation request to the network device through the second terminal device. The first creation request includes the second phone number of the called party and the third phone number of the second calling party.

When the network device receives the first creation request, it can create a verification token based on the second phone number and the third phone number, and store the correlation between the verification token and the second phone number and the third phone number.

It is understandable that in the above-mentioned method of generating the verification token, the second calling party is required to show the third phone number. However, in some situations, the second caller is also worried that his third phone number will be unintentionally or deliberately leaked by others, leading to a large number of harassing calls.

Therefore, in other possible implementation manners, the second calling party may not directly show its phone number. The second calling party can send an identity request to the network device through the third terminal device. If the second calling party has previously stored the third phone number in the network device, the network device may generate the first identity according to the identity request, and associate the first identity with the third phone number.

If the second calling party does not store the first phone number in the network device in advance, the identity request should include the third phone number of the second calling party. The network device generates the first identity identifier according to the identity identifier request, stores the third telephone number and the first identity identifier, and associates the third telephone number with the first identity identifier.

After the network device generates the first identity, the first identity can be returned to the third terminal device. The form of the first identity can be determined according to actual conditions. For example, the first identity identifier may be one or more of two-dimensional code, barcode, number, character, and the like.

When the second calling party needs to show the contact information to the called party, it can show the first identity to the called party. After obtaining the first identity, the called party sends a first creation request to the network device through the second terminal device. The first creation request includes the second phone number of the called party and the first identity of the second calling party.

It is understandable that, in order to prevent the first identity from being leaked unintentionally or maliciously by others, corresponding leakage prevention measures can be set for the first identity. For example, the effective number of times of the first identity can be set, assuming that the number of effective times is set to 1, then the first identity will become invalid after it is used once; or, the effective time of the first identity can also be set, assuming that it is valid If the time is 5 minutes, the second calling party or called party must use the first identity within 5 minutes, otherwise the first identity becomes invalid.

After receiving the first creation request, the network device verifies the legitimacy and validity of the first identity. If the first identity is verified, the third phone number corresponding to the first identity is queried, a verification token is created based on the third phone number and the second phone number, and the verification token and the third phone number are stored And the association relationship of the second phone number.

The method of creating a verification token based on the third phone number and the second phone number can be set according to actual conditions. In some embodiments, random numbers can be used as verification tokens. For example, when the network device receives the first creation request, it generates a random number, uses the random number as a verification token, and records the association relationship between the random number and the third phone number and the second phone number. In other embodiments, the hash value can also be used as the verification token. For example, when the network device receives the first creation request, it hashes the time when the first creation request is received to obtain a hash value, uses the hash value as a verification token, and records the hash value and The association relationship between the third phone number and the second phone number. Alternatively, in some other embodiments, other methods may be selected to generate the verification token, which will not be repeated here.

After the network device generates the verification token, it can send the verification token to the designated recipient. The sending form of the verification token and the designated receiver can be set according to the actual situation. For example, the third terminal device can be used as the designated receiver, and the network device can send the verification token to the third terminal device in the form of Uniform Resource Locator (URL) via SMS, and the URL contains the verification token. Token; or, the second terminal device can also be used as the designated recipient, the network device sends the verification token to the second terminal device in the form of a URL through a short message, and the called party then verifies the verification token through the second terminal device The token is presented to the third terminal device.

S102: The network device verifies the first phone number according to the verification token.

After the network device obtains the call request, it can verify the verification token according to the first phone number.

The network device may first verify the validity of the verification token, and determine whether the verification token is legitimate according to whether the format information of the verification token is compliant, whether the verification token is stored in a database, and so on.

If the verification token is valid, the first phone number can be verified according to the verification token. The network device can obtain the third phone number associated with the verification token. If the first phone number is consistent with the third phone number, it means that the first phone number has passed the verification. If the first phone number is inconsistent with the third phone number, it means that the first phone number verification failed.

In addition to using the third phone number to verify the first phone number, other information can also be used for verification.

In some possible implementations, the called party can set the callable time period of the verification token. The network device can obtain the dialing time and verify the dialing time according to the callable time period. If the dialing time is within the callable time period, it means that the first phone number has passed the verification. If the dialing time is not within the callable time, the first phone number indicates that the verification has failed.

The network device can obtain the dialing time through the call request. At this time, the dialing time indicates the time when the first user triggers the call request. Alternatively, the network device may also use the time when the call request is received as the dialing time.

For example, if the called party does not want to receive a call between 23:00 at night and 7 am, the time between 7 am and 23:00 at night can be set as the callable time period.

If the dialing time is 10:23 when the first calling party triggers the call request, and 10:23 is within the time interval from 7 to 23:00, the first phone number will pass the verification in terms of dialing time.

If the dialing time is 23:12 when the first calling party triggers the call request, and 23:12 is not within the time interval from 7 to 23:00, the first phone number verification fails.

In other possible implementation manners, the called party can set the callable area of the verification token, and the network device can obtain the dialing location through the call request, and verify the dialing location according to the callable area. If the dialing location is within the callable area, it means that the first phone number has passed the verification. If the dialing location is not in the callable area, it means that the first phone number verification failed.

For example, if the customers of the called party are in Guangzhou, Shenzhen, and Nanjing, the called party can set Guangzhou, Shenzhen, and Nanjing as callable areas.

When the first calling party sends a call request to the network device, the call request includes the location information of the first terminal device, and the location information is the dialing location. If the dialing location is Nanshan District, Shenzhen, which is within the callable area, it means that the first phone number has passed the verification of the dialing location.

If the dialing location of the first calling party is Shijiazhuang, Hebei, and Shijiazhuang, Hebei is not in the callable area, the first phone number verification fails.

In other possible implementations, the called party can set the valid times of the verification token. When the network device receives the call request, it detects whether the verification token is invalid. If the verification token is not invalid, the first phone number has passed the verification in terms of the token status, and the number of calls is increased by 1. When the number of calls is greater than or equal to the valid number, the verification token is invalid. If the verification token is invalid, it means that the verification of the first phone number has failed.

For example, the second calling party is a real estate salesperson, and when the called party leaves contact information, considering that the number of contacts between the two parties may not exceed 10 times, in order to avoid continuous harassment by the real estate salesperson, the first creation request or follow-up The number of times setting instruction sets the valid times of the verification token to 10 times.

When the first calling party sends a call request to the network device, assuming that the network device detects that the number of calls of the verification token is 9, and the verification token has not expired, the first phone number passes the verification in terms of the token status. The number of calls increases by 1.

After this call, the number of calls of the verification token is 10, and the number of calls is equal to the number of valid times, and the network device modifies the token status of the verification token to an invalid state.

When the first calling party sends a call request to the network device next time, and the network device detects that the status of the verification token is an invalid state, the verification of the first phone number fails.

In other possible implementations, the called party can set the valid time of the verification token. When the network device receives the call request, it detects whether the verification token is invalid. If the verification token is not invalid, the first phone number is verified in terms of the status of the token. If the valid time has passed, the verification token becomes invalid, indicating that the verification of the first phone number has failed.

For example, if the second caller is a food delivery person, when the called party leaves the contact information, considering that both parties may need to contact within two hours, in order to avoid continuous harassment by the food delivery person, the first creation request or follow-up The time setting instruction sets the valid time of the verification token to 2 hours.

Assume that the called party sets the valid time of the verification token to 2 hours at 11:23. When the first calling party sends a call request to the network device at 12:45, the network device detects that the current verification token is in a valid state, and the first phone number passes the verification in terms of the token status.

At 13:23, the network device detects that the valid time of the verification token is over, and then modifies the token status of the verification token to an invalid state.

When the first calling party sends a call request to the network device at 13:34, and the network device detects that the current verification token is in an invalid state, the verification of the first phone number fails.

In other possible implementation manners, the called party may also actively send a state modification instruction to the network device, so that the network device changes the token state of the verification token to an invalid state. Therefore, when the network device receives the call request, it detects whether the verification token is invalid. If the verification token is not invalid, the first phone number is verified in terms of the status of the token. If the verification token is invalid, the first phone number verification fails.

For example, if the called party does not want to continue to be called by the second calling party, it can actively send a state modification instruction to the network device through the second terminal device, and the network device sets the token state of the designated check token to the network device according to the state modification instruction Invalid state.

When the first calling party subsequently sends a call request to the network device, and the network device detects that the verification token is in an invalid state, the verification of the first phone number fails.

S103. If the first phone number is verified, the network device obtains a second phone number associated with the verification token, and establishes a call connection between the first phone number and the second phone number .

If the first phone number is verified, it means that the first calling party and the second calling party are the same user, and the call request is not a nuisance call. At this time, the network device can obtain the second phone number associated with the verification token, and establish a call connection between the first phone number and the second phone number.

The call connection establishment method can be set according to the actual situation. In some possible implementations, the network device can directly establish a call link between the first phone number and the second phone number through the operator’s network, and perform an anonymous operation on the first phone number and the second phone number, and transfer the first phone number to the second phone number. The number and the second phone number are converted into intermediate numbers generated according to preset rules, thereby disguising the real numbers of the first phone number and the second phone number, and protecting the privacy of the first phone number and the second phone number.

In another possible implementation, the network device may send the first phone number and the second phone number to the conference call server to instruct the conference call server to pull the first phone number and the second phone number into the same conference call , The first calling party and called party can talk.

When the call connection between the first phone number and the second phone number is established in the form of a conference call, there is no need to use the operator's roaming service, even if the operator network of the first calling party and the operator network of the called party are different, The above solution can also be implemented smoothly, which expands the application scenarios of the number privacy protection method of this embodiment, and improves user experience. Moreover, when a call connection in the form of a conference call is used, the numbers displayed on the first terminal device and the second terminal device are the conference number of the conference call, not the real number of the first phone number or the real number of the second phone number, Thereby protecting the privacy of the first phone number and the second phone number.

In addition, when the first calling party calls the called party, it is possible that the phone number is forged, that is, the first phone number of the first calling party is not the third phone number, but the first phone number is changed through the number virtualization software. A phone number is virtualized as a third phone number, so as to pass the token verification program of the network device.

At this time, if a call connection between the first telephone number and the second telephone number is established in the form of a telephone conference, the telephone conference server calls the third telephone number and the second telephone number instead of the original number and the first telephone number. The second phone number.

For example, suppose that the original number of the first phone number is 138XXXXX101, and the third phone number is 188XXXXX404. At this time, in order to call the called party, the first calling party can virtualize the original number 138XXXXX101 of the first phone number into 188XXXXX404 through the number virtualization software. However, even if the first calling party passes the token verification procedure of the network device by forging the number, the number called by the teleconference server is 188XXXXX404 and the second phone number instead of 138XXXXX101 and the second phone number. In other words, even if the first calling party passes the token verification procedure of the network device by forging the number, it cannot enter the conference call and cannot harass the called party.

If the verification of the first phone number fails, it means that the first caller and the second caller are not the same user, the verification token may have been leaked to an unrelated person, and the call request of the first caller may be Harassing phone calls. At this time, the network device refuses to create a call channel for the first phone number and the second phone number.

In addition, when the called party finds that the verification token has been leaked to an unrelated person and changes the token status of the verification token to an invalid state, if the called party saves the third phone number of the second calling party, Or the called party saves the first identity of the second calling party and the first identity is in a valid state, the called party can send a second creation instruction to the network device, and the second creation instruction includes the second phone number, And the third phone number or the first identity.

After receiving the second creation instruction, the network device can obtain the second phone number and the third phone number, generate a new verification token based on the second phone number and the third phone number, and send the new verification token to The designated recipient.

When the second terminal device and/or the third terminal device loses the verification token, the token retrieval instruction can also be sent to the network device. When the network device receives the token retrieval instruction, it sends the verification token associated with the second phone number to the second terminal device, and/or sends the verification token associated with the third phone number to the third terminal equipment.

The following describes the number privacy protection method provided in this embodiment in combination with specific application scenarios:

As shown in Figure 2, terminal device 1 is the terminal device of user 1, and terminal device 2 is the terminal device of user 2. User 1 is a real estate salesperson, and user 2 wants to entrust the real estate to user 1 for rent. The terminal device 1 and the terminal device 2 are installed with privacy protection software, and the registration process of the privacy protection software and the binding phone number have been completed.

At this time, user 2 needs to leave the contact information as user 1. User 2 consults User 1’s contact information, and User 1 informs User 2 of his phone number 1.

User 2 records user 1's phone number 1 into the mobile phone address book of terminal device 1, and sends the first creation request to the network device through the privacy protection software of terminal device 1. The first creation request contains the phone number 1 of user 1 and the phone number 2 of user 2.

The network device generates a verification token 1 according to the telephone number 1 and the telephone number 2, and stores the association relationship between the telephone number 1, the telephone number 2 and the verification token 1. After that, the network device sends the verification token 1 to the short message server to instruct the short message server to send the URL link of the H5 web page carrying the verification token 1 to the terminal device 1 in the form of a short message.

As shown in Figure 3, when user 1 finds a suitable tenant and wants to contact user 2, user 1 can click the URL link in the short message of terminal device 1 to trigger dial instruction 1 and send it to the network device.

After receiving the dialing instruction 1, the network device generates a dialing web page and returns it to the terminal device 1.

User 1 views the dialing web page displayed on the terminal device and clicks the dial button to trigger call request 1. The terminal device 1 sends the call request 1 to the network device. The call request 1 contains the phone number 1, the verification token 1, and the terminal device 1. Current location information (ie dialing location).

After the network device receives the call request 1, it detects that the verification token 1 is a valid verification token, and the token status 1 of the verification token 1 is valid (indicating that the number of uses of the verification token 1 has not exceeded the valid The number of times and/or the current time has not exceeded the valid time of verification token 1), the dialing time of the network device receiving call request 1 is within the callable time period and the dialing location in call request 1 is within the callable area, then the network The device obtains the phone number 1 associated with the verification token 1.

The network device verifies that the phone number 1 in the call request 1 is the same as the phone number 1 associated with the verification token 1, and the phone number 1 passes the verification, and the phone number 1 and the phone associated with the verification token 1 The number 2 is sent to the teleconference server to instruct the teleconference server to call the terminal device 1 according to the telephone number 1 and the terminal device 2 according to the telephone number 2, and pull the terminal device 1 and the terminal device 2 into the same conference call, so that the user 1 and User 2 can communicate by phone.

As shown in Figure 4, if the user 1 or the user 2 accidentally leaks the verification token 1 to the user 3, the user 3 wants to promote the product to the user 2.

At this time, the user 3 clicks the URL link in the short message related to the verification token 1 through the terminal device 3 to trigger the dialing instruction 2 and send it to the network device.

After receiving the dialing instruction 2, the network device generates a dialing web page and returns it to the terminal device 3.

User 3 views the dialing web page displayed on the terminal device, clicks the dial button, and triggers a call request 2. The terminal device 3 sends the call request 2 to the network device. The call request 2 contains the phone number 3, the verification token 1, and the terminal device 3. Current location information (ie dialing location).

After the network device receives the call request 2, it detects that the verification token 1 is a valid verification token, and the token status 1 of the verification token 1 is a valid state (indicating that the number of uses of the verification token 1 has not exceeded the valid The number of times and/or the current time has not exceeded the valid time of the verification token 1), the dialing time of the network device receiving the call request 2 is within the callable time period and the dialing location in the call request 2 is within the callable area, then the network The device obtains the phone number 1 associated with the verification token 1.

The network device verification found that the phone number 3 in the call request 2 is inconsistent with the phone number 1 associated with the verification token 1, indicating that the phone number 3 does not have the right to call the phone associated with the verification token 2 through the verification token 1 Number 2.

At this time, the network device returns the call failure information to the terminal device 3, notifies the user 3 of the call result, and ends the response to the call request 2.

As shown in Figure 5, when user 1 accidentally deletes the short message related to verification token 1 when clearing the short message, user 1 can send a retrieval instruction to the network device through the privacy protection software in the terminal device 1, and retrieve it The command contains the phone number 1 of user 1.

After receiving the retrieval instruction, the network device queries the verification token associated with the phone number 1. After inquiring, the network device inquires that the verification token 1 is associated with the phone number 1, and then sends the verification token 1 to the SMS server to instruct the SMS server to link the URL of the H5 webpage carrying the verification token 1 to the SMS The method is sent to the terminal device 1.

As shown in Figure 6, if user 2 finds that verification token 1 has been leaked, user 2 can send a second creation request to the network device through the privacy protection software of terminal device 2. The second creation request contains user 1’s phone number. Number 1 and User 2’s phone number 2.

The network device generates the verification token 2 according to the phone number 1 and the phone number 2, stores the association relationship between the phone number 1, the phone number 2 and the verification token 2, and modifies the token status of the verification token 1 to the invalid state . After that, the network device sends the verification token 2 to the short message server to instruct the short message server to send the URL link of the H5 webpage carrying the verification token 2 to the terminal device 1 in the form of a short message.

As shown in Fig. 7, after user 1 completes user 2’s house rental entrustment, in order to prevent user 1 from harassing user 2 subsequently, user 2 can send a state modification instruction to the network device by the privacy protection software of terminal device 2.

After receiving the state modification instruction, the network device modifies the token state of the verification token 2 to an invalid state according to the state modification instruction.

Later, when the user 1 wants to contact the user 2, he can click the URL link related to the verification token 2 in the short message of the terminal device 1 to trigger the dialing instruction 3 and send it to the network device.

After receiving the dialing instruction 3, the network device generates a dialing web page and returns it to the terminal device 1.

User 1 views the dialing web page displayed on the terminal device and clicks the dial button to trigger a call request 3. The terminal device 1 sends the call request 3 to the network device. The call request 3 contains the phone number 1, the verification token 2 and the terminal device 1. Current location information (ie dialing location).

After the network device receives the call request 1, it detects that the token status of the verification token 1 is invalid, which means that the user 1 does not have the authority to contact the user 2 through the verification token 2, and the verification of the phone number 1 fails, and the network device returns The call failure information is sent to the terminal device 1, informing the user 1 of the call result, and ending the response to the call request 3.

In the number privacy protection method of this embodiment, the first calling party does not directly make a call through the called party's second phone number, but makes a call through a verification token. When the called party shows the contact information, it is not necessary to show the second phone number directly, but just show the verification token, so as to realize the anonymization of the called party's phone number and prevent the called party's second phone number from being unintentionally leaked or Malicious disclosure.

The verification token is generated based on the second phone number of the called party and the third phone number of the second calling party. When the first calling party calls the called party through the verification token, the network device will verify the first phone number of the first calling party according to the verification token, and identify whether the first phone number is the same as the third phone number. The numbers are the same. When the first phone number is consistent with the third phone number, it means that the first calling party and the second calling party are the same users, and the first calling party has the right to call the second phone number. When the first phone number is not consistent with the third phone number, it means that the first calling party and the second calling party are different users, and the first calling party has no right to call the second phone number, and the call fails. Therefore, even if the verification token is leaked, users other than the second calling party cannot call the called party through the verification token, which prevents the called party from frequently receiving harassing calls due to the leak of the verification token.

In addition, the called party can manage the authority of the verification token, for example, whether to set the callable time period, whether to set the callable area, whether to set the effective number of times, whether to set the effective time, and whether to verify the token of the token The status is changed to a failed status, etc. In addition, when the verification token is leaked, the called party can also actively request the network device to generate a new verification token and revoke the original verification token. Through the above-mentioned authority management measures, it is possible to further prevent the called party from receiving harassing calls from others.

At the same time, the second calling party can also manage the verification token to a certain extent. For example, when the second calling party discovers that the verification token is leaked, it can also actively send a status modification instruction to the network device to instruct the network device to modify the token status of the verification token to an invalid state; When the calling party loses the verification token, it can also request the network device to retrieve the lost verification token. Through the above rights management measures, it is possible to further prevent the called party from receiving harassing calls from others, and to prevent the second calling party from being unable to contact the called party after losing the verification token.

It should be understood that the size of the sequence number of each step in the foregoing embodiment does not mean the order of execution, and the execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiment of the present application.

Please refer to FIG. 8, an embodiment of the present application provides a network device. For ease of description, only the parts related to the present application are shown. As shown in FIG. 8, the network device includes:

The call request module 801 is configured to obtain a call request sent by a first terminal device, where the call request includes a verification token and the first phone number of the first calling party;

The number verification module 802 is configured to verify the first phone number according to the verification token;

The call connection module 803 is configured to obtain a second phone number associated with the verification token if the first phone number is verified, and establish a call between the first phone number and the second phone number connection.

Further, the network equipment further includes:

Further, the token sending module is specifically configured to send the verification token to the second terminal device, or send the verification token to the third terminal device.

Further, the call connection module 803 is specifically configured to, if the first phone number is consistent with the third phone number, obtain a second phone number associated with the verification token, and establish the first phone number. The phone number is connected to the call of the second phone number.

Further, the call connection module 803 includes:

The teleconference sub-module is used to obtain the second telephone number associated with the verification token, and send the first telephone number and the second telephone number to the teleconference server to instruct the teleconference server to The first phone number and the second phone number are pulled into the same conference call.

It should be noted that the information interaction and execution process between the above-mentioned devices/units are based on the same concept as the method embodiment of this application, and its specific functions and technical effects can be found in the method embodiment section. I won't repeat it here.

Referring to FIG. 9, an embodiment of the present application also provides a network device. The network device 9 includes: a processor 90, a memory 91, and a computer program stored in the memory 91 and running on the processor 90 92. When the processor 90 executes the computer program 92, the steps in the above embodiment of the number privacy protection method are implemented, such as steps S101 to S103 shown in FIG. 1. Alternatively, when the processor 90 executes the computer program 92, the functions of the modules/units in the foregoing device embodiments, for example, the functions of the modules 801 to 803 shown in FIG. 8 are realized.

Exemplarily, the computer program 92 may be divided into one or more modules/units, and the one or more modules/units are stored in the memory 91 and executed by the processor 90 to complete This application. The one or more modules/units may be a series of computer program instruction segments capable of completing specific functions, and the instruction segments are used to describe the execution process of the computer program 92 in the network device 9. For example, the computer program 92 can be divided into a call request module, a number verification module, and a call connection module. The specific functions of each module are as follows:

The network device 9 may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server. The network device may include, but is not limited to, a processor 90 and a memory 91. Those skilled in the art can understand that FIG. 9 is only an example of the network device 9 and does not constitute a limitation on the network device 9. It may include more or less components than those shown in the figure, or a combination of certain components, or different components. For example, the network device may also include input and output devices, network access devices, buses, and so on.

The so-called processor 90 may be a central processing unit (Central Processing Unit, CPU), other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.

The memory 91 may be an internal storage unit of the network device 9, for example, a hard disk or a memory of the network device 9. The memory 91 may also be an external storage device of the network device 9, for example, a plug-in hard disk equipped on the network device 9, a smart memory card (Smart Media Card, SMC), or a Secure Digital (SD). Card, Flash Card, etc. Further, the memory 91 may also include both an internal storage unit of the network device 9 and an external storage device. The memory 91 is used to store the computer program and other programs and data required by the network device. The memory 91 can also be used to temporarily store data that has been output or will be output.

Those skilled in the art can clearly understand that for the convenience and conciseness of description, only the division of the above functional units and modules is used as an example. In practical applications, the above functions can be allocated to different functional units and modules as required. Module completion, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist alone physically, or two or more units can be integrated into one unit. The above-mentioned integrated units can be hardware-based Formal realization can also be realized in the form of a software functional unit. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the present application. For the specific working process of the units and modules in the foregoing system, reference may be made to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the above-mentioned embodiments, the description of each embodiment has its own focus. For parts that are not described in detail or recorded in an embodiment, reference may be made to related descriptions of other embodiments.

A person of ordinary skill in the art may realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

In the embodiments provided in this application, it should be understood that the disclosed apparatus/network equipment and method may be implemented in other ways. For example, the device/network device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units. Or components can be combined or integrated into another system, or some features can be omitted or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.

If the integrated module/unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiments and methods, and can also be completed by instructing relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the program is executed by the processor, it can implement the steps of the foregoing method embodiments. Wherein, the computer program includes computer program code, and the computer program code may be in the form of source code, object code, executable file, or some intermediate forms. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory) , Random Access Memory (RAM, Random Access Memory), electrical carrier signal, telecommunications signal, and software distribution media, etc. It should be noted that the content contained in the computer-readable medium can be appropriately added or deleted according to the requirements of the legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to the legislation and patent practice, the computer-readable medium Does not include electrical carrier signals and telecommunication signals.

The above-mentioned embodiments are only used to illustrate the technical solutions of the present application, not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still implement the foregoing The technical solutions recorded in the examples are modified, or some of the technical features are equivalently replaced; and these modifications or replacements 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 the application, and should be included in Within the scope of protection of this application.

Claims

A method for protecting number privacy, which is characterized in that it includes:

The network device obtains a call request sent by the first terminal device, where the call request includes a verification token and the first phone number of the first calling party;

The network device verifies the first phone number according to the verification token;

If the first phone number is verified, the network device obtains the second phone number associated with the verification token, and establishes a call connection between the first phone number and the second phone number.
The number privacy protection method according to claim 1, wherein before the network device obtains the call request sent by the first terminal device, the method further comprises:

Acquiring, by the network device, a first creation request sent by a second terminal device, where the first creation request includes the second phone number and the third phone number of the second calling party;

The network device creates the verification token according to the second phone number and the third phone number;

The network device sends the verification token to the designated recipient.
The number privacy protection method according to claim 1, wherein before the network device obtains the call request sent by the first terminal device, the method further comprises:

Acquiring, by the network device, an identity request sent by a third terminal device, where the identity request includes the third telephone number of the second calling party;

The network device creates a first identity corresponding to the third telephone number, and returns the first identity to the third terminal device;

Acquiring, by the network device, a first creation request sent by a second terminal device, where the first creation request includes the second phone number and the first identity;

The network device queries a third phone number corresponding to the first identity identifier, and creates the verification token according to the second phone number and the third phone number;

The network device sends the verification token to the designated recipient.
The number privacy protection method according to claim 2 or 3, wherein the network device sending the verification token to a designated recipient comprises:

The network device sends the verification token to the second terminal device, or sends the verification token to the third terminal device.
The number privacy protection method according to claim 2 or 3, wherein if the first phone number is verified, the network device obtains the second phone number associated with the verification token Establishing a call connection between the first telephone number and the second telephone number includes:

If the first phone number is consistent with the third phone number, the network device obtains the second phone number associated with the verification token, and establishes the first phone number and the second phone number Call connection.
The number privacy protection method of claim 1, wherein the network device obtains a second phone number associated with the verification token, and establishes a connection between the first phone number and the second phone number Call connection includes:

The network device obtains the second phone number associated with the verification token, and sends the first phone number and the second phone number to the teleconference server to instruct the teleconference server to transfer the first A phone number and the second phone number are pulled into the same conference call.
A network device, characterized in that it comprises:

A call request module, configured to obtain a call request sent by a first terminal device, the call request including a verification token and the first phone number of the first calling party;

A number verification module, configured to verify the first phone number according to the verification token;

A call connection module, configured to obtain a second phone number associated with the verification token if the first phone number is verified, and establish a call connection between the first phone number and the second phone number .
8. The network device of claim 7, wherein the network device further comprises:

A creation request module, configured to obtain a first creation request sent by a second terminal device, where the first creation request includes the second phone number and the third phone number of the second calling party;

A token creation module, configured to create the verification token according to the second phone number and the third phone number;

The token sending module is used to send the verification token to the designated receiver.
8. The network device of claim 7, wherein the network device further comprises:

An identity request module, configured to obtain an identity request sent by a third terminal device, where the identity request includes the third phone number of the second calling party;

An identity module, configured to create a first identity corresponding to the third phone number, and return the first identity to the third terminal device;

A creation request module, configured to obtain a first creation request sent by a second terminal device, the first creation request including the second phone number and the first identity;

A token creation module, configured to query a third phone number corresponding to the first identity identifier, and create the verification token according to the second phone number and the third phone number;

The token sending module is used to send the verification token to the designated receiver.
The network device according to claim 8 or 9, wherein the token sending module is specifically configured to send the verification token to the second terminal device, or send the verification command The card is sent to the third terminal device.
The network device according to claim 8 or 9, wherein the call connection module is specifically configured to obtain the verification token if the first phone number is consistent with the third phone number The associated second phone number establishes a call connection between the first phone number and the second phone number.
8. The network device according to claim 7, wherein the call connection module comprises:

The teleconference sub-module is used to obtain the second telephone number associated with the verification token, and send the first telephone number and the second telephone number to the teleconference server to instruct the teleconference server to The first phone number and the second phone number are pulled into the same conference call.
A network device, comprising a memory, a processor, and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the computer program as claimed in claims 1 to 6. Steps of any one of the methods.
A computer-readable storage medium storing a computer program, wherein the computer program implements the steps of the method according to any one of claims 1 to 6 when the computer program is executed by a processor.