Hop bandwidth indication enhancement for positioning

Abstract

According to some embodiments, a method performed by a wireless device (e.g., reduced capacity (RedCap) wireless device) comprises receiving, from a network node, information indicating a common hop bandwidth for a sounding reference signal (SRS) frequency hopping pattern for positioning associated with the wireless device and transmitting an SRS according to the common hop bandwidth.

Description

Hop Bandwidth Indication Enhancement for PositioningTECHNICAL FIELD

[0001] The present disclosure generally relates to communication networks, and more specifically to hop bandwidth indication enhancement for reference signal frequency hopping for positioning.BACKGROUND

[0002] Third Generation Partnership Project (3GPP) is discussing New Radio (NR) positioning Rel-18 with the potential enhancements for reduced capacity (RedCap) positioning in which the maximal bandwidth of RedCap user equipment (UE) is 20MHz in frequency range 1 (FR1) and 100MHz in frequency range 2 (FR2). One of the potential solutions is to introduce sounding reference signal (SRS) frequency hopping for the positioning accuracy improvement of uplink-related RedCap positioning.

[0003] For SRS Tx hopping, the configuration includes:• a hop bandwidth common to all hops• a single overlap value can be configured for all hops for the SRS resource• the starting slot offset and starting symbol for the SRS resource with Tx hopping (first hop)• the starting slot offset and symbol for each of the hops following the first hop• the number of consecutive symbols in a hop common to all hops• the number of hops• UE does not expect to be configured for any hops across slot boundaries, i.e. the starting position and duration of a hop cannot exceed a slot duration

[0004] One existing parameter to indicate the legacy SRS frequency hopping pattern is common SRS (c-SRS) and more parameters of the legacy SRS frequency hopping pattern can be obtained by this parameter and Table 6.4.1.4.3-1 in TS 38.211.Table 6.4.1.4.3-1: SRS bandwidth configuration.SUMMARY

[0005] There currently exist certain challenges. For example, the maximal bandwidth supported by one RedCap UE is 20MHz in FR1 and 100MHz in FR2, and thus if the total wide bandwidth is 100MHz in FR1, then a more optimal hop bandwidth is 20MHz, while if the total wide bandwidth is 30MHz in FR1, then a more optimal hop bandwidth still may be 20MHz for simplification. Therefore, the hop bandwidth may be configured to 20MHz in FR1 and 100MHz in FR2. The bandwidth of 20MHz in FR1 corresponds to 106 resource blocks (RBs) if subcarrier spacing (SCS) is 15kHz, 51 RBs if SCS is 30kHz and 24 RBs if SCS is 60kHz, and the bandwidth of 100MHz in FR2 corresponds to 132 RBs if SCS is 60kHz and 66 RBs if SCS is 120kHz. Thus, the value range of hop bandwidth is {24, 51, 66, 106, 132} in a unit of RB. One way is to use the existing parameter c-SRS in the legacy SRS configuration to indicate this common hop bandwidth and some values in the legacy c-SRS is excluded by the network based on UE bandwidth capability. In this case, the considered values of c-SRS are {7, 12, 17, 25, 33} which corresponds to {24, 48, 64, 104, 132}, so the value range that c-SRS may indicate is not matched with the value range of the hop bandwidth.

[0006] As described above, certain challenges currently exist with hop bandwidth indication for reference signal frequency hopping. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, in particular embodiments, a first node sends information to a second node that indicates a common hop bandwidth for a reference signal frequency hopping pattern. The information may include explicit bandwidth indication (e.g., 20MHz, 100MHz) or implicit bandwidth information (e.g., 0 means 20MHz and 1 means100MHz). In some embodiments, the information comprises a joint parameter indication (e.g., subcarrier spacing (SCS) (first parameter of joint indication) plus number of resource blocks (RBs) (second parameter of joint indication)).

[0007] For example, the second parameter may indicate the value of RB number directly, or may be an index information (e.g., 0 means 24, 1 means 51, 2 means 66, 3 means 106, 4 means 132).

[0008] The second parameter may be indicated by the existing parameter c-SRS, for example, in SRS resource. For example, if c-SRS is set to 7, then the number of common hop bandwidth is 24. If c-SRS is set to 12, then the number of common hop bandwidth is 48. If c-SRS is set to 17, then the number of common hop bandwidth is 64. If c-SRS is set to 25, then the number of common hop bandwidth is 104. If c-SRS is set to 33, then the number of common hop bandwidth is 132.

