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

Abstract

A method implemented by a policy control function (PCF) is provided. The method includes receiving a first request related to an Application Function (AF) session bound to a Protocol Data Unit (PDU) session from a Network Open Function (NEF) or a Time Sensitive Communication and Time Synchronization Function (TSCTSF). The method also includes, upon receiving the first request relating to the AF session bound to the PDU session, determining whether the PDU session is potentially used for time sensitive communication (TSC). The method further includes determining whether to accept or reject the first request based on determining whether the PDU session is potentially used for the TSC; and transmitting a first response indicating whether the first request is accepted to the NEF or the TSCTSF.

Description

Technical Field

[0001] The present disclosure relates to processing messages related to an application function (AF) session bound to a protocol data unit (PDU) session. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) Technical Specification 23.502 Version 17.7.0 (TS 23.502) discloses a procedure 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 determines whether to direct signaling to the Policy Control Function (PCF) directly or via the Time Sensitive Communication and Time Synchronization Function (TSCTSF). This determination can be made based on the requested optional QoS parameter set or a set of separate QoS parameters received from the AF.

[0004] After establishing the AF session with the required QoS, the AF may want to update the AF session with the updated QoS. In this 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 determines whether to direct the signaling to the PCF directly or via the TSCTSF. This determination may be made based on the requested optional QoS parameter set received from the AF or a set of separate QoS parameters.

[0005] To request a specific QoS, a create request and / or update request may include:

[0006] (1) QoS reference + (optional) traffic characteristics (i.e., burst arrival time, periodicity, time domain, time to live, flow direction, user equipment (UE) (uplink) or user plane function (UPF) (downlink)), or

[0007] (2) Individual QoS parameters (i.e., requested 5G system (5GS) latency (optional), requested priority (optional), requested guaranteed bit rate, requested maximum bit rate, maximum burst size) + (optional) service characteristics (i.e., flow direction, burst arrival time at UE (uplink) or UPF (downlink), periodicity, time domain, time to live).

[0008] 3GPP TS 23.503 Version 17.6.0 (TS 23.503) recommends that create requests and update requests associated with the same AF session should have the same type of QoS information. For example, where a create request includes a QoS reference, the AF cannot include separate QoS parameters in place of the QoS reference. In other words, the AF cannot replace the previously provided QoS in the create request with separate QoS parameters in an update request. In another example, where a create request includes separate QoS parameters, the AF cannot include a QoS reference in place of the separate QoS parameters.

[0009] As briefly discussed above, signaling from the NEF to the PCF may be implemented directly between the NEF and the PCF, or may be implemented indirectly via the TSC TSF.

[0010] Such indirect signaling (i.e., signaling via TSCTSF) may be required in the case where 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 service characteristics (i.e., flow direction, burst arrival time at UE (uplink) or UPF (downlink) , periodicity, time domain, lifetime), and such QoS parameters may be provided regardless of whether the create and update requests contain a QoS reference or separate QoS parameters. Another example is when a separate QoS parameter in a create or update request contains a requested 5GS delay (e.g., which may include a UE device-side Time Sensitive Network (TSN) translator (UE-DS-TT) dwell time). In other cases, directed signaling may be implemented between the NEF and the PCF (not through the TSCTSF). Summary of the Invention

[0011] There are some challenges. For example, as explained 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 should 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).

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

[0013] If the update request is rejected, the AF will need to send another create request (directly or via TSCTSF), resulting in excessive signaling and service interruption.Thus, during creation of an AF session, the signaling path between the NEF and the PCF needs to be determined.

[0014] In order to solve this problem, in one aspect of an embodiment of the present disclosure, a method implemented by a policy control function (PCF) is provided. The method includes: receiving a first request related to an application function (AF) session bound to a protocol data unit (PDU) session from a network exposure function NEF or a time-sensitive communication and time synchronization function (TSCTSF). The method also includes: after receiving the first request related to the AF session bound to the PDU session, determining whether the PDU session is potentially used for time-sensitive communication (TSC). The method also includes: based on determining whether the PDU session is potentially used for TSC, determining whether to accept or reject the first request. The method also includes: sending a first response to the NEF or the TSCTSF indicating whether the first request is accepted.

[0015] In another aspect, a method implemented by a network exposure function (NEF) is provided. The method includes sending a first request related to an application function (AF) session bound to a protocol data unit (PDU) session to a policy control function (PCF). The method also includes receiving a first response from the PCF after sending the first request, indicating that the first request is rejected, wherein 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.

