ODB exempted dnns

Abstract

Disclosed herein is a method performed by first core network node in a core network of a cellular communications system, the method comprising: storing (Fig. 7A, step 1; Fig. 7B, step 7; Fig. 70, step 13) information that indicates one or more Data Network Names, DNNs, that are exempted from Operator Defined Barring, ODB; and using the information that indicates the one or more DNNs that are exempted from ODB to perform one or more actions related to Protocol Data Unit, PDU, establishment or session mobility.

Description

ODB EXEMPTED DNNsTECHNICAL FIELD

[0001] The present disclosure relates to a cellular communications system and, more specifically, to Operator Determined Barring (ODB) in a cellular communications system.BACKGROUND

[0002] 3rdGeneration Partnership Project (3GPP) Technical Specification (TS) 23.015 V18.0.0 describes the networks feature Operator Determined Barring (ODB). Clause 2.5B of 3GPP TS 23.015 describes barring of Protocol Data Unit (PDU) session establishment and is reproduced below in an excerpt from 3GPP TS 23.015. Clause 2.6C of 3GPP TS 23.015 describes barring of existing PDU sessions and is reproduced below in an excerpt from 3GPP TS 23.015. Clause 2.9 of 3GPP TS 23.015 describes barring of access to all except some specific Data Network Names (DNNs) I Access Point Name (APN) through Unified Data Management (UDM)ZHome Subscriber Server (HSS)ZHome Location Register (HLR) provisioned subscription profile with only non-barred DNNs, and is reproduced below in an excerpt from 3GPP TS 23.015. Clause 3.1 A of 3GPP TS 23.015 describes information stored in the Unified Data Management (UDM) I Unified Data Repository (UDR) and is reproduced below in an excerpt from 3GPP TS 23.015.***** START EXCERPTS FROM 3GPP TS 23.015 *****2.5B Barring of PDU Session establishmentBarring of PDU Session establishment shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3 GPP TS 22.041 [2],2.5B.1 Application or Change of Barring in the UDMIf barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the UDM, the UDM shall update the subscription information accordingly, and transfer the updated subscription information to the AMF / SMF using Nudm_SDM Notification operation, as shown in figure 2.5B.1 / 1.Figure 1[REPRODUCED HEREIN AS FIGURE 1]Figure 2.5B.1Z1 : Transfer of updated subscription information to AMFZSMF2.5B.2 Invocation of BarringBarring of PDU Session establishment is invoked in the SMF. If the SMF receives from an UE connected over 5GS a PDU Session connectivity request which is prohibited by Operator Determined Barring, the SMF shall return a negative response to the request with an appropriate error indication to the UE over the 5G radio path.NOTE: Barring of PDU Session establishment for Packet Oriented Services is not applicable for Local Access Data Network (LADN).For subscribers completely barred from the Packet Oriented Services, the AMF may reject the registration requests.Barring of PDU Session establishment for other barring categories for the Packet Oriented Services, SMF determines whether a request for PDU Session establishment shall be barred or not:For "bar subscribers completely from the Packet Oriented Services", the SMF shall reject the PDU connectivity request.For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN" , if the subscriber is not located in the HPLMN and the SMF being accessed is located in HPLMN, then the SMF shall reject the PDU connectivity request,For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", if the subscriber is not located in the HPLMN and the SMF being accessed is located in VPLMN, then the SMF shall reject the PDU connectivity request.Indicative message flow diagram for the handling of Operator Determined Barring of PDU Session establishment is given in figures 2.5B.2 / 1.Figure 2[REPRODUCED HEREIN AS FIGURE 2]Figure 2.5B.2 / 1 : Operator Determined Barring of PDU Session Establishment in the SMF***** START NEXT EXCERPT FROM 3GPP TS 23.015 *****2.6C Barring of existing PDU SessionsBarring of existing PDU Sessions shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2],2.6C.1 Application or Change of Barring in the UDMIf barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the UDM, the UDM shall update the subscription information accordingly, and transfer the updated subscription information to the AMF using Nudm_SDM Notification operation, as shown in figure 2.6C.1 / 1.Figure 3[REPRODUCED HEREIN AS FIGURE 3]Figure 2.6C.1 / 1 : Transfer of updated subscription information to AMF2.6C.2 Invocation of BarringBarring of existing PDU Sessions is invoked in the AMF. If the AMF receives Nudm_SDM Notification message due to barring of Packet Oriented Services being applied to a subscription (or existing barring of Packet Oriented Services is modified) by administrative action in the UDM, or if the new AMF received the barring of Packet Oriented Services from the UDM during a mobility registration procedure, the AMF shall take the following action depending on barring category when one or more PDU Sessions exist in AMF.For "bar subscribers completely from the Packet Oriented Services", AMF shall request SMF to release all existing PDU Sessions.For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN" , AMF shall check whether or not the subscriber is located in the HPLMN. If it is not and the SMF being accessed is located in HPLMN, then all associated PDU Sessions with this path shall be released by the SMF on request of the AMF .For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", AMF shall check whether or not the subscriber is located in the HPLMN. If it is not and the SMF being accessed is located in VPLMN, then all associated PDU sessions with this path shall be released by the SMF on request of the AMF.NOTE: Barring of existing EPS Bearer contexts for Packet Oriented Services is not applicable for Local Access Data Network (LADN).***** START NEXT EXCERPT FROM 3GPP TS 23.015 *****2.9 Barring of Access to All Except Some SpecificDNNs / APNs2.9.1 GeneralBarring of access to all except some specific DNNs / APNs shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2],2.9.2 Application or Change of Barring in the UDM / HSS / HLRWhen barring of access to all except some specific DNNs / APNs is invoked in the UDM / HSS / HLR, the UDM / HSS / HLR shall update the subscription profile to contain only the specific non barred DNNs / APNs as the subscribed DNNs / APNs and indicate the updated subscription information to the AMF, SMF, MME or the SGSN.If the existing default DNN / APN is barred, one of the specific non barred DNN / APNs shall be the new default DNN / APN.The UDM / HSS / HLR shall disable any other barring of Packet Oriented Services when this function is used.When barring of access to all except some specific DNNs / APNs is removed in the UDM / HSS / HLR, the UDM / HSS / HLR shall update the subscription profile to restore the originally subscribed DNNs / APNs, including the original default DNN / APN and indicate the updated subscription information to the AMF, SMF, the MME or the SGSN.2.9.3 Invocation of BarringWhen the AMF, the SMF, the MME or the SGSN updates the subscription, and if the subscriber has existing PDN connectivity for DNNs / APNs not in the received list of subscribed DNN / APN, the SMF, MME or the SGSN deactivates the PDU / PDN connectivity for these DNNs / APNs as specified in 3GPP TS 23.502 [7], 3GPP TS 23.401 [6] and 3GPP TS 23.060 [4],To bar a subscriber from access to all except some specific DNNs / APNs, when the AMF, the MME or the SGSN receives PDU / PDN Connectivity Request message from the UE or the MS, the AMF, the MME or the SGSN shall check whether or not the requested DNN / APN is included in the list of subscribed DNNs / APNs for the subscriber. If included, then the AMF, the MME or the SGSN continues the Attach or UE -requested PDU / PDN connectivity or MS-requested PDP Context Activation procedures as specified in 3GPP TS 23.502 [7], 3GPP TS 23.401 [6] and 3GPP TS 23.060 [4], If not included, then the AMF, the MME or the SGSN rejects the Attach or UE-requested PDU / PDN connectivity or MS-requested PDP Context Activation requests as specified in 3GPP TS 23.502 [7], 3GPP TS 23.401 [6] and 3GPP TS 23.060 [4],***** START NEXT EXCERPT FROM 3GPP TS 23.015 *****3.1 A Information stored in the UDM / UDRBarring of roaming - one of:Barring of roaming outside the home PLMN:Barring of roaming outside the home PLMN country. - Barring of Packet Oriented Services - one of:Barring of all Packet Oriented Services;Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN;Barring of Packet Oriented Services from access points that are within the roamed to VPLMN;*****ENDEXCERPTS FROM 3GPP TS 23.015 *****

