WO2020015137A1 - 短消息重传方法、装置、设备及存储介质 - Google Patents

短消息重传方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2020015137A1
WO2020015137A1 PCT/CN2018/105922 CN2018105922W WO2020015137A1 WO 2020015137 A1 WO2020015137 A1 WO 2020015137A1 CN 2018105922 W CN2018105922 W CN 2018105922W WO 2020015137 A1 WO2020015137 A1 WO 2020015137A1
Authority
WO
WIPO (PCT)
Prior art keywords
retransmission
short message
classification table
error
cause value
Prior art date
Application number
PCT/CN2018/105922
Other languages
English (en)
French (fr)
Inventor
崔恒彬
李文涛
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to JP2018557882A priority Critical patent/JP6884160B2/ja
Priority to RU2018144408A priority patent/RU2713606C1/ru
Priority to KR1020187036315A priority patent/KR102104739B1/ko
Publication of WO2020015137A1 publication Critical patent/WO2020015137A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/23—Reliability checks, e.g. acknowledgments or fault reporting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/234—Monitoring or handling of messages for tracking messages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H04W88/184—Messaging devices, e.g. message centre

Definitions

  • the present application relates to the field of communications, and in particular, to a method, a device, a device, and a storage medium for short message retransmission.
  • SMS Short Message Service
  • SM-RP Short Message Relay Protocol
  • SM-CP Short Message Control Protocol
  • smartphones will retransmit all SMS messages when they receive error messages (such as CP ERROR, RP ERROR), and some retransmission operations will end in failure, resulting in waste of resources.
  • the present disclosure provides a short message retransmission method, device, device, and storage medium.
  • a short message retransmission method includes:
  • determining whether the short message can be successfully retransmitted according to the cause value of the error message includes:
  • the target number of retransmissions is determined based on whether the short message can be successfully retransmitted.
  • the number of retransmissions includes at least 0. Times
  • the preset mapping relationship is represented by different preset classification tables, and the different preset classification tables are divided based on the number of retransmissions.
  • the error message includes CP_ERROR and RP_ERROR
  • the preset classification table includes 0 retransmission classification tables, 1 retransmission classification table, and 2 retransmission classification tables, and the 0 retransmission classifications
  • the table includes: the cause values that have been confirmed to cause retransmission failure
  • the 1 retransmission classification table includes: the cause value of the unclear cause
  • the 2 retransmission classification table includes: 0 retransmission classification table and 1 Cause value other than the cause value in the retransmission classification table.
  • the preset mapping relationship is determined based on a probability that the retransmission is successful under the cause indicated by the cause value in the historical record.
  • a short message retransmission apparatus includes:
  • the retransmission judging module is configured to determine whether the short message can be successfully retransmitted according to a cause value of the error message if an error message returned by the network side is received after the short message is sent;
  • the retransmission execution module is configured to determine whether to resend the short message according to a determination result.
  • the retransmission judgment module includes:
  • the number-of-times determination submodule is configured to determine, after a short message is sent, the error value corresponding to the cause value of the error message from a preset mapping relationship between the cause value and the number of retransmissions if an error message is returned from the network side
  • the target number of retransmissions is determined based on whether the short message can be successfully retransmitted, and the number of retransmissions includes at least 0;
  • the retransmission judging submodule is configured to determine whether the short message can be successfully retransmitted according to the target retransmission times corresponding to the cause value of the error message and the number of retransmission times of the short message.
  • the preset mapping relationship is represented by different preset classification tables, and the different preset classification tables are divided based on the number of retransmissions.
  • the error message includes CP_ERROR and RP_ERROR
  • the preset classification table includes 0 retransmission classification tables, 1 retransmission classification table, and 2 retransmission classification tables, and the 0 retransmission classifications
  • the table includes: the cause values that have been confirmed to cause retransmission failure
  • the 1 retransmission classification table includes: the cause value of the unclear cause
  • the 2 retransmission classification table includes: 0 retransmission classification table and 1 Cause value other than the cause value in the retransmission classification table.
  • the preset mapping relationship is determined based on a probability that the retransmission is successful under the cause indicated by the cause value in the historical record.
  • an electronic device including:
  • Memory for storing processor-executable instructions
  • the processor is configured to:
  • a computer-readable storage medium having stored thereon a computer program that, when executed by a processor, implements the steps of the method described in any one of the above.
  • the short message after the short message is sent, if an error message is returned from the network side, it can be determined whether the short message can be successfully retransmitted according to the cause value of the error message, and then whether to resend the short message according to the judgment result. . Avoid wasting resources due to retransmissions for all failures.
  • Fig. 1 is a flow chart showing a method for retransmitting a short message according to an exemplary embodiment of the present disclosure.
  • Fig. 2 is a flowchart illustrating another short message retransmission method according to an exemplary embodiment of the present disclosure.
  • Fig. 3 is a block diagram of a short message retransmission apparatus according to an exemplary embodiment of the present disclosure.
  • Fig. 4 is a block diagram of another short message retransmission apparatus according to an exemplary embodiment of the present disclosure.
  • Fig. 5 is a block diagram of a device for short message retransmission according to an exemplary embodiment of the present disclosure.
  • first, second, third, etc. may be used in this disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information.
  • word “if” as used herein can be interpreted as “at” or "when” or "in response to determination”.
  • Short messages can also be called text messages, messages, text messages or text messages.
  • the short message can be sent in accordance with the protocol Short Message, Relay Protocol (SM-RP), Short Message Control Protocol (SM-CP).
  • SM-RP Short Message, Relay Protocol
  • SM-CP Short Message Control Protocol
  • smartphones will retransmit all SMS messages when they receive error messages (such as CP ERROR, RP ERROR), and some retransmission operations will end in failure, resulting in waste of resources.
  • an embodiment of the present disclosure provides a short message retransmission method. After a short message is sent, if an error message is returned from the network side, it can be determined whether the short message can be successfully retransmitted according to the cause value of the error message. , And then determine whether to resend the short message according to the judgment result. Avoid wasting resources due to retransmissions for all failures.
  • FIG. 1 is a flowchart illustrating a short message retransmission method according to an exemplary embodiment of the present disclosure.
  • the method may be used in a mobile terminal and includes the following steps:
  • step 101 after the short message is sent, if an error message returned by the network side is received, it is determined whether the short message can be successfully retransmitted according to the cause value of the error message.
  • step 102 it is determined whether to resend the short message according to the determination result.
  • the mobile terminal may be various handheld devices, wearable devices, or other electronic devices with wireless communication functions, for example, a communication module applied to a smart terminal.
  • the edited short message can be interacted with the network side through a protocol.
  • the network side may include two entities (Short MessageRelay (entity)) and SMR (Short MessageControl (entity)).
  • the protocol is used to solve the problem through the retransmission mechanism, and the embodiments of the present disclosure are optimized for situations where there is an error prompt. If an error message (ERROR) returned from the network side is received, it can be determined whether the short message can be successfully retransmitted according to the cause value of the error message, and then whether to resend the short message.
  • ERPOR error message
  • the short message sending process can be sent in accordance with the protocol Short Message Relay Protocol (SM-RP, Short Message Relay Protocol), Short Message Control Protocol (SM-CP, Short Message Control Protocol), etc., and may be received accordingly.
  • SM-RP Short Message Relay Protocol
  • SM-CP Short Message Control Protocol
  • CP_ERROR and RP_ERROR For this reason, error messages can include CP_ERROR and RP_ERROR. It can be understood that the error messages received may be different according to different protocols.
  • the error messages in the embodiments of the present disclosure may also be error messages corresponding to other protocols, which are not listed here one by one.
  • the cause values in the error messages represent different causes. Some of the cause values of CP_ERROR are used as examples to illustrate, as shown in Table 1.
  • cause values indicate different reasons, there are many ways to judge whether the short message can be successfully retransmitted according to the cause value. For example, classify the cause values in the error message in advance, and divide which cause values represent that the short message can be successfully retransmitted, and which cause values represent that the short message cannot be successfully retransmitted.
  • FIG. 2 is a flowchart of another short message retransmission method according to an exemplary embodiment of the present disclosure.
  • the method is implemented in the foregoing. Based on the example, it describes how to determine whether the short message can be successfully retransmitted according to the cause value of the error message.
  • the method includes the following steps:
  • step 201 after the short message is sent, if an error message returned by the network side is received, the target weight corresponding to the cause value of the error message is determined from the preset mapping relationship between the cause value and the number of retransmissions. Number of passes.
  • the number of retransmissions is determined based on whether the short message can be successfully retransmitted, and the number of retransmissions includes at least 0.
  • step 202 it is determined whether the short message can be successfully retransmitted according to the target number of retransmissions corresponding to the cause value of the error message and the number of times the short message has been retransmitted.
  • step 203 it is determined whether to resend the short message according to the determination result.
  • the number of retransmissions includes at least 0 times, so as not to perform retransmission operations on short messages under all cause values.
  • the corresponding relationship between the cause value and the number of retransmissions can be expressed.
  • the mapping relationship between different retransmission times and different cause values can be recorded in the same table.
  • the preset mapping relationship may be represented by different preset classification tables, and different preset classification tables are divided based on the number of retransmissions.
  • different cause values can be divided into different classification tables according to the number of retransmissions, and the same number of retransmissions in the same classification table is achieved, so that the classification table is used to distinguish the number of retransmissions of different cause values.
  • the preset classification table includes a retransmission classification table of 0 times, a retransmission classification table of 1 time, and a retransmission classification table of 2 times
  • the 0 retransmission classification table may include: a reason that has been confirmed to cause retransmission failure Value
  • the one-time retransmission classification table may include: the cause value of unclear reason
  • the two-time retransmission classification table may include: the reason value in the retransmission classification table 0 and the one time retransmission classification table Other cause values.
  • the 0-time retransmission classification table may include 81, 95, 96, 97, 98, 99.
  • the 1-time retransmission classification table may include: 111 and equivalent cause.
  • the secondary retransmission classification table may include CP_ERROR error values, other than the cause values in the zero retransmission classification table and the primary retransmission classification table.
  • the partial cause value of RP_ERROR is taken as an example for description, as shown in Table 2.
  • the 0-time retransmission classification table may include 1, 8, 10, 29, 30, 50, 69, 81, 95, 96, 97, 98, 99.
  • the 1-time retransmission classification table may include: 111 and 127.2
  • the second retransmission classification table may include: among the error values of RP_ERROR, other cause values than the retransmission classification table of 0 times and the cause value in the first retransmission classification table.
  • the classification table may not be limited to the 0-time retransmission classification table, the 1-time retransmission classification table, and the 2-time retransmission classification table, and is specifically set according to requirements.
  • a mapping relationship between the cause value and the number of retransmissions may be created based on the received user input instruction. For example, the user can directly treat the reason value that can't be retransmitted as the failure treatment (0 retransmissions), perform retransmission failure probability statistics for some ambiguous cause values, and treat the failure as the retransmission failure probability is greater than a certain level. Set the number of retransmission times greater than 0 for the remaining cause of retransmission success value.
  • a preset mapping relationship between the cause value and the number of retransmissions may be determined based on the probability of successful retransmission under the cause indicated by the cause value in the historical record.
  • the probability of retransmission success under the reasons indicated by different cause values in the statistical history record is determined, so as to determine a preset mapping relationship between the cause value and the number of retransmission times according to the probability.
  • the classification table includes a retransmission classification table of 0 times, a retransmission classification table of 1 time, and a retransmission classification table of 2 times as an example
  • the probability of successful short message retransmission is lower than a first preset threshold for a certain reason value
  • the The cause value is divided into 0 retransmission classification tables; if the probability is between the first preset threshold and the second preset threshold, the cause value is divided into 1 retransmission classification table; if the probability is greater than the second preset Threshold, the cause value is divided into a secondary retransmission classification table.
  • the first preset threshold is smaller than the second threshold.
  • the target retransmission times corresponding to the cause value in the currently received error message may be obtained, Determine whether the short message can be successfully retransmitted.
  • the number of retransmissions of the short message may be the number of retransmissions of the short message under the cause value, so as to achieve the retransmission operation of performing the target number of retransmissions of the short message under the cause value of the error message. If the target number of retransmissions is 0, it is determined that the short message cannot be retransmitted successfully; if the target number of retransmissions is not equal to 0, and the number of retransmissions has not reached the target number of retransmissions, it is determined that the short message can be retransmitted successfully; The number of transmissions is not equal to 0, and the number of retransmissions reaches the target number of retransmissions, it is determined that the short message cannot be successfully retransmitted.
  • the target retransmission times corresponding to the cause value and the number of retransmissions of the short message are determined to determine whether the short message can be successfully retransmitted and improve the judgment efficiency.
  • the present disclosure also provides embodiments of a short message retransmission device, a device to which the device is applied, and a storage medium.
  • FIG. 3 is a block diagram of a short message retransmission apparatus according to an exemplary embodiment of the present disclosure.
  • the apparatus includes:
  • the retransmission judging module 31 is configured to determine whether the short message can be successfully retransmitted according to a cause value of the error message if an error message returned by the network side is received after the short message is sent;
  • the retransmission execution module 32 is configured to determine whether to resend the short message according to a determination result.
  • FIG. 4 is a block diagram of another short message retransmission apparatus according to an exemplary embodiment of the present disclosure. This embodiment is based on the foregoing embodiment shown in FIG. Module 31 includes:
  • the number of times determining sub-module 311 is configured to determine the cause of the error message from the preset mapping relationship between the cause value and the number of retransmissions if an error message is returned from the network side after the short message is sent.
  • the corresponding number of target retransmissions is determined based on whether the short message can be successfully retransmitted.
  • the number of retransmissions includes at least 0.
  • the retransmission judging sub-module 312 is configured to determine whether the short message can be successfully retransmitted according to the target number of retransmissions corresponding to the cause value of the error message and the number of retransmissions of the short message.
  • the preset mapping relationship is represented by different preset classification tables, and the different preset classification tables are divided based on the number of retransmissions.
  • the cause values corresponding to different retransmission times can be divided into different classification tables, the cause values corresponding to the same retransmission times can be divided into the same classification table, and the classification table can be used to distinguish the number of retransmission times of the cause values.
  • the error message includes CP_ERROR and RP_ERROR
  • the preset classification table includes 0 retransmission classification tables, 1 retransmission classification table, and 2 retransmission classification tables, and the 0 retransmission classifications
  • the table includes: the cause values that have been confirmed to cause retransmission failure
  • the 1 retransmission classification table includes: the cause value of the unclear cause
  • the 2 retransmission classification table includes: 0 retransmission classification table and 1 Cause value other than the cause value in the retransmission classification table.
  • this embodiment limits the number of short message retransmissions to 0, 1 and 2 times, so that no retransmission operation is performed for some short messages, and a maximum of 2 retransmissions are performed for some short messages, thereby saving. Resources.
  • the preset mapping relationship is determined based on a probability that the retransmission is successful under the cause indicated by the cause value in the historical record.
  • this embodiment determines the correspondence between the cause value and the number of retransmissions according to the probability of successful retransmission under the cause indicated by the cause value in the historical record, and can realize the automatic establishment of a preset mapping relationship.
  • the present disclosure also provides an electronic device including a processor; a memory for storing processor-executable instructions; wherein the processor is configured to:
  • the present disclosure also provides a computer-readable storage medium having stored thereon a computer program that, when executed by a processor, implements the steps of the method described in any one of the above.
  • the present disclosure may take the form of a computer program product implemented on one or more storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing program code therein.
  • Computer-usable storage media includes permanent and non-permanent, removable and non-removable media, and information can be stored by any method or technology.
  • Information may be computer-readable instructions, data structures, modules of a program, or other data.
  • Examples of computer storage media include, but are not limited to: phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media may be used to store information that can be accessed by computing devices.
  • PRAM phase change memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • RAM random access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory or other memory technologies
  • CD-ROM compact disc read-only memory
  • DVD digital versatile disc
  • Magnetic tape cartridges magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media may be used to store information that can be accessed
  • the relevant part may refer to the description of the method embodiment.
  • the device embodiments described above are only schematic, and the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, which may be located in One place, or can be distributed to multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solution of the present disclosure. Those of ordinary skill in the art can understand and implement without creative efforts.
  • FIG. 5 is a block diagram of an apparatus for short message retransmission according to an exemplary embodiment of the present disclosure.
  • the device 500 may be a mobile phone.
  • the device 500 may include one or more of the following components: a processing component 502, a memory 504, a power component 506, a multimedia component 508, an audio component 510, an input / output (I / O) interface 512, a sensor component 514, And communication component 516.
  • the processing component 502 generally controls overall operations of the device 500, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • the processing component 502 may include one or more processors 520 to execute instructions to complete all or part of the steps of the method described above.
  • the processing component 502 may include one or more modules to facilitate the interaction between the processing component 502 and other components.
  • the processing component 502 may include a multimedia module to facilitate the interaction between the multimedia component 508 and the processing component 502.
  • the memory 504 is configured to store various types of data to support operation at the device 500. Examples of such data include instructions for any application or method operating on the device 500, contact data, phone book data, messages, pictures, videos, and the like.
  • the memory 504 may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), Programming read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM Programming read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory flash memory
  • flash memory magnetic disk or optical disk.
  • the power supply component 506 provides power to various components of the device 500.
  • the power component 506 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the device 500.
  • the multimedia component 508 includes a screen that provides an output interface between the device 500 and a user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user.
  • the touch panel includes one or more touch sensors to sense touch, swipe, and gestures on the touch panel. The touch sensor may not only sense a boundary of a touch or slide action, but also detect duration and pressure related to the touch or slide operation.
  • the multimedia component 508 includes a front camera and / or a rear camera. When the device 500 is in an operation mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 510 is configured to output and / or input audio signals.
  • the audio component 510 includes a microphone (MIC) that is configured to receive an external audio signal when the device 500 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode.
  • the received audio signal may be further stored in the memory 504 or transmitted via the communication component 516.
  • the audio component 510 further includes a speaker for outputting audio signals.
  • the I / O interface 512 provides an interface between the processing component 502 and a peripheral interface module.
  • the peripheral interface module may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
  • the sensor component 514 includes one or more sensors for providing status assessment of various aspects of the device 500.
  • the sensor component 514 can detect the on / off state of the device 500 and the relative positioning of the components, such as the display and keypad of the device 500.
  • the sensor component 514 can also detect the position of the device 500 or a component in the device 500 Changes, the presence or absence of the user's contact with the device 500, the orientation or acceleration / deceleration of the device 500, and the temperature change of the device 500.
  • the sensor component 514 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • the sensor component 514 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 514 may further include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • the communication component 516 is configured to facilitate wired or wireless communication between the device 500 and other devices.
  • the device 500 may access a wireless network based on a communication standard, such as WiFi, 2G, or 3G, or a combination thereof.
  • the communication component 516 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel.
  • the communication component 516 further includes a near field communication (NFC) module to facilitate short-range communication.
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra wideband
  • Bluetooth Bluetooth
  • the apparatus 500 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor, or other electronic component is implemented to perform the above method.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A gate array
  • controller microcontroller, microprocessor, or other electronic component is implemented to perform the above method.
  • a non-transitory computer-readable storage medium including instructions such as a memory 504 including instructions, may be provided, which may be executed by the processor 520 of the apparatus 500 to complete the method.
  • the non-transitory computer-readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
  • the device 500 can execute a short message retransmission method, including:

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)
  • Communication Control (AREA)

