Patent Description:
Currently the fifth generation ("<NUM>") of cellular systems, also referred to as New Radio (NR), is being standardized within the Third-Generation Partnership Project (3GPP). NR is developed for maximum flexibility to support multiple and substantially different use cases. These include enhanced mobile broadband (eMBB), machine type communications (MTC), ultra-reliable low latency communications (URLLC), side-link device-to-device (D2D), and several other use cases. The present disclosure relates generally to <NUM> but similar principles can be applied to earlier-generation Long Term Evolution (LTE) networks.

LTE is an umbrella term for so-called fourth-generation (<NUM>) radio access technologies developed within the Third-Generation Partnership Project (3GPP) and initially standardized in Release <NUM> (Rel-<NUM>) and Release <NUM> (Rel-<NUM>), also known as Evolved UTRAN (E-UTRAN). LTE is targeted at various licensed frequency bands and is accompanied by improvements to non-radio aspects commonly referred to as System Architecture Evolution (SAE), which includes Evolved Packet Core (EPC) network. LTE continues to evolve through subsequent releases.

An overall exemplary architecture of a network comprising LTE and SAE is shown in <FIG>. E-UTRAN <NUM> includes one or more evolved Node B's (eNB), such as eNBs <NUM>, <NUM>, and <NUM>, and one or more user equipment (UE), such as UE <NUM>. As used within the 3GPP standards, "user equipment" or "UE" means any wireless communication device (e.g., smartphone or computing device) that is capable of communicating with 3GPP-standard-compliant network equipment, including E-UTRAN as well as UTRAN and/or GERAN, as the third-generation ("<NUM>") and second-generation ("<NUM>") 3GPP RANs are commonly known.

As specified by 3GPP, E-UTRAN <NUM> is responsible for all radio-related functions in the network, including radio bearer control, radio admission control, radio mobility control, scheduling, and dynamic allocation of resources to UEs in uplink and downlink, as well as security of the communications with the UE. These functions reside in the eNBs, such as eNBs <NUM>, <NUM>, and <NUM>. Each of the eNBs can serve a geographic coverage area including one more cells, including cells <NUM>, <NUM>, and <NUM> served by eNBs <NUM>, <NUM>, and <NUM>, respectively.

The eNBs in the E-UTRAN communicate with each other via the X2 interface, as shown in <FIG>. The eNBs also are responsible for the E-UTRAN interface to the EPC <NUM>, specifically the S1 interface to the Mobility Management Entity (MME) and the Serving Gateway (SGW), shown collectively as MME/S-GWs <NUM> and <NUM> in <FIG>. Generally speaking, the MME/S-GW handles both the overall control of the UE and data flow between the UE and the rest of the EPC. More specifically, the MME processes the signaling (e.g., control plane) protocols between the UE and the EPC, which are known as the Non-Access Stratum (NAS) protocols. The S-GW handles all Internet Protocol (IP) data packets (e.g., data or user plane) between the UE and the EPC and serves as the local mobility anchor for the data bearers when the UE moves between eNBs, such as eNBs <NUM>, <NUM>, and <NUM>.

EPC <NUM> can also include a Home Subscriber Server (HSS) <NUM>, which manages user- and subscriber-related information. HSS <NUM> can also provide support functions in mobility management, call and session setup, user authentication and access authorization. The functions of HSS <NUM> can be related to the functions of legacy Home Location Register (HLR) and Authentication Centre (AuC) functions or operations.

HSS <NUM> can communicate with MMEs <NUM> and <NUM> via respective S6a interfaces, and with a user data repository (UDR) - labelled EPC-UDR <NUM> in <FIG> - via a Ud interface. EPC-UDR <NUM> can store user credentials after they have been encrypted by AuC algorithms. These algorithms are not standardized (i.e., vendor-specific), such that encrypted credentials stored in EPC-UDR <NUM> are inaccessible by any other vendor than the vendor of HSS <NUM>.

In addition, S-GWs <NUM> and <NUM> can communicate with a packet gateway (P-GW) <NUM> via respective S5 interfaces. P-GW <NUM> provides access to external Packet Data Networks (PDNs), such as PDN <NUM> shown in <FIG>. For example, PDN <NUM> can be the point of entry to (or exit from) EPC <NUM> of traffic for UE <NUM>. However, if UE <NUM> has multiple data sessions to multiple PDNs, UE <NUM> can be connected with multiple P-GWs but it will still be served by only one SGW (e.g., <NUM> or <NUM>). In some cases, P-GW <NUM> can also act as an Internet Protocol (IP) router with support for mobile-specific tunneling and signaling protocols. In some deployments, PDN <NUM> can include an IP Multimedia Subsystem (IMS).

P-GW <NUM> also communicates with a Policy and Charging Rules Function (PCRF) <NUM> over an S7 interface. PCRF <NUM> provides policy control decisions and charging control functionalities for users (e.g., UE <NUM>) operating in the LTE network. PCRF <NUM> also provides network control of service data flow detection, gating, quality of service (QoS), and flow-based charging (except credit management). PCRF <NUM> performs these functions (referred to collectively as "policy and charging control" or PCC) together with a Policy Control Enforcement Function (PCEF), which can be part of P-GW <NUM>. For example, PCRF <NUM> can communicate with the PCEF over the Gx interface as shown in <FIG>. More generally, these functions are part of a PCC architecture that is defined in 3GPP TS <NUM> (for EPC/LTE).

For example, as a packet data (e.g., IMS) session is being set up, signaling (e.g., SIP signaling) containing media requirements is exchanged between UE <NUM> and PDN <NUM>. At some time in the session establishment process, PCRF <NUM> receives those requirements from the PDN (e.g., an IMS P-CSCF) and makes decisions based on network operator rules. Such decisions can include Allowing or rejecting the media request, using new or existing packet data context for the media request, and checking the allocation of new resources against the maximum authorized for UE <NUM>. PCRF <NUM> communicates with PDN <NUM> over an RXi interface.

Users can be charged for services (e.g., packet data sessions) provided by the LTE network by either an online charging system (OCS) or an offline charging system (OFCS), shown collectively in <FIG> as OCS/OFCS <NUM>. A primary difference is that online charging can affect provisioning of services to users in real-time, while offline charging is applied after services are rendered and, thus, does not affect real-time provisioning. As in <FIG>, PCRF <NUM> communicates with OCS/OFCS <NUM> via respective Gy/Gz interfaces.

<FIG> shows a high-level view of an exemplary <NUM> network architecture, including a Next Generation Radio Access Network (NG-RAN) <NUM> and a <NUM> Core (5GC) <NUM>. As shown in the figure, NG-RAN <NUM> can include gNBs <NUM> (e.g., 210a,b) and ng-eNBs <NUM> (e.g., 220a,b) that are interconnected with each other via respective Xn interfaces. The gNBs and ng-eNBs are also connected via the NG interfaces to 5GC <NUM>, more specifically to the AMF (Access and Mobility Management Function) <NUM> (e.g., AMFs 230a,b) via respective NG-C interfaces and to the UPF (User Plane Function) <NUM> (e.g., UPFs 240a,b) via respective NG-U interfaces. Moreover, the AMFs 230a,b can communicate with one or more policy control functions (PCFs, e.g., PCFs 250a,b) and network exposure functions (NEFs, e.g., NEFs 260a,b). The AMFs, UPFs, PCFs, and NEFs are described further below.

Each of the gNBs <NUM> can support the NR radio interface including frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof. In contrast, each of ng-eNBs <NUM> can support the LTE radio interface but, unlike conventional LTE eNBs (such as shown in <FIG>), connect to the 5GC via the NG interface. Each of the gNBs and ng-eNBs can serve a geographic coverage area including one more cells, including cells 211a-b and 221a-b shown as exemplary in <FIG>. Depending on the particular cell in which it is located, a UE <NUM> can communicate with the gNB or ng-eNB serving that particular cell via the NR or LTE radio interface, respectively.

