User Equipment (UE) Aggregate Maximum Bit Rate (AMBR) for Emergency Services

Abstract

According to some embodiments, a core network node 15 is provided, the core network node 15 including processing circuitry 98 configured to: store a local UE aggregate maximum bit rate (AMBR) parameter to be applied to any user equipment (UE) 22 requesting emergency services; receive a request for emergency services from a first UE 22 via an access network node 16 after storing the local UE AMBR parameter; and cause transmission of a message to the access network node 16 including the local UE AMBR parameter for emergency service configuration for the first UE 22.

Description

[Technical Field]

[0001] The present disclosure relates to wireless communications, and more particularly to network functionality when a wireless device's (eg, UE's) aggregate maximum bit rate (AMBR) is unavailable. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP®) has developed and is developing standards for fourth-generation (4G) (also referred to as Long Term Evolution (LTE)) and fifth-generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WDs), as well as communication between network nodes and between WDs. 3GPP® is also developing standards for sixth-generation (6G) wireless communication networks.

[0003] In particular, in 5G, the aggregate maximum bit rate (AMBR) of a wireless device (e.g., user equipment (UE) AMBR) limits the aggregate bit rate that can be expected to be provided across all non-guaranteed bit rate (non-GBR) quality of service (QoS) flows of the wireless device (e.g., UE). Each (R)AN sets the UE AMBR to the sum of the session AMBRs of all active user plane PDU sessions to that (R)AN, up to the UE AMBR value received from the Access and Mobility Function (AMF). The UE AMBR is a parameter provided to the (R)AN by the AMF based on the subscribed UE AMBR value obtained from the UDM or the dynamic serving network UE AMBR (e.g., for roaming subscribers) obtained from the Policy Control Function (PCF). The AMF provides the UE AMBR provided by the PCF to the (R)AN, if available. The UE AMBR is measured over an AMBR averaging window, which may be a standardized value. The UE AMBR is not applicable to GBR QoS flows.

[0004] The UE AMBR is signaled to the NG-RAN node (e.g., network node, gNB, etc.) either during the initial radio device context configuration procedure or during the PDU session resource configuration procedure. If non-GBR QoS is configured, 3GPP specifications mandate that the UE AMBR be sent to the NG-RAN node.

[0005] In some cases when performing or implementing emergency access via the packet core, the wireless device may not be able to register with the network and remain unauthenticated, or it may not have a Universal Integrated Circuit Card (UICC) and therefore may not have a UDM record, and due to regulations in some countries this wireless device needs / must be authorized to set up emergency services.

[0006] An unauthenticated wireless device may be a wireless device that does not have a Universal Subscriber Identity Module (USIM), or a wireless device that has a USIM but has failed authentication. There may also be a scenario where the wireless device is authenticated (via the Authentication Server Function (AUSF)), but the AMF fails to receive the wireless device's subscription data from the UDM.

[0007] When emergency services are configured, it is based on the DNN (e.g., data network name) configured in the service network for emergency services, and if the emergency access is voice, there may be a QoS flow for IP Multimedia Subsystem (IMS) signaling (non-GBR service) and a QoS flow for conversational voice (GBR service).

[0008] According to 3GPP standards, in certain cases the AMF may not be able to provide the UE AMBR, but the NG-RAN node requires the UE AMBR for non-GBR IMS signaling, so emergency services cannot be configured in the NG-RAN node.

[0009] Therefore, 3GPP does not define a procedure to support emergency service setup when the UE AMBR cannot be obtained by the AMF during the emergency service setup procedure and cannot be sent from the AMF to the NG-RAN node. Summary of the Invention [Problem to be solved by the invention]

[0010] Some embodiments advantageously provide methods, systems, and apparatus for network functionality when UE aggregate maximum bit rate (AMBR) is unavailable.

[0011] One or more embodiments provide both a core network (CN)-based solution and a radio access network (RAN)-based solution for configuring emergency services without an available UE AMBR from the UDM or PCF (e.g., the wireless device is not authenticated or the wireless device is authenticated without a UE AMBR), or when the wireless device is authenticated (via the AMF) but the AMF fails to obtain wireless device subscription data from the UDM, or when the wireless device does not have a subscription (no UICC) and therefore no UE AMBR is available from the UDM or PCF. [Means for solving the problem]

[0012] According to one aspect of the present disclosure, a core network node is provided, the core network node including: processing circuitry configured to store a local UE aggregate maximum bit rate (AMBR) parameter to be applied to any user equipment (UE) requesting emergency services; after storing the local UE AMBR parameter, receive a request for emergency services from a first UE via an access network node; and cause transmission, toward the access network node, of a message including the local UE AMBR parameter for emergency service configuration for the first UE.

[0013] According to one or more embodiments of this aspect, the processing circuitry is further configured to determine that the core network node does not have subscription data stored for the first UE, and the sending of the message including the local UE AMBR parameter is based on the determination.

[0014] According to one or more embodiments of this aspect, the sending of the message including the local UE AMBR parameter is based on the UE AMBR parameter not being obtained from a network entity.

[0015] According to one or more embodiments of this aspect, the network entity is a Unified Data Manager (UDM) node.

[0016] According to one or more embodiments of this aspect, the network entity is a Policy Control Function (PCF) node.

[0017] According to one or more embodiments of this aspect, the core network node is an Access and Mobility Management Function (AMF).

[0018] According to one or more embodiments of this aspect, the emergency service corresponds to an Internet Protocol Multimedia Subsystem (IMS) emergency session.

[0019] According to one or more embodiments of this aspect, the processing circuitry is further configured, after storing the local UE AMBR parameter, to receive, via the access network node, a request for emergency services from the second UE, and to cause transmission, towards the access network node, of a message including the local UE AMBR parameter for emergency service configuration for the second UE.

[0020] According to one or more embodiments of this aspect, the local UE AMBR parameter is stored as part of emergency configuration data that applies to emergency services.

[0021] According to another aspect of the present disclosure, there is provided a method performed by a core network node, the method including: storing a local UE aggregate maximum bit rate (AMBR) parameter to be applied to any user equipment (UE) requesting emergency services; after storing the local UE AMBR parameter, receiving a request for emergency services from a first UE via the access network node; and transmitting a message to the access network node including the local UE AMBR parameter for emergency service configuration for the first UE.

[0022] According to one or more embodiments of this aspect, the method further includes determining that the core network node does not have subscription data stored for the first UE, and transmitting the message including the local UE AMBR parameter is based on the determination.

[0023] According to one or more embodiments of this aspect, the sending of the message including the local UE AMBR parameter is based on the UE AMBR parameter not being obtained from a network entity.

[0024] According to one or more embodiments of this aspect, the network entity is a Unified Data Manager (UDM) node.

[0025] According to one or more embodiments of this aspect, the network entity is a Policy Control Function (PCF) node.

[0026] According to one or more embodiments of this aspect, the core network node is an Access and Mobility Management Function (AMF).

