Patent ID: 12207317

DETAILED DESCRIPTION

FIG.1shows a wireless communication network10according to some embodiments. The wireless communication network10includes a radio access network (RAN)10A (e.g., based on New Radio, NR) and a core network (CN)10B. The RAN10A includes a network node12(e.g., base station) that provides radio access to a wireless device14. In some embodiments (e.g., where the RAN10A is an NR Unlicensed, NR-U, network), this radio access may be provided in unlicensed frequency spectrum. The unlicensed frequency spectrum is frequency spectrum within which transmissions may be performed without a license from a licensor (which may be a regulatory or governing entity, e.g., the United States Federal Communications Commission, FCC, or the International Telecommunication Union, ITU). Regardless, the RAN10A via the radio access connects the wireless device14to the CN10B, which may in turn connect to one or more data networks (e.g., the Internet).

The wireless device14is configured to perform a random access procedure with the network node12. The random access procedure may for instance be performed in order for the wireless device14to acquire uplink synchronization, to establish or resume a radio resource control (RRC) connection, etc.

The random access procedure as shown includes two steps, e.g., as opposed to the conventional 4 steps. In the first step, the wireless device14performs a transmission16on a random access channel (RACH) and an uplink shared channel (e.g., a physical uplink shared channel, PUSCH). This transmission16may be referred to as MSG A. The transmission16on the RACH may convey a random access preamble. The transmission16on the uplink shared channel may convey an RRC establishment request or RRC resume request. The transmission16on the RACH and the transmission16on the uplink shared channel may be performed in the same subframe, or in successive subframes, e.g., such that the transmission16on the uplink shared channel is performed before any response is received to the transmission16on the RACH.

In the second step, the network node12transmits a response to the RACH and uplink shared channel transmission16. If the network node12successfully decoded the RACH and the uplink shared channel payload, the network node12transmits a random access success response message (also referred to as a random access success response, or simply, success response). This random access success response message correspondingly indicates that both the RACH and the uplink shared channel payload were decoded successfully. Note in this regard that, unlike the traditional 4-step procedure, the random access success response is transmitted as a response to both the RACH and the uplink shared channel transmission16.

In any event, the network node12in some embodiments conveys this random access success response message18within or as a transmission referred to as MSG B. In one or more embodiments, for instance, the random access success response message18is included in a medium access control (MAC) protocol data unit (PDU)20. In one embodiment, this MAC PDU20may be a shared message that it is addressed to multiple wireless devices, e.g., because it includes multiple random access success responses for respective ones of the wireless devices. Regardless, in some embodiments, the random access success response message18includes a contention resolution identity, a cell radio network temporary identity (C-RNTI), a timing advance (TA) command, an uplink grant, and/or a random access preamble identifier (RAPID).

According to embodiments herein, it is configurable as to whether or not the MAC PDU20carrying the random access success response message18also includes a MAC service data unit (SDU)22for a signaling radio bearer (SRB) or a data radio bearer (DRB). The MAC SDU22for an SRB may convey for instance RRC signaling, e.g., in the form of one or more RRC messages such as an RRC setup message or an RRC resume message. Alternatively or additionally, the MAC SDU22for a DRB may convey user plane data, e.g., for an early data transmission. With regard to RRC signaling, then, it is configurable as to whether or not the MAC PDU20carrying the random access success response message18includes RRC signaling.

In some embodiments, this configurability is realized by way of the network node12transmitting information24to the wireless device14. The information24may for instance comprise system information (SI), e.g., included in a System Information Block Type 1, SIB1, wherein the SIB1 indicates scheduling of one or more other System Information Blocks. In other embodiments, the information24may comprise or be included in dedicated RRC signaling. Regardless, in some embodiments, the information24(e.g., in the form of a flag26) indicates whether or not the MAC SDU22for an SRB or DRB is to be received by the wireless device14in the same MAC PDU as the MAC PDU20carrying the random access success response message18. Equivalently, the information24may indicate whether or not the MAC SDU22for an SRB or DRB is to be received by the wireless device14in a different MAC PDU than the MAC PDU20carrying the random access success response message18.

In some embodiments, the information24further indicates one or more parameter values that govern reception of the random access success response message18(or the MAC PDU20carrying the message18). For example, the one or more parameter values may include a value for a reception window within which the wireless device14must receive the random access success response message18or the MAC PDU20carrying the random access success response message18. Alternatively or additionally, the one or more parameter values may include an identity (e.g., Cell Radio Network Temporary Identity, C-RNTI, or Random Access RNTI, RA-RNTI) with which the wireless device14is to descramble a control channel on which, or a control channel search space within which, the random access success response message18or a MAC PDU20carrying the random access success response message18is to be sent. Alternatively or additionally, the information24may indicate a backoff procedure for random access by the wireless device14.

Regardless, in some embodiments, the wireless device14processes the received MAC PDU20based on the received information24. For example, in some embodiments, one or more parameter values governing random access depend on or are otherwise based on whether a MAC SDU22for an SRB or DRB is included in the received MAC PDU20. For example, in these and other embodiments, a random access response reception timer (corresponding to the reception window) has a value that depends or is based on whether the MAC SDU22for an SRB or DRB is to be received by the wireless device14in the same PAC PDU as a MAC PDU20carrying the random access success response message18. The timer value (and reception window) may be relatively larger or smaller, for instance, depending respectively on whether or not the MAC SDU22for the SRB or DRB is to be received by the wireless device14in the same PAC PDU as a MAC PDU20carrying the random access success response message18. In these and other embodiments, then, the wireless device14may determine the value for the random access response reception timer (i.e., the reception window) based on the received information24. Alternatively or additionally, a radio network temporary identity (e.g., C-RNTI) may be determined based on the received information24.

Configurability via the information24may advantageously enable the network node12to adapt inclusion of the MAC SDU22for SRB or DRB in the MAC PDU20carrying the success response18, e.g., on an as-needed basis to account for varying circumstances or conditions, or to account for a specific network deployment (e.g., in unlicensed frequency spectrum). In some embodiments, for instance, the network node12may determine whether or not the MAC SDU22for an SRB or DRB is to be included in the same MAC PDU as the MAC PDU20carrying the random access success response message18based on one or more of: a type of network deployment within which the network node12is deployed; expected radio resource control, RRC, processing delay; delay between a central unit and a distributed unit of the network node12; cell layout; a category or type of the wireless device14; whether the wireless device14is in connected mode, idle mode, or inactive mode; a random access trigger; a priority of the wireless device14or of a transmission for the wireless device14; a random access load; and/or radio resource control, RRC, processing load.

