APPARATUSES AND METHODS FOR DUAL CONNECTIVITY

TECHNICAL FIELD

The present disclosure generally relates to telecommunications. In particular, the various embodiments described in this disclosure relates to apparatuses and methods for handling dual connectivity.

BACKGROUND

This section is intended to provide a background to the various embodiments of the invention that are described in this disclosure. Therefore, unless otherwise indicated herein, what is described in this section should not be interpreted to be prior art by its mere inclusion in this section.

International Mobile station Equipment Identity and Software Version number (IMEISV) is a number, usually unique, to identify 3rd Generation Partnership Project (3GPP) and integrated Digital Enhanced Network (iDEN) User Equipment (UEs), as well as some satellite UEs. As illustrated in Figure 1, the IMEISV consists of an International Mobile station Equipment Identity (IMEI) and a Software Version Number (SVR). The IMEISV consists of 16 decimal digits, i.e. 64 bits, wherein 14 digits represent the IMEI and two digits represent the SVN. The IMEI consist of a Type Allocation Code (TAC) and a Serial NumbeR (SNR). The TAC consists of 8 digits and the SNR consists of 6 digits.

A masked IMEISV is an information element that contains the IMEISV value with a mask to identify a terminal model without identifying an individual mobile equipment, or a UE. Typically, it is the SNR that is masked in order to keep the individual mobile equipment secret. The last 4 digits of the SNR is masked by setting the corresponding bits to 1. By using the masked IMEISV, it may be possible to apply different functionality on UEs depending on model type. It may be possible to restrict or enable usage of specific features for certain UE models only. For example, it may be possible to block certain features for certain UE models when they exhibit faulty or non-standard compliant behavior. Additionally, the masked IMEISV may also be used for RAN diagnostics, where the observability of behavior of different UE models can be tracked. The concept of Dual Connectivity (DC) was introduced in Long Term Evolution (LTE) to allow a UE to simultaneously transmit and receive data on multiple component carriers from two cell groups via a Master eNB (MeNB) and a Secondary eNB (SeNB). The UE may communicate simultaneously with both the MeNB and the SeNB, which allows the communication system to increase the total bandwidth of communications to and from the UE. The general procedure to set up DC in LTE is illustrated in Figure 2.

The IMEISV is given to the Radio Access Network (RAN) by the Mobility Management Entity (MME). Figures 3a, 3b and 3c illustrates how the RAN may receive the masked IMEISV. Figure 3a shows that the masked IMEISV can be received from the MME during initial connection establishment and Figure 3b shows that the masked IMEISV can be received during incoming SI handover via the MME. Figure 3c illustrates that the masked IMEISV can be received by incoming X2 handover from a source eNB to a target eNB. The masked IMEISV may then be stored in UE context and may feature differentiated UE handling. The masked IMEISV is transferred to the eNBs such that there can be uniform UE handling across the RAN network.

Figure 4 is a flowchart that illustrates how the differentiated UE handling generally may be performed. By using the masked IMEISV, it is possible to turn off, or on, a feature X for a given UE. As seen is the flowchart, it is first decided whether a feature X is operable, at step 1100. If not, feature X is turned off, at step 1600. However, if feature X is operable, it is decided, at step 1200, whether differentiated UE handling is operable. If differentiated UE handling is not operable, the feature X is turned on 1500, while if differentiated UE handling is operable, it has to be determined whether IMEISV for the UE is received 1300. If IMEISV is not received, feature X is turned on, while if IMEISV is received, it is determined 1400 whether feature X is configured as off for the UE’s IMEISV. If feature X is configured as off, it is turned off 1600, otherwise feature X is turned on. Feature X can, for example, relate to Coverage-Triggered Wideband Code Division Multiple Access (WCDMA) Inter Radio Access Technology (IRAT) Handover; Single Radio Voice Call Continuity (SRVCC) to Universal Terrestrial Radio Access Network (UTRAN), SRVCC to Global System for Mobile communications (GSM) EDGE Radio Access Network (GERAN), Transmission Time Interval (TTI) bundling, carrier aggregation and basic intelligent connectivity. SUMMARY

It is in view of the above background and other considerations that the various embodiments of the present disclosure have been made.

Traditionally, a UE is connected to one Radio Access Technology (RAT) at a time, i.e. either connected to Global System for Mobile communications (GSM), or to Universal Mobile Telecommunications System (UMTS) or to Long Term Evolution (LTE). With the introduction of 5G, this changes. Due to, inter alia, the higher frequencies bands used it was deemed better to enable UEs to connect to LTE and New Radio (NR) simultaneously. This is referred to as Dual Connectivity EN-DC. EN-DC stands for E- UTRAN (i.e. Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access) New Radio - Dual Connectivity. With the NR rollouts beginning, NR is used side-by-side with LTE, i.e. Non-Stand-Alone (NSA). An example of such wireless communication system is illustrated in Figure 5. The gNodeB (gNB) is connected to the eNodeB (eNB) via EN-DC X2. The eNB is the master node that carries the control plane and the gNB is the secondary node which carries the user plane part only. The eNB controls the gNB addition and release for a call. One eNB may connect to multiple gNBs and one gNB may be connected to multiple eNBs. The eNB may provide the Master Cell Group (MCG) and the gNB may provide the Secondary Cell Group (SCG). In EN-DC, the process to allocate radio resources for a specific E-UTRAN Radio Access Bearer (E-RAB) is similar to the process in LTE. This process to allocate radio resources is illustrated in Figure 6.

The previously described differentiated UE handling is generally used in LTE today. The described methods of sharing the masked IMEISV are enabled because there is only one type of capability container to interpret and the functionality can be implemented in the MeNB. However, NR introduces a different numerology between the gNBs, which means a difference in the capabilities that can go on either side. The eNB cannot read and understand the capabilities in a NR container. This is why there is an EN-DC co ordination during the gNB addition where the eNB and gNB negotiate the feature and supported capabilities. In these situations, there is no possibility to provide the gNBs with the IMEISV and thus not possible to control certain features in gNBs via IMEISV for certain UE models. Hence, a common principle will be applied to all the UEs. Accordingly, there is no solution for how differentiated UE handling could be introduced together with 5G, neither for the NSA deployment nor the Stand-Alone (SA) deployment.

Wireless devices, e.g. UEs, will be offered services from a mix of eNBs and gNBs from different vendors. However, there is no flexible solution for providing Base Stations (BS) with wireless device models in order to enable differentiated wireless device handling. There is a need for a solution where operators can obtain the flexibility to block certain features for certain wireless device models, without the operators needing a first BS to have the knowledge of the second BS features to control operations such as, for example, observing a wireless device behaviour in a multi-vendor deployment scenario. Accordingly, there is a need for a solution that enables differentiated wireless device handling regardless of vendors and RAT used in the communication system.

In view of the above, it is therefore a general object of the aspects and embodiments described throughout this disclosure to provide a solution to address this problem.

This general object has been addressed by the appended independent claims. Advantageous embodiments are defined in the appended dependent claims.

It is proposed to provide a solution to address this problem by adding an identifier that identifies a wireless device model of a wireless device into a message that is transmitted from a first BS to a second BS.

According to a first aspect, there is provided a method for handling Dual Connectivity (DC) in a wireless communication system. The method is implemented in a first Base Station (BS). The wireless communication system is adapted to provide for DC between a wireless device and the first BS and between the wireless device and a second BS.

The method comprises transmitting, to the second BS, a request to allocate resources for DC operation for the wireless device. The request comprises an identifier that identifies a wireless device model of the wireless device.

In some embodiments, the identifier is a masked International Mobile station Equipment Identity and Software Version number (IMEISV) that identifies the wireless device model without identifying the individual wireless device. In some embodiments, the first BS operates a first radio connection using a first Radio Access Technology (RAT) which is different from a second RAT used by the second BS to operate a second radio connection. For example, the first BS may operate the first radio connection using Long Term Evolution (LTE), while the second BS may operate the second radio connection using New Radio (NR). The request to allocate radio resources for DC operation may be transmitted to the second BS via an X2 interface. The first BS may, for example, be a Master eNode B (MeNB) and the request to allocate radio resources for DC operation may be transmitted to the second BS, which may, for example, be a Secondary gNode B (SgNB), via an X2 SgNB Addition Request message.