In <NUM> networks (e.g., in 5GC), conventional peer-to-peer interfaces and protocols (e.g., in LTE/EPC networks) are modified by a so-called Service Based Architecture (SBA) in which Network Functions (NFs) provide one or more services to one or more service consumers. This can be done, for example, by Hyper Text Transfer Protocol/Representational State Transfer (HTTP/REST) application programming interfaces (APIs). In general, the various services are self-contained functionalities that can be changed and modified in an isolated manner without affecting other services. Furthermore, the services are composed of various "service operations", which are more granular divisions of the overall service functionality. In order to access a service, both the service name and the targeted service operation must be indicated. The interactions between service consumers and producers can be of the type "request/response" or "subscribe/notify".

3GPP specifications define an Access Traffic Steering, Switching and Splitting (ATSSS) feature that enables a Multi-Access (MA) Packet Data Unit (PDU) Connectivity Service, in which a UE can exchange PDUs with a data network by simultaneously using one 3GPP access network and one non-3GPP access network. As defined in 3GPP TS <NUM> (vl6. <NUM>) section <NUM>. <NUM>, a PCF in the 5GC is informed of ATSSS capabilities (e.g., Steering Mode and Steering Functionality) of a UE MA PDU Session by a session management function (SMF) in the 5GC.

The MA PDU Session Control information in the PCC rules is used by the SMF to create ATSSS rules for the UE. The ATSSS rules are sent to UE when the MA PDU Session is created or updated by the SMF/PCF. This is described in more detail in 3GPP TS <NUM> (vl6. <NUM>) and <NUM> (vl <NUM>. The ATSSS rules sent by SMF to the UE includes various types of traffic descriptor information. However, certain aspects of the traffic descriptors are not directly available to the SMF, which can create various problems, issues, and/or difficulties.

"<NPL>, discloses that during the establishment of a MA PDU session and if dynamic PCC is to be used for the MA PDU session, the PCF may take ATSSS policy decisions and create PCC rules that contain ATSSS policy control information, which determines how the uplink and the downlink traffic of the MA PDU Session should be distributed across the 3GPP and non-3GPP accesses. If dynamic PCC is not deployed, local policy in SMF is used. The SMF receives the PCC rules with ATSSS policy control information and maps these rules into (a) ATSSS rules, which are sent to UE, and (b) N4 (reference point between the SMF and the UPF) rules, which are sent to UPF. The ATSSS rules is a prioritized list of rules, which are applied by the UE to enforce the ATSSS policy in the uplink direction and the N4 Rules are applied by the UPF to enforce the ATSSS policy in the downlink direction. The ATSSS rules are sent to UE with a NAS message when the MA PDU Session is created or when they are updated by the SMF, e.g. after receiving updated/new PCC rules from the PCF. Similarly, the N4 are sent to UPF when the MA PDU Session is created or when they are updated by SMF.

"<NPL>, discloses a Stage <NUM> policy and charging control framework for a <NUM> system. The policy and charging control framework encompasses the following high level functions: Flow Based Charging for network usage, including charging control and online credit control, for service data flows; Policy control for session management and service data flows (e.g. gating control, QoS control, etc.); Management for access and mobility related policies; Management for UE access selection and PDU Session selection related policies.

According to aspects of the present disclosure, a method performed by a policy control function, PCF, of a communication network, a method performed by a session management function, SMF, of a communication network, and non-transitory computer readable media are provided according to the independent claims. Preferred embodiments are recited in the dependent claims.

Embodiments of the present disclosure provide specific improvements to management of policies and/or rules for use of applications in a communication network, such as by facilitating solutions to overcome exemplary problems summarized above and described in more detail below.

Exemplary embodiments include methods (e.g., procedures) performed by a policy control function (PCF) for a communication network (e.g., EPC, 5GC). The PCF can be hosted and/or provided by one or more network nodes in or associated with the communication network.

These exemplary methods can include, during establishment of a PDU session for a UE, determining one or more UE application descriptors that correspond to a network application identifier (Appld) of a service data flow (SDF) template for the PDU session. Each UE application descriptor includes a first identifier (OSId) of a UE-supported operating system (OS), and a second identifier (OSAppId) of an application for the UE-supported OS identified by the first identifier. These exemplary methods can also include sending policy rules for the PDU session to a session management function (SMF) of the communication network. The policy rules include the UE application descriptors.

In some embodiments, these exemplary methods can also include receiving, from the SMF, a request for the policy rules for the PDU session. In such embodiments, the request can include the SDF template, including the network application identifier (AppId). The policy rules can be sent in response to the request. In some embodiments, the request also includes an indication that the requested policy rules are for a multi-access (MA) PDU session and the policy rules include Access Traffic Steering, Switching, and Splitting (ATSSS) information.

In some embodiments, these exemplary methods can also include determining identifiers of one or more UE-supported OS during registration of the UE in the communication network, and storing the determined identifiers in a user data repository (UDR) of the communication network.

In some of these embodiments, determining the identifiers can include one of the following: receiving the identifiers from the UE, or deriving the identifiers based on a permanent equipment identifier (PEI), of the UE, that was obtained from an access and mobility management function (AMF) of the communication network.

In some embodiments, determining the UE application descriptors can include various operations, including: mapping the network application identifier to one or more OS identifiers and corresponding one or more OS-specific application identifiers; obtaining identifiers of one or more UE-supported OS; selecting, as the first identifiers, the mapped OS identifiers that match the obtained identifiers of UE-supported OS; and selecting, as the second identifiers, the mapped OS-specific application identifiers that correspond to the selected first identifiers.

In some of these embodiments, the obtaining the identifiers can be further represented by various sub-operations including: retrieving the identifiers of the one or more UE-supported OS from a user data repository (UDR) of the communication network; when the identifiers are unavailable from the UDR, determining the identifiers based on a permanent equipment identifier (PEI) of the UE obtained from the SMF; and when the identifiers cannot be determined based on the PEI, selecting identifiers of OS that are commonly supported by UEs operating in the communication network.

In some of these embodiments, these exemplary method can also include the additional operations of: locally storing the identifiers of the one or more UE-supported OS retrieved from the UDR; subsequently receiving, from the SMF, a request for updated policy rules for the PDU session, wherein the request includes an updated network application identifier; determining one or more updated UE application descriptors based on the updated network application identifier and the locally stored identifiers; and sending, to the SMF, updated policy rules including the updated UE application identifiers.

In certain embodiments, the UE application descriptions (e.g., included in the policy rules sent) can exclude respective versions of the identified UE-supported OS and respective versions of the identified applications.

Other embodiments include methods (e.g., procedures) performed by a session management function (SMF) for a communication network (e.g., 5GC). The SMF can be hosted and/or provided by one or more network nodes in or associated with the communication network.

These exemplary methods can include sending, to a PCF of the communication network, a second request for policy rules for a PDU session for a UE. The second request includes a service data flow (SDF) template that includes a network application identifier (AppId) associated with the PDU session. These exemplary methods can include receiving policy rules for the PDU session from the PCF. The policy rules can include one or more UE application descriptors that correspond to the network application identifier. Each UE application descriptor includes a first identifier (OSId) of a UE-supported operating system (OS) and a second identifier (OSAppId) of an application for the UE-supported OS identified by the first identifier. These exemplary methods can also include sending, to the UE, PDU session rules that include the one or more UE application descriptors. In some embodiments, the PDU session rules are for Access Traffic Steering, Switching, and Splitting (ATSSS).

In some embodiments the UE application descriptions (e.g., included in the policy rules received) can exclude respective versions of the identified UE-supported OS and respective versions of the identified applications.

According to one aspect, these exemplary methods include receiving a first request to establish the PDU session for the UE. The first request includes an indication that the requested PDU session is a multi-access (MA) PDU session. The second request includes an indication that the policy rules are for a MA PDU session.

In some embodiments, these exemplary methods can also include: sending, to the PCF, a third request for updated policy rules for the PDU session, wherein the third request includes an updated network application identifier; and receiving, from the PCF, updated policy rules including one or more updated UE application identifiers that correspond to the updated network application identifier.

Other embodiments also include PCFs and SMFs that are configured to perform operations (e.g., using processing circuitry) corresponding to any of the exemplary methods described herein. Other embodiments also include non-transitory, computer-readable media storing computer-executable instructions that, when executed by processing circuitry associated with such PCFs and SMFs, configure the same to perform operations corresponding to any of the exemplary methods described herein.

These and other described embodiments facilitate a single configuration point in the network for application descriptor (e.g., OSId+OSAppId) information related to a UE. For example, AppId to OSAppId mapping is centralized in the PCF. Another benefit is that the application descriptors included in the ATSSS rules delivered to the UE match the OS(s) requirements of the UE, such that the UE is neither under- nor over-provisioned.

These and other objects, features, and advantages of embodiments of the present disclosure will become apparent upon reading the following Detailed Description in view of the Drawings briefly described below.

Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

The steps of any methods and/or procedures disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein can be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments can apply to any other embodiments, and vice versa. Other objects, features, and advantages of the enclosed embodiments will be apparent from the following description.

Furthermore, the following terms are used throughout the description given below:.

In the present disclosure, the term "service" is used generally to refer to a set of data, associated with one or more applications, that is to be transferred via a network with certain specific delivery requirements that need to be fulfilled in order to make the applications successful. In the present disclosure, the term "component" is used generally to refer to any component needed for the delivery of the service. Examples of components are RANs (e.g., E-UTRAN, NG-RAN, or portions thereof such as eNBs, gNBs, base stations (BS), etc.), CNs (e.g., EPC, 5GC, or portions thereof, including all type of links between RAN and CN entities), and cloud infrastructure with related resources such as computation and storage. In general, each component can have a "manager", a term used generally to refer to an entity that can collect historical information about utilization of resources as well as provide information about the current and the predicted future availability of resources associated with that component (e.g., a RAN manager).

As briefly mentioned above, Access Traffic Steering, Switching and Splitting (ATSSS) rules for a Multi-Access (MA) PDU session that are sent by an SMF to a UE can include various types of traffic descriptor information. However, certain aspects of the traffic descriptors are not directly available to the SMF, which can create various problems, issues, and/or difficulties. This discussed in more detail below after the following description of <NUM> network architecture.

<FIG> shows an exemplary non-roaming <NUM> reference architecture with service-based interfaces and various 3GPP-defined network functions (NFs) within the control plane (CP). These include:.

The Unified Data Management (UDM) function shown in <FIG> is similar to the HSS in LTE/EPC networks discussed above. UDM supports Generation of 3GPP authentication credentials, user identification handling, access authorization based on subscription data, and other subscriber-related functions. To provide this functionality, the UDM uses subscription data (including authentication data) stored in the 5GC unified data repository (UDR) shown in <FIG>. The UDR (which has an Nudr interface) supports storage and retrieval of policy data by the PCF, as well as storage and retrieval of application data by NEF. Application data can also be placed into the UDR by the external AFs, via the Network Exposure Function (NEF), in order to be made available to whichever <NUM> NFs need - and are authorized to request - subscriber-related information.

PCF control of ATSSS for a detected service data flow (SDF) is enabled by including Multi-Access PDU (MA PDU) Session Control information in the relevant PCC rule. This allows the PCF to control the following capabilities:.

Other information in the PCC Rule applies to the SDF itself and is generally independent of Access Type used for a packet. The MA PDU Session Control information in the PCC rules is used by the SMF to create ATSSS rules for the UE. The ATSSS rules are sent to UE when the MA PDU Session is created or updated by the SMF/PCF. This is described in more detail in 3GPP TS <NUM> and <NUM>.

According to 3GPP TS <NUM>, the traffic to be split/switched/steered is identified by the SDF template in the PCC rule. The SDF template is identified by either a list of SDF filters or an application identifier (AppId) that references the corresponding application detection filter for the detection of the service data flow.

According to 3GPP TS <NUM>, clause <NUM>. <NUM>, an ATSSS rule sent to the UE includes traffic descriptor information that can include at least one of the following descriptors:.

It is further specified that an application descriptor includes the following information:.

The UE may check received OSId(s) to determine if this information that matches OS(s) installed in the UE. However, it is not specified how the SMF obtains the OSId and OSAppId to be provided as part of traffic descriptor information in the ATSSS rule. Also, note that the OSAppId is different than an AppId that may be included in the SDF template of the PCC rule. While OSAppId is intended to be used by the UE, AppId is intended to be used by the network. The policy information provided from the PCF to the UE can include the following policies:.

When the PCF determines to send the UE any of these policies that contain an application descriptor it will check if the OSId(s) of the UE is known. To determine the operating system of the UE, the PCF may use a Permanent Equipment Identifier (PEI) for the UE that is provided by the AMF and/or an OSId provided by the UE. These parameters can be received from the UE in the UE Policy Container (e.g., OSId(s)) from the AMF in the Npcf_UEPolicyControl_Create response message. If the PEI or the OSId is available to the PCF, the PCF stores them in the UDR using Nudr_DM_Create including DataSet "Policy Data" and Data Subset "UE context policy control data".

If the PCF determines the operating system of the UE and if the PCF should deliver UE policies that contain application descriptors, then the Traffic Descriptors of such UE Policies include the OSAppID associated with the operating system determined by the PCF for the UE. On the other hand, if the PCF is unable to determine the UE operating system, and if the PCF should deliver UE Policies that contain application descriptors, then the Traffic Descriptors include multiple OSAppIDs, each associated with different UE operating systems supported by the network operator implementation.

The PCF selects the ANDSP, URSP and V2X policies applicable for each UE based on local configuration and operator policies. UE policies are provided from the PCF to the AMF via N15/Namf interface and then from AMF to the UE via the N1 interface as described in 3GPP TS <NUM> clause <NUM>. The AMF shall not change the information provided by PCF.

The SMF will include the OSId and OSAppld as part of the ATSSS rule provided to the UE when the traffic descriptor refers to an Application descriptor. However, OSId and OSAppld are not available at the SMF. Instead the SMF will get an AppId configured in the PCF that is provided as part of the SDF Template in the PCC rule. This AppId provided as part of the SDF template is a reference to a corresponding application detection filter for the detection of the service data flow.

In order to provide the required information to the UE, SMFs deployed in the network would be required to have mapping tables between the AppId included in the PCC Rules SDF template and the OSId and OSAppld. Since the UE can handle different Operating Systems, this mapping relation could be one-to-many. This is inefficient as it requires configuration information in both PCF and SMF, i.e., the PCF needs to configure the AppId value and the SMF needs to configure the AppId to one or more OSAppId values. In addition, configured mapping tables in all deployed SMFs with ATSSS capabilities kept up-to-date with information about the mapping relation between AppId and OSAppId.

In addition, if the OSId for the UE is unclear or ambiguous, current solutions require the SMF to provide ATSSS rules with one or more application descriptors, each with one possible OSAppId that corresponds to an AppId. Based on this information, the UE must resolve the supported application identifier for its supported OS among all the received OSAppIds. This procedure can be inefficient and/or demanding in terms of processing requirements on the UE and various NFs, particularly SMF.

Accordingly, embodiments of the present disclosure provide techniques that facilitate a single configuration point in the network for the OSId+OSAppId information related to a UE. In addition, embodiments facilitate a PCF, selected for handling SM Policy Context association, to obtain accurate OSId+OSAppId for a registered UE from a common storage point, thereby avoiding over-provisioning the UE with ATSSS rule information that will never be invoked by the UE. In other words, the application descriptors included in the ATSSS rules delivered to the UE match the OS(s) requirements of the UE. In addition, embodiments remove requirements for SMFs with ATSSS capabilities to keep updated configuration mapping tables with relations between AppIds in SDF templates and corresponding OSId(s)/OSAppId(s). In other words, AppId to OSAppId mapping is centralized in the PCF.

Various embodiments enable the PCF to provide OSId and OSAppId information as part of the PCC Rule following a high-level procedure described as follows. As per current procedures, during the UE registration, the PCF checks if OSId(s) are provided by the UE. If not, the PCF checks if the Permanent Equipment Identifier (PEI) is available as a basis for deriving OSId. If OSId is obtained from the UE or from the PEI, PCF stores it in the UDR using the Nudr_DM_Create including the DataSet "Policy Data" and Data Subset "UE context policy control data".

During the PDU Session Establishment and if ATSSS feature is supported, the PCF will check whether PCC Rules including ATSSS policy should be provided (e.g., as defined in 3GPP TS <NUM>, clause <NUM>. If so and if a corresponding traffic descriptor refers to an application descriptor, in addition to the current procedures for the PCC Rule derivation, the PCF performs various operations as part of the PCC Rule derivation. First, the PCF retrieves the list of OSIds associated with the UE from the UDR by using the Nudr_DM_Query including the DataSet "Policy Data" and Data Subset "UE context policy control data". Second, for the retrieved OSIds, the PCF obtains the configured OSAppIds that correspond to the AppId included in the SDF template, and the PCF includes the list of OSId+OSAppId within the PCC Rule being derived.

On the other hand, if the list of OSIds is not available in the UDR and the PCF cannot derive the OSId from the PEI, the PCF may include within the PCC rule the configured information about the available OSId(s)/OSAppId(s) that corresponds to the AppId included in the SDF template. When the SMF receives the PCC rules related to ATSSS policy from the PCF, it will derive the ATSSS Rules based on the OSId+OsAppId obtained directly from the PCC Rule. The SMF will send to the UE, as part of the ATSSS rules, all the combinations received in the PCC Rule.

The following explanation also illustrates high-level operation of various embodiments. A PCF can store the OSAppId associated with an OSId in the UDR at UE Registration. In addition, using Npcf_SMPolicyControl_Create operation, the PCF can obtain a configured list of OSId+AppId related to that UE as well as the OSId(s) related to that UE. However, if the information is not available in the UDR in response to a Npcf_SMPolicyControl_Create operation, the PCF can derive the necessary OSId from the PEI provided by the SMF and obtain the OSAppId related to that OSId. Furthermore, based on operator policies, the PCF can decide to send the configured list of OSId and OSAppId for that UE instead of the information retrieved from the UDR. The PCF can include the OSId and OSAppId in the PCC Rule as part of the MA PDU Session Control information. In addition, the SMF can include the application descriptor information in the PCC rule, received from the PCF, in the ATSSS rule sent to the UE.

<FIG> is a flow diagram of an exemplary procedure for ATSS policy control in a 5GC, according to various exemplary embodiments of the present disclosure. The exemplary procedure involves various operations by, and interactions between, a UE <NUM>, an AMF <NUM>, an SMF <NUM>, a PCF(UE) <NUM> (which includes PCF(UE) and PCF(SM) parts), and a UDR <NUM>. For brevity, these devices, nodes, or functions will be referred to without their reference numbers in the following description. Although <FIG> shows numbered operations, the numbers are intended to facilitate description and neither require nor imply a particular order of the operations. In other words, the operations shown in <FIG> can be performed in a different order than shown and can be combined and/or divided into operations different than the ones shown.

In operation <NUM>, the AMF, at UE registration, invokes the Npcf_UEPolicy-Control_Create request and includes in the request the PEI and UEPolicyRequest container delivered by the UE. The UEPolicyRequest container may include the UE OSId(s).

In operation <NUM>, the PCF(UE) interacts with the UDR via Nudr_DataRepository to retrieve the UE Policy Set information, which can include the UE OSId(s). The PCF uses this retrieved information to derive UE Policies to deliver to the UE. The PCF can base the determination of application information included in the derived UE Policies on the following information:.

In case the PCF retrieves OSId(s) in operation <NUM>, the PCF can also store the retrieved UE OSId(s) in the UDR in the UP Policy Set.

In operation <NUM>, the PCF responds to the AMF's request in operation <NUM> with the Npcf_UEPolicyControl_Create Response operation. Subsequently, an end-to-end procedure for UE policies delivery to the UE takes place, as illustrated by the dashed box and followed by the final delivery of UE policies by AMF to UE. After the UE requests the establishment of a MA PDU session (shown in dashed box after policy delivery), in operation <NUM> the SMF sends a Npcf_SMPolicyControl_Create Request message to the PCF, including the indication that the PDU session is for a MA PDU session. In operation <NUM>, the PCF fetches Session Management (SM) data from the UDR using a Nudr_DataRepository_Query, and in combination with internal policies, determines the PCC rules to deliver to the UE.

In operation <NUM>, when the derived PCC rules include ATSSS information, and the SDF Template of the PCC rules includes an AppId, the PCF performs the following operations to provide the SMF with an application descriptor to include in the ATSSS rule. First, the PCF retrieves the mapping of the AppId into the one or more OSId+OSAppId combinations from internal configuration. Based on operator policies, the PCF invokes Nudr_DataRepository_Query request to retrieve from the UE Policy Set the UE OSId(s) stored at the UDR in operation <NUM>. Next, if the UE OSId information is available from the UDR, the PCF includes in the PCC rule the OSId+OSAppId pairs that match the retrieved UE OSId(s). Alternately, if the UE OSId information is not available from the UDR, the PCF can derive the OSId(s) from the PEI, and include in the PCC rule the OSId+OSAppId pairs that match the derived UE OSId(s). However, if the UE OSId cannot be retrieved or derived from PEI, or if required by operator policies, the PCF includes in the PCC rule the list of OSId+OSAppId pairs retrieved in operation <NUM> with respect to UE policies.

In operation <NUM>, the PCF sends a Npcf_SMPolicyControl_Create response to the SMF including ATSSS information in the corresponding PCC rules. For the PCC rules that include an AppId in the SDF template, the PCC rule also includes the corresponding application descriptors (OSId+OSAppId). Subsequently, the PCC ATSSS rules are delivered to the UE for use during an MA PDU session.

A PCC rule update can be required, e.g., due to a MA PDU session modification (shown as dashed box). In operation <NUM>, the SMF send an NPCF_SMPolicyControl_Update_Request to the PCF(SM), which has cached or stored information previously retrieved from UDR. The PCF(SM) then derives new/modified PCC rules with ATSSS information that include application descriptions, if required. These can be derived in the same manner as discussed above in relation to operation <NUM>. In operation <NUM>, the PCF delivers the updated PCC rules to SMF via a NPCF_SMPolicyControl_Update_Response, and the updated PCC ATSSS rules are delivered to the UE in the same manner as discussed above.

Although <FIG> shows an exemplary procedure involving a 5GC, similar principles can be employed for EPC ATSSS policy control procedures. For example, the signal flow shown in <FIG> can also be applied to EPC with PCF replaced by PCRF, AMF replaced by MME, SMF replaced PCEF (or by PGW-C when Control Plane and User Plane are split), UDR replaced by EPC-UDR, etc. <FIG> shows an exemplary arrangement of such elements.

Aspects of the techniques described herein can also be embodied in the text of a 3GPP specification. The following exemplary text for 3GPP TS <NUM> (Rel-<NUM>) relates to certain aspects of various embodiments described above.

As specified in TS <NUM> [<NUM>], the Access Traffic Steering, Switching and Splitting (ATSSS) feature is an optional feature that may be supported by the UE and the 5GC network. The ATSSS feature enables a multi-access PDU Connectivity Service, which can exchange PDUs between the UE and a data network by simultaneously using one 3GPP access network and one non-3GPP access network.

The PCF is informed of the ATSSS capabilities of a MA PDU Session by the SMF, as defined in TS <NUM> [<NUM>] clause <NUM>. The ATSSS capabilities are both the Steering Mode and the Steering Functionality.

The PCF control of Access Traffic Steering, Switching and Splitting for a detected service data flow (SDF) is enabled by including Multi-Access PDU (MA PDU) Session Control information in the PCC rule. This allows the PCF to control:.

The rest of the information in the PCC Rule apply to the SDF as such and are not dependent on what Access Type is used for a packet.

The MA PDU Session Control information in the PCC rules is used by the SMF in order to create applicable N4 rules for the UPF and ATSSS rules for the UE, as described in TS <NUM> [<NUM>]. The ATSSS rules are sent to UE via NAS when the MA PDU Session is created or updated by the SMF/PCF, as described in TS <NUM> [<NUM>] and TS <NUM> [<NUM>].

When MA PDU Session Control Information is provided to the SMF within a PCC Rule, the (H-)PCF provides both the Service Data Flow template to identify a Service Data Flow in the UPF and if the Service Data Flow template includes an application identifier, then the OSAppId(s) and associated OSId to identify the application traffic in the UE is also included.

The (H-)PCF may use the OSid stored in the UDR as DataSet "Policy Data" and Data Subset "UE context policy control data" to determine the OSAppId(s) supported by the OSid. If no OSid is available in the UDR; the (H-)PCF may use the PEI to determine the OSid supported by the UE. If the (H-)PCF does not determine the OSId supported by the UE, the (H-)PCF may provide multiple instances of each OSAppId, each OSAppId is associated to the supported OSId according to operator policies in the (H-)PCF.

The (H-)SMF includes the OSId and OSAppId(s) received from the PCF as part of the MA PDU Session information in the PCC Rule within the Traffic Descriptors in the ATSSS rule. The (H-)SMF includes the SDF templates in the ATSSS Rule as Traffic Descriptors if the OSId(s) and OSAppId(s) are not provided in the MA PDU Session Control Information within the PCC Rule. The PCF may also provide URSP rules to the UE for instructing the UE to establish a MA PDU Session, as described in clause <NUM>.

The PCF control of PDU session level Usage Monitoring depending on what access type is used to carry the traffic is enabled by providing Usage Monitoring control related information per access in the PDU Session related policy control information (as described in clause <NUM>).

If the MA PDU session is capable of MPTCP and ATSSS-LL with any Steering Mode in the downlink and MPTCP and ATSSS-LL with Active-Standby in the uplink, then the PCF shall provide a PCC Rule for non-MPTCP traffic. This PCC Rule contains a "match all" SDF template, the lowest precedence, the Steering Functionality set to "ATSSS-LL" and the Steering Mode set to "Active-Standby" for the uplink direction, and the Steering Functionality set to "ATSSS-LL" and the Steering Mode set to any supported steering mode for the downlink direction.

If the MA PDU session is capable of MPTCP and ATSSS-LL with Active-Standby in the uplink and downlink, then the PCF shall provide a PCC Rule for non-MPTCP traffic. This PCC Rule contains a "match all" SDF template, the lowest precedence, the Steering Functionality set to "ATSSS-LL" and the Steering Mode set to "Active-Standby" for the uplink direction and the downlink direction.

These PCC Rules are used by the SMF to generate an ATSSS rule for the UE and an N4 rule for the UPF to route the non-MPTCP traffic of the MA PDU Session in the uplink and downlink direction respectively. NOTE: The PCF can also use the ATSSS capability of the MA PDU Session to provide PCC Rules containing SDF template for some specific non-MPTCP traffic other than the PCC Rule containing a "match all" SDF template. This allows the operator to apply different policies e.g. charging key to non-MPTCP traffic other than the non-MPCTP traffic matching the "match all" PCC Rule.

In conjunction with the above description, the following exemplary entry can be added to Table <NUM>. <NUM> in section <NUM>. <NUM> of 3GPP TS <NUM>, along with the subsequent exemplary description.

The Application descriptors provides one or several instances of the OSId and OSAppId combination. It is used by the UE to identify the application traffic to apply the Steering Functionality and the Steering mode.

The embodiments described above can be further illustrated by the exemplary methods (e.g., procedures) shown in <FIG>, described below. For example, features of various embodiments discussed above are included in various operations of the exemplary methods shown in <FIG>. Although these exemplary methods are illustrated by specific blocks in particular orders, the operations corresponding to the blocks can be performed in different orders than shown and can be combined and/or divided into blocks and/or operations having different functionality than shown. The exemplary methods shown in <FIG> can be used cooperatively (e.g., with each other and/or with other exemplary methods, such as shown in <FIG>) to provide benefits, advantages, and/or solutions to problems described herein. Optional blocks and/or operations are indicated by dashed lines.

In particular, <FIG> illustrates an exemplary method (e.g., procedure) for a policy control function (PCF) of a communication network (e.g., 5GC), according to various exemplary embodiments of the present disclosure. The PCF can be hosted and/or provided by one or more network nodes in or associated with the communication network, such as described elsewhere herein.

The exemplary method can include the operations of block <NUM>, in which the PCF can, during establishment of a PDU session for a UE, determine one or more UE application descriptors that correspond to a network application identifier (AppId) of a service data flow (SDF) template for the PDU session. Each UE application descriptor includes a first identifier (OSId) of a UE-supported operating system (OS), and a second identifier (OSAppId) of an application for the UE-supported OS identified by the first identifier. The exemplary method can also include the operations of block <NUM>, in which the PCF can send policy rules for the PDU session to a session management function (SMF) of the communication network. The policy rules include the UE application descriptors.

In some embodiments, the exemplary method can also include the operations of block <NUM>, in which the PCF can receive, from the SMF, a request for the policy rules for the PDU session. In such embodiments, the request can include the SDF template, including the network application identifier (AppId). The policy rules can be sent (e.g., in block <NUM>) in response to the request. In some embodiments, the request also includes an indication that the requested policy rules are for a multi-access (MA) PDU session and the policy rules (e.g., sent in block <NUM>) include Access Traffic Steering, Switching, and Splitting (ATSSS) information.

In some embodiments, the exemplary method can also include the operations of blocks <NUM>-<NUM>. In block <NUM>, the PCF can determine identifiers of one or more UE-supported OS during registration of the UE in the communication network. In block <NUM>, the PCF can store the determined identifiers in a user data repository (UDR) of the communication network.

In some of these embodiments, determining the identifiers in block <NUM> can include the operations of either sub-block <NUM> or sub-block <NUM>. In sub-block <NUM>, the PCF can receive the identifiers from the UE. In sub-block <NUM>, the PCF can derive the identifiers based on a permanent equipment identifier (PEI), of the UE, that was obtained from an access and mobility management function (AMF) of the communication network.

In some embodiments, determining the UE application descriptors in block <NUM> can include the operations of sub-blocks <NUM>-<NUM>. In sub-block <NUM>, the PCF can map the network application identifier to one or more OS identifiers and corresponding one or more OS-specific application identifiers. In sub-block <NUM>, the PCF can obtain identifiers of one or more UE-supported OS. In sub-block <NUM>, the PCF can select, as the first identifiers, the mapped OS identifiers that match the obtained identifiers of UE-supported OS. In sub-block <NUM>, the PCF can select, as the second identifiers, the mapped OS-specific application identifiers that correspond to the selected first identifiers.

In some of these embodiments, the obtaining operations of sub-block <NUM> can be further represented by sub-operations 542a-c. In 542a, the PCF can retrieve the identifiers of the one or more UE-supported OS from a user data repository (UDR) of the communication network. In 542b, the PCF can, when the identifiers are unavailable from the UDR, determine the identifiers based on a permanent equipment identifier (PEI) of the UE obtained from the SMF. In 542c, the PCF can, when the identifiers cannot be determined based on the PEI, select identifiers of OS that are commonly supported by UEs operating in the communication network.

In some of these embodiments, the exemplary method can also include the operations of blocks <NUM>-<NUM>. In block <NUM>, the PCF can locally store the identifiers of the one or more UE-supported OS retrieved from the UDR (e.g., in 542a). In block <NUM>, the PCF can subsequently receive, from the SMF, a request for updated policy rules for the PDU session, wherein the request includes an updated network application identifier. In block <NUM>, the PCF can determine one or more updated UE application descriptors based on the updated network application identifier and the locally stored identifiers. In block <NUM>, the PCF can send, to the SMF, updated policy rules including the updated UE application identifiers.

In certain embodiments, the UE application descriptions (e.g., included in the policy rules sent in block <NUM>) can exclude (e.g., not contain) respective versions of the identified UE-supported OS and respective versions of the identified applications.

In addition, <FIG> illustrates an exemplary method (e.g., procedure) for a session management function (SMF) for a communication network (e.g., 5GC), according to various exemplary embodiments of the present disclosure. The SMF can be hosted and/or provided by one or more network nodes in or associated with the communication network, such as described elsewhere herein.

The exemplary method can include the operations of blocks <NUM>-<NUM>. In block <NUM>, the SMF can send, to a PCF of the communication network, a second request for policy rules for a PDU session for a UE. The second request includes a service data flow (SDF) template that includes a network application identifier (AppId) associated with the PDU session. In block <NUM>, the PCF can receive policy rules for the PDU session from the PCF. The policy rules can include one or more UE application descriptors that correspond to the network application identifier. Each UE application descriptor includes a first identifier (OSId) of a UE-supported operating system (OS) and a second identifier (OSAppId) of an application for the UE-supported OS identified by the first identifier. In block <NUM>, the SMF can send, to the UE, PDU session rules that include the one or more UE application descriptors. In some embodiments, the PDU session rules are for Access Traffic Steering, Switching, and Splitting (ATSSS).

In some embodiments the UE application descriptions (e.g., included in the policy rules received in block <NUM>) can exclude (e.g., not contain) respective versions of the identified UE-supported OS and respective versions of the identified applications.

In some embodiments, the exemplary method can also include the operations of block <NUM>, where the SMF can receive a first request to establish the PDU session for the UE. The first request includes an indication that the requested PDU session is a multi-access (MA) PDU session. In such embodiments, the second request (e.g., sent in block <NUM>) includes an indication that the policy rules are for a MA PDU session.

In some embodiments, the exemplary method can also include the operations of blocks <NUM>-<NUM>. In block <NUM>, the SMF can send, to the PCF, a third request for updated policy rules for the PDU session, wherein the third request includes an updated network application identifier. In block <NUM>, the SMF can receive, from the PCF, updated policy rules including one or more updated UE application identifiers that correspond to the updated network application identifier.

Although the subject matter described herein can be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in <FIG>. For simplicity, the wireless network of <FIG> only depicts network <NUM>, network nodes <NUM> and 760b, and wireless devices (WDs) <NUM><NUM>, 710b, and 710c. In practice, a wireless network can further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node <NUM> and WD <NUM> are depicted with additional detail. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

The wireless network can comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network can be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network can implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable <NUM>, <NUM>, <NUM>, or <NUM> standards; wireless local area network (WLAN) standards, such as the IEEE <NUM> standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network <NUM> can comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

In different embodiments, the wireless network can comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that can facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

Base stations can be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and can then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node controlling a relay. A network node can also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Parts of a distributed radio base station can also be referred to as nodes in a distributed antenna system (DAS).

Further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs, S-GW, M-GW, etc.), core network functions (e.g., PCEF, PCRF, AMF, UPF, NEF, SMF, PCF, etc.), application functions (AF) associated with the core network, O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node can be a virtual network node as described in more detail below. More generally, however, network nodes can represent any suitable device (or group of devices) or function capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

Although network node <NUM> illustrated in the example wireless network of <FIG> can represent a device that includes the illustrated combination of hardware components, other embodiments can comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods and/or procedures disclosed herein. Moreover, while the components of network node <NUM> are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node can comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium <NUM> can comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node <NUM> can be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), which can each have their own respective components. In certain scenarios in which network node <NUM> comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components can be shared among several network nodes. For example, a single RNC can control multiple NodeB's. In such a scenario, each unique NodeB and RNC pair, can in some instances be considered a single separate network node. In some embodiments, network node <NUM> can be configured to support multiple radio access technologies (RATs). In such embodiments, some components can be duplicated (e.g., separate device readable medium <NUM> for the different RATs) and some components can be reused (e.g., the same antenna <NUM> can be shared by the RATs). Network node <NUM> can also include multiple sets of the various illustrated components for different wireless technologies integrated into network node <NUM>, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies can be integrated into the same or different chip or set of chips and other components within network node <NUM>.

