User Equipment (UE) Aggregated Maximum Bitrate (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] This disclosure relates to wireless communication, and in particular to network functions when the aggregated maximum bitrate (AMBR) of a wireless device (e.g., UE) is unavailable.

Background Art

[0002] The 3rd Generation Partnership Project (3GPP (registered trademark)) has developed and is developing standard specifications for 4th Generation (4G) (also referred to as Long Term Evolution (LTE)) and 5th 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), and communication between network nodes and between WDs. 3GPP (registered trademark) is also developing standard specifications for 6th Generation (6G) wireless communication networks.

[0003] In particular, in 5G, the aggregated maximum bitrate (AMBR) of a wireless device (e.g., user equipment (UE) AMBR) limits the aggregated bitrate that can be expected to be provided across all non-guaranteed bitrate (non-GBR) quality of service (QoS) flows of the wireless device (e.g., UE). Each (R)AN sets the sum of the session AMBRs of all PDU sessions of the active user plane to the (R)AN to the UE AMBR up to the value of the UE AMBR received from the access and mobility function (AMF) at most. 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.) during either the initial radio device context configuration procedure or the PDU session resource configuration procedure. If non-GBR QoS is configured, the transmission of the UE AMBR to the NG-RAN node is mandatory according to the 3GPP® specification.

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

[0006] An unauthenticated wireless device may be one that does not have a Universal Subscriber Identification Module (USIM), or one that has a USIM but failed to authenticate. Another scenario is that 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] If an emergency service is configured, it may be based on the DNN (e.g., data network name) configured in the service network for the emergency service, 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 the 3GPP® standard, in certain cases AMF may not be able to provide UE AMBR, but because NG-RAN nodes require UE AMBR for non-GBR IMS signaling, emergency services cannot be configured on NG-RAN nodes.

[0009] Therefore, 3GPP® does not define procedures to support emergency service configuration when the UE AMBR cannot be obtained by the AMF during the emergency service configuration procedure and cannot be transmitted from the AMF to the NG-RAN node. [Overview of the project] [Problems that the invention aims to solve]

[0010] Several embodiments advantageously provide methods, systems, and apparatus for network functions when the UE aggregated maximum bitrate (AMBR) is unavailable.

[0011] One or more embodiments provide both core network (CN)-based and radio access network (RAN)-based solutions for setting up emergency services in cases where there is no UE AMBR available from the UDM or PCF (e.g., the radio device is not authenticated, or the radio device is authenticated without a UE AMBR), or the radio device is authenticated (via AUSF) but the AMF fails to obtain radio device subscription data from the UDM, or the radio device does not have a subscription (no UICC) and therefore cannot utilize a UE AMBR 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 includes processing circuitry configured to store a local UE aggregated maximum bitrate (AMBR) parameter applicable to any user equipment (UE) requesting emergency service; to receive an emergency service request from a first UE via an access network node after storing the local UE AMBR parameter; and to cause the access network node to send a message containing the local UE AMBR parameter for setting up emergency service for the first UE.

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

[0014] According to one or more embodiments of this model, the transmission of a message containing local UE AMBR parameters is based on the fact that the UE AMBR parameters have not been obtained from the network entity.

[0015] According to one or more embodiments of this model, the network entity is an integrated data manager (UDM) node.

[0016] According to one or more embodiments of this model, the network entity is a policy control function (PCF) node.

[0017] According to one or more embodiments of this model, the core network node is an access and mobility management function (AMF).

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

[0019] According to one or more embodiments of this model, the processing circuit is further configured to store local UE AMBR parameters, receive an emergency service request from a second UE via an access network node, and send a message containing local UE AMBR parameters for emergency service setup for the second UE to the access network node.

[0020] According to one or more embodiments of this model, local UE AMBR parameters are stored as part of emergency configuration data applied to emergency services.

[0021] According to another aspect of the present disclosure, a method executed by a core network node is provided. The method includes storing local UE aggregated maximum bitrate (AMBR) parameters applicable to any user equipment (UE) requesting an emergency service, and after storing the local UE AMBR parameters, receiving a request for an emergency service from a first UE via an access network node, and transmitting a message including the local UE AMBR parameters for the emergency service configuration for the first UE to the access network node.

[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 the transmission of the message including the local UE AMBR parameters is based on the determination.

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

[0024] According to one or more embodiments of this aspect, the network entity is an integrated 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 receiving a request for an emergency service from a second UE via an access network node after storing local UE AMBR parameters.

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

[0030] According to one or more embodiments of this aspect, the local UE AMBR parameters are stored as part of emergency configuration data applied to the emergency service.

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

[0032] A more complete understanding of this embodiment and its attendant advantages and features will be more readily understood by reference to the following detailed description, considered in conjunction with the accompanying drawings.

Brief Description of the Drawings

[0033] [Figure 1] A schematic diagram of an exemplary network architecture showing a communication system connected to a host computer via an intermediate network according to the principles of the present disclosure. [Figure 2] A block diagram of a host computer communicating with a wireless device via a network node by at least a partial wireless connection according to some embodiments of the present disclosure. [Figure 3] A flowchart showing an exemplary method executed 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]A flowchart illustrating exemplary methods performed in a communication system including a host computer, a network node, and a wireless device for receiving user data on a wireless device, according to some embodiments of the present disclosure. [Figure 5] A flowchart illustrating exemplary methods performed in a communication system including a host computer, a network node, and a wireless device for a host computer to receive user data from a wireless device, according to some embodiments of the present disclosure. [Figure 6] A flowchart illustrating exemplary methods performed in a communication system including a host computer, network nodes, and wireless devices for receiving user data on a host computer, according to some embodiments of the present disclosure. [Figure 7] A flowchart illustrating an exemplary process in a network node according to several embodiments of the present disclosure. [Figure 8] A flowchart illustrating an exemplary process in a core network node according to several embodiments of the present disclosure. [Figure 9] A flowchart of another exemplary process in a core network node according to several embodiments of the present disclosure. [Modes for carrying out the invention]

