KR20240066221A - Method of managing connection for group call based on neighbor cell information and electronic device therefor - Google Patents

Abstract

An electronic device including a communication circuit, a display, a memory, and a processor is disclosed. The electronic device can receive data of a group call session through a multicast bear. If the communication quality associated with the group call session falls below a threshold, the electronic device may add a unicast bearer. After adding a unicast bearer, the electronic device may determine whether to release the multicast bearer based on the SAI of the serving cell and the SAI of the neighboring cell.

Description

Group call connection management method based on neighboring cell information and electronic device therefor {METHOD OF MANAGING CONNECTION FOR GROUP CALL BASED ON NEIGHBOR CELL INFORMATION AND ELECTRONIC DEVICE THEREFOR}

Embodiments disclosed in this document relate to a group call connection management method based on neighboring cell information and an electronic device therefor.

For those involved in public safety to prevent, prepare for, respond to, and recover from disasters, separate methods of communication may be required. For example, communication for public safety may be performed using a communication network such as Public Safety (PS) LTE based on Long-Term Evolution (LTE). For example, for public safety, PS LTE technology may support group calls and/or direct calls based on Group Communication System Enabler (GCSE) and/or Device-to-Device (D2D). For example, PS LTE technology can support group calls such as Mission Critical Push-To-Talk (MCPTT).

eMBMS (evolved Multimedia Broadcast and Multicast Service) is a technology that can transmit the same data to multiple user devices through an LTE network. For eMBMS, the same data can be delivered to multiple user devices through MBSFN (Multicast-Broadcast Single Frequency Network). For example, participants in a group call can transmit data associated with the group call via MBSFN. Within one cell, multiple user devices can receive data using a single frequency. For example, by connecting to the server of a content provider that provides the group number, the user device can receive data associated with the group number.

The above information may be provided as background art for the purpose of aiding understanding of the present disclosure. No claim or determination is made as to whether any of the foregoing may apply as prior art with respect to the present disclosure.

An electronic device according to an example of the present disclosure may include a communication circuit, a memory, and a processor. Memory can store instructions that, when executed by the processor, allow the processor to perform various operations. The processor may receive data of a group call session through a multicast bearer using a communication circuit. When the communication quality associated with the group call session falls below the first threshold, the processor may add a unicast bearer for the group call session and receive data associated with the group call session through the unicast bearer. After adding a unicast bearer, the processor multicasts based on a first service area identifier (SAI) associated with a group call session of the serving cell of the electronic device and at least one second SAI of at least one neighboring cell of the serving cell. You can decide whether to release the bearer.

In one example of the present disclosure, a method of an electronic device may include receiving data of a group call session through a multicast bearer using the communication circuit. The operation includes, when the communication quality associated with the group call session falls below a first threshold, adding a unicast bearer for the group call session and receiving data associated with the group call session through the unicast bearer. Can include actions. The method includes, after adding the unicast bearer, a first service area identifier (SAI) associated with the group call session of the serving cell of the electronic device and at least one second SAI of at least one neighboring cell of the serving cell. It may include an operation of determining whether to release the multicast bearer based on .

1 shows a communication environment according to one embodiment.
Figure 2 illustrates group call connection of an electronic device according to an embodiment.
Figure 3 shows a block diagram of an electronic device according to an embodiment.
FIG. 4 illustrates a cell environment of an electronic device according to an embodiment.
Figure 5 shows changes in communication quality according to one embodiment.
FIG. 6 illustrates a flowchart of a group call connection management method based on neighboring cell information of an electronic device, according to an embodiment.
Figure 7 shows a flowchart of a unicast bearer management method of an electronic device according to an embodiment.
Figure 8 shows a flowchart of a method of performing a group call in an electronic device according to an embodiment.
Figure 9 shows a flowchart of a multicast bearer management method for an electronic device according to an embodiment.
Figure 10 is a block diagram of an electronic device in a network environment, according to one embodiment.
In connection with the description of the drawings, similar reference numbers may be used for similar components.

Hereinafter, various embodiments of this document are described with reference to the attached drawings. However, this is not intended to limit the technology described in this document to specific embodiments, and should be understood to include various modifications, equivalents, and/or alternatives to the embodiments of this document. . In connection with the description of the drawings, similar reference numbers may be used for similar components.

1 shows a communication environment according to one embodiment.

Referring to FIG. 1 , according to one embodiment, a communication environment may include a server device 200 and a plurality of electronic devices 100, 101, 102, and 103. For example, a plurality of electronic devices 100, 101, 102, and 103 may communicate with the server device 200 through the network 299. Network 299 may be any internet protocol (IP) network. For example, network 299 may correspond to second network 1099 in FIG. 10 .

The plurality of electronic devices 100, 101, 102, and 103 include the electronic device 100, the first external electronic device 101, the second external electronic device 102, and the third external electronic device 103. It can be included. For example, the plurality of electronic devices 100, 101, 102, and 103 may be electronic devices that perform group calls (eg, group communication). A plurality of electronic devices 100, 101, 102, and 103 may receive a group call by receiving data corresponding to the group call session from the server device 200 through the network 299. For example, when the electronic device 100 transmits data to the server device 200, the server device 200 responds to the first external electronic device 101 and the second external electronic device 102 participating in the same group call session. ), and the data received from the electronic device 100 can be transmitted to the third external electronic device 103. For example, the server device 200 may be a server operated by a service provider that provides services related to group numbers.

The network 299 may create a group call session with each of the plurality of electronic devices 100, 101, 102, and 103 based on session initiation protocol (SIP). For example, the electronic device 100 may output data of a group call session. The electronic device 100 may output data received from the server device 200 audio and/or visually. Group calls may include, for example, voice calls and/or video calls. Group calls may include, for example, MCPTT calls.

