Optimizing user device operations by conditionally setting multiple policies on information elements

By sending policy rules containing location and time information elements in the network function, optimizing the operation of user equipment in the wireless communication network, solving the shortcomings in the selection of network slicing, wireless access technology and access network in the prior art, realizing the implementation of the implementation of the following requirements More efficient resource utilization and service quality control.

CN118945818APending Publication Date: 2024-11-12HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410538151.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2019-06-17
Filing Date
2019-06-19
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

The prior art has failed to fully optimize the operation of user equipment in wireless communication networks, especially under the background data transmission strategy, and lacks effective control mechanisms to select network slices, wireless access technology and access networks, and lacks QoS-enabled Packet filter mechanism.

Method used

Send policy rules at network function (NF), including location and time information elements as conditions, control how user equipment (UE) exchanges packets, ensures that UE performs packet exchanges according to the rules when the rule conditions are met or not met, and if the rule conditions are not met, and if it is not met, Block or allow packet exchange when conditions are performed.

Benefits of technology

By dynamically controlling the packet switching strategy of the UE, the resource utilization and service quality of the wireless network are optimized, the flexibility and efficiency of the network are improved, and the reliability of data transmission and on-demand billing are ensured.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945818A_ABST
    Figure CN118945818A_ABST
Patent Text Reader

Abstract

A method for optimizing operation of a user equipment (UE) in a wireless communication network. The method is performed at a network function (NF), comprising: transmitting at least one rule of at least one policy over the network, the rule controlling how the UE exchanges packets over the network and containing information conditioned by at least one information element, such that: when the at least one rule contains information conditioned by at least one information element and the UE does not satisfy the information contained in the at least one rule, the UE cannot exchange packets according to the at least one rule; when the at least one rule contains information under the condition of at least one information element and the UE satisfies the information contained in the at least one rule, the UE exchanges packets according to any constraint contained in the at least one rule; when there is no information corresponding to the at least one information element in the at least one rule, the UE exchanges packets according to any constraints contained in the at least one rule.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application. The application number of the original application is 201980042106.9, and the original application date is June 19, 2019. The entire contents of the original application are incorporated into this application by reference.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. non-provisional patent application No. 16 / 443,450, filed on June 17, 2019, which claims priority to U.S. provisional patent application serial number 62 / 688,996, filed on June 22, 2018, the entire contents of which are incorporated herein by reference. Technical Field

[0004] The present disclosure relates to wireless communications, and certain embodiments or aspects relate to optimizing operation of user equipment in a wireless network in accordance with the present disclosure. Background Art

[0005] Network slicing is a technology that aims to improve network resource utilization efficiency and deployment flexibility and support the rapid growth of OTT (over-the-top)

[0006] The third generation partnership project (3GPP) is committed to developing comprehensive network slicing related standards in various working groups (including but not limited to the SA2 (Architecture) working group responsible for the overall system architecture).

[0007] The 3GPP SA2 working group is working on the specifications of the 5G core (5GC) architecture, including network slicing as a feature. Its technical specification (TS) TS-503 defines the policy and charging control framework for 5G systems.

[0008] One mechanism proposed to support the policy and charging control framework is a network data analytics function (NWDAF), such as the NWDAF discussed in U.S. Patent Application No. 15 / 898,444, filed on February 17, 2018 by DAO, Ngoc Dung, et al., entitled “NETWORK POLICY OPTIMIZATION SYSTEM AND METHOD,” which is incorporated herein by reference in its entirety. The NWDAF is proposed to optimize the operation of 5G networks, such as traffic routing, mobility management, and interaction with control plane (CP) functions (CPF), including but not limited to session management functions (SMF) 92( Figure 2 ), policy and control function (PCF) 201 (Figure

[0009] 2) Access and mobility management function (AMF) 90( Figure 2 ), network repository function (NRF) 98 ( Figure 2 ), and / or operation, administration and maintenance (OAM) functions, and / or third-party functions. However, this mechanism does not fully address the user equipment (UE) 52 ( Figure 1 )'s operation is affected.

[0010] PCF 201 can manage and / or optimize one or more policies for controlling UE operation, including but not limited to, policies that allow UE 52 to select one or more routes through which to send and / or receive data (including but not limited to UE route selection policy (URSP)), policies that allow UE 52 to discover and / or select a suitable access network (AN) (including but not limited to access network discovery and selection policy (ANDSP)), policies that allow UE 52 to send a large amount of data to an application server (AS) in a data network 88 (DN) (including but not limited to UE background data transfer policy (UBDTP)), policies that allow UE 52 to select one or more specific routes through which to send data of multiple quality of service (QoS) flows and / or data of QoS flows of a common protocol data unit (PDU) session to the AS (including but not limited to access traffic steering, switching and splitting (ATSSS) policy), policies that allow UE 52 to send and / or receive data packets with predefined QoS parameters, and / or policies (including but not limited to spending policies) that allow UE 52 to send and / or receive data packets with specific billing rates and / or consumption limits.

[0011] The URSP may control how the UE 52 determines how to route outgoing traffic (for example, but not limited to, by establishing a new PDU session, routing to an established PDU session, or offloading to a non-3GPP AN outside a PDU session) and / or how to select a network slice identified by one or more single network slice selection assistance information (S-NSSAI, collectively referred to as NSSAI).

[0012] The ANDSP may control how the UE 52 selects a non-3GPP AN and / or decide how to route traffic between the selected 3GPP AN and the non-3GPP AN.

[0013] UBDTP is intended to control how UE 52 sends background data collected by UE 52 to AS. Background data is data sent to AS but with low or no urgency, so background data does not need to be sent immediately. On the other hand, the volume of background data may be very large.

[0014] One non-limiting example of background data is in the context of a vehicle to network (V2X) UE 52. Such a V2X UE 52 may collect sensor data for fault diagnosis and / or onboard camera photos of road conditions that may be used to build a 2D or 3D model of the road.

[0015] UBDTP is based on the proposition that the UE 52 can send background data when the network load is low.

[0016] Typically, an application function (AF) 104 ( Figure 3 ) can negotiate with the network to determine the time window and location where background data can be transmitted. In this way, AF 104 can use a dedicated solution to send the time window to UE 52.

[0017] Such a solution may involve extensive signaling and network load for conveying this information to the UE 52 .

[0018] Alternatively, it has been proposed that the network may interact directly with the UE 52 in order to communicate UBDTP to the UE 52. This proposal is promising, but lacks information about the mechanism that controls how the UE 52 will select a network slice, and / or a radio access technology (RAT), and / or an access network (AN), and which packet filter will be used for QoS support. In addition, there is currently no method that allows the mobile network to perform UBDTP.

[0019] The ATSSS policy controls how the UE 52 can use multiple ANs to establish a PDU session. The AN can be a non-3GPP AN and / or a 3GPP AN, where the non-3GPP AN is, for example, but not limited to, a Wi-Fi AN or a fixed AN, and the 3GPP AN is, for example, but not limited to, a 4G and / or 5G wireless AN (RAN or (R) AN) 84 ( Figure 2 ). When a PDU session is allowed to send PDUs across multiple ANs, a packet processing entity in UE 52 may select a specific AN to send uplink (UL) packets for one or more QoS flows. In some examples, the packet processing entity may send a certain proportion of packets to one AN and another proportion of packets to another AN.

[0020] A QoS policy can include one or more QoS flows and support guaranteed flow bit rate (GBR).

[0021] QoS flows that involve GBR, QoS flows that do not involve GBR, and / or reflective QoS. QoS flows represent the finest granularity for QoS differentiation within a PDU session.

[0022] and is associated with a QoS flow identifier (QFI). User plane (UP) 106 traffic with a common QFI within a PDU session is subject to the same traffic forwarding (including but not limited to scheduling and / or admission thresholds), which is understood and referred to as a service. A QoS flow is characterized by three elements, namely:

[0023] ● QoS profile, provided by SMF 92 to AN 84 via AMF 90;

[0024] ● one or more QoS rules provided by the SMF 92 to the UE 52 via the AMF 90 and / or derived by the UE 52 using reflective QoS control; and

[0025] ● Information about UP traffic is sent by SMF 92 to UP function (UPF) 86 to enable classification, bandwidth enforcement, and marking. Figure 3 ), including but not limited to:

[0026] ● One or more UL packet detection rules (PDRs) provided by SMF 92, including a UL packet filter group of a service data flow (SDF) template,

[0027] ● One or more downlink (DL) PDRs, DL packet filter groups containing SDF templates and / or reflective QoS indications,

[0028] ● The PDR priority value of each UL PDR and / or DL ​​PDR may be set to a priority value of a policy and charging control (PCC) rule in some examples.

[0029] ● QoS related rules, and

[0030] ●The corresponding packet marking information includes but is not limited to QFI and / or transport level packet marking value, which in some examples may be a differentiated services code point (DSCP) of an outer IP header.

[0031] In a 5G network, a (typically non-GBR) QoS flow associated with a default QoS rule is established for a PDU session and remains established throughout the lifetime of the PDU session to provide connectivity to the UE 52.

[0032] Therefore, there may be a need for mechanisms for optimizing operation of a UE 52 in a wireless communication network, including but not limited to operation under a background data transfer policy, that are not subject to one or more limitations of the prior art.

[0033] This background information is intended to provide information that may be relevant to the present invention. It is not necessarily acknowledged, nor should it be construed, that any of the foregoing information constitutes prior art against the present invention. Summary of the invention

[0034] It is an object of the present disclosure to obviate or mitigate at least one disadvantage of the prior art.

[0035] According to the first broad aspect of the present disclosure, a method for optimizing the operation of user equipment in a wireless network is disclosed, comprising the following actions at a NF of the network: sending at least one rule of at least one policy on the network, the at least one rule controlling how UE exchanges packets on the network and containing information conditioned on at least one information element, so that: when the information conditioned on at least one information element is contained in the at least one rule and the UE does not satisfy the information contained in the at least one rule, the UE cannot exchange packets according to the at least one rule; when the information conditioned on the at least one information element is contained in the at least one rule and the UE satisfies the information contained in the at least one rule, the UE can exchange packets according to any constraints contained in the at least one rule; and when there is no information corresponding to the at least one information element in the at least one rule, the UE can exchange packets according to any constraints contained in the at least one rule.

[0036] In an embodiment, the at least one information element may include a location element. In an embodiment, the location element may include at least one of: a geographic location specified by a 2D and / or 3D coordinate system, a geographic location specified by an identifier of a geographic area of ​​a mapping system, a RAN address, a cell identifier, a TAI, a registration area identifier, and / or an indication that the at least one rule is always considered.

[0037] In an embodiment, the at least one information may include a time element. In an embodiment, the time element may include at least one of the following: a time of day, a date, a day of the week, a day of the month, a month, a year, a time period (specifying at least one of the above time elements to start the time period and / or specifying at least one of the above time elements to end the time period), a cycle, and / or an indication that the at least one rule is always considered.

[0038] In an embodiment, the at least one policy includes at least one of the following: URSP, ANDSP, UBDTP, ASSSS policy, QoS policy, access and mobility management policy, and / or expenditure policy.

[0039] In an embodiment, the at least one information element mentioned above may be included in at least one of the components of the URSP rule and / or the routing descriptor of the URSP rule, the component comprising at least one of the following: SSC mode, network slice selection, DNN selection, non-seamless offload indication, and / or access type preference.

[0040] In an embodiment, the UBDTP policy may specify at least one of the following: a UBDTP identification phase, used to identify whether at least one UE is authorized to use the UBDTP service; a UBDTP rule definition phase, used to define at least one rule containing information conditioned on at least one information element, and the at least one rule may include at least one of the UBDTP rule and / or the URSP rule; a UBDTP AS configuration phase, used to identify the AS associated with at least one UE receiving the UBDTP service; and / or a UBDTP operation phase, used to provide UBDTP services to background data according to at least one rule defined in the UBDTP rule definition phase, the background data being transmitted by at least one UE to the AS associated with the at least one UE.

[0041] In an embodiment, the QoS policy may include at least one of the following: a QoS profile of a QoS flow, a QoS rule, and / or at least one QoS-related information set, the QoS profile being used to be exchanged between the SMF and the RAN node subject to the above-mentioned at least one information element, the QoS rule being used to be exchanged between the SMF and at least one UE subject to the above-mentioned at least one information element, and the at least one QoS-related information set being used to be exchanged between the SMF and the UPF subject to the above-mentioned at least one information element.

[0042] In an embodiment, the access and mobility management policy may include at least one TAI, which is used to be exchanged between the NF and the operator through the AMF subject to the above-mentioned at least one information element.

[0043] In an embodiment, the above-mentioned NF may include a PCF.

[0044] In an embodiment, the above method may further include an action: including an indication specifying whether the above at least one rule will be strictly enforced. In an embodiment, when the above indication specifies that the above at least one rule will be strictly enforced, if the UE does not meet the information contained in the above at least one rule, the UE cannot exchange packets according to the above at least one rule. In an embodiment, when the above at least one indication specifies that the above at least one rule will not be strictly enforced, even if the UE does not meet the information contained in the above at least one rule, the UE can exchange packets according to any constraints contained in the above at least one rule. In an embodiment, if the above at least one rule is taken into account, different criteria may be applied to packets exchanged according to the above at least one rule. In an embodiment, the above different criteria may be at least one of different billing rates and / or different QoS.

[0045] According to a second aspect of the present disclosure, a NF of a wireless communication network is disclosed, the NF comprising: a processor; and a non-temporary memory for storing instructions, when the instructions are executed by the processor, the NF optimizes the operation of UEs in the network by: sending at least one rule of at least one policy on the network, the at least one rule controlling how UEs exchange packets on the network and containing information conditioned on at least one information element, so that: when the information conditioned on at least one information element is contained in the at least one rule and the UE does not satisfy the information contained in the at least one rule, the UE cannot exchange packets according to the at least one rule; when the information conditioned on the at least one information element is contained in the at least one rule and the UE satisfies the information contained in the at least one rule, the UE can exchange packets according to any constraints contained in the at least one rule; and when there is no information corresponding to the at least one information element in the at least one rule, the UE can exchange packets according to any constraints contained in the at least one rule.