[0027] According to one or more embodiments of this aspect, the emergency service corresponds to an Internet Protocol Multimedia Subsystem (IMS) emergency session.

[0028] According to one or more embodiments of this aspect, the method further includes, after storing the local UE AMBR parameter, receiving a request for emergency services from the second UE via the access network node.

[0029] According to one or more embodiments of this aspect, a message including a local UE AMBR parameter for emergency service configuration for the second UE is sent to an access network node.

[0030] According to one or more embodiments of this aspect, the local UE AMBR parameter is stored as part of emergency configuration data that applies to emergency services.

[0031] According to another aspect of the present disclosure, a computer-readable medium stores program instructions that, when executed by a processor, configure the processor to perform one or more of the methods described herein.

[0032] A more complete understanding of the present embodiments, together with their attendant advantages and features, will be readily appreciated by reference to the following detailed description, when considered in conjunction with the accompanying drawings. [Brief explanation of the drawings]

[0033] [Figure 1] 1 is a schematic diagram of an exemplary network architecture illustrating a communication system connected to a host computer through an intermediate network in accordance with the principles of the present disclosure; [Figure 2] 1 is a block diagram of a host computer communicating with a wireless device via a network node over at least a partial wireless connection, in accordance with some embodiments of the present disclosure. [Figure 3] 1 is a flowchart illustrating an example method performed in a communication system including a host computer, a network node, and a wireless device for executing a client application on the wireless device, according to some embodiments of the present disclosure. [Figure 4]1 is a flowchart illustrating an example method performed in a communication system including a host computer, a network node, and a wireless device for receiving user data at the wireless device, according to some embodiments of the present disclosure. [Figure 5] 1 is a flowchart illustrating an exemplary method performed in a communication system including a host computer, a network node, and a wireless device for receiving user data at a host computer from a wireless device, according to some embodiments of the present disclosure. [Figure 6] 1 is a flowchart illustrating an exemplary method performed in a communication system including a host computer, a network node, and a wireless device for receiving user data at a host computer, according to some embodiments of the present disclosure. [Figure 7] 6 is a flowchart of an example process in a network node according to some embodiments of the present disclosure. [Figure 8] 1 is a flowchart of an example process in a core network node, in accordance with some embodiments of the present disclosure. [Figure 9] 10 is a flowchart of another example process in a core network node, in accordance with some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0034] Before describing the details of the exemplary embodiments, it should be noted that the embodiments primarily consist of a combination of device components and processing steps related to network functionality when a UE AMBR is unavailable, not received, and / or not checked. Accordingly, components are described with conventional symbols in the drawings to show only the specific details relevant to understanding the embodiments and in a degree of detail that will be readily apparent to one of ordinary skill in the art having the benefit of this disclosure so as not to obscure the disclosure. Like reference numerals refer to like components throughout this description.

[0035] As used herein, relative terms such as "first," "second," "upper," and "lower" may be used only to distinguish one entity or element from another, without implying or requiring a physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the concepts described herein. As used herein, the singular forms are intended to include the plural forms as well, unless the context clearly dictates otherwise. It will be further understood that as used herein, the terms "comprise," "comprising," and / or "having" specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0036] In the embodiments described herein, coupling terms such as "communicating with" may be used to indicate electrical or data communication that may be achieved, for example, by physical contact, induction, electromagnetic radiation, radio signals, infrared signals, or optical signals. Those skilled in the art will appreciate that multiple components may interoperate and modifications and variations are possible to achieve electrical and data communication.

[0037] In some embodiments described herein, the terms "coupled," "connected," and the like may be used herein to indicate a connection, which need not be direct, and may include wired and / or wireless connections.

[0038] The term "network node" as used herein may refer to any type of network node included in a wireless network, which may further include any of a base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), gNodeB (gNB), evolved NodeB (eNB or eNodeB), NodeB, multi-standard radio (MSR) radio node such as an MSR BS, a multi-cell / multicast coordination entity (MCE), an integrated access and backhaul (IAB) node, a relay node, a donor node controlling a relay, a wireless access point (AP), a transmission point, a transmitting node, a remote radio unit (RRU), a remote radio head (RRH), a self-organizing network (SON) node, a coordination node, a positioning node, an MDT node, etc.), an external node (e.g., a third-party node, a node outside the current network), a node of a distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. A network node may also include test equipment. As used herein, the term "wireless node" may also be used to refer to a wireless device (WD) or a wireless network node, such as a wireless device (WD).

[0039] In some embodiments, the non-limiting terms wireless device (WD) or user equipment (UE) are used interchangeably. A WD herein may be any type of wireless device capable of communicating with a network node or another WD via wireless signals, such as a wireless device (WD). A WD may include a wireless communication device, a target device, a device-to-device (D2D) WD, a machine-type WD, or a WD capable of machine-to-machine (M2M) communication, a low-cost and / or low-complexity WD, a sensor with a WD, a tablet, a mobile terminal, a smartphone, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a USB dongle, a customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IoT) device, etc.

[0040] Also, in some embodiments, the general term "radio network node" is used, which may be any type of radio network node, which may include any of a base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, multi-cell / multicast coordination entity (MCE), IAB node, relay node, access point, radio access point, remote radio unit (RRU), and remote radio head (RRH).

[0041] It should be noted that although terminology from one particular wireless system, such as 3GPP® LTE and / or New Radio (NR), may be used in this disclosure, this should not be considered to limit the scope of this disclosure to only the aforementioned systems. Other wireless systems, including but not limited to Wideband Code Division Multiple Access (WCDMA®), WiMax (Worldwide Interoperability for Microwave Access), Ultra Mobile Broadband (UMB), and GSM (Global System for Mobile Communications), can also benefit from utilizing the ideas covered in this disclosure.

[0042] Furthermore, it should be noted that functionality described herein as being performed by a wireless device or a network node may be distributed across multiple wireless devices and / or network nodes. In other words, it is contemplated that the functionality of the network nodes and wireless devices described herein is not limited to being performed by a single physical device, but may in fact be distributed among several physical devices.

[0043] In some embodiments, a general description of the form "one of A and B" corresponds to A or B. In some embodiments, at least one of A and B corresponds to A, B, or AB, or one or more of A and B. In some embodiments, at least one of A, B, and C corresponds to one or more of A, B, and C, and / or A, B, C, or combinations thereof.

[0044] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted to have a meaning consistent with their meaning in the context of the present specification and related art, and will not be interpreted in an ideal or overly formal sense unless expressly defined herein.

[0045] Some embodiments relate to network functionality when UE aggregate maximum bit rate (AMBR) is unavailable.

[0046] Referring now to the drawings, where like elements are referred to by like reference numerals, FIG. 1 illustrates a schematic diagram of a communication system 10 according to one embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G), comprising an access network 12, such as a radio access network, and a core network 14. The core network 14 includes one or more core network nodes 15 (collectively referred to as core network nodes 15) that perform one or more core network functions. The core network nodes may be one or more of an AMF, a UDM, a PCF, etc. The access network 12 comprises multiple network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NBs, eNBs, gNBs, or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c may be connectable to the core network 14 via a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, a corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to a corresponding network node 16b. While multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to situations where a single WD is in a coverage area or where a single WD connects to a corresponding wireless network node 16. For convenience, only two WDs 22 and three network nodes 16 are shown, but it should be noted that a communication system may include many more WDs 22 and network nodes 16.

