WO2022162920A1

WO2022162920A1 - Network node and communication method

Info

Publication number: WO2022162920A1
Application number: PCT/JP2021/003425
Authority: WO
Inventors: 淳巳之口; 政宏澤田; 敬浩青木; 聡永田
Original assignee: 株式会社Ｎｔｔドコモ
Priority date: 2021-01-29
Filing date: 2021-01-29
Publication date: 2022-08-04
Also published as: JPWO2022162920A1

Abstract

This network node has a transmission unit which transmits scheduling support information to a next generation Node B Distributed Unit (gNB-DU), and a receiving unit which, on the basis of the aforementioned scheduling support information, receives the wireless-side scheduling information generated by the gNB-DU, wherein the transmission unit transmits the scheduling information based on the wireless-side scheduling information to a transport arranged between the gNB-DU and a next generation Node B - Central Unit - User Plane (gNB-CU-UP) on a data transmission path.

Description

Network node and communication method

The present invention relates to a network node and communication method in a wireless communication system.

NR (New Radio) (also called "5G"), which is the successor system to LTE (Long Term Evolution), requires a large-capacity system, high data transmission speed, low latency, and the simultaneous use of many terminals. Techniques satisfying connection, low cost, power saving, etc. are being studied (for example, Non-Patent Document 1).

In the existing specifications in the NR network, when enabling the TSN (Time-Sensitive Networking) function, the CNC (Central Network Controller) performs the SMF (Session Management function) via TSN-AF (Application Function) and PCF (Policy Control Function) ) to send scheduling assistance information. SMF transmits the scheduling assistance information to gNB (next generation Node-B) as TSCAI (Time-Sensitive Communication Assistance Information). The gNB refers to the scheduling assistance information, and appropriately determines the scheduling of radio part communication using configured grant for UL and semi-persistent scheduling for DL.

On the other hand, in the NR network, the transmission line between gNB-RU (Remote Unit) and gNB-DU (Distributed Unit), the transmission line between gNB-DU and gNB-CU-UP (Central Unit - User Plane), Scheduling of transmission paths between gNB-CU-UP and UPF (User plane function) could not be controlled based on information from CNC.

The present invention has been made in view of the above points, and aims to improve the utilization efficiency of user data transmission lines in a wireless communication system.

According to the disclosed technique, a transmission unit that transmits scheduling support information to gNB-DU (next generation Node B Distributed Unit), and the radio side scheduling information generated by the gNB-DU based on the scheduling support information is received. a receiving unit, and the transmitting unit transmits schedule information based on the wireless side scheduling information to the gNB-DU and gNB-CU-UP (next generation Node B - Central Unit - User Plane) on the data transmission path A network node is provided that transmits to a transport that is placed between.

According to the disclosed technology, it is possible to improve the usage efficiency of user data transmission lines in a wireless communication system.

1 is a diagram for explaining an example of a communication system; FIG. It is a figure showing an example of network composition in an embodiment of the invention. FIG. 2 is a diagram showing an example of transmission lines in the embodiment of the present invention; FIG. FIG. 4 is a sequence diagram for explaining example (1) of PDU session establishment in the embodiment of the present invention; FIG. 4 is a sequence diagram for explaining example (2) of PDU session establishment in the embodiment of the present invention; FIG. 4 is a sequence diagram for explaining example (3) of PDU session establishment in the embodiment of the present invention; FIG. 10 is a sequence diagram for explaining example (4) of PDU session establishment in the embodiment of the present invention; FIG. 10 is a sequence diagram for explaining example (5) of PDU session establishment in the embodiment of the present invention; It is a figure showing an example of functional composition of base station 10 in an embodiment of the invention. 2 is a diagram showing an example of the functional configuration of terminal 20 according to the embodiment of the present invention; FIG. 2 is a diagram showing an example of hardware configuration of base station 10 or terminal 20 according to an embodiment of the present invention; FIG.

Embodiments of the present invention will be described below with reference to the drawings. In addition, the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

Existing technologies are appropriately used for the operation of the wireless communication system according to the embodiment of the present invention. However, the existing technology is, for example, existing LTE, but is not limited to existing LTE. In addition, the term “LTE” used in this specification has a broad meaning including LTE-Advanced and LTE-Advanced and subsequent systems (eg, NR) unless otherwise specified.

Further, in the embodiments of the present invention described below, SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), PUSCH (Physical Uplink Shared Channel). This is for convenience of description, and signals, functions, etc. similar to these may be referred to by other names. Also, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, NR-PDCCH, NR-PDSCH, NR-PUCCH, NR-PUSCH, and the like. However, even a signal used for NR is not necessarily specified as "NR-".

Further, in the embodiment of the present invention, the duplex system may be a TDD (Time Division Duplex) system, an FDD (Frequency Division Duplex) system, or other (for example, Flexible Duplex etc.) method may be used.

Further, in the embodiment of the present invention, "configuring" wireless parameters and the like may mean that predetermined values are preset (Pre-configure), and the base station 10 or A wireless parameter notified from the terminal 20 may be set.

FIG. 1 is a diagram for explaining an example of a communication system. As shown in FIG. 1 , a communication system consists of a UE, which is a terminal 20 , and a plurality of network nodes 30 . Hereinafter, one network node 30 corresponds to each function, but one network node 30 may realize a plurality of functions, or a plurality of network nodes 30 may realize one function. . Also, the "connection" described below may be a logical connection or a physical connection.

A RAN (Radio Access Network) is a network node 30 having a radio access function, may include a base station 10, and is connected with a UE, an AMF (Access and Mobility Management Function) and a UPF (User plane function). The AMF is a network node 30 having functions such as RAN interface termination, NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 that has functions such as a PDU (Protocol Data Unit) session point to the outside that interconnects with a DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) handling. UPF and DN constitute a network slice. A plurality of network slices are constructed in the wireless communication network according to the embodiment of the present invention.

AMF is UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function) and AF (Application Function) are connected. AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF are interconnected via respective service-based interfaces Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, Naf. network node 30 .