[0003] 3GPP TS 29.503 V18.5.0 defines for ODB provisioned in UDM forAccessAndMobilitySubscription and SessionManagementSubscription data as shown in the excerpts below:***** START EXCERPTS FROM 3GPP TS 29.503 *****6.1.6.2.4 Type: AccessAndMobilitySubscriptionDataTable 6.1.6.2.4-1 : Definition of type AccessAndMobilitySubscriptionDataNNN***** START NEXT EXCERPT FROM 3GPP TS 29.503 ***** .1.6.2.8 Type: SessionManagementSubscriptionDataTable 6.1.6.2.8-1 : Definition of type SessionManagementSubscriptionData*****ENDEXCERPTS FROM 3GPP TS 29.503 *****

[0004] 3GPP TS 29.571 V18.5.0 provides an enumeration of OdbPacketServices, as shown in the excerpt below.***** START EXCERPT FROM 3GPP TS 29.571 *****5.7.3.2 Enumeration: OdbPacketServicesThe enumeration OdbPacketServices defines the Barring of Packet Oriented Services. See 3GPP TS 23.015

[0026] for further description. It shall comply with the provisions defined in table 5.7.3.2-1.Table 5.7.3.2-1 : Enumeration OdbPacketServices*****ENDEXCERPT FROM 3GPP TS 29.571 *****

[0005] For barring of access to all except some specific DNNs, it requires the UDM provision the specific DNNs are exempted from ODB as subscribed DNNs instead of UDM provision ODB in the subscription data.SUMMARY

[0006] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0007] There currently exist certain challenge(s). In 3GPP specifications, it is currently required at stage 1 (SA1) that the network shall be able to allow a subscriber to access some specific APNs while barring the subscriber from other Packet Oriented Services (see 3GPP TS 22.041). Correspondingly, stage 2 has specified that those nonbarred DNNs / APNs are provisioned as the subscribed DNNs / APNs. So, as long as DnnConfiguration is provisioned in the SessionManagementSubscriptionData in the UDM, the corresponding dnn is exempted by the ODB barring.

[0008] In view of this there is amongst other things a need in a real network to exempt some DNNs' traffic from the ODB barring only when the UE is in certain locations and / or in a specific time of day, week, or month.

[0009] To overcome or mitigate at least one problem mentioned herein or other problems, a solution is proposed that enables an operator to deploy local policy for ODB user to access free services and facilitates that legacy end to end session management and session mobility functions work well and that 23.015 principle for ODB may still be applied, that AMF is responsible for existing sessions handling and SMF is responsible for new session handling. While not limited to the above mentioned proposed solution or any particular advantage provided by that solution, other solutions disclosures herein may provide a number of advantages over existing technology.

[0010] One solution that is disclosed herein is directed to a method performed by first core network node in a core network of a cellular communications system and a core network node performing the method. The method comprises: storing (Fig. 7A, step 1; Fig. 7B, step 7; Fig. 7C, step 13) information that indicates one or more Data Network Names, DNNs, that are exempted from Operator Defined Barring, ODB; and using the information that indicates the one or more DNNs that are exempted from ODB to perform one or more actions related to Protocol Data Unit, PDU, establishment or session mobility.

[0011] Another solution that is disclosed herein is directed to a method performed by a Session Management Function (SMF) and a SMF performing the method comprises: as part of a Protocol Data Unit, PDU, session establishment procedure, receiving (Fig. 7A, step 2; Fig. 7B, step 8; Fig. 7C, step 16) a request to create a session management context for the PDU session, wherein the request comprises information that indicates a Data Network Name, DNN, for which establishment of the PDU session is requested; obtaining (Fig. 7A, step 2; Fig. 7B, step 7; Fig. 7C, step 18), either from local storage or from another network node, information that indicates that the DNN is exempted from Operator Determined Barring, ODB; and determining (Fig. 7A, step 5; Fig. 7B, step 11; Fig. 7C, step 19) to accept the request to create the session management context for the PDU session based on the information that indicates that the DNN is exempted from ODB (e.g., even if subscription data obtained from a UDM indicates that ODB is applicable for the DNN).

[0012] Now, the description will turn to a more detailed description of some example embodiments of the present disclosure.BRIEF DESCRIPTION OF THE DRAWINGSThe above and other aspects, features, and benefits of various embodiments of the present disclosure will become more fully apparent, by way of example, from the following detailed description with reference to the accompanying drawings, in which like reference numerals or letters are used to designate like or equivalent elements. The drawings are illustrated for facilitating better understanding of the embodiments of the disclosure and not necessarily drawn to scale, in which:FIG. 1 illustrates a transfer of updated subscription information to AMF / SMF as shown in 3GPP TS 23.015 Figure 2.5B.1 / 1;FIG. 2 illustrates an Operator Determined Barring of PDU Session Establishment in the SMF as shown in 3GPP TS 23.015 Figure 2.5B.2 / 1;FIG. 3 illustrates a Transfer of updated subscription information to AMF as shown in 3GPP TS 23.015 Figure 2.6C.1 / 1;FIG. 4 illustrates one example of a cellular communications system 400 in which embodiments of the present disclosure may be implemented;FIG. 5 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs);FIG. 6 illustrates a 5G network architecture using service-based interfaces between the NFs in the Control Plane (CP);FIG. 7A illustrates a PDU session establishment procedure in accordance with one example solution;FIG. 7B illustrates a PDU session establishment procedure in accordance with another example solution;FIG. 7C illustrates a PDU session establishment procedure in accordance with still another example solution;FIG. 8A and 8B illustrate an example embodiment of an inter-AMF mobility procedure in accordance with the present disclosure;FIG. 9 is a schematic block diagram of a network node 900 according to some embodiments of the present disclosure;FIG. 10 is a schematic block diagram that illustrates a virtualized embodiment of the network node 900 according to some embodiments of the present disclosure;FIG. 11 is a schematic block diagram of the network node 900 according to some other embodiments of the present disclosure;FIG. 12 is a schematic block diagram of a UE 412 according to some embodiments of the present disclosure; FIG. 13 is a schematic block diagram of the UE 412 according to some other embodiments of the present disclosure.DETAILED DESCRIPTION

