JP7581386B2 - Network node, communication method and transport - Google Patents

Description

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

For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies are being considered that meet the requirements of a large-capacity system, high data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and low power consumption (for example, non-patent document 1).

In the existing specifications for the NR network, there is an implicit assumption that a mobile communications operator corresponding to a PLMN (Public Land Mobile Network) that owns a gNB-DU (next generation Node B - Distributed Unit), gNB-CU-UP (next generation Node B - Central Unit - User Plane) and UPF (User plane function) owns the user data transmission paths between the gNB-DU and gNB-CU-UP and between the gNB-CU-UP and the UPF.

3GPP TS 38.300 V16.4.0 (2020-12)

In the NR network, the user data transmission paths between the gNB-DU and gNB-CU-UP, and between the gNB-CU-UP and UPF, may be owned by a transmission network operator independent of the mobile communications operator corresponding to the PLMN. However, the specifications did not establish an interface for mobile communications operators corresponding to other PLMNs to use the user data transmission paths.

The present invention has been made in consideration of the above points, and aims to improve the utilization efficiency of user data transmission paths in wireless communication systems.

According to the disclosed technology, when establishing a PDU (Protocol Data Unit) session, a control unit selects a UPF (User Plane Function) and a transmission network operator, and encodes information indicating the transmission network operator and a service type provided by the transmission network operator to determine a network instance; and a transmission unit transmits the network instance to the UPF.
A network node is provided that has a receiving unit that receives a first TEID (Tunnel Endpoint Identifier) corresponding to the uplink from the UPF and receives a second TEID corresponding to the downlink from a gNB-CU-CP (next generation Node B - Central Unit - Control Plane), and the transmitting unit transmits the first TEID, the second TEID, and information indicating an interface corresponding to a PLMN (Public Land Mobile Network) to a transport installed between the UPF and a gNB-CU-UP (next generation Node B - Central Unit - User Plane) in a data transmission path, thereby establishing the PDU session.

In addition, the system includes a receiving unit that receives from an SMF (Session Management Function) a first TEID (Tunnel Endpoint Identifier) corresponding to the uplink, a second TEID corresponding to the downlink, and information indicating an interface corresponding to a PLMN (Public Land Mobile Network), and a control unit that sets up a data transmission path between a UPF (User Plane Function) and a gNB-CU-UP (next generation Node B - Central Unit - User Plane) based on the first TEID, the second TEID, and the information indicating the interface corresponding to the PLMN, and a transport is provided in which the first TEID is transmitted from the UPF to the SMF and the second TEID is transmitted from the gNB-CU-CP (next generation Node B - Central Unit - Control Plane) to the SMF.

Furthermore, according to the disclosed technology, a network node is provided that, when establishing a PDU session, has a control unit that selects a gNB-CU-UP and a transmission network operator, and determines a network instance by encoding information indicating the transmission network operator and the service type provided by the transmission network operator, a transmitting unit that transmits the network instance to the gNB-CU-UP, and a receiving unit that receives a fifth TEID corresponding to the uplink from the gNB-CU-UP and a sixth TEID corresponding to the downlink from a gNB-DU (next generation Node B - Distributed Unit), wherein the transmitting unit transmits the fifth TEID, the sixth TEID, and information indicating an interface corresponding to a PLMN to a transport installed between the gNB-CU-UP and the gNB-DU in a data transmission path, thereby establishing the PDU session.

In addition, the device has a receiving unit that receives a fifth TEID (Tunnel Endpoint Identifier) corresponding to the uplink from a gNB-CU-CP (next generation Node B - Central Unit - Control Plane), a sixth TEID corresponding to the downlink, and information indicating an interface corresponding to a PLMN (Public Land Mobile Network), and a control unit that sets up a data transmission path between a gNB-CU-UP (next generation Node B - Central Unit - User Plane) and a gNB-DU (next generation Node B - Distributed Unit) based on the fifth TEID, the sixth TEID, and the information indicating the interface corresponding to the PLMN, and transport is provided in which the fifth TEID is transmitted from the gNB-CU-UP to the gNB-CU-CP and the sixth TEID is transmitted from the gNB-DU to the gNB-CU-CP.

The disclosed technology makes it possible to improve the utilization efficiency of user data transmission paths in wireless communication systems.

FIG. 1 is a diagram illustrating an example of a communication system. FIG. 1 is a diagram illustrating an example of a network configuration according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a transmission path according to an embodiment of the present invention. A sequence diagram for explaining an example (1) of establishing a PDU session in an embodiment of the present invention. A sequence diagram for explaining an example (2) of establishing a PDU session in an embodiment of the present invention. A sequence diagram for explaining an example (3) of establishing a PDU session in an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a functional configuration of a base station 10 according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 20 according to an embodiment of the present invention. 2 is a diagram illustrating an example of a hardware configuration of a base station 10 or a terminal 20 according to an embodiment of the present invention.

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

