Method, device and system for managing incoming calls

Abstract

The present disclosure discloses a method and system for managing incoming calls by sending operable notifications. The method includes receiving, from a first device, a first call to a second device. The method includes detecting, among the plurality of devices, a third device to transmit an operable notification of the first call. The method includes detecting, by an acknowledgement from the third device for an action regarding the operable notification, and initiating a second call based on the detected action. The method includes simultaneously managing the first call and the second call via the conference call.

Description

Technical Field

[0001] This disclosure relates to methods, apparatus, and systems for managing incoming calls. For example, this disclosure relates to seamlessly transferring an incoming call from a caller's device to another device by sending an actionable notification. Background Technology

[0002] Call forwarding services are supplementary services typically offered in mobile devices. They are valuable tools for businesses and individuals seeking to effectively manage their incoming calls. By establishing call forwarding, users can redirect incoming calls to user-defined numbers, such as their mobile phone or another landline. This feature allows users to remain connected and accessible even when they are away from their mobile phone.

[0003] Typically, in call forwarding services, when an incoming call is received, it is automatically rerouted to a user-defined number. This can be done through various methods, such as using the mobile phone's settings or accessing a specific call forwarding service provided by the mobile operator. Therefore, by forwarding an incoming call to a user-defined number, the incoming call receives attention from the appropriate user associated with that user-defined number.

[0004] However, traditional call forwarding services are inherently static. For example, incoming calls are automatically forwarded to a user-defined number. This technology for forwarding incoming calls is inherently static because users cannot change the mobile number used for forwarding incoming calls at runtime.

[0005] Therefore, the aforementioned issues related to call transfer services need to be addressed. Summary of the Invention

[0006] Solution to the problem According to an example embodiment of this disclosure, a method for managing incoming calls in a called device is disclosed. The method includes: receiving a first call to a second device from a first device. The method includes: detecting a third device among a plurality of devices to transmit an operable notification of the first call. The method includes: detecting the operable notification by means of confirmation of an action from the third device regarding the operable notification, and initiating a second call based on the detected action. The method includes: simultaneously managing the first and second calls via a conference call.

[0007] According to an example embodiment of this disclosure, an apparatus for managing incoming calls in a called device is disclosed. The apparatus includes at least one processor, which includes processing circuitry, configured individually and / or collectively to receive a first call to a second device from a first device, and to detect a third device among a plurality of devices to transmit an operable notification of the first call. The at least one processor is configured individually and / or collectively to: detect an action from the third device regarding the operable notification, and to initiate a second call based on the detected action. The at least one processor is configured individually and / or collectively to: simultaneously manage the first and second calls via a conference call.

[0008] According to an example embodiment of this disclosure, a method for managing incoming calls in a called device is disclosed. The method includes: receiving an operable notification from a second device (B) for a first call originating from a third device (A). The method includes: sending an acknowledgment to the second device (B) regarding an action related to the operable notification, and initiating a second call based on the detected action. The method also includes: simultaneously managing the first and second calls via a conference call.

[0009] According to an example embodiment of this disclosure, an apparatus for managing incoming calls in a called device is disclosed. The apparatus includes at least one processor, which includes processing circuitry, and is individually and / or collectively configured to receive an operable notification from a second device (B) for a first call originating from a third device (A). One or more processors are configured to: send an acknowledgment to the second device (B) regarding an action related to the operable notification, and initiate a second call based on the detected action. At least one processor is individually and / or collectively configured to simultaneously manage the first and second calls via a conference call.

[0010] To further illustrate the advantages and features of this disclosure, a more detailed description will be presented with reference to various exemplary embodiments of the disclosure illustrated in the accompanying drawings. It should be understood that these drawings depict various exemplary embodiments and should therefore not be considered as limiting its scope. This disclosure and its various embodiments will be described and explained with reference to the accompanying drawings, incorporating additional features and details.

[0011] Beneficial effects of the invention The aspects of this disclosure at least address the aforementioned problems and / or disadvantages, and at least provide the advantages described below. Therefore, one aspect of this disclosure will provide an efficient communication method in a wireless communication system. Attached Figure Description

[0012] These and other features, aspects and advantages of certain embodiments of the present disclosure will become clearer from the accompanying drawings and the following detailed description, wherein the same characters denote the same parts throughout the drawings.

[0013] Figure 1 This is a diagram illustrating an example working environment for managing incoming calls according to various embodiments; Figure 2A This is a block diagram illustrating an example system architecture of a user equipment according to various embodiments; Figure 2B This is a block diagram illustrating example configurations of a user equipment according to various embodiments; Figure 3 This is a block diagram illustrating an example configuration of the module / engine of a user equipment according to various embodiments of FIG2; Figure 4 This is a block diagram illustrating an example configuration of a notification monitor module according to various embodiments; Figure 5 This is a block diagram illustrating an example configuration of a motion analyzer module according to various embodiments; Figure 6A and Figure 6B This is a block diagram illustrating an example configuration of a nearby call manager module according to various embodiments; Figure 7 This is a flowchart illustrating example methods for managing incoming calls according to various embodiments; Figure 8A This is a signal flow diagram illustrating an example method for managing an incoming call while a call session with a first device and a second device continues, according to various embodiments; Figure 8B This is a signal flow diagram illustrating an example method for managing an incoming call when a call session with a first device and a second device is terminated, according to various embodiments. Figure 9 This is a flowchart illustrating example methods implemented in a user equipment where an incoming call is to be transferred, according to various embodiments.

[0014] Figure 10 The structure of a user equipment (UE) according to an embodiment of the present disclosure is shown.

[0015] Furthermore, those skilled in the art will understand that the elements in the accompanying drawings are shown for simplicity and may not necessarily be drawn to scale. For example, flowcharts illustrate methods that help improve understanding of various aspects of this disclosure. Additionally, regarding the construction of the device, one or more components of the device may have already been represented by conventional symbols in the drawings, and the drawings may illustrate those specific details relevant to understanding embodiments of this disclosure, so that the drawings do not obscure the focus with details obvious to those skilled in the art in conjunction with the specification.

[0016] Best mode for carrying out the invention The aspects of this disclosure at least address the aforementioned problems and / or disadvantages, and at least provide the advantages described below. Therefore, one aspect of this disclosure is to provide a terminal in a wireless communication system and a communication method thereof. Detailed Implementation

[0017] First, it should be understood that although various illustrative embodiments of the present disclosure are shown below, any number of techniques, whether currently known or existing, can be used to implement the present disclosure. The present disclosure should in no way be limited to the illustrative embodiments, drawings, and techniques shown below, including the example designs and implementations illustrated and described herein, but modifications can be made within the scope of the present disclosure, including the full scope of the appended claims and their equivalents.

