KR20220040407A - METHOD OF CREATING QoS FLOW FOR TIME SYNCHRONIZATION PROTOCOL IN WIRELESS COMMUNICATION NETWORK - Google Patents

Abstract

Provided is a method for creating a QoS flow for a time synchronization protocol in a wireless communication system. The method for creating a QoS flow may comprise the steps of: receiving, by an SMF, PTP profile information, from UE, along with DNN, S-NSSAI information, and a session ID for a TSC service; setting, by the SMF, a QoS flow for PCCrule and time synchronization protocol; providing, by the SMF, SDF filter information for the QoS flow and the QoS flow to a UPF; and providing, by the SMF, the QoS flow and a QoS rule filter to an AMF.

Description

Method of creating QoS flow for time synchronization protocol in wireless communication system

The present invention relates to a method of generating a QoS flow for effectively delivering a time synchronization protocol for supporting Time Sensitive Communication (TSC) in 5GS.

5GS supports interworking with TSN (Time Sensitive Networking) to support citizen communication. In civic communication, time synchronization of devices participating in civic communication is premised, and time synchronization is performed using a time synchronization protocol. there is. However, since the time synchronization protocol corresponds to user traffic in the 5GS virtual bridge, a method for efficiently delivering the time synchronization protocol by creating a QoS flow is required.

In 5G, one or more QoS flows are supported for a PDU (Protocol Data Unit) session, and each QoS flow may have different traffic processing characteristics. If the QoS flow for delivering the time synchronization protocol does not satisfy the QoS level required by the time synchronization protocol, the time synchronization quality may not be satisfactory. Since QoS flow generation in the conventional 5G does not automatically reflect the characteristics for time synchronization protocol delivery, effective operation of the time synchronization protocol cannot be guaranteed.

It is difficult to guarantee the operation of the time synchronization protocol if the delay occurring in the transmission of the time synchronization protocol is above a certain level or if the deviation in the delay occurring in the transmission of the time synchronization protocol is large. The time synchronization protocol has a principle of operation using the mean path delay between the master clock and the slave clock for time synchronization, and the 5GS virtual bridge on the time synchronization protocol path If the proper QoS is not guaranteed, the average path delay will be out of the appropriate level or the deviation will become too large, so the performance of the time synchronization protocol cannot be guaranteed.

The problem to be solved by the present invention is to create a QoS flow that can satisfy the QoS required by the time synchronization protocol when the master clock and slave clocks for citizen communication in 5GS perform synchronization using the time synchronization protocol. It is to provide a method of creating a QoS flow that can be

A QoS flow generation method according to an embodiment of the present invention comprises: receiving, by an SMF, PTP profile information from a UE together with DNN for TSC service, S-NSSAI information and a session ID; setting, by the SMF, a QoS flow for PCCrule and time synchronization protocol; providing, by the SMF, SDF filter information for the QoS flow and the QoS flow to the UPF; and providing, by the SMF, the QoS flow and QoS rule filter to the AMF.

In an embodiment, the step of the SMF setting the QoS flow for the PCCrule and the time synchronization protocol includes the step of using the preset PCCrule, the SMF setting the QoS flow for the PCCrule and the time synchronization protocol. can do.

In an embodiment, the SMF setting the QoS flow for the PCCrule and the time synchronization protocol includes: the SMF requesting the PCF to set the PCCrule; receiving the configured PCCrule from the PCF; and using the received PCCrule, the SMF setting the QoS flow for the PCCrule and the time synchronization protocol.

In one embodiment, the step of the SMF requesting the PCF to set the PCCrule, the SMF transmits the PTP profile information provided from the UE to the PCF along with the DNN, the S-NSSAI information and the session ID. may include steps.

In an embodiment, the PTP profile information may be transmitted through an Announce message.

In an embodiment, the PTP profile information includes selection information for one-step and two-step, information on a method to be used as a path delay mechanism and information on a method to use as a transport mechanism, multicast or Information on whether to use unicast, the address, and information on the period of each PTP message may be included.

In an embodiment, the QoS flow may include at least one of Packet Delay Budget (PDB), Priority, Allocation and Retention Priority (ARP), and Guaranteed Flow Bit Rate (GFBR).

In an embodiment, the SDF filter and the QoS rule filter include a multicast address of Ethernet for a time synchronization protocol, an ethertype of Ethernet for a time synchronization protocol, a multicast address of IP for a time synchronization protocol, and a time synchronization protocol. It may include at least one of ports of UDP for

In an embodiment, the QoS flow, when the QoS requirement of the PTP profile information provided from the UE is lower than the QoS requirement for the preset PTP profile, based on the QoS requirement for the preset PTP profile can be created

A network entity according to an embodiment of the present invention includes: a network interface; and receiving PTP profile information from UE along with DNN, S-NSSAI information and session ID for TSC service, setting QoS flow for PCCrule and time synchronization protocol, and SDF for the QoS flow and the QoS flow in UPF It may include a processor that provides filter information and provides the QoS flow and QoS rule filter to the AMF.

A QoS flow generation method according to an embodiment of the present invention comprises: receiving, by an SMF, a session change request including ReqQoS, which is QoS required for a QoS flow that can be specified by PktFltr for a time synchronization message from a UE; setting the SMF session policy; requesting, by the SMF, to change the QoS flow for the session to the UPF; and the SMF providing the QoS flow change information for the session to the AMF.

In an embodiment, the step of setting the session policy by the SMF may include setting the session policy by the SMF using a preset PCCrule.

In an embodiment, the step of the SMF setting the session policy may include: the SMF requesting the PCF to change the PCCrule; receiving the modified PCCrule from the PCF; and setting, by the SMF, a session policy using the received PCCrule.

In one embodiment, in the method, if the ReqQoS and PTP profile from the UE are higher than the QoS requirements of the PTP profile currently used in the TSN domain to which the UE belongs, the PTP currently used in the TSN domain The method may further include performing a session change for sessions of other UEs using the profile-based QoS flow.

In an embodiment, the PTP profile information includes selection information for one-step and two-step, information on a method to be used as a path delay mechanism and information on a method to use as a transport mechanism, multicast or Information on whether to use unicast, the address, and information on the period of each PTP message may be included.

A network entity according to an embodiment of the present invention includes: a network interface; Receives a session change request including ReqQoS, which is the QoS required for a QoS flow that can be specified with PktFltr for a time synchronization message from the UE, sets a session policy, and requests a QoS flow change for the session to UPF and a processor that provides the QoS flow change information for the session to the AMF.

QoS flow generation method according to an embodiment of the present invention, the step of receiving the SMF together with DNN, S-NSSAI information and session ID for a TSC service that does not include PTP profile information from a UE; setting, by the SMF, a QoS flow for a PCCrule and a time synchronization protocol using the PTP profile information stored by the SMF; providing, by the SMF, SDF filter information for the QoS flow and the QoS flow to the UPF; and providing, by the SMF, the QoS flow and QoS rule filter to the AMF.

A network entity according to an embodiment of the present invention includes: a network interface; and DNN, S-NSSAI information, and session ID for TSC service that does not include PTP profile information from the UE and a processor that provides SDF filter information for the QoS flow and the QoS flow to the UPF, and provides the QoS flow and QoS rule filter to the AMF.