The number of electronic devices 100, 101, 102, and 103 shown in FIG. 1 is illustrative, and embodiments of this document are not limited thereto. For example, any number of electronic devices may be associated with server device 200. The types of the plurality of electronic devices 101, 102, 103, and 104 shown in FIG. 1 are illustrative, and embodiments of this document are not limited thereto. For example, the plurality of electronic devices 101, 102, 103, and 104 may include any user equipment.

Below, for convenience of explanation, various embodiments of the disclosure may be described focusing on the electronic device 100. Those skilled in the art will understand that the operations described below in relation to the electronic device 100 may be performed using any electronic device (e.g., the first external electronic device 101, the second external electronic device 102, and/or the third external electronic device ( You will be able to understand that it can be performed by 103)).

Figure 2 illustrates group call connection of an electronic device according to an embodiment.

According to one embodiment, the electronic device 100 may transmit and receive data associated with a group call from the server device 200 through at least one of the unicast bearer 271 or the multicast bearer 272. For example, data associated with a group call may include media data to be shared in the group call session.

For example, the unicast bearer 271 may be a data path between the electronic device 100 and the server device 200. The server device 200 may set the data destination to the electronic device 100 and receive data from the electronic device 100 through the unicast bearer 271.

For example, the multicast bearer 272 may be a data path between a plurality of electronic devices 100, 101, and 102 and the server device 200. The server device 200 may set the data destination to a plurality of electronic devices 100, 101, and 102 and receive data from the electronic device 100 through the multicast bearer 272.

According to one embodiment, the electronic device 100 uses a unicast bearer 271 and/or a multicast bearer 272 based on the service area identifier (SAI) of a neighboring cell of the serving cell to which the electronic device 100 belongs. It can be managed. For example, the electronic device 100 may manage the unicast bearer 271 and/or the multicast bearer 272 based on the communication quality associated with the group call and the SAI of the neighboring cell. Below, various operations of the electronic device 100 according to an embodiment may be described with reference to FIGS. 3 to 9 . Hereinafter, various operations of the electronic device 100 will be described with reference to the contents described above with respect to FIGS. 1 and 2. However, the contents described above with respect to FIGS. 1 and 2 are intended to aid understanding, and It is not intended to limit the scope of rights.

Figure 3 shows a block diagram of an electronic device according to an embodiment.

2 and 3, according to one embodiment, the electronic device 100 may include a processor 120, a memory 130, a communication circuit 140, and/or an antenna module 170. . For example, processor 120 may correspond to processor 1020 of FIG. 10 . For example, memory 130 may correspond to memory 1030 of FIG. 10 . For example, the communication circuit 140 may correspond to the communication module 1090 of FIG. 10 . For example, the antenna module 170 may correspond to the antenna module 1097 of FIG. 10 . The configuration of the electronic device 100 in FIG. 3 is an example, and the electronic device 100 may further include a configuration not shown in FIG. 3 . For example, the electronic device 100 may include a camera and/or microphone to obtain data related to the group call. For example, the electronic device 100 may include a display and/or speaker for outputting data related to the group call. The first external electronic device 101, the second external electronic device 102, and/or the third external electronic device 103 of FIG. 1 may include the same or similar configuration as the electronic device 100.

The processor 120 may be electrically, operatively, or functionally connected to the memory 130, the communication circuit 140, and/or the antenna module 170. In the present disclosure, when one component is “operably” connected to another component, it may mean that one component is connected to operate the other component. For example, one component may actuate another component by transmitting a control signal to the other component, either directly or via another component. In the present disclosure, when one component is “functionally” connected to another component, it may mean that one component is connected to execute the function of the other component. For example, one component may execute the function of another component by transmitting a control signal to the other component directly or via another component.

Memory 130 may store instructions. When executed by the processor 120, the instructions may cause the electronic device 100 to perform various operations. In the present disclosure, the operation of the electronic device 100 may be referred to as an operation performed by the processor 120 by executing instructions stored in the memory 130. For example, the memory 130 may store an application for performing a group call. The processor 120 can participate in a group call by executing an application.

The communication circuit 140 may be connected to the electronic device 100 and other electronic devices (e.g., the server device 200) and/or external electronic devices (e.g., the first external electronic device 101, the second external electronic device 102, and/or the third external electronic device 103). The communication circuit 140 may support wired communication and/or wireless communication. For example, the communication circuit 140 may support long-distance wireless communication and may be electrically connected to the antenna module 170. , the processed signal may be transmitted to the processor 120, and the communication circuit 140 may perform preprocessing on the signal received from the processor 120 and transmit the preprocessed signal through the antenna module 170. .

According to one embodiment, the electronic device 100 may perform a group call through the multicast bearer 272. While performing a group call, the electronic device 100 may receive data related to the group call from the server device 200 through the multicast bearer 272. While performing a group call, the electronic device 100 may establish a unicast bearer 271 when the communication quality associated with the group call falls below a reference value. By establishing the unicast bearer 271 before releasing the multicast bearer 272, the electronic device 100 can provide a seamless connection.

According to one embodiment, the electronic device 100 may determine whether to maintain the multicast bearer 272 based on the SAI of a neighboring cell after establishing the unicast bearer 271. If the SAI of the serving cell and at least one of the SAIs of neighboring cells are the same, the electronic device 100 may maintain the multicast bearer 272. In this case, the electronic device 100 may receive data associated with the group call through at least one of the multicast bearer 272 or the unicast bearer 271. By managing the multicast bearer 272 based on the SAI of a neighboring cell, the electronic device 100 can reduce unnecessary switching between the multicast bearer 272 and the unicast bearer 271. For example, when communication quality changes frequently, the electronic device 100 maintains the unicast bearer 271 and the multicast bearer 272 to reduce delays due to bearer switching and additional bearer connection flows, and to ensure data stability. can increase. By reducing unnecessary switching, the electronic device 100 can reduce resource waste of the network 299 and call quality deterioration.

