WO2021213282A1 - 一种通信方法及系统 - Google Patents

一种通信方法及系统 Download PDF

Info

Publication number
WO2021213282A1
WO2021213282A1 PCT/CN2021/087860 CN2021087860W WO2021213282A1 WO 2021213282 A1 WO2021213282 A1 WO 2021213282A1 CN 2021087860 W CN2021087860 W CN 2021087860W WO 2021213282 A1 WO2021213282 A1 WO 2021213282A1
Authority
WO
WIPO (PCT)
Prior art keywords
call
terminal device
message
user front
user
Prior art date
Application number
PCT/CN2021/087860
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 EP21792822.5A priority Critical patent/EP4132137A4/en
Publication of WO2021213282A1 publication Critical patent/WO2021213282A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/14—WLL [Wireless Local Loop]; RLL [Radio Local Loop]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • One or more embodiments of the present application generally relate to the field of communication, and specifically relate to a communication method and system.
  • CPE Customer Premises Equipment
  • SIM card a device that is inserted with a SIM card and can convert 3G/4G/5G cellular mobile network signals into WiFi signals, thereby providing terminals with WiFi networks.
  • CPE has a built-in modem module, which supports both Internet access and voice calls.
  • Some CPE modem modules also support EVS (Enhanced Voice Service) HD codec.
  • the current voice call function of the CPE is realized by connecting an analog phone with an analog line through the RJ11 interface. Wiring needs to be considered, and the immovability of the analog phone is brought to the user. The experience is poor.
  • analog lines can only transmit narrowband voice signals, and analog phones can only process narrowband voice signals. Therefore, even if the CPE modem module supports EVS HD codec, users cannot experience HD voice calls.
  • Some embodiments of the application provide a communication method and system.
  • the following describes the application from multiple aspects, and the implementations and beneficial effects of the following multiple aspects can be referred to each other.
  • the first aspect of the present application provides a communication method for user front-end equipment, and the method may include:
  • the user front-end device implements a call between the user front-end device and the network side on the first terminal device through a wireless communication mode, where the call includes a called process and a calling process,
  • implementing the call between the user front-end equipment and the network side on the first terminal device includes: the user front-end equipment responds to the received call from the network side for the The call of the user front-end equipment sends the call to the first terminal equipment through the wireless communication mode; and
  • implementing the call between the user front-end device and the network side on the first terminal device includes: the user front-end device responds to the call received from the user through the wireless communication mode.
  • the call setup message of the first terminal device initiates a call to the network side.
  • the user front-end equipment since the user front-end equipment implements the call between the user front-end equipment and the network side on the terminal device through the wireless communication mode, the user can be within the coverage of the wireless communication network between the user front-end equipment and the terminal device Move around at will, thereby optimizing the user experience.
  • the method further includes:
  • the first terminal device In a case where it is determined that the first terminal device meets a predetermined condition, record that the first terminal device is in an online state, and send a registration success message to the first terminal device.
  • the user's front-end device can know the connected terminal device through the registration process. In this way, when the user's front-end device as the called party receives a call from the network side, the call can be sent to the online state. Terminal Equipment.
  • the terminal device that receives the registration success message can display its online status, so that the user can send a call setup message to the user's front-end device through the terminal device, so that the user's front-end device initiates a call to the network side 11.
  • the method further includes:
  • the call may not be sent to the terminal device recorded as offline.
  • the user front-end device sending the call to the first terminal device includes:
  • the user front-end equipment and the terminal equipment complete the call indication and answering actions based on the messages sent through the wireless connection.
  • the answering message sent by the terminal equipment indicates the call type, and the user front-end equipment can follow the support of the terminal equipment.
  • the audio and/or video codec type is negotiated with the network side, and the terminal device can support high-definition voice EVS-WB, EVS-SWB, EVS-FB and other codecs, and when the terminal device also supports video calls, it can also be negotiated It can be used for video communication, and supports general-definition, standard-definition, high-definition and other video formats.
  • the received registration request message or the answer message from the first terminal device includes the audio and/or video codec type supported by the first terminal device.
  • the answer message further includes an address of the first terminal device for receiving and/or sending the media data packet
  • the negotiation notification message also includes an address of the user front-end equipment for receiving and/or sending the media data packet.
  • the user front-end equipment adopts a wireless communication mode:
  • the call setup message indicates that the type of the call is a voice call or a video call and the identity of the called user, and the user front-end device initiates the call to the network side Calls, including:
  • the call request message including the type of the call, the audio or video codec type supported by the first terminal device, and the identity of the called user;
  • the call setup message sent by the terminal device indicates the call type
  • the user front-end device can negotiate media with the network side according to the audio and/or video codec type supported by the terminal device, and the terminal device can support high-definition voice EVS-WB, EVS-SWB, EVS-FB and other codecs, and when the terminal device also supports video calls, it can also be negotiated into video communication, and supports general definition, standard definition, high definition and other video formats.
  • the registration request message or the call establishment message includes the audio and/or video codec type supported by the first terminal device.
  • the received call establishment message from the first terminal device further includes an address of the first terminal device for receiving and/or sending the media data packet
  • the negotiation notification message also includes an address of the user front-end equipment for receiving and/or sending the media data packet.
  • the user front-end device sending the call to the first terminal device further includes, in a wireless communication mode:
  • a third terminal device is recorded as the online state, the call is sent to the third terminal device, and the call is sent to the first terminal device End message
  • sending the call to the third terminal device includes:
  • the user when multiple terminal devices are registered online, the user can switch between the multiple terminal devices at will during the call process, and the call type can also be changed while switching the terminal devices.
  • the registration request message or the answer message received from the third terminal device includes the audio and/or video codec type supported by the third terminal device.
  • the received answer message from the third terminal device further includes an address of the third terminal device for receiving and/or sending the media data packet.
  • the user front-end equipment initiates a call to the network side, which further includes, in a wireless communication mode:
  • a third terminal device is recorded as the online state, the call is sent to the third terminal device, and the call is sent to the first terminal device End message
  • the sending the call to the third terminal device includes:
  • the user when multiple terminal devices are registered online, during a call, the user can switch between multiple terminal devices at will, and the call type can be changed while switching the terminal devices.
  • the received registration request message or the answer message from the third terminal device includes the audio or video codec type supported by the third terminal device.
  • the received answer message from the third terminal device further includes an address of the third terminal device for receiving and/or sending the media data packet.
  • the wireless communication mode is a WiFi communication mode.
  • the identifier of the user front-end device is the user identifier of the user front-end device, or the device identifier of the user front-end device.
  • the second aspect of the present application provides a communication method for terminal equipment, the method including:
  • the call includes a calling process and a called process
  • the realization of the call between the user front-end equipment and the network side includes: the terminal device receives a wireless communication mode from the user front-end equipment from the network side to the user front-end equipment Call; and
  • the realization of the call between the user front-end equipment and the network side includes: the terminal device sends a call setup message to the user front-end equipment through a wireless communication mode, so that the user front-end equipment sends a call to the user front-end equipment.
  • the network side initiates a call.
  • the user front-end equipment since the user front-end equipment implements the call between the user front-end equipment and the network side on the terminal device through the wireless communication mode, the user can be within the coverage of the wireless communication network between the user front-end equipment and the terminal device Move around at will, thereby optimizing the user experience.
  • the method further includes, before the terminal device implements the call for the user front-end device, using the wireless communication mode:
  • the user's front-end device can know the connected terminal device through the registration process. In this way, when the user's front-end device as the called party receives a call from the network side, the call can be sent to the online state. Terminal Equipment.
  • the terminal device that receives the registration success message can display its online status, so that the user can send a call setup message to the user's front-end device through the terminal device, so that the user's front-end device initiates a call to the network side 11.
  • the terminal device receiving a call from the network side of the user's front-end device to the user's front-end device includes:
  • the user front-end equipment and the terminal equipment complete the call indication and answering actions based on the messages sent through the wireless connection.
  • the answering message sent by the terminal equipment indicates the call type, and the user front-end equipment can follow the support of the terminal equipment.
  • the audio and/or video codec type is negotiated with the network side, and the terminal device can support high-definition voice EVS-WB, EVS-SWB, EVS-FB and other codecs, and when the terminal device also supports video calls, it can also be negotiated It can be used for video communication, and supports general-definition, standard-definition, high-definition and other video formats.
  • the registration request message or the answer message includes the audio and/or video codec type supported by the terminal device.
  • the answer message includes an address of the terminal device for receiving and/or sending the media data packet
  • the negotiation result message includes an address of the user front-end equipment for receiving and/or sending the media data packet.
  • the call setup message indicates that the type of the call is a voice call or a video call and the identity of the called user, and further includes:
  • the call setup message sent by the terminal device indicates the call type
  • the user front-end device can negotiate media with the network side according to the audio and/or video codec type supported by the terminal device, and the terminal device can support high-definition voice EVS-WB, EVS-SWB, EVS-FB and other codecs, and when the terminal device also supports video calls, it can also be negotiated into video communication, and supports general definition, standard definition, high definition and other video formats.
  • the registration request message or the call establishment message includes an audio and/or video codec type supported by the terminal device.
  • the call setup message includes an address of the terminal device for receiving and/or sending the media data packet
  • the negotiation notification message includes an address of the user front-end equipment for receiving and/or sending the media data packet.
  • the terminal device receiving a call from the network side of the user's front-end device for the user's front-end device further includes:
  • the user when multiple terminal devices are registered online, during a call, the user can switch between multiple terminal devices at will, and the call type can be changed while switching the terminal devices.
  • the calling process further includes:
  • the terminal device receives a handover failure message from the user front-end device, or receives a call end message from the user front-end device.
  • the user when multiple terminal devices are registered online, during a call, the user can switch between multiple terminal devices at will, and the call type can be changed while switching the terminal devices.
  • the wireless communication mode is a WiFi communication mode.
  • a third aspect of the present application provides a machine-readable medium on which instructions are stored, and when the instructions are run on the machine, the machine is caused to execute any one of the communication methods described above.
  • the fourth aspect of the present application provides a system including: user front-end equipment and terminal equipment, wherein the user front-end equipment is used to execute the above-mentioned communication methods related to the user front-end equipment, and the terminal equipment is used to execute the above-mentioned communication methods. Communication methods related to terminal equipment.
  • Fig. 1 shows a schematic structural diagram of a communication system 10 according to an embodiment of the present application
  • FIG. 2 shows a schematic structural diagram of user front-end equipment 12 and terminal equipment 13 according to an embodiment of the present invention
  • FIG. 3 shows a schematic diagram of the structure and transmission protocol of the control plane signaling between the user front-end equipment 12 and the terminal equipment 13 according to an embodiment of the present invention
  • FIG. 4 shows a schematic diagram of a media plane data transmission protocol between user front-end equipment 12 and terminal equipment 13 according to an embodiment of the present invention
  • FIG. 5 shows a schematic flowchart of a registration process 500 according to an embodiment of the present application
  • FIG. 6 shows a schematic flowchart of a calling process 600 according to an embodiment of the present application
  • FIG. 7 shows a schematic flowchart of a called process 700 according to an embodiment of the present application.
  • FIG. 8 shows a schematic flowchart of a handover process 800 according to an embodiment of the present application
  • FIG. 9 shows a schematic structural diagram of an electronic device 900 according to an embodiment of the present application.
  • A/B can mean A or B; "and/or” in this article is only an association relationship describing the associated object, indicating that there can be three relationships, For example, A and/or B can mean that: A alone exists, A and B exist at the same time, and B exists alone. .
  • first, second, etc. may be used herein to describe various units or data, these units or data should not be limited by these terms. These terms are used only to distinguish one feature from another.
  • first feature may be referred to as the second feature, and similarly the second feature may be referred to as the first feature.
  • Fig. 1 shows a schematic structural diagram of a communication system 10 according to an embodiment of the present invention.
  • the communication system 10 includes a network side 11, a user front-end device 12, and one or more terminal devices 13a-13n (in this case). In the application, they are collectively referred to as terminal equipment 13).
  • the network side 11 may include, but is not limited to, a wireless access network, a core network, and a public data network of a cellular mobile communication network.
  • Cellular mobile communication networks may include, but are not limited to, third-generation mobile communication networks, fourth-generation mobile communication networks, and fifth-generation mobile communication networks.
  • the user front-end equipment 12 is connected to the network side 11 through the air interface of the cellular mobile communication network, and is connected to the terminal equipment 13 through the wireless communication mode.
  • the wireless communication mode can be WiFi communication, that is, the user front-end device 12 converts the received cellular mobile communication network signal into a WiFi signal, so that the terminal device 13 can be connected to the user front-end device 12 through WiFi communication; the wireless communication mode can also be Bluetooth communication, ZigBee communication or other wireless communication modes.
  • the user front-end equipment 12 may also be connected to the terminal device 13 in a wired communication mode.
  • the user front-end equipment 12 is connected through a LAN (Local Area Network) port and a network cable (for example, but not Limited to twisted pair wires, optical cables, coaxial cables, etc.) are connected to the terminal device 13 and communicate with the terminal device 13 based on a local area network protocol (for example, but not limited to, IEEE 802.3, TCP/IP protocol).
  • a local area network protocol for example, but not limited to, IEEE 802.3, TCP/IP protocol.
  • the user front-end device 12 may also be connected to one or more terminal devices 13 through both the above-mentioned wireless communication mode and the wired communication mode.
  • the terminal device 13 may include, but is not limited to, portable or mobile devices, mobile phones, tablet computers, televisions, personal digital assistants, laptop devices, desktop computers, handheld PCs, servers, network devices, graphics devices, video game devices, set-top boxes , Cellular phones, portable media players, handheld devices, wearable devices (for example, display glasses or goggles, head-mounted displays, watches, head-mounted devices, armbands, jewelry, etc.), virtual reality and/or augmented reality devices , Internet of Things equipment, industrial control equipment, in-vehicle infotainment equipment, streaming media client equipment, e-book reading equipment, POS machines, or other electronic equipment capable of wireless communication and/or wired communication.
  • portable or mobile devices mobile phones, tablet computers, televisions, personal digital assistants, laptop devices, desktop computers, handheld PCs, servers, network devices, graphics devices, video game devices, set-top boxes , Cellular phones, portable media players, handheld devices, wearable devices (for example, display glasses or goggles, head-mounted displays, watches, head-mounted devices
  • the user front-end device 12 can establish a call connection with the network side 11, and can implement a call on the terminal device 13 through a wireless communication mode and/or a wired communication mode, where the call includes the called process and Calling process.
  • the user front-end equipment 12 in the process of being called, can receive a call from the network side 11 to the user front-end equipment 12, and can send the call to the terminal equipment through the wireless communication mode and/or the wired communication mode. 13 Send the call.
  • the user front-end device 12 may receive a call establishment message from the terminal device 13 in a wireless communication mode and/or a wired communication mode, and initiate a call to the network side 11.
  • FIG. 2 shows a schematic structural diagram of the user front-end equipment 12 and the terminal device 13 according to an embodiment of the present application.
  • the user front-end equipment 12 may include a first wireless transceiver module 120a and a second wireless transceiver module 120b. And the first call control module 125.
  • the first wireless transceiver module may include a mobile communication radio frequency unit 121, a PS (Packet Switch) protocol stack 122, a TCP/IP (Transmission Control Protocol/Internet Protocol, Transmission Control Protocol/Internet Protocol) protocol stack 123, and IMS (IP Multimedia Subsystem, IP Multimedia Subsystem) protocol stack 124.
  • PS Packet Switch
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • Transmission Control Protocol/Internet Protocol Transmission Control Protocol/Internet Protocol
  • IMS IP Multimedia Subsystem, IP Multimedia Subsystem
  • the second wireless transceiver module may include a UDP/IP (User Datagram Protocol/Internet Protocol) protocol stack 126, a WiFi protocol stack 127, and a WiFi radio frequency unit 128.
  • Each module of the user front-end equipment 12 can be composed of application specific integrated circuit (ASIC), field programmable gate circuit (Field Programmable Gate Array, FPGA), electronic circuit, execution of one or more software or firmware programs (shared , Dedicated or group) processor and/or memory, combinational logic circuit and/or other suitable components that provide the described functions.
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the structures of the first wireless transceiver module and the second wireless transceiver module are not limited to those shown in FIG.
  • the Bluetooth protocol stack can be used instead of the WiFi protocol stack 127; in addition, the first wireless transceiver module and the second wireless transceiver module may also include other units, such as, but not limited to, a baseband processing unit.
  • the user front-end equipment 12 may also include a wired transceiver module.
  • the first wireless transceiver module can implement wireless communication between the user front-end equipment 12 and the network side 11.
  • the mobile communication radio frequency unit 121 can receive and/or send radio frequency signals through an antenna feeder, where the radio frequency signals are used for cellular mobile communications.
  • the PS protocol stack 122, the TCP/IP protocol stack 123, and the IMS protocol stack 124 can respectively encapsulate the PS protocol, the TCP/IP protocol, and the IMS protocol for the data to be sent to the network side 11, or they can respectively encapsulate the data from the network side 11
  • the data is decapsulated by PS protocol, TCP/IP protocol and IMS protocol.
  • the IMS protocol stack 124 decapsulates the data from the network side 11 to obtain an RTP (Real-time Transport Protocol) code stream, or can perform IMS protocol encapsulation on the RTP code stream, and the RTP code stream may include Media data, such as, but not limited to, audio data encoded by EVS, etc.
  • RTP Real-time Transport Protocol
  • the second wireless transceiver module can realize the wireless communication between the user front-end equipment 12 and the terminal device 13.
  • the UDP/IP protocol stack 126 and the WiFi protocol stack 127 can be used to send data to the terminal device 13 respectively.
  • the data is encapsulated in the UDP/IP protocol and the WiFi protocol, and the data from the terminal device 13 may also be de-encapsulated in the UDP/IP protocol and the WiFi protocol respectively.
  • the WiFi radio frequency unit 128 may receive and/or transmit radio frequency signals through an antenna feed, where the radio frequency signals are used for WiFi communication.
  • the first call control module 125 can interact with the network side 11 and the terminal device 13 through the first wireless transceiver module and the second wireless transceiver module during the calling process and the called process, respectively, to interact with the control plane signaling used to control the call. And the media plane data (audio data and/or video data) generated during the call. According to some embodiments of the present application, the first call control module 125 may also interact with the terminal device 13 through the second wireless transceiver module during the registration process to control the control plane signaling used to control the registration, and the terminal device 13 that is successfully registered may Perform the above called process and calling process.
  • the first call control module 125 may also interact with the network side 11 and different terminal devices 13 during the call switching process through the second wireless transceiver module to control the control plane information used to control the call switching.
  • the media plane data (audio data and/or video data) generated during the call.
  • the terminal device 13 may include a third wireless transceiver module 130, a second call control module 134, a HiFi module 135, an analog-to-digital/digital-analog conversion module 136, and an input/output module 137.
  • the third wireless transceiver module may It further includes a WiFi radio frequency unit 131, a WiFi protocol stack 132, and a UDP/IP protocol stack 133.
  • Each module of the terminal device 13 can be composed of application specific integrated circuit (ASIC), field programmable gate circuit (Field Programmable Gate Array, FPGA), electronic circuit, execution of one or more software or firmware programs (shared, Dedicated or group) processors and/or memories, combinational logic circuits, and/or other suitable components that provide the described functions.
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the structure of the third wireless transceiver module is not limited to that shown in FIG. 2, and it may include any suitable number and any suitable type of protocol stack.
  • the Bluetooth protocol may be used in the third wireless transceiver module.
  • the stack replaces the WiFi protocol stack 132; in addition, the third wireless transceiver module may also include other units, such as, but not limited to, a baseband processing unit.
  • the terminal device 13 may also include a wired transceiver module.
  • the third wireless transceiver module can realize wireless communication between the terminal device 13 and the user front-end equipment 12.
  • the WiFi radio frequency unit 131 can receive and/or transmit radio frequency signals through an antenna feeder, wherein the radio frequency signal Used for WiFi communication.
  • the WiFi protocol stack 132 and the UDP/IP protocol stack 133 can respectively encapsulate the WiFi protocol and UDP/IP protocol for the data to be sent to the user front-end device 12, and can also perform the WiFi protocol and UDP respectively on the data from the user front-end device 12 /IP protocol decapsulation.
  • the second call control module 134 can interact with the user front-end equipment 12 through the third wireless transceiver module during the calling process and the called process to control the control plane signaling of the call and the media plane data generated during the call ( Audio data and/or video data). According to some embodiments of the present application, the second call control module 134 may also interact with the user front-end equipment 12 through the third wireless transceiver module during the registration process to control the control plane signaling used to control the registration, and the registered terminal device 13 The above-mentioned called process and calling process can be performed.
  • the HiFi module 135 can decode the media data in the RTP code stream to obtain a PCM (Pulse Code Modulation, pulse code modulation) code stream. For example, the HiFi module 135 can perform EVS decoding on the EVS-encoded audio data in the RTP code stream.
  • PCM Pulse Code Modulation, pulse code modulation
  • the analog-to-digital/digital-to-analog conversion module 136 can convert the analog signal from the input/output module 137 into a digital signal, and can also convert the digital signal from the HiFi module 135 into an analog signal.
  • the input/output module 137 can receive audio input, image input, etc., and can also output audio and images, etc. Examples of the input/output module 137 can include, but are not limited to, speakers, microphones, displays (for example, liquid crystal displays, touch screen displays, etc.) )Wait.
  • FIG. 3 shows the structure and transmission protocol of the control plane signaling between the first call control module 125 and the second call control module 134 in FIG. 2.
  • the control plane signaling between the first call control module 125 and the second call control module 134 may include a command part, a terminal device ID (Identity, identification) part, and a message body part.
  • the command part is used to indicate the type of signaling, which may include, but is not limited to, a 1-byte hexadecimal string;
  • the terminal device ID part is used to indicate the identification of the terminal device 13 (for example, but not limited to , The MAC (Media Access Control, Media Access Control) address of the terminal device 13, which may include, but is not limited to, a 6-byte character string;
  • the message body part is used to indicate the specific content of the signaling, for example, but Not limited to, call type (voice call or video call), codec type, address for receiving and/or sending media data packets (for example, but not limited to, IP address, port number related to media transmission protocol, etc.), etc.
  • call type voice call or video call
  • codec type address for receiving and/or sending media data packets
  • IP address for example, but not limited to, IP address, port number related to media transmission protocol, etc.
  • the transmission of control plane signaling between the first call control module 125 and the second call control module 134 is based on the UDP/IP protocol and the WiFi protocol, where the WiFi protocol includes the WiFi MAC protocol and WiFi PHY (Physical, Physical layer) protocol. It should be noted that the transmission protocol of the control plane signaling is not limited to that shown in FIG. 3.
  • FIG. 4 shows the media plane data transmission protocol between the first call control module 125 and the second call control module 134.
  • the communication between the first call control module 125 and the second call control module 134 The transmission of media plane data is based on RTP/RTCP (Real-time Transport Control Protocol, Real-time Transport Control Protocol) protocol, UDP/IP protocol and WiFi protocol, among which WiFi protocol includes WiFi MAC protocol and WiFi PHY protocol.
  • RTP/RTCP Real-time Transport Control Protocol, Real-time Transport Control Protocol
  • WiFi protocol includes WiFi MAC protocol and WiFi PHY protocol. It should be noted that the transmission protocol of media plane data is not limited to that shown in FIG. 3.
  • FIG. 5 shows a schematic flowchart of the registration process 500 between the user front-end device 12 and the terminal device 13, which needs to be explained.
  • the various steps of the method are presented in a specific order in the embodiments of the present application, the order of the steps can be changed in different embodiments, and in some embodiments, they can be executed at the same time. One or more steps shown in sequence.
  • the registration method 500 includes:
  • S501 Establish a wireless communication connection between the user front-end equipment 12 and the terminal equipment 13;
  • one of a WiFi communication connection, a Bluetooth communication connection, a ZigBee communication connection, and other wireless communication connections can be established between the user front-end device 12 and the terminal device 13;
  • a wired communication connection may also be established between the user front-end equipment 12 and the terminal equipment 13;
  • the terminal device 13 sends a registration request message to the user front-end device 12;
  • the registration request message may include the audio and/or video codec types supported by the terminal device 13, where the audio codec types supported by the terminal device 13 may include, but are not limited to EVS (Enhanced Voice Service, Enhanced Voice Service). Service), AMR (Adaptive multi-Rate, adaptive multi-rate), AMR-WB (Adaptive multi-Rate Wide Band, adaptive multi-rate broadband), and ITU-T G.711 codec, etc., video supported by terminal device 13 Codec types can include, but are not limited to H.264, MPEG-2, MPEG-4, WMA-HD and VC-1 codec, etc.;
  • the user opens the smart terminal App on the terminal device 13, so that the terminal device 13 sends a registration request message to the user front-end device 12, where the smart terminal App may include the second call control module 134;
  • the terminal device 13 automatically sends a registration request message to the user front-end device 12;
  • S503 The user front-end equipment 12 determines whether the terminal device 13 meets the predetermined condition, if so, execute S504 and S505, if not, execute S506 and S507;
  • the predetermined condition may include, but is not limited to, one or more of the following: the identification of the terminal device 13 is in a preset whitelist, and the terminal device 13 has a specific audio and/or video codec type Wait;
  • the user front-end equipment 12 records that the terminal device 13 is online, and if the user front-end equipment 12 receives a call from the network side 11 to the user front-end equipment 12, the call may be sent to the terminal device 13 recorded as online;
  • the user front-end device 12 may also record the audio and/or video codec type of the terminal device 13;
  • the user front-end device 12 sends a registration success message to the terminal device 13, where the registration success message is used to indicate that the terminal device 13 is successfully registered;
  • the terminal device 13 that receives the registration success message can reflect its online status, and can send a call setup message to the user front-end device 12, so that the user front-end device 12 initiates a call to the network side 11;
  • the user front-end device 12 records that the terminal device 13 fails to register. If the user front-end device 12 receives a call from the network side 11 to the user front-end device 12, it will not send the call to the terminal device 13 recorded as a registration failure;
  • the user front-end device 12 sends a registration failure message to the terminal device 13, where the registration failure message is used to indicate that the terminal device 13 fails to register;
  • the terminal device 13 that receives the registration failure message will not send a call setup message to the user front-end device 12, or may send a call setup message to the user front-end device 12, but the user front-end device 12 will not initiate a call to the network side 11;
  • the terminal device 13 For the terminal device 13 that receives the registration success message during the registration of S502-S507, in order to enable the user front-end device 12 to perceive the online status of the terminal device 13 in real time for a period of time, the terminal device 13 and the user front-end device 12 Periodic registration can be continued in between, where S502-S507 are executed for each registration;
  • the foregoing period of time may include, but is not limited to, establishing a wireless communication connection between the terminal device 13 and the user front-end device 12 and enabling the terminal device 13 to enable the user front-end device 12 to implement a call with the network side 11 (for example, but It is not limited to a period of time when the smart terminal APP is turned on, or a period of time when a wireless communication connection is established between the terminal device 13 and the user front-end device 12;
  • the registration request message may not include the audio and/or video codec types supported by the terminal device 13;
  • terminal device 13 that receives the registration failure message during the registration of S502-S507 and the user front-end device 12 can also continue to perform periodic registration, wherein each registration performs S502-S507;
  • the user front-end device 12 determines the time interval between the latest time when the registration request message of the terminal device 13 is received and the current time;
  • the user front-end equipment 12 determines whether the time interval is greater than or equal to the predetermined time interval, if yes, continue to execute S511, if not, return to execute S509;
  • Examples of the predetermined time interval may include, but are not limited to, time intervals of 10 seconds, 1 minute, 5 minutes, 10 minutes, or other lengths;
  • the user front-end equipment 12 changes the online status of the terminal device 13 to an offline state. If the user front-end equipment 12 receives a call from the network side 11 to the user front-end equipment 12, it will not send the call to the terminal recorded as offline. Equipment 13.
  • Table 1 shows an example of the control plane signaling between the user front-end device 12 and the terminal device 13 involved in the registration process.
  • the command part of the first registration request message within a period of time can include the value " 0x01”
  • the terminal device ID part may include the MAC address of the terminal device 13
  • the message body part may include the audio and/or video codec types supported by the terminal device 13.
  • the supported audio codec types may include EVS, AMR, AMR-WB, G.711, the supported video codec types can include H.264, MPEG-2, MPEG-4, WMA-HD, VC-1;
  • the command part of the non-first registration request message within a period of time It can include a string with a value of "0x02", the terminal device ID part can include the MAC address of the terminal device 13, and the message body part can be empty;
  • the command part of the registration success message can include a string with a value of "0x10", the terminal
  • the device ID part may include the MAC address of the terminal device 13, and the message body part may be empty;
  • the command part of the registration failure message may include a character string with a value of "0x20”, and the terminal device ID part may include the MAC address of the terminal device 13.
  • the message body part can be empty.
  • control plane signaling involved in the registration process are not limited to the form shown in Table 1.
  • a user front-end device is connected to an analog phone through an RJ11 port, where the SLIC (Subscriber Line Interface Circuit) of the user front-end device determines whether the analog phone is online based on voltage and current.
  • the user front-end device 12 knows the connected terminal device 13 through the registration process, and records the terminal device 13 in the online state, and the audio and/or audio and/or audio supported by the terminal device 13 in the online state. Video codec type. In this way, when the user front-end device 12 receives a call from the network side 11 as the called party, it can send the call to the terminal device 13 recorded as online.
  • the terminal device 13 that receives the registration success message can display its online status, so that the user can send a call setup message to the user's front-end device 12 through the terminal device 13, so that the user's front-end device 12
  • the network side 11 initiates a calling.
  • FIG. 6 shows a schematic flow chart of the calling process 600 between the user front-end device 12 and the terminal device 13. It should be noted that although in the embodiment of the present application, the steps of the method are presented in a specific order, they can The order of the steps is changed in different embodiments, and in some embodiments, one or more steps shown in order in this specification can be performed at the same time.
  • the calling process 600 includes:
  • the terminal device 13 sends a call establishment message to the user front-end device 12, and the call establishment message may instruct the user front-end device 12 to initiate a call to the network side 11.
  • the call setup message may include the call type (voice call or video call) and the identity of the called party.
  • the identity of the called party may include, but is not limited to, IMSI (International Mobile Subscriber Identity, International Mobile Subscriber Identity). User Identity), TMSI (Temporary Mobile Subscriber Identity, Temporary Mobile Subscriber Identity), MSISDN (Mobile Subscriber International ISDN/PSTN Number), IMEI (International Mobile Equipment Identity), MSIN (Mobile Subscriber Identification Number), mobile user Identification number) etc.;
  • the call establishment message may also include the address of the terminal device 13 used to receive and/or send the media data packet, for example, the IP address, the port number related to the transmission protocol of the media data packet, etc.;
  • the call setup message may also include video resolution, for example, general definition video (for example, but not limited to, 640x480 resolution), standard definition video (for example, but not limited to, 960x720 resolution) And high-definition video (for example, but not limited to, 1440x1080 resolution), etc.;
  • video resolution for example, general definition video (for example, but not limited to, 640x480 resolution), standard definition video (for example, but not limited to, 960x720 resolution) And high-definition video (for example, but not limited to, 1440x1080 resolution), etc.;
  • the call setup message may also include the type of audio and/or video codec supported by the terminal device 13. Audio codec type, corresponding to the call type being video call, the call setup message may also include the video codec type supported by the terminal device 13, or the call setup message may also include the audio codec type and video codec type supported by the terminal device 13
  • the call establishment message may indicate that the call type is a voice call, and indicate that the audio codec type supported by the terminal device 13 is the EVS-NB codec;
  • the user front-end equipment 12 sends a call request message to the network side 11.
  • the call request message may include the call type, the identity of the called party, and the audio or video codec type supported by the terminal device 13;
  • the call request message may also include the video resolution
  • the user front-end equipment 12 sends a ring back tone message to the terminal device 13, where the ring-back tone message may indicate to the terminal device 13 that the user front-end equipment 12 is dialing;
  • the ring back tone message may include a ring back tone, and the terminal device 13 plays the ring back tone after receiving the ring back tone message;
  • the ringback tone message may include an instruction for the terminal device 13 to play the ringback tone, and the terminal device 13 will play the ringback tone stored by the terminal device 13 after receiving the ringback tone message;
  • S604 Perform media negotiation between the user front-end equipment 12 and the network side 11.
  • the user front-end equipment 12 may determine the final call type with the network side 11.
  • the final call type may be a call type selected by both the terminal equipment 13 and the called party, or a call selected by the terminal equipment 13 and the called party.
  • the call type with higher priority can be used as the final call type according to the pre-set priority of voice call and video call;
  • the user front-end equipment 12 can also determine the final audio or video codec type with the network side 11.
  • the final audio or video codec type can be an audio or video codec type supported by both the terminal equipment 13 and the called party. If the terminal equipment There are multiple audio or video codec types supported by both 13 and the called party. You can determine an audio or video codec type as the final audio or video codec according to the pre-set priority of the audio or video codec type type;
  • the user front-end equipment 12 may also determine the final video resolution of the video call with the network side 11.
  • the final video resolution may be the video resolution selected by both the terminal equipment 13 and the called party, or In the case where the video resolutions selected by the terminal device 13 and the called party are different, the lower video resolution among the video resolutions selected by the terminal device 13 and the called party is used as the final video resolution, or it can be set according to the preset video resolution.
  • the priority of the video resolution select the video resolution with the highest priority as the final video resolution;
  • the user front-end equipment 12 sends a called answering instruction and a negotiation notification message to the terminal device 13, where the negotiation notification message includes the media negotiation result.
  • the media negotiation result may include the final call type and the final audio or video codec type.
  • the media negotiation result may also include the final video resolution.
  • the media negotiation result includes
  • the final call type can be a voice call, and the final audio codec type can be EVS-NB codec;
  • the negotiation notification message may also include the address of the user front-end device 12 for receiving and/or sending the media data packet, for example, the IP address, the port number related to the transmission protocol of the media data packet, etc.;
  • the terminal device 13 sends a media data packet to the user front-end device 12;
  • the terminal device 13 may send the media data packet based on the media negotiation result and the address of the user front-end device 12 for and/or sending the media data packet, for example, an audio data packet encoded by EVS-NB;
  • the user front-end equipment 12 sends the media data packet from the terminal equipment 13 to the network side 11.
  • the user front-end device 12 when the user front-end device 12 sends a media data packet to the network side 11, it does not carry the ID of the terminal device 13;
  • the network side 11 sends a media data packet from the called party to the user front-end equipment 12, for example, an audio data packet encoded by EVS-NB;
  • the media data packet from the called party is for the user front-end equipment 12, not the terminal device 13, and for the user front-end equipment 12 means that the called party carries the user front-end equipment 12 when sending the media data packet.
  • IMSI International Mobile Subscriber Identity, International Mobile Subscriber Identity
  • TMSI Temporary Mobile Subscriber Identity, Temporary Mobile Subscriber Identity
  • MSISDN Mobile Subscriber International ISDN/PSTN Number
  • IMEI International Mobile Equipment Identity, mobile equipment international identification
  • MSIN Mobile Subscriber Identification Number, mobile subscriber identification number
  • the user front-end equipment 12 sends a media data packet from the called party to the terminal equipment 13;
  • the user front-end equipment 12 may send the media data packet based on the address of the terminal device 13 for receiving and/or sending the media data packet;
  • the terminal device 13 sends a call end message to the user front-end device 12, and the call end message indicates the end of the call.
  • the network side 11 sends a call end message to the user front-end equipment 12;
  • the user front-end equipment 12 sends a call end message to the network side 11.
  • the user front-end device 12 sends a call end message to the terminal device 13.
  • Table 2 shows an example of the control plane signaling between the user front-end equipment 12 and the terminal equipment 13 involved in the calling process.
  • the command part of the call setup message may include a value of "0x03" Character string
  • the terminal device ID part may include the MAC address of the terminal device 13
  • the message body part may indicate that the call type selected by the terminal device 13 is a voice call, and the IP address of the terminal device 13 for receiving and/or sending media data packets Port number
  • the command part of the ringback tone message can include a string of "0x11”
  • the terminal device ID part can include the MAC address of the terminal device 13, the message body part can be empty
  • the command part of the negotiation notification message can include
  • the value is a string of "0x12”
  • the terminal device ID part can include the MAC address of the terminal device 13
  • the message body part can indicate that the final call type is voice call
  • the final audio codec type is EVS-NB
  • the user front-end device 12 The IP address and port number used to
  • control plane signaling involved in the calling process are not limited to the form shown in Table 2.
  • the user front-end device 12 may first determine the registration status of the terminal device 13. If the terminal device 13 fails to register, Then the user front-end device 12 will not send a call request message to the network side 11, and the calling process ends; if the terminal device 13 is successfully registered and recorded as online, then the user front-end device 12 sends a call request message to the network side 11, and Perform the steps in the above embodiment.
  • the terminal device 13 that is successfully registered and displayed online can send a call setup message to the user front-end device 12 at any time, so that the user front-end device 12 initiates a call to the network side, and during the call, the terminal device 13 can Move freely within the wireless network coverage.
  • the SLIC chip of the user's front-end equipment judges the off-hook and on-hook of the analog phone by voltage and current, and judges the dialing by the signal on the analog line.
  • the SLIC chip provides dial tone, ringback tone, etc. for the analog phone.
  • analog phone lines and analog phones only support narrowband voice, and media negotiation generally can only be negotiated as AMR-NB or EVS-NB.
  • the user front-end device 12 and the terminal device 13 complete actions such as dialing and hanging up based on messages sent through the wireless connection.
  • the call establishment message sent by the terminal device 13 indicates the call type
  • the user front-end device 13 12 can negotiate media with the network side according to the audio and/or video codec types supported by the terminal device 13, and the terminal device 13 can support high-definition voice codecs such as EVS-WB, EVS-SWB, EVS-FB, etc., and act as a terminal
  • the device 13 also supports video calls, it can also negotiate video communication, and supports video formats such as general definition, standard definition, and high definition.
  • FIG. 7 shows a schematic flowchart of the called process 700 between the user front-end device 12 and the terminal device 13. It should be noted that although in the embodiment of the present application, the steps of the method are presented in a specific order, The order of the steps is changed in different embodiments, and in some embodiments, one or more steps shown in order in this specification can be performed at the same time.
  • the called process 700 includes:
  • S701 The network side 11 sends a call to the user front-end equipment 12 to the user front-end equipment 12;
  • the user front-end equipment 12 refers to the call from the network side 11 including the identification of the user front-end equipment 12;
  • the user front-end device 12 determines one or more terminal devices 13 recorded as online;
  • the user front-end device 12 may determine that the terminal devices 13a, 13b, and 13n are recorded as online during the registration process;
  • the user front-end device 12 sends an incoming call message to one or more terminal devices 13 (for example, terminal devices 13a, 13b, and 13n) recorded as an online state, and the incoming call message may indicate that the terminal device 13 is ringing;
  • terminal devices 13 for example, terminal devices 13a, 13b, and 13n
  • the user front-end device 12 may simultaneously send incoming call messages to multiple terminal devices 13 recorded as online;
  • the user front-end device 12 may send an incoming call message to a plurality of terminal devices 13 recorded as online in a predefined sequence (for example, according to a preset priority of the terminal device 13), for example, first The terminal device 13 with the highest priority sends an incoming call message. If within a predetermined time, such as 15 seconds, the user front-end device 12 does not receive an answer message from the terminal device 13, the user front-end device 12 stops sending to the terminal device 13. Incoming call messages, and following the same rules, continue to send incoming call messages to the terminal device 13 with the second highest priority until the user front-end device 12 receives the answer message from the terminal device 13;
  • a terminal device 13 (for example, the terminal device 13a) that receives the incoming call message sends an answer message to the user front-end device 12;
  • the answering message may include the call type, and when the call type is a video call, the answering message may also include the video resolution of the video call;
  • the answer message may also include the address of the terminal device 13 for receiving and/or sending media data packets, for example, an IP address, a port number related to the transmission protocol, etc.;
  • the answering message may also include the audio supported by the terminal device 13.
  • the codec type, corresponding to the call type being a video call the answering message may also include the video codec type supported by the terminal device 13, or the answering message may also include the audio codec type and video codec type supported by the terminal device 13; for example, The answering message may indicate that the call type is a voice call, and the audio codec type supported by the terminal device 13 is the EVS-WB codec;
  • the user front-end device 12 is the terminal device 13 (for example, the terminal device 13a) described in S704, and media negotiation is performed with the network side 11;
  • the user front-end equipment 12 may determine the final call type with the network side 11.
  • the final call type may be a call type selected by both the terminal equipment 13 and the called party, or a call selected by the terminal equipment 13 and the called party.
  • the call type with higher priority can be used as the final call type according to the pre-set priority of voice call and video call;
  • the user front-end equipment 12 can also determine the final audio or video codec type with the network side 11.
  • the final audio or video codec type can be an audio or video codec type supported by both the terminal equipment 13 and the called party. If the terminal equipment There are multiple audio or video codec types supported by both 13 and the called party. You can determine an audio or video codec type as the final audio or video codec according to the pre-set priority of the audio or video codec type type;
  • the user front-end equipment 12 may also determine the final video resolution of the video call with the network side 11.
  • the final video resolution may be the video resolution selected by both the terminal equipment 13 and the called party, or In the case where the video resolutions selected by the terminal device 13 and the called party are different, the lower video resolution among the video resolutions selected by the terminal device 13 and the called party is used as the final video resolution, or it can be set according to the preset video resolution.
  • the priority of the video resolution select the video resolution with the highest priority as the final video resolution;
  • the user front-end device 12 stops sending the incoming call message to other terminal devices 13 (for example, the terminal devices 13b and 13n).
  • the user front-end equipment 12 sends a negotiation notification message to the terminal device 13 (for example, the terminal device 13a) described in S704, where the negotiation notification message includes the media negotiation result;
  • the media negotiation result may include the final call type and the final audio or video codec type.
  • the media negotiation result may also include the final video resolution.
  • the media negotiation result includes
  • the final call type can be a voice call, and the final audio codec type can be EVS-WB codec;
  • the negotiation notification message may also include the address of the user front-end device 12 for receiving and/or sending the media data packet, for example, the IP address, the port number related to the transmission protocol of the media data packet, etc.;
  • the terminal device 13 (for example, the terminal device 13a) described in S704 sends a media data packet to the user front-end device 12;
  • the terminal device 13 may send the media data packet based on the media negotiation result and the address of the user front-end device 12 for and/or sending the media data packet, for example, an audio data packet encoded by EVS-WB;
  • the user front-end device 12 sends the media data packet from the terminal device 13 (for example, the terminal device 13a) described in S704 to the network side 11;
  • the user front-end device 12 when the user front-end device 12 sends a media data packet to the network side 11, it does not carry the ID of the terminal device 13;
  • the network side 11 sends a media data packet from the called party to the user front-end equipment 12, for example, an audio data packet encoded by EVS-WB;
  • the media data packet from the called party is for the user's front-end device 12, not for the terminal device 13; S711, use
  • the user front-end device 12 sends the media data packet from the called party to the terminal device 13 (for example, the terminal device 13a) described in S704;
  • the user front-end equipment 12 may send the media data packet based on the address of the terminal device 13 for receiving and/or sending the media data packet;
  • the terminal device 13 (for example, the terminal device 13a) described in S704 sends a call end message to the user front-end device 12, and the call end message indicates the end of the call;
  • the network side 11 sends a call end message to the user front-end equipment 12;
  • the user front-end device 12 sends a call end message to the terminal device 13 described in S704.
  • Table 3 shows an example of the control plane signaling between the user's front-end device 12 and the terminal device 13 involved in the called process.
  • the command part of the incoming call message can include characters with a value of "0x13"
  • the terminal device ID part can include the MAC address of the terminal device 13, for example, the MAC address of the terminal device 13a, 13b, or 13n.
  • the message body part can be empty; the command part of the answer message can include a string with a value of "0x03"
  • the terminal device ID part may include the MAC address of the terminal device 13, for example, the MAC address of the terminal device 13a, and the message body part may indicate that the call type selected by the terminal device 13a is a voice call, and the terminal device 13a is used to receive and/or The IP address and port number for sending the media data packet; for the call end message sent by the user front-end device 12, the command part may include a character string with a value of "0x14", and the terminal device ID part may include the MAC address of the terminal device 13, for example, The MAC address of the terminal device 13a, 13b or 13n, the message body part may be empty; the command part of the negotiation notification message may include a character string with a value of "0x12", and the terminal device ID part may include the MAC address of the terminal device 13, for example, The MAC address of the terminal device 13a, the message body part can indicate that the final
  • control plane signaling involved in the called process are not limited to the form shown in Table 3.
  • the SLIC chip in the user's front-end equipment uses the subscriber line signaling to indicate a new incoming call to the analog phone. After the user answers the call, the subscriber line signaling is used to notify the user's front-end equipment; the analog phone line and the analog phone only support narrowband voice.
  • Media negotiation generally can only be negotiated as AMR-NB or EVS-NB; in addition, a user front-end device usually has only one RJ11 interface, so only one analog phone can be connected, and multiple terminals cannot be used to answer calls.
  • the user front-end device 2 and the terminal device 13 complete the call indication and answering actions based on the message sent through the wireless connection.
  • the answering message sent by the terminal device 13 indicates the call type, and the user front-end device 12 can According to the audio and/or video codec types supported by the terminal device 13, media negotiation is carried out with the network side, and the terminal device 13 can support high-definition voice codecs such as EVS-WB, EVS-SWB, EVS-FB, etc., and act as the terminal device 13 When it also supports video calls, it can also be negotiated into video communication, and supports general definition, standard definition, high definition and other video formats.
  • the user front-end equipment 12 can send calls from the network side to the user front-end equipment 12 through a wireless connection to one or more terminal devices 13 recorded as online during the registration process, and the user The most convenient terminal device 13 can be selected for answering, and when answering, it can move freely within the coverage of the wireless communication network.
  • the user if the user is using, for example, the terminal device 13a to make a call, and wants to switch to, for example, the terminal device 13n to make a call, then the user can initiate a switch to the user front-end device 12 through the terminal device 13a process.
  • FIG. 8 shows a schematic flow chart of the switching process 800 between the user front-end equipment 12 and the terminal equipment 13.
  • the order of the steps is changed in different embodiments, and in some embodiments, one or more steps shown in order in this specification can be executed at the same time.
  • the handover process 800 includes:
  • the terminal device 13 (for example, the terminal device 13a) sends a call switching message to the user front-end device 12, where the call switching message is used to instruct the user front-end device 12 to perform call switching;
  • the user front-end device 12 determines whether there are one or more other terminal devices 13 recorded as online in addition to the terminal device 13a, if not, execute step S803, if yes, execute steps S804-S815;
  • the user front-end equipment 12 sends a handover failure message to the terminal device 13a, where the handover failure message is used to indicate to the terminal device 13a that the call handover fails;
  • the user front-end device 12 sends an incoming call message to the one or more other terminal devices 13 (for example, terminal devices 13b and 13n);
  • the user front-end device 12 can send incoming call messages to the multiple other terminal devices 13 at the same time;
  • the user front-end device 12 may send incoming call messages to the multiple other terminal devices 13 in a predefined sequence (for example, according to the preset priority of the terminal device 13).
  • a predefined sequence for example, according to the preset priority of the terminal device 13.
  • a terminal device 13 (for example, a terminal device 13n) that receives an incoming call message sends an answer message to the user front-end device 12.
  • a terminal device 13n that receives an incoming call message sends an answer message to the user front-end device 12.
  • the answer message may indicate that the call type is a video call, the video codec type supported by the terminal device 13 is H.264 codec, and the video resolution is high-definition resolution;
  • the user front-end device 12 is the terminal device 13 (for example, the terminal device 13n) described in S805, and media negotiation is carried out with the network side 11.
  • the terminal device 13 for example, the terminal device 13n
  • media negotiation is carried out with the network side 11.
  • the user front-end device 12 stops sending the incoming call message to other terminal devices 13 (for example, the terminal device 13b);
  • the user front-end device 12 sends a negotiation notification message to the terminal device 13 (for example, the terminal device 13n) described in S805.
  • the terminal device 13 for example, the terminal device 13n
  • S808 The user front-end device 12 sends a negotiation notification message to the terminal device 13 (for example, the terminal device 13n) described in S805.
  • the terminal device 13 (for example, the terminal device 13n) described in S805 sends a media data packet to the user front-end device 12;
  • the terminal device 13 may send the media data packet based on the media negotiation result and the address of the user front-end device 12 for and/or sending the media data packet, for example, a video data packet encoded by H.264;
  • the user front-end device 12 sends the media data packet from the terminal device 13 (for example, the terminal device 13n) described in S805 to the network side 11;
  • the user front-end device 12 when the user front-end device 12 sends a media data packet to the network side 11, it does not carry the ID of the terminal device 13;
  • the network side 11 sends a media data packet from the called party to the user front-end device 12, for example, a video data packet encoded by H.264 and a video data packet encoded by H.264;
  • the media data packet from the called party is for the user's front-end equipment 12, not for the terminal device 13.
  • the user's front-end equipment 12 sends to the terminal device 13 (for example, the terminal device 13n) described in S805 from the called party.
  • the user front-end equipment 12 may send media data packets based on the address of the terminal device 13 for receiving and/or sending media data packets;
  • the terminal device 13 (for example, the terminal device 13n) described in S805 sends a call end message to the user front-end device 12, and the call end message indicates the end of the call;
  • the network side 11 sends a call end message to the user front-end equipment 12;
  • the user front-end device 12 sends a call end message to the terminal device 13 described in S805.
  • Table 4 shows an example of the control plane signaling between the user front-end equipment 12 and the terminal equipment 13 involved in the handover process.
  • the command part of the call handover message can include characters with a value of "0x06"
  • the terminal device ID part may include the MAC address of the terminal device 13, for example, the MAC address of the terminal device 13a, and the message body part may be empty; the command part of the incoming call message may include a string with a value of "0x13", the terminal device ID
  • the part may include the MAC address of the terminal device 13, for example, the MAC address of the terminal device 13b or 13n, the message body part may be empty; the command part of the answer message may include a character string with a value of "0x03", and the terminal device ID part may include The MAC address of the terminal device 13, for example, the MAC address of the terminal device 13n.
  • the message body part may indicate that the call type selected by the terminal device 13n is a video call, the video resolution is high-definition resolution, and the terminal device 13n is used for receiving and/ Or the IP address and port number for sending the media data packet;
  • the command part of the negotiation notification message may include a character string with a value of "0x12”
  • the terminal device ID part may include the MAC address of the terminal device 13, for example, the MAC address of the terminal device 13n
  • the message body part can indicate that the final call type is a video call, the final video resolution is high-definition resolution, the final video codec type is H.264, and the IP of the user front-end device 12 for receiving and/or sending media data packets Address and port number;
  • the command part may include a character string with a value of "0x14”
  • the terminal device ID part may include the MAC address of the terminal device 13, for example, the terminal device 13a or 13n MAC address, the message body part can be empty;
  • control plane signaling involved in the handover process are not limited to the form shown in Table 4.
  • a user front-end device 12 usually has only one RJ11 interface, so only one analog phone can be connected, and multiple terminal devices cannot be used to answer calls, and it is also impossible to switch between multiple terminal devices at will.
  • the user when multiple terminal devices 13 are registered online, the user can switch between the multiple terminal devices 13 at will during the call, and the terminal device 13 can be switched while changing the call type. .
  • FIG. 9 shows a block diagram of an electronic device 900 according to an embodiment of the present application.
  • the electronic device 900 may be a user front-end device 12 or a terminal device 13.
  • the electronic device 900 may include one or more processors 901.
  • the electronic device 900 may also include a memory 902 and a communication interface 903 coupled to the processor 901. Alternatively, the memory 902 may be integrated in the processor 901.
  • the processor 901 may include one or more single-core or multi-core processors.
  • the processor 902 may include any combination of a general-purpose processor and a special-purpose processor (for example, a graphics processor, an application processor, a baseband processor, etc.).
  • the processor 901 may be configured to execute one or more embodiments according to the various embodiments shown in FIGS. 5-8.
  • the memory 902 may be used to load and store data and/or instructions for the electronic device 900, for example.
  • the memory 902 may include any suitable volatile memory, such as a suitable dynamic random access memory (DRAM).
  • DRAM dynamic random access memory
  • the memory 902 may include one or more tangible, non-transitory computer-readable media for storing data and/or instructions.
  • the memory 902 may include, but is not limited to, a non-transitory tangible arrangement of objects manufactured or formed by machines or equipment, including storage media, such as hard disks, any other types of disks, including floppy disks, optical disks, compact disk read-only memory (CD-ROM), compact disk rewritable (CD-RW) and magneto-optical disk; semiconductor devices such as read only memory (ROM), such as dynamic random access memory (DRAM) and static random access memory (SRAM) Random access memory (RAM), erasable programmable read-only memory (EPROM), flash memory, electrically erasable programmable read-only memory (EEPROM); phase change memory (PCM); magnetic or optical card; or Any other type of medium suitable for storing electronic instructions.
  • storage media such as hard disks, any other types of disks, including floppy disks, optical disks, compact disk read-only memory (CD-ROM), compact disk rewritable (CD-RW) and magneto-optical disk
  • semiconductor devices such as
  • the memory 902 may contain instructions or contain design data, such as a hardware description language (HDL), which defines the structures, circuits, devices, processors, and/or system features described herein. These embodiments are also called program products.
  • HDL hardware description language
  • the memory 902 may include storage resources that are physically part of the electronic device 900, or it may be accessed by the electronic device 900, but not necessarily a part of the electronic device 900.
  • the storage 902 can be accessed through the network via the communication interface 903.
  • the memory 902 may specifically include temporary or permanent copies of instructions.
  • the instructions may include instructions that, when executed by the at least one processor 902, cause the electronic device 900 to implement the method as described with reference to FIGS. 5-8.
  • the communication interface 903 may include any transceiver module to provide a signal transmission interface for the electronic device 900.
  • the various embodiments of the mechanisms disclosed herein can be implemented in hardware, software, firmware, or a combination of these implementation methods.
  • the embodiments of the present application can be implemented as a computer program or program code executed on a programmable system including at least one processor and a storage system (including volatile and non-volatile memory and/or storage elements) , At least one input device and at least one output device.
  • Program code can be applied to input instructions to perform the functions described in this article and generate output information.
  • the output information can be applied to one or more output devices in a known manner.
  • a processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • the program code can be implemented in a high-level programming language or an object-oriented programming language to communicate with the processing system.
  • assembly language or machine language can also be used to implement the program code.
  • the mechanisms described in this article are not limited to the scope of any particular programming language. In either case, the language can be a compiled language or an interpreted language.
  • IP cores can be stored on a tangible machine-readable medium and provided to multiple customers or production facilities to be loaded into the manufacturing machine that actually manufactures the logic or processor.
  • Such machine-readable storage media may include, but are not limited to, non-transitory tangible arrangements of objects manufactured or formed by machines or equipment, including storage media, such as hard disks, any other types of disks, including floppy disks, optical disks, compact disks, etc.
  • CD-ROM Compact disk rewritable
  • CD-RW compact disk rewritable
  • magneto-optical disk semiconductor devices such as read only memory (ROM), such as dynamic random access memory (DRAM) and static random access Random access memory (RAM) such as memory (SRAM), erasable programmable read-only memory (EPROM), flash memory, electrically erasable programmable read-only memory (EEPROM); phase change memory (PCM); magnetic card Or optical card; or any other type of medium suitable for storing electronic instructions.
  • ROM read only memory
  • DRAM dynamic random access memory
  • RAM static random access Random access memory
  • SRAM erasable programmable read-only memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • PCM phase change memory
  • magnetic card Or optical card or any other type of medium suitable for storing electronic instructions.
  • the embodiments of the present application also include non-transitory tangible machine-readable media containing instructions or design data, such as hardware description language (HDL), which defines the structures, circuits, devices, and processes described herein. And/or system characteristics.
  • HDL hardware description language