[0046] The above describes various embodiments in conjunction with various aspects of the present disclosure, and each embodiment can be implemented based on these aspects. It will be appreciated by those skilled in the art that the embodiments can be implemented in conjunction with the aspects described therewith, but can also be implemented together with other embodiments of the aspect. It will be apparent to those skilled in the art when the embodiments are mutually exclusive or incompatible with each other. It will be apparent to those skilled in the art that some embodiments can be described with respect to one aspect, but can also be applied to other aspects.

[0047] According to another broad aspect of the present invention, a method for optimizing the operation of a user equipment (UE) in a wireless communication network is provided. The method is performed at a network function (NF), comprising: sending at least one rule of at least one policy on the network, the at least one rule controlling how the UE exchanges packets on the network, and containing information conditioned on at least one information element, so that: when the information conditioned on the at least one information element is contained in the at least one rule and the UE does not satisfy the information contained in the at least one rule, the UE cannot exchange packets according to the at least one rule; when the information conditioned on the at least one information element is contained in the at least one rule and the UE satisfies the information contained in the at least one rule, the UE exchanges packets according to any constraints contained in the at least one rule; and when there is no information corresponding to the at least one information element in the at least one rule, the UE exchanges packets according to any constraints contained in the at least one rule.

[0048] In one aspect, at least one information element comprises a location element.

[0049] On the other hand, the location element includes at least one of: a geographic location specified by a 2D and / or 3D coordinate system, a geographic location specified by an identifier of a geographic area of ​​a mapping system, a RAN address, a cell identifier, a tracking area identifier (TAI), a registration area identifier, and / or an indication that at least one of the above rules is always considered.

[0050] In one aspect, the at least one information element comprises a time element.

[0051] In one embodiment, the time element includes at least one of: a time of day, a date, a day of the week, a day of a month, a month, a year, a period (specifying at least one of the above time elements to start the period and / or specifying at least one of the above time elements to end the period), a loop, and / or an indication that at least one of the above rules is always considered.

[0052] In another embodiment, the at least one policy includes at least one of the following: UE route selection policy (URSP), access network discovery and selection policy (ANDSP), UE background data transfer policy (UBDTP), access traffic steering, switching and splitting (ATSSS) policy, quality of service (QoS) policy, access and mobility management policy, and expenditure policy.

[0053] In one embodiment, the URSP includes a list of routing descriptors, each routing descriptor including a routing descriptor priority value that determines the priority of the routing descriptor, and one or more of a location information element and a time information element that respectively determine the location and time period for which the routing descriptor applies.

[0054] In another embodiment, the at least one information element is included in at least one of the components of the URSP rule and the routing descriptor of the URSP rule, the component comprising at least one of: session continuity (SSC) mode, network slice selection, data network name (DNN) selection, and non-seamless offload indication and / or access type preference.

[0055] In another embodiment, the UBDTP policy specifies at least one of: a UBDTP identification phase for identifying whether at least one UE is authorized to use the UBDTP service; a UBDTP rule definition phase for defining at least one rule including information conditioned on at least one information element, the at least one rule including at least one of a UBDTP rule and a URSP rule; a UBDTP application server (AS) configuration phase for identifying an AS associated with at least one UE receiving the UBDTP service; and a UBDTP operation phase for providing the UBDTP service to background data according to the at least one rule defined in the UBDTP rule definition phase, the background data being transmitted by the at least one UE to the AS associated with the at least one UE.

[0056] In another embodiment, the QoS policy includes at least one of the following: a QoS profile of a QoS flow, a QoS rule, and at least one QoS-related information set, the QoS profile being exchanged between a session management function (SMF) and a radio access network (RAN) node based on the at least one information element, the QoS rule being exchanged between the SMF and at least one UE based on the at least one information element, and the at least one QoS-related information set being exchanged between the SMF and a user plane (UP) function (UPF) based on the at least one information element.

[0057] In another embodiment, the access and mobility management policy includes at least one tracking area identifier (TAI) for exchange between the NF and the operator through the access and mobility management function (AMF) subject to the above at least one information element.

[0058] In another embodiment, the NF includes a policy and control function (PCF).

[0059] In another embodiment, the at least one policy includes at least one UE route selection policy (UE route selection policy, USRP), and the PCF creates a URSP that can be used for background data transmission.

[0060] In another embodiment, the PCF sends a set of policy charging and control (PCC) rules to a session management function (SMF) of the network, the PCC rules including information on handling UE background data transfer services associated with the PDU session. The PCC rules include at least one of a time information element and a location information element.

[0061] In another embodiment, when at least one of the above-mentioned PCF and unified data management (UDM) indicates that the UE is entitled to use the background data transfer service, and at least one of the above-mentioned UBDTP and URSP includes at least one of the location information element and the time information element that are not satisfied, the SMF rejects the UE request.

[0062] In another embodiment, when the UE configuration data indicates that the UE is entitled to use the background data transfer service, but at least one of the PCF and the UDM confirms that at least one of the location information element and the time information element is not satisfied, at least one of the PCF and the UDM sends a response to the SMF indicating a rejection indication of the SMF request for a data association that is specific to the PDU session establishment requested by the UE.

[0063] In another embodiment, when the UE configuration data indicates that the UE is authorized to use the background data transfer service, and at least one of the PCF and the UDM confirms that both the location information element and the time information element are satisfied, at least one of the PCF and the UDM sends a response to the SMF, indicating an acceptance indication of the SMF request for a data association that is specific to the PDU session establishment requested by the UE.

[0064] In another embodiment, the SMF rejects the UE request by sending a rejection message to the UE via an application management function (AMF) of the network, the rejection message including a reason indicating at least one reason for rejecting the UE request.

[0065] In another embodiment, the at least one reason includes at least one of the following: the UE is not authorized to use the background data transmission service, the current UE location does not satisfy the location information element constraint, and the current UE time does not satisfy the time information element constraint.

[0066] In another embodiment, the UE is entitled to use the UBDTP service, and the SMF establishes a requested PDU session for transmitting background data.

[0067] In another embodiment, the SMF checks at least one of the location information element and the time information element of the PDU session to determine whether the UE is entitled to use the PDU session to transmit background data.

[0068] In another embodiment, when the UE is not entitled to use the background data delivery service, or when the UE is entitled to use the background data delivery service but at least one of the location information element constraint and the time information element constraint is not met, the SMF sends a rejection message to the AMF, which includes a reason indicating at least one reason why the UE is not entitled to establish a PDU session or activate the user plane of an existing PDU session to transmit background data.

[0069] In another embodiment, when the UE is entitled to use the background data transfer service and the location information element and time information element constraints are met, at least one of the SMF and the PCF monitors the location information element and the time information element for the duration of the PDU session of the background data transfer.

[0070] In another embodiment, based on the above monitoring, the SMF determines that at least one of the location information element and the time information element is not met, and the SMF initiates a PDU session release process.

[0071] In another embodiment, based on the above monitoring, the SMF determines that at least one of the location information element and the time information element is not satisfied, and the SMF initiates UP deactivation of the UP connection of the existing PDU session.

[0072] In another embodiment, the SMF initiates a PDU session release procedure at the request of the PCF due to violation of at least one of the time information element constraint and the location information element constraint.

[0073] In another embodiment, at least one of the location information element and the time information element constraints is not satisfied due to UE mobility and handover transition.

[0074] In another embodiment, the above method further includes: including at least one indication specifying whether at least one rule is strictly enforced.

[0075] In another embodiment, the network includes an application function (AF) that specifies at least one of network area information and time window information, and the AF includes at least one indication of whether at least one of the network area information and the time window information will be strictly enforced.

[0076] In another embodiment, when the indication specifies that the at least one rule is to be strictly enforced, if the UE does not satisfy the information included in the at least one rule, the UE cannot exchange packets according to the at least one rule.

[0077] In another embodiment, when the indication specifies that the at least one rule will not be strictly enforced, the UE exchanges packets according to any constraints included in the at least one rule even if the UE does not satisfy the information included in the at least one rule.

[0078] In another embodiment, the PCF sends a UE Routing Policy (USRP) when conditions regarding at least one of a time period and a location are met.

[0079] In another embodiment, when a condition regarding at least one of the time information element and the location information element is met, the UE performs one of establishing a PDU session and activating a UP connection of an existing PDU session to couple to a data network name (DNN) selection to use a network service provided therein.

[0080] In another embodiment, if the UE exchanges packets even if the UE does not satisfy information in the at least one rule, different criteria are applied to the packets exchanged according to the at least one rule.

[0081] In another embodiment, the above-mentioned criterion is at least one of different billing rates and different quality of service (QoS).

[0082] In another broad aspect of the present invention, a network function (NF) of a wireless communication network is provided. The NF includes a processor; and a non-transitory memory for storing instructions, which, when executed by the processor, cause the NF to optimize the operation of a user equipment (UE) in the network by: sending at least one rule of at least one policy on the network, the at least one rule controlling how the UE exchanges packets on the network and containing information conditioned on at least one information element, so that: when the information conditioned on the at least one information element is contained in the at least one rule and the UE does not satisfy the information contained in the at least one rule, the UE cannot exchange packets according to the at least one rule; when the information conditioned on the at least one information element is contained in the at least one rule and the UE satisfies the information contained in the at least one rule, the UE can exchange packets according to any constraints contained in the at least one rule; and when there is no information corresponding to the at least one information element in the at least one rule, the UE can exchange packets according to any constraints contained in the at least one rule. A system including the NF is also provided.

[0083] Some aspects and embodiments of the present disclosure may provide methods for optimizing UE operation by making multiple policies conditional on one or more information elements. BRIEF DESCRIPTION OF THE DRAWINGS

[0084] Examples of the present disclosure are now described with reference to the following drawings, in which like reference numerals refer to like elements throughout the different drawings, and in which:

[0085] Figure 1 is a block diagram of an electronic device within a computing and communication environment that can be used to implement devices and methods according to representative examples of the present disclosure;

[0086] Figure 2 is a block diagram showing a service-based view of the system architecture of 5GCN;

[0087] Figure 3 To show the connection of reference points Figure 2 A block diagram of the system architecture of 5GCN is shown;

[0088] Figure 4To illustrate a signal flow diagram according to an example signal flow by which the NEF may negotiate with the H-PCF a delivery strategy regarding future background data delivery;

[0089] Figure 5 To illustrate an example of a method at a NF according to an example, the method is used to optimize the operation of UEs in a network.

[0090] In the present disclosure, for the purpose of explanation rather than limitation, specific details are set forth in order to provide a thorough understanding of the present disclosure. In some cases, detailed descriptions of well-known devices, circuits, and methods are omitted so as to avoid making the description of the present disclosure unclear with unnecessary details.

[0091] Therefore, where appropriate, system and method components are represented by conventional symbols in the figures, and only those specific details relevant to understanding the examples of the present disclosure are shown so as not to obscure the present disclosure with details that would be readily apparent to those skilled in the art having the benefit of the description herein.

[0092] Any features or actions shown in dashed lines may be considered optional in some examples. DETAILED DESCRIPTION

[0093] Figure 11 is a block diagram of an electronic device (ED) 52 shown within a computing and communication environment 100, which can be used to implement the devices and methods disclosed herein. In some embodiments, the ED 52 can be a communication network infrastructure unit, such as a base station (e.g., NodeB, evolved NodeB (eNodeB or eNB), next generation NodeB (sometimes referred to as gNodeB or gNB)), a home subscriber server (HSS), a gateway (GW) such as a packet gateway (PGW) or a serving gateway (SGW), or various other nodes or functions within a core network (CN) or a public land mobile network (PLMN). In other examples, the ED 52 can be a device coupled to the network infrastructure via a wireless interface, such as a mobile phone, a smart phone, or other such devices that can be classified as user equipment (UE). In some examples, ED 52 may be a machine type communications (MTC) device (also known as a machine-to-machine (m2m) device), or another such device that may be classified as a UE despite not providing direct services to a user. In some references, ED 52 may also be referred to as a mobile device, a term intended to reflect a device that is connected to a mobile network, regardless of whether the device itself is designed to be mobile or is capable of being mobile. A particular device may utilize all of the components shown or only a subset of the components, and the degree of integration may vary from device to device. In addition, a device may include multiple instances of components, such as multiple processors, memories, transmitters, receivers, and the like. ED 52 typically includes a processor 54, such as a central processing unit (CPU), and may also include a dedicated processor such as a graphics processing unit (GPU) or other such processor, a memory 56, a network interface 58, and a bus 60 for connecting the components of ED 52. ED 52 also optionally includes components such as mass storage 62, video adapter 64, and I / O interface 68 (shown in phantom).

[0094] Memory 56 may include any type of non-transitory system memory readable by processor 54, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or a combination thereof. In an example, memory 56 may include more than one type of memory, such as ROM used at boot time, and DRAM for storing programs and data used when executing programs. Bus 60 may be one or more of any type of several bus architectures, including a memory bus or memory controller, a peripheral bus, or a video bus.

[0095] The ED 52 may also include one or more network interfaces 58, which may include at least one of a wired network interface and a wireless network interface. Figure 1 As shown, the network interface 58 may include a wired network interface for connecting to a network 74, and may also include a wireless access network interface 72 for connecting to other devices via a wireless link. When the ED 52 is a network infrastructure unit, the wireless access network interface 72 may be omitted for nodes or functions that are units of the PLMN rather than those located at the wireless edge (e.g., eNB). When the ED 52 is an infrastructure at the wireless edge of the network 74, a wired network interface and a wireless network interface may be included. When the ED 52 is a wirelessly connected device (e.g., UE), the wireless access network interface 72 may be present, and the wireless access network interface 72 may be supplemented by other wireless interfaces such as a WiFi network interface. The network interface 58 enables the ED 52 to communicate with a remote entity such as one connected to the network 74.