According to one embodiment, the electronic device 100 may determine whether to maintain the multicast bearer 272 based on the SAI of a neighboring cell after establishing the unicast bearer 271. If there is no SAI identical to the SAI of the serving cell among the SAIs of the neighboring cell, the electronic device 100 may release the multicast bearer 272 after establishing the unicast bearer 271. In this case, the electronic device 100 releases the multicast bearer 272 rather than maintaining it, thereby preventing repeated disconnection.

According to one embodiment, the electronic device 100 may receive data related to a group call through the unicast bearer 271 and the multicast bearer 272. For example, the electronic device 100 may combine at least a portion of data received through the unicast bearer 271 and at least a portion of data received through the multicast bearer 272. By combining data, the electronic device 100 can supplement missing data.

The effects described above are intended to aid understanding, and the effects of the embodiments of the present disclosure are not limited to the effects described above.

FIG. 4 illustrates a cell environment of an electronic device according to an embodiment.

Referring to FIG. 4, the electronic device 100 may be connected to the serving cell 290. For example, serving cell 290 may be associated with base station 280. For example, cells neighboring the serving cell 290 may be referred to as neighboring cells. In the example of FIG. 4, the first neighboring cell 291, the second neighboring cell 292, and the third neighboring cell 293 may be referred to as neighboring cells of the serving cell 290. The first neighboring cell 291 is associated with the first neighboring base station 281, the second neighboring cell 292 is associated with the second neighboring base station 282, and the third neighboring cell 293 is associated with the third neighboring base station. It can be related to (283). In the example of FIG. 4, for convenience of explanation, it is explained that one base station is associated with one cell. However, in one example, one base station may be associated with multiple cells.

Base stations 280, 281, 282, and 283 in FIG. 4 may be base stations that support any cellular wireless communication (eg, 3rd generation, 4th generation, and/or 5th generation wireless mobile communication). For example, the electronic device 100 may perform a group call while connected to the base station 280.

Referring to FIGS. 2 and 4 , according to one embodiment, the electronic device 100 may perform a group call based on MBMS or eMBMS. The electronic device 100 may perform a group call through the multicast bearer 272. For example, the serving cell 290 is a cell belonging to the first MSMB service area, and the base station 280 may be a base station that supports Multimedia Broadcast multicast service Single Frequency Network (MBSFN) transmission. For example, the first MBMS service area may include a plurality of cells. Base stations belonging to the same MBSFN can transmit data through the MBSFN based on timing synchronized between base stations.

Cells belonging to the same MBMS service area may have the same service area identifier (SAI). Across cells with the same SAI, the electronic device 100 can receive the same service (eg, group call) through the same MBSFN. For example, the electronic device 100 may perform a group call through the first MBSFN associated with the serving cell 290. For example, the electronic device 100 may move to the third neighboring cell 293. In one example, when the third neighboring cell 293 belongs to the first MBSFN, the SAI of the serving cell 290 and the SAI of the third neighboring cell 293 may be the same. In this case, the electronic device 100 can perform a group call using the multicast bearer 272 even after moving to the third neighboring cell 293. In one example, when the third neighboring cell 293 does not belong to the first MBSFN, the SAI of the serving cell 290 and the SAI of the third neighboring cell 293 are different, or the third neighboring cell 293 is in the MBSFN Transmission may not be supported. In this case, the electronic device 100 can perform a group call using the unicast bearer 271 after moving to the third neighboring cell 293.

According to one embodiment, the electronic device 100 may manage the unicast bearer 271 and/or the multicast bearer 272 based on communication quality associated with the group call. For example, the electronic device 100 may receive at least one threshold value from the network 299. Below, with reference to FIG. 5, a bearer management method based on the communication quality of the electronic device 100 may be described.

In FIG. 4, for convenience of explanation, a serving cell, a neighboring cell, a base station, and a neighboring base station are described, but embodiments of the present disclosure are not limited thereto. For example, when the electronic device 100 is handed over from the serving cell 290 to the third neighboring cell 293, the third neighboring cell 293 may become the serving cell of the electronic device 100.

Figure 5 shows changes in communication quality according to one embodiment.

Referring to FIGS. 3 and 5 , according to one embodiment, the electronic device 100 may identify communication quality associated with a group call. For example, the electronic device 100 may identify communication quality by measuring the reception quality of a signal associated with a group call. For example, the electronic device 100 may identify communication quality by receiving communication quality from a serving cell (eg, serving cell 290 in FIG. 4). The communication quality associated with the group call is Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Noise Ratio (SNR), Signal-to-Interference plus Noise Ratio (SINR), and/or BLER. (Block Error Rate) may be included. The communication quality associated with the group call may include the communication quality of the MBSFN. For example, the communication quality associated with the group call may include MBSFN RSRP.

According to one embodiment, the electronic device 100 may receive at least one threshold related to the communication quality of a group call from a network (eg, the base station 280 of FIG. 4). For example, the electronic device 100 may receive the first threshold Th1 and the second threshold Th2 from the network. For example, the electronic device 100 may receive at least one threshold related to communication quality through Radio Resource Control (RRC) signaling.

Referring to FIGS. 2 and 5 , at time t0, the electronic device 100 may perform a group call using the multicast bearer 272. For example, the electronic device 100 may perform a group call by receiving an MBSFN subframe from the base station of the serving cell (e.g., base station 280 in FIG. 4).

At time t1, the communication quality associated with the group call may fall below the first threshold Th1. Instead of changing the multicast bearer 272 to the unicast bearer 271, the electronic device 100 may establish the unicast bearer 271 while maintaining the multicast bearer 272. Seamless bearer switching can be performed by establishing the unicast bearer 271 before releasing the multicast bearer 272. When performing a group call using the unicast bearer 271, the electronic device 100 can receive data associated with the group call through a general subframe rather than an MBSFN subframe.