In some embodiments, the first BS operates a first radio connection using same RAT as used by the second BS to operate a second radio connection. In one embodiment, the first BS operates a first radio connection using LTE. The request to allocate radio resources for DC operation is transmitted to the second BS via an X2 interface. The first BS may, for example, be an MeNB and the request to allocate radio resources for DC operation may be transmitted to the second BS, which may be a Secondary eNode B (SeNB), via an X2 SeNB Addition Request message. In another embodiment, the first BS operates a first radio connection using NR. The request to allocate radio resources for DC operation is transmitted to the second BS via an Xn interface. The first BS may, for example, be a Master gNB (MgNB) and the request to allocate radio resources for DC operation may be transmitted to the second BS, which may be a SgNB, via an Xn S- Node Addition Request message.

According to a second aspect, there is provided a method for handling DC in a wireless communication system. The method is implemented in a second BS. The wireless communication system is adapted to provide for DC between a wireless device and a first BS and between the wireless device and the second BS.

The method comprises receiving, from the first BS, a request to allocate radio resources for DC operation for the wireless device. The request comprises an identifier that identifies a wireless device model of the wireless device.

In some embodiments, the identifier is a masked IMEISV that identifies the wireless device model without identifying the individual wireless device. In one embodiment, the method further comprises performing, based on the received identifier, differentiated control on the wireless device. The differentiated control may, for example, be implemented on the wireless device during at least one of scheduling, state control and power distribution.

In some embodiments, the second BS operates a second radio connection using a second RAT, which is different from a first RAT used by the first BS, to operate a first radio connection. For example, the second BS may operate the second radio connection using NR, while the first BS may operate the first radio connection using LTE. The request to allocate radio resources for DC operation for the wireless device may be received from the first BS via an X2 interface. The second BS may, for example, be a SgNB and the request to allocate radio resources for DC operation may be received from the first BS, which may, for example, be an MeNB, via an X2 SeNB Addition Request message.

In some embodiments, the second BS operates a second radio connection using same RAT as used by the first BS to operate a first radio connection. In one embodiment, the second BS operates a second radio connection using LTE. The request to allocate radio resources for DC operation is received from the first BS via an X2 interface. The second BS may, for example, be a SeNB and the request to allocate radio resources for DC operation may be received from the first BS, which may be an MeNB, via an X2 SeNB Addition Request message. In another embodiment, the second BS operates a second radio connection using NR. The request to allocate radio resources for DC operation is received from the first BS via an Xn interface. The second BS may, for example, be a SgNB and the request to allocate radio resources for DC operation may be received from the first BS, which may be an MgNB, via an Xn S-Node Addition Request message.

According to a third aspect, there is provided a first BS configured to perform the method according to the first aspect.

The first BS is configured for handling DC in a wireless communication system. The wireless communication system is adapted to provide for DC between a wireless device and the first BS and between the wireless device and a second BS. The first BS comprises a processing circuitry and a memory circuitry. The memory circuit stores computer program code which, when run in the processing circuitry, causes the first BS to transmit, to the second BS, a request to allocate resources for DC operation for the wireless device. The request comprises an identifier that identifies a wireless device model of the wireless device.

In one embodiment, the identifier is a masked IMEISV that identifies the wireless device model without identifying the individual wireless device.

In some embodiments, the first BS is configured to operate a first radio connection using a first RAT, which is different from a second RAT used by the second BS to operate a second radio connection. The wireless device is operable to communicate over the first and the second radio connection. For example, the first BS may be configured to operate the first radio connection using LTE, while the second BS may operate the second radio connection using NR. The first BS may be configured to transmit the request to allocate radio resources for DC operation to the second BS via an X2 interface. The first BS may, for example, be an MeNB and the request to allocate radio resources for DC operation may be transmitted to the second BS, which may, for example, be a SgNB, via an X2 SeNB Addition Request message

In some embodiments, the first BS is configured to operate a first radio connection using same RAT as used by the second BS to operate a second radio connection. In one embodiment, the first BS is configured to operate the first radio connection using LTE, and the first BS is configured to transmit the request to allocate radio resources for DC operation to the second BS via an X2 interface. The first BS may, for example, be an MeNB and the request to allocate radio resources for DC operation may be transmitted to the second BS, which may be a SeNB, via an X2 SeNB Addition Request message. In another embodiment, the first BS is configured to operate the first radio connection using NR and the first BS is configured to transmit the request to allocate radio resources for DC operation to the second BS via an Xn interface. The first BS may, for example, be an MgNB and the request to allocate radio resources for DC operation may be transmitted to the second BS, which may be a SgNB, via an Xn S-Node Addition Request message.

According to a fourth aspect, there is provided a second BS configured to perform the method according to the second aspect.

The second BS is configured for handling DC in a wireless communication system. The wireless communication system is adapted to provide for DC between a wireless device and a first BS, and between the wireless device and the second BS. The second BS comprises a processing circuitry and a memory circuitry. The memory circuit stores computer program code which, when run in the processing circuitry, causes the second BS to receive, from the first BS, a request to allocate radio resources for DC operation for the wireless device. The request comprises an identifier that identifies a wireless device model of the wireless device.

In one embodiment, the identifier is a masked IMEISV that identifies the wireless device model without identifying the individual wireless device.

In one embodiment, the memory circuitry stores computer program code which, when run in the processing circuitry, further causes the second BS to perform differentiated control on the wireless device based the received identifier. The differentiated control may, for example, be implemented on the wireless device during at least one of scheduling, state control and power distribution.

In some embodiments, the second BS is configured to operate a second radio connection using a second RAT, which is different from a first RAT used by the first BS to operate a first radio connection. The wireless device is operable to communicate over the first and the second radio connection. For example, the second BS may be configured to operate the second radio connection using NR while the first BS may operate the first radio connection using LTE. The second BS may be configured to receive the request to allocate radio resources for DC operation from the first BS via an X2 interface. The second BS may, for example, be a SgNB and the request to allocate radio resources for DC operation may be received from the first BS, which may, for example, be an MeNB, via an X2 SeNB Addition Request message.

In some embodiments, the second BS is configured to operate a second radio connection using same RAT as used by the first BS to operate a first radio connection. In one embodiment, the second BS is configured to operate the second radio connection using LTE. The second BS is configured to receive the request to allocate radio resources for DC operation from the first BS via an X2 interface. The second BS may, for example, be a SeNB and the request to allocate radio resources for DC operation may be received from the first BS, which may be an MeNB, via an X2 SeNB Addition Request message. In another embodiment, the second BS is configured to operate the second radio connection using NR. The second BS is configured to receive the request to allocate radio resources for DC operation from the first BS via an Xn interface. The second BS may, for example, be a SgNB and the request to allocate radio resources for DC operation may be received from the first BS, which may be an MgNB, via an Xn S-Node Addition Request message.

According to a fifth aspect, there is provided a computer program, comprising instructions which, when executed on a processing circuitry, cause the processing circuitry to carry out the method according to the first aspect and/or the second aspect.

According to a sixth aspect, there is provided a carrier containing the computer program of the fifth aspect, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

The various proposed embodiments herein provide a solution for controlling NR feature and LTE feature availability for a specific wireless device in multi-RAT and multi vendor deployment scenario.

BRIEF FESCRIPTION OF THE DRAWINGS

These and other aspects, features and advantages will be apparent and elucidated from the following description of various embodiments, reference being made to the accompanying drawings, wherein:

Figure 1 illustrates an IMEISV;

Figure 2 illustrates a general procedure to set up DC in LTE;

Figures 3a, 3b and 3c show how flowcharts of how the RAN receives the IMEISV; Figure 4 is a flowchart of how differentiated UE handling;

Figure 5 shows an example of a wireless communication system;

Figure 6 illustrates a process of allocating radio resources;

Figure 7 illustrates a message sequence chart of a process for handling DC in a wireless communication system; Figure 8 is a flowchart of an example method performed by a first BS;

Figure 9 is a flowchart of an example method performed by a second BS;

Figure 10 shows an example implementation of a first BS;

Figure 11 shows an example implementation of a second BS; Figure 12 illustrates an example wireless network;