[0013] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0014] Radio Node: As used herein, a "radio node” is either a radio access node or a User Equipment (UE).

[0015] Radio Access Network (RAN) Node: As used herein, a "RAN node” or "radio access node” or "radio network node” is any node in a RAN of a cellular communications network. Some examples of a RAN node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB Central Unit (gNB-CU) or a network node that implementsa gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of RAN node.

[0016] Core Network Node: As used herein, a "core network node” is any type of node in a core network or any node that implements a core network function. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.

[0017] Communication Device: As used herein, a "communication device” is any type of device that has access to an access network. Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The communication device may be a portable, hand-held, computer- comprised, or vehicle-mounted mobile device, enabled to communicate voice and / or data via a wireless or wireline connection.

[0018] User Equipment (UE): One type of communication device is a UE, which as used herein may be any type of wireless communication device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a UE include, but are not limited to: a UE in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (loT) device. Such UEs may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC. The UE may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and / or data via a wireless connection.

[0019] Network Node: As used herein, a "network node” is any node that is either part of the RAN or the core network of a cellular communications network / system.

[0020] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

[0021] Note that, in the description herein, reference may be made to the term "cell”; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

[0022] There currently exist certain challenge(s). In 3GPP specifications, it is currently required at stage 1 (SA1) that the network shall be able to allow a subscriber to access some specific APNs while barring the subscriber from other Packet Oriented Services (see 3GPP TS 22.041). Correspondingly, stage 2 has specified that those non-barred DNNs / APNs are provisioned as the subscribed DNNs / APNs. So, as long as DnnConfiguration is provisioned in the SessionManagementSubscriptionData in the UDM, the corresponding dnn is exempted by the ODB barring.See the following requirement cited from 3GPP TS 23.015 (emphasis added):2.9.2 Application or Change of Barring in the UDM / HSS / HLRWhen barring of access to all except some specific DNNs / APNs is invoked in the UDM / HSS / HLR, the UDM / HSS / HLR shall update the subscription profile to contain only the specific non barred DNNs / APNs as the subscribed DNNs / APNs and indicate the updated subscription information to the AMF, SMF, MME or the SGSN.If the existing default DNN / APN is barred, one of the specific non barred DNN / APNs shall be the new default DNN / APN.The UDM / HSS / HLR shall disable any other barring of Packet Oriented Services when this function is used.When barring of access to all except some specific DNNs / APNs is removed in the UDM / HSS / HLR, the UDM / HSS / HLR shall update the subscription profile to restore the originally subscribed DNNs / APNs, including the original default DNN / APN and indicate the updated subscription information to the AMF, SMF, the MME or the SGSN.

[0023] However, there is a need in a real network to exempt some DNNs' traffic from the ODB barring only when the UE is in certain locations and / or in a specific time of day, week, or month. Such function may be achieved by:(1) configuring local policies on the AMF or the SMF, e.g. AMF I SMF may override ODB barring information received from the UDM, to allow the PDU session establishment if UE is in certain location at certain timeslot. But, as shown in the Background section, in the existing 3GPP specifications e.g. 3GPP TS 29.503, the SAME odbPacketServices is provisioned in both AccessAndMobilitySubscriptionData and SessionManagementSubscriptionData. In addition, the existing 3GPP specifications require (emphasis added):NOTE 2: For the same UE, the value of this IE shall be identical to the value of the odbPacketServices IE in AccessAnd Mobilitysubscription Data data set (see clause 6.1.6.2.4). The SMF shall not trigger PDU session release when receiving change of OdbPacketService. Only the AMF take responsibility to perform PDU session related actions subject to change of ODB setting, e.g. release existing PDU session.This leads to a clash with the subscription if one of entity (e.g. the AMF or the SMF) determines the Dnn is exempted from ODB and didn't inform the other entity.(2) enhancing the subscription data to enable provisioning a non-barred DNN configuration with the location and / or time conditions.

[0024] Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. Systems and methods are disclosed herein that provide the following solutions to enable data traffic from some access points (e.g., as identified by the DNN) is exempted from Operator Determined Barring (ODB).

[0025] Solution 1 : ODB exempted DNNs information is defined in AMF, e.g., the AMF may be configured with such information for those UEs attaching from a specific area where it is offered with a data connectivity at a specific timeslot even when ODB is provisioned in subscription data in UDM. For this solution, a new indication is introduced so that the AMF can indicate to the SMF to skip the UDM provisioned ODB data for PDU Session Establishment.• In one example embodiment, the AMF includes a new Information Element (IE) e.g., odbExemptedlndFromAmf in SmContextCreateData based on its local configuration for ODB exempted DNN(s) information, where the AMF can indicate to the SMF that the data traffic from the DN (identified by DNN) is exempted from the ODB, so that the SMF should handle the PDU Session Establishment request without considering the OdbPacketServices in the SessionManagementSubscriptionData received from the UDM.• In one example embodiment, the new attribute "odbExemptedlndFromAmf" can be encoded as a Boolean value indicating that the requested DNN is exempted from the ODB.

[0026] Solution 2: ODB exempted DNNs information is defined in SMF, e.g., the SMF may be configured to accept PDU Session establishment for those UEs attaching from a specific area and / or at a specific timeslot even when ODB is provisioned in subscription data in UDM. In one embodiment, the local configuration for ODB exempted DNN(s) information in the SMF has higher priority than the same information received from the AMF and UDM, since the SMF is the network function managing session management to determine if the PDU session establishment can be accepted.• In one embodiment, the SMF includes a new IE, e.g., "odbExemptedlndFromSmf" in SMContextCreatedData to indicate to the AMF that the PDU session establishment is accepted based on the local configuration in the SMF even though the subscription from the UDM indicates that the PDU session establishment should be barred. This enables the AMF to be aware that this PDU session is established and is exempted from ODB control, and the AMF may use this information when handling the existing PDU Sessions, e.g., when there is an ODB subscription change, there is no need to enforce it.• In one embodiment, the new attribute "odbExemptedlndFromSmf" may be encoded as a Boolean value indicating that the requested DNN is exempted.

