Method and device for multiple transmission and reception points beam failure recovery

A method of implementing beam failure recovery for a multi-transmission-and-reception-point (M-TRP) transmission including a first transmission from a first TRP and a second transmission from a second TRP may include: receiving a first set of reference signals (RSs) corresponding to the first TRP and a second set of RSs corresponding to the second TRP; determining that the first set of RSs indicates a beam failure instance (BFI) specific to the first TRP, and responsively updating a first BFI counter specific to the first TRP; determining that a beam failure with respect to the first TRP has occurred based on a count of the first BFI counter equaling or surpassing a first BFI counter threshold; and performing a BFR process for the first TRP responsive to determining that the beam failure with respect to the first TRP has occurred.

FIELD

The present disclosure relates generally to communication schemes and protocols, including communications involving multiple transmission and reception points (M-TRPs), and beam failure detection and beam failure recovery thereof.

BACKGROUND

Certain communications between network systems and devices (also referred to as user equipments (UEs)) performed according to the 3rdGeneration Partnership Project (3GPP) Fifth Generation (5G) or New Radio (NR) cellular communication standard involve transmissions from the network system over beams from different TRPs (e.g., different physical antennas or different antenna ports (e.g., on a same antenna)). The beams may be combined at or by a receiving UE. Such “M-TRP” transmissions may involve processing for beam failure detection and/or for beam failure recovery (BFR).

SUMMARY

According to some embodiments, a method of implementing beam failure recovery for an M-TRP transmission including a first transmission from a first TRP and a second transmission from a second TRP may include: receiving a first set of reference signals (RSs) corresponding to the first TRP and a second set of RSs corresponding to the second TRP; determining that the first set of RSs indicates a beam failure instance (BFI) specific to the first TRP, and responsively updating a first BFI counter specific to the first TRP; determining that a beam failure with respect to the first TRP has occurred based on a count of the first BFI counter equaling or surpassing a first BFI counter threshold; and performing a BFR process for the first TRP responsive to determining that the beam failure with respect to the first TRP has occurred.

According to some embodiments, a system includes a UE that includes a processing circuit. The processing circuit is configured to implement a method of BFR for an M-TRP transmission that includes a first transmission from a first TRP and a second transmission from a second TRP. The method includes: receiving a first set of RSs corresponding to the first TRP and a second set of RSs corresponding to the second TRP; determining that the first set of RSs indicates a BFI specific to the first TRP, and responsively updating a first BFI counter specific to the first TRP; determining that a beam failure with respect to the first TRP has occurred based on a count of the first BFI counter equaling or surpassing a first BFI counter threshold; and performing a BFR process for the first TRP responsive to determining that the beam failure with respect to the first TRP has occurred.

DETAILED DESCRIPTION

Certain embodiments described herein provide for improved beam failure detection and/or beam failure recovery for M-TRP transmissions. Such improvements may provide for, among other things, detecting and reporting beam failure upon failure of one of the TRP's beam(s), and implementing an appropriate BFR procedure. This can, for example, prevent a network from implementing scheduling dependent on the failed TRP, which may in turn improve the network's data throughput.

FIG.1illustrates an example embodiment of a communication system100configured for communications according to the 5G standard. The communication system100includes a network system102, and network104, and a UE106. The techniques described herein may be implemented by the communication system100, or by one or more components thereof.

The network system102may include a g Node B (gNB) device, and may be configured to schedule transmissions between the gNB and the UE, and to communicate with one or more other gNBs. The network system102may be a 5G network device. Note that the term “network system” may be used herein to refer to a network device or a plurality of network devices. The network system is not limited to referring to a single physical device, but may also refer to plurality of distributed devices (or components thereof) that perform networking functions.

The network104may include, for example, a large area network (LAN), such as a cellular communication network. The UE106may include, for example, any device configured to communicate via the network104(e.g., a mobile device, a smartphone, a tablet, a desktop, a laptop, a local area network (LAN) device that serves local devices and that connects them the network104(such as a router), an internet of things device, or any other appropriate communication device). Note that the term UE is not necessarily limited to a device that is operated by a user, and may refer to devices that operate independent of user control. The UE106may be configured to process communications that are transmitted by the network system102.

