Methods, apparatus and computer-readable media related to positioning in a communication network

Abstract

A method is performed by a second network node. The method comprises receiving a connection resume message from a user equipment, requesting resumption of a connection between the user equipment and a communication network. The connection resume message comprises an indication that a cause for resuming the connection is to configure SRS for positioning or to request activation of a configuration for SRS for positioning. The method further comprises transmitting, to a first network node, which is an anchor network node for the connection, a request message to retrieve a context for the user equipment. The request message comprises an indication that the cause for resuming the connection is to configure SRS for positioning or to request activation of a configuration for SRS for positioning. The method further comprises receiving, from the first network node, a response message comprising at least part of the context for the user equipment. The at least part of the context for the user equipment comprises at least part of an SRS configuration for positioning for the user equipment.

Description

METHODS, APPARATUS AND COMPUTER-READABLE MEDIA RELATED TO POSITIONING IN A COMMUNICATION NETWORKTECHNICAL FIELD

[0001] Embodiments of the present disclosure relate to communication networks, and particularly to methods, apparatus and computer-readable media related to positioning in communication networks.BACKGROUND

[0002] In the 3rd Generation Partnership Project (3GPP) RAN#99, the Work Item (WI) on "Expanded and Improved NR Positioning" was agreed in RP-230328, which includes the following objectives (most relevant portions underlined for emphasis):The objective of this work item is to specify solutions to introduce sidelink ranging / positioning, to introduce integrity for Radio Access Technology (RAT) -dependent positioning methods, to enable Low-Power High- Accuracy Positioning (LPHAP) use-case 6 defined in Technical Standard (TS) 22.104, to improve positioning accuracy, and to introduce support of positioning for Reduced Capability (RedCap) User Equipment (UEs).The specific objectives of this work item are:• [ . ]• Specify enhancements for enabling LPHAP use-case 6 as defined in TS 22.104 including: o Extending Extended Discontinuous Reception (eDRX) beyond 10.24s in RRC INACTIVE state towards meeting the battery life requirement for LPHAP [RAN2, RAN3, RAN4]■ Positioning-specific enhancement for eDRX cycle beyond 10.24s to be defined as part of Rel-18 WI on expanded and improved NR positioning.• NOTE: Work on this objective should be coordinated with that in Release 18 (Rel-18) WI on eRedCap. Towards this, the feature of extending eDRX cycle beyond 10.24s should be defined as part of Rel-18 WI on eRedCap.■ NOTE: Inputs from RANI as necessary may be facilitated via Liaison Statements (LSs) o For Uplink (UL) and Downlink (DL) +UL positioning for UEs in RRC IN ACTIVE state, specify Sounding Reference Signal (SRS) configuration enhancements based on SRS positioning validity area to avoid frequent Radio Resource Control (RRC) connection for SRS (re)configuration [RAN2, RANI, RAN3],■ SRS for positioning configurations in multiple cells [RAN2, RANI],• Note: Details including issues such as interference, timing advance, spatial relation information, pathloss reference and common SRS parameters across multiple cells can be further discussed during normative work.• Pre-configuration of one or multiple SRS for positioning configurations [RAN2. RAN31,• SRS for positioning activation / request procedure(s) [RAN2, RANI], o Specify solutions for DL Positioning Reference Signal (PRS) measurements for a UE in RRC IDLE state and reporting of the measurements in RRC CONNECTED state [RAN2], o Specify solutions for alignment between eDRX and PRS configurations [RAN2], o Specify corresponding new core requirements, as well as identifying and specifying the impact on the existing RAN4 specification, including Radio Resource Management (RRM) measurements and procedures [RAN4],• [ . ]• Define extensions of signalling, protocol, and procedure for New Radio (NR) positioning enhancement, as needed for the above objectives [RAN3],

[0003] Pre-configuration of positioning SRS is characterized by a Validity Area (VA). The relevant RANI and RAN2 agreements are copied below:Agreements:• When configured with SRS configuration along with SRS validity area, if the UE reselects to another cell within the SRS validity area during SRS transmission, the UE continues the SRS transmission, subject to validation for SRS transmission.• Wait for RANI progress for the validation of SRS transmission with issues such as interference, timing advance and spatial relation information, etc.Agreements:• RAN2 assume when the UE reselects out of the positioning validity area during SRS transmission, the UE may send an RRC message to the network for SRS configuration request.• LS to RAN3 to confirm this.

[0004] According to TS 38.305 V18.0.0, when the UE reselects in another cell within the VA, it continues the SRS transmission with only one SRS configuration, subject to the validation by the (new) serving gNB (relevant portions underlined for emphasis):7.9 Positioning in RRC INACTIVE statePositioning may be performed when a UE is in RRC INACTIVE state. Any uplink Location Service (LCS) or Long-Term Evolution (LTE) Positioning Protocol (LPP) message can be transported in RRC INACTIVE state. If the UE initiated data transmission using UL Small Data Transmission (SDT), the network can send DL LCS, LPP, RRC Release message (e.g. to configure SRS for UL positioning, if it is supported) and Semi-Persistent (SP) Positioning SRS Activation / Deactivation Medium Access Control (MAC) Control Element (CE) to the UE without the need of state transition.Periodic and Semi-persistent UL-SRS transmission for positioning can be supported in RRC INACTIVE. The UL-SRS for positioning configuration in RRC INACTIVE state may be associated with an SRS Validity Area. The SRS Validity Area contains a list of cells in which the SRS for positioning configuration in RRC INACTIVE state is valid. When configured with an SRS configuration for positioning along with SRS Validity Area, if the UE reselects to another cell within the SRS Validity Area during SRS transmission, the UE continues the SRS transmission, subject to validation for SRStransmission as specified in TS 38,321

[0039] and TS 38,331

[0014] , When the UE reselects out of the SRS for positioning Validity Area during SRS transmission, the UE may send an "RRC Resume Request" message to the network for SRS configuration request.NOTE: Aperiodic UL-SRS transmission for positioning is not supported inRRC INACTIVE.The SRS for positioning configuration in RRC INACTIVE state may be pre-configured in the target device. The target device may send an "RRC Resume Request" message to the network when a configured periodic or triggered location event has been detected to request activation of the pre-configured SRS for positioning. For preconfigured multiple SRS configurations, the UE is configured with only one SRS for positioning configuration for each validity area.

[0005] Hence for preconfigured SRS, there can be multiple validity areas, and only one SRS configuration for each area.