The SMF is a network node 30 that has functions such as session management, UE IP (Internet Protocol) address allocation and management, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function. A NEF is a network node 30 that has the function of notifying other NFs (Network Functions) of capabilities and events. NSSF selects the network slice to which the UE connects, determines the allowed NSSAI (Network Slice Selection Assistance Information), determines the NSSAI to be set, determines the AMF set to which the UE connects. be. A PCF is a network node 30 having a function of performing network policy control. AF is a network node 30 having the function of controlling an application server. An NRF is a network node 30 that has the ability to discover NF instances that provide services. A UDM is a network node 30 that manages subscriber data and authentication data. The UDM is connected to a UDR (User Data Repository) that holds the data.

In the existing specifications in the NR network, PLMN (Public There is an implicit assumption that the mobile operator supporting the Land Mobile Network) owns the user data transmission path between gNB-DU and gNB-CU-UP and between gNB-CU-UP and UPF. Also, the notification of the traffic characteristics to the transmission path is only based on the DSCP (Differentiated Services Code Point) value.

In other words, the existing specifications in the NR network do not have the concept of a transmission network operator, there is no method for the transmission network operator to accept traffic from multiple PLMNs for each call, and a transmission line that acquires traffic characteristics off-path is used. can't

Therefore, each part of the transmission path is configured so that it can be regarded as one UPF (hereinafter referred to as "transport") from the outside. A transport may act as one network node, or the transport may also be composed of multiple network nodes.

FIG. 2 is a diagram showing an example of a network configuration according to the embodiment of the present invention. As shown in Figure 2, gNB-CU-CP (next generation Node B - Central Unit - Control Plane) shall be able to set up transport between gNB-DU and gNB-CU-UP. Also, the SMF shall be able to set up the transport between the gNB-CU-UP and the UPF.

As shown in Figure 2, the transport consists of the following three parts 1)-3).

1) A part that receives instructions from gNB-CU-CP or SMF, manages TEID (Tunnel Endpoint Identifier), and deploys traffic characteristics inside the transport. Hereinafter, it is referred to as "tSMF".

2) A portion located on the edge side as a transmission line. Hereinafter, it is referred to as "aUPF".

3) A portion located on the central side as a transmission line. Hereinafter, it is referred to as "bUPF".

As shown in Figure 2, the transport can connect gNB-DU, gNB-CU-UP and UPF in one PLMN and gNB-DU, gNB-CU-UP and UPF in another PLMN.

The requesting PLMN can be distinguished by the instructions sent from the gNB-CU-CP or SMF to the transport. Also, the indication to send from gNB-CU-CP to gNB-CU-UP or from SMF to UPF includes the existing network instance. The network instance shall newly encode the name of the transmission network operator that provides the transport and the transmission service type provided by the transmission network operator.

FIG. 3 is a diagram showing an example of transmission lines in the embodiment of the present invention. In FIG. 3, the transport corresponds to the transmission path between the core U-plane and the RANU plane and the transmission path between the RANU plane and the RAN lower layer. As shown in Figure 3, one PLMN and another PLMN can use transport provided by the same transport network operator. Also, a given PLMN may utilize multiple transports provided by multiple transport network operators. For example, as shown in FIG. 3, the transport provided by transport network operator B accommodates the time-synchronized signaling traffic of a PLMN.

Here, in the existing specifications in the NR network, when enabling the TSN (Time-Sensitive Networking) function, the CNC (Central Network Controller) is SMF ( Send scheduling assistance information to the Session Management function). SMF transmits the scheduling assistance information to gNB (next generation Node-B) as TSCAI (Time-Sensitive Communication Assistance Information). The gNB refers to the scheduling information and appropriately determines the scheduling of radio part communication using configured grant for UL and semi-persistent scheduling for DL.

On the other hand, in the NR network, the transmission line between gNB-RU (Remote Unit) and gNB-DU (Distributed Unit), the transmission line between gNB-DU and gNB-CU-UP (Central Unit - User Plane), Scheduling of transmission paths between gNB-CU-UP and UPF (User plane function) could not be controlled based on information from CNC. Therefore, for example, in the case of a transmission line in which transmission is performed in a time-division manner, a delay occurs due to unnecessary waiting between the wireless part and the wired part.

The communication procedure in the embodiment of the present invention may be executed as A)-E) shown below.

A) At PDU session establishment, SMF sets the appropriate network instance values, for example based on S-NSSAI (Single-Network Slice Selection Assistance Information) and DNN (Data Network Name). The SMF selects the appropriate UPF and advertises the network instance value. The UPF selects the appropriate interface. The interface may be TEID. The SMF selects an appropriate transport to be installed between the UPF and the gNB-CU-UP and informs the requesting PLMN information to the tSMF. The tSMF sets up the interface for the PLMN with aUPF and bUPF and responds to the SMF.

B) SMF informs the gNB-CU-CP of the network instance value. The gNB-CU-CP selects the appropriate gNB-CU-UP and informs it of the network instance value. The gNB-CU-UP selects the appropriate interface. The interface may be TEID. The gNB-CU-CP selects the appropriate transport installed between the gNB-CU-UP and gNB-DU and informs the requesting PLMN information to tSMF. The tSMF sets up the interface for the PLMN with aUPF and bUPF and responds to the gNB-CU-CP.

C) The gNB-CU-CP configures the gNB-DU's UL interface. At this time, the gNB-DU may determine the schedule by internal MAC (Medium Access Control) function to obtain schedule assistance information. gNB-DU is a node that manages the transmission path between gNB-DU and gNB-CU (for example, OLT (Optical Line Terminal) in the case of PON (Passive Optical Network)) to notify the determined traffic characteristics good.

D) The gNB-CU-CP configures the transport DL interface that is installed between the gNB-CU-UP and the gNB-DU. The SMF may then inform the transport of the traffic characteristics determined by the gNB-DU MAC function.

