A short message receiving and sending method and related device

Abstract

The present application discloses a short message receiving and sending method and related devices, which relate to the field of short message service control technology, including: obtaining target contract data of a user device, obtaining real scene information of the user device when receiving a target short message, and determining whether to send the target short message to a target network element according to the real scene information and the scene range contained in the target contract data. The present application can control the SMS service more finely based on the real scene information of the user device, thereby improving the user experience of using the SMS service.

Description

Technical Field

[0001] The present application relates to the technical field of short message service control, and in particular to a short message sending and receiving method and related devices. Background Art

[0002] Short Message Service (SMS) is a technology for sending and receiving text messages through mobile phone networks. It is widely used in personal communication, commercial marketing, customer service, security verification, and emergency notification.

[0003] A current short message sending and receiving method is based on the short message service function (Short Message Service Function, SMSF) to send and receive short messages between user equipment (User Equipment, UE) and short message service center (Short Message Service Center, SMSC). However, the granularity of SMSF's control over SMS services is based on the user as a whole and whether the user is in a roaming state, that is, it can only prohibit all short message sending and receiving or prohibit the user from sending and receiving short messages when roaming, which cannot meet the user's requirements for more precise control of SMS services. Summary of the invention

[0004] In view of the above problems, the present application provides a short message sending and receiving method and related devices to achieve the purpose of more finely controlling the SMS service based on the scene information corresponding to the target short message. The specific scheme is as follows:

[0005] The first aspect of the present application provides a short message sending and receiving method, comprising:

[0006] Acquire target subscription data of a user equipment, wherein the target subscription data includes a scenario range in which the user equipment is prohibited and / or allowed to use a short message service;

[0007] When receiving the target short message, obtaining the real scene information of the user equipment;

[0008] According to the real scenario information and the scenario range included in the target subscription data, it is determined whether to send the target short message to the target network element.

[0009] Optionally, the real scene information includes location information of the user equipment, and the scene range includes at least one area;

[0010] Before acquiring the real scene information of the user equipment, the method further includes:

[0011] Calling the location subscription service interface provided by the access and mobility management network element to subscribe to the location information of the user equipment from the access and mobility management network element, wherein the access and mobility management network element actively reports the changed location information to the SMS service network element when the location information of the user equipment changes.

[0012] Optionally, each of the at least one area is an area indicated by a tracking area identifier, or an area jointly indicated by the tracking area identifier and a next generation cell global identifier.

[0013] Optionally, the real scene information includes time information, and the scene range includes at least one time period.

[0014] Optionally, determining whether to send the target short message to the target network element according to the real scenario information and the scenario range included in the target subscription data includes:

[0015] In the case where the target subscription data includes a scenario range in which the user equipment is prohibited from using a short message service, if the real scenario information falls within the scenario range in which the user equipment is prohibited from using a short message service, the target short message is not sent to the target network element; if the real scenario information does not fall within the scenario range in which the user equipment is prohibited from using a short message service, the target short message is sent to the target network element;

[0016] and / or,

[0017] In a case where the target subscription data includes a scope of scenarios in which the user equipment is allowed to use the short message service, if the actual scenario information does not fall within the scope of scenarios in which the user equipment is allowed to use the short message service, the target short message will not be sent to the target network element; if the actual scenario information falls within the scope of scenarios in which the user equipment is allowed to use the short message service, the target short message will be sent to the target network element.

[0018] Optionally, if the target short message is a short message generated by the user equipment, the target network element is a short message service center; if the target short message is a short message generated by the short message service center, the target network element is the user equipment.

[0019] A second aspect of the present application provides a short message sending and receiving device, comprising:

[0020] A first acquisition module, configured to acquire target subscription data of a user equipment, wherein the target subscription data includes a scenario range in which the user equipment is prohibited and / or allowed to use a short message service;

[0021] A second acquisition module, configured to acquire real scene information of the user equipment when receiving a target short message;

[0022] The short message management module is used to determine whether to send the target short message to the target network element according to the real scene information and the scene range included in the target contract data.

[0023] The third aspect of the present application provides a computer program product, including computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements the short message sending and receiving method of the first aspect or any implementation manner of the first aspect.

[0024] A fourth aspect of the present application provides an electronic device, comprising at least one processor and a memory connected to the processor, wherein:

[0025] The memory is used to store computer programs;

[0026] The processor is used to execute the computer program so that the electronic device can implement the short message sending and receiving method of the first aspect or any implementation manner of the first aspect.

