Method and apparatus for adjusting scheduling in wireless communication system

Abstract

The present disclosure relates to a 5th-Generation (5G) or 6th-Generation (6G) communication system for supporting higher data transmission rates. An application function (AF) entity in a wireless communication system is provided. The AF entity includes a transceiver and at least one processor. The at least one processor may be configured to: transmit traffic scheduling information to a network entity, the traffic scheduling information comprising at least one of a period range and a burst arrival time (BAT) range; receiving, from the network entity, information about at least one of the first period and the first BAT; and adjusting a schedule of the application based on information about at least one of the first period and the first BAT, where the information about at least one of the first period and the first BAT is determined based on at least one of the period range and the BAT range.

Description

Technical Field

[0001] The present disclosure relates to a method for adjusting the scheduling of applications based on feedback from a base station when performing low-latency communications. Background Art

[0002] 5G mobile communication technology defines a wide frequency band, making it possible to realize high transmission rates and new services, and it can be realized not only in the "below 6GHz" frequency band such as 3.5GHz, but also in the "above 6GHz" frequency band including 28GHz and 39GHz, which are called millimeter waves. In addition, in order to achieve a transmission rate 50 times faster than 5G mobile communication technology and an ultra-low latency of only one-tenth of that, the realization of 6G mobile communication technology in the terahertz frequency band (such as the 95GHz to 3THz frequency band) (called a super 5G system) has been considered.

[0003] In the early stages of 5G mobile communication technology development, in order to support services related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC) and massive machine type communications (mMTC) and meet their performance requirements, the standardization work that has been ongoing includes: beamforming and massive MIMO for alleviating radio wave path loss in millimeter waves and increasing radio wave transmission distance, support for multiple parameter sets (e.g., operating multiple subcarrier spacings) for efficient use of millimeter wave resources and dynamic operation of time slot formats, initial access technology for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods such as LDPC (low-density parity check) codes for large amounts of data transmission and polarization codes for highly reliable control information transmission, L2 preprocessing, and network slicing for providing dedicated networks for specific services.

[0004] Currently, discussions are underway on improvements and performance enhancements to initial 5G mobile communications technologies in view of the services they will support, and physical layer standardization has been initiated for technologies such as: V2X (vehicle-to-everything), which aims to assist autonomous vehicles in making driving decisions and improving user convenience based on information transmitted by the vehicle about its own location and status; New Radio Frequency Unlicensed (NR-U), which aims to enable system operations to comply with various regulatory requirements in unlicensed frequency bands; NR UE energy saving; Non-terrestrial Network (NTN), in which UEs communicate directly with satellites, to provide coverage in areas where communication with terrestrial networks is not possible, and positioning technology.

[0005] In addition, in terms of air interface architecture / protocol, standardization is also ongoing for the following technologies: Industrial Internet of Things (IIoT), supporting new services through interoperability and integration with other industries; IAB (Integrated Access and Backhaul), providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner; Mobility enhancement, including conditional switching and DAPS (Dual Active Protocol Stack) switching and two-step random access (NR's 2-step RACH) for simplifying the random access process. In terms of system architecture / services, standardization work is also ongoing, including 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) technology and software defined network (SDN) technology and mobile edge computing (MEC) for receiving services based on UE location.

[0006] As 5G mobile communication systems are commercialized, an exponentially increasing number of connected devices will be connected to the communication network, so it is expected that enhancements in the functions and performance of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is planned related to: effective support for extended reality (XR) such as AR (augmented reality), VR (virtual reality), MR (mixed reality), etc.; 5G performance improvement and complexity reduction by utilizing artificial intelligence (AI) and machine learning (ML); AI service support; Metaverse service support; and drone communication.

[0007] In addition, this development of 5G mobile communication systems will not only lay the foundation for the development of the following technologies: new waveforms required to provide coverage in the terahertz band of 6G mobile communication technology; multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas and massive antennas; metamaterial-based lenses and antennas for improving terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (orbital angular momentum) and RIS (reconfigurable smart surface), but will also lay the foundation for the development of the following technologies: full-duplex technology to improve the frequency efficiency of 6G mobile communication technology and improve system networks; AI-based communication technology that uses satellites and AI (artificial intelligence) to achieve system optimization and internalize end-to-end AI support functions from the design stage; and next-generation distributed computing technology that implements services with complexity that exceeds the limits of UE operating capabilities by utilizing ultra-high performance communication and computing resources.

[0008] The above information is provided as background information only to assist in understanding the present disclosure. No determination has been made and no statement has been made as to whether any of the above content may be used as prior art for the present disclosure. Summary of the invention

[0009] Technical Solution

[0010] When synchronization between a 3rd Generation Partnership Project (3GPP) communication network fifth generation system (5GS) and an external application (app) is supported so that NW-TT or DS-TT supports (precision) precision time protocol (PTP) messages, and a data stream generated by the external application at fixed intervals is transmitted through the communication network fifth generation system (5GS), it is necessary to consider the delay in the communication network, especially the scheduling characteristics in the radio access network (RAN) to meet the low latency requirement. However, there is currently no method for transmitting the scheduling characteristics of the external application to the RAN, nor is there a method for notifying the scheduling characteristics of the RAN to the external application. Therefore, a method for solving such problems is needed.

[0011] Aspects of the present disclosure are intended to at least address the above-mentioned problems and / or disadvantages and to provide at least the following advantages: Therefore, one aspect of the present disclosure is to provide a method for adjusting the scheduling of applications according to base station feedback when performing low-latency communication.

[0012] Additional aspects will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the presented embodiments.

[0013] According to one aspect of the present disclosure, an application function (AF) entity in a wireless communication system is provided. The AF entity includes a transceiver and at least one processor. The at least one processor can be configured to: send traffic scheduling information to a network entity, the traffic scheduling information including at least one of a cycle range and a burst arrival time (BAT) range; receive information about at least one of a first cycle and a first BAT from the network entity; and adjust the scheduling of the application based on the information about at least one of the first cycle and the first BAT, wherein the information about at least one of the first cycle and the first BAT is determined based on at least one of the cycle range or the BAT range.

[0014] According to another aspect of the present disclosure, a base station in a wireless communication system is provided. The base station includes a transceiver and at least one processor. The at least one processor can be configured to: receive traffic scheduling information from a network entity, the traffic scheduling information including at least one of a period range and a burst arrival time (BAT) range; determine information about at least one of a first period and a first burst arrival time (BAT) based on the traffic scheduling information; and send information about at least one of a first period and a first BAT to the network entity, wherein the information about at least one of the first period and the first BAT is used to adjust the scheduling of an application.

[0015] According to another aspect of the present disclosure, a method for an application function (AF) entity in a wireless communication system is provided. The method includes sending traffic scheduling information to a network entity, the traffic scheduling information including at least one of a cycle range and a burst arrival time (BAT) range; receiving information about at least one of a first cycle and a first BAT from the network entity; and adjusting the scheduling of the application based on the information about at least one of the first cycle and the first BAT, wherein the information about at least one of the first cycle and the first BAT is determined based on at least one of the cycle range or the BAT range.

[0016] According to another aspect of the present disclosure, a method for a base station in a wireless communication system is provided. The method includes receiving traffic scheduling information from a network entity, the traffic scheduling information including at least one of a period range and a burst arrival time (BAT) range; determining information about at least one of a first period and a first burst arrival time (BAT) based on the traffic scheduling information; and sending information about at least one of the first period and the first BAT to the network entity, wherein the information about at least one of the first period and the first BAT is used to adjust the scheduling of an application.

[0017] According to one aspect of the present disclosure, an application function (AF) entity in a wireless communication system is provided. The AF entity includes a transceiver and at least one processor. The at least one processor can be configured to send traffic scheduling information, receive information about a first period and a first burst arrival time (BAT), and adjust the scheduling of an application based on the first period and the first BAT.

[0018] According to another aspect of the present disclosure, a base station in a wireless communication system is provided. The base station includes a transceiver and at least one processor. The at least one processor can be configured to receive traffic scheduling information, identify scheduling characteristics, determine a first period and a first burst arrival time (BAT) based on the traffic scheduling information and the scheduling characteristics, and send the first period and the first BAT to a network entity.

[0019] RAN can consider optimal scheduling by a method for transmitting scheduling characteristics of external applications to RAN, and external applications can apply the characteristics of 5GS to adjust scheduling by a method for notifying external applications of scheduling characteristics of RAN. Therefore, low latency requirements can be met.

[0020] For those skilled in the art, other aspects, effects and salient features of the present disclosure will become apparent from the following detailed description, which is combined with the attached drawings. Figure 1 Various embodiments of the present disclosure are disclosed. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The above and other aspects, features and effects of certain embodiments of the present disclosure will become more apparent from the following description in conjunction with the accompanying drawings, in which:

[0022] Figure 1 An example is shown in which the scheduling characteristics of the external application and the scheduling characteristics of the 5GS RAN are different from each other according to an embodiment of the present disclosure;

[0023] Figure 2 A method for transmitting the scheduling characteristics of an external application to a RAN and an embodiment of notifying the scheduling characteristics of the RAN to the external application according to an embodiment of the present disclosure are shown;

[0024] Figure 3a and Figure 3b A first method for adjusting scheduling by an AF entity according to various embodiments of the present disclosure is shown;

[0025] Figure 4 According to an embodiment of the present disclosure, Figure 3a and Figure 3b Methods for adjusting scheduling when scheduling characteristics or information change after operation;

[0026] Figure 5a and Figure 5b A second method for adjusting scheduling by an AF entity according to various embodiments of the present disclosure is shown;

[0027] Figure 6 According to an embodiment of the present disclosure, Figure 5a and Figure 5b Methods for adjusting scheduling when scheduling characteristics or information change after operation;

[0028] Figure 7a and Figure 7b A third method of adjusting scheduling by an AF entity according to various embodiments of the present disclosure is shown;

[0029] Figure 8 According to an embodiment of the present disclosure, Figure 7a and Figure 7b Methods for adjusting scheduling when scheduling characteristics or information change after operation;

[0030] Figure 9a and Figure 9b A fourth method of adjusting scheduling by an AF entity according to various embodiments of the present disclosure is shown;

[0031] Fig.10 According to an embodiment of the present disclosure, Figure 9a and Figure 9b Methods for adjusting scheduling when scheduling characteristics or information change after operation;

[0032] Fig.11a and Fig.11b A fifth method of adjusting scheduling by an AF entity according to various embodiments of the present disclosure is shown;

[0033] Fig.12 According to an embodiment of the present disclosure, Fig.11a and Fig.11b Methods for adjusting scheduling when scheduling characteristics or information change after operation;

[0034] Fig.13 A schematic diagram showing the structure of a UE according to an embodiment of the present disclosure;

[0035] Fig.14 A schematic diagram showing the structure of a base station (RAN) according to an embodiment of the present disclosure;

[0036] Fig.15 A schematic diagram showing the structure of an application function (AF) entity according to an embodiment of the present disclosure;

[0037] Fig.16 A schematic diagram showing the structure of a network device (or communication network or network entity) according to an embodiment of the present disclosure is shown.

[0038] Throughout the drawings, note that like reference numbers are used to depict the same or similar elements, features, and structures. DETAILED DESCRIPTION

[0039] The following description in conjunction with the accompanying drawings is intended to assist in a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. Various specific details are included in the description to assist understanding, but these are considered to be exemplary only. Therefore, it will be appreciated by those of ordinary skill in the art that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and structures may be omitted for clarity and brevity.

[0040] The terms and words used in the following description and claims are not limited to their literal meanings, but are used by the inventors only to achieve a clear and consistent understanding of the present disclosure. Therefore, it should be clear to those skilled in the art that the following description of various embodiments of the present disclosure is for illustrative purposes only and is not intended to limit the present disclosure as defined by the attached claims and their equivalents.

[0041] It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0042] The terms used in this document to identify access nodes, terms representing network entities, terms representing messages, terms representing interfaces between network entities, and terms representing various identification information are all given as examples for ease of description. Therefore, the present disclosure is not limited by these terms, and these terms can be replaced by other terms representing objects with equivalent technical concepts.