In view of the above modifications and variations,FIG.2depicts a method performed by a wireless device14in accordance with particular embodiments. The method includes receiving, from a network node12, information24indicating whether or not a medium access control, MAC, service data unit, SDU,22for a signaling radio bearer, SRB, or data radio bearer, DRB, is to be received by the wireless device14in the same MAC protocol data unit, PDU, as a MAC PDU20carrying a random access success response message18(Block200). In some embodiments, the random access success response message18indicates both a random access channel and an uplink shared channel payload were decoded successfully.

In some embodiments, the method may further include transmitting the random access channel and the uplink shared channel payload, e.g., as conveyed by msgA described herein (Block210). The method may alternatively or additionally include receiving a MAC PDU20carrying the random access success response message18(Block220). The method in some embodiments further includes processing the received MAC PDU20based on the received information24indicating whether a MAC SDU22for an SRB or DRB is included in the received MAC PDU20(Block230).

FIG.3depicts a method performed by a network node12in accordance with other particular embodiments. The method includes transmitting, from the network node12to a wireless device14, information24indicating whether or not a medium access control, MAC, service data unit, SDU,22for a signaling radio bearer, SRB, or data radio bearer, DRB, is to be received by the wireless device14in the same MAC protocol data unit, PDU, as a MAC PDU20carrying a random access success response message18(Block300). In some embodiments, the random access success response message18indicates both a random access channel and an uplink shared channel payload were decoded successfully.

In some embodiments, the method may further include receiving the random access channel and the uplink shared channel payload, e.g., as conveyed by msgA described herein (Block310). The method may alternatively or additionally include transmitting a MAC PDU20carrying the random access success response message18(Block320).

Note that the apparatuses described above may perform the methods herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory. For instance, the circuitry 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, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include 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 several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

FIG.4for example illustrates a wireless device400(e.g., wireless device14) as implemented in accordance with one or more embodiments. As shown, the wireless device400includes processing circuitry410and communication circuitry420. The communication circuitry420(e.g., radio circuitry) is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas that are either internal or external to the wireless device400. The processing circuitry410is configured to perform processing described above, e.g., inFIG.2, such as by executing instructions stored in memory430. The processing circuitry410in this regard may implement certain functional means, units, or modules.

FIG.5illustrates a network node500(e.g., network node12) as implemented in accordance with one or more embodiments. As shown, the network node500includes processing circuitry510and communication circuitry520. The communication circuitry520is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. The processing circuitry510is configured to perform processing described above, e.g., inFIG.3, such as by executing instructions stored in memory530. The processing circuitry510in this regard may implement certain functional means, units, or modules.

Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.

A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.

Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.

Additional embodiments will now be described. At least some of these embodiments may be described as applicable in certain contexts and/or wireless network types for illustrative purposes, but the embodiments are similarly applicable in other contexts and/or wireless network types not explicitly described. In the below embodiments, though, the wireless device14may be exemplified as a UE, the network node12may be exemplified as an eNB or gNB, the MAC SDU22for an SRB or DRB may be exemplified as conveying an RRC message, and the random access success response message18may be exemplified as a successRAR message. Accordingly, in the below embodiments, Option 1 corresponds to the MAC PDU20not including a MAC SDU22for an SRB or DRB, whereas Option 2 corresponds to the MAC PDU20including a MAC SDU22for an SRB or DRB.

FIG.6shows a legacy 4-step Random Access (RA) that is the baseline for both Long Term Evolution (LTE) and New Radio (NR). The user equipment (UE) in this 4-step procedure randomly selects a preamble to transmit. The UE then starts the ra-ResponseWindow in which the RA Response (RAR) message must be received. The maximum duration of the ra-ResponseWindow is 10 ms (20 ms is discussed for NR Unlicensed, NR-U).

When the eNB detects the preamble, it estimates the Timing alignment (TA) the UE should use in order to obtain uplink (UL) synchronization at the eNB. The eNB responds with the TA and a grant for Msg3 in the RAR message.

In Msg3, the UE transmits its identifier for contention resolution (part of RRC message or C-RNTI). Upon transmission of Msg3, the UE starts the ra-ContentionResolutionTimer in which Msg4 must be received. The maximum configurable duration is 64 sub frames (64 ms). The reason why this timer is longer than the ra-ResponseWindow is that it may involve RRC processing and needs to account for centralized unit (CU)/distributed unit (DU) delays, where a CU and DU may be different parts of the eNB that implement different layers of a protocol stack, e.g., the CU may terminate higher layer and/or less time-critical protocols, such as the Packet Data Convergence Protocol (PDCP) and Radio Resource Control (RRC) protocols, whereas the DU by contrast may terminate lower layer and/or more time-critical protocols, such as the Radio Link Control (RLC), Medium Access Control (MAC), and physical layer protocols.

In any event, to gNB responds by acknowledging the UE id in Msg 4. The Msg 4 gives contention resolution, i.e. only one UE's identifier will be sent even if several UEs have used the same preamble (and Msg 3) simultaneously. A UE which has successful contention resolution has successfully completed its random access procedure.

FIG.7shows an example of a MAC PDU consisting of MAC random access responses (RARs). A Medium Access Control (MAC) Protocol Data Unit (PDU) for RA Response (RAR or msg2) consists of one or more MAC subPDUs and optionally padding. Each MAC subPDU consists one of the following:a MAC subheader with Backoff Indicator only;a MAC subheader with RAPID only (i.e. acknowledgment for SI request);a MAC subheader with RAPID and MAC RAR.

A MAC subheader with Backoff Indicator consists of five header fields E/T/R/R/BI as described inFIG.8(corresponding to Figure 6.1.5-1 of 3GPP TS 38.321 v15.4.0). A MAC subPDU with Backoff Indicator (BI) only is placed at the beginning of the MAC PDU, if included. ‘MAC subPDU(s) with RAPID only’ and ‘MAC subPDU(s) with RAPID and MAC RAR’ can be placed anywhere between MAC subPDU with Backoff Indicator only (if any) and padding (if any).

A MAC subheader with RAPID consists of three header fields E/T/RAPID as described inFIG.9(corresponding to Figure 6.1.5-2 of TS 38.321 v15.4.0).

Padding is placed at the end of the MAC PDU if present. Presence and length of padding is implicit based on transport block (TB) size, size of MAC subPDU(s).

