WO2018000338A1 - 编码格式确定方法及装置 - Google Patents

编码格式确定方法及装置 Download PDF

Info

Publication number
WO2018000338A1
WO2018000338A1 PCT/CN2016/087909 CN2016087909W WO2018000338A1 WO 2018000338 A1 WO2018000338 A1 WO 2018000338A1 CN 2016087909 W CN2016087909 W CN 2016087909W WO 2018000338 A1 WO2018000338 A1 WO 2018000338A1
Authority
WO
WIPO (PCT)
Prior art keywords
encoding format
format
encoding
call
data
Prior art date
Application number
PCT/CN2016/087909
Other languages
English (en)
French (fr)
Inventor
吴鸣
崔恒彬
王琪
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN201680000713.5A priority Critical patent/CN107852647B/zh
Priority to PCT/CN2016/087909 priority patent/WO2018000338A1/zh
Priority to EP17177611.5A priority patent/EP3264735B1/en
Priority to US15/635,207 priority patent/US10348793B2/en
Publication of WO2018000338A1 publication Critical patent/WO2018000338A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/764—Media network packet handling at the destination 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1046—Call controllers; Call servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1059—End-user terminal functionalities specially adapted for real-time communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
    • G—PHYSICS
    • G10—MUSICAL INSTRUMENTS; ACOUSTICS
    • G10L—SPEECH ANALYSIS TECHNIQUES OR SPEECH SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING TECHNIQUES; SPEECH OR AUDIO CODING OR DECODING
    • G10L19/00—Speech or audio signals analysis-synthesis techniques for redundancy reduction, e.g. in vocoders; Coding or decoding of speech or audio signals, using source filter models or psychoacoustic analysis
    • G10L19/04—Speech or audio signals analysis-synthesis techniques for redundancy reduction, e.g. in vocoders; Coding or decoding of speech or audio signals, using source filter models or psychoacoustic analysis using predictive techniques
    • G10L19/16—Vocoder architecture
    • G10L19/18—Vocoders using multiple modes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0014—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the source coding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/74—Admission control; Resource allocation measures in reaction to resource unavailability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
    • H04M7/0072—Speech codec negotiation

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a method and apparatus for determining an encoding format.
  • VoLTE Voice over Long Term Evolution
  • the VoLTE call process includes: the calling terminal sends a request message to the call center, where the request message carries the called number and an encoding format supported by the calling terminal; the call center forwards the received request message to the called terminal; The called terminal sends a request response to the calling terminal through the call center, and the request response carries the encoding format supported by the called terminal; the called terminal and the calling terminal negotiate the call center to determine the code used by the two parties during the call. format. After the calling terminal encodes the data carried in the sent data packet by using the negotiated coding format, the called terminal needs to decode the data through the negotiated coding format after receiving the data packet, and finally completes the normal call process.
  • the calling terminal may use other encoding formats to encode the data carried in the transmitted data packet, and the called terminal cannot decode the received data by using the negotiated encoding format, resulting in decoding. A decoding error and an abnormality occurred during the call.
  • an embodiment of the present disclosure provides an encoding format determining method and apparatus.
  • the technical solution is as follows:
  • an encoding format determining method comprising:
  • the encoding format used during the call is modified from the second encoding format to the first encoding format.
  • the number of data packets is at least two;
  • Modifying the encoding format used during the call from the second encoding format to the first encoding format including:
  • the encoding format used in the call is modified from the second encoding format to the first encoding format.
  • the method further includes:
  • the data to be transmitted is encoded according to the first encoding format, and the encoded data is carried in the data packet and sent to the call center.
  • the method further includes:
  • a format adjustment notification is sent to the call center, and the format adjustment notification carries the first encoding format.
  • the method further includes:
  • the SIP supports the encoding format supported by the call center through the session initiation protocol SIP;
  • an encoding format determining apparatus comprising:
  • a data receiving module configured to receive a data packet forwarded by the call center during a VoLTE call, where the data packet carries a first encoding format
  • a format detection module configured to detect whether the first encoding format is the same as the negotiated second encoding format
  • the format confirmation module is configured to modify the encoding format used in the call from the second encoding format to the first encoding format if not identical.
  • the number of data packets is at least two;
  • Format confirmation module including:
  • a number statistics submodule configured to count the number of the first encoding format and the second encoding format of the at least two data packets are different
  • a number detection submodule configured to detect whether the number is greater than a preset threshold
  • the code determining submodule is configured to modify the encoding format used in the call from the second encoding format to the first encoding format if the number is greater than a preset threshold.
  • the device further includes:
  • the data sending module is configured to encode the data to be transmitted according to the first encoding format, and carry the encoded data in the data packet and send the data to the call center.
  • the device further includes:
  • the format notification module is configured to send a format adjustment notification to the call center, where the format adjustment notification carries the first encoding format.
  • the device further includes:
  • a format sending module configured to send a coding format supported by the call center to the call center during a VoLTE call
  • the request receiving module is configured to receive a format confirmation request sent by the call center, where the format confirmation request carries the negotiated second encoding format;
  • a format storage module configured to respond to the format confirmation request and store the second encoding format.
  • an encoding format determining apparatus comprising:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the encoding format used during the call is modified from the second encoding format to the first encoding format.
  • the data packet carries a first encoding format; detecting whether the first encoding format is the same as the negotiated second encoding format; if not, the session used during the call
  • the encoding format is modified from the second encoding format to the first encoding format; when the calling terminal uses other encoding formats to encode the data carried in the transmitted data packet, the called terminal cannot use the negotiated encoding format to receive the data. Decoding of data, resulting in decoding errors and The problem occurs when the first encoding format carried in the data packet is different from the negotiated second encoding format, and the received data packet is decoded by using the first encoding format to ensure normal call quality. effect.
  • FIG. 1 is a schematic diagram of an implementation environment involved in an encoding format determining method according to some exemplary embodiments
  • FIG. 2 is a flowchart of a method for determining an encoding format according to an exemplary embodiment
  • FIG. 3 is a flowchart of a method for determining an encoding format according to another exemplary embodiment
  • FIG. 4 is a schematic diagram of a packet header of an RTP voice packet according to an exemplary embodiment
  • FIG. 5 is a flowchart of a method for determining an encoding format according to an exemplary embodiment
  • FIG. 6 is a flowchart of a method for encoding format negotiation according to an exemplary embodiment
  • FIG. 7 is a block diagram of an encoding format determining apparatus according to an exemplary embodiment
  • FIG. 8 is a block diagram of an encoding format determining apparatus according to another exemplary embodiment.
  • FIG. 9 is a block diagram of an encoding format determining apparatus according to an exemplary embodiment.
  • VoLTE call process is first introduced and described.
  • the VoLTE call process includes the following steps:
  • the calling terminal sends an INVITE message to the call center through a SIP (Session Initiation Protocol), where the INVITE message includes the number of the called terminal and an encoding format supported by the calling terminal.
  • SIP Session Initiation Protocol
  • the encoding formats supported by the calling terminal are: AMR-WB (Adaptive Multi-rate-Wideband) 104, AMR-WB105, and AMR-WB106.
  • AMR-WB Adaptive Multi-rate-Wideband
  • the call center feeds back a response message to the calling terminal, where the response message is used to indicate that the INVITE message is being processed.
  • the call center forwards the INVITE message to the called terminal in the idle state.
  • the called terminal responds to the received INVITE message, and the called terminal sends an INVITE response to the calling terminal through the call center, and the INVITE response carries the encoding format supported by itself.
  • the encoding formats supported by the called terminal include: AMR-WB104, AMR-WB106, and AMR-WB107.
  • the calling terminal feeds back a confirmation message PRACK to the called terminal through the call center.
  • the called terminal after receiving the PRACK, the called terminal feeds back the PRACK response to the calling terminal through the call center.
  • the calling terminal After receiving the PRACK response forwarded by the call center, the calling terminal sends an UPDATE message to the called terminal through the call center, where the UPDATA message carries the negotiated coding format.
  • the calling terminal negotiates with the called terminal, it determines that the encoding format is AMR-WB104.
  • the called terminal after receiving the UPDATE message, the called terminal sends an UPDATE response to the calling terminal through the call center.
  • the UPDATE response is used to indicate that the encoding format negotiation is completed, the VoLTE calling process ends, and the VoLTE call process is entered.
  • FIG. 1 is a schematic diagram of an implementation environment involved in an encoding format determining method according to some exemplary embodiments. As shown in FIG. 1, the implementing environment may include: a calling terminal 120, a called terminal 140, and a call center 160. .
  • the calling terminal 120 can be a smart phone, an e-book reader, a MP3 (Moving Picture Experts Group Audio Layer III) player, and an MP4 (Moving Picture Experts Group Audio Layer IV). Standard audio layer Face 4) player and laptop portable computer, etc.
  • a connection is established between the calling terminal 120 and the call center 160 via a mobile data network.
  • the data packet transmitted by the calling terminal 120 is forwarded to the called terminal 140 after being processed by the call center 160; the called terminal 140 and the call center 160 establish a connection through the mobile data network.
  • the data packet transmitted by the called terminal 140 is processed by the call center 160 and forwarded to the calling terminal 120.
  • the called terminal 140 may be a smart phone, an e-book reader, an MP3 player, an MP4 player, a laptop portable computer, or the like.
  • FIG. 2 is a flowchart of a method for determining an encoding format according to an exemplary embodiment. This embodiment is illustrated by using the encoding format determining method in the called terminal 140 in the implementation environment shown in FIG. 1.
  • the encoding format determination method includes:
  • step 201 during the long-term evolution voice service VoLTE call, the data packet forwarded by the call center is received, and the data packet carries the first coding format.
  • step 202 it is detected whether the first encoding format is the same as the negotiated second encoding format.
  • step 203 if not the same, the encoding format used in the call is modified from the second encoding format to the first encoding format.
  • the encoding format determining method detects whether the first encoding format carried in the data packet forwarded by the call center is the same as the negotiated second encoding format when the VoLTE call is received; The same, the encoding format used in the call is modified from the second encoding format to the first encoding format; and the called party is called when the calling terminal uses other encoding formats to encode the data carried in the transmitted data packet.
  • the terminal cannot use the negotiated encoding format to decode the received data, resulting in a decoding error and an abnormality in the call process.
  • the terminal uses The first encoding format decodes the received data packet to ensure the normal call quality.
  • FIG. 3 is a flowchart of a method for determining an encoding format according to another exemplary embodiment. This embodiment is exemplified by applying the encoding format determining method to the implementation environment shown in FIG. 1.
  • the encoding format determination method includes:
  • step 301 during the VoLTE call, the calling terminal sends a data packet to the call center, where the data packet carries the first encoding format.
  • the encoded data is encoded.
  • the bearer is sent to the call center in the data packet, and the data packet is a data packet that the calling terminal sends to the called terminal through the call center.
  • the data packet is an RTP (Realtime Transport Protocol) voice packet.
  • RTP Realtime Transport Protocol
  • step 302 the call center forwards the received data packet sent by the calling terminal to the called terminal.
  • step 303 the called terminal detects whether the first encoding format is the same as the negotiated second encoding format.
  • the called terminal After receiving the data packet forwarded by the call center, the called terminal acquires the first encoding format carried in the data packet.
  • the first encoding format acquired by the called terminal is the PT value in the header of the RTP voice packet.
  • the called terminal compares the obtained first encoding format with the pre-negotiated second encoding format, and detects whether the obtained first encoding format is the same as the pre-negotiated second encoding format.
  • the called terminal may have two detection results during the detection process. If the detection result is the same, the data carried in the received data packet is decoded by using the pre-negotiated second coding format; if the detection result is different, then Go to step 304.
  • the number of data packets forwarded by the call center is at least one. If the detection result is different, the method may be divided into two cases. The first type is when the number of data packets forwarded by the call center is one. And directly performing step 306 to modify the encoding format used in the call process from the second encoding format to Step of the first encoding format; secondly, when the number of data packets forwarded by the call center is at least two, step 304 is performed.
  • step 304 if the first encoding format is different from the second encoding format, the called terminal counts the number of the first encoding format and the second encoding format of the at least two data packets.
  • the called terminal When receiving the at least two data packets forwarded by the call center, the called terminal acquires a first encoding format in each data packet, and compares each obtained first encoding format with a pre-negotiated second encoding format. The number of the obtained first encoding format is different from the pre-negotiated second encoding format.
  • the called terminal receives 5 data packets forwarded by the call center, and assumes that three data packets of the five data packets carry the first coding format, and two data packets carry the second coding format, and the called terminal statistics
  • the number of the first encoding format and the second encoding format of the five data packets is three.
  • step 305 the called terminal detects whether the number is greater than a preset threshold.
  • the called terminal After the number of the first encoding format and the second encoding format of the at least two data packets are counted, the called terminal compares the number of statistics with the pre-threshold value, and detects whether the number of statistics is greater than the pre-predetermined value.
  • the preset threshold may be any positive integer.
  • the preset threshold is 2, in the above example, if the called terminal counts that the number of the first encoding format and the second encoding format of the five data packets are different, the called terminal can detect The number 3 is greater than the preset threshold 2.
  • the called terminal may generate two detection results. If the detected number is greater than the preset threshold, step 306 is performed; if the detected number is less than the preset threshold, the called terminal is used. Decoding of data carried by the packet containing the first encoding format is ignored.
  • the called terminal When the called terminal detects that the number of the first encoding format and the second encoding format of the at least two data packets are different than the preset threshold, the called terminal ignores the data packet including the first encoding format.
  • the preset threshold is usually set to 1, that is, when the first encoding format is detected to be different from the pre-negotiated second encoding format, the encoding used in the call is used.
  • the format is modified from the second encoding format to the first encoding format.
  • step 306 if the number is greater than the preset threshold, the called terminal modifies the encoding format used in the call from the second encoding format to the first encoding format.
  • the called terminal When the called terminal detects the statistics to the first encoding format and the second encoding in the at least two data packets When the number of different formats is greater than the preset threshold, the called terminal changes the encoding format used in the call from the second encoding format to the first encoding format.
  • the first encoding format is used to decode the data carried in the received data packet, and the information in the data is obtained to ensure normal call quality.
  • the encoding format determining method may further include:
  • step 307 the called terminal encodes the data to be transmitted according to the first encoding format, and carries the encoded data in the data packet and sends the data to the call center.
  • the called terminal After the first encoding format is confirmed as the second encoding format, the called terminal encodes the data to be transmitted by the called terminal by using the first encoding format, and carries the data encoded by using the first encoding format in the data packet. Give the call center so that the call center forwards the packet to the calling terminal.
  • step 308 the call center forwards the received data packet to the calling terminal.
  • the encoding format determining method detects whether the first encoding format carried in the data packet forwarded by the call center is the same as the negotiated second encoding format when the VoLTE call is received; The same, the encoding format used in the call is modified from the second encoding format to the first encoding format; and the called party is called when the calling terminal uses other encoding formats to encode the data carried in the transmitted data packet.
  • the terminal cannot use the negotiated encoding format to decode the received data, resulting in a decoding error and an abnormality in the call process.
  • the terminal uses The first encoding format decodes the received data packet to ensure the normal call quality.
  • the method for determining the encoding format may further include the following steps before the called terminal sends the data packet carrying the data encoded by the first encoding format to the calling center, as shown in FIG. 5:
  • step 501 the called terminal sends a format adjustment notification to the call center, where the format adjustment notification carries the first encoding format.
  • the called terminal After the called terminal modifies the encoding format used in the call from the second encoding format to the first encoding format, the called terminal sends a format adjustment notification to the call center, and the format adjustment notification is used to notify the call center that the forwarded data packet is in the data packet.
  • the data is encoded using the first encoding format.
  • step 502 the call center forwards the received format adjustment notification to the calling terminal.
  • the call center After receiving the format adjustment notification, the call center forwards the received format adjustment notification to the calling terminal to notify the calling terminal, and the called terminal will encode the transmitted data using the first encoding format, and the calling terminal needs to use
  • the first encoding format solves the received data transmitted by the called terminal code.
  • the encoding format determining method may further include the following steps, as shown in FIG. 6:
  • step 601 during the VoLTE call, the encoding format supported by the call center is sent to the call center through the SIP protocol.
  • the calling terminal and the called terminal complete the VoLTE call through the call center.
  • the called terminal sends the encoding format supported by the calling center to the call center through the SIP protocol.
  • step 602 the format confirmation request sent by the call center is received, and the format confirmation request carries the negotiated second encoding format.
  • a commonly supported encoding format is selected as the second encoding format after negotiation in the encoding formats supported by the calling terminal and the called terminal.
  • the called terminal After determining the negotiated second encoding format, the called terminal receives a format confirmation request sent by the call center, and the format confirmation request is used to confirm the negotiated second encoding format.
  • step 603 a format confirmation request is responded and a second encoding format is stored.
  • the called terminal After receiving the format confirmation request, the called terminal responds with the format confirmation request, and the response indicates that the called terminal confirms the negotiated second encoding format. After confirming the negotiated second encoding format, the called terminal stores or identifies the second encoding format, so that when the VoLTE call is used, the data to be transmitted is encoded by using the second encoding format.
  • FIG. 7 is a block diagram of an encoding format determining apparatus, as shown in FIG. 7, which is applied to a called terminal 140 in the implementation environment shown in FIG. 1 according to an exemplary embodiment.
  • Determining devices include but are not limited to:
  • the data receiving module 720 is configured to receive, during the long-term evolution voice service VoLTE call, a data packet forwarded by the call center, where the data packet carries the first encoding format.
  • the format detection module 740 is configured to detect whether the first encoding format is the same as the negotiated second encoding format.
  • the format confirmation module 760 is configured to, if not identical, the code grid used during the call The formula is modified from the second encoding format to the first encoding format.
  • the encoding format determining apparatus detects whether the first encoding format carried in the data packet forwarded by the call center is the same as the negotiated second encoding format when the VoLTE call is received; The same, the encoding format used in the call is modified from the second encoding format to the first encoding format; and the called party is called when the calling terminal uses other encoding formats to encode the data carried in the transmitted data packet.
  • the terminal cannot use the negotiated encoding format to decode the received data, resulting in a decoding error and an abnormality in the call process.
  • the terminal uses The first encoding format decodes the received data packet to ensure the normal call quality.
  • FIG. 8 is a block diagram of an encoding format determining apparatus, as shown in FIG. 8, which is applied to a called terminal 140 in the implementation environment shown in FIG. 1, the encoding is performed, according to another exemplary embodiment.
  • Format determining means include but are not limited to:
  • the data receiving module 810 is configured to receive, during a long-term evolution voice service VoLTE call, a data packet forwarded by the call center, where the data packet carries a first encoding format.
  • the format detection module 820 is configured to detect whether the first encoding format is the same as the negotiated second encoding format.
  • the format confirmation module 830 is configured to modify the encoding format used during the call from the second encoding format to the first encoding format if not identical.
  • the format confirmation module 830 includes: a number statistics submodule 831, a number detection submodule 832, and an encoding determination submodule 833.
  • the number statistics sub-module 831 is configured to count the number of the first encoding format and the second encoding format of the at least two data packets.
  • the number detection sub-module 832 is configured to detect whether the number is greater than a preset threshold.
  • the encoding determination sub-module 833 is configured to modify the encoding format used in the call from the second encoding format to the first encoding format if the number is greater than a preset threshold.
  • the device may further include: a data sending module 840.
  • the data sending module 840 is configured to encode the data to be transmitted according to the first encoding format, and carry the encoded data in the data packet and send the data to the call center.
  • the device may further include: a format notification module 850.
  • the format notification module 850 is configured to send a format adjustment notification to the call center, and the format adjustment is The knowledge carries the first encoding format.
  • the apparatus may further include: a format sending module 860, a request receiving module 870, and a format storage module 880.
  • the format sending module 860 is configured to send a coding format supported by the call center to the call center through the session initiation protocol SIP when the VoLTE call is made.
  • the request receiving module 870 is configured to receive a format confirmation request sent by the call center, where the format confirmation request carries the negotiated second encoding format.
  • the format storage module 880 is configured to respond to the format confirmation request and store the second encoding format.
  • the encoding format determining apparatus detects whether the first encoding format carried in the data packet forwarded by the call center is the same as the negotiated second encoding format when the VoLTE call is received; The same, the encoding format used in the call is modified from the second encoding format to the first encoding format; and the called party is called when the calling terminal uses other encoding formats to encode the data carried in the transmitted data packet.
  • the terminal cannot use the negotiated encoding format to decode the received data, resulting in a decoding error and an abnormality in the call process.
  • the terminal uses The first encoding format decodes the received data packet to ensure the normal call quality.
  • An exemplary embodiment of the present disclosure provides an encoding format determining apparatus capable of implementing an encoding format determining method provided by the present disclosure, the encoding format determining apparatus comprising: a processor, a memory for storing processor-executable instructions;
  • processor is configured to:
  • the encoding format used during the call is modified from the second encoding format to the first encoding format.
  • FIG. 9 is a block diagram of an encoding format determining apparatus according to an exemplary embodiment.
  • device 900 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a gaming console, a tablet device, a medical device, a fitness device, a personal digital assistant, and the like.
  • apparatus 900 can include one or more of the following components: processing component 902, memory 904, power component 906, multimedia component 908, audio component 910, input/output (I/O) interface 912, sensor component 914, and Communication component 916.
  • Processing component 902 typically controls the overall operation of device 900, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • Processing component 902 can include one or more processors 918 to execute instructions to perform all or part of the steps of the above described methods.
  • processing component 902 can include one or more modules to facilitate interaction between component 902 and other components.
  • processing component 902 can include a multimedia module to facilitate interaction between multimedia component 908 and processing component 902.
  • Memory 904 is configured to store various types of data to support operation at device 900. Examples of such data include instructions for any application or method operating on device 900, contact data, phone book data, messages, pictures, videos, and the like.
  • the memory 904 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk or Optical Disk.
  • Power component 906 provides power to various components of device 900.
  • Power component 906 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for device 900.
  • the multimedia component 908 includes a screen between the device 900 and the user that provides an output interface.
  • the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor can sense not only the boundaries of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation.
  • the multimedia component 908 includes a front camera and/or a rear camera. When the device 900 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 910 is configured to output and/or input an audio signal.
  • audio component 910 includes a microphone (MIC) that is configured to receive an external audio signal when device 900 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode.
  • the received audio signal can be It is further stored in the memory 904 or transmitted via the communication component 916.
  • the audio component 910 also includes a speaker for outputting an audio signal.
  • the I/O interface 912 provides an interface between the processing component 902 and the peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.
  • Sensor assembly 914 includes one or more sensors for providing device 900 with various aspects of status assessment.
  • sensor component 914 can detect an open/closed state of device 900, a relative positioning of components, such as a display and a keypad of device 900, and sensor component 914 can also detect a change in position of one component of device 900 or device 900, user The presence or absence of contact with device 900, device 900 orientation or acceleration/deceleration and temperature variation of device 900.
  • Sensor assembly 914 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 914 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 914 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • Communication component 916 is configured to facilitate wired or wireless communication between device 900 and other devices.
  • the device 900 can access a wireless network based on a communication standard, such as Wi-Fi, 2G or 3G, or a combination thereof.
  • communication component 916 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel.
  • communication component 916 also includes a near field communication (NFC) module to facilitate short range communication.
  • NFC near field communication
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • device 900 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation for performing the above described encoding format determination method.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A gate array
  • controller microcontroller, microprocessor or other electronic component implementation for performing the above described encoding format determination method.
  • non-transitory computer readable storage medium comprising instructions, such as a memory 904 comprising instructions executable by processor 918 of apparatus 900 to perform the above described encoding format determination method.
  • the non-transitory computer readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本公开提供了一种编码格式确定方法及装置，涉及通信技术领域，所述方法包括：在VoLTE通话时，接收呼叫中心转发的数据包，数据包携带有第一编码格式；检测第一编码格式与协商的第二编码格式是否相同；若不相同，则将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式；解决了当主叫终端使用其它的编码格式对发送的数据包中携带的数据进行编码时，被叫终端使用协商的编码格式无法对接收到的数据进行解码，导致解码错误和通话过程出现异常的问题；达到了在数据包中携带的第一编码格式与协商的第二编码格式不相同时，使用第一编码格式对接收到的数据包进行解码，保证正常的通话质量的效果。