[0018] As used herein, the term "some" can mean, for example, "none," "one," "more than one," or "all." Therefore, the terms "none," "one," "more than one," "more than one, but not all," or "all" all fall under the definition of "some." The term "some embodiments" can mean no embodiment, one embodiment, several embodiments, or all embodiments. Therefore, the term "some embodiments" has the meaning including "no embodiment," "one embodiment," "more than one embodiment," or "all embodiments."

[0019] The terminology and structure used herein are intended to describe, teach, and elucidate various exemplary embodiments and their specific features and elements, and do not limit, constrain, or diminish the spirit and scope of the claims or their equivalents.

[0020] For example, unless otherwise stated, any term used herein (such as, but not limited to, “including,” “contains,” “has,” “composes of,” and its grammatical variations) does not specify precise limitations or constraints, and certainly does not preclude the possibility of adding one or more features or elements, and furthermore, unless otherwise stated in the restrictive language “must include” or “requires inclusion,” the possibility of removing one or more of the listed features and elements shall not be precluded.

[0021] Whether a feature or element is limited to being used only once, it may still be referred to as “one or more features” or “one or more elements” or “at least one feature” or “at least one element”, regardless of whether it is used in any way. Furthermore, the use of the terms “one or more” or “at least one” features or elements does not preclude the absence of that feature or element unless otherwise specified by restrictive language such as “required to be one or more…” or “expected to be one or more elements”.

[0022] Unless otherwise defined, all terms used herein, in particular any technical and / or scientific terms, may be considered to have the same meaning as commonly understood by one of ordinary skill in the art.

[0023] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings.

[0024] According to embodiments, this disclosure discloses a method and system for managing incoming calls in a called device. For example, this disclosure generally relates to a method and system for seamlessly transferring incoming calls from a caller's device to another device by sending an operable notification. In embodiments, another device may be pre-registered with the called device. According to various embodiments, the other device may be a device located near the called device.

[0025] Figure 1 This diagram illustrates an example working environment for managing incoming calls according to various embodiments. According to an embodiment, consider a scenario where user A has called user B through their user equipment 101. However, user B may be considered busy or not near their user equipment 103 to participate in the incoming call from user A. According to an embodiment, when user B is busy, user B can select a number from pre-registered numbers at runtime to transfer the incoming call. Figure 1 As depicted, user B has selected a number corresponding to user equipment 105 for transferring incoming calls. According to an embodiment, when user B is not near their user equipment 103 to participate in an incoming call, user equipment 103 can detect nearby devices to transfer the incoming call. In an embodiment, user equipment 103 sends an operable notification to transfer the incoming call. In an embodiment, the operable notification includes a notification for accepting or rejecting the incoming call, as well as other parameters associated with user equipment 101 and user equipment 103.

[0026] The following diagram explains the method in more detail.

[0027] Figure 2AThis is a block diagram illustrating an example system architecture of a user equipment according to various embodiments. User equipment 200 includes a processor (e.g., including processing circuitry) 201, a memory 203, a module / engine (e.g., including various circuitry and / or executable program instructions) 205, a database 207, an input / output (I / O) unit (e.g., including I / O circuitry) 109, and a network interface (NI) (e.g., including various circuitry) 211, all interconnected with each other via a bus.

[0028] As an example, user equipment 200 can correspond to various devices, such as mobile devices, smartphones, communication devices, user equipment (UE), or any other machine capable of executing a set of instructions and establishing a call with another device. In embodiments, user equipment 200 is capable of receiving incoming calls and initiating outgoing calls to another device. As an example, an incoming or outgoing call can be, but is not limited to, a Voice over LTE (VoLTE) call or a 5G call. Throughout this disclosure, user equipment 200 can be interchangeably referred to as a UE, a smartphone, or a mobile device.

[0029] As an example, processor 201 may be a single processing unit or multiple units, all of which may include multiple computing units. Processor 201 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic processors, virtual processors, state machines, logic circuits, application processors, communication processors, and / or any device that manipulates signals based on operating instructions. Among other capabilities, processor 201 is configured to acquire and execute computer-readable instructions and data stored in memory 203. Furthermore, the functions of module 205 may alternatively be performed using processor 201. Processor 201 according to embodiments of this disclosure may include various processing circuitry and / or multiple processors. For example, as used herein (including the claims), the term "processor" may include various processing circuitry, including at least one processor, wherein one or more of the at least one processor may be individually and / or collectively configured in a distributed manner to perform the various functions described herein. As used herein, when “processor,” “at least one processor,” and “one or more processors” are described as being configured to perform a number of functions, these terms cover, for example, but not limited to, a situation where one processor performs some of the functions and other processors perform other functions, and a situation where a single processor can perform all of the functions. Additionally, at least one processor may comprise, for example, a combination of processors performing various said / disclosed functions in a distributed manner. At least one processor can execute program instructions to implement or perform various functions. However, for ease of understanding, the following references... Figure 3 The various modules will be explained in more detail.

[0030] Memory 203 may include any non-transitory computer-readable medium known in the art, including, for example, volatile memory (such as static random access memory (SRAM) and dynamic random access memory (DRAM)) and / or non-volatile memory (such as read-only memory (ROM), erasable programmable ROM, flash memory, hard disk, optical disk and magnetic tape).

[0031] For example, module / engine 205 may include programs, subroutines, parts of programs, software components, and / or hardware components capable of performing the tasks or functions described herein. As used herein, module / engine 205 may be implemented independently of other modules on hardware components such as servers, or the module may reside on the same server or within the same program as other modules. Module / engine 205 may be implemented on hardware components such as processors, one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuits, and / or any device that manipulates signals based on operating instructions. When executed by processor 201, module / engine 205 may be configured to perform any function as discussed herein.

[0032] As another example, database 207 can be implemented using integrated hardware and software. The hardware may include a hardware disk controller with programmable search capabilities or a software system running on general-purpose hardware. Examples of database 207 are, but are not limited to, in-memory databases, cloud databases, distributed databases, embedded databases, etc. Database 207, among other functions, also serves as a repository for storing data processed, received, and generated by one or more processors and modules / engines / units.