[0034] Before describing the details of exemplary embodiments, it should be noted that the embodiments primarily concern combinations of device components and processing steps related to network functionality when UE AMBR is unavailable, not received, and / or not inspected. Therefore, components are described by conventional symbols in the drawings only to the extent relevant to understanding the embodiments, and not to obscure the disclosure with details that would be readily apparent to those skilled in the art who benefit from this disclosure. Throughout this description, similar reference numerals indicate similar components.

[0035] When used herein, relative terms such as “first,” “second,” “upper,” and “lower” may be used solely to distinguish one entity or element from another, without implying or requiring any physical or logical relationship or order between such entities or elements. The terms used herein are intended solely to describe specific embodiments and are not intended to limit the concepts described herein. When used herein, the singular form is intended to include the plural form as well, unless the context clearly indicates otherwise. When used herein, the terms “include,” “equip,” and / or “have” identify the presence of a described feature, integer, step, action, element, and / or component, but do not exclude the presence or addition of one or more other features, integers, steps, actions, elements, components, and / or groups thereof.

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

[0037] In some embodiments described herein, the terms “connection” and “bonding,” etc., may be used here to indicate a connection, and do not necessarily have to be direct, and may include wired and / or wireless connections.

[0038] As used herein, the term “network node” can refer to any type of network node included in a wireless network, which may further include any of the following: base stations (BS), radio base stations, base transceiver stations (BTS), base station controllers (BSC), radio network controllers (RNC), g-node B (gNB), advanced node B (eNB or eNodeB), node B, multi-standard radio (MSR) radio nodes such as MSR BS, multi-cell / multicast coordination entities (MCE), integrated access and backhaul (IAB) nodes, relay nodes, donor nodes that control relays, radio access points (AP), transmit points, transmit nodes, remote radio units (RRU), remote radio heads (RRH), self-organizing network (SON) nodes, coordination nodes, positioning nodes, MDT nodes, etc., external nodes (e.g., third-party nodes, nodes outside the current network), nodes of a distributed antenna system (DAS), spectrum access system (SAS) nodes, element management systems (EMS), etc. Network nodes 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)" and "user equipment (UE)" are used interchangeably. A WD as used herein can 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 wireless communication devices, target devices, device-to-device (D2D) WDs, machine-type WDs, or machine-to-machine (M2M) capable WDs, low-cost and / or low-complexity WDs, sensors having a WD, tablets, mobile terminals, smartphones, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, customer premises equipment (CPEs), IoT (Internet of Things) devices, or narrowband IoT (NB-IoT) devices, etc.

[0040] Furthermore, in some embodiments, the general term “wireless network node” is used. It can be any type of wireless network node, which may include any of the following: base station, wireless base station, base station transceiver station, base station controller, network controller, RNC, advanced node B (eNB), node B, gNB, multicell / multicast coordinating entity (MCE), IAB node, relay node, access point, wireless access point, remote radio unit (RRU), or remote radio head (RRH).

[0041] For example, while terminology from a specific wireless system such as 3GPP® LTE and / or NEW Radio (NR) may be used in this disclosure, it should be noted that this should not be considered to limit the scope of this disclosure to the aforementioned system only. Other wireless systems, including but not limited to Broadband Code Division Multiple Access (WCDMA®), WiMAX (Worldwide Interoperability for Microwave Access), Ultra Mobile Broadband (UMB), and GSM (Global System for Mobile Communications), may also benefit from leveraging the ideas covered in this disclosure.

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

[0043] In some embodiments, a general descriptive element 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 a combination thereof.

[0044] Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as those generally understood by those skilled in the art to which this disclosure belongs. Terms used herein should be construed to have meanings consistent with their meanings in the context of this specification and related art, and it will be further understood that they should not be construed in an ideal or overly formal sense unless explicitly defined herein.

[0045] Some embodiments relate to network functionality when UE aggregated maximum bitrate (AMBR) is unavailable.