According to embodiments of the present invention, by creating a QoS flow reflecting the PTP (Precision Time Protocol) profile of the time synchronization protocol and allowing the time synchronization protocol to be processed as the corresponding QoS flow, the time synchronization quality is guaranteed and a sense of citizenship Communication can be smoothly provided.

1 is a diagram for explaining a TSN bridge according to an embodiment of the present invention.
2 is a diagram for explaining a TSN bridge according to an embodiment of the present invention.
3 is a diagram for explaining an example of a master clock and a slave clock when a time synchronization protocol according to an embodiment of the present invention is applied.
4 and 5 show an example in which a TSN bridge is configured of 5GS according to an embodiment of the present invention.
6 is a diagram for explaining a PDU session and QoS flow of 5GS according to an embodiment of the present invention.
7 is a diagram for explaining the properties of a QoS flow used in 5GS according to an embodiment of the present invention.
8 is a diagram for explaining a delay from a TSN GM to a TSN bridge/end station according to an embodiment of the present invention.
9 is a diagram for explaining a delay when a 5G network operates as a TSN bridge according to an embodiment of the present invention.
10 is a diagram for explaining an example of a PTP protocol according to an embodiment of the present invention.
11 is a diagram for explaining an example of an Ethernet frame according to an embodiment of the present invention.
12 is a diagram for explaining an example of a UDP/IPv4 header according to an embodiment of the present invention.
13 is a diagram for explaining an example of a PTP profile according to an embodiment of the present invention.
14 is a diagram for explaining obtaining a time synchronization protocol profile according to an embodiment of the present invention.
15 is a diagram for explaining a relationship between QoS requirements of a master clock profile according to an embodiment of the present invention.
16 is a diagram for explaining a procedure for setting a QoS flow for a time synchronization protocol when establishing a PDU session according to an embodiment of the present invention.
17 is a diagram for explaining a QoS flow change procedure through a PDU session change procedure from a UE according to an embodiment of the present invention.
18 is a diagram for explaining a procedure for changing a QoS flow for an existing time synchronization protocol of another UE using a PDU session change procedure according to an embodiment of the present invention.
19 is a diagram for explaining a procedure for setting a QoS flow for a PDU session time synchronization protocol according to an embodiment of the present invention.
20 is a block diagram illustrating a computing device according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described in detail so that those of ordinary skill in the art can easily implement them with reference to the accompanying drawings. However, the present invention may be implemented in several different forms and is not limited to the embodiments described herein. And in order to clearly explain the present invention in the drawings, parts irrelevant to the description are omitted, and similar reference numerals are attached to similar parts throughout the specification.

Throughout the specification and claims, when a part "includes" a certain element, it means that other elements may be further included, rather than excluding other elements, unless otherwise stated.

1 is a diagram for explaining a TSN bridge according to an embodiment of the present invention.

Referring to FIG. 1, an example in which the bridges B1, B2, ..., Bn are connected between the citizen communication stations S1 and S2 of both ends is shown. One of the stations S1 and S2 can operate as a master clock and the other as a slave clock. The master clock provides a time synchronization message, and the slave clock receives the time synchronization message provided from the master clock. You can synchronize your own time to the master clock. Unlike the one shown in FIG. 1, the bridges (B1, B2, ..., Bn) between the master clock and the slave clock can be configured in various types of networks, and in any configuration, a certain level of communication quality must be guaranteed to ensure accurate Time synchronization can be guaranteed.

2 is a diagram for explaining a TSN bridge according to an embodiment of the present invention.

Referring to FIG. 2 , there is shown an example in which the bridges B1, B2, ..., Bn are connected between the citizen communication stations S1 to S4 at both ends as a case in which there are several clocks for citizen communication. . If the station S1 is the master clock and the stations S2, S3, and S4 are slave clocks, the stations S2, S3, and S4 synchronize to the station S1.

When both the station S1 and the station S2 are master clocks, the station S1 is selected as the master clock through the BMCA (Best Master Clock Algorithm) between them, and the station S2 serves as the master clock. I never do that. In some embodiments of the present invention, the master clock may mean both the station S1 and the station S2, or differently, only the station S1 after performing BMCA.

Within one civil communication domain, the highest master clock becomes the GrandMaster Clock, and other clocks can operate as the master clock by synchronizing clocks from the grandmaster clock.

3 is a diagram for explaining an example of a master clock and a slave clock when a time synchronization protocol according to an embodiment of the present invention is applied.

Referring to FIG. 3 , when two master clocks GM1 and GM2 are applied, BMCA is applied between them to operate the master clock GM1 as the active master clock and the master clock GM2 does not act as a master. It can be operated with a passive master clock. A Boundary Clock BC and a first slave clock 1 are synchronized from the master clock GM1 via a first Transparent Clock TC1, and the Two slave clocks (Slave clock 2) may be synchronized, and a third slave clock (Slave clock 3) may be synchronized via the second transparent clock (TC2). That is, the boundary clock BC receives the time synchronization message from the master clock, becomes the master and supplies the time synchronization message to the lower clocks again, and the first transparent clock TC1 and the second transparent clock TC2 ), the transparent clock can transparently transmit the time synchronization protocol between the master clock and the slave clock. There are two methods of operating the transparent clock in an end-to-end (EE) mode and a peer-to-peer (PP) mode, which will be described later with reference to FIGS. 8 and 10 .

4 and 5 show an example in which a TSN bridge is configured of 5GS according to an embodiment of the present invention.

Referring to FIG. 4 , 5GS may be applied to any of the bridges B1, B2, ..., Bn of FIG. 1, and the 5GS bridge 10 includes a user equipment (UE) 100, a UPF ( User Plane Function) 104 and Radio Access Network (RAN) 108 , and the like.

Referring to FIG. 5 , an example of a control interface of 5G citizen communication is shown. When the 5G network 10 is inserted as a TSN bridge in the middle of the TSN system, translators for TSN may be required on both sides of the 5G network 10 . 5 , the 5G network 10 may operate as a bridge for connecting the TSN bridge/end station 20 to the TSN system 30 . The TSN system 30 may be referred to as a DN or a TSN-DN. The 5G network 10 may transmit starter information of a TSN GrandMaster clock (GM) 32 existing in the TSN-DN 30 to the TSN bridge/end station 20 .

The CNC/CUC 34 may collect configuration information and requirements of the TSN end stations 36 in the TSN system 30 and define and command the operating characteristics of the TSN bridge and TSN end stations.

The AF (Application Function) 110 provides the 5G network 10 and the shape information of the TSN bridge/end station 20 connected through the 5G network 10 to the CNC/CUC 34, and the CNC/CUC 34 ) from the 5G network 10 and the command for the operation method of the TSN bridge/end station 20 connected through the 5G network 10 may be received. AF can be replaced by the term TSN AF, which receives requirements for processing citizenship data for a specific stream via a control protocol from CNC/CUC (34) and implements them via a Policy Control Function (PCF) (112). can transmit The PCF 112 may set a PCCrule based on the information received from the AF 100 . Requirements for citizen data processing may include a stream identifier (ID) for a specific stream, bandwidth, maximum frame size, frame period, and the like. The AF 110 and the PCF 112 may communicate directly or communicate through a Network Exposure Function (NEF) 120 according to a network shape.

