MAC-PHY MODEL FOR SIDELINK CARRIER (RE)SELECTION

Abstract

A method in a communication device having a plurality of protocol layers including a media access control, MAC, layer and a physical, PHY, layer, includes, at the MAC layer, selecting a plurality of carriers for carrier aggregation, each of the carriers being associated to a respective hybrid automatic repeat request, HARQ, entity, and at the MAC layer, initiating a sidelink carrier reselection process by the first communication device in response to a triggering event. Related devices and computer program products are disclosed.

Description

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Application No. 17/044,944, filed Oct. 2, 2020, which is a 35 U.S.C. § 371 national stage application of PCT International Application No. PCT/EP2019/058520 filed on Apr. 4, 2019, which in turn claims priority to U.S. Provisional Pat. Application No. 62/653,370, filed on Apr. 5, 2018, the disclosures and content of which are incorporated by reference herein in their entireties.

TECHNICAL FIELD

The present disclosure relates generally to communications, and more particularly, to wireless communications and related wireless devices and network nodes.

BACKGROUND

Sidelink (SL) is a long-term evolution (LTE) feature which enables device-to-device (D2D) communication within cellular-based LTE radio access networks. For example, as illustrated in FIG. 1, SL can be used to enable the direct communication (i.e., D2D) between proximal user equipments (UEs) such that the data does not need to go through a base station (eNB). Such D2D communication can be useful in public safety and commercial communication use-cases, and to vehicle-to-everything (V2X) scenarios. V2X communication is a type of communication which typically includes any combination of direct communication between vehicles, pedestrians, and infrastructure. V2X communication may use a network infrastructure, when available, but may also be used where lack of coverage is an issue. V2X communications may carry both non-safety and safety information, where each of the applications and services may be associated with specific requirements sets, such as requirements regarding latency, reliability, and capacity.

The European Telecommunications Standards Institute (ETSI) has defined two types of messages for road safety: (1) Co-operative Awareness Message (CAM), and (2) Decentralized Environmental Notification Message (DENM). CAM messages are intended to enable vehicles, including emergency vehicles, to notify their presence and other relevant parameters in a broadcast fashion. Such messages target other vehicles, pedestrians, and infrastructure, and are handled by their applications. CAM message also serves as active assistance to safety driving for normal traffic. The availability of a CAM message is typically indicatively checked approximately every 100 milliseconds (ms), yielding a maximum detection latency requirement of less than or equal to 100 ms for most messages. However, the latency requirement for pre-crash sensing warning is 50 ms. DENM messages are event-triggered messages, which are triggered by events such as by braking, and the availability of a DENM message is also typically checked approximately every 100 ms. For DENM messages, the requirement of maximum latency is less than or equal to 100 ms. The package size of CAM and DENM message typically varies from greater than 100 bytes to greater than 800 bytes, with a typical size around 300 bytes. In this regard, the message is supposed to be detected by all vehicles in proximity.

The Society of Automotive Engineers (SAE) has also defined the Basic Safety Message (BSM) for DSRC (Distributed Short Range Communications) with various defined messages sizes. According to the importance and urgency of a message, the BSM further classifies such messages into different priorities.

SUMMARY

Some embodiments provide a method in a first communication device having a plurality of protocol layers including a media access control, MAC, layer and a physical, PHY, layer, includes receiving, at the MAC layer, data for transmission over a sidelink interface to a second communication device, generating, at the MAC layer, first and second MAC protocol data units, PDUs, from the data, providing the first and second MAC PDUs from the MAC layer to the PHY layer for transmission in a first transmission time interval, TTI, along with an indication of selected first and second carriers from a set of available carriers that the PHY layer should use for transmission of the first and second MAC PDUs in a sidelink transmission to the second communication device, respectively, and receiving, at the MAC layer, an acknowledgement from the PHY layer, the acknowledgement indicating whether or not the transmission of the first and second MAC PDUs on the selected first and second carriers was performed successfully.

Some further embodiments provide a method in a communication device having a plurality of protocol layers including a media access control, MAC, layer and a physical, PHY, layer, includes at the MAC layer, selecting a plurality of carriers for carrier aggregation, each of the carriers being associated to a respective hybrid automatic repeat request, HARQ, entity, at the MAC layer, initiating a sidelink resource reselection process by the first communication device in response to a triggering event, and determining an identity of a carrier associated with the triggering event, wherein initiating the sidelink resource reselection process is performed only for the carrier and associated HARQ event associated with the triggering event.

Related wireless communications devices are also disclosed.

Systems/methods according to some embodiments provide cross-layer signaling between MAC and PHY layers in a V2X device that enhance carrier reselection for sidelink carriers, and in particular, enhance the selection of carriers on which MAC PDUs can be delivered simultaneously on a sidelink.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in a constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

FIG. 1 is a diagram illustrating a wireless device UE according to some embodiments of inventive concepts, wherein vehicle-to-everything and device-to-device communications are illustrated in a communications network;

FIG. 2 is a block diagram illustrating a wireless device UE according to some embodiments of inventive concepts;

FIG. 3 is a block diagram illustrating a network node eNB according to some embodiments of inventive concepts;

FIG. 4 is a block diagram illustrating E-UTRAN protocol layers;

FIGS. 5-7, 8A, 8B and 9 are flowcharts illustrating operations of systems/methods according to some embodiments of inventive concepts;

FIG. 10 is a block diagram of a wireless network in accordance with some embodiments;

FIG. 11 is a block diagram of a user equipment in accordance with some embodiments

FIG. 12 is a block diagram of a virtualization environment in accordance with some embodiments;

FIG. 13 is a block diagram of a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments;

FIG. 14 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments;

FIG. 15 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments;

FIG. 16 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments;

FIG. 17 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments; and

FIG. 18 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

DETAILED DESCRIPTION

Inventive concepts will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.

The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded upon without departing from the scope of the described subject matter.

FIG. 2 is a block diagram illustrating elements of a wireless device user equipment (200) (also referred to as a wireless terminal, a wireless communication device, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.) configured to provide wireless communication according to embodiments of inventive concepts. As shown, wireless device 200 may include an antenna 207, and a transceiver circuit 201 (also referred to as a transceiver) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station eNB of a wireless communication network (also referred to as a radio access network (RAN)). Wireless device 200 may also include a processor circuit 203 (also referred to as a processor) coupled to the transceiver circuit, and a memory circuit 205 (also referred to as memory) coupled to the processor circuit. The memory circuit 205 may include computer readable program code that when executed by the processor circuit 203 causes the processor circuit to perform operations according to embodiments disclosed herein. According to other embodiments, processor circuit 203 may be defined to include memory so that a separate memory circuit is not required. Wireless device 200 may also include an interface (such as a user interface) coupled with processor 03, and/or wireless device 200 may be an IoT and/or MTC device.

As discussed herein, operations of wireless device 200 may be performed by processor 203 and/or transceiver 201. For example, processor 203 may control transceiver 201 to transmit uplink communications through transceiver 201 over a radio interface to a base station eNB of a wireless communication network and/or to receive downlink communications through transceiver 201 from a base station eNB of the wireless communication network over a radio interface. Moreover, modules may be stored in memory 205, and these modules may provide instructions so that when instructions of a module are executed by processor 203, processor 203 performs respective operations (e.g., operations discussed below with respect to Example Embodiments).

FIG. 3 is a block diagram illustrating elements of a node 300 (also referred to as a network node, base station, eNB, eNodeB, gNB, gNodeB, etc.) of a wireless communication network (also referred to as a Radio Access Network RAN) configured to provide cellular communication according to embodiments of inventive concepts. As shown, the network node may include a transceiver circuit 301 (also referred to as a transceiver) including a transmitter and a receiver configured to provide uplink and downlink radio communications with wireless devices. The network node 300 may include a network interface circuit 307 (also referred to as a network interface) configured to provide communications with other nodes (e.g., with other base stations and/or core network nodes) of the RAN. The network node 300 may also include a processor circuit 303 (also referred to as a processor) coupled to the transceiver circuit, and a memory circuit 305 (also referred to as memory) coupled to the processor circuit. The memory circuit 305 may include computer readable program code that when executed by the processor circuit 303 causes the processor circuit to perform operations according to embodiments disclosed herein. According to other embodiments, processor circuit 303 may be defined to include memory so that a separate memory circuit is not required.

As discussed herein, operations of the network node 300 may be performed by processor 303, network interface 307, and/or transceiver 301. For example, processor 303 may control transceiver 301 to transmit downlink communications through transceiver 301 over a radio interface to one or more UEs and/or to receive uplink communications through transceiver 301 from one or more UEs over a radio interface. Similarly, processor 303 may control network interface 307 to transmit communications through network interface 307 to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes. Moreover, modules may be stored in memory 305, and these modules may provide instructions so that when instructions of a module are executed by processor 303, processor 303 performs respective operations (e.g., operations discussed below with respect to Example Embodiments).

The Evolved Universal Terrestrial Radio Access Network (E-UTRAN) is the radio access network architecture defined for the E-UTRA radio interface as a part of the 3GPP LTE physical layer specification. In the E-UTRA, data flows and is altered across various protocol layers. In this regard, FIG. 4 illustrates an example of a logical diagram of E-UTRAN protocol layers. As illustrated in FIG. 4, data in the form of IP packets are routed from the IP layer to the packet data convergence protocol (PDCP) layer. At the PDCP layer, the data packets are referred to as PDCP service data units (SDUs). At the PDCP layer, the PDCP SDUs are altered using header compression and a PDCP header (PDCP HDR) is appended thereon, thereby forming PDCP protocol data units (PDUs). Once the PDCP PDUs are formed, they are transferred to the radio link control (RLC) layer as RLC SDUs. The RLC SDUs are segmented to become RLC PDU, and an RLC header is appended thereon. The RLC PDUs are sent to the media access control (MAC) layer so that a MAC header (MAC HDR) and padding (PAD) can be appended as illustrated in FIG. 4, thereby forming a MAC PDU. Once formed, the MAC PDU is sent to the physical (PHY) layer, where it is referred to as a transport block (TB). The transport block in this layer is thereafter set to be transmitted over physical channels to other UEs, for example. In this manner, as one non-limiting example, vehicle-to-everything (V2X) communications can be provided.