[0016] In another aspect, a method implemented by a Time Sensitive Communication and Time Synchronization Function (TSCTSF) is provided. The method comprises: sending a first request related to an Application Function (AF) session bound to a Protocol Data Unit (PDU) session to a Policy Control Function (PCF). The method further comprises: after sending the first request, receiving (s504) a first response from the PCF indicating that the first request is rejected, wherein the first response indicates that a TSCTSF is not required for the AF session bound to the PDU session.

[0017] In another aspect, a computer program is provided comprising instructions which, when executed by a processing circuit (602), cause the processing circuit to implement the method of any one of the above embodiments.

[0018] In another aspect, a carrier containing the computer program of the above embodiment is provided, wherein the carrier is one of an electronic signal, an optical signal, a radio signal and a computer-readable storage medium.

[0019] In another aspect, a policy control function (PCF) is provided. The PCF is configured to: receive a first request related to an application function (AF) session bound to a protocol data unit (PDU) session from a network exposure function (NEF) or a time-sensitive communication and time synchronization function (TSCTSF); after receiving the first request related to the AF session bound to the PDU session, determine whether the PDU session is potentially used for time-sensitive communication (TSC); the PCF is configured to: determine whether to accept or reject the first request based on determining whether the PDU session is potentially used for TSC; and send a first response to the NEF or the TSCTSF indicating whether the first request is accepted.

[0020] In another aspect, a network exposure function (NEF) is provided. The NEF is configured to: send a first request related to an application function (AF) session bound to a protocol data unit (PDU) session to a policy control function (PCF); after sending the first request, receive a first response from the PCF indicating that the first request is rejected, wherein 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.

[0021] In another aspect, a time-sensitive communication and time synchronization function (TSCTSF) is provided. The TSCTSF is configured to: send a first request related to an application function (AF) session bound to a protocol data unit (PDU) session to a policy control function (PCF); after sending the first request, receive a first response from the PCF indicating that the first request is rejected, wherein the first response indicates that the TSCTSF is not required for the AF session bound to the PDU session.

[0022] In another aspect, a device is provided, comprising a processing circuit; and a memory containing instructions executable by the processing circuit, whereby the device is operable to implement the method of any one of the above embodiments.

[0023] Some embodiments of the present disclosure allow the signaling path for requests to be determined during creation of an AF session, thereby minimizing the probability that legitimate requested updates from the AF are rejected. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0025] Figure 1 A portion of a system according to some embodiments is shown.

[0026] Figure 2A A process according to some embodiments is shown.

[0027] Figure 2B A process according to some embodiments is shown.

[0028] Figure 3 A process according to some embodiments is shown.

[0029] Figure 4 A process according to some embodiments is shown.

[0030] Figure 5 A process according to some embodiments is shown.

[0031] Figure 6 An apparatus according to some embodiments is shown. DETAILED DESCRIPTION

[0032] Figure 1 1 shows 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 computer, 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, which includes an AF 102, a NEF 104, a TSCTSF 106, and a PCF 108. Note that Figure 1 The number of each entity (102, 104, 106, 108, 114, 116, etc.) shown in FIG is provided only for the purpose of simplicity of explanation and does not limit the embodiments of the present disclosure in any way. Note also that Figure 1 Only a portion of the 3GPP network system 112 is shown (meaning that the 3GPP network system 112 may include additional entities). The network functions / nodes may be implemented as network elements on dedicated hardware, as software instances running on dedicated hardware, or as virtualized functions instantiated on an appropriate platform (e.g., on a cloud infrastructure).

[0033] AF 102 is a control plane function within the 5G core network. AF 102 can be configured to create an AF session for providing application services (e.g., video streaming services) to UE 116. Figure 2A and Figure 2B A process 200 for creating an AF session is shown in accordance with some embodiments.

[0034] Process 200 may begin with AF 102 sending AF request 202 to NEF 104. In some embodiments, AF request 202 may correspond to a request to provide a specific QoS (e.g., minimum video resolution) for an AF session (e.g., a video streaming service) for UE 116. An example of such a request is an Nnef_AFsessionWithQoS create request.

[0035] In the event that the AF request 202 is a request for providing a specific QoS, upon receiving the AF request 202, the NEF 104 may implement step s202. Step s202 includes determining whether to authorize the AF request 202. If the NEF 104 determines not to authorize 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 denied. An example of the AF response 216 is an Nnef_AFsessionWithQoS Create Response.