[0027] In a fifth aspect, the present application provides a computer storage medium, which carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement the short message sending and receiving method of the first aspect or any implementation method of the first aspect.

[0028] By means of the above technical solution, the short message sending and receiving method provided by the present application can set the scene range of prohibiting and / or allowing the use of the short message service related to the real scene information of the user equipment into the target contract data, so that each time the target short message is received, it can be determined whether to send the target short message to the target network element according to the real scene information and the scene range contained in the target contract data. It can be seen that the present application can control the SMS service more finely based on the real scene information of the user equipment, thereby improving the user experience of using the SMS service. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale.

[0030] Figure 1 A schematic diagram of a system architecture provided for this application;

[0031] Figure 2A schematic diagram of an optional hardware structure of the terminal 100 provided in this application;

[0032] Figure 3 A schematic diagram of the structure of a server 200 provided in this application;

[0033] Figure 4 A flowchart of a method for sending and receiving short messages provided in this application;

[0034] Figure 5 A flowchart of another short message sending and receiving method provided by this application;

[0035] Figure 6 A schematic diagram of the control flow after the SMSF provided by the present application receives an uplink target short message;

[0036] Figure 7 A schematic diagram of the control flow after the SMSF provided by the present application receives a downlink target short message;

[0037] Figure 8 A schematic diagram of the structure of a short message receiving and sending device provided by the present application;

[0038] Fig. 9 A schematic diagram of the structure of an electronic device provided in this application. DETAILED DESCRIPTION

[0039] The following describes the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. The terms used in the implementation method section of the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application.

[0040] The embodiments of the present application are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0041] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and need not be used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, which is only to describe the distinction mode adopted by the objects of the same attributes when describing in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0042] As a basic service in the communications industry, SMS has undergone a transformation from the circuit switching domain of the 2G / 3G era to the packet switching domain of the 4G era in the process of technological evolution. With the advent of the 5G era, there are two main technical solutions for the implementation of short message services: SMS over NAS and SMS over IP. Among them, the SMS over IP solution uses the existing IMS (IP Multimedia Subsystem) architecture to send and receive short messages; while the SMS over NAS technology uses the NAS (Network Attached Storage) signaling channel to send and receive short messages.

[0043] The above-mentioned SMS over NAS technology breaks the dependence on IMS, allowing user devices to smoothly communicate short messages in the 5G network even when IMS services are unavailable.

[0044] However, as introduced in the background technology, in SMS over NAS technology, the granularity of SMSF's control over SMS services is based on the user as a whole and whether the user is in roaming status, that is, it can only prohibit all sending and receiving of short messages or prohibit the user from sending and receiving short messages when roaming, which cannot meet the user's requirements for more precise control of SMS services.

[0045] In order to achieve the purpose of more finely controlling the SMS service based on the scenario information corresponding to the target short message, the present application provides a short message sending and receiving method and a related device. In order to enable those skilled in the art to better understand the present application, the following embodiments are described in detail.

[0046] See also Figure 1 , Figure 1 A schematic diagram of a system architecture is shown. The system may include a terminal 100 and a server 200. The server 200 may include one or more servers ( Figure 1 In the example, a server is included, and the server 200 can provide the method provided in the embodiment of the present application for one or more terminals.

[0047] Among them, an application can be installed on the terminal 100, and the above application and web page can provide an interface. The terminal 100 can receive relevant parameters entered by the user on the interface and send the above parameters to the server 200. The server 200 can obtain processing results based on the received parameters and return the processing results to the terminal 100.

[0048] It should be understood that in some optional implementations, the terminal 100 can also complete the action of obtaining the processing result based on the received parameters by itself without the cooperation of the server, and the embodiments of the present application are not limited to this.

[0049] Next describe Figure 1 The product form of the mid-terminal 100;

[0050] The terminal 100 in the embodiment of the present application can be a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), etc., and the embodiment of the present application does not impose any restrictions on this.

[0051] Figure 2 An optional hardware structure diagram of the terminal 100 is shown.

[0052] refer to Figure 2 As shown, the terminal 100 may include a radio frequency unit 110, a memory 120, an input unit 130, a display unit 140, a camera 150 (optional), an audio circuit 160 (optional), a speaker 161 (optional), a microphone 162 (optional), an earphone jack 163 (optional), a processor 170, an external interface 180, a power supply 190 and other components. Those skilled in the art will appreciate that Figure 2 These are merely examples of terminals or multi-function devices and do not constitute limitations on the terminals or multi-function devices, which may include more or fewer components than those shown in the figures, or combinations of certain components, or different components.