Existing technology is used as appropriate in the operation of the wireless communication system of the embodiment of the present invention. However, the existing technology is, for example, the existing LTE, but is not limited to the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR) unless otherwise specified.

In addition, in the embodiment of the present invention described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel) used in existing LTE are used. This is for convenience of description, and similar signals, functions, etc. may be called by other names. In addition, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, NR-PDCCH, NR-PDSCH, NR-PUCCH, NR-PUSCH, etc. However, even if a signal is used in NR, it is not necessarily specified as "NR-".

In addition, in an embodiment of the present invention, the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or another method (e.g., Flexible Duplex, etc.).

In addition, in an embodiment of the present invention, when radio parameters, etc. are "configured," this may mean that predetermined values are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are configured.

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 multiple network nodes 30. In the following, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. In addition, the "connection" described below may be a logical connection or a physical connection.

The RAN (Radio Access Network) is a network node 30 having a radio access function, which may 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 functions such as a RAN interface termination, a NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU (Protocol Data Unit) session point to the outside that interconnects with a DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and the DN constitute a network slice. In the wireless communication network in the embodiment of the present invention, multiple network slices are constructed.

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 mutually connected via interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf, based on their respective services.

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

In the existing specifications for the NR network, there is an implicit assumption that a mobile communications operator corresponding to a PLMN (Public Land Mobile Network) that owns a gNB-DU (next generation Node B - Distributed Unit), a gNB-CU-UP (next generation Node B - Central Unit - User Plane), and a UPF (User plane function) owns the user data transmission path between the gNB-DU and the gNB-CU-UP and between the gNB-CU-UP and the UPF. In addition, notification of traffic characteristics to the transmission path is only by the DSCP (Differentiated Services Code Point) value.

In other words, in the existing specifications for NR networks, there is no concept of a transmission network operator, there is no way for a transmission network operator to accept traffic from multiple PLMNs on a call-by-call basis, and it is not possible to use transmission paths that obtain traffic characteristics off-path.

Therefore, each part of the transmission path is configured so that it can be viewed from the outside as a single UPF (hereinafter referred to as "transport"). The transport may operate as a single network node, or the transport may be further composed of multiple network nodes.

Figure 2 is a diagram showing an example of a network configuration in an embodiment of the present invention. As shown in Figure 2, the gNB-CU-CP (next generation Node B - Central Unit - Control Plane) is capable of setting up transport between the gNB-DU and the gNB-CU-UP. In addition, the SMF is capable of setting up transport between the gNB-CU-UP and the UPF.

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

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

2) The part located on the edge side as a transmission path. Hereinafter referred to as "aUPF."

3) The part located in the center as a transmission path. Hereinafter referred to as "bUPF."

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

The requesting PLMN can be distinguished by the instruction sent from the gNB-CU-CP or SMF to the transport. Furthermore, the instruction sent from the gNB-CU-CP to the gNB-CU-UP or the instruction sent from the SMF to the UPF includes an existing network instance. The network instance is a newly encoded name of the transmission network operator through which the gNB-CU-CP or SMF provides transport and the type of transmission service provided by the transmission network operator.

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

The communication procedure in an embodiment of the present invention is performed as follows: 1)-5).

1) When establishing a PDU session, the SMF sets an appropriate network instance value, for example based on S-NSSAI (Single-Network Slice Selection Assistance Information) and DNN (Data Network Name). The SMF selects an appropriate UPF and notifies it of the network instance value. The UPF selects an appropriate interface, which may be a TEID. The SMF selects an appropriate transport installed between the UPF and gNB-CU-UP and notifies the tSMF of the requesting PLMN information. The tSMF sets interfaces for the PLMN in the aUPF and bUPF and responds to the SMF.

2) The SMF notifies the gNB-CU-CP of the network instance value. The gNB-CU-CP selects an appropriate gNB-CU-UP and notifies it of the network instance value. The gNB-CU-UP selects an appropriate interface, which may be a TEID. The gNB-CU-CP selects an appropriate transport to be installed between the gNB-CU-UP and the gNB-DU, and notifies the tSMF of the requesting PLMN information. The tSMF configures interfaces for the PLMN in the aUPF and bUPF, and responds to the gNB-CU-CP.

3) The gNB-CU-CP configures the UL interface of the gNB-DU. At this time, the gNB-DU may determine the schedule using its internal MAC (Medium Access Control) function to obtain schedule assistance information. The gNB-DU may notify the determined traffic characteristics to a node that manages the transmission path between the gNB-DU and the gNB-RU (Remote Unit) (e.g., an OLT (Optical Line Terminal) in the case of a PON (Passive Optical Network)).

4) The gNB-CU-CP configures a transport DL interface between the gNB-CU-UP and the gNB-DU. At this time, the SMF may notify the transport of the traffic characteristics for which the gNB-DU's MAC function has been determined.

5) The SMF configures a DL interface of the transport installed between the UPF and the gNB-CU-UP. At this time, the SMF may notify the transport of the traffic characteristics for which the MAC function of the gNB-DU has been determined.

