Control method and device for only receiving but not sending IP (Internet Protocol) short message

Abstract

The invention relates to the technical field of communication, in particular to a control method and device for only receiving but not sending an IP short message. The control method for only receiving and not sending the IP short message comprises the steps that under the condition that first subscription data of a short message semi-stop SiFC is obtained, a short message sending request corresponding to a first terminal is received, the short message semi-stop SiFC comprises a short message registration iFC and a short message calling iFC, or the short message semi-stop SiFC comprises the short message registration iFC and does not comprise the short message calling iFC, and the first subscription data of the short message semi-stop SiFC comprises the short message registration iFC and does not comprise the short message calling iFC; the short message semi-stop SiFC first subscription data is data signed by the first terminal and used for executing only receiving and not sending operation on an IP short message of the first terminal; the target information of the short message sending request is obtained, and when the short message semi-stop SiFC comprises a short message registration iFC and a short message calling iFC, the target information is an In-Reply-To parameter or an IP short message gateway host name parameter of a Request URI; and according to the target information and the triggering condition of the short message semi-stop SiFC, executing an operation of only receiving but not sending on the IP short message of the first terminal. According to the invention, the accuracy of half-stop of the IP short message can be improved.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a control method and device for receiving but not sending Internet Protocol (IP) short messages. Background Art

[0002] With the development of communication technology, short messages are a communication service that accompanies digital mobile communication systems. They are quasi-real-time, non-voice communication services. In the traditional second-generation mobile phone communication technology (2-Generation wireless telephone technology, 2G) era, short messages transmit text, numbers and other character information through the signaling channel and signaling network of the mobile communication system. For example, the sending and receiving of short messages can be controlled through the short messaging service (SMS) over IP. For example, when the short messaging service is cancelled, the function of IP short messages can be completely cancelled, that is, the receiving and sending functions of IP short messages can be completely cancelled, making the sending and receiving accuracy of IP short messages poor. Summary of the invention

[0003] The present invention provides a control method and device for receiving but not sending IP short messages, which can provide a mechanism for half-pausing IP short messages and improve the accuracy of half-pausing IP short messages. The technical solution of the present invention is as follows:

[0004] According to a first aspect of an embodiment of the present disclosure, a control method for receiving but not sending an IP short message is provided, which is applied to a first network element and includes:

[0005] In the case of acquiring the first contract data of the SMS semi-stop SiFC, receiving the SMS sending request corresponding to the first terminal, wherein the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC or the SMS semi-stop SiFC includes the SMS registration iFC but does not include the SMS calling iFC, and the SMS semi-stop SiFC first contract data is the data signed by the first terminal and used to perform a receiving-only but not sending operation on the IP SMS of the first terminal;

[0006] Obtaining the target information of the SMS sending request, wherein when the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC, the target information is the "In-Reply-To" parameter or the IP SMS gateway host name parameter of the Request URI;

[0007] According to the target information and the triggering condition of the SMS semi-stop SiFC, the IP SMS of the first terminal is only received but not sent.

[0008] According to some embodiments, the SMS semi-stop SiFC includes SMS registration iFC and SMS calling iFC, the target information is an "In-Reply-To" parameter, and the receiving-only but not sending operation is performed on the IP SMS of the first terminal according to the target information, including:

[0009] When the SMS sending request includes an SMS message and the SIP Header of the SMS message does not include the "In-Reply-To" parameter, the triggering condition of the SMS calling iFC in the SMS semi-stop SiFC is not met, and the sending of the SMS message to the second terminal is stopped, wherein the SMS message is the message sent by the first terminal to the second terminal in the SMS sending request;

[0010] When the SMS sending request includes a SMS receipt message and the SIP Header field of the SMS receipt message includes the "In-Reply-To" parameter, the trigger condition of the SMS caller iFC in the SMS semi-stop SiFC is met, triggering the IP SMS receipt sending operation for the first terminal, wherein the SMS receipt message is a message sent by the first terminal to the IP SMS gateway.

[0011] According to some embodiments, the SMS semi-stop SiFC includes SMS registration iFC and SMS calling iFC, the target information is the IP SMS gateway host name parameter of the Request URI, and the receiving-only but not sending operation is performed on the IP SMS of the first terminal according to the target information, including:

[0012] When the SMS sending request includes an SMS message and the request Request Uniform Resource Identifier (URI) does not include the IP SMS gateway host name parameter, the triggering condition of the SMS calling iFC in the SMS semi-stop SiFC is not met, and the sending of the SMS message to the second terminal is stopped, wherein the SMS message is the message sent by the first terminal to the second terminal in the SMS sending request;

[0013] When the SMS sending request includes an SMS receipt message and the Request URI includes the IP SMS gateway host name parameter, the trigger condition of the SMS caller iFC in the SMS semi-stop SiFC is met, triggering the IP SMS receipt sending operation for the first terminal, wherein the SMS receipt message is a message sent by the first terminal to the IP SMS gateway.

[0014] According to some embodiments, the SMS semi-stop SiFC includes the SMS registration iFC but does not include the SMS calling iFC, and the performing of the receiving-only but not sending operation on the IP SMS of the first terminal according to the target information includes:

[0015] In a case where the SMS sending request includes an SMS message, stopping sending the SMS message to the second terminal, wherein the SMS message is a message sent from the first terminal to the second terminal in the SMS sending request;

[0016] In the case that the SMS sending request includes a SMS receipt message, an IP SMS receipt sending operation is triggered for the first terminal, wherein the SMS receipt message is a message sent by the first terminal to the IP SMS gateway.

[0017] According to some embodiments, the method further comprises:

[0018] When the second contract data is obtained, the IP SMS sending and receiving function of the first terminal is restored.

[0019] According to a second aspect of an embodiment of the present disclosure, a control method for receiving but not sending IP short messages is provided, the method being executed by a first terminal, wherein the short message semi-stop SiFC includes the short message registration iFC and does not include the short message calling iFC, the method comprising:

[0020] Get the host name of the IP SMS gateway carried in the From header field of the SMS receipt message;

[0021] The From header field is used as the Request-URI, wherein the Request-URI is used to instruct the first network element to send the SMS receipt message to the IP SMS gateway according to the path corresponding to the Request-URI.

[0022] According to a third aspect of an embodiment of the present disclosure, a control method for receiving but not sending an IP short message is provided, the method being executed by a second network element, comprising:

[0023] Receiving a first instruction sent by a business operation support system, wherein the first instruction is generated by the business operation support system when it receives a semi-stop request;

[0024] In response to the first instruction, canceling the IP SMS function of the first terminal corresponding to the half-stop request;

[0025] receiving a second instruction sent by the business operation support system, and canceling the non-IP SMS sending function of the first terminal in response to the second instruction;

[0026] receiving a third instruction sent by the business operation support system, and restoring the non-IP SMS receiving function of the first terminal in response to the third instruction;

[0027] Receive the fourth instruction sent by the business operation support system, and in response to the fourth instruction, sign a contract for the first terminal for the first contract data of the half-stop SMS SiFC, wherein the first contract data of the half-stop SMS SiFC is used by the first network element to perform a receive-only but not send operation on the IP SMS of the first terminal.

[0028] According to a fourth aspect of an embodiment of the present disclosure, a control method for receiving but not sending an IP short message is provided, the method being executed by a second network element, comprising:

[0029] Receiving a fifth instruction sent by the business operation support system, wherein the fifth instruction is generated by the business operation support system when it receives an IP SMS restoration request;

[0030] In response to the fifth instruction, restoring the non-IP SMS sending function of the first terminal;

[0031] receiving a sixth instruction sent by the business operation support system, and restoring the non-IP SMS receiving function of the first terminal in response to the sixth instruction;

[0032] receiving a seventh instruction sent by the business operation support system, and canceling the semi-stop function of the IP SMS of the first terminal in response to the seventh instruction;

[0033] An eighth instruction sent by the business operation support system is received, and in response to the eighth instruction, an IP short message sending and receiving function of the first terminal is restored.

[0034] According to a fifth aspect of an embodiment of the present disclosure, a control device for receiving but not sending IP short messages is provided, comprising:

[0035] a request receiving unit, configured to receive a text message sending request corresponding to the first terminal when obtaining first contract data of a half-stop SMS SiFC, wherein the half-stop SMS SiFC includes a text message registration iFC and a text message calling iFC or the half-stop SMS SiFC includes a text message registration iFC but does not include a text message calling iFC, and the first contract data of the half-stop SMS SiFC is data signed by the first terminal and used to perform a receive-only but not send operation on an IP text message of the first terminal;

[0036] An information acquisition unit, used for acquiring target information of the SMS sending request, wherein when the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC, the target information is an "In-Reply-To" parameter or an IP SMS gateway host name parameter of the Request URI;

[0037] The operation execution unit is used to execute the operation of receiving but not sending IP short messages of the first terminal according to the target information and the triggering condition of the short message semi-stop SiFC.

[0038] According to a sixth aspect of an embodiment of the present disclosure, there is provided a control device for receiving but not sending IP short messages, comprising:

[0039] A first instruction receiving unit, configured to receive a first instruction sent by a business operation support system, wherein the first instruction is generated by the business operation support system when it receives a semi-stop request;

[0040] a function canceling unit, configured to cancel the IP SMS function of the first terminal corresponding to the semi-stop request in response to the first instruction;

[0041] The first instruction receiving unit is further used to receive a second instruction sent by the business operation support system, and cancel the non-IP SMS sending function of the first terminal in response to the second instruction;

[0042] The first instruction receiving unit is further configured to receive a third instruction sent by the business operation support system, and restore the non-IP SMS receiving function of the first terminal in response to the third instruction;

[0043] The first instruction receiving unit is further used to receive a fourth instruction sent by the business operation support system, and in response to the fourth instruction, to sign a contract for the first terminal for the first SMS semi-stop SiFC first contract data, wherein the first SMS semi-stop SiFC first contract data is used to perform a receive-only but not send operation on the first terminal.

[0044] According to a seventh aspect of an embodiment of the present disclosure, there is provided a control device for receiving but not sending IP short messages, comprising:

[0045] A second instruction receiving unit is used to receive a fifth instruction sent by the business operation support system, wherein the fifth instruction is generated by the business operation support system when it receives an IP SMS restoration request;

[0046] a function recovery unit, configured to recover the non-IP short message sending function of the first terminal in response to the fifth instruction;

[0047] The second instruction receiving unit is further configured to receive a sixth instruction sent by the business operation support system, and restore the non-IP SMS receiving function of the first terminal in response to the sixth instruction;

[0048] The second instruction receiving unit is further configured to receive a seventh instruction sent by the business operation support system, and cancel the semi-stop function of the IP SMS of the first terminal in response to the seventh instruction;

[0049] The second instruction receiving unit is further configured to receive an eighth instruction sent by the business operation support system, and restore the IP short message sending and receiving function of the first terminal in response to the eighth instruction.

[0050] According to an eighth aspect of an embodiment of the present disclosure, a network side device is provided, including:

[0051] processor;

[0052] a memory for storing instructions executable by the processor;

[0053] The processor is configured to execute the instructions to implement the control method for receiving but not sending IP short messages as described in any one of the first aspect or the third aspect.

[0054] According to a ninth aspect of an embodiment of the present disclosure, a first terminal is provided, including:

[0055] processor;

[0056] a memory for storing instructions executable by the processor;

[0057] The processor is configured to execute the instructions to implement the control method for receiving but not sending IP short messages as described in any one of the second aspects above.

[0058] According to the tenth aspect of an embodiment of the present disclosure, a storage medium is provided. When the instructions in the storage medium are executed by a processor of a network side device, the network side device can execute the control method for receiving but not sending IP text messages as described in any one of the first aspect or the third aspect.

[0059] According to an eleventh aspect of an embodiment of the present disclosure, a computer program product is provided, including a computer program, wherein the computer program implements the method described in any one of the first aspect or the third aspect when executed by a processor.

[0060] According to the twelfth aspect of an embodiment of the present disclosure, a communication system is provided, characterized in that it includes a first terminal, a first network element, and a second network element, wherein the first network element is configured to implement the method described in any one of the first aspect, the first terminal is configured to implement the method described in any one of the second aspect, and the second network element is configured to implement the method described in any one of the third aspect or the fourth aspect.

[0061] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:

[0062] In some or related embodiments, by obtaining the first contract data of the SMS semi-stop SiFC, receiving the SMS sending request corresponding to the first terminal, wherein the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC or the SMS semi-stop SiFC includes the SMS registration iFC but does not include the SMS calling iFC; obtaining the target information of the SMS sending request, wherein when the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC, the target information is the "In-Reply-To" parameter or the IP SMS gateway host name parameter of the Request URI; and performing a receive-only but not send operation on the IP SMS of the first terminal according to the target information and the triggering condition of the SMS semi-stop SiFC. Therefore, a mechanism of IP SMS semi-stop can be provided, which can determine whether to perform a receive-only but not send operation on the IP SMS according to the target information, improve the accuracy of IP SMS control, reduce the situation where the complete cancellation of IP SMS increases the probability of complaints, improve the accuracy of IP SMS semi-stop, and reduce the probability of complaints.

[0063] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0065] Figure 1 It is a flow chart of a control method for receiving but not sending IP short messages according to an exemplary embodiment;

[0066] Figure 2 It is a flow chart of a control method for receiving but not sending IP short messages according to an exemplary embodiment;

[0067] Figure 3 is a schematic diagram showing an example structure of an iFC according to an exemplary embodiment;

[0068] Figure 4 An example schematic diagram showing a method for creating a short message semi-stop SiFC according to an embodiment of the present disclosure;

[0069] Figure 5 An example schematic diagram showing a method for creating a short message semi-stop SiFC according to an embodiment of the present disclosure;

[0070] Figure 6 An example schematic diagram showing a method for creating a short message semi-stop SiFC according to an embodiment of the present disclosure;

[0071] Figure 7 It is a flow chart of a control method for receiving but not sending IP short messages according to an exemplary embodiment;

[0072] Figure 8 is a block diagram of a control device for receiving but not sending IP short messages according to an exemplary embodiment;

[0073] Fig. 9 is a block diagram of a control device for receiving but not sending IP short messages according to an exemplary embodiment;

[0074] Fig.10 is a block diagram of a control device for receiving but not sending IP short messages according to an exemplary embodiment;

[0075] Fig.11 It is a block diagram of a control system for receiving but not sending IP short messages according to an exemplary embodiment;

[0076] Fig.12 The invention is a block diagram of a network side device according to an exemplary embodiment. DETAILED DESCRIPTION

[0077] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0078] The disclosed embodiments provide a control method and device for receiving but not sending IP short messages. In some embodiments, the control method for receiving but not sending IP short messages can be replaced with information processing method, communication method and other terms, the control device for receiving but not sending IP short messages can be replaced with information processing device, communication device and other terms, and the terms information processing system, communication system and other terms can be replaced with each other.

[0079] The embodiments of the present disclosure are not exhaustive, but are only illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined, for example, some or all of the steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0080] In each embodiment of the present disclosure, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment based on their internal logical relationships.

[0081] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0082] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular form, such as "a", "an", "the", "above", "said", "aforementioned", "this", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun after the article may be understood as a singular expression or a plural expression.

[0083] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0084] In some embodiments, the terms “at least one,” “one or more,” “a plurality of,” “multiple,” etc. may be used interchangeably.

[0085] In some embodiments, "at least one of A and B", "A and / or B", "A in one case, B in another case", "in response to one case A, in response to another case B", etc., may include the following technical solutions according to the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). When there are more branches such as A, B, C, etc., the above is also similar.

[0086] In some embodiments, the recording method of "A or B" may include the following technical solutions according to the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). When there are more branches such as A, B, C, etc., the above is also similar.

[0087] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects, and do not constitute restrictions on the position, order, priority, quantity or content of the description objects. The statement of the description object refers to the description in the context of the claims or embodiments, and should not constitute unnecessary restrictions due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields", and the "first" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number, and can be one or more. Taking the "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes may be the same or different. For example, if the description object is "device", then the "first device" and the "second device" may be the same device or different devices, and their types may be the same or different. For another example, if the description object is "information", then the "first information" and the "second information" may be the same information or different information, and their contents may be the same or different.

