Processing messages related to application function sessions that are bound to protocol data unit sessions

Abstract

A method performed by a Policy Control Function (PCF) is provided. The method includes receiving, from either a Network Publishing Function (NEF) or a Time-Sensitive Communications and Time Synchronization Function (TSCTSF), a first request associated with an Application Function (AF) session bound to a Protocol Data Unit (PDU) session. The method further includes, after receiving the first request associated with the AF session bound to the PDU session, determining whether the PDU session is likely for Time-Sensitive Communications (TSC). The method further includes determining whether to accept or reject the first request based on the determination of whether the PDU session is likely for TSC, and sending a first response toward the NEF or the TSCTSF indicating whether the first request is accepted.

Description

[Technical Field]

[0001] The present disclosure relates to processing messages associated with an application function (AF) session that is bound to a protocol data unit (PDU) session. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP®) Technical Specification 23.502, version 17.7.9 (TS 23.502) discloses a process for setting up an Application Function (AF) session with a required Quality of Service (QoS).

[0003] The process begins with the AF sending a create request to the network exposure function (NEF) to reserve service resources for the AF session. After receiving the create request, the NEF decides whether to direct the signaling to the Policy Control Function (PCF) directly or via the time sensitive communication and time synchronization function (TSCTSF). The decision can be based on the individual QoS parameter set or one or more requested alternative QoS parameter sets received from the AF.

[0004] After an AF session is established with the required QoS, the AF may want to update the AF session with updated QoS. In such a case, the AF may send an update request to update the service resources for the AF session. After receiving the update request, the NEF again decides whether to direct signaling to the PCF directly or via the TSCTSF. The decision may be made based on the individual QoS parameter set or one or more requested alternative QoS parameter sets received from the AF.

[0005] To request a specific QoS, the create and / or update request may include any of the following: (1) QoS reference + (optional) traffic characteristics (i.e., flow direction, burst arrival time at the user equipment (UE) (uplink) or user plane function (UPF) (downlink), periodicity, time domain, survival time), or (2) Individual QoS parameters (i.e., requested 5G system (5GS) delay (optional), requested priority (optional), requested guaranteed bit rate, requested maximum bit rate, maximum burst size) + (optional) traffic characteristics (i.e., flow direction, burst arrival time at the UE (uplink) or UPF (downlink)), periodicity, time domain, time to live).

[0006] 3GPP TS 23.503, version 17.6.0 (TS 23.503) suggests that create requests and update requests associated with the same AF session must have the same type of QoS information. For example, if a create request includes a QoS reference, the AF cannot include individual QoS parameters in place of the QoS reference. In other words, the AF cannot replace a previously provided QoS in the create request with individual QoS parameters in the update request. In another example, if a create request includes one or more individual QoS parameters, the AF cannot include a QoS reference in place of the individual QoS parameter(s).

[0007] As briefly described above, signaling from the NEF to the PCF may be performed directly between the NEF and the PCF, or indirectly via the TSCTSF.

[0008] Such indirect signaling (i.e., signaling via the TSCTSF) may be required when certain QoS parameters are present in the AF request (e.g., the aforementioned Create Request, the aforementioned Update Request, etc.). Examples of such QoS parameters include any time sensitive communication assistance container (TSCAC)-related parameters that describe traffic characteristics (i.e., flow direction, burst arrival time at the UE (uplink) or UPF (downlink)), periodicity, time domain, and time to live), and may be provided regardless of whether the Create and Update request includes QoS reference parameters or individual QoS parameters. Another example is when an individual QoS parameter in a Create or Update request includes a requested 5GS delay (e.g., which may include a UE device-side time sensitive networking (TSN) translator (UE-DS-TT) residence time). In other cases, direct signaling (without going via the TSCTSF) may be performed between the NEF and PCF. Summary of the Invention

[0009] Currently, several challenges exist. For example, as mentioned above, if the type of QoS information included in the update request is different from the type of QoS information included in the create request, the NEF shall reject the update request because the update request requires a different signaling path (e.g., an indirect signaling path between the NEF and the PCF via the TSCTSF) than the signaling path required for the create request (e.g., a direct signaling path between the NEF and the PCF).

[0010] For example, if the update request includes the requested 5GS delay and TSCAC related information (which requires signaling via TSCTSF), but the create request does not, the NEF may determine that the update request requires a different signaling path than the signaling path for the create request, and may therefore reject the update request even though it is legitimate.

[0011] If the update request is rejected, the AF will need to send another create request (directly or via TSCTSF), which will result in excessive signaling and service interruption. Therefore, it is necessary to determine the signaling path between the NEF and the PCF during the creation of an AF session.

[0012] To solve this problem, one aspect of an embodiment of the present disclosure provides a method executed by a policy control function (PCF). The method includes receiving, from either a network publishing function (NEF) or a time-sensitive communications and time synchronization function (TSCTSF), a first request associated with an application function (AF) session bound to a protocol data unit (PDU) session. The method further includes, after receiving the first request associated with the AF session bound to the PDU session, determining whether the PDU session is likely for time-sensitive communications (TSC). The method further includes determining whether to accept or reject the first request based on the determination of whether the PDU session is likely for TSC. The method further includes transmitting a first response indicating whether the first request is accepted or rejected to the NEF or TSCTSF.

[0013] In another aspect, a method performed by a Network Publishing Function (NEF) is provided. The method includes sending a first request associated with an Application Function (AF) session bound to a Protocol Data Unit (PDU) session toward a Policy Control Function (PCF). The method further includes, after sending the first request, receiving a first response from the PCF indicating that the first request is denied, the first response indicating that a Time Sensitive Communications and Time Synchronization Function (TSCTSF) is required for the AF session bound to the PDU session.

[0014] In another aspect, a method is provided that is performed by a Time Sensitive Communications and Time Synchronization Function (TSCTSF). The method includes sending a first request related to an Application Function (AF) session bound to a Protocol Data Unit (PDU) session toward a Policy Control Function (PCF). The method further includes receiving (s504) a first response from the PCF after sending the first request, the first response indicating that the first request is denied, the first response indicating that the TSCTSF is not required for the AF session bound to the PDU session.

[0015] In another aspect, a computer program is provided that includes instructions that, when executed by a processing circuit (602), cause the processing circuit to perform the method of any one of the above-described embodiments.

[0016] In another aspect, there is provided a carrier comprising the computer program of the above embodiments, the carrier being one of an electrical signal, an optical signal, a radio signal, and a computer readable storage medium.

[0017] In another aspect, a policy control function (PCF) is provided. The PCF is configured to receive, from either a network publishing function (NEF) or a time-sensitive communications and time synchronization function (TSCTSF), a first request associated with an application function (AF) session bound to a protocol data unit (PDU) session, and determine, after receiving the first request associated with the AF session bound to the PDU session, whether the PDU session is likely for time-sensitive communications (TSC). The PCF is configured to determine whether to accept or reject the first request based on the determination of whether the PDU session is likely for TSC, and to send a first response indicating whether the first request is accepted or not toward the NEF or the TSCTSF.

[0018] In another aspect, a Network Publish Function (NEF) is provided, the NEF being configured to: send a first request related to an Application Function (AF) session bound to a Protocol Data Unit (PDU) session toward a Policy Control Function (PCF); and, after sending the first request, receive a first response from the PCF indicating that the first request is rejected, the first response indicating that a Time Sensitive Communications and Time Synchronization Function (TSCTSF) is required for the AF session bound to the PDU session.

[0019] In another aspect, a Time Sensitive Communications and Time Synchronization Function (TSCTSF) is provided, configured to: send a first request related to an Application Function (AF) session bound to a Protocol Data Unit (PDU) session toward a Policy Control Function, PCF; and, after sending the first request, receive a first response from the PCF indicating that the first request is rejected, the first response indicating that the TSCTSF is not required for the AF session bound to the PDU session.

[0020] In another aspect, there is provided an apparatus comprising a processing circuit and a memory, the memory including instructions executable by the processing circuit, such that the apparatus is operable to perform the method of any one of the preceding embodiments.

[0021] Some embodiments of the present disclosure allow for determining the signaling path for the request during the creation of the AF session, thereby minimizing the possibility of a legitimate requested update from the AF being rejected. [Brief explanation of the drawings]

[0022] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate various embodiments.

[0023] [Figure 1] FIG. 1 illustrates a portion of a system according to some embodiments.

[0024] [Figure 2A] FIG. 2A illustrates a process according to some embodiments.

[0025] [Figure 2B] FIG. 2B illustrates a process according to some embodiments.

[0026] [Figure 3] FIG. 3 illustrates a process according to some embodiments.

[0027] [Figure 4] FIG. 4 illustrates a process according to some embodiments.

[0028] [Figure 5] FIG. 5 illustrates a process according to some embodiments.

[0029] [Figure 6] FIG. 6 illustrates an apparatus according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0030] FIG. 1 illustrates a portion of a system 100 according to some embodiments. In the system 100, a user equipment (UE) 116 (e.g., a mobile phone, a computer, a watch, a tablet, a vehicle, an Internet of Things (IoT) device, etc.) is connected to a base station 114 via a wireless network provided by the base station 114. The base station 114 is part of a 3GPP network system 112 that includes an AF 102, a NEF 104, a TSCTSF 106, and a PCF 108. It should be noted that the number of each of the entities (102, 104, 106, 108, 114, 116, etc.) illustrated in FIG. 1 is provided solely for ease of explanation and does not limit the embodiments of the present disclosure. It should also be noted that FIG. 1 illustrates only a portion of the 3GPP network system 112 (meaning that the 3GPP network system 112 may include additional entities). A network function / node may be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform, for example on a cloud infrastructure.

[0031] The AF 102 is a control plane function in a 5G core network. The AF 102 may be configured to create an AF session for providing application services (e.g., video streaming services) to a UE 116. Figures 2A and 2B illustrate a process 200 for creating an AF session, according to some embodiments.

[0032] The process 200 may begin with the AF 102 sending an AF request 202 to the NEF 104. In some embodiments, the AF request 202 may correspond to a request to provide a particular QoS (e.g., minimum video resolution) for an AF session (e.g., video streaming service) for the UE 116. One example of such a request is an Nnef_AFsessionWithQoS Create request.

[0033] If the AF request 202 is a request to provide a specific QoS, the NEF 104 may perform step s202 upon receiving the AF request 202. Step s202 includes determining whether to grant the AF request. If the NEF 104 determines not to grant the AF request 202, the NEF 104 may send an AF response 216 to the AF 102 indicating that the AF request 202 has been rejected. An example of the AF response 216 is an Nnef_AFsessionWithQoSCreate response.

[0034] On the other hand, if the NEF 104 decides to grant the AF request 202, then in step s204, the NEF 104 may further decide whether to invoke the TSCTSF 106 in the signaling PCF 108 or whether to signal the PCF 108 directly (i.e., whether to send / receive message(s) to / from the PCF 108 without passing through the TSCTSF 106, or whether to send / receive message(s) to / from the PCF 108 via the TSCTSF 106). This decision may be based on the presence of a specific QoS reference or specific QoS-specific parameter(s) in the AF request 202. Additionally or alternatively, the decision may be based on an AF identifier identifying a specific AF session or AF-provisioned parameters describing traffic characteristics.

[0035] 2A , if the NEF 104 decides to signal the PCF 108 directly without using the TSCTSF 106, the NEF 104 may send an NEF request 204 to the PCF 108. In some embodiments, the NEF request 204 is a request to create one or more policies as requested by the AF 102 for the PDU session to which the AF session is bound. In one example, the NEF request 204 is an Npcf_PolicyAuthorization_Create request.

[0036] Upon receiving the NEF request 204, in step s206, the PCF 108 may determine whether the PDU session bound to the AF session for which the NEF request 204 is made is for time-sensitive communication (TSC) (i.e., whether a TSCTSF may be required in the signaling path between the NEF 104 and the PCF 108). An example of determining that a PDU session is for TSC is determining that the PDU session may be affected by the precision time protocol (PTP) time synchronization service. Determining whether the PDU session for which the NEF request 204 is made is for TSC may be based on any one or more of 5GS bridge information, data network name (DNN), network slice selection assistance information (S-NSSAI), application identifier (ID) identifying an application, group ID identifying a UE group, and / or local configuration. For example, the mere presence of 5GS bridge information may indicate that the PDU session may be used for TSC. Alternatively or additionally, a DNN identifying a particular data network, an S-NSSAI identifying a particular network slice, and / or an application ID identifying a particular application may indicate that the PDU session is likely for a TSC. More detailed information about these parameters is provided in Section 5.2.27.3 of 3GPP TS 23.502, which is incorporated herein by reference.

[0037] Note that the PCF 108 knows whether the NEF request 204 is originated by the NEF 104 or the TSCTSF 106. For example, the NEF 104 and the TSCTSF 106 may configure a user-agent HTTP header in the requests they send to the PCF 108. In another example, each request may include various information elements or parameters that identify the sender of the request. Thus, if the PCF 108 determines that a PDU session bound to an AF session is likely for a TSC, the PCF 108 may reject the NEF request 204 because the request was originated by the NEF 104, indicating that there is no TSCTSF for this signaling between the NEF 104 and the PCF 108.

[0038] Therefore, the PCF 108 may send an NEF response 210 to the NEF 104 indicating that the NEF request 204 has been rejected. An example of the NEF response 210 is an Npcf_PolicyAuthorization_Create response. In some embodiments, the NEF response 210 may indicate that a TSCTSF is required for the AF session bound to the PDU session. Such information may be very useful to the NEF 104, as the NEF 104 now knows that a TSCTSF is required for the AF session bound to the PDU session, and therefore, when the NEF 104 retries sending the NEF request, it may send the request via the TSCSTF 106 (instead of sending the request directly to the PCF 108).

[0039] On the other hand, if the PCF 108 determines that the PDU session bound to the AF session is not possible for TSC, the PCF 108 may accept the NEF request 204 because the request was initiated by the NEF 104, which indicates that there is no TSCTSF for this signaling between the NEF 104 and the PCF 108. In this case, the NEF response 210 may indicate that the NEF request 204 is accepted. An example of the NEF response 210 is an Npcf_PolicyAuthorization_Create response.

[0040] Upon receiving the NEF response 210, the NEF 104 may send an AF response 216 to the AF 102 indicating that the AF request 202 has been accepted. An example of an AF response 216 is an Nnef_AFsessionWithQoS Create response.

[0041] Referring back to step s204, as shown in FIG. 2B, if the NEF 104 decides to invoke the TSCTSF in the signaling PCF 108, the NEF 104 may send an NEF request 206 to the TSCTSF 106 instead of sending an NEF request 204 to the PCF 108. In some embodiments, the NEF request 206 is a request to provide a specific QoS for the AF session. In one example, the NEF request 206 is an Ntsctsf_QoSandSCAssistance_Create request.

[0042] If the NEF request 206 is a request to provide a specific QoS for an AF session, upon receiving the NEF request 206, the TSCTSF 106 may determine in step s208 whether it has an AF session with a PCF for the given UE address. If so, the TSCTSF 106 may send a TSCTSF request 208 toward the PCF 108. In some embodiments, the TSCTSF request 208 is a request to provide a specific QoS for the AF session. One example of a TSCTSF request 208 is an Npcf_PolicyAuthorization_Update request.

[0043] On the other hand, if the TSCTSF 106 determines that it does not currently have an AF session with a PCF for the given UE address, the TSCTSF 106 may discover the PCF 108 and send a TSCTSF request 208, where examples of a TSCTSF request 208 are an Npcf_PolicyAuthorization_Create request or an Npcf_PolicyAuthorization_Subscribe request.

[0044] Upon receiving the TSCTSF request 208, in step s210, the PCF 108 may determine whether the PDU session bound to the AF session for which the TSCTSF (Create or Subscribe) request 208 is made is for time-sensitive communication (TSC) (i.e., whether TSCTSF may be required in the signaling path between the NEF 104 and the PCF 108). An example of determining that a PDU session is for TSC is determining that the PDU session may be affected by the Precision Time Protocol (PTP) time synchronization service. Such a determination may be made based on any one or more of 5GS bridge information, a data network name (DNN), a network slice selection assistance information (S-NSSAI), an application identifier (ID) that identifies an application, a group ID that identifies a UE group, and / or a local configuration.

[0045] Note that in some embodiments, if the PDU session is likely for a TSC (i.e., if a TSCTSF is required in the signaling path between the NEF 104 and the PCF 108), the PCF 108 may send a message including 5GS bridge information to the TSCTSF 106. In such embodiments, the PCF 108 may check whether the PCF 108 has sent the 5GS bridge information to the TSCTSF 106 in step s210.

[0046] The PCF 108 knows whether the TSCTSF request 208 was originated by the NEF 104 or the TSCTSF 106 (e.g., by analyzing the user-agent HTTP header of the NEF request 204). Thus, if the PCF 108 determines that the PDU session cannot be for a TSC, the PCF 108 may reject the TSCTSF request 208 because the request was originated by the TSCTSF 106, which indicates that a TSCTSF exists for this signaling between the NEF 104 and the PCF 108. In this case, the PCF 108 may send a TSCTSF response 212 to the TSCTSF 106 indicating that the TSCTSF request 208 was rejected. In some embodiments, the TSCTSF response 212 may indicate that a TSCTSF is not required for the PDU session. Examples of TSCTSF responses 212 are the Npcf_PolicyAuthorization_Create response and the Npcf_PolicyAuthorization_Subscribe response.

[0047] On the other hand, if the PCF 108 determines that the PDU session bound to the AF session is likely for a TSC, the PCF 108 may accept the TSCTSF request 208 because the request was initiated by the TSCTSF 106, which indicates that a TSCTSF exists for this signaling between the NEF 104 and the PCF 108. In this case, the PCF 108 may send a TSCTSF response 212 to the TSCTSF 106 indicating that the TSCTSF request 208 has been accepted.

[0048] Upon receiving the TSCTSF response 212, the TSCTSF 106 may send a NEF response 214 to the NEF 104. An example of the NEF response 214 is a Ntsctsf_QoSandTSCAssistance_Create response. According to some embodiments, if the NEF response 214 is a rejection message rejecting the NEF request 206, the NEF response 214 may indicate the reason why the NEF request 206 is rejected. For example, the NEF response 214 may indicate that a TSCTSF is not required in the signaling path between the NEF 104 and the PCF 108 for the PDU session. This information may be very useful to the NEF 104 because if the NEF 104 retries sending the request, the NEF 104 can attempt to send the request directly to the PCF 108 (instead of sending it via the TSCTSF 106).

[0049] Upon receiving the NEF response 214, the NEF 104 may transmit an AF response 214 to the AF 102 indicating whether the AF request 202 is accepted or not.

[0050] 3 illustrates a process 300 performed by the PCF 108 according to some embodiments. The process 300 may begin at step s302. Step s302 includes receiving a first request associated with an AF session bound to a PDU session from either the NEF 104 or the TSCTSF. Step s304 includes determining, after receiving the first request associated with the AF session bound to the PDU session, whether the PDU session is likely for time-sensitive communication (TSC). Step s306 includes determining whether to accept or reject the first request based on the determination of whether the PDU session is likely for TSC. Step s308 includes sending a first response to the NEF or the TSCTSF indicating whether the first request is accepted.

[0051] In some embodiments, the process 300 includes determining whether the first request was originated by the NEF or the TSCTSF, and whether to accept or reject the first request is further determined based on the determination of whether the first request was originated by the NEF or the TSCTSF.

[0052] In some embodiments, the first request is a request to create one or more policies for a PDU session bound to the AF session or a request to subscribe to reporting of one or more events in the PCF.

[0053] In some embodiments, the first request is one of an Npcf_PolicyAuthorization_Create request or an Npcf_PolicyAuthorization_Subscribe request.

[0054] In some embodiments, whether a PDU session is likely for a TSC is determined based on any one or more of 5GS bridge information, a specific data network name (DNN), a specific network slice selection assistance information (S-NSSAI), a specific application identifier (ID) identifying a specific application, a specific group ID identifying a user equipment (UE) group, or a specific local configuration associated with a specific set of one or more rules and / or policies.

[0055] In some embodiments, the process 300 includes identifying that the first request was originated by an NEF, determining whether the PDU session is likely for a TSC includes determining that a TSCTSF is a network function (NF) type required for the request, and the first response is a reject message rejecting the first request.

[0056] In some embodiments, the reject message indicates that a TSCTSF is required for the AF session bound to the PDU session.

[0057] In some embodiments, the process 300 includes identifying that the first request was sent by a TSCTSF and determining that the PDU session bound to the AF session is not likely for the TSC, and the first response is a reject message rejecting the first request, the reject message indicating that the TSCTSF is not required for the AF session bound to the PDU session.

[0058] 4 illustrates a process 400 performed by the NEF 104 according to some embodiments. The process 400 may begin at step s402. Step s402 may include sending a first request related to an AF session bound to a PDU session to a PCF. Step s404 may include receiving, after sending the first request, a first response from the PCF indicating that the first request is rejected, where the first response indicates that a TSCTSF is required for the AF session bound to the PDU session.

[0059] In some embodiments, the first request is a request to create one or more policies for a PDU session bound to the AF session or a request to subscribe to reporting of one or more events in the PCF.

[0060] In some embodiments, the first request is one of an Npcf_PolicyAuthorization_Create request or an Npcf_PolicyAuthorization_Subscribe request.

[0061] In some embodiments, whether a TSCTSF is required for an AF session bound to a PDU session is determined by the PCF based on any one or more of 5GS bridge information, a specific data network name (DNN), a specific network slice selection assistance information (S-NSSAI), a specific application identifier (ID) identifying a specific application, a specific group ID identifying a user equipment (UE) group, or a specific local configuration associated with a specific set of one or more rules and / or policies.

[0062] In some embodiments, the process 400 includes, after receiving the first response, sending a second request to the first TSCTSF to request that a particular quality of service (QoS) be provided for a particular application function (AF) session, and, after sending the second request, receiving a second response from the first TSCTSF accepting the second request.

[0063] In some embodiments, the second request is an Ntsctsf_QoSandTSCAssistance_Create request and the second response is an Ntsctsf_QoSandTSCAssistance_Create response.

[0064] 5 illustrates a process 500 performed by the TSCTSF 106 according to some embodiments. The process 500 may begin at step s502. Step s502 includes sending a first request associated with an AF session bound to a PDU session to the PCF 108. Step s504 includes receiving, after sending the first request, a first response from the PCF indicating that the first request is rejected, the first response indicating that a TSCTSF is not required for the AF session bound to the PDU session.

[0065] In some embodiments, the first request is a request to create one or more policies for a PDU session or a request to subscribe to reporting of one or more events in the PCF.

[0066] In some embodiments, the first request is one of an Npcf_PolicyAuthorization_Create request or an Npcf_PolicyAuthorization_Subscribe request.

[0067] In some embodiments, whether a TSCTSF may be required for an AF session bound to a PDU session is determined by the PCF based on any one or more of 5GS bridge information, a specific data network name (DNN), a specific network slice selection assistance information (S-NSSAI), a specific application identifier (ID) identifying a specific application, a specific group ID identifying a user equipment (UE) group, or a specific local configuration associated with a specific set of one or more rules and / or policies.

[0068] In some embodiments, the process 500 includes receiving a second request from a network exposure function (NEF) to request that a particular quality of service (QoS) be provided for a particular application function (AF) session, and after receiving the second request, sending a second response to the NEF rejecting the second request, wherein the second response indicates that a TSCTSF is not required for the AF session bound to the PDU session.

[0069] In some embodiments, the second request is an Ntsctsf_QoSandTSCAssistance_Create request and the second response is an Ntsctsf_QoSandTSCAssistance_Create response.

[0070] 6 is a block diagram of an apparatus 600, according to some embodiments, for implementing any one or combination of the AF 102, the NEF 104, the TSCTSF 106, and the PCF 108. As shown in FIG. 6, the apparatus 600 includes a processing circuit (PC) 602, which may include one or more processors (P) 655 (e.g., a general-purpose microprocessor and / or one or more other processors, such as an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), etc.), which may be co-located in a single enclosure or a single data center, or may be geographically distributed (i.e., the apparatus 600 may be a distributed computing device); The PC 602 may comprise: a network interface 648, including a transmitter (Tx) 645 and a receiver (Rx) 647, for enabling the network interface 648 to connect (directly or indirectly) to the network (e.g., the network interface 648 may be wirelessly connected to the network 110, in which case the network interface 648 may be connected to an antenna arrangement); and a local storage unit (a.k.a. "data storage system") 608, which may include one or more non-volatile storage devices and / or one or more volatile storage devices. In embodiments in which the PC 602 comprises a programmable processor, a computer program product (CPP) 641 may be provided. The CPP 641 includes a computer readable medium (CRM) 642 that stores a computer program (CP) 643, which includes computer readable instructions (CRI) 644. The CRM 642 may be a non-transitory computer readable medium, such as a magnetic medium (e.g., a hard disk), an optical medium, a memory device (e.g., a random access memory, a flash memory), etc.In some embodiments, the CRI 644 of the computer program 643 is configured to cause the device 600 to perform the steps described herein (e.g., steps described herein with reference to flowcharts) when the CRI is executed by the PC 602. In other embodiments, the device 600 may be configured to perform the steps described herein without the need for code. That is, for example, the PC 602 may simply consist of one or more ASICs. Thus, the functionality of the embodiments described herein may be implemented in hardware and / or software.

[0071] Abbreviation TIFF2026506282000002.tif109148

[0072] Overview of the embodiment

[0073] Some of the above-described embodiments can be summarized as follows: -------------------------------------------------------------------------------- The PCF may determine if the Create request is not routed via the TSCTSF, and if so, may return a special error cause to the NEF, indicating that the signaling path for the entire AF session must pass via the TSCTSF. According to TS 23.501, 6.2.29 TSCTSF, the TSCTSF supports the detection of 5GS bridge information and the determination of the requested PDB (another QoS parameter whose priority level can be determined by the TSCTSF). Therefore, if the TSCTSF is required in the signaling path, the PCF needs to inform the TSCTSF about the 5GS bridge information. And to be able to inform the TSCTSF, the PCF needs to know in advance (based on DNN / S-NSSAI and GPSI and / or SUPI / Internal Group Id or local configuration) whether the PDU session is for TSC communication. Considering the above, if a PCF receives an Npcf_PolicyAuthorization_Create request to bind to a PDU session for TSC communication, but this request is not issued by a TSCTSF, the PCF may reject the request and indicate that a TSCTSF is required for a TSC PDU session; similarly, if a PCF receives an Npcf_PolicyAuthorization_Creation request issued by a TSCTSF, but the PDU session is not for TSC communication, the PCF may reject the request and indicate that a TSCTSF is not required for a non-TSC PDU session. For the stage 3 specification, the PCF may check which NF is sending the request based on the User-Agent HTTP header included by the NF service consumer (see TS 29.500, 5.2.2.2). Then, based on the value received in the User-Agent HTTP header: (Impact on TS 29.514) If User-Agent: TSCTSF and the PDU session is not a TSC PDU session, the PCF returns 403 Forbidden with error cause (for example) NON_TSC_PDU_SESSION to TSCTSF. The TSCTSF forwards this error to the NEF (impact in TS 29.565), which then selects the PCF rather than the TSCTSF in subsequent attempts to create an AF session (impact in TS 29.522). (Impact on TS 29.514) If User-Agent: NEF (or AF) and the PDU session is a TSC PDU session, the PCF returns 403 Forbidden with error cause (for example) TSC_PDU_SESSION to the NEF (or AF). (Impact on TS 29.522) The NEF then includes the TSCTSF in the signaling path for subsequent attempts to create an AF session. --------------------------------------------------------------------------------

[0074] A1. A method (300) performed by a PCF (Policy Control Function) (108), said method comprising: receiving (s302) a first request associated with an AF (Application Function) session bound to a PDU (Protocol Data Unit) session from either a NEF (Network Publishing Function) (104) or a TSCTSF (Time Sensitive Communication and Time Synchronization Function) (106); After receiving the first request related to the AF session bound to the PDU session, determining whether the PDU session is likely for TSC (Time Sensitive Communication) (s304); determining whether to accept or reject the first request based on a determination of whether the PDU session is likely for a TSC (s306); sending a first response to the NEF or the TSCTSF indicating whether the first request is accepted (s308); A method comprising:

[0075] A1a. The method of embodiment A1, comprising: determining whether the first request was sent by the NEF or originated by the TSCTSF; The method of claim 1, wherein whether to accept or reject the first request is determined further based on a determination of whether the first request was sent by the NEF or the TSCTSF.

[0076] A2. A method of embodiment A1 or A1a, wherein the first request is a request to create one or more policies for the PDU session bound to the AF session or a request to subscribe to reporting of one or more events in the PCF.

[0077] A3. The method of embodiment A2, wherein the first request comprises: Npcf_PolicyAuthorization_Create request, or Npcf_PolicyAuthorization_Subscribe request, A method, which is any one of the following:

[0078] A4. The method of any one of embodiments A1 to A3, wherein determining whether the PDU session is likely for a TSC comprises: 5GS Bridge Information, A specific DNN (Data Network Name), A specific S-NSSAI (Network Slice Selection Assistance Information), A specific application ID (identifier) ​​that identifies a specific application, A specific group ID that identifies a group of UEs (user equipment), or a particular local configuration associated with a particular set of one or more rules and / or policies; The method is determined based on any one or more of the following:

[0079] A5. The method of any one of embodiments A1a to A4, comprising: The method includes identifying that the first request is sent by the NEF; and determining that the PDU session bound to the AF session is potentially for the TSC; the first response is a rejection message rejecting the first request; The method, wherein the reject message indicates that a TSCTSF is required for the AF session bound to the PDU session.

[0080] A6. The method of any one of embodiments A1a to A4, comprising: The method includes identifying that the first request was sent by the TSCTSF; and determining that the PDU session bound to the AF session is not likely for the TSC; the first response is a rejection message rejecting the first request; The method, wherein the rejection message indicates that a TSCTSF is not required for the AF session bound to the PDU session.

[0081] B1. A method (400) performed by a Network Publishing Function (NEF) (104), said method comprising: sending (s402) a first request related to an AF (Application Function) session bound to a PDU (Protocol Data Unit) session to a PCF (Policy Control Function) (108); and after sending the first request, receiving (s404) a first response from the PCF indicating that the first request has been denied; The first response indicates that a Time Sensitive Communication and Time Synchronization Function (TSCTSF) is required for the AF session bound to the PDU session, NEF.

[0082] B2. The method of embodiment B1, wherein the first request is a request to create one or more policies for the PDU session bound to the AF session or a request to subscribe to reporting of one or more events in the PCF.

[0083] B3. The method of embodiment B2, wherein the first request comprises: Npcf_PolicyAuthorization_Create request, or Npcf_PolicyAuthorization_Subscribe request, A method, which is any one of the following:

[0084] B4. The method of any one of embodiments B1 to B3, wherein whether a TSCTSF is required for the AF session bound to the PDU session is determined by the PCF: 5GS Bridge Information, A specific DNN (Data Network Name), A specific S-NSSAI (Network Slice Selection Assistance Information), A specific application ID (identifier) ​​that identifies a specific application, A specific group ID that identifies a group of UEs (user equipment), or a particular local configuration associated with a particular set of one or more rules and / or policies; The method is determined based on any one or more of the following:

[0085] B5. The method of any one of embodiments B1-B4, comprising: After receiving the first response, sending a second request to the first TSCTSF to request that a specific QoS (Quality of Service) be provided for a specific AF (Application Function) session; receiving, after sending the second request, a second response from the first TSCTSF accepting the second request; A method comprising:

[0086] B6. The method of embodiment B5, the second request is an Ntsctsf_QoSandTSCAssistance_Create request; The method, wherein the second response is a Ntsctsf_QoSandTSCAssistance_Create response.

[0087] C1. A method (500) performed by a Time Sensitive Communication and Time Synchronization Function (106) (TSCTSF), said method comprising: sending (s502) a first request related to an AF (Application Function) session bound to a PDU (Protocol Data Unit) session to a PCF (Policy Control Function) (108); and after sending the first request, receiving a first response from the PCF indicating that the first request has been denied (s504); The first response indicates that a TSCTSF is not required for the AF session bound to the PDU session.

[0088] C2. A method of embodiment C1, wherein the first request is a request to create one or more policies for the PDU session or a request to subscribe to reporting of one or more events in the PCF.

[0089] C3. The method of embodiment C2, wherein the first request comprises: Npcf_PolicyAuthorization_Create request, or Npcf_PolicyAuthorization_Subscribe request, A method, which is any one of the following:

[0090] C4. The method of any one of embodiments C1 to C3, wherein determining whether a TSCTSF may be required for the AF session bound to the PDU session is performed by the PCF: 5GS Bridge Information, A specific DNN (Data Network Name), A specific S-NSSAI (Network Slice Selection Assistance Information), A specific application ID (identifier) ​​that identifies a specific application, A specific group ID that identifies a group of UEs (user equipment), or a particular local configuration associated with a particular set of one or more rules and / or policies; The method is determined based on any one or more of the following:

[0091] C5. The method of any one of embodiments C1-C4, comprising: receiving a second request from a Network Exposure Function (NEF) to request that a particular Quality of Service (QoS) be provided for a particular Application Function (AF) session; after receiving the second request, sending a second response to the NEF rejecting the second request; The second response indicates that a TSCTSF is not required for the AF session bound to the PDU session.

[0092] C6. The method of embodiment C5, the second request is an Ntsctsf_QoSandTSCAssistance_Create request; The method, wherein the second response is a Ntsctsf_QoSandTSCAssistance_Create response.

[0093] D1. A computer program (600) comprising instructions (644) that, when executed by a processing circuit (602), cause the processing circuit to perform the method of any of embodiments A1-C6.

[0094] D2. A carrier comprising the computer program of embodiment D2, the carrier being one of an electrical signal, an optical signal, a radio signal, and a computer-readable storage medium.

[0095] E1. A PCF (Policy Control Function) (108), said PCF comprising: receiving (s302) a first request associated with an AF (Application Function) session bound to a PDU (Protocol Data Unit) session from either a NEF (Network Publishing Function) (104) or a TSCTSF (Time Sensitive Communication and Time Synchronization Function) (106); After receiving the first request related to the AF session bound to the PDU session, determining whether the PDU session is likely for TSC (Time Sensitive Communication) (s304); determining whether to accept or reject the first request based on a determination of whether the PDU session is likely for a TSC (s308); sending (s310) a first response to the NEF or the TSCTSF indicating whether the first request is accepted; The PCF is configured to:

[0096] E2. The PCF of embodiment E1, wherein the PCF is configured to perform the method of any of embodiments A2-A6.

[0097] F1. A NEF (Network Publish Function) (104), said NEF comprising: sending (s402) a first request related to an AF (Application Function) session bound to a PDU (Protocol Data Unit) session to a PCF (Policy Control Function) (108); and after sending the first request, receiving (s404) a first response from the PCF indicating that the first request has been rejected; The first response indicates that a Time Sensitive Communication and Time Synchronization Function (TSCTSF) is required for the AF session bound to the PDU session, NEF.

[0098] F2. The NEF of embodiment F1, wherein the NEF is configured to perform the method of any of embodiments B2 to B6.

[0099] G1. A Time Sensitive Communication and Time Synchronization Function (106) (TSCTSF), comprising: sending (s502) a first request related to an AF (Application Function) session bound to a PDU (Protocol Data Unit) session to a PCF (Policy Control Function) (108); and after sending the first request, receiving (s504) a first response from the PCF indicating that the first request has been rejected; The first response indicates that a TSCTSF is not required for the AF session bound to the PDU session.

[0100] G2. The TSCTSF of embodiment G1, wherein the TSCTSF is configured to perform the method of any of embodiments C2 through C6.

[0101] H1. An apparatus (600) comprising: A processing circuit (602); and a memory (641), the memory containing instructions executable by the processing circuitry such that the apparatus is operable to perform the method of any one of embodiments A1 to C6.

[0102] conclusion

[0103] While various embodiments have been described herein, it should be understood that they are presented by way of example only, and not limitation. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the present disclosure unless otherwise indicated herein or clearly contradicted by context.

[0104] As used herein, sending a message "to" or "toward" an intended recipient encompasses sending the message directly to the intended recipient or sending the message indirectly to the intended recipient (i.e., one or more other nodes are used to relay the message from the source node to the intended recipient). Similarly, as used herein, receiving a message "from" a sender encompasses receiving the message directly from the sender or receiving the message indirectly from the sender (i.e., one or more nodes are used to relay the message from the sender to the receiving node). Furthermore, as used herein, "a" means "at least one" or "one or more."

[0105] Additionally, while the processes described above and illustrated in the figures are shown as a series of steps, this is done for illustrative purposes only, and it is therefore contemplated that some steps may be added, some steps may be omitted, the order of steps may be rearranged, and some steps may be performed in parallel.

Claims

1. A method (300) performed by a Policy Control Function (108) (PCF), the method comprising: receiving (s302) a first request related to an AF (Application Function) session bound to a PDU (Protocol Data Unit) session from either a NEF (Network Publishing Function) (104) or a TSCTSF (Time Sensitive Communications and Time Synchronization Function) (106); After receiving the first request related to the AF session bound to the PDU session, determining whether the PDU session may be for TSC (Time Sensitive Communication) (s304); determining whether to accept or reject the first request based on a determination of whether the PDU session is likely for a TSC (s306); sending (s308) a first response to the NEF or the TSCTSF indicating whether the first request is accepted; A method comprising:

2. 10. The method of claim 1, determining whether the first request was originated by the NEF or the TSCTSF; The method, wherein whether to accept or reject the first request is determined further based on a determination of whether the first request was originated by the NEF or the TSCTSF.

3. 3. The method of claim 1 or 2, The method, wherein the first request is a request to create one or more policies for the PDU session bound to the AF session, or a request to subscribe to reporting of one or more events in the PCF.

4. 4. The method of claim 3, wherein the first request comprises: Npcf_PolicyAuthorization_Create request, or Npcf_PolicyAuthorization_Subscribe request, The method is any one of the following:

5. 5. The method according to any one of claims 1 to 4, Whether the PDU session is likely to be for TSC is determined by 5GS bridge information, A specific DNN (Data Network Name), A specific S-NSSAI (Network Slice Selection Assistance Information), A specific application ID (identifier) ​​that identifies a specific application; A specific group ID that identifies a group of UEs (user equipment), or a particular local configuration associated with a particular set of one or more rules and / or policies; The method is determined based on any one or more of the following:

6. 6. The method according to any one of claims 1 to 5, The method includes identifying that the first request was originated by the NEF; Determining whether the PDU session is likely for a TSC includes determining that the TSCTSF is a network function (NF) type required for the request; The method, wherein the first response is a denial message that denies the first request.

7. 7. The method of claim 6, wherein the reject message indicates that a TSCTSF is required for the AF session bound to the PDU session.

8. 6. The method according to any one of claims 1 to 5, The method includes identifying that the first request was sent by the TSCTSF; and determining that the PDU session bound to the AF session is not likely for the TSC; the first response is a rejection message rejecting the first request; The method, wherein the rejection message indicates that a TSCTSF is not required for the AF session bound to the PDU session.

9. A method (400) performed by a Network Publish Function (NEF) (104), the method comprising: sending (s402) a first request related to an AF (Application Function) session bound to a PDU (Protocol Data Unit) session towards a PCF (Policy Control Function) (108); and receiving (s404) after sending the first request, a first response from the PCF indicating that the first request is denied; The method, wherein the first response indicates that a Time Sensitive Communications and Time Synchronization Function (TSCTSF) is required for the AF session bound to the PDU session.

10. 10. The method of claim 9, The method, wherein the first request is a request to create one or more policies for the PDU session bound to the AF session, or a request to subscribe to reporting of one or more events in the PCF.

11. 11. The method of claim 10, wherein the first request comprises: Npcf_PolicyAuthorization_Create request, or Npcf_PolicyAuthorization_Subscribe request, The method is any one of the following:

12. 12. The method according to any one of claims 9 to 11, Whether a TSCTSF is required for the AF session bound to the PDU session is determined by the PCF: 5GS bridge information, A specific DNN (Data Network Name), A specific S-NSSAI (Network Slice Selection Assistance Information), A specific application ID (identifier) ​​that identifies a specific application; A specific group ID that identifies a group of UEs (user equipment), or a particular local configuration associated with a particular set of one or more rules and / or policies; The method is determined based on any one or more of the following:

13. 13. The method of any one of claims 9 to 12, comprising: After receiving the first response, sending a second request towards the first TSCTSF to request that a specific QoS (Quality of Service) be provided for a specific AF (Application Function) session; receiving, after sending the second request, a second response from the first TSCTSF accepting the second request; A method comprising:

14. 14. The method of claim 13, the second request is an Ntsctsf_QoSandTSCAssistance_Create request; The method, wherein the second response is a Ntsctsf_QoSandTSCAssistance_Create response.

15. A method (500) performed by a Time Sensitive Communication and Time Synchronization Function (TSCTSF) (106), the method comprising: sending (s502) a first request related to an AF (Application Function) session bound to a PDU (Protocol Data Unit) session towards a PCF (Policy Control Function) (108); and receiving (s504) a first response from the PCF after sending the first request, the first response indicating that the first request has been denied; The first response indicates that a TSCTSF is not required for the AF session bound to the PDU session.

16. 16. The method of claim 15, wherein the first request is a request to create one or more policies for the PDU session or a request to subscribe to reporting of one or more events in the PCF.

17. 17. The method of claim 16, wherein the first request comprises: Npcf_PolicyAuthorization_Create request, or Npcf_PolicyAuthorization_Subscribe request, The method is any one of the following:

18. 18. The method of any one of claims 15 to 17, Whether a TSCTSF may be required for the AF session bound to the PDU session is determined by the PCF: 5GS bridge information, A specific DNN (Data Network Name), A specific S-NSSAI (Network Slice Selection Assistance Information), A specific application ID (identifier) ​​that identifies a specific application; A specific group ID that identifies a group of UEs (user equipment), or a particular local configuration associated with a particular set of one or more rules and / or policies; The method is determined based on any one or more of the following:

19. 19. The method of any one of claims 15 to 18, receiving a second request from a Network Exposure Function (NEF) to request that a particular Quality of Service (QoS) be provided for a particular Application Function (AF) session; after receiving the second request, sending a second response to the NEF rejecting the second request; The second response indicates that a TSCTSF is not required for the AF session bound to the PDU session.

20. 20. The method of claim 19, the second request is an Ntsctsf_QoSandTSCAssistance_Create request; The method, wherein the second response is a Ntsctsf_QoSandTSCAssistance_Create response.

21. A computer program (600) comprising instructions (644) that, when executed by a processing circuit (602), cause the processing circuit to perform the method of any one of claims 1 to 20.

22. 22. A carrier containing the computer program of claim 21, wherein the carrier is one of an electrical signal, an optical signal, a radio signal, and a computer readable storage medium.

23. A PCF (Policy Control Function) (108), said PCF comprising: receiving (s302) a first request related to an AF (Application Function) bound to a PDU (Protocol Data Unit) session from either a NEF (Network Publishing Function) (104) or a TSCTSF (Time Sensitive Communications and Time Synchronization Function) (106); After receiving the first request related to the AF session bound to the PDU session, determining whether the PDU session may be for TSC (Time Sensitive Communication) (s304); determining whether to accept or reject the first request based on a determination of whether the PDU session is likely for a TSC (s308); sending (s310) a first response to the NEF or the TSCTSF indicating whether the first request is accepted; The PCF is configured to:

24. 24. A PCF according to claim 23, wherein the PCF is configured to perform the method according to any one of claims 2 to 8.

25. A Network Publish Function (NEF) (104), said NEF comprising: sending (s402) a first request related to an AF (Application Function) session bound to a PDU (Protocol Data Unit) session towards a PCF (Policy Control Function) (108); and (s404) receiving, after sending the first request, a first response from the PCF indicating that the first request has been denied; The first response is an NEF indicating that a Time Sensitive Communication and Time Synchronization Function (TSCTSF) is required for the AF session bound to the PDU session.

26. 26. The NEF of claim 25, wherein the NEF is configured to perform the method of any one of claims 10 to 14.

27. TSCTSF (Time Sensitive Communication and Time Synchronization Function) (106), said TSCTSF comprising: sending (s502) a first request related to an AF (Application Function) session bound to a PDU (Protocol Data Unit) session towards a PCF (Policy Control Function) (108); and (s504) receiving, after sending the first request, a first response from the PCF indicating that the first request has been denied; The first response is a TSCTSF indicating that a TSCTSF is not required for the AF session bound to the PDU session.

28. 28. A TSCTSF according to claim 27, wherein the TSCTSF is configured to perform a method according to any one of claims 16 to 20.

29. An apparatus (600), a processing circuit (602); and a memory (641), said memory containing instructions executable by said processing circuitry, whereby said apparatus is operable to perform the method of any one of claims 1 to 20.

Images