According to one embodiment, the electronic device 100 may determine whether to maintain the multicast bearer 272 based on the SAI of a neighboring cell. For example, if the multicast bearer 272 is released immediately after establishment of the unicast bearer 271, when communication quality improves, the electronic device 100 performs the procedure for establishing the multicast bearer 272 again. may need to be performed. In this case, the electronic device 100 can reduce unnecessary bearer establishment procedures by determining whether to maintain the multicast bearer 272 based on the SAI of the neighboring cell. A method for determining the multicast bearer 272 of the electronic device 100 may be described later with reference to FIGS. 6 and 9.

At time t2, the communication quality associated with the group call may be improved above the first threshold Th1. Even if the multicast bearer 272 is released at time t1, the electronic device 100 may not re-establish the multicast bearer 272. For example, in order to prevent repeated release and establishment of bearers, the electronic device 100 may establish the multicast bearer 272 when communication quality improves to the second threshold (Th2) or more at time t3. For example, the second threshold Th2 may indicate relatively higher communication quality than the first threshold Th1. In this case, the electronic device 100 may release the unicast bearer 271 after establishing the multicast bearer 272. Establishment of the unicast bearer 271 may be described later with reference to FIG. 7.

In one example, the electronic device 100 may maintain the unicast bearer 271 and the multicast bearer 272 for at least part of the time between time t1 and time t3. According to one embodiment, the electronic device 100 may receive data associated with a group call through the unicast bearer 271 and the multicast bearer 272. The electronic device 100 can perform a group call using data received through the unicast bearer 271 and data received through the multicast bearer 272. Performance of a group call using the unicast bearer 271 and the multicast bearer 272 may be described later with reference to FIG. 8.

FIG. 6 illustrates a flowchart of a group call connection management method based on neighboring cell information of an electronic device, according to an embodiment.

Referring to FIGS. 3 and 6 , according to one embodiment, the electronic device 100 may manage the connection (eg, bearer) of a group call based on neighboring cell information (eg, SAI of the neighboring cell). In the embodiment of FIG. 6, the electronic device 100 may be assumed to perform a group call through a multicast bearer (eg, multicast bearer 272 in FIG. 2).

In operation 605, the electronic device 100 may receive a threshold value of a serving cell (eg, serving cell 290 of FIG. 4). For example, the electronic device 100 may receive at least one threshold related to the communication quality of a group call from a network (eg, base station 280 in FIG. 4). For example, the electronic device 100 may receive the first threshold Th1 and the second threshold Th2 described above with reference to FIG. 5 from the network. For example, the electronic device 100 may receive a signal including information about the threshold from a base station (eg, base station 280 in FIG. 4) using the communication circuit 140. The electronic device 100 may store information about the received threshold in the memory 130.

In operation 610, the electronic device 100 may determine whether the communication quality associated with the group call is less than a first threshold. For example, the electronic device 100 may identify communication quality by measuring the reception quality of a signal associated with a group call. For example, the electronic device 100 may identify communication quality by receiving communication quality from a serving cell (eg, serving cell 290 in FIG. 4). Communication quality associated with the group call may include RSRP, RSRQ, SNR, SINR, and/or BLER. The communication quality associated with the group call may include the communication quality of the MBSFN. For example, the communication quality associated with the group call may include MBSFN RSRP.

If the communication quality is greater than or equal to the first threshold (e.g., operation 610-No), the electronic device 100 may continue to monitor the communication quality. If the communication quality is less than the first threshold (e.g., operation 610 - Yes), in operation 615, the electronic device 100 may determine whether the SAI value of the neighboring cell is the same as the SAI value of the serving cell. For example, the electronic device 100 may receive the SAI of a neighboring cell through RRC signaling (eg, RRC signaling including a system information block (SIB)) from the neighboring cell or serving cell. For example, the electronic device 100 may identify the SAI of a neighboring cell from the SAI of the serving cell. The electronic device 100 may identify the SAI of a neighboring cell using the SAI information for each cell stored in the memory 130. The electronic device 100 may identify the SAI of neighboring cells mapped to the serving cell based on information stored in the memory 130. For example, the electronic device 100 may identify the SAI of neighboring cells from the service provider of the group call (eg, the operator of the server device 200 in FIG. 2).

For example, when there are a plurality of neighboring cells adjacent to the serving cell, the electronic device 100 determines that if at least one of the SAIs of the plurality of neighboring cells is the same as the SAI of the serving cell, the SAI value of the neighboring cell is that of the serving cell. It can be determined to be equal to the SAI value. If all SAIs of a plurality of neighboring cells are different from the SAI of the serving cell, the electronic device 100 may determine that the SAI value of the neighboring cell is not the same as the SAI value of the serving cell.

Referring to the example of FIG. 4, the SAI of the serving cell 290 may be the first value. In this case, when the SAI of at least one of the first neighboring cell 291, the second neighboring cell 292, or the third neighboring cell 293 has a first value, the electronic device 100 determines the SAI value of the neighboring cell. It may be determined to be equal to the SAI value of this serving cell. If the first neighboring cell 291, the second neighboring cell 292, and the third neighboring cell 293 do not all have the same SAI value as the first SAI, the electronic device 100 uses the SAI value of the neighboring cell as the serving It may be determined that it is not equal to the SAI value of the cell.