[0047] It is also understood that the WD 22 may simultaneously communicate with and / or be configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, the WD 22 may have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, the WD 22 may communicate with an eNB of LTE / E-UTRAN and a gNB of NR / NG-RAN.

[0048] The communication system 10 itself may be connected to a host computer 24, which may be embodied by standalone server, cloud-implemented server, distributed server hardware and / or software, or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. The connection 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend through an optional intermediate network 30. The intermediate network 30 may be either a public, private, or hosted network, or a combination of two or more thereof. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may include two or more subnetworks (not shown).

[0049] The communication system of FIG. 1 as a whole enables a connection between one of the connected WDs 22 a, 22 b and the host computer 24. The connection may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22 a, 22 b are configured to communicate data and / or signaling via the OTT connection using the access network 12, the core network 14, any intermediate networks 30, and possibly additional intermediary infrastructure (not shown). The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of the routing of the uplink and downlink communications. For example, the network node 16 may not be informed, or need not be informed, about the past routing of incoming downlink communications with data originating from the host computer 24 being forwarded (e.g., handed over) to the connected WD 22 a. Similarly, the network node 16 need not be aware of the future routing of outgoing uplink communications from the WD 22 a toward the host computer 24.

[0050] The network node 16 is configured to include a node unit 32 configured to perform one or more network node 16 functions described herein, such as with respect to network functioning when the UE AMBR is unavailable. The core network node 15 is configured to include a configuration unit 34 configured to perform one or more core network node 15 functions described herein, such as with respect to network functioning when the UE AMBR is unavailable.

[0051] An exemplary implementation of the embodiments of the WD 22, network node 16, core network node 15, and host computer 24 described in the previous paragraph will be described with reference to FIG. 2. In the communication system 10, the host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to establish and maintain wired or wireless connections with interfaces of different communication devices of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and / or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor and memory such as a central processing unit, the processing circuitry 42 may include integrated circuits for processing and / or control, such as one or more processors and / or processor cores adapted to execute instructions, and / or an FPGA (Field Programmable Gate Array) and / or an ASIC (Application Specific Integrated Circuit). Processing circuitry 44 may be configured to access (e.g., write to and / or read from) memory 46, which may include any type of volatile and / or non-volatile memory, such as cache, and / or buffer memory, and / or RAM (random access memory), and / or ROM (read only memory), and / or optical memory, and / or EPROM (erasable programmable read only memory).

[0052] Processing circuitry 42 may be configured to control and / or cause any of the methods and / or processes described herein to be performed by, for example, host computer 24. Processor 44 corresponds to one or more processors 44 for performing the functions of host computer 24 described herein. Host computer 24 includes memory 46 configured to store data, program software code, and / or other information described herein. In some embodiments, software 48 and / or host application 50 may include instructions that, when executed by processor 44 and / or processing circuitry 42, cause processor 44 and / or processing circuitry 42 to perform the processes described herein in connection with host computer 24. The instructions may be software associated with host computer 24.

[0053] Software 48 may be executable by processing circuitry 42. Software 48 includes a host application 50. Host application 50 may be operable to provide services to remote users, such as WD 22, connecting via an OTT connection 52 terminated at WD 22 and host computer 24. In providing services to the remote users, host application 50 may provide user data to be transmitted using OTT connection 52. "User data" may be data and information described herein as implementing the described functionality. In one embodiment, host computer 24 may be configured to provide control and functionality to a service provider and may be operated by or on behalf of a service provider. Processing circuitry 42 of host computer 24 may enable host computer 24 to observe, monitor, control, transmit to, and / or receive from network node 16, core network node 15, and / or wireless device 22.

[0054] The communication system 10 further includes a network node 16 including hardware 58 provided in the communication system 10 to enable communication with the host computer 24 and the WD 22. The hardware 58 may include a communication interface 60 for establishing and maintaining wired or wireless connections with interfaces of different communication devices in the communication system 10, and a radio interface 62 for establishing and maintaining radio connections 64 with at least the WD 22 located in the coverage area 18 served by the network node 16. The radio interface 62 may be formed as or include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24 and / or the core network node 15. The connection 66 may be direct or may pass through the core network 14 of the communication system 10 and / or one or more intermediate networks 30 external to the communication system 10.

[0055] In the illustrated embodiment, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and memory 72. In particular, in addition to or instead of a central processing unit-like processor and memory, the processing circuitry 68 may include integrated circuits for processing and / or control, e.g., one or more processors and / or processor cores adapted to execute instructions, and / or FPGAs (field programmable gate arrays), and / or ASICs (application-specific integrated circuits). The processing circuitry 70 may be configured to access (e.g., write to and / or read from) memory 72, which may include any type of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).

[0056] As such, network node 16 further includes software 74, e.g., stored within memory 72 or stored in external memory (e.g., a database, storage array, network storage device, etc.) accessible by network node 16 via an external connection. Software 74 may be executable by processing circuitry 68. Processing circuitry 68 may be configured to control and / or cause any of the methods and / or processes described herein to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing the functions of network node 16 described herein. Memory 72 is configured to store data, program software code, and / or other information described herein. In some embodiments, software 74 may include instructions that, when executed by processor 70 and / or processing circuitry 68, cause processor 70 and / or processing circuitry 68 to perform the processes described herein in connection with network node 16. For example, the processing circuitry 68 of the network node 16 may include a node unit 32 configured to perform one or more of the network node 16 functions described herein, such as with respect to network functionality when the UE AMBR is unavailable.

[0057] The communication system 10 further includes the previously mentioned WD 22. The WD 22 may have hardware 80 that may include a wireless interface 82 configured to establish and maintain a wireless connection 64 with a network node 16 that serves the coverage area 18 in which the WD 22 is currently located. The wireless interface 82 may be formed as or include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0058] The WD 22 hardware 80 further includes processing circuitry 84. Processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a central processing unit-like processor and memory, processing circuitry 84 may include integrated circuits for processing and / or control, such as one or more processors and / or processor cores adapted to execute instructions, and / or FPGAs (field programmable gate arrays), and / or ASICs (application-specific integrated circuits). Processing circuitry 86 may be configured to access (e.g., write to and / or read from) memory 88, which may include any type of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).

[0059] As such, the WD 22 may further include software 90, for example, stored in the memory 88 of the WD 22 or in an external memory accessible by the WD 22 (e.g., a database, a storage array, a network storage device, etc.). The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide services to a human or non-human user via the WD 22 with the support of the host computer 24. A host application 50 running on the host computer 24 may communicate with the running client application 92 via the WD 22 and an OTT connection 52 terminating at the host computer 24. In providing services to a user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data to provide.