[0006] The SRS configuration for VA is defined in TS 38.331 V18.0.0, with two configType as below (relevant portions underlined for emphasis):SRS-PosRRC-InactiveValidityAreaConfig-rl8 ::= SEQUENCE ( configType-rl8 ENUMERATED [preconfig, non-preconfig]. srs-PosConfigValidityArea-rl 8 SEQUENCE (SIZE(1..maxNrOfCellsInVA- r!8)) OF Cellldentity, srs-PosConfigNUL-r!8 SRS-PosConfig-rl7OPTIONAL, - Need R srs-PosConfigSUL-r!8 SRS-PosConfig-rl7OPTIONAL, - Need R bwp-NUL-r!8 BWP OPTIONAL,— Need S bwp-SUL-rl8 BWP OPTIONAL,— Need S areaValidityTA-Config-rl8 SetupRelease { AreaValidityTA-Config-rl8} OPTIONAL, - Need Msrs-PosRRC-AggBW-InactiveConfigList-rl8 SetupRelease { SRS-PosRRC-AggBW-InactiveConfigList-rl8 } OPTIONAL, -- Need M srs-PosResSetLinkedForAggBWInactiveList-rl8 SetupRelease { SRS-PosResSetLinkedForAggBWInactiveList-rl8 } OPTIONAL, — Need M srs-PosHyperSFN-Index-r!8 ENUMERATED {evenO, oddl}OPTIONAL, -Need SSUMMARY

[0007] There currently exist certain challenge(s).

[0008] Currently, the procedure to support multiple pre-configured SRS during UE mobility is not supported and RAN3 have not discussed it yet. According to TS 38.305 V18.0.0, when the UE reselects, it triggers RRC resume request, with the new cause value introduced by RAN2. See the following extract (relevant portions underlined for emphasis):

[0009] The following extract from TS 38.331 V18.0.0 is also relevant:

[0010] Thus, when a UE resumes its connection outside the VA and has active SRS transmission, it sends a RRC resume message to the new gNB with resumeCause set to “srs- PosConfigOrActivationReq”. The Location Management Function (LMF) is notified of the cell change outside of the V A, and a new SRS configuration can be performed between the N etwork (NW) and UE.

[0011] However, for pre-configured SRS, a UE may send the resume message and / or the ResumeCause to a Receiving gNB within the VA, so that the Receiving gNB can activate the SRS pre-configuration for the UE. Currently, however, there is no signalling over Xn that allows for the Receiving gNB to be aware of UE’s preconfigured SRS configuration for the VA for this specific UE.

[0012] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.

[0013] In one aspect of the disclosure, when the Receiving gNB receives the UE RRC Resume cause, it sends the RETRIEVE UE CONTEXT REQUEST message over Xn to the anchor gNB, so that the anchor gNB provides the pre-configured SRS configuration over Xn to the receiving gNB via the RETRIEVE UE CONTEXT RESPONSE message. The anchor gNB may release all pre-configured SRS configurations after sending the RETRIEVE UE CONTEXT RESPONSE message to the receiving gNB.

[0014] Additionally or alternatively, in case of small data transmission with non-anchor relocation (i.e., the context of the UE stays at the old gNB), when the receiving gNB sends the RETRIEVE UE CONTEXT REQUEST message over Xn, the anchor gNB provides the preconfigured SRS configuration over Xn to the receiving gNB via the PARTIAL UE CONTEXT TRANSFER message. The anchor gNB keeps all pre-configured SRS configurations after sending the PARTIAL UE CONTEXT TRANSFER message to the receiving gNB.

[0015] One or more of the embodiments disclosed herein may involve the addition of a first new Information Element (IE) in the Positioning Information IE, in the UE ContextInformation - Retrieve UE Context Response IE contained in the RETRIEVE UE CONTEXT RESPONSE message indicating the UE’s preconfigured SRS configuration associated to the VA.

[0016] Additionally or alternatively, one or more of the embodiments disclosed herein may involve the addition of a second new IE in the Partial UE Context Information for Positioning IE contained in the RETRIEVE UE CONTEXT RESPONSE message indicating the UE’s preconfigured SRS configuration associated to the VA.

[0017] In a first aspect of the disclosure, there is disclosed a method performed by a second network node. The method comprises receiving a connection resume message from a user equipment, requesting resumption of a connection between the user equipment and a communication network. The connection resume message comprises an indication that a cause for resuming the connection is to configure SRS for positioning or to request activation of a configuration for SRS for positioning. The method further comprises transmitting, to a first network node, which is an anchor network node for the connection, a request message to retrieve a context for the user equipment. The request message comprises an indication that the cause for resuming the connection is to configure SRS for positioning or to request activation of a configuration for SRS for positioning. The method further comprises receiving, from the first network node, a response message comprising at least part of the context for the user equipment. The at least part of the context for the user equipment comprises at least part of an SRS configuration for positioning for the user equipment.

[0018] In a second aspect of the disclosure, there is disclosed a method performed by a first network node. The method comprises receiving, from a second network node, a request message to retrieve a context for a connection between a user equipment and a communication network. The second network node has received a connection resume request from the user equipment. The first network node is an anchor network node for the connection. The request message comprises an indication that a cause for resuming the connection is to configure SRS for positioning or to request activation of a configuration for SRS for positioning. The method further comprises transmitting, to the second network node, a response message comprising at least part of the context for the user equipment. The at least part of the context for the user equipment comprises at least part of an SRS configuration for positioning for the user equipment.

[0019] In a third aspect of the disclosure, there is disclosed a method performed by a user equipment. The method comprises transmitting a connection resume message to a network node of a communication network. Responsive to one or more criteria being met, theconnection resume message comprises an indication that a cause for resuming a connection with the communication network is to configure SRS for positioning or to request activation of a configuration for SRS for positioning. The one or more criteria comprise a first criterion that the user equipment receives, from the network node, an indication that the user equipment is permitted to include the indication in the connection resume message.

[0020] In a fourth aspect of the disclosure, there is provided a second network node comprising processing circuitry configured to cause the second network node to perform a method according to embodiments of the first aspect.

[0021] In a fifth aspect of the disclosure, there is provided a second network node configured to perform a method according to embodiments of the first aspect.

[0022] In a sixth aspect of the disclosure, there is provided a first network node comprising processing circuitry configured to cause the first network node to perform a method according to embodiments of the second aspect.

[0023] In a seventh aspect of the disclosure, there is provided a first network node configured to perform a method according to embodiments of the second aspect.

[0024] In an eighth aspect of the disclosure, there is provided a UE comprising processing circuitry configured to cause the UE to perform a method according to embodiments of the third aspect.

[0025] In a ninth aspect of the disclosure, there is provided a UE configured to perform a method according to embodiments of the third aspect.

[0026] Certain embodiments may provide one or more technical advantage(s), such as enabling the UE to continue a LPHAP session in the validity area in another cell, when the SRS configuration is preconfigured by another gNB. The teachings of certain embodiments may reduce power consumption for positioning (particularly when the UE is mobile between cells), and may also increase the accuracy of positioning.BRIEF DESCRIPTION OF THE DRAWINGS

[0027] For a better understanding of the embodiments of the present disclosure, and to show how it may be put into effect, reference will now be made, by way of example only, to the accompanying drawings, in which:

[0028] Fig. 1 is a signalling diagram showing a procedure for anchor relocation with preconfigured SRS signalling over Xn.

[0029] Fig. 2 is a signalling diagram showing a procedure for partial anchor relocation with preconfigured SRS signalling over Xn.

[0030] Fig. 3 is a flow chart illustrating a method in accordance with some embodiments;

[0031] Fig. 4 is a flow chart illustrating a method in accordance with some embodiments;

[0032] Fig. 5 is a flow chart illustrating a method in accordance with some embodiments;

[0033] Fig. 6 shows an example of a communication system in accordance with some embodiments;

[0034] Fig. 7 shows a UE in accordance with some embodiments;

[0035] Fig. 8 shows a network node in accordance with some embodiments; and

[0036] Fig. 9 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.DETAILED DESCRIPTION

[0037] Some of the embodiments contemplated herein will now be 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.

[0038] Figure 1 illustrates a case of anchor relocation with preconfigured SRS signalling over Xn. The signalling involves a UE 102, a receiving node 104, an anchor node 106, and an LMF 108.

[0039] In this scenario, the case is considered where the UE 102 is pre-configured with SRS configuration for a VA, and resumes its connection in anode which forms part of the VA (e.g., serves a cell within the VA). The UE 102 performs an RRC resume procedure with the receiving node 104, as described in step 120 of Figure 1. At step 110, the LMF 108 sends, to the anchor node 106, a POSITIONING INFORMATION REQUEST with LPHAP information and type of configuration (immediate or pre-configuration) including recommended SRS characteristics, sequence ID, etc.

[0040] At step 112, if deferred configuration, the anchor node 106 determines a list of preconfigured SRS configurations and preconfigures the UE 102.

[0041] At step 114, the anchor node 106 sends, to the UE 102, an RRC Release message with one preconfigured SRS.

[0042] At step 116, the anchor node 106 sends, to the LMF 108, a POSITIONING INFORMATION RESPONSE with configured SRS configuration for LPHAP.

[0043] At step 118, the LMF 108 sends, to the receiving node 104, an SRS Information Reservation Notification with SRS resources to reserve.

[0044] At step 120, the UE 102 sends, to the receiving node 104, an RRC Resume with srs-PosConfigOrActivationReq.

[0045] At step 122, the receiving node 104 sends, to the anchor node 106, a RETRIEVE UE CONTEXT REQUEST with new RRC resume cause. That is, in one embodiment, the Receiving gNB 104 (i.e., the network node to which the UE 102 transmits the RRC Resume message) signals an activation request related to SRS pre-configuration for the UE 102 in VA to the Anchor gNB 106 in Xn RETRIEVE UE CONTEXT REQUEST message (see step 122 in Figure 1).

[0046] At step 124, the anchor node 106 performs direct context relocation.

[0047] At step 126, the anchor node 106 sends, to the receiving node 104, a RETRIEVE UE CONTEXT RESPONSE message with preconfigured SRS configuration.

[0048] That is, in one embodiment, the old node (e.g., the Anchor gNB 106) provides the preconfigured SRS configuration for validity area to be activated by the new node (e.g., the Receiving gNB 104) via Xn message, in the Positioning Information IE, in the UE Context Information - Retrieve UE Context Response IE contained in the RETRIEVE UE CONTEXT RESPONSE message (see step 126 in Figure 1).

[0049] At step 128, the receiving node 104 sends, to the UE 102, an RRC Release with preconfigured SRS.

[0050] At step 130, the receiving node 104 sends, to the LMF 108, a POSITIONING INFORMATION UPDATE message.

[0051] The following sets out one possible implementation in TS 38.423 V18.0.0 with new additions underlined:9.2.3.168 Positioning InformationThis IE contains positioning information that assists in the SRS configuration of the UE.

[0052] In one embodiment, when the Receiving gNB 104 receives the SRS Positioning RRC Inactive Validity Area configuration from the Anchor gNB 106, the Receiving gNB 104 considers that it can use and activate this SRS pre-configuration for the resuming UE 102 when sending the RRC message to UE 102.

[0053] Figure 2 illustrates a case of partial anchor relocation with preconfigured SRS signalling over Xn. The signalling involves a UE 202, a receiving node 204, an anchor node 206, and an LMF 208. In this scenario, it is considered that the 202 has been configured with one immediate SRS configuration (e.g., not-preconfigured). The UE resumes outside of the VA and sends the RRC resume message as illustrated in step 220 of Figure 2.

[0054] At step 210, the LMF 208 sends, to the anchor node 206, a POSITIONING INFORMATION REQUEST with LPHAP information and type of configuration (immediate or pre-configuration) including recommended SRS characteristics, sequence ID, etc.

[0055] At step 212, if immediate configuration, the anchor node 206 determines one SRS configuration for the VA.

[0056] At step 214, the anchor node 206 sends, to the UE 202, an RRC Release message with one configured SRS.

[0057] At step 216, the anchor node 206 sends, to the LMF 208, a POSITIONING INFORMATION RESPONSE with configured SRS configuration for LPHAP.

[0058] At step 218, the LMF 208 sends, to the receiving node 204, an SRS Information Reservation Notification with SRS resources to reserve.

[0059] At step 220, the UE 202 sends, to the receiving node 204, an RRC Resume with srs-PosConfigOrActivationReq.

[0060] At step 222, the receiving node 204 sends, to the anchor node 206, a RETRIEVE UE CONTEXT REQUEST with new RRC Resume Cause.

[0061] However, the Anchor gNB decides not to relocate the context (i.e. , keep the UE context). That is, at step 224, the anchor node 206 performs partial context relocation. In such a scenario, the anchor gNB provides, at step 226, the LPHAP SRS characteristics to the new Receiving gNB, so that the Receiving gNB decides the new LPHAP SRS configuration to adopt.

[0062] In one embodiment, the old node (e.g., the Anchor node 206) provides the LPHAP SRS characteristics to the new node (e.g., the Receiving node 204) via Xn message, in the PARTIAL UE CONTEXT TRANSFER message (see step 226 of Figure 2). The information may include indications of one or more of:• SRS-PosResourceSet• srs-PosResourceSetld• srs-PosResourceldList• resourceType• SRS-PosResource• srs-PosResourceld• transmissionComb• resourceMapping• freqDomainShift• freqHopping• groupOrSequenceHopping• resourceType• The "Pathloss Reference Information" and "Spatial Relation Information" of an SRS for positioning configuration may or may not be included in an SRS for positioning pre-configuration.

[0063] At step 228, the receiving node 204 sends, to the anchor node 206, a PARTIAL UE CONTEXT TRANSFER ACKNOWLEDGE with confirmed configured SRS configuration.

[0064] At step 230, the anchor node 206 sends, to the receiving node 204, a RETRIEVE UE CONTEXT FAILURE.

[0065] At step 232, the receiving node 204 sends, to the UE 202, an RRC Release with new configured SRS.

[0066] The following sets out one possible implementation in TS 38.423 V18.0.0 with new additions underlined:9.1.1.17 PARTIAL UE CONTEXT TRANSFERThis message is sent by the old NG-RAN node to transfer part of the UE Context to the new NG-RAN node.Direction: old NG-RAN node —> new NG-RAN node.

[0067] In one embodiment, when the new (receiving) gNB receives the characteristics for SRS Positioning RRC Inactive Validity Area configuration from the old (anchor) gNB, if it decides an SRS configuration for VA, it configures and provides it to the anchor gNB via the PARTIAL UE CONTEXT TRANSFER ACKNOWLEDGE message, so that the anchor gNB puts it in the RRC Release message. See the following for an implementation example (additions underlined):9.1.1.18 PARTIAL UE CONTEXT TRANSFER ACKNOWLEDGEThis message is sent by the new NG-RAN node to acknowledge the transferring part of the UE context from the old NG-RAN node. This message is also used to provide data forwarding related information for NR SDT.Direction: new NG-RAN node — old NG-RAN node.

[0069] Figure 3 depicts a method in accordance with particular embodiments. The method of Figure 3 may be performed by a UE or wireless device (e.g. the UE 612 or UE 700 as described later with reference to Figures 6 and 7 respectively).

[0070] The method begins at step 302, in which the user equipment transmits a connection resume message to a network node of a communication network. Responsive to one or more criteria being met, the connection resume message (e.g., RRC Resume message) comprises an indication (e.g., a Resume Cause set to srs-PosConflgOrActivationReq) that a cause forresuming a connection with the communication network is to configure SRS for positioning or to request activation of a configuration for SRS for positioning. See step 120 of Figure 1 and step 220 of Figure 2 for further information.

[0071] The one or more criteria may comprise a first criterion that the network node indicates to the user equipment that the user equipment is permitted to include the indication in the connection resume message. For example, the user equipment may receive, from the network node, system information comprising an indication that the user equipment is permitted to include the indication in the connection resume message. The system information may be broadcast by the network node.

[0072] The one or more criteria may comprise a second criterion that the network node serves a cell that is not within a validity area for an immediate (e.g., ongoing) SRS configuration. The one or more criteria may comprise a third criterion that the network node serves a cell within a validity area for a pre-configured SRS configuration.

[0073] In one or more embodiments, the UE may therefore send the resume cause srs- PosConfigOrActivationReq:• only to the gNBs whose cells are in the validity area• And / or if a gNB indicates via System Information broadcast on whether it allows UE to send such resume cause. The indication may be provided via a flag (e.g., one bit true / false) which can be present in System information Block (e.g., SIB1 or SIB2). It is also possible that this indication may be provided in specific positioning system information block (posSIB). In such case, the UE may acquire the relevant SIB (posSIB) before sending the request.

[0074] Figure 4 depicts a method in accordance with particular embodiments. The method of Figure 4 may be performed by a network node (e.g. the network node 610 or network node 800 as described later with reference to Figures 6 and 8 respectively). The method of Figure 4 may describe, at least in some respects, complementary steps to those performed by a UE and described with respect to Figure 3, and those performed by a first (anchor) network node and described with respect to Figure 5.

[0075] The method begins at step 402, in which the network node receives a connection resume message from a user equipment, requesting resumption of a connection between the user equipment and a communication network. The connection resume message may comprise an indication (e.g., a Resume Cause set to srs-PosConflgOrActivationReq) that a cause for resuming the connection is to configure SRS for positioning or to request activation of aconfiguration for SRS for positioning. See step 120 in Figure 1 and step 220 in Figure 2 for further information. The network node may serve a cell within a validity area for the SRS configuration, or a cell outside the validity area.

[0076] The SRS configuration for positioning for the user equipment may be pre-configured in the user equipment (e.g., and therefore subject to activation by an appropriate command from a network node). Alternatively, the SRS configuration for positioning for the user equipment may be immediate and / or ongoing in the user equipment.

[0077] In step 404, the network node transmits, to an anchor network node for the connection, a request message (e.g., Retrieve UE Context Request message) to retrieve a context for the user equipment. The request message comprises an indication (e.g., a Resume Cause set to srs-PosConflgOrActivationReq) that the cause for resuming the connection is to configure SRS for positioning or to request activation of a configuration for SRS for positioning. See step 122 in Figure 1 and step 222 in Figure 2for further information.

[0078] The request message may comprise a request to activate the SRS configuration for positioning for the user equipment.

[0079] In step 406, the network node receives, from the anchor network node, a response message (e.g., Retrieve UE Context Response message) comprising at least part of the context for the user equipment. The at least part of the context for the user equipment comprises at least part of an SRS configuration for positioning for the user equipment. See step 126 in Figure 1 and step 226 in Figure 2for further detail.

[0080] The response message may comprise the entire SRS configuration for positioning for the user equipment. Additionally or alternatively, the response message may comprise an indication of characteristics for a positioning configuration (e.g., LPHAP) used by the user equipment. In the latter case, the network node may use the characteristics to determine a new SRS configuration for positioning for the user equipment. The network node may then transmit an indication of the new SRS configuration for positioning to one or more of: the user equipment and the anchor network node.

[0081] The SRS configuration and / or the characteristics may comprise one or more of: an indication of frequency resources on which SRS for positioning are to be transmitted by the user equipment; an indication of time resources on which SRS for positioning are to be transmitted by the user equipment; information concerning a comb with which SRS for positioning are to be transmitted by the user equipment; information concerning frequency hopping or sequence hopping to be used by the user equipment when transmitting SRS for positioning.

[0082] In a further step not illustrated in Figure 4, the network node may transmit an activation message (e.g., RRC Release message) to the user equipment, activating the SRS configuration. See step 128 in Figure 1 and step 232 in Figure 2.

[0083] Figure 5 depicts a method in accordance with particular embodiments. The method of Figure 4 may be performed by a network node (e.g. the network node 610 or network node 800 as described later with reference to Figures 6 and 8 respectively). The method of Figure 5 may describe, at least in some respects, complementary steps to those performed by a UE and described with respect to Figure 3, and those performed by a receiving (second) network node and described with respect to Figure 4.

[0084] The method begins at step 502, in which the first network node (e.g., an anchor node for the UE connection to the network) receives, from a second network node (e.g., a network node which receives a connection resume request from the UE), a request message (e.g., Retrieve UE Context Request message) to retrieve a context for a conn / ection between the user equipment and a communication network. The request message may comprise an indication (e.g., a Resume Cause set to srs-PosConflgOrActivationReq) that a cause for resuming the connection is to configure SRS for positioning or to request activation of a configuration for SRS for positioning. See step 122 in Figure 1 and step 222 in Figure 2 for further information.

[0085] The SRS configuration for positioning for the user equipment may be pre-configured in the user equipment (e.g., and therefore subject to activation by an appropriate command from a network node). Alternatively, the SRS configuration for positioning for the user equipment may be immediate and / or ongoing in the user equipment.

[0086] The request message may comprise a request to activate the SRS configuration for positioning for the user equipment.

[0087] The second network node may serve a cell within a validity area for the SRS configuration, or a cell outside the validity area.

[0088] In step 504, the first network node transmits, to the second network node, a response message (e.g., Retrieve UE Context Response message) comprising at least part of the context for the user equipment, wherein the at least part of the context for the user equipment comprises at least part of an SRS configuration for positioning for the user equipment. See step 126 in Figure 1 and step 226 in Figure 2 for further detail.

[0089] The response message may comprise the entire SRS configuration for positioning for the user equipment. Additionally or alternatively, the response message may comprise an indication of characteristics for a positioning configuration (e.g., LPHAP) used by the user equipment. In the latter case, the second network node may use the characteristics to determinea new SRS configuration for positioning for the user equipment. The network node may then transmit an indication of the new SRS configuration for positioning to one or more of: the user equipment and the first (anchor) network node.

[0090] The SRS configuration and / or the characteristics may comprise one or more of: an indication of frequency resources on which SRS for positioning are to be transmitted by the user equipment; an indication of time resources on which SRS for positioning are to be transmitted by the user equipment; information concerning a comb with which SRS for positioning are to be transmitted by the user equipment; information concerning frequency hopping or sequence hopping to be used by the user equipment when transmitting SRS for positioning.

[0091] In step 506, after transmitting the response message, the first network node releases the context for the user equipment, or maintains the context for the user equipment.

[0092] Figure 6 shows an example of a communication system 600 in accordance with some embodiments.

[0093] In the example, the communication system 600 includes a telecommunication network 602 that includes an access network 604, such as a radio access network (RAN), and a core network 606, which includes one or more core network nodes 608. The access network 604 includes one or more access network nodes, such as network nodes 610a and 610b (one or more of which may be generally referred to as network nodes 610), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 602 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 602 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 602, including one or more network nodes 610 and / or core network nodes 608.

[0094] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O- CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time controlapplication (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies. The network nodes 610 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 612a, 612b, 612c, and 612d (one or more of which may be generally referred to as UEs 612) to the core network 606 over one or more wireless connections.

[0095] 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 600 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 600 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0096] The UEs 612 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 610 and other communication devices. Similarly, the network nodes 610 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 612 and / or with other network nodes or equipment in the telecommunication network 602 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 602.

[0097] In the depicted example, the core network 606 connects the network nodes 610 to one or more host computing systems, such as host 616. 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 606 includes one more core network nodes (e.g., core network node 608) that are structured with hardware and software components. Featuresof 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 608. 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).

