WO2022143070A1

WO2022143070A1 - Communication method and communication system

Info

Publication number: WO2022143070A1
Application number: PCT/CN2021/136688
Authority: WO
Inventors: 谭郑斌; 孔德卫; 张劲锐
Original assignee: 华为技术有限公司
Priority date: 2020-12-31
Filing date: 2021-12-09
Publication date: 2022-07-07
Also published as: CN114698101A

Abstract

Embodiments of the present application relate to the field of communication and disclose a communication method and a communication system, which solve the problem of excessive power consumption due to a terminal device currently needing to frequently establish an RRC connection with a network device. Specifically, a solution is: receiving a first request message from a first network device, the first request message being used for indicating to send a voice call to a terminal device; and sending a voice call to the terminal device, the voice call being used to indicate that the terminal device has a push message.

Description

A communication method and communication system

This application claims the priority of the Chinese patent application with the application number 202011640420.8 and the application title "a communication method and communication system" filed with the State Intellectual Property Office on December 31, 2020, the entire contents of which are incorporated herein by reference middle.

technical field

The embodiments of the present application relate to the field of communication, and in particular, to a communication method and a communication system.

Background technique

During the communication process between the terminal device and the network device, the data to be transmitted may be transmitted through the communication link between the terminal device and the network device.

In some scenarios, in order to realize data transmission quickly and accurately, it is necessary to maintain the validity of the communication link between the terminal device and the network device. For example, the terminal device may send heartbeat packets to the network device (such as the server) at certain time intervals, so that the server can determine that the terminal device is online (or called alive) according to the received heartbeat packets. Thus, the server is made aware that the communication link with the terminal device is in a valid state. In this way, when the server needs to transmit data to the terminal device, the data can be transmitted through the effective communication link.

It can be understood that, the sending of the heartbeat packet can be implemented based on the connection between the terminal device and the network device. For example, the connection may be a radio resource control (Radio Resource Control, RRC) connection. In order to allow the resources corresponding to the connection to be scheduled more flexibly, the network device will release the resources of the RRC connection within a short period of time (eg, 20 seconds) after the RRC connection is established. In this way, each time the terminal device sends a heartbeat packet to the network device, it needs to re-establish an RRC connection with the network device. The frequent establishment of RRC connections will significantly increase the power consumption of the terminal device. In the case where the network is not configured with Connected Discontinuous Reception (CDRX), it will lead to greater waste of power consumption.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a communication method and a communication system, which solve the problem of excessive power consumption caused by the need for frequent establishment of an RRC connection with a network device by a terminal device at present.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:

In a first aspect, a communication method is provided. The method includes: receiving a first request message from a first network device, where the first request message is used to instruct to initiate a voice call to a terminal device. A voice call is initiated to the terminal device, and the voice call is used to indicate that the terminal device has a push message.

Based on this solution, a solution is provided in which a terminal device can know that a push message needs to be received without frequently establishing an RRC connection. In this example, the communication method can be applied to a voice push gateway. The voice push gateway can receive a request from the first network device (such as a service server and a push server), and accordingly, the voice push server can initiate a voice call to the corresponding terminal device, so that the terminal device receives the specific voice call. Next, know that there are push messages that need to be received, and then perform subsequent operations. It can be seen that, through this solution, the terminal device does not need to frequently send heartbeat packets to the network device to inform the network device that the current terminal device is still in a live state. Plus, there's no need to go through text messaging services that introduce additional fees. Therefore, the power consumption overhead introduced by the frequent establishment of RRC connections caused by the frequent sending of heartbeat packets can be saved, and additional communication costs are not required at the same time.

In a possible design, the first request message includes an identifier corresponding to the terminal device, and initiating a voice call to the terminal device includes: initiating a voice call to the terminal device according to the identifier corresponding to the terminal device. Based on the solution, a mechanism for the voice push gateway to determine the corresponding terminal device is provided. In this example, when the voice push gateway receives the first request message, it can also determine to which terminal device the voice call needs to be initiated through the identifier of the terminal device included in the message. It can be understood that different terminal devices may have different identifiers. Therefore, the voice push gateway can accurately determine the terminal device that needs to initiate a voice call according to the identification of the terminal device.

In a possible design, the identifier corresponding to the terminal device is the phone number of the terminal device. Based on this solution, an example of a specific identifier corresponding to a terminal device is provided. For example, the identifier of the terminal device may be the phone number of the corresponding terminal device. It should be noted that, in other implementation manners of the present application, the identifier of the terminal device may also be other identifiers that can uniquely identify the terminal device, such as the UE ID of the terminal device.

In a possible design, initiating a voice call to the terminal device according to the identifier corresponding to the terminal device includes: determining the phone number of the terminal device according to the identifier corresponding to the terminal device, and making a voice call to the phone number. Based on this solution, a specific example of a mechanism for initiating a voice call to a terminal device is provided. In this example, taking the identification of the terminal device as a phone number as an example, the voice push gateway can directly initiate a call to the phone number. It should be noted that, in other implementations, when the identifier of the terminal device is the UE ID, the voice push gateway can determine the phone number corresponding to the UE ID according to the preset correspondence between the UE ID and the corresponding phone number number and make a call.

In a possible design, the method further includes: acquiring a push number segment. Send a first configuration message to the second network device, where the first configuration message includes the push number segment, so that the second network device sends the push number segment to the terminal device. Or, send a second configuration message to the first network device, where the second configuration message includes the push number segment, so that the first network device sends the push number segment to the terminal device. Based on this solution, a mechanism for obtaining a push number for initiating a voice call to a terminal device is provided. It can be understood that, since the voice call involved in this example is not an ordinary call, a specific push number needs to be configured for it, so that the terminal device can determine the purpose of the voice call (such as prompting a new push message). In this example, the voice push gateway may acquire a push number segment including multiple push numbers, and send the push number segment to a second network device (such as a service server) through the first configuration message, so that the service server can directly The push number segment is sent to the terminal device, or the push number segment is sent to the terminal device through the push server.

In a possible design, the outgoing number for initiating a voice call to the terminal device is included in the push number field. Based on this solution, it is clarified that the outgoing number corresponding to the voice call initiated to the terminal device is in the push number segment, so that the terminal device can compare the corresponding incoming number of the received voice call with the push number segment to determine the voice call. The role of the incoming call, and perform the corresponding operation.