E) The SMF configures the transport DL interface that is installed between the UPF and the gNB-CU-UP. The SMF may then inform the transport of the traffic characteristics determined by the gNB-DU MAC function.

Furthermore, the communication procedure in the embodiment of the present invention may be executed as 1)-10) shown below. The communication procedures A) to E) above and the communication procedures 1) to 10) shown below may be executed in parallel.

1) CNC determines the traffic pattern. The traffic pattern may be, for example, stream definition and gate opening/closing timing at a 5GS (5G System) bridge entrance/exit for each stream. CNC notifies the traffic pattern to SMF via TSN-AF and PCF.

2) SMF configures TSCAI and notifies RAN based on the traffic pattern.

3) The RAN (specifically the MAC function of the gNB-DU) decides the scheduling of the radio part.

4) The gNB-DU notifies the management node (for example, OLT in the case of PON) of the transmission line between the gNB-RU and the gNB-DU of the determined wireless communication schedule. The management node may also have a standardized API to support various wireline transmission technologies. Regarding UL, cooperation between radio communication scheduling and PON scheduling may be implemented as DBA (Dynamic Bandwidth Allocation).

5) gNB-CU-CP, which receives notification of the radio schedule after determination from gNB-DU, based on the radio schedule, the transmission path between gNB-DU and gNB-CU-UP, gNB-CU-UP and UPF, respectively. The gNB-CU-CP informs the respective management node, eg the tSMF of the transport, of the scheduling information. In addition, gNB-CU-CP, when notifying the schedule information to the management node of the transmission path between gNB-CU-UP and UPF, for example, tSMF of the transport, may notify via SMF . The gNB-CU-CP may notify the management node of the scheduling of the wireless communication part, and each management node may correct the time difference due to the distance and use it as schedule information for itself. The management node may also have a standardized API to support various wireline transmission technologies.

6) Each management node performs scheduling on each transmission path.

7) gNB-DU monitors whether the queue status in the device is appropriate for both DL/UL, and if necessary, sends radio scheduling modification information to gNB-CU-CP.

8) gNB-CU-CP receives radio schedule modification information from gNB-DU, based on the modification information, the transmission path between gNB-DU and gNB-CU-UP, gNB-CU-UP and UPF derives schedule correction information necessary for communication on the transmission path between them, respectively. The gNB-CU-CP informs the respective management node, eg tSMF of the transport, of the schedule modification information. In addition, when gNB-CU-CP notifies the management node of the transmission path between gNB-CU-UP and UPF, for example, tSMF of transport, the schedule correction information, even if notified via SMF good. In addition, the gNB-CU-CP may notify the management node of the scheduling correction information for the wireless communication part, and each management node may correct the time difference due to the distance and use it as the schedule correction information to be used by itself. The management node may also have a standardized API to support various wireline transmission technologies.

9) Each management node modifies the scheduling on each transmission path.

10) Through 1) to 9) above, the wireless schedule and the schedule of each part of the wired transmission line are matched.

FIG. 4 is a sequence diagram for explaining example (1) of PDU session establishment according to the embodiment of the present invention. In FIG. 4, the TEID corresponding to UL of UPF 30B is 1, the TEID corresponding to DL of bUPF 30D is 2, the TEID corresponding to UL is 3, the TEID corresponding to DL of aUPF 30E is 4, and the TEID corresponding to UL is 5. do.

In step S101, the UE 20 transmits UL information transfer to the gNB-DU 10C. The gNB-DU 10C then sends a UL-RRC message transfer to the gNB-CU-CP 10A (S102). Subsequently, gNB-CU-CP 10A sends a UL-NAS message transfer to AMF 30F (S103). Subsequently, AMF 30F transmits a PDU session establishment request to SMF 30A (S104).

FIG. 5 is a sequence diagram for explaining example (2) of PDU session establishment according to the embodiment of the present invention. Following step S104 shown in FIG. 4, step S1041 is executed. In step S1041, SMF 30A transmits a policy control request including S-NSSAI and DNN to PCF 30J. Subsequently, PCF 30J transmits a query request to UDR 30K (S1042). Subsequently, UDR 30K transmits a query response to PCF 30J (S1043). Subsequently, PCF 30J transmits a policy control response including TSCAI to SMF 30A. That is, SMF 30A acquires TSCAI using S-NSSAI and DNN as keys. TSCAI may consist of TSCAI for UL and TSCAI for DL.

Return to Figure 4. In step S105, SMF 30A transmits a PDU session establishment response to AMF 30F. Subsequently, the SMF 30A executes UPF selection and transport selection (S106). Subsequently, SMF 30A transmits a PFCP (Packet Forwarding Control Protocol) session establishment request to UPF 30B (S107). The PFCP session establishment request in step S107 includes the appropriate network instance selected by SMF based on the S-NSSAI and DNN. The network instance is assumed to encode the name of the transport network operator that provides the transport and the type of transmission service provided by the transport network operator (for example, deterministic communication with slot allocation, etc.). Subsequently, UPF 30B transmits a PFCP session establishment response to SMF 30A (S108). In step S108, the UPF 30B selects an appropriate local F-TEID (Fully Qualified TEID) based on the network instance and includes it in the PFCP session establishment response. FIG. 4 shows an example in which F-TEID=1.

In step S109, the SMF 30A transmits a PFCP session establishment request to the tSMF 30C. In the PFCP session establishment request in step S109, the SMF 30A also assumes the use of the other company's transmission network, sets the DL source interface and UL destination interface to PLMN specific core (PLMN specific core), and sets the DL destination interface and UL source interface. is set as PLMN specific access, and the company MCC (Mobile Country Code)/MNC (Mobile Network Code) is set as additional information in each setting. Also, the PFCP session establishment request in step S109 includes information that sets 1 to the TEID corresponding to the outer header corresponding to UL. The SMF 30A sets the transport as one UPF. Based on this setting, the tSMF 30C sets each of the multiple UPFs in the transport. tSMF30C behaves as UPF to SMF30A and as SMF to transport. Note that the PLMN-specific core may indicate the UPF in the PLMN, and the PLMN-specific access may indicate the gNB-CU-UP in the PLMN.