[0027] Solution 3: ODB exempted DNNs is provisioned by UDM. Solution 3 includes:• The UDM includes a new IE, e.g., OdbExemptedDnnsFromUdmData as type of map in the SessionManagementSubscriptionData, including a map of ODB exempted information for each of the DNNs exempted from the ODB.• Either:o The UDM includes a new IE (the same one as above), e.g., OdbExemptedDnnsFromUdmData as type of map in the AccessAndMobilitySubscriptionData, including a map of ODB exempted information for each of the DNNs exempted from the ODB. This is to enable the AMF to release the PDU Session for the DNN included in the OdbExemptedDnnsFromUdm but is removed by the operator later. The IE also indicates that the AMF is to allow the UE's registration (even when OdbPacketServices is set to "bar subscribers completely from the Packet Oriented Services") and let the SMF to determine if PDU session establishment can be accepted. OR o UDM includes a new indication in the AccessAndMobilitySubscriptionData to indicate to the AMF that the AMF is to allow the UE's registration (even when OdbPacketServices is set to "bar subscribers completely from the Packet Oriented Services") and let the SMF to determine if PDU session establishment can be accepted.In one embodiment, the new attribute "OdbExemptedDnnsFromUdmData" is a map of "odbExemptedDnnsFromUdmlnfo", containing Boolean type odbExemptedlnd, and ODB exempted conditions for this DNN when it is exempted from the ODB, for example:• time-condition: e.g., ODB is exempted from 0700 to 1700; and / or• spatial condition: ODB is exempted only when UE is in ECGI1 and NCGI2

[0028] Embodiments of Solutions 1, 2 and 3 may include the following changes in the existing 3GPP specifications: The ODB exempted information should be transferred as part of the PduSessionContext to new AMF in case of an inter AMF mobility procedures. Depending on where the ODB exempted information is defined, source AMF includes new IE, e.g., "odbExemptedlndFromSmf', "odbExemptedlndFromAmf” or “odbExemptedlndFromUdm” to new AMF.

[0029] Certain embodiments may provide one or more of the following technical advantage(s). Embodiments of the solutions disclosed herein enable a network operator to deploy local policy for ODB user to access free services. Proposed new lEs make sure the legacy end to end session management and session mobility functions work well and the principle for ODB specified in 3GPP TS 23.015 is still applied, i.e., the AMF is responsible for existing sessions handling and the SMF is responsible for new session handling.Figure 4

[0030] Figure 4 illustrates one example of a cellular communications system 400 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system 400 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC) or a similar 6thGeneration (6G) system. In this example, the RAN includes base stations 402-1 and 402-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC), controlling corresponding (macro) cells 404-1 and 404-2. The base stations 402-1 and 402-2 are generally referred to herein collectively as base stations 402 and individually as base station 402. Likewise, the (macro) cells 404-1 and 404-2 are generally referred to herein collectively as (macro) cells 404 and individually as (macro) cell 404. The RAN may also include a number of low power nodes 406-1 through 406-4 controlling corresponding small cells408-1 through 408-4. The low power nodes 406-1 through 406-4 can be small base stations (such as pico or femto base stations) or RRHs, or the like. Notably, while not illustrated, one or more of the small cells 408-1 through 408-4 may alternatively be provided by the base stations 402. The low power nodes 406-1 through 406-4 are generally referred to herein collectively as low power nodes 406 and individually as low power node 406. Likewise, the small cells 408-1 through 408-4 are generally referred to herein collectively as small cells 408 and individually as small cell 408. The cellular communications system 400 also includes a core network 410, which in the 5G System (5GS) is referred to as the 5GC. The base stations 402 (and optionally the low power nodes 406) are connected to the core network 410.

[0031] The base stations 402 and the low power nodes 406 provide service to UEs 412-1 through 412-5 in the corresponding cells 404 and 408. The UEs 412-1 through 412-5 are generally referred to herein collectively as UEs 412 and individually as UE 412.Figure 5

[0032] Figure 5 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to- point reference poi nt / i nterface. Figure 5 can be viewed as one particular implementation of the system 400 of Figure 4.

[0033] Seen from the access side the 5G network architecture shown in Figure 5 comprises a plurality of UEs 412 connected to either a RAN 402 or an Access Network (AN) as well as an AMF 500. Typically, the R(AN) 402 comprises base stations, e.g. such as eNBs or gNBs or similar. Seen from the core network side, the 5GC NFs shown in Figure 5 include a NSSF 502, an AUSF 504, a UDM 506, the AMF 500, a SMF 508, a PCF 510, and an Application Function (AF) 512.

[0034] Reference point representations of the 5G network architecture are used to develop detailed call flows in the normative standardization. The N1 reference point is defined to carry signaling between the UE 412 and AMF 500. The reference points for connecting between the AN 402 and AMF 500 and between the AN 402 and UPF 514 are defined as N2 and N3, respectively. There is a reference point, N11, between the AMF 500 and SMF 508, which implies that the SMF 508 is at least partly controlled by the AMF 500. N4 is used by the SMF 508 and UPF 514 so that the UPF 514 can be set using the control signal generated by the SMF 508, and the UPF 514 can report its state to the SMF 508. N9 is the reference point for the connection between different UPFs 514, and N14 is the reference point connecting between different AMFs 500, respectively. N15 and N7 are defined since the PCF 510 applies policy to the AMF 500 and SMF 508, respectively. N12 is required for the AMF 500 to perform authentication of the UE 412. N8 and N10 are defined because the subscription data of the UE 412 is required for the AMF 500 and SMF 508.

[0035] The 5GC network aims at separating UP and CP. The UP carries user traffic while the CP carries signaling in the network. In Figure 5, the UPF 514 is in the UP and all other NFs, i.e., the AMF 500, SMF 508, PCF 510, AF 512, NSSF 502, AUSF 504, and UDM 506, are in the CP. Separating the UP and CP guarantees each plane resource to be scaled independently. It also allows UPFs to be deployed separately from CP functions in adistributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data network for some applications requiring low latency.

[0036] The core 5G network architecture is composed of modularized functions. For example, the AMF 500 and SMF 508 are independent functions in the CP. Separated AMF 500 and SMF 508 allow independent evolution and scaling. Other CP functions like the PCF 510 and AUSF 504 can be separated as shown in Figure 5. Modularized function design enables the 5GC network to support various services flexibly.

[0037] Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF. In the CP, a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity. The UP supports interactions such as forwarding operations between different UPFs.Figure 6

[0038] Figure 6 illustrates a 5G network architecture using service-based interfaces between the NFs in the CP, instead of the point-to-point reference points / interfaces used in the 5G network architecture of Figure 5. However, the NFs described above with reference to Figure 5 correspond to the NFs shown in Figure 6. The service(s) etc. that a NF provides to other authorized NFs can be exposed to the authorized NFs through the servicebased interface. In Figure 6 the service based interfaces are indicated by the letter “N” followed by the name of the NF, e.g. Namf for the service based interface of the AMF 500 and Nsmf for the service based interface of the SMF 508, etc. The NEF 600 and the NRF 602 in Figure 6 are not shown in Figure 5 discussed above. However, it should be clarified that all NFs depicted in Figure 5 can interact with the NEF 600 and the NRF 602 of Figure 6 as necessary, though not explicitly indicated in Figure 5.