For both subheaders, the fields have the following explanations:E: The Extension field is a flag indicating if the MAC subPDU including this MAC subheader is the last MAC subPDU or not in the MAC PDU. The E field is set to “1” to indicate at least another MAC subPDU follows. The E field is set to “0” to indicate that the MAC subPDU including this MAC subheader is the last MAC subPDU in the MAC PDU;T: The Type field is a flag indicating whether the MAC subheader contains a Random Access Preamble ID or a Backoff Indicator. The T field is set to “0” to indicate the presence of a Backoff Indicator field in the subheader (BI). The T field is set to “1” to indicate the presence of a Random Access Preamble ID field in the subheader (RAPID);R: Reserved bit, set to “0”;BI: The Backoff Indicator field identifies the overload condition in the cell. The size of the BI field is 4 bits;RAPID: The Random Access Preamble IDentifier field identifies the transmitted Random Access Preamble. The size of the RAPID field is 6 bits. If the RAPID in the MAC subheader of a MAC subPDU corresponds to one of the Random Access Preambles configured for SI request, MAC RAR is not included in the MAC subPDU.

If a UE receives a RAR with the E/T/R/R/BI mac subheader but no ‘MAC subPDU(s) with RAPID and MAC RAR’ with RAPID matching its preamble transmission, the UE will back-off for a random time between 0 and a time indicated by the BI field before doing a new preamble transmission attempt, i.e. return to Random Access Resource selection (Section 5.1.2 in 38.321 v15.4.0).

A 2-step RA procedure gives much shorter latency than the ordinary 4 step RA. In the 2 step RA, the preamble (transmitted on PRACH) and a message corresponding to Message 3 (transmitted on PUSCH) in the 4 step RA are transmitted in the same or in two subsequent sub frames. The first message in the 2-step procedure is denoted Message A (MsgA). The 2-step procedure is depicted inFIG.10. In the 4-step procedure, the grant is linked to a particular preamble. The same kind of mapping will be needed in the 2-step procedure. For all different preamble ids that have been configured for the 2-step there must be a mapping to a particular PUSCH resource. The PUSCH resource may be time multiplexed, frequency multiplexed or code multiplexed.

Upon successful reception of MsgA (i.e. both the preamble and Msg 3), the eNB will respond with a TA (which by assumption should not be needed or just give very minor updates) and a Msg 4 for contention resolution. The second message in the 2-step procedure is denoted Message B (MsgB) in NR-U.

In the two step procedure, there will be a timer, hereafter called “msgB reception timer”, in which msgB must be received. It should be noted that in the 4-step procedure, there were two different timers governing when the network response must be received. In the 2-step procedure, only one is used.

In case the UE does not receive a MsgB, it would re-try with a new MsgA, similar to the action taken by the UE which does not receive a RAR in the 4-step procedure.

In case the UE is in connected mode, MsgA may contain the UEs C-RNTI and the msgB may be identified by Physical Downlink Control Channel (PDCCH) scrambled by the C-RNTI and a TA and possibly an uplink (UL) grant.

In case the UE is in idle or inactive mode, msgA may contain common control channel (CCCH) (RRC message) and the msgB may include a contention resolution MAC Control Element (CE), TA, C-RNTI and most possibly an RRC message.

One option (referred to as Option 1) is to have a “SuccessRAR” containing contention resolution MAC CE, TA, C-RNTI and possibly a RAPID. The SuccessRaAR is addressed to a single UE (not multiplexed), possibly using the RA-RNTI. After receiving the SuccessRAR, the contention resolution is complete and the gNB can send the RRC message part in a later stage. The advantage with this approach is that contention resolution can be carried out quickly, e.g. using a msgB reception timer with a setting corresponding to the ra-ResponseWindow in the 4-step procedure. This is illustrated inFIG.11. In case the RRC message is to be included, this may mean extra latency to account for RRC processing and CU/DU delays implying the need for a longer setting of msgB reception timer (corresponding to the ra-ContentionResolutionTimer in the 4-step procedure).

Another option (referred to as Option 2) would be to not send a SuccessRAR and instead wait until a complete msgB can be sent. This has the advantage that only 2 LBTs (Listen Before Talk) are needed in case of NR-U (NR Unlicensed), compared to three LBTs if the RRC part is sent in a later stage. The overall latency would be similar (since the UE needs to wait until it receives the RRC part in case of the first option) between the options, except in case the SuccessRAR would fail LBT, in which case the second option would be better. This option is illustrated inFIG.12.

There currently exist certain challenge(s). As explained above, the setting of msgB reception timer depends on which of the two options (msgB sent in two steps or in one step) is used. Both options have advantages and may be preferable in different situations. However they may be difficult to use simultaneously. For example, the second option could require a longer length of msgB reception window compared to the first option using SuccessRAR. The two options could also require different RNTIs to identify msgB (e.g. first option might use RA-RNTI but the second option would need a new RNTI capable of handling longer reception windows). Furthermore, the methods to do back off could be different under the different options, since if a back off is sent in the shorter window, it might back off a user which otherwise would receive its msgB after the shorter window has expired.

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. Some embodiments include a mechanism for how to configure the UE to know which of the options is used, e.g., by configuration.

Certain embodiments may provide one or more of the following technical advantage(s). Some embodiments enable a network to order the UE to follow a procedure consisting of a SuccessRAR and a later RRC message or a procedure where only one msgB containing both content from the SuccessRAR and the RRC message is included.

More particularly, consider now additional details of various embodiments for UEs which have transmitted a msgA in the 2-step RA procedure. Option 1 is referred to as the case where msgB in the 2-step Random Access procedure is sent in two steps: (i) A first step for contention resolution, C-RNTI assignment, and possibly TA command; and (ii) a second step consisting of an RRC message, e.g., as shown inFIG.11. Option 2 is referred to as the case where msgB in the 2-step Random Access procedure is sent in one step (message/MAC PDU), e.g., as shown inFIG.12. The msgB in this option 2 may contain contention resolution, C-RNTI assignment, possibly TA command and RRC message.

As a first embodiment, the network configures in system information (SI) which option (Option 1 or Option 2) is used. The configuration can be included in either the RACH-ConfigCommon or RACH-ConfigGeneric Information Element (IE) in System Information (SI) Block Type 1 (SIB1). The SI in some embodiments may contain a flag to indicate which option is configured and to indicate parameter values of the msgB reception window. The UE will then, based on the configuration in the SI, know which procedure to follow and which parameter values to use.

The procedures to follow for the different options may differ in terms of msgB reception window length, how to identify msgB (RNTI used for scrambling of PDCCH or PDCCH search space) and/or back off procedure.

The configuration of Option 1 or Option 2 may also consist of a mix of the two options, where option 1 is used for UEs in connected mode and option 2 is used for UEs in idle or inactive mode.

As a second embodiment, the option to use (Option 1 or Option 2) is signaled through dedicated RRC signaling. An RRC message in this case may contain a flag to indicate which option is configured and to indicate parameter values of msgB reception window. The UE will then, based on the configuration in the RRC message, know which procedure to follow and which parameter values to use. This may be used in e.g. hand over.

The network may decide on which option to use based on network deployment including expected RRC delays, CU/DU fronthaul or backhaul delay and/or cell layout.

