EP-4738794-A2 - METHODS, APPARATUSES AND SYSTEMS DIRECTED TO PROVISIONING DOMAIN SUPPORT IN 5G NETWORKS
Abstract
Methods, apparatuses, systems, etc., directed to support provisioning domains (PvDs) in 5G networks are disclosed herein. In an embodiment, a network entity running a policy control function (PCF), may send to a wireless receive and transmit unit (WTRU) at least one WTRU route selection policy (URSP) rule associated with, for example, PvD descriptors. For example, URSP rules may be configured e.g., as part of the subscription profile and PvD descriptors may be configured e.g., as part of a network-wide configuration. An application function (AF) may use a network exposure function (NEF) application programming interface (API) to access and, for example, update, e.g. through any of NEF and PCF, any of URSP rules and PvD descriptors. According to embodiments, a WTRU may participate in a data network access identifier (DNAI) selection by including a PvD ID in, for example, PDU session establishment messages.
Inventors
- DE FOY, XAVIER
- OLVERA-HERNANDEZ, ULISES
- AHMAD, SAAD
Assignees
- InterDigital Patent Holdings, Inc.
Dates
- Publication Date
- 20260506
- Application Date
- 20210505
Claims (15)
- A method implemented in a network element, the method comprising: receiving, from an application function, AF, a request to associate a provisioning domain, PvD, identifier, PvD ID, with at least one association parameter; identifying a wireless transmit/receive unit, WTRU, route selection policy, URSP, rule corresponding to the association parameter, modifying the URSP rule by inserting the PvD ID into at least one of a traffic descriptor section and a route selection section of the URSP rule; and sending a message to a data repository to store the URSP rule.
- The method of claim 1, wherein identifying the URSP rule comprises creating the URSP rule based on the at least one association parameter.
- The method of any of claims 1 to 2, wherein the at least one association parameter comprises at least one of: (i) a WTRU identifier, (ii) a WTRU group identifier, (iii) a data network name, DNN, (iv) a data network access identifier, DNAI, (v) a network slice identifier, (vi) a protocol data unit, PDU, session type, (vii) an application identifier, or (viii) a domain name.
- The method of any of claims 1 to 3, wherein receiving the request from the AF comprises receiving an AF transaction identifier for at least one of referencing, updating, or deleting the association of the PvD ID with the at least one association parameter.
- The method of any of claims 1 to 4, wherein sending the message to the data repository comprises transmitting a policy update message identifying the URSP rule and the PvD ID.
- The method of any of claims 1 to 5, further comprising sending the URSP rule to a policy control function, PCF, for delivery to the WTRU.
- The method of any of claims 1 to 6, further comprising receiving, from the AF, a request to modify one or more PvD attributes associated with the PvD ID.
- A network element comprising circuitry including a transmitter, a receiver, a processor and memory configured to: receive, from an application function, AF, a request to associate a provisioning domain, PvD, identifier, PvD ID, with at least one association parameter; identify a wireless transmit/receive unit, WTRU, route selection policy, URSP, rule corresponding to the association parameter, modify the URSP rule by inserting the PvD ID into at least one of a traffic descriptor section and a route selection section of the URSP rule; and send a message to a data repository to store the URSP rule.
- The network element of claim 8, wherein being configured to identify the URSP rule comprises being configured to create the URSP rule based on the at least one association parameter.
- The network element of any of claims 8 to 9, wherein the at least one association parameter comprises at least one of: (i) a WTRU identifier, (ii) a WTRU group identifier, (iii) a data network name, DNN, (iv) a data network access identifier, DNAI, (v) a network slice identifier, (vi) a protocol data unit, PDU, session type, (vii) an application identifier, or (viii) a domain name.
- The network element of any of claims 8 to 10, wherein being configured to receive the request from the AF comprises being configured to receive an AF transaction identifier for at least one of referencing, updating, or deleting the association of the PvD ID with the at least one association parameter.
- The network element of any of claims 8 to 11, wherein being configured to send the message to the data repository comprises being configured to transmit a policy update message identifying the URSP rule and the PvD ID.
- The network element of any of claims 8 to 12, configured to send the URSP rule to a policy control function, PCF, for delivery to the WTRU.
- The network element of any of claims 8 to 13, configured to receive, from the AF, a request to modify one or more PvD attributes associated with the PvD ID.
- The network element of any of claims 8 to 14, comprising a network exposure function, NEF.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 63/024,080 filed 13-05-2020, which is incorporated herein by reference. BACKGROUND The present disclosure relates to network communications, including, but not exclusively, to methods, apparatuses, systems, etc. directed to domain provisioning support in 5G networks. SUMMARY Methods, apparatuses, systems, etc., directed to support provisioning domains (PvDs) in 5G networks are disclosed herein. In an embodiment, a network entity running a policy control function (PCF), may send to a wireless receive and transmit unit (WTRU) at least one WTRU route selection policy (URSP) rule associated with, for example, PvD descriptors. For example, URSP rules may be configured e.g., as part of the subscription profile and PvD descriptors may be configured e.g., as part of a network-wide configuration. An application function (AF) may use a network exposure function (NEF) application programming interface (API) to access and, for example, update, e.g. through any of NEF and PCF, any of URSP rules and PvD descriptors. According to embodiments, a WTRU may participate in a data network access identifier (DNAI) selection by including a PvD ID in, for example, PDU session establishment messages. Although various embodiments are described and/or claimed herein in which an apparatus, system, device, etc. and/or any element thereof is configured to carry out an operation, process, algorithm, function, etc. and/or any portion thereof, it is to be understood that any embodiments described and/or claimed herein assume that any apparatus, system, device, etc. and/or any element thereof carries out any operation, process, algorithm, function, etc. and/or any portion thereof (and vice versa). BRIEF DESCRIPTION OF THE DRAWINGS A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings. Figures in such drawings, like the detailed description, are examples. As such, the Figures and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals in the figures indicate like elements. FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented;FIG. 1B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;FIG. 1D is a system diagram illustrating a further example RAN and a further example of a CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment;FIG. 2A and FIG. 2B are two of JavaScript object notation (JSON) objects representing PvD attributes;FIG. 3 is a diagram illustrating an example of a PvD support in a 5G architecture;FIG. 4 is a diagram illustrating an example of a deployment of PvD information in a 5G network;FIG. 5 is a diagram illustrating an example of a method for supporting provisioning domains in a 5G network;FIG. 6 is a diagram illustrating an example of a method for supporting a PvD in a WTRU. DETAILED DESCRIPTION A detailed description of illustrative embodiments will now be described with reference to the various Figures. Although this description provides a detailed example of possible implementations, it should be noted that the details are intended to be exemplary and in no way limit the scope of the application. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and/or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described, disclosed or otherwise provided explicitly, implicitly and/or inherently (collectively "provided") herein. Example Communications Networks FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sha