User Plane Device

Abstract

This session management device comprises: a reception unit that receives, from a user plane device, information about a time comparison between the TSN time of a certain TSN time domain and a 5G time, and identification information for the TSN time domain; and a transmission unit that, for each of one or more TSN streams belonging to the TSN time domain, transmits toward a base station device TSC assistance information determined on the basis of the time comparison information and the TSN stream identification information.

Description

[Technical field]

[0001] The present invention relates to a network device in a communication system. [Background technology]

[0002] 3GPP (3rd Generation Partnership Project) is currently studying a wireless communication system called 5G or NR (New Radio) (hereinafter, the wireless communication system is referred to as "5G" or "NR") in order to realize a larger system capacity, a higher data transmission speed, and a lower latency in wireless sections. In 5G, various wireless technologies are being studied to meet the requirements of achieving a throughput of 10 Gbps or more while keeping the latency in wireless sections to 1 ms or less.

[0003] For 5G, a network architecture is being considered that includes 5G Core Network (5GC), which corresponds to EPC (Evolved Packet Core), the core network in the network architecture of LTE (Long Term Evolution), and NG-RAN (Next Generation Access Network), which corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), the RAN (Radio Access Network) in the network architecture of LTE. NG-RAN is sometimes referred to as 5G-AN, RAN, or gNB.

[0004] In recent years, there has been an increasing demand for synchronous control of multiple devices in factories and the like, and standards for synchronous communication that enable such control (such as IEEE P802.1Qcc) have been defined.

[0005] The 5G system also supports Time Sensitive Communication (TSC) defined in IEEE P802.1Qcc (Non-Patent Document 1). In TSC, the 5G system functions as a Time Sensitive Networking (TSN) bridge.

[0006] In addition, the SMF provides the NG-RAN with TSCAI (TSC Assistance Information), which describes the TSC traffic characteristics. The NG-RAN gNB can grasp the TSN traffic pattern by TSCAI and perform efficient scheduling. [Prior art documents] [Non-patent literature]

[0007] [Non-Patent Document 1] 3GPP TS 23.501 V16.1.0 (2019-06) [Non-Patent Document 2] 3GPP TS 23.502 V16.1.1 (2019-06) [Non-Patent Document 3] 3GPP TS 29.244 V16.0.0 (2019-06) [Non-Patent Document 4] 3GPP TS 29.518 V15.4.0 (2019-06) [Non-Patent Document 5] 3GPP TS 38.413 V15.4.0 (2019-07) [Non-Patent Document 6] 3GPP TS 38.415 V15.2.0 (2018-12) [Non-Patent Document 7] 3GPP TS 23.503 V16.1.0 (2019-06) Summary of the Invention [Problem to be solved by the invention]

[0008] As described in Non-Patent Document 1, when drift or the like occurs between the TSN time and the 5G time in a certain TSN time domain (TSN working domain), the core NW notifies the NG-RAN of the modified TSCAI parameters. The TSN time domain may be called the "time domain". In this specification, it is assumed that the TSCAI is applied to each TSN stream.

[0009] 5G systems support multiple TSN time domains, and the above modified TSCAI only needs to be applied to the specific TSN stream to which the TSCAI should apply among the multiple TSN streams belonging to the multiple TSN time domains.

[0010] The present invention has been made in consideration of the above points, and has an object to provide a technology that makes it possible to apply TSC support information only to a specific TSN stream. [Means for solving the problem]

[0011] According to the disclosed technology, a receiving unit for receiving a request for a progress difference report from the session management device; A control unit that detects drift between an external time domain clock and a 5G system clock; A transmitter that transmits to the session management device a difference in speed between the clock of the external time domain and the 5G system clock and identification information of the external time domain. A user plane device comprising: is provided. Effect of the Invention

[0012] According to the disclosed technology, a technology is provided that allows TSC assistance information to be applied only to a specific TSN stream. [Brief description of the drawings]