Processing circuitry <NUM> can be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry <NUM> can include processing information obtained by processing circuitry <NUM> by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry <NUM> can comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide various functionality of network node <NUM>, either alone or in conjunction with other network node <NUM> components (e.g., device readable medium <NUM>). Such functionality can include any of the various wireless features, functions, or benefits discussed herein.

For example, processing circuitry <NUM> can execute instructions stored in device readable medium <NUM> or in memory within processing circuitry <NUM>. In some embodiments, processing circuitry <NUM> can include a system on a chip (SOC). As a more specific example, instructions (also referred to as a computer program product) stored in medium <NUM> can include instructions that, when executed by processing circuitry <NUM>, can configure network node <NUM> to perform operations corresponding to various exemplary methods (e.g., procedures) described herein.

In some embodiments, processing circuitry <NUM> can include one or more of radio frequency (RF) transceiver circuitry <NUM> and baseband processing circuitry <NUM>. In some embodiments, radio frequency (RF) transceiver circuitry <NUM> and baseband processing circuitry <NUM> can be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry <NUM> and baseband processing circuitry <NUM> can be on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device can be performed by processing circuitry <NUM> executing instructions stored on device readable medium <NUM> or memory within processing circuitry <NUM>. In alternative embodiments, some or all of the functionality can be provided by processing circuitry <NUM> without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.

