Network node and communication method

Abstract

A network node has: a reception unit that receives, from a first network node, information including an uplink destination address (UL destination address), a downlink destination address (DL destination address), the number of paths, and traffic characteristic information for each path; 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 each setting result within the network from the second network node, and the control unit generates TN path setting completion information including a list on the basis of each setting result, and transmits the TN path setting completion information to the second network node. The list has a number of entries corresponding to the number of routes, with the name of one terminated ingress-side communication port, the name of the other terminated egress-side communication port, and the route traffic characteristic information as one entry. The transmission unit transmits, to the first network node, TN path setting completion including the TN path setting completion information.

Description

Technical Field

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

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) is conducting research on wireless communication methods known as 5G or NR (New Radio) (hereinafter referred to as "5G" or "NR") to achieve further increases in system capacity, higher data transmission speeds, and lower latency within wireless networks. In 5G, various wireless technologies are being researched to meet the requirements of achieving throughput of 10 Gbps or more and keeping latency within wireless networks to 1 ms or less.

[0003] In NR, a network architecture including 5GC (5G Core Network) and NG-RAN (Next Generation-Radio Access Network) is studied. The 5GC (5G Core Network) corresponds to the core network in the network architecture of LTE (Long Term Evolution), namely EPC (Evolved Packet Core), and the NG-RAN (Next Generation-Radio Access Network) corresponds to the RAN (Radio Access Network) in the network architecture of LTE, namely E-UTRAN (Evolved Universal Terrestrial Radio Access Network) (for example, non-patent document 1).

[0004] In addition, in the future network architecture, research is being conducted on innovations in the user plane transmission network, mechanisms that allow future independent development of functions related to the transmission network, and mechanisms for mobile communication operators to select functions related to the transmission network from options.

[0005] Prior art literature

[0006] Non-patent literature

[0007] Non-Patent Document 1: 3GPP TS 23.501 V17.7.0 (December 2022)

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

[0009] Non-Patent Document 3: 3GPP TS 23.502 V17.7.0 (December 2022)

[0010] Non-Patent Document 4: 3GPP TS 29.244 V17.7.1 (December 2022)

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

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

[0013] Non-Patent Document 7: 3GPP TR 23.700-25 V2.0.0 (November 2022)

[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 user plane transport network, rather than using GTP-U (GPRS Tunnelling Protocol for User Plane) as previously used, research is underway to utilize SRv6 (Segment Routing IPv6) and an optical forwarding network that utilizes photoelectric conversion. However, the existing architecture does not allow for the independent development or selection of transport network functions.

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

[0018] Means for solving problems

[0019] According to the disclosed technology, a network node is provided, comprising: a receiving unit that receives information including an uplink destination address, i.e., a UL destination address, a downlink destination address, i.e., a DL destination address, the number of paths, and service characteristic information of each path from a first network node; a control unit that generates information for setting the inside of a transmission network, i.e., a TN, based on the information; and a sending unit that sends the generated information to a second network node that controls the TN, wherein the receiving unit receives each setting result within the network from the second network node, the control unit generates TN path setting completion information including a list based on the each setting result, the list having a name of an inlet-side communication port at the termination of one party, a name of an outlet-side communication port at the termination of the other party, and path service characteristic information as one entry, and having a number of entries corresponding to the number of paths, and the sending unit sends a TN path setting completion message including the TN path setting completion information to the first network node.

[0020] Effects 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 This is a diagram for explaining an example of a communication system.

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

[0024] Figure 3 This is a diagram used to illustrate example (1) of the network architecture.

[0025] Figure 4 This is a diagram used to illustrate example (2) of the network architecture.

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

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

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

[0029] Figure 8 This is a sequence diagram for illustrating an example of the start of PDU session establishment in an embodiment of the present invention.

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

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

[0032] Figure 11 This is a sequence diagram for explaining example (1) of TN path setting in the case of an APN-specific TN system in the embodiment of the present invention.

[0033] Figure 12 This is a sequence diagram for explaining example (1) of the completion of the PDU session establishment in an embodiment of the present invention.

[0034] Figure 13 This is a sequence diagram for explaining Example (2) of TN path setting in the case of an APN-specific TN system in the embodiment of the present invention.

[0035] Figure 14 This is a sequence diagram for explaining example (2) of the completion of the PDU session establishment in an embodiment of the present invention.

[0036] Figure 15 1 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30 in the embodiment of the present invention.

[0037] Figure 16 This is a diagram showing an example of the functional configuration of the terminal 20 in the embodiment of the present invention.

[0038] Figure 17 This is a diagram showing an example of the hardware configuration of the base station 10 and the terminal 20 in the embodiment of the present invention.

[0039] Figure 18 1 is a diagram showing an example of the structure of a vehicle 2001 in the embodiment of the present invention. DETAILED DESCRIPTION

[0040] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. The embodiments described below are merely examples, and embodiments to which the present invention is applied are not limited to the following embodiments.

[0041] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are appropriately used. The existing technologies are, for example, but not limited to, existing LTE. Furthermore, unless otherwise specified, the term "LTE" used in this specification has a broad meaning that includes LTE-Advanced and subsequent technologies (e.g., NR) or wireless LANs (Local Area Networks).

[0042] Further, in the embodiment of the present application, the "Configure" radio parameters and the like can be pre-configured with predetermined values, or can be configured with radio parameters notified from the network node 30 or the terminal 20.

[0043] Figure 1 is a diagram for explaining an example of a communication system. As shown in Figure 1 , the communication system is composed of a UE which is a terminal 20, and a plurality of network nodes 30. Hereinafter, although it is assumed that there is one network node 30 corresponding to each function, a plurality of functions can be implemented by one network node 30, and one function can be implemented by a plurality of network nodes 30. Further, the "connection" described below can be a logical connection, or can be a physical connection.

[0044] The RAN (Radio Access Network) is a network node 30 having a radio access function, and can include a base station 10, and is connected to a UE, an AMF (Access and Mobility Management Function), and a UPF (User plane function). The AMF is a network node 30 having a function of terminating a RAN interface, terminating a NAS (Non-Access Stratum), registration management, connection management, reachability management, mobility management, and the like. The UPF is a network node 30 having a function of a PDU (Protocol Data Unit) session point to the outside, packet routing and forwarding, QoS (Quality of Service) processing of a user plane, and the like, and is connected to a DN (Data Network). The UPF and the DN constitute a network slice. A plurality of network slices are constructed in the wireless communication network of the embodiment of the present application.

[0045] 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 interfaces based on their respective services, namely, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0046] 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, roaming function, etc. NEF is a network node 30 that has the function of notifying other NFs (Network Function) of capabilities and events. NSSF is a network node 30 that has functions such as selecting the network slice to which the UE is connected, determining the authorized NSSAI (Network Slice Selection Assistance Information), determining the set NSSAI, and determining the AMF set to which the UE is connected. PCF is a network node 30 that has the function of performing network policy control. AF is a network node 30 that has the function of controlling application servers. NRF is a network node 30 that has the function of discovering NF instances that provide services. UDM is a network node 30 that manages subscriber data and authentication data. UDM is connected to the UDR (User Data Repository) that stores this data.