The PCF 112 transmits the shape information and PTP requirements of the 5G network 10 and the TSN bridge/end station 20 connected through the 5G network 10 received from the SMF (Session Management Function) 114 to the AF 110 ), it is determined whether the UE 100 can be provided with a requirement for processing citizenship data from the AF 110 , and the determined result can be informed to the SMF 114 . The UDM 118 manages subscription information including the citizenship service subscribed by the UE 100 in the 5G network 10, and provides it to the Access and Mobility Management Function (AMF) 116 / SMF 114. can provide The AMF 116 allows the UE 100 to access the 5G network 10 , and the AMF 115 enables the UE 100 to establish a session for citizen communication in the 5G network 10 . there is.

A Network TSN Translator (NW-TT) 106 may perform conversion between the 5G network 10 and the TSN system 30 on TSN data frames. The NW-TT 106 may exist within the UPF 104 or may exist independently outside the UPF 104 . Since the 5G network 10 employs a packet processing method higher than the IP layer and the TSN system 30 adopts a frame processing method in the data link layer, the NW-TT 106 can perform conversion for different layers. there is.

The UE 100 may be connected to the TSN bridge/end station 20 through a Device Side TSN Translator (DS-TT) 102 . The DS-TT 102 performs conversion for the traffic transmitted from the TSN system 30 and the traffic transmitted to the TSN system for the UE 100 belonging to the 5G network 10, and further conversion for control can be performed. This DS-TT 102 is similar to the roles of the AF 110 and the NW-TT 106 . The DS-TT 102 may exist inside the UE 100 , or may exist independently outside the UE 100 .

A Radio Access Network (RAN) 108 may perform radio access to the moving UE 100 . The UPF 104 processes user data, and serves as an anchor of the UE 100 to the TSN system 30 when the user moves to a range where the UPF 104 changes. Here, one or more UPFs 104 may be added between the anchor UPF 104 and the RAN 108 . The NEF 120 informs the TSN system 30 of the function of the 5G network 10 , and the TSN system 30 can use the 5G network 10 through this.

The 5G network 10 is time-synchronized with the 5G clock internally to support citizen communication. The TSN system 30 and the TSN bridge/end station 20 must be time synchronized with the TSN GM 32 . For this purpose, PTP or the like may be used. When the starter information received from the TSN system 30 is transmitted to the TSN bridge/end station 20 , the starter information is corrected by measuring a residence time required to traverse the 5G network 10 , and thus the TSN GM can be synchronized to In embodiments of the present invention, the performance of the time synchronization protocol is ensured by creating a QoS flow for the time synchronization protocol so that the 5G residence time is within a certain time and the deviation is also within a certain range.

Here, the synchronized time display may include year, month, day, hour, minute, second, millisecond, microsecond, and nanosecond.

6 is a diagram for explaining a PDU session and QoS flow of 5GS according to an embodiment of the present invention.

Referring to FIG. 6 , a PDU session may generally include uplink (UL) and downlink (DL) data radio bearer (DRB) and GTP-U tunnels, and the GTP-U tunnel includes N3 tunnels and N9 tunnels. can do. If there is no intermediate UPF between the anchor UPF and the RAN connected to the TSN system, only the N3 tunnel exists. On the other hand, when there is an intermediate UPF, an N9 tunnel exists between the intermediate UPF and the anchor UPF. QoS rules and SDF filters can be used to map user data in the form of Ethernet frames or IP packets to QoS flows.

One service data flow has one or more QoS flows, and in this case, QoS flows can be applied independently or equally for each uplink/downlink (UL/DL).

7 is a diagram for explaining the properties of a QoS flow used in 5GS according to an embodiment of the present invention.

Referring to FIG. 7 , a QoS Flow Identifier (QFI) is an identifier indicating a QoS flow, and is a unique value within a PDU session. Packet flows with the same QFI receive the same QoS treatment. A QoS flow represented by one QFI may be defined with various parameters.

5QI (5G QoS Identifier) is an identifier for the QoS flow processing method predetermined in 5G, and some operation characteristics for 5QI can be changed, and a new 5QI can be defined.

In addition, Priority indicating priority, Packet Delay Budget (PDB) indicating delay, CN_PDB indicating delay of the core network (see Fig. 9), Packet Error Rate (PER) indicating allowable packet error rate, pre-emption Allocation and Retention Priority (ARP) indicating capability) and pre-emption vulnerability, Maximum Data Burst Volume (MDBV) indicating maximum instantaneous transmission amount, Averaging Window indicating unit time for calculating the transmission rate of GFBR/MFBR, Reflective QoS Attribute (RQA) indicating information related to applying reflective QoS, Notification Control (NC) indicating whether to report when GFBR is not satisfied, Guaranteed Flow Bit Rate (GFBR) indicating guaranteed transmission rate, Maximum indicating maximum transmission rate QoS flow can be defined with properties such as Flow Bit Rate (MFBR) and Maximum Packet Loss Rate (MPLR) indicating the maximum packet loss rate. Here, GFBR, MFBR, and MPLR can be set separately for uplink/downstream. In some embodiments of the present invention, only specific parameters may be set without setting all of the QoS flow attribute values listed above, and no special control may be performed on unset parameters.

Uplink/downlink QoS flows may be set with the same characteristics or set with different characteristics.

8 is a diagram for explaining a delay from a TSN GM to a TSN bridge/end station according to an embodiment of the present invention.

Referring to FIG. 8 , the delay from the TSN GM to the TSN Bridge/End station is shown for each section, indicating the delay when the bridge B operates as the transparent clock TC of the PTP. When the transparent clock (TC) operates in end-to-end mode, it measures the end-to-end delay between the master clock (MC) and the slave clock (SC), When the transparent clock (TC) operates in peer-to-peer mode, the peer-to-peer delay between the master clock (MC) and the slave clock (SC) and the transparent clock (TC) is delay) can be measured and used. The transparent clock (TC) can be corrected by measuring the residence time in the bridge (B) when the time synchronization protocol signal from the master clock is transmitted, and the residence time and deviation must be within a certain range.

5GS can operate as a transparent clock to TSN.

9 is a diagram for explaining a delay when a 5G network operates as a TSN bridge according to an embodiment of the present invention.

9, the delay from the UPF (104) / NW-TT (106) to the UE (100) of the 5G network 10 is a Packet Delay Bound (PDB), of which UPF (104) / NW-TT The delay from 106 to RAN 108 is CN_PDB, and the delay from RAN 108 to UE 100 is RAN_PDB. The sum of RAN_PDB and CN_PDB is the PDB of the 5G network 10 . The transfer time from the DS-TT 102 to the UE 100 is the UE-DSTT dwell time, and the sum of the UE-DSTT dwell time and the PDB is the 5G bridge dwell time.

In the case of the TSN system A (20a, 30a) of FIG. 9, the master clocks (MC) are shown as A1 and A2, respectively, but only one of them operates as the best master clock through BMCA, and the delay at this time is 5G bridge It takes as much time as your stay.

In the case of the TSN system B 20b, 20c, 30b of FIG. 9, the delay when B1 operates as the best master clock through BMCA among the master clocks B1, B2, and B3 takes as much as the 5G bridge residence time. . If B2 or B3 is running with the best master clock, the delay when the time-synchronized protocol is delivered to the TSN end station B1 takes as much as the 5G bridge dwell time, but the time-synchronized protocol from the GM being B2 or B3 is transmitted to the TSN end station B3. However, the delay in the case of delivery to the TSN end station B2 is (2 * (5G bridge dwell time) - UPF_processingdelay). Here, UPF_processingdelay is a value included in the calculation of CN_PDB as a packet processing delay in the UPF 104/NW-TT 106.