[0088] In some embodiments, “including A”, “comprising A”, “used to indicate A”, and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0089] In some embodiments, terms such as "in response to ...", "in response to determining ...", "in the case of ...", "at the time of ...", "when ...", "if ...", "if ...", etc. can be used interchangeably.

[0090] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not lower than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "no more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0091] In some embodiments, devices and equipment may be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they may also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0092] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0093] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station (radio base station)", "fixed station (fixed station)", and in some embodiments may also be understood as "node (node)", "access point (access point)", "transmission point (TP)", "reception point (reception point, RP)", "transmission and / or reception point (transmission / reception point, TRP)"", "panel (panel)", "antenna panel (antenna panel)", "antenna array (antenna array)"", "cell (cell)", "macro cell (macro cell)", "small cell (small cell)", "femto cell (femto cell)", "pico cell (pico cell)", "sector (sector)", "cell group (cell group)", "serving cell (serving cell)", "carrier (carrier)", "component carrier (component carrier)", "bandwidth part (bandwidth part, BWP)" and the like.

[0094] In some embodiments, "terminal" or "terminal device" can be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

[0095] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0096] In addition, each element, each row, or each column in the table of the embodiments of the present disclosure may be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns may also be implemented as an independent embodiment.

[0097] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0098] Figure 1 FIG. 1 is a flow chart of a control method for receiving but not sending IP short messages according to an exemplary embodiment. Figure 1 As shown, the control method for receiving but not sending IP short messages can be used in a control scenario where only IP short messages are received but not sent, and includes the following steps:

[0099] In step S11, when the first contract data of the SMS semi-stop SiFC is obtained, a SMS sending request corresponding to the first terminal is received;

[0100] According to some embodiments, the execution subject of the embodiments of the present disclosure may be, for example, a first network element, wherein the first network element may be, for example, a serving-call session control function (S-CSCF) network element.

[0101] In some embodiments, the SMS semi-stop of the embodiments of the present disclosure may be, for example, a situation where IP SMS can only be received but not sent. Among them, the first contract data may be, for example, data about the SMS semi-stop contract in the Home Subscriber Server (HSS) or the Unified Data Management (UDM). The first contract data does not specifically refer to a fixed data. The first in the first contract data is only used to distinguish it from the remaining contract data. For example, when the contract time point corresponding to the first contract data changes, the first contract data may also change accordingly. For example, when the contract content corresponding to the first contract data changes, the first contract data may also change accordingly. Among them, the SMS semi-stop SiFC includes the SMS registration iFC and the SMS caller iFC, or the SMS semi-stop SiFC includes the SMS registration iFC and does not include the SMS caller iFC. The first contract data of the SMS semi-stop SiFC is the data signed by the first terminal and is used to perform a receive-only but not send operation on the IP SMS of the first terminal.

[0102] According to some embodiments, the first terminal may be, for example, a terminal that has created SiFC and obtained the first subscription data. The first terminal does not specifically refer to a fixed terminal. For example, when the terminal identifier of the first terminal changes, the first terminal may also change accordingly.

[0103] In some embodiments, the SMS sending request corresponding to the first terminal may be, for example, a request for the first terminal to send or receive a SMS.

[0104] According to some embodiments, when the first contract data of the SMS semi-stop SiFC is obtained, a SMS sending request corresponding to the first terminal is received.

[0105] In step S12, the target information of the SMS sending request is obtained;

[0106] According to some embodiments, the target information may refer to information used to determine whether to perform a corresponding operation on a text message sending request. The target information does not specifically refer to a fixed information. For example, when the trigger type of the SMS semi-stop SiFC changes, the target information may also change accordingly.

[0107] According to some embodiments, for example, the target information of the SMS sending request can be obtained. Wherein, when the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC, the target information is the "In-Reply-To" parameter or the IP SMS gateway host name parameter of the Request URI.

[0108] In step S13, according to the target information and the triggering condition of the SMS semi-stop SiFC, the IP SMS of the first terminal is only received but not sent.

[0109] According to some embodiments, the trigger condition of the SMS SiFC corresponds to the trigger type corresponding to the target information. For example, when different trigger types change, the trigger condition of the SMS SiFC may also change accordingly.

[0110] Optionally, the IP SMS receiving but not sending operation may be, for example, the receiving operation of the IP SMS but not the sending operation of the IP SMS, that is, the first terminal can only receive the IP SMS but not send the IP SMS.

[0111] In some embodiments, for example, according to the target information and the triggering condition of the SMS semi-stop SiFC, the IP SMS of the first terminal may be only received but not sent.

[0112] In some or related embodiments, by obtaining the first contract data of the SMS semi-stop SiFC, receiving the SMS sending request corresponding to the first terminal, wherein the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC or the SMS semi-stop SiFC includes the SMS registration iFC and does not include the SMS calling iFC; obtaining the target information of the SMS sending request, wherein when the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC, the target information is the "In-Reply-To" parameter or the IP SMS gateway host name parameter of the Request URI; and performing a receive-only but not send operation on the IP SMS of the first terminal according to the target information and the triggering condition of the SMS semi-stop SiFC. Therefore, a mechanism for the semi-stop of IP SMS can be provided, which can determine whether to perform the receive-only but not send operation on the IP SMS according to the target information, improve the accuracy of the IP SMS control, reduce the situation where the complete cancellation of IP SMS increases the probability of complaints, improve the accuracy of the semi-stop of IP SMS, and reduce the probability of complaints.

[0113] Figure 2FIG. 1 is a flow chart of a control method for receiving but not sending IP short messages according to an exemplary embodiment. Figure 2 As shown, the control method for receiving but not sending IP short messages can be used in a control scenario where only IP short messages are received but not sent, and includes the following steps:

[0114] In step S21, when the first contract data of the SMS semi-stop SiFC is obtained, a SMS sending request corresponding to the first terminal is received;

[0115] The specific process is as described above and will not be repeated here.

[0116] Optionally, the structure of iFC can be, for example, Figure 3 As shown, the trigger condition "Trigger Point" includes "Request-Uniform Resource Identifier (URI)", "Session Initiation Protocol (SIP) Method", "SIP Header", "Session Case" and "Session Description".

[0117] According to some embodiments, the first contract data may be, for example, data obtained from one of the serving-call session control function (S-CSCF) HSS network element and the UDM network element. The data in the HSS / UDM network element may be, for example, contract data generated when the first terminal signs up for "SMS semi-stop SiFC" according to the instruction sent by the BOSS system. The first contract data of the SMS semi-stop SiFC is the data signed by the first terminal and is used to perform a receive-only operation on the IP SMS of the first terminal.

[0118] In step S22, the target information of the SMS sending request is obtained;

[0119] The specific process is as described above and will not be repeated here.

[0120] Optionally, the created SiFC may include, for example, SMS registration iFC and SMS calling iFC, wherein the trigger condition of SMS calling iFC may be, for example, adding an "In-Reply-To" parameter to the trigger condition "SIP Header" of calling iFC. At this time, the target information may be, for example, the In-Reply-To parameter.

[0121] Optionally, the created SiFC may include, for example, SMS registration iFC and SMS calling iFC, wherein the trigger condition of SMS calling iFC may be, for example, adding an IP SMS gateway host name parameter to the trigger condition "Request URI" of calling iFC. At this time, the target information may be, for example, an IP SMS gateway host name parameter.

[0122] Optionally, the created SiFC may, for example, only include SMS registration iFC, but not SMS calling iFC, wherein the triggering condition of SMS calling iFC may, for example, be for sending an SMS message MESSAGE. Since the "SMS calling iFC" is not included in the "SMS half-stop SiFC" configuration of the S-CSCF network element, the S-CSCF network element does not trigger the "SMS half-stop SiFC", and the SMS message MESSAGE cannot be sent; for receiving the SMS message MESSAGE, since the "SMS half-stop SiFC" configuration of the S-CSCF network element does not include the "SMS calling iFC", the S-CSCF network element does not trigger the "SMS half-stop SiFC". After the first terminal receives the IP SMS, the SMS receipt message is returned by the first network element to the IP SMS gateway according to the path of the Request-URI parameter in the SMS message.

