Processing messages related to application functionality sessions 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] This 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 (registered trademark)) Technical Specification 23.502, version 17.7.9 (TS 23.502) discloses a process for setting up an Application Function (AF) session with required Quality of Service (QoS).

[0003] The process starts when the AF sends a creation request to the Network Exposure Function (NEF) to reserve service resources for the AF session. After receiving the creation request, the NEF decides whether to direct the signaling directly to the Policy Control Function (PCF) or via the Time Sensitive Communication and Time Synchronization Function (TSCTSF). This decision can be made based on a set of individual QoS parameters received from the AF or a set of (one or more) requested alternative QoS parameter sets.

[0004] After the AF session is established with the required QoS, the AF may wish 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 decides again whether to direct the signaling directly to the PCF or via the TSCTSF. This decision can be made based on a set of individual QoS parameters received from the AF or a set of (one or more) requested alternative QoS parameter sets.

[0005] To request specific QoS, a create request and / or update request may include any of the following: (1) QoS reference + (optional) traffic characteristics (i.e., flow direction, burst arrival time in 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 bitrate, requested maximum bitrate, maximum burst size) + (optional) traffic characteristics (i.e., flow direction, burst arrival time in UE (uplink) or UPF (downlink)), periodicity, time domain, lifespan).

[0006] 3GPP TS 23.503, version 17.6.0 (TS 23.503) indicates that create 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, AF cannot include individual QoS parameters in place of the QoS reference. In other words, AF cannot replace previously provided QoS in a create request with individual QoS parameters in an update request. In another example, if a create request includes (one or more) individual QoS parameters, AF cannot include a QoS reference in place of (one or more) individual QoS parameters.

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

[0008] Such indirect signaling (i.e., signaling via TSCTSF) may be required if specific QoS parameters are present in the AF request (e.g., the aforementioned creation request, update request, etc.). Examples of such QoS parameters include any time-sensitive communication assistance container (TSCAC) related parameters describing traffic characteristics (i.e., flow direction, burst arrival time at the UE (uplink) or UPF (downlink)), periodicity, time domain, and lifespan, and may be provided regardless of whether the creation and update requests include QoS reference parameters or individual QoS parameters. Another example is when the individual QoS parameter in the creation or update request includes the requested 5GS delay (e.g., it may include the UE device-side time-sensitive networking (TSN) translator (UE-DS-TT) residence time). In other cases, direct signaling may be performed between the NEF and PCF (without going through TSCTSF). [Overview of the Initiative]

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

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

[0011] If an update request is rejected, the AF must send another creation request (either directly or via TSCTSF), which results in excessive signaling and service interruptions. Therefore, the signaling path between the NEF and PCF must be determined during the creation of the AF session.

[0012] To address this problem, one embodiment of the present disclosure provides a method performed by a policy control function (PCF). The method includes receiving a first request from either a network exposure function (NEF) or a time-sensitive communications and time synchronization function (TSCTSF) relating to an application function (AF) session bound to a protocol data unit (PDU) session. After receiving the first request relating to the AF session bound to the PDU session, the method further includes determining whether the PDU session is suitable for time-sensitive communications (TSC). Based on the determination of whether the PDU session is suitable for TSC, the method further includes deciding whether to accept or reject the first request. The method further includes sending a first response to the NEF or TSCTSF indicating whether the first request is accepted or rejected.

[0013] In another embodiment, a method is provided that is performed by a Network Exposure Function (NEF). This method includes sending a first request to a Policy Control Function (PCF) relating to an Application Function (AF) session bound to a Protocol Data Unit (PDU) session. The method further includes, after sending the first request, receiving a first response from the PCF indicating that the first request has been rejected, and that 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.

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

[0015] In another embodiment, a computer program is provided which, when executed by a processing circuit (602), includes instructions that cause the processing circuit to perform one of the methods of the above embodiments.

[0016] In another embodiment, a carrier is provided which includes the computer program of the above embodiment, the carrier being one of an electrical signal, an optical signal, a radio signal, and a computer-readable storage medium.