[0060] Processing circuitry 84 may be configured to control and / or cause any of the methods and / or processes described herein to be performed, for example, by WD22. Processor 86 corresponds to one or more processors 86 for performing the functions of WD22 described herein. WD22 includes memory 88 configured to store data, program software code, and / or other information described herein. In some embodiments, software 90 and / or client application 92 may include instructions that, when executed by processor 86 and / or processing circuitry 84, cause processor 86 and / or processing circuitry 84 to perform the processes described herein in connection with WD22.

[0061] The communication system 10 further includes a core network node 15 that includes hardware 94 that is provided in the communication system 10 and enables communication with the host computer 24 and the network node 16. The hardware 94 may include a communication interface 96 for establishing and maintaining wired or wireless connections with interfaces of different communication devices in the communication system 10.

[0062] In the illustrated embodiment, the hardware 94 of the network node 16 further includes processing circuitry 98. The processing circuitry 98 may include a processor 100 and memory 102. In particular, in addition to or instead of a central processing unit-like processor and memory, the processing circuitry 98 may include integrated circuits for processing and / or control, e.g., one or more processors and / or processor cores adapted to execute instructions, and / or FPGAs (field programmable gate arrays), and / or ASICs (application-specific integrated circuits). The processing circuitry 100 may be configured to access (e.g., write to and / or read from) memory 102, which may include any type of volatile and / or non-volatile memory, such as cache, and / or buffer memory, and / or RAM (random access memory), and / or ROM (read-only memory), and / or optical memory, and / or EPROM (erasable programmable read-only memory).