In a second aspect, a communication apparatus is provided, the apparatus includes: a receiving unit, configured to receive a first request message from a first network device, where the first request message is used to instruct to initiate a voice call to a terminal device. The calling unit is used to initiate a voice call to the terminal device, and the voice call is used to indicate that the terminal device has a push message.

In a possible design, the calling unit is specifically configured to initiate a voice call to the terminal device according to the identifier corresponding to the terminal device.

In a possible design, the identifier corresponding to the terminal device is the phone number of the terminal device.

In a possible design, the calling unit is configured to determine the phone number of the terminal device according to the identifier corresponding to the terminal device, and make a voice call to the phone number.

In a possible design, the apparatus further includes: an acquiring unit, configured to acquire the push number segment. The sending unit is configured to send a first configuration message to the second network device, where the first configuration message includes a push number segment, so that the second network device can send the push number segment to the terminal device. Or, a sending unit, configured to send a second configuration message to the first network device, where the second configuration message includes a push number segment, so that the first network device sends the push number segment to the terminal device.

In a possible design, the outgoing number for initiating a voice call to the terminal device is included in the push number field.

In a third aspect, a network device is provided, the network device including one or more processors and one or more memories. One or more memories are coupled to the one or more processors, and the one or more memories store computer instructions. The computer instructions, when executed by one or more processors, cause a network device to perform a communication method as described in any one of the first aspect and possible designs thereof.

In a fourth aspect, a chip system is provided, the chip includes a processing circuit and an interface. The processing circuit is used to call and run the computer program stored in the storage medium from the storage medium, so as to execute the communication method according to any one of the first aspect and its possible designs.

In a fifth aspect, a computer-readable storage medium is provided, the computer-readable storage medium includes computer instructions, and when the computer instructions are executed, executes the communication method according to any one of the first aspect and possible designs thereof.

A sixth aspect provides a computer program product, the computer program product includes instructions, when the computer program product is run on a computer, the computer can execute according to the instructions as described in any one of the first aspect and its possible designs communication method.

It should be understood that, the solutions provided by the second aspect to the sixth aspect can all correspond to the first aspect or its possible designs, and thus the beneficial effects that can be obtained are similar, which will not be repeated here.

In a seventh aspect, a communication method is provided, the method comprising: receiving a voice call; determining an incoming call number of the voice call; when the incoming call number is a pushed push number, sending a connection request to a first network device corresponding to the push number, the connection request for establishing a communication connection with the first network device; and receiving a push message from the first network device through the communication connection.

Based on this solution, a solution is provided that does not need to send heartbeat packets frequently to maintain a long TCP connection, and at the same time can receive push messages quickly and accurately. For example, the solution can be applied to terminal equipment. In this example, the terminal device may determine that there is a new push message to be received by receiving a voice call from a voice push gateway and determining that the incoming number is a push number. Then, the terminal device may initiate a connection request to the first network device (eg, a service server, a push server), so as to receive a push message through a communication connection corresponding to the connection request. It can be understood that, with this solution, since heartbeat packets do not need to be sent frequently, RRC connections do not need to be established frequently, so the power consumption overhead caused by frequent establishment of RRC connections can be saved. In addition, since the solution does not require the introduction of other paid services (such as short message services), there is no additional cost.

In one possible design, when the incoming call number is included in the stored push number field, the incoming call number is a push number. Based on the solution, a mechanism for determining the number corresponding to the incoming voice call as the push number is provided. For example, a push number segment may be stored in the terminal device, and the push number segment may include multiple push numbers. When the incoming number falls into the push number segment, it can be determined that the incoming number is a push number, and then it is determined that the voice call is used to prompt the terminal device that there is a new push message that needs to be viewed.

In a possible design, determining the incoming number of the voice call includes: the non-access layer NAS parses the air interface message corresponding to the voice call, and determines the incoming number of the voice call. The method further includes: when the incoming call number is a push number, the NAS rejects the voice call. Based on this solution, a mechanism for specifically dealing with incoming voice calls corresponding to push numbers is provided. In this example, the determination of the incoming call number and the corresponding operation may be performed at the NAS layer in the terminal device. For example, the NAS layer can directly hang up at the bottom layer when determining that the incoming number is a push number, without uploading the information corresponding to the incoming voice call to the upper layer, so as to improve efficiency.

In a possible design, sending a connection request to the first network device corresponding to the push number includes: initiating a radio resource control RRC connection request to the first network device corresponding to the push number, so as to establish an RRC connection with the first network device . Receiving the push message from the first network device through the communication connection includes: receiving the push message from the first network device through the RRC connection. Based on this solution, a specific example of acquiring push messages is provided. For example, when it is determined that there is a new push message, the terminal device can initiate an RRC connection request to the first network device (such as the service server), so as to obtain the RRC resource configured for it by the service server, and obtain the push message on the RRC resource. information.

In a possible design, the method further includes: receiving a first configuration message, where the first configuration message includes a push number field. Store the push number segment. Based on this solution, a mechanism for acquiring a push number segment is provided. For example, the terminal device may receive a configuration message including a high push number segment, and store the push number segment to facilitate subsequent identification of whether a subsequent incoming number is a push number.

In an eighth aspect, a communication device is provided, the device comprising: a receiving unit configured to receive a voice call. The determining unit is used to determine the incoming call number of the voice call. The sending unit is configured to send a connection request to the first network device corresponding to the push number when the incoming call number is a pushed push number, where the connection request is used to establish a communication connection with the first network device. The receiving unit is further configured to receive the push message from the first network device through the communication connection.

In one possible design, when the incoming call number is included in the stored push number field, the incoming call number is a push number.

In a possible design, the determining unit corresponds to a non-access stratum NAS set in the communication device, and the determining unit is configured to parse the air interface message corresponding to the voice call, and determine the incoming call number of the voice call. The device further includes: a rejecting unit, used for rejecting the voice call by the NAS when the incoming call number is a push number.

In a possible design, the sending unit is configured to initiate a radio resource control RRC connection request to the first network device corresponding to the push number, so as to establish an RRC connection with the first network device. A receiving unit, configured to receive the push message from the first network device through the RRC connection.

In a possible design, the receiving unit is further configured to receive a first configuration message, where the first configuration message includes a push number field. The device further includes: a storage unit for storing the push number segment.

In a ninth aspect, a terminal device is provided, the terminal device includes one or more processors and one or more memories. One or more memories are coupled to the one or more processors, and the one or more memories store computer instructions. When one or more processors execute the computer instructions, the terminal device is caused to perform the communication method according to any one of the seventh aspect and possible designs thereof.