[0043] For ease of description, this document uses the terms and names defined in the latest 3GPP 5G and NR standards in current communication standards. However, the present disclosure is not limited to these terms and names, and is also applicable to wireless communication networks that comply with other standards. In particular, the present disclosure can be applied to 3GPP GS / NR (fifth generation mobile communication standard).

[0044] When used in applications such as smart grids, accurate time synchronization between UEs is required. In this case, the time synchronization between UEs can use the Global Navigation Satellite System (GNSS) using satellite signals. However, if the GNSS is unavailable even for a moment, problems may arise because accurate time synchronization between UEs may not be maintained.

[0045] Figure 1 An example is shown in which the scheduling characteristics of the external application and the scheduling characteristics of the 5GS RAN are different from each other according to an embodiment of the present disclosure.

[0046] Reference Figure 1 , an external application 109 (application, app or application function AF) generates flow traffic at a time interval of a predetermined time of every 10 milliseconds (e.g., 100 milliseconds) (i.e., (100×K+10, where K is 0, 1, 2, ...) milliseconds) and sends the flow traffic through a communication network (e.g., a 3GPP network). In this case, the flow can be a downlink (DL) flow sent from an external server to UE 101 via a user plane function (UPF) 105 and a RAN (or next generation RAN (NG-RAN)) 102, or an uplink (UL) flow in which traffic generated by UE 101 is directed to an external server via NG-RAN 102 and UPF 105. In addition, a delay of less than 2 milliseconds should be guaranteed at the time of delivery. However, there is currently no method for transmitting traffic scheduling information to NG-RAN 102.

[0047] 5GS can guarantee a delay of 0.5 ms, which is the core network packet delay budget (CN-PDB) between UPF 105 and NG-RAN 102. In the scheduling of NG-RAN 102, a cycle is repeated every 3 ms in a time division duplex (TDD) manner, and a DL transmission frame starts every 3.2 ms (i.e. (3×L+3.2, where L is 0, 1, 2, 3, ...)) and lasts for a total of 6 frames, and a UL transmission frame starts every 5.2 ms (i.e. (3×M+5.2, where M is 0, 1, 2, ...)) and transmits a total of 3 frames. When DL traffic arrives at NG-RAN 102 at the beginning of the last DL frame in consecutive DL frames, the traffic may experience a scheduling delay of at least 4 frames (i.e. 1 DL frame, 3 UL frames, a total of 4 / 3 ms). Similarly, when UL traffic arrives at the NG-RAN 102 at the beginning of the last UL frame in the continuous UL frames, the traffic may experience a scheduling delay of at least 7 frames (1 UL frame, 6 DL frames, a total of 7 / 3 milliseconds). In other words, in a state where the scheduling characteristics of each other are not known, the time when the flow traffic generated by the external application 109 arrives at the NG-RAN 102 does not match the TDD cycle of the NG-RAN 102, so it is impossible to avoid the occurrence of a DL delay of 4 frames or a UL delay of 7 frames.

[0048] When the DL / UL traffic scheduling information of the external application 109 is shared with the NG-RAN 102, the NG-RAN 102 can provide UL / DL scheduling feedback to the external application 109 by reflecting the information such as the NG-RAN and the scheduling characteristics of the TDD cycle. For example, as the DL scheduling feedback information, 99 milliseconds are provided as the recommended period, and 102.7 milliseconds are provided as the recommended burst arrival time, that is, each (99×N+3.2-0.5 milliseconds, where N is 0, 1, 2, 3...). Therefore, when the external application server generates flow traffic and sends the flow traffic through the downlink, the flow traffic can be sent to the UE 101 with the minimum scheduling delay in consideration of the scheduling of the RAN. For example, as the UL scheduling feedback information, 99 milliseconds are provided as the recommended period, and 104.2 milliseconds are provided as the recommended burst arrival time, that is, each (99×N+5.2 milliseconds, where N is 0, 1, 2, 3...). Therefore, when UE 101 generates external application flow traffic and sends it via uplink, the external application flow traffic can be sent to the external application server with minimal scheduling delay considering the scheduling of RAN. The flow can also be sent via unified data repository (UDR) / unified data management (UDM) 104 alternatively. AF 109 and UE 101 are part of data network 110.

[0049] Figure 2A method of transmitting the scheduling characteristics of an external application to a RAN and a method of notifying the scheduling characteristics of the RAN to an external application according to an embodiment of the present disclosure are shown.

[0050] Reference Figure 2 , in order to transmit the scheduling characteristics of the external application to the RAN, the AF (i.e., the external application 109) transmits the UL / DL traffic scheduling information to the Time Sensitive Communication and Time Synchronization Function (TSCTSF) 108 directly or through the Network Exposure Function (NEF). The TSCTSF 108 determines whether the subscriber can process the information by referring to the information, and then sends the information to the Policy Control Function (PCF) 107. The PCF 107 identifies whether the Quality of Service (QoS) related requirements can be met, determines whether the related processing is feasible, and then sends the information to the Session Management Function (SMF) 106. The SMF 106 further processes the information and modifies it into information that can be transmitted to the NG-RAN 102, and then transmits the modified information to the Access and Mobility Management Function (AMF) 103. The AMF 103 transmits the modified information to the NG-RAN 102 for the corresponding flow of the corresponding UE.

[0051] UL / DL traffic scheduling information may include source / destination (src / dst) address / port, application identifier (ID), required bit rate, scheduling adaptation capability indication, initial period, period range (P-range), initial burst arrival time (BAT), BAT-range, and required delay. The scheduling adaptation capability indication is a parameter indicating whether the external application can adjust the scheduling. P-range is a period range and indicates the possible range in which the external application can adjust the period. BAT-range indicates the possible range in which the external application can adjust the burst arrival time.

[0052] In order to inform the external application of the scheduling characteristics of the RAN 102, the RAN 102 can identify that the external application can adjust the scheduling through the scheduling application capability indication. Alternatively, the RAN 102 can identify that the external application can adjust the scheduling by identifying whether the P-range or BAT-range is included in the information received from the network. The RAN 102 can generate or determine the recommended period considering the initial period and the P-range. In addition, the recommended BAT can be generated or determined considering the initial BAT and the BAT-range. The RAN 102 transmits the recommended period and the recommended BAT created in this way to the AMF 103. Alternatively, the RAN 102 can leave the role of creating the recommended period and the recommended BAT to other network functions (NFs), and only send the scheduling characteristics including the TDD period information to the AMF 103. The AMF 103 can send the information received from the RAN 102 to the SMF 106. The SMF 106 can perform necessary modification tasks on the information received from the AMF 103, such as converting between the master time referenced by the external application and the 5GS system. The SMF 106 may transmit the converted information to the PCF 107. The PCF 107 transmits the information received from the SMF 106 to the TSCTSF 108. The TSCTSF 108 may determine whether the proposed period satisfies the required initial period and P-range conditions, and whether the proposed BAT satisfies the required initial BAT and BAT-range conditions. According to an embodiment, when the information transmitted from the RAN 102 simply includes scheduling characteristics such as TDD period information, the TSCTSF 108 may generate or determine a proposed period that matches the required initial period and P-range conditions, and may generate or determine a proposed BAT that matches the required initial BAT and BAT-range conditions. Thereafter, the TSCTSF 108 may transmit the identified information or the directly generated information to the NEF 108. The NEF returns the information to the AF (i.e., the external application 109). The AF (i.e., the external application 109) may adjust the application scheduling based on this scheduling information. In other words, for DL ​​scheduling, the flow generation and transmission time of the server are adjusted, and for UL scheduling, the flow generation and transmission time of the UE are adjusted.

[0053] There are many variations in the way of creating the suggested cycle and the suggested BAT, but for example, they are generated as follows. However, they are not limited to the following method.