[0013] [Figure 1] 1 is a diagram illustrating a communication system according to an embodiment of the present invention. [Diagram 2] FIG. 1 is a diagram illustrating a system configuration of TSN Time Synchronization. [Diagram 3] FIG. 1 illustrates a TSN bridge. [Figure 4] FIG. 1 is a diagram for explaining operation in a TSN bridge. [Diagram 5] FIG. 1 is a diagram for explaining operation in a TSN bridge. [Figure 6] FIG. 13 is a diagram showing TSC Assistance Information. [Figure 7] FIG. 11 is a diagram for explaining a processing sequence. [Figure 8] FIG. 13 is a diagram showing an example of a change to the specification (TS23.501). [Figure 9] FIG. 13 is a diagram showing an example of a change to the specification (TS23.503). [Figure 10] FIG. 13 is a diagram showing an example of a change to the specification (TS23.503). [Figure 11] FIG. 13 is a diagram showing an example of a change to the specification (TS23.503). [Figure 12] FIG. 13 is a diagram showing an example of a modification to the specification (TS29.244). [Figure 13] FIG. 13 is a diagram showing an example of a modification to the specification (TS29.244). [Figure 14] FIG. 13 is a diagram showing an example of a modification to the specification (TS29.244). [Figure 15] FIG. 13 is a diagram showing an example of a modification to the specification (TS29.244). [Figure 16] FIG. 13 is a diagram showing an example of a modification to the specification (TS29.244). [Figure 17] FIG. 13 is a diagram showing an example of a modification to the specification (TS29.244). [Figure 18] FIG. 13 is a diagram showing an example of a modification to the specification (TS29.244). [Figure 19] FIG. 13 is a diagram showing an example of a modification to the specification (TS29.244). [Figure 20] FIG. 13 is a diagram showing an example of a modification to the specification (TS29.244). [Figure 21] FIG. 13 is a diagram showing an example of a modification to the specification (TS29.244). [Figure 22] FIG. 13 is a diagram showing an example of a modification to the specification (TS29.244). [Figure 23] FIG. 13 is a diagram showing an example of a modification to the specification (TS29.244). [Figure 24] FIG. 13 is a diagram showing an example of a modification to the specification (TS29.244). [Diagram 25] FIG. 13 is a diagram showing an example of a modification to the specification (TS29.244). [Figure 26] FIG. 13 is a diagram showing an example of a modification to the specification (TS29.244). [Figure 27] FIG. 13 is a diagram showing an example of a modification to the specification (TS29.244). [Figure 28] FIG. 13 is a diagram showing an example of a change to the specification (TS23.502). [Figure 29] FIG. 13 is a diagram showing an example of a change to the specification (TS23.502). [Diagram 30] FIG. 13 is a diagram showing an example of a change to the specification (TS23.502). [Diagram 31] This is a diagram showing an example of a change to the specification (TS38.413). [Diagram 32] This is a diagram showing an example of a change to the specification (TS38.413). [Diagram 33] This is a diagram showing an example of a change to the specification (TS38.413). [Diagram 34] This is a diagram showing an example of a change to the specification (TS38.413). [Diagram 35] This is a diagram showing an example of a change to the specification (TS38.413). [Diagram 36] This is a diagram showing an example of a change to the specification (TS38.413). [Figure 37] This is a diagram showing an example of a change to the specification (TS38.413). [Figure 38] This is a diagram showing an example of a change to the specification (TS38.415). [Figure 39] This is a diagram showing an example of a change to the specification (TS38.415). [Diagram 40] This is a diagram showing an example of a change to the specification (TS38.415). [Diagram 41] 2 is a diagram illustrating an example of a functional configuration of a base station device 30 according to an embodiment of the present invention. [Diagram 42] A figure showing an example of the functional configuration of AMF 20 in the embodiment of the present invention. [Diagram 43] 2 is a diagram illustrating an example of a functional configuration of an SMF 40 according to an embodiment of the present invention. [Diagram 44] 2 is a diagram illustrating an example of a functional configuration of a UPF 50 according to an embodiment of the present invention. [Diagram 45] A diagram showing an example of the hardware configuration of a base station device 30, an AMF 20, an SMF 40, and a UPF 50 in an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0015] In the operation of the communication system according to the embodiment of the present invention, an existing technology may be used as appropriate. The existing technology may be, for example, the existing LTE or the existing 5G, but is not limited to the existing LTE or the existing 5G.

[0016] In addition, in the following explanation, we will use node names, signal names, etc. currently described in the 5G standard (or LTE standard), but node names, signal names, etc. having similar functions may be called by different names.

[0017] (System configuration example) Fig. 1 is a diagram for explaining a communication system (which may be called a communication network) in an embodiment of the present invention. As shown in Fig. 1, the communication system is composed of UE 10 (which may be called user equipment 10 or terminal 10) and multiple network nodes. In the following, it is assumed that one network node corresponds to each function, but multiple functions may be realized by one network node, or multiple network nodes may realize one function. In addition, the "connection" described below may be a logical connection or a physical connection.

[0018] 1, the UPF 50, the AMF 20, and the SMF 40 are examples of network nodes (which may be called network devices) constituting a core network of a communication system (5G in this case). Communication between the RAN 30 and the UPF 50 is performed via the core network.

[0019] The RAN (Radio Access Network) 30 is a network node having a radio access function, and is connected to the UE 10, the AMF (Access and Mobility Management Function) 20, and the UPF (User plane function) 50. The RAN 30 may be referred to as a gNB 30 or a base station device 30.

[0020] The AMF 20 is a network node having functions such as a RAN interface termination, a NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, mobility management, etc. The AMF 20 may be called an access mobility management device.

[0021] The UPF 50 is a network node having functions such as a PDU (Protocol Data Unit) session point for the outside that interconnects with the DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) handling, and transmits and receives user data. The UPF 50 and the DN constitute a network slice. In the communication network according to the embodiment of the present invention, a plurality of network slices are constructed.

[0022] In the example of Fig. 1, as an example, one UPF 50 corresponds to one network slice, but one UPF 50 may operate multiple network slices. Also, the UPF 50 may be called a user plane device.

[0023] Furthermore, the UPF 50 is physically one or more computers (servers, etc.), and considers multiple resources obtained by logically integrating and dividing the hardware resources (CPU, memory, hard disk, network interface, etc.) of the computer as a resource pool, and each resource in the resource pool can be used as a network slice. The UPF 50 operates a network slice by, for example, managing the correspondence between the network slice and the resource, starting and stopping the resource, and monitoring the operating status of the resource.

[0024] The AMF 20 is connected to the UE 10, the RAN 30, a session management function (SMF) 40, a network slice selection function (NSSF), a network exposure function (NEF), a network repository function (NRF), an authentication server function (AUSF), a policy control function (PCF), and an application function (AF). The AMF, SMF, NSSF, NEF, NRF, AUSF, PCF 70, and AF 60 are network nodes that are mutually connected via interfaces Namf, Nsmf, Nnssf, Nnef, Nnrf, Nausf, Npcf, and Naf based on their respective services. In this embodiment, the AF 60 corresponds to a TSN AF, which will be described later.

[0025] The SMF 40 is a network node having functions such as session management, IP (Internet Protocol) address allocation and management for UEs, a DHCP (Dynamic Host Configuration Protocol) function, an ARP (Address Resolution Protocol) proxy, a roaming function, etc. The SMF 40 may be called a session management device.

[0026] The NEF is a network node having a function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node having functions such as selecting a network slice to which the UE connects, determining an allowed NSSAI (Network Slice Selection Assistance Information), determining an NSSAI to be set, and determining an AMF set to which the UE connects. The PCF 70 is a network node having a function of controlling network policies. The AF 60 is a network node having a function of controlling application servers.