In a tenth aspect, a chip system is provided, the chip includes a processing circuit and an interface. The processing circuit is used to call and run the computer program stored in the storage medium from the storage medium, so as to execute the communication method according to any one of the seventh aspect and its possible designs.

In an eleventh aspect, a computer-readable storage medium is provided, the computer-readable storage medium includes computer instructions, and when the computer instructions are executed, the communication method as described in any one of the seventh aspect and its possible designs is executed. .

A twelfth aspect provides a computer program product, the computer program product includes instructions, when the computer program product is run on a computer, the computer can execute according to the instructions as described in any one of the seventh aspect and its possible designs communication method.

It should be understood that the solutions provided by the eighth aspect to the twelfth aspect can all correspond to the seventh aspect or a possible design thereof, and thus the beneficial effects that can be obtained are similar, which will not be repeated here.

A thirteenth aspect provides a communication method, the method comprising: receiving a first request message from a first network device, where the first request message is used to request to push a message to a terminal device. A second request message is sent, where the second request message is used to instruct the second network device to make a voice call to the terminal device.

Based on this solution, a mechanism for instructing a second network device (eg, a voice push gateway) to initiate a specific voice call is provided. Among them, the method can be applied to the push server. The specific voice call can be used to alert the terminal device of a new push message. For example, the push server can receive a service request from a first network device (such as a service server). In this scenario, the terminal device does not directly establish a connection with the push server. Therefore, the push server can notify the voice through the second request message. The push gateway uses the push number to initiate a voice call to the terminal device, so that the terminal device determines that there is a new push message according to the call received from the push number, and then initiates a communication connection to the service server to obtain the push message. It can be seen that in this solution, since the terminal device does not need to send heartbeat packets frequently, it does not need to establish RRC connections frequently, so the power consumption overhead caused by frequent establishment of RRC connections can be saved. In addition, since the solution does not require the introduction of other paid services (such as short message services), there is no additional cost.

In a possible design, the first request message includes the identifier of the terminal device. Before sending the second request message, the method further includes: determining the phone number of the terminal device according to the identifier of the terminal device, and sending the second request message, including: sending the phone number of the terminal device to the second network device through the second request message . Based on this solution, a mechanism for determining a terminal device that needs to receive a push message is provided. For example, the push server may determine the phone number corresponding to the terminal device according to the identifier of the terminal device carried in the first request message, and deliver the phone number to the voice push gateway, so that the voice push gateway can initiate a call to the terminal device voice call. Of course, in other implementations, the first request message can also directly include the phone number of the corresponding terminal device, that is, the identifier of the terminal device can be the phone number of the terminal device, then the push server can directly send the The phone number is delivered to the voice push gateway.

In a possible design, the first request message includes the identifier of the terminal device. Sending the second request message includes: sending the identifier of the terminal device to the second network device through the second request message. Based on this solution, another solution for determining a terminal device that needs to receive a push message is provided. For example, the push server can directly deliver the received identifier of the terminal device to the second network device (eg, a voice push gateway), so that the voice push gateway can determine the corresponding terminal device that needs to initiate a voice call according to the identifier.

In a possible design, the method further includes: receiving a first configuration message, where the first configuration message includes a push number field. Send a second configuration message to the terminal device, where the second configuration message includes a push number field. Based on this solution, a mechanism for pushing a push number segment to a terminal device is provided. For example, after acquiring the push number segment, the service server or the voice push gateway can push the push number segment to the terminal device through the push server, so that the terminal device can store the push number segment and determine whether the subsequent incoming number is not. is the push number.

A fourteenth aspect provides a communication apparatus, the apparatus comprising: a receiving unit configured to receive a first request message from a first network device, where the first request message is used to request to push a message to a terminal device. The sending unit is configured to send a second request message, where the second request message is used to instruct the second network device to make a voice call to the terminal device.

In a possible design, the first request message includes the identifier of the terminal device. The apparatus further includes: a determining unit, configured to determine the phone number of the terminal device according to the identification of the terminal device before sending the second request message. The sending unit is configured to send the phone number of the terminal device to the second network device through the second request message.

In a possible design, the first request message includes the identifier of the terminal device. The sending unit is configured to send the identifier of the terminal device to the second network device through the second request message.

In a possible design, the receiving unit is further configured to receive a first configuration message, where the first configuration message includes a push number field. The sending unit is further configured to send a second configuration message to the terminal device, where the second configuration message includes a push number segment.

A fifteenth aspect provides a network device including one or more processors and one or more memories. One or more memories are coupled to the one or more processors, and the one or more memories store computer instructions. The computer instructions, when executed by one or more processors, cause a network device to perform the communication method of any of the seventh aspect and possible designs thereof.

A sixteenth aspect provides a chip system, the chip includes a processing circuit and an interface. The processing circuit is used to call and run the computer program stored in the storage medium from the storage medium, so as to execute the communication method according to any one of the seventh aspect and its possible designs.

A seventeenth aspect provides a computer-readable storage medium, the computer-readable storage medium comprising computer instructions, when the computer instructions are executed, perform the communication method described in any one of the seventh aspect and its possible designs .

An eighteenth aspect provides a computer program product, the computer program product includes instructions, when the computer program product is run on a computer, the computer can execute according to the instructions as described in any one of the seventh aspect and its possible designs communication method.

It should be understood that, the solutions provided by the above fourteenth aspects to the eighteenth aspects can all correspond to the thirteenth aspect or its possible designs, and thus the beneficial effects that can be obtained are similar, which will not be repeated here.

A nineteenth aspect provides a communication system, which includes the network device provided in the third aspect, the terminal device provided in the ninth aspect, and the network device provided in the fifteenth aspect.

Description of drawings

Fig. 1 is a kind of sending schematic diagram of heartbeat packet;

2 is a schematic diagram of a communication scenario;

3 is a schematic diagram of another communication scenario;

FIG. 4 is a schematic diagram of the composition of a communication architecture provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of the composition of another communication architecture provided by an embodiment of the present application;

6 is a schematic flowchart of a communication method provided by an embodiment of the present application;

FIG. 7 is a schematic flowchart of another communication method provided by an embodiment of the present application;

FIG. 8 is a schematic flowchart of another communication method provided by an embodiment of the present application;

FIG. 9 is a schematic flowchart of another communication method provided by an embodiment of the present application;

FIG. 10 is a schematic diagram of the composition of a communication device according to an embodiment of the present application;