[0054] - Recommended cycle = (K × TDD_cycle), k = 0, 1, 2, ... This value minimizes the absolute value | recommended cycle - initial cycle | and the recommended cycle is within the P-Range range

[0055] - Recommended BAT = (M × TDD_cycle) + first UL frame range, M = 0, 1, 2, ..., this value minimizes the absolute value | recommended BAT - initial BAT |, and the recommended BAT is within the B-Range

[0056] - Recommended BAT = (N×TDD_cycle) + first DL frame range - CN_PDB, M = 0, 1, 2, ..., this value minimizes the absolute value | recommended BAT - initial BAT |, and the recommended BAT is within the B-Range

[0057] - Information used to convey the scheduling characteristics of the RAN (e.g., DL / UL scheduling feedback information) may include src / dst address / port, application ID, required bit rate, recommended period, recommended BAT, and required delay.

[0058] 3A and 3B illustrate a first method of adjusting scheduling by an AF according to various embodiments of the present disclosure.

[0059] 3, in operation S305, UE 301 may perform registration on 5GS. In this case, UE 301 may be in a state of subscribing to a low-latency service and monitoring a service.

[0060] In operation S310, UE 301 may set up a packet data unit (PDU) session. In this case, time synchronization with an external application server may be maintained through a device-side TSN converter (DS-TT) located in UE 301 and a network-side TSN converter (NW-TT) located in NW-TT / UPF 303. In this case, the master clock referenced by the external application may be exactly the same as or different from the master clock referenced by 5GS. When the master clock referenced by the external application is different from the master clock referenced by 5GS, NW-TT may identify and update the difference and send it to SMF 305. In addition, when interacting with external application functions, it may be bound to TSCTSF 308, which is responsible for time synchronization related functions.

[0061] In operation S315, AF 309 may transmit a time-sensitive communication (TSC) / QoS request to TSC TSF 308 directly or through NEF 308, or through UDR / UDM 307. The request may include traffic scheduling information (e.g., DL / UL traffic scheduling information). The traffic scheduling information may include GPSI, source / destination (src / dst) address / port, application ID, required bit rate, scheduling adaptation capability indication, initial period, P-range, initial BAT, BAT-range, UL / DL, and at least one of the required delays. The Global Public Subscription Identifier (GPSI) indicates a UE identifier that can be referenced outside the 5GS and may include an IP address or an Ethernet address. The scheduling adaptation capability indication indicates whether an external application can adjust the scheduling. The period range (P-range) indicates the range of periods that can be adjusted by external applications. BAT-range indicates the range of burst arrival times that can be adjusted by external applications.

[0062] In operation S320, the TSCTSF or NEF 308 may discover the UE 301 and discover the PDU session. In this case, the GPSI and src / dst address / port may be utilized. In this case, the TSCTSF 308 may determine whether the information can be processed by referring to the subscriber information.

[0063] In operation S320a, the TSC TSF or the NEF 308 may transmit a TSC / QoS response message to the AF 309. The response message may include a transaction ID and DL / UL traffic scheduling information.

[0064] In operation S325, the TSCTSF 308 may transmit the information received from the AF in operation S315 to the PCF 306 bound to the UE and PDU session discovered in operation S320. The transmission request may include traffic scheduling information, UEid, DNN, S-NSSAI, PDU session ID, src / dst address / port, required bit rate, scheduling adaptation capability indication, initial period, P-range, initial BAT, BAT-range, UL / DL, and required delay.

[0065] In operation S330, the PCF 306 may determine whether the QoS related requirements can be met and whether the QoS related requirements can be processed. A guaranteed flow bit rate (GFBR) that can achieve the required bit rate, a core network packet delay budget (CN-PDB) that can achieve the required bit rate, and an access network packet delay budget (AN-PDB) that can achieve the required bit rate may be mapped to the QoS information.

[0066] In operation S335, the PCF 306 may transmit the information identified in operation S330 to the SMF 305. The information may include at least one of UE id, DNN, S-NSSAI, PDU session ID, flow descriptor, QoS information (GFBR, CN-PDB, AN-PDB), scheduling adaptation capability indication, initial period, P-range, initial BAT, BAT-range, and UL / DL received from the TSC TSF 308. The flow descriptor may include src / dst address / port and application ID.

[0067] In operation S340, the SMF 305 may generate time synchronization assistance information (e.g., TSC assistance information (TSCAI)). In this case, when the master clock referenced by the external application is different from the master clock referenced by the 5GS, the NW-TT / UPF 303 may identify the difference and update using the difference, and send the difference to the SMF 305. The SMF 305 may convert the information specified based on the external time into the 5GS time by reflecting the received difference information. In this case, the TSCAI may include a scheduling adaptation capability indication, an initial period, a P-range, an initial BAT, a BAT-range, and an UL / DL.

[0068] In operation S345, the SMF 305 may transmit the generated information to the AMF 304 through a request message (e.g., a QoS setup request message), and the AMF 304 may transmit the information to the NG-RAN 302. The transmitted information may include at least one of a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, AN-PDB), and TSCAI (scheduling adaptation capability indication, initial cycle, P-range, initial BAT, BAT-range, and UL / DL).

[0069] In operation S350, the NG-RAN 302 may identify scheduling characteristic information such as a TDD cycle, and identify that an external application can adjust scheduling based on the received scheduling adaptation capability indication. Alternatively, the NG-RAN 302 may determine that the external application can adjust scheduling by identifying whether the received information includes a P-range or a BAT-range. The NG-RAN 302 may determine or generate a recommended cycle by considering at least one of the initial cycle and the P-range. In addition, the recommended BAT may be determined or generated by considering at least one of the initial BAT and the BAT-range. In addition, when the scheduling information is updated due to the configuration of a scheduling characteristic such as a TDD cycle, or the scheduling information of the newly connected cell such as a TDD cycle is updated due to the switching of the UE, the NG-RAN 302 may determine the updated recommended cycle and the recommended BAT and may subscribe so as to transmit the determined recommended cycle and the recommended BAT to the SMF 305.

[0070] In operation S355, the NG-RAN 302 may send the determined or generated recommended cycle and recommended BAT as a response message (e.g., QoS setup response message) to the SMF 305 through the AMF 304. In this case, the response message may include a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, AN-PDB), and TSCAI (recommended cycle, recommended BAT, and UL / DL).

[0071] In operation S360, if necessary, SMF 305 may time convert the recommended period and the recommended BAT. SMF 305 may convert the 5GS time reference to the external time reference in the opposite manner to operation S340.

[0072] In operation S365, the SMF 305 may transmit the updated information to the TSCTSF 308 through the PCF 306. A response message (e.g., a policy update response) for transmitting the updated information may include a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, AN-PDB), a recommended period, a recommended BAT, and UL / DL.

[0073] In operation S370, the TSCTSF 308 may determine whether the proposed cycle meets the required initial cycle and P-range conditions, and whether the proposed BAT meets the required initial BAT and BAT-range conditions. It may also be verified again whether other information in the DL / UL scheduling feedback information that has been sent also meets the conditions.

[0074] In operation S375, the TSCTSF 308 may send a response to the TSC / QoS request received in operation S325 to the AF 309 directly or through the NEF. In this case, if the TSCTSF 308 has sent a response to the TSC / QoS request in operation 320a, the TSCTSF 308 may send information to the AF 309 in the format of a TSC / QoS notification. The message sent to the AF 309 may include GPSI, transaction ID, and DL / UL scheduling feedback information. The DL / UL scheduling feedback information may include src / dst address / port, application ID, required bit rate, recommended period, recommended BAT, and required delay.

[0075] In operation S380, the AF 309 may adjust application scheduling based on the information received from the TSCTSF 308. In other words, for DL ​​scheduling, the flow generation and transmission time of the server may be adjusted, and for UL scheduling, the flow generation and transmission time of the UE may be adjusted.

[0076] Figure 4 A method for adjusting scheduling when scheduling characteristics or information changes after the operations of FIG. 3A and FIG. 3B according to an embodiment of the present disclosure is shown.

[0077] Reference Figure 4 , after performing operation S380 in operation S305 in Figures 3A and 3B, in operation S405, when it is identified that a scheduling characteristic such as a TDD cycle is reconfigured or scheduling information such as a TDD cycle of a newly connected cell is updated due to UE switching, the NG-RAN 302 may update the recommended cycle and the recommended BAT based on the updated scheduling characteristic or information.

[0078] In operation S410, the NG-RAN 302 may transmit the updated recommended period and recommended BAT to the SMF 305 through the AMF 304. In this case, the transmitted information may include a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, and AN-PDB), and TSCAI (recommended period, recommended BAT, and UL / DL).

[0079] In operation S415, SMF 305 may perform time conversion on the recommended period and the recommended BAT as needed. The time conversion method may be similar to the method performed in operation S360 in FIG. 3B.

[0080] In operation S420, the SMF 305 may transmit the updated period and BAT information to the TSCTSF 308 through the PCF 306. In this case, the transmitted information may include at least one of a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, AN-PDB), a recommended period, a recommended BAT, and UL / DL.

[0081] In operation S425, the TSCTSF 308 may identify whether the updated recommended period meets the required initial period and P-range conditions, and whether the recommended BAT meets the required initial BAT and BAT-range conditions. It may also verify again whether other information in the DL / UL scheduling feedback information meets the conditions.

[0082] In operation S430, the TSCTSF 308 may transmit information to the AF 309 directly or through the NEF, or directly in the format of TSC / QoS notification. In this case, the transmitted message may include at least one of GPSI, transaction ID, and DL / UL scheduling feedback information. The DL / UL scheduling feedback information may include at least one of src / dst address / port, application ID, required bit rate, recommended period, recommended BAT, and required delay.

[0083] In operation S435, the AF 309 may readjust the application scheduling based on the received update information. In other words, for DL ​​scheduling, the flow generation and transmission time of the server may be adjusted, and for UL scheduling, the flow generation and transmission time of the UE may be adjusted.

[0084] 5A and 5B illustrate a second method of adjusting scheduling by an AF according to various embodiments of the present disclosure.