[0053] The input unit 130 can be used to receive input digital or character information, and generate key signal input related to the user settings and function control of the portable multifunctional device. Specifically, the input unit 130 may include a touch screen 131 (optional) and / or other input devices 132. The touch screen 131 can collect the user's touch operations on or near it (such as the user's operation on or near the touch screen using any suitable object such as fingers, joints, stylus, etc.), and drive the corresponding connection device according to a pre-set program. The touch screen can detect the user's touch action on the touch screen, convert the touch action into a touch signal and send it to the processor 170, and can receive and execute the command sent by the processor 170; the touch signal at least includes the touch point coordinate information. The touch screen 131 can provide an input interface and an output interface between the terminal 100 and the user. In addition, the touch screen can be implemented using multiple types such as resistive, capacitive, infrared and surface acoustic wave. In addition to the touch screen 131, the input unit 130 can also include other input devices. Specifically, other input devices 132 may include, but are not limited to, one or more of a physical keyboard, function keys (such as a volume control key, a switch key, etc.), a trackball, a mouse, a joystick, and the like.

[0054] Among them, the input device 132 can receive input data and the like.

[0055] The display unit 140 may be used to display information input by a user or provided to a user, various menus of the terminal 100, an interactive interface, file display, and / or playback of any multimedia file.

[0056] The memory 120 can be used to store instructions and data. The memory 120 can mainly include an instruction storage area and a data storage area. The data storage area can store various data, such as multimedia files, texts, etc.; the instruction storage area can store software units such as operating systems, applications, instructions required for at least one function, or their subsets and extensions. It can also include a non-volatile random access memory; provide the processor 170 with hardware, software and data resources including management of computing and processing equipment, and support control software and applications. It is also used for the storage of multimedia files, and the storage of running programs and applications.

[0057] The processor 170 is the control center of the terminal 100. It uses various interfaces and lines to connect various parts of the entire terminal 100. By running or executing instructions stored in the memory 120 and calling data stored in the memory 120, it executes various functions of the terminal 100 and processes data, thereby controlling the terminal device as a whole. Optionally, the processor 170 may include one or more processing units; preferably, the processor 170 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface and application program, and the modem processor mainly processes wireless communication. It is understandable that the above-mentioned modem processor may not be integrated into the processor 170. In some embodiments, the processor and the memory may be implemented on a single chip, and in some embodiments, they may also be implemented separately on separate chips. The processor 170 may also be used to generate corresponding operation control signals, send them to corresponding components of the computing and processing device, read and process data in the software, especially read and process data and programs in the memory 120, so that each functional module therein performs corresponding functions, thereby controlling the corresponding components to act according to the requirements of the instructions.

[0058] The memory 120 may be used to store software codes related to the short message sending and receiving method, the processor 170 may execute the steps of the short message sending and receiving method, and may also schedule other units (such as the above-mentioned input unit 130 and display unit 140) to implement corresponding functions.

[0059] The radio frequency unit 110 (optional) can be used for receiving and sending information or receiving and sending signals during a call, for example, after receiving the downlink information of the base station, it is sent to the processor 170 for processing; in addition, the designed uplink data is sent to the base station. Generally, the RF circuit includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (Low Noise Amplifier, LNA), a duplexer, etc. In addition, the radio frequency unit 110 can also communicate with network devices and other devices through wireless communication. The wireless communication can use any communication standard or protocol, including but not limited to Global System of Mobile Communication (Global System of Mobile Communication, GSM), General Packet Radio Service (General Packet Radio Service, GPRS), Code Division Multiple Access (Code Division Multiple Access, CDMA), Wideband Code Division Multiple Access (Wideband Code Division Multiple Access, WCDMA), Long Term Evolution (Long Term Evolution, LTE), email, Short Messaging Service (SMS), etc.

[0060] In this embodiment of the present application, the RF unit 110 can send data to the server 200 and receive processing results sent by the server 200.

[0061] It should be understood that the radio frequency unit 110 is optional and can be replaced by other communication interfaces, such as a network port.

[0062] The terminal 100 also includes a power supply 190 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 170 through a power management system, so that the power management system can manage functions such as charging, discharging, and power consumption.

[0063] The terminal 100 further includes an external interface 180 , which may be a standard Micro USB interface or a multi-pin connector, and may be used to connect the terminal 100 to communicate with other devices, or to connect a charger to charge the terminal 100 .

[0064] Although not shown, the terminal 100 may also include a flashlight, a wireless fidelity (WiFi) module, a Bluetooth module, sensors with different functions, etc., which are not described in detail here. Some or all of the methods described below may be applied in the following embodiments. Figure 2 In the terminal 100 shown.