In providing such communications, an LTE-based V2X interface may be advantageous because of the economies of scale associated with LTE. Further, providing an LTE-based V2X interface may be advantageous because it may enable enhanced integration between communications with the network infrastructure, vehicle-to-infrastructure (V2I) communications, vehicle-to-pedestrian (V2P) communications, and vehicle-to-vehicle (V2V) communications, as compared to using a dedicated V2X technology.

Modes of operation (sometimes referred to as transmission modes or resource allocation modes) for V2X UEs include Mode 3 and Mode 4. Mode 4 is also referred to as the autonomous mode because the UE typically can make decisions related to transmission on its own. Generally, in Mode 4, the UE selects the time-frequency resources to use for transmission from a large set of resources configured by the network or preconfigured in the UE. In other words, the UE performs autonomous resource allocation (also referred to as distributed resource allocation).

Autonomous resource allocation in Mode 4 typically makes combined use of two features: semi-persistent transmission and sensing-based resource allocation. Semi-persistent transmission exploits the fact that typical safety V2X traffic is approximately periodic (i.e., new packets are generated at regular intervals). Since packet arrivals are periodic, a transmitting UE can notify other UEs about its intention to use certain time-frequency resources for future transmissions. Whereas, sensing consists of monitoring the radio channel to learn about the presence of such semi-persistent transmissions. In this way, UEs can avoid collisions when selecting their resources for their own transmissions. This is also referred to as sensing-based resource allocation.

Mode 4 semi-persistent scheduling (SPS) is also known as resource reservation or resource booking, since it involves a set of time/frequency resources potentially reserved for future transmissions. Depending on the actual usage of such resources, resource reselection may be triggered to avoid excessive resource consumption. Other triggering criteria instead imply that resource reselection is triggered due to the fact that the actual MAC PDU to transmit is not tailored for the time/frequency grant previously reserved. For example, if a grant is too small or a grant is coming too late in time with respect to the packet delay budget of a MAC PDU.

Such resource reselection triggering criteria are conventionally specified in MAC layer. In conventional specifications, seven different criteria are typically used. Under the first criterion, resource reselection is triggered if SL _RESOURCE_RESELECTION_COUNTER = 0 and, when SL_RESOURCE_RESELECTION_COUNTER was equal to 1, the MAC entity randomly selected, with equal probability, a value in the interval [0, 1], which is above the probability configured by upper layers in probResourceKeep. Under the second criterion, resource reselection is triggered if neither transmission nor retransmission has been performed by the MAC entity on any resource indicated in the configured sidelink grant during the last second. Under the third criterion, resource reselection is triggered if sl-ReselectAfter is configured and the number of consecutive unused transmission opportunities on resources indicated in the configured sidelink grant is equal to sl-ReselectAfter. Under the fourth criterion, resource reselection is triggered if there is no configured sidelink grant. Under the fifth criterion, resource reselection is triggered if the configured sidelink grant cannot accommodate an RLC SDU by using the maximum allowed MCS configured by upper layers in maxMCS-PSSCH and the MAC entity selects not to segment the RLC SDU. Under the sixth criterion, resource reselection is triggered if transmission(s) with the configured sidelink grant cannot fulfil the latency requirement of the data in a sidelink logical channel according to the associated PPPP, and the MAC entity selects not to perform transmission(s) corresponding to a single MAC PDU. Under the seventh criterion, resource reselection is triggered if a pool of resources is configured or reconfigured by upper layers.

With regard to sensing-based resource allocation, sensing-based resource allocation in the LTE specification generally consists of two different parts. The first part is sensing channel resources. The procedure in TS 36.213 of the 3GPP specification describes how a UE is expected to sense the channel during a certain period of time (1 second) and use received signals to predict the future utilization of the radio resources. Based on this predicted utilization, the UE creates a list of radio resources (i.e., time-frequency resources) that may be selected for transmission. This list is typically a subset of all the radio resources; that is, some resources are excluded as candidates for selection (e.g., because the UE predicts that they will be used by another UE). The second part is resource allocation. The procedure in TS 36.321 describes how the UE selects the resources it needs for transmission from the list of candidate resources provided by sensing.

Enhancements to conventional LTE V2X functionalities may be desirable. One such desirable functionality involves carrier aggregation (CA), which consists of performing simultaneous transmissions over multiple carriers. By using CA, it is possible to transmit larger packets, achieve larger transmission rates (in bits per second), and/or increase the reliability of the system (e.g., by transmitting the same packet over multiple carriers). The transmissions over multiple carriers may take place at the same time or at different times (usually separated by a few milliseconds).

To support carrier aggregation, particular UE mechanisms to select the different SL carriers may be useful. Different criteria can be used, such as the congestion of the carriers, the amount of data that a UE wants to deliver, the UE capabilities, power consumptions, and RF requirements. In this regard, which carrier(s) to select is therefore a decision that can involve information that is available at the MAC layer (such as the volume of data to transmit), and physical layer aspects (such as the UE capabilities and the power budget available).

When sidelink carrier (re)selection is triggered at the MAC layer, the MAC layer may not be aware of whether the carrier(s) selected can actually be used by physical layer for transmission. The MAC may select a certain set of carriers on the basis of MAC-related criteria, such as volume of data to transmit and/or on the basis of whether resource reselection is triggered.

In this regard, none of the above conditions take into account potential limitations at physical layer, so that once MAC PDUs are selected for simultaneous transmissions on different sidelink carriers, it may happen the physical layer (PHY) of the UE is not able to deliver all of the MAC PDUs because of limited transmission (TX) capabilities, RF requirements, power spectral density (PSD) imbalance across carriers, and/or power budget limitations.

Additionally, from the above conditions, it can be unclear whether the above resource reselection criteria should trigger carrier reselection for all carriers (which are currently in use for V2X SL communications) or only for some of those carriers or for none of the carriers.

In this regard, in some embodiments disclosed herein, methods to model MAC-PHY interaction (i.e., cross-layer signaling) for TX carrier(s) (re)selection and to describe the MAC behavior on how and on which carrier(s) to perform carrier(s) (re)selection and/or when resource (re)selection is triggered are disclosed. In this manner a MAC-PHY UE model to select a set of carriers on which MAC PDUs can be delivered simultaneously is provided.

In embodiments disclosed herein, the terminology MAC PDU and transport block (TB) are used interchangeably to indicate a transport block, selected by the MAC layer (i.e., a MAC PDU) for transmission to the physical layer. The term “same TTI” and/or “simultaneous transmission” used in the description below refers to time intervals or transmissions that are fully aligned/overlapping in time, but also to refer cases in which the transmissions of MAC PDUs on different carriers are not fully aligned in time, but for example, are within a predetermined time window, such as within a time window that a UE would need to retune/re-sync from one carrier to another. For example, assume PDU 1 is transmitted on carrier 1 during TTI1 and PDU 2 is transmitted on carrier 2 in TTI2, where TTI2 is adjacent to TTI1. Such a situation may be considered “simultaneous transmission” for purposes of the present discussion. To generalize, it could be said that if at time T1 the UE transmits in carrier 1, such UE cannot transmit in carrier 2 at time T2 wherein (T2-T1) < time threshold, where the time threshold is defined as the time the UE needs to retune/re-sync to carrier 2, then transmissions at T2 and T1 are said to be simultaneous transmissions.

In one embodiment, the MAC layer selects a certain set of carriers “A” for transmissions to lower layers, i.e., it prepares one MAC PDU for each carrier selected for transmissions on the same TTI. The HARQ entity associated to each carrier delivers the MAC PDU to the physical layer (PHY) for transmissions on the corresponding carrier.

Upon receiving MAC PDUs, i.e., TBs, for transmission on the different carriers, the physical layer evaluates whether such MAC PDUs can be transmitted in the same TTI on the selected carriers. The decision regarding whether to transmit on the carrier(s) or not can depend on the following:

• whether PHY is capable of transmitting on the selected carriers simultaneously (for example, if the given carrier combination is not supported);
• whether the power budget for transmissions on such carriers is not overwhelmed;
• whether the transmissions on multiple carriers simultaneously lead to power spectral density (PSD) imbalance;
• whether there is no other strong interfering node detected on the same carrier (for example, upon sensing or upon exemplary listen before talk (LBT) procedures, or feedback from neighboring UEs on the presence of potential interferers);
• whether some carriers are too busy to receive SL data, or are monitoring Uu transmissions;
• whether some carriers are too busy to receive/monitor Uu data or transmit Uu data; and/or
• whether PHY is capable of transmitting due to limitation on TX switching time.

In some embodiments, PHY selects all carriers of the set A indicated by the MAC layer for transmission on the radio interface. In some embodiments, PHY only selects a subset of carriers belonging to set A for transmission. In some embodiments, PHY does not perform transmission on any carrier of set A.

In some embodiments, depending on whether all carriers of the set A are effectively used for transmission of the corresponding TBs, or only a subset or none, PHY sends feedback to MAC indicating the outcome of the transmission. The outcome can be a PHY ACK in case all TBs have been used, NACK in case none of the TBs has been transmitted, or an array of PHY feedbacks indicating for each carrier/TB whether the corresponding TB has been transmitted or not (ACK/NACK).