[0085] 5A and 5B, in operation S505, UE 501 may perform registration on 5GS. In this case, UE 501 may be in a state of subscribing to a low-latency service and monitoring a service.

[0086] In operation S510, UE 501 may set up a PDU session. In this case, time synchronization with an external application server may be maintained through a device-side TSN converter (DS-TT) located in UE 501 and a network-side TSN converter (NW-TT) located in UPF 503. In this case, the master clock referenced by the external application may be exactly the same as or different from the master clock referenced by 5GS. When the master clock referenced by the external application is different from the master clock referenced by 5GS, NW-TT may identify the difference and use the difference to update, and send the difference to SMF 505. In addition, when interacting with external application functions, it may be bound to TSCTSF 508 responsible for time synchronization related functions.

[0087] In operation S515, the AF 509 may transmit a time-sensitive communication (TSC) / QoS request to the TSC TSF 508 directly or through the NEF 508, or through the UDR / UDM 507. The request may include traffic scheduling information (e.g., DL / UL traffic scheduling information). The traffic scheduling information may include GPSI, source / destination (src / dst) address / port, application ID, required bit rate, scheduling adaptation capability indication, initial period, P-range, initial BAT, BAT-range, UL / DL, and at least one of the required delays. The Global Public Subscription Identifier (GPSI) indicates a UE identifier that can be referenced outside the 5GS and may include an IP address or an Ethernet address. The scheduling adaptation capability indication indicates whether an external application can adjust the scheduling. The period range (P-range) indicates the range of periods that can be adjusted by external applications. BAT-range indicates the range of burst arrival times that can be adjusted by external applications.

[0088] In operation S520, the TSCTSF or NEF 508 may discover the UE 501 and discover the PDU session. In this case, the GPSI and src / dst address / port may be utilized. In this case, the TSCTSF 508 may determine whether the information can be processed by referring to the subscriber information.

[0089] In operation S520a, the TSC TSF or the NEF 508 may transmit a TSC / QoS response message to the AF 509. The response message may include a transaction ID and DL / UL traffic scheduling information.

[0090] In operation S525, the TSCTSF 508 may transmit the information received from the AF in operation S515 to the PCF 506 bound to the UE and PDU session discovered in operation S520. The transmission request may include traffic scheduling information, UEid, DNN, S-NSSAI, PDU session ID, src / dst address / port, required bit rate, scheduling adaptation capability indication, initial period, P-range, initial BAT, BAT-range, UL / DL, and required delay.

[0091] In operation S530, the PCF 506 may determine whether the QoS related requirements can be met and whether the QoS related requirements can be processed. A guaranteed flow bit rate (GFBR) that can achieve the required bit rate, a core network packet delay budget (CN-PDB) that can achieve the required bit rate, and an access network packet delay budget (AN-PDB) that can achieve the required bit rate may be mapped to the QoS information.

[0092] In operation S535, the PCF 506 may transmit the information identified in operation S530 to the SMF 505. The information may include at least one of UE id, DNN, S-NSSAI, PDU session ID, flow descriptor, QoS information (GFBR, CN-PDB, AN-PDB), scheduling adaptation capability indication, initial period, P-range, initial BAT, BAT-range, and UL / DL received from the TSC TSF 508. The flow descriptor may include src / dst address / port and application ID.

[0093] In operation S540, SMF 505 may generate time synchronization assistance information (e.g., TSC assistance information (TSCAI)). In this case, when the master clock referenced by the external application is different from the master clock referenced by the 5GS, NW-TT503 may identify the difference and update using the difference, and send the difference to SMF 505. SMF 505 may convert the information specified based on the external time into 5GS time by reflecting the received difference information. In this case, TSCAI may include scheduling adaptation capability indication, initial cycle, P-range, initial BAT, BAT-range, and UL / DL.

[0094] In operation S545, the SMF 505 may transmit the generated and converted information to the AMF 504 through a request message (e.g., a QoS setup request message), and the AMF 504 may transmit the information to the NG-RAN 502. The transmitted information may include at least one of a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, AN-PDB), and TSCAI (scheduling adaptation capability indication, initial cycle, P-range, initial BAT, BAT-range, and UL / DL).

[0095] In operation S550, the NG-RAN 502 may identify scheduling characteristic information such as a TDD cycle, and identify that an external application can adjust scheduling based on the received scheduling adaptation capability indication. Alternatively, the NG-RAN 502 may determine that the external application can adjust scheduling by identifying whether the received information includes a P-range or a BAT-range. The NG-RAN 502 may send only scheduling characteristics such as TDD cycle information to the AMF 504. In addition, when the scheduling information is updated due to configuration of a scheduling characteristic such as a TDD cycle, or when the scheduling information such as a TDD cycle of a newly connected cell is updated due to handover of the UE, the NG-RAN 502 may determine the updated recommended cycle and recommended BAT and subscribe so that the updated scheduling information is transmitted to the SMF 505.

[0096] In operation S555, the NG-RAN 502 may transmit scheduling characteristics such as TDD cycle information to the SMF 505 through the AMF 504. The AMF 504 may transmit the information received from the NG-RAN 502 as a response message (e.g., a QoS setup response message) to the SMF 505. In this case, the response message may include a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, and AN-PDB), and TDD cycle information.

[0097] In operation S560, if necessary, the SMF 505 may time convert the TDD cycle information. The SMF 505 may convert the 5GS time reference to the external time reference in the opposite manner to that in operation S540.

[0098] In operation S565, SMF 505 may transmit the converted information to TSCTSF 508 through PCF 506. A response message (e.g., policy update response) for transmitting updated information may include PDU session ID, flow descriptor, QoS information (GFBR, CN-PDB, AN-PDB), and TDD cycle information.

[0099] In operation S570, the TSCTSF 508 may generate a recommended cycle that matches the required initial cycle and P-range conditions, and generate a recommended BAT that matches the required initial BAT and BAT-range conditions. In addition, the TSCTSF 508 may determine whether the generated recommended cycle satisfies the required initial cycle and P-range conditions, and whether the generated recommended BAT satisfies the required initial BAT and BAT-range conditions. It may also be verified again whether other information in the DL / UL scheduling feedback information that has been sent also satisfies the conditions.

[0100] In operation S575, the TSCTSF 508 may send a response to the TSC / QoS request received in operation S515 to the AF 509 directly or through the NEF. In this case, if the TSCTSF 508 has sent a response to the TSC / QoS request in operation 520a, the TSCTSF 308 may send information to the AF 509 in the format of a TSC / QoS notification. The message sent to the AF 509 may include GPSI, transaction ID, and DL / UL scheduling feedback information. The DL / UL scheduling feedback information may include src / dst address / port, application ID, required bit rate, recommended period, recommended BAT, and required delay.

[0101] In operation S575a, the TSC TSF 508 may send an update request (e.g., a TSCAI update request) including the recommended period and the recommended BAT to the SMF 505 through the PCF 506. The SMF 505 may generate a TSCAI including the received information and send it to the NG-RAN 502 through the AMF 504. The NG-RAN 502 may use the information to schedule the corresponding flow.

[0102] In operation S580, the AF 509 may adjust the application scheduling based on the information received from the TSCTSF 508. In other words, for DL ​​scheduling, the flow generation and transmission time of the server may be adjusted, and for UL scheduling, the flow generation and transmission time of the UE may be adjusted.

[0103] Figure 6 A method of adjusting scheduling when scheduling characteristics or information changes after the operations of FIG. 5A and FIG. 5B according to an embodiment of the present disclosure is shown.

[0104] Reference Figure 6, after executing S580 in operation S505 of Figures 5A and 5B, in operation S605, when it is identified that the scheduling characteristics such as the TDD cycle are reconfigured or the scheduling information such as the TDD cycle of the newly connected cell is updated due to UE switching, the NG-RAN 502 can transmit the updated scheduling information (or characteristics) to the AMF 504.

[0105] In operation S610, the NG-RAN 502 may transmit scheduling information (or characteristics) such as updated TDD cycle information to the SMF 505 through the AMF 504. In this case, the transmitted information may include a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, and AN-PDB), and TDD cycle information.

[0106] In operation S615, if necessary, the SMF 505 may time-convert the scheduling information (or characteristics) such as the TDD cycle. The time conversion method may be similar to the method performed in operation S560 of FIG. 5B.

[0107] In operation S620, the SMF 505 may transmit the updated scheduling information to the TSCTSF 508 through the PCF 506. In this case, the transmitted information may include a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, and AN-PDB), and TDD cycle information.

[0108] In operation S570, the TSCTSF 508 may generate or update a recommended period that matches the required initial period and P-range conditions based on the updated scheduling information, and generate or update a recommended BAT that matches the required initial BAT and BAT-range conditions. In addition, the TSCTSF 508 may identify whether the updated recommended period satisfies the required initial period and P-range conditions, and whether the updated recommended BAT satisfies the required initial BAT and BAT-range conditions. It may also be verified again whether other information in the DL / UL scheduling feedback information satisfies the conditions.

[0109] In operation S630, the TSCTSF 508 may send a response to the TSC / QoS request to the AF 509 directly or through the NEF. In this case, if the TSCTSF 508 has sent a response to the TSC / QoS request in operation 520a, the TSCTSF 308 may send information to the AF 509 in the format of a TSC / QoS notification. In this case, the transmitted message may include GPSI, transaction ID, and DL / UL scheduling feedback information. The DL / UL scheduling feedback information may include src / dst address / port, application ID, required bit rate, recommended period, recommended BAT, and required delay.

[0110] In operation S630a, the TSC TSF 508 may send a request including the generated recommended period and recommended BAT to the SMF 505 through the PCF 506. The SMF 505 may regenerate a TSCAI including the information and send the TSCAI to the NG-RAN 502 through the AMF 504. The NG-RAN 502 may use the information to schedule the corresponding flow.