Figure 13 shows a user equipment according to an embodiment;

Figure 14 shows a virtualization environment according to an embodiment;

Figure 15 illustrates an example telecommunication network connected via an intermediate network to a host computer; Figure 16 shows a host computer communicating via a base station with a user equipment over a partially wireless connection according to an embodiment;

Figure 17 shows an example method implemented in a communication system including a host computer, a base station and a user equipment;

Figure 18 illustrates an example method implemented in a communication system including a host computer, a base station and a user equipment; and

Figures 19 and 20 show example methods implemented in a communication system including a host computer, a base station and a user equipment.

DETAILED DESCRIPTION

The present invention will now be described more fully hereinafter. The present invention 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 by way of example so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those persons skilled in the relevant art. Like reference numbers refer to like elements throughout the description. In one of its aspects, the disclosure presented herein concerns a method for handling Dual Connectivity (DC) in a wireless system.

With reference to the Figure 7 and 8, a first embodiment will now be described. Figure 7 illustrates a message sequence chart of a process for handling DC in a wireless communication system. Figure 8 illustrates a method 100, implemented in a first BS, for handling DC in a wireless communication system, wherein the wireless communication system being adapted to provide for DC between a wireless device and the first BS, and between the wireless device and a second BS. The wireless device may, for example, be a User Equipment (UE).

The method 100 starts at step 110 with the first BS transmitting, to the second BS, a request to allocate resources for DC operation for the wireless device. The request comprises an identifier that identifies a wireless device model of the wireless device.

The proposed method 100 uses the request to allocate resources for DC operation for the wireless device to transmit an identifier that identifies a wireless device model of the wireless device. By adding this identifier, it may be possible to provide the second BS with the wireless device model in order to enable differentiated wireless device handling. This may provide operators the flexibility to block certain features for certain wireless device models. The operators do not need a first BS to have the knowledge of the second BS features to control operations such as, for example, observing a wireless device behavior in a multi-vendor deployment scenario. Accordingly, the proposed method discloses a solution that enables differentiated wireless device handling regardless of vendors and RAT used in the communication system.

In one embodiment, the identifier may be a masked International Mobile station Equipment Identity and Software Version number (IMEISV) that identifies the wireless device model without identifying the individual wireless device.

By using a masked IMEISV, it may be possible to identify the wireless device model, without identifying the individual wireless device, with only 64 bits. Different functionality may be applied to the wireless device depending on the model type. It may be possible to restrict usage of specific features for certain wireless device models and it may be possible to enable specific features for only certain wireless device models. Furthermore, the masked IMEISV is used today by eNodeBs (eNBs) to implement differentiated wireless device handling and by using the masked IMEISV it may be possible to re-use at least parts of the existing process, as previously described and illustrated in Figure 4.

In some embodiments, the first BS may operate a first radio connection using a first Radio Access Technology (RAT), which is different from a second RAT used by the second BS to operate a second radio connection. The first BS may, for example, operate the first radio connection using Long Term Evolution (LTE), while the second BS, for example, may operate the second radio connection using New Radio (NR). The request to allocate radio resources for DC operation may then for example be transmitted to the second BS via an X2 interface. In accordance with the proposed embodiment, the first BS may be a Master eNode B (MeNB) and the request to allocate radio resources for DC operation may be transmitted to the second BS, which may be a Secondary gNode B (SgNB), via an X2 SgNB Addition Request message.

Accordingly, the proposed embodiment discloses a solution for differentiated wireless device handling in multi-RAT DC by using an identifier. The proposed embodiment provides a solution for a non-standalone 5G deployment solution with DC between E- UTRA and NR networks. Furthermore, the proposed method may use existing framework to implement a solution whereby it may be possible to block and/or allow a feature X for a wireless device based on an identifier by using an existing message, such as the an X2 SgNB Addition Request message.

In one exemplary embodiment, the identifier may be a masked IMEISV, which may be added in the X2 SgNB Addition Request message. The X2 SgNB Addition Request message is specified in section 9.1.4.1 in TS 36.423 vl 5.2.0. This message is sent by the MeNB to the SgNB to request the preparation of resources for EN-DC operation for a specific UE, or wireless device. The X2 SgNB Addition Request message would accordingly be defined as specified in Table 1.

Table 1. SGNB ADDITION REQUEST

In one embodiment, the method 100 may further comprise receiving 120 an addition request acknowledgement message. The first BS may then be informed about that the second BS has decided to accept the transmitted request.

In some embodiments, the first BS may operate a first radio connection using same RAT as used by the second BS to operate a second radio connection. In one embodiment the first BS may operate a first radio connection using LTE. The request to allocate radio resources for DC operation may be transmitted to the second BS via an X2 interface. The first BS may, for example, be an MeNB and the request to allocate radio resources for DC operation may be transmitted to the second BS, which may be a Secondary eNode B (SeNB), via an X2 SeNB Addition Request message.

In one exemplary embodiment, the identifier may be a masked IMEISV, which may be added in the X2 SeNB Addition Request message. The X2 SeNB Addition Request message is specified in section 9.1.3.1 in TS 36.423 vl5.2.0. This message is sent by the MeNB to the SeNB to request the preparation of resources for DC operation for a specific UE, or wireless device. The X2 SeNB Addition Request message would accordingly be defined as specified in Table 2.

Table 2. SENB ADDITION REQUEST

In another embodiment, the first BS may operate a first radio connection using NR. The request to allocate radio resources for DC operation may be transmitted to the second BS via an Xn interface. The first BS may, for example, be a Master gNB (MgNB) and the request to allocate radio resources for DC operation may be transmitted to the second BS, which may be a SgNB, via an Xn S-Node Addition Request message.

The proposed method accordingly discloses a new solution for differentiated wireless device handling also in LTE DC, and a solution for NR DC, by using an identifier. The proposed embodiments may use existing framework to implement a solution whereby it may be possible to block and/or allow a feature X for a wireless device based on an identifier by using an existing request resource allocation message.

According to a second aspect, there is provided a method, implemented in a second BS, for handling DC in a wireless communication system. The wireless communication system being adapted to provide for DC between a wireless device and a first BS, and between the wireless device and the second BS. The wireless device may, for example, be a UE. The method 200 is now going to be described with reference to the Figure 7 and 9. As previously mentioned, Figure 7 illustrates a message sequence chart of a process for handling DC in a wireless communication system. Figure 9 illustrates the method 200, implemented in the second BS, for handling DC in a wireless system.

The method 200 starts at step 210 with receiving 210, from the first BS, a request to allocate radio resources for DC operation for the wireless device. The request comprises an identifier that identifies a wireless device model of the wireless device.

The proposed method 200 uses the request to allocate resources for DC operation for the wireless device to receive an identifier that identifies a wireless device model of the wireless device. By receiving this identifier, it may be possible to receive the wireless device model in order to enable differentiated wireless device handling. This may provide operators the flexibility to block certain features for certain wireless device models. The operators do not need a first BS to have the knowledge of the second BS features to control operations such as, for example, observing a wireless device behavior in a multi-vendor deployment scenario. Accordingly, the proposed method 200 disclose a solution that enables differentiated wireless device handling regardless of vendors and RAT used in the communication system.

In one embodiment, the identifier may be a masked IMEISV that identifies the wireless device model without identifying the individual wireless device.

In one embodiment, the method 200 may further comprise performing 220, based on the received identifier, differentiated control on the wireless device. The differentiated control may, for example, be implemented on the wireless device during at least one of scheduling, state control and power distribution. The differentiated control may govern what radio configuration that is given to the wireless device for the secondary radio resource. It may, for example, be possible to control the number of carriers to be aggregated, Time Division Duplex (TDD) pattern, numerology and bands to be used.