[0047] Figure 2FIG is a diagram for explaining an example of a communication system in a roaming environment. Figure 2 As shown, the network is composed of a UE (terminal terminal) 20 and multiple network nodes 30. Hereinafter, it is assumed that there is one network node 30 corresponding to each function. However, multiple functions may be implemented by one network node 30, or one function may be implemented by multiple network nodes 30. Furthermore, the "connection" described below may refer to either a logical connection or a physical connection.

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

[0049] 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 their respective service-based interfaces, namely, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

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

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

[0052] Figure 3 This is a diagram for explaining example (1) of the network architecture. Figure 3 As shown, the gNB-CU-CP (gNB Central Unit Control Plane) performs PDCP (Packet Data Convergence Protocol) and RRC (Radio Resource Control) functions and is connected to the AMF within the SBA (Service Based Architecture) via the N2 interface (see References 1 and 2). Furthermore, the gNB-CU-CP is connected to the gNB-CU-UP (gNB Central Unit User Plane) via the E1 interface.

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

[0054] Figure 4 This is a diagram used to illustrate example (2) of the network architecture. Regarding the control plane, Figure 4 As shown, the RAN side is composed of the RU (Radio Unit), DU (Distributed Unit), PDCP, RRC, and NGAP communication unit (vehicle) in this order. The link between the center-edge boundary is formed by the N2 interface, and the NGAP communication unit is connected to the AMF. For example, the AMF, SMF, and UDM are connected to each other via the SBI (Service Based Interface).

[0055] Here, in the future network architecture, regarding the control plane, in order to unify the management and operation mechanism of the boundary link between the edge center and the management and operation mechanism of the NF inter-path within the core network, the SBI of the boundary link and the application of the service mesh are studied.

[0056] For example, the gNB-CU-CP is split into the PDCP termination component, gNB-PDCP, and the RRC termination component, RRC-NF. The gNB-PDCP connects to the RRC-NF via the SBI. The gNB-PDCP has an F1 interface and connects to the DU via the F1 interface. In addition to the F1 interface, the gNB-PDCP and RRC-NF are integrated into the SBA.

[0057] Similarly, the gNB-CU-UP is separated into the PDCP termination component, gNB-PDCP, and the GTP-U termination component, the GTP-U Termination Adapter. The GTP-U Termination Adapter is integrated with the GTP-U Termination Adapters on the transport network and UPF sides to form a generalized TN (Transport Network) system. Furthermore, the generalized TN can also use user plane protocols other than GTP-U. For example, a generalized TN system can be constructed with a Termination Adapter that terminates the user plane protocol of the N3 interface.

[0058] The E1 interface between the gNB-CU-CP and gNB-CU-UP is replaced by an SBI extension between the gNB-PDCP and RRC-NF. Each E1 interface message is converted to an SBI. Furthermore, the PDCP termination part gNB-PDCP in the gNB-CU-CP and the PDCP termination part gNB-PDCP in the gNB-CU-UP can be integrated to operate as a single function.

[0059] Figure 5 This is a diagram for explaining an example (1) of a network architecture in an embodiment of the present invention. Figure 5 As shown, the SBA includes gNB-PDCP, RRC-NF, AMF, SMF, etc. The gNB-PDCP is connected to the GTP-U terminal adapter of the generalized TN system separated from the gNB-CU-UP.

[0060] In addition, UPF may include a GTP-U terminal adapter and a GW (Gateway) on the UPF side.

[0061] Figure 6 This is a diagram for explaining example (2) of the network architecture in the embodiment of the present invention. Figure 6As shown, the RAN side is composed of RU, DU, PDCP, and SBI communication units (vehicles) in this order. The link between the edge center is composed of the SBI interface, and RRC, AMF, SMF, UDM, etc. are connected to each other via SBI.

[0062] Here, in the future network architecture, we further study the innovation of the user plane transmission network, the mechanism that allows the future independent development of functions related to the transmission network, and the mechanism that allows mobile communication operators to select functions related to the transmission network from options.

[0063] In the user-plane transport network, rather than using GTP-U (GPRS Tunnelling Protocol for User Plane), as has been the case in the past, research is underway into utilizing SRv6 (Segment Routing IPv6) and the use of optical forwarding networks that utilize photoelectric conversion. However, the existing architecture does not allow for the independent development or selection of transport network-related functions.

[0064] Therefore, by introducing a universal TN system and a universal user plane path setting process, independent development or selection of the user plane transmission network can be enabled.

[0065] Figure 7 1 is a diagram for explaining an example of a generalized TN system in an embodiment of the present invention. Figure 7 As shown, the generalized TN system is composed of a generalized TN system management node and a unique TN system.

[0066] The universal TN system management node has a Northbound Interface (NBI) for the 5G System (5G System) control plane. This NBI obtains information related to the universal TN system's ingress and egress connection targets, as well as service scheduling (e.g., PCC (Policy and Charging Control) rules and service feature information) from the 5GS for a specific PDU session. Furthermore, the universal TN system management node controls the inherent TN system management node within the universal TN system.

[0067] The native TN system includes a GTP-U network, TSN (Time Sensitive Networking), an optical transport network, etc. The native TN system follows instructions from a generalized TN system management node.

[0068] like Figure 7As shown, the native TN system is composed of a native TN system management node, a second native system management node, a native TN system terminal adapter and a native TN.

[0069] The unique TN system management node has an NBI in the universal TN system management node. The information obtained by the universal system management node from the 5GS is passed to the NBI of the fixed TN system management node.

[0070] The second unique TN system management node does not have an NBI in the generalized TN system management node, and cooperates with the unique TN system management node to control the unique TN system.

[0071] The native TN system terminal adapter is placed at the entry and exit sides of the native TN system. The native TN system terminal adapter adds necessary information to the data to be transferred and performs necessary conversion to form it in a format that can be transferred within the native TN system.