[0111] In operation S635, the AF 509 may readjust the application scheduling based on the received information. In other words, for DL ​​scheduling, the flow generation and transmission time of the server may be adjusted, and for UL scheduling, the flow generation and transmission time of the UE may be adjusted.

[0112] 7A and 7B illustrate a third method of adjusting scheduling by an AF according to various embodiments of the present disclosure.

[0113] 7A and 7B, in operation S705, UE 701 may perform registration on 5GS. In this case, UE 701 may be in a state of subscribing to a low-latency service and monitoring a service.

[0114] In operation S710, UE 701 may set up a PDU session. In this case, time synchronization with an external application server may be maintained through a device-side TSN converter (DS-TT) located in UE 701 and a network-side TSN converter (NW-TT) located in UPF 703. In this case, the master clock referenced by the external application may be exactly the same as or different from the master clock referenced by 5GS. When the master clock referenced by the external application is different from the master clock referenced by 5GS, NW-TT may identify the difference and use the difference to update, and send the difference to SMF 705. In addition, when interacting with external application functions, it may be bound to TSCTSF 708, which is responsible for time synchronization related functions.

[0115] In operation S715, AF 709 may transmit a time-sensitive communication (TSC) / QoS request to TSC TSF 708 directly or through NEF 708, or through UDR / UDM 707. The request may include traffic scheduling information (e.g., DL / UL traffic scheduling information). The traffic scheduling information may include GPSI, source / destination (src / dst) address / port, application ID, required bit rate, scheduling adaptation capability indication, initial period, P-range, initial BAT, BAT-range, UL / DL, and at least one of the required delays. The Global Public Subscription Identifier (GPSI) indicates a UE identifier that can be referenced outside the 5GS, which may include an IP address or an Ethernet address. The scheduling adaptation capability indication indicates whether an external application can adjust the scheduling. The period range (P-range) indicates the range of periods that can be adjusted by external applications. BAT-range indicates the range of burst arrival times that can be adjusted by external applications.

[0116] In operation S720, the TSCTSF or NEF 708 may discover the UE 701 and discover the PDU session. In this case, the GPSI and src / dst address / port may be utilized. In this case, the TSCTSF 708 may determine whether the information can be processed by referring to the subscriber information.

[0117] In operation S720a, the TSC TSF or the NEF 708 may transmit a TSC / QoS response message to the AF 709. The response message may include a transaction ID and DL / UL traffic scheduling information.

[0118] In operation S725, the TSCTSF 708 may transmit the information received from the AF in operation S715 to the PCF 706 bound to the UE and PDU session discovered in operation S720. The transmission request may include traffic scheduling information, UEid, DNN, S-NSSAI, PDU session ID, src / dst address / port, required bit rate, scheduling adaptation capability indication, initial period, P-range, initial BAT, BAT-range, UL / DL, and required delay.

[0119] In operation S730, the PCF 706 may determine whether the QoS related requirements can be met and whether the QoS related requirements can be processed. A guaranteed flow bit rate (GFBR) that can achieve the required bit rate, a core network packet delay budget (CN-PDB) that can achieve the required bit rate, and an access network packet delay budget (AN-PDB) that can achieve the required bit rate may be mapped to the QoS information.

[0120] In operation S735, the PCF 706 may transmit the information identified in operation S730 to the SMF 705. The information may include at least one of UE id, DNN, S-NSSAI, PDU session ID, flow descriptor, QoS information (GFBR, CN-PDB, AN-PDB), scheduling adaptation capability indication, initial period, P-range, initial BAT, BAT-range, and UL / DL received from the TSC TSF 708. The flow descriptor may include src / dst address / port and application ID.

[0121] In operation S740, SMF 705 may generate time synchronization assistance information (e.g., TSC assistance information (TSCAI)). In this case, when the master clock referenced by the external application is different from the master clock referenced by the 5GS, NW-TT 703 may identify the difference and update using the difference, and send the difference to SMF 705. SMF 705 may convert the information specified based on the external time into 5GS time by reflecting the received difference information. In this case, TSCAI may include scheduling adaptation capability indication, initial cycle, P-range, initial BAT, BAT-range, and UL / DL.

[0122] In operation S745, the SMF 705 may transmit the generated and converted information to the AMF 704 through a request message (e.g., a QoS setup request message), and the AMF 704 may transmit the information to the NG-RAN 702. The transmitted information may include at least one of a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, AN-PDB), and TSCAI (scheduling adaptation capability indication, initial cycle, P-range, initial BAT, BAT-range, and UL / DL).

[0123] In operation S750, the NG-RAN 702 may identify scheduling characteristic information such as a TDD cycle, and based on the received scheduling adaptation capability indication, identify that the external application can adjust the scheduling. Alternatively, the NG-RAN 702 may identify that the external application can adjust the scheduling by identifying whether the received information includes a P-range or a BAT-range. The NG-RAN 702 may send only scheduling characteristics such as TDD cycle information to the AMF 704. In addition, when the scheduling information is updated due to configuration of a scheduling characteristic such as a TDD cycle, or when the scheduling information such as a TDD cycle of a newly connected cell is updated due to handover of the UE, the NG-RAN 702 may determine the updated recommended cycle and recommended BAT and subscribe so that the updated scheduling information is transmitted to the SMF 705.

[0124] In operation S755, the NG-RAN 702 may transmit scheduling characteristics such as TDD cycle information to the SMF 705 through the AMF 704. The AMF 704 may transmit the information received from the NG-RAN 702 as a response message (e.g., a QoS setup response message) to the SMF 705. In this case, the response message may include a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, and AN-PDB), and TDD cycle information.

[0125] In operation S760, SMF 705 may generate a recommended period that matches the required initial period and P-range conditions, and generate a recommended BAT that matches the required initial BAT and BAT-range conditions by referring to the received scheduling information such as the TDD period. SMF 705 may perform necessary modification tasks on the information received from AMF 704, such as converting between the master time referenced by the external application and the 5GS system. In other words, SMF 705 may perform time conversion on the recommended period and the recommended BAT as needed.

[0126] In operation S765, the SMF 705 may transmit the converted information to the TSCTSF 708 through the PCF 706. In this case, the transmitted message may include a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, and AN-PDB), a recommended cycle, a recommended BAT, and UL / DL.

[0127] In operation S765a, the SMF 705 may generate a TSCAI including the generated recommended period and the recommended BAT, and transmit the TSCAI to the NG-RAN 702 through the AMF 704. The NG-RAN 702 may use the information to schedule the corresponding flow.

[0128] In operation S770, the TSCTSF 708 may determine whether the received recommended period meets the required initial period and P-range conditions, and whether the recommended BAT meets the required initial BAT and BAT-range conditions. It may also verify again whether other information in the DL / UL scheduling feedback information meets the conditions.

[0129] In operation S775, the TSCTSF 708 may send a response to the TSC / QoS request received in operation S715 to the AF 709 directly or through the NEF. In this case, if the TSCTSF 708 has sent a response to the TSC / QoS request in operation 720a, the TSCTSF 308 may send information to the AF 709 in the format of a TSC / QoS notification. The message sent to the AF 709 may include GPSI, transaction ID, and DL / UL scheduling feedback information. The DL / UL scheduling feedback information may include src / dst address / port, application ID, required bit rate, recommended period, recommended BAT, and required delay.

[0130] In operation S780, the AF 709 may adjust application scheduling based on the information received from the TSCTSF 708. In other words, for DL ​​scheduling, the flow generation and transmission time of the server may be adjusted, and for UL scheduling, the flow generation and transmission time of the UE may be adjusted.

[0131] Figure 8 A method of adjusting scheduling when scheduling characteristics or information changes after the operations of FIG. 7A and FIG. 7B according to an embodiment of the present disclosure is shown.

[0132] Reference Figure 8 , after executing S780 in operation S705 of Figures 7A and 7B, in operation S805, when it is identified that the scheduling characteristics such as the TDD cycle are reconfigured or the scheduling information such as the TDD cycle of the newly connected cell is updated due to UE switching, the NG-RAN 702 can transmit the updated scheduling information (or characteristics) to the AMF 704.

[0133] In operation S810, the NG-RAN 702 may transmit scheduling information (or characteristics) such as updated TDD cycle information to the SMF 705 through the AMF 704. In this case, the transmitted information may include a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, and AN-PDB), and TDD cycle information.

[0134] In operation S815, SMF 705 can generate or update a recommended cycle that matches the required initial cycle and P-range conditions based on the updated scheduling information (or characteristics), and generate or update a recommended BAT that matches the required initial BAT and BAT-range conditions. In addition, SMF 705 can perform time conversion on the updated recommended cycle and recommended BAT as needed.

[0135] In operation S820, the SMF 705 may transmit the updated recommended period and the recommended BAT to the TSCTSF 708 through the PCF 706. In this case, the transmitted information may include a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, and AN-PDB), an updated recommended period, an updated recommended BAT, and UL / DL.

[0136] In operation S820a, the SMF 705 may generate a TSCAI including an updated recommended period and an updated recommended BAT, and transmit the TSCAI to the NG-RAN 702 through the AMF 704. The NG-RAN 702 may use the information to schedule the corresponding flow.

[0137] In operation S825, the TSCTSF 708 may identify whether the updated recommended period meets the required initial period and P-range conditions, and whether the updated recommended BAT meets the required initial BAT and BAT-range conditions. It may also verify again whether other information in the DL / UL scheduling feedback information meets the conditions.

[0138] In operation S830, the TSCTSF 708 may send a response to the TSC / QoS request to the AF 709 directly or through the NEF. In this case, if the TSCTSF 708 has sent a response to the TSC / QoS request in operation 720a, the TSCTSF 308 may send information to the AF 709 in the format of a TSC / QoS notification. In this case, the transmitted message may include GPSI, transaction ID, and DL / UL scheduling feedback information. The DL / UL scheduling feedback information may include src / dst address / port, application ID, required bit rate, recommended period, recommended BAT, and required delay.