[0009] The second parameter may be indicated by extension of the existing parameter c-SRS (or one extension parameter based on the legacy c-SRS) in, for example, SRS resource. For example, the value range of c-SRS (may be one new parameter that is extended based on the legacy c-SRS) is extended from (0..63) to (0..68) where• 64 means the common hop bandwidth is 24• 65 means the common hop bandwidth is 51• 66 means the common hop bandwidth is 66• 67 means the common hop bandwidth is 106• 132 means the common hop bandwidth is 132

[0010] In another example, the value range of c-SRS (may be one new parameter that is extended based on the legacy c-SRS) is extended from (0..63) to (0..66) where• 7 still means the common hop bandwidth is 24• 64 means the common hop bandwidth is 51• 65 means the common hop bandwidth is 66• 66 means the common hop bandwidth is 106• 33 still means the common hop bandwidth is 132

[0011] In another example, the value range of c-SRS is a compact value; e.g., (0..15) and thus refers to a new table that is specific for redcap device-specific bandwidth hopping configurations• 1 means the common hop bandwidth is 5• 2 means the common hop bandwidth is 10• 3 means the common hop bandwidth is 15• 4 means the common hop bandwidth is 20• 5 means the common hop bandwidth is 25

[0012] In some embodiments, c-SRS here may be changed by another parameter.