[0072] Import the following generalized user plane path setting process using the generalized TN system. Figure 8 The timing diagram of the Figure 9 、 Figure 10 or Figure 11 Timing diagram of Figure 9 、 Figure 10 or Figure 11 The timing diagram of the Figure 12 Timing diagram of .

[0073] Figure 8 This is a timing diagram for illustrating an example of the start of PDU session establishment in an embodiment of the present invention. In step S101, UE 20 sends a PDU session establishment request to AMF 30C (see non-patent document 3). In the next step S102, AMF 30C sends a PDU session generation request to SMF 30D. In the next step S103, SMF 30D obtains PCC rules (which may also be default PCC rules) from PCF 30E (see non-patent document 3). PCC rules may include TSCAC (Time Sensitive Communication Assistance Container).

[0074] In the following step S104, the SMF 30D determines the GW, similar to the case of determining the UPF in the existing specification (see Non-Patent Document 3). In the following step S105, similar to the case of setting the UPF in the existing specification, a PFCP session establishment request is sent to the GW 30F (see Non-Patent Document 3). This PFCP session establishment request can be Ngw_PFCPSessionEstablishmentrequest, which is a SBI-ized version of the PFCP Session Establishment Request in Section 7.5.2.1 of Non-Patent Document 4.

[0075] In the next step S106, GW 30F sends a PFCP session establishment response to SMF 30D (see non-patent document 3). This PFCP session establishment response can be Ngw_PFCPSessionEstablishmentresponse, which is a SBI-ized version of the PFCP session establishment response (PFCPSession Establishment Response) in Section 7.5.3.1 of non-patent document 4. This PFCP session establishment response includes the Created PDR (Packet Detection Rule) IE. The Created PDR includes the Local F-TEID (Fully Qualified Tunnel Endpoint Identifier). However, GW 30F may also set an IP address for the Local F-TEID instead of setting a TEID.

[0076] In the next step S107, SMF 30D sends a PDU session resource setup request to RRC-NF 30B. The PDU session resource setup request may include the PDU session resource setup request forwarding IE (PDUSession Resource Setup Request Transfer IE) of 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 forwarding IE (PDUSession Resource Setup Request Transfer IE) may include UL NG-U UP TNL information IE (ULNG-U UP TNL Information IE). SMF 30D may set the IP address in the UL NG-U UP TNL information IE (UL NG-U UP TNLInformation IE) without setting the GTP-TEID.

[0077] In the next step S108, RRC-NF 30B sends a PDCP bearer context setup request to gNB-PDCP 30A. The PDCP bearer context setup request may be Ngnb-pdcp_BearerContextSetup request obtained by SBIing 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 To Setup List IE (PDU Session Resource To Setup List IE) (refer to Section 9.3.3.2 of Non-Patent Document 6). The PDU Session Resource To Setup List IE may include an NG UL UP Transport Layer Information IE. RRC-NF 30B may set the IP address in the NG UL UP Transport Layer Information IE without setting the GTP-TEID.

[0078] 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 may be the Ngnb-pdcp_BearerContextSetup response obtained by SBIing section 9.2.2.2 of non-patent document 6. The PDCP bearer context setup response may include established service feature information. The PDCP bearer context setup response may include a PDU Session Resource Setup List IE (see section 9.3.3.5 of non-patent document 6). The PDU Session Resource Setup List IE may include an NG DL UP Transport Layer Information IE. gNB-PDCP 30A may set the IP address in the NG DL UP Transport Layer Information IE, but not the GTP-TEID.

[0079] In the next step S110, RRC-NF 30B sends a PDU session resource setup response to SMF 30D. The PDU session resource setup response may include the PDU session resource setup response forwarding IE (PDUSession Resource Setup Response Transfer IE) of Section 9.3.4.2 of non-patent document 5. The PDU session resource setup response may include established service feature information. The PDU session resource setup response forwarding IE (PDU Session Resource SetupResponse Transfer IE) may include the DL QoS Flow per TNLInformation IE (9.3.4.2 of non-patent document 5) of each TNL information IE. RRC-NF 30B may 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 of each TNL information IE without setting the GTP-TEID.

[0080] Figure 9This is a sequence diagram illustrating an example of TN path setup in the case of a GTP-U native TN system in an embodiment of the present invention. In step S201 following step S110, the SMF 30D sends a TN path setup request, a new message, to the generalized TN system management node (hereinafter also referred to as "GTNMF"). This message is SBI-ized and may be named something like Ngtnmf_TNpathSetup request. This message may include PCC rules (which may also be default PCC rules), service feature information presented by the gNB-PDCP 30A, a UL (uplink) destination IP address presented by the GW 30F, and a DL (downlink) destination IP address presented by the gNB-PDCP 30A.

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

[0082] In the next step S204, the STNMFgtp-u 30H transmits the DL destination IP address, configured based on the PCC rule, to the GTP-U native TN system termination adapter 30J adjacent to the GW. In the next step S205, the GTP-U native TN system termination adapter 30J adjacent to the GW selects a UL GTP-U TEID and transmits it to the STNMFgtp-u 30H.

[0083] In the following step S206, the STNMFgtp-u 30H sends the settings based on the PCC rule, the UL destination IP address, and the UL GTP-U TEID to the GTP-U native TN system termination adapter 30I adjacent to the gNB-PDCP. In the following step S207, the GTP-U native TN system termination adapter 30I adjacent to the gNB-PDCP selects a DL GTP-U TEID and sends it to the STNMFgtp-u 30H.

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

[0085] Figure 10 This is a sequence diagram illustrating an example of TN path setup in the case of a TSN-specific TN system according to an embodiment of the present invention. In step S301 following step S110, the SMF 30D sends a TN path setup request as a new message to the generalized TN system management node (hereinafter also referred to as "GTNMF"). This message is SBI-ized and may be named something like Ngtnmf_TNpathSetup request. This message may include PCC rules (which may also be default PCC rules), service feature information presented by the gNB-PDCP 30A, the UL destination IP address presented by the GW 30F, and the DL destination IP address presented by the gNB-PDCP 30A.

[0086] 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 rules, service feature information, UL destination IP address, and DL destination IP address to the TSN-specific TN system management node (hereinafter referred to as "STNMFtsn") operating as CUC (Centralized User Configuration).

[0087] In the next step S304, STNMFtsn 30K generates a merge flow request condition based on the information received in step S303, and sends the merge flow request condition to the second TSN-specific TN system management node (hereinafter also referred to as "STNMF2tsn") acting as a CNC (Central Network Controller) (see Non-Patent Document 7). In the next step S305, STNMF2tsn30L sends the merge terminal communication setting to STNMFtsn 30K.