[0139] In operation S835, the AF 709 may readjust the application scheduling based on the received information. In other words, for DL ​​scheduling, the flow generation and transmission time of the server may be adjusted, and for UL scheduling, the flow generation and transmission time of the UE may be adjusted.

[0140] 9A and 9B illustrate a fourth method of adjusting scheduling by an AF according to various embodiments of the present disclosure.

[0141] 9A and 9B, in operation S905, UE 901 may perform registration on 5GS. In this case, UE 901 may be in a state of subscribing to a low-latency service and monitoring a service.

[0142] In operation S910, UE 901 may set up a PDU session. In this case, time synchronization with an external application server may be maintained through a device-side TSN converter (DS-TT) located in UE 901 and a network-side TSN converter (NW-TT) located in UPF 903. In this case, the master clock referenced by the external application may be exactly the same as or different from the master clock referenced by 5GS. When the master clock referenced by the external application is different from the master clock referenced by 5GS, NW-TT may identify the difference and use the difference to update, and send the difference to SMF 905. In addition, when interacting with external application functions, it may be bound to TSCTSF 908, which is responsible for time synchronization related functions.

[0143] In operation S915, the AF 909 may transmit a time-sensitive communication type (TSC) / QoS request to the TSC TSF 908 directly or through the NEF 908, or through the UDR / UDM 907. The request may include traffic scheduling information (e.g., DL / UL traffic scheduling information). The traffic scheduling information may include GPSI, source / destination (src / dst) address / port, application ID, required bit rate, scheduling adaptation capability indication, initial period, P-range, initial BAT, BAT-range, UL / DL, and at least one of the required delays. The Global Public Subscription Identifier (GPSI) indicates a UE identifier that can be referenced outside the 5GS, which may include an IP address or an Ethernet address. The scheduling adaptation capability indication indicates whether an external application can adjust the scheduling. The period range (P-range) indicates the range of periods that can be adjusted by external applications. BAT-range indicates the range of burst arrival times that can be adjusted by external applications.

[0144] In operation S920, the TSCTSF or NEF 908 may discover the UE 901 and discover the PDU session. In this case, the GPSI and src / dst address / port may be utilized. In this case, the TSCTSF 908 may determine whether the information can be processed by referring to the subscriber information.

[0145] In operation S920a, the TSC TSF or the NEF 908 may transmit a TSC / QoS response message to the AF 909. The response message may include a transaction ID and DL / UL traffic scheduling information.

[0146] In operation S925, the TSCTSF 908 may transmit the information received from the AF in operation S915 to the PCF 906 bound to the UE and PDU session discovered in operation S920. The transmission request may include traffic scheduling information, UEid, DNN, S-NSSAI, PDU session ID, src / dst address / port, required bit rate, scheduling adaptation capability indication, initial period, P-range, initial BAT, BAT-range, UL / DL, and required delay.

[0147] In operation S930, the PCF 906 may determine whether the QoS related requirements can be met and whether the QoS related requirements can be processed. A guaranteed flow bit rate (GFBR) that can achieve the required bit rate, a core network packet delay budget (CN-PDB) that can achieve the required bit rate, and an access network packet delay budget (AN-PDB) that can achieve the required bit rate may be mapped to the QoS information.

[0148] In operation S935, the PCF 906 may transmit the information identified in operation S930 to the SMF 905. The information may include at least one of UE id, DNN, S-NSSAI, PDU session ID, flow descriptor, QoS information (GFBR, CN-PDB, AN-PDB), scheduling adaptation capability indication, initial cycle, P-range, initial BAT, BAT-range, and UL / DL received from the TSC TSF 908. The flow descriptor may include src / dst address / port and application ID.

[0149] In operation S940, the SMF 905 may generate time synchronization assistance information (e.g., TSC assistance information (TSCAI)). In this case, when the master clock referenced by the external application is different from the master clock referenced by the 5GS, the NW-TT 903 may identify the difference and update it using the difference and send it to the SMF 905. The SMF 905 may convert the information specified based on the external time into 5GS time by reflecting the received difference information. In this case, the TSCAI may include a scheduling adaptation capability indication, an initial cycle, a P-range, an initial BAT, a BAT-range, and an UL / DL.

[0150] In operation S945, the SMF 905 may transmit the generated and converted information to the AMF 904 through a request message (e.g., a QoS setup request message), and the AMF 904 may transmit the information to the NG-RAN 902. The transmitted information may include at least one of a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, AN-PDB), and TSCAI (scheduling adaptation capability indication, initial cycle, P-range, initial BAT, BAT-range, and UL / DL).

[0151] In operation S950, the NG-RAN 902 may identify scheduling characteristic information such as a TDD cycle, and based on the received scheduling adaptation capability indication, identify that the external application can adjust the scheduling. Alternatively, the NG-RAN 902 may determine that the external application can adjust the scheduling by identifying whether the received information includes a P-range or a BAT-range. The NG-RAN 902 may send only scheduling characteristics such as TDD cycle information to the AMF 904. In addition, when the scheduling information is updated due to the configuration of a scheduling characteristic such as a TDD cycle, or the scheduling information such as a TDD cycle of a newly connected cell is updated due to the handover of the UE, the NG-RAN 902 may determine the updated recommended cycle and recommended BAT and subscribe so that the updated scheduling information is transmitted to the SMF 905.

[0152] In operation S955, the NG-RAN 902 may transmit scheduling characteristics such as TDD cycle information to the SMF 905 through the AMF 904. The AMF 904 may transmit the information received from the NG-RAN 902 as a response message (e.g., a QoS setup response message) to the SMF 905. In this case, the response message may include a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, and AN-PDB), and TDD cycle information.

[0153] In operation S960, SMF 905 may perform necessary modification tasks on the information received from AMF 904, such as converting between the master time referenced by the external application and the 5GS system.

[0154] In operation S965, SMF 905 may transmit the updated information to PCF 906.

[0155] In operation S970, the PCF 906 may generate a suggested cycle by referring to scheduling information such as a TDD cycle and considering the initial cycle and P-range. In addition, the PCF 906 may generate a suggested BAT by referring to scheduling information such as a TDD cycle and considering the initial BAT and BAT-range.

[0156] In operation S975, the PCF 906 may transmit information to the TSCTSF 908. In this case, the transmitted information may include PDU session ID, flow descriptor, QoS information (GFBR, CN-PDB, and AN-PDB), recommended cycle, recommended BAT, and UL / DL.

[0157] In operation S975a, the PCF 906 may transmit the recommended period and the recommended BAT to the SMF 905, and the SMF 905 may generate a TSCAI including the recommended period and the recommended BAT, and transmit the TSCAI to the NG-RAN 902 through the AMF 904. The NG-RAN 902 may use the information to schedule the corresponding flow.

[0158] In operation S980, the TSCTSF 908 may determine whether the received recommended period meets the required initial period and P-range conditions, and whether the recommended BAT meets the required initial BAT and BAT-range conditions. It may also verify again whether other information in the DL / UL scheduling feedback information meets the conditions.

[0159] In operation S985, the TSCTSF 908 may send a response to the TSC / QoS request received in operation S915 to the AF 909 directly or through the NEF. In this case, if the TSCTSF 908 has sent a response to the TSC / QoS request in operation 920a, the TSCTSF 308 may send information to the AF 909 in the format of a TSC / QoS notification. The message sent to the AF 909 may include GPSI, transaction ID, and DL / UL scheduling feedback information. The DL / UL scheduling feedback information may include src / dst address / port, application ID, required bit rate, recommended period, recommended BAT, and required delay.

[0160] In operation S990, the AF 909 may adjust application scheduling based on the information received from the TSCTSF 908. In other words, for DL ​​scheduling, the flow generation and transmission time of the server may be adjusted, and for UL scheduling, the flow generation and transmission time of the UE may be adjusted.

[0161] Fig.10A method of adjusting scheduling when scheduling characteristics or information changes after the operations of FIG. 9A and FIG. 9B according to an embodiment of the present disclosure is shown.

[0162] Reference Fig.10 , after executing S990 in operation S905 of Figures 9A and 9B, in operation S1005, when it is identified that the scheduling characteristics such as the TDD cycle are reconfigured or the scheduling information such as the TDD cycle of the newly connected cell is updated due to UE switching, the NG-RAN 902 can transmit the updated scheduling information (or characteristics) to the AMF 904.

[0163] In operation S1010, the NG-RAN 902 may transmit scheduling information (or characteristics) such as updated TDD cycle information to the SMF 905 through the AMF 904. In this case, the transmitted information may include a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, and AN-PDB), and TDD cycle information.

[0164] In operation S1015, SMF 905 may perform necessary modification tasks on the information received from AMF 904, such as converting between the master time referenced by the external application and 5GS. In other words, if necessary, SMF 905 may perform time conversion on scheduling information such as TDD cycles.

[0165] In operation S1020, SMF 905 may transmit updated scheduling information to PCF 906.

[0166] In operation S1025, the PCF 906 may generate or update a recommended cycle matching the required initial cycle and the P-range condition, and generate or update a recommended BAT matching the required initial BAT and the BAT-range.

[0167] In operation S1030, the PCF 906 may transmit the updated recommended cycle and recommended BAT to the TSCTSF 908. In this case, the transmitted information may include PDU session ID, flow descriptor, QoS information (GFBR, CN-PDB, and AN-PDB), recommended cycle, recommended BAT, and UL / DL.

[0168] In operation S1030a, the PCF 906 may transmit the updated recommended period and recommended BAT to the SMF 905, and the SMF 905 may generate a TSCAI including the recommended period and recommended BAT, and transmit the TSCAI to the NG-RAN 902 through the AMF 904. The NG-RAN 902 may schedule the corresponding flow using the received information.

[0169] In operation S1035, the TSCTSF 908 may identify whether the updated recommended period meets the required initial period and P-range conditions, and whether the updated recommended BAT meets the required initial BAT and BAT-range conditions. It may also verify again whether other information in the DL / UL scheduling feedback information meets the conditions.