[0013] An example of extension is shown below from TS 38.331 v 17.5.0. In one specific example, the extension is extended value of the current value. In a separate example, instead of extension a compact new value is used that is specific for RedCap and maps the c-SRS indexes to RedCap specific bandwidth hopping configuration / table. In the example below, the enhancement for c-SRS is under SRS-PosResource-rl6. The enhancement may also be under SRS-Resource (i.e., enhancement for SRS-Resource).SRS-Resource SEQUENCE { srs-Resourceld SRS-ResourceId, nrof SRS-Ports ENUMERATED {portl, ports2, ports4 } , ptrs-PortIndex ENUMERATED {n0, n1 } OPTIONAL, — Need R transmissionComb CHOICE { n2 SEQUENCE { combO f f set-n2 INTEGER (0. .1) , cyclicShift-n2 INTEGER (0..7) }, n4 SEQUENCE { combO f f set-n4 INTEGER (0. .3) , cyclicShift-n4 INTEGER (0. .11) }}, resourceMapping SEQUENCE { start Position INTEGER (0. .5) , nrofSymbols ENUMERATED {nl, n2, n4}, repetitionFactor ENUMERATED {nl, n2, n4} }, f reqDomainPosition INTEGER (0. .67) , f reqDomainShi ft INTEGER (0. .268) , f reqHopping SEQUENCE { c-SRS INTEGER (0. .63) , b-SRS INTEGER (0. .3) , b-hop INTEGER (0. .3)}, groupOrSequenceHopping ENUMERATED { neither, groupHopping, sequenceHopping }, resourceType CHOICE { aperiodic SEQUENCE {}, semi-persistent SEQUENCE { periodicityAndOf f set-sp SRS- PeriodicityAndOf f set,}, periodic SEQUENCE { periodicityAndOf fset-p SRS- PeriodicityAndOf f set,}}, sequenceld INTEGER ( 0. .1023) , spatial Relation Info S RS -Spatial Relationinfo OPTIONAL, — Need RresourceMapping-rl6 SEQUENCE { start Position-rl6 INTEGER (0. .13) , nrofSymbols-rl6 ENUMERATED {nl, n2, n4} repetitionFactor-rl6 ENUMERATED {nl, n2, n4}}OPTIONAL — Need R] ] ,[ [ spatial Re lati on Info-PDC-rl7 SetupRelease {SpatialRelationInfo-PDC-rl7 } OPTIONAL, — Need M resourceMapping-rl7 SEQUENCE { start Position-rl7 INTEGER (0. .13) , nrofSymbols-rl7 ENUMERATED {nl, n2, n4, n8, n10, n12, n14}, repetitionFactor-rl7 ENUMERATED {nl, n2, n4, n5 , n6, n7, n8, n10, nl2, nl4}}OPTIONAL, — Need R partial FreqSounding- rl 7 SEQUENCE { startRBIndexFScaling-rl7 CHOICE{ startRBIndexAndFreqScalingFactor2-rl7 INTEGER (0..1) , startRBIndexAndFreqScalingFactor4-rl7 INTEGER (0..3) enables tar tRBHoppi ng- r 17 ENUMERATED {enable} OPTIONAL — Need R}OPTIONAL, — Need R transmi ssionComb-n8-rl 7 SEQUENCE { combO f f set-n8-rl7 INTEGER (0. .7) , cyclicShift-n8-rl7 INTEGER (0. .5)}OPTIONAL, — Need R srs-TCI-State-rl7 CHOICE { srs-UL-TCI-State TCI-UL-StateId-rl7, srs-DLorJointTCI -State TCI-Stateld}OPTIONAL — Need R] ] ,[ [ repetitionFactor-vl730 ENUMERATED { n3 }OPTIONAL, — Need R srs-DLorJointTCI-State-vl730 SEQUENCE { cellAndBWP-rl7 ServingCellAndBWP-Id-rl7}OPTIONAL — Cond DLor JointTCI-SRS] ]}SRS-PosResource-r16 : := SEQUENCE { srs-PosResourceId-r16 SRS-PosResourceId-rl6, transmissionComb-rl6 CHOICE { n2-rl6 SEQUENCE { combO f f set-n2-rl6 INTEGER (0..1) , cyclicShift-n2-r16 INTEGER (0..7)}, n4-rl6 SEQUENCE { combO f f set-n4-rl6 INTEGER (0. .3) , cyclicShift-n4-r16 INTEGER (0. .11)}, n8-rl6 SEQUENCE { combO f f set-n8-r!6 INTEGER (0..7) ,cyclicShift-n8-rl6 INTEGER (0..5)},}, resourceMapping-rl6 SEQUENCE { start Position-rl6 INTEGER (0..13) , nrofSymbols-rl6 ENUMERATED {nl, n2, n4, n8 , nl2 }}, freqDomainShift-rl6 INTEGER (0..268) , freqHopping-rl6 SEQUENCE { c-SRS-r16 INTEGER ( 0. .63) , c-SRS-extended-0ptionl-rl8 INTEGER (0. .16) OPTIONAL,Need R c-SRS-extended-Option2-rl8 INTEGER (64..128) OPTIONAL,Need R txhoppingConf ig-rl 8 TxhoppingConfig-rl 8OPTIONAL — Need R] ]}, groupOrSequenceHopping-rl6 ENUMERATED { neither, groupHopping, sequenceHopping }, resourceType-rl6 CHOICE { aperiodic-rl6 SEQUENCE { slotOffset-rl6 INTEGER (1. .32)OPTIONAL, — Need S}, semi-persistent-rl6 SEQUENCE { periodicityAndOf f set- sp-r 16 SRS-PeriodicityAndOf fset-rl6,[ [ periodicityAndOf fset-sp-Ext-rl6 SRS-PeriodicityAndOf f setExt-rl 6 OPTIONAL — Need R] ]}, periodic-rl6 SEQUENCE { periodicityAndOf fset-p-rl6 SRS-PeriodicityAndOf fset-rl6,[ [ periodicityAndOf fset-p-Ext-rl6 SRS-PeriodicityAndOf f setExt-rl 6 OPTIONAL — Need R] ]}}, sequence I d-rl6 INTEGER (0..65535) , spatial Re lati on InfoPos-rl6 S RS -Spatial Re lationInfoPos-rl6OPTIONAL, — Need R}TxhoppingConfig-rl8 SEQUENCE { overlapValue-rl8 INTEGER ( number of PRBs) , numberOfHops-rl8 INTEGER ( 1.. FFS ) , hopStartPositionlist-rl8 SEQUNECE ( 1. . maxNrOfHops ) of HopStartPosition, txHoppingPointA-r18 ARFCN-ValueNR,HopStartPosition-rl8 SEQUENCE { c-SRS-extended-rl8 INTEGER(0. .256) , OPTIONAL — NeedR relative StartSlotOffset-rl8 CHOICE { scsl5-rl8 INTEGER (0. .9) , scs30-rl8 INTEGER (0..19) , scs60-rl8 INTEGER (0..39) , s cs 120-rl 8 INTEGER (0. .79)}, startSymbolIndex-rl8 INTEGER (0. .13)}}

[0014] One example of the extension of the table in TS 38.211 is shown in the table below.

[0015] Another example is to introduce one new table below in TS 38.211 for the extended values of c-SRS, such as Table 1 below.Table 1.

[0016] Another example is to introduce one new table below in TS 38.211 if using the extended c-SRS, such as Table 2 below.Table 2.

[0017] Another example is to introduce one new table below in TS 38.211 to indicate the hop bandwidth in MHz via for example c-SRS or extended c-SRS, such as Table 3 below.Table 3.