[0027] (Basic operation) The communication system (5G system) according to the present embodiment supports TSN time synchronization as shown in FIG. 2 (Figure 5.27.1-1 in Non-Patent Document 1). A 5G system that supports TSN time synchronization corresponds to a "time aware system" of IEEE802.1AS. In the 5G system, only the TSN translator (TT) at the edge supports the operation of IEEE802.1AS, and the UE, gNB, UPF, NW-TT (Network-side TSN translator), and DS-TT (Device-side TSN translator) are synchronized with the 5G GM (5G internal system clock).

[0028] As shown in Figure 3 (Figure 4.4.8.2-1 in Non-Patent Document 1), the 5G system functions as a TSN bridge. Note that Figure 3 shows a TSN AF60, which is an application node related to TSN.

[0029] An example of a method for distributing a TSN clock will be described with reference to Fig. 4. A gPTP message is used to distribute the TSN clock. The gPTP message includes a timestamp (precise origin timestamp) at the time of sending the gPTP message, a correction field, etc.

[0030] A gPTP message sent from a TSN end station or the like in a certain TSN time domain is received by the UPF 50, and an ingress timestamp (TSi) is added to the gPTP message by the NW-TT in the UPF 50. The NW-TT may be a function built into the UPF 50, or may be a function outside the UPF 50.

[0031] The gPTP message is transmitted to the UE 10 using a PDU session for communication of the UE 10. The UE 10 transmits the received gPTP message to the DS-TT, which generates an egress timestamp (TSe) for the gPTP message and calculates the residence time of the gPTP message in the 5G system as "TSe-TSi". The DS-TT puts the residence time in the correction field of the gPTP message and transmits it to a TSN end station or the like. The DS-TT may be a function built into the UE 10 or may be a function outside the UE 10.

[0032] Regardless of the number of TSN time domains, one PDU session is used for transmitting gPTP messages per UPF and per UE. Figure 5 shows an example in which gPTP messages for two TSN time domains are transmitted in one PDU session. Since the gPTP message includes a domain number for identifying the TSN time domain, the end station receiving the gPTP message can identify which TSN time domain the gPTP message belongs to by the domain number.

[0033] The above TSN clock and timestamp distribution is performed between the UE 10 and the UPF 50 for each TSN time domain. If the UE 10 is connected to multiple TSN time domains via one UPF 50, gPTP messages for all TSN time domains are sent to the UE 10 in the same PDU session.

[0034] The above example focuses on gPTP messages. In reality, packets other than gPTP messages (e.g., a collection of packets transmitted at a certain period) form a TSN stream, and the TSN stream is transmitted from a TSN end station. One or more TSN streams belong to a certain TSN time domain. A TSN stream may also be called a TSC stream.

[0035] (About TSCAI) For example, when a QoS flow is established, TSCAI (TSC Assistance Information) describing TSC traffic characteristics is provided from the SMF 40 to the RAN 30 via the AMF 20. The gNB, which is the RAN 30 in this embodiment, can grasp the TSN traffic pattern by the TSCAI and perform efficient scheduling.

[0036] An example of a TSCAI is shown in Figure 6 (Table 5.27.2-1 in Non-Patent Document 1). As shown in Figure 6, the TSCAI includes Flow Direction, Periodicity, and Burst Arrival Time. Flow Direction indicates whether the target TSC flow (in this embodiment, the "TSC flow" may be rephrased as a TSN stream) is uplink or downlink. Periodicity indicates the time interval (period) between two bursts in a series of traffic of the TSN stream. Burst Arrival Time indicates the arrival time of the first data burst of a series of traffic to the RAN 30 in the uplink or downlink.

[0037] In this embodiment, the Burst Arrival Time and Periodicity are based on the 5G clock (5G time), and the SMF 40 performs mapping from the TSN clock, which is the basis of the TSN stream, to the 5G clock for the Burst Arrival Time and Periodicity. This mapping may be performed by the TSN AF 60.

[0038] For example, in a certain TSN time domain, assume that the time of the 5G clock (e.g., the clock provided in the UPF 50) is ahead of the time of the TSN clock (e.g., the clock provided in the TSN end station) by ΔT. In this case, if the Burst Arrival Time of the TSN clock is T, the SMF 40 sets the Burst Arrival Time of the 5G clock to T+ΔT.

[0039] In the conventional technology described in Non-Patent Document 1 and the like, when a drift (e.g., the above ΔT has changed) occurs between the TSN time (TSN time) and the 5G time (5G time) in a certain TSN time domain, the UPF 50 notifies the SMF 40 of the offset, and the SMF 40 notifies the RAN 30 of the TSCAI parameter corrected based on the offset. The TSCAI parameter here is, for example, Burst Arrival Time, but is not limited to Burst Arrival Time. Also, the "offset" is the difference between the TSN time and the 5G time (corrected ΔT), but is not limited to this. For example, the "offset" may be the amount of deviation from ΔT before correction.

[0040] When a UE 10 is connected to multiple TSN time domains via one UPF 50, gPTP messages of all TSN time domains are sent to the UE 10 via one and the same PDU session. Since there is no reason to treat each of these multiple TSN time domains with different QoS, it is assumed that in practice, all gPTP messages of all these TSN time domains are sent via one QoS flow. Here, a gPTP message belonging to a single TSN time domain is an example of a TSN stream. It is also conceivable that multiple TSN streams of multiple TSN time domains are sent via one QoS flow, even if the TSN stream is formed of packets other than gPTP messages.

[0041] The above modified TSCAI parameters need to be applied only to the specific TSN stream to which they should be applied. However, since multiple TSN streams in multiple TSN time domains may belong to one QoS flow, the conventional technology cannot apply the modified TSCAI parameters only to a specific TSN stream. When applying TSCAI to each TSN stream as in the present embodiment, the above problem occurs not only in the modified TSCAI parameters but also in the notification of the TSCAI parameters before modification.

[0042] In addition, the conventional technology described in Non-Patent Document 1 etc. takes into account the drift between TSN time and 5G time in a certain TSN time domain, but does not take into account the change in the difference in the progress, so there is also the issue that the periodicity cannot be corrected.