[0039] Some properties of the NFs shown in Figures 5 and 6 may be described in the following manner. The AMF 500 provides UE-based authentication, authorization, mobility management, etc. A UE 412 even using multiple access technologies is basically connected to a single AMF 500 because the AMF 500 is independent of the access technologies. The SMF 508 is responsible for session management and allocates Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF 514 for data transfer. If a UE 412 has multiple sessions, different SMFs 508 may be allocated to each session to manage them individually and possibly provide different functionalities per session. The AF 512 provides information on the packet flow to the PCF 510 responsible for policy control in order to support QoS. Based on the information, the PCF 510 determines policies about mobility and session management to make the AMF 500 and SMF 508 operate properly. The AUSF 504 supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM 506 stores subscription data of the UE 412. The Data Network (DN), not part of the 5GC network, provides Internet access or operator services and similar.

[0040] An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.Solution 1 :Figure 7A

[0041] Figure 7A illustrates a PDU session establishment procedure in accordance with one example embodiment of Solution 1. In this embodiment, ODB exempted DNNs information is defined in AMF and a new IE, which is referred to herein by exemplary name "odbExemptedlndFromAmf', is added in the PDU Session Create Context Request sent from the AMF to SMF. In one example embodiment, the odbExemptedlndFromAmf is included in the Session Management (SM) Context Create Data as shown in Table 1 below, which is one example of a new IE or row added to Table 6.1 .6.2.2-1 ("Definition of type SmContextCreateData) in 3GPP TS 29.502.Table 1

[0042] In regard to Solution 1, as shown in Figure 7A, the PDU session establishment procedure includes the following steps:• Step 1 : The AMF locally defines an ODB Exempted DNN list, e.g., based on local policy (e.g., a policy defined by the network operator). The OBD Exempted DNN list is a list of DNNs (including one or more DNNs) that are exempted from ODB.• Step 2: The AMF sends an Nsmf_PDUSession_CreateSMContext Request with odbExemptedlndFromAmf = 'true' to the SMF, thereby indicating the requesting DNN (i.e., the DNN for which PDU session establishment is requested) is an ODB exempted DNN.• Step 3: The SMF sends a Nudm_SubscriberDataManagement Request to UDM.• Step 4: The UDM sends a Nudm_SubscriberDataManagement Response with provision of odbPacketService to the SMF. In this example, obdPacketServices = ‘ALL_PACKET_SERVICES', which is a value that indicates ODB of all Packet Oriented Services for the DNN.• Step 5: The SMF decides to accept the requested PDU session establishment for the DNN, even though obdPacketServices = ‘ALL_PACKET_SERVICES', because the requested DNN's odbExemptedlndFromAmf = 'true' in step 2.• Step 6: The SMF sends Nsmf_PDUSession_CreateSMContext Accept to the AMF.

[0043] Note that, if the requesting DNN is not an ODB exempted DNN, then in step 2, obdExemptedlndFromAmf would alternatively be set to 'false' or the information is omitt4ed in Nsmf_PDUSession_CreateSMContext Request message, in which case the SMF would decide to reject the requested PDU session establishment for the DNN because obdPacketServices = 'ALL_PACKET_SERVICES' and the requested DNN's odbExemptedlndFromAmf = 'false'.Solution 2:Figure 7B

[0044] Figure 7B illustrates a PDU session establishment procedure in accordance with one example embodiment of Solution 2. In this embodiment, ODB exempted DNN information is defined in SMF and a new IE, which is referred to herein by exemplary name "odbExemptedlndFromSmf', is added to PDU Session Create Context Response sent from the SMF to the AMF. In one example embodiment, the odbExemptedlndFromSmf IE is include the SM Context Created Data as shown in Table 2 below, which is one example of a new IE or row added to Table 6.1.6.2.3-1 ("Definition of type SmContextCreatedData) in 3GPP TS 29.502.Table 2

[0045] In regard to Solution 2, as shown in Figure 7B, the PDU session establishment procedure includes the following steps:• Step 7: SMF locally defines an ODB Exempted DNN list, e.g., based on local policy (e.g., a policy defined by the network operator). The OBD Exempted DNN list is a list of DNNs (including one or more DNNs) that are exempted from ODB.• Step 8: The AMF sends an Nsmf_PDUSession_CreateSMContext Request to the SMF.• Step 9: The SMF sends an Nudm_SubscriberDataManagement Request to the UDM.• Step 10: The UDM sends Nudm_SubscriberDataManagement Request with provision of odbPacketService to the SMF. In this example, obdPacketServices = 'ALL_PACKET_SERVICES', which is a value that indicates ODB of all Packet Oriented Services for the DNN.• Step 11 : The SMF decides to accept the requested PDU session establishment for the requested DNN, even though obdPacketServices = ‘ALL_PACKET_SERVICES', because the requested DNN is defined as an ODB exempted DNN in SMF in step 7.• Step 12: The SMF sends Nsmf_PDUSession_CreateSMContext Accept with odbExemptedlndFromSmf = 'true' to AMF indicating the requested DNN is an ODB exempted DNN defined in the SMF.

[0046] Note that, if the requesting DNN is not an ODB exempted DNN as defined locally in the SMF, then in step 11, the SMF would alternatively decide to reject the requested PDU session establishment for the DNN because obdPacketServices = ‘ALL_PACKET_SERVICES’ and the requested DNN is not an OBD exempted DNN defined in the SMF. Then, in step 12, an Nsmf_PDUSession_CreateSMContext Reject would be sent to the AMF.Solution 3:Figure 7C

[0047] Figure 7C illustrates a PDU session establishment procedure in accordance with one example embodiment of Solution 3. In this embodiment, ODB exempted DNN information is defined in the UDM and a new IE, which is referred to herein by exemplary name "OdbExemptedDnnsFromUdm”, is added in the SessionManagementSubscriptionData as shown in Table 3 below, which is one example of new lEs or rows added to Table 6.1 .6.2.8-1 of 3GPP TS 29.503. Tables 4 and 5 below provide further details regarding an example embodiment of the odbExemptedDnnsFromUdmlnfo of Table 3.Table 3Table 4: Definition of type OdbExemptedDnnsFromUdmlnfoTable 5: Definition of type OdbExemptedConditions