[0123] In step S23, according to the target information and the triggering condition of the SMS semi-stop SiFC, the IP SMS of the first terminal is only received but not sent;

[0124] The specific process is as described above and will not be repeated here.

[0125] Among them, the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC, and the target information is the "In-Reply-To" parameter. According to the target information, the IP SMS of the first terminal is only received but not sent, including:

[0126] When the SMS sending request includes an SMS message and the SIP Header of the SMS message does not include an "In-Reply-To" parameter, the triggering condition of the SMS calling iFC in the SMS semi-stop SiFC is not met, and the sending of the SMS message to the second terminal is stopped, wherein the SMS message is the message sent from the first terminal to the second terminal in the SMS sending request;

[0127] When the SMS sending request includes an SMS receipt message and the SIP Header field of the SMS receipt message includes the "In-Reply-To" parameter, the trigger condition of the SMS caller iFC in the SMS semi-stop SiFC is met, triggering the IP SMS receipt sending operation for the first terminal, wherein the SMS receipt message is a message sent by the first terminal to the IP SMS gateway.

[0128] In some embodiments, a SiFC is created, including the SMS registration iFC and the SMS calling iFC, and the "In-Reply-To" parameter is added to the trigger condition "SIP Header" of the calling iFC. For example, by comparing the IP SMS origination MESSAGE message packet and the IP SMS receipt MESSAGE message packet, it can be found that the IP SMS receipt MESSAGE message packet contains the "In-Reply-To" header field, so a SMS SiFC can be created, including the SMS registration iFC and the SMS calling iFC, and the judgment of the "In-Reply-To" parameter is added to the "SIP Header" trigger condition of the calling iFC structure, so that the IP SMS receiving but not sending operation can be performed on the first terminal.

[0129] Optionally, in the SMS sending request received by the S-CSCF, the SMS sending request includes an SMS message MESSAGE, and the SMS message MESSAGE may include, for example, an initial SMS sending message. If the initial SMS sending message does not include an "In-Reply-To" header field, the IP SMS cannot be sent. In the SMS sending request received by the S-CSCF, the SMS sending request includes an SMS receipt message MESSAGE. If the SMS receipt message MESSAGE includes an "In-Reply-To" header field, the triggering condition of the SMS semi-stop SiFC created in this embodiment is met, and the first terminal can receive IP SMS but cannot send IP SMS, thereby meeting the communication operator's requirement to control IP SMS to only receive but not send. Among them, the "In-Reply-To" header field may, for example, indicate that the message is an SMS receipt message.

[0130] According to some embodiments, Figure 4 A method for creating a SMS semi-stop SiFC in an embodiment of the present disclosure is shown. For example, a "SMS semi-stop SiFC" may be created on an S-CSCF network element. The configuration includes specific configurations of SMS calling iFC and SMS registration iFC, which may include priority, host name, trigger condition (SPT), etc.

[0131] Optionally, creating a "SMS semi-stop SiFC" on the S-CSCF network element may include, for example:

[0132] Add a trigger condition judgment in the TriggerPoint configuration: judge whether the SIP message header field SIP Header of the received MESSAGE message contains the "In-Reply-To" parameter representing the "receipt message". If it does, trigger the SiFC:

[0133]

[0134]

[0135] Optionally, in the SMS sending process: the Header field in the request message MESSAGE does not contain the "In-Reply-To" parameter, and the trigger condition of "SMS semi-stop SiFC" is not met. The S-CSCF network element does not trigger the IP SMS gateway, so the first terminal cannot send a text message.

[0136] In the SMS receiving process: the Header field in the receipt message MESSAGE contains the "In-Reply-To" parameter, which meets the triggering condition of "SMS semi-stop SiFC". The S-CSCF network element will trigger the IP SMS gateway, and the SMS receipt message will be successfully sent, which will not cause the SMS center to resend the SMS multiple times, reducing the probability of complaints.

[0137] Optionally, the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC, the target information is the IP SMS gateway host name parameter of the Request URI, and according to the target information, the IP SMS of the first terminal is only received but not sent, including:

[0138] When the SMS sending request includes an SMS message and the Request URI does not include an IP SMS gateway host name parameter, the triggering condition of the SMS calling iFC in the SMS semi-stop SiFC is not met, and the SMS message is stopped from being sent to the second terminal, wherein the SMS message is a message sent from the first terminal to the second terminal in the SMS sending request;

[0139] When the SMS sending request includes an SMS receipt message and the Request URI includes the IP SMS gateway host name parameter, the trigger condition of the SMS caller iFC in the SMS semi-stop SiFC is met, triggering the IP SMS receipt sending operation for the first terminal, wherein the SMS receipt message is a message sent by the first terminal to the IP SMS gateway.

[0140] According to some embodiments, for example, a SiFC can be created, including the SMS registration iFC and the SMS calling iFC, and the host name can be added to the trigger condition "Request-URI" of the calling iFC. By comparing the IP SMS origination MESSAGE message packet and the IP SMS receipt MESSAGE message packet, it is determined that the Request-URI header field of the IP SMS receipt MESSAGE message packet includes the host name of the IP SMS center. Therefore, a new SMS SiFC can be created, including the SMS registration iFC and the SMS calling iFC, and the judgment of the IP SMS gateway host name can be added to the "Request-URI" trigger condition of the calling iFC structure.

[0141] Optionally, in the message received by the S-CSCF, if the Request-URI is a specific IP SMS gateway host name (indicating that this is an SMS receipt message), the trigger condition of the SMS semi-stop SiFC is met, the first terminal can receive IP SMS but cannot send IP SMS, thereby meeting the requirement of controlling IP SMS to only receive but not send.

[0142] For example, after signing the SiFC, that is, obtaining the first contract data of the SiFC, when the first terminal sends a text message, the "Request URI" header field in the text message MESSAGE message is "tel: global format telephone number", so the S-CSCF network element does not trigger the "SMS semi-stop SiFC", and the IP text message of the first terminal cannot be sent. When the first terminal receives a text message, the "Request URI" header field in the text message receipt MESSAGE message is "sip: SMS gateway host name.*", so the S-CSCF network element can trigger the "SMS semi-stop SiFC", the text message receipt message can be returned to the IP text message gateway normally, and the first terminal can receive the IP text message.

[0143] For example, a comparative analysis of the "SMS Initial Send" and "SMS Receipt" message packets sent to the S-CSCF network element shows that the "Request URI" header field of the "SMS Initial Send" message packet is "tel:global format telephone number", while the "Request URI" header field of the "SMS Receipt" is "sip:SMS gateway host name.*". Based on this, by adding the judgment of "Request URI" header field as "sip:SMS gateway host name.*" to the "SMS Caller iFC", the initial SMS and SMS receipt messages can be distinguished, which can improve the accuracy of IP SMS receiving but not sending.

[0144] Optional, Figure 5 A method for creating a SMS semi-stop SiFC in an embodiment of the present disclosure is shown, where a "SMS semi-stop SiFC" is created on an S-CSCF network element, and the configuration includes specific configurations of the SMS calling iFC and the SMS registration iFC (priority, host name, trigger condition (SPT), etc.).

[0145] Optionally, creating a "SMS semi-stop SiFC" on the S-CSCF network element may include, for example:

[0146] Add a trigger condition judgment in the TriggerPoint configuration: judge whether the SIP message header field Request URI of the received MESSAGE message contains the "sip: SMS gateway host name.*" parameter. If it does, the SiFC is triggered. In view of the proposed "SMS caller iFC" requirement for the "Request URI" header field, the configuration method may include:

[0147]

[0148] Optionally, in the SMS sending process: the Request URI in the request message MESSAGE does not include the IP SMS gateway host name, and the triggering condition of "SMS semi-stop SiFC" is not met. The S-CSCF network element does not trigger the IP SMS gateway, so the first terminal cannot send a SMS.

[0149] In the SMS receiving process: the Request URI of the receipt message MESSAGEd contains the IP SMS gateway host name, which meets the triggering condition of "SMS semi-stop SiFC". The S-CSCF network element will trigger the IP SMS gateway, and the IP SMS receipt will be successfully sent, which will not cause the SMS center to resend the SMS multiple times, reducing the probability of complaints.