[0043] In this embodiment, in order to solve the above problem, the configuration of TSCAI can be set for each QoS flow + TSN stream (TSN stream identification information) on N2, and the TSN stream identification information can be set in the PDU Session user plane protocol on N3. In addition, the change in the progress difference is taken into consideration. This technology will be described in detail below as an example.

[0044] (Example) In this embodiment, one QoS flow includes one or more TSN streams that belong to one or more TSN time domains. For example, one QoS flow may include TSN streams A-1 and A-2 that belong to TSN time domain A, and TSN streams B-1 and B-2 that belong to TSN time domain B.

[0045] As explained above, TSCAI is information for each TSN stream. For example, TSCAI_A-1 is provided for TSN stream A-1, and TSCAI_A-2 is provided for TSN stream A-2.

[0046] The SMF 40 determines the TSCAI parameters based on, for example, information acquired from the TSN AF 60. The SMF 40 may determine the TSCAI parameters based on information (such as an offset) reported from the UPF 50.

[0047] For example, the TSN AF 60 transmits, for a certain TSN stream, the TSN time domain number to which the TSN stream belongs and the TSCAI in TSN time to the SMF 40 via the PCF 70. The SMF 40 holds and manages association information (correspondence information) between the TSN stream identifier and the time domain number for each UE and UPF. An example of the processing flow of this embodiment under such a premise is shown in FIG. 7.

[0048] In S101, the TSN AF 60 transmits, for example, a domain number related to a TSN stream to be transmitted and a TSCAI at the TSN time to the PCF 70. In S102, the PCF 70 transmits the domain number and the TSCAI at the TSN time received from the TSN AF 60 to the SMF 40 as a PCC rule.

[0049] In S103, the SMF 40 holds (manages) information on the association (binding) between the TSN stream identifier and the time domain number for each TSN stream including the TSN stream. This association is managed for each "1UE-1UPF." In addition, the SMF 40 maps the TSCAI in TSN time to the TSCAI in 5G time, and holds (manages) the TSCAI (5G time) in association with the corresponding TSN stream identifier.

[0050] In S104, the SMF 40 transmits a message to the UPF 50 requesting a report of the offset (the time difference between the 5G time and the TSN time) and the difference in the progress between the 5G time and the TSN time (hereinafter, referred to as the "difference in progress"). As will be described later, the difference in progress is called the "cumulative rateRatio." The offset and the difference in progress may be collectively referred to as time comparison information.

[0051] The above message is, for example, a PFCP Session Establishment Request when a PDU session is established or a PFCP Session Modification Request when a PDU session is modified, but is not limited to these. Also, UPF 50 may report the offset and the difference in the progress to SMF 40 at its own discretion without making a request of S104.

[0052] In the following description, the offset report when drift is detected or the lead difference report when a change in the lead difference is detected is described, but this is an example. The UPF 50 may report the offset, the lead difference, or both for each TSN time domain detected in the corresponding PDU session even if neither drift detection nor lead difference change detection is performed.

[0053] In S105, the UPF 50 detects drift between the TSN time and the 5G time in a certain TSN time domain in a corresponding PDU session for the UE 10. Or, in S105, the UPF 50 detects a change in the difference in advance in a certain TSN time domain in a corresponding PDU session for the UE 10. Or, in S105, the UPF 50 detects drift and a change in the difference in advance in a certain TSN time domain in a corresponding PDU session for the UE 10.

[0054] Any method may be used to detect the drift. For example, the UPF 50 may detect the drift based on the fluctuation of the difference between the timestamp given by the NW-TT to the gPTP message in the TSN time domain and the TSN source timestamp, or may detect the drift based on information from the TSN AF 60, or may detect the drift by other methods. In addition, any method may be used to detect the change in the difference in the advance, and for example, the change in the difference in the advance may be detected based on the timestamp.

[0055] In S106, the UPF 50 obtains the number (domain number) of the TSN time domain in which the drift or the change in the lead difference (or both) was detected from the gPTP message, and transmits a message including the domain number, offset, and lead difference to the SMF 40. This message is, for example, a PFCP Session Report Request. The domain number is extracted from the corresponding gPTP message. Note that the UPF 50 may transmit the domain number and offset when it detects a drift, and transmit the domain number and lead difference when it detects a change in the lead difference.

[0056] The SMF 40 that has received the message determines (this "determination" also includes "updating") the TSCAI parameters (e.g., Burst Arrival Time and Periodicity) for all TSN streams (one or more TSN streams) for the UE 10 that are bound to the domain number received from the UPF 50 based on the offset and the difference in the advance, and transmits a message including the TSCAI parameters and TSN stream identifiers for each TSN stream to the AMF 20 (S107). This transmission is performed, for example, by step 3b (Namf_Communication_N1N2MessageTransfer) of PDU session modification (Non-Patent Document 2, Figure 4.3.3.2-1).

[0057] In S108, the AMF 20 transmits a message including a TSN stream identifier and TSCAI parameters (e.g., Burst Arrival Time, Periodicity) for each TSN stream to which the TSCAI parameters are applied to the RAN 30. This transmission is performed, for example, by step 4 (N2 PDU Session Request) of PDU session modification (Non-Patent Document 2, Figure 4.3.3.2-1).

[0058] It is assumed that, based on the TSCAI received before the execution of S108 shown in Fig. 7, the control unit of the RAN 30 prepares (allocates) a time slot for transmitting data of Burst Arrival Time=T, period P, and size per period S in a certain TSN stream in a certain QoS flow in a PDU session to the UE 10 or the UPF 50. In this case, if the RAN 30 receives Burst Arrival Time=T+ΔD and period P+ΔP for the TSN stream in S108 in Fig. 7, the control unit of the RAN 30 shifts the start of the above time slot to T+ΔD and sets the period to P+ΔP for the TSN stream and allocates the time slot.