Figure 4 is a sequence diagram for explaining an example (1) of PDU session establishment in an embodiment of the present invention. In Figure 4, the TEID corresponding to the UL of UPF30B is 1, the TEID corresponding to the DL of bUPF30D is 2, the TEID corresponding to the UL is 3, the TEID corresponding to the DL of aUPF30E is 4, and the TEID corresponding to the UL is 5.

In step S101, UE 20 transmits UL information transfer to gNB-DU 10C. Next, gNB-DU 10C transmits UL-RRC message transfer to gNB-CU-CP 10A (S102). Next, gNB-CU-CP 10A transmits UL-NAS message transfer to AMF 30F (S103).

In step S104, AMF30F sends a PDU session establishment request to SMF30A. Then, SMF30A sends a PDU session establishment response to AMF30F (S105). Then, SMF30A performs UPF selection and transport selection (S106). Then, SMF30A sends a PFCP (Packet Forwarding Control Protocol) session establishment request to UPF30B (S107). The PFCP session establishment request in step S107 includes an appropriate network instance selected by the SMF based on the S-NSSAI and DNN. The network instance encodes the name of the transport network operator that provides the transport and the type of transmission service provided by the transport network operator (e.g., deterministic communication with slot allocation, etc.). Then, UPF30B sends a PFCP session establishment response to SMF30A (S108). In step S108, the UPF 30B selects an appropriate local F-TEID (Fully Qualified TEID) based on the network instance, and includes it in the PFCP session establishment response. In FIG. 4, an example in which F-TEID=1 is shown.

In step S109, SMF30A sends a PFCP session establishment request to tSMF30C. In the PFCP session establishment request in step S109, SMF30A assumes the use of other companies' transmission networks, sets the DL source interface and UL destination interface to PLMN specific core, sets the DL destination interface and UL source interface to PLMN specific access, and sets its own MCC (Mobile Country Code) / MNC (Mobile Network Code) as additional information in each setting. In addition, the PFCP session establishment request in step S109 includes information that sets the TEID corresponding to the outer header corresponding to UL to 1. SMF30A sets the transport as one UPF. tSMF30C sets each of the multiple UPFs in the transport based on the setting. The tSMF 30C behaves as a UPF for the SMF 30A and as an SMF for the transport. Note that the PLMN-specific core may indicate a UPF in the PLMN, and the PLMN-specific access may indicate a gNB-CU-UP in the PLMN.

In step S110, tSMF30C sends a PFCP session establishment request to bUPF30D. In the PFCP session establishment request in step S110, tSMF30C sets a PLMN-specific core to the DL source interface and UL destination interface, and sets information in which the TEID corresponding to the UL outer header is 1. Next, bUPF30D sends a PFCP session establishment response to tSMF30C in which the F-TEID corresponding to DL is set to 2 and the F-TEID corresponding to UL is set to 3 (S111). bUPF30D selects an appropriate TEID for DL corresponding to the UPF based on the PLMN-ID.

In step S112, tSMF30C sends a PFCP session establishment request to aUPF30E. In the PFCP session establishment request in step S112, tSMF30C sets PLMN-specific access to the DL destination interface and the UL source interface, and sets information that the TEID corresponding to the UL outer header is 3. Next, aUPF30E sends a PFCP session establishment response to tSMF30C in which the F-TEID corresponding to DL is set to 4 and the F-TEID corresponding to UL is set to 5 (S113). aUPF30E selects an appropriate UL TEID corresponding to the gNB based on the PLMN-ID.

In step S114, tSMF30C sends a PFCP session change request to bUPF30D with the TEID corresponding to the DL external header set to 4. Next, bUPF30D sends a PFCP session change response to tSMF30C (S115). Next, tSMF30C sends a PFCP session establishment response to SMF30A with the F-TEID corresponding to DL set to 2 and the F-TEID corresponding to UL set to 5 (S116). tSMC30C, bUPF30D and aUPF30E appear as a single UPF from the outside.

In step S117, SMF30A sends a PFCP session change request to UPF30B with the TEID corresponding to the DL outer header set to 2. Then, UPF30B sends a PFCP session change response to SMF30A (S118). Then, SMF30A sends a message transfer request including the UL endpoint IP address, information with GTP (GPRS Tunnelling Protocol)-TEID set to 5, and a network instance to AMF30F (S119). The message transfer request requests resource configuration for the PDU session. Then, AMF30F sends a message transfer response to SMF30A (S120).

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

In step S121, AMF30F sends a PDU session resource setting request to gNB-CU-CP10A, including the UL endpoint IP address, information indicating that GTP-TEID is 5, and a network instance. Here, gNB-CU-CP10A may select an appropriate gNB-CU-UP10B and a transmission network operator. The network instance may be an appropriate network instance selected by gNB-CU-CP10A based on the S-NSSAI and DNN. The network instance is encoded with the name of the transmission network operator providing the transport and the type of transmission service provided by the transmission network operator (e.g., deterministic communication with slot allocation, etc.).