[0048] Solution 3 also proposes to include a new IE OdbExemptedDnnsFromUdmData as type of map in the AccessAndMobilitySubscriptionData (see, e.g., Table 6) or a new indication OdbExemptedlndFromUdmData in the AccessAndMobilitySubscriptionData (see, e.g., Table 7), in 3GPP TS 29.503 Table 6.1.6.2.4 Type: AccessAndMobilitySubscriptionData.Table 6: New IES for Table 6.1.6.2.4-1 of 3GPP TS 29.503 (Definition of type AccessAnd Mobi I itySu bscri ption Data)Table 7: New IES for Table 6.1.6.2.4-1 of 3GPP TS 29.503 (Definition of type AccessAnd Mobi I itySu bscri ption Data)

[0049] In regard to Solution 3, as shown in Figure 73, the PDU session establishment procedure includes the following steps:• Step 13: The UDM locally defines an ODB Exempted DNN list with some conditions. The OBD Exempted DNN list is a list of DNNs (including one or more DNNs) that are exempted from ODB.• Step 14 and Step 15 are part of AMF procedure, registration, or SDM notification. The change enables the AMF to know the ODB exempted DNNs and perform proper handling in UE registration or SDM notification procedure. o Step 14: The UDM sends the AMF AccessAndMobilitySubscriptionData with the same IE as the SMF in step 18, i.e., OdbExemptedDnnsFromUdmData. o Step 15: The UDM sends the AMF AccessAndMobilitySubscriptionData with indication odbExemptedlndFromUdmData(Dnnx, true).• Step 16: The AMF sends Nsmf_PDUSession_CreateSMContext Request to the SMF.• Step 17: The SMF sends Nudm_SubscriberDataManagement Request to the UDM.• Step 18: The UDM sends Nudm_SubscriberDataManagement Response with provision of odbPacketService and includes IE odbExemptedDnnsFromUdm Data in SessionManagementSubscriptionData, including odbExemptedlnd = true, DnnConfiguration and odbExemptedConditionData.• Step 19: The SMF decides to accept session establishment because of step 18 indicating the requesting DNN is ODB exempted DNN.• Step 20: The SMF sends Nsmf_PDUSession_CreateSMContext Accept to the AMF.

[0050] Embodiments related to inter-AMF mobility, which are applicable to Solutions 1, 2, and 3 above, will now be described. In one embodiment, a new IE is proposed to be added, and applicable for all solutions mentioned above. E.g., "odbExemptedDNNsFromAmf”, "odbExemptedlndFromSmf”, or"odbExemptedlndFromUdm” in TS 29.518 clause 6.1.6.2.37-1 pduSessionContext. This is used in inter AMF mobility procedure to transfer the existing session's ODB exempted information to new AMF. See Table 8 below.Table 8: New IE for Table 6.1.6.2.37-1 (Definition of type pduSessionContext) in 3GPP TS 29.518Figures 8A and 8B

[0051] In this regard, Figures 8A and 8B illustrate one example embodiment of an inter-AMF mobility procedure in accordance with the present disclosure. The steps of the procedure are as follows:• Step 1 : With Solution 1, source AMF stores Exempted ODB info in odbExemptedDnnsFromAmf during session establishment.• Step 2: With Solution 2, source AMF stores Exempted ODB info in odbExemptedDnnsFromSmf during session establishment.• Step 3: With Solution 3, source AMF stores Exempted ODB info in odbExemptedDnnsFromUdm during session establishment. Note that not all of steps 1, 2, and 3 have to be performed. Any one or more of them may be performed.• Step 4: Source Radio Access Network (RAN) node (e.g., Source NG-RAN node in the illustrated example) sends a Handover Required message to the source AMF.• Step 5: The source AMF sends an Namf_Communication_CreateUEContext Request with Boolean type odbExemptedlndFromAmf or odbExemptedlndFromSmf or odbExemptedlndFromUdm in pduSessionContext to a Target AMF.• Step 6: The Target AMF and the SMF perform an Nsmf_PDUSession_UpdateSMContext procedure.• Step 7: The Target RAN node (i.e., target NG RAN node in the illustrated example) and the Target AMF perform Handover procedures.• Step 8: The Target AMF and the SMF performs the Nsmf_PDUSession_UpdateSMContext procedure.• Step 9: The Target AMF sends an Namf_Communication_CreateUEContext Response to the Source AMF.Figure 9

[0052] Figure 9 is a schematic block diagram of a network node 900 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The network node 900 may be, for example, a base station 402 or 406 or a network node that implements all or part of the functionality of the base station 402 or gNB described herein, or a core network node (e.g., an SMF, AMF, or UDM, as described herein). As illustrated, the network node 900 includes a control system 902 that includes one or more processors 904 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and / or the like), memory 906, and a network interface 908. The one or more processors 904 are also referred to herein as processing circuitry. In addition, if the network node 900 is a radio access node (e.g., a base station 402, gNB, or network node that implements at least some of the functionality of the base station 402 or gNB), the network node 900 may include one or more radio units 910 that each includes one or more transmitters 912 and one or more receivers 914 coupled to one or more antennas 916. The radio units 910 may be referred to or be part of radio interface circuitry. In some embodiments, the radio unit(s) 910 is external to the control system 902 and connected to the control system 902 via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s) 910 and potentially the antenna(s) 916 are integrated together with the control system 902. The one or more processors 904 operate to provide one or more functions of the network node 900 as described herein (e.g., one or more functions of an AMF, SMF, or UDM described herein). In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 906 and executed by the one or more processors 904.Figure 10

[0053] Figure 10 is a schematic block diagram that illustrates a virtualized embodiment of the network node 900 according to some embodiments of the present disclosure. Again, optional features are represented by dashed boxes. As used herein, a "virtualized” network node is an implementation of the network node 900 in which at least a portion of the functionality of the network node 900 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, if the network node 900 is a radio access node, the network node 900 may include the control system 902 and / or the one or more radio units 910, as described above. The control system 902 may be connected to the radio unit(s) 910 via, for example, an optical cable or the like. The network node 900 includes one or more processing nodes 1000 coupled to or included as part of a network(s) 1002. If present, the control system 902 or the radio unit(s) are connected to the processing node(s) 1000 via the network 1002. Each processing node 1000 includes one or more processors 1004 (e.g., CPUs, ASICs, FPGAs, and / or the like), memory 1006, and a network interface 1008.

[0054] In this example, functions 1010 of the network node 900 described herein (e.g., one or more functions of an AMF, SMF, or UDM described herein) are implemented at the one or more processing nodes 1000 or distributed across the one or more processing nodes 1000 and the control system 902 and / or the radio unit(s) 910 in any desired manner. In some particular embodiments, some or all of the functions 1010 of the network node 900 described herein are implemented as virtual components executed by one or more virtual machines implemented in avirtual environment(s) hosted by the processing node(s) 1000. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 1000 and the control system 902 is used in order to carry out at least some of the desired functions 1010. Notably, in some embodiments, the control system 902 may not be included, in which case the radio unit(s) 910 communicate directly with the processing node(s) 1000 via an appropriate network interface(s).

