Network node and communication method

Abstract

A network node has: a reception unit that receives, from a first network node, information including a policy and charging control rule (PCC) rule, traffic characteristic information, an uplink destination address (UL destination address), and a downlink destination address (DL destination address); a control unit that generates, on the basis of the information, information for setting the interior of a transport network (TN); and a transmission unit that transmits the generated information to a second network node that controls the TN, the reception unit receives a TN path setting completion from the second network node, and the transmission unit transmits the TN path setting completion to the first network node.

Description

Technical Field

[0001] The present invention relates to a network node and a communication method in a communication system. Background Art

[0002] In 3GPP (registered trademark) (3rd Generation Partnership Project), in order to further increase system capacity, further increase data transmission speed, further reduce latency in the wireless section, etc., research on a wireless communication method called 5G or NR (New Radio) has been carried out (hereinafter, this wireless communication method will be referred to as "5G" or "NR"). In 5G, in order to meet the requirement conditions of achieving a throughput of 10 Gbps or more and making the latency in the wireless section 1 ms or less, various wireless technologies have been studied.

[0003] In NR, a network architecture including 5GC (5G Core Network) and NG-RAN (Next Generation-Radio Access Network) has been studied. This 5GC (5G Core Network) corresponds to the core network EPC (Evolved Packet Core) in the network architecture of LTE (Long Term Evolution), and this NG-RAN (Next Generation-Radio Access Network) corresponds to the RAN (Radio Access Network) in the network architecture of LTE, that is, E-UTRAN (Evolved Universal Terrestrial Radio Access Network) (for example, Non-Patent Document 1).

[0004] In addition, in a future network architecture, innovation of the transport network of the user plane, a mechanism that allows for the future independent development of functions related to the transport network, a mechanism for a mobile communication operator to select functions related to the transport network from options, etc. have been studied.

[0005] Prior Art Documents

[0006] Non-Patent Documents

[0007] Non-Patent Document 1: 3GPP TS23.501 V17.6.0 (2022-09)

[0008] Non - Patent Document 2: 3GPP TS 38.401 V17.2.0 (2022 - 09)

[0009] Non - Patent Document 3: 3GPP TS23.502 V17.6.0 (2022 - 09)

[0010] Non - Patent Document 4: 3GPP TS29.244 V17.6.0 (2022 - 09)

[0011] Non - Patent Document 5: 3GPP TS 38.413 V17.2.0 (2022 - 09)

[0012] Non - Patent Document 6: 3GPP TS 37.483 V17.2.0 (2022 - 09)

[0013] Non - Patent Document 7: 3GPP TS23.700 - 25 V2.0.0 (2022 - 11)

[0014] Non - Patent Document 8: IOWN GF System and Technology Outlook (2021 - 04) Summary of the Invention

[0015] Problems to be Solved by the Invention

[0016] In the transport network of the user plane, instead of using GTP - U (GPRS Tunnelling Protocol for User Plane) as in the past, the utilization of SRv6 (Segment Routing IPv6) and the use of an optical forwarding network utilizing optoelectronic conversion have been studied. However, in the existing structure, the independent development or selection of functions related to the transport network cannot be achieved.

[0017] The present invention has been completed in view of the above problems, and its object is to introduce a generalized TN (Transport Network) system.

[0018] Means for Solving the Problems

[0019] According to the disclosed technology, a network node is provided, which has: a receiving unit that receives, from a first network node, information including a policy and charging control rule (PCC rule), service characteristic information, a destination address for the uplink (UL destination address), and a destination address for the downlink (DL destination address); a control unit that generates, based on the information, information for setting inside the transport network (TN); and a transmitting unit that transmits the generated information to a second network node that controls the TN. The receiving unit receives TN path setting completion from the second network node, and the transmitting unit transmits TN path setting completion to the first network node.

[0020] Advantages of the Invention

[0021] According to the disclosed technology, a generalized TN (Transport Network) system can be introduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 It is a diagram for explaining an example of a communication system.

[0023] Figure 2 It is a diagram for explaining an example of a communication system in a roaming environment.

[0024] Figure 3 It is a diagram for explaining Example (1) of a network architecture.

[0025] Figure 4 It is a diagram for explaining Example (2) of a network architecture.

[0026] Figure 5 It is a diagram for explaining Example (1) of the network architecture in an embodiment of the present invention.

[0027] Figure 6 It is a diagram for explaining Example (2) of the network architecture in an embodiment of the present invention.

[0028] Figure 7 It is a diagram for explaining an example of a generalized TN system in an embodiment of the present invention.

[0029] Figure 8 It is a timing diagram for explaining an example of the start of PDU session establishment in an embodiment of the present invention.

[0030] Figure 9 It is a timing diagram for explaining an example of TN path setting in the case of a GTP-U specific TN system in an embodiment of the present invention.

[0031] Figure 10 It is a timing diagram for explaining an example of TN path setting in the case of a TSN specific TN system in an embodiment of the present invention.

[0032] Figure 11 It is a timing diagram for explaining an example of TN path setting in the case of the APN native TN system in the embodiment of the present invention.

[0033] Figure 12 It is a timing diagram for explaining an example of the completion of PDU session establishment in the embodiment of the present invention.

[0034] Figure 13 It is a diagram showing an example of the functional structure of the base station 10 and the network node 30 in the embodiment of the present invention.

[0035] Figure 14 It is a diagram showing an example of the functional structure of the terminal 20 in the embodiment of the present invention.

[0036] Figure 15 It is a diagram showing an example of the hardware structure of the base station 10 and the terminal 20 in the embodiment of the present invention.

[0037] Figure 16 It is a diagram showing an example of the structure of the vehicle 2001 in the embodiment of the present invention. Detailed implementation manners

[0038] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In addition, the embodiments described below are examples, and the embodiments applying the present invention are not limited to the following embodiments.

[0039] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are appropriately used. Among them, the existing technology is, for example, existing LTE, but is not limited to existing LTE. In addition, unless otherwise specified, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and subsequent modes (e.g., NR) or wireless LAN (Local Area Network).

[0040] In addition, in the embodiment of the present invention, "configuring" wireless parameters, etc. may be pre-configuring a predetermined value, or may be configuring wireless parameters notified from the network node 30 or the terminal 20.

[0041] Figure 1 It is a diagram for explaining an example of a communication system. As Figure 1As shown, the communication system consists of a UE serving as a terminal 20 and multiple network nodes 30. Hereinafter, although it is assumed that there is one network node 30 corresponding to each function, multiple functions can be implemented by one network node 30, or one function can be implemented by multiple network nodes 30. In addition, the "connection" described below can be a logical connection or a physical connection.