[0170] In operation S1040, the TSCTSF 908 may send a response to the TSC / QoS request to the AF 909 directly or through the NEF. In this case, if the TSCTSF 908 has sent a response to the TSC / QoS request in operation 920a, the TSCTSF 308 may send information to the AF 909 in the format of a TSC / QoS notification. In this case, the transmitted message may include GPSI, transaction ID, and DL / UL scheduling feedback information. The DL / UL scheduling feedback information may include src / dst address / port, application ID, required bit rate, recommended period, recommended BAT, and required delay.

[0171] In operation S1045, the AF 909 may readjust the application scheduling based on the received information. In other words, for DL ​​scheduling, the flow generation and transmission time of the server may be adjusted, and for UL scheduling, the flow generation and transmission time of the UE may be adjusted.

[0172] 11A and 11B illustrate a fifth method of adjusting scheduling by an AF according to various embodiments of the present disclosure.

[0173] 11A and 11B, in operation S1105, UE 1101 may perform registration on 5GS. In this case, UE 1101 may be in a state of subscribing to a low-latency service and monitoring a service.

[0174] In operation S1110, UE 1101 may set up a PDU session. In this case, time synchronization with an external application server may be maintained through a device-side TSN converter (DS-TT) located in UE 1101 and a network-side TSN converter (NW-TT) located in UPF 1103. In this case, the master clock referenced by the external application may be exactly the same as or different from the master clock referenced by 5GS. When the master clock referenced by the external application is different from the master clock referenced by 5GS, NW-TT may identify the difference and use the difference to update, and send the difference to SMF 1105. In addition, when interacting with external application functions, it may be bound to TSCTSF 1108 responsible for time synchronization related functions.

[0175] In operation S1115, AF 1109 may transmit a time-sensitive communication (TSC) / QoS request to TSC TSF 1108 directly or through NEF 1108, or through UDR / UDM 1107. The request may include traffic scheduling information (e.g., DL / UL traffic scheduling information). The traffic scheduling information may include GPSI, source / destination (src / dst) address / port, application ID, required bit rate, scheduling adaptation capability indication, initial period, P-range, initial BAT, BAT-range, UL / DL, and at least one of the required delays. The Global Public Subscription Identifier (GPSI) indicates a UE identifier that can be referenced outside the 5GS, which may include an IP address or an Ethernet address. The scheduling adaptation capability indication indicates whether an external application can adjust the scheduling. The period range (P-range) indicates the range of periods that can be adjusted by external applications. BAT-range indicates the range of burst arrival times that can be adjusted by external applications.

[0176] In operation S1120, the TSCTSF or NEF 1108 may discover the UE 1101 and discover the PDU session. In this case, the GPSI and src / dst address / port may be utilized. In this case, the TSCTSF 1108 may determine whether the information can be processed by referring to the subscriber information.

[0177] In operation S1120a, the TSC TSF or the NEF 1108 may transmit a TSC / QoS response message to the AF 1109. The response message may include a transaction ID and DL / UL traffic scheduling information.

[0178] In operation S1125, the TSCTSF 1108 may transmit the information received from the AF in operation S1115 to the PCF 1106 bound to the UE and PDU session found in operation S1120. The transmission request may include traffic scheduling information, UEid, DNN, S-NSSAI, PDU session ID, src / dst address / port, required bit rate, scheduling adaptation capability indication, initial period, P-range, initial BAT, BAT-range, UL / DL, and required delay.

[0179] In operation S1130, the PCF 1106 may determine whether the QoS-related requirements can be met and whether the QoS-related requirements can be processed. A guaranteed flow bit rate (GFBR) that can achieve the required bit rate, a core network packet delay budget (CN-PDB) that can achieve the required bit rate, and an access network packet delay budget (AN-PDB) that can achieve the required bit rate may be mapped to the QoS information.

[0180] In operation S1135, the PCF 1106 may transmit the information identified in operation S1130 to the SMF 1105. The information may include at least one of UE id, DNN, S-NSSAI, PDU session ID, flow descriptor, QoS information (GFBR, CN-PDB, AN-PDB), scheduling adaptation capability indication, initial period, P-range, initial BAT, BAT-range, and UL / DL received from the TSC TSF 1108. The flow descriptor may include src / dst address / port and application ID.

[0181] In operation S1140, SMF 1105 may generate time synchronization assistance information (e.g., TSC assistance information (TSCAI)). In this case, when the master clock referenced by the external application is different from the master clock referenced by the 5GS, NW-TT 1103 may identify the difference and update it using the difference and send it to SMF 1105. SMF 1105 may convert the information specified based on the external time into 5GS time by reflecting the received difference information. In this case, TSCAI may include scheduling adaptation capability indication, initial cycle, P-range, initial BAT, BAT-range, and UL / DL.

[0182] In operation S1145, the SMF 1105 may transmit the generated and converted information to the AMF 1104 through a request message (e.g., a QoS setup request message), and the AMF 1104 may transmit the information to the NG-RAN 1102. The transmitted information may include at least one of a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, AN-PDB), and TSCAI (scheduling adaptation capability indication, initial cycle, P-range, initial BAT, BAT-range, and UL / DL).

[0183] In operation S1150, the NG-RAN 1102 may identify scheduling characteristic information such as a TDD cycle, and based on the received scheduling adaptation capability indication, identify that the external application can adjust the scheduling. Alternatively, the NG-RAN 1102 may determine that the external application can adjust the scheduling by identifying whether the received information includes a P-range or a BAT-range. The NG-RAN 1102 may send only scheduling characteristics such as TDD cycle information to the AMF 1104. In addition, when the scheduling information is updated due to the configuration of a scheduling characteristic such as a TDD cycle or the scheduling information such as a TDD cycle of a newly connected cell is updated due to the handover of the UE, the NG-RAN 1102 may determine the updated recommended cycle and recommended BAT and subscribe so that the updated scheduling information is transmitted to the SMF 1105.

[0184] In operation S1155, the NG-RAN 1102 may transmit scheduling characteristics such as TDD cycle information to the SMF 1105 through the AMF 1104. The AMF 1104 may transmit the information received from the NG-RAN 1102 as a response message (e.g., a QoS setup response message) to the SMF 1105. In this case, the response message may include a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, and AN-PDB), and TDD cycle information.

[0185] In operation S1160, the SMF 1105 may perform time conversion on scheduling information such as a TDD cycle, if necessary.

[0186] In operation S1165, the SMF 1105 may transmit the updated information to the TSC TSF 1108 through the PCF 1106. In this case, the transmitted information may include a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, and AN-PDB), and TDD cycle information.

[0187] In operation S1170, the TSCTSF 1108 may identify the received TDD cycle information.

[0188] In operation S1175, the TSCTSF 1108 may send a response to the TSC / QoS request received in operation S1115 to the AF 1109 directly or through the NEF. In this case, if the TSCTSF 1108 has sent a response to the TSC / QoS request in operation 1120a, the TSCTSF 308 may send information to the AF 909 in the format of a TSC / QoS notification. The message sent to the AF 1109 may include GPSI, transaction ID, and DL / UL scheduling feedback information. The DL / UL scheduling feedback information may include src / dst address / port, application ID, required bit rate, recommended period, recommended BAT, and required delay.

[0189] In operation S1180, the AF 1109 may generate a recommended cycle based on the received scheduling information such as the TDD cycle and taking into account the initial cycle and the P-range. In addition, the AF 1109 may generate a recommended BAT based on the received scheduling information such as the TDD cycle and taking into account the initial BAT and the BAT-range. Thereafter, the AF 1109 may adjust the application scheduling based on the generated information. In other words, for DL ​​scheduling, the flow generation and transmission time of the server may be adjusted, and for UL scheduling, the flow generation and transmission time of the UE may be adjusted.

[0190] In operation S1185, the AF 1109 may update the TSCAI up to the NG-RAN 1102 to include the generated proposed cycle and proposed BAT by using the flow of operation S1115 to operation S1145.

[0191] Fig.12 A method of adjusting scheduling when scheduling characteristics or information changes after the operations of FIG. 11A and FIG. 11B according to an embodiment of the present disclosure is shown.

[0192] Reference Fig.12 , after executing S1185 in operation S1105 of Figure 11A and Figure 11B, in operation S1205, when it is identified that the scheduling characteristics such as the TDD cycle are reconfigured or the scheduling information such as the TDD cycle of the newly connected cell is updated due to UE switching, the NG-RAN 1102 can transmit the updated scheduling information (or characteristics) to the AMF 1104.

[0193] In operation S1210, the NG-RAN 1102 may transmit scheduling information (or characteristics) such as updated TDD cycle information to the SMF 1105 through the AMF 1104. In this case, the transmitted information may include a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, and AN-PDB), and TDD cycle information.

[0194] In operation S1215, SMF 1105 may perform necessary modification tasks on the information received from AMF 1104, such as converting between the master time referenced by the external application and the 5GS system. In other words, if necessary, SMF 1105 may perform time conversion on scheduling information such as TDD cycles.

[0195] In operation S1220, the SMF 1105 transmits the updated scheduling information to the TSC TSF 1108 through the PCF 1106. In this case, the transmitted information may include a PDU session ID, a flow descriptor, QoS information (GFBR, CN-PDB, and AN-PDB), and TDD cycle information.

[0196] In operation S1225, the TSCTSF 1108 may identify the received scheduling information such as a TDD cycle.

[0197] In operation S1230, the TSCTSF 1108 may send a response to the TSC / QoS request directly or through the NEF to the AF 1109. In this case, if the TSCTSF 1108 has sent a response to the TSC / QoS request in operation 1120a, the TSCTSF 1108 may send information in the format of a TSC / QoS notification to the AF 1109. In this case, the transmitted information may include GPSI, transaction ID, and TDD cycle information.

[0198] In operation S1235, AF 1109 may generate or update a recommended cycle based on the received scheduling information (e.g., TDD cycle) and taking into account the initial cycle and P-range. In addition, a recommended BAT may be generated or updated based on the scheduling information and taking into account the initial BAT and BAT-range. Thereafter, AF 1109 may adjust the application scheduling based on the generated or updated information. In other words, for DL ​​scheduling, the flow generation and transmission time of the server may be adjusted, and for UL scheduling, the flow generation and transmission time of the UE may be adjusted.