FIG.2illustrates an example embodiment of the network system102configured for M-TRP transmissions, and shows a beam failure of such a transmission. In the depicted example, different antenna ports of one or different channels of the transmission are within multiple TRPs (TRP202aand TRP202b), which are non-co-located.

M-TRP transmissions may be categorized into single downlink control information (DCI) and multi-DCI M-TRPs. In single-DCI M-TRP communications, a single physical downlink control channel (PDCCH) is transmitted from one of the TRPs and schedules one or multiple PDSCHs. In one transmission scheme different layers of a single PDSCH are transmitted from different TRPs. In other transmission schemes multiple PDSCHs (multiplexed in time or frequency domain) with the same transport block (TB) are transmitted where all the layers of a PDSCH are transmitted from one of the TRPs. Different PDSCHs among the multiple ones may be transmitted from different TRPs according to a pattern. In multi-DCI M-TRP communications, each TRP transmits its own PDCCH which schedules a PDSCH which is also transmitted from the ports within the same TRP. The example shown inFIG.2may pertain to either single-DCI M-TRP or multi-DCI M-TRP.

The following details some protocols for beam failure detection or BFR. The network system102may transmit a set of reference signals (RS)204afrom TRP202a, and may transmit a set of reference signals RS204bfrom TRP202b. RS204amay include a first subset of one or more RS q0(a) comprising beam failure detection (BFD) RSs such as one or more channel status information (CSI) RSs, which may be monitored or sampled by the UE106and may indicate a failure of a currently active beam from the TRP202a. The RS204amay further include a second subset of one or more RS q1(a) comprising new beam identification (NBI) RSs such as one or more CSI-RS and/or synchronization signal block (SSB) signals, which may be monitored or sampled by the UE106and may indicate a strength of one or more alternative candidate beams from the TRP202athat might be used in a BFR process.

Similarly, the RS204bmay include a first subset of one or more RS q0(b) comprising BFD CSI-RSs, which may be monitored or sampled by the UE106and may indicate a strength of a currently active beam from the TRP202b. The RS204bmay further include a second subset of one or more RS q1(b) comprising NBI CSI-RS and/or SSB signals, which may be monitored or sampled by the UE106and may indicate a strength of one or more alternative candidate beams from the TRP202bthat might be used in a BFR process.

FIG.1depicts a beam failure detected by the UE based on the UE's monitoring or sampling of the RS204a. Certain embodiments described herein provide for the UE determining that the RS204acorresponds specifically to the TRP202a(and not corresponding to the TRP202b), thus allowing the UE to determine that the beam failure occurred on a beam that corresponds to the TRP202a(and not the TRP202b). The UE may thus implement a BFR protocol accordingly (e.g., as described herein).

Certain 5G processes may be improved by the TRP-specific processes described herein. For example, certain 5G processes do not provide for the UE determining which TRP a failed beam correspond to, in an M-TRP scenario. Furthermore, certain 5G processes do not provide for the UE readily selecting a replacement beam that is optimized for the specific failed TRP, in a BFR process. Yet further, certain 5G processes sub-optimally count an insufficient number of beam failure instances (which may be used to detect beam failure). For example, a beam from a first TRP may be associated with RSs that would, on their own, indicate that the beam from the first TRP has failed. However, if RSs associated with the second TRP are strong enough that they would not, on their own, indicate that the beam from the second TRP has failed, the UE might not count such a scenario as a beam failure instance, and beam failure may then sub-optimally not be declared in a scenario where the first beam has failed.

The present disclosure provides for, among other things, improved processes and devices that can ameliorate or solve the above-mentioned potential problems. Certain processes described herein include beam failure detection and/or recovery performed on a per-TRP basis.

FIG.3illustrates an example embodiment of a beam failure process300in an M-TRP scenario (e.g., the scenario shown inFIG.2), including beam failure detection specific to a first TRP (blocks302-308), and beam failure recovery specific to the first TRP (block310). For example, the UE106may use RS204ato detect a beam failure of the TRP202aand to implement BFR for the TRP202a, or may use RS204bto detect a beam failure of the TRP202band to implement BFR for the TRP202b, as discussed in more detail below.