[0046] Next, referring to drawings in which similar elements are referenced by the same reference number, Figure 1 shows a schematic diagram of a communication system 10 according to one embodiment, such as a 3GPP® type cellular network capable of supporting standards such as LTE and / or NR (5G), comprising an access network 12 such as a wireless 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 AMF, UDM, PCF, etc. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NB, eNB, gNB, 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 can be connected 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 to a corresponding network node 16a. A second WD 22b in coverage area 18b can wirelessly connect to a corresponding network node 16b. Although multiple WDs 22a, 22b (collectively referred to as wireless device 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 is connected 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 more WDs 22 and network nodes 16.

[0047] Furthermore, it is understood that the WD22 may be configured to communicate simultaneously with and / or individually with two or more network nodes 16 and two or more types of network nodes 16. For example, the WD22 may have dual connectivity with a network node 16 that supports LTE and the same or different network nodes 16 that support NR. As an example, the WD22 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 implementation server, distributed server hardware and / or software, or as a processing resource in a server farm. The host computer 24 may be owned or under the control of a service provider, or may be operated by or on behalf of a service provider. The connections 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 via an optional intermediate network 30. The intermediate network 30 may be a public, private, or hosted network, or a combination of two or more of these. The intermediate network 30 may be a backbone network or the internet, if any. In some embodiments, the intermediate network 30 may include two or more subnets (not shown).

[0049] The communication system in Figure 1, as a whole, enables a connection between one of the connected WD22a, 22b and the host computer 24. The connection can be described as an over-the-top (OTT) connection. The host computer 24 and the connected WD22a, 22b are configured to communicate data and / or signaling over the OTT connection using the access network 12, the core network 14, an optional intermediate network 30, and possible further infrastructure (not shown) acting as intermediaries. The OTT connection can 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 uplink and downlink communications. For example, network node 16 may not be notified, or not need to be notified, of the past routing of incoming downlink communications with data originating from host computer 24 that is forwarded (e.g., handed over) to the connected WD22a. Similarly, network node 16 does not need to know the future routing of outgoing uplink communications from WD22a to host computer 24.

[0050] Network node 16 is configured to include node units 32 configured to perform one or more functions of network node 16 as described herein, such as network functions when UE AMBR is unavailable. Core network node 15 is configured to include configuration units 34 configured to perform one or more functions of core network node 15 as described herein, such as network functions when UE AMBR is unavailable.

[0051] An exemplary implementation of the WD22, network node 16, core network node 15, and host computer 24 as described in the previous paragraph will be described with reference to Figure 2. In the communication system 10, the host computer 24 includes hardware (HW) 38 including a communication interface 40 configured to set up and maintain wired or wireless connections with the interfaces of different communication devices of the communication system 10. The host computer 24 further includes a processing circuit 42 which may have storage and / or processing capabilities. The processing circuit 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 circuit 42 may include an integrated circuit for processing and / or control, such as one or more processors adapted to execute instructions, and / or a processor core, and / or an FPGA (field-programmable gate array), and / or an ASIC (application-specific integrated circuit). The processing circuit 44 may be configured to access (for example, write to and / or read from) the memory 46 and may include any type of volatile and / or nonvolatile memory, such as a 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] The processing circuit 42 may be configured to control any of the methods and / or processes described herein and / or to cause such methods and / or processes to be executed, for example, by a host computer 24. The processor 44 corresponds to one or more processors 44 for performing the functions of the host computer 24 described herein. The host computer 24 includes memory 46 configured to store data, program software code and / or other information described herein. In some embodiments, the software 48 and / or host application 50, when executed by the processor 44 and / or processing circuit 42, may include instructions that cause the processor 44 and / or processing circuit 42 to execute the processes described herein in relation to the host computer 24. The instructions may be software associated with the host computer 24.

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

[0054] The communication system 10 further includes a network node 16 provided in the communication system 10, which includes hardware 58 that enables 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 the interfaces of different communication devices of the communication system 10, and a wireless interface 62 for establishing and maintaining a wireless connection 64 with the WD 22 located in a coverage area 18 served by the network node 16. The wireless interface 62 may be formed as, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers, or may include them. 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 outside the communication system 10.

[0055] In the illustrated embodiment, the hardware 58 of the network node 16 further includes a processing circuit 68. The processing circuit 68 may include a processor 70 and memory 72. In particular, in addition to, or instead of, a processor and memory such as a central processing unit, the processing circuit 68 may include an integrated circuit for processing and / or control, such as one or more processors adapted to execute instructions, and / or a processor core, and / or an FPGA (Field Programmable Gate Array), and / or an ASIC (Application-Specific Integrated Circuit). The processing circuit 70 may be configured to access (e.g., write to and / or read from) the memory 72 and may include any kind of volatile and / or non-volatile memory, such as a 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] Thus, the network node 16 further has software 74, which is stored, for example, in memory 72 or in external memory (e.g., a database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by a processing circuit 68. The processing circuit 68 may be configured to control any of the methods and / or processes described herein and / or to cause such methods and / or processes to be executed, for example, by the network node 16. The processor 70 corresponds to one or more processors 70 for performing the functions of the network node 16 described herein. Memory 72 is configured to store data, program software code and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or the processing circuit 68, cause the processor 70 and / or the processing circuit 68 to execute the processes described herein in relation to the network node 16. For example, the processing circuit 68 of the network node 16 may include a node unit 32 configured to perform one or more functions of the network node 16 as described herein, such as network functions when UE AMBR is unavailable.

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

[0058] The WD22 hardware 80 further includes a processing circuit 84. The processing circuit 84 may include a processor 86 and memory 88. In particular, in addition to, or instead of, a processor and memory such as a central processing unit, the processing circuit 84 may include an integrated circuit for processing and / or control, such as one or more processors adapted to execute instructions, and / or processor cores, and / or FPGAs (Field Programmable Gate Arrays), and / or ASICs (Application-Specific Integrated Circuits). The processing circuit 86 may be configured to access (e.g., write to and / or read from) the memory 88 and may include any kind of volatile and / or non-volatile memory, such as caches, and / or buffer memories, 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] Thus, WD22 may further include software 90, which may be stored in the WD22's memory 88, for example, or in external memory accessible by WD22 (e.g., a database, storage array, network storage device, etc.). The software 90 may be executable by the processing circuit 84. The software 90 may include a client application 92. The client application 92 may be able to operate to provide services to human or non-human users via WD22 with the support of the host computer 24. On the host computer 24, a running host application 50 can communicate with the running client application 92 via an OTT connection 52 that terminates at WD22 and the host computer 24. When 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] The processing circuit 84 may be configured to control any of the methods and / or processes described herein and / or to cause such methods and / or processes to be executed by, for example, the WD22. The processor 86 corresponds to one or more processors 86 for performing the functions of the WD22 described herein. The WD22 includes a memory 88 configured to store data, program software code and / or other information described herein. In some embodiments, the software 90 and / or client application 92, when executed by the processor 86 and / or the processing circuit 84, may include instructions that cause the processor 86 and / or the processing circuit 84 to execute the processes described herein in relation to the WD22.

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