In step S110, the tSMF 30C transmits a PFCP session establishment request to the bUPF 30D. In the PFCP session establishment request in step S110, the tSMF 30C sets the PLMN-specific core in the DL source interface and the UL destination interface, and sets information that sets the TEID corresponding to the UL outer header to 1. Subsequently, the bUPF 30D transmits to the tSMF 30C a PFCP session establishment response in which the F-TEID corresponding to the DL is set to 2 and the F-TEID corresponding to the UL is set to 3 (S111). The bUPF 30D selects the appropriate TEID for DL relative to the UPF based on the PLMN-ID.

At step S112, the tSMF 30C transmits a PFCP session establishment request to the aUPF 30E. In the PFCP session establishment request in step S112, the tSMF 30C sets PLMN-specific access to the DL destination interface and the UL source interface, and sets information that sets the TEID corresponding to the UL outer header to 3. Subsequently, the aUPF 30E transmits to the tSMF 30C a PFCP session establishment response in which the F-TEID corresponding to DL is set to 4 and the F-TEID corresponding to UL is set to 5 (S113). The aUPF 30E selects the appropriate TEID for UL relative to the gNB based on the PLMN-ID.

In step S114, the tSMF 30C transmits a PFCP session change request with 4 as the TEID corresponding to the DL external header to the bUPF 30D. Subsequently, bUPF 30D transmits a PFCP session change response to tSMF 30C (S115). Subsequently, tSMF 30C transmits to SMF 30A a PFCP session establishment response in which the F-TEID corresponding to DL is set to 2 and the F-TEID corresponding to UL is set to 5 (S116). tSMC30C, bUPF30D and aUPF30E appear as one UPF from the outside.

In step S117, the SMF 30A transmits a PFCP session change request with 2 as the TEID corresponding to the DL outer header to the UPF 30B. Subsequently, UPF 30B transmits a PFCP session change response to SMF 30A (S118). Subsequently, the SMF 30A transmits to the AMF 30F a message transfer request including the UL endpoint IP address, GTP (GPRS Tunneling Protocol)-TEID information of 5, and the network instance (S119). The message transfer request may further include TSCAI-based schedule information acquired by SMF 30A. The message transfer request requests resource configuration for a PDU session. Subsequently, AMF 30F transmits a message transfer response to SMF 30A (S120).

FIG. 6 is a sequence diagram for explaining example (3) of PDU session establishment according to the embodiment of the present invention. In FIG. 6, the TEID corresponding to the DL of gNB-CU-UP10A is 6, the TEID corresponding to the UL is 7, the TEID corresponding to the DL of bUPF30H is 8, the TEID corresponding to the UL is 9, and the DL of aUPF30I. Let 10 be the TEID, 11 be the TEID corresponding to the UL, and 12 be the TEID corresponding to the DL of the gNB-DU.

In step S121, the AMF 30F sends to the gNB-CU-CP 10A a PDU session resource configuration request including the UL endpoint IP address, information with GTP-TEID set to 5, and network instance. Here, the gNB-CU-CP 10A may select the appropriate gNB-CU-UP 10B and transport network operator. Note that the network instance may be a suitable network instance selected by the gNB-CU-CP 10A based on the S-NSSAI and DNN. The network instance is assumed to encode the name of the transport network operator that provides the transport and the type of transmission service provided by the transport network operator (for example, deterministic communication with slot allocation, etc.). The PDU session resource configuration request may further include schedule information based on the TSCAI acquired by the SMF 30A.

Next, the gNB-CU-CP 10A sends a bearer setup request including the UL transport layer address, information with GTP-TEID set to 5, and network instance to the gNB-CU-UP 10B (S122). A network instance encodes the name of a transport network operator that provides transport and the type of transmission service provided by the transport network operator (for example, deterministic communication with slot allocation). Subsequently, gNB-CU-UP 10B sets GTP-TEID to 6 as the transport layer address corresponding to DL, and sets GTP-TEID to 7 as the transport layer address corresponding to UL gNB-CU- Send to CP 10A (S123). In step S123 the gNB-CU-UP 10B selects an appropriate local GTP-TEID based on the network instance on the UL and includes it in the bearer setup response. FIG. 6 shows an example in which DL has GTP-TEID=6 and UL has GTP-TEID=7.

In step S124, the gNB-CU-CP 10A sends a PFCP session establishment request to the tSMF 30G. In the PFCP session establishment request in step S124, the PLMN specific core is set for the DL source interface and the UL destination interface, and the PLMN specific access is set for the DL destination interface and the UL source interface. Also, the PFCP session establishment request in step S124 includes information that sets 7 as the TEID corresponding to the outer header corresponding to UL. The gNB-CU-CP 10A configures the transport as one UPF. Based on this setting, the tSMF 30G sets each of the multiple UPFs in the transport. tSMF30G behaves as UPF towards gNB-CU-CP10A and as SMF towards transport.

In step S125, the tSMF 30G transmits a PFCP session establishment request to the bUPF 30H. In the PFCP session establishment request in step S125, the tSMF 30G sets the PLMN-specific core in the DL source interface and the UL destination interface, and sets the information that the TEID corresponding to the UL outer header is 7. Subsequently, the bUPF 30H transmits to the tSMF 30G a PFCP session establishment response in which the F-TEID corresponding to DL is set to 8 and the F-TEID corresponding to UL is set to 9 (S126). The bUPF 30H selects the appropriate TEID for DL relative to the gNB-CU-UP based on the PLMN-ID.

In step S127, the tSMF 30G transmits a PFCP session establishment request to the aUPF 30I. In the PFCP session establishment request in step S127, the tSMF 30G sets PLMN-specific access to the DL destination interface and the UL source interface, and sets information that the TEID corresponding to the UL outer header is 9. Subsequently, the aUPF 30I transmits to the tSMF 30G a PFCP session establishment response in which the F-TEID corresponding to DL is set to 10 and the F-TEID corresponding to UL is set to 11 (S128). The aUPF 30I selects the appropriate TEID for UL relative to the gNB-DU based on the PLMN-ID.