Alternatively or additionally, the network may decide on which option to use based on UE categories and/or random access trigger. For example, UEs doing random access for high priority use cases may use one option while other UEs use the other option. This could be specified in the 3GPP standard and possibly combined with configuration in SI.

Alternatively or additionally, the selected option may be based on load, e.g. random access load, RRC processing load.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated inFIG.13. For simplicity, the wireless network ofFIG.13only depicts network1306, network nodes1360and1360b, and WDs1310,1310b, and1310c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node1360and wireless device (WD)1310are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

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

Network1306may 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 node1360and WD1310comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

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

InFIG.13, network node1360includes processing circuitry1370, device readable medium1380, interface1390, auxiliary equipment1384, power source1386, power circuitry1387, and antenna1362. Although network node1360illustrated in the example wireless network ofFIG.13may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node1360are 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 medium1380may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node1360may 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 node1360comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB's. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node1360may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium1380for the different RATs) and some components may be reused (e.g., the same antenna1362may be shared by the RATs). Network node1360may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node1360, 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 node1360.

Processing circuitry1370is 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 circuitry1370may include processing information obtained by processing circuitry1370by, 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 circuitry1370may 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 node1360components, such as device readable medium1380, network node1360functionality. For example, processing circuitry1370may execute instructions stored in device readable medium1380or in memory within processing circuitry1370. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry1370may include a system on a chip (SOC).

In some embodiments, processing circuitry1370may include one or more of radio frequency (RF) transceiver circuitry1372and baseband processing circuitry1374. In some embodiments, radio frequency (RF) transceiver circuitry1372and baseband processing circuitry1374may 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 circuitry1372and baseband processing circuitry1374may be on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry1370executing instructions stored on device readable medium1380or memory within processing circuitry1370. In alternative embodiments, some or all of the functionality may be provided by processing circuitry1370without 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 circuitry1370can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry1370alone or to other components of network node1360, but are enjoyed by network node1360as a whole, and/or by end users and the wireless network generally.

Device readable medium1380may 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 circuitry1370. Device readable medium1380may 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 circuitry1370and, utilized by network node1360. Device readable medium1380may be used to store any calculations made by processing circuitry1370and/or any data received via interface1390. In some embodiments, processing circuitry1370and device readable medium1380may be considered to be integrated.

Interface1390is used in the wired or wireless communication of signalling and/or data between network node1360, network1306, and/or WDs1310. As illustrated, interface1390comprises port(s)/terminal(s)1394to send and receive data, for example to and from network1306over a wired connection. Interface1390also includes radio front end circuitry1392that may be coupled to, or in certain embodiments a part of, antenna1362. Radio front end circuitry1392comprises filters1398and amplifiers1396. Radio front end circuitry1392may be connected to antenna1362and processing circuitry1370. Radio front end circuitry may be configured to condition signals communicated between antenna1362and processing circuitry1370. Radio front end circuitry1392may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry1392may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters1398and/or amplifiers1396. The radio signal may then be transmitted via antenna1362. Similarly, when receiving data, antenna1362may collect radio signals which are then converted into digital data by radio front end circuitry1392. The digital data may be passed to processing circuitry1370. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node1360may not include separate radio front end circuitry1392, instead, processing circuitry1370may comprise radio front end circuitry and may be connected to antenna1362without separate radio front end circuitry1392. Similarly, in some embodiments, all or some of RF transceiver circuitry1372may be considered a part of interface1390. In still other embodiments, interface1390may include one or more ports or terminals1394, radio front end circuitry1392, and RF transceiver circuitry1372, as part of a radio unit (not shown), and interface1390may communicate with baseband processing circuitry1374, which is part of a digital unit (not shown).

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

Antenna1362, interface1390, and/or processing circuitry1370may 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, antenna1362, interface1390, and/or processing circuitry1370may 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 circuitry1387may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node1360with power for performing the functionality described herein. Power circuitry1387may receive power from power source1386. Power source1386and/or power circuitry1387may be configured to provide power to the various components of network node1360in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source1386may either be included in, or external to, power circuitry1387and/or network node1360. For example, network node1360may 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 circuitry1387. As a further example, power source1386may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry1387. 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 node1360may include additional components beyond those shown inFIG.13that 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 node1360may include user interface equipment to allow input of information into network node1360and to allow output of information from network node1360. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node1360.

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

As illustrated, wireless device1310includes antenna1311, interface1314, processing circuitry1320, device readable medium1330, user interface equipment1332, auxiliary equipment1334, power source1336and power circuitry1337. WD1310may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD1310, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, NB-IoT, 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 WD1310.

Antenna1311may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface1314. In certain alternative embodiments, antenna1311may be separate from WD1310and be connectable to WD1310through an interface or port. Antenna1311, interface1314, and/or processing circuitry1320may 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 antenna1311may be considered an interface.

As illustrated, interface1314comprises radio front end circuitry1312and antenna1311. Radio front end circuitry1312comprise one or more filters1318and amplifiers1316. Radio front end circuitry1314is connected to antenna1311and processing circuitry1320, and is configured to condition signals communicated between antenna1311and processing circuitry1320. Radio front end circuitry1312may be coupled to or a part of antenna1311. In some embodiments, WD1310may not include separate radio front end circuitry1312; rather, processing circuitry1320may comprise radio front end circuitry and may be connected to antenna1311. Similarly, in some embodiments, some or all of RF transceiver circuitry1322may be considered a part of interface1314. Radio front end circuitry1312may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry1312may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters1318and/or amplifiers1316. The radio signal may then be transmitted via antenna1311. Similarly, when receiving data, antenna1311may collect radio signals which are then converted into digital data by radio front end circuitry1312. The digital data may be passed to processing circuitry1320. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry1320may 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 WD1310components, such as device readable medium1330, WD1310functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry1320may execute instructions stored in device readable medium1330or in memory within processing circuitry1320to provide the functionality disclosed herein.

As illustrated, processing circuitry1320includes one or more of RF transceiver circuitry1322, baseband processing circuitry1324, and application processing circuitry1326. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry1320of WD1310may comprise a SOC. In some embodiments, RF transceiver circuitry1322, baseband processing circuitry1324, and application processing circuitry1326may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry1324and application processing circuitry1326may be combined into one chip or set of chips, and RF transceiver circuitry1322may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry1322and baseband processing circuitry1324may be on the same chip or set of chips, and application processing circuitry1326may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry1322, baseband processing circuitry1324, and application processing circuitry1326may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry1322may be a part of interface1314. RF transceiver circuitry1322may condition RF signals for processing circuitry1320.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry1320executing instructions stored on device readable medium1330, 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 circuitry1320without 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 circuitry1320can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry1320alone or to other components of WD1310, but are enjoyed by WD1310as a whole, and/or by end users and the wireless network generally.