For example, for an EN-DC call, the carrier aggregation for the NR side in existing solutions is decided by the gNB. It is not possible for the eNB to signal to the gNB to not configure carrier aggregation. The eNB can restrict gNB to certain band combinations, but with NR there is a concept of not signaling fallback combinations by the wireless device. Accordingly, there is no obvious way for the eNB to indicate disabling of NR carrier aggregation, and it is not possible to do it via X2 signaling. The eNB may only indicate the NR Primary Secondary cell (pSCell) candidate list to the gNB. The gNB may select a pSCell and choose its Secondary cells (SCells). With existing solutions, if the eNB indicates the wireless device capability to the gNB, the gNB will use this to select the NR carrier aggregation for the wireless device. However, with the proposed method where an identifier, which identifies a wireless device model of the wireless device, may be signaled to the gNB, the gNB will be informed that the NR carrier aggregation can be disabled.

In some embodiments, the second BS may operate a second radio connection using a second RAT, which is different from a first RAT used by the first BS to operate a first radio connection. The second BS may, for example, operate the second radio connection using NR, while the first BS may operate the first radio connection using LTE. The request to allocate radio resources for DC operation for the wireless device may be received from the first BS via an X2 interface. For example, the second BS may be a SgNB, and the request to allocate radio resources for DC operation is received from the first BS, which may be an MeNB, via an X2 SgNB Addition Request message.

Accordingly, the proposed embodiment disclose a solution for differentiated wireless device handling in multi-RAT DC by using an identifier. The proposed embodiment provides a solution for a non-standalone 5G deployment solution with DC between E- UTRA and NR network. Furthermore, the proposed method may use existing framework to implement a solution whereby it may be possible to block and/or allow a feature X for a wireless device based on an identifier and by using an existing message, such as the an X2 SgNB Addition Request message.

In some embodiments, the second BS may operate a second radio connection using same RAT as used by the first BS to operate a first radio connection. In one embodiment, the second BS may operate a second radio connection using LTE. The request to allocate radio resources for DC operation may be received from the first BS via an X2 interface. The second BS may, for example, be a SeNB and the request to allocate radio resources for DC operation may be received from the first BS, which may be an MeNB, via an X2 SeNB Addition Request message. In another embodiment, the second BS may operate a second radio connection using NR. The request to allocate radio resources for DC operation may be received from the first BS via an Xn interface. The second BS may, for example, be a SgNB and the request to allocate radio resources for DC operation may be received from the first BS, which may be an MgNB, via an Xn S-Node Addition Request message.

In one embodiment, the method 200 may further comprise transmitting 230 a request acknowledgement, if the second BS has decided to accept the received allocation request. In a further embodiment, the second BS may further allocate the necessary radio resources and provide radio resource configurations to the first BS.

According to a third aspect, there is provided a first BS for implementing the method according to the first aspect.

The first BS 300 is now going to be described with reference to Figure 10. The first BS 300 may be used in, but are not limited to, a wireless communication systems 600 such as illustrated in Figure 5.

The first BS 300 is configured for handling DC in a wireless communication system. The wireless communication system is being adapted to provide for DC between a wireless device and the first BS 300, and between the wireless device and a second BS. As illustrated in Figure 10, the first BS 300 comprises a processor, or a processing circuitry 310, and a memory, or a memory circuitry 320. The memory circuitry 320 storing computer program code which, when run in the processing circuitry 310, causes the first BS 300 to transmit, to the second BS, a request to allocate resources for DC operation for the wireless device. The request comprises an identifier that identifies a wireless device model of the wireless device.

Additionally, or alternatively, the first BS 300 may further comprise a transmitter, or a transmitting circuitry 340, configured to transmit data to other apparatuses, such as the second BS. In one embodiment, the identifier is a masked IMEISV that identifies the wireless device model without identifying the individual wireless device.

In some embodiments, the first BS 300 may be configured to operate a first radio connection using a first RAT, which is different from a second RAT used by the second

BS to operate a second radio connection. The wireless device may be operable to communicate over the first and the second radio connection. For example, the first BS 300 may be configured to operate the first radio connection using LTE, while the second BS may operate the second radio connection using NR. The first BS 300 may be configured to transmit the request to allocate radio resources for DC operation to the second BS via an X2 interface. The first BS may, according to this example, be an MeNB and the request to allocate radio resources for DC operation may be transmitted to the second BS, which may be a SgNB, via an X2 SgNB Addition Request message.

In some embodiments, the first BS 300 may be configured to operate a first radio connection using same RAT as used by the second BS to operate a second radio connection. In one embodiment, the first BS 300 may be configured to operate the first radio connection using LTE. The first BS 300 may be configured to transmit the request to allocate radio resources for DC operation to the second BS via an X2 interface. The first BS may, for example, be an MeNB and the request to allocate radio resources for DC operation may be transmitted to the second BS, which may be a SeNB, via an X2 SeNB Addition Request message. In another embodiment, the first BS 300 may be configured to operate the first radio connection using NR. The first BS 300 may be configured to transmit the request to allocate radio resources for DC operation to the second BS via an Xn interface. The first BS may, for example, be an MgNB and the request to allocate radio resources for DC operation may be transmitted to the second BS, which may be a SgNB, via an Xn S-Node Addition Request message.

In one embodiment, the memory circuitry 320 of the first BS 300 may further store computer program code which, when run in the processing circuitry 310, causes the first BS 300 to receive a request acknowledgement. Additionally, or alternatively, the first BS 300 may further comprise a receiver, or a receiving circuitry 330, configured to receive data from other apparatuses, such as a second BS.

According to a fourth aspect, there is provided a second BS for implementing the method according to the second aspect.

The second BS 400 is now going to be described with reference to Figure 11. The second BS 400 may be used in, but are not limited to, a wireless communication systems 600 such as illustrated in Figure 5.

The second BS 400 is configured for handling DC in a wireless communication system. The wireless communication system is being adapted to provide for DC between a wireless device and a first BS 300 and between the wireless device and the second BS 400. As illustrated in Figure 11, the second BS 400 comprises a processor, or a processing circuitry 410, and a memory, or a memory circuitry 420. The memory circuitry 420 storing computer program code which, when run in the processing circuitry 410, causes the second BS 400 to receive, from the first BS 300, a request to allocate radio resources for DC operation for the wireless device. The request comprises an identifier that identifies a wireless device model of the wireless device.

Additionally, or alternatively, the second BS 400 may further comprise a receiver, or a receiving circuitry 430, configured to receive data from other apparatuses, such as a first BS 300.

In one embodiment, the identifier may be a masked IMEISV that identifies the wireless device model without identifying the individual wireless device.

In one embodiment, the memory circuitry 420 may store computer program code which, when run in the processing circuitry 410, further may cause the second BS 400 to perform differentiated control on the wireless device based the received identifier. The differentiated control may, for example, be implemented on the wireless device during at least one of scheduling, state control and power distribution. In some embodiments, the second BS 400 may be configured to operate a second radio connection using a second RAT, which is different from a first RAT used by the first BS 300 to operate a first radio connection. The wireless device may be operable to communicate over the first and the second radio connection. The second BS 400 may, for example, be configured to operate the second radio connection using NR, while the first BS 300 may operate the first radio connection using LTE. The second BS 400 may be configured to receive the request to allocate radio resources for DC operation from the first BS 300 via an X2 interface. According to this example, the second BS 400 may, for example, be a SgNB, and the request to allocate radio resources for DC operation may be received from the first BS 300, which is an MeNB, via an X2 SgNB Addition Request message.

In some embodiments, the second BS 400 may be configured to operate a second radio connection using same RAT as used by the first BS 300 to operate a first radio connection. In one embodiment, the second BS 400 may be configured to operate the second radio connection using LTE. The second BS 400 may be configured to receive the request to allocate radio resources for DC operation from the first BS (300) via an X2 interface. The second BS 400 may, for example, be a SeNB and the request to allocate radio resources for DC operation may be received from the first BS 300, which may be an MeNB, via an X2 SeNB Addition Request message. In another embodiment, the second BS 400 may be configured to operate the second radio connection using NR. The second BS 400 may be configured to receive the request to allocate radio resources for DC operation from the first BS 300 via an Xn interface. The second BS 400 may, for example, be a SgNB and the request to allocate radio resources for DC operation may be received from the first BS, which may be an MgNB, via an Xn S-Node Addition Request message.