[0096] The mass storage 62 may include any type of non-transitory storage device for storing data, programs, and other information and for making the data, programs, and other information accessible via the bus 60. For example, the mass storage 62 may include one or more of a solid-state drive, a hard disk drive, a magnetic disk drive, or an optical disk drive. In some examples, the mass storage 62 may be remote from the ED 52 and may be accessed using a network interface such as the network interface 58. In the illustrated example, the mass storage 62 is distinct from the memory 56 that includes the mass storage, and may generally perform storage tasks that are compatible with higher latency, while generally providing less volatility or no volatility. In some examples, the mass storage 62 may be integrated with the heterogeneous memory 56.

[0097] An optional video adapter 64 and an I / O interface 68 (shown in dashed lines) provide interfaces for coupling the ED 52 to external input and output devices. Examples of input and output devices include a display 66 coupled to the video adapter 64 and an I / O device 70 such as a touch screen coupled to the I / O interface 68. Other devices may be coupled to the ED 52, and more or fewer interfaces may be used. For example, a serial interface such as a universal serial bus (USB) (not shown) may be used to provide an interface for external devices. Those skilled in the art will appreciate that in embodiments where the ED 52 is part of a data center, the I / O interface 68 and the video adapter 64 may be virtualized and provided through the network interface 58.

[0098] In some examples, ED 52 may be a stand-alone device, while in other embodiments, ED 52 may reside in a data center. As understood in the art, a data center is a collection of computing resources (usually in the form of servers) that can be used as collective computing and storage resources. Within a data center, multiple services can be connected together to provide a computing resource pool on which virtualized entities can be instantiated. Data centers can be interconnected to form a network consisting of pooled computing and storage resources connected to each other through connectivity resources. Connectivity resources can take the form of physical connections such as Ethernet or optical communication links, and in some cases may also include wireless communication channels. If two different data centers are connected via multiple different communication channels, any of a variety of technologies including forming a link aggregation group (LAG) can be used to combine the links together. It should be understood that any or all computing resources, storage resources, and connectivity resources (as well as other resources within the network 74) can be divided between different subnets, and in some cases, the above resources can be divided in the form of resource slices. If resources across multiple connected data centers or other node collections are sliced, different network slices can be created.

[0099] Figure 2A service-based architecture 200 of a 5G core network (5GCN) or next generation core network (NGCN / NCN) is shown, generally shown in the architecture 200. This figure depicts logical connections between nodes and functions, and the connections shown should not be interpreted as direct physical connections. ED 52 establishes a radio access network connection with a (radio) access network node ((R)AN) 84, which is connected to a user plane (UP) function (UPF) 86, such as a UP gateway of a network interface (such as an N3 interface). UPF 86 is connected to a data network (DN) 88 via a network interface (such as an N6 interface). DN 88 can be a data network for providing operator services, or can be outside the scope of standardization of the third generation partnership project (3GPP), such as the Internet (a network for providing third-party services), and in some examples, DN 88 can represent an edge computing network or resource, such as a mobile edge computing (MEC) network. ED 52 is also connected to access and mobility management function (AMF) 90. AMF 90 is responsible for authentication and authorization of access requests, and is responsible for mobility management functions. AMF 90 can perform other roles and functions defined by 3GPP technical specification (TS) 23.501. In a service-based view, AMF 90 can communicate with other functions through a service-based interface represented as Namf. Session management function (SMF) 92 is a network function responsible for allocating and managing IP addresses assigned to UEs, and is responsible for selecting UPF 86 (or a specific instance of UPF86) for traffic related to a specific session of ED 52. In a service-based view, SMF 92 can communicate with other functions through a service-based interface represented as Namf. Authentication server function (AUSF) 94 provides authentication services to other network functions through a service-based Nausf interface. A network exposure function (NEF) 96 may be deployed in the network to allow servers, functions, and other entities such as those outside the trust domain to access services and capabilities within the network.In one such example, NEF 96 can be similar to an agent between an application server outside the network shown and network functions such as policy control function (PCF) 201, SMF 92, and AMF 90, so that an external application server can provide information that can be used to set parameters related to data sessions. NEF 96 can communicate with other NFs through a service-based Nnef network interface. NEF 96 can also have an interface to non-3GPP functions. Network storage function (network repository function, NRF) 98 provides network service discovery functions. NRF 98 can be specific to the PLMN or network operator associated with it. The service discovery function can allow NFs and UEs connected to the network to determine where and how to access existing NFs, and can present a service-based interface Nnrf. PCF 201 communicates with other NFs through a service-based Npcf interface, and can be used to provide policies and rules to other NFs (including those within the control plane (CP) 108). The implementation and application of these policies and rules are not necessarily the responsibility of PCF 201, but are usually the responsibility of the functions to which PCF 201 sends policies. In one such example, the PCF 201 may send policies related to session management to the SMF 92. This may be used to allow a unified policy framework that may be utilized to manage network behavior. The unified data management function (UDM) 102 may present a service-based Nudm interface for communicating with other NFs, and may provide data storage facilities to other NFs. Unified data storage may allow a unified view of network information that may be used to ensure that the most relevant information may be provided to different NFs from a single resource. This may make implementation of other NFs easier because these NFs do not need to determine where a particular type of data is stored in the network. Because the PCF 201 may be involved in requesting and providing subscription policy information to the UDR 401, the PCF 201 may be associated with the UDM 102, but it should be understood that the PCF 201 and the UDM 102 are typically independent functions. The PCF 201 may have a direct interface to the UDR 401. The stored data is typically associated with policy profile information (which may be provided by the PCF 201) that manages access rights to the stored data. In some examples, UDR 401 may store policy data, structured data for opening, application data, and user subscription data, which may include any or all of subscription identifiers, security credentials, access and mobility related subscription data, and session related data.The application function (AF) 104 represents the non-data plane (also known as non-user plane) functions of applications deployed within the network operator domain and within a 3GPP-compatible network. AF 104 interacts with other core NFs through a service-based Naf interface and can access network capability exposure information, as well as provide application information for decisions such as traffic routing. AF 104 can also interact with functions such as PCF 201 to provide application-specific inputs for policy and policy implementation decisions. It should be understood that in many cases, AF 104 does not provide network services to other NFs, but is often regarded as a consumer or user of services provided by other NFs. Application functions outside the 3GPP network can perform many of the same functions as AF 104 by using NEF 96.

[0100] like Figure 3 As shown, ED 52 communicates with NFs in UP 106 and CP 108. UPF 86 is part of CN UP 106 (DN 88 is outside 5GCN). (R)AN 84 can be considered part of UP, but because (R)AN 84 is not strictly part of the core network, (R)AN 84 is not considered part of CN UP 106. AMF 90, SMF 92, AUSF 94, NEF 96, NRF 98, PCF 201, and UDM 102 are functions located within CN CP 108 and are generally referred to as CP functions (CPF). AF 104 can communicate with other functions within CN CP 108 (directly or indirectly through NEF 96), but AF 104 is generally not considered part of CN CP 108.

[0101] Those skilled in the art will appreciate that multiple UPFs 86 may be connected in series between the (R)AN 84 and the DN 88, and as will be described with respect to Figure 3 As discussed, multiple data sessions to different DNs may be mediated by using multiple UPFs 86 in parallel.

[0102] Figure 3 A reference point representation of the 5GCN architecture 300 is shown. For clarity, Figure 3 Omitted Figure 2 Some NFs are shown in the figure, but it should be understood that the omitted functions and those not in the Figure 2 or Figure 3 The functions shown in can interact with the functions shown.

[0103] ED 52 is connected to (R)AN 84 (in UP 304) and AMF 90 (in CP 306). The connection of ED to AMF is N1 connection. (R)AN 84 is also connected to AMF 90 via N2 connection. (R)AN 84 is connected to UPF function 86 via N3 connection. UPF86 is associated with PDU session and is connected to SMF 92 via N4 interface to receive session control information. If ED 52 has multiple active PDU sessions, these PDU sessions can be supported by multiple different UPFs 86, each UPF 86 is connected to SMF 92 via N4 interface. It should be understood that from the perspective of reference point representation, multiple instances of SMF 92 or UPF 86 are considered to be different entities. Each UPF 86 is connected to at least DN 88 outside 5GCN via N6 interface. SMF 92 is connected to PCF 201 via N7 interface, and PCF 201 is connected to AF 104 via N5 interface. The AMF 90 is connected to the UDM 102 through the N8 interface. If two UPFs 86 in the UP304 are connected to each other, the two UPFs 86 can be connected through the N9 interface. The UDM 102 can be connected to the SMF 92 through the N10 interface. The AMF 90 and the SMF 92 are connected to each other through the N11 interface. The N12 interface connects the AUSF 94 to the AMF 90. The AUSF 94 can be connected to the UDM 102 through the N13 interface. In a network where multiple AMFs 90 exist, these AMFs 90 can be connected to each other through the N14 interface. The PCF 201 can be connected to the AMF 90 through the N15 interface. If there are multiple SMFs 92 in the network, these SMFs 92 can communicate with each other through the N16 interface.

[0104] It should also be understood that any or all of the functions and nodes discussed above with respect to the 5GCN architectures 200 and 300 may be virtualized within the network, and as will be discussed below, the network itself may be provided as a network slice of a larger resource pool.

[0105] Information Elements Introduction

[0106] The present disclosure introduces various information elements that can be combined with multiple PCF 201 policies to provide additional granularity in controlling the operation of the UE 52. Thus, as a non-limiting example, with the input from the NWDAF, the PCF 201 obtains statistical and / or analytical information of various network parameters, including but not limited to network traffic load, network slice traffic load, resource usage, traffic distribution in different network locations, service experience (quality of experience, QoE), UE mobility information, UE behavior information, and / or QoS, and the PCF 201 includes one or more of such new information elements as information elements of various UE policies, such new information elements alone or in combination with each other and / or in combination with other information elements to provide guidance to the UE 52, thereby optimizing the UE's access to the best available network resources, and other information elements include but are not limited to S-NSSAI, RAT, Application ID, and / or Packet Filter Descriptor.

[0107] PCF 201 can establish and maintain policies including one or more rules and send these policies to UE 52, which contain such information elements as their parameters. In some examples, the above rules can be provided to UE 52 during the initial registration of UE 52 to the network. In some examples, the rules can be provided to UE 52 as policy updates when UE 52 changes its state so that it is suitable to provide one or more of these rules to UE 52. In some examples, PCF 201 can provide policy updates to UE 52 at other time points, which include but are not limited to when one or more such rules have been updated. In some examples, depending on the network load, the ability of PCF 201 to provide policy updates to UE 52 may be postponed or completely eliminated. In some examples, SMF 92 can provide one or more rules (and / or update one or more rules previously provided) to UE 52 during the PDU session establishment and / or PDU session modification process.

[0108] The present disclosure contemplates two such information elements, namely, a location element and a time element, which may be introduced individually or together into one or more such policies.

[0109] Positional Elements

[0110] The location element indicates a geographical indication of where a given rule of a given policy can be used by a UE 52. The form of the location element includes, but is not limited to, any or all of the following:

[0111] ● A geographic location that can be specified by a 2D or 3D coordinate system;

[0112] ●A geographic location may be specified by a unique identifier of a geographic area in a predetermined mapping system. The area may overlap with another area, or the areas may be non-overlapping. In some examples, the mapping may be performed via a CP 306 interface (including but not limited to an N1 interface).

[0113] Sent from a 5G core network (CN) function to the UE 52, or from the AS to the UE 52 via a UP 304 data connection;

[0114] ● A list of RAN 84 addresses, which in some examples may be Internet Protocol (IP) addresses

[0115] and / or fully qualified domain name (FQDN);

[0116] ● The access type, which in some examples may be a non-3GPP AN (e.g., Wi-Fi) or a 3GPP AN (e.g., but not limited to, 3G, 4G, 5G, and / or 6G RAN 84);

[0117] ● A list of cell identifiers and / or a list of RAN identifiers, each identifier identifying a cell that sends and receives wireless signals to connect UE 52 to the RAN.

[0118] The identity of the wireless node receiving DN 88;

[0119] ● A tracking area identifier (TAI) identifies a tracking area. In some examples, a tracking area may include a cell.

[0120] a list of identifiers and / or a list of RAN node identifiers;

[0121] ● A registration area identifier that uniquely indicates a particular registration area. In some examples, UE 52 may store the registration area in local storage. In some examples, a registration area may include a collection of tracking areas; and / or

[0122] ● The policy rules overridden by the location element apply to any location indication.

[0123] Time Element

[0124] The time element indicates the date and / or time and / or time range during which the UE 52 may use a given rule of a given policy. The form of the time element may include, but is not limited to, any or all of the following:

[0125] ● The time the day starts;

[0126] ● the end of the day;

[0127] ● start date;

[0128] ● End date;

[0129] ● Day of the week (and / or list of days);

[0130] ● Day of the month (and / or list of days);

[0131] ● month (and / or list of months of the year);

[0132] ● Year (and / or list of years) and / or Start Year and / or End Year;

[0133] ● One or more time periods, each time period specifying a start time and end time and / or date and / or recurring; and / or

[0134] ● The policy rules covered by the time element apply to any indication of time.

[0135] It should be understood that in addition to the two information elements identified, namely the location element and the time element, other information elements may be understood by those skilled in the art in consideration of the present disclosure and without departing from the scope of the present disclosure.

[0136] A number of non-limiting examples will now be described showing how new information elements may be introduced into the rules of various policies that control how UE 52 exchanges packets with the AS on the network, including but not limited to the policies identified above. It should be understood that these are merely examples, and that these (and other) information elements may be introduced into these (and other) policies with the aid of the described (and other) example mechanisms with consideration of the present disclosure and without departing from the scope of the present disclosure.

[0137] For each type of policy, PCF 201 may send one or more policy rules to UE 52 on the network, wherein each policy rule covers a different location information element and / or time information element. The various location information elements and / or time information elements in the various policy rules may overlap or may not overlap. It is understood that the terms "information element" and "element information" may be used interchangeably in the embodiments of the present invention. For example, location element information may be referred to as a location information element, and time element information may be referred to as a time information element.