[0088] In the following steps S306a and S306b, based on the combined terminal communication settings, STNMFtsn 30K sets up the TSN native TN system terminal adapter 30M adjacent to the gNB-PDCP and the TSN native TN system terminal adapter 30N adjacent to the GW, which act as the TSN sender / receiver (talker / listener). In the following step S307, STNMF2tsn 30L sets up the TSN network interior including the TSN bridge. In the following step S308, STNMF2tsn 30L sends a TN path setup completion message to STNMFtsn 30K. In the following step S309, STNMFtsn 30K sends a TN path setup completion message to GTNMF 30G.

[0089] Figure 11 This is a sequence diagram for illustrating Example (1) of TN path setup in the case of an APN-specific TN system in an embodiment of the present invention. In step S401 following step S110, the SMF 30D sends a TN path setup request as a new message to the generalized TN system management node (hereinafter also referred to as "GTNMF"). This message is SBI-ized and may be named Ngtnmf_TNpathSetup request. This message may include PCC rules (which may also be default PCC rules), service feature information presented by the gNB-PDCP 30A, a UL destination IP address presented by the GW 30F, and a DL destination IP address presented by the gNB-PDCP 30A.

[0090] In the next step S402, the GTNMF 30G recognizes the APN (All-Photonic Network) to be used through the network setting. In the next step S403, the GTNMF 30G sends a request to the Apps in the OpenAPN Controller (see Non-Patent Document 8). Figure 3 .3.1-2) The APN-specific TN system management node (hereinafter also referred to as "STNMFapn") that performs the action sends PCC rules, service feature information, UL destination IP address, and DL destination IP address.

[0091] In the next step S404, the STNMFapn 30O generates appropriate control information based on the information received in step S403, and transmits it to various control functions, such as static dynamic path control functions, band control functions, path control functions, monitoring functions, and the like, within the Open APN Controller functioning as the group of the 2nd APN-specific TN system management nodes (hereinafter also referred to as "STNMF2apn_X").

[0092] In the next steps S405a and S405b, the STNMF2apn_X 30P sets the APN-specific TN system termination adapter 30Q adjacent to the gNB-PDCP and the APN-specific TN system termination adapter 30R adjacent to the GW, which operate as the forwarder type 2 (refer to Non-Patent Literature 8 Figure 3 .3.1-2).

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

[0094] Figure 12 is a sequence chart for explaining example (1) of the PDU session establishment completion in the embodiment of the present application. In step S501 following step S209, step S309, or step S408, the GTNMF 30G transmits the TN path setup completion to the SMF 30D. The TN path setup completion can be a new message Nsmf_TNpathSetupNotify request. The message can include a new IE, TN path setup completion notification IE, which notifies that the path setup in the general TN system is completed.

[0095] In the next step S502, SMF 30D sends a PDU session resource modification request to RRC-NF 30B. The PDU session resource modification request may include the PDU session resource modification request forwarding IE (PDUSession Resource Modify Request Transfer IE) in Section 9.3.4.3 of Non-Patent Document 5. The PDU session resource modification request forwarding IE (PDUSession Resource Modify Request Transfer IE) may include the TN setup completion notification IE.

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

[0097] In the next step S504, RRC-NF 30B sends a PDCP Bearer Context Modification Request to gNB-PDCP 30A. This PDCP Bearer Context Modification Request may be a Ngnb-pdcp_BearerContextModification request obtained by SBIing Section 9.2.2.4 of Non-Patent Document 6, which includes the TN Path Setup Complete Notification IE.

[0098] Here, in the above-mentioned universal TN system, it is necessary to import a series of identifiers (such as TEID, QFI (QoS Flow Identifier)) statically set in T-PDU for multiplexing and processing identification separation among the functions provided by GTP-U, and support functions equivalent to those of the GTP-U network on the IP network.

[0099] In connection with this, in existing specifications using GTP-U, processing is separated based on TEID and QFI, so it is difficult to perform processing branching for multiple flows with the same QFI but different TSCAI in the user plane and the transport network.

[0100] Furthermore, although the RAN considers the radio resource status to determine whether a QoS flow can be established, the process involves first setting the QFI in the UPF and then notifying the RAN of the set QFI. Therefore, rework is required if a QoS flow cannot be established.

[0101] Furthermore, there are many situations where it is not necessary to dynamically set an identifier for each individual T-PDU, such as when not in HO, when DC is not used, or when QoS control is not performed for each packet. Even in these situations, static identification of the required TEID and QFI is always required in GTP-U, resulting in a waste of communication resources.

[0102] Therefore, communication ports are introduced into the generalized TN system. A native TN system terminal adapter can have multiple ingress and egress communication ports for a single termination (e.g., a single GW, gNB-PDCP, or gNB-DU IP address) from the perspective of the generalized TN system. Under the control of the native TN system management node or a second native TN system management node, an ingress communication port of a single termination is associated with an egress communication port of another termination.

[0103] The communication port allocation process is introduced in the generalized user plane path setting process. 5GS notifies the generalized TN system of the two terminations, the number of paths required between the terminations, and the service feature information determined after each path is confirmed in the RAN. The generalized TN system notifies the 5GS of the TN path setting completion information (for example, a list consisting of [termination A: inlet side communication port name ai1, termination B: outlet side communication port be1, path service feature information xx], [termination B: inlet side communication port name bi1, termination A: outlet side communication port ae1, path service feature information yy], etc.). One entry of the list included in the TN path setting completion information can be composed of the inlet side communication port name of termination A on one side, the outlet side communication port name of termination B on the other side, and the path service information between termination A and termination B. The list can also have a number of entries corresponding to the number of paths.

[0104] In addition, the following description takes the process between gNB-PDCP and GW (N3 interface) as an example, but it can also be applied similarly between gNB-DU and gNB-PDCP (F1-U interface), between two gNB-PDCPs (Xn-U interface), and between two GWs (N9 interface).

[0105] Figure 13This is a sequence diagram illustrating Example (2) of TN path setup in the case of an APN-specific TN system according to an embodiment of the present invention. In step S601 following step S110, the SMF 30D sends a TN path setup request as a new message to the generalized TN system management node GTNMF 30G. This message is SBI-ized and may be named something like Ngtnmf_TNpathSetup request. This message may include the UL destination IP address indicated by the GW 30F, the DL destination IP address indicated by the gNB-PDCP 30A, the number of paths required between the GW and gNB-PDCP, and service feature information for confirming and determining each path in the RAN.