FIG. 11 is a schematic diagram of the composition of a network device according to an embodiment of the application;

FIG. 12 is a schematic diagram of the composition of a chip system provided by an embodiment of the present application;

FIG. 13 is a schematic diagram of the composition of another communication device provided by an embodiment of the present application;

FIG. 14 is a schematic diagram of the composition of a terminal device provided by an embodiment of the present application;

FIG. 15 is a schematic diagram of the composition of another chip system provided by an embodiment of the present application;

FIG. 16 is a schematic diagram of the composition of another communication apparatus provided by an embodiment of the present application;

FIG. 17 is a schematic diagram of the composition of another network device provided by an embodiment of the present application;

FIG. 18 is a schematic diagram of the composition of another chip system provided by an embodiment of the present application.

Detailed ways

During the use of the terminal device, it is often necessary to receive push messages from different network devices. Generally speaking, a terminal device can maintain a long transmission control protocol (Transmission Control Protocol, TCP) connection with a network device (such as a push server) that pushes messages, that is, after completing a data transmission based on a TCP connection, the TCP connection is not closed. So that when the next data transmission is required, the push server can quickly and accurately transmit data to the terminal device based on the TCP connection.

At present, in order to maintain a long TCP connection, the terminal device can send heartbeat packets to the network device that pushes the corresponding message at certain time intervals (such as 2 to 10 minutes), so that the network device can know that the terminal device is always online, that is, Keep a long TCP connection.

Exemplarily, with reference to FIG. 1 , the terminal device is a mobile phone 101 , and the network device that pushes a message is a push server 102 as an example. The mobile phone 101 may establish an RRC connection with the push server 102 every time it needs to send a heartbeat packet to the push server 102, so as to send the heartbeat packet to the push server 102 through the uplink data transmission resources corresponding to the RRC connection. Generally speaking, in order to be able to schedule resources more flexibly, the push server 102 may disconnect the RRC connection after a period of time (eg, 20 seconds) after establishing the RRC connection, so that the resources corresponding to the RRC connection can be reallocated. Therefore, when the mobile phone 101 wants to send the heartbeat packet to the push server 102 again, the above process needs to be repeated, that is, the RRC connection is established first, and then the heartbeat packet is sent on the corresponding resource.

The terminal device can maintain a long TCP connection with the push server according to the method described in FIG. 1 above. In this way, the push server can quickly and accurately send corresponding data to the terminal device when a message needs to be pushed to the terminal device. With reference to FIG. 2 , a scenario of sending and feedback of a push message is shown. The push message is taken as an example of a positioning instruction requesting the terminal device (such as the mobile phone 203 ) to perform positioning and feeding back the positioning result. As shown in FIG. 2 , the service server 201 can send the positioning instruction to the mobile phone 203 through the push server 202 . In response to the positioning instruction, the mobile phone 203 may perform a corresponding positioning operation to obtain positioning information corresponding to the positioning instruction as a positioning result. After acquiring the positioning result information, the mobile phone 203 can transmit it to the service server 201 . In this way, the positioning of the mobile phone can be completed once. Among them, since the push server 202 maintains a long TCP connection with the mobile phone 203, after receiving the positioning instruction, the push server 202 can quickly and accurately send the positioning instruction to the mobile phone 203 through the long TCP connection, so as to improve the message push performance. efficiency.

It can be seen that in the message push scheme based on the TCP long connection, it is necessary to keep the TCP long connection. Therefore, the terminal device needs to frequently initiate an RRC connection and send a heartbeat packet to the push server to maintain the long TCP connection. For a terminal device, when initiating an RRC connection, components such as an application processor (Application Processor, AP) and a modem (Modem) set in it need to be woken up. In combination with the above description, since the terminal device needs to establish an RRC connection frequently, the AP and the Modem are frequently woken up. This will also bring additional power consumption caused by frequently waking up the AP and Modem.

In the prior art, in order to save the power consumption of the terminal device, other means can be used to replace the solution of maintaining a long TCP connection, so that the terminal device does not need to frequently establish an RRC connection with the push server, thereby saving the AP and the Modem from being frequently woken up. resulting power consumption.

In this solution, a short message push server for providing short message service (Short Message Service, SMS) is added. The short message push server can be used to receive push messages from the push server, and generate corresponding short message messages accordingly. The short message push server can send the short message to the terminal device to prompt the terminal device to request the push message from the network side (such as a push server or a service server), and perform corresponding operations and feedback.

Exemplarily, with reference to FIG. 3 , a message push solution combined with a short message server is shown. Among them, the push message is still taken as an example of the positioning instruction requesting the mobile phone to perform positioning and feeding back the positioning result. Compared with the communication scenario shown in FIG. 2 , in the solution shown in FIG. 3 , a short message server 301 is added. Correspondingly, different from the communication process shown in FIG. 2 , when the service server needs to push a message, a positioning instruction can be issued to the push server. The push server may send the push message to the short message server 301 . The short message server 301 can generate a corresponding short message message according to the push message, and send the short message message to the mobile phone. After the mobile phone receives the short information message, the mobile phone can parse the short information message, and according to the short information message, know that there is currently a message in the service server that needs to be received and processed. Then, the mobile phone can initiate a communication connection, such as an RRC connection, to the service server, and obtain a corresponding push message from the push server. After obtaining the push message (such as a positioning instruction), the mobile phone can perform a corresponding positioning operation, and feed back the obtained positioning result to the service server.

It can be seen that, based on the solution shown in Figure 3, the terminal device does not need to maintain a long TCP connection with the network device (such as a push server), so that the terminal device does not need to frequently wake up the AP and the Modem to establish an RRC connection. Thus, the corresponding power consumption overhead is saved.

However, this scheme also has obvious problems. For example, because the SMS service is generally provided by a third party (such as an operator) for a fee. Each push message needs to use a short message, and a fee corresponding to the short message will also be incurred. And due to the huge number of push messages, the resulting costs cannot be ignored. In addition, for some terminal devices that cannot use the SMS service (for example, a terminal device that cannot be inserted into a card, or a terminal device that uses an IoT card), this solution cannot be implemented.

In order to solve the above problem, the embodiment of the present application provides a communication solution, so that the terminal device does not need to maintain a long TCP connection with the network device, and can simultaneously acquire push messages quickly and accurately. Since there is no need to maintain a long TCP connection with the network device, the terminal device does not need to frequently wake up the AP and the Modem, thereby saving the corresponding power consumption overhead. In addition, this solution does not need to use SMS services, so it is more suitable for various terminal devices. At the same time, because the method of voice push is used in this solution, no additional charges (such as charges for using SMS services) will be generated.