Next, gNB-CU-CP10A sends a bearer setting request including the UL transport layer address, information that GTP-TEID is 5, and a network instance to gNB-CU-UP10B (S122). The network instance is an encoded version of the name of the transmission network operator providing the transport and the type of transmission service provided by the transmission network operator (e.g., deterministic communication with slot allocation, etc.). Next, gNB-CU-UP10B sends a bearer setting response to gNB-CU-CP10A in which GTP-TEID is set to 6 as the transport layer address corresponding to DL and GTP-TEID is set to 7 as the transport layer address corresponding to UL (S123). In step S123, gNB-CU-UP10B selects an appropriate local GTP-TEID based on the network instance in UL and includes it in the bearer setting response. FIG. 5 shows an example in which DL is GTP-TEID=6 and UL is GTP-TEID=7.

In step S124, gNB-CU-CP10A sends a PFCP session establishment request to tSMF30G. In the PFCP session establishment request in step S124, a PLMN-specific core is set to the DL source interface and the UL destination interface, and a PLMN-specific access is set to the DL destination interface and the UL source interface. In addition, the PFCP session establishment request in step S124 includes information that the TEID corresponding to the outer header corresponding to the UL is set to 7. gNB-CU-CP10A sets the transport as one UPF. tSMF30G sets each of the multiple UPFs in the transport based on the setting. tSMF30G behaves as a UPF for gNB-CU-CP10A and as an SMF for the transport.

In step S125, tSMF30G sends a PFCP session establishment request to bUPF30H. In the PFCP session establishment request in step S125, tSMF30G sets a PLMN-specific core to the DL source interface and the UL destination interface, and sets information that the TEID corresponding to the UL outer header is 7. Next, bUPF30H sends a PFCP session establishment response to tSMF30G in which the F-TEID corresponding to DL is set to 8 and the F-TEID corresponding to UL is set to 9 (S126). bUPF30H selects an appropriate DL TEID corresponding to the gNB-CU-UP based on the PLMN-ID.

In step S127, tSMF30G sends a PFCP session establishment request to aUPF30I. In the PFCP session establishment request in step S127, tSMF30G sets PLMN-specific access to the DL destination interface and the UL source interface, and sets information such that the TEID corresponding to the UL outer header is 9. Next, aUPF30I sends a PFCP session establishment response to tSMF30G in which the F-TEID corresponding to DL is set to 10 and the F-TEID corresponding to UL is set to 11 (S128). aUPF30I selects an appropriate UL TEID corresponding to the gNB-DU based on the PLMN-ID.

In step S129, tSMF30G sends a PFCP session change request to bUPF30H with the TEID corresponding to the DL external header set to 10. Next, bUPF30H sends a PFCP session change response to tSMF30G (S130). Next, tSMF30G sends a PFCP session establishment response to gNB-CU-CP10A with the F-TEID corresponding to DL set to 8 and the F-TEID corresponding to UL set to 11 (S131). tSMC30G, bUPF30H and aUPF30I appear as a single UPF from the outside.

In step S132, gNB-CU-CP10A transmits a PFCP session change request to gNB-CU-UP10B with the TEID corresponding to the DL outer header set to 8. Next, gNB-CU-UP10B transmits a PFCP session change response to gNB-CU-CP10A (S133). Next, gNB-CU-CP10A transmits a UE context change request to gNB-DU10C including the UL transport layer address and information with the GTP-TEID set to 11 (S134). Next, gNB-DU10C transmits a UE context change response to gNB-CU-CP10A including the DL transport layer address and information with the GTP-TEID set to 12 (S135).

In addition, by changing steps S132 and S133 to a bearer context change request and a bearer context change response, the amount of change in gNB-CU-UP can be reduced.

In step S136, gNB-CU-CP10A sends a PFCP session change request to tSMF30G with the TEID corresponding to the DL's outer header set to 12. Next, tSMF30G sends a PFCP session change request to aUPF30I with the TEID corresponding to the DL's outer header set to 12 (S137). Next, aUPF30I sends a PFCP session change response to tSMF30G (S138). Next, tSMF30G sends the PFCP session change response to gNB-CU-CP10A (S139).

In step S140, gNB-CU-CP10A transmits a DL-RRC message transfer to gNB-DU10C indicating that the PDU session establishment has been accepted. Next, gNB-DU10C transmits an RRCReconfiguration to UE20 indicating that the PDU session establishment has been accepted (S141). Next, UE20 transmits an RRCReconfigurationComplete to gNB-DU10C (S142). Next, gNB-DU10C transmits a UL-RRC message transfer to gNB-CU-CP10A indicating that the RRC reconfiguration has been completed (S143). Next, gNB-CU-CP10A sends a PDU session resource setting response to AMF30F indicating the DL endpoint IP address and the GTP-TEID is 6 (S144).