[0150] Optionally, the SMS semi-stop SiFC includes the SMS registration iFC but does not include the SMS calling iFC, and according to the target information, the IP SMS of the first terminal is only received but not sent, including:

[0151] When the SMS sending request includes an SMS message, stop sending the SMS message to the second terminal, wherein the SMS message is a message sent from the first terminal to the second terminal in the SMS sending request;

[0152] In the case that the SMS sending request includes a SMS receipt message, an IP SMS receipt sending operation is triggered for the first terminal, wherein the SMS receipt message is a message sent by the first terminal to the IP SMS gateway.

[0153] According to some embodiments, for example, a SiFC can be created that only contains the SMS registration iFC but does not contain the SMS caller iFC: for example, when the IP SMS gateway sends a text message, the From header field carries its own host name. After the first terminal receives the text message, it uses the content of the From header field as the Request-URI to send a text message receipt, which can be delivered to the IP SMS gateway without triggering the SMS caller iFC. Based on this, a new SMS SiFC can be created that only contains the SMS registration iFC but does not contain the SMS caller iFC. After the first terminal signs up for the SiFC, it can receive text messages normally. Through the Request-URI in the message sent by the IP SMS gateway, the first terminal's text message receipt can be returned to the IP SMS gateway normally, and the SMS receiving process can end normally. At the same time, due to the lack of the SMS caller iFC, the first terminal cannot send text messages, which meets the communication operator's requirement to control the reception of text messages but not the sending of text messages.

[0154] According to some embodiments, the "SMS half-stop SiFC" triggering condition may include, for example: after signing the SiFC contract, when the first terminal initiates a text message MESSAGE, since the "SMS caller iFC" is not included in the "SMS half-stop SiFC" configuration of the S-CSCF network element, the S-CSCF network element does not trigger the "SMS half-stop SiFC", and the first terminal cannot send the text message; when the first terminal receives the text message, since the "SMS caller iFC" is not included in the "SMS half-stop SiFC" configuration of the S-CSCF network element, the S-CSCF network element does not trigger the "SMS half-stop SiFC", and the first terminal can receive the IP text message, and the text message receipt message is returned by the first network element to the IP text message gateway according to the path of the Request-URI parameter in the text message sent.

[0155] Optionally, the failure of the first terminal to send the IP SMS may be, for example:

[0156] (1) The terminal sends a MESSAGE request to the P-CSCF.

[0157] (2) The P-CSCF forwards the request to the S-CSCF. Since there is no "SMS caller iFC" when the first terminal is registered, the request will not be triggered to the IP SMS gateway.

[0158] (3) The S-CSCF queries the routing data from the called number (SMS center number) to the ENUM network element but fails and enters the external network selection process.

[0159] (4) The default MGCF network element can be selected to be eliminated. However, since the MGCF network element is usually set to not support MESSAGE requests in terms of service policy, it can reply "405 Method Not Allowed" and the IP SMS sending fails.

[0160] Optionally, the SMS semi-stop SiFC includes the SMS registration iFC but does not include the SMS calling iFC. For example, the embodiment of the present disclosure may also provide a control method for receiving but not sending IP SMS executed by the first terminal, including:

[0161] Get the host name of the IP SMS gateway carried in the From header field of the SMS receipt message;

[0162] The From header field is used as the Request-URI, wherein the Request-URI is used to instruct the first network element to send a short message receipt message to the IP short message gateway according to the path corresponding to the Request-URI.

[0163] Optionally, the first terminal successfully receives the IP SMS, for example: In the "SMS Half-Stop SiFC" scenario where the first terminal has signed a contract for this embodiment, the MESSAGE message routing is based on the Request-URI. When the IP SMS gateway sends the SMS, the From header field in the SMS MESSAGE request message carries its own host name. The first terminal uses the content of the From header field as the Request-URI to send the SMS receipt MESSAGE message. The first network element returns to the IP SMS gateway according to the path of the Request-URI parameter, and the IP SMS reception process ends normally. Instead of using the Route header field (containing the FQDN or IP address of the IP SMS gateway) in some embodiments.

[0164] Optional, Figure 6 A method for creating a SMS semi-stop SiFC in an embodiment of the present disclosure is shown. The SMS semi-stop SiFC can be configured on the S-CSCF network element: it does not include "SMS calling iFC" but only includes "SMS registration iFC". The specific configuration is as follows:

[0165]

SMS registration iFC

[0166]

[0167] In step S24, when the second contract data is obtained, the IP SMS sending and receiving function of the first terminal is restored.

[0168] According to some embodiments, the second subscription data may be data for restoring the first terminal to be able to receive IP text messages and send IP text messages. The second in the second subscription data is only used to distinguish the first subscription data.

[0169] According to some embodiments, when the second contract data is obtained, the IP SMS sending and receiving function of the first terminal is restored.

[0170] In some or related embodiments, by restoring the IP SMS sending and receiving function of the first terminal when the second contract data is obtained, a mechanism for restoring the semi-stopped IP SMS can be provided, and whether to restore the sending and receiving function of the IP SMS can be determined according to the second contract data, thereby improving the accuracy of the IP SMS control, reducing the situation where the probability of complaints increases due to inaccurate IP SMS control, and improving the accuracy of the semi-stopped IP SMS and reducing the probability of complaints.

[0171] Figure 7 FIG. 1 is a flow chart of a control method for receiving but not sending IP short messages according to an exemplary embodiment. Figure 7 As shown, the control method for receiving but not sending IP short messages can be used in a control scenario where IP short messages are only received but not sent, and includes the following steps:

[0172] In step S31, a first instruction sent by the business operation support system is received, wherein the first instruction is generated by the business operation support system when receiving a semi-stop request;

[0173] According to some embodiments, the business operation support system may be, for example, a BOSS system. The first of the first instructions is only used to distinguish from other instructions. The first instruction may be generated, for example, when the business operation support system receives a semi-stop request.

[0174] According to some embodiments, the execution subject of the embodiment of the present disclosure may be, for example, a second network element, and the second network element may be, for example, an HSS / UDM network element.

[0175] In some embodiments, the second network element may, for example, receive a first instruction sent by the business operation support system, wherein the first instruction is generated by the business operation support system when it receives a semi-stop request.

[0176] Optionally, the BOSS sends a command to the HSS / UDM network element to cancel the "IP SMS General SiFC", indicating that the 4 / 5G IP SMS function of the first terminal is canceled. "IP SMS General SiFC" is usually signed by the BOSS system to the HSS / UDM network element for the first terminal when the 4 / 5G first terminal opens an account, and the SMS sending and receiving functions are enabled for the first terminal. Canceling the "IP SMS General SiFC" means that when the first terminal is registered in the 4 / 5G network, it does not have the ability to send and receive IP SMS.

[0177] Among them, the trigger conditions are:

[0178] When the 4 / 5G first terminal registers the network, the S-CSCF network element downloads the first terminal's subscription data from the HSS / UDM network element. The S-CSCF network element obtains the specific iFC content from the local database based on the SiFC in the subscription data. Since the first terminal on the HSS / UDM network element has not signed the "SMS Universal SiFC", the S-CSCF network element cannot trigger the process of continuing to register with the IP SMS gateway, so the 4 / 5G first terminal does not have the ability to send and receive IP SMS.

[0179] In step S32, in response to the first instruction, canceling the IP SMS function of the first terminal corresponding to the semi-stop request;

[0180] In some embodiments, when the second network element receives the first instruction, it may cancel the IP SMS function of the first terminal corresponding to the half-stop request in response to the first instruction.

[0181] In step S33, a second instruction sent by the business operation support system is received, and in response to the second instruction, a non-IP SMS sending function of the first terminal is cancelled;

[0182] In some embodiments, the second in the second instruction may be distinguished from other instructions. The second instruction may be used to instruct, for example, to cancel the non-IP SMS sending function of the first terminal.

[0183] According to some embodiments, when the second network element receives the second instruction sent by the business operation support system, it can cancel the non-IP SMS sending function of the first terminal in response to the second instruction.

[0184] Optionally, the BOSS system sends a command to the HSS / UDM network element to set "CS domain SMS sending parameter TS22" = FALSE, indicating that the traditional SMS sending function of the first terminal is cancelled. When the first terminal is attached to 2G, traditional SMS cannot be sent.