Processing circuitry1320may 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 circuitry1320, may include processing information obtained by processing circuitry1320by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD1310, 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 medium1330may 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 circuitry1320. Device readable medium1330may 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 circuitry1320. In some embodiments, processing circuitry1320and device readable medium1330may be considered to be integrated.

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

Auxiliary equipment1334is 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 equipment1334may vary depending on the embodiment and/or scenario.

Power source1336may, 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. WD1310may further comprise power circuitry1337for delivering power from power source1336to the various parts of WD1310which need power from power source1336to carry out any functionality described or indicated herein. Power circuitry1337may in certain embodiments comprise power management circuitry. Power circuitry1337may additionally or alternatively be operable to receive power from an external power source; in which case WD1310may 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 circuitry1337may also in certain embodiments be operable to deliver power from an external power source to power source1336. This may be, for example, for the charging of power source1336. Power circuitry1337may perform any formatting, converting, or other modification to the power from power source1336to make the power suitable for the respective components of WD1310to which power is supplied.

FIG.14illustrates 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). UE14200may be any UE identified by the 3rdGeneration Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE1400, as illustrated inFIG.14, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rdGeneration 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, althoughFIG.14is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

InFIG.14, UE1400includes processing circuitry1401that is operatively coupled to input/output interface1405, radio frequency (RF) interface1409, network connection interface1411, memory1415including random access memory (RAM)1417, read-only memory (ROM)1419, and storage medium1421or the like, communication subsystem1431, power source1433, and/or any other component, or any combination thereof. Storage medium1421includes operating system1423, application program1425, and data1427. In other embodiments, storage medium1421may include other similar types of information. Certain UEs may utilize all of the components shown inFIG.14, 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.

InFIG.14, processing circuitry1401may be configured to process computer instructions and data. Processing circuitry1401may 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 circuitry1401may 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 interface1405may be configured to provide a communication interface to an input device, output device, or input and output device. UE1400may be configured to use an output device via input/output interface1405. 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 UE1400. 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. UE1400may be configured to use an input device via input/output interface1405to allow a user to capture information into UE1400. 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.

InFIG.14, RF interface1409may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface1411may be configured to provide a communication interface to network1443a. Network1443amay 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, network1443amay comprise a Wi-Fi network. Network connection interface1411may 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 interface1411may 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.

RAM1417may be configured to interface via bus1402to processing circuitry1401to 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. ROM1419may be configured to provide computer instructions or data to processing circuitry1401. For example, ROM1419may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium1421may 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 medium1421may be configured to include operating system1423, application program1425such as a web browser application, a widget or gadget engine or another application, and data file1427. Storage medium1421may store, for use by UE1400, any of a variety of various operating systems or combinations of operating systems.

Storage medium1421may 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 medium1421may allow UE1400to 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 medium1421, which may comprise a device readable medium.

InFIG.14, processing circuitry1401may be configured to communicate with network1443busing communication subsystem1431. Network1443aand network1443bmay be the same network or networks or different network or networks. Communication subsystem1431may be configured to include one or more transceivers used to communicate with network1443b. For example, communication subsystem1431may 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.14, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter1433and/or receiver1435to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter1433and receiver1435of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem1431may 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 subsystem1431may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network1443bmay 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, network1443bmay be a cellular network, a Wi-Fi network, and/or a near-field network. Power source1413may be configured to provide alternating current (AC) or direct current (DC) power to components of UE1400.

The features, benefits and/or functions described herein may be implemented in one of the components of UE1400or partitioned across multiple components of UE1400. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem1431may be configured to include any of the components described herein. Further, processing circuitry1401may be configured to communicate with any of such components over bus1402. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry1401perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry1401and communication subsystem1431. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

FIG.15is a schematic block diagram illustrating a virtualization environment1500in 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 environments1500hosted by one or more of hardware nodes1530. 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 applications1520(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. Applications1520are run in virtualization environment1500which provides hardware1530comprising processing circuitry1560and memory1590. Memory1590contains instructions1595executable by processing circuitry1560whereby application1520is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment1500, comprises general-purpose or special-purpose network hardware devices1530comprising a set of one or more processors or processing circuitry1560, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory1590-1which may be non-persistent memory for temporarily storing instructions1595or software executed by processing circuitry1560. Each hardware device may comprise one or more network interface controllers (NICs)1570, also known as network interface cards, which include physical network interface1580. Each hardware device may also include non-transitory, persistent, machine-readable storage media1590-2having stored therein software1595and/or instructions executable by processing circuitry1560. Software1595may include any type of software including software for instantiating one or more virtualization layers1550(also referred to as hypervisors), software to execute virtual machines1540as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines1540, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer1550or hypervisor. Different embodiments of the instance of virtual appliance1520may be implemented on one or more of virtual machines1540, and the implementations may be made in different ways.

During operation, processing circuitry1560executes software1595to instantiate the hypervisor or virtualization layer1550, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer1550may present a virtual operating platform that appears like networking hardware to virtual machine1540.

As shown inFIG.15, hardware1530may be a standalone network node with generic or specific components. Hardware1530may comprise antenna15225and may implement some functions via virtualization. Alternatively, hardware1530may 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)15100, which, among others, oversees lifecycle management of applications1520.

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

In the context of NFV, virtual machine1540may 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 machines1540, and that part of hardware1530that 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 machines1540, 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 machines1540on top of hardware networking infrastructure1530and corresponds to application1520inFIG.15.

In some embodiments, one or more radio units15200that each include one or more transmitters15220and one or more receivers15210may be coupled to one or more antennas15225. Radio units15200may communicate directly with hardware nodes1530via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use of control system15230which may alternatively be used for communication between the hardware nodes1530and radio units15200.

FIG.16illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. In particular, with reference toFIG.16, in accordance with an embodiment, a communication system includes telecommunication network1610, such as a 3GPP-type cellular network, which comprises access network1611, such as a radio access network, and core network1614. Access network1611comprises a plurality of base stations1612a,1612b,1612c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area1613a,1613b,1613c. Each base station1612a,1612b,1612cis connectable to core network1614over a wired or wireless connection1615. A first UE1691located in coverage area1613cis configured to wirelessly connect to, or be paged by, the corresponding base station1612c. A second UE1692in coverage area1613ais wirelessly connectable to the corresponding base station1612a. While a plurality of UEs1691,1692are 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 station1612.

Telecommunication network1610is itself connected to host computer1630, 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 computer1630may 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. Connections1621and1622between telecommunication network1610and host computer1630may extend directly from core network1614to host computer1630or may go via an optional intermediate network1620. Intermediate network1620may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network1620, if any, may be a backbone network or the Internet; in particular, intermediate network1620may comprise two or more sub-networks (not shown).