[0098] The host 616 may be under the ownership or control of a service provider other than an operator or provider of the access network 604 and / or the telecommunication network 602. The host 616 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.

[0099] As a whole, the communication system 600 of Figure 6 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.

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

[0101] In some examples, the UEs 612 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 604 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 604. 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).

[0102] In the example, the hub 614 communicates with the access network 604 to facilitate indirect communication between one or more UEs (e.g., UE 612c and / or 612d) and network nodes (e.g., network node 610b). In some examples, the hub 614 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 614 may be a broadband router enabling access to the core network 606 for the UEs. As another example, the hub 614 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 610, or by executable code, script, process, or other instructions in the hub 614. As another example, the hub 614 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 614 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 614 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 614 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 614 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0103] The hub 614 may have a constant / persistent or intermittent connection to the network node 610b. The hub 614 may also allow for a different communication scheme and / or schedule between the hub 614 and UEs (e.g., UE 612c and / or 612d), and between the hub 614 and the core network 606. In other examples, the hub 614 is connected to the core network 606 and / or one or more UEs via a wired connection. Moreover, the hub 614 may be configured to connect to an M2M service provider over the access network 604 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 610 while still connected via the hub 614 via a wired or wireless connection. In someembodiments, the hub 614 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 610b. In other embodiments, the hub 614 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 610b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0104] Figure 7 shows a UE 700 in accordance with some embodiments. The UE 700 presents additional details of some embodiments of the UE 612 of Figure 1. 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 / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, 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.