[0036] On the other hand, if the NEF 104 determines that the AF request 202 is authorized, in step s204, the NEF 104 may also determine whether to invoke the TSCTSF 106 when signaling the PCF 108, or whether to signal the PCF 108 directly (i.e., whether to send / receive messages to / from the PCF 108 without going through the TSCTSF 106, or whether to send / receive messages to / from the PCF 108 via the TSCTSF 106). This determination may be based on the presence of a specific QoS reference or a specific QoS separate parameter in the AF request 202. Additionally or alternatively, this determination may be based on an AF identifier that identifies a specific AF session or a parameter provided by the AF that describes a service characteristic.

[0037] like Figure 2A , in the event that the NEF 104 determines to send a signal directly to the PCF 108 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 for the PDU session to which the AF session is bound, as required by the AF 102. In one example, the NEF request 204 is an Npcf_PolicyAuthorization_Create request.

[0038] 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 used for time-sensitive communication (TSC) (i.e., whether TSC TSF is potentially required in the signaling path between the NEF 104 and the PCF 108). An example of determining whether a PDU session is used for TSC is determining whether the PDU session is potentially affected by a Precision Time Protocol (PTP) time synchronization service. Whether the PDU session for which the NEF request 204 is made is used for TSC may be determined based on any one or more of the following: 5GS bridge information, data network name (DNN), network slice selection assistance information (S-NSSAI), an application identifier (ID) identifying an application, a group ID identifying a UE group, and / or a local configuration. For example, the presence of only 5GS bridge information may indicate that the PDU session may be used for TSC. Alternatively or additionally, a DNN identifying a specific data network, an S-NSSAI identifying a specific network slice, and / or an application ID identifying a specific application may indicate that the PDU session is potentially used for TSC. More detailed information on these parameters is provided in Section 5.2.27.3 of 3GPP TS 23.502, which is hereby incorporated by reference.

[0039] Note that the PCF 108 is aware of whether the NEF request 204 was initiated by the NEF 104 or the TSCTSF 106. For example, the NEF 104 and the TSCTSF 106 may be configured to include a User-Agent HTTP header in the requests they send to the PCF 108. In another example, each request may include a different information element or parameter that identifies the sender of the request. Thus, if the PCF 108 determines that the PDU session bound to the AF session is potentially used for TSC, the PCF 108 may reject the NEF request 204 because the request was initiated by the NEF 104, indicating that there is no TSCTSF between the NEF 104 and the PCF 108 for this signaling.

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

[0041] On the other hand, if the PCF 108 determines that the PDU session bound to the AF session is potentially not for TSC, the PCF 108 may accept the NEF request 204 because the request is initiated by the NEF 104, which indicates that there is no TSC TSF 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.

[0042] After 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 the AF response 216 is a Nnef_AFsessionWithQoS Create Response.

[0043] Return to step s204, as Figure 2B As shown in FIG, if the NEF 104 determines that the TSCTSF should be invoked when signaling the PCF 108, the NEF 104 may send an NEF request 206 to the TSCTSF 106 instead of sending the NEF request 204 to the PCF 108. In some embodiments, the NEF request 206 is a request for providing a specific QoS for the AF session. In one example, the NEF request 206 is an Ntsctsf_QoSandSCAssistance_Create request.

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

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

[0046] 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 used for time-sensitive communication (TSC) (i.e., whether a TSCTSF is potentially required in the signaling path between the NEF 104 and the PCF 108). One example of determining whether a PDU session is potentially used for TSC is determining whether the PDU session is potentially affected by a Precision Time Protocol (PTP) time synchronization service. This determination may be made based on any one or more of the following: 5GS bridge information, a data network name (DNN), network slice selection assistance information (S-NSSAI), an application identifier (ID) identifying an application, a group ID identifying a UE group, and / or a local configuration.

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

[0048] The PCF 108 knows whether the TSCTSF request 208 was initiated by the NEF 104 or the TSCTSF 106 (e.g., by analyzing the User-Agent HTTP header of the NEF request 204). Therefore, if the PCF 108 determines that the PDU session is not potentially used for TSC, the PCF 108 can reject the TSCTSF request 208 because the request was initiated by the TSCTSF 106, indicating that a TSCTSF exists between the NEF 104 and the PCF 108 for this signaling. In this case, the PCF 108 can send a TSCTSF response 212 to the TSCTSF 106 indicating that the TSCTSF request 208 was rejected. In some embodiments, the TSCTSF response 212 can 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.

