Method for Operating Application Providing Group Call Service Using Mobile Voice over Internet Protocol
Claim Score by NHIP
Abstract
Disclosed is a method for operating an application providing a group call service using mobile voice over internet protocol (mVoIP). According to one embodiment, a request signal for a group call is received, and regardless of participation in the corresponding the group call, meta information for the group chat room corresponding to the group call can be received from a server. The meta information can comprise at least the group call connection status for each member of the group chat room.

Term
7.7 yearsto projected expiry
Projected expiry 15 June 2034, counted from filing; an application has no term until it is granted.
- Priority
- Filed
- Published
- Today
- Projected expiry
19 claims: 3 independent, 16 dependent
- 1Broadest claimClaim Score 70, broad(NHIP)A method of operating an application providing a group call service using a mobile voice over Internet protocol (mVolP), the method comprising:receiving a request signal for a group call;and receiving meta information for a group call chat room corresponding to the group call from a server, regardless of participation in the group call, wherein the meta information at least comprises a group call connection status of each of members in the group call chat room.
- 11A method of operating an application providing a group call service using a mobile voice over Internet protocol (mVolP), the method comprising:providing an interface used to transmit a request signal for a group call to members in a group chat room;determining group call members who are able to participate in the group call among the members, in response to an input to transmit the request signal being received;creating a new group call chat room comprising the group call members, when the members are different from the group call members;and transmitting the request signal in the new group call chat room.
- 17A mobile terminal for providing a group call service using a mobile voice over Internet protocol (mVolP), the mobile terminal comprising:a receiver, wherein the receiver comprises: a request signal receiver to receive a request signal for a group call;and a meta information receiver to receive meta information for a group call chat room corresponding to the group call from a server, regardless of participation in the group call, and wherein the meta information at least comprises a group call connection status of each of members in the group call chat room.
Independent claims3
165 paragraphs in 5 sections, as filed
TECHNICAL FIELD
0001The following description relates to a method of operating an application providing a group call service using a mobile voice over Internet protocol (mVoIP).
BACKGROUND ART
0002Recently, a technology of constructing a mobile voice over IP (mVoIP) network through interworking with an Internet protocol (IP) multimedia subsystem (IMS) network and a portable Internet, and of providing a portable Internet subscriber with an mVoIP-based call service (for example, a voice call service or a video call service) as an additional service, has been developed. The portable Internet may include, for example, a wireless broadband Internet (WiBro), a mobile Worldwide Interoperability for Microwave Access (WiMAX), a 3rd generation partnership project (3GPP) long term evolution (LTE), a 4<sup>th </sup>generation (4G) LTE, and the like.
0003An mVoIP is a technology of providing a VoIP service of a voice call level based on a data service of a portable Internet network. VoIP services may be classified into stationary VoIP services and mVoIP services, based on a mobility. In other words, a VoIP service based on a portable Internet, for example a mobile communication network, may be classified as an mVoIP service.
0004An instant message service may support an instant (real-time) text communication between at least two people, using a network, for example, the Internet. An instant messenger is a client to relay instant messages. The instant message service may enable real-time conversations and accordingly, differs from an electronic mail (e-mail) service. A conversation message may be transmitted every time people enter in a line and accordingly, the instant message service is similar to a telephone conversation rather than exchanging letters.
0005In addition, a group call service may enable a voice call between at least three participants at a time, and may include, for example, a conference call.
DISCLOSURE OF INVENTION
Technical Solutions
0006According to an aspect of the present invention, there is provided a method of operating an application providing a group call service using a mobile voice over Internet protocol (mVoIP), the method including: receiving a request signal for a group call; and receiving meta information for a group call chat room corresponding to the group call from a server, regardless of participation in the group call, wherein the meta information at least includes a group call connection status of each of members in the group call chat room.
0007The method may further include providing an interface used to receive an input on whether to participate in the group call now, in response to the request signal being received, automatically entering the group call chat room, in response to an input to participate in the group call now being received, and providing information regarding the group call using an indicator provided in the group call chat room, the information regarding the group call including the group call connection status.
0008The method may further include not automatically entering the group call chat room, in response to an input to participate in the group call later being received, and providing an interface enabling participation in the group call without a need to receive again the request signal when entering the group call chat room later.
0009The request signal may include request caller information and request receiver information, the request caller information may include information associated with a single request caller, and the request receiver information may include information associated with at least two request receivers.
0010The group call connection status may include a “connecting” status, a “connected” status, a “terminated” status, and an “impossible connection” status, and the server may change the group call connection status to the “terminated” status when the “connecting” status continues during a predetermined period of time.
0011The information regarding the group call may further include a profile photo of each of the members, and the providing of the information regarding the group call may include adjusting a dimness of the profile photo based on the group call connection status.
0012The meta information may further include at least one of a period of time of participation in the group call, a network connection status for the group call, and a member requesting the group call.
0013The method may further include providing at least one of an interface used to activate at least one of a voice change function, a mute function and a speakerphone function using an indicator provided in the group call chat room, an interface used to terminate the group call, and an interface used to fold or unfold the indicator.
0014The method may further include terminating the group call, in response to an input to terminate the group call being received, and providing an interface enabling participation in the group call without a need to receive again the request signal, and the information regarding the group call, using the indicator.
0015The terminating of the group call may include inputting a predetermined message associated with termination of the group call to the group call chat room.
0016The method may further include receiving a group call termination signal from the server, and deactivating a group call-related function provided in the group call chat room, in response to the group call termination signal being received. The server may transmit the group call termination signal based on a number of members currently participating in the group call.
0017The method may further include determining whether the group call chat room is already included in a chat room list, and adding the group call chat room to the chat room list based on a determination that the group call chat room is not included in the chat room list.
0018The method may further include providing an interface used to receive an input on whether to accept the request signal, in response to the request signal being received, entering the group call chat room, in response to an input to accept the request signal being received, providing information regarding the group call using an indicator provided in the group call chat room, the information regarding the group call including the group call connection status, providing an interface used to receive an input on whether to participate in the group call now, using the indicator, and providing an interface enabling participation in the group call without a need to receive again the request signal, in response to an input to participate in the group call later being received.
0019The method may further include deactivating at least one predetermined function associated with the group call chant room during the group call.
0020The method may further include at least one of playing a first preset notification when a member currently participating in the group call terminates the group call, playing a second preset notification when a member not participating in the group call participates in the group call, playing a third preset notification when a new message is input to the group call chat room, playing a fourth preset notification when a new message is input to another chat room, and playing a fifth preset notification when the request signal is received.
0021The method may further include providing a warning message saying that a group chat is to be terminated when leaving the group call chat room, in response to an input to leave the group call chat room being received during participation in the group call.
0022The method may further include providing information indicating that a participant is participating in the group call to an indicator associated with a background mode, in response to a reception of an input to allow the application to be executed in the background mode during participation in the group call.
0023According to an aspect of the present invention, there is provided a method of operating an application providing a group call service using an mVoIP, the method including: providing an interface used to transmit a request signal for a group call to members in a group chat room; determining group call members who are able to participate in the group call among the members, in response to an input to transmit the request signal being received; creating a new group call chat room including the group call members, when the members are different from the group call members; and transmitting the request signal in the new group call chat room.
0024The determining may include selecting the group call members based on at least one of an application version of each of the members and whether each of the members is allowed to participate in the group call.
0025The group chat room may include a chat room including at least three members.
0026The method may further include providing a predetermined warning message based on a number of the group call members. The predetermined warning message may include at least one of a warning message about impossibility to transmit the request signal when the number of the group call members exceeds a preset maximum threshold or is lower than a preset minimum threshold, a warning message used to determine whether to create the new group call chat room when the number of the group call members is equal to or higher than the preset minimum threshold, is equal to or lower than the preset maximum threshold and is different from a number of the members, and a warning message used to determine whether to create a new one-to-one call chat room when two group call members exist.
0027The predetermined warning message may include a list of members who are unable to participate in the group call among the members, and a reason why each of the members in the list is unable to participate in the group call.
0028The method may further include creating the new one-to-one call chat room with the two group call members based on a determination that the new one-to-one call chat room is to be created, and transmitting a request signal for a one-to-one call in the new one-to-one call chat room.
0029The method may further include inputting a predetermined message associated with a transmission of the request signal to the group call chat room.
0030According to an aspect of the present invention, there is provided a mobile terminal for providing a group call service using an mVoIP, the mobile terminal including: a receiver including a request signal receiver to receive a request signal for a group call, and a meta information receiver to receive meta information for a group call chat room corresponding to the group call from a server, regardless of participation in the group call, wherein the meta information at least includes a group call connection status of each of members in the group call chat room.
0031The mobile terminal may further include a controller, and an interface unit. In response to the request signal being received, the controller may control the interface unit to provide an interface used to receive an input on whether to participate in the group call now or later. In response to an input to participate in the group call now being received via the interface unit, the controller may automatically enter the group call chat room. In response to an input to participate in the group call later being received via the interface unit, the controller may not automatically enter the group call chat room and may control the interface unit to provide an interface enabling participation in the group call without a need to receive again the request signal when entering the group call chat room later. The controller may control the interface unit to provide an indicator including information regarding the group call, and the information regarding the group call may include the group call connection status.
BRIEF DESCRIPTION OF DRAWINGS
0032<figref idref="DRAWINGS">FIGS. 1A and 1B</figref> are diagrams provided to explain a method of receiving a group call in an application providing a group call service using a mobile voice over Internet protocol (mVoIP) according to an embodiment.
0033<figref idref="DRAWINGS">FIGS. 2A through 2C</figref> are diagrams provided to explain an interface used to receive an input on whether to participate in a group call now in response to a request signal being received, according to an embodiment.
0034<figref idref="DRAWINGS">FIGS. 3A and 3B</figref> are diagrams provided to explain an indicator used to provide information regarding a group call according to an embodiment.
0035<figref idref="DRAWINGS">FIGS. 4A and 4B</figref> are diagrams provided to explain an interface enabling participation in a group call without a need to receive again a request signal according to an embodiment.
0036<figref idref="DRAWINGS">FIG. 5</figref> is a diagram provided to explain an interface used to receive an input on whether to accept a request signal in response to the request signal being received according to an embodiment.
0037<figref idref="DRAWINGS">FIG. 6</figref> is a diagram provided to explain a predetermined message associated with a group call according to an embodiment.
0038<figref idref="DRAWINGS">FIGS. 7A and 7B</figref> are diagrams provided to explain an indicator associated with a background mode according to an embodiment.
0039<figref idref="DRAWINGS">FIG. 8</figref> is a flowchart illustrating a method of making a group call in an application providing a group call service using an mVoIP according to an embodiment.
0040<figref idref="DRAWINGS">FIG. 9</figref> is a diagram provided to explain an interface used to transmit a request signal for a group call according to an embodiment.
0041<figref idref="DRAWINGS">FIGS. 10A through 10D</figref> are diagrams provided to explain a predetermined warning message provided based on a number of group call members according to an embodiment.
0042<figref idref="DRAWINGS">FIGS. 11A and 11B</figref> are diagrams provided to explain a predetermined warning message provided when an input to leave a group call chat room is received according to an embodiment.
0043<figref idref="DRAWINGS">FIG. 12</figref> is a diagram provided to explain a predetermined warning message associated with a function deactivated during a group call according to an embodiment.
0044<figref idref="DRAWINGS">FIG. 13</figref> is a diagram provided to explain a predetermined warning message associated with a network error according to an embodiment.
0045<figref idref="DRAWINGS">FIG. 14</figref> is a block diagram illustrating a mobile terminal for providing a group call service using an mVoIP according to an embodiment.
BEST MODE FOR CARRYING OUT THE INVENTION
0046The following detailed description is provided in order to explain the embodiments by referring to the figures.
0047<figref idref="DRAWINGS">FIGS. 1A and 1B</figref> are diagrams provided to explain a method of receiving a group call in an application providing a group call service using a mobile voice over Internet protocol (mVoIP) according to an embodiment.
0048Referring to <figref idref="DRAWINGS">FIG. 1A</figref>, in operation <b>110</b>, the application may receive a request signal for a group call.
0049The group call may include a voice call performed between at least three members using the mVoIP. In other words, the request signal may include request caller information and request receiver information. The request caller information may include information associated with a single request caller, and the request receiver information may include information associated with at least two request receivers.
0050However, depending on circumstances, the group call may include a voice call performed between two members using the mVoIP. For example, the group call may be requested only when at least three members are included, however, may be maintained when only two members remain in the group call after the group call is started.
0051In operation <b>120</b>, the application may receive meta information for a group call chat room from a server, regardless of participation in the group call. In other words, when a user does not participate in a group chat as well as when the user participates in the group chat, the application may receive the meta information for the group call chat room from the server.
0052In the following description, the server may be an apparatus to support a group call service using the mVoIP in connection with the application, and may include, for example, an instant message server or an mVoIP server.
0053The meta information received from the server may include a group call connection status of each of members in the group call chat room. According to another embodiment, an application may receive, from a server, meta information including a group call connection status of each of members other than a user of the application among members in a group call chat room.
0054The group call connection status may be a status in which each of a plurality of members is connected to a group call, and may include, for example, a “connecting” status, a “connected” status, a “terminated” status, or an “impossible connection” status. For example, when the “connecting” status continues during a preset period of time (for example, <b>1</b> minute), the server may change the group call connection status to the “terminated” status.
0055In operation <b>130</b>, the application may provide an interface used to receive an input on whether to participate in the group call now, in response to the request signal being received. In operation <b>140</b>, the user may provide at least one of an input to participate in the group call now and an input to participate in the group call later, using the interface.
0056In operation <b>150</b>, the application may automatically enter a group call chat room corresponding to the group call, in response to the input to participate in the group call now being received. The group call chat room may include a chat room that performs a similar function to a typical instant message group chat room and that additionally provides a function for a group call. For example, the group call chat room may include a plurality of members, may function as an instant messenger to exchange instant messages between the plurality of members, and may additionally provide a voice call function between the plurality of members using an mVoIP.
0057In operation <b>160</b>, the application may provide information regarding the group call using an indicator provided in the group call chat room. The information regarding the group call may include a group call connection status of each of the members in the group call chat room. The indicator may be located in a preset area of a group call chat room interface (for example, a top portion of the group call chat room interface). An indicator according to another embodiment may be located in a portion of an area corresponding to the group call chat room in a chat room list.
0058In operation <b>170</b>, the application may not automatically enter the group call chat room, in response to the input to participate in the group call later being received.
0059In this example, the user may manually enter the group call chat room later. For example, a group call chat room may be automatically added to a chat room list. The application may determine whether a group call chat room is already included in the chat room list, and may add the group call chat room to the chat room list based on a determination that the group call chat room is not included in the chat room list. Accordingly, the user may select the group call chat room from the chat room list, and may manually enter the group call chat room.
0060In operation <b>180</b>, the application may provide an interface enabling participation in the group call without a need to receive again the request signal when entering the group call chat room. For example, the application may provide a reenter button (or a reconnect button) using the indicator provided in the group call chat room. When the user selects the reenter button, the application may exchange required information with the server to allow the user to participate in an ongoing group call.
0061More specifically, the application may receive meta information for the group call chat room from the server, even though the user does not participate in the group call. The meta information may include request caller information and request receiver information included in the request signal.
0062Accordingly, the application may provide a technology of allowing a user to freely participate in a group call until a group call termination signal is received from the server, after the group call is started in response to a reception of a request signal for the group call. The server may transmit the group call termination signal based on a number of members who are participating in the group call. For example, when a single member is participating in the group call, the server may transmit the group call termination signal to all of members in the group call chat room.
0063In addition, the meta information may further include a group call connection status of each of members in the group call chat room. Accordingly, the application may provide the group call connection status of each of the members in the group call chat room, regardless of whether each of the members is participating in the group call.
0064In other words, the application may provide information regarding whether each of the members is currently participating in the group call, when each of the members does not participate in the group call as well as when each of the members participates in the group call.
0065Accordingly, the user may be provided with information on members currently participating in a group call among members in a group call chat room to which the user belongs, and may participate in the group call or terminate the group call at any time during the group call.
0066The terminating the group call may be distinguished from receiving a group call termination signal from the server. For example, when a group call is terminated, a user may participate in the group call again later using a reenter button. When a group call termination signal is received from the server, the user may not participate in a corresponding group call any more.
0067For example, in response to the group call termination signal being received, the application may deactivate a group call-related function provided in the group call chat room. In this example, the group call chat room may perform the same function as a typical instant message group chat room. In other words, the user may start a new group call by transmitting a request signal for the new group call to the same members, and may participate in the new group call.
0068The group call may be distinguished from the group call chat room. For example, the application may provide the group call based on the group call chat room.
0069Also, participating in or terminating a group call may be distinguished from entering or leaving a group call chat room.
0070The entering the group call chat room may literally include entering a group call chat room that supports a group call service. On the other hand, the participating in the group call may include participating in a voice call (for example, a conference call) between a plurality of members using an mVoIP.
0071Similarly, the leaving the group call chat room may literally include leaving a group call chat room that supports a group call service. For example, when a user leaves a group call chat room, the application may change a group call chat room screen to a chat room list screen. On the other hand, the terminating the group call may include terminating a voice call (for example, a conference call) between a plurality of members using an mVoIP. As described above, when a group call is terminated, a user may participate in the group call again later using a reenter button while the group call is in progress by at least two members.
0072Accordingly, the user may not participate in the group call even though the user is in the group call chat room.
0073Referring to <figref idref="DRAWINGS">FIG. 1B</figref>, a user desiring to start a group call (hereinafter, referred to as a “request caller”) may transmit a request signal for a group call using an interface configured to transmit the request signal (<b>191</b>). An application of the request caller may display a screen saying “waiting for connection” until at least one of users receiving the request signal (hereinafter, referred to as “request receivers”) is connected (<b>192</b>).
0074Applications of the request receivers may provide an interface used to receive an input on whether to participate in the group call now, in response to the request signal being received from the request caller (<b>193</b>). When a request receiver enters an input to participate in the group call now using the interface, an application of the request receiver may automatically enter a group call chat room corresponding to the group call, may receive a group call connection status of each of members in the group call chat room from a server, and may provide information regarding the group call using an indicator provided in the group call chat room (<b>194</b>).
0075When a request receiver enters an input to participate in the group call later using the interface, an application of the request receiver may not automatically enter the group call chat room. When the request receiver manually enters the group call chat room later, the application of the request receiver may provide an interface (for example, a reenter button or a reconnect button) allowing the request receiver to participate in the group call without a need to receive again the request signal (<b>195</b>).
0076Additionally, the application of the request receiver may display members who are currently participating in the group call, using the indicator provided in the group call chat room, even though the request receiver does not participate in the group call.
0077When a request receiver selects a reenter button, an application of the request receiver may perform operations to participate in the group call. When the request receiver succeeds in participating in the group call, the application of the request receiver may provide information regarding the group call using the indicator provided in the group call chat room (<b>195</b>-><b>194</b>).
0078When a user (for example, a request caller or a request receiver) terminates a group call by selecting an end button after participating in the group call, an application of the user may provide an interface (for example, a reenter button or a reconnect button) allowing the user to participate in the group call without a need to receive again the request signal (<b>194</b>-><b>195</b>).
0079Accordingly, an application according to an embodiment may provide a technology of allowing a user to freely participate in a group call or terminate the group call until a group call termination signal is received from a server after the group call is started, through the above-described operations.
0080<figref idref="DRAWINGS">FIGS. 2A through 2C</figref> are diagrams provided to explain an interface used to receive an input on whether to participate in a group call now in response to a request signal being received, according to an embodiment.
0081In an example, referring to <figref idref="DRAWINGS">FIG. 2A</figref>, an interface used to receive an input on whether to participate in a group call now may include a button <b>220</b> for an input to participate in the group call now, and a button <b>210</b> for an input to participate in the group call later.
0082The interface may further include information <b>230</b> associated with a member sending a request signal for a group call. For example, the interface may display an identification (ID) of a member sending a request signal for a group call.
0083In addition, the interface may further include a predetermined message <b>240</b> corresponding to a request signal for a group call. For example, a message saying “Let's group call˜” may correspond to the request signal.
0084In another example, referring to <figref idref="DRAWINGS">FIG. 2B</figref>, an interface used to receive an input on whether to participate in a group call now may further include a profile photo <b>250</b> of a member sending a request signal for a group call. Accordingly, a request receiver may more intuitively recognize a request caller.
0085In still another example, referring to <figref idref="DRAWINGS">FIG. 2C</figref>, an interface used to receive an input on whether to participate in a group call now may further include information <b>270</b> regarding a member receiving a request signal for a group call together with a user of the interface. In this example, when the member receives the request signal, but does not yet participate in the group call, an application may process a profile photo of the member to dimly appear.
0086Also, the interface may further include a group call connection status <b>280</b> of the user of the interface. For example, an application may display a group call connection status of the user of the interface as “waiting for connection” while waiting until an input to participate in the group call now is received from the user of the interface.
0087<figref idref="DRAWINGS">FIGS. 3A and 3B</figref> are diagrams provided to explain an indicator used to provide information regarding a group call according to an embodiment.
0088In an example, referring to <figref idref="DRAWINGS">FIG. 3A</figref>, information regarding a group call may include a group call connection status <b>310</b> of each of members in a group call chat room and a profile photo <b>320</b> of each of the members.
0089In this example, an application may adjust a dimness of the profile photo based on the group call connection status. For example, the application may process a profile photo of a member in a “terminated” status or a “connecting” status to dimly appear. In this example, the application may process a profile photo of a member currently participating in the group call to clearly appear.
0090In another example, information regarding a group call may further include at least one of a period of time <b>330</b> of participation in a group call, a network connection status <b>340</b> for the group call, and a member requesting the group call. The application may generate the information regarding the group call based on meta information received from a server.
0091The period of time <b>330</b> may be measured from a point in time at which a user of the application participates in a group call. When the user ends a group call and participates in the group call again, the period of time <b>330</b> may be measured from a point in time at which the user participates in the group call again.
0092The network connection status <b>340</b> may be displayed using a weather icon, for example, a sun icon, a cloud icon or a rain icon. For example, when a network connection status is good, the application may display the sun icon. When the network connection status is normal, the application may display the cloud icon. When the network connection status is bad, the application may display the rain icon. When the network connection status is changed during a group call, the application may change an icon and may play back a notification sound notifying a change in the network connection status.
0093Additionally, the application may display the member requesting the group call by assigning a predetermined graphic effect (for example, a crown icon) to a profile photo of the member.
0094In still another example, an application may further provide at least one of an interface <b>350</b> used to activate at least one of a voice change function, a mute function and a speakerphone function using an indicator provided in the group call chat room, an interface <b>360</b> used to terminate a group call, and an interface <b>370</b> used to fold the indicator.
0095When the voice change function is activated, the application may change a user's voice based on the activated voice change function, and may transmit the changed voice. When the mute function is activated, the application may prevent a user's voice from being transferred to the other party. When the speakerphone function is activated, the application may play back a voice of the other party through a speaker so that people around the application may listen to conversation.
0096When an input to terminate a group call is received, the application may terminate the group call and may provide an interface enabling participation in the group call again.
0097When an input to fold an indicator is received, the application may reduce the indicator so that only information regarding a group call may be displayed.
0098For example, referring to <figref idref="DRAWINGS">FIG. 3B</figref>, in response to an input to fold an indicator being received, the application may display a group call connection status of each of members in a group call chat room, a profile photo of each of the members in the group call chat room, a period of time of participation in a group call, a network connection status for the group call and a member requesting the group call, instead of displaying an interface used to activate at least one of a voice change function, a mute function and a speakerphone function, an interface used to terminate the group call, and an interface used to fold the indicator.
0099In this example, the application may further provide an interface <b>380</b> to unfold the indicator. When an input to unfold the indicator is received, the application may display the interface used to activate at least one of the voice change function, the mute function and the speakerphone function, the interface used to terminate the group call, and the interface used to fold the indicator.
0100<figref idref="DRAWINGS">FIGS. 4A and 4B</figref> are diagrams provided to explain an interface enabling participation in a group call without a need to receive again a request signal according to an embodiment.
0101In an example, referring to <figref idref="DRAWINGS">FIG. 4A</figref>, an interface enabling participation in a group call without a need to receive again a request signal may include a reconnect button <b>410</b> or a reenter button.
0102In this example, an application may provide information <b>420</b> regarding the group call, using an indicator provided in a group call chat room. The information <b>420</b> may include a group call connection status.
0103In another example, referring to <figref idref="DRAWINGS">FIG. 4B</figref>, an application may further provide a connection status <b>430</b> of a user of the application using an indicator provided in a group call chat room.
0104<figref idref="DRAWINGS">FIG. 5</figref> is a diagram provided to explain an interface used to receive an input on whether to accept a request signal in response to the request signal being received according to an embodiment.
0105Referring to <figref idref="DRAWINGS">FIG. 5</figref>, an application according to an embodiment may provide an interface used to receive an input on whether to accept a request signal for a group call, in response to the request signal being received (<b>510</b>).
0106In response to an input to accept the request signal being received, the application may enter a group call chat room corresponding to the group call. The application may provide an interface used to receive an input on whether to participate in the group call now, using an indicator provided in the group call chat room (<b>520</b>).
0107The above description of <figref idref="DRAWINGS">FIGS. 1 through 4B</figref> may equally be applicable to subsequent operations of the application and accordingly, will not be repeated here. For example, when an input to participate in the group call now is received, the application may display information regarding the group call, and the like (<b>530</b>). When an input to participate in the group call later is received, the application may an interface enabling participation in the group call without a need to receive again the request signal (<b>540</b>).
0108<figref idref="DRAWINGS">FIG. 6</figref> is a diagram provided to explain a predetermined message associated with a group call according to an embodiment.
0109Referring to <figref idref="DRAWINGS">FIG. 6</figref>, an application according to an embodiment may input a predetermined message in a group call chat room corresponding to the group call, in response to an operation associated with the group call being performed. The application may display each message in a form (for example, a speech bubble) the same as or similar to a message directly input by a user.
0110For example, when a request signal for a group call is transmitted, the application may input a message <b>610</b> saying “Let's group call˜” to a group call chat room. When no answer is received from request receivers, the application may input a message <b>620</b> saying “No answer” to the group call chat room.
0111When an input to cancel the group call before the group call is started is received after the request signal is transmitted, the application may input a message <b>630</b> saying “Cancel” to the group call chat room. When an input to terminate the group call is received after the group call is started, the application may input a message <b>640</b> saying “End” to the group call chat room. The application may also input a message <b>650</b> indicating a period of time of participation in the group call to the group call chat room.
0112In another example, an application may play preset notifications corresponding to various events occurring in association with a group call, although not shown in the drawings. The preset notifications may include, for example, at least one of an effect sound, a ringtone, a vibration, a light emitting diode (LED) lamp, and a graphic effect of a display.
0113For example, when a member currently participating in a group call terminates the group call, the application may play a first preset notification (for example, Ding-Dong). When a member not participating in a group call participants in the group call, the application may play a second preset notification (for example, Ding). When a new message is input to a group call chat room, the application may play a third preset notification (for example, Tick-Tock). When a new message is input to another chat room, the application may play a fourth preset notification (for example, a notification based on a basic setting of the application). When a request signal for a group call is received, the application may play a fifth preset notification (for example, a ringback tone or a vibration).
0114In other words, the application may play different notifications based on various cases occurring in association with a group call and accordingly, may provide a technology allowing a user to more easily recognize a situation based on a played notification only.
0115<figref idref="DRAWINGS">FIGS. 7A and 7B</figref> are diagrams provided to explain an indicator associated with a background mode according to an embodiment.
0116In an example, referring to <figref idref="DRAWINGS">FIG. 7A</figref>, an application may receive an input to allow the application to be executed in the background mode during participation in a group call.
0117For example, when an input of a home button in a mobile terminal including the application is received using the application during the participation in the group call, the application may recognize the input of the home button as an input to execute the application in the background mode.
0118In this example, the application may provide information indicating that a participant is participating in the group call to an indicator <b>710</b> associated with the background mode. In another example, referring to <figref idref="DRAWINGS">FIG. 7B</figref>, an application may provide information indicating that a participant is participating in a group call to a notification window <b>720</b> associated with a background mode.
0119<figref idref="DRAWINGS">FIG. 8</figref> is a flowchart illustrating a method of making a group call in an application providing a group call service using an mVoIP according to an embodiment.
0120Referring to <figref idref="DRAWINGS">FIG. 8</figref>, in operation <b>810</b>, the application may provide an interface used to transmit a request signal for a group call to members in a group chat room.
0121For example, referring to <figref idref="DRAWINGS">FIG. 9</figref>, the application may provide a group call request button <b>910</b> to transmit the request signal to the members in the group chat room.
0122In this example, the group chat room may include a chat room including at least three members. In other words, the application may provide an interface used to transmit a request signal for a group call to only the chat room including at least three members.
0123In operation <b>820</b>, the application may determine group call members who are able to participate in the group call among the members in the group chat room, in response to an input to transmit the request signal being received.
0124The application may determine the group call members based on an application version of each of the members in the group chat room. For example, the application may select, as a member unable to participate in the group call, a member having a terminal in which an application with a version lower than a version of an application supporting a group call is installed.
0125The application may also determine the group call members based on whether each of the members in the group chat room is allowed to participate in the group call. For example, the application may select a member who deactivates a group call as a member unable to participate in the group call.
0126In operation <b>830</b>, the application may create a new group call chat room including the group call members, when the members in the group chat room are different from the group call members.
0127The application may provide a user with a warning message about whether to create a new group call chat room including the group call members, which will be further described with reference to <figref idref="DRAWINGS">FIGS. 10A through 10D</figref>.
0128In operation <b>840</b>, the application may transmit the request signal in the new group call chat room.
0129<figref idref="DRAWINGS">FIGS. 10A through 10D</figref> are diagrams provided to explain a predetermined warning message provided based on a number of group call members according to an embodiment.
0130An application according to an embodiment may provide a user with a predetermined warning message based on a number of group call members who are able to participate in a group call.
0131For example, in response to an input to select an interface <b>1010</b> used to transmit a request signal for a group call being received, the application may determine the group call members among members in a group chat room. In this example, the application may provide a user with a predetermined warning message based on a number of the determined group call members. In the following description, a number of the members in the group chat room and the number of the group call members may be calculated to include a request caller.
0132For example, referring to <figref idref="DRAWINGS">FIG. 10A</figref>, when the number of the group call members exceeds a preset maximum threshold (for example, five people), the application may provide the user with a warning message <b>1020</b> about impossibility to transmit a request signal for a group call.
0133Referring to <figref idref="DRAWINGS">FIG. 10B</figref>, when the number of the group call members is equal to or higher than a preset minimum threshold (for example, three people), is equal to or lower than a preset maximum threshold (for example, five people), and is different from the number of the members in the group chat room, the application may provide the user with a warning message <b>1030</b> used to determine whether to create a new group call chat room. When creation of a new group call chat room is determined, the application may create a new group call chat room including the group call members, and may transmit a request signal for a group call in the new group call chat room.
0134Referring to <figref idref="DRAWINGS">FIG. 10C</figref>, when the number of the group call members is lower than a preset minimum threshold (for example, two people), the application may provide the user with a warning message <b>1040</b> about impossibility to transmit a request signal for a group call.
0135Referring to <figref idref="DRAWINGS">FIG. 10D</figref>, when two group call members exist, the application may provide the user with a warning message <b>1040</b> used to determine whether to create a new one-to-one call chat room. When creation of a new one-to-one call chat room is determined, the application may create a new one-to-one call chat room including the two group call members, and may transmit a request signal for a one-to-one call in the new one-to-one call chat room.
0136Each of the above-described warning messages may include a list of members unable to participate in the group call among the members in the group chat room, and a reason why each of the members in the list is unable to participate in the group call.
0137<figref idref="DRAWINGS">FIGS. 11A and 11B</figref> are diagrams provided to explain a predetermined warning message provided when an input to leave a group call chat room is received according to an embodiment.
0138In an example, referring to <figref idref="DRAWINGS">FIG. 11A</figref>, in response to an input <b>1110</b> to leave a group call chat room being received during participation in (or connection to) a group call, an application according to an embodiment may provide a user with a warning message <b>1120</b> about impossibility to participate in (or connect to) the group chat when leaving the group call chat room.
0139In this example, the application may interrupt participating in the group chat based on a determination to leave the group call chat room.
0140In another example, referring to <figref idref="DRAWINGS">FIG. 11B</figref>, in response to an input <b>1110</b> to leave a group call chat room being received during participation in a group call, the application may provide the user with a warning message <b>1130</b> saying that a group chat will be terminated when leaving the group call chat room.
0141In this example, the application may terminate the group chat based on a determination to leave the group call chat room.
0142<figref idref="DRAWINGS">FIG. 12</figref> is a diagram provided to explain a predetermined warning message associated with a function deactivated during a group call according to an embodiment.
0143Referring to <figref idref="DRAWINGS">FIG. 12</figref>, an application according to an embodiment may deactivate at least one predetermined function associated with a group call chat room when a group call is ongoing.
0144The ongoing group call may indicate that at least two member among members in a group call chat room are participating in the group call even though a user of the application does not participate in the group call.
0145For example, the application may deactivate a function of inviting a new member to a group call chat room during the group call. In this example, the application may deactivate a settings menu of the group call chat room, to deactivate the function of inviting the new member to the group call chat room.
0146Also, the application may deactivate at least one of a video playback function, a sound playback function, a gift shop function, an emoticon store function and a mini-profile function in the group call chat room during the group call. In <figref idref="DRAWINGS">FIG. 12</figref>, when a single interface is selected from an interface <b>1210</b> corresponding to the mini profile function, an interface <b>1220</b> corresponding to the emoticon store function, an interface <b>1230</b> corresponding to the gift shop function, and an interface <b>1240</b> corresponding to the video playback function or the sound playback function, the application may provide a user with a warning message <b>1250</b> saying that a corresponding function is disabled.
0147<figref idref="DRAWINGS">FIG. 13</figref> is a diagram provided to explain a predetermined warning message associated with a network error according to an embodiment.
0148Referring to <figref idref="DRAWINGS">FIG. 13</figref>, when participation in a group call now is impossible due to a network error, even though an input <b>1310</b> to participate in the group call now is received, an application according to an embodiment may provide a user with a warning message <b>1320</b> saying a network error.
0149<figref idref="DRAWINGS">FIG. 14</figref> is a block diagram illustrating a mobile terminal for providing a group call service using an mVoIP according to an embodiment.
0150Referring to <figref idref="DRAWINGS">FIG. 14</figref>, a mobile terminal <b>1400</b> may include a receiver <b>1410</b>. The receiver <b>1410</b> may include a request signal receiver and a meta information receiver, although not shown in <figref idref="DRAWINGS">FIG. 14</figref>.
0151The request signal receiver may receive a request signal for a group call. The meta information receiver may receive meta information for a group call chat room corresponding to the group call from a server, regardless of participation in the group call. The meta information may at least include a group call connection status of each of members in the group call chat room.
0152The mobile terminal <b>1400</b> may further include a controller <b>1420</b> and an interface unit <b>1430</b>.
0153The interface unit <b>1430</b> may be a module configured to provide an input interface or an output interface to a user of the mobile terminal <b>1400</b>, and may include, for example, a display, a keypad, or a touch screen.
0154The controller <b>1420</b> may control the interface unit <b>1430</b> based on information received by the receiver <b>1410</b>, and may perform operations to provide the group call service.
0155For example, in response to a request signal being received by the receiver <b>1410</b>, the controller <b>1420</b> may control the interface unit <b>1430</b> to provide an interface used to receive an input on whether to participate in the group call now or later.
0156In an example, in response to an input to participate in the group call now being received via the interface unit <b>1430</b>, the controller <b>1420</b> may automatically enter the group call chat room.
0157In another example, in response to an input to participate in the group call later being received via the interface unit <b>1430</b>, the controller <b>1420</b> may not automatically enter the group call chat room. In this example, the controller <b>1420</b> may control the interface unit <b>1430</b> to provide an interface enabling participation in the group call without a need to receive again the request signal when entering the group call chat room later.
0158In addition, the controller <b>1420</b> may control the interface unit <b>1430</b> to provide an indicator including information regarding the group call. The information regarding the group call may include a group call connection status of each of members in the group call chat room.
0159The above description of <figref idref="DRAWINGS">FIGS. 1 through 13</figref> may equally be applicable to each module of <figref idref="DRAWINGS">FIG. 14</figref> and accordingly, will not be repeated here.
0160The units and/or modules described herein may be implemented using hardware components, software components, or a combination thereof. For example, the units and/or modules may include a processor, a controller and an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable array (FPA), a programmable logic unit (PLU), a microprocessor or any other device capable of responding to and executing instructions in a defined manner. A processing device may run an operating system (OS) and one or more software applications that run on the OS. The processing device also may access, store, manipulate, process, and create data in response to execution of the software. For purpose of simplicity, the description of a processing device is used as singular; however, one skilled in the art will appreciated that a processing device may include multiple processing elements and multiple types of processing elements. For example, a processing device may include multiple processors or a processor and a controller. In addition, different processing configurations are possible, such a parallel processors.
0161The software may include a computer program, a piece of code, an instruction, or some combination thereof, to independently or collectively instruct and/or configure the processing device to operate as desired, thereby transforming the processing device into a special purpose processor. Software and data may be embodied permanently or temporarily in any type of machine, component, physical or virtual equipment, computer storage medium or device, or in a propagated signal wave capable of providing instructions or data to or being interpreted by the processing device. The software also may be distributed over network coupled computer systems so that the software is stored and executed in a distributed fashion. The software and data may be stored by one or more non-transitory computer readable recording mediums.
0162The methods according to the above-described embodiments may be recorded in non-transitory computer-readable media including program instructions to implement various operations of the above-described embodiments. The media may also include, alone or in combination with the program instructions, data files, data structures, and the like. The program instructions recorded on the media may be those specially designed and constructed for the purposes of embodiments, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of non-transitory computer-readable media include magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM discs, DVDs, and/or Blue-ray discs; magneto-optical media such as optical discs; and hardware devices that are specially configured to store and perform program instructions, such as read-only memory (ROM), random access memory (RAM), flash memory (e.g., USB flash drives, memory cards, memory sticks, etc.), and the like. Examples of program instructions include both machine code, such as produced by a compiler, and files containing higher level code that may be executed by the computer using an interpreter. The above-described devices may be configured to act as one or more software modules in order to perform the operations of the above-described embodiments, or vice versa.
0163A number of embodiments have been described above. Nevertheless, it should be understood that various modifications may be made to these embodiments. For example, suitable results may be achieved if the described techniques are performed in a different order and/or if components in a described system, architecture, device, or circuit are combined in a different manner and/or replaced or supplemented by other components or their equivalents.
0164Accordingly, other implementations are within the scope of the following claims.
Contents5
25 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23 Sheet 24 Sheet 25
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2023031018A1 | Cited by | United States of America | Search report |
| US11032408B2 | Cited by | United States of America | Search report |
| US2015036664A1 | Cited by | United States of America | Pre-grant |
| US2021194835A1 | Cited by | United States of America | Search report |
| US12294555B2 | Cited by | United States of America | Search report |
| US9912777B2 | Cited by | United States of America | Search report |
| US11695582B2 | Cited by | United States of America | Applicant |
| US2020037104A1 | Cited by | United States of America | Search report |
| US2016269504A1 | Cited by | United States of America | Pre-grant |
| US2016294893A1 | Cited by | United States of America | Pre-grant |
| US2015036664A1 | Cited by | United States of America | Pre-grant |
| US9526049B2 | Cited by | United States of America | Search report |
| US10908779B2 | Cited by | United States of America | Search report |
| US11763317B2 | Cited by | United States of America | Search report |
| US10924897B2 | Cited by | United States of America | Applicant |
| US11902225B2 | Cited by | United States of America | Search report |
| US11362847B2 | Cited by | United States of America | Search report |
| US11281358B2 | Cited by | United States of America | Applicant |
| US2020104015A1 | Cited by | United States of America | Search report |
| US2002188731A1 | Cites | United States of America | Pre-grant |
| US2005074107A1 | Cites | United States of America | Pre-grant |
| US2007208806A1 | Cites | United States of America | Pre-grant |
| US2008104169A1 | Cites | United States of America | Pre-grant |
| US2008159503A1 | Cites | United States of America | Pre-grant |
| US2008184326A1 | Cites | United States of America | Pre-grant |
| US2012054008A1 | Cites | United States of America | Pre-grant |
| US2012110099A1 | Cites | United States of America | Pre-grant |
| US2012230484A1 | Cites | United States of America | Pre-grant |
| US2013039223A1 | Cites | United States of America | Pre-grant |
| US2013063543A1 | Cites | United States of America | Pre-grant |
| US2013246628A1 | Cites | United States of America | Pre-grant |
| US2013293665A1 | Cites | United States of America | Pre-grant |
| US2014349621A1 | Cites | United States of America | Pre-grant |
| US7734692B1 | Cites | United States of America | Pre-grant |
| US7779139B2 | Cites | United States of America | Pre-grant |
| US8166079B2 | Cites | United States of America | Pre-grant |
| US8856355B2 | Cites | United States of America | Pre-grant |
| US9736089B2 | Cites | United States of America | Pre-grant |
13 members in 5 offices; this record represents the family
Priority claims3
| Document | Office | Kind | Date |
|---|---|---|---|
| 1020120119720 | Republic of Korea | – | |
| 20120119720 | Republic of Korea | A | |
| 2013009584 | Republic of Korea | W |
Members13
| Document | Office | Kind | |
|---|---|---|---|
| WO2014065631A1 | World Intellectual Property Organization (WIPO) | A1 | |
| KR20140056491A | Republic of Korea | A | |
| KR101467248B1 | Republic of Korea | B1 | |
| US2015256570A1 | United States of America | A1 | |
| CN104937545A | China | A | |
| JP2015536607A | Japan | A | |
| JP6083834B2 | Japan | B2 | |
| JP2017099008A | Japan | A | |
| CN104937545B | China | B | |
| US10069879B2 | United States of America | B2 | |
| US2018375911A1 | United States of America | A1 | |
| JP6469737B2 | Japan | B2 | |
| US10305946B2 | United States of America | B2 |
93 transactions on the USPTO file
Allowed after 1 non-final rejection, 1 final rejection and 1 RCE.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Email NotificationEML_NTR | EML_NTR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Interview Summary - Examiner Initiated - TelephonicEXET | EXET | |
| After Final Consideration Program Additional Consideration and/or updated searchAFAC | AFAC | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| PILOT- Request for After Final Consideration ProgramRAFC | RAFC | |
| Response after Final ActionA.NE | A.NE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Incoming Letter Pertaining to the DrawingsLTDR | LTDR | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response to Election / Restriction FiledELC. | ELC. | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Restriction RequirementMCTRS | MCTRS | |
| Restriction/Election RequirementCTRS | CTRS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Close TICLTI | CLTI | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| Filing Receipt - CorrectedFLRCPT.C | FLRCPT.C | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Is Now CompleteCOMP | COMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Pre-Exam NoticeMPEN | MPEN | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Notice of DO/EO Acceptance MailedM903 | M903 | |
| Sent to Classification ContractorPGPC | PGPC | |
| FITF set to NO - revise initial settingFTFI | FTFI | |
| Mail Pre-Exam NoticeMPEN | MPEN | |
| Cleared by OIPE CSRL194 | L194 | |
| Cleared by OIPE CSRL194 | L194 | |
| Cleared by OIPE CSRL194 | L194 | |
| Cleared by OIPE CSRL194 | L194 | |
| Request for Foreign Priority (Priority Papers May Be Included)RQPR | RQPR | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Preliminary AmendmentA.PE | A.PE | |
| 371 Completion Date371COMP | 371COMP | |
| Patent Term Adjustment - Ready for ExaminationPTA.RFE | PTA.RFE | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Entity Status Set To Undiscounted (Initial Default Setting or Status Change)BIG. | BIG. | |
| Initial Exam Team nnIEXX | IEXX |
5 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication
- 20150256570
- Application
- 14438861
Titles
- English
- Method for Operating Application Providing Group Call Service Using Mobile Voice over Internet Protocol
Patent term adjustment
- A delay
- +248 daysthe office missed an examination deadline
- Applicant delay
- −15 days
- Net adjustment
- 233 days
Classification
- CPC, 10
- H04L65/403
- H04L12/1813
- H04M1/2535
- H04W4/16
- H04L51/04
- H04L65/1016
- H04L65/1069
- H04M1/72436
- G06F9/448
- H04W88/02
- IPC, 3
- H04L29 06
- H04M1 72436
- H04W4 16