[0065] Next describe Figure 1 The product form of the server 200;

[0066] Figure 3 A structural diagram of a server 200 is provided, such as Figure 3 As shown, the server 200 includes a bus 201, a processor 202, a communication interface 203, and a memory 204. The processor 202, the memory 204, and the communication interface 203 communicate with each other via the bus 201.

[0067] The bus 201 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0068] The processor 202 may be any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0069] The memory 204 may include a volatile memory, such as a random access memory (RAM). The memory 204 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid state drive (SSD).

[0070] The memory 204 may be used to store software codes related to the short message receiving and sending method, and the processor 202 may execute the steps of the short message receiving and sending method of the chip, and may also schedule other units to implement corresponding functions.

[0071] It should be understood that the above-mentioned terminal 100 and server 200 can be centralized or distributed devices, and the processors in the above-mentioned terminal 100 and server 200 (such as processor 170 and processor 202) can be hardware circuits (such as application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), general-purpose processors, DSPs, microprocessors or microcontrollers, etc.), or a combination of these hardware circuits. For example, the processor can be a hardware system with an instruction execution function, such as a CPU, DSP, etc., or a hardware system without an instruction execution function, such as an ASIC, FPGA, etc., or a combination of the above-mentioned hardware systems without an instruction execution function and hardware systems with an instruction execution function.

[0072] The present application provides a short message sending and receiving method, which can be applied to SMSF. In the SMSover NAS technology, SMSF is mainly used to complete short message contract data inspection, message forwarding, short message routing between UE and SMSC, short message billing and legal interception, etc. The short message sending and receiving method of the embodiment of the present application is described in detail below with reference to the accompanying drawings.

[0073] Reference Figure 4 , Figure 4 A flow chart of a method for sending and receiving short messages provided in an embodiment of the present application, the method may include:

[0074] Step S401: Acquire target subscription data of a user equipment, wherein the target subscription data includes a range of scenarios in which the user equipment is prohibited and / or allowed to use the short message service.

[0075] Here, the target subscription data is stored in the Unified Data Management (UDM) network element.

[0076] In this embodiment, the user equipment UE can send a registration request to the access and mobility management network element (Access and MobilityManagement Function, AMF). After receiving the registration request, the AMF will determine whether to call the short message activation service interface (i.e., Nsmsf_SMService_Activate service interface) provided by the SMSF to request activation of the UE's ability to send and receive short messages based on the UE's target subscription data and the UE's capabilities. If the UE's ability to send and receive short messages is allowed to be activated, the AMF will set the 5G system registration result (i.e., 5GS registration result) in the registration acceptance message to 1, indicating that the UE is allowed to use the SMS service; if the UE's ability to send and receive short messages is not allowed to be activated, the AMF will set the 5G system registration result in the registration acceptance message to 0, indicating that the UE is not allowed to use the SMS service.

[0077] In the above process of activating the ability of UE to send and receive short messages, SMSF can obtain the target subscription data from UDM and save it. In addition, SMSF can also subscribe to the target subscription data of the user equipment, so that when the target subscription data changes, UDM can promptly notify SMSF of the change so that SMSF can save the latest target subscription data.

[0078] In this embodiment, the target subscription data includes at least one of the following data: a scenario range in which the user equipment is prohibited from using the short message service, and a scenario range in which the user equipment is allowed to use the short message service.

[0079] That is, the target contract data specifies the scenarios within which users can use the short message service. Therefore, by updating the target contract data in the UDM, the purpose of finely controlling the SMS service according to user needs can be achieved.

[0080] Step S402: upon receiving the target short message, obtaining the real scene information of the user equipment.

[0081] In SMS over NAS technology, the short message sending path includes an upstream short message (Mobile Originated SMS, MO-SMS) sending path and a downstream short message (Mobile Terminated SMS, MT-SMS) sending path. The upstream short message sending path is: the user equipment UE encapsulates the short message (for the convenience of subsequent description, this application defines the short message as the target short message, the same below) in NAS signaling and sends it to the access and mobility management network element (Access and Mobility Management Function, AMF), AMF decodes and forwards the target short message to the short message service network element SMSF, SMSF then forwards the target short message to SMSC, the downstream short message sending path is: SMSC sends the target short message to SMSF, SMSF sends the target short message to AMF, AMF then encapsulates the target short message in NAS signaling and sends it to UE.

[0082] In this embodiment, no matter it is an upstream short message sending path or a downstream short message sending path, the target short message needs to be sent to the short message service network element SMSF, and then the SMSF can receive the target short message.