[0042] The RAN (Radio Access Network) is a network node 30 with radio access functions, which can include a base station 10 and is connected to the UE, the AMF (Access and Mobility Management Function), and the UPF (User plane function). The AMF is a network node with functions such as termination of the RAN interface, termination of the NAS (Non-Access Stratum), registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 that is interconnected with the DN (Data Network) and has functions such as an external PDU (Protocol Data Unit) session point, routing and forwarding of packets, and QoS (Quality of Service) processing of the user plane. The UPF and the DN form a network slice. Multiple network slices are constructed in the wireless communication network of the embodiment of the present invention.

[0043] The AMF is connected to the 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). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via their respective service-based interfaces, namely Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0044] The SMF is a network node 30 with functions such as session management, IP (Internet Protocol) address allocation and management for the UE, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function. The NEF is a network node with the ability to notify other NFs (Network Functions) and event functions. The NSSF is a network node 30 with functions such as selection of the network slice to which the UE is connected, determination of the authorized NSSAI (Network Slice Selection Assistance Information), determination of the configured NSSAI, and determination of the set of AMFs to which the UE is connected. The PCF is a network node 30 with the function of performing policy control of the network. The AF is a network node 30 with the function of controlling the application server. The NRF is a network node 30 with the function of discovering NF instances that provide services. The UDM is a network node 30 that manages subscriber data and authentication data. The UDM is connected to the UDR (User Data Repository) that stores this data.

[0045] Figure 2This is a diagram for explaining an example of a communication system in a roaming environment. As Figure 2 shown, the network consists of a UE as a terminal 20 and multiple network nodes 30. Hereinafter, although it is assumed that there is one network node 30 corresponding to each function, one network node 30 can implement multiple functions, or multiple network nodes 30 can implement one function. In addition, the "connection" described hereinafter can be a logical connection or a physical connection.

[0046] The RAN is a network node 30 with radio access capabilities, connected to the UE, AMF, and UPF. The AMF is a network node 30 with functions such as termination of the RAN interface, termination of the NAS, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 that is interconnected with the DN and has functions such as an external PDU session point for the user plane, routing and forwarding of packets, and QoS processing of the user plane. The UPF and the DN form a network slice. Multiple network slices are constructed in the wireless communication network according to the embodiments of the present invention.

[0047] The AMF is connected to the UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via service-based interfaces, namely Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0048] The SMF is a network node 30 with functions such as session management, IP address allocation and management for the UE, DHCP function, ARP proxy, and roaming function. The NEF is a network node 30 with the function of notifying other NFs of capabilities and events. The NSSF is a network node 30 with functions such as selection of the network slice to which the UE is connected, determination of the authorized NSSAI, determination of the configured NSSAI, and determination of the set of AMFs to which the UE is connected. The PCF is a network node 30 with the function of performing policy control of the network. The AF is a network node 30 with the function of controlling the application server. The NRF is a network node 30 with the function of discovering NF instances that provide services. The SEPP is a non-transparent proxy for filtering control plane messages between PLMNs (Public Land Mobile Networks). Figure 2 The vSEPP shown is the SEPP in the visited network, and the hSEPP is the SEPP in the home network.

[0049] As shown Figure 2 in the figure, the UE is in a roaming environment connected to the RAN and the AMF in the VPLMN (Visited PLMN). The VPLMN and the HPLMN (Home PLMN) are connected via the vSEPP and the hSEPP. The UE can communicate with the UDM of the HPLMN via the AMF of the VPLMN, for example.

[0050] Figure 3 is a diagram for explaining Example (1) of the network architecture. As shown Figure 3 in the figure, the gNB-CU-CP (gNB Central Unit Control Plane) has the functions of PDCP (Packet Data Convergence Protocol) and RRC (Radio Resource Control), and is connected to the AMF within the SBA (Service Based Architecture) via the N2 interface (refer to Reference 1 and Reference 2). In addition, the gNB-CU-CP is connected to the gNB-CU-UP (gNB Central Unit User Plane) via the E1 interface.

[0051] The gNB-CU-UP has the functions of PDCP and GTP-U (GPRS Tunnelling Protocol), and is connected to the UPF with the function of GTP-U via the N3 interface (refer to Reference 1 and Reference 2).

[0052] Figure 4 is a diagram for explaining Example (2) of the network architecture. Regarding the control plane, as shown Figure 4 in the figure, the RAN side is composed in the order of RU (Radio Unit), DU (Distributed Unit), PDCP, RRC, and NGAP communication unit (vehicle). The link of the center-edge boundary is composed of the N2 interface, and the NGAP communication unit is connected to the AMF. For example, the AMF, SMF, UDM, etc. are connected to each other via the SBI (Service Based Interface).

[0053] Here, in a future network architecture, regarding the control plane, in order to unify the mechanism for managing and operating the border links between edge centers with the mechanism for managing and operating the paths between NFs within the core network, the SBI-ization of these border links and the application of Service Mesh have been studied.

[0054] For example, gNB-CU-CP is separated into a PDCP termination part gNB-PDCP and an RRC termination part RRC-NF. gNB-PDCP and RRC-NF are connected via SBI. gNB-PDCP has an F1 interface and is connected to the DU via the F1 interface. Except for this F1 interface, both gNB-PDCP and RRC-NF are integrated into the SBA.

[0055] Similarly, gNB-CU-UP is separated into a PDCP termination part gNB-PDCP and a GTP-U termination part GTP-U termination station adapter. The GTP-U termination station adapter is integrated with the transport network and the GTP-U termination station adapter on the UPF side to form a generalized TN (Transport Network) system. Additionally, the generalized TN can also use user plane protocols other than GTP-U. For example, a generalized TN system with a termination station adapter for a user plane protocol that terminates the N3 interface can also be formed.

[0056] By expanding the SBI between gNB-PDCP and RRC-NF to replace the E1 interface between gNB-CU-CP and gNB-CU-UP. Each message of the E1 interface is SBI-ized. Additionally, the PDCP termination part gNB-PDCP in gNB-CU-CP and the PDCP termination part gNB-PDCP in gNB-CU-UP can be integrated and operate as one function.

[0057] Figure 5 This is a diagram for illustrating Example (1) of the network architecture in the embodiment of the present invention. As Figure 5 shown, within the SBA, it includes gNB-PDCP, RRC-NF, AMF, SMF, etc. gNB-PDCP is connected to the GTP-U termination station adapter of the generalized TN system separated from gNB-CU-UP.

[0058] In addition, the UPF can include a GTP-U termination station adapter on the UPF side and a GW (Gateway).

[0059] Figure 6 This is a diagram for illustrating Example (2) of the network architecture in the embodiment of the present invention. As Figure 6As shown, the RAN side is constituted in the order of the RU, DU, PDCP, and SBI communication units (vehicle). The link of the boundary between the edge centers is constituted by the SBI interface, and RRC, AMF, SMF, UDM, etc. are connected to each other via the SBI.