Description

编码格式确定方法及装置 技术领域
本公开涉及通信技术领域，特别涉及一种编码格式确定方法及装置。
背景技术
VoLTE(Voice over Long Term Evolution，长期演进语音业务)通话是指主叫终端与被叫终端之间通过传输数据包的形式实现的网络通话。
相关技术中VoLTE通话过程包括：主叫终端向呼叫中心发送请求消息，该请求消息中携带有被叫号码和主叫终端所支持的编码格式；呼叫中心向被叫终端转发接收到的请求消息；被叫终端通过呼叫中心向主叫终端发送请求响应，该请求响应中携带有被叫终端所支持的编码格式；被叫终端和主叫终端通过呼叫中心协商后确定双方在通话过程中使用的编码格式。当主叫终端使用协商的编码格式对发送的数据包中携带的数据进行编码后，被叫终端在接收到数据包后需要通过协商的编码格式对数据进行解码，最终完成正常的通话过程。
当主叫终端出现异常情况时，主叫终端可能会使用其它的编码格式对发送的数据包中携带的数据进行编码，则被叫终端使用协商的编码格式无法对接收到的数据进行解码，导致解码错误和通话过程出现异常。
发明内容
为了解决相关技术中的问题，本公开实施例提供了一种编码格式确定方法及装置。所述技术方案如下：
根据本公开实施例的第一方面，提供了一种编码格式确定方法，该方法包括：
在VoLTE通话时，接收呼叫中心转发的数据包，数据包携带有第一编码格式；
检测第一编码格式与协商的第二编码格式是否相同；
若不相同，则将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式。
可选的，数据包的个数为至少两个；
将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式，包括：
统计至少两个数据包中的第一编码格式与第二编码格式不相同的个数；
检测个数是否大于预设阈值；
若个数大于预设阈值，则将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式。
可选的，该方法，还包括：
根据第一编码格式对待传送的数据进行编码，将编码后的数据携带在数据包中发送给呼叫中心。
可选的，该方法，还包括：
向呼叫中心发送格式调整通知，格式调整通知中携带有第一编码格式。
可选的，该方法，还包括：
在VoLTE呼叫时，通过会话初始协议SIP向呼叫中心发送自身所支持的编码格式；
接收呼叫中心发送的格式确认请求，格式确认请求中携带有经过协商的第二编码格式；
对格式确认请求进行响应，并存储第二编码格式。
根据本公开实施例的第二方面，提供了一种编码格式确定装置，该装置包括：
数据接收模块，被配置为在VoLTE通话时，接收呼叫中心转发的数据包，数据包携带有第一编码格式；
格式检测模块，被配置为检测第一编码格式与协商的第二编码格式是否相同；
格式确认模块，被配置为若不相同，则将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式。
可选的，数据包的个数为至少两个；
格式确认模块，包括：
个数统计子模块，被配置为统计至少两个数据包中的第一编码格式与第二编码格式不相同的个数；
个数检测子模块，被配置为检测个数是否大于预设阈值；
编码确定子模块，被配置为若个数大于预设阈值，则将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式。
可选的，该装置，还包括：
数据发送模块，被配置为根据第一编码格式对待传送的数据进行编码，将编码后的数据携带在数据包中发送给呼叫中心。
可选的，该装置，还包括：
格式通知模块，被配置为向呼叫中心发送格式调整通知，格式调整通知中携带有第一编码格式。
可选的，该装置，还包括：
格式发送模块，被配置为在VoLTE呼叫时，通过SIP协议向呼叫中心发送自身所支持的编码格式；
请求接收模块，被配置为接收呼叫中心发送的格式确认请求，格式确认请求中携带有经过协商的第二编码格式；
格式存储模块，被配置为对格式确认请求进行响应，并存储第二编码格式。
根据本公开实施例的第三方面，提供了一种编码格式确定装置，该装置包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，处理器被配置为：
在VoLTE通话时，接收呼叫中心转发的数据包，数据包携带有第一编码格式；
检测第一编码格式与协商的第二编码格式是否相同；
若不相同，则将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式。
本公开的实施例提供的技术方案可以包括以下有益效果：
通过在VoLTE通话时，接收呼叫中心转发的数据包，数据包携带有第一编码格式；检测第一编码格式与协商的第二编码格式是否相同；若不相同，则将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式；解决了当主叫终端使用其它的编码格式对发送的数据包中携带的数据进行编码时，被叫终端使用协商的编码格式无法对接收到的数据进行解码，导致解码错误和通 话过程出现异常的问题；达到了在数据包中携带的第一编码格式与协商的第二编码格式不相同时，使用第一编码格式对接收到的数据包进行解码，保证正常的通话质量的效果。
应当理解的是，以上的一般描述和后文的细节描述仅是示意性的，并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并于说明书一起用于解释本公开的原理。
图1是根据部分示例性实施例示出的一种编码格式确定方法所涉及的实施环境的示意图；
图2是根据一示例性实施例示出的一种编码格式确定方法的方法流程图；
图3是根据另一示例性实施例示出的一种编码格式确定方法的方法流程图；
图4是根据一示例性实施例示出的RTP语音包的包头的示意图；
图5是根据一示例性实施例示出的一种编码格式确定方法的方法流程图；
图6是根据一示例性实施例示出的一种编码格式协商的方法流程图；
图7是根据一示例性实施例示出的一种编码格式确定装置的框图；
图8是根据另一示例性实施例示出的一种编码格式确定装置的框图；
图9是根据一示例性实施例示出的一种编码格式确定装置的框图。
具体实施方式
这里将详细地对示意性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示意性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
为了便于对本公开实施例的理解，首先对VoLTE呼叫过程进行介绍和说明。
在一个示例性的例子中，VoLTE呼叫过程包括以下步骤：
第一步，主叫终端通过SIP(Session Initiation Protocol，会话初始协议)向呼叫中心发送INVITE消息，该INVITE消息中包括有被叫终端的号码和主叫终端支持的编码格式。
比如：主叫终端支持的编码格式有：AMR-WB(Adaptive Multi-rate-Wideband，自适应多速率宽带编码)104、AMR-WB105和AMR-WB106。
第二步，呼叫中心在接收到主叫终端发送的INVITE消息后，向主叫终端反馈应答消息，该应答消息用于表示正在处理INVITE消息。
第三步，呼叫中心向处于空闲态的被叫终端转发INVITE消息。
第四步，被叫终端对接收到的INVITE消息进行响应，被叫终端通过呼叫中心向主叫终端发送INVITE响应，INVITE响应中携带有自身所支持的编码格式。
比如：被叫终端所支持的编码格式包括：AMR-WB104、AMR-WB106和AMR-WB107。
第五步，主叫终端在接收到呼叫中心转发的INVITE响应后，通过呼叫中心向被叫终端反馈确认消息PRACK。
第六步，被叫终端接收到PRACK后，通过呼叫中心向主叫终端反馈PRACK响应。
第七步，主叫终端接收到呼叫中心转发的PRACK响应后，通过呼叫中心向被叫终端发送UPDATE消息，该UPDATA消息中携带有协商后的编码格式。
比如：主叫终端与被叫终端进行协商后确定编码格式为AMR-WB104。
第八步，被叫终端在接收到UPDATE消息后，通过呼叫中心向主叫终端发送UPDATE响应，该UPDATE响应用于表示编码格式协商完成，VoLTE呼叫过程结束，进入VoLTE通话过程。
图1是根据部分示例性实施例示出的一种编码格式确定方法所涉及的实施环境的示意图，如图1所示，该实施环境可以包括：主叫终端120、被叫终端140和呼叫中心160。
主叫终端120可以是智能手机、电子书阅读器、MP3(Moving Picture Experts Group Audio Layer III，动态影像专家压缩标准音频层面3)播放器、MP4(Moving Picture Experts Group Audio Layer IV，动态影像专家压缩标准音频层 面4)播放器和膝上型便携计算机等等。
主叫终端120与呼叫中心160之间通过移动数据网络建立连接。主叫终端120传输的数据包经过呼叫中心160的处理后转发给被叫终端140；被叫终端140与呼叫中心160之间通过移动数据网络建立连接。被叫终端140传输的数据包经过呼叫中心160处理后转发给主叫终端120。
被叫终端140可以是智能手机、电子书阅读器、MP3播放器、MP4播放器和膝上型便携计算机等等。
图2是根据一示例性实施例示出的一种编码格式确定方法的方法流程图。本实施例以该编码格式确定方法应用于图1所示的实施环境中的被叫终端140中举例说明。该编码格式确定方法包括：
在步骤201中，在长期演进语音业务VoLTE通话时，接收呼叫中心转发的数据包，数据包携带有第一编码格式。
在步骤202中，检测第一编码格式与协商的第二编码格式是否相同。
在步骤203中，若不相同，则将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式。
综上所述，本实施例中提供的编码格式确定方法，通过在VoLTE通话时，检测接收到呼叫中心转发的数据包中携带的第一编码格式与协商的第二编码格式是否相同；若不相同，则将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式；解决了当主叫终端使用其它的编码格式对发送的数据包中携带的数据进行编码时，被叫终端使用协商的编码格式无法对接收到的数据进行解码，导致解码错误和通话过程出现异常的问题；达到了在数据包中携带的第一编码格式与协商的第二编码格式不相同时，使用第一编码格式对接收到的数据包进行解码，保证正常的通话质量的效果。
图3是根据另一示例性实施例示出的一种编码格式确定方法的方法流程图。本实施例以该编码格式确定方法应用于图1所示的实施环境中举例说明。该编码格式确定方法包括：
在步骤301中，在VoLTE通话时，主叫终端向呼叫中心发送数据包，该数据包中携带有第一编码格式。
主叫终端将待发送的数据通过第一编码格式进行编码后，将编码后的数据 携带在数据包中发送给呼叫中心，该数据包是主叫终端通过呼叫中心发送给被叫终端的数据包。
可选的，数据包是RTP(Realtime Transport Protocol，实时传输协议)语音包。
在一个示例性的例子中，RTP语音包的包头如图4所示，其中，每一行包括有32bits，0-9所在的位置分别表示1bit，v表示RTP语音包的版本，v＝2表示是RTP包的第二版本，占有2bits；P表示末尾是否被填充，占有1bit，若末尾被填充，则P＝1；X表示扩展，占有1bit；CC表示贡献源列表的个数，占有4bits；M表示标志，占有1bit；PT表示RTP语音包载荷的类型，占有7bits；序列号(sequence number)，占有16bits，在每发送完一个RTP语音包后序列号的值加1；时间戳(timestamp)，占有32bits，记录了该RTP语音包中第一个字节的采样时刻；同步源标识符(synchronization source(SSRC)identifier)，占有32bits；贡献源列表(contributing source(CSRC)identifier)，包含有0-15项不等，每一项占有32bits，用于标志对一个新RTP语音包有贡献的所有RTP语音包的源。
在步骤302中，呼叫中心将接收到的主叫终端发送的数据包转发给被叫终端。
在步骤303中，被叫终端检测第一编码格式与协商的第二编码格式是否相同。
被叫终端在接收到呼叫中心转发的数据包后，获取数据包中携带的第一编码格式。
在一个示例性的例子中，若数据包为RTP语音包时，被叫终端获取到的第一编码格式为RTP语音包的包头中的PT值。
被叫终端将获取到的第一编码格式与预先协商的第二编码格式进行比较，检测获取到的第一编码格式与预先协商的第二编码格式是否相同。
被叫终端在检测过程中可能存在两种检测结果，若检测结果为相同，则使用预先协商的第二编码格式对接收到的数据包中携带的数据进行解码；若检测结果为不相同，则执行步骤304。
可选的，呼叫中心转发的数据包的个数至少为一个，若检测结果为不相同时，则可以分为两种情况，第一种，当呼叫中心转发的数据包的个数为一个时，则直接执行步骤306中将通话过程中所使用的编码格式由第二编码格式修改为 第一编码格式的步骤；第二种，当呼叫中心转发的数据包的个数为至少两个时，则执行步骤304。
在步骤304中，若第一编码格式与第二编码格式不相同，则被叫终端统计至少两个数据包中第一编码格式与第二编码格式不相同的个数。
被叫终端在接收到呼叫中心转发的至少两个数据包时，获取每个数据包中的第一编码格式，将获取到的每个第一编码格式与预先协商的第二编码格式进行比较，统计获取到的第一编码格式与预先协商的第二编码格式不相同的个数。
比如：被叫终端接收到呼叫中心转发的5个数据包，假定5个数据包中有三个数据包携带有第一编码格式，有2个数据包携带有第二编码格式，则被叫终端统计得到5个数据包中的第一编码格式与第二编码格式不相同的个数为3个。
在步骤305中，被叫终端检测个数是否大于预设阈值。
被叫终端在统计到至少两个数据包中的第一编码格式与第二编码格式不相同的个数后，将统计得到的个数与预先阈值进行比较，检测统计得到的个数是否大于预设阈值。其中，预设阈值可以为任意正整数。
比如：假定预设阈值为2，在上述示例中，被叫终端统计到5个数据包中的第一编码格式与第二编码格式不相同的个数为3个，则被叫终端可以检测到个数3是大于预设阈值2的。
被叫终端在检测个数是否大于预设阈值时，可能出现两种检测结果，若检测到个数大于预设阈值，则执行步骤306；若检测到个数小于预设阈值，则被叫终端忽略对包含第一编码格式的数据包携带数据的解码。
当被叫终端检测到统计到至少两个数据包中的第一编码格式与第二编码格式不相同的个数小于预设阈值时，则被叫终端忽略包含第一编码格式的数据包。
可选的，为了保证正常的通话质量，预设阈值通常设置为1，也就是说在检测到第一编码格式与预先协商的第二编码格式不相同时，则将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式。
在步骤306中，若个数大于预设阈值，则被叫终端将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式。
当被叫终端检测到统计到至少两个数据包中的第一编码格式与第二编码 格式不相同的个数大于预设阈值时，则被叫终端将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式。使用第一编码格式对接收到的数据包中携带的数据进行解码，获取数据中的信息，保证正常的通话质量。
作为一种可能的实现方式，该编码格式确定方法还可以包括：
在步骤307中，被叫终端根据第一编码格式对待传送的数据进行编码，将编码后的数据携带在数据包中发送给呼叫中心。
被叫终端在将第一编码格式确认为第二编码格式后，使用第一编码格式对被叫终端待传送的数据进行编码，并将使用第一编码格式编码后的数据携带在数据包中发送给呼叫中心，以便呼叫中心将该数据包转发给主叫终端。
在步骤308中，呼叫中心将接收到的数据包转发给主叫终端。
综上所述，本实施例中提供的编码格式确定方法，通过在VoLTE通话时，检测接收到呼叫中心转发的数据包中携带的第一编码格式与协商的第二编码格式是否相同；若不相同，则将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式；解决了当主叫终端使用其它的编码格式对发送的数据包中携带的数据进行编码时，被叫终端使用协商的编码格式无法对接收到的数据进行解码，导致解码错误和通话过程出现异常的问题；达到了在数据包中携带的第一编码格式与协商的第二编码格式不相同时，使用第一编码格式对接收到的数据包进行解码，保证正常的通话质量的效果。
需要补充说明的一点是，被叫终端在向呼叫中心发送携带有第一编码格式编码后的数据的数据包之前，该编码格式确定方法还可以包括如下步骤，如图5所示：
在步骤501中，被叫终端向呼叫中心发送格式调整通知，格式调整通知中携带有第一编码格式。
被叫终端在将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式后，向呼叫中心发送格式调整通知，该格式调整通知用于通知呼叫中心，其转发的数据包中的数据是使用第一编码格式进行编码的。
在步骤502中，呼叫中心将接收到的格式调整通知转发给主叫终端。
呼叫中心在接收到格式调整通知后，将接收到的格式调整通知转发给主叫终端，以便通知主叫终端，被叫终端将使用第一编码格式对传输的数据进行编码，主叫终端需要使用第一编码格式对接收到的被叫终端传输的数据进行解 码。
需要补充说明的另一点是，在被叫终端接收到呼叫中心转发的数据包之前，该编码格式确定方法还可以包括如下步骤，如图6所示：
在步骤601中，在VoLTE呼叫时，通过SIP协议向呼叫中心发送自身所支持的编码格式。
在VoLTE通话之前，主叫终端与被叫终端通过呼叫中心先完成VoLTE呼叫的过程，在VoLTE呼叫过程中，被叫终端通过SIP协议向呼叫中心发送自身所支持的编码格式。
在步骤602中，接收呼叫中心发送的格式确认请求，格式确认请求中携带有经过协商的第二编码格式。
主叫终端与被叫终端通过呼叫中心协商后，在主叫终端和被叫终端所支持的编码格式中选择一个共同支持的编码格式作为协商后的第二编码格式。
在确定协商后的第二编码格式后，被叫终端接收呼叫中心发送的格式确认请求，该格式确认请求用于对协商后的第二编码格式进行确认。
在步骤603中，对格式确认请求进行响应，并存储第二编码格式。
被叫终端在接收到格式确认请求后，将该格式确认请求进行响应，该响应表示被叫终端对协商后的第二编码格式的确认。被叫终端在确认协商后的第二编码格式后，将第二编码格式进行存储或标识，便于在VoLTE通话时，使用该第二编码格式对待传送的数据进行编码。
下述为本公开装置实施例，可以用于执行本公开方法实施例。对于本公开装置实施例中未披露的细节，请参照本公开方法实施例。
图7是根据一示例性实施例示出的一种编码格式确定装置的框图，如图7所示，该编码格式确定装置应用于图1所示实施环境中的被叫终端140中，该编码格式确定装置包括但不限于：
数据接收模块720，被配置为在长期演进语音业务VoLTE通话时，接收呼叫中心转发的数据包，数据包携带有第一编码格式。
格式检测模块740，被配置为检测第一编码格式与协商的第二编码格式是否相同。
格式确认模块760，被配置为若不相同，则将通话过程中所使用的编码格 式由第二编码格式修改为第一编码格式。
综上所述，本实施例中提供的编码格式确定装置，通过在VoLTE通话时，检测接收到呼叫中心转发的数据包中携带的第一编码格式与协商的第二编码格式是否相同；若不相同，则将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式；解决了当主叫终端使用其它的编码格式对发送的数据包中携带的数据进行编码时，被叫终端使用协商的编码格式无法对接收到的数据进行解码，导致解码错误和通话过程出现异常的问题；达到了在数据包中携带的第一编码格式与协商的第二编码格式不相同时，使用第一编码格式对接收到的数据包进行解码，保证正常的通话质量的效果。
图8是根据另一示例性实施例示出的一种编码格式确定装置的框图，如图8所示，该编码格式确定装置应用于图1所示实施环境中的被叫终端140中，该编码格式确定装置包括但不限于：
数据接收模块810，被配置为在长期演进语音业务VoLTE通话时，接收呼叫中心转发的数据包，数据包携带有第一编码格式。
格式检测模块820，被配置为检测第一编码格式与协商的第二编码格式是否相同。
格式确认模块830，被配置为若不相同，则将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式。
可选的，数据包的个数为至少两个；格式确认模块830，包括：个数统计子模块831、个数检测子模块832和编码确定子模块833。
个数统计子模块831，被配置为统计至少两个数据包中的第一编码格式与第二编码格式不相同的个数。
个数检测子模块832，被配置为检测个数是否大于预设阈值。
编码确定子模块833，被配置为若个数大于预设阈值，则将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式。
可选的，该装置还可以包括：数据发送模块840。
数据发送模块840，被配置为根据第一编码格式对待传送的数据进行编码，将编码后的数据携带在数据包中发送给呼叫中心。
可选的，该装置还可以包括：格式通知模块850。
格式通知模块850，被配置为向呼叫中心发送格式调整通知，格式调整通 知中携带有第一编码格式。
可选的，该装置还可以包括：格式发送模块860、请求接收模块870和格式存储模块880。
格式发送模块860，被配置为在VoLTE呼叫时，通过会话初始协议SIP向呼叫中心发送自身所支持的编码格式。
请求接收模块870，被配置为接收呼叫中心发送的格式确认请求，格式确认请求中携带有经过协商的第二编码格式。
格式存储模块880，被配置为对格式确认请求进行响应，并存储第二编码格式。
综上所述，本实施例中提供的编码格式确定装置，通过在VoLTE通话时，检测接收到呼叫中心转发的数据包中携带的第一编码格式与协商的第二编码格式是否相同；若不相同，则将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式；解决了当主叫终端使用其它的编码格式对发送的数据包中携带的数据进行编码时，被叫终端使用协商的编码格式无法对接收到的数据进行解码，导致解码错误和通话过程出现异常的问题；达到了在数据包中携带的第一编码格式与协商的第二编码格式不相同时，使用第一编码格式对接收到的数据包进行解码，保证正常的通话质量的效果。
本公开一示例性实施例提供了一种编码格式确定装置，能够实现本公开提供的编码格式确定方法，该编码格式确定装置包括：处理器、用于存储处理器可执行指令的存储器；
其中，处理器被配置为：
在长期演进语音业务VoLTE通话时，接收呼叫中心转发的数据包，数据包携带有第一编码格式；
检测第一编码格式与协商的第二编码格式是否相同；
若不相同，则将通话过程中所使用的编码格式由第二编码格式修改为第一编码格式。
图9是根据一示例性实施例示出的一种编码格式确定装置的框图。例如，装置900可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图9，装置900可以包括以下一个或多个组件：处理组件902，存储器904，电源组件906，多媒体组件908，音频组件910，输入/输出(I/O)接口912，传感器组件914，以及通信组件916。
处理组件902通常控制装置900的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件902可以包括一个或多个处理器918来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件902可以包括一个或多个模块，便于处理组件902和其他组件之间的交互。例如，处理组件902可以包括多媒体模块，以方便多媒体组件908和处理组件902之间的交互。
存储器904被配置为存储各种类型的数据以支持在装置900的操作。这些数据的示例包括用于在装置900上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器904可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件906为装置900的各种组件提供电力。电源组件906可以包括电源管理系统，一个或多个电源，及其他与为装置900生成、管理和分配电力相关联的组件。
多媒体组件908包括在装置900和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件908包括一个前置摄像头和/或后置摄像头。当装置900处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件910被配置为输出和/或输入音频信号。例如，音频组件910包括一个麦克风(MIC)，当装置900处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被 进一步存储在存储器904或经由通信组件916发送。在一些实施例中，音频组件910还包括一个扬声器，用于输出音频信号。
I/O接口912为处理组件902和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件914包括一个或多个传感器，用于为装置900提供各个方面的状态评估。例如，传感器组件914可以检测到装置900的打开/关闭状态，组件的相对定位，例如组件为装置900的显示器和小键盘，传感器组件914还可以检测装置900或装置900一个组件的位置改变，用户与装置900接触的存在或不存在，装置900方位或加速/减速和装置900的温度变化。传感器组件914可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件914还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件914还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件916被配置为便于装置900和其他设备之间有线或无线方式的通信。装置900可以接入基于通信标准的无线网络，如Wi-Fi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件916经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，通信组件916还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置900可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述编码格式确定方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器904，上述指令可由装置900的处理器918执行以完成上述编码格式确定方法。例如，非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公 开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示意性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (11)

  1. 一种编码格式确定方法，其特征在于，所述方法包括：
    在长期演进语音业务VoLTE通话时，接收呼叫中心转发的数据包，所述数据包携带有第一编码格式；
    检测所述第一编码格式与协商的第二编码格式是否相同；
    若不相同，则将通话过程中所使用的编码格式由所述第二编码格式修改为所述第一编码格式。
  2. 根据权利要求1所述的方法，其特征在于，所述数据包的个数为至少两个；
    所述将通话过程中所使用的编码格式由所述第二编码格式修改为所述第一编码格式，包括：
    统计至少两个所述数据包中的所述第一编码格式与所述第二编码格式不相同的个数；
    检测所述个数是否大于预设阈值；
    若所述个数大于所述预设阈值，则将通话过程中所使用的编码格式由所述第二编码格式修改为所述第一编码格式。
  3. 根据权利要求1所述的方法，其特征在于，所述方法，还包括：
    根据所述第一编码格式对待传送的数据进行编码，将编码后的所述数据携带在数据包中发送给所述呼叫中心。
  4. 根据权利要求1至3任一所述的方法，其特征在于，所述方法，还包括：
    向所述呼叫中心发送格式调整通知，所述格式调整通知中携带有所述第一编码格式。
  5. 根据权利要求1至3任一所述的方法，其特征在于，所述方法，还包括：
    在VoLTE呼叫时，通过会话初始协议SIP向所述呼叫中心发送自身所支持的编码格式；
    接收所述呼叫中心发送的格式确认请求，所述格式确认请求中携带有经过 协商的所述第二编码格式；
    对所述格式确认请求进行响应，并存储所述第二编码格式。
  6. 一种编码格式确定装置，其特征在于，所述装置包括：
    数据接收模块，被配置为在长期演进语音业务VoLTE通话时，接收呼叫中心转发的数据包，所述数据包携带有第一编码格式；
    格式检测模块，被配置为检测所述第一编码格式与协商的第二编码格式是否相同；
    格式确认模块，被配置为若不相同，则将通话过程中所使用的编码格式由所述第二编码格式修改为所述第一编码格式。
  7. 根据权利要求6所述的装置，其特征在于，所述数据包的个数为至少两个；
    所述格式确认模块，包括：
    个数统计子模块，被配置为统计至少两个所述数据包中的所述第一编码格式与所述第二编码格式不相同的个数；
    个数检测子模块，被配置为检测所述个数是否大于预设阈值；
    编码确定子模块，被配置为若所述个数大于所述预设阈值，则将通话过程中所使用的编码格式由所述第二编码格式修改为所述第一编码格式。
  8. 根据权利要求6所述的装置，其特征在于，所述装置，还包括：
    数据发送模块，被配置为根据所述第一编码格式对待传送的数据进行编码，将编码后的所述数据携带在数据包中发送给所述呼叫中心。
  9. 根据权利要求6至8任一所述的装置，其特征在于，所述装置，还包括：
    格式通知模块，被配置为向所述呼叫中心发送格式调整通知，所述格式调整通知中携带有所述第一编码格式。
  10. 根据权利要求6至8任一所述的装置，其特征在于，所述装置，还包括：
    格式发送模块，被配置为在VoLTE呼叫时，通过会话初始协议SIP向所述 呼叫中心发送自身所支持的编码格式；
    请求接收模块，被配置为接收所述呼叫中心发送的格式确认请求，所述格式确认请求中携带有经过协商的所述第二编码格式；
    格式存储模块，被配置为对所述格式确认请求进行响应，并存储所述第二编码格式。
  11. 一种编码格式确定装置，其特征在于，所述装置包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    在长期演进语音业务VoLTE通话时，接收呼叫中心转发的数据包，所述数据包携带有第一编码格式；
    检测所述第一编码格式与协商的第二编码格式是否相同；
    若不相同，则将通话过程中所使用的编码格式由所述第二编码格式修改为所述第一编码格式。