[0017] In another embodiment, a policy control function (PCF) is provided. The PCF is configured to receive a first request relating to an application function (AF) session bound to a protocol data unit (PDU) session from either a network exposure function (NEF) or a time-sensitive communications and time synchronization function (TSCTSF), and, after receiving the first request relating to an AF session bound to a PDU session, to determine whether the PDU session is suitable for time-sensitive communications (TSC). Based on the determination of whether the PDU session is suitable for TSC, the PCF is configured to decide whether to accept or reject the first request, and to send a first response to the NEF or TSCTSF indicating whether the first request is accepted or rejected.

[0018] In another embodiment, a Network Exposure Function (NEF) is provided. The NEF is configured to send a first request relating to an Application Function (AF) session bound to a Protocol Data Unit (PDU) session to a Policy Control Function (PCF), and, after sending the first request, receive a first response from the PCF indicating that the first request has been 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 embodiment, a time-sensitive communications and time synchronization function (TSCTSF) is provided. The TSCTSF is configured to send a first request relating to an application function (AF) session bound to a protocol data unit (PDU) session to a policy control function, PCF, and, after sending the first request, receive a first response from the PCF indicating that the first request has been rejected, the first response indicating that the TSCTSF is not required for the AF session bound to the PDU session.

[0020] In another aspect, an apparatus is provided that includes a processing circuit and a memory, the memory including instructions executable by the processing circuit, whereby the apparatus is operable to perform any one of the methods of the above-described embodiments.

[0021] Some embodiments of the present disclosure enable determination of a signaling path for requests during the creation of an AF session, thereby minimizing the possibility that a legitimate request update from the AF is rejected.

Brief Description of the Drawings

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

[0023] [Figure 1] FIG. 1 shows a part of a system according to some embodiments.

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

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

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

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

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

[0029] [Figure 6] FIG. 6 shows an apparatus according to some embodiments.

Modes for Carrying Out the Invention

[0030] Figure 1 shows a portion of System 100 according to several embodiments. In System 100, user devices (UEs) 116 (e.g., mobile phones, computers, watches, tablets, vehicles, Internet of Things (IoT) devices, etc.) are connected to base station 114 via a wireless network provided by base station 114. Base station 114 is part of a 3GPP network system 112 comprising AF 102, NEF 104, TSCTSF 106, and PCF 108. Note that the number of each entity shown in Figure 1 (102, 104, 106, 108, 114, 116, etc.) is provided for the sake of simplicity and does not limit the embodiments of this disclosure in any way. Also note that Figure 1 shows only a portion of the 3GPP network system 112 (meaning that the 3GPP network system 112 may include additional entities). Network functions / nodes can be implemented as network elements on dedicated hardware, as software instances running on dedicated hardware, or as virtualized functions instantiated on a suitable platform, for example, on a cloud infrastructure.

[0031] AF 102 is a control plane function within the 5G core network. AF 102 can be configured to create AF sessions to provide application services (e.g., video streaming services) to UE 116. Figures 2A and 2B show a process 200 for creating an AF session according to several embodiments.

[0032] 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 for 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 the Nnef_AFsessionWithQoS Create request.

[0033] If AF request 202 is a request for the provision of a specific QoS, NEF 104 may perform step s202 upon receiving AF request 202. Step s202 includes step 202, which determines whether to allow the AF request. If NEF 104 decides not to allow AF request 202, NEF 104 may send an AF response 216 to AF 102 indicating that AF request 202 has been rejected. An example of an AF response 216 is the Nnef_AFsessionWithQoS Create response.

[0034] On the other hand, if NEF 104 decides to allow AF request 202, in step s204, NEF 104 may further decide whether to invoke TSCTSF 106 in signaling PCF 108, or to signal directly to PCF 108 (i.e., whether to send / receive (one or more) messages to / from PCF 108 without going through TSCTSF 106, or whether to send / receive (one or more) messages to / from PCF 108 via TSCTSF 106). This decision may be based on the presence of a specific QoS reference or (one or more) specific QoS individual parameters in AF request 202. Additionally or alternatively, the above decision may be based on an AF identifier or traffic characteristics that identify a particular AF session, or on AF-providing parameters.