[0060] Here, further in the future network architecture, the innovation of the transport network of the user plane, the mechanism that allows the future independent development of the functions related to the transport network, the mechanism for a mobile communication operator to select the functions related to the transport network from options, etc. have been studied.

[0061] In the transport network of the user plane, instead of using GTP-U (GPRS Tunnelling Protocol for User Plane) as in the past, the utilization of SRv6 (Segment Routing IPv6), the use of an optical forwarding network utilizing optical and electrical conversion, etc. have been studied. However, in the existing structure, the independent development or selection of the functions related to the transport network cannot be achieved.

[0062] Thus, by introducing a generalized TN system and a generalized user plane path setting process, the independent development or selection of the transport network of the user plane can be carried out.

[0063] Figure 7 It is a diagram for explaining an example of the generalized TN system in the embodiment of the present invention. As Figure 7 shown, the generalized TN system is constituted by a generalized TN system management node and an inherent TN system.

[0064] The generalized TN system management node has an NBI (Northbound Interface) for the 5GS (5G System) control plane. This NBI obtains, for a specific PDU session, the ingress side connection target, egress side connection target, information related to service scheduling (for example, PCC (Policy and Charging Control) rules, service characteristic information, etc.) of the generalized TN system from the 5GS. In addition, the generalized TN system management node controls the inherent TN system management node within the generalized TN system.

[0065] In the inherent TN system, there are a GTP-U network, a TSN (Time Sensitive Networking), an optical transport network, etc. The inherent TN system follows the instructions of the generalized TN system management node.

[0066] As Figure 7As shown, the native TN system consists of a native TN system management node, a second native system management node, a native TN system termination station adapter, and a native TN.

[0067] The native TN system management node has an NBI in the generalized TN system management node. Information obtained by the generalized system management node from the 5GS is transmitted to the NBI of the fixed TN system management node.

[0068] The second native TN system management node does not have an NBI in the generalized TN system management node. It collaborates with the native TN system management node to control the native TN system.

[0069] The native TN system termination station adapter is configured on the ingress side and egress side within the native TN system. The native TN system termination station adapter adds necessary information to the data to be forwarded, performs necessary conversions, and makes it in a form that can be forwarded within the native TN.

[0070] The following generalized user plane path setting process using the generalized TN system is introduced. Enter from the following Figure 8 timing diagram into Figure 9 , Figure 10 or Figure 11 timing diagram. Enter from the following Figure 9 , Figure 10 or Figure 11 timing diagram into Figure 12 timing diagram.

[0071] Figure 8 is a timing diagram for explaining an example of the start of PDU session establishment in the embodiment of the present invention. In step S101, the UE 20 sends a PDU session establishment request to the AMF 30C (refer to Non-Patent Document 3). In the next step S102, the AMF 30C sends a PDU session generation request to the SMF 30D. In the next step S103, the SMF 30D obtains a PCC rule (which can also be a default PCC rule) from the PCF 30E (refer to Non-Patent Document 3). The PCC rule may include a TSCAC (TimeSensitive Communication Assistance Container).

[0072] In the next step S104, the SMF 30D determines the GW in the same way as in the case of determining the UPF in the existing specification (refer to Non-Patent Document 3). In the next step S105, in the same way as in the case of setting the UPF in the existing specification, a PFCP session establishment request is sent to the GW 30F (refer to Non-Patent Document 3). This PFCP session establishment request can be the Ngw_PFCPSessionEstablishment request obtained by SBI-ifying the PFCP session establishment request (PFCP Session Establishment Request) in Section 7.5.2.1 of Non-Patent Document 4.

[0073] In the next step S106, the GW 30F sends a PFCP session establishment response to the SMF 30D (refer to Non-Patent Document 3). This PFCP session establishment response can be the Ngw_PFCPSessionEstablishmentresponse obtained by SBI-ifying the PFCP session establishment response (PFCPSession Establishment Response) in Section 7.5.3.1 of Non-Patent Document 4. This PFCP session establishment response contains the created PDR (Packet Detection Rule) IE, and the created PDR contains the local F-TEID (Fully Qualified Tunnel Endpoint Identifier). However, the GW 30F can also set an IP address for the local F-TEID and not set the TEID.

[0074] In the next step S107, the SMF 30D sends a PDU session resource setup request to the RRC-NF 30B. The PDU session resource setup request may include a PDU session resource setup request transfer IE (PDUSession Resource Setup Request Transfer IE) in section 9.3.4.1 of non-patent document 5. The PDU session resource setup request may include TSCAI (TSC Assistance Information). The PDU session resource setup request transfer IE (PDUSession Resource Setup Request Transfer IE) may include a UL NG-U UP TNL information IE (ULNG-U UP TNL Information IE). The SMF 30D may set an IP address in the UL NG-U UP TNL information IE (UL NG-U UP TNL Information IE) without setting the GTP-TEID.

[0075] In the next step S108, the RRC-NF 30B sends a PDCP bearer context setup request to the gNB-PDCP 30A. The PDCP bearer context setup request may be an Ngnb-pdcp_BearerContextSetup request obtained by SBI-ifying section 9.2.2.1 of non-patent document 6. The PDCP bearer context setup request may include TSCAI. The PDCP bearer context setup request may include a PDU session resource setup list IE (PDU Session Resource To SetupList IE) (refer to section 9.3.3.2 of non-patent document 6). The PDU session resource setup list IE (PDU SessionResource To Setup List IE) may include an NG UL UP transport layer information IE (NG UL UP TransportLayer Information IE). The RRC-NF 30B may set an IP address in the NG UL UP transport layer information IE (NG UL UP TransportLayer Information IE) without setting the GTP-TEID.

[0076] In the next step S109, gNB-PDCP 30A sends a PDCP bearer context setup response to RRC-NF 30B. The PDCP bearer context setup response can be the Ngnb-pdcp_BearerContextSetup response obtained by SBI-ifying Section 9.2.2.2 of Non-Patent Document 6. The PDCP bearer context setup response can include the established service characteristic information. The PDCP bearer context setup response can include a PDU session resource setup list IE (PDU Session Resource Setup List IE) (refer to Section 9.3.3.5 of Non-Patent Document 6). The PDU session resource setup list IE (PDU Session Resource Setup List IE) can include an NG DL UP transport layer information IE (NG DL UP Transport Layer Information IE). gNB-PDCP 30A can set the IP address in the NG DL UP transport layer information IE (NG DL UP Transport Layer Information IE) without setting the GTP-TEID.