[0018] In other examples, the table may indicate the information on common hop bandwidth, number ofhops, wide bandwidth and / or overlap size oftwo adjacent hops in the frequency domain.

[0019] According to some embodiments, a method performed by a wireless device comprises receiving, from a network node, information indicating a common hop bandwidth for a SRS frequency hopping pattern for positioning associated with the wireless device and transmitting an SRS according to the common hop bandwidth.

[0020] According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the wireless device methods described above.

[0021] According to some embodiments, a method performed by a network node comprises transmitting, to a wireless device, information indicating a common hop bandwidth for a SRS frequency hopping pattern for positioning associated with the wireless device and receiving an SRS from the wireless device according to the common hop bandwidth.

[0022] According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

[0023] In particular embodiments, the wireless device comprises a RedCap wireless device.

[0024] In particular embodiments, the information comprises an indication of a SCS and / or an indication of a number of RBs.

[0025] In particular embodiments, the information comprises an explicit bandwidth indication specifying at least one bandwidth range or an implicit bandwidth indication.

[0026] In particular embodiments, the information comprises a joint bandwidth indication, the joint bandwidth indication comprising a SCS parameter and a RB parameter. The RB parameter may indicate an RB value or an index that maps to an RB value. The RB parameter may beindicated by an existing c-SRS indicated in an SRS resource or by an extension of an existing c- SRS indicated in an SRS resource.

[0027] In particular embodiments, the c-SRS depends on a capability of the wireless device with respect to a number of RBs that the wireless device is configured to support. The number of RBs that the wireless device is configured to support depends on a capability of the wireless device to: support an SCS, support FR1, support FR2, and perform SRS transmission hopping with a maximum number of RBs.

[0028] In particular embodiments, a table maps the c-SRS to RBs for RedCap devices.

[0029] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless device described above.

[0030] Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network node described above.

[0031] Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments reuse the existing signaling for hop bandwidth indication of reference signal frequency hopping.BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The present disclosure may be best understood by way of example with reference to the following description and accompanying drawings that are used to illustrate embodiments of the present disclosure. In the drawings:Figure 1 shows an example of a communication system, according to certain embodiments;Figure 2 shows a user equipment (UE), according to certain embodiments;Figure 3 shows a network node, according to certain embodiments;Figure 4 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized;Figure 5 is a flowchart illustrating an example method in a wireless device, according to certain embodiments; andFigure 6 is a flowchart illustrating an example method in a network node, according to certain embodiments.DETAILED DESCRIPTION

[0033] As described above, certain challenges currently exist with hop bandwidth indication for reference signal frequency hopping. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, in particular embodiments, a first node sends information to a second node that indicates a common hop bandwidth for a reference signal frequency hopping pattern. The information may include explicit bandwidth indication (e.g., 20MHz, 100MHz) or implicit bandwidth information (e.g., 0 means 20MHz and 1 means 100MHz). In some embodiments, the information comprises a joint parameter indication (e.g., subcarrier spacing (SCS) plus number of resource blocks (RBs)).

[0034] Particular embodiments are described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0035] In some embodiments, the phrase “uplink (UL) sounding reference signal (SRS)” may be replaced by “downlink (DL) physical reference signal (PRS).” In some embodiments, the phrase “UL SRS” may be replaced by “UL reference signal”. In some embodiments, the phrase “UL SRS” may be replaced by “DL reference signal.” For example, in some embodiments, the reference signal indicated in the information indicating a common hop bandwidth for the reference signal frequency hopping pattern may be UL SRS, DL PRS, UL reference signal, and / or DL reference signal.

[0036] In some embodiments, the phrase “UL SRS frequency hopping pattern” may be replaced by “DL PRS frequency hopping pattern.” In some embodiments, the phrase “UL SRS frequency hopping pattern” may be replaced by “UL reference signal frequency hopping pattern.” In some embodiments, the phrase “UL SRS frequency hopping pattern” may be replaced by “DL reference signal frequency hopping pattern.” For example, in some embodiments, the information indicating a common hop bandwidth for a reference signal frequency hopping pattern may include UL SRS frequency pattern, DL PRS frequency hopping pattern, UL reference signal frequency hopping pattern, and / or DL reference signal frequency hopping pattern.

[0037] In some embodiments, node A may send information to node B to indicate the common hop bandwidth of (partially overlapped) UL SRS frequency hopping pattern. In some embodiments, the information may be an explicit bandwidth indication (e.g., 20MHz, 100MHz). In some embodiments, the information may be a joint bandwidth indication (e.g., SCS plus RB number). In some embodiments, the information may be an index that indicates the bandwidth information (e.g., 0 means 20MHz, 1 means 100MHz). In some embodiments, node A may be one of a network node, a gNB, a UE, a location management function (LMF), or other type of node.In some embodiments, node B may be one of a network node, a gNB, a UE, an LMF, or other type of node.