[0035] As shown in Figure 2A, if NEF 104 decides to signal directly to PCF 108 without using TSCTSF 106, NEF 104 may send an NEF request 204 to 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 AF 102. 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 on which the NEF request 204 is made is for time-sensitive communications (TSC) (i.e., whether TSCTSF may be required in the signaling path between the NEF 104 and the PCF 108). One example of determining that a PDU session is for TSC is determining that the PDU session may be affected by the time synchronization service of the Precision Time Protocol (PTP). Determining whether a PDU session on which the NEF request 204 is made is for TSC may be based on one or more of the following: 5GS bridge information, data network name (DNN), network slice selection assistance information (S-NSSAI), application identifier (ID) that identifies the application, group ID that identifies the UE group, and / or local settings. For example, the mere presence of 5GS bridge information may indicate that the PDU session can 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 a PDU session is potentially for TSC. More detailed information on these parameters is provided in Section 5.2.27.3 of 3GPP TS 23.502, which is incorporated herein by reference.

[0037] It should be noted that PCF 108 knows whether NEF request 204 is initiated by NEF 104 or by TSCTSF 106. For example, NEF 104 and TSCTSF 106 may be set in the user-agent HTTP header in the request they send to PCF 108. In another example, each request may contain various informational elements or parameters that identify the sender of the request. Therefore, if PCF 108 determines that a PDU session bound to an AF session may be for TSC, PCF 108 may reject NEF request 204 because the request was initiated by NEF 104, which indicates that there is no TSCTSF for this signaling between NEF 104 and PCF 108.

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

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

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

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

[0042] If the NEF request 206 is a request to provide specific QoS for an AF session, then upon receiving the NEF request 206, the TSCTSF 106 may, in step s208, determine whether it has an AF session with the PCF for a 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 to provide specific QoS for an AF session. An example of a TSCTSF request 208 is the Npcf_PolicyAuthorization_Update request.

[0043] 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 find the PCF 108 and send a TSCTSF request 208. Here, examples of TSCTSF request 208 are an Npcf_PolicyAuthorization_Create request or an Npcf_PolicyAuthorization_Subscribe request.

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

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

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

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

[0048] Upon receiving a TSCTSF response 212, TSCTSF 106 may send an NEF response 214 to NEF 104. An example of an NEF response 214 is the 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 TSCTSF is not required in the signaling path between NEF 104 and PCF 108 for the PDU session. This information can be very useful to NEF 104, as if NEF 104 were to retry sending the request, it could attempt to send the request directly to PCF 108 (instead of sending it via TSCTSF 106).

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

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

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

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

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

[0054] In some embodiments, whether a PDU session is potentially for TSC is determined based on 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) that identifies a specific application, a specific group ID that identifies a user equipment (UE) group, or specific local settings 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 initiated by the NEF, determining whether the PDU session is available for the TSC, determining that the TSCTSF is of the required Network Function (NF) type for the request, and the first response being a rejection message rejecting the first request.

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

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

[0058] Figure 4 shows a process 400 performed by the NEF 104 in several embodiments. The process 400 may begin with step s402. Step s402 includes sending a first request to the PCF relating to an AF session bound to a PDU session. Step s404 includes receiving a first response from the PCF after sending the first request, indicating that the first request has been rejected, and 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 PDU sessions bound to an AF session, or a request to subscribe to the reporting of one or more events in the PCF.

[0060] In some embodiments, the first request is either 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 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) that identifies a specific application, a specific group ID that identifies a user equipment (UE) group, or specific local settings associated with a specific set of one or more rules and / or policies.

[0062] In some embodiments, the process 400 includes, after receiving a first response, sending a second request to the first TSCTSF requesting that a specific 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] Figure 5 shows a process 500 performed by the TSCTSF 106 in several embodiments. The process 500 may begin with step s502. Step s502 includes sending a first request to the PCF 108 relating to an AF session bound to a PDU session. Step s504 includes receiving a first response from the PCF after sending the first request, indicating that the first request has been rejected, and that the 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 the reporting of one or more events in the PCF.