In some embodiments, the UE106may be configured with a first set of parameters specific to the TRP202a(e.g., configured by the network system102). The first set of parameters may include any one or more of periodic CSI-RS resource indices or SSB indices corresponding to the TRP202aand the RS204a, a signal power threshold (e.g., a reference signal received power (RSRP) threshold) specific to the TRP202a, a beam failure instance (BFI) counter threshold specific to the TRP202a, or a BFI timing window specific to the TRP202a. The UE106may use the first set of parameters in the beam failure process300(e.g., as discussed below) to implement beam failure detection and/or BFR specific to the TRP202a. The UE106may be similarly configured with a second set of parameters specific to the TRP202b. The second set of parameters may include any one or more of periodic CSI-RS resource indices or SSB indices corresponding to the TRP202band the RS204b, a signal power threshold (e.g., a reference signal received power (RSRP) threshold) specific to the TRP202b, a BFI counter threshold specific to the TRP202b, or a BFI timing window specific to the TRP202b. The UE106may use the first set of parameters in the beam failure process300(e.g., as discussed below) to implement beam failure detection and/or BFR specific to the TRP202b.

In some embodiments, the UE106determines that the RS204ais specific to TRP202a, and determines that the RS204bis specific to the TRP202b. The UE may determine this via implicit indication of which TRPs the RSs204aand204bcorrespond to, or may determine this via explicit indication, as discussed in more detail below. The UE106may make use of this known correspondence in the beam failure process300, for example.

In some embodiments, the UE may determine that the RS204ais specific to TRP202aand that the RS204bis specific to the TRP202bby implicit indication as follows. The UE may be configured with a first Core Resource Set (CORESET) corresponding to the TRP202a, and a second CORESET corresponding to the TRP202b. The UE106may determine that the RS204ais associated with a first transmission configuration indication (TCI) state corresponding to the first CORESET, and the UE106may determine based on this that the RS204acorresponds to the TRP202a. Similarly, the UE106may determine that the RS204bis associated with a second transmission configuration indication (TCI) state corresponding to the second CORESET, and the UE106may determine based on this that the RS204bcorresponds to the TRP202b.

In some embodiments, the UE106may determine that the RS204ais specific to TRP202aand that the RS204bis specific to the TRP202bby explicit indication from the network system102. For example, a gNB of the network system102may indicate to the UE106(e.g., via radio resource control (RRC) signaling) that the RS204ais associated with the TRP202aand/or that the RS204bis associated with the TRP202b.

Referring to the example beam failure process300shown inFIG.3, at block302, the UE106monitors the RS204a(e.g., samples the RS204aat predetermined timings or on another schedule), which corresponds to the TRP202a(e.g., is transmitted from the TRP202a). As discussed above in reference toFIG.2, the RS204amay include a first subset of one or more RS q0(a) comprising BFD RSs such as one or more CSI-RSs, which may be monitored by the UE106and may indicate a strength of a currently active beam from the TRP202a. Monitoring the RS204amay include determining the respective RSRPs of the one or more CSI-RSs. Monitoring the RS204amay be performed by the UE106based on the periodic CSI-RS resource indices of the first set of parameters corresponding to the TRP202a.

At block304, the UE106determines that a BFI has occurred for the TRP202a. In some embodiments, the BFI is determined to have occurred when all the RSRPs of the CSI-RSs of the RS q0(a) subset are below an RSRP threshold (e.g., the signal power threshold specified by the first set of parameters specific to the TRP202a). In other embodiments, the BFI may be determined to have occurred if one or more of the RSRPs of the CSI-RSs of the RS q0(a) subset are below the RSRP threshold. The UE106may determine that the BFI corresponds to, or occurred for, the TRP202aspecifically, in response to the BFI being detected based on the RS q0(a) which are specific to (e.g., transmitted from) the TRP202a. When the UE106determines that the BFI has occurred, the process proceeds to block306.