According to a fifth aspect, there is provided a computer program comprising instructions which, when executed on a processing circuitry, cause the processing circuitry to carry out the method according to the first aspect and/or the second aspect. According to an sixth aspect, there is provided a carrier containing the computer program of the fifth aspect, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments described herein relate to a wireless network, such as the example wireless communication network illustrated in Figure 12. For simplicity, the wireless communication network of Figure 12 only depicts network 1206, network nodes 1260 and 1260b, and Wireless Devices (WDs) 1210, 1210b, and 1210c. The wireless communication 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. Of the illustrated components, network node 1260 and wireless device (WD) 1210 are depicted with additional detail. The illustrated wireless communication 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 the wireless communication network.

The wireless communication 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 communication network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless communication 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, and/or ZigBee standards.

Network 1206 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 1260 and WD 1210 comprise various components described in more detail below. These components may 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 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 communication network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless communication 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, and evolved Node Bs (eNBs)). 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, network node 1260 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 communication network or to provide some service to a wireless device that has accessed the wireless communication network.

In Figure 12, Network node 1260 includes processing circuitry 1270, device readable medium 1280, interface 1290, user interface equipment 1282, auxiliary equipment 1284, power source 1286, power circuitry 1287, and antenna 1262. Although network node 1260 illustrated in the example wireless communication network of Figure 12 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 may comprise 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 1260 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 1280 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 1260 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 1260 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 NodeBs. 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 1260 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 1280 for the different RATs) and some components may be reused (e.g., the same antenna 1262 may be shared by the RATs). Network node 1260 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1260, 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 1260.

Processing circuitry 1270 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 1270 may include processing information obtained by processing circuitry 1270 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 1270 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 1260 components, such as device readable medium 1280, network node 1260 functionality. For example, processing circuitry 1270 may execute instructions stored in device readable medium 1280 or in memory within processing circuitry 1270. Such functionality may include providing any of the various wireless features or benefits discussed herein. In some embodiments, processing circuitry 1270 may include a system on a chip (SOC).

In some embodiments, processing circuitry 1270 may include one or more of radio frequency (RF) transceiver circuitry 1272 and baseband processing circuitry 1274. In some embodiments, radio frequency (RF) transceiver circuitry 1272 and baseband processing circuitry 1274 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 1272 and baseband processing circuitry 1274 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 provided by processing circuitry 1270 executing instructions stored on device readable medium 1280 or memory within processing circuitry 1270. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 1270 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 1270 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1270 alone or to other components of network node 1260, but are enjoyed by network node 1260 as a whole, and/or by end users and the wireless network generally.

Device readable medium 1280 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 1270. Device readable medium 1280 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 1270 and, utilized by network node 1260. Device readable medium 1280 may be used to store any calculations made by processing circuitry 1270 and/or any data received via interface 1290. In some embodiments, processing circuitry 1270 and device readable medium 1280 may be considered to be integrated. Interface 1290 is used in the wired or wireless communication of signaling and/or data between network node 1260, network 1206, and/or WDs 1210. As illustrated, interface 1290 comprises port(s)/terminal(s) 1294 to send and receive data, for example to and from network 1206 over a wired connection. Interface 1290 also includes radio front end circuitry 1292 that may be coupled to, or in certain embodiments a part of, antenna 1262. Radio front end circuitry 1292 comprises filters 1298 and amplifiers 1296. Radio front end circuitry 1292 may be connected to antenna 1262 and processing circuitry 1270. Radio front end circuitry may be configured to condition signals communicated between antenna 1262 and processing circuitry 1270. Radio front end circuitry 1292 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1292 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1298 and/or amplifiers 1296. The radio signal may then be transmitted via antenna 1262. Similarly, when receiving data, antenna 1262 may collect radio signals which are then converted into digital data by radio front end circuitry 1292. The digital data may be passed to processing circuitry 1270. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 1260 may not include separate radio front end circuitry 1292, instead, processing circuitry 1270 may comprise radio front end circuitry and may be connected to antenna 1262 without separate radio front end circuitry 1292. Similarly, in some embodiments, all or some of RF transceiver circuitry 1272 may be considered a part of interface 1290. In still other embodiments, interface 1290 may include one or more ports or terminals 1294, radio front end circuitry 1292, and RF transceiver circuitry 1272, as part of a radio unit (not shown), and interface 1290 may communicate with baseband processing circuitry 1274, which is part of a digital unit (not shown).

Antenna 1262 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 1262 may be coupled to radio front end circuitry 1290 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 1262 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 1262 may be separate from network node 1260 and may be connectable to network node 1260 through an interface or port.