Device readable medium <NUM> can comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that can be used by processing circuitry <NUM>. Device readable medium <NUM> can store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry <NUM> and, utilized by network node <NUM>. Device readable medium <NUM> can be used to store any calculations made by processing circuitry <NUM> and/or any data received via interface <NUM>. In some embodiments, processing circuitry <NUM> and device readable medium <NUM> can be considered to be integrated.

Interface <NUM> is used in the wired or wireless communication of signaling and/or data between network node <NUM>, network <NUM>, and/or WDs <NUM>. Interface <NUM> also includes radio front end circuitry <NUM> that can be coupled to, or in certain embodiments a part of, antenna <NUM>. Radio front end circuitry <NUM> can be connected to antenna <NUM> and processing circuitry <NUM>. Radio front end circuitry can be configured to condition signals communicated between antenna <NUM> and processing circuitry <NUM>. Radio front end circuitry <NUM> can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry <NUM> can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters <NUM> and/or amplifiers <NUM>. The radio signal can then be transmitted via antenna <NUM>. Similarly, when receiving data, antenna <NUM> can collect radio signals which are then converted into digital data by radio front end circuitry <NUM>. The digital data can be passed to processing circuitry <NUM>. In other embodiments, the interface can comprise different components and/or different combinations of components.