[0083] In this embodiment, when receiving the target short message, the SMSF can obtain the real scene information of the user device, so as to control the SMS service more finely through the real scene information. In this embodiment, the specific form of the real scene information is set according to the user's control requirements for the SMS service, and this application does not specifically limit it.

[0084] For example, in some scenarios, the user needs to achieve more precise control of the SMS service in specific occasions, then the real scenario information of the user device may be the location information of the user device, that is, the location information of the user device when sending or receiving the target short message; for another example, in other scenarios, the user needs to achieve more precise control of the SMS service at a specific time, then the real scenario information of the user device may be the time information when the user device sends or receives the target short message (that is, the current time of sending or receiving the short message).

[0085] Step S403: Determine whether to send the target short message to the target network element according to the real scenario information and the scenario range included in the target subscription data.

[0086] Further to the above introduction, the target subscription data includes a scenario range for prohibiting and / or allowing the user equipment to use the short message service. Optionally, if the above-mentioned real scenario information includes the location information of the user equipment, the scenario range includes at least one area; optionally, the above-mentioned at least one area may exist in the form of a list, and each area in the list may be an area indicated by a tracking area identity (TAI), or may be an area jointly indicated by a tracking area identity TAI and a next generation cell global identity (NCGI).

[0087] Optionally, if the real scene information includes time information, the scene range includes at least one time period, wherein each time period includes a start time and an end time, for example, the start time is 2024-07-31 00:00 and the end time is 2024-07-31 6:00.

[0088] This application can determine whether the actual scenario information falls within the scenario range included in the target contract data, and determine whether to send the target short message to the target network element based on the judgment result.

[0089] If the target short message is a short message generated by a user equipment UE, the target network element is a short message service center SMSC; if the target short message is a short message generated by an SMSC, the target network element is the user equipment.

[0090] The short message sending and receiving method provided by the present application can set the scene range of prohibiting and / or allowing the use of the short message service related to the real scene information of the user equipment into the target contract data, so that each time the target short message is received, it can be determined whether to send the target short message to the target network element according to the real scene information and the scene range contained in the target contract data. It can be seen that the present application can control the SMS service more finely based on the real scene information of the user equipment, thereby improving the user experience of using the SMS service.

[0091] The following embodiment provides another method for sending and receiving short messages.

[0092] See also Figure 5 As shown, it is a flow chart of another short message receiving and sending method provided in an embodiment of the present application, such as Figure 5 As shown, the method may include:

[0093] Step S501: Acquire subscription data of a user device.

[0094] Step S502: upon receiving the target short message, obtaining the real scene information of the user equipment.

[0095] Step S503: If the target contract data contains a range of scenarios in which the user device is prohibited from using the short message service, determine whether the actual scenario information falls within the range of scenarios in which the user device is prohibited from using the short message service. If so, execute step S506; if not, execute step S505.

[0096] Step S504: If the target contract data contains the scope of scenarios that allow the user device to use the short message service, determine whether the actual scenario information falls within the scope of the user device using the short message service. If so, execute step S505; if not, execute step S506.

[0097] Step S505: Send the target short message to the target network element.

[0098] Step S506: Do not send the target short message to the target network element.

[0099] By flexibly setting the scope of scenarios for allowing / forbidding the user equipment to use the short message service in the target subscription data, the user can control the SMS service more finely based on his or her own requirements, thereby improving the user's experience in using the SMS service.

[0100] As described above, the target subscription data includes at least one of a scenario range in which the user equipment UE is prohibited from using the short message service and a scenario range in which the user equipment UE is allowed to use the short message service, and the above scenario range may include at least one area and / or at least one time period.

[0101] It should be noted that for each type included in the scenario range (for example, at least one area and at least one time period are two types), only one of the scenario range that prohibits user equipment UE from using the short message service and the scenario range that allows user equipment UE to use the short message service can be signed.

[0102] See Tables 1 to 4 below for four optional target signing data provided in this embodiment.

[0103] Table 1 The first type of target contract data

[0104]

[0105] In the scenario range shown in Table 1, as long as the location information of the user device is in the SMS prohibited area when sending or receiving the target short message, or the time information when the user device sends or receives the target short message is in the SMS prohibited time, the target short message will not be sent to the target network element; only when the location information of the user device is not in the SMS prohibited area and the time information when the user device sends or receives the target short message is not in the SMS prohibited time, the target short message will be sent to the target network element.

[0106] In order to enable those skilled in the art to better understand the present application, taking the target subscription data shown in Table 1 as an example, an optional process of controlling the SMS service of the present application is introduced in detail.