[0062] In the illustrated embodiment, the hardware 94 of the network node 16 further includes a processing circuit 98. The processing circuit 98 may include a processor 100 and memory 102. In particular, in addition to, or instead of, a processor and memory such as a central processing unit, the processing circuit 98 may include an integrated circuit for processing and / or control, such as one or more processors adapted to execute instructions, and / or a processor core, and / or an FPGA (Field Programmable Gate Array), and / or an ASIC (Application-Specific Integrated Circuit). The processing circuit 100 may be configured to access (e.g., write to and / or read from) the memory 102 and may include any kind of volatile and / or non-volatile memory, such as a 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] Thus, the core network node 15 further has software 104, which is stored, for example, in memory 102 or in 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 that can be executed by processing circuit 98. Processing circuit 98 may be configured to control any of the methods and / or processes described herein and / or to cause such methods and / or processes to be executed, for example, by the core network node 15. Processor 100 corresponds to one or more processors 100 for performing the functions of the core network node 15 described herein. 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 processing circuit 98, cause the processor 100 and / or processing circuit 98 to execute the processes described herein in relation to the core network node 15. For example, the processing circuit 98 of the core network node 15 may include a configuration unit 34 configured to perform one or more functions of the core network node 16 as described herein, such as network functions when UE AMBR is unavailable.

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

[0065] In Figure 2, the OTT connection 52 is depicted abstractly to illustrate communication between the host computer 24 and the wireless device 22 via the network node 16, without explicitly referring to the intermediate devices and the exact routing of messages through these devices. The network infrastructure may determine the routing, and the routing may be configured to be hidden from the WD22 or the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may make further decisions to dynamically change the routing (for example, based on considerations or reconfiguration of the network load balancing).

[0066] The wireless connection 64 between the WD22 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 services provided to the WD22 by using an OTT connection 52 in which the wireless connection 64 may form the final segment. More precisely, some teachings 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 rate, latency, and other factors that improve one or more embodiments. Furthermore, there may be optional network functions for reconfiguring the OTT connection 52 between the host computer 24 and the WD22 in response to variations in the measurement results. Measurement procedures and / or network functions for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24, or the software 90 of the WD22, or both. In embodiments, sensors (not shown) may be located in or in connection with a communication device through which the OTT connection 52 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or by providing values ​​of other physical quantities that the software 48, 90 may calculate or estimate. Reconfiguration of the OTT connection 52 may include message format, retransmission settings, preferred routing, etc., and the reconfiguration does not need to affect the network node 16, which may be unknown or imperceptible to the network node 16. Some of such procedures and functions may be known and practiced in the art. In certain embodiments, the measurements may include proprietary WD signaling that facilitates measurements of the host computer 24, such as throughput, propagation time, and latency. In some embodiments, the measurements may be implemented so that software 48, 90 sends messages, particularly empty or "dummy" messages, while monitoring propagation time, errors, etc., using an OTT connection 52.

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

[0069] In some embodiments, the host computer 24 includes a processing circuit 42 and a communication interface 40 configured to receive user data resulting from transmissions from the WD22 to the network node 16. In some embodiments, the WD22 includes a radio interface 82 and / or processing circuit 84 configured to perform the functions and / or methods described herein for preparing / starting / maintaining / supporting / terminating transmissions to the network node 16 and / or preparing / terminating / maintaining / supporting / terminating transmissions from the network node 16.

[0070] Figures 1 and 2 show various "units," such as the node unit 32 and the component unit 34, as being located within their respective processors. However, these units are intended to be implemented such that parts of the unit are stored in corresponding memory within the processing circuit. In other words, the units can be implemented as hardware within the processing circuit or as a combination of hardware and software.

