WO2019233255A1 - 短信分组方法及装置、计算机可读存储介质 - Google Patents

短信分组方法及装置、计算机可读存储介质 Download PDF

Info

Publication number
WO2019233255A1
WO2019233255A1 PCT/CN2019/087060 CN2019087060W WO2019233255A1 WO 2019233255 A1 WO2019233255 A1 WO 2019233255A1 CN 2019087060 W CN2019087060 W CN 2019087060W WO 2019233255 A1 WO2019233255 A1 WO 2019233255A1
Authority
WO
WIPO (PCT)
Prior art keywords
short message
grouping
short
service provider
short messages
Prior art date
Application number
PCT/CN2019/087060
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 中兴通讯股份有限公司
Publication of WO2019233255A1 publication Critical patent/WO2019233255A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support

Definitions

  • the embodiments of the present application relate to, but are not limited to, the field of communications, for example, a method and a device for grouping short messages, and a computer-readable storage medium.
  • the first and second short messages are all the notification short messages of Industrial Securities. Due to the different sender numbers, they are divided into different groups.
  • the sixth and ninth short messages are from ZTE. SMS notifications are grouped into different groups due to different sender numbers. Therefore, it is necessary to provide a method for grouping short messages to improve the accuracy of grouping.
  • An embodiment of the present application provides a method and a device for grouping short messages, and a computer-readable storage medium to improve the accuracy of grouping.
  • An embodiment of the present application provides a method for grouping short messages, including: obtaining a service provider number of the short message from a sender number of the short message; and grouping the short messages according to at least the service provider number of the short message.
  • An embodiment of the present application provides a short message grouping device, which includes a memory and a processor.
  • the memory stores a program.
  • the program is read and executed by the processor, the short message grouping method according to any one of the embodiments is implemented. .
  • An embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement any The short message grouping method described in the embodiment.
  • FIG. 1 is a schematic diagram of short message grouping in the related art
  • FIG. 2 is a flowchart of a short message grouping method according to an embodiment of the present application
  • FIG. 3 is a flowchart of a short message grouping method according to an embodiment of the present application.
  • FIG. 4 is a flowchart of extracting a provider information of a short message according to an embodiment of the present application.
  • FIG. 5 is a flowchart of a short message grouping method according to another embodiment of the present application.
  • 6a to 6e are block diagrams of a short message grouping device according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a short message group according to an embodiment of the present application.
  • FIG. 8 is a block diagram of a short message grouping device according to an embodiment of the present application.
  • an embodiment of the present application provides a short message grouping method, which includes steps 201 and 202.
  • a service provider (SP) number of the short message is obtained from the sender number of the short message.
  • step 202 the short messages are grouped according to at least the SP number of the short messages.
  • the short message grouping method provided in this embodiment groups short messages according to an SP number, so that short messages from the same SP number can be grouped into the same group.
  • this method The application enables the short messages from the same SP number but different sender numbers to be grouped into the same group, which improves the accuracy of grouping and facilitates users to find and manage.
  • this embodiment does not need to modify the communication protocol in the related technology, and does not increase the interface and signaling burden of the base station or the core network.
  • the method before step 201, the method further includes: determining whether the short message is a PUSH (push) short message, and performing step 201 based on a determination result that the short message is a PUSH short message. It should be noted that this step may not be performed.
  • PUSH push
  • obtaining the SP number of the short message from the sender number of the short message in step 201 includes: when the short message is a service type short message, obtaining the short message from the sender number of the short message. SP number.
  • service-type short messages must start with 955 or 106. Therefore, you can check whether the first 3 digits of the text message are 955 or 106. Of course, you can also check whether the first 2 digits of the text message are 95 or 10, or check whether the first digit of the text message is 9 or 1.
  • Only follow-up grouping method is used for service text messages to improve grouping efficiency. Of course, if the specification is changed (the number rule of the service type short message is changed), it is checked whether the short message is a service type short message according to the changed specification.
  • obtaining the SP number of the short message from the sender number of the short message includes: matching the sender number of the short message with the SP number in a pre-stored SP number database, and The matched SP number is used as the SP number of the short message.
  • the sender number of the short message is not the SP number of the short message.
  • the sender number of the short message also includes the number information added by the short message gateway. For example, to send a text message to the user at 13768057893, the SP number is: 106575257205. When passing the SMS gateway, the SMS gateway added 160001 at the end.
  • Matching the sender number of the short message with the SP number in the pre-stored SP number database includes: determining whether the sender number of the short message contains the SP number in the SP number database, and based on the sender number of the short message contains the SP The judgment result of the SP number in the code base determines that the SP number is the SP number of the short message. For example, if the sender number of the short message is 106575257205160001, which matches the SP number in the SP number database and matches 106575257205, the SP number of the short message is 106575257205.
  • the sender number of the short message is 1069035695562, which matches the SP number in the SP number database. If the number matches 96652, the SP number of the short message is 95562.
  • the service provider number database can be stored in the terminal or in the cloud. When stored in the cloud, obtaining the SP number of the short message from the sender number of the short message includes: sending the sender number of the short message to the cloud server, receiving the matched SP number returned by the cloud server, and using the received SP number as SP number of the short message.
  • the SP number database contains multiple SP numbers.
  • the SP numbers in the SP number database are sorted according to their frequency of occurrence in a short message.
  • the short messages are: historical short messages received by the terminal, or all short messages in the server providing the short message service. If it is a historical short message received by the terminal, the terminal sorts the SP numbers. If it is a short message in the server that improves the short message service, the ordering is implemented by the server, and the ordered SP number database is sent to the terminal.
  • the SP numbers can be sorted in real time or periodically. The sorting method is, for example, each time an SP number appears in a text message, the number of occurrences is increased by 1, and then the number is sorted according to the number of occurrences of the SP number.
  • the SP number database includes: SP numbers starting with 955 and SP numbers starting with 106.
  • the former SP number beginning with 955
  • the latter SP number beginning with 106
  • SP numbers starting with 955 and SP numbers starting with 106 are sorted according to the frequency of occurrence of SP numbers in the received service text messages. That is, the higher the frequency of an SP number in a text message, the higher the ranking. It should be noted that this is just an example, and it can also be sorted in other ways, such as sorting by the SP number, etc. SP numbers starting with 955 and SP numbers starting with 106 can also be mixed. In addition, It is not necessary to sort the SP numbers. In the case that the SP numbers in the SP number database are sorted according to the frequency of occurrence, when the SP numbers are matched, the SP number with a higher frequency is preferentially matched, which can improve the matching efficiency.
  • the SP number database may include all or part of the SP numbers filed by the Ministry of Industry and Information Technology.
  • the SP number database includes the following SP numbers:
  • SP number can be stored in the SP number database, and the SP number and users (China Merchants Bank, Industrial Securities, etc.) using the SP number can also be stored.
  • the sender number of the short message can be obtained from the Src_ID field of the CMPP_SUBMIT message.
  • the Src_ID field usually contains the service code of the SP or a long number prefixed with the service code.
  • the SMS gateway completely fills the number into the corresponding source_addr field of the Submit_SM message of the SMPP (Short Message Peer to Peer, Peer to Peer) protocol. The number will eventually be displayed on the user terminal as the calling number of the SMS (that is, the sender number).
  • the method before grouping the short messages according to the SP number of the short message, the method further includes: obtaining the information of the short message provider from the short message content;
  • the provider information is identity attribute information
  • the provider information of the short message is the identity attribute information of the sender of the short message.
  • the short message is sent to the user by "China Merchants Bank”
  • the provider of the short message is "China Merchants Bank”.
  • Service text messages usually require the content provider to clearly indicate their name in the text message to the user. Therefore, the provider information of the short message can be obtained from the content of the short message.
  • the step 102 includes: grouping the short messages according to the SP number of the short message and the provider information of the short message.
  • the solution provided in this embodiment groups the short messages according to the SP number and the information of the short message provider at the same time, and can distinguish the short messages from the same SP number but different providers of the short messages. For example, different businesses of the same company may use the same SP number, but the providers of the SMS are different, and you can distinguish them at this time.
  • the name of the short message provider is usually abbreviated and marked for highlighting, such as placing the short message provider information in the symbol "[]".
  • the obtaining the information of the short message provider from the content of the short message includes identifying a target identifier in the content of the short message, and using the information marked by the target identifier as the provision of the short message. ⁇ ⁇ Information.
  • the target identifier includes, but is not limited to, the symbol “[]”, and the information in the symbol “[]” is the information marked by the target identifier.
  • the target identifier is preset by the Ministry of Industry and Information Technology or industry rules or service providers.
  • the method further includes, when the target identifier does not exist in the content of the short message, searching a local index table according to the SP number of the short message, and obtaining a provision corresponding to the SP number
  • the provider information is used as the candidate provider information
  • the candidate provider information is matched with the content of the short message
  • the matched candidate provider information is used as the provider information of the short message. If all candidate provider information does not match the content of the short message, the short message has no provider information, and the short message is not grouped at this time, or the short message is grouped by other methods.
  • the local index table contains multiple indexes, and each index contains the SP number, provider information, and grouping information.
  • the provider information is inconsistent. That is, the same SP number may match multiple candidate provider information.
  • it can be used to filter short messages that do not include the provider information in the short message content in a standardized manner (for example, the provider information is not placed in the symbol "[]").
  • the provider information corresponding to its SP number can be found in the index table as the alternative provider information, and then the existence of alternative provider information is found in the short message. If it exists, it is used as the provider information of the short message. .
  • the grouping the short message according to the SP number of the short message and the provider information of the short message includes:
  • index table An example of the index table is as follows:
  • 10690228 is the SP number
  • "Amazon” is the provider information of the short message, corresponding to group 1. If the SP number of a text message is "10690228" and the provider information is "Amazon”, it will be classified into group 1 after matching the index table. If the SP number of a text message is "10690298" and the extracted provider information is "ZTE”, it is classified into group 2. If the SP number of a text message is "95555”, the extracted provider information is "China Merchants Bank”, and when matching with the index table, it is found that there is no matching group in the index table, then a new group 3 is created and the message is classified into the group 3. Add an index to the index table, 95555 China Merchants Bank Group 3. The index table looks like this:
  • the grouping the short messages according to at least the service provider number of the short message includes: grouping the short messages with the same SP number into one group.
  • the method further includes combining and displaying the short messages of the same group.
  • the combined display includes: displaying in the same short message display interface.
  • This display mode is convenient for users to view information from the same SMS provider at the same time. Especially when there is an association relationship between text messages, it is more convenient for users to check in parallel.
  • an embodiment of the present application provides a short message grouping method, which includes steps 301 to 311.
  • step 301 a short message is received.
  • step 302 it is determined whether the short message is a push message. Based on the determination result that the short message is a push short message, proceed to step 303; based on the determination result that the short message is not a push short message, step 311 is performed.
  • step 303 determine whether the short message is a service short message. For example, identify whether the sender number of the short message is a number starting with 106 or 955. Based on the determination result that the short message is a service short message, proceed to step 304; based on the short message is not a service If the result is a short message-like judgment, step 311 is executed.
  • step 304 the sender number of the short message is matched with the SP number in the local SP number database.
  • This step is used to obtain the SP number of the short message from the sender number of the short message.
  • the matching method is to determine whether the sender number of the short message contains the SP number in the SP number database. In an embodiment, if the SP number to be matched is 5 digits, it is sequentially judged whether any consecutive 5 digits of the sender number of the short message are the SP number, based on the determination result that there are 5 consecutive digits consistent with the SP number, Use this SP number as the SP number for this message.
  • step 305 it is determined whether the matching is successful. Based on the determination result of the successful matching, the matched SP number is obtained, and step 306 is performed; based on the determination result of the unsuccessful matching, step 311 is performed.
  • step 306 the provider information of the short message is extracted from the content of the short message.
  • the target identifier in the content of the short message is identified, and the information marked by the target identifier is used as the provider information of the short message.
  • step 307 the short messages are grouped according to the SP number of the short message and the provider information of the short message. First, the matched SP number and the provider information of the short message are matched with the local index table.
  • the index is successfully matched, and the group corresponding to the index is used as the group of the short message.
  • step 308 it is determined whether the matching is successful in step 307. Based on the determination result of the successful matching, step 309 is performed; based on the determination result of the unsuccessful matching, step 310 is performed.
  • step 309 the short message is placed under the matched group, and step 311 is performed.
  • step 310 a new group is created, the short message is classified into the newly created group, an index is created in an index table, and the newly created index corresponds to the newly created group.
  • step 311 the session ends.
  • step 306 may not be performed, that is, the provider information of the short message is not extracted.
  • step 307 the short messages are grouped directly according to the SP number of the short message, that is, according to the SP number of the short message. Matches the local index table.
  • step 306 when the provider information of the short message is extracted from the content of the short message, the target identifier is "[]", and the extraction method is: converting the short message content into a character string, and scanning after going there , Extract the information contained in "[]", as shown in FIG. 4, including steps 401 to 405.
  • step 401 use a string search function to find the first "[", and record the first character subscript, that is, the character subscript corresponding to "[";
  • step 402 a string search function is used to find the first "]", and the second character subscript is recorded, that is, the character subscript corresponding to "]".
  • step 403 it is determined whether the second character index is greater than the first character index. Based on the determination result that the second character index is greater than the first character index, proceed to step 404; based on the second character index being not greater than the first character If the result of the subscript is determined, step 405 is performed.
  • a string interception function is used to intercept a character string between the first character subscript and the second character subscript.
  • step 405 the session ends.
  • the alternative provider information uses the alternative provider information to match the content of the short message (you can use the string matching method to match): If the content of the short message matches the information of the alternative provider, the matched information of the alternative provider is used as the information of the short message provider. If the information of the alternative provider cannot be matched in the content of the short message, other methods can be used. Group the message or leave it ungrouped.
  • the above-mentioned provision of the corresponding SMS SP number in the index table can be performed only on some SP numbers in the SP number database (for example, the SP numbers ranked higher, such as the SP number ranked first 15%).
  • the method of the provider information can also be performed on all SP numbers by the method of finding the provider information corresponding to the short message SP number in the index table.
  • the SP number database may be stored on a server in the cloud.
  • the terminal sends the sender number of the short message to the server, the server performs matching, and then sends the matched SP number to the terminal, as shown in FIG. 5
  • an embodiment of the present application provides a method for grouping short messages, including steps 501 to 511.
  • step 501 a short message is received.
  • step 502 it is determined whether the short message is a push message. Based on the determination result that the short message is a push short message, proceed to step 503; based on the determination result that the short message is not a push short message, step 511 is performed.
  • step 503 determine whether the short message is a service short message. For example, identify whether the sender number of the short message is a number starting with 106 or 955. Based on the determination result that the short message is a service short message, proceed to step 504; based on the short message is not a service. If the result is a short message-like judgment, step 511 is executed.
  • step 504 the sender number of the short message is sent to a server in the cloud.
  • the SP number database is stored on a server in the cloud, so the server in the cloud performs SP number matching.
  • the server in the cloud receives the SMS sender number, matches it with the SP number in the SP number database, and sends the matched SP number to the terminal. If the SP number is not matched, it notifies the terminal that the match failed;
  • step 505 if the SP number sent by the server in the cloud is received, and the SP number is used as the SP number of the short message, step 506 is performed; if the matching failure information is received, step 511 is performed.
  • step 506 the provider information of the short message is extracted from the content of the short message.
  • the target identifier in the content of the short message is identified, and the information marked by the target identifier is used as the provider information of the short message.
  • step 507 the short messages are grouped according to the SP number of the short message and the provider information of the short message.
  • the provider information of the short message matches the SP number and provider information of an index in the index table, It is determined that the SP number and the provider information match the index successfully, and the group corresponding to the index is used as the group of the short message.
  • step 508 it is determined whether the matching is successful in step 507. Based on the determination result of the successful matching, step 509 is performed; based on the determination result of the unsuccessful matching, step 510 is performed.
  • step 509 the short message is placed under the matched packet, and step 511 is performed.
  • step 510 a new group is created, the short message is classified into the newly created group, an index is created in an index table, and the newly created index corresponds to the newly created group.
  • step 511 the session ends.
  • step 506 may not be performed, that is, the provider information of the short message is not obtained, and the short message group is directly performed according to the matched SP number.
  • an embodiment of the present application provides a short message grouping device, which includes a number matching module 601 and a group determination module 602.
  • the number matching module 601 is configured to obtain the SP number of the short message from the sender number of the short message.
  • the group determination module 602 is configured to group the short messages according to at least the SP number of the short messages.
  • the short message grouping device further includes a number identification module 600, and the number identification module 600 is configured to identify whether the short message is a service short message, for example, to determine the sending of the short message. Is the first 3 digits of the party number 955 or 106?
  • the short message grouping device further includes: an SP number management module 603.
  • the SP number management module 603 is configured to manage the SP numbers in the SP number database; for example, modify, add, or delete SP numbers according to user operations.
  • the number matching module 601 obtaining the SP number of the short message from the sender number of the short message includes: matching the sender number of the short message with the SP number in the SP number database, and using the matched SP number as SP number of the short message.
  • the short message grouping device further includes a short message content extraction module 604.
  • the short message content extraction module 604 is configured to obtain the information of the short message provider from the content of the short message.
  • the grouping determining module 602 grouping the short message according to at least the SP number of the short message includes: grouping the short message according to the service provider number of the short message and the provider information of the short message.
  • the short message grouping device further includes: an index table management module 605.
  • the grouping determining module 602 grouping the short message according to the short message service provider number and the short message provider information includes: according to the short message service provider number and the short message provider information and local information.
  • the index table is matched, if the corresponding group is matched, the short message is classified into the matched group, if the corresponding group is not matched, a new group is created, the short message is classified into the newly created group, and Notify the index table management module 605 to create a new index in the index table corresponding to the newly created group.
  • the index table management module 605 is configured to manage the index table and, upon receiving a notification from the group determination module 602, create a new index in the index table corresponding to the newly created group.
  • an embodiment of the present application provides a short message grouping device 80 including a memory 810 and a processor 820.
  • the memory 810 stores a program.
  • the program is read and executed by the processor 820, Implement the short message grouping method described in any of the embodiments.
  • An embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement any The short message grouping method described in the embodiment.
  • Computer storage medium includes both volatile and nonvolatile implementations in any method or technology used to store information such as computer-readable instructions, data structures, program modules or other data.
  • Computer storage media include, but are not limited to, Random Access Memory (RAM), Read-Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Flash memory or other memory technology, Compact Disc-Ready-Only Memory (CD-ROM), Digital Video Disc (DVD), or other optical disc storage, magnetic box, magnetic tape, disk storage, or other magnetic storage device Or any other medium that can be used to store desired information and can be accessed by a computer.
  • a communication medium typically contains computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium .

Abstract

本申请公开了一种短信分组方法及装置、计算机可读存储介质，该短信分组方法包括：从短信的发送方号码中获取所述短信的服务提供商号码；至少根据所述短信的服务提供商号码对所述短信进行分组。

Description

短信分组方法及装置、计算机可读存储介质
本申请要求在2018年06月05日提交中国专利局、申请号为201810568617.1的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及但不限于通信领域，例如涉及一种短信分组方法及装置、计算机可读存储介质。
背景技术
随着无线通信技术的迅速发展，短信在人们的生活中得到了越来越广泛的应用，成为了信息交流的一种重要手段。当存在大量短信时，为了方便查阅，有必要对短信进行分组。目前终端一般直接根据短信的发送方号码对短信进行分组，这导致大量的服务类短信无法正确分组，给用户查找和管理带来了诸多不便。
如图1所示，第1条、第2条短信都是兴业证券的通知短信，由于其发送方号码不同，被分在了不同的组中，第6条、第9条短信都是来自ZTE的通知短信，由于其发送方号码不同，被分在了不同的组中。因此，有必要提供一种短信分组方法，提高分组的准确性。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本申请一实施例提供了一种短信分组方法及装置、计算机可读存储介质，提高分组的准确性。
本申请一实施例提供一种短信分组方法，包括：从短信的发送方号码中获取所述短信的服务提供商号码；至少根据所述短信的服务提供商号码对所述短信进行分组。
本申请一实施例提供一种短信分组装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现任一实施例所述的短信分组方法。
本申请一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现任一实施例所述的短信分组方法。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图说明
附图用来提供对本申请技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1为相关技术中短信分组示意图；
图2为本申请一实施例提供的短信分组方法流程图；
图3为本申请一实施例提供的短信分组方法流程图；
图4为本申请一实施例提供的提取短信的提供者信息的流程图；
图5为本申请另一实施例提供的短信分组方法流程图；
图6a～图6e为本申请实施例提供的短信分组装置框图；
图7为本申请一实施例提供的短信分组示意图；
图8为本申请一实施例提供的短信分组装置框图。
具体实施方式
下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
如图2所示，本申请一实施例提供一种短信分组方法，包括步骤201和步骤202。
在步骤201中，从短信的发送方号码中获取所述短信的服务提供商(Service Provider，SP)号码。
在步骤202中，至少根据所述短信的SP号码对所述短信进行分组。
本实施例提供的短信分组方法，根据SP号码对短信进行分组，使得来自同一SP号码的短信能分到同一组，相比相关技术中直接根据短信的发送方号码对短信进行分组的方法，本申请使得来自同一SP号码但短信发送方号码不同的短信能分到同一组，提高了分组的准确性，方便用户进行查找和管理。另外，本实施例不需修改相关技术中的通信协议，不增加基站或核心网的接口与信令负担。
在一实施例中，步骤201之前，还包括：判断所述短信是否为PUSH(推送)短信，基于所述短信是PUSH短信的判断结果，执行步骤201。需要说明的是，也可以不执行该步骤。
其中，所述步骤201中，从短信的发送方号码中获取所述短信的SP号码包括：在所述短信为服务类短信的情况下，从所述短信的发送方号码中获取所述短信的SP号码。其中，根据相关技术中的规范要求，服务类短信需以955或106开头。因此，可以检查短信的前3位是否为955或106，当然，也可以检查短信的前2位是否为95或10，或者，检查短信的第1位是否为9或1，从而对短信进行筛选，只对服务类短信使用后续分组方法，提高分组效率。当然，如果规范改变(服务类短信的号码规则改变)，依据改变后的规范检查短信是否为服务类短信。
在一实施例中，所述步骤201中，从短信的发送方号码中获取所述短信的SP号码包括：将所述短信的发送方号码与预存的SP号码库中的SP号码进行匹配，将匹配到的SP号码作为所述短信的SP号码。需要说明的是，短信的发送方号码非短信的SP号码，短信的发送方号码中除了包括SP号码外，还包括短信网关添加的号码信息。比如，给号码13768057893的用户发送短信，其SP号码为：106575257205。在经过短信网关时，短信网关在其末尾添加了160001。于是，用户收到该短信时，看到短信的主叫号码是：106575257205160001。其中，将短信的发送方号码与预存的SP号码库中的SP号码进行匹配包括：判断短信的发送方号码中是否包含SP号码库中的SP号码，基于所述短信的发送方号码中包含SP码库中的SP号码的判断结果，确定该SP号码为短信的SP号码。举例来说，短信的发送方号码为106575257205160001，与SP号码库中的SP号码进行匹配，匹配到106575257205，则该短信的SP号码为106575257205。又比如，短信的发送方号码为1069035695562，与SP号码库中的SP号码进行匹配，匹配到96652，则该短信的SP号码为95562。其中，服务提供商号码库可以存储在终端内，也可以存储在云端。存储在云端时，从短信的发送方号码中获取所述短信的SP号码包括：将短信的发送方号码发送到云端服务器，接收云端服务器返回的匹配到的SP号码，将接收到的SP号码作为所述短信的SP号码。
其中，SP号码库中包含多个SP号码。在一实施例中，所述SP号码库中的SP号码按照其在短信中的出现频率进行排序。所述短信为：终端收到的历史短信，或者，提供短信服务的服务器中所有的短信。如果是终端收到的历史短信，则由终端对SP号码进行排序。如果是提高短信服务的服务器中的短信，则排序由服务器实现，并将排好序的SP号码库发送给终端。对SP号码的排序可以是实时的，也可以是周期性进行，排序方式比如为：SP号码在短信中每出现一次，将其出现次数加1，然后根据SP号码的出现次数进行排序。SP号码库包括：955开头的SP号码、106开头的SP号码。在一实施例中，前者(955开头的SP号码)的优先级高于后者(106开头的SP号码)。955开头的SP号码和106开头的SP号码均根据接收到的服务类短信中SP号码的出现频率由高到低进行排 序。即某个SP号码在短信中出现的频率越高，排序越靠前。需要说明的是，此处仅为示例，也可以按照其他方式进行排序，比如按照SP号码的大小进行排序，等等，955开头的SP号码、106开头的SP号码也可以混合排列，另外，也可以不对SP号码进行排序。在SP号码库中的SP号码按照出现频率进行排序的情况下，对SP号码匹配时，优先匹配的是出现频率较高的SP号码，可以提高匹配效率。
其中，SP号码库可以包含工业和信息化部备案的所有或部分SP号码，举例来说，SP号码库中比如包括如下SP号码：
10657中国移动自营业务号码
10658中国移动自营业务号码
10655中国联通自营业务号码
10659中国电信自营业务号码
10690002北京亚联电信网络有限公司
10690007上海恒瑞网络信息有限公司
10690008北京通天世纪科技有限公司
95555招商银行
95562兴业证券
需要说明的是，SP号码库中可以仅存储SP号码，也可以存储SP号码及使用该SP号码的用户(招商银行、兴业证券等)。
其中，不同类型的SP号码用途参考下表1。
其中，短信的发送方号码可以从CMPP_SUBMIT消息的Src_ID字段中获取。Src_ID字段通常包含SP的服务代码或前缀为服务代码的长号码。短信网关将该号码完整地填到SMPP(Short Message Peer to Peer，对等短消息)协议的Submit_SM消息相应的source_addr字段，该号码最终将在用户终端上显示为短信的主叫号码(即发送方号码)。
在一实施例中，所述步骤102，至少根据所述短信的SP号码对所述短信进行分组前，还包括：从所述短信的内容中获取所述短信的提供者信息；其中，所述提供者信息为身份属性信息，短信的提供者信息即短信的发送方的身份属性信息。比如，短信由“招商银行”发送给用户，短信的提供者即“招商银行”。服务类短信通常要求短信内容的提供者在给用户的短信中明确注明其名称。因此，可以从短信的内容中获取所述短信的提供者信息。
所述步骤102包括：根据所述短信的SP号码和所述短信的提供者信息对所述短信进行分组。
表1 SP号码规范
Figure PCTCN2019087060-appb-000001
本实施例提供的方案，同时根据SP号码和短信的提供者信息对短信进行分组，可以对来自相同的SP号码但短信的提供者不同的短信进行区分。比如，同一公司的不同业务，可能会采用相同的SP号码，但短信的提供者不同，此时可以进行区分。
一般地，短信提供者的名称通常是简称，并加上标记以突出显示，比如将短信的提供者信息放在符号“【】”中。在一实施例中，所述从所述短信的内容中获取所述短信的提供者信息包括：识别所述短信的内容中的目标标识，将所述目标标识标注的信息作为所述短信的提供者信息。其中，所述目标标识包括但不限于符号“【】”，所述符号“【】”内的信息为所述目标标识标注的信息。一般地，所述目标标识由工信部或行业规则或服务提供商预设。
在一实施例中，所述方法还包括，在所述短信的内容中不存在所述目标标识的情况下，根据所述短信的SP号码查找本地的索引表，获取所述SP号码对应的提供者信息作为备选提供者信息，将所述备选提供者信息与所述短信的内容进行匹配，将匹配到的备选提供者信息作为所述短信的提供者信息。如果所有的备选提供者信息均与短信的内容不匹配，则该短信无提供者信息，此时不对短信分组，或者，采用其他方式对短信进行分组。本地的索引表中包含多条索引，每条索引包含SP号码、提供者信息以及分组信息。需要说明的是，可能存在多条索引中的SP号码一致，但提供者信息不一致。即同一SP号码可能匹配到多个备选提供者信息。该实施例中，可以用于筛选中未按照规范方式在短信内容中包含提供者信息的短信(比如未将提供者信息放在符号“【】”中)。此时，可以在索引表中查找到其SP号码对应的提供者信息作为备选提供者信息， 然后在短信中查找是否存在备选提供者信息，如果存在，将其作为该短信的提供者信息。
在一实施例中，所述根据所述短信的SP号码和所述短信的提供者信息对所述短信进行分组包括：
根据所述短信的SP号码和所述短信的提供者信息与本地的索引表进行匹配，如果匹配到对应的分组，将所述短信归入所匹配到的分组，如果未匹配到对应的分组，新建一个分组，并在所述索引表中新建一条与所述新建的分组对应的索引。
其中，索引表一个实例如下：
10690228亚马逊分组1
10690298ZTE分组2
以第一条索引为例，10690228为SP号码，“亚马逊”为短信的提供者信息，对应分组1。如果某条短信其SP号码为“10690228”，提供者信息为“亚马逊”，则与索引表匹配后，将其归类到分组1。如果某条短信其SP号码为“10690298”，提取的提供者信息为“ZTE”，则将其归类到分组2。如果某条短信其SP号码为“95555”，提取的提供者信息为“招商银行”，与索引表进行匹配时发现索引表中无匹配的分组，则新建一个分组3，将该短信归入分组3，在索引表中增加一条索引，95555招商银行分组3。此时索引表为如下所示：
10690228亚马逊分组1
10690298ZTE分组2
95555招商银行分组3
在一实施例中，所述至少根据所述短信的服务提供商号码对所述短信进行分组包括：将SP号码相同的短信分为一组。
在一实施例中，所述至少根据所述短信的服务提供商号码对所述短信进行分组之后，还包括，将同一组的短信进行合并显示。
在一实施例中，所述合并显示包括：在同一个短信显示界面中显示。这种显示方式，方便用户同时查看来自同一短信提供者的信息。尤其是短信之间存在关联关系时，更便于用户进行并行查看。
下面通过具体实施例对本申请作进一步说明。
如图3所示，本申请一实施例提供了一种短信分组方法，包括步骤301至步骤311。
在步骤301中，接收到一条短信。
在步骤302中，判断所述短信是否为push(推送)短信。基于所述短信为推送短信的判断结果，继续执行步骤303；基于所述短信不是推送短信的判断结果，执行步骤311。
在步骤303中，判断短信是否为服务类短信，比如，识别短信的发送方号码是否为106开头或955开头的号码，基于短信为服务类短信的判断结果，继续执行步骤304；基于短信不是服务类短信的判断结果，执行步骤311。
在步骤304中，将所述短信的发送方号码与本地SP号码库中的SP号码进行匹配。
该步骤用于从短信的发送方号码中获取短信的SP号码。匹配方式为判断短信的发送方号码中是否包含SP号码库中的SP号码。在一实施例中，如果待匹配的SP号码为5位，则依次判断短信的发送方号码中的任意连续5位是否为该SP号码，基于存在连续5位与该SP号码一致的判断结果，将该SP号码作为该短信的SP号码。
在步骤305中，判断是否匹配成功，基于匹配成功的判断结果，获取匹配到的SP号码，执行步骤306；基于匹配未成功的判断结果，执行步骤311。
在步骤306中，从所述短信的内容中提取短信的提供者信息。
在一实施例中，识别所述短信的内容中的目标标识，将所述目标标识标注的信息作为所述短信的提供者信息。
在步骤307中，根据短信的SP号码、短信的提供者信息对短信进行分组，首先根据匹配到的SP号码、短信的提供者信息与本地的索引表进行匹配。
在SP号码、提供者信息与索引表中某一索引的SP号码和提供者信息匹配成功的情况下，与该索引匹配成功，将该索引对应的分组作为短信的分组。
在步骤308中，判断步骤307中是否匹配成功，基于匹配成功的判断结果，执行步骤309；基于匹配未成功的判断结果，执行步骤310。
在步骤309中，将该条短信放到匹配到的分组下，执行步骤311。
在步骤310中，新建一个分组，将所述短信归入所述新建的分组，在索引表中新建一条索引，所述新建的索引与所述新建的分组对应。
在步骤311中，本次会话结束。
需要说明的是，在另一实施例中，也可以不执行步骤306，即不提取短信的提供者信息，在步骤307中，直接根据短信的SP号码对短信进行分组，即根据短信的SP号码与本地的索引表进行匹配。
在一实施例中，步骤306中，从所述短信的内容中提取短信的提供者信息时，目标标识为“【】”，提取方法为：将短信内容转换为字符串，从前往后进行扫描，提取“【】”中包含的信息，如图4所示，包括步骤401至步骤405。
在步骤401中，使用字符串查找函数找到第一个"【"，记录第一字符下标，即"【"对应的字符下标；
在步骤402中，使用字符串查找函数找到第一个"】"，记录第二字符下标，即"】"对应的字符下标。
在步骤403中，判断是否第二字符下标>第一字符下标，基于第二字符下标大于第一字符下标的判断结果，继续执行步骤404；基于第二字符下标不大于第一字符下标的判断结果，执行步骤405。
在步骤404中，使用字符串截取函数，截取第一字符下标和第二字符下标之间的字符串。
在步骤405中，本次会话结束。
需要说明的是，上述提取方法仅为示例，可以根据需要使用其他方法进行提取。
为避免可能的修改(比如要求使用“{}”而不是“【】”)导致误判，如果根据“【】”提取不到短信的提供者信息，则采用以下方法：
在索引表中找到该短信的SP号码对应的提供者信息，作为备选提供者信息，使用该备选提供者信息与短信的内容进行匹配(可采用字符串匹配的方法进行匹配)：如果在短信的内容中匹配到备选提供者信息，则将匹配到的备选提供者信息作为该短信的提供者信息；如果在短信的内容中匹配不到备选提供者信息，则可以使用其他方式对该短信进行分组，或者，不进行分组。
需要说明的是，可以仅对SP号码库中的部分SP号码(比如，排序靠前的SP号码，比如排序为前15％的SP号码)执行上述在索引表中找到该短信SP号码对应的提供者信息的方法，也可以对所有SP号码执行上述在索引表中找到该短信SP号码对应的提供者信息的方法。
在另一实施例中，SP号码库可以存储在云端的服务器，此时，终端将短信的发送方号码发送给服务器，由服务器进行匹配，然后将匹配到的SP号码发送给终端，如图5所示，本申请一实施例提供了一种短信分组方法，包括步骤501至步骤511。
在步骤501中，接收到一条短信。
在步骤502中，判断所述短信是否为push(推送)短信。基于所述短信为推送短信的判断结果，继续执行步骤503；基于所述短信不是推送短信的判断结果，执行步骤511。
在步骤503中，判断短信是否为服务类短信，比如，识别短信的发送方号码是否为106开头或955开头的号码，基于短信是服务类短信的判断结果，继续执行步骤504；基于短信不是服务类短信的判断结果，执行步骤511。
在步骤504中，将所述短信的发送方号码发送给云端的服务器。
本实施例中，SP号码库存储在云端的服务器，因此，由云端的服务器来进行SP号码的匹配。其中，云端的服务器接收到短信的发送方号码后，与SP号码库的SP号码进行匹配，将匹配到的SP号码发送给终端，如果未匹配到SP号码，则通知终端匹配失败；
在步骤505中，如果接收到云端的服务器发送的SP号码，将该SP号码作为所述短信的SP号码，执行步骤506；如果接收到匹配失败的信息，则执行步骤511。
在步骤506中，从所述短信的内容中提取短信的提供者信息。
在一实施例中，识别所述短信的内容中的目标标识，将所述目标标识标注的信息作为所述短信的提供者信息。
在步骤507中，根据短信的SP号码、短信的提供者信息对短信进行分组。
将短信的SP号码、短信的提供者信息与本地的索引表进行匹配，在短信的SP号码、短信的提供者信息与索引表中某一索引的SP号码和提供者信息匹配成功的情况下，确定SP号码、提供者信息与该索引匹配成功，将该索引对应的分组作为所述短信的分组。
在步骤508中，判断步骤507中是否匹配成功，基于匹配成功的判断结果，执行步骤509；基于匹配未成功的判断结果，执行步骤510。
在步骤509中，将该条短信放到匹配到的分组下，执行步骤511。
在步骤510中，新建一个分组，将所述短信归入所述新建的分组，在索引表中新建一条索引，所述新建的索引与所述新建的分组对应。
在步骤511中，本次会话结束。
需要说明的是，在另一实施例中，也可以不执行步骤506，即不获取短信的提供者信息，直接根据匹配到的SP号码进行短信分组。
如图6a所示，本申请一实施例提供一种短信分组装置，包括：号码匹配模块601和分组判别模块602。
所述号码匹配模块601设置为，从短信的发送方号码中获取所述短信的SP号码。
所述分组判别模块602设置为，至少根据所述短信的SP号码对所述短信进行分组。
在另一实施例中，如图6b所示，所述短信分组装置还包括号码识别模块600，所述号码识别模块600设置为，识别所述短信是否为服务类短信，比如，判断短信的发送方号码的前3位是否为955或106。
在另一实施例中，如图6c所示，所述短信分组装置还包括：SP号码管理模块603。
所述SP号码管理模块603设置为，对SP号码库中的SP号码进行管理；比如，根据用户操作修改、增删SP号码。
所述号码匹配模块601从短信的发送方号码中获取所述短信的SP号码包括：将所述短信的发送方号码与所述SP号码库中的SP号码进行匹配，将匹配到的SP号码作为所述短信的SP号码。
在另一实施例中，如图6d所示，所述短信分组装置还包括：短信内容提取模块604。
所述短信内容提取模块604设置为，从所述短信的内容中获取所述短信的提供者信息。
所述分组判别模块602至少根据所述短信的SP号码对所述短信进行分组包括：根据所述短信的服务提供商号码和所述短信的提供者信息对所述短信进行分组。
在另一实施例中，如图6e所示，所述短信分组装置还包括：索引表管理模块605。
所述分组判别模块602根据所述短信的服务提供商号码和所述短信的提供者信息对所述短信进行分组包括：根据所述短信的服务提供商号码和所述短信的提供者信息与本地的索引表进行匹配，如果匹配到对应的分组，将所述短信归入所匹配到的分组，如果未匹配到对应的分组，新建一个分组，将所述短信归入所述新建的分组，并通知所述索引表管理模块605在所述索引表中新建一条与所述新建的分组对应的索引。
所述索引表管理模块605设置为，对所述索引表进行管理，以及接收到所述分组判别模块602的通知后，在所述索引表中新建一条与所述新建的分组对应的索引。
下面通过一个实例进一步说明本申请。以图1中的短信为例，内容中带“【ZTE】”，分别来自106902989892652、106902989882137两个号码的短信，与SP号码库中的SP号码进行匹配，其匹配到的SP号码均为10690298，而这两条短信的提供者信息均为“ZTE”，因此，被分到了同一组。来自“兴业证券”的5条短信中，第一条短信的发送方号码为95562，其余短信的发送方号码为1069035695562，其匹配到的SP号码均为95562，其短信的提供者信息均为“兴业证券”，因此，也被归类到同一组。归类后的短信分组如图7所示。在用户点击图7中第一组的短信的情况下，来自“ZTE”的两条短信在同一短信显示界面进行显示，在用户点击图7中第二组的短信的情况下，来自“兴业证券”的5条短信在同一短信显示界面进行显示。需要说明的是，图7中未示出图1中其他短信的分组。
如图8所示，本申请一实施例提供一种短信分组装置80，包括存储器810和处理器820，所述存储器810存储有程序，所述程序在被所述处理器820读取执行时，实现任一实施例所述的短信分组方法。
本申请一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现任一实施例所述的短信分组方法。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于随机存取存储器(Random Access Memory，RAM)、只读存储器(Read Only Memory，ROM)、带电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、闪存或其他存储器技术、只读光盘(Compact Disc Read-Only Memory，CD-ROM)、数字多功能盘(Digital Video Disc，DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。

Claims (16)

  1. 一种短信分组方法，包括：
    从短信的发送方号码中获取所述短信的服务提供商号码；
    至少根据所述短信的服务提供商号码对所述短信进行分组。
  2. 根据权利要求1所述的短信分组方法，其中，所述从短信的发送方号码中获取所述短信的服务提供商号码包括：在所述短信为服务类短信的情况下，从所述短信的发送方号码中获取所述短信的服务提供商号码。
  3. 根据权利要求1所述的短信分组方法，其中，所述从短信的发送方号码中获取所述短信的服务提供商号码包括：将所述短信的发送方号码与预存的服务提供商号码库中的服务提供商号码进行匹配，将匹配到的服务提供商号码作为所述短信的服务提供商号码。
  4. 根据权利要求3所述的短信分组方法，其中，所述将所述短信的发送方号码与预存的服务提供商号码库中的服务提供商号码进行匹配包括：
    判断所述短信的发送方号码中是否包含所述服务提供商号码库中的服务提供商号码，基于所述短信的发送方号码中包含所述服务提供商号码库中的服务提供商号码的判断结果，确定所述短信的发送方号码中包含的服务提供商号码为所述短信的服务提供商号码。
  5. 根据权利要求3所述的短信分组方法，其中，所述服务提供商号码库中的服务提供商号码按照其在短信中的出现频率进行排序。
  6. 根据权利要求1至5中任一项所述的短信分组方法，所述至少根据所述短信的服务提供商号码对所述短信进行分组前，还包括：
    从所述短信的内容中获取所述短信的提供者信息；
    所述至少根据所述短信的服务提供商号码对所述短信进行分组包括：
    根据所述短信的服务提供商号码和所述短信的提供者信息对所述短信进行分组。
  7. 根据权利要求6所述的短信分组方法，其中，所述提供者信息为身份属性信息。
  8. 根据权利要求6所述的短信分组方法，其中，所述从所述短信的内容中获取所述短信的提供者信息包括：识别所述短信的内容中的目标标识，将所述目标标识标注的信息作为所述短信的提供者信息。
  9. 根据权利要求8所述的短信分组方法，其中，所述目标标识为符号“【】”，所述符号“【】”内的信息为所述目标标识标注的信息。
  10. 根据权利要求8所述的短信分组方法，所述从所述短信的内容中获取所述短信的提供者信息还包括：
    在所述短信的内容中不存在所述目标标识的情况下，根据所述短信的服务提供商号码查找本地的索引表，获取所述服务提供商号码对应的提供者信息作 为备选提供者信息，将所述备选提供者信息与所述短信的内容进行匹配，将匹配到的备选提供者信息作为所述短信的提供者信息。
  11. 根据权利要求6所述的短信分组方法，其中，所述根据所述短信的服务提供商号码和所述短信的提供者信息对所述短信进行分组包括：
    将所述短信的服务提供商号码和所述短信的提供者信息与本地的索引表进行匹配；在匹配到所述索引表中的对应分组的情况下，将所述短信归入所匹配到的分组；在未匹配到所述索引表中的对应分组的情况下，新建一个分组，将所述短信归入所述新建的分组，并在所述索引表中新建一条与所述新建的分组对应的索引。
  12. 根据权利要求1至4任一项所述的短信分组方法，其中，所述至少根据所述短信的服务提供商号码对所述短信进行分组包括：
    将服务提供商号码相同的短信分为一组。
  13. 根据权利要求1至4任一项所述的短信分组方法，所述至少根据所述短信的服务提供商号码对所述短信进行分组之后，还包括：将同一组的短信进行合并显示。
  14. 根据权利要求13所述的短信分组方法，其中，所述合并显示包括：在同一个短信显示界面中显示。
  15. 一种短信分组装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现如权利要求1至14中任一项所述的短信分组方法。
  16. 一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现如权利要求1至14中任项一所述的短信分组方法。
PCT/CN2019/087060 2018-06-05 2019-05-15 短信分组方法及装置、计算机可读存储介质 WO2019233255A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810568617.1 2018-06-05
CN201810568617.1A CN109089227A (zh) 2018-06-05 2018-06-05 一种短信分组方法及装置、计算机可读存储介质

Publications (1)

Publication Number Publication Date
WO2019233255A1 true WO2019233255A1 (zh) 2019-12-12

Family

ID=64839372

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/087060 WO2019233255A1 (zh) 2018-06-05 2019-05-15 短信分组方法及装置、计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN109089227A (zh)
WO (1) WO2019233255A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109089227A (zh) * 2018-06-05 2018-12-25 中兴通讯股份有限公司 一种短信分组方法及装置、计算机可读存储介质
CN109587353B (zh) * 2018-12-17 2020-12-04 珠海市小源科技有限公司 短信号码归属信息的识别方法、装置及存储介质
CN109947944A (zh) * 2019-03-18 2019-06-28 北京小米移动软件有限公司 短信显示方法、装置以及存储介质
CN110046014A (zh) * 2019-03-27 2019-07-23 维沃移动通信有限公司 一种界面显示方法及终端设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1529524A (zh) * 2003-09-26 2004-09-15 移动通讯中的短消息分类方法
CN101754182A (zh) * 2008-12-19 2010-06-23 北京网秦天下科技有限公司 基于分组的网络通讯录的实现方法及系统
CN103179499A (zh) * 2011-12-22 2013-06-26 中国电信股份有限公司 服务提供商服务号码的号码显示处理方法与系统
US9232373B1 (en) * 2013-10-21 2016-01-05 West Corporation Providing data messaging support by intercepting and processing received short message service (SMS) messages at a customer support service
CN109089227A (zh) * 2018-06-05 2018-12-25 中兴通讯股份有限公司 一种短信分组方法及装置、计算机可读存储介质

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110317684A1 (en) * 2010-06-24 2011-12-29 Lazzaro Nicholas P Systems and methods for terminating communication requests
CN104202473B (zh) * 2014-08-25 2017-07-07 华为技术有限公司 合并会话的方法及移动终端
CN105847555A (zh) * 2016-03-24 2016-08-10 珠海市小源科技有限公司 短信会话合并方法及其系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1529524A (zh) * 2003-09-26 2004-09-15 移动通讯中的短消息分类方法
CN101754182A (zh) * 2008-12-19 2010-06-23 北京网秦天下科技有限公司 基于分组的网络通讯录的实现方法及系统
CN103179499A (zh) * 2011-12-22 2013-06-26 中国电信股份有限公司 服务提供商服务号码的号码显示处理方法与系统
US9232373B1 (en) * 2013-10-21 2016-01-05 West Corporation Providing data messaging support by intercepting and processing received short message service (SMS) messages at a customer support service
CN109089227A (zh) * 2018-06-05 2018-12-25 中兴通讯股份有限公司 一种短信分组方法及装置、计算机可读存储介质

Also Published As

Publication number Publication date
CN109089227A (zh) 2018-12-25

Similar Documents

Publication Publication Date Title
WO2019233255A1 (zh) 短信分组方法及装置、计算机可读存储介质
US10219150B2 (en) Method, client terminal and server for establishing communication
CN109640312B (zh) “黑卡”识别方法、电子设备及计算机可读取存储介质
CN105898085B (zh) 骚扰通信账号的识别方法及装置
CN101072067A (zh) 实现短消息分类发送、接收、显示的装置及方法
CN102438205B (zh) 一种基于移动用户行为的业务推送的方法与系统
CN105847555A (zh) 短信会话合并方法及其系统
WO2021129446A1 (zh) 一种搜网方法及装置、存储介质
CN102968430A (zh) 用于在地址簿中自动产生和管理组的方法和设备
CN105989457A (zh) 一种信息查询方法及装置
CN111753210A (zh) 资源推送方法、装置、计算机设备及计算机可读存储介质
US11599673B2 (en) Ascertaining network devices used with anonymous identifiers
CN107360331B (zh) 短信显示方法
JP6197112B2 (ja) モバイルネットワーク機器用の通信事業者の自動検出
CN105120046A (zh) 一种根据新增号码的备注信息创建通讯录的方法及装置
US20170272402A1 (en) Method and electronic device for searching for special contacts
WO2018152978A1 (zh) 提醒更改账号绑定电话号码的方法及装置和计算机存储介质
CN107332999A (zh) 一种陌生来电号码识别方法及装置
US20170171128A1 (en) Method and electronic device for email processing
CN108924840B (zh) 黑名单管理方法、装置及终端
WO2021129849A1 (zh) 日志处理方法、装置、设备和存储介质
CN109121137B (zh) 双卡终端的用户号码使用类型识别方法及装置
CN115718676A (zh) 一种GoIP设备电子数据的恢复方法和系统
CN112689249B (zh) 短信的发送方法及装置、系统、存储介质、电子设备
CN110493735B (zh) 一种短信处理方法及装置

Legal Events

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

Ref document number: 19815179

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 16/04/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19815179

Country of ref document: EP

Kind code of ref document: A1