[0063] As such, the core network node 15 further comprises software 104, for example, stored internally in the memory 102 or stored in an external memory (e.g., a database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 104 may include instructions executable by the processing circuitry 98. The processing circuitry 98 may be configured to control and / or cause any of the methods and / or processes described herein to be performed, for example, by the core network node 15. The processor 100 corresponds to one or more processors 100 for performing the functions of the core network node 15 described herein. The memory 102 is configured to store data, program software code, and / or other information described herein. In some embodiments, the software 104 may include instructions that, when executed by the processor 100 and / or the processing circuitry 98, cause the processor 100 and / or the processing circuitry 98 to perform the processes described herein in connection with the core network node 15. For example, the processing circuitry 98 of the core network node 15 may include a configuration unit 34 configured to perform one or more of the functions of the core network node 16 described herein, such as with respect to network functionality when the UE AMBR is unavailable.

[0064] In some embodiments, the internal operation of core network node 15, network node 16, WD 22, and host computer 24 may be as shown in FIG. 2, and independently, the surrounding network topology may be as shown in FIG.

[0065] 2, OTT connection 52 is depicted abstractly to illustrate communication between host computer 24 and wireless device 22 via network nodes 16, without explicit reference to intermediate devices and the exact routing of messages through those devices. The network infrastructure may determine the routing, which may be configured to be hidden from WD 22, the service provider operating host computer 24, or both. While OTT connection 52 is active, the network infrastructure may further decide to dynamically change the routing (e.g., based on network load balancing considerations or reconfiguration).

[0066] The wireless connection 64 between the WD 22 and the network node 16 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the WD 22 using the OTT connection 52, of which the wireless connection 64 may form the final segment. More precisely, the teachings of some of these embodiments may improve data rate, latency, and / or power consumption, thereby providing benefits such as reduced user latency, relaxed file size limitations, improved responsiveness, and extended battery life.

[0067] In some embodiments, measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors to improve one or more embodiments. Additionally, there may be optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and the WD 22 in response to fluctuations in the measurement results. The measurement procedures and / or network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24, the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be located in or associated with the communication devices through which the OTT connection 52 passes, and the sensors may participate in the measurement procedures by providing values ​​for the monitored quantities exemplified above or other physical quantities from which the software 48, 90 may calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 52 may include changes to message formats, retransmission settings, priority routing, etc., and the reconfiguration need not affect the network node 16, which may be unknown or imperceptible to the network node 16. Some of such procedures and functionality may be known and practiced in the art. In particular embodiments, the measurements may include proprietary WD signaling that facilitates the host computer 24 measuring throughput, propagation time, latency, etc. In some embodiments, the measurements may be implemented such that the software 48, 90 uses the OTT connection 52 to send messages, particularly empty or "dummy" messages, while monitoring propagation time, errors, etc.

[0068] Thus, in some embodiments, host computer 24 includes processing circuitry 42 configured to provide user data and communication interface 40 configured to transfer the user data to a cellular network for transmission to WD 22. In some embodiments, the cellular network also includes network node 16 with wireless interface 62. In some embodiments, network node 16 and / or processing circuitry 68 of network node 16 are configured to perform the functions and / or methods described herein to prepare / initiate / maintain / support / terminate transmissions to WD 22 and / or prepare / terminate / maintain / support / terminate reception of transmissions from WD 22.

[0069] In some embodiments, host computer 24 includes processing circuitry 42 and a communications interface 40 configured to receive user data resulting from transmissions from WD 22 to network node 16. In some embodiments, WD 22 includes a wireless interface 82 and / or processing circuitry 84 configured to and / or adapted to perform the functions and / or methods described herein to prepare / initiate / maintain / support / terminate transmissions to network node 16 and / or prepare / terminate / maintain / support / terminate reception of transmissions from network node 16.

[0070] 1 and 2 depict various "units," such as node unit 32 and configuration unit 34, as being within respective processors, it is contemplated that these units may be implemented such that portions of the units are stored in corresponding memories within the processing circuitry. In other words, the units may be implemented in hardware within the processing circuitry or in a combination of hardware and software.

[0071] 3 is a flowchart illustrating an exemplary method implemented in a communications system, such as the communications systems of FIGS. 1 and 2, according to one embodiment. The communications system may include a host computer 24, a network node 16, and a WD 22, as may be described with reference to FIG. 2. In a first step of the method, the host computer 24 provides user data (block S100). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as host application 50 (block S102). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (block S104). In an optional third step, the network node 16 transmits the user data carried in the host computer 24-initiated transmission to the WD 22 (block S106), in accordance with the teachings of embodiments described throughout this disclosure. In an optional fourth step, the WD 22 executes a client application, such as client application 92, associated with the host application 50 executed by the host computer 24 (block S108).

[0072] 4 is a flow chart illustrating an exemplary method implemented in a communications system, such as the communications system of FIG. 1, according to one embodiment. The communications system may include a host computer 24, a network node 16, and a WD 22, as may be described with reference to FIGS. 1 and 2. In a first step of the method, the host computer 24 provides user data (block S110). In an optional substep (not shown), the host computer 24 provides the user data by executing a host application, such as host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (block S112). In accordance with the teachings of embodiments described throughout this disclosure, the transmission may pass through the network node 16. In an optional third step, the WD 22 receives the user data carried in the transmission (block S114).

[0073] 5 is a flowchart illustrating an exemplary method implemented in a communications system, such as the communications system of FIG. 1, according to one embodiment. The communications system may include a host computer 24, a network node 16, and a WD 22, as may be described with reference to FIGS. 1 and 2. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (block S116). In an optional sub-step of the first step, the WD 22 executes a client application 92, which provides user data in response to the received input data provided by the host computer 24 (block S118). Additionally or alternatively, in an optional second step, the WD 22 provides the user data (block S120). In an optional sub-step of the second step, the WD provides the user data by executing a client application, such as the client application 92 (block S122). In providing the user data, the executed client application 92 may further take into account user input received from a user. Regardless of the particular manner in which the user data was provided, in an optional third substep, WD 22 may begin transmitting the user data to host computer 24 (block S124). In a fourth step of the method, host computer 24 receives the transmitted user data from WD 22 (block S126) in accordance with the teachings of the embodiments described throughout this disclosure.

[0074] 6 is a flow chart illustrating an exemplary method implemented in a communications system, such as the communications system of FIG. 1, according to one embodiment. The communications system may include a host computer 24, a network node 16, and a WD 22, as may be described with reference to FIGS. 1 and 2. In an optional first step of the method, the network node 16 receives user data from the WD 22 (block S128), in accordance with the teachings of embodiments described throughout this disclosure. In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (block S130). In a third step, the host computer 24 receives the user data carried in transmissions initiated by the network node 16 (block S132).

[0075] 7 is a flowchart of an example process in network node 16, according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16, such as by one or more of processing circuitry 68 (including node unit 32), processor 70, radio interface 62, and / or communication interface 60. Network node 16 is configured to perform one of emergency service setup and handover procedures for wireless device 22 (block S134) without receiving a UE aggregate maximum bit rate (AMBR) parameter associated with wireless device 22 from a network entity (e.g., core network node 15) as described herein.

[0076] According to one or more embodiments, processing circuitry 68 is configured to refrain from examining the UE AMBR for quality of service (QoS) flows associated with one of an emergency service setup and handover procedure.

[0077] According to one or more embodiments, the processing circuitry 68 is further configured to determine a UE AMBR from a packet data network (PDU) session AMBR, and one of an emergency service setup and handover procedure is performed based on the PDU session AMBR.

[0078] According to one or more embodiments, the processing circuitry 68 is further configured to cause transmission of the determined UE AMBR to an Access and Mobility Management Function (AMF) node in a Next Generation Application Protocol (NGAP) message.

[0079] According to one or more embodiments, the network entity is one of a Unified Data Manager (UDM) node and a Policy Control Function (PCF) node.

[0080] According to one or more embodiments, the network node 16 is configured to use the locally configured UE AMBR to perform one of emergency service setup and handover procedures for the wireless device 22.

[0081] In one or more embodiments, the AMF provides the UE AMBR to the NG-RAN node. The AMF may receive the UE AMBR from the UDM or PCF, but if the AMF does not receive the UE AMBR from the UDM / PCF for one or more reasons, one of the solutions described herein describes an AMF with a locally configured UE AMBR that can be used for emergency services and provided to the NG-RAN.

[0082] Other alternatives (if AMF does not provide UE ABMR at all): NG-RAN may refrain from checking the UE AMBR if it is not provided. The NG-RAN has a locally configured UE AMBR for emergency services, and the NG-RAN uses this locally configured UE AMBR. The NG-RAN infers the UE AMBR from the PDU session AMBR. In this case, the NG-RAN may need to send the inferred UE AMBR parameter back to the AMF in an NGAP message (e.g., HO Required).

[0083] 8 is a flowchart of an example process in the core network node 15, according to some embodiments of the present disclosure. One or more blocks described herein may be executed by one or more elements of the core network node 15, such as by one or more of the processing circuitry 98 (including the configuration unit 34), the processor 100, and / or the communication interface 96. The core network node 15 is configured to store a preconfigured UE aggregate maximum bit rate (AMBR) parameter (block S136), as described herein. The core network node 15 is configured to use the preconfigured UE AMBR for emergency service setup if the radio AMBR is not available from the network entity (block S138), as described herein.

[0084] According to one or more embodiments, the network entity is one of a Unified Data Manager (UDM) node and a Policy Control Function (PCF) node.

[0085] According to one or more embodiments, the core network node 15 is an Access and Mobility Management Function (AMF).

[0086] According to one or more embodiments, the processing circuitry 98 is further configured to transfer the preconfigured UE AMBR to another core network node during a handover between core network nodes.

[0087] According to one or more embodiments, the pre-configured UE AMBR is one of a pre-configured UE AMBR or a UE AMBR configured locally at the network node 16 .

[0088] 9 is a flowchart of another example process in the core network node 15, according to some embodiments of the present disclosure. One or more blocks described herein may be executed by one or more elements of the core network node 15, such as by one or more of the processing circuitry 98 (including the configuration unit 34), the processor 100, and / or the communication interface 96. The core network node 15 is configured to store (block S140) a local UE aggregate maximum bit rate (AMBR) parameter that applies to any user equipment (UE) (22) requesting emergency services, as described herein. After storing the local UE AMBR parameter, the core network node 15 is configured to receive (block S142) a request for emergency services from the first UE 22 via the access network node 16, as described herein. The core network node 15 is configured to send (block S144) a message to the access network node 16 including the local UE AMBR parameter for emergency service configuration for the first UE 22, as described herein.

[0089] According to one or more embodiments, the core network node 15 is further configured to determine that the core network node 15 does not have subscription data stored for the first UE 22, and the sending of the message including the local UE AMBR parameter is based on the determination.

[0090] According to one or more embodiments, the sending of the message including the local UE AMBR parameter is based on the UE AMBR parameter not being obtained from a network entity.

[0091] According to one or more embodiments, the network entity is a Unified Data Manager (UDM) node.

[0092] According to one or more embodiments, the network entity is a Policy Control Function (PCF) node.

[0093] According to one or more embodiments, the core network node 15 is an Access and Mobility Management Function (AMF).

[0094] According to one or more embodiments, the emergency service corresponds to an Internet Protocol Multimedia Subsystem (IMS) emergency session.

[0095] According to one or more embodiments, the core network node 15 is further configured, after storing the local UE AMBR parameters, to receive a request for emergency services from the second UE 22 via the access network node 16, and to send a message to the access network node 16 including the local UE AMBR parameters for emergency service configuration for the second UE 22.

[0096] According to one or more embodiments, the local UE AMBR parameter is stored as part of the emergency configuration data that applies to emergency services.

[0097] According to one or more embodiments, if the core network node 15 is an AMF, the core network node 15 provides access to emergency services.

[0098] Having described the general process flow for configuring the present disclosure and provided example hardware and software configurations for implementing the processes and functions of the present disclosure, the following sections provide details and examples for configuring network functions when UE Aggregate Maximum Bit Rate (AMBR) is not available.

[0099] Some embodiments provide network functionality when the UE AMBR is unavailable. In one or more embodiments, the functionality of the core network node 15 (e.g., AMF) is performed by one or more of the processing circuitry 98, the processor 100, the configuration unit 34, etc. In one or more embodiments, the functionality of the network node 16 (e.g., the NG-RAN node) may be performed by one or more of the processing circuitry 68, the processor 70, the node unit 32, etc.

[0100] The embodiments described herein relate to establishing emergency services even when a UE AMBR (eg, a wireless device AMBR) is unavailable at the UDM or PCF.

[0101] Example of an embodiment in a core network node 15 (e.g., AMF)

[0102] In one embodiment, the AMF includes the UE AMBR in the emergency configuration based on operator decision / configuration if the UE AMBR is not available from the UDM / PCF (e.g., network entity or other core network node 15).

[0103] In another embodiment, the AMF may always include the UE AMBR from the UDM, PCF, or based on local configuration.

[0104] In yet another embodiment, the AMF includes the UE AMBR (either configured or received from the RAN) and forwards it to another AMF during inter-AMF handover as a result of emergency fallback.

[0105] Example of an implementation in an NG-RAN node (e.g., network node 16) In one embodiment:

[0106] If QoS of 5QI==5 "IMS signaling" and 5QI==1 "conversational voice" is configured from the emergency service, the NG-RAN node shall not fail the procedure (e.g., execute the procedure) even if the UE AMBR is not offered, not received, or is unknown. The emergency service shall be able to configure or execute emergency service fallback accordingly. An example is shown in Table 1 below, which is a modified version of Chapter 9.2.3.1 of 3GPP® Technical Specification (TS) 38.413, modified to allow emergency services even if the UE AMBR is not provided during the PDU session resource configuration procedure. The changes are in bold.

[0107] In particular, 3GPP TS38.413, Chapter 8.2.1.2 - Successful Operation of PDU Session Resource Setup Procedure states:

[0108] If the AMF has not previously sent a UE aggregated max bitrate information element (IE), it must be sent to the NG-RAN node. If it is included in the PDU SESSION RESOURCE SETUP REQUEST message, the NG-RAN node stores the UE aggregated max bitrate in the wireless device context and uses the received UE aggregated max bitrate for all non-GBR QoS flows of the wireless device as specified in 3GPP TS 23.501.

[0109] For emergency services, if the UE aggregated maximum bit rate is not sent or received early, the NG-RAN node skips applying the UE aggregated maximum bit rate to all non-GBR QoS flows of the corresponding wireless device 22.

[0110] [Table 1]

[0111] In another embodiment, if an emergency service is configured in 5G without the UE AMBR being provided by the AMF, the UE AMBR limit is not checked, for example, by the network node 16. The emergency service is configured with all requested QoS fulfilled, see Table 1.

[0112] In yet another embodiment, the NG-RAN node will "configure" the UE AMBR parameter, which is configured to be "large enough" to facilitate emergency services, as described herein.

[0113] In yet another embodiment, the NG-RAN node may use the PDU session level AMBR parameter as the UE AMBR parameter, either by local configuration or calculation.

[0114] In yet another embodiment, when emergency fallback is performed, if the UE AMBR is not provided by the AMF, the NG-RAN node may include a "configured UE AMBR." The "configured UE AMBR" could be configured in OAM or calculated by the NG-RAN node, for example, UE AMBR = SUM(PDU session AMBR). The configured UE AMBR is sent from the source NG-RAN node to the AMF. The AMF uses it and sends it to the target NG-RAN node. See Table 2 (NG-RAN includes "NG-RAN UE AMBR" (based on configuration or calculation) in the AMF during handover preparation).

[0115] [Table 2]

[0116] In yet another embodiment, during intra-system handover for emergency fallback, the target NG-RAN node continues the emergency service handover without receiving a UE AMBR from the AMF, similar to the emergency service setup procedure described above (no UE AMBR restriction check, use of locally configured UE AMBR, or use of PDU session AMBR as UE AMBR).

[0117] In yet another embodiment, the handover request message is updated such that the presence of the UE AMBR is changed from "mandatory" to "optional." See Table 3, a modified table from 3GPP TS38.413, chapter 9.2.3.4 (Direction: AMF -> NG-RAN node). The modifications to Table 3 are shown in bold and strikethrough, where "M" is mandatory and "O" is optional.

[0118] [Table 3]

[0119] In yet another embodiment, the split NG-RAN architecture specifies that the gNB-CU (e.g., network node CU) may configure the UE AMBR (if it does not receive it) and send it to the gNB-DU (e.g., network node DU) during context setup. A similar approach may also be used for the Xn and E1 interfaces.

[0120] Instead, the absence of the UE AMBR is tolerated during emergency service setup or handover procedures, which may lead to a change in XnAP, F1AP, and / or E1AP, and similar to Table 3, the presence of the UE AMBR IE changes from mandatory to optional.

[0121] One or more embodiments described herein may be included in one or more of the following 3GPP® standards: 3GPP® TS38.413, 3GPP® TS23.501, 3GPP® TS38.473, 3GPP® TS38.423, and 3GPP® TS37.473.

[0122] Accordingly, one or more embodiments described herein provide for the configuration of emergency services even when a UE AMBR is unavailable (e.g., the configuration of emergency services regardless of the availability of a UE AMBR).

[0123] Some examples:

[0124] Examples of core network nodes 15 (e.g., AMF): The AMF may include the UE AMBR in emergency configuration based on the network operator's decision, such as when the UE AMBR is not available from the UDM / PCF. In another approach, the AMF always includes the UE AMBR obtained from the UDM, PCF, or based on local configuration. · If the UE AMBR is not available, the AMF uses the configured UE AMBR or the NG-RAN node (e.g., network node 16) uses its locally configured UE AMBR (e.g., received from the NG-RAN node) and transfers the UE AMBR to another AMF during inter-AMF handover.

[0125] Example of an NG-RAN node (e.g., network node 16) NG-RAN nodes will not fail emergency service setup or handover procedures if the UE AMBR is not presented. In the above cases, the UE AMBR check for the QoS flow may not be performed. Instead, it is specified that the NG-RAN node uses the locally configured UE AMBR. Alternatively, the NG-RAN node can use the PDU session AMBR as the UE AMBR. In the above options, if the NG-RAN node creates the UE AMBR, the RAN can provide the UE AMBR to the AMF in the NGAP Response or Handover Required message. The AMF stores the value in the WD context and transfers the value between AMFs during mobility, thereby supporting emergency fallback through handover. In a split NG-RAN node architecture, the gNB-CU may configure the UE AMBR (if it does not receive it) and send it to the gNB-DU during context setup. A similar approach may also be used for the Xn and E1 interfaces. Alternatively, in emergency service setup or handover procedures, the absence of the UE AMBR is tolerated, e.g., predefined as allowed in the specification.

[0126] One advantage provided by the teachings of the present disclosure is that emergency services (e.g., emergency services via a wireless device) may be configured or provided in accordance with regulations even when the UE AMBR is unavailable.

[0127] According to one or more embodiments, to support emergency registration for UEs that do not have subscription data in the AMF (e.g., unauthenticated UEs or failure to read subscription data from the UDM), the AMF / SMF uses local emergency configuration data to configure the UE context and PDU session resources on the RAN side. The UE-AMBR is part of the UE context required on the RAN side. The AMF emergency configuration data may include the UE-AMBR; otherwise, emergency resource configuration may fail. For example, the UE-AMBR may be required when a non-GBR QoS flow is configured. If the UE cannot register with the network or does not have a UICC and therefore does not have a UDM record, the UE should be allowed to configure emergency services by law, but does not have a UE AMBR. In the case of 5QI 5 "IMS signaling," non-GBR services will be configured and the NG-RAN node will fail the procedure. The network should provide support for emergency services in this situation. Therefore, one or more embodiments described herein provide that if the UE AMBR is not provided, the NG-RAN node will allow emergency services and checking of the UE AMBR will be skipped. The mandatory presence of the UE AMBR in the handover request is changed to optional.

[0128] In other words, if the AMF has not previously sent the UE aggregated max bit rate IE, it needs to be sent to the NG-RAN node. If the PDU SESSION RESOURCE SETUP REQUEST message includes the UE aggregated max bit rate IE, the NG-RAN node stores it in the UE context and uses the received UE aggregated max bit rate for all non-GBR QoS flows of the corresponding UE. In the case of emergency services, if the UE aggregated max bit rate is not sent or received early, the NG-RAN node skips applying the UE aggregated max bit rate to all non-GBR QoS flows of the corresponding UE.

[0129] According to one or more embodiments, to provide emergency services, the AMF is configured with emergency configuration data that applies to emergency services established by the AMF based on a request from a UE. The AMF emergency configuration data includes an S-NSSAI and an emergency DNN used to derive the SMF. Furthermore, the AMF emergency configuration data may include a statically configured SMF for the emergency DNN. The SMF may also store emergency configuration data including statically configured UPF information for the emergency DNN. The AMF emergency configuration data may also include a UE-AMBR.

[0130] According to one or more embodiments, upon receiving the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node is configured as follows: -attempts to perform the requested PDU session configuration; - storing the received UE aggregated maximum bit rate in the UE context and using the received UE aggregated maximum bit rate for the non-GBR QoS flows of the corresponding UE as specified in 3GPP TS23.501. In the case of emergency services, if the UE aggregated maximum bit rate is not sent or received and is not received early, the NG-RAN node shall skip applying the UE aggregated maximum bit rate to all non-GBR QoS flows of the corresponding UE; - storing the received mobility restriction list in the UE context; and / or - Store the received UE radio capabilities in the UE context.

[0131] According to one or more embodiments, upon receiving the HANDOVER REQUEST message, the target NG-RAN node is configured as follows: - Attempt to perform the requested PDU session configuration and associated security; - storing the received UE aggregated max bit rate in the UE context and using the received UE aggregated max bit rate for all non-GBR QoS flows of the corresponding UE as specified in 3GPP TS23.501. In case of emergency services, if the UE aggregated max bit rate is not sent / received and is not received early, the NG-RAN node shall skip applying the UE aggregated max bit rate to all non-GBR QoS flows of the corresponding UE; - storing the received mobility restriction list in the UE context; and / or - Store the received UE security capabilities in the UE context.

[0132] Some additional examples

[0133] Example A1. A network node 16, A network node configured to, and / or including a radio interface 62 configured to, and / or including processing circuitry 68 configured to, perform one of emergency service setup and handover procedures for a wireless device 22 without receiving a user equipment (UE) aggregate maximum bit rate (AMBR) parameter associated with the wireless device 22 from a network entity.

[0134] Example A2. The network node 16 of Example A1, wherein the processing circuitry 68 is configured to refrain from examining the UE AMBR for quality of service (QoS) flows associated with one of an emergency service setup and handover procedure.

[0135] Example A3. The network node 16 of Example A1, wherein the processing circuitry 68 is further configured to determine a UE AMBR from a packet data network (PDU) session AMBR, and wherein one of an emergency service setup and handover procedure is performed based on the PDU session AMBR.

[0136] Example A4. The network node 16 of Example A3, wherein the processing circuitry 68 is further configured to cause transmission of the determined UE AMBR to an Access and Mobility Management Function (AMF) node in a Next Generation Application Protocol (NGAP) message.

[0137] Example A5. The network node 16 of Example A1, wherein the network entity is one of a Unified Data Manager (UDM) node and a Policy Control Function (PCF) node.

[0138] Example A6. The network node 16 of Example A1, wherein the network node 16 is configured to use a locally configured UE AMBR to perform one of an emergency service setup and handover procedure for the wireless device 22.

[0139] Example B1. A method performed at a network node 16, comprising: A method comprising performing one of an emergency service setup and handover procedure for a wireless device 22 without receiving a user equipment (UE) aggregate maximum bit rate (AMBR) parameter associated with the wireless device 22 from a network entity.

[0140] Example B2. The method of example B1, further comprising refraining from examining the UE AMBR for Quality of Service (QoS) flows associated with one of an emergency service setup and handover procedure.

[0141] Example B3. The method of Example B1, further comprising determining the UE AMBR from a packet data network (PDU) session AMBR; A method in which one of the emergency service setup and handover procedures is performed based on the PDU session AMBR.

[0142] Example B4. The method of Example B1, further comprising causing transmission of the determined UE AMBR to an Access and Mobility Management Function (AMF) node in a Next Generation Application Protocol (NGAP) message.

[0143] Example B5. The method of example B1, wherein the network entity is one of a Unified Data Manager (UDM) node and a Policy Control Function (PCF) node.

[0144] Example B6. The method of Example B1, wherein the network node 16 is configured to use the locally configured UE AMBR to perform one of an emergency service setup and handover procedure for the wireless device 22.

[0145] Example C1. A core network node 15, storing preconfigured user equipment (UE) aggregate maximum bit rate (AMBR) parameters; If the UE AMBR is not obtained from the network entity, a pre-configured UE AMBR is used for emergency service setup.

[0146] Example C2. The core network node 15 of Example C1, wherein the network entity is one of a Unified Data Manager (UDM) node and a Policy Control Function (PCF) node.

[0147] Example C3. The core network node 15 of Example C1, wherein the core network node 15 is an Access and Mobility Management Function (AMF).

[0148] Example C4. The core network node 15 of Example C1, wherein the processing circuitry 98 is further configured to transfer the preconfigured UE AMBR to another core network node 15 during an inter-core network node handover.

[0149] Example C5. The core network node 15 of Example C4, wherein the preconfigured UE AMBR is one of a preconfigured UE AMBR or a UE AMBR configured locally at the network node 16.

[0150] Example D1. A method performed in a core network node 15, comprising: storing preconfigured user equipment (UE) aggregate maximum bit rate (AMBR) parameters; If the UE AMBR is not available from the network entity, using a pre-configured UE AMBR for emergency service configuration; A method comprising:

[0151] Example D2. The method of example D1, wherein the network entity is one of a Unified Data Manager (UDM) node and a Policy Control Function (PCF) node.

[0152] Example D3. The method of Example D1, wherein the core network node 15 is an Access and Mobility Management Function (AMF).

[0153] Example D4. The method of Example D1, further comprising transferring the preconfigured UE AMBR to another core network node 15 during an inter-core network node handover.

[0154] Example D5. The method of example D4, wherein the preconfigured UE AMBR is one of a preconfigured UE AMBR or a UE AMBR configured locally at the network node 16.

[0155] As will be appreciated by those skilled in the art, the concepts described herein may be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Accordingly, the concepts described herein may take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects, all generally referred to herein as "circuits" or "modules." Any process, step, action, and / or function described herein may be performed by and / or associated with a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the present disclosure may take the form of a computer program product on a tangible computer-usable storage medium having computer program code embodied therein, which may be executed by a computer. Any suitable tangible computer-readable medium may be utilized, including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0156] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer (thereby creating a special-purpose computer), a special-purpose computer, or other programmable data processing apparatus to create a machine, where the instructions, executed by the processor of the computer or other programmable data processing apparatus, create means for performing the functions / acts identified in the flowchart illustrations and / or block diagrams.