[0071] Figure 3 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system of Figures 1 and 2, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be described with reference to Figure 2. In the first step of this method, the host computer 24 provides user data (block S100). In an optional substep of the first step, the host computer 24 provides user data by executing a host application, such as a host application 50 (block S102). In the second step, the host computer 24 initiates a transmission to carry 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 transmission initiated by the host computer 24 to the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (block S106). In an optional fourth step, the WD 22 executes a client application, such as a client application 92, related to the host application 50 executed by the host computer 24 (block S108).

[0072] Figure 4 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system of Figure 1, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD22, which may be described with reference to Figures 1 and 2. In the first step of this method, the host computer 24 provides user data (block S110). In an optional substep (not shown), the host computer 24 provides user data by executing a host application, such as a host application 50. In the second step, the host computer 24 initiates a transmission to carry the user data to the WD22 (block S112). As taught in the embodiments described throughout this disclosure, the transmission may pass through the network node 16. In an optional third step, the WD22 receives the user data carried in the transmission (block S114).

[0073] Figure 5 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system of Figure 1, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD 22, which may be described with reference to Figures 1 and 2. In an optional first step of this method, the WD 22 receives input data provided by the host computer 24 (block S116). In an optional substep of the first step, the WD 22 runs a client application 92 that 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 user data (block S120). In an optional substep of the second step, the WD provides user data by running a client application, such as the client application 92 (block S122). When providing user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific method by which the user data is provided, WD22 may, in an optional third substep, initiate transmission of the user data to the host computer 24 (block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from WD22 in accordance with the teachings of the embodiments described throughout this disclosure (block S126).

[0074] Figure 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as the communication system of Figure 1, according to one embodiment. The communication system may include a host computer 24, a network node 16, and a WD22, which may be described with reference to Figures 1 and 2. In an optional first step of the method, the network node 16 receives user data from the WD22 (block S128), in accordance with the teachings of the 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 the transmission initiated by the network node 16 (block S132).

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

[0076] According to one or more embodiments, the processing circuit 68 is configured to refrain from inspecting the UE AMBR for a quality of service (QoS) flow associated with one of the emergency service setup and handover procedures.

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

[0078] According to one or more embodiments, the processing circuit 68 is further configured to transmit Next Generation Application Protocol (NGAP) messages to the determined UE AMBR access and mobility management function (AMF) node.

[0079] According to one or more embodiments, the network entity is one of an Integrated 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 a locally configured UE AMBR to perform one of the emergency service setup and handover procedures for the wireless device 22.

[0081] In one or more embodiments, the AMF provides UE AMBRs to NG-RAN nodes. While the AMF may receive UE AMBRs from a UDM or PCF, if it does not receive UE AMBRs from a 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 performing its inspection if UE AMBR is not provided. NG-RAN has a locally configured UE AMBR for emergency services, and NG-RAN uses this locally configured UE AMBR. NG-RAN infers the UE AMBR from the PDU session AMBR. In this case, NG-RAN may also need to send the inferred UE AMBR parameters back to AMF in an NGAP message (e.g., HO required).

[0083] Figure 8 is a flowchart of an exemplary process in a core network node 15 according to several 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 circuit 98 (including the configuration unit 34), the processor 100 and / or the communication interface 96. The core network node 15 is configured to store pre-configured UE aggregated maximum bitrate (AMBR) parameters (block S136), as described herein. The core network node 15 is configured to use a pre-configured UE AMBR for emergency service setup if a 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 an Integrated 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 circuit 98 is further configured to transfer a pre-configured 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 the pre-configured UE AMBRs or a UE AMBR configured locally at the network node 16.

[0088] Figure 9 is a flowchart of another exemplary process in the core network node 15 according to several 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 circuit 98 (including the configuration unit 34), the processor 100 and / or the communication interface 96. The core network node 15 is configured to store local UE aggregated maximum bitrate (AMBR) parameters applied to any user equipment (UE) (22) requesting emergency service (block S140), as described herein. After storing the local UE AMBR parameters, the core network node 15 is configured to receive an emergency service request from a first UE 22 via the access network node 16 (block S142), as described herein. The core network node 15 is configured to send a message to the access network node 16 containing the local UE AMBR parameters for emergency service setup for the first UE 22 (block S144), as described herein.

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

[0090] According to one or more embodiments, the transmission of a message containing local UE AMBR parameters is based on the fact that the UE AMBR parameters are not obtained from the network entity.

[0091] According to one or more embodiments, the network entity is an integrated 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 to receive an emergency service request from the second UE 22 via the access network node 16, after storing the local UE AMBR parameters, and to send a message to the access network node 16 containing the local UE AMBR parameters for setting up emergency services for the second UE 22.

[0096] According to one or more embodiments, local UE AMBR parameters are stored as part of emergency configuration data applied 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] While the general process flow of the configuration of this disclosure has been described and examples of hardware and software configurations for implementing the processes and functions of this disclosure have been provided, the following sections provide details and examples of network function configurations when UE Aggregated Maximum Bitrate (AMBR) is not available.

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

[0100] Embodiments described herein relate to establishing emergency services even when a UE AMBR (e.g., a wireless device AMBR) is unavailable in the UDM or PCF.

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

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

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

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

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

[0106] If the Emergency Service has configured QoS for 5QI==5"IMS Signaling" and 5QI==1"Conversational Voice", the NG-RAN node will not fail the procedure (e.g., execute the procedure) even if the UE AMBR is not offered, not received, or unknown. The Emergency Service must be able to configure or execute an 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 the Emergency Service even if the UE AMBR is not provided during the PDU session resource configuration procedure. Changes are shown in bold.

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