[0138] The application software in UE 52 may have a user interface through which this information may be presented to the user of UE 52. By viewing the policy (and its policy rules) using such a user interface, the user may decide where and when to use one or more network services, including but not limited to voice, video, and / or data services. The user may also decide when and where to access one or more wireless access types, including but not limited to 3GPP AN and / or non-3GPP AN. In some examples, the software in UE 52 may automatically select and use network services, including but not limited to 3GPP AN and / or non-3GPP AN and / or network slices, based on location information elements and / or time information elements contained in various policy rules.

[0139] In some non-limiting examples, PCF 201 may include one or more indications, including but not limited to an enforcement indication, which specifies whether the location information element and / or the time information element are to be strictly enforced.

[0140] In some non-limiting examples, PCF 201 may notify SMF 92 of applicable indications of location information elements and / or time information elements of respective policy rules. In some non-limiting examples, SMF 92 may then forward the indication to UPF 86 and / or RAN 84.

[0141] In some non-limiting examples, PCF 201 may include in UE policies (including but not limited to URSP) applicable indications of location information elements and / or time information elements for various policy rules.

[0142] If the above indication specifies that the location information element and / or the time information element will be strictly enforced, the UE 52 cannot exchange packets according to the rules associated with the information elements because one or more of the UE 52, UPF 86, and / or RAN 84 will discard packets of the PDU session and / or QoS flow that do not satisfy the location information element and / or the time information element.

[0143] If the above indication specifies that the location information element and / or the time information element will not be strictly enforced, one or more of the UE 52, UPF 86, and / or RAN 84 can prevent the UE 52 from exchanging packets according to the rules associated with the information element. Alternatively, one or more of the UE 52, UPF 86, and / or RAN 84 can choose to allow the UE to exchange packets according to any constraints contained in the rules associated with the information element, rather than preventing the exchange or discarding packets of the QoS flow and / or PDU session that do not meet the location information element and / or the time information element. The charging system can apply different standards to packets that are exchanged even if the location information element and / or the time information element are not met. In some non-limiting examples, the above different standards can be a higher charging rate. Alternatively, the above different standards can be that the PCF applies different QoS policies to packets that do not meet the exchange of the location information element and / or the time information element.

[0144] URSP

[0145] PCF 201 provides URSP rules of the home PLMN (HPLMN) to UE 52. In some examples, UE 52 may have been pre-configured with URSP rules by a mobile network operator (MNO) or otherwise. In this case, the URSP rules provided by PCF 201 will take precedence over any pre-configured URSP rules. In addition, PCF 201 in the HPLMN can update the URSP rules in UE 52 when UE 52 roams. URSP has been described at least in 3GPP TS23.503.

[0146] In some examples, the PCF 201 includes the location element and / or the time element as information elements within the URSP. The location element and / or the time information element are sent to the UE 52 as part of one or more rules defined to include these information elements.

[0147] In some examples, in addition to the rule priority value that determines the priority of the rule within the URSP, each URSP rule sent to and stored in the UE 52 also has one or more of a location information element and / or a time information element, which respectively determine the location and / or time period for applying the URSP rule. The PCF 201 may provide the UE 52 with one or more URSP rules for any location and / or time and / or time period within the network, respectively. For each URSP rule, if a location information element is provided, the URSP rule may be applied only at the location described by the location information element. If no location information element is provided, the URSP rule may be applied regardless of the location of the UE 52. Similarly, for each URSP rule, if a time information element is provided, the URSP rule may be applied only at the time described by the time information element. If no time information element is provided, the URSP rule may be applied regardless of the time of the UE 52.

[0148] Each URSP rule contains a traffic descriptor that determines under what traffic conditions the URSP will be applied. The traffic descriptor works together with one or both of the location information element and / or the time information element so that only when the UE 52 is in a location and / or time period that satisfies the location information element and the time information element, respectively, can the traffic that satisfies the traffic descriptor be sent to the network. Otherwise, even if a packet satisfies the above traffic descriptor, one or more of the UE 52 and / or the UPF 86 will discard the packet.

[0149] Each URSP rule contains a list of routing descriptors, each of which has one or more of a location information element and / or a time information element, in addition to a routing descriptor priority value that determines the priority of the routing descriptor, the location information element and the time information element respectively determining the location and / or time period to which the routing descriptor applies. In some examples, the routing descriptor may include one or more of the following components:

[0150] ● a session and service continuity (SSC) mode indicating that traffic for matching applications will be routed via a PDU session supporting the SSC mode. In some examples, the SSC mode may have one or more of an SSC location information element and / or an SSC time information element, the SSC location information element and / or the SSC time information element indicating a location and / or time, respectively, at which an SCC mode policy may be applied;

[0151] ●Network slice selection, indicating that traffic for matching applications will be routed via PDU sessions that support any included S-NSSAI. In some examples, the network slice selection may have one or more of a network slice selection location information element and / or a network slice selection time information element, the network slice selection location information element and / or the network slice selection time information element respectively indicating the location and / or time at which the network slice selection policy can be applied. In some examples, a mobile network operator may use a network slice selection location information element and / or a network slice selection time information element to indicate the availability of a network slice at a specific location and / or time period, respectively. To give a non-limiting example, if a 5G RAN 84 provides URLLC services along a highway, the network slice selection may include a list of RAN nodes 84 installed along the highway as a network slice selection location information element. In another non-limiting example, the network may be optimized so that when the traffic load of a particular network slice is low, network management may shut down the computing hardware associated with the network slice to save energy and transfer traffic to other network slices for processing. In this scenario, one or more network slice selection time information elements may be used to indicate only the time period during which the network slice can be accessed.

[0152] ● A data network name (DNN) is selected, indicating that traffic for matching applications will be routed via PDU sessions that support any included DNNs. In some examples, the DNN selection can have one or more of a DNN selection location information element and / or a DNN selection time information element to indicate the location and / or time at which the DNN selection policy will be applied. In some non-limiting examples, IP multimedia subsystem (IMS) voice services, IMS video services, and / or local area data network (LADN) services may be available at a specific location and / or time period. In this scenario, the MNO can use the DNN selection location information element and / or the DNN selection time information element to notify the UE 52.

[0153] ●A non-seamless diversion indication indicating that traffic of a matching application will be diverted to a non-3GPP AN outside of the PDU session. In some examples, the non-seamless diversion indication may have one or more of a non-seamless diversion indication location information element and / or a non-seamless diversion indication time information element to indicate the location and / or time at which the non-seamless diversion indication may be applied. In some non-limiting examples, a video streaming application may use a non-3GPP AN at a specific location and / or time period. In this scenario, the MNO may use the non-seamless diversion indication location information element and / or the non-seamless diversion indication time information element to notify the UE 52.

[0154] ● An access type preference indicating the access type (3GPP or non-3GPP AN) for which the PDU session should be established. In some examples, the access type preference may have one or more of an access type preference location information element and / or an access type preference time information element to indicate the location and / or time at which the access type preference is to be performed. In this scenario, the MNO may use the access type preference location information element and / or the access type preference time information element to notify the UE 52.

[0155] In some examples, SMF 92 may send one or more of location information elements and / or time information elements and related information including, but not limited to, S-NSSAI, DNN, application ID, packet filters (including, but not limited to IP, Ethernet, or unstructured data) to RAN 84 and / or UPF 86 during a PDU session establishment and / or PDU session modification process.

[0156] In these examples, there may be situations where UE 52 erroneously sends a PDU that meets the criteria established by the relevant information but does not meet any information elements associated with the location element (including in its various variations including but not limited to the SSC location information element, the network slice selection location information element, the DNN selection location information element, the non-seamless splitting indication location information element, and / or the access type preference location information element) and / or the time element (including in its various variations including but not limited to the SSC time information element, the network slice selection time information element, the DNN selection time information element, the non-seamless splitting indication time information element, and / or the access type preference time information element).

[0157] In this case, the RAN node 84 and / or UPF86 can detect such a packet and notify the SMF 92. In some non-limiting examples, if the location information element and / or the time information element that stipulates a specific rule will be strictly enforced, the RAN84 and / or UPF 86 can discard such a packet. The SMF 92 can then decide to deactivate the UP connection of the PDU session used to carry the illegal PDU. Alternatively, the SMF 92 can then decide to release the PDU session used to carry the illegal PDU and / or send a notification message to the AMF 90, notifying that the UE 52 is sending traffic that violates one or more of the location element and / or the time element. The AMF 90 can then perform an AN release procedure to put the UE 52 into the CM-IDLE state. Alternatively, the AMF 90 can perform a UE deregistration procedure to deregister the UE 52. Alternatively, the AMF 90 can send a mobility management (MM) message to the UE 52 at the N1 interface, requesting the UE 52 to stop sending traffic that violates the location element and / or the time element standard.

[0158] In some examples, the visiting PCF 201 (visiting PCF, V-PCF) in the visiting PLMN (VPLMN) may obtain the URSP rules from the HPLMN, and modify the location element and / or the time element to correspond to various parameters of the HPLMN.

[0159] By introducing as parameters the location element and / or the time element on which one or more URSP rules can be conditioned, the PCF 201 can send multiple URSP rules simultaneously to the UE 52. This eliminates the need for the PCF 201 to establish a mechanism for sending a certain URSP rule whenever the PCF 201 detects that the UE 52 meets the conditions set forth in one or both of the location element and / or the time element, and for sending another URSP rule whenever the PCF 201 detects that the UE 52 no longer meets such conditions, which would cost considerable network resources and consume considerable UE power to update UE policies.

[0160] Instead, the UE 52 may utilize the location element and / or the time information element included in the URSP rule to obtain network information. As a non-limiting example, in this example, only the location element is considered, and different access technologies (ATs) (including but not limited to 3GPP 4G RAN 84, 3GPP 5G RAN 84, and / or non-3GPP AN) may exist in different geographic areas of the network. As shown in the following non-limiting example scenario, the UE 52 may use the information contained in the location element and the network service availability to select appropriate communication parameters:

[0161] ● The UE 52 is aware of the availability of Wi-Fi or 5G RAN 84 in a particular network location and may also have a map showing the network ATs. The UE 52 may be relocated by its associated user to a location utilizing a desired RAT (e.g., to a location that provides Wi-Fi and / or 5G RAN 84);

[0162] ● The UE 52 uses the URSP information element (including but not limited to the access type preference, the access type preference location information element, and / or the DNN selection location information element) and the time information element associated with the URSP information element (including but not limited to the SSC time information element, the network slice selection time information element, the DNN selection time information element, the non-seamless offload indication time information element, and / or the access type preference time information element) to activate the appropriate communication interface when the UE 52 moves to the area where the given AT is provided, such as but not limited to the 5G RAN 84 interface. This capability can reduce the time spent by the UE 52 searching for the RAN 84 (the RAN 84 includes but is not limited to a Wi-Fi radio node, a Wi-Fi access point (AP), and / or a 4G and / or 5G radio base station (BS)).

[0163] UE 52 can know the location (including but not limited to LADN) where a specific service is provided. UE 52 can use DNN as a proxy indication of the availability of LADN. In addition, by using URSP information elements associated with location elements (including in various variations thereof, including but not limited to SSC location information elements, network slice selection location information elements, DNN selection location information elements, non-seamless splitting indication location information elements, and / or access type preference location information elements) and / or time elements (including in various variations thereof, including but not limited to SSC time information elements, network slice selection time information elements, DNN selection time information elements, non-seamless splitting indication time information elements, and / or access type preference time information elements), UE 52 can establish a PDU session or activate a UP connection for an existing PDU session to connect to the DNN and use the services provided by it when UE 52 enters a location and / or time period that satisfies such information elements.

[0164] ANDSP

[0165] In some examples, PCF 201 includes one or more of a location element and a time element as information elements within the ANDSP. The location element and / or the time information element are sent to UE 52 as part of one or more ANDSP rules defined to include these information elements. In some examples, the mechanism can be similar to the mechanism described above in conjunction with URSP.

[0166] UBDTP

[0167] UBDTP provides UE 52 with network information that allows UE 52 to request a PDU session with appropriate QoS for uploading background data to an AS located in or connected to DN 88.

[0168] In some examples, PCF 201 can provide background data transfer policies to UE 52 at any time, including but not limited to during the initial registration of UE 52, or when UE 52 changes location. However, network congestion may prevent PCF 201 from providing policy updates when needed. In some examples, PCF 201 includes one or more of the location element and / or the time element as information elements within the UBDTP. The location element and / or the time information element are sent to UE 52 within the UBDTP. This allows PCF 201 to proactively provide multiple policy rules to UE 52 when network congestion allows.

[0169] UBDTP involves four phases, namely, identification phase, rule definition phase, AS configuration phase, and operation phase. These phases will be discussed separately below.

[0170] UBDTP Identification Phase

[0171] In the UBDTP identification phase, the CN identifies whether a given UE 52 is a UE that the specifications of the UBDTP rules apply to.

[0172] This identification can be done through a variety of mechanisms, including but not limited to:

[0173] ● The CN and / or OAM function configures the UE subscription data of the UE 52 in the UDM 102 and / or the UDR 401 to receive the UBDTP service,

[0174] ● The CN and / or OAM function configures the UE subscription data of the UE 52 in the PCF 201 to receive the UBDTP service,

[0175] ● The CN receives a request for UBDTP service from the UE 52, and

[0176] ● The CN receives a notification from the AF 104 identifying the UE 52 as receiving UBDTP service.

[0177] In the first mechanism, the CN may configure the UE 52 to receive the UBDTP service in the UDM 102 and / or the UDR 401. In this mechanism, an indicator may be used to indicate that the UE 52 is to receive the UBDTP service. In the UDR 401 and / or the UDM 102, the indicator may be stored in the subscription data of the UE 52 and / or as part of the access and mobility subscription data. In some examples, the indicator may take values ​​indicating that the UBDTP service is allowed or not allowed, respectively.