[0059] Note that "allocating" means reserving the time slot for transmitting the burst data. When the burst data arrives from the UPF 50 or the UE 10, the transmitter of the RAN 30 transmits the burst data to the UE 10 or the UPF 50 in the reserved time slot.

[0060] (Example of specification changes) Next, an example of modification of the specification (standard) corresponding to the above flow will be described. The communication system of this embodiment operates, for example, according to the modified specification.

[0061] FIG. 8 shows changes from Non-Patent Document 1 (excerpt from TS38.501). In particular, as described in "In the case of change of the cumulative rateRatio between TSN time and 5G time, the UPF updates the cumulative rateRatio to SMF," it is stipulated that when the cumulative rateRatio (difference in progress) changes, the UPF 50 updates the cumulative rateRatio for the SMF 40. In addition, as described in "The TSCAI is signalled to the 5G-AN per TSN stream. This applies also to the case when multiple TSN streams are forwarded via the same QoS flow in the same PDU session," it is stipulated that the TSCAI is notified to the 5G-AN for each stream.

[0062] Also, as described in the section "To address each individual drift and change of the cumulative rateRatio between each TSN time and 5G time when supporting multiple TSN working domains, the UPF updates the offset and the cumulative rateRatio to SMF per TSN working domain. Then the SMF identifies TSN streams belonging to each TSN working domain within the same UE and the same UPF, calculates revised TSCAIs, and triggers PDU session modification(s)," it is specified that the UPF50 updates the offset and cumulative rateRatio for the SMF40 for each TSN time domain, and the SMF40 identifies the TSN streams belonging to each TSN time domain within the same UE and the same UPF, calculates updated TSCAIs, and triggers PDU session modification(s).

[0063] Figures 9 to 11 show examples of specification changes for the parts corresponding to S101 and S102 in Figure 7, and show changes from Non-Patent Document 7 (excerpt from TS23.503). Figure 9 shows an excerpt from 5.3.1 Interactions between PCF and AF, and as described in "TSN AF provides burst arrival time (in reference to TSN GM), periodicity (in reference to TSN GM), flow direction, and time domain identifier needed for TSCAI determination (as described in clauses 5.27 and 5.28 of TS 23.501 [2])," TSN AF 60 provides burst arrival time (in reference to TSN GM), periodicity (in reference to TSN GM), flow direction, and time domain identifier needed for TSCAI determination.

[0064] Fig. 10(a) shows the TSN AF Parameters input from the TSN AF 60 to the PCF 70, and Fig. 10(b) shows the TSN AF QoS container provided from the PCF 70 to the SMF 40. Fig. 11 explains the TSN AF container.

[0065] 12 to 27 show examples of specification changes in the parts corresponding to S104 and S105 in FIG. 7, and show changes from Non-Patent Document 3 (an excerpt from TS29.244).

[0066] Figure 12 specifies Reporting of the offset and the cumulative rateRatio between TSN time and 5G time to the SMF. The SMF 40 can request the UPF 50 to start or stop reporting the offset between TSN time and 5G time and the cumulative rateRatio in a PFCP Session Establishment Request or a PFCP Session Modification Request. Upon receiving the request for reporting, the UPF 50 reports, for example, the offset value for which drift has been detected and the cumulative rateRatio for which a change has been detected for all domain numbers together with the corresponding domain numbers to the SMF 40 by the PFCP Session Report procedure. Details are as shown in Figure 12.

[0067] Figure 13 shows the details of the information elements of the PFCP Session Establishment Request, with the addition of Create PTR. Figure 14 shows the details of the Create PDR IE, with the addition of PTR ID. Figure 15 shows the Ethernet Packet Filter IE within PFCP Session Establishment Request, showing the addition of EtherType. This EtherType IE is the key for the UPF50 to perform DPI to detect values ​​or fields in the gPTP message. Figure 16 shows the details of the Create PTR IE within PFCP Session Establishment Request.

[0068] Figure 17 shows information elements of a PFCP Session Modification Request, where Remove PTR, Create PTR, and Update PTR are added. Figure 18 shows details of an Update PTR IE within a PFCP Session Modification Request, where a PTR ID is added. Figure 19 shows details of the Update PTR IE, and Figure 20 shows details of the Remove PTR IE.

[0069] Figure 21 shows information elements of a PFCP Session Report Request, to which a PTP Report is added. Figure 22 shows details of the PTP Report IE, which specifies that a set of a domain number, offset, and cumulative rateRatio is notified as time comparison information. Figures 23 to 27 show details of Report Type, EtherType, PTR ID, PTP Reporting Triggers, Domain Number, Time Offset, and Time RateRatio.

[0070] Figures 28 to 30 show modifications from Non-Patent Document 2 (excerpt from TS23.502). Figure 28 shows a modification of 4.3.2.2.1 of Non-Patent Document 2, and a modification of step 10a of UE-requested PDU Session Establishment shown in Figure 4.3.2.2.1-1. As shown in Figure 28, when SMF 40 decides to use TSCAI in the PDU session, it includes rules for detecting offset drift and cumulative rateRatio change in N4 Session Establishment / Modification Request.

[0071] FIG. 29 shows a modification of step 1d of UE or network requested PDU Session Modification shown in Figure 4.3.3.2-1 of Non-Patent Document 2. As shown in FIG. 29, for example, when UPF 50 reports drift or cumulative rateRatio change, SMF requested modification is triggered to update TSCAI.

[0072] FIG. 30 shows a modification of step 2a of UE or network requested PDU Session Modification shown in Figure 4.3.3.2-1 of Non-Patent Document 2. When SMF 40 determines to use TSCAI in the PDU session, it includes rules for drift and cumulative rateRatio change detection in the N4 Session Establishment / Modification Request.