If the SAI value of the neighboring cell is the same as the SAI value of the serving cell (e.g., operation 615 - Yes), in operation 620, the electronic device 100 establishes a unicast bearer (e.g., unicast bearer 271 of 2). And, a multicast bearer (e.g., multicast bearer 272 in FIG. 2) can be maintained. In this case, the electronic device 100 can maintain the multicast bearer even after establishing the unicast bearer. Since there are cells in the vicinity that can support multicast bearers (e.g., cells with the same SAI), multicast bearers can be used even when the electronic device 100 moves to a neighboring cell. In case of temporary deterioration of communication quality, the electronic device 100 can reduce the procedure for re-establishing a multicast bearer by maintaining the multicast bearer. In this case, for example, the device 100 may perform a group call (e.g., operation 805 of FIG. 8) using a multicast bearer and a unicast bearer.

If the SAI value of the neighboring cell is different from the SAI value of the serving cell (e.g., operation 615-No), in operation 625, the electronic device 100 may establish a unicast bearer and release the multicast bearer. The electronic device 100 may release the multicast bearer after establishing the unicast bearer. Since there is no cell in the vicinity that can support a multicast bearer, the electronic device 100 may release the multicast bearer. In this case, the electronic device 100 can perform a group call using a unicast bearer.

Figure 7 shows a flowchart of a unicast bearer management method of an electronic device according to an embodiment.

Referring to FIGS. 3 and 7 , according to one embodiment, the electronic device 100 may manage group call connections (eg, bearers) based on communication quality. In the embodiment of FIG. 7, the electronic device 100 sends a group call through a unicast bearer (e.g., unicast bearer 271 in FIG. 2) and a multicast bearer (e.g., multicast bearer 272 in FIG. 2). It may be assumed that (e.g., operation 620 of FIG. 6) is performed.

In operation 705, the electronic device 100 may perform a group call using a unicast bearer and a multicast bearer. For example, the electronic device 100 may receive data associated with a group call while maintaining a unicast bearer and a multicast bearer.

In operation 710, the electronic device 100 may determine whether the communication quality associated with the group call is greater than or equal to a second threshold (eg, the second threshold Th2 in FIG. 5). The electronic device 100 may determine whether the communication quality associated with the group call is greater than or equal to the second threshold by identifying the communication quality associated with the multicast bearer. For example, the electronic device 100 may identify the communication quality associated with the group call from at least one of RSRP, RSRQ, SNR, SINR, or BLER associated with the MBSFN.

If the communication quality is less than the second threshold (e.g., operation 710-No), the electronic device 100 may continue to monitor the communication quality associated with the group call. If the communication quality is equal to or higher than the second threshold (e.g., operation 710 - Yes), the electronic device 100 may release the unicast bearer in operation 715. In this case, the electronic device 100 can perform a group call using a multicast bearer. Since the multicast bearer is maintained (e.g., operation 620 of FIG. 6), the electronic device 100 can continue to perform group calls without performing an additional multicast bearer establishment procedure.

Figure 8 shows a flowchart of a method of performing a group call in an electronic device according to an embodiment.

Referring to FIGS. 3 and 8 , according to one embodiment, the electronic device 100 may perform a group call using a unicast bearer and a multicast bearer. In the embodiment of FIG. 8, the electronic device 100 sends a group call through a unicast bearer (e.g., unicast bearer 271 in FIG. 2) and a multicast bearer (e.g., multicast bearer 272 in FIG. 2). It may be assumed that (e.g., operation 620 of FIG. 6 or operation 705 of FIG. 7) is performed.

In operation 805, the electronic device 100 may perform a group call using a unicast bearer and a multicast bearer. For example, the electronic device 100 may receive data associated with a group call while maintaining a unicast bearer and a multicast bearer.

In operation 810, the electronic device 100 may determine whether an error exists in data received through a unicast bearer. For example, the electronic device 100 fails to perform a cyclic redundancy check (CRC) of data received through a unicast bearer, fails to receive data through a unicast bearer, or fails to receive data through a unicast bearer. If decoding fails, it can be determined that there is an error in the data.

If an error exists in the data received through the unicast bearer (e.g., operation 810-Yes), in operation 815, the electronic device 100 uses the data received through the unicast bearer and the multicast bearer to generate a group call. can be performed. For example, the electronic device 100 may combine at least a portion of first data received through a unicast bearer and at least a portion of second data received through a multicast bearer. Using the combined data, the electronic device 100 may attempt to decode the data. By combining data, the data error rate can be reduced.

If there is no error in the data received through the unicast bearer (e.g., operation 810-No), in operation 820, the electronic device 100 performs a group call using the data received through the unicast bearer. You can. In this case, the electronic device 100 may discard the data received through the multicast bearer without performing decoding.

Figure 9 shows a flowchart of a multicast bearer management method for an electronic device according to an embodiment.

Referring to FIGS. 3 and 9 , according to one embodiment, the electronic device 100 may manage multicast bearers based on the SAI of the handed over cell. In the embodiment of FIG. 9, the electronic device 100 sends a group call through a unicast bearer (e.g., unicast bearer 271 in FIG. 2) and a multicast bearer (e.g., multicast bearer 272 in FIG. 2). It may be assumed that (e.g., operation 620 of FIG. 6 or operation 705 of FIG. 7) is performed.

In operation 905, the electronic device 100 may perform a group call using a unicast bearer and a multicast bearer. For example, the electronic device 100 may receive data associated with a group call while maintaining a unicast bearer and a multicast bearer.

In operation 910, the electronic device 100 may be handed over from the first cell to the second cell. For example, the electronic device 100 may be handed over to a second cell according to the movement of the electronic device 100.

In operation 915, the electronic device 100 may determine whether the SAI of the second cell is the same as the SAI of the first cell. For example, the electronic device 100 may acquire SAI information of the second cell through RRC signaling from a base station associated with the second cell.

If the SAI of the first cell and the SAI of the second cell are the same (e.g., operation 915-YES), in operation 920, the electronic device 100 may maintain the unicast bearer and the multicast bearer. In this case, as described above with reference to FIG. 7, if the group call-related communication quality measured in the second cell is greater than or equal to the second threshold, the electronic device 100 releases the unicast bearer (e.g., operation 715). You can.