Abstract

本申请涉及一种用于用户前端设备的通信方法，包括：用户前端设备通过无线通信模式，在第一终端设备上实现用户前端设备与网络侧之间的呼叫，其中，呼叫包括被叫过程和主叫过程，在被叫过程中，在第一终端设备上实现用户前端设备与网络侧之间的呼叫包括：用户前端设备响应于接收到的来自网络侧的针对用户前端设备的呼叫，通过无线通信模式向第一终端设备发送呼叫；以及在主叫过程中，在第一终端设备上实现用户前端设备与网络侧之间的呼叫包括：用户前端设备响应于通过无线通信模式接收到的来自第一终端设备的呼叫建立消息，向网络侧发起呼叫。在本申请中，用户可以在用户前端设备与终端设备之间的无线通信网络的覆盖范围内随意移动。

Description

一种通信方法及系统
本申请要求于2020年04月23日提交中国专利局、申请号为202010327368.4、发明名称为“一种通信方法及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请的一个或多个实施例通常涉及通信领域，具体涉及一种通信方法及系统。
背景技术
用户前端设备(Customer Premises Equipment，CPE)是一种插有SIM卡、可将3G/4G/5G蜂窝移动网络信号转换为WiFi信号，从而为终端提供WiFi网络的设备。CPE内置调制解调模块，既支持上网，又支持语音通话，有些CPE的调制解调模块还支持EVS(Enhanced Voice Service)高清编解码。
由于CPE不具备扬声器、麦克风等输入/输出模块，当前CPE的语音通话功能是通过RJ11接口以模拟线路连接模拟话机实现的，需要考虑布线的问题，并且模拟话机的不可移动性给用户带来的体验较差。另外，模拟线路只能传输窄带语音信号，模拟话机也只能处理窄带语音信号，因此即使CPE的调制解调模块支持EVS高清编解码，用户也不能体验到高清语音通话。
发明内容
本申请的一些实施方式提供了一种通信方法及系统。以下从多个方面介绍本申请，以下多个方面的实施方式和有益效果可互相参考。
本申请的第一方面提供了一种用于用户前端设备的通信方法，该方法可以包括：
所述用户前端设备通过无线通信模式，在第一终端设备上实现所述用户前端设备与网络侧之间的呼叫，其中，所述呼叫包括被叫过程和主叫过程，
在所述被叫过程中，在所述第一终端设备上实现所述用户前端设备与网络侧之间的呼叫包括：所述用户前端设备响应于接收到的来自所述网络侧的针对所述用户前端设备的所述呼叫，通过所述无线通信模式向所述第一终端设备发送所述呼叫；以及
在所述主叫过程中，在所述第一终端设备上实现所述用户前端设备与网络侧之间的呼叫包括：所述用户前端设备响应于通过所述无线通信模式接收到的来自所述第一终端设备的呼叫建立消息，向所述网络侧发起呼叫。
根据本申请的实施例，由于用户前端设备通过无线通信模式在终端设备上实现用户前端设备与网络侧之间的呼叫，用户可以在用户前端设备与终端设备之间的无线通信网络的覆盖范围内随意移动，由此用户体验得以优化。
在一些实施例中，该方法还包括：
所述用户前端设备在所述第一终端设备上实现所述呼叫之前，通过所述无线通信模式：
接收来自所述第一终端设备的注册请求消息；
在确定所述第一终端设备符合预定条件的情况下，记录所述第一终端设备处于在线状态，并向所述第一终端设备发送注册成功消息。
根据本申请的实施例，用户前端设备通过注册过程可以知晓下挂的终端设备，如此，在用户前端设 备作为被叫方接收到来自网络侧的呼叫时，可以将呼叫发送给记录为在线状态的终端设备。另外，收到注册成功消息的终端设备可以显示自己的在线状态，使得用户可以通过该终端设备，向用户前端设备发送呼叫建立消息，以使用户前端设备向网络侧11发起主叫。
在一些实施例中，该方法还包括：
所述用户前端设备确定最新一次接收所述第一终端设备的所述注册请求消息的时间与当前时间之间的时间间隔；
在所述用户前端设备确定所述时间间隔大于或等于预定时间间隔的情况下，记录所述第一终端设备处于离线状态。
根据本申请的实施例，通过记录终端设备处于离线状态，在用户前端设备接收到来自网络侧针对用户前端设备的呼叫时，可以不将呼叫发送给记录为离线状态的终端设备。
在一些实施例中，在所述被叫过程中，所述用户前端设备向所述第一终端设备发送所述呼叫，包括：
向所述第一终端设备发送来电消息；
接收来自所述第一终端设备的接听消息，所述接听消息指示所述呼叫的类型为语音呼叫或视频呼叫；
根据所述第一终端设备支持的音频或视频编解码类型，以及所述呼叫的所述类型，与所述网络侧进行媒体协商；
向所述第一终端设备发送协商通知消息，所述协商通知消息包括所述媒体协商的结果；
向所述第一终端设备发送来自所述网络侧的媒体数据包，和/或向所述网络侧发送来自所述第一终端设备的所述媒体数据包。
根据本申请的实施例，用户前端设备和终端设备之间基于通过无线连接发送的消息来完成来电指示、接听动作，终端设备发送的接听消息指示呼叫类型，用户前端设备可以根据终端设备的支持的音频和/或视频编解码类型与网络侧进行媒体协商，而终端设备可以支持高清语音EVS-WB、EVS-SWB、EVS-FB等编解码，并且当终端设备还支持视频呼叫时，还可以协商成视频通信，并支持普清、标清、高清等视频格式。
在一些实施例中，接收的来自所述第一终端设备的所述注册请求消息或者所述接听消息包括所述第一终端设备支持的所述音频和/或视频编解码类型。
在一些实施例中，所述接听消息还包括所述第一终端设备的用于接收和/或发送所述媒体数据包的地址；
所述协商通知消息还包括所述用户前端设备的用于接收和/或发送所述媒体数据包的地址。
在一些实施例中，在所述被叫过程中，还包括，所述用户前端设备通过无线通信模式：
向被记录为在线状态的第二终端设备发送所述来电消息；
响应于接收来自所述第一终端设备的所述接听消息，向所述第二终端设备发送呼叫结束消息。
在一些实施例中，在所述主叫过程中，所述呼叫建立消息指示所述呼叫的类型为语音呼叫或视频呼叫以及被叫用户的标识，并且所述用户前端设备向所述网络侧发起呼叫，包括：
向所述网络侧发送呼叫请求消息，所述呼叫请求消息包括所述呼叫的所述类型，所述第一终端设备支持的音频或视频编解码类型以及所述被叫用户的标识；
向所述第一终端设备发送回铃音消息，所述回铃音消息指示所述第一终端设备播放回铃音；
根据所述第一终端设备支持的所述音频或视频编解码类型，以及所述呼叫的所述类型，与所述网络侧进行媒体协商；
向所述第一终端设备发送协商通知消息以及被叫接听指示，所述协商通知消息包括所述媒体协商的 结果；
向所述第一终端设备发送来自所述网络侧的媒体数据包，和/或向所述网络侧发送来自所述第一终端设备的所述媒体数据包。
根据本申请的实施例，终端设备发送的呼叫建立消息指示呼叫类型，用户前端设备可以根据终端设备的支持的音频和/或视频编解码类型与网络侧进行媒体协商，而终端设备可以支持高清语音EVS-WB、EVS-SWB、EVS-FB等编解码，并且当终端设备还支持视频呼叫时，还可以协商成视频通信，并支持普清、标清、高清等视频格式。
在一些实施例中，所述注册请求消息或者所述呼叫建立消息包括所述第一终端设备支持的所述音频和/或视频编解码类型。
在一些实施例中，接收的来自所述第一终端设备的所述呼叫建立消息还包括所述第一终端设备的用于接收和/或发送所述媒体数据包的地址；
所述协商通知消息还包括所述用户前端设备的用于接收和/或发送所述媒体数据包的地址。
在一些实施例中，在所述被叫过程中，所述用户前端设备向所述第一终端设备发送所述呼叫，还包括，通过无线通信模式：
接收来自所述第一终端设备的呼叫切换消息；
确定除了所述第一终端设备之外，是否还存在被记录为在线状态的终端设备；
在确定除了所述第一终端设备之外，不存在被记录为所述在线状态的所述终端设备的情况下，向所述第一终端设备发送切换失败消息；
在确定除了所述第一终端设备之外，存在第三终端设备被记录为所述在线状态的情况下，向所述第三终端设备发送所述呼叫，并且向所述第一终端设备发送呼叫结束消息；
其中，向所述第三终端设备发送所述呼叫，包括：
向所述第三终端设备发送来电消息；
接收来自所述第三终端设备的接听消息，所述接听消息指示所述呼叫的类型为语音呼叫或视频呼叫；
根据所述第三终端设备支持的音频或视频编解码类型，以及所述呼叫的所述类型，与所述网络侧进行媒体协商；
向所述第三终端设备发送协商通知消息，所述协商通知消息包括所述媒体协商的结果；
向所述第三终端设备发送来自所述网络侧的媒体数据包，和/或向所述网络侧发送给来自所述第三终端设备的所述媒体数据包。
根据本申请的实施例，当有多个终端设备注册在线时，在呼叫过程中，用户可以在多个终端设备之间随意切换，并且切换终端设备的同时还可以改变呼叫类型。
在一些实施例中，接收的来自所述第三终端设备的所述注册请求消息或者所述接听消息包括所述第三终端设备支持的所述音频和/或视频编解码类型。
在一些实施例中，接收的来自所述第三终端设备的所述接听消息还包括所述第三终端设备的用于接收和/或发送所述媒体数据包的地址。
在一些实施例中，在所述主叫过程中，所述用户前端设备向所述网络侧发起呼叫，还包括，通过无线通信模式：
接收来自所述第一终端设备的呼叫切换消息；
确定除了所述第一终端设备之外，是否还存在被记录为所述在线状态的终端设备；
在确定除了所述第一终端设备之外，不存在被记录为所述在线状态的所述终端设备的情况下，向所 述第一终端设备发送切换失败消息；
在确定除了所述第一终端设备之外，存在第三终端设备被记录为所述在线状态的情况下，向所述第三终端设备发送所述呼叫，并且向所述第一终端设备发送呼叫结束消息；
其中，所述向所述第三终端设备发送所述呼叫，包括：
向所述第三终端设备发送来电消息；
接收来自所述第三终端设备的接听消息，所述接听消息指示所述呼叫的类型为语音呼叫或视频呼叫；
根据所述第三终端设备支持的音频或视频编解码类型，以及所述呼叫的所述类型，与所述网络侧进行媒体协商；
向所述第三终端设备发送协商通知消息，所述协商通知消息包括所述媒体协商的结果；
向所述第三终端设备发送来自所述网络侧的媒体数据包，和/或向所述网络侧发送给来自所述第三终端设备的所述媒体数据包。
根据本申请的实施例，当有多个终端设备注册在线时，在呼叫过程中，用户可以在多个终端设备之间随意切换，并且切换终端设备的同时还可以改变呼叫类型。
在一些实施例中，接收的来自所述第三终端设备的所述注册请求消息或者所述接听消息包括所述第三终端设备支持的所述音频或视频编解码类型。
在一些实施例中，接收的来自所述第三终端设备的所述接听消息还包括所述第三终端设备的用于接收和/或发送所述媒体数据包的地址。
在一些实施例中，所述无线通信模式为WiFi通信模式。
在一些实施例中，所述用户前端设备的标识是所述用户前端设备的用户标识，或者所述用户前端设备的设备标识。
本申请的第二方面提供一种用于终端设备的通信方法，该方法包括：
通过无线通信模式与用户前端设备建立连接，并为所述用户前端设备实现所述用户前端设备与网络侧之间的呼叫；
其中，所述呼叫包括主叫过程和被叫过程，
在被叫过程中，所述实现所述用户前端设备与网络侧之间的呼叫包括：所述终端设备通过无线通信模式接收来自所述用户前端设备的所述网络侧针对所述用户前端设备的呼叫；以及
在主叫过程中，所述实现所述用户前端设备与网络侧之间的呼叫包括：所述终端设备通过无线通信模式向所述用户前端设备发送呼叫建立消息，使得所述用户前端设备向所述网络侧发起呼叫。
根据本申请的实施例，由于用户前端设备通过无线通信模式在终端设备上实现用户前端设备与网络侧之间的呼叫，用户可以在用户前端设备与终端设备之间的无线通信网络的覆盖范围内随意移动，由此用户体验得以优化。
在一些实施例中，该方法还包括，所述终端设备在为所述用户前端设备实现所述呼叫之前，通过所述无线通信模式：
向所述用户前端设备发送注册请求消息；
接收来自所述用户前端设备的注册成功消息。
根据本申请的实施例，用户前端设备通过注册过程可以知晓下挂的终端设备，如此，在用户前端设备作为被叫方接收到来自网络侧的呼叫时，可以将呼叫发送给记录为在线状态的终端设备。另外，收到注册成功消息的终端设备可以显示自己的在线状态，使得用户可以通过该终端设备，向用户前端设备发送呼叫建立消息，以使用户前端设备向网络侧11发起主叫。
在一些实施例中，在所述被叫过程中，所述终端设备接收来自用户前端设备的所述网络侧针对所述用户前端设备的呼叫，包括：
接收来自所述用户前端设备的来电消息；
向所述用户前端设备发送接听消息，所述接听消息指示所述呼叫的类型为语音呼叫或视频呼叫；
接收来自所述用户前端设备的协商结果消息，所述协商结果消息包括所述用户前端设备与所述网络侧基于所述终端设备支持的音频或视频编解码类型以及所述呼叫的所述类型进行的媒体协商的结果；
接收来自所述用户前端设备的媒体数据包，和/或向所述用户前端设备发送媒体
数据包。
根据本申请的实施例，用户前端设备和终端设备之间基于通过无线连接发送的消息来完成来电指示、接听动作，终端设备发送的接听消息指示呼叫类型，用户前端设备可以根据终端设备的支持的音频和/或视频编解码类型与网络侧进行媒体协商，而终端设备可以支持高清语音EVS-WB、EVS-SWB、EVS-FB等编解码，并且当终端设备还支持视频呼叫时，还可以协商成视频通信，并支持普清、标清、高清等视频格式。
在一些实施例中，所述注册请求消息或者所述接听消息包括所述终端设备支持的所述音频和/或视频编解码类型。
在一些实施例中，所述接听消息包括所述终端设备的用于接收和/或发送所述媒体数据包的地址，
所述协商结果消息包括所述用户前端设备的用于接收和/或发送所述媒体数据包的地址。
在一些实施例中，在所述主叫过程中，所述呼叫建立消息指示所述呼叫的类型为语音呼叫或视频呼叫以及被叫用户的标识，并且还包括：
接收来自所述用户前端设备的回铃音消息，并响应于所述回铃音消息，播放回铃音；
接收来自所述用户前端设备的协商结果消息，所述协商结果消息包括所述用户前端设备与所述网络侧基于所述终端设备支持的音频或视频编解码类型以及所述呼叫的所述类型进行的媒体协商的结果；
向所述用户前端设备发送媒体数据包，和/或接收来自所述用户前端设备的所述媒体数据包。
根据本申请的实施例，终端设备发送的呼叫建立消息指示呼叫类型，用户前端设备可以根据终端设备的支持的音频和/或视频编解码类型与网络侧进行媒体协商，而终端设备可以支持高清语音EVS-WB、EVS-SWB、EVS-FB等编解码，并且当终端设备还支持视频呼叫时，还可以协商成视频通信，并支持普清、标清、高清等视频格式。
在一些实施例中，所述注册请求消息或者所述呼叫建立消息包括所述终端设备支持的音频和/或视频编解码类型。
在一些实施例中，所述呼叫建立消息包括所述终端设备的用于接收和/或发送所述媒体数据包的地址，
所述协商通知消息包括所述用户前端设备的用于接收和/或发送所述媒体数据包的地址。
在一些实施例中，在所述被叫过程中，所述终端设备接收来自用户前端设备的所述网络侧针对所述用户前端设备的呼叫，还包括：
向所述用户前端设备发送呼叫切换消息；
接收来自所述用户前端设备的切换失败消息，或者接收来自所述用户前端设备的呼叫结束消息。
根据本申请的实施例，当有多个终端设备注册在线时，在呼叫过程中，用户可以在多个终端设备之间随意切换，并且切换终端设备的同时还可以改变呼叫类型。
在一些实施例中，在所述主叫过程中，还包括：
所述终端设备向所述用户前端设备发送呼叫切换消息；
所述终端设备接收来自所述用户前端设备的切换失败消息，或者接收来自所述用户前端设备的呼叫结束消息。
根据本申请的实施例，当有多个终端设备注册在线时，在呼叫过程中，用户可以在多个终端设备之间随意切换，并且切换终端设备的同时还可以改变呼叫类型。
在一些实施例中，所述无线通信模式为WiFi通信模式。
本申请的第三方面提供一种机器可读介质，在所述介质上存储有指令，当所述指令在所述机器上运行时，使得所述机器执行以上所述任意一种通信方法。
本申请的第四方面提供一种系统，该系统包括：用户前端设备和终端设备，其中该用户前端设备用于执行以上所述与用户前端设备相关的通信方法，终端设备用于执行以上所述与终端设备相关的通信方法。
附图说明
图1示出了根据本申请实施例的通信系统10的结构示意图；
图2示出了根据本发明实施例的用户前端设备12和终端设备13的结构示意图；
图3示出了根据本发明实施例的用户前端设备12和终端设备13之间的控制面信令的结构和传输协议的示意图；
图4示出了根据本发明实施例的用户前端设备12和终端设备13之间的媒体面数据的传输协议的示意图；
图5示出了根据本申请实施例的注册过程500的流程示意图；
图6示出了根据本申请实施例的主叫过程600的流程示意图；
图7示出了根据本申请实施例的被叫过程700的流程示意图；
图8示出了根据本申请实施例切换过程800的流程示意图；
图9示出了根据本申请的实施例的电子设备900的结构示意图。
具体实施方式
除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。。
应当理解的是，虽然在这里可能使用了术语“第一”、“第二”等等来描述各个单元或是数据，但是这些单元或数据不应当受这些术语限制。使用这些术语仅仅是为了将一个特征与另一个特征进行区分。举例来说，在不背离示例性实施例的范围的情况下，第一特征可以被称为第二特征，并且类似地第二特征可以被称为第一特征。
图1示出了根据本发明实施例的通信系统10的一种结构示意图，如图所示，通信系统10包括网络侧11、用户前端设备12以及一个或多个终端设备13a-13n(在本申请中，统称为终端设备13)。网络侧11可以包括，但不限于，蜂窝移动通信网络的无线接入网、核心网以及公用数据网络。蜂窝移动通信网络可以包括，但不限于，第三代移动通信网络、第四代移动通信网络以及第五代移动通信网络。
用户前端设备12通过蜂窝移动通信网络的空中接口连接到网络侧11，并通过无线通信模式连接到终端设备13。无线通信模式可以是WiFi通信，即用户前端设备12将接收的蜂窝移动通信网络信号转换为 WiFi信号，使得终端设备13可以通过WiFi通信连接到用户前端设备12；无线通信模式也可以是蓝牙通信、ZigBee通信或者其他的无线通信模式。
根据本申请的另外一些实施例，用户前端设备12也可以通过有线通信模式与终端设备13连接，例如，但不限于，用户前端设备12通过LAN(Local Area Network)口及网线(例如，但不限于，双绞线、光缆、同轴电缆等)与终端设备13连接，并且基于局域网协议(例如，但不限于，IEEE 802.3、TCP/IP协议)与终端设备13通信。
根据本申请的另外一些实施例，用户前端设备12也可以既通过上述无线通信模式又通过有线通信模式与一个或多个终端设备13连接。
终端设备13可以包括，但不限于，便携式或移动设备、手机、平板电脑、电视、个人数字助理、膝上型设备、台式机、手持PC、服务器、网络设备、图形设备、视频游戏设备、机顶盒、蜂窝电话、便携式媒体播放器、手持设备、可穿戴设备(例如，显示眼镜或护目镜、头戴式显示器、手表、头戴设备、臂带、珠宝等)、虚拟现实和/或增强现实设备、物联网设备、工业控制设备、车载信息娱乐设备、流媒体客户端设备、电子书阅读设备、POS机、或者能够进行无线通信和/或有线通信的其他电子设备。
根据本申请的一些实施例，用户前端设备12可以与网络侧11建立呼叫连接，并可以通过无线通信模式和/或有线通信模式，在终端设备13上实现呼叫，其中，呼叫包括被叫过程和主叫过程。根据本申请的一些实施例，在被叫过程中，用户前端设备12可以接收到来自网络侧11的针对用户前端设备12的呼叫，并可以通过无线通信模式和/或有线通信模式，向终端设备13发送呼叫。根据本申请的一些实施例，在主叫过程中，用户前端设备12可以通过无线通信模式和/或有线通信模式接收来自终端设备13的呼叫建立消息，并向网络侧11发起呼叫。
图2示出了根据本申请实施例的用户前端设备12和终端设备13的一种结构示意图，如图2所示，用户前端设备12可以包括第一无线收发模块120a、第二无线收发模块120b以及第一呼叫控制模块125。其中，第一无线收发模块可以包括移动通信射频单元121、PS(Packet Switch，分组交换)协议栈122、TCP/IP(Transmission Control Protocol/Internet Protocol，传输控制协议/因特网协议)协议栈123以及IMS(IP Multimedia Subsystem，IP多媒体子系统)协议栈124。第二无线收发模块可以包括UDP/IP(User Datagram Protocol/Internet Protocol，用户数据报协议/因特网协议)协议栈126、WiFi协议栈127以及WiFi射频单元128。用户前端设备12的各个模块可以由专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门电路(Field Programmable Gate Array，FPGA)、电子电路、执行一个或多个软件或固件程序的(共享、专用或组)处理器和/或存储器、组合逻辑电路和/或提供所描述的功能的其他合适的组件构成。
需要说明的是，第一无线收发模块和第二无线收发模块的结构不限于图2中所示出的，它们可以包括任意合适数量、任意合适类型的协议栈，例如，在第二无线收发模块中，可以使用蓝牙协议栈替代WiFi协议栈127；另外，第一无线收发模块和第二无线收发模块也可以包括其他单元，例如，但不限于，基带处理单元。在用户前端设备12通过有线通信模式与终端设备13连接的情况下，用户前端设备12也可以包括有线收发模块。
第一无线收发模块可以实现用户前端设备12和网络侧11之间的无线通信。在第一无线收发模块中，移动通信射频单元121可以通过天馈接收和/或发送射频信号，其中，该射频信号用于蜂窝移动通信。PS协议栈122、TCP/IP协议栈123以及IMS协议栈124可以分别对要向网络侧11发送的数据进行PS协议、TCP/IP协议以及IMS协议的封装，也可以分别对来自网络侧11的数据进行PS协议、TCP/IP协议以及IMS协议的解封装。其中，IMS协议栈124对来自网络侧11的数据解封装后可以得到RTP(Real-time Transport  Protocol，实时传输协议)码流，或者可以对RTP码流进行IMS协议封装，RTP码流中可以包括媒体数据，例如，但不限于，经过EVS编码的音频数据等。
第二无线收发模块可以实现用户前端设备12和终端设备13之间的无线通信，在第二无线收发模块中，UDP/IP协议栈126、WiFi协议栈127可以分别对要向终端设备13发送的数据进行UDP/IP协议、WiFi协议的封装，也可以分别对来自终端设备13的数据进行UDP/IP协议、WiFi协议的解封装。WiFi射频单元128可以通过天馈接收和/或发送射频信号，其中，该射频信号用于WiFi通信。
第一呼叫控制模块125可以在主叫过程和被叫过程中，分别通过第一无线收发模块和第二无线收发模块，与网络侧11和终端端设备13交互用于控制呼叫的控制面信令和在呼叫过程中产生的媒体面数据(音频数据和/或视频数据)。根据本申请的一些实施例，第一呼叫控制模块125还可以在注册过程中，通过第二无线收发模块，与终端设备13交互用于控制注册的控制面信令，注册成功的终端设备13可以进行上述被叫过程和主叫过程。根据本申请的一些实施例，第一呼叫控制模块125还可以在呼叫切换过程中，通过第二无线收发模块，与网络侧11和不同的终端端设备13交互用于控制呼叫切换的控制面信令和在呼叫过程中产生的媒体面数据(音频数据和/或视频数据)。
如图2所示，终端设备13可以包括第三无线收发模块130、第二呼叫控制模块134、HiFi模块135、模数/数模转换模块136以及输入/输出模块137，第三无线收发模块可以进一步包括WiFi射频单元131、WiFi协议栈132以及UDP/IP协议栈133。终端设备13的各个模块可以由专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门电路(Field Programmable Gate Array，FPGA)、电子电路、执行一个或多个软件或固件程序的(共享、专用或组)处理器和/或存储器、组合逻辑电路和/或提供所描述的功能的其他合适的组件构成。
需要说明的是，第三无线收发模块的结构不限于图2中所示出的，其可以包括任意合适数量、任意合适类型的协议栈，例如，在第三无线收发模块中，可以使用蓝牙协议栈替代WiFi协议栈132；另外，第三无线收发模块也可以包括其他单元，例如，但不限于，基带处理单元。在终端设备13通过有线通信模式与用户前端设备12连接的情况下，终端设备13也可以包括有线收发模块。
第三无线收发模块可以实现终端设备13和用户前端设备12之间的无线通信，在第三无线收发模块中，WiFi射频单元131可以通过天馈接收和/或发送射频信号，其中，该射频信号用于WiFi通信。WiFi协议栈132、UDP/IP协议栈133可以分别对要向用户前端设备12发送的数据进行WiFi协议、UDP/IP协议的封装，也可以分别对来自用户前端设备12的数据进行WiFi协议、UDP/IP协议的解封装。
第二呼叫控制模块134可以在主叫过程和被叫过程中，通过第三无线收发模块，与用户前端设备12交互用于控制呼叫的控制面信令和在呼叫过程中产生的媒体面数据(音频数据和/或视频数据)。根据本申请的一些实施例，第二呼叫控制模块134还可以在注册过程中，通过第三无线收发模块，与用户前端设备12交互用于控制注册的控制面信令，注册成功的终端设备13可以进行上述被叫过程和主叫过程。
HiFi模块135可以对RTP码流中的媒体数据进行解码，得到PCM(Pulse Code Modulation，脉冲编码调制)码流，例如，HiFi模块135可以对RTP码流中经过EVS编码的音频数据进行EVS解码。
模数/数模转换模块136可以将来自输入/输出模块137的模拟信号转换为数字信号，也可以将来自HiFi模块135的数字信号转换为模拟信号。
输入/输出模块137可以接收音频输入、图像输入等，也可以输出音频和图像等，输入/输出模块137的示例可以包括，但不限于，扬声器、麦克风、显示器(例如，液晶显示器、触摸屏显示器等)等。
图3示出了图2中的第一呼叫控制模块125和第二呼叫控制模块134之间的控制面信令的结构和传输协议。如图3所示，第一呼叫控制模块125和第二呼叫控制模块134之间的控制面信令可以包括命令部分、 终端设备ID(Identity，标识)部分以及消息体部分。其中，命令部分用于指示信令的类型，其可以包括，但不限于，1个字节的十六进制字符串；终端设备ID部分用于指示终端设备13的标识(例如，但不限于，终端设备13的MAC(Media Access Control，媒体访问控制层)地址)，其可以包括，但不限于，6个字节的字符串；消息体部分用于指示信令的具体内容，例如，但不限于，呼叫类型(语音呼叫或视频呼叫)、编解码类型、接收和/或发送媒体数据包的地址(例如，但不限于，IP地址、与媒体传输协议相关的端口号等)等。需要说明的，控制面信令的结构不限于图3所示出的。
如图3所示，第一呼叫控制模块125和第二呼叫控制模块134之间的控制面信令的传输基于UDP/IP协议和WiFi协议，其中WiFi协议包括WiFi MAC协议和WiFi PHY(Physical，物理层)协议。需要说明的是，控制面信令的传输协议不限于图3所示出的。
图4示出了第一呼叫控制模块125和第二呼叫控制模块134之间的媒体面数据的传输协议，如图4所示，第一呼叫控制模块125和第二呼叫控制模块134之间的媒体面数据的传输基于RTP/RTCP(Real-time Transport Control Protocol，实时传输控制协议)协议、UDP/IP协议和WiFi协议，其中WiFi协议包括WiFi MAC协议和WiFi PHY协议。需要说明的是，媒体面数据的传输协议不限于图3所示出的。
为了在终端设备13上实现呼叫，用户前端设备12和终端设备13之间首先要进行注册过程，图5示出了用户前端设备12和终端设备13之间的注册过程500的流程示意图，需要说明的是，虽然在本申请的实施例中，以特定顺序呈现了方法的各个步骤，但是可以在不同的实施例中改变步骤的顺序，并且在一些实施例中，可以同时执行在本说明书中按顺序示出的一个或多个步骤。
如图5所示，注册方法500包括：
S501，用户前端设备12与终端设备13之间建立无线通信连接；
在一种示例中，用户前端设备12与终端设备13之间可以建立WiFi通信连接、蓝牙通信连接、ZigBee通信连接以及其他无线通信连接中的一种；
在另一种示例中，用户前端设备12与终端设备13之间也可以建立有线通信连接；
S502，终端设备13向用户前端设备12发送注册请求消息；
在一种示例中，注册请求消息可以包括终端设备13支持的音频和/或视频编解码类型，其中，终端设备13支持的音频编解码类型可以包括，但不限于EVS(Enhanced Voice Service，增强语音服务)、AMR(Adaptive multi-Rate，自适应多速率)、AMR-WB(Adaptive multi-Rate Wide Band，自适应多速率宽带)以及ITU-T G.711编解码等，终端设备13支持的视频编解码类型可以包括，但不限于H.264、MPEG-2、MPEG-4、WMA-HD以及VC-1编解码等；
在一种示例中，用户打开终端设备13上的智能终端App，使得终端设备13向用户前端设备12发送注册请求消息，其中该智能终端App可以包括第二呼叫控制模块134；
在另一种示例中，在用户前端设备12与终端设备13之间建立无线通信连接后，终端设备13自动向用户前端设备12发送注册请求消息；
S503，用户前端设备12确定终端设备13是否符合预定条件，若是，则执行S504和S505，若否，则执行S506和S507；
在一种示例中，预定条件可以包括，但不限于，以下中的一个或多个：终端设备13的标识在预设的白名单中，终端设备13具有特定的音频和/或视频编解码类型等；
S504，用户前端设备12记录终端设备13处于在线状态，如果用户前端设备12接收到来自网络侧11针对用户前端设备12的呼叫，则可以将呼叫发送给记录为在线状态的终端设备13；
在注册请求消息包括终端设备13支持的音频和/或视频编解码类型的情况下，用户前端设备12还可 以记录终端设备13的音频和/或视频编解码类型；
S505，用户前端设备12向终端设备13发送注册成功消息，该注册成功消息用于指示终端设备13注册成功；
接收到注册成功消息的终端设备13可以体现自己的在线状态，并且可以向用户前端设备12发送呼叫建立消息，以使用户前端设备12向网络侧11发起呼叫；
S506，用户前端设备12记录终端设备13注册失败，如果用户前端设备12接收到来自网络侧11针对用户前端设备12的呼叫，则不会将呼叫发送给记录为注册失败的终端设备13；
S507，用户前端设备12向终端设备13发送注册失败消息，该注册失败消息用于指示终端设备13注册失败；
接收到注册失败消息的终端设备13不会向用户前端设备12发送呼叫建立消息，或者可以向用户前端设备12发送呼叫建立消息，但是用户前端设备12不会向网络侧11发起呼叫；
S508，对于在S502-S507的注册中接收到注册成功消息的终端设备13，为了使得用户前端设备12在一段时间内实时地感知该终端设备13的在线状态，该终端设备13与用户前端设备12之间可以继续进行周期性注册，其中，每次注册执行S502-S507；
上述一段时间可以包括，但不限于，在终端设备13与用户前端设备12之间建立无线通信连接并且终端设备13开启为用户前端设备12实现与网络侧11之间的呼叫的功能(例如，但不限于，开启智能终端APP)的一段时间，或者在终端设备13与用户前端设备12之间建立无线通信连接的一段时间；
在另一种示例中，由于终端设备13已经在S502-S507的首次注册中向用户前端设备12发送过支持的音频和/或视频编解码类型，因此，在S508的周期性注册(即，非首次注册)中，注册请求消息可以不包括终端设备13支持的音频和/或视频编解码类型；
需要说明的是，对于在S502-S507的注册中接收到注册失败消息的终端设备13与用户前端设备12之间也可以继续进行周期性注册，其中，每次注册执行S502-S507；
S509，对于记录为在线状态的终端设备13，用户前端设备12确定最新一次接收到终端设备13的注册请求消息的时间与当前时间之间的时间间隔；
S510，用户前端设备12确定该时间间隔是否大于或等于预定时间间隔，若是，则继续执行S511，若否，则返回执行S509；
预定时间间隔的示例可以包括，但不限于，10秒、1分钟、5分钟、10分钟或其他长度的时间间隔；
S511，用户前端设备12将终端设备13的在线状态更改为离线状态，如果用户前端设备12接收到来自网络侧11针对用户前端设备12的呼叫，则不会将呼叫发送给记录为离线状态的终端设备13。
表1示出了注册过程涉及的用户前端设备12和终端设备13之间的控制面信令的一个示例，如表1所示，一段时间内的首次注册请求消息的命令部分可以包括值为“0x01”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，消息体部分可以包括终端设备13支持的音频和/或视频编解码类型，例如，支持的音频编解码类型可以包括EVS、AMR、AMR-WB、G.711，支持的视频编解码类型可以包括H.264、MPEG-2、MPEG-4、WMA-HD、VC-1；一段时间内的非首次注册请求消息的命令部分可以包括值为“0x02”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，消息体部分可以为空；注册成功消息的的命令部分可以包括值为“0x10”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，消息体部分可以为空；注册失败消息的的命令部分可以包括值为“0x20”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，消息体部分可以为空。
需要说明的是，注册过程涉及的控制面信令的结构和内容不限于表1示出的形式。
表1注册过程涉及的用户前端设备和终端设备之间的控制面信令
Figure PCTCN2021087860-appb-000001
现有技术中，用户前端设备通过RJ11口连接模拟话机，其中，用户前端设备的SLIC(Subscriber Line Interface Circuit，用户线接口电路)通过电压、电流判断模拟话机是否在线。而在本申请的实施例中，用户前端设备12通过注册过程知晓了下挂的终端设备13，并记录了处于在线状态的终端设备13，以及处于在线状态的终端设备13支持的音频和/或视频编解码类型，如此，在用户前端设备12作为被叫方接收到来自网络侧11的呼叫时，可以将呼叫发送给记录为在线状态的终端设备13。
在本申请的实施例中，收到注册成功消息的终端设备13可以显示自己的在线状态，使得用户可以通过该终端设备13，向用户前端设备12发送呼叫建立消息，以使用户前端设备12向网络侧11发起主叫。
图6示出了用户前端设备12和终端设备13之间的主叫过程600的流程示意图，需要说明的是，虽然在本申请的实施例中，以特定顺序呈现了方法的各个步骤，但是可以在不同的实施例中改变步骤的顺序，并且在一些实施例中，可以同时执行在本说明书中按顺序示出的一个或多个步骤。
如图6所示，主叫过程600包括：
S601，终端设备13向用户前端设备12发送呼叫建立消息，该呼叫建立消息可以指示用户前端设备12向网络侧11发起主叫；
在一种示例中，呼叫建立消息可以包括呼叫类型(语音呼叫或视频呼叫)和被叫方的标识，其中，被叫方的标识可以包括，但不限于，IMSI(International Mobile Subscriber Identity，国际移动用户标识)、TMSI(Temporary Mobile Subscriber Identity，临时移动用户标识)、MSISDN(Mobile Subscriber International ISDN/PSTN Number)、IMEI(International Mobile Equipment Identity，移动设备国际标识)、MSIN(Mobile Subscriber Identification Number，移动用户识别号码)等；
另外，呼叫建立消息还可以包括终端设备13的用于接收和/或发送媒体数据包的地址，例如，IP地址、与媒体数据包的传输协议相关的端口号等；
在呼叫类型为视频呼叫的情况下，呼叫建立消息还可以包括视频分辨率，例如，普清视频(例如，但不限于，640x480分辨率)、标清视频(例如，但不限于，960x720分辨率)和高清视频(例如，但不限于，1440x1080分辨率)等；
在另一种示例中，在注册请求消息中不包括终端设备13支持的音频和/或视频编解码类型的情况下，对应于呼叫类型为语音呼叫，呼叫建立消息还可以包括终端设备13支持的音频编解码类型，对应于呼叫类型为视频呼叫，呼叫建立消息还可以包括终端设备13支持的视频编解码类型，或者呼叫建立消息还可以包括终端设备13支持的音频编解码类型和视频编解码类型；例如，呼叫建立消息可以指示呼叫类型为语音呼叫，并且指示终端设备13支持的音频编解码类型为EVS-NB编解码；
S602，用户前端设备12向网络侧11发送呼叫请求消息；
在一种示例中，呼叫请求消息可以包括呼叫类型、被叫方的标识以及终端设备13支持的音频或视频编解码类型；
在呼叫类型为视频呼叫的情况下，呼叫请求消息还可以包括视频分辨率；
S603，用户前端设备12向终端设备13发送回铃音消息，该回铃音消息可以向终端设备13指示用户前端设备12正在拨号；
在一种示例中，回铃音消息可以包括回铃音，终端设备13收到回铃音消息后播放其中的回铃音；
在另一种示例中，回铃音消息中可以包括使得终端设备13播放回铃音的指示，终端设备13收到回铃音消息后播放终端设备13存储的回铃音；
S604，用户前端设备12与网络侧11之间进行媒体协商；
在一种示例中，用户前端设备12可以与网络侧11确定最终呼叫类型，最终呼叫类型可以是终端设备13和被叫方均选择的呼叫类型，或者在终端设备13和被叫方选择的呼叫类型不同的情况下，可以按照预先设置的语音呼叫和视频呼叫的优先级，以具有较高优先级的呼叫类型作为最终呼叫类型；
另外，用户前端设备12还可以与网络侧11确定最终音频或视频编解码类型，最终音频或视频编解码类型可以是终端设备13和被叫方均支持的音频或视频编解码类型，如果终端设备13和被叫方均支持的音频或视频编解码类型有多种，则可以按照预先设置的音频或视频编解码类型的优先级，确定一种音频或视频编解码类型作为最终音频或视频编解码类型；
在呼叫类型为视频呼叫的情况下，用户前端设备12还可以与网络侧11确定视频呼叫的最终视频分辨率，最终视频分辨率可以是终端设备13和被叫方均选择的视频分辨率，或者在终端设备13和被叫方选择的视频分辨率不同的情况下，以终端设备13和被叫方选择的视频分辨率中较低的视频分辨率作为最终视频分辨率，或者可以按照预先设置的视频分辨率的优先级，选择具有最高优先级的视频分辨率作为最终视频分辨率；
S605，网络侧11向用户前端设备12发送被叫接听指示；
S606，用户前端设备12向终端设备13发送被叫接听指示和协商通知消息，其中，协商通知消息包括媒体协商结果；
在一种示例中，媒体协商结果可以包括最终呼叫类型以及最终音频或视频编解码类型，在呼叫类型为视频呼叫的情况下，媒体协商结果还可以包括最终视频分辨率，例如，媒体协商结果包括的最终呼叫类型可以是语音呼叫，并且最终音频编解码类型可以是EVS-NB编解码；
另外，协商通知消息还可以包括用户前端设备12的用于接收和/或发送媒体数据包的地址，例如，IP地址、与媒体数据包的传输协议相关的端口号等；
S607，终端设备13向用户前端设备12发送媒体数据包；
在一种示例中，终端设备13可以基于媒体协商结果以及用户前端设备12的用于和/或发送媒体数据包的地址，发送媒体数据包，例如，采用EVS-NB编码的音频数据包；
S608，用户前端设备12向网络侧11发送来自终端设备13的媒体数据包；
其中，用户前端设备12向网络侧11发送媒体数据包时，不会携带终端设备13的ID；
S609，网络侧11向用户前端设备12发送来自被叫方的媒体数据包，例如，采用EVS-NB编码的音频数据包；
其中，来自被叫方的媒体数据包是针对用户前端设备12的，而不是针对终端设备13的，并且针对用户前端设备12指的是被叫方在发送媒体数据包时，携带用户前端设备12的标识，例如，但不限于，IMSI(International Mobile Subscriber Identity，国际移动用户标识)、TMSI(Temporary Mobile Subscriber Identity，临时移动用户标识)、MSISDN(Mobile Subscriber International ISDN/PSTN Number)、IMEI(International Mobile Equipment Identity，移动设备国际标识)、MSIN(Mobile Subscriber Identification  Number，移动用户识别号码)等；
S610，用户前端设备12向终端设备13发送来自被叫方的媒体数据包；
其中，用户前端设备12可以基于终端设备13的用于接收和/或发送媒体数据包的地址，发送媒体数据包；
S611，终端设备13向用户前端设备12发送呼叫结束消息，该呼叫结束消息指示呼叫结束；
在另一种示例中，在S611，网络侧11向用户前端设备12发送呼叫结束消息；
S612，用户前端设备12向网络侧11发送呼叫结束消息；
在另一种示例中，在S612，用户前端设备12向终端设备13发送呼叫结束消息。
表2示出了主叫过程涉及的用户前端设备12和终端设备13之间的控制面信令的一种示例，如表2所示，呼叫建立消息的命令部分可以包括值为“0x03”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，消息体部分可以指示终端设备13选择的呼叫类型为语音呼叫，以及终端设备13的用于接收和/或发送媒体数据包的IP地址、端口号；回铃音消息的命令部分可以包括值为“0x11”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，消息体部分可以为空；协商通知消息的命令部分可以包括值为“0x12”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，消息体部分可以指示最终呼叫类型为语音呼叫，最终音频编解码类型为EVS-NB，以及用户前端设备12的用于接收和/或发送媒体数据包的IP地址、端口号；对于终端设备13发送的呼叫结束消息，命令部分可以包括值为“0x04”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，消息体部分可以为空；对于用户前端设备12发送的呼叫结束消息，命令部分可以包括值为“0x14”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，消息体部分可以为空。
需要说明的是，主叫过程涉及的控制面信令的结构和内容不限于表2示出的形式。
表2主叫过程涉及的用户前端设备和终端设备之间的控制面信令
Figure PCTCN2021087860-appb-000002
需要说明的是，根据本申请的另一些实施例，用户前端设备12在接收到来自终端设备13的呼叫建立消息之后，可以首先确定该终端设备13的注册状态，如果该终端设备13注册失败，那么用户前端设备12不会向网络侧11发送呼叫请求消息，主叫过程结束；如果该终端设备13注册成功并且被记录为在线状态，那么用户前端设备12向网络侧11发送呼叫请求消息，并进行以上实施例中的步骤。
在本申请的实施例中，注册成功显示在线的终端设备13可以随时向用户前端设备12发送呼叫建立消息，使得用户前端设备12向网络侧发起呼叫，并且，在呼叫过程中，终端设备13可以在无线网络覆盖范围内随意移动。
另外，在现有技术中，用户前端设备的SLIC芯片通过电压、电流判断模拟话机的摘机、挂机，通过模拟线路上的信号判断拨号，SLIC芯片为模拟话机提供拨号音、回铃音等，另外，模拟话机线路和模拟话机只支持窄带语音，媒体协商一般只能协商成AMR-NB或者EVS-NB。
而在本申请的实施例中，用户前端设备12和终端设备13之间基于通过无线连接发送的消息来完成拨号、挂机等动作另外，终端设备13发送的呼叫建立消息指示呼叫类型，用户前端设备12可以根据终端设备13的支持的音频和/或视频编解码类型与网络侧进行媒体协商，而终端设备13可以支持高清语音EVS-WB、EVS-SWB、EVS-FB等编解码，并且当终端设备13还支持视频呼叫时，还可以协商成视频通信，并支持普清、标清、高清等视频格式。
图7示出了用户前端设备12和终端设备13之间的被叫过程700的流程示意图，需要说明的是，虽然在本申请的实施例中，以特定顺序呈现了方法的各个步骤，但是可以在不同的实施例中改变步骤的顺序，并且在一些实施例中，可以同时执行在本说明书中按顺序示出的一个或多个步骤。
如图7所示，被叫过程700包括：
S701，网络侧11向用户前端设备12发送针对用户前端设备12的呼叫；
其中，针对用户前端设备12指的是来自网络侧11的的呼叫包括用户前端设备12的标识；
S702，用户前端设备12确定记录为在线状态的一个或多个终端设备13；
例如，但不限于，用户前端设备12可以确定终端设备13a、13b以及13n在注册过程中被记录为在线状态；
S703，用户前端设备12向记录为在线状态的一个或多个终端设备13(例如，终端设备13a、13b以及13n)送来电消息，该来电消息可以指示终端设备13振铃；
在一些示例中，用户前端设备12可以同时向记录为在线状态的多个终端设备13发送来电消息；
在另一些示例中，用户前端设备12可以按照预定义的顺序(例如，按照预先设置的终端设备13的优先级)向记录为在线状态的多个终端设备13发送来电消息，例如，首先向具有最高优先级的终端设备13发送来电消息，如果在预定时间内，例如15秒内，用户前端设备12没有接收到来自该终端设备13的接听消息，则用户前端设备12停止向该终端设备13发送来电消息，并且遵循同样的规则，继续向具有次高优先级的终端设备13发送来电消息，直至用户前端设备12接收到来自终端设备13的接听消息为止；
S704，接收到来电消息的一个终端设备13(例如，终端设备13a)向用户前端设备12发送接听消息；
在一种示例中，接听消息可以包括呼叫类型，并且在呼叫类型为视频呼叫的情况下，接听消息还可以包括视频呼叫的视频分辨率；
另外，接听消息还可以包括终端设备13的用于接收和/或发送媒体数据包的地址，例如，IP地址、与传输协议相关的端口号等；
在另一种示例中，在注册请求消息中不包括终端设备13支持的音频和/或视频编解码类型的情况下，对应于呼叫类型为语音呼叫，接听消息还可以包括终端设备13支持的音频编解码类型，对应于呼叫类型为视频呼叫，接听消息还可以包括终端设备13支持的视频编解码类型，或者接听消息还可以包括终端设备13支持的音频编解码类型和视频编解码类型；例如，接听消息可以指示呼叫类型为语音呼叫，并且终端设备13支持的音频编解码类型为EVS-WB编解码；
S705，用户前端设备12为S704所述的终端设备13(例如，终端设备13a)，与网络侧11之间进行媒体协商；
在一种示例中，用户前端设备12可以与网络侧11确定最终呼叫类型，最终呼叫类型可以是终端设备13和被叫方均选择的呼叫类型，或者在终端设备13和被叫方选择的呼叫类型不同的情况下，可以按照预先设置的语音呼叫和视频呼叫的优先级，以具有较高优先级的呼叫类型作为最终呼叫类型；
另外，用户前端设备12还可以与网络侧11确定最终音频或视频编解码类型，最终音频或视频编解码类型可以是终端设备13和被叫方均支持的音频或视频编解码类型，如果终端设备13和被叫方均支持的音频或视频编解码类型有多种，则可以按照预先设置的音频或视频编解码类型的优先级，确定一种音频或视频编解码类型作为最终音频或视频编解码类型；
在呼叫类型为视频呼叫的情况下，用户前端设备12还可以与网络侧11确定视频呼叫的最终视频分辨率，最终视频分辨率可以是终端设备13和被叫方均选择的视频分辨率，或者在终端设备13和被叫方选择的视频分辨率不同的情况下，以终端设备13和被叫方选择的视频分辨率中较低的视频分辨率作为最终视频分辨率，或者可以按照预先设置的视频分辨率的优先级，选择具有最高优先级的视频分辨率作为最终视频分辨率；
S706，用户前端设备12停止向其他终端设备13(例如，终端设备13b和13n)发送来电消息；
S707，用户前端设备12向S704所述的终端设备13(例如，终端设备13a)发送协商通知消息，其中，协商通知消息包括媒体协商结果；
在一种示例中，媒体协商结果可以包括最终呼叫类型以及最终音频或视频编解码类型，在呼叫类型为视频呼叫的情况下，媒体协商结果还可以包括最终视频分辨率，例如，媒体协商结果包括的最终呼叫类型可以是语音呼叫，并且最终音频编解码类型可以是EVS-WB编解码；
另外，协商通知消息还可以包括用户前端设备12的用于接收和/或发送媒体数据包的地址，例如，IP地址、与媒体数据包的传输协议相关的端口号等；
S708，S704所述的终端设备13(例如，终端设备13a)向用户前端设备12发送媒体数据包；
在一种示例中，终端设备13可以基于媒体协商结果以及用户前端设备12的用于和/或发送媒体数据包的地址，发送媒体数据包，例如，采用EVS-WB编码的音频数据包；
S709，用户前端设备12向网络侧11发送来自S704所述的终端设备13(例如，终端设备13a)的媒体数据包；
其中，用户前端设备12向网络侧11发送媒体数据包时，不会携带终端设备13的ID；
S710，网络侧11向用户前端设备12发送来自被叫方的媒体数据包，例如，采用EVS-WB编码的音频数据包；
其中，来自被叫方的媒体数据包是针对用户前端设备12的，而不是针对终端设备13的；S711，用
户前端设备12向S704所述的终端设备13(例如，终端设备13a)发送来自被叫方的媒体数据包；
其中，用户前端设备12可以基于终端设备13的用于接收和/或发送媒体数据包的地址，发送媒体数据包；
S712，S704所述的终端设备13(例如，终端设备13a)向用户前端设备12发送呼叫结束消息，该呼叫结束消息指示呼叫结束；
在另一种示例中，在S712，网络侧11向用户前端设备12发送呼叫结束消息；
S713，用户前端设备12向网络侧11发送呼叫结束消息；
在另一种示例中，在S713，用户前端设备12向S704所述的终端设备13发送呼叫结束消息。
表3示出了被叫过程涉及的用户前端设备12和终端设备13之间的控制面信令的一种示例，如表3所示， 来电消息的命令部分可以包括值为“0x13”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，例如，终端设备13a、13b或者13n的MAC地址，消息体部分可以为空；接听消息的命令部分可以包括值为“0x03”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，例如，终端设备13a的MAC地址，消息体部分可以指示终端设备13a选择的呼叫类型为语音呼叫，以及终端设备13a的用于接收和/或发送媒体数据包的IP地址、端口号；对于用户前端设备12发送的呼叫结束消息，命令部分可以包括值为“0x14”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，例如，终端设备13a、13b或者13n的MAC地址，消息体部分可以为空；协商通知消息的命令部分可以包括值为“0x12”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，例如，终端设备13a的MAC地址，消息体部分可以指示最终呼叫类型为语音呼叫，最终音频编解码类型为EVS-WB，以及用户前端设备12的用于接收和/或发送媒体数据包的IP地址、端口号；对于终端设备13发送的呼叫结束消息，命令部分可以包括值为“0x04”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，例如，终端设备13a的MAC地址，消息体部分可以为空。
需要说明的是，被叫过程涉及的控制面信令的结构和内容不限于表3示出的形式。
表3被叫过程涉及的用户前端设备和终端设备之间的控制面信令
Figure PCTCN2021087860-appb-000003
在现有技术中，用户前端设备中的SLIC芯片通过用户线信令指示模拟话机有新的来电，用户接听后通过用户线信令通知用户前端设备；模拟话机线路和模拟话机只支持窄带语音，媒体协商一般只能协商成AMR-NB或者EVS-NB；并且，一个用户前端设备通常只有一个RJ11接口，因此只能接一个模拟话机，不能使用多个终端接听呼叫。
而在本申请的实施例中，用户前端设备2和终端设备13之间基于通过无线连接发送的消息来完成来电指示、接听动作，终端设备13发送的接听消息指示呼叫类型，用户前端设备12可以根据终端设备13的支持的音频和/或视频编解码类型与网络侧进行媒体协商，而终端设备13可以支持高清语音EVS-WB、EVS-SWB、EVS-FB等编解码，并且当终端设备13还支持视频呼叫时，还可以协商成视频通信，并支持普清、标清、高清等视频格式。
另外，在本申请的实施例中，用户前端设备12可以将来自网络侧的针对用户前端设备12的呼叫，通过无线连接发送给注册过程中记录为在线状态的一个或多个终端设备13，用户可以选择最方便的终端设 备13进行接听，并且，在接听时，可以在无线通信网络的覆盖范围内随意移动。
在以上实施例的主叫过程和被叫过程中，若用户正在使用例如终端设备13a进行呼叫，并希望切换到例如终端设备13n进行呼叫，那么用户可以通过终端设备13a向用户前端设备12发起切换过程。
图8示出了用户前端设备12和终端设备13之间的切换过程800的流程示意图，需要说明的是，虽然在本申请的实施例中，以特定顺序呈现了方法的各个步骤，但是可以在不同的实施例中改变步骤的顺序，并且在一些实施例中，可以同时执行在本说明书中按顺序示出的一个或多个步骤。
如图8所示，切换过程800包括：
S801，终端设备13(例如，终端设备13a)向用户前端设备12发送呼叫切换消息，该呼叫切换消息用于指示用户前端设备12进行呼叫切换；
S802，用户前端设备12确定除了终端设备13a之外，是否还存在记录为在线状态的一个或多个其他终端设备13，若否，则执行步骤S803，若是，则执行步骤S804-S815；
S803，用户前端设备12向终端设备13a发送切换失败消息，该切换失败消息用于向终端设备13a指示呼叫切换失败；
S804，用户前端设备12向该一个或多个其他终端设备13(例如，终端设备13b和13n)发送来电消息；
在一些示例中，用户前端设备12可以同时向该多个其他终端设备13发送来电消息；
在另一些示例中，用户前端设备12可以按照预定义的顺序(例如，按照预先设置的终端设备13的优先级)向该多个其他终端设备13发送来电消息，具体可以参照以上实施例中相应的描述；
S805，接收到来电消息的一个终端设备13(例如，终端设备13n)向用户前端设备12发送接听消息，具体可以参照以上实施例中相应的描述；
例如，接听消息可以指示呼叫类型为视频呼叫，终端设备13支持的视频编解码类型为H.264编解码，以及视频分辨率为高清分辨率；
S806，用户前端设备12为S805所述的终端设备13(例如，终端设备13n)，与网络侧11之间进行媒体协商，具体可以参照以上实施例中相应的描述；
S807，用户前端设备12停止向其他终端设备13(例如，终端设备13b)发送来电消息；
S808，用户前端设备12向S805所述的终端设备13(例如，终端设备13n)发送协商通知消息，具体可以参照以上实施例中相应的描述；
S809，S805所述的终端设备13(例如，终端设备13n)向用户前端设备12发送媒体数据包；
在一种示例中，终端设备13可以基于媒体协商结果以及用户前端设备12的用于和/或发送媒体数据包的地址，发送媒体数据包，例如，采用H.264编码的视频数据包；
S810，用户前端设备12向网络侧11发送来自S805所述的终端设备13(例如，终端设备13n)的媒体数据包；
其中，用户前端设备12向网络侧11发送媒体数据包时，不会携带终端设备13的ID；
S811，网络侧11向用户前端设备12发送来自被叫方的媒体数据包，例如，采用H.264编码的视频数据包采用H.264编码的视频数据包；
其中，来自被叫方的媒体数据包是针对用户前端设备12的，而不是针对终端设备13的；S812，用户前端设备12向S805所述的终端设备13(例如，终端设备13n)发送来自被叫方的媒体数据包；
其中，用户前端设备12可以基于终端设备13的用于接收和/或发送媒体数据包的地址，发送媒体数 据包；
S813，S805所述的终端设备13(例如，终端设备13n)向用户前端设备12发送呼叫结束消息，该呼叫结束消息指示呼叫结束；
在另一种示例中，在S813，网络侧11向用户前端设备12发送呼叫结束消息；
S814，用户前端设备12向网络侧11发送呼叫结束消息；
在另一种示例中，在S814，用户前端设备12向S805所述的终端设备13发送呼叫结束消息。
表4示出了切换过程涉及的用户前端设备12和终端设备13之间的控制面信令的一种示例，如表4所示，呼叫切换消息的命令部分可以包括值为“0x06”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，例如，终端设备13a的MAC地址，消息体部分可以为空；来电消息的命令部分可以包括值为“0x13”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，例如，终端设备13b或者13n的MAC地址，消息体部分可以为空；接听消息的命令部分可以包括值为“0x03”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，例如，终端设备13n的MAC地址，消息体部分可以指示终端设备13n选择的呼叫类型为视频呼叫，视频分辨率为高清分辨率，以及终端设备13n的用于接收和/或发送媒体数据包的IP地址、端口号；协商通知消息的命令部分可以包括值为“0x12”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，例如，终端设备13n的MAC地址，消息体部分可以指示最终呼叫类型为视频呼叫，最终视频分辨率为高清分辨率，最终视频编解码类型为H.264，以及用户前端设备12的用于接收和/或发送媒体数据包的IP地址、端口号；对于用户前端设备12发送的呼叫结束消息，命令部分可以包括值为“0x14”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，例如，终端设备13a或者13n的MAC地址，消息体部分可以为空；对于终端设备13发送的呼叫结束消息，命令部分可以包括值为“0x04”的字符串，终端设备ID部分可以包括终端设备13的MAC地址，例如，终端设备13n的MAC地址，消息体部分可以为空。
需要说明的是，切换过程涉及的控制面信令的结构和内容不限于表4示出的形式。
表4切换过程涉及的用户前端设备和终端设备之间的控制面信令
Figure PCTCN2021087860-appb-000004
Figure PCTCN2021087860-appb-000005
在现有技术中，一个用户前端设备12通常只有一个RJ11接口，因此只能连接一个模拟话机，不能用多个终端设备接听呼叫，也不能在多个终端设备之间随意切换。
而在本申请的实施例中，当有多个终端设备13注册在线时，在呼叫过程中，用户可以在多个终端设备13之间随意切换，并且切换终端设备13的同时还可以改变呼叫类型。
图9示出了根据本申请的实施例的电子设备900的框图，电子设备900可以是用户前端设备12或终端设备13。电子设备900可以包括一个或多个处理器901。电子设备900还可包括耦合到处理器901的存储器902和通信接口903。或者，存储器902可以被集成在处理器901内。
处理器901可以包括一个或多个单核或多核处理器。处理器902可以包括通用处理器和专用处理器(例如，图形处理器，应用处理器，基带处理器等)的任何组合。在本申请的实施例中，处理器901可以被配置为执行根据如图5-8所示的各种实施例的一个或多个实施例。
存储器902可以用于加载和存储例如，用于电子设备900的数据和/或指令。对于一个实施例，存储器902可以包括任何合适的易失性存储器，例如合适的动态随机存取存储器(DRAM)。在另一些实施例中，例如，存储器902可以包括用于存储数据和/或指令的一个或多个有形的，非暂时性计算机可读介质。存储器902可以包括但不限于通过机器或设备制造或形成的物品的非瞬态的有形安排，其包括存储介质，诸如：硬盘任何其它类型的盘，包括软盘、光盘、紧致盘只读存储器(CD-ROM)、紧致盘可重写(CD-RW)以及磁光盘；半导体器件，例如只读存储器(ROM)、诸如动态随机存取存储器(DRAM)和静态随机存取存储器(SRAM)之类的随机存取存储器(RAM)、可擦除可编程只读存储器(EPROM)、闪存、电可擦除可编程只读存储器(EEPROM)；相变存储器(PCM)；磁卡或光卡；或适于存储电子指令的任何其它类型的介质。
存储器902可以包含指令或包含设计数据，诸如硬件描述语言(HDL)，它定义本文中描述的结构、电路、装置、处理器和/或系统特征。这些实施例也被称为程序产品。
存储器902可以包括物理上是电子设备900的一部分的存储资源，或者它可以由电子设备900访问，但不一定是电子设备900的一部分。例如，可以经由通信接口903通过网络访问存储器902。
存储器902可以特别地包括指令的暂时或持久副本。指令可以包括当由至少一个处理器902执行时，导致电子设备900实现如参考图5-8描述的方法的指令。
通信接口903可以包括任何收发模块，以为电子设备900提供信号传输接口。
本文公开的机制的各实施例可以被实现在硬件、软件、固件或这些实现方法的组合中。本申请的实施例可实现为在可编程系统上执行的计算机程序或程序代码，该可编程系统包括至少一个处理器、存储系统(包括易失性和非易失性存储器和/或存储元件)、至少一个输入设备以及至少一个输出设备。
可将程序代码应用于输入指令，以执行本文描述的各功能并生成输出信息。可以按已知方式将输出信息应用于一个或多个输出设备。为了本申请的目的，处理系统包括具有诸如例如数字信号处理器(DSP)、微控制器、专用集成电路(ASIC)或微处理器之类的处理器的任何系统。
程序代码可以用高级程序化语言或面向对象的编程语言来实现，以便与处理系统通信。在需要时，也可用汇编语言或机器语言来实现程序代码。事实上，本文中描述的机制不限于任何特定编程语言的范围。在任一情形下，该语言可以是编译语言或解释语言。
至少一些实施例的一个或多个方面可以由存储在机器可读介质上的表示性指令来实现，指令表示处理器中的各种逻辑，指令在被机器读取时使得该机器制作用于执行本文所述的技术的逻辑。被称为“IP 核”的这些表示可以被存储在有形的机器可读介质上，并被提供给多个客户或生产设施以加载到实际制造该逻辑或处理器的制造机器中。
这样的机器可读存储介质可以包括但不限于通过机器或设备制造或形成的物品的非瞬态的有形安排，其包括存储介质，诸如：硬盘任何其它类型的盘，包括软盘、光盘、紧致盘只读存储器(CD-ROM)、紧致盘可重写(CD-RW)以及磁光盘；半导体器件，例如只读存储器(ROM)、诸如动态随机存取存储器(DRAM)和静态随机存取存储器(SRAM)之类的随机存取存储器(RAM)、可擦除可编程只读存储器(EPROM)、闪存、电可擦除可编程只读存储器(EEPROM)；相变存储器(PCM)；磁卡或光卡；或适于存储电子指令的任何其它类型的介质。
因此，本申请的各实施例还包括非瞬态的有形机器可读介质，该介质包含指令或包含设计数据，诸如硬件描述语言(HDL)，它定义本文中描述的结构、电路、装置、处理器和/或系统特征。这些实施例也被称为程序产品。