In certain alternative embodiments, network node <NUM> may not include separate radio front end circuitry <NUM>, instead, processing circuitry <NUM> can comprise radio front end circuitry and can be connected to antenna <NUM> without separate radio front end circuitry <NUM>. Similarly, in some embodiments, all or some of RF transceiver circuitry <NUM> can be considered a part of interface <NUM>. In still other embodiments, interface <NUM> can include one or more ports or terminals <NUM>, radio front end circuitry <NUM>, and RF transceiver circuitry <NUM>, as part of a radio unit (not shown), and interface <NUM> can communicate with baseband processing circuitry <NUM>, which is part of a digital unit (not shown).

Antenna <NUM> can include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna <NUM> can be coupled to radio front end circuitry <NUM> and can be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna <NUM> can comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, <NUM> and <NUM>. An omni-directional antenna can be used to transmit/receive radio signals in any direction, a sector antenna can be used to transmit/receive radio signals from devices within a particular area, and a panel antenna can be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna can be referred to as MIMO. In certain embodiments, antenna <NUM> can be separate from network node <NUM> and can be connectable to network node <NUM> through an interface or port.

Antenna <NUM>, interface <NUM>, and/or processing circuitry <NUM> can be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals can be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna <NUM>, interface <NUM>, and/or processing circuitry <NUM> can be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals can be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry <NUM> can comprise, or be coupled to, power management circuitry and can be configured to supply the components of network node <NUM> with power for performing the functionality described herein. Power circuitry <NUM> can receive power from power source <NUM>. Power source <NUM> and/or power circuitry <NUM> can be configured to provide power to the various components of network node <NUM> in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source <NUM> can either be included in, or external to, power circuitry <NUM> and/or network node <NUM>. For example, network node <NUM> can be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry <NUM>. As a further example, power source <NUM> can comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry <NUM>. The battery can provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, can also be used.