In some embodiments where one or more TBs have not been transmitted by the PHY, PHY may also indicate the reason why TB transmission(s) failed. For example, PHY may indicate the set of carriers, and associated time/frequency resources which MAC should not select for simultaneous transmission in a certain time window, or in the next number of TTIs or never in time. In some embodiments, additional information is provided by PHY to restrict the use of certain carrier(s). For instance, if PHY sees that it cannot support a certain carrier combination or TX switching times or power allocation are too restrictive to provide good system performance.

In some embodiments, the following actions may be taken by MAC for the TB transmissions for which PHY feedback was NACK at time T1.

The MAC can exclude for simultaneous transmission on different carriers some MAC PDUs that were not transmitted at a time T1, as per PHY indication. For example, if PHY indicated that a first transport block TB1 in carrier 1 and a second transport block TB2 in carrier 2 can be transmitted simultaneously but not a third transport block TB3 in carrier 3, MAC can select in one of the next TTI at a time T2 greater than or equal to time T1, resources to transmit TB1 and TB2, while TB3 is postponed for transmission at time T3 and carrier 3 is not selected for transmission at time T2. In some embodiments, TB3 is postponed for transmission based on the latency requirements (which can be acquired using PPPP associated to the TB).

Additional actions in some embodiments also include MAC triggering carrier reselection and/or resource reselection for transmission of such TBs, by either performing resource reservation of a new set(s) of time-frequency resources in the same or different carriers than the one or more previously selected (i.e., configuring a new SL grant), or by performing transmission of a TB without reserving resources. For example, MAC may select again TB1 and TB2 for transmission on carrier 1 and carrier 2 respectively for transmission at time T2, and it may select another carrier (different from carrier 3) for transmission of TB3 still at time T2. Or in another alternative only resource reselection is triggered (i.e., MAC just selects another set of time/frequency resources for simultaneous transmission of TB 1/TB2/TB3 in different carriers, but still keep carriers 1/2/3 for transmission (i.e., it does not perform carrier reselection)).

In other embodiments, actions include, in case PHY only provides ACK/NACK for the MAC PDUs previously scheduled by MAC, with no additional indication, MAC performing either carrier reselection for the carriers in which MAC PDUs could not be transmitted by PHY, and/or performing resource reselection on the basis of resource availability indicated by PHY which can also be acquired upon sensing (i.e., before MAC delivered to PHY the concerned MAC PDUs at time T1). MAC may not take into account the reasons for which MAC PDUs were not transmitted at time T1, in case PHY did not provide such indication to MAC.

In other embodiments, MAC can put back in the RLC buffer the TBs that were not transmitted at time T1 in case those TBs correspond to initial transmission (i.e., not retransmission). Depending on when MAC decides to select a transmitting grant and the size of the selected grant, segmentation/concatenation and logical channel prioritization can be performed again in some embodiments.

In other embodiments, MAC can store the information that a certain carrier combination and/or the time-frequency resources for which transmission was not successful at time T1, so that the same combination will not be used again in a later occasion.

In other embodiments, MAC may not step transmission counters related to the TBs that were not transmitted. For instance, MAC may not step the retransmission counter, the CURRENT_IRV counter that steps the RVI in physical layer, and/or the SL_RESOURCE_RESELECTION_COUNTER which counts the usage of reserved time/frequency resources. In another embodiment, the SL_RESOURCE_RESELECTION_COUNTER is stepped considering that the UE tries to transmit. Similarly, the sl-ReselectAfter counter may not be stepped since the UE, in some embodiments, did try to transmit on a certain resource though it did not manage.

According to some embodiments, the PHY layer may also indicate whether the unsuccessful transmission is of transmission or retransmissions (i.e., 1st or 2nd transmission of same TB). If a TB corresponding to retransmission is unsuccessful, then MAC can choose to just drop the transmission instead of performing the above-mentioned procedures. Furthermore, MAC can apply some further limitations while again scheduling the drop TB corresponding to retransmissions. For instance, in some embodiments, MAC may not select a different carrier than its original transmission. In some embodiments, extra signaling is performed to assist the Rx UE which indicates/refers to the original transmission if time/frequency resources are only reselected for retransmissions.

The above procedure(s) may be repeated until all TBs are transmitted by the physical layer. For example, in considering that either all or none of the MAC PDUs initially selected by MAC can be transmitted by PHY, MAC may try to select a different set of carriers and/or timer/frequency resources until all TBs are transmitted by PHY, in which case PHY will signal ACK.

In some embodiments, the following actions may be taken by MAC for the TB transmissions for which PHY feedback was ACK at time T1. The MAC layer can consider the packet transmitted over the air. This implies that the SL_RESOURCE_RESELECTION_COUNTER is stepped down, the CURRENT _IRV is stepped, and the retransmission counter is stepped. In additional embodiments, MAC stores the info that at time T1 a certain combination of SL carriers were successfully used for transmission.

With regard to carrier selection upon resource reselection, in some embodiments, carrier selection may be triggered for one or more carriers depending on the type of trigger for the resource reselection. For example, if the MAC entity triggers carrier reselection for all carriers whenever one triggering condition is met there might be a risk of having carrier switches occurring too frequently because some triggering condition might affect only operations in one specific HARQ entity/carrier. For example, if the carrier selection is triggered because of SL_RESOURCE_RESELECTION_COUNTER = 0 for one HARQ entity/carrier, there may be no need to trigger carrier reselection for all other carriers currently in use, with reserved resources. Similarly, if there is a TX capability issue only with some of the carriers in set A, PHY may indicate that a subset B of carriers in set A can be used simultaneously, while another subset C of carriers in set A cannot be used simultaneously. In such a case, carrier reselection may be performed for those carriers in subset C. Furthermore, to increase the system performance, PHY can also indicate the restriction of the use of multiple carriers simultaneously by MAC layer.

In this regard, in some embodiments, carrier reselection may be triggered for the specific carrier/HARQ entity in which a certain event occurred. In additional embodiments, events that affect a specific carrier/HARQ entity are included, however such embodiments may not be limited by the below events:

• For a specific carrier/HARQ entity, if SL_RESOURCE_RESELECTION_COUNTER = 0 and, when SL_RESOURCE_RESELECTION_COUNTER was equal to 1, the MAC entity randomly selected, with equal probability, a value in the interval [0, 1] which is above the probability configured by upper layers in probResourceKeep;
• if neither transmission nor retransmission has been performed by the MAC entity on any resource indicated in the configured sidelink grant during the last second for a specific carrier/HARQ entity;
• if sl-ReselectAfter is configured and the number of consecutive unused transmission opportunities on resources indicated in the configured sidelink grant is equal to sl-ReselectAfter, for a specific carrier/HARQ entity;
• if a pool of resources is configured or reconfigured by upper layers for a specific carrier; and/or
• if capability issues, power limitations or other radio problems (as the one indicated in previous section) only affect a specific carrier.

After triggering carrier reselection, the MAC entity may also perform the following actions in additional embodiments:

• continue using the same sidelink carrier affected by any of the events above (and perform resource reselection on that carrier (i.e., configure a new SL grant));
• select another sidelink carrier and configure another SL grant (i.e., perform resource selection) and stop using the sidelink carrier affected by any of the events above;
• select multiple sidelink carriers and configure other SL grants (i.e., perform resource selection) and stop using the sidelink carriers affected by any of the events above;
• stop using the sidelink carrier affected by any of the events above, and not select any other sidelink carrier; and/or
• perform one single transmission rather than selecting a carrier for resource reservation.

In other embodiments, carrier reselection may be triggered for more than one carrier. For example, for events that impact the UE behavior, such as the MAC entity behavior, irrespective of the specific per HARQ entity/carrier operations. Such events include, but are not limited to, those performance criteria that may not be met for none of the sidelink grants already configured in the different sidelink carriers:

• if there is no configured sidelink grant in any SL carrier;
• if the configured sidelink grant cannot accommodate a RLC SDU by using the maximum allowed MCS configured by upper layers in maxMCS-PSSCH for any SL carrier with configured SL grant and the MAC entity selects not to segment the RLC SDU;
• if transmission(s) with the configured sidelink grant cannot fulfil the latency requirement of the data in a sidelink logical channel according to the associated PPPP for any SL carrier with configured SL grant; and the MAC entity selects not to perform transmission(s) corresponding to a single MAC PDU;
• if the UE capability and/or power limitations are experienced by potential simultaneous transmissions in multiple carriers; and/or
• if transmissions with the configured sidelink grant are such that the UE is unable to listen/sense the carriers for a long time due to half duplex limitation. For instance, if the total transmission time of UE on all the selected carriers is more than a pre-defined threshold.

For carrier reselection triggered for the above reasons, the MAC entity may perform the following actions:

• continue using the same sidelink carriers, and perform resource reselection in one carrier;
• select another sidelink carrier and stop using any of the sidelink carriers with a configured sidelink grant;
• select multiple other sidelink carriers and stop using any of the sidelink carriers with a configured sidelink grant;
• stop using any of the sidelink carriers and not select any other sidelink carrier (i.e., just perform one shot transmission).

Operations of a wireless communication device, such as a UE or base station, will now be discussed with reference to the flowchart of FIG. 5 according to some embodiments of inventive concepts. For example, modules may be stored in wireless terminal memory 405 of FIG. 2, and these modules may provide instructions so that when the instructions of a module are executed by wireless device processor 4003, processor 4003 performs respective operations of the flow chart of FIG. 5. Similarly, modules may be stored in network node memory 5005 of FIG. 3, and these modules may provide instructions so that when the instructions of a module are executed by network node processor 5003, 5rocessor 4003 performs respective operations of the flow chart of FIG. 5.