Claims (25)

  1. 一种用于用户前端设备的通信方法，其特征在于，包括：
    所述用户前端设备通过无线通信模式，在第一终端设备上实现所述用户前端设备与网络侧之间的呼叫，其中，所述呼叫包括被叫过程和主叫过程，
    在所述被叫过程中，在所述第一终端设备上实现所述用户前端设备与网络侧之间的呼叫包括：所述用户前端设备响应于接收到的来自所述网络侧的针对所述用户前端设备的所述呼叫，通过所述无线通信模式向所述第一终端设备发送所述呼叫；以及
    在所述主叫过程中，在所述第一终端设备上实现所述用户前端设备与网络侧之间的呼叫包括：所述用户前端设备响应于通过所述无线通信模式接收到的来自所述第一终端设备的呼叫建立消息，向所述网络侧发起呼叫。
  2. 如权利要求1所述的方法，其特征在于，还包括：
    所述用户前端设备在所述第一终端设备上实现所述呼叫之前，通过所述无线通信模式：
    接收来自所述第一终端设备的注册请求消息；
    在确定所述第一终端设备符合预定条件的情况下，记录所述第一终端设备处于在线状态，并向所述第一终端设备发送注册成功消息。
  3. 如权利要求2所述的方法，其特征在于，还包括：
    所述用户前端设备确定最新一次接收所述第一终端设备的所述注册请求消息的时间与当前时间之间的时间间隔；
    在所述用户前端设备确定所述时间间隔大于或等于预定时间间隔的情况下，记录所述第一终端设备处于离线状态。
  4. 权利要求2或3所述的方法，其特征在于，在所述被叫过程中，所述用户前端设备向所述第一终端设备发送所述呼叫，包括：
    向所述第一终端设备发送来电消息；
    接收来自所述第一终端设备的接听消息，所述接听消息指示所述呼叫的类型为语音呼叫或视频呼叫；
    根据所述第一终端设备支持的音频或视频编解码类型，以及所述呼叫的所述类型，与所述网络侧进行媒体协商；
    向所述第一终端设备发送协商通知消息，所述协商通知消息包括所述媒体协商的结果；
    向所述第一终端设备发送来自所述网络侧的媒体数据包，和/或向所述网络侧发送来自所述第一终端设备的所述媒体数据包。
  5. 如权利要求4所述的方法，其特征在于，接收的来自所述第一终端设备的所述注册请求消息或者所述接听消息包括所述第一终端设备支持的所述音频和/或视频编解码类型。
  6. 如权利要求4或5所述的方法，其特征在于，所述接听消息还包括所述第一终端设备的用于接收和/或发送所述媒体数据包的地址；
    所述协商通知消息还包括所述用户前端设备的用于接收和/或发送所述媒体数据包的地址。
  7. 如权利要求4-6中任一项所述的方法，其特征在于，在所述被叫过程中，还包括，所述用户前端设备通过无线通信模式：
    向被记录为在线状态的第二终端设备发送所述来电消息；
    响应于接收来自所述第一终端设备的所述接听消息，向所述第二终端设备发送呼叫结束消息。
  8. 如权利要求2或3所述的方法，其特征在于，在所述主叫过程中，所述呼叫建立消息指示所述呼叫 的类型为语音呼叫或视频呼叫以及被叫用户的标识，并且所述用户前端设备向所述网络侧发起呼叫，包括：
    向所述网络侧发送呼叫请求消息，所述呼叫请求消息包括所述呼叫的所述类型，所述第一终端设备支持的音频或视频编解码类型以及所述被叫用户的标识；
    向所述第一终端设备发送回铃音消息，所述回铃音消息指示所述第一终端设备播放回铃音；
    根据所述第一终端设备支持的所述音频或视频编解码类型，以及所述呼叫的所述类型，与所述网络侧进行媒体协商；
    向所述第一终端设备发送协商通知消息以及被叫接听指示，所述协商通知消息包括所述媒体协商的结果；
    向所述第一终端设备发送来自所述网络侧的媒体数据包，和/或向所述网络侧发送来自所述第一终端设备的所述媒体数据包。
  9. 如权利要求8所述的方法，其特征在于，所述注册请求消息或者所述呼叫建立消息包括所述第一终端设备支持的所述音频和/或视频编解码类型。
  10. 如权利要求8或9所述的方法，其特征在于，接收的来自所述第一终端设备的所述呼叫建立消息还包括所述第一终端设备的用于接收和/或发送所述媒体数据包的地址；
    所述协商通知消息还包括所述用户前端设备的用于接收和/或发送所述媒体数据包的地址。
  11. 如权利要求1-10中任一项所述的方法，其特征在于，所述无线通信模式为WiFi通信模式。
  12. 如权利要求8-10中任一项所述的方法，其特征在于，所述用户前端设备的标识是所述用户前端设备的用户标识，或者所述用户前端设备的设备标识。
  13. 一种用于终端设备的通信方法，其特征在于，包括：
    通过无线通信模式与用户前端设备建立连接，并为所述用户前端设备实现所述用户前端设备与网络侧之间的呼叫；
    其中，所述呼叫包括主叫过程和被叫过程，
    在被叫过程中，所述实现所述用户前端设备与网络侧之间的呼叫包括：所述终端设备通过无线通信模式接收来自所述用户前端设备的所述网络侧针对所述用户前端设备的呼叫；以及
    在主叫过程中，所述实现所述用户前端设备与网络侧之间的呼叫包括：所述终端设备通过无线通信模式向所述用户前端设备发送呼叫建立消息，使得所述用户前端设备向所述网络侧发起呼叫。
  14. 如权利要求13所述的方法，其特征在于，还包括，所述终端设备在为所述用户前端设备实现所述呼叫之前，通过所述无线通信模式：
    向所述用户前端设备发送注册请求消息；
    接收来自所述用户前端设备的注册成功消息。
  15. 如权利要求13或14所述的方法，其特征在于，在所述被叫过程中，所述终端设备接收来自用户前端设备的所述网络侧针对所述用户前端设备的呼叫，包括：
    接收来自所述用户前端设备的来电消息；
    向所述用户前端设备发送接听消息，所述接听消息指示所述呼叫的类型为语音呼叫或视频呼叫；
    接收来自所述用户前端设备的协商结果消息，所述协商结果消息包括所述用户前端设备与所述网络侧基于所述终端设备支持的音频或视频编解码类型以及所述呼叫的所述类型进行的媒体协商的结果；
    接收来自所述用户前端设备的媒体数据包，和/或向所述用户前端设备发送媒体
    数据包。
  16. 如权利要求15所述的方法，其特征在于，所述注册请求消息或者所述接听消息包括所述终端设备支持的所述音频和/或视频编解码类型。
  17. 如权利要求15或16所述的方法，其特征在于，所述接听消息包括所述终端设备的用于接收和/或发送所述媒体数据包的地址，
    所述协商结果消息包括所述用户前端设备的用于接收和/或发送所述媒体数据包的地址。
  18. 如权利要求13或14所述的方法，其特征在于，在所述主叫过程中，所述呼叫建立消息指示所述呼叫的类型为语音呼叫或视频呼叫以及被叫用户的标识，并且还包括：
    接收来自所述用户前端设备的回铃音消息，并响应于所述回铃音消息，播放回铃音；
    接收来自所述用户前端设备的协商结果消息，所述协商结果消息包括所述用户前端设备与所述网络侧基于所述终端设备支持的音频或视频编解码类型以及所述呼叫的所述类型进行的媒体协商的结果；
    向所述用户前端设备发送媒体数据包，和/或接收来自所述用户前端设备的所述媒体数据包。
  19. 如权利要求18所述的方法，其特征在于，所述注册请求消息或者所述呼叫建立消息包括所述终端设备支持的音频和/或视频编解码类型。
  20. 如权利要求18或19所述的方法，其特征在于，所述呼叫建立消息包括所述终端设备的用于接收和/或发送所述媒体数据包的地址，
    所述协商通知消息包括所述用户前端设备的用于接收和/或发送所述媒体数据包的地址。
  21. 如权利要求15-17中任一项所述的方法，其特征在于，在所述被叫过程中，所述终端设备接收来自用户前端设备的所述网络侧针对所述用户前端设备的呼叫，还包括：
    向所述用户前端设备发送呼叫切换消息；
    接收来自所述用户前端设备的切换失败消息，或者接收来自所述用户前端设备的呼叫结束消息。
  22. 如权利要求18-20中任一项所述的方法，其特征在于，在所述主叫过程中，还包括：
    所述终端设备向所述用户前端设备发送呼叫切换消息；
    所述终端设备接收来自所述用户前端设备的切换失败消息，或者接收来自所述用户前端设备的呼叫结束消息。
  23. 如权利要求13-22中任一项所述的方法，其特征在于，所述无线通信模式为WiFi通信模式。
  24. 一种机器可读介质，其特征在于，在所述介质上存储有指令，当所述指令在所述机器上运行时，使得所述机器执行权利要求1至12中任意一项所述的通信方法，和/或权利要求13至23中任意一项所述的通信方法。
  25. 一种系统，其特征在于，包括：用户前端设备和终端设备；所述用户前端设备用于执行所述权利要求1-12中任意一项所述的通信方法，所述终端设备用于执行所述权利要求13至23中任意一项所述的通信方法。