The solutions provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

Please refer to FIG. 4 , which is a schematic diagram of a communication architecture provided by an embodiment of the present application. As shown in FIG. 4 , the communication architecture 400 may include a service server 401, a push module 402, and multiple terminal devices (eg, terminal 1 to terminal N). Exemplarily, the plurality of terminal devices may be terminal devices within the service range of the push module 402.

The service server 401 may be used to provide service for the terminal. The business service may include sending push messages, and may also include receiving feedback information from terminals, and the like. It should be noted that, in different implementations, the service server 401 may further include components or modules corresponding to the application server. Alternatively, the service server 401 can also be connected with an independent application server, so as to assist the application server to realize the function corresponding to the relevant application.

The push module 402 may be configured to receive the push message sent by the service server 401, and push the push message to the terminal device. In some implementations of the embodiments of the present application, the push module 402 may be an independent device, or may include multiple devices.

As an example, FIG. 5 shows a schematic diagram of a specific communication architecture provided by an embodiment of the present application. As shown in FIG. 5 , the push module 402 may include a push server 501 and a voice push gateway 502 . In some implementations, the push server 501 and the voice push gateway 502 may be integrated in one device to implement the function of the push module 402 . In other implementation manners, the push server 501 and the voice push gateway 501 may also be independently set up to cooperate to implement the function of the push module 402 .

As shown in FIG. 5 , the communication architecture may further include a service server 401 that communicates with the push server 501 , and a terminal 403 that communicates with the voice push gateway 502 . In an implementation, referring to FIG. 5 , the terminal may be a wearable electronic device such as a children's watch.

It should be noted that, the solutions provided in the embodiments of the present application may be applied to a communication architecture as shown in FIG. 4 . Of course, this solution can also be applied to the specific architecture composition shown in FIG. 5 . For convenience of description, the following description is given by taking the application of the communication solution provided by the embodiment of the present application to the architecture shown in FIG. 5 as an example.

Please refer to FIG. 6 , which is a schematic flowchart of a communication method provided by an embodiment of the present application. As shown in Figure 6, the method may include:

S601. The service server sends a first request message to the push server.

Exemplarily, in some implementation manners, the first request message may be sent by the service server to the push server when it needs to send a push message to the terminal device.

It should be noted that, in different implementation scenarios, the content of the first request message may be different.

For example, in some scenarios, the first request message may include a push request. The push request can be used to inform the push server that the service server needs to send a push message to the terminal device.

In other scenarios, the first request message may include service information specifically corresponding to the push message. So that the push server can determine, according to the received service information, that the service server needs to send a push message to the terminal device.

For convenience of description, the following description is given by taking the first request message including the push request as an example.

S602. The push server sends a second request message to the voice push gateway.

After receiving the first request message, the push server may send the second request message to the voice push gateway according to the first request message.

In different implementations, the content of the second request message may also be the same or different. For example, after the push server receives the first request message including the push request, it can directly forward the push request to the voice push gateway. For another example, after the push server receives the first request message including the service information, it can directly forward the service information to the voice push gateway. For another example, after the push server receives the first request message including the service information, it may send a push request corresponding to the service information to the voice push gateway.

S603. The voice push gateway initiates a voice call to the terminal device.

After receiving the second request message including the push request and/or service information, the voice push gateway may know that the service server needs to push messages to the terminal device. In this embodiment of the present application, since the terminal device does not maintain a long TCP connection with the network side (such as a push server), the voice push gateway needs to inform the terminal device that a connection needs to be established with the network side in order to receive the push message.

Exemplarily, the voice push gateway may initiate a voice call to the terminal device. The voice call may be a traditional voice call based on a 2G/3G circuit switched (Circuit Switched, CS) domain. The voice call may also be a voice call based on a 4G/5G/6G packet switch (Packet Switch, PS) domain. So that the terminal device needs to establish a connection with the network side (such as a service server) to obtain the corresponding push message according to the voice call.

In this embodiment of the present application, since the voice call is used to prompt the terminal device to establish a connection with the network side. Therefore, the voice call is not the same as a normal voice call. In the embodiment of the present application, the voice push gateway may use a preconfigured number segment to initiate a voice call to the terminal device, so that the terminal device can determine according to the incoming call number that the voice call is a call for prompting the terminal device to establish a connection with the network side .

S604. The terminal device identifies the calling number as a push request number.

S605, the terminal device refuses to answer the call, and performs a corresponding operation.

When the terminal device receives the voice call, it can determine the follow-up operation according to the incoming call number corresponding to the voice call.

Exemplarily, the terminal device receives a voice call, and determines that the incoming number of the voice call is a pre-configured number (eg, a push request number) corresponding to a call that prompts the terminal device to establish a connection with the network side. In this example, the incoming call number, that is, the calling number of the voice push gateway may be pre-configured. The number segment corresponding to the number may also be referred to as the push number segment.

In this way, the terminal device can actively reject the voice call without the user's perception (such as not displaying an incoming call interface on the interface, etc.). In some implementations, the operations of identifying the push request number and rejecting the call may be performed in a non-access stratum (NAS) in the terminal device.

As an example, FIG. 7 shows a schematic diagram of an interaction flow between a terminal device and a voice push gateway provided by an embodiment of the present application. As shown in FIG. 7 , when receiving the second request message, the voice push gateway may initiate a voice call to the terminal device (ie, perform S701). It can be understood that, when receiving a voice call, the terminal device may also receive an air interface message corresponding to the voice call, and the air interface message may include information such as an incoming call number. After receiving the air interface message, the terminal device can parse the incoming call number and compare the number with the saved push number segment list. The NAS layer rejects the connection (ie, execute S702). It should be noted that, in some scenarios, in order to enable the voice push gateway to know that the terminal device has successfully parsed, the terminal device may also send a hangup instruction to the voice push gateway (ie, perform S703).

It can be understood that the terminal device can also initiate a connection with the network side according to the received voice call. For example, a terminal device may establish an RRC connection with a service server or a push server on the network side, so as to receive push messages from the network side quickly and accurately. Exemplarily, in some scenarios, the service information is included in the first request message as an example. The terminal device may directly initiate an RRC connection with the push server, and obtain corresponding push messages including service information from the push server through resources corresponding to the RRC connection. In other scenarios, the first request message includes a push request as an example. The terminal device can initiate a communication connection with the service server, and obtain the push message including the service information from the service server through the corresponding resource, or obtain the push message including the service information from the service server through the corresponding resource through the push server.