[0077] In the next step S110, RRC-NF 30B sends a PDU session resource setup response to SMF 30D. The PDU session resource setup response can include a PDU session resource setup response transfer IE (PDU Session Resource Setup Response Transfer IE) in Section 9.3.4.2 of Non-Patent Document 5. The PDU session resource setup response can include the established service characteristic information. The PDU session resource setup response transfer IE (PDU Session Resource Setup Response Transfer IE) can include a DL QoS flow per TNL information IE (DL QoS Flow per TNL Information IE) for each TNL information IE (Non-Patent Document 5, 9.3.4.2). RRC-NF 30B can also set the IP address in the UP transport layer information IE (UP Transport Layer Information IE) of the DL QoS flow per TNL information IE (DL QoS Flow per TNL Information IE) for each TNL information IE without setting the GTP-TEID.

[0078] Figure 9This is a timing diagram showing an example of TN path setting in the case of the GTP-U native TN system in the embodiments of the present invention. In step S201 following step S110, the SMF 30D sends a TN path setting request as a new message to the generalized TN system management node (hereinafter also referred to as "GTNMF"). This message is SBI-enabled and can be named Ngtnmf_TNpathSetup request. This message may include a PCC rule (which may also be a default PCC rule), service characteristic information prompted by the gNB-PDCP 30A, the UL (Uplink) destination IP address prompted by the GW 30F, and the DL (Downlink) destination IP address prompted by the gNB-PDCP 30A.

[0079] In the next step S202, the GTNMF 30G identifies the use of GTP-U through network settings. In the next step S203, the GTNMF 30G sends the PCC rule, the UL destination IP address, and the DL destination IP address to the GTP-U native TN system management node (hereinafter also referred to as "STNMFgtp-u").

[0080] In the next step S204, the STNMFgtp-u 30H sends the setting based on the PCC rule and the DL destination IP address to the GTP-U native TN system terminating station adapter 30J adjacent to the GW. In the next step S205, the GTP-U native TN system terminating station adapter 30J adjacent to the GW selects the UL GTP-U TEID and sends this GTP-U TEID to the STNMFgtp-u 30H.

[0081] In the next step S206, the STNMFgtp-u 30H sends the setting based on the PCC rule, the UL destination IP address, and the UL GTP-U TEID to the GTP-U native TN system terminating station adapter 30I adjacent to the gNB-PDCP. In the next step S207, the GTP-U native TN system terminating station adapter 30I adjacent to the gNB-PDCP selects the DL GTP-U TEID and sends this GTP-U TEID to the STNMFgtp-u 30H.

[0082] In the next step S208, the STNMFgtp-u 30H sends the DL GTP-U TEID to the GTP-U native TN system terminating station adapter 30J adjacent to the GW. In the next step S209, the STNMFgtp-u 30H sends TN path setting completion to the GTNMF 30G.

[0083] Figure 10 This is a timing diagram for an example of TN path setting in the case of the TSN-native TN system in the embodiments of the present invention. In step S301 following step S110, the SMF 30D sends a TN path setting request as a new message to the generalized TN system management node (hereinafter also referred to as "GTNMF"). This message is SBI-enabled and can have a name such as Ngtnmf_TNpathSetup request. This message may include a PCC rule (which may be a default PCC rule), service characteristic information prompted by the gNB-PDCP 30A, the UL destination IP address prompted by the GW 30F, and the DL destination IP address prompted by the gNB-PDCP 30A.

[0084] In the next step S302, the GTNMF 30G identifies the use of TSN through network settings. In the next step S303, the GTNMF 30G sends the PCC rule, service characteristic information, UL destination IP address, and DL destination IP address to the TSN-native TN system management node (hereinafter also referred to as "STNMFtsn") that operates as a CUC (Centralized User Configuration).

[0085] In the next step S304, the STNMFtsn 30K generates a merged flow request condition based on the information received in step S303 and sends the merged flow request condition to the second TSN-native TN system management node (hereinafter also referred to as "STNMF2tsn") that operates as a CNC (Central Network Controller) (see Non-Patent Document 7). In the next step S305, the STNMF2tsn 30L sends a merged end-station communication setting to the STNMFtsn 30K.

[0086] In the next steps S306a and S306b, the STNMFtsn 30K sets the TSN native TN system terminator adapters 30M adjacent to the gNB-PDCP and 30N adjacent to the GW that operate as TSN senders / receivers (talkers / listeners) based on the merged terminating station communication settings. In the next step S307, the STNMF2tsn 30L sets the inside of the TSN network including a TSN bridge. In the next step S308, the STNMF2tsn 30L sends a TN path setup completion to the STNMFtsn 30K. In the next step S309, the STNMFtsn 30K sends a TN path setup completion to the GTNMF 30G.

[0087] Figure 11 It is a timing diagram showing an example of TN path setting in the case of explaining the APN native TN system in the embodiment of the present invention. In step S401 following step S110, the SMF 30D sends a TN path setting request as a new message to the generalized TN system management node (hereinafter also referred to as "GTNMF"). This message is SBI-enabled and can be named Ngtnmf_TNpathSetup request. This message may include a PCC rule (which may be a default PCC rule), service characteristic information prompted by the gNB-PDCP 30A, the UL destination IP address prompted by the GW 30F, and the DL destination IP address prompted by the gNB-PDCP 30A.

[0088] In the next step S402, the GTNMF 30G identifies the use of an APN (All-Photonic Network) through network settings. In the next step S403, the GTNMF 30G sends the PCC rule, service characteristic information, UL destination IP address, and DL destination IP address to the APN native TN system management node (hereinafter also referred to as "STNMFapn") that operates as an Apps (refer to Figure 3 .3.1-2) within the Open APN Controller.

[0089] In the next step S404, STNMFapn 30O generates appropriate control information based on the information received in step S403, and sends it to various control functions within the Open APN Controller that functions as the second APN-specific TN system management node group (hereinafter also referred to as "STNMF2apn_X"), such as static and dynamic path control functions, band control functions, path control functions, monitoring functions, etc.

[0090] In the next steps S405a and S405b, STNMF2apn_X 30P sets the APN-specific TN system termination station adapter 30Q adjacent to gNB-PDCP and the APN-specific TN system termination station adapter 30R adjacent to GW that operate as repeater category 2 (refer to Figure 3 .3.1-2 of Non-Patent Document 8).

[0091] In the next step S406, STNMF2apn_X 30P sets the inside of the APN network including an optical aggregation device and an optical switching and amplification device (refer to Figure 3 .3.1-2 of Non-Patent Document 8). In the next step S407, STNMF2apn_X 30P sends TN path setup completed to STNMFapn 30O. In the next step S408, STNMFapn 30O sends TN path setup completed to GTNMF 30G.