[0038] For the joint bandwidth indication, node A may send two parameters to node B according to any of the example scenarios below.

[0039] In some embodiments, the first parameter is the SCS value (e.g., 15kHz, 30kHz, 60kHz, or 120kHz) and the second parameter is the RB number (e.g., 24, 51, 66, 106, 132). The second parameter may indicate the value of RB number directly. The second parameter may be an index information where, for example, 0 indicates 24, 1 indicates 51, 2 indicates 66, 106 indicates 132.

[0040] In some embodiments, the second parameter may be indicated by the existing parameter c-SRS in, for example, SRS resource. For example, if c-SRS is set to 7, then the number of common hop bandwidth is 24. If c-SRS is set to 12, then the number of common hop bandwidth is 48. If c-SRS is set to 17, then the number of common hop bandwidth is 64. If c-SRS is set to 25, then the number of common hop bandwidth is 104. If c-SRS is set to 33, then the number of common hop bandwidth is 132.

[0041] In some embodiments, the second parameter may be indicated by the extension of existing parameter c-SRS (or one extension parameter based on the legacy c-SRS) in, for example, SRS resource. For example, the value range of c-SRS (may be a new parameter that is extended based on the legacy c-SRS) is extended from (0..63) to (0..68) where• 64 means the common hop bandwidth is 24• 65 means the common hop bandwidth is 51• 66 means the common hop bandwidth is 66• 67 means the common hop bandwidth is 106• 132 means the common hop bandwidth is 132

[0042] In another example, the value range of c-SRS (may be a new parameter (or new table) that is extended based on the legacy c-SRS) is extended from (0..63) to (0..66) where• 7 still means the common hop bandwidth is 24• 64 means the common hop bandwidth is 51• 65 means the common hop bandwidth is 66• 66 means the common hop bandwidth is 106• 33 means the common hop bandwidth is 132

[0043] In some embodiments, the configured value of c-SRS is dependent upon the UE capability on the number of resource blocks that the UE supports, which may be dependent upon UE support of SCS, FR1 , FR2, and UE capability on performing SRS Tx hopping with a maximum number of resource blocks.

[0044] In some embodiments, a table mapping the c-SRS index (values) to RBs is created specifically for redcap devices. Particular embodiments introduce a c-SRS (common hop bandwidth) indexing to RBs based upon a new table that is specific for redcap devices. This may cause the hop to be more compact saving UE power and also at the same time performing a number of hops between several RBs to give better accuracy and remove any error that may happen because of fast fading.

[0045] Figure 1 shows an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rdGeneration Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

[0046] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, 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. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0047] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 toenable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 102.

[0048] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0049] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102, and may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0050] As a whole, the communication system 100 of Figure 1 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0051] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

[0052] In some examples, the UEs 112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi -radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0053] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0054] The hub 114 may have a constant / persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the corenetwork 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 110b. In other embodiments, the hub 114 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0055] Figure 2 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0056] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to- everything (V2X). In other examples, a 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).

[0057] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 2. The level of integration between the components mayvary 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.

[0058] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 may be implemented as one or more hardware -implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).

[0059] In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include 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. An input device may allow a user to capture information into the UE 200. Examples of an input device 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, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0060] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.

[0061] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[0062] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), 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 tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and 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 as or in the memory 210, which may be or comprise a device -readable storage medium.

[0063] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and / or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0064] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, 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. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0065] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0066] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0067] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), awearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 200 shown in Figure 2.

[0068] As yet another specific example, in an loT scenario, a UE 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 UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0069] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0070] Figure 3 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication 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 NRNodeBs (gNBs)).

[0071] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may 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 RemoteRadio 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).

[0072] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, 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), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0073] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.

[0074] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

[0075] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.

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

[0077] The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318.The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0078] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).

[0079] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.

[0080] The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 310, the communication interface 306, and / or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0081] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, orintegrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0082] Embodiments of the network node 300 may include additional components beyond those shown in Figure 3 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, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.

[0083] Figure 4 is a block diagram illustrating a virtualization environment 400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, 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. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

[0084] Applications 402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0085] Hardware 404 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 408a and 408b (one or more of which may be generally referred to as VMs 408), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 406 may present a virtual operating platform that appears like networking hardware to the VMs 408.