It should be noted that, since there may be multiple terminal devices within the voice call range of the voice push gateway, not all terminal devices need to receive the push message from the service server. Therefore, in order to enable the voice push gateway to select an accurate terminal device, in the embodiment of the present application, when the terminal device establishes a connection with the push gateway for the first time, the Push software development kit (Software Development Kit, SDK) set therein can be used. An application message is sent to the Push server, where the application message can be used to apply to the push server for a token corresponding to the terminal device, and the push server can configure a token to the corresponding terminal device. Next, the corresponding relationship between the token and the terminal device may be reported to the service server by the terminal device or the push server. So that the service server can, according to the corresponding relationship between the token and the terminal device, carry the token corresponding to the terminal device in the first request message when it needs to deliver a push message to the corresponding terminal device, so that the push server can send the push message to the corresponding terminal device. The token is carried in the second request message to inform the voice push gateway, so that the voice push gateway can determine the number of the corresponding terminal device according to the token to make a voice call.

Exemplarily, it is taken as an example that the push server may push messages to four terminal devices (eg, UE1, UE2, UE3, and UE4), and the first request message includes a push request. When UE1 establishes a connection with the push server for the first time, it may apply for a corresponding token to the push server, and the push server may configure token1 to the UE1. Correspondingly, the push server may configure token2 to UE2, configure token3 to UE3, and configure token4 to UE4. The UE1 corresponds to token1, UE2 corresponds to token2, UE3 corresponds to token3, and the corresponding relationship between UE4 and token4 can be reported by the push server to UE1, UE2, UE3 and the service server corresponding to the application used by UE4. When the service server wants to push a message to UE1, token1 can be carried in the push request to the push server. Similarly, when the service server wants to push a message to UE2, it can carry token2 in the push request to the push server. When the service server wants to push a message to UE3, token3 can be carried in the push request to the push server. When the service server wants to push a message to UE4, it can carry token4 in the push request to the push server.

It can be understood that, after receiving the first request message carrying token1, the push server may carry the token1 in the second request message and send it to the voice push gateway. The voice push gateway may determine that it needs to initiate a voice call to UE1 according to the token1. Then the voice push gateway can initiate a voice call to the number corresponding to UE1. In this way, the voice push gateway can accurately find the UE1 and initiate a call. It should be noted that, in some implementations of the present application, the push request issued by the service server may further include one or more items of device identification, phone number, and Push content. In this way, the voice push gateway can more accurately find the corresponding terminal device to make a voice call.

It should be noted that, in some implementations, the push server may determine the number of UE1 after receiving token1, and directly send the number to the voice push gateway. The voice push gateway can directly initiate a voice call to the received number.

Similarly, when the service server wants to push a message to UE2, UE3, or UE4, the above process can also be referred to, and the corresponding token is carried in the first request message and sent, so that the voice push gateway can send voice to the corresponding terminal device. call. Of course, when the service server wants to push messages to multiple terminal devices, the first request message can also carry the tokens of these terminal devices, so that the voice push gateway can initiate a voice call to the corresponding terminal devices.

In order to more clearly describe the solutions provided by the embodiments of the present application, the communication methods provided by the embodiments of the present application are described below with reference to examples.

Please refer to FIG. 8 , which is a schematic flowchart of a push message according to an embodiment of the present application. Wherein, it is taken as an example that the service server wants to push a positioning request to the terminal device, and the service server sends a push request to the push server. As shown in Figure 8, the process can include:

S801. The service server sends a push request to the push server.

In combination with the above description, the push request may include information such as the token (or token identifier, such as token ID) corresponding to the terminal device, device identifier, phone number, and Push content.

S802, the push server forwards the push request to the voice push gateway.

S803, the voice push gateway initiates a voice call to the terminal device.

The voice push gateway can determine the number of the called party (that is, the corresponding terminal device) to initiate a voice call according to the token, and initiate a voice call to the number.

S804, the terminal device identifies the calling number as a push request number.

S805. The terminal device refuses to answer the call.

S806, the terminal device initiates a connection request to the service server.

S807, the service server sends a positioning request to the terminal device.

S808. The terminal device acquires the positioning information corresponding to the positioning request.

S809, the terminal device sends positioning information to the service server.

Based on the example shown in FIG. 8 , the service server can implement the communication connection with the terminal device through the above S801-S806. In this way, the terminal device does not need to maintain a long TCP connection with the network side (such as the push server) all the time, and the push message of the service server can be quickly and accurately transmitted to the terminal device. Further, the terminal device may perform a corresponding operation according to the received push message, such as performing positioning in the above example, obtaining positioning information, and then feeding back the positioning information to the service server. Thereby, the receiving and processing of the push message without the user's perception is realized.

In the description of the above solution, the voice push gateway needs to initiate a voice call to the terminal device, so that the terminal device can determine the push request number according to the incoming call number. In some implementations of the present application, the calling number of the voice push gateway (ie, the number of the voice push gateway itself) may be pre-configured. In this example, the number segment corresponding to the number may also be called a push number segment.

Exemplarily, FIG. 9 shows a method for a terminal to acquire a preset push number segment. As shown in Figure 9, the method may include:

S901, the voice push gateway obtains the push number segment.

The voice push gateway may obtain the corresponding configured push number segment from the operator. The push number segment can be used as the calling number of the voice push gateway to make a voice call to the terminal device.

S902, the voice push gateway sends the push number segment to the service server.

S903, the terminal device sends the feature information to the service server.

The characteristic information of the terminal device may include information such as the phone number and account information of the terminal device. It can be understood that, through the feature information, the service server can distinguish different terminal devices. In some implementations, the terminal device may report the corresponding feature information to the service server when using the application program corresponding to the service server for the first time.

S904, the service server delivers the push number segment to the push server.

S905, the push server pushes the push number segment to the terminal device.

After acquiring the push number segment and the feature information of each terminal device, the service server may push the push number segment to each terminal device respectively through the push server. It can be understood that, since the terminal device will upload the corresponding feature information when interacting with the service server for the first time, the service server can know that these terminal devices all have the possibility of message push requirements. Thus, the service server can push the push number segment to each terminal device respectively through the push server.

S906, the terminal device receives and stores the push number segment.