Antenna 1262, interface 1290, and/or processing circuitry 1270 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 1262, interface 1290, and/or processing circuitry 1270 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 1287 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 1260 with power for performing the functionality described herein. Power circuitry 1287 may receive power from power source 1286. Power source 1286 and/or power circuitry 1287 may be configured to provide power to the various components of network node 1260 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1286 may either be included in, or external to, power circuitry 1287 and/or network node 1260. For example, network node 1260 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 1287. As a further example, power source 1286 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 1287. 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 1260 may include additional components beyond those shown in Figure 12 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 1260 may include user interface equipment to allow input of information into network node 1260 and to allow output of information from network node 1260. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1260.

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- every thing (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 1210 includes antenna 1211, interface 1214, processing circuitry 1220, device readable medium 1230, user interface equipment 1232, auxiliary equipment 1234, power source 1236 and power circuitry 1237. WD 1210 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 1210, 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 1210.

Antenna 1211 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 1214. In certain alternative embodiments, antenna 1211 may be separate from WD 1210 and be connectable to WD 1210 through an interface or port. Antenna 1211, interface 1214, and/or processing circuitry 1220 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 1211 may be considered an interface.

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

Processing circuitry 1220 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 1210 components, such as device readable medium 1230, WD 1210 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 1220 may execute instructions stored in device readable medium 1230 or in memory within processing circuitry 1220 to provide the functionality disclosed herein. As illustrated, processing circuitry 1220 includes one or more of RF transceiver circuitry 1222, baseband processing circuitry 1224, and application processing circuitry 1226. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 1220 of WD 1210 may comprise a SOC. In some embodiments, RF transceiver circuitry 1222, baseband processing circuitry 1224, and application processing circuitry 1226 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 1224 and application processing circuitry 1226 may be combined into one chip or set of chips, and RF transceiver circuitry 1222 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 1222 and baseband processing circuitry 1224 may be on the same chip or set of chips, and application processing circuitry 1226 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 1222, baseband processing circuitry 1224, and application processing circuitry 1226 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 1222 may be a part of interface 1214. RF transceiver circuitry 1222 may condition RF signals for processing circuitry 1220.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 1220 executing instructions stored on device readable medium 1230, 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 1220 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 1220 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1220 alone or to other components of WD 1210, but are enjoyed by WD 1210 as a whole, and/or by end users and the wireless network generally. Processing circuitry 1220 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 1220, may include processing information obtained by processing circuitry 1220 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 1210, 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 1230 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 1220. Device readable medium 1230 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 1220. In some embodiments, processing circuitry 1220 and device readable medium 1230 may be considered to be integrated.

User interface equipment 1232 may provide components that allow for a human user to interact with WD 1210. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 1232 may be operable to produce output to the user and to allow the user to provide input to WD 1210. The type of interaction may vary depending on the type of user interface equipment 1232 installed in WD 1210. For example, if WD 1210 is a smart phone, the interaction may be via a touch screen; ifWD 1210 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 1232 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 1232 is configured to allow input of information into WD 1210, and is connected to processing circuitry 1220 to allow processing circuitry 1220 to process the input information. User interface equipment 1232 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 1232 is also configured to allow output of information from WD 1210, and to allow processing circuitry 1220 to output information from WD 1210. User interface equipment 1232 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 1232, WD 1210 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment 1234 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 1234 may vary depending on the embodiment and/or scenario.

Power source 1236 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 1210 may further comprise power circuitry 1237 for delivering power from power source 1236 to the various parts of WD 1210 which need power from power source 1236 to carry out any functionality described or indicated herein. Power circuitry 1237 may in certain embodiments comprise power management circuitry. Power circuitry 1237 may additionally or alternatively be operable to receive power from an external power source; in which case WD 1210 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 1237 may also in certain embodiments be operable to deliver power from an external power source to power source 1236. This may be, for example, for the charging of power source 1236. Power circuitry 1237 may perform any formatting, converting, or other modification to the power from power source 1236 to make the power suitable for the respective components of WD 1210 to which power is supplied. Figure 13 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 1300 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 1300, as illustrated in Figure 13, 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 Figure 13 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In Figure 13, UE 1300 includes processing circuitry 1301 that is operatively coupled to input/output interface 1305, radio frequency (RF) interface 1309, network connection interface 1311, memory 1315 including random access memory (RAM) 1317, read-only memory (ROM) 1314, and storage medium 1321 or the like, communication subsystem 1331, power source 1333, and/or any other component, or any combination thereof. Storage medium 1321 includes operating system 1323, application program 1325, and data 1327. In other embodiments, storage medium 1321 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 13, 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 Figure 13, processing circuitry 1301 may be configured to process computer instructions and data. Processing circuitry 1301 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 1301 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 1305 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 1300 may be configured to use an output device via input/output interface 1305. 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 1300. 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 1300 may be configured to use an input device via input/output interface 1305 to allow a user to capture information into UE 1300. 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, and an optical sensor.

In Figure 13, RF interface 1309 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 1311 may be configured to provide a communication interface to network 1343a. Network 1343a 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 1343a may comprise a Wi-Fi network. Network connection interface 1311 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 1311 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 1317 may be configured to interface via bus 1302 to processing circuitry 1301 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 1314 may be configured to provide computer instructions or data to processing circuitry 1301. For example, ROM 1314 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 anon-volatile memory. Storage medium 1321 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 1321 may be configured to include operating system 1323, application program 1325 such as a web browser application, a widget or gadget engine or another application, and data file 1327. Storage medium 1321 may store, for use by UE 1300, any of a variety of various operating systems or combinations of operating systems.

Storage medium 1321 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 1321 may allow UE 1300 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 1321, which may comprise a device readable medium. In Figure 13, processing circuitry 1301 may be configured to communicate with network 1343b using communication subsystem 1331. Network 1343a and network 1343b may be the same network or networks or different network or networks. Communication subsystem 1331 may be configured to include one or more transceivers used to communicate with network 1343b. For example, communication subsystem 1331 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.13, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 1333 and/or receiver 1335 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 1333 and receiver 1335 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 1331 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 1331 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 1343b 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 1343b may be a cellular network, a Wi-Fi network, and/or a near- field network. Power 5 source 1313 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 1300.

The features, benefits and/or functions described herein may be implemented in one of the components of UE 1300 or partitioned across multiple components of UE 1300. 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 1331 may be configured to include any of the components described herein. Further, processing circuitry 1301 may be configured to communicate with any of such components over bus 1302. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 1301 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 1301 and communication subsystem 1331. 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.

Figure 14 is a schematic block diagram illustrating a virtualization environment 1400 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 1400 hosted by one or more of hardware nodes 1430. 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 1420 (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 1420 are run in virtualization environment 1400 which provides hardware 1430 comprising processing circuitry 1460 and memory 1490. Memory 1490 contains instructions 1495 executable by processing circuitry 1460 whereby application 1420 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment 1400, comprises general-purpose or special-purpose network hardware devices 1430 comprising a set of one or more processors or processing circuitry 1460, 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 analogue hardware components or special purpose processors. Each hardware device may comprise memory 1490-1 which may be non- persistent memory for temporarily storing instructions 1495 or software executed by processing circuitry 1460. Each hardware device may comprise one or more network interface controllers (NICs) 1470, also known as network interface cards, which include physical network interface 1480. Each hardware device may also include non-transitory, persistent, machine-readable storage media 1490-2 having stored therein software 1495 and/or instructions executable by processing circuitry 1460. Software 1495 may include any type of software including software for instantiating one or more virtualization layers 1450 (also referred to as hypervisors), software to execute virtual machines 1440 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

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

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

As shown in Figure 14, hardware 1430 may be a standalone network node with generic or specific components. Hardware 1430 may comprise antenna 14225 and may implement some functions via virtualization. Alternatively, hardware 1430 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) 14100, which, among others, oversees lifecycle management of applications 1420.

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 centres, and customer premise equipment.

In the context of NFV, virtual machine 1440 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 1440, and that part of hardware 1430 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 1440, 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 1440 on top of hardware networking infrastructure 1430 and corresponds to application 1420 in Figure 14.

In some embodiments, one or more radio units 14200 that each include one or more transmitters 14220 and one or more receivers 14210 may be coupled to one or more antennas 14225. Radio units 14200 may communicate directly with hardware nodes 1430 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 signaling can be affected with the use of control system 14230 which may alternatively be used for communication between the hardware nodes 1430 and radio units 14200.

With reference to Figure 15, in accordance with an embodiment, a communication system includes telecommunication network 1510, such as a 3GPP-type cellular network, which comprises access network 1511, such as a radio access network, and core network 1514. Access network 1511 comprises a plurality of base stations 1512a, 1512b, 1512c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1513a, 1513b, 1513c. Each base station 1512a, 1512b, 1512c is connectable to core network 1514 over a wired or wireless connection 1515. A first UE 1591 located in coverage area 1513c is configured to wirelessly connect to, or be paged by, the corresponding base station 1512c. A second UE 1592 in coverage area 1513a is wirelessly connectable to the corresponding base station 1512a. While a plurality of UEs 1591, 1592 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 1512.

Telecommunication network 1510 is itself connected to host computer 1530, 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 1530 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 1516 and 1522 between telecommunication network 1510 and host computer 1530 may extend directly from core network 1514 to host computer 1530 or may go via an optional intermediate network 1520. Intermediate network 1520 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1520, if any, may be a backbone network or the Internet; in particular, intermediate network 1520 may comprise two or more sub-networks (not shown).

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

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 Figure 16. In communication system 1600, host computer 1610 comprises hardware 1615 including communication interface 1616 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1600. Host computer 1610 further comprises processing circuitry 1618, which may have storage and/or processing capabilities. In particular, processing circuitry 1618 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 1610 further comprises software 1611, which is stored in or accessible by host computer 1610 and executable by processing circuitry 1618. Software 1611 includes host application 1612. Host application 1612 may be operable to provide a service to a remote user, such as UE 1630 connecting via OTT connection 1650 terminating at UE 1630 and host computer 1610. In providing the service to the remote user, host application 1612 may provide user data which is transmitted using OTT connection 1650.

Communication system 1600 further includes base station 1620 provided in a telecommunication system and comprising hardware 1625 enabling it to communicate with host computer 1610 and with UE 1630. Hardware 1625 may include communication interface 1626 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1600, as well as radio interface 1627 for setting up and maintaining at least wireless connection 1670 with UE 1630 located in a coverage area (not shown in Figure 16) served by base station 1620. Communication interface 1626 may be configured to facilitate connection 1660 to host computer 1610. Connection 1660 may be direct, or it may pass through a core network (not shown in Figure 16) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 1625 of base station 1620 further includes processing circuitry 1628, 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 1620 further has software 1616 stored internally or accessible via an external connection.

Communication system 1600 further includes UE 1630 already referred to. Its hardware 1635 may include radio interface 1637 configured to set up and maintain wireless connection 1670 with a base station serving a coverage area in which UE 1630 is currently located. Hardware 1635 of UE 1630 further includes processing circuitry 1638, 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 1630 further comprises software 1631, which is stored in or accessible by UE 1630 and executable by processing circuitry 1638. Software 1631 includes client application 1632. Client application 1632 may be operable to provide a service to a human or non-human user via UE 1630, with the support of host computer 1610. In host computer 1610, an executing host application 1612 may communicate with the executing client application 1632 via OTT connection 1650 terminating at UE 1630 and host computer 1610. In providing the service to the user, client application 1632 may receive request data from host application 1612 and provide user data in response to the request data. OTT connection 1650 may transfer both the request data and the user data. Client application 1632 may interact with the user to generate the user data that it provides.

It is noted that host computer 1610, base station 1620 and UE 1630 illustrated in Figure 16 may be similar or identical to host computer 1630, one of base stations 1512a, 1512b, 1512c and one of UEs 1591, 1592 of Figure 15, respectively. This is to say, the inner workings of these entities may be as shown in Figure 16 and independently, the surrounding network topology may be that of Figure 15.

In Figure 16, OTT connection 1650 has been drawn abstractly to illustrate the communication between host computer 1610 and UE 1630 via base station 1620, 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 1630 or from the service provider operating host computer 1610, or both. While OTT connection 1650 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 1670 between UE 1630 and base station 1620 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 1630 using OTT connection 1650, in which wireless connection 1670 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate and thereby provide benefits such as better responsiveness. 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 1650 between host computer 1610 and UE 1630, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 1650 may be implemented in software 1611 and hardware 1615 of host computer 1610 or in software 1631 and hardware 1635 of UE 1630, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 1650 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 1611, 1631 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 1650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 1620, and it may be unknown or imperceptible to base station 1620. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 1610’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 1611 and 1631 causes messages to be transmitted, in particular empty or‘dummy’ messages, using OTT connection 1650 while it monitors propagation times, errors etc.

Figure 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 Figures 15 and 16. For simplicity of the present disclosure, only drawing references to Figure 17 will be included in this section. In step 1710, the host computer provides user data. In substep 1711 (which may be optional) of step 1710, the host computer provides the user data by executing a host application. In step 1720, the host computer initiates a transmission carrying the user data to the UE. In step 1730 (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 1740 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

Figure 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 Figures 15 and 16. For simplicity of the present disclosure, only drawing references to Figure 18 will be included in this section. In step 1810 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 1820, 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 1830 (which may be optional), the UE receives the user data carried in the transmission.

Figure 19 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 Figures 15 and 16. For simplicity of the present disclosure, only drawing references to Figure 19 will be included in this section. In step 1910 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1920, the UE provides user data. In substep 1921 (which may be optional) of step 1920, the UE provides the user data by executing a client application. In substep 1911 (which may be optional) of step 1910, 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 1930 (which may be optional), transmission of the user data to the host computer. In step 1940 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.

Figure 20 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 Figures 15 and 16. For simplicity of the present disclosure, only drawing references to Figure 20 will be included in this section. In step 2010 (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 2020 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 2100 (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.

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.

Numbered embodiments in particular related to Figures 12-20

1. A first Base Station (BS) configured to communicate with a User Equipment (UE), the first BS comprising a radio interface and processing circuitry configured to:

transmit, to a second BS , a request to allocate resources for DC operation for the UE, wherein the request comprises an identifier that identifies a UE model of the UE.

2. The first base station according to embodiment 1, wherein the identifier is a masked International Mobile station Equipment Identity and Software Version number, IMEISV, that identifies the UE model without identifying the individual UE.

3. The first BS according to any of embodiment 1 and 2, wherein the first BS is configured to operate a first radio connection using a first Radio Access Technology (RAT), which is different from a second RAT used by the second BS to operate a second radio connection, wherein the UE is operable to communicate over the first and the second radio connection.

4. The first BS according to embodiment 3, wherein the first BS is configured to operate the first radio connection using Long Term Evolution (LTE), while the second BS operates the second radio connection using New Radio (NR), and wherein the first BS is configured to transmit the request to allocate radio resources for DC operation to the second BS via an X2 interface.

5. The first BS according to embodiment 4, wherein the first BS is a Master eNode B (MeNB), and the request to allocate radio resources for DC operation is transmitted to the second BS, which is a Secondary gNode B (SgNB), via an X2 SgNB Addition Request message

6. The first BS according to any of embodiment 1 and 2, wherein the first BS is configured to operate a first radio connection using same Radio Access Technology (RAT), as used by the second BS to operate a second radio connection.

7. The first BS according to embodiment 6, wherein the first BS is configured to operate the first radio connection using Long Term Evolution (LTE), and wherein the first BS is configured to transmit the request to allocate radio resources for DC operation to the second BS via an X2 interface.

8. The first BS (300) according to embodiment 6, wherein the first BS is configured to operate the first radio connection using New Radio (NR) and wherein the first BS is configured to transmit the request to allocate radio resources for DC operation to the second BS via an Xn interface.

9. A communication system including a host computer comprising:

processing circuitry configured to provide user data; and

a communication interface configured to forward the user data to a cellular network for transmission to a User Equipment (UE),

wherein the cellular network comprises a first Base Station (BS) having a radio interface and processing circuitry, the base station’s processing circuitry configured to transmit, to a second BS, a request to allocate resources for DC operation for the UE, wherein the request comprises an identifier that identifies a UE model of the UE.

10. The communication system of embodiment 9, further including the first BS.

11. The communication system of embodiment 10, further including the UE, wherein the UE is configured to communicate with the first BS.

12. The communication system of embodiment 11, wherein:

the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and

the UE comprises processing circuitry configured to execute a client application associated with the host application.

13. A method implemented in a first Base Station (BS), comprising

transmitting, to a second BS, a request to allocate resources for DC operation for a User Equipment (UE), wherein the request comprises an identifier that identifies a UE model of the UE. 14. A method implemented in a communication system including a host computer, a first Base Station (BS) and a User Equipment (UE), the method comprising:

at the host computer, providing user data; and

at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the first BS, wherein the first BS

transmitting, to a second BS, a request to allocate resources for DC operation for a User Equipment (UE), wherein the request comprises an identifier that identifies a UE model of the UE.

15. The method of embodiment 14, further comprising:

at the first BS, transmitting the user data.

16. The method of embodiment 15, wherein the user data is provided at the host computer by executing a host application, the method further comprising:

at the UE, executing a client application associated with the host application.

17. A User Equipment (UE) configured to communicate with a first Base Station (BS), the UE comprising a radio interface and processing circuitry configured to transmit and receive data to and from the first BS.

18. A communication system including a host computer comprising:

processing circuitry configured to provide user data; and

a communication interface configured to forward user data to a cellular network for transmission to a User Equipment (UE),

wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to transmit and receive data to and from a first Base Station (BS).

19. The communication system of embodiment 18, further including the UE.

20. The communication system of embodiment 18, wherein the cellular network further includes a first BS configured to communicate with the UE.

21. The communication system of embodiment 19 or 20, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and

the UE’s processing circuitry is configured to execute a client application associated with the host application.

22. A method implemented in a communication system including a host computer, a first Base Station (BS) and a User Equipment (UE), the method comprising:

at the host computer, providing user data; and

at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the first BS, wherein the UE transmits and receives to and from the first BS.

23. The method of embodiment 22, further comprising:

at the UE, receiving the user data from the first BS.

24. A communication system including a host computer comprising:

a communication interface configured to receive user data originating from a transmission from a User Equipment (UE) to a first Base Station (BS),

wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to transmit and receive data to and from the first BS.

25. The communication system of embodiment 24, further including the UE.

26. The communication system of embodiment 25, further including the first BS,

wherein the first BS comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the first BS.

27. The communication system of embodiment 25 or 26, wherein:

the processing circuitry of the host computer is configured to execute a host application;

and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data. 28. The communication system of embodiment 25 or 26, wherein:

the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and

the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

29. A method implemented in a User Equipment (UE), comprising transmitting and

receiving data to and from a first Base Station (BS).

30. The method of embodiment 29, further comprising:

providing user data; and

forwarding the user data to a host computer via the transmission to the first BS.

31. A method implemented in a communication system including a host computer, a first Base Station (BS) and a User Equipment (UE), the method comprising:

at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE transmitting and receiving data to and from the first BS.

32. The method of embodiment 31, further comprising:

at the UE, providing the user data to the first BS.

33. The method of embodiment 32, further comprising:

at the UE, executing a client application, thereby providing the user data to be transmitted; and

at the host computer, executing a host application associated with the client application.

34. The method of embodiment 33, further comprising:

at the UE, executing a client application; and

at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.

35. A communication system including a host computer comprising a communication

interface configured to receive user data originating from a transmission from a User Equipment (UE) to a first Base Station (BS), wherein the first BS comprises a radio interface and processing circuitry, the BS’s processing circuitry configured to transmit, to a second BS, a request to allocate resources for DC operation for the UE, wherein the request comprises an identifier that identifies a UE model of the UE.

36. The communication system of embodiment 35, further including the first BS.

37. The communication system of embodiment 36, further including the UE, wherein the UE is configured to communicate with the first BS.

38. The communication system of embodiment 37, wherein:

the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

39. A method implemented in a communication system including a host computer, a first Base Station (BS) and a User Equipment (UE), the method comprising:

at the host computer, receiving, from the first BS, user data originating from a transmission which the first BS has received from the UE, wherein the UE transmits and receives data to and from the first BS.

40. The method of embodiment 39, further comprising:

at the first BS, receiving the user data from the UE.

41. The method of embodiment 40, further comprising:

at the first BS, initiating a transmission of the received user data to the host

computer.

42. A second Base Station (BS) configured to communicate with a User Equipment (UE), the second BS comprising a radio interface and processing circuitry configured to: receive, from a first BS, a request to allocate radio resources for DC operation for the UE, wherein the request comprises an identifier that identifies a UE model of the UE.

43. The second BS according to embodiment 42, wherein the identifier is a masked International Mobile station Equipment Identity and Software Version number (IMEISV) that identifies the UE model without identifying the individual UE.

44. The second BS according to any of embodiment 42 and 43, wherein the second BS further is configured to:

perform, based on the received identifier, differentiated control on the UE.

45. The second BS according to embodiment 44, wherein the differentiated control is implemented on the UE during at least one of scheduling, state control and power distribution.

46. The second BS according to any of embodiments 42 to 45, wherein the second BS operates a second radio connection using a second Radio Access Technology (RAT), which is different from a first RAT used by the first BS to operate a first radio connection.

47. The second BS according to embodiment 46, wherein the second BS is configured to operate the second radio connection using NR, while the first BS operates the first radio connection using LTE, and wherein the second BS is configured to receive the request to allocate radio resources for DC operation from the first BS via an X2 interface.

48. The second BS according to embodiment 47, wherein the second BS is a Secondary gNode B (SgNB), and the request to allocate radio resources for DC operation is received from the first BS, which is a Master eNode B (MeNB), via an X2 SgNB Addition Request message

49. The second BS according to any of embodiment 42 and 45, wherein the second BS is configured to operate a second radio connection using same Radio Access Technology (RAT) as used by the first BS to operate a first radio connection. 50. The second BS according to embodiment 49, wherein the second BS is configure to operate a second radio connection using LTE, and wherein the request to allocate radio resources for DC operation is received from the first BS via an X2 interface.

51. The second BS according to embodiment 49, wherein the second BS is configured to operate a second radio connection using NR and wherein the second BS is configured to receive the request to allocate radio resources for DC operation from the first BS via an Xn interface.

52. A communication system including a host computer comprising:

processing circuitry configured to provide user data; and

a communication interface configured to forward the user data to a cellular network for transmission to a User Equipment (UE),

wherein the cellular network comprises a second Base Station (BS) having a radio interface and processing circuitry, the base station’s processing circuitry configured to receive, from a first BS, a request to allocate resources for DC operation for the UE, wherein the request comprises an identifier that identifies a UE model of the UE.

53. The communication system of embodiment 52, further including the second BS.

54. The communication system of embodiment 53, further including the UE, wherein the UE is configured to communicate with the second BS.

55. The communication system of embodiment 54, wherein:

the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and

the UE comprises processing circuitry configured to execute a client application associated with the host application.

56. A method implemented in a second Base Station (BS), comprising

receiving, from a first BS, a request to allocate resources for DC operation for a User Equipment (UE), wherein the request comprises an identifier that identifies a UE model of the UE. 57. A method implemented in a communication system including a host computer, a second Base Station (BS) and a User Equipment (UE), the method comprising:

at the host computer, providing user data; and

at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the second BS, wherein the secon BS

receiving, from a first BS, a request to allocate resources for DC operation for a User Equipment (UE), wherein the request comprises an identifier that identifies a UE model of the UE.

58. The method of embodiment 57, further comprising:

at the second BS, transmitting the user data.

59. The method of embodiment 58, wherein the user data is provided at the host computer by executing a host application, the method further comprising:

at the UE, executing a client application associated with the host application.

60. A User Equipment (UE) configured to communicate with a second Base Station (BS), the UE comprising a radio interface and processing circuitry configured to transmit and receive data to and from the second BS.

61. A communication system including a host computer comprising:

processing circuitry configured to provide user data; and

a communication interface configured to forward user data to a cellular network for transmission to a User Equipment (UE),

wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to transmit and receive data to and from a second Base Station (BS).

62. The communication system of embodiment 61, further including the UE.

63. The communication system of embodiment 61, wherein the cellular network further includes a second BS configured to communicate with the UE.

64. The communication system of embodiment 62 or 63, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and

the UE’s processing circuitry is configured to execute a client application associated with the host application.

65. A method implemented in a communication system including a host computer, a second Base Station (BS) and a User Equipment (UE), the method comprising:

at the host computer, providing user data; and

at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the second BS, wherein the UE transmits and receives to and from the second BS.

66. The method of embodiment 65, further comprising:

at the UE, receiving the user data from the second BS.

67. A communication system including a host computer comprising:

a communication interface configured to receive user data originating from a transmission from a User Equipment (UE) to a second Base Station (BS),

wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to transmit and receive data to and from the second BS.

68. The communication system of embodiment 67, further including the UE.

69. The communication system of embodiment 68, further including the second BS,

wherein the second BS comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the second BS.

70. The communication system of embodiment 68 or 69, wherein:

the processing circuitry of the host computer is configured to execute a host application;

and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data. 71. The communication system of embodiment 68 or 69, wherein:

the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and

the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

72. A method implemented in a User Equipment (UE), comprising transmitting and

receiving data to and from a second Base Station (BS).

73. The method of embodiment 72, further comprising:

providing user data; and

forwarding the user data to a host computer via the transmission to the second BS.

74. A method implemented in a communication system including a host computer, a second Base Station (BS) and a User Equipment (UE), the method comprising:

at the host computer, receiving user data transmitted to the second BS from the UE, wherein the UE transmitting and receiving data to and from the second BS.

75. The method of embodiment 74, further comprising:

at the UE, providing the user data to the second BS.

76. The method of embodiment 75, further comprising:

at the UE, executing a client application, thereby providing the user data to be transmitted; and

at the host computer, executing a host application associated with the client application.

77. The method of embodiment 76, further comprising:

at the UE, executing a client application; and

at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.

78. A communication system including a host computer comprising a communication

interface configured to receive user data originating from a transmission from a User Equipment (UE) to a second Base Station (BS), wherein the second BS comprises a radio interface and processing circuitry, the second BS’s processing circuitry configured to receive, from a first BS, a request to allocate resources for DC operation for the UE, wherein the request comprises an identifier that identifies a UE model of the UE.

79. The communication system of embodiment 78, further including the second BS.

80. The communication system of embodiment 79, further including the UE, wherein the UE is configured to communicate with the second BS.

81. The communication system of embodiment 80, wherein:

the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

82. A method implemented in a communication system including a host computer, a

second Base Station (BS) and a User Equipment (UE), the method comprising:

at the host computer, receiving, from the second BS, user data originating from a transmission which the second BS has received from the UE, wherein the UE transmits and receives data to and from the second BS.

83. The method of embodiment 82, further comprising:

at the second BS, receiving the user data from the UE.

84. The method of embodiment 40, further comprising:

at the second BS, initiating a transmission of the received user data to the host computer. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. 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. It will be further understood that the terms "comprises" "comprising," "includes" and/or "including" when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood. It will be further understood that terms used herein 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.

Modifications and other variants of the described embodiments will come to mind to one skilled in the art having benefit of the teachings presented in the foregoing description and associated drawings. Therefore, it is to be understood that the embodiments are not limited to the specific example embodiments described in this disclosure and that modifications and other variants are intended to be included within the scope of this disclosure. Furthermore, although specific terms may be employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation. Therefore, a person skilled in the art would recognize numerous variations to the described embodiments that would still fall within the scope of the appended claims. As used herein, the terms“comprise/comprises” or“include/includes” do not exclude the presence of other elements or steps. Furthermore, although individual features may be included in different claims, these may possibly advantageously be combined, and the inclusion of different claims does not imply that a combination of features is not feasible and/or advantageous. In addition, singular references do not exclude a plurality.