[0106] In the next step S602, the GTNMF 30G recognizes the APN (All-Photonic Network) to be used through the network setting. In the next step S603, the GTNMF 300 sends a request to the Apps in the OpenAPN Controller (see Non-Patent Document 8). Figure 3 .3.1-2) The APN-specific TN system management node STNMFapn 30O that performs the action sends the UL destination IP address, the DL destination IP address, the required number of paths, and the service characteristic information of each path.

[0107] In the next step S604, 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 (Open APN Conroller) that functions as the second APN inherent TN system management node group STNMF2apn_X30P, such as static and dynamic path control functions, frequency band control functions, path control functions, monitoring functions, etc.

[0108] In the following steps S605a and S605b, STNMF2apn_X 30P is set as transponder type 2 (see Non-Patent Document 8). Figure 3 The APN-specific TN system termination adapter 30Q adjacent to the gNB-PDCP and the APN-specific TN system termination adapter 30R adjacent to the GW, which are performing operations in 3.1-2), are configured. The STNMF2apn_X 30P sets one or more ingress communication ports and one or more egress communication ports for each APN-specific TN system termination adapter, based on the number of required paths received from the GTNMF 30G.

[0109] In the next step S606, STNMF2apn_X 30P considers the required number of paths and the service characteristics of each path to set the optical aggregator and the optical switching amplifier (see Non-Patent Document 8). Figure 3 .3.1-2) within the APN network.

[0110] In the next step S607, each STNMF2apn_X 30P notifies the STNMFapn 30O of the setting results. In the next step S608, the STNMFapn 30O generates TN path setting completion information, i.e., a list consisting of [Termination A: ingress side communication port name ai1, Termination B: egress side communication port be1, path service characteristic information xx], [Termination B: ingress side communication port name bi1, Termination A: egress side communication port ae1, path service characteristic information yy], etc.

[0111] In step S609, the STNMFapn 300 sends a TN path setting completion message including the above-mentioned TN path setting completion information to the GTNMF 30G.

[0112] Figure 14 This is a sequence diagram for illustrating Example (2) of PDU session establishment completion in an embodiment of the present invention. In step S610 following step S609, the GTNMF 30G sends a TN path setup completion message to the SMF 30D. This TN path setup completion message may be a new message, Ngtnmf_TNpathSetupNotify request. This message may include a new IE, namely, a TN path setup completion notification IE, which notifies that path setup within the generalized TN system has been completed. Furthermore, this message may include the aforementioned TN path setup completion information IE as a new IE.

[0113] In the next step S611, SMF 30D sends a PDU session resource modification request to RRC-NF 30B. The PDU session resource modification request may include the PDU session resource modification request forwarding IE (PDUSession Resource Modify Request Transfer IE) in Section 9.3.4.3 of Non-Patent Document 5. The PDU session resource modification request forwarding IE (PDUSession Resource Modify Request Transfer IE) may include the TN setup completion notification IE and the TN path setup completion information IE.

[0114] In step S612, SMF 30D sends a PFCP Session Modification Request to GW 30F. This PFCP Session Modification Request can be a PFCP Session Modification Request or can include a TN Path Setup Complete Notification IE and a TN Path Setup Complete Information IE. In step S613, GW 30F confirms the TN Path Setup Complete Information IE and sets the internal communication port.

[0115] In step S614, RRC-NF 30B sends a PDCP Bearer Context Modification Request to gNB-PDCP 30A. This PDCP Bearer Context Modification Request may be a Ngnb-pdcp_BearerContextModificationrequest, obtained by SBI-ing Section 9.2.2.4 of Non-Patent Document 6, which includes the TN Path Setup Complete Notification IE and the TN Path Setup Complete Information IE. In the following step S615, gNB-PDCP 30A checks the TN Path Setup Complete Information IE and sets the internal communication port.

[0116] In the above-described embodiment, a UL destination IP address and a DL destination IP address are used. However, the UL destination and the DL destination may be any destination for routing and are not limited to IP addresses.

[0117] Through the above-mentioned embodiment, a universal TN system is introduced and a universal user plane path setting process is executed, thereby enabling the transmission network of the user plane to be independently developed or independently selected.

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

[0119] (Device Structure)

[0120] Next, we will describe the functional configuration examples of base station 10, network node 30, and terminal 20 that implement the above-described processes and operations. Base station 10, network node 30, and terminal 20 include functions for implementing the above-described embodiments. However, base station 10, network node 30, and terminal 20 may each include only a portion of the functions described in the embodiments.

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

[0122] Figure 15 1 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30. Figure 15 As shown, the base station 10 includes a transmitting unit 110 , a receiving unit 120 , a setting unit 130 , and a control unit 140 . Figure 15The functional structure shown is merely an example. As long as the operations described in the embodiments of the present invention can be implemented, the functional divisions and names of the functional units may be arbitrary. Furthermore, the network node 30 may have the same functional structure as the base station 10. Furthermore, a network node 30 having multiple distinct functions in the system architecture may be composed of multiple network nodes 30 separated by function.

[0123] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 or another network node 30 and transmitting the signal via wired or wireless means. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 or another network node 30 and obtaining, for example, higher-layer information from the received signals. A communication unit including the transmitter 110 and the receiver 120 may also be configured.

[0124] The setting unit 130 stores pre-set setting information and various setting information sent to the terminal 20 in a storage device, and reads out the setting information from the storage device as needed. The content of the setting information is, for example, information related to the generalized TN system.

[0125] As described in the embodiment, the control unit 140 performs processing related to PDCP in the network. Furthermore, the control unit 140 performs processing related to communication using the generalized TN system. Furthermore, the control unit 140 performs processing related to communication with the terminal 20. The functional units related to signal transmission in the control unit 140 may be included in the transmitter 110, while the functional units related to signal reception in the control unit 140 may be included in the receiver 120.

[0126] <Terminal 20>

[0127] Figure 16 2 is a diagram showing an example of the functional structure of the terminal 20. Figure 16 As shown, the terminal 20 includes a transmitting unit 210 , a receiving unit 220 , a setting unit 230 , and a control unit 240 . Figure 16 The functional structure shown is only an example. As long as the operations involved in the embodiments of the present invention can be implemented, the functional divisions and names of the functional units can be arbitrary. In addition, the communication device that serves as the resource holder 20 can also have the same functional structure as the terminal 20.

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

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