After receiving the push number segment pushed by the push server, the terminal device can store the push number segment, so that when receiving a voice call from the voice push gateway, it can match the incoming call number according to the push number segment to determine whether the The voice call is rejected, and a communication connection is initiated with the network side, thereby receiving the push message from the service server.

It should be noted that, in some implementation manners, the terminal device may also feed back corresponding information to the service server after receiving the push number segment, so as to prompt the service server that the push number segment has been received.

In the above example, the voice push gateway obtains the push number segment and then delivers it to the terminal device through the service server as an example for description. In other implementation manners of the present application, the voice push gateway may also directly push the push number segment to the terminal device through the push server after acquiring the push number segment. The specific implementation process thereof will not be repeated here. In addition, in the above example, the voice push gateway obtains the push number segment and delivers it to the terminal device through the service server and the push server as an example for description. In other implementations of the present application, the push number segment may also be transmitted to the terminal device through other paths. For example, the voice push gateway can send the push number segment to the service server after obtaining the push number segment. After receiving the push number segment, the service server can directly use the communication resources with the network device to send the push number segment to the service server. delivered to the terminal device.

It can be seen that, with reference to the above description, it should be clear to those skilled in the art that, based on the solutions provided by the embodiments of the present application, the terminal device can receive push messages without maintaining a long TCP connection with the push server. In this way, the power consumption overhead caused by the frequent awakening of the AP and the Modem due to the terminal device needing to send heartbeat packets frequently can be saved. It is understandable that since the Modem needs to be in a working state all the time after being woken up, additional power consumption overhead will also be generated. In addition, because this solution uses the voice push gateway to make a voice call, the terminal device is prompted to initiate a communication connection to the network side. Based on the immediacy of the voice call, the terminal device can also establish a connection with the network side in a relatively short period of time. Communication connection and get the corresponding push message.

The foregoing mainly introduces the solutions provided by the embodiments of the present application from the perspective of each network element. In order to realize the above-mentioned functions, it includes corresponding hardware structures and/or software modules for executing each function. Those skilled in the art should easily realize that the present application can be implemented in hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

In this embodiment of the present application, the above network elements can be divided into functional modules according to the above method examples. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation.

Please refer to FIG. 10 , which is a schematic diagram of the composition of a communication apparatus 1000 according to an embodiment of the present application. In some implementations, the communication device may be included in a voice push gateway. As shown in FIG. 10 , the communication apparatus 1000 may include: a receiving unit 1001, configured to receive a first request message from a first network device, where the first request message is used to instruct to initiate a voice call to the terminal device. The calling unit 1002 is configured to initiate a voice call to the terminal device, where the voice call is used to indicate that the terminal device has a push message.

In a possible design, the calling unit 1002 is specifically configured to initiate a voice call to the terminal device according to the identifier corresponding to the terminal device.

In a possible design, the calling unit 1002 is configured to determine the phone number of the terminal device according to the identifier corresponding to the terminal device, and make a voice call to the phone number.

In a possible design, the apparatus further includes: an obtaining unit 1003, configured to obtain the push number segment. The sending unit 1004 is configured to send a first configuration message to the second network device, where the first configuration message includes a push number segment, so that the second network device can send the push number segment to the terminal device. Alternatively, the sending unit 1004 is configured to send a second configuration message to the first network device, where the second configuration message includes the push number segment, so that the first network device sends the push number segment to the terminal device.

It should be noted that, all relevant contents of the steps involved in the above method embodiments can be cited in the functional description of the corresponding functional module, which will not be repeated here.

FIG. 11 shows a schematic diagram of the composition of a network device 1100 . The network device 1100 may include: a processor 1101 and a memory 1102 . The memory 1102 is used to store computer-implemented instructions. Exemplarily, in some embodiments, when the processor 1101 executes the instructions stored in the memory 1102, the network device 1100 can be made to perform the operations that the network device (eg, a voice push gateway) needs to perform in the above examples.

FIG. 12 shows a schematic composition diagram of a chip system 1200 . The chip system 1200 may include: a processor 1201 and a communication interface 1202 for supporting a network device (eg, a voice push gateway) to implement the functions involved in the foregoing embodiments. In a possible design, the system-on-a-chip 1200 further includes a memory for storing necessary program instructions and data of a network device (such as a voice push gateway). The chip system 1200 may be composed of chips, or may include chips and other discrete devices.

Please refer to FIG. 13 , which is a schematic diagram of the composition of a communication apparatus 1300 according to an embodiment of the present application. In some examples, the communication apparatus 1300 may be provided in the terminal equipment involved in the above examples.

As shown in FIG. 13 , the communication device 1300 may include a receiving unit 1301 for receiving a voice call. The determining unit 1302 is configured to determine the incoming call number of the voice call. The sending unit 1303 is configured to send a connection request to the first network device corresponding to the push number when the incoming call number is a pushed push number, where the connection request is used to establish a communication connection with the first network device. The receiving unit 1301 is further configured to receive the push message from the first network device through the communication connection.

In a possible design, the determining unit 1302 corresponds to the non-access stratum NAS set in the communication device, and the determining unit 1302 is configured to parse the air interface message corresponding to the voice call and determine the incoming number of the voice call. The apparatus further includes: a rejecting unit 1304, configured to reject the voice call when the incoming call number is a push number.

In a possible design, the sending unit 1303 is configured to initiate a radio resource control RRC connection request to the first network device corresponding to the push number, so as to establish an RRC connection with the first network device. The receiving unit 1301 is configured to receive a push message from a first network device through an RRC connection.

In a possible design, the receiving unit 1301 is further configured to receive a first configuration message, where the first configuration message includes a push number field. The apparatus further includes: a storage unit 1305 for storing the push number segment.

FIG. 14 shows a schematic diagram of the composition of a terminal device 1400 . The terminal device 1400 may include: a processor 1401 and a memory 1402 . The memory 1402 is used to store computer-implemented instructions. Exemplarily, in some embodiments, when the processor 1401 executes the instructions stored in the memory 1402, the terminal device 1400 may be caused to perform the operations that the terminal device needs to perform in the above examples.

FIG. 15 shows a schematic diagram of the composition of a chip system 1500 . The chip system 1500 may include: a processor 1501 and a communication interface 1502, which are used to support the terminal device to implement the functions involved in the above embodiments. In a possible design, the chip system 1500 further includes a memory for storing necessary program instructions and data of the terminal device. The chip system 1500 may be composed of chips, or may include chips and other discrete devices.