10 is a diagram for explaining an example of a PTP protocol according to an embodiment of the present invention.

Referring to FIG. 10 , OC-M is an ordinary clock operating as a master, and OC-S is an ordinary clock operating as a slave. BC is a boundary clock, TC(EE) is a transparent clock operating in end-to-end mode, and TC(PP) is a transparent clock operating in peer-to-peer mode. Usually the clock is a master clock or a slave clock with only one port. The boundary clock is a clock with two phase ports, and one port operates as a slave to the upper master and the other ports operate as the master. The boundary clock synchronizes with the upper master as a slave and supplies the synchronized time to other slaves as a master. One port operates as a slave to the upper master, and the other ports operate as masters. A transparent clock is a clock with two ports on the clock. By measuring the residence time of a PTP event message passing through the transparent clock and providing the transit time information using the PTP message, the PTP message is transmitted through the transparent clock. Allows incoming clocks to compensate for the time spent passing through the transparent clock. Transparent clock provides end-to-end mode and peer-to-peer mode. The transparent clock in end-to-end mode provides a transit time of the transparent clock for end-to-end delay measurement between master and slave. The transparent clock in peer-to-peer mode measures the peer-to-peer delay between the upper master and the transparent clock and provides it in addition to the transit time of the transparent clock. At this time, the slave under the transparent clock measures the peer-to-peer delay between the transparent clock and itself and uses it to compensate for its own time.

The Sync message is a packet that periodically transmits the reference time from the master to the slave. In One-step PTP, the time at which the Sync message is transmitted is recorded in the Sync message. The FollowUp message records the transmission time of the Sync message in the two-step PTP and delivers it to the slave. FollowUp message is delivered at the same cycle as Sync message.

DelayReq/DelayResp messages are used to calculate one way delay, and the time when the master receives the DelayReq message from the slave is recorded in the DelayResp message and delivered back to the slave. These are delivered in the same period as the Sync message. The PDelayReq/PDelayResp/PDelayRespFollowUp message measures the link delay between the upper master and the transparent clock and between the transparent clock and the lower slave when the peer-to-peer transparent clock method is used. used to do The PDelayRespFollowUp message transmits the time when the PDelayResp message is sent when two-step PTP is applied. The other Announce message is a message that periodically delivers the PTP attribute of each master to determine the GM, and determines the GM using the BMCA based on the PTP attribute of the Announce message. BMCA organizes clocks in a hierarchical structure and ensures that slave clocks use the most accurate clock available on the network. Ports of normal and boundary clocks that are not slave-only transmit Announce messages including attributes including clock priority and quality, and each clock in the network uses attributes received from BMCA and Announce messages. to select the best clock to synchronize and determine the PTP state of each port as M, S, P. M is a port that sends synchronization information to the master, S is a port that receives synchronization information to a slave, and P is a passive port that neither sends nor receives synchronization information. Management message is used for network management such as monitoring, setting, and management of the PTP system. Signaling messages are used for non-time-critical communication such as service negotiation between clocks.

PTP can operate in one-step and two-step. One-step is a method in which the time when the Sync message is transmitted from the master is directly recorded in the Sync message. Similarly, in one step, the time is directly recorded in the PDelayResp message, but in the two step, the time at which the PDelayResp message is transmitted is recorded in the PDelayRespFollowUp message and delivered.

The PTP Sync, FollowUp, DelayReq, DelayResp, PDelayReq, PDelayResp, and PDelayRespFollowUp messages of FIG. 10 are transmitted periodically. Also, an Announce message is transmitted periodically. For clarity of explanation, the explanation is mainly based on the Sync message.

The syncInterval indicating the period of the PTP Sync message is expressed as an exponent of 2 using LogSyncInterval. If LogSyncInterval=0, syncInterval is 1 second, if LogSyncInterval=1, syncInterval is 2 seconds, if LogSyncInterval=-1, syncInterval is 1/2 second, LogSyncInterval= If -5, syncInterval is 1/32 second, and if LogSyncInterval=-7, syncInterval is 1/128 second. SyncInterval is determined according to the accuracy of the local clock of the end station and the clock accuracy required by the application of the end station.

The amount of data required for PTP may vary depending on the applied PTP profile. It is affected by various factors such as the type of transport such as Ethernet/IPv4/IPv6 used, the one-step/two-step PTP method, the transmission period of each message, and the size of the variable message body. Here, an example of calculation is shown based on the case of transmitting only Sync messages with LogSyncInterval=-7 through Ethernet in one-step PTP method. One-step PTP's Sync message is 118 bytes including Ethernet overhead, which is 944 bits. If you send this at 128 times/sec, it will be about 120kbps. When the slave clocks receiving the time synchronization protocol message from another master clock provide time synchronization messages to B2 and B3 in FIG. 9, B2 and B3 each need 120 kbps, but B2 is the master In the case of providing a time synchronization message to B1 and B3, B2 needs a higher transmission rate for Delay Req/Resp from B3.

As described above, the guaranteed flow bit rate of 5G QoS required for PTP protocol transmission depends on the type of transport, one-step/two-step PTP method, and end-to-end/peer-to-peer path delay mechanism (Path Delay). Mechanism), Sync message, DelayRep/Resp message, PDelayReq/Resp message, and announcement message transmission period, variable message body size, and number of connected slave clocks are taken into consideration.

The bridge delay (residence time) required to transmit the PTP message is affected by the transmission period of the Sync message. For example, the bridge delay must be greater than or equal to 0.7*syncInterval and less than or equal to 1.3*syncInterval. Here, an example of calculation based on the case of LogSyncInterval=-7 is shown. The syncInterval becomes 1/128 second, and the requirement of the bridge delay is 5.5ms or more and 10ms or less. The 5G QoS PDB required for PTP protocol transmission is determined in consideration of the Sync message cycle, and a QoS flow that satisfies the transmission delay is set.

An acceptable error rate in transmitting a PTP message is affected by the accuracy of the local clock of the end station and the clock accuracy required by the application of the end station. The local clock of the end station receives the Sync message and synchronizes to the GM, and an error occurs after a certain period of time passes, and the error is overcome by receiving the next Sync message. That is, the degree of error in the Sync messages from GM is determined at the time of designing the civic communication system.

11 is a diagram for explaining an example of an Ethernet frame according to an embodiment of the present invention.

Referring to FIG. 11 , when PTP is transmitted over Ethernet, Ethernet preamble, Start of Frame Delimiter (SFD), destination MAC address, Source MAC address, 802.1Q Tag, EtherType, PTP -Data, FCS (Frame Check Sequence), and IFG (Inter Frame Gap) are all added up, and in the case of PTP sync message, if PTP is configured as two-step, it is 76 bytes, and if it is configured as one-step, it is 118 bytes.

The PTP message format included in the payload of Ethernet consists of a message header 34 bytes and a variable message body, but in the case of a Sync message, the message body is 10 bytes or 52 bytes, which is 44 bytes or 86 bytes in total. When PTP is composed of one-step, it is 44 bytes, and when it is composed of two-step, it is 86 bytes. A QoS flow that satisfies such a transmission delay is set, and a required transmission rate can be obtained by multiplying the period described in relation to FIG. 10 and the size described in FIG. 11 .