[0108] If the AMF has not previously sent the UE aggregated maximum 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 maximum bitrate in the radio device context and uses the received UE aggregated maximum bitrate for all non-GBR QoS flows of the radio device, as specified in 3GPP® TS23.501.

[0109] In the case of emergency services, if the UE aggregated maximum bitrate is not transmitted or received, and is not received promptly, the NG-RAN node skips applying the UE aggregated maximum bitrate to all non-GBR QoS flows for the relevant radio device 22.

[0110] [Table 1]

[0111] In another embodiment, if an emergency service is configured over 5G without a UE AMBR being provided by the AMF, the UE AMBR limits are not checked, for example, by network node 16. The emergency service is configured with all requested QoS conditions met. See Table 1.

[0112] In yet another embodiment, the NG-RAN node would “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 can use PDU session-level AMBR parameters as UE AMBR parameters, either through local configuration or computation.

[0114] In yet another embodiment, if an emergency fallback is performed and the UE AMBR is not provided by the AMF, the NG-RAN node may include a "configured UE AMBR". The "configured UE AMBR" may be configured in the 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 an in-system handover for emergency fallback, the target NG-RAN node proceeds with the emergency service handover without receiving a UE AMBR from the AMF, similar to the emergency service setup procedures described above (no UE AMBR limit check, use of a locally configured UE AMBR, or using a PDU session AMBR as the UE AMBR).

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

[0118] [Table 3]

[0119] In yet another embodiment, the split NG-RAN architecture is defined as allowing a gNB-CU (e.g., network node CU) to configure the UE AMBR (if the UE AMBR is not received) and send it to the gNB-DU (e.g., network node DU) during context setting. A similar approach may be used for the Xn and E1 interfaces.

[0120] Instead, the absence of UE AMBR is permitted in emergency service setup or handover procedures. This may result in changes to XnAP, F1AP, and / or E1AP, where the presence of UE AMBR IE changes from mandatory to optional, as shown in Table 3.

[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] Therefore, one or more embodiments described herein provide emergency service configuration even when UE AMBR is unavailable (e.g., emergency service configuration independent of UE AMBR availability).

[0123] Some examples:

[0124] Example of core network node 15 (e.g., AMF): • The AMF may include the UE AMBR in emergency configurations based on the network operator's decision, for example, when the UE AMBR is not available from the UDM / PCF. In an alternative approach, the AMF always includes a UE AMBR obtained from the UDM, PCF, or based on the local configuration. If a UE AMBR is unavailable, the AMF will use the configured UE AMBR or the UE AMBR configured locally by the NG-RAN node (e.g., network node 16) (e.g., the one received from the NG-RAN node), and will forward the UE AMBR to the other AMF during an AMF handover.

[0125] Example of an NG-RAN node (e.g., network node 16) • NG-RAN nodes will not fail to perform emergency service configuration or handover procedures even if the UE AMBR is not presented. In the above case, UE AMBR inspection for QoS flow may not be performed. Instead, it is stipulated that the NG-RAN node will use a 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. This supports emergency fallback due to handover. In a split NG-RAN node architecture, the gNB-CU can configure the UE AMBR (if it does not receive a UE AMBR) and send it to the gNB-DU during context setup. A similar approach can be used for the Xn and E1 interfaces. Instead, the absence of UE AMBR is permitted in emergency service setup or handover procedures, for example, by being predefined as allowed in the specification.

[0126] One of the benefits provided by the teachings of this disclosure is that emergency services (e.g., emergency services via wireless devices) can be set up or provided in accordance with regulations even when UE AMBR is unavailable.

[0127] According to one or more embodiments, to support emergency registration of 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 required UE context on the RAN side. The AMF emergency configuration data may be included in the UE-AMBR; otherwise, the configuration of emergency resources may fail. For example, if a non-GBR QoS flow is configured, the UE-AMBR may be required. If a UE cannot register with the network or does not have a UICC and therefore no UDM record, this UE should be allowed to configure emergency services by rule, but does not have a UE AMBR. In the case of 5QI 5"IMS signaling", a non-GBR service 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 stipulate that if a UE AMBR is not provided, the NG-RAN node will permit emergency service and the UE AMBR inspection will be skipped. The mandatory presence of a UE AMBR in a handover request is changed to optional.

[0128] In other words, if the AMF has not previously sent a UE aggregated maximum bitrate IE, it must be sent to the NG-RAN node. If the PDU SESSION RESOURCE SETUP REQUEST message contains a UE aggregated maximum bitrate IE, the NG-RAN node stores it in the UE context and uses the received UE aggregated maximum bitrate for all non-GBR QoS flows of the applicable UE. In the case of emergency service, if the UE aggregated maximum bitrate is not sent or received and is not received early, the NG-RAN node skips applying the UE aggregated maximum bitrate to all non-GBR QoS flows of the applicable UE.