PCT/CN2021/087860 2020-04-23 2021-04-16 一种通信方法及系统 WO2021213282A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP21792822.5A EP4132137A4 (en) 2020-04-23 2021-04-16 COMMUNICATION METHOD AND SYSTEM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010327368.4A CN111654909B (zh) 2020-04-23 2020-04-23 一种通信方法及系统
CN202010327368.4 2020-04-23

Publications (1)

Publication Number Publication Date
WO2021213282A1 true WO2021213282A1 (zh) 2021-10-28

Family

ID=72352180

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/087860 WO2021213282A1 (zh) 2020-04-23 2021-04-16 一种通信方法及系统

Country Status (3)

Country Link
EP (1) EP4132137A4 (zh)
CN (1) CN111654909B (zh)
WO (1) WO2021213282A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111654909B (zh) * 2020-04-23 2022-06-24 华为技术有限公司 一种通信方法及系统

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101212313A (zh) * 2006-12-28 2008-07-02 深圳润汇科技有限公司 第三代移动通信系统用无线局域网路由器
CN102739676A (zh) * 2012-06-29 2012-10-17 中兴通讯股份有限公司 语音呼叫业务的实现方法及装置
US20170013232A1 (en) * 2012-07-20 2017-01-12 Time Warner Cable Enterprises Llc Transitioning video call between devices
CN106488167A (zh) * 2015-08-26 2017-03-08 中兴通讯股份有限公司 一种视频通话方法、网络设备、终端及系统
CN108322435A (zh) * 2017-12-26 2018-07-24 努比亚技术有限公司 一种多媒体通话方法、终端、ims服务器及存储介质
US20190110168A1 (en) * 2017-10-06 2019-04-11 D2 Technologies Inc. Communications system for establishing communications between mobile device and telephone network or broadband network
CN111654909A (zh) * 2020-04-23 2020-09-11 华为技术有限公司 一种通信方法及系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101572570B (zh) * 2009-06-10 2013-07-24 青岛海信移动通信技术股份有限公司 一种无线上网卡通过移动终端进行信息处理的方法和系统
CN102571153B (zh) * 2010-12-22 2014-06-04 深圳市云通时代科技开发有限公司 短距离无线移动终端及用于该终端的方法
US9961664B2 (en) * 2016-08-10 2018-05-01 Verizon Patent And Licensing Inc. Locating customer premises equipment in a narrow beamwidth based radio access network
WO2018155908A1 (ko) * 2017-02-22 2018-08-30 엘지전자(주) 무선 통신 시스템에서 릴레이를 통한 데이터 송수신 방법 및 이를 위한 장치
US10231104B2 (en) * 2017-06-08 2019-03-12 T-Mobile Usa, Inc. Proactive and reactive management for devices in a network
US10736070B2 (en) * 2017-07-26 2020-08-04 Blackberry Limited Method and system for use of a relay user equipment in an internet protocol multimedia subsystem

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101212313A (zh) * 2006-12-28 2008-07-02 深圳润汇科技有限公司 第三代移动通信系统用无线局域网路由器
CN102739676A (zh) * 2012-06-29 2012-10-17 中兴通讯股份有限公司 语音呼叫业务的实现方法及装置
US20170013232A1 (en) * 2012-07-20 2017-01-12 Time Warner Cable Enterprises Llc Transitioning video call between devices
CN106488167A (zh) * 2015-08-26 2017-03-08 中兴通讯股份有限公司 一种视频通话方法、网络设备、终端及系统
US20190110168A1 (en) * 2017-10-06 2019-04-11 D2 Technologies Inc. Communications system for establishing communications between mobile device and telephone network or broadband network
CN108322435A (zh) * 2017-12-26 2018-07-24 努比亚技术有限公司 一种多媒体通话方法、终端、ims服务器及存储介质
CN111654909A (zh) * 2020-04-23 2020-09-11 华为技术有限公司 一种通信方法及系统

