Network handling of power saving devices
By enabling the AMF to share UE power saving information and availability times with network functions, the 5G core network optimizes UE reachability handling, reducing signaling and improving power management within the 5G core network architecture.
Patent Information
- Application Number
- PCT/EP2024/062643
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-16
- Filing Date
- 2024-05-07
- Publication Date
- 2024-11-14
AI Technical Summary
The current 5G core network architecture lacks an efficient method to handle mobile termination reachability in combination with UE power saving methods, leading to increased core network signaling as network functions like SMF and PCF do not have knowledge of UE power saving status, resulting in unnecessary signaling attempts.
A method where the AMF sends power saving information and estimated next available time of UE to network functions, allowing them to avoid signaling attempts when the UE is unreachable, and providing finer granularity notifications for UE reachability.
This approach reduces unnecessary signaling, allows network functions to plan requests better, and optimizes UE reachable handling by providing accurate predictions of UE availability, thereby decreasing core network signaling and improving power management.
Smart Images

Figure EP2024062643_14112024_PF_FP_ABST
Abstract
Description
[0001] NETWORK HANDLING OF POWER SAVING DEVICES
[0002] TECHNICAL FIELD
[0003] The present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting power saving devices.
[0004] BACKGROUND
[0005] Over the different mobile system generations there have been user equipment (UE) power saving methods added to save radio resources in the UE and the network. One key is to save battery in the UE. Examples include Discontinuous Reception (DRX), Extended Discontinuous Reception (eDRX), MICO (Mobile Initiated Connection Only) and UE power saving mode. The first two are applicable from 2G to 5G networks. MICO is introduced in 5G, and UE power saving mode is applicable in 4G. There could be up to 3 hours where the UE is unreachable when eDRX applies. For MICO, unreachable time is typically the granularity of hour / hours when periodic registration update in 5GC (5G core) (Tracking area updates in legacy) applies.
[0006] UE power saving is of importance for all types of UEs, and in particular for different types of loT (Internet of Things) devices.
[0007] RedCap (Reduced Capability) is added in 3 GPP for 5G and for New Radio (NR) is in short “loT for NR”. A RedCap UE has reduced capability in terms of radio impact and the purpose for RedCap introduction was to limit UE complexity as well as UE cost. For RedCap devices, power saving is of importance. RedCap devices addresses many areas: Wearables; Video surveillance; Industrial wireless sensors. Wearables are e.g., smart watches, XR (extended reality), VR (virtual reality), AR (augmented reality). For wearables, battery life of up to 2 weeks are assumed. For industrial wireless sensors use case battery life of a few years are expected. A specification for such sensors is described in 3rd Generation Partnership Project (3GPP) Technical Standard (TS) 23.502 V17.8.0 (2023-03) 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17). Table 5.2.2.2.2-1 of this document mentions a UE Context in AMFNR RedCap Indication. SUMMARY
[0008] There currently exist certain challenge(s). The current network architecture in 5GC (5G core network) has not considered an efficient way to handle MT (mobile termination) reachability in combination with UE power saving methods. Consumer (network function) NF, in 5GC perspective SMF (session management function) and PCF (policy control function) and the like, is involved for addressing this but has no knowledge that UE power saving applies and in what grade. This is only known by the AMF (access and mobility management function) in 5GC. Thus, all UEs need to have the same treatment in the NF (e.g., SMF, PCF, etc.) irrespective if any power saving method applies for a UE or not. This will increase the core network signaling. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.
[0009] According to a first aspect of the invention there is provided a method performed in a network node having an access and mobility management function, AMF. The method comprises: receiving a request message; transmitting, to a network function, NF, a create request having a power saving user equipment, UE, parameter and an estimated next UE available time parameter. The method further comprises receiving, from the NF a create response having a support for power saving UE parameter; and transmitting, to the UE , an accept message. According to a further aspect of the invention there is provided method in a network node having a network function, NF, the method comprising: receiving, from an access and mobility management function, AMF, a create request having a power saving user equipment, UE, parameter and an estimated next UE available time parameter; and transmitting, to the AMF, a create response having a support for power saving UE parameter.
[0010] According to a further aspect of the invention there is provided a method performed in a network node having an access and mobility management function, AMF, the method comprising: receiving, from a network function, NF, a request with UE interaction required message, the request with UE interaction required message identifying a UE with which UE interaction is required and having a Subscribe for UE reachable parameter. Responsive to the UE not being reachable, the method transmitting, to the NF, a failure response message having an estimated next UE available time parameter and a subscription ID for UE reachability; and transmitting, to the NF , a UE Reachable message having a remaining UE reachable time parameter.
[0011] According to a still further aspect of the invention there is provided a method in a network node having a network function, NF, , the method comprising: transmitting , to an access and mobility management function, AMF, , a request with UE interaction required message, the request identifying a UE with which UE interaction is required and having a Subscribe for UE reachable parameter; receiving , from the AMF , a failure response message having an estimated next UE available time parameter and a subscription ID for UE reachability. The method further comprises receiving, from the AMF, a UE Reachable message having a remaining UE reachable time parameter.
[0012] According to a still further aspect of the invention there is provided a network node having an access and mobility function, AMF, and also a network node having a network function, NF, . According to some embodiments, for 5G and in some cases, later mobile generations, information when UE is expected to return to CM (Connection Management)- Connected / reachable is sent from the AMF to the NF (e.g., SMF, PCF, etc.) (Estimated Next UE Available Time) and UE power saving information.
[0013] According to other embodiments, the NF (e.g., SMF, PCF, etc.) can initiate an early reception of UE reachability by including a request to subscribe for UE Reachable (Subscribe for UE Reachable) in a Request with UE interaction required message. The AMF will respond to the request by sending an indication (Subscription ID for UE Reachable). The AMF will notify the NF (e.g., SMF, PCF, etc.) that the UE is reachable at the next time the UE enters a reachable state (e.g., CM-Connected) and thus is available for a Request with UE interaction required message.
[0014] Certain embodiments may provide one or more of the following technical advantage(s). The NF (e.g., the SMF, PCF, etc.) can obtain information of UE power saving earlier and thus does not have to do an attempt with failure outcome due to the UE not being reachable. Examples are protocol data unit (PDU) session procedures for SMFs and policy association establishment and modification procedures for AMFs and PCFs. The NF (e.g., SMF, PCF, etc.) can also obtain information for which UEs that power saving applies. Decreased signaling may also be achieved. For a network triggered service request, the AMF can provide information when a UE is assumed to be available together with the finer granularity UE reachable notifications to the NF (e.g., SMF, PCF, etc.). This can result in the NF (e.g., SMF, PCF, etc.) avoiding the sending or requests to the UE when the UE is not reachable. This results in decreased signaling. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain nonlimiting embodiments of inventive concepts. In the drawings:
[0016] Figure 1 is a block diagram of a RedCap device;
[0017] Figure 2 is a signaling diagram illustrating a UE performing a PDU session establishment procedure where the AMF indicates if the UE is activated for any power saving together with a time where UE is expected to be available according to some embodiments;
[0018] Figure 3 is a signaling diagram illustrating a UE performing a PDU session modification procedure where the AMF indicates if the UE is activated for any power saving together with a time where UE is expected to be available according to some embodiments;
[0019] Figures 4-6 are flow charts illustrating operations of an AMF node according to some embodiments;
[0020] Figures 7-9 are flowcharts illustrating operations of an SMF node according to some embodiments;
[0021] Figure 10 is a signaling diagram where when a UE is in CM-Idle or is otherwise non-reachable and an SMF request with UE interaction is received at the AMF and the failure response from the AMF indicates that the UE is not reachable and the AMF adds informational information on UE available time according to some embodiments;
[0022] Figure 11 is a flowchart illustrating further operations of an AMF node according to some embodiments;
[0023] Figure 12 is a flowchart illustrating further operations of a SMF node according to some embodiments;
[0024] Figure 13 is a signaling diagram illustrating a UE performing an AM (Access and Mobility) policy association establishment procedure where the AMF indicates if the UE is activated for any power saving together with a time where UE is expected to be available according to some embodiments;
[0025] Figure 14 is a signaling diagram illustrating a UE performing an AM (Access and Mobility) policy modification procedure where the AMF indicates if the UE is activated for any power saving together with a time where UE is expected to be available according to some embodiments;
[0026] Figure 15 is a signaling diagram illustrating a UE Policy Association Establishment including UE Configuration Update procedure where the AMF indicates if the UE is activated for any power saving together with a time where UE is expected to be available according to some embodiments;
[0027] Figure 16 is a signaling diagram where when a UE is in CM-Idle or is otherwise non-reachable and a PCF request with UE interaction is received at the AMF and the failure response from the AMF indicates that the UE is not reachable and the AMF adds informational information on UE available time according to some embodiments;
[0028] Figures 17-20 are flow charts illustrating operations of an AMF node according to some embodiments;
[0029] Figures 21-24 are flowcharts illustrating operations of a PCF node according to some embodiments;
[0030] Figures 25-28 are flow charts illustrating operations of an AMF node according to some embodiments;
[0031] Figures 29-32 are flowcharts illustrating operations of a network function, NF, node according to some embodiments;
[0032] Figure 33 is a block diagram of a communication system in accordance with some embodiments; Figure 34 is a block diagram of a user equipment in accordance with some embodiments;
[0033] Figure 35 is a block diagram of a network node in accordance with some embodiments;
[0034] Figure 36 is a block diagram of a host computer communicating with a user equipment in accordance with some embodiments;
[0035] Figure 37 is a block diagram of a virtualization environment in accordance with some embodiments; and
[0036] Figure 38 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.
[0037] DETAILED DESCRIPTION
[0038] 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, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present / used in another embodiment.
[0039] As previously indicated, the current network architecture in 5GC has not considered an efficient way to handle mobile termination reachability in combination with UE power saving methods. The various embodiments described herein enable information to be sent when UE is expected to return to CM-Connected / reachable from AMF to NF (e.g., SMF, PCF, etc.) (Estimated Next UE Available Time) and UE power saving information.
[0040] The UE being reachable in the disclosure and in the various embodiments means that the UE is in Connected state both on NAS (non-access stratum) level and on RRC (radio resource control) level and there is a signaling connection established between the AMF and the UE. For this situation, there is no need for any paging to retrieve the UE.
[0041] In various embodiments, an enhanced handling of UE power saving in the core network, impacting both the (consumer) NF (e.g., SMF, PCF, etc.), for which a Request with UE interaction required message is needed to be sent, and the AMF is provided. As the AMF is aware of if power saving applies to the UE and how the UE is allowed to access the network again, an estimated time the UE is expected to return to CM-Connected / reachable is provided from the AMF to the NF (e.g., SMF, PCF, etc.) together with an indication that UE power saving applies. By that, the NF (e.g., SMF, PCF, etc.) knows when the same or a new Request with UE interaction required message can be sent. The NF (e.g., SMF, PCF, etc.) acknowledges the handling of UE power saving.
[0042] Optimization of UE reachable handling can be achieved. A UE reachable notification can be provided to the NF (e.g., SMF, PCF, etc.) next time the UE is reachable. This is not only related to when UE power saving applies but can be a general method. In the UE reachable notification, an indication with the time period the UE will be reachable is provided and is in CM-Connected. Figure 1 is a block diagram illustrating elements of a RedCap device 100 (also referred to as a wearable user equipment, UE, an Internet of Things (loT) device, a wearable device, an industrial wireless sensor, a video surveillance device, and the like configured to provide wireless communication according to some embodiments. As shown, RedCap device 100 may include an antenna 107 (e.g., corresponding to antenna 3422 of Figure 34), and transceiver circuitry 101 (also referred to as a transceiver, e.g., corresponding to interface 3412 of Figure 34) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station(s) (e.g., corresponding to network node 3310A, 3310B of Figure 33, network node 3500 of Figure 35, also referred to as a RAN node, network node 3704) of a radio access network of Figure 37. RedCap device 100 may also include processing circuitry 103 (also referred to as a processor) coupled to the transceiver circuitry, and memory circuitry 105 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 105 may include computer readable program code that when executed by the processing circuitry 103 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 103 may be defined to include memory so that separate memory circuitry is not required. RedCap device 100 may also include an interface (such as a user interface) coupled with processing circuitry 103, and / or RedCap device 100 may be incorporated in a vehicle.
[0043] As discussed herein, operations of a RedCap device 100 may be performed by processing circuitry 103 and / or transceiver circuitry 101. For example, processing circuitry 103 may control transceiver circuitry 101 to transmit communications through transceiver circuitry 101 over a radio interface to a radio access network node (also referred to as a base station) and / or to receive communications through transceiver circuitry 101 from a RAN node over a radio interface. Moreover, modules may be stored in memory circuitry 105, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 103, processing circuitry 103 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to wireless communication devices). According to some embodiments, a RedCap device 100 and / or an elements ) / function(s) thereof may be embodied as a virtual node / nodes and / or a virtual machine / machines.
[0044] Figure 2 illustrates a first scenario where the NF is an SMF and the enhanced UE power handling can be used during PDU session establishment and Figure 3 illustrates where the enhanced UE power handling can be used during PDU session modification. In Figure 2 and Figure 3, the UE 200 may be a redcap device 100, a UE 3312A-3312D, a UE 3400, or a UE 1706. The AMF 202 may be implemented in a core network node 3308, a network node 3310A-3310B, a network node 3500, a virtual node 3702, or network node 3704. Similarly, the SMF 202 may be implemented in a core network node 3308, a network node 3310A-3310B, a network node 3500, a virtual node 3702, or network node 3704.
[0045] Turning to Figure 2, in operation 201, the UE 200 transmits a PDU Session Establishment Request to the AMF 202.
[0046] In operation 203, the AMF transmits a PDU session create request. In some embodiments, the PDU session create request is aNsmf_PDUSession_CreateSMContext Request. Information included in or transmitted with the PDU session create request includes a Power Saving UE parameter and an Estimated Next UE Available Time parameter. The power saving UE parameter indicates a consumer (e.g., a SMF) cannot get immediate response when the UE 200 is needed to be contacted. Power saving UE is e.g., a MICO activated UE and / or a UE using DRX / eDRX. The parameter may indicate if power saving for the UE 200 is changed i.e., enabled or disabled.
[0047] The Estimated Next UE Available Time parameter is the time the UE 200 is expected to return to being reachable (e.g., is in CM-Connected (based on e.g., periodic registration timer)).
[0048] NOTE: Estimated Next UE Available Time gives a prediction when the UE 200 may return to CM-Connected (i.e., becomes reachable). This is typically a maximum time. The UE 200 may choose to return earlier and if so, the UE reachable notification will give the moment when the UE 200 returns to CM-Connected and thus a Request with UE interaction required message can be sent to the AMF 202 immediately for the buffered request, meanwhile the Remaining UE Reachable Time can help the SMF 204 in deciding if a new request should be sent or if it should be buffered without trying to contact the AMF 202 again.
[0049] In operation 205, the SMF 204 transmits a PDU session create response to the AMF 202. In some embodiments, the PDU session create response is aNsmf_PDUSession_CreateSMContext Response. Information included in or transmitted with the PDU session create response includes a Support for Power Saving UE parameter. This parameter indicates that the receiving network function (NF) (e.g., the SMF 204) acknowledges support of reception and handling of ‘Power saving UE’ and handling of ‘Estimated Next UE Available Time’.
[0050] In operation 207, the SMF 204 transmits a communication message transfer request message to the AMF 202. In some embodiments, the communication message transfer request is a Namf_Communication_NlN2MessageTransferReq message. Information included in or transmitted with the communication message transfer request includes a Subscribe for UE Reachable parameter. The Subscribe for UE Reachable parameter indicates that the SMF 204 needs to be informed when the UE 200 is reachable again (i.e., the next time the UE is reachable).
[0051] In operation 209, the AMF 202 transmits a communication message transfer response message to the SMF 204. In some embodiments, the communication message transfer response is a Namf_Communication_NlN2MessageTransferRsp message. Information included in or transmitted with the communication message transfer response includes a subscription ID for UE reachability. The Subscription ID for UE Reachability indicates the ID of the UE Reachable subscription that the AMF 202 has created for the requesting NF (e.g., the SMF 204). It will be used when the AMF 202 detects the UE 200 is reachable and notifies the SMF 204 of the UE Reachable event. In operation 211, the AMF 200 transmits a PDU Session Establishment accept message to the UE 200.
[0052] In operation 213, the AMF 202 transmits a UE Reachable message to the SMF 204. Information included in or transmitted with the UE Reachable message includes a Remaining UE Reachable Time parameter. The Remaining UE Reachable Time parameter indicates a time period that the AMF 202 can hold the UE 200 in connected mode (e.g., CM-Connected) and the UE 200 is reachable.
[0053] In operation 215, the SMF 204 transmits a Request with UE interaction required message to the AMF 202. The Request with UE interaction required message may happen after the NF (e.g., the SMF 204) has received the UE Reachable message from the AMF 200. This is part of Network initiated Service Requests described hereinbelow.
[0054] For PDU session modifications, similar messages can be used in the PDU session modification procedures. Figure 3 illustrates PDU session modification from the perspective of the UE 200 requesting session modification. Turning to Figure 3, in operation 301, the UE 200 transmits a PDU Session Modification Request to the AMF 202. This operation does not occur during a SMF initiated session modification.
[0055] In operation 303, the AMF transmits a PDU session update request. In some embodiments, the PDU session update request is aNsmf PDUSession UpdateSMContext Request. Information included in or transmitted with the PDU session update request includes the Power Saving UE parameter and the Estimated Next UE Available Time parameter described above.
[0056] In operation 305, the SMF 204 transmits a PDU session update response to the AMF 202. In some embodiments, the PDU session update response is a
[0057] Nsmf PDUSession UpdateSMContext Response. Information included in or transmitted with the PDU session create response includes a Support for Power Saving UE parameter.
[0058] In operation 307, the SMF 204 transmits a communication message transfer request message to the AMF 202. In some embodiments, the communication message transfer request is a Namf_Communication_NlN2MessageTransferReq message. Information included in or transmitted with the communication message transfer request includes the Subscribe for UE Reachable parameter.
[0059] In operation 309, the AMF 202 transmits a communication message transfer response message to the SMF 204. In some embodiments, the communication message transfer response is a Namf_Communication_NlN2MessageTransferRsp message. Information included in or transmitted with the communication message transfer response includes the subscription ID for UE reachability. In operation 311 , the AMF 200 transmits a PDU Session Modification command message to the UE 200.
[0060] In operation 313, the UE 200 transmits a PDU Session Modification Complete message that acknowledges the session modification.
[0061] In operation 315, the AMF 202 transmits a UE Reachable message to the SMF 204. Information included in or transmitted with the UE Reachable message includes the Remaining UE Reachable Time parameter.
[0062] In operation 317, the SMF 204 transmits a Request with UE interaction required message to the AMF 202. The Request with UE interaction required message may happen after the NF (e.g., the SMF 204) has received the UE Reachable message from the AMF 200 and the UE 200 is reachable. This is part of network initiated Service Requests described hereinbelow.
[0063] As can be seen from the above, in PDU Session procedures, the following advantages may be achieved:
[0064] The SMF 204 gets information of UE power saving early and does not have to do an attempt with failure outcome due to the UE 200 not being reachable. The SMF 204 also gets the information for which UEs that power saving applies. This could also be used as an input to determine usage of Extended Buffering (defined in 3GPP) in the SMF 204.
[0065] The SMF 204 gets an assumed estimation when the UE 200 is available (maximum time). The UE reachability message to the SMF 204 applies already from the beginning and is triggered by the AMF 202 for power saving UEs which give a finer granularity.
[0066] Decreased signaling (no Subscribe for UE Reachable sent from the SMF 204 to the AMF 202) and avoiding SMF retries of sending Request with UE interaction required messages while the UE is unreachable.
[0067] The AMF 202 provides the SMF 204 with information for how long the UE may be reachable. This can be used by the SMF 204 to determine times the UE is likely to be reachable.
[0068] Note that if the SMF 204 will seldom transit a Request with UE interaction required but has subscribed for the UE Reachable parameter and the AMF 202 is sending UE Reachable messages when the SMF 204 does not have anything to send to the UE, the above may result in increased signaling.
[0069] Figure 4 illustrates operations of Figure 2 from the perspective of the AMF 202. Turning to Figure 4, in block 401, the AMF 202 receives a protocol data unit, PDU, session establishment request message. Block 401 is operation 201 of Figure 2 from the perspective of the AMF 202. In block 403, the AMF 202 transmits, to the SMF 204, a PDU session create request having a power saving UE parameter and an estimated next UE available time parameter. Block 403 is operation 203 of Figure 2 from the perspective of the AMF 202.
[0070] In block 405, the AMF 202, receives from the SMF 204, a PDU session create response having a support for power saving UE parameter. Block 405 is operation 205 of Figure 2 from the perspective of the AMF 202.
[0071] In block 407, the AMF 202, transmits to the UE 200, a PDU session establishment accept message. Block 407 is operation 211 of Figure 2 from the perspective of the AMF 202. Figure 5 illustrates operations of Figure 3 from the perspective of the AMF 202. Turning to Figure 5, in block 501, the AMF 202 receives a PDU session modification request message from the UE 200. Block 501 is operation 301 of Figure 3 from the perspective of the AMF 202.
[0072] In block 503, the AMF 202 transmits, to the SMF 204, a PDU session update request having a power saving UE parameter and an estimated next UE available time parameter. Block 503 is operation 303 of Figure 3 from the perspective of the AMF 202.
[0073] In block 505, the AMF 202, receives from the SMF 204, a PDU session update response having a support for power saving UE parameter. Block 505 is operation 305 of Figure 3 from the perspective of the AMF 202.
[0074] In block 507, the AMF 202, transmits to the UE 200, a PDU session modification command message. Block 507 is operation 311 of Figure 3 from the perspective of the AMF 202.
[0075] In block 509, the AMF 202, receives from the UE 200, a PDU session modification complete message. Block 507 is operation 313 of Figure 3 from the perspective of the AMF 202.
[0076] Figure 6 illustrates further operations of Figure 2 and Figure 3 from the perspective of the AMF 202. Turning to Figure 6, in block 601, the AMF 202 receives, from the SMF 204, a communication transfer request having a subscribe for UE reachable parameter. Block 401 is operation 207 of Figure 2 and operation 307 of Figure 3 from the perspective of the AMF 2022. In block 603, the AMF 202 assigns a subscription ID for UE reachability to the SMF 204. In Block 605, the AMF 202 transmits, to the SMF 204, a communication message transfer response having the subscription ID for UE reachability assigned to the SMF 204. Block 605 is operation 209 of Figure 2 and operation 309 of Figure 3 from the perspective of the AMF 202.
[0077] In block 607, the AMF 200 transmits, to the SMF, a UE reachable message having a remaining UE reachable time parameter. Block 607 is operation 213 of Figure 2 and operation 315 of Figure 3 from the perspective of the AMF 202.
[0078] Figure 7 illustrates operations of Figure 2 from the perspective of the SMF 204. Turning to Figure 7, in block 701, the SMF 204 receives, from the AMF 202, a PDU session create request. having a power saving UE parameter and an estimated next UE available time parameter. Block 701 is operation 203 of Figure 2 from the perspective of the SMF 204.
[0079] In block 703, the SMF 204, transmits to the AMF 202, a PDU session create response having a support for power saving UE parameter. Block 703 is operation 205 of Figure 2 from the perspective of the SMF 204.
[0080] Figure 8 illustrates operations of Figure 3 from the perspective of the SMF 204. Turning to Figure 8, in block 801, the SMF 204 receives, from the AMF 202, a PDU session update request having a power saving UE parameter and an estimated next UE available time parameter. Block 801 is operation 303 of Figure 3 from the perspective of the SMF 204.
[0081] In block 803, the SMF 204, transmits to the AMF 202, a PDU session update response having a support for power saving UE parameter. Block 803 is operation 305 of Figure 3 from the perspective of the SMF 204.
[0082] Figure 9 illustrates further operations of Figure 2 and Figure 3from the perspective of the SMF 204. Turning to Figure 9, in block 901, the SMF 202 transmits, to the AMF 202, a communication transfer request having a subscribe for UE reachable parameter. Block 901 is operation 207 of Figure 2 and operation 307 of Figure 3 from the perspective of the SMF 204. In block 903, the SMF 204 receives, from the AMF 202, a communication message transfer response having a subscription ID for UE reachability assigned to the SMF 204. Block 903 is operation 209 of Figure 2 and operation 309 of Figure 3 from the perspective of the SMF 204. In block 905, the SMF 204 receives, from the AMF 202, a UE reachable message having a remaining UE reachable time parameter. Block 905 is operation 213 of Figure 2 and operation 315 of Figure 3 from the perspective of the SMF 204.
[0083] FigurelO illustrates a second scenario where the UE 200 is in CM-Idle / unreachable or RRC (radios resource control)-Inactive / unreachable and there is a need to send downlink signaling or downlink user data from the SMF 204. In such a scenario, a Network triggered Service Request procedure is triggered.
[0084] Examples of applicable procedures:
[0085] NAS and NG-AP message from SMF SMF setup of DL data
[0086] Prerequisite: UE is a RedCap UE 100 and UE power saving is activated (DRX, eDRX, or MICO) or there is a need to apply UE power saving.
[0087] In Figure 10, the RedCap device 100 is in CM-Idle or is non-reachable and an SMF request with UE interaction is received by the AMF 202. The failure response indicates that the RedCap devicelOO is not reachable (e.g., 504 Gateway timeout and UE NOT REACHABLE) and the AMF 202 adds informational information on UE available time.
[0088] In operation 1001, the SMF 204 transmits a request with UE interaction required message to the AMF 202, the request identifying a UE with which UE interaction is required. In some embodiments, the request includes or is transmitted with a Subscribe for UE reachable parameter. The Subscribe for UE Reachable parameter indicates that the SMF 204 wants additional information in case the AMF 202 provides an unsuccessful response that the UE 200 is not reachable. In other words, the Subscribe for UE reachable parameter is an optional parameter and is used by the SMF 204 when the SMF 204 knows that the UE 200 is a power saving UE and wants to subscribe to when the UE is reachable. In some embodiments, the request also includes an extended buffering support on whether the SMF 204 is providing extended buffering support.
[0089] In operation 1003, responsive to the UE 200 not being reachable (e.g., the UE 200 is in Idle mode and UE power saving applies or is in RRC -Inactive and UE power saving applies), the AMF 202 transmits a failure response message to the SMF 204. The failure response message may include a 504 gateway timeout, a UE Not Reachable indication, an estimated maximum waiting time (if extended buffering support indication was included in the received request) and an estimated next UE available time parameter and a subscription ID for UE reachability assigned by the AMF 202 to the SMF 204.
[0090] The estimated next UE available time parameter indicates the time the UE 200 is expected to return to being reachable - e.g., CM-Connected for MICO UE (maximum time based on e.g., periodic registration) or DRX / eDRX cycle length. If no MICO or DRX / eDRX is activated, the value is set to FALSE. The SMF 204 can use the value of the estimated next UE available time parameter as a prediction of when the UE will become available. The parameter may be a new parameter or included as part of an existing parameter with changed condition. The SMF 204 shall not send any new request to AMF 202 with UE interaction required until after a UE Reachable message (see below) has been received and a corresponding remaining UE reachable time parameter indicates that the UE 200 is still reachable.
[0091] The AMF 202 includes the Subscription ID for UE Reachability if the SMF 204 has asked for it e.g., for MICO and DRX / eDRX active UEs or other reasons. The parameter is included if the SMF 204 has provided Subscribe for UE Reachable in the request message.
[0092] In operation 1005, the AMF 202 transmits a UE Reachable message to the SMF 204. The UE Reachable is sent from the AMF 202 when the UE 200 is reachable if Subscribe for UE Reachable is included in the SMF request and the AMF 202 has responded with Subscription ID for UE Reachability. The UE Reachable message includes or is transmited with a remaining UE reachable time parameter. The remaining UE reachable time parameter indicates the Time period that AMF can hold the UE in CM-Connected and the UE 200 is reachable.
[0093] In operation 1007, the SMF 204 transmits a request with UE interaction required message to the AMF 202. The request with UE interaction required is transmited after the SMF 204 has received the UE Reachable message and the remaining UE reachable time parameter indicates the UE is still reachable.
[0094] As can be seen from the above, in network triggered service requests as described above, the following advantages can be achieved:
[0095] The AMF 202 can provide information when the UE 200 is assumed to be available together with the finer granularity UE reachable notifications to the SMF 204. The SMF 204 then can avoid sending requests when the 200 UE is not reachable.
[0096] The SMF 204 obtains prediction information when the UE 200 is available and reachable. The SMF 204 can schedule for new request with UE interaction required.
[0097] Decreased signaling (no Subscribe for UE Reachable sent from the SMF 204 to the AMF 202) by the SMF 204 avoiding retries of sending Requests with UE interaction required messages while the UE 200 is unreachable.
[0098] The AMF 202 can trigger UE reachable notification to the SMF 204 without the SMF 204 sending a specific "subscribe" message.
[0099] The AMF 202 provides the SMF 204 with information for how long the UE 200 is reachable. This can be used by the SMF 204 to determine times the UE is likely to be reachable.
[0100] Figure 11 illustrates operations of Figure 10 from the perspective of the AMF 202. Turning to Figure 11, in block 1101, the AMF 202 receives, from the SMF 204, a request with UE interaction required message, the request identifying a UE with which UE interaction is required and having a Subscribe for UE reachable parameter. Block 1101 is operation 1001 of Figure 10 from the perspective of the AMF 202.
[0101] In block 1103, the AMF 202, responsive to the UE 200 not being reachable, transmits, to the SMF 204, a failure response message having an estimated next UE available time parameter and a subscription ID for UE reachability. The failure response message in some embodiments also includes a 504 gateway timeout and a UE_Not_Reachable indication. Responsive to the extended buffering support indication being included in the request with UE interaction required message, the failure response further includes an estimated maximum waiting time. Block 1103 is operation 1003 of Figure 10 from the perspective of the AMF 202. In block 1105, the AMF 202 transmits, to the SMF 204, a UE Reachable message having a remaining UE reachable time parameter. Block 1105 is operation 1005 of Figure 10 from the perspective of the AMF 202.
[0102] Figure 12 illustrates operations of Figure 10 from the perspective of the SMF 204. Turning to Figure 12, in block 1201, the SMF 204 transmits, to the AMF 202, a request with UE interaction required message, the request with UE interaction required message identifying a UE 200 with which UE interaction is required and having a Subscribe for UE reachable parameter. The Subscribe for UE reachable parameter is an optional parameter and is used by the SMF 204 when the SMF 204 knows that the UE 200 is a power saving UE and wants to subscribe to when the UE is reachable. Block 1201 is operation 1001 of Figure 10 from the perspective of the SMF 204. In some embodiments, the request with UE interaction required message includes an extended buffering support indication.
[0103] In block 1203, the SMF 204 receives, from the AMF 204, a failure response message having an estimated next UE available time parameter and responsive to the SMF 204 transmitting the Subscribe for UE reachable parameter, a subscription ID for UE reachability. The failure response message in some embodiments also includes a 504 gateway timeout, and a UE Not Reachable indication. When the extended buffering support indication was included in the received request, the failure response further includes an estimated maximum waiting time. Block 1203 is operation 1003 of Figure 10 from the perspective of the SMF 204.
[0104] In block 1205, the SMF 204 receives, from the AMF 202, a UE Reachable message having a remaining UE reachable time parameter.
[0105] In some embodiments, the SMF 204 transmits another request with UE interaction required message. The request with UE interaction required is transmitted after the UE reachable message has been received and the corresponding remaining UE reachable time parameter indicates that the UE 200 is still reachable.
[0106] It can be seen that an enhanced handling of UE power saving in the core network, impacting both the (consumer) SMF, for which a Request with UE interaction required message is needed to be sent, and the AMF has been presented herein. As the AMF is aware of if power saving applies to the UE and how the UE is allowed to access the network again, an estimated time the UE is expected to return to CM-Connected / reachable is provided from the AMF to the SMF together with an indication that UE power saving applies. By that, the SMF knows when the same or a new Request with UE interaction required message can be sent with a failure response not likely to be sent by the AMF. The SMF acknowledges the handling of UE power saving. Optimization of UE reachable handling is also provided. UE reachable notification can be provided to SMF the next time the UE is reachable. This is not only related to when UE power saving applies, but can be a general method. In the UE reachable notification, an indication with the time period the UE will be reachable and is in CM-Connected.
[0107] Similar to the SMF 204, the enhanced handling of UE power savings can impact a policy control function, PCF, (designated as PCF 206 herein). Figure 13 illustrates a scenario where the enhanced UE power handling can be used during an AM (access and mobility) Policy Association Establishment. Figure 14 illustrates where the enhanced UE power handling can be used during AM Policy Association Modification. These figures are a simplified view of Registration only including some NAS (Non Access Stratum) signaling and relevant policy signaling between AMF and PCF. In Figure 13 and Figure 14, the UE 200 may be a redcap device 100, a UE 3312A-3312D, a UE 3400, or a UE 3806. The AMF 202 may be implemented in a core network node 3308, a network node 3310A-3310B, a network node 3500, a virtual node 3702, or network node 3704. Similarly, the PCF 206 may be implemented in a core network node 3308, a network node 3310A-3310B, a network node 3500, a virtual node 3702, or network node 3704.
[0108] Turning to Figure 13, in operation 1301, the UE 200 transmits a Registration Request to the AMF 202 for establishing an AM policy association establishment.
[0109] In operation 1303, the AMF transmits an AM policy control create request. In some embodiments, the AM policy control create request is aNpcf_AMPolicyControl_Create Request. Information included in or transmitted with the AM policy control create request includes a Power Saving UE parameter and an Estimated Next UE Available Time parameter. The power saving UE parameter indicates a consumer (e.g., a PCF) cannot get immediate response when the UE 200 is needed to be contacted. Power saving UE is e.g., a MICO activated UE and / or a UE using DRX / eDRX. The parameter may indicate if power saving for the UE 200 is changed i.e., enabled or disabled.
[0110] The Estimated Next UE Available Time parameter is the time the UE 200 is expected to return to being reachable (e.g., is in CM-Connected (based on e.g., periodic registration timer)).
[0111] NOTE: Estimated Next UE Available Time gives a prediction when the UE 200 may return to CM-Connected (i.e., becomes reachable). This is typically a maximum time. The UE 200 may choose to return earlier and if so, the UE reachable notification will give the moment when the UE 200 returns to CM-Connected and thus a Request with UE interaction required message can be sent to the AMF 202 immediately for the buffered request, meanwhile the Remaining UE Reachable Time can help the PCF 206 in deciding if a new request should be sent or if it should be buffered without trying to contact the AMF 202 again.
[0112] In operation 1305, the PCF 206 transmits an AM policy control create response to the AMF 202. In some embodiments, the AM policy control create response is a
[0113] Npcf AMPolicyControl Create Response. Information included in or transmitted with the AM policy control create response includes a Support for Power Saving UE parameter. This parameter indicates that the receiving network function (NF) (e.g., the PCF 206) acknowledges support of reception and handling of ‘Power saving UE’ and handling of ‘Estimated Next UE Available Time’.
[0114] In operation 1307, the AMF 200 transmits a Registration Accept message to the UE 200.
[0115] In operation 1309, the PCF 206 transmits a message to the AMF 202. In some embodiments, the message is a Namf_Communication_N!N2MessageTransferReq message. Information included in or transmitted with the message includes a Subscribe for UE Reachable parameter. The Subscribe for UE Reachable parameter indicates that the PCF 206 needs to be informed when the UE 200 is reachable again (i.e., the next time the UE is reachable). This message may happen before or after the Registration Accept is sent.
[0116] In operation 1311, the AMF 202 transmits a response message to the PCF 206. In some embodiments, the communication message transfer response is a Namf_Communication_NlN2MessageTransferRsp message. Information included in or transmitted with the response message includes a subscription ID for UE reachability. The Subscription ID for UE Reachability indicates the ID of the UE Reachable subscription that the AMF 202 has created for the requesting NF (e.g., the PCF 206). It will be used when the AMF 202 detects the UE 200 is reachable and notifies the PCF 206 of the UE Reachable event.
[0117] In operation 1313, the AMF 202 transmits a UE Reachable message to the PCF 206. Information included in or transmitted with the UE Reachable message includes a Remaining UE Reachable Time parameter. The Remaining UE Reachable Time parameter indicates a time period that the AMF 202 can hold the UE 200 in connected mode (e.g., CM-Connected) and the UE 200 is reachable.
[0118] In operation 1315, the PCF 206 transmits a Request with UE interaction required message to the AMF 202. The Request with UE interaction required message may happen after the NF (e.g., the PCF 204) has received the UE Reachable message from the AMF 200. This is part of Network initiated Service Requests described hereinbelow.
[0119] For AM policy association modifications, similar messages can be used in the AM policy association modification procedures. Figure 14 illustrates an AM policy association modification procedure from the perspective of the AMF 202 requesting session modification. Turning to Figure 14, in operation 1401, the UE 200 transmits a registration request to the AMF 202. In operation 1403, the AMF transmits an AM policy control update request. In some embodiments, the PDU session update request is aNpcf_AMPolicyControl_Update Request. Information included in or transmitted with the AM policy control update request includes the Power Saving UE parameter and the Estimated Next UE Available Time parameter described above.
[0120] In operation 1405, the PCF 206 transmits an AM policy control update response to the AMF 202. In some embodiments, the AM policy control update response is a
[0121] Npcf AMPolicyControl Update Response. Information included in or transmitted with the PDU session create response includes a Support for Power Saving UE parameter.
[0122] In operation 1407, the AMF 200 transmits a Registration Accept message to the UE 200.
[0123] In operation 1409, the PCF 206 transmits a communication message to the AMF 202. In some embodiments, the communication message is a Namf_Communication_NlN2MessageTransferReq message. Information included in or transmitted with the communication message includes the Subscribe for UE Reachable parameter.
[0124] In operation 1411, the AMF 202 transmits a response message to the PCF 206. In some embodiments, the response message is aNamf_Communication_NlN2MessageTransferRsp message. Information included in or transmitted with the communication message transfer response includes the subscription ID for UE reachability.
[0125] In operation 1413, the AMF 202 transmits a UE Reachable message to the PCF 206. Information included in or transmitted with the UE Reachable message includes the Remaining UE Reachable Time parameter.
[0126] In operation 1415, the PCF 206 transmits a Request with UE interaction required message to the AMF 202. The Request with UE interaction required message may happen after the NF (e.g., the PCF 206) has received the UE Reachable message from the AMF 200 and the UE 200 is reachable. This is part of network initiated Service Requests described hereinbelow.
[0127] As can be seen from the above, in PCF registration procedures, the following advantages may be achieved:
[0128] AM Policy Association Establishment and Modification:
[0129] The PCF 206 gets information of UE power saving early and does not have to do an attempt with failure outcome due to the UE 200 not being reachable. The PCF 206 also get the information for which UEs having power saving applies. The PCF 206 gets an assumed estimation when the UE 200 is available (maximum time). UE reachability notification to the PCF 206 applies already from the beginning and is triggered by the AMF 202 for power saving UEs which give a finer granularity.
[0130] The AMF 202 provides the PCF 206 with information for how long UE is reachable.
[0131] UE Policy Association Establishment:
[0132] The PCF 206 gets information of UE power saving early and does not have to do an attempt with failure outcome due to the UE 200 not being reachable. The PCF 206 also gets the information for which UEs where power saving applies.
[0133] The PCF 206 get an assumed estimation when the UE 200 is available (maximum time). UE reachability notification to the PCF 206 applies already from the beginning and is triggered by the AMF 202 for power saving UEs which give a finer granularity.
[0134] Decreased signaling (no Subscribe for UE Reachable sent from the PCF 206 to the AMF 202) The AMF 202 provides the PCF 206 with information for how long UE is reachable.
[0135] Note that if the PCF 206 will seldom transit a Request with UE interaction required but has subscribed for the UE Reachable parameter and the AMF 202 is sending UE Reachable messages when the PCF 206 does not have anything to send to the UE, the above may result in increased signaling.
[0136] Figure 15 illustrates operations of UE Policy Association Establishment (3GPP TS 23.502 4.16.11) including UE Configuration Update procedure (3GPP TS 23.502 4.2.4.3). This could be used for URSP (UE Route Selection Policy) usage. Figure 15 is a simplified view of Registration only including some NAS (Non Access Stratum) signaling and relevant policy signaling between the AMF 202 and the PCF 206. The policy includes UE policy delivery from the PCF 206 to the UE 200 via the AMF 202.
[0137] Operations 1501-1511 and 1517-1519 are similar to operations 1301-1315 with the difference that the subscribe for UE reachable and subscription for UE reachability are sent via a Namf_Communication_NlN2MessageTransferReq message and a Namf_Communication_NlN2MessageTransferRsp message, respectively.
[0138] The Namf_Communication_NlMessageNotify Request in operation 1513 and the Namf_Communication_NlMessageNotify Response in operation 1515 are used to send messages to and from the AMF 202 and PCF 206.
[0139] Figurel6 illustrates another scenario where the UE 200 is in CM-Idle / unreachable or RRC (radios resource control)-Inactive / unreachable and there is a need to send downlink signaling or downlink user data from the PCF 206. In such a scenario, a Network triggered Service Request procedure is triggered. Examples of applicable procedures:
[0140] UE Policy Association Modification initiated by the PCF 206 (e.g., 3GPP TS 23.502 4.16.12.2) AM Policy Association Modification initiated by the PCF 206 (e.g., 3GPP TS 23.502 4.16.2.2) These UE policy association procedures can be used e.g., for URSP usage.
[0141] Prerequisite: UE is a RedCap UE 100 and UE power saving is activated (DRX, eDRX, or MICO) or there is a need to apply UE power saving.
[0142] In Figure 16, the RedCap device 100 is in CM-Idle or is non-reachable and a PCF request with UE interaction is received by the AMF 202. The failure response indicates that the RedCap devicelOO is not reachable (e.g., 504 Gateway timeout and UE NOT REACHABLE) and the AMF 202 adds informational information on UE available time.
[0143] In operation 1601, the PCF 206 transmits a request with UE interaction required message to the AMF 202, the request identifying a UE with which UE interaction is required. In some embodiments, the request includes or is transmitted with a Subscribe for UE reachable parameter. The Subscribe for UE Reachable parameter indicates that the PCF 206 wants additional information in case the AMF 202 provides an unsuccessful response that the UE 200 is not reachable. In other words, the Subscribe for UE reachable parameter is an optional parameter and is used by the PCF 206 when the PCF 206 knows that the UE 200 is a power saving UE and wants to subscribe to when the UE is reachable.
[0144] In operation 1603, responsive to the UE 200 not being reachable (e.g., the UE 200 is in Idle mode and UE power saving applies or is in RRC -Inactive and UE power saving applies), the AMF 202 transmits a failure response message to the PCF 206. The failure response message may include a 504 gateway timeout, a UE_Not_Reachable indication, and an estimated next UE available time parameter and a subscription ID for UE reachability assigned by the AMF 202 to the PCF 206.
[0145] The estimated next UE available time parameter indicates the time the UE 200 is expected to return to being reachable - e.g., CM-Connected for MICO UE (maximum time based on e.g., periodic registration) or DRX / eDRX cycle length. If no MICO or DRX / eDRX is activated, the value is set to FALSE. The PCF 206 can use the value of the estimated next UE available time parameter as a prediction of when the UE will become available. The parameter may be a new parameter or included as part of an existing parameter with changed condition. The PCF 206 shall not send any new request to AMF 202 with UE interaction required until after a UE Reachable message (see below) has been received and a corresponding remaining UE reachable time parameter indicates that the UE 200 is still reachable. The Subscription ID for UE Reachability is included by the AMF 202 if the PCF 206 has asked for it e.g., for MICO and DRX / eDRX active UEs or other reasons. The parameter is included if the PCF 206 has provided Subscribe for UE Reachable in the request message.
[0146] In operation 1605, the AMF 202 transmits a UE Reachable message to the PCF 206. The UE Reachable is sent from the AMF 202 when the UE 200 is reachable if Subscribe for UE Reachable is included in the PCF request and the AMF 202 has responded with Subscription ID for UE Reachability. The UE Reachable message includes or is transmitted with a remaining UE reachable time parameter. The remaining UE reachable time parameter indicates the Time period that AMF can hold the UE in CM-Connected and the UE 200 is reachable.
[0147] In operation 1607, the PCF 206 transmits a request with UE interaction required message to the AMF 202. The request with UE interaction required is transmitted after the PCF 206 has received the UE Reachable message and the remaining UE reachable time parameter indicates the UE is still reachable.
[0148] As can be seen from the above, in network triggered service requests as described above, the following advantages can be achieved:
[0149] The AMF 202 can provide information when the UE 200 is assumed to be available together with the finer granularity UE reachable notifications to the PCF 206. The PCF 206 then can avoid sending requests when the 200 UE is not reachable.
[0150] The PCF 206 obtains prediction information when the UE 200 is available and reachable. The PCF 206 can schedule for new request with UE interaction required.
[0151] Decreased signaling (no Subscribe for UE Reachable sent from the PCF 206 to the AMF 202) by the PCF 206 avoiding retries of sending Requests with UE interaction required messages while the UE 200 is unreachable.
[0152] The AMF 202 can trigger UE reachable notification to the PCF 206 without the PCF 206 sending a specific "subscribe" message.
[0153] The AMF 202 provides the PCF 206 with information for how long the UE 200 is reachable. The PCF 206 can use this information to determine times the UE is likely to be reachable.
[0154] Figure 17 illustrates operations of Figure 13 and 15 from the perspective of the AMF 202. Turning to Figure 17, in block 1701, the AMF 202 receives a registration request message from the UE 200 for establishing an AM policy association establishment or UE policy association establishment. Block 1701 is operation 1301 of Figure 13 and block 1501 of Figure 15 from the perspective of the AMF 202.
[0155] In block 1703, the AMF 202 transmits, to the PCF 206, a policy create request having a power saving UE parameter and an estimated next UE available time parameter. Block 1703 is operation 1303 of Figure 13 and operation 1505 of Figure 15 from the perspective of the AMF 202.
[0156] In block 1705, the AMF 202, receives from the PCF 206, a policy create response having a support for power saving UE parameter. Block 1705 is operation 1305 of Figure 13 and operation 1507 from the perspective of the AMF 202.
[0157] In block 1707, the AMF 202, transmits to the UE 200, a registration accept message. Block 1707 is operation 1307 of Figure 13 and operation 1503 of Figure 15 from the perspective of the AMF 202.
[0158] Figure 18 illustrates operations of Figure 14 from the perspective of the AMF 202. Turning to Figure 18, in block 1801, the AMF 202 receives a registration request message from the UE 200. Block 1801 is operation 1401 of Figure 14 from the perspective of the AMF 202.
[0159] In block 1803, the AMF 202 transmits, to the PCF 206, a policy control update request having a power saving UE parameter and an estimated next UE available time parameter. Block 1803 is operation 1403 of Figure 14 from the perspective of the AMF 202.
[0160] In block 1805, the AMF 202 receives from the PCF 206, a policy control update response having a support for power saving UE parameter. Block 1805 is operation 1305 of Figure 13 and operation 1507 of Figure 15 from the perspective of the AMF 202.
[0161] In block 1807, the AMF 202 transmits to the UE 200, a registration accept message. Block 1807 is operation 1407 of Figure 14 from the perspective of the AMF 202.
[0162] Figure 19 illustrates further operations of Figures 13-15 from the perspective of the AMF 202. Turning to Figure 19, in block 1901, the AMF 202 receives, from the PCF 206, a message having a subscribe for UE reachable parameter. Block 1901 is operation 1309 of Figure 13, operation 1409 of Figure 14, and operation 1509 of Figure 15 from the perspective of the AMF 202.
[0163] In block 1903, the AMF 202 assigns a subscription ID for UE reachability to the PCF 206. In Block 1905, the AMF 202 transmits, to the PCF 206, a response having the subscription ID for UE reachability assigned to the PCF 206. Block 1905 is operation 1311 of Figure 13, operation 1411 of Figure 14, and operation 1511 of Figure 15 from the perspective of the AMF 202. In block 1907, the AMF 200 transmits, to the PCF 106, a UE reachable message having a remaining UE reachable time parameter. Block 1907 is operation 1313 of Figure 13, operation 1413 of Figure 14, and operation 1517 of Figure 15 from the perspective of the AMF 202. Figure 20 illustrates operations of Figure 16 from the perspective of the AMF 202. Turning to Figure 20, in operation 2001, the AMF 202 receives, from the PCF 206, a request with UE interaction required message, the request identifying a UE with which UE interaction is required and having a Subscribe for UE reachable parameter. Block 2001 is operation 1601 of Figure 16 from the perspective of the AMF 202.
[0164] In block 2003, the AMF 202, responsive to the UE 200 not being reachable, transmits, to the PCF 206, a failure response message having an estimated next UE available time parameter and a subscription ID for UE reachability. The failure response message in some embodiments also includes a 504 gateway timeout and a UE_Not_Reachable indication. Block 2003 is operation 1603 of Figure 16 from the perspective of the AMF 202.
[0165] In block 2005, the AMF 202 transmits, to the PCF 206, a UE Reachable message having a remaining UE reachable time parameter. Block 2005 is operation 1605 of Figure 16 from the perspective of the AMF 202.
[0166] Figure 21 illustrates operations of Figure 13 and Figure 15 from the perspective of the PCF 206. Turning to Figure 21, in block 2101, the PCF 206 receives, from the AMF 202, an AM policy control create request or UE policy control create request having a power saving UE parameter and an estimated next UE available time parameter. Block 2101 is operation 1303 of Figure 13 and operation 1505 of Figure 15 from the perspective of the PCF 206.
[0167] In block 2103, the PCF 206, transmits to the AMF 202, an AM policy control create response or UE policy association response having a support for power saving UE parameter. Block 2103 is operation 1305 of Figure 13 and operation 1507 of Figure 15 from the perspective of the PCF 206.
[0168] Figure 22 illustrates operations of Figure 14 from the perspective of the PCF 206. Turning to Figure 22, in block 2201, the PCF 206 receives, from the AMF 202, a policy control update request or a UE policy control update request having a power saving UE parameter and an estimated next UE available time parameter. Block 2201 is operation 1403 of Figure 14 from the perspective of the PCF 206.
[0169] In block 2203, the PCF 206 transmits to the AMF 202, a policy control update response having a support for power saving UE parameter. Block 2203 is operation 1405 of Figure 14 from the perspective of the PCF 206.
[0170] Figure 23 illustrates further operations of Figures 13-15 from the perspective of the PCF 206. Turning to Figure 23, in block 2301, the PCF 202 transmits, to the AMF 202, a message having a subscribe for UE reachable parameter. Block 2301 is operation 1309 of Figure 13, operation 1409 of Figure 14 and operation 1509 of Figure 15 from the perspective of the PCF 206.
[0171] In block 2303, the PCF 206 receives, from the AMF 202, a response having a subscription ID for UE reachability assigned to the PCF 206. Block 2303 is operation 1311 of Figure 13, operation 1411 of Figure 14, and operation 1511 of Figure 15 from the perspective of the PCF 206. In block 2305, the PCF 206 receives, from the AMF 202, a UE reachable message having a remaining UE reachable time parameter. Block 2305 is operation 1313 of Figure 13, operation 1413 of Figure 14, and operation 1517 of Figure 15 from the perspective of the PCF 206. Figure 24 illustrates operations of Figure 16 from the perspective of the PCF 206. Turning to Figure 24, in block 2401, the PCF 206 transmits, to the AMF 202, a request with UE interaction required message, the request with UE interaction required message identifying a UE 200 with which UE interaction is required and having a Subscribe for UE reachable parameter. The Subscribe for UE reachable parameter is an optional parameter and is used by the PCF 206 when the PCF 206 knows that the UE 200 is a power saving UE and wants to subscribe to when the UE is reachable. Block 2401 is operation 1601 of Figure 16 from the perspective of the PCF 206. In block 2403, the PCF 206 receives, from the AMF 204, a failure response message having an estimated next UE available time parameter and responsive to the PCF 206 transmitting the Subscribe for UE reachable parameter, a subscription ID for UE reachability. The failure response message in some embodiments also includes a 504 gateway timeout, and a UE_Not_Reachable indication. Block 2403 is operation 1603 of Figure 16 from the perspective of the PCF 206.
[0172] In block 2405, the PCF 206 receives, from the AMF 202, a UE Reachable message having a remaining UE reachable time parameter. Block 2405 is operation 1605 of Figure 16 from the perspective of the PCF 206.
[0173] In some embodiments, the PCF 206 transmits another request with UE interaction required message. The request with UE interaction required is transmitted after the UE reachable message has been received and the corresponding remaining UE reachable time parameter indicates that the UE 200 is still reachable.
[0174] It can be seen that an enhanced handling of UE power saving in the core network, impacting both the (consumer) PCF 206, for which a Request with UE interaction required message is needed to be sent, and the AMF 202 has been presented herein. As the AMF 202 is aware of if power saving applies to the UE 200 and how the UE 200 is allowed to access the network again, an estimated time the UE 200 is expected to return to CM-Connected / reachable is provided from the AMF 204 to the PCF 206 together with an indication that UE power saving applies. By that, the PCF 206 knows when the same or a new Request with UE interaction required message can be sent with a failure response not likely to be sent by the AMF 202. The PCF 206 acknowledges the handling of UE power saving.
[0175] Optimization of UE reachable handling is also provided. UE reachable notification can be provided to the PCF 206 the next time the UE is reachable. This is not only related to when UE power saving applies, but can be a general method. In the UE reachable notification, an indication with the time period the UE will be reachable and is in CM-Connected.
[0176] The above description of the AMF, SMF and PCF operations can be extended to other network functions. This is illustrated in Figures 25-32.
[0177] Figures 25-28 illustrates operations of a network node having an AMF 202 communicating with an NF such as SMF 204, PCF 206, and the like. In the description that follows, the NF shall be designated as NF 204, 206 with the understanding that the NF can be other types of network functions. Turning to Figure 25, in block 2501, the AMF 202 receives a request message. For example, the request message can be a PDU session establishment request, a registration request for establishing an AM policy establishing an AM policy association establishment, and the like. In block 2503, the AMF 202 transmits, to the NF 204, 206 a create request having a power saving user equipment, UE, parameter and an estimated next UE available time parameter. These parameters have been described above. Block 2503 is similar to block 403 of Figure 4 and block 1701 of Figure 17.
[0178] In block 2505, the AMF receives, from the NF 204, 206, a create response having a support for power saving UE parameter. The support for power saving UE parameter has been described above. Block 2505 is similar to block 405 of Figure 4 and block 1705 of Figure 17.
[0179] In block 2507, the AMF 202 transmits, to the UE 200, an accept message. Block 2507 is similar to block 407 of Figure 4 and block 1707 of Figure 17.
[0180] Figure 26 illustrates operations to update a session, a policy, a parameter, etc. Turning to Figure 26, in block 2601, the AMF 202 receives an update request message. Block 2601 is similar to block 501 of Figure 5 and block 1801 of Figure 18.
[0181] In block 2603, the AMF 202 transmits, to the NF 204, 206, an update request having a power saving UE parameter and an estimated next UE available time parameter. The power saving UE parameter indicates an NF 204, 206 cannot obtain an immediate response from a UE 200 when the UE 200 is needed to be contacted. The estimated next UE available time parameter has been described above. Block 2603 is similar to block 503 of Figure 5 and block 1803 of Figure 18. In block 2605, the AMF 202 receives, from the NF 204, 206, an update response having a support for power saving UE parameter. The support of power saving UE parameter has been described above. Block 2605 is similar to block 505 of Figure 5 and block 1805 of Figure 18. In block 2607, the AMF 202 transmits, to the UE 200, an update response message. Block 2607 is similar to block 507 of Figure 5 and block 1807 of Figure 18.
[0182] Figure 27 illustrates further operations the AMF 202 performs in communicating with NF 204, 206. Turning to Figure 27, in block 2701, the AMF 202 receives, from the NF 204, 206, a communication transfer request having a subscribe for UE reachable parameter. The subscribe for UE reachable parameter has been described above. Block 2701 is similar to block 601 of Figure 6 and block 1901 of Figure 19.
[0183] In block 2703, the AMF 202 assigns a subscription ID for UE reachability to the NF 204, 206. Block 2703 is similar to block 603 of Figure 6 and block 1903 of Figure 19.
[0184] In block 2705, the AMF 202 transmits, to the NF 204, 206, a communication message transfer response having the subscription ID for UE reachability assigned to the NF 204, 206. Block 2705 is similar to block 605 of Figure 6 and block 1905 of Figure 19.
[0185] In block 2707, the AMF 202 transmits, to the NF 204, 206, a UE reachable message having a remaining UE reachable time parameter. The remaining reachable time parameter has been described above. Block 2707 is similar to block 607 of Figure 6 and block 1907 of Figure 19. Figure 28 illustrates further operations of the AMF 202. Turning to Figure 28, in block 2801, the AMF 202 receives, from the NF 204, 206, a request with UE interaction required message, the request with UE interaction required message identifying a UE 200 with which UE interaction is required and having a Subscribe for UE reachable parameter. Block 2801 is similar to block 1101 of Figure 11 and block 2001 of Figure 20.
[0186] In block 2803, the AMF 202, responsive to the UE 200 not being reachable, transmits, to the NF 204, 206, a failure response message having an estimated next UE available time parameter and a subscription ID for UE reachability. Block 2803 is similar to block 1103 of Figure 11 and block 2003 of Figure 20.
[0187] In block 2805, the AMF 202, transmits to the NF 204, 206, a UE Reachable message having a remaining UE reachable time parameter. Block 2805 is similar to block 1105 of Figure 11 and block 2005 of Figure 20.
[0188] Figure 29 illustrates operations from the perspective of the NF 204, 206. Turning to Figure 29, in block 2901, the NF 204, 206 receives, from the AMF 202, a create request having a power saving user equipment, UE, parameter and an estimated next UE available time parameter. The power saving UE parameter and the estimated next UE available time parameter have been described above. Block 2901 is similar to block 701 of Figure 7 and block 2101 of Figure 21. In block 2903, the NF 204, 206 transmits, to the AMF 202, a create response having a support for power saving UE parameter. The support for power saving UE parameter has been described above. Block 2903 is similar to block 703 of Figure 7 and block 2103 of Figure 21.
[0189] Figure 30 illustrates operations from the perspective of the NF 204, 206 to update a parameter. The parameter may be a policy update request, a PDU session update request, and the like. Turning to Figure 30, in block 3001, the NF 204, 206 receives, from the AMF 202, an update request having the power saving user equipment, UE, parameter and the estimated next UE available time parameter. The power saving UE parameter indicates a consumer (e.g., NF 204, 206) cannot obtain an immediate response from a UE (200) when the UE (200) is needed to be contacted. The estimated next UE available time parameter has been described above. Block 3001 is similar to block 801 of Figure 8 and block 2201 of Figure 22.
[0190] In block 3003, the NF 204, 206 transmits, to the AMF 202, an update response having a support for power saving UE parameter. The support for power saving UE parameter has been described above. Block 3003 is similar to block 803 of Figure 8 and block 2203 of Figure 22.
[0191] Figure 31 illustrates further operations of the NF 204, 206. Turning to Figure 31, in block 3101, the NF 204, 206 transmits, to the AMF 202, a communication transfer request having a subscribe for UE reachable parameter. The subscribe for UE reachable parameter has been described above. Block 3101 is similar to block 901 of Figure 9 and block 2301 of Figure 23.
[0192] In block 3103, the NF 204, 206 receives, from the AMF 202, a communication message transfer response having a subscription ID for UE reachability assigned to the NF 204, 206. The subscription for UE reachability has been described above. Block 3103 is similar to block 903 of Figure 9 and block 2303 of Figure 23.
[0193] In block 3105, the NF 204, 206 receives, from the AMF 202, a UE reachable message having a remaining UE reachable time parameter. The remaining UE reachable time parameter has been described above. Block 3105 is similar to Block 905 of Figure 9 and block 2305 of Figure 23. Figure 32 illustrates further operations of the NF 204, 206. In block 3201, the NF 204, 206 transmits, to an AMF 202, a request with UE interaction required message, the request identifying a UE 200 with which UE interaction is required and having a Subscribe for UE reachable parameter. Block 3201 is similar to block 1201 of Figure 12 and block 2401 of Figure 24.
[0194] In block 3203, the NF 204, 206 receives, from the AMF 202, a failure response message having an estimated next UE available time parameter and a subscription ID for UE reachability. These parameters have been described above. Block 3202 is similar to block 1203 of Figure 12 and block 2403 of Figure 24.
[0195] In block 3205, the NF 204, 206 receives, from the AMF 202, a UE Reachable message having a remaining UE reachable time parameter. The remaining UE reachable time parameter has been described above. Block 3205 is similar to block 1205 of Figure 12 and block 2405 of Figure 24. Figure 33 shows an example of a communication system 3300 in accordance with some embodiments. In the example, the communication system 3300 includes a telecommunication network 3302 that includes an access network 3304, such as a radio access network (RAN), and a core network 3306, which includes one or more core network nodes 3308. The access network 3304 includes one or more access network nodes, such as network nodes 3310A and 3310B (one or more of which may be generally referred to as network nodes 3310), or any other similar 3rdGeneration Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 3310 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 3312A, 3312B, 3312C, and 3312D (one or more of which may be generally referred to as UEs 3312) to the core network 3306 over one or more wireless connections.
[0196] 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 3300 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 3300 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0197] The UEs 3312 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 3310 and other communication devices. Similarly, the network nodes 3310 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 3312 and / or with other network nodes or equipment in the telecommunication network 3302 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 3302.
[0198] In the depicted example, the core network 3306 connects the network nodes 3310 to one or more hosts, such as host 3316. 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 3306 includes one more core network nodes (e.g., core network node 3308) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 3308. 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). The host 3316 may be under the ownership or control of a service provider other than an operator or provider of the access network 3304 and / or the telecommunication network 3302, and may be operated by the service provider or on behalf of the service provider. The host 3316 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.
[0199] As a whole, the communication system 3300 of Figure 33 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), New Radio (NR), 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 (Light Fidelity), and / or any low-power wide-area network (LPWAN) standards such as LoRa (Long Range) and Sigfox.
[0200] In some examples, the telecommunication network 3302 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 3302 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 3302. For example, the telecommunications network 3302 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT (Internet of Things) services to yet further UEs. In some examples, the UEs 3312 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 3304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 3304. 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).
[0201] In the example, the hub 3314 communicates with the access network 3304 to facilitate indirect communication between one or more UEs (e.g., UE 3312C and / or 3312D) and network nodes (e.g., network node 3310B). In some examples, the hub 3314 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 3314 may be a broadband router enabling access to the core network 3306 for the UEs. As another example, the hub 3314 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 3310, or by executable code, script, process, or other instructions in the hub 3314. As another example, the hub 3314 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 3314 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 3314 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 3314 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 3314 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
[0202] The hub 3314 may have a constant / persistent or intermittent connection to the network node 3310B. The hub 3314 may also allow for a different communication scheme and / or schedule between the hub 3314 and UEs (e.g., UE 3312C and / or 3312D), and between the hub 3314 and the core network 3306. In other examples, the hub 3314 is connected to the core network 3306 and / or one or more UEs via a wired connection. Moreover, the hub 3314 may be configured to connect to an M2M service provider over the access network 3304 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 3310 while still connected via the hub 3314 via a wired or wireless connection. In some embodiments, the hub 3314 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 3310B. In other embodiments, the hub 3314 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 331 OB, but which is additionally capable of operating as a communication start and / or end point for certain data channels. Figure 34 shows a UE 3400 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.
[0203] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
[0204] The UE 3400 includes processing circuitry 3402 that is operatively coupled via a bus 3404 to an input / output interface 3406, a power source 3408, a memory 3410, a communication interface 3412, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 34. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. The processing circuitry 3402 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 3410. The processing circuitry 3402 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 3402 may include multiple central processing units (CPUs).
[0205] In the example, the input / output interface 3406 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 3400. 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.
[0206] In some embodiments, the power source 3408 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 3408 may further include power circuitry for delivering power from the power source 3408 itself, and / or an external power source, to the various parts of the UE 3400 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging the power source 3408. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 3408 to make the power suitable for the respective components of the UE 3400 to which power is supplied.
[0207] The memory 3410 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 3410 includes one or more application programs 3414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 3416. The memory 3410 may store, for use by the UE 3400, any of a variety of various operating systems or combinations of operating systems. The memory 3410 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 3410 may allow the UE 3400 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 3410, which may be or comprise a device-readable storage medium.
[0208] The processing circuitry 3402 may be configured to communicate with an access network or other network using the communication interface 3412. The communication interface 3412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 3422. The communication interface 3412 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 3418 and / or a receiver 3420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 3418 and receiver 3420 may be coupled to one or more antennas (e.g., antenna 3422) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0209] In the illustrated embodiment, communication functions of the communication interface 3412 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.13, 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.
[0210] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 3412, 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). 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.
[0211] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), 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 3400 shown in Figure 34. 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 transmit 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.
[0212] 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.
[0213] Figure 35 shows a network node 3500 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)).
[0214] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as 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).
[0215] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).
[0216] The network node 3500 includes a processing circuitry 3502, a memory 3504, a communication interface 3506, and a power source 3508. The network node 3500 may be composed of multiple physically separate components (e.g., aNodeB 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 3500 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 3500 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 3504 for different RATs) and some components may be reused (e.g., a same antenna 3510 may be shared by different RATs). The network node 3500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 3500, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 3500.
[0217] The processing circuitry 3502 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 3500 components, such as the memory 3504, to provide network node 3500 functionality.
[0218] In some embodiments, the processing circuitry 3502 includes a system on a chip (SOC). In some embodiments, the processing circuitry 3502 includes one or more of radio frequency (RF) transceiver circuitry 3512 and baseband processing circuitry 3514. In some embodiments, the radio frequency (RF) transceiver circuitry 3512 and the baseband processing circuitry 3514 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 3512 and baseband processing circuitry 3514 may be on the same chip or set of chips, boards, or units.
[0219] The memory 3504 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 3502. The memory 3504 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 3502 and utilized by the network node 3500. The memory 3504 may be used to store any calculations made by the processing circuitry 3502 and / or any data received via the communication interface 3506. In some embodiments, the processing circuitry 3502 and memory 3504 is integrated.
[0220] The communication interface 3506 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 3506 comprises port(s) / terminal(s) 3516 to send and receive data, for example to and from a network over a wired connection. The communication interface 3506 also includes radio front-end circuitry 3518 that may be coupled to, or in certain embodiments a part of, the antenna 3510. Radio front-end circuitry 3518 comprises filters 3520 and amplifiers 3522. The radio front-end circuitry 3518 may be connected to an antenna 3510 and processing circuitry 3502. The radio front-end circuitry may be configured to condition signals communicated between antenna 3510 and processing circuitry 3502. The radio front-end circuitry 3518 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 3518 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 3520 and / or amplifiers 3522. The radio signal may then be transmitted via the antenna 3510. Similarly, when receiving data, the antenna 3510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 3518. The digital data may be passed to the processing circuitry 3502. In other embodiments, the communication interface may comprise different components and / or different combinations of components.
[0221] In certain alternative embodiments, the network node 3500 does not include separate radio frontend circuitry 3518, instead, the processing circuitry 3502 includes radio front-end circuitry and is connected to the antenna 3510. Similarly, in some embodiments, all or some of the RF transceiver circuitry 3512 is part of the communication interface 3506. In still other embodiments, the communication interface 3506 includes one or more ports or terminals 3516, the radio front-end circuitry 3518, and the RF transceiver circuitry 3512, as part of a radio unit (not shown), and the communication interface 3506 communicates with the baseband processing circuitry 3514, which is part of a digital unit (not shown).
[0222] The antenna 3510 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 3510 may be coupled to the radio front-end circuitry 3518 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 3510 is separate from the network node 3500 and connectable to the network node 3500 through an interface or port.
[0223] The antenna 3510, communication interface 3506, and / or the processing circuitry 3502 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 3510, the communication interface 3506, and / or the processing circuitry 3502 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.
[0224] The power source 3508 provides power to the various components of network node 3500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 3508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 3500 with power for performing the functionality described herein. For example, the network node 3500 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 3508. As a further example, the power source 3508 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.
[0225] Embodiments of the network node 3500 may include additional components beyond those shown in Figure 35 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 3500 may include user interface equipment to allow input of information into the network node 3500 and to allow output of information from the network node 3500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 3500. Figure 36 is a block diagram of a host 3600, which may be an embodiment of the host 3316 of Figure 33, in accordance with various aspects described herein. As used herein, the host 3600 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 3600 may provide one or more services to one or more UEs.
[0226] The host 3600 includes processing circuitry 3602 that is operatively coupled via a bus 3604 to an input / output interface 3606, a network interface 3608, a power source 3610, and a memory 3612. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 34 and 35, such that the descriptions thereof are generally applicable to the corresponding components of host 3600.
[0227] The memory 3612 may include one or more computer programs including one or more host application programs 3614 and data 3616, which may include user data, e.g., data generated by a UE for the host 3600 or data generated by the host 3600 for a UE. Embodiments of the host 3600 may utilize only a subset or all of the components shown. The host application programs 3614 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 3614 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 3600 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 3614 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
[0228] Figure 37 is a block diagram illustrating a virtualization environment 3700 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 3700 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.
[0229] Applications 3702 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 3700 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0230] Hardware 3704 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 3706 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 3708A and 3708B (one or more of which may be generally referred to as VMs 3708), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 3706 may present a virtual operating platform that appears like networking hardware to the VMs 3708.
[0231] The VMs 3708 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 3706. Different embodiments of the instance of a virtual appliance 3702 may be implemented on one or more of VMs 3708, 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.
[0232] In the context of NFV, a VM 3708 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 3708, and that part of hardware 3704 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 3708 on top of the hardware 3704 and corresponds to the application 3702. Hardware 3704 may be implemented in a standalone network node with generic or specific components. Hardware 3704 may implement some functions via virtualization. Alternatively, hardware 3704 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 3710, which, among others, oversees lifecycle management of applications 3702. In some embodiments, hardware 3704 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 3712 which may alternatively be used for communication between hardware nodes and radio units.
[0233] Figure 38 shows a communication diagram of a host 3802 communicating via a network node 3804 with a UE 3806 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 3312A of Figure 33 and / or UE 3400 of Figure 34), network node (such as network node 3310A of Figure 33 and / or network node 3500 of Figure 35), and host (such as host 3316 of Figure 33 and / or host 3600 of Figure 36) discussed in the preceding paragraphs will now be described with reference to Figure 38.
[0234] Like host 3600, embodiments of host 3802 include hardware, such as a communication interface, processing circuitry, and memory. The host 3802 also includes software, which is stored in or accessible by the host 3802 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 3806 connecting via an over-the-top (OTT) connection 3850 extending between the UE 3806 and host 3802. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 3850.
[0235] The network node 3804 includes hardware enabling it to communicate with the host 3802 and UE 3806. The connection 3860 may be direct or pass through a core network (like core network 3306 of Figure 33) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.
[0236] The UE 3806 includes hardware and software, which is stored in or accessible by UE 3806 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 3806 with the support of the host 3802. In the host 3802, an executing host application may communicate with the executing client application via the OTT connection 3850 terminating at the UE 3806 and host 3802. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 3850 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 3850.
[0237] The OTT connection 3850 may extend via a connection 3860 between the host 3802 and the network node 3804 and via a wireless connection 3870 between the network node 3804 and the UE 3806 to provide the connection between the host 3802 and the UE 3806. The connection 3860 and wireless connection 3870, over which the OTT connection 3850 may be provided, have been drawn abstractly to illustrate the communication between the host 3802 and the UE 3806 via the network node 3804, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
[0238] As an example of transmitting data via the OTT connection 3850, in step 3808, the host 3802 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 3806. In other embodiments, the user data is associated with a UE 3806 that shares data with the host 3802 without explicit human interaction. In step 3810, the host 3802 initiates a transmission carrying the user data towards the UE 3806. The host 3802 may initiate the transmission responsive to a request transmitted by the UE 3806. The request may be caused by human interaction with the UE 3806 or by operation of the client application executing on the UE 3806. The transmission may pass via the network node 3804, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 3812, the network node 3804 transmits to the UE 3806 the user data that was carried in the transmission that the host 3802 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 3814, the UE 3806 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 3806 associated with the host application executed by the host 3802.
[0239] In some examples, the UE 3806 executes a client application which provides user data to the host 3802. The user data may be provided in reaction or response to the data received from the host 3802. Accordingly, in step 3816, the UE 3806 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 3806. Regardless of the specific manner in which the user data was provided, the UE 3806 initiates, in step 3818, transmission of the user data towards the host 3802 via the network node 3804. In step 3820, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 3804 receives user data from the UE 3806 and initiates transmission of the received user data towards the host 3802. In step 3822, the host 3802 receives the user data carried in the transmission initiated by the UE 3806.
[0240] In an example scenario, factory status information may be collected and analyzed by the host 3802. As another example, the host 3802 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 3802 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 3802 may store surveillance video uploaded by a UE. As another example, the host 3802 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 3802 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.
[0241] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 3850 between the host 3802 and UE 3806, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 3802 and / or UE 3806. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 3850 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 3850 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 3804. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 3802. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3850 while monitoring propagation times, errors, etc.
[0242] Although the computing devices described herein (e.g., UEs, network nodes, hosts) 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.
[0243] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device- readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-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.
[0244] In the following some numbered embodiments are provided: 1. A method performed in a network node (3310A, 3310B, 3500, 3702, 3804) having an access and mobility management function, AMF, (202), the method comprising: receiving (2501) a request message; transmitting (2503), to a network function, NF, (204, 206), a create request having a power saving user equipment, UE, parameter and an estimated next UE available time parameter; receiving (2505), from the NF (204, 206), a create response having a support for power saving UE parameter; and transmitting (2507), to the UE (200), an accept message.
[0245] 2. The method of Embodiment 1, further comprising: receiving (2601) an update request message; transmitting (2603), to the NF (204, 206), an update request having a power saving UE parameter and an estimated next UE available time parameter; receiving (2605), from the NF (204, 206), an update response having a support for power saving UE parameter; and transmitting (2607), to the UE (200), an update response message.
[0246] 3. The method of any of Embodiments 1-2, wherein the power saving UE parameter indicates a consumer cannot obtain an immediate response from a UE (200) when the UE (200) is needed to be contacted.
[0247] 4. The method of any of Embodiments 1-3, wherein the estimated next UE available time parameter indicates a time the UE (200) is expected to return to being reachable.
[0248] 5. The method of any of Embodiments 1-4, wherein the support for power saving UE parameter indicates the NF (204, 206) acknowledges support of reception and handling of ‘Power saving UE’ and handling of ‘Estimated Next UE Available Time’.
[0249] 6. The method of any of Embodiments 1-5, further comprising: receiving (2701), from the NF (204, 206), a communication transfer request having a subscribe for UE reachable parameter; assigning (2703) a subscription ID for UE reachability to the NF (204, 206); transmitting (2705), to the NF (204, 206), a communication message transfer response having the subscription ID for UE reachability assigned to the NF (204, 206); and transmitting (2707), to the NF (204, 206), a UE reachable message having a remaining UE reachable time parameter.
[0250] 7. The method of Embodiment 6, wherein the subscribe for UE reachable parameter indicates that the NF (204, 206) needs to be informed when the UE (200) is reachable. 8. The method of any of Embodiments 6-7, wherein the remaining UE reachable time parameter indicates a time period that the AMF (202) can hold the UE 200 in a connected mode and the UE (200) is reachable.
[0251] 9. The method of any of Embodiments 1 -8, further comprising: receiving (2801), from a network function, NF, (204, 206), a request with UE interaction required message, the request with UE interaction required message identifying a UE (200) with which UE interaction is required and having a Subscribe for UE reachable parameter; responsive to the UE (200) not being reachable, transmitting (2803), to the NF (204, 206), a failure response message having an estimated next UE available time parameter and a subscription ID for UE reachability; and transmitting (2805), to the NF (204, 206), a UE Reachable message having a remaining UE reachable time parameter.
[0252] 10. The method of any of Embodiments 1-9, wherein the NF (204, 206) comprises a policy control function, PCF, (206) and the request message comprises a registration request for creating a policy control session at the PCF (206).
[0253] 11. The method of any of Embodiments 1-9, wherein the NF (204, 206) comprises a session management function, SMF, (204) and the request message comprises a protocol data unit, PDU, session establishment request.
[0254] 12. The method of Embodiment 11, wherein the update response message comprises a PDU session modification command message, the method further comprising: receiving, from the UE (200), a session modification complete message.
[0255] 13. A method performed in a network node (3310A, 3310B, 3500, 3702, 3804) having an access and mobility management function, AMF, (202), the method comprising: receiving (2801), from a network function, NF, (204, 206), a request with UE interaction required message, the request with UE interaction required message identifying a UE (200) with which UE interaction is required and having a Subscribe for UE reachable parameter; responsive to the UE (200) not being reachable, transmitting (2803), to the NF (204, 206), a failure response message having an estimated next UE available time parameter and a subscription ID for UE reachability; and transmitting (2805), to the NF (204, 206), a UE Reachable message having a remaining UE reachable time parameter.
[0256] 14. The method of Embodiment 13, wherein the failure response message further comprises a 504 gateway timeout and a UE_Not_Reachable indication 15. The method of any of Embodiments 13-14, wherein the Subscribe for UE Reachable parameter indicates that the NF (204, 206) needs to be informed when the UE (200) is reachable in case the AMF (202) provides a failure response message indicating that the UE (200) is not reachable.
[0257] 16. The method of any of Embodiments 13-15, wherein the estimated next UE available time parameter indicates a time the UE (200) is expected to return to being reachable.
[0258] 17. The method of any of Embodiments 13-16, wherein the remaining UE reachable time parameter indicates a time period that the AMF (202) can hold the UE (200) in connected mode and the UE (200) is reachable.
[0259] 18. The method of any of Embodiments 10-17, wherein the NF (204, 206) comprises a policy control function, PCF, (206).
[0260] 19. The method of Embodiment 10, wherein the NF (204, 206) comprises a session management function, SMF, (204), the request with UE interaction required message further comprising an extended buffering support indication.
[0261] 20. The method of Embodiment 19, wherein responsive to the extended buffering support indication being included in the request with UE interaction required message, the failure response further comprises an estimated maximum waiting time.
[0262] 21. The method of any of Embodiments 10-20, wherein the NF (204, 206) comprises a policy control function, PCF, (206).
[0263] 22. The method of any of Embodiments 10-20, wherein the NF (204, 206) comprises a session management function, SMF, (204).
[0264] 23. A method in a network node (3310A, 3310B, 3500, 3702, 3804) having a network function, NF, (204, 206), the method comprising: receiving (2901), from an access and mobility management function, AMF, (202), a create request having a power saving user equipment, UE, parameter and an estimated next UE available time parameter; and transmitting (2903), to the AMF (202), a create response having a support for power saving UE parameter.
[0265] 24. The method of Embodiment 23, further comprising: receiving (3001), from the AMF (202), an update request having the power saving user equipment, UE, parameter and the estimated next UE available time parameter; and transmitting (3003), to the AMF (202), an update response having a support for power saving UE parameter. 25. The method of any of Embodiments 23-24, wherein the power saving UE parameter indicates a consumer cannot obtain an immediate response from a UE (200) when the UE (200) is needed to be contacted.
[0266] 26. The method of any of Embodiments 23-25, wherein the estimated next UE available time parameter indicates a time the UE (200) is expected to return to being reachable.
[0267] 27. The method of any of Embodiments 23-26, wherein the support for power saving UE parameter indicates the NF (204, 206) acknowledges support of reception and handling of ‘Power saving UE’ and handling of ‘Estimated Next UE Available Time’.
[0268] 28. The method of any of Embodiments 23-27, further comprising: transmitting (3101), to the AMF (202), a communication transfer request having a subscribe for UE reachable parameter; receiving (3103), from the AMF (202), a communication message transfer response having a subscription ID for UE reachability assigned to the NF (204, 206); and receiving (3105), from the AMF (202), a UE reachable message having a remaining UE reachable time parameter.
[0269] 29. The method of Embodiment 28, wherein the subscribe for UE reachable parameter indicates that the NF (204, 206) needs to be informed when the UE (200) is reachable to avoid the AMF (202) providing a failure response message indicating that the UE (200) is not reachable
[0270] 30. The method of any of Embodiments 28-29, wherein the remaining UE reachable time parameter indicates a time period that the AMF (202) can hold the UE (200) in connected mode and the UE (200) is reachable.
[0271] 31. The method of any of Embodiments 23-30, further comprising: transmitting (3201), to an access and mobility management function, AMF, (202), a request with UE interaction required message, the request identifying a UE (200) with which UE interaction is required and having a Subscribe for UE reachable parameter; receiving (3203), from the AMF (204), a failure response message having an estimated next UE available time parameter and a subscription ID for UE reachability; and receiving (3205), from the AMF (202), a UE Reachable message having a remaining UE reachable time parameter.
[0272] 32. The method of any of Embodiments 23-31, wherein the NF (204, 206) comprises a policy control function, PCF, (206) and the create message comprise a policy control create message. 33. The method of any of Embodiments 23-31, wherein the NF (204, 206) comprises a session management function, SMF, (204) and the create message comprises a protocol data unit, PDU, session create message.
[0273] 34. A method in a network node having a network function, NF, (204, 206), the method comprising: transmitting (3201), to an access and mobility management function, AMF, (202), a request with UE interaction required message, the request identifying a UE (200) with which UE interaction is required and having a Subscribe for UE reachable parameter; receiving (3203), from the AMF (204), a failure response message having an estimated next UE available time parameter and a subscription ID for UE reachability; and receiving (3205), from the AMF (202), a UE Reachable message having a remaining UE reachable time parameter.
[0274] 35. The method of Embodiment 34, wherein the Subscribe for UE reachable parameter indicates that the NF (204, 206) needs to be informed when the UE (200) is reachable to avoid the AMF (202) providing a failure response message indicating that the UE (200) is not reachable.
[0275] 36. The method of any of Embodiments 34-35, wherein the request with UE interaction required message further comprises an extended buffering support indication.
[0276] 37. The method of and of Embodiments 34-36, wherein the failure response message further comprises a 504 gateway timeout and a UE_Not_Reachable indication
[0277] 38. The method of any of Embodiments 34-37, wherein responsive to the extended buffering support indication being included in the request with UE interaction required message, the failure response further comprises an estimated maximum waiting time.
[0278] 39. The method of any of Embodiments 34-38, wherein estimated next UE available time parameter indicates a time the UE (200) is expected to return to being reachable.
[0279] 40. The method of any of Embodiments 34-39, wherein the remaining UE reachable time parameter indicates a time period that the AMF (202) can hold the UE (200) in connected mode and the UE (200) is reachable.
[0280] 41. The method of any of Embodiments 34-40, further comprising transmitting another request with UE interaction required message to the AMF (202) after the UE reachable message has been received and a corresponding remaining reachable time parameter indicates that the UE is still reachable.
[0281] 42. The method of any of Embodiments 34-41, wherein the NF (204, 206) comprises a policy control function, PCF, (206). 43. The method of any of Embodiments 34-41, wherein the NF (204, 206) comprises a session management function, SMF, (204).
[0282] 44. A network node (3310A, 3310B, 3500, 3702, 3804) having an access and mobility function, AMF, (202), the network node comprising: processing circuitry (3502); and memory (3504) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the network node (3310A, 3310B, 3500, 3702, 3804) to perform operations according to any of Embodiments 1-22.
[0283] 45. A network node (3310A, 3310B, 3500, 3702, 3804) having an access and mobility function, AMF, (202) and adapted to perform according to any of Embodiments 1-22.
[0284] 46. A computer program comprising program code to be executed by processing circuitry (3502) of a network node (3310A, 3310B, 3500, 3702, 3804) having an access and mobility function, AMF, (204), whereby execution of the program code causes the network node (3310A, 3310B, 3500, 3702, 3804) to perform operations according to any of Embodiments 1-22.
[0285] 47. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (3502) of a network node (3310A, 3310B, 3500, 3702, 3804) having an access and mobility function, AMF, (202), whereby execution of the program code causes the network node (3310A, 3310B, 3500, 3702, 3804) to perform operations according to any of embodiments 1-22.
[0286] 48. A network node (3310A, 3310B, 3500, 3702, 3804) having a network function, NF, (204, 206), the network node comprising: processing circuitry (3502); and memory (3504) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the network node (3310A, 3310B, 3500, 3702, 3804) to perform operations according to any of Embodiments 23-43.
[0287] 49. A network node (3310A, 3310B, 3500, 3702, 3804) having a network function, NF, (204, 206) and adapted to perform according to any of Embodiments 23-43.
[0288] 50. A computer program comprising program code to be executed by processing circuitry (3502) of a network node (3310A, 3310B, 3500, 3702, 3804) having a network function, NF, (204, 206), whereby execution of the program code causes the network node (3310A, 3310B, 3500, 3702, 3804) to perform operations according to any of Embodiments 23-43.
[0289] 51. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (3502) of a network node (3310A, 3310B, 3500, 3702, 3804) having a network function, NF, (204, 206), whereby execution of the program code causes the network node (3310A, 3310B, 3500, 3702, 3804) to perform operations according to any of Embodiments 23-43.
Claims
CLAIMS1. A method performed in a network node (3310A, 3310B, 3500, 3702, 3804) having an access and mobility management function, AMF, (202), the method comprising: receiving (2501) a request message; transmitting (2503), to a network function, NF, (204, 206), a create request having a power saving user equipment, UE, parameter and an estimated next UE available time parameter; receiving (2505), from the NF (204, 206), a create response having a support for power saving UE parameter; and transmitting (2507), to the UE (200), an accept message.
2. The method of Claim 1, further comprising: receiving (2601) an update request message; transmitting (2603), to the NF (204, 206), an update request having a power saving UE parameter and an estimated next UE available time parameter; receiving (2605), from the NF (204, 206), an update response having a support for power saving UE parameter; and transmitting (2607), to the UE (200), an update response message.
3. The method of any of claims 1-2, wherein the power saving UE parameter indicates a consumer cannot obtain an immediate response from a UE (200) when the UE (200) is needed to be contacted.
4. The method of any of claims 1-3, wherein the estimated next UE available time parameter indicates a time the UE (200) is expected to return to being reachable.
5. The method of any of claims 1-4, wherein the support for power saving UE parameter indicates the NF (204, 206) acknowledges support of reception and handling of ‘Power saving UE’ and handling of ‘Estimated Next UE Available Time’.
6. The method of any of claims 1-5, further comprising: receiving (2701), from the NF (204, 206), a communication transfer request having a subscribe for UE reachable parameter;assigning (2703) a subscription ID for UE reachability to the NF (204, 206); transmitting (2705), to the NF (204, 206), a communication message transfer response having the subscription ID for UE reachability assigned to the NF (204, 206); and transmitting (2707), to the NF (204, 206), a UE reachable message having a remaining UE reachable time parameter.
7. The method of claim 6, wherein the subscribe for UE reachable parameter indicates that the NF (204, 206) needs to be informed when the UE (200) is reachable.
8. The method of any of claims 6-7, wherein the remaining UE reachable time parameter indicates a time period that the AMF (202) can hold the UE 200 in a connected mode and the UE (200) is reachable.
9. The method of any of claims 1-8, further comprising: receiving (2801), from a network function, NF, (204, 206), a request with UE interaction required message, the request with UE interaction required message identifying a UE (200) with which UE interaction is required and having a Subscribe for UE reachable parameter; responsive to the UE (200) not being reachable, transmitting (2803), to the NF (204, 206), a failure response message having an estimated next UE available time parameter and a subscription ID for UE reachability; and transmitting (2805), to the NF (204, 206), a UE Reachable message having a remaining UE reachable time parameter.
10. The method of any of claims 1-9, wherein the NF (204, 206) comprises a policy control function, PCF, (206) and the request message comprises a registration request for creating a policy control session at the PCF (206).
11. The method of any of claims 1-9, wherein the NF (204, 206) comprises a session management function, SMF, (204) and the request message comprises a protocol data unit, PDU, session establishment request.
12. The method of claim 11, wherein the update response message comprises a PDU session modification command message, the method further comprising: receiving, from the UE (200), a session modification complete message.
13. A method performed in a network node (3310A, 3310B, 3500, 3702, 3804) having an access and mobility management function, AMF, (202), the method comprising: receiving (2801), from a network function, NF, (204, 206), a request with UE interaction required message, the request with UE interaction required message identifying a UE (200) with which UE interaction is required and having a Subscribe for UE reachable parameter; responsive to the UE (200) not being reachable, transmitting (2803), to the NF (204, 206), a failure response message having an estimated next UE available time parameter and a subscription ID for UE reachability; and transmitting (2805), to the NF (204, 206), a UE Reachable message having a remaining UE reachable time parameter.
14. The method of claim 13, wherein the failure response message further comprises a (504) gateway timeout and a UE Not Reachable indication.
15. The method of any of claims 13-14, wherein the Subscribe for UE Reachable parameter indicates that the NF (204, 206) needs to be informed when the UE (200) is reachable in case the AMF (202) provides a failure response message indicating that the UE (200) is not reachable.
16. The method of any of claims 13-15, wherein the estimated next UE available time parameter indicates a time the UE (200) is expected to return to being reachable.
17. The method of any of claims 13-16, wherein the remaining UE reachable time parameter indicates a time period that the AMF (202) can hold the UE (200) in connected mode and the UE (200) is reachable.
18. The method of any of claims 10-17, wherein the NF (204, 206) comprises a policy control function, PCF, (206).
19. The method of claim 10, wherein the NF (204, 206) comprises a session management function, SMF, (204), the request with UE interaction required message further comprising an extended buffering support indication.
20. The method of claim 19, wherein responsive to the extended buffering support indication being included in the request with UE interaction required message, the failure response further comprises an estimated maximum waiting time.
21. The method of any of claims 10-20, wherein the NF (204, 206) comprises a policy control function, PCF, (206).
22. The method of any of claims 10-20, wherein the NF (204, 206) comprises a session management function, SMF, (204).
23. A method in a network node (3310A, 3310B, 3500, 3702, 3804) having a network function, NF, (204, 206), the method comprising: receiving (2901), from an access and mobility management function, AMF, (202), a create request having a power saving user equipment, UE, parameter and an estimated next UE available time parameter; and transmitting (2903), to the AMF (202), a create response having a support for power saving UE parameter.
24. The method of claim 23, further comprising: receiving (3001), from the AMF (202), an update request having the power saving user equipment, UE, parameter and the estimated next UE available time parameter; and transmitting (3003), to the AMF (202), an update response having a support for power saving UE parameter.
25. The method of any of claims 23-24, wherein the power saving UE parameter indicates a consumer cannot obtain an immediate response from a UE (200) when the UE (200) is needed to be contacted.
26. The method of any of claims 23-25, wherein the estimated next UE available time parameter indicates a time the UE (200) is expected to return to being reachable.
27. The method of any of claims 23-26, wherein the support for power saving UE parameter indicates the NF (204, 206) acknowledges support of reception and handling of ‘Power saving UE’ and handling of ‘Estimated Next UE Available Time’.
28. The method of any of claims 23-27, further comprising: transmitting (3101), to the AMF (202), a communication transfer request having a subscribe for UE reachable parameter; receiving (3103), from the AMF (202), a communication message transfer response having a subscription ID for UE reachability assigned to the NF (204, 206); and receiving (3105), from the AMF (202), a UE reachable message having a remaining UE reachable time parameter.
29. The method of claim 28, wherein the subscribe for UE reachable parameter indicates that the NF (204, 206) needs to be informed when the UE (200) is reachable to avoid the AMF (202) providing a failure response message indicating that the UE (200) is not reachable.
30. The method of any of claims 28-29, wherein the remaining UE reachable time parameter indicates a time period that the AMF (202) can hold the UE (200) in connected mode and the UE (200) is reachable.
31. The method of any of claims 23-30, further comprising: transmitting (3201), to an access and mobility management function, AMF, (202), a request with UE interaction required message, the request identifying a UE (200) with which UE interaction is required and having a Subscribe for UE reachable parameter; receiving (3203), from the AMF (204), a failure response message having an estimated next UE available time parameter and a subscription ID for UE reachability; and receiving (3205), from the AMF (202), a UE Reachable message having a remaining UE reachable time parameter.
32. The method of any of claims 23-31, wherein the NF (204, 206) comprises a policy control function, PCF, (206) and the create message comprise a policy control create message.
33. The method of any of claims 23-31, wherein the NF (204, 206) comprises a session management function, SMF, (204) and the create message comprises a protocol data unit, PDU, session create message.
34. A method in a network node having a network function, NF, (204, 206), the method comprising:transmitting (3201), to an access and mobility management function, AMF, (202), a request with UE interaction required message, the request identifying a UE (200) with which UE interaction is required and having a Subscribe for UE reachable parameter; receiving (3203), from the AMF (204), a failure response message having an estimated next UE available time parameter and a subscription ID for UE reachability; and receiving (3205), from the AMF (202), a UE Reachable message having a remaining UE reachable time parameter.
35. The method of claim 34, wherein the Subscribe for UE reachable parameter indicates that the NF (204, 206) needs to be informed when the UE (200) is reachable to avoid the AMF (202) providing a failure response message indicating that the UE (200) is not reachable.
36. The method of any of claims 34-35, wherein the request with UE interaction required message further comprises an extended buffering support indication.
37. The method of and of claims 34-36, wherein the failure response message further comprises a 504 gateway timeout and a UE_Not_Reachable indication.
38. The method of any of claims 34-37, wherein responsive to the extended buffering support indication being included in the request with UE interaction required message, the failure response further comprises an estimated maximum waiting time.
39. The method of any of claims 34-38, wherein estimated next UE available time parameter indicates a time the UE (200) is expected to return to being reachable.
40. The method of any of claims 34-39, wherein the remaining UE reachable time parameter indicates a time period that the AMF (202) can hold the UE (200) in connected mode and the UE (200) is reachable.
41. The method of any of claims 34-40, further comprising transmitting another request with UE interaction required message to the AMF (202) after the UE reachable message has been received and a corresponding remaining reachable time parameter indicates that the UE is still reachable.
42. The method of any of claims 34-41, wherein the NF (204, 206) comprises a policy control function, PCF, (206).
43. The method of any of claims 34-41, wherein the NF (204, 206) comprises a session management function, SMF, (204).
44. A network node (3310A, 3310B, 3500, 3702, 3804) having an access and mobility function, AMF, (202), the network node comprising: processing circuitry (3502); and memory (3504) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the network node (3310A, 3310B, 3500, 3702, 3804) to perform operations according to any of claims 1-22.
45. A network node (3310A, 3310B, 3500, 3702, 3804) having an access and mobility function, AMF, (202) and adapted to perform according to any of claims 1-22.
46. A computer program comprising program code to be executed by processing circuitry (3502) of a network node (3310A, 3310B, 3500, 3702, 3804) having an access and mobility function, AMF, (204), whereby execution of the program code causes the network node (3310A, 3310B, 3500, 3702, 3804) to perform operations according to any of claims 1-22.
47. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (3502) of a network node (3310A, 3310B, 3500, 3702, 3804) having an access and mobility function, AMF, (202), whereby execution of the program code causes the network node (3310A, 3310B, 3500, 3702, 3804) to perform operations according to any of claims 1-22.
48. A network node (3310A, 3310B, 3500, 3702, 3804) having a network function, NF, (204, 206), the network node comprising: processing circuitry (3502); and memory (3504) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the network node (3310A, 3310B, 3500, 3702, 3804) to perform operations according to any of claims 23-43.
49. A network node (3310A, 3310B, 3500, 3702, 3804) having a network function, NF, (204, 206) and adapted to perform according to any of claims 23-43.
50. A computer program comprising program code to be executed by processing circuitry (3502) of a network node (3310A, 3310B, 3500, 3702, 3804) having a network function, NF,(204, 206), whereby execution of the program code causes the network node (3310A, 3310B, 3500, 3702, 3804) to perform operations according to any of claims 23-43.
51. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (3502) of a network node (3310A, 3310B, 3500, 3702, 3804) having a network function, NF, (204, 206), whereby execution of the program code causes the network node (3310A, 3310B, 3500, 3702, 3804) to perform operations according to any of claims 23-43.
Citation Information
Patent Citations
Method and apparatus for data transmission
WO2019232780A1
