[go: up one dir, main page]

WO2023058009A1 - Indication d'itinérance en cas de catastrophe pour session et politique - Google Patents

Indication d'itinérance en cas de catastrophe pour session et politique Download PDF

Info

Publication number
WO2023058009A1
WO2023058009A1 PCT/IB2022/059706 IB2022059706W WO2023058009A1 WO 2023058009 A1 WO2023058009 A1 WO 2023058009A1 IB 2022059706 W IB2022059706 W IB 2022059706W WO 2023058009 A1 WO2023058009 A1 WO 2023058009A1
Authority
WO
WIPO (PCT)
Prior art keywords
disaster
smf
roaming service
amf
roaming
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/IB2022/059706
Other languages
English (en)
Inventor
Qian Chen
Stefan Rommer
Shabnam Sultana
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2023058009A1 publication Critical patent/WO2023058009A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/06—Registration at serving network Location Register, VLR or user mobility server
    • H04W8/065—Registration at serving network Location Register, VLR or user mobility server involving selection of the user mobility server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/12—Mobility data transfer between location registers or mobility servers

Definitions

  • the present disclosure relates generally to disaster roaming.
  • AMF provides Disaster Roaming service indication to SMF in corresponding service operations during PDU Session establishment procedure.
  • AMF provides Disaster Roaming service indication to PCF during Registration procedure.
  • PCF and SMF receive Disaster Roaming service indication and apply corresponding policies applicable to UE for Disaster Roaming service.
  • the Disaster Roaming service indication information is stored in Charging related data and local logs in individual NFs.
  • Certain embodiments may provide one or more of the following technical advantage(s). Operator can apply differentiated policy control for mobility and session for UE disaster roaming service.
  • a method performed by an Access and Mobility Management Function (AMF) for enabling Disaster Roaming includes: receiving, from a User Equipment (UE), a Disaster Roaming service indication during a registration; and providing the Disaster Roaming service indication to a Session Management Function (SMF) in corresponding service operations during a Protocol Data Unit (PDU) Session establishment procedure.
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • PDU Protocol Data Unit
  • the method includes storing the Disaster Roaming service indication in a PDU session context.
  • the Disaster Roaming service indication information is stored in Charging related data.
  • the Disaster Roaming service indication provided to the SMF is the Disaster Roaming service indication stored in the UE context sent during the UE registration procedure.
  • differentiated policy control is applied for mobility and/or session for UE disaster roaming service.
  • one or more different charging policies are applied based on the Disaster Roaming service indication.
  • the method also includes providing a Disaster Roaming service indication to a Policy Control Function (PCF) during Registration procedure.
  • PCF Policy Control Function
  • the method also includes providing the Disaster Roaming service indication to an Authentication Server Function (AUSF) and/or a Unified Data Management (UDM).
  • AUSF Authentication Server Function
  • UDM Unified Data Management
  • a method performed by a SMF for enabling Disaster Roaming includes: receiving a Disaster Roaming service indication from an AMF in corresponding service operations during a PDU Session establishment procedure; and storing the Disaster Roaming service indication in a context.
  • the Disaster Roaming service indication is stored in a Session Management (SM) context.
  • SM Session Management
  • one or more different charging policies are applied based on the Disaster Roaming service indication.
  • Figure 1 illustrates Figure 4.3.2.2.1-1: UE-requested PDU Session Establishment for non-roaming and roaming with local breakout;
  • Figure 2 illustrates Figure 4.3.2.2.2-1: UE-requested PDU Session Establishment for home-routed roaming scenarios
  • Figure 3 illustrates Figure 4.2.2.2.2-1: Registration procedure
  • Figure 4 shows an example of a communication system in accordance with some embodiments
  • Figure 5 illustrates a method performed by an AMF for enabling Disaster Roaming
  • Figure 6 illustrates a method performed by a network node, such as a SMF, and/or a PCF for enabling Disaster Roaming;
  • a network node such as a SMF, and/or a PCF for enabling Disaster Roaming
  • Figure 7 illustrates a method performed by various network nodes for enabling Disaster Roaming
  • Figure 8 shows a UE in accordance with some embodiments
  • Figure 9 shows a network node in accordance with some embodiments.
  • Figure 10 is a block diagram of a host, which may be an embodiment of the host of Figure 4, in accordance with various aspects described herein;
  • Figure 11 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.
  • Figure 12 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.
  • Clause 4.3.2.2.1 specifies PDU Session establishment in the non-roaming and roaming with local breakout cases. The procedure is used to:
  • the AMF determines if a PDU Session is to be established in LBO or Home Routing.
  • LBO the procedure is as in the case of non-roaming with the difference that the AMF, the SMF, the UPF and the PCF are located in the visited network.
  • PDU Sessions for Emergency services are never established in Home Routed mode.
  • the NEF is not used as the anchor of this PDU Session.
  • NOTE 1 UE provides both the S-NSSAIs of the Home PLMN and Visited PLMN to the network as described in clause 5.15.5.3 of TS 23.501 [2].
  • FIG. 1 illustrates Figure 4.3.2.2.1-1: UE-requested PDU Session Establishment for non-roaming and roaming with local breakout.
  • Nsmf_PDUSession_CreateSMContext Request (SUPI, selected DNN, UE requested DNN, S-NSSAI(s), PDU Session ID, AMF ID, Request Type, [PCF ID, Same PCF Selection Indication], Priority Access, [Small Data Rate Control Status], N1 SM container (PDU Session Establishment Request), User location information, Access Type, RAT Type, PEI, GPSI, UE presence in LADN service area, Subscription For PDU Session Status Notification, DNN Selection Mode, Trace Requirements, Control Plane CIoT 5GS Optimization indication, Control Plane Only indicator, Satellite backhaul category, [PVS FQDN or PVS IP address], [Disaster Roaming service indication]) or Nsmf_PD
  • the AMF invokes the Nsmf_PDUSession_CreateSMContext Request, but if the AMF already has an association with an SMF for the PDU Session ID provided by the UE (e.g., when Request Type indicates "existing PDU Session"), the AMF invokes the Nsmf_PDUSession_UpdateSMContext Request.
  • the AMF sends the S-NSSAI of the Serving PLMN from the Allowed NSSAI to the SMF.
  • the AMF also sends the corresponding S-NSSAI of the HPLMN from the Mapping Of Allowed NSSAI to the SMF.
  • the AMF ID is the UE's GUAMI which uniquely identifies the AMF serving the UE.
  • the AMF forwards the PDU Session ID together with the N1 SM container containing the PDU Session Establishment Request received from the UE.
  • the GPSI shall be included if available at AMF.
  • the AMF determines Access Type and RAT Type, see clause 4.2.2.2.1.
  • the AMF provides the PEI instead of the SUPI when the UE in limited service state has registered for Emergency services (i.e., Emergency Registered) without providing a SUPI.
  • the PEI is defined in clause 5.9.3 of TS 23.501 [2]. If the UE in the limited service state has registered for Emergency services (i.e., Emergency Registered) with a SUPI but has not been authenticated, the AMF indicates that the SUPI has not been authenticated. The SMF determines that the UE has not been authenticated when it does not receive a SUPI for the UE or when the AMF indicates that the SUPI has not been authenticated.
  • the AMF determines that the selected DNN corresponds to an LADN then the AMF provides the "UE presence in LADN service area" that indicates if the UE is IN or OUT of the LADN service area.
  • the AMF also includes Old PDU Session ID in the Nsmf_PDUSession_CreateSMContext Request.
  • DNN Selection Mode is determined by the AMF. It indicates whether an explicitly subscribed DNN has been provided by the UE in its PDU Session Establishment Request.
  • the SMF may use DNN Selection Mode when deciding whether to accept or reject the UE request.
  • the AMF When the Establishment cause received as part of AN parameters during the Registration procedure or Service Request procedure is associated with priority services (e.g., MPS, MCS), the AMF includes a Message Priority header to indicate priority information.
  • the SMF uses the Message Priority header to determine if the UE request is subject to exemption from NAS level congestion control.
  • Other NFs relay the priority information by including the Message Priority header in service-based interfaces, as specified in TS 29.500 [17].
  • the SMF in the VPLMN
  • the SMF responds to the AMF that it is not the right SMF to handle the N1 SM message by invoking Nsmf_PDUSession_CreateSMContext Response service operation.
  • the SMF includes a proper Nil cause code triggering the AMF to proceed with home routed case. The procedure starts again at step 2 of clause 4.3.2.2.2.
  • the AMF checks if the PCF Selection Assistance info from the UDM indicates that the same PCF is required for the requested DNN and S-NSSAI, and if required, the AMF includes in Nsmf_PDUSession_CreateSMContext Request both the Same PCF Selection Indication and the PCF ID selected by the AMF, this PCF ID identifies the H-PCF, [0056] If PCF Selection Assistance info is not received from the UDM, the AMF may include a PCF ID in the Nsmf_PDUSession_CreateSMContext Request based on operator policies. This PCF ID identifies the H-PCF in the non-roaming case and the V-PCF in the local breakout roaming case.
  • the AMF includes Trace Requirements if Trace Requirements have been received in subscription data.
  • the AMF decides to use the Control Plane CIoT 5GS Optimization or User Plane CIoT 5GS Optimization as specified in step 2 or to only use Control Plane CIoT 5GS Optimization for the PDU session as described in clause 5.31.4 of TS 23.501 [2], the AMF sends the Control Plane CIoT 5GS Optimization indication or Control Plane Only indicator to the SMF.
  • the AMF may either reject the PDU Session Establishment Request or continue with the PDU Session establishment and include the Control Plane CIoT 5GS Optimization indication or Control Plane Only indicator to the SMF.
  • the AMF includes the latest Small Data Rate Control Status if it has stored it for the PDU Session.
  • the SMF stores the RAT type in SM Context.
  • the AMF shall include the extended NAS-SM timer indication. Based on the extended NAS-SM timer indication, the SMF shall use the extended NAS-SM timer setting for the UE as specified in TS 24.501 [25].
  • the AMF informs the SMF of the NWDAF ID(s) used for UE related Analytics and corresponding Analytics ID(s).
  • the AMF includes Satellite backhaul category indication.
  • the AMF provides the Disaster Roaming service indication if UE context stored in AMF indicating UE is registered for Disaster Roaming service.
  • Session Management Subscription data for corresponding SUPI, DNN and S-NSSAI of the HPLMN is not available, then SMF retrieves the Session Management Subscription data using Nudm_SDM_Get (SUPI, Session Management Subscription data, selected DNN, S-NSSAI of the HPLMN, Serving PLMN ID, [NID]) and subscribes to be notified when this subscription data is modified using Nudm_SDM_Subscribe (SUPI, Session Management Subscription data, selected DNN, S- NSSAI of the HPLMN, Serving PLMN ID, [NID]).
  • Nudm_SDM_Get SUPI, Session Management Subscription data, selected DNN, S- NSSAI of the HPLMN, Serving PLMN ID, [NID]
  • UDM may get this information from UDR by Nudr_DM_Query (SUPI, Subscription Data, Session Management Subscription data, selected DNN, S-NSSAI of the HPLMN, Serving PLMN ID, [NID]) and may subscribe to notifications from UDR for the same data by Nudr_DM_subscribe.
  • Nudr_DM_Query SUPI, Subscription Data, Session Management Subscription data, selected DNN, S-NSSAI of the HPLMN, Serving PLMN ID, [NID]
  • the SMF may use DNN Selection Mode when deciding whether to retrieve the Session Management Subscription data, e.g. if the (selected DNN, S-NSSAI of the HPLMN) is not explicitly subscribed, the SMF may use local configuration instead of Session Management Subscription data.
  • the SMF determines that the request is due to switching between 3GPP access and non-3GPP access or due to handover from EPS.
  • the SMF identifies the existing PDU Session based on the PDU Session ID. In such a case, the SMF does not create a new SM context but instead updates the existing SM context and provides the representation of the updated SM context to the AMF in the response.
  • the SMF identifies the existing PDU Session to be released based on the Old PDU Session ID.
  • Subscription data includes the Allowed PDU Session Type(s), Allowed SSC mode(s), default 5QI and ARP, subscribed Session-AMBR, SMF-Associated external parameters.
  • IP Index or Static IP address/prefix may be included in the subscription data if the UE has subscribed to it.
  • the SMF checks the validity of the UE request: it checks [0073] - Whether the UE request is compliant with the user subscription and with local policies;
  • the SMF determines whether the PDU Session requires redundancy and the SMF determines the RSN as described in clause 5.33.2.1 of TS 23.501 [2]. If the SMF determines that redundant handling is not allowed or not possible for the given PDU Session, the SMF shall either reject the establishment of the PDU Session or accept the establishment of a PDU session without redundancy handling based on local policy.
  • the SMF decides to not accept to establish the PDU Session.
  • the SMF can, instead of the Nudm_SDM_Get service operation, use the Nudm_SDM_Subscribe service operation with an Immediate Report Indication that triggers the UDM to immediately return the subscribed data if the corresponding feature is supported by both the SMF and the UDM.
  • Nsmf_PDUSession_CreateSMContext Response (Cause, SM Context ID or N1 SM container (PDU Session Reject (Cause))) or an Nsmf_PDUSession_UpdateSMContext Response depending on the request received in step 3.
  • the SMF If the SMF received Nsmf_PDUSession_CreateSMContext Request in step 3 and the SMF is able to process the PDU Session establishment request, the SMF creates an SM context and responds to the AMF by providing an SM Context ID.
  • the SMF may, based on local configuration, decide whether to accept or reject the PDU Session request based on the UE Integrity Protection Maximum Data Rate.
  • the SMF can, e.g., be configured to reject a PDU Session if the UE Integrity Protection Maximum Data Rate has a very low value, if the services provided by the DN would require higher bitrates.
  • the SMF decides to not accept to establish a PDU Session, the SMF rejects the UE request via NAS SM signalling including a relevant SM rejection cause by responding to the AMF with Nsmf_PDUSession_CreateSMContext Response.
  • the SMF also indicates to the AMF that the PDU Session ID is to be considered as released, the SMF proceeds to step 20 and the PDU Session Establishment procedure is stopped.
  • Optional Secondary authentication/authorization is optionally configured to reject a PDU Session if the UE Integrity Protection Maximum Data Rate has a very low value, if the services provided by the DN would require higher bitrates.
  • step 3 If the Request Type in step 3 indicates "Existing PDU Session", the SMF does not perform secondary authentication/authorization.
  • the SMF shall not perform secondary a uthentication ⁇ a uthorization .
  • the SMF needs to perform secondary authentication/authorization during the establishment of the PDU Session by a DN-AAA server as described in clause 5.6.6 of TS 23.501 [2], the SMF triggers the PDU Session establishment authentication/authorization as described in clause 4.3.2.3.
  • the SMF may apply local policy.
  • the SMF may perform an SM Policy Association Establishment procedure as defined in clause 4.16.4 to establish an SM Policy Association with the PCF and get the default PCC Rules for the PDU Session.
  • the GPSI and PVS FQDN or PVS IP address shall be included if available at SMF.
  • the SMF may provide information on the Policy Control Request Trigger condition(s) that have been met by an SMF initiated SM Policy Association Modification procedure as defined in clause 4.16.5.1.
  • the PCF may provide policy information defined in clause 5.2.5.4 (and in TS 23.503 [20]) to SMF.
  • the PCF based on the Emergency DNN, sets the ARP of the PCC rules to a value that is reserved for Emergency services as described in TS 23.503 [20].
  • step 7 The purpose of step 7 is to receive PCC rules before selecting UPF. If PCC rules are not needed as input for UPF selection, step 7 can be performed after step 8. [0092]
  • the SMF may provide the Disaster Roaming service indication to PCF for policy control if the indication is received from AMF in step 3 above.
  • the PCF may provide corresponding SM policy applicable to UEs for Disaster Roaming service.
  • FIG. 2 illustrates Figure 4.3.2.2.2-1: UE-requested PDU Session Establishment for home- routed roaming scenarios.
  • V-SMF to H-SMF Nsmf_PDUSession_Create Request (SUPI, GPSI (if available), V-SMF SM Context ID, DNN, S-NSSAI with the value defined by the HPLMN, PDU Session ID, V-SMF ID, V-CN-Tunnel-Info, PDU Session Type, PCO, Number Of Packet Filters, User location information, Access Type, RAT Type, PCF ID, [Small Data Rate Control Status], SM PDU DN Request Container, DNN Selection Mode, Control Plane CIoT 5GS Optimization Indication, [Always-on PDU Session Requested], AMF ID, Serving Network, the QoS constraints from the VPLMN, Satellite backhaul category, [Disaster Roaming service indication]) or Nsmf_PDUSession_Update Request (V- CN-Tunnel-Info, PCO, User location information, Access Type, RAT Type
  • Protocol Configuration Options may contain information that H-SMF may needs to properly establish the PDU Session (e.g., SSC mode or SM PDU DN Request Container to be used to authenticate the UE by the DN- AAA as defined in clause 4.3.2.3).
  • the H-SMF may use DNN Selection Mode when deciding whether to accept or reject the UE request. If the V-SMF does not receive any response from the H-SMF due to communication failure on the N16 interface, depending on operator policy the V-SMF may create the PDU Session to one of the alternative H- SMF(s) if additional H-SMF information is provided in step 3a, as specified in detail in TS 29.502 [36].
  • the Small Data Rate Control Status is included if received from the AMF.
  • the Control Plane CIoT 5GS Optimization Indication is set by the V-SMF, if the PDU Session is intended for Control Plane CIoT 5GS Optimization.
  • the QoS constraints from the VPLMN contains a 5QI and corresponding ARP value that the VPLMN can accept for the QoS Flow associated with the default QoS rule and the highest Session- AMBR that the VPLMN can accept.
  • the Disaster Roaming service indication is included if the indication is received from AMF in step 3a above.
  • V-SMF SM Context ID contains the addressing information it has allocated for service operations related with this PDU Session.
  • the H-SMF stores an association of the PDU Session and V-SMF Context ID for this PDU Session for this UE.
  • the H-SMF needs to use V-SMF services for this PDU Session (invoking Nsmf_PDUSession_Update Request) before step 13, at the first invocation of Nsmf_PDUSession_Update Request the H-SMF provides the V-SMF with the H-SMF SM Context ID it has allocated for service operations related with this PDU Session.
  • the H-SMF stores the RAT type in SM Context.
  • the V-SMF invokes Nsmf_PDUSession_Update Request. Otherwise the V-SMF invokes Nsmf_PDUSession_Create Request.
  • the NF Service Consumer can request the creation of a SM Policy Association and provide relevant parameters about the PDU Session to the PCF.
  • Inputs Optional: Information provided by the SMF as defined in clause 6.2.1.2 of TS 23.503 [20], such as Access Type, the IPv4 address and/or IPv6 prefix, PEI, GPSI, User Location Information, UE Time Zone, Serving Network (PLMN ID, or PLMN ID and NID, see clause 5.34 of TS 23.501 [2]), Charging Characteristics information, Session AMBR, subscribed default QoS information, Trace Requirements and Internal Group Identifier (see clause 5.9.7 of TS 23.501 [2]), DN Authorization Profile Index, Framed Route information.
  • MA PDU Request indication indicates whether MA PDU Network- Upgrade Allowed indication, ATSSS capabilities of the MA PDU Session, QoS constraints from the VPLMN (see clause 4.3.2.2.2), Satellite Backhaul Category information, list of NWDAF instance Ids used by AMF, SMF, and UPF and corresponding Analytics ID(s), Disaster Roaming service indication.
  • SMF receives the DN authorized Session AMBR from the DN-AAA at PDU session establishment, it includes the DN authorized Session AMBR within the Session-AMBR, instead of the subscribed Session AMBR received from the UDM, in the request.
  • W-5GAN specific PDU session information provided by the SMF is specified in TS 23.316 [53].
  • PLMN ID Serving Network
  • Input Optional: S-NSSAI, PCO, Requested PDU Session Type, 5GSM Core Network Capability, Requested SSC mode, PDU Session ID, Number Of Packet Filters, UE location information, subscription get notified of PDU Session status change, PEI, GPSI, AN type, PCF ID, PCF Group ID, DNN Selection Mode, UE's Routing Indicator optionally with Home Network Public Key identifier or UDM Group ID for the UE, Always- on PDU Session Requested, Control Plane CIoT 5GS Optimization Indication, information provided by V-SMF related to charging in home routed scenario (see TS 32.255 [45]), AMF ID, EPS Bearer Status, extended NAS-SM timer indication, DNAI list supported by I- SMF (from I-SMF to SMF), HO Preparation Indication.
  • S-NSSAI S-NSSAI
  • PCO Requested PDU Session Type
  • MA PDU request indication MA PDU Network-Upgrade Allowed indication, Indication on whether the UE is registered in both accesses; QoS constraints from the VPLMN (see clause 4.3.2.2.2), Satellite backhaul category, Notification of the SM Policy Association Establishment and Termination, PCF binding information, Disaster Roaming service indication.
  • Output Optional: PDU Session ID, S-NSSAI, Cause, PCO, UE IP address, IPv6 Prefix allocated to the PDU Session, information needed by V-SMF in the case of EPS interworking such as the PDN Connection Type, EPS bearer context(s), linked EBI, Reflective QoS Timer, Always-on PDU Session Granted, information provided by H-SMF related to charging in home routed scenario (see TS 32.255 [45]), DNAI(s) of interest for this PDU Session (from SMF to I-SMF), indication of multi-homing support (from SMF to I-SMF). MA PDU session Accepted indication, Indication on whether Small Data Rate Control applies or not.
  • V-SMF SM Context ID in the Input provides addressing information allocated by the V-SMF (to be used for service operations towards the V-SMF for this PDU Session).
  • the I-SMF SM Context ID in the Input provides addressing information allocated by the I-SMF (to be used for service operations towards the I-SMF for this PDU Session).
  • Service operation name Nsmf_PDUSession_CreateSMContext.
  • Input, Required SUPI or PEI, DNN, AMF ID (AMF Instance ID), RAT Type, Serving Network (PLMN ID, or PLMN ID and NID, see clause 5.18 of TS 23.501 [2]).
  • Input Optional: PEI, S-NSSAI(s), PDU Session Id, N1 SM container, UE location information, UE Time Zone, AN type, H-SMF identifier/address, list of alternative H-SMF(s) if available, old PDU Session ID (if the AMF also received an old PDU Session ID from the UE as specified in clause 4.3.5.2), Subscription For PDU Session Status Notification, Subscription for DDN Failure Notification, NEF Correlation ID, indication that the SUPI has not been authenticated, PCF ID, PCF Group ID, Same PCF Selection Indication, DNN Selection Mode, UE PDN Connection Context, GPSI, UE presence in LADN service area, GUAMI, backup AMF(s) (if NF Type is AMF), Trace Requirements, Control Plane CIoT 5GS Optimization indication, Small Data Rate Control Status, APN Rate Control Status.
  • UE's Routing Indicator optionally with Home Network Public Key identifier or UDM Group ID for the UE, EPS Bearer Status.
  • Target ID for EPS to 5GS handover
  • "Invoke NEF" flag flag
  • target DNAI additional following for SM context transfer: SMF transfer indication, Old SMF ID, SM context ID in old SMF (see clause 4.26.5.3), HO Preparation Indication, indication of no NG-RAN change.
  • MA PDU request indication MA PDU Network-Upgrade Allowed indication, Indication on whether the UE is registered in both accesses, Satellite backhaul category, Disaster Roaming service indication.
  • Output, Required Result Indication, and if successful SM Context ID.
  • the AMF When the PDU Session is for Emergency services for a UE without USIM, the AMF provides the PEI and not the SUPI as identifier of the UE. When the PDU Session is for Emergency services of an unauthenticated UE with an USIM, the AMF shall provide both the SUPI and the PEI and shall provide an indication that the SUPI has not been authenticated.
  • Service operation name Nsmf_PDUSession_ContextRequest.
  • This service operation is used by the NF Consumer to request for SM Context (e.g., during EPS IWK, HO, SM Context transfer indication), or during mobility procedure with I-SMF changes or may be triggered by OAM.
  • Session ID (include PDU Session ID when available), SMF transfer indication, indication of no NG-RAN change.
  • the SM context type indicates the type of SM context to be requested, e.g.
  • the SM Context included in the SM Context container is the PDN Connection Context. If the SM context type is all, the SM Context included in the SM Context container includes both the PDN Connection Context and the 5G SM Context.
  • Table 5.2.8.2.10-1 (SM Context of a PDU Session transferred between I- SMF(s) or between V-SMF(s)) illustrates the SM Context that may be transferred between I-SMF(s) or between V-SMF(s) in home-routed roaming case: [0150] If the new AMF selects a new (V-)PCF in step 15, the new AMF performs AM Policy Association Establishment with the selected (V-)PCF as defined in clause 4.16.1.2.
  • the new AMF performs AM Policy Association Modification with the (V-)PCF as defined in clause 4.16.2.1.2.
  • the AMF If the AMF notifies the Mobility Restrictions (e.g., UE location) to the PCF for adjustment, or if the PCF updates the Mobility Restrictions itself due to some conditions (e.g., application in use, time and date), the PCF shall provide the updated Mobility Restrictions to the AMF. If the subscription information includes Tracing Requirements, the AMF provides the PCF with Tracing Requirements.
  • Mobility Restrictions e.g., UE location
  • the PCF shall provide the updated Mobility Restrictions to the AMF. If the subscription information includes Tracing Requirements, the AMF provides the PCF with Tracing Requirements.
  • the AMF If the AMF supports DNN replacement, the AMF provides the PCF with the Allowed NSSAI and, if available, the Mapping Of Allowed NSSAI.
  • the PCF If the PCF supports DNN replacement, the PCF provides the AMF with triggers for DNN replacement.
  • the AMF provides the Disaster Roaming service indication to PCF if UE registers for Disaster Roaming service.
  • the V-PCF may provide corresponding AM policy based on local configuration applicable to UEs for Disaster Roaming service.
  • NF Service Consumer can request the creation of an AM Policy Association and by providing relevant parameters about the UE context to the PCF.
  • Inputs, Required SUPI.
  • Inputs Optional: Information provided by the AMF as defined in 6.2.1.2 of TS 23.503 [20], such as Access Type, Permanent Equipment Identifier, GPSI, User Location Information, UE Time Zone, Serving Network (PLMN ID, or PLMN ID and NID, see clause 5.34 of TS 23.501 [2]), RAT type, List of subscribed Service Area Restrictions, subscribed RFSP Index, the Allowed NSSAI, Target NSSAI, GUAMI, backup AMF(s) (if NF Type is AMF). Backup AMF(s) are sent only once by the AMF to the PCF in its first interaction with the PCF, list of NWDAF instance Ids and corresponding Analytics ID(s), Disaster Roaming indication.
  • Outputs, Required AM Policy Association ID.
  • Outputs, Optional The requested Access and mobility related policy information as defined in clause 6.5 of TS 23.503 [20], and Policy Control Request Trigger of AM Policy Association.
  • step 16 the AMF requests the PCF to apply operator policies for the UE.
  • step 2 the AMF requests the PCF to apply operator policies for the UE; in step 3, the PCF acknowledges AMF with requested policy.
  • a UE For a UE to receive Disaster Roaming service from a PLMN providing Disaster Roaming service, the UE sends a NAS Registration Request message with Registration Type value "Disaster Roaming":
  • the PLMN providing Disaster Roaming service is configured to support communication with the network entities in the HPLMN of the UE, i.e. configurations related to roaming interfaces for communication between serving PLMN and HPLMN shall be deployed in the affected entities.
  • the Disaster Roaming service is limited to the impacted geographic area with Disaster Condition.
  • the NG-RAN nodes and AMF in the PLMN providing Disaster Roaming service are configured with the area information, i.e. a list of TAIs which can be formulated by the PLMN providing the Disaster Roaming service based on the geographic area with Disaster Condition in the other PLMN(s).
  • the AMF in the PLMN providing Disaster Roaming service provides the mobility restriction list to the NG-RAN as specified in clause 5.3.4.1.1 considering the area with Disaster Condition, and also indicating that EPC is not an allowed core network.
  • the AMF shall also provide the Disaster Roaming service indication to other NFs, e.g., SMF, PCF.
  • the NFs interacting with CHF shall also provide the Disaster Roaming service information, if it is available.
  • the policy differentiation can be, e.g., different RFSP value, SMF selection information (e.g., DNN replacement, S-NSSAI), UE-AMBR, UE slice-MBRs.
  • SMF selection information e.g., DNN replacement, S-NSSAI
  • UE-AMBR e.g., UE slice-MBRs.
  • PCF When PCF receives Disaster Roaming service indication from SMF, different policies may be applied for PDU sessions for a UE in Disaster Roaming service.
  • the policy differentiation can be, e.g., different QoS, charging policy.
  • SMF When SMF receives Disaster Roaming service indication from AMF, SMF can apply different policies if PCF is not deployed.
  • CHF When CHF receives Disaster Roaming service information as part of the charging data information, it shall be stored in the CDR. Different charging policy may be applied based on operator decision.
  • Figure 4 shows an example of a communication system 400 in accordance with some embodiments.
  • the communication system 400 includes a telecommunication network 402 that includes an access network 404, such as a Radio Access Network (RAN), and a core network 406, which includes one or more core network nodes 408.
  • the access network 404 includes one or more access network nodes, such as network nodes 410A and 410B (one or more of which may be generally referred to as network nodes 410), or any other similar Third Generation Partnership Project (3GPP) access node or non-3GPP Access Point (AP).
  • 3GPP Third Generation Partnership Project
  • the network nodes 410 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 412A, 412B, 412C, and 412D (one or more of which may be generally referred to as UEs 412) to the core network 406 over one or more wireless connections.
  • UE User Equipment
  • 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.
  • the communication system 400 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 400 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 412 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 410 and other communication devices.
  • the network nodes 410 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 412 and/or with other network nodes or equipment in the telecommunication network 402 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 402.
  • the core network 406 connects the network nodes 410 to one or more hosts, such as host 416. 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 406 includes one more core network nodes (e.g., core network node 408) 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 408.
  • 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).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-Concealing Function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • UPF User Plane Function
  • the host 416 may host a variety of applications to provide one or more service. Examples of such applications include live and prerecorded 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.
  • applications include live and prerecorded 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.
  • the communication system 400 of Figure 4 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system 400 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile
  • the telecommunication network 402 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 402. For example, the telecommunication network 402 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 Internet of Things (loT) services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine Type Communication
  • LoT massive Internet of Things
  • the UEs 412 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 404.
  • a UE may be configured for operating in single- or multiRadio Access Technology (RAT) or multi-standard mode.
  • RAT Radio Access Technology
  • a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. be configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).
  • MR-DC Multi-Radio Dual Connectivity
  • E-UTRAN Evolved UMTS Terrestrial RAN
  • EN-DC Dual Connectivity
  • a hub 414 communicates with the access network 404 to facilitate indirect communication between one or more UEs (e.g., UE 412C and/or 412D) and network nodes (e.g., network node 410B).
  • the hub 414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 414 may be a broadband router enabling access to the core network 406 for the UEs.
  • the hub 414 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 414 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.
  • the hub 414 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 414 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 414 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the hub 414 may have a constant/persistent or intermittent connection to the network node 410B.
  • the hub 414 may also allow for a different communication scheme and/or schedule between the hub 414 and UEs (e.g., UE 412C and/or 412D), and between the hub 414 and the core network 406.
  • the hub 414 is connected to the core network 406 and/or one or more UEs via a wired connection.
  • the hub 414 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 404 and/or to another UE over a direct connection.
  • M2M Machine-to-Machine
  • UEs may establish a wireless connection with the network nodes 410 while still connected via the hub 414 via a wired or wireless connection.
  • the hub 414 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 410B.
  • the hub 414 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 410B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • a method performed by an AMF for enabling Disaster Roaming includes: receiving, from a UE, a Disaster Roaming service indication during a registration; and providing the Disaster Roaming service indication to a SMF in corresponding service operations during a PDU Session establishment procedure.
  • an operator can apply differentiated policy control at the mobility and session level for a UE registered for disaster roaming service.
  • Figure 5 illustrates a method performed by an AMF for enabling Disaster Roaming.
  • the method includes one or more of: providing (step 500) a Disaster Roaming service indication to a SMF in corresponding service operations during PDU Session establishment procedure; and providing (step 502) a Disaster Roaming service indication to a PCF during Registration procedure.
  • this provides means to apply differentiated policy control at the mobility and session level for UE registered for disaster roaming service.
  • an Operator can apply differentiated policy control for mobility and session for UE disaster roaming service.
  • Figure 6 illustrates a method performed by a network node, such as a SMF, and/or a PCF for enabling Disaster Roaming.
  • the method includes one or more of: receiving (step 600) a Disaster Roaming service indication from an AMF in corresponding service operations during PDU Session establishment procedure; and receiving (step 602) a Disaster Roaming service indication from an AMF.
  • this provides means to apply differentiated policy control at the mobility and session level for UE registered for disaster roaming service. In this way, an Operator can apply differentiated policy control for mobility and session for UE disaster roaming service.
  • Figure 7 illustrates a method performed by various network nodes for enabling Disaster Roaming.
  • a method for enabling Disaster Roaming includes: receiving (step 700), by the AMF, from a UE a Disaster Roaming service indication during a registration.
  • the AMF optionally stores the Disaster Roaming service indication in a PDU session context (step 702).
  • the AMF provides (step 704) the Disaster Roaming service indication to a SMF in corresponding service operations during a PDU Session establishment procedure.
  • the SMF stores (step 706) the Disaster Roaming service indication in a context (e.g., a SM context).
  • the AMF provides (step 708) the Disaster Roaming service indication to a PCF during a Registration procedure.
  • the AMF provides (step 710) the Disaster Roaming service indication to an AUSF and/or a UDM.
  • the AMF provides the Disaster Roaming service indication to AUSF and UDM during communication as specified in TS 23.502 [3] clause 4.2.2.
  • the AMF provides also the Disaster Roaming service indication to SMF during PDU Session Establishment procedure as specified in TS 23.502 [3] clause 4.2.3.
  • the NFs interacting with CHF shall include the Disaster Roaming service information if it is available.
  • the HPLMN or registered PLMN may provide disaster roaming wait range information to control when the UE can initiate the registration for Disaster Roaming service upon arriving in the PLMN providing Disaster Roaming service as specified in TS 23.122[17] and 24.501[47].
  • the HPLMN or registered PLMN may provide disaster roaming wait range information to control when the UE can initiate the registration upon returning to the PLMN previously with Disaster Condition.
  • the AMF requests it from the AUSF; if Tracing Requirements about the UE are available at the AMF, the AMF provides Tracing Requirements in its request to AUSF.
  • the AMF also provides the Disaster Roaming service indication.
  • the AUSF shall execute authentication of the UE. The authentication is performed as described in TS 33.501 [15].
  • the AUSF selects a UDM as described in clause 6.3.8 of TS 23.501 [2] and gets the authentication data from UDM.
  • the AUSF also provides the Disaster Roaming service indication if received from AMF.
  • the AMF also provides the Disaster Roaming service indication.
  • the UDM provides applicable subscription data for Disaster Roaming service to the AMF based on operator policy.
  • Service Operation name Nudm_SDM_Get, Nsmf_PDUSession_Create, Nsmf_PDUSession_CreateSMContext, and/or Service operation name: Nudm_UECM_Registration: inputs can include Disaster Roaming indication.
  • Nsmf_PDUSession_CreateSMContext Request (SUPI, selected DNN, UE requested DNN, S-NSSAI(s), PDU Session ID, AMF ID, Request Type, [PCF ID, Same PCF Selection Indication], Priority Access, [Small Data Rate Control Status], N1 SM container (PDU Session Establishment Request), User location information, Access Type, RAT Type, PEI, GPSI, UE presence in LADN service area, Subscription For PDU Session Status Notification, DNN Selection Mode, Trace Requirements, Control Plane CIoT 5GS Optimisation indication, Control Plane Only indicator, Satellite backhaul category, [PVS FQDN or PVS IP address], [Disaster Roaming service indication]) or Nsmf_PDUS
  • the AMF provides the Disaster Roaming service indication if UE context stored in AMF indicating UE is registered for Disaster Roaming service.
  • V-SMF to H-SMF Nsmf_PDUSession_Create Request (SUPI, GPSI (if available), V-SMF SM Context ID, DNN, S-NSSAI with the value defined by the HPLMN, PDU Session ID, V-SMF ID, V-CN-Tunnel-Info, PDU Session Type, PCO, Number Of Packet Filters, User location information, Access Type, RAT Type, PCF ID, [Small Data Rate Control Status], SM PDU DN Request Container, DNN Selection Mode, Control Plane CIoT 5GS Optimisation Indication, [Always-on PDU Session Requested], AMF ID, Serving Network, the QoS constraints from the VPLMN, Satellite backhaul category, Disaster Roaming service indication ) or Nsmf_PDUSession_Update Request (V-CN- Tunnel-Info, PCO, User location information, Access Type, RAT Type, SM PDU DN
  • Protocol Configuration Options may contain information that H-SMF may needs to properly establish the PDU Session (e.g., SSC mode or SM PDU DN Request Container to be used to authenticate the UE by the DN- AAA as defined in clause 4.3.2.3).
  • the H-SMF may use DNN Selection Mode when deciding whether to accept or reject the UE request. If the V-SMF does not receive any response from the H-SMF due to communication failure on the N16 interface, depending on operator policy the V-SMF may create the PDU Session to one of the alternative H- SMF(s) if additional H-SMF information is provided in step 3a, as specified in detail in TS 29.502 [36].
  • the Small Data Rate Control Status is included if received from the AMF.
  • the Control Plane CIoT 5GS Optimisation Indication is set by the V-SMF, if the PDU Session is intended for Control Plane CIoT 5GS Optimisation.
  • the QoS constraints from the VPLMN contains a 5QI and corresponding ARP value that the VPLMN can accept for the QoS Flow associated with the default QoS rule and the highest Session- AMBR that the VPLMN can accept.
  • the Disaster Roaming service indication is included if the indication is received from AMF in step 3a above.
  • SM Context of a PDU Session transferred between I- SMF(s) or between V-SMF(s) can include: Disaster Roaming: Indicates the UE is registered for Disaster Roaming service.
  • FIG. 8 shows a UE 800 in accordance with some embodiments.
  • 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 Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, 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/integ rated wireless device, etc.
  • Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 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).
  • D2D Device-to-Device
  • DSRC Dedicated Short-Range Communication
  • V2V Vehicle-to-Vehicle
  • V2I Vehicle-to-Infrastructure
  • V2X Vehicle-to-Everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • 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).
  • a UE may represent a device that is not intended
  • the UE 800 includes processing circuitry 802 that is operatively coupled via a bus 804 to an input/output interface 806, a power source 808, memory 810, a communication interface 812, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 8. 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 802 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 810.
  • the processing circuitry 802 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.
  • the processing circuitry 802 may include multiple Central Processing Units (CPUs).
  • the input/output interface 806 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 800.
  • 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.
  • USB Universal Serial Bus
  • the power source 808 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 808 may further include power circuitry for delivering power from the power source 808 itself, and/or an external power source, to the various parts of the UE 800 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging the power source 808.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 808 to make the power suitable for the respective components of the UE 800 to which power is supplied.
  • the memory 810 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 810 includes one or more application programs 814, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 816.
  • the memory 810 may store, for use by the UE 800, any of a variety of various operating systems or combinations of operating systems.
  • the memory 810 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 Inline Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external microDIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and/or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof.
  • RAID Redundant Array of Independent Disks
  • HD-DVD High Density Digital Versatile Disc
  • HDDS Holographic Digital Data Storage
  • DIMM Dual Inline Memory Module
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a 'SIM card.
  • the memory 810 may allow the UE 800 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 810, which may be or comprise a device-readable storage medium.
  • the processing circuitry 802 may be configured to communicate with an access network or other network using the communication interface 812.
  • the communication interface 812 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 822.
  • the communication interface 812 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 818 and/or a receiver 820 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 818 and receiver 820 may be coupled to one or more antennas (e.g., the antenna 822) and may share circuit components, software, or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 812 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, NFC, 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.
  • GPS Global Positioning System
  • Communications may be implemented according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol/Internet Protocol (TCP/IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.
  • a UE may provide an output of data captured by its sensors, through its communication interface 812, or 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).
  • 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.
  • the states of the actuator, the motor, or the switch may change.
  • 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.
  • a UE when in the form of an 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 television, 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 VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device,
  • AR
  • a UE may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • 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.
  • 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.
  • a UE might comprise the sensor and the actuator and handle communication of data for both the speed sensor and the actuators.
  • FIG. 9 shows a network node 900 in accordance with some embodiments.
  • 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, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).
  • APs e.g., radio APs
  • BSs Base Stations
  • eNBs evolved Node Bs
  • gNBs NR Node Bs
  • BSs 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 BSs, pico BSs, micro BSs, or macro BSs.
  • a BS 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 BS such as centralized digital units and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs Remote Radio Heads
  • Parts of a distributed radio BS may also be referred to as nodes in a Distributed Antenna System (DAS).
  • DAS Distributed Antenna System
  • 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 BS 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).
  • MSR Multi-Standard Radio
  • RNCs Radio Network Controllers
  • BSCs Base Transceiver Stations
  • MCEs Multi- Cell/Multicast Coordination Entities
  • OFM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evol
  • the network node 900 includes processing circuitry 902, memory 904, a communication interface 906, and a power source 908.
  • the network node 900 may be composed of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 900 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple Node Bs.
  • each unique Node B and RNC pair may in some instances be considered a single separate network node.
  • the network node 900 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 904 for different RATs) and some components may be reused (e.g., an antenna 910 may be shared by different RATs).
  • the network node 900 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 900, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (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 the network node 900.
  • the processing circuitry 902 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, 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 900 components, such as the memory 904, to provide network node 900 functionality.
  • the processing circuitry 902 includes a System on a Chip (SOC).
  • the processing circuitry 902 includes one or more of Radio Frequency (RF) transceiver circuitry 912 and baseband processing circuitry 914.
  • RF Radio Frequency
  • the RF transceiver circuitry 912 and the baseband processing circuitry 914 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 the RF transceiver circuitry 912 and the baseband processing circuitry 914 may be on the same chip or set of chips, boards, or units.
  • the memory 904 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, RAM, 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 nonvolatile, 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 902.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, 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)
  • the memory 904 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 902 and utilized by the network node 900.
  • the memory 904 may be used to store any calculations made by the processing circuitry 902 and/or any data received via the communication interface 906.
  • the processing circuitry 902 and the memory 904 are integrated.
  • the communication interface 906 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE.
  • the communication interface 906 comprises port(s)/terminal(s) 916 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 906 also includes radio front-end circuitry 918 that may be coupled to, or in certain embodiments a part of, the antenna 910.
  • the radio front-end circuitry 918 comprises filters 920 and amplifiers 922.
  • the radio front-end circuitry 918 may be connected to the antenna 910 and the processing circuitry 902.
  • the radio front-end circuitry 918 may be configured to condition signals communicated between the antenna 910 and the processing circuitry 902.
  • the radio front-end circuitry 918 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 918 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 920 and/or the amplifiers 922. The radio signal may then be transmitted via the antenna 910. Similarly, when receiving data, the antenna 910 may collect radio signals which are then converted into digital data by the radio front-end circuitry 918. The digital data may be passed to the processing circuitry 902. In other embodiments, the communication interface 906 may comprise different components and/or different combinations of components.
  • the network node 900 does not include separate radio front-end circuitry 918; instead, the processing circuitry 902 includes radio front-end circuitry and is connected to the antenna 910. Similarly, in some embodiments, all or some of the RF transceiver circuitry 912 is part of the communication interface 906. In still other embodiments, the communication interface 906 includes the one or more ports or terminals 916, the radio front-end circuitry 918, and the RF transceiver circuitry 912 as part of a radio unit (not shown), and the communication interface 906 communicates with the baseband processing circuitry 914, which is part of a digital unit (not shown).
  • the antenna 910 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 910 may be coupled to the radio front-end circuitry 918 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 910 is separate from the network node 900 and connectable to the network node 900 through an interface or port.
  • the antenna 910, the communication interface 906, and/or the processing circuitry 902 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 900. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 910, the communication interface 906, and/or the processing circuitry 902 may be configured to perform any transmitting operations described herein as being performed by the network node 900. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment.
  • the power source 908 provides power to the various components of the network node 900 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 908 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 900 with power for performing the functionality described herein.
  • the network node 900 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 908.
  • the power source 908 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.
  • Embodiments of the network node 900 may include additional components beyond those shown in Figure 9 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.
  • the network node 900 may include user interface equipment to allow input of information into the network node 900 and to allow output of information from the network node 900. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 900.
  • FIG 10 is a block diagram of a host 1000, which may be an embodiment of the host 416 of Figure 4, in accordance with various aspects described herein.
  • the host 1000 may be or comprise various combinations of 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 1000 may provide one or more services to one or more UEs.
  • the host 1000 includes processing circuitry 1002 that is operatively coupled via a bus 1004 to an input/output interface 1006, a network interface 1008, a power source 1010, and memory 1012.
  • processing circuitry 1002 that is operatively coupled via a bus 1004 to an input/output interface 1006, a network interface 1008, a power source 1010, and memory 1012.
  • 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 8 and 9, such that the descriptions thereof are generally applicable to the corresponding components of the host 1000.
  • the memory 1012 may include one or more computer programs including one or more host application programs 1014 and data 1016, which may include user data, e.g. data generated by a UE for the host 1000 or data generated by the host 1000 for a UE.
  • Embodiments of the host 1000 may utilize only a subset or all of the components shown.
  • the host application programs 1014 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (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, and heads-up display systems).
  • video codecs e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9
  • audio codecs e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711
  • FLAC Free Lossless Audio Codec
  • AAC Advanced Audio Cod
  • the host application programs 1014 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 1000 may select and/or indicate a different host for Over-The-Top (OTT) services for a UE.
  • the host application programs 1014 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 (DASH or MPEG-DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • DASH or MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices, and networking resources.
  • 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 1100 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.
  • VMs Virtual Machines
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Applications 1102 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1104 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 1106 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 1108A and 1108B (one or more of which may be generally referred to as VMs 1108), and/or perform any of the functions, features, and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1106 may present a virtual operating platform that appears like networking hardware to the VMs 1108.
  • the VMs 1108 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 1106. Different embodiments of the instance of a virtual appliance 1102 may be implemented on one or more of the VMs 1108, 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. [0242] In the context of NFV, a VM 1108 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, nonvirtualized machine.
  • NFV Network Function Virtualization
  • Each of the VMs 1108, and that part of the hardware 1104 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs 1108, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1108 on top of the hardware 1104 and corresponds to the application 1102.
  • the hardware 1104 may be implemented in a standalone network node with generic or specific components.
  • the hardware 1104 may implement some functions via virtualization.
  • the hardware 1104 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 1110, which, among others, oversees lifecycle management of the applications 1102.
  • the hardware 1104 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 RAN or a BS.
  • some signaling can be provided with the use of a control system 1112 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 12 shows a communication diagram of a host 1202 communicating via a network node 1204 with a UE 1206 over a partially wireless connection in accordance with some embodiments.
  • embodiments of the host 1202 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1202 also includes software, which is stored in or is accessible by the host 1202 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 1206 connecting via an OTT connection 1250 extending between the UE 1206 and the host 1202.
  • a host application may provide user data which is transmitted using the OTT connection 1250.
  • the network node 1204 includes hardware enabling it to communicate with the host 1202 and the UE 1206 via a connection 1260.
  • the connection 1260 may be direct or pass through a core network (like the core network 406 of Figure 4) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 1206 includes hardware and software, which is stored in or accessible by the UE 1206 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 the UE 1206 with the support of the host 1202.
  • 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 the UE 1206 with the support of the host 1202.
  • an executing host application may communicate with the executing client application via the OTT connection 1250 terminating at the UE 1206 and the host 1202.
  • 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 1250 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
  • the OTT connection 1250 may extend via the connection 1260 between the host 1202 and the network node 1204 and via a wireless connection 1270 between the network node 1204 and the UE 1206 to provide the connection between the host 1202 and the UE 1206.
  • the connection 1260 and the wireless connection 1270, over which the OTT connection 1250 may be provided, have been drawn abstractly to illustrate the communication between the host 1202 and the UE 1206 via the network node 1204, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1202 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 1206.
  • the user data is associated with a UE 1206 that shares data with the host 1202 without explicit human interaction.
  • the host 1202 initiates a transmission carrying the user data towards the UE 1206.
  • the host 1202 may initiate the transmission responsive to a request transmitted by the UE 1206.
  • the request may be caused by human interaction with the UE 1206 or by operation of the client application executing on the UE 1206.
  • the transmission may pass via the network node 1204 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1212, the network node 1204 transmits to the UE 1206 the user data that was carried in the transmission that the host 1202 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1214, the UE 1206 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1206 associated with the host application executed by the host 1202.
  • the UE 1206 executes a client application which provides user data to the host 1202.
  • the user data may be provided in reaction or response to the data received from the host 1202.
  • the UE 1206 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 1206. Regardless of the specific manner in which the user data was provided, the UE 1206 initiates, in step 1218, transmission of the user data towards the host 1202 via the network node 1204.
  • the network node 1204 receives user data from the UE 1206 and initiates transmission of the received user data towards the host 1202.
  • the host 1202 receives the user data carried in the transmission initiated by the UE 1206.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1206 using the OTT connection 1250, in which the wireless connection 1270 forms the last segment. More precisely, the teachings of these embodiments may improve the e.g., data rate, latency, power consumption, etc. and thereby provide benefits such as e.g., reduced user waiting time, relaxed restriction on file size, improved content resolution, better responsiveness, extended battery lifetime, etc.
  • factory status information may be collected and analyzed by the host 1202.
  • the host 1202 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1202 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1202 may store surveillance video uploaded by a UE.
  • the host 1202 may store or control access to media content such as video, audio, VR, or AR which it can broadcast, multicast, or unicast to UEs.
  • the host 1202 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.
  • 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.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 1250 may be implemented in software and hardware of the host 1202 and/or the UE 1206.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1250 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or by supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1250 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 1204. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency, and the like by the host 1202.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection 1250 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • 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.
  • 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.
  • processing circuitry executing instructions stored in memory, which in certain embodiments may be a computer program product in the form of a non- transitory computer-readable storage medium.
  • 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 hardwired manner.
  • 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.
  • Embodiment 1 A method performed by an Access and Mobility Management Function, AMF, for enabling Disaster Roaming, the method comprising one or more of: a. providing (500) a Disaster Roaming service indication to a Session Management Function, SMF, in corresponding service operations during Protocol Data Unit, PDU, Session establishment procedure; and b. providing (502) a Disaster Roaming service indication to a Policy Control Function, PCF, during Registration procedure.
  • AMF Access and Mobility Management Function
  • Embodiment 2 The method of embodiment 1 wherein the Disaster Roaming service indication information is stored in Charging related data and/or local logs
  • Embodiment 3 The method of any of the previous embodiments further capable of implementing any of the embodiments discloses herein
  • Embodiment 4 The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node
  • Embodiment 5 A method performed by a network node, such as a Session Management Function, SMF, and/or a Policy Control Function, PCF, for enabling Disaster Roaming, the method comprising one or more of: a. receiving (600) a Disaster Roaming service indication from an Access and Mobility Management Function, AMF, in corresponding service operations during Protocol Data Unit, PDU, Session establishment procedure; and b. receiving (602) a Disaster Roaming service indication from an AMF.
  • a network node such as a Session Management Function, SMF, and/or a Policy Control Function, PCF
  • Embodiment 6 The method of embodiment 5 wherein the Disaster Roaming service indication information is stored in Charging related data and/or local logs.
  • Embodiment 7 The method of any of the previous embodiments further capable of implementing any of the embodiments discloses herein.
  • Embodiment 8 The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.
  • Embodiment 9 A user equipment or an Access and Mobility Management Function, AMF, for enabling Disaster Roaming, comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.
  • AMF Access and Mobility Management Function
  • Embodiment 10 A network node for enabling Disaster Roaming, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.
  • Embodiment 11 A user equipment (UE) or an Access and Mobility Management Function, AMF, for enabling Disaster Roaming, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
  • UE user equipment
  • AMF Access and Mobility Management Function
  • Embodiment 12 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to receive the user data from the host.
  • OTT over-the-top
  • Embodiment 13 The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.
  • Embodiment 14 The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 15 A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.
  • UE user equipment
  • Embodiment 16 The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.
  • Embodiment 17 The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • Embodiment 18 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.
  • OTT over-the-top
  • Embodiment 19 The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.
  • Embodiment 20 The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 21 A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.
  • UE user equipment
  • Embodiment 22 The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.
  • Embodiment 23 The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • Embodiment 24 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • OTT over-the-top
  • Embodiment 25 The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.
  • Embodiment 26 A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • Embodiment 27 The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.
  • Embodiment 28 The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 29 A communication system configured to provide an over-the- top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • Embodiment 30 The communication system of the previous embodiment, further comprising: the network node; and/or the user equipment.
  • Embodiment 31 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.
  • OTT over-the-top
  • Embodiment 32 The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 33 The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.
  • Embodiment 34 A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host.
  • UE user equipment
  • Embodiment 35 The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Emergency Management (AREA)
  • Environmental & Geological Engineering (AREA)
  • Public Health (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des systèmes et des procédés pour activer l'itinérance en cas de catastrophe. Dans certains modes de réalisation, un procédé mis en œuvre par une fonction de gestion d'accès et de mobilité (AMF) pour activer l'itinérance en cas de catastrophe comprend les étapes consistant à : recevoir, d'un équipement utilisateur (UE), une indication de service d'itinérance en cas de catastrophe au cours d'un enregistrement ; et fournir l'indication de service d'itinérance en cas de catastrophe à une fonction de gestion de session (SMF) dans des opérations de service correspondantes pendant une procédure d'établissement de session d'unités de données de protocole (PDU). De cette manière, un opérateur peut appliquer une commande de politique différenciée au niveau mobilité et session pour un UE enregistré pour un service d'itinérance en cas de catastrophe.
PCT/IB2022/059706 2021-10-08 2022-10-10 Indication d'itinérance en cas de catastrophe pour session et politique Ceased WO2023058009A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163253838P 2021-10-08 2021-10-08
US63/253,838 2021-10-08

Publications (1)

Publication Number Publication Date
WO2023058009A1 true WO2023058009A1 (fr) 2023-04-13

Family

ID=84047792

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2022/059706 Ceased WO2023058009A1 (fr) 2021-10-08 2022-10-10 Indication d'itinérance en cas de catastrophe pour session et politique

Country Status (1)

Country Link
WO (1) WO2023058009A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023241467A1 (fr) * 2022-06-16 2023-12-21 华为技术有限公司 Procédé de communication et appareil de communication
US20240365102A1 (en) * 2023-04-26 2024-10-31 Oracle International Corporation Data network name replacement for roaming subscribers
CN120151818A (zh) * 2025-05-14 2025-06-13 中国电信股份有限公司 空天地场景对终端授权卫星接入的方法、装置及相关设备
CN120166433A (zh) * 2025-03-17 2025-06-17 中国联合网络通信集团有限公司 一种核心网的容灾处理方法、装置、设备及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020204310A1 (fr) * 2019-04-02 2020-10-08 엘지전자 주식회사 Procédé pour faire face à une panne de réseau
WO2021007447A1 (fr) * 2019-07-09 2021-01-14 Ofinno, Llc Resélection de réseau lors d'un sinistre

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020204310A1 (fr) * 2019-04-02 2020-10-08 엘지전자 주식회사 Procédé pour faire face à une panne de réseau
US20220167185A1 (en) * 2019-04-02 2022-05-26 Lg Electronics Inc. Method for dealing with network failure
WO2021007447A1 (fr) * 2019-07-09 2021-01-14 Ofinno, Llc Resélection de réseau lors d'un sinistre

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Study on the support for minimization of service interruption; (Release 17)", no. V17.1.0, 25 September 2021 (2021-09-25), pages 1 - 112, XP052056826, Retrieved from the Internet <URL:https://ftp.3gpp.org/Specs/archive/24_series/24.811/24811-h10.zip 24811-h10.docx> [retrieved on 20210925] *
ERICSSON ET AL: "Introduction of MINT support", vol. SA WG2, no. E (e-meeting); 20210816 - 20210827, 28 August 2021 (2021-08-28), XP052054479, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG2_Arch/TSGS2_146E_Electronic_2021-08/Docs/S2-2106660.zip S2-2106660_was_2105812_23502_Registration for disaster roaming servicer.docx> [retrieved on 20210828] *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023241467A1 (fr) * 2022-06-16 2023-12-21 华为技术有限公司 Procédé de communication et appareil de communication
US20240365102A1 (en) * 2023-04-26 2024-10-31 Oracle International Corporation Data network name replacement for roaming subscribers
US12452641B2 (en) * 2023-04-26 2025-10-21 Oracle International Corporation Data network name replacement for roaming subscribers
CN120166433A (zh) * 2025-03-17 2025-06-17 中国联合网络通信集团有限公司 一种核心网的容灾处理方法、装置、设备及存储介质
CN120151818A (zh) * 2025-05-14 2025-06-13 中国电信股份有限公司 空天地场景对终端授权卫星接入的方法、装置及相关设备

Similar Documents

Publication Publication Date Title
US20240276217A1 (en) Application-specific gpsi retrieval
WO2023058009A1 (fr) Indication d&#39;itinérance en cas de catastrophe pour session et politique
US12407668B2 (en) Authorization of consumer network functions
US20240364600A1 (en) Topology hiding in 5gc with roaming
WO2023185737A1 (fr) Procédé et appareil permettant d&#39;effectuer une authentification/autorisation secondaire pour un dispositif terminal dans un réseau de communication
US20240235996A1 (en) Deterministic network entity for communications networks
US20250168120A1 (en) Methods for handling packet filters for interworking between a service based architecture, sba, network and an evolved packet system, eps, network as well as corresponding devices
US20250193767A1 (en) Data collection from user equipment on user equipment route selection policy usage
US20250159473A1 (en) Routing Indicator Update via UE Parameters Update (UPU) Procedure
WO2024079717A1 (fr) Rapport de rapports qoe au sn
WO2023218383A1 (fr) Systèmes et procédés pour permettre une configuration par service pour mt-sdt
CN118786705A (zh) 处理基于服务的架构（sba）网络与演进分组系统（eps）网络之间互通的分组过滤器的方法以及对应的设备
WO2024234945A1 (fr) Procédé et appareil d&#39;exposition d&#39;informations de tranche souscrite d&#39;ue
US12495029B2 (en) Data collection coordination function (DCCF) data access authorization without messaging framework
WO2024235213A1 (fr) Procédé et appareil de découverte et de synchronisation d&#39;eas sur des edn pour un groupe d&#39;application
WO2024208179A1 (fr) Procédé et appareil de service de diffusion/multidiffusion dépendant de l&#39;emplacement
WO2024172726A1 (fr) Systèmes et procédés de signalisation de paramètres de différenciation de radiomessagerie
WO2024144446A1 (fr) Optimisation de plan de commande pendant un changement d&#39;amf
WO2024117960A1 (fr) Filtre de liste de bandes de fréquences appliquées prédéfinies
WO2025155226A1 (fr) Procédure améliorée de rapport de mesure de qualité d&#39;expérience et de récupération de configurations de qualité d&#39;expérience
EP4569920A1 (fr) Restriction d&#39;utilisation basée sur l&#39;emplacement pour une tranche de réseau
WO2024074990A1 (fr) Authentification commandée par un réseau domestique
WO2023061980A1 (fr) Optimisation d&#39;architecture basée sur un service 5gc de sélection de saut suivant en itinérance qui est un mandataire de protection de périphérie de sécurité (sepp)
WO2025158176A1 (fr) Activation de profil sim d&#39;itinérance basée sur une politique
WO2024038340A1 (fr) Connexions en mode relais dans un réseau de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22798378

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22798378

Country of ref document: EP

Kind code of ref document: A1