At block306, the UE106increments a BFI counter that is specific to the TRP202a(e.g., which is incremented based on TRP202aBFIs and not based on TRP202bBFIs), and the process proceeds to block308. In some embodiments, the UE106is configured with a respective BFI counter for each of the TRPs in the M-TRP scenario (e.g., one BFI counter specific to BFIs of TRP202a, and one BFI counter specific to BFIs of TRP202b).

At block308, the UE106determines whether the BFI counter is at or above a BFI counter threshold (e.g., the BFI counter threshold specified in the first set of parameters specific to the TRP202a). If the BFI counter is not at or above the BFI counter threshold, the process proceeds to block302, and the UE106continues to monitor the RS q0(a). If the BFI counter is at or above the BFI counter threshold, the UE106proceeds to block310to implement a BFR process.

In some embodiments, the BFI counter is reset at the end of a BFI timing window or timing period (e.g., the BFI timing window specified by the first set of parameters specific to the TRP202a). Thus, the UE106implements BFR when the BFI counter is incremented to meet or exceed the BFI counter threshold within the timing window (e.g., when a threshold number of BFIs are detected within the timing window). In some embodiments, the UE106determines whether the BFI counter is at or above the BFI counter threshold at the expiration of the timing window, and determines whether to proceed to block302or to block310at that time. In other implementations, as shown inFIG.3, the UE106determines whether the BFI counter is at or above the BFI counter threshold each time the BFI counter is incremented.

At block310, the UE implements a BFR process. The BFR process may be specific to the particular TRP. Some example embodiments of the BFR process are described herein with respect toFIG.4.

FIG.3shows an embodiment of a beam failure process300specific to a particular TRP, which as discussed above, provides for detecting and reporting beam failure and implementing an appropriate BFR procedure. This can, for example, prevent a network from implementing scheduling dependent on a failed TRP, which may in turn improve the network's data throughput. In some implementations, TRP-specific beam failure detection and corresponding TRP-specific BFR may be implemented for both a first TRP and a second TRP (e.g., a first beam failure process300may be implemented specifically for the TRP202ausing RS204a, and a second beam failure process300may be implemented specifically for the TRP202busing RS204b).

Referring now toFIG.4,FIG.4shows an example embodiment of a BFR process400that includes sending BFR information via physical uplink control channel (PUCCH). The BFR process400may be implemented, for example, in block310ofFIG.3. The BFR process400may be a BFR process specific to a particular TRP. For example, the BFR process400may be implemented by the UE106responsive to the UE106determining that beam failure has occurred specifically for the TRP202a(e.g., responsive to the UE106determining that beam failure has occurred based on monitoring of RS q0(a)), and the BFR process400may select a candidate replacement beam for the using the NBI RSs of the second subset RS q1(a), which are specific to the TRP202a. The BFR process400may additionally or alternatively be implemented by the UE106responsive to the UE106determining that beam failure has occurred specifically for the TRP202b(e.g., responsive to the UE106determining that beam failure has occurred based on monitoring of RS q0(b)), and the BFR process400may select a candidate replacement beam for the using the NBI RSs of the second subset RS q1(b), which are specific to the TRP202b. In this sense, the RS q0(a)) pertaining to the TRP202amay be said to have a one-to-one association with the RS q1(a)), and the RS q0(b)) pertaining to the TRP202bmay be said to have a one-to-one association with the RS q1(b)). By having such a one-to-one association, BFR may be readily implemented in a manner specific to a TRP.

The BFR process400includes, following a determination that a particular TRP (e.g., the TRP202a) experienced beam failure, the UE106sending the network system102a BFR request via PUCCH at block402. The BFR request may include a scheduling request (SR) on a PUCCH resource carrying a link recovery request (LRR). The UE106may be configured for the PUCCH transmission via RRC. The configuration may include a first configuration specific to the TRP202awhereby the BFR request may be sent to the TRP202a, and a second configuration to specific to the TRP202bwhereby the BFR request may be sent to the TRP202b. Using the appropriate configuration, the UE106may send the BFR request to one of the TRP202aand TRP202bfor which beam failure was not detected. For example, if a beam failure specific to TRP202awas detected, the UE106may responsively send the BFR request to the TRP202b. This helps to assure that the BFR request is received by the network system102. In an alternative embodiment, a common configuration may be implemented in which single designated on of the TRPs receives the SR, and transfers relevant information to the other TRP. In another alternative embodiment, the UE may attempt to send the SR to both TRPs.