Figure 6 is a sequence diagram for explaining an example (3) of PDU session establishment in an embodiment of the present invention. In step S145, AMF30F transmits a PDU session update request indicating the DL endpoint IP address and the GTP-TEID being 6 to SMF30A. Then, SMF30A transmits a PFCP session change request with the TEID corresponding to the DL outer header set to 6 to tSMF30C (S146). Then, tSMF30C transmits a PFCP session change request with the TEID corresponding to the DL outer header set to 6 to aUPF30I (S147). Then, aUPF30I transmits a PFCP session change response to tSMF30G (S148). Then, tSMF30C transmits a PFCP session change response to SMF30A (S149). Next, SMF 30A sends a PDU session update response to AMF 30F (S150).

By applying the above-mentioned embodiment, it is possible to promote the growth of transmission network operators who provide transmission paths that have advanced transmission capabilities such as enabling deterministic communication with slot allocation, or have added value such as relaying via time synchronization servers. PLMNs can provide subscribers with advanced services that are unlikely to generate large amounts of traffic using the services of transmission network operators. In addition, by enhancing the content of the traffic characteristics provided to the transmission paths off-path, it is expected that mainly optical transmission paths can be effectively utilized.

In addition, PLMNs can select other companies' transmission paths for each call depending on the traffic characteristics. Transmission network operators can respond to requests for transmission services for each call from multiple PLMNs. The transmission network can obtain traffic characteristics off-path.

In other words, the utilization efficiency of user data transmission paths can be improved in wireless communication systems.

(Device configuration)
Next, a functional configuration example of the base station 10 and the terminal 20 that execute the processes and operations described above will be described. The base station 10 and the terminal 20 include functions for implementing the above-mentioned embodiments. However, the base station 10 and the terminal 20 may each include only a part of the functions in the embodiments.

<Base Station 10>
Fig. 7 is a diagram showing an example of a functional configuration of the base station 10 in the embodiment of the present invention. As shown in Fig. 7, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 7 is merely an example. The names of the functional divisions and functional units may be any as long as the operations related to the embodiment of the present invention can be executed. The network node 30 may have the same functional configuration as the base station 10.

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

The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20. The contents of the setting information include, for example, information related to a PDU session.

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

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

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

The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores setting information that is set in advance. The contents of the setting information include, for example, information related to a PDU session.

As described in the embodiment, the control unit 240 controls communication via the PDU session. 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.

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

Functions include, but are not limited to, judgement, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the transmission function is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on the method of realization for either of these.

For example, the base station 10, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 9 is a diagram showing an example of the hardware configuration of the base station 10 and terminal 20 in one embodiment of the present disclosure. The above-mentioned base station 10 and terminal 20 may be physically configured as a computer device including a processor 1001, a memory device 1002, an auxiliary memory device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

In the following description, the term "apparatus" may be interpreted as a circuit, device, unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the devices shown in the figure, or may be configured to exclude some of the devices.

Each function in the base station 10 and the terminal 20 is realized by loading a specific software (program) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of the reading and writing of data in the memory device 1002 and the auxiliary memory device 1003.

The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

The processor 1001 reads out a program (program code), a software module, or data, etc., from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and executes various processes according to the program. As the program, a program that causes a computer to execute at least a part of the operations described in the above-mentioned embodiment is used. For example, the control unit 140 of the base station 10 shown in FIG. 7 may be stored in the storage device 1002 and realized by a control program that runs on the processor 1001. For example, the control unit 240 of the terminal 20 shown in FIG. 8 may be stored in the storage device 1002 and realized by a control program that runs on the processor 1001. Although the above-mentioned various processes have been described as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from a network via a telecommunications line.

The storage device 1002 is a computer-readable recording medium, and may be composed of 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 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to one embodiment of the present disclosure.

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

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

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

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

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), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

(Summary of the embodiment)
As described above, according to an embodiment of the present invention, when establishing a PDU (Protocol Data Unit) session, a control unit selects a UPF (User Plane Function) and a transmission network operator, and encodes information indicating the transmission network operator and the service type provided by the transmission network operator to determine a network instance, a transmission unit transmits the network instance to the UPF, and a reception unit receives a first TEID (Tunnel Endpoint Identifier) corresponding to an uplink from the UPF and a second TEID corresponding to a downlink from a gNB-CU-CP (next generation Node B - Central Unit - Control Plane), and the transmission unit transmits the first TEID, the second TEID, and information indicating an interface corresponding to a PLMN (Public Land Mobile Network) to a transport installed between the UPF and the gNB-CU-UP (next generation Node B - Central Unit - User Plane) in a data transmission path to establish the PDU session.

With the above configuration, a PLMN can select another company's transmission path for each call depending on the traffic characteristics. Transmission network operators can respond to requests for transmission services for each call from multiple PLMNs. In other words, the utilization efficiency of user data transmission paths can be improved in wireless communication systems.