[0129] According to one or more embodiments, in order to provide emergency services, the AMF is configured with emergency configuration data that is applied to the emergency services established by the AMF based on a request from the UE. The AMF emergency configuration data includes the S-NSSAI and the 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 that includes statically configured UPF information for the emergency DNN. The AMF emergency configuration data may also include the 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: - Attempt to execute the requested PDU session configuration; - The received UE aggregated maximum bitrate is stored in the UE context, and the received UE aggregated maximum bitrate is used for the non-GBR QoS flows of the applicable UE, as specified in 3GPP® TS23.501. In the case of emergency service, if the UE aggregated maximum bitrate is not transmitted or received and is not received promptly, the NG-RAN node must skip applying the UE aggregated maximum bitrate to all non-GBR QoS flows of the applicable UE; -Store the received mobility restriction list in the UE context; and / or - Store the received UE radio capability in the UE context.

[0131] According to one or more embodiments, upon receiving a HANDOVER REQUEST message, the target NG-RAN node is configured as follows: - Attempt to perform the requested PDU session configuration and associated security measures; - The received UE aggregated maximum bitrate is stored in the UE context, and the received UE aggregated maximum bitrate is used for all non-GBR QoS flows of the applicable UE, as specified in 3GPP® TS23.501. In the case of emergency service, if the UE aggregated maximum bitrate is not transmitted / received and is not received promptly, the NG-RAN node must skip applying the UE aggregated maximum bitrate to all non-GBR QoS flows of the applicable UE; -Store the received mobility restriction list in the UE context; and / or - Store the received UE security capabilities in the UE context.

[0132] Several additional examples

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

[0134] Example A2. A network node 16 as described in Example A1, wherein the processing circuit 68 is configured to refrain from inspecting the UE AMBR for a Quality of Service (QoS) flow associated with one of the emergency service setup and handover procedures.

[0135] Example A3. A network node 16 as described in Example A1, wherein the processing circuit 68 is further configured to determine the UE AMBR from the Packet Data Network (PDU) session AMBR, and one of the emergency service setup and handover procedures is performed based on the PDU session AMBR.

[0136] Example A4. A network node 16 as described in Example A3, wherein the processing circuit 68 is further configured to transmit the determined UE AMBR to the Access and Mobility Management Function (AMF) node using Next Generation Application Protocol (NGAP) messages.

[0137] Example A5. A network node 16 as described in Example A1, wherein the network entity is one of the following: an Integrated Data Manager (UDM) node and a Policy Control Function (PCF) node.

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

[0139] Example B1. A method that is executed on network node 16, A method comprising performing one of the emergency service setup and handover procedures for a wireless device 22 without receiving user equipment (UE) aggregated maximum bitrate (AMBR) parameters associated with the wireless device 22 from a network entity.

[0140] Example B2. A method relating to Example B1, further comprising refraining from inspecting the UE AMBR for a Quality of Service (QoS) flow associated with one of the emergency service setup and handover procedures.

[0141] Example B3. The method described in Example B1, further comprising determining the UE AMBR from the Packet Data Network (PDU) session AMBR, One of the emergency service setup and handover procedures is performed based on the PDU session AMBR.

[0142] Example B4. A method relating to Example B1, further comprising causing a Next Generation Application Protocol (NGAP) message to be sent to the determined UE AMBR's Access and Mobility Management Function (AMF) node.

[0143] Example B5. A method relating to Example B1, wherein the network entity is one of an Integrated Data Manager (UDM) node and a Policy Control Function (PCF) node.

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

[0145] Example C1. Core network node 15, This involves storing pre-configured User Equipment (UE) aggregated maximum bitrate (AMBR) parameters, A core network node, including a radio interface and / or processing circuit 98, is configured to use a pre-configured UE AMBR for emergency service setup if a UE AMBR is not available from a network entity.

[0146] Example C2. A core network node 15 as described in Example C1, wherein the network entity is one of the following: an Integrated Data Manager (UDM) node and a Policy Control Function (PCF) node.

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

[0148] Example C4. A core network node 15 as described in Example C1, wherein the processing circuit 98 is further configured to transfer a pre-configured UE AMBR to another core network node 15 during a handover between core network nodes.

[0149] Example C5. A core network node 15 as described in Example C4, wherein the pre-configured UE AMBR is one of the pre-configured UE AMBRs or a UE AMBR configured locally on network node 16.

[0150] Example D1. A method that is executed on core network node 15, This involves storing pre-configured User Equipment (UE) aggregated maximum bitrate (AMBR) parameters, If a UE AMBR cannot be obtained from the network entity, a pre-configured UE AMBR will be used for emergency service configuration. A method that includes this.

[0151] Example D2. A method relating to Example D1, wherein the network entity is one of an Integrated Data Manager (UDM) node and a Policy Control Function (PCF) node.

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

[0153] Example D4. A method relating to Example D1, further comprising transferring a pre-configured UE AMBR to another core network node 15 during a handover between core network nodes.

[0154] Example D5. A method relating to Example D4, wherein the pre-configured UE AMBR is one of the pre-configured UE AMBRs or a UE AMBR configured locally on the network node 16.

[0155] As those skilled in the art will understand, the concepts described herein can be embodied as methods, data processing systems, computer program products, and / or computer storage media for storing executable computer programs. Accordingly, the concepts described herein can 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 can be executed and / or associated with corresponding modules that can be implemented in software and / or firmware and / or hardware. Furthermore, this disclosure can take the form of computer program products on tangible computer-readable storage media having computer program code embodied in the medium, which can be executed by a computer. Any suitable tangible computer-readable medium, including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices, can be used.

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