When transmitting PTP over Ethernet, use 01-80-C2-00-00-0E or 01-1B-19-00-00-00 as the destination MAC address and use 0x088F7 as the Ethertype. For the destination MAC address, use 01-80-C2-00-00-0E for messages such as PDelayReq, PDelayResp, PDelayRespFollowUp, and 01:1B:19:00 for other messages (Announce, Sync, Follow_up, Delay_Req, Delay_Resp, etc.) Use :00:00. This information can be used as a packet filter when setting up a PCCrule.

12 is a diagram for explaining an example of a UDP/IPv4 header according to an embodiment of the present invention.

Referring to FIG. 12 , when PTP is transmitted through UDP/IP, 28 bytes are increased compared to when PTP is transmitted through Ethernet. That is, in the case of the PTP Sync message, when PTP is configured as two-step, it is 76+28 bytes, and when it is configured as one-step, it is 118+28 bytes.

When transmitting PTP using UDP/IPv4, use 224.0.0.107 or 224.0.1.129 for the destination IP address, and use 319 or 320 for the UDP destination port. For the destination IP address, use 224.0.0.107 for messages such as PDelayReq, PDelayResp, PDelayRespFollowUp, and use 224.0.1.129 for other messages (Announce, Sync, Follow_up, Delay_Req, Delay_Resp, etc.). On the other hand, depending on the PTP domain, 224.0.1.129 ~ 224.0.1.132 are used instead of the destination IP address of 224.0.1.129. For UDP destination port, use 319 for PTP event messages such as Sync, DelayReq, PDelayReq, and PDelayResp, and use 320 for other PTP general messages (FollowUp, DelayResp, PDelayRespFollowUp, Announce, Management, Signaling, etc.). . As such, it can be used as a packet filter when setting up a PCCrule.

In case of transmitting PTP with UDP/IPv6, IPv6 header is 20 bytes longer than IPv4 header. become bytes.

The case of transmitting the PTP using UDP/IPv6 is similar to the case of transmitting the above-described UDP/IPv4. However, FF02:0:0:0:0:0:0:6B instead of 224.0.0.107 and FF0x:0:0:0:0:0:0:181 instead of 224.0.1.129 are used as destination IP addresses. This information can be used as a packet filter when setting up a PCCrule.

13 is a diagram for explaining an example of a PTP profile according to an embodiment of the present invention.

Referring to FIG. 13 , the PTP profile describes a profile name, an identifier, a domain number of the corresponding PTP, priority (priority), and a BMCA type, and includes information indicating the type of clock used. In addition, selection information for one-step and two-step, information on a method to be used as a path delay mechanism, and information on a method to be used as a transport mechanism are designated. In addition, information on whether to use multicast or unicast, an address thereof, and information on a period of each PTP message are included.

Applying QoS rules and SDF filters using address information used for multicast/unicast, one-step/two-step information, path delay mechanism, delivery mechanism, message rate (Sync Rate, Delay Req/Resp) Rate, Announce Rate) can be used to determine the parameters of the QoS flow of FIG. 7 . In some embodiments of the present invention, since the Announce message is less sensitive to the delivery time, it may be excluded from the calculation of the parameter setting of the QoS flow and delivered as a Default QoS flow that is a Non-GBR (Guranteed Bit Rate).

The PTP profile has the UE or AF when the UE provides the master clock, and the SMF, PCF, or AF when the TSN-DN provides the master clock. The PTP profile is information used for the configuration and operation of PTP, and UE, SMF, PCF, and AF have the PTP profile as it is and generate the information necessary for QoS flow formation when necessary, or convert it into the information required for QoS flow formation and manage it. can

In addition, without receiving a PTP profile from the UE, the SMF may generate a PccRule capable of supporting the PTP profile required for TSC service through DNN and S-NSSAI. When a session is requested from the UE including PTP profile information along with DNN and S-NSSAI, or when a session is requested from the UE including only DNN and S-NSSAI that do not include PTP profile information, there may be cases, In each of these two cases, the SMF may determine the PCCrule itself (according to the stored TSC PTP information for the DNN/S-NSSAI), or the SMF may request the PCF to set the PCCrule. When the SMF requests the PCF to set the PCCrule, the PCF determines the PCCrule according to the information it stores (TSC PTP information for DNN/S-NSSAI) or information from AF or UDM. can decide

14 is a diagram for explaining obtaining a time synchronization protocol profile according to an embodiment of the present invention.

Referring to FIG. 14 , acquiring a time synchronization protocol profile according to an embodiment of the present invention is performed through an Announce message. In the present invention, the time synchronization protocol profile is a method of presetting the time synchronization protocol profile of the master clock to be used in the UE 100 to the UE 100 and the setting of the UE 100 using an Announce message through the DS-TT 102 use the method The method of presetting in the UE 100 is a method of setting time synchronization protocol profile information of a master clock to be connected to the UE 100 to the UE 100, and the UE 100 using an Announce message through the DS-TT 102 ) can be set through (A) or (B) of FIG. 14 . In (A), the DS-TT 102 obtains the time synchronization protocol profile from the Announce message and provides it to the UE 100, and (B) is a method in which the UE 100 obtains the time synchronization protocol profile from the Announce message. way.

Similarly, the method of setting the time synchronization protocol profile in the network is also similar to the method of setting the time synchronization protocol profile in any one of the SMF (114) / PCF (112) / AF (110) and NW-TT (106) through A method of setting any one of the SMF 114 / PCF 112 / AF 110 using the Announce message is used. 14C shows that the time synchronization protocol profile is transferred from the Announce message received by the NW-TT 106 to the SMF 114, the SMF 114 back to the PCF 112, and the PCF 112 again. This is an example of transferring to the AF 110 .

15 is a diagram for explaining a relationship between QoS requirements of a master clock profile according to an embodiment of the present invention.

Referring to FIG. 15 , an embodiment of the setting relationship of QoS requirements of the master clocks MC is shown with a focus on the 5G virtual bridge 10 . For convenience of explanation, the description will be made based on the preset method, not the setting of the time synchronization protocol profile using the Announce message.

First, PtpPrf0 corresponding to the time synchronization protocol profile of the master clock (MC4) is set in advance.

When the UE1 100a establishes a session for citizen communication with PtpPrf_1 corresponding to the time synchronization protocol profile of the master clock MC1, the QoS flow for the time synchronization protocol to the UE1 100a is the higher of PtpPrf0 and PtpPrf_1 It is established based on the requirements. In this case, the time synchronization protocol profile for the set QoS flow may be referred to as PtpPrf0.

When the master clock MC2 is not connected to the UE2 yet, and the UE2 100b establishes a session for citizen communication without information about the time synchronization protocol profile, the QoS for the time synchronization protocol to the UE2 100b The flow is established based on the requirements of PtpPrf0.

After the master clock MC2 is connected to the UE2 100b, if the QoS requirement of the time synchronization protocol profile of the master clock MC2 is higher than the requirement of PtpPrf0, the UE2 100b sets the time of the master clock MC2 Session is changed for QoS flow setting with synchronous protocol profile (PtpPrf_2). Accordingly, the QoS flow for the time synchronization protocol of the session to the UE1 100a that has been previously set will also be changed to a QoS flow that can satisfy the requirement of PtpPrf_2.