Alternative embodiments of network node <NUM> can include additional components beyond those shown in <FIG> that can be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node <NUM> can include user interface equipment to allow and/or facilitate input of information into network node <NUM> and to allow and/or facilitate output of information from network node <NUM>. This can allow and/or facilitate a user to perform diagnostic, maintenance, repair, and other administrative functions for network node <NUM>.

Furthermore, various network functions (NFs, e.g., SMF, PCF, UDR, AMF, etc.) described herein can be implemented with and/or hosted by different variants of network node <NUM>, including variants described above.

In some embodiments, a wireless device (WD, e.g., WD <NUM>) can be configured to transmit and/or receive information without direct human interaction. For instance, a WD can be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, smart phones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer-premise equipment (CPE), mobile-type communication (MTC) devices, Internet-of-Things (IoT) devices, vehicle-mounted wireless terminal devices, etc..

A WD can support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and can in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD can represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD can in this case be a machine-to-machine (M2M) device, which can in a 3GPP context be referred to as an MTC device. As one particular example, the WD can be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g., refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD can represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above can represent the endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, a WD as described above can be mobile, in which case it can also be referred to as a mobile device or a mobile terminal.

As illustrated, WD <NUM> includes antenna <NUM>, interface <NUM>, processing circuitry <NUM>, device readable medium <NUM>, user interface equipment <NUM>, auxiliary equipment <NUM>, power source <NUM> and power circuitry <NUM>. WD <NUM> can include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD <NUM>, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies can be integrated into the same or different chips or set of chips as other components within WD <NUM>.