[0157] These computer program instructions may also be stored in computer-readable memory or on a readable medium and can instruct a computer or other programmable data processing device to function in a particular way, and instructions stored in computer-readable memory may produce a product that includes instruction means to perform the functions / operations specified in the flowchart and / or block diagram.

[0158] Furthermore, computer program instructions may be loaded into a computer or other programmable data processing device to produce a series of operational steps executed on the computer or other programmable device for creating a process that runs on the computer, and the instructions executed by the computer or other programmable device provide steps for performing functions / operations identified in flowcharts and / or block diagrams.

[0159] Please understand that the functions / operations shown in the blocks may occur in a different order than that shown in the operation diagram. For example, depending on the related functions / operations, two blocks shown consecutively may actually be executed substantially simultaneously, or the blocks may be executed in reverse order. Some diagrams include arrows on the communication path to indicate the main direction of communication, but please understand that communication may occur in the opposite direction to the depicted arrows.

[0160] Computer program code for performing the operations of the concepts described herein may be written in an object-oriented programming language such as Python, Java®, or C++. However, computer program code for performing the operations of the disclosure may also be written in a conventional procedural programming language such as the "C" programming language. The program code may run entirely on the user's computer, partially on the user's computer, as a standalone 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 may be connected to the user's computer via a local area network (LAN) or wide area network (WAN), or the connection may be made to an external computer (for example, via the Internet using an Internet service provider).

[0161] In connection with the above description and drawings, many different embodiments are disclosed herein. It will be understood that a literal description and illustration of every combination and partial combination of these embodiments would be overly repetitive and confusing. Therefore, all embodiments can be combined in any way and / or combination, and this specification, including the drawings, shall be construed as constituting a complete written description of all combinations and partial combinations of the embodiments described herein, and the methods and processes for creating and using them, and shall support any claims for such combinations or partial combinations.

[0162] Abbreviations that may be used in the above explanation include the following: Abbreviations and Explanations 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 aggregated maximum bitrate

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

Claims

1. A core network node (15), To store the local UE aggregated maximum bitrate (AMBR) parameter applied to any user equipment (UE) (22) requesting emergency service, After storing the local UE AMBR parameters, the access network node (16) receives an emergency service request from the first UE (22), To cause the access network node (16) to send a message containing the local UE AMBR parameters for setting up emergency services for the first UE (22), A core network node including a processing circuit (98) configured to perform the following.

2. A core network node (15) according to claim 1, The processing circuit (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 of the core network node.

3. A core network node (15) according to claim 1, The transmission of the message containing the local UE AMBR parameters is based on the fact that the UE AMBR parameters are not obtained from the network entity, and is therefore carried out by a core network node.

4. A core network node (15) according to claim 3, The aforementioned network entity is a core network node, which is an integrated data manager (UDM) node.

5. 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 claim 1, The aforementioned core network node (15) is a core network node that provides access and mobility management functions (AMF).

7. A core network node (15) according to claim 1, The aforementioned emergency service is a core network node that supports Internet Protocol Multimedia Subsystem (IMS) emergency sessions.

8. A core network node (15) according to claim 1, The aforementioned local UE AMBR parameters are stored as part of the emergency configuration data applied to the emergency service on the core network node.

9. A core network node (15) according to any one of claims 1 to 8, The processing circuit (98) further, After storing the local UE AMBR parameters, the access network node (16) receives an emergency service request from the second UE (22), To cause the access network node (16) to send a message containing the local UE AMBR parameters for setting up emergency services for the second UE (22), A core network node configured to perform this task.

10. A method that is executed on the core network node (15), To store the local UE aggregated maximum bitrate (AMBR) parameter applied to any user equipment (UE) requesting emergency service, After storing the local UE AMBR parameters, the system receives an emergency service request from the first UE via the access network node. Sending a message to the access network node containing the local UE AMBR parameters for emergency service configuration for the first UE, A method that includes this.

11. The method according to claim 10, further, A method comprising determining that the core network node does not have subscription data stored for the first UE, wherein the transmission of the message including the local UE AMBR parameters is based on the determination.

12. The method according to claim 10, The transmission of the message containing the local UE AMBR parameter is based on the fact that the UE AMBR parameter is not obtained from the network entity.

13. A method according to claim 12, The method wherein the network entity is an integrated data manager (UDM) node.

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

15. The method according to claim 10, The method wherein the core network node is an Access and Mobility Management Function (AMF).

16. The method according to claim 10, The aforementioned emergency service is a method for responding to an Internet Protocol Multimedia Subsystem (IMS) emergency session.

17. The method according to claim 10, further, A method comprising storing the local UE AMBR parameters and then receiving an emergency service request from a second UE via the access network node.

18. The method according to claim 17, further, A method comprising sending a message to the access network node containing the local UE AMBR parameters for emergency service configuration for the second UE.

19. The method according to claim 10, The local UE AMBR parameter is stored as part of the emergency configuration data applied to the emergency service.

20. A computer-readable medium storing program instructions that, when executed by the processor, constitute the processor to perform the method according to any one of claims 10 to 19.

Images