[0066] In some embodiments, the first request is either 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 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) that identifies a specific application, a specific group ID that identifies a user equipment (UE) group, or specific local settings 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-published function (NEF) requesting the provision of a specific quality of service (QoS) for a particular application function (AF) session, and, after receiving the second request, sending a second response to the NEF rejecting the second request, the second response indicating that TSCTSF is not required for an AF session bound to a 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] Figure 6 is a block diagram of the device 600 according to several embodiments for implementing one or a combination thereof of AF 102, NEF 104, TSCTSF 106, and PCF 108. As shown in Figure 6, the device 600 includes a processing circuit (PC) 602 and a processing circuit (PC) 602 which may include one or more processors (P) 655 (e.g., general-purpose microprocessors and / or one or more other processors such as application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), etc., wherein the one or more processors may be jointly located in a single enclosure or a single data center, or may be geographically distributed (i.e., the device 600 may be a distributed computing device); and the device 600 transmits data to other nodes connected to network 110 (e.g., an Internet Protocol (IP) network). The PC may also include a network interface 648, which includes a transmitter (Tx) 645 and a receiver (Rx) 647 for enabling the reception of data from the other node, and to which the network interface 648 is connected (directly or indirectly) to the network (for example, the network interface 648 may be wirelessly connected to network 110, in which case the network interface 648 is connected to an antenna device); and a local storage unit (also known 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 in which the PC 602 has 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-temporary computer-readable medium such as a magnetic medium (e.g., a hard disk), an optical medium, or a memory device (e.g., random access memory, flash memory).In some embodiments, the CRI 644 of the computer program 643 is configured such that, when the CRI is executed by the PC 602, the device 600 performs the steps described herein (for example, the steps described herein with reference to a flowchart). In other embodiments, the device 600 may be configured to perform the steps described herein without requiring code. That is, for example, the PC 602 may consist of simply one or more ASICs. Thus, the functions of the embodiments described herein may be implemented in hardware and / or software.

[0071] Abbreviation TIFF0007897440000001.tif109148

[0072] Overview of the Embodiment

[0073] The above embodiments can be summarized as follows: -------------------------------------------------------------------------------- PCF may determine whether the Create request is not routed through TSCTSF, and if so, may return a special error cause to NEF, indicating that the signaling path for the entire AF session must pass through TSCTSF. According to TS 23.501, 6.2.29 TSCTSF, TSCTSF supports the detection of 5GS bridge information and the determination of requested PDBs (other QoS parameters whose priority level can be determined by TSCTSF). Therefore, if TSCTSF is required in the signaling path, PCF needs to notify TSCTSF of the 5GS bridge information. Furthermore, in order for the PCF to notify the TSCTSF, the PCF needs to know in advance whether the PDU session is for TSC communication (based on DNN / S-NSSAI and GPSI and / or SUPI / Internal Group ID or local settings). Considering the above, if PCF receives an Npcf_PolicyAuthorization_Create request to bind to a PDU session for TSC communication, but this request is not initiated by TSCTSF, PCF may reject the request and indicate that TSCTSF is required for the TSC PDU session; similarly, if PCF receives an Npcf_PolicyAuthorization_Creation request initiated by TSCTSF, but the PDU session is not for TSC communication, PCF may reject the request and indicate that TSCTSF is not required for the non-TSC PDU session. For Stage 3, the PCF can 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 (implying to TS 29.514), if User-Agent is TSCTSF and the PDU session is not a TSC PDU session, the PCF returns a 403 Forbidden with error cause (e.g.) NON_TSC_PDU_SESSION to TSCTSF. TSCTSF forwards this error to NEF (impact in TS 29.565). Then, in subsequent attempts to create an AF session, NEF does not select TSCTSF but selects PCF (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, PCF returns a 403 Forbidden with error cause (e.g.) TSC_PDU_SESSION to NEF (or AF). (Impact on TS 29.522) NEF then includes 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), wherein the method is Receiving a first request related to an AF (Application Function) session bound to a PDU (Protocol Data Unit) session from either NEF (Network Exposure Function) (104) or TSCTSF (Time Sensitive Communication and Time Synchronization Function) (106) (s302), After receiving the first request relating to the AF session bound to the PDU session, determine whether the PDU session is potentially for TSC (Time Sensitive Communication) (s304), Based on the determination of whether the PDU session may be for TSC, a decision is made to accept or reject the first request (s306), Sending a first response to the NEF or the TSCTSF indicating whether the first request is accepted (s308), A method that includes this.

[0075] A1a. The method of Embodiment A1, This includes determining whether the first request was transmitted by the NEF or initiated by the TSCTSF, A method wherein whether to accept or reject the first request is determined based on a determination of whether the first request was sent by the NEF or the TSCTSF.

[0076] A2. A method according to 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 the reporting of one or more events in the PCF.

[0077] A3. The method of Embodiment A2, wherein the first requirement is: Npcf_PolicyAuthorization_Create request, or Npcf_PolicyAuthorization_Subscribe request, A method that is one of the following.

[0078] A4. Any one of the embodiments A1 to A3, wherein the PDU session may be for TSC, 5GS bridge information, A specific DNN (Data Network Name), Specific S-NSSAI (Network Slice Selection Support Information), A specific application ID (identifier) ​​that identifies a particular application, A specific group ID that identifies the UE (User Equipment) group, or Specific local settings associated with a particular set of one or more rules and / or policies, A method determined based on one or more of the following.

[0079] A5. One of the methods of Embodiments A1a to A4, The method includes identifying that the first request was 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 that rejects the first request. A method by which the rejection message indicates that TSCTSF is required for the AF session bound to the PDU session.

[0080] A6. One of the methods of Embodiments A1a to A4, 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 available for the TSC. The first response is a rejection message that rejects the first request. A method by which the rejection message indicates that TSCTSF is not required for the AF session bound to the PDU session.

[0081] B1. A method (400) performed by NEF (Network Publish Function) (104), wherein the method is Sending 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) (s402), The process includes, after sending the first request, receiving a first response from the PCF indicating that the first request has been rejected (s404), The first response indicates that TSCTSF (Time Sensitive Communication and Time Synchronization Function) is required for the AF session bound to the PDU session, NEF.