When the UE3 100c establishes a session for citizen communication with PtpPrf_3 corresponding to the time synchronization protocol profile of the master clock MC3, the QoS flow for the time synchronization protocol to the UE3 100c is the higher of PtpPrf_2 and PtpPrf_3 QoS flows for the time synchronization protocol of sessions to UE1 100a and UE2 100b that have been set based on the requirement PtpPrf_3 and have been preset will also be changed to a QoS flow that can satisfy the requirement of PtpPrf_3.

Now, when the master clock (MC5) with a higher level time synchronization protocol profile is connected to support the master clock (MC5), the SMF(114)/PCF(112)/AF(110) becomes the master clock (MC5). QoS flows to support PtpPrf5, the time synchronization protocol profile of It will change to QoS flow.

The above example is an example of setting a QoS flow based on a higher requirement of a time synchronization protocol profile. In contention when there are multiple master clocks, the master clock is determined through BMCA. At this time, the priority of each clock to become the master clock, clock class, clock accuracy, etc. to select the master clock. Comparing the time synchronization protocol profile in the above example compares the profile when the master clock is selected based on priority, clock class, clock accuracy, etc. through BMCA. Here, BMCA is a method of selecting a master clock for each port by being distributed from each clock using an announce message, as well as a centralized type in which the connected clock information is transmitted to the SMF(114)/PCF(112)/AF(110) and compared. includes all methods.

16 is a diagram for explaining a procedure of setting up a QoS flow for a time synchronization protocol when establishing a PDU session according to an embodiment of the present invention.

Referring to FIG. 16 , in step (1), when UE_n 100, which is an arbitrary n-th UE, establishes a session, DNN and S-NSSAI information for TSC service are included in the PDU Session Establish Request. In this case, the ID of the session to be set and PTP profile (PtpPrf_n of UE_n ( 100 )) information may be included together. The PTP profile is provided to the UE 100 through DS-TT as information on the master clock to be transmitted from the UE 100 . The time synchronization protocol profile for the master clock may be preset in the UE 100 for storage and management, or the UE 100 may store/manage the time synchronization protocol profile included in the Announce message received through DS-TT. may be

In step (3), the PDU Session Establish Request from the UE 100 is forwarded to the SMF 114, and in step 7, the SMF 114 sets the policy of the session for the received PDU Session Establish Request. do. At this time, you can also use the predefined PCCrule (policy and charging control rule) preset in the SMF (114). This is a PCCrule that includes QoS information and packet filter information that can support the DNN and S-NSSAI PTP profiles that provide TSC. Knowing that it is necessary (preset), QoS information for PTP for the corresponding TSC (preset), and packet filter information for PTP for TSC (preset) can be determined.

Alternatively, the SMF 114 may request the PCF 112 to set a dynamic PCCrule in step 7-1. In this case, the SMF 114 includes the DNN, S-NSSAI, session ID and PTP profile information included in the PDU Session Establish Request received from the UE 100 and delivers it, as in step (7-2), the PCF ( 112) can be used to configure PCCrule. This is a PCCrule that includes QoS information and packet filter information that can support DNN and S-NSSAI PTP profile that provides TSC. Knowing that it is necessary (preset a), it can determine the Qos information for PTP for that TSC (preset b), and packet filter information for PTP for the TSC (preset c), and the PCF can determine the above preset (a, b, c) information can be set internally in advance or can be acquired through AF or UDM.

In step 7-3, the PCF 112 transmits the set PCCrule to the SMF 114.

Referring to step 7-4, the PCF 112 may set the PCCrule by itself, but by requesting the AF for authorization for the service to be provided to the UE 100, the service information for the service from the AF ( Service Information) can be provided and applied to PCCrule creation. At this time, the PCF 112 transmits DNN, S-NSSAI, session ID, and PTP profile information to the AF, and receives information necessary for PCCrule setting from the AF.

If the PTP profile from the UE 100 is not provided, the PCF 112 creates a PCCrule by referring to the time synchronization protocol profile of the corresponding DN and the TSN domain provided by the DNN, S-NSSAI, and TSN domains.

The time synchronization protocol profile (PtpPrf0) of the TSN DN specified by one or more of DNN, S-NSSAI, and TSN domains may be stored and managed in the SMF 114/PCF 112/AF in advance. PtpPrf0 can be managed as a preset value, and the SMF 114/PCF 112/AF receives and stores the time synchronization protocol profile included in the Announce message received by the UPF 104 (NW-TT). /manageable.

PCCrule may include information necessary to set up a QoS flow for a time synchronization protocol.

Meanwhile, if the PTP profile from the UE 100 is lower than the QoS requirements of PtpPrf0, a QoS flow may be generated based on PtpPrf0.

In step (7-3) or less of FIG. 16, one or more QoS flows indicating the corresponding QoS flows are denoted by QFI. The QFI includes attribute information of each QoS flow as shown in FIG. 7 . As the QoS flow for the time synchronization protocol, the uplink/downlink QoS flow is set respectively.

The SMF 114 determines the QoS flow by the SMF 114 itself in step 7, or determines the QoS flow based on the PCCrule received from the PCF 112 and then transmits the information to the UPF 104 / RAN 108 / transmitted to the UE 100 . In addition, the PCF 112 generates a PCCrule based on the DNN received from the SMF 114, the S-NSSAI, and the TSN domain included in the UE profile so that the SMF 114 generates a QoS flow. Also, the PCF 112 may request permission for a service including a PTP profile when requesting service information from the AF. Alternatively, when the PTP profile is not included in the service information request of the PCF 112 , service information on the service provided to the UE 100 by the AF may be provided to the PCF 112 .

In step 10, the UPF 104 provides the corresponding QoS flow and SDF filter information for the QoS flow, and sets the QoS flow for the downlink from the UPF 104 to the RAN 108 to the UPF 104. do.

In step 16, the QoS flow for the uplink from the RAN 108 to the UPF 104 is set to the UPF 104.

In steps 11 and 12, the SMF 114 provides the QoS flow configuration information for the session to the RAN 108 through the AMF 116, and also sends the UE 100 a PDU session establish accept. QoS rules are provided. This QoS rule includes a PacketFilter (ie, a QosRule filter) that can set a QoS flow for a time synchronization protocol and QoS parameters required therefor, and map time synchronization messages to the QoS flow.

Step 13 represents that PDU session establish accept information from the SMF 114 to the UE 100 is transferred from the RAN 108 to the UE 100 . A response from the UE 100 is transmitted to the SMF 114 through steps 13, 14, and 15, and the SMF 114 receives downlink information of the corresponding QoS flow from the RAN 108 and in step 16 Set to UPF 104.

17 is a diagram for explaining a QoS flow change procedure through a PDU session change procedure from a UE according to an embodiment of the present invention.

Referring to FIG. 17 , when the QoS flow set in FIG. 16 cannot satisfy PtpPrf_n of the UE_n 100 or when the QoS requirement of the master clock to be transmitted from the UE 100 increases, the UE 100 performs the session change procedure You can request to change the QoS flow through At this time, the QoS flow can be specified as a QoS flow having PktFltr for a time synchronization message among the PktFltrs received by the UE 100 in step 13 of FIG. 16 .

In step (1), the UE 100 requests a session change including ReqQoS, which is a required QoS, for a QoS flow that can be specified by PktFltr for a time synchronization message. In this case, the UE 100 may request a session change by including PtpPrf_n to be transmitted.