[0199] In operation S1240, the AF 1109 may update the TSCAI to the NG-RAN 1102 to include the generated proposed cycle and proposed BAT by using the process of operation S1115 to operation S1145.

[0200] Fig.13 A schematic diagram showing the structure of a UE according to an embodiment of the present disclosure is shown.

[0201] Reference Fig.13 According to an embodiment, the UE may include at least one controller (or processor) 1310 and a transceiver 1320 including a receiver and a transmitter. The UE may include a memory (not shown). The transceiver 1320 and the memory may be connected to the at least one controller 1310 and operate under the control of the at least one controller 1310.

[0202] At least one controller 1310 can control a series of processes to perform the combined Figure 1 , Figure 2 , Figure 3A, Figure 3B, Figure 4 , Figure 5A, Figure 5B, Figure 6 , Figure 7A, Figure 7B, Figure 8 , Figure 9A, Figure 9B, Fig.10 , FIG. 11A, FIG. 11B and Fig.12 The UE operation described in the embodiment of the present invention. The transceiver 1320 can transmit and receive signals with the base station 1400, the application function entity 1500 and the network entity 1600. These signals may include control information and data.

[0203] Fig.14 A schematic diagram showing the structure of a base station (RAN) according to an embodiment of the present disclosure is shown.

[0204] Reference Fig.14 According to an embodiment, the base station may include at least one controller (or processor) 1410 and a transceiver 1420 including a receiver and a transmitter. The base station may include a memory (not shown). The transceiver 1420 and the memory may be connected to the at least one controller 1410 and operate under the control of the at least one controller 1410.

[0205] At least one controller 1410 can control the Figure 1 , Figure 2 , Figure 3A, Figure 3B, Figure 4 , Figure 5A, Figure 5B, Figure 6 , Figure 7A, Figure 7B, Figure 8 , Figure 9A, Figure 9B, Fig.10 , FIG. 11A, FIG. 11B and Fig.12The operations of the base station ((NG-)RAN) to be performed are described. The transceiver 1420 can perform signal transmission and reception with the UE 1300 , the application function entity 1500 , and the network entity 1600 .

[0206] Fig.15 A schematic diagram showing the structure of an application function (AF) entity according to an embodiment of the present disclosure is shown. The application function (AF) entity may be a concept including an external application or an application server.

[0207] Reference Fig.15 According to an embodiment, the application function may include at least one controller (e.g., processor) 1510 and a transceiver 1520 including a receiver and a transmitter. The application function may include a memory (not shown). The transceiver 1520 and the memory may be connected to the at least one controller 1510 and operate under the control of the at least one controller 1510.

[0208] At least one controller 1510 can control the Figure 1 , Figure 2 , Figure 3A, Figure 3B, Figure 4 , Figure 5A, Figure 5B, Figure 6 , Figure 7A, Figure 7B, Figure 8 , Figure 9A, Figure 9B, Fig.10 , FIG. 11A, FIG. 11B and Fig.12 The described operation of the application function (AF) to be performed. The transceiver 1520 can perform signal transmission and reception with the UE 1300, the base station 1400, and the network entity 1600.

[0209] Fig.16 A schematic diagram showing the structure of a network device (or communication network or network entity) according to an embodiment of the present disclosure is shown.

[0210] Reference Fig.16 According to an embodiment, the network entity may include at least one controller (e.g., processor) 1610 and a transceiver 1620 including a receiver and a transmitter. The network device may include a memory (not shown). The transceiver 1620 and the memory may be connected to at least one controller 1610 and operate under the control of at least one controller 1610.

[0211] At least one controller 1610 can control a series of processes to perform the combined Figure 1 , Figure 2 , Figure 3A, Figure 3B, Figure 4 , Figure 5A, Figure 5B, Figure 6 , Figure 7A, Figure 7B, Figure 8 , Figure 9A, Figure 9B, Fig.10 , FIG. 11A, FIG. 11B and Fig.12The operation of the network device (or communication network, 5G core network or network entity) described in the embodiments of the present invention. The transceiver 1620 can send and receive signals with the UE 1300, the base station 1400 and the application function entity 1500. These signals may include control messages and data information.

[0212] The network entity 1600 may include all devices corresponding to network functional entities according to the present disclosure, such as TSC TSF, NEF, NF, unified data repository (UDR) / unified data management (UDM), AMF, UPF, SMF and PCF, and these network functional entities may be configured independently.

[0213] The methods according to the embodiments described in the specification or claims of this disclosure may be implemented by hardware, software, or a combination of hardware and software.

[0214] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. One or more programs contain instructions that cause the electronic device to execute the methods described in the embodiments of the disclosure or claims.

[0215] These programs (software modules or software) can be stored in random access memory, non-volatile memory including flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage device, optical disk read-only memory, digital versatile disk (DVD) or other types of optical storage devices, or magnetic tape. Alternatively, these programs can be stored in a memory composed of all or part of the above storage devices. Each component memory can include multiple storage units.

[0216] These programs may be stored in a connectable storage device accessible via a communication network (e.g., the Internet, an intranet, a local area network (LAN), a wide area network (WLAN), a storage area network (SAN), or a communication network formed by a combination thereof). The storage device may be connected to a device executing an embodiment of the present disclosure via an external port. A separate storage device may also be connected to a device executing an embodiment of the present disclosure via a communication network.

[0217] In the above specific embodiments, the components included in the present disclosure are expressed in singular or plural form according to the specific embodiments proposed. However, the singular or plural form is selected to adapt to the context suggested for convenience of description, and the present disclosure is not limited to singular or plural components. As used herein, the singular forms "a", "an", and "the" are intended to include plural forms as well, unless the context clearly indicates otherwise.

[0218] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.

Claims

1. An application function AF entity in a wireless communication system, the AF entity comprising: Transceiver; as well as at least one processor, wherein the at least one processor is configured to: Sending traffic scheduling information to a network entity, the traffic scheduling information including at least one of a period range and a burst arrival time BAT range, receiving information about at least one of a first period and a first BAT from the network entity, and adjusting a schedule of an application based on information about at least one of the first period and the first BAT, The information about at least one of the first period and the first BAT is determined based on at least one of the period range and the BAT range.

2. The AF entity according to claim 1, wherein: The traffic scheduling information includes at least one of the following: Capability indication for scheduling adaptation, Initial cycle, Initial BAT, or Uplink / downlink flow direction.

3. The AF entity according to claim 2, in, The traffic scheduling information is included in the time-sensitive communication assistance information TSCAI through the session management function SMF entity, and The TSCAI is sent to the base station.

4. The AF entity according to claim 1, in, The first period and the first BAT are determined by a base station, The first BAT is determined when the traffic scheduling information includes the capability indication for scheduling adaptation, and The first BAT is adjusted by a session management function SMF entity.

5. A base station in a wireless communication system, the base station comprising: Transceiver; as well as at least one processor, wherein the at least one processor is configured to: receiving traffic scheduling information from a network entity, the traffic scheduling information including at least one of a period range and a burst arrival time BAT range, Based on the traffic scheduling information, determining information about at least one of a first period and a first burst arrival time BAT, and sending information about at least one of the first period and the first BAT to the network entity, The information about at least one of the first period and the first BAT is used to adjust the scheduling of the application.

6. The base station according to claim 5, wherein: The traffic scheduling information includes at least one of the following: Capability indication for scheduling adaptation, Initial cycle, Initial BAT, Uplink / downlink flow direction.

7. The base station according to claim 6, in, The at least one processor is further configured to receive the traffic scheduling information in time sensitive communication assistance information TSCAI, and The traffic scheduling information is included in the TSCAI through the session management function SMF entity.

8. The base station according to claim 5, in, The first BAT is determined when the traffic scheduling information includes the capability indication for scheduling adaptation, and The first BAT is adjusted by a session management function SMF entity.

9. A method for an application function AF entity in a wireless communication system, the method comprising: Sending traffic scheduling information to a network entity, the traffic scheduling information including at least one of a period range and a burst arrival time BAT range; receiving information about at least one of a first period and a first BAT from the network entity; as well as adjusting a schedule of an application based on information about at least one of the first period and the first BAT; The information about at least one of the first period and the first BAT is determined based on at least one of the period range and the BAT range.

10. The method according to claim 9, wherein: The traffic scheduling information includes at least one of the following: Capability indication for scheduling adaptation, Initial cycle, Initial BAT, or Uplink / downlink flow direction.

11. The method according to claim 10, in, The scheduling information is included in the time-sensitive communication assistance information TSCAI through the session management function SMF entity, and The TSCAI is sent to the base station.

12. The method according to claim 9, in, The first period and the first BAT are determined by a base station, The first BAT is determined when the traffic scheduling information includes the capability indication for scheduling adaptation, and The first BAT is adjusted by a session management function SMF entity.

13. A method for a base station in a wireless communication system, the method comprising: receiving traffic scheduling information from a network entity, the traffic scheduling information including at least one of a period range and a burst arrival time BAT range, Based on the traffic scheduling information, determining information about at least one of a first period and a first burst arrival time BAT, and sending information about at least one of the first period and the first BAT to the network entity, The information about at least one of the first period and the first BAT is used to adjust the scheduling of the application.

14. The method according to claim 13, wherein: The traffic scheduling information includes at least one of the following: Capability indication for scheduling adaptation, Initial cycle, Initial BAT, Uplink / downlink flow direction.

15. The method according to claim 14, in, Receiving the traffic scheduling information includes receiving the traffic scheduling information in time-sensitive communication assistance information TSCAI, The traffic scheduling information is included in the TSCAI through a session management function SMF entity. The first BAT is determined when the traffic scheduling information includes the capability indication for scheduling adaptation, and The first BAT is adjusted by a session management function SMF entity.

Images