The communication system ofFIG.16as a whole enables connectivity between the connected UEs1691,1692and host computer1630. The connectivity may be described as an over-the-top (OTT) connection1650. Host computer1630and the connected UEs1691,1692are configured to communicate data and/or signaling via OTT connection1650, using access network1611, core network1614, any intermediate network1620and possible further infrastructure (not shown) as intermediaries. OTT connection1650may be transparent in the sense that the participating communication devices through which OTT connection1650passes are unaware of routing of uplink and downlink communications. For example, base station1612may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer1630to be forwarded (e.g., handed over) to a connected UE1691. Similarly, base station1612need not be aware of the future routing of an outgoing uplink communication originating from the UE1691towards the host computer1630.

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 toFIG.17.FIG.17illustrates host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments In communication system1700, host computer1710comprises hardware1715including communication interface1716configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system1700. Host computer1710further comprises processing circuitry1718, which may have storage and/or processing capabilities. In particular, processing circuitry1718may 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 computer1710further comprises software1711, which is stored in or accessible by host computer1710and executable by processing circuitry1718. Software1711includes host application1712. Host application1712may be operable to provide a service to a remote user, such as UE1730connecting via OTT connection1750terminating at UE1730and host computer1710. In providing the service to the remote user, host application1712may provide user data which is transmitted using OTT connection1750.

Communication system1700further includes base station1720provided in a telecommunication system and comprising hardware1725enabling it to communicate with host computer1710and with UE1730. Hardware1725may include communication interface1726for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system1700, as well as radio interface1727for setting up and maintaining at least wireless connection1770with UE1730located in a coverage area (not shown inFIG.17) served by base station1720. Communication interface1726may be configured to facilitate connection1760to host computer1710. Connection1760may be direct or it may pass through a core network (not shown inFIG.17) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware1725of base station1720further includes processing circuitry1728, 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 station1720further has software1721stored internally or accessible via an external connection.

Communication system1700further includes UE1730already referred to. Its hardware1735may include radio interface1737configured to set up and maintain wireless connection1770with a base station serving a coverage area in which UE1730is currently located. Hardware1735of UE1730further includes processing circuitry1738, 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. UE1730further comprises software1731, which is stored in or accessible by UE1730and executable by processing circuitry1738. Software1731includes client application1732. Client application1732may be operable to provide a service to a human or non-human user via UE1730, with the support of host computer1710. In host computer1710, an executing host application1712may communicate with the executing client application1732via OTT connection1750terminating at UE1730and host computer1710. In providing the service to the user, client application1732may receive request data from host application1712and provide user data in response to the request data. OTT connection1750may transfer both the request data and the user data. Client application1732may interact with the user to generate the user data that it provides.

It is noted that host computer1710, base station1720and UE1730illustrated inFIG.17may be similar or identical to host computer1630, one of base stations1612a,1612b,1612cand one of UEs1691,1692ofFIG.16, respectively. This is to say, the inner workings of these entities may be as shown inFIG.17and independently, the surrounding network topology may be that ofFIG.16.

InFIG.17, OTT connection1750has been drawn abstractly to illustrate the communication between host computer1710and UE1730via base station1720, 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 UE1730or from the service provider operating host computer1710, or both. While OTT connection1750is 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 connection1770between UE1730and base station1720is 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 UE1730using OTT connection1750, in which wireless connection1770forms the last segment.

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 connection1750between host computer1710and UE1730, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection1750may be implemented in software1711and hardware1715of host computer1710or in software1731and hardware1735of UE1730, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection1750passes; 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 software1711,1731may compute or estimate the monitored quantities. The reconfiguring of OTT connection1750may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station1720, and it may be unknown or imperceptible to base station1720. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer1710's measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software1711and1731causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection1750while it monitors propagation times, errors etc.