[0055] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the network node 900 or a node (e.g., a processing node 1000) implementing one or more of the functions 1010 of the network node 900 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).Figure 11

[0056] Figure 11 is a schematic block diagram of the network node 900 according to some other embodiments of the present disclosure. The network node 900 includes one or more modules 1100, each of which is implemented in software. The module(s) 1100 provides the functionality of the network node 900 described herein. This discussion is equally applicable to the processing node 1000 of Figure 10 where the modules 1100 may be implemented at one of the processing nodes 1000 or distributed across multiple processing nodes 1000 and / or distributed across the processing node(s) 1000 and the control system 902.Figure 12

[0057] Figure 12 is a schematic block diagram of a UE 412 according to some embodiments of the present disclosure. As illustrated, the UE 412 includes one or more processors 1202 (e.g., CPUs, ASICs, FPGAs, and / or the like), memory 1204, and one or more transceivers 1206 each including one or more transmitters 1208 and one or more receivers 1210 coupled to one or more antennas 1212. The transceiver(s) 1206 includes radio-front end circuitry connected to the antenna(s) 1212 that is configured to condition signals communicated between the antenna(s) 1212 and the processor(s) 1202, as will be appreciated by on of ordinary skill in the art. The processors 1202 are also referred to herein as processing circuitry. The transceivers 1206 are also referred to herein as radio circuitry. In some embodiments, the functionality of the UE 412 described above may be fully or partially implemented in software that is, e.g., stored in the memory 1204 and executed by the processor(s) 1202. Note that the UE 412 may include additional components not illustrated in Figure 12 such as, e.g., one or more user interface components (e.g., an input / output interface including a display, buttons, a touch screen, a microphone, a speaker®, and / or the like and / or any other components for allowing input of information into the UE 412 and / or allowing output of information from the UE 412), a power supply (e.g., a battery and associated power circuitry), etc.

[0058] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the UE 412 according to any of theembodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).Figure 13

[0059] Figure 13 is a schematic block diagram of the UE 412 according to some other embodiments of the present disclosure. The UE 412 includes one or more modules 1300, each of which is implemented in software. The module(s) 1300 provides the functionality of the UE 412 (or UE) described herein.EMBODIMENTS

[0060] Some of the embodiments disclosed above may be summarized in the following enumerated manner:1 . A method performed by first core network node in a core network of a cellular communications system, the method comprising: storing (Fig. 7A, step 1; Fig. 7B, step 7; Fig. 7C, step 13) information that indicates one or more Data Network Names, DNNs, that are exempted from Operator Defined Barring, ODB; and using the information that indicates the one or more DNNs that are exempted from ODB to perform one or more actions related to Protocol Data Unit, PDU, establishment or session mobility.2. The method of embodiment 1, wherein the first core network node is an Access and Mobility Management Function, AMF.3. The method of embodiment 2, wherein using the information that indicates the one or more DNNs that are exempted from ODB to perform one or more actions related to PDU establishment or session mobility comprises: sending (Fig. 7A, step 2) to a Session Management Function, SMF, a request to create a session management context for a PDU session for which establishment is requested, the request comprising: information that indicates a DNN for which establishment of the PDU session is requested, wherein the DNN is one of the one or more DNNs that are exempted from ODB; and information that indicates that the DNN is exempted from ODB.4. The method of embodiment 3, wherein the DNN is exempted from barring even if subscriber data from a UDM indicates that OBD applies to the DNN.5. The method of embodiment 3 or 4, further comprising receiving (Fig. 7A, step 6) session management context create accept message from the SMF.6. The method of embodiment 1, wherein the first core network node is a Session Management Function, SMF.7. The method of embodiment 6, further comprising: receiving (Fig. 7B, step 8) request to create a session management context for a PDU session for which establishment is requested, wherein the request comprises information that indicates a DNN for which establishment of the PDU session is requested and the DNN is one of the one or more DNNs that are exempt from ODB (or the establishment request indicates that the establishment should be rejected due to ODB); wherein using the information (e.g., which is locally stored in the SMF) that indicates the one or more DNNs that are exempted from ODB to perform one or more actions related to PDU establishment or session mobility comprises determining (Fig. 7B, step 11) to accept establishment of the PDU session based on information that indicates that the DNN for which establishment of the PDU session is requested is exempt from ODB.8. The method of embodiment 7, further comprising obtaining (Fig. 7B, steps 9 and 10) subscriber data management data for the DNN for which establishment of the PDU session is requested, wherein the subscriber data management data comprises information that indicates that ODB is applicable for the DNN; wherein determining (Fig. 7B, step 11) to accept establishment of the PDU session comprises determining (Fig. 7B, step 11) to accept establishment of the PDU session, even though ODB is applicable for the DNN, because the DNN is exempt from ODB.9. The method of embodiment 7 or 8, further comprising sending (Fig. 7B, step 12) session management context create accept message to the AMF, the accept message comprising an indication flag that indicates that the acceptance is due to ODB being exempted.10. The method of embodiment 1, wherein the first core network node is a Unified Data Management, UDM.11. The method of embodiment 10, wherein using the information that indicates the one or more DNNs that are exempted from ODB to perform one or more actions related to PDU establishment or session mobility comprises, as part of an AMF related UE registration or SDM notification procedure, sending (Fig. 70, step 14 or step 15), to an AMF, information that indicates that a DNN, from among the one or more DNNs, is exempted from ODB.12. The method of embodiment 11, wherein sending (Fig. 70, step 14 or step 15), to the AMF, the information that indicates that the DNN is exempted from ODB comprises sending (Fig. 70, step 14 or 15), to the AMF, access and mobility subscription data comprising information that indicates that the ODB is applicable for the DNN and the information that indicates that the DNN is nevertheless exempted from ODB.13. The method of embodiment 12, wherein the access and mobility subscription data further comprises information that indicates one or more conditions (e.g., one or more time and / or location based conditions) under which the DNN is exempted from ODB.14. The method of any of embodiments 10 to 13, wherein using the information that indicates the one or more DNNs that are exempted from ODB to perform one or more actions related to PDU establishment or session mobility comprises: receiving (Fig. 7C, step 17), from an SMF as part of a PDU session establishment procedure, a subscriber data management request for the DNN; and sending (Fig. 70, step 18), to the SMF, session management subscription data for the DNN comprising information that indicates that the DNN is exempted from ODB.15. A network node adapted to perform the method of any of embodiments 1 to 14.16. A method performed by a Session Management Function, SMF, the method comprising: as part of a Protocol Data Unit, PDU, session establishment procedure: receiving (Fig. 7A, step 2; Fig. 7B, step 8; Fig. 70, step 16) a request to create a session management context for the PDU session, wherein the request comprises information that indicates a Data Network Name, DNN, for which establishment of the PDU session is requested; obtaining (Fig. 7A, step 2; Fig. 7B, step 7; Fig. 70, step 18), either from local storage or from another network node, information that indicates that the DNN is exempted from Operator Determined Barring, ODB; and determining (Fig. 7A, step 5; Fig. 7B, step 11; Fig. 70, step 19) to accept the request to create the session management context for the PDU session based on the information that indicates that the DNN is exempted from ODB (e.g., even if subscription data obtained from a UDM indicates that ODB is applicable for the DNN).17. A network node adapted to perform the method of embodiment 16.18. A method comprising any one or more of the following:• at a source AMF for an inter-AMF mobility procedure: o receiving (Fig. 8B, step 4), from a source RAN node, a handover required message; o sending (Fig. 8B, step 5), to a target AMF for the inter-AMF mobility procedure, a request to create a UE context, the request comprising information that indicates that an associated DNN is exempted from ODB;• at the target AMF:o receiving (Fig. 8B, step 5) the request to create the UE context; o communicating (Fig. 8B, step 6) with an SMF to update a session management context of PDU session to which the handover applies.