[0073] For the notification of the domain number and the TSCAI parameters from the SMF 40 to the AMF 20, for example, N1N2MessageTransfer shown in step 11 of Figure 4.3.2.2.1-1 (UE-requested PDU Session Establishment) and step 3b of Figure 4.3.3.2-1 (UE or network requested PDU Session Modification) in Non-Patent Document 2 (TS23.502) is used. Specifically, N1N2MessageTransferReqData including the TSN stream identifier and the TSCAI parameters is sent from the SMF 40 to the AMF 20. As will be described later, the TSN stream identifier and the TSCAI parameters are sent as a list having a "pair of TSN stream identifier and TSCAI parameter" for each of one or more TSN stream identifiers. However, sending in the form of a list is just one example, and they may be sent in a manner other than a list.

[0074] As shown in 6.1.6.2.18 of TS29.518, N1N2MessageTransferReqData contains N2InfoContainer. As shown in 6.1.6.2.15, N2InfoContainer contains N2SmInformation. As shown in 6.1.6.2.26, N2SmInformation contains N2InfoContent. As shown in 6.1.6.2.27, N2InfoContent contains ngapData.

[0075] Furthermore, as shown in 6.1.6.4.3.2, there is a description that non-patent document 5 (TS38.413) should be referred to for PDU Session Resource Setup Request Transfer IE or PDU Session Resource Modify Request Transfer IE, which are the contents of NGAP IE. The operation of this embodiment complies with non-patent document 4 (TS29.518) and also complies with the specification modified from non-patent document 5 (TS38.413).

[0076] Figures 31 to 35 show a first modification from Non-Patent Document 5 (excerpt from TS38.413). Figure 31 shows a modification in 8.2.1.2 Successful Operation of PDU session resource setup executed between the AMF 20 and the RAN 30. In the PDU Session Resource Setup Request transmitted from the AMF 20 to the RAN 30, if a Traffic Characteristics list IE is included in the PDU Session Resource Setup Request Transfer IE of the PDU SESSION RESOURCE SETUP REQUEST message for each QoS flow requesting setup, the RAN 30 must take the Traffic Characteristics list IE into consideration.

[0077] Figure 32 shows the modified part in 8.2.3.2 Successful Operation of PDU session resource modify executed between AMF 20 and RAN 30. In the PDU Session Resource Modify Request transmitted from AMF 20 to RAN 30, if the Traffic Characteristics list IE is included in the PDU Session Resource Modify Request Transfer IE of the PDU SESSION RESOURCE MODIFY REQUEST message, RAN 30 must take the Traffic Characteristics list IE into account.

[0078] Figure 33 shows the details of the PDU Session Resource Setup Request Transfer IE, and the description of Traffic Characteristics is described. Figure 34 shows that the Traffic Characteristic item in the Traffic Characteristics list consists of Tsn Stream identifier and Traffic Characteristic. Figure 35 shows the details of Tsn Stream identifier and Traffic Characteristic.

[0079] Figures 36 and 37 show a second modification from Non-Patent Document 5 (an excerpt from TS38.413). Figure 36 shows that a TSC Assistance information list including TSC Assistance information for each TSN stream is included in the GBR QoS Flow Information transmitted from the AMF 20 to the RAN 30. Figure 37 shows details of the TSC Assistance Information and the TSN Stream identifier.

[0080] 38 to 40 show an example of modification from Non-Patent Document 6 (excerpt from TS38.415). As shown in FIG. 38, in this embodiment, a Tsn Stream identifier (TSI) field can be included in the DL PDU SESSION INFORMATION frame. The RAN 30 can identify the TSN stream to which the received packet belongs by the TSI. FIG. 39 shows the DL PDU SESSION INFORMATION (PDU Type 0) Format. FIG. 40 shows the details of the Tsn Stream identifier (TSI).

[0081] It should be noted that the modifications shown in Figures 38 to 40 are not essential. Even without making the modifications shown in Figures 38 to 40, RAN 30 can grasp the Burst Arrival Time, Periodicity, and the like for each TSN stream based on the TSCAI for each TSN stream, and can therefore process packets for each TSN stream.

[0082] As described above, according to this embodiment, it is possible to apply support information for time-sensitive communication only to a specific TSN stream.

[0083] (Device configuration) Next, examples of functional configurations of the base station device 30 corresponding to the RAN 30, the access mobility management device 20 corresponding to the AMF 20, the session management device 40 corresponding to the SMF 40, and the user plane device 50 corresponding to the UPF 50, which perform the processes and operations described above, will be described. Note that the TSN AF 60 and the PCF 70 also have the same configurations as those shown in Figs. 41 to 45.

[0084] <Base station device 30> Fig. 41 is a diagram showing an example of the functional configuration of the base station device 30. As shown in Fig. 41, the base station device 30 has a transmitting unit 310, a receiving unit 320, a setting unit 330, and a control unit 340. The functional configuration shown in Fig. 41 is merely an example. The functional divisions and names of the functional units may be any as long as they can execute the operations related to the embodiment of the present invention.

[0085] The transmitting unit 310 includes a function of generating a signal to be transmitted and transmitting the signal to the terminal side (Uu side) / core network side. The receiving unit 320 includes a function of receiving various signals from the terminal side (Uu side) / core network side and acquiring, for example, information of a higher layer from the received signals. The transmitting unit 310 and the receiving unit 320 may be referred to as a transmitter and a receiver, respectively.

[0086] The setting unit 330 stores the setting information in a storage device (memory unit) and reads it out from the storage device as necessary. The control unit 340 controls the base station device 30.

[0087] For example, the receiving unit 320 receives a message including TSC support information and identification information of a TSN stream to which the TSC support information should be applied from a network device, and the transmitting unit 310 performs data transmission based on the TSC support information.

[0088] <Access mobility management device 20> Fig. 42 is a diagram showing an example of the functional configuration of the access mobility management device 20. As shown in Fig. 42, the access mobility management device 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 42 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention.

[0089] The transmitting unit 210 includes a function of generating a signal to be transmitted and transmitting the signal to a network. The receiving unit 220 includes a function of receiving various signals and acquiring, for example, information of a higher layer from the received signals. The transmitting unit 210 and the receiving unit 220 may be referred to as a transmitter and a receiver, respectively.