[0105] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP 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).

[0106] The UE 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input / output interface 706, a power source 708, a memory 710, a communication interface 712, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 7. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may containmultiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0107] The processing circuitry 702 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 710. The processing circuitry 702 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 702 may include multiple central processing units (CPUs). The processing circuitry 702 may be configured to cause the UE 702 to perform the methods as described with reference to Figure 3, and / or the signalling of the UE in one or more of Figures 1 and 2.

[0108] In the example, the input / output interface 706 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 700. 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.

[0109] In some embodiments, the power source 708 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 708 may further include power circuitry for delivering power from the power source 708 itself, and / or an external power source, to the various parts of the UE 700 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of thepower source 708. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 708 to make the power suitable for the respective components of the UE 700 to which power is supplied.

[0110] The memory 710 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 710 includes one or more application programs 714, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 716. The memory 710 may store, for use by the UE 700, any of a variety of various operating systems or combinations of operating systems.

[0111] The memory 710 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 710 may allow the UE 700 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 710, which may be or comprise a device-readable storage medium.

[0112] The processing circuitry 702 may be configured to communicate with an access network or other network using the communication interface 712. The communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722. The communication interface 712 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 718 and / or a receiver 720 appropriate to provide network communications (e.g., optical, electrical,frequency allocations, and so forth). Moreover, the transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0113] In the illustrated embodiment, communication functions of the communication interface 712 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.