[0092] Figure 12 It is a timing diagram for explaining an example of the completion of PDU session establishment in the embodiment of the present invention. In step S501 following step S209, step S309, or step S408, GTNMF 30G sends TN path setup completed to SMF 30D. This TN path setup completed can be a new message Nsmf_TNpathSetupNotify request. This message can include a new IE, i.e., a TN path setup completion notification IE, notifying the completion of path setup within the generalized TN system.

[0093] In the next step S502, the SMF 30D sends a PDU session resource modification request to the RRC-NF 30B. The PDU session resource modification request may include a PDU session resource modification request transfer IE (PDUSession Resource Modify Request Transfer IE) in section 9.3.4.3 of non-patent document 5. The PDU session resource modification request transfer IE (PDUSession Resource Modify Request Transfer IE) may include a TN setting completion notification IE.

[0094] In the next step S503, the SMF 30D sends a PFCP session modification request to the GW 30F. The PFCP session modification request may be a PFCP Session Modification Request or may include a TN path setting completion notification IE.

[0095] In the next step S504, the RRC-NF 30B sends a PDCP bearer context modification request to the gNB-PDCP 30A. The PDCP bearer context modification request may be an Ngnb-pdcp_BearerContextModification request obtained by SBI-ifying section 9.2.2.4 of non-patent document 6 that includes a TN path setting completion notification IE.

[0096] In addition, in the above embodiments, a UL destination IP address and a DL destination IP address are used, but the UL destination and the DL destination only need to be destinations for path selection and are not limited to IP addresses.

[0097] Through the above embodiments, a generalized TN system is introduced and a generalized user plane path setting process is executed. Thus, the transport network of the user plane can be developed independently or selected independently.

[0098] That is, a generalized TN (Transport Network) system can be introduced.

[0099] (Device Structure)

[0100] Next, a functional structure example of the base station 10, the network node 30, and the terminal 20 that implement the above-described processing and actions will be described. The base station 10, the network node 30, and the terminal 20 include the functions of implementing the above embodiments. However, the base station 10, the network node 30, and the terminal 20 may each only have a part of the functions in the embodiments.

[0101] <Base Station 10 and Network Node 30>

[0102] Figure 13 This is a diagram showing an example of the functional structures of base station 10 and network node 30. As Figure 13 shown, base station 10 includes a transmission unit 110, a reception unit 120, a setting unit 130, and a control unit 140. Figure 13 The functional structures shown are merely examples. As long as the operations involved in the embodiments of the present invention can be implemented, the functional distinctions and the names of the functional units can be arbitrary. Additionally, network node 30 may have the same functional structure as base station 10. Furthermore, multiple network nodes 30 with different functions in the system architecture may be composed of multiple network nodes 30 separated by function.

[0103] Transmission unit 110 includes the function of generating signals to be transmitted to terminal 20 or other network nodes 30 and transmitting these signals in a wired or wireless manner. Reception unit 120 includes the function of receiving various signals transmitted from terminal 20 or other network nodes 30 and obtaining, for example, higher-layer information from the received signals. A communication unit including transmission unit 110 and reception unit 120 may also be configured.

[0104] Setting unit 130 stores preset setting information and various setting information to be transmitted to terminal 20 in a storage device, and reads from the storage device as needed. The content of the setting information is, for example, information related to a generalized TN system, etc.

[0105] As described in the embodiments, control unit 140 performs processing related to PDCP in the network. Additionally, control unit 140 performs processing for communication based on the generalized TN system. Moreover, control unit 140 performs processing related to communication with terminal 20. The functional units in control unit 140 related to signal transmission may also be included in transmission unit 110, and the functional units in control unit 140 related to signal reception may be included in reception unit 120.

[0106] <Terminal 20>

[0107] Figure 14 This is a diagram showing an example of the functional structure of terminal 20. As Figure 14 shown, terminal 20 includes a transmission unit 210, a reception unit 220, a setting unit 230, and a control unit 240. Figure 14 The functional structures shown are merely examples. As long as the operations involved in the embodiments of the present invention can be implemented, the functional distinctions and the names of the functional units can be arbitrary. Additionally, the communication device that is the resource holder 20 may also have the same functional structure as terminal 20.

[0108] The transmitting unit 210 generates a transmission signal based on transmission data and transmits the transmission signal wirelessly. The receiving unit 220 receives various signals wirelessly and obtains a higher-layer signal from the received physical-layer signal. In addition, the receiving unit 220 has a function of receiving an NR-PSS, an NR-SSS, an NR-PBCH, a DL / UL control signal, a reference signal, etc. transmitted from the network node 30. A communication unit including the transmitting unit 210 and the receiving unit 220 may also be configured.

[0109] The setting unit 230 stores various setting information received from the network node 30 by the receiving unit 220 in the storage device and reads it out from the storage device as needed. In addition, the setting unit 230 also stores preset setting information. The content of the setting information is, for example, information related to PDCP.

[0110] As described in the embodiments, the control unit 240 performs processing related to PDCP in the network. The functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0111] (Hardware Structure)

[0112] The block diagrams ( Figure 13 and Figure 14 ) used in the description of the above embodiments show blocks in terms of functions. These functional blocks (structural units) are implemented by any combination of at least one of hardware and software. In addition, there is no particular limitation on the implementation method of each functional block. That is, each functional block may be implemented using one device physically or logically combined, or two or more physically or logically separated devices may be directly or indirectly (e.g., using wired, wireless, etc.) connected and these multiple devices may be used to implement it. The functional block may also be implemented by combining software in the above one device or the above multiple devices.

[0113] The functions include judgment, decision-making, determination, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, establishment, comparison, assumption, expectation, regarded as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), assigning, etc., but are not limited to these. For example, a functional block (structural part) that exhibits a transmission function is called a transmitting unit or a transmitter. In short, as described above, there is no particular limitation on the implementation method.

[0114] For example, the network node 30, the terminal 20, etc. in an embodiment of the present disclosure can also function as a computer that processes the wireless communication method of the present disclosure. Figure 15 FIG. is an example showing the hardware structure of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The network node 30 may have the same hardware structure as the base station 10. The above-mentioned base station 10 and terminal 20 may be configured to physically include a computer device such as a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0115] In addition, in the following description, the term "device" can be replaced with "circuit", "equipment (device)", "unit", etc. The hardware structure of the base station 10 and the terminal 20 may be configured to include one or more of the illustrated devices, or may be configured not to include some of the devices.

[0116] Each function in the base station 10 and the terminal 20 is implemented by the following method: a predetermined software (program) is read into hardware such as the processor 1001 and the storage device 1002, so that the processor 1001 performs operations and controls at least one of the communication of the communication device 1004 or the reading and writing of data in the storage device 1002 and the auxiliary storage device 1003.