[0090] The setting unit 230 stores the setting information in a storage device (storage unit) and reads it out from the storage device as necessary. The control unit 240 controls the access mobility management device 20.

[0091] <Session Management Device 40> Fig. 43 is a diagram showing an example of a functional configuration of session management device 40. As shown in Fig. 43, session management device 40 has a transmitting unit 410, a receiving unit 420, a setting unit 430, and a control unit 440. The functional configuration shown in Fig. 43 is merely an example. The functional divisions and names of the functional units may be any as long as they can execute the operations related to the embodiment of the present invention.

[0092] The transmitting unit 410 includes a function of generating a signal to be transmitted and transmitting the signal to a network. The receiving unit 420 includes a function of receiving various signals and acquiring, for example, information of a higher layer from the received signals. The transmitting unit 410 and the receiving unit 420 may be referred to as a transmitter and a receiver, respectively.

[0093] The setting unit 430 stores the setting information in a storage device (memory unit) and reads it out from the storage device as necessary. The control unit 440 controls the session management device 40.

[0094] <User Plane Device 50> Fig. 44 is a diagram showing an example of the functional configuration of the user plane device 50. As shown in Fig. 44, the user plane device 50 has a transmitting unit 510, a receiving unit 520, a setting unit 530, and a control unit 540. The functional configuration shown in Fig. 44 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention.

[0095] The transmitting unit 510 includes a function of generating a signal to be transmitted and transmitting the signal to a network. The receiving unit 520 includes a function of receiving various signals and acquiring, for example, information of a higher layer from the received signals. The transmitting unit 510 and the receiving unit 520 may be referred to as a transmitter and a receiver, respectively.

[0096] The setting unit 530 stores the setting information in a storage device (memory unit) and reads it out from the storage device as necessary. The control unit 540 controls the user plane device 50.

[0097] (Hardware configuration) The block diagrams (FIGS. 41 to 44) used in the description of the above-mentioned embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by using wires, wirelessly, etc.). The functional blocks may be realized by combining the one device or the multiple devices with software.

[0098] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, mapping, assignment, etc. For example, a functional block (component) that performs the function of transmission is called a transmitting unit or a transmitter. In either case, as described above, there is no particular limitation on the method of realization.

[0099] For example, the base station device 30, the access mobility management device 20, the session management device 40, the user plane device 50, the TSN AF 60, the PCF 70, and the like in an embodiment of the present disclosure may function as a computer that performs the processing of the present disclosure. FIG. 41 is a diagram showing an example of a hardware configuration of the base station device 30, the access mobility management device 20, the session management device 40, the user plane device 50, the TSN AF 60, the PCF 70, and the like in an embodiment of the present disclosure. The above-mentioned base station device 30, the access mobility management device 20, the session management device 40, the user plane device 50, and the like may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. Note that the base station device 30, the access mobility management device 20, the session management device 40, the user plane device 50, and the like may each be a virtual machine.

[0100] In the following description, the term "apparatus" may be interpreted as a circuit, a device, a unit, etc. The hardware configurations of the base station apparatus 30, the access mobility management apparatus 20, the session management apparatus 40, the user plane apparatus 50, etc. may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0101] Each function in the base station device 30, the access mobility management device 20, the session management device 40, the user plane device 50, etc. is realized by loading a specific software (program) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communications by the communication device 1004, and controls at least one of the reading and writing of data in the memory device 1002 and the auxiliary memory device 1003.

[0102] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control units 340, 440, 540, etc. may be realized by the processor 1001.

[0103] Furthermore, the processor 1001 reads out a program (program code), software module, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and executes various processes according to the program. The program used is a program that causes a computer to execute at least a part of the operations described in the above-mentioned embodiment. For example, the control unit of each device may be realized by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-mentioned various processes have been described as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from a network via a telecommunication line.

[0104] The storage device 1002 is a computer-readable recording medium, and may be configured by at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), a Random Access Memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The storage device 1002 can store a program (program code), software modules, etc. that are executable to implement a communication method according to an embodiment of the present disclosure.

[0105] The auxiliary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of the storage device 1002 and the auxiliary storage device 1003.

[0106] The communication device 1004 is hardware (transmission and reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to realize at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, a transmission and reception antenna, an amplifier unit, a transmission and reception unit, a transmission line interface, etc. may be realized by the communication device 1004. The transmission and reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated from each other.

[0107] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0108] In addition, each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0109] Furthermore, the base station device 30, the access mobility management device 20, the session management device 40, the user plane device 50, etc. may be configured to include hardware such as a microprocessor, a digital signal processor (DSP: Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), an FPGA (Field Programmable Gate Array), etc., and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0110] (Summary of the embodiment) According to this embodiment, at least a session management device, a user plane device, and an access mobility management device as shown in the following items 1 to 6 are provided. (Section 1) A receiving unit that receives time comparison information between a TSN time and a 5G time of a certain TSN time domain and identification information of the TSN time domain from a user plane device; a transmitter that transmits, for each of the one or more TSN streams belonging to the TSN time domain, TSC support information determined based on the time comparison information and identification information of the TSN stream to a base station device; A session management device comprising: (Section 2) The time comparison information is a time offset between a TSN time and a 5G time in the TSN time domain, a difference in advance between a TSN time and a 5G time in the TSN time domain, or both the time offset and the difference in advance. 2. A session management device according to claim 1. (Section 3) When a drift or a change in the difference in the advance between the TSN time and the 5G time of the TSN time domain is detected in the user plane device, the receiving unit receives the time comparison information and the identification information of the TSN time domain. 3. A session management device according to claim 1 or 2. (Section 4) A control unit that detects a drift or change in the difference in lead between a TSN time and a 5G time in a TSN time domain; a transmission unit that transmits time comparison information between the TSN time and 5G time of the TSN time domain and identification information of the TSN time domain to a session management device when the drift or the change in the difference in the advancement is detected; A user plane device comprising: (Section 5) A receiving unit that receives TSC support information and identification information of a TSN stream to which the TSC support information is to be applied from a session management device; a transmitter that transmits a message including the TSC support information and identification information of the TSN stream to which the TSC support information should be applied to a base station device; An access mobility management device comprising: (Section 6) The transmitter transmits to the base station device a message including a list having TSC support information and identification information of the TSN stream to which the TSC support information should be applied, for each of one or more TSN streams. 2. An access mobility management device as set forth in claim 1.