[0178] In this mechanism, the AMF 90 extracts the subscription data of the UE 52, including the above-mentioned indicator, from the UDM 102 during the registration of the UE 52, for example, through the Nudm_SDM_Get service operation of the UDM 102. Then, the AMF 90 may perform a policy association establishment procedure as disclosed at least in 3GPP TS23.502, in particular in Section 4.16.1.2. If the indicator indicates that the UBDTP service is allowed, the PCF 201 provides the AMF 90 with UBDTP information (in some examples, the UBDTP information may be a new set of UBDTPs to be added to the UE 52, or a set of UBDTPs existing in the UE 52 are deleted and / or modified), and the AMF 90 (including but not limited to) deploys the UBDTP to the UE 52 using the UE 52 update delivery procedure as disclosed at least in 3GPP TS23.502, in particular in Section 4.2.4.3.

[0179] In some examples, UBDTP services may be allowed or prohibited based on a network slice instance (NSI) (denoted by S-NSSAI in some non-limiting examples) and / or for an internal group of UE 52. In this scenario, a second mechanism is appropriate, in which the CN configures UE 52 in PCF 201 to receive UBDTP services. In this mechanism, AMF 90 may send a request to PCF 201 for UE access selection and / or PDU session selection information. In some examples, the request may include an appropriate S-NSSAI and / or internal group ID. PCF 201 examines the information provided by AMF 90 and makes a decision as to whether to allow UBDTP services to UE 52, such as in situations where the S-NSSAI and / or internal group ID is associated with the UE that will use UBDTP. If PCF 201 decides to allow UBDTP service, PCF 201 may provide UBDTP information to AMF 90 as disclosed in at least 3GPP TS 23.503, in particular in Section 6.6, as part of UE access selection and / or PDU session selection information, or as independent application information, and AMF 90 (including but not limited to) deploying UBDTP to UE 52 using the UE 52 update delivery procedure as disclosed in at least 3GPP TS 23.502, in particular in Section 4.2.4.3.

[0180] In a third mechanism, the UE 52 may send a request for UBDTP service to the AMF 90 during the UE registration process, such as disclosed at least in 3GPP TS 23.502, particularly in step 1 of clause 4.2.2.2.2 or clause 4.2.2.2.3, but including an indicator indicating that UBDTP service has been requested. The RAN 84 forwards the UE registration request to the AMF 90. The AMF 90 checks whether the indicator has been included in the request, and if so, sends the indicator (or another corresponding indicator) to the PCF 201 to request UBDTP service. The PCF 201 checks the information provided by the AMF 90 and decides whether to allow UBDTP service to the UE 52, such as the case where the S-NSSAI, internal group ID, and / or DNN are associated with the UE that will use UBDTP. If PCF 201 decides to allow UBDTP service, PCF 201 may provide UBDTP information to AMF 90 as part of UE access selection and / or PDU session selection information or as independent application information, and AMF 90 (including but not limited to) deploying UBDTP to UE 52 using the UE update delivery procedure as disclosed in at least 3GPP TS 23.502, in particular in Section 4.2.4.3.

[0181] In a fourth mechanism, as disclosed at least in 3GPP TS 23.502, particularly in clause 4.16.7, the CN may receive a notification from the AF 104 identifying the UE 52 as receiving UBDTP service.

[0182] Figure 4 is an example signal flow diagram generally shown at 400. The figure shows the communication between UDR 401, home PCF (H-PCF 402), NEF 96, and AF 104 in the negotiation of a delivery strategy between NEF 96 and H-PCF 402 as disclosed at least in 3GPP TS 23.503, in particular in clause 6.1.2.4, including but not limited to a required time window for future background data delivery (as disclosed at least in 3GPP TS 23.203, in particular in clause 6.1.16), a charging rate (or a reference thereto), and / or a maximum aggregate bit rate.

[0183] This negotiation may be performed prior to establishing a PDU session for the UE 52, and in some examples, is performed when the AF 104 initiates the process to the NEF 96. The NEF 96 may then apply UBDTP to a single UE 52, including but not limited to, by invoking Npcf_PolicyAuthorization_Create and / or Npcf_PolicyAuthorization_Update service operations directly with the PCF 201 and / or indirectly through the policy control function (PCF) 201. The service operation will include an indication requesting that the CN allow the UE 52 to use UBDTP. In some examples, the AF 104 includes information indicating which UEs 52 are allowed to use UBDTP, including but not limited to one or more external UE IDs, GPSIs, external group IDs, S-NSSAIs, DNNs, application identifiers, and / or AF service identifiers. In some non-limiting examples, the AF 104 may specify required network area information and / or required time windows.

[0184] In some non-limiting examples, the AF 104 may include one or more indications regarding whether the required network area information and / or the required time window will be strictly enforced. If the indication specifies that the required network area information and / or the required time window will be strictly enforced, the PCF may specify one or more UBDTPs for the UE 52 so that the UE 52 is prohibited from using the background data transfer service for packets of the PDU session and / or QoS flow that do not meet the required network area information and / or the required time window. If the indication specifies that the location information element and / or the time information element will not be strictly enforced, the PCF may specify one or more UBDTPs for the UE 52 so that the UE 52 may choose to send (rather than discard) packets of the PDU sessions and / or QoS flows that do not satisfy the location information element and / or the time information element, so that the 5G system applies different charging policies to the PDU sessions and / or QoS flows that do not satisfy the location information element and / or the time information element, and / or enables the PCF 201 to apply different QoS policies to the PDU sessions and / or QoS flows that do not satisfy the location information element and / or the time information element, and / or the SMF 92 may send different QoS parameters to the UE 52, the RAN 84, and the UPF 86 to apply to the PDU sessions and / or QoS flows that do not satisfy the location information element and / or the time information element.

[0185] Step 1. Negotiation begins when AF 104 invokes the Nnef_BDTPNegotiation_Create service as described at least in TS 23.502, particularly in clause 5.2.6.6.2. In some examples, AF 104 may include information indicating which UE will be allowed to use UBDTP, including but not limited to one or more external UE IDs, GPSI of UE 52, external group ID, S-NSSAI, DNN, application identifier, and / or AF service identifier.

[0186] Step 2. In response thereto, the NEF 96 and the H-PCF 402 invoke the Npcf_BDTPolicyControl_Create request service as described at least in 3GPP TS 23.502, particularly in Section 5.2.5.5.2, to authorize the creation of the UBDTP. If the UE 52 information is provided in step 1, the NEF 96 may map the external UE ID to another internal UE ID, such as SUPI, subscription concealed identifier (SUCI), and / or GPSI, and / or may map the external group ID to the internal group ID. In some non-limiting examples, after mapping the received UE 52 information to the internal parameters as described above, the NEF 96 may include the UE 52 information in the Npcf_BDTPolicyControl_Create request message.

[0187] Step 3. H-PCF 402 may request all stored delivery policies corresponding to the application service provider (ASP) identifier from UDR 401. H-PCF 402 may identify the network slice to which the ASP belongs based on the ASP identifier. If a list of UE IDs that can use the background data delivery service is provided in step 1, H-PCF 402 forwards the list of UE IDs to UDR 401. In the case where only one H-PCF 402 is deployed in the PLMN, the delivery policies may be stored locally without the need for interaction with UDR 401.

[0188] Step 4: UDR 401 provides the corresponding network area information and all stored delivery policies associated with the ASP identifier to H-PCF 401. If a list of UE IDs that can use the background data transfer service is provided in step 3, UDR 401 marks the UE as being able to use the background data transfer (BDT) service in the session management subscription data.

[0189] Step 5. Based on the information provided by AF 104 and other available information, H-PCF 402 determines one or more delivery strategies, including URSP for UBDTP for background data delivery. The maximum aggregate bit rate is not enforced in the network.

[0190] Step 6: H-PCF 402 sends a response message with an acceptable delivery policy and background data delivery reference ID to NFF 96. NEF 96 forwards the received delivery policy to AF 104 and stores the background data delivery reference ID for future interactions with PCF 402.

[0191] Step 7: NEF 96 sends Nnef_BDTPNegotiation_Create response to AF 104 to provide one or more background data transfer policies to AF 104. If NEF receives only one background transfer policy from H-PCF 402, steps 8 to 11 are not performed and the process proceeds to step 12. Otherwise, the process proceeds to step 8.

[0192] Step 8. Finally, the AF 104 invokes the Nnef_BDTPNegotiation_Update request service as described at least in 3GPP TS23.502, particularly in Section 5.2.6.6.3, to provide one or more selected UBDTP updates to the NEF 96. In some examples, the UBDTP update includes information indicating which UE 52 will be allowed to use UBDTP, including but not limited to one or more external UE IDs, GPSI, external group ID, S-NSSAI, DNN, application identifier, and / or AF service identifier.

[0193] Step 9. NEF 96 calls Npcf_BDTPolicyControl_Update service to provide H-PCF 402 with the selected background data transfer policy and the associated background data transfer reference ID.

[0194] Step 10: H-PCF 402 sends a response message to NEF 96.

[0195] Step 11, NEF 96 sends a reply message to AF 104. If NEF 96 receives only one delivery policy, AF 104 confirmation is not required.

[0196] Step 12, H-PCF 402 stores the reference ID together with the new delivery policy and the corresponding network area information in UDR 401. When H-PCF 402 decides to store the delivery policy locally, this step is not performed. If a list of UE IDs that can use the background data delivery service is provided in step 8, H-PCF 402 forwards the list of UE IDs to UDR 401 and takes action.

[0197] Step 13: UDR 401 sends a response to H-PCF 402 as its reply.

[0198] UBDTP rule definition phase

[0199] In some examples, the PCF 201 may send a URSP policy to the UE 52 instead of sending the UBDTP to the UE 52, and the UE 52 may use the URSP policy to transmit background data to its associated AS. The URSP may contain a traffic descriptor that matches the application ID, IP descriptor, and / or non-IP descriptor and / or a DNN used by the UE 52 to send background data to the associated AS. In some examples, in addition to a rule priority value that determines the priority of the rule within the UBDTP, each URSP rule sent to the UE 52 and stored therein also has a URSP rule value that determines the URSP rule to be applied to the QoS flow and / or PDU session established for transmitting background data, and each URSP rule also has a DNN selection that determines the DNN to which the UBDTP will be applied, and one or more of a location information element and / or a time information element that respectively determines the location and / or time period for executing the UBDTP rule. The PCF 201 may provide the UE 52 with one or more URSP rules for any location and / or time and / or time period within the network, respectively.

[0200] In some non-limiting examples, PCF 201 may include an indication of whether the location information element and / or time information element contained in one or more policy rules will be strictly enforced. These indications may be determined based on or not based on the information provided by AF104. If the indication specifies that the location information element and / or time information element will be strictly enforced, UE 52 will not allow the background data transmission service to be used for packets of PDU sessions and / or QoS flows that do not meet the location information element and / or time information element. If the indication specifies that the location information element and / or time information element will not be strictly enforced, UE 52 may choose to send (rather than discard) packets of PDU sessions and / or QoS flows that do not meet the location information element and / or time information element, so that the 5G system applies different charging policies and / or QoS policies to traffic that does not meet the location information element and / or time information element.

[0201] For each URSP rule, if a location information element is provided, the URSP rule may be applied only at the location described by the location information element. If no location information element is provided, the URSP rule may be applied regardless of the location of the UE 52. Similarly, for each URSP rule, if a time information element is provided, the URSP rule may be executed at the time described by the time information element. If no time information element is provided, the URSP rule may be applied regardless of the time of the UE 52.

[0202] In addition, during the UBDTP rule definition phase, PCF 201 provides UE 52 with UBDTP rules of the HPLMN. In some examples, UE 52 may be pre-configured with UBDTP rules by MNO or other means. In this case, the UBDTP rules provided by PCF 201 will take precedence over any pre-configured UBDTP rules. In addition, PCF 201 in the HPLMN may update the UBDTP rules in UE 52 when UE 52 roams.

[0203] In some examples, in addition to the rule priority value that determines the priority of the rule within the UBDTP, each UBDTP rule sent to the UE 52 and stored therein also has one or more of a location information element and / or a time information element that respectively determines the location and / or time at which the UBDTP rule is executed. The PCF 201 may provide the UE 52 with one or more UBDTP rules for any location and / or time and / or time period within the network, respectively. For each UBDTP rule, if a location information element is provided, the UBDTP rule may be used only at the location described by the location information element. If no location information element is provided, the UBDTP rule may be applied regardless of the location of the UE 52. Similarly, for each UBDTP rule, if a time information element is provided, the UBDTP rule may be applied only at the time described by the time information element. If no time information element is provided, the UBDTP rule may be applied regardless of the time at which the UE 52 sends background data.

[0204] In some non-limiting examples, PCF 201 may include an indication of whether the location information element and / or time information element included in one or more policy rules is to be strictly enforced. If the indication specifies that the location information element and / or time information element will be strictly enforced, UE 52 will not allow the background data transmission service to be used for packets of PDU sessions and / or QoS flows that do not satisfy the location information element and / or time information element. If the indication specifies that the location information element and / or time information element will not be strictly enforced, UE 52 may choose to send (rather than discard) packets of PDU sessions and / or QoS flows that do not satisfy the location information element and / or time information element, so that the 5G system applies different charging policies and / or QoS policies to traffic that does not satisfy the location information element and / or time information element.

[0205] In some examples, PCF 201 includes the location element and / or the time element as information elements within the UBDTP. The location information element and / or the time information element are sent to UE 52 as part of one or more rules defined to include these information elements.

[0206] Each UBDTP rule contains a traffic descriptor that determines under what traffic conditions the UBDTP will be applied, which in some non-limiting examples may have a form and content similar to the traffic descriptor described above in the context of URSP. The traffic descriptor works in conjunction with one or both of the location information element and / or the time information element, so that traffic that satisfies the traffic descriptor can be sent to the network only when the UE 52 is in a location and / or time period that satisfies the location information element and / or the time information element, respectively. Otherwise, even if a packet satisfies the traffic descriptor, the UE 52 may discard the packet.

[0207] In some examples, a UBDTP rule with a "match all" traffic descriptor may be provided. This UBDTP rule may be used to route traffic for background data applications that do not match any other more specific UBDTP rule. As such, this traffic is typically assigned the lowest available routing preference value.

[0208] As discussed above, each URSP rule contains a list of routing descriptors. In some examples, the URSP rule structure does not define how the PCF 201 separates the URSPs when the URSPs are not transmitted to the UE 52 in a single NAS message.