[0107] See also Figure 6 FIG. 4 is a schematic diagram of the control flow after the SMSF receives an uplink target short message.

[0108] Step S601: SMSF obtains the target subscription data of UE.

[0109] Step S602: When receiving the target short message from the UE, the SMSF obtains the location information and time information of the UE.

[0110] Step S603: The SMSF determines whether the location information of the UE is within the SMS prohibited area. If so, execute step S606; if not, execute step S604.

[0111] Optionally, in this application, the location information of the UE can be obtained by subscribing to the access and mobility management network element AMF, that is, before the SMSF obtains the real scene information, the SMSF can call the location subscription service interface (i.e., Namf_EventExposure service interface) provided by the access and mobility management network element AMF to subscribe to the location information of the user device from the AMF. After subscribing to the location information of the user device, the AMF can actively report the changed location information to the SMSF when the location information of the user device changes. As a result, the SMSF can promptly determine the current location information of the user device when receiving the target short message.

[0112] Step S604, the SMSF determines whether the time information is within the SMS prohibited time, if so, executes step S606, if not, executes step S605.

[0113] In this embodiment, the execution order of the above step S603 and step S604 can be interchanged.

[0114] Step S605: forward the target short message to the SMSC.

[0115] Step S606: Do not forward the target short message.

[0116] That is, after SMSF receives the uplink target short message forwarded by AMF, it checks the SMS prohibited area and SMS prohibited time in the target contract data according to the current location information and current time of the user equipment. Only when it is not within the SMS prohibited time and the SMS prohibited area, it forwards the uplink target short message to SMSC. Otherwise, it does not forward the uplink target short message.

[0117] See also Figure 7, which is a schematic diagram of the control flow after the SMSF receives the downlink target short message.

[0118] Step S701: SMSF obtains the target subscription data of UE.

[0119] Step S702: When receiving the target short message from the SMSC, the SMSF obtains the location information and time information of the UE.

[0120] Step S703: The SMSF determines whether the location information of the UE is within the SMS prohibited area. If so, execute step S706; if not, execute step S704.

[0121] Step S704, the SMSF determines whether the generation time information of the target short message is within the SMS prohibited time, if so, executes step S706, if not, executes step S705.

[0122] In this embodiment, the execution order of the above step S704 and step S703 can be interchanged.

[0123] Step S705: forward the target short message to the UE.

[0124] Step S706: Do not forward the target short message.

[0125] That is, after SMSF receives the downlink target short message forwarded by SMSC, it checks the SMS prohibited area and SMS prohibited time in the target contract data according to the current location information and current time of the user equipment. Only when it is not within the SMS prohibited time and the SMS prohibited area, the downlink target short message is forwarded to the UE through AMF. Otherwise, the downlink target short message is not forwarded.

[0126] Table 2 The second target contract data

[0127]

[0128] In the scenario range shown in Table 2, when sending or receiving a target short message, if the location information of the user device is in an SMS prohibited area, the target short message will not be sent to the target network element regardless of whether the time information when the user device sends or receives the target short message is in an SMS allowed time; if the location information of the user device is not in an SMS prohibited area, the target short message will be sent to the target network element when the time information when the user device sends or receives the target short message is in an SMS allowed time, and will not be sent to the target network element when the time information when the user device sends or receives the target short message is not in an SMS allowed time.

[0129] Table 3 The third target contract data

[0130]

[0131] In the scenario range shown in Table 3, when sending and receiving the target short message, if the time information when the user equipment sends and receives the target short message is in the SMS prohibited time, the target short message will not be sent to the target network element regardless of whether the location information of the user equipment is in the SMS allowed area; if the time information when the user equipment sends and receives the target short message is not in the SMS prohibited time, the target short message will be sent to the target network element when the location information of the user equipment is in the SMS allowed area, and will not be sent to the target network element when the location information of the user equipment is not in the SMS allowed area.

[0132] Table 4 The fourth target contract data

[0133]

[0134] In the scenario range shown in Table 4, when sending and receiving the target short message, if the location information of the user equipment is in the SMS allowed area, and the time information when the user equipment sends and receives the target short message is in the SMS allowed time, the target short message is sent to the target network element; if the location information of the user equipment is not in the SMS prohibited area, or the time information when the user equipment sends and receives the target short message is not in the SMS allowed time, the target short message is not sent to the target network element.

[0135] It can be seen that the embodiment of the present application provides a method for more finely controlling the NAS short message service, which can prohibit or allow the UE to use the SMS service in a specified area or time period according to actual needs, thereby improving the user experience of using the SMS service.