The information indicating the interface corresponding to the PLMN may include information indicating a UPF in the PLMN corresponding to a downlink source interface and an uplink destination interface in a PFCP (Packet Forwarding Control Protocol) session establishment request, and information indicating a gNB-CU-UP in the PLMN corresponding to a downlink destination interface and an uplink source interface. With this configuration, a transmission network operator can respond to transmission service provision requests for each call from multiple PLMNs.

The receiver may receive a third TEID corresponding to a downlink and a fourth TEID corresponding to an uplink from the transport. This configuration enables a transmission network operator to respond to transmission service requests for each call from multiple PLMNs.

The transmitting unit may transmit the third TEID to the UPF. With this configuration, a transmission network operator can respond to transmission service provision requests for each call from multiple PLMNs.

The transmitting unit may transmit the fourth TEID and the network instance to an AMF (Access and Mobility Management Function). With the above configuration, a PLMN can select another company's transmission path for each call depending on traffic characteristics. A transmission network operator can respond to requests for transmission services for each call from multiple PLMNs.

In addition, according to an embodiment of the present invention, a communication method is provided in which, when establishing a PDU (Protocol Data Unit) session, a network node executes the following steps: a control procedure for selecting a UPF (User Plane Function) and a transmission network operator, and encoding information indicating the transmission network operator and the service type provided by the transmission network operator to determine a network instance; a transmission procedure for transmitting the network instance to the UPF; a reception procedure for receiving a first TEID (Tunnel Endpoint Identifier) corresponding to the uplink from the UPF and receiving a second TEID corresponding to the downlink from a gNB-CU-CP (next generation Node B - Central Unit - Control Plane); and a procedure for transmitting the first TEID, the second TEID, and information indicating an interface corresponding to a PLMN (Public Land Mobile Network) to a transport installed between the UPF and the gNB-CU-UP (next generation Node B - Central Unit - User Plane) in a data transmission path to establish the PDU session.

With the above configuration, a PLMN can select another company's transmission path for each call depending on the traffic characteristics. Transmission network operators can respond to requests for transmission services for each call from multiple PLMNs. In other words, the utilization efficiency of user data transmission paths can be improved in wireless communication systems.

According to an embodiment of the present invention, the present invention includes a receiving unit that receives from an SMF (Session Management Function) a first TEID (Tunnel Endpoint Identifier) corresponding to an uplink, a second TEID corresponding to a downlink, and information indicating an interface corresponding to a PLMN (Public Land Mobile Network), and a control unit that sets a data transmission path between a UPF (User Plane Function) and a gNB-CU-UP (next generation Node B - Central Unit - User Plane) based on the first TEID, the second TEID, and the information indicating the interface corresponding to the PLMN, and a transport is provided in which the first TEID is transmitted from the UPF to the SMF and the second TEID is transmitted from the gNB-CU-CP (next generation Node B - Central Unit - Control Plane) to the SMF.

With the above configuration, a PLMN can select another company's transmission path for each call depending on the traffic characteristics. Transmission network operators can respond to requests for transmission services for each call from multiple PLMNs. In other words, the utilization efficiency of user data transmission paths can be improved in wireless communication systems.

Furthermore, according to an embodiment of the present invention, a network node is provided that, when establishing a PDU (Protocol Data Unit) session, has a control unit that selects a gNB-CU-UP (next generation Node B - Central Unit - User Plane) and a transmission network operator, and encodes information indicating the transmission network operator and the service type provided by the transmission network operator to determine a network instance, a transmission unit that transmits the network instance to the gNB-CU-UP, and a reception unit that receives a fifth TEID (Tunnel Endpoint Identifier) corresponding to the uplink from the gNB-CU-UP and a sixth TEID corresponding to the downlink from the gNB-DU (next generation Node B - Distributed Unit), wherein the transmission unit transmits the fifth TEID, the sixth TEID, and information indicating an interface corresponding to a PLMN (Public Land Mobile Network) to a transport installed between the gNB-CU-UP and the gNB-DU in a data transmission path, thereby establishing the PDU session.

With the above configuration, a PLMN can select another company's transmission path for each call depending on the traffic characteristics. Transmission network operators can respond to requests for transmission services for each call from multiple PLMNs. In other words, the utilization efficiency of user data transmission paths can be improved in wireless communication systems.

The information indicating the interface corresponding to the PLMN may include information indicating a gNB-CU-UP in the PLMN corresponding to a downlink source interface and an uplink destination interface in a PFCP (Packet Forwarding Control Protocol) session establishment request, and information indicating a gNB-DU in the PLMN corresponding to a downlink destination interface and an uplink source interface. With this configuration, a transmission network operator can respond to transmission service provision requests for each call from multiple PLMNs.

The receiver may receive from the transport a seventh TEID corresponding to the downlink and an eighth TEID corresponding to the uplink. With this configuration, the transmission network operator can respond to transmission service provision requests for each call from multiple PLMNs.

The transmitting unit may transmit the seventh TEID to the gNB-CU-UP. With this configuration, a transmission network operator can respond to transmission service provision requests for each call from multiple PLMNs.