FIG. 16 shows a schematic composition diagram of a communication apparatus 1600 provided by an embodiment of the present application. In some implementations, the communication device 1600 may be provided in a push server.

As shown in FIG. 16 , the communication apparatus 1600 includes: a receiving unit 1601, configured to receive a first request message from a first network device, where the first request message is used to request to push a message to a terminal device. The sending unit 1602 is configured to send a second request message, where the second request message is used to instruct the second network device to make a voice call to the terminal device.

In a possible design, the first request message includes the identifier of the terminal device. The communication apparatus 1600 further includes: a determining unit 1603, configured to determine the phone number of the terminal device according to the identifier of the terminal device before sending the second request message. The sending unit 1602 is configured to send the phone number of the terminal device to the second network device through the second request message.

In a possible design, the first request message includes the identifier of the terminal device. The sending unit 1602 is configured to send the identifier of the terminal device to the second network device through the second request message.

In a possible design, the receiving unit 1601 is further configured to receive a first configuration message, where the first configuration message includes a push number field. The sending unit 1602 is further configured to send a second configuration message to the terminal device, where the second configuration message includes a push number field.

FIG. 17 shows a schematic diagram of the composition of a network device 1700 . The network device 1700 may include: a processor 1701 and a memory 1702 . The memory 1702 is used to store computer-implemented instructions. Exemplarily, in some embodiments, when the processor 1701 executes the instructions stored in the memory 1702, the network device 1700 can be made to perform the operations that the network device (such as a push server) needs to perform in the above examples.

FIG. 18 shows a schematic composition diagram of a chip system 1800 . The chip system 1800 may include: a processor 1801 and a communication interface 1802, which are used to support a network device (such as a push server) to implement the functions involved in the above embodiments. In a possible design, the system-on-a-chip 1800 further includes a memory for storing necessary program instructions and data of the network device. The chip system 1800 may be composed of chips, or may include chips and other discrete devices.

The functions or actions or operations or steps in the above embodiments may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer, or data storage devices including one or more servers, data centers, etc. that can be integrated with the medium. The usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.

Although the application has been described in conjunction with specific features and embodiments thereof, it will be apparent that various modifications and combinations can be made therein without departing from the spirit and scope of the application. Accordingly, this specification and drawings are merely exemplary illustrations of the application as defined by the appended claims, and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of this application. Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

A communication method, characterized in that the method comprises:

receiving a first request message from a first network device, where the first request message is used to instruct to initiate a voice call to the terminal device;

A voice call is initiated to the terminal device, where the voice call is used to indicate that the terminal device has a push message.
The method according to claim 1, wherein the first request message includes an identifier corresponding to the terminal device,

The initiating a voice call to the terminal device includes:

According to the identifier corresponding to the terminal device, a voice call is initiated to the terminal device.
The method according to claim 2, wherein the identifier corresponding to the terminal device is a phone number of the terminal device.
The method according to claim 2, wherein the initiating a voice call to the terminal device according to the identifier corresponding to the terminal device comprises:

Determine the phone number of the terminal device according to the identifier corresponding to the terminal device, and make a voice call to the phone number.
The method according to any one of claims 1-4, wherein the method further comprises:

Get the push number segment;

sending a first configuration message to a second network device, where the first configuration message includes the push number segment, so that the second network device can send the push number segment to the terminal device; or,

Send a second configuration message to the first network device, where the second configuration message includes the push number segment, so that the first network device sends the push number segment to the terminal device.
The method according to claim 5, wherein the outgoing number for initiating a voice call to the terminal device is included in the push number segment.
A communication method, characterized in that the method comprises:

receive voice calls;

determining the incoming number of the voice call;

When the incoming call number is a pushed push number, send a connection request to the first network device corresponding to the push number, where the connection request is used to establish a communication connection with the first network device;

A push message is received from the first network device over the communication connection.
The method according to claim 7, wherein when the incoming call number is included in the stored push number segment, the incoming call number is the push number.
The method of claim 8, wherein:

The determining of the incoming call number of the voice call includes:

The non-access stratum NAS parses the air interface message corresponding to the voice call, and determines the incoming number of the voice call;

The method also includes:

When the incoming call number is the push number, the NAS rejects the voice call.
The method according to any one of claims 7-9, wherein sending a connection request to the first network device corresponding to the push number comprises:

Initiating a radio resource control RRC connection request to the first network device corresponding to the push number, so as to establish an RRC connection with the first network device;

The receiving a push message from the first network device through the communication connection includes:

A push message from the first network device is received through the RRC connection.
The method according to any one of claims 7-10, wherein the method further comprises:

receiving a first configuration message, where the first configuration message includes a push number segment;

The push number segment is stored.
A communication method, characterized in that the method comprises:

receiving a first request message from a first network device, where the first request message is used to request to push a message to the terminal device;

Send a second request message, where the second request message is used to instruct the second network device to make a voice call to the terminal device.
The method according to claim 12, wherein the first request message includes an identifier of the terminal device;

Before the sending the second request message, the method further includes:

According to the identification of the terminal device, determine the phone number of the terminal device,

The sending the second request message includes: sending the phone number of the terminal device to the second network device through the second request message.
The method according to claim 12, wherein the first request message includes an identifier of the terminal device;

The sending the second request message includes: sending the identifier of the terminal device to the second network device through the second request message.
The method according to any one of claims 12-14, wherein the method further comprises:

receiving a first configuration message, where the first configuration message includes a push number segment;

Send a second configuration message to the terminal device, where the second configuration message includes the push number field.
A network device, characterized in that the network device includes one or more processors and one or more memories; the one or more memories are coupled with the one or more processors, and the one or more memories a memory storing computer instructions;

The computer instructions, when executed by the one or more processors, cause the network device to perform the communication method of any of claims 1-6.
A terminal device, characterized in that the terminal device includes one or more processors and one or more memories; the one or more memories are coupled with the one or more processors, and the one or more memories a memory storing computer instructions;

When the one or more processors execute the computer instructions, the terminal device is caused to perform the communication method according to any one of claims 7-11.
A network device, characterized in that the network device includes one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, and the one or more memories a memory storing computer instructions;

The computer instructions, when executed by the one or more processors, cause the network device to perform the communication method of any of claims 12-15.
A communication system, characterized in that, the communication system comprises the network device as claimed in claim 16 , the terminal device as claimed in claim 17 , and the network device as claimed in claim 18 .