According to some embodiments, a method in a first communication device having a plurality of protocol layers including a media access control, MAC, layer and a physical, PHY, layer, includes receiving (block 502), at the MAC layer, data for transmission over a sidelink interface to a second communication device. The method further includes generating (block 504) at the MAC layer, first and second MAC protocol data units, PDUs, from the data, and providing (block 506) the first and second MAC PDUs from the MAC layer to the PHY layer for simultaneous or near-simultaneous transmission in a first transmission time interval, TTI, along with an indication of selected first and second carriers from a set of available carriers that the PHY layer should use for transmission of the first and second MAC PDUs in a sidelink transmission to the second communication device, respectively. Finally, the method includes receiving (block 508), at the MAC layer, an acknowledgement from the PHY layer, the acknowledgement indicating whether or not the simultaneous transmission of the first and second MAC PDUs on the selected first and second carriers was performed successfully. The acknowledgement from the PHY layer may include a negative acknowledgement, NAK, the NAK indicating that the PHY layer was unable to transmit at least one of the first and second MAC PDUs on the respective selected carrier indicated by the MAC layer.

The acknowledgement may include an array of feedback indicators indicating whether transmission of respective MAC PDUs on the selected first and second carriers was successful.

Referring to FIG. 6, methods according to some embodiments further include receiving (block 602), from the PHY layer, an indication of a carrier that the MAC layer should not select for simultaneous transmission in future TTIs.

Methods according to some embodiments may further include, for a MAC PDU transmission for which a negative acknowledgement is received at the MAC layer, performing at least one of excluding the MAC PDU from simultaneous transmission on different carriers in subsequent TTIs, triggering carrier reselection and/or resource reselection for transmission of the MAC PDU in a subsequent TTI, returning the MAC PDU to a radio link control, RLC, buffer, storing information relating to a carrier combination and/or time/frequency resources for which the MAC PDU transmission was unsuccessful, and refraining from advancing a transmission counter relating to the MAC PDU that was not successfully transmitted. In particular, one or more MAC SDUs of the MAC PDU may be returned to the RLC buffer.

The transmission counter may include a retransmission counter, a CURRENT_IRV counter and/or a SL_RESOURCE_RESELECTION_COUNTER.

The method may further include in response to the acknowledgement indicating that the transmission of the first and second MAC PDUs on the selected first and second carriers was successful, storing information indicating that simultaneous transmission on the first and second carriers was successful.

The method may further include receiving an indication from the PHY layer that an unsuccessful transmission was a retransmission.

The method may further include in response to receiving the indication from the PHY layer that an unsuccessful transmission of a MAC PDU was a retransmission, dropping transmission of the MAC PDU.

The data received at the MAC layer for transmission includes a radio link control, RLC, layer service data unit, SDU.

Referring to FIG. 7, methods according to some embodiments may further include at the PHY layer, evaluating (block 702) whether the first and second MAC PDUs can be transmitted over the first and second carriers, respectively, within the first TTI, and generating (block 704) the acknowledgement indicating whether or not the simultaneous transmission of the first and second MAC PDUs on the selected first and second carriers was performed successfully based at least in part on the evaluation.

Evaluating whether the first and second MAC PDUs can be transmitted over the first and second carriers, respectively, within the first TTI may depend on at least one of whether the PHY is capable of transmitting on the first and second carriers simultaneously, whether a power budget for transmissions on the first and second carriers is overwhelmed, whether simultaneous transmissions on the first and second carriers may lead to power spectral density, PSD, imbalance, whether a strong interfering node is detected on the first or second carrier, whether the first or second carrier is busy to receiving sidelink data or monitoring Uu transmissions, whether the first or second carrier is busy receiving or transmitting Uu data, and whether the PHY layer is capable of transmitting on the first and second carriers due to a limitation on transmitter switching time.

Referring to FIG. 8A, a method in a communication device having a plurality of protocol layers including a media access control, MAC, layer and a physical, PHY, layer, includes at the MAC layer, selecting (802) a plurality of carriers for carrier aggregation, each of the carriers being associated to a respective hybrid automatic repeat request, HARQ, entity, at the MAC layer, initiating (804) a sidelink resource reselection process by the first communication device in response to a triggering event, and determining (806) an identity of a carrier associated with the triggering event, wherein initiating the sidelink resource reselection process is performed only for the carrier and associated HARQ event associated with the triggering event.

The method may further include, after initiating the sidelink resource reselection process, performing at least one of continuing to use a previous carrier and performing resource reselection on the previous carrier, selecting a second sidelink carrier and configuring a second sidelink grant on the second sidelink carrier, and ceasing to use the sidelink carrier and not selecting any other sidelink carrier.

Referring to FIG. 8B, in some embodiments, a method in a communication device having a plurality of protocol layers including a media access control, MAC, layer and a physical, PHY, layer, includes, at the MAC layer, selecting (block 812) a plurality of carriers for carrier aggregation, each of the carriers being associated to a respective hybrid automatic repeat request, HARQ, entity, and at the MAC layer, initiating (block 814) a sidelink carrier reselection process by the first communication device in response to a triggering event.

Initiating the sidelink carrier reselection process may be performed only for the carrier and associated HARQ event associated with the triggering event. In some embodiments, initiating the sidelink carrier reselection process is performed for all sidelink carriers configured for sidelink operations.

The method may further include, after initiating the sidelink carrier reselection process, performing at least one of: continuing to use a previous carrier and performing resource reselection on the previous carrier, selecting a second sidelink carrier (or multiple additional sidelink carriers) and configuring a second sidelink grant on the second sidelink carrier(s), and ceasing to use the sidelink carrier and not selecting any other sidelink carrier.

The triggering event may include at least one of: for a specific carrier/HARQ entity, if an SL_RESOURCE_RESELECTION_COUNTER = 0 and, when the SL_RESOURCE_RESELECTION_COUNTER was equal to 1, the MAC randomly selected, with equal probability, a value in an interval [0, 1] which is above a probability configured by upper layers, neither transmission nor retransmission has been performed by MAC on any resource indicated in a configured sidelink grant during a previous second for a specific carrier/HARQ entity, sl-ReselectAfter is configured and a number of consecutive unused transmission opportunities on resources indicated in the configured sidelink grant is equal to sl-ReselectAfter, for a specific carrier/HARQ entity, and/or a pool of resources is configured or reconfigured by upper layers for a specific carrier.

In some embodiments, the triggering event may include at least one of there is no configured sidelink grant in any sidelink carrier, a configured sidelink grant cannot accommodate an RLC SDU by using a maximum allowed modulation and coding scheme, MCS, configured by upper layers for any sidelink carrier with configured SL grant and the MAC entity selects not to segment the RLC SDU, transmission(s) with a configured sidelink grant cannot fulfil a latency requirement of data in a sidelink logical channel for any sidelink carrier with a configured sidelink grant, and the MAC selects not to perform transmission(s) corresponding to a single MAC PDU, UE capability and/or power limitations are experienced by potential simultaneous transmissions in multiple carriers, and/or transmissions with a configured sidelink grant are such that the UE is unable to listen/sense the carriers for a long time due to half duplex limitation.

FIG. 9 illustrates a method in a first communication device having a plurality of protocol layers including a media access control, MAC, layer and a physical, PHY, layer. The method includes receiving (block 902), at the MAC layer, data for transmission over a sidelink interface to a second communication device, generating (block 904), at the MAC layer, first and second MAC protocol data units, PDUs, from the data, receiving (block 906) information from the PHY layer regarding the availability of one or more carriers for transmitting the first and second MAC PDUs, performing (block 908) a carrier selection or reselection procedure to select first and second carriers from the one or more carriers for transmission of the first and second MAC PDUs based on the information from the PHY layer, and providing (block 910) the first and second MAC PDUs from the MAC layer to the PHY layer for simultaneous transmission in a first transmission time interval, TTI, along with an indication of the selected first and second carriers.

The information from the PHY layer may include an indication of a carrier or time/frequency resources on the carrier that the MAC layer should not select for simultaneous transmission in the future.

The information from the PHY layer may include an indication of a carrier combination and/or time/frequency resources that the information from the PHY layer indicates is unavailable for transmission.

The information from the PHY layer may include an indication of a carrier combination and/or time/frequency resources that the information from the PHY layer indicates is available for transmission.

The method may further include MAC triggering carrier reselection and/or resource reselection for transmission of at least one of the first and second MAC PDUs excluding the time/frequency resources for simultaneous transmissions of MAC PDUs in different carriers as indicated by PHY, and storing information relating to a carrier combination and/or time/frequency resources that the information from the PHY layer indicates is unavailable for transmission.

In some embodiments, for example, when the available set of time/frequency resources is not sufficient to accommodate the MAC PDTU, the method may include returning one or more MAC SDUs of at least one of the first and second MAC PDUs to a radio link control, RLC, buffer.

The data received at the MAC layer for transmission may include a radio link control, RLC, layer service data unit, SDU.

The method may further include generating, at the PHY layer, an indication of whether or not simultaneous transmission of the first and second MAC PDUs on the selected first and second carriers can be performed successfully, and transmitting the indication to the MAC layer.

Evaluating whether the first and second MAC PDUs can be transmitted over the first and second carriers, respectively, within the first TTI may depend on at least one of: whether the PHY is capable of transmitting on the first and second carriers simultaneously, whether a power budget for transmissions on the first and second carriers is overwhelmed, whether simultaneous transmissions on the first and second carriers may lead to power spectral density, PSD, imbalance, whether a strong interfering node is detected on the first or second carrier, whether the first or second carrier is busy to receiving sidelink data or monitoring Uu transmissions, whether the first or second carrier is busy receiving or transmitting Uu data, and whether the PHY layer is capable of transmitting on the first and second carriers due to a limitation on transmitter switching time.

