Terminal, network node, and communication method

Abstract

This terminal comprises: a control unit that stores a list of combinations of identifiers of network slices and types of core networks supporting the network slices, determines a network slice to be connected, determines the type of core network to be connected on the basis of the list, and determines a base station to be connected to a core network having the type; and a transmission unit that transmits, to the base station, a message including a registration request addressed to the core network to be connected.

Description

Terminal, network node and communication method

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

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

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

[0004] Furthermore, studies have begun on systems beyond 5G (5GC) or 6G (6GC). In these future systems, diversified requirements are expected regarding power consumption, latency, communication speed, etc., for diversified devices such as ambient IoT (e.g., wireless tags) and XR (extended reality) with functions that extend virtual reality.

[0005] 3GPP TS 23.501 V18.6.0 (2024-06) 3GPP TS 23.502 V18.6.0 (2024-06) 3GPP TS 38.331 V18.2.0 (2024-06) 3GPP TS 33.535 V18.4.0 (2024-07) 3GPP TS 36.331 V18.2.0 (2024-07)

[0006] In a PLMN (Public Land Mobile Network) that supports multiple generation networks (e.g., both 5GC and 6GC), for example, a configuration is possible in which 5GC has a network slice that supports a first service and 6GC has a network slice that supports a second service.

[0007] However, when a terminal connects to a network slice that supports the first service, existing specifications do not allow the terminal to determine which cell to connect to (i.e., whether it is a 5G or 6G base station) and which core network to connect to (i.e., whether it is 5GC or 6GC).

[0008] The present invention has been made in view of the above points, and has as its object to determine the base station and core network to which a terminal connects in a wireless communication system that supports multiple types of core networks.

[0009] According to the disclosed technology, a terminal is provided that has: a control unit that stores a list of combinations of a network slice identifier and a type of core network that supports the network slice, determines a network slice to connect to, determines a type of core network to connect to based on the list, and determines a base station to connect to a core network having the type; and a transmission unit that transmits a message to the base station that includes a registration request addressed to the core network to connect to.

[0010] According to the disclosed technology, in a wireless communication system that supports multiple types of core networks, it is possible to determine the base station and core network to which a terminal connects.

[0011] FIG. 1 is a diagram for explaining an example of a communication system. FIG. 1 is a diagram for explaining an example of a communication system in a roaming environment. FIG. 2 is a diagram showing an example of a first sequence diagram in an embodiment of the present invention. FIG. 3 is a diagram showing an example of a second sequence diagram in an embodiment of the present invention. FIG. 4 is a diagram showing an example of a third sequence diagram in an embodiment of the present invention. FIG. 5 is a diagram showing an example of a fifth sequence diagram in an embodiment of the present invention. FIG. 6 is a diagram showing an example of the functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. FIG. 7 is a diagram showing an example of the functional configuration of a terminal 20 in an embodiment of the present invention. FIG. 8 is a diagram showing an example of the hardware configuration of a base station 10, a terminal 20, and a network node 30 in an embodiment of the present invention. FIG. 9 is a diagram showing an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

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

[0013] In the operation of the wireless communication system according to the embodiment of the present invention, existing technology is used as appropriate. 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), or wireless LAN (Local Area Network), unless otherwise specified.

[0014] Furthermore, in the embodiments of the present invention, "configuring" radio parameters and the like may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the network node 30 or the terminal 20 are set.

[0015] Fig. 1 is a diagram illustrating an example of a communication system. As shown in Fig. 1, the communication system is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, 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. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0016] 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 terminating the RAN interface, terminating the NAS (Non-Access Stratum), registering management, connecting management, reachability management, and terminal mobility management. The UPF is a network node 30 having functions related to processing user plane data, such as a PDU (Protocol Data Unit) session point to the outside that interconnects with the DN (Data Network), packet routing and forwarding, and user plane Quality of Service (QoS) handling. The UPF and the DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

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

[0018] 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 a UE connects, determining an allowed NSSAI (Network Slice Selection Assistance Information), determining an NSSAI to be set, and determining an AMF set to which a UE connects. The PCF is a network node 30 having a function of controlling network policies. The AF is a network node 30 having a function of controlling application servers. The NRF is a network node 30 having a function of discovering NF instances that provide services. The UDM is a network node 30 that manages subscriber data and authentication data. The UDM is connected to a UDR (User Data Repository) that stores the data.