Abstract

本公开提供一种短消息重传方法、装置、设备及存储介质，所述方法包括：在短消息被发送后，若接收到网络侧回传的错误消息，根据所述错误消息的原因值判断所述短消息是否能重传成功；根据判断结果确定是否重新发送所述短消息。应用本公开实施例可以避免对所有失败情况都进行重传导致的资源浪费。

Description

短消息重传方法、装置、设备及存储介质 技术领域
本申请涉及通信领域，尤其涉及短消息重传方法、装置、设备及存储介质。
背景技术
利用移动通信网络在移动终端上实现的各类数据业务已变得和人们的日常生活越来越密不可分，特别是短消息服务(Short Message Service,SMS)，已经成为大部分移动通信用户的常用联系方式。短消息发送过程中可以按照协议Short Message Relay Protocol(SM-RP),Short Message Control Protocol(SM-CP)进行发送。目前，大多数智能手机在短信收到错误消息(如CP ERROR,RP ERROR)的情况下全部会进行重传，而部分重传操作会以失败告终，从而造成资源浪费。
发明内容
为克服相关技术中存在的问题，本公开提供了短消息重传方法、装置、设备及存储介质。
根据本公开实施例的第一方面，提供一种短消息重传方法，所述方法包括：
在短消息被发送后，若接收到网络侧回传的错误消息，根据所述错误消息的原因值判断所述短消息是否能重传成功；
根据判断结果确定是否重新发送所述短消息。
在一个实施例中，所述根据所述错误消息的原因值判断所述短消息是否能重传成功，包括：
从原因值与重传次数的预设映射关系中，确定所述错误消息的原因值所对应的目标重传次数，重传次数基于短消息是否能重传成功而确定，重传次数至少包括0次；
根据所述错误消息的原因值所对应的目标重传次数、以及所述短消息的已重传次数，判断所述短消息是否能重传成功。
在一个实施例中，所述预设映射关系通过不同预设分类表表示，不同预设分类表基于重传次数进行划分。
在一个实施例中，所述错误消息包括CP_ERROR和RP_ERROR，所述预设分类表包括0次重发分类表、1次重发分类表和2次重发分类表，所述0次重发分类表包括：已确认会导致重传失败的原因值，所述1次重发分类表包括：不明确原因的原因值；所述2次重发分类表包括：除0次重发分类表以及1次重发分类表中原因值以外的其 他原因值。
在一个实施例中，所述预设映射关系基于历史记录中在原因值所表示的原因下重传成功的概率而确定。
根据本公开实施例的第二方面，提供一种短消息重传装置，所述装置包括：
重传判断模块，被配置为在短消息被发送后，若接收到网络侧回传的错误消息，根据所述错误消息的原因值判断所述短消息是否能重传成功；
重传执行模块，被配置为根据判断结果确定是否重新发送所述短消息。
在一个实施例中，所述重传判断模块，包括：
次数确定子模块，被配置为在短消息被发送后，若接收到网络侧回传的错误消息，从原因值与重传次数的预设映射关系中，确定所述错误消息的原因值所对应的目标重传次数，重传次数基于短消息是否能重传成功而确定，重传次数至少包括0次；
重传判断子模块，被配置为根据所述错误消息的原因值所对应的目标重传次数、以及所述短消息的已重传次数，判断所述短消息是否能重传成功。
在一个实施例中，所述预设映射关系通过不同预设分类表表示，不同预设分类表基于重传次数进行划分。
在一个实施例中，所述错误消息包括CP_ERROR和RP_ERROR，所述预设分类表包括0次重发分类表、1次重发分类表和2次重发分类表，所述0次重发分类表包括：已确认会导致重传失败的原因值，所述1次重发分类表包括：不明确原因的原因值；所述2次重发分类表包括：除0次重发分类表以及1次重发分类表中原因值以外的其他原因值。
在一个实施例中，所述预设映射关系基于历史记录中在原因值所表示的原因下重传成功的概率而确定。
根据本公开实施例的第三方面，提供一种电子设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
在短消息被发送后，若接收到网络侧回传的错误消息，根据所述错误消息的原因值判断所述短消息是否能重传成功；
根据判断结果确定是否重新发送所述短消息。
根据本公开实施例的第四方面，提供一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现上述任一项所述方法的步骤。
本公开的实施例提供的技术方案可以包括以下有益效果：
本公开实施例在短消息被发送后，若接收到网络侧回传的错误消息，可以根据错误消息的原因值判断该短消息是否能重传成功，进而根据判断结果确定是否重新发送该短消息。避免对所有失败情况都进行重传导致的资源浪费。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并与说明书一起用于解释本公开的原理。
图1是本公开根据一示例性实施例示出的一种短消息重传方法的流程图。
图2是本公开根据一示例性实施例示出的另一种短消息重传方法的流程图。
图3是本公开根据一示例性实施例示出的一种短消息重传装置的框图。
图4是本公开根据一示例性实施例示出的另一种短消息重传装置的框图。
图5是本公开根据一示例性实施例示出的一种用于短消息重传的装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
在本公开使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开。在本公开和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
短消息又可以称为简讯、信息、短信或文字消息等。短消息发送过程中可以按照协议Short Message Relay Protocol(SM-RP),Short Message Control Protocol(SM-CP)进行发送。目前，大多数智能手机在短信收到错误消息(如CP ERROR,RP ERROR)的 情况下全部会进行重传，而部分重传操作会以失败告终，从而造成资源浪费。
鉴于此，本公开实施例提供一种短消息重传方法，在短消息被发送后，若接收到网络侧回传的错误消息，可以根据错误消息的原因值判断该短消息是否能重传成功，进而根据判断结果确定是否重新发送该短消息。避免对所有失败情况都进行重传导致的资源浪费。
以下结合附图对本公开实施例进行示例说明。
如图1所示，图1是本公开根据一示例性实施例示出的一种短消息重传方法的流程图，该方法可以用于移动终端中，包括以下步骤：
在步骤101中，在短消息被发送后，若接收到网络侧回传的错误消息，根据所述错误消息的原因值判断所述短消息是否能重传成功。
在步骤102中，根据判断结果确定是否重新发送所述短消息。
本公开实施例中，移动终端可以是各种具有无线通信功能的手持设备、可穿戴设备或其他电子设备，例如，应用于智能终端中的通信模块。在移动终端中，可以将编辑好的短消息通过协议与网络侧(network)进行交互。在一个例子中，网络侧可以包括两个实体SMC(Short Message Relay(entity))和SMR(Short Message Control(entity))。
在短消息被发送后可能会出现很多状况，针对部分状况，在协议中通过重传机制解决，而本公开实施例针对有错误提示的情况进行优化。如果接收到网络侧回传的错误消息(ERROR)，则可以根据错误消息的原因值判断短消息是否能重传成功，进而决定是否重新发送该短消息。
其中，短消息发送过程中可以按照协议Short Message Relay Protocol(SM-RP，短消息中继协议),Short Message Control Protocol(SM-CP，短消息控制协议)等进行发送，相应的，可能收到CP_ERROR和RP_ERROR。鉴于此，错误消息可以包括CP_ERROR和RP_ERROR。可以理解的是，根据协议的不同，收到的错误消息可能不同，本公开实施例的错误消息还可以是其他协议对应的错误消息，在此不一一列举。
错误消息中的原因值代表不同的原因，以CP_ERROR的部分原因值为例进行示例说明，如表1。
表1
Figure PCTCN2018105922-appb-000001
Figure PCTCN2018105922-appb-000002
可见，由于不同原因值表示不同的原因，而原因可以用于判断短消息是否能重传成功，因此，可以根据原因值判断短消息是否能重传成功，进而根据判断结果确定是否重新发送短消息，实现针对有错误提示的情况进行优化，避免对所有失败情况都进行重传导致的资源浪费。
由于不同原因值表示不同的原因，因此，根据原因值判断短消息是否能重传成功的方式有很多种。例如，预先将错误消息中的原因值进行分类，划分哪些原因值代表短消息能重传成功，哪些原因值代表短消息不能重传成功。
在一个实施例中，提供一种具体的判断手段，如图2所示，图2是本公开根据一示例性实施例示出的另一种短消息重传方法的流程图，该方法在前述实施例的基础上，描述了如何根据错误消息的原因值判断短消息是否能重传成功，所述方法包括以下步骤：
在步骤201中，在短消息被发送后，若接收到网络侧回传的错误消息，从原因值与重传次数的预设映射关系中，确定所述错误消息的原因值所对应的目标重传次数。
其中，预设映射关系中，重传次数基于短消息是否能重传成功而确定，重传次数至少包括0次。
在步骤202中，根据所述错误消息的原因值所对应的目标重传次数、以及所述短消息的已重传次数，判断所述短消息是否能重传成功。
在步骤203中，根据判断结果确定是否重新发送所述短消息。
其中，重传次数至少包括0次，以实现并非对所有原因值下的短消息执行重传操作。
关于预设映射关系，可以表示原因值与重传次数的对应关系。在一个例子中，可 以通过同一个表记录不同重传次数与不同原因值的映射关系。在另一个例子中，所述预设映射关系可以通过不同预设分类表表示，同时，不同预设分类表基于重传次数进行划分。在该实施例中，可以按重传次数将不同原因值划分到不同分类表中，同一分类表中重传次数相同，从而实现利用分类表区分不同原因值的重传次数。例如，所述预设分类表包括0次重发分类表、1次重发分类表和2次重发分类表，所述0次重发分类表可以包括：已确认会导致重传失败的原因值，所述1次重发分类表可以包括：不明确原因的原因值；所述2次重发分类表可以包括：除0次重发分类表以及1次重发分类表中原因值以外的其他原因值。
例如，针对CP_ERROR的错误值，0次重发分类表可以包括81，95，96，97，98，99。1次重发分类表可以包括：111以及等同cause。2次重发分类表可以包括CP_ERROR的错误值中，除0次重发分类表以及1次重发分类表中原因值以外的其他原因值。
又如，以RP_ERROR的部分原因值为例进行示例说明，如表2。
表2
Figure PCTCN2018105922-appb-000003
Figure PCTCN2018105922-appb-000004
在该例子中，0次重发分类表可以包括1，8，10，29，30，50，69，81，95，96，97，98，99。1次重发分类表可以包括：111和127。2次重发分类表可以包括：RP_ERROR的错误值中，除0次重发分类表以及1次重发分类表中原因值以外的其他原因值。
可以理解的是，上述仅以CP_ERROR和RP_ERROR中的错误值为例进行示例说明，针对其他错误值在此不一一赘述。另外，分类表也可以不限于0次重发分类表、1次重发分类表和2次重发分类表，具体根据需求设置。
关于如何确定原因值与重传次数的预设映射关系，在一个例子中，可以基于接收的用户输入指令，创建原因值与重传次数的映射关系。例如，用户可以将明显知道不能重传的原因值直接作为失败处理(0次重传)，对于一些模棱两可的原因值进行重传失败概率统计，在重传失败概率大于一定程度后作为失败处理，对于剩下有几率重传成功的原因值设置重传次数大于0。
在另一个例子中，可以基于历史记录中在原因值所表示的原因下重传成功的概率而确定原因值与重传次数的预设映射关系。在该实施例中，通过统计历史记录中，不同原因值所表示的原因下重传成功的概率，从而根据概率确定原因值与重传次数的预设映射关系。例如，以分类表包括0次重发分类表、1次重发分类表和2次重发分类表 为例，若某原因值下短消息重传成功的概率小于第一预设阈值，则将该原因值划分到0次重传分类表；若概率在第一预设阈值与第二预设阈值之间，则将该原因值划分到1次重传分类表；若概率大于第二预设阈值，则将该原因值划分到2次重传分类表。其中，第一预设阈值小于第二阈值。
在根据预设映射关系确定当前接收到的错误消息中的原因值所对应的目标重传次数后，可以根据错误消息的原因值所对应的目标重传次数、以及短消息的已重传次数，判断短消息是否能重传成功。
其中，短消息的已重传次数可以是短消息在该原因值下的已重传次数，从而实现在错误消息的原因值下，能实现对短消息执行目标重传次数的重传操作。若目标重传次数为0，则判定短消息不能重传成功；若目标重传次数不等于0，且已重传次数未达到目标重传次数，则判定短消息能重传成功；若目标重传次数不等于0，且已重传次数达到目标重传次数，则判定短消息不能重传成功。
可见，在该实施例中，通过确定原因值所对应的目标重传次数，以及短消息的已重传次数，从而判断短消息是否能重传成功，提高判断效率。
以上实施方式中的各种技术特征可以任意进行组合，只要特征之间的组合不存在冲突或矛盾，但是限于篇幅，未进行一一描述，因此上述实施方式中的各种技术特征的任意进行组合也属于本说明书公开的范围。
与前述短消息重传方法的实施例相对应，本公开还提供了短消息重传装置、装置所应用的设备以及存储介质的实施例。
如图3所示，图3是本公开根据一示例性实施例示出的一种短消息重传装置的框图，所述装置包括：
重传判断模块31，被配置为在短消息被发送后，若接收到网络侧回传的错误消息，根据所述错误消息的原因值判断所述短消息是否能重传成功；
重传执行模块32，被配置为根据判断结果确定是否重新发送所述短消息。
由上述实施例可见，在短消息被发送后，若接收到网络侧回传的错误消息，可以根据错误消息的原因值判断该短消息是否能重传成功，进而根据判断结果确定是否重新发送该短消息。避免对所有失败情况都进行重传导致的资源浪费。
如图4所示，图4是本公开根据一示例性实施例示出的另一种短消息重传装置的框图，该实施例在前述图3所示实施例的基础上，所述重传判断模块31，包括：
次数确定子模块311，被配置为在短消息被发送后，若接收到网络侧回传的错误消息，从原因值与重传次数的预设映射关系中，确定所述错误消息的原因值所对应的目标重传次数，重传次数基于短消息是否能重传成功而确定，重传次数至少包括0次；
重传判断子模块312，被配置为根据所述错误消息的原因值所对应的目标重传次数、以及所述短消息的已重传次数，判断所述短消息是否能重传成功。
由上述实施例可见，通过确定原因值所对应的目标重传次数，以及短消息的已重传次数，从而判断短消息是否能重传成功，提高判断效率。
在一个实施例中，所述预设映射关系通过不同预设分类表表示，不同预设分类表基于重传次数进行划分。
由上述实施例可见，可以实现将对应不同重传次数的原因值划分到不同分类表，将对应相同重传次数的原因值划分到相同分类表，实现利用分类表区分原因值的重传次数。
在一个实施例中，所述错误消息包括CP_ERROR和RP_ERROR，所述预设分类表包括0次重发分类表、1次重发分类表和2次重发分类表，所述0次重发分类表包括：已确认会导致重传失败的原因值，所述1次重发分类表包括：不明确原因的原因值；所述2次重发分类表包括：除0次重发分类表以及1次重发分类表中原因值以外的其他原因值。
由上述实施例可见，本实施例将短消息的重传次数限定为0次、1次和2次，实现针对部分短消息不进行重传操作，针对部分短消息最多重传2次，从而节约资源。
在一个实施例中，所述预设映射关系基于历史记录中在原因值所表示的原因下重传成功的概率而确定。
由上述实施例可见，本实施例根据历史记录中在原因值所表示的原因下重传成功的概率确定原因值与重传次数的对应关系，可以实现自动化构建预设映射关系。
相应的，本公开还提供一种电子设备，所述设备包括有处理器；用于存储处理器可执行指令的存储器；其中，所述处理器被配置为：
在短消息被发送后，若接收到网络侧回传的错误消息，根据所述错误消息的原因值判断所述短消息是否能重传成功；
根据判断结果确定是否重新发送所述短消息。
相应的，本公开还提供一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现上述任一项所述方法的步骤。
本公开可采用在一个或多个其中包含有程序代码的存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。计算机可用存储介质包括永久性和非永久性、可移动和非可移动媒体，可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括但不限于：相变内存(PRAM)、静态随机存取存储器(SRAM)、 动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。
上述装置中各个模块的功能和作用的实现过程具体详情见上述方法中对应步骤的实现过程，在此不再赘述。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个地方，或者也可以分布到多个网络模块上。可以根据实际的需要选择其中的部分或者全部模块来实现本公开方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
如图5所示，图5是本公开根据一示例性实施例示出的一种用于短消息重传的装置的框图。该装置500可以是移动电话。
参照图5，装置500可以包括以下一个或多个组件：处理组件502，存储器504，电源组件506，多媒体组件508，音频组件510，输入/输出(I/O)的接口512，传感器组件514，以及通信组件516。
处理组件502通常控制装置500的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件502可以包括一个或多个处理器520来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件502可以包括一个或多个模块，便于处理组件502和其他组件之间的交互。例如，处理组件502可以包括多媒体模块，以方便多媒体组件508和处理组件502之间的交互。
存储器504被配置为存储各种类型的数据以支持在装置500的操作。这些数据的示例包括用于在装置500上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器504可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件506为装置500的各种组件提供电力。电源组件506可以包括电源管理系统，一个或多个电源，及其他与为装置500生成、管理和分配电力相关联的组件。
多媒体组件508包括在所述装置500和用户之间的提供一个输出接口的屏幕。在 一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件508包括一个前置摄像头和/或后置摄像头。当装置500处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件510被配置为输出和/或输入音频信号。例如，音频组件510包括一个麦克风(MIC)，当装置500处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器504或经由通信组件516发送。在一些实施例中，音频组件510还包括一个扬声器，用于输出音频信号。
I/O接口512为处理组件502和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件514包括一个或多个传感器，用于为装置500提供各个方面的状态评估。例如，传感器组件514可以检测到装置500的打开/关闭状态，组件的相对定位，例如所述组件为装置500的显示器和小键盘，传感器组件514还可以检测装置500或装置500中一个组件的位置改变，用户与装置500接触的存在或不存在，装置500方位或加速/减速和装置500的温度变化。传感器组件514可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件514还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件514还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件516被配置为便于装置500和其他设备之间有线或无线方式的通信。装置500可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件516经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件516还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置500可以被一个或多个应用专用集成电路(ASIC)、数 字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器504，上述指令可由装置500的处理器520执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
其中，当所述存储介质中的指令由所述处理器执行时，使得装置500能够执行一种短消息重传方法，包括：
在短消息被发送后，若接收到网络侧回传的错误消息，根据所述错误消息的原因值判断所述短消息是否能重传成功；
根据判断结果确定是否重新发送所述短消息。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。
以上所述仅为本公开的较佳实施例而已，并不用以限制本公开，凡在本公开的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本公开保护的范围之内。

