WO2019144720A1 - 业务共享方法、装置、存储介质及电子装置 - Google Patents

业务共享方法、装置、存储介质及电子装置 Download PDF

Info

Publication number
WO2019144720A1
WO2019144720A1 PCT/CN2018/120801 CN2018120801W WO2019144720A1 WO 2019144720 A1 WO2019144720 A1 WO 2019144720A1 CN 2018120801 W CN2018120801 W CN 2018120801W WO 2019144720 A1 WO2019144720 A1 WO 2019144720A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
sharing
service
request
response message
Prior art date
Application number
PCT/CN2018/120801
Other languages
English (en)
French (fr)
Inventor
覃磊
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2019144720A1 publication Critical patent/WO2019144720A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/16Communication-related supplementary services, e.g. call-transfer or call-hold
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08User group management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12Messaging; Mailboxes; Announcements
    • H04W4/14Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Definitions

  • the present disclosure relates to the field of communications, and relates to a service sharing method, apparatus, storage medium, and electronic device.
  • services can be transferred between terminals, for example, call forwarding and three-party calling.
  • Call forwarding also known as call forwarding, inbound and outbound. This feature can transfer incoming calls to other terminals.
  • Three-party calling also known as multi-party calling or conference calling, is a new service based on call waiting and call hold.
  • the three-party calling function of the mobile phone can realize a total of six-party calls including the caller.
  • multi-way dialogue (including two-way, the same principle) is to use the method of packet exchange, that is, all users are connected through the switch and transmitted to the backplane through the system bus. They are processed by a number of distributed processing units. They collect and amplify the signals and send them to the target terminal block. In this process, even if there are countless ways to talk at the same time, as long as any one sounds, it will be copied to all participants' ports immediately.
  • Call forwarding can be used to transfer incoming calls to another number when the user is inconvenient to answer the call.
  • the drawback is that the call can only be forwarded to a fixed number, and the user is not sure whether the phone of the other number is in the state of being turned off, on standby or in a call. This may result in another number not being answered after the call is transferred.
  • a three-way call enables multiple people to make a call at the same time, but if the conference initiator hangs up, everyone can't continue the call.
  • the embodiments of the present disclosure provide a service sharing method, device, storage medium, and electronic device, so as to at least solve the problem that the service of the terminal existing in the related art can only be shared to a fixed terminal, thereby resulting in low service sharing efficiency and poor user experience.
  • the problem is to at least solve the problem that the service of the terminal existing in the related art can only be shared to a fixed terminal, thereby resulting in low service sharing efficiency and poor user experience.
  • a service sharing method including: receiving an input service sharing indication, wherein the service sharing indication is used to indicate that a first service of a first terminal is shared to the first terminal On the second terminal in the shared group, the sharing group includes three or more terminals, and each terminal has the capability of sharing services with each other; and the service sharing request is sent to the network side under the trigger of the service sharing indication. And requesting, by the network side, the first service of the first terminal to be shared to the second terminal.
  • the method further includes: receiving a sharing success response message from the network side, and successfully responding according to the sharing The message terminates the first service in the first terminal; receives a sharing failure response message from the network side, and continues to execute the first service in the first terminal according to the sharing failure response message.
  • the method further comprises: receiving an input service sharing termination indication, wherein the service sharing termination indication is used to indicate termination of the The second terminal shares the first service of the first terminal, and sends a service sharing termination request to the network side under the trigger of the service sharing termination indication, to request the network side to terminate the second terminal sharing.
  • the first service of the first terminal after receiving the sharing success response message from the network side, the method further comprises: receiving an input service sharing termination indication, wherein the service sharing termination indication is used to indicate termination of the The second terminal shares the first service of the first terminal, and sends a service sharing termination request to the network side under the trigger of the service sharing termination indication, to request the network side to terminate the second terminal sharing.
  • the first service of the first terminal is a service sharing termination request to the network side under the trigger of the service sharing termination indication, to request the network side to terminate the second terminal sharing.
  • the method further includes: receiving a sharing termination success response message from the network side, according to The sharing termination success response message turns on the first service in the first terminal; receives a sharing termination failure response message from the network side, and maintains termination in the first terminal according to the sharing termination failure response message The status of the first service.
  • the method further includes receiving an input addition indication or a deletion indication, wherein the adding indication is used to indicate adding a third terminal in the sharing group, the deletion indication is used to indicate Deleting a fourth terminal in the sharing group; sending an add request to the network side under the trigger of the adding indication, to request the network side to add the third terminal in the sharing group; or The triggering of the deletion indication sends a deletion request to the network side to request the network side to delete the fourth terminal in the sharing group.
  • the method further includes: receiving an adding success response message from the network side, and successfully responding according to the adding The message adds the third terminal in the sharing group; receiving an add failure response message from the network side.
  • the method further includes: receiving a deletion success response message from the network side, and successfully responding according to the deletion The message deletes the fourth terminal in the sharing group.
  • the service sharing request includes first text information, where the first text information is used to instruct the network side to display the first text information on the second terminal. .
  • the sharing termination request includes second text information, wherein the second text information is used to instruct the network side to display the second text information on the second terminal.
  • the adding request includes third text information, wherein the third text information is used to instruct the network side to display the third text information on the third terminal.
  • the deletion request includes fourth text information, wherein the fourth text information is used to instruct the network side to display the fourth text information on the fourth terminal.
  • the method before receiving the input service sharing indication, the method further includes: displaying a usage status of the terminal other than the first terminal in the sharing group.
  • a service sharing method including: receiving a service sharing request from a first terminal, wherein the service sharing request is used to request to share a first service of the first terminal to On the second terminal in the sharing group where the first terminal is located, the sharing group includes three or more terminals, and each terminal has the capability of sharing services with each other; and determining that the second terminal has the shared In the case of the capability of the first service of the first terminal, the second terminal is controlled to share the first service of the first terminal according to the service sharing request.
  • the method further includes: returning a sharing success response message to the first terminal, and terminating the The first service in the first terminal.
  • the method further includes: determining that the second terminal does not have the capability of sharing the first service of the first terminal In the case, the sharing failure response message is sent to the first terminal to instruct the first terminal to continue to execute the first service.
  • the method further includes: receiving a service sharing termination request from the first terminal; performing termination according to the service sharing termination request The second terminal shares the processing of the first service of the first terminal.
  • the method further includes: to the first The terminal sends a sharing termination success response message, and starts the first service in the first terminal; sends a sharing termination failure response message to the first terminal, and maintains the second terminal sharing the first terminal. The status of the first service.
  • the method further includes: receiving an addition request from the first terminal; performing a process of adding a third terminal in the sharing group according to the adding request; or receiving from the a deletion request of the first terminal; performing a process of deleting the fourth terminal in the shared group according to the deletion request.
  • the method further includes: sending an add success response message to the first terminal, where Adding a success response message for indicating that the third terminal has been successfully added in the sharing group; sending an add failure response message to the first terminal, wherein the adding a failure response message is used to indicate that the sharing is Adding the third terminal to the group fails.
  • the method further includes: sending a deletion success response message to the first terminal, where The deletion success response message is used to indicate that the fourth terminal in the sharing group has been successfully deleted; and the deletion failure response message is sent to the first terminal, where the deletion failure response message is used to indicate that the sharing is deleted.
  • the fourth terminal in the group fails.
  • the service sharing request includes first text information
  • the method further includes: displaying the first text information in the first On the second terminal.
  • the sharing termination request includes second text information
  • the method further includes: displaying the second text information in On the second terminal.
  • the adding request includes third text information
  • the method further includes: displaying the third text information in the first On the three terminals.
  • the deletion request includes fourth text information
  • the method further includes: displaying the fourth text information in the first On the four terminals.
  • a service sharing apparatus including: a first receiving module, configured to receive an input service sharing indication, where the service sharing indication is used to indicate that the first terminal is to be first The service is shared to the second terminal in the sharing group where the first terminal is located, and the sharing group includes three or more terminals, and each terminal has the capability of sharing services with each other; the first sending module is configured to The service sharing indication is triggered to send a service sharing request to the network side, to request the network side to share the first service of the first terminal to the second terminal.
  • a service sharing apparatus including: a second receiving module, configured to receive a service sharing request from a first terminal, where the service sharing request is used to request the first The first service of a terminal is shared with the second terminal in the sharing group where the first terminal is located, and the sharing group includes three or more terminals, and each terminal has the capability of sharing services with each other; the control module, And determining, in the case that the second terminal has the capability of sharing the first service of the first terminal, controlling, according to the service sharing request, the second terminal to share the first terminal A business.
  • a storage medium having stored therein a computer program, wherein the computer program is configured to perform the steps of any one of the method embodiments described above at runtime.
  • an electronic device comprising a memory and a processor, wherein the memory stores a computer program, the processor being configured to execute the computer program to perform any of the above The steps in the method embodiments.
  • each terminal in the sharing group can share services with each other, that is, the terminal sharing the service of a certain terminal is no longer fixed, and the terminal can be flexibly selected from the sharing group according to actual conditions.
  • Service sharing can solve the problem that the services of the terminals existing in the related technologies can only be shared to a fixed terminal, resulting in low efficiency of service sharing and poor user experience, thereby achieving flexible sharing of the services of the terminal and improving user experience. effect.
  • FIG. 1 is a block diagram showing a hardware structure of a mobile terminal according to a service sharing method according to an embodiment of the present disclosure
  • FIG. 2 is a flowchart of a service sharing method according to an embodiment of the present disclosure
  • FIG. 3 is a flowchart of a service sharing method according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of a telephone switch in accordance with an embodiment of the present disclosure.
  • FIG. 5 is a flowchart of an incoming call handover process according to an embodiment of the present disclosure
  • FIG. 6 is a structural table of voice switching instructions provided according to an embodiment of the present disclosure.
  • FIG. 8 is a flowchart of a short message/mMS message switching process according to an embodiment of the present disclosure
  • FIG. 9 is a flowchart of canceling a short multimedia message sharing relationship according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic diagram of an interface display of a shared application according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic diagram of a voice switching prompt box according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic diagram of a video telephone switching prompt box according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic diagram of a short message forwarding prompt box according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic diagram of a multimedia message forwarding prompt box according to an embodiment of the present disclosure.
  • 15 is a schematic diagram of canceling a short message forwarding prompt box according to an embodiment of the present disclosure.
  • 16 is a schematic diagram of a cancel MMS forwarding prompt box according to an embodiment of the present disclosure.
  • FIG. 17 is a schematic diagram of adding a shared phone prompt box according to an embodiment of the present disclosure.
  • FIG. 18 is a structural block diagram of a first sharing device according to an embodiment of the present disclosure.
  • FIG. 19 is a structural block diagram of a second sharing device in accordance with an embodiment of the present disclosure.
  • FIG. 1 is a hardware structural block diagram of a mobile terminal of a service sharing method according to an embodiment of the present disclosure.
  • mobile terminal 10 may include one or more (only one shown in FIG. 1) processor 102 (processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA. And a memory 104 for storing data, in an exemplary embodiment, the mobile terminal may further include a transmission device 106 for communication functions and an input and output device 108.
  • processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA.
  • a memory 104 for storing data
  • the mobile terminal may further include a transmission device 106 for communication functions and an input and output device 108.
  • the structure shown in FIG. 1 is merely illustrative, and does not limit the structure of the above mobile terminal.
  • the mobile terminal 10 may also include more or fewer components than those shown in FIG
  • the memory 104 can be used to store computer programs, such as software programs and modules of application software, such as computer programs corresponding to the service sharing method in the embodiments of the present disclosure, and the processor 102 executes each by running a computer program stored in the memory 104.
  • a functional application and data processing, that is, the above method is implemented.
  • Memory 104 may include high speed random access memory, and may also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
  • memory 104 may further include memory remotely located relative to processor 102, which may be connected to mobile terminal 10 over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • Transmission device 106 is for receiving or transmitting data via a network.
  • An exemplary embodiment of the network described above may include a wireless network provided by a communication provider of the mobile terminal 10.
  • the transmission device 106 includes a Network Interface Controller (NIC) that can be connected to other network devices through a base station to communicate with the Internet.
  • the transmission device 106 can be a Radio Frequency (RF) module for communicating with the Internet wirelessly.
  • NIC Network Interface Controller
  • RF Radio Frequency
  • FIG. 2 is a flowchart of a service sharing method according to an embodiment of the present disclosure. As shown in FIG. 2, the process includes the following steps:
  • Step S202 Receive an input service sharing indication, where the service sharing indication is used to indicate that the first service of the first terminal is shared to the second terminal in the sharing group where the first terminal is located, and the sharing group includes three or more Terminals, and each terminal has the ability to share services with each other;
  • Step S204 Send a service sharing request to the network side under the trigger of the service sharing indication, to request the network side to share the first service of the first terminal to the second terminal.
  • the above operation may be performed by the first terminal, for example, and may be the terminal shown in Embodiment 1.
  • the terminals in the sharing group can share services with each other. That is to say, the terminals sharing the services of a certain terminal are no longer fixed, and the terminal can be flexibly selected from the sharing group according to actual conditions.
  • Service sharing can solve the problem that the services of the terminals existing in the related technologies can only be shared to a fixed terminal, resulting in low efficiency of service sharing and poor user experience, thereby achieving flexible sharing of the services of the terminal and improving user experience. effect.
  • the method further includes: receiving a sharing success response message from the network side, and terminating the first terminal according to the sharing success response message.
  • the first service in the network; receiving a sharing failure response message from the network side, and continuing to execute the first service in the first terminal according to the sharing failure response message.
  • the first terminal receives the sharing success response message sent from the network side, that is, after the first terminal requests the second terminal in the sharing group to share the first service successfully, the second terminal executes the first terminal.
  • the first service may terminate the current first service.
  • the first terminal receives the sharing failure response message sent by the network side, the first terminal requests the designated terminal in the sharing group to fail to share the first service. The first terminal can continue to execute the current first service.
  • the method further includes: receiving an input service sharing termination indication, where the service sharing termination indication is used to indicate termination of the second terminal sharing.
  • the first service of the first terminal is configured to send a service sharing termination request to the network side under the trigger of the service sharing termination indication, to request the network side to terminate the first terminal to share the first service of the first terminal.
  • the first terminal may also control to terminate the sharing operation, that is, after the first terminal receives the service sharing termination indication.
  • the service sharing termination request is sent to the network side, requesting the network side to terminate the first service of the first terminal currently shared by the second terminal, and ending the sharing operation with other terminals in the sharing group.
  • the method further includes: receiving a sharing termination success response message from the network side, according to the sharing termination success response message.
  • the first service in the first terminal is started; the shared termination failure response message from the network side is received, and the state of terminating the first service in the first terminal is maintained according to the shared termination failure response message.
  • the sharing termination operation succeeds, that is, when the first terminal and the other terminals in the sharing group end the sharing of the first service, the first terminal may continue to execute the first service; if the sharing termination operation fails In order to ensure the continuity of the service, the second terminal may continue to execute the first service shared by the first terminal.
  • the method further includes: receiving an input addition indication or a deletion indication, where the adding indication is used to indicate adding a third terminal in the sharing group, and the deleting indication is used to indicate deleting the sharing group.
  • the fourth terminal sends an addition request to the network side to trigger the network side to add the third terminal to the sharing group, or sends a deletion request to the network side to trigger the network side to request the network side. Delete the fourth terminal in the shared group.
  • the first terminal needs to add the terminal to the shared group, for example, adding the third terminal, the first terminal sends the related information (for example, the identification information) of the third terminal to the network side.
  • the network side determines whether the third terminal can be added to the shared group of the first terminal according to the relevant judgment condition (for example, whether the first terminal and the third terminal have the service sharing capability); if the first terminal Requesting to delete the fourth terminal in the sharing group sends a delete request to the network side to request cancellation of the sharing relationship.
  • the relevant judgment condition for example, whether the first terminal and the third terminal have the service sharing capability
  • the method further includes: receiving an add success response message from the network side, adding the first in the sharing group according to the adding a success response message.
  • Three terminals receive an add failure response message from the network side.
  • the first terminal sends an add request for requesting to add the third terminal to the shared group to the network side, if the add success response message fed back from the network side is received, the first terminal succeeds in the sharing group.
  • Adding a third user if the receiving failure response message is received, that is, the request to establish a sharing relationship fails, and no sharing is successful.
  • the method further includes: receiving a deletion success response message from the network side, and deleting the first in the sharing group according to the deletion success response message.
  • the first terminal sends a delete request for deleting the fourth terminal to the network side, if the received success response message is received from the network side, the fourth user in the shared group may be deleted. Otherwise, the request fails.
  • the foregoing service sharing request includes first text information, where the first text information is used to instruct the network side to display the first text information on the second terminal.
  • the other terminal may simultaneously carry the text information input by the first terminal, and the network side sends the text information to the network side.
  • the second terminal is displayed on the second terminal.
  • the sharing termination request includes second text information, where the second text information is used to instruct the network side to display the second text information on the second terminal.
  • the text information input by the first terminal may be carried, and the network side sends the text information to the sharing group.
  • a second terminal sharing the relationship is established and displayed on the second terminal.
  • the foregoing adding request includes third text information, wherein the third text information is used to instruct the network side to display the third text information on the third terminal.
  • the first terminal when the first terminal sends an add request for establishing a sharing relationship with the third terminal to the network side, the first terminal may carry the text information input by the first terminal, and the network side sends the text information to the third terminal, and Display on the third terminal.
  • the foregoing deletion request includes fourth text information, wherein the fourth text information is used to indicate that the network side displays the fourth text information on the fourth terminal.
  • the first terminal when the first terminal sends a deletion request for deleting the fourth terminal in the sharing group to the network side, the first terminal may carry the text information input by the first terminal, and the network side sends the text information to the fourth terminal. And display on the fourth terminal.
  • the method before receiving the input service sharing indication, further includes: displaying a usage status of the terminal other than the first terminal in the sharing group.
  • the first terminal because there are more than three terminals in the sharing group, when the first terminal needs to request the other terminal in the sharing group to share the first service of the first terminal, the first terminal needs to query the current usage state of the other terminal, and determine the sharing. In the group, the terminals in the group are idle. To ensure the success of service sharing, you can select the terminal in the idle state to share services.
  • FIG. 3 is a flowchart of a service sharing method according to an embodiment of the present disclosure. As shown in FIG. 3, the process includes the following steps:
  • Step S302 receiving a service sharing request from the first terminal, where the service sharing request is used to request to share the first service of the first terminal to the second terminal in the sharing group where the first terminal is located.
  • the sharing group includes three or more terminals, and each terminal has the capability of sharing services with each other;
  • Step S304 if it is determined that the second terminal has the capability of sharing the first service of the first terminal, controlling, according to the service sharing request, the second terminal to share the first terminal First business.
  • the above operation may be performed on the network side (for example, a base station).
  • the network side controls the service sharing operation between the terminals in the sharing group according to the received service sharing request, that is, the terminal that shares the service of a certain terminal through the network side is no longer fixed, and may be based on actual conditions.
  • the service of the terminal in the related technology can only be shared with a fixed terminal, resulting in low service sharing efficiency and poor user experience, thereby achieving service to the terminal.
  • Flexible sharing to improve the user experience.
  • the method further includes: returning a sharing success response message to the first terminal, and terminating the first in the first terminal business.
  • the network side sends a sharing success response message to the first terminal, that is, after the first terminal requests the second terminal to share the first service of the first terminal in the sharing group, the second terminal successfully executes the first terminal. The first service, the first terminal will terminate the current first service.
  • the method further includes: after determining that the second terminal does not have the capability of sharing the first service of the first terminal, The first terminal sends a sharing failure response message to instruct the first terminal to continue to execute the first service.
  • the network side sends a sharing failure response message to the first terminal, that is, the second terminal in the sharing group shares the first terminal. A service fails. At this time, the first terminal can continue to execute the current first service.
  • the method further includes: receiving a service sharing termination request from the first terminal; and performing termination of the second terminal sharing according to the service sharing termination request.
  • the processing of the first service of the terminal after the network side returns to the first terminal, the other terminal in the sharing group successfully shares the first service, if the network side receives the sharing termination request from the first terminal, the network side terminates the execution according to the sharing termination request.
  • the first service of the first terminal ends the current sharing operation.
  • the method further includes: sending a sharing termination success response message to the first terminal, and enabling The first service in the first terminal sends a shared termination failure response message to the first terminal, and maintains the state in which the second terminal shares the first service in the first terminal.
  • the network side after the network side receives the service sharing termination request from the first terminal, the network side feeds back a response message to the first terminal, and if the feedback is a shared termination success response message, the sharing termination operation request is successful.
  • the second terminal terminates sharing the first service of the first terminal, and the first terminal may continue to perform the first service; if the feedback is the shared termination failure response message, the sharing termination operation request fails, and the network side maintains the second terminal to continue sharing.
  • the method further includes: receiving an addition request from the first terminal; performing a process of adding a third terminal in the sharing group according to the adding request; or receiving a deletion request from the first terminal;
  • the delete request performs the process of deleting the fourth terminal in the shared group.
  • the network side may according to the relevant judgment condition (for example, whether the service is available between the first terminal and the third terminal) a sharing capability) to determine whether the third terminal can be added to the sharing group of the first terminal; if the network side receives the deletion request from the first terminal requesting to delete the fourth terminal in the sharing group, the network side shares the sharing group according to the deletion request.
  • the fourth terminal in the middle deletes and cancels the sharing relationship.
  • the method further includes: sending an adding success response message to the first terminal, where the adding a success response message is used to indicate The third terminal has been successfully added in the sharing group; the adding failure response message is sent to the first terminal, wherein the adding the failure response message is used to indicate that the adding of the third terminal fails in the sharing group.
  • the network side receives the add request from the first terminal requesting to add the third terminal in the shared group, if the network side sends the add success response message to the first terminal, the user may be in the shared group. If the third terminal is successfully added, if the network side sends an add failure response message, the request to add the third terminal fails.
  • the method further includes: sending a deletion success response message to the first terminal, where the deletion success response message is used to indicate The fourth terminal in the sharing group has been successfully deleted; the deletion failure response message is sent to the first terminal, where the deletion failure response message is used to indicate that the deletion of the fourth terminal in the sharing group fails.
  • the network side receives the deletion request from the first terminal to delete the fourth terminal, if the network side feeds back the deletion success response message, the first terminal may delete the fourth terminal in the sharing group; Request failed.
  • the foregoing service sharing request includes first text information
  • the method further includes: displaying the first text information on the second terminal.
  • the network side after the network side receives the service sharing request carrying the text information input by the first terminal, the network side sends the text information to the second terminal in the sharing group, and controls to display on the fourth terminal.
  • the foregoing sharing termination request includes second text information.
  • the method further includes: displaying the second text information on the second terminal.
  • the network side receives the sharing termination request that carries the text information input by the first terminal, the network side sends the text information to the sharing group, and the second sharing operation is established between the first terminal and the first terminal.
  • the terminal controls the display on the second terminal.
  • the foregoing adding request includes third text information
  • the method further includes: displaying the third text information on the third terminal.
  • the network side after the network side receives the add request carrying the text information input by the first terminal, the network side sends the text information to the third terminal in the sharing group, and controls the display on the third terminal.
  • the foregoing deletion request includes fourth text information.
  • the method further includes: displaying the fourth text information on the fourth terminal.
  • the network side after the network side receives the deletion request carrying the text information input by the first terminal, the network side sends the text information to the fourth terminal in the sharing group, and controls to display on the fourth terminal.
  • an app similar to "shared application” can be added to the mobile phone.
  • the mobile phone needs to send a sharing request to the other party. If the other party agrees, the shared application can be successfully added, and the sharing relationship is also stored in the network side.
  • FIG. 4 is a schematic diagram of a telephone handover according to an embodiment of the present disclosure, as shown in FIG.
  • S401, A and B are in a call state or call A.
  • A initiates a handover request, and switches the call to the mobile phone C.
  • the mobile phone A initiates a handover request to the network side, requesting C to share the A telephone service.
  • S403 The network sends the called party to the mobile phone C. After the network side receives the switching request of the A, the network side calls the C to request the control C to share the service of the mobile phone A after determining that the mobile phone C has the capability of sharing the service.
  • the short/mMS service is similar to the above-mentioned telephone switching service, which is relatively simple and will not be described here.
  • FIG. 5 is a flowchart of an incoming call handover process according to an embodiment of the present disclosure. As shown in FIG. 5, a process of switching an incoming call to a shared telephone, including a voice call and a video call, is as shown in FIG. 5 .
  • the process may include, for example:
  • Step 501 The mobile phone B calls the mobile phone A, A receives an incoming call prompt, or A and B are already in a call state;
  • Step 502 A opens the shared application interface on the mobile phone, and selects the shared number C;
  • Step 503 The mobile phone A sends a handover request to the network, where the request carries the caller number B and the switch number C. If the user further inputs text information, the switch request also carries the text information;
  • Step 504 The network receives the handover request, and determines whether there is a sharing relationship between A and C; if yes, proceeds to step 505, otherwise proceeds to step 509;
  • Step 505 The network sends an incoming call notification to the mobile phone C, and notifies that the A handover is successful, and A ends the call;
  • Step 506 User A has entered text information when selecting C in the shared application, if yes, proceeds to step 507, otherwise proceeds to step 508;
  • Step 507 The C mobile phone receives the incoming call prompt of B, and prompts C on the UI, which is the call that user A switches, and the process ends.
  • Step 508 The C mobile phone receives the incoming call prompt of B, and prompts C on the UI, which is the call that user A switches, and displays the text information input by A on the incoming call interface, and the process ends.
  • Step 509 The network rejects the handover request, and notifies the A that the handover fails due to the reason of no sharing relationship;
  • Step 510 A receives the message that the handover fails, the mobile phone prompts the user that the handover fails, and A is still in the previous call or call state, and the process ends.
  • the call includes both normal voice calls and volte (Voice over LTE) calls, that is, calls in the data domain. Because the difference between the two is relatively large, the following will be described separately:
  • FIG. 6 is a structural table of a voice switching instruction according to an embodiment of the present disclosure.
  • the instruction signaling is roughly structured as shown in FIG. 6.
  • the C mobile phone receives the incoming call from the A, and the incoming call information is transmitted through the SETUP signaling, but needs to add the A number information in the current SETUP information, so that C can know
  • the call was switched by A. 7 is a SETUP structure table received by a user according to an embodiment of the present disclosure. The approximate structure of the SETUP signaling received by the C user is as shown in FIG. 7.
  • the extended instruction 608 is tentatively defined (ie, the extended instruction is denoted by 608); according to RFC3261, the instruction set of 6XX is Is the type of user rejection.
  • the extended 608 instruction is similar to:
  • the C mobile phone receives the incoming call from the A, and the incoming call information is transmitted through the INVITE message, but needs to be added in the current INVITE message by the keyword “P-Switched-Party-ID”.
  • the number information of A so that C can know that the incoming call is switched by A.
  • the following is an example of an INVITE message received by a C user, and the underlined part is an extended message:
  • FIG. 8 is a flowchart of a short message/mMS message switching process according to an embodiment of the present disclosure. As shown in FIG. 8, an exemplary process for switching a short/mMS message to a shared number is:
  • Step 801 User A enters the shared app and selects to transfer the SMS/MMS to the shared number B.
  • Step 802 The mobile phone sends a short/multimedia message switching request to the network, where the request carries the mobile phone number of the user A and the shared number B. If A still has input text information, it also carries text information;
  • Step 803 The network receives the handover request, and determines whether there is a sharing relationship between the numbers AB. If yes, go to step 804, otherwise go to step 806;
  • Step 804 The network sends a switching notification to B. If A has input text information, it also carries text information. At the same time, notify user A that the handover is successful. The short/multiple letter sent to A after that will be sent directly to B;
  • Step 805 The mobile phone notifies the user B: User A transfers the short/MMS to the mobile phone, and the process ends.
  • Step 806 The network rejects the handover request, and notifies the A that the handover fails due to the reason of no sharing relationship;
  • Step 807 A receives the message that the handover fails, and the mobile phone prompts the user to fail the handover.
  • the short/mMS sent to A will still be sent to the number of A, and the process ends.
  • the phone-related sharing function is an operation in an incoming call or a call, that is, the sharing switch is one-time.
  • the short/MMS share switching is not the case.
  • User A's short/MMS will always be used for the shared number. So there must be a process to cancel the short/MMS sharing relationship.
  • FIG. 9 a flow chart for canceling the short/MMS sharing relationship is provided in the embodiment of the present disclosure.
  • the process of canceling the short/MMS cancellation relationship with a certain number, for example, the process shown in FIG. 9 may include:
  • Step 901 User A enters the sharing app, and selects the SMS/MMS sharing relationship of the number B to be canceled;
  • Step 902 The mobile phone sends a short/mMS unsubscribe request to the network, where the request carries the mobile phone number of the user A and the shared number B. If A still has input text information, it also carries text information;
  • Step 903 The network receives the cancel sharing request, determines whether there is a sharing relationship between the numbers AB, and if yes, proceeds to step 904, otherwise proceeds to step 906;
  • Step 904 The network side deletes the sharing relationship between A and B, and sends a cancellation sharing notification to B. If A has input text information, it also carries text information, and notifies A that the cancellation is successful.
  • Step 905 The mobile phone notifies B: User A has cancelled the short/MMS sharing, and the process ends.
  • Step 906 The network rejects the handover request, and notifies A that the cancellation fails due to the reason of no sharing relationship;
  • Step 907 A receives the message that the cancellation failed, and the mobile phone prompts the user to cancel the failure.
  • the short/MMS sent to A will still be sent to the number of B, and the process ends.
  • FIG. 10 is a schematic diagram of an interface display of a shared application according to an embodiment of the present disclosure. As shown in FIG. 10, it is assumed that at least four user terminals are shared in the shared application, and more mobile phone numbers can be added in the shared application. Can share voice calls, video calls, SMS, MMS, etc., display the mobile phone number 1, 2, 3, 4 users' usage status. If mobile numbers 1 and 3 are in standby, mobile number 2 is in the call, mobile number 4 is in the shutdown state, then at this time, the user can request to share the specified service from any one of the mobile phone numbers 1 and 3.
  • FIG. 11 is a schematic diagram of a voice switching prompt box according to an embodiment of the present disclosure. If a user clicks on a voice phone part of the mobile phone number 1, a prompt box is popped up on the original interface, as shown in FIG. 11 : in order to avoid misoperation Generated, so you still need to have a confirmation box. And in the confirmation box, you can continue to input text information, the information will be displayed on the incoming call interface of the mobile phone number 1, and give the mobile phone 1 user some prompt information.
  • FIG. 12 is a schematic diagram of a video telephone switching prompt box according to an embodiment of the present disclosure. If a video telephone part of the mobile phone number 1 is clicked, a prompt box is popped up on the original interface, as shown in FIG. 12: the same is to avoid If the operation is wrong, a confirmation box will be displayed on the interface. The confirmation box can continue to input text information, and the network side will send the text information to the caller ID interface in the mobile number 1.
  • FIG. 13 is a schematic diagram of a short message forwarding prompt box according to an embodiment of the present disclosure. As shown in FIG. 13 , if the user does not share a short message with the mobile phone number 1 , the short message portion of the mobile phone number 1 is clicked, and the original interface is popped up. A prompt box.
  • FIG. 14 is a schematic diagram of a MMS forwarding prompt box according to an embodiment of the present disclosure. As shown in FIG. 14 , if the user does not share the MMS with the mobile phone number 1 , the MMS part of the mobile phone number 1 is clicked, and the original interface is popped up. A prompt box.
  • FIG. 15 is a schematic diagram of canceling a short message forwarding prompt box according to an embodiment of the present disclosure. If a user and a mobile phone number 1 are already in a shared short message state, and the user needs to terminate the shared service, the short message portion of the mobile phone number 1 is clicked. A prompt box is displayed on the interface. As shown in Figure 15, the confirmation box indicates whether the current service needs to be canceled. The user can also input text information, and the network side controls the text information to be sent to the mobile phone number 1.
  • FIG. 16 is a schematic diagram of canceling a multimedia message forwarding prompt box according to an embodiment of the present disclosure. As shown in FIG. 16, if a user and a mobile phone number 1 have shared a multimedia message, clicking the MMS part of the mobile phone number 1 is performed on the original interface. A prompt box is displayed, which is similar to canceling the SMS sharing service, and will not be described again.
  • FIG. 17 is a schematic diagram of adding a shared telephone prompt box according to an embodiment of the present disclosure.
  • the mobile phone will send a sharing request to the network, which carries the shared phone number. If the user needs to input text information, the text information can also be sent to the network together. Send the relevant information to the shared number user, and complete the sharing process after obtaining the consent of the other party. The phone UI prompt was added successfully.
  • the network side also stores a list of the user's shared number.
  • the first type of service sharing device is also provided in the embodiment, and the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 18 is a structural block diagram of a first sharing apparatus according to an embodiment of the present disclosure.
  • the apparatus may be applied to a terminal, for example, applied to a first terminal.
  • the apparatus includes: a first receiving module 182. And a service sharing indication, where the service sharing indication is used to indicate that the first service of the first terminal is shared to the second terminal in the sharing group where the first terminal is located, where the sharing group includes three or more terminals.
  • the first sending module 184 is connected to the first receiving module 182, and is configured to send a service sharing request to the network side under the trigger of the service sharing indication, to request the network side to The first service of the first terminal is shared with the second terminal.
  • the apparatus is further configured to: after sending the service sharing request to the network side triggered by the service sharing indication, receive the sharing success response message from the network side, and terminate the first terminal according to the sharing success response message.
  • the first service in the first service receiving the sharing failure response message from the network side, and continuing to execute the first service in the first terminal according to the sharing failure response message.
  • the apparatus is further configured to: after receiving the sharing success response message from the network side, receive an input service sharing termination indication, where the service sharing termination indication is used to indicate termination of the second terminal sharing.
  • the first service of the first terminal is configured to send a service sharing termination request to the network side to trigger the second terminal to share the first service of the first terminal.
  • the apparatus is further configured to: after sending the service sharing termination request to the network side under the trigger of the service sharing termination indication, receive the sharing termination success response message from the network side, according to the sharing termination success response message
  • receive the sharing termination success response message from the network side according to the sharing termination success response message
  • the first service in the first terminal is started; the shared termination failure response message from the network side is received, and the state of terminating the first service in the first terminal is maintained according to the shared termination failure response message.
  • the apparatus is further configured to: receive an input addition indication or a deletion indication, where the adding indication is used to indicate adding a third terminal in the sharing group, and the deleting indication is used to indicate deletion in the sharing group
  • the fourth terminal sends an addition request to the network side to trigger the network side to add the third terminal to the sharing group, or sends a deletion request to the network side to trigger the network side deletion.
  • the fourth terminal in the shared group is further configured to: receive an input addition indication or a deletion indication, where the adding indication is used to indicate adding a third terminal in the sharing group, and the deleting indication is used to indicate deletion in the sharing group
  • the fourth terminal sends an addition request to the network side to trigger the network side to add the third terminal to the sharing group, or sends a deletion request to the network side to trigger the network side deletion.
  • the fourth terminal in the shared group is further configured to: receive an input addition indication or a deletion indication, where the adding indication is used to indicate adding a third terminal in the sharing group, and the deleting indication is used to indicate deletion
  • the apparatus is further configured to: after sending the adding request to the network side under the trigger of adding the indication, receiving the adding success response message from the network side, adding the first in the sharing group according to the adding success response message Three terminals; receive an add failure response message from the network side.
  • the apparatus is further configured to: after sending the deletion request to the network side under the trigger of the deletion indication, receive the deletion success response message from the network side, and delete the first in the sharing group according to the deletion success response message.
  • the apparatus is further configured to: after sending the deletion request to the network side under the trigger of the deletion indication, receive the deletion success response message from the network side, and delete the first in the sharing group according to the deletion success response message.
  • the service sharing request includes first text information, where the first text information is used to instruct the network side to display the first text information on the second terminal.
  • the sharing termination request includes second text information, wherein the second text information is used to instruct the network side to display the second text information on the second terminal.
  • the adding request includes third text information, wherein the third text information is used to instruct the network side to display the third text information on the third terminal.
  • the deletion request includes fourth text information, wherein the fourth text information is used to instruct the network side to display the fourth text information on the fourth terminal.
  • the apparatus is further configured to: before receiving the input service sharing indication, display a usage status of the terminal other than the first terminal in the sharing group.
  • the second receiving module 192 is configured to receive a service sharing request from the first terminal, where the service sharing request is used to request to share the first service of the first terminal to the sharing group where the first terminal is located.
  • the sharing group includes three or more terminals, and each terminal has the capability of sharing services with each other; the control module 194 is connected to the second receiving module 192 for determining that the second terminal has the sharing.
  • the second terminal is controlled to share the first service of the first terminal according to the service sharing request.
  • the apparatus is further configured to: after controlling the second terminal to share the first service of the first terminal, return a sharing success response message to the first terminal, and terminate the first service in the first terminal .
  • the apparatus is further configured to: after receiving the service sharing request from the first terminal, determining that the second terminal does not have the capability of sharing the first service of the first terminal, A terminal sends a sharing failure response message to instruct the first terminal to continue to execute the first service.
  • the apparatus is further configured to: after returning the sharing success response message to the first terminal, receive a service sharing termination request from the first terminal; and terminate the second terminal sharing according to the service sharing termination request. The processing of the first service of a terminal.
  • the apparatus is further configured to: after performing the process of terminating the first terminal sharing the first service of the first terminal according to the service sharing termination request, sending a sharing termination success response message to the first terminal, and The first service in the first terminal is started, and the shared termination failure response message is sent to the first terminal, and the second terminal is maintained to share the state of the first service in the first terminal.
  • the apparatus is further configured to: receive an addition request from the first terminal; perform a process of adding a third terminal in the sharing group according to the adding request; or receive a deletion request from the first terminal; The process of deleting the fourth terminal in the shared group is performed according to the deletion request.
  • the apparatus is further configured to: after performing the process of adding the third terminal in the sharing group according to the adding request, sending an adding success response message to the first terminal, where the adding a success response message is used for Indicates that the third terminal has been successfully added in the sharing group; and the adding failure response message is sent to the first terminal, wherein the adding the failure response message is used to indicate that the adding of the third terminal in the sharing group fails.
  • the apparatus is further configured to: after performing the process of deleting the fourth terminal in the sharing group according to the deletion request, sending a deletion success response message to the first terminal, where the deletion success response message is used for Indicates that the fourth terminal in the sharing group has been successfully deleted; and the deletion failure response message is sent to the first terminal, where the deletion failure response message is used to indicate that the deletion of the fourth terminal in the sharing group fails.
  • the service sharing request includes first text information
  • the apparatus is further configured to display the first text information on the second terminal after receiving the service sharing request from the first terminal.
  • the sharing termination request includes second text information
  • the apparatus is further configured to display the second text information on the second terminal after receiving the service sharing termination request from the first terminal.
  • the adding request includes the third text information
  • the apparatus is further configured to display the third text information on the third terminal after receiving the adding request from the first terminal.
  • the fourth text information is included in the deletion request, and the apparatus is further configured to display the fourth text information on the fourth terminal after receiving the deletion request from the first terminal.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • Embodiments of the present disclosure also provide a storage medium having stored therein a computer program, wherein the computer program is configured to execute the steps of any one of the method embodiments described above.
  • the foregoing storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (Random Access Memory).
  • Various media that can store computer programs such as RAM), mobile hard disks, disks, or optical disks.
  • Embodiments of the present disclosure also provide an electronic device including a memory and a processor having a computer program stored therein, the processor being configured to execute a computer program to perform the steps of any one of the method embodiments described above.
  • the electronic device may further include a transmission device and an input and output device, wherein the transmission device is connected to the processor, and the input and output device is connected to the processor.
  • modules or steps of the present disclosure described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices.
  • they may be implemented by program code executable by a computing device such that they may be stored in a storage device for execution by the computing device and, in some cases, may be different
  • the steps shown or described herein are performed sequentially, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the disclosure is not limited to any specific combination of hardware and software.
  • the terminal sharing the service of a certain terminal is not fixed, and the terminal can be flexibly selected from the sharing group to perform service sharing according to the actual situation, and the service of the terminal existing in the related technology can only be shared.
  • a fixed terminal causes poor service sharing and poor user experience, and thus achieves the effect of flexibly sharing the services of the terminal and improving the user experience.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本公开提供了一种业务共享方法、装置、存储介质及电子装置,该方法包括:接收输入的业务共享指示,其中,所述业务共享指示用于指示将第一终端的第一业务共享到所述第一终端所在的共享组中的第二终端上,所述共享组中包括三个以上终端,且各终端之间具备互相共享业务的能力。通过本公开,解决了相关技术中存在的终端的业务只能共享给固定的一个终端,从而导致业务共享效率低,用户体验差的问题,进而达到可以对终端的业务进行灵活共享,提高用户体验的效果。