At block404, the UE106receives, from the network system102, a physical uplink shared channel (PUSCH) schedule via PDCCH. The PUSCH schedule may indicate a media access control (MAC) control element (CE) PUSCH that the UE may use to transmit BFR information.

At block406, the UE106sends BFR information to the network system102via PUSCH transmission, according to the schedule received at block404. The PUSCH transmission may be a MAC CE PUSCH transmission. The BFR information may include information specific to the TRP202aand/or the TRP202b, and may include, for example, the indices of SCells with detected beam failure (e.g., SCells for which beam failure was detected based on corresponding one or more of the RS q0(a)) or the RS q0(b)), indication of presence of qnewfor the corresponding SCells, and index of qnewfor the corresponding SCells (e.g., new candidate beams selected based on corresponding RS q1(a)) or RS q1(b)).

Although the BFR process400involves the UE106sending the network system102BFR information via PUCCH, the BFR process may be implemented in other suitable ways. For example, the UE106may perform a random-access channel (RACH) procedure. This may involve the UE106performing the RACH procedure for BFR specifically for the TRP202aaccording to a selected RS index from those indices in the set RS q1(a) whose RSRP values are above the relevant threshold (e.g., a threshold specific to the TRP202a). In some embodiments, the RACH configuration for BFR may be a single configuration while certain RACH occasions (ROs) and certain physical random access channel (PRACH) preambles are linked to each of RS q1(a) and RS q1(b). Using this protocol, the TRP202aand the TRP202bmay each receive an intended PRACH transmission corresponding the appropriate one of RS q1(a) and RS q1(b). In some embodiments, such single RACH configuration may involve tight coordination between TRPs which may not be readily achieved. As an alternative then, separate RACH configurations linked with each of RS q1(a) and RS q1(b) may be utilized.

Some additional example embodiments are described below.

In some embodiments, no selection decoding/soft combining of a failed TRP candidate may be implemented with repeated PDCCH. In such embodiments, if the UE106reports beam failure to a higher layer and before completion of BFR, if the UE106is configured to receive PDCCHs which are repeated in same or multiple synchronization signal (SS) sets, the UE106monitors the PDCCHs among linked candidates using the following process. If a set A of PDCCH candidates are linked to a set B, and the set A is associated with a TRP that experienced beam failure, the UE106does not monitor the PDCCH candidates in the set A. The UE does not perform soft-combining, and monitors the candidates in set B. A similar technique may be applied to the reception of repeated PDSCHs.

In some embodiments, no selection decoding/soft combining of the failed TRP candidate may be implemented using multi-chance PDCCH. In such embodiments, if the UE106reports beam failure to a higher layer and before completion of BFR, if the UE106is configured to receive PDCCHs which are transmitted in a multi-chance scheme in same or multiple SS sets, the UE106monitors the PDCCHs among the candidates using the following process. If a set of PDCCH candidates are associated with a TRP that experienced beam failure, the UE does not monitor the PDCCH candidates. A similar technique may be applied to the reception of repeated PDSCHs.

In some embodiments, no selection decoding/soft combining of the failed TRP candidate may be implemented using certain PDSCH schemes. In such embodiments, if the UE106reports beam failure to a higher layer and before completion of BFR, if the UE106is configured to receive multi-TRP PDSCH, the UE receives the PDCCHs using the following process. If the PDSCH transmission scheme is single DCI, the UE106does not receive the PDSCH occasion with the TCI state associated with the failed TRP. If the PDSCH transmission scheme is such that a single PDSCH occasion is associated with two TRPs with two different TCI states, the UE106is not expected to the receive the PDSCH, perform channel estimation and demodulation on the set of REs (RBs) or resources which are transmitted with the TCI state of the failed TRP.