[0111] Any of the first to sixth aspects provides a technique that enables the TSC assistance information to be applied only to a specific TSN stream.

[0112] (Supplementary embodiment) Although the embodiment of the present invention has been described above, the disclosed invention is not limited to such an embodiment, and those skilled in the art will understand various modifications, modifications, alternatives, replacements, and the like. Although the description has been given using specific numerical examples to facilitate understanding of the invention, unless otherwise specified, those numerical values ​​are merely examples and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be used in combination as necessary, and matters described in one item may be applied to matters described in another item (as long as there is no contradiction). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operations of multiple functional units may be physically performed by one part, or the operations of one functional unit may be physically performed by multiple parts. The order of the processing procedures described in the embodiment may be changed as long as there is no contradiction. For convenience of explaining the processes, the base station device 30, the access mobility management device 20, the session management device 40, the user plane device 50, etc. have been explained using functional block diagrams, but such devices may be realized by hardware, software, or a combination thereof. Software operated by a processor included in each device according to the embodiment of the present invention may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, etc.

[0113] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination of these. Furthermore, the RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0114] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other suitable systems, and next-generation systems extended based on these. In addition, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G, etc.) may be applied.

[0115] The steps, sequences, flowcharts, etc. of each aspect / embodiment described herein may be reordered unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0116] In this specification, specific operations that are described as being performed by the base station device 30, the access mobility management device 20, the session management device 40, the user plane device 50, etc. may be performed by other nodes in some cases.

[0117] The information or signals described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0118] The input and output information may be stored in a specific location (e.g., memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added to. The output information may be deleted. The input information may be transmitted to another device.

[0119] In the present disclosure, the determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0120] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0121] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired and / or wireless technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.

[0122] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0123] In addition, the terms described in this disclosure and the terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Also, a signal may be a message. Also, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0124] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0125] In addition, the information, parameters, etc. described in the present disclosure may be represented using absolute values, may be represented using relative values ​​from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by an index.

[0126] The names used for the above-mentioned parameters are not limiting in any way. Moreover, the formulas using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any way.

[0127] In the present disclosure, terms such as "base station (BS)", "wireless base station", "base station device", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", "component carrier", etc. may be used interchangeably. A base station may also be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, etc.

[0128] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or a base station subsystem that provides communication services in this coverage.

[0129] In this disclosure, the terms "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal", etc. may be used interchangeably.

[0130] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0131] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may include a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0132] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), and the like. In addition, "judgment" and "decision" can include considering resolving, selecting, choosing, establishing, comparing, etc., to be a "judgment" or "decision." In other words, "judgment" and "decision" can include considering some action to be a "judgment" or "decision." In addition, "judgment" can be interpreted as "assuming," "expecting," "considering," etc.

[0133] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0134] The reference signal may be abbreviated as RS (Reference Signal) and may be called a pilot depending on the applicable standard.

[0135] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0136] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.

[0137] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0138] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Further, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0139] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0140] The numerology may be communication parameters that apply to the transmission and / or reception of a signal or channel, such as, for example, at least one of a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), a number of symbols per TTI, a radio frame structure, a particular filtering operation that the transceiver performs in the frequency domain, a particular windowing operation that the transceiver performs in the time domain, etc.

[0141] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) in the time domain. A slot may be a time unit based on numerology.

[0142] A slot may include multiple minislots. Each minislot may be composed of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may be composed of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0143] A radio frame, a subframe, a slot, a minislot, and a symbol each represent a time unit for transmitting a signal. The radio frame, the subframe, the slot, the minislot, and the symbol may each be referred to by a different name.

[0144] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit expressing the TTI may be called a slot, a minislot, or the like, instead of a subframe.

[0145] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user plane device 50) to each user plane device 50 in TTI units. Note that the definition of TTI is not limited to this.

[0146] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) in which a transport block, a code block, a code word, etc. are actually mapped may be shorter than the TTI.

[0147] In addition, when one slot or one minislot is called TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. Also, the number of slots (minislots) constituting the minimum time unit of scheduling may be controlled.

[0148] A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, etc.

[0149] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0150] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the numerology, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.

[0151] In addition, the time domain of the RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length. Each of one TTI, one subframe, etc. may be composed of one or more resource blocks.

[0152] Note that one or more RBs may be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0153] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0154] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a numerology on a carrier, where the common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0155] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0156] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell", "carrier", etc. in this disclosure may be replaced with "BWP".

[0157] The above-mentioned structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0158] In this disclosure, where articles have been added due to translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0159] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0160] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the specific information).

[0161] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0162] 20 Access mobility management device 210 Transmitter 220 Receiving unit 230 Setting section 240 Control Unit 30 Session Management Device 310 Transmitter 320 Receiving unit 330 Setting Department 340 Control Unit 40 Session Management Device 410 Transmitter 420 Receiving unit 430 Setting Department 440 Control Unit 50 User Plane Device 510 Transmitter 520 Receiving unit 530 Setting Department 540 Control Unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output device

Claims

[Claim 1] a receiving unit for receiving a request for a progress difference report from the session management device; A control unit that detects drift between a clock of an external time domain and a 5G system clock; A transmitter that transmits to the session management device a difference in speed between the clock of the external time domain and the 5G system clock and identification information of the external time domain. A user plane device comprising:

Images