[0185] Optional, trigger condition:

[0186] When the first terminal attaches to the 2G network and initiates to send a text message, the end office MSS determines that TS22 is FALSE, and then the end office MSS no longer sends a (traditional) text message to the text message center SMSC.

[0187] Through the above steps S31 to S33, the IP SMS and traditional SMS sending functions of the first terminal can be cancelled, so that the first terminal cannot send SMS.

[0188] In step S34, a third instruction sent by the business operation support system is received, and in response to the third instruction, a non-IP SMS receiving function of the first terminal is restored;

[0189] According to some embodiments, the third in the third instruction may be, for example, distinguished from the other instructions. The second instruction may be, for example, used to instruct to restore the non-IP SMS receiving function of the first terminal.

[0190] In some embodiments, the second network element may, for example, receive a third instruction sent by the business operation support system, and restore the non-IP SMS receiving function of the first terminal in response to the third instruction.

[0191] Optionally, the BOSS system sends a command to the HSS / UDM network element to set "CS domain SMS reception parameter TS21" = TRUE, indicating that the traditional SMS & IP SMS reception functions are enabled. When the first terminal is attached to the 2 / 3 / 4 / 5G network, the first terminal is not restricted from receiving traditional SMS and IP SMS.

[0192] Optional, trigger condition:

[0193] Under the current networking, the first terminal needs to pass the judgment of the SMSC when receiving traditional SMS and IP SMS (the SMSC is the network element node in the traditional 2G network): in the process of the first terminal receiving SMS, the SMSC obtains the ability of the first terminal to receive SMS from the HSS / UDM network element, and checks the CS domain "SMS reception" parameter TS21. If TS21 is TRUE, the SMSC determines that the first terminal has the ability to receive SMS (including traditional SMS and IP SMS), so the SMSC continues to send SMS to the called terminal (CS first terminal) and the IP SMS gateway (4 / 5G first terminal).

[0194] In step S35, the fourth instruction sent by the business operation support system is received, and in response to the fourth instruction, the first terminal is signed for the first contract data of the SMS semi-stop SiFC, wherein the SMS semi-stop SiFC first contract data is used by the first network element to perform a receive-only but not send operation on the IP SMS of the first terminal.

[0195] According to some embodiments, the fourth in the fourth instruction may be, for example, distinguished from other instructions. The fourth instruction may be used, for example, to instruct the first terminal to subscribe to a short message semi-stop SiFC.

[0196] Optionally, the BOSS sends a command to the HSS / UDM network element to sign a "SMS Half-Stop SiFC" contract for the first terminal, indicating that when the first terminal is attached to the 4 / 5G network, it cannot send IP SMS but can receive IP SMS.

[0197] Optionally, although the SMS receiving parameter TS21 is TRUE in step S34, indicating that the network does not restrict the 4 / 5G first terminal from receiving IP SMS; but in steps S31 and S32, since the first terminal has not signed the "SMS Universal SiF C", the first terminal does not have the ability to receive IP SMS in the 4 / 5G network, and therefore it is necessary to sign a SMS semi-stop SiFC contract for the first terminal so that the first terminal has the ability to receive IP SMS.

[0198] In some or related embodiments, by receiving a first instruction sent by a business operation support system, wherein the first instruction is generated by the business operation support system when receiving a semi-stop request; in response to the first instruction, canceling the IP SMS function of the first terminal corresponding to the semi-stop request; receiving a second instruction sent by the business operation support system, and canceling the non-IP SMS sending function of the first terminal in response to the second instruction; receiving a third instruction sent by the business operation support system, and restoring the non-IP SMS receiving function of the first terminal in response to the third instruction; receiving a fourth instruction sent by the business operation support system, and signing a contract for the first terminal for the semi-stop of SMS SiFC first contract data in response to the fourth instruction, wherein the semi-stop of SMS SiFC first contract data is used by the first network element to perform a receive-only but not send operation on the IP SMS of the first terminal. Therefore, a mechanism for semi-stopping of IP SMS can be provided, which can determine whether to perform a receive-only but not send operation on the IP SMS after signing the semi-stop of SMS SiFC, which can improve the accuracy of IP SMS control, reduce the situation where the probability of complaints increases due to the complete cancellation of IP SMS, and improve the accuracy of semi-stopping of IP SMS and reduce the probability of complaints.

[0199] In some related embodiments, the control method for receiving but not sending IP short messages may also include:

[0200] Receiving a fifth instruction sent by the business operation support system, wherein the fifth instruction is generated by the business operation support system when receiving an IP SMS restoration request;

[0201] In response to the fifth instruction, restoring the non-IP SMS sending function of the first terminal;

[0202] receiving a sixth instruction sent by the business operation support system, and restoring the non-IP SMS receiving function of the first terminal in response to the sixth instruction;

[0203] receiving a seventh instruction sent by the business operation support system, and canceling the semi-stop function of the IP SMS of the first terminal in response to the seventh instruction;

[0204] The eighth instruction sent by the business operation support system is received, and the IP short message sending and receiving function of the first terminal is restored in response to the eighth instruction. Therefore, the IP short message sending and receiving function can be restored, the accuracy of the control of the IP short message sending and receiving function can be improved, the convenience of using IP short messages can be improved, and the probability of complaints can be reduced.

[0205] Optionally, the BOSS system may send an instruction to the HSS / UDM network element to set "CS domain SMS sending parameter TS 22 = TRUE", indicating that the traditional SMS sending function of the first terminal is restored. The triggering condition may be, for example:

[0206] When the first terminal attaches to the 2G network and sends a text message, if the end office MSS determines that TS22=TRUE, the end office MSS transparently transmits the first terminal text message (traditional text message) to the text message center SMSC.

[0207] Optionally, the BOSS system sends a command to the HSS / UDM network element to set "CS domain SMS receiving parameter TS21" = TRUE, indicating that the traditional SMS and IP SMS receiving functions are enabled. The triggering condition may be, for example:

[0208] Under the current networking, the first terminal needs to pass the judgment of the SMSC when receiving traditional SMS and IP SMS (the SMSC is the network element node in the traditional 2G network): in the process of the first terminal receiving SMS, the SMSC obtains the ability of the first terminal to receive SMS from the HSS / UDM network element, and checks the CS domain "SMS reception" parameter TS21. If TS21 is TRUE, the SMSC determines that the first terminal has the ability to receive SMS (including traditional SMS and IP SMS), and the SMSC can continue to send SMS to the called terminal (CS first terminal) and the IP SMS gateway (4 / 5G first terminal).

[0209] Optionally, the BOSS system sends a command to the HSS / UDM network element to cancel the "SMS semi-stop SiFC", indicating that the 4 / 5G IP SMS semi-stop function of the first terminal is canceled. The triggering condition may be, for example:

[0210] When the 4 / 5G first terminal registers the network, the S-CSCF network element downloads the first terminal's contract data from the HSS / UDM network element. The S-CSCF network element obtains the specific iFC content from the local database based on the SiFC in the contract data. Since the "SMS Half-Stop SiFC" is not signed on the HSS / UDM network element, the S-CSCF network element cannot trigger the process of continuing to register with the IP SMS gateway. At this time, the 4 / 5G first terminal has completely lost its IP SMS capability.

[0211] Optionally, the BOSS system sends a command to the HSS / UDM network element to sign a contract for "IP SMS Universal SiFC", indicating that the first terminal is restored to be able to send and receive IP SMS normally under 4 / 5G. Usually, when the first terminal opens an account or the operator allows / restores the ability of the first terminal to send and receive SMS, the BOSS system sends a command to the HSS / UDM network element to sign a contract for the SiFC for the first terminal, where the triggering conditions include:

[0212] Trigger condition 1:

[0213] When the 4 / 5G first terminal registers the network, the S-CSCF network element downloads the first terminal's subscription data from the HSS / UDM network element, and the S-CSCF network element obtains the specific iFC content from the local database based on the SiFC in the subscription data. The S-CSCF network element triggers the "Register iFC" in the "SMS General SiFC", and the first terminal can continue to register with the IP SMS gateway.

[0214] Trigger condition 2:

[0215] When the 4 / 5G first terminal initiates a text message, the S-CSCF network element triggers the "Calling iFC" in the "SMS General SiFC", and the S-CSCF network element continues to send the text message to the IP SMS gateway.

[0216] Trigger condition 3:

[0217] When the 4 / 5G first terminal receives the SMS, the S-CSCF network element triggers the "Caller iFC" in the "SMS General SiFC", and the S-CSCF network element returns the SMS receipt to the IP SMS gateway.

[0218] Figure 8 1 is a block diagram of a control device for receiving but not sending IP short messages according to an exemplary embodiment. Figure 8 , the device 800 comprises:

[0219] The request receiving unit 801 is used to receive a text message sending request corresponding to the first terminal when the first contract data of the SMS semi-stop SiFC is obtained, wherein the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC or the SMS semi-stop SiFC includes the SMS registration iFC but does not include the SMS calling iFC, and the SMS semi-stop SiFC first contract data is the data signed by the first terminal and is used to perform a receive-only but not send-only operation on the IP SMS of the first terminal;

[0220] The information acquisition unit 802 is used to acquire the target information of the SMS sending request, wherein the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC, and the target information is the "In-Reply-To" parameter or the IP SMS gateway host name parameter of the Request URI;

[0221] The operation execution unit 803 is used to execute the operation of receiving but not sending IP short messages of the first terminal according to the target information and the triggering condition of the short message semi-stop SiFC.

[0222] According to some embodiments, the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC, the target information is the "In-Reply-To" parameter, and the operation execution unit 803 is used to perform the receiving-only but not sending operation on the IP SMS of the first terminal according to the target information, specifically for:

[0223] When the SMS sending request includes an SMS message and the SIP Header of the SMS message does not include an "In-Reply-To" parameter, the triggering condition of the SMS calling iFC in the SMS semi-stop SiFC is not met, and the sending of the SMS message to the second terminal is stopped, wherein the SMS message is the message sent from the first terminal to the second terminal in the SMS sending request;

[0224] When the SMS sending request includes an SMS receipt message and the SIP Header field of the SMS receipt message includes the "In-Reply-To" parameter, the trigger condition of the SMS caller iFC in the SMS semi-stop SiFC is met, triggering the IP SMS receipt sending operation for the first terminal, wherein the SMS receipt message is a message sent by the first terminal to the IP SMS gateway.

[0225] According to some embodiments, the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC, the target information is the IP SMS gateway host name parameter of the Request URI, and the operation execution unit 803 is used to perform the receiving-only but not sending operation on the IP SMS of the first terminal according to the target information, specifically for:

[0226] When the SMS sending request includes an SMS message and the Request URI does not include an IP SMS gateway host name parameter, the triggering condition of the SMS calling iFC in the SMS semi-stop SiFC is not met, and the SMS message is stopped from being sent to the second terminal, wherein the SMS message is a message sent from the first terminal to the second terminal in the SMS sending request;

[0227] When the SMS sending request includes an SMS receipt message and the Request URI includes the IP SMS gateway host name parameter, the trigger condition of the SMS caller iFC in the SMS semi-stop SiFC is met, triggering the IP SMS receipt sending operation for the first terminal, wherein the SMS receipt message is a message sent by the first terminal to the IP SMS gateway.

[0228] According to some embodiments, the SMS semi-stop SiFC includes the SMS registration iFC but does not include the SMS calling iFC, and the operation execution unit 803 is used to perform the receiving-only but not sending operation on the IP SMS of the first terminal according to the target information, specifically for:

[0229] When the SMS sending request includes an SMS message, stop sending the SMS message to the second terminal, wherein the SMS message is a message sent from the first terminal to the second terminal in the SMS sending request;

[0230] In the case that the SMS sending request includes a SMS receipt message, an IP SMS receipt sending operation is triggered for the first terminal, wherein the SMS receipt message is a message sent by the first terminal to the IP SMS gateway.

[0231] According to some embodiments, the operation execution unit 803 is further specifically configured to:

[0232] When the second contract data is obtained, the IP SMS sending and receiving function of the first terminal is restored.

[0233] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0234] In some or related embodiments, the request receiving unit 801 is used to receive a text message sending request corresponding to the first terminal when the first contract data of the SMS semi-suspended SiFC is obtained; the information obtaining unit 802 is used to obtain the target information of the text message sending request; the operation executing unit 803 is used to perform a receive-only but not send operation on the IP text message of the first terminal according to the target information and the trigger condition of the SMS semi-suspended SiFC. Therefore, a mechanism of IP text message semi-suspended can be provided, and it can be determined whether to perform a receive-only but not send operation on the IP text message according to the target information, which can improve the accuracy of IP text message control, reduce the situation where the probability of complaints increases due to the complete cancellation of IP text messages, and improve the accuracy of IP text message semi-suspended and reduce the probability of complaints.

[0235] Fig. 9 1 is a block diagram of a control device for receiving but not sending IP short messages according to an exemplary embodiment. Fig. 9 , the device 900 comprises:

[0236] A first instruction receiving unit 901 is configured to receive a first instruction sent by the business operation support system, wherein the first instruction is generated by the business operation support system when it receives a semi-stop request;

[0237] A function canceling unit 902, configured to cancel the IP SMS function of the first terminal corresponding to the semi-stop request in response to the first instruction;

[0238] The first instruction receiving unit 901 is further configured to receive a second instruction sent by the business operation support system, and cancel the non-IP SMS sending function of the first terminal in response to the second instruction;

[0239] The first instruction receiving unit 901 is further configured to receive a third instruction sent by the business operation support system, and to restore the non-IP SMS receiving function of the first terminal in response to the third instruction;

[0240] The first instruction receiving unit 901 is also used to receive the fourth instruction sent by the business operation support system, and respond to the fourth instruction to sign a contract for the first terminal with the first contract data of the semi-stop SMS SiFC, wherein the first contract data of the semi-stop SMS SiFC is used by the first network element to perform a receive-only but not send operation on the IP SMS of the first terminal.

[0241] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0242] In some or related embodiments, a first instruction receiving unit 901 is used to receive a first instruction sent by a business operation support system, wherein the first instruction is generated by the business operation support system when it receives a semi-stop request; a function canceling unit 902 is used to cancel the IP SMS function of the first terminal corresponding to the semi-stop request in response to the first instruction; the first instruction receiving unit 901 is also used to receive a second instruction sent by the business operation support system, and cancel the non-IP SMS sending function of the first terminal in response to the second instruction; the first instruction receiving unit 901 is also used to receive a third instruction sent by the business operation support system, and restore the non-IP SMS receiving function of the first terminal in response to the third instruction; the first instruction receiving unit 901 is also used to receive a fourth instruction sent by the business operation support system, and in response to the fourth instruction, sign a contract for the first terminal for the first contract data of the semi-stop SiFC of the SMS, wherein the first contract data of the semi-stop SiFC of the SMS is used by the first network element to perform a receive-only but not send operation on the IP SMS of the first terminal. Therefore, a mechanism for semi-stopping of IP SMS can be provided, which can determine whether to execute the operation of only receiving but not sending IP SMS after signing the SiFC contract for semi-stopping of SMS. This can improve the accuracy of IP SMS control and reduce the situation where the probability of complaints increases due to complete cancellation of IP SMS. This can improve the accuracy of semi-stopping of IP SMS and reduce the probability of complaints.

[0243] Fig.10 1 is a block diagram of a control device for receiving but not sending IP short messages according to an exemplary embodiment. Fig.10 , the device 1000 comprises:

[0244] The second instruction receiving unit 1001 is used to receive a fifth instruction sent by the business operation support system, wherein the fifth instruction is generated by the business operation support system when receiving an IP SMS restoration request;

[0245] The function recovery unit 1002 is used to recover the non-IP short message sending function of the first terminal in response to the fifth instruction;

[0246] The second instruction receiving unit 1001 is further configured to receive a sixth instruction sent by the business operation support system, and to restore the non-IP SMS receiving function of the first terminal in response to the sixth instruction;

[0247] The second instruction receiving unit 1001 is further configured to receive a seventh instruction sent by the business operation support system, and cancel the semi-stop function of the IP SMS of the first terminal in response to the seventh instruction;