Antenna <NUM> can include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface <NUM>. In certain alternative embodiments, antenna <NUM> can be separate from WD <NUM> and be connectable to WD <NUM> through an interface or port. Antenna <NUM>, interface <NUM>, and/or processing circuitry <NUM> can be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals can be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna <NUM> can be considered an interface.

Radio front end circuitry <NUM> is connected to antenna <NUM> and processing circuitry <NUM> and can be configured to condition signals communicated between antenna <NUM> and processing circuitry <NUM>. Radio front end circuitry <NUM> can be coupled to or a part of antenna <NUM>. In some embodiments, WD <NUM> may not include separate radio front end circuitry <NUM>; rather, processing circuitry <NUM> can comprise radio front end circuitry and can be connected to antenna <NUM>. Similarly, in some embodiments, some or all of RF transceiver circuitry <NUM> can be considered a part of interface <NUM>. Radio front end circuitry <NUM> can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry <NUM> can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters <NUM> and/or amplifiers <NUM>. The radio signal can then be transmitted via antenna <NUM>. Similarly, when receiving data, antenna <NUM> can collect radio signals which are then converted into digital data by radio front end circuitry <NUM>. The digital data can be passed to processing circuitry <NUM>. In other embodiments, the interface can comprise different components and/or different combinations of components.

Processing circuitry <NUM> can comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide WD <NUM> functionality either alone or in combination with other WD <NUM> components, such as device readable medium <NUM>. Such functionality can include any of the various wireless features or benefits discussed herein.

For example, processing circuitry <NUM> can execute instructions stored in device readable medium <NUM> or in memory within processing circuitry <NUM> to provide the functionality disclosed herein. More specifically, instructions (also referred to as a computer program product) stored in medium <NUM> can include instructions that, when executed by processing circuitry <NUM>, can configure WD <NUM> to perform operations corresponding to various exemplary methods (e.g., procedures) described herein.

In other embodiments, the processing circuitry can comprise different components and/or different combinations of components. In certain embodiments processing circuitry <NUM> of WD <NUM> can comprise a SOC. In some embodiments, RF transceiver circuitry <NUM>, baseband processing circuitry <NUM>, and application processing circuitry <NUM> can be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry <NUM> and application processing circuitry <NUM> can be combined into one chip or set of chips, and RF transceiver circuitry <NUM> can be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry <NUM> and baseband processing circuitry <NUM> can be on the same chip or set of chips, and application processing circuitry <NUM> can be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry <NUM>, baseband processing circuitry <NUM>, and application processing circuitry <NUM> can be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry <NUM> can be a part of interface <NUM>. RF transceiver circuitry <NUM> can condition RF signals for processing circuitry <NUM>.

In certain embodiments, some or all of the functionality described herein as being performed by a WD can be provided by processing circuitry <NUM> executing instructions stored on device readable medium <NUM>, which in certain embodiments can be a computer-readable storage medium. In alternative embodiments, some or all of the functionality can be provided by processing circuitry <NUM> without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.

Processing circuitry <NUM> can be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry <NUM>, can include processing information obtained by processing circuitry <NUM> by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD <NUM>, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium <NUM> can be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry <NUM>. Device readable medium <NUM> can include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that can be used by processing circuitry <NUM>. In some embodiments, processing circuitry <NUM> and device readable medium <NUM> can be considered to be integrated.

User interface equipment <NUM> can include components that allow and/or facilitate a human user to interact with WD <NUM>. Such interaction can be of many forms, such as visual, audial, tactile, etc. User interface equipment <NUM> can be operable to produce output to the user and to allow and/or facilitate the user to provide input to WD <NUM>. The type of interaction can vary depending on the type of user interface equipment <NUM> installed in WD <NUM>. For example, if WD <NUM> is a smart phone, the interaction can be via a touch screen; if WD <NUM> is a smart meter, the interaction can be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment <NUM> can include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment <NUM> can be configured to allow and/or facilitate input of information into WD <NUM> and is connected to processing circuitry <NUM> to allow and/or facilitate processing circuitry <NUM> to process the input information. User interface equipment <NUM> can include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment <NUM> is also configured to allow and/or facilitate output of information from WD <NUM>, and to allow and/or facilitate processing circuitry <NUM> to output information from WD <NUM>. User interface equipment <NUM> can include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment <NUM>, WD <NUM> can communicate with end users and/or the wireless network and allow and/or facilitate them to benefit from the functionality described herein.

This can comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment <NUM> can vary depending on the embodiment and/or scenario.

Power source <NUM> can, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, can also be used. WD <NUM> can further comprise power circuitry <NUM> for delivering power from power source <NUM> to the various parts of WD <NUM> which need power from power source <NUM> to carry out any functionality described or indicated herein. Power circuitry <NUM> can in certain embodiments comprise power management circuitry. Power circuitry <NUM> can additionally or alternatively be operable to receive power from an external power source; in which case WD <NUM> can be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry <NUM> can also in certain embodiments be operable to deliver power from an external power source to power source <NUM>. This can be, for example, for the charging of power source <NUM>. Power circuitry <NUM> can perform any converting or other modification to the power from power source <NUM> to make it suitable for supply to the respective components of WD <NUM>.

Instead, a UE can represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE can represent a device that is not intended for sale to, or operation by, an end user but which can be associated with or operated for the benefit of a user (e.g., a smart power meter). UE <NUM> can be any UE identified by the <NUM>rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. As mentioned previously, the term WD and UE can be used interchangeable.

In other embodiments, storage medium <NUM> can include other similar types of information. Certain UEs can utilize all of the components shown in <FIG>, or only a subset of the components. The level of integration between the components can vary from one UE to another UE. Further, certain UEs can contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc..