[0117] The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may also be composed of a central processing unit (CPU: Central Processing Unit) including an interface with peripheral devices, a control device, an arithmetic device, registers, etc. For example, the above-mentioned control unit 140, control unit 240, etc. can also be implemented by the processor 1001.

[0118] In addition, 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 performs various processes accordingly. As the program, a program that causes a computer to execute at least a part of the operations described in the above embodiments is used. For example, Figure 13 The control unit 140 of the base station 10 shown can also be implemented by a control program stored in the storage device 1002 and operating in the processor 1001. In addition, for example, Figure 14 The control unit 240 of the terminal 20 shown can also be implemented by a control program stored in the storage device 1002 and operating in the processor 1001. Although it has been described that the above various processes are executed by one processor 1001, the above various processes can also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 can also be implemented by one or more chips. In addition, the program can also be transmitted from a network via a telecommunication line.

[0119] The storage device 1002 is a computer-readable recording medium, and can be constituted by at least one of, for example, a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), a RAM (Random Access Memory), etc. The storage device 1002 can also be referred to as a register, a cache, a main memory (main storage device), etc. The storage device 1002 can store a program (program code), software module, etc. that can be executed in order to implement the communication method according to one embodiment of the present disclosure.

[0120] The auxiliary storage device 1003 is a computer-readable recording medium, and can be constituted by at least one of, for example, an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a floppy disk, a magneto-optical disk (for example, a compact disc, a digital versatile disc, a Blu-ray (registered trademark) disc, a smart card, a flash memory (for example, a card, a stick, a key drive (Key drive)), a Floppy (registered trademark) disk, a magnetic stripe, etc. The above storage medium can be, for example, a database, a server, and other appropriate media including at least one of the storage device 1002 and the auxiliary storage device 1003.

[0121] The communication device 1004 is hardware (a transceiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, a network controller, a network card, a communication module, etc. For example, the communication device 1004 may also be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., to implement at least one of frequency-division duplex (FDD: Frequency Division Duplex) and time-division duplex (TDD: Time Division Duplex). For example, a transceiver antenna, an amplifier unit, a transceiver unit, a transmission path interface, etc. may also be implemented by the communication device 1004. The transceiver unit may also be physically or logically separately implemented by a transmission unit and a reception unit.

[0122] 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 an input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that performs an output to the outside. In addition, the input device 1005 and the output device 1006 may also be integrally formed (e.g., a touch panel).

[0123] 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 devices.

[0124] In addition, the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP: Digital Signal Processor), an ASIC (Application Specific Integrated Circuit: application-specific integrated circuit), a PLD (Programmable Logic Device: programmable logic device), an FPGA (Field Programmable Gate Array: field programmable gate array), etc., and a part or all of each functional block may also be implemented by this hardware. For example, the processor 1001 may also be implemented using at least one of these hardwares.

[0125] Figure 16 An example of the structure of the vehicle 2001 is shown. As Figure 16As shown, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a gear lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013. Each form / embodiment described in the present disclosure can also be applied to the communication device mounted on the vehicle 2001. For example, it can also be applied to the communication module 2013.

[0126] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also referred to as a steering disk), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0127] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals from various sensors 2021-2029 provided in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 can also be referred to as an ECU (Electronic Control Unit).

[0128] As signals from various sensors 2021-2029, there are a current signal from a current sensor 2021 that senses the current of the motor, a rotational speed signal of the front and rear wheels obtained by a rotational speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, a depression amount signal of the accelerator pedal obtained by an accelerator pedal sensor 2029, a depression amount signal of the brake pedal obtained by a brake pedal sensor 2026, an operation signal of the gear lever obtained by a gear lever sensor 2027, a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028, and so on.

[0129] The information service unit 2012 is composed of various devices such as a car navigation system, an audio system, a speaker, a television, and a radio for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses the information obtained from an external device via the communication module 2013 or the like to provide various multimedia information and multimedia services to the passengers of the vehicle 2001. The information service unit 2012 may include an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) for accepting an input from the outside, and may also include an output device (for example, a display, a speaker, an LED lamp, a touch panel, etc.) for performing an output to the outside.