[0157] These computer program instructions may also be stored in a computer-readable memory or readable medium and may direct a computer or other programmable data processing apparatus to function in a particular manner, and the instructions stored in the computer-readable memory may produce an article of manufacture including instruction means that implement the functions / acts identified in the flowcharts and / or block diagrams.

[0158] Also, computer program instructions may be loaded into a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to create a computer-implemented process, the instructions executed by the computer or other programmable apparatus providing the steps for implementing the functions / operations identified in the flowcharts and / or block diagrams.

[0159] It should be understood that the functions / acts noted in the blocks may occur in a different order than that shown in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may be executed in the reverse order, depending on the functionality / acts involved. While some of the figures include arrows on communication paths to indicate the primary direction of communication, it should be understood that communication may occur in the opposite direction to that of the depicted arrow.

[0160] Computer program code for carrying out operations of the concepts described herein can be written in an object-oriented programming language such as Python, Java, or C++. However, computer program code for carrying out operations of the present disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code can execute entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer. In the latter scenario, the remote computer can be connected to the user's computer via a local area network (LAN) or wide area network (WAN), or connection can be made to an external computer (e.g., via the Internet through use of an Internet Service Provider).

[0161] Many different embodiments are disclosed herein in connection with the above description and drawings. It is understood that literally describing and illustrating every combination and subcombination of these embodiments would be overly repetitive and confusing. Accordingly, all embodiments can be combined in any manner and / or combination, and the specification, including the drawings, should be construed as constituting a complete written description of all combinations and subcombinations of the embodiments described herein, and the methods and processes for making and using them, and is intended to support claims to such combinations or subcombinations.