In step S129, the tSMF 30G transmits a PFCP session change request with 10 as the TEID corresponding to the DL external header to the bUPF 30H. Subsequently, bUPF 30H transmits a PFCP session change response to tSMF 30G (S130). Subsequently, the tSMF 30G transmits to the gNB-CU-CP 10A a PFCP session establishment response in which the F-TEID corresponding to DL is set to 8 and the F-TEID corresponding to UL is set to 11 (S131). tSMC30G, bUPF30H and aUPF30I appear as one UPF from the outside.

In step S132, the gNB-CU-CP 10A transmits a PFCP session change request with 8 as the TEID corresponding to the DL external header to the gNB-CU-UP 10B. Subsequently, gNB-CU-UP 10B sends a PFCP session change response to gNB-CU-CP 10A (S133). Subsequently, the gNB-CU-CP 10A transmits a UE context change request including the UL transport layer address and information to set the GTP-TEID to 11 to the gNB-DU 10C (S134). The UE context change request may further include schedule assistance information based on TSCAI acquired by SMF 30A. Subsequently, the gNB-DU 10C sends a UE context change response including the DL transport layer address and GTP-TEID to 12 to the gNB-CU-CP 10A (S135). The UE context change response is based on the TSCAI-based schedule support information acquired by SMF 30A in gNB-DU 10C, and further includes "TSC traffic characteristics information (TSC Traffic Characteristics)" as the radio side scheduling information actually established. may contain.

FIG. 7 is a sequence diagram for explaining example (4) of PDU session establishment according to the embodiment of the present invention. The steps shown in FIG. 7 may be performed in parallel with step S135. In step S1351, the gNB-DU 10C notifies the TSC traffic characteristic information to the management node 30L (for example, OLT in the case of PON) of the transmission line between the gNB-RU and the gNB-DU 10C. The management node appropriately schedules the transmission path between the gNB-RU and the gNB-DU 10C based on the TSC traffic characteristics information. Subsequently, the management node 30L of the transmission line between the gNB-RU and the gNB-DU10C transmits a response to the gNB-DU10C (S1352).

Return to Figure 6. Note that if step S132 and step S133 are changed to a bearer context change request and a bearer context change response, the change amount of gNB-CU-UP can be suppressed.

In step S136, the gNB-CU-CP 10A transmits a PFCP session change request with 12 as the TEID corresponding to the outer header of the DL to the tSMF 30G. The PFCP session modification request may further include TSC information generated based on TSC traffic characteristic information. Note that the TSC information may be the same as the TSC traffic characteristic information. Based on the TSC information, the tSMF 30G appropriately schedules transmission paths between the aUPF 30I and the bUPF 30H. Subsequently, the tSMF 30G transmits a PFCP session change request with 12 as the TEID corresponding to the external header of the DL to the aUPF 30I (S137). Subsequently, aUPF 30I transmits a PFCP session change response to tSMF 30G (S138). Subsequently, tSMF 30G sends a PFCP session change response to gNB-CU-CP 10A (S139).

In step S140, the gNB-CU-CP 10A sends a DL-RRC message transfer indicating that the PDU session establishment has been accepted to the gNB-DU 10C. Subsequently, the gNB-DU 10C transmits RRCReconfiguration indicating that the PDU session establishment has been accepted to the UE 20 (S141). Subsequently, the UE 20 transmits RRCReconfigurationComplete to the gNB-DU 10C (S142). Subsequently, the gNB-DU 10C sends a UL-RRC message transfer indicating that the RRC reconfiguration is completed to the gNB-CU-CP 10A (S143). Subsequently, the gNB-CU-CP 10A sends a PDU session resource setting response indicating that the DL endpoint IP address and the GTP-TEID is 6 to the AMF 30F (S144). The PDU session resource configuration response may further include TSC traffic characteristic information.

FIG. 8 is a sequence diagram for explaining example (5) of PDU session establishment according to the embodiment of the present invention. In step S145, the AMF 30F transmits to the SMF 30A a PDU session update request indicating that the endpoint IP address of the DL and the GTP-TEID is 6. The PDU session resource update request may further include TSC traffic characteristic information. Subsequently, the SMF 30A transmits to the tSMF 30C a PFCP session change request with 6 as the TEID corresponding to the external header of the DL (S146). The PFCP session modification request may further include TSC information generated based on TSC traffic characteristic information. Note that the TSC information may be the same as the TSC traffic characteristic information. Based on the TSC information, the tSMF 30C appropriately schedules transmission paths between the aUPF 30E and the bUPF 30D. Subsequently, the tSMF 30C transmits a PFCP session change request with 6 as the TEID corresponding to the DL external header to the aUPF 30I (S147). Subsequently, aUPF 30I transmits a PFCP session change response to tSMF 30G (S148). Subsequently, tSMF 30C transmits a PFCP session change response to SMF 30A (S149). Subsequently, SMF 30A transmits a PDU session update response to AMF 30F (S150).

By applying the above-described embodiment, it is possible to create a transmission path that has advanced transmission capabilities such as enabling deterministic communication with slot allocation, or has added value such as relaying via a time synchronization server. It is possible to promote the growth of the transmission network operator that provides it. The PLMN can provide subscribers with advanced services that do not tend to generate large amounts of traffic using the services of the transmission network operator. In addition, by enriching the content of the traffic characteristics provided to the transmission line in the off-path, it can be expected to effectively utilize mainly the optical transmission line.

In addition, the PLMN can select another company's transmission line for each call according to traffic characteristics. A transport network operator can respond to call-by-call transport service provision requests from multiple PLMNs. The transport network can obtain traffic characteristics off-path.