[0033] In embodiments, module / engine 205 may be implemented using one or more AI modules, which may include multiple neural network layers. Examples of neural networks include, but are not limited to, convolutional neural networks (CNNs), deep neural networks (DNNs), recurrent neural networks (RNNs), and restricted Boltzmann machines (RBMs). 'Learning' in this disclosure may refer to a method for training a predetermined target device (e.g., a robot) using multiple learning data to enable, allow, or control the target device to make a determination or prediction. Examples of learning techniques include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning. At least one of multiple CNN, DNN, RNN, RMB, etc., models may be implemented to enable the execution of the mechanisms of this subject matter through an AI model. Functionality associated with the AI ​​module may be executed via non-volatile memory, volatile memory, and a processor. The processor may include one or more processors. At this point, one or more processors can be general-purpose processors (such as central processing units (CPUs), application processors (APs), graphics processing units only (such as graphics processing units (GPUs), vision processing units (VPUs)), and / or AI-specific processors (such as neural processing units (NPUs)). One or more processors control the processing of input data according to predefined operating rules or artificial intelligence (AI) models stored in non-volatile and volatile memory. The predefined operating rules or AI models are provided through training or learning.

[0034] As an example, input / output (IO) unit 209 may include various I / O circuitry and receive and output audio data from multiple users. In a non-limiting example, IO unit 209 includes a microphone and a speaker to receive and output audio data, respectively. As another example, network interface 211 may include various circuitry and establish network connections with networks such as home networks, public networks, or private networks.

[0035] Figure 2BThis is a block diagram illustrating example configurations of a user equipment according to various embodiments. It can be seen that user equipment 200 includes an application layer 231 implemented with one or more applications. User equipment 200 also includes a framework layer 233 implemented with module 205 and an IP Multimedia Subsystem (IMS) module 235. In embodiments, the IMS module 235 handles all incoming and outgoing calls, such as VoLTE, Wi-Fi, and 5G calls. According to embodiments, the next layer of user equipment 200 (e.g., operating system layer 249) includes system libraries for Bluetooth 237 and Wi-Fi 239. This layer includes a Relay Interface (RIL) 241. The RIL is an interface layer between an application processor (AP) and a communication processor (CP) (e.g., a modem) and is used for all communication between the AP and CP, such as sending and receiving notification messages and calls in LTE / 5G. User equipment 200 also includes layer 243 implemented with a kernel and drivers. Furthermore, user equipment 200 may also include WLAN and BT chip modules 245 for performing Bluetooth and Wi-Fi communication. User equipment 200 also includes a modem 247 for providing messaging services. Modem 247 is a CP protocol layer that conforms to the LTE protocol required by user equipment 200 for locking onto the network and thereby sending or receiving packets to or from the network.

[0036] Figure 3 This is a block diagram illustrating an example configuration of a module / engine for a user equipment according to various embodiments of Figure 2. For example, such as... Figure 3 The module / engine 205 shown may include a device detector module 301, a notification monitor module 303, a motion analyzer module 305, and a nearby call manager module 307, each of which may include various circuits and / or executable program instructions. Each module will be explained in more detail below.

[0037] According to an embodiment, the device detector module 301 detects nearby devices to which incoming calls need to be transferred. According to an embodiment, the device detector module 301 detects user equipment used for transferring incoming calls. As described above, when a user is busy and unable to answer an incoming call at a given time, or when a user is not near their mobile device to answer an incoming call, the incoming call can be transferred to another device. Therefore, when a user is busy and unable to answer an incoming call at a given time, the user can select a number from pre-registered numbers at runtime to transfer the incoming call. According to an embodiment, based on runtime user input, the device detector module 301 detects another device for transferring incoming calls by selecting another device from a list of devices pre-registered in user equipment 200 with its identification number (e.g., IMEI number). Figure 1In the example scenario, a device list is pre-registered to user device B 103, including device C105 pre-registered to user device B 103. Figure 1 In the example scenario, the incoming call originates from user equipment A 101. Additionally, an incoming call is made to user equipment B 103. Furthermore, when the user is busy, the incoming call is transferred to user equipment C 105 based on the selection of user equipment C at runtime.

[0038] According to an embodiment, when a user is not near their mobile device to answer an incoming call (i.e., during an unanswered event of an incoming call), the device detector module 301 performs one or more operations by pre-registering its identification number (e.g., IMEI number) in a list of devices in the user equipment 200 to detect another device. In an embodiment, the device detector module 301 performs one or more operations, including sending at least one of: a first scan request for discovering nearby Bluetooth (BT) devices, a second scan request for discovering nearby Wi-Fi devices, or a Short Message Service (SMS) request.

[0039] In one embodiment, the device detector module 301 sends an operable notification to another device after detection. In another embodiment, the operable notification includes a notification for accepting or rejecting an incoming call, as well as other parameters associated with the user equipment that initiated the incoming call and the user equipment that made the incoming call to it. Return to Reference Figure 1 In an example scenario, the user equipment initiating the incoming call is user equipment A 101, and the user equipment making the incoming call to it is user equipment B 103. Therefore, user equipment B 103 sends an operable notification to user equipment C 105. In an embodiment, the operable notification includes at least: the caller ID of the user equipment initiating the incoming call (e.g., user equipment A 101), the address of the user equipment making the incoming call to it (e.g., user equipment B 103), the address of the user equipment to which the incoming call is to be transferred (e.g., user equipment C 105), a message ID indicating an acknowledgment for accepting or rejecting the incoming call, and a response code for accepting or rejecting the incoming call. In another embodiment, the operable notification is transcoded along with the message at the user equipment making the incoming call (e.g., user equipment B 103) and further sent to the user equipment to which the incoming call is to be transferred (e.g., user equipment C).

[0040] According to an embodiment, the monitoring module 303 detects incoming notifications. Figure 4This is a block diagram illustrating an example configuration of a notification monitor module according to various embodiments. The notification monitor module 303 includes a service module manager 401 and a service handler 407. In embodiments, the service module manager 401 handles services such as calls, SMS, and SS via a VoLTE service module 405, an SMS service module 404, and a supplementary service (SS) service module 403, respectively. SS includes Bluetooth (BT) service, Wi-Fi service, and other communication services. In embodiments, the service module manager 401 extends the service handler 407. In embodiments, the service handler 407 includes an SS handler 409 for handling SS services, an SMS handler 411 for handling SMS services, and a VoLTE handler 413 for handling VoLTE services. Each module may include various circuits and / or executable program instructions.

[0041] In this embodiment, the notification monitoring module 303 detects all types of incoming requests. For example, the notification monitoring module 303 detects requests related to a first scan request for discovering nearby BT devices, a second scan request for discovering nearby Wi-Fi devices, or an SMS request. In this embodiment, the notification monitoring module 303 may send an acknowledgment message in response to an incoming request.

[0042] In one embodiment, the incoming notification includes receiving an operable notification from the user equipment (e.g., user equipment B103) that initiated the incoming call. Therefore, the notification monitor module 303 notifies the action analyzer module 305 of the incoming request (e.g., the incoming call). In another embodiment, the notification monitor module 303 may send an acknowledgment message in response to the incoming request.

[0043] In one embodiment, the action analyzer module 305 detects actions for accepting or rejecting an incoming call notification sent by the user equipment (e.g., user equipment B 103) making the incoming call. In another embodiment, when an operable notification is sent by the user equipment (e.g., user equipment B 103) making the incoming call, the action analyzer module 305 analyzes actions performed by the user to whom the incoming call is to be transferred (e.g., user equipment C 105). Specifically, the action analyzer module 305 performs detection based on confirmation from the user equipment (e.g., user equipment C 105) regarding actions related to the operable notification. The operation of the action analyzer module 305 is described in more detail below.

[0044] Figure 5This is a block diagram illustrating an example configuration of an action analyzer module according to various embodiments. In one embodiment, the action analyzer module 305 includes an event monitor module 501, an ACK notification module 503, an Rx_PDU module 505, a PDU parser 507, and a timeout manager 519. In one embodiment, the action analyzer module 305 receives notifications related to incoming requests for incoming calls from the notification monitor module 303. In one embodiment, the event monitor module 501 monitors the reception of acknowledgment messages from another device regarding actions related to incoming call notifications. Return to Reference Figure 1 The event monitor module 501 of user equipment B 103 monitors acknowledgment messages for actions taken by the corresponding user of user equipment C 105 in response to received operable notifications. According to an embodiment, the corresponding user of the user equipment to which an incoming call is to be transferred (e.g., user equipment C 105) can accept or reject the incoming call notification. When an acknowledgment message is received, the ACK notification module 503 is triggered. Thereafter, the RX_PDU module 505 receives, via a protocol data unit (PDU), an acknowledgment message including multiple device parameters and confirmation of actions regarding the operable notification. In a non-limiting example, the multiple device parameters include at least one of a call identifier (ID) or a type of content in the acknowledgment message. Furthermore, confirmation of the action includes accepting or rejecting the incoming call. In a non-limiting example, the call identifier (ID) corresponds to the identifier of the user equipment that has sent the notification. Furthermore, in a non-limiting example, the type of content in the acknowledgment message includes content related to the incoming message or content related to the incoming call.

[0045] In one embodiment, PDU parser 507 parses the acknowledgment message to identify the user's action and device parameters. In another embodiment, PDU parser 507 includes various modules such as a call ID acquisition module 509, a call type acquisition module 511, a content data acquisition module 513, a result classifier module 515, and a result notification module 517. In one embodiment, call ID acquisition module 509 parses the acknowledgment message to obtain the call ID, and call type acquisition module 511 parses and obtains the type of content in the acknowledgment message. Content data acquisition module 513 parses and obtains the data in the acknowledgment message. In this example, the data obtained by content data acquisition module 513 includes data such as acceptance or rejection messages from another device. In another embodiment, result classifier module 515 analyzes the acknowledgment message and classifies the action of accepting or rejecting an incoming call notification. Specifically, the result notification module 517 then notifies the nearby call manager module 307 of the acceptance or rejection result.

[0046] According to another embodiment, timeout manager 519 is triggered when there is no response to an incoming call from a user device (e.g., user device C 105) to which the incoming call is to be transferred within a predefined time period. Clock 523 monitors the expiration of the predefined time period. In this embodiment, the nearby call manager module 307 is not activated when there is no response from any connected device. Therefore, a call from user device A 101 at user device B 103 will not be accepted or established.

[0047] In this embodiment, when a confirmation message is received, the last notification context 521 of the action analyzer module 305 disables the clock 523. Furthermore, in this embodiment, the IMS interface 525 exposes APIs for managing all IMS-based calls.

[0048] According to an embodiment, when a user equipment (e.g., user equipment C 105) to which an incoming call is to be transferred receives an acknowledgment of acceptance of the incoming call, and the call session between the user equipment (e.g., user equipment A 101) that initiated the incoming call and the user equipment (e.g., user equipment B 103) that initiated the incoming call continues, the nearby call manager module 307 initiates an outgoing call to the user equipment (e.g., user equipment C 105) to which the incoming call is to be transferred.

[0049] According to an embodiment, upon receiving confirmation of acceptance of an incoming call from a user equipment (e.g., user equipment C 105) to which the incoming call is to be transferred, and provided that the call session between the user equipment that initiated the incoming call (e.g., user equipment A 101) and the user equipment that initiated the incoming call (e.g., user equipment B 103) is terminated, the nearby call manager module 307 initiates an outgoing call with both the user equipment to which the incoming call is to be transferred (e.g., user equipment C 105) and the user equipment that initiated the incoming call (e.g., user equipment A 101). The operation of the nearby call manager module 307 through its various components will be described in more detail below.

[0050] Figure 6A and Figure 6B This is a block diagram illustrating an example configuration of a nearby call manager module according to various embodiments. In an embodiment, the nearby call manager module 307 includes an incoming call manager module 601, a call creator module 603, and a nearby conference manager module 605, each of which includes various circuitry and / or executable program instructions (which may be in the form of additional modules). According to an embodiment, based on the results of the action analyzer module 305, the incoming call manager module 601 accepts incoming calls using the IMS interface 607. Reference Figure 1For example, the incoming call manager module 601 of the user equipment (e.g., user equipment C 105) to which the incoming call is to be transferred accepts the incoming call. According to an embodiment, the incoming call manager module 601 includes an incoming call handler module 601-1, a call status acquisition notification module 601-2, a hold response notification module 601-3, and a hold call module 601-4 with a session ID. Therefore, the incoming call handler module 601-1 processes the incoming call using the IMS interface 607. The call status acquisition notification module 601-2 obtains the current status of the incoming call. In an embodiment, if a call status is established, the hold call module 601-4 with a session ID sends a request to user equipment A 101 to hold the currently ongoing call. Furthermore, once the incoming call is successfully held, the hold response notification module 601-3 receives a notification. Figure 1 In the example scenario, consider user equipment C 105 accepting an incoming call and the call being established. Therefore, once the incoming call is successfully established, the incoming call manager 601 of user equipment B 103 will maintain a very short, predefined time period with the incoming call from user equipment A.

[0051] In this embodiment, after holding an incoming call, the call creator module 603 creates a new outgoing call session for the user equipment (e.g., user equipment C 105) to which the incoming call is to be transferred, as detected by the action analyzer module 305. Therefore, the call creator module 603 of the user equipment (e.g., user equipment B 103) to which the incoming call is being held sends a new call invitation to the user equipment (e.g., user equipment C 105) to which the incoming call is to be transferred. Once a notification that a call has been established is received, the call creator module 603 of the user equipment (e.g., user equipment B 103) to which the incoming call is being held sends a request to hold the incoming call with the user equipment (e.g., user equipment C 105) to which the incoming call is to be transferred. Thus, a conference call is established by simultaneously merging the incoming and outgoing calls while both incoming and outgoing calls are held.

[0052] In this embodiment, the call creator module 603 includes a call setup data creation module 603-1 and a call initiation module 603-2 for creating a new outgoing call session with the user equipment (e.g., user equipment C 105) to which the incoming call is to be transferred, and for initiating the call. While the call session of the user equipment (e.g., user equipment A 101) from which the incoming call originated continues, and the call session of the user equipment (e.g., user equipment B 103) to which the incoming call is to be transferred continues, an outgoing call is established with the user equipment (e.g., user equipment C 105) to which the incoming call is to be transferred. Furthermore, the call creator module 603 includes a call response notification module 603-3 for receiving notifications of call establishment. A hold-call module 603-4 with a session ID holds the outgoing call with the user equipment (e.g., user equipment C 105) to which the incoming call is to be transferred. Therefore, after holding both the incoming and outgoing calls, the hold-call response notification module 603-5 sends a notification related to holding both the incoming and outgoing calls to the nearby conference manager module 605.

[0053] According to an embodiment, when a call session between a user equipment (e.g., user equipment A 101) that initiated the incoming call and a user equipment (e.g., user equipment B 103) that initiated the incoming call is terminated, the call creator module 603 creates a new outgoing call session between the user equipment (e.g., user equipment A 101) that initiated the incoming call and the user equipment (e.g., user equipment C 105) to which the incoming call is to be transferred. The operation of the various components will be the same as or similar to those explained above.

[0054] In this embodiment, when both calls are successfully held, the nearby conference manager module 605 creates a conference by sending an invitation request with a Conference Factory Uniform Resource Indicator (URI) for a three-way session to the operator's conference server. The Conference Factory URI is a unique Session Initiation Protocol (SIP) address of the operator's conference server. In this embodiment, conference call setup data 611 and start N-side conference call 613 create the conference and send the invitation request, respectively. Specifically, conference call setup data 611 uses the IMS interface to create data for setting up the conference call. In a non-limiting example, the data includes at least the Conference Factory URI, the type of incoming call (e.g., voice or video call), the device's Mobile Station Integrated Services Digital Network (MSISDN), audio / video codecs, etc.

[0055] In one embodiment, the conference call response notification 615 receives the establishment status of the conference call. In another embodiment, the conference subscriber 617 subscribes to conference event packets. Furthermore, upon termination of the conference call, a conference notification 619 is received. In another embodiment, a call reference 621 for the session ID sends a reference request for the maintained session ID. In another embodiment, via a conference call reference response 623, once the conference call is successfully created and established, the nearby call module manager 307 of the user equipment (e.g., user equipment B 103) to which the incoming call originated (e.g., user equipment A 101) and the user equipment (e.g., user equipment C 105) to which the incoming call is to be transferred release the active session. That is, a termination call 625 for the session ID terminates the session ID of the nearby conference manager module 605, terminating the call sessions with user equipment A 101 and user equipment C 105.

[0056] According to the embodiment, by Figures 3 to 6B The various components of the explained module 205 can be interchangeably performed by the user equipment that initiates the incoming call, the user equipment that makes the incoming call, and the user equipment to which the incoming call is transferred, depending on their required operation in the call management process.

[0057] Figure 7 This is a flowchart 700 illustrating example methods for managing incoming calls according to various embodiments. Figure 8A This is a signal flow diagram illustrating an example operation flow 800A for managing an incoming call while a call session with a first device and a second device continues, according to various embodiments. Figure 8B This is a signal flow diagram illustrating example operation flow 800B for managing incoming calls in the event of a call session with a first device and a second device being terminated, according to various embodiments. For ease of understanding, method 700 will be explained in conjunction with operations 800A and 800B. In an embodiment, method 700 is implemented in user equipment 200 of FIG2 via module 205. In an embodiment, as depicted in operation flow 800A, first device A 101 is the user equipment that initiated the incoming call (e.g., user equipment A 101), second device B 103 is the user equipment that initiated the incoming call (e.g., user equipment B 103), and third device C is the user equipment to which the incoming call is transferred (e.g., user equipment C 105). Therefore, for ease of understanding, the reference numerals remain the same. In an embodiment, method 700 is implemented in second device B. The above has been explained with reference to FIG2 to... Figure 6B The detailed explanation of module 205 has already been provided, so it will not be repeated here.

[0058] At step 701, an incoming call to the second device B 103 is received from the first device A 101. Step 701 corresponds to... Figure 8A Step 801. Now, in the case that the user is unable to answer the call or is busy, at step 703, the second device B 103 detects the third device C 105 among one or more devices to transmit an operational notification of the incoming call. Therefore, the second device B 103 performs the detection of the third device among multiple devices based on either user input during runtime or a no-answer event of the incoming call. A no-answer event occurs when the user is not near the second device B 103. Furthermore, it is assumed that the second device B 103 initially performed pre-registration with one or more devices based on user input. Step 703 corresponds to Figure 8A Step 803.

[0059] In an embodiment, during operation, the second device B 103 detects the third device C 105 by performing one or more operations or by selecting the third device C 103. According to an embodiment, in an incoming call no-answer event, detecting the third device C among one or more devices includes performing multiple operations, including sending at least one of: a first scan request for discovering nearby Bluetooth (BT) devices, a second scan request for discovering nearby Wi-Fi devices, or a Short Message Service (SMS) request. Figure 8A At step 805, multiple operations are performed. Therefore, after performing one or more operations, the third device C 105 receives a response corresponding to at least one of the first scan request, the second scan request, and the SMS request. Therefore, the second device B 103 detects the third device C 105 based on this response. In an embodiment, the response includes at least one of device identifier (ID), device type, signal strength information, device capability information, available service information, etc. In an example embodiment, consider receiving a response from the third device C 105.

[0060] According to various embodiments, when the user is busy to answer the call, the user of the second device B 103 selects the third device C 105 during operation.

[0061] According to an embodiment, in Figure 8A At step 807, after detecting the third device C 105, the second device B 103 sends an operable notification for accepting or rejecting an incoming call to the third device C 105. Therefore, steps 803, 805, and 807 collectively correspond to step 703.

[0062] At step 705, the second device B 103 detects an acknowledgment from the third device C 105 regarding an action on the operability notification. In an embodiment, the action performed by the third device C 105 may include accepting or rejecting an incoming call. In an embodiment, consider the third device C 105 accepting an incoming call. Therefore, the third device C 105 sends an acknowledgment to the second device B 103 regarding the acceptance of the incoming call. Step 705 corresponds to step 809.

[0063] Once the incoming call is accepted by the third device C 105, in step 707, the second device B initiates an outgoing call with the third device C 105. Similarly, the third device C 105 initiates an outgoing call with the second device B 103. Step 817 is similar to step 707. Thereafter, the second device B 103 generates a conference bridge via the operator conference server 815. Simultaneously, the outgoing call between the second device B 103 and the third device C 105 remains in progress.

[0064] Based on the example scenario of operation method 800A, consider the call session between the second device B 103 and the first device C 101 continuing during the operation performed by the second device B 103.

[0065] Furthermore, according to the example scenario of operation method 800B, consider the scenario where the call session between the second device B 103 and the first device C 101 is disconnected during the operation performed by the second device B 103. In this scenario, such as Figure 8B As shown in steps 817 and 827, an outgoing call is initiated for both the first device A 101 and the third device C 105. Because the steps are similar and for ease of understanding, Figure 8B The attached figures and Figure 8A Keep it the same.

[0066] Return to reference Figure 8A After generating a conference bridge via the operator conference server 815 in step 813, the second device B 103 connects to the third device C 105 in step 819 by merging incoming and outgoing calls, and connects to the first device in step 821. Therefore, in step 709, the second device B 103 manages both incoming and outgoing calls simultaneously via the conference call. Subsequently, in step 825, calls from the first device A 101 are transferred to the third device C 103 via the conference call. Simultaneously, the second device B 103 exits in step 823 by releasing its active call sessions with the third device C 105 and the first device A.

[0067] Figure 9This is a flowchart illustrating an example method 900 implemented in a third device C 105 according to various embodiments. In the embodiments, embodiments of method 900 can be conceived from the descriptions of methods 700, 800A, and 800B, so for the sake of brevity, the same details are not repeated here.

[0068] At step 901, the third device C 105 receives an operable notification from the second device B 103 regarding an incoming call originating from the first device A 101. Step 901 corresponds to step 807. Subsequently, at step 903, the third device C 105 sends an acknowledgment regarding the action taken by the third device C 105 concerning the operable notification. Subsequently, at step 905, the third device C 105 initiates an outgoing call based on the detected action. Subsequently, at step 907, the third device C 105 simultaneously manages both incoming and outgoing calls via a conference call. Therefore, the disclosed technology provides a unique method for managing calls via establishing a conference call. Thus, the disclosed method seamlessly delivers Vo-LTE / 5G calls to selected contacts during operation.

[0069] Figure 10 The structure of a user equipment (UE) or device according to an embodiment of the present disclosure is shown.

[0070] like Figure 10 As shown, the UE according to the embodiment may include a transceiver 1010, a memory 1020, and a processor 1030. The transceiver 1010, memory 1020, and processor 1030 of the UE can operate according to the communication method of the UE described above. However, the components of the UE are not limited thereto. For example, the UE may include more or fewer components than those described above. Furthermore, the processor 1030, transceiver 1010, and memory 1020 may be implemented as a single chip. Furthermore, the processor 1030 may include at least one processor. Additionally, Figure 10 The UE corresponds to Figure 2A The equipment.

[0071] Transceiver 1010 generally refers to both a UE receiver and a UE transmitter, and can send / receive signals to / from a base station or network entity. Signals sent to or received from a base station or network entity may include control information and data. Transceiver 1010 may include an RF transmitter for up-converting and amplifying the transmitted signal, and an RF receiver for low-noise amplification and down-converting the received signal. However, this is only an example of transceiver 1010, and the components of transceiver 1010 are not limited to RF transmitters and RF receivers.

[0072] In addition, transceiver 1010 can receive signals via a wireless channel and output them to processor 1030, and can also transmit signals output from processor 1030 via a wireless channel.

[0073] The memory 1020 can store programs and data required for the operation of the UE. Furthermore, the memory 1020 can store control information or data included in signals received by the UE. The memory 1020 can be a storage medium, such as a read-only memory (ROM), random access memory (RAM), hard disk, optical disk, and DVD, or a combination of storage media.

[0074] The processor 1030 can control a series of processes to enable the UE to operate as described above. For example, the transceiver 1010 can receive data signals including control signals transmitted by a base station or network entity, and the processor 1030 can determine the result of receiving control signals and data signals transmitted by another UE, entity, or device. Figure 10 The UE corresponds to devices, entities, modules, etc.

[0075] In various embodiments, a method for managing incoming calls includes: receiving a first call to a second device from a first device; detecting a third device among a plurality of devices to transmit an operable notification of the first call; detecting confirmation of an action from the third device regarding the operable notification; initiating a second call based on the detected action; and simultaneously managing the first and second calls via a conference call.

[0076] Preferably, a third device is detected among multiple devices based on one of the runtime input or the no-response event of an incoming call.

[0077] Preferably, detecting a third device among multiple devices based on an unanswered incoming call event includes: performing multiple operations, said multiple operations including sending at least one of: a first scan request for discovering a nearby Bluetooth (BT) device, a second scan request for discovering a nearby Wi-Fi device, or a Short Message Service (SMS) request; receiving a response corresponding to at least one of the first scan request, the second scan request, and the SMS request; and detecting the third device among multiple devices based on receiving the response corresponding to at least one of the first scan request, the second scan request, and the SMS request, wherein the response includes at least one of device identifier (ID), device type, signal strength information, device capability information, and available service information.

[0078] Preferably, detecting a third device among multiple devices based on input at runtime includes: selecting a third device from multiple pre-registered devices via input at runtime.

[0079] Preferably, the operable notification includes at least: a caller ID of the first device, an address of the second device, an address of the third device, a message ID indicating confirmation of acceptance or rejection of the first call, and a response code for acceptance or rejection of the first call, wherein the operable notification is transcoded together with the message sent to the third device.

[0080] Preferably, the detection via confirmation of an action regarding the operability notification from a third device includes: monitoring by a second device the reception of confirmation messages regarding the action regarding the operability notification from the third device, wherein the action of the third device includes accepting or rejecting a first call; and receiving, via a protocol data unit (PDU), a confirmation message including multiple device parameters and confirmation of the action regarding the operability notification, wherein the multiple device parameters include at least one of a call identifier (ID) or a type of content in the confirmation message, wherein the confirmation of the action includes accepting or rejecting the first call.

[0081] Preferably, based on receiving confirmation from the third device for accepting the first call, one of the following is initiated: a second call with the third device (if the call session between the first and second devices continues) or a second call with both the third device and the first device (if the call session between the first and second devices is terminated).

[0082] Preferably, the method further includes: maintaining the first call and the second call for a specified period of time based on the confirmation received from the third device for accepting the first call.

[0083] Preferably, managing the first and second calls simultaneously via conference call includes: establishing a conference call between the first device, the second device, and the third device.

[0084] Preferably, the method further includes: pre-registering multiple devices to the second device based on input, wherein multiple operations are performed on the pre-registered multiple devices.

[0085] Preferably, the second device's no-response event for an incoming call is based on the condition that the user is not present in the vicinity of the second device.

[0086] In various embodiments, a method for managing incoming calls at a first device includes: receiving from a second device an operable notification for a first call originating from a third device; sending an acknowledgment to the second device of an action regarding the operable notification; initiating a second call based on the detected action; and simultaneously managing the first and second calls via a conference call.

[0087] Preferably, the operable notification includes accepting or rejecting one of the first calls.

[0088] Preferably, the method further includes: receiving at least one of a first scan request for discovering nearby Bluetooth (BT) devices, a second scan request for discovering nearby Wi-Fi devices, or a Short Message Service (SMS) request; and sending a response corresponding to at least one of the first scan request, the second scan request, and the SMS request. The response includes at least one of the following: device identifier (ID), device type, signal strength information, device capability information, and available service information.

[0089] Preferably, an operable notification is received from the second device based on the occurrence of an event at the second device, wherein the occurrence of the event at the second device includes: receiving input during runtime, or an unanswered event of an incoming call at the second device.

[0090] Preferably, the operable notification includes at least: a caller ID of the third device, an address of the first device, a message ID indicating confirmation of acceptance or rejection of the first call, and a response code for acceptance or rejection of the first call, wherein the operable notification is transcoded together with a message received from the second device.

[0091] Preferably, the method further includes: sending an acknowledgment message for an action regarding an operable notification, wherein the action includes accepting or rejecting a first call, wherein the acknowledgment message includes a plurality of device parameters and an acknowledgment of the action regarding the operable notification, and wherein the plurality of device parameters include at least one of a call identifier (ID) or a type of content in the acknowledgment message, wherein the acknowledgment of the action includes accepting or rejecting the first call.

[0092] Preferably, the second call is initiated while the call session corresponding to the second device and the third device continues.

[0093] Preferably, the method further includes: after initiating the second call, the first call and the second call are maintained for a specified period of time.

[0094] Preferably, managing the first and second calls simultaneously via conference call includes: establishing a conference call between the second device, the third device, and the first device.

[0095] Preferably, the first device pre-registers with the second device.

[0096] Preferably, the second device's no-response event to an incoming call is based on the condition that there is no user near the second device.

[0097] In various embodiments, a user equipment for managing incoming calls includes: a memory, communication circuitry, and at least one processor including processing circuitry, the at least one processor being individually and / or collectively configured to: receive a first call; detect a first device among a plurality of devices to transmit an operable notification of the first call; detect confirmation of an action from a third device regarding the operable notification; initiate a second call based on the detected action; and simultaneously manage the first and second calls via a conference call.

[0098] In various embodiments, a user equipment for managing incoming calls includes: a memory, communication circuitry, and at least one processor including processing circuitry, the at least one processor being individually and / or collectively configured to: receive an operable notification for a first call originating from a first device; send an acknowledgment to a second device regarding an action related to the operable notification; initiate a second call based on the detected action; and simultaneously manage the first and second calls via a conference call.

[0099] While this disclosure has been described in specific language, it is not intended to be limiting in any way. It will be apparent to those skilled in the art that various working modifications can be made to the method to achieve the concepts taught herein.

[0100] The accompanying drawings and the foregoing description provide examples of embodiments. Those skilled in the art will understand that one or more of the described elements can be well combined into a single functional element. Certain elements can be divided into multiple functional elements. Elements from one embodiment can be added to another embodiment. For example, the order of the processes described herein can be changed and is not limited to the manner described herein.

[0101] Furthermore, the actions in any flowchart need not be performed in the order shown; nor is it necessary to execute all actions. Moreover, those actions that do not depend on other actions can be performed in parallel with other actions. The scope of the embodiments is not limited to these specific examples. Many variations, such as differences in structure, size, and material use, are possible, whether or not explicitly given in this disclosure. The scope of the embodiments is at least as broad as given by the appended claims.

[0102] The benefits, other advantages, and solutions to problems have been described above with respect to various embodiments. However, the benefits, advantages, solutions to problems, and any components that may cause any benefit, advantage, or solution to occur or become more apparent should not be construed as key, essential, or necessary features or components of any or all claims.

Claims

1. A method performed by a transmitter in a wireless communication network for processing segments, the method comprising: Multiple Service Data Units (SDUs) are received from the upper layer of the sending end; By using the aggregation L2 at the transmitting end, multiple SDUs received from the upper layer are cascaded to obtain Protocol Data Units (PDUs); The L2 sequence number SN is assigned to the PDU through the aggregation L2 of the transmitting end, wherein the L2 SN includes at least one of the following: a last SDU indicator LSI indicating the existence of the last SDU of the complete PDU, a length indicator LIE indicating the existence of a length indicator L1 after the L2 header, or a segmentation indicator SI indicating the segmentation status or stage of the complete PDU. The media access control (MAC) layer of the transmitting end receives an authorization opportunity or transmission opportunity for transmitting the PDU available at the aggregation L2. as well as The PDU is transmitted to the lower layer of the sending end via the MAC layer of the sending end, based on the authorization opportunity or the transmission opportunity, whether in segments or not, for transmission to the receiving end.

2. The method according to claim 1, wherein, The PDU is transmitted to the receiving end via the MAC layer of the transmitting end, based on the grant opportunity or the transmission opportunity, whether in a segmented or unsegmented manner, including: The MAC layer of the transmitting end determines whether the authorized opportunity or the transmitting opportunity is sufficient to transmit a complete PDU to the receiving end; and One of the following is performed by the MAC layer of the sending end: When the authorization opportunity is sufficient to transmit the complete PDU, the complete PDU is transmitted to the lower layer of the transmitting end to the receiving end without segmentation, based on the authorization opportunity or the transmission opportunity. Based on the authorization opportunity or the transmission opportunity, the complete PDU is segmented into multiple PDU segments, or When the authorized opportunity or the transmission opportunity is insufficient to transmit the complete PDU, the multiple PDU segments are transmitted to the lower layer of the transmitting end for transmission to the receiving end.

3. The method according to claim 2, wherein, Transmitting the plurality of PDU segments to the lower layer of the transmitting end for transmission to the receiving end includes: Through the MAC layer of the sending end, a segment header is created for each of the plurality of PDU segments based on the authorization opportunity or the sending opportunity; The MAC layer at the sending end assigns an identifier field with the same L2SN to each PDU segment in the segment header. The L2 SN includes a segmented offset SO field, and The SO field indicates the offset from the first byte of the payload. A MAC PDU is created by the MAC layer of the sending end by assigning a MAC sub-header to the plurality of PDU segments of the complete PDU; and The MAC PDU is transmitted to the lower layer of the sending end via the MAC layer of the sending end for transmission to the receiving end.

4. The method according to claim 3, wherein, The process of transmitting the MAC PDU to the lower layer of the transmitting end via the MAC layer of the transmitting end for transmission to the receiving end includes: The MAC layer of the transmitting end determines whether the grant opportunity or the transmission opportunity is sufficient to transmit the original LI within the Transmission Time Interval (TTI); and One of the following is performed through the MAC layer: When the grant opportunity or the transmission opportunity is sufficient to transmit the original LI in a subsequent TTI, the original LI is transmitted in all payloads of the PDU segment of the MAC PDU in the subsequent TTI, or Transmitted truncation LI, which applies only to the SDU portion present in the PDU segment following the segmentation of the MAC PDU.

5. The method according to claim 3, wherein, When the identifier field used for PDU segments is in the same L2 header, the same L2 SN is assigned to all PDU segments of the complete PDU.

6. The method according to claim 2, wherein, Based on the authorization opportunity or the transmission opportunity, the complete PDU is transmitted to the lower layer of the transmitting end without segmentation to be sent to the receiving end, including: A MAC PDU is created by the MAC layer of the transmitting end by allocating the following SI, LSI, and LIE: SI indicates that the complete PDU is not segmented; LSI indicates that the complete PDU includes the last SDU concatenated at the aggregation L2 to form the complete PDU; and LIE indicates the presence of a length indicator as an L2 subheader including a LI field for the multiple SDUs. The MAC PDU is transmitted to the lower layer of the sending end via the MAC layer of the sending end for transmission to the receiving end.

7. The method according to claim 1, wherein, When the SI indicates the last SDU of the complete PDU, the LSI is set to high. Wherein, when the L2 header is followed by the L1, the LIE is set to high.

8. The method according to claim 1, in, The cascading of multiple SDUs to form a complete PDU is accomplished non-real-time by NTR, and The segmentation is performed in real time through the layer between the aggregation L2 and the MAC layer, or through the MAC layer using the same SN as the group at the aggregation layer 2 or a new identifier at the MAC layer, or through a new layer between the aggregation L2 and the MAC layer.

9. A transmitter in a wireless communication network for processing segments, the transmitter comprising: transceiver; processor; as well as The memory stores instructions that, when executed by the processor, cause the sending end to: Using the upper layer of the transmitting end, multiple Service Data Units (SDUs) are received. Using the aggregation L2 at the transmitting end, multiple SDUs received from the upper layer are cascaded to obtain Protocol Data Units (PDUs). Using the aggregated L2 at the transmitting end, an L2 sequence number SN is assigned to the PDU, wherein the L2 SN includes at least one of the following: a last SDU indicator LSI indicating the presence of the last SDU of the complete PDU, a length indicator LIE indicating the presence of a length indicator L1 after the L2 header, or a segmentation indicator SI indicating the segmentation status or stage of the complete PDU. Using the Media Access Control (MAC) layer of the transmitting end, an authorization opportunity or transmission opportunity is received for transmitting the PDU available at the aggregation L2, and Using the MAC layer of the sending end, the PDU is transmitted to the lower layer of the sending end, in a segmented or unsegmented manner, based on the authorization opportunity or the transmission opportunity, to be sent to the receiving end.

10. The transmitting end according to claim 9, wherein, In order to utilize the MAC layer of the transmitting end, and to transmit the PDU to the lower layer of the transmitting end for transmission to the receiving end based on the grant opportunity or the transmission opportunity, whether in a segmented or unsegmented manner, the memory further includes the following instructions, which, when executed by the processor, cause the transmitting end to: Using the MAC layer of the transmitting end, determine whether the authorized opportunity or the transmitting opportunity is sufficient to transmit a complete PDU to the receiving end; and Perform one of the following using the MAC layer of the sending end: When the grant opportunity is sufficient to transmit the complete PDU, the complete PDU is transmitted to the lower layer of the transmitting end without segmentation, based on the grant opportunity or the transmission opportunity, to be sent to the receiving end. When the authorization opportunity or the transmission opportunity is insufficient to transmit the complete PDU, the complete PDU is segmented into multiple PDU segments based on the authorization opportunity or the transmission opportunity, and the multiple PDU segments are transmitted to the lower layer of the transmitting end to be sent to the receiving end.

11. The transmitting end according to claim 10, wherein, In order to transmit the plurality of PDU segments to the lower layer of the transmitting end for transmission to the receiving end, the memory further includes the following instructions, which, when executed by the processor, cause the transmitting end to: Using the MAC layer of the sending end, a segment header is created for each of the plurality of PDU segments based on the authorization opportunity or the sending opportunity. Using the MAC layer of the transmitting end, an identifier field with the same L2SN is assigned to each PDU segment in the segment header, wherein the L2SN includes a segment offset SO field, wherein the SO field indicates the offset from the first byte of the payload. Using the MAC layer of the sending end, a MAC PDU is created by assigning a MAC sub-header to the plurality of PDU segments of the complete PDU, and Using the MAC layer of the sending end, the MAC PDU is transmitted to the lower layer of the sending end for transmission to the receiving end.

12. The transmitting end according to claim 11, wherein, In order to utilize the MAC layer of the transmitting end and transmit the MAC PDU to the lower layer of the transmitting end for transmission to the receiving end, the memory further includes the following instructions, which, when executed by the processor, cause the transmitting end to: Using the MAC layer of the transmitting end, determine whether the grant opportunity or the transmission opportunity is sufficient to transmit the original LI within the Transmission Time Interval (TTI); and Perform one of the following using the MAC layer of the sending end: When the grant opportunity or the transmission opportunity is sufficient to transmit the original LI in a subsequent TTI, the original LI is transmitted in all payloads of the PDU segment of the MAC PDU in the subsequent TTI, or Transmitted truncation LI, which applies only to the SDU portion present in the PDU segment following the segmentation of the MAC PDU.

13. The transmitting end according to claim 11, wherein, The identifier field used for PDU segments is in the same L2 header, and the same L2 SN is assigned to all PDU segments of the complete PDU.

14. The transmitting end according to claim 10, wherein, In order to transmit the complete PDU to the receiving end without segmentation based on the authorization opportunity or the transmission opportunity, the memory further includes the following instructions, which, when executed by the processor, cause the transmitting end to: Using the MAC layer of the transmitting end, a MAC PDU is created by assigning the following SI, LSI, and LIE: SI indicates that the complete PDU is not segmented; LSI indicates that the complete PDU includes the last SDU concatenated at the aggregation L2 to form the complete PDU; and LIE indicates the presence of a length indicator as an L2 subheader including an LI field for the multiple SDUs. Using the MAC layer of the sending end, the MAC PDU is transmitted to the lower layer of the sending end for transmission to the receiving end.

15. The transmitting end according to claim 9, wherein, When the SI indicates the last SDU of the complete PDU, the LSI is set to high. Specifically, when the L2 header is subsequently accompanied by the L1, the LIE is set to high. The cascading of multiple SDUs to form a complete PDU is accomplished non-real-time by NTR, and The segmentation is performed in real time through the layer between the aggregation L2 and the MAC layer, or through the MAC layer using the same SN as the group at the aggregation layer 2 or a new identifier at the MAC layer, or through a new layer between the aggregation L2 and the MAC layer.

Images