Example embodiments of inventive concepts are set forth below.

• Embodiment 1. A method in a first communication device having a plurality of protocol layers including a media access control, MAC, layer and a physical, PHY, layer, the method comprising:
  • receiving, at the MAC layer, data for transmission over a sidelink interface to a second communication device;
  • generating, at the MAC layer, first and second MAC protocol data units, PDUs, from the data;
  • providing the first and second MAC PDUs from the MAC layer to the PHY layer for simultaneous transmission in a first transmission time interval, TTI, along with an indication of selected first and second carriers from a set of available carriers that the PHY layer should use for transmission of the first and second MAC PDUs in a sidelink transmission to the second communication device, respectively; and
  • receiving, at the MAC layer, an acknowledgement from the PHY layer, the acknowledgement indicating whether or not the simultaneous transmission of the first and second MAC PDUs on the selected first and second carriers was performed successfully.
• Embodiment 2. The method of Embodiment 1, wherein the acknowledgement from the PHY layer comprises a negative acknowledgement, NAK, the NAK indicating that the PHY layer was unable to transmit at least one of the first and second MAC PDUs on the respective selected carrier indicated by the MAC layer.
• Embodiment 3. The method of Embodiment 1 or 2, wherein the acknowledgement comprises an array of feedback indicators indicating whether transmission of respective MAC PDUs on the selected first and second carriers was successful.
• Embodiment 4. The method of any previous Embodiment, further comprising:
  • receiving, from the PHY layer, an indication of a carrier that the MAC layer should not select for simultaneous transmission in future TTIs.
• Embodiment 5. The method of any previous Embodiment, further comprising:
  • for a MAC PDU transmission for which a negative acknowledgement is received at the MAC layer, performing at least one of:
  • excluding the MAC PDU from simultaneous transmission on different carriers in subsequent TTIs;
  • triggering carrier reselection and/or resource reselection for transmission of the MAC PDU in a subsequent TTI;
  • returning the MAC PDU to a radio link control, RLC, buffer;
  • storing information relating to a carrier combination and/or time/frequency resources for which the MAC PDU transmission was unsuccessful; and
  • refraining from advancing a transmission counter relating to the MAC PDU that was not successfully transmitted.
• Embodiment 6. The method of Embodiment 5, wherein the transmission counter comprises a retransmission counter, a CURRENT_IRV counter and/or a SL_RESOURCE_RESELECTION_COUNTER.
• Embodiment 7. The method of any previous Embodiment, further comprising:
  • in response to the acknowledgement indicating that the transmission of the first and second MAC PDUs on the selected first and second carriers was successful, storing information indicating that simultaneous transmission on the first and second carriers was successful.
• Embodiment 8. The method of any previous Embodiment, further comprising:
  • receiving an indication from the PHY layer that an unsuccessful transmission was a retransmission.
• Embodiment 9. The method of Embodiment 8, further comprising:
  • in response to receiving the indication from the PHY layer that an unsuccessful transmission of a MAC PDU was a retransmission, dropping transmission of the MAC PDU.
• Embodiment 10. The method of Embodiment 1, wherein the data received at the MAC layer for transmission comprises a radio link control, RLC, layer service data unit, SDU.
• Embodiment 11. The method of any previous Embodiment, further comprising:
  • at the PHY layer, evaluating whether the first and second MAC PDUs can be transmitted over the first and second carriers, respectively, within the first TTI; and
  • generating the acknowledgement indicating whether or not the simultaneous transmission of the first and second MAC PDUs on the selected first and second carriers was performed successfully based at least in part on the evaluation.
• Embodiment 12. The method of Embodiment 11, wherein evaluating whether the first and second MAC PDUs can be transmitted over the first and second carriers, respectively, within the first TTI depends on at least one of: whether the PHY is capable of transmitting on the first and second carriers simultaneously; whether a power budget for transmissions on the first and second carriers is overwhelmed; whether simultaneous transmissions on the first and second carriers may lead to power spectral density, PSD, imbalance; whether a strong interfering node is detected on the first or second carrier; whether the first or second carrier is busy to receiving sidelink data or monitoring Uu transmissions; whether the first or second carrier is busy receiving or transmitting Uu data; and whether the PHY layer is capable of transmitting on the first and second carriers due to a limitation on transmitter switching time.
• Embodiment 13. A first wireless device (UE) comprising:
  • a transceiver (4001) configured to provide wireless network communication with a wireless communication network; and
  • a processor (4003) coupled with the transceiver, wherein the processor is configured to provide wireless network communication through the transceiver, and wherein the processor is configured to perform operations according to any of Embodiments 1 to 12.
• Embodiment 14. A wireless device (UE) wherein the wireless terminal is adapted to perform according to any of Embodiments 1 to 12.
• Embodiment 15. A base station (eNB) of a wireless communication network, the base station comprising:
  • a transceiver (5001) configured to provide wireless network communication with a wireless terminal; and
  • a processor (5003) coupled with the transceiver, wherein the processor is configured to provide wireless network communications through the transceiver, and wherein the processor is configured to perform operations according to any of Embodiments 1 to 12.
• Embodiment 16. A base station (eNB) of a radio access network, wherein the base station is adapted to perform according to any of Embodiments 1 to 12.
• Embodiment 17. A method in a communication device having a plurality of protocol layers including a media access control, MAC, layer and a physical, PHY, layer, the method comprising:
  • at the MAC layer, selecting a plurality of carriers for carrier aggregation, each of the carriers being associated to a respective hybrid automatic repeat request, HARQ, entity;
  • at the MAC layer, initiating a sidelink resource reselection process by the first communication device in response to a triggering event; and
  • determining an identity of a carrier associated with the triggering event;
  • wherein initiating the sidelink resource reselection process is performed only for the carrier and associated HARQ event associated with the triggering event.
• Embodiment 18. The method of Embodiment 17, further comprising:
  • after initiating the sidelink resource reselection process, performing at least one of: continuing to use a previous carrier and performing resource reselection on the previous carrier; selecting a second sidelink carrier and configuring a second sidelink grant on the second sidelink carrier; and ceasing to use the sidelink carrier and not selecting any other sidelink carrier.
• Embodiment 19. A first wireless device (UE) comprising:
  • a transceiver (4001) configured to provide wireless network communication with a wireless communication network; and
  • a processor (4003) coupled with the transceiver, wherein the processor is configured to provide wireless network communication through the transceiver, and wherein the processor is configured to perform operations according to any of Embodiments 17 to 18.
• Embodiment 20. A wireless device (UE) wherein the wireless terminal is adapted to perform according to any of Embodiments 17 to 18.
• Embodiment 21. A base station (eNB) of a wireless communication network, the base station comprising:
  • a transceiver (5001) configured to provide wireless network communication with a wireless terminal; and
  • a processor (5003) coupled with the transceiver, wherein the processor is configured to provide wireless network communications through the transceiver, and wherein the processor is configured to perform operations according to any of Embodiments 17 to 18.
• Embodiment 22. A base station (eNB) of a radio access network, wherein the base station is adapted to perform according to any of Embodiments 17 to 18.
• Embodiment 23. The method of Embodiment 5, wherein returning the MAC PDU to the RLC buffer comprises returning one or more MAC service data units, SDUs, of the MAC PDU to the RLC buffer.

Explanations for abbreviations from the above disclosure are provided below.

Abbreviation Explanation
CAM          Collective awareness message
CBR          Channel busy ratio
CR           Channel ratio or occupancy ratio
DENM         Decentralized environmental notification message
NW           Network
PPPP         ProSe Per-Packet Priority
ProSe        Proximity Services
RRC          Radio Resource Control
RSRP         Reference Signal Received Power
RSSI         Received Signal Strength Indicator
UE           User equipment
V2I          Vehicle-to-infrastructure
V2P          Vehicle-to-pedestrian
V2V          Vehicle-to-vehicle
V2X          Vehicle-to-anything
MAC          Medium Access Control
PHY          Physical Layer
PSD          Power Spectral Density
PDU          Protocol Data Unit
RLC          Radio Link Control
TB           Transport Block
SDU          Service Data Unit
SL           Sidelink
PHY          Physical Layer

Further definitions and embodiments are discussed below.

In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

When an element is referred to as being “connected”, “coupled”, “responsive”, or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being “directly connected”, “directly coupled”, “directly responsive”, or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, “coupled”, “connected”, “responsive”, or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term “and/or” includes any and all combinations of one or more of the associated listed items.

It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another element/operation. Thus, a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.

As used herein, the terms “comprise”, “comprising”, “comprises”, “include”, “including”, “includes”, “have”, “has”, “having”, or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation “e.g.”, which derives from the Latin phrase “exempli gratia,” may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation “i.e.”, which derives from the Latin phrase “id est,” may be used to specify a particular item from a more general recitation.

Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).

These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as “circuitry,” “a module” or variants thereof.

It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

Additional explanation is provided below.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to alan/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

FIG. 10: A wireless network in accordance with some embodiments.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIG. 10. For simplicity, the wireless network of FIG. 10 only depicts network 1006, network nodes 1060 and 1060b, and WDs 1010, 1010b, and 1010c (also referred to as mobile terminals). In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 1060 and wireless device (WD) 1010 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network 1006 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node 1060 and WD 1010 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In FIG. 10, network node 1060 includes processing circuitry 1070, device readable medium 1080, interface 1090, auxiliary equipment 1084, power source 1086, power circuitry 1087, and antenna 1062. Although network node 1060 illustrated in the example wireless network of FIG. 10 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 1060 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 1080 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 1060 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 1060 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 1060 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 1080 for the different RATs) and some components may be reused (e.g., the same antenna 1062 may be shared by the RATs). Network node 1060 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1060, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1060.