If the PDSCH transmission scheme is multi-DCI, the UE106does not receive the PDSCH occasion with the TCI state associated with the failed TRP. The association of the TCI states to the TRPs may be according to the value of CORSETPoolIndex of the CORSET scheduling the PDSCH.

A similar behavior may be defined when the UE106transmits PUSCH/PUCCH with two different TCI states. In such a scenario, the UE106is not expected to transmit the PUSCH/PUCCH which are associated with the failed TRP.

FIG.5shows an example of a system500configured to manage M-TRP beam failure reporting and/or beam failure recovery, according to some embodiments. Referring toFIG.5, the electronic device501(which may be similar to, or the same as, the UE106) in the system500may communicate with an electronic device502via a first network598(e.g., a short-range wireless communication network, such as a Wi-Fi network), or an electronic device504or a server508(which may be similar to, or the same as, the network system102) via a second network599(which may be similar to, or the same as, the network104), such as a long-range wireless communication network (e.g., a cellular communication network, such as a 5G network). The electronic device501may communicate with the electronic device504via the server508. The electronic device501may include a processor520, a memory530, an input device550, a sound output device555, a display device560, an audio module570, a sensor module576, an interface577, a haptic module579, a camera module580, a power management module588, a battery589, a communication module590, a subscriber identification module (SIM)596, and/or an antenna module597. In one embodiment, at least one of the components (e.g., the display device560or the camera module580) may be omitted from the electronic device501, or one or more other components may be added to the electronic device501. In one embodiment, some of the components may be implemented as a single integrated circuit (IC). For example, the sensor module576(e.g., a fingerprint sensor, an iris sensor, or an illuminance sensor) may be embedded in the display device560(e.g., a display), or the display device560may include one or more sensors in addition to the sensor module576.

In some embodiments, the electronic device501may include a computing device or processor configured to implement M-TRP beam failure reporting and/or beam failure recovery, such as the methods of managing M-TRP beam failure reporting and/or beam failure recovery described herein.