[0114] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 712, 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).

[0115] 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.

[0116] 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, avoice 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 wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking 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 700 shown in Figure 7.

[0117] 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.

[0118] 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.

[0119] Figure 8 shows a network node 800 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 NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e g., O-RU, O-DU, O-CU).

[0120] 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, distributed units (e.g., in an O-RAN access node) 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).

[0121] 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 / multi cast 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).

[0122] The network node 800 includes a processing circuitry 802, a memory 804, a communication interface 806, and a power source 808. The network node 800 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 800 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 800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 804 for different RATs) and some components may be reused (e.g., a same antenna 810 may be shared by different RATs). The network node 800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 800, 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 networknode 800.

[0123] The processing circuitry 802 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 800 components, such as the memory 804, to provide network node 800 functionality. For example, the processing circuitry 802 may be configured to cause the network node to perform the methods as described with reference to Figure 4 or Figure 5, and / or the signalling of the Anchor node or the Receiving node in one or more of Figures 1 and 2.

[0124] In some embodiments, the processing circuitry 802 includes a system on a chip (SOC). In some embodiments, the processing circuitry 802 includes one or more of radio frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814. In some embodiments, the radio frequency (RF) transceiver circuitry 812 and the baseband processing circuitry 814 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 812 and baseband processing circuitry 814 may be on the same chip or set of chips, boards, or units.