[0019] Fig. 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Fig. 2, the network is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, 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. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0020] The RAN is a network node 30 having a radio access function, and is connected to the UE, the AMF, and the UPF. The AMF is a network node 30 having functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU session point to the outside that interconnects with the DN, packet routing and forwarding, and user plane QoS handling. The UPF and the DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

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

[0022] The SMF is a network node 30 having functions such as session management, UE IP address allocation and management, DHCP function, ARP proxy, and roaming function. The NEF is a network node 30 having a function of notifying other NFs of capabilities and events. The NSSF is a network node 30 having functions such as selecting a network slice to which a UE connects, determining an allowed NSSAI, determining a configured NSSAI, and determining an AMF set to which a UE connects. The PCF is a network node 30 having a function of controlling network policies. The AF is a network node 30 having a function of controlling application servers. The NRF is a network node 30 having a function of discovering NF instances that provide services. The SEPP is a non-transparent proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). The vSEPP shown in FIG. 2 is a SEPP in the visited network, and the hSEPP is a SEPP in the home network.

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

[0024] (Example) A method for determining a base station and a core network to which a terminal connects in a wireless communication system that supports multiple types of core networks will be described. In this example, the configured network slice selection assistance information (Configured NSSAI (Network Slice Selection Assistance Information), see Non-Patent Document 1) possessed by a terminal is a list including a combination of a network slice identifier (S(Single)-NSSAI) and a type of core network (CN type) that supports the network slice, and is expressed as, for example, [S-NSSAI, CN type]. Here, the CN type is 5GC or 6GC.

[0025] When a 5G base station (5G base station 10A) connects to 6GC in addition to 5GC, it broadcasts information indicating the connection by including it in broadcast information (SIB (System Information Block) 1). Also, when a 6G base station (6G base station 10B) connects to 5GC in addition to 6GC, it broadcasts information indicating the connection by including it in broadcast information (SIB1).

[0026] When selecting a cell and a CN, the terminal 20 refers to the Configured NSSAI and the received broadcast information.

[0027] If 6GC supports the network slice requested by the terminal 20, the 5G AMF (5G AMF 30A) transmits a Rejected NSSAI to the terminal 20, with information indicating the support (referred to as a cause) attached. Furthermore, if 5GC supports the network slice requested by the terminal 20, the 6G AMF (6GAMF 30B) transmits a Rejected NSSAI to the terminal 20, with information indicating the support (cause) attached.

[0028] Below, the initial registration procedure of the terminal 20 in this embodiment will be explained using sequence diagrams for three cases: Case A (when the terminal 20 has a Configured NSSAI in advance and the 6G base station 30B does not connect to 5GC), Case B (when the terminal 20 has a Configured NSSAI in advance and the 6G base station 30B connects to 5GC), and Case C (when the terminal 20 does not have a Configured NSSAI in advance).

[0029] Requests, responses, notifications, etc. transmitted and received in the procedures described below may be referred to as messages (e.g., request messages). For details of existing specifications regarding the messages transmitted and received in this sequence diagram, see Non-Patent Documents 2-5, etc. UDM includes the functions of ARPF (Authentication Credential Repository and Processing Function) and SIDF (Subscription Identifier De-concealing Function) or enables the invocation of these functions. A network slice may also be simply referred to as a slice. In 5G, the 5G base station 10A, 5GAMF 30A, 5G broadcast information, etc. may be referred to as the base station 10A, AMF 30A, and broadcast information without the 5G prefix.

[0030] (Initial Registration Procedure (Case A)) An initial registration procedure for terminal 20 in a case where terminal 20 has a Configured NSSAI in advance and 6G base station 30B does not connect to 5GC will be described. FIG. 3 is a diagram showing an example of a first sequence diagram in an embodiment of the present invention. The processing of each step will be described below.