Processing circuitry 1070 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 1070 may include processing information obtained by processing circuitry 1070 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry 1070 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1060 components, such as device readable medium 1080, network node 1060 functionality. For example, processing circuitry 1070 may execute instructions stored in device readable medium 1080 or in memory within processing circuitry 1070. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 1070 may include a system on a chip (SOC).

In some embodiments, processing circuitry 1070 may include one or more of radio frequency (RF) transceiver circuitry 1072 and baseband processing circuitry 1074. In some embodiments, radio frequency (RF) transceiver circuitry 1072 and baseband processing circuitry 1074 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1072 and baseband processing circuitry 1074 may be on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 1070 executing instructions stored on device readable medium 1080 or memory within processing circuitry 1070. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 1070 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 1070 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1070 alone or to other components of network node 1060, but are enjoyed by network node 1060 as a whole, and/or by end users and the wireless network generally.

Device readable medium 1080 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 1070. Device readable medium 1080 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1070 and, utilized by network node 1060. Device readable medium 1080 may be used to store any calculations made by processing circuitry 1070 and/or any data received via interface 1090. In some embodiments, processing circuitry 1070 and device readable medium 1080 may be considered to be integrated.

Interface 1090 is used in the wired or wireless communication of signalling and/or data between network node 1060, network 1006, and/or WDs 1010. As illustrated, interface 1090 comprises port(s)/terminal(s) 1094 to send and receive data, for example to and from network 1006 over a wired connection. Interface 1090 also includes radio front end circuitry 1092 that may be coupled to, or in certain embodiments a part of, antenna 1062. Radio front end circuitry 1092 comprises filters 1098 and amplifiers 1096. Radio front end circuitry 1092 may be connected to antenna 1062 and processing circuitry 1070. Radio front end circuitry may be configured to condition signals communicated between antenna 1062 and processing circuitry 1070. Radio front end circuitry 1092 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1092 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1098 and/or amplifiers 1096. The radio signal may then be transmitted via antenna 1062. Similarly, when receiving data, antenna 1062 may collect radio signals which are then converted into digital data by radio front end circuitry 1092. The digital data may be passed to processing circuitry 1070. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 1060 may not include separate radio front end circuitry 1092, instead, processing circuitry 1070 may comprise radio front end circuitry and may be connected to antenna 1062 without separate radio front end circuitry 1092. Similarly, in some embodiments, all or some of RF transceiver circuitry 1072 may be considered a part of interface 1090. In still other embodiments, interface 1090 may include one or more ports or terminals 1094, radio front end circuitry 1092, and RF transceiver circuitry 1072, as part of a radio unit (not shown), and interface 1090 may communicate with baseband processing circuitry 1074, which is part of a digital unit (not shown).

Antenna 1062 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 1062 may be coupled to radio front end circuitry 1090 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 1062 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 1062 may be separate from network node 1060 and may be connectable to network node 1060 through an interface or port.

Antenna 1062, interface 1090, and/or processing circuitry 1070 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 1062, interface 1090, and/or processing circuitry 1070 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry 1087 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 1060 with power for performing the functionality described herein. Power circuitry 1087 may receive power from power source 1086. Power source 1086 and/or power circuitry 1087 may be configured to provide power to the various components of network node 1060 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1086 may either be included in, or external to, power circuitry 1087 and/or network node 1060. For example, network node 1060 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 1087. As a further example, power source 1086 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 1087. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node 1060 may include additional components beyond those shown in FIG. 10 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 1060 may include user interface equipment to allow input of information into network node 1060 and to allow output of information from network node 1060. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1060.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE). a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g., refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 1010 includes antenna 1011, interface 1014, processing circuitry 1020, device readable medium 1030, user interface equipment 1032, auxiliary equipment 1034, power source 1036 and power circuitry 1037. WD 1010 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 1010, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 1010.

Antenna 1011 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 1014. In certain alternative embodiments, antenna 1011 may be separate from WD 1010 and be connectable to WD 1010 through an interface or port. Antenna 1011, interface 1014, and/or processing circuitry 1020 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 1011 may be considered an interface.

As illustrated, interface 1014 comprises radio front end circuitry 1012 and antenna 1011. Radio front end circuitry 1012 comprise one or more filters 1018 and amplifiers 1016. Radio front end circuitry 1014 is connected to antenna 1011 and processing circuitry 1020, and is configured to condition signals communicated between antenna 1011 and processing circuitry 1020. Radio front end circuitry 1012 may be coupled to or a part of antenna 1011. In some embodiments, WD 1010 may not include separate radio front end circuitry 1012; rather, processing circuitry 1020 may comprise radio front end circuitry and may be connected to antenna 1011. Similarly, in some embodiments, some or all of RF transceiver circuitry 1022 may be considered a part of interface 1014. Radio front end circuitry 1012 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1012 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1018 and/or amplifiers 1016. The radio signal may then be transmitted via antenna 1011. Similarly, when receiving data, antenna 1011 may collect radio signals which are then converted into digital data by radio front end circuitry 1012. The digital data may be passed to processing circuitry 1020. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry 1020 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 1010 components, such as device readable medium 1030, WD 1010 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 1020 may execute instructions stored in device readable medium 1030 or in memory within processing circuitry 1020 to provide the functionality disclosed herein.

As illustrated, processing circuitry 1020 includes one or more of RF transceiver circuitry 1022, baseband processing circuitry 1024, and application processing circuitry 1026. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 1020 of WD 1010 may comprise a SOC. In some embodiments, RF transceiver circuitry 1022, baseband processing circuitry 1024, and application processing circuitry 1026 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 1024 and application processing circuitry 1026 may be combined into one chip or set of chips, and RF transceiver circuitry 1022 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 1022 and baseband processing circuitry 1024 may be on the same chip or set of chips, and application processing circuitry 1026 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 1022, baseband processing circuitry 1024, and application processing circuitry 1026 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 1022 may be a part of interface 1014. RF transceiver circuitry 1022 may condition RF signals for processing circuitry 1020.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 1020 executing instructions stored on device readable medium 1030, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 1020 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 1020 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1020 alone or to other components of WD 1010, but are enjoyed by WD 1010 as a whole, and/or by end users and the wireless network generally.

Processing circuitry 1020 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 1020, may include processing information obtained by processing circuitry 1020 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 1010, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium 1030 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1020. Device readable medium 1030 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 1020. In some embodiments, processing circuitry 1020 and device readable medium 1030 may be considered to be integrated. User interface equipment 1032 may provide components that allow for a human user to interact with WD 1010. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 1032 may be operable to produce output to the user and to allow the user to provide input to WD 1010. The type of interaction may vary depending on the type of user interface equipment 1032 installed in WD 1010. For example, if WD 1010 is a smart phone, the interaction may be via a touch screen; if WD 1010 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 1032 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 1032 is configured to allow input of information into WD 1010, and is connected to processing circuitry 1020 to allow processing circuitry 1020 to process the input information. User interface equipment 1032 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 1032 is also configured to allow output of information from WD 1010, and to allow processing circuitry 1020 to output information from WD 1010. User interface equipment 1032 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 1032, WD 1010 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment 1034 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 1034 may vary depending on the embodiment and/or scenario.

Power source 1036 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 1010 may further comprise power circuitry 1037 for delivering power from power source 1036 to the various parts of WD 1010 which need power from power source 1036 to carry out any functionality described or indicated herein. Power circuitry 1037 may in certain embodiments comprise power management circuitry. Power circuitry 1037 may additionally or alternatively be operable to receive power from an external power source; in which case WD 1010 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 1037 may also in certain embodiments be operable to deliver power from an external power source to power source 1036. This may be, for example, for the charging of power source 1036. Power circuitry 1037 may perform any formatting, converting, or other modification to the power from power source 1036 to make the power suitable for the respective components of WD 1010 to which power is supplied.

FIG. 11: User Equipment in accordance with some embodiments

FIG. 11 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 11200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 1100, as illustrated in FIG. 11, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although FIG. 11 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In FIG. 11, UE 1100 includes processing circuitry 1101 that is operatively coupled to input/output interface 1105, radio frequency (RF) interface 1109, network connection interface 1111, memory 1115 including random access memory (RAM) 1117, read-only memory (ROM) 1119, and storage medium 1121 or the like, communication subsystem 1131, power source 1133, and/or any other component, or any combination thereof. Storage medium 1121 includes operating system 1123, application program 1125, and data 1127. In other embodiments, storage medium 1121 may include other similar types of information. Certain UEs may utilize all of the components shown in FIG. 11, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

In FIG. 11, processing circuitry 1101 may be configured to process computer instructions and data. Processing circuitry 1101 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1101 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface 1105 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 1100 may be configured to use an output device via input/output interface 1105. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 1100. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 1100 may be configured to use an input device via input/output interface 1105 to allow a user to capture information into UE 1100. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, or an optical sensor.

In FIG. 11, RF interface 1109 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 1111 may be configured to provide a communication interface to network 1143a. Network 1143a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 1143a may comprise a Wi-Fi network. Network connection interface 1111 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 1111 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM 1117 may be configured to interface via bus 1102 to processing circuitry 1101 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 1119 may be configured to provide computer instructions or data to processing circuitry 1101. For example, ROM 1119 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 1121 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 1121 may be configured to include operating system 1123, application program 1125 such as a web browser application, a widget or gadget engine or another application, and data file 1127. Storage medium 1121 may store, for use by UE 1100, any of a variety of various operating systems or combinations of operating systems.

Storage medium 1121 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 1121 may allow UE 1100 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 1121, which may comprise a device readable medium.