Furthermore, by applying the above embodiment, the delay can be shortened. It is possible to efficiently use the transmission line resources of the wired part. Also, as a secondary effect, guaranteeing low jitter or isochronism is originally a function of DS-TT (Device-Side TSN Translator) and NW-TT (Network-Side TSN Translator), but RAN When scheduling is always performed according to TSCAI, low-jitter isochronous communication can be performed without DS-TT and NW-TT.

That is, in the wireless communication system, it is possible to improve the usage efficiency of the user data transmission path.

(Device configuration)
Next, functional configuration examples of the base station 10 and the terminal 20 that execute the processes and operations described above will be described. The base stations 10 and terminals 20 contain the functionality to implement the embodiments described above. However, each of the base station 10 and terminal 20 may have only part of the functions in the embodiment.

<Base station 10>
FIG. 9 is a diagram showing an example of the functional configuration of base station 10 according to the embodiment of the present invention. As shown in FIG. 9, the base station 10 has a transmitting section 110, a receiving section 120, a setting section 130, and a control section 140. The functional configuration shown in FIG. 9 is merely an example. As long as the operation according to the embodiment of the present invention can be executed, the functional division and the names of the functional units may be arbitrary. The network node 30 may have functional configurations similar to those of the base station 10 .

The transmission unit 110 includes a function of generating a signal to be transmitted to the terminal 20 side and wirelessly transmitting the signal. The transmitter 110 also transmits inter-network-node messages to other network nodes. The receiving unit 120 includes a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, higher layer information from the received signals. Also, the transmitting unit 110 has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL/UL control signals, etc. to the terminal 20 . The receiving unit 120 also receives inter-network node messages from other network nodes.

The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 . The content of the setting information is, for example, information related to the PDU session.

The control unit 140 performs control related to communication by the PDU session, as described in the embodiment. Also, the control unit 140 controls communication with the terminal 20 based on the UE capability report regarding radio parameters received from the terminal 20 . A functional unit related to signal transmission in control unit 140 may be included in transmitting unit 110 , and a functional unit related to signal reception in control unit 140 may be included in receiving unit 120 .

<Terminal 20>
FIG. 10 is a diagram showing an example of the functional configuration of terminal 20 according to the embodiment of the present invention. As shown in FIG. 10, the terminal 20 has a transmitting section 210, a receiving section 220, a setting section 230, and a control section 240. The functional configuration shown in FIG. 10 is merely an example. As long as the operation according to the embodiment of the present invention can be executed, the functional division and the names of the functional units may be arbitrary.

The transmission unit 210 creates a transmission signal from the transmission data and wirelessly transmits the transmission signal. The receiving unit 220 wirelessly receives various signals and acquires a higher layer signal from the received physical layer signal. Also, the receiving unit 220 has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL/UL/SL control signals and the like transmitted from the base station 10 . Further, for example, the transmission unit 210, as D2D communication, to the other terminal 20, PSCCH (Physical Sidelink Control Channel), PSSCH (Physical Sidelink Shared Channel), PSDCH (Physical Sidelink Discovery Channel), PSBCH (Physical Sidelink Broadcast Channel) etc., and the receiving unit 120 receives PSCCH, PSSCH, PSDCH, PSBCH, or the like from other terminals 20 .

The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220 . The setting unit 230 also stores preset setting information. The content of the setting information is, for example, information related to the PDU session.

The control unit 240 performs control related to communication by the PDU session, as described in the embodiment. A functional unit related to signal transmission in control unit 240 may be included in transmitting unit 210 , and a functional unit related to signal reception in control unit 240 may be included in receiving unit 220 .

(Hardware configuration)
The block diagrams (FIGS. 9 and 10) used to describe the above embodiments show blocks in functional units. These functional blocks (components) are implemented by any combination of at least one of hardware and software. Also, the method of implementing each functional block is not particularly limited. That is, each functional block may be implemented using one device that is physically or logically coupled, or directly or indirectly using two or more devices that are physically or logically separated (e.g. , wired, wireless, etc.) and may be implemented using these multiple devices. A functional block may be implemented by combining software in the one device or the plurality of devices.

Functions include judging, determining, determining, calculating, calculating, processing, deriving, investigating, searching, checking, receiving, transmitting, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, assuming, Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. can't For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. In either case, as described above, the implementation method is not particularly limited.

For example, the base station 10, the terminal 20, etc. according to the embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. FIG. 11 is a diagram illustrating an example of hardware configurations of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and terminal 20 described above are 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. good too.

In the following explanation, the term "apparatus" can be read as a circuit, device, unit, or the like. The hardware configuration of the base station 10 and terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured without some devices.

Each function of the base station 10 and the terminal 20 is performed by the processor 1001 performing calculations and controlling communication by the communication device 1004 by loading predetermined software (programs) onto hardware such as the processor 1001 and the storage device 1002. or by controlling at least one of data reading and writing in the storage device 1002 and the auxiliary storage device 1003 .

The processor 1001, for example, operates an operating system and controls the entire computer. The processor 1001 may be configured with a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like. For example, the control unit 140 , the control unit 240 and the like described above may be implemented by the processor 1001 .

In addition, the processor 1001 reads programs (program codes), software modules, 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 them. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. For example, control unit 140 of base station 10 shown in FIG. 9 may be implemented by a control program stored in storage device 1002 and operated by processor 1001 . Also, for example, the control unit 240 of the terminal 20 shown in FIG. Although it has been explained that the above-described various processes are executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. FIG. Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via an electric communication line.

The storage device 1002 is a computer-readable recording medium, for example, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. may be configured. The storage device 1002 may also be called a register, cache, main memory (main storage device), or the like. The storage device 1002 can store executable programs (program code), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

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

The communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like. The communication device 1004 includes a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to realize at least one of, for example, frequency division duplex (FDD) and time division duplex (TDD). may consist of For example, a transmitting/receiving antenna, an amplifier section, a transmitting/receiving section, a transmission line interface, etc. may be implemented by the communication device 1004 . The transceiver may be physically or logically separate implementations for the transmitter and receiver.