[0031] S101: Terminal 20 has {[S-NSSAI#1, 5GC], [S-NSSAI#2, 6GC]} as a list (Configured NSSAI) of combinations of network slice identifiers and types of core networks that support the network slices.

[0032] S102: The 5G base station 10A transmits 5G notification information (5G notification information, 5G SIB1) to the terminal 20.

[0033] S103: The 6G base station 10B transmits 6G notification information (6G notification information, 6G SIB1) to the terminal 20. Here, the notification information does not include information indicating connection to 5GC (cellAccessRelated-5GC, see Non-Patent Document 5).

[0034] S104: Terminal 20 decides to connect to a network slice with identifier S-NSSAI#1.

[0035] S105: The terminal 20 determines to connect to 5GC by referring to the Configured NSSAI. Also, the terminal 20 determines to connect to the 5G base station 10A based on the 5G broadcast information received in S102 and the 6G broadcast information received in S103 (which does not include information indicating that the terminal 20 is connected to 5GC).

[0036] S106: The terminal 20 transmits a request message (RRCSetup request) to the 5G base station 10A requesting settings related to the radio resource control protocol (RRC).

[0037] S107: The 5G base station 10A transmits to the terminal 20 a response message (RRCSetup) in response to the request message received in S106.

[0038] S108: The terminal 20 transmits a message (RRCSetupComplete) notifying the 5G base station 10A of completion of RRC setup. The message includes information indicating a registration request and is expressed as, for example, RRCSetupComplete (dedicated NAS-Message (Registration request)).

[0039] S109: The 5G base station 10A transmits a message (Initial UE message) including information indicating a registration request to the 5G base station 30A. For example, the message is expressed as an Initial UE message (NAS-PDU (Registration request)).

[0040] S110: The 5GAMF 30A transmits a request message (Nausf_UEAuthentication_Authenticate request) to the AUSF 30B, requesting the execution of authentication of the terminal 20 (hereinafter, may be simply referred to as authentication).

[0041] S111: The AUSF 30B transmits a request message (Nudm_UEAuthentication_Get request) requesting authentication information to the UDM 30C.

[0042] S112: The UDM 30C transmits to the AUSF 30B a response message (Nudm_UEAuthentication_Get response) in response to the request message received in S111.

[0043] S113: The AUSF 30B transmits to the 5GAMF 30A a response message (Nausf_UEAuthentication_Authenticate response) in response to the request message received in S110.

[0044] S114: The 5GAMF 30A transmits a message (Downlink NAS Transport) requesting the execution of authentication to the 5G base station 10A. For example, the message is expressed as Downlink NAS Transport (NAS-PDU (Authentication request)).

[0045] S115: The 5G base station 10A transmits a message (DLInformationTransfer) requesting the execution of authentication to the terminal 20. For example, the message is expressed as DLInformationTransfer(dedicatedNAS-Message(Authentication request)).

[0046] S116: The terminal 20 transmits to the 5G base station 10A a message (ULInformationTransfer) including an authentication response in response to the authentication request included in the message received in S115. For example, the message is expressed as ULInformationTransfer (dedicatedNAS-Message(Authentication response)).

[0047] S117: The 5G base station 10A transmits a message (ULInformationTransfer) including the authentication response received in S116 to the 5G base station 30A. For example, the message is expressed as Uplink NAS Transport (NAS-PDU (Authentication response)).

[0048] S118: The 5GAMF 30A transmits a request message (Nausf_UEAuthentication_Authenticate request) to the AUSF 30B, requesting that authentication of the terminal 20 be performed.

[0049] S119: The AUSF 30B authenticates the terminal 20 in response to the request message received in S118.

[0050] S120: The AUSF 30B transmits to the 5GAMF 30A a response message (Nausf_UEAuthentication_Authenticate response) in response to the request message received in S118.

[0051] S121: A SEAF (Security Anchor Function) having an authentication function in the 5GAMF 30A performs authentication of the terminal 20.

[0052] S122: The AUSF 30B transmits a request message (Nudm_UEAuthentication_ResultConfirmation request) requesting registration of the authentication result of the terminal 20 to the UDM 30C.

[0053] S123: The UDM 30C transmits to the AUSF 30B a response message (Nudm_UEAuthentication_ResultConfirmation response) in response to the request message received in S122.

[0054] The process following S123 will be described. Fig. 4 is a diagram showing an example of a second sequence diagram according to an embodiment of the present invention. The process of each step will be described below.

[0055] S124: The 5GAMF30A sends an Initial Context Setup request to the 5G base station 10A.

[0056] S125: The 5G base station 10A sends a SecurityModeCommand to the terminal 20.

[0057] S126: The terminal 20 transmits SecurityModeComplete to the 5G base station 10A.

[0058] S127: The 5G base station 10A sends an Initial Context Setup response to the 5G base station 10A.

[0059] S128: The 5GAMF 30A transmits a message (Downlink NAS Transport) including a Security Mode Command in the NAS to the 5G base station 10A. For example, the message is expressed as Downlink NAS Transport (NAS-PDU (Security Mode Command)).

[0060] S129: The 5G base station 10A transmits a message (DLInformationTransfer) including a Security Mode Command in the NAS to the terminal 20. For example, the message is expressed as DLInformationTransfer(dedicatedNAS-Message(Security Mode Command)).

[0061] S130: The terminal 20 sends a message (ULInformationTransfer) to the 5G base station 10A notifying the completion of NAS security configuration. The message includes information indicating the registration request that could not be transmitted before NAS security was established. In particular, the message includes a list (of identifiers) of network slices to which connection is requested. For example, the request message is expressed as ULInformationTransfer(dedicatedNAS-Message(Security Mode Complete(IMEISV, NAS message container(Registration request (Requested NSSAI=S-NSSAI#1))))).

[0062] S131: The 5G base station 10A sends a message (Uplink NAS Transport) to the 5G 5G base station 30A, including a notification of completion of NAS security configuration and a request for terminal registration. The message includes a list (of identifiers) of network slices to which connection is requested. For example, the request message is expressed as Uplink NAS Transport (NAS-PDU (Security Mode Complete (IMEISV, NAS message container (Registration request (Requested NSSAI = S-NSSAI # 1))))).

[0063] S132: The 5GAMF 30A sends a request message (Nudm_UECM_Registration request) to the UDM 30C requesting registration of the terminal 20.

[0064] S133: The UDM 30C sends a response message (Nudm_UECM_Registration response) to the request message received in S132 to the 5GAMF 30A.

[0065] S134: The 5GAMF 30A sends a request message (Nudm_SDM_Get request) requesting subscriber information of the terminal 20 to the UDM 30C.

[0066] S135: The UDM 30C sends a response message (Nudm_SDM_Get response) to the request message received in S134 to the 5GAMF 30A.

[0067] S136: The 5GAMF 30A sends to the 5G base station 10A a message (Downlink NAS Transport) including information indicating acceptance of the registration request, including a list (of identifiers) of network slices allowed to be connected. For example, the message is expressed as Downlink NAS Transport (NAS-PDU(Registration accept(Allowed NSSAI=S-NSSAI#1))).

[0068] S137: The 5G base station 10A sends a message (DLInformationTransfer) including information indicating acceptance of the registration request, including a list (of identifiers) of network slices allowed to be connected, to the terminal 20. For example, the message is expressed as DLInformationTransfer (dedicatedNAS-Message(Registration accept (Allowed NSSAI=S-NSSAI#1))).

[0069] (Initial Registration Procedure (Case B)) An initial registration procedure for terminal 20 when terminal 20 has a Configured NSSAI in advance and 6G base station 30B connects to 5GC will be described. Fig. 5 is a diagram showing an example of a third sequence diagram in the embodiment of the present invention. The processing of each step will be described below.

[0070] S201: Terminal 20 has {[S-NSSAI#1, 5GC], [S-NSSAI#2, 6GC]} as a list (Configured NSSAI) of combinations of network slice identifiers and types of core networks that support the network slices.

[0071] S202: The 5G base station 10A transmits 5G notification information (5G notification information, 5G SIB1) to the terminal 20.

[0072] S203: The 6G base station 10B transmits 6G notification information (6G notification information, 6G SIB1) to the terminal 20. Here, the notification information includes information indicating connection to 5GC (cellAccessRelated-5GC, see Non-Patent Document 5).

[0073] S204: Terminal 20 decides to connect to a network slice with identifier S-NSSAI#1.

[0074] S205: The terminal 20 determines to connect to 5GC by referring to the Configured NSSAI. Furthermore, the terminal 20 determines to connect to 5GC via the 6G base station 10B based on the 5G broadcast information received in S202 and the 6G broadcast information received in S203 (including information indicating that the terminal 20 is connected to 5GC).

[0075] S206: The terminal 20 transmits to the 6G base station 10B a request message (6G RRC Setup request) requesting settings related to the radio resource control protocol (RRC).

[0076] S207: The 6G base station 10B transmits to the terminal 20 a response message (6G RRCSetup) in response to the request message received in S206.

[0077] S208: The terminal 20 transmits a message (6G RRCSetupComplete) notifying completion of RRC setup to the 6G base station 10B. The message includes information indicating connection to 5GC (connectTo5GC, see Non-Patent Document 5) and information indicating a registration request, and is expressed as, for example, 6G RRCSetupComplete(connectTo5GC, dedicatedNAS-Message(Registration request)).

[0078] S209: The 6G base station 10B transmits a message (Initial UE message) including information indicating a registration request to the 5G base station 30A. For example, the message is expressed as an Initial UE message (NAS-PDU (Registration request)).

[0079] S210: The 5GAMF 30A transmits a request message (Nausf_UEAuthentication_Authenticate request) to the AUSF 30B, requesting the execution of authentication of the terminal 20 (hereinafter, may be simply referred to as authentication).

[0080] S211: The AUSF 30B transmits a request message (Nudm_UEAuthentication_Get request) requesting authentication information to the UDM 30C.

[0081] S212: The UDM 30C transmits to the AUSF 30B a response message (Nudm_UEAuthentication_Get response) in response to the request message received in S211.

[0082] S213: The AUSF 30B transmits to the 5GAMF 30A a response message (Nausf_UEAuthentication_Authenticate response) in response to the request message received in S210.

[0083] S214: The 5G MF 30A transmits a message (Downlink NAS Transport) requesting the execution of authentication to the 6G base station 10B. For example, the message is expressed as Downlink NAS Transport (NAS-PDU (Authentication request)).

[0084] S215: The 6G base station 10B transmits a message (6G DLInformationTransfer) requesting the execution of authentication to the terminal 20. For example, this message is expressed as 6G DLInformationTransfer(dedicatedNAS-Message(Authentication request)).

[0085] S216: The terminal 20 transmits to the 6G base station 10B a message (6G ULInformationTransfer) including an authentication response in response to the authentication request included in the message received in S215. For example, this message is expressed as 6G ULInformationTransfer (dedicated NAS-Message (Authentication response)).

[0086] S217: The 6G base station 10B transmits a message (ULInformationTransfer) including the authentication response received in S216 to the 5G base station 30A. For example, this message is expressed as Uplink NAS Transport (NAS-PDU (Authentication response)).

[0087] S218: The 5GAMF 30A transmits a request message (Nausf_UEAuthentication_Authenticate request) to the AUSF 30B, requesting that the terminal 20 be authenticated.

[0088] S219: The AUSF 30B authenticates the terminal 20 in response to the request message received in S218.

[0089] S220: The AUSF 30B transmits to the 5GAMF 30A a response message (Nausf_UEAuthentication_Authenticate response) in response to the request message received in S218.

[0090] S221: A SEAF (Security Anchor Function) having an authentication function in the 5GAMF 30A performs authentication of the terminal 20.

[0091] S222: The AUSF 30B transmits a request message (Nudm_UEAuthentication_ResultConfirmation request) requesting registration of the authentication result of the terminal 20 to the UDM 30C.

[0092] S223: The UDM 30C transmits to the AUSF 30B a response message (Nudm_UEAuthentication_ResultConfirmation response) in response to the request message received in S222.

[0093] The process following S223 will be described. Fig. 6 is a diagram showing an example of a fourth sequence diagram according to an embodiment of the present invention. The process of each step will be described below.

[0094] S224: The 5GAMF 30A transmits an Initial Context Setup request to the 6G base station 10B.

[0095] S225: The 6G base station 10B transmits a 6G SecurityModeCommand to the terminal 20.

[0096] S226: The terminal 20 transmits 6G SecurityModeComplete to the 6G base station 10B.

[0097] S227: The 6G base station 10B transmits an Initial Context Setup response to the 6G base station 10B.

[0098] S228: The 5G FM F30A transmits a message (Downlink NAS Transport) including a Security Mode Command in the NAS to the 6G base station 10B. For example, the message is expressed as Downlink NAS Transport (NAS-PDU (Security Mode Command)).

[0099] S229: The 6G base station 10B transmits a message (6G DLInformationTransfer) including a Security Mode Command in the NAS to the terminal 20. For example, the message is expressed as 6G DLInformationTransfer(dedicatedNAS-Message(Security Mode Command)).

[0100] S230: The terminal 20 sends a message (6G ULInformationTransfer) to the 6G base station 10B notifying the completion of NAS security configuration. The message also includes information indicating the registration request that could not be transmitted before NAS security was established. In particular, the message includes a list (of identifiers) of network slices to which connection is requested. For example, the request message is expressed as 6G ULInformationTransfer(dedicatedNAS-Message(Security Mode Complete(IMEISV, NAS message container(Registration request (Requested NSSAI=S-NSSAI#1))))).

[0101] S231: The 6G base station 10B sends to the 5G UE 30A a message (Uplink NAS Transport) including a notification of completion of NAS security configuration and a request for terminal registration. The message includes a list (identifiers) of network slices to which connection is requested. For example, the request message is expressed as Uplink NAS Transport(NAS-PDU(Security Mode Complete(IMEISV, NAS message container(Registration request (Requested NSSAI=S-NSSAI#1))))).

[0102] S232: The 5GAMF 30A sends a request message (Nudm_UECM_Registration request) to the UDM 30C requesting registration of the terminal 20.

[0103] S233: UDM30C sends a response message (Nudm_UECM_Registration response) to the request message received in S232 to 5GAMF30A.

[0104] S234: The 5GAMF 30A sends a request message (Nudm_SDM_Get request) requesting subscriber information of the terminal 20 to the UDM 30C.

[0105] S235: The UDM 30C sends a response message (Nudm_SDM_Get response) to the request message received in S234 to the 5GAMF 30A.

[0106] S236: The 5GAMF 30A sends a message (Downlink NAS Transport) including information indicating acceptance of the registration request, including a list (identifiers) of network slices allowed to be connected, to the 6G base station 10B. For example, the message is represented as Downlink NAS Transport (NAS-PDU(Registration accept(Allowed NSSAI=S-NSSAI#1))).

[0107] S237: The 6G base station 10B sends a message (6G DLInformationTransfer) including information indicating acceptance of the registration request, including a list (of identifiers) of network slices allowed to be connected, to the terminal 20. For example, the message is expressed as 6G DLInformationTransfer (dedicatedNAS-Message(Registration accept (Allowed NSSAI=S-NSSAI#1))).

[0108] (Initial Registration Procedure (Case C)) An initial registration procedure for terminal 20 in a case where terminal 20 does not have a Configured NSSAI in advance will be described. Fig. 7 is a diagram showing an example of a fifth sequence diagram in the embodiment of the present invention. The processing of each step will be described below.

[0109] S301: The terminal 20 determines to connect to the 6G base station 30B based on the setting information related to the priority of the RAT (Radio Access Technology) stored in the terminal 20. Here, the setting information is set to connect to the 6GC as a default setting. Furthermore, the terminal 20 determines to connect to the network slice whose identifier is S-NSSAI#1.

[0110] S302: The terminal 20 transmits to the 6G base station 10B a request message (6G RRC Setup request) requesting settings related to the radio resource control protocol (RRC).

[0111] S303: The 6G base station 10B transmits to the terminal 20 a response message (6G RRCSetup) in response to the request message received in S302.

[0112] S304: The terminal 20 transmits a message (6G RRCSetupComplete) to the 6G base station 10B notifying completion of RRC setup. The message includes information indicating a registration request. The information includes a list of network slices (identifiers of network slices) to which connection is requested, which is explicitly indicated or implicitly indicated according to the subscriber information (for example, if not explicitly indicated, it may be specified in the specifications that it is based on the subscriber information). For example, the message is expressed as 6G RRCSetupComplete (dedicated NAS-Message (6G Registration request)).

[0113] S305: The 6G base station 10B transmits to the 6G UE MFP 30D a message (Initial UE message) including information indicating a registration request. The information includes a list of network slices (identifiers of network slices) to which connection is requested, which is explicitly indicated or implicitly indicated according to the subscriber information (for example, if not explicitly indicated, it may be specified in the specification that it is based on the subscriber information). For example, the message is referred to as an Initial UE message (NAS-PDU(6G Registration request)).

[0114] S306: The same processing as that from S210 to S231 in FIG. 5 is executed, except that 5GAMF30A is replaced with 6GAMF30D.

[0115] S307: The 6GAMF30D determines that the requested network slice (S-NSSAI#1) is not supported by the type of core network to which the device belongs, but is supported by a type of core network other than the core network to which the device belongs. This determination may be performed based on, for example, information indicating the relationship between the type of core network and the supported network slice.

[0116] S308: The 6GAMF30D sends to the 6G base station 10B a message (Downlink NAS Transport) including information indicating acceptance of the registration request, including a list of (identifiers of) network slices allowed for connection and a list of (identifiers of) network slices denied for connection. The list of (identifiers of) network slices denied for connection includes information (cause=available in 5GC) indicating that 5GC supports the network slice (i.e., indicating the result of the determination in S307). For example, the message is expressed as Downlink NAS Transport (NAS-PDU(6G Registration accept(Allowed NSSAI=S-NSSAI#2, Rejected NSSAI=S-NSSAI#1(cause=available in 5GC)))).

[0117] S309: The 6G base station 10B sends to the terminal 20 a message (6G DLInformationTransfer) including information indicating acceptance of the registration request, including a list of (identifiers of) network slices allowed for connection and a list of (identifiers of) network slices denied for connection. The list of (identifiers of) network slices denied for connection includes information (cause=available in 5GC) indicating that 5GC supports the network slice (i.e., indicating the result of the determination in S307). For example, the message is expressed as DLInformationTransfer(dedicatedNAS-Message(Registration accept (Allowed NSSAI=S-NSSAI#2, Rejected NSSAI=S-NSSAI#1(cause=available in 5GC)))).

[0118] S310: The terminal 20 stores the information contained in the message received in S309. The terminal 20 also determines to connect to the network slice having the identifier S-NSSAI#1.

[0119] S311: Terminal 20 decides to register with 5GC using the procedure described in Case A or Case B.

[0120] According to the above-described embodiment, in a wireless communication system that supports multiple types of core networks, it is possible to determine the base station and core network to which a terminal connects.

[0121] (Device Configuration) Next, a description will be given of an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processes and operations described above. The base station 10, network node 30, and terminal 20 include functions for performing the above-described embodiments. However, the base station 10, network node 30, and terminal 20 may each include only a part of the functions of the embodiments.

[0122] <Base Station 10 and Network Node 30> Fig. 8 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30. As shown in Fig. 8, 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. 8 is merely an example. As long as the operations according to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. Note that the network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different 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 by wire or wirelessly. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 or another network node 30 and acquiring, for example, information of a higher layer from the received signal. A communication unit including the transmitter 110 and the receiver 120 may be configured.

[0124] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 in a storage device, and reads out the information from the storage device as needed.

[0125] The control unit 140 performs the processes described in the embodiments, etc. The control unit 140 also performs processes related to communication with the terminal 20. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0126] <Terminal 20> Fig. 9 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 9, 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. 9 is merely an example. As long as the operations related to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. In addition, the communication device that becomes the resource holder 20 may have the same functional configuration as the terminal 20.

[0127] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving control signals, reference signals, etc. transmitted from the network node 30. A communication unit including the transmitter 210 and the receiver 220 may be configured.

[0128] The setting unit 230 stores various pieces of setting information received from the network node 30 by the receiving unit 220 in a storage device, and reads them out from the storage device as needed. The setting unit 230 also stores setting information that is set in advance.

[0129] The control unit 240 performs the processes described in the embodiments. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

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

[0131] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0132] For example, the base station 10, the network node 30, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 10 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The network node 30 may have the same hardware configuration as the base station 10. The above-described base station 10 and the terminal 20 may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

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

[0134] Each function in the base station 10 and the terminal 20 is realized by loading specified software (programs) 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 reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

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

[0136] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 8 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. For example, the control unit 240 of the terminal 20 shown in FIG. 9 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0137] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), 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 an embodiment of the present disclosure.

[0138] The secondary 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 appropriate medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0139] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, 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 frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0140] 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 outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0141] Furthermore, 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.

[0142] 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 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.

[0143] Fig. 11 shows an example configuration of a vehicle 2001. As shown in Fig. 11, the 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. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

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

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

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

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

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

[0149] 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 transmits and receives data via the communication port 2033 to and from 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 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.

[0150] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0151] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

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

[0153] <Additional Notes> (Additional Item 1) A terminal having: a control unit that stores a list of combinations of identifiers of network slices and types of core networks supporting the network slices, determines a network slice to connect to, determines the type of core network to connect to based on the list, and determines a base station to connect to a core network having the type, and a transmission unit that transmits a message including a registration request addressed to the base station for the core network to connect to. (Additional Item 2) The terminal according to Additional Item 1, further having a receiving unit that receives, from the base station, notification information including the type of core network to which the base station connects, and the control unit determines, based on the notification information, the type of core network to connect to and the base station to connect to. (Additional Item 3) The terminal according to Additional Item 1, wherein the message includes information indicating the type of core network to connect to. (Supplementary Item 4) A network node having: a receiving unit that receives from a terminal a first message including a registration request, the first message including a list of network slices to which connection is requested, which are explicitly indicated or implicitly indicated according to subscriber information; a control unit that determines that the network slice to which connection is requested is not supported by the type of core network to which the terminal belongs, but is supported by a type of core network other than the core network to which the terminal belongs; and a transmitting unit that transmits to the terminal a second message including information rejecting connection to the network slice and information indicating the result of the determination. (Supplementary Item 5) A terminal comprising: a transmitter that transmits a first message including first information indicating a registration request to a first network node; a receiver that receives from the first network node a second message including third information indicating acceptance of the registration, the second message including second information indicating that the first network slice is not supported in a first type of core network to which the first network node belongs but is supported in a second type of core network; and a control unit that stores the third information and decides to connect to the first network slice, wherein the transmitter transmits a third message including fourth information indicating a registration request to a second network node belonging to the second type of core network.(Supplementary Item 6) A communication method executed by a terminal, comprising the steps of: storing a list of combinations of identifiers of network slices and types of core networks supporting the network slices; determining a network slice to connect to; determining a type of core network to connect to based on the list; determining a base station to connect to a core network having the type; and sending a message to the base station including a registration request addressed to the core network to connect to.

[0154] Any of Supplementary Items 1 to 6 makes it possible to determine the base station and core network to which a terminal is connected in a wireless communication system that supports multiple types of core networks.

[0155] (Supplementary Notes on the Embodiments) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and 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 base station 10 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 random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

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

[0157] Each aspect / embodiment described in the present disclosure may be implemented using any of the following standards: LTE (Long Term Evolution), LTE-Advanced (LTE-A), 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 number)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 ( The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0158] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be rearranged unless it is consistent. 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.

[0159] In this specification, a specific operation described as being performed by the base station 10 may be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

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

[0161] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

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

[0163] 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.

[0164] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if 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 transmission media.

[0165] 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.

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

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

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

[0169] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions 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 intended to be limiting in any way.

[0170] In the present 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 a macrocell, a small cell, a femtocell, and a picocell.

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

[0172] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

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

[0174] 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.

[0175] At least one of the base station and the mobile station may be referred to as 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 mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (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 be a device that does 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.

[0176] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments 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, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0177] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

[0178] 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. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

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

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

[0181] 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."

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

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

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

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

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

[0187] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0188] 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.

[0189] 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 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Tire pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A terminal having: a control unit that stores a list of combinations of network slice identifiers and types of core networks that support the network slices, determines a network slice to connect to, determines a type of core network to connect to based on the list, and determines a base station to connect to a core network having the type; and a transmission unit that transmits a message to the base station including a registration request addressed to the core network to connect to.

2. The terminal according to claim 1, further comprising a receiving unit that receives, from the base station, notification information including the type of core network to which the base station is connected, and the control unit determines, based on the notification information, the type of core network to which the base station is connected and the base station to which the base station is connected.

3. The terminal according to claim 1, wherein the message includes information indicating the type of core network to which the terminal is connected.

4. A network node having: a receiving unit that receives from a terminal a first message including a registration request, the first message including a list of network slices to which connection is requested, either explicitly indicated or implicitly indicated according to subscriber information; a control unit that determines that the network slice to which connection is requested is not supported by the type of core network to which the terminal belongs, but is supported by a type of core network other than the core network to which the terminal belongs; and a transmitting unit that transmits to the terminal a second message including information rejecting connection to the network slice and information indicating the result of the determination.

5. A terminal comprising: a transmitter that transmits a first message including first information indicating a registration request to a first network node; a receiver that receives from the first network node a second message including third information indicating acceptance of the registration, the second message including second information indicating that the first network slice is not supported in a first type of core network to which the first network node belongs but is supported in a second type of core network; and a control unit that stores the third information and decides to connect to the first network slice, wherein the transmitter transmits a third message including fourth information indicating a registration request to a second network node belonging to the second type of core network.

6. A communication method executed by a terminal, comprising the steps of: storing a list of combinations of network slice identifiers and types of core networks supporting the network slices; determining a network slice to connect to; determining a type of core network to connect to based on the list; determining a base station to connect to a core network having the type; and sending a message to the base station including a registration request addressed to the core network to connect to.

Images