Also Published As

Publication number Publication date
EP4132137A1 (en) 2023-02-08
CN111654909A (zh) 2020-09-11
CN111654909B (zh) 2022-06-24
EP4132137A4 (en) 2023-09-27

Similar Documents

Publication Publication Date Title
CN103596065B (zh) 装置定向能力交换信令和多媒体内容的服务器适应性修改
US9118934B2 (en) Integration of remote electronic device with media local area network
JP6359128B2 (ja) ビデオメディア再生方法、装置及びシステム、コンピュータ記憶メディア
RU2359424C2 (ru) Видеотелефонная система, устройство автономной базовой станции, телевизионная абонентская приставка и способ видеотелефонной связи
TWI559727B (zh) 高保真音頻分配設備
CN101346964A (zh) 用于与通信网络的远程用户建立多媒体会话的方法
US8320530B2 (en) Method, apparatus and system for realizing a multimedia call
WO2010003352A1 (zh) 一种彩铃选择方法、系统及相关装置
WO2015066972A1 (zh) 一种视频通话的转接方法、终端及系统
Shacham et al. Ubiquitous device personalization and use: The next generation of IP multimedia communications
CN104219479A (zh) 视频通信业务处理方法与系统
KR101730115B1 (ko) 영상 처리 장치 및 영상 처리 방법
WO2021213282A1 (zh) 一种通信方法及系统
CN116636192A (zh) 一种呼叫处理系统和呼叫处理方法
CN107547932A (zh) 数据信息的共享方法及装置、终端
JP2006229994A (ja) Ｉｐ端末装置
CN117062034A (zh) 蓝牙数据的传输方法、装置、设备及存储介质
JP4130542B2 (ja) マルチメディアコンテンツ変換装置およびテレビ電話端末
BRPI0720240A2 (pt) Método, sistema de telefone e terminal de telefone para seção de chamada
WO2020192435A1 (zh) 一种播放多媒体彩振、彩铃的方法、应用服务器
TW201412083A (zh) 高保真音頻分配系統之通訊設備
CN116346988A (zh) 接收来电的方法和装置
WO2001049014A1 (fr) Systeme de communication mobile comportant une fonction reponse, son dispositif de reseau et terminal de radiocommunication
CN114124906A (zh) 网关装置、用于网关装置的方法、计算机可读介质和装置
CN113132923A (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: 21792822

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021792822

Country of ref document: EP

Effective date: 20221025

NENP Non-entry into the national phase

Ref country code: DE