PCT/CN2016/087909 2016-06-30 2016-06-30 编码格式确定方法及装置 WO2018000338A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201680000713.5A CN107852647B (zh) 2016-06-30 2016-06-30 编码格式确定方法及装置
PCT/CN2016/087909 WO2018000338A1 (zh) 2016-06-30 2016-06-30 编码格式确定方法及装置
EP17177611.5A EP3264735B1 (en) 2016-06-30 2017-06-23 Method and device for determining coding format in volte
US15/635,207 US10348793B2 (en) 2016-06-30 2017-06-28 Method, device and medium for determining coding format

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/087909 WO2018000338A1 (zh) 2016-06-30 2016-06-30 编码格式确定方法及装置

Publications (1)

Publication Number Publication Date
WO2018000338A1 true WO2018000338A1 (zh) 2018-01-04

Family

ID=59312975

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/087909 WO2018000338A1 (zh) 2016-06-30 2016-06-30 编码格式确定方法及装置

Country Status (4)

Country Link
US (1) US10348793B2 (zh)
EP (1) EP3264735B1 (zh)
CN (1) CN107852647B (zh)
WO (1) WO2018000338A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110662186A (zh) * 2018-06-29 2020-01-07 中国电信股份有限公司 媒体协商方法、媒体网关控制设备和计算机可读存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106464691B (zh) * 2015-03-12 2020-01-10 华为技术有限公司 一种实时传输协议rtp包传输方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1878175A (zh) * 2006-02-28 2006-12-13 华为技术有限公司 一种媒体流桥接设备及一种媒体业务系统
CN101953200A (zh) * 2008-02-20 2011-01-19 阿尔卡特朗讯美国公司 在基于因特网协议的语音切换期间改变语音编码器技术的方法
CN103414697A (zh) * 2013-07-22 2013-11-27 中国联合网络通信集团有限公司 一种voip自适应语音编码方法、系统及sip服务器

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ATE324751T1 (de) * 2004-02-10 2006-05-15 Cit Alcatel Verfahren zur bereitstellung von verbesserter audioqualität zu einer kommunikationssitzung und entsprechendes endgerät und maschinenlesbares speichermedium
WO2010117326A1 (en) * 2009-04-07 2010-10-14 Telefonaktiebolaget Lm Ericsson (Publ) Method and arrangement for session negotiation
CN104156373B (zh) * 2013-05-15 2017-06-06 宏碁股份有限公司 编码格式检测方法及装置
WO2014205834A1 (zh) * 2013-06-29 2014-12-31 华为技术有限公司 调制与编码格式选择方法、用户设备及基站
US10499229B2 (en) * 2016-01-24 2019-12-03 Qualcomm Incorporated Enhanced fallback to in-band mode for emergency calling

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1878175A (zh) * 2006-02-28 2006-12-13 华为技术有限公司 一种媒体流桥接设备及一种媒体业务系统
CN101953200A (zh) * 2008-02-20 2011-01-19 阿尔卡特朗讯美国公司 在基于因特网协议的语音切换期间改变语音编码器技术的方法
CN103414697A (zh) * 2013-07-22 2013-11-27 中国联合网络通信集团有限公司 一种voip自适应语音编码方法、系统及sip服务器

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110662186A (zh) * 2018-06-29 2020-01-07 中国电信股份有限公司 媒体协商方法、媒体网关控制设备和计算机可读存储介质