[0125] The memory 804 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 computerexecutable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 802. The memory 804 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 802 and utilized by the network node 800. The memory 804 may be used to store any calculations made by the processing circuitry 802 and / or any data received via the communication interface 806. In some embodiments, the processing circuitry 802 and memory 804 is integrated.

[0126] The communication interface 806 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 806 comprises port(s) / terminal(s) 816 to send and receive data, forexample to and from a network over a wired connection. The communication interface 806 also includes radio front-end circuitry 818 that may be coupled to, or in certain embodiments a part of, the antenna 810. Radio front-end circuitry 818 comprises filters 820 and amplifiers 822. The radio front-end circuitry 818 may be connected to an antenna 810 and processing circuitry 802. The radio front-end circuitry may be configured to condition signals communicated between antenna 810 and processing circuitry 802. The radio front-end circuitry 818 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 818 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 820 and / or amplifiers 822. The radio signal may then be transmitted via the antenna 810. Similarly, when receiving data, the antenna 810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 818. The digital data may be passed to the processing circuitry 802. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0127] In certain alternative embodiments, the network node 800 does not include separate radio front-end circuitry 818, instead, the processing circuitry 802 includes radio front-end circuitry and is connected to the antenna 810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 812 is part of the communication interface 806. In still other embodiments, the communication interface 806 includes one or more ports or terminals 816, the radio front-end circuitry 818, and the RF transceiver circuitry 812, as part of a radio unit (not shown), and the communication interface 806 communicates with the baseband processing circuitry 814, which is part of a digital unit (not shown).

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

[0129] The antenna 810, communication interface 806, and / or the processing circuitry 802 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 810, the communication interface 806, and / or the processing circuitry 802 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 aUE, another network node and / or any other network equipment.

[0130] The power source 808 provides power to the various components of network node 800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 808 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 800 with power for performing the functionality described herein. For example, the network node 800 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 808. As a further example, the power source 808 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0131] Embodiments of the network node 800 may include additional components beyond those shown in Figure 8 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 800 may include user interface equipment to allow input of information into the network node 800 and to allow output of information from the network node 800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 800. In some embodiments providing a core network node, such as core network node 108 of FIG. 6, some components, such as the radio front-end circuitry 818 and the RF transceiver circuitry 812 may be omitted.

[0132] Figure 9 is a block diagram illustrating a virtualization environment 900 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 900 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. In some embodiments, thevirtualization environment 900 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

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

[0134] Hardware 904 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 906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 908a and 908b (one or more of which may be generally referred to as VMs 908), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 906 may present a virtual operating platform that appears like networking hardware to the VMs 908.

[0135] The VMs 908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 906. Different embodiments of the instance of a virtual appliance 902 may be implemented on one or more of VMs 908, 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.

[0136] In the context of NFV, a VM 908 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 908, and that part of hardware 904 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 908 on top of the hardware 904 and corresponds to the application 902.

[0137] Hardware 904 may be implemented in a standalone network node with generic or specific components. Hardware 904 may implement some functions via virtualization.Alternatively, hardware 904 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 910, which, among others, oversees lifecycle management of applications 902. In some embodiments, hardware 904 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 912 which may alternatively be used for communication between hardware nodes and radio units.

[0138] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0139] 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 ordiscrete 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- readable storage 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.