Claims (12)

  1. 一种短消息重传方法，其特征在于，所述方法包括：
    在短消息被发送后，若接收到网络侧回传的错误消息，根据所述错误消息的原因值判断所述短消息是否能重传成功；
    根据判断结果确定是否重新发送所述短消息。
  2. 根据权利要求1所述的方法，其特征在于，所述根据所述错误消息的原因值判断所述短消息是否能重传成功，包括：
    从原因值与重传次数的预设映射关系中，确定所述错误消息的原因值所对应的目标重传次数，重传次数基于短消息是否能重传成功而确定，重传次数至少包括0次；
    根据所述错误消息的原因值所对应的目标重传次数、以及所述短消息的已重传次数，判断所述短消息是否能重传成功。
  3. 根据权利要求2所述的方法，其特征在于，所述预设映射关系通过不同预设分类表表示，不同预设分类表基于重传次数进行划分。
  4. 根据权利要求3所述的方法，其特征在于，所述错误消息包括CP_ERROR和RP_ERROR，所述预设分类表包括0次重发分类表、1次重发分类表和2次重发分类表，所述0次重发分类表包括：已确认会导致重传失败的原因值，所述1次重发分类表包括：不明确原因的原因值；所述2次重发分类表包括：除0次重发分类表以及1次重发分类表中原因值以外的其他原因值。
  5. 根据权利要求2至4任一项所述的方法，其特征在于，所述预设映射关系基于历史记录中在原因值所表示的原因下重传成功的概率而确定。
  6. 一种短消息重传装置，其特征在于，所述装置包括：
    重传判断模块，被配置为在短消息被发送后，若接收到网络侧回传的错误消息，根据所述错误消息的原因值判断所述短消息是否能重传成功；
    重传执行模块，被配置为根据判断结果确定是否重新发送所述短消息。
  7. 根据权利要求6所述的装置，其特征在于，所述重传判断模块，包括：
    次数确定子模块，被配置为在短消息被发送后，若接收到网络侧回传的错误消息，从原因值与重传次数的预设映射关系中，确定所述错误消息的原因值所对应的目标重传次数，重传次数基于短消息是否能重传成功而确定，重传次数至少包括0次；
    重传判断子模块，被配置为根据所述错误消息的原因值所对应的目标重传次数、以及所述短消息的已重传次数，判断所述短消息是否能重传成功。
  8. 根据权利要求7所述的装置，其特征在于，所述预设映射关系通过不同预设分类表 表示，不同预设分类表基于重传次数进行划分。
  9. 根据权利要求8所述的装置，其特征在于，所述错误消息包括CP_ERROR和RP_ERROR，所述预设分类表包括0次重发分类表、1次重发分类表和2次重发分类表，所述0次重发分类表包括：已确认会导致重传失败的原因值，所述1次重发分类表包括：不明确原因的原因值；所述2次重发分类表包括：除0次重发分类表以及1次重发分类表中原因值以外的其他原因值。
  10. 根据权利要求7至9任一项所述的装置，其特征在于，所述预设映射关系基于历史记录中在原因值所表示的原因下重传成功的概率而确定。
  11. 一种电子设备，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    在短消息被发送后，若接收到网络侧回传的错误消息，根据所述错误消息的原因值判断所述短消息是否能重传成功；
    根据判断结果确定是否重新发送所述短消息。
  12. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，该程序被处理器执行时实现权利要求1至5任一项所述方法的步骤。