FIG.18is 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 toFIGS.16and17. For simplicity of the present disclosure, only drawing references toFIG.18will be included in this section. In step1810, the host computer provides user data. In substep1811(which may be optional) of step1810, the host computer provides the user data by executing a host application. In step1820, the host computer initiates a transmission carrying the user data to the UE. In step1830(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 step1840(which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIG.19is 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 toFIGS.16and17. For simplicity of the present disclosure, only drawing references toFIG.19will be included in this section. In step1910of 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 step1920, 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 step1930(which may be optional), the UE receives the user data carried in the transmission.

FIG.20is 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 toFIGS.16and17. For simplicity of the present disclosure, only drawing references toFIG.20will be included in this section. In step2010(which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step2020, the UE provides user data. In substep2021(which may be optional) of step2020, the UE provides the user data by executing a client application. In substep2011(which may be optional) of step2010, 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 substep2030(which may be optional), transmission of the user data to the host computer. In step2040of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

FIG.21is 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 toFIGS.16and17. For simplicity of the present disclosure, only drawing references toFIG.21will be included in this section. In step2110(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 step2120(which may be optional), the base station initiates transmission of the received user data to the host computer. In step2130(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.

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

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.

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

Example embodiments of the techniques and apparatus described herein include, but are not limited to, the following enumerated examples:

Group A Embodiments

A1. A method performed by a wireless device, the method comprising:

receiving, from a network node, information indicating whether or not a medium access control, MAC, service data unit, SDU, for a signaling radio bearer, SRB, or data radio bearer, DRB, is to be received by the wireless device in the same MAC protocol data unit, PDU, as a MAC PDU carrying a random access success response message, wherein the random access success response message indicates both a random access channel and an uplink shared channel payload were decoded successfully.
A2. The method of embodiment A1, wherein the MAC SDU for an SRB or DRB includes or conveys radio resource control, RRC, signaling.
A3. The method of any of embodiments A1-A2, wherein the MAC SDU for an SRB or DRB includes or conveys an RRC setup message or an RRC resume message.
A4. The method of any of embodiments A1-A3, wherein the information comprises system information.
A5. The method of any of embodiments A1-A4, wherein the information is included in a System Information Block Type 1, SIB1, wherein the SIB1 indicates scheduling of one or more other System Information Blocks.
A6. The method of any of embodiments A1-A3, wherein the information is received via dedicated RRC signaling.
A7. The method of any of embodiments A1-A6, wherein the information includes a flag that indicates whether or not a MAC SDU for an SRB or DRB is to be received by the wireless device in the same MAC PDU as a MAC PDU carrying a random access success response message.
A8. The method of any of embodiments A1-A7, wherein the information further indicates one or more parameter values that govern reception of the random access success response message or a MAC PDU carrying the random access success response message.
A9. The method of embodiment A8, wherein the one or more parameter values include one or more of:a value for a reception window within which the wireless device must receive the random access success response message or a MAC PDU carrying the random access success response message; oran identity with which the wireless device is to descramble a control channel on which, or a control channel search space within which, the random access success response message or a MAC PDU carrying the random access success response message is to be sent.
A10. The method of any of embodiments A1-A7, wherein the information further indicates a backoff procedure for random access by the wireless device.
A11. The method of any of embodiments A1-A10, wherein the MAC PDU carrying the random access success response message is a shared message addressed to multiple wireless devices.
A12. The method of any of embodiments A1-A11, wherein the random access success response message indicates one or more of:a contention resolution identity;a cell radio network temporary identity, C-RNTI;a timing advance command;an uplink grant; ora random access preamble identifier.
A13. The method of any of embodiments A1-A12, further comprising transmitting the random access channel and the uplink shared channel payload.
A14. The method of any of embodiments A1-A13, further comprising receiving a MAC PDU carrying the random access success response message.
A15. The method of embodiment A14, further comprising processing the received MAC PDU based on the received information indicating whether a MAC SDU for an SRB or DRB is included in the received MAC PDU.
A16. The method of any of embodiments A1-A13, further comprising stopping a random access response reception timer upon:determining that the random access success response message has been received;receiving the random access success response message; orreceiving the MAC PDU carrying the random access success response message.
A17. The method of embodiment A16, wherein the random access response reception timer has a value that depends or is based on whether a MAC SDU for an SRB or DRB is to be received by the wireless device in the same PAC PDU as a MAC PDU carrying the random access success response message.
A18. The method of any of embodiments A16-A17, further comprising starting the random access response reception timer after an uplink shared channel transmission opportunity for transmission of a message conveying the random access channel and the uplink shared channel payload.
A19. The method of any of embodiments A1-A18, further comprising determining a value for a random access response reception timer based on the received information.
A20. The method of any of embodiments A1-A19, further comprising determining, based on the received information, a radio network temporary identity to use for receiving the random access success response message.
A21. The method of any of embodiments A1-A20, wherein one or more of:the random access channel and the uplink shared channel payload are transmitted within unlicensed frequency spectrum; orthe MAC PDU carrying the random access success response message is received within unlicensed frequency spectrum.
A22. The method of any of embodiments A1-A21, wherein the information indicates one or more conditions under which the MAC SDU for an SRB or DRB is to be received by the wireless device in the same MAC PDU as a MAC PDU carrying the random access success response message and/or indicates one or more conditions under which the MAC SDU for an SRB or DRB is not to be received by the wireless device in the same MAC PDU as a MAC PDU carrying the random access success response message.
A23. The method of any of embodiments A1-A22, wherein the information indicates one or more of:the MAC SDU for an SRB or DRB is to be received by the wireless device in the same MAC PDU as a MAC PDU carrying the random access success response message when the wireless device is in an idle mode or an inactive mode; orthe MAC SDU for an SRB or DRB is to be received by the wireless device in a different MAC PDU than a MAC PDU carrying the random access success response message when the wireless device is in a connected mode.
AA. A method performed by a wireless device, the method comprising:receiving, from a network node, information indicating whether or not a MAC PDU carrying a random access success response message includes radio resource control, RRC, signaling, wherein the random access success response message indicates both a random access channel and an uplink shared channel payload were decoded successfully.
AB. A method performed by a wireless device, the method comprising:receiving, from a network node, information indicating whether or not a message carrying a random access success response includes radio resource control, RRC, signaling, wherein the random access success response indicates both a random access channel and an uplink shared channel payload were decoded successfully.
AC. A method performed by a wireless device, the method comprising:determining, based on one or more criteria, whether or not a medium access control, MAC, service data unit, SDU, for a signaling radio bearer, SRB, or data radio bearer, DRB, is to be received by the wireless device in the same MAC protocol data unit, PDU, as a MAC PDU carrying a random access success response message, wherein the random access success response message indicates both a random access channel and an uplink shared channel payload were decoded successfully.
AD. The method of embodiment AC, wherein the one or more criteria include whether:the random access channel and the uplink shared channel payload are transmitted within unlicensed frequency spectrum; and/orthe MAC PDU carrying the random access success response message is received within unlicensed frequency spectrum
AE. The method of any of embodiments AC-AD, wherein the one or more criteria include whether the wireless device is in an idle mode, an inactive mode, or a connected mode.
AF. The method of any of the previous embodiments, further comprising:providing user data; andforwarding the user data to a host computer via the transmission to a base station.

Group B Embodiments

B1. A method performed by a network node, the method comprising:

transmitting, from the network node to a wireless device, information indicating whether or not a medium access control, MAC, service data unit, SDU, for a signaling radio bearer, SRB, or data radio bearer, DRB, is to be received by the wireless device in the same MAC protocol data unit, PDU, as a MAC PDU carrying a random access success response message, wherein the random access success response message indicates both a random access channel and an uplink shared channel payload were decoded successfully.
B2. The method of embodiment B1, wherein the MAC SDU for an SRB or DRB includes or conveys radio resource control, RRC, signaling.
B3. The method of any of embodiments B1-B2, wherein the MAC SDU for an SRB or DRB includes or conveys an RRC setup message or an RRC resume message.
B4. The method of any of embodiments B1-B3, wherein the information comprises system information.
B5. The method of any of embodiments B1-B4, wherein the information is included in a System Information Block Type 1, SIB1, wherein the SIB1 indicates scheduling of one or more other System Information Blocks.
B6. The method of any of embodiments B1-B3, wherein the information is received via dedicated RRC signaling.
B7. The method of any of embodiments B1-B6, wherein the information includes a flag that indicates whether or not a MAC SDU for an SRB or DRB is to be received by the wireless device in the same MAC PDU as a MAC PDU carrying a random access success response message.
B8. The method of any of embodiments B1-B7, wherein the information further indicates one or more parameter values that govern reception of the random access success response message or a MAC PDU carrying the random access success response message.
B9. The method of embodiment B8, wherein the one or more parameter values include one or more of:a value for a reception window within which the wireless device must receive the random access success response message or a MAC PDU carrying the random access success response message; oran identity with which the wireless device is to descramble a control channel on which, or a control channel search space within which, the random access success response message or a MAC PDU carrying the random access success response message is to be sent.
B10. The method of any of embodiments B1-B7, wherein the information further indicates a backoff procedure for random access by the wireless device.
B11. The method of any of embodiments B1-B10, wherein the MAC PDU carrying the random access success response message is a shared message addressed to multiple wireless devices.
B12. The method of any of embodiments B1-B11, wherein the random access success response message indicates one or more of:a contention resolution identity;a cell radio network temporary identity, C-RNTI;a timing advance command;an uplink grant; ora random access preamble identifier.
B13. The method of any of embodiments B1-B12, further comprising receiving the random access channel and the uplink shared channel payload.
B14. The method of any of embodiments B1-B13, further comprising transmitting a MAC PDU carrying the random access success response message.
B15. The method of embodiment B14, further comprising determining whether or not the MAC SDU for an SRB or DRB is to be received by the wireless device in the same MAC PDU as a MAC PDU carrying the random access success response message.
B16. The method of embodiment B15, wherein said determining is based on one or more of:a type of network deployment within which the network node is deployed;expected radio resource control, RRC, processing delay;delay between a central unit and a distributed unit of the network node; or cell layout.
B17. The method of any of embodiments B15-B16, wherein said determining is based on one or more of:a category or type of the wireless device;whether the wireless device is in connected mode, idle mode, or inactive mode;a random access trigger;a priority of the wireless device or of a transmission for the wireless device;a random access load; or radio resource control, RRC, processing load.
B18. The method of any of embodiments B1-B17, wherein the information further indicates a value for a random access response reception timer.
B19. The method of embodiment B18, further comprising determining the value of the random access response reception timer based on whether a MAC SDU for an SRB or DRB is included in the received MAC PDU is to be received by the wireless device in the same PAC PDU as a MAC PDU carrying the random access success response message.
B20. The method of any of embodiments B1-B19, wherein one or more of:the random access channel and the uplink shared channel payload are received within unlicensed frequency spectrum; orthe MAC PDU carrying the random access success response message is transmitted within unlicensed frequency spectrum.
B21. The method of any of embodiments B1-B20, wherein the information indicates one or more conditions under which the MAC SDU for an SRB or DRB is to be received by the wireless device in the same MAC PDU as a MAC PDU carrying the random access success response message and/or indicates one or more conditions under which the MAC SDU for an SRB or DRB is not to be received by the wireless device in the same MAC PDU as a MAC PDU carrying the random access success response message.
B22. The method of any of embodiments B1-B21, wherein the information indicates one or more of:the MAC SDU for an SRB or DRB is to be received by the wireless device in the same MAC PDU as a MAC PDU carrying the random access success response message when the wireless device is in an idle mode or an inactive mode; orthe MAC SDU for an SRB or DRB is to be received by the wireless device in a different MAC PDU than a MAC PDU carrying the random access success response message when the wireless device is in a connected mode.
BA. A method performed by a network node, the method comprising:transmitting, from the network node to a wireless device, information indicating whether or not a MAC PDU carrying a random access success response message includes radio resource control, RRC, signaling, wherein the random access success response message indicates both a random access channel and an uplink shared channel payload were decoded successfully.
AB. A method performed by a network node, the method comprising:transmitting, from the network node to a wireless device, information indicating whether or not a message carrying a random access success response includes radio resource control, RRC, signaling, wherein the random access success response indicates both a random access channel and an uplink shared channel payload were decoded successfully.
BC. The method of any of the previous embodiments, further comprising:obtaining user data; andforwarding the user data to a host computer or a wireless device.

Group C Embodiments

C1. A wireless device configured to perform any of the steps of any of the Group A embodiments.

C2. A wireless device comprising processing circuitry configured to perform any of the steps of any of the Group A embodiments.

C3. A wireless device comprising:

communication circuitry; andprocessing circuitry configured to perform any of the steps of any of the Group A embodiments.
C4. A wireless device comprising:processing circuitry configured to perform any of the steps of any of the Group A embodiments; andpower supply circuitry configured to supply power to the wireless device.
C5. A wireless device comprising:processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the wireless device is configured to perform any of the steps of any of the Group A embodiments.
C6. A user equipment (UE) comprising:an antenna configured to send and receive wireless signals;radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; anda battery connected to the processing circuitry and configured to supply power to the UE.
C7. A computer program comprising instructions which, when executed by at least one processor of a wireless device, causes the wireless device to carry out the steps of any of the Group A embodiments.
C8. A carrier containing the computer program of embodiment C7, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
C9. A network node configured to perform any of the steps of any of the Group B embodiments.
C10. A network node comprising processing circuitry configured to perform any of the steps of any of the Group B embodiments.
C11. A network node comprising:communication circuitry; andprocessing circuitry configured to perform any of the steps of any of the Group B embodiments.
C12. A network node comprising:processing circuitry configured to perform any of the steps of any of the Group B embodiments;power supply circuitry configured to supply power to the network node.
C13. A network node comprising:processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the network node is configured to perform any of the steps of any of the Group B embodiments.
C14. The network node of any of embodiments C9-C13, wherein the network node is a base station.
C15. A computer program comprising instructions which, when executed by at least one processor of a network node, causes the network node to carry out the steps of any of the Group B embodiments.
C16. The computer program of embodiment C14, wherein the network node is a base station.
C17. A carrier containing the computer program of any of embodiments C15-C16, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

Group D Embodiments

D1. A communication system including a host computer comprising:

processing circuitry configured to provide user data; anda 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 base station having a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.
D2. The communication system of the previous embodiment further including the base station.
D3. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
D4. The communication system of the previous 3 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; andthe UE comprises processing circuitry configured to execute a client application associated with the host application.
D5. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, providing user data; andat the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.
D6. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.
D7. The method of the previous 2 embodiments, 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.
D8. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform any of the previous 3 embodiments.
D9. A communication system including a host computer comprising:processing circuitry configured to provide user data; anda 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 components configured to perform any of the steps of any of the Group A embodiments.
D10. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.
D11. The communication system of the previous 2 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; andthe UE's processing circuitry is configured to execute a client application associated with the host application.
D12. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, providing user data; andat the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.
D13. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.
D14. A communication system including a host computer comprising:communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,wherein the UE comprises a radio interface and processing circuitry, the UE's processing circuitry configured to perform any of the steps of any of the Group A embodiments.
D15. The communication system of the previous embodiment, further including the UE.
D16. The communication system of the previous 2 embodiments, further including the base station, wherein the base station 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 base station.
D17. The communication system of the previous 3 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application; andthe UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
D18. The communication system of the previous 4 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; andthe 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.
D19. A method implemented in a communication system including a host computer, a base station 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 performs any of the steps of any of the Group A embodiments.
D20. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.
D21. The method of the previous 2 embodiments, further comprising:at the UE, executing a client application, thereby providing the user data to be transmitted; andat the host computer, executing a host application associated with the client application.
D22. The method of the previous 3 embodiments, further comprising:at the UE, executing a client application; andat 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.
D23. 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 base station, wherein the base station comprises a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.
D24. The communication system of the previous embodiment further including the base station.
D25. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
D26. The communication system of the previous 3 embodiments, 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.
D27. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
D28. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.
D29. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.