If the SAI of the first cell and the SAI of the second cell are different (e.g., operation 915-NO), the electronic device 100 may release the multicast bearer in operation 925. The electronic device 100 can perform a group call using a unicast bearer. For example, at least one of the neighboring cells of the first cell may have a cell with the same SAI as the SAI of the first cell. In this case, the electronic device 100 may maintain the multicast bearer even after establishing the unicast bearer based on the SAI of the neighboring cell (e.g., operation 620 of FIG. 6). This is because the electronic device 100 may be handed over to a neighboring cell with the same SAI. However, when handed over to a neighboring cell (eg, a second cell) that has a different SAI or does not belong to the MBSFN, the electronic device 100 may release the multicast bearer.

FIG. 10 is a block diagram of an electronic device 1001 in a network environment 1000, according to various embodiments. Referring to FIG. 10, in the network environment 1000, the electronic device 1001 communicates with the electronic device 1002 through a first network 1098 (e.g., a short-range wireless communication network) or a second network 1099. It is possible to communicate with at least one of the electronic device 1004 or the server 1008 through (e.g., a long-distance wireless communication network). According to one embodiment, the electronic device 1001 may communicate with the electronic device 1004 through the server 1008. According to one embodiment, the electronic device 1001 includes a processor 1020, a memory 1030, an input module 1050, an audio output module 1055, a display module 1060, an audio module 1070, and a sensor module ( 1076), interface (1077), connection terminal (1078), haptic module (1079), camera module (1080), power management module (1088), battery (1089), communication module (1090), subscriber identification module (1096) , or may include an antenna module 1097. In some embodiments, at least one of these components (eg, the connection terminal 1078) may be omitted, or one or more other components may be added to the electronic device 1001. In some embodiments, some of these components (e.g., sensor module 1076, camera module 1080, or antenna module 1097) are integrated into one component (e.g., display module 1060). It can be.

The processor 1020, for example, executes software (e.g., program 1040) to operate at least one other component (e.g., hardware or software component) of the electronic device 1001 connected to the processor 1020. It can be controlled and various data processing or calculations can be performed. According to one embodiment, as at least part of the data processing or computation, the processor 1020 stores instructions or data received from another component (e.g., the sensor module 1076 or the communication module 1090) in the volatile memory 1032. The commands or data stored in the volatile memory 1032 can be processed, and the resulting data can be stored in the non-volatile memory 1034. According to one embodiment, the processor 1020 may include a main processor 1021 (e.g., a central processing unit or an application processor) or an auxiliary processor 1023 that can operate independently or together (e.g., a graphics processing unit, a neural network processing unit ( It may include a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor). For example, if the electronic device 1001 includes a main processor 1021 and a auxiliary processor 1023, the auxiliary processor 1023 may be set to use lower power than the main processor 1021 or be specialized for a designated function. You can. The auxiliary processor 1023 may be implemented separately from the main processor 1021 or as part of it.

The auxiliary processor 1023 may, for example, act on behalf of the main processor 1021 while the main processor 1021 is in an inactive (e.g., sleep) state, or while the main processor 1021 is in an active (e.g., application execution) state. ), together with the main processor 1021, at least one of the components of the electronic device 1001 (e.g., the display module 1060, the sensor module 1076, or the communication module 1090) At least some of the functions or states related to can be controlled. According to one embodiment, coprocessor 1023 (e.g., image signal processor or communication processor) may be implemented as part of another functionally related component (e.g., camera module 1080 or communication module 1090). there is. According to one embodiment, the auxiliary processor 1023 (eg, neural network processing unit) may include a hardware structure specialized for processing artificial intelligence models. Artificial intelligence models can be created through machine learning. This learning may be performed, for example, in the electronic device 1001 itself on which the artificial intelligence model is performed, or may be performed through a separate server (e.g., server 1008). Learning algorithms may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but It is not limited. An artificial intelligence model may include multiple artificial neural network layers. Artificial neural networks include deep neural network (DNN), convolutional neural network (CNN), recurrent neural network (RNN), restricted boltzmann machine (RBM), belief deep network (DBN), bidirectional recurrent deep neural network (BRDNN), It may be one of deep Q-networks or a combination of two or more of the above, but is not limited to the examples described above. In addition to hardware structures, artificial intelligence models may additionally or alternatively include software structures.

The memory 1030 may store various data used by at least one component (eg, the processor 1020 or the sensor module 1076) of the electronic device 1001. Data may include, for example, input data or output data for software (e.g., program 1040) and instructions related thereto. Memory 1030 may include volatile memory 1032 or non-volatile memory 1034.

The program 1040 may be stored as software in the memory 1030 and may include, for example, an operating system 1042, middleware 1044, or application 1046.

The input module 1050 may receive commands or data to be used in a component of the electronic device 1001 (e.g., the processor 1020) from outside the electronic device 1001 (e.g., a user). The input module 1050 may include, for example, a microphone, mouse, keyboard, keys (eg, buttons), or digital pen (eg, stylus pen).

The sound output module 1055 can output sound signals to the outside of the electronic device 1001. The sound output module 1055 may include, for example, a speaker or receiver. Speakers can be used for general purposes such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker or as part of it.

The display module 1060 can visually provide information to the outside of the electronic device 1001 (eg, a user). The display module 1060 may include, for example, a display, a hologram device, or a projector, and a control circuit for controlling the device. According to one embodiment, the display module 1060 may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of force generated by the touch.

The audio module 1070 can convert sound into an electrical signal or, conversely, convert an electrical signal into sound. According to one embodiment, the audio module 1070 acquires sound through the input module 1050, the sound output module 1055, or an external electronic device (e.g., directly or wirelessly connected to the electronic device 1001). Sound may be output through an electronic device 1002 (e.g., speaker or headphone).