[0140] The following groups of numbered statements set out embodiments of the disclosure.EMBODIMENTSGroup A Embodiments1. A method performed by a user equipment, the method comprising: transmitting a connection resume message to a network node of a communication network, wherein, responsive to one or more criteria being met, the connection resume message comprises an indication that a cause for resuming a connection with the communication network is to configure sounding reference signals, SRS, for positioning or to request activation of a configuration for SRS for positioning.2. The method of embodiment 1, wherein the one or more criteria comprise a first criterion that the network node serves a cell that is not within a validity area for an immediate (e.g., ongoing) SRS configuration.3. The method of embodiment 1 or 2, wherein the one or more criteria comprise a second criterion that the network node serves a cell within a validity area for a pre-configured SRS configuration.4. The method of any one of the preceding embodiments, wherein the one or more criteria comprise a third criterion that the network node indicates to the user equipment that the user equipment is permitted to include the indication in the connection resume message.5. The method of embodiment 4, wherein the user equipment receives, from the network node, system information comprising an indication that the user equipment is permitted to include the indication in the connection resume message.6. The method of embodiment 5, wherein the system information is broadcast.7. The method of any one of the preceding embodiments, wherein the connection resume message comprises an RRC Resume message.8. The method of any one of the preceding embodiments, wherein the indication comprises a Resume Cause set to srs-PosConflgOrActivationReq.Group B Embodiments9. A method performed by a network node, the method comprising: receiving a connection resume message from a user equipment, requesting resumption of a connection between the user equipment and a communication network, wherein the connection resume message comprises an indication that a cause for resuming the connection is to configure sounding reference signals, SRS, for positioning or to request activation of a configuration for SRS for positioning; transmitting, to an anchor network node for the connection, a request message to retrieve a context for the user equipment, wherein the request message comprises an indication that the cause for resuming the connection is to configure SRS for positioning or to request activation of a configuration for SRS for positioning; and receiving, from the anchor network node, a response message comprising at least part of the context for the user equipment, wherein the at least part of the context for the user equipment comprises at least part of an SRS configuration for positioning for the user equipment.10. The method of embodiment 9, wherein the SRS configuration for positioning for the user equipment is pre-configured in the user equipment.11. The method of embodiment 9, wherein the SRS configuration for positioning for the user equipment is immediate and / or ongoing in the user equipment.12. The method of any one of embodiments 9 to 11, wherein the request message comprises a request to activate the SRS configuration for positioning for the user equipment.13. The method of any one of embodiments 9 to 12, wherein the response message comprises the entire SRS configuration for positioning for the user equipment.14. The method of any one of embodiments 9 to 13, wherein the response message comprises one or more of: an indication of frequency resources on which SRS for positioning are to be transmitted by the user equipment; an indication of time resources on which SRS for positioning are to be transmitted by the user equipment; information concerning a comb with which SRS for positioning are to be transmitted by the user equipment; information concerning frequency hopping or sequence hopping to be used by the user equipment when transmitting SRS for positioning.15. The method of any one of embodiments 9 to 14, wherein the response message comprises an indication of characteristics for a positioning configuration used by the user equipment.16. The method of embodiment 15, further comprising determining anew SRS configuration for positioning for the user equipment based on the characteristics.17. The method of embodiment 16, further comprising transmitting an indication of the new SRS configuration for positioning to one or more of: the user equipment and the anchor network node.18. The method of any one of embodiments 9 to 17, wherein the network node serves a cell within a validity area for the SRS configuration.19. The method of any one of embodiments 9 to 18, further comprising transmitting an activation message to the user equipment, activating the SRS configuration.20. The method of embodiment 19, wherein the activation message comprises an RRC Release message.21. The method of any one of embodiments 9 to 20, wherein the request message comprises a Retrieve UE Context Request message.22. The method of any one of embodiments 9 to 21 , wherein the response message comprises a Retrieve UE Context Response message.23. The method of any one of embodiments 9 to 22, wherein the indication comprises a Resume Cause set to srs-PosConflgOrActivationReq.24. A method performed by a first network node, the method comprising: receiving, from a second network node, a request message to retrieve a context for a connection between a user equipment and a communication network, wherein the second network node has received a connection resume request from the user equipment, wherein the first network node is an anchor network node for the connection, and wherein the request message comprises an indication that a cause for resuming the connection is to configure SRS for positioning or to request activation of a configuration for SRS for positioning; and transmitting, to the second network node, a response message comprising at least part of the context for the user equipment, wherein the at least part of the context for the user equipment comprises at least part of an SRS configuration for positioning for the user equipment.25. The method of embodiment 24, wherein the SRS configuration for positioning for the user equipment is pre-configured in the user equipment.26. The method of embodiment 24, wherein the SRS configuration for positioning for the user equipment is immediate and / or ongoing in the user equipment.27. The method of any one of embodiments 24 to 26, wherein the request message comprises a request to activate the SRS configuration for positioning for the user equipment.28. The method of any one of embodiments 24 to 27, wherein the response message comprises the entire SRS configuration for positioning for the user equipment.29. The method of any one of embodiments 24 to 28, wherein the response message comprises one or more of: an indication of frequency resources on which SRS for positioning are to be transmitted by the user equipment; an indication of time resources on which SRS for positioning are to be transmitted by the user equipment; information concerning a comb with which SRS for positioning are to be transmitted by the user equipment; information concerning frequency hopping or sequence hopping to be used by the user equipment when transmitting SRS for positioning.30. The method of any one of embodiments 24 to 29, wherein the response messagecomprises an indication of characteristics for a positioning configuration used by the user equipment.31. The method of embodiment 30, further comprising receiving, from the second network node an indication of a new SRS configuration for positioning based on the characteristics.32. The method of any one of embodiments 24 to 31, wherein the second network node serves a cell within a validity area for the SRS configuration.33. The method of any one of embodiments 24 to 32, wherein the request message comprises a Retrieve UE Context Request message.34. The method of any one of embodiments 24 to 33, wherein the response message comprises a Retrieve UE Context Response message.35. The method of any one of embodiments 24 to 34, wherein the indication comprises a Resume Cause set to srs-PosConflgOrActivationReq.36. The method of any one of embodiments 24 to 35, further comprising releasing the context for the user equipment after transmitting the response message.37. The method of any one of embodiments 24 to 35, further comprising maintaining the context for the user equipment after transmitting the response message.Group C Embodiments38. A user equipment, comprising: processing circuitry configured to cause the user equipment 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.39. A network node, the network node comprising: processing circuitry configured to cause the network node to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.40. A user equipment (UE), 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 cause the user equipment 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.

Claims

CLAIMS1. A method performed by a second network node, the method comprising: receiving (402) a connection resume message from a user equipment, requesting resumption of a connection between the user equipment and a communication network, wherein the connection resume message comprises an indication that a cause for resuming the connection is to configure sounding reference signals, SRS, for positioning or to request activation of a configuration for SRS for positioning; transmitting (404), to a first network node, which is an anchor node for the connection, a request message to retrieve a context for the user equipment, wherein the request message comprises an indication that the cause for resuming the connection is to configure SRS for positioning or to request activation of a configuration for SRS for positioning; and receiving (406), from the first network node, a response message comprising at least part of the context for the user equipment, wherein the at least part of the context for the user equipment comprises at least part of an SRS configuration for positioning for the user equipment.

2. The method of claim 1, wherein the SRS configuration for positioning for the user equipment is:- pre-configured in the user equipment; or.- immediate and / or ongoing in the user equipment.

3. The method of any one of the preceding claims, wherein the request message comprises a request to activate the SRS configuration for positioning for the user equipment.

4. The method of any one of the preceding claims, wherein the response message comprises the entire SRS configuration for positioning for the user equipment.

5. The method of any one of the preceding claims, wherein the response message comprises one or more of: an indication of frequency resources on which SRS for positioning are to be transmitted by the user equipment; an indication of time resources on which SRS for positioning are to be transmitted by the user equipment; information concerning a comb with which SRS for positioning are to be transmitted by the user equipment; information concerning frequency hopping or sequence hopping to be used by the user equipment when transmittingSRS for positioning.

6. The method of any one of the preceding claims, wherein the response message comprises an indication of characteristics for a positioning configuration used by the user equipment.