[0209] If the CN rejects the PDU session establishment request from the UE 52, the UE 52 may trigger a new PDU session establishment based on the reason for the rejection and the UBDTP.

[0210] The traffic descriptors in USRP and / or UBDTP, as the case may be, ensure that the UE 52 uses the appropriate network slice instance to send background data to the pre-configured AS. In this way, the possibility of the UE 52 abusing UBDTP to send non-background data is significantly reduced. In addition, the mechanism allows charging for the upload of background data at a lower rate and / or a better QoS (e.g., at a higher maximum bit rate).

[0211] UBDTP AS configuration phase

[0212] During the UBDTP AS configuration phase, PCF 201 is provided with information identifying the AS associated with UE 52 receiving UBDTP services, as identified during the UBDTP identification phase.

[0213] The associated AS is identified by AS information, which in some non-limiting examples may include an AF service identifier, an external application identifier, an application identifier, a DNN, an external group ID, a PFD, an IP and / or Ethernet descriptor, and / or a data network access identifier (DNAI).

[0214] In some examples, if PCF 201 is provided with an external application identifier, PCF 201 may map the identifier to an application identifier used by UPF 86 and / or CPF (including but not limited to PCF 201 and / or SMF 92). In some examples, a PFD may be identified by a PFD identifier, which in some non-limiting examples may be unique within the scope of a specific application identifier. Different PFD types may be associated with a given application identifier. In some examples, as non-limiting examples, a PFD may include a PDF identifier, an IP 3-tuple (including but not limited to a protocol, a service-side IP address, and / or a port number), a portion of a URL to be matched (which may be a host name in some non-limiting examples), or a domain matching criterion. In the case where an IP 3-tuple is specified in the PFD, PCF 201 may be used to create AS information. In some non-limiting examples, a PFD may be designed to convey a proprietary extension of a proprietary application traffic detection mechanism agreed upon by AF 104 and the MNO.

[0215] In some examples, the IP descriptor may include one or more IP 3-tuples, and in some non-limiting examples, the one or more IP 3-tuples may include one or more of the following: source IP address and / or destination IP address, IPv6 network prefix, source port number and / or destination port number, protocol ID of the protocol above the IP level, next header type, type of service (TOS) (IPv4) and / or traffic class (IPv6) and / or mask, flow label (IPv6), security parameter index, and / or packet filter direction.

[0216] In some examples, the Ethernet descriptor may include one or more of: a destination MAC address, an Ethernet type as defined in IEEE Standard 802.3 (which in some non-limiting examples may indicate an IPv4 / IPv6 payload), a customer-VLAN tag (C-TAG) and / or a service-VLAN tag (S-TAG), a priority code point (PCP) / drop eligible indicator (DEI) field as defined in IEEE Standard 802.1Q, and / or an IP 3-tuple (which in some non-limiting examples may include a destination IP address, an IPv6 network prefix, a destination port number, and / or a protocol ID for a protocol above the IP level).

[0217] In some examples, PCF 201 is provided with one or more DNAIs. A DNAI is used to indicate a traffic routing profile for data routing between UPF 86 and an AS. The traffic routing profile may be considered in SMF 92 and / or PCF 201. In some examples, PCF 201 may use the DNAI to obtain AS information, including but not limited to IP descriptors and / or Ethernet descriptors.

[0218] In some examples, the AS information can be configured by OAM. In some examples, the AS provider (ASP) can Figure 4 The AS information for UBDTP is sent to the CN in the manner of the signaling flow diagram, as described below:

[0219] ● In some examples, the AF 104 may send the AS information to the NEF 96 as part of a Nnef_BDTPNegotiation_Create request (as disclosed at least in 3GPP TS 23.502, in particular in clause 5.2.6.6.2) and / or a Nnef_BDTPNegotiation_Update request (as disclosed at least in 3GPP TS 23.502, in particular in clause 5.2.6.3.3) service operation. In some non-limiting examples, if the AS information includes an external group ID, the NEF 96 may replace it with an internal group ID. If the AS information includes an external application identifier, the NEF 96 may map the identifier to an application identifier used by the UPF 86 and / or CPF (including but not limited to the PCF 201 and / or SMF 92).

[0220] ●Step 9. In some examples, when receiving the AS information as part of the Nnef_BDTPNegotiation_Create request and / or the Nnef_BDTPNegotiation_Update request service operation, the NEF 96 may send the AS information as part of the Npcf_BDTPPolicyControl_Create request and / or the Nnef_BDTPolicyControl_Update request service operation to the H-PCF 402. In some non-limiting examples, if the AS information includes an external group ID, the NEF 96 may replace it with an internal group ID. If the AS information includes an external application identifier, the H-PCF 402 may map the identifier to an application identifier used by the UPF 86 and / or CPF (including but not limited to the PCF 201 and / or the SMF 92).

[0221] ● In some examples, Figure 4 In step 5, the H-PCF 402 may make one or more UBDTP decisions based on the information provided by the AF 104 and / or other available information. If the AF 104 provides AS information, the H-PCF 402 may use the information to create a traffic descriptor, which in some non-limiting examples may include an application ID and / or IP (or non-IP) descriptor for UBDTP and / or URSP (for background data transfer) service operations. In some examples, if the H-PCF 402 is provided with an external application identifier, the H-PCF 402 may map the identifier to an application identifier used by the UPF 86 and / or CPF (including but not limited to the PCF 201 and / or SMF 92).

[0222] Therefore, AF 104 can provide AS information to the mobile network for use in UBDTP. In this way, since UE 52 will comply with the specified AS information, the possibility of UE 52 abusing UBDTP to send non-background data is significantly reduced.

[0223] UBDTP Operation Phase

[0224] In the UBDTP operation phase, the UE 52 identified in the UBDTP identification phase registers with the CN and starts using background data transfer services under UBDTP.

[0225] When the UE 52 performs the UE registration procedure, the AMF 90 extracts access and mobility subscription data from the UDM 102 through (including but not limited to) the Nudm_SDM_Get service operation as disclosed at least in 3GPP TS23.502, particularly in clause 5.2.3.3.2. In some examples, the UDM 102 may obtain the UE subscription data from the UDR 401, including but not limited to an indication that the UE is allowed to use the UBDTP service. The UDM 102 then provides the indication to the AMF 90.

[0226] In some examples, AMF 90 may request UE-related policies from PCF 201 using (including but not limited to) a policy association establishment procedure as disclosed at least in 3GPP TS23.502, in particular in clause 4.16.1.2. If the access and mobility subscription data includes the indication, AMF 90 sends the indication or a related indication with similar meaning to PCF 201.

[0227] In some examples, PCF 201 may be configured with an indication that a UE 52 belonging to an internal group is accessing an NSI represented by an S-NSSAI and / or accessing a DNN and / or a UE ID (including but not limited to a GPSI, a permanent equipment identifier (PEI), and / or a SUPI), which allows the UE 52 to use UBDTP services.

[0228] If it is confirmed that the UE 52 is entitled to use the UBDTP service, in some non-limiting examples, the PCF 201 may send the UBDTP (or URSP for background data transfer) to the AMF 90. The AMF 90 may then include the UBDTP (or URSP) in the Registration Accept it sends to the UE 52. Alternatively, in some non-limiting examples, as disclosed at least in 3GPP TS 23.502, in particular in clause 4.2.4.3, the AMF 90 may include the UBDTP (or URSP) in the UE configuration update procedure to transparently transmit the UE policy to the UE 52.

[0229] AF 104 may do so by using Nnef_BDTPNegotiation_Create as disclosed at least in 3GPP TS 23.502, in particular in clause 4.16.7 (eg, Figure 4 ) and / or Nnef_BDTPNegotiation_Update (as shown in step 1 of Figure 48) service operation, requesting the CN to allow the UE 52 to use the UBDTP service. The AF 104 may include in such service operation an indication that the UE 52 is allowed to use the UBDTP service and information identifying the affected UE 52. In some non-limiting examples, the information identifying the affected UE 52 includes one or more of the following: an AF service identifier, an external group ID, an NSI represented by an S-NSSAI, a DNN, a UE ID (including but not limited to one or more of GPSI, PEI, SUPI, and / or an external UE ID), and / or an external application identifier.

[0230] In some examples, NEF 96 may map external IDs to internal IDs, including, but not limited to, mapping GPSIs to SUPIs, mapping external group IDs to internal group IDs, and / or mapping external application identifiers to application identifiers.