The transmitting unit may transmit the eighth TEID to the gNB-DU. With this configuration, a transmission network operator can respond to transmission service provision requests for each call from multiple PLMNs.

In addition, according to an embodiment of the present invention, a communication method is provided in which, when establishing a PDU (Protocol Data Unit) session, a network node executes the following procedures: a control procedure for selecting a gNB-CU-UP (next generation Node B - Central Unit - User Plane) and a transmission network operator, and encoding information indicating the transmission network operator and the service type provided by the transmission network operator to determine a network instance; a transmission procedure for transmitting the network instance to the gNB-CU-UP; a reception procedure for receiving a fifth TEID (Tunnel Endpoint Identifier) corresponding to the uplink from the gNB-CU-UP and receiving a sixth TEID corresponding to the downlink from the gNB-DU (next generation Node B - Distributed Unit); and a procedure for transmitting the fifth TEID, the sixth TEID, and information indicating an interface corresponding to a PLMN (Public Land Mobile Network) to a transport installed between the gNB-CU-UP and the gNB-DU in a data transmission path to establish the PDU session.

With the above configuration, a PLMN can select another company's transmission path for each call depending on the traffic characteristics. Transmission network operators can respond to requests for transmission services for each call from multiple PLMNs. In other words, the utilization efficiency of user data transmission paths can be improved in wireless communication systems.

Furthermore, according to an embodiment of the present invention, a receiving unit receives a fifth TEID (Tunnel Endpoint Identifier) corresponding to the uplink from a gNB-CU-CP (next generation Node B - Central Unit - Control Plane), a sixth TEID corresponding to the downlink, and information indicating an interface corresponding to a PLMN (Public Land Mobile Network), and a control unit sets up a data transmission path between a gNB-CU-UP (next generation Node B - Central Unit - User Plane) and a gNB-DU (next generation Node B - Distributed Unit) based on the fifth TEID, the sixth TEID, and the information indicating the interface corresponding to the PLMN, and transport is provided in which the fifth TEID is transmitted from the gNB-CU-UP to the gNB-CU-CP and the sixth TEID is transmitted from the gNB-DU to the gNB-CU-CP.

With the above configuration, a PLMN can select another company's transmission path for each call depending on the traffic characteristics. Transmission network operators can respond to requests for transmission services for each call from multiple PLMNs. In other words, the utilization efficiency of user data transmission paths can be improved in wireless communication systems.

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

In addition, the notification of information is not limited to the aspects/embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., 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 combinations thereof. In addition, the RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

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

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

In this specification, a particular operation that is described as being performed by the network node 30 may in some cases be performed by its upper node. In a network consisting of one or more network nodes having the network node 30, it is clear that various operations performed for communication with the terminal 20 may be performed by the network node 30 and at least one of other network nodes other than the network node 30 (e.g., MME or S-GW, etc., but are not limited to these). Although the above example shows a case where there is one other network node other than the network node 30, the other network node may be a combination of multiple other network nodes (e.g., MME and S-GW).

The information or signals described in this disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). They may be input and output via multiple network nodes.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

In addition, the base station in the present disclosure may be read as a user terminal. For example, each aspect/embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminal 20 may be configured to have the functions possessed by the above-mentioned network node 30. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, the uplink channel, downlink channel, etc. may be read as a side channel.

Similarly, the user terminal in this disclosure may be interpreted as a base station. In this case, the base station may be configured to have the functions of the user terminal described above.

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

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

The reference signal may also be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

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

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

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

When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Additionally, the term "or," as used in this disclosure, is not intended to be an exclusive or.

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

In this disclosure, the term "A and B are different" may mean "A and B are different from each other." In addition, the term may mean "A and B are each different from C." Terms such as "separate" and "combined" may also be interpreted in the same way as "different."

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

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

10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 30 Network node 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims (14)