[0130] The driving assistance system unit 2030 is composed of various devices such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioners for positioning (such as GNSS, etc.), map information (such as high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyroscopic systems (such as IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, which are used to provide functions for preventing accidents in advance or reducing the driving load of the driver, and one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to implement driving assistance functions or autonomous driving functions.

[0131] The communication module 2013 can communicate with the microprocessor 2031 and the components of the vehicle 2001 via a communication port. For example, the communication module 2013 transmits and receives data between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gear shifter 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and the memory (ROM, RAM) 2032, and the sensors 2021 - 2029 in the electronic control unit 2010 of the vehicle 2001 via the communication port 2033.

[0132] The communication module 2013 can be controlled by the microprocessor 2031 of the electronic control unit 2010 and is a communication device capable of communicating with external devices. For example, it transmits and receives various information with external devices via wireless communication. The communication module 2013 can be located inside or outside the electronic control unit 2010. External devices can also be, for example, base stations, mobile stations, etc.

[0133] The communication module 2013 can send at least one of the signals from the various sensors 2021 - 2028 input to the electronic control unit 2010, the information obtained based on this signal, and the information based on the input from the external (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021 - 2028, the information service unit 2012, etc. can also be referred to as input units that accept input. For example, the PUSCH sent by the communication module 2013 can contain the information based on the above input.

[0134] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) sent from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 can also be referred to as an output unit that outputs information (for example, outputs information to devices such as a display and a speaker based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH)). In addition, the communication module 2013 stores various information received from the external device in the memory 2032 that can be utilized by the microprocessor 2031. The microprocessor 2031 can also control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gear lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001 based on the information stored in the memory 2032.

[0135] (Summary of the Embodiment)

[0136] As described above, according to an embodiment of the present invention, there is provided a network node having: a receiving unit that receives information including a policy and charging control rule, i.e., a PCC rule, service characteristic information, a destination address for the uplink, i.e., a UL destination address, and a destination address for the downlink, i.e., a DL destination address, from a first network node; a control unit that generates information for setting information inside a transport network, i.e., TN inside, based on the information; and a transmitting unit that transmits the generated information to a second network node that controls the TN, the receiving unit receives completion of TN path setting from the second network node, and the transmitting unit transmits completion of TN path setting to the first network node.

[0137] According to the above structure, by introducing a generalized TN system and performing a generalized user plane path setting process, it is possible to develop or select the transport network of the user plane independently. That is, it is possible to introduce a generalized TN (Transport Network) system.

[0138] The second network node may control a time-sensitive network, i.e., TSN. According to this structure, it is possible to use TSN as a generalized TN system.

[0139] The generated information may be a merged flow request condition. According to this structure, it is possible to use TSN as a generalized TN system.

[0140] The second network node may control an all-optical network, i.e., APN. According to this structure, it is possible to use APN as a generalized TN system.

[0141] The sending unit can send the generated information to a plurality of the second network nodes each having different functions related to an APN. With this configuration, it is possible to use the APN as a generalized TN system.

[0142] Furthermore, according to an embodiment of the present invention, there is provided a communication method, in which a network node performs the following steps: a receiving step of receiving, from a first network node, information including a policy and charging control rule (PCC rule), service characteristic information, an uplink destination address (UL destination address), and a downlink destination address (DL destination address); a control step of generating, based on the information, information for setting inside a transport network (TN); a sending step of sending the generated information to a second network node that controls the TN; a step of receiving TN path setting completion from the second network node; and a step of sending TN path setting completion to the first network node.

[0143] According to the above configuration, by introducing a generalized TN system and performing a generalized user plane path setting process, it is possible to develop or select the transport network of the user plane independently. That is, it is possible to introduce a generalized TN (Transport Network) system.

[0144] (Supplement of the embodiment)

[0145] The above has described the embodiments of the present invention. However, the disclosed invention is not limited to such embodiments, and those skilled in the art should understand various variations, modifications, alternatives, substitution examples, etc. Specific numerical examples have been used for the purpose of facilitating the understanding of the invention, but these numerical values are only examples and any appropriate arbitrary values can be used as long as not specifically indicated. The item classification in the above description is not essential for the present invention. The matters described in two or more items can be combined as needed, or the matters described in one item can be applied to the matters described in another item (as long as there is no contradiction). The boundaries of the functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical components. The operations of multiple functional units can be performed by one physical component, or the operation of one functional unit can be performed by multiple physical components. Regarding the processing procedures described in the embodiments, the order of processing can be swapped without contradiction. For the purpose of facilitating the description of the processing, the base station 10 and the terminal 20 are illustrated using functional block diagrams, but such devices can also be implemented by hardware, software, or a combination thereof. The software that operates according to the embodiments of the present invention through the processor of the base station 10 and the software that operates according to the embodiments of the present invention through the processor of the terminal 20 can also be stored in a random access memory (RAM), a flash memory, a read-only memory (ROM), an EPROM, an EEPROM, a register, a hard disk drive (HDD), a removable disk, a CD-ROM, a database, a server, and other appropriate arbitrary storage media respectively.

[0146] In addition, the notification of information is not limited to the forms / embodiments described in this disclosure, and other methods can also be used. For example, the notification of information can be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), high layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof. In addition, RRC signaling can be referred to as an RRC message. For example, it can also be an RRC connection setup message, an RRC connection reconfiguration message, etc.

[0147] Each form / embodiment described in the present disclosure can also be applied to systems using at least one of LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (x is an integer or a decimal, for example), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), 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), other appropriate systems, and next-generation systems extended, modified, created, or defined based on these systems. In addition, multiple systems can be combined (for example, a combination of at least one of LTE and LTE-A and 5G, etc.) and applied.

[0148] For the processing procedures, timings, flows, etc. of each form / embodiment described in this specification, the order can be swapped without contradiction. For example, for the methods described in the present disclosure, the order of examples is used to indicate the elements of various steps, but is not limited to the specific order indicated.

[0149] In this specification, specific actions performed by base station 10 are sometimes also performed by its upper node according to circumstances. In a network composed of one or more network nodes including base station 10, it is obvious that various actions performed for communication with terminal 20 can be carried out by at least one of base station 10 and other network nodes other than base station 10 (for example, MME or S-GW etc. are considered, but not limited to these). In the above, the case where there is one other network node other than base station 10 is illustrated, but the other network nodes can also be a combination of multiple other network nodes (for example, MME and S-GW).

[0150] The information, signals, etc. described in this disclosure can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). Input and output can also be performed via multiple network nodes.

[0151] The input or output information, etc. can be stored in a specific location (for example, memory), or can be managed using a management table. The input or output information, etc. can be rewritten, updated, or appended. The output information, etc. can also be deleted. The input information, etc. can also be sent to other devices.

[0152] The determination in this disclosure can be made by a value represented by 1 bit (0 or 1), can also be made by a Boolean value (true or false), and can also be made by a numerical comparison (for example, comparison with a predetermined value).

[0153] For software, regardless of whether it is called software, firmware, middleware, microcode, hardware description language, or by other names, it should be broadly interpreted as referring to commands, command sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc.

[0154] In addition, software, commands, information, etc. can be transmitted and received via a transmission medium. For example, when using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technologies (infrared, microwave, etc.) to send software from a web page, server, or other remote source, at least one of these wired technologies and wireless technologies is included in the definition of the transmission medium.

[0155] The information, signals, etc. described in this disclosure can also be represented using any one of a variety of different technologies. For example, the data, commands, instructions (command), information, signals, bits, symbols, chips, etc. that may be involved in the overall description above can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination of these.

[0156] In addition, the terms described in this disclosure and the terms required to understand this disclosure can be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol can also be a signal (signaling). In addition, a signal can also be a message. In addition, a component carrier (CC: Component Carrier) can also be referred to as a carrier frequency, a cell, a frequency carrier, etc.

[0157] The terms "system" and "network" used in this disclosure can be used interchangeably.

[0158] In addition, the information, parameters, etc. described in this disclosure can be represented using absolute values, relative values with respect to a predetermined value, or can also be represented using corresponding other information. For example, wireless resources can be indicated using indexes.

[0159] The names used for the above parameters are non-restrictive names in any aspect. Furthermore, the mathematical expressions, etc. using these parameters are sometimes different from the content explicitly disclosed in this disclosure. All kinds of channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by all appropriate names, so the various names assigned to these various channels and information elements are non-restrictive names in any aspect.

[0160] In this disclosure, the terms "base station (BS: Base Station)", "radio 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. can be used interchangeably. Sometimes, the base station is also referred to by terms such as macro cell, small cell, femto cell, pico cell, etc.

[0161] A base station can accommodate one or more (e.g., 3) cells. When the base station accommodates multiple cells, the overall coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also be provided with communication services through a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). Terms such as "cell" or "sector" refer to a part or the whole of the coverage area of at least one of the base station and the base station subsystem that provides communication services within the coverage range.

[0162] In the present disclosure, the base station sending information to the terminal can also be replaced by the base station instructing the terminal to perform control / action based on the information.

[0163] In the present disclosure, terms such as "mobile station (MS)", "user terminal", "user equipment (UE)", and "terminal" can be used interchangeably.