[0082] B2. A method according to 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 the reporting of one or more events in the PCF.

[0083] B3. The method of Embodiment B2, wherein the first requirement is: Npcf_PolicyAuthorization_Create request, or Npcf_PolicyAuthorization_Subscribe request, A method that is one of the following.

[0084] B4. In any one of the embodiments B1 to B3, whether 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), Specific S-NSSAI (Network Slice Selection Support Information), A specific application ID (identifier) ​​that identifies a particular application, A specific group ID that identifies the UE (User Equipment) group, or Specific local settings associated with a particular set of one or more rules and / or policies, A method determined based on one or more of the following.

[0085] B5. One of the methods of Embodiments B1 to B4, After receiving the first response, a second request is sent to the first TSCTSF requesting that a specific QoS (Quality of Service) be provided for a specific AF (Application Function) session. After sending the second request, a second response is received from the first TSCTSF accepting the second request. Methods that include...

[0086] B6. The method of Embodiment B5, The second request mentioned above is the Ntsctsf_QoSandTSCAssistance_Create request, The second response described above is the Ntsctsf_QoSandTSCAssistance_Create response, by method.

[0087] C1. A method (500) performed by TSCTSF (Time Sensitive Communication and Time Synchronization Function) (106), wherein the method is Sending 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) (s502), The process includes, after sending the first request, receiving a first response from the PCF indicating that the first request has been rejected (s504), The first response indicates that 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 the reporting of one or more events in the PCF.

[0089] C3. The method of Embodiment C2, wherein the first requirement is: Npcf_PolicyAuthorization_Create request, or Npcf_PolicyAuthorization_Subscribe request, A method that is one of the following.

[0090] C4. In any one of the embodiments C1 to C3, whether 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), Specific S-NSSAI (Network Slice Selection Support Information), A specific application ID (identifier) ​​that identifies a particular application, A specific group ID that identifies the UE (User Equipment) group, or Specific local settings associated with a particular set of one or more rules and / or policies, A method determined based on one or more of the following.

[0091] C5. Any one of the embodiments C1 to C4, Receiving a second request from NEF (Network Publish Function) to request the provision of specific QoS (Quality of Service) for a specific AF (Application Function) session, The process includes, after receiving the second request, sending a second response to the NEF rejecting the second request, The second response is a method indicating that TSCTSF is not required for the AF session bound to the PDU session.

[0092] C6. The method of Embodiment C5, The second request mentioned above is the Ntsctsf_QoSandTSCAssistance_Create request, The second response described above is the Ntsctsf_QoSandTSCAssistance_Create response, by method.

[0093] D1. A computer program (600) which, when executed by a processing circuit (602), includes an instruction (644) that causes the processing circuit to execute any of the methods of embodiments A1 to C6.

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

[0095] E1. PCF (Policy Control Function) (108), wherein the PCF is Receiving a first request related to an AF (Application Function) session bound to a PDU (Protocol Data Unit) session from either NEF (Network Exposure Function) (104) or TSCTSF (Time Sensitive Communication and Time Synchronization Function) (106) (s302), After receiving the first request relating to the AF session bound to the PDU session, determine whether the PDU session is potentially for TSC (Time Sensitive Communication) (s304), Based on the determination of whether the PDU session may be for TSC, a decision is made to accept or reject the first request (s308), Sending a first response indicating whether the first request is accepted or not to the NEF or the TSCTSF (s310), A PCF configured to perform the following actions.