[0086] The VMs 408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 406. Different embodiments of the instance of a virtual appliance 402 may be implemented on one or more of VMs 408, and the implementations may be made in different ways. 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.

[0087] In the context of NFV, a VM 408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 408, and that part of hardware 404 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 408 on top of the hardware 404 and corresponds to the application 402.

[0088] Hardware 404 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 404 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 410, which, among others, oversees lifecycle management of applications 402. In some embodiments, hardware 404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 412 which may alternatively be used for communication between hardware nodes and radio units.

[0089] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readablestorage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0090] FIGURE 5 is a flowchart illustrating an example method 500 in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 5 may be performed by UE 200 described with respect to FIGURE 2.

[0091] The method begins at step 512, where the wireless device (e.g., UE 200) receives, from a network node, information indicating a common hop bandwidth for a SRS frequency hopping pattern for positioning associated with the wireless device.

[0092] In particular embodiments, the wireless device comprises a RedCap wireless device. For example, RedCap and eRedCap wireless devices are described in TS 38.306 Section 4.2.22.1 and Section 4.2.21.1.

[0093] In particular embodiments, the information comprises an indication of a SCS and / or an indication of a number of RBs.

[0094] In particular embodiments, the information comprises an explicit bandwidth indication specifying at least one bandwidth range or an implicit bandwidth indication.

[0095] In particular embodiments, the information comprises a j oint bandwidth indication, the joint bandwidth indication comprising a SCS parameter and a RB parameter. The RB parameter may indicate an RB value or an index that maps to an RB value. The RB parameter may be indicated by an existing c-SRS indicated in an SRS resource or by an extension of an existing c- SRS indicated in an SRS resource.

[0096] In particular embodiments, the c-SRS depends on a capability of the wireless device with respect to a number of RBs that the wireless device is configured to support. The number of RBs that the wireless device is configured to support depends on a capability of the wireless device to: support an SCS, support FR1, support FR2, and perform SRS transmission hopping with a maximum number of RBs.

[0097] In particular embodiments, a table maps the c-SRS to RBs for RedCap devices.

[0098] In particular embodiments, the information includes any of the embodiments and examples described above.

[0099] At step 514, the wireless device transmits an SRS according to the common hop bandwidth.

[0100] Modifications, additions, or omissions may be made to method 500 of FIGURE 5. Additionally, one or more steps in the method of FIGURE 5 may be performed in parallel or in any suitable order.

[0101] FIGURE 6 is a flowchart illustrating an example method 600 in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 6 may be performed by network node 300 described with respect to FIGURE 3.

[0102] The method begins at step 612, where the network node (e.g., network node 300) transmits, to a wireless device, information indicating a common hop bandwidth for a SRS frequency hopping pattern for positioning associated with the wireless device.

[0103] Examples of the frequency hopping pattern are described in more detail with respect to FIGURE 5 and the embodiments and examples described above.

[0104] At step 614, the network node receives an SRS from the wireless device according to the common hop bandwidth.

[0105] Modifications, additions, or omissions may be made to method 600 of FIGURE 6. Additionally, one or more steps in the method of FIGURE 6 may be performed in parallel or in any suitable order.