In step (3), the PDU Session Modify Request from the UE 100 is transmitted to the SMF 114 through the step (3), and the SMF 114 sets the session policy for the received PDU Session Modify Request. . At this time, you can use the predefined PCCrule (policy and charging control rule) preset in the SMF 114, or request the PCF 112 to change the dynamic PCCrule in step (7-1). In this case, the SMF 114 transmits the session ID, PktFltr, ReqQoS, and PtpPrf_n information included in the PDU Session Modify Request received from the UE 100, so that the PCF 112 as in step 7-2. Make it usable for PCCrule change.

In step 7-3, the PCF 112 transmits the changed PCCrule to the SMF 114.

Referring to step 7-4, the PCF 112 may change the PCCrule by itself, but by requesting the AF for permission for the service to be provided to the UE 100, the AF receives service information for the service and receives the PCCrule It can be applied to creation. In this case, the PCF 112 transmits the session ID, PktFltr, ReqQoS, and PtpPrf_n information, and receives information necessary for PCCrule setting from the AF.

The SMF 114/PCF 112/AF may be selectively used among ReqQoS and PtpPrf_n.

If ReqQoS and PtpPrf_n from the UE 100 are higher than the QoS requirements of PtpPrf0 currently used in the TSN domain to which the UE 100 belongs, sessions of other UEs using the existing PtpPrf0-based QoS flow in the TSN domain 18, the session change procedure of FIG. 18 must be performed.

In step (7), the SMF 114 determines the change of the QoS flow by itself or determines the QoS flow based on the PCCrule received from the PCF 112, and then transmits the information to the UPF 104 / RAN 108 / UE. forward to (100). Also, the PCF 112 generates a PCCrule based on the session ID, PktFltr, ReqQoS, PtpPrf_n, and TSN domain received from the SMF 114 so that the SMF 114 changes the QoS flow. Also, the PCF 112 may request permission for a service including a PTP profile when requesting service information from the AF.

In any one of steps 10, 16, and 19, the SMF 114 requests the UPF 104 to change the corresponding QoS flow.

In steps 11 and 12, the SMF 114 provides QoS flow change information for the session to the RAN 108 through the AMF 116, and also sends a PDU session modify command to the UE 100. QoS rules are provided. This QoS rule includes a PakcetFilter that can change the QoS flow for the time synchronization protocol and map time synchronization messages to the QoS flow.

Step 13 indicates that PDU session modification command information from the SMF 114 to the UE 100 is transferred from the RAN 108 to the UE 100 .

A response from the RAN 108 is transmitted to the SMF 114 through steps 14 and 15 , and a response from the UE 100 is transmitted to the SMF 114 through steps 17 and 18 .

18 is a diagram for explaining a procedure for changing a QoS flow for an existing time synchronization protocol of another UE using a PDU session change procedure according to an embodiment of the present invention.

Referring to FIG. 18, FIG. 18 is a case in which the SMF 114/PCF 112/AF detects a PTP profile having a higher requirement than the QoS requirement of PtpPrf0 currently being used for the corresponding TSN domain. SMF (114) / PCF (112) / AF is higher than the QoS requirements of PtpPrf0 of PtpPrf_n or ReqQoS received from any n-th UE 100, or PtpPrf0 being used for the TSN domain. When the time synchronization protocol profile is higher than the QoS requirements of PtpPrf0 being used for the TSN domain, the procedure for changing the QoS flow for the time synchronization protocol of each UE 100 in use for the TSN domain is shown. This means that UE1 is being serviced by setting PtpPrf0 of a certain level, and when a higher level PTP is to be serviced due to UE2 or other network circumstances, the setting is changed to PtpPrf_n of the higher level for UE1 as well. See FIG. 19 can do.

In step (7-2), when ReqQoS and PtpPrf_n from the UE 100 are higher than the QoS requirements of PtpPrf0 currently used in the TSN domain to which the UE 100 belongs, in the TSN domain based on the existing PtpPrf0 The PCF 112 detects the need to change the QoS flow for the sessions of other UEs using the QoS flow, changes the PCCrule for the sessions of each UE, and informs the SMF 114 through step 7-1. .

Change of PCCrule of PCF 112 is performed by PCF 112 itself or by notifying AF that PtpPrf_n of UE_n 100 is higher than existing QoS. Service information related to change of PCCrule is received from AF.

In step 7-1, after the PCF 112 notifies the SMF 114 of the PCCrule change, steps 10 to 19 are the same as described with reference to FIG. However, it is applied to each of the QoS flows of each UE in the corresponding TSN domain.

19 is a diagram for explaining a procedure for setting a QoS flow for a PDU session time synchronization protocol according to an embodiment of the present invention.

Referring to FIG. 19, FIG. 19 shows the overall flow in 5GS for setting a QoS flow for time synchronization of a PDU session. In step S001, the PTP profile corresponding to the DNN, S-NSSAI, and TSN domains in any one or more of SMF/PCF/AF is set as PtpProf0. In step S003, an SsnEstb (session establishment) request is received from an arbitrary UE, and in step S003-1, the DNN, S-NSSAI, and PTP profile of the corresponding session are reported and QoS flow is established for citizen communication. Determine if this is necessary At this time, in step (S003-2), any one of SMF/PCF/AF reports the DNN and S-NSSAI delivered through the AMF, and if there is no need to set the QoS flow for the time synchronization protocol, the Non-GBR default QoS flow is set, and proceeds to step S00A.

In step S005, in the case of civil communication requiring the establishment of a QoS flow for the time synchronization protocol, it is checked whether the PTP profile is included in the session establishment request message from the UE, and if the PTP profile is not included, step S005 In step S011, QoS flow is set to PtpPrf0 of the corresponding TSN domain. The QoS flow set at this time can be set as a separate QoS flow, or the default QoS flow can be set by applying GBR or higher QoS instead of Non-GBR.

If the PTP profile is included and the PTP profile from the UE (PtpPrf_n, which is the PTP profile from the nth UE, UE_n) in step S009 is lower than the existing PTP profile, PtpPrf0, step S011 Set QoS flow at PtpPrf0 level.

If PtpPrf_n from the UE has a higher requirement than PtpPrf0, which is the existing PtpProfile, in step S009, a QoS flow of PtpPrf_n level is set during the session establishment procedure in step S103, and the corresponding time synchronization protocol in step S115 Changes the QoS flow in the PDU sessions of other UEs that have been previously set up using ? Steps S011 and S013 are also described in FIG. 16 , and step S115 is also described in FIG. 17 .

On the other hand, in response to the session change request from the UE in step S203, it is checked whether the corresponding session is citizen communication in step S203-1, and in the case of a non-civic communication session, in step S203-2 The QoS flow is changed in the conventional way in response to the UE's session change request.

In step S209, the QoS parameter (QosPara_n) or PtpPrf_n of the QoS flow of the UE's session change request is higher than the current PtpPrf0 or the corresponding QoS parameter (QosPara_n(t-1), the previous QoS flow parameter of UE_n). If the requirement is high, the QoS parameters of the QoS flow for the UE's time synchronization protocol are changed during the session change (SsnMod) procedure in step S213. Also, in step S115, the QoS flow in the PDU sessions of other UEs that are previously set using the time synchronization protocol of the same TSN domain is changed to PtpPrf_n level, and PtpPrf0 is changed to PtpPrf_n in step S117.

20 is a block diagram illustrating a computing device according to an embodiment of the present invention.