The sensor module 1076 detects the operating state (e.g., power or temperature) of the electronic device 1001 or the external environmental state (e.g., user state) and generates an electrical signal or data value corresponding to the detected state. can do. According to one embodiment, the sensor module 1076 includes, for example, a gesture sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, It may include a temperature sensor, humidity sensor, or light sensor.

The interface 1077 may support one or more designated protocols that can be used to connect the electronic device 1001 directly or wirelessly with an external electronic device (eg, the electronic device 1002). According to one embodiment, the interface 1077 may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

The connection terminal 1078 may include a connector through which the electronic device 1001 can be physically connected to an external electronic device (eg, the electronic device 1002). According to one embodiment, the connection terminal 1078 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (eg, a headphone connector).

The haptic module 1079 can convert electrical signals into mechanical stimulation (e.g., vibration or movement) or electrical stimulation that the user can perceive through tactile or kinesthetic senses. According to one embodiment, the haptic module 1079 may include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

The camera module 1080 can capture still images and videos. According to one embodiment, the camera module 1080 may include one or more lenses, image sensors, image signal processors, or flashes.

The power management module 1088 can manage power supplied to the electronic device 1001. According to one embodiment, the power management module 1088 may be implemented as at least a part of, for example, a power management integrated circuit (PMIC).

The battery 1089 may supply power to at least one component of the electronic device 1001. According to one embodiment, the battery 1089 may include, for example, a non-rechargeable primary cell, a rechargeable secondary cell, or a fuel cell.

The communication module 1090 provides a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 1001 and an external electronic device (e.g., the electronic device 1002, the electronic device 1004, or the server 1008). It can support establishment and communication through established communication channels. Communication module 1090 operates independently of processor 1020 (e.g., an application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module 1090 may be a wireless communication module 1092 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 1094 (e.g., : LAN (local area network) communication module, or power line communication module) may be included. Among these communication modules, the corresponding communication module is a first network 1098 (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network 1099 (e.g., legacy It may communicate with an external electronic device 1004 through a telecommunication network such as a cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., LAN or WAN). These various types of communication modules may be integrated into one component (e.g., a single chip) or may be implemented as a plurality of separate components (e.g., multiple chips). The wireless communication module 1092 uses subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module 1096 to communicate within a communication network, such as the first network 1098 or the second network 1099. The electronic device 1001 can be confirmed or authenticated.

The wireless communication module 1092 may support 5G networks after 4G networks and next-generation communication technologies, for example, NR access technology (new radio access technology). NR access technology provides high-speed transmission of high-capacity data (enhanced mobile broadband (eMBB)), minimization of terminal power and access to multiple terminals (massive machine type communications (mMTC)), or ultra-reliable and low-latency (URLLC). -latency communications)) can be supported. The wireless communication module 1092 may support high frequency bands (e.g., mmWave bands), for example, to achieve high data rates. The wireless communication module 1092 uses various technologies to secure performance in high frequency bands, for example, beamforming, massive MIMO (multiple-input and multiple-output), and full-dimensional multiplexing. It can support technologies such as input/output (FD-MIMO: full dimensional MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module 1092 may support various requirements specified in the electronic device 1001, an external electronic device (e.g., electronic device 1004), or a network system (e.g., second network 1099). According to one embodiment, the wireless communication module 1092 supports peak data rate (e.g., 20 Gbps or more) for realizing eMBB, loss coverage (e.g., 164 dB or less) for realizing mmTC, or U-plane latency (e.g., 164 dB or less) for realizing URLLC. Example: Downlink (DL) and uplink (UL) each of 0.5 ms or less, or round trip 1 ms or less) can be supported.

The antenna module 1097 may transmit or receive signals or power to or from the outside (e.g., an external electronic device). According to one embodiment, the antenna module 1097 may include an antenna including a radiator made of a conductor or a conductive pattern formed on a substrate (eg, PCB). According to one embodiment, the antenna module 1097 may include a plurality of antennas (eg, an array antenna). In this case, at least one antenna suitable for the communication method used in the communication network, such as the first network 1098 or the second network 1099, is connected to the plurality of antennas by, for example, the communication module 1090. can be selected. Signals or power may be transmitted or received between the communication module 1090 and an external electronic device through the selected at least one antenna. According to some embodiments, in addition to the radiator, other components (eg, radio frequency integrated circuit (RFIC)) may be additionally formed as part of the antenna module 1097.

According to various embodiments, antenna module 1097 may form a mmWave antenna module. According to one embodiment, a mmWave antenna module includes a printed circuit board, an RFIC disposed on or adjacent to a first side (e.g., bottom side) of the printed circuit board and capable of supporting a designated high-frequency band (e.g., mmWave band); And a plurality of antennas (e.g., array antennas) disposed on or adjacent to the second side (e.g., top or side) of the printed circuit board and capable of transmitting or receiving signals in the designated high frequency band. can do.