[0164] For a mobile station, those skilled in the art sometimes also refer to it by the following terms: subscriber station, mobile unit, subscriber unit, radio 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 appropriate terms.

[0165] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a communication device, etc. Additionally, 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 refers to an object that can move, and the moving speed can be arbitrary. In addition, of course, the case where the moving body stops is also included. The moving body includes, for example, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, rear cars, rickshaws, ships (ship and other watercraft), airplanes, rockets, artificial satellites, Drone (registered trademark), multi-rotor helicopters, quad-rotor helicopters, balloons, and objects mounted on them, and is not limited thereto. Furthermore, the moving body may be a moving body that autonomously travels based on an operation instruction. It can be a means of transportation (e.g., a car, an airplane, etc.), a moving body that moves in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanoid or non-humanoid). Additionally, at least one of the base station and the mobile station also includes a device that does not necessarily move during a 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.

[0166] In addition, the base station in the present disclosure may also be replaced with a user terminal. For example, a structure in which the communication between the base station and the user terminal is replaced with the communication between multiple terminals 20 (for example, it may also be referred to as D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.) can also apply various forms / embodiments of the present disclosure. In this case, it may also be configured such that the terminal 20 has the functions of the above base station 10. In addition, terms such as "uplink" and "downlink" may also be replaced with terms corresponding to inter-terminal communication (for example, "side"). For example, an uplink channel, a downlink channel, etc. may also be replaced with a side channel.

[0167] Similarly, the user terminal in the present disclosure may be replaced with a base station. In this case, it may also be configured such that the base station has the functions of the above user terminal.

[0168] As used in this disclosure, terms such as "determining" and "deciding" sometimes encompass a variety of actions. For example, "determining" and "deciding" may include considering as having been "determined" or "decided" matters that have been judged, calculated, computed, processed, derived, investigated, looked up, searched, inquired (e.g., searched in a table, database, or other data structure), or ascertained. In addition, "determining" and "deciding" may include considering as having been "determined" or "decided" matters that have been received (e.g., receiving information), transmitted (e.g., transmitting information), input, output, accessed (e.g., accessing data in memory). Further, "determining" and "deciding" may include considering as having been "determined" or "decided" matters that have been resolved, selected, chosen, established, compared, etc. That is, "determining" and "deciding" may include considering certain actions as having been "determined" or "decided" matters. Additionally, "determining (deciding)" may also be replaced by "assuming", "expecting", "considering", etc.

[0169] Terms such as "connected" and "coupled" or any variations of these terms are intended to represent all direct or indirect connections or couplings between two or more elements, and may include cases where there is one or more intermediate elements between the two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be a physical coupling or connection, a logical coupling or connection, or a combination of these. For example, "access" may be used to replace "connected". In the context of this disclosure, it may be considered that two elements are "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, and, as some non-limiting and non-exhaustive examples, using electromagnetic energy having wavelengths in the radio frequency domain, microwave region, and optical (including both visible and invisible) regions to "connect" or "couple" to each other.

[0170] The reference signal can be abbreviated as RS (Reference Signal), or can be called a pilot according to the applied standard.

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

[0172] Any reference to elements using terms such as "first", "second", etc. used in this disclosure does not entirely limit the quantity or order of these elements. These terms may be used in this disclosure as a convenient method for distinguishing between two or more elements. Therefore, the reference to the first element and the second element does not mean that only two elements can be adopted, or that the first element must precede the second element in any form.

[0173] The "unit" in the structure of each of the above devices can also be replaced with "section", "circuit", "equipment", etc.

[0174] When "include", "including" and their variants are used in this disclosure, these terms mean inclusive in the same way as the term "comprising". Also, the term "or" used in this disclosure does not refer to exclusive or.

[0175] In this disclosure, for example, when articles are added through translation as in the case of a, an, and the in English, this disclosure also includes the case where the noun following these articles is in the plural form.

[0176] In this disclosure, the term "A and B are different" can mean "A and B are mutually different". In addition, this term can also mean "A and B are respectively different from C". Terms such as "separate", "combine" can also be interpreted in the same way as "different".

[0177] Each form / embodiment described in this disclosure can be used alone, can be used in combination, or can be switched according to execution. In addition, the notification of predetermined information (for example, the notification of "is X") is not limited to being explicitly performed, and can also be implicitly performed (for example, without performing the notification of the predetermined information).

[0178] As described above, this disclosure has been described in detail, but for those skilled in the art, it should be clear that this disclosure is not limited to the embodiments described in this disclosure. This disclosure can be implemented in the form of modifications and changes without departing from the gist and scope of this disclosure determined by the claims. Therefore, the purpose of the description of this disclosure is to illustrate, and it has no restrictive meaning for this disclosure.

[0179] Description of Reference Numerals

[0180] 10: Base Station

[0181] 110: Transmitter

[0182] 120: Receiver

[0183] 130: Setting Unit

[0184] 140: Control Unit

[0185] 20: Terminal

[0186] 210: Transmitter

[0187] 220: Receiver

[0188] 230: Setting Unit

[0189] 240: Control Unit

[0190] 30: Network Node

[0191] 1001: Processor

[0192] 1002: Storage Device

[0193] 1003: Auxiliary Storage Device

[0194] 1004: Communication Device

[0195] 1005: Input Device

[0196] 1006: Output Device

Claims

1. A network node, comprising: a receiving unit that receives, from a first network node, information including a policy and charging control rule, i.e., a PCC rule, service characteristic information, an uplink destination address, i.e., a UL destination address, and a downlink destination address, i.e., a DL destination address; a control unit that generates, based on the information, information for setting inside a transport network, i.e., inside a TN; and a transmitting unit that transmits the generated information to a second network node that controls the TN, wherein the receiving unit receives TN path setting completion from the second network node, and the transmitting unit transmits TN path setting completion to the first network node.

2. The network node according to claim 1, wherein the second network node controls a time-sensitive network, i.e., a TSN.

3. The network node according to claim 2, wherein the generated information is a merged flow request condition.

4. The network node according to claim 1, wherein the second network node controls an all-optical network, i.e., an APN.

5. The network node according to claim 4, wherein the transmitting unit transmits the generated information to a plurality of the second network nodes each having a different function related to the APN.

6. A communication method, wherein, The following steps are performed by a network node: a receiving step of receiving, from a first network node, information including a policy and charging control rule, i.e., a PCC rule, service characteristic information, an uplink destination address, i.e., a UL destination address, and a downlink destination address, i.e., a DL destination address; a control step of generating, based on the information, information for setting inside a transport network, i.e., inside a TN; a transmitting step of transmitting the generated information to a second network node that controls the TN; a step of receiving TN path setting completion from the second network node; and a step of transmitting TN path setting completion to the first network node.

Images