In <FIG>, processing circuitry <NUM> can be configured to process computer instructions and data. Processing circuitry <NUM> can be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry <NUM> can include two central processing units (CPUs). Data can be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface <NUM> can be configured to provide a communication interface to an input device, output device, or input and output device. UE <NUM> can be configured to use an output device via input/output interface <NUM>. An output device can use the same type of interface port as an input device. For example, a USB port can be used to provide input to and output from UE <NUM>. The output device can be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE <NUM> can be configured to use an input device via input/output interface <NUM> to allow and/or facilitate a user to capture information into UE <NUM>. The input device can include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display can include a capacitive or resistive touch sensor to sense input from a user. A sensor can be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In <FIG>, RF interface <NUM> can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface <NUM> can be configured to provide a communication interface to network 843a. Network 843a can encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 843a can comprise a Wi-Fi network. Network connection interface <NUM> can be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface <NUM> can implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions can share circuit components, software or firmware, or alternatively can be implemented separately.

RAM <NUM> can be configured to interface via bus <NUM> to processing circuitry <NUM> to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM <NUM> can be configured to provide computer instructions or data to processing circuitry <NUM>. For example, ROM <NUM> can be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium <NUM> can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.

In one example, storage medium <NUM> can be configured to include operating system <NUM>; application program <NUM> such as a web browser application, a widget or gadget engine or another application; and data file <NUM>. Storage medium <NUM> can store, for use by UE <NUM>, any of a variety of various operating systems or combinations of operating systems. For example, application program <NUM> can include executable program instructions (also referred to as a computer program product) that, when executed by processor <NUM>, can configure UE <NUM> to perform operations corresponding to various exemplary methods (e.g., procedures) described herein.

Storage medium <NUM> can be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium <NUM> can allow and/or facilitate UE <NUM> to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system can be tangibly embodied in storage medium <NUM>, which can comprise a device readable medium.

In <FIG>, processing circuitry <NUM> can be configured to communicate with network 843b using communication subsystem <NUM>. Network 843a and network 843b can be the same network or networks or different network or networks. Communication subsystem <NUM> can be configured to include one or more transceivers used to communicate with network 843b. For example, communication subsystem <NUM> can be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE <NUM>, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver can include transmitter <NUM> and/or receiver <NUM> to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter <NUM> and receiver <NUM> of each transceiver can share circuit components, software or firmware, or alternatively can be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem <NUM> can include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem <NUM> can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 843b can encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 843b can be a cellular network, a Wi-Fi network, and/or a near-field network. Power source <NUM> can be configured to provide alternating current (AC) or direct current (DC) power to components of UE <NUM>.

The features, benefits and/or functions described herein can be implemented in one of the components of UE <NUM> or partitioned across multiple components of UE <NUM>. Further, the features, benefits, and/or functions described herein can be implemented in any combination of hardware, software or firmware. In one example, communication subsystem <NUM> can be configured to include any of the components described herein. Further, processing circuitry <NUM> can be configured to communicate with any of such components over bus <NUM>. In another example, any of such components can be represented by program instructions stored in memory that when executed by processing circuitry <NUM> perform the corresponding functions described herein. In another example, the functionality of any of such components can be partitioned between processing circuitry <NUM> and communication subsystem <NUM>. In another example, the non-computationally intensive functions of any of such components can be implemented in software or firmware and the computationally intensive functions can be implemented in hardware.

<FIG> is a schematic block diagram illustrating a virtualization environment <NUM> in which functions implemented by some embodiments can be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which can include virtualizing hardware platforms, storage devices and networking resources.

In some embodiments, some or all of the functions described herein can be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments <NUM> hosted by one or more of hardware nodes <NUM>. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node can be entirely virtualized.

The functions can be implemented by one or more applications <NUM> (which can alternatively be called software instances, virtual appliances, network functions, application functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications <NUM> (including, e.g., network functions and/or application functions) are run in virtualization environment <NUM> which provides hardware <NUM> comprising processing circuitry <NUM> and memory <NUM>.

Virtualization environment <NUM> can include general-purpose or special-purpose network hardware devices (or nodes) <NUM> comprising a set of one or more processors or processing circuitry <NUM>, which can be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device can comprise memory <NUM>-<NUM> which can be non-persistent memory for temporarily storing instructions <NUM> or software executed by processing circuitry <NUM>. For example, instructions <NUM> can include program instructions (also referred to as a computer program product) that, when executed by processing circuitry <NUM>, can configure hardware node <NUM> to perform operations corresponding to various exemplary methods (e.g., procedures) described herein. Such operations can also be attributed to virtual node(s) <NUM> that is/are hosted by hardware node <NUM>.

Each hardware device can comprise one or more network interface controllers (NICs) <NUM>, also known as network interface cards, which include physical network interface <NUM>. Each hardware device can also include non-transitory, persistent, machine-readable storage media <NUM>-<NUM> having stored therein software <NUM> and/or instructions executable by processing circuitry <NUM>. Software <NUM> can include any type of software including software for instantiating one or more virtualization layers <NUM> (also referred to as hypervisors), software to execute virtual machines <NUM> as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines <NUM>, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and can be run by a corresponding virtualization layer <NUM> or hypervisor. Different embodiments of the instance of virtual appliance <NUM> can be implemented on one or more of virtual machines <NUM>, and the implementations can be made in different ways.

During operation, processing circuitry <NUM> executes software <NUM> to instantiate the hypervisor or virtualization layer <NUM>, which can sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer <NUM> can present a virtual operating platform that appears like networking hardware to virtual machine <NUM>.

As shown in <FIG>, hardware <NUM> can be a standalone network node with generic or specific components. Hardware <NUM> can comprise antenna <NUM> and can implement some functions via virtualization. Alternatively, hardware <NUM> can be part of a larger cluster of hardware (e.g., such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) <NUM>, which, among others, oversees lifecycle management of applications <NUM>.

NFV can be used to consolidate many network equipment types onto industry standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine <NUM> can be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.

In some embodiments, one or more radio units <NUM> that each include one or more transmitters <NUM> and one or more receivers <NUM> can be coupled to one or more antennas <NUM>. Radio units <NUM> can communicate directly with hardware nodes <NUM> via one or more appropriate network interfaces and can be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. Nodes arranged in this manner can also communicate with one or more UEs, such as described elsewhere herein.

In some embodiments, some signaling can be performed via control system <NUM>, which can alternatively be used for communication between the hardware nodes <NUM> and radio units <NUM>.

Various network functions (NFs, e.g., SMF, PCF, UDR, AMF, etc.) described herein can be implemented in virtualization environment <NUM>, e.g., as NFs <NUM> running on hardware <NUM>.

Furthermore, functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes.

In addition, certain terms used in the present disclosure, including the specification, drawings and exemplary embodiments thereof, can be used synonymously in certain instances, including, but not limited to, e.g., data and information. It should be understood that, while these words and/or other words that can be synonymous to one another, can be used synonymously herein, that there can be instances when such words can be intended to not be used synonymously.

As used herein unless expressly stated to the contrary, the phrases "at least one of' and "one or more of," followed by a conjunctive list of enumerated items (e.g., "A and B", "A, B, and C"), are intended to mean "at least one item, with each item selected from the list consisting of' the enumerated items. For example, "at least one of A and B" is intended to mean any of the following: A; B; A and B. Likewise, "one or more of A, B, and C" is intended to mean any of the following: A; B; C; A and B; B and C; A and C; A, B, and C.

As used herein unless expressly stated to the contrary, the phrase "a plurality of' followed by a conjunctive list of enumerated items (e.g., "A and B", "A, B, and C") is intended to mean "multiple items, with each item selected from the list consisting of' the enumerated items. For example, "a plurality of A and B" is intended to mean any of the following: more than one A; more than one B; or at least one A and at least one B.

The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the scope of the disclosure as defined by the appended set of claims.

Claim 1:
A method performed by a policy control function, PCF, of a communication network, the method comprising:
during establishment of a packet data unit, PDU, session for a user equipment, UE, determining (<NUM>) one or more UE application descriptors that correspond to a network application identifier, AppId, of a service data flow, SDF, template for the PDU session, wherein each of the one or more UE application descriptors includes:
a first identifier, OSId, of a UE-supported operating system, OS, and
a second identifier, OSAppId, of an application for the UE-supported OS identified by the first identifier; and
sending (<NUM>), to a session management function, SMF, of the communication network, policy rules for the PDU session, wherein the policy rules include the one or more UE application descriptors.