PCT/CN2018/105922 2018-07-19 2018-09-17 短消息重传方法、装置、设备及存储介质 WO2020015137A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2018557882A JP6884160B2 (ja) 2018-07-19 2018-09-17 ショートメッセージ再送信方法、装置、機器及び記憶媒体
RU2018144408A RU2713606C1 (ru) 2018-07-19 2018-09-17 Способ и устройство для повторной передачи коротких сообщений, а также устройство и носитель данных
KR1020187036315A KR102104739B1 (ko) 2018-07-19 2018-09-17 단문 메시지 재전송 방법, 장치, 기기 및 저장 매체

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810799432.1A CN108566628A (zh) 2018-07-19 2018-07-19 短消息重传方法、装置、设备及存储介质
CN201810799432.1 2018-07-19

Publications (1)

Publication Number Publication Date
WO2020015137A1 true WO2020015137A1 (zh) 2020-01-23

Family

ID=63555806

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/105922 WO2020015137A1 (zh) 2018-07-19 2018-09-17 短消息重传方法、装置、设备及存储介质

Country Status (7)

Country Link
US (1) US10491556B1 (zh)
EP (1) EP3598702B1 (zh)
JP (1) JP6884160B2 (zh)
KR (1) KR102104739B1 (zh)
CN (1) CN108566628A (zh)
RU (1) RU2713606C1 (zh)
WO (1) WO2020015137A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112654006A (zh) * 2020-12-15 2021-04-13 北京金山云网络技术有限公司 短信服务的处理方法、装置及电子设备
CN113132063B (zh) * 2021-04-02 2022-07-01 天津瑞发科半导体技术有限公司 一种物理层重传控制方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101068381A (zh) * 2007-06-07 2007-11-07 中兴通讯股份有限公司 短消息系统及短消息重新发送方法
CN101621770A (zh) * 2009-07-22 2010-01-06 中兴通讯股份有限公司 一种短消息传递失败的处理方法及装置
CN101951574A (zh) * 2010-09-01 2011-01-19 中兴通讯股份有限公司 短消息处理方法和短消息中心
CN103686635A (zh) * 2012-09-13 2014-03-26 中国电信股份有限公司 一种用于短信重发的方法和系统
CN104581659A (zh) * 2013-10-24 2015-04-29 宏碁股份有限公司 处理短信服务信息在传送被拒绝时的方法及通信系统

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS62207042A (ja) * 1986-03-07 1987-09-11 Mitsubishi Electric Corp 送受信モジユ−ル
JPH09326911A (ja) * 1996-06-05 1997-12-16 Oki Electric Ind Co Ltd 画像送信装置
KR101506029B1 (ko) * 2006-11-13 2015-03-27 삼성전자주식회사 통합 메시징 서비스를 제공하기 위한 시스템과 방법
CN100512314C (zh) * 2007-06-15 2009-07-08 中兴通讯股份有限公司 一种优化Push通告消息的方法
US8254971B1 (en) * 2007-11-29 2012-08-28 At&T Mobility Ii Llc System and method for determining an SMS message retransmission schedule
US20090176517A1 (en) * 2008-01-06 2009-07-09 Apple Inc. Multiple Recipient Messaging Service for Mobile Device
US8032164B2 (en) * 2008-09-22 2011-10-04 Interdigital Patent Holdings, Inc. Method and apparatus for communicating short message service and supplementary services messages
JP2010093354A (ja) * 2008-10-03 2010-04-22 Sanyo Electric Co Ltd 通信装置
US8831650B2 (en) * 2010-02-10 2014-09-09 Lg Electronics Inc. Method of exchanging SMS data in a wireless communications system
BR112014024570B1 (pt) * 2012-04-10 2022-07-05 Nokia Technologies Oy Método; aparelho; e meio legível por computador
US9026851B2 (en) * 2012-09-05 2015-05-05 Wipro Limited System and method for intelligent troubleshooting of in-service customer experience issues in communication networks
CN107370666B (zh) * 2012-10-26 2020-10-16 华为技术有限公司 一种短消息信令优化方法、设备和系统
US8971343B2 (en) * 2013-01-11 2015-03-03 Acer Incorporated Method of providing short message service in a network
CN103973419A (zh) * 2013-01-31 2014-08-06 中兴通讯股份有限公司 一种短消息服务中心及短消息重发的方法
CN104507059B (zh) * 2014-12-19 2018-01-16 广东欧珀移动通信有限公司 一种彩信发送管理方法和彩信发送管理装置
JP6515560B2 (ja) * 2015-02-09 2019-05-22 富士ゼロックス株式会社 画像形成装置及びプログラム

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101068381A (zh) * 2007-06-07 2007-11-07 中兴通讯股份有限公司 短消息系统及短消息重新发送方法
CN101621770A (zh) * 2009-07-22 2010-01-06 中兴通讯股份有限公司 一种短消息传递失败的处理方法及装置
CN101951574A (zh) * 2010-09-01 2011-01-19 中兴通讯股份有限公司 短消息处理方法和短消息中心
CN103686635A (zh) * 2012-09-13 2014-03-26 中国电信股份有限公司 一种用于短信重发的方法和系统
CN104581659A (zh) * 2013-10-24 2015-04-29 宏碁股份有限公司 处理短信服务信息在传送被拒绝时的方法及通信系统