7. The method of claim 6, further comprising determining a new SRS configuration for positioning for the user equipment based on the characteristics.

8. The method of claim 7, further comprising transmitting an indication of the new SRS configuration for positioning to one or more of: the user equipment and the first network node.

9. The method of any one of the preceding claims, wherein the second network node serves a cell within a validity area for the SRS configuration.

10. The method of any one of the preceding claims, further comprising transmitting an activation message to the user equipment, activating the SRS configuration.

11. The method of claim 10, wherein the activation message comprises an RRC Release message.

12. The method of any one of the preceding claims, wherein the request message comprises a Retrieve UE Context Request message, and / or wherein the response message comprises a Retrieve UE Context Response message.

13. The method of any one of the preceding claims, wherein the indication comprises a Resume Cause set to srs-PosConflgOrActivationReq.

14. A method performed by a first network node, the method comprising: receiving (502), from a second network node, a request message to retrieve a context for a connection between a user equipment and a communication network, wherein the second network node has received a connection resume request from the user equipment, wherein the first network node is an anchor network node for the connection, wherein the request message comprises an indication that a cause for resuming the connection is to configure SRS for positioning or to request activation of a configuration for SRS for positioning; andtransmitting (504), to the second network node, a response message comprising at least part of the context for the user equipment, wherein the at least part of the context for the user equipment comprises at least part of an SRS configuration for positioning for the user equipment.

15. The method of claim 14, wherein the SRS configuration for positioning for the user equipment is:- pre-configured in the user equipment; or- immediate and / or ongoing in the user equipment.

16. The method of any one of claims 14 to 15, wherein the request message comprises a request to activate the SRS configuration for positioning for the user equipment.

17. The method of any one of claims 14 to 16, wherein the response message comprises the entire SRS configuration for positioning for the user equipment.

18. The method of any one of claims 14 to 17, wherein the response message comprises one or more of: an indication of frequency resources on which SRS for positioning are to be transmitted by the user equipment; an indication of time resources on which SRS for positioning are to be transmitted by the user equipment; information concerning a comb with which SRS for positioning are to be transmitted by the user equipment; information concerning frequency hopping or sequence hopping to be used by the user equipment when transmitting SRS for positioning.

19. The method of any one of claims 14 to 18, wherein the response message comprises an indication of characteristics for a positioning configuration used by the user equipment.

20. The method of claim 19, further comprising receiving, from the second network node an indication of a new SRS configuration for positioning based on the characteristics.

21. The method of any one of claims 14 to 20, wherein the second network node serves a cell within a validity area for the SRS configuration.

22. The method of any one of claims 14 to 21, wherein the request message comprises aRetrieve UE Context Request message, and / or wherein the response message comprises a Retrieve UE Context Response message.

23. The method of any one of claims 14 to 22, wherein the indication comprises a Resume Cause set to srs-PosConflgOrActivationReq.

24. The method of any one of claims 14 to 23, further comprising releasing or maintaining the context for the user equipment after transmitting the response message.

25. A method performed by a user equipment, the method comprising: transmitting (302) a connection resume message to a network node of a communication network, wherein, responsive to one or more criteria being met, the connection resume message comprises an indication that a cause for resuming a connection with the communication network is to configure sounding reference signals, SRS, for positioning or to request activation of a configuration for SRS for positioning, wherein the one or more criteria comprise a first criterion that the user equipment receives, from the network node, an indication that the user equipment is permitted to include the indication in the connection resume message.

26. The method of claim 25, wherein the one or more criteria comprise a second criterion that the network node serves a cell that is not within a validity area for an ongoing SRS configuration.

27. The method of claim 25 or 26, wherein the one or more criteria comprise a third criterion that the network node serves a cell within a validity area for a pre-configured SRS configuration.

28. The method of any one of claims 25 to 27, wherein the user equipment receives, from the network node, system information comprising the indication that the user equipment is permitted to include the indication in the connection resume message.

29. The method of claim 28, wherein the system information is broadcast.

30. The method of any one of claims 25 to 29, wherein the connection resume message comprises an RRC Resume message.

31. The method of any one of claims 25 to 30, wherein the indication comprises a Resume Cause set to srs-PosConflgOrActivationReq.

32. A second network node comprising processing circuitry configured to cause the second network node to: receive (402) a connection resume message from a user equipment, requesting resumption of a connection between the user equipment and a communication network, wherein the connection resume message comprises an indication that a cause for resuming the connection is to configure sounding reference signals, SRS, for positioning or to request activation of a configuration for SRS for positioning; transmit (404), to a first network node, which is an anchor network node for the connection, a request message to retrieve a context for the user equipment, wherein the request message comprises an indication that the cause for resuming the connection is to configure SRS for positioning or to request activation of a configuration for SRS for positioning; and receive (406), from the first network node, a response message comprising at least part of the context for the user equipment, wherein the at least part of the context for the user equipment comprises at least part of an SRS configuration for positioning for the user equipment.

33. The second network node of claim 32, wherein the processing circuitry is further configured to cause the second network node to perform the method of any of claims 2-13.

34. A second network node configured to perform the method of any of claims 1-13.

35. A first network node comprising processing circuitry configured to cause the first network node to: receive (502), from a second network node, a request message to retrieve a context for a connection between a user equipment and a communication network, wherein the second network node has received a connection resume request from the user equipment, wherein the first network node is an anchor network node for the connection, and wherein the request message comprises an indication that a cause for resuming the connection is to configure SRS for positioning or to request activation of a configuration for SRS for positioning; and transmit (504), to the second network node, a response message comprising at least partof the context for the user equipment, wherein the at least part of the context for the user equipment comprises at least part of an SRS configuration for positioning for the user equipment.

36. The first network node of claim 35, the processing circuitry further configured to cause the first network node to perform the method of any of claims 15-24.

37. A first network node configured to perform the method of any of claims 14-24.

38. A user equipment, UE, comprising processing circuitry configured to cause the UE to: transmit (302) a connection resume message to a network node of a communication network, wherein, responsive to one or more criteria being met, the connection resume message comprises an indication that a cause for resuming a connection with the communication network is to configure sounding reference signals, SRS, for positioning or to request activation of a configuration for SRS for positioning, wherein the one or more criteria comprise a first criterion that the user equipment receives, from the network node, an indication that the user equipment is permitted to include the indication in the connection resume message.

39. The UE of claim 38, wherein the processing circuitry is further configured to cause the UE to perform the method of any of claims 26 to 31.

40. A user equipment, UE, configured to perform the method of any of claims 25-31.

Images