The processor520may execute, for example, software (e.g., a program540) to control at least one other component (e.g., a hardware or a software component) of the electronic device501coupled with the processor520, and may perform various data processing and/or computations. As at least a part of the data processing and/or computations, the processor520may load a command or data received from another component (e.g., the sensor module576or the communication module590) in volatile memory532, process the command or the data stored in the volatile memory532, and store resulting data in non-volatile memory534. The processor520may include a main processor521(e.g., a central processing unit (CPU) or an application processor (AP)), and an auxiliary processor523(e.g., a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that is operable independently from, or in conjunction with, the main processor521. Additionally or alternatively, the auxiliary processor523may be adapted to consume less power than the main processor521, and/or execute a particular function. The auxiliary processor523may be implemented as being separate from, or as a part of, the main processor521.

The auxiliary processor523may control at least some of the functions or states related to at least one component (e.g., the display device560, the sensor module576, or the communication module590) from among the components of the electronic device501, instead of the main processor521while the main processor521is in an inactive (e.g., sleep) state, or together with the main processor521while the main processor521is in an active state (e.g., executing an application). According to one embodiment, the auxiliary processor523(e.g., an image signal processor or a communication processor) may be implemented as a part of another component (e.g., the camera module580or the communication module590) functionally related to the auxiliary processor523.

The memory530may store various data used by at least one component (e.g., the processor520or the sensor module576) of the electronic device501. The various data may include, for example, software (e.g., the program540) and input data or output data for a command related thereto. The memory530may include the volatile memory532and/or the non-volatile memory534.

The program540may be stored in the memory530as software, and may include, for example, an operating system (OS)542, middleware544, or an application546.

The input device550may receive a command or data to be used by another component (e.g., the processor520) of the electronic device501, from the outside (e.g., a user) of the electronic device501. The input device550may include, for example, a microphone, a mouse, and/or a keyboard.

The sound output device555may output sound signals to the outside of the electronic device501. The sound output device555may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as playing multimedia or recording, and the receiver may be used for receiving an incoming call. According to one embodiment, the receiver may be implemented as being separate from, or as a part of, the speaker.

The display device560may visually provide information to the outside (e.g., a user) of the electronic device501. The display device560may include, for example, a display, a hologram device, and/or a projector and control circuitry to control a corresponding one of the display, the hologram device, and the projector. According to one embodiment, the display device560may include touch circuitry adapted to detect a touch, or sensor circuitry (e.g., a pressure sensor) adapted to measure the intensity of force incurred by the touch.

The audio module570may convert a sound into an electrical signal and vice versa. According to one embodiment, the audio module570may obtain the sound via the input device550, and/or output the sound via the sound output device555or a headphone of an external electronic device502directly (e.g., wired) or wirelessly coupled with the electronic device701.

The sensor module576may detect an operational state (e.g., power or temperature) of the electronic device501and/or an environmental state (e.g., a state of a user) external to the electronic device501, and then generate an electrical signal or data value corresponding to the detected state. The sensor module576may include, for example, a gesture sensor, a gyro sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, and/or an illuminance sensor.

The interface577may support one or more specified protocols to be used for the electronic device501to be coupled with the external electronic device502directly (e.g., wired) or wirelessly. According to one embodiment, the interface577may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, and/or an audio interface.

A connecting terminal578may include a connector via which the electronic device501may be physically connected with the external electronic device502. According to one embodiment, the connecting terminal578may include, for example, an HDMI connector, a USB connector, an SD card connector, and/or an audio connector (e.g., a headphone connector).

The haptic module579may convert an electrical signal into a mechanical stimulus (e.g., a vibration or a movement) and/or an electrical stimulus which may be recognized by a user via tactile sensation or kinesthetic sensation. According to one embodiment, the haptic module579may include, for example, a motor, a piezoelectric element, and/or an electrical stimulator.

The camera module580may capture a still image or moving images. According to one embodiment, the camera module580may include one or more lenses, image sensors, image signal processors, and/or flashes.

The power management module588may manage power supplied to the electronic device501. The power management module588may be implemented as at least a part of, for example, a power management integrated circuit (PMIC).

The battery589may supply power to at least one component of the electronic device501. According to one embodiment, the battery589may include, for example, a primary cell which is not rechargeable, a secondary cell which is rechargeable, and/or a fuel cell.

The communication module590may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device501and the external electronic device (e.g., the electronic device502, the electronic device504, and/or the server508) and performing communication via the established communication channel. The communication module590may include one or more communication processors that are operable independently from the processor520(e.g., the AP) and may support a direct (e.g., wired) communication and/or a wireless communication. According to one embodiment, the communication module590may include a wireless communication module592(e.g., a cellular communication module, a short-range wireless communication module, and/or a global navigation satellite system (GNSS) communication module) or a wired communication module594(e.g., a local area network (LAN) communication module or a power line communication (PLC) module). A corresponding one of these communication modules may communicate with the external electronic device via the first network598(e.g., a short-range communication network, such as Bluetooth®, wireless-fidelity (Wi-Fi) direct, and/or a standard of the Infrared Data Association (IrDA)) or the second network599(e.g., a long-range communication network, such as a cellular network, the Internet, and/or a computer network (e.g., LAN or wide area network (WAN)). Bluetooth® is a registered trademark of Bluetooth SIG, Inc., Kirkland, WA These various types of communication modules may be implemented as a single component (e.g., a single IC), or may be implemented as multiple components (e.g., multiple ICs) that are separate from each other. The wireless communication module592may identify and authenticate the electronic device501in a communication network, such as the first network598or the second network599, using subscriber information (e.g., international mobile subscriber identity (IMSI)) stored in the subscriber identification module596.

The antenna module597may transmit and/or receive a signal and/or power to and/or from the outside (e.g., the external electronic device) of the electronic device501. According to one embodiment, the antenna module597may include one or more antennas, and, therefrom, at least one antenna appropriate for a communication scheme used in the communication network, such as the first network598and/or the second network599, may be selected, for example, by the communication module590(e.g., the wireless communication module592). The signal and/or the power may then be transmitted and/or received between the communication module590and the external electronic device via the selected at least one antenna.

At least some of the above-described components may be mutually coupled and communicate signals (e.g., commands and/or data) therebetween via an inter-peripheral communication scheme (e.g., a bus, a general purpose input and output (GPIO), a serial peripheral interface (SPI), and/or a mobile industry processor interface (MIPI)).

According to one embodiment, commands and/or data may be transmitted and/or received between the electronic device501and the external electronic device504via the server508coupled with the second network599. Each of the electronic devices502and504may be a device of a same type as, or a different type from, the electronic device501. All or some of operations to be executed at or by the electronic device501may be executed at one or more of the external electronic devices502,504, or the server508. For example, if the electronic device501should perform a function and/or a service automatically, or in response to a request from a user or another device, the electronic device501, instead of, or in addition to, executing the function and/or the service, may request the one or more external electronic devices to perform at least a part of the function and/or the service. The one or more external electronic devices receiving the request may perform the at least a part of the function and/or the service requested, and/or an additional function and/or an additional service related to the request, and transfer an outcome of the performing to the electronic device501. The electronic device501may provide the outcome, with or without further processing of the outcome, as at least a part of a reply to the request. To that end, a cloud computing, distributed computing, and/or client-server computing technology may be used, for example.

One embodiment may be implemented as software (e.g., the program540) including one or more instructions that are stored in a storage medium (e.g., internal memory536or external memory538) that is readable by a machine (e.g., the electronic device501). For example, a processor of the electronic device501may invoke at least one of the one or more instructions stored in the storage medium, and execute it, with or without using one or more other components under the control of the processor. Thus, a machine may be operated to perform at least one function according to the at least one instruction invoked. The one or more instructions may include code generated by a compiler or code executable by an interpreter. A machine-readable storage medium may be provided in the form of a non-transitory storage medium. The term “non-transitory” indicates that the storage medium is a tangible device, and does not include a signal (e.g., an electromagnetic wave), but this term does not differentiate between where data is semi-permanently stored in the storage medium and where the data is temporarily stored in the storage medium.

Herein, embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be noted that same or similar elements may be designated by the same reference numerals/letters even though they are shown in different drawings. In the description herein, specific details such as detailed configurations and components are provided to assist with the overall understanding of the embodiments of the present disclosure. Various changes and modifications of the embodiments described herein may be made without departing from the scope of the present disclosure. Certain detailed descriptions may be omitted for clarity and conciseness.

The present disclosure provides for various modifications and various embodiments. It should be understood that the present disclosure is not limited to the various embodiments explicitly described or detailed herein, and that the present disclosure includes modifications, equivalents, and alternatives within the scope of the present disclosure.

Although terms including an ordinal number such as first, second, etc., may be used for describing various elements, the elements are not restricted by such terms. Such terms are used to distinguish one element from another element, and do not imply any specific ordering. As used herein, the term “and/or” includes any and all combinations of one or more associated items. Singular forms are intended to include plural forms unless the context clearly indicates otherwise. In the present disclosure, it should be understood that the terms “include” or “have” indicate the existence of a feature, a number, a step, an operation, a structural element, a part, or a combination thereof, and do not exclude the existence or probability of the addition of one or more other features, numbers, steps, operations, structural elements, parts, or combinations thereof.

According to one embodiment, at least one component (e.g., a manager, a set of processor-executable instructions, a program, or a module) of the above-described components may include a single entity or multiple entities. One or more of the above-described components may be omitted, or one or more other components may be added. Alternatively or additionally, a plurality of components (e.g., a manager, a set of processor-executable instructions, a program, or a module) may be integrated into a single component. In this case, the integrated component may still perform one or more functions of each of the plurality of components in the same or similar manner as they are performed by a corresponding one of the plurality of components before the integration. Operations performed by the manager, the set of processor-executable instructions, the program, the module, or another component may be carried out sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations may be executed in a different order or omitted, or one or more other operations may be added.

While certain references are made herein to the 3GPP 5G specification, the techniques disclosed herein may be applied to or extended to other specifications, including cellular specifications (whether 3GPP or otherwise), such as the 3GPP 4G or LTE specification, any cellular specification that follows 5G (e.g., a 6G specification).