At least some of the components are connected to each other through a communication method between peripheral devices (e.g., bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)) and signal ( (e.g. commands or data) can be exchanged with each other.

According to one embodiment, commands or data may be transmitted or received between the electronic device 1001 and the external electronic device 1004 through the server 1008 connected to the second network 1099. Each of the external electronic devices 1002 or 1004 may be of the same or different type as the electronic device 1001. According to one embodiment, all or part of the operations performed in the electronic device 1001 may be executed in one or more of the external electronic devices 1002, 1004, or 1008. For example, when the electronic device 1001 needs to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device 1001 may perform the function or service instead of executing the function or service on its own. Alternatively, or additionally, one or more external electronic devices may be requested to perform at least part of the function or service. One or more external electronic devices that have received the request may execute at least part of the requested function or service, or an additional function or service related to the request, and transmit the result of the execution to the electronic device 1001. The electronic device 1001 may process the result as is or additionally and provide it as at least part of a response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology can be used. The electronic device 1001 may provide an ultra-low latency service using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device 1004 may include an Internet of Things (IoT) device. Server 1008 may be an intelligent server using machine learning and/or neural networks. According to one embodiment, the external electronic device 1004 or server 1008 may be included in the second network 1099. The electronic device 1001 may be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

Electronic devices according to various embodiments disclosed in this document may be of various types. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to embodiments of this document are not limited to the above-described devices.

The various embodiments of this document and the terms used herein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various changes, equivalents, or replacements of the embodiments. In connection with the description of the drawings, similar reference numbers may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the above items, unless the relevant context clearly indicates otherwise. As used herein, “A or B”, “at least one of A and B”, “at least one of A or B”, “A, B or C”, “at least one of A, B and C”, and “A Each of phrases such as “at least one of , B, or C” may include any one of the items listed together in the corresponding phrase, or any possible combination thereof. Terms such as "first", "second", or "first" or "second" may be used simply to distinguish one component from another, and to refer to those components in other respects (e.g., importance or order) is not limited. One (e.g., first) component is said to be “coupled” or “connected” to another (e.g., second) component, with or without the terms “functionally” or “communicatively.” Where mentioned, it means that any of the components can be connected to the other components directly (e.g. wired), wirelessly, or through a third component.

The term “module” used in various embodiments of this document may include a unit implemented in hardware, software, or firmware, and is interchangeable with terms such as logic, logic block, component, or circuit, for example. It can be used as A module may be an integrated part or a minimum unit of the parts or a part thereof that performs one or more functions. For example, according to one embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

Various embodiments of the present document are one or more instructions stored in a storage medium (e.g., built-in memory 1036 or external memory 1038) that can be read by a machine (e.g., electronic device 1001). It may be implemented as software (e.g., program 1040) including these. For example, a processor (e.g., processor 1020) of a device (e.g., electronic device 1001) may call at least one command among one or more commands stored from a storage medium and execute it. This allows the device to be operated to perform at least one function according to the at least one instruction called. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. A storage medium that can be read by a device may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' only means that the storage medium is a tangible device and does not contain signals (e.g. electromagnetic waves). This term refers to cases where data is stored semi-permanently in the storage medium. There is no distinction between temporary storage cases.

According to one embodiment, methods according to various embodiments disclosed in this document may be included and provided in a computer program product. Computer program products are commodities and can be traded between sellers and buyers. The computer program product may be distributed in the form of a machine-readable storage medium (e.g. compact disc read only memory (CD-ROM)) or through an application store (e.g. Play Store™) or on two user devices (e.g. It can be distributed (e.g. downloaded or uploaded) directly between smart phones) or online. In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

According to various embodiments, each component (e.g., module or program) of the above-described components may include a single or plural entity, and some of the plurality of entities may be separately placed in other components. there is. According to various embodiments, one or more of the components or operations described above may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (eg, modules or programs) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each component of the plurality of components identically or similarly to those performed by the corresponding component of the plurality of components prior to the integration. . According to various embodiments, operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, or omitted. Alternatively, one or more other operations may be added.

Claims (10)

In electronic devices,
communication circuit;
Memory; and
Includes a processor,
When executed by the processor, the memory causes the processor to:
Receiving data of a group call session through a multicast bearer using the communication circuit,
If the communication quality associated with the group call session falls below a first threshold:
Add a unicast bearer for the group call session,
Receiving data associated with the group call session through the unicast bearer,
After adding the unicast bearer, the service area identifier (SAI) associated with the group call session of the serving cell of the electronic device and the at least one second SAI of at least one neighboring cell of the serving cell are used. An electronic device that stores instructions for determining whether to release a multicast bearer. According to claim 1,
The instructions, when executed by the processor, cause the processor to maintain the multicast bearer if at least one of the at least one second SAI and the first SAI are the same,
An electronic device that releases the multicast bearer if all of the at least one second SAI and the first SAI are different. According to claim 2,
The instructions, when executed by the processor, cause the processor to release the multicast bearer in response to establishment of the unicast bearer if both of the at least one second SAIs and the first SAI are different. ), an electronic device that allows. According to claim 2,
The instructions, when executed by the processor, cause the processor to maintain the multicast bearer after establishment of the unicast bearer if at least one of the at least one second SAI is the same as the second SAI, and An electronic device configured to receive data associated with the group call through at least one of the unicast bearer and the multicast bearer. According to claim 4,
The instructions, when executed by the processor, cause the processor to:
An electronic device that combines at least a portion of data received through the multicast bearer and at least a portion of data received through the unicast bearer. According to claim 4,
The instructions, when executed by the processor, cause the processor to:
While maintaining the multicast bearer and the unicast bearer, if the communication quality associated with the multicast bearer exceeds a second threshold, release the unicast bearer,
Receiving data associated with the group call through the multicast bearer,
The electronic device, wherein the second threshold is greater than the first threshold. According to claim 1,
The instructions, when executed by the processor, cause the processor to:
An electronic device configured to receive the first threshold from a first Multicast-Broadcast Single-Frequency Network (MBSFN) associated with the group call session. According to claim 7,
The instructions, when executed by the processor, cause the processor to receive data of the group call session from a content provider server connected to the first MBSFN. According to claim 1,
The instructions, when executed by the processor, cause the processor to:
While maintaining the unicast bearer and the multicast bearer, if the electronic device is handed over to a neighboring cell that does not include the first SAI, the electronic device releases the multicast bearer. According to claim 1,
The instructions, when executed by the processor, cause the processor to:
An electronic device configured to acquire the at least one second SAI from a serving cell of the electronic device, the at least one neighboring cell, or the memory.

Images