[0106] Some example embodiments are as follows.Group A Embodiments1. A method performed by a first network node in a wireless communication network, the method comprising: communicating, to a second network node, information indicating a common hop bandwidth for a reference signal frequency hopping pattern.2. The method of the previous embodiment, wherein the reference signal comprises one or more of the following: an uplink sounding reference signal (SRS); or a downlink SRS.3. The method of any of the previous embodiments, wherein the information comprises an explicit bandwidth indication specifying at least one bandwidth ranges.4. The method of any of the previous embodiments, wherein the information comprises an implicit bandwidth indication.5. The method of any of the previous embodiments, wherein the information comprises a joint bandwidth indication, the joint bandwidth indication comprising subcarrier spacing (SCS) and resource block (RB) parameters.6. The method of the previous embodiment, wherein the RB parameter indicates a value of the RB or an index that is mapped to the RB.7. The method of the embodiment 5, wherein the RB parameter is indicated by an existing common SRS (c-SRS) indicated in a SRS resource.8. The method of the embodiment 5, wherein the RB parameter is indicated by an extension of an existing common SRS (c-SRS) indicated in a SRS resource.9. The method of any one of the embodiments 7 and 8, wherein the c-SRS is dependent on the first network node capability on a number of RBs that the first network node is configured to support, wherein the number of RBs that the first network node is configured to support is dependent on the first network node capability to support SCS, frequency range 1 (FR1), frequency range 2 (FR2), and on performing SRS transmission hopping with a maximum number of RBs.10. The method of any one of the embodiments 7 and 8, wherein a table mapping the c-SRS index to RBs is created for reduced capacity devices.11. The method of any of the previous embodiments, wherein the information comprises an index which indicates the common hop bandwidth.12. The method of any of the previous embodiments, wherein the first network node is a user equipment (UE), a gNB, or a location management function (LMF).13. The method of any of the previous embodiments, wherein the second network node is a user equipment (UE), a gNB, or a location management function (LMF).14. A method performed by a wireless node, the method comprising: any of the wireless device steps, features, or functions described above, either alone or incombination with other steps, features, or functions described above.15. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above.Group B Embodiments16. A method performed by a second network node in a wireless communication network, the method comprising: receiving, from a first network node, information indicating a common hop bandwidth for a reference signal frequency hopping pattern.17. A method performed by a network node, the method comprising: any of the network node steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.18. The method of the previous embodiment, further comprising one or more additional network node steps, features or functions described above.Group C Embodiments19. A user equipment for indicating a common hop bandwidth for a reference signal frequency hopping pattern, comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.20. A network node for receiving an indication of a common hop bandwidth for a reference signal frequency hopping pattern, the 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 processing circuitry.21. A user equipment (UE) for indicating a common hop bandwidth for a reference signal frequency hopping pattern, the 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; and a battery connected to the processing circuitry and configured to supply power to the UE.

[0107] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

[0108] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0109] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.

Claims

Claims1. A method performed by a wireless device, the method comprising: receiving (512), from a network node, information indicating a common hop bandwidth for a sounding reference signal (SRS) frequency hopping pattern for positioning associated with the wireless device; and transmitting (514) an SRS according to the common hop bandwidth.

2. The method of claim 1, wherein the wireless device comprises a reduced capacity (RedCap) wireless device.

3. The method of any one of claims 1-2, wherein the information comprises an indication of a subcarrier spacing (SCS).

4. The method of any one of claims 1-3, wherein the information comprises an indication of a number of resource blocks (RBs).

5. The method of any one of claims 1-4, wherein the information comprises an explicit bandwidth indication specifying at least one bandwidth range.

6. The method of any one of claims 1-4, wherein the information comprises an implicit bandwidth indication.

7. The method of any one of claims 1-6, wherein the information comprises a joint bandwidth indication, the joint bandwidth indication comprising a subcarrier spacing (SCS) parameter and a resource block (RB) parameter.

8. The method of claim 7, wherein the RB parameter indicates an RB value or an index that maps to an RB value.

9. The method of claim 7, wherein the RB parameter is indicated by an existing common SRS (c-SRS) indicated in an SRS resource.

10. The method of claim 7, wherein the RB parameter is indicated by an extension of anexisting common SRS (c-SRS) indicated in an SRS resource.

11. The method of any one of claims 9-10, wherein the c-SRS depends on a capability of the wireless device with respect to a number of RBs that the wireless device is configured to support: wherein the number of RBs that the wireless device is configured to support depends on a capability of the wireless device to: support an SCS, support frequency range 1 (FR1), support frequency range 2 (FR2), and perform SRS transmission hopping with a maximum number of RBs.

12. The method of any one of claims 9-10, wherein a table maps the c-SRS to RBs for RedCap devices.

13. A wireless device (200) comprising processing circuitry (202) operable to: receive, from a network node (300), information indicating a common hop bandwidth for a sounding reference signal (SRS) frequency hopping pattern for positioning associated with the wireless device; and transmit an SRS according to the common hop bandwidth.

14. The wireless device of claim 13, wherein the wireless device comprises a reduced capacity (RedCap) wireless device.

15. The wireless device of any one of claims 13-14, wherein the information comprises an indication of a subcarrier spacing (SCS).

16. The wireless device of any one of claims 13-15, wherein the information comprises an indication of a number of resource blocks (RBs).

17. The wireless device of any one of claims 13-16, wherein the information comprises an explicit bandwidth indication specifying at least one bandwidth range.

18. The wireless device of any one of claims 13-16, wherein the information comprises animplicit bandwidth indication.

19. The wireless device of any one of claims 13-18, wherein the information comprises a joint bandwidth indication, the joint bandwidth indication comprising a subcarrier spacing (SCS) parameter and a resource block (RB) parameter.

20. The wireless device of claim 19, wherein the RB parameter indicates an RB value or an index that maps to an RB value.