[0130] As described in the embodiment, the control unit 240 performs PDCP-related processing in the network. Functional units related to signal transmission in the control unit 240 may be included in the transmitter 210 , and functional units related to signal reception in the receiver 220 .

[0131] (Hardware Structure)

[0132] The block diagram used in the description of the above embodiment ( Figure 15 and Figure 16 ) shows blocks in functional units. These functional blocks (structural parts) 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 can be implemented using one device that is physically or logically combined, or can be implemented using multiple devices by connecting two or more physically or logically separated devices directly or indirectly (for example, using wired or wireless connections). The functional blocks can also be implemented by combining software in the above-mentioned one device or the above-mentioned multiple devices.

[0133] Functions include, but are not limited to, judging, determining, determining, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, regarding, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. For example, a functional block (structural unit) that performs a transmitting function is referred to as a transmitting unit or a transmitter. In short, as described above, there is no particular limitation on the implementation method.

[0134] For example, the network node 30 , the terminal 20 , and the like in one embodiment of the present disclosure may also function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 17This figure shows an example of the hardware structure of a base station 10 and a terminal 20 according to one embodiment of the present disclosure. The network node 30 may have the same hardware structure as the base station 10. The base station 10 and the terminal 20 may be configured as computer devices that physically include 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.

[0135] In the following description, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and the terminal 20 may include one or more of the devices shown in the figures, or may exclude some of the devices.

[0136] The various functions in the base station 10 and the terminal 20 are implemented as follows: predetermined software (programs) are read into hardware such as the processor 1001 and the storage device 1002, so that the processor 1001 performs calculations and controls the communication of the communication device 1004 or controls at least one of the reading and writing of data in the storage device 1002 and the auxiliary storage device 1003.

[0137] Processor 1001 controls the entire computer by, for example, running an operating system. Processor 1001 may also be comprised of a central processing unit (CPU) that includes interfaces with peripheral devices, a control device, a computing device, registers, and the like. For example, control unit 140 and control unit 240 described above may also be implemented by processor 1001.

[0138] In addition, the processor 1001 reads a program (program code), a software module, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and performs various processes based on the program. As a program, a program that causes the computer to execute at least a part of the operations described in the above embodiments is used. For example, Figure 15 The control unit 140 of the base station 10 shown may also be implemented by a control program stored in the storage device 1002 and executed in the processor 1001. Figure 16 The control unit 240 of the terminal 20 shown can also be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. Although the various processes described above are performed by a single processor 1001, the various processes described above can also be performed 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 the network via a telecommunications line.

[0139] The storage 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), or the like. The storage 1002 can also be referred to as a register, a cache, a main memory (main storage), or the like. The storage 1002 is capable of holding a program (program code), a software module, or the like that can be executed in order to implement the communication method according to an embodiment of the present disclosure.

[0140] The auxiliary storage 1003 is a computer-readable recording medium, and can be constituted by at least one of, 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 (registered trademark) disk, a smart card, a flash memory (for example, a card, a stick, a Key drive), a Floppy (registered trademark) disk, a magnetic stripe, or the like. The above-described storage medium can be, for example, a database, a server, and another appropriate medium that includes at least one of the storage 1002 and the auxiliary storage 1003.

[0141] The communication device 1004 is hardware (a transceiver device) for performing communication 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, or the like. The communication device 1004 can also be constituted to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, or the like, in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transceiving antenna, an amplifier section, a transceiving section, a transmission path interface, or the like can also be implemented by the communication device 1004. The transceiving section can also be implemented physically or logically by a transmission section and a reception section.

[0142] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, or the like) that receives an input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, or the like) that implements an output to the outside. In addition, the input device 1005 and the output device 1006 can also be integrally constituted (for example, a touch panel).

[0143] Furthermore, the processor 1001, the storage device 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 may be configured using a single bus or different buses between devices.

[0144] Furthermore, the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), and may implement some or all of the functional blocks using this hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0145] Figure 18 2001 shows a structural example of a vehicle. Figure 18 As shown, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. The various forms and embodiments described in this disclosure may also be applied to a communication device mounted on vehicle 2001, such as communication module 2013.

[0146] The driving 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 wheel) and is configured to steer at least one of the front wheels and the rear wheels based on the user's operation of the steering wheel.

[0147] 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 to 2029 included in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be referred to as an ECU (Electronic Control Unit).

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

[0149] The information service unit 2012 is composed of various devices such as a car navigation system, audio system, speakers, televisions, and radios that provide (output) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 2012 uses information obtained from external devices via the communication module 2013 and other means to provide various multimedia information and multimedia services to the passengers of the vehicle 2001. The information service unit 2012 may include input devices that receive input from the outside (e.g., a keyboard, mouse, microphone, switches, buttons, sensors, touch panels, etc.) and output devices that provide output to the outside (e.g., a display, speakers, LED lights, touch panels, etc.).

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

[0151] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 can transmit and receive data via the communication port 2033 with the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 in the electronic control unit 2010, memory (ROM, RAM) 2032, and sensors 2021 to 2029 included in the vehicle 2001.

[0152] The communication module 2013 is controlled by the microprocessor 2031 of the electronic control unit 2010 and is a communication device capable of communicating with external devices. For example, various information can be transmitted and received with the external device via wireless communication. The communication module 2013 can be located inside or outside the electronic control unit 2010. The external device can also be, for example, a base station or a mobile station.

[0153] The communication module 2013 can transmit at least one of the signals input to the electronic control unit 2010 from the various sensors 2021-2028, information obtained based on these signals, and information based on external (user) input received 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, and the like can also be referred to as input units that receive input. For example, the PUSCH transmitted by the communication module 2013 can include information based on these inputs.

[0154] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from external devices and displays it on the information service unit 2012 included 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 a display, speaker, or other device based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH)). Furthermore, the communication module 2013 stores various information received from external devices in a memory 2032 accessible to the microprocessor 2031. Based on the information stored in the memory 2032, 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, and sensors 2021 to 2029 included in the vehicle 2001.

[0155] (Summary of Implementation Methods)

[0156] As described above, according to an embodiment of the present invention, a network node is provided, comprising: a receiving unit that receives information including an uplink destination address, i.e., a UL destination address, a downlink destination address, i.e., a DL destination address, the number of paths, and service characteristic information of each path from a first network node; a control unit that generates information for setting up a transmission network, i.e., a TN, based on the information; and a sending unit that sends the generated information to a second network node that controls the TN, wherein the receiving unit receives various setting results within the network from the second network node, the control unit generates TN path setting completion information including a list based on the various setting results, the list having a name of an ingress-side communication port at one end, a name of an egress-side communication port at the other end, and path service characteristic information as one entry, and having a number of entries corresponding to the number of paths, and the sending unit sends a TN path setting completion message including the TN path setting completion information to the first network node.