The input device 1005 is an input device (for example, keyboard, mouse, microphone, switch, button, sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, display, speaker, LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated (for example, a touch panel).

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 devices.

In addition, the base station 10 and the terminal 20 include hardware such as microprocessors, digital signal processors (DSPs), ASICs (Application Specific Integrated Circuits), PLDs (Programmable Logic Devices), and FPGAs (Field Programmable Gate Arrays). , and part or all of each functional block may be implemented by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

(Summary of embodiment)
As described above, according to the embodiment of the present invention, a transmission unit that transmits scheduling assistance information to gNB-DU (next generation Node B Distributed Unit), and the gNB-DU based on the scheduling assistance information and a receiving unit that receives the radio-side scheduling information generated by the transmitting unit, the schedule information based on the radio-side scheduling information is transmitted to the gNB-DU and gNB-CU-UP (next generation Node B - Central Unit - User Plane).

With the above configuration, the delay can be shortened. It is possible to efficiently use the transmission line resources of the wired part. Also, as a secondary effect, guaranteeing low jitter or isochronism is originally a function of DS-TT (Device-Side TSN Translator) and NW-TT (Network-Side TSN Translator), but RAN When scheduling is always performed according to TSCAI, low-jitter isochronous communication can be performed without DS-TT and NW-TT. That is, in a wireless communication system, it is possible to improve the usage efficiency of the user data transmission path.

Based on the radio side scheduling information, further comprising a control unit for generating a schedule in a data transmission path between the gNB-DU and the gNB-CU-UP, transmitting the generated schedule to the transport may With this configuration, the delay can be shortened, and the transmission line resources of the wired portion can be efficiently used.

Further, according to the embodiment of the present invention, a transmitting unit that transmits scheduling assistance information to AMF (Access and Mobility Management Function), and gNB-DU (next generation Node B Distributed Unit) based on the scheduling assistance information a receiving unit that receives the generated radio-side scheduling information from the AMF, and the transmitting unit transmits the radio-side scheduling information to UPF (User Plane Function) and gNB-CU-UP (next generation Node B - Central Unit - User Plane) is provided for the network node to send to the transport.

Further, according to the embodiment of the present invention, a receiving unit that receives scheduling support information, a control unit that determines radio-side scheduling information based on the scheduling support information, and a gNB-RU ( A network node is provided having a transmitter for transmitting to a management node of a data transmission path between next generation Node B - Remote Unit.

Further, according to the embodiment of the present invention, a transmission procedure for transmitting scheduling assistance information to gNB-DU (next generation Node B Distributed Unit), and the radio side generated by the gNB-DU based on the scheduling assistance information A reception procedure for receiving scheduling information and schedule information based on the radio side scheduling information are transmitted between the gNB-DU and the gNB-CU-UP (next generation Node B - Central Unit - User Plane) on the data transmission path. A communication method is provided in which a network node performs a step of transmitting to a transport located in a network node.

(Supplement to the embodiment)
Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art can understand various modifications, modifications, alternatives, replacements, and the like. be. Although specific numerical examples have been used to facilitate understanding of the invention, these numerical values are merely examples and any appropriate values may be used unless otherwise specified. The division of items in the above description is not essential to the present invention, and the items described in two or more items may be used in combination as necessary, and the items described in one item may be used in another item. may apply (unless inconsistent) to the matters set forth in Boundaries of functional or processing units in functional block diagrams do not necessarily correspond to boundaries of physical components. The operations of a plurality of functional units may be physically performed by one component, or the operations of one functional unit may be physically performed by a plurality of components. As for the processing procedures described in the embodiments, the processing order may be changed as long as there is no contradiction. Although the network node 30 and the terminal 20 have been described using functional block diagrams for convenience of process description, such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of the network node 30 according to the embodiment of the invention and the software operated by the processor of the terminal 20 according to the embodiment of the invention are respectively stored in random access memory (RAM), flash memory, read-only memory. (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other appropriate storage medium.

Also, notification of information is not limited to the aspects/embodiments described in the present disclosure, and may be performed using other methods. For example, notification of information includes physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, It may be implemented by broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof.In addition, RRC signaling may also be called an RRC message, for example, RRC It may be a connection setup (RRC Connection Setup) message, an RRC connection reconfiguration message, or the like.

Each aspect/embodiment described in the present disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system) 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 extended It may be applied to at least one of the next generation systems. Also, a plurality of systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A and 5G, etc.).

The order of the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this specification may be changed as long as there is no contradiction. For example, the methods described in this disclosure present elements of the various steps using a sample order, and are not limited to the specific order presented.

A specific operation performed by the network node 30 in this specification may be performed by its upper node in some cases. In a network of one or more network nodes, including network node 30, various operations performed for communication with terminal 20 may be network node 30 and other network nodes other than network node 30 ( (eg, but not limited to MME or S-GW). Although the above example illustrates the case where there is one network node other than the network node 30, the other network node may be a combination of a plurality of other network nodes (for example, MME and S-GW). .

Information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may be input and output via multiple network nodes.

Input/output information may be stored in a specific location (for example, memory) or managed using a management table. Input/output information and the like can be overwritten, updated, or appended. The output information and the like may be deleted. The entered information and the like may be transmitted to another device.

The determination in the present disclosure may be performed by a value represented by 1 bit (0 or 1), may be performed by a boolean value (Boolean: true or false), or may be performed by comparing numerical values (e.g. , comparison with a predetermined value).

Software, whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, includes instructions, instruction sets, code, code segments, program code, programs, subprograms, and software modules. , applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like.

In addition, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, the software uses at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.) to website, Wired and/or wireless technologies are included within the definition of transmission medium when sent from a server or other remote source.

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

The terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, the channel and/or symbols may be signaling. A signal may also be a message. A component carrier (CC) may also be called a carrier frequency, a cell, a frequency carrier, or the like.

The terms "system" and "network" used in this disclosure are used interchangeably.

In addition, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. may be represented. For example, radio resources may be indexed.

The names used for the parameters described above are not restrictive names in any respect. Further, the formulas, etc., using these parameters may differ from those expressly disclosed in this disclosure. Since the various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are in no way restrictive names. is not.

In the present disclosure, "base station (BS)", "radio base station", "base station device", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission/reception point", "cell", "sector", Terms such as "cell group," "carrier," and "component carrier" may be used interchangeably. A base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, and the like.

A base station can accommodate one or more (eg, three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, each smaller area being associated with a base station subsystem (e.g., an indoor small base station (RRH: The term "cell" or "sector" refers to part or all of the coverage area of at least one of the base stations and base station subsystems serving communication services in this coverage. point to

In the present disclosure, terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal", etc. may be used interchangeably. .

A mobile station is defined 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 It may also be called a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

At least one of the base station and mobile station may be called a transmitting device, a receiving device, a communication device, or the like. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, or the like. The mobile object may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile object (e.g., drone, self-driving car, etc.), or a robot (manned or unmanned ). Note that at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations. 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.

Also, the base station in the present disclosure may be read as a user terminal. For example, communication between a base station and a user terminal is replaced with communication between a plurality of terminals 20 (for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.) For the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the terminal 20 may have the functions of the network node 30 described above. Also, words such as "up" and "down" may be replaced with words corresponding to inter-terminal communication (for example, "side"). For example, uplink channels, downlink channels, etc. may be read as side channels.

Similarly, user terminals in the present disclosure may be read as base stations. In this case, the base station may have the functions that the above-described user terminal has.

The terms "determining" and "determining" used in this disclosure may encompass a wide variety of actions. "Judgement" and "determination" are, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (eg, lookup in a table, database, or other data structure), ascertaining as "judged" or "determined", and the like. Also, "judgment" and "determination" are used for receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, access (accessing) (for example, accessing data in memory) may include deeming that a "judgment" or "decision" has been made. In addition, "judgment" and "decision" are considered to be "judgment" and "decision" by resolving, selecting, choosing, establishing, comparing, etc. can contain. In other words, "judgment" and "decision" may include considering that some action is "judgment" and "decision". Also, "judgment (decision)" may be read as "assuming", "expecting", "considering", or the like.

The terms "connected", "coupled", or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, It can include the presence of one or more intermediate elements between two elements being "connected" or "coupled." Couplings or connections between elements may be physical, logical, or a combination thereof. For example, "connection" may be read as "access". As used in this disclosure, two elements are in the radio frequency domain using at least one of one or more wires, cables and printed electrical connections, and as some non-limiting and non-exhaustive examples. , electromagnetic energy having wavelengths in the microwave and optical (both visible and invisible) regions, and the like.

The reference signal can also be abbreviated as RS (Reference Signal), and may also be called Pilot depending on the applicable standard.

The term "based on" as used in this disclosure does not mean "based only on" unless otherwise specified. In other words, the phrase "based on" means both "based only on" and "based at least on."

Any reference to elements using the "first," "second," etc. designations 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, reference to a first and second element does not imply that only two elements can be employed or that the first element must precede the second element in any way.

"Means" in the configuration of each device described above may be replaced with "unit", "circuit", "device", or the like.

Where "include," "including," and variations thereof are used in this disclosure, these terms are inclusive, as is the term "comprising." is intended. Furthermore, the term "or" as used in this disclosure is not intended to be an exclusive OR.

In this disclosure, if articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are plural.

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 that "A and B are different from C". Terms such as "separate," "coupled," etc. may also be interpreted in the same manner as "different."

Each aspect/embodiment described in the present disclosure may be used alone, may be used in combination, or may be used by switching along with execution. In addition, the notification of predetermined information (for example, notification of “being X”) is not limited to being performed explicitly, but may be performed implicitly (for example, not notifying the predetermined information). good too.

In addition, in the present disclosure, TSCAI is an example of scheduling assistance information. The TSC traffic characteristic information is an example of radio side scheduling information.

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 practiced with modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Accordingly, the description of the present disclosure is for illustrative purposes and is not meant to be limiting in any way.

10 base station 110 transmitting unit 120 receiving unit 130 setting unit 140 control unit 20 terminal 210 transmitting unit 220 receiving unit 230 setting unit 240 control unit 30 network node 1001 processor 1002 storage device 1003 auxiliary storage device 1004 communication device 1005 input device 1006 output device

Claims

A transmission unit that transmits scheduling assistance information to gNB-DU (next generation Node B Distributed Unit);
A receiving unit that receives radio side scheduling information generated by the gNB-DU based on the scheduling assistance information,
The transmission unit, the schedule information based on the wireless side scheduling information, in the data transmission path gNB-DU and gNB-CU-UP (next generation Node B - Central Unit - User Plane) is installed between Network node to send to transport.
Based on the radio side scheduling information, further comprising a control unit that generates a schedule in the data transmission path between the gNB-DU and the gNB-CU-UP,
2. The network node of claim 1, transmitting the generated schedule to the transport.
A transmission unit that transmits scheduling assistance information to an AMF (Access and Mobility Management Function);
A receiving unit that receives wireless side scheduling information generated by gNB-DU (next generation Node B Distributed Unit) based on the scheduling support information from the AMF,
The transmitting unit transmits the radio-side scheduling information to a transport installed between UPF (User Plane Function) and gNB-CU-UP (next generation Node B-Central Unit-User Plane) on a data transmission path. Network node to send.
a receiver that receives scheduling assistance information;
a control unit that determines radio-side scheduling information based on the scheduling support information;
A network node having a transmission unit that transmits the radio side scheduling information to a management node of a data transmission path between gNB-RU (next generation Node B-Remote Unit).
A transmission procedure for transmitting scheduling assistance information to gNB-DU (next generation Node B Distributed Unit);
A reception procedure for receiving radio side scheduling information generated by the gNB-DU based on the scheduling assistance information;
Send schedule information based on the radio side scheduling information to a transport installed between the gNB-DU and the gNB-CU-UP (next generation Node B-Central Unit-User Plane) on the data transmission path A communication method in which network nodes perform procedures.