[0096] E2. A PCF of Embodiment E1, wherein the PCF is configured to perform any of the methods of Embodiments A2 to A6.

[0097] F1. NEF (Network Publish Function) (104), wherein the NEF is Sending 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) (s402), The system is configured to receive a first response from the PCF indicating that the first request has been rejected (s404) after sending the first request, The first response indicates that TSCTSF (Time Sensitive Communication and Time Synchronization Function) is required for the AF session bound to the PDU session, NEF.

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

[0099] G1. TSCTSF (Time-Sensitive Communication and Time Synchronization Function) (106), wherein the TSCTSF is Sending 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) (s502), The system is configured to receive a first response from the PCF indicating that the first request has been rejected (s504) after sending the first request, The first response indicates that TSCTSF is not required for the AF session bound to the PDU session.

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

[0101] H1. Apparatus (600), Processing circuit (602), A device comprising a memory (641), wherein the memory includes instructions executable by the processing circuit, thereby enabling the device to operate to perform any one of the embodiments A1 to C6.

[0102] conclusion

[0103] While various embodiments are described herein, it should be understood that they are presented merely as examples and not as limitations. Therefore, the scope and breadth of this disclosure should not be limited by any of the exemplary embodiments described above. Furthermore, unless otherwise suggested herein, or unless clearly contradicted by the context, any combination of the elements described above in all possible variations is encompassed by this disclosure.

[0104] As used herein, sending a message "to" or "toward" an intended recipient includes 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 includes 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, "one (a)" means "at least one" or "one or more".

[0105] In addition, the process described above and shown in the drawings is presented as a series of steps, but this is merely illustrative. Therefore, it is possible that some steps may be added, some steps may be omitted, the order of the steps may be rearranged, and some steps may be performed in parallel.

Claims

1. A method (300) performed by a PCF (Policy Control Function) (108), wherein the method is Receiving a first request related to an AF (Application Function) session bound to a PDU (Protocol Data Unit) session from either NEF (Network Public Function) (104) or TSCTSF (Time Sensitive Communication and Time Synchronization Function) (106) (s302), After receiving the first request relating to the AF session bound to the PDU session, determine whether the PDU session is suitable for TSC (Time Sensitive Communication) (s304), Based on the determination of whether the PDU session may be for TSC, a decision is made to accept or reject the first request (s306), Sending a first response indicating whether the first request is accepted to the NEF or the TSCTSF (s308), A method that includes this.

2. The method according to claim 1, This includes determining whether the first request was initiated by the NEF or the TSCTSF, A method wherein whether to accept or reject the first request is determined based on a determination of whether the first request was initiated by the NEF or the TSCTSF.

3. The method according to claim 1, 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 the reporting of one or more events in the PCF, in a method.

4. The method according to claim 3, wherein the first requirement is: Npcf_PolicyAuthorization_Create request, or Npcf_PolicyAuthorization_Subscribe request, A method that is one of the following.

5. The method according to claim 1, Whether the aforementioned PDU session is potentially for TSC is, 5GS bridge information, A specific DNN (Data Network Name), Specific S-NSSAI (Network Slice Selection Support Information), A specific application ID (identifier) ​​that identifies a particular application. A specific group ID that identifies the UE (User Equipment) group, or Specific local settings associated with a particular set of one or more rules and / or policies, A method determined based on one or more of the following.

6. The method according to claim 1, The method includes identifying that the first request was initiated by the NEF, Determining whether the PDU session is suitable for a TSC further includes determining that the TSCTSF is of the Network Function (NF) type required for the first request. The method wherein the first response is a rejection message that rejects the first request.

7. A method according to claim 6, wherein the rejection message indicates that the TSCTSF is required for the AF session bound to the PDU session.

8. The method according to claim 1, The method further includes identifying that the first request was sent by the TSCTSF and determining that the PDU session bound to the AF session is not available for the TSC. The first response is a rejection message that rejects the first request. A method for the rejection message to indicate that the TSCTSF is not required for the AF session bound to the PDU session.