[0157] According to the above structure, a universal TN system is introduced and a universal user plane path setting process is executed, thereby enabling independent development or selection of the user plane transport network. In other words, a universal TN (Transport Network) system can be introduced.

[0158] The second network node can control the time-sensitive network (TSN). According to this structure, TSN can be used as a generalized TN system.

[0159] The second network node can control the all-photonic network, namely APN. According to this structure, the APN can be used as a generalized TN system.

[0160] The transmitting unit may transmit the generated information for setting the inside of the TN to a plurality of the second network nodes each having a different function related to the APN. According to this configuration, the APN can be used as a generalized TN system.

[0161] Further, according to the embodiment of the present application, there is provided a communication method, wherein the following steps are performed by a network node: receiving, from a first network node, information including an uplink destination address (UL destination address), a downlink destination address (DL destination address), a number of paths, and service characteristic information of each path; generating information for setting a transport network internal (TN internal) based on the information; transmitting the generated information to a second network node that controls the TN; receiving each setting result of the network internal from the second network node; generating TN path setting completion information including a list, which has a number of entries corresponding to the number of paths, and in which each entry includes an entry-side communication port name of one end, an exit-side communication port name of the other end, and path service characteristic information; and transmitting the TN path setting completion including the TN path setting completion information to the first network node.

[0162] According to the above configuration, a general TN system is introduced, and a general user plane path setting process is executed, whereby the transport network of the user plane can be developed or selected independently. That is, a general TN (Transport Network) system can be introduced.

[0163] (Supplement to Embodiment)

[0164] The above describes the embodiments of the present application, but the disclosed application is not limited to such embodiments, and those skilled in the art will understand various modifications, changes, alternatives, substitutions, and the like. Specific numerical examples are used for facilitating understanding of the application, but these numerical examples are only one example, and any appropriate value can be used unless specifically indicated. The items in the above description are not essential to the present application, and two or more items described in the items can be combined as needed, or an item described in one item can be applied to an item described in another item (as long as there is no contradiction). The boundaries of the functional blocks or processing blocks in the functional block diagram do not necessarily correspond to the boundaries of physical components. The actions of multiple functional blocks can be performed by one physical component, or the actions of one functional block can be performed by multiple physical components. As for the processing procedures described in the embodiments, the order of the processing can be changed without contradiction. The base station 10 and the terminal 20 are described using a functional block diagram for facilitating the description of the processing, but such devices can also be implemented by hardware, software, or a combination thereof. Software that acts according to the embodiments of the present application by the processor of the base station 10 and software that acts according to the embodiments of the present application by the processor of the terminal 20 can each 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 (HDD), a removable disk, a CD-ROM, a database, a server, and other appropriate arbitrary storage media.

[0165] Further, the notification of the information is not limited to the forms / embodiments described in the present disclosure, and other methods can be used. For example, the notification of the information can be implemented by 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), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof. Further, the RRC signaling can be referred to as an RRC message, and for example, can be an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0166] Each form / embodiment described in the present disclosure can also be applied to a mobile communication system using LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), 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 At least one of 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), other appropriate systems, and next-generation systems that are expanded, modified, created, or specified based on these systems. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be used.

[0167] The processing procedures, timings, and flows of each form / implementation described in this specification may be rearranged in order unless there is a conflict. For example, the methods described in this disclosure use an illustrative order to present the elements of various steps, but are not limited to the specific order presented.

[0168] In this specification, specific actions performed by base station 10 may also be performed by its upper node, depending on the situation. In a network consisting of one or more network nodes including base station 10, it is obvious that various actions performed for communication with terminal 20 can be performed by at least one of base station 10 and other network nodes other than base station 10 (e.g., MME or S-GW, but not limited to these). While the above example illustrates a single other network node other than base station 10, the other network node may also be a combination of multiple other network nodes (e.g., MME and S-GW).

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

[0170] Input or output information can be stored in a specific location (e.g., memory) or managed using a management table. Input or output information can be overwritten, updated, or appended. Output information can also be deleted. Input information can also be sent to other devices.

[0171] The determination in the present disclosure may be performed using a value represented by one bit (0 or 1), a Boolean value (Boolean: true or false), or a comparison of numerical values ​​(for example, comparison with a predetermined value).

[0172] Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or by other names, shall be interpreted broadly to refer to instructions, sets of instructions, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0173] Furthermore, software, commands, information, and the like may be transmitted and received via a transmission medium. For example, if software is transmitted from a web page, server, or other remote source using at least one of a wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and a wireless technology (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0174] The information, signals, etc. described in this disclosure may also be represented using any of a variety of different technologies. For example, data, commands, instructions, information, signals, bits, symbols, chips, etc. that may be referred to in the entire description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0175] In addition, the terms used in this disclosure and those necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may also be referred to as a carrier frequency, a cell, or a frequency carrier.

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

[0177] In addition, the information, parameters, etc. described in this disclosure can be expressed using absolute values, relative values ​​relative to predetermined values, or other corresponding information. For example, wireless resources can be indicated using indexes.

[0178] The names used for the above parameters are non-limiting in any respect. Furthermore, the formulas and the like using these parameters may sometimes differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, and therefore the names assigned to these channels and information elements are non-limiting in any respect.

[0179] In this disclosure, terms such as "base station (BS)," "wireless base station," "base station apparatus," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" are used interchangeably. Base stations are also sometimes referred to as macrocells, small cells, femtocells, and picocells.

[0180] A base station can accommodate one or plural (for example, 3) cells. In a case where the base station accommodates plural cells, the coverage area of the base station as a whole can be divided into plural smaller areas, and each of the smaller areas can also be provided with a communication service by a base station subsystem (for example, a small-sized base station for indoor use (RRH: Remote Radio Head)). The term "cell" or "sector" refers 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 a communication service in the coverage range.

[0181] In the present disclosure, the base station transmitting information to the terminal can also be replaced with the base station instructing the terminal of a control·action based on the information.

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