a control unit for selecting a user plane function (UPF) and a transport network operator when establishing a protocol data unit (PDU) session, and encoding information indicating the transport network operator and a service type provided by the transport network operator to determine a network instance;
a sending unit for sending the network instance to the UPF;
A receiver that receives a first TEID (Tunnel Endpoint Identifier) corresponding to an uplink from the UPF and receives a second TEID corresponding to a downlink from a gNB-CU-CP (next generation Node B - Central Unit - Control Plane),
The transmitter transmits the first TEID, the second TEID, and information indicating an interface corresponding to a PLMN (Public Land Mobile Network) to a transport installed between the UPF and a gNB-CU-UP (next generation Node B - Central Unit - User Plane) in a data transmission path, thereby establishing the PDU session. A network node. A network node as described in claim 1, wherein the information indicating the interface corresponding to the PLMN includes information indicating a UPF in the PLMN corresponding to a downlink source interface and an uplink destination interface in a PFCP (Packet Forwarding Control Protocol) session establishment request, and information indicating a gNB-CU-UP in the PLMN corresponding to a downlink destination interface and an uplink source interface. A network node as described in claim 2, wherein the receiving unit receives a third TEID corresponding to a downlink and a fourth TEID corresponding to an uplink from the transport. A network node as described in claim 3, wherein the transmitting unit transmits the third TEID to the UPF. A network node as described in claim 4, wherein the transmitting unit transmits the fourth TEID and the network instance to an AMF (Access and Mobility Management Function). A control procedure for selecting a User Plane Function (UPF) and a transport network operator when establishing a Protocol Data Unit (PDU) session, and encoding information indicating the transport network operator and a service type provided by the transport network operator to determine a network instance;
a sending step of sending the network instance to the UPF;
A reception procedure of receiving a first TEID (Tunnel Endpoint Identifier) corresponding to an uplink from the UPF and receiving a second TEID corresponding to a downlink from a gNB-CU-CP (next generation Node B - Central Unit - Control Plane);
A communication method in which a network node executes a procedure of transmitting the first TEID, the second TEID, and information indicating an interface corresponding to a PLMN (Public Land Mobile Network) to a transport installed between the UPF and a gNB-CU-UP (next generation Node B - Central Unit - User Plane) in a data transmission path, thereby establishing the PDU session. a receiving unit that receives, from a session management function (SMF), a first tunnel endpoint identifier (TEID) corresponding to an uplink, a second tunnel endpoint identifier (TEID) corresponding to a downlink, and information indicating an interface corresponding to a public land mobile network (PLMN);
A control unit that sets a data transmission path between a UPF (User Plane Function) and a gNB-CU-UP (next generation Node B - Central Unit - User Plane) based on information indicating the first TEID, the second TEID, and an interface corresponding to the PLMN,
The first TEID is sent from the UPF to the SMF;
The second TEID is a transport transmitted from a gNB-CU-CP (next generation Node B - Central Unit - Control Plane) to the SMF. A control unit that selects a next generation Node B - Central Unit - User Plane (gNB-CU-UP) and a transport network operator when establishing a Protocol Data Unit (PDU) session, and determines a network instance by encoding information indicating the transport network operator and the service type provided by the transport network operator;
A transmitter that transmits the network instance to the gNB-CU-UP;
A receiving unit that receives a fifth TEID (Tunnel Endpoint Identifier) corresponding to an uplink from the gNB-CU-UP and receives a sixth TEID corresponding to a downlink from a gNB-DU (next generation Node B - Distributed Unit),
The transmitter transmits the fifth TEID, the sixth TEID, and information indicating an interface corresponding to a PLMN (Public Land Mobile Network) to a transport installed between the gNB-CU-UP and the gNB-DU in a data transmission path, thereby establishing the PDU session. A network node. A network node as described in claim 8, wherein the information indicating the interface corresponding to the PLMN includes information indicating a gNB-CU-UP in the PLMN corresponding to a downlink source interface and an uplink destination interface in a PFCP (Packet Forwarding Control Protocol) session establishment request, and information indicating a gNB-DU in the PLMN corresponding to a downlink destination interface and an uplink source interface. A network node as described in claim 9, wherein the receiving unit receives a seventh TEID corresponding to a downlink and an eighth TEID corresponding to an uplink from the transport. A network node as described in claim 10, wherein the transmitting unit transmits the seventh TEID to the gNB-CU-UP. A network node as described in claim 11, wherein the transmitting unit transmits the eighth TEID to the gNB-DU. When establishing a Protocol Data Unit (PDU) session, a control procedure for selecting a next generation Node B - Central Unit - User Plane (gNB-CU-UP) and a transport network operator, encoding information indicating the transport network operator and the service type provided by the transport network operator to determine a network instance;
A transmission procedure for transmitting the network instance to the gNB-CU-UP;
A reception procedure of receiving a fifth TEID (Tunnel Endpoint Identifier) corresponding to an uplink from the gNB-CU-UP and receiving a sixth TEID corresponding to a downlink from a gNB-DU (next generation Node B - Distributed Unit);
A communication method in which a network node executes a procedure of transmitting the fifth TEID, the sixth TEID, and information indicating an interface corresponding to a PLMN (Public Land Mobile Network) to a transport installed between the gNB-CU-UP and gNB-DU in a data transmission path, thereby establishing the PDU session. A receiving unit that receives a fifth TEID (Tunnel Endpoint Identifier) corresponding to an uplink, a sixth TEID corresponding to a downlink, and information indicating an interface corresponding to a PLMN (Public Land Mobile Network) from a gNB-CU-CP (next generation Node B - Central Unit - Control Plane);
and a control unit that sets a data transmission path between a gNB-CU-UP (next generation Node B - Central Unit - User Plane) and a gNB-DU (next generation Node B - Distributed Unit) based on information indicating the fifth TEID, the sixth TEID, and an interface corresponding to the PLMN;
The fifth TEID is transmitted from the gNB-CU-UP to the gNB-CU-CP;
The sixth TEID is a transport transmitted from the gNB-DU to the gNB-CU-CP.

Images