9. A method (400) performed by the NEF (Network Publish Function) (104), wherein the method is Sending 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) (s402), The process includes, after sending the first request, receiving a first response from the PCF indicating that the first request has been rejected (s404), A method for indicating that the first response requires TSCTSF (Time Sensitive Communication and Time Synchronization Function) for the AF session bound to the PDU session.

10. The method according to claim 9, 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 the reporting of one or more events in the PCF, in a method.

11. The method according to claim 10, wherein the first requirement is: Npcf_PolicyAuthorization_Create request, or Npcf_PolicyAuthorization_Subscribe request, A method that is one of the following.

12. The method according to claim 9, Whether the T SCTSF 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), Specific S-NSSAI (Network Slice Selection Support Information), A specific application ID (identifier) ​​that identifies a particular application. A specific group ID that identifies the UE (User Equipment) group, or Specific local settings associated with a particular set of one or more rules and / or policies, A method determined based on one or more of the following.

13. The method according to claim 9, After receiving the first response, a second request is sent to the first TSCTSF requesting the provision of a specific QoS (Quality of Service) for a specific AF (Application Function) session. After sending the second request, a second response is received from the first TSCTSF accepting the second request. Methods that include...

14. The method according to claim 13, The second request is the Ntsctsf_QoSandTSCAssistance_Create request, The second response described above is the Ntsctsf_QoSandTSCAssistance_Create response, by method.

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

16. A method according to 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 the reporting of one or more events in the PCF.

17. The method according to claim 16, wherein the first requirement is: Npcf_PolicyAuthorization_Create request, or Npcf_PolicyAuthorization_Subscribe request, A method that is one of the following.

18. The method according to claim 15, Whether the 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), Specific S-NSSAI (Network Slice Selection Support Information), A specific application ID (identifier) ​​that identifies a particular application. A specific group ID that identifies the UE (User Equipment) group, or Specific local settings associated with a particular set of one or more rules and / or policies, A method determined based on one or more of the following.

19. The method according to claim 15, Receiving a second request from NEF (Network Publish Function) to request the provision of specific QoS (Quality of Service) for a specific AF (Application Function) session, The further includes, after receiving the second request, sending a second response rejecting the second request to the NEF, A method for indicating that the second response is not required for the AF session bound to the PDU session.

20. The method according to claim 19, The second request is the Ntsctsf_QoSandTSCAssistance_Create request, The second response described above is the Ntsctsf_QoSandTSCAssistance_Create response, by method.

21. A computer program (600) comprising an instruction (644) which, when executed by a processing circuit (602), causes the processing circuit to perform the method according to any one of claims 1 to 20.

22. A computer-readable storage medium containing the computer program described in claim 21.

23. PCF (Policy Control Function) (108), wherein the PCF is Receiving a first request related to an AF (Application Function) bound to a PDU (Protocol Data Unit) session from either NEF (Network Public Function) (104) or TSCTSF (Time Sensitive Communication and Time Synchronization Function) (106) (s302), After receiving the first request relating to the AF session bound to the PDU session, determine whether the PDU session is suitable for TSC (Time Sensitive Communication) (s304), Based on the determination of whether the PDU session may be for TSC, a decision is made to accept or reject the first request (s306), Sending a first response indicating whether the first request is accepted to the NEF or the TSCTSF (s308), A PCF configured to perform the following actions.

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

25. NEF (Network Publish Function) (104), wherein the NEF is Sending 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) (s402), The system is configured to receive a first response from the PCF indicating that the first request has been rejected (s404) after the first request has been sent, The first response indicates that TSCTSF (Time Sensitive Communication and Time Synchronization Function) is required for the AF session bound to the PDU session, NEF.

26. An NEF according to claim 25, wherein the NEF is configured to perform the method described in any one of claims 10 to 14.

27. TSCTSF (Time-Sensitive Communication and Time Synchronization Function) (106), wherein the TSCTSF is Sending 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) (s502), The system is configured to receive a first response from the PCF indicating that the first request has been rejected (s504) after the first request has been sent, The first response indicates that a TSCTSF is not required for the AF session bound to the PDU session.

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

29. Apparatus (600), Processing circuit (602), A device comprising a memory (641), wherein the memory includes instructions executable by the processing circuit, thereby enabling the device to operate to perform the method according to any one of claims 1 to 20.

Images