[0183] For a mobile station, the following terms are also used by those skilled in the art: subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0184] 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. Furthermore, at least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to an object that can move, and the moving speed is arbitrary. Furthermore, of course, this also includes situations where the mobile body is stationary. Examples of mobile bodies include, but are not limited to, vehicles, transport vehicles, cars, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, two-wheeled trailers (rear cars), rickshaws, ships and other watercraft, airplanes, rockets, artificial satellites, Drones (registered trademark), multi-rotor helicopters, quadcopters, balloons, and objects mounted thereon. Furthermore, the mobile body may also be a mobile body that moves autonomously based on operating instructions. It may be a means of transportation (such as a car, airplane, etc.), a mobile body that moves unmanned (such as a drone, self-driving car, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station also 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.

[0185] In addition, the base station in the present disclosure can also be replaced by a user terminal. For example, the various forms / implementations of the present disclosure can also be applied to a structure in which the communication between the base station and the user terminal is replaced by the communication between multiple terminals 20 (for example, it can also be called D2D (Device-to-Device: device to device), V2X (Vehicle-to-Everything: vehicle to everything system), etc.). In this case, it can also be set as a structure in which the terminal 20 has the functions of the above-mentioned base station 10. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (such as "side"). For example, uplink channels, downlink channels, etc. can also be replaced by side channels.

[0186] Likewise, the user terminal in the present disclosure may be replaced by a base station. In this case, the base station may also have the functions of the user terminal.

[0187] The terms "determining" and "deciding" as used in the present disclosure include a wide variety of actions. For example, "determining" or "deciding" can include "determining" or "deciding" that a state of affairs has been judged, calculated, computed, processed, derived, investigated, searched (e.g., searched in a table, a database, or other data structure), ascertained, or the like. In addition, "determining" or "deciding" can include "determining" or "deciding" that a state of affairs has been received (e.g., received information), transmitted (e.g., transmitted information), input, output, accessed (e.g., accessed data in a memory), or the like. Furthermore, "determining" or "deciding" can include "determining" or "deciding" that a state of affairs has been resolved, selected, chosen, established, compared, or the like. That is, "determining" or "deciding" can include "determining" or "deciding" that a certain action has been performed. In addition, "determining" or "deciding" can be replaced by "assuming", "expecting", "considering", or the like.

[0188] The terms "connected" and "coupled" or all modifications thereof are intended to mean all possible direct or indirect connections or couplings between two or more elements. Such a connection or coupling between elements can include one or more intervening elements. The connection or coupling between elements can be physical or logical, or a combination thereof. For example, "connected" can be replaced by "accessed". In the present disclosure, it can be considered that two elements are "connected" or "coupled" to each other using at least one of a wire, a cable, and a printed electrical connection, and as some non-limiting and non-inclusive examples, electromagnetic energy having a wavelength in the radio frequency region, the microwave region, and the light region (including both visible and invisible) is used to "connect" or "couple" to each other.

[0189] The reference signal may be referred to as RS (Reference Signal) for short, or may be called a pilot signal depending on the applied standard.

[0190] The phrase “based on” used in this disclosure does not mean “based only on” unless explicitly stated otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”

[0191] Any reference to an element using the terms "first," "second," etc., as used in this disclosure, does not necessarily limit the number or order of these elements. These terms may be used in this disclosure as a convenient way to distinguish between two or more elements. Therefore, a reference to a first element and a second element does not mean that only two elements can be used or that the first element must precede the second element in any form.

[0192] The “unit” in the configuration of each of the above-mentioned devices may be replaced with a “section,” “circuit,” “device,” or the like.

[0193] When the terms "include," "including," and variations thereof are used in this disclosure, these terms, like the term "comprising," are intended to be inclusive. Furthermore, the term "or" used in this disclosure does not mean an exclusive or.

[0194] In the present disclosure, when an article is added by translation, such as a, an, and the in English, the present disclosure also includes cases where the noun following the article is in a plural form.

[0195] In this disclosure, the phrase "A and B are different" can mean "A and B are different from each other." Alternatively, the phrase can mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0196] Each form / implementation described in this disclosure may be used individually or in combination, and may be switched between them depending on the execution. Furthermore, notification of predetermined information (e.g., notification of "yes X") is not limited to being performed explicitly, but may also be performed implicitly (e.g., not notifying the predetermined information).

[0197] While the present disclosure has been described in detail above, it should be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in various modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is for illustrative purposes only and does not have any limiting meaning on the present disclosure.

[0198] Label Description

[0199] 10: Base Station

[0200] 110: Sending Department

[0201] 120: Receiving Department

[0202] 130: Setting Department

[0203] 140: Control Department

[0204] 20: Terminal

[0205] 210: Sending Department

[0206] 220: Receiving Department

[0207] 230: Setting Department

[0208] 240: Control Department

[0209] 30: Network node

[0210] 1001: Processor

[0211] 1002: Storage device

[0212] 1003: Auxiliary storage device

[0213] 1004: Communication device

[0214] 1005: Input device

[0215] 1006: Output device

Claims

1. A network node, comprising: a receiving unit configured to receive, from the first network node, information including an uplink destination address (UL destination address), a downlink destination address (DL destination address), the number of paths, and service characteristic information of each path; a control unit that generates information for setting the inside of a transmission network (TN) based on the information; and a sending unit that sends the generated information to a second network node that controls the TN, The receiving unit receives various setting results within the network from the second network node, The control unit generates TN path setting completion information including a list based on the setting results, the list including a name of an entry-side communication port for termination of one party, a name of an exit-side communication port for termination of the other party, and path service characteristic information as one entry, and having a number of entries corresponding to the number of paths. The transmitting unit transmits a TN path setting completion message including the TN path setting completion information to the first network node.

2. The network node according to claim 1, wherein: The second network node controls a time-sensitive network (TSN).

3. The network node according to claim 1, wherein: The second network node controls the all-photonic network, namely, the APN. The network node according to claim 3 , wherein: The transmitting unit transmits the generated information for setting the inside of the TN to the plurality of second network nodes each having a different function related to the APN.

5. A communication method, wherein: The network nodes perform the following steps: receiving, from the first network node, information including an uplink destination address (UL destination address), a downlink destination address (DL destination address), the number of paths, and service characteristic information of each path; Based on the information, information for setting the internal part of the transmission network, i.e., the internal part of the TN, is generated; sending the generated information to a second network node controlling the TN; receiving various setting results within the network from the second network node; Based on the respective setting results, generating TN path setting completion information including a list, the list including a name of an ingress-side communication port of one end point, a name of an egress-side communication port of the other end point, and path service characteristic information as one entry, and having a number of entries corresponding to the number of the paths; and A TN path setting completion message including the TN path setting completion information is sent to the first network node.

Images