In FIG. 11, processing circuitry 1101 may be configured to communicate with network 1143b using communication subsystem 1131. Network 1143a and network 1143b may be the same network or networks or different network or networks. Communication subsystem 1131 may be configured to include one or more transceivers used to communicate with network 1143b. For example, communication subsystem 1131 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 1133 and/or receiver 1135 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 1133 and receiver 1135 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem 1131 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 1131 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 1143b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 1143b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 1113 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 1100.

The features, benefits and/or functions described herein may be implemented in one of the components of UE 1100 or partitioned across multiple components of UE 1100. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 1131 may be configured to include any of the components described herein. Further, processing circuitry 1101 may be configured to communicate with any of such components over bus 1102. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 1101 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 1101 and communication subsystem 1131. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

FIG. 12: Virtualization environment in accordance with some embodiments

FIG. 12 is a schematic block diagram illustrating a virtualization environment 1200 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1200 hosted by one or more of hardware nodes 1230. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications 1220 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 1220 are run in virtualization environment 1200 which provides hardware 1230 comprising processing circuitry 1260 and memory 1290. Memory 1290 contains instructions 1295 executable by processing circuitry 1260 whereby application 1220 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment 1200, comprises general-purpose or special-purpose network hardware devices 1230 comprising a set of one or more processors or processing circuitry 1260, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 1290-1 which may be non-persistent memory for temporarily storing instructions 1295 or software executed by processing circuitry 1260. Each hardware device may comprise one or more network interface controllers (NICs) 1270, also known as network interface cards, which include physical network interface 1280. Each hardware device may also include non-transitory, persistent, machine-readable storage media 1290-2 having stored therein software 1295 and/or instructions executable by processing circuitry 1260. Software 1295 may include any type of software including software for instantiating one or more virtualization layers 1250 (also referred to as hypervisors), software to execute virtual machines 1240 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines 1240 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1250 or hypervisor. Different embodiments of the instance of virtual appliance 1220 may be implemented on one or more of virtual machines 1240, and the implementations may be made in different ways.

During operation, processing circuitry 1260 executes software 1295 to instantiate the hypervisor or virtualization layer 1250, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 1250 may present a virtual operating platform that appears like networking hardware to virtual machine 1240.