Also Published As

Publication number Publication date
CN107852647B (zh) 2021-09-28
EP3264735B1 (en) 2020-11-25
CN107852647A (zh) 2018-03-27
EP3264735A1 (en) 2018-01-03
US10348793B2 (en) 2019-07-09
US20180007110A1 (en) 2018-01-04

Similar Documents

Publication Publication Date Title
WO2019144387A1 (zh) 信息配置方法及装置、时频位置的确定方法及装置和基站
CN107277423B (zh) 丢包重传的方法及装置
EP3706349B1 (en) Hybrid automatic repeat request feedback indication and feedback method, device, and base station
WO2018195752A1 (zh) 缓存状态的上报方法及装置
WO2018129936A1 (zh) 信息反馈方法、装置、基站和用户设备
JP6382345B2 (ja) ネットワークジッタ処理方法、装置、端末デバイス、プログラム及び記録媒体
WO2019191948A1 (zh) 下行控制信息格式大小的确定方法及装置
WO2017092392A1 (zh) 信息处理方法及装置
TW201724879A (zh) 在遠距通信期間發送語音對話的轉錄本
US20210314996A1 (en) Method and apparatus for configuring and determining transmission block scheduling interval, and base station
WO2019148465A1 (zh) 控制信令的传输方法、终端及基站
CN107404462B (zh) 调整通话参数的方法及装置
WO2018000338A1 (zh) 编码格式确定方法及装置
WO2016169209A1 (zh) 控制接入的方法和装置
WO2018205279A1 (zh) 用于接收和发送系统消息的方法、装置、用户设备及基站
CN107124679A (zh) 多媒体文件播放的方法和装置
US11444927B2 (en) Method and apparatus for encrypting data
KR102109607B1 (ko) 통신 네트워크에서 송수신 지연을 감소시키기 위한 시스템 및 장치
WO2020097883A1 (zh) 传输消息的方法及装置
WO2016169208A1 (zh) 控制智能设备接入的方法和装置
WO2020252741A1 (zh) 接收状态反馈方法和装置
WO2017000781A1 (zh) 一种视频通信方法及装置
WO2021243699A1 (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: 16906739

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16906739

Country of ref document: EP

Kind code of ref document: A1