Referring to FIG. 8 , a computing device 50 is a network entity of a 5G system, for example, UE 100 , DS-TT 102 , UPF 104 , NW-TT 106 , RAN 108 . , TSN AF 110 , PCF 112 , SMF 114 , AMF 116 , UDM 118 and NEF 120 , and the like. In addition, the method of generating a QoS flow for a time synchronization protocol in a wireless communication system according to embodiments of the present invention may be implemented using the computing device 50 .

The computing device 50 includes at least one of a processor 510 , a memory 530 , a user interface input device 540 , a user interface output device 550 , and a storage device 560 in communication via a bus 520 . can do. Computing device 50 may also include network interface 570 electrically connected to network 40 , such as a wireless network. Network interface 570 may transmit or receive signals with other network entities over network 40 .

The processor 510 may be implemented in various types such as an application processor (AP), a central processing unit (CPU), a graphic processing unit (GPU), and the like, and executes a command stored in the memory 530 or the storage device 560 . It may be any semiconductor device that does The processor 510 may be configured to implement the functions and methods described with reference to FIGS. 1 to 19 .

The memory 530 and the storage device 560 may include various types of volatile or non-volatile storage media. For example, the memory may include a read-only memory (ROM) 531 and a random access memory (RAM) 532 . In an embodiment of the present invention, the memory 530 may be located inside or outside the processor 510 , and the memory 530 may be connected to the processor 510 through various known means.

In addition, the QoS flow generation method for the time synchronization protocol in the wireless communication system according to the embodiments of the present invention may be implemented as a program or software executed in the computing device 50, and the program or software is stored in a computer-readable medium. can be saved.

In addition, the method for generating a QoS flow for a time synchronization protocol in a wireless communication system according to embodiments of the present invention may be implemented as hardware capable of being electrically connected to the computing device 50 .

According to the embodiments of the present invention described so far, by creating a QoS flow reflecting the PTP profile of the time synchronization protocol and allowing the time synchronization protocol to be processed as the corresponding QoS flow, the time synchronization quality is guaranteed and citizen communication is smoothly provided. can

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and common knowledge in the technical field to which the present invention pertains using the basic concept of the present invention defined in the following claims Various modifications and improved forms of those with

Claims (18)

A method of generating a QoS flow for a time synchronization protocol in a wireless communication system, the method comprising:
SMF receiving the PTP profile information from the UE together with DNN, S-NSSAI information and session ID for TSC service;
setting, by the SMF, a QoS flow for PCCrule and time synchronization protocol;
providing, by the SMF, SDF filter information for the QoS flow and the QoS flow to the UPF; and
Including the step of the SMF providing the QoS flow and QoS rule filter to the AMF
How to create a QoS flow. According to claim 1,
The step of the SMF setting the QoS flow for PCCrule and time synchronization protocol is,
Using a preset PCCrule, the SMF configures the QoS flow for the PCCrule and the time synchronization protocol. According to claim 1,
The step of the SMF setting the QoS flow for PCCrule and time synchronization protocol is,
the SMF requesting the PCF to set up a PCCrule;
receiving the configured PCCrule from the PCF; and
using the received PCCrule, the SMF setting the QoS flow for the PCCrule and the time synchronization protocol. According to claim 1,
The step of the SMF requesting the PCF to set the PCCrule,
The SMF transmitting the PTP profile information provided from the UE to the PCF together with the DNN, the S-NSSAI information and the session ID. According to claim 1,
The PTP profile information is transmitted through an Announce message, a method of generating a QoS flow. According to claim 1,
The PTP profile information includes selection information for one-step and two-step, information on a method to be used as a path delay mechanism, and information on a method to use as a transport mechanism, multicast or unicast A method of generating a QoS flow, including information on whether to use the , its address, and information on the period of each PTP message. According to claim 1,
The QoS flow includes at least one of Packet Delay Budget (PDB), Priority (Priority), Allocation and Retention Priority (ARP), and Guaranteed Flow Bit Rate (GFBR). According to claim 1,
The SDF filter and the QoS rule filter are among the multicast address of Ethernet for the time synchronization protocol, the ethertype of Ethernet for the time synchronization protocol, the multicast address of IP for the time synchronization protocol, and the UDP port for the time synchronization protocol. A method of generating a QoS flow, comprising at least one. According to claim 1,
The QoS flow is generated based on the QoS requirements for the preset PTP profile when the QoS requirements of the PTP profile information provided from the UE are lower than the QoS requirements for the preset PTP profile. method of creation. As a network entity of a 5G system operating as a TSN bridge,
network interface; and
Receive PTP profile information from UE along with DNN, S-NSSAI information and session ID for TSC service, set QoS flow for PCCrule and time synchronization protocol, and SDF filter for QoS flow and QoS flow in UPF A processor that provides information and provides the QoS flow and QoS rule filter to the AMF.
network entity. A method of generating a QoS flow for a time synchronization protocol in a wireless communication system, the method comprising:
receiving, by the SMF, a session change request including ReqQoS, which is a QoS required for a QoS flow specifyable by PktFltr for a time synchronization message, from the UE;
setting the SMF session policy;
requesting, by the SMF, to change the QoS flow for the session to the UPF; and
Comprising the step of the SMF providing the QoS flow change information for the session to the AMF
How to create a QoS flow. 12. The method of claim 11,
The step of the SMF setting the session policy comprises:
Using a preset PCCrule, the SMF setting the session policy, the QoS flow generation method comprising the step. 12. The method of claim 11,
The step of the SMF setting the session policy comprises:
The SMF requesting the PCF to change the PCCrule;
receiving the modified PCCrule from the PCF; and
using the received PCCrule, the SMF setting a session policy. 12. The method of claim 11,
If the ReqQoS and PTP profile from the UE are higher than the QoS requirements of the PTP profile currently in use in the TSN domain to which the UE belongs, another user using a QoS flow based on the PTP profile in use in the TSN domain The method of generating a QoS flow, further comprising performing a session change for sessions of UEs. 15. The method of claim 14,
The PTP profile information includes selection information for one-step and two-step, information on a method to be used as a path delay mechanism, and information on a method to use as a transport mechanism, multicast or unicast A method of generating a QoS flow, including information on whether to use the , its address, and information on the period of each PTP message. As a network entity of a 5G system operating as a TSN bridge,
network interface; and
Receives a session change request including ReqQoS, which is a QoS required for a QoS flow that can be specified with PktFltr for a time synchronization message, from the UE, sets a session policy, and requests a QoS flow change for the session to UPF, , including a processor that provides information on change of QoS flow for the session to the AMF
network entity. A method of generating a QoS flow for a time synchronization protocol in a wireless communication system, the method comprising:
receiving the SMF from the UE along with DNN, S-NSSAI information and session ID for TSC service that does not include PTP profile information;
setting, by the SMF, a QoS flow for a PCCrule and a time synchronization protocol using the PTP profile information stored by the SMF;
providing, by the SMF, SDF filter information for the QoS flow and the QoS flow to the UPF; and
Including the step of the SMF providing the QoS flow and QoS rule filter to the AMF
How to create a QoS flow. As a network entity of a 5G system operating as a TSN bridge,
network interface; and
It is provided with DNN, S-NSSAI information and session ID for TSC service that does not include PTP profile information from the UE, and sets QoS flow for PCCrule and time synchronization protocol using the PTP profile information stored by the UE. , a processor that provides SDF filter information for the QoS flow and the QoS flow to UPF, and provides the QoS flow and QoS rule filter to AMF
network entity.

Images