[0231] NEF 96 can be created by using Npcf_BDTPolicyControl_Create of PCF 201 (e.g. Figure 4 ) and / or Npcf_BDTPolicyControl_Update (as shown in step 2 of Figure 4 The service operation updates the existing UBDTP and processes the request of AF 104 to allow UE 52 to use the UBDTP service.

[0232] like Figure 4 As shown in step 5, PCF 201 creates and / or updates one or more new UBDTP (and / or URSP for background data transmission) rules for background data transmission by UE 52 identified by AF 104.

[0233] In some examples, PCF 201 can provide UBDTP (and / or USRP) rules to authorized UE 52 through a UE configuration update procedure for transparent UE policy delivery as disclosed at least in 3GPP TS 23.502, particularly in clause 4.2.4.3. In some examples, PCF 201 can map external IDs to internal IDs, including but not limited to mapping a generic public subscription identifier (GPSI) to a subscription permanent identifier (SUPI), mapping an external group ID to an internal group ID, and / or mapping an external application identifier to an application identifier.

[0234] In some non-limiting examples, the UBDTP may include a URSP that specifies one or more URSP rules that the UE 52 will follow when requesting to establish a PDU session for transmitting background data. Alternatively, in some non-limiting examples, the PCF 201 may create a URSP that can be used for background data transmission. Such a URSP may include one or more of the following: an application identifier assigned for background data transmission, a DNN with an associated AS for receiving background data transmission, and / or an IP or non-IP descriptor indicating information of the AS for receiving background data transmission (in some non-limiting examples, may include an IP address, UDP, and / or TCP port).

[0235] The CN can detect background data transmission through various mechanisms.

[0236] In the first mechanism, when UE 52 requests a PDU session in a manner similar to the UE requesting a PDU session establishment process, UE 52 sends a service request indicating background data transfer to AMF 90. At least in 3GPP TS23.502, in particular, in its Section 4.3.2.2.1 regarding non-roaming scenarios and / or roaming scenarios with local breakout and / or its Section 4.3.2.2.2 regarding home-routed roaming scenarios, the above-mentioned UE requesting a PDU session establishment process is disclosed. It should be noted that when UE 52 requests a PDU session in step 1 of Section 4.3.2.2.1 and / or in step 1 of Section 4.3.2.2., UE 52 can indicate "background data transfer service" as the request type to AMF 90 in the N1 NAS message.

[0237] In some examples, AMF 90 may have obtained access and mobility policies associated with UE 52 during the UE 52's registration process.

[0238] If the access and mobility policy does not include an indicator that the UE 52 is allowed to use the UBDTP service, the AMF 90 may reject the request of the UE 52. Alternatively, if the access and mobility policy includes an indicator that the UE 52 is allowed to use the UBDTP service, but the UBDTP (and / or URSP) rules include a location information element and / or a time information element that are not satisfied, the AMF 90 may reject the request of the UE 52. In either case, for example, steps 2 to 12 of clause 4.3.2.2.1 and / or steps 2 to 14 of clause 4.3.2.2.2 may be omitted. Instead, the AMF 90 may send a rejection message to the UE 52 in a NAS message to the RAN 84 discussed in step 12 of clause 4.3.2.2.1, which the RAN 84 forwards to the UE 52 in step 13 of clause 4.3.2.2.1.

[0239] Conversely, if the access and mobility policy includes an indicator allowing the UE 52 to use the UBDTP service, and the UBDTP (and / or URSP) rules do not include any location information element and / or time information element, or include location information elements and / or time information elements that have been satisfied, the AMF 90 stores the PDU session ID and the background data transfer service for the PDU session ID in the UE context, and, for example, in step 3 of 4.3.2.2.1 and / or in step 3 of 4.3.2.2.2, the AMF 90 may select the SMF 92 responsible for establishing a PDU session to carry the background data transfer service, and indicate "background data transfer service" as the request type in the message to the SMF 92.

[0240] In accordance with applicable UBDTP (and / or URSP) rules associated with the background data transfer service, AMF 90 may include location information elements and / or time information elements associated with at least one or more of DNN, S-NSSAI, access type, RAT type, and / or SSC mode.

[0241] In the second mechanism, when the UE 52 requests a PDU session in a manner similar to the UE request PDU session establishment process, the UE 52 sends a service request to the AMF 90, at least in 3GPP TS23.502, in particular, in its 4.3.2.2.1 for non-roaming scenarios and / or roaming scenarios with local breakout and / or in its 4.3.2.2.2 for home-routed roaming scenarios, the above UE request PDU session establishment process is disclosed, it should be noted that the UE 52 does not inform the AMF 90 that the requested PDU session is for background data transmission. Instead, for example, by sending an N1 SM container indicating "background data transfer service" to the AMF 90 in step 1 of 4.3.2.2.1 and / or in step 1 of 4.3.2.2.2, the UE 52 requests the SMF 92 to establish the requested PDU session for background data transmission. In step 3 of Section 4.3.2.2.1 and / or step 3 of Section 4.3.2.2.2, AMF 90 forwards the N1 SM container to the selected SMF 92.

[0242] Upon receiving the request, SMF 92 checks with UDM 102 and / or PCF 201 to determine whether UE 52 is entitled to use the UBDTP service. In response, UDM 102 may send an indication of whether UE 52 is entitled to use the UBDTP service, for example in step 4 of clause 4.3.2.2.1 and / or step 7 of clause 4.3.2.2.2.

[0243] If UE 52 is not authorized to use the UBDTP service, steps 5 to 10 of clause 4.3.2.2.1 and / or steps 8 to 13 of clause 4.3.2.2.2 may be omitted.

[0244] If the UE 52 is entitled to use the UBDTP service, then in some non-limiting examples, for example, in step 7b of clause 4.3.2.2.1 and / or step 9b of clause 4.3.2.2.2, the SMF 92 may provide an indication of this result to the PCF 201. In response thereto, the PCF 201 may send a PCC rule to the SMF 92, the PCC rule including information on how to handle the UBDTP service for the PDU session. In some non-limiting examples, this may include a location information element and / or a time information element associated with at least one or more of the DNN, S-NA ASI, access type, RAT type, SSC mode, and / or charging policy, as a non-limiting example, the charging policy may indicate a maximum data amount for the PDU session.

[0245] If one or both of the UDM 102 and / or PCF 201 indicate that the UE 52 is not entitled to use the UBDTP service, the SMF 92 may reject the request of the UE 52. Alternatively, if one or both of the UDM 102 and / or PCF 201 indicate that the UE 52 is entitled to use the UBDTP service, but the UBDTP (and / or URSP) rules include location information elements and / or time information elements that are not satisfied, the SMF 92 may reject the request of the UE 52. In either case, for example, steps 8 to 10 in clause 4.3.2.2.1 and / or steps 2 to 14 in clause 4.3.2.2.2 may be omitted. On the contrary, for example, as discussed in step 11 of Section 4.3.2.2.1 and / or step 14 of Section 4.3.2.2.2, SMF 92 may send a rejection message to UE 52 in the N1 SM container sent to AMF 90, the rejection message including a reason indicating why UE 52 is not entitled to use the UBDTP service (including but not limited to that UE 52 is not entitled to use the UBDTP service, the current location of UE 52 does not satisfy the location information element constraint, and / or the current time of UE 52 does not satisfy the time information element constraint).

[0246] The AMF 90 forwards the N1 SM container to the RAN 84 in step 12 of section 4.3.2.2.1. The RAN 84 forwards the N1 SM container to the UE 52 in step 13 of section 4.3.2.2.1.

[0247] If the UE 52 is entitled to use the UBDTP service, the SMF 92 establishes a requested PDU session for background data transfer, and in some non-limiting examples, such as discussed in step 11 of clause 4.3.2.2.1 and / or step 14 of clause 4.3.2.2.2, the AMF 90 may be notified by sending an indication of the result associated with the PDU session to the RAN 84 in an N2 SM message sent to the AMF 90. If so, the AMF 90 may store the indication of the result for the PDU session. In some non-limiting examples, the AMF 90 may refer to the UBDTP (and / or URSP) policy to obtain any universal location information element and / or time information element constraints. In some non-limiting examples, the N2 SM information message may include one or more time information elements of the PDU session during which the PDU session may employ background data transfer.

[0248] Once a PDU session for background data transmission is established, the RAN 84 may allow UL and / or DL ​​data transmission if the time of the UE 52 satisfies one or more time information elements of the PDU session. However, if the time of the UE 52 does not satisfy any time information element of the PDU session, the RAN 84 may not allocate radio resources to the PDU session and / or QoS flow for transmitting background data, and / or may request the SMF 92 to deactivate the UP of the PDU session established for background data transmission. Alternatively, in some non-limiting examples, the RAN 84 may request the SMF 92 to release the PDU session and / or QoS flow for transmitting background data. If the UE 52 has only one PDU session for background data transmission, the RAN 84 may initiate an AN release procedure as discussed at least in 3GPP TS23.502, particularly in clause 4.2.6, by which the UE 52 will enter the CM-IDLE state.

[0249] Likewise, if the UE 52 is entitled to use the UBDTP service and satisfies all location information element and / or time information element constraints, thereby establishing a requested PDU session for background data transfer, the SMF 92 may send an indication to the UPF 86 that the PDU session is for background data transfer, which, in some non-limiting examples, may include a time information element for the PDU session and / or QoS flow to be used for transferring background data. If the time of the UE 52 satisfies one or more time information elements for the PDU session described in the time information element provided by the SMF 92 to the UPF 86, the UPF 86 may allow UL and / or DL ​​data transfer. However, if the time of UE 52 does not satisfy one or more time information elements for the PDU session described in the time information element provided by SMF 92 to UPF 86, UPF 86 may discard any UL PDU, may not notify SMF 92 of the DL PDU, and / or may notify SMF 92 that the time information element constraint has expired and or the data amount limit has been reached, so that SMF 92 may deactivate the UP of the PDU session established for background data transmission as discussed at least in 3GPP TS23.502, in particular in Section 4.3.7, and / or SMF 92 may release the PDU session established for background data transmission as discussed at least in 3GPP TS23.502, in particular in Section 4.3.4.

[0250] When the UE 52 sends a service request to enter the CM-CONNECTED state, the UE 52 may initiate a UE-triggered service request procedure as discussed at least in 3GPP TS 23.502, particularly in clause 4.3.3.2.

[0251] In step 1 of clause 4.3.3.2, the UE 52 may include an indication that the UE 52 wants to use the UBDTP service. The AMF 90 may check the location information element and / or the time information element associated with the UBDTP (and / or URSP) rule (the rule is associated with background data transfer) to determine whether the UE 52 is entitled to use the UBDTP service. If not, or if the UE 52 is entitled to use the UBDTP service but at least one of the location information element and / or time information element constraints is not satisfied, the AMF 90 may reject the service request.

[0252] Alternatively, for example, in step 1 of clause 4.3.3.2, the UE 52 may include a list of PDU sessions to be activated in a service request message sent to the AMF 90, at least one of which may be a PDU session previously established for background data transfer. In this scenario, the AMF 90 may be aware of the PDU sessions previously established for background data transfer, or if not, process each PDU session in the list. In this way, the AMF 90 may check the location information element and / or time information element associated with the UBDTP (and / or URSP) rule (which is associated with background data transfer) (or generally) to determine whether the UE 52 is entitled to use the UBDTP service (or generally, to perform service operations).

[0253] If the UE 52 is not entitled to use the UBDTP service (or generally, to perform service operations), or if the UE 52 is entitled to use the UBDTP service (or generally, to perform service operations) but at least one of the location information element and / or time information element constraints is not met, the AMF 90 may reject the service request.

[0254] This rejection of the service request may be in the form of an MM NAS message sent by the AMF 90, such as in step 12 of Section 4.3.3.2, which includes the PDU session status in the AMF 90. The MM NAS message may include the PDU session ID rejected by the AMF 90 and / or indicate a reason, which indicates the reason why the UE 52 is not entitled to use the UBDTP service (including but not limited to the UE 52 not being entitled to use the UBDTP service, the current location of the UE 52 not satisfying the location information element constraint, and / or the current time of the UE 52 not satisfying the time information element constraint).

[0255] If the UE 52 is entitled to use the UBDTP service (or, in general, to perform service operations) and the location information element and / or time information element constraints are met, then, for example, in step 4 of clause 4.3.3.2, the AMF 90 may request the SMF 92 to activate the UP connection. In this way, the SMF 92 may check the location information element and / or time information element for the PDU session associated with the background data transfer (or, in general) to determine whether the UE 52 is entitled to use the UBDTP service (or, in general, to perform service operations).

[0256] If the UE 52 is not entitled to use the UBDTP service (or, in general, to perform service operations), or if the UE 52 is entitled to use the UBDTP service (or, in general, to perform service operations) but at least one of the location information element and / or time information element constraints is not satisfied, then, for example, in step 11 of 4.3.3.2, the SMF 92 may send a rejection message to the AMF 90, the rejection message including a reason indicating why the UE 52 is not entitled to use the UBDTP service (including but not limited to the UE 52 not being entitled to use the UBDTP service, the current UE 52 location not satisfying the location information element constraint, and / or the current UE 52 time not satisfying the time information element constraint). Then, for example, in step 12 of clause 4.3.3.2, the AMF 90 sends an MM NAS message including the PDU session status in the AMF 90. The MM NAS message may include the PDU session ID rejected by the AMF 90 and / or indicate a reason, which indicates the reason why the UE 52 sent by the SMF 92 to the AMF 90 is not entitled to use the UBDTP service (including but not limited to the UE 52 not being entitled to use the UBDTP service, the current location of the UE 52 not satisfying the location information element constraints, and / or the current time of the UE 52 not satisfying the time information element constraints).

[0257] If the UE 52 is entitled to use the UBDTP service (or, in general, to perform service operations), and the location information element and / or time information element constraints are satisfied, the SMF 92 monitors the location information element and / or time information element specified for establishing a PDU session for background data transfer. If at any time, for example (without limitation) due to the mobility and / or handover of the UE 52, at least one of the location information element and / or time information element is not satisfied, the SMF 92 may:

[0258] ●Initiate a PDU session release procedure as described, for example, at least in 3GPP TS 23.502, in particular in clause 4.3.4.2 (PDU session release requested by UE 52 or network, for non-roaming or local-guided roaming) and / or clause 4.3.4.3 (PDU session release requested by UE 52 or network, for home-routed roaming). The SMF 92 may release a PDU session associated with background data transfer based on a request by the UE 52, a decision by the AMF 90 (due to violation of location information element and / or time information element constraints), a decision by the PCF 201 (due to violation of location information element and / or time information element constraints), and / or a decision by the SMF 92 to release the PDU session (due to violation of location information element and / or time information element constraints); or

[0259] ● A UP deactivation is initiated as described at least in 3GPP TS 23.502, in particular in clause 4.3.7 (CN initiated deactivation of a UP connection of selected existing PDU sessions).

[0260] ATSSS Strategy

[0261] In some examples, PCF 201 includes a location information element and / or a time element as an information element along with ATSSS. The location element and / or the time information element are sent to UE 52 as part of one or more rules defined to include these information elements. UE 52 can therefore apply different ASSSS policies at different locations and / or at different times, which allows for greater flexibility and customized ASSSS policies.

[0262] In some non-limiting examples, PCF 302 may include one or more indications, including but not limited to an enforcement indication, that specifies whether the location information element and / or the time element are to be strictly enforced.

[0263] In some non-limiting examples, PCF 201 may notify SMF 92 of the applicable indication of the location information element and / or time information element of each policy rule. Then, in some non-limiting examples, SMF 92 may forward the indication to UPF 86 and / or RAN 84.

[0264] In some non-limiting examples, PCF 201 may include applicable indications of location information elements and / or time information elements for various policy rules in the ATSSS policy.

[0265] If the above indication specifies that the location information element and / or the time information element will be strictly enforced, one or more of the UE 52, UPF 86, and / or RAN 84 may discard packets of the PDU session and / or QoS flow that do not satisfy the location information element and / or the time information element.

[0266] If the above indication specifies that the location information element and / or the time information element will not be strictly enforced, one or more of the UE 52, UPF 86, and / or RAN 84 may choose to send (rather than discard) packets for PDU sessions and / or QoS flows that do not meet the location information element and / or the time information element. The charging system may apply different charging policies to PDU sessions and / or QoS flows that do not meet the location information element and / or the time information element. The SMF may provide different QoS parameters to the UE 52, RAN 84, and / or UPF 86 for PDU sessions and / or QoS flows that do not meet the location information element and / or the time information element.

[0267] In some examples, PCF 201 sends the ATSSS policy rules to SMF 92 during the PDU session establishment process. In some examples, SMF 92 may send the ATSSS policy rules to UE 52 in a non-access stratum (NAS) message on the N1 interface. In some examples, SMF 92 may send the ATSSS policy rules to UE 52 as part of the QoS rules.

[0268] In some examples, the ATSSS policy rules may be applied to DL traffic. In such examples, the PCF 201 may send the DL ATSSS policy rules to the SMF 92 during the PDU session establishment process or continuously for the established PDU session. In some examples, the SMF 92 may use the DL ATSSS policy rules to establish a DL connection from the UPF 86 to the RAN node 84 associated with the UE 52. Such DL ATSSS policy rules may include a location information element and / or a time information element in a location information element and / or a time information element that allow the SMF 92 to select the RAN node 84 based thereon, respectively.

[0269] In some examples, SMF 92 may send a DL ATSSS policy rule to UPF 86 that includes a location information element and / or a time information element that allows UPF 86 to forward the DL PDU to the appropriate RAN node 84 based on the location information element and / or the time information element.

[0270] QoS Policy

[0271] QoS policies have been discussed at least in 3GPP TS23.501, especially in clause 5.7 thereof.

[0272] In some examples, when establishing or modifying a PDU session, SMF 92 may send one or more QoS profiles for one or more QoS flows to RAN 84, and RAN 84 may select a QoS profile that satisfies the location information element and / or time information element specified therein.

[0273] In some examples, the QoS profile may overlap with other QoS profiles in terms of one or both of the location information element and / or the time information element. If multiple QoS profiles overlap in terms of the time information element, the RAN 84 may select any one of the overlapping QoS profiles based on the traffic load condition in the current RAN node 84. If multiple QoS profiles overlap in terms of the location information element, the RAN 84 may select any one of the overlapping QoS profiles based on the traffic load condition in the current RAN node 84 and the available resources of the RAN node 84 and / or information about the mobility of the UE 52, and notify the SMF 92 of the selected QoS profile using the N2 SM message.

[0274] After selecting one of the overlapping QoS profiles, the RAN 84 may send an RRC signaling message to the UE 52 to inform the UE 52 of the selected QoS parameters.

[0275] In some examples, SMF 92 may send a PDU session modification request message to UPF 86 to provide UPF 86 with information of the selected QoS.

[0276] In some examples, when establishing or modifying a PDU session, the SMF 92 sends one or more QoS rules associated with the QoS flow to the UE 52 so that the UE 52 can select an appropriate QoS profile. In some examples, the SMF 92 sends one or more default QoS rules to the UE 52. In some examples, the SMF 92 sends a location element and / or a time element as part of the one or more QoS rules. The UE 52 can therefore apply different QoS rules at different locations and / or at different times, which allows greater flexibility and customized QoS policies.

[0277] In some examples, the QoS rule may overlap with other QoS rules (which may be default QoS rules in some examples) with respect to one or both of the location information element and / or the time information element. If multiple QoS (default) rules overlap with respect to one or both of the location information element and / or the time information element, the UE 52 may select any one of the overlapping (default) QoS rules based on the QoS parameters and resource allocation information received by the UE 52 from the serving RAN node 84, which in some examples may be the selected QoS parameters sent by the RAN 84 in the above-mentioned RRC message.

[0278] In some examples, the SMF 92 may provide the QoS related information as a set to the UPF 86. In some examples, the SMF 92 sends a location information element and / or a time information element as part of one or more QoS related information sets. The UPF 86 may therefore apply different QoS related information sets at different locations and / or at different times to select corresponding QoS parameters, including but not limited to session-aggregated maximum bitrate (Session-AMBR), GFBR, MFBR, and / or packet delay budgets and maximum data bursts of the RAN 84 and the UPF 86.

[0279] In some examples, the QoS related information set may overlap with other QoS related information sets in terms of one or both of the location information element and / or the time information element. If multiple QoS related information sets overlap in terms of one or both of the location information element and / or the time information element, the UPF 86 may select any one of the overlapping QoS related information sets based on traffic conditions and / or resources available to the UPF 86.

[0280] After selecting one of the overlapping QoS related information sets, the UPF 86 may send a message to the SMF 92 to inform the SMF 92 of the selected QoS related information set. Therefore, the SMF 92 may then select a QoS profile and / or QoS rules for the QoS flow, and may use the PDF session modification procedure to inform the RAN 84 and / or UE 52 of the selected QoS profile and / or QoS rules.

[0281] By introducing the location element and / or the time element as a parameter on which one or more of the QoS profiles, QoS rules, and / or QoS related information sets can be conditioned, the SMF 92 can assign multiple QoS profiles to the RAN 84, assign multiple QoS rules to the UE 52, and assign the QoS related information sets to the UPF 86. This allows the UE 52, the UPF 86, and / or the RAN 84 to select an appropriate QoS profile based on the traffic load, the conditions of the radio channels of the UE 52 and other UEs 52, the resources available to the RAN node 84, and / or the conditions of the CN, without additional instructions from the SMF 92. In particular, using the location element and / or the time element in this manner tends to reduce the amount of CP 306 signaling sent to the UE 52 when the CN is congested. This is particularly applicable to the case when the UE 52 is a device such as an Internet of Things device (IoT) and / or a vehicle-mounted UE 52, in which case the UE 52 has a PDU session that lasts for a considerable period of time (even until the UE 52 logs off and the PDU session is not released).

[0282] In addition, the RAN 84 and / or the UPF 86 may perform traffic enforcement and / or detect abnormal behavior of the UE 52 using corresponding QoS parameters.

[0283] In addition to the above, UE 52 may also be aware of QoS availability at various locations and / or at various times. In some examples, UE 52 may have a user interface and / or application software for displaying QoS parameters to a user of UE 52, which allows the user to invoke one or more applications corresponding to the QoS parameters provided by the CN, as shown in the following non-limiting example scenario:

[0284] ● When the user knows that the network can support high data rates, the user may choose to use only video streaming applications that involve high data rates;

[0285] ● The user may choose to use a video streaming application that may select a video data rate corresponding to known QoS parameters, including but not limited to MFBR, session AMBF, and / or UE Aggregate Maximum Bit Rate (UE-AMBR);

[0286] ● Some devices (including but not limited to IoT devices and / or vehicle-mounted UE 52) may send UL data when the network can support higher data rates or is less congested.

[0287] Access and mobility management

[0288] In some examples, PCF 201 sends access and mobility related policy control messages to AMF 90 to execute access and mobility policy decisions made by PCF 201 for controlling service area restrictions and RAT / frequency selection policy (RFSP) index. Access and mobility related policies are described at least in 3GPP TS23.503, particularly in its clause 6.5.

[0289] Because the UE 52 may exhibit different mobility patterns at different locations and / or times (e.g., but not limited to, on weekdays, weekends, evenings, and nights), the access and mobility management parameters may be conditioned on one or more of the location information element and / or the time information element, and the access and mobility management parameters may be sent to the UE 52 so that the UE 52 may select appropriate parameters that satisfy the conditions set forth in the location information element and / or the time information element.

[0290] These parameters use the TAI which indicates where the UE 52 is allowed (or not allowed, as the case may be) to register. It can therefore be appreciated that, to some extent, the TAI already takes the location information element into account when establishing access and mobility management parameters. Therefore, the following will primarily discuss the time information element.

[0291] The access and mobility related policy control information includes a list of allowed TAIs and a list of non-allowed TAIs.

[0292] In some examples, each (or in some examples, all) allowed TAIs may be associated with a time information element that determines the time period for which the allowed TAI is applied. For each (or all, as the case may be) allowed TAI, if a time information element is provided, then the (or all, as the case may be) allowed TAI is implemented only at the time described by the time information element. If no time information element is provided, then the (or all, as the case may be) allowed TAI may be applied regardless of the time of the UE 52.

[0293] In some examples, each (or in some examples, all) non-allowed TAI can be associated with a time information element that determines the time period for which the non-allowed TAI is applied. For each (or all, as the case may be) non-allowed TAI, if a time information element is provided, then the (or all, as the case may be) non-allowed TAI is implemented only at the time described by the time information element. If no time information element is provided, then the (or all, as the case may be) non-allowed TAI can be implemented regardless of the time of the UE 52.

[0294] The MNO may utilize a time information element for each (or in some examples, all) allowed TAIs. For example, without limitation, the expected behavior of the UE 52 may be to send UL data at a scheduled time, such as, but not limited to, between midnight and 2:00am on Sunday. If one or more allowed TAIs contain a time information element that is restricted to that time period, the UE 52 will not be able to send and / or receive data outside that time period, thereby reducing the risk of unauthorized access to the network by a third party. In addition, the RAN 84 may detect violations of the time information element and use this to detect malicious behavior that may be reported to a CPF, including but not limited to an AMF 90, an SMF 92, and / or a PCF 201. In some non-limiting examples, the CPF may report the detected malicious behavior to the AF 104, which may be used by an AS for interacting with the mobile network.

[0295] In some examples, PCF 201 may provide multiple RFSP indexes in the access and mobility policy for radio resource management. In some examples, such RFSP indexes may be associated with a time information element that determines the time period for which the RFSP index is applied. For each RFSP index, if a time information element is provided, the RFSP index is only implemented at the time described by the time information element. If no time information element is provided, the RFSP index will be applied regardless of the time of the UE 52.

[0296] By introducing location elements and / or time elements as parameters on which one or more access and mobility management policy rules can be conditioned, PCF 201 can define flexible access and mobility management policies. For example, without limitation:

[0297] ● Registration areas and / or tracking areas can be restricted at different times, reducing signaling to page the UE 52 when an incoming call arrives;

[0298] ● By specifying where and / or when the UE 52 may access the network, unauthorized calls and / or data connections may be prevented.

[0299] Spending strategy

[0300] In some examples, UE 52 may reside primarily in a given location for a significant period of time. For example, and without limitation, UE 52 may reside primarily in an office building during the weekdays, but may reside primarily in a suburban or rural residential area during the weekends and / or evenings.

[0301] In such an example, the NWDAF may identify locations and / or times at which the UE 52 may most likely be transmitting and / or receiving data, and provide this information to the PCF 201 .

[0302] With these messages, PCF 201 can change the spending policy associated with UE 52, including, for example, without limitation, providing higher (or lower) data rates, providing higher (or lower) data usage caps, and / or charging at higher (or lower) per MB rates.

[0303] Method Actions

[0304] Now describe Figure 5 , a flow chart illustrating example actions performed at a NF for optimizing operation of a UE in a network is generally shown at 500.

[0305] One example action 510 is sending at least one rule of at least one policy on a network, the at least one rule controlling how a UE exchanges packets on the network and including information conditioned on at least one information element.

[0306] Each rule is considered in decision 520. If there is information 521 in the rule being considered that is conditional on the information element, then the flow proceeds to decision 530. If not 522, then the flow proceeds to action 540.

[0307] This information is considered in decision 530. If the UE 531 satisfies the information, the flow proceeds to action 540. If not 532, the flow proceeds to action 550.

[0308] An example action 540 is allowing the UE to exchange packets according to any constraints included in the at least one rule.

[0309] An example action 550 is preventing the UE from exchanging packets according to the at least one rule.

[0310] The number of rules is considered in decision 560. If more rules 561 should be considered, flow proceeds to decision 520.

[0311] the term

[0312] The terms "including" and "comprising" are used in an open-ended manner, and thus should be interpreted to mean "including, but not limited to." The terms "example" and "exemplary" are used merely to identify examples for illustrative purposes, and should not be interpreted as limiting the scope of the present invention to the stated examples. In particular, the term "exemplary" should not be interpreted as indicating or conferring any complimentary, beneficial, or other quality on the expressions with which it is used, whether in design, performance, or otherwise.

[0313] The terms "coupled" and "in communication" in any form are intended to mean a direct or indirect connection through some interface, device, intermediate component, or connection, whether optical, electrical, mechanical, chemical, or other means.

[0314] Unless otherwise indicated, references to the singular include the plural and vice versa.

[0315] As used herein, relational terms such as "first" and "second" and numbering devices such as "a", "b" may be used solely to distinguish one entity or element from another entity or element without requiring or implying any physical or logical relationship or order between such entities or elements.

[0316] General

[0317] All statements citing the principles, aspects, and embodiments of the present disclosure and specific examples thereof herein are intended to cover equivalents in structure and function. In addition, such equivalents include currently known equivalents and equivalents developed in the future, i.e., any element of the performance of the same function developed, regardless of structure.

[0318] It should be understood that the present disclosure, which can be modified by omitting, adding, or replacing elements with equivalent functional elements, provides many applicable inventive concepts that can be embodied in various specific contexts. The specific embodiments discussed are merely illustrations of specific ways to make and use the concepts disclosed herein, and do not limit the scope of the present disclosure. On the contrary, the general principles set forth herein are considered to be merely illustrations of the scope of the present disclosure.

[0319] Obviously, various modifications and variations including substitutions, modifications, and equivalents will be apparent to those skilled in the relevant art in light of this specification, and modifications may be made to the embodiments disclosed herein as defined in the appended claims without departing from the invention.

[0320] Accordingly, the specification and embodiments disclosed herein should be considered as examples only, with the true scope of the disclosure being indicated by the following claims.

Claims

1. A communication method, characterized in that: include: The PCF provides one or more user routing policy rules to the user equipment; Each of the one or more user routing policy rules includes a list of routing descriptors, each routing descriptor includes a routing descriptor priority value and one or more of a location information element and a time information element, the routing descriptor priority value determines the priority of the routing descriptor, and the location information element and the time information element respectively determine the location and time period for applying the routing descriptor.

2. The method according to claim 1, characterized in that: The location information element comprises at least one of: a geographic location specified by a 2D and / or 3D coordinate system, a geographic location specified by an identifier of a geographic area of ​​a mapping system, a RAN address, a cell identifier, a tracking area identifier TAI, a registration area identifier, and / or an indication that at least one of the rules is always taken into account.

3. The method according to claim 1 or 2, characterized in that: The time information element includes at least one of the following: time of day, date, day of the week, day of the month, month, year, time period, the time period specifies at least one of the above time elements to start the time period and / or specifies at least one of the above time elements to end the time period, loops, and / or always considers an indication of the at least one rule.

4. The method according to any one of claims 1 to 3, characterized in that: The routing descriptor further includes at least one of the following: Session continuity SSC mode, network slice selection, data network name DNN selection, and non-seamless offload indication and / or access type preference.

5. The method according to any one of claims 1 to 3, characterized in that: The user routing policy rules are used for background data transmission.

6. The method according to claim 1, characterized in that The method further comprises: The PCF creates the one or more URSP rules.

7. The method according to any one of claims 1 to 6, characterized in that: Further includes When at least one of the time information element constraint and the location information element constraint is violated, the policy control function network element requests the session management function network element to initiate a release procedure of the protocol data unit session.

8. A communication method, characterized in that: include: The user equipment receives one or more user routing selection policy rules provided by the policy control function entity; Each of the one or more user routing policy rules includes a list of routing descriptors, each routing descriptor includes a routing descriptor priority value and one or more of a location information element and a time information element, the routing descriptor priority value determines the priority of the routing descriptor, and the location information element and the time information element respectively determine the location and time period for applying the routing descriptor.

9. The method according to claim 8, characterized in that The location information element comprises at least one of: a geographic location specified by a 2D and / or 3D coordinate system, a geographic location specified by an identifier of a geographic area of ​​a mapping system, a RAN address, a cell identifier, a tracking area identifier TAI, a registration area identifier, and / or an indication that at least one of the rules is always taken into account.

10. The method according to claim 8 or 9, characterized in that: The time information element includes at least one of the following: time of day, date, day of the week, day of the month, month, year, time period, the time period specifies at least one of the above time elements to start the time period and / or specifies at least one of the above time elements to end the time period, loops, and / or always considers an indication of the at least one rule.

11. The method according to any one of claims 8 to 10, characterized in that: The routing descriptor further includes at least one of the following: Session continuity SSC mode, network slice selection, data network name DNN selection, and non-seamless offload indication and / or access type preference.

12. The method according to any one of claims 8 to 11, characterized in that: The user routing policy rules are used for background data transmission.

13. The method according to any one of claims 8 to 12, characterized in that: The method further comprises: When the time information element and the location information element are satisfied, the user equipment proposes a protocol data unit session.

14. The method according to any one of claims 8 to 13, characterized in that: When information conditional on at least one information element is included in the at least one rule and the UE does not satisfy the information included in the at least one rule, the UE cannot exchange packets according to the at least one rule; or When information conditional on the at least one information element is included in the at least one rule and the UE satisfies the information included in the at least one rule, the UE may exchange packets according to any constraint included in the at least one rule.

15. A device, characterized in that: The method comprises a processor coupled to a memory, wherein the processor is configured to execute the method according to any one of claims 1 to 14.

16. A system, characterized in that: Comprising means for performing the method according to any one of claims 1-14.

17. A non-transitory processor-readable medium, characterized in that The readable medium stores instructions which, when executed by one or more processors, cause the one or more processors to perform the method according to any one of claims 1-14.