[0049] On the other hand, if the PCF 108 determines that the PDU session bound to the AF session is potentially used for TSC, the PCF 108 may accept the TSCTSF request 208 because the request is 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 is accepted.

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

[0051] After receiving the NEF response 214, the NEF 104 may send an AF response 214 to the AF 102, indicating whether the AF request 202 is accepted.

[0052] Figure 3 A process 300 implemented by the PCF 108 according to some embodiments is shown. 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 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 potentially used for time-sensitive communication (TSC). Step s306 includes determining, based on determining whether the PDU session is potentially used for TSC, whether to accept or reject the first request. Step s308 includes sending a first response to the NEF or the TSCTSF indicating whether the first request was accepted.

[0053] In some embodiments, process 300 includes determining whether the first request was initiated by the NEF or the TSCTSF, wherein determining whether to accept or reject the first request is further based on determining whether the first request was initiated by the NEF or the TSCTSF.

[0054] In some embodiments, the first request is a request to create one or more policies for a PDU session bound to an AF session, or a request to subscribe to reports of one or more events at the PCF.

[0055] In some embodiments, the first request is any one of: an Npcf_PolicyAuthorization_Create request; or an Npcf_PolicyAuthorization_Subscribe request.

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

[0057] In some embodiments, process 300 includes identifying that the first request is initiated by an NEF, determining whether the PDU session is potentially for a TSC includes determining that a TSC TSF is a network function NF type required for the request, and the first response is a rejection message rejecting the first request.

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

[0059] In some embodiments, process 300 includes identifying that the first request is sent by a TSCTSF, and determining that the PDU session bound to the AF session is potentially not for the TSC, the first response is a rejection message that rejects the first request, and the rejection message indicates that the TSCTSF is not required for the AF session bound to the PDU session.

[0060] Figure 4 A process 400 implemented by the NEF 104 according to some embodiments is shown. The process 400 may begin at step s402. Step s402 includes sending a first request related to an AF session bound to a PDU session to a PCF. Step s404 includes receiving a first response from the PCF indicating that the first request is rejected after sending the first request, wherein the first response indicates that a TSCTSF is required for the AF session bound to the PDU session.

[0061] In some embodiments, the first request is a request to create one or more policies for a PDU session bound to an AF session, or a request to subscribe to reports of one or more events at the PCF.

[0062] In some embodiments, the first request is any one of: an Npcf_PolicyAuthorization_Create request; or an Npcf_PolicyAuthorization_Subscribe request.

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

[0064] In some embodiments, process 400 includes: after receiving the first response, sending a second request to the first TSCTSF for requesting provision of a specific quality of service (QoS) for a specific application function (AF) session; and after sending the second request, receiving a second response from the first TSCTSF accepting the second request.

[0065] In some embodiments, the second request is a Ntsctsf_QoSandTSCAssistance_Create request and the second response is a Ntsctsf_QoSandTSCAssistance_Create response.

[0066] Figure 5A process 500 implemented by the TSCTSF 106 according to some embodiments is shown. The process 500 may begin at step s502. Step s502 includes sending a first request related to an AF session bound to a PDU session to the PCF 108. Step s504 includes receiving a first response from the PCF indicating that the first request was denied after sending the first request, wherein the first response indicates that the TSCTSF is not required for the AF session bound to the PDU session.

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

[0068] In some embodiments, the first request is any one of: an Npcf_PolicyAuthorization_Create request; or an Npcf_PolicyAuthorization_Subscribe request.

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

[0070] In some embodiments, process 500 includes: receiving a second request from a network exposure function NEF for requesting a specific quality of service QoS to be provided for a specific application function AF session; after receiving the second request, sending a second response to the NEF to reject the second request, wherein the second response indicates that TSCTSF is not required for the AF session bound to the PDU session.

[0071] In some embodiments, the second request is a Ntsctsf_QoSandTSCAssistance_Create request and the second response is a Ntsctsf_QoSandTSCAssistance_Create response.

