WO2011076000A1 - 编码格式识别、转换方法及装置、处理方法及系统 - Google Patents
编码格式识别、转换方法及装置、处理方法及系统 Download PDFInfo
- Publication number
- WO2011076000A1 WO2011076000A1 PCT/CN2010/075024 CN2010075024W WO2011076000A1 WO 2011076000 A1 WO2011076000 A1 WO 2011076000A1 CN 2010075024 W CN2010075024 W CN 2010075024W WO 2011076000 A1 WO2011076000 A1 WO 2011076000A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- source
- account
- encoding format
- information
- target
- Prior art date
Links
Classifications
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a coding format identification method and apparatus, a conversion method and apparatus, a processing method and a system. Background technique
- Coding is a technique that is often used in communications.
- the encoding format (data_coding) of communication data is usually various, such as ASCII, UNICODE, 7BIT, and so on. Users typically communicate with other users based on a communication protocol with the communication carrier.
- a communication protocol may involve multiple encoding formats of communication data.
- the encoding formats used by different communication protocols may be the same or different, and the encoding methods used in different regions may be the same or different.
- the encoding format conversion processing method commonly used in the prior art mainly includes: For a specific account, a single-to-single conversion is performed, for example, the account 1 sends a message to the account 2, and the prior art mainly includes: 1 The location is area A, and the encoding format UNICODE used by account 1 is 10 in the communication protocol of the regional A specification;
- the account number of the account 2 is B, and the encoding format used by account 2 is 7 in the communication protocol of the national B specification;
- the inventor has found that at least the following technical problems exist in the prior art: Although the prior art can implement the conversion between the encoding formats, since it only determines the encoding format according to the encoding format identifier value carried in the message, It is prone to conversion errors, resulting in users not being able to use the relevant business.
- the identifier of the area A defines UNICODE is 10
- the area C The value of the 7BIT is defined as 10, and the prior art is based on the same identification value of the two different encoding formats, and the two encoding formats are mistakenly considered to be the same, and the conversion is not performed on the current message, resulting in an error; Single conversion processing results in scalability and configuration flexibility, and it is difficult to adapt to the continuous development of communication technology and coding technology. Summary of the invention
- the present invention provides a coding format identification and conversion method and apparatus, a processing method and a system thereof, which are used to solve the technical problems in the prior art that the coding format identification is inaccurate, the conversion is error-prone, the system is expanded, and the configuration is inflexible.
- an encoding format identifying method includes:
- the coding format information of the first account group includes: a home zone to which each account in the first account group belongs, a communication protocol specified by each home zone, and each coding format description information specified by each communication protocol;
- the source encoding format for finding the source information according to the source account and the source information includes:
- the source encoding format description information is used to identify a source encoding format used by the source information.
- each encoding format description information specified by each communication protocol includes: an encoding format corresponding to each encoding format identifier value and each encoding format identifier value;
- the encoding format description information carried in the source information is a source encoding format identifier value, and the encoding format description information carried in the source information is matched with each encoding format description information specified by the matching communication protocol.
- the source encoding format description information includes: identifying, from each of the encoding format identifier values specified by the matched communication protocol, an identifier value that is the same as the encoding format identifier value carried in the source information;
- the source encoding format used by the source encoding format description information to identify the source information includes: determining, according to the found encoding format corresponding to the identifier value, a source encoding format used by the source information.
- the method further comprises:
- the source information is processed according to a preset transmission processing policy.
- an encoding format conversion method includes:
- a conversion processing policy capable of converting the source encoding format into a target encoding format; wherein the source encoding format is an encoding format used by the source information;
- the target account receives the source information sent based on the source account; And converting the source information into target information in the target encoding format according to the conversion processing policy.
- the code conversion information of the second account group includes: coding format description information supported by each account in the second account group, each coding format supported by the communication system to which the target account belongs, and each coding format to the target Each conversion processing strategy for encoding format conversion;
- the converting processing information for converting the source encoding format into the target encoding format from the encoding conversion information of the second account group includes:
- the method further comprises:
- the source information is processed according to a preset transmission processing policy.
- the encoding format processing method includes: presetting the encoding format information of the first account group; and presetting the encoding conversion information of the second account group; the method further includes:
- a conversion processing policy capable of converting the source encoding format into a target encoding format; wherein the source encoding format is an encoding format used by the source information;
- the target account receives the source information sent based on the source account; and converts the source information into target information in the target encoding format according to the conversion processing policy.
- the encoding format identifying device includes: a first storage module, a first search module, a second search module, and a third search module;
- the first storage module is configured to store the encoding format information of the preset first account group;
- the first searching module is configured to: find, according to the source account, from the encoding format information of the first account group a home area to which the source account belongs;
- the second searching module is configured to: according to the attribution area to which the source account belongs, find a communication protocol specified by the home area to which the source account belongs from the coding format information of the first account group;
- the third search module is configured to search, according to the source account and the source information, from a coding format information of the first account group, a communication protocol specified by a home zone to which the source account belongs, The source encoding format used by the source information.
- the coding format information of the first account group includes: a home zone to which each account in the first account group belongs, a communication protocol in each home zone, and each coding format description information specified by each communication protocol;
- the third search module further includes: a sub-look processing module and an identification module, where the sub-look processing module is configured to determine, according to the source account, that the source account is in a home zone to which the source account belongs a source communication protocol used; finding a communication protocol matching the source communication protocol from a communication protocol specified by the home zone to which the source account belongs;
- An identification module configured to describe each encoding format from the matched communication protocol And identifying source coding format description information that matches the coding format description information carried in the source information; and identifying, by the source coding format description information, a source coding format used by the source information.
- the device further includes:
- a first control processing module configured to: when the third search module does not find the source coding format of the source information from the coding format information of the first account group, according to a preset transmission processing policy Processing the source information.
- the encoding format conversion device includes: a second storage module, a fourth search module, a fifth search module, and a conversion module;
- the second storage module is configured to store the code conversion information of the preset second account group;
- the fourth search module is configured to: find, according to the target account, the code conversion information of the second account group a target encoding format supported by the target account;
- the fifth search module is configured to: find, from the code conversion information of the second account group, a conversion processing policy capable of converting a source encoding format into a target encoding format; wherein the source encoding format is a source information format The encoding format used by the target account is used to receive the source information sent based on the source account based on the target account;
- the conversion module is configured to convert the source information into target information in the target encoding format according to the conversion processing policy.
- the code conversion information of the second account group includes: coding format description information supported by each account in the second account group, each coding format supported by the communication system to which the target account belongs, and each coding format to the target coding format.
- Each conversion processing strategy of the conversion is:
- the fourth searching module is further configured to: find, from each encoding format supported by the communication system, an encoding format that matches the source encoding format;
- the fifth searching module is further configured to: find, from the each conversion processing policy, a conversion processing policy that converts the matched encoding format to the target encoding format.
- the device further includes:
- a second control processing module configured to: when the conversion processing policy capable of converting the source encoding format into the target encoding format is not found in the encoding conversion information of the second account group by the fifth searching module, according to the preset transmission Processing the policy, processing the source information.
- the encoding format processing system includes: an encoding format identifying device and an encoding format conversion device;
- the encoding format identifying apparatus includes: a first storage module, a first searching module, a second searching module, and a third searching module; wherein
- the storage module is configured to store the encoding format information of the preset first account group;
- the first searching module is configured to: find, according to the source account, from the encoding format information of the first account group The attribution area to which the source account belongs;
- the second searching module is configured to: according to the attribution area to which the source account belongs, find a communication protocol specified by the home area to which the source account belongs from the coding format information of the first account group;
- the third search module is configured to search, according to the source account and the source information, from a coding format information of the first account group, a communication protocol specified by a home zone to which the source account belongs, a source encoding format used by the source information;
- the encoding format conversion device includes: a second storage module, a fourth search module, a fifth search module, and a conversion module;
- the second storage module is configured to store the code conversion information of the preset second account group;
- the fourth search module is configured to: find, according to the target account, the code conversion information of the second account group a target encoding format supported by the target account;
- the fifth search module is configured to: find, from the code conversion information of the second account group, a conversion processing policy capable of converting a source encoding format into a target encoding format, where the source encoding format is a source The encoding format used by the information; the target account number is used based on the target The target account receives the source information sent based on the source account;
- the conversion module is configured to convert the source information into target information in the target encoding format according to the conversion processing policy.
- the invention is based on the preset encoding format information of the first account group and the encoding conversion information of the second account group, and finds the source encoding format used by the source account to be used in the communication protocol specified by the home zone, and the target account. Accept the target encoding format, so as to accurately determine the encoding format used by the sent information, and the encoding format expected by the target account, to avoid coding conversion errors.
- FIG. 1 is a flowchart of a method for identifying an encoding format according to an embodiment of the present invention
- FIG. 2 is a flowchart of a method for converting an encoding format according to an embodiment of the present invention
- FIG. 3 is a schematic structural diagram of an encoding format processing system according to an embodiment of the present invention.
- FIG. 4 is a schematic structural diagram of an encoding format identifying apparatus 301 according to an embodiment of the present invention
- FIG. 5 is another schematic structural diagram of an encoding format identifying apparatus 301 according to an embodiment of the present invention
- FIG. 6 is a schematic diagram of an encoding format converting apparatus 302 according to an embodiment of the present invention
- FIG. 7 is a schematic diagram of another structure of an encoding format conversion apparatus 302 according to an embodiment of the present invention
- FIG. 8 is a schematic diagram of a mapping table used in an embodiment of the present invention
- FIG. 10 is another flowchart of an encoding format conversion failure process according to an embodiment of the present invention
- FIG. 11 is a flowchart of a process for failing to identify an encoding format of source information according to an embodiment of the present invention.
- the prior art is difficult to avoid the conversion error in the transcoding process, mainly because it determines the encoding format based only on the encoding format identification value in the source message, which results in the determination result not necessarily accurate, which may easily lead to conversion error.
- the invention is based on accurately determining the coding format used by the information sent by the source account and the coding format expected by the target account, thereby effectively avoiding conversion errors.
- FIG. 1 is a flowchart of a method for identifying an encoding format according to an embodiment of the present invention, where the process may include the following steps:
- Step 101 Predetermine coding format information of the first account group.
- the coding format information of each account may be pre-configured according to the maximum number of accounts that the system can support.
- the encoding format information of the source account may be searched from the encoding format information of the first account group.
- the coding format information of the first account group may include: a home zone to which each account in the first account group belongs, a communication protocol in each home zone, and each coding format description information specified by each communication protocol.
- Step 102 Receive source information sent by the source account.
- Step 103 Find, according to the source account, the attribution area to which the source account belongs from the coding format information of the first account group.
- Step 104 According to the home area to which the source account belongs, find the communication protocol specified in the home zone to which the source account belongs from the coding format information of the first account group.
- Step 105 According to the source account and the source information, check the source code format of the source information in the communication protocol specified by the home zone to which the source account belongs according to the code format information of the first account group.
- the coding format description information about the source account may be searched from the coding format information of the first account group, and the communication protocol used by the source account may be determined based on the source account, and the attribution zone to which the source account belongs is found. ; description of each encoding format specified by the communication protocol In the information, the source coding format description information matching the coding format description information carried in the source information is found; if found, the source coding format description information may be used to identify the source coding format used by the source information; If it is not found, it means that the encoding format used by the source information cannot be identified.
- the source information can be processed based on the preset transmission processing strategy.
- the transmission processing policy such as the transparent transmission policy, does not process the source information, and directly sends the source information to the target account.
- the foregoing encoding format description information may include an encoding format identifier value and an encoding format represented by the identifier value.
- the encoding format description information carried in the source information is usually an encoding format identifier value, and may be from the first account group.
- An identifier value that is the same as the identifier of the encoding format in the source information is found in the encoding format information, and the corresponding encoding format is determined to be the source encoding format based on the identifier value.
- the coding format information of the first account group can be preset for subsequent search processing, the coding format information of the account can be configured at any time when the specific account is accessed, which is convenient and flexible, and is flexible in configuration. Very easy to extend the system.
- FIG. 2 is a flowchart of a method for converting an encoding format according to an embodiment of the present invention, where the process may include:
- Step 201 Predetermine code conversion information of the second account group.
- the code conversion information of the second account group may include: encoding format description information supported by each account in the second account group, each encoding format supported by the communication system to which the target account belongs, and each conversion process of converting each encoding format to the target encoding format. Strategy.
- Step 202 Find, according to the target account, the target encoding format supported by the target account from the code conversion information of the second account group.
- Step 203 Identify, from the code conversion information of the second account group, the source coding format The conversion processing strategy for the target encoding format conversion; wherein, the source encoding format is an encoding format used by the source account source information; the target account is used to receive the source information.
- an encoding format matching the source encoding format may be found from each encoding format supported by the communication system. From each conversion processing strategy, a conversion processing strategy for converting the encoding format to the target encoding format is found.
- Step 204 Convert the source information into the target information in the target encoding format according to the conversion processing policy.
- the source information is processed according to the preset transmission policy, such as rejecting the source. information.
- the target encoding format may be found based on the encoding format supported by the pre-configured target account. Finding the conversion processing strategy of the source encoding format to the target encoding format, accurately confirming the encoding format and conversion processing strategy of the target account, thereby ensuring the correctness of the conversion processing.
- the present invention also provides an encoding format processing method, in which the above-described encoding format recognition method provided by the present invention identifies a source encoding format of source information; and based on the above encoding format conversion method provided by the present invention, the source information is The format conversion process is to convert the target information into the target encoding format.
- the conversion processing strategy based on the source encoding format for accurately identifying the source information, the target encoding format of the target account, and the appropriate source encoding format to the target encoding format is converted to ensure the correctness of the conversion processing.
- FIG. 3 is a schematic structural diagram of an encoding format processing system according to an embodiment of the present invention.
- the system may include: an encoding format identifying apparatus 301 and an encoding format converting apparatus 302.
- FIG. 4 is a schematic structural diagram of an encoding format identifying apparatus 301 according to an embodiment of the present invention.
- the encoding format identifying apparatus 301 may include: a first storage module 401, a first searching module 402, a second searching module 403, and a third lookup. Module 404;
- the first storage module 401 is configured to store the encoding format information of the preset first account group.
- the first searching module 402 is configured to: according to the source account, find the attribution of the source account from the encoding format information of the first account group. Area
- the second search module 403 is configured to: according to the attribution area of the source account, find a communication protocol specified by the home area to which the source account belongs from the code format information of the first account group;
- the third search module 404 is configured to: according to the source information of the source account and the source account, search for the source code of the source information in the communication protocol specified by the home zone to which the source account belongs from the coding format information of the first account group. format.
- the third search module 404 can include a sub-look processing module and an identification module.
- the sub-look processing module and the identification module are not shown in FIG. 4;
- a sub-find processing module configured to determine, according to the source account, a source communication protocol used by the source account in the home zone to which the source account belongs; and find a communication that matches the source communication protocol from a communication protocol specified by the home zone to which the source account belongs Agreement
- An identification module configured to: find, according to each coding format description information specified by the matched communication protocol, source coding format description information that matches the coding format description information carried in the source information; and the source coding format description information , identify the source encoding format used by the source information.
- FIG. 5 is another schematic structural diagram of an encoding format identifying apparatus 301 according to an embodiment of the present invention.
- the encoding format identifying apparatus 301 may further include: a first control processing module 501.
- the third search module processes the source information according to the preset transmission processing policy, such as transparently transmitting the source information to the target account.
- FIG. 6 is a schematic structural diagram of an encoding format conversion apparatus 302 according to an embodiment of the present invention.
- the encoding format conversion device 302 may include: a second storage module 601, a fourth search module 602, a fifth search module 603, and a conversion module 604;
- the second storage module 601 is configured to store the code conversion information of the preset second account group.
- the fourth search module 602 is configured to: find, according to the target account, the target account from the code conversion information of the second account group.
- the target encoding format is specifically configured to: find, from each encoding format supported by the communication system, an encoding format that matches the source encoding format.
- the fifth searching module 603 is configured to: find, from the code conversion information of the second account group, a conversion processing policy that can convert the source encoding format into the target encoding format conversion; the fifth searching module is specifically configured to: The conversion processing strategy for converting the encoding format to the target encoding format is found.
- the conversion module 604 is configured to convert the source information into the target information in the target encoding format according to the conversion processing policy.
- FIG. 7 is another schematic structural diagram of an encoding format conversion apparatus 302 according to an embodiment of the present invention. Compared with the apparatus shown in FIG. 6, the apparatus shown in FIG. 7 further includes:
- the second control processing module 701 is configured to: when the fifth search module 603 does not find a conversion processing policy capable of converting the source encoding format into the target encoding format conversion from the encoding conversion information of the second account group, according to the preset transmission strategy , processing source information, such as rejecting source information.
- the above-described encoding format identifying means 301 and encoding format converting means 302 can be used together in one system, or can be selected as needed in practical applications.
- the code conversion information may be configured in the form of an index table, and the search function is implemented based on the index table.
- the encoding format information of the first account group may be embodied by a three-level mapping table:
- the first level table is called the account attribution mapping table of the first account group:
- the table can be set up only in the whole system.
- the content of the table mainly includes two parts, and some of them are individual account IDs, and the maximum number of accounts that the system can support. Is N1; the other part is the home zone of the account corresponding to the account ID.
- the attribution zone can be a region of a country, or a country.
- a system assigns a unique ID to an account for indexing.
- the attribution area of the account ID can be indexed to the corresponding entry in the second level table. As shown in Table 1 below:
- N is not greater than Nl.
- the second level table is called the country/region attribution mapping table: This table has N2 tables in the whole system, and N2 is the number of countries supported by the system.
- the second level table mainly contains two parts: the communication protocol ID, and the specific communication protocol corresponding to the communication protocol ID.
- Each secondary table has a record value of up to M2, and M2 is the maximum protocol type supported by the system in a country.
- the second level table has three sheets, one table corresponding to the type of communication protocol supported by one region. As shown in Table 2 to Table 4 below:
- Table 2 above shows the four communication protocols used by the system in China with the account ID 1 being: SMPP, CMPP, SGIP, SMGP.
- Table 3 shows the two communication protocols used by the United States with an account ID of 2, namely: SMPP, SP1.
- Table 4 shows the three communication protocols used in Europe with the system support account ID of 3, namely: SMPP, SP1, SP2.
- the value of each record is specific protocol type information, which points to a specific third level table.
- the third-level table is called the protocol attribution mapping table: The table has a maximum of N3 tables in the whole system, N3 is the number of protocols supported by the system * the number of second-level tables, that is, different countries/regions have such a different protocol specification A separate three-level mapping table.
- the table mainly includes two types of content: an encoding format ID and an encoding format corresponding to the encoding format ID; wherein, the encoding format ID may also be referred to as an encoding format field value, or an encoding format identification value, and the table is indexed by each protocol.
- the record value of each three-level table is up to M3, and M3 is the maximum value of the code format field of the protocol supported by the system.
- the value of each record is specific protocol encoding format information, which stores the specific encoding format. As shown in Table 5 to Table 8 below:
- the coding formats involved in Tables 5 to 8 above include: ASCII, UNICODE, GBK, 7BIT, 8BIT. It should be noted that, in the examples enumerated in the present invention, in Tables 5 and 6, the encoding format ID is 15 to identify the GBK encoding format, and in Table 7, the encoding format ID is 15 to identify the 7BIT encoding format. If it is based on the prior art, it will be difficult to identify, and based on the technical solution of the present invention, on the basis of the first level and the second level table, the encoding format with the same encoding format ID but different actual can be accurately identified.
- a corresponding three-level mapping table is created according to the maximum value supported by the system.
- the system automatically fills in the corresponding entry in the protocol type to the home level mapping table according to the account type.
- each item can be initialized according to the encoding format type supported by the system when the table is created or dynamically updated when the account is manually configured.
- the preferred three-level mapping table can highlight the advantages of the present invention being excellent in scalability and flexible in configuration.
- the system when the system receives the information sent by the source account, such as a message, the system obtains the mapping information of the second level mapping table according to the account ID in the first level mapping table, and then uses the second level mapping table according to the account attribution area. The corresponding third-level mapping table information is obtained, and then the corresponding encoding format type is obtained according to the data_coding field carried in the message.
- the conversion process can be reflected by the secondary mapping table:
- the first level table may be referred to as an account attribution mapping table of the second account group: the table reflects the code conversion information of the second account group, and the table may only need to set one in the whole system, and the table content mainly includes two parts, part of It is the ID of each account.
- the maximum number of accounts that the system can support is Al.
- A1 is the maximum number of accounts supported by the system.
- A1 and N1 can be the same or different.
- the second part is the encoding format that each account ID expects to use. In an account, an account can set multiple desired encoding formats according to priority.
- the second part of the information points to the specific second level table; as shown in Table 9 below:
- M is not greater than Al.
- the system defines the encoding format ID, as shown in Table 10 below: Predefined encoding format ID table in the system
- the second-level table is called the encoding format attribution mapping table: This table can reflect the conversion support licensing mechanism.
- the table has A2 sheets in the whole system, and A2 is the number of encoding formats supported by the system, that is, each convertible encoding exists.
- Such an independent secondary mapping table is indexed by the encoding format ID in Table 10. Therefore, each secondary table has a maximum of B1 records, and B1 is the number of encoding types that the system supports for encoding.
- the value of each record is the specific encoding format. See Tables 11 through 15 below:
- a corresponding two-level mapping table can be created according to the supported maximum value.
- select the encoding format that the account expects to use or support and fill in the corresponding item in the first-level account attribution mapping table of the second account group.
- the system automatically fills in the corresponding items in the second-level encoding format attribution mapping table according to the supported code conversion information.
- a plurality of encoding formats may be sequentially selected according to the priority.
- the target encoding format is obtained according to the target account ID in the automatically converted first-level account mapping table, and then the source encoding format that has been obtained by the automatic identification is indexed, and the second-level encoding is performed.
- the format attribution mapping table obtains the corresponding encoding conversion function for conversion. If multiple target conversion encoding formats are configured, the encoding conversion processing is performed in order of priority high to low.
- FIG. 8 is a schematic diagram of using a mapping table according to an embodiment of the present invention.
- the implementation you can easily achieve the extension of the encoding conversion, you only need to expand the size of each mapping table. For high configurability flexibility, you only need to dynamically modify the specific values in each table. Due to the added country map, it is also possible to resolve inconsistencies in different country codes.
- FIG. 9 is a flowchart of encoding format conversion in an embodiment of the present invention, and the process may include the following steps:
- Step 901 The account A sends a message to the account B, and the message carries the code format ID of 15.
- Step 903 The gateway finds that the communication protocol type of the account A in the second-level country/region attribution mapping table is SMPP.
- Step 904 The gateway finds that the encoding format of the message is 7 BIT in the protocol mapping table of the SMPP in the third-level European region according to the encoding format ID in the message is 15.
- Step 905 The gateway finds that the encoding format supported by the target account B is UNICODE in the account attribution mapping table of the second account group according to the target account B.
- Step 906 The gateway searches for the conversion function 7BIT_TO_UNICODE for performing conversion processing in the UNICODE encoding format attribution mapping table by using 7BIT as an index.
- Step 907 The gateway calls the conversion function 7BIT_TO_UNICODE to convert the message sent by the account A into the target message in the UNICODE encoding format.
- Step 908 The gateway sends the target message to the target account.
- the accurate identification of the encoding format of the source message and the preparation identifier of the target encoding format are implemented based on the mapping tables of the above-mentioned levels, thereby realizing the correct processing of the encoding format conversion, realizing communication between users, and improving user experience.
- FIG. 10 is another flowchart of an encoding format conversion failure processing according to an embodiment of the present invention, where the process may include: Step 1001: The account C sends a message to the account A, and the code format ID carried in the message is
- Step 1002 According to the account ID of the account C, the gateway searches for the home area of the account C in the first-level account attribution mapping table of the first account group.
- Step 1003 The gateway finds that the communication protocol type of the account C in the second-level country/region attribution mapping table is CMPP.
- Step 1004 The gateway finds a matching encoding format ID from the third-level protocol attribution mapping table of the CMPP according to the encoding format ID of 15, and the corresponding encoding format is GBK.
- Step 1005 The gateway finds the target account A in the account mapping mapping table of the second account group according to the target account A.
- the supported encoding format is 7BIT.
- Step 1006 The gateway uses the GBK as an index to search for the processing mode in the 7BIT encoding format attribution mapping table, and the search result does not support the conversion from GBK to 7BIT.
- Step 1007 The gateway refuses to send the source message according to the preset transmission processing policy.
- Fig. 10 The flow shown in Fig. 10 is an embodiment of the treatment of a special case of the present invention.
- FIG. 11 is a flowchart of processing failure of identifying an encoding format of source information according to an embodiment of the present invention, where the process may include:
- Step 1101 Account A sends a message to account B, and the message carries an encoding format ID of 200.
- Step 1103 The gateway finds that the communication protocol type of the account A in the second-level country/region attribution mapping table is SMPP.
- Step 1104 The gateway according to the encoding format ID in the message is 200, and the encoding format ID matching the 200 is not found in the protocol mapping table of the SMPP in the third-level European region.
- Step 1105 The gateway does not identify the source message, and the source message is transparently transmitted to the account B according to the preset transmission processing policy.
- the implementation of the present invention not only correctly handles code conversion, facilitates system configuration and expansion, but also correctly handles various situations encountered in actual communication.
- the spirit and scope of the invention Thus, it is intended that the present invention cover the modifications and the modifications of the invention.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Communication Control (AREA)
- Computer And Data Communications (AREA)
- Storage Device Security (AREA)
- Compression, Expansion, Code Conversion, And Decoders (AREA)
Description
编码格式识别、 转换方法及装置、 处理方法及系统 技术领域
本发明涉及通信技术领域, 尤其涉及一种编码格式识别方法及装置、 转换方法及装置、 处理方法及系统。 背景技术
编码是通信中常需釆用的技术。通信数据的编码格式( data_coding )通 常存在多种, 如 ASCII、 UNICODE, 7BIT等等。 用户通常基于与通信运营 商之间的通信协议进行与其他用户之间的通信。 一个通信协议可能涉及通 信数据的多种编码格式, 不同通信协议釆用的编码格式可能相同或不同, 不同区域内釆用的编码方式也可能相同或不同。
现有技术中, 为实现通信, 常需要对不同编码格式做转换处理。 现有 技术常釆用的编码格式转换处理方式主要包括: 针对两个具体帐号, 釆用 单对单的固定转换, 举例如: 帐号 1发送消息给帐号 2, 现有技术主要是: 查出帐号 1所在地为地区 A, 帐号 1使用的编码格式 UNICODE在地 区 A规范的通信协议内的值为 10;
查出帐号 2所在国家为 B,帐号 2使用的编码格式 7BIT在国家 B规范 的通信协议内的值为 8;
将编码格式为 UNICODE的消息转换为编码格式为 7BIT的消息。
发明人在实现本发明的过程中发现现有技术至少存在以下技术问题: 现有技术虽然能够实现编码格式之间的转换, 但是由于其仅根据消息 中携带的编码格式标识值来确定编码格式, 易出现转换错误, 导致用户不 能正常使用相关业务的问题。 如不同地区和国家所规范的通信协议定义不 同, 如自行扩展的协议, 地区 A定义 UNICODE的标识值为 10, 而地区 C
定义 7BIT的标识值为 10, 则现有技术根据两种不同编码格式的相同标识 值, 误认为两种编码格式相同, 并不对本次消息作转换处理, 导致错误发 生; 并且由于釆用单对单转换处理, 导致扩展性、 配置灵活性不高, 难以 适应通信技术、 编码技术的不断发展。 发明内容
本发明提供一种编码格式识别、 转换方法及装置、 处理方法及系统, 用以解决现有技术中存在编码格式识别不准确, 转换易错、 系统扩展及配 置不灵活的技术问题。
本发明中, 编码格式识别方法, 该方法包括:
预设第一帐号组的编码格式信息;
接收基于源帐号发送的源信息;
根据所述源帐号, 从所述第一帐号组的编码格式信息中, 查找出所述 源帐号所属的归属区域;
根据所述源帐号所属的归属区域, 从所述第一帐号组的编码格式信息 中, 查找出在所述源帐号所属归属区域所规范的通信协议;
根据所述源帐号和所述源信息, 从所述第一帐号组的编码格式信息中, 查找出所述源帐号所属的归属区域所规范的通信协议内, 所述源信息釆用 的源编码格式。
优选地, 所述第一帐号组的编码格式信息包括: 第一帐号组内各帐号 各自所属的归属区域、 各归属区域所规范的通信协议、 各通信协议所规范 的各编码格式描述信息;
根据所述源帐号和所述源信息查找出所述源信息釆用的源编码格式包 括:
根据所述源帐号, 确定所述源帐号在所述源帐号所属的归属区域内釆 用的源通信协议;
从所述源帐号所属的归属区域所规范的通信协议内, 找出与所述源通 信协议相匹配的通信协议;
从所述相匹配的通信协议所规范的各编码格式描述信息中, 找出与所 述源信息内携带的编码格式描述信息相匹配的源编码格式描述信息;
由所述源编码格式描述信息, 识别出所述源信息所釆用的源编码格式。 优选地, 所述各通信协议所规范的各编码格式描述信息包括: 各编码 格式标识值和各编码格式标识值对应的编码格式;
所述源信息内携带的编码格式描述信息为源编码格式标识值; 所述从 相匹配的通信协议所规范的各编码格式描述信息中, 找出与源信息内携带 的编码格式描述信息相匹配的源编码格式描述信息包括: 从相匹配的通信 协议所规范的各编码格式标识值中, 找出与所述源信息内携带的编码格式 标识值相同的标识值;
所述由源编码格式描述信息, 识别出源信息所釆用的源编码格式包括: 根据找出的所述标识值对应的编码格式, 确定所述源信息釆用的源编码格 式。
优选地, 该方法还包括:
从所述第一帐号组的编码格式信息中, 未查找到出所述源信息釆用的 源编码格式时, 按照预设传输处理策略, 处理所述源信息。
本发明中, 编码格式转换方法, 该方法包括:
预设第二帐号组的编码转换信息;
根据目标帐号, 从所述第二帐号组的编码转换信息中, 找出所述目标 帐号所支持的目标编码格式;
从所述第二帐号组的编码转换信息中, 找出能够将源编码格式转换为 目标编码格式的转换处理策略; 其中, 所述源编码格式为源信息所釆用的 编码格式; 基于所述目标帐号接收基于源帐号发送的所述源信息;
根据所述转换处理策略, 将所述源信息转换为釆用所述目标编码格式 的目标信息。
优选地, 所述第二帐号组的编码转换信息包括: 第二帐号组内各帐号 所支持的编码格式描述信息、 目标帐号所属通信系统所支持的各编码格式、 和各编码格式向所述目标编码格式转换的各转换处理策略;
所述从所述第二帐号组的编码转换信息中, 找出能够将源编码格式转 换为目标编码格式的转换处理策略包括:
从所述通信系统所支持的各编码格式中, 找出与所述源编码格式相匹 配的编码格式; 从所述各转换处理策略中, 找出所述相匹配的编码格式向 所述目标编码格式转换的转换处理策略。
优选地, 该方法还包括:
从所述第二帐号组的编码转换信息中, 未找到能够将源编码格式转换 为目标编码格式的转换处理策略时, 按照预设传输处理策略, 处理所述源 信息。
本发明中, 编码格式处理方法, 该方法包括: 预设第一帐号组的编码 格式信息; 预设第二帐号组的编码转换信息; 该方法还包括:
基于目标帐号接收基于源帐号发送的源信息;
根据所述源帐号, 从所述第一帐号组的编码格式信息中, 查找出所述 源帐号所属的归属区域;
根据所述源帐号所属的归属区域, 从所述第一帐号组的编码格式信息 中, 查找出在所述源帐号所属的归属区域所规范的通信协议;
根据所述源帐号和所述源信息, 从所述第一帐号组的编码格式信息中, 查找出所述源帐号所属的归属区域所规范的通信协议内, 所述源信息釆用 的源编码格式;
根据目标帐号, 从所述第二帐号组的编码转换信息中, 找出所述目标
帐号所支持的目标编码格式;
从所述第二帐号组的编码转换信息中, 找出能够将所述源编码格式转 换为目标编码格式的转换处理策略; 其中, 所述源编码格式为源信息所釆 用的编码格式; 基于所述目标帐号接收基于源帐号发送的所述源信息; 根据所述转换处理策略, 将所述源信息转换为釆用所述目标编码格式 的目标信息。
本发明中, 编码格式识别装置, 该装置包括: 第一存储模块、 第一查 找模块、 第二查找模块和第三查找模块; 其中,
所述第一存储模块, 用于存储预设的第一帐号组的编码格式信息; 所述第一查找模块, 用于根据源帐号, 从所述第一帐号组的编码格式 信息中, 查找出所述源帐号所属的归属区域;
所述第二查找模块, 用于根据所述源帐号所属的归属区域, 从所述第 一帐号组的编码格式信息中, 查找出在所述源帐号所属的归属区域所规范 的通信协议;
所述第三查找模块, 用于根据所述源帐号和所述源信息, 从所述第一 帐号组的编码格式信息中, 查找出所述源帐号所属的归属区域所规范的通 信协议内, 所述源信息釆用的源编码格式。
优选地, 所述第一帐号组的编码格式信息包括: 第一帐号组内各帐号 各自所属的归属区域、 各归属区域内的通信协议、 和各通信协议所规范的 各编码格式描述信息;
所述第三查找模块进一步包括: 子查找处理模块和识别模块; 其中, 所述子查找处理模块, 用于根据所述源帐号, 确定所述源帐号在所述 源帐号所属的归属区域内釆用的源通信协议; 从所述源帐号所属的归属区 域所规范的通信协议内, 找出与所述源通信协议相匹配的通信协议;
识别模块, 用于从所述相匹配的通信协议所规范的各编码格式描述信
息中, 找出与所述源信息内携带的编码格式描述信息相匹配的源编码格式 描述信息; 由所述源编码格式描述信息, 识别出所述源信息所釆用的源编 码格式。
优选地, 所述装置还包括:
第一控制处理模块, 用于在所述第三查找模块从所述第一帐号组的编 码格式信息中, 未查找到出所述源信息釆用的源编码格式时, 按照预设传 输处理策略, 处理所述源信息。
本发明中, 编码格式转换装置, 该装置包括: 第二存储模块、 第四查 找模块、 第五查找模块和转换模块; 其中,
所述第二存储模块, 用于存储预设的第二帐号组的编码转换信息; 所述第四查找模块, 用于根据目标帐号, 从所述第二帐号组的编码转 换信息中, 找出所述目标帐号所支持的目标编码格式;
所述第五查找模块, 用于从所述第二帐号组的编码转换信息中, 找出 能够将源编码格式转换为目标编码格式的转换处理策略; 其中, 所述源编 码格式为源信息所釆用的编码格式; 所述目标帐号用于基于所述目标帐号 接收基于源帐号发送的所述源信息;
所述转换模块, 用于根据所述转换处理策略, 将所述源信息转换为釆 用所述目标编码格式的目标信息。
优选地, 所述第二帐号组的编码转换信息包括: 第二帐号组内各帐号 所支持的编码格式描述信息、 目标帐号所属通信系统所支持的各编码格式、 和各编码格式向目标编码格式转换的各转换处理策略;
所述第四查找模块, 进一步用于从所述通信系统所支持的各编码格式 中, 找出与所述源编码格式相匹配的编码格式;
所述第五查找模块, 进一步用于从所述各转换处理策略中, 找出所述 相匹配的编码格式向所述目标编码格式转换的转换处理策略。
优选地, 所述装置还包括:
第二控制处理模块, 用于在所述第五查找模块从所述第二帐号组的编 码转换信息中, 未找到能够将源编码格式转换为目标编码格式的转换处理 策略时, 按照预设传输处理策略, 处理所述源信息。
本发明中, 编码格式处理系统包括: 编码格式识别装置和编码格式转 换装置; 其中,
所述编码格式识别装置, 包括: 第一存储模块、 第一查找模块、 第二 查找模块和第三查找模块; 其中,
所述存储模块, 用于存储预设的第一帐号组的编码格式信息; 所述第一查找模块, 用于根据源帐号, 从所述第一帐号组的编码格式 信息中, 查找出所述源帐号所属的归属区域;
所述第二查找模块, 用于根据所述源帐号所属的归属区域, 从所述第 一帐号组的编码格式信息中, 查找出在所述源帐号所属的归属区域所规范 的通信协议;
所述第三查找模块, 用于根据所述源帐号和所述源信息, 从所述第一 帐号组的编码格式信息中, 查找出所述源帐号所属的归属区域所规范的通 信协议内, 所述源信息釆用的源编码格式;
所述编码格式转换装置, 包括: 第二存储模块、 第四查找模块、 第五 查找模块和转换模块; 其中,
所述第二存储模块, 用于存储预设的第二帐号组的编码转换信息; 所述第四查找模块, 用于根据目标帐号, 从所述第二帐号组的编码转 换信息中, 找出所述目标帐号所支持的目标编码格式;
所述第五查找模块, 用于从所述第二帐号组的编码转换信息中, 找出 能够将源编码格式转换为目标编码格式的转换处理策略; 其中, 其中, 所 述源编码格式为源信息所釆用的编码格式; 所述目标帐号用于基于所述目
标帐号接收基于源帐号发送的所述源信息;
所述转换模块, 用于根据所述转换处理策略, 将所述源信息转换为釆 用所述目标编码格式的目标信息。
本发明有益效果如下:
本发明基于预设的第一帐号组的编码格式信息以及第二帐号组的编码 转换信息, 查找出源帐号所发信息在归属区域所规范的通信协议内釆用的 源编码格式, 以及目标帐号接受釆用的目标编码格式, 从而可准确确定所 发信息所釆用的编码格式, 以及目标帐号期望的编码格式, 避免编码转换 的错误。
并且通过预先配置各帐号的编码转换信息, 后续基于查找机制, 查找 实际釆用的编码格式, 不仅使查找结果准确, 还可方便系统的扩展, 实现 灵活配置。 附图说明
图 1为本发明实施例中编码格式识别方法流程图;
图 2为本发明实施例中编码格式转换方法流程图;
图 3为本发明实施例中编码格式处理系统的结构示意图;
图 4为本发明实施例中编码格式识别装置 301的结构示意图; 图 5为本发明实施例中编码格式识别装置 301的另一结构示意图; 图 6为本发明实施例中编码格式转换装置 302的结构示意图; 图 7为本发明实施例中编码格式转换装置 302的另一结构示意图; 图 8为本发明实施例中映射表使用示意图;
图 9为本发明实施例中编码格式转换的流程图;
图 10为本发明实施例中编码格式转换失败处理的另一流程图; 图 11为本发明实施例中对源信息的编码格式识别失败的处理流程图。
具体实施方式
现有技术之所以难以避免编码转换处理中的转换出错, 主要因其仅基 于源消息中的编码格式标识值来确定编码格式, 导致确定结果未必准确, 从而易导致转换出错。
本发明基于准确确定源帐号所发信息釆用的编码格式以及目标帐号期 望釆用的编码格式, 有效避免转换出错。
下面结合附图对本发明的具体实现作详细说明。
参见图 1 , 图 1为本发明实施例中编码格式识别方法流程图, 该流程可 包括以下步骤:
步骤 101、 预设第一帐号组的编码格式信息。
本发明的实际应用中, 可根据系统所能够支持的最多帐号数, 预先配 置各帐号的编码格式信息。 实际应用中, 可从第一帐号组的编码格式信息 中查找源帐号的编码格式信息。 具体地, 第一帐号组的编码格式信息可包 括: 第一帐号组内各帐号各自所属归属区域、 各归属区域内的通信协议、 各通信协议所规范的各编码格式描述信息。
步骤 102、 接收源帐号发送的源信息。
步骤 103、 根据源帐号, 从第一帐号组的编码格式信息中, 查找出源帐 号所属归属区域。
步骤 104、根据源帐号所属归属区域,从第一帐号组的编码格式信息中, 查找出在源帐号所属归属区域所规范的通信协议。
步骤 105、 根据源帐号与源信息, 从第一帐号组的编码格式信息中, 查 找出源帐号所属归属区域所规范的通信协议内, 源信息釆用的源编码格式。
上述图 1 所示流程中, 可从第一帐号组的编码格式信息中查找关于源 帐号的编码格式描述信息, 具体可基于源帐号, 确定源帐号所用通信协议, 并查找出源帐号所属归属区域; 从该通信协议所规范的各编码格式描述信
息中, 找出与源信息内携带的编码格式描述信息相匹配的的源编码格式描 述信息; 若查找到, 则可基于源编码格式描述信息, 识别出源信息釆用的 源编码格式; 若未能查找到, 则表示不能识别源信息所釆用的编码格式, 实际应用中, 可基于预设传输处理策略, 处理源信息。 传输处理策略如透 传策略, 即不对源信息做处理, 直接将源信息发送给目标帐号。
实际应用中, 上述编码格式描述信息可包括编码格式标识值以及该标 识值所表示的的编码格式; 源信息中携带的编码格式描述信息通常是编码 格式标识值, 则可从第一帐号组的编码格式信息中找到与源信息中编码格 式标识值相同的标识值, 基于该标识值确定对应的编码格式为源编码格式。
图 1 所示流程中, 在识别源信息釆用的编码格式时, 不仅参考源信息 中的编码格式描述信息如编码格式标识值, 还结合该源帐号所属归属区域, 以及源帐号在该归属区域内使用的通信协议, 从而准备确定该通信协议下 编码格式标识值所指的源编码格式具体为哪种编码格式。
另外, 由于上述第一帐号组的编码格式信息可预设, 以用于后续的查 找处理, 因此可在具体帐号接入时, 随时配置该帐号的各编码格式信息, 方便易行, 配置灵活, 非常易于系统的扩展。
参见图 2, 图 2为本发明实施例中编码格式转换方法流程图, 该流程可 包括:
步骤 201、 预设第二帐号组的编码转换信息。
第二帐号组的编码转换信息可包括: 第二帐号组内各帐号所支持的编 码格式描述信息、 目标帐号所属通信系统所支持的各编码格式、 各编码格 式向目标编码格式转换的各转换处理策略。
步骤 202、 根据目标帐号, 从第二帐号组的编码转换信息中, 找出目标 帐号所支持的目标编码格式。
步骤 203、从第二帐号组的编码转换信息中, 找出能够将源编码格式转
换为目标编码格式转换的转换处理策略; 其中, 源编码格式为源帐号所发 源信息所釆用的编码格式; 目标帐号用于接收所述源信息。
具体地, 可从通信系统所支持的各编码格式中, 找出与源编码格式相 匹配的编码格式; 从各转换处理策略中, 找出该编码格式向目标编码格式 转换的转换处理策略。
步骤 204、根据转换处理策略, 将源信息转换为釆用目标编码格式的目 标信息。
实际应用中, 若从第二帐号组的编码转换信息中, 未找到能够将源编 码格式转换为目标编码格式转换的转换处理策略, 则按照预设传输策略, 处理源信息, 如拒绝接受该源信息。
上述图 2所示流程中, 为使目标帐号能够准确解读源信息中的内容, 在收到发送给目标帐号的信息后, 可基于预先配置的目标帐号所支持的编 码格式, 查找到目标编码格式, 查找源编码格式向目标编码格式的转换处 理策略, 准确确认目标帐号的编码格式及转换处理策略, 从而保证转换处 理的正确性。
本发明还提供一种编码格式处理方法, 该方法中, 基于本发明提供的 上述编码格式识别方法识别出源信息的源编码格式; 并基于本发明提供的 上述编码格式转换方法, 对源信息做格式转换处理, 以转换为目标编码格 式的目标信息。
该编码格式处理方法中, 基于准确识别源信息的源编码格式、 目标帐 号的目标编码格式, 以及合适的源编码格式向目标编码格式转换的转换处 理策略, 确保转换处理的正确性。
相应地, 本发明提供编码格式处理系统。 参见图 3 , 图 3为本发明实施 例中编码格式处理系统的结构示意图, 该系统可包括: 编码格式识别装置 301、 编码格式转换装置 302。
参见图 4,图 4为本发明实施例中编码格式识别装置 301的结构示意图, 编码格式识别装置 301可包括: 第一存储模块 401、 第一查找模块 402、 第 二查找模块 403和第三查找模块 404;
第一存储模块 401 , 用于存储预设的第一帐号组的编码格式信息; 第一查找模块 402,用于根据源帐号,从第一帐号组的编码格式信息中, 查找出源帐号所属归属区域;
第二查找模块 403 , 用于根据源帐号所属归属区域,从第一帐号组的编 码格式信息中, 查找出在源帐号所属归属区域所规范的通信协议;
第三查找模块 404, 用于根据源帐号与源帐号所发源信息,从第一帐号 组的编码格式信息中, 查找出源帐号所属归属区域所规范的通信协议内, 源信息釆用的源编码格式。
其中, 第三查找模块 404可包括子查找处理模块和识别模块, 图 4中 未示出子查找处理模块和识别模块;
子查找处理模块, 用于根据源帐号, 确定源帐号在源帐号所属归属区 域内釆用的源通信协议; 从源帐号所属归属区域所规范的通信协议, 找出 与源通信协议相匹配的通信协议;
识别模块, 用于从该相匹配的通信协议所规范的各编码格式描述信息 中, 找出与源信息内携带的编码格式描述信息相匹配的的源编码格式描述 信息; 由源编码格式描述信息, 识别出源信息所釆用的源编码格式。
参见图 5 ,图 5为本发明实施例中编码格式识别装置 301的另一结构示 意图, 相比较图 4所示装置, 图 5中, 编码格式识别装置 301还可包括: 第一控制处理模块 501 ,用于在第三查找模块从第一帐号组的编码格式 信息中, 未查找到出所述源编码格式时, 按照预设传输处理策略, 处理源 信息, 如透传源信息给目标帐号。
参见图 6,图 6为本发明实施例中编码格式转换装置 302的结构示意图,
编码格式转换装置 302可包括: 第二存储模块 601、 第四查找模块 602、 第 五查找模块 603和转换模块 604;
第二存储模块 601 , 用于存储预设的第二帐号组的编码转换信息; 第四查找模块 602, 用于根据目标帐号, 从第二帐号组的编码转换信息 中, 找出目标帐号所支持的目标编码格式; 该第四查找模块具体用于, 从 通信系统所支持的各编码格式中, 找出与源编码格式相匹配的编码格式。
第五查找模块 603 , 用于从第二帐号组的编码转换信息中, 找出能够将 源编码格式转换为目标编码格式转换的转换处理策略; 第五查找模块具体 用于, 从各转换处理策略中, 找出该编码格式向目标编码格式转换的转换 处理策略。
转换模块 604, 用于根据转换处理策略, 将源信息转换为釆用目标编码 格式的目标信息。
参见图 7,图 7为本发明实施例中编码格式转换装置 302的另一结构示 意图, 相比较图 6所示装置, 图 7所示装置还包括:
第二控制处理模块 701 ,用于在第五查找模块 603从第二帐号组的编码 转换信息中, 未找到能够将源编码格式转换为目标编码格式转换的转换处 理策略时, 按照预设传输策略, 处理源信息, 如拒绝源信息。
上述编码格式识别装置 301与编码格式转换装置 302可一起用于一个 系统, 或可在实际应用中, 根据需要进行选用。
本发明的具体实现中, 可釆用索引表的形式配置编码转换信息, 基于 索引表实现查找功能。
详细地, 第一帐号组的编码格式信息可由三级映射表体现:
第一级表称为第一帐号组的帐号归属映射表: 该表整个系统内可只需 设置一张, 该表内容主要包含两部分, 一部分是各个帐号 ID, 设系统能够 支持的最大帐号数为 N1 ; 另一部分为与帐号 ID对应的该帐号所属归属区
域, 根据系统的部署, 归属区域可以是一个国家的各个地区, 或各个国家。 一个系统为一个帐号分配唯一的 ID, 以用于索引。 由帐号 ID的归属区域可 索引到第二级表中相应表项。 如下表 1所示:
表 1
表 1中, N不大于 Nl。
第二级表称为国家 /地区归属映射表: 该表在整个系统有 N2张表, N2 为系统支持的国家 /地区数量。第二级表主要包含两部分内容:通信协议 ID, 以及与通信协议 ID对应的具体通信协议。每张二级表的记录值最多 M2项, M2为系统支持某个国家 /地区的最大协议类型。
表 2
表 4
上述表 2体现系统支持帐号 ID为 1的中国所使用的 4个通信协议, 分 别是: SMPP、 CMPP, SGIP, SMGP。 表 3体现系统支持帐号 ID为 2的美 国所使用的 2个通信协议, 分别是: SMPP、 SP1。 表 4体现系统支持帐号 ID为 3的欧洲所使用的 3个通信协议, 分别是: SMPP, SP1、 SP2。
每项记录的值为具体的协议类型信息, 该信息指向具体某个第三级表。 第三级表称为协议归属映射表: 该表在整个系统最多有 N3 张表, N3 为系统支持的协议数量 *第二级表数,即不同国家 /地区如果协议规范不同都 存在这样一张独立的三级映射表。 该表主要包含两种内容: 编码格式 ID和 编码格式 ID对应的编码格式; 其中, 编码格式 ID也可以称为编码格式字 段值、 或编码格式标识值, 该表以每种协议的为索引。 每张三级表的记录 值最多 M3项, M3为系统支持的协议的编码格式字段的最大值。 每项记录 的值为具体的协议编码格式信息, 该信息存放具体编码格式。 如下表 5 至 表 8所示:
表 6
表 8
上述表 5至表 8所涉及编码格式包括: ASCII, UNICODE, GBK、 7BIT、 8BIT。 值得注意的是, 本发明列举的实例中, 表 5、 6中, 编码格式 ID为 15标识 GBK编码格式,而表 7中,编码格式 ID为 15标识 7BIT编码格式。
若基于现有技术, 则将难以识别, 而基于本发明的技术方案, 可在上述第 一级与第二级表的基础上, 准确识别编码格式 ID相同而实际不同的编码格 式。
具体应用中, 可系统启动初始化时, 根据系统支持的最大值, 创建相 应的三级映射表。 当添加帐号时, 只需要选择该帐号的归属地区, 填入第 一级映射表中对应项中。 系统根据帐号类型自动填入协议类型到归属地二 级映射表中对应的项。 对于第三级映射表的值, 可在创建该表时根据系统 支持的编码格式类型进行每项的初始化或者手动配置帐号时动态更新。 优 选使用的三级映射表, 可突出体现本发明扩展性好、 配置灵活的优点。
具体应用中, 当系统收到源帐号发来的信息如消息时, 根据该帐号 ID 在第一级映射表获取对应第二级映射表信息, 再根据帐号归属区域在指定 的第二级映射表中获取对应的第三级映射表信息, 之后根据消息中携带的 data_coding字段获取对应的编码格式类型。
转换处理可由二级映射表体现:
第一级表可称为第二帐号组的帐号归属映射表: 该表体现第二帐号组 的编码转换信息, 该表整个系统内可只需设置一张, 该表内容主要包含两 部分, 一部分是各个帐号 ID, 设系统能够支持的最大帐号数为 Al , A1为 系统支持的最大帐号数, A1与上述 N1可相同或不同; 第二部分为各帐号 ID期望釆用的编码格式, 实际应用中, 一个帐号可以根据优先级设置多个 期望编码格式。 第二部分的信息指向具体第二级表; 如下表 9所示:
表 9
表 9中, M不大于 Al。
系统定义编码格式 ID, 如下表 10所示:
系统中预定义的编码格式 ID表
编码格式 1 2 3 4 5
ID
值 ASCII UNICODE GBK 7BIT 8BIT
表 10
第二级表称为编码格式归属映射表: 该表可体现转换支持许可机制, 该表在整个系统有 A2张表, A2为系统支持的编码格式的数量, 即每种可 以转换的编码都存在这样一张独立的二级映射表。 该表以表 10中编码格式 ID为索引。 因此每张二级表的记录值最多 B1项, B1为系统支持可以编码 转换的编码类型数量。 每项记录的值为具体编码格式。 如下表 11 至表 15 所示:
实际应用中, 在系统启动初始化时, 可根据支持的最大值, 创建相应 的两级映射表。 当添加帐号时, 选择该帐号期望釆用或支持的编码格式, 填入第二帐号组的第一级帐号归属映射表中对应项中。 系统根据支持的编 码转换信息自动填入第二级编码格式归属映射表中对应的项。 其中, 所述 选择该帐号期望釆用或支持的编码格式时, 可以根据优先级依次选择多个 编码格式。
当系统准备将源消息转发给目标帐号时, 根据目标帐号 ID在自动转换 的第一级帐号映射表中获取目标编码格式, 再根据自动识别已经获取的源 编码格式为索引, 在第二级编码格式归属映射表中获取相应的编码转换函 数进行转换。 如果配置了多个目标转换编码格式, 则按优先级高到低进行 编码转换处理。 在自动识别编码格式失败时, 根据帐号配置是否允许透传 选项, 进行相应的透传处理。
参见图 8, 图 8为本发明实施例中映射表使用示意图。通过上述本发明
的实现, 可以很容易就实现编码转换的扩展, 只需要扩展相应的每张映射 表的大小即可。 对于高可配置灵活性, 则只需要动态修改每张表中具体的 值即可。 由于加入了的国家 /地区映射表, 也可以解决不同国家 /地区规范不 一致的问题。
参见图 9, 图 9为本发明实施例中编码格式转换的流程图, 该流程可包 括以下步骤:
步骤 901、 帐号 A发送消息给帐号 B, 消息中携带编码格式 ID为 15。 步骤 902、 网关收到该消息后, 查找到帐号 A的帐号 ID为 3 , 在第一 帐号组的第一级帐号归属映射表中查找到归属区域为欧洲。
步骤 903、 网关查找到帐号 A在第二级国家 /地区归属映射表中的通信 协议类型为 SMPP。
步骤 904、 网关根据消息中的编码格式 ID为 15 , 在第三级欧洲地区 SMPP的协议归属映射表中查找到该消息的编码格式为 7BIT。
步骤 905、 网关根据目标帐号 B , 在第二帐号组的帐号归属映射表中找 到目标帐号 B支持的编码格式为 UNICODE。
步骤 906、 网关以 7BIT为索引, 在 UNICODE的编码格式归属映射表 中查找用于进行转换处理的转换函数 7BIT_TO_UNICODE。
步骤 907、 网关调用转换函数 7BIT_TO_UNICODE, 将帐号 A发来的 消息转换为 UNICODE编码格式的目标消息。
步骤 908、 网关将目标消息发送给目标帐号。
图 9所示实施例中, 基于上述各级映射表, 实现源消息的编码格式的 准确识别 , 以及目标编码格式的准备标识 , 从而实现编码格式转换的正确 处理, 实现用户之间的通信, 提高用户体验。
参见图 10,图 10为本发明实施例中编码格式转换失败处理的另一流程 图, 该流程可包括:
步骤 1001、 帐号 C发送消息给帐号 A, 消息中携带的编码格式 ID为
15。
步骤 1002、 网关根据帐号 C的帐号 ID为 1 , 在第一帐号组的第一级帐 号归属映射表中查找帐号 C的归属区域为中国。
步骤 1003、网关查找到帐号 C在第二级国家 /地区归属映射表中的通信 协议类型为 CMPP。
步骤 1004、 网关根据编码格式 ID为 15 , 从 CMPP的第三级协议归属 映射表中找到匹配的编码格式 ID, 对应编码格式为 GBK。
步骤 1005、 网关根据目标帐号 A, 在第二帐号组的帐号归属映射表中 找到目标帐号 A支持的编码格式为 7BIT。
步骤 1006、 网关以 GBK为索引, 在 7BIT的编码格式归属映射表中查 找处理方式, 查找的结果为不支持由 GBK向 7BIT的转换。
步骤 1007、 网关根据预设的传输处理策略, 拒绝下发源消息。
图 10所示流程为本发明对特殊情况的处理实施例。
参见图 11 , 图 11为本发明实施例中对源信息的编码格式识别失败的处 理流程图, 该流程可包括:
步骤 1101、帐号 A发送消息给帐号 B,消息中携带编码格式 ID为 200。 步骤 1102、 网关收到该消息后, 查找到帐号 A的帐号 ID为 3 , 在第一 帐号组的第一级帐号归属映射表中查找到归属区域为欧洲。
步骤 1103、网关查找到帐号 A在第二级国家 /地区归属映射表中的通信 协议类型为 SMPP。
步骤 1104、 网关根据消息中的编码格式 ID为 200, 在第三级欧洲地区 SMPP的协议归属映射表中未查找到与该 200相匹配的编码格式 ID。
步骤 1105、 网关不识别源消息, 则根据预设传输处理策略为透传不识 别的消息, 将源消息透传给帐号 B。
综上所述, 本发明的实现不仅可正确处理编码转换, 方便系统配置与 扩展, 而且能够正确处理实际通信中遇到的各种情况。 本发明的精神和范围。 这样, 倘若本发明的这些修改和变型属于本发明权 利要求及其等同技术的范围之内, 则本发明也意图包含这些改动和变型在 内。
Claims
1、 一种编码格式识别方法, 其特征在于, 该方法包括:
预设第一帐号组的编码格式信息;
接收基于源帐号发送的源信息;
根据所述源帐号, 从所述第一帐号组的编码格式信息中, 查找出所述 源帐号所属的归属区域;
根据所述源帐号所属的归属区域, 从所述第一帐号组的编码格式信息 中, 查找出在所述源帐号所属的归属区域所规范的通信协议;
根据所述源帐号和所述源信息, 从所述第一帐号组的编码格式信息中, 查找出所述源帐号所属的归属区域所规范的通信协议内, 所述源信息釆用 的源编码格式。
2、 根据权利要求 1所述的方法, 其特征在于, 所述第一帐号组的编码 格式信息包括: 第一帐号组内各帐号各自所属的归属区域、 各归属区域所 规范的通信协议、 各通信协议所规范的各编码格式描述信息;
根据所述源帐号和所述源信息查找出所述源信息釆用的源编码格式包 括:
根据所述源帐号, 确定所述源帐号在所述源帐号所属的归属区域内釆 用的源通信协议;
从所述源帐号所属的归属区域所规范的通信协议内, 找出与所述源通 信协议相匹配的通信协议;
从所述相匹配的通信协议所规范的各编码格式描述信息中, 找出与所 述源信息内携带的编码格式描述信息相匹配的源编码格式描述信息;
由所述源编码格式描述信息, 识别出所述源信息所釆用的源编码格式。
3、 根据权利要求 2所述的方法, 其特征在于, 所述各通信协议所规范 的各编码格式描述信息包括: 各编码格式标识值和各编码格式标识值对应 的编码格式;
所述源信息内携带的编码格式描述信息为源编码格式标识值; 所述从 相匹配的通信协议所规范的各编码格式描述信息中, 找出与源信息内携带 的编码格式描述信息相匹配的源编码格式描述信息包括: 从相匹配的通信 协议所规范的各编码格式标识值中, 找出与所述源信息内携带的编码格式 标识值相同的标识值;
所述由源编码格式描述信息, 识别出源信息所釆用的源编码格式包括: 根据找出的所述标识值对应的编码格式, 确定所述源信息釆用的源编码格 式。
4、 根据权利要求 1至 3任一项所述的方法, 其特征在于, 该方法还包 括:
从所述第一帐号组的编码格式信息中, 未查找出所述源信息釆用的源 编码格式时, 按照预设传输处理策略, 处理所述源信息。
5、 一种编码格式转换方法, 其特征在于, 该方法包括:
预设第二帐号组的编码转换信息;
根据目标帐号, 从所述第二帐号组的编码转换信息中, 找出所述目标 帐号所支持的目标编码格式;
从所述第二帐号组的编码转换信息中, 找出能够将源编码格式转换为 目标编码格式的转换处理策略; 其中, 所述源编码格式为源信息所釆用的 编码格式; 基于所述目标帐号接收基于源帐号发送的所述源信息;
根据所述转换处理策略, 将所述源信息转换为釆用所述目标编码格式 的目标信息。
6、 根据权利要求 5所述的方法, 其特征在于, 所述第二帐号组的编码 转换信息包括: 第二帐号组内各帐号所支持的编码格式描述信息、 目标帐 号所属通信系统所支持的各编码格式、 和各编码格式向目标编码格式转换 的各转换处理策略;
所述从第二帐号组的编码转换信息中, 找出能够将源编码格式转换为 目标编码格式的转换处理策略包括:
从所述通信系统所支持的各编码格式中, 找出与所述源编码格式相匹 配的编码格式; 从所述各转换处理策略中, 找出所述相匹配的编码格式向 所述目标编码格式转换的转换处理策略。
7、 根据权利要求 5或 6所述的方法, 其特征在于, 该方法还包括: 从所述第二帐号组的编码转换信息中, 未找到能够将源编码格式转换 为目标编码格式的转换处理策略时, 按照预设传输处理策略, 处理所述源 信息。
8、 一种编码格式处理方法, 其特征在于, 该方法包括: 预设第一帐号 组的编码格式信息; 预设第二帐号组的编码转换信息; 该方法还包括: 基于目标帐号接收基于源帐号发送的源信息;
根据所述源帐号, 从所述第一帐号组的编码格式信息中, 查找出所述 源帐号所属的归属区域;
根据所述源帐号所属的归属区域, 从所述第一帐号组的编码格式信息 中, 查找出在所述源帐号所属的归属区域所规范的通信协议;
根据所述源帐号和所述源信息, 从所述第一帐号组的编码格式信息中, 查找出所述源帐号所属的归属区域所规范的通信协议内, 所述源信息釆用 的源编码格式;
根据目标帐号, 从所述第二帐号组的编码转换信息中, 找出所述目标 帐号所支持的目标编码格式;
从所述第二帐号组的编码转换信息中, 找出能够将所述源编码格式转 换为目标编码格式的转换处理策略; 其中, 所述源编码格式为源信息所釆 用的编码格式; 基于所述目标帐号接收基于源帐号发送的所述源信息; 根据所述转换处理策略, 将所述源信息转换为釆用所述目标编码格式 的目标信息。
9、 一种编码格式识别装置, 其特征在于, 该装置包括: 第一存储模块、 第一查找模块、 第二查找模块和第三查找模块; 其中,
所述第一存储模块, 用于存储预设的第一帐号组的编码格式信息; 所述第一查找模块, 用于根据源帐号, 从所述第一帐号组的编码格式 信息中, 查找出所述源帐号所属的归属区域;
所述第二查找模块, 用于根据所述源帐号所属的归属区域, 从所述第 一帐号组的编码格式信息中, 查找出在所述源帐号所属的归属区域所规范 的通信协议;
所述第三查找模块, 用于根据所述源帐号和所述源信息, 从所述第一 帐号组的编码格式信息中, 查找出所述源帐号所属的归属区域所规范的通 信协议内, 所述源信息釆用的源编码格式。
10、 根据权利要求 9所述的装置, 其特征在于, 所述第一帐号组的编 码格式信息包括: 第一帐号组内各帐号各自所属的归属区域、 各归属区域 内的通信协议、 和各通信协议所规范的各编码格式描述信息;
所述第三查找模块进一步包括: 子查找处理模块和识别模块; 其中, 所述子查找处理模块, 用于根据所述源帐号, 确定所述源帐号在所述 源帐号所属的归属区域内釆用的源通信协议; 从所述源帐号所属的归属区 域所规范的通信协议内, 找出与所述源通信协议相匹配的通信协议;
识别模块, 用于从所述相匹配的通信协议所规范的各编码格式描述信 息中, 找出与所述源信息内携带的编码格式描述信息相匹配的源编码格式 描述信息; 由所述源编码格式描述信息, 识别出所述源信息所釆用的源编 码格式。
11、根据权利要求 9或 10所述的装置, 其特征在于, 所述装置还包括: 第一控制处理模块, 用于在所述第三查找模块从所述第一帐号组的编 码格式信息中, 未查找到出所述源信息釆用的源编码格式时, 按照预设传 输处理策略, 处理所述源信息。
12、 一种编码格式转换装置, 其特征在于, 该装置包括: 第二存储模 块、 第四查找模块、 第五查找模块和转换模块; 其中,
所述第二存储模块, 用于存储预设的第二帐号组的编码转换信息; 所述第四查找模块, 用于根据目标帐号, 从所述第二帐号组的编码转 换信息中, 找出所述目标帐号所支持的目标编码格式;
所述第五查找模块, 用于从所述第二帐号组的编码转换信息中, 找出 能够将源编码格式转换为目标编码格式的转换处理策略; 其中, 所述源编 码格式为源信息所釆用的编码格式; 所述目标帐号用于基于所述目标帐号 接收基于源帐号发送的所述源信息;
所述转换模块, 用于根据所述转换处理策略, 将所述源信息转换为釆 用所述目标编码格式的目标信息。
13、 根据权利要求 12所述的装置, 其特征在于, 所述第二帐号组的编 码转换信息包括: 第二帐号组内各帐号所支持的编码格式描述信息、 目标 帐号所属通信系统所支持的各编码格式、 和各编码格式向目标编码格式转 换的各转换处理策略;
所述第四查找模块, 进一步用于从所述通信系统所支持的各编码格式 中, 找出与所述源编码格式相匹配的编码格式;
所述第五查找模块, 进一步用于从所述各转换处理策略中, 找出所述 相匹配的编码格式向所述目标编码格式转换的转换处理策略。
14、 根据权利要求 12或 13所述的装置, 其特征在于, 所述装置还包 括: 第二控制处理模块, 用于在所述第五查找模块从所述第二帐号组的编 码转换信息中, 未找到能够将源编码格式转换为目标编码格式的转换处理 策略时, 按照预设传输处理策略, 处理所述源信息。
15、 一种编码格式处理系统, 其特征在于, 该系统包括: 编码格式识 别装置和编码格式转换装置; 其中,
所述编码格式识别装置, 包括: 第一存储模块、 第一查找模块、 第二 查找模块和第三查找模块; 其中,
所述存储模块, 用于存储预设的第一帐号组的编码格式信息; 所述第一查找模块, 用于根据源帐号, 从所述第一帐号组的编码格式 信息中, 查找出所述源帐号所属的归属区域;
所述第二查找模块, 用于根据所述源帐号所属的归属区域, 从所述第 一帐号组的编码格式信息中, 查找出在所述源帐号所属的归属区域所规范 的通信协议;
所述第三查找模块, 用于根据所述源帐号和所述源信息, 从所述第一 帐号组的编码格式信息中, 查找出所述源帐号所属的归属区域所规范的通 信协议内, 所述源信息釆用的源编码格式;
所述编码格式转换装置, 包括: 第二存储模块、 第四查找模块、 第五 查找模块和转换模块; 其中,
所述第二存储模块, 用于存储预设的第二帐号组的编码转换信息; 所述第四查找模块, 用于根据目标帐号, 从所述第二帐号组的编码转 换信息中, 找出所述目标帐号所支持的目标编码格式;
所述第五查找模块, 用于从所述第二帐号组的编码转换信息中, 找出 能够将源编码格式转换为目标编码格式的转换处理策略; 其中, 所述源编 码格式为源信息所釆用的编码格式; 所述目标帐号用于基于所述目标帐号 接收基于源帐号发送的所述源信息; 所述转换模块, 用于根据所述转换处理策略, 将所述源信息转换为釆 用所述目标编码格式的目标信息。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/516,746 US8890724B2 (en) | 2009-12-24 | 2010-07-07 | Method and device for identifying or converting data—coding and method and system for processing data—coding |
EP10838563.4A EP2503752B1 (en) | 2009-12-24 | 2010-07-07 | Method and apparatus for coding format identification and transformation, processing method and system thereof |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2009102600803A CN102111391A (zh) | 2009-12-24 | 2009-12-24 | 编码格式识别、转换方法及装置、处理方法及系统 |
CN200910260080.3 | 2009-12-24 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011076000A1 true WO2011076000A1 (zh) | 2011-06-30 |
Family
ID=44175421
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2010/075024 WO2011076000A1 (zh) | 2009-12-24 | 2010-07-07 | 编码格式识别、转换方法及装置、处理方法及系统 |
Country Status (4)
Country | Link |
---|---|
US (1) | US8890724B2 (zh) |
EP (1) | EP2503752B1 (zh) |
CN (1) | CN102111391A (zh) |
WO (1) | WO2011076000A1 (zh) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103378994A (zh) * | 2012-04-19 | 2013-10-30 | 北京动力源科技股份有限公司 | 一种通信设备的测试方法及终端 |
US8959365B2 (en) * | 2012-07-01 | 2015-02-17 | Speedtrack, Inc. | Methods of providing fast search, analysis, and data retrieval of encrypted data without decryption |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1893431A (zh) * | 2005-07-05 | 2007-01-10 | 年代数位媒体股份有限公司 | 具有格式与协议转换的内容整合平台 |
CN1988694A (zh) * | 2005-12-23 | 2007-06-27 | 中兴通讯股份有限公司 | 多媒体业务系统接入数字集群系统的方法及业务系统 |
US20080043831A1 (en) * | 2006-08-17 | 2008-02-21 | Sriram Sethuraman | A technique for transcoding mpeg-2 / mpeg-4 bitstream to h.264 bitstream |
CN101321280A (zh) * | 2008-07-22 | 2008-12-10 | 国家广播电影电视总局广播科学研究院 | 一种实时视频转码流媒体服务器 |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1463264A3 (en) * | 1994-12-01 | 2005-11-23 | Sharp Kabushiki Kaisha | Communication equipment |
US6362856B1 (en) * | 1997-06-30 | 2002-03-26 | Sun Microsystems, Inc. | Play to air control workstation system in a distributed object television broadcast studio |
US6407680B1 (en) * | 2000-12-22 | 2002-06-18 | Generic Media, Inc. | Distributed on-demand media transcoding system and method |
SG111087A1 (en) * | 2002-10-03 | 2005-05-30 | St Microelectronics Asia | Cache memory system |
JP4557752B2 (ja) * | 2005-03-07 | 2010-10-06 | 株式会社東芝 | 動画像処理装置、動画像処理方法、及び動画像処理プログラム |
US8155194B2 (en) * | 2005-08-05 | 2012-04-10 | Lsi Corporation | Method and apparatus for MPEG-2 to H.264 video transcoding |
US7729694B2 (en) * | 2006-08-08 | 2010-06-01 | Arinc Incorporated | Systems and methods for facilitating communication between transceivers using different protocols |
US8626951B2 (en) * | 2007-04-23 | 2014-01-07 | 4Dk Technologies, Inc. | Interoperability of network applications in a communications environment |
CN101551792A (zh) * | 2008-04-03 | 2009-10-07 | 鸿富锦精密工业(深圳)有限公司 | 乱码恢复系统及方法 |
-
2009
- 2009-12-24 CN CN2009102600803A patent/CN102111391A/zh active Pending
-
2010
- 2010-07-07 US US13/516,746 patent/US8890724B2/en not_active Expired - Fee Related
- 2010-07-07 EP EP10838563.4A patent/EP2503752B1/en not_active Not-in-force
- 2010-07-07 WO PCT/CN2010/075024 patent/WO2011076000A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1893431A (zh) * | 2005-07-05 | 2007-01-10 | 年代数位媒体股份有限公司 | 具有格式与协议转换的内容整合平台 |
CN1988694A (zh) * | 2005-12-23 | 2007-06-27 | 中兴通讯股份有限公司 | 多媒体业务系统接入数字集群系统的方法及业务系统 |
US20080043831A1 (en) * | 2006-08-17 | 2008-02-21 | Sriram Sethuraman | A technique for transcoding mpeg-2 / mpeg-4 bitstream to h.264 bitstream |
CN101321280A (zh) * | 2008-07-22 | 2008-12-10 | 国家广播电影电视总局广播科学研究院 | 一种实时视频转码流媒体服务器 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2503752A4 * |
Also Published As
Publication number | Publication date |
---|---|
US20120250702A1 (en) | 2012-10-04 |
EP2503752A4 (en) | 2015-08-19 |
US8890724B2 (en) | 2014-11-18 |
CN102111391A (zh) | 2011-06-29 |
EP2503752A1 (en) | 2012-09-26 |
EP2503752B1 (en) | 2018-03-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN101009516B (zh) | 一种进行数据同步的方法、系统及装置 | |
CN110635933B (zh) | 用于管理sdn的网络的装置、控制方法及记录介质 | |
US20070078997A1 (en) | Efficient endpoint matching using a header-to-bit conversion table | |
US20070283048A1 (en) | Method, Apparatus and Computer Program Product for Providing Universal Information Transcoding | |
US20130046900A1 (en) | Dynamic transaction protocol upgrades | |
US20050055461A1 (en) | Determining an international destination address | |
JP6014761B2 (ja) | サービス情報を発見する方法およびデバイス | |
CN107391632B (zh) | 数据库存储处理方法、装置、计算设备及计算机存储介质 | |
US10148739B2 (en) | M2M data querying and invoking methods, querying and invoking devices, and system | |
US20160308801A1 (en) | Email service adapter | |
US9848059B2 (en) | Content handling method, apparatus, and system | |
US20210248483A1 (en) | Data classification and conformation system and method | |
EP2224661A1 (en) | A method, system and apparatus of affair control | |
CN110633329A (zh) | 一种区块链交易记录的系统及方法 | |
WO2011076000A1 (zh) | 编码格式识别、转换方法及装置、处理方法及系统 | |
JP2017503371A (ja) | 環境コンテキストを共有するための方法及び装置 | |
US20120303601A1 (en) | Mobile search method and system thereof | |
WO2013170796A1 (zh) | 数据更新方法、系统和设备 | |
KR101700198B1 (ko) | 장치 관리를 위한 노드의 주소 표현 방법 및 이를 위한 장치 | |
US20100136910A1 (en) | Apparatus and method for device search for high-speed based bluetooth applications | |
WO2015085573A1 (zh) | 一种利用白频谱通信的方法及设备 | |
US10104530B2 (en) | Information query method, device, and system | |
CN115118547A (zh) | F5g终端vlan聚合方法、系统、装置和存储介质 | |
CN104756465B (zh) | 一种路由方法、设备及系统 | |
CN109635250B (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: 10838563 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010838563 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13516746 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 6431/DELNP/2012 Country of ref document: IN |