Description

业务共享方法、装置、存储介质及电子装置 技术领域
本公开涉及通信领域,涉及一种业务共享方法、装置、存储介质及电子装置。
背景技术
随着近年来移动终端的普及,人们对移动终端的依赖度呈直线上升,以手机为例,随着低价位手机的推出,基本上人手一部手机,某些用户甚至有2部以上手机。而电话、短信业务作为手机的最基本业务之一,也是最重要的业务之一。用户可以拨打电话,接听来电,与其他人进行通话,与他人发送短信进行沟通。
在相关技术中,终端之间是可以进行业务转移的,例如,呼叫转移和三方通话。
呼叫转移,又称呼叫前转、呼入转移。该功能可以将来电转移到其它终端上。
三方通话又称多方通话或会议电话,是建立在呼叫等待与呼叫保持基础上的一项新业务,手机的三方通话功能最多可以实现包括发话者在内总计六方通话。对于目前微电子式的程控交换机,要实现多路对话(包括两路,原理一样),都是使用数据包交换的方法,即所有用户通过接线器接入,通过系统总线传递到背板上,分别由很多的分布式处理单元进行处理,他们将各路信号采集,放大等处理之后,再送到目标接线板上。在这个过程中,即便是无数路同时通话,只要有任何一条发出声音,就会被马上复制到所有参与者的端口。
呼叫转移可以实现在用户不方便接听电话的时候,可以将来电转到另一个号码上。存在的缺陷是:只能将来电转给一个固定的号码,而且用户并不能确定另一个号码的手机所处的状态,是关机了还是待机还是正在通话中。这样就可能出现来电转接之后,另一个号码也没有顺利接听的情况。
三方通话则实现了多人同时进行通话,但是如果会议发起者挂断电话,则所有人都无法继续通话。
针对相关技术中存在的上述问题至少之一,目前尚未提出有效的解决方案。
发明内容
本公开实施例提供了一种业务共享方法、装置、存储介质及电子装置,以至少解决相关技术中存在的终端的业务只能共享给固定的一个终端,从而导致业务共享效率低,用户体验差的问题。
根据本公开的一个实施例,提供了一种业务共享方法,包括:接收输入的业务共享指示,其中,所述业务共享指示用于指示将第一终端的第一业务共享到所述第一终端所在的共享组中的第二终端上,所述共享组中包括三个以上终端,且各终端之间具备互相共享业务的能力;在所述业务共享指示的触发下向网络侧发送业务共享请求,以请求所述网络侧将所述第一终端的第一业务共享给所述第二终端。
在一示例性实施例中,在所述业务共享指示的触发下向网络侧发送业务共享请求之后,所述方法还包括:接收来自所述网络侧的共享成功响应消息,根据所述共享成功响应消息终止所述第一终端中的所述第一业务;接收到来自所述网络侧的共享失败响应消息,根据所述共享失败响应消息在所述第一终端中继续执行所述第一业务。
在一示例性实施例中,在接收来自所述网络侧的共享成功响应消息之后,所述方法还包括:接收输入的业务共享终止指示,其中,所述业务共享终止指示用于指示终止所述第二终端共享所述第一终端的所述第一业务;在所述业务共享终止指示的触发下向所述网络侧发送业务共享终止请求,以请求所述网络侧终止所述第二终端共享所述第一终端的所述第一业务。
在一示例性实施例中,在所述业务共享终止指示的触发下向所述网络侧发送业务共享终止请求之后,所述方法还包括:接收来自所述网络侧的共享终止成功响应消息,根据所述共享终止成功响应消息开启所述第一终端中的所述第一业务;接收来自所述网络侧的共享终止失败响应消息,根据所述共享终止失败响应消息维持终止所述第一终端中的所述第一业务的状态。
在一示例性实施例中,所述方法还包括:接收输入的添加指示或删除指示,其中,所述添加指示用于指示在所述共享组中添加第三终端,所述删除指示用于指示删除所述共享组中的第四终端;在所述添加指示的触发下向所述网络侧发送添加请求,以请求所述网络侧在所述共享组中添加所述第三终端;或者,在所述删除指示的触发下向所述网络侧发送删除请求,以请求所述网络侧删除所述共享组中的所述第四终端。
在一示例性实施例中,在所述添加指示的触发下向所述网络侧发送添加请求之后,所述方法还包括:接收来自所述网络侧的添加成功响应消息,根据所述添加成功响应消息在所述共享组中添加所述第三终端;接收来自所述网络侧的添加失败响应消息。
在一示例性实施例中,在所述删除指示的触发下向所述网络侧发送删除请求之后,所述方法还包括:接收来自所述网络侧的删除成功响应消息,根据所述删除成功响应消息删除所述共享组中的所述第四终端。
在一示例性实施例中,所述业务共享请求中包括第一文本信息,其中,所述第一文本信息用于指示所述网络侧将所述第一文本信息显示在所述第二终端上。
在一示例性实施例中,所述共享终止请求中包括第二文本信息,其中,所述第二文本信息用于指示所述网络侧将所述第二文本信息显示在所述第二终端上。
在一示例性实施例中,所述添加请求中包括第三文本信息,其中,所述第三文本信息用于指示所述网络侧将所述第三文本信息显示在所述第三终端上。
在一示例性实施例中,所述删除请求中包括第四文本信息,其中,所述第四文本信息用于指示所述网络侧将所述第四文本信息显示在所述第四终端上。
在一示例性实施例中,在接收输入的业务共享指示之前,所述方法还包括:显示所述共享组中除所述第一终端之外的其他终端的使用状态。
根据本公开的一个实施例,提供了一种业务共享方法,包括:接收来自第一终端的业务共享请求,其中,所述业务共享请求用于请求将所述第一终端的第一业务共享到所述第一终端所在的共享组中的第二终端上,所述共享组中包括三个以上终端,且各终端之间具备互相共享业务的能力;在确定所述第二终端具备共享所述第一终端的所述第一业务的能力的情况下,根据所述业务共享请求控制所述第二终端共享所述第一终端的所述第一业务。
在一示例性实施例中,在控制所述第二终端共享所述第一终端的所述第一业务之后,所述方法还包括:向所述第一终端返回共享成功响应消息,并终止所述第一终端中的所述第一业务。
在一示例性实施例中,在接收来自第一终端的业务共享请求之后,所述方法还包括:在确定所述第二终端不具备共享所述第一终端的所述第一业务的能力的情况下,向所述第一终端发送共享失败响应消息,以指示所述第一终端继续执行所述第一业务。
在一示例性实施例中,在向所述第一终端返回共享成功响应消息之后,所述方法还包括:接收来自所述第一终端的业务共享终止请求;根据所述业务共享终止请求执行终止所述第二终端共享所述第一终端的所述第一业务的处理。
在一示例性实施例中,在根据所述业务共享终止请求执行终止所述第二终端共享所述第一终端的所述第一业务的处理之后,所述方法还包括:向所述第一终端发送共享终止成功响应消息,并开启所述第一终端中的所述第一业务;向所述第一终端发送共享终止失败响应消息,维持所述第二终端共享所述第一终端中的所述第一业务的状态。
在一示例性实施例中,所述方法还包括:接收来自所述第一终端的添加请求;根据所述添加请求执行在所述共享组中添加第三终端的处理;或者,接收来自所述第一终端的删除请求;根据所述删除请求执行在所述共享组中删除第四终端的处理。
在一示例性实施例中,在根据所述添加请求执行在所述共享组中添加第三终端的处理之后,所述方法还包括:向所述第一终端发送添加成功响应消息,其中,所述添加成功响应消息用于指示已在所述共享组中成功添加所述第三终端;向所述第一终端发送添加失败响应消息,其中,所述添加失败响应消息用于指示在所述共享组中添加所述第三终端失败。
在一示例性实施例中,在根据所述删除请求执行在所述共享组中删除第四终端的处理之后,所述方法还包括:向所述第一终端发送删除成功响应消息,其中,所述删除成功响应消息用于指示已成功删除所述共享组中的所述第四终端;向所述第一终端发送删除失败响应消息,其中,所述删除失败响应消息用于指示删除所述共享组中的所述第四终端失败。
在一示例性实施例中,所述业务共享请求中包括第一文本信息,在接收来自第一终端的业务共享请求之后,所述方法还包括:将所述第一文本信息显示在所述第二终端上。
在一示例性实施例中,所述共享终止请求中包括第二文本信息,在接收来自所述第一终端的业务共享终止请求之后,所述方法还包括:将所述第二文本信息显示在所述第二终端上。
在一示例性实施例中,所述添加请求中包括第三文本信息,在接收来自所述第一终端 的添加请求之后,所述方法还包括:将所述第三文本信息显示在所述第三终端上。
在一示例性实施例中,所述删除请求中包括第四文本信息,在接收来自所述第一终端的删除请求之后,所述方法还包括:将所述第四文本信息显示在所述第四终端上。
根据本公开的另一个实施例,提供了一种业务共享装置,包括:第一接收模块,用于接收输入的业务共享指示,其中,所述业务共享指示用于指示将第一终端的第一业务共享到所述第一终端所在的共享组中的第二终端上,所述共享组中包括三个以上终端,且各终端之间具备互相共享业务的能力;第一发送模块,用于在所述业务共享指示的触发下向网络侧发送业务共享请求,以请求所述网络侧将所述第一终端的第一业务共享给所述第二终端。
根据本公开的另一个实施例,提供了一种业务共享装置,包括:第二接收模块,用于接收来自第一终端的业务共享请求,其中,所述业务共享请求用于请求将所述第一终端的第一业务共享到所述第一终端所在的共享组中的第二终端上,所述共享组中包括三个以上终端,且各终端之间具备互相共享业务的能力;控制模块,用于在确定所述第二终端具备共享所述第一终端的所述第一业务的能力的情况下,根据所述业务共享请求控制所述第二终端共享所述第一终端的所述第一业务。
根据本公开的又一个实施例,还提供了一种存储介质,所述存储介质中存储有计算机程序,其中,所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本公开的又一个实施例,还提供了一种电子装置,包括存储器和处理器,所述存储器中存储有计算机程序,所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
通过本公开,共享组中的各个终端之间是可以相互之间进行业务共享的,也就是说,共享某一个终端的业务的终端不再固定,可以根据实际情况从共享组中灵活选择终端进行业务共享,可以解决相关技术中存在的终端的业务只能共享给固定的一个终端,从而导致业务共享效率低,用户体验差的问题,进而达到可以对终端的业务进行灵活共享,提高用户体验的效果。
附图说明
此处所说明的附图用来提供对本公开的进一步理解,构成本申请的一部分,本公开的示意性实施例及其说明用于解释本公开,并不构成对本公开的不当限定。在附图中:
图1是根据本公开实施例的一种业务共享方法的移动终端的硬件结构框图;
图2是根据本公开实施例的一种业务共享方法的流程图;
图3是根据本公开实施例的一种业务共享方法的流程图;
图4是根据本公开实施例的一种电话切换的示意图;
图5是根据本公开实施例提供的一种来电切换过程的流程图;
图6是根据本公开实施例提供的语音切换指令的结构表;
图7是根据本公开实施例提供的用户接收SETUP结构表;
图8是根据本公开实施例提供的一种短信/彩信切换过程的流程图;
图9是根据本公开实施例提供的一种取消短彩信共享关系的流程图;
图10是根据本公开实施例提供的一种共享应用的界面显示示意图;
图11是根据本公开实施例提供的一种语音切换提示框的示意图;
图12是根据本公开实施例提供的一种视频电话切换提示框的示意图;
图13是根据本公开实施例提供的一种短信转发提示框的示意图;
图14是根据本公开实施例提供的一种彩信转发提示框的示意图;
图15是根据本公开实施例提供的一种取消短信转发提示框的示意图;
图16是根据本公开实施例提供的一种取消彩信转发提示框的示意图;
图17是根据本公开实施例提供的一种添加共享电话提示框的示意图;
图18是根据本公开实施例的第一种共享装置的结构框图;
图19是根据本公开实施例的第二种共享装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开。需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是,本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象,而不必用于描述特定的顺序或先后次序。
实施例1
本申请实施例一所提供的方法实施例可以在移动终端、计算机终端或者类似的运算装置中执行。以运行在移动终端上为例,图1是本公开实施例的一种业务共享方法的移动终端的硬件结构框图。如图1所示,移动终端10可以包括一个或多个(图1中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)和用于存储数据的存储器104,在一示例性实施例中,上述移动终端还可以包括用于通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解,图1所示的结构仅为示意,其并不对上述移动终端的结构造成限定。例如,移动终端10还可包括比图1中所示更多或者更少的组件,或者具有与图1所示不同的配置。
存储器104可用于存储计算机程序,例如,应用软件的软件程序以及模块,如本公开实施例中的业务共享方法对应的计算机程序,处理器102通过运行存储在存储器104内的计算机程序,从而执行各种功能应用以及数据处理,即实现上述的方法。存储器104可包括高速随机存储器,还可包括非易失性存储器,如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中,存储器104可进一步包括相对于处理器102远程设置的存储器,这些远程存储器可以通过网络连接至移动终端10。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106用于经由一个网络接收或者发送数据。上述的网络示例性实例可包括移动终端10的通信供应商提供的无线网络。在一个实例中,传输装置106包括一个网络适配器(Network Interface Controller,简称为NIC),其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中,传输装置106可以为射频(Radio Frequency,简称为RF)模块,其用于通过无线方式与互联网进行通讯。
为使本公开的目的、技术方案和优点更加清楚,以下对本公开作进一步地详细说明。
实施例2
图2是根据本公开实施例的一种业务共享方法的流程图,如图2所示,该流程包括如下步骤:
步骤S202,接收输入的业务共享指示,其中,上述业务共享指示用于指示将第一终端的第一业务共享到第一终端所在的共享组中的第二终端上,共享组中包括三个以上终端,且各终端之间具备互相共享业务的能力;
步骤S204,在上述业务共享指示的触发下向网络侧发送业务共享请求,以请求网络侧将第一终端的第一业务共享给第二终端。
其中,执行上述操作的可以是上述的第一终端,例如,可以是实施例1中所示的终端。
通过上述步骤,共享组中的各个终端之间是可以相互之间进行业务共享的,也就是说,共享某一个终端的业务的终端不再固定,可以根据实际情况从共享组中灵活选择终端进行业务共享,可以解决相关技术中存在的终端的业务只能共享给固定的一个终端,从而导致业务共享效率低,用户体验差的问题,进而达到可以对终端的业务进行灵活共享,提高用户体验的效果。
在一个可选的实施例中,在上述业务共享指示的触发下向网络侧发送业务共享请求之后,上述方法还包括:接收来自网络侧的共享成功响应消息,根据共享成功响应消息终止第一终端中的所述第一业务;接收到来自网络侧的共享失败响应消息,根据共享失败响应消息在第一终端中继续执行第一业务。在本实施例中,当第一终端接收来自网络侧发送的共享成功响应消息,即,第一终端请求共享组中第二终端共享第一业务成功后,此时第二终端会执行第一终端的第一业务,则第一终端可以终止当前的第一业务;当第一终端接收来自网络侧发送的共享失败响应消息时,说明第一终端请求共享组中指定终端共享第一业务失败,此时,第一终端可以继续执行当前的第一业务。
在一个可选的实施例中,在接收来自网络侧的共享成功响应消息之后,所述方法还包括:接收输入的业务共享终止指示,其中,业务共享终止指示用于指示终止第二终端共享第一终端的所述第一业务;在业务共享终止指示的触发下向网络侧发送业务共享终止请求,以请求网络侧终止第二终端共享第一终端的第一业务。在本实施例中,当第一终端与共享组中其他终端共享第一业务成功后,第一终端还可以控制终止本次共享操作,也就是说,当第一终端接收到业务共享终止指示后,会向网络侧发送业务共享终止请求,请求网络侧 终止第二终端当前共享的第一终端的第一业务,结束与共享组中其他终端之间的共享操作。
在一个可选的实施例中,在上述业务共享终止指示的触发下向网络侧发送业务共享终止请求之后,上述方法还包括:接收来自网络侧的共享终止成功响应消息,根据共享终止成功响应消息开启第一终端中的第一业务;接收来自网络侧的共享终止失败响应消息,根据共享终止失败响应消息维持终止第一终端中的第一业务的状态。在本实施例中,当共享终止操作成功后,即第一终端与共享组中其他终端之间结束了第一业务的共享时,第一终端可以继续执行上述第一业务;若共享终止操作失败,为了保证业务的连续性,可以由第二终端继续执行第一终端共享过来的第一业务。
在一个可选的实施例中,上述方法还包括:接收输入的添加指示或删除指示,其中,所述添加指示用于指示在共享组中添加第三终端,删除指示用于指示删除共享组中的第四终端;在添加指示的触发下向网络侧发送添加请求,以请求网络侧在共享组中添加第三终端;或者,在删除指示的触发下向网络侧发送删除请求,以请求网络侧删除共享组中的第四终端。在本实施例中,若第一终端需要在共享组中添加终端,例如,添加上述的第三终端,则第一终端会向网络侧发送携带第三终端的相关信息(例如,标识信息)的添加请求,网络侧会根据相关判断条件(例如,第一终端和第三终端之间是否具备业务共享能力)来确定是否可以将第三终端添加到第一终端的共享组中;若第一终端请求删除共享组中的第四终端,会向网络侧发送删除请求,以请求取消共享关系。
在一个可选的实施例中,在上述添加指示的触发下向网络侧发送添加请求之后,上述方法还包括:接收来自网络侧的添加成功响应消息,根据添加成功响应消息在共享组中添加第三终端;接收来自网络侧的添加失败响应消息。在本实施例中,当第一终端向网络侧发送用于请求在共享组中添加第三终端的添加请求后,若接收来自网络侧反馈回来的添加成功响应消息,即可在共享组中成功添加第三用户,若接收的是添加失败响应消息,即此次请求建立共享关系失败,没有共享成功。
在一个可选的实施例中,在上述删除指示的触发下向网络侧发送删除请求之后,上述方法还包括:接收来自网络侧的删除成功响应消息,根据删除成功响应消息删除共享组中的第四终端。在本实施例中,当第一终端向网络侧发送删除第四终端的删除请求之后,若接收来自网络侧反馈回来的是删除成功响应消息,则说明可以删除共享组中的上述第四用户;反之,请求失败。
在一个可选的实施例中,上述业务共享请求中包括第一文本信息,其中,第一文本信息用于指示网络侧将第一文本信息显示在第二终端上。在本实施例中,第一终端向网络侧发送请求共享组中其他终端共享第一终端的第一业务时,还可以同时携带第一终端输入的文本信息,网络侧会将该文本信息发送给第二终端,并在第二终端上进行显示。
在一个可选的实施例中,上述共享终止请求中包括第二文本信息,其中,第二文本信息用于指示网络侧将第二文本信息显示在第二终端上。在本实施例中,当第一终端向网络侧发送共享终止请求时,可以携带第一终端输入的文本信息,网络侧会将该文本信息发送 给共享组中此时与第一终端之间已经建立了共享关系的第二终端,并在该第二终端上进行显示。
在一个可选的实施例中,上述添加请求中包括第三文本信息,其中,第三文本信息用于指示网络侧将第三文本信息显示在第三终端上。在本实施例中,当第一终端向网络侧发送与第三终端建立共享关系的添加请求时,可以携带第一终端输入的文本信息,网络侧会将该文本信息发送给第三终端,并在第三终端上进行显示。
在一个可选的实施例中,上述删除请求中包括第四文本信息,其中,第四文本信息用于指示网络侧将第四文本信息显示在第四终端上。在本实施例中,当第一终端向网络侧发送删除共享组中的第四终端的删除请求时,可以携带第一终端输入的文本信息,网络侧会将该文本信息发送给第四终端,并在第四终端上进行显示。
在一个可选的实施例中,在接收输入的业务共享指示之前,方法还包括:显示共享组中除第一终端之外的其他终端的使用状态。在本实施例中,因为共享组中有三个以上终端,当第一终端需要请求共享组中其他终端共享第一终端的第一业务时,第一终端需要查询其他终端的当前使用状态,判断共享组中哪些终端是处于空闲状态,为了保证业务共享成功,可以选中处于空闲态的终端进行业务共享。
实施例3
图3是根据本公开实施例的一种业务共享方法的流程图,如图3所示,该流程包括如下步骤:
步骤S302,接收来自第一终端的业务共享请求,其中,所述业务共享请求用于请求将所述第一终端的第一业务共享到所述第一终端所在的共享组中的第二终端上,所述共享组中包括三个以上终端,且各终端之间具备互相共享业务的能力;
步骤S304,在确定所述第二终端具备共享所述第一终端的所述第一业务的能力的情况下,根据所述业务共享请求控制所述第二终端共享所述第一终端的所述第一业务。
其中,执行上述操作的可以是网络侧(例如,基站)。
通过上述步骤,网络侧根据接收的业务共享请求,控制共享组中的各个终端之间建立业务共享操作,也就是说,通过网络侧共享某一个终端的业务的终端不再固定,可以根据实际情况从共享组中灵活选择终端进行业务共享,可以解决相关技术中存在的终端的业务只能共享给固定的一个终端,从而导致业务共享效率低,用户体验差的问题,进而达到可以对终端的业务进行灵活共享,提高用户体验的效果。
在一个可选的实施例中,在控制第二终端共享第一终端的第一业务之后,上述方法还包括:向第一终端返回共享成功响应消息,并终止所述第一终端中的第一业务。在本实施例中,当网络侧向第一终端发送共享成功响应消息,即,第一终端请求共享组中第二终端共享第一终端的第一业务成功之后,第二终端成功执行第一终端的第一业务,则第一终端会终止当前的第一业务。
在一个可选的实施例中,在接收来自第一终端的业务共享请求之后,上述方法还包括:在确定第二终端不具备共享第一终端的所述第一业务的能力的情况下,向第一终端发送共享失败响应消息,以指示第一终端继续执行第一业务。在本实施例中,若确定第二终端不具备共享第一终端的第一业务能力时,网络侧会向第一终端发送共享失败响应消息,即共享组中第二终端共享第一终端的第一业务失败,此时,第一终端可以继续执行当前的第一业务。
在一个可选的实施例中,在向第一终端返回共享成功响应消息之后,上述方法还包括:接收来自第一终端的业务共享终止请求;根据业务共享终止请求执行终止第二终端共享第一终端的第一业务的处理。在本实施例中,在网络侧向第一终端反馈共享组中其他终端共享第一业务成功后,若网络侧接收来自第一终端的共享终止请求,网络侧根据共享终止请求第二终端终止执行第一终端的第一业务,结束当前共享操作。
在一个可选的实施例中,在根据业务共享终止请求执行终止第二终端共享第一终端的第一业务的处理之后,上述方法还包括:向第一终端发送共享终止成功响应消息,并开启第一终端中的第一业务;向第一终端发送共享终止失败响应消息,维持第二终端共享第一终端中的第一业务的状态。在本实施例中,当网络侧接收来自第一终端请求的业务共享终止请求后,网络侧会向第一终端反馈响应消息,若反馈的是共享终止成功响应消息,则共享终止操作请求成功,第二终端终止共享第一终端的第一业务,第一终端可以继续执行第一业务;若反馈的是共享终止失败响应消息,则共享终止操作请求失败,网络侧会维持第二终端继续共享第一终端的第一业务的状态。
在一个可选的实施例中,上述方法还包括:接收来自第一终端的添加请求;根据添加请求执行在共享组中添加第三终端的处理;或者,接收来自第一终端的删除请求;根据删除请求执行在共享组中删除第四终端的处理。在本实施例中,若网络侧接收来自第一终端发送的在共享组中添加第三终端的添加请求,网络侧会根据相关判断条件(例如,第一终端和第三终端之间是否具备业务共享能力)来确定是否可以将第三终端添加到第一终端的共享组中;若网络侧接收来自第一终端请求删除共享组中的第四终端的删除请求,网络侧根据删除请求将共享组中的第四终端删除,取消共享关系。
在一个可选的实施例中,在根据添加请求执行在共享组中添加第三终端的处理之后,上述方法还包括:向第一终端发送添加成功响应消息,其中,添加成功响应消息用于指示已在共享组中成功添加第三终端;向第一终端发送添加失败响应消息,其中,添加失败响应消息用于指示在共享组中添加第三终端失败。在本实施例中,当网络侧接收来自第一终端请求在共享组中添加第三终端的添加请求之后,如果网络侧向第一终端发送的是添加成功响应消息,则用户可以在共享组中成功添加第三终端,若网络侧发送的是添加失败响应消息,即此次请求添加第三终端操作失败。
在一个可选的实施例中,在根据删除请求执行在共享组中删除第四终端的处理之后,上述方法还包括:向第一终端发送删除成功响应消息,其中,删除成功响应消息用于指示 已成功删除共享组中的第四终端;向第一终端发送删除失败响应消息,其中,删除失败响应消息用于指示删除共享组中的第四终端失败。在本实施例中,当网络侧接收来自第一终端发送删除第四终端的删除请求之后,若网络侧反馈的是删除成功响应消息,则第一终端可以删除共享组中第四终端;反之,请求失败。
在一个可选的实施例中,上述业务共享请求中包括第一文本信息,在接收来自第一终端的业务共享请求之后,上述方法还包括:将第一文本信息显示在第二终端上。在本实施例中,网络侧接收携带第一终端输入的文本信息的业务共享请求之后,网络侧会将该文本信息发送给共享组中第二终端,并控制在第四终端上进行显示。
在一个可选的实施例中,上述共享终止请求中包括第二文本信息,在接收来自第一终端的业务共享终止请求之后,上述方法还包括:将第二文本信息显示在第二终端上。在本实施例中,当网络侧接收携带第一终端输入的文本信息的共享终止请求之后,网络侧会将该文本信息发送给共享组中此时与第一终端之间建立共享操作的第二终端,并控制在第二终端上进行显示。
在一个可选的实施例中,上述添加请求中包括第三文本信息,在接收来自第一终端的添加请求之后,上述方法还包括:将第三文本信息显示在第三终端上。在本实施例中,当网络侧接收携带第一终端输入的文本信息的添加请求之后,网络侧会将该文本信息发送给共享组中的第三终端,并控制在第三终端上显示。
在一个可选的实施例中,上述删除请求中包括第四文本信息,在接收来自第一终端的删除请求之后,上述方法还包括:将第四文本信息显示在第四终端上。在本实施例中,当网络侧接收携带第一终端输入的文本信息的删除请求之后,网络侧会将该文本信息发送给共享组中的第四终端,并控制在第四终端上进行显示。
下面结合具体实施例对本公开进行详细介绍。
下面以具有UI界面的,且支持电话/短彩信的手机为例,对本公开进行说明:
在本实施例中,可以在手机中增加一个类似于“共享应用”的app。在应用中可以添加共享的电话号码,可直接从电话本中添加或者自己手动输入号码。若直接从电话本中选择号码添加,则应用中直接显示联系人姓名。若直接手动输入号码,能在电话本里匹配到联系人姓名则显示联系人姓名;若无法匹配到,则显示电话号码。在共享组中增加号码时,需要先得到对方同意。手机要向对方发送共享请求,对方如果同意,则共享应用里可成功添加,并且这个共享关系也会在网络侧存储一份。
如图4是根据本公开实施例的一种电话切换的示意图,如图4所示,
S401,A与B处于通话状态或者呼叫A。
S402,A发起切换请求,将通话切换至手机C;手机A向网络侧发起切换请求,请求C共享A电话业务。
S403,网络发送被叫给手机C;网络侧接收A的切换请求之后,网络侧在确定手机C具备共享业务的能力下,呼叫C,请求控制C共享手机A的业务。
S404,结束A和B之间的通话或者来电;当A请求C共享A的业务请求成功后,网络侧会提示A共享成功,并终止A和B之间的通话业务。
S405,呼叫C;电话切换成功后,手机C共享了A的业务,此时B呼叫C。
短/彩信业务与上述电话切换业务类似,比较简单,此处不再赘述。
本公开实施例中提供了在以某种关系,例如家庭,同事等,为单位的共享某些手机事件的方法。要实现该方法,可以在终端的用户界面上通过一个“共享应用”的app来实现,下面结合电话共享流程以及短彩信切换流程做进一步说明。
如图5所示为本公开实施例提供的一种来电切换过程的流程图,如图5所述,来电切换到某共享电话的过程,包括语音电话和视频电话两种情况,如图5所示,流程例如可包括:
步骤501:手机B呼叫手机A,A收到来电提示,或者A和B已经处于通话状态;
步骤502:A打开手机上的共享应用界面,选择共享号码C;
步骤503:手机A向网络发送切换请求,请求中携带来电号码B和切换号码C,若用户还有输入文本信息,切换请求中也会携带文本信息;
步骤504:网络收到切换请求,判断A与C之间是否有共享关系;若有,则进入步骤505,反之进入步骤509;
步骤505:网络给手机C发送来电通知,并通知A切换成功,A结束通话;
步骤506:用户A是否在共享应用里选择C时有输入文字信息,若有则进入步骤507,反之则进入步骤508;
步骤507:C手机收到B的来电提示,并在UI上提示C这是用户A切换过来的电话,流程结束。
步骤508:C手机收到B的来电提示,并在UI上提示C这是用户A切换过来的电话,且在来电界面显示A输入的文本信息,流程结束。
步骤509:网络拒绝该切换请求,并以:无共享关系这种理由通知A切换失败;
步骤510:A收到切换失败的消息,手机提示用户切换失败,且A依旧处于之前的来电或通话状态,流程结束。
通话既包含普通的语音通话,也包括volte(Voice over LTE,基于IMS的语音业务)通话,即数据域的通话。因为两者在信令上区别比较大,故以下将分开描述:
图6是本公开实施例提供的语音切换指令的结构表,针对CS域语音通话,对于图5中的A用户步骤503的切换指令,指令信令大致结构如如图6所示。
切换指令信令示例如下:
Figure PCTCN2018120801-appb-000001
Figure PCTCN2018120801-appb-000002
CS域语音通话,对于图5中的步骤508,C手机收到A切换过来的来电,其来电信息通过SETUP信令传递,但是需要在目前的SETUP信息中增加A的号码信息,使C能知道该来电是被A切换过来的。图7是本公开实施例提供的用户接收SETUP结构表,C用户收到的SETUP信令大致的结构如图7所示。
C用户收到的SETUP信令示例如下:
Figure PCTCN2018120801-appb-000003
Volte通话,对于图5中的A用户步骤503的切换指令,需要扩充RFC3261中的SIP指令,这里暂定扩充指令608(即,用608指代该扩充指令);根据RFC3261,6XX的指令集都是用户拒绝应答的类型。扩充的608指令类似于:
Figure PCTCN2018120801-appb-000004
Volte通话,对于图5中的步骤508,C手机收到A切换过来的来电,其来电信息通过INVITE消息传递,但是需要在目前的INVITE消息中通过关键字“P-Switched-Party-ID”增加A的号码信息,使C能知道该来电是被A切换过来的。如下是C用户收到的INVITE消息示例,下划线部分为扩充的信息:
Figure PCTCN2018120801-appb-000005
Figure PCTCN2018120801-appb-000006
如图8是根据本公开实施例提供的一种短信/彩信切换过程的流程图,如图8所述,将短/彩信切换到某共享号码的示例性流程为:
步骤801:用户A进入共享app,选择将短信/彩信转移到共享号码B;
步骤802:手机向网络发送短/彩信切换请求,请求中携带用户A的手机号码和共享号码B。若A还有输入文本信息,也携带文本信息;
步骤803:网络收到切换请求,判断号码AB之间是否有共享关系?若有,则进入步骤804,反之进入步骤806;
步骤804:网络给B发送切换通知,若A有输入文本信息,也会携带文本信息。同时通知用户A切换成功。至此之后发给A的短/彩信就会直接发给B;
步骤805:手机通知用户B:用户A将短/彩信转移到此手机,流程结束。
步骤806:网络拒接该切换请求,并以:无共享关系这种理由通知A切换失败;
步骤807:A收到切换失败的消息,手机提示用户切换失败。发给A的短/彩信仍然会发到A的号码上,流程结束。
电话相关的共享功能都是来电或者通话中的操作,即这种共享切换是一次性的。但是短/彩信的共享切换确不是这样,只要切换成功,则用户A的短/彩信就会一直用给共享号码。所以必须还得有一个取消短/彩信共享关系的过程。如图9所示为本公开实施例提供的一种取消短/彩信共享关系的流程图,将短/彩信取消与某号码的共享关系过程,如图9所示流程例如可包括:
步骤901:用户A进入共享app,选择将号码B的短信/彩信共享关系取消;
步骤902:手机向网络发送短/彩信取消共享请求,请求中携带用户A的手机号码和共享号码B。若A还有输入文本信息,也携带文本信息;
步骤903:网络收到取消共享请求,判断号码AB之间是否有共享关系,若有,则进入步骤904,反之进入步骤906;
步骤904:网络侧删除A与B之间的共享关系,给B发送取消共享通知,若A有输入文本信息,也会携带文本信息,并通知A取消成功;
步骤905:手机通知B:用户A已经取消了短/彩信共享,流程结束。
步骤906:网络拒接该切换请求,并以:无共享关系这种理由通知A取消失败;
步骤907:A收到取消失败的消息,手机提示用户取消失败。发给A的短/彩信仍然会发到B的号码上,流程结束。
本公开提供了在以某种关系,例如家庭,同事等,为单位的共享某些手机事件的方法。这种共享关系的实现在终端需要有一个界面,可以通过一个共享应用来实现。如图10是根据本公开实施例提供的一种共享应用的界面显示示意图,如图10所示,假设共享应用中至少有四个用户终端,还可以继续添加更多的手机号码,共享应用中可以共享语音电话、视频电话、短信、彩信……等业务,显示手机号码1、2、3、4用户的使用状态,若手机号码1和3处于待机状态,手机号码2处于通话中,手机号码4处于关机状态,那么此时,用户可以从手机号码1和3中任一选一个请求共享指定业务。
图11是根据本公开实施例提供的一种语音切换提示框的示意图,若用户点击手机号码1的语音电话部分,则在原有界面上弹出一个提示框,如图11所示:为了避免误操作的产生,所以还是需要有个确认框。且在该确认框里,还可以继续输入文本信息,该信息将会在手机号码1的来电界面显示出来,给手机1用户一些提示信息。
图12是根据本公开实施例提供的一种视频电话切换提示框的示意图,若点击手机号码1的视频电话部分,则在原有界面上弹出一个提示框,如图12所示:同样是为了避免误操作,界面上会显示一个确认框,该确认框还可以继续输入文本信息,网络侧会将该文本信息发送至手机号码1中的来电显示界面上。
若用户已经将短信/彩信切换到某共享号码上了,则在UI上会有一个共享中的提示,如图10所示;若没有,则没有共享中的提示出现。
图13是根据本公开实施例提供的一种短信转发提示框的示意图,如图13所示,若用户与手机号码1没有共享短信,则点击手机号码1的短信部分,则在原有界面上弹出一个提示框。
图14是根据本公开实施例提供的一种彩信转发提示框的示意图,如图14所示,若用户与手机号码1没有共享彩信,则点击手机号码1的彩信部分,则在原有界面上弹出一个提示框。
图15是根据本公开实施例提供的一种取消短信转发提示框的示意图,若用户与手机号码1已经处于共享短信状态,用户需要终止共享业务,则点击手机号码1的短信部分,则在原有界面上弹出一个提示框,如图15所示,在该确认框中提示是否需要取消当前业务,用户还可以输入文本信息,网络侧会控制该文本信息发送至手机号码1。
图16是根据本公开实施例提供的一种取消彩信转发提示框的示意图,如图16所示,若用户与手机号码1已经共享彩信,则点击手机号码1的彩信部分,则在原有界面上弹出一个提示框,此处与取消短信共享业务类似,不再赘述。
若点击+添加号码,则在原有界面上弹出一个提示框,图17是根据本公开实施例提供的一种添加共享电话提示框的示意图。
如图17所示,若用户需要点击添加共享用户,则手机将会把共享请求发送给网络,其中携带共享电话号码,如果用户需要输入文本信息,也可以将文本信息一并发给网络,网络会将相关信息发送给共享号码用户,在得到对方同意之后,完成共享过程。手机UI 提示添加成功。网络侧也会存一份该用户的共享号码列表。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端设备(可以是手机,计算机,服务器,或者网络设备等)执行本公开各个实施例所述的方法。
实施例4
在本实施例中还提供了第一种业务共享装置,该装置用于实现上述实施例及优选实施方式,已经进行过说明的不再赘述。如以下所使用的,术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现,但是硬件,或者软件和硬件的组合的实现也是可能并被构想的。
图18是根据本公开实施例的第一种共享装置的结构框图,该装置可以应用于终端中,例如,应用于第一终端中,如图18所示,该装置包括:第一接收模块182,用于接收输入的业务共享指示,其中,业务共享指示用于指示将第一终端的第一业务共享到第一终端所在的共享组中的第二终端上,共享组中包括三个以上终端,且各终端之间具备互相共享业务的能力;第一发送模块184,连接至上述第一接收模块182,用于在业务共享指示的触发下向网络侧发送业务共享请求,以请求网络侧将第一终端的第一业务共享给第二终端。
在一个可选的实施例中,该装置还用于:在业务共享指示的触发下向网络侧发送业务共享请求之后,接收来自网络侧的共享成功响应消息,根据共享成功响应消息终止第一终端中的第一业务;接收到来自网络侧的共享失败响应消息,根据共享失败响应消息在第一终端中继续执行第一业务。
在一个可选的实施例中,该装置还用于:在接收来自网络侧的共享成功响应消息之后,接收输入的业务共享终止指示,其中,业务共享终止指示用于指示终止第二终端共享第一终端的第一业务;在业务共享终止指示的触发下向网络侧发送业务共享终止请求,以请求网络侧终止第二终端共享第一终端的第一业务。
在一个可选的实施例中,该装置还用于:在业务共享终止指示的触发下向网络侧发送业务共享终止请求之后,接收来自网络侧的共享终止成功响应消息,根据共享终止成功响应消息开启第一终端中的第一业务;接收来自网络侧的共享终止失败响应消息,根据共享终止失败响应消息维持终止第一终端中的第一业务的状态。
在一个可选的实施例中,该装置还用于:接收输入的添加指示或删除指示,其中,添加指示用于指示在共享组中添加第三终端,删除指示用于指示删除共享组中的第四终端;在添加指示的触发下向网络侧发送添加请求,以请求网络侧在共享组中添加第三终端;或者,在删除指示的触发下向网络侧发送删除请求,以请求网络侧删除共享组中的第四终端。
在一个可选的实施例中,该装置还用于:在添加指示的触发下向网络侧发送添加请求之后,接收来自网络侧的添加成功响应消息,根据添加成功响应消息在共享组中添加第三终端;接收来自网络侧的添加失败响应消息。
在一个可选的实施例中,该装置还用于:在删除指示的触发下向网络侧发送删除请求之后,接收来自网络侧的删除成功响应消息,根据删除成功响应消息删除共享组中的第四终端。
在一个可选的实施例中,业务共享请求中包括第一文本信息,其中,第一文本信息用于指示网络侧将第一文本信息显示在第二终端上。
在一个可选的实施例中,共享终止请求中包括第二文本信息,其中,第二文本信息用于指示网络侧将第二文本信息显示在第二终端上。
在一个可选的实施例中,添加请求中包括第三文本信息,其中,第三文本信息用于指示网络侧将第三文本信息显示在第三终端上。
在一个可选的实施例中,删除请求中包括第四文本信息,其中,第四文本信息用于指示网络侧将第四文本信息显示在第四终端上。
在一个可选的实施例中,该装置还用于:在接收输入的业务共享指示之前,显示共享组中除第一终端之外的其他终端的使用状态。
实施例5
图19是根据本公开实施例的第二种共享装置的结构框图,该装置可以应用于网络侧,例如,基站中。如图19所示,包括第二接收模块192,用于接收来自第一终端的业务共享请求,其中,业务共享请求用于请求将第一终端的第一业务共享到第一终端所在的共享组中的第二终端上,共享组中包括三个以上终端,且各终端之间具备互相共享业务的能力;控制模块194,连接至上述第二接收模块192,用于在确定第二终端具备共享第一终端的第一业务的能力的情况下,根据业务共享请求控制第二终端共享第一终端的第一业务。
在一个可选的实施例中,该装置还用于:在控制第二终端共享第一终端的第一业务之后,向第一终端返回共享成功响应消息,并终止第一终端中的第一业务。
在一个可选的实施例中,该装置还用于:在接收来自第一终端的业务共享请求之后,在确定第二终端不具备共享第一终端的第一业务的能力的情况下,向第一终端发送共享失败响应消息,以指示第一终端继续执行第一业务。
在一个可选的实施例中,该装置还用于:在向第一终端返回共享成功响应消息之后,接收来自第一终端的业务共享终止请求;根据业务共享终止请求执行终止第二终端共享第一终端的第一业务的处理。
在一个可选的实施例中,该装置还用于:在根据业务共享终止请求执行终止第二终端共享第一终端的第一业务的处理之后,向第一终端发送共享终止成功响应消息,并开启第一终端中的第一业务;向第一终端发送共享终止失败响应消息,维持第二终端共享第一终 端中的第一业务的状态。
在一个可选的实施例中,该装置还用于:接收来自第一终端的添加请求;根据添加请求执行在共享组中添加第三终端的处理;或者,接收来自第一终端的删除请求;根据删除请求执行在共享组中删除第四终端的处理。
在一个可选的实施例中,该装置还用于:在根据添加请求执行在共享组中添加第三终端的处理之后,向第一终端发送添加成功响应消息,其中,添加成功响应消息用于指示已在共享组中成功添加第三终端;向第一终端发送添加失败响应消息,其中,添加失败响应消息用于指示在共享组中添加第三终端失败。
在一个可选的实施例中,该装置还用于:在根据删除请求执行在共享组中删除第四终端的处理之后,向第一终端发送删除成功响应消息,其中,删除成功响应消息用于指示已成功删除共享组中的第四终端;向第一终端发送删除失败响应消息,其中,删除失败响应消息用于指示删除共享组中的第四终端失败。
在一个可选的实施例中,业务共享请求中包括第一文本信息,该装置还用于:在接收来自第一终端的业务共享请求之后,将第一文本信息显示在第二终端上。
在一个可选的实施例中,共享终止请求中包括第二文本信息,该装置还用于:在接收来自第一终端的业务共享终止请求之后,将第二文本信息显示在第二终端上。
在一个可选的实施例中,添加请求中包括第三文本信息,该装置还用于:在接收来自第一终端的添加请求之后,将第三文本信息显示在第三终端上。
在一个可选的实施例中,删除请求中包括第四文本信息,该装置还用于:在接收来自第一终端的删除请求之后,将第四文本信息显示在第四终端上。
需要说明的是,上述各个模块是可以通过软件或硬件来实现的,对于后者,可以通过以下方式实现,但不限于此:上述模块均位于同一处理器中;或者,上述各个模块以任意组合的形式分别位于不同的处理器中。
本公开的实施例还提供了一种存储介质,该存储介质中存储有计算机程序,其中,该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
在一示例性实施例中,在本实施例中,上述存储介质可以包括但不限于:U盘、只读存储器(Read-Only Memory,简称为ROM)、随机存取存储器(Random Access Memory,简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本公开的实施例还提供了一种电子装置,包括存储器和处理器,该存储器中存储有计算机程序,该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
在一示例性实施例中,上述电子装置还可以包括传输设备以及输入输出设备,其中,该传输设备和上述处理器连接,该输入输出设备和上述处理器连接。
显然,本领域的技术人员应该明白,上述的本公开的各模块或各步骤可以用通用的计算装置来实现,它们可以集中在单个的计算装置上,或者分布在多个计算装置所组成的网 络上,在一示例性实施例中,它们可以用计算装置可执行的程序代码来实现,从而,可以将它们存储在存储装置中由计算装置来执行,并且在某些情况下,可以以不同于此处的顺序执行所示出或描述的步骤,或者将它们分别制作成各个集成电路模块,或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样,本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已,并不用于限制本公开,对于本领域的技术人员来说,本公开可以有各种更改和变化。凡在本公开的原则之内,所作的任何修改、等同替换、改进等,均应包含在本公开的保护范围之内。
工业实用性
根据本公开提供的业务共享方案,共享某一个终端的业务的终端不再固定,可以根据实际情况从共享组中灵活选择终端进行业务共享,可以解决相关技术中存在的终端的业务只能共享给固定的一个终端,从而导致业务共享效率低,用户体验差的问题,进而达到可以对终端的业务进行灵活共享,提高用户体验的效果。

Claims (20)

  1. 一种业务共享方法,包括:
    接收输入的业务共享指示,其中,所述业务共享指示用于指示将第一终端的第一业务共享到所述第一终端所在的共享组中的第二终端上,所述共享组中包括三个以上终端,且各终端之间具备互相共享业务的能力;
    在所述业务共享指示的触发下向网络侧发送业务共享请求,以请求所述网络侧将所述第一终端的第一业务共享给所述第二终端。
  2. 根据权利要求1所述的方法,其中,在所述业务共享指示的触发下向网络侧发送业务共享请求之后,所述方法还包括:
    接收来自所述网络侧的共享成功响应消息,根据所述共享成功响应消息终止所述第一终端中的所述第一业务;
    接收到来自所述网络侧的共享失败响应消息,根据所述共享失败响应消息在所述第一终端中继续执行所述第一业务。
  3. 根据权利要求2所述的方法,其中,在接收来自所述网络侧的共享成功响应消息之后,所述方法还包括:
    接收输入的业务共享终止指示,其中,所述业务共享终止指示用于指示终止所述第二终端共享所述第一终端的所述第一业务;
    在所述业务共享终止指示的触发下向所述网络侧发送业务共享终止请求,以请求所述网络侧终止所述第二终端共享所述第一终端的所述第一业务。
  4. 根据权利要求3所述的方法,其中,在所述业务共享终止指示的触发下向所述网络侧发送业务共享终止请求之后,所述方法还包括:
    接收来自所述网络侧的共享终止成功响应消息,根据所述共享终止成功响应消息开启所述第一终端中的所述第一业务;
    接收来自所述网络侧的共享终止失败响应消息,根据所述共享终止失败响应消息维持终止所述第一终端中的所述第一业务的状态。
  5. 根据权利要求1所述的方法,其中,所述方法还包括:
    接收输入的添加指示或删除指示,其中,所述添加指示用于指示在所述共享组中添加第三终端,所述删除指示用于指示删除所述共享组中的第四终端;
    在所述添加指示的触发下向所述网络侧发送添加请求,以请求所述网络侧在所述共享组中添加所述第三终端;或者,在所述删除指示的触发下向所述网络侧发送删除请求,以请求所述网络侧删除所述共享组中的所述第四终端。
  6. 根据权利要求5所述的方法,其中,
    在所述添加指示的触发下向所述网络侧发送添加请求之后,所述方法还包括:
    接收来自所述网络侧的添加成功响应消息,根据所述添加成功响应消息在所述共享组 中添加所述第三终端;
    接收来自所述网络侧的添加失败响应消息,
    或者,在所述删除指示的触发下向所述网络侧发送删除请求之后,所述方法还包括:
    接收来自所述网络侧的删除成功响应消息,根据所述删除成功响应消息删除所述共享组中的所述第四终端。
  7. 根据权利要求1至6中任一项所述的方法,其中,所述业务共享请求中包括第一文本信息,其中,所述第一文本信息用于指示所述网络侧将所述第一文本信息显示在所述第二终端上。
  8. 一种业务共享方法,包括:
    接收来自第一终端的业务共享请求,其中,所述业务共享请求用于请求将所述第一终端的第一业务共享到所述第一终端所在的共享组中的第二终端上,所述共享组中包括三个以上终端,且各终端之间具备互相共享业务的能力;
    在确定所述第二终端具备共享所述第一终端的所述第一业务的能力的情况下,根据所述业务共享请求控制所述第二终端共享所述第一终端的所述第一业务。
  9. 根据权利要求8所述的方法,其中,在控制所述第二终端共享所述第一终端的所述第一业务之后,所述方法还包括:
    向所述第一终端返回共享成功响应消息,并终止所述第一终端中的所述第一业务。
  10. 根据权利要求8所述的方法,其中,在接收来自第一终端的业务共享请求之后,所述方法还包括:
    在确定所述第二终端不具备共享所述第一终端的所述第一业务的能力的情况下,向所述第一终端发送共享失败响应消息,以指示所述第一终端继续执行所述第一业务。
  11. 根据权利要求9所述的方法,其中,在向所述第一终端返回共享成功响应消息之后,所述方法还包括:
    接收来自所述第一终端的业务共享终止请求;
    根据所述业务共享终止请求执行终止所述第二终端共享所述第一终端的所述第一业务的处理。
  12. 根据权利要求11所述的方法,其中,在根据所述业务共享终止请求执行终止所述第二终端共享所述第一终端的所述第一业务的处理之后,所述方法还包括:
    向所述第一终端发送共享终止成功响应消息,并开启所述第一终端中的所述第一业务;
    向所述第一终端发送共享终止失败响应消息,维持所述第二终端共享所述第一终端中的所述第一业务的状态。
  13. 根据权利要求8所述的方法,其中,所述方法还包括:
    接收来自所述第一终端的添加请求;根据所述添加请求执行在所述共享组中添加第三终端的处理;或者,
    接收来自所述第一终端的删除请求;根据所述删除请求执行在所述共享组中删除第四 终端的处理。
  14. 根据权利要求13所述的方法,其中,在根据所述添加请求执行在所述共享组中添加第三终端的处理之后,所述方法还包括:
    向所述第一终端发送添加成功响应消息,其中,所述添加成功响应消息用于指示已在所述共享组中成功添加所述第三终端;
    向所述第一终端发送添加失败响应消息,其中,所述添加失败响应消息用于指示在所述共享组中添加所述第三终端失败。
  15. 根据权利要求13所述的方法,其中,在根据所述删除请求执行在所述共享组中删除第四终端的处理之后,所述方法还包括:
    向所述第一终端发送删除成功响应消息,其中,所述删除成功响应消息用于指示已成功删除所述共享组中的所述第四终端;
    向所述第一终端发送删除失败响应消息,其中,所述删除失败响应消息用于指示删除所述共享组中的所述第四终端失败。
  16. 根据权利要求8至15中任一项所述的方法,其中,所述业务共享请求中包括第一文本信息,在接收来自第一终端的业务共享请求之后,所述方法还包括:
    将所述第一文本信息显示在所述第二终端上。
  17. 一种业务共享装置,包括:
    第一接收模块,用于接收输入的业务共享指示,其中,所述业务共享指示用于指示将第一终端的第一业务共享到所述第一终端所在的共享组中的第二终端上,所述共享组中包括三个以上终端,且各终端之间具备互相共享业务的能力;
    第一发送模块,用于在所述业务共享指示的触发下向网络侧发送业务共享请求,以请求所述网络侧将所述第一终端的第一业务共享给所述第二终端。
  18. 一种业务共享装置,包括:
    第二接收模块,用于接收来自第一终端的业务共享请求,其中,所述业务共享请求用于请求将所述第一终端的第一业务共享到所述第一终端所在的共享组中的第二终端上,所述共享组中包括三个以上终端,且各终端之间具备互相共享业务的能力;
    控制模块,用于在确定所述第二终端具备共享所述第一终端的所述第一业务的能力的情况下,根据所述业务共享请求控制所述第二终端共享所述第一终端的所述第一业务。
  19. 一种存储介质,所述存储介质中存储有计算机程序,其中,所述计算机程序被设置为运行时执行所述权利要求1至7任一项中所述的方法,或者执行权利要求8至16任一项中所述的方法。
  20. 一种电子装置,包括存储器和处理器,其中,所述存储器中存储有计算机程序,所述处理器被设置为运行所述计算机程序以执行所述权利要求1至7任一项中所述的方法,或者执行权利要求8至16任一项中所述的方法。
PCT/CN2018/120801 2018-01-29 2018-12-13 业务共享方法、装置、存储介质及电子装置 WO2019144720A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810085457.5A CN108206993B (zh) 2018-01-29 2018-01-29 业务共享方法、装置、存储介质及电子装置
CN201810085457.5 2018-01-29

Publications (1)

Publication Number Publication Date
WO2019144720A1 true WO2019144720A1 (zh) 2019-08-01

Family

ID=62605678

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/120801 WO2019144720A1 (zh) 2018-01-29 2018-12-13 业务共享方法、装置、存储介质及电子装置

Country Status (2)

Country Link
CN (1) CN108206993B (zh)
WO (1) WO2019144720A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108206993B (zh) * 2018-01-29 2022-04-29 中兴通讯股份有限公司 业务共享方法、装置、存储介质及电子装置
CN115243401A (zh) * 2021-04-22 2022-10-25 展讯通信(上海)有限公司 业务处理方法、装置、系统、可读取存储介质和电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090270081A1 (en) * 2008-01-21 2009-10-29 Ji-Hye Lee Method for suspending and resuming content transmission/reception
CN102394992A (zh) * 2011-11-07 2012-03-28 华为技术有限公司 一种终端通话切换方法和装置
CN102780678A (zh) * 2011-05-10 2012-11-14 华为终端有限公司 共享内容的方法和设备
CN105245741A (zh) * 2015-09-28 2016-01-13 努比亚技术有限公司 通话转移方法及装置
CN108206993A (zh) * 2018-01-29 2018-06-26 中兴通讯股份有限公司 业务共享方法、装置、存储介质及电子装置

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6915136B2 (en) * 2000-11-10 2005-07-05 Ntt Docomo, Inc. Mobile communication method and mobile communication system
JP3682767B2 (ja) * 2000-12-20 2005-08-10 株式会社エヌ・ティ・ティ・ドコモ 転送制御システム、転送制御方法、及び、転送制御端末
CN1863250A (zh) * 2005-05-23 2006-11-15 华为技术有限公司 一种号码绑定方法及采用该绑定方法进行呼叫的方法
CN101188834B (zh) * 2006-11-22 2010-12-22 Nec卡西欧移动通信株式会社 电子装置和呈现通信系统
CN101711019A (zh) * 2009-12-09 2010-05-19 中兴通讯股份有限公司 一种自动呼叫转移方法及装置
CN103139723B (zh) * 2011-11-30 2016-03-16 中国联合网络通信集团有限公司 多媒体消息信息处理方法和系统以及设备
CN102892072B (zh) * 2012-11-20 2015-06-17 北京邮电大学 一种基于人群协同的呼叫转移系统及其方法
CN103152715A (zh) * 2013-03-16 2013-06-12 唐启鹏 一种在移动终端间对语音通话转发的方法
FR3006531A1 (fr) * 2013-05-31 2014-12-05 France Telecom Procede et dispositif correspondant de gestion de l'etablissement d'une communication entre un terminal appelant et un groupe de terminaux partageant une meme identite publique
CN105898724B (zh) * 2015-01-26 2019-12-17 中国移动通信集团公司 一种信息处理方法及终端
CN105228118B (zh) * 2015-09-28 2019-01-04 小米科技有限责任公司 呼叫转移方法、装置和终端设备
US9658817B2 (en) * 2015-10-15 2017-05-23 Optim Corporation Screen sharing terminal, method of screen sharing, and program for screen sharing terminal
CN106686542B (zh) * 2015-11-06 2020-02-21 中国移动通信集团设计院有限公司 一种呼叫处理的方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090270081A1 (en) * 2008-01-21 2009-10-29 Ji-Hye Lee Method for suspending and resuming content transmission/reception
CN102780678A (zh) * 2011-05-10 2012-11-14 华为终端有限公司 共享内容的方法和设备
CN102394992A (zh) * 2011-11-07 2012-03-28 华为技术有限公司 一种终端通话切换方法和装置
CN105245741A (zh) * 2015-09-28 2016-01-13 努比亚技术有限公司 通话转移方法及装置
CN108206993A (zh) * 2018-01-29 2018-06-26 中兴通讯股份有限公司 业务共享方法、装置、存储介质及电子装置

Also Published As

Publication number Publication date
CN108206993B (zh) 2022-04-29
CN108206993A (zh) 2018-06-26

Similar Documents

Publication Publication Date Title
US10171657B1 (en) System and method for omni-channel notification and selection
US8649819B2 (en) Mobile phone integration with a private branch exchange in a distributed telephony system
EP1997326B1 (en) System and method for employing state information to enhance network functionality
US10230847B1 (en) Conferencing and meeting implementations with advanced features
CN106576227B (zh) Dmr/pdt集群和dmr/pdt常规互联互通的方法、装置及系统
JPWO2009084528A1 (ja) サーバ装置、及び、メッセージ送信方法
US7899172B2 (en) Call forwarding systems, methods and network devices
WO2019144720A1 (zh) 业务共享方法、装置、存储介质及电子装置
CN103024687A (zh) 用于建立即时通信的方法和设备
JP2006101528A (ja) ループ通信チャネルの検出
US8639222B2 (en) Message transmission method and message transmission system
US8630632B2 (en) Managing mobile communication identity
WO2015017179A1 (en) Method for responding to push notification based communication request
US20110293085A1 (en) Private Branch Exchange
EP3973692B1 (en) Systems and methods for handling camped incoming telephone calls
JP2018182474A (ja) Ip電話ネットワークシステム、親ゲートウェイ、子ゲートウェイ、およびip電話システム
US20140269440A1 (en) Systems and methods for handling incoming communications directed to a telephony device
JP2021182710A (ja) 中継装置、通信システム、中継方法及びプログラム
US20170374691A1 (en) Systems and methods for managing communication sessions at endpoints accessible via more than one network
US20220321696A1 (en) Presence based presentation of call identification information
CA2769369C (en) Managing mobile communication identity
JP2021136513A (ja) 通話システム、通話端末、通信制御装置、通話プログラム、通信制御プログラム、及び、通話方法
CN113630509A (zh) 一种ip电话的呼叫系统及呼叫方法
US20200153970A1 (en) Calling-party identifier selection in a contact center based on previous association with a called party
US20140274017A1 (en) Systems and methods for handling incoming communications directed to a telephony device

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: 18902650

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

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

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 03/12/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18902650

Country of ref document: EP

Kind code of ref document: A1