[0061] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.

[0062] While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

Claims

CLAIMSWhat is claimed is:1 . A method performed by first core network node in a core network of a cellular communications system, the method comprising: storing (Fig. 7A, step 1; Fig. 7B, step 7; Fig. 70, step 13) information that indicates one or more Data Network Names, DNNs, that are exempted from Operator Defined Barring, ODB; and using the information that indicates the one or more DNNs that are exempted from ODB to perform one or more actions related to Protocol Data Unit, PDU, establishment or session mobility.

2. The method of claim 1, wherein the first core network node is an Access and Mobility Management Function, AMF.

3. The method of claim 2, wherein using the information that indicates the one or more DNNs that are exempted from ODB to perform one or more actions related to PDU establishment or session mobility comprises: sending (Fig. 7A, step 2) to a Session Management Function, SMF, a request to create a session management context for a PDU session for which establishment is requested, the request comprising: information that indicates a DNN for which establishment of the PDU session is requested, wherein the DNN is one of the one or more DNNs that are exempted from ODB; and information that indicates that the DNN is exempted from ODB.

4. The method of claim 3, wherein the DNN is exempted from barring even if subscriber data from a UDM indicates that OBD applies to the DNN.

5. The method of claim 3 or 4, further comprising receiving (Fig. 7A, step 6) session management context create accept message from the SMF.

6. The method of claim 1, wherein the first core network node is a Session Management Function, SMF.

7. The method of claim 6, further comprising: receiving (Fig. 7B, step 8) request to create a session management context for a PDU session for which establishment is requested, wherein the request comprises information that indicates a DNN for which establishment of the PDU session is requested and the DNN is one of the one or more DNNs that are exempt from ODB (or the establishment request indicates that the establishment should be rejected due to ODB);wherein using the information (e.g., which is locally stored in the SMF) that indicates the one or more DNNs that are exempted from ODB to perform one or more actions related to PDU establishment or session mobility comprises determining (Fig. 7B, step 11) to accept establishment of the PDU session based on information that indicates that the DNN for which establishment of the PDU session is requested is exempt from ODB.

8. The method of claim 7, further comprising obtaining (Fig. 7B, steps 9 and 10) subscriber data management data for the DNN for which establishment of the PDU session is requested, wherein the subscriber data management data comprises information that indicates that ODB is applicable for the DNN; wherein determining (Fig. 7B, step 11) to accept establishment of the PDU session comprises determining (Fig. 7B, step 11) to accept establishment of the PDU session, even though ODB is applicable for the DNN, because the DNN is exempt from ODB.

9. The method of claim 7 or 8, further comprising sending (Fig. 7B, step 12) session management context create accept message to the AMF, the accept message comprising an indication flag that indicates that the acceptance is due to ODB being exempted.

10. The method of claim 1, wherein the first core network node is a Unified Data Management, UDM.11 . The method of claim 10, wherein using the information that indicates the one or more DNNs that are exempted from ODB to perform one or more actions related to PDU establishment or session mobility comprises, as part of an AMF related UE registration or SDM notification procedure, sending (Fig. 70, step 14 or step 15), to an AMF, information that indicates that a DNN, from among the one or more DNNs, is exempted from ODB.

12. The method of claim 11, wherein sending (Fig. 70, step 14 or step 15), to the AMF, the information that indicates that the DNN is exempted from ODB comprises sending (Fig. 70, step 14 or 15), to the AMF, access and mobility subscription data comprising information that indicates that the ODB is applicable for the DNN and the information that indicates that the DNN is nevertheless exempted from ODB.

13. The method of claim 12, wherein the access and mobility subscription data further comprises information that indicates one or more conditions (e.g., one or more time and / or location based conditions) under which the DNN is exempted from ODB.

14. The method of any one of claim 10 to 13, wherein using the information that indicates the one or more DNNs that are exempted from ODB to perform one or more actions related to PDU establishment or session mobility comprises:receiving (Fig. 7C, step 17), from an SMF as part of a PDU session establishment procedure, a subscriber data management request for the DNN; and sending (Fig. 7C, step 18), to the SMF, session management subscription data for the DNN comprising information that indicates that the DNN is exempted from ODB.

15. A network node adapted to perform the method of any one of claim 1 to 14.

16. A method performed by a Session Management Function, SMF, the method comprising: as part of a Protocol Data Unit, PDU, session establishment procedure: receiving (Fig. 7A, step 2; Fig. 7B, step 8; Fig. 7C, step 16) a request to create a session management context for the PDU session, wherein the request comprises information that indicates a Data Network Name, DNN, for which establishment of the PDU session is requested; obtaining (Fig. 7A, step 2; Fig. 7B, step 7; Fig. 7C, step 18), either from local storage or from another network node, information that indicates that the DNN is exempted from Operator Determined Barring, ODB; and determining (Fig. 7A, step 5; Fig. 7B, step 11; Fig. 70, step 19) to accept the request to create the session management context for the PDU session based on the information that indicates that the DNN is exempted from ODB (e.g., even if subscription data obtained from a UDM indicates that ODB is applicable for the DNN).

17. A network node adapted to perform the method of claim 16.

18. A method comprising any one or more of the following:• at a source AMF for an inter-AMF mobility procedure: o receiving (Fig. 8B, step 4), from a source RAN node, a handover required message; o sending (Fig. 8B, step 5), to a target AMF for the inter-AMF mobility procedure, a request to create a UE context, the request comprising information that indicates that an associated DNN is exempted from ODB;• at the target AMF: o receiving (Fig. 8B, step 5) the request to create the UE context; o communicating (Fig. 8B, step 6) with an SMF to update a session management context of PDU session to which the handover applies.

Images