Also Published As

Publication number Publication date
KR102104739B1 (ko) 2020-04-27
KR20200009997A (ko) 2020-01-30
EP3598702B1 (en) 2023-03-08
EP3598702A1 (en) 2020-01-22
JP6884160B2 (ja) 2021-06-09
RU2713606C1 (ru) 2020-02-05
JP2020530667A (ja) 2020-10-22
US10491556B1 (en) 2019-11-26
CN108566628A (zh) 2018-09-21

Similar Documents

Publication Publication Date Title
WO2017000490A1 (zh) 报警方法及装置
RU2619083C2 (ru) Способ и устройство для сообщения о запросе на вызов
WO2018076820A1 (zh) 一种无线链路失败的处理方法和装置
WO2016134600A1 (zh) 智能设备检测方法和装置
JP6338782B2 (ja) 通信メッセージの処理方法及び装置
CN107071862B (zh) 账号绑定方法及装置和智能设备
WO2016155231A1 (zh) 网络接入方法及装置
WO2019218366A1 (zh) 前导码和调度请求的发送方法及装置
US11375403B2 (en) Method and apparatus for detecting maximum transmission unit value
WO2020034072A1 (zh) 上行调度请求的发送方法、装置、设备及存储介质
WO2020056741A1 (zh) 接入控制限制方法及装置
WO2020097810A1 (zh) 调度请求发送方法和装置
WO2020006745A1 (zh) 信息传输方法及装置
WO2019237360A1 (zh) 确定上下行切换点的方法及装置
JP2018503989A (ja) 情報処理方法、装置、プログラム、及び記録媒体
WO2020015137A1 (zh) 短消息重传方法、装置、设备及存储介质
WO2020087348A1 (zh) 信息反馈方法及装置
WO2018232755A1 (zh) 抢占时频资源的确定方法及装置和用户设备
WO2019227318A1 (zh) 物理下行控制信道监测配置、监测方法及装置和基站
WO2016192322A1 (zh) 一种信息发送的方法及装置
WO2020014824A1 (zh) 随机接入控制方法和随机接入控制装置
WO2018205279A1 (zh) 用于接收和发送系统消息的方法、装置、用户设备及基站
WO2020223969A1 (zh) 直连链路数据发送和直连链路资源配置方法以及装置
WO2020087321A1 (zh) 配置调整方法、装置、电子设备和计算机可读存储介质
WO2019174049A1 (zh) 系统消息请求调整方法及装置和用户设备

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2018557882

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20187036315

Country of ref document: KR

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18926768

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18926768

Country of ref document: EP

Kind code of ref document: A1