[0162] Abbreviations that may be used in the above description include the following: Abbreviation Description CN Core Network AMF Access and Mobility Management Functions CP Control Plane CU Central Unit CU-CP Central Unit Control Plane CU-UP Central Unit User Plane UE AMBR UE aggregate maximum bit rate

[0163] It will be understood by those skilled in the art that the embodiments described herein are not limited to those particularly shown and described hereinabove. Furthermore, unless otherwise noted above, it should be noted that all of the accompanying drawings are not to scale. Various modifications and variations are possible in light of the above teachings without departing from the scope of the appended claims.

Claims

1. A core network node (15), storing a local UE aggregate maximum bit rate (AMBR) parameter to be applied to any user equipment (UE) (22) requesting emergency services; receiving a request for emergency services from a first UE (22) via an access network node (16) after storing said local UE AMBR parameters; sending a message including the local UE AMBR parameters for emergency service setup for the first UE (22) towards the access network node (16); A core network node comprising: a processing circuit (98) configured to:

2. A core network node (15) according to claim 1, The processing circuitry (98) is further configured to determine that the core network node (15) does not have subscription data stored for the first UE (22), and the transmission of the message including the local UE AMBR parameter is based on the determination.

3. A core network node (15) according to claim 1 or 2, The core network node, wherein the sending of the message including the local UE AMBR parameter is based on the UE AMBR parameter not being obtained from a network entity.