[0136] The following introduces several optional usage scenarios of this application.

[0137] Scenario 1: For some reason, it is necessary to restrict a person who has lost his credibility from using the short message service during the period of losing his credibility. In this case, the SMS prohibition time can be set as the period of losing credibility in the target contract data of the person who has lost his credibility. In this case, the person who has lost his credibility cannot use the short message service during the period of losing his credibility.

[0138] Scenario 2: For information security reasons, it is necessary to restrict the use of short message services by all people in area A. In this case, the SMS prohibited area can be set as area A in the target contract data. In this case, all people in area A cannot use the short message service.

[0139] In addition to the usage scenarios listed above, the present application can also be applied to other scenarios, which are not specifically limited here.

[0140] A method for sending and receiving short messages provided in an embodiment of the present application is introduced above, and a device for executing the above method for sending and receiving short messages will be introduced below.

[0141] See also Figure 8 , Figure 8 The structure diagram of a short message receiving and sending device provided in an embodiment of the present application is shown in FIG. Figure 8 As shown, the device may include:

[0142] The first acquisition module 801 is used to acquire target subscription data of a user equipment, wherein the target subscription data includes a scenario range in which the user equipment is prohibited and / or allowed to use the short message service;

[0143] The second acquisition module 802 is used to acquire the real scene information of the user equipment when receiving the target short message;

[0144] The short message management module 803 is used to determine whether to send the target short message to the target network element according to the real scene information and the scene range included in the target contract data.

[0145] In a possible implementation, the real scene information includes location information of a user device, and the scene range includes at least one area.

[0146] In this implementation, the short message sending and receiving device provided by the present application may also include a location subscription module.

[0147] The location subscription module is used to call the location subscription service interface provided by the access and mobility management network element to subscribe the location information of the user equipment to the access and mobility management network element before obtaining the real scene information of the user equipment. When the location information of the user equipment changes, the access and mobility management network element actively reports the changed location information to the SMS service network element.

[0148] In a possible implementation, each area of ​​the at least one area is an area indicated by a tracking area identifier, or an area indicated by both a tracking area identifier and a next generation cell global identifier.

[0149] In a possible implementation, the real scene information includes time information, and the scene range includes at least one time period.

[0150] In a possible implementation, when the short message management module determines whether to send the target short message to the target network element according to the real scenario information and the scenario range included in the target contract data, it can be specifically used to:

[0151] In the case where the target subscription data includes a scenario range in which the user equipment is prohibited from using the short message service, if the actual scenario information falls within the scenario range in which the user equipment is prohibited from using the short message service, the target short message is not sent to the target network element; if the actual scenario information does not fall within the scenario range in which the user equipment is prohibited from using the short message service, the target short message is sent to the target network element;

[0152] and / or,

[0153] When the target contract data includes the scenario range that allows the user equipment to use the short message service, if the actual scenario information does not fall within the scenario range that allows the user equipment to use the short message service, the target short message will not be sent to the target network element; if the actual scenario information falls within the scenario range that allows the user equipment to use the short message service, the target short message will be sent to the target network element.

[0154] In a possible implementation, if the target short message is a short message generated by the user equipment, the target network element is a short message service center; if the target short message is a short message generated by the short message service center, the target network element is the user equipment.

[0155] The present application also provides an electronic device in an embodiment. Fig. 9 As shown, it shows a schematic diagram of the structure of an electronic device suitable for implementing the embodiment of the present application. The electronic device in the embodiment of the present application may include but is not limited to fixed terminals such as mobile phones, laptops, PDAs (personal digital assistants), PADs (tablet computers), desktop computers, etc. Fig. 9 The electronic device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0156] like Fig. 9 As shown, the electronic device may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage device 908 to a random access memory (RAM) 903. When the electronic device is powered on, various programs and data required for the operation of the electronic device are also stored in the RAM 903. The processing device 901, the ROM 902, and the RAM 903 are connected to each other via a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0157] Typically, the following devices may be connected to the I / O interface 905: an input device 906 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 907 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 908 including, for example, a memory card, a hard disk, etc.; and a communication device 909. The communication device 909 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. Although Fig. 9 An electronic device having various devices is shown, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0158] An embodiment of the present application also provides a computer program product including computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements any short message sending and receiving method provided in the embodiment of the present application.

[0159] A computer-readable storage medium is also provided in an embodiment of the present application. The storage medium carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement any short message sending and receiving method provided in the embodiment of the present application.