21. The wireless device of claim 19, wherein the RB parameter is indicated by an existing common SRS (c-SRS) indicated in an SRS resource.

22. The wireless device of claim 19, wherein the RB parameter is indicated by an extension of an existing common SRS (c-SRS) indicated in an SRS resource.

23. The wireless device of any one of claims 21-22, wherein the c-SRS depends on a capability of the wireless device with respect to a number of RBs that the wireless device is configured to support: wherein the number of RBs that the wireless device is configured to support depends on a capability of the wireless device to: support an SCS, support frequency range 1 (FR1), support frequency range 2 (FR2), and perform SRS transmission hopping with a maximum number of RBs.

24. The wireless device of any one of claims 21-22, wherein a table maps the c-SRS to RBs for RedCap devices.

25. A method performed by a network node, the method comprising: transmitting (612), to a wireless device, information indicating a common hop bandwidth for a sounding reference signal (SRS) frequency hopping pattern for positioning associated with the wireless device; and receiving (614) an SRS from the wireless device according to the common hop bandwidth.

26. The method of claim 25, wherein the wireless device comprises a reduced capacity (RedCap) wireless device.

27. The method of any one of claims 25-26, wherein the information comprises an indication of a subcarrier spacing (SCS).

28. The method of any one of claims 25-27, wherein the information comprises an indication of a number of resource blocks (RBs).

29. The method of any one of claims 25-28, wherein the information comprises an explicit bandwidth indication specifying at least one bandwidth range.

30. The method of any one of claims 25-28, wherein the information comprises an implicit bandwidth indication.

31. The method of any one of claims 25-30, wherein the information comprises a joint bandwidth indication, the joint bandwidth indication comprising a subcarrier spacing (SCS) parameter and a resource block (RB) parameter.

32. The method of claim 31, wherein the RB parameter indicates an RB value or an index that maps to an RB value.

33. The method of claim 31, wherein the RB parameter is indicated by an existing common SRS (c-SRS) indicated in an SRS resource.

34. The method of claim 31, wherein the RB parameter is indicated by an extension of an existing common SRS (c-SRS) indicated in an SRS resource.

35. The method of any one of claims 33-34, wherein the c-SRS depends on a capability of the wireless device with respect to a number of RBs that the wireless device is configured to support: wherein the number of RBs that the wireless device is configured to support depends on a capability of the wireless device to: support an SCS,support frequency range 1 (FR1), support frequency range 2 (FR2), and perform SRS transmission hopping with a maximum number of RBs.

36. The method of any one of claims 33-34, wherein a table maps the c-SRS to RBs for RedCap devices.

37. A network node (300) comprising processing circuitry (302) operable to: transmit, to a wireless device (200), information indicating a common hop bandwidth for a sounding reference signal (SRS) frequency hopping pattern for positioning associated with the wireless device; and receive an SRS from the wireless device according to the common hop bandwidth.

38. The network node of claim 37, wherein the wireless device comprises a reduced capacity (RedCap) wireless device.

39. The network node of any one of claims 37-38, wherein the information comprises an indication of a subcarrier spacing (SCS).

40. The network node of any one of claims 37-39, wherein the information comprises an indication of a number of resource blocks (RBs).

41. The network node of any one of claims 37-40, wherein the information comprises an explicit bandwidth indication specifying at least one bandwidth range.

42. The network node of any one of claims 37-40, wherein the information comprises an implicit bandwidth indication.

43. The network node of any one of claims 37-42, wherein the information comprises a joint bandwidth indication, the joint bandwidth indication comprising a subcarrier spacing (SCS) parameter and a resource block (RB) parameter.

44. The network node of claim 43, wherein the RB parameter indicates an RB value or an index that maps to an RB value.

45. The network node of claim 43, wherein the RB parameter is indicated by an existing common SRS (c-SRS) indicated in an SRS resource.

46. The network node of claim 43, wherein the RB parameter is indicated by an extension of an existing common SRS (c-SRS) indicated in an SRS resource.

47. The network node of any one of claims 45-46, wherein the c-SRS depends on a capability of the wireless device with respect to a number of RBs that the wireless device is configured to support: wherein the number of RBs that the wireless device is configured to support depends on a capability of the wireless device to: support an SCS, support frequency range 1 (FR1), support frequency range 2 (FR2), and perform SRS transmission hopping with a maximum number of RBs.

48. The network node of any one of claims 45-46, wherein atable maps the c-SRS to RBs for RedCap devices.

Images