4. A core network node (15) according to claim 3, The network entity is a Unified Data Manager (UDM) node, a core network node.

5. 4. A core network node (15) according to claim 3, wherein the network entity is a Policy Control Function (PCF) node.

6. A core network node (15) according to any one of claims 1 to 5, The core network node (15) is an Access and Mobility Management Function (AMF).

7. A core network node (15) according to any one of claims 1 to 6, The emergency service corresponds to an Internet Protocol Multimedia Subsystem (IMS) emergency session.

8. A core network node (15) according to any one of claims 1 to 7, The processing circuit (98) further comprises: receiving a request for emergency services from a second UE (22) via said access network node (16) after storing said local UE AMBR parameters; sending a message including the local UE AMBR parameters for emergency service setup for the second UE (22) towards the access network node (16); a core network node configured to:

9. A core network node (15) according to any one of claims 1 to 8, The local UE AMBR parameter is stored as part of emergency configuration data applied to emergency services in a core network node.

10. A method performed in a core network node (15), comprising: storing a local UE aggregate maximum bit rate (AMBR) parameter that applies to any user equipment (UE) requesting emergency services; receiving a request for emergency services from a first UE via an access network node after storing the local UE AMBR parameter; sending a message to the access network node including the local UE AMBR parameters for emergency service configuration for the first UE; A method comprising:

11. 11. The method of claim 10, further comprising:

11. The method of claim 10, further comprising: determining that the core network node does not have subscription data stored for the first UE; and wherein the sending of the message including the local UE AMBR parameter is based on the determining.

12. 12. The method of claim 10 or 11, 10. The method of claim 9, wherein the sending of the message including the local UE AMBR parameters is based on UE AMBR parameters not being obtained from a network entity.

13. 13. The method of claim 12, The method, wherein the network entity is a Unified Data Manager (UDM) node.

14. 13. The method of claim 12, The method, wherein the network entity is a Policy Control Function (PCF) node.

15. 15. The method of any one of claims 10 to 14, The method, wherein the core network node is an Access and Mobility Management Function (AMF).

16. 16. The method of any one of claims 10 to 15, The method, wherein the emergency service corresponds to an Internet Protocol Multimedia Subsystem (IMS) emergency session.

17. 17. The method of any one of claims 10 to 16, further comprising: After storing the local UE AMBR parameter, receiving a request for emergency services from a second UE via the access network node.

18. 18. The method of claim 17, further comprising: sending a message to the access network node including the local UE AMBR parameters for emergency service setup for the second UE.

19. 19. The method of any one of claims 10 to 18, The local UE AMBR parameter is stored as part of emergency configuration data applied to emergency services.

20. A computer readable medium having stored thereon program instructions which, when executed on a processor, configure the processor to perform the method of any one of claims 10 to 19.

Images