[0160] It should also be noted that the device embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed over multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, in the drawings of the device embodiments provided by the present application, the connection relationship between the modules indicates that there is a communication connection between them, which may be specifically implemented as one or more communication buses or signal lines.

[0161] Through the description of the above implementation mode, the technicians in the field can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course, it can also be implemented by special hardware including special integrated circuits, special CPUs, special memories, special components, etc. In general, all functions completed by computer programs can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be various, such as analog circuits, digital circuits or special circuits. However, for the present application, software program implementation is a better implementation mode in more cases. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer floppy disk, a U disk, a mobile hard disk, a ROM, a RAM, a disk or an optical disk, etc., including a number of instructions to enable a computer device (which can be a personal computer, a training device, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0162] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0163] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, a computer, a training device, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, training device, or data center. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a training device, a data center, etc. that includes one or more available media integrations. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)), etc.

Claims

1. A method for sending and receiving short messages, characterized in that: The SMSF network element used in the 5GC system includes: Acquire target subscription data of a user equipment, wherein the target subscription data includes a scenario range for prohibiting and / or allowing the user equipment to use a NAS short message service, and the scenario range includes at least one area; Calling a location subscription service interface provided by an access and mobility management network element to subscribe to the location information of the user equipment from the access and mobility management network element, wherein when the location information of the user equipment changes, the access and mobility management network element actively reports the changed location information to the SMS service network element; When receiving the target NAS short message, obtaining real scene information where the user equipment is located, the real scene information including location information of the user equipment; Determine whether to send the target NAS short message to the target network element according to the real scenario information and the scenario range included in the target subscription data.

2. The short message sending and receiving method according to claim 1, characterized in that: Each of the at least one area is an area indicated by a tracking area identifier, or an area indicated by both the tracking area identifier and a next generation cell global identifier.

3. The short message sending and receiving method according to claim 1, characterized in that: The real scene information includes time information, and the scene range includes at least one time period.

4. The short message sending and receiving method according to claim 1, characterized in that: The determining, according to the real scenario information and the scenario range included in the target subscription data, whether to send the target NAS short message to the target network element includes: In a case where the target subscription data includes a scenario range in which the user equipment is prohibited from using the NAS short message service, if the real scenario information falls within the scenario range in which the user equipment is prohibited from using the NAS short message service, the target NAS short message is not sent to the target network element; if the real scenario information does not fall within the scenario range in which the user equipment is prohibited from using the NAS short message service, the target NAS short message is sent to the target network element; and / or, In a case where the target subscription data includes a scenario range in which the user equipment is allowed to use the NAS short message service, if the actual scenario information does not fall within the scenario range in which the user equipment is allowed to use the NAS short message service, the target NAS short message is not sent to the target network element; if the actual scenario information falls within the scenario range in which the user equipment is allowed to use the NAS short message service, the target NAS short message is sent to the target network element.

5. The short message sending and receiving method according to claim 1, characterized in that: If the target NAS short message is a NAS short message generated by the user equipment, the target network element is a NAS short message service center; If the target NAS short message is a NAS short message generated by the NAS short message service center, the target network element is the user equipment.

6. A short message sending and receiving device, characterized in that: The SMSF network element used in the 5GC system includes: A first acquisition module is configured to acquire target subscription data of a user equipment, wherein the target subscription data includes a scenario range in which the user equipment is prohibited and / or allowed to use the NAS short message service, and the scenario range includes at least one area; A location subscription module, configured to call a location subscription service interface provided by an access and mobility management network element to subscribe to the location information of the user equipment from the access and mobility management network element, wherein when the location information of the user equipment changes, the access and mobility management network element actively reports the changed location information to the SMS service network element; A second acquisition module is used to acquire real scene information of the user equipment when receiving the target NAS short message, wherein the real scene information includes location information of the user equipment; The short message management module is used to determine whether to send the target NAS short message to the target network element according to the real scenario information and the scenario range included in the target subscription data.

7. A computer program product, characterized in that The method comprises computer-readable instructions, and when the computer-readable instructions are executed on an electronic device, the electronic device implements the short message sending and receiving method as claimed in any one of claims 1 to 5.

8. An electronic device, characterized in that: The method comprises at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs; The processor is used to execute the computer program so that the electronic device can implement the short message sending and receiving method as described in any one of claims 1 to 5.

9. A computer storage medium, characterized in that: The storage medium carries one or more computer programs, and when the one or more computer programs are executed by an electronic device, the electronic device can implement the short message sending and receiving method as described in any one of claims 1 to 5.

Images