[0248] The second instruction receiving unit 1001 is further configured to receive an eighth instruction sent by the business operation support system, and restore the IP short message sending and receiving function of the first terminal in response to the eighth instruction.

[0249] Fig.11 1 is a block diagram of a control device for receiving but not sending IP short messages according to an exemplary embodiment. Fig.11 , the device 1100 comprises:

[0250] A communication system, characterized in that it includes a first terminal 1101, a first network element 1102 and a second network element 1103, wherein the first network element 1102 is configured to implement any of the methods described above, the first terminal 1101 is configured to implement any of the methods described above, and the second network element 1102 is configured to implement any of the methods described above.

[0251] Fig.12 1 is a block diagram of a network side device 1200 provided in an embodiment of the present disclosure. For example, the network side device 1200 may be provided as a network side device. Fig.12 The network side device 1200 includes a processing component 1222, which further includes at least one processor, and a memory resource represented by a memory 1232 for storing instructions executable by the processing component 1222, such as an application. The application stored in the memory 1232 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 1222 is configured to execute instructions to perform any method of the aforementioned method applied to the network side device.

[0252] The network side device 1200 may further include a power supply component 1226 configured to perform power management of the network side device 1200, a wired or wireless network interface 1250 configured to connect the network side device 1200 to a network, and an input / output (I / O) interface 1258. The network side device 1200 may operate based on an operating system stored in the memory 1232, such as Windows Server TM, Mac OS X TM, Unix TM, Linux TM, Free BSD TM or the like.

[0253] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0254] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0255] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0256] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0257] The systems and techniques described herein can be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), the Internet, and a blockchain network.

[0258] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship between the client and the server is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services ("Virtual Private Server", or "VPS" for short). The server may also be a server of a distributed system, or a server combined with a blockchain.

[0259] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved, and this document does not limit this.

[0260] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A control method for receiving but not sending IP short messages, characterized in that: The method is performed by a first network element and includes: In the case of acquiring the first contract data of the SMS semi-stop SiFC, receiving the SMS sending request corresponding to the first terminal, wherein the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC or the SMS semi-stop SiFC includes the SMS registration iFC but does not include the SMS calling iFC, and the SMS semi-stop SiFC first contract data is the data signed by the first terminal and used to perform a receiving-only but not sending operation on the IP SMS of the first terminal; Obtaining the target information of the SMS sending request, wherein when the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC, the target information is the "In-Reply-To" parameter or the IP SMS gateway host name parameter of the Request URI; According to the target information and the triggering condition of the SMS semi-stop SiFC, the IP SMS of the first terminal is only received but not sent.

2. The method according to claim 1, characterized in that in, The SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC, the target information is the "In-Reply-To" parameter, and the receiving-only but not sending operation is performed on the IP SMS of the first terminal according to the target information, including: When the SMS sending request includes an SMS message and the SIP Header of the SMS message does not include the "In-Reply-To" parameter, the triggering condition of the SMS calling iFC in the SMS semi-stop SiFC is not met, and the sending of the SMS message to the second terminal is stopped, wherein the SMS message is the message sent by the first terminal to the second terminal in the SMS sending request; When the SMS sending request includes a SMS receipt message and the SIP Header field of the SMS receipt message includes the "In-Reply-To" parameter, the trigger condition of the SMS caller iFC in the SMS semi-stop SiFC is met, triggering the IP SMS receipt sending operation for the first terminal, wherein the SMS receipt message is a message sent by the first terminal to the IP SMS gateway.

3. The method according to claim 1, characterized in that in, The SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC, the target information is the IP SMS gateway host name parameter of the Request URI, and the receiving-only but not sending operation is performed on the IP SMS of the first terminal according to the target information, including: When the SMS sending request includes an SMS message and the Request URI does not include the IP SMS gateway host name parameter, the triggering condition of the SMS calling iFC in the SMS semi-stop SiFC is not met, and the sending of the SMS message to the second terminal is stopped, wherein the SMS message is the message sent by the first terminal to the second terminal in the SMS sending request; When the SMS sending request includes an SMS receipt message and the Request URI includes the IP SMS gateway host name parameter, the trigger condition of the SMS caller iFC in the SMS semi-stop SiFC is met, triggering the IP SMS receipt sending operation for the first terminal, wherein the SMS receipt message is a message sent by the first terminal to the IP SMS gateway.

4. The method according to claim 1, characterized in that: in, The SMS semi-stop SiFC includes the SMS registration iFC but does not include the SMS calling iFC, and the receiving-only but not sending operation is performed on the IP SMS of the first terminal according to the target information, including: In a case where the SMS sending request includes an SMS message, stopping sending the SMS message to the second terminal, wherein the SMS message is a message sent from the first terminal to the second terminal in the SMS sending request; In the case that the SMS sending request includes a SMS receipt message, an IP SMS receipt sending operation is triggered for the first terminal, wherein the SMS receipt message is a message sent by the first terminal to the IP SMS gateway.

5. The method according to claim 1, characterized in that The method further comprises: When the second contract data is obtained, the IP SMS sending and receiving function of the first terminal is restored.

6. A control method for receiving but not sending IP short messages, characterized in that: The method is executed by the first terminal, wherein the SMS semi-stop SiFC includes the SMS registration iFC and does not include the SMS calling iFC, and the method includes: Get the host name of the IP SMS gateway carried in the From header field of the SMS receipt message; The From header field is used as the Request-URI, wherein the Request-URI is used to instruct the first network element to send the SMS receipt message to the IP SMS gateway according to the path corresponding to the Request-URI.

7. A control method for receiving but not sending IP short messages, characterized in that: The method is performed by a second network element, and includes: Receiving a first instruction sent by a business operation support system, wherein the first instruction is generated by the business operation support system when it receives a semi-stop request; In response to the first instruction, canceling the IP SMS function of the first terminal corresponding to the half-stop request; receiving a second instruction sent by the business operation support system, and canceling the non-IP SMS sending function of the first terminal in response to the second instruction; receiving a third instruction sent by the business operation support system, and restoring the non-IP SMS receiving function of the first terminal in response to the third instruction; Receive the fourth instruction sent by the business operation support system, and in response to the fourth instruction, sign a contract for the first terminal for the first contract data of the half-stop SMS SiFC, wherein the first contract data of the half-stop SMS SiFC is used by the first network element to perform a receive-only but not send operation on the IP SMS of the first terminal.

8. A control method for receiving but not sending IP short messages, characterized in that: The method is performed by a second network element, and includes: Receiving a fifth instruction sent by the business operation support system, wherein the fifth instruction is generated by the business operation support system when it receives an IP SMS restoration request; In response to the fifth instruction, restoring the non-IP SMS sending function of the first terminal; receiving a sixth instruction sent by the business operation support system, and restoring the non-IP SMS receiving function of the first terminal in response to the sixth instruction; receiving a seventh instruction sent by the business operation support system, and canceling the semi-stop function of the IP SMS of the first terminal in response to the seventh instruction; An eighth instruction sent by the business operation support system is received, and in response to the eighth instruction, an IP short message sending and receiving function of the first terminal is restored.

9. A control device for receiving but not sending IP short messages, characterized in that: include: a request receiving unit, configured to receive a text message sending request corresponding to the first terminal when obtaining first contract data of a half-stop SMS SiFC, wherein the half-stop SMS SiFC includes a text message registration iFC and a text message calling iFC or the half-stop SMS SiFC includes a text message registration iFC but does not include a text message calling iFC, and the first contract data of the half-stop SMS SiFC is data signed by the first terminal and used to perform a receive-only but not send operation on an IP text message of the first terminal; An information acquisition unit, used to acquire the target information of the SMS sending request, wherein when the SMS semi-stop SiFC includes the SMS registration iFC and the SMS calling iFC, the target information is the "In-Reply-To" parameter or the IP SMS gateway host name parameter of the Request URI; The operation execution unit is used to execute the operation of receiving but not sending IP short messages of the first terminal according to the target information and the triggering condition of the short message semi-stop SiFC.

10. A communication system, characterized in that: The method comprises a first terminal, a first network element and a second network element, wherein the first network element is configured to implement the method according to any one of claims 1 to 5, the first terminal is configured to implement the method according to claim 6, and the second network element is configured to implement the method according to any one of claims 7 or 8.

Images