As shown in FIG. 12, hardware 1230 may be a standalone network node with generic or specific components. Hardware 1230 may comprise antenna 12225 and may implement some functions via virtualization. Alternatively, hardware 1230 may be part of a larger cluster of hardware (e.g., such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 12100, which, among others, oversees lifecycle management of applications 1220.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine 1240 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 1240, and that part of hardware 1230 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 1240, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 1240 on top of hardware networking infrastructure 1230 and corresponds to application 1220 in FIG. 12.

In some embodiments, one or more radio units 12200 that each include one or more transmitters 12220 and one or more receivers 12210 may be coupled to one or more antennas 12225. Radio units 12200 may communicate directly with hardware nodes 1230 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use of control system 12230 which may alternatively be used for communication between the hardware nodes 1230 and radio units 12200.

FIG. 13: Telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.

With reference to FIG. 13, in accordance with an embodiment, a communication system includes telecommunication network 1310, such as a 3GPP-type cellular network, which comprises access network 1311, such as a radio access network, and core network 1314. Access network 1311 comprises a plurality of base stations 1312a, 1312b, 1312c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1313a, 1313b, 1313c. Each base station 1312a, 1312b, 1312c is connectable to core network 1314 over a wired or wireless connection 1315. A first UE 1391 located in coverage area 1313c is configured to wirelessly connect to, or be paged by, the corresponding base station 1312c. A second UE 1392 in coverage area 1313a is wirelessly connectable to the corresponding base station 1312a. While a plurality of UEs 1391, 1392 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 1312.

Telecommunication network 1310 is itself connected to host computer 1330, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 1330 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 1321 and 1322 between telecommunication network 1310 and host computer 1330 may extend directly from core network 1314 to host computer 1330 or may go via an optional intermediate network 1320. Intermediate network 1320 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1320, if any, may be a backbone network or the Internet; in particular, intermediate network 1320 may comprise two or more sub-networks (not shown).

The communication system of FIG. 13 as a whole enables connectivity between the connected UEs 1391, 1392 and host computer 1330. The connectivity may be described as an over-the-top (OTT) connection 1350. Host computer 1330 and the connected UEs 1391, 1392 are configured to communicate data and/or signaling via OTT connection 1350, using access network 1311, core network 1314, any intermediate network 1320 and possible further infrastructure (not shown) as intermediaries. OTT connection 1350 may be transparent in the sense that the participating communication devices through which OTT connection 1350 passes are unaware of routing of uplink and downlink communications. For example, base station 1312 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 1330 to be forwarded (e.g., handed over) to a connected UE 1391. Similarly, base station 1312 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1391 towards the host computer 1330.

FIG. 14: Host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIG. 14. In communication system 1400, host computer 1410 comprises hardware 1415 including communication interface 1416 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1400. Host computer 1410 further comprises processing circuitry 1418, which may have storage and/or processing capabilities. In particular, processing circuitry 1418 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 1410 further comprises software 1411, which is stored in or accessible by host computer 1410 and executable by processing circuitry 1418. Software 1411 includes host application 1412. Host application 1412 may be operable to provide a service to a remote user, such as UE 1430 connecting via OTT connection 1450 terminating at UE 1430 and host computer 1410. In providing the service to the remote user, host application 1412 may provide user data which is transmitted using OTT connection 1450.

Communication system 1400 further includes base station 1420 provided in a telecommunication system and comprising hardware 1425 enabling it to communicate with host computer 1410 and with UE 1430. Hardware 1425 may include communication interface 1426 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1400, as well as radio interface 1427 for setting up and maintaining at least wireless connection 1470 with UE 1430 located in a coverage area (not shown in FIG. 14) served by base station 1420. Communication interface 1426 may be configured to facilitate connection 1460 to host computer 1410. Connection 1460 may be direct or it may pass through a core network (not shown in FIG. 14) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 1425 of base station 1420 further includes processing circuitry 1428, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 1420 further has software 1421 stored internally or accessible via an external connection.

Communication system 1400 further includes UE 1430 already referred to. Its hardware 1435 may include radio interface 1437 configured to set up and maintain wireless connection 1470 with a base station serving a coverage area in which UE 1430 is currently located. Hardware 1435 of UE 1430 further includes processing circuitry 1438, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 1430 further comprises software 1431, which is stored in or accessible by UE 1430 and executable by processing circuitry 1438. Software 1431 includes client application 1432. Client application 1432 may be operable to provide a service to a human or non-human user via UE 1430, with the support of host computer 1410. In host computer 1410, an executing host application 1412 may communicate with the executing client application 1432 via OTT connection 1450 terminating at UE 1430 and host computer 1410. In providing the service to the user, client application 1432 may receive request data from host application 1412 and provide user data in response to the request data. OTT connection 1450 may transfer both the request data and the user data. Client application 1432 may interact with the user to generate the user data that it provides.

It is noted that host computer 1410, base station 1420 and UE 1430 illustrated in FIG. 14 may be similar or identical to host computer 1330, one of base stations 1312a, 1312b, 1312c and one of UEs 1391, 1392 of FIG. 13, respectively. This is to say, the inner workings of these entities may be as shown in FIG. 14 and independently, the surrounding network topology may be that of FIG. 13.

In FIG. 14, OTT connection 1450 has been drawn abstractly to illustrate the communication between host computer 1410 and UE 1430 via base station 1420, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 1430 or from the service provider operating host computer 1410, or both. While OTT connection 1450 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection 1470 between UE 1430 and base station 1420 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments may improve the performance of OTT services provided to UE 1430 using OTT connection 1450, in which wireless connection 1470 forms the last segment. More precisely, the teachings of these embodiments may improve the deblock filtering for video processing and thereby provide benefits such as improved video encoding and/or decoding.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 1450 between host computer 1410 and UE 1430, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 1450 may be implemented in software 1411 and hardware 1415 of host computer 1410 or in software 1431 and hardware 1435 of UE 1430, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 1450 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 1411, 1431 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 1450 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 1420, and it may be unknown or imperceptible to base station 1420. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 1410′s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 1411 and 1431 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 1450 while it monitors propagation times, errors etc.

FIG. 15: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

FIG. 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 13 and 14. For simplicity of the present disclosure, only drawing references to FIG. 15 will be included in this section. In step 1510, the host computer provides user data. In substep 1511 (which may be optional) of step 1510, the host computer provides the user data by executing a host application. In step 1520, the host computer initiates a transmission carrying the user data to the UE. In step 1530 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1540 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIG. 16: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

FIG. 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 13 and 14. For simplicity of the present disclosure, only drawing references to FIG. 16 will be included in this section. In step 1610 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 1620, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1630 (which may be optional), the UE receives the user data carried in the transmission.

FIG. 17: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

FIG. 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 13 and 14. For simplicity of the present disclosure, only drawing references to FIG. 17 will be included in this section. In step 1710 (which may be optional), the UE receives input data provided by the host computer. Additionally, or alternatively, in step 1720, the UE provides user data. In substep 1721 (which may be optional) of step 1720, the UE provides the user data by executing a client application. In substep 1711 (which may be optional) of step 1710, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 1730 (which may be optional), transmission of the user data to the host computer. In step 1740 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

FIG. 18: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

FIG. 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 13 and 14. For simplicity of the present disclosure, only drawing references to FIG. 18 will be included in this section. In step 1810 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 1820 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1830 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

In the specification, there have been disclosed embodiments of the invention and, although specific terms are employed, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

1. A method in a first wireless device having a plurality of protocol layers including a media access control, MAC, layer and a physical, PHY, layer, the method comprising:

at the MAC layer, selecting a plurality of carriers for carrier aggregation, each of the carriers being associated to a respective hybrid automatic repeat request, HARQ, entity; and

at the MAC layer, initiating a carrier reselection process by the first wireless device if there is no configured sidelink grant on any carrier of the plurality of carriers.

2. The method of claim 1, wherein each respective HARQ entity is different from a HARQ entity of each other carrier of the plurality of carriers.

3. The method of claim 1, further comprising:

at the MAC layer, initiating a sidelink carrier reselection process by the first wireless device in response to a triggering event, the triggering event comprising at least one of: there is no configured sidelink grant in any sidelink carrier; a configured sidelink grant cannot accommodate a radio link control, RLC, service data unit, SDU, by using a maximum allowed modulation and coding scheme, MCS, configured by upper layers for any sidelink carrier with configured SL grant and the MAC entity selects not to segment the RLC SDU; and transmission(s) with a configured sidelink grant cannot fulfil a latency requirement of data in a sidelink logical channel for any sidelink carrier with a configured sidelink grant, and the MAC selects not to perform transmission(s) corresponding to a single MAC protocol data unit, PDU.

4. The method of claim 3, wherein initiating the sidelink carrier reselection process is performed only for the carrier and associated HARQ event associated with the triggering event;

wherein the triggering event comprises at least one of: for a specific carrier/HARQ entity, if an SL_RESOURCE_RESELECTION_COUNTER = 0 and, when the SL_RESOURCE_RESELECTION_COUNTER was equal to 1, the MAC randomly selected, with equal probability, a value in an interval [0, 1] which is above a probability configured by upper layers; neither transmission nor retransmission has been performed by MAC on any resource indicated in a configured sidelink grant during a previous second for a specific carrier/HARQ entity; sl-ReselectAfter is configured and a number of consecutive unused transmission opportunities on resources indicated in the configured sidelink grant is equal to sl-ReselectAfter, for a specific carrier/HARQ entity; and/or a pool of resources is configured or reconfigured by upper layers for a specific carrier.

5. The method of claim 3, wherein initiating the sidelink carrier reselection process is performed for all sidelink carriers configured for sidelink operations;

wherein the triggering event comprises at least one of: UE capability and/or power limitations are experienced by potential simultaneous transmissions in multiple carriers; and/or transmissions with a configured sidelink grant are such that the UE is unable to listen/sense the carriers for a long time due to half duplex limitation.

6. The method of claim 3, further comprising:

after initiating the sidelink carrier reselection process, performing at least one of: continuing to use a previous carrier and performing resource reselection on the previous carrier; selecting a second sidelink carrier and configuring a second sidelink grant on the second sidelink carrier; and ceasing to use the sidelink carrier and not selecting any other sidelink carrier.

7. The method of claim 1 wherein the first wireless device comprises a vehicle-mounted wireless device.

8. A first wireless device comprising:

a transceiver configured to provide wireless network communication with a wireless communication network using a plurality of protocol layers including a media access control, MAC, layer; and

a processor coupled with the transceiver, wherein the processor is configured to provide wireless network communication through the transceiver, and wherein the processor is configured to perform operations comprising: at the MAC layer, selecting a plurality of carriers for carrier aggregation, each of the carriers being associated to a respective hybrid automatic repeat request, HARQ, entity; and at the MAC layer, initiating a carrier reselection process if there is no configured sidelink grant in any carrier of the plurality of carriers.

9. The first wireless device of claim 8, wherein each respective HARQ entity is different from a HARQ entity of each other carrier of the plurality of carriers.

10. The first wireless device of claim 8, wherein the processor is configured to perform operations further comprising:

at the MAC layer, initiating a sidelink carrier reselection process by the first wireless device in response to a triggering event, the triggering event comprising at least one of: there is no configured sidelink grant in any sidelink carrier; a configured sidelink grant cannot accommodate a radio link control, RLC, service data unit, SDU, by using a maximum allowed modulation and coding scheme, MCS, configured by upper layers for any sidelink carrier with configured SL grant and the MAC entity selects not to segment the RLC SDU; and transmission(s) with a configured sidelink grant cannot fulfil a latency requirement of data in a sidelink logical channel for any sidelink carrier with a configured sidelink grant, and the MAC selects not to perform transmission(s) corresponding to a single MAC protocol data unit, PDU.

11. The first wireless device of claim 10, wherein initiating the sidelink carrier reselection process is performed only for the carrier and associated HARQ event associated with the triggering event;

wherein the triggering event comprises at least one of: for a specific carrier/HARQ entity, if an SL_RESOURCE_RESELECTION_COUNTER = 0 and, when the SL_RESOURCE_RESELECTION_COUNTER was equal to 1, the MAC randomly selected, with equal probability, a value in an interval [0, 1] which is above a probability configured by upper layers; neither transmission nor retransmission has been performed by MAC on any resource indicated in a configured sidelink grant during a previous second for a specific carrier/HARQ entity; sl-ReselectAfter is configured and a number of consecutive unused transmission opportunities on resources indicated in the configured sidelink grant is equal to sl-ReselectAfter, for a specific carrier/HARQ entity; and/or a pool of resources is configured or reconfigured by upper layers for a specific carrier.

12. The first wireless device of claim 10, wherein initiating the sidelink carrier reselection process is performed for all sidelink carriers configured for sidelink operations;

wherein the triggering event comprises at least one of: UE capability and/or power limitations are experienced by potential simultaneous transmissions in multiple carriers; and/or transmissions with a configured sidelink grant are such that the UE is unable to listen/sense the carriers for a long time due to half duplex limitation.

13. The first wireless device of claim 10, further comprising:

after initiating the sidelink carrier reselection process, performing at least one of: continuing to use a previous carrier and performing resource reselection on the previous carrier; selecting a second sidelink carrier and configuring a second sidelink grant on the second sidelink carrier; and ceasing to use the sidelink carrier and not selecting any other sidelink carrier.

14. The first wireless device of claim 8 wherein the first wireless device is a vehicle mounted wireless device.

15. A non-transitory storage medium including program code to be executed by processing circuitry of a first wireless device configured to operate in a communication network, whereby execution of the program code causes the first wireless device to perform operations comprising:

at the MAC layer, selecting a plurality of carriers for carrier aggregation, each of the carriers being associated to a respective hybrid automatic repeat request, HARQ, entity; and

at the MAC layer, initiating a carrier reselection process by the first wireless device if there is no configured sidelink grant on any carrier of the plurality of carriers.

16. The non-transitory storage medium of claim 15, including further program code to be executed by processing circuitry whereby execution of the further program code causes the first wireless device to perform operations comprising wherein in selecting the plurality of carriers, each respective HARQ entity is different from a HARQ entity of each other carrier of the plurality of carriers.

17. The non-transitory storage medium of claim 15, wherein the non-transitory storage medium includes further program code to be executed by processing circuitry whereby execution of the further program code causes the first wireless device to perform operations further comprising:

at the MAC layer, initiating a sidelink carrier reselection process by the first wireless device in response to a triggering event, the triggering event comprising at least one of: there is no configured sidelink grant in any sidelink carrier; a configured sidelink grant cannot accommodate a radio link control, RLC, service data unit, SDU, by using a maximum allowed modulation and coding scheme, MCS, configured by upper layers for any sidelink carrier with configured SL grant and the MAC entity selects not to segment the RLC SDU; and transmission(s) with a configured sidelink grant cannot fulfil a latency requirement of data in a sidelink logical channel for any sidelink carrier with a configured sidelink grant, and the MAC selects not to perform transmission(s) corresponding to a single MAC protocol data unit, PDU.

18. The non-transitory storage medium of claim 15, wherein the non-transitory storage medium includes further program code to be executed by processing circuitry whereby execution of the further program code causes the first wireless device to perform operations further comprising: wherein initiating the sidelink carrier reselection process is performed only for the carrier and associated HARQ event associated with the triggering event;

wherein the triggering event comprises at least one of: for a specific carrier/HARQ entity, if an SL_RESOURCE_RESELECTION_COUNTER = 0 and, when the SL_RESOURCE_RESELECTION_COUNTER was equal to 1, the MAC randomly selected, with equal probability, a value in an interval [0, 1] which is above a probability configured by upper layers; neither transmission nor retransmission has been performed by MAC on any resource indicated in a configured sidelink grant during a previous second for a specific carrier/HARQ entity; sl-ReselectAfter is configured and a number of consecutive unused transmission opportunities on resources indicated in the configured sidelink grant is equal to sl-ReselectAfter, for a specific carrier/HARQ entity; and/or a pool of resources is configured or reconfigured by upper layers for a specific carrier.

19. The non-transitory storage medium of claim 15, wherein the non-transitory storage medium includes further program code to be executed by processing circuitry whereby execution of the further program code causes the first wireless device to perform operations further comprising: wherein initiating the sidelink carrier reselection process is performed for all sidelink carriers configured for sidelink operations;

wherein the triggering event comprises at least one of: UE capability and/or power limitations are experienced by potential simultaneous transmissions in multiple carriers; and/or transmissions with a configured sidelink grant are such that the UE is unable to listen/sense the carriers for a long time due to half duplex limitation.

20. The non-transitory storage medium of claim 15, wherein the non-transitory storage medium includes further program code to be executed by processing circuitry whereby execution of the further program code causes the first wireless device to perform operations further comprising:

after initiating the sidelink carrier reselection process, performing at least one of: continuing to use a previous carrier and performing resource reselection on the previous carrier; selecting a second sidelink carrier and configuring a second sidelink grant on the second sidelink carrier; and ceasing to use the sidelink carrier and not selecting any other sidelink carrier.