[0072] Figure 6 6 is a block diagram of an apparatus 600 for implementing any one or a combination of the AF 102, NEF 104, TSCTSF 106, and PCF 108, according to some embodiments. Figure 6As shown in , the device 600 may include: a processing circuit (PC) 602, which may include one or more processors (P) 655 (for example, 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 housing or a single data center, or may be geographically distributed (i.e., the device 600 may be a distributed computing device); a network interface 648, which includes a transmitter (Tx) 645 and a receiver (Rx) 647, for enabling the device 600 to send data to and receive data from other nodes connected to a network 110 (e.g., an Internet Protocol (IP) network), wherein the network interface 648 is connected (directly or indirectly) to the network 110 (for example, the network interface 648 may be wirelessly connected to the network 110, in which case the network interface 648 is connected to an antenna device); and a local storage unit (also referred to as 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 where PC 602 includes a programmable processor, a computer program product (CPP) 641 may be provided. CPP 641 includes a computer-readable medium (CRM) 642 storing a computer program (CP) 643 including computer-readable instructions (CRI) 644. CRM 642 may be a non-transitory computer-readable medium, such as a magnetic medium (e.g., a hard drive), an optical medium, a storage device (e.g., random access memory, flash memory), or the like. In some embodiments, CRI 644 of computer program 643 is configured such that, when executed by PC 602, CRI causes apparatus 600 to implement the steps described herein (e.g., the steps described herein with reference to the flowcharts). In other embodiments, apparatus 600 may be configured to implement the steps described herein without requiring code. That is, for example, PC 602 may consist solely of one or more ASICs. Thus, the features of the embodiments described herein may be implemented in hardware and / or software.

[0073] abbreviation

[0074] abbreviation explain AF Application Features CN Core Network DNN Data network name DS-TT Device-side converter NF Network capabilities NEF Network openness PCF Policy control function PDB Packet Delay Budget QoS Quality of Service SMF Session management capabilities S-NSSAI Single network slice selection auxiliary information TSCAC Time-Sensitive Communication Auxiliary Container TSCTSF Time-sensitive communication and time synchronization capabilities UE User Equipment UPF User plane functions

[0075] Overview of the Examples

[0076] Some of the above embodiments can be summarized as follows:

[0077]

[0078]

[0079] A1. A method (300) implemented by a policy control function (PCF) (108), the method comprising:

[0080] receiving (s302) a first request related to an application function AF session bound to a protocol data unit PDU session from a network opening function NEF (104) or a time sensitive communication and time synchronization function TSCTSF (106);

[0081] After receiving the first request associated with the AF session bound to the PDU session, determining (s304) whether the PDU session is potentially used for time sensitive communication TSC;

[0082] determining (s306) whether to accept or reject the first request based on determining whether the PDU session is potentially for TSC; and

[0083] A first response is sent (s308) to the NEF or the TSCTSF, indicating whether the first request is accepted.

[0084] A1a. The method of embodiment A1, comprising:

[0085] Determine whether the first request is sent by the NEF or the TSCTSF, wherein

[0086] Whether to accept or reject the first request is also determined based on determining whether the first request is sent by the NEF or the TSCTSF.

[0087] A2. The method of embodiments 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 reports of one or more events at the PCF.

[0088] A3. The method of embodiment A2, wherein the first request is any of the following:

[0089] Npcf_PolicyAuthorization_Create request; or

[0090] Npcf_PolicyAuthorization_Subscribe request.

[0091] A4. The method of any one of embodiments A1-A3, wherein determining whether the PDU session is potentially for TSC is based on any one or more of the following:

[0092] 5GS bridge information;

[0093] Specific data network name DNN;

[0094] Specific network slice selection assistance information S-NSSAI;

[0095] A specific application identifier ID that identifies a specific application;

[0096] A specific group ID that identifies a group of user equipments UE; or

[0097] A specific local configuration associated with a specific set of one or more rules and / or policies.

[0098] A5. The method according to any one of embodiments A1a-A4, wherein

[0099] The method comprises: identifying that the first request is sent by the NEF, and determining that the PDU session bound to the AF session is potentially used for the TSC,

[0100] The first response is a rejection message rejecting the first request, and

[0101] The reject message indicates that a TSCTSF is required for the AF session bound to the PDU session.

[0102] A6. The method of any one of embodiments A1a-A4, wherein

[0103] The method comprises identifying that the first request is sent by the TSC TSF, and determining that the PDU session bound to the AF session is potentially not for the TSC,

[0104] The first response is a rejection message rejecting the first request, and

[0105] The reject message indicates that a TSCTSF is not required for the AF session bound to the PDU session.

[0106] B1. A method (400) implemented by a network open function (NEF) (104), the method comprising:

[0107] sending (s402) a first request related to an application function AF session bound to a protocol data unit PDU session to a policy control function PCF (108); and

[0108] After sending the first request, receiving (s404) a first response from the PCF indicating that the first request is rejected, wherein

[0109] 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.

[0110] 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 reports of one or more events at the PCF.

[0111] B3. The method of embodiment B2, wherein the first request is any of the following:

[0112] Npcf_PolicyAuthorization_Create request; or

[0113] Npcf_PolicyAuthorization_Subscribe request.

[0114] B4. The method of any one of embodiments B1-B3, wherein determining by the PCF whether a TSCTSF is required for the AF session bound to the PDU session is based on any one or more of the following:

[0115] 5GS bridge information;

[0116] Specific data network name DNN;

[0117] Specific network slice selection assistance information S-NSSAI;

[0118] A specific application identifier ID that identifies a specific application;

[0119] A specific group ID that identifies a group of user equipments UE; or

[0120] A specific local configuration associated with a specific set of one or more rules and / or policies.

[0121] B5. The method of any one of embodiments B1-B4, comprising:

[0122] After receiving the first response, sending a second request to the first TSCTSF for requesting provision of a specific quality of service (QoS) for a specific application function (AF) session; and

[0123] After sending the second request, a second response accepting the second request is received from the first TSCTSF.

[0124] B6. The method according to embodiment B5, wherein

[0125] The second request is a Ntsctsf_QoSandTSCAssistance_Create request, and

[0126] The second response is an Ntsctsf_QoSandTSCAssistance_Create response.

[0127] C1. A method (500) implemented by a time-sensitive communication and time synchronization function TSCTSF (106), the method comprising:

[0128] sending (s502) a first request related to an application function AF session bound to a protocol data unit PDU session to a policy control function PCF (108); and

[0129] After sending the first request, receiving (s504) a first response from the PCF indicating that the first request is rejected, wherein

[0130] The first response indicates that a TSCTSF is not required for the AF session bound to the PDU session.

[0131] C2. The 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 reports of one or more events at the PCF.

[0132] C3. The method of embodiment C2, wherein the first request is any of the following:

[0133] Npcf_PolicyAuthorization_Create request; or

[0134] Npcf_PolicyAuthorization_Subscribe request.

[0135] C4. The method of any one of embodiments C1-C3, wherein determining, by the PCF, whether a TSCTSF is potentially required for the AF session bound to the PDU session is based on any one or more of the following:

[0136] 5GS bridge information;

[0137] Specific data network name DNN;

[0138] Specific network slice selection assistance information S-NSSAI;

[0139] A specific application identifier ID that identifies a specific application;

[0140] A specific group ID that identifies a group of user equipments UE; or

[0141] A specific local configuration associated with a specific set of one or more rules and / or policies.

[0142] C5. The method of any one of embodiments C1-C4, comprising:

[0143] receiving, from the network exposure function NEF, a second request for requesting provision of a specific quality of service QoS for a specific application function AF session;

[0144] After receiving the second request, a second response rejecting the second request is sent to the NEF, wherein

[0145] The second response indicates that a TSCTSF is not required for the AF session bound to the PDU session.

[0146] C6. The method of embodiment C5, wherein

[0147] The second request is a Ntsctsf_QoSandTSCAssistance_Create request, and

[0148] The second response is an Ntsctsf_QoSandTSCAssistance_Create response.

[0149] D1. A computer program (600) comprising instructions (644) which, when executed by a processing circuit (602), cause the processing circuit to implement the method according to any one of embodiments A1-C6.

[0150] D2. A carrier embodying the computer program according to embodiment D1, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer-readable storage medium.

[0151] E1. A policy control function PCF (108), the PCF being configured to:

[0152] receiving (s302) a first request related to an application function AF session bound to a protocol data unit PDU session from a network opening function NEF (104) or a time sensitive communication and time synchronization function TSCTSF (106);

[0153] After receiving the first request associated with the AF session bound to the PDU session, determining (s304) whether the PDU session is potentially used for time sensitive communication TSC;

[0154] determining (s308) whether to accept or reject the first request based on determining whether the PDU session is potentially for TSC; and

[0155] A first response is sent (s310) to the NEF or the TSCTSF, indicating whether the first request is accepted.

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

[0157] F1. A network open function NEF (104), wherein the NEF is configured to:

[0158] sending (s402) a first request related to an application function AF session bound to a protocol data unit PDU session to a policy control function PCF (108); and

[0159] After sending the first request, receiving (s404) a first response from the PCF indicating that the first request is rejected, wherein

[0160] 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.

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

[0162] G1. A time-sensitive communication and time synchronization function TSCTSF (106), the TSCTSF being configured to:

[0163] sending (s502) a first request related to an application function AF session bound to a protocol data unit PDU session to a policy control function PCF (108); and

[0164] After sending the first request, receiving (s504) a first response from the PCF indicating that the first request is rejected, wherein

[0165] The first response indicates that a TSCTSF is not required for the AF session bound to the PDU session.

[0166] G2. The TSCTSF of embodiment G1, wherein the TSCTSF is configured to implement the method of any one of embodiments C2-C6.

[0167] H1. An apparatus (600), comprising:

[0168] processing circuitry (602); and

[0169] A memory (641) containing instructions executable by the processing circuitry, whereby the apparatus is operable to implement the method of any one of embodiments A1-C6.

[0170] in conclusion

[0171] Although various embodiments are described herein, it should be understood that they are presented by way of example only and not limitation. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above exemplary embodiments. In addition, unless otherwise indicated herein or unless clearly contradicted by the context, any combination of the above elements in all possible variations thereof is included in the present disclosure.

[0172] As used herein, sending a message "to" or "towards" an intended recipient includes sending the message directly to the intended recipient or 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). Likewise, as used herein, receiving a message "from" a sender includes receiving the message directly from the sender or 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" or "an" means "at least one" or "one or more"

[0173] Furthermore, although the processes described above and shown in the accompanying drawings are shown as a series of steps, this is done for illustrative purposes only. It is therefore contemplated that steps may be added, steps may be omitted, the order of steps may be rearranged, and steps may be performed in parallel.

Claims

1. A method (300) implemented by a policy control function (PCF) (108), the method comprising: receiving (s302) a first request related to an application function AF session bound to a protocol data unit PDU session from a network opening function NEF (104) or a time sensitive communication and time synchronization function TSCTSF (106); After receiving the first request associated with the AF session bound to the PDU session, determining (s304) whether the PDU session is potentially used for time sensitive communication TSC; determining (s306) whether to accept or reject the first request based on determining whether the PDU session is potentially for TSC; as well as A first response is sent (s308) to the NEF or the TSCTSF, indicating whether the first request is accepted.

2. The method according to claim 1, comprising: Determine whether the first request is initiated by the NEF or the TSCTSF, wherein Whether to accept or reject the first request is also determined based on determining whether the first request is initiated by the NEF or the TSCTSF.

3. The method according to claim 1 or 2, wherein: The first request is a request for creating one or more policies for the PDU session bound to the AF session, or a request for subscribing to reports of one or more events at the PCF.

4. The method according to claim 3, wherein: The first request is any of the following: Npcf_PolicyAuthorization_Create request; or Npcf_PolicyAuthorization_Subscribe request.

5. The method according to any one of claims 1 to 4, wherein Determining whether the PDU session is potentially for TSC is based on any one or more of the following: 5GS bridge information; Specific data network name DNN; Specific network slice selection assistance information S-NSSAI; A specific application identifier ID that identifies a specific application; A specific group ID that identifies a group of user equipments UEs; or A specific local configuration associated with a specific set of one or more rules and / or policies.

6. The method according to any one of claims 1 to 5, wherein The method comprises: Identifying that the first request is initiated by the NEF, Determining whether the PDU session is potentially for a TSC comprises determining that the TSC TSF is a network function NF type required for the request, and The first response is a rejection message rejecting the first request.

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

8. The method according to any one of claims 1 to 5, wherein The method comprises: identifying that the first request is sent by the TSC TSF, and determining that the PDU session bound to the AF session is potentially not for the TSC, The first response is a rejection message rejecting the first request, and The reject message indicates that a TSCTSF is not required for the AF session bound to the PDU session.

9. A method (400) implemented by a network open function (NEF) (104), the method comprising: sending (s402) a first request related to an application function AF session bound to a protocol data unit PDU session to a policy control function PCF (108); as well as After sending the first request, receiving (s404) a first response from the PCF indicating that the first request is rejected, wherein 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.

10. The method according to claim 9, wherein: The first request is a request for creating one or more policies for the PDU session bound to the AF session, or a request for subscribing to reports of one or more events at the PCF.

11. The method according to claim 10, wherein: The first request is any of the following: Npcf_PolicyAuthorization_Create request; or Npcf_PolicyAuthorization_Subscribe request.

12. The method according to any one of claims 9 to 11, wherein: The PCF determines whether a TSCTSF is required for the AF session bound to the PDU session based on any one or more of the following: 5GS bridge information; Specific data network name DNN; Specific network slice selection assistance information S-NSSAI; A specific application identifier ID that identifies a specific application; A specific group ID that identifies a group of user equipments UEs; or A specific local configuration associated with a specific set of one or more rules and / or policies.

13. The method according to any one of claims 9 to 12, comprising: After receiving the first response, sending a second request to the first TSCTSF for requesting provision of a specific quality of service QoS for a specific application function AF session; as well as After sending the second request, a second response accepting the second request is received from the first TSCTSF.

14. The method according to claim 13, wherein The second request is a Ntsctsf_QoSandTSCAssistance_Create request, and The second response is an Ntsctsf_QoSandTSCAssistance_Create response.

15. A method (500) implemented by a Time Sensitive Communication and Time Synchronization Function (TSCTSF) (106), the method comprising: sending (s502) a first request related to an application function AF session bound to a protocol data unit PDU session to a policy control function PCF (108); as well as After sending the first request, receiving (s504) a first response from the PCF indicating that the first request is rejected, wherein The first response indicates that a TSCTSF is not required for the AF session bound to the PDU session.

16. The method according to claim 15, wherein The first request is a request for creating one or more policies for the PDU session, or a request for subscribing to reports of one or more events at the PCF.

17. The method according to claim 16, wherein The first request is any of the following: Npcf_PolicyAuthorization_Create request; or Npcf_PolicyAuthorization_Subscribe request.

18. The method according to any one of claims 15 to 17, wherein: The PCF determines whether a TSCTSF is potentially required for the AF session bound to the PDU session based on any one or more of the following: 5GS bridge information; Specific data network name DNN; Specific network slice selection assistance information S-NSSAI; A specific application identifier ID that identifies a specific application; A specific group ID that identifies a group of user equipments UEs; or A specific local configuration associated with a specific set of one or more rules and / or policies.

19. The method according to any one of claims 15 to 18, comprising: receiving, from the network exposure function NEF, a second request for requesting provision of a specific quality of service QoS for a specific application function AF session; After receiving the second request, a second response rejecting the second request is sent to the NEF, wherein The second response indicates that a TSCTSF is not required for the AF session bound to the PDU session.

20. The method according to claim 19, wherein The second request is a Ntsctsf_QoSandTSCAssistance_Create request, and The second response is an Ntsctsf_QoSandTSCAssistance_Create response.

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

22. A carrier containing a computer program according to claim 21, wherein The carrier is one of an electronic signal, an optical signal, a radio signal and a computer-readable storage medium.

23. A policy control function (PCF) (108), the PCF being configured to: receiving (s302) a first request related to an application function AF session bound to a protocol data unit PDU session from a network opening function NEF (104) or a time sensitive communication and time synchronization function TSCTSF (106); After receiving the first request associated with the AF session bound to the PDU session, determining (s304) whether the PDU session is potentially used for time sensitive communication TSC; determining (s308) whether to accept or reject the first request based on determining whether the PDU session is potentially for TSC; as well as A first response is sent (s310) to the NEF or the TSCTSF, indicating whether the first request is accepted.

24. The PCF according to claim 23, wherein The PCF is configured to implement the method according to any one of claims 2-8.

25. A network open function (NEF) (104), wherein the NEF is configured to: sending (s402) a first request related to an application function AF session bound to a protocol data unit PDU session to a policy control function PCF (108); and After sending the first request, receiving (s404) a first response from the PCF indicating that the first request is rejected, wherein 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.

26. The NEF of claim 25, wherein: The NEF is configured to implement the method according to any one of claims 10-14.

27. A time sensitive communication and time synchronization function (TSCTSF) (106), the TSCTSF being configured to: sending (s502) a first request related to an application function AF session bound to a protocol data unit PDU session to a policy control function PCF (108); and After sending the first request, receiving (s504) a first response from the PCF indicating that the first request is rejected, wherein The first response indicates that a TSCTSF is not required for the AF session bound to the PDU session.

28. The TSCTSF according to claim 27, wherein The TSCTSF is configured to implement the method according to any one of claims 16-20.

29. An apparatus (600), comprising: Processing circuit (602); as well as A memory (641) containing instructions executable by the processing circuitry